Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

Part V — Coordinate Queues and Treat the Current Constraint

OPS.8 - Coordinate Queues and Buffers

Status: Stable

OPS.8:0 - Use This When

Use this Method when items wait across service or resource boundaries, a downstream activity is starved despite full boards, or you need to determine whether the release and buffer rules protect the operating result. It is especially useful when teams optimize their own columns while unfinished inputs accumulate elsewhere.

Ask which work is ready for the service, which work is waiting for something else, and what loss calls for protection. The first useful result is a bounded queue-and-buffer policy: eligible population, ordering and release rules, protective purpose and amount where justified, replenishment action, exception authority, and a condition for reconsideration. A useful result can establish eligibility and release rules while returning an unresolved sizing question.

Use OPS.5 for one admission decision, OPS.6 for the next permissible Work in an admitted case, and OPS.7 for a local priority or existing-commitment decision when the shared policy remains adequate. Recover confused subjects through OPS.3. A numerical service or protection claim whose uncertainty matters also needs OPS.10.

OPS.8:1 - Problem frame

An operation may contain several queues and joins. A release needs a tested configuration, a safety result and an authorized decision; a shipment needs product and documents; a case may need more than one specialist contribution. Completing one contribution does not make the whole result ready.

A queue is a selected waiting population eligible for a named service, ordered under a stated policy. A buffer protects or decouples something against a specified disturbance. A board column can describe either, both under separate rules, or neither. Identify which items are eligible for the service and what, if anything, the arrangement protects.

OPS.8:2 - Problem

Local limits can hide unfinished Work beyond a board boundary. Conversely, removing every visible queue can eliminate the ready supply that protects a costly or time-critical activity. Starting more items may increase incomplete kits while the activity needed for completion still lacks usable inputs.

Coordinate release, readiness, ordering and protection together, while preserving the distinction between a customer’s waiting time and the waiting visible at one service station.

OPS.8:3 - Forces

ForcePractical tension
less started Work and reliable replenishmentA small started population can reduce congestion, but too little eligible supply can leave an important resource idle.
local autonomy and joinsA team can finish its own contribution while the receiving activity still waits for the rest of its kit.
small batches and setup burdenSmaller transfers can expose problems sooner; frequent setups or transactions can consume scarce time.
pooling and differentiated serviceSharing eligible demand can reduce idle capacity while changing failure exposure, priority, tail delay or fairness.
simple rules and protected conditionsA common dispatch rule is easy to use, but clinical, safety, compatibility and contractual conditions may require distinct treatment.

OPS.8:4 - Solution

OPS.8:4.1 - Fix the result, service boundary and population

Name the continuing result and its acceptance conditions, the service or resource in question, and the horizon. Reuse the operating focus and current subject account when they fit. Distinguish demand, an admitted matter, a work item, a service visit, a batch and an accepted result. One matter can require several visits; failed or repeated visits are not additional accepted matters.

State the event from which end-to-end waiting is counted. Define ready-queue membership by the inputs, permission, capability and access required for the next service. Keep upstream waiting, blocked matters and work already in progress visible under their own rules; excluding an item from the ready queue does not erase it from the operation’s load or commitments.

OPS.8:4.2 - Recover incomplete joins and ready supply

At each handoff that affects the result, establish which inputs the receiving service can now use. Match the required inputs to the same configuration, case or result. Record the missing input and its supplier when the kit is incomplete. Inspect arrivals and eligibility changes over time, not just one queue snapshot.

A complete kit is relative to the next action. A test can be ready because its configuration, equipment, procedure and permission are available even though its test result does not yet exist. That result may be a prerequisite for later release. Requiring the future output as an input would prevent the action that produces it.

Where several actual structures interact, use OPS.11 to recover the relevant coupling. A local “Done” label is insufficient evidence that a receiving service has its inputs.

OPS.8:4.3 - State what each buffer protects

If the service needs protection, identify what must be protected and a quantity that represents it.

ArrangementWhat its policy controls or protectsUseful quantity
ready-work buffer before a selected serviceservice continuity during replenishment delayeligible service load, related to the resource’s operating calendar
inventory reserveavailability of specified material under replenishment and consumption uncertaintyusable quantity by material, location and condition
capacity reserveresponse or recovery when load or availability changesusable resource time with the necessary capability and access
limit on started itemscongestion and exposure from concurrent unfinished mattersitems under an explicit start/finish boundary, with load differences retained

For the selected arrangement, state the shortage or disturbance, the consequence of failure, who replenishes it, what consumes it, and which signal calls for replenishment or another response. A customer’s commitment has its own parties and conditions; it does not automatically put the item in a protective buffer.

Work backward from the next shortage: when must replenishment become eligible, how long do recognition, request, authorization, supply and receiving checks take, and what other work uses the same people or resources? Choose a trigger that leaves that whole response available. For continuing service, also recover the quantity supplied per request, the earliest permitted next request, any overlap limit and the supplier’s capacity. Follow successive consumption and replenishment events: the available eligible load must cover consumption until the next replenishment is eligible for use, and replenishment must sustain the required pace. More initial stock can cover a finite gap but cannot correct a continuing supply deficit. Distinguish material ordered, delivered and actually ready. A late-response signal needs a permitted alternative, such as different supply, protected capacity or an explicit service revision.

OPS.8:4.4 - Compare policies by their operating mechanism

Use an existing policy when its eligibility, release and protection rules suffice. Where a choice remains, compare it with a feasible alternative before examining more elaborate policies.

  • If incomplete kits create downstream starvation, coordinate the missing inputs and release into the receiving service only when its kit is ready.
  • If excess starts congest the relevant operation, compare a whole-boundary release limit with the existing local limits. Count unfinished matters that crossed local board boundaries.
  • If a supported constraint needs protection, relate release and replenishment to its usable pace. Use OPS.9 when the constraint itself is uncertain.
  • If pooling is proposed, test service compatibility, routing, resource failures, priority and the service criterion that matters. Also ask whether ownership, visibility of waiting work or interruption changes the performer’s processing and checking behavior. Hold service quality and protected classes fixed when comparing those observations. Fixed service-time analysis remains useful when that premise is supported; otherwise weigh the cost of checking how dispatch affects service against the value of that answer before rollout.
  • If batch size is the lever, compare setup or transaction burden with waiting, holding, feedback and rework consequences. Transfer batch and processing batch may differ.

Keep the end-to-end result and waiting origin fixed in the comparison. Reducing a downstream queue by holding demand just outside its measured boundary is not an end-to-end improvement.

When earlier work can revisit a resource after the release signal, OPS.8.1 - Choose Work-Release Rules When Earlier Work Can Return constructs the release decision with that remaining or contingent demand. When auxiliary work could occupy an idle reserve, OPS.8.2 - Use Protective Capacity While Keeping It Available constructs its interruption or completion and the return to protected service. Reuse an adequate existing arrangement when the proposed use changes none of its relevant conditions.

OPS.8:4.5 - Size protection only to the supported use

Translate the supported replenishment delay into the amount consumed during it, using the protected activity’s calendar and rate. For example, a rig consuming one rig-hour of eligible load per open hour needs two ready rig-hours to cover one stated two-open-hour interruption. For a repeating policy, apply the quantity and cadence check in :4.3 as well. These are scenario-qualified conclusions; a probability guarantee needs the corresponding distributional basis.

Compare the carrying, delay and attention costs of more protection with the consequences of shortage. Include unusable or expired stock, changing case mix, correlated demand, failures, recovery and competing service classes where they change the choice. Use OPS.10 for a capacity/service comparison or a model-qualified distributional claim.

A relation among average population, arrival rate and time can check consistent units and accounting. It cannot determine a protective percentile or establish that a buffer never empties. If replenishment behavior or shortage consequences are unknown, keep the part of the policy that is supported and return the exact missing sizing input.

OPS.8:4.6 - Return and operate the bounded policy

State the eligible population, ordering rule, release condition, any protective amount selected or still unresolved, replenishment signal and action, exception authority, affected commitments, and review condition. Use the operation’s existing account when it can carry that information.

For a trial, state its horizon, monitored consequences and withdrawal condition. Observe whether the policy changes accepted results, total waiting, starvation, rework, burden and protected service classes. Keep the population and waiting origin visible when using a column count. A demand, eligibility, replenishment, access or acceptance change can reopen the policy before the scheduled review.

OPS.8:5 - Archetypal Grounding

OPS.8:5.1 - PumpWorks: twelve matters, four ready test packages

In this constructed case, PumpWorks coordinates weekly evidenced controller releases and incident response. Across five eight-hour rig-access windows, its history shows 20 hours of test execution, 4 of setup, 4 of unavailability and 12 with no eligible job. The final board snapshot contains twelve matters. Four test packages are ready and require eight rig-hours under their current estimates.

The snapshot supports a ready queue of four packages with eight rig-hours of estimated load. The history shows lost open time with no eligible job. Neither establishes that twelve matters form one service queue or that rig capacity limits accepted releases.

The immediate policy is to book and dispatch only packages whose next-test inputs, permission and access are current; track the remaining matters by their missing inputs; and retain their waiting in the end-to-end account. The existing authorized priority rule orders the eligible packages. No new buffer quantity is claimed until replenishment and shortage consequences are known.

ReleaseCandidate-R42 lacks test evidence T9. If the inputs and lab-test permission for T9 are current, that missing output is not a reason to mark the test itself ineligible. SafetyQuestion-S19 and release authority remain separate conditions for the later release decision.

