From fault report to work order
Fault reports become work orders in IBM Maximo, IFS or SAP.
Before and after
The same piece of work, as it waits today and once NgageFlow has run it.
Pump P-114 is leaking again
- From
- Shift lead, site 100
- Sent
- 06:40
- Says
- Seal leak at the pump house, getting worse
Waiting Read at 09:00, then keyed into Maximo
Work order flow
- 1Read the fault reportOutlook
- 2Check open work on P-114Maximo
- 3Check the seal at the storeSAP
- 4Raise the work order, tell the crewMaximo
Work order 3452 is raised in IBM Maximo on pump P-114.
- Asset
- P-114, pump house, site 100
- Priority
- 2, no other open work on P-114
- Part
- Mechanical seal, 6 in stock in SAP
Raised Triaged, checked and raised by NgageFlow
Illustrative, on a test landscape. Names, numbers and amounts are samples.
What runs between report and Maximo
Every fault report or alarm starts a run like this.
New email in the maintenance inbox: pump P-114 is leaking again
- 1 Read the fault reportP-114, seal leak, getting worse Outlook
- 2 Check open work on P-114No open work, job plan JP-20 Maximo
- 3 Check the seal at the storeMechanical seal, 6 in stock SAP
- 4 Raise the work order, tell the crew3452, priority 2, crew told in Teams Maximo
- 1
Read the fault report
Outlook, the maintenance inbox
The agent finds the asset and writes a clean work description.
- 2
Check open work on P-114
IBM Maximo, work orders
A second report on the same asset joins the open work order instead.
- 3
Check the seal at the store
SAP, stock
In this landscape the stores run on SAP, so the part is checked there.
- 4
Raise the work order, tell the crew
IBM Maximo and Teams
Priority 1 work waits for the planner. This one runs alone.
Runs on IBM Maximo, IFS and SAP
One flow can read two ERPs in one run.
| System | What it holds | What NgageFlow does |
|---|---|---|
| IBM Maximo | Assets, work orders, job plans | Checks open work, raises the work order |
| IFS | Equipment objects, work orders | The same, on IFS |
| SAP | Equipment, maintenance orders, stock | The same, and checks spare parts |
| Webhooks and email | Alarms and fault reports | Start a run for each new fault |
IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
You choose what waits
Routine faults run alone. The rest wait for a person.
- Read and triage the reportRuns alone
- Raise priority 2 and 3 workRuns alone
- Raise priority 1 workWaits for the planner
- Work that needs a shutdownWaits for the site manager
Questions about work order automation
How does it avoid duplicate work orders?
Before it raises anything, the flow reads the open work on the same asset. A second report joins the open work order, so a noisy sensor raises one work order, not one per alarm.
Can an alarm start it, not just an email?
Yes. A webhook from condition monitoring starts the same flow as the maintenance inbox.
Does the person who reported it hear back?
Yes. A second flow watches the work order status and tells them when the work is done.
Describe your fault process
Write it the way you would brief a new planner.
Or write to hello@ngagesuite.com