MES Integration Series · Part 2
Production Event and Traceability Workflow
How do events from the machines turn into complete traceability?
A traceable product has a record for everything that happened to it: which work order, which station, which settings, which measured values, which operator, which material lots. This page shows the events of one part, the status changes it can go through, and how genealogy limits a recall to what is really affected. The data and numbers are examples.
Each station sends its key events to the MES in real time or near real time. The six steps below are the path of one part, from the work order to the confirmation.
| Event | Time | Serial | Station | Parameter | Result |
|---|
Each row is one production event: what happened, when, to which part, at which station, with which measured value and result. Pick a station that should fail and run the part through: the event stream shows where it stopped and the status changes to Failed. The values are generated examples.
A part is always in exactly one status, and only some changes are allowed. Use the buttons: the MES offers only the moves that make sense, and it keeps the log.
A battery pack contains modules and each module contains cells. With genealogy, each cell is linked to its module and pack by serial number, so a suspect cell lot leads straight to the packs that contain it. Without it, you would have to treat the whole run as suspect. The lot size and the lot number are yours to set; the cell use is a simple sequence for the demo.
More fields mean more questions can be answered later, and more data to store and send. Tick the fields and see the trade-off.
| Stage | Tools shown in the case | What they do here |
|---|
The tools are examples, not recommendations. Choose by what your team owns and what your machines and PLCs support.
The examples are simplified. Traceability and recall rules depend on your product, your customers and the regulations that apply to you.