The order’s record, built from what ran.
The routing the order actually followed, every run on every machine, the stops that belong to it, its materials against the bill of materials and the checks it passed, in one record, printable as a PDF that can still be searched years later.
A record assembled afterwards inherits every gap in its sources.
Production holds the counts, quality the checks, the store the lots, and someone puts them together once the order is done. Whatever none of them wrote down is simply absent, and an absence looks the same as a check that passed. VZIAM MES computes the record from the data the line produced, so a missing declaration shows as missing.
Four rules the record is held to.
Each one is a way a batch record can look complete and be wrong. The record is computed so that it cannot.
- 01
The order keeps the routing it followed.
When the order first starts, it takes a copy of its routing. A routing edited afterwards does not rewrite what this order did.
- 02
A stop belongs to the run it happened in.
Stops are attached run by run, not by the order’s overall time window. On an order that moved from one machine to another, a stop on the first while only the second was running is not counted, and a stop that straddles two orders counts only for its share.
- 03
Zero is a value, not a gap to fill.
A run that produced nothing shows nothing. The record never borrows the machine’s other output to fill it; counts the machine made outside the run are listed as a diagnostic instead.
- 04
Closing with something undone takes a comment.
At closure the record lists what is not done: quantity short of the order, a component expected and never declared, a check not carried out. Closure is not blocked, but the comment is written into the record.
Everything one order did, in one place.
Runs, operation by operation
Each operation with the machine or workstation that ran it, its good quantity and rejects in its own unit, and which operation’s output counts as the order’s.
Materials against the bill of materials
Expected consumption beside what was declared, line by line, with components declared outside the bill and components never declared both shown.
Stops and checks of the same order
The stops attached to its runs, with their reasons and corrections, and its quality checks with their results and rechecks.
The finished lot and its state
The lot the order produced, with its state named by the server, so the printed record and the screen say the same thing about it.
Forms due, and forms missing
Forms due at the start or end of the order are listed with their submissions. One not filled in does not stop the order; it shows on the order’s report, where it can be discussed the next morning.
A PDF composed from the data
The printable record is built from the data rather than captured from the screen, so its text can be selected, searched and archived.
What the record commits to.
- Scope
- One work order and its finished lot
- Routing
- Copied when the order first starts
- Stops
- Attached run by run, prorated at the edges
- Materials
- Reconciled against the bill of materials
- Closure
- Undone items listed; a comment is required
- Output
- PDF with searchable text
Frequently asked questions.
Bring a recent batch record and ask the engineers where each part would come from.
Book a callThe routing the order followed, each run with its machine or workstation and quantities, the stops attached to those runs, material consumption against the bill of materials, quality checks and their rechecks, the finished lot and its state, and any comment made at closure.
No software makes a plant compliant on its own; compliance belongs to your validated system and procedures. VZIAM MES keeps audited corrections, read-only submitted forms and the reasons behind release decisions, and we go through the requirements with your quality team.
Yes, deliberately. The closure lists what is not done (production short of the order, a component never declared, a check not carried out) and asks for a comment, which goes into the record. Blocking would put the paperwork on the line’s critical path at three in the morning.
The order keeps the copy it took when it first started, and its record shows that routing. Orders started after the change follow the new one.
As a PDF composed from the data, with text that can be selected and searched. Reports across orders export as CSV that opens in Excel.
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.