To diagnose lost releases, use OPS.9 to distinguish late readiness from insufficient usable rig time as explanations for lost accepted releases. The return to OPS.10 is the eligible-load and access-window comparison, including recovery and rework. OPS.11 handles ProviderChange-P8 when its access decision changes those windows. The first policy can be used while those wider questions remain bounded and explicit.

OPS.8:5.2 - A small protection calculation

A service has one qualified resource, consuming one unit of ready service load per open hour. Its coordinator has a supported planning scenario in which replenishment can be interrupted for two open hours, and no other resource can serve that class. A two-unit ready buffer covers that interruption if service demand and eligibility remain as stated.

Keeping only one unit leaves one open hour exposed in that scenario. Keeping four units adds no coverage needed for the specified two-hour interruption, although another supported disturbance might justify it. If that interruption can instead last four hours, the two-unit conclusion reopens. For continuing service, check how many eligible units each request supplies and when another request can be made.

In a two-hour planning scenario, each ready unit is a one-hour job. At hour 0, A and B are eligible; replenishment is authorized and requested before A starts. The rule requests the next two jobs when two unstarted jobs remain immediately before dispatch and no earlier request is outstanding. For each such request, the supplier can make the next pair eligible within two open hours. Setup, receiving checks and access are included in that bound; they use separately available support, not the protected resource. This repeatable response supplies two jobs for each two-hour consumption cycle.

In the supplied sequence, A runs 0–1, B runs 1–2; C and D arrive and pass their receiving checks at 1.5. Although no unstarted job remains from 1 to 1.5, B is still running: there is no service starvation. At 2, C and D are ready, the earlier request is closed, and the next pair is requested before C starts. It becomes ready at 3.5; C and D run 2–3 and 3–4. This return demonstrates two cycles under the supplied trace. The observation burden is one request/acknowledgement and one eligibility confirmation per pair; an existing dispatch record can carry both.

Now, at 1.25 the supplier reports that C and D cannot be ready before 2.5. The coordinator has no approved substitute. A and B still finish by 2; service then waits half an hour, and C cannot finish before 3.5. A promise of three completions by 3 cannot be met under these conditions and needs the OPS.13 service decision.

For later operation, three initial one-hour jobs would cover one 2.5-hour response, but adding that stock alone does not repair the continuing two-job policy. Even if the first pair is requested at 0, successive 2.5-hour responses can leave five jobs consumed by hour 5 and the next pair unavailable until 5.5. Compare a change to quantity or request cadence with the supplier. One conditional alternative is three eligible jobs per request, requested before dispatch when three unstarted jobs remain and no earlier request is outstanding, with a supported whole-response bound of 2.5 hours for every request. Starting with three jobs, their three-hour coverage then contains each response; the next request is made before the next three-job group begins. The former two-job promise does not establish this larger response. Use the supplier’s established capacity and commitment for the larger request if they cover these conditions. Otherwise ask what quantity and request cadence it can support under the same receiving checks and support capacity. Until that answer is obtained, retain the supported finite coverage and return the unsupported continuing-service promise for revision. Include the added stock and coordination burden in the choice.

OPS.8:5.3 - Patient waiting is not one interchangeable queue

A hospital coordinator receives qualified clinical eligibility and priority for a particular resource class. The operating queue includes only cases that can use that service under those conditions. Patients awaiting a different clinical decision or capability remain visible in the wider waiting account.

Coordinate the resource queue using the applicable clinical eligibility and priority. Establish any required consent or treatment decision through its qualified holder. Pooling unlike service classes is not justified merely because the combined list is shorter.

OPS.8:5.4 - Pooling can change how people serve the queue

Consider two qualified diagnostic practitioners serving interchangeable routine requests for two hours. A separate protected urgent-service arrangement and the same diagnostic acceptance criteria remain unchanged. With two assigned requests each, the supplied dedicated-queue trace takes 60 minutes per request and completes four accepted results by hour 2. A fixed-rate pooling calculation predicts the same four, with potential benefit when the assignment becomes unbalanced.

The proposed common queue removes each practitioner’s visible pending count and makes assignment negotiation part of every pickup. In a constructed matched replay, each request now consumes 60 minutes of diagnosis plus 12 minutes of that coordination; checking is unchanged. Only two results finish by hour 2; all four finish by 2.4. The change has not provided four timely accepted results, even though the jobs remain compatible and total demand is unchanged. Do not roll out that policy for the four-result commitment. Retain the current arrangement, or test a pooled policy with explicit pickup ownership and visible pending load before claiming that it preserves the earlier rate.

The comparison itself needs time: here 30 minutes to agree the comparable requests and quality check, and 10 minutes of independent observation per arrangement, in addition to the observed service work. Those supplied costs belong to the choice, as do transition and training if a revised pool is tried. In live use, preserve mix, staffing and quality, account for learning/carryover, and inspect whether the observed change supports the claimed cause. The stipulated times establish the consequence of the specified coordination work. Evidence from operating use is needed to attribute an actual service change to the queue arrangement. When automated service has a stable rate and dispatch changes none of these behaviors, the fixed-rate model can be sufficient for the planned comparison.

OPS.8:6 - Bias-Annotation

BiasConsequenceCountermeasure
board-boundary biasWaiting disappears when an item leaves a local column.Retain the operation’s population and waiting origin.
zero-buffer idealProtection is removed together with avoidable congestion.State the disturbance and shortage consequence before changing the amount.
complete-kit absolutismEvery future result is demanded before any useful action can start.Define readiness for the next service, not for the whole case’s eventual completion.
local-utilization pressureMore starts create incomplete kits and downstream waiting.Inspect the accepted result and receiver-ready inputs.
pooling optimismMean efficiency hides class-specific or failure-related loss.Compare the actual service criterion and resource assumptions.

OPS.8:7 - Conformance Checklist

  1. Can the reader identify the operating result, service boundary, eligible queue members and wider unfinished population?
  2. Does readiness describe inputs for the next service without requiring that service’s future output?
  3. Does every selected buffer have a protective purpose, units, replenishment action and shortage consequence?
  4. For a proposed change, does the comparison with the current arrangement use total waiting and accepted results?
  5. For any protection that needs sizing, is the amount justified for the stated scenario or distributional claim, or is the missing sizing condition clear?
  6. Are exception authority, affected commitments, monitored consequences and reopening conditions usable by the participants?

These questions help identify whether the policy specifies usable actions. Assurance additionally requires the case evidence, capability, permission, load and uncertainty basis needed for the particular protection or service claim.

OPS.8:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
Count every board item as ready supply.Some items lack prerequisites or use another service.Recover membership and missing-input populations.
Treat commitment as buffer membership.A promise does not establish eligibility or physical protection.State the two relations separately.
Size a “never empty” buffer from averages.A mean relation does not establish the shortage tail.Qualify replenishment scenarios and consequences through OPS.10.
Improve the metric by moving its start boundary.The customer can wait just as long outside the reported queue.Preserve the end-to-end origin and show local waiting separately.
Use one pooling or batch rule everywhere.Compatibility, failure, setup and service objectives differ.Compare the concrete alternative under the receiving operation’s conditions.

OPS.8:9 - Consequences

The operation can reduce avoidable congestion while retaining justified protection. Participants can see whether the next useful action is to replenish a kit, dispatch eligible work, restrict starts, obtain capacity evidence or coordinate another structure.

The cost is maintaining consequential eligibility and replenishment information. A more precise ready queue can initially look smaller without any improvement in the wider operation. Use operating evidence to establish whether the revised policy improved the receiving result.

OPS.8:10 - Rationale

Queue coordination works at the receiver’s service boundary and at the wider result boundary together. The first prevents dispatch of unusable inputs; the second prevents hidden waiting and local improvement from replacing the actual purpose.

Choose protection for the disturbance it must absorb and a concurrency limit for the risk of starting more work. A cheap eligibility rule can be useful before a numerical buffer study, while a numerical guarantee cannot borrow that rule’s adequacy.

OPS.8:11 - SoTA-Echoing

Practice question and selected lineSerious alternative, trade-off and pattern changeSource roles, limits and reopen condition
How should local completion and downstream readiness be coordinated? Adapt whole-operation ready-supply and complete-kit reasoning.Local column limits are cheaper but can miss joins; a complete-kit rule applied to the whole case can block useful investigation. Sections 4.1–4.4 and 5.1 instead bind readiness to the next service while retaining total waiting. The added input matching is justified when it establishes which jobs can be dispatched or helps prevent starvation.Tendon, The Book of TameFlow (2022), complete-kit example and time-buffer discussion, printed pp. 135–137 and 141–143, is a mechanism candidate. The Kanban Guide 2025.5 is the serious workflow-policy comparator. Neither establishes one policy for every operation. Reopen when the join, eligibility or receiving result changes.
How much protection or batching is useful? Adapt disturbance-specific protection and the setup-versus-delay comparison.Minimizing every queue or batch ignores the cost of shortage or repeated setup. Sections 4.3–4.5 and 5.2 require a purpose and supported scenario instead of a universal optimum. This costs an explicit consumption/replenishment account, not necessarily a full optimizer.Tendon’s time-buffer account and Reinertsen, The Principles of Product Development Flow (2009), E6–E9 and Figure 5-4, supply competing mechanism candidates. Their models do not establish a protection tail or transferable batch optimum. Reopen when setup, replenishment, feedback or shortage consequences change.
Should eligible demand be pooled? Adapt model- and service-criterion-specific comparison.Pooling can improve one mean measure while worsening a protected tail or class. Section 4.4 keeps the service criterion and failure assumptions explicit.Andradóttir, Ayhan and Down (2017) and Cao et al. (2021) supply counterexamples under different modeled conditions. Their results do not prescribe a rig or clinical queue. Reopen for the actual routing, failure, abandonment or service-class change.

