Two Batches, One Assembly Order

Consider an illustrative manufacturing job: a small company builds 40 control panels, each containing one circuit board, using boards from two incoming batches. Twenty-four boards come from batch A and sixteen from batch B. The purchasing system shows both deliveries. The assembly record shows 40 finished panels.

Then the board supplier asks which panels received batch B.

In this example, the invoices, packing slips, and assembly record contain aggregate quantities but no mapping from boards to individual panels. Those documents could carry that mapping; these do not. Identifying the sixteen panels requires the connection between each finished unit and the board actually installed in it.

This is a useful place to begin a traceability discussion because the answer has a practical consequence. In this example, a reliable connection would let the company identify a specific group for further investigation. Without it, the uncertainty covers more of the production run.

Preserve the relationship at assembly

NIST’s manufacturing traceability report, finalized in September 2026, describes an approach for connecting product histories across organizations that use different systems. The September announcement emphasizes exchanging and verifying information while allowing existing industry standards to remain in use. This guidance for designing traceability does not prescribe purchasing a particular platform. NIST announcement.

For our example, the first design choice is the level of detail needed. If the customer needs an answer for individual panels, a record saying that both batches were used somewhere in the order will be insufficient. The local production record needs to preserve which board went into which panel, or a sufficiently precise grouping that supports the customer’s question.

The supplier inquiry and internal panel mapping are CTS’s operational example. NIST focuses on traceability between organizations; section 4.3.2 supports backward links to preceding events and deliberately avoids forward tracking. The framework does not deliver the downstream panel lookup imagined here. The manufacturer still has to decide how to capture and query its internal work accurately.

A practical trial could use one completed order. Have production and quality staff reconstruct the component-to-panel relationships from the records they actually retain. Notice where they rely on memory, assumptions about installation order, or labels that no longer accompany the part. Those are specific capture problems to resolve before expanding the trial.

Ask for a bounded supplier record

Now extend the example upstream. The supplier may be able to identify the shipment and manufacturing batch while keeping its process settings private. The customer needs to decide which additional claim it wants supported: the batch’s origin, a particular test result, or conformity with an agreed specification.

Those requests call for different evidence. A delivery record establishes a different fact from a test report. Before asking for another document, state what it must establish and which components it covers.

NIST’s report allows for selective disclosure and alternative evidence, including digitized paper records. It also distinguishes links to preceding supply-chain events from supporting material such as test reports. The buyer must judge whether that evidence provides sufficient assurance for the item’s risk. NIST IR 8536, sections 3.4 and 4.2.3.

For the panel maker, a sensible pilot request might identify batch B, the supplier’s shipment reference, and the specific test documentation needed for the investigation. Requesting the supplier’s entire production database would add a much larger disclosure question without necessarily resolving this one.

Leave the gaps visible

Suppose the supplier’s older test report cannot be retrieved. Our editorial recommendation is to record that limitation alongside the batch relationship. A missing report and a report showing an unacceptable result are different findings; the response should reflect what is actually known.

NIST explicitly recommends distinguishing gaps such as unknown, withheld, and unreachable information. Its scope also matters: the core framework follows products through acquisition or initial deployment, with broader later-life applications reserved for further work. It should not be presented as a complete recall-management system. NIST IR 8536, sections 1.3 and 3.5.

The pilot can end with a concrete result: a list of panels associated with batch B, the evidence supporting that list, and any units whose component history remains uncertain. That gives the quality team a bounded set of facts to assess with the supplier. It also shows exactly which information the next assembly order needs to retain.