RTLS the COO can run.
Throughput, accuracy and exception labour on the KPIs you already report. Technology last; the operating problem first.
Programmes fail when ops never owns the exception queue.
KPI owner
If the floor does not act on alerts, you bought wallpaper.
Peak design
Average-day maps hide the hour that kills OTIF.
Process before radio
Fix the ritual — then choose UWB, RFID or hybrid.
Which KPIs move first, and when
On a properly-scoped RTLS programme, the first KPIs to move are inventory accuracy (often within 60–90 days of go-live) and search time per asset (immediate).
Throughput and OEE typically lift over 6–12 months as the location data feeds back into scheduling, slotting and process change.
Safety KPIs (near-miss frequency, time-to-muster) move within weeks once the worn devices are issued. Customer-facing KPIs (perfect-order rate, on-time-in-full) follow inventory accuracy by 3–6 months.
Deployment risk, in your language
Every RTLS deployment has three failure modes: a pilot that didn't reflect production load (most common), an integration that nobody owned past go-live, and an architecture sized to the catalogue not your operation.
The mitigation in each case is structural, not technical: a pilot designed to break the system early, a named operational owner before go-live, and an architecture chosen on RF survey evidence. Our methodology bakes these in as gate criteria.
Integration is where it lives or dies
Location data that doesn't reach your MES, WMS, ERP, CMMS or EMR is decoration. The first integration question we ask any client is: which decisions, made by which people, currently lack the location signal? The answer dictates the integration scope.
We do this work directly — see build & integration — or in partnership with your incumbent SI on a vendor-neutral basis.
Change management is half the budget
Operators ignore systems that don't help them. The single highest-use change-management move is a 30-minute supervisor briefing where the system is positioned as ‘this tells you where things are, so your team stops hunting’ — not as productivity surveillance.
Done right, adoption is high within weeks. Done wrong, the system collects dust and an expensive write-off appears on next year's audit.
Related reading.
“We’d stalled twice on WIP tracking before TRACIO. They insisted the pilot run at full production load, not a demo lane — that’s why it held up. WIP accuracy settled at 99.2% and we were still holding +6 OEE points six months after go-live.”Operations Technology Director
Tier-1 automotive supplier · DACH
Buying criteria operations leaders use for locating
COOs sponsor locating programmes to move throughput, accuracy and exception handling — not to own another dashboard. Criteria that separate useful programmes from science projects:
- KPI ownership on the floor — OEE, cycle time, WIP accuracy, dock dwell or service level owned by ops after go-live.
- Exception workflow first — who acts when a tote, tool or trailer is late, and in which system?
- Production-load proof — pilot on a live shift with written go/no-go, not a quiet demo lane.
- Integration into run-the-business tools — MES, WMS, TMS or CMMS events, not a parallel map.
Hardware vendors sell coverage maps. SIs sell install capacity. Consultancies sell operating-model decks. Ops should buy a locating design that changes the tier meeting within one quarter of pilot.
Operational failure modes in RTLS and RFID programmes
- WIP or yard maps that supervisors stop opening after week two.
- Tags that add more than a few seconds of friction per shift — operators bypass them.
- RF design that works at commissioning and fails under full metal, traffic and shift noise.
- Night-shift and contractor processes never designed — data collapses after 22:00.
- Alerts without owners — noise that trains people to ignore the system.
Questions COOs should ask vendors and integrators
- Which bottleneck cell or dock will show a measurable KPI move in the pilot window?
- How do exceptions land in our MES/WMS — and who owns false positives?
- What is the tagging ritual for operators, and have you timed it on a live shift?
- Show a reference where supervisors, not IT, run the daily huddle from locating data.
- What is the rollback if MES write-paths misbehave during go-live?
How TRACIO differs for the COO
TRACIO designs locating programmes around the constraint and the exception queue. We stay vendor-neutral — no RTLS box, RFID portfolio or AMR margin — so the recommendation follows your KPIs. Gate 1 locks success criteria; the pilot proves them under production load before scale.
Buying criteria operations leaders use for locating
COOs sponsor locating programmes to move throughput, accuracy and exception handling — not to own another dashboard. Criteria that separate useful programmes from science projects:
- KPI ownership on the floor — OEE, cycle time, WIP accuracy, dock dwell or service level owned by ops after go-live.
- Exception workflow first — who acts when a tote, tool or trailer is late, and in which system?
- Production-load proof — pilot on a live shift with written go/no-go, not a quiet demo lane.
- Integration into run-the-business tools — MES, WMS, TMS or CMMS events, not a parallel map.
Hardware vendors sell coverage maps. SIs sell install capacity. Consultancies sell operating-model decks. Ops should buy a locating design that changes the tier meeting within one quarter of pilot.
Operational failure modes in RTLS and RFID programmes
- WIP or yard maps that supervisors stop opening after week two.
- Tags that add more than a few seconds of friction per shift — operators bypass them.
- RF design that works at commissioning and fails under full metal, traffic and shift noise.
- Night-shift and contractor processes never designed — data collapses after 22:00.
- Alerts without owners — noise that trains people to ignore the system.
Questions COOs should ask vendors and integrators
- Which bottleneck cell or dock will show a measurable KPI move in the pilot window?
- How do exceptions land in our MES/WMS — and who owns false positives?
- What is the tagging ritual for operators, and have you timed it on a live shift?
- Show a reference where supervisors, not IT, run the daily huddle from locating data.
- What is the rollback if MES write-paths misbehave during go-live?
How TRACIO differs for the COO
TRACIO designs locating programmes around the constraint and the exception queue. We stay vendor-neutral — no RTLS box, RFID portfolio or AMR margin — so the recommendation follows your KPIs. Gate 1 locks success criteria; the pilot proves them under production load before scale.
Frequently asked questions
Will RTLS slow down my line during deployment?
Properly phased, no. We deploy zone by zone around live operations; downtime windows are usually shift-change or planned maintenance. The risk is in big-bang rollouts — which we avoid as a gate-2 criterion.
How long until I see results?
Inventory accuracy and asset-search time move in weeks. OEE and throughput improvements compound over 6–12 months. We agree the baseline KPIs and review cadence at gate 1 so improvement is measurable, not anecdotal.
Who in my organisation needs to own this?
A named operational owner — typically Operations, Plant Engineering, or a programme manager reporting to the COO — must own the live system from gate 3 onwards. Without that, drift accumulates and the system silently degrades.
Will it work with our existing WMS / MES / ERP?
Yes, in almost every case. Modern WMS and MES platforms accept location and event data via API or MQTT. The integration scope is sized in stage 1 (Design) and validated in the pilot.
Last updated: