Work orders come down. What actually happened goes back up.
Your ERP knows what was meant to be made; the floor knows what was. VZIAM MES imports work orders, articles, bills of materials and routings from it, and posts good quantities, rejects and real cycle times back when each order closes.
The plan and the record are reconciled by hand, once a day, by one person.
Somebody keys yesterday’s output into the ERP from a stack of sheets. Until they do, the planning system describes a factory that does not exist; once they have, it describes one that existed yesterday. That person is also the only place the two systems touch.
Typed instead of confirmed
When the order does not reach the machine, the operator types what is being run instead of confirming it, which is where most entry errors come from.
A day behind the floor
Results keyed in at the end of the shift or the next morning leave the ERP describing a factory that existed yesterday.
Posting back is a project
Reading orders down is bounded work. Posting results back touches your ERP’s validation rules, your work order lifecycle and somebody’s month-end close, and it is a project with your ERP team in it rather than a connector we can price sight unseen.
Both directions, with the floor’s figures protected.
The exchange runs through a REST API or JSON and CSV files, mapped field by field with your ERP team, on a schedule or by hand. There is no packaged connector to install: the mapping is the work.
- 01
Orders and bills of materials at the terminal
Released work orders arrive ready to start and planned ones as drafts, with the article, its bill of materials and its routing. The operator confirms what they are running instead of typing it, which is where most of the entry errors were.
The terminal the order arrives at - 02
Results posted when the order closes
Good quantities, rejects and real cycle times go back when the order closes, from the same record the line produced. Nobody has to remember what happened in order to enter it, and the ERP never receives a total someone typed.
The order’s record the results come from - 03
The floor wins once an order runs
Once an order is in production, a change from the ERP to its target quantity or its routing waits for a supervisor’s approval. A late edit upstream cannot rewrite what the line is doing.
- 04
Unknown data is refused, not guessed
An order that names an article VZIAM MES does not know is not created, and the rejection is logged with its reason. Each exchange reports what it accepted and what it refused, so the ERP team sees the gap rather than discovering it.
Where VZIAM MES runs
Four people on one exchange.
The ERP team owns the mapping, planning releases the orders, the supervisor decides what changes once a line is running, and the operator confirms. Each sees the part that is theirs.
The mapping is written with the people who own the ERP.
Fields are mapped one by one against your ERP’s own data, and each exchange reports what it accepted and what it refused, with the reason. An order naming an unknown article is refused, not guessed.
Where VZIAM MES runs- Accepted
- Created or updated
- Refused
- With its reason
- Unknown article
- Order not created
Release an order in the ERP, see it at the line.
A released order arrives ready to start; a planned one arrives as a draft. An order not yet started can still be updated from the ERP, so planning keeps its tool and the line keeps its plan.
The terminal the order arrives at- Planned
- Draft
- Released
- Ready to start
- Not yet started
- Updated from the ERP
A change to a running order waits for a person.
Once an order is in production, a new target quantity or routing from the ERP is held until a supervisor approves it. A late edit upstream cannot rewrite what the line is doing behind its back.
How a correction is audited- Target or routing
- Held
- Decided by
- The supervisor
- Meanwhile
- The line runs as started
Confirm what is running, never type it.
The order, its article and its bill of materials are on the terminal already. The operator confirms them, declares stops and rejects, and the results go back to the ERP from that record when the order closes.
The order’s record the results come from- Order
- Confirmed
- Bill of materials
- Already there
- Results
- Sent at close
What crosses, in each direction.
- From the ERP
- Orders, articles, BOMs, routings
- To the ERP
- Good, rejects, cycle times
- Results sent
- When the order closes
- Interface
- REST API, JSON, CSV
- Runs
- Scheduled or on demand
- Order in production
- Changes held for approval
- Unknown article
- Order refused, logged
- Packaged connector
- None, mapped per plant
Frequently asked questions.
Tell us which ERP you run and who owns it, and ask the engineers what the mapping would cover.
Book a callNo. The exchange is a REST API or JSON and CSV files, mapped to your ERP’s fields with the team that owns it. That takes longer to start than installing a connector would, and it means the mapping is written for your data rather than for a demo.
Orders down, usually. Reading work orders and bills of materials into the MES is bounded work and removes typing at the terminal. Posting results back touches your ERP’s validation rules and month-end close, so it is planned with your ERP team as a step of its own.
The change waits. Once an order is in production, its target quantity and routing are not rewritten from the ERP without a supervisor’s approval, so the line keeps doing what it was started on.
On a schedule you set, hourly or nightly for example, and on demand by an administrator. Results go back when each order closes, from the record the line produced.
The rest of what we do.
Plan the change before it reaches the line.
Request a demo and an engineer looks at how your production runs today, shows how the software would fit around it, and where a pilot on one line would start.
01Pick a time
Choose a slot in the calendar, and note what you make and what reads your machines today.
02Screen shared with an engineer
A video call with someone who builds the software, in English or French.
03What would connect
For each machine, its path: native (OPC UA, MQTT or HTTP push), through a gateway, or nothing to build.