Skip to content

Raise, plan and close IFS work orders by typing a sentence

The maintenance backlog does not grow because people are lazy. It grows because reporting a fault properly means finding the right screen, the right object, the right organisation code and four fields nobody remembers. NgageChat removes the navigation, not the discipline.

Book a demo How it works
NgageChat — work orders IFS Cloud connected

Raise a fault report for pump P-114 — mechanical seal is leaking, water on the floor

search_ifs_pages fault report, maintenance
get_ifs_entity_api_spec FaultReportHandling
ifs_get_defaults FaultReportSet/_Default()
ifs_get_server_time site 100 local time

Found pump P-114 at site 100 (Utilities / Pump House 2). I have the defaults from IFS — I just need the priority.

  • Fault code options came back from your IFS enum: Leakage, Vibration, Noise, Overheating, No Function
  • I have pre-selected Leakage based on your description

Priority 2, it can wait until the morning shift

Confirm before writing to IFS

Object
P-114
Site
100
Fault code
LEAKAGE
Priority
2
Reported by
j.okafor
Reported date
2026-08-03 21:40
Yes, create it Change something

Yes, create it

ifs_create_record POST FaultReportSet

Fault report 41207 created

Written to IFS Cloud as j.okafor. Visible in Aurena now.

Fault report
41207
State
Registered

Created under the reporter’s own IFS account — not a shared integration user.

What can NgageChat do with IFS work orders?

NgageChat is a work order chatbot for IFS Cloud. A technician describes a fault in plain English and NgageChat finds the right IFS projection, resolves the equipment object, site and required fields against your system, shows a summary for approval, and creates the work order or fault report through the IFS OData REST API under that person’s own IFS login.

Last reviewed 3 August 2026 · NgageChat by EX10

What you can ask it

  • Overdue work orders by site, discipline or priority
  • Work order history for a specific object or functional location
  • Open operations and their planned dates
  • Material demand and reservations on a work order
  • Who a work order is assigned to and its current state

What it can change in IFS

  • Create a fault report from a plain-language description
  • Create a work order and attach it to an equipment object
  • Add operations and material lines to an existing work order
  • Update priority, dates, planner or work type
  • Release, start, complete or cancel a work order via IFS bound actions
  • Attach a photograph or document to the work order

Every write is shown to you as a complete summary and only executes after you approve it — then runs under your own IFS login, inside your own IFS permissions.

Try it like this

Things people actually type

Which work orders at site 100 are overdue?
Raise a fault report for pump P-114 — the mechanical seal is leaking
Show me all corrective work orders on the boiler house raised this month
Add a 4-hour inspection operation to work order 3391
Release work order 3391
What was the last work done on compressor C-22?

Why it matters

The friction this removes

None of this is a failure of the ERP. It is the cost of a very large system being used occasionally by people who were trained on it once.

The fault gets reported to a WhatsApp group

Because a message takes eight seconds and someone who touches IFS twice a month has to find the screen first. The work never enters the system, so the history is wrong and the next planner is flying blind.

Supervisors become data-entry clerks

One person on the team knows the screens, so every job routes through them. That is a bottleneck disguised as expertise.

Nobody can answer "what is late" without a report

The answer exists in IFS. Getting it out means a saved search someone built two years ago and nobody dares change.

IFS objects this typically touches

FaultReportHandlingActiveSeparateSetWorkOrderHandlingMaintenanceObjectWorkOrderOperation

Exact projections depend on your configuration and IFS release — NgageChat resolves them from its index of the IFS Cloud data model, with your custom fields read live from your environment.

FAQ

Questions about work orders & maintenance

Can NgageChat actually create a work order in IFS, or does it just draft one?
It creates it. NgageChat calls the IFS OData REST API and writes the record to your environment, then returns the work order number. Nothing is written until you approve the on-screen summary, and the call is made with the signed-in user’s own IFS token.
Can a technician release or complete a work order by chat?
Yes, if their IFS permissions allow it. Release, start, complete and cancel are IFS bound actions, and NgageChat calls them the same way Aurena does. If the user’s permission set does not grant the action, IFS refuses it and NgageChat reports the refusal.
Will it pick the right equipment object?
It searches your IFS data for the object you named and confirms what it found before doing anything else. If several objects match "P-114", it asks which one rather than guessing.
Can it attach a photo of the fault?
Yes. Attach a photograph in the chat and NgageChat reads it to help draft the description, and can link a document reference to the work order or object in IFS.

Also worth reading

HSE & field reporting Inventory & stock Manufacturing & shop orders

Early access

See it do this against your own IFS environment

Bring one real scenario from your system. Thirty minutes, no slideware — we run it live and you watch every step.

Book a demo See how it works