RTLS for the COO.
You don't buy radio technology. You buy throughput, accuracy, safety and the ability to defend a number to the board. This is the operations lens on RTLS, RFID and IoT — what moves first, what moves slowest, and what to watch for.
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-leverage 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.
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: