Just-in-sequence — RTLS that prevents mis-builds.
JIS line-side sequencing is the difference between a body-shop that holds the takt time and one that drops 2–3 OEE points to mis-build rework. UWB on the line plus Passive RFID at parts portals delivers the visibility; the integration into MES delivers the prevention.
What JIS actually requires.
Parts arrive at the right station, in the right sequence, at the right time — not before, not after, not in the wrong order. Mis-sequence triggers mis-build; mis-build triggers rework or scrap.
Real-time visibility of part position from supplier dock through line-side delivery through fitment confirmation. The data flow is continuous; the system that delivers it cannot drop events.
Integration into MES (SAP MII, Rockwell FactoryTalk, Siemens Opcenter, in-house) so the sequence event triggers the line workflow — andon, station prep, downstream handoff.
Traceability to VIN for IATF 16949 audit — every part, every fitment, every torque event tied to the vehicle ID.
The technology stack we deploy.
UWB on the line for live parts position with 30 cm accuracy. Sewio, Ubisense, Pozyx all credible depending on procurement constraints.
Passive RFID at supplier-dock portal, line-side delivery point and station-level confirmation reads.
Tag-and-bin on parts containers with item-level RFID inside for individual part traceability.
Integration: MES event consumption, sequence rule engine, andon trigger on mis-sequence event.
Where JIS programmes succeed or fail.
Supplier-side integration: parts have to arrive tagged. Without supplier compliance, the system sees gaps. Programme-led supplier onboarding is usually the slow stage.
Line-side delivery point design: RFID portal placement and tag-orientation against the actual stillage geometry decides read accuracy.
MES sequence rule engine: defining what counts as out-of-sequence, what triggers andon, what the operator workflow looks like. Most programmes underestimate this scope.
VIN-tied traceability: tying every part event to VIN through MES is the IATF 16949 audit win. Implementations that skip this fail the audit-grade test.
Cost and timeline.
UWB anchors: 40–60 typical for a 5,000 m² line; €12,000–€18,000 hardware, €40,000–€90,000 install.
Passive RFID at portals: 8–15 portal locations typical; €15,000–€25,000 hardware, €15,000–€30,000 install.
Integration into MES: 20–40% of programme cost; this is where the rule engine, andon and workflow design lives.
Typical timeline: 6–12 months from scoping to operational, longer if supplier onboarding is in scope.
Who sells into JIS — and what sequence programmes get wrong.
Automotive Tier-1 and OEM programmes meet MES vendors, Passive RFID portal specialists (Impinj/Zebra-class fixed readers via SIs), UWB RTLS vendors for in-plant WIP, and AGV/AMR fleets that promise sequence integrity if the robots are bought. Each solves a slice: portals confirm rack presence at the dock; UWB tracks dollies in flight; MES owns the sequence list; AMRs move the metal. Nobody automatically owns the end-to-end “right part, right slot, right minute” evidence when a carrier is late or a tag dies mid-route.
What programmes get wrong: choosing UWB everywhere when dock and line-side chokepoints only need Passive RFID events; buying AMR orchestration without a locating layer that can prove sequence before the robot arrives; and measuring read-rate instead of sequence integrity and line stop minutes.
TRACIO designs the hybrid stack and integration contract vendor-neutrally — including AGV/AMR advisory and integration only (we sell no robots). Acceptance is sequence KPIs in the MES, not a radio demo. Related: automotive WIP tracking.
What good JIS locating proves before the line calls for the rack.
Just-in-sequence fails in public: the wrong rack at the wrong minute stops the line. Locating must prove sequence integrity early enough to intervene — at the supplier dock, the plant gate, the supermarket buffer and the line-side slot — not only after the andon is red. Passive RFID portals excel at those chokepoints; UWB adds continuous visibility for dollies and tugs moving between them when dwell and misroute risk justify the density.
MES owns the sequence list; locating must emit validated presence and zone events the MES can trust without a second manual scan. Carrier and rack identity must survive weather, wash and metal. AGV/AMR fleets can execute moves but should consume the same truth layer rather than inventing a private map — TRACIO advises and integrates robots; we do not sell them.
Programmes that skip live-shift RF survey discover too late that simultaneous dock doors and steel cages destroy the lab read-rate. Buffer health KPIs (starve risk, excess dwell, wrong-slot rate) belong on the same dashboard as read-rate. Supplier scorecards improve when portal events are shared upstream with clear dispute rules.
Acceptance: sequence integrity over a multi-day production window, minutes of line stop attributable to locate/identity failure trending to zero, and a rehearsed exception path when a tag dies mid-route.
Who sells into JIS — and what sequence programmes get wrong.
Automotive Tier-1 and OEM programmes meet MES vendors, Passive RFID portal specialists (Impinj/Zebra-class fixed readers via SIs), UWB RTLS vendors for in-plant WIP, and AGV/AMR fleets that promise sequence integrity if the robots are bought. Each solves a slice: portals confirm rack presence at the dock; UWB tracks dollies in flight; MES owns the sequence list; AMRs move the metal. Nobody automatically owns the end-to-end “right part, right slot, right minute” evidence when a carrier is late or a tag dies mid-route.
What programmes get wrong: choosing UWB everywhere when dock and line-side chokepoints only need Passive RFID events; buying AMR orchestration without a locating layer that can prove sequence before the robot arrives; and measuring read-rate instead of sequence integrity and line stop minutes.
TRACIO designs the hybrid stack and integration contract vendor-neutrally — including AGV/AMR advisory and integration only (we sell no robots). Acceptance is sequence KPIs in the MES, not a radio demo. Related: automotive WIP tracking.
What good JIS locating proves before the line calls for the rack.
Just-in-sequence fails in public: the wrong rack at the wrong minute stops the line. Locating must prove sequence integrity early enough to intervene — at the supplier dock, the plant gate, the supermarket buffer and the line-side slot — not only after the andon is red. Passive RFID portals excel at those chokepoints; UWB adds continuous visibility for dollies and tugs moving between them when dwell and misroute risk justify the density.
MES owns the sequence list; locating must emit validated presence and zone events the MES can trust without a second manual scan. Carrier and rack identity must survive weather, wash and metal. AGV/AMR fleets can execute moves but should consume the same truth layer rather than inventing a private map — TRACIO advises and integrates robots; we do not sell them.
Programmes that skip live-shift RF survey discover too late that simultaneous dock doors and steel cages destroy the lab read-rate. Buffer health KPIs (starve risk, excess dwell, wrong-slot rate) belong on the same dashboard as read-rate. Supplier scorecards improve when portal events are shared upstream with clear dispute rules.
Acceptance: sequence integrity over a multi-day production window, minutes of line stop attributable to locate/identity failure trending to zero, and a rehearsed exception path when a tag dies mid-route.
Frequently asked questions
Why JIS rather than just JIT?
Just-in-time delivers parts when needed; just-in-sequence delivers them in the right order for the line. JIS is the harder problem and the higher value. UWB-tracked JIS is what holds takt time at scale.
Can we do JIS with just RFID, or do we need UWB?
RFID alone is sufficient for presence at delivery points but not for live in-flight position. Modern JIS programmes use the hybrid stack — UWB for line position, RFID at portals and stations.
What is the typical mis-build rate reduction?
Baseline 0.4–0.8% of vehicles; production-grade JIS RTLS drives this to under 0.1%. The labour and rework saving is meaningful but the IATF 16949 audit-grade traceability is usually the primary commercial driver.
How does this integrate with our MES?
Event consumption via the MES API. SAP MII, Rockwell FactoryTalk, Siemens Opcenter and in-house MES platforms all well-supported. The sequence rule engine sits in the integration layer.
Last updated: