Do you need an MES to get traceability?
No. Producing a build record requires three things: an identity for the unit, a routing the work actually follows, and capture at the point of work. A manufacturing execution system provides all three. It is also the heaviest way to get them, because it asks you to model the enterprise before the first record exists.
By Javier Ortiz
What traceability actually requires
Three things, and only three. Everything else in a traceability project is implementation detail around them.
An identity for the unit
A serial, a lot, a job number, something that names the specific thing being built. Without it every record you capture belongs to a shift or a shop order rather than to a part, and no amount of data will answer a question about one unit.
Usually already exists. It is on the traveler, the label, the ERP work order, or the barcode on the tote.
A routing the work actually follows
The sequence of operations the unit passes through, with the gates that stop it. This is what makes a record structured rather than a pile of readings, because every captured value has a known place in a known order.
Usually already exists on paper. The routing sheet, the traveler, the process map on the whiteboard.
Capture at the point of work
The value recorded where and when the work happened, bound to both of the above. This is the one that is normally missing, and it is the only one of the three that requires software rather than paper.
This is the gap. Everything else in the plant is usually already in place.
Two ways to get all three
Both routes end in the same place. They differ entirely in what the plant has to settle before anything works at all.
Top down
Start with the system
Model the plant, the equipment hierarchy, the material definitions and the process segments. Configure the routings. Integrate the ERP. Then the first record exists.
It produces a complete and coherent result, and for a plant that needs enterprise scheduling and full material management it is the right answer. It also means the first useful output arrives after most of the budget has been spent, which is why the category average runs twelve to eighteen months.
Bottom up
Start with the station
The work instruction already carries the routing, because it is the sequence of steps. It already carries the revision, because that is what the operator is being shown. It is already at the point of work, because that is the only place it is ever displayed.
Two of the three requirements come free. Adding the unit identity turns the thing the operator reads into the thing that writes the record, and one line can be producing real records in weeks.
These are not competing philosophies. They are different entry points into the same problem, and the second one does not prevent the first. A plant that starts at the station and later needs enterprise scheduling adds it underneath what is already running.
When you do want the heavier system
Starting at the station is the right first move for most plants in the 30 to 150 employee range. It is not the right answer for everything, and it is worth being specific about where it stops.
If you need finite capacity scheduling across multiple lines with material availability driving the sequence, that is a scheduling engine, not a work instruction. If you need full work-in-process material management with automatic backflush against a multi-level bill of materials, that is an execution system doing inventory. If you are in regulated pharmaceutical or medical device production and need 21 CFR Part 11 controls with a validation package, that is a different class of product with a different assurance model, and you should ask any vendor including us to show you the evidence rather than the claim.
What is worth separating is the record from the scheduling. Plants routinely buy a full execution system because they need traceability, and end up with a large project whose most-used feature is a screen the operators avoid. If traceability is the actual requirement, it is worth knowing that it is the cheapest of the things that system does.
Common questions
Can you have traceability without an MES?
Yes. Traceability requires unit identity, a routing the work follows, and capture at the point of work. A manufacturing execution system provides all three, but so does a digital work instruction running at the station, because the instruction already carries the routing and the revision and is already displayed where the work happens. Adding the unit identity is what turns it into a record.
Is a spreadsheet enough for traceability?
It can satisfy an auditor and many plants pass audits on spreadsheets today. What it cannot do is prove capture at the point of work. A spreadsheet filled in at the end of shift is a recollection of measurements rather than a record of them, and it cannot demonstrate which revision of the instruction was in front of the operator at the moment the work was done. It also makes forward trace expensive, because finding every unit that received a suspect lot means reading rather than querying.
What does IATF 16949 actually require for traceability?
Clause 8.5.2.1 requires the organization to identify the status of product with respect to monitoring and measurement throughout production, and to have a documented process for traceability that meets customer, statutory and regulatory requirements. It defines what the traceability has to achieve rather than what software you use. Most customer-specific requirements go further than the standard itself, which is why the practical requirement usually comes from the OEM purchase agreement rather than from the standard.
We already have an MES. Do we still need work instructions?
The MES holds the record and usually holds it well. What it often does not do is give the operator a usable interface at the moment of work, which is why plants with a fully deployed MES still run paper instructions in binders next to the terminal. Connecting the two means the record keeps living in the system of record while the operator gets a screen designed for the person wearing gloves.
What is the fastest way to start?
One line, one process, one set of instructions with the unit identity attached. It produces a real record set for a real product within weeks, which is enough to show a customer or an auditor and enough to find out what your actual requirements are. Plants that start by specifying traceability for the whole site tend to spend the first six months on the specification.
Traceability is not a system you buy. It is a property a record has, and the record gets written wherever the work is already being done.