Apps, forms and reports on your ERP
Six kinds of app NgageCode builds on IBM Maximo, IFS or SAP. Each one starts as a sentence and is reviewed by a person before it merges.
Six kinds of app, each from one sentence
Each card shows the sentence and a sample of what it produced. Open a kind to see the full example.
-
Custom apps
“An app for stores to raise purchase requisitions.”
Purchase requisitionsIFS
4102 Mechanical seal 2 Waiting 4101 Impeller 1 Released 4099 Drive belt 4 Released 4096 Gasket set 6 Closed -
Custom forms
“A goods receipt form with lookups on PO lines.”
Goods receiptSAP
Purchase order4500018PO line10, Mechanical sealQuantity received2 of 2 -
Custom reports
“Open work orders by site and priority.”
Open work ordersIBM Maximo
Site P1 P2 P3 Total Site 100 3 8 12 23 Site 200 1 5 9 15 Site 300 0 4 6 10 -
Dashboards
“A work order board for the planning team.”
Planning boardIFSSAP
24Open6Overdue80%of budget3391 P-114 Within 3417 C-22 Over -
Integrations and APIs
“Send approved invoices to our payment system and mark them sent.”
Invoice syncSAPREST
5105600103 480.00 Sent 5105600102 96.00 Sent 5105600101 2,050.00 Retrying -
Industry accelerators
“A permit to work app for every site.”
For partners and centres of excellence who adapt one ERP to one industry.
Permit 0318Pump house, site 100IBM Maximo
- Isolation points locked
- Gas test recorded
- Area barriered
- Supervisor sign-off Waiting
Example apps by team
What each team might describe, for a desk or a phone. Illustrative examples. See all six use cases
| Team | The app they describe | Kind |
|---|---|---|
| Manufacturing | “An output and scrap app for line operators.” | App |
| Maintenance | “An inspection checklist that posts to the work order.” | Form |
| Field service | “A day view app for our field technicians.” | App |
| Supply chain | “A stock count by bin for the stores team.” | Form |
| Projects | “A daily progress report for each site.” | App |
| Finance | “An approvals inbox for invoices on hold.” | App |
Rules every app follows
Whatever kind of app you describe, these stay the same. Read about security
- Interfaces
- Each ERP’s official interfaces, never the database.
- Permissions
- Each user signs in as themselves, within their ERP permissions.
- Review
- A person reviews all AI-written code before it merges.
- Every commit
- Secret scanning and static analysis. Any finding blocks the merge.
- Credentials
- No coding tool ever holds production ERP credentials.
Questions about what it builds
What if our app is not one of the six?
Describe it anyway. The six are examples, not a limit, and we will tell you plainly if an app is not a fit.
Which ERPs can the apps run on?
IBM Maximo, IFS and SAP work out of the box. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
Can one app use two ERPs?
Yes. One app can work across two of IBM Maximo, IFS and SAP, for example the asset in IFS and the cost in SAP.
Do the apps work on phones?
Yes. The same app runs in a browser at a desk and on a phone at the site, and each user signs in as themselves.
How do we start?
Describe one app your team needs, in a sentence. We build it with you on your scenario, in a safe test setup.
Start with one app your team needs
Describe it in a sentence. We build it with you on your scenario, in a safe test setup.