NeoGen CMMS
Deploy and get value

Help with the parts nobody enjoys

Sorting a vaguely worded request, spotting that two people reported the same fault, reading four years of history before a handover. Good places for a suggestion — as long as a person still decides.

Sorting a new request

Suggested

Someone typed

“the office on block b is boiling again, aircon making a noise”

  • Likely asset92%

    AHU-14

    The words “Block B” and “not cooling” match this unit’s history.

  • Category88%

    HVAC — no cooling

    Matches 34 previous requests worded the same way.

  • Suggested priority71%

    High

    This unit serves a server room. Past jobs here were raised High.

AcceptChange it

A suggestion, never a decision. Nothing is raised until a person agrees.

  • A suggestion, never an action

    Every suggestion shows its confidence and its reasoning, and waits for a person to accept or change it.

  • Traceable to the record

    Suggestions come from your own closed work orders, and you can open the jobs they came from.

  • Saves the dull minutes

    Classifying, de-duplicating and summarising are exactly the tasks worth handing over.

The same fault, reported twice

Two people report one problem thirty minutes apart, and two technicians get sent.

  • Similar requests on the same asset are flagged, not merged automatically
  • You merge or keep both, and the second reporter still gets an answer
  • One van trip instead of two

Two people, one fault

Possible duplicate
  • REQ-447109:12

    “AC not working in the big meeting room”

    Reception

  • REQ-447409:41

    “Meeting room 2 is really hot”

    A tenant

Same room, 29 minutes apart84%
Same locationBlock B, meeting room 2
Same symptomNo cooling
SuggestionMerge into one work order
MergeKeep both

One van trip instead of two, and the second reporter still gets told what happened.

Four years of history, in a paragraph

Nobody reads seventeen work orders before a handover. They should not have to.

  • A draft handover note assembled from the asset’s closed jobs
  • Recurring themes surfaced rather than buried in a list
  • Every sentence traces back to a job you can open and check

Handover note

Drafted from the record

AHU-14 has had seventeen jobs since 2021, most of them belt tension or filter changes. A bearing was replaced in 2022 after a noise complaint. Filter Δp has been creeping up since April and is now above the change threshold. Nothing outstanding, but the belt is due at the next service.

  • Jobs on this asset17 in 4 years

    Drawn from closed work orders on this asset — open any of them to check the summary against the source.

  • Recurring themeBelt and bearing wear

    Drawn from closed work orders on this asset — open any of them to check the summary against the source.

  • Longest gap14 months, 2022–23

    Drawn from closed work orders on this asset — open any of them to check the summary against the source.

A draft to check, not a fact to quote. Every sentence traces back to a job you can open.

What to take with you

The single biggest cause of a second visit is a part that stayed on the shelf.

  • Parts commonly used on this fault, from your own history
  • Current stock shown next to each suggestion
  • The technician still decides what goes in the van

What to take with you

From past jobs

Eleven jobs on this asset class started with the same symptom.

  • V-belt A48

    9 of 11 similar jobs

    18 in stock
    SuggestionTake it
    Based onParts issued on similar closed jobs
  • HEPA filter 24×24

    6 of 11 similar jobs

    3 in stock
    SuggestionTake it
    Based onParts issued on similar closed jobs
  • Bearing 6204-2RS

    2 of 11 similar jobs

    5 in stock
    SuggestionProbably not needed
    Based onParts issued on similar closed jobs
The technician decides what goes in the van. This just saves the second trip back.

Ready to simplify your maintenance operations?

Book a personalized demo and see how NeoGen CMMS fits the way your team already works.

No obligation. Just 30 minutes of your time.

FAQ

AI Assistance questions

Does it close work orders on its own?

No. Nothing here takes an action. Every suggestion is presented with its confidence and a plain accept-or-change decision, because a maintenance record a person did not agree to is not evidence.

What is it learning from?

Your own closed work orders — how your team words requests, which assets they refer to, and which parts those jobs actually consumed.

What happens when it is wrong?

You change it, the same way you would correct a colleague’s guess. Because a person confirms every suggestion before it lands, a wrong suggestion costs a moment rather than a wasted visit.

Can we turn it off?

Yes. It is assistance, not a dependency — the system works exactly as described on every other page of this site without it.