COO — opérationnellisation RTLS, RFID et 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.
La question sous-jacente du 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.
Alignement KPI — la question de la barrière
Every RTLS deployment should be scoped against 1–3 specific operational KPIs the COO already tracks. Fabrication: OEE, WIP turn, cycle time variance, first-pass yield. Logistique: dock-to-stock, OTIF, inventory accuracy, throughput per labour hour.
Soins de santé: 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.
Conception de l’adoption — le deuxième problème le plus difficile
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.
La gestion du changement — le troisième problème le plus difficile
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.
Intégration avec les systèmes d’exploitation
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.
Gouvernance du programme — sous la propriété de qui
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.
Questions fréquemment posées
Comment relier un déploiement RTLS à OEE ?
Plus précisément, en mesurant quel composant OEE le programme est censé déplacer (disponibilité, performance, qualité) et quelle cause fondamentale il traite.
La visibilité en cours améliore les performances ; L’emplacement des outils améliore la disponibilité. Nous concevons le modèle d’attribution OEE à l’étape 1.
Combien de temps prend l’adoption en pratique ?
Adoption au niveau opérateur : 4 à 12 semaines avec gestion ciblée du changement ; plus longtemps sans. Adoption de la prise de décision au niveau de la direction : 8 à 24 semaines. Nous concevons pour les deux délais du plan de mise en œuvre.
Les opérations devraient-elles posséder le programme ou l’informatique ?
Les opérations doivent posséder les résultats et la gouvernance ; L’informatique doit s’occuper de la livraison et de l’intégration de la plateforme. La responsabilité conjointe avec des droits de décision séparés fonctionne mieux en pratique.
Quel est le rôle de l’intégrateur système par rapport à l’équipe des opérations ?
L’intégrateur système assure le déploiement technique ; L’équipe des opérations assure le changement de processus et l’adoption. Les programmes échouent lorsque ces rôles sont confondus — nous concevons explicitement le RACI dès l’étape 1.
Comment gérer la résistance des opérateurs ?
La résistance est généralement un signal que l’intégration des workflows est mauvaise — les opérateurs résistent rationnellement aux systèmes qui ajoutent du travail sans valeur.
Nous diagnostiquons le problème du flux de travail et repensons plutôt que de « gérer » la résistance.
Dernière mise à jour :