Song, Armony and Roels (2024) report two online experiments in a healthcare-delivery context in which queue configuration, ownership and awareness of queue length interact with processing behavior. Their abstract supports questioning a fixed-service-time premise, not importing an effect size, clinical conclusion or dedicated-queue rule. Sections 4.4 and 5.4 adapt that question to a same-result comparison and include observation cost. Keep a capable pooling model when its behavioral assumptions fit; reopen when the arrangement changes attention, quality, ownership or the protected population.

OPS.8:12 - Relations

OPS.3 and OPS.4 supply matching subject and current-state accounts. OPS.5 consumes the applicable admission or release limit; OPS.6 uses the policy for permissible case continuation; OPS.7 supplies local priority under its authority without redesigning the queue.

OPS.9 supplies a supported constraint account when protection depends on that diagnosis. OPS.10 qualifies load, capacity and protection/service uncertainty. OPS.11 coordinates couplings that a local queue rule cannot resolve.

Current FPF C.16 and C.27.TA govern measurement and time use. A.22 and E.18 govern relevant structures; E.18.NET applies only to independently identified flow structures with obtaining cross-flow relations. Clinical, safety, legal and other specialist permission remains with the practice that supplies it.

OPS.8:End

OPS.8.1 - Choose Work-Release Rules When Earlier Work Can Return

Type: Method pattern Status: Stable Normativity: Normative

OPS.8.1:1 - Problem frame

Use this when finishing one operation can trigger new work even though the previous result may still need correction, another visit or downstream acceptance. A specialist finishes an analysis and begins a long client session; the analysis then returns for urgent revision. A part leaves a machine but may return after inspection. An admission limit frees a place at local completion while later work still needs the same resources.

Choose what event should permit another start, what remaining and possible work that start must accommodate, and how to act when feedback arrives. The result is a release rule that can be operated: a signal, eligible next work, a load or time condition, treatment of returns and a response when the conditions no longer fit.

Start with the result and resource that the rule must protect. If the existing rule already handles these returns adequately, use it through OPS.5 rather than reconstruct it for every admission. Identifying the resource that limits throughput, when that is uncertain, is a separate contribution from OPS.9.

OPS.8.1:2 - Problem

A completion signal establishes that something finished within its stated boundary. The next start can nevertheless displace work still needed for the previous customer’s result. A rule that waits for all possible later claims can create the opposite loss: useful resources remain idle while a completed item awaits a response that uses none of them.

The operator needs to compare these consequences before selecting a signal. The signal, the population limited by a card or count, the resource load and the customer’s completion event may have different boundaries.

OPS.8.1:3 - Forces

ForcePractical tension
Earlier release and correction capacityStarting sooner can advance new work but occupy the resource needed when an earlier result returns.
Simple counts and unequal demandsOne freed place is easy to recognize; the returning and incoming jobs may require very different resources and times.
Protection and useful idle timeHolding capacity can preserve a deadline; excessive protection postpones work without improving the required service.
Feedback timing and decisionsWaiting can reveal whether a return is needed, but that information may arrive too late to protect the result.
Local pace and the receiving resultA constraint’s completion can regulate replenishment while another resource or downstream join determines customer delivery.

OPS.8.1:4 - Solution

Choose the receiving result → locate the proposed release signal → recover work that remains or can return → compare the next admission with the capacity it would leave → choose the rule and its response to feedback → operate it and reconsider the changed conditions.

The capacity comparison can return to the proposed signal, job selection, resource arrangement or commitment. A signal that works for one product mix may fail for another.

OPS.8.1:4.1 - Choose the completion and release events separately

Name the service to be protected, its receiving result and relevant horizon or deadline. Retain the event from which the customer has been waiting. Then identify the event currently proposed to permit another start: an operation completes, the selected constraint consumes its next ready job, a job leaves a controlled loop, acceptance arrives, or the remaining workload falls below a limit.

For a count limit, identify what enters and leaves its population. For a replenishment signal, identify the activity and ready supply it serves. Define readiness for the next operation using OPS.8; future outputs need not already exist.

Ask what obligation or operating work survives the signal. Trace it to the resource that would perform it. A card may be returned when a job leaves one loop even though that job still contributes load to another resource or a later visit. Preserve those contributions in the comparison.

OPS.8.1:4.2 - Recover known work and possible returns

For each resource on which the release decision depends, establish the unfinished operations already assigned to it, their remaining occupancy, calendars and required times. Include known later visits by the same job. Count the resource use of each visit, while retaining one customer’s result and waiting history.

For work that may return, identify the event that reveals the need, when the resource could be needed and the possible amount and kind of work. A supported bound, a small set of scenarios or a joint probability model can be enough, depending on the receiving question. Preserve shared causes: the same defect may return several jobs together.

Separate work already known to remain from allowance for work that is still contingent. If a return becomes known, replace its contingent allowance with the known remaining work; do not add both for the same visit. When acceptance or another suitable event excludes that return within the selected horizon, release the corresponding allowance. An acceptance event does not remove separately retained warranty or other later service obligations.

When the possible return cannot yet be quantified, keep the supported comparison and identify which promised service remains unsupported. Seek further observations when their attainable result could improve the release decision or the grounds for relying on it enough to justify the cost. Release despite that uncertainty is a separate decision for a participant with the relevant authority, under commitments and protected conditions that permit the choice. It does not establish that the earlier service is protected.

OPS.8.1:4.3 - Test what capacity the next start leaves

Begin with the simplest consequence that can decide the question. In a fixed horizon, the known remaining occupancy, the proposed job’s occupancy and a chosen allowance for returns can be compared with usable resource time.

For example, a resource with five usable hours cannot complete two hours of existing work, two hours of a protected return and two hours of new work within that horizon. Even when enough hours are available in total, readiness, precedence, joint resource requirements or an uninterrupted window may prevent a feasible placement. OPS.10.2 constructs that schedule or obstruction.

Match the comparison to the promised protection:

  • For a stated return scenario, place that return and the new work with their readiness, access and deadlines.
  • For protection over a bounded family, show that the selected response can handle every member of that family.
  • For a probability requirement, use the joint model and the operating policy through OPS.10.1; a mean return load alone does not determine a service probability.

A policy that reacts to feedback must use information available at the time of its choice. If release is allowed before inspection, the policy needs an executable response when inspection later requires a return. It cannot choose an early start only in retrospect for the outcomes in which no correction was needed.

A workload-control norm can instead be a calibrated congestion-control quantity. Retain its definition and units: a route-position-weighted load is not the same quantity as occupied hours available before a deadline. Use its operating comparison for its intended purpose, and a finite schedule when the deadline question requires one.

OPS.8.1:4.4 - Compare signals and their return treatment

Compare the existing rule with a material alternative on the same arrivals, resources, receiving result and waiting origin. Keep the rule’s actual mechanism visible.

Candidate ruleWhat permits new workWhat to resolve about returns
Completion at a selected constrained activity triggers replenishmentThat activity consumes the next ready supply and calls for its replacement.Which later work can revisit this resource or occupy another resource needed for delivery? What ready supply and remaining capacity protect those visits?
A job’s departure frees a place in a limited loopThe controlled population falls below its limit.Is a return inside that loop, or admitted through another rule after departure? Retain its load wherever it will be served.
Remaining workload fits the selected normsThe candidate’s contributions fit the resource-specific load rule.Include repeated visits under that rule, distinguish known work from uncertain returns, and define what happens when feedback changes the load.
Acceptance permits the next startThe selected receiving event closes the exposure being protected.Does waiting for this event preserve useful capacity, or unnecessarily hold a place while acceptance uses another resource?

The names Drum-Buffer-Rope, CONWIP and workload control locate families of these methods. Identify the boundaries and exceptions of the rule being used. A rule can combine a replenishment signal with a return allowance or use a separate return queue. Evaluate that combination rather than assuming that choosing a name determines its behavior.

Compare the delay imposed on new work with the protected earlier result. If holding one job would starve an important resource, consider another ready job with compatible resource use, a smaller independently useful unit, another capable resource or a different start window. Any exception that spends protected capacity changes what the rule can support. OPS.7 and OPS.13 supply priority and commitment decisions when the two services cannot both be retained.

OPS.8.1:4.5 - Define the actions at release and feedback

Choose the next eligible work and the condition under which it can start. Make the condition usable in the operation’s existing account: for example a freed loop place together with a reserved correction window, or a remaining-load calculation updated at inspection.

When the need for a return becomes known, replace its contingent allowance with the required work and identify when its inputs, access and resources will be available. Apply the priority and placement rule under those conditions. Keep the original customer clock. A repeated service visit may restart a station’s own interval without restarting the customer’s wait.

When a suitable event rules out the return, remove only the allowance that the event actually resolves, then reconsider held work. At late or ambiguous feedback, update the possible demand and the time left; absence of a message alone does not establish acceptance.

