COO — operationaliseert RTLS, RFID en IoT.
For a COO, an RTLS, RFID or IoT programme has to move an operational KPI — cycle time, OEE, fill rate, dock-to-stock, OTIF, length-of-stay.
It also has to land in an operating environment where front-line operators actually use it, sustainably, after the implementation team leaves. This insight covers how we think about both halves of that job with COO clients.
De onderliggende vraag van de COO
Not "will the technology work?" — but "will the technology, integrated into our operations, deliver a measurable improvement in the operational KPIs that I'm accountable for,
that holds after the project team leaves?" Most failed RTLS programmes at the COO level fail not because the technology didn't work, but because the operational and adoption work was treated as secondary.
The COO should require operational KPI alignment, adoption design and integration architecture as scoping inputs — not as afterthoughts.
KPI-uitlijning — de gating-vraag
Every RTLS deployment should be scoped against 1–3 specific operational KPIs the COO already tracks. Productie: OEE, WIP turn, cycle time variance, first-pass yield. Logistiek: dock-to-stock, OTIF, inventory accuracy, throughput per labour hour.
Gezondheidszorg: average length of stay, OR turnover time, hand-hygiene compliance rate, asset utilisation. If the deployment can't be tied to a tracked operational KPI, it shouldn't proceed.
This filter alone kills 30–40% of typical RTLS business cases at the diagnostic stage — usually because the underlying use case was speculative.
Adoptieontwerp — het op één na moeilijkste probleem
Operations leaders know that technology deployments fail at adoption more often than at deployment. RTLS adoption depends on three things. Workflow integration: the system has to make a specific operator's job easier or required, not just produce reports for management.
Trust: front-line operators need to trust the data, which means visible accuracy and reliable response when they flag errors.
Time-to-utility: operators have to see benefit within their first week of using the system, not their first quarter. We design for adoption in stage 1 alongside the technical architecture.
Verandermanagement — het derde moeilijkste probleem
Process change is the leverage point that turns RTLS data into operational KPI improvement. Without process change, the data is reporting overhead, not value.
The COO should require a documented process-change plan as part of the deployment scope, covering: new standard work, decision rights at each level, escalation paths, and what stops being done because the system replaces it.
The system is the smaller half of the change; the process change is the larger half.
Integratie met operationele systemen
RTLS data has to flow into systems operators already use — MES on the shop floor, WMS at the dock, EMR at the bedside, EAM for asset management. Standalone RTLS dashboards rarely get adopted; integrated alerts in the operator's existing tooling get adopted.
The COO should require integration into operations systems as a deployment gate, not as a downstream feature. See /integrations for our enterprise integration patterns.
Programmabeheer — onder wiens eigendom
RTLS programmes that fail at the COO level often fail at governance — they're owned by IT or by an external consultant rather than by operations. The COO should own the programme governance, with IT and finance as supporting functions.
Steering committee should have operational metrics on every agenda, not just project milestones. We work as independent programme advisors to COOs in this model. See /for-coo for the dedicated COO persona page.
Veelgestelde vragen
Hoe koppelen we een RTLS-implementatie aan OEE?
Specifiek door te meten welke OEE-component het programma moet verplaatsen (beschikbaarheid, prestaties, kwaliteit) en welke oorzaak het aanpakt.
WIP-zichtbaarheid verbetert de prestaties; De locatie van gereedschap verbetert de beschikbaarheid. We ontwerpen het OEE-attributiemodel in fase 1.
Hoe lang duurt adoptie in de praktijk?
Operator-niveau adoptie: 4–12 weken met gericht verandermanagement; Langer zonder. Adoptie op managementniveau: 8–24 weken. We ontwerpen voor beide tijdsperioden in het implementatieplan.
Moeten de operaties het programma bezitten of IT?
Operaties moeten eigenaar zijn van de resultaten en het bestuur; IT zou eigenaar moeten zijn van de platformlevering en integratie. Gezamenlijk verantwoordelijkheid met gescheiden beslissingsrechten werkt in de praktijk het beste.
Wat is de rol van de systeemintegrator versus het operationele team?
De systeemintegrator verzorgt de technische implementatie; Het operationele team verzorgt de proceswijziging en adoptie. Programma's falen wanneer deze rollen door elkaar raken — we ontwerpen de RACI expliciet in fase 1.
Hoe gaan we om met de weerstand van operators?
Weerstand is meestal een signaal dat workflow-integratie verkeerd is — operators verzetten rationeel weerstand tegen systemen die werk toevoegen zonder waarde. We diagnosticeren het workflowprobleem en herontwerpen in plaats van de weerstand te "beheren".
Laatst bijgewerkt: