COO — operativizzazione RTLS, RFID e 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 domanda sottostante del 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.
Allineamento KPI — la domanda sulla cancellazione
Every RTLS deployment should be scoped against 1–3 specific operational KPIs the COO already tracks. Produzione: OEE, WIP turn, cycle time variance, first-pass yield. Logistica: dock-to-stock, OTIF, inventory accuracy, throughput per labour hour.
Sanità: 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.
Progettazione dell'adozione — il secondo problema più 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.
Gestione del cambiamento — il terzo problema più 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.
Integrazione con i sistemi operativi
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.
Governance del programma — sotto la cui proprietà
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.
Domande frequenti
Come collegamo un deployment di RTLS a OEE?
In particolare, misurando quale componente OEE il programma dovrebbe spostare (disponibilità, prestazioni, qualità) e quale causa principale affronta.
La visibilità dei WIP migliora le prestazioni; La posizione degli strumenti migliora la disponibilità. Prosegniamo il modello di attribuzione OEE nella fase 1.
Quanto tempo richiede l'adozione nella pratica?
Adozione a livello operatore: 4–12 settimane con gestione del cambiamento mirata; più a lungo senza. Adozione decisionale a livello manageriale: 8–24 settimane. Progettiamo per entrambe le tempistiche del piano di implementazione.
Le operazioni dovrebbero possedere il programma o l'IT?
Le operazioni dovrebbero possedere i risultati e la governance; L'IT dovrebbe gestire la consegna e l'integrazione della piattaforma. La responsabilità congiunta con diritti decisionali separati funziona meglio nella pratica.
Qual è il ruolo dell'integratore di sistemi rispetto al team operativo?
L'integratore di sistema si occupa del deployment tecnico; Il team operativo gestisce il cambiamento e l'adozione del processo. I programmi falliscono quando questi ruoli si confondono — progettiamo esplicitamente il RACI nella fase 1.
Come gestiamo la resistenza degli operatori?
La resistenza è solitamente un segnale che l'integrazione del flusso di lavoro è sbagliata — gli operatori resistono razionalmente ai sistemi che aggiungono lavoro senza valore. Diagnostichiamo il problema del flusso di lavoro e ridisegnamo invece di "gestire" la resistenza.
Ultimo aggiornamento: