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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:00:05 UTC

OPS.9:5.1 - PumpWorks: readiness or rig capacity?

PumpWorks coordinates weekly evidenced releases. In the constructed history, five eight-hour rig-access windows contain 20 test hours, 4 setup hours, 4 unavailable hours and 12 hours with no eligible job. Twelve matters appear on local boards at the final snapshot, but only four ready test packages require eight rig-hours.

A proposal to buy more rig time cites the twelve cards. The practitioner identifies the claimed result—accepted evidence-complete releases—and distinguishes it from test attempts and ready packages. The history supports a late-readiness explanation, but it does not rule out insufficient rig time in a later peak window.

The initial account is:

ElementBounded result
observed losstwelve open hours without an eligible job; accepted-release shortfall still requires its own event and acceptance account
candidate explanationprerequisite delivery misses usable rig windows
serious rivaleligible demand exceeds usable rig time in the relevant deadline windows
discriminating next observationtimestamp package eligibility, usable rig slots, starts, results, returns and final acceptance for the same release population
bounded probewhere engineering and test permissions allow, prepare the next-test inputs earlier for a comparable class; preserve test/acceptance criteria and record mix, access and shared-resource effects
present decisiondo not infer a rig-capacity treatment from card count; operate the supported ready-queue policy and obtain the missing discriminatory basis

If earlier readiness reduces starvation but accepted releases remain unchanged, that result does not establish completion improvement. Inspect acceptance waiting, rework and the next consequential coupling. If usable access is then reduced by ProviderChange-P8, re-evaluate the capacity explanation under the new window.

This is a completed diagnostic/probe decision. It is not a claim that the constructed probe has been performed or that late readiness has already been established as the sole cause.