Material & Part Traceability Software for Regulated Manufacturing
A material and metal part traceability solution: trace any raw lot forward to the finished units it reached, and any unit back to every lot inside it, from one append-only record. Barcode and RFID capture, with profiles for IATF 16949, AS9100D, 21 CFR Part 11, the EU MDR and FSMA 204.
Schematic
Material genealogy, both directions
One chain of scans, read forward from a suspect lot and backward from a failed unit.
Material and part traceability is decided at capture, not at query
MileSoft Material Traceability records how material actually moves through a plant: which raw lot was consumed by which sub-assembly, which sub-assembly went into which finished unit, and which unit shipped to which customer on which date. Those links are written at the moment each transformation happens, so a containment question walks a record that already exists instead of reconstructing one from transaction logs under pressure.
Capture is hardware-agnostic. Barcode and RFID are usually mixed on the same line, and the carrier matters less than the identifier scheme: as long as each lot and unit carries a unique identifier, the record closes the same way whether it was scanned or read. Events follow the EPCIS model standardised as ISO/IEC 19987, and the history is append-only, so a corrected mis-scan supersedes the original rather than overwriting it.
One record serves several regulatory regimes at once. IATF 16949 attaches quality data at each tier; AS9100D holds the supplier certificate on the raw-lot node; 21 CFR Part 11 relies on the append-only audit trail; the EU Medical Device Regulation carries instance identity to the finished unit; and FSMA 204 uses the tier events themselves. A manufacturer in two regulated sectors needs one traceability record with two field profiles, not two systems.
Material traceability
Why a lot number is not traceability
Almost every manufacturer records lot numbers. Very few can compute a containment set.
A lot number on a receiving document is a label on a node. Traceability needs edges: this lot was consumed by that sub-assembly, that sub-assembly went into this unit, this unit shipped to that customer on that date. A node without its edges cannot be traversed — and edges cannot be inferred afterwards from timestamps and part numbers without assuming the very consumption order that was never recorded.
The practical test is not whether lot numbers are stored. It is whether, given one lot number, the system returns finished units — rather than a list of documents that mention that lot.
It follows that the binding constraint is capture, not query. Every traceability system can traverse a graph; the differences that decide whether a plant can answer a recall are upstream, in whether the links exist. The buying question is how many events per shift the floor must contribute, how many of those are automatic, and what happens to the record when one is missed. A system needing a dozen manual scans per unit will have gaps; one deriving most of them from equipment will not.
That also moves the real cost of deployment. The expensive part is not configuration — it is instrumenting the consumption points, which is a floor-layout and process question software cannot answer on its own.
What a gap costs
A 90% complete genealogy does not give a 90% good answer
It fails all at once, at the first broken tier.
It is tempting to treat completeness as a percentage. The failure is structural instead: below the earliest tier where a link is missing, a containment query has nothing to follow, so every unit in that tier becomes a candidate and must be contained. The computed set equals the true one only if every tier along the suspect path is complete. Otherwise it is the whole population of the first broken tier.
What genealogy is worth in a particular recall is therefore computable, not a marketing contrast. Call it the blast-radius ratio:
β = units shipped in the exposure window ÷ units the suspect lot actually reached
The exposure window runs from the earliest to the latest possible use of the suspect lot — the envelope a plant must contain when it cannot trace. Multiply the difference between the two sets by the fully loaded cost of containing, recovering and replacing one unit, and that is the cost the genealogy avoided.
β is a property of the plant, not of the incident. It rises with production rate, with lot size relative to consumption rate, and with the delay between consumption and the defect being noticed. You can compute your own today, from shipping records and a bill of materials, without deploying anything — which is a better way to size this investment than any vendor’s figure, including ours.
Honest resolution
The resolution your process allows, before any software is chosen
Where lots are physically mixed, traceability precision has a floor.
A hopper fed from two lots produces parts that belong to both. A paint batch, a bulk fastener bin and a resin silo behave the same way. At each mixing point, the units implicated by a suspect lot are at least the population drawn from that vessel between the lot entering it and the vessel being emptied.
So improving traceability is often a process change rather than a software change: emptying a hopper between lots, reducing vessel size, or recording a purge event all tighten it directly. A system that captures mixing events makes that bound visible. One that does not lets a plant believe its resolution is finer than the physics allows.
A supplier claiming unit-level traceability through a bulk feed is claiming something the process does not support. The honest claim is lot-to-vessel-population traceability.
Regulatory profiles
One genealogy, five regulatory regimes
The sector standards differ in obligation while agreeing almost entirely in structure.
| Regime | What it adds | Where it lands in the model |
|---|---|---|
| IATF 16949 | Traceability as evidence of process control | Backward closure with quality data attached at each tier |
| AS9100D | Configuration management, counterfeit-part prevention | Supplier certificate held on the raw-lot node and traversed with it |
| 21 CFR Part 11 | Secure, computer-generated, tamper-evident audit trail | Append-only event history; superseding events rather than edits |
| EU 2017/745 (MDR) | Unique device identifier, economic-operator traceability | Instance-level identity at the finished-unit tier; shipment tier extended past the first consignee |
| 21 CFR Part 1, Subpart S | Critical tracking events, key data elements, 24-hour sortable record | The tier events themselves, with a mandated field set and response-time obligation |
The practical consequence: a manufacturer serving two regulated sectors does not need two traceability systems. It needs one record, two field profiles and two report formats. Events follow the EPCIS model standardised as ISO/IEC 19987 — what object, when, where, and under which business step — with ISO/IEC 19988 fixing the permitted vocabulary, so packing at one site and packing at another are the same recorded fact.
Evaluating a traceability system
Eight questions to put to any traceability system
Each separates a traceability system from a lot-number field, and each is answerable on a running line rather than a specification sheet — including ours.
| # | Dimension | Ask the vendor to demonstrate |
|---|---|---|
| D1 | Edges, not labels | Given one raw lot number, does the system return finished units — or documents mentioning that lot? |
| D2 | Both closures | Can it answer forward containment and backward genealogy from the same structure? |
| D3 | Instance identity | Does the finished tier carry a serial or vehicle identification number, or only a part number? |
| D4 | Append-only history | Correct a mis-scanned lot. Is the original still visible, superseded rather than overwritten? |
| D5 | Commingling visible | Does a mixing point record an event, so that resolution is computed rather than assumed? |
| D6 | Gap detection | Break one link deliberately. Does the system report a gap, or silently return a smaller answer? |
| D7 | As-of queries | Ask for the disposition of a lot as it stood ninety days ago. Does it answer? |
| D8 | Time to answer | Run a containment query on live production data, not a demonstration dataset. How long does it take? |
D6 is the dimension buyers almost never test, and the one that decides whether a recall answer can be trusted. A system that returns a confident wrong set is more dangerous than one that returns nothing.
Standards referenced: ISO/IEC 19987 (EPCIS), ISO/IEC 19988 (CBV), ISO 22005, IATF 16949, AS9100D, 21 CFR Part 11, Regulation (EU) 2017/745, 21 CFR Part 1 Subpart S. The derivations, including worked examples of the blast-radius ratio, are in the material traceability method paper. For a plain-language walk through forward and backward genealogy, see end-to-end lot genealogy.
Features
Key Features
Built-in capabilities that set our software apart
Forward and backward closure
containment and genealogy answered from the same record
Hardware-agnostic capture
barcode and RFID, mixed on the same line
Append-only history
corrections supersede the original event instead of overwriting it
Gap detection
a missing link is reported, never silently returned as a smaller answer
Supplier certificates on the raw lot
held on the raw-lot node and traversed with the genealogy
Benefits
Key Benefits
What your team gains from adopting our platform
Testimonials
What Our Clients Say
Trusted by industry leaders across manufacturing, HVAC, and logistics.
"The software features, such as real-time monitoring and alerts, have proved invaluable in optimizing machine operations. MileSoft team's professionalism, technical expertise, and dedication to meeting our requirements have been impressive."
FAQ
Material & Part Traceability Software — FAQs
Answers to the most common questions about this product. Need more? Book a demo or reach out via Contact.
What does material traceability actually give us?
Why do automotive suppliers need it?
How fast does a containment query run?
Which standards does it support?
Does it work with barcode and RFID both?
Do you provide metal part traceability?
What is end-to-end lot genealogy?
Explore More
Related Products
Complementary tools teams often pair with this solution
Related Reading
Go deeper
Explore the long-form story behind this product.
The Blast Radius Problem: Genealogy Closure, Containment Queries, and Why a Lot Number Is Not Traceability
Architecture, Computational Methods, and Reported Outcomes from MileSoft Material Traceability
Read the paperRead the full Material & Part Traceability Software for Regulated Manufacturing deep-dive
Read articleSee how MileSoft delivers in Industry 4.0
Read case studySee your savings in under a minute
Estimate the time and cost this tool could give back — free, instant, no sign-up.
Test a traceability system with one of your own lot numbers
Bring a raw lot from a real incident. We will show what it returns, where your consumption points would need capture, and where mixing limits the resolution any system can reach.