Observe whether the rule changes completion, total waiting, resource starvation, actual correction burden and displaced work. Reopen it when the return route, feedback time, service duration, resource access, product mix or receiving requirement changes. Stop redesigning once the existing inputs support a usable rule or a specific choice requiring changed conditions.

OPS.8.1:5 - Archetypal Grounding

OPS.8.1:5.1 - An analysis returns during the next client session

A specialist finishes report X at hour zero. A review at hour one will either accept it or identify a correction requiring two uninterrupted specialist-hours. If a correction is needed, the corrected report is required by hour three. These are the two stated possibilities; the correction input becomes usable at hour one.

New job Y is a four-hour live session using the same specialist throughout. It is ready at zero, can start at any suitable time, must finish by hour seven and cannot be paused to perform X. Other resources do not change these conditions.

Releasing Y to run at 0–4 on X’s first completion gives X no correction window before three. In the return case, the earliest correction is 4–6. The completion signal did not remove X’s possible resource need.

A rule that preserves X’s 1–3 correction window works as follows:

Feedback at hour oneSpecialist’s next workCompletion of Y
X acceptedStart Y at 1 and finish at 5.5
X needs correctionCorrect X at 1–3; run Y at 3–7.7

The same observable rule handles both possibilities. It costs one hour of delayed Y completion in the no-return case relative to starting at zero. Holding a loop place until review and returning the place earlier while separately preserving the correction window can implement the same resource decision.

If Y instead needs one uninterrupted hour, with the other conditions unchanged, it can run at 0–1 and leave the same 1–3 correction window. Waiting for review before starting that Y would add delay without improving the stated protection of X.

Change the review time to hour two while retaining X’s deadline three and its two-hour correction. Even an idle specialist can now finish that correction only at four. Keeping Y outside the system does not repair this obstruction. The operation needs earlier usable feedback, a genuinely shorter correction or a changed commitment.

OPS.8.1:5.2 - A free place and a full receiving resource

A manufacturing resource S is available continuously from 0 to 5. Job A is already running there from 0 to 2. A part X undergoing inspection elsewhere may need one additional two-hour visit to S; the answer becomes available at hour one, and any such visit must be complete by five.

A new job Y would require two uninterrupted hours at S and is also wanted by five. Its upstream activity has space and emits a release signal. There are no other operations needed for these completions.

Protecting the stated return and promising Y requires 2 + 2 + 2 = 6 hours in a five-hour window. The free upstream place does not remove this obstruction.

At hour one, one hour of A remains. If X is accepted, the remaining requirement is one hour of A plus two of Y; A finishes at two and Y runs 2–4. If X returns, its visit can run 2–4, but Y cannot also finish by five. Replacing the two-hour return allowance with X’s known visit preserves this result; adding both would falsely claim eight original hours of demand.

This example uses full occupied hours and a finite deadline. A workload norm based on a different weighted quantity would need its own interpretation. If Y instead used an independent resource, holding it because of S’s protected hours would require another reason.

OPS.8.1:5.3 - Waiting for an event that cannot consume the resource

An operation completes a job inside a machining loop. The remaining customer acknowledgment will use a separate administrative service, and the operating arrangement excludes any further use of the machining loop for this job in the horizon under consideration. The next eligible part has the required resources and fits the loop’s release rule.

Keeping the machining-loop card until that acknowledgment would postpone the part without protecting any machining work in the stated horizon. Return the card at the loop’s completion and retain the customer’s outstanding acknowledgment in its own account. If inspection can instead return the part to that machine, this premise is lost and the release decision reopens.

OPS.8.1:6 - Bias-Annotation

A board or card encourages attention to visible membership. Keep the resource work that survives a boundary crossing. Conversely, a policy designed around a painful return can retain every item until remote final acceptance; test whether that event can still change the protected resource use.

Expected load can make correlated returns appear manageable. Use the return pattern needed for the actual consequence. For a claim about a group of returns, qualify the rule against the corresponding joint demand.

OPS.8.1:7 - Conformance Checklist

  • The receiving result, its time requirement and the proposed release event are distinguishable.
  • Known remaining operations and possible returns retain their resource use, readiness and customer waiting origin.
  • Any claimed protection states its scenario, bounded family or probability interpretation; an unresolved risk remains visible in the release choice.
  • A total-load screen is followed by placement when calendars, precedence or uninterrupted work can change feasibility.
  • Feedback replaces or releases the relevant allowance; it does not count the same return twice.
  • The selected rule states what happens to both returning work and the next candidate, including conflicts that need a changed priority or commitment.
  • A changed feedback time or return route can reopen the decision.

OPS.8.1:8 - Common Anti-Patterns and How to Avoid Them

MistakeConsequenceRepair
Treating a local completion as the end of resource responsibilityA new long job displaces an earlier correction.Retain the remaining and contingent resource demands after that event.
Holding every place until remote final acceptanceUnrelated acknowledgment delays useful service.Choose the controlled loop and retain obligations outside it in their own account.
Reserving for a return and then adding the same work againArtificial overload blocks usable capacity.Replace the matching allowance when the return becomes known.
Calling a mean return load protectiveA burst or correlated return defeats the promised deadline.Test the scenario, bounded family or joint probability required by that promise.
Resetting the customer’s clock when work returnsA policy appears faster by losing earlier waiting.Separate visit intervals from the original receiving interval.

OPS.8.1:9 - Consequences

The release rule can exploit available capacity while retaining the demand that may return. Its price is the information and coordination needed to distinguish the relevant events and resource contributions. A small deterministic comparison may suffice; larger operations can need the capacity and scheduling constructions.

Protecting an earlier correction can delay new work, and waiting for information can itself make the earlier result unattainable. The method exposes those choices for the responsible operating decision.

OPS.8.1:10 - Architectural Rationale

A release rule can permit new work at local completion while the customer’s result still requires another resource or a later visit. The method therefore couples that event with the work still needed and with the consequence of the next start.

The comparison works in both directions. Requirements of the receiving result constrain local starts; actual readiness and resource windows constrain the delivery that can be supported. A specialist’s service, a loop’s population and the customer’s result can retain different boundaries without becoming inconsistent.

Use the service question and its horizon to identify which returns matter. Distinguishing a known visit, a contingent allowance and new work makes updates local and keeps counts from replacing the work they are intended to regulate.

OPS.8.1:11 - SoTA-Echoing

For the question “may this new job start while earlier work can return?”, the selected line combines a defined release signal with the remaining resource demand and the required service. Two simpler alternatives are one-in/one-out counting and waiting for final acceptance. The first can omit consequential load; the second can delay work without protecting that service. Sections 4.1–4.5 add the event, load, timing and feedback operations needed to decide between them. Cases 5.1–5.3 demonstrate different outcomes, including a condition under which holding capacity cannot help.

Hopp and Spearman, Factory Physics, third edition, §10.4 and §§14.3.1–14.3.2, supply CONWIP’s controlled-loop construction and the distinction between counting jobs and accounting for unequal resource demands. Adopt the loop boundary and adapt the treatment of work diverted for rework: freeing a card requires retaining whichever other admission and load rules govern that work. Decide separately whether customer acceptance closes the resource exposure in this operation.

Steve Tendon, The Book of TameFlow (2022), printed pp. 117 and 138, supplies a concrete contrast: a constrained team’s completion triggers replenishment, while the teaching exercise also permits a customer return for reprocessing and retains elapsed project time. Adopt the separate signal and customer-clock operations. Adapt the release choice to the actual return resource and timing through sections 4.2–4.5; whether a later correction fits depends on those resources and times.

Thürer and Stevenson, Workload Control in Job Shops with Re-entrant Flows: An Assessment by Simulation, §§3.2 and 4.3–4.4, compare load accounting and release behavior for known repeated visits. Their corrected load weights route positions, and a starvation-triggered exception can exceed a norm. Adopt explicit repeated-visit accounting; distinguish that congestion policy from the finite occupied-hours test in 4.3. The study does not supply the timing or distribution of an as-yet-undiscovered correction.

Prabhu and colleagues (2024), the REM subsection on printed p. 149 and comparison on pp. 152–153, combine regular and re-entrant workload in a release rule. Adapt that combined-load comparison in 4.2–4.3: possible corrections still awaiting discovery need an allowance or scenario in addition to known visits, and resource-specific time limits remain. The study’s rankings differ for flow time, throughput and modeled profit, supporting the receiving-question comparison in 4.4. Those rankings concern the simulated rotor-blade operation and the selected performance measure. The occupied-hours screen here is an accounting bound followed by placement, rather than a protection claim inferred from an average population-time relation.

Reopen the selection when another signal or accounting method supports the same receiving result with less delay, information or coordination, or when returns, resource sharing, interruption, feedback timing or service requirements change. Compare outcomes at the original customer boundary; changing that boundary is not evidence that the rule improved service.

OPS.8.1:12 - Relations

OPS.8 supplies the queue, readiness and protective-policy context. OPS.5 applies the resulting rule to a particular admission; OPS.6 continues an admitted case; OPS.7 and OPS.13 handle priority and commitment changes.

OPS.11.1 supplies the operating arrangement and resource relationships. OPS.15.1 constructs the visit, occupancy and customer-time quantities. OPS.10.1 compares capacity and uncertain service; OPS.10.2 constructs the finite schedule and revises it after feedback. These contributions let the release rule remain about when to start work rather than redefining the underlying quantities or scheduling method.

