Library / Operations Management Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:10:20 UTC

OPS.5:5.1 - PumpWorks controller service

PumpWorks-ControlServiceOps considers ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, and competing test-rig requests while maintaining weekly evidenced-release commitments. The current account exposes missing test T9, a safety-return gap, provider-access conflict, release authority, service consequences, and the current rig-access relation.

OPS.5 keeps the items separate. It can admit bounded incident-diagnosis Work for FieldIncident-I73 when identity, incident authority, evidence, performer, and access conditions obtain. It defers release continuation whose required T9 evidence or rig access is absent. It returns SafetyQuestion-S19 to the competent safety authority. A high rank, booked rig request, release candidate, or weekly horizon creates neither capacity, permission, Work, nor release. The first usable result is the item-by-item admission account and visible residual demand; the first honest blocker is the exact missing permission, evidence, access, or specialist return.