Augos Factory / For ERP users
For plants that plan in an ERP
Plans go down to the line. Actual results come back.
Your ERP knows what should be made. The line knows what was made. Augos Factory connects the two through a documented API, with one job reference from start to finish.
How the link works
One job reference closes the loop
In most plants someone retypes the gap between the plan and the floor. Here the ERP's job reference travels with the job, so nobody has to.
One job, down and back
Illustrativethat can call the API
is set up, then queues it
Down · set by your ERP
- Job reference
- PF-1042
- Product
- Pouch 100 g
- Pack size
- 100 g
- Planned quantity
- 5,000
Back · pulled by your ERP
- Job reference
- PF-1042
- Good units
- 3,580
- Rejects
- 0
- OEE
- 64.0%
The same PF-1042 stays on the job at the terminal, on every stop and on the result.
How the Augos ERP integration works. A schematic on demo data, not a customer.
1 · Jobs ready on the terminal
The operator picks the job, not types it
Your ERP creates a job and queues it on the line's terminal as a pending job. Operators pick it from the job list instead of setting it up by hand. Every job carries the ERP's reference from the first unit.
- The product and pack size must already be set up in Augos. A job for one that isn't is rejected, so it never reaches the line.
- The pack size sets the rated speed, so OEE is measured against the right standard for that job.
| Set by your ERP | Why it matters |
|---|---|
| Job reference | The shared key between your ERP and Augos |
| Product | Must already be set up in Augos |
| Pack size | Sets the rated speed used for OEE |
| Planned quantity | The target for planned against actual |
2 · Results back to the ERP
Actuals land where costing happens
Your ERP calls the Augos API for job results when it needs them. It can ask by date range, by product or by job reference. Each result includes units produced and other job metrics.
The actuals then sit in your ERP for costing, stock and planning, with no manual capture. Results are pulled by your ERP when it asks, not pushed live.
Deliberately scoped
Only jobs and results cross the boundary
Products stay in Augos. Brand, name, pack size, rated speed and pulse factor are set up during onboarding, not sent from the ERP.
Rated speed and pulse factor drive OEE and unit counts, so keeping them in one place keeps the numbers trustworthy. Plants that already set products up this way keep their current setup.
Questions
The ERP link, answered
Which ERPs work?
Any ERP that can call the documented Augos API. Syspro is a common example. There is no pre-built connector to install; your IT team or ERP partner connects through the API.
Who sets up the link?
Your ERP partner or IT team, using the Augos API. We supply the API details and test the first jobs with you.
Can products come from the ERP too?
No. Products are set up in Augos during onboarding, because rated speed and pulse factor drive OEE and unit counts. The ERP sends jobs for products that are already set up.
Is it a real-time sync?
No. Jobs are queued on the terminal when your ERP sends them. Results are pulled by your ERP when it asks for them.
Is it running anywhere today?
Yes. Jobs from an ERP run live today at one South African food group.
Do we need the link to start?
No. Lines run from a product list in your workbook. The link removes job set-up at the line and returns actuals to your ERP.
See your ERP jobs on the line.
Thirty minutes with a manufacturing specialist, with your planner or ERP partner if you like.
- Jobs from your ERP to the terminal
- Results back to your ERP by job reference
- Prices in rand, ex VAT
A manufacturing specialist replies within two business hours to set a 30-minute call.