MMP.8 and MMP.8.SD supply sequential information and consequence reasoning when the choice depends on what can be learned before acting. C.11 supports choice under the actual alternatives and resources; C.29 retains correspondence between the modeled load and the operating work.

OPS.8.1:End

OPS.8.2 - Use Protective Capacity While Keeping It Available

Type: Method pattern Status: Stable Normativity: Normative

OPS.8.2:1 - Problem frame

Use this when a person, machine or computing resource has idle intervals reserved for another service, and useful auxiliary work could occupy those intervals. An operator could prepare the next job or practise a skill. A machine could run an experimental batch. A computing resource could run a background analysis. For a reserve that must keep its present protection, consider activities whose interruption or completion leaves the required service available in time.

Construct a usable arrangement: eligible auxiliary work, conditions for starting it, what triggers its end or interruption, and how the resource becomes ready for the protected work. The first result can be a short timing comparison that accepts one candidate and rejects another.

Start from the protection already selected through OPS.8: what work needs which capability, amount of resource, response time and access. If an existing arrangement meets those conditions and the proposed auxiliary work changes none of them, apply it. Choosing a learning goal or an improvement experiment belongs to the corresponding development method; this pattern establishes whether its execution fits the operation.

OPS.8.2:2 - Problem

“No work is running” and “this capacity can be promised elsewhere” describe different conditions. An auxiliary job can consume the time needed to resume the protected service, retain a required resource after suspension, or create another commitment that prevents recall.

Keeping all such intervals empty can also forgo useful preparation and development. The practitioner needs to distinguish work that preserves the selected protection from work that spends it, and to compare the useful contribution with the costs of interruption and recovery.

OPS.8.2:3 - Forces

ForcePractical tension
Useful preparation and availabilityAuxiliary work can improve later service while obstructing a call that arrives now.
Short fragments and retained progressSmaller units can be easier to stop, but repeated saving, switching and reconstruction can consume their value.
Nominal priority and actual releaseA priority rule can demand a return while the required person, machine state or memory remains unavailable.
Development and present capabilityLearning may expand future options; the protected work still needs capability available today.
One return and sustained serviceA quick first response can conceal exhaustion, displaced recovery or insufficient capacity for subsequent calls.

OPS.8.2:4 - Solution

Recover the protected service → choose an auxiliary unit → construct its interruption or completion and the return to service → compare the preserved service and useful gain → operate the arrangement and revise changed conditions.

OPS.8.2:4.1 - Recover what must remain available

Name the protected work, the event that can call the resource, and the condition that counts as ready. Readiness includes the capability, access, configuration and inputs needed for the next protected action. Moving a person back to a workstation may precede readiness if the person still needs a handover or must reconstruct the situation.

Distinguish two common requirements:

  • Be ready by a known time, with no earlier call included in the selected protection.
  • Be ready within a stated delay after a call that can arrive while auxiliary work is running.

A job that fits the first requirement may fail the second. Also retain the amount and duration of protected service needed after the return; a prompt start alone may not satisfy the commitment.

Separate capacity needed for this protection from capacity left over after it. An idle interval does not establish either amount. If several services rely on the same reserve, retain their relevant joint demand through OPS.10.1. OPS.12 supplies the human capability, fatigue, rest and relief conditions that the allocation must preserve.

OPS.8.2:4.2 - Choose a unit that can yield the required resources

Identify a useful auxiliary contribution and its actual execution conditions. Preparation, learning, research, an improvement trial and an ordinary lower-priority job can all qualify. Compare the particular unit that can be stopped or completed and the resources it must release.

For that unit, establish how progress and resources can be released:

Auxiliary arrangementWhat must be established
Finish before a known protected startThe unit, cleanup and restoration fit the available calendars before that start.
Pause and resume laterA permissible stopping point can be reached; the needed resources are released; sufficient state remains for resumption.
Abandon and later restartAbandonment is permissible, resources can be recovered in time, and lost work and any remaining effects are included in the choice.
Transfer the auxiliary workA capable recipient is available, the handover fits, and the transfer does not consume another resource needed by the protected service.

For human work, a short note of the current state, next step and unresolved difficulty can reduce later reconstruction when that information would otherwise be lost. Use the existing work materials when adequate. Include the time to leave that note and the effort of repeated transitions.

For equipment, recover the work needed to leave a usable state: for example completing an indivisible cycle, removing material, cleaning or restoring a fixture. For computing, distinguish pausing execution from releasing the memory, accelerator, license or other allocation the protected job needs. A saved computation can help auxiliary resumption without itself preparing the protected job.

Retain effects outside the suspended activity. Stopping an AI computation does not undo a request it already sent to a person or another service. Establish what has occurred before deciding how to resume or repeat that activity.

OPS.8.2:4.3 - Construct the return to protected work

Starting from a possible call, follow the actual operations until the protected resource is ready. Include detection, remaining work before a permissible interruption, preservation or disposal of auxiliary work, resource release, movement or handover, and restoration of the protected configuration or context.

For a simple serial return with immediately available supporting resources, the elapsed time is:

return delay = detection delay + remaining time to interruption + release time + transfer time + protected-work restoration time.

Use each duration once. For example, a stop procedure that already saves and releases the auxiliary state does not need a second saving allowance.

Where operations can overlap or must wait for a person, tool or calendar window, construct their precedence and resource placement through OPS.10.2. Adding durations alone then does not determine the return time. End the schedule when the protected work is ready to start. Include any restoration still required after a pause or transfer.

Compare the resulting readiness with the protected requirement. For an anytime-call claim, cover the states in which the auxiliary work may be interrupted, including its longest indivisible segment and consequential calls during setup. For a known-time requirement, place completion and restoration before that time. Keep the information available when each decision must be made; an arrangement cannot choose the right auxiliary start using a later call’s timing.

Use a bound, a finite set of scenarios or a joint probability model according to the service question. A typical transition time does not establish a maximum or a percentile. OPS.10.1 supplies the corresponding uncertain-capacity comparison. If a material duration remains unknown, retain what the comparison does establish and decide whether obtaining a better estimate could justify or change the choice enough to warrant the work.

Finally, check that the returned resources can perform the protected work for its required duration. If the arrangement fails, change the auxiliary unit, preparation, recall timing or supporting allocation, or leave this capacity available. Spending some protection is a different operating choice that requires reconsidering the affected commitment through OPS.7 or OPS.13.

OPS.8.2:4.4 - Compare useful gain with the whole interruption cost

Compare feasible auxiliary candidates with leaving the interval unused. Retain the result each candidate could supply and the work needed to obtain it, including preparation, interruptions, lost partial progress, later auxiliary resumption and any new obligations.

An already-paid salary does not make those consequences vanish. Use OPS.14 when the choice or its economic justification depends on the financial comparison. Use OPS.12 when repeated transitions can impair continuing human service. Observe a trial through OPS.16 or A.3.1.WT when an unresolved operating effect justifies one; do not demand a new experiment when the available comparison already settles the choice.

If development is the intended gain, C.40.OI and C.40.DC construct the opportunity and transition. For a human capability goal, use HCD.2 to arrange the required practice, feedback and support. Establish any gained capability from the learner’s performance. An interruptible activity can fit the reserve and still teach little. C.39.MF and A.3.1.WT support a method-improvement question and its trial. Use the development results to assess the intended gain. Check its compatibility with the operation by calculating the full return to protected service.

Choose the simplest adequate arrangement. The choice may favor a short useful unit, preparation outside the protected resource, another resource, a later window or continued availability.

OPS.8.2:4.5 - Operate the start, recall and resumption conditions

Before starting, establish that the protected service is covered under the selected conditions, the auxiliary unit can use the interval, and the recall or finish signal will reach the performer or controller in time. The existing queue and work instructions can carry the arrangement.

On recall, execute the selected interruption and restoration, then start the protected action when its inputs are ready. If the supporting resource or restoration condition has changed, use the corresponding alternative or revise the affected commitment; repeating the old timing estimate cannot restore availability.

When protected work permits auxiliary resumption, recover its actual state and any changes that occurred during the interruption. Continue from a still-valid checkpoint, revise the plan, restart or discard the unit according to the chosen arrangement. Preserve already incurred work and effects in that decision.

Reopen the arrangement when call timing, service demand, resource access, capability, auxiliary stopping behavior, restoration or repeated interruption costs change. Stop elaborating once the operation has a usable choice under the conditions it needs to protect.

OPS.8.2:5 - Archetypal Grounding

OPS.8.2:5.1 - Practice during an operator’s reserve interval

An already-qualified operator has a 45-minute interval during which a call can require a return to protected service within five minutes. Once back, the operator and required equipment can sustain that service. A proposed practice exercise uses an independent training setup and can be stopped at short points.

The constructed timing assumptions are maximum durations under this arrangement:

Return operationMinutes
Detect the call1
Reach a stopping point and leave the needed resumption note1
Move to the protected workstation1
Recover its current situation and prepare the next action2
Total, with these operations serial and no additional waiting5

This exercise fits the stated response requirement. The calculation does not establish its learning value; its practice and feedback still need to serve the selected development question.

A live lesson with a 25-minute segment that cannot be left can exceed the entire five-minute allowance before transfer or restoration begins. Its fit within the 45-minute interval does not make it suitable for this anytime-call protection.

