IATF 16949 & RTLS — automotive traceability.
Automotive manufacturers and Tier 1 suppliers are scored against IATF 16949 plus their OEM customers' Customer Specific Requirements (CSRs).
Traceability — lot, part, process — is central, and RTLS / RFID is the layer that delivers it automatically. This is the operator-level summary.
What IATF 16949 requires from traceability
Clause 8.5.2 (Identification and Traceability) requires that organisations identify product status throughout production, service provision and post-delivery, and that traceability is maintained throughout (including the storage of relevant evidence).
For automotive, this means lot, batch and part-level genealogy captured automatically and retained for the documented period (often 10–15 years). RFID and RTLS are the dominant technologies for capturing this without operator overhead.
Customer-Specific Requirements (CSRs)
Each OEM publishes additional CSRs that extend IATF 16949: Ford Q1, GM BIQS, Stellantis MOPS, VW Formel-Q, Toyota TPS-adjacent requirements, BMW VDA standards, and so on. CSRs typically tighten traceability granularity (e.g.
critical-feature traceability at the individual-part level rather than the batch), introduce specific data retention, and require named process-event capture. We map your CSRs to the RTLS architecture at gate 1 so the deployment satisfies the strictest customer in your portfolio.
Just-in-Sequence and the verification problem
JIS supply requires that parts arrive at the line in the exact build order.
Verification — proving that the part attached to vehicle VIN-N is the part assigned to it — is enforced by RFID or 2D-code reads at every handoff: supplier-sequence assembly, sequenced racking, dispatch, delivery, line-side put-away, build station.
The trace must be tamper-evident and time-stamped. See our JIS solution page for the architecture pattern.
Audit evidence — what the customer auditor will ask
An IATF 16949 surveillance audit or an OEM customer audit on traceability typically requests: a documented traceability map (which records prove which clause),
evidence of unbroken trace for a sample of in-service vehicles, change-control history for the traceability system, and evidence of effectiveness (recall scoping demonstrations).
We assemble this as part of stage 3 (Deploy) of the TRACIO Programme Method.
Frequently asked questions
RFID, 2D code or both for parts traceability?
Usually both. 2D codes provide a human-readable verification path; RFID provides automatic capture at scale without line-of-sight. Most Tier 1 plants use 2D for piece-part identity and RFID for container or sequence-level tracking.
How long must traceability records be retained?
IATF 16949 requires retention for the documented period — typically aligned to the vehicle service life plus regulatory requirements. 10–15 years is common; some OEM CSRs require longer for safety-critical features.
Can existing systems handle the data volume?
Usually, with the right architecture. We model expected event volumes at gate 1 — typical Tier 1 plants generate 10-100 million traceability events per year.
Streaming architectures (Kafka, MQTT brokers) handle this comfortably; legacy relational-only stacks may need restructuring.
How is the recall-scoping use case demonstrated?
By running a recall-simulation exercise on the live traceability data, scoping a hypothetical defective batch to the exact list of affected vehicles, and timing the response. OEM auditors increasingly ask for this drill. We script it as a gate-3 deliverable.
Last updated: