Pretend you are the plant ops lead and force the utility package to survive questions about who can freeze a chiller failure drill, how restore paths are timed across buildings, and which override classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between plant tools and the facilities narrative leadership will quote. It asks which utility trees invent completeness the page export never measured, which restore windows look crisp on a slide and soft in the live sample, and what happens when a delayed chiller response lands because ownership is incomplete. A green plant board does not answer those questions. The review needs the utility map, chiller calendar, override packet, and the named person who can freeze a plant path.
Exhibits that belong in the packet
Hand over the plant tools in use, chiller failure drill draft, utility restore plan, override packet, last payer-visible temperature gaps, and one recent case where a delayed freeze hurt a facilities narrative. Include which plant promises still bypass the same review. State the decision: clear the plant change, revise specific controls, or hold until a utility owner is named.
Boundaries matter. The plant ops lead can challenge untested chiller failure drills, restore windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical unit ownership stays with treating teams. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle utility path.
Questions that need written owners
- Which critical chiller class still lacks a tested freeze path with a measured age-out, and who owns the gap?
- What must hold before a utility restore rule can promote into a lasting policy, and who can waive it without a written reason?
- How does a declined plant exception become visible to the requester within the claimed window?
- What is the measured time from a failed temperature finding to a human with freeze authority?
- Which shared override can ship many plant changes without failing a single building health check?
- Who has authority to pause exceptions or force a plant rollback at week end without waiting for the system owner?
Require observed, inferred, or unknown labels. Observed claims need a source. Unknowns become owners and due dates. When two teams claim the same plant authority, force one named decision before the next tool change starts.
Leave a plant ledger
Run the role in Pingpong with the same exhibits the plant team will use. Have the home team answer each objection in writing. The useful output is a short plant ledger: approved utility classes, blocked classes, freeze windows, and the person who can call a freeze.
For adjacent facilities work, pair this seat with a chiller failure drill, the facilities ops lead seat, a water-system alarm stress test, and the EVS ops lead seat. The war-game decisions hub has more seats. Before approving the package, make the plant ops lead write the exact freeze and temperature check that will decide whether the change continues.