Now change the workstation’s restoration to five minutes. The former exercise gives 1 + 1 + 1 + 5 = 8 minutes and no longer preserves the response. Preparing a usable handover in advance might reduce restoration, but that is a changed arrangement whose time and burden must be included. Otherwise choose another activity or preserve readiness.

OPS.8.2:5.2 - A free machine but an unavailable setter

A machine must be ready for its protected job at 09:30. There is no earlier-call requirement in this case. An auxiliary trial needs five minutes of setup by a setter, twenty minutes of unattended machine time and five minutes of restoration by that setter. The setter is available from 09:00 to 09:20 and then from 09:40. The protected job’s operator is available at 09:30.

The durations total thirty minutes. Setup at 09:00–09:05 and running at 09:05–09:25 leave restoration waiting until 09:40–09:45. The trial does not fit the protected start.

If a separately useful ten-minute trial is available, setup at 09:00–09:05, running at 09:05–09:15 and restoration at 09:15–09:20 fit both calendars. The machine is ready before 09:30. Alternatively, prepare a different unit or obtain another qualified setter; merely labeling the trial low priority changes none of these times.

This arrangement protects the named start. It has not established immediate recall during the trial’s indivisible machine cycle.

OPS.8.2:5.3 - Suspending a background AI job leaves its accelerator occupied

A protected computation needs an accelerator and its memory. A background job uses that allocation while the protected queue is empty. The scheduler can suspend the job’s execution, but under this configuration suspension retains the accelerator allocation. Starting the protected job requires that allocation to be released.

A “suspend on arrival” rule therefore fails to provide the needed resource even if the suspension command is immediate. For example, Slurm’s generic-resource documentation states that resources allocated to a suspended job remain unavailable to other jobs. Use a release mechanism supported by the actual application and scheduler, such as checkpointing followed by termination and later restart.

For a constructed alternative, allow one minute to receive the call, checkpoint and terminate; one minute to release and clean up the allocation; and one minute to load the protected computation. With those serial bounds and resources available, the three-minute return fits a three-minute start requirement. The protected computation’s subsequent capacity needs are also assumed to fit.

An extra cleanup wait breaks that bound. Keeping the allocation free may then be the usable choice. Separately retain the cost of restarting the auxiliary computation and any external actions that its earlier execution already caused.

OPS.8.2:6 - Bias-Annotation

A utilization display makes idle time conspicuous while the protection it supplies may be invisible. Conversely, a label such as “reserve” can discourage useful work even when its full return fits the service requirement.

A successful short return can hide later costs. Repeated interruption may waste auxiliary progress, exhaust a person or occupy supporting resources. Assess the protected service and the auxiliary result over the relevant interval, including the costs of interruptions.

OPS.8.2:7 - Conformance Checklist

  • The protected work has a recognizable readiness condition, response or start requirement, and sufficient continuing service.
  • The auxiliary unit has a usable completion, interruption, transfer or abandonment mechanism.
  • The return includes consequential resource release, supporting calendars and restoration.
  • The claimed protection covers the relevant call times and auxiliary states under the selected bound, scenario or probability model.
  • Auxiliary benefit is compared with transition, restart and continuing-service costs.
  • The decision to suspend or resume accounts for commitments already made and external effects already produced.
  • A changed return condition can change the start or recall decision.

OPS.8.2:8 - Common Anti-Patterns and How to Avoid Them

MistakeWhat failsRepair
Filling every idle intervalProtection disappears when the call arrives.Recover the protected service and fit the whole return before promising the interval.
Treating priority as interruptibilityAn indivisible operation or retained allocation prevents recall.Identify the actual stopping and resource-release mechanism.
Ending the calculation at “paused”Travel, cleanup or restoration delays readiness.Calculate through the first ready protected action.
Fitting duration without fitting calendarsA needed setter or handover participant is unavailable.Place return operations with their required resources.
Treating an easy-to-stop lesson as capability gainedAn operating fit substitutes for practice and transfer.Retain HCD’s learning and capability question separately.
Counting only the first successful returnRepeated transitions damage auxiliary progress or sustained service.Compare the whole relevant operating interval and its actual burden.

OPS.8.2:9 - Consequences

Useful preparation and development can occupy otherwise idle intervals without spending the selected protection.

The construction can also justify leaving an interval empty. It exposes which change would make another use feasible: a smaller auxiliary unit, earlier preparation, a different resource, faster restoration or a revised service commitment.

OPS.8.2:10 - Architectural Rationale

Protective capacity is useful through the work it can perform when needed. Its availability depends on capability, timing, location, access and state. The same idle machine or person can therefore be available for one protected service and unavailable for another.

The auxiliary unit, its interruption and the restoration form one operating construction. Keeping them together prevents an attractive auxiliary result from hiding the work needed to resume service. Preserving the auxiliary state and restoring the protected state remain separate contributions.

The method uses ordinary scheduling and capacity comparisons for the return. Its particular contribution is selecting and operating auxiliary work around that return, including the effects that remain after interruption.

OPS.8.2:11 - SoTA-Echoing

The selected approach compares a complete return with the protected service, then evaluates the auxiliary contribution and its burden. Simpler alternatives remain useful: keep the resource ready, or use only capacity established as excess to protection. Temporarily occupying protective capacity needs the additional construction in sections 4.2–4.5.

Steve Tendon, The Book of TameFlow (2022), printed pp. 226–229, distinguishes productive, protective and excess capacity and uses excess capacity for preparation and development. Adopt that distinction. Applying it to temporary use of the reserve adds an explicit interruption and restoration construction; the source’s use of excess capacity does not itself establish that permission. Its fixed-expense argument also leaves transition burden, consumables, lost alternatives and changed service consequences to the receiving comparison.

Hopp and Spearman, Factory Physics, third edition, §4.4.3 and §§7.4.2–7.4.3, supplies two ways to preserve capacity: move eligible preparation outside machine downtime, and use already-capable workers where work needs them. The simple worker-transfer equivalence assumes no handoff delay. Adapt preparation and transfer to the actual return calendars in 4.2–4.3 and identify whether the transferred worker is already capable and how long the handover actually takes.

Van Zoonen and Scharp, Managing Daily Work Intrusions (2025), describes a ready-to-resume planning intervention. Adopt the small state-and-continuation aid when it reduces reconstruction. Their field study reports reduced attention residue alongside increased general exhaustion, so include the intervention’s burden and do not infer a universal response-time benefit. Sections 4.2 and 4.4 keep those two effects in the choice.

The Slurm documentation makes computational resource release concrete: suspension can retain memory and licenses, and generic resources remain allocated to suspended jobs. Requeueing restarts the batch script, so application recovery must be supplied separately. Backfill scheduling protects expected starts using runtime limits; that is a different timing requirement from an unknown call. Prolog and epilog behavior adds real preparation, cleanup and failure conditions. Adapt these mechanisms to the selected configuration rather than inferring released capacity from a generic pause command.

Reopen the arrangement when a different auxiliary unit or return mechanism improves useful service at acceptable cost, or when call timing, allocations, interruption behavior or restoration changes.

OPS.8.2:12 - Relations

Use OPS.8 to establish the purpose and amount of protection. OPS.5 applies a start rule; OPS.7 and OPS.13 handle an incompatible priority or commitment. OPS.8.1 treats earlier work that can return after a release; this method treats the auxiliary work occupying resources needed for protection.

OPS.10.1 supplies capacity and uncertainty comparisons; OPS.10.2 places interruption and restoration with precedence and calendars. OPS.11.1 recovers the operating arrangement, and OPS.15.1 keeps occupancy and waiting intervals distinct.

Use OPS.12 for human capability and workload conditions, OPS.14 for the financial comparison and OPS.16 for an operating trial. C.40.OI and C.40.DC guide the development choice. For human learning, HCD.2 guides arranging practice and feedback. C.39.MF and A.3.1.WT guide a method trial when that is the proposed auxiliary work.

C.11 supports the choice between useful gain, retained protection and unresolved risk. MMP.10 and CMP supply the constraint and obtaining methods used by the scheduling contribution when the simple comparison no longer suffices.

OPS.8.2:End

OPS.9 - Diagnose and Treat the Current Operating Constraint

Status: Stable

OPS.9:0 - Use This When

Use this Method when an operation is not producing its accepted result as required and someone proposes to remove a bottleneck, increase capacity, automate a step or accelerate a team. The question is which relation currently limits completion, and what, if any, treatment the evidence supports.

The first useful result is a bounded constraint account: the lost result and observation window, relevant observations, the supported limiting relation or still-live explanations, and a treatment, hold or precise inquiry. Compare a serious rival if it fits the observations and distinguishing it could affect the treatment or the grounds for the required diagnosis. The result can conclude that a proposed resource addition is unsupported while specifying a useful readiness or measurement action.

Use OPS.8 when a queue policy can be repaired without settling a wider constraint claim. Use OPS.10 when the immediate question is a load/capacity/service comparison with an already adequate causal basis. A safety, clinical, engineering or financial diagnosis remains with the qualified practice that supplies it.

OPS.9:1 - Problem frame

A queue can be long because service capacity is scarce, inputs arrive in bursts, prerequisites are incomplete, acceptance is delayed, or earlier defects return as rework. Several of these conditions can occur together. A resource may be idle for much of a week and still constrain a short critical window.

