RenewOps / Research / EC-WP-1102
What the Incoming Operator Cannot See
Turnover, attribution, and the record that has to answer when the control room is not in the room.
EC-WP-1102 in the Monitoring Truth & Fleet Reconciliation Series31 pagesRob Smith, Energy Compliance, Inc.
Seventeen standing Critical alarms, zero rendered, and a turnover screen reporting none. Acknowledgement time equal to archive time in 4,791 of 4,791 sampled rows, every one naming a person. Operator KPI coverage of one percent. Five failures of situational awareness, each measured, treating awareness as a testable property of the record rather than a quality of a dashboard.
Contents
- What turnover is actually for
- The seventeen alarms nobody could see
- Attribution that was manufactured
- Metrics computed from a population that was not the population
- Identity — one person, two codes; one code, two people
- Acknowledgement is not resolution
- What a defensible turnover pack contains
- Ten questions for your own control room
- What RenewOps does about this
Next in the series: A Rules Engine That Measures Its Own Usefulness
Start of the series: Missing Is Not Zero
See it on your own fleet
The paper describes the method. A demo shows it running against a fleet.
Request a demo