Just-in-sequence traceability that lifted OEE by 9 points.
A German OEM body-shop was losing time to sequence errors and had no audit-grade genealogy for IATF 16949.
Case studies and programme figures on this page are composite worked examples — patterns from comparable deployments, not attributed results for a named client. Named references are available under NDA when you engage.
What they were up against.
Sequence errors caused rework
Mis-sequenced work drove rework and unplanned line stoppages.
No audit-grade genealogy
IATF 16949 traceability could not be reconstructed quickly for audit.
Manual tool control
Torque-tool control was manual and not bound to the vehicle.
Composite worked example — figures are ranges from comparable programmes, not attributed named-client results. Named references available under NDA. We model your own numbers when you engage.
Vendor-neutral, tied to a named KPI.
We combined UWB tool control with Passive RFID just-in-sequence traceability, integrated to Siemens Opcenter MES, binding every torque event to the VIN.
What we delivered.
- Just-in-sequence WIP traceability at IATF 16949 audit grade
- UWB-tagged torque tools bound to the VIN
- Siemens Opcenter MES integration
The typical range for a programme of this shape.
The stack behind it
Baseline, method, period — and what we excluded.
These pages are composite worked examples, not named-client scorecards. Figures are ranges from comparable RTLS/RFID programmes and published industry sources where noted.
- Baseline: JIS telegrams trusted; mis-builds found at fit.
- Method: RFID/RTLS confirmation at dock and lineside supermarket vs MES sequence; mis-build and stoppage counts.
- Period: Pilot supermarket and two docks, then plant standard.
- Excluded: MES sequence quality without physical confirmation.
Programme pattern for this vertical
JIS programmes verify sequence integrity from supplier through yard to station consume. UHF RFID portals plus selective RTLS on tuggers/AGVs is a common pattern under IATF and OEM CSRs.
Genealogy queries and containment speed are the design north star.
Outcomes to expect — and how they are earned
Outcomes: sequence accuracy in the high 90s when process discipline matches technology; faster containment; fewer line stops from wrong-kit.
Lessons from comparable programmes
Lessons: portal physics in metal yards; MES as SOR; CSR mapping at gate 1; do not skip 2D fallback.
Deeper problem framing
Wrong-sequence kits stop lines. Containment without genealogy freezes excess inventory. CSR pressure exceeds batch-level comfort.
Approach
Portal verification at handoffs; MES SOR; CSR map; 2D fallback; tugger/AGV visibility where yards blur truth.
Outcomes and measurement
Sequence accuracy, stoppage minutes, containment elapsed time.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Implementation sequence and change management
Map CSR strictest requirements; instrument supplier-to-station handoffs; MES as SOR; prove containment query in pilot. Include yard metal in RF design.
KPIs: sequence accuracy, line-stop minutes, containment elapsed time. Keep 2D fallback. Challenge 'IATF compliant' logos without genealogy demo on your part numbers.
Buyer checklist, vendor challenges and engagement shape
For JIS, make containment query speed and CSR mapping gate criteria equal to portal read rate.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Programme pattern for this vertical
JIS programmes verify sequence integrity from supplier through yard to station consume. UHF RFID portals plus selective RTLS on tuggers/AGVs is a common pattern under IATF and OEM CSRs.
Genealogy queries and containment speed are the design north star.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Implementation sequence and change management
Map CSR strictest requirements; instrument supplier-to-station handoffs; MES as SOR; prove containment query in pilot. Include yard metal in RF design.
KPIs: sequence accuracy, line-stop minutes, containment elapsed time. Keep 2D fallback. Challenge 'IATF compliant' logos without genealogy demo on your part numbers.
Buyer checklist, vendor challenges and engagement shape
For JIS, make containment query speed and CSR mapping gate criteria equal to portal read rate.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Last updated:
Line-side truth
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
JIS / WIP that procurement can audit
Start from the sequence problem and the stations that break first.
Score radios against the plant
Metal, conveyors and existing MES integrations beat brochure accuracy claims.
Feed the systems the plant already runs
Position and identity events into MES/WMS — not a second glass the line ignores.
Measurement
Baseline: sequence integrity, lineside stockouts, and expedite counts on the target line. Pilot: one model/line with identity + location events vs the JIS / sequencing system. Steady-state: sequence error rate, lineside replenishment exceptions, and expedite labour. KPI bands are typical for this programme shape.