From changed record to the right channel
NgageFlow watches IBM Maximo, IFS and SAP, and posts what matters.
Before and after
The same piece of work, as it waits today and once NgageFlow has run it.
Purchase order 4500017 was changed
- From
- SAP notifications
- Says
- A field on this order changed.
- Link
- None
Unread Under 213 others, found next week
Alert flow
- 1Notice the new delivery dateSAP
- 2Filter for what mattersSAP
- 3Find the work it holds upMaximo
- 4Post to #buyersTeams
PO 4500017 from Nordia Components now arrives 9 days late.
- New date
- 23 November, was 14 November
- Holds up
- Work order 3452 in IBM Maximo
- Owner
- Buyer, site 100
Escalates No reply in 4 hours, it goes to the lead buyer
Illustrative, on a test landscape. Names, numbers and amounts are samples.
What runs between SAP and Teams
Every changed purchase order starts a run like this.
Changed in SAP: the delivery date on PO 4500017
- 1 Notice the new delivery datePO 4500017, 9 days later SAP
- 2 Filter for what mattersMore than 5 days, for open work SAP
- 3 Find the work it holds upWork order 3452, pump P-114 Maximo
- 4 Post to #buyersEscalates if unanswered in 4 hours Teams
- 1
Notice the new delivery date
SAP, purchase orders
The flow watches purchase orders and starts when a delivery date moves.
- 2
Filter for what matters
The filter you set
Most changes stop here, silently. This one passes.
- 3
Find the work it holds up
IBM Maximo, work orders
The agent adds the context a buyer needs, from the system that holds it.
- 4
Post to #buyers
Teams, #buyers
One message with a link to act. If nobody acts, it goes up.
Runs on IBM Maximo, IFS and SAP
Any record you choose can start a flow.
| System | What it holds | What NgageFlow does |
|---|---|---|
| IBM Maximo | Work orders, assets, meter readings | Watches status, priority and readings |
| IFS | Customer orders, work orders, invoices | Watches the records you choose |
| SAP | Purchase orders, sales orders, deliveries | Watches dates, amounts and status |
| Teams and Slack | Your channels | Posts the message, escalates if nobody acts |
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 set the rules
Four settings decide which changes reach a channel.
- Which recordsPurchase orders for site 100
- Which changesA delivery date that moves 5 days or more
- Which channel#buyers in Teams
- When to escalateNo reply in 4 hours, to the lead buyer
Questions about ERP alerts
How does NgageFlow know a record changed?
A trigger watches the records you choose in IBM Maximo, IFS or SAP, and starts the flow when one is created or changed.
Will it flood our channels?
No. Filters drop every change you did not ask for, so each channel gets fewer, sharper messages.
Slack or Teams?
Either, or both. Each connects in one click, and one flow can post different messages to different channels.
Describe the alert you need
Name the record, the change and who should hear.
Or write to hello@ngagesuite.com
Whoever reads the alert can ask the follow-up questions in NgageChat. See NgageChat on work orders