Each finished lot knows what went into it.
Starting a work order creates its finished lot. Material lots are scanned against it as they are consumed, a blocked or expired lot is refused at the machine, and a recall is traced through every level of the genealogy, upstream and downstream.
A recall you cannot bound becomes a recall of everything.
When the link between a finished lot and the material inside it is written on a batch sheet, the link is only as complete as the sheet. Faced with a supplier’s call and an incomplete record, the only safe answer is to take back more than you need. VZIAM MES makes the link at the moment of consumption, at the machine, and keeps it whatever happens to the lot afterwards.
Five rules the genealogy is held to.
Each one exists because the opposite produced a genealogy that looked right and was not.
- 01
One work order, one finished lot.
The lot is created when the order starts and stays the same for the whole order, even across machines. Splitting production into two lots means closing the order and starting another.
- 02
A lot that cannot be used is refused at the machine.
Consuming a lot that is quarantined, rejected, expired or blocked is refused, with a message that says what to do instead. A lot the system has never seen is not blocked: unreferenced material can still be declared.
- 03
A declaration is never edited, only offset.
Correcting a consumption adds a credit line that references the original. Both stay readable, and the gap between them is the trace of the error. Cancelling more than remains is refused.
- 04
A block never stops a machine.
If a recalled lot is in production, it goes into logical quarantine, the run continues and management gets a critical alert. Stopping the line is a decision for a person, not a side effect.
- 05
The software does not claim to contain what it no longer holds.
VZIAM MES does not know what was shipped. A lot already at a customer is shown as impacted, never as quarantined, and containment is declared by the person who went to look.
From the scanner at the machine to the recall.
Scanned at the machine
Any USB or Bluetooth scanner in keyboard mode, with no driver. GS1 codes fill in the lot number, quantity and expiry, and an expired lot is flagged. Typing the number by hand always works.
Consumption against the bill of materials
Actual use is compared with what the bill of materials expects for the good quantity produced. A tolerance per line flags over- and under-consumption without stopping the line or the closure.
Substitutions recorded, not refused
A component outside the bill of materials is accepted and flagged. Refusing it would turn a normal substitution on the floor into a gap in the genealogy.
Lot states, each change with a reason
Available, consumed, quarantined, rejected, expired or blocked. Every change records who, when, from what, to what and why. Rejected is final, and expiry is the only automatic change.
Recall through every level
Search by your lot number or the supplier’s label number. The recalled lot is blocked and everything made from it is quarantined, level after level; lifting the recall releases only the lots that recall blocked.
One list of what cannot be used
A failed critical point, a recall, an expiry or a manual decision: every unusable lot in one list, each with the origin of its block.
What the module commits to.
- Lot rule
- One work order, one finished lot
- Lot number
- From the ERP, or a mask per article or site
- Scanner input
- Keyboard mode, GS1 lot, quantity and expiry
- Genealogy
- Upstream and downstream, every level
- Lot states
- Available · consumed · quarantined · rejected · expired · blocked
- Corrections
- Credit lines; the original is never edited
Frequently asked questions.
Planning a recall drill? An engineer can walk through one with you on the sample plant.
Book a callIf the ERP supplies one, it is used. Otherwise a mask applies (per article, then per site, then globally), with a preview before it is saved. Numbers are unique by construction and kept short enough for a GS1-128 label.
Yes, any scanner in keyboard mode, with no driver to install. GS1 codes fill in the lot, quantity and expiry. A scanner configured without the FNC1 separator is detected and flagged rather than guessed around.
The recalled lot is blocked and its descendants are quarantined at every level. A lot in production goes into logical quarantine and the run continues, with a critical alert to management; no line stops on its own.
No. Your ERP or warehouse system decides whether received material is released. VZIAM MES receives the lot with its state and enforces that state when the lot is consumed.
Yes, by a supervisor, with a reason. The new lot inherits the parent’s state and supplier identity; the quantity is moved, not duplicated, and a split never releases a blocked lot.
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.