Choosing a Traceability Granularity for Small-Batch Production

Piece-level traceability gets treated as the ambition and batch-level as the compromise, and in small-batch high-mix production that is backwards. Tracing to the individual item means every item must be individually identifiable, which means a serial number, a barcode or an RFID tag, plus the readers, the labelling operation and the discipline to keep it accurate. That is real money, and in a plant running forty orders a week it frequently answers a question nobody was going to ask. The right granularity is the one that serves the decisions you actually make, and identifying those decisions first is what makes the level obvious.

Three levels and the decisions each serves

Work-order level answers the question management actually asks: did this order run correctly. Batch level answers the question process engineering asks: where did the drift start and what did it correlate with. Piece level answers the question that arises in a dispute with one customer about one item. All three are legitimate; the question is which arise in your plant often enough to justify their cost. In a great deal of small-batch production, work-order level covers accountability, batch level covers improvement, and piece level would serve a dispute that is handled by other means — usually by rework or by replacement, whose cost is lower than the tracing infrastructure. The exception is where the product itself demands piece-level tracing for regulatory or safety reasons, and there the level is not a choice.

The cost of getting it wrong in each direction

• Too coarse: a quality issue surfaces, the batch is large, and the whole batch has to be held or recalled. The saving on infrastructure is repaid in a single event, which is the case that justifies going a level finer.
• Too fine: every item needs labelling and reading, adding time to every station, plus maintenance on readers and the ongoing labour of keeping the data clean. This cost is paid daily and is the one more often underestimated.
• Inferred tracking: where items have no identifier and tracing is reconstructed from the time sequence, a single missed frame or double trigger shifts every later record, and the shifted record looks entirely credible. This is worse than a coarser level chosen deliberately.
• Level mismatch across processes: some stations at piece level, others at order level, so that joining the two produces records that do not line up. Agreeing the level across the whole process before building is essential.

Remember the time dimension

Granularity is two-dimensional. How finely items are distinguished is one axis; how long records are kept is the other. A system that traces to the piece but keeps records for a month is effectively a work-order system for anything older. Retention should follow the window in which a question could realistically be asked, which usually means the product's warranty or traceability requirement. Setting the two together avoids the familiar outcome of building expensive piece-level tracing and then expiring the records long before they would ever be needed. The retention side is examined in network and data security, and the fields that carry the identifiers in MES write-back field design.