Here a current constraint is a supported limiting relation for one operating result under a stated arrangement and horizon. It can concern usable capacity, readiness, sequence, quality, access, a decision or another condition. A bottleneck identified from machine or staff utilization still needs this connection to the result and horizon.

OPS.9:2 - Problem

Local speed and utilization are easy to observe. The causal relation to accepted operating results is harder. An improvement can halve touch time while leaving completion unchanged because work still waits for acceptance, a complementary input or another resource.

The opposite error demands a complete causal model before making any useful decision. A small feasibility bound, a discriminating observation or a reversible probe can sometimes rule out a proposed treatment at much lower effort.

OPS.9:3 - Forces

ForcePractical tension
urgent treatment and adequate diagnosisDelay can be costly, but the wrong treatment consumes resources and can move congestion elsewhere.
one focal constraint and distributed delayFocusing effort helps, while several short waits or alternating regimes can defeat one-resource explanations.
local measures and accepted resultsTouch time, busy time and queue length can change without changing what the operation delivers.
useful probes and protected conditionsA probe can discriminate explanations only while preserving the relevant professional, acceptance and comparison conditions.
learning and migrationA useful treatment changes the arrangement; its success can make the former constraint cease to be current.

OPS.9:4 - Solution

OPS.9:4.1 - Fix the result and the shortfall

Name the operating result, its accepted unit, demand or commitment being compared, relevant subjects, horizon and acceptance criteria. Reuse current OPS.1–OPS.4 inputs where they fit. Distinguish accepted demand, service attempts and accepted results; a failed test or reopened case can consume capacity without adding a result.

State the shortfall in terms that matter to the question, such as fewer accepted results, unacceptable time to result, missed qualified service conditions, or another explicit operating consequence. Preserve the result definition and case mix in later comparisons. A changed definition reopens the account rather than silently improving the metric.

OPS.9:4.2 - Reconstruct where completion is lost

Follow representative matters through the relevant services and joins. Recover entry, eligibility, start, completion, return and acceptance events. Distinguish the processing, setup, starvation, blocking, unavailability or rework that bears on the shortfall.

Use the event sequence and the resource calendar together. A snapshot identifies a population at one time; it does not explain a week of waiting. A utilization average can hide a critical peak. Before interpreting a rate, identify missing events and how they limit the inference about the cause.

If the result is delayed by many small waits, inspect cadence, handoff and decision timing across the path and identify the waits that can accumulate.

Choose the time question before choosing the bottleneck measure. Sustained accepted output, the first accepted result by a deadline and the elapsed wait of a particular case can have different useful treatments. For accumulated delay, sum the actual waits along the consequential path and identify which can be removed together without merely moving work into another queue. A nonlimiting resource can still govern a first-result deadline; a faster sustained pace need not produce that first result sooner.

OPS.9:4.3 - State the mechanism and resolve live alternatives

Express the candidate explanation as a relation: “Under this demand and access pattern, the final test cannot process the required eligible load before the horizon,” or “Late prerequisite delivery leaves the booked rig without eligible packages.”

Consider alternatives that could fit the available observations and matter to the requested diagnosis or treatment. Examples are insufficient usable rig time versus incomplete kits; scarce acceptance effort versus evidence repeatedly missing at acceptance; or slow processing versus arrivals concentrated near the deadline. Keep only those still plausible under the current grounds. A supported bound or directly established condition can settle the bounded question without constructing another rival.

If the available observations fit more than one explanation, state what they establish and which causes remain possible. When the question requires further discrimination, identify what result would count against each explanation and whether a distinguishing observation can be obtained. If it is unavailable, report that limit and use any treatment or hold already justified.

OPS.9:4.4 - Obtain the least burdensome discriminating basis

Select the basis appropriate to the claim and decision:

  • A resource/precedence bound can establish infeasibility under explicit demand, capability, calendar and acceptance assumptions. Show a feasible schedule as well when claiming that a proposed treatment makes the result achievable.
  • Event-history replay can reveal starvation, blocking, rework and timing relations. Its observational explanation remains limited by event quality and unobserved conditions.
  • A bounded field probe changes one consequential mechanism under the applicable professional Method and permission. State the comparison cases or windows, preserved conditions, interference, expected observations and stopping rule.
  • A specialist causal or scheduling analysis is warranted when uncertainty, confounding or coupled behavior could alter a consequential treatment or the grounds for the diagnosis, and simpler evidence is insufficient.

For a probe, keep the same accepted-result criteria and record demand, mix, resource availability and consequential conditions. Shared queues or common providers can affect nominal comparison cases too. Use an appropriate time-blocked, matched or other justified comparison; a convenient before/after label does not remove interference or confounding.

Current FPF C.16 governs the measurement chain and C.28 governs what causal use the basis supports. For the proposed use, identify the measurements or observations and their professional basis. Use a suitable existing result or obtain the missing evidence if the judgement requires it.

When a utilization ranking leaves the diagnosis unresolved, compare feasible ways of investigating the limiting mechanism. Active-period analysis can expose shifting production bottlenecks from a qualified history of machine states; sensitivity analysis can compare throughput response under a validated model. Obtain their actual state definitions, time resolution, observation window and performance criterion before interpreting the result. Price instrumentation, event reconciliation, missing/censored intervals, implementation and validation, as well as continuing observation. A five-job feasibility bound may settle a fixed deadline without any of that apparatus. Repeated regime changes that make one aggregate ranking misleading can justify it. Use the diagnostic result to identify a possible treatment or a useful probe. To claim an effect of the proposed investment, establish its consequences at the relevant operating boundary.

OPS.9:4.5 - Compare treatments from the current arrangement

If a treatment decision remains, compare the current arrangement with a feasible change that acts on the supported mechanism. Candidate treatments include protecting usable constraint time, changing release or dispatch, completing prerequisites earlier, reducing avoidable setup or rework, obtaining capacity, or changing a domain Method.

Account for implementation effort, transition loss, displaced work, downstream congestion, affected commitments and reversibility. Use C.11.CRC for the finite comparison and C.11 for the choice when several admissible alternatives remain.

A treatment is supported only to the scope of the evidence. A deterministic scenario can show feasibility; it does not establish actual field effectiveness. A probe can support a bounded effect without showing that the same treatment remains useful under another demand regime.

OPS.9:4.6 - Return the decision and remeasure

Return the result definition and window, observations, supported explanation or unresolved rival, basis and limits, any selected treatment, probe or hold, the authority for that decision, the affected uses and any observation that would reopen the conclusion.

After a treatment, inspect the accepted result and the actual load, waiting, quality and resource consequences. Reopen when demand, mix, eligibility, access, acceptance, recovery or a coupled structure changes. If another condition now limits completion, direct the next improvement decision to that condition.

OPS.9:5 - Archetypal Grounding

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 diagnosis identifies what was observed, what might explain it and what to do next.

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.

OPS.9:5.2 - A narrow capacity treatment with a feasible witness

A different constructed service must finish five ready jobs within twelve hours. All upstream inputs are complete. Each job requires two hours of final verification and then ten minutes of certification; the certificate service has reserved slots after each possible verification completion. Acceptance requires both results, with no failures or rework in this stated scenario.

The verifier is available for eight hours. Verification completions occur at hours 2, 4, 6 and 8, so no more than four jobs can be accepted. Extra upstream processing capacity cannot change that bound: the five inputs are already ready.

The resource owner can supply two additional verifier-hours within the same twelve-hour horizon. With that change, the fifth verification completes at hour 10 and certification at hour 10 plus ten minutes. The comparison therefore returns a feasible five-job treatment candidate under the stated conditions. Its selection still uses the supplied resource cost, permission and protected consequences.

If certification availability later falls to two reserved slots, the old verifier treatment no longer supports five accepted jobs. The same result definition now exposes another limiting relation. Adding further verifier time cannot repair that missing certification capacity.

OPS.9:5.3 - Faster automation without more accepted cases

An operation automates a repeatable step and halves its touch time, but the same accepted-case rate remains. The practitioner keeps the accepted-case criteria, mix and observation window fixed and inspects waiting and returns at acceptance.

Two possible causes are insufficient acceptance capacity and repeated gaps in the evidence presented for acceptance. Hiring more acceptors addresses the first. Completing the evidence before presenting the case addresses the second. If a diagnosis or treatment choice depends on their contributions, use the least burdensome comparison that can establish them. A faster automated step alone establishes neither cause.

OPS.9:5.4 - The first result and sustained output choose different changes

Three independent serial resources A, B and C take 3, 5 and 2 hours per job. Inputs are ready at 0; transfers are immediate; buffers and downstream acceptance do not restrict this constructed deterministic case. A job is accepted only after C. The first completion is at 10; subsequent completions are five hours apart, so the fifth is at 30.

Two qualified arrangements are available before the window. An upstream fixture reduces A to 2 hours, leaving 5 and 2 elsewhere. Alternatively, moving qualified assistance from C to B produces durations 3, 4 and 4. Each has supplied permission and preserves the same accepted result; the move’s slower C is part of its actual cost, not an omitted side effect.

ArrangementFirst accepted resultFifth accepted resultPreparation burden outside the service window
Current 3/5/21030none
Upstream fixture 2/5/2929two qualified staff-hours, with a reversible fixture change
Reassigned assistance 3/4/41127three staff-hours of preparation and a changed C assignment

