Progress and cost apps for projects
Daily reports, time and cost on IBM Maximo, IFS and SAP.
A daily report from one sentence
The activity from IFS, the cost from SAP, in one daily report. An illustrative app on a test landscape.
Describe your app
Build a daily progress report app for site engineers.
Web, at a desk
IFS ActivitiesSAP Cost
Phone, at the site
9:41
Daily report
- ActivityIFS
- A-110, foundations
- Concrete poured today
- 12 m³
- Crew hours
- 48
- Budget left on A-110SAP
- 20%
Apps project teams ask for
Each row is the sentence a team would type, the ERPs it reads and where it runs.
| The app, in one sentence | Reads | Runs on |
|---|---|---|
| “A punch list app for site handover.” | IFS | Phone and web |
| “A time and expense form tied to project activities.” | IFSSAP | Phone and web |
| “A board of actual against budget cost by project.” | IFSSAP | Web |
| “A milestone sign-off for project managers.” | IFS | Web |
Controls that hold in every app
Official interfaces, the signed-in user’s permissions, a person’s review and checks on every commit, whichever team asks.
- Official interfaces
- Reads and writes go through each ERP’s official interfaces, never the database.
- Your users’ permissions
- Every call runs as the signed-in user, never a shared service account.
- Reviewed code
- A person reviews all AI-written code before it merges.
- Every commit checked
- Secret scanning and static analysis. A finding blocks the merge.
Questions from project teams
Can engineers report progress from site?
Yes. The app runs on phones and in a browser. Each engineer signs in as themselves and works within their own ERP permissions.
Can a report wait for the project manager?
Yes. The app can send each report for approval before it posts. You decide which writes wait.
Does it connect to project and cost data?
Yes. NgageCode works from how your ERP structures projects, activities and cost, and reads them through official interfaces. One app can read two ERPs, such as activities in IFS and cost in SAP.
Describe the app your team needs
One sentence is enough to start: what the app does and who uses it.
We build it with you, live, in a safe test setup.