OPS.19:5.1 - PumpWorks: preserve incident coverage and recovery
In this constructed continuation of the PumpWorks control-service case, four ready test packages require two rig-hours each. Six rig-hours are currently available, and the retained adverse scenario includes one immediate two-hour repeat. A field incident consumes the change interval and two hours previously available from specialist E27 while exhausting the interruption reserve. No qualified relief is available for an extension.
The local utilization proposal starts all four ready packages and therefore consumes eight rig-hours. Preserving the retained two-hour repeat would require ten rig-hours, so an eight-hour plan silently displaces that repeat. The current financial comparison says only that qualified deferral of the third package is worth 700 more within the stated two-month horizon than immediate completion, while the service account protects incident coverage and E27’s recovery. No current priority, acceptance-window, or financial premise decides the fourth package.
| Decision-bearing item | Supported current fact | Conflict exposed |
|---|---|---|
| package cases and test Work | four ready packages, two rig-hours each, plus one retained two-hour repeat | two selected packages can complete and the repeat can remain reserved inside six hours; the third has a qualified deferral premise, while the fourth has no supported later disposition yet |
| incident and service Work | the incident consumes the change interval and interruption reserve | an extension removes protected response and recovery margin |
| rig and specialist resource use | the rig can appear locally available while qualified specialist support is not | rig utilization alone overstates feasible Work |
| financial consequence | qualified deferral of the third package is worth 700 more in the stated horizon | immediate completion is locally visible but financially worse under the current premises |
| proposed Method trial | its support, permission, service, and recovery conditions are not yet current | starting the trial would convert missing conditions into unsupported Work |
The sequence-only alternative forces incident response, test execution, release coordination, financial comparison, and Method-improvement Work into successive steps of one process. It hides their different subjects, overlap and authority. A combined schedule remains useful when it preserves those distinctions. The utilization-first alternative spends eight rig-hours on all four packages and therefore needs ten hours to retain the adverse repeat; keeping it to eight silently displaces that repeat, while extending qualified specialist Work consumes protected recovery and requires support not present in the current account.
OPS.19 returns a bounded cross-scale reconfiguration: preserve incident coverage and E27’s recovery; complete the two selected packages and reserve the possible two-hour repeat inside six rig-hours; defer the third package to its qualified later slot; hold the fourth package’s start and return its later disposition as unresolved because no qualified priority, acceptance-window, or financial premise selects it; and keep the Method trial closed until service recovery, support, permission, and trial conditions are current. Reopen if qualified relief and access become available, the financial horizon or acceptance premise changes, a qualified fourth-package disposition basis returns, or the incident or service result changes.
This result does not decide the later Method change. It supplies OPS.16 only with the feasible trial boundary and protected conditions.