For one accepted result due by 9, select the fixture if its preparation can actually be supplied without displacing protected work. It changes the deadline result although B still limits the sustained pace. If the receiving requirement changes to five results by 28, that fixture is insufficient and the reassigned arrangement supplies a feasible alternative. A financial ranking needs the comparative costs. A probability of timely service needs evidence beyond these fixed durations.

Accumulated waits can make another noncapacity treatment useful. Add four evidenced 15-minute handoff waits before acceptance of the first current job: it now finishes at 11. A coordinated handoff arrangement that removes those four waits returns completion to 10 without changing B’s five-hour rate. If the required first-result deadline is 10 and the supplied coordination/cover burden is half a staff-hour outside the service window, this can be preferable to the two-hour fixture preparation. If a wait is instead required for a qualified acceptance observation, it is not removable by dispatch policy; retain it and redo the comparison. The useful intervention follows the actual path and permissible waits, not the label “nonconstraint.”

OPS.9:5.5 - Choose diagnostic effort for a changing production regime

The fixed five-job case in :5.2 needs durations, readiness and reserved calendars. Those inputs already prove that eight verifier-hours cannot supply ten required hours. A new continuous machine-state feed would not improve that conclusion. Reuse the bound and its feasible extension.

A recurring production service instead alternates its limiting behavior. The question is where movable qualified assistance could help accepted output in each regime. A competent event-history account identifies jobs, accepted outputs and losses, but its weekly totals do not distinguish the shifting intervals. The supplied instrumentation can recover complete active intervals for machines A and B using a specialist-confirmed active/passive definition, including how blocking, starvation and unavailable states are classified. That definition, synchronized times and observed interval ends are prerequisites; a generic “busy” field is insufficient.

In a small constructed diagnostic return, A’s complete active interval is 0–6 and B’s is 4–10, with no other active intervals in that ten-hour window. Both have six-hour durations. The active-period analysis returns A alone over 0–4, shared/shifting involvement over 4–6 and B alone over 6–10. Each is involved for six of ten hours; the two 60% figures include the same overlap and must not be normalized into a single winner. These are descriptive shares of this trace, not confidence levels or a forecast for next week.

The analyst needs two hours to qualify and align the existing events, three to implement and check the duration-based analysis, and fifteen minutes per shift to examine missing states and the operating return. These are supplied local effort estimates. They are worth comparing with the cost of a permanent one-machine intervention and with a simpler manual replay if shifts are rare. If the treatment decision calls for a probe, use the identified intervals to design a permitted test of assistance in the relevant regime. Inspect accepted output, quality and interference. Do not buy permanent extra A capacity from an equal weekly total or from the diagnostic label alone. A model-based sensitivity study becomes the stronger supplier when a proposed finite change alters both machines and their buffers; it must represent that coupling and the relevant regime, rather than extrapolate a local derivative into the whole investment effect.

OPS.9:6 - Bias-Annotation

BiasHow it misdirects treatmentCountermeasure
busy-resource attributionHigh utilization becomes the causal explanation.Relate usable capacity and timing to the accepted-result shortfall.
queue-length attributionVisible waiting is treated as sufficient proof of the constraint.Check eligibility, arrivals and returns. Examine a rival explanation when it fits the evidence and matters to the diagnosis.
preferred-solution biasAutomation, hiring or acquisition is selected before diagnosis.Identify what would defeat the proposed explanation. If a different mechanism remains plausible and material, compare the treatment it would require.
before/after confidenceCoincident changes are attributed to the intervention.Preserve comparison conditions and account for interference and confounding.
permanent-bottleneck identityAttention remains on a resource after conditions change.Remeasure the current limiting relation and accepted result.

OPS.9:7 - Conformance Checklist

  1. Are the accepted result and shortfall defined for the relevant population and horizon?
  2. Which limiting mechanisms do the observations distinguish, and which remain open?
  3. Where rival explanations matter to the required conclusion or treatment, are they resolved or is the remaining question identifiable?
  4. Does the selected bound, replay, probe or specialist analysis support the claim actually made?
  5. For a selected treatment, does it act on that mechanism and include consequential interactions and transition costs?
  6. Can participants act on the treatment, hold or exact probe request and recognize when it must reopen?

These questions help readers interpret the diagnosis and any decision based on it. For reliance, check the quality of the observations, the validity of any comparison, the professional premises and the relevant authority.

OPS.9:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Every operation has one permanently named bottleneck.Distributed delay and changing regimes are excluded before observation.State the result-relative limiting relation and allow unresolved or multiple mechanisms.
A fast local step proves whole-operation improvement.Acceptance, joins and rework may dominate the result.Preserve the accepted unit and inspect the whole relevant path.
A capacity ratio is a feasible schedule.Precedence, access and simultaneous-resource conditions can defeat it.Supply the timed witness or retain an infeasibility bound only.
A generic causal checklist replaces the field probe.No actual admissible change or observation is specified.Name the professional Method, changed action, comparison and stop.
A successful treatment remains the answer forever.The arrangement and limiting relation have changed.Reopen the account after the material change.

OPS.9:9 - Consequences

Effort can be directed to a mechanism that affects accepted results. An exact “not yet justified” treatment decision can prevent waste while leaving a cheap useful policy or probe available.

The cost is some additional measurement and comparison discipline. The appropriate depth depends on the consequence of error: a reversible readiness trial and a major capacity acquisition need not carry the same evidence burden.

OPS.9:10 - Rationale

A constraint claim connects an arrangement to an operating result. Its meaning therefore depends on demand, acceptance, time and complementary resources. A resource label cannot retain that meaning when those conditions change.

Identifying what limits completion and deciding whether a particular treatment will help require different grounds. Retaining a live alternative and the evidence limit permits action at the smallest justified scope; a sufficient bound or established condition can finish the current decision.

OPS.9:11 - SoTA-Echoing

Practice question and selected lineSerious alternative, trade-off and pattern changeSource roles, limits and reopen condition
What should be treated when local speed does not improve accepted output? Adapt result-relative diagnosis followed by mechanism-specific treatment.Constraint-focused improvement is useful, but a forced single-resource answer can miss many waits or incomplete inputs. Sections 4.1–4.3 and 5.1/5.3 preserve the accepted result and compare a serious rival when the available grounds leave one live. Further examination of events is worthwhile if it can change the choice or substantiate a consequential diagnosis at a justified cost.Tendon, The Book of TameFlow (2022), constraint and complete-kit reasoning, is a mechanism candidate. Reinertsen, The Principles of Product Development Flow (2009), E8, explains how many small waits can accumulate. Use evidence from the operation to establish which mechanisms contribute and how. Reopen for a different waiting mechanism or demand regime.
How much evidence is enough before acting? Adapt the least burdensome bound, replay or admissible probe sufficient for the operating question. Compare live alternatives when their differences matter to the conclusion.Pure utilization ranking is cheaper but cannot support the causal move; a complete optimizer or experiment is unnecessarily costly for some bounded decisions. Sections 4.4–4.6 and 5.2 separate infeasibility, feasible scenario and actual effect.Current FPF C.16 and C.28 supply measurement and causal-use discipline; C.11.CRC supplies finite comparison. The professional operational data, probe and authority remain case inputs. Reopen when confounding, interference or consequence makes the selected basis insufficient.
Should the former constraint keep receiving improvement effort? Adopt remeasurement of the accepted result and current arrangement after change.A fixed improvement programme can keep optimizing a relation that no longer limits completion. Section 4.6 and the changed certification case make migration observable at modest extra comparison effort.The constraint-refocusing line in Tendon and the changing-information reasoning in Reinertsen suggest mechanisms to examine against the accepted result after a change. Reopen if the result, acceptance conditions or connected resources change.

The first-result/steady-pace distinction in :5.4 adapts the deterministic timing comparison in TameFlow (2022), printed p.92, and Reinertsen’s E8 accumulated-wait argument. It rejects the stronger claim that only the sustained-throughput constraint can be worth improving: a finite deadline is a different receiving result, and removing waits has a real coordination cost.

For the diagnostic choice in :4.4/:5.5, Roser et al. (2021), §§2–3, supplies a capable active-period method and duration-aware matrix construction. Its author manuscript makes state preparation and irregular timestamp handling explicit. When the timing of the changing constraint matters, use active-period analysis if the state meanings and observation effort support it. The intervals can identify involvement in that constraint. A claim about the effect of a treatment requires separate evidence. Calvo (2026), §5, compares throughput-oriented state, queue and sensitivity criteria under a serial-line model. It is a serious modeled alternative, not evidence that its steady-regime selection solves a finite deadline or arbitrary changing service. Reopen when the performance criterion, state coverage, coupling or regime makes the cheaper diagnosis insufficient.

OPS.9:12 - Relations

OPS.1–OPS.4 supply matching operating focus, subject identities and current observations. OPS.8 supplies relevant queue, readiness and buffer policy; OPS.10 supplies usable-capacity and service comparisons; OPS.11 exposes couplings that can sustain or move a limiting relation.

OPS.5–OPS.7 consume supported operating-policy consequences under their own admission, continuation, priority and commitment authority. A domain Method change returns to its owner. OPS.16 is available for the separate local operating-Method-improvement question but is not a prerequisite for diagnosing the current constraint.

Current FPF C.16, C.27.TA/C.27, C.28, C.11.CRC and C.11 govern measurement, temporal and causal claims, finite contribution and choice. Use a qualified clinical, engineering, safety, labor or financial source when the operational conclusion depends on such a diagnosis.

OPS.9:End