Operations Management Principles Framework
DocID: OPS within FPF Library.
A domain pattern language for understanding, arranging and managing continuing production and service, and for improving the ways that obtain their results.
- Author: Anatoly Levenchuk, with AI-assisted development and review
- Version: 27 October 2026
- Status: Eternal alpha: the current Methods can be used for their stated operating questions and conditions; the framework continues to develop as practice and evidence change.
- License: CC BY 4.0 for original framework content; third-party material retains its own terms.
- Publication: FPF Library repository
Start with the Readme for a working difficulty or the Table of Contents for a familiar question or PatternID. Open the smallest useful pattern, reuse current matching inputs and stop at its sufficient result. For references to this version, use the Citation.
Table of Contents
Use the Readme for worked connections across several operating questions. Use this Table of Contents to find an individual method by difficulty, needed result or PatternID. Each method explains how to do the work, what its evidence supports and when the result is sufficient.
OPS.* is this framework’s PatternID namespace. Numbers are stable addresses; the Parts give reader order and do not prescribe Work order.
Public units
| Unit | Reader use |
|---|---|
| Operations Management Principles Framework Readme | Connect readiness, capacity, commitments, service results and changes to operating practice; follow the consequences of a changed condition. |
| Operations Management Principles Framework Architectural Reference | Understand how results, operating units, dependencies and resources give rise to an operating arrangement; connect knowledge, management, performance and improvement. |
| OPS.Reference:1 | Start from a difficulty in continuing operation; recover the discipline through results, units, relations, knowledge and change |
| OPS.Reference:2 | Competing demands on one operation |
| OPS.Reference:3 | Work, descriptions, structures, and records remain distinct |
| OPS.Reference:4 | Demand, commitments, subjects, and units remain distinct |
| OPS.Reference:5 | Several management views can coexist on the same Work |
| OPS.Reference:6 | Shared attention is stronger than visibility and weaker than consensus |
| OPS.Reference:7 | The control branch is conditional |
| OPS.Reference:8 | Pattern relations do not prescribe an operating lifecycle |
| OPS.Reference:9 | Use the Methods together where their results meet |
| OPS.Reference:10 | Conditions on a whole combination |
| OPS.Reference:10.1 | Operational mantra: connect local work to accepted results |
| OPS.Reference:11 | Check the combined decision and its result |
| OPS.Reference:12 | Architectural Rationale |
| OPS.Reference:13 | Apply the repertoire in production and service settings |
| OPS.Reference:14 | Gains, burden and limits of combined use |
| OPS.Reference:15 | What this publication covers and leaves outside |
| OPS.Reference:16 | Intended use and ordinary non-use |
| OPS.Reference:17 | PatternID and reader order |
| OPS.Reference:18 | Practical entry forms |
| OPS.Reference:19 | Source use and shared architectural choices |
| OPS.Reference:19.1 | Operating aims and performance sources |
| OPS.Reference:19.2 | Shared source choices for the repertoire |
| OPS.Reference:19.3 | Grounds for the disciplinary account |
| OPS.Reference:20 | FPF dependency and compatibility |
| OPS.Reference:21 | Sibling-domain returns and availability |
| OPS.Reference:22 | Available contributions |
| OPS.Reference:23 | Representative case coverage |
| OPS.Reference:24 | Edition return |
| OPS.Reference:25 | Publication boundary |
| OPS.Sources:1 | Bibliographic returns for shared sources |
| OPS.Sources:2 | Citation |
| OPS.Application - Cross-Pattern Application | Follow PumpWorks, public-hospital and AI-assisted cases through local coordination, human conditions, service commitments, operating consequences, accounts, Method improvement, quality responses, simultaneous Work and cultural continuation. |
| Operations Management Principles Framework Sources and Edition Notes | Find the consulted editions of shared sources and the citation for this publication. |
Part I — Bound the Operation and Select Coordination Views
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 1 | OPS.23 - Connect Operational Reasoning — The Operational Mantra | Stable | How do local work, accepted results, resources and receiving conditions fit together, and what does a changed answer reopen? | OPS.1; relevant OPS.3–OPS.22; FPF A.1.STM |
| 2 | OPS.1 - Identify the Operating System, Commitments, and Flow Units | Stable | Which operation, commitments, subjects and units matter to this decision? | FPF A.1.SCR, A.6.REL, C.2.1, A.10 |
| 3 | OPS.2 - Select Work-Management Views and Coordination Methods | Stable | Which project, process, case, queueing, control, or mixed views and coordination Methods answer the current questions? | OPS.1; FPF A.22, C.29; conditional C.30.LCA, B.2.5, C.27.TA |
Part II — Recover Operating Subjects and Maintain Current State
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 4 | OPS.3 - Distinguish Operating Subjects, Cases, Queues, Resources, and Records | Stable | Which subjects and relations do you need to distinguish in the cases, Work items, queues, resources, events, and records? | OPS.1, OPS.2; FPF A.6.REL, C.2.1; conditional B.2.5 |
| 5 | OPS.4 - Keep Current Operating State Recoverable Across Participants | Stable | Which qualified current claims let named participants decide, resume, and coordinate? | OPS.2, OPS.3; FPF C.2.1, A.10, A.15.8; conditional C.30.LCA |
Part III — Admit Demand and Continue Cases
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 6 | OPS.5 - Admit Work and Limit Starts | Stable | Which eligible work may the decision holder admit now, under what start conditions, and what demand remains? | OPS.2, OPS.3, OPS.4; FPF C.11, A.10 |
| 7 | OPS.6 - Continue Cases and Handle Exceptions | Stable | What Work may happen next in this admitted case, and what evidence supports progression? | OPS.5; FPF A.15.7, C.11, A.10 |
Part IV — Revise Priority and Existing Commitments
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 8 | OPS.7 - Manage Aging, Urgency, and Service Commitments | Stable | Do timing or consequences warrant revising the present priority or an existing commitment? | OPS.6 evidence; FPF C.27.TA; conditional C.27, C.11 |
Part V — Coordinate Queues and Treat the Current Constraint
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 9 | OPS.8 - Coordinate Queues and Buffers | Stable | What is ready for which service, and what should release and protection policy control? | OPS.3, OPS.4; conditional OPS.9–OPS.11; FPF C.16, A.22, E.18 |
| 10 | OPS.8.1 - Choose Work-Release Rules When Earlier Work Can Return | Stable | When may new work start if an earlier result can return, and what resource time must remain available? | OPS.8, OPS.5; conditional OPS.10.1 and OPS.10.2, OPS.15.1, MMP.8 and MMP.8.SD |
| 11 | OPS.8.2 - Use Protective Capacity While Keeping It Available | Stable | Which auxiliary work can use idle reserve while its completion or interruption preserves the required service? | OPS.8; conditional OPS.10.1 and OPS.10.2, OPS.12, C.40.OI and C.40.DC, HCD.2, C.39.MF and A.3.1.WT |
| 12 | OPS.9 - Diagnose and Treat the Current Operating Constraint | Stable | What limits the result now? Would comparing rival explanations change the proposed treatment? | OPS.3, OPS.4; conditional OPS.8, OPS.10, OPS.11; FPF C.16, C.28, C.11.CRC |
Part VI — Qualify Capacity and Coordinate Operating Structures
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 13 | OPS.10 - Qualify Operating Capacity Under Variability | Stable | What fits usable resource windows, and what service claim does the variability basis support? | OPS.3, OPS.4; conditional OPS.8, OPS.9, OPS.11; FPF C.16, C.27.TA, C.11.CRC |
| 14 | OPS.10.1 - Construct and Compare Operating Capacity Models | Stable | Which service model answers the capacity question, and how do variation, dependence and the completion criterion change the comparison? | OPS.10, OPS.11.1, OPS.15.1; conditional OPS.10.2, MMP.7 and MMP.13, CMP.9; FPF C.29, C.11.CRC |
| 15 | OPS.10.2 - Construct and Revise a Feasible Deadline Schedule | Stable | Which schedule can meet the deadline under the dependencies, resource sharing and calendar gaps? Which starts can wait, and what must change after a disruption? | OPS.10, OPS.11.1, OPS.15.1; conditional OPS.10.1, OPS.7 and OPS.8, MMP.10, CMP.4 and CMP.5; FPF C.29 |
| 16 | OPS.11 - Coordinate Interacting Operating Structures | Stable | Which dependencies among operations can defeat a local plan, and which decisions must be coordinated? | OPS.3, OPS.4; conditional OPS.8–OPS.10; FPF A.22, E.18.NET, C.11.CRC |
| 17 | OPS.11.1 - Construct and Reconcile Operating Models Across Scales | Stable | How can an operating arrangement be constructed from the needed result, and its local routes, shared resources and receiving completion be modeled together? | OPS.11, OPS.19; conditional OPS.15.1, MMP.10 and MMP.18; FPF A.22.CGUS, E.18.3, C.29 |
Part VII — Protect Human Conditions and Establish Service Commitments
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 18 | OPS.12 - Protect Human Conditions in Operating Decisions | Stable | Which feasible operating intervention protects affected people and supports the service? | OPS.3; conditional OPS.10, OPS.13–OPS.15; FPF C.16, A.10, A.11.OP |
| 19 | OPS.13 - Align Commitments, Resources, and Service Outcomes | Stable | What service can the authorized parties agree given the available resources, evidence and operating conditions? | conditional OPS.10, OPS.12, OPS.14, OPS.15, OPS.18; FPF A.10, C.16 |
Part VIII — Compare Operating Consequences and Build Useful Accounts
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 20 | OPS.14 - Relate Throughput, Cash, and Operating Consequences | Stable | What service, resource, payment and receipt differences change the operating choice? | conditional OPS.10, OPS.12, OPS.13, OPS.15; FPF C.16, A.10, A.11.OP |
| 21 | OPS.15 - Build a Decision-Specific Operating Account | Stable | Which observations and meanings support the requested operating claim or decision? | OPS.3; conditional OPS.4, OPS.12–OPS.14, OPS.18; FPF C.16, A.10, E.13, A.11.OP |
| 22 | OPS.15.1 - Derive Operating Quantities from Events | Stable | How do events yield waiting, resource occupancy and completion quantities when work overlaps, returns or remains unfinished at the cutoff? | OPS.15; conditional OPS.11.1; FPF C.16, C.29; MMP.7 for an observation model |
Part IX — Improve Methods, Control Quality, Reconcile Work, and Continue Practice
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 23 | OPS.16 - Decide Whether and How to Change an Operating Method | Stable | What does bounded evidence support: continuing an established use, adopting, revising or branching an admitted operating Method; retaining or revising a candidate account; testing Method identity; stopping; or further observation? | OPS.15, OPS.17 and OPS.18; applicable OPS.10–OPS.13, OPS.19; conditional OPS.11.1, OCE.11; A.3.1.WT, A.3.1.CC, A.3.1.FT, C.11.MV, A.3.1.MV and A.3.1.MI; FPF A.3.1.MR, A.3.1, A.3.2, A.15.1, A.15.2, A.10, C.16 |
| 24 | OPS.17 - Compare and Refresh Operations Methods | Stable | Which operating moves fit this Work family? How can recurring support develop usable knowledge, and what change reopens the choice? | A.3.1.MV; conditional OPS.5–OPS.15, OPS.18, OPS.22, KCAE.MEMORY, KCAE.CHANGE, KCAE.EVAL, CB.14, A.3.1.WT, A.3.1.FT, C.11.MV; FPF A.3.1, A.3.2, C.16, G.5, A.11.OP |
| 25 | OPS.18 - Control Operating Quality and Reliability | Stable | What does the evidence establish about quality or reliability? What continuation, acceptance, containment or recovery does the applicable rule or operating task require? | conditional OPS.12–OPS.15, OPS.17; FPF C.16, A.10, A.11.OP |
| 26 | OPS.19 - Reconcile Simultaneous Operating Work Across Cases and Scales | Stable | Which cross-scale reconfiguration, bounded continuation, or unresolved conflict preserves the simultaneous operating results that matter? | OPS.1, OPS.3; conditional OPS.11, OPS.12, OPS.15, OPS.17; FPF C.32.MWA, C.11 |
| 27 | OPS.20 - Deliberately Continue and Change Operations Culture | Stable | What does the evidence establish about transmission, use, selection, retention or loss of this operating practice in the named population? If a decision is needed, what continuation or change does it support? | OPS.16, OPS.17, OPS.19; FPF C.36; C.36.MC |
Part X — Choose Operating Aims and Interpret Performance
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| 28 | OPS.21 - Choose Operating Aims, Targets and Comparisons | Stable | What improvement is worthwhile, or what adequate condition should the team monitor? Which comparison fits the need? | conditional OPS.1, OPS.10, OPS.13, OPS.15, OPS.19, STR.5 and STR.8, MA.1, MA.2, MA.5 and MA.6, OCE.10 |
| 29 | OPS.22 - Interpret Operating Performance and Decide the Response | Stable | What does this result mean given target difficulty, changed conditions and joint work? What response, if requested, do the findings support? | conditional OPS.13, OPS.15, OPS.19, OPS.21, MA.7 and MA.9, OCE.10; HCD.11 and CGOV.13 for distinct receiving questions |
Operations Management Principles Framework Readme
Practical entries
Operations Management connects decisions about continuing service: what may start, what a case needs next, what the available resources can support, what can be promised, and what must change when results fail. These decisions use different results. A capacity calculation can constrain admission; an incident can change priorities; a service promise can remain unresolved after a feasible schedule has been found.
For the broader question of what Operations Management studies and changes, read OPS.Reference:1.1–1.6. That account derives operating units and dependencies from the receiving result, distinguishes knowledge from an arrangement and its actual work, and explains how to construct or revise the means of obtaining the result. OPS.11.1 develops the operating construction when an adequate arrangement is not yet available.
These selected examples show how to combine the methods around a current difficulty. Enter where adequate inputs are available and stop at the result the decision needs. The Table of Contents gives direct access to OPS.1–OPS.23 and their nested methods. The Architectural Reference, including its conditions on a whole combination, explains why individually useful operating moves can conflict when they use the same resources, authority or evidence.
Keep the connected operating reasoning in view. The operational mantra (OPS.23) relates accepted results, readiness, limiting conditions, feasible starts, commitments and observed consequences. It explains why these answers must fit together and which ones to revisit when conditions change. Use it to connect local work to the receiving operation; use a sufficient individual method directly for a smaller question.
You can ask an assisting agent to explain a pattern or comment on your case in ordinary language, without framework jargon.
The numbers in these applications are constructed. The examples stipulate their professional premises. A clinical, safety, financial or release decision needs qualified inputs for its own case.
If repeated support questions consume expert time, OPS.17:4.2.1 distinguishes a missing answer, poor access and a service problem. It explains when to use the KCS professional practice and how to return its results to the operating choice. The changed support case follows that choice through new conditions and agent performance.
OPS-PUMPWORKS — Find the next supported controller-service decision
-
Situation: PumpWorks must continue controller test service and incident response while incomplete inputs, rig access, operator recovery and field-release decisions interact.
-
Question: What can start and finish within the available window, and which other decision must change if the plan changes?
-
First useful result or blocker: A readiness and capacity basis for a supported operating plan, with any demand to defer and any permission, staffing or funding condition still unresolved.
-
Start with: OPS.8 - Coordinate Queues and Buffers when the immediate difficulty is ready work and incomplete inputs. Reuse an adequate operating account; recover a missing subject or commitment only if it can change this decision.
-
Stop or return: Return changed feasibility to admission and affected commitments. A supported test-service plan does not authorize release to the field. For a field-release claim, identify the supporting evidence for that use.
- Keep the same subjects across the needed views. OPS.1 - Identify the Operating System, Commitments, and Flow Units bounds the continuing control-service operation. OPS.3 - Distinguish Operating Subjects, Cases, Queues, Resources, and Records separates a release candidate, incident, rig request and test attempt. OPS.2 - Select Work-Management Views and Coordination Methods can use case, recurring-process and queueing views for their different questions. OPS.4 - Keep Current Operating State Recoverable Across Participants makes the relevant evidence, unresolved conditions and next decisions recoverable to the participants; they need not share one screen.
- Establish readiness for the next action. In the PumpWorks application, twelve matters appear on boards but only four are ready test packages. OPS.8 identifies what the test can use now. The test’s future output is not its own prerequisite. If laboratory permission is current and the unresolved safety question concerns only field release, the test may proceed while release remains held. A safety condition that also governs testing changes that conclusion.
- Distinguish missing inputs from insufficient usable time. Across forty rig-access hours, the example records twenty testing, four setup, four unavailable and twelve without eligible work. OPS.9 - Diagnose and Treat the Current Operating Constraint uses eligibility and service histories to distinguish late prerequisites from a resource deficit in the required window. The historical starvation does not settle the next window: OPS.10 - Qualify Operating Capacity Under Variability finds six usable rig-hours and four packages needing two consecutive hours each. All four require eight hours and cannot fit.
- Make the adverse case and other demands part of the plan. Suppose one planned package requires an immediate two-hour repeat and then passes, while the other planned packages pass first time. Two completions plus that repeat use six hours; three plus the repeat need eight. OPS.12 - Protect Human Conditions in Operating Decisions preserves the operator’s required recovery and incident coverage after hour six. Extra rig access needs qualified relief as well as the resource owner’s decision. The full application also compares advance funding and a later slot; an extra window alone does not make the whole extension feasible.
- Use the combined result to decide starts and returns. OPS.19 - Reconcile Simultaneous Operating Work Across Cases and Scales retains the feasible two-package plan, defers the third to its qualified later slot and keeps a competing trial closed in the same six-hour window. OPS.5 - Admit Work and Limit Starts gives each considered item its disposition. OPS.7 - Manage Aging, Urgency, and Service Commitments handles the affected local priority or existing promise under the appropriate authority. OPS.11 - Coordinate Interacting Operating Structures checks that access and evidence still concern the required interval and configuration.
If an extra window, qualified relief and the other required conditions later become available, reopen the affected plan and offer. Keep the useful readiness rule and unchanged evidence. Within an already admitted incident, OPS.6 - Continue Cases and Handle Exceptions can instead apply a sufficient current rule directly; report progression only when the performed work and result support it.
OPS-SERVICE-WINDOW — Offer service that rooms, people and commitments can support together
-
Situation: A recipient requests additional service. Visible space appears sufficient, but qualified staff, existing commitments, support work and recovery share the same window.
-
Question: What can the parties credibly agree given the available rooms, qualified team time and remaining obligations?
-
First useful result or blocker: A supported smaller offer, another feasible resource or timing arrangement, a refusal, or the particular professional or authority result still missing.
-
Start with: OPS.13 - Align Commitments, Resources, and Service Outcomes, distinguishing the requested target, forecast and actual undertaking.
-
Stop or return: Obtain the parties’ decision on a changed promise. Internal replanning does not discharge an existing commitment; an unresolved professional condition remains with its responsible practitioner.
- Use the resource that limits this service. In the constructed hospital application, two rooms each have four available hours, but one qualified team has four usable hours. Supplied clinical and operating assumptions require thirty minutes per routine visit, including turnover, and reserve one team-hour for the stated urgent-case scenario. OPS.10 therefore supports six routine visits in total, not sixteen from the room count.
- Subtract what is already promised. Two visits are committed and six additional visits are requested. The supported proposal is four additional routine visits under the stated reserve. Serving all six additional requests needs another qualified arrangement or an agreed later time. Eligibility, clinical priority and protected conditions remain supplied professional decisions.
- Make the schedule usable for everyone who supplies it. OPS.12 follows the support team’s other duty and recovery. Where the supplied windows permit two groups of three visits, that arrangement can preserve both service and support duties. If the reserve changes from one to two team-hours, only four routine visits fit: after the two existing commitments, the additional offer falls to two. Return that changed resource result to OPS.13 before confirming the larger offer.
- Use an account that retains unfinished obligations. OPS.15 - Build a Decision-Specific Operating Account distinguishes the historical due-request cohort from completed visits. Twenty-seven timely, three late-completed and ten still-open requests give timely service of
27/40 = 67.5%. The completed-only27/30 = 90%answers another question. Use the due-cohort result for overdue service, while the clinical evidence determines clinical action.
OPS.14 - Relate Throughput, Cash, and Operating Consequences enters when paid cover, displaced service or funding changes the choice. It compares the payments and receipts that differ between the alternatives over the decision horizon. An allocated share of an unchanged room or salary cost is not an avoided payment, and a later receipt cannot fund an earlier expense without an available financing arrangement.
OPS-ACCEPTED-RESULT — Faster generation still leaves the promised result unavailable
-
Situation: An AI-assisted software operation produces more drafts at lower unit cost, but qualified review, acceptance and deployed-service conditions limit what the recipient can rely on.
-
Question: Which operating change improves the needed result, rather than merely increasing attempts or moving work to reviewers?
-
First useful result or blocker: A supported admission or service change, a comparison of feasible alternatives, or a quality response with the evidence needed for continuation.
-
Start with: OPS.15 to recover the requested result and its population, then OPS.10 when the available review capacity decides the immediate question.
-
Stop or return: Retain the distinction between drafts, review decisions, accepted changes and authorized deployments. A settled resource bound can answer the current request without an additional model or experiment.
- Follow generation to acceptance. In the constructed software application, sixty drafts can be generated per day but qualified staffing supports six individual review decisions. Each accepted output needs its own decision. Ten accepted outputs tomorrow are therefore excluded under the current arrangement. Recent days with four to six accepted outputs do not supply a probability for tomorrow, or a guarantee that all six reviews will accept.
- Compare changes at the receiving result. OPS.17 - Compare and Refresh Operations Methods compares limiting starts, obtaining qualified review capacity and changing preparation or acceptance. OPS.12 follows review, rework, interruptions and recovery; OPS.13 uses the resulting capacity and conditions to form a later or narrower offer. If the recipient accepts a review service instead of accepted output, make that changed result explicit.
- Keep payment and service consequences together. A separate constructed day in the application has four accepted outputs due. Both alternatives generate sixty charged drafts, use six reviews and pay the same salary of 240. The current alternative pays 60 for drafts and accepts four outputs: total payments 300. The cheaper-generation alternative pays 30 plus 10 for rework and accepts two: total 280. Its 20 payment reduction leaves two due outputs unaccepted. OPS.14 compares that service consequence before treating the lower generation price as an improvement.
- Use deployed-service evidence for the deployed-service decision. OPS.18 - Control Operating Quality and Reliability uses a separately defined population of one million eligible service requests with a 99.9% success objective. The permitted failure amount is 1,000; 1,500 unsuccessful requests consume 150% of it. Under the example’s authorized response policy, discretionary feature releases pause while permitted urgent recovery and security work continue. Restart needs the agreed service evidence. Accepted code and a fresh reporting period do not establish restored service.
When recovery, review and testing compete for the same people or environment, OPS.19 uses their separate results to change starts or allocations while preserving the required service. Software assurance, security and release authority remain inputs from their responsible practices.
OPS-PRACTICE-CHANGE — Change the way of working without treating publication as successful use
-
Situation: A new admission or handover method looks promising, but testing it competes with continuing service, and a local success is being used to justify wider adoption.
-
Question: What can be retained or changed now, and which later-use claim does the evidence support?
-
First useful result or blocker: A supported local method-use decision or revised candidate account, and, when needed, a separate conclusion about the named practitioners’ use.
-
Start with: OPS.17 when alternatives need comparison, or OPS.16 - Decide Whether and How to Change an Operating Method when the question concerns one method or proposed way of working.
-
Stop or return: Keep a sufficient current result. Treat the proposed way as a candidate when its status as a reusable method is still unresolved; publication, attendance and tool use do not establish independent later application.
- Select the changed operating contribution. Compare the proposed action and result with current practice and a simpler sufficient correction. Readiness-based admission, protection of an established constraint and extra capacity solve different problems. Use the constraint diagnosis from OPS.9, retaining an unresolved rival explanation when it could change the treatment.
- Establish that the trial can coexist with service. OPS.19 can keep a trial closed when two package completions and a possible repeat already occupy all six rig-hours. OPS.16 uses an actual coexistence result, including incident coverage, support, permission, fallback and the return to continuing service, before relying on a later trial window. A plan to obtain those conditions is not their availability.
- Limit the local conclusion to what was done. In the later constructed PumpWorks interval, the already admitted method
PW-TestAdmission-v2is tried on two packages. One is correctly admitted; the other is correctly held for missing permission, while service and recovery remain protected. OPS.16 retains that method for the specified package family and conditions, keeps the earlier method for the unaffected family and leaves provider-unavailability use unresolved. This does not establish general superiority or wider independent use. - Ask a different question when another group must use it. OPS.20 - Deliberately Continue and Change Operations Culture bounds the practitioners, practice and interval. In the six-week example, two coordinators use the method correctly in familiar eligible cases; a third starts a case without required provider support. Preserve the supported familiar use and revise the failed branch. The other named shift and longer retention remain unknown. The current conclusion can finish without a new experiment; a later receiving use may justify a feasible protected replay of the unresolved branch.
OPS-RELEASE-AND-WAIT - Change admission without losing the customer’s wait
- Situation: The reported time from internal admission to completion falls after a limit on work in progress, but customers receive their orders no earlier.
- Question: What improved, and what waiting did the internal measure leave out?
- First useful result or blocker: A comparison that keeps the resource arrangement, release rule and customer’s waiting origin together.
- Start with: OPS.11.1 - Construct and Reconcile Operating Models Across Scales for the arrangement being changed, and OPS.15.1 - Derive Operating Quantities from Events for the observations used to compare it.
- Stop or return: Keep a sufficient comparison. Return a changed service limit to admission and commitments; weigh further inquiry only if its answer could change the decision or the grounds for relying on it.
- Construct the alternatives on the same operation. Four orders arrive at time zero. Each needs one hour at A and then two hours at B. The two stations have independent resources, work in order and start as soon as permitted; there are no setups, failures or returns. OPS.11.1 keeps these premises and the customer’s completion event while OPS.8 supplies the admission and transfer policy. With individual transfer and all orders admitted at zero, B finishes at hours 3, 5, 7 and 9.
- Apply the changed admission rule. With at most two orders admitted but unfinished, admit another immediately when a completion frees a place. Admissions occur at 0, 0, 3 and 5; the same resource calculation gives the same four completions. OPS.10.2 - Construct and Revise a Feasible Deadline Schedule places the operations under that admission rule and the unchanged resource conditions. OPS.10 uses the resulting schedule for its capacity and service question. The last order is still ready at hour 9.
- Measure both waits from their own events. OPS.15.1 derives a mean internal residence of four hours and a mean customer wait of six. Across the empty-to-empty nine-hour interval, the corresponding count-time areas are 16 and 24 order-hours. Eight order-hours moved outside the admission boundary. OPS.15 presents that distinction to the decision maker; a lower internal average alone does not establish earlier delivery.
- Return a changed physical premise to the plan. If one operator must instead perform every A and B operation without overlap, the four orders require twelve operator-hours. The previous nine-hour plan is infeasible. OPS.11.1 revises the shared-resource account; OPS.10.1 - Construct and Compare Operating Capacity Models derives the resource-time obstruction, and OPS.19 reconciles competing work. A promise to deliver all four by hour 10 needs a changed arrangement or a revised commitment through OPS.13.
The Foundational Thinking Suite Reference (Foundational.Reference:3.8) develops this constructed example through the mathematical formulation and its computation. A WIP limit can improve service through reduced interference or rework; that conclusion needs the corresponding mechanism and comparison.
OPS-PROTECT-AND-DEVELOP - Prepare or learn while preserving promised service
- Situation: A specialist has finished a first pass and could start new work, but an earlier result may return for correction. Some of the waiting interval could be used for preparation or learning.
- Question: Which new work can proceed while the promised service remains feasible, and what counts as improvement?
- First useful result or blocker: An operating choice that preserves the required correction window, identifies a useful auxiliary unit and retains the customer’s whole waiting interval.
- Start with: OPS.11.1 to recover the work and shared resources; then combine OPS.8.1, OPS.8.2 and the capacity, scheduling and quantity methods for the consequences that affect the choice.
- Stop or return: Use a sufficient arrangement. Return an impossible promise to its conditions or OPS.13. Use HCD or the Core methods for opportunity construction and Method development to assess the proposed learning or improvement.
- Keep the unfinished service in the operating model. In this constructed case, report X arrived at hour −2 and its first pass finished at zero. At hour one, a separate reviewer either accepts it or supplies a correction requiring two uninterrupted specialist-hours. If correction is needed, its completion supplies the promised result, required by hour three. New session Y needs the same specialist for four uninterrupted hours, is ready at zero and must finish by seven. OPS.11.1 retains the shared specialist and feedback event; OPS.15.1 distinguishes first-pass completion from delivery of the required result.
- Construct a response that can use the reviewer’s answer. Two hours of correction and four hours for Y fit within seven available hours, but that total does not settle their placement. OPS.10.2 shows that starting Y at zero would postpone correction until 4–6, too late for X. OPS.8.1 - Choose Work-Release Rules When Earlier Work Can Return preserves the 1–3 correction window. If X is accepted at one, run Y at 1–5; if it returns, correct X at 1–3 and run Y at 3–7. This rule uses information available at the choice and meets both stated requirements.
- Use only an auxiliary unit that leaves the protected action ready. Suppose a prepared exercise takes half an hour and its closure and restoration of the specialist’s work context take another quarter-hour. No earlier recall is included in this case, and the required resources remain available. OPS.8.2 - Use Protective Capacity While Keeping It Available fits the unit at 0–0.75, before the feedback at one. A longer indivisible lesson could consume the correction window. If learning is the aim, use HCD.2 to identify the practice and feedback the learner needs, then provide them. The available interval shows that the exercise fits. To establish improvement, examine the learner’s performance. C.40.OI and C.40.DC or C.39.MF and A.3.1.WT can instead develop a preparation opportunity or method trial with its own full burden.
- Measure the promised result and compare the cost. OPS.15.1 retains X’s wait from −2: three hours if accepted at one and five if corrected by three. Y waits five or seven hours from its own arrival. The exercise neither erases that waiting nor creates an additional accepted customer result. OPS.14 can compare its incremental financial consequences when that changes the choice; HCD or Core’s Method-development family establishes its intended development contribution.
- Reopen the affected relation when the condition changes. Move the review to hour two and retain the two-hour correction and deadline three. Even an idle specialist can finish only at four. OPS.10.1 identifies that finite timing obstruction; holding all new work cannot remove it. Obtain earlier usable feedback, a correction method that fits the remaining interval, or a revised commitment through OPS.13. Preserve the unaffected resource and waiting definitions.
OPS-PREPARE-AND-RESPOND - Prepare useful work and keep a response possible
- Situation: A requested result needs preparation, several participants and a timely decision. More starts or more status messages are consuming the same attention needed to finish it.
- Question: What should be prepared, promised and started, and how soon must a consequential change reach someone who can act?
- First useful result or blocker: A feasible service arrangement, including the needed preparation and response, or a specific condition that requires a different offer.
- Start with: OPS.1 and OPS.13 for the recipient’s result; use OPS.11.1, OPS.10.2, OPS.4 and OPS.14 to connect the work, response and financial consequences.
- Stop or return: Use the arrangement while its assumptions hold. Obtain any missing professional contribution and agree any needed change to the promise with the responsible parties.
- Choose a useful whole result before dividing the work. In the constructed report case, the recipient needs an accepted comparison by hour fourteen. Input recovery, analysis and release contribute to one report. Two teams recording their contributions do not create two accepted reports. OPS.1 fixes this result and its completion event; OPS.11.1 connects the contributions. If a smaller comparison would serve the recipient, OPS.13 can offer it explicitly. Omitting a relation that the decision needs would instead leave an unfinished result.
- Prepare what the selected work will need. Recover the input, capabilities and resource windows with OPS.13:4.2. A prerequisite may already be available or have a supported arrival before its consuming operation starts. When an unresolved fact could change the offer, use C.11.DUA to compare a useful inquiry with a conditional offer or accepting the stated uncertainty, where the service permits those choices. Count any selected inquiry or trial as work with its own burden. OPS.5 then distinguishes an offer, an agreed commitment and permission to start. OPS.8.1 updates release choices when earlier work returns, and OPS.8.2 can place preparation in spare time that the planned return permits.
- Make the information arrive while a remedy can still work. The report needs its input by ten. At seven, recovery takes two hours after authorization, so authorization is needed by eight. A review at nine loses the opportunity. OPS.13:4.5 constructs the detection, decision and recovery timing; in its example, a response starts by 7.5 and delivery occurs by 13.5. OPS.4 supplies the relevant state to the participant who can decide. If recovery cannot start before ten, the same signal instead leads to a changed remedy or service offer.
- Keep the four accounts connected and distinct. The work account counts the accepted report and the operations it requires. The information account follows when the input failure becomes known and usable for a decision. The attention account preserves the analyst’s three uninterrupted hours and includes the coordination and recovery burden; extra messages can disrupt that interval. The financial account follows the payments and receipts changed by the choice. OPS.15.1 supplies the event and interval definitions, OPS.12 the human conditions, and OPS.14 the financial comparison. Sharing a diagram does not give these quantities one conservation law.
- Check funding and the next admission against the changed arrangement. Suppose immediate input recovery requires a payment of 120 currency units, only 100 is available, and the report would bring 300 the following day. At the required payment time, available funds fall short by twenty. Obtain that funding in time or change the plan; its eventual positive balance cannot fund an earlier payment. Once recovery occupies a resource, include that occupation before admitting another job.
OPS-ADVICE-IN-USE - Follow an operating explanation into the user’s work
- Situation: Reports and lessons are being produced, but their recipients still cannot choose or adapt the described operating method, or different teams offer incompatible advice.
- Question: Is the obstruction in the operating claim, its explanation, the learning arrangement or the later application?
- First useful result or blocker: A corrected claim or explanation, usable support for the recipient’s next action, or a clearly bounded learning or transfer question.
- Start with: OPS.1 for the service result, then EXD.4, FPF A.3.1.CC, HCD.19 or HCD.12 according to the difficulty found.
- Stop or return: Stop when the intended use is supported. Publishing a correct text, understanding it with help and applying it independently later are different results; pursue the one the service promises.
- Follow the recipient’s question. In the admission example, mean internal time is four hours while mean customer waiting remains six. Suppose a reader asks why. EXD.4 uses that question to explain the two starting events: the two-hour average before admission remains part of the customer’s wait. The useful result is a correctly bounded comparison, from which the reader can reject an apparent delivery improvement caused only by moving the counting boundary.
- Repair the claim or the explanation where it fails. If a second team’s advice equates arrival-to-delivery time with processing time in this same queued operation, A.3.1.CC locates the contradicted claim and its dependent calculation. If the teams simply measure different intervals, retain their definitions and relate them through OPS.15.1 instead. If the account is correct but the reader cannot recover the omitted waiting interval, EXD.4 supplies the missing relation. HCD.19 distinguishes what the published material supplied from what a teacher later explained, so a successful helped response does not hide a missing explanation in the material.
- Test the intended further use. For a claim about transfer, HCD.12 uses a materially unfamiliar condition whose consequence is already understood by the assessor. Sharing a previously independent resource can invalidate the old completion schedule; the reader must reconstruct the relevant occupations with OPS.10.2. A worked variant already shown to that reader tests supported reuse, so choose another unrehearsed condition when independent adaptation is the claim. These constructed examples explain the test.
- Coordinate production and receiving support. Count publication when the agreed publication result is delivered. If the service also includes explanation, practice or later application, OPS.11.1 includes their work, resources and completion conditions; OPS.10.1 compares the support demand with available capacity. A growing queue of requests for clarification may call for one material repair under HCD.19 rather than more publications. OPS.14 compares the consequential costs. Preserve a useful completed publication without claiming that it has already changed anyone’s capability.
The long applications add case-specific conditions and returns. Use the common Operations methods whose results the current decision needs, together with the qualified contributions of the relevant professional practice.
OPS-AIMS-AND-PERFORMANCE — Set a meaningful aim and interpret what follows
- Situation: A target gives little guidance, a peer ranking hides different work, or a missed aim prompts judgement before the changed conditions and joint result are examined.
- Question: What contribution is worth pursuing, how will it be compared, and what should the later result change?
- First useful result or blocker: A meaningful aim, a condition to monitor, or a reasoned operating assessment. An aim can guide the next action. The assessment can support a response under existing authority or a proposal for whoever must decide.
- Start with: OPS.21 when the aim or comparison is missing; OPS.22 when the result needs interpretation. Use an adequate supplied basis directly.
- Stop or return: A target does not authorize a service promise or spending. Return a changed premise to the aim, forecast, provision, commitment or consequence rule it affects.
In the repair cooperative example (Engineering.Reference:7), twelve known useful opportunities justify considering an ambition of twelve while bookings and warranted further demand support a forecast of eight. OPS.21 constructs that distinction and chooses what evidence would show a useful result. MA.5–MA.6 preserve the outlook; the operating and financial methods expose staffing and cash conditions before OPS.13 establishes promises. When work becomes harder, OPS.13 and OPS.19 obtain an agreed response rather than merely lowering a number. OPS.22 then retains the factual miss, examines difficulty and shared consequences, and distinguishes the useful response from an unsupported team ranking. An effective change in the local review rule makes the adverse forecast usable for action; changing its label alone would leave the conflict intact.
Operations Management Principles Framework Architectural Reference
Operations Management studies and changes how an operation obtains useful production or service results through work over time. Practitioners relate what recipients need to the work that can obtain it, the resources and agreements that make that work possible, and the conditions under which the result remains usable. They use that understanding to arrange provision, manage current work, and improve the ways of working. The operation can be a production facility, a service, a development undertaking or a network of cooperating providers; its relevant boundary follows the result and its dependencies.
The framework begins before optimization. OPS.1–OPS.4 identify the operation and commitments, select views for the current questions, distinguish subjects from records and maintain a usable current account. OPS.5–OPS.7 guide admission, case continuation and local priority or existing commitments. OPS.8–OPS.11 connect those decisions to queues, constraints, capacity and interacting structures. OPS.12–OPS.18 add human-condition interventions, credible service commitments, operating-financial comparisons, decision-specific accounts, evidence-bounded Method improvement, Method-repertoire choices and quality/reliability control. OPS.19 reconciles simultaneous operating results across cases and scales. OPS.20 tests deliberate continuation or change of Operations practice in a bounded practitioner population.
OPS.Reference:1 - Start from a difficulty in continuing operation
A production coordinator can have a busy cell while promised orders remain unfulfilled. A service lead can see an improving completed-case average while difficult requests remain open. A software team can generate changes faster while qualified review, incident recovery and delivery to users fall behind. In each situation, the question is what the operation can do next while preserving the results its recipients already depend on.
Use OPS when production or service needs a workable arrangement, or continuing Work needs an admission, continuation, coordination, service, quality or improvement decision. A useful first result may be one request deferred with a clear reconsideration condition, one permissible next action in an admitted case, a corrected service denominator, or a feasible response to a conflicting duty. When the required inputs are already clear, use the corresponding Method directly. Otherwise, OPS.1–OPS.4 recover only the operating focus, subjects, views or current claims that the decision needs.
The recurring difficulty is that a locally reasonable move can lose its purpose at the receiving boundary. Starting more work can consume the time needed to finish existing commitments. A completed test may still lack the configuration correspondence needed for release. A cheaper method may shift unpaid checking to another participant. Calling all of these situations a flow problem leaves some decisive questions unanswered; ignoring their resource and timing relations can make the proposed service impossible.
OPS.Reference:1.1 - Derive operating objects and units from the result
The starting object is a result a recipient can use or a condition that must continue. A recipient may need a repaired device, a warranted answer to an investigated question, an available incident service or a specified amount of material. These results require different completion and observation rules. A physical item can continue through several transformations; a service can change the recipient’s system; an investigation can change what is known while leaving the eventual product undecided. An operation’s output is therefore identified through its receiving use before a convenient count is chosen.
Work becomes necessary through a difference between that required result and the current situation. Recover the actions that could close the difference from the relevant professional methods and from observations of competent performance. Work backward to the inputs, intermediate results and conditions each action needs, then forward to check that their combination obtains the receiving result. This is how preparation, production, inspection, correction, transport and support enter the operating account when the result needs them. Examine repeated steps for a contribution that can be omitted without losing the receiving result or a required condition. Before scheduling a step called “resolve the problem”, identify how the work could produce the required result.
Choose working units at the boundaries where a meaningful contribution can become ready, be assigned, be interrupted or completed, and be used by another action. Those boundaries need not coincide. A customer’s order can require several components; a machine batch can contain components for several orders; a diagnostic attempt can produce useful evidence without completing the case. The case remains the continuing matter, the attempt is one performance, and the evidence is its result. Combining them under one count loses the relation needed to decide what to do next. OPS.1 and OPS.3 establish the identities; OPS.11.1 constructs the corresponding work and completion relations.
The choice of unit can change the work. Split a large commitment where a smaller result would be usable, or where a separately ready contribution can be performed without defeating the whole. Keep together contributions that must be obtained or accepted together. Compare the saved waiting with added preparation, coordination, checking and unfinished inventory. In exploratory work, a worthwhile unit can be one interpretable test of a consequential hypothesis; the scientific or engineering method supplies the test and its interpretation, while Operations arranges its performance and use. A time allowance can bound the expenditure without promising that a question will be solved within it.
A resource is relevant through what it can contribute to this work under the required conditions. A qualified person’s hour, an available machine interval, information access and a consumable supply impose different constraints. A machine can remain occupied while its operator is free for other work. A person assigned to two departments remains one person. Recover usable capacity through capability, configuration, access and time, and retain the shared identity across the accounts that consume it. An aggregate headcount or equipment count can serve a broad comparison only while it preserves these consequential distinctions.
OPS.Reference:1.2 - Recover the relations that make an operation possible
Several kinds of dependence connect operating units. A later action may need a result produced earlier. Two actions may compete for the same resource. A permission or state condition may enable an action without being consumed by it. Several outputs may have to be present together before the recipient can accept the result. A commitment connects participants through what they have undertaken to provide. These relations determine which continuations are available; a single sequence or one organization chart may show only some of them.
Describe an operating arrangement by explaining how those dependencies will be satisfied. Identify the contribution of each action, how its result reaches its receiver, what shared means it occupies, and how a return or exception changes the remaining work. For a known manufacturing method this may yield a repeatable route with alternative machines. For a service case, new facts can select the next permitted action. For continuing infrastructure service, maintenance and incident response preserve an operating condition across many episodes. The work can overlap, repeat or branch in each arrangement. OPS.2 chooses views for these different questions; OPS.11 and OPS.11.1 recover the dependencies that the views must preserve.
Scope, functional organization and modular organization answer different questions. Bringing an external laboratory into the model widens the operating scope. Producing a result, maintaining the means of production and improving the method can form functional layers when their production-and-use relations organize the account. Interfaces let teams or equipment modules coordinate as peers. To identify modular levels, state what orders the modules, such as enclosure within a composite module or an acyclic dependency on other modules. Use that order for the decision it supports. A replacement can require checking the enclosing module’s interfaces while leaving the work schedule open. One team can contribute in several functional layers and several modules can jointly perform one function. FPF C.30.STRAT:4.2 explains how to recover the relation from working language.
The resulting description is knowledge about a possible or actual arrangement. To realize the arrangement, participants must obtain the needed contributions and access, and establish the necessary agreements. Performing the actions produces dated work and results. A changed description, a changed reusable method, a changed allocation and a changed organization can therefore lead to different next actions even when all are described as “changing the process”. OPS.16 qualifies method change; OCE.4 and OCE.6 supply organization design and effective assignment where those relations must change. An ordinary operating allocation can reuse an already sufficient arrangement.
OPS.Reference:1.3 - Distinguish the grounds of operating knowledge
Operating knowledge joins professional knowledge of what actions can obtain a result with knowledge of their combined behavior over time. Observations can establish what happened under the conditions they cover. Models expose consequences of selected relations and assumptions. Controlled comparisons, experiments and other suitable inquiries can test an explanation or proposed improvement. Commitments and professional rules establish obligations and permissible actions through their own authority. Each contribution can inform a decision without supplying the others.
Some operating conclusions follow from identities or bounds. For a fixed population with well-defined entry and exit, the number present at the end equals the number present at the start plus entries minus exits. If items split, join, are rejected or re-enter, the account must represent those events under the chosen identity rule. A resource cannot supply more occupied time than its available interval permits. Such relations can disprove a proposed arrangement before detailed scheduling. They cannot establish that the permitted work will be performed correctly, that the recipient will accept it or that a numerical objective is worth pursuing.
Other conclusions depend on a behavioral or statistical model. A service-time distribution, failure model or forecast must fit the work class and conditions to which it is applied. The long-run relation commonly written as Little’s law connects consistent averages; a finite reporting interval with unfinished work needs its own boundary treatment. A mean load can conceal a peak that defeats a response promise. OPS.10 and OPS.15.1 develop the appropriate capacity, event and interval reasoning. Choose the representation from the question: an arithmetic bound can settle an impossibility, a schedule can exhibit one feasible order, and a stochastic model may be needed for a probability of timely service.
Practical knowledge grows when observations challenge these grounds. An unexpected wait can expose an omitted approval, a shared operator or a changed demand mix. A disappointing trial can reveal an unsuitable method, a failure to perform it, or a change in the environment. First determine which claim the evidence bears on. Correcting the event account, changing an allocation, developing another method and revising an explanatory model are different responses. OPS.15, OPS.16, OPS.18 and OPS.22 give those questions separate treatment. Their results return to the operating account that relied on the defeated premise.
Operations Management connects explanations of operating behavior with reusable ways of arranging and managing production or service. Its knowledge explains why a way can work and where it can fail; its methods make that knowledge usable in practice; the results of practice can revise either. Replacing a queueing approximation or a dispatch policy can preserve that field while changing an important part of its knowledge or practice.
OPS.Reference:1.4 - Construct an arrangement as well as calculate its consequences
The forward question is what a proposed arrangement can deliver. Follow the required transformations, resource use and receiving conditions to obtain a bound, schedule, forecast or other supported consequence. The constructive question runs in the other direction: given the result and the conditions to preserve, which arrangement could obtain it? Recover the missing contributions, then compare ways to supply and connect them. The two questions inform one another. A failed schedule can expose an allocation to change; a new operating method can change which work needs scheduling at all.
Start that construction from a competent existing way when one is available. Vary a relation that can change the result: prepare a reusable input before demand arrives, separate preparation from case-specific work, change a transfer batch, share a resource, provide an alternative route, reserve response capacity or move an acceptance contribution to a usable time. Follow each alternative through to the recipient. Earlier preparation may create obsolete stock. Smaller transfers may consume more setup. Pooling may require qualification and additional coordination. A proposed improvement is complete enough to compare when these changed demands and dependencies are included with its gain.
Variability makes the choice consequential even when average demand appears to fit capacity. In a continuing production setting, inventory, available capacity and permitted waiting can absorb different effects of uneven demand and processing. Removing one protection changes what the others must absorb. Their usefulness depends on the subject: components may be stored, an unused response interval expires, and an unknown customer’s future diagnosis cannot be produced in advance. Product variety and discovery can also be desired sources of variation. Determine what variation can be reduced without losing the sought result, and what must instead be accommodated. OPS.8–OPS.10 compare the relevant protection and service mechanisms; their conditions govern any quantitative choice.
The technical way to obtain the result can be the missing contribution. If no qualified operation can produce the required material property or answer the research question, obtain that engineering or research work before relying on a production rate. A method can also be constructed or adapted from usable contributions. FPF C.39 supplies that construction; C.32.MWA.PP connects available methods to possible performance and provision. OPS.11.1 develops the operating choices of work boundaries, preparation, resource occupancy and timing, and OPS.16–OPS.17 qualify a proposed reusable change and its use. Developing a way, making it available and performing it remain distinct accomplishments.
A new arrangement can reveal a need to change the product, the service offer, an organizational relationship or financing. For example, delayed customization may need a different product design, another participant may need authority to accept the result, or funds may be needed before materials can be purchased. Use a sufficient contribution already available or take the outstanding question to the provider who can answer it. With an answer, recalculate the operating alternative. While it is open, show what would be feasible under the proposed conditions or identify the gap that prevents the operation. An operating impossibility can give another discipline a reason to change the design or provision on which the operation depends.
OPS.Reference:1.5 - Relate management practice to its control arrangements
Operations Management is the field that studies, arranges and manages the work described here. Control identifies a relation within that account: information and an embodied rule or participant’s choice determine an influence on a subject in relation to an outcome. A temperature regulator, an admission rule using queue state and a manager revising a service offer can each participate in control. Their concrete observations, interventions, delays, commitments and decision rights determine what those relations can achieve. Operations practitioners also develop knowledge of operating behaviour and design arrangements for delivering the result.
Recover the particular claim. A regulator can maintain a chosen condition while the operating offer remains unviable; management can revise that offer or arrange another supplier. Both can be understood through the relevant influence and its consequences, without making organizational commitments identical to a machine’s feedback signal. A fixed target and continuous feedback are possible arrangements, not universal conditions of control. A forecast or inspection contributes when its result informs the continuing action. FPF C.43:4.1.4 develops this recovery of field wording; its complete Method connects observation, choice, realization and revision. Use OPS.21 for the operating aim, OPS.13 for the promise, and OPS.Reference:7 when the structure of control is the unresolved question. FPF C.32.LCA constructs that arrangement when its observation, influence or timing must change.
Functional separation can make that influence possible. Estimating current state, planning resource use, selecting an immediate response and revising a commitment can need different information and time. Allocate those contributions to capable participants and connect their results. A single participant can perform several of them. The operating decision must account for the work, resources and authority needed for their combined performance.
OPS.Reference:1.6 - Use changed conditions to choose and revise the parts
A replacement-parts operation illustrates the construction from a receiving result. Customers need a configured kit soon after ordering. If common preparation remains usable across orders, the operation can prepare that part in advance and retain only the case-specific work after arrival. That choice changes the release boundary, stock exposure and resource calendar; it need not change who accepts the kit. If a new configuration requires all preparation to depend on the customer’s serial number, the common-stock premise fails. OPS.11.1:5.5 follows the change into alternative provision and a revised service choice. The old arithmetic can remain correct for the old product while ceasing to answer the new offer.
A live incident service has a different receiving condition: qualified response must remain obtainable during the covered interval. Completed incidents are useful events, but a quiet interval can still provide the promised readiness. Here the operation can prepare tools, access and knowledge, and reserve qualified response; it cannot store a completed future response for an unknown incident. Admission, staffing and scheduled improvement must be compared with that continuing service condition. OPS.8.2 tests whether an assisting resource can be released and restored in time, OPS.12 retains the person’s other duties and recovery, and OPS.13 establishes the feasible promise. A rise in demand can require a different reserve or service agreement without changing the incident method.
An investigation instead needs a warranted answer to a question whose solution path is partly unknown. Counting completed experiments as delivered answers would change the result being promised. A failed hypothesis may be valuable if it changes which continuation is justified. Use the research or engineering method to identify that information gain and the next useful inquiry; use OPS to arrange the qualified performers, equipment, sequence and support it needs. A new discovery can invalidate the planned work, while the completed experiments remain evidence. Reopen the method or question that changed rather than forcing the investigation to complete an obsolete task list.
These situations share a connection between receiving result, possible action, dependencies, provision and learning from consequences. They require different units, protection and grounds of inference. Use those differences to select or adapt the operating methods. OPS.23 helps assemble the resulting operating judgement. A direct method remains sufficient when its inputs and receiving connection are already settled.
OPS.Reference:2 - Competing demands on one operation
Operations practitioners choose among consequences that are useful on different subjects and horizons. Earlier service may cost more. A larger ready buffer can protect a scarce resource while increasing waiting and holding burden. A small batch can expose defects sooner while consuming more setup. A Method trial can improve later practice while using the same expertise that current incident recovery needs. OPS keeps those differences visible long enough for the responsible participants to make the choice.
Three conditions shape that choice throughout the repertoire. First, only usable capacity at the required time can support a promise; nominal hours, equipment counts and available money answer different questions. Second, existing commitments and protected human, service and specialist conditions limit which alternatives are feasible. Third, the evidence must fit the claim: a load bound, observed event, forecast and causal explanation support different decisions. Within the feasible alternatives, the responsible decision maker can state a preference for earlier service, lower payment, greater resilience or another relevant gain.
OPS.Reference:3 - Work, descriptions, structures, and records remain distinct
Work is admitted under its own conditions. Project, programme, process, case, queueing, and control views describe or coordinate Work for different questions; they do not create rival Work kinds. To identify an existing operating structure, establish which parts participate and which relations hold between them. A board, diagram, mathematical graph, event log, case file, model, or dashboard is a representation or record with a bounded use.
Name the structure relevant to the decision. For example, transformations connect inputs and results, while a resource dependency connects an activity to the capacity it requires. Commitment, event, case-state and control relations can answer other questions. If you use a graph, specify what its nodes and edges represent and how the result will be used.
OPS.Reference:4 - Demand, commitments, subjects, and units remain distinct
Demand can enter before Work is admitted. A commitment has parties, content, conditions, horizon, authority, status, and evidence limits. A subject can be a customer, case subject, physical item, release candidate, incident, material, service relation, account, or another identifiable entity. A Work item, case, batch, transaction, physical item, result, and commitment are not one “flow unit” by default.
Every counted unit needs an identity rule and receiving use. Every measure and queue policy inherits that unit. The foundation patterns therefore make identity and relation gaps visible before later flow, constraint, capacity, quality, or financial decisions use them.
OPS.Reference:5 - Several management views can coexist on the same Work
A project view can expose time-bounded commitments, WorkPlan content, decisions, dates, allocations, and closure. A process view can expose recurring Method, inputs, results, order, and controls. A case view can expose changing subject state, new facts, exceptions, permissible next Work, and closure. A queueing view can expose membership, waiting, order or service relation, and resource demand. A control-structure view can expose observation, actuation, reference, supervision, feedback, and unlike rates.
To use several views together, establish which subjects and levels of detail correspond, which commitments govern them and how their states relate. Identify when work can pass between them or proceed together, how updates affect the decision and any conflict or stopping condition that matters. The views can differ in structure.
Constituent actions in ongoing work. For example, inspecting a returned item can constitute part of resolving its service case, while resolving that case constitutes part of operating a repair service. All three can be under way during the inspection. A change from cosmetic acceptance to a requirement about intermittent failure changes the inspection needed in that case; faster visual checks alone cannot establish the new result. The operative must have the diagnostic capability and access the case requires, and shared test equipment must fit the combined operating demand. OPS.19 examines simultaneous work and conflicts, using FPF B.1.5.EW to recover these constituent connections when needed.
OPS.Reference:6 - Shared attention is stronger than visibility and weaker than consensus
A current operating account carries qualified claims about exact subjects and commitments for named decisions. It includes evidence and provenance, uncertainty and disagreement, permissions and authority, next decisions or permissible Work, and refresh or expiry conditions. Different participants may use different views while preserving subject and claim correspondence.
Participants should be able to recover the claim, its source, the decision and period it concerns, the basis for acting on it, any remaining uncertainty and any next action required.
OPS.Reference:7 - The control branch is conditional
Observer, controller, plant, supervisor, observation, actuation, feedback, and rate distinctions enter an Operations decision only when they change its coordination choice. Current FPF supplies generic control relations, selected control-structure views, and rate/dynamics claim discipline. Operations retains the decision-specific operating System, commitments, current state, intervention, authority and evidence for that intervention, and service or production consequences.
A controller product, loop diagram, feedback label, or control room does not make every operation a control loop. For a control decision, establish any feedback path, timing, stability, protection, authority and evidence it relies on. The operating question determines which Method can use that result.
OPS.Reference:8 - Pattern relations do not prescribe an operating lifecycle
OPS.1 → OPS.2, OPS.1 → OPS.3, OPS.2 + OPS.3 → OPS.4, OPS.2 + OPS.3 + OPS.4 → OPS.5, OPS.5 → OPS.6, and OPS.6 → OPS.7 are useful result dependencies only where a matching current input changes the receiving decision. They are not a mandatory calendar sequence. A subject account can be repaired while a view is selected; a stale claim can be refreshed without reopening the operating System; admission can start from current OPS.1–OPS.4 inputs; an already admitted case can enter OPS.6 directly; and a temporal or consequence question can enter OPS.7 when its evidence and authority exist.
OPS.5 permission applies only to the same admitted matter and effective conditions and does not establish performed Work. OPS.6 progression or unmet condition is evidence input to OPS.7, not authority to revise priority or a commitment. Practitioners may repeat or revisit these methods, select a different branch or stop as their conditions require.
OPS.8–OPS.11 likewise have conditional result relations: queue policy can require a constraint or capacity result; diagnosis can require a capacity bound or a coupled-structure explanation; a capacity change can require another owner’s decision. Their useful results can return to OPS.5–OPS.7.
The service and Method decisions also have conditional relations. OPS.12 helps preserve the required human conditions when choosing a feasible operating arrangement; OPS.13 can expose the resource decision that a promise needs; OPS.14 compares the consequential payments and receipts; OPS.15 makes the receiving claim inspectable. OPS.16 can use bounded evidence to improve a particular admitted Method or to test a candidate that retains its provisional status, OPS.17 selects or refreshes a Method repertoire, and OPS.18 establishes what the evidence supports about quality or reliability and guides any response the task or applicable rule requires. Each can be entered directly when its question is live and the needed inputs exist.
Use OPS.18:4.4 to reconstruct an incident, develop explanations of its contributing conditions and choose supported prevention. Keep containment, restart, completion of a correction and later recurrence evidence distinct. OPS.16 receives a resulting operating Method-change question; OPS.17 receives a repertoire comparison. B.5.2 and C.28 help with explanation and causal support, while C.11/C.11.CRC govern the preventive choice and its whole burden. Use C.11.DUA if the value or feasibility of further inquiry remains in question.
OPS.19 opens only when several otherwise valid operating results conflict across subjects, scopes, or horizons; its result can constrain an OPS.16 trial without deciding the later Method change. OPS.16, OPS.17 and OPS.19 may supply a practice variation or operating consequence to OPS.20. With OPS.20, specify the practitioner population, what continued use would mean for it and what the evidence establishes about that use and, for a requested decision, which continuation it supports. A sufficient existing answer can finish that question. A selected intervention needs authority, and a claim about later use needs evidence from the relevant interval.
Use the smallest pattern that can supply the decision, claim or operating result you need. Stop when the result is sufficient or when the next needed result belongs to another specialist practice or remains unsupported by the current evidence and authority.
OPS.Reference:9 - Use the Methods together where their results meet
OPS is a repertoire of related Methods that can be used independently when their inputs are available. The Parts group their descriptions for reading. The useful connection is a result needed by another decision. Keep that result’s subject, conditions, horizon and evidence when reusing it, and obtain only the missing contribution. The following combinations illustrate where more than one result matters.
| Current difficulty | Contributions that can cooperate | Decision-changing branch |
|---|---|---|
| An admitted case cannot take its planned next step. | OPS.6 refreshes the case and selects permissible continuation. OPS.7 uses the resulting delay or unmet condition if current priority or an existing commitment needs a separate decision. | If the current domain rule supplies the next action, use it. If several permissible actions remain, compare them. A changed case fact need not reopen queue or capacity policy. |
| Ready work waits while a resource sometimes has nothing usable to process. | OPS.8 recovers readiness and protection; OPS.9 distinguishes missing inputs from insufficient usable time; OPS.10 supplies a bound or suitable service analysis when that question can change treatment. | An existing readiness rule may settle dispatch immediately. A new constraint buffer needs a supported limiting relation; more capacity is a separate alternative for a demonstrated window deficit. |
| A recipient requests more service than the present arrangement supports. | OPS.13 forms the promise question and uses the relevant resource result from OPS.10, human-condition comparison from OPS.12, financial difference from OPS.14 and observations from OPS.15. | The parties may change timing, scope or resources, refuse the request, or keep a missing result explicit. A feasible schedule supplies only one premise of the service agreement. |
| Quality or service evidence requires action now. | OPS.18 selects monitoring, service control, acceptance or recovery and develops incident explanations when prevention needs them. OPS.15 repairs an unclear observation; OPS.12 and OPS.13 address affected duties or continuing service. | Apply a qualified response already settled by the evidence and authority. Further discrimination is unnecessary for prevention when the remaining explanations support the same available correction; keep any limit on the causal claim. |
| Locally supported decisions interfere, or the way of working needs change. | OPS.19 reconciles simultaneous operating results; OPS.17 compares reusable moves; OPS.16 examines a bounded change to an operating Method using existing evidence or a justified trial; OPS.20 tests one population relation about continued practice. | Open only the relevant question. A cross-scale decision can keep a trial closed; a trial decision can support one local use while wider receiving enactment or retention remains unknown. |
OPS.11 connects any of these uses to a dependency that could defeat the proposed use: for example, resource access granted for another interval or test evidence for another configuration. OPS.4 keeps the necessary claims recoverable for the participating decision makers. The detailed input and return conditions remain in the cited bodies’ Solutions and Relations.
OPS.Reference:10 - Conditions on a whole combination
When several operating moves are to be used together, judge their combined demands against the same actual operation and interval. OPS.10:4.2–OPS.10:4.4 supplies the resource and timing questions; OPS.12:4.4 supplies the comparison by affected group; OPS.13:4.2–OPS.13:4.4 preserves service and commitment conditions; OPS.14:4.4 preserves payment timing; OPS.17:4.4 and OPS.19:4.4–OPS.19:4.7 resolve consequential co-use conflicts. The whole chosen arrangement must fit the resources available in that interval, preserve each protected condition, comply with applicable rules and use evidence adequate for the claims on which it relies.
For each shared resource needed over a time window, combine the remaining demand from continuing Work with the additional setup, coordination, observation, recovery and trial work that the proposed moves require in that window. Keep setup, rework and reserves separate only when they are not already included in the service-time estimate. Compare the combined load with usable time under the required capability, configuration and access. Passing this necessary load bound still needs a feasible sequence where arrivals, precedence or simultaneous resource use matter. Check cash when payments fall due as well as at the end of the comparison horizon. A later receipt cannot fund an earlier payment unless available financing covers the gap.
Check the policies together too. A permitted incident exception can displace another start, reserve or commitment; identify that displaced consequence and the participant entitled to decide it. A local start policy, service objective, safety stop and provider permission can all constrain one action without having the same authority. Resolve an incompatible demand through the appropriate holders, or retain a bounded action plus the unresolved return. A favorable total throughput or financial result does not offset a breached protected service class or human condition.
The evidence used by the combination must refer to the same subjects, configurations, populations and relevant intervals, or state the qualified correspondence. A forecast of visits cannot be substituted for accepted packages, and evidence from an earlier provider arrangement may not support the current one. Separate what is already established from what an authorized intervention must still produce. The common result is a supported operating decision; claims about performance, acceptance and subsequent effect need evidence that covers each result.
PumpWorks makes the whole condition tangible. In its stated repeat scenario, two test completions plus the possible two-hour repeat use all six usable rig-hours. If a proposed Method trial also needs that rig in the same window, its demand must join that total. A separately feasible trial and a separately feasible service plan do not establish their coexistence. Extra rig access alone also leaves qualified relief, incident coverage, advance funding and field-release evidence to be established. The application therefore retains the six-hour service plan, defers the third package under its qualified later slot, and keeps the trial closed until its distinct coexistence conditions obtain. The later OPS.16 trial belongs to a later interval with those conditions supplied.
If a shared condition changes, reopen each combination that relied on it and the specific local result made stale by the change. Keep independent results whose subjects and conditions still match. A new resource window can alter admission and a service offer while leaving a valid subject account and a useful readiness rule available.
OPS.Reference:10.1 - Operational mantra: connect local work to accepted results
The operational mantra in OPS.23 helps practitioners recall the questions that connect local work, feasible provision and delivery. OPS.23 explains how to use their answers to judge what the operation can deliver and which decision a change reopens.
Use OPS.23 to connect the operating results a decision needs. Use OPS.19 when simultaneous work creates a conflict that calls for an operating choice.
OPS.Reference:11 - Check the combined decision and its result
Recognizing that one local gain can damage another result is enough to find a useful entry. Relying on a combined decision requires answers to the following substantive questions. Use an existing answer when it fits. Investigate a gap or a changed condition when it matters to the decision or to a claim the recipient needs to make.
- What must continue, for whom, and under which conditions? Recover the operating System, result, subjects, demand and commitments through OPS.1 and OPS.3. Preserve the recipient’s waiting and acceptance boundary when another view counts different events.
- What does each Method contribute to this decision? Recover its first useful result, current inputs and stopping condition from its body. If a direct rule already answers the question, use that result without adding a repertoire comparison.
- Can all parts of the arrangement work together under the shared conditions? Apply the preceding whole-combination condition to the combined resource use, policy interaction, protected results, funding and evidence. Use OPS.19 when reconciling the conflict is itself the missing operating result.
- What may the participants decide and perform now? Distinguish a proposal, admission, authorized intervention, performed Work and accepted result. OPS.5, OPS.6, OPS.13 and OPS.18 supply their different decision and evidence boundaries; the service or specialist authority remains explicit.
- What observation could change the decision or the conditions under which it is supported? Keep the relevant refresh or stop from the used body. For Method improvement, distinguish the local Method-change decision in OPS.16 from the population predicate and later interval in OPS.20.
The cases document three consequential misreadings of combined use. Moving incomplete matters out of the ready queue improves that queue’s appearance while leaving the recipient’s waiting unresolved; OPS.8 retains the earlier waiting origin. Reporting only completed requests can hide due but still-open commitments; OPS.15 reconstructs the receiving population. Extending the rig operator’s duty can improve utilization while consuming protected recovery and incident coverage; OPS.12 and OPS.19 change the operating arrangement. Inspect what the recipient receives and how the work affects the people involved.
OPS.Reference:12 - Architectural Rationale
The repertoire is organized around questions that can close separately. Admission can be decided while a later Work occurrence is still unperformed. A capacity bound can be established while service agreement remains open. An account can be correct while a quality response is undecided. A local Method change can be supported while wider retention remains unknown. Giving each result a direct entry makes those useful stopping points available and lets changed facts reopen only their real consumers.
Other arrangements are serious alternatives at a suitable scope.
| Alternative | When it is useful | Why this framework retains another choice |
|---|---|---|
| Use a current local rule or FPF plus one direct professional source. | One well-bounded question already has an adequate answer and no new operating synthesis is needed. | Across recurring operating questions, repeatedly reconstructing the domain units, service consequences and professional returns costs effort. OPS makes that shared reasoning available; it still preserves direct use when it suffices. |
| Adopt a connected Kanban, TOC, TameFlow, BPM or SRE arrangement. | Its Methods, evidence and objectives fit the operation and the practitioners can sustain them. | A school can supply useful combinations, but the operation also has commitments, case facts and protected consequences outside a selected school mechanism. OPS.17 compares the actual reusable moves and retains a whole arrangement only to its supported scope. |
| Coordinate through one project plan or process model. | Work and dependencies are sufficiently predictable and the chosen description answers the receiving questions. | Changing cases, recurring subprocedures, shared-resource queues and time-bounded changes can need different views of the same Work. OPS.2 preserves their correspondence without requiring every operation to use every view. |
| Optimize one formal resource or financial model. | The modeled feasible set, objective, resource relations and assumptions fit the actual decision. | The optimizer cannot supply omitted acceptance, permission or protection conditions. OPS.10 and OPS.14 use its qualified result; OPS.11 and OPS.19 preserve consequential relations outside that model. |
| Manage from one common dashboard. | Its observations, access and refresh are adequate for the participants’ decisions. | Displaying one account is a representation choice. OPS.3–OPS.4 preserve subject and claim meaning; OPS.15 can construct an account for the question. Use OPS.18 to assess quality or reliability. If the governing rule requires action, act within your authority or pass the finding to the participant authorized to respond. |
| Use one continuous-improvement cycle for all change. | It provides a useful local learning rhythm without merging the claims it handles. | Operating reconfiguration, a Method trial, repertoire maintenance and population continuation have different subjects and evidence. OPS.19, OPS.16, OPS.17 and OPS.20 retain those differences while sharing results conditionally. |
The control branch follows the same choice. FPF supplies control relations, views and temporal-claim discipline; OPS supplies the operating reason to use them and the resulting intervention question. A production controller, a service supervisor and a human decision maker can participate in different relations. Prefer the simpler coordination account when no control relation changes the decision.
OPS.11.1 and OPS.15.1 develop two constructions used by these decisions: an operating model connecting resource use, activities and order completion, and quantities calculated from the corresponding events. They retain shared resource use, branch joins, repeated work and unfinished cases where those change the answer. The model can then be compared with observations without mistaking a changed boundary or denominator for better service. Use the construction that supplies the missing model or quantity; reuse one that is already adequate.
OPS.Reference:13 - Apply the repertoire in production and service settings
The three applications use the same Operations distinctions among demand, commitment, Work, accepted result and evidence. Each starts from the operating result needed and checks whether the selected contributions can work together. The operating subject, practical gain, necessary professional contributions and evidence differ by setting.
| Operating setting and application | Domain-specific gain | Conditions that change from another setting |
|---|---|---|
| Production and controller test service — APP-OPS-01 and OPS.8–OPS.14 | Match eligible packages to real equipment windows, account for setup and repeated attempts, and compare a completion date with its accepted evidence and cash consequences. | Material/configuration correspondence, equipment access, qualified operators, product acceptance and field-release decisions matter. Busy equipment and additional attempts alone do not establish accepted service. |
| Public-hospital emergency service — APP-OPS-02 and OPS.12–OPS.15 | Coordinate the service that the supplied clinical decisions require, preserve cases still waiting, and expose conflicts between rooms, qualified team time, support work and recovery. | Clinical eligibility, priority, treatment, consent and protection are supplied professional results. A common service measure must retain consequential patient groups; the numerical probe supplies no clinical threshold or patient-outcome claim. |
| AI-assisted software operation — APP-OPS-03 and OPS.13–OPS.19 | Relate faster generation to qualified acceptance, incident recovery, test capacity and the actual user promise, while counting attempts, accepted changes and deployed-service events separately. | Provider/model conditions, review burden, configuration-specific evidence, security, software assurance and deployment authority can reverse the choice. Changed generation cost or episode count does not supply added acceptance capacity. |
Coordinator, performer, service recipient, resource provider and acceptance authority name participants through their contribution or authority in the case. The same participant can coordinate a case and accept its result when both responsibilities and the necessary authority are established. Count the demands of that participant’s existing assignments against its available time and resources. Changing their case allocation or dispatch order within current authority is an operating decision.
OPS.11.1 connects the product transformations, resource use, enabling conditions and commitment or authority relations needed for that decision. Its report-route example compares a new completeness check with unchanged acceptance authority, then contrasts changing who may accept the report. OPS.16 uses such a comparison to bound an improvement or trial. A proposed organization change can require new contribution, assignment or support relations; OCE supplies that work at its own scope. Acquiring and sustaining a new practice can also require development and introduction methods even when job titles stay unchanged. Include the time and resources needed for development or introduction alongside the work already promised.
OPS.Reference:14 - Gains, burden and limits of combined use
The combined use makes an operating choice explainable: which result it protects, which demand waits, which resource or authority is missing, what another participant must supply, and what observation could alter the decision or its grounds. It supports a truthful refusal or narrower service offer as well as a new start. Its costs are the observations, correspondence work, coordination and occasionally specialist analysis needed to make those claims. Reuse a current account or direct rule when it already answers the question; a larger model earns its effort only through a decision, assurance or recovery use.
The examples favor operations where cases, commitments, resource windows and result evidence can be recovered. Real operations can have incomplete records, unequal access to information and affected people whose burden is absent from the official account. OPS.12 asks those affected about displaced work and conditions; OPS.15 preserves missing observations and omitted populations. A manager’s account alone can therefore be insufficient even when its arithmetic is correct. Retain disagreement and professional limits instead of treating missing information as zero burden or permission to proceed.
The three constructed applications demonstrate the reasoning and its branches. The source and refresh account identifies what to reconsider when a professional premise changes.
OPS.Reference:15 - What this publication covers and leaves outside
The framework explains the construction and revision of operating units, dependencies and arrangements, and connects this knowledge to independently enterable questions about operating focus, views, subjects, current state, admission, continuation, priority, queues, constraints, capacity and structural coordination. The methods connect that work to affected people, supported promises, operating and financial consequences, useful accounts, bounded Method improvement, Method-repertoire selection, quality/reliability responses, reconciliation of simultaneous operating results, and deliberate cultural continuation. OPS.21–OPS.22 add the construction of meaningful operating aims and the interpretation of performance under changed conditions, while keeping service promises, capability assessments and reward decisions distinct.
A plan or calculation does not establish performed Work, accepted service, a health effect, field release, Method identity, causal improvement or later use by a practitioner population. Those claims require their own evidence, conditions, authority and specialist results.
OPS.Reference:16 - Intended use and ordinary non-use
Use this framework when a decision about continuing Work needs a better operating basis: the operation or subjects are unclear, current evidence cannot support admission or continuation, queues and resources conflict, human conditions, service, financial consequences, Method choice or quality require a decision, several operating results must be reconciled, a bounded population relation about continued practice must be tested, or the operation needs a meaningful aim or a reasoned performance assessment. Use the one pattern or small cooperating set whose result answers that question.
When an operating choice needs a specialist result, use suitable existing grounds or obtain the missing contribution from the practice that can provide it. Examples include asset engineering, organization change, human capability development, finance, governance, administration, strategy, safety, legal, medical, ecological and security judgements.
OPS.Reference:17 - PatternID and reader order
OPS.* is this framework’s PatternID namespace. The numbers are stable addresses. The ten Parts organize twenty-nine pattern bodies for reading, including six nested methods. A result dependency applies when one decision needs the matching result; Work can overlap, branch, repeat or start from existing inputs.
OPS.Reference:18 - Practical entry forms
Readme practical entries develop connected use through selected operating situations. Use the Table of Contents and full pattern bodies for another question. OPS.23 supplies the operational reasoning that connects local work to the receiving result.
OPS.Reference:19 - Source use and shared architectural choices
The framework connects Methods and Work with resources, transformation flows, queues, constraints and descriptions. Project, process, case, queueing, issue-tracking and operations-management viewpoints can concern the same Work. Changing conditions, improvement cycles and the scale at which a change is made affect which diagnostic and coordination results are useful. Each pattern develops the contribution needed for its operating question.
The Kanban Guide 2025.5, TameFlow sources, Reinertsen, Throughput Accounting and TOC, DEMO, integrated relation-specific structures, CMMN, DCR, OCEL, object-centric process management, layered control and LCA, statistical process control and SRE, DORA, harness engineering, and loop engineering each contribute bounded questions or Methods. Each body names the contribution it uses, its current limit, and the observation that reopens that use.
The comparisons in OPS.1:11 through OPS.7:11 start with capable incumbent arrangements: an explicit workflow, governed case/process integration, subject-correct histories, maintained incident coordination, policy-governed pull, outcome-aware case execution and consequence-aware service policies. OPS.3 retains its separate event/object question. The other bodies identify the decision their added receiving-result, permission, evidence or agreement distinction can change, the added cost of maintaining the distinction and when the incumbent approach suffices. OPS.2 connects rule selection and composition to OPS.17; the constructed OPS.5–OPS.7 matter connects a permitted start, limited diagnostic result, changed access and effective promise agreement without imposing a lifecycle. Each comparison identifies the part of the method affected and the change that would warrant revisiting it. The further comparisons in OPS.8:11–OPS.11:11 concern receiver-ready supply and purpose-specific protection, rival-based constraint diagnosis, variability-appropriate capacity/service analysis, and coordination across the structures involved. Primary queueing and coupled-scheduling sources qualify those uses; the published Whitt–You 2022 model supplies the same bounded network-analysis line as its 2020 preprint. These comparisons do not rank one source family across all eleven questions.
Revisit the use of a source when its revision changes the action, identity, relation, view, account or stopping condition on which the pattern relies. Use the comparison conditions in that pattern’s SoTA-Echoing section to decide whether a proposed source change improves the current guidance.
The comparisons in OPS.12:11–OPS.18:11 extend this basis to changes in work demands, staffing and support, supported service promises, incremental cash and constrained-resource models, observation populations, bounded Method trials, conditional Method composition, quality-control questions and incident prevention. HSE and NIOSH contribute work-demand and intervention guidance; ACCA contributes relevant-cost and throughput-accounting reasoning; the SRE Workbook and NIST handbook contribute service-indicator, monitoring, capability and acceptance distinctions. OPS.18 also adapts Ries’s chapter 11, LEI’s Five Whys guidance and the 2016 SRE postmortem chapter for reconstructing contributing conditions and choosing supported prevention. Their assumptions and professional limits remain explicit in the bodies. Historical methods are identified as such; a source’s date or maintained status alone does not establish the strongest answer for the operating question.
OPS.16:11 compares its exact Method or candidate-account return with competent PDSA, preserving prediction, observation, adaptation and the separate implementation decision. OPS.19:11 compares the same cross-scale allocation with a capable bounded integrated arrangement. OPS.20:11 compares bounded cultural continuation with adaptive SRE practice, including receiving support, migration burden and voluntary uptake. Each may reuse a sufficient incumbent account; an added distinction must improve the choice or its grounds enough to warrant its total cost. Use the cited work on interacting structures, operating finances, improvement and service change within the scope established in the relevant pattern. None of these patterns claims a universal school, comparative effectiveness across domains, or transfer beyond the named conditions; each body states the observation that reopens its source use.
OPS.11.1 draws on conceptual modeling to choose scope and detail while representing shared resources and order completion. OPS.15.1 uses relationships between events and their participants to construct intervals and aggregates. Their source discussions distinguish finite event histories from steady means, and modeled capacity from the work and resources available for the required interval.
Queueing and scheduling provide complementary constructions in OPS.10.1 and OPS.10.2. A mean comparison can distinguish fast but variable service from slower predictable service; it does not settle an individual deadline. A finite schedule can establish attainability under shared resources and calendars; protection against uncertain delay additionally needs a disturbance or probability account. The bodies compare these source contributions at the question they answer, retaining the cost and limits of a richer model.
OPS.8.1 compares release signals while retaining known visits and possible returns. OPS.8.2 distinguishes capacity left over after protection from temporarily used reserve, then constructs its return to service. Factory Physics, TameFlow, workload-control studies, interruption research and computational preemption contribute different mechanisms and limits. Together, the two bodies connect the release decision to feasible recovery; they do not make final acceptance a universal release signal or idle time universally available for development.
OPS.Reference:19.1 - Operating aims and performance sources
Bjarte Bogsnes, Implementing Beyond Budgeting: Unlocking the Performance Potential, second edition (Wiley, 2016), chapter 4, printed pp.142–159 and 182–190, supplies the developed historical practice account used in OPS.21–OPS.22. Jeremy Hope and Robin Fraser, Beyond Budgeting (Harvard Business School Press, 2003), chapters 4–5, pp.69–116, connects targets, current outlook, provision, coordinated action and assessment, including implementation failures when the wider management uses remain unchanged. The adopted connection does not prescribe either source’s complete organizational model.
Bukh, Ringgaard and Sandalgaard, “Moving beyond Beyond Budgeting” (2025), pp.1221–1244, examines one Scandinavian bank that abandoned and later reinstated budgets. Its retrospective interviews and documents show changing uses of forecasts alongside retained or restored budget controls. This case illustrates how forecasts and budget controls can serve different purposes together. To decide whether to adopt that combination elsewhere, compare its conditions with the operation in question. One author disclosed a board position. The case supplies no general causal estimate of performance gains. OPS.21–OPS.22 retain the functional distinctions and reopen the arrangement when practice contradicts its intended use.
In “Forecasting, goals and planning”, Hyndman and Athanasopoulos distinguish a forecast of what is likely, a goal for what the operation should achieve, and a plan for acting. OPS.21 uses that distinction to develop an operating aim. OPS.22 uses the actual results, changed conditions and contributions to make a performance judgement.
OPS.Reference:19.2 - Shared source choices for the repertoire
The shared architectural choice is to combine source contributions by the operating question they answer. The following comparisons explain that choice across several bodies; each cited method’s SoTA-Echoing section explains its mechanism, illustrates the distinction and identifies what could change its use.
| Professional answer | Contribution adopted or adapted in OPS | Alternative, limit and reason to reconsider |
|---|---|---|
| The Kanban Guide 2025.5 defines a workflow, controls started work and relates a service expectation to elapsed time and probability. | OPS.5, OPS.8, OPS.13 and OPS.17 use explicit boundaries and policies for admission, waiting and forecasts. | Retain a bounded Kanban use where it answers the question. For a wider operating decision, also recover case facts, commitment authority and resource conditions. Reconsider the selected policy when item boundaries, demand or the service population change. |
| TameFlow’s complete-kit and constraint-protection mechanisms, Reinertsen’s economic flow trade-offs, and the queueing comparisons in OPS.8:11–OPS.10:11 answer different waiting questions. | OPS adapts receiver-ready supply, comparison of rival explanations when treatment depends on the cause and analysis chosen for the required service claim. | Replenishment must arrive in time to preserve protection. A pooling change can alter processing behavior; a finite deadline or accumulated waits can favor treatment away from the sustained-throughput constraint. OPS.8–OPS.9 compare these choices and the effort of stronger diagnostics. Retain the cheaper adequate policy or bound, and reopen when behavior, regime or the receiving result changes. |
| CMMN 1.1, the DCR execution documentation and OCEL contribute authorized case planning, outcome-aware execution and multi-object evidence. | OPS.2 and OPS.6 reuse a competent integrated contract and add only a missing subject-state, permission or rule-composition distinction; OPS.3 and OPS.15 retain their event/object contributions. | A fixed subprocedure or sufficient case contract remains in use. An execution outcome supports only the external subject claim justified by its evidence. OPS.3 uses current object-centric data-quality work to correct a faulty relation or time meaning locally, preserving unaffected claims. Reopen when changed facts, permission or a missing relation can alter continuation. |
| The coupled-scheduling and several-network sources discussed in OPS.11:11 connect material and transaction requirements to shared resources. | OPS.11 and OPS.19 retain a coupling when it can alter the operating choice or the conditions that justify it, then coordinate the affected choices. | A full network model may be useful for strongly coupled scheduling; one simple binding condition can suffice for a local decision. The cited industrial models and perspectives do not establish an obtaining relation or autonomous coordination in another operation. |
| HSE’s work-demand guidance and NIOSH’s Total Worker Health hierarchy address the demands and arrangements that produce human burden. | OPS.12 adapts changing the source of burden; OPS.13, OPS.17 and OPS.19 preserve supplied human conditions in the combined choice. | Individual support can help, but cannot resolve incompatible duties by itself. The sources supply no universal workload threshold. Reconsider the intervention when the affected people, demands, support or qualified protection change. |
| ACCA’s relevant-cost reasoning compares cash consequences that differ because of a choice. | OPS.14 connects incremental payments and receipts to accepted service, displaced uses and timing; OPS.13 and OPS.19 use the resulting financial premise. | A short-horizon throughput model can help with a fitting resource-mix question. Funding, long-lived investment or accounting recognition can require another qualified result. Reopen when avoidability, displacement, acceptance or the horizon changes. |
| The SRE Workbook’s service-indicator treatment distinguishes user-relevant behavior from its measurement; the NIST process-monitoring and control handbook separates statistical monitoring and acceptance questions. | OPS.13, OPS.15 and OPS.18 adapt the observation boundary and select the evidence branch needed for a service, process, lot or recovery decision. | A supplied acceptance rule or direct protection can suffice. A monitoring choice also pays for inspection, false/repeated signals and the work of responding; grouped observations or drift can change its detection basis. OPS.13 and OPS.18 work those returns without treating software error budgets as safety permission. Reconsider when the population, response or required decision changes. |
Anderson’s Kanban (2010) combines operating mechanisms with an approach to evolutionary change; later Kanban principles explicitly distinguish service delivery and change management. OPS uses their contribution to admission, release, queues and flow while separately considering how a changed practice can become usable. Dietz and Mulder’s Enterprise Ontology (2020), §§4.4.4–4.4.6, helps distinguish product-making from request, promise and acceptance relations. OPS.11.1 retains those relations in the operating model without treating every new assignment as a new authority structure. A source’s single programme can therefore contribute to several domains; its title does not allocate all of its methods to one DPF.
Tendon and Doiron’s Tame your Work Flow (2020), chapters 6–8, connects a proposed production improvement to a package that customers can use and to its financial consequences. OPS.1 and OPS.13 retain the receiving result and commitment; OPS.14 compares the future payments and receipts that differ between feasible alternatives. Shared contributions belong in one combined comparison, with each receipt and payment counted once. The book’s instructional cases do not establish that higher physical throughput necessarily increases financial throughput, or that one accounting model resolves participants’ disagreements.
Chapter 21 presents its starter patterns as prototypes and an illustrative route. Its organizational vertical slice connects performers and successive management responsibilities; the relation among those responsibilities differs from the relation between a method and its constituent methods. OPS.17 selects usable operating moves and their conditions, while OPS.20 addresses their continuation among practitioners. OPS.13 and OPS.18 connect signals to response timing and supported corrective action. The full starter sequence, CEO participation and financial throughput as a single objective apply only where that organizational arrangement and purpose fit; they are not prerequisites for an ordinary local operating decision.
Tendon’s The Book of TameFlow (2022), pp. 194-203 and 241-247, contributes the connection between a useful outcome, its work package and preparation involving the people who will perform it. OPS-PREPARE-AND-RESPOND combines that contribution with the current service, resource and financial methods. The package boundary follows the recipient’s needed result; a financial throughput measure is useful only where its assumptions fit that decision. Pages 249-269 connect execution changes to future admissions and focused management attention. OPS.13 supplies response timing, and OPS.8.2 checks whether a proposed assisting resource can be released and restored in time. Source-specific prescriptions about immutable queue positions, a compulsory common deadline or a universal ban on concurrent work are replaced by comparison of the affected commitments and feasible arrangements.
These sources explain why the operating methods are organised this way. To establish that this arrangement works better than another, compare their performance for the operating use in question. A stronger professional result can replace one analysis or coordination contribution while preserving the other Methods. Reopen the architecture itself when repeated use shows that the question boundaries systematically hide a needed operating result, or when an integrated alternative preserves the relevant subjects, commitments, protections and evidence at lower total burden.
Competent improvement and adoption practices are also reusable sources. IHI’s PDSA testing guidance and implementation guidance supply the improvement comparison in OPS.16. Google SRE’s incident management and organizational-change account supply maintained coordination and adaptive receiving support for OPS.4 and OPS.20. Use these contributions directly when they suffice. Add an operating distinction when it could change the decision or what its recipient can justifiably conclude.
The bibliographic returns give edition and publication details for shared works cited here.
OPS.Reference:19.3 - Grounds for the disciplinary account
The professional field is wider than short-term dispatch. The Manufacturing & Service Operations Management editorial statement includes descriptive, predictive and prescriptive contributions at strategic, tactical and operational scopes. Charles Fine’s MIT course is a historical teaching treatment of the connection between product development, process management and supply chains. OPS adopts the need to connect operating design and use while obtaining product engineering, organization design and other specialist results from the practices that can supply them.
Hopp and Spearman (2004), §§5–6, supply the manufacturing mechanisms adapted in OPS.Reference:1.4 and OPS.11.1:4.2a: the inventory/order interface, explicit work-in-process limits and alternative buffers. Their production setting leaves the transfer to service or discovery to be established for the receiving subject and result.
Kim and Whitt (2013), §§1–2, show why applying Little’s law to finite observations requires attention to interval boundaries and the statistical question. This supports the distinction between an identity, an estimate and a promise in OPS.Reference:1.3. The full event construction remains in OPS.15.1. A reliable accounting relation cannot by itself select a desired result or establish a causal explanation.
These sources support different parts of the account. The construction connecting result, work units, provision and selective revision is the framework’s synthesis. Retain an adequate existing professional treatment when it already supplies that connection. Reconsider the account when a different kind of operation defeats its stated relation, when a supplier leaves a promised contribution unavailable, or when another arrangement supplies the same result with a better supported balance of consequences.
OPS.Reference:20 - FPF dependency and compatibility
The OPS methods are described in their pattern bodies. The Table of Contents, SoTA-Echoing and Relations identify their external FPF contributions and receiving uses. For an OPS use that requires an FPF contribution, open the current FPF edition, identify the needed pattern edition, and check that its content and use conditions provide the stated contribution. When later reliance depends on the edition used, keep a permanent link or copy of that edition. If the contribution is unavailable or no longer fits, keep the dependent use open and reconsider the affected OPS pattern and dependent conclusions. Unaffected results remain reusable.
Direct uses. FPF supplies System recognition, direct relation and selected-structure governors, Work and WorkPlan distinctions, Methods and descriptions, claim-bearing accounts, evidence and provenance, time and currentness, mathematical-lens use, control relations and views, Work-performance recovery, comparison, choice, simultaneous Work, and culture mechanics. Operations Management retains operating subjects, commitments, domain quantities and Methods, evidence, authority, interventions, service and production consequences, and receiving decisions.
Compatibility. A compatible FPF change leaves unaffected OPS results reusable. A changed relied-on kind, relation, Solution, predicate, or result form reopens the consuming OPS pattern and its dependency claim. Qualify that affected use before relying on the changed contribution.
Authority direction. FPF does not depend on this DPF for its transdisciplinary results. A transdisciplinary discovery returns to FPF through its own decision and review. An Operations-specific remainder found in FPF returns to this DPF and is removed from the general host rather than duplicated.
OPS.Reference:21 - Sibling-domain returns and availability
Use the FPF contributions and professional sources named in the method when the operating question needs them. Some choices also depend on a qualified clinical, safety, legal, privacy, security, financial, product-release or capability result. Use an applicable result already available, including a documented decision or permission when one is required. If it is missing, take the question to the qualified provider or the party entitled to decide and identify what depends on the answer.
OPS.16 uses the published Method Engineering trial, coherence, fit, worth, lineage and bounded-introduction guidance. OPS.11.1 models the affected transformation network and its proposed change; OPS.10–OPS.13 and OPS.19 can establish the resource and service conditions its trial needs. OCE supplies changed organizational relations and their realization when those are needed, with OCE.11 coordinating change and continuing service. Existing assignments and authorized operating allocations remain inputs to the Operations resource account. OPS.17 uses the published Method Engineering repertoire guidance. OPS.20 uses the current FPF and Method Engineering cultural-continuation contributions while retaining the Operations population, predicate, supported continuation, evidence and needed authority; intervention is conditional on the selected work. OPS.12 can use Organization Change Engineering’s consequence comparison when the intervention changes the organization. For the decision in hand, check whether a suitable result is already available. If a required capability, staffing arrangement, cultural condition or consequence remains unknown, obtain the missing result or state the limit on the decision.
Strategy retains direction and strategic commitments; Corporate Finance financial decisions; Corporate Governance and law authority; Organization Administration enabling conditions; Maintenance restored asset functioning; Systems Engineering product/service engineering and assurance; Human Capability Development one human’s capability development; and other specialists their own subjects, Methods, evidence, and authority. Use an applicable existing result or a qualified direct source. If neither supplies what the decision needs, identify the missing result and how it limits the decision.
The following direct returns help when the operating question exposes work owned by a neighboring framework. Use the corresponding guidance when it can supply the missing result. The returned result must fit the operating subject and conditions.
| Missing result in the operating situation | External guidance and practical return |
|---|---|
| An organization change competes with continuing service for coverage and support. | OCE.11 guides the work of agreeing and operating a bounded arrangement for change alongside service. OPS.16 needs grounds that the trial fits that arrangement. Evidence of how it worked comes from operation. OCE.13 supplies consequence comparison when the changed subject is the organization arrangement. |
| The required contribution of one human is unclear, or a training proposal is being used as a capacity answer. | HCD.1 derives demand from that person’s representative later Work and returns diagnosis, profile or non-training questions as appropriate. A demand account supplies neither present capability nor usable staffed capacity; OPS retains the current service and allocation decision. |
| A changed prompt, tool, procedure or support arrangement may change the reusable Method. | FPF A.3.1.MV distinguishes reusable semantic change from description, support and local-Work changes and preserves candidate status. OPS.16–OPS.17 retain the operating effect, feasible use and repertoire decision. |
| The operation needs a separately prepared inquiry, comparison or recommendation, and the support engagement is unclear. | Use PSDA.11 to establish the question, intended use, recipient and terms of the support. An assessment of a known operating method can finish with a supported finding about its suitability. If a choice is required, identify its holder and use the applicable decision rule. An operating choice already formed with adequate inputs can proceed through the relevant OPS Method. |
| A wish to develop the operation precedes any clear worthwhile contribution or adequate alternatives. | FPF C.40.OI bounds the subject, receiving use, horizon and affordable opportunity inquiry. If the operating difficulty and adequate alternatives already exist, use the direct operating or decision-support result. The opportunity inquiry grants no service commitment or implementation authority. |
Use the linked contribution while its current content supplies the stated result and boundaries. Keep the edition or copy actually used with a consequential receiving result. If a supplier’s content, availability or case conditions change, requalify the affected return; unrelated OPS uses remain available.
OPS.Reference:22 - Available contributions
The Table of Contents gives direct access to the Methods published here and identifies their working questions and dependencies.
OPS.Reference:23 - Representative case coverage
Use OPS.Reference:13 to compare the applications’ operating settings, gains and professional conditions; their full reasoning is in the Cross-Pattern Application.
OPS.Reference:24 - Edition return
This publication contains the Readme, Table of Contents, Architectural Reference, ten Parts, nine connected practical entries, three extended applications, framework boundary and the pattern bodies listed in the contents.
Use any of the twenty-nine patterns whose working question and conditions match your situation. Combine them when one needs another’s result. Each body states the professional contributions, evidence and authority its use requires.
In the earlier edition, OPS.5:4.1 (another source edition) and OPS.6:4.2 (another source edition) correspond to Recover the inputs needed for admission and Establish the current conditions for continuation in this edition.
Earlier OPS.11:4.3 (another source edition) corresponds to Recover the couplings that matter to the decision. Earlier OPS.11.1:4.5 (another source edition) corresponds to Refine the part on which the answer depends.
Earlier OPS.15:4.1 (another source edition) corresponds to Identify the receiving question. Earlier OPS.15:4.5 (another source edition) corresponds to Stop when the evidence suffices and refresh when its grounds change.
Earlier OPS.15.1:4.1 (another source edition) corresponds to Choose the quantity that answers the operating question. Earlier OPS.15.1:4.6 (another source edition) corresponds to Report the quantity for its intended use.
Earlier OPS.19:4.3 (another source edition) corresponds to Select the structures on which the choice depends.
Earlier OPS.20:4.4 (another source edition) corresponds to Identify the participants and arrangements on which the claim or decision depends. Earlier OPS.20:4.5 (another source edition) corresponds to Compare explanations that matter to the claim or decision. Earlier OPS.20:4.8 (another source edition) corresponds to Return the cultural account and any requested decision.
Earlier OPS.22:4.1 (another source edition) corresponds to Identify the question and recover the comparison.
OPS.Reference:25 - Publication boundary
Pattern bodies are the authoritative working references. The Readme, Architectural Reference, Table of Contents, practical entries, and applications help readers enter and combine them; they do not replace conditions, evidence boundaries, stops, or specialist returns.
The complete method bodies support direct use. The Architectural Reference explains how they fit together, the alternatives and the grounds for choosing among them. An educational Guide supports learning and memory, while a Suite Architectural Reference explains the connections among its frameworks.
For source qualifications, citation and edition information, see the Sources and Edition Notes.
OPS.Reference:End
Part I — Bound the Operation and Select Coordination Views
OPS.23 - Connect Operational Reasoning — The Operational Mantra
Type: Method pattern Status: Stable Normativity: Normative within the stated operating use.
OPS.23:1 - Problem frame
Use this when individually plausible answers about local work, delivery, capacity, service, money or people’s working conditions do not yet explain what the continuing operation can actually deliver. An assigned task can finish while its recipient still waits. A team can speed up processing while its service promise becomes infeasible. The needed result is a connected operating judgement: what can proceed, what must change, or which missing answer prevents a responsible decision.
The first useful move is to name the result the recipient must be able to use and follow one proposed local action to that result. Where does its contribution become usable, and which other condition must hold? Reuse current answers; pursue a missing connection when it could change the operating choice or the grounds for relying on it. Ordinary prose, a sketch or a current shared account can suffice.
Use a direct OPS Method when it already supplies the whole answer. An isolated capacity calculation, a known permission rule or a settled service decision does not require reconstruction of the whole operation. Use OPS.19 for an identified conflict among simultaneous work; this pattern also applies before such a conflict has been found. It supplies reasoning, not specialist judgements, missing resources or authority.
OPS.23:2 - Problem
Operating decisions are often made from different local accounts. A completion count, a queue view, a resource calendar, a service promise and a cash forecast can each be correct while their combination is impossible or useless. Conversely, requiring a complete enterprise model before any decision delays an adequate local result. The practitioner needs to assemble just the mutually relevant answers and preserve their conditions through a change.
OPS.23:3 - Forces
| Force | Tension |
|---|---|
| Local progress and receiving use | A finished task can supply a needed intermediate result or merely increase unfinished inventory. |
| Speed and continuing provision | Faster processing can consume recovery capacity or leave the decisive wait untouched. |
| Shared judgement and authority | Participants can expose an incompatibility without being entitled to change each other’s commitments. |
| Coherence and unnecessary reconstruction | The whole needs compatible answers, but an unchanged sufficient answer should not be rebuilt. |
| Immediate protection and learning about causes | A supported response can protect service while the reason for recurrence remains unresolved. |
OPS.23:4 - Solution
Use this mantra to connect the work of a person, team or other contributor to what the operation can deliver. Follow a local action through to the result its recipient can use. The short form is:
Accepted result → route and readiness → limiting conditions → release and feasible order → service, money and human conditions → observed result and changed conditions.
These are connected questions to keep in attention. Their answers constrain one another. Start wherever a missing answer could change the present decision or its grounds, and use adequate answers already available. OPS.Reference:8–OPS.Reference:11 explains the connections with other operating methods.
Relate local work to a result the recipient can use. Identify the operating system, required result, acceptance boundary and commitments through OPS.1 and OPS.3. Follow the work and its required inputs through the relevant workstations or contributors. Locate the local contribution in that route: producing an intermediate item, making later work ready, handling a return or preserving service can affect the whole differently. A completed local task is useful on this account when the receiving work can use its contribution. OPS.11.1 develops the connection between local routes, shared resources and order-level completion. When the route or work unit is itself missing, its :4.2a constructs operating alternatives from the required result and available professional methods; an unavailable method returns to its subject discipline. The judgement can therefore begin before an adequate operating arrangement exists. When the required system or its intended use remains unclear, FPF A.1.STM supplies the connected system-thinking questions; an operating calculation cannot settle that earlier choice by itself.
Find which condition limits the result under the present demand. Work can wait because an input or permission is missing, because usable capacity is insufficient, or because the selected order delays a needed completion. OPS.8 and OPS.9 distinguish these causes; OPS.10 qualifies capacity over the relevant interval. Improving an already non-limiting station can increase intermediate inventory without increasing accepted output. Conversely, protecting the limiting station may require work elsewhere. The target matters: shortening the time to a first accepted result and increasing sustained output can require different changes, as OPS.9:5.4 explains. To identify the constraint, relate the queue or occupied resource to the result being limited.
Choose starts and order from those conditions. Use OPS.2 to select the relevant management view, OPS.8 for release and queue rules, and OPS.10.2 when a deadline needs a feasible schedule. Count waiting from the recipient’s relevant starting event; moving an incomplete item off a board does not remove that delay. Include returning work, setup and recovery where they consume the same capacity. A calculation of total required hours supplies a necessary bound, while precedence and simultaneous resource requirements can still prevent a schedule. Priorities need the decision’s supported consequences and available authority. OPS.14 compares financial consequences on a common basis; its indivisible-job case shows why a value-per-hour ranking need not select the best feasible set. An unknown monetary estimate does not establish that work has no value.
Require the combined promise to be feasible. The whole-combination conditions in OPS.Reference:10 apply to continuing service and the proposed change together. OPS.12 preserves the affected people’s required conditions, OPS.13 relates service commitments to available provision, and OPS.14 checks payments when they fall due. OPS.19 reconciles conflicts that otherwise valid local decisions leave unresolved. PumpWorks in OPS.19:5.1 shows the consequence: two test completions and a possible repeat exhaust the same six rig-hours, so a separately feasible Method trial cannot also use that interval. Qualified relief, incident coverage and funding remain separate conditions even if more rig access can be obtained.
Return observations to the answers they change. OPS.15 keeps the observed result and its population clear; OPS.18 distinguishes containment, correction and evidence about recurrence. If a constraint moves, a return consumes a reserve or an input becomes unavailable, reconsider the starts, commitments and resource choices that relied on the earlier condition. Keep unrelated valid results. A change to the way of working uses OPS.16 with its own trial conditions, including coexistence with continuing service. If the work extends to development for further problems, use FPF C.40.OD to establish its purpose and means. The operating account supplies the conditions that undertaking must meet.
The same reasoning applies at a workplace and across an organization. Within the authority already given, a contributor can revise a local choice from the shared operating facts. A change to a commitment, resource allocation or protected condition outside that authority goes to the party entitled to decide it.
OPS.23:4.1 - Assemble the decision and select its next useful question
Keep the receiving result, proposed action and the conditions on which their connection depends in the same account. For each consequential claim, distinguish an observed fact, a justified forecast, an authorized commitment and an unresolved condition. A promised specialist is not the same as an available specialist; a planned acceptance is not an accepted result. Use OPS.4 and OPS.15 when recovering these facts is the difficulty.
Follow a suspected mismatch in both directions. If a test may finish late, identify the input, resource window or ordering constraint that could explain the delay and the accepted promise that depends on the test. If a promise changes, trace it back to the work and provision it requires. Use the relevant method or its available result to establish whether the promise can stand, what supports that conclusion and whether a change needs a decision from the party responsible.
A current sufficient answer closes the question. Otherwise choose the next inquiry, coordination or permitted operating action by what its result could change about the choice or its grounds. If a fact or decision is still missing, identify the work it limits. Independent work can proceed when its conditions and authority are established.
A plausible mismatch is enough to select this Method. Reliance on a schedule, service promise, causal diagnosis or protected human condition needs the corresponding qualified result.
OPS.23:5 - Archetypal Grounding
OPS.23:5.1 - Four ready packages do not imply four accepted results
Use the constructed PumpWorks conditions in OPS.19:5.1. Four packages are ready; each requires two rig-hours; six hours are available; one possible two-hour repeat must remain protected. The resource account permits two selected packages and that repeat: four hours of initial tests plus two reserved hours. Starting all four would require eight hours before any repeat. Readiness therefore supplies one premise of release, not a sufficient start rule.
Connecting the answers changes more than the count. An incident consumes the change interval and interruption reserve; qualified specialist relief is unavailable. An extension would defeat incident coverage and recovery even if more rig access could be arranged. The qualified financial account supports later completion of the third package, but supplies no disposition for the fourth. The resulting judgement retains two starts, protected repeat capacity and incident response, returns the fourth package’s later disposition as an unanswered question, and keeps the Method trial closed. OPS.19 explains how the people responsible resolve this conflict within the rig, service, financial and staffing constraints.
Suppose additional rig hours are offered while specialist relief is still unavailable. Reopen the rig premise and its affected schedule; retain the independent support restriction. The offer alone does not permit the extension or trial. Conversely, if both support and service conditions later change, recover their actual answers before reusing the earlier refusal.
OPS.23:5.2 - One workplace can need the same connection
A technician has a finished repair and wants to begin the next. Under the stated working conditions, the recipient can use the repair only after an acceptance test, and the test fixture will be free in the afternoon. Preparing the required test input now can advance the accepted result more than beginning another repair. If that preparation is already complete, a permissible independent task can proceed instead. Relate the local choice to the missing contribution and current permissions.
If the recipient cancels the afternoon acceptance window, the technically finished repair remains finished. The service promise and useful next action change. Seek the revised receiving decision instead of reporting the local completion as delivered service or silently making a new promise.
OPS.23:6 - Bias-Annotation
Visible tasks and well-recorded resources can crowd out recipient use, support work and the conditions of less powerful participants. Use available evidence about affected contributions and burdens. Where a participant’s conditions remain unclear, ask the participant or a source able to establish them. Neither a monetary estimate nor the easiest available dashboard is a universal measure of the result.
OPS.23:7 - Conformance Checklist
- The local action is connected to a result its recipient can use.
- Ready input, usable capacity, feasible order, permitted action and service agreement remain distinguishable.
- Shared resources, returning work and protected conditions are included where they change this decision.
- The account states a supported continuation, a specific question or a justified stop; an unknown is not silently made favorable.
- A changed premise reopens its dependent answers, while independently sufficient results remain usable.
- Recognition of a problem is not presented as assurance of a schedule, causal account or service result.
OPS.23:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| Maximize activity at each workplace | Follow the contribution to the accepted result and the condition currently limiting it. |
| Replace whole feasibility with a sum of hours | Recover ordering, simultaneous resource needs, support and receiving conditions. |
| Repeat every analysis after any change | Identify which premise changed and follow the answers that depend on it. |
| Recite the mantra as a workflow | Choose the current question from available answers and what the answer could change about the decision or its grounds. |
| Let the most complete account confer authority | Return commitment changes to those entitled to make them. |
OPS.23:9 - Consequences
Participants can explain why a local action helps, why an apparently feasible start remains unavailable and what a changed condition reopens. They can retain adequate partial answers. The cost is recovering consequential relations and obtaining qualified missing answers; the Method earns that cost only when the direct local treatment leaves the operating judgement incomplete.
OPS.23:10 - Architectural Rationale
Assemble and revise the operating judgement from the answers the current decision needs. Use applicable specialist results and obtain a missing one when it matters to the judgement. OPS.19 can resolve an identified conflict. At any scale, readiness, authority to start, local completion and use by the recipient can differ. The short mantra recalls these connections. A claim that learners do better with this form than with another would need a comparison of their learning.
OPS.23:11 - SoTA-Echoing
The serious smaller alternative is direct use of a competent current workflow and its operating rules. The Kanban Guide, May 2025, sections “Why Use Kanban?”, “Defining and Visualizing the Workflow” and “Improving the Workflow”, connects value, workflow definition, active management and improvement. It permits multiple workflow definitions and additions for the local setting. Reuse such an account when it already makes the relevant promise, provision and response clear.
Connect contributions when the current workflow leaves them separate. At PumpWorks, the rig schedule leaves open specialist relief, incident coverage, recovery and the disposition of the remaining packages. Establish what is known about each and reconcile their consequences. OPS.8–OPS.14 and OPS.19 give the conditions for using their flow, scheduling, service and financial results. The case shows what combining the answers adds here. Comparing the two approaches across operations would require evidence from those uses.
Keep the simpler arrangement if it supplies the same judgement with less reconstruction. Reopen this choice when an operating method supplies the missing connection directly, a changed receiving condition invalidates a join, or use shows that maintaining the account costs more than the decisions it improves.
OPS.23:12 - Relations
OPS.1–OPS.15 and their nested Methods supply the relevant operating answers. OPS.19 reconciles actual cross-scale conflicts; OPS.16–OPS.18 address Method change and quality; OPS.21–OPS.22 distinguish aims from performance interpretation. STR.18 connects a changed operating possibility to direction and commitments when that strategic question is live. FPF A.1.STM supplies system-project reasoning and C.40.OD the distinct continuation of development. The Architectural Reference explains the language and its field boundaries; this pattern supplies the operational reasoning Method.
OPS.23:End
OPS.1 - Identify the Operating System, Commitments, and Flow Units
Status: Stable
OPS.1:0 - Use This When
Use this pattern when you want to improve a process, clear a backlog, raise utilization, accelerate flow, or redesign a board but cannot yet name the operation whose result must continue. Typical warning signs are an organization name used as the operating boundary, one ticket called the customer need, a queue column treated as the Work, or a service promise discussed without its parties, conditions, or horizon.
The first useful result is one bounded operating focus. An existing account or a short statement can carry it:
For this decision and horizon,
OperatingSystem-Xmust continue supplyingResult-or-Service-Y; current demand and commitments are...; the decision-bearing subjects and counted units are...under these identity rules; any boundary, authority, evidence or control question that still affects this decision is....
That statement is useful before a workflow, target, priority, or policy is chosen. Use this focus in OPS.2 if coordination needs a decision, or in OPS.3 if subject identities or relations need clarification.
Recognition is cheap: enter when a practical decision cannot name its operating System, continuing result, commitments, or tracked unit. Assurance is claim-specific: System identity, commitment, Work, subject identity, authority, evidence, safety, value, and effectiveness use their own governing patterns and specialist Methods before reliance.
Use an established operating boundary when it already answers the decision. When an outside result determines the answer, use the relevant specialist contribution. For example, the question may concern a product or asset change, organization change, a person’s capability, finance, law or safety. Return to the operating focus if the contribution changes its boundary, use or grounds.
OPS.1:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| operating System | One actual System whose continuing operation and results are current for the decision. It is not inferred from an organization name, process diagram, product label, software tool, or reporting boundary. |
| continuing result or service | The result, service, or preserved condition the operation must keep supplying to a named receiver under stated conditions. Continuation does not prove value, quality, acceptance, or fulfilment. |
| demand | A request, need, condition, candidate Work claim, arrival, or other input entering the operating decision. Demand is not automatically admitted Work or a commitment. |
| commitment | A promise or obligation with parties, promised result or service, conditions, horizon, authority, and current status. A due date or priority label alone is not a commitment. |
| operating subject | The exact System, item, case subject, material, service relation, account, or other entity whose state or relation can change the operating decision. |
| flow or case unit | A decision-specific counted or tracked unit with an identity rule and receiving use. Treat Work items, cases, physical items, batches, transactions, commitments, and results as different units unless their identity rules and evidence establish that the labels denote the same counted or tracked unit for this use. |
| operating boundary | The included subjects, Work, resources, relations, environments, and time horizon needed for this decision, with consequential exclusions and any needed specialist contribution. |
| control-relevant operating concern | A question in which observation, decision, actuation, supervision, feedback or unlike rates can change coordination. It calls for the relevant control account, with a formal structure or view only when that claim is needed. |
| operating-focus result | The bounded operating System, continuing result, demand, commitments, subjects and units, with the boundary and grounds needed for the current decision. Include a missing condition or further use when one remains. |
OPS.1:1 - Problem Frame
Operations work begins in the middle. Demand has arrived, commitments already exist, cases are open, resources are shared, records disagree, and service must continue while changes are considered. Familiar representations make that situation look simpler than it is. A board foregrounds Work items, an organization chart foregrounds positions, a process map foregrounds recurring order, and a product model foregrounds the engineered object.
Answering the operating question may require several of these representations. A useful starting boundary therefore comes from the continuing result and present decision, then identifies the actual operating System, commitments, subjects, and units needed to decide.
OPS.1:2 - Problem
Without an operating focus, later optimization can improve the representation while degrading the operation. A team can shorten one board column while customer cases age, increase resource utilization while service commitments fail, count ticket closures while the field condition persists, or optimize product-control performance while release and incident-response Work remain blocked.
The failure propagates. Queue, constraint, capacity, quality, service, finance, and Method-improvement decisions inherit the wrong boundary and unit.
OPS.1:3 - Forces
| Force | Tension |
|---|---|
| Urgency | A visible backlog invites immediate action, while an incorrect operating boundary makes the action locally efficient and globally harmful. |
| Familiar names | Company, team, product, service, platform, and process names help orientation, while none alone identifies the operating System. |
| Several commitments | Customer, safety, provider, release, support, and financial commitments can coexist without one being the universal priority. |
| Countability | Boards and logs offer convenient units, while convenience does not establish identity or receiving use. |
| Continuing service | The operation must act with incomplete evidence, while uncertainty does not license invented state or authority. |
| Bounded entry | The first result must be affordable, while later decisions need enough identity and boundary precision to avoid rework. |
OPS.1:4 - Solution
Start with the result that must continue. Identify the operating System, relevant commitments, subjects and units at the boundary the current decision needs.
OPS.1:4.1 - Pattern-Use Unfolding
- Name the first user and decision. State who needs the focus, what decision it enables, the relevant horizon, and the first useful result or the condition that prevents it.
- Resolve the operating-System boundary. Use the already supported referent when it fits the decision. Where the boundary is unsettled, compare materially different plausible candidates: for example, the whole organization, a service operation, production cell, development operation, hospital function, supply relation, personal operation, product or asset, or coordination software. Use
A.1.SCRonly when System identity changes the decision; otherwise name the actual subject and leave through its pattern. - State the continuing result or service. Name its receiver, conditions, horizon, and the observation that would show interruption or degradation. Keep value, quality, acceptance, fulfilment, safety, and causal effect as separate claims.
- Recover demand and commitments. Distinguish requests and candidate Work from admitted Work. For each decision-bearing commitment, name parties, promised result or service, conditions, horizon, authority, current status and any gap in the evidence.
- Name operating subjects. Identify the customers, cases, physical items, release candidates, incidents, transactions, materials, services, accounts, or other subjects whose state or relation changes action.
- Define every tracked unit. Derive it from the result and the boundaries at which a contribution can become ready, be assigned or be used. Retain the difference between a customer matter, an operation on it, a processing batch and an accepted result where their events diverge. State the unit’s identity rule, start and finish when it is a Work item, subject/result relation, counted interval, and receiving use. If the unit itself needs a different work boundary or preparation arrangement, use OPS.11.1:4.2a; a count on a board alone does not supply that construction.
- Draw the operating boundary. Include only the Work, resources, relations, environments, and time horizon needed by the decision. Name the specialist questions left outside the boundary and when their results matter to the operation. Examples include product design, asset condition, finance, law, safety and capability.
- Check the control branch. If observation, decision, actuation, supervision, feedback, or rate separation can change coordination, record the control-relevant operating concern for
OPS.2. Do not construct a control view or infer a feedback relation here. - Recover authority and evidence limits. Name who may use the focus for which decision, what evidence supports it, any material uncertainty and any missing fact or authority that limits reliance.
- Return the focus and any needed continuation. State the supported operating focus or exact unresolved condition. Explain rejected candidates when a boundary comparison was needed. A sufficient answer can finish here; name a next contribution only when the receiving decision still needs it. For a focus maintained across uses, identify changes that would require revision. When a field changes, check the known views, accounts, policies and decisions that relied on it; explain which need rechecking or a return and which remain usable. Communicate that disposition in the account used by the affected participants.
Use an existing workflow or service account when it already identifies the needed result, receiver, promise and return. Add a missing distinction when it could change the decision or the grounds for a conclusion the recipient needs. A short statement can supply it.
OPS.1:4.2 - Carry the Result
Use the current account when it preserves the needed content below. Maintain a record when later reliance, coordination or a governing requirement needs it; a one-time answer can be stated directly.
| Result position | Content for the receiving use |
|---|---|
| use boundary | First user, decision, horizon, the result that suffices or the condition limiting the answer. |
| operating-System boundary | Supported System or subject-pattern return; decisive identity and boundary facts, with alternatives and their disposition when comparison was needed. |
| continuing result or service | Receiver, result or preserved condition, operating conditions, interruption observation, and any value, quality, safety or acceptance claim that remains open. |
| demand and commitments | Demand classes; commitment parties, contents, conditions, horizons, authority, status and any gaps in their evidence. |
| subjects and units | Identified subjects, unit identity rules, Work-item start/finish where relevant, subject/result relations, and receiving uses. |
| boundary and returns | Included Work, resources, relations, environments, horizon, exclusions, and specialist results needed. |
| control concern | The relevant observation, actuation, supervision, feedback, or rate question, when it changes coordination. |
| continuation | Missing contribution and next useful method, if any; revision conditions for a focus that will be maintained or reused. |
| downstream effect | When a focus field changes, which known consumers need rechecking or a return and which remain usable, with the reason needed by their users. |
OPS.1:4.3 - What Changes in Practice
The practitioner stops treating “the process”, backlog, service label, or reporting unit as self-evident. Every later view, queue, capacity measure, or intervention must refer to one operating System, a continuing result, explicit commitments, and units whose identity and use are known. A missing boundary or commitment becomes a useful blocker before a policy change accumulates cost.
OPS.1:5 - Archetypal Grounding — PumpWorks Continuing Control Service
PumpWorks must continue weekly evidenced controller releases while field incidents, provider changes, test-rig access, safety questions, and service commitments coexist.
| Candidate | Disposition for this decision |
|---|---|
| PumpWorks company | Too broad; corporate, financial, and legal questions remain specialist returns. |
| controller product | An engineered product and possible plant/controller participant, not the operation coordinating its continuing service. |
| field installation | A product-use and service subject whose state matters, not the whole release-and-incident operation. |
| board and issue tracker | Representations and records used by the operation; neither acts as the operating System. |
PumpWorks-ControlServiceOps | Selected operating System because its continuing Work coordinates evidenced releases, incident response, provider change, rig access, and service commitments. |
The continuing results are usable evidenced releases and truthful incident/service responses, not card movement or software deployment alone. Current demand includes ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, and test-rig requests. They are not one unit kind.
The weekly release commitment names the product/service receivers, required evidence, release horizon, release authority, and hold conditions. Incident response has different parties and horizons. Provider access and safety review have their own commitments and authority. Identify the terms of each commitment before deciding which work can proceed.
The operating subjects include the release candidate, field installation, incident case, safety question, provider change, rig booking, evidence results, and service relation. A release-candidate Work item may be counted for one workflow; the incident case and field pump remain separately identified. The selected boundary excludes product redesign, safety acceptance, corporate finance, and provider-contract decisions except as named returns.
Unlike rates make a control concern current: sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change can affect the release decision. Use OPS.2 to determine which of these timing and control relations matter for the release decision. A conclusion about stability or safety needs its own engineering grounds.
Reopen the focus if the operation’s continuing result changes, field-service Work makes another System the decision bearer, a commitment’s parties or authority change, or the current units cannot preserve subject identity across the next decision.
Suppose ProviderChange-P8 becomes a separately authorized provider-transition operation rather than Work inside PumpWorks-ControlServiceOps. Recheck the OPS.2 migration-project view and the OPS.4 provider-access and authority claims because they consumed that boundary. Keep the release-validation process view and the FieldIncident-I73 case account usable while their subjects, commitments, and relations remain unchanged. Return provider-contract authority to its specialist owner. The focus record carries these three dispositions instead of discarding every downstream result.
OPS.1:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| process-name bias | “The release process” becomes the operating System. | Start from the continuing result. Use a supported System boundary, or compare plausible candidates when their differences matter to this decision. |
| organization-boundary bias | A department or company name fixes the operation. | Recover the Work and relations that make the bounded operation relevant. |
| ticket-as-subject bias | The record becomes the customer, product, incident, or commitment. | Name the represented subject and the record relation separately. |
| commitment-by-date bias | A due date or service target is treated as an obtaining promise or authority. | Recover parties, content, conditions, horizon, status, and authority. |
| unit-of-value bias | Every counted item is called value or flow. | State identity and receiving use; use the source-local term only within its boundary. |
| controller-name bias | A controller product makes every operating question a control question. | Enter the control branch only when control relations or rates change coordination. |
OPS.1:7 - Conformance Checklist
- The opening names a first user, operating decision, horizon, and useful stop.
- The operating System has a supported boundary; materially different plausible candidates are resolved when they affect the choice, or the result returns to the appropriate subject pattern.
- The continuing result or service names its receiver and conditions without declaring value, quality, safety, acceptance, or fulfilment by wording.
- Demand, commitments, admitted Work, subjects, records, and units remain distinct.
- Every decision-bearing commitment names parties, content, conditions, horizon, authority, status, and evidence limits.
- Every counted or tracked unit has an identity rule and receiving use.
- The boundary names included Work and relations, consequential exclusions, any needed specialist results and any evidence or authority gaps.
- A control concern is recorded only when it can change the decision; no diagram or controller label establishes it.
- Any still-needed contribution is explicit; a maintained or reused focus states the changes that would require revision.
- A changed focus is checked against known uses of the changed field, and affected participants can recover the needed revision or continued use.
OPS.1:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Optimize the whole value stream.” | Name the operating System, receiver, result, subjects, and exact selected transformation-flow structure before optimizing. |
| “The backlog is demand.” | Distinguish external demand, candidate Work claims, admitted Work, deferred demand, and records. |
| “One ticket equals one customer outcome.” | Recover the customer or service subject, case, Work items, results, and record relations. |
| “All urgent items have commitments.” | Recover the actual promise or obligation and its authority; urgency and queue rank are separate. |
| “The board is our operating model.” | Treat the board as a representation; select the operation and decision before choosing views. |
| “The controller is the operation.” | Keep the engineered controller, controlled plant, service operation, control structure, and operating account distinct. |
OPS.1:9 - Consequences
Using this focus gives later work identified subjects, commitments, units and return conditions before an improvement is selected. It also exposes when the useful next result belongs to product engineering, organization change, maintenance, finance, safety, law, capability development, or another specialist practice.
The cost is early boundary and identity work. Some urgent requests stop because no one can support the operating System, commitment, unit, authority, or evidence claim.
OPS.1:10 - Rationale
Continuing operation is coordinated through actual Systems, Work, relations, commitments, and results. A board, process description, metric, or school can help only after its subject and use are fixed. Beginning from the continuing result and decision makes the boundary small enough to use while preserving the distinctions later queue, constraint, capacity, quality, service, and improvement decisions consume.
OPS.1:11 - SoTA-Echoing
The decision is where to place the operating boundary before changing coordination. A capable incumbent is an explicit Definition of Workflow with meaningful start and finish, receiving stakeholders, policies, service expectations and flow observations. The Kanban Guide 2025.5 supplies that bounded construction. TameFlow’s preparation and commitment discussions add the recipient’s useful package and the distinction between an option and committed work. OPS adopts those contributions rather than replacing them with a new preliminary form.
Compare the same PumpWorks decision. A well-maintained release workflow can already identify its validation work, completion criteria, WIP and promised delivery. If that is the decision’s whole reach, reuse it as the operating focus. If the question is whether the service can release R42 while continuing incident I73, however, finishing validation and restoring the field installation are different results. A single workflow may deliberately exclude the field receiver, the safety decision and provider-access commitments. Sections 4.1–4.2 add only the missing relation to those subjects and the participant who can answer it. The gain is a changed boundary and return: a completed lab package can be available while field restoration or release permission remains unresolved. If the release workflow already represents these relations, use it directly.
For another use, consider a competent travel-office workflow whose finished item is an issued ticket. The receiver now needs arrival before a site-access window. OPS.1 asks whether the current promise is ticket issuance or a usable travel arrangement, and who supplies the access and timing conditions. The result may remain a bounded travel service with a returned access question, rather than expanding its responsibility to the success of the whole visit. If the existing workflow already captures that receiving use and return, nothing must be added.
Establishing a missing relation between a subject and a commitment can take work with the receiver. Count that work and any later maintenance that continued use requires. Compare the cost with what the distinction can change about admission, continuation, a promise, an intervention or the grounds for a conclusion the recipient needs. Use the existing workflow directly when it already supplies those grounds.
FPF’s A.1.SCR, A.6.REL, C.2.1 and A.10 govern System recognition, relations, accounts and evidence. The historical DEMO distinction between production and coordination helps identify commitments and participants. Choose the operating boundary for the decision and establish local authority from the applicable arrangements. The PumpWorks and travel-office examples show when a missing relation changes the useful boundary. A comparison of effectiveness needs evidence from use of the alternatives. Reconsider your choice when it omits a relation that matters or when the existing workflow can supply the same answer at lower total cost.
OPS.1:12 - Relations
A.1.SCRgoverns conditional System recognition; OPS.1 consumes that result and adds the operating continuation, commitment, subject, and unit boundary.A.6.RELand direct subject patterns govern obtaining relations.C.2.1governs persisted claim-bearing accounts; a focus statement creates neither relation nor world state.OPS.2consumes the operating System, commitments, subjects, units, decision questions, and any control-relevant concern.OPS.3consumes subject candidates, commitments, evidence questions, and identity gaps.OPS.5later consumes the eligible demand and current commitments for admission;OPS.15,OPS.17, andOPS.19later consume the operating scope for account, repertoire, and simultaneous-Work decisions.- Product engineering, OCE, Maintenance, HCD, finance, governance, administration, safety, law, medicine, and other specialists retain their subjects, Methods, evidence, and authority.
OPS.1:End
OPS.2 - Select Work-Management Views and Coordination Methods
Status: Stable
OPS.2:0 - Use This When
Use this pattern when the same continuing Work is being called a project, process, case, workflow, queue, programme, or control loop and that choice changes coordination. Enter when one view hides a decision that another exposes: a process map may not show a permissible next action for an exceptional case, a project plan hides recurring service, a case file hides aggregate load, a queue hides commitments and subject state, or a loop diagram hides the operating account.
Choose the view and coordination method that answer the current question. For example:
For decision
Dabout subjectsSat grainG, use viewVand coordination MethodMunder conditionsC. If another view must be used with it, specify how their subjects correspond, which commitments and handoffs connect them, which rules apply and when to stop.
You may select one view or several compatible views, or keep the current arrangement when the existing coordination already answers the question.
A disagreement about how to coordinate the Work or a question the current view cannot answer gives a reason to use this method. Establish the structures, relations, performed Work, plans, control claims, authority, safety or evidence on which the selected decision relies through their applicable FPF or specialist methods.
Do not use OPS.2 to classify Work into a universal natural kind, infer performed Work from a plan, select a structure by diagram appearance, or prescribe one lifecycle. If the question concerns only the identity of an already selected structure, mathematical lens, or architecture view, use A.22, C.29, or C.30.LCA directly.
OPS.2:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| Work | Actual dated activity under its governing FPF pattern, including the enacted Method. Intended activity belongs to a plan or proposal. A management view describes or coordinates Work; it does not create another Work occurrence. |
| viewpoint question | The question a view must answer for a named user and decision, such as dates and allocation, repeatability, changing subject state, aggregate waiting, or feedback and rate separation. |
| Work-management mode | The selected use of one or more descriptions and coordination Methods for the current Work and questions. The same Work can be coordinated through different views and Methods. |
| project view | A description emphasizing a time-bounded undertaking, commitments, intended results, decisions, dates, WorkPlan content, allocation, dependencies, and closure conditions. |
| programme view | A description coordinating several projects or change commitments and their dependencies or intended contributions. Claims about a containing System, a benefit or decision authority need their own grounds. |
| process view | A description emphasizing a recurring Method, inputs, results, repeated order or constraints, and control points. It does not prove that every occurrence follows the description. |
| case view | A description organized around a changing subject, current facts, commitments, discretionary or constrained next Work, exceptions, and closure conditions. The case is not its file. |
| queueing view | A description of eligible items, membership, order or service relation, waiting, arrival, departure, resource demand, and policy for one receiving question. The queue is not a board column. |
| control-structure view | A current FPF description of one selected control structure and its actual observation, actuation, reference, supervision, feedback, and rate-relevant relations. Use it when the decision depends on identifying that structure and its relations. |
| coordination Method | A reusable way of coordinating the Work under stated conditions. A view can expose what the Method needs without being that Method. |
| mixed-mode decision | An explicit co-use account stating subject correspondence, scope and grain, commitments, handoff or coexistence conditions, decision rules, conflicts, and stops among unlike views and Methods. |
OPS.2:1 - Problem Frame
Project, process, and case management are often offered as competing descriptions of reality. Operations practice then chooses a tool or school and lets its default object model decide what exists. Yet one release operation can have a project for platform migration, a recurring process for validation, cases for field incidents, a queue for a scarce test rig, and a control view for observation and intervention at unlike rates.
These views are useful when they supply information needed by the receiving decision. Select each for the question it can answer. Where a decision uses more than one view, identify the subjects and relations that correspond across them.
OPS.2:2 - Problem
Using one view for questions it cannot answer loses information. A process-only account can force evolving cases through a route whose next Work depends on new facts. A case-only account can hide repeatable validation and shared capacity. A project-only account can treat continuing service as a temporary deliverable. A queue-only account can optimize waiting while breaking a commitment. A control-only account can turn observation and actuation into a complete management Method.
The opposite failure is an ungoverned hybrid: every tool and view is kept, but subjects, grains, states, and decisions disagree. Participants spend more effort reconciling records than coordinating Work.
OPS.2:3 - Forces
| Force | Tension |
|---|---|
| Familiar methods | Teams can act quickly with a known project or process Method, while familiarity can hide the wrong question. |
| Several truths | Unlike views can all be useful, while their subjects and state claims may conflict. |
| Runtime discretion | Some Work can be planned, while new facts require case-responsive continuation. |
| Aggregate coordination | Individual cases need attention, while shared queues and resources require a population view. |
| Control language | Feedback and rate distinctions can change coordination, while a loop diagram can overclaim stability, safety, or authority. |
| Affordability | A full multi-model account is expensive, while one view may omit the next decision. |
OPS.2:4 - Solution
Select views and coordination Methods from the operating questions they must answer. Preserve Work identity across views, select actual structures independently, and combine views when their distinct information can change the decision or what supports it.
OPS.2:4.1 - Pattern-Use Unfolding
- Recover the operating input. Start from the OPS.1 operating System, continuing result, commitments, subjects, units, horizon, and decision. Stop if the mode question is only a label preference.
- List the viewpoint questions. Name each user, decision, subject, grain, horizon and any information still needed. Separate planning, recurring execution, case continuation, aggregate waiting/capacity, and control questions.
- Identify relevant view candidates. Use a sufficient current selection directly. For an open choice, compare the incumbent with plausible alternatives, including a simpler view where it can answer the question. Candidate views include project or programme, process, case, queueing and control-structure views.
- Compare fit to the current Work. Examine the conditions that distinguish the serious candidates: for example, predictability, recurrence, subject identity, decision latency, runtime discretion, plannability, shared-resource coupling, exception frequency, evidence refresh or authority. Reuse an adequate existing selection when its grounds still hold.
- Select the coordination Method separately. Recover the actual rule or reusable way currently used: what fact permits a start or continuation, who applies it, what it orders, what evidence it needs and when it stops. Use
OPS.17:4.1–OPS.17:4.4when a real alternative or combination must be chosen. Compare the incumbent with that alternative at the same operating decision and include application and maintenance effort. Retain the incumbent when adequate. A notation, board, model or view alone is not this rule. - Qualify a selected structure when needed. Use
A.22when the decision needs a claim about a selected transformation-flow, queue/resource-dependency, commitment, event, case-state, control or other structure. Preserve its actual constituents and relations. A mathematical graph or diagram represents that subject under its own correspondence conditions. - Use the control branch conditionally. When coordination or the grounds for its decision depend on observation, decision, influence or their timing, use
C.43to recover the actual participants, information, choice, realization and return. That ordinary account can suffice. UseA.22andC.30.LCAwhen a selected control structure and view are needed; useB.2.5only for an obtaining two-sided supervisor relation andC.27.TA,C.27orA.3.3for the exact rate, temporal or dynamics claim. Stop without a control account when the decision and its grounds are independent of these relations. - When views must work together, relate them. State the shared subjects, relevant grain and horizon, state and evidence correspondence, governing commitments, receiving decisions, handoff and update rules. If Methods coexist, settle which rule governs a disputed permission, ordering, resource or stop decision; retain the other rule where its conditions still hold. Use the existing
OPS.17:4.4composition result where current. An unresolved conflict returns to its authority; a “hybrid” label does not settle it. - Examine a consequential change when its handling is unresolved. For a new or changed rule or an uncertain correspondence, change an input the rule uses and apply the resulting permitted action or stop. Identify unaffected subwork: a new fact may retire one exception without changing the recurring procedure, case identity or every view. Reuse a current qualifying replay or operating observation when it already answers this question; communicate what the next participant can still rely on.
- Return the selection. State the views and coordination Methods to use, the grounds for a material rejection, and any unresolved correspondence or needed input. A sufficient existing selection can finish the decision. Identify revision conditions when the selection will be maintained or reused.
OPS.2:4.2 - Carry the Result
Use the current coordination account when adequate. The following content is needed only for the questions and combinations selected above; retain it in a record when the receiving use or governing requirement needs one.
| Result position | Content for the receiving use |
|---|---|
| use boundary | Users, decisions, subjects, grains, horizons, and useful stop. |
| viewpoint questions | The planning, recurrence, case-state, aggregate waiting/capacity, control, or other questions that remain current. |
| candidate views | A sufficient existing selection, or the incumbent and plausible alternatives considered. Give the reasons for the choice, any material rejection and any evidence still missing. |
| coordination Methods | The coordination Methods in use or proposed, their conditions, costs, evidence, authority and stopping rules. |
| selected structures | Exact actual structures and direct relations relied on, plus representation and mathematical-lens boundaries. |
| mixed-mode correspondences | Subjects, grains, commitments, state correspondence, handoffs or conditions of coexistence, update and decision rules, any conflicts and stopping conditions. |
| control branch | Actual information, choice, influence and return needed by the operating question; a selected control view and qualified relation, rate or dynamics claims when that stronger use is needed, or the precise missing result. |
| continuation | Any still-needed subject or state-account input; revision conditions for a maintained or reused selection. |
OPS.2:4.3 - What Changes in Practice
Choose descriptions and coordination Methods for the decision, then relate those used together through their subjects and commitments. A view can be added, narrowed, or retired without retyping the Work or rebuilding every other view.
OPS.2:5 - Archetypal Grounding — PumpWorks Mixed Operating Views
OPS.2:5.1 - Identify the useful views
PumpWorks-ControlServiceOps coordinates several unlike questions:
| Current question | Useful view | Boundary |
|---|---|---|
How should FieldIncident-I73 continue after new field evidence? | Case view over the field installation, incident state, commitments, evidence, authority, and permissible next Work. | The ticket is a record; safety and product decisions retain their owners. |
| How is release evidence repeatedly produced and checked? | Process view of the recurring validation Method and its input/result relations. | A process description does not establish that an occurrence happened or conformed. |
| How is a time-bounded provider-platform migration coordinated? | Project and, when several projects are coordinated, programme views of commitments, WorkPlan content, decisions, allocations, and closure. | The plan is not performed Work, adoption, or benefit. |
| How is scarce rig access coordinated across eligible requests? | Queueing view over request membership, order/service relation, waiting, resource access, and policy. | Establish request membership, service order, and resource access for this queueing view; a board column alone does not establish them. |
| Which observations and interventions matter at unlike rates? | Conditional control-structure views for the product-side plant/controller/observer/supervisor relations and the operating-supervision relation. | FPF owns the generic structures and rate claims; the diagram is neither the account nor the Operations Method. |
The views preserve correspondences to ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, the test rig, commitments, evidence results, and decisions. The incident case can request a validation-process occurrence; that occurrence can consume rig capacity; its evidence can inform the weekly release decision; a platform-migration project can change provider access. None of these relations makes the views one structure.
The product-control structure has FieldPumpInstallation-P4 as plant, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 only where their direct relations obtain. The operating-supervision structure has ReleaseSupervisorTeam-S2 receive operating-state reports and return release, hold, rollback, or permitted-mode constraints to the operating System. The timing claims remain separate: sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change. Select the timing or control relations needed for this coordination decision. Establish feedback closure, stability, safety or authority separately when the decision relies on such a claim.
OPS.2:5.2 - Choose and combine actual coordination rules
In a constructed 09:00–11:00 window, PumpWorks permits at most two active engineering work packages under its existing staffing and recovery policy. T8 is already running. Incident diagnosis I73-D and the older provider-preparation package P8-P are both ready and permitted; both would need engineer E18. I73 has a field-contact window closing at 11:00, while P8-P can wait until the afternoon without violating a promise. The recurring T8 validation procedure is adequate and remains unchanged.
The incumbent rule starts the oldest ready package when a slot and performer are free. Its virtue is predictable order with little coordination. The incident rule allows a ready package to precede that order when a named response window would otherwise be lost, provided the incident lead authorizes the exception, the resource owner confirms it, displaced work remains feasible and the active limit is respected. These are supplied local rules, not universal properties of either a case view or Kanban.
Using OPS.17:4.2–OPS.17:4.4, the coordinator compares the two rules at this decision. Starting the noninterruptible two-hour P8-P would remove E18 from the incident’s remaining evidence-and-response interval. The exception instead starts I73-D, defers P8-P to an authorized afternoon review and leaves T8 running. Preserving the field-contact window costs one confirmation and a follow-up on the deferred package. Under the combined rules, readiness and permission govern eligibility, the incident exception governs order among eligible packages, the two-package limit still governs starts, and validation controls its own safe completion. No extra active slot is created.
At 09:50 the field contact becomes unavailable. The exception no longer justifies reserving E18 for live verification. The incident remains a case with a partial diagnostic result, but the live continuation returns for access and permission. T8’s completed evidence and the independently permitted T9 validation remain usable; the coordinator reconsiders ready demand without reopening every view. OPS.5:5.1, OPS.6:5.1 and OPS.7:5.1 develop the admission, observation and commitment decisions for this same constructed matter. They can also be used independently.
Keep the existing validation process where its rule fits. Add the case, queue or commitment relation when it changes the decision or the grounds for relying on it.
Reopen the mode decision when a new subject cannot be related across views, a plan repeatedly fails after new facts, queue policy changes a commitment, a control relation becomes decisive, or maintaining one view costs more than the decision value it supplies.
OPS.2:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| one-true-kind bias | Work is declared inherently project, process, or case. | Recover the question, subject, and selected view; preserve Work identity. |
| tool ontology bias | The tracker schema decides which objects and states exist. | Identify subjects and relations first; treat the schema as representation. |
| hybrid-label bias | “Hybrid” hides missing correspondences and decision rules. | State subject/grain mappings, commitments, coexistence, conflicts, and stops. |
| process-normality bias | Exceptions are forced back into the designed route. | Use a case view when new facts change permissible next Work. |
| project-temporariness bias | Continuing operation is treated as a project deliverable. | Keep the time-bounded change view separate from ongoing service Work. |
| loop-as-method bias | A feedback diagram becomes the whole Operations Method. | Use the conditional FPF control branch and retain the operating decision separately. |
OPS.2:7 - Conformance Checklist
- The decision begins with an OPS.1 operating focus and exact viewpoint questions.
- Work identity is preserved across every selected view.
- Project, programme, process, case, queueing, and control are selected for questions rather than declared natural Work kinds.
- Coordination Methods, views, actual structures, diagrams, and tools remain distinct.
- Selection uses the conditions that distinguish the serious candidates and reuses an adequate current answer.
- Every mixed-mode use states subject and grain correspondence, commitments, coexistence or handoff, update and decision rules, any conflicts and stopping conditions.
- The control branch names actual participants and direct relations only where they obtain and returns rate/dynamics claims to their FPF owners.
- A changed case or cross-view probe can expose a failed selection or correspondence.
- Any material rejection, unresolved gap or needed continuation is explained. A selection maintained or reused includes the conditions for revision.
OPS.2:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Everything is a process.” | Identify changing subjects and ask whether discretionary or constrained case continuation is needed. |
| “Every initiative is a project.” | Separate time-bounded change commitments from recurring and continuing operation. |
| “Case management means no process.” | Retain reusable Methods and recurring subwork while letting subject state govern permissible next Work. |
| “Put all work in one queue.” | Name eligibility, service/resource relation, commitment effects, and the subjects that must remain separate. |
| “Use one integrated model.” | Preserve non-isomorphic views and relate only the claims the decision consumes. |
| “The loop proves control.” | Recover actual relations and use direct rate, dynamics, evidence, safety, and assurance patterns. |
OPS.2:9 - Consequences
The operation can combine familiar practices while preserving the subjects and results each one addresses. Missing correspondences, duplicated state, disagreements between records, stale mappings and the cost of maintaining them can then affect which views to retain.
The cost is maintaining subject and state correspondence where several views are genuinely useful. Some integrations are rejected because the views answer no different question or cannot preserve identity and commitments reliably.
OPS.2:10 - Rationale
A view earns its place when it supplies information needed for a decision or for a warranted conclusion about it. Project, process, case, queueing, and control descriptions foreground unlike structures, times, and questions. Treating them as views preserves their strengths and avoids a false taxonomy of Work. Explicit mixed-mode rules then make coexistence testable without requiring one universal model.
OPS.2:11 - SoTA-Echoing
The question is how to coordinate evolving case work with recurring procedures and shared resources. A strong alternative already integrates them. CMMN 1.1, §4.1 and §5.4.9 supports runtime case planning, procedural subwork and authorized planning roles. An adaptive project arrangement can likewise revise its plan when facts change. Both can already support coordination that changes with the case.
At PumpWorks, such an arrangement can retain T8’s procedure while a case manager selects incident diagnosis. If its case file, resource policy and decision rights also settle the shared E18 allocation and preserve the field-contact window, use it unchanged. OPS adds no gain by displaying the same decision in more tools. The remaining question arises when the case manager’s chosen action, the queue’s oldest-ready rule and the resource owner’s active limit produce incompatible starts. Sections 4.1.5 and 4.1.8 connect to OPS.17 to recover and compose the actual rules; section 5.2 makes the incident exception govern order without overriding eligibility or increasing the limit. The changed contact condition retires that exception while recurring validation survives.
This synthesis costs rule recovery, agreement on the one disputed decision, mapping of the shared subject and evidence, and maintenance of that correspondence. It can be more expensive than using a capable integrated case model, especially when one owner already maintains all relevant policies. Its conditional gain is avoiding an unsupported cross-view action when those policies were separately governed. Stop adding views when they cannot change the decision or its grounds. Retire a duplicate view when its continued use no longer warrants the cost of keeping it in agreement.
CMMN shows how planned and discretionary work can coexist. The DCR tradition supplies explicit conditions and responses. For the operating case, use applicable domain evidence and establish any required external authority from the arrangements or decisions that grant it. The Kanban Guide supplies the bounded flow-policy contribution. FPF C.43 supplies the ordinary control account; A.22, C.29, C.30.LCA and the applicable temporal patterns govern selected structures, mathematical representations and stronger control claims. Reopen when the integrated incumbent already settles the same conflicts more simply, or a new case defeats a relied-on composition rule.
OPS.2:12 - Relations
OPS.1supplies the operating System, continuing result, commitments, subjects, units, horizon, and any control concern relevant to the decision.C.43supplies the ordinary control account.A.22governs selected structures;C.29governs mathematical-lens use;C.30.LCA,B.2.5,C.27.TA,C.27andA.3.3govern the corresponding view, supervisor, rate, temporal and dynamics claims when needed.OPS.3receives selected subjects, grains, view correspondences, direct-relation questions, and representation gaps.OPS.4receives the selected participant views and their state-correspondence obligations.OPS.5later consumes the selected coordination form for admission.OPS.6later consumes case-state and continuation needs.OPS.8–OPS.11can use the selected views to answer queue, constraint, capacity and interacting-structure questions.- Project Management, case management, BPM, Kanban, SRE, and other practices offer candidate coordination Methods. Select a particular Method using its applicability conditions and evidence.
OPS.2:End
Part II — Recover Operating Subjects and Maintain Current State
OPS.3 - Distinguish Operating Subjects, Cases, Queues, Resources, and Records
Status: Stable
OPS.3:0 - Use This When
Use this pattern when one card, ticket, order, object identifier, case file, event row, or status label is being asked to stand for several different things. Enter when the subject of a measure or the item waiting in a queue is unclear, an incident record is treated as the incident, a resource is treated as its availability, or two views cannot agree because they identify their subjects differently.
The first useful move is to resolve one decision-bearing subject and the claim needed about it. An existing account or a short explanation can carry this result:
Subject
Shas identity conditionI. The decision-bearing claimQaboutSand its relationsRis qualified for time or horizonTand supported byE. State a formal kind, represented view, governing rule or missing condition when the receiving use depends on it.
Repeat for distinctions that can change the decision or the grounds for a conclusion the user needs. Stop with an account of the relevant subjects and their relations.
Use the method when a record label, metric denominator, queue item, or “work object” has several plausible referents. Assurance is claim-specific: entity kinds, Work, relations, commitments, state, evidence, event occurrence, control participation, resource availability, and representation each retain their FPF or specialist tests.
Use an existing subject pattern or an adequate subject account when it answers the identity or relation question. Add the Operations correspondence needed for this decision. For example, a ticket number may identify the record while the field installation and the incident have separate identities.
OPS.3:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| operating subject | The entity or relation the operating question concerns. It may be, for example, a case subject, material, a service or an account whose identity or state matters to the decision. |
| case | One bounded continuing Work situation organized around a named subject, commitments, current facts, evidence, authority, permissible next Work, and closure conditions. The case is neither its file nor every Work item within it. |
| Work occurrence | Actual dated Work admitted through its governing pattern. A ticket, plan, or event record does not establish that Work occurred. |
| Work item | A bounded item admitted to a selected workflow or coordination account with stated start, finish, subject/result relation, and receiving use. |
| queue membership | An obtaining relation placing one eligible item in one named waiting or service order under a policy and time window. A column or list is a representation. |
| buffer membership | An obtaining relation to a bounded protective or coordination reserve with purpose, policy, extent, and receiving use. It is not inferred from spare inventory or a board column. |
| resource relation | A relation that matters to the provision or use of a resource. For planned work, identify what is available, accessible or allocated under the stated conditions. For a claim about performed Work, identify the support it received or the resource it consumed. |
| event | An occurrence or change under its subject rule and time boundary. An event record or timestamp is evidence about it, not the event by identity. |
| record or trace | A claim-bearing episteme about subjects, Work, events, relations, or decisions, recorded on an identified carrier. Its claims have stated sources and scope limits. |
| state claim | A qualified claim about one subject at a stated time or horizon with provenance, uncertainty and conditions; include authority where the claimed state or receiving action depends on it. A status label is one possible representation. |
| control participant meaning | Observer, controller, plant or supervisor as the participant meaning in an actual control relation. Qualify a selected control structure when that claim is needed. The label does not establish that the relation obtains. |
| operating-subject account | The smallest relation-specific set of identities, direct relations, records, state claims, and any limits the decision maker needs to know. |
OPS.3:1 - Problem Frame
Operational tools summarize subjects, events and states so participants can coordinate their work. That compression is useful until one row is read as the customer, order, case, Work, queue position, resource claim, event history, and current state at once. Object-centric and case-responsive approaches repair parts of this problem, but their own records and identifiers still need receiving-use limits.
The practitioner needs a small account that restores identity and obtaining relations before measures and policies are applied. The account can use several records and views while keeping the world-side subjects and claim-bearing epistemes distinct.
OPS.3:2 - Problem
When identities collapse, flow measures acquire false denominators, cases close while the conditions they were meant to resolve persist, queue policies compare unlike items, resources are double-counted, and events are reconstructed into Work that may never have occurred. A record update can then masquerade as an operational change.
An unnecessarily broad modeling effort can delay the current decision while still omitting the few direct relations it needs. Tool categories require the same check against the subjects and relations they claim to represent.
OPS.3:3 - Forces
| Force | Tension |
|---|---|
| Coordination shorthand | One ticket or identifier is affordable, while it can hide several subjects and relations. |
| Measurement | Stable units enable comparison, while identity changes and joins can silently change the measured population. |
| Several records | Logs, trackers, files, and physical observations can complement one another, while their claims may conflict. |
| Runtime change | Cases and subjects evolve, while records arrive late or use stale identity rules. |
| Resource scarcity | Capacity decisions need resource relations, while people and machines must not be reduced to scalar capacity. |
| Minimality | The operation needs decisive distinctions now, while a complete domain model is expensive and brittle. |
OPS.3:4 - Solution
Use or develop a small operating-subject account that preserves the identities, relations, times and evidence the decision needs. Identify how each relevant record or view represents its subject. Start from the subjects and views already selected through OPS.1 or OPS.2.
OPS.3:4.1 - Pattern-Use Unfolding
- Name the receiving decision and suspected compression. Identify the subjects or relations that may have been treated as the same, the measure, queue, case continuation, commitment, control question, or account use that depends on that identity assumption, and what fails if the assumption is false.
- Select the primary subject. Identify the entity or relation the action or conclusion depends on, and how to recognize it across time. Use its subject pattern when the answer depends on its kind.
- Separate case, Work, and Work item. Name the case subject and closure conditions; admit actual Work independently; define each coordination Work item by start, finish, subject/result relation, and receiving use.
- Recover queue and buffer relations. Name eligible item, queue or buffer, membership interval, order or protective purpose, policy, resource/service relation, and evidence. If the decision uses a position shown in a view, establish which of those relations it represents.
- Recover resources through exact relations. Distinguish the System, capability, material, information, access condition, or time from availability, access, allocation, support, consumption, or other obtaining relation. Preserve authority and human-condition questions.
- Separate events, records, and state claims. Identify the occurrence or changed subject and the records supporting it. For a consequential time, distinguish occurrence, observation, receipt and later correction; recover the clock and field meaning actually used. A later upload does not move the occurrence or reset its waiting time. State the supported claim and its uncertainty. Event order alone does not establish performed Work.
- Recover commitments and direct relations. Use
A.6.RELor the direct governor for each relied-on relation. Keep promise, obligation, fulfilment, responsibility, authority, assignment, and evidence distinct. - Apply the control branch only when selected. Preserve actual Systems or holons and direct observation, actuation, reference, supervision, and feedback relations. Treat observer, controller, plant, and supervisor as relation-specific meanings. Use
B.2.5only when both observation/report and returned influence/constraint sides obtain. - Reconcile records by subject and claim, not by row. When a relation or timestamp is disputed, identify the source that can settle that particular meaning and who or what is authorized to correct the account. Preserve the original observation and explain the correction. Recompute only the state, elapsed time, queue membership or other decision that used the defective relation. Keep an unresolved association unusable for that inference; do not guess a replacement. Retain independently supported claims and ongoing work. A correction to a record does not itself change permission or undo performed Work.
- Stop at the smallest sufficient account. Return the subjects, relations, state claims and support needed by the decision, with any unresolved condition. Use OPS.4 when participants need to maintain or share the current account; otherwise the resolved identity or relation can finish this use. Identify revision conditions when the result will be reused. Leave unrelated objects outside.
OPS.3:4.2 - Carry the Result
Preserve the content needed by the selected question. Use the existing record or explain the result directly; create or maintain a record only when coordination, later reliance or another governing requirement needs it.
| Result position | Content when relevant to the receiving use |
|---|---|
| use boundary | User, decision, horizon, suspected compression, and useful stop. |
| subjects and identity | Identified primary and related subjects, relevant kinds or predicates, identity conditions and any unresolved referents. |
| cases and Work | Case subject and closure; actual Work basis; Work-item start/finish, subject/result relation, and receiving use. |
| queue, buffer, and resource relations | Participants, membership or access interval, purpose/policy, order or extent, direct relation, and evidence. |
| events and records | Occurrences, claim-bearing records and carriers, source, scope, time, uncertainty, and any inference limits that matter to the decision. |
| state and commitments | Qualified state claims, commitment relations, provenance, any applicable authority, conflicts that matter, and the conditions under which the claims remain current. |
| control relations, when the control branch is selected | The actual participants and decision-bearing observation, actuation, reference or supervision relations. Omit this row for an account that makes no control claim. |
| continuation | Any unresolved condition or needed account maintenance; revision conditions for a result that will be reused. |
OPS.3:4.3 - What Changes in Practice
Measures, queues, and dashboards acquire named subjects and relation semantics. A card move updates the record. Separately establish any change in the subject or relation that the updated record represents. Teams can keep several tools while knowing which claim each can support and where a missing identity or relation blocks action.
OPS.3:5 - Archetypal Grounding — PumpWorks Subject Account
The weekly release decision initially sees four cards and a rig calendar. To decide what can be relied on, distinguish the cards and calendar from the following subjects and relations:
| Visible item | Recovered subject or relation | Record boundary |
|---|---|---|
ReleaseCandidate-R42 card | A release-candidate subject and its candidate contents, required evidence results, release Work items, and receiving release decision. | The card and commit identifiers are records; moving the card does not change deployed field state or satisfy the release commitment. |
FieldIncident-I73 ticket | A case organized around FieldPumpInstallation-P4, reported symptoms, service commitments, evidence, authority, permissible next Work, and closure conditions. | Ticket closure does not establish restored field condition or fulfilled service. |
SafetyQuestion-S19 issue | A question episteme, related evidence needs, specialist safety decision, and any Work items created to obtain that result. | A red label is neither a safety state nor authority to accept risk. |
ProviderChange-P8 epic | A time-bounded change subject with provider relations, access conditions, project WorkPlan content, affected release cases, and decisions. | The epic does not make the provider part of PumpWorks or prove performed migration Work. |
| test-rig booking row | Queue membership of an exact eligible request for resource relation to TestRig-2, with interval, order/policy, access condition, and status evidence. | The booking row records planned access. Establish request eligibility, allocation authority, performed test Work, and test completion separately. |
Distinguish the records for this decision: ticket, trace, source commit, build result, test result, service log, field-engineer report, telemetry record, and release decision each support bounded claims. A multi-object event record may relate one event to several subjects, but it does not identify those subjects with one case or prove the represented Work.
Consider a later, constructed PumpWorks reconciliation. An imported test event L17 has been associated with both R41 and R42 because their records share a release folder. The board consequently removes R42’s test request from the ready queue and reports “tested at 10:20.” That conclusion assumes that L17 tested R42, and that 10:20 is test completion rather than receipt of the message.
The lab’s signed execution record identifies the tested build as R41 and completion at 09:50; the intake trace identifies 10:20 as message receipt. The lab engineer confirms those meanings, and the authorized record maintainer replaces the false R42 association with the supported R41 association while retaining the original import and the correction’s basis. R42’s completion claim is withdrawn. After confirming that R42’s independently established inputs and permission still hold, the scheduler restores its waiting eligibility and the priority justified by the current queue rule and original waiting history. Correction time does not restart its age or revoke work already permitted or performed on other requests. L17 supports the stated R41 test result, not R41’s wider release or field condition.
S19’s unresolved safety question, I73’s field observations and the independently permitted work on them remain as they were. The correction reaches OPS.4’s R42 state and OPS.8’s test population because those uses consumed the bad link; it does not invalidate the entire operating account. If the execution record cannot identify the tested build, neither R41 nor R42 acquires test completion from L17. Ask the lab which build the record covers, or identify that missing fact in the result. Other work can proceed where its independent conditions and permissions hold. This small reconciliation is sufficient when those are the only affected uses; a full data-model migration would add cost without changing the decision.
For the product-side control view, FieldPumpInstallation-P4, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 retain their relation-specific meanings. For operating supervision, ReleaseSupervisorTeam-S2 is an admitted acting System only where supported and the two-sided report/constraint relation to PumpWorks-ControlServiceOps is recorded only if both sides obtain. The diagram, participants, relations, state claims, and operating account remain distinct.
When participants need a shared or maintained account, use these subjects, records, current claims and any relevant conflicts, permissions or update conditions in OPS.4. Reopen only the affected identity or relation when a release candidate is superseded, an incident splits or merges under an explicit rule, a queue membership changes, a record source becomes stale, or a claimed control relation loses one side.
OPS.3:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| card-identity bias | Card, case, Work item, and subject become one thing. | State separate identities and direct relations. |
| case-file bias | The file becomes the continuing case. | Name the subject, commitments, current facts, permissible Work, and closure conditions. |
| queue-container bias | A column or list is treated as an obtaining queue. | Recover membership, order/service relation, policy, interval, and evidence. |
| resource-scalar bias | A person, machine, or capability is reduced to available hours. | Preserve the subject and access, support, allocation or use relation on which the decision relies. |
| event-log realism | A log is treated as complete performed Work. | Preserve source limits and admit Work independently. |
| object-centric collapse | Multi-object linkage is read as one universal case or process. | Keep subjects, event relations, records, views, and receiving uses distinct. |
| control-role reification | Observer, controller, plant, or supervisor labels become permanent kinds. | Recover participant meanings in exact obtaining relations. |
OPS.3:7 - Conformance Checklist
- The account begins from one receiving decision and a named suspected compression.
- Each decision-bearing subject has an identity condition and direct subject governor when needed.
- Case, actual Work, Work item, queue membership, buffer membership, resource, event, record, and state claim remain distinct.
- Work items state start, finish, subject/result relation, and receiving use.
- Queue, buffer, and resource claims name exact participants, purpose or policy, interval, and obtaining relation.
- A relied-on record preserves its source, subject, claim scope, time and uncertainty, and any inference limit material to the receiving use.
- Direct relations use current governors; a representation or co-occurrence creates none.
- Control participants and two-sided feedback are recorded only where actual relations obtain.
- The result is the smallest account sufficient for the decision, with any unresolved condition and the revision conditions needed for reuse.
OPS.3:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “One issue equals one unit of value.” | Name the represented subject, Work item, result relation, identity rule, and receiving decision. |
| “The customer is in the queue.” | State whether the queued participant is a request, case, Work item, physical subject, or another identified entity. |
| “The resource is 80% utilized.” | Identify the resource subject, availability/allocation/use relation, time window, Work, and decision. |
| “The event log shows the process.” | State the logged events, object relations, source coverage, reconstruction rule, and missing Work evidence. |
| “Status Done means fulfilled.” | Recover the commitment, supplied result, acceptance or fulfilment evidence, and authority separately. |
| “The dashboard closes the feedback loop.” | Recover both in-life relation sides and keep the display, claims, rates, and proof separate. |
OPS.3:9 - Consequences
Identifying the units and their evidence gives practitioners a basis for measurement, policy and reconciliation across views. It also localizes repairs: a stale record source, changed identity rule, missing relation, or uncertain state claim can reopen without rebuilding the whole operating account.
The cost is refusing convenient conflations. Some metrics and historical analyses become unusable because their unit identity or source coverage cannot be recovered. That loss is explicit rather than hidden in a precise-looking chart.
OPS.3:10 - Rationale
Identify the subjects and relations on which the operating decision or required conclusion depends. Use the available observations, confirmations and records to establish them. A small account can suffice when it shows which conclusion is supported, how any cited record represents its subject, and what limit still matters.
OPS.3:11 - SoTA-Echoing
The question is which subjects, relations and times must be recovered before the responsible practitioner can rely on the records for an operating decision. A capable object-centric account already relates events to several objects, retains histories and distinguishes relation meanings. OPS adapts that contribution.
OCEL supplies an exchange model for that account. The 2026 object-centric process management manifesto, particularly §2.3 and §3, distinguishes execution data from their representations and identifies changing relations as a limitation of OCEL 2.0. The 2026 object-centric data-quality study, “Relationship-based quality issues” and its practitioner cases, shows why a well-formed multi-object log can still have wrong or insufficiently qualified links and changing timestamp meanings. These findings motivate checking object links and timestamp meanings in steps 6 and 9 of OPS.3:4.1 and in OPS.3:5. Whether the correction improves a particular operating decision requires evidence from its use there.
In the L17 choice, a competent data-quality procedure that already checks the build, timestamp meaning, correction provenance and affected consumers is sufficient. Use it unchanged. Where it repairs the log but leaves the operating consequence undecided, OPS adds the narrow return: withdraw the unsupported R42 completion, recompute only dependent membership and age, and retain the independently supported work. The extra cost is consulting the responsible source and following the faulty relation into the decisions that relied on it. Recreating every object or copying all histories into a second account is unnecessary. An unresolved relation can block one inference without blocking the rest of the operation.
Current FPF A.6.REL governs the direct relations relied on; distinguish relation occurrences only when the receiving use must tell repeated occurrences apart. C.2.1 governs claim-bearing accounts and B.2.5 the selected two-sided supervision relation. Subject-specific identity and specialist evidence remain with their direct governors. CMMN 1.1, DCR and DEMO’s bounded commitment/coordination account retain their case-planning and relation contributions; none makes record closure proof of physical completion. Integrated network descriptions can retain unlike coupled relations without identifying their subjects.
Reopen this choice when the record’s meaning, relation history, clock, consumer or correction authority changes, or when the incumbent supplies the same bounded correction and operating return at lower effort. For a larger data migration, use the appropriate data-engineering method.
OPS.3:12 - Relations
OPS.1supplies operating scope, subject candidates, commitments, units, and evidence questions.OPS.2supplies selected views, grains, correspondences, and conditional control questions.A.6.RELand direct subject patterns govern obtaining relations and identities;C.2.1governs claim-bearing accounts;B.2.5andC.30.LCAgovern the conditional control relation/view boundary.- For ongoing coordination through
OPS.4, use the identified subjects, relations, records, state claims and provenance, together with any conflicts, permission conditions or material gaps. OPS.8,OPS.9,OPS.10,OPS.11,OPS.12, andOPS.18later consume the exact subjects and relations whose queue, constraint, capacity, interaction, human-condition, or quality claim is current.- Data engineering, process mining, product engineering, safety, finance, law, medicine, and other specialists retain their schemas, inference Methods, evidence, and authority.
OPS.3:End
OPS.4 - Keep Current Operating State Recoverable Across Participants
Status: Stable
OPS.4:0 - Use This When
Use this pattern when participants must coordinate continuing Work but act from stale, partial, conflicting, differently authorized, or differently grained accounts of the same operating subjects. Typical cues are “we need one source of truth”, a control room with no claim provenance, a board that hides field state, a case handoff that loses the next decision, or a dashboard whose users cannot tell what they may change.
The first useful move is to use or repair the account needed by one participant decision:
For subjects
Sand commitmentsC, current claimsQat horizonsThave supportE, with the provenance and uncertainty needed by this decision. Preserve any consequential disagreement, missing condition, access or decision authority, next action and condition for updating the account.
Participants can coordinate from different screens and can retain a material disagreement. Each needs the subjects, claims, evidence, permissions and next decisions relevant to its Work.
Recognition is cheap: enter when a participant cannot resume, decide, or explain a material disagreement from the maintained account. Assurance is claim-specific: world state, evidence, authority, permission, Work, safety, stability, causal effect, and release or acceptance decisions keep their own governing patterns.
Do not use OPS.4 to build a generic dashboard, mandate transparency, create one shared mental model, replace specialist records, or declare state true because it is visible. If the current problem is a Work-performance configuration or recovery dependency after interruption or support loss, use A.15.8 for that general question and keep the operation-specific state and commitments here.
OPS.4:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| current operating account | A participant-usable set of qualified claims tied to exact operating subjects, commitments, evidence, permissions, decisions, and refresh conditions. It is neither the operating System nor a universal database. |
| subject-state claim | A claim about one subject or relation at a stated time or horizon, with the scheme, conditions, provenance and uncertainty needed to use it; authority is a separate condition where the claim or action depends on it. |
| currentness | The condition under which a claim remains usable for a named decision and horizon. Recent timestamps alone do not establish it. |
| provenance | The source, observation, transformation, record, and responsibility facts needed to judge the claim’s receiving use. Provenance does not make the claim true by itself. |
| uncertainty | Missing, estimated, conflicting, stale, or bounded information that could change a decision, a claim the participants need to support or the conditions for relying on it. |
| disagreement | Two or more recoverable claims, interpretations, or decisions that cannot yet be used as one result. Visibility of disagreement is compatible with aligned attention. |
| permission and change authority | Separately supported relations governing who may read, write, approve, hold, release, or otherwise use account content. Visibility, responsibility, assignment, and capability imply none of one another. |
| next decision or permissible Work | The decision or Work option currently enabled, blocked, or awaiting a named condition. The account does not perform or authorize it by display. |
| participant view | A use-bounded representation of selected account claims for one participant action. Several views may coexist when subject and claim correspondence remain recoverable. |
| control representation | A view, loop diagram, dashboard, or control-room display representing selected control structures, relations, rates, or account claims. It establishes none of those facts by appearance. |
| attention-maintenance result | A usable current account and the views its participants need, with material gaps, update conditions and next decisions identified where applicable. |
OPS.4:1 - Problem Frame
Continuing operation needs a present account because the operation outlives one meeting, screen, shift, or model session. Claims arrive at different rates from field observations, cases, tests, providers, plans, queues, and specialist decisions. Different participants need different slices and hold different authority.
Participants can coordinate when they can relate claims, evidence and permissions to the same subjects and recover what each decision requires. Preserve a material disagreement and its grounds wherever the participants’ accounts differ.
OPS.4:2 - Problem
Visibility without claim discipline amplifies error. A fresh dashboard can repeat stale field state, a green board can hide an unresolved service commitment, and an integrated twin can merge observations with predictions and planned states. Participants appear aligned until a decision exposes different referents, time horizons, or authority.
The opposite failure stores every record and overwhelms users. Important gaps, conflicts, and expiry conditions disappear in detail, so participants may have to reconstruct the state from memory or information unavailable to the next shift.
OPS.4:3 - Forces
| Force | Tension |
|---|---|
| Speed | Participants need a quick current view, while rushed aggregation can erase provenance and uncertainty. |
| Several horizons | Field control, incident response, release, provider change, and finance update at unlike rates. |
| Several participants | Participants need different views and permissions, while divergence can hide conflicting claims. |
| Continuing Work | Handoffs and interruptions require recoverability, while an account cannot guarantee capability or performance. |
| Disagreement | Teams want one answer, while preserving a qualified conflict can be safer than premature consensus. |
| Representation | Dashboards and control rooms improve attention, while appearance can be mistaken for state, authority, or proof. |
OPS.4:4 - Solution
Maintain the smallest decision-specific account that lets named participants recover exact subjects, current qualified claims, commitments, evidence, uncertainty, permissions, disagreements, next decisions, and refresh conditions. Present several views when needed, but keep claim and subject correspondence explicit.
OPS.4:4.1 - Pattern-Use Unfolding
- Name participants and decisions. State who must resume, coordinate, hold, release, escalate, or perform next Work; name the horizon and useful stop for each action.
- Import exact subjects and relations. Use the OPS.3 operating-subject account. Do not let a dashboard row, case file, queue position, or control diagram replace the subject or obtaining relation.
- Select claims that matter to the receiving work. For each subject or commitment, state the claim, its effective scheme, conditions, time or horizon, and what decision or conclusion depends on it.
- Attach evidence and provenance. Preserve the source and support needed for the claim and receiving use, including the observation or result, carrier, transformation, version, reach and uncertainty where they affect reliance. Reuse that basis from the current account. Keep prediction, plan, observation and decision claims distinct.
- Show material disagreements and gaps. Where claims conflict, preserve their grounds and the decision they affect. Identify any missing observation or specialist result, stale evidence or uncertainty about authority that limits the decision.
- Recover applicable permissions and authority. For a restricted access, account change or operating decision, establish who may act, on what and under which conditions. Preserve the existing basis when current. Keep assignment, capability, responsibility, permission and authority separate. A factual observation can support a state claim without itself granting permission to alter that state or a commitment.
- State next decisions and permissible Work. Name what is enabled, blocked, awaiting evidence, or returned to a specialist; include the condition and participant that can advance it.
- Use a suitable view for each participant. Use a sufficient current representation or develop the one the action needs. Preserve subject identity and claim correspondence; show what the view omits and where claims conflict, and provide a return to the owning account. Do not require one screen.
- Qualify a selected control view. Relate its depicted observation and intervention to the actual participants, evidence and authority. Obtain stronger control claims, such as stability or rate adequacy, from their direct analysis; the picture cannot supply them.
- Test interruption and handoff when current. Use
A.15.8for the general Work or WorkPlan performance-configuration question. Ask a representative next participant to recover the bounded question, current claims, evidence, disagreements, permissions, next Work, and stop without private memory. - Keep the account current for its use. Identify the source or event that changes a relied-on claim and how affected participants will receive the update. Specify cadence, expiry, supersession or conflict handling where the claim or its use requires them. Reopen only the affected claim, view or decision.
OPS.4:4.2 - Maintain the Usable Account
Reuse existing specialist records and participant views. Keep the content below to the extent needed for the selected decisions, access conditions and continuing use.
| Result position | Content for the receiving use |
|---|---|
| use boundary | Participants, actions or decisions, horizons, first useful result, and truthful stops. |
| subjects and commitments | Exact OPS.3 subjects and direct relations; commitment parties, content, conditions, status, and authority. |
| current claims | Claim content, effective scheme, time/horizon, conditions, uncertainty, and receiving action. |
| evidence and provenance | Sources, observations/results, carriers, transformations, versions, reach and any missing evidence. |
| permissions and authority | Applicable access, account-change and operating-decision relations, with their scope and basis. |
| disagreement and gaps | Any conflicting or missing claims, the decisions they limit, and the specialist results or separate interpretations needed. |
| next decisions and Work | Enabled, blocked, awaiting, or returned actions; required condition and responsible participant. |
| participant views | Selected claims, subject correspondence, explicit scope of omitted material, conflict cues, return route, and access limits. |
| refresh and recovery | Update or expiry conditions, handoff/recovery observation when current, and smallest reopen rule. |
OPS.4:4.3 - What Changes in Practice
Each participant can recover the subjects, claims, evidence, permissions and next action needed for its decision. If participants disagree or a fact is missing, the account shows which action or conclusion that limits. A change to a record can then be distinguished from a change to the state it describes.
OPS.4:5 - Archetypal Grounding — PumpWorks Current Operating Account
The weekly release decision uses a small account rather than one status board:
| Account claim | Evidence, uncertainty, and authority | Next decision or Work |
|---|---|---|
FieldIncident-I73 may affect controller behavior at FieldPumpInstallation-P4. | Field-engineer report and telemetry record are current to different times; lab reproduction is absent; service-impact extent is disputed. Field service may update observations but cannot accept product safety. | Continue bounded diagnosis, obtain lab evidence, and keep release effect unresolved. |
ReleaseCandidate-R42 passed tests T1–T8; T9 remains blocked by rig access. | Signed test results identify candidate and fixture versions; the test-rig booking is current but does not prove a completed test. Release authority remains separate. | Await exact rig access and T9; no release from card status. |
SafetyQuestion-S19 has no current specialist decision. | The issue record contains a question and evidence request, not a safety verdict. Only the named safety authority can return the needed result. | Hold the affected release use or narrow its scope under the current authority rule. |
ProviderChange-P8 changes model-artifact access after the current window. | Contract and technical-access records disagree on effective date. | Resolve the access relation or choose the supported incumbent route. |
| Weekly evidenced-release commitment is at risk. | Incident, test, provider, and release claims have different horizons and authority. The account displays the relation without collapsing them into one status. | Release, hold, rollback, narrow, or renegotiate only through the corresponding authority and evidence. |
The product-side control view separately represents FieldTelemetryObserver-O4, DeployedController-C17, plant FieldPumpInstallation-P4, FieldModeSupervisor-S1, and their direct relations where supported. The operating-supervision view represents reports from PumpWorks-ControlServiceOps and constraints returned by ReleaseSupervisorTeam-S2. Qualify each timing claim needed for the decision: the rates at issue are sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change.
For a shift or model-session handoff, the next participant must recover the operating question, five subject claims above, evidence versions, unresolved conflicts, permissions, next permissible Work, and stop. If recovery requires private memory or an unrecorded chat, A.15.8 returns the exact missing carrier, update/use relation, cue, or support condition. OPS.4 then repairs the operation-specific account claim or view.
Reopen only the affected claim when new telemetry arrives, T9 completes, safety authority returns a decision, provider access changes, a commitment is renegotiated, or a participant view can no longer support its action.
OPS.4:5.1 - Recover after a late observation
At 10:10 a participant receives a field report observed at 09:00. Its stated currentness window ended at 10:00. It cannot replace a 10:05 observation merely because it arrived later. The incident lead keeps the report as evidence about 09:00, marks the present field condition unknown where no current observation exists, and asks the field owner for a refresh. T1–T8’s laboratory evidence remains valid for its separate tested configuration and claim.
The next coordinator cannot open the raw field source. The handoff therefore includes the qualified claim, observation and receipt times, the source owner’s reachable confirmation route and the unverified present condition. The receiver acknowledges that the live-field decision is blocked; read access to the shared document does not resolve it. If the maintained incident document already carries these facts and this handoff, it is the OPS.4 account—no parallel register is required.
OPS.4:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| single-source-of-truth bias | One database or screen is treated as the world and final authority. | Preserve exact claims, provenance, conflicts, permissions, and receiving decisions. |
| visibility-as-alignment bias | Everyone can see the board, so coordination is assumed. | Test whether each participant can recover the next decision and any material disagreement. |
| consensus bias | Conflicting qualified claims are forced into one status. | Keep disagreement explicit with evidence reach and resolution condition. |
| freshness bias | The newest timestamp is assumed current for every horizon. | State claim-specific currentness and expiry for the receiving use. |
| access-authority bias | The ability to edit or view is treated as authority to decide. | Recover permission and decision authority separately. |
| representation-as-control bias | A loop or control room is treated as feedback closure or operating Method. | Recover actual relations and keep view, account, rates, and stronger claims distinct. |
| memory-repair bias | People or models are told to remember more after handoff failure. | Use A.15.8 to recover the missing state, carrier, update/use relation, cue, or support condition. |
OPS.4:7 - Conformance Checklist
- The account begins from named participants, decisions/actions, horizons, and useful stops.
- Exact OPS.3 subjects, commitments, and direct relations remain recoverable in every relied-on view.
- Each current claim states content, scheme, time/horizon, conditions, evidence/provenance, uncertainty, and receiving action.
- Observation, prediction, plan, record, decision, and world-state claims remain distinct.
- Disagreements, missing observations, stale evidence, and specialist returns remain visible with their decision reach.
- Read, write, annotate, accept, hold, release, responsibility, capability, and authority relations are not inferred from one another.
- Next decisions and permissible Work name their enabling or blocking conditions.
- Participant views preserve subject and claim correspondence, make omitted scope and claim conflicts visible, and provide a return to the owning account.
- Any selected control view returns to the actual observation/intervention relations and to the direct support for its stronger claims.
- Participants can recover updates that affect their use; applicable expiry, supersession, conflict and recovery conditions are retained.
OPS.4:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Build one dashboard for everyone.” | Start from participant actions and select claims and views for each, with correspondence and return. |
| “Green means done.” | Recover the subject state, commitment, evidence, acceptance or fulfilment result, and authority. |
| “Latest update wins.” | Apply claim-specific currentness, source reach, conflict, and supersession rules. |
| “Make everyone agree.” | Preserve qualified disagreement and name the evidence or authority needed for resolution. |
| “If it is editable, the team owns it.” | Separate access, permission, responsibility, assignment, and decision authority. |
| “The control room closes the loop.” | Recover the in-life relation sides and rate claims; treat the display as a representation. |
| “The handoff failed because attention was low.” | Identify the missing subject claim, carrier, update/use relation, cue, permission, or stop. |
OPS.4:9 - Consequences
An accessible, current account lets the next participant recover the state of the work and the conditions for proceeding across shifts, tools, teams or interruptions. A participant can identify a permitted next action or report the specific condition that still blocks it. Different views can preserve the same subject identity and any material disagreement.
The cost is explicit provenance, permission, conflict, and refresh maintenance. Some attractive dashboards become secondary because they cannot preserve the claim and authority distinctions needed by the decision.
OPS.4:10 - Rationale
Shared attention is an operating achievement when participants can coordinate from qualified claims about the same subjects and commitments. Seeing the same display is insufficient if the next participant cannot recover the meaning of a claim or its authority. Where claims disagree, both can still be available for the decision. A small decision-specific account preserves the distinction, while FPF continues to govern epistemes, evidence, Work-performance recovery, structures, and control claims.
OPS.4:11 - SoTA-Echoing
The question is whether the next participant can act from a current, qualified operating account. A competent incumbent is SRE incident practice with separated responsibilities, a maintained live incident document, communications and an acknowledged handoff. Google SRE, “Managing Incidents” develops those mechanisms, including a usable document when the affected service cannot host it. OPS adopts this arrangement.
At PumpWorks, a good incident document can already identify I73, its commander, current actions and next handoff. When that account also distinguishes field-observation time from receipt time, laboratory evidence from current installation state, and release authority from document access, it suffices. Sections 4.1–4.3 ask for those distinctions where a recipient’s action or what the recipient can justify depends on them. The residual in section 5.1 is concrete: an expired field claim cannot supply the current evidence required for a live intervention, yet the laboratory results remain usable. A receiver lacking raw-source access needs an effective confirmation or an explicit blocker, not a second copy labelled current.
The extra work is qualifying the few decision-bearing claims, maintaining their different expiry conditions, and testing that the recipient can recover them. Frequent rechecking can itself consume scarce attention and delay response. Use the shortest refresh and handoff arrangement that preserves the decision, keep a qualified unknown instead of fabricating certainty, and reuse the incumbent’s document and roles. If those provisions already exist, adding an OPS template would be pure maintenance burden.
FPF C.2.1, A.15.8, A.10 and C.27.TA supply account, recovery, evidence and temporal distinctions. OCEL and object-centric methods help retain different event-object histories, but the use of a log for a current-state claim depends on its meaning, coverage and time. Control relations matter only for an actual observation-and-intervention question. DORA and agent-runtime sources remain bounded software-use comparisons, not a general theory of attention. Reopen this selection when a stronger existing account gives the same recoverable decisions more cheaply, or a failed handoff exposes an omitted claim, permission or source-access condition.
OPS.4:12 - Relations
OPS.3can supply identified subjects, relations, records, state claims and provenance, with any relevant conflicts, permissions or gaps.OPS.2supplies selected participant and control views plus correspondence obligations.C.2.1governs the claim-bearing account episteme;A.10governs evidence reliance;A.15.8governs the general Work/WorkPlan performance-configuration and recovery question.C.30.LCA,B.2.5,C.27.TA,C.27, andA.3.3govern the conditional control structure, relation, and rate/dynamics claims. OPS.4 retains operation-specific commitments, state, intervention, authority/evidence, and consequences.OPS.5later consumes current eligible demand, commitments, and uncertainty for admission.OPS.6consumes case state and permissible next Work.OPS.15andOPS.18remain separate inspectability and operating quality/reliability decisions.- Security, privacy, law, safety, medicine, product engineering, finance, governance, and other specialists retain their evidence, permission, authority, and decision results.
OPS.4:End
Part III — Admit Demand and Continue Cases
OPS.5 - Admit Work and Limit Starts
Status: Stable
OPS.5:0 - Use This When
Use this pattern when you must decide which eligible demand to admit now under the authority and start limits in force. An item can look ready before the conditions for its start are met. Typical cues are “pull the next item”, “approve this case”, “the card is top priority”, “the agent is free”, “the rig has an opening”, or “we already selected it” without a current admission decision, start permission, or explicit start limit.
The first useful result is one bounded admission account:
For eligible demand
Dserving operating result or commitmentR, under criteria and non-negotiable conditionsK, explicit-start limitL, deciding authorityA, configuration and horizonH, each considered item isadmitted,deferred,rejected, orreturned; an admitted item has effective start conditions and an authorized starter where one exists; identify any residual demand and the next review or return that is needed.
Recognition asks whether this demand may enter now. Assurance establishes its admission criteria, start permission and effective bound; any later performance or fulfilment claim needs its own evidence.
Do not use OPS.5 to design a queue or buffer policy, identify or exploit the current constraint, size capacity under variability, coordinate interacting structures, or make a whole-service commitment credible. Use a relevant result from OPS.8–OPS.13 or a qualified direct source. When that result is missing, identify the question for its provider. If the current problem is continuing an already admitted case after facts changed, use OPS.6. If age, dependency, risk, or consequence may revise priority or an existing commitment, use OPS.7.
OPS.5:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| eligible demand | An identified demand item, such as a request, need, condition, case, or candidate Work item, that may be considered for current admission. Identify the demand claim and the subject it concerns separately. Eligibility makes it a candidate for this decision, not a permitted start. |
| option or request | A possible demand item presented for consideration. Its presence in a list or account creates no right to admission. |
| admission decision | A bounded decision about whether an identified demand item may enter the selected current coordination account under stated criteria, limits, horizon, and authority. |
| admitted item | Eligible demand whose admission conditions obtain for the stated configuration and horizon. Admission permits a further start decision under its conditions; it does not establish start or result. |
| deferred item | Demand not admitted now, with the observation, condition, horizon, or changed fact that would make reconsideration useful. |
| rejected item | Demand declined for this operating use, with its reason and any receiving return that another owner can answer. |
| returned item | Demand for which a named missing, stale, unsupported, or externally owned condition prevents this admission decision. |
| start permission | An obtaining permission or authorization for the admitted matter under effective conditions. A comparison or selected answer is not permission unless the deciding System also has and exercises the required authority. |
| explicit-start limit | A stated bound on what may be started now for this operating use. Identify the unit, period and counting rule for this limit. |
| commitment | A promise or obligation with parties, content, conditions, horizon, authority, and status. Admission can rely on or create a bounded commitment only where the relevant authority is present. |
| authorized starter | The System permitted to initiate the admitted Work under the effective conditions. Responsibility, capability, availability, and permission remain separate. |
| Work occurrence | Dated Work whose occurrence is established from performance evidence, independently of the demand-admission decision. Use a card change, approval, plan, invocation or artifact as evidence only for the Work it actually records. |
| residual demand | Every considered or still-relevant demand item not in the admitted set, with enough identity and disposition to avoid hidden starts or silent loss. |
| admission result | The dispositions, reasons, conditions, authority, horizon, starter relations, residual demand, and next review or return that make the admission decision usable. |
OPS.5:1 - Problem Frame
Continuing operation may receive more apparent demand than it can start under its commitments and operating limits. Requests arrive through customers, incidents, clinical cases, release candidates, providers, planned changes, automated agents, and internal commitments. Each item may be valuable, urgent, visible, or technically ready while still lacking the identity, evidence, permission, access, authority, or explicit-start condition required now.
Decide which demand can enter current operating coordination. Keep the remaining demand visible and distinguish admission from evidence that Work started.
OPS.5:2 - Problem
Boards and intake systems compress unlike truth states. “Ready”, “selected”, “approved”, “assigned”, and “in progress” become interchangeable labels. A high priority is treated as permission; an available performer as authority; a scheduled slot as capacity; a generated change as started Work; and an admission decision as a fulfilled commitment.
The opposite failure keeps every item nominally open. Nothing is explicitly rejected, deferred, or returned, so the operation accumulates hidden commitments and starts. Practitioners cannot recover which demand was considered, why it did not enter, or what would justify another look.
OPS.5:3 - Forces
| Force | Tension |
|---|---|
| responsiveness versus truthful starts | Delay can harm service, but premature starts create hidden Work, interruption, or unsafe continuation. |
| common intake versus unlike subjects | A shared account aids coordination, but incidents, patients, release candidates, provider changes, and rig requests retain different identities and conditions. |
| comparison versus direct rule | Several live alternatives may need choice, while mandatory or recognition-based conditions should not be converted into an artificial option contest. |
| local limit versus wider policy | One explicit-start bound can close the current decision without claiming a complete queue, capacity, or constraint Method. |
| visibility versus authority | Making demand and evidence visible helps, but neither visibility nor rank grants permission or commitment authority. |
| fast admission versus adequate evidence | A short-horizon answer is useful only if evidence currentness, conditions, and reopen triggers remain explicit. |
| focus versus residual demand | A bounded admitted set reduces active burden, but deferred, rejected, and returned demand must not disappear. |
OPS.5:4 - Solution
OPS.5:4.1 - Recover the inputs needed for admission
Name the deciding operating System, receiving result or commitment, configuration, and horizon. Reuse matching current OPS.2, OPS.3, and OPS.4 results when their account of the coordination form, subjects, relations, evidence, permissions, commitments or gaps bears on admission or its grounds. If a needed input is stale, mismatched or missing, use a qualified replacement or say how the gap limits this decision. Other admissions can proceed on independent grounds.
OPS.5:4.2 - Name each exact demand item and its proposed use
For every item under consideration, state the demand subject, claimant or source, proposed operating result, relevant commitment, and why admission is current. Keep a request, option, candidate Work item, admitted item, commitment, start permission, and performed Work separate even when one record represents several of them.
OPS.5:4.3 - State criteria, non-negotiable conditions, and the explicit-start limit
Record the conditions on which admission depends. Identify the item and what the proposed start must supply. Check its readiness, evidence, permissions, performer and access against that use. Apply the specialist conditions, commitments, capacity, resource access and concurrency or start limits relevant here.
Judge readiness for the proposed consuming operation, not for every eventual use. OPS.8:4.2 supplies receiver-ready work; OPS.13:4.2 connects preparation to a promised result. Recover the applicable prerequisites and the evidence or authorized source that can confirm them. Name the start bound’s unit, interval and counting rule, including how safe stops and suspended work count. A supplied justified bound can be applied here; deriving its value is a capacity or policy question.
Some conditions are mandatory, some admit qualified comparison, and some require a return to another owner.
OPS.5:4.4 - Choose only where a real choice exists
When a direct domain rule, mandatory condition, or recognition branch gives the answer, apply it and record the basis. When several live admissible alternatives genuinely require comparison, form a stable current OptionSet and comparison basis and use C.11. If the options or comparison facts are insufficient, choose a bounded inquiry when its attainable result could improve the decision or the grounds for relying on it enough to warrant the work. Otherwise state the missing condition and its consequence.
OPS.5:4.5 - Give every item a usable disposition
Return each considered item as:
- admitted, with reason, effective conditions and horizon, governing authority, authorized starter where established, and the next review if one is required;
- deferred, with the condition, observation, horizon, or changed fact that makes reconsideration useful;
- rejected, with the reason and receiving return where another owner can answer the need; or
- returned, with the exact missing or externally owned result, what it blocks, safe stop or fallback, and when reconsideration could be useful.
Keep the residual demand visible. Record no start merely because the item is admitted.
OPS.5:4.6 - Close the local decision and expose wider returns
State the admitted set and the current limit on starts. Identify any residual demand, its disposition and the conditions for a needed review. For questions of queue order, buffer design, constraints, capacity under variability, interacting structures, whole-service commitments or specialist judgements such as clinical triage, safety acceptance, release, law or finance, use a result qualified for this decision. If a required result is missing, return that question to its owner and identify what can still proceed.
OPS.5:5 - Archetypal Grounding — Three Admission Replays
OPS.5:5.1 - PumpWorks controller service
The following observations and permissions are constructed case inputs. At 09:00, PumpWorks has an established limit of two active engineering work packages for the 09:00–11:00 window. The staffing owner has justified this bound from available performers and protected recovery work; OPS.5 applies it without deriving a universal WIP value. A package counts from actual start until completion or a documented safe stop. Waiting demand is not counted as active. T8 is already running with engineer E17 until its expected safe completion at 09:30, so one slot is free.
| Proposed work | Obtaining conditions at 09:00 | Disposition and next action |
|---|---|---|
| I73-D: inspect the captured incident logs | Exact installation and log identity confirmed; engineer E18 available; incident lead authorizes read-only diagnosis until 11:00; local copies and diagnostic procedure ready. | Admit I73-D under the incident-order exception in OPS.2:5.2. E18 starts at 09:05. With T8, there are now two active packages. No live setting change or release is permitted. |
| R42-T9: final laboratory validation | Lab testing is permitted independently of field release, but the signed fixture check is missing and the rig is occupied by T8. | Defer until the fixture check and rig access obtain; recheck at 09:40. An empty active slot alone is insufficient. |
| S19: resolve the safety question | The operating coordinator is not the safety authority. | Return the exact question and supporting material to the safety owner. Release remains blocked pending the safety decision; unrelated permitted diagnosis may continue. |
| P8-P: provider preparation | Inputs and permission exist, but it competes for E18; the resource owner confirms an afternoon review can preserve its existing obligation. | Defer to 13:00 rather than silently remove it from demand. Reopen earlier if that obligation or E18’s availability changes. |
At 09:25 E18 safely completes the bounded log inspection, as developed in OPS.6:5.1. One active slot is freed, but the incident case is not resolved. At 09:30 T8 completes. At 09:40 the fixture owner supplies the missing signed check; the rig owner and E17 confirm access, and the coordinator admits R42-T9. E17 starts its permitted laboratory procedure. This is a new bounded admission, not permission for field release.
At 09:50 the field contact becomes unavailable. The next live I73 verification is returned for restored access and matching permission rather than being counted as started. R42-T9’s independent lab permission and fixture evidence still hold, so that Work continues. The admission return records the permitted starts separately from the supplied observations of actual starts, with the active count at each time, the still-open S19 and I73 returns, and P8-P’s afternoon reconsideration. OPS.7:5.1 shows the resulting promise decision.
OPS.5:5.2 - Public-hospital emergency-care operation
An emergency-care operating function decides whether work on a patient’s case may start. It considers current observations, bed availability, service horizons, clinical and operating evidence, and the permissions the work requires. The qualified clinical service determines clinical priority and may use the patient’s waiting time as evidence.
If a required condition is missing, such as consent, clinical evidence, competence, a medical safety judgement, privacy protection or statutory permission, the result names that blocker and its owner. Operations neither supplies treatment authority nor overrides clinical judgement. The first useful result is an authorized operating admission or an exact returned condition, not a dashboard state or automatic triage result.
OPS.5:5.3 - AI-assisted software operation
One software operation considers user issues, agent episodes, candidate changes, harness and tool access, traces, test results, human decisions, and release commitments. The authorized decision maker uses current context and tool capacity, concurrency, integration burden and required evidence to decide what may start.
A model score, available agent, free context window, generated patch, or scheduled episode does not by itself establish admission, permission, performed Work, or release. The result admits only the exact bounded Work whose identity, conditions, evidence, access, authority, and start limit obtain; it identifies deferred and returned items with their conditions for reconsideration, and gives the grounds for any rejection. Security, software assurance, provider capability, agenthood, and release authorization remain direct specialist returns.
OPS.5:6 - Bias-Annotation
| Bias or pressure | How it distorts admission | Countermeasure |
|---|---|---|
| visibility and rank bias | The top visible item appears authorized and ready. | Test identity, evidence, permission, authority, and start conditions separately. |
| sunk-commitment pressure | Earlier planning or public promise is used to force admission. | Recover the actual commitment parties, conditions, authority, and current status. |
| utilization pressure | Every available person, rig, tool, or model is filled immediately. | State the bounded receiving result and explicit-start limit; preserve deliberate non-start. |
| automation bias | A model recommendation or generated artifact is treated as admission or Work. | Identify the admission decision and any authorized starter. For a claim of performed Work or a later result, check the evidence for that claim. |
| urgency leakage | Age or consequence language becomes automatic admission order. | Leave priority and commitment revision to OPS.7; use only the current admission criteria here. |
| silent-rejection pressure | Deferred or rejected demand disappears from the account. | Preserve identity, disposition, reason, retry or return, and residual demand. |
| source-school anchoring | A familiar board, backlog, buffer, or WIP rule supplies the whole Method. | Adopt only the bounded mechanism that helps establish the decision or its conditions and keep its limits explicit. |
OPS.5:7 - Conformance Checklist
- The exact operating System, receiving result or commitment, configuration, and horizon are named.
- Every considered demand item has an identity and proposed receiving use.
-
Matching
OPS.2,OPS.3, andOPS.4inputs are reused when current and relevant to admission or its grounds. - Admission criteria and non-negotiable conditions include relevant evidence, authority, permissions, access, specialist returns, and currentness.
- The explicit-start limit is bounded to this use and is not presented as a universal queue, capacity, or constraint policy.
-
C.11is used only for several real live alternatives on a stable comparison basis. - Every item is admitted, deferred, rejected, or returned with reason, conditions, horizon, and any review or return required by that disposition.
- The authorized starter is named only where that relation is established.
- Residual demand remains visible.
- Admission is not claimed as started or completed Work.
- Wider Operations and specialist questions return to their direct owners.
OPS.5:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| top card means start | Rank substitutes for authority and permission. | Record admission, permission, starter, and start conditions separately. |
| everything is “in progress” | Hidden starts erase residual demand and overload the operation. | Apply an explicit-start limit and give every item a disposition. |
| availability implies capacity | A free slot, worker, rig, tool, or model is treated as a complete capability and access result. | Recover the exact performer, resource relation, capability, permission, and configuration. |
| choose-first option set | An artificial score replaces mandatory conditions or direct rules. | Use the direct branch; compare only genuine admissible alternatives. |
| admission by artifact | Ticket creation, assignment, plan, model output, or code generation becomes “Work started”. | Establish whether Work occurred from independent performance evidence; decide admission and permission before the prospective start. |
| rejection without return | Demand silently disappears or repeatedly re-enters. | Keep the reason, residual identity, owner, and retry condition. |
| local rule claims the system | One start limit becomes a universal WIP, queue, capacity, or constraint Method. | Bound the result and return wider policy questions. |
OPS.5:9 - Consequences
The operation gains a usable distinction between demand and current starts. Participants can see what entered, what did not, why, under whose authority, for which horizon, and what should be reviewed. Hidden starts and silent residual demand become easier to challenge.
The cost is explicit identity, evidence, conditions, authority, and disposition work. Some demand remains visibly deferred or returned rather than cosmetically “active”.
OPS.5:10 - Rationale
Admission is valuable because it protects the boundary between possible demand and authorized current Work. Combining it with queue design, performed Work, or service assurance would make a locally usable decision depend on much wider results and would hide exactly where permission and evidence are needed.
The four dispositions prevent the false binary “start or lose”. Direct rules remain direct, genuine alternatives can be compared, and residual demand stays available for reconsideration or specialist return. The pattern therefore closes the smallest decision that lets a continuing operation limit starts while leaving unresolved queue, constraint, capacity, interacting-structure, and whole-service questions for their own decisions.
OPS.5:11 - SoTA-Echoing
The question is which prepared work may start now. The serious comparator is competent policy-governed pull. The Kanban Guide 2025.5 already provides explicit workflow policies and active-work control; TameFlow’s preparation account adds useful-package readiness and distinguishes optional from committed demand. OPS adopts these contributions.
Apply both approaches to section 5.1. Using a capable pull policy, the coordinator can identify the free slot, preserve the WIP bound and admit I73-D under the authorized exception. E18 then starts the work. The possible residual is narrower: the fixture readiness required for R42-T9 differs from the safety decision required for release, and the operating coordinator cannot manufacture the latter. Sections 4.3–4.6 distinguish those consuming uses, apply the existing bound and return S19 to its owner while retaining permissible work. If the incumbent’s policies and records already do this, they are the adequate admission arrangement.
The addition costs a check of current prerequisites and permission, an exact return for a missing condition, and follow-up on deferred demand. Where eligibility rarely changes and one authority already covers the operation, a separate per-item OPS form costs more without altering starts. Reuse the existing policy and item record; do not duplicate its queue history. Where multiple authorities or prerequisites differ by action, that bounded work can prevent a ready-looking item from acquiring a permission it lacks.
FPF C.11 supplies comparison among genuine admissible alternatives; it neither sets the bound nor grants permission. Reinertsen’s historical queue and economic mechanisms inform policy questions returned to OPS.8–OPS.10. No universal WIP value, service guarantee or proof of completed Work is imported. Reopen when the unit or counting rule, readiness, authority or protected capacity changes, or when the incumbent supplies the same dispositions with less total work.
OPS.5:12 - Relations
- Use the coordination form selected through
OPS.2when admission or its grounds depend on that form.OPS.3supplies exact operating subjects and direct relations.OPS.4supplies current claims, evidence, permissions, commitments, uncertainty, and gaps. None of those results admits demand by itself. C.11governs comparison only when several live admissible alternatives require choice.A.10governs evidence reliance;A.15.8governs performance-configuration and recovery questions when they become the actual blocker.OPS.6consumes the applicable admission and independently supported current permission for the same matter and conditions; an admission account may carry both results.OPS.7separately governs current priority or bounded commitment revision.OPS.8–OPS.13retain queue, buffer, constraint, capacity, interacting-structure, and wider commitment questions.- Clinical, safety, legal, privacy, security, finance, product release, capability, and other specialist practices retain their subjects, evidence, permission, authority, and conclusions.
- Practitioners may enter OPS.5 directly when matching current inputs already exist, repeat it as demand changes, or stop after its result.
OPS.5:End
OPS.6 - Continue Cases and Handle Exceptions
Status: Stable
OPS.6:0 - Use This When
Use this pattern during one admitted continuing case when current facts, an exception, or a changed condition makes the standard next action uncertain. Typical cues are “the normal route no longer fits”, “the ticket moved but nothing changed”, “the model recommends a fix”, “we are waiting for one more result”, or “who may act now?” while the case subject, permission, performer, evidence, and next permissible Work are unclear.
The first useful result has one of two forms:
Progression: for case subject
Sin qualified stateQat configuration and horizonH, matching permissionPand domain MethodMsupport next WorkWby responsible performerR, with stop or fallbackFand expected evidenceE; after independently supported performance, report the progressed stateQ'and its evidence to the participant responsible for the next operating decision under return conditionsN.Blocker: condition
Kis missing, stale, contradicted, unauthorized, unsafe, unsupported, or unavailable; the result needed from sourceOis specified; the safe fallback or stop isF; reconsider whenTmakes that useful.
Recognition concerns a next action left uncertain by current case facts. Before action, assurance establishes the needed permission and performance conditions. After action, any progression claim needs performance evidence and support for the reported state.
Do not use OPS.6 to design one universal workflow or case lifecycle, reconstruct a reusable Method from event data, infer progress from a ticket, plan, model, trace, or record update, or revise priority merely because the case is old. Use A.15.7 for the general situation-responsive next-action Method, A.3.1.MR when reusable Method recovery from several performances is the actual question, and OPS.7 when temporal or consequence evidence can change priority or an existing commitment.
OPS.6:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| case | One bounded continuing Work situation organized around an exact subject, state, commitments, evidence, authority, and permissible next Work. It is not its file, ticket, queue position, or every Work item within it. |
| case subject | The patient, incident, user issue, release candidate, service relation, request, physical item, or other identified subject around which continuation is being coordinated. |
| case-state claim | A qualified claim about the case subject and relevant relations at a stated time or horizon. Revise it when warranted by new evidence, a corrected interpretation or a change in its conditions of use. |
| exception | A fact or condition for which the standard continuation branch is absent, contradicted, no longer adequate, or requires bounded choice or return. It is not automatically an error or rare event. |
| matching admission and permission | The applicable case admission and independently supported current permission for the same matter, effective conditions, configuration, and horizon. A valid OPS.5 result may carry both; admission alone is not permission. |
| deciding System | The System authorized to select or confirm the next permissible Work. It may differ from the responsible performer. |
| responsible performer | The System assigned and capable for the selected Work under its conditions. Assignment, capability, permission, authority, and performance remain distinct. |
| next permissible Work | The exact Work that may occur next under the applicable domain Method, permission, obligations, evidence, and stop conditions. A task description or tool call alone does not show that this Work was performed. |
| action choice | A selected next Work, probe, fallback, stop, or return. Choice does not perform the Work or progress the case. |
| Work occurrence | Dated performance admitted from direct evidence under the relevant configuration. Intention, assignment, invocation, trace presence, or artifact creation does not establish it alone. |
| evidence expected from performance | The observations, produced results, or records needed to judge what occurred. State the claim each supports, including any claim of a changed subject state or a failure. |
| record update | A change to a ticket, case file, plan, model, trace, database, or dashboard. It may carry evidence but is not the case-state change by itself. |
| unmet condition | The exact missing, stale, contradicted, unauthorized, unsafe, unsupported, or unavailable condition that prevents a truthful next action or progressed state, together with its return or stop. |
| progression result | Either an evidenced progressed case state with its next return, or an unmet-condition return with owner, fallback or stop, and retry condition. |
OPS.6:1 - Problem Frame
Continuing cases do not simply advance because a standard sequence exists. New observations, dependency failures, changed permissions, resource relations, specialist decisions, or unexpected outcomes can make yesterday’s next action unsafe, impossible, or irrelevant. The operation still needs a bounded way to continue without replacing the applicable clinical, engineering, legal, safety, security, or other domain Method.
Select the next permissible Work from the current situation. Report what progressed only when the performed Work and its result are supported. When a prerequisite is missing, identify the condition that limits continuation.
OPS.6:2 - Problem
A selected workflow transition can be mistaken for performed Work or an evidenced change in the case. A case-file state, agent loop, plan update, model recommendation, or “done” ticket appears to settle the case even when no authorized performer acted or the resulting subject state is unknown.
The opposite failure treats every exception as improvisation. Practitioners bypass mandatory domain branches, create an ungoverned OptionSet, or keep analyzing without a responsible performer, stop, evidence expectation, or return. Cases then drift between records while obligations and commitments remain unresolved.
OPS.6:3 - Forces
| Force | Tension |
|---|---|
| responsiveness versus currentness | Cases need timely continuation, but stale facts or permission can make the selected action inapplicable or harmful. |
| domain Method versus local exception | The applicable Method constrains permissible Work, yet current facts may require recognition, adaptation, comparison, probe, or return. |
| chooser versus performer | The System that decides may not perform; collapsing them hides assignment, capability, permission, and responsibility. |
| action versus evidence | Selecting a good action is useful, but it does not show that Work occurred or the case changed. |
| recordability versus subject truth | Files and transitions support coordination, but they represent rather than constitute the case subject and state. |
| automation speed versus authority | Automated episodes can run quickly, but tool access and output do not establish permission, software assurance, release, or accountable continuation. |
| progress pressure versus honest blocker | A visible “next state” is attractive, while naming an unmet condition may be the only truthful result. |
OPS.6:4 - Solution
OPS.6:4.1 - Confirm the case and matching permission
Name the exact case subject, current configuration and horizon, and the demand or commitment being served. Recover the applicable admission and the required current permission for the same matter and conditions. A valid OPS.5 result may carry both; admission by itself does not establish permission. If the required permission is absent, expired, or contradicted, return that blocker to the authority or source that can resolve it; do not select Work or claim progression under a merely similar item, earlier approval, queue rank, or general mandate.
OPS.6:4.2 - Establish the current conditions for continuation
Recover the current qualified case state, applicable domain Method, obligations and operating commitments, the evidence for continuing and the conditions under which it is still current, relevant permissions and authority, and the condition that made continuation uncertain. Follow the claims that can change the next action, the conditions for relying on it or the conclusion the recipient needs. Reuse unaffected case claims within their established conditions.
OPS.6:4.3 - Separate decision, performance, records, and state
Name the deciding System, responsible performer, required permission or authority, available actions, Work proposed or selected for performance, records used or changed, and the state claims the result may support. Do not infer one relation from another. If performer capability, assignment, access, permission, or authority is missing, return that exact condition.
OPS.6:4.4 - Use the least elaborate adequate steering branch
Apply the direct mandatory branch when a current rule and facts determine the next permissible Work. Use recognition when one current situation clearly matches a governed action. Adapt within the applicable domain Method when a bounded variation is authorized. Use C.11 only when several admissible live actions genuinely require comparison. Select a bounded probe when its expected result could improve the decision or its grounds enough to warrant the burden. When no permissible action is available, report the stop and its basis. Seek another candidate or a missing contribution through the relevant practice if it can give the recipient a useful continuation.
OPS.6:4.5 - Specify the executable continuation contract
State the selected next Work, responsible performer, permission and effective conditions, stop or fallback, expected evidence, and the return to continuing operation. Name the observable change that would invalidate the action and require refresh. An existing plan, instruction, prompt, ticket-transition record, or model recommendation can carry this contract if it states these terms and identifies the required authorization.
OPS.6:4.6 - Admit performance and update state separately
After the Work, recover direct performance evidence, the result, any change to the subject, and any failure or limit, and the claim each observation supports. Update the case-state claim only when the relevant Work and resulting evidence are independently adequate. If Work did not occur or evidence is insufficient, retain only earlier claims whose support still holds and return the unmet condition. A contradicted or expired claim becomes unsupported or unknown; it is not restored merely because a new result is missing. Never use a record update, successful invocation, generated artifact, or selected action as automatic progression evidence.
OPS.6:4.7 - Return one usable result
Return either:
- an evidenced progressed case state, its evidence and limits, fulfilled or still-open obligations, and next return; or
- the unmet condition, direct owner or source of the needed result, safe fallback or stop, and exact retry condition.
Return a required priority, commitment or policy decision to its Operations owner, and a specialist decision to the practice that can supply it. The continuation result does not inherit their authority.
OPS.6:5 - Archetypal Grounding — Three Continuing-Case Replays
OPS.6:5.1 - PumpWorks field incident
Continue the constructed matter in OPS.5:5.1. At 09:05, incident I73 remains unresolved on installation P4. A field report describes intermittent pressure readings; neither their cause nor correction is known. The incident lead has authorized engineer E18 to inspect the identified captured logs until 11:00. The permission allows reading and diagnosis, not altering the deployed controller, declaring safety or releasing R42.
The applicable diagnostic procedure says: compare the captured sensor and controller timestamps; if the discrepancy persists in the captured interval, retain the discrepancy claim and request live verification; if identity fails or the data are corrupt, stop and return to the log owner. This direct rule is sufficient—no alternative-ranking exercise is needed. The incident lead chooses the bounded continuation; E18 performs it. The expected evidence is the identified input, execution trace, comparison result and its time interval.
The supplied observations are: E18 performed the comparison from 09:05 to 09:25; the retained trace identifies the P4 capture and comparison; a timestamp mismatch occurs in that capture; no live verification or controller change was performed. The defensible update is “discrepancy established in the captured interval; live cause and present field condition unresolved.” It is progress in diagnosis, not restoration of the installation. E18 returns the trace and this limited claim to the incident lead, closes I73-D at a safe stop and requests observational live verification in the 10:00–11:00 contact window. At 09:30 the field owner confirms access and the required permission for that bounded observation, without authorizing a setting change.
At 09:50 the field contact withdraws availability. The lead cannot start live verification under the earlier access assumption. The result becomes a returned access-and-permission condition, with the field owner as recipient and confirmed contact plus matching permission as the retry condition. Offline analysis of the already authorized capture remains allowed. The separate R42-T9 lab procedure, fixture check and performer are unaffected and remain in use; its result at 10:10 can support only its laboratory criterion. The operation does not erase the captured discrepancy or assert a current safe field state from the lack of a new report.
The next participant receives the bounded diagnostic result, the live-verification blocker, still-permitted work and the next useful contact action. For a priority or promise decision, use those facts through OPS.7 and identify who has the authority for each proposed change to priority or the promise.
OPS.6:5.2 - Public-hospital clinical case
One admitted clinical case continues from the exact patient and clinical-case subjects, current observations, applicable clinical and operating Methods, authorized practitioners, bed and resource relations, service obligations, and current consent, privacy, safety, and statutory conditions. A qualified clinical System retains medical decisions.
Use the authorized clinical result and applicable operating criteria to identify the next permitted Work, its responsible performer, stop or fallback, and the evidence needed to update the case-state claim. Missing consent, clinical evidence, bed relation, competence, medical-safety return, or statutory permission remains an unmet condition, not an Operations workaround. A record closure, bed-board move, or elapsed wait does not establish treatment, patient change, or clinical resolution.
OPS.6:5.3 - AI-assisted user issue
An admitted user issue encounters a changed trace, tool result, provider condition, model input, candidate change, or harness state. The operation refreshes evidence and applies the software domain Method and current established authority. It distinguishes the human or other deciding System, the responsible performer, agent episode, tool invocation, candidate change, test evidence, issue record, and release decision.
The continuation contract may authorize one bounded diagnostic, test, or repair Work with context and tool limits, stop, fallback, expected evidence and the responsible recipient, including a human reviewer when the case requires one. Report issue or candidate progression only after performance evidence supports it. A successful episode, green local test, visible trace, automated loop, or generated patch does not by itself establish issue progression, an integrated change, software assurance, a security result, or release permission.
OPS.6:6 - Bias-Annotation
| Bias or pressure | How it distorts continuation | Countermeasure |
|---|---|---|
| workflow-state bias | A configured transition becomes the case truth. | Recover the exact case subject, performance evidence, and qualified state separately. |
| action bias | Selecting any next step feels better than returning a blocker. | Use direct mandatory and recognition branches first; return when no permissible action exists. |
| automation bias | A successful agent episode or model output is treated as progress. | Separate invocation, Work, artifact, evidence, integration, and case-state claims. |
| plan-completion bias | Updating a plan or checklist appears to satisfy the obligation. | Name the actual Work, responsible performer, result, and evidence expected. |
| stale-permission bias | Earlier permission is reused after conditions changed. | Match matter, conditions, configuration, horizon, and authority before selection. |
| expert-shadowing bias | Operations quietly substitutes for clinical, safety, legal, or engineering judgement. | Use a qualified specialist result or ask its provider for the needed answer. Make the coordination decision within the operating authority. |
| exception novelty bias | Every surprising event is treated as unprecedented improvisation. | Reuse the applicable domain Method and choose the least elaborate adequate branch. |
OPS.6:7 - Conformance Checklist
- The exact case subject, configuration, horizon, and served demand or commitment are named.
- The required current permission is supported for the same matter and conditions; admission alone is not treated as that permission.
- Current case state, domain Method, obligations, commitments, evidence, and exception are recovered.
- For Work selected to proceed, identify the authorized chooser and the capable, assigned performer. If either is missing, identify the condition that prevents action. Use evidence of performance and its effect for claims about them.
- Direct mandatory or recognition branches are used when adequate.
-
C.11is used only when several admissible live actions genuinely require comparison. - The continuation contract names Work, performer, conditions, stop or fallback, expected evidence, refresh, and return.
- Case progression is reported only after independently supported Work and adequate resulting evidence.
- The result is either evidenced progression or an exact unmet-condition return with owner, fallback or stop, and retry.
- Specialist and wider Operations results remain with their owners.
OPS.6:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| workflow transition equals progress | A representation substitutes for changed case state. | Require independently supported Work and resulting evidence. |
| selected action equals Work | A choice or instruction becomes a performance claim. | Name performer and admit the dated Work separately. |
| agent ran, therefore case advanced | Invocation and output hide authority, integration, and subject evidence. | Preserve episode, Work, artifact, test, integration, decision, and state distinctions. |
| generic exception handler | One fallback overrides domain Methods and specialist returns. | Recover the applicable Method and exact unmet condition. |
| chooser-performer collapse | Decision authority, assignment, capability, and performance become one relation. | Name and support each relation independently. |
| stale authorization carryover | Permission survives changed conditions by default. | Revalidate exact matter, configuration, horizon, and effective conditions. |
| endless analysis | No responsible performer, stop, evidence expectation, or return is stated. | Produce the executable continuation contract or a blocker return. |
OPS.6:9 - Consequences
The operation gains a defensible continuation move for exceptional and changing cases. Practitioners can tell what may happen next, who should perform it, what evidence will count, when to stop, and whether the case truly progressed or remains blocked.
Checking performance and the subject’s state takes time and may require evidence from another participant. When that evidence is missing, the recipient can act on the specific limitation without mistaking a record change for progress.
OPS.6:10 - Rationale
Case continuation sits between permission and evidence. If it collapses into admission, selection appears to perform Work. If it collapses into priority or commitment management, elapsed time or consequence pressure can bypass the applicable domain Method. Keeping the continuation contract and the later state update separate makes exceptions usable without inventing a lifecycle.
The two-result form is deliberate. An exact unmet condition with owner, safe fallback, and retry can be the complete useful Operations result. It prevents administrative state changes from hiding missing permission, capability, evidence, or specialist conclusions.
OPS.6:11 - SoTA-Echoing
The decision is how to continue a case after new facts while reporting a defensible result. A strong incumbent combines authorized case planning with outcome-aware execution. CMMN 1.1, §4.1 and §5.4.9 supplies runtime discretion, procedural subwork and planning authorization. Current DCR robot documentation distinguishes effect success, failure and timeout and the associated continuation. OPS adopts these mechanisms.
In I73, such an arrangement can authorize log inspection, execute a diagnostic activity and route a failed or unavailable live verification. If its case contract already states the capture identity, evidence interval, external subject claim and receiving authority, it produces the same adequate continuation as OPS.6. A second contract would only add synchronization work. The residual arises when an engine’s successful diagnostic activity is used as evidence that the physical installation is now restored. Sections 4.5–4.7 bind the operation’s observation to its warranted subject-state claim: the capture shows a discrepancy; present field condition remains unresolved. Loss of contact stops the dependent action without invalidating independent laboratory work.
That addition costs the domain mapping from execution outcome to observation and subject claim, a check of current permission, and a return the next participant can use. Use a sufficient direct procedure and its existing evidence. Additional logging is warranted when the receiving decision needs it and the cost or delay is acceptable within the applicable requirements.
FPF A.15.7 supplies situation-responsive steering and C.11 the conditional comparison branch. DEMO helps distinguish production and coordination; software-runtime sources inform bounded automation and stopping. Their execution semantics, source-local roles and software evidence do not grant external domain authority. Reopen when the incumbent already preserves the same physical-subject and permission distinctions more cheaply, or changed evidence, permission or execution semantics defeats the current continuation.
OPS.6:12 - Relations
OPS.5supplies admission and may carry independently grounded start permission for the same matter and effective conditions.A.15.7governs the general situation-responsive steering Method.A.3.1.MRseparately governs candidate reusable Method recovery from several performances or other direct evidence.C.11governs comparison only where several admissible live actions require choice.A.10governs evidence reliance;A.15.8governs the performance configuration or recovery dependency when that is current.- For an
OPS.7decision, use the evidenced progression or unmet condition when it bears on a priority, commitment or the grounds for retaining either. Establish who can revise priority and who can revise the commitment when those decisions arise. OPS.8–OPS.13retain wider queue, capacity, interacting-structure, and commitment-account questions.- Clinical, medical-safety, consent, privacy, legal, software assurance, security, release, provider, capability, and other specialist practices retain their decisions and evidence.
- Practitioners may enter OPS.6 directly with matching valid permission for an admitted case, repeat it as facts change, stop at a blocker, or return to another current pattern.
OPS.6:End
Part IV — Revise Priority and Existing Commitments
OPS.7 - Manage Aging, Urgency, and Service Commitments
Status: Stable
OPS.7:0 - Use This When
Use this when further delay could affect an operating result, a coordination priority or an existing service promise. A deadline may be approaching, a dependency may have changed or new evidence may show deterioration. Identify the subject, what delay would affect, who can decide and how much time remains to respond.
State the result for the particular subject and coordination decision.
Identify the subject of the decision, its current state and the evidence about what delay would change. Give the priority decision and its authority if established. If either remains unresolved, identify what prevents the decision or its use. For an affected promise, give its parties, conditions, horizon, authority and current disposition. Give the immediate action or blocker, the affected parties, how long the result applies, the limits of the evidence and the next review.
One System may hold both authorities. If a required authority is missing, identify which decision must wait.
Recognition asks what further delay could change for the case or for a decision about it. Assurance needs the temporal evidence, consequence and the distinct authority for priority, promise revision and any specialist action.
Use OPS.8–OPS.13 for wider queue, constraint, capacity and service-commitment questions, and OPS.18 for operating quality and reliability. Clinical triage and release require their own authoritative decisions. Use C.27 for an intervention-sensitive claim about a change in rate, rhythm, recovery or regime.
OPS.7:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| exact subject or case | The incident, patient case, user issue, release candidate, service relation, request, or other subject whose temporal and consequence claims matter. A queue item or record may refer to this subject. |
| state claim | A qualified claim about the subject and relevant relations at a stated time or horizon. |
| age | Elapsed time since a defined event for an exact subject under a stated clock and conditions. Age is not urgency, priority, or rank. |
| time remaining | The interval between the current reference time and one relevant horizon under stated assumptions. A deadline alone creates no permission. |
| rate or trend | A relation concerning change per interval or a supported direction across observations. Attributing the change to an intervention requires evidence for the connection. |
| intervention-sensitive temporal claim | A claim that an intervention changes a rate, rhythm, recovery, inertia, or regime. It requires the stronger discipline of C.27. |
| urgency | A decision-relative judgement that delay can change a named consequence, commitment, risk, recoverability, or supported use. |
| priority | A current relation used for one coordination decision. It may inform but does not automatically equal queue position, admission order, clinical triage, economic value, authority, or service promise. |
| queue rank | A position under one queue policy and unit definition. Use rank here when the decision depends on the queue policy. |
| bounded commitment | An existing promise or obligation with parties, result or service, conditions, horizon, authority, and current status. |
| commitment disposition | Preserve, clarify, renegotiate, or withdraw an existing bounded commitment under the applicable authority and conditions. |
| whole-service commitment account | A wider account relating demand, resources, capability, uncertainty, service outcomes, and credible promises. Use OPS.13 to develop that account. |
| priority-and-commitment result | The current priority disposition and reason, the status of any affected commitment and any authorized change, immediate coordination action or blocker, parties, horizon, evidence, and next review. |
OPS.7:1 - Problem Frame
Time matters in operations because delay can alter consequences, commitments, dependencies, recoverability, and the usefulness of later action. Yet the same elapsed time can mean different things for an incident, patient, release candidate, provider change, user issue, maintenance condition, or administrative request.
Decide what the temporal evidence supports for the operating question. It may justify retaining or changing the current priority. If a promise is affected, identify what remains supportable and who may change it.
OPS.7:2 - Problem
Age dashboards and escalation scores compress distinct claims. The oldest item appears most urgent; urgency appears to dictate queue position; a missed horizon appears to authorize release, treatment, staffing, or spending; and one local reprioritization appears to settle a system-wide service promise.
The opposite failure treats time as display-only. Practitioners notice age or deterioration but do not connect it to consequence, recovery burden, dependency, affected parties, existing commitment, authority, or next review. Avoidable delay then becomes visible only after a promise or protected condition has failed.
OPS.7:3 - Forces
| Force | Tension |
|---|---|
| simple age signal versus decision relevance | Age is inexpensive to compute. What further delay means for the case and its commitments depends on the subject, conditions and horizon. |
| fast escalation versus authority | Delay can demand attention, but priority and commitment changes require their respective authorized Systems. |
| local coordination versus system policy | One priority disposition can change immediate Work without designing queue order, capacity, constraint, or whole-service promises. |
| current evidence versus forecast | Deterioration, delay cost, and recovery burden may be uncertain; unsupported projections should not become urgency facts. |
| fairness versus unlike consequences | A common waiting rule can be legible, while clinical, safety, service, economic, and recovery consequences remain unlike and separately governed. |
| preserving promises versus truthful renegotiation | Keeping a commitment can matter, but hiding infeasibility harms affected parties and later recovery. |
| measurement versus intervention claim | State, age, rate, and trend can be observed directly; claimed intervention effects require stronger temporal and causal discipline. |
OPS.7:4 - Solution
OPS.7:4.1 - Recover the exact subject, state, and existing commitment
Name the exact subject or case, its current qualified state, configuration and horizon, and any relevant existing commitment. For that commitment, record the parties, promised result or service, conditions, horizon, authority, current status, and evidence limits. If no such commitment exists, do not create one by calling a target, service label, or desired date a promise.
Use a progressed state or unmet condition from OPS.6 while it applies to this decision. An authorized participant decides whether those facts warrant retaining or revising priority or a commitment.
OPS.7:4.2 - Qualify the temporal claim before interpreting it
State the defining event, clock, observation time, horizon, and conditions. Decide whether the claim is current state, age, time remaining, rate, trend, or an intervention-sensitive temporal claim. Use C.27 only when an intervention is claimed to change rate, rhythm, recovery, inertia, or regime; keep the C.27.TA time-window, cadence, and currentness discipline for all temporal uses.
OPS.7:4.3 - Relate time to the decision-bearing consequences
Identify what bears on this decision or its grounds. Consider the promised service, dependencies, risk, consequences of delay, reversibility, recovery work, affected parties, evidence limits and the basis of comparison. If a proposed inquiry could improve the answer in time to matter, compare that benefit with its cost. Use qualified clinical, safety, legal, security, financial or other specialist results where needed.
Relate the remaining useful interval to the whole response: detecting the change, reaching a decision, obtaining any required agreement, and performing or communicating the remedy. Use the supported response account in OPS.13:4.4–OPS.13:4.5. An alert may arrive after the change was detected. Allow for that delay and the work still needed to respond.
Age alone does not prove urgency. Express urgency as “delay can change X for decision Y under evidence Z”, or leave it unsupported.
OPS.7:4.4 - Separate priority authority from commitment authority
Name the System authorized to maintain or change priority for the selected coordination use. For an affected commitment, identify the System that holds the relevant authority under its terms. A coordinator may have one authority but not the other. Rank, expertise, responsibility, impact, and visibility grant neither by themselves.
OPS.7:4.5 - Decide the bounded dispositions
For priority, preserve, raise, or lower it only when current evidence is sufficient and the decision is authorized; state the reason and intended coordination use. If the decision cannot be made, name the unresolved priority question, its intended recipient, and the condition for resuming the decision.
For an existing commitment, preserve it when support and conditions remain adequate; otherwise trigger authorized clarification, renegotiation, or withdrawal. When escalation or specialist return is needed, send the unresolved priority or commitment question to the participant with the relevant authority and state the decision expected from that participant. Include each unresolved question in the immediate coordination action or truthful blocker recorded in OPS.7:4.6.
A proposal to revise a promise is not the revised promise. Keep the old obligation and its current risk visible while the required parties decide; record the effective agreement, refusal or unresolved response. If continued fulfilment is no longer possible, report that fact through the authorized relation without silently substituting a new date. Apply any existing withdrawal or emergency rule on its own authority.
Use C.11 only where several real admissible dispositions need comparison. Use a bounded probe when its attainable result could improve the disposition or its grounds enough to justify the work before the relevant horizon.
OPS.7:4.6 - State immediate action, parties, horizon, and review
Record the current priority disposition, the status of any affected commitment and any change effective under its terms, immediate coordination action or truthful blocker, affected parties, effective horizon, supporting evidence and uncertainty, and next review or reopen trigger. Notify or coordinate with affected parties through the established relation; this pattern does not invent notification authority or prove receipt.
Choose the review time early enough that a discovered adverse condition can still receive a useful response. When supported durations are additive, subtract their total from the latest useful action time, then allow for uncertainty; when they overlap or vary, use the applicable response model instead. If no useful interval remains, act or return the blocker now rather than schedule a review after the consequence.
OPS.7:4.7 - Return wider policy and specialist questions
Return a shared queue, constraint, capacity or service-design question to OPS.8–OPS.13, and a quality/reliability response to OPS.18. Use applicable clinical, legal, safety or release decisions within their terms. Refer any outstanding decision to the party with the relevant authority.
OPS.7:5 - Archetypal Grounding — Three Aging and Commitment Replays
OPS.7:5.1 - PumpWorks incident and release horizon
Continue the constructed matter in OPS.5:5.1 and OPS.6:5.1. At 09:30, I73 is one hour old from its 08:30 opening, while R42 has awaited its final evidence for 36 hours. I73’s age is lower, but the field representative is available from 10:00 to 11:00 and has confirmed the required permission for observational live verification; losing that contact would prevent the planned verification today. R42’s current promise is an authorized evidenced-release package to the service recipient by 17:00, conditional on the stated safety and field checks. Lab validation alone cannot fulfil it.
The representative needs the decided response before contact closes at 11:00. For this incident, the supplied response estimate is 20 minutes for live verification, 10 for the authorized decision and 10 for communicating its result: 40 minutes in sequence. The latest review that leaves that response possible is 10:20. The incident lead chooses 10:00 to retain 20 minutes of margin for the stated uncertainty. The priority authority gives the incident contact action precedence over the older provider-preparation package; the resource owner retains the active-work limit. This priority leaves R42-T9’s independently permitted 09:40 laboratory start unchanged.
At 09:50 the field representative reports loss of access, with the earliest supported replacement contact at 09:00 next day. The lead acts immediately instead of waiting for 10:00: live verification is blocked, the customer liaison sends a truthful partial-result notice by 10:00, and the service owner checks the consequence for R42. The 10:10 laboratory result still counts for its test, and the captured incident discrepancy remains established.
The incident lead can change diagnostic priority but cannot change the customer’s promise. At 10:05 the service owner, who has that authority, proposes delivery by 10:00 next day, on the supplied replacement-contact reservation, remaining safety decision and one-hour completion-and-return allowance confirmed by their owners. The recipient has not yet agreed: the old 17:00 obligation remains visible as at risk, and the proposed date is labelled a proposal. At 10:20 the authorized recipient explicitly accepts the changed conditional result and date; the service owner records the agreement and sends it to the affected performers. Only then is the commitment revised. A refusal would have left the old obligation and an unresolved authorized service decision, not licensed a local date edit.
The return contains the priority actually applied, partial result and live-access blocker, effective revised promise, conditions still open and next review at 08:30 next day. The owners supply a ten-minute allowance to obtain current contact/permission confirmation and any already-produced safety result, ten minutes to decide and communicate which 09:00 work may start and whether the conditional 10:00 promise remains supportable, and ten minutes of contingency. Thus 08:30 + 10 + 10 + 10 minutes reaches 09:00. This is time to recover and use a qualified result, not an allowance for inventing a safety verdict. If the result or contact remains unavailable at 08:40, return that exact blocker while a service decision is still possible. A missing safety result blocks reliance on the release promise; observational work can continue when its own permission and inputs hold. Lost contact blocks live verification without erasing the completed laboratory result. A newly lost condition reopens the response immediately. P8-P retains its 13:00 reconsideration, and neither agreement nor priority grants field-release or safety authority.
OPS.7:5.2 - Public-hospital waiting and deterioration
One clinical case has a defined waiting age, current observations, possible deterioration evidence, dependencies on clinicians, beds and other resources, a service horizon, affected patient and care participants, and explicit clinical and operating authorities. OPS.7 makes those relations available to the authorized priority and commitment decision.
The qualified clinical service uses its clinical evidence and authority to determine triage and treatment. Use the waiting and deterioration evidence for the operating priority decision and any needed return to the holder of a service commitment. Use a qualified result for a dependent question of queue design, staffing, capacity, consent, privacy, medical safety, statutory permission, treatment efficacy or patient outcome. Refer any consequential gap to the competent source.
OPS.7:5.3 - AI-assisted software issue and service promise
One user issue has an exact age and state, user and service consequence, dependency on tool or model access, current trace and test evidence, integration load, recovery burden, bounded concurrency, and a promised horizon. Assess what further delay would change for the user or service, using the evidence behind any severity score.
The authorized System may revise the issue’s coordination priority or trigger an authorized commitment renegotiation, with an immediate check, integration action, fallback, or stop and next review. Use the evidence and authority for any dependent technical, release or fulfilment claim.
OPS.7:6 - Bias-Annotation
| Bias or pressure | How it distorts temporal decisions | Countermeasure |
|---|---|---|
| age-equals-urgency bias | Elapsed time substitutes for consequence and decision context. | Relate delay to one named risk, commitment, dependency, recovery, or supported use. |
| score reification | A severity or priority number appears to be an objective property. | Recover the comparison basis, intended coordination use, evidence, and authority. |
| deadline authority | A date is treated as permission to release, treat, spend, or bypass a condition. | Keep commitment horizon, priority, and specialist permission separate. |
| queue-rank collapse | Current priority becomes one universal queue position. | Bound the disposition and return queue policy to its owner. |
| commitment-preservation bias | An earlier promise is preserved despite unsupported conditions. | Revalidate parties, content, conditions, horizon, authority, and feasibility evidence. |
| local-to-system overreach | One reprioritization is reported as a service-wide promise or capacity result. | State the local result and return to OPS.13 or the wider owner. |
| intervention-story bias | A change in rate or recovery is attributed to the chosen action without adequate temporal support. | Apply C.27 only to the intervention-sensitive claim and preserve evidence limits. |
OPS.7:7 - Conformance Checklist
- The exact subject or case, qualified state, configuration, and horizon are named.
- For any relevant existing commitment, the account gives parties, content, conditions, horizon, authority, status, and evidence limits.
-
Any
OPS.6result is used as evidence only at the matching configuration and horizon. - State, age, time remaining, rate, trend, and intervention-sensitive temporal claims are distinguished.
-
C.27is used only for an intervention-sensitive rate, rhythm, recovery, inertia, or regime claim. - Urgency names the consequence, commitment, risk, recovery, or supported use that delay can change.
- Priority, queue rank, clinical triage, economic value, permission, and commitment remain distinct.
- The account identifies who can set priority and, for an affected commitment, who can revise its terms. If the required authority is still unknown, the account identifies the decision that must wait.
- The current comparison basis and any useful probe are explicit.
- The result gives the priority decision or blocker, the status of any affected commitment, the immediate coordination action if one is available, affected parties, horizon, evidence and next review.
- Any wider policy, service or specialist question has a usable return to the participant who can answer it.
OPS.7:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| oldest first by nature | Age becomes a universal priority rule. | State the subject, consequence, commitment, comparison basis, and policy owner. |
| urgency score as fact | A representation hides assumptions, evidence, and receiving use. | Reconstruct the decision-relative claim and uncertainty. |
| deadline grants permission | Commitment pressure bypasses clinical, safety, legal, security, or release authority. | Keep horizon, priority, and permission as separate results. |
| local escalation becomes queue policy | One disposition silently reorders every item. | Bound the coordination result and return the queue decision. |
| promise by label | A service target or desired date is treated as an obtaining commitment. | Recover parties, content, conditions, authority, and status. |
| record change becomes stakeholder agreement | A revised field is treated as renegotiation or receipt. | Use the established commitment and communication relations and preserve evidence of acceptance. |
| temporal overanalysis | Ordinary age or rate triggers unnecessary dynamics modelling. | State the event, interval and clock. Use C.27 only when the intervention-sensitive claim is current. |
OPS.7:9 - Consequences
Practitioners can identify the last useful response time. If that time has passed, they can report which response is no longer possible and consider any alternative. They can explain the grounds for retaining or changing priority, what happened to any affected commitment, who held each authority, which parties are affected and when to review the result.
The cost is obtaining the consequence and authority information that one convenient age score omits. Some cases must return to another decision owner before their priority or promise can change; actual fulfilment is observed later.
OPS.7:10 - Rationale
Age is broadly observable, but urgency depends on what delay changes; priority depends on one coordination use; and commitment alteration depends on parties, conditions, and authority. Keeping these relations separate prevents time pressure from becoming unearned permission.
Practitioners can preserve or revise priority for the subject of the operating decision and the terms of an affected commitment without waiting for a complete queue, capacity, or service-design account. Explicit returns keep queue, buffer, constraint, capacity, service-design, whole-service commitment, and specialist questions with their governing patterns or competent participants.
OPS.7:11 - SoTA-Echoing
The question is how a temporal change alters present action and an existing promise. Competent flow practice already compares consequences, not just age. The Open Guide to Kanban, July 2025, prioritization appendix discusses service classes, delay-cost rates, cumulative delay cost and opportunity cost, with cautions about uncertain estimates and reprioritizing started work. Reinertsen’s historical economic-flow treatment and TameFlow’s commitment and signal reasoning supply related mechanisms. OPS adopts that consequential comparison.
For section 5.1, a capable fixed-date or expedite policy can already prefer the younger incident because the field-contact opportunity expires. Both approaches can preserve the ongoing laboratory work rather than interrupt it. The residual OPS contribution is the connection between unlike clocks, the remaining whole response, and the distinct authority to change the promise. A local severity or queue decision cannot make the proposed next-day date effective. Sections 4.3–4.6 keep the 17:00 obligation visible until agreement and select a review early enough for action; the case shows the adverse change before that review and the actual agreement afterward.
If the incumbent service policy already records the response window, the affected recipients and effective agreement, use it unchanged. The additional burden otherwise is estimating the relevant response, obtaining the missing authorized decision and maintaining the applicable promise. Those calls and confirmations consume time too; include them in feasibility and prefer a direct rule when it settles the matter. No precise score compensates for absent safety, clinical or legal authority.
FPF C.27.TA qualifies event, interval and currentness claims; C.27 applies only to a consequential intervention-sensitive temporal claim. DEMO’s commitment distinctions help inspect parties and agreement without assigning their authority. OPS.13 supplies service-level support and response construction. Reopen when consequence, required response, parties or agreement conditions change, or an incumbent achieves the same action and truthful promise account at lower total effort.
OPS.7:12 - Relations
- Use the progressed state or unmet condition from
OPS.6when it applies to the configuration and horizon and bears on priority, a commitment or the grounds for retaining either. Establish authority for changing priority or changing a promise separately. C.27.TAgoverns temporal aspect, window, cadence, and currentness.C.27governs intervention-sensitive rate, rhythm, recovery, inertia, or regime claims; neither supplies Operations priority or authority.C.11governs comparison only when several admissible live dispositions require choice.A.10governs evidence reliance.OPS.5retains admission and explicit-start conditions. A current priority relation neither admits demand nor establishes start permission or Work.OPS.8–OPS.11retain queue, buffer, constraint, capacity, variability, and interacting-structure decisions.OPS.13retains the credible whole-service commitment account.OPS.18retains operating quality and reliability questions.- Clinical triage, consent, medical safety, law, privacy, security, finance, product assurance, release, provider authority, and other specialist results remain with their direct owners.
- Enter
OPS.7directly when you need a decision about timing and priority or an affected commitment. Use the evidence and authority already available, or identify what is missing. Reapply the method when conditions change. A particular episode may require neitherOPS.5norOPS.6.
OPS.7:End
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
| Force | Practical tension |
|---|---|
| less started Work and reliable replenishment | A small started population can reduce congestion, but too little eligible supply can leave an important resource idle. |
| local autonomy and joins | A team can finish its own contribution while the receiving activity still waits for the rest of its kit. |
| small batches and setup burden | Smaller transfers can expose problems sooner; frequent setups or transactions can consume scarce time. |
| pooling and differentiated service | Sharing eligible demand can reduce idle capacity while changing failure exposure, priority, tail delay or fairness. |
| simple rules and protected conditions | A 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.
| Arrangement | What its policy controls or protects | Useful quantity |
|---|---|---|
| ready-work buffer before a selected service | service continuity during replenishment delay | eligible service load, related to the resource’s operating calendar |
| inventory reserve | availability of specified material under replenishment and consumption uncertainty | usable quantity by material, location and condition |
| capacity reserve | response or recovery when load or availability changes | usable resource time with the necessary capability and access |
| limit on started items | congestion and exposure from concurrent unfinished matters | items 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
| Bias | Consequence | Countermeasure |
|---|---|---|
| board-boundary bias | Waiting disappears when an item leaves a local column. | Retain the operation’s population and waiting origin. |
| zero-buffer ideal | Protection is removed together with avoidable congestion. | State the disturbance and shortage consequence before changing the amount. |
| complete-kit absolutism | Every 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 pressure | More starts create incomplete kits and downstream waiting. | Inspect the accepted result and receiver-ready inputs. |
| pooling optimism | Mean efficiency hides class-specific or failure-related loss. | Compare the actual service criterion and resource assumptions. |
OPS.8:7 - Conformance Checklist
- Can the reader identify the operating result, service boundary, eligible queue members and wider unfinished population?
- Does readiness describe inputs for the next service without requiring that service’s future output?
- Does every selected buffer have a protective purpose, units, replenishment action and shortage consequence?
- For a proposed change, does the comparison with the current arrangement use total waiting and accepted results?
- For any protection that needs sizing, is the amount justified for the stated scenario or distributional claim, or is the missing sizing condition clear?
- 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-pattern | Why it fails | Repair |
|---|---|---|
| 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 line | Serious alternative, trade-off and pattern change | Source 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
| Force | Practical tension |
|---|---|
| Earlier release and correction capacity | Starting sooner can advance new work but occupy the resource needed when an earlier result returns. |
| Simple counts and unequal demands | One freed place is easy to recognize; the returning and incoming jobs may require very different resources and times. |
| Protection and useful idle time | Holding capacity can preserve a deadline; excessive protection postpones work without improving the required service. |
| Feedback timing and decisions | Waiting can reveal whether a return is needed, but that information may arrive too late to protect the result. |
| Local pace and the receiving result | A 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 rule | What permits new work | What to resolve about returns |
|---|---|---|
| Completion at a selected constrained activity triggers replenishment | That 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 loop | The 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 norms | The 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 start | The 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 one | Specialist’s next work | Completion of Y |
|---|---|---|
| X accepted | Start Y at 1 and finish at 5. | 5 |
| X needs correction | Correct 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
| Mistake | Consequence | Repair |
|---|---|---|
| Treating a local completion as the end of resource responsibility | A new long job displaces an earlier correction. | Retain the remaining and contingent resource demands after that event. |
| Holding every place until remote final acceptance | Unrelated 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 again | Artificial overload blocks usable capacity. | Replace the matching allowance when the return becomes known. |
| Calling a mean return load protective | A 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 returns | A 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
| Force | Practical tension |
|---|---|
| Useful preparation and availability | Auxiliary work can improve later service while obstructing a call that arrives now. |
| Short fragments and retained progress | Smaller units can be easier to stop, but repeated saving, switching and reconstruction can consume their value. |
| Nominal priority and actual release | A priority rule can demand a return while the required person, machine state or memory remains unavailable. |
| Development and present capability | Learning may expand future options; the protected work still needs capability available today. |
| One return and sustained service | A 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 arrangement | What must be established |
|---|---|
| Finish before a known protected start | The unit, cleanup and restoration fit the available calendars before that start. |
| Pause and resume later | A permissible stopping point can be reached; the needed resources are released; sufficient state remains for resumption. |
| Abandon and later restart | Abandonment is permissible, resources can be recovered in time, and lost work and any remaining effects are included in the choice. |
| Transfer the auxiliary work | A 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 operation | Minutes |
|---|---|
| Detect the call | 1 |
| Reach a stopping point and leave the needed resumption note | 1 |
| Move to the protected workstation | 1 |
| Recover its current situation and prepare the next action | 2 |
| Total, with these operations serial and no additional waiting | 5 |
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
| Mistake | What fails | Repair |
|---|---|---|
| Filling every idle interval | Protection disappears when the call arrives. | Recover the protected service and fit the whole return before promising the interval. |
| Treating priority as interruptibility | An 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 calendars | A needed setter or handover participant is unavailable. | Place return operations with their required resources. |
| Treating an easy-to-stop lesson as capability gained | An operating fit substitutes for practice and transfer. | Retain HCD’s learning and capability question separately. |
| Counting only the first successful return | Repeated 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
| Force | Practical tension |
|---|---|
| urgent treatment and adequate diagnosis | Delay can be costly, but the wrong treatment consumes resources and can move congestion elsewhere. |
| one focal constraint and distributed delay | Focusing effort helps, while several short waits or alternating regimes can defeat one-resource explanations. |
| local measures and accepted results | Touch time, busy time and queue length can change without changing what the operation delivers. |
| useful probes and protected conditions | A probe can discriminate explanations only while preserving the relevant professional, acceptance and comparison conditions. |
| learning and migration | A 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.
| Element | Bounded result |
|---|---|
| observed loss | twelve open hours without an eligible job; accepted-release shortfall still requires its own event and acceptance account |
| candidate explanation | prerequisite delivery misses usable rig windows |
| serious rival | eligible demand exceeds usable rig time in the relevant deadline windows |
| discriminating next observation | timestamp package eligibility, usable rig slots, starts, results, returns and final acceptance for the same release population |
| bounded probe | where 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 decision | do 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.
| Arrangement | First accepted result | Fifth accepted result | Preparation burden outside the service window |
|---|---|---|---|
| Current 3/5/2 | 10 | 30 | none |
| Upstream fixture 2/5/2 | 9 | 29 | two qualified staff-hours, with a reversible fixture change |
| Reassigned assistance 3/4/4 | 11 | 27 | three 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
| Bias | How it misdirects treatment | Countermeasure |
|---|---|---|
| busy-resource attribution | High utilization becomes the causal explanation. | Relate usable capacity and timing to the accepted-result shortfall. |
| queue-length attribution | Visible 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 bias | Automation, 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 confidence | Coincident changes are attributed to the intervention. | Preserve comparison conditions and account for interference and confounding. |
| permanent-bottleneck identity | Attention remains on a resource after conditions change. | Remeasure the current limiting relation and accepted result. |
OPS.9:7 - Conformance Checklist
- Are the accepted result and shortfall defined for the relevant population and horizon?
- Which limiting mechanisms do the observations distinguish, and which remain open?
- Where rival explanations matter to the required conclusion or treatment, are they resolved or is the remaining question identifiable?
- Does the selected bound, replay, probe or specialist analysis support the claim actually made?
- For a selected treatment, does it act on that mechanism and include consequential interactions and transition costs?
- 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-pattern | Failure | Repair |
|---|---|---|
| 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 line | Serious alternative, trade-off and pattern change | Source 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
Part VI — Qualify Capacity and Coordinate Operating Structures
OPS.10 - Qualify Operating Capacity Under Variability
Status: Stable
OPS.10:0 - Use This When
Use this Method when demand, a proposed commitment, a queue policy or a resource change requires an answer about what the operation can support. Average utilization may look acceptable even though a deadline, skill requirement or protected service class cannot be met.
The first useful result is a capacity-and-service comparison for the actual demand, resource arrangement and horizon. It states usable resource time, required load, relevant variation, feasible alternatives, supported service consequences and uncertainty. It can establish a feasible option, a bound that settles the question, or a specific missing input.
Use an adequate existing result. When calculation is needed, start with a simple load/time bound and add the analysis the service question requires. Use OPS.9 when the limiting mechanism is itself unresolved. Use OPS.5 for an individual admission decision under an adequate capacity basis. A clinical staffing rule, engineering capability, labor condition or financial authorization is supplied by its own qualified practice.
When the needed calculation is missing, OPS.10.1 - Construct and Compare Operating Capacity Models develops finite, mean or probabilistic service consequences from the operating conditions. OPS.10.2 - Construct and Revise a Feasible Deadline Schedule develops resource sequencing, calendar placement and conditional time reserve for a finite delivery. Reuse an adequate calculation without repeating these constructions.
OPS.10:1 - Problem frame
Capacity is useful only relative to a service, resource capability, operating conditions and time window. Nominal resource hours, accessible hours, hours usable by the required skill or configuration, completed service visits and accepted operating results are different quantities.
Variability matters even when totals fit. Demand can arrive together, service can take longer, a provider can withdraw access, a qualified person can be absent, or failed work can return. The operation may have enough total hours and still miss a deadline because the needed hours occur at the wrong time or require incompatible resources.
OPS.10:2 - Problem
Average load divided by nominal capacity can conceal unusable time, setup, recovery, skill restrictions and rework. A favorable mean can also conceal long waits or losses for a protected service class.
The opposite response applies a sophisticated queueing model to every decision. That creates calculation effort and apparent precision without improving a bounded choice that a transparent schedule or stress scenario could already settle.
OPS.10:3 - Forces
| Force | Practical tension |
|---|---|
| utilization and timely service | Keeping a resource busy can consume the slack needed to absorb a burst or recover. |
| simple estimates and changing conditions | A mean estimate is cheap; its validity can disappear when mix, timing or availability changes. |
| pooling and capability | Shared time can help only where the resource can perform the required service under its conditions. |
| capacity and reversibility | Extra capacity can be costly or slow to obtain; scheduling and batch changes can be cheaper but have their own consequences. |
| explicit reserve and apparent waste | Unused capacity can look inefficient while protecting a specified response or recovery scenario. |
OPS.10:4 - Solution
OPS.10:4.1 - State the demand and service question
Name the accepted result, population, demand profile, horizon and service criterion. Distinguish a service-visit queue from the operation’s final accepted-result population. State whether the question concerns a hard deadline for known jobs, a mean delay, a probability of completion, a protected response class or a bounded overload scenario.
Recover the initial unfinished work and its remaining service requirements. Preserve the customer’s waiting origin when local release times differ. If a target is an existing commitment, keep its parties and authority; any change to the promise depends on its terms and the parties authorized to change it.
OPS.10:4.2 - Recover usable time and required load
For each necessary resource, identify capability, access, calendar, location, configuration and skill conditions. Deduct known unusable intervals only where they actually remove the needed service. Keep uncertainty about outages or absence separate from known deductions.
Translate each demand class into resource-time requirements under the supplied Method. Include normal setup, joint-resource occupancy, expected or scenario-specific rework, recovery and other consequential load. State which effects are already included in a service-time estimate so they are not counted again as lost capacity.
Use compatible units. Two hours of a specialist and two hours of a general resource are not four hours of interchangeable service. A test attempt and an accepted release are not two interchangeable outputs.
The first calculation is a necessary bound: for the work to fit, the load it requires from each resource must fit that resource’s usable time in the window. Passing that bound is not enough when precedence, arrival timing, simultaneous resources or non-interchangeable classes can prevent a schedule.
OPS.10:4.3 - Choose the smallest adequate service analysis
| Receiving question | Appropriate first analysis | What it can establish |
|---|---|---|
| Can these known jobs fit the actual windows? | A finite schedule using arrival, readiness, service, calendar and precedence data, or a necessary time/resource bound. | A feasible assignment; impossibility only when a necessary bound or complete valid search excludes the deadline. |
| What is a useful mean steady-state screen? | A queueing approximation whose population, service, routing, stability and dependence assumptions fit. | A qualified mean estimate, not a tail guarantee. |
| What happens under a specified disruption or burst? | A trace replay or explicit stress schedule, with actual policy and resources. | A conditional scenario result, not its probability of occurrence. |
| Does a changing or coupled operation meet a probabilistic service target? | A stochastic model or simulation of the relevant inputs and policy, retaining parameter and model uncertainty. | A conditional service probability; reliance on actual service additionally needs the corresponding input and model basis. |
For a single continuously available compatible server operating first-come, first-served, a finite calculation can be very small. For each job in arrival order, start is the later of its arrival and the previous finish; finish is start plus service time; wait is start minus arrival. This assumes no other setup, interruption, precedence or resource requirement. Add those conditions to the schedule when they apply.
For a finite overload or changing regime, use a model that represents the initial state and the relevant time window. Correlated bursts, feedback, blocking, priorities and skill classes may require a different model. If specialist analysis is needed, supply the operating question and the conditions that analysis must cover.
OPS.10:4.4 - Test variability and the proposed change
When deciding whether to change the arrangement, compare the current arrangement with the proposed alternatives where they differ, such as demand/admission changes, timing, usable access, skill coverage, batch/setup changes, pooling or segregation, reserve, recovery and capacity acquisition.
Keep the result and service criterion fixed. Inspect arrival patterns as well as total demand, service and recovery variation as well as average duration, and common-cause losses as well as independent failures. Test plausible adverse conditions that could change the choice or the service claim supporting it.
A batching change may reduce setup time while delaying the first result or defect feedback. A pooled resource may improve a mean while changing a tail or protected class. A reserve must name the disturbance and capability it covers. A proposed schedule must not claim improvement by moving waiting outside the measured start boundary.
Use C.11.CRC for the finite comparison of consequences, resource cost, transition, reversibility and affected options. Keep a recommendation, provision of the resource, authority to use it and the resulting performance separate.
OPS.10:4.5 - State exactly what the result supports
Name each result as a hard bound, a feasible schedule under stated inputs, a stress scenario, an estimated mean, a percentile/probability forecast or an unresolved question. Attach the relevant uncertainty, data window and model limitations. Historical coverage of a target is not automatically its future probability.
For a consistently defined population with stable compatible averages, Little’s relation L = λW connects mean in-system count, effective flow rate and mean time. Returns, rework, abandonment and finite-window boundary terms need correct population accounting. The arrival/exit rate of service visits is not necessarily the rate of accepted final results. The relation is useful for consistency; it neither supplies a delay distribution nor makes a protective buffer sufficient.
If the available basis supports only a load bound, return the bound. If the question also requires a service result the bound cannot establish, identify the missing information. A missing distribution does not prevent a known infeasibility result or a useful conditional stress comparison.
OPS.10:4.6 - Return the operating decision and refresh basis
Return demand and result units, horizon, usable capacity and load assumptions, the selected analysis, the consequences of any alternatives compared and the supported option, bound or unresolved question, provision/decision authority, residual demand and reopening conditions.
OPS.5 can use this basis for admission. OPS.8 can use it for release and protection. Use OPS.7 when capacity evidence bears on the feasibility or continued support of an existing commitment. Use OPS.13, or an appropriate method from the responsible service practice, to establish a wider credible service offer; the local capacity result alone does not supply it.
Reopen when mix, arrivals, access, capability, absence, failure/rework, resource coupling or the service criterion changes. Retain observations of actual performance so the next decision can test, rather than silently inherit, the previous model.
OPS.10:5 - Archetypal Grounding
OPS.10:5.1 - PumpWorks: fit, reserve and a deferred package
In this constructed extension, four eligible test packages each require two consecutive rig-hours, including their normal setup, under the current estimate. In the next eight-hour horizon, this operation has access during hours 0–6; hours 6–8 are currently reserved for another use. This gives six continuous usable rig-hours. Permission and required configuration for the tests are current; release authority and SafetyQuestion-S19 remain separate.
The initial load is eight rig-hours, so all four packages cannot fit the six usable hours even before uncertain recovery. More ready packages or a larger buffer cannot remove that deficit.
For comparison, assume one adverse scenario: one of the planned packages needs a single consecutive two-hour repeat, after which it passes. The failed attempt is identified on completion and its repeat can run next under the current test conditions. This is a supplied scenario, not an estimated failure probability. The resource owner can offer hours 6–8 to this operation through a separate access and cost decision that accounts for the displaced use.
| Option | Usable rig-hours | Planned packages | Explicit reserve | Accepted test packages without repeat | Accepted packages in the one-repeat scenario |
|---|---|---|---|---|---|
| current access, plan three | 6 | 3 | 0 | 3 | 2, with unfinished load returned |
| extra access, plan three | 8 | 3 | 2 | 3 | 3 |
| extra access, plan four | 8 | 4 | 0 | 4 | 3, with unfinished load returned |
Both eight-hour options deliver at least three accepted packages in either stated scenario. Planning three and reserving two hours completes every admitted package in both. Planning four can deliver four without a repeat and leaves one unfinished if a repeat is needed. The six-hour option can fall to two. Compare the cost of extra access, the displaced commitment and the consequences of admitting work that may return unfinished.
If the decision requires every admitted package to finish in either scenario and the resource owner grants the extra access, admit three, reserve two hours for the repeat and return the fourth package to OPS.5. Send any affected existing commitment to OPS.7. If extra access is unavailable, use the six-hour result.
More than one repeat, a longer repeat, changed configuration or another loss reopens the comparison. A passed test package still does not settle the release decision for R42.
OPS.10:5.2 - Equal total load, different waiting
One continuously available server processes four one-hour jobs. There is no setup, failure, other resource or initial backlog.
| Scenario | Arrival times in hours | Start times | Waiting times |
|---|---|---|---|
| one burst | 0, 0, 0, 0 | 0, 1, 2, 3 | 0, 1, 2, 3 |
| one job per hour | 0, 1, 2, 3 | 0, 1, 2, 3 | 0, 0, 0, 0 |
Both consume four server-hours and finish the last job at hour 4. If the criterion is completion within two hours of arrival, two of four jobs meet it in the burst scenario and all four in the second. The difference follows from the stated arrival scenarios.
Measure arrival-to-completion time from the actual arrival. If a job waits for admission, starting its clock at admission omits that wait.
OPS.10:5.3 - Nominal beds and qualified capacity
A hospital’s bed count is not the capacity for every care requirement. The receiving question may depend on the supplied clinical class, staffing qualification, equipment, cleaning readiness, access and synchronized availability.
Use the applicable clinical and staffing results to compare arrangements and state the resource-time or scenario result. If a required qualification is missing, identify which service capacity remains unresolved and the evidence or decision needed to establish it.
OPS.10:6 - Bias-Annotation
| Bias | Consequence | Countermeasure |
|---|---|---|
| nominal-capacity bias | Calendar presence substitutes for usable capability and access. | Recover the relevant service and resource conditions. |
| average sufficiency | Equal totals are treated as equal service. | Inspect arrival timing, variation and the actual service criterion. |
| double-counted loss | A failure is included in service time and again deducted from capacity. | State each estimate’s contents and count the effect once. |
| precise-number confidence | A sophisticated model hides poor premises. | Match model scope to the question and qualify the result kind. |
| reserve-as-waste bias | Recovery capacity is removed to increase utilization. | Compare the named disturbance and service consequence. |
OPS.10:7 - Conformance Checklist
- Are demand, service visits, accepted results and the waiting origin distinct where they affect the calculation?
- Does usable capacity include the actual capability, access, calendar and joint-resource conditions?
- Does required load include relevant setup, recovery and rework without double counting?
- Does the chosen analysis fit the finite/steady, deterministic/stochastic and dependence conditions?
- Are the service criterion, uncertainty and adverse scenarios explicit where they affect the capacity claim or the option comparison?
- Does the result distinguish its supported claim from resource provision, authority and a service promise?
- Can the receiving admission, queue or commitment decision use the result and identify its reopening condition?
The calculation is recognizable when another practitioner can reproduce its inputs and outputs. Assurance requires the empirical and professional basis appropriate to the claimed bound, model or forecast.
OPS.10:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Total demand is below total hours, so the deadline is safe. | Timing, precedence or incompatible capability can prevent a schedule. | Recover the actual resource windows and a feasible witness. |
| Use mean utilization as a service guarantee. | The wait distribution and relevant tail remain unknown. | State the intended service criterion and select a suitable analysis. |
| Treat a scenario as a probability. | No occurrence model or calibrated data supplies that probability. | Label the conditional result and return the missing probabilistic basis. |
| Treat every person or machine-hour as interchangeable. | Capability, configuration and access differ. | Compare usable service capacity by the relevant class. |
| Count repeats as additional delivered results. | Attempts and accepted outputs have different identities. | Keep load and result populations separate. |
| Buy capacity before establishing the limiting mechanism. | The added resource may not change completion. | Use OPS.9 where the treatment basis is unresolved. |
OPS.10:9 - Consequences
The operation can distinguish known infeasibility, conditional feasibility and supported service uncertainty. Admission and protection decisions can use reserve deliberately rather than treating all unused time as waste.
The cost is maintaining resource and workload premises that can change. A modest schedule can be enough for a small finite decision; a consequential probabilistic promise may need substantial specialist modeling and evidence.
OPS.10:10 - Rationale
Usable capacity, workload and service are related but different. A load bound can show that a required resource has too little usable time. If total hours fit, their timing and compatibility may still prevent delivery. A schedule answers whether that time can be used as needed. A service forecast adds a claim about uncertain outcomes. Keeping these questions separate prevents a cheap answer to one from being mistaken for an answer to all three.
OPS.10:11 - SoTA-Echoing
| Practice question and selected line | Serious alternative, trade-off and pattern change | Source roles, limits and reopen condition |
|---|---|---|
| Can average population and flow data establish timely service? Adopt compatible population accounting; reject using a mean identity as a tail guarantee. | Mean utilization cannot distinguish the two arrival scenarios in 5.2. A mean-flow identity can recover different mean times from compatible population data, but does not establish their two-hour completion fractions. Sections 4.1, 4.3 and 4.5 retain the service criterion and result kind. | Little (2011) relates compatible averages of population, flow and time. Individual deadline performance requires additional timing information. The finite example provides the decision-changing contrast at comparable calculation effort. Reopen when the population, boundary, returns or required service claim changes. |
| What model should handle dependent arrivals and feedback? Adapt model selection to the actual temporal and network dependence. | A simple independent-input mean approximation is easier but can omit consequential burst structure. Sections 4.3–4.5 call for a suitable specialist model when the omitted dependence could affect the choice or the grounds for the requested performance estimate. | Whitt and You (2022) is a bounded model candidate: a single-class open single-server network with Markovian routing, nonrenewal arrivals and feedback, estimating mean steady-state performance through dispersion functions. It does not supply every service tail or transient solution. Reopen for nonmatching routing, classes, regime or service criterion. |
| Should the response be more capacity, pooling, or a different batch policy? Adapt finite comparison of setup, waiting, reliability and service effects. | Capacity additions can be lumpy; smaller batches and pooling can have different protected consequences. Sections 4.2–4.4 and 5.1 retain those costs and scenarios when deciding which arrangement supports the required service. | Reinertsen (2009), batch-size trade-offs, supplies a mechanism candidate. Andradóttir et al. (2017) and Cao et al. (2021) supply conditional pooling counterexamples. Their studied conditions are not transferable staffing or rig prescriptions. Reopen when capability, failures, batching or the service criterion changes. |
OPS.10:12 - Relations
OPS.3 and OPS.4 supply the matching subjects, resource relations and qualified current observations. OPS.8 supplies the release/queue/buffer policy whose consequences are analyzed. OPS.9 supplies a supported limiting mechanism when choosing a capacity treatment depends on it. OPS.11 handles consequential cross-structure constraints.
OPS.5 consumes an adequate capacity basis for admission; OPS.6 continues permitted Work without treating the plan as performance; OPS.7 uses changed feasibility for an existing bounded commitment. OPS.13 and OPS.14 use the capacity basis with their own service and financial inputs to address the wider commitment and operating-consequence decisions.
Current FPF C.16, C.27.TA/C.27, C.11.CRC and C.11 govern measurement, temporal interpretation, finite comparison and choice. Field specialists supply the capability, labor, engineering, clinical, safety and financial premises for their respective uses.
OPS.10:End
OPS.10.1 - Construct and Compare Operating Capacity Models
Type: Method pattern Status: Stable Normativity: Normative
OPS.10.1:1 - Problem frame
Use this when you know the service question and operating arrangement, but the calculation needed to answer it is missing or misleading. A faster machine produces longer queues. Two staffing plans have the same average hours but different completion risks. A workload controller changes an aggregate smoothly while the customer is waiting for one complete order.
Model how the available resources produce the required result, then calculate the service result under the stated conditions and for any proposed changes. Keep the arrival, service, resource and completion meanings attached to the quantities. The result can be a finite schedule, an obstruction, a mean estimate, a conditional probability or a useful bound.
First useful move. Select one result and its time criterion. Recover who or what must serve it, what is already waiting and whether anything prevents the next service from starting. A resource-time shortfall may settle the question immediately.
The reader needs to interpret rates, durations and elementary probability for the branches used. A practitioner can obtain a specialist calculation while retaining the operating assumptions and result interpretation. Use an adequate existing model directly; reconstruct it when a changed resource, arrival process or question invalidates a needed relation. OPS.10 selects the wider capacity/service decision. This method develops the model used in that decision.
OPS.10.1:2 - Problem
Dividing mean demand by nominal capacity suppresses the arrangement that makes service possible. It can hide shared attention, interrupted availability, burst arrivals and visits that fail to produce a final result. A mean waiting-time formula can then be used to promise a deadline it never calculated.
At the other extreme, a full simulation can consume effort while leaving a simpler decisive bound unused. The difficulty is to model enough of the service process to answer the question and identify which assumption or relation needs revision when the model is insufficient.
OPS.10.1:3 - Forces
| Force | Practical tension |
|---|---|
| Amount and timing | Enough total resource time may exist, yet be unavailable when a job needs it. |
| Detail and useful consequence | A richer model can retain a lost dependency, but also cost more to build and maintain. |
| Average performance and individual service | A mean can compare recurring load without determining a completion probability or hard deadline. |
| Local change and shared work | Speeding one activity can move waiting or consume a resource needed elsewhere. |
OPS.10.1:4 - Solution
Model how work arrives, uses resources and reaches completion. For a choice between alternatives, calculate the answer to the same service question for each. If an assumption fails, revise it and the results that depend on it. Enter at a later step when its inputs are already adequate.
OPS.10.1:4.1 - Define the completion question and its clock
Choose the operating population, arrival event, completion event and horizon. Keep an order, its visits and its accepted result distinct. For each alternative, measure customer waiting from the same event unless the question concerns that starting event.
State the output needed: all listed jobs finished by a date; a mean residence time in a continuing regime; a fraction completed within a duration; a probability under a specified model; or protection against a stated disturbance. Recover the initial unfinished work and its remaining requirements. A system started empty is a different input from a busy operation observed halfway through a shift.
For example, “the two jobs need four hours on average” does not yet answer “with what probability will both be complete by hour four?” Section 5.2 constructs both answers from the same service assumptions.
OPS.10.1:4.2 - Construct usable service and a first load bound
Use the operating model to identify the resources needed by each activity, including simultaneous needs. Recover usable calendars, capabilities, access, setup, interruption, restart and return rules. An unattended machine interval may occupy the machine while releasing its operator.
For a finite horizon, sum the required remaining occupancy separately for each resource. Compare it with the time in which that resource can perform this work. If the requirement exceeds that time, the proposed completion is impossible under those inputs. If it fits, timing, precedence or resource compatibility may still prevent a schedule.
For recurring demand, a useful first load expression is:
resource demand per unit time =
sum over arriving classes of
(class arrival rate * expected resource time used by one arrival)
Expected resource time includes the modeled visits, setups and recovery attributable to that arrival. A return may require another visit without producing another delivered order. If return behavior depends on congestion or policy, recover that dependence before reusing the old expectation.
Divide this demand by the usable resource time supplied per unit time to obtain an offered-load ratio. A ratio above one means that offered work exceeds this capacity. The observed fraction of time busy remains at most one. Both measures can be useful, but they answer different questions.
Define service time for the chosen server. Include an interruption in effective service when the model treats it as extending that server’s service; otherwise represent the unavailable interval separately. Count its loss once. Waiting for another team or for permission is not automatically occupancy of this server. A batch’s shared machine time is also different from the sum of its parts’ elapsed times. OPS.11.1 and OPS.15.1 supply these resource and event constructions.
OPS.10.1:4.3 - Build the finite or changing-regime account
For a continuously available single server, first-come service, known arrivals and service durations, construct each start and finish in arrival order:
start[i] = max(arrival[i], finish[i-1])
finish[i] = start[i] + service[i]
wait[i] = start[i] - arrival[i]
The initial finish represents the server’s remaining occupied time; it is zero for an empty system available at zero. This recurrence obtains the earliest schedule under that fixed policy. It does not choose a better job order.
When a job needs an uninterrupted usable interval, replace the proposed start by the first interval that fits its duration and required resources. If work can pause, account for the work completed before each interruption and the permitted restart, including lost setup or recovery. Construct precedence and resource choices explicitly when several activities interact. OPS.10.2 develops this finite schedule, including calendar windows and conditional time reserve. A feasible placement shows that the schedule fits the modeled conditions. Distinguish a search that finds no schedule from a complete valid exclusion of every permitted placement.
For a changing regime, begin with the actual initial state and advance arrivals, completions, failures, returns and control actions using their event rules. A model of continuous aggregate quantities can use fewer variables when amounts and rates are the required outputs: write its accumulation balance and the rule that determines outflow. Retain any capacity, nonnegativity and delay constraints of that rule. Section 5.3 shows why a proportional outflow and a constant service rate give different completion accounts.
A feedback policy can be part of either an event or continuous model. Its requested capacity change must correspond to an obtainable operating change, such as an available shift, machine setting or additional resource.
OPS.10.1:4.4 - Construct a continuing-regime mean when that is the question
First establish the modeled regime: arrival process, service order, number of servers, availability, initial transients, return behavior and relevant dependence. Long-run parameters do not describe an arbitrary finite overload merely because their units fit.
For one continuously available first-come server, consider independent, identically distributed interarrival intervals and independent, identically distributed service times, with the two sequences independent. Let lambda be the arrival rate, E[S] the mean service duration and rho = lambda * E[S]. With finite second moments and rho < 1, a useful two-moment approximation is:
mean queue wait ≈ ((ca² + cs²) / 2) * rho / (1-rho) * E[S]
mean residence ≈ mean queue wait + E[S]
Here ca² is interarrival variance divided by squared mean interarrival time; cs² is service-time variance divided by squared mean service time. The factor rho/(1-rho) retains the sharp rise near saturation. Both arrival and service variation matter.
Use this as a qualified mean calculation under those premises. In the Poisson-arrival case, the displayed mean wait equals the established single-server result for a general independent service distribution with finite second moment. Section 5.1 uses that special case. Neither use supplies a wait percentile.
Temporal dependence can defeat a description consisting of two moments. Count arrivals in windows at time scales relevant to the queue; examine whether their variance relative to mean changes with window length. Retain that dependence in a richer queue model or in simulated arrival paths when it matters to the required service result or the choice that depends on it. Dispersion-based queueing analysis supplies one such mean-performance alternative; it retains its own stationarity and service assumptions.
Do not substitute the one-server formula after pooling servers, adding priorities, introducing blocking or changing the dependence. Reconstruct the model of service. A deterministic arrival every hour and a one-hour uninterrupted service can operate continuously without a queue; its feasible timing is not invalidated by a stochastic formula singular at rho = 1.
OPS.10.1:4.5 - Obtain the needed probability or protective bound
For a finite probability question, specify the joint uncertain inputs, initial state and operating policy. When a policy adapts during execution, base each choice on information available at that time. Separate schedules chosen after each complete outcome is known do not establish one policy that can be executed. State the service event, such as both named orders completing by hour four. Derive its probability directly from the joint model when possible. Alternatively, apply the event rules to enumerated outcomes and sum their probabilities, or to sampled paths and estimate the probability with its sampling uncertainty. MMP.7, MMP.13 and CMP.9 supply observation, inference and sampling methods when those contributions are needed.
Preserve dependence between arrivals, service durations, outages and returns. Equal marginal means or distributions do not make different joint models equivalent. Section 5.2 changes only service dependence and changes the probability while preserving the mean completion time.
A scenario without probabilities supports a conditional consequence. A family of bounded disturbances can support a protective bound if the response is shown to work for every disturbance in that family. One successful replay supplies only its case. A mean replenishment time multiplied by a consumption rate gives no such worst-case or probability statement by itself.
Include the starting backlog and horizon for a transient service question. Use a continuing-regime mean only for the mean question it answers. For an empirical claim, interpret source coverage and input/model uncertainty as well as calculation or sampling error. Obtain another observation when it could improve the required service estimate or the decision enough to justify its cost.
OPS.10.1:4.6 - Compare operating changes and return their consequences
Change the modeled mechanism of each alternative: service requirement, resource access, setup, interruption, release, route or policy. Recalculate the affected consequence while preserving unaffected inputs and the common service question.
Compare the relevant results separately: completion, waiting, resource demand, cost, burden and recovery. Use the existing finite-comparison or portfolio methods when these consequences compete. A faster nominal operation can lose to a more predictable one on mean residence, yet remain preferable at another arrival rate or cost.
Distinguish waiting moved before admission from service made faster by reduced interference. The first can improve an internal measure without earlier delivery; the second needs the changed service mechanism in the model. Return the result to admission, release/protection or commitments together with the conditions that can change it. A modeled resource does not establish that it has been provided or authorized.
Stop with the answer the decision needs: a usable alternative, demonstrated shortfall, sufficient bound or an identified unresolved relation. Reopen the affected calculation when arrivals, mix, service, access, dependence or the requested service criterion changes.
OPS.10.1:5 - Archetypal Grounding
OPS.10.1:5.1 - A slower machine gives a better mean, within its capacity
Jobs arrive as a Poisson process at one job per three hours. A continuously available first-come machine serves one job at a time; its service durations are independent across jobs and of arrivals. Service includes all job-specific recovery. There is no other setup, loss, resource or return. These are constructed alternatives.
Machine A takes one hour with probability 0.9 and eleven hours with probability 0.1. Its mean service is two hours, its variance is nine squared hours and cs² = 2.25. Machine B always takes 2.2 hours, so its service variance is zero. Poisson arrivals give ca² = 1.
| Result | A | B |
|---|---|---|
| Mean service, hours | 2 | 2.2 |
| Offered-load ratio | 2/3 | 11/15 |
| Mean queue wait, hours | 6.5 | 3.025 |
| Mean arrival-to-completion time, hours | 8.5 | 5.225 |
For example, A’s mean wait is ((1+2.25)/2) * ((2/3)/(1/3)) * 2 = 6.5. The special-case mean relation applies to these stated service laws. B has the larger mean service duration and higher load ratio, yet the smaller mean residence. Its absence of service variation changes the queue consequence.
If the decision needs a mean residence below six hours, B meets that modeled criterion and A does not. Cost and actual availability still affect the operating choice.
Change the arrival rate to 0.48 jobs per hour. A’s mean service rate is 0.5 and B’s is about 0.455. A has load ratio 0.96, while B has 1.056. The former comparison cannot justify B for that continuing arrival regime. Review the admission or capacity arrangement at the increased demand. The steady-mean formula used here requires a load ratio below one.
OPS.10.1:5.2 - Four hours on average, with a missed-deadline risk
Two independent jobs are ready at time zero. One server processes them in fixed order without interruption. Each service takes one or three hours with probability one half, independently of the other service. Both jobs must be complete by hour four.
| Service durations, hours | Last completion, hour | Probability | Both complete by four? |
|---|---|---|---|
| 1, 1 | 2 | 1/4 | Yes |
| 1, 3 | 4 | 1/4 | Yes |
| 3, 1 | 4 | 1/4 | Yes |
| 3, 3 | 6 | 1/4 | No |
Mean last completion is four hours; the probability of meeting the deadline is three quarters. Replacing both durations by their mean of two hours would produce a single on-time schedule and discard that risk.
An additional independent server capable of the same work would allow both to start at zero and finish by three in every listed case. That is a conditional alternative; obtaining it is another operating action. Without it, a deadline of six covers all cases in this bounded model.
Now keep both marginal service distributions but make their durations equal, perhaps because a shared job condition affects both. The only outcomes are (1,1) and (3,3), each with probability one half. Mean last completion remains four; deadline probability falls to one half. The changed dependence reopens the probability result without changing the two means.
OPS.10.1:5.3 - An aggregate curve and a completed job
A controller represents remaining workload q in job-equivalents, starting at one with no new arrivals. Its assumed output rate is k*q, with k = 1 per hour. The balance gives q(t) = exp(-t): after one hour, about 0.368 job-equivalents remain. This model can support an aggregate regulation question where that outflow law fits.
A different operating account says one indivisible job takes exactly one uninterrupted hour on the available resource. Its completion event occurs at hour one. A constant-rate fluid balance, stopped at zero, also gives q(t) = max(1-t,0) in job-equivalents, but its intermediate fractions do not make the actual job partially delivered.
Even the exponential curve permits another interpretation under different premises. For one exponentially distributed service duration with mean one hour, it is the expected number of unfinished jobs; completion by one hour then has probability about 0.632. It is not a deterministic promise.
The practitioner chooses the account by the receiving question and the operating service law. For the fixed one-hour deadline, use the completion event. For aggregate feedback, establish the outflow relation and how a commanded rate change can be realized. A new capacity setting without a corresponding operating mechanism leaves the proposed intervention unsupported.
OPS.10.1:6 - Bias-Annotation
Nominal speed attracts attention because it is easy to compare. Section 5.1 keeps recovery variation and queue consequences visible. A smooth trajectory can be equally persuasive: section 5.3 recovers what the curve represents before interpreting it as a completed result.
A familiar formula can survive after its regime disappears. Reconstruct the changed arrival, service or dependence relation and recompute the service quantity under the applicable model.
OPS.10.1:7 - Conformance Checklist
- Are the completion event, clock and service criterion clear before the calculation?
- Are usable resources and each job’s demands represented, with shared occupancy and losses counted once?
- Does a finite schedule preserve the initial backlog, policy, calendars and precedence it uses?
- Does a continuing-regime calculation retain its arrival, service, dependence and stability premises?
- Is a probability derived from the joint uncertain model, and a protective bound from its stated disturbance family?
- Does the comparison distinguish a changed service mechanism from a changed measurement boundary?
- Can admission, protection or commitment use the result and identify what would reopen it?
Recognition and assurance. A reproducible conditional calculation is a model result. For reliance on actual service, establish the resource availability and input assumptions on which the service claim or decision depends, at the assurance level the work requires. Missing information may leave a probability unknown while a resource bound still settles the decision.
OPS.10.1:8 - Common Anti-Patterns and How to Avoid Them
| Tempting move | Consequence | Repair |
|---|---|---|
| Replace the utilization factor by the busy fraction alone. | The rise in waiting near saturation disappears from the mean calculation. | Retain rho/(1-rho) with the selected model’s premises. |
| Put mean durations into one schedule and report its deadline as assured. | Different uncertain paths collapse into an unrepresentative outcome. | Calculate the required predicate over the joint paths or derive an applicable bound. |
| Deduct interruption time after already including it in effective service. | The same capacity loss is counted twice. | Choose a consistent service/availability representation. |
| Apply the old one-server model after pooling resources or changing service dependence. | The mathematical account no longer describes the proposal. | Reconstruct the affected service mechanism before comparing its result. |
OPS.10.1:9 - Consequences
The practitioner can obtain a capacity comparison from the smallest sufficient construction and see which operating change would alter its conclusion. Mean, scenario, deadline and probability questions remain connected without substituting one answer for another.
The cost grows when dependence, calendars or uncertain service matter. A bounded decision may finish with an elementary obstruction; a probability-sensitive decision may need richer modeling and input support.
OPS.10.1:10 - Architectural Rationale
To compare capacity choices, explain how available resources perform activities under a policy and produce the required results. Observations, estimates or stipulated case inputs supply the quantities; the mathematical model relates them, and solving it gives the consequences under its premises. Their correspondence to the operating work determines what a calculation answers.
The construction therefore separates what the resources must do, how their service evolves and which result is requested. The same arrangement can need a finite deadline model today and a continuing mean model for another decision. Cases 5.1–5.3 show changes of variation, dependence and interpretation that a single scalar capacity value cannot retain.
Common model construction, inference and comparison remain in their supplying Methods. Use the operating arrangement and evidence to select the service laws and assumptions that the capacity calculation requires.
OPS.10.1:11 - SoTA-Echoing
For a quick mean comparison of one continuing first-come server, adopt the service-process and two-moment construction in Hopp and Spearman, Factory Physics, third edition, §8.6.5, equations 8.25–8.26. A utilization-only calculation is cheaper but loses the action-changing service variation in section 5.1. Sections 4.2 and 4.4 retain both variance contributions, the saturation factor and their premises. The formula is a mature approximation with a useful exact Poisson-arrival special case. Its low calculation cost is accepted for the mean question; a changed operating regime or a required deadline probability reopens the choice.
For dependent traffic, adapt the richer description developed by Whitt and You (2022), §§2.1–2.2: count dispersion over time retains variability a fixed two-moment description can lose. This costs additional traffic characterization. Section 4.4 selects that effort when the lost dependence matters. Their robust-queueing construction approximates mean performance in a steady regime under its stationarity and independent-service assumptions. Although the derivation uses a worst-case construction, the returned result estimates a mean; it does not guarantee an upper bound on individual waits. Changed dependence, routing or the requested result reopens that use.
For changing aggregate workload, Oliveira, Sagawa and Mušič (2025), §§3–4, supplies a current continuous feedback-control alternative. Adapt its explicit accumulation and capacity-response account for a suitable aggregate question; reject treating continuous versus discrete representation as the test for whether feedback is possible. Sections 4.3 and 5.3 retain the outflow law, completion interpretation and obtainable capacity change. An event model requires individual timing detail and is preferable when that detail decides the deadline. The paper’s simulated control response does not establish physical access or every individual completion. Reopen when a changed service law or required completion event invalidates the chosen correspondence.
The finite probability and changed-dependence case is a direct construction from its stated premises. It avoids a simulation project for four enumerable outcomes. Use a larger probabilistic construction when the joint inputs or the risk question being answered require it.
OPS.10.1:12 - Relations
OPS.10 selects the capacity/service decision. OPS.10.2 constructs the detailed deadline schedule and its conditional reserve. OPS.11.1 supplies the shared-resource and completion model; OPS.15.1 constructs the operating quantities. OPS.9 diagnoses an unresolved limiting mechanism. OPS.5, OPS.8 and OPS.13 use capacity results in admission, protection and commitments; OPS.19 reconciles simultaneous operating work.
MMP.10 supplies constraint construction, MMP.11 the response formulation and MMP.7 and MMP.13 the observation and inference contributions. CMP.9 supplies a randomized estimator when enumeration is insufficient. C.29 qualifies returning a mathematical result to its operating subject; C.16 preserves quantity meaning, and C.11/C.11.CRC supply common comparison and decision-use discipline.
OPS.10.1:End
OPS.10.2 - Construct and Revise a Feasible Deadline Schedule
Type: Method pattern Status: Stable Normativity: Normative
OPS.10.2:1 - Problem frame
Use this when particular work must deliver particular results by particular times, but a list of tasks and estimated durations does not establish whether the work fits. Two ready tasks compete for one specialist. A test needs an uninterrupted window. A delayed input changes which remaining operation can now postpone delivery.
Determine whether the required operations can fit their time and resource conditions. A feasible schedule shows how to meet the deadline. A sufficient bound or complete search can show that no such schedule exists. If neither result is available, state what is still unresolved. For a feasible plan, determine which delays it can absorb. Reconsider affected results when a condition changes.
First useful move. Name the recipient’s completion event and deadline. Trace the remaining operations to that event, including required handovers and acceptance. Identify the performers, equipment and calendar windows shared by the operations. OPS.11.1 supplies that operating account; OPS.15.1 supplies event and clock interpretation.
Practical gain. The planner can state what should start when, which reservations matter, how much postponement is still possible under the chosen arrangement, and what change could recover a threatened commitment.
This method addresses finite delivery timing within the broader capacity and service question of OPS.10. Its subject is the proposed schedule, not the performed work or a new customer promise. Use an adequate existing schedule directly when its conditions still answer the question. Use OPS.10’s demand and capacity analysis when the question instead concerns sustained throughput or a distribution of future delays.
The elementary cases need time intervals, arithmetic and a dependency diagram or equivalent list. A large search may need a scheduling specialist. For known jobs and durations, a deterministic calculation can answer the finite scheduling question.
OPS.10.2:2 - Problem
A dependency diagram can allow work to proceed in parallel while the same person must perform both branches. A resource total can fit a day while a continuous operation fits none of its open windows. A priority rule can produce a late plan even though another order meets the deadline.
A second error arises after a plan has been obtained. Its apparent spare time is spent independently by several participants, or a once-critical sequence continues to determine priorities after resource access has changed. The practitioner needs a construction that connects the proposed times, their feasibility, the reserve being used and the conditions requiring revision.
OPS.10.2:3 - Forces
| Force | Tension |
|---|---|
| Early results and shared resources | Advancing one result can postpone another. |
| Compact model and consequential detail | Whole-operation durations are convenient, but attendance phases or calendar gaps can decide feasibility. |
| Fast plan and strong conclusion | A useful candidate may be easy to obtain; optimality or impossibility needs an additional argument. |
| Deferred starts and protection | Waiting can reduce aging or premature work while consuming opportunities to recover delay. |
| Stable coordination and changed facts | Keeping appointments has value, but preserving an invalid order can lose the delivery. |
OPS.10.2:4 - Solution
Recover the recipient’s result and deadline and the operations needed to deliver it. Identify what enables each operation, which resources it occupies and the usable calendar windows. Seek a feasible schedule or a sufficient obstruction. A failed placement leaves other allowed schedules open unless a bound or complete search rules them out. For a feasible plan, calculate the start windows and delivery reserve needed to compare early work, postponement or protection. When a condition changes, retain completed facts, reconsider the affected dependencies and resource competition, and return the consequences to whoever can set priorities or authorize release.
OPS.10.2:4.1 - Recover the delivery question and remaining work
State the result that must be available, its deadline and its waiting origin. An internal completion can precede transport, approval or receiving acceptance. Include those operations when the promise needs them.
Separate hard requirements from preferences. “Meet all three dates” asks for feasibility. “Finish the last order as early as possible” minimizes the last completion. “Obtain the first result sooner” can prefer a different order. If competing recipients cannot all receive their earliest possible result, OPS.7 supplies the priority and commitment choice.
For each remaining operation, recover its readiness event, required predecessors, duration or bounded scenario, eligible resources, and whether it can be interrupted. Include setups, transfers and known return work when they consume relevant time. Retain completed operations and work already under way as facts; estimate only their remaining requirements.
Qualify the duration before calculating a schedule. Recover the execution conditions and whether the quoted time includes waiting or deliberate protection against overruns. A protected task commitment is not, by itself, a measure of the time the work takes. Keep work and required waiting in the timing model, and identify protection already included before reserving more time for the same delays. If that split is unknown, obtain a supported estimate or compare explicit duration scenarios; cutting every quotation by the same percentage does not recover the missing basis.
Keep the finite work list at the detail the decision needs. If a task requires an operator only during loading, recover that phase without decomposing every machine movement. If an uncertain duration affects feasibility, the scope of the service claim or a choice between plans, compare supported bounds or obtain that particular input. A full event history is unnecessary when the supplied conditions already settle the schedule.
OPS.10.2:4.2 - Construct precedence, occupation and calendar conditions
A precedence relation states which event must occur before another operation may begin. For a continuous operation i of duration p_i, finish f_i equals start s_i plus p_i. A finish-to-start relation from i to j with required delay l requires s_j >= f_i + l. At a join, every required predecessor must satisfy its relation. An actual partial handover can use an earlier event, provided the downstream work can use that partial result.
Resource sharing adds a different condition. Two operations requiring the same exclusive resource cannot occupy it at the same time. Their order is a choice unless the operation already fixes it. For a pool, check how many eligible members are needed simultaneously; one free but unqualified person does not supply the required capability.
Recover each occupation separately. A machine may hold an order for three hours while its operator is needed only in the first hour. Represent the machine interval and that operator interval with their common start. Apply each resource’s capacity and calendar to its own intervals. Use half-open intervals, including the start and excluding the finish, when a resource can pass immediately to the next operation.
Distinguish three calendar conditions that require different placements:
- A continuous occupation must fit wholly inside an available window.
- Work that may pause can accumulate processing across open windows, with any restart cost included.
- A machine may continue through an operator’s absence when that phase needs no attendance.
A rule allowing an operation to start during working hours does not establish that its later occupied hours are available. Where several resources are needed together, find a window in which their required occupations are jointly possible.
Check that the precedence relations can be satisfied. A finish-to-start cycle with positive total required duration and delay is an obstruction. When the work actually revisits a station, represent the later visit as a later operation rather than requiring one operation to precede itself.
MMP.10 supplies the joint formulation. Keep the operational reason for a condition recoverable: actual precedence, chosen resource order, calendar closure, admission policy or deadline. A chosen order can be reconsidered without pretending the technological route changed.
OPS.10.2:4.3 - Place the work and distinguish the resulting conclusions
For a small case, start with operations whose required predecessors have been placed. Choose an eligible operation, find its earliest jointly available placement after readiness, reserve the required intervals, and continue. Several reservations may be made within one long machine operation when its attendance phases allow other work.
At a resource conflict, compare the competing orders. A near deadline or a long downstream continuation can guide the first attempt. Preserve alternatives when that first attempt fails or gives an inadequate result. Inserting work into a gap, leaving a resource temporarily idle, or changing an uncommitted order can permit a schedule that a simple dispatch rule misses.
Once the relevant orders are fixed, calculate the earliest times consistent with them. With continuous availability and finish-to-start relations, each start is the maximum of its readiness and predecessor finishes plus their required intervening delays. Chosen resource-order relations also contribute predecessors. For partial attendance, connect the occupied phases, not the finish of an unrelated unattended phase. With calendars, move each proposed occupation to the next jointly permitted window and propagate the resulting finish.
Check the complete candidate against every required operation, precedence, occupation, calendar and completion event. A feasible assignment is a witness that the modeled work fits; the participants must still have the stated access and capability.
Use cheap necessary bounds before a larger search. A required dependency chain cannot finish faster than its ordered work permits. A resource cannot supply more mandatory occupation than its available capacity in the required window. A continuous operation cannot use several disjoint short windows as one long window. Passing these bounds does not construct a schedule.
Return the actual strength of the result:
| Obtained result | Supported conclusion |
|---|---|
| Complete feasible schedule meeting the dates | Those dates are attainable under the stated conditions. |
| Feasible completion C and lower bound L on the earliest possible completion | The optimum lies between L and C. Equality establishes an earliest completion. |
| Necessary condition incompatible with the deadline, or a complete valid search excluding every permitted schedule | The deadline is impossible within that modeled arrangement. |
| A failed priority rule, restricted sequence or interrupted search | That attempt found no satisfactory plan; other permitted schedules remain unresolved. |
CMP.4 supplies justified search when the operational choices remain numerous. CMP.5 supplies relaxations and bounds. Use an adequate existing bound or schedule. If a specialist must develop one, supply the relevant resource and calendar conditions and the conclusion to establish.
Stop when a suitable plan or sufficient obstruction answers the decision. Continue optimizing when a reachable improvement in the schedule or the bound justifies the additional work.
OPS.10.2:4.4 - Derive time reserve and conditional criticality
First state the event against which reserve is measured. If the proposed final completion is C and its deadline is D, D-C is the plan’s final margin. A negative value shows that this plan misses the deadline; it does not by itself exclude another plan.
For a precedence network with fixed durations, continuous calendars and no binding resource contention, calculate early starts forward and latest starts backward. Start the backward pass from the selected final time T, retaining any earlier hard intermediate deadlines. For each successor, subtract the required intervening delay from that successor’s latest start. The earliest of those bounds and any deadline on the operation gives its latest finish; subtract its duration to obtain its latest start. Latest start minus early start is its total float relative to those targets. Free float is the delay that leaves the successors’ early starts unchanged, including their required intervening delays.
When only the final event governs this calculation, setting T to the earliest final completion identifies zero-float paths controlling that completion. An earlier intermediate deadline can instead give zero float to work protecting that intermediate event; identify which event the result concerns. Using a later final deadline adds delivery margin where other commitments permit it, so an operation on the longest precedence path can have positive deadline float. Several longest paths can exist. Serial operations may draw on the same margin, so their individual floats are not independent allowances to add together.
With shared resources, retain the selected allocations and orders when making the timing calculation. For whole-operation exclusive occupations, add the chosen resource-order relations to the precedence network; its timing is conditional on those orders. For partial occupations or calendars, use the corresponding phase and window constraints. A different allowed order or calendar can change the controlling sequence.
To assess a proposed postponement, hold the stated commitments fixed, delay that start, and refit the affected work. Identify the latest feasible placement or the set of feasible start windows that still meets the protected event. Calendar gaps can make intermediate start times infeasible even when a later window exists. A backward arithmetic pass that ignores those gaps supplies no usable postponement permission.
Call a sequence critical for a stated plan, resource order and target event. Test a claimed critical operation by varying its duration or availability and recalculating that event. A throughput bottleneck limits sustained flow under a workload. A different condition can govern the first result by a deadline. Use OPS.9 to diagnose the constraint on the result in question.
OPS.10.2:4.5 - Choose early work, deferred starts and protection
Compare start policies inside the feasible windows. Starting earlier can reveal problems and retain recovery time. Deferring can avoid aging, premature expenditure or work invalidated by a later input. Retain the recipient’s original waiting boundary in either comparison.
When protection is needed, name the event and disturbance to be absorbed. Choose an internal target earlier than the commitment, or reserve time before a consequential join. Determine its amount from the delay scenario, supported bound or risk model that matters to the decision. A final margin is available time; calling it a buffer adds a policy for preserving and using it.
When several operations protect the same delivery, compare keeping their individual protection with placing protection before the common delivery or a feeding join. Revise the operation estimates and protection together, preserving the required work, intermediate obligations and execution conditions. Size the shared protection for the joint delays it must absorb: delays that can occur together cannot be treated as mutually exclusive. Check the new plan and the participants’ release and handover rules; moving reserve into one place does not make it available before every earlier commitment. Keep or restore local protection where the joint arrangement cannot protect that earlier result.
For known deterministic conditions, the feasible schedule can be enough. To protect against a stated extra hour of review, add that hour to the appropriate operation and recompute the plan. This answers the scenario without inventing its probability. A service-probability claim needs the corresponding duration and dependence model; OPS.10.1 supplies that construction.
After inserting protection, recheck resource and calendar feasibility. Moving a feeding operation earlier can take another task’s reservation. Keeping two hours before final delivery does not make those hours usable before an earlier calendar closure. Do not allocate the same margin to several independent promises without checking their combined delay.
Return the selected target times, reserved intervals and response to reserve consumption to OPS.8 for release and protection. OPS.7 uses the delivery consequences for priorities; use OPS.14 when the start policy or its economic justification depends on a financial comparison.
OPS.10.2:4.6 - Reconstruct the affected remainder after a change
At the current time, retain actual starts, completions and ongoing occupations. Replace the changed duration, readiness, access window, required operation or commitment. Do not restart completed work or shorten an uninterrupted operation merely to recover the former finish date.
Follow the changed operation through both its successors and the resources it shares. A task outside its precedence descendants can still lose a resource window. Include resulting admission changes and downstream joins; widen the affected set until its remaining boundary conditions are unchanged.
Try retaining unaffected reservations and the useful parts of the former plan. Refit the affected work under those commitments. If that restricted repair fails, identify which still-changeable reservation or resource order could matter and compare a broader rearrangement with its coordination cost. Failure while preserving the old order excludes only that restricted repair.
Recompute completion times, feasible postponement windows and protected reserve. Compare them with the same recipient events and deadlines. Report what that comparison establishes, such as a changed start or allocation, reserve consumed, an obtainable operating remedy, a commitment needing reconsideration, or an unresolved scheduling choice. Retain unaffected model and calculation results whose premises still hold.
OPS.10.2:5 - Archetypal Grounding
OPS.10.2:5.1 - A deliverable with a join and shared deadline margin
A report needs preparation P, taking four hours, and evidence extraction E, taking two. Different people can perform them concurrently from time zero. Review V takes three hours after both finish; release R takes one hour after review. These resources are independently available, durations are known, and release completes delivery. The deadline is hour ten.
| Operation | Predecessors | Earliest interval | Latest start for delivery at 10 | Total float |
|---|---|---|---|---|
| P | None | 0-4 | 2 | 2 |
| E | None | 0-2 | 4 | 4 |
| V | P and E | 4-7 | 6 | 2 |
| R | V | 7-8 | 9 | 2 |
The precedence path P-V-R takes eight hours and controls earliest delivery. E has two hours of free float before its delay moves V’s early start. Starting E at hour two preserves delivery at eight and may avoid producing an input earlier than useful. Starting it at four instead gives V at 6-9 and R at 9-10, consuming all final margin.
P, V and R each have two hours of total float against ten, but they share those hours. Delaying P by two moves V to six and R to nine; another two-hour delay of V would miss the deadline.
To preserve one hour before the external deadline, use an internal delivery target of nine. The latest starts become P at one, E at three, V at five and R at eight. They jointly give one feasible deferred plan with the intended final reserve.
Return to execution of the earliest-start plan. At hour two, preparation is found to need three further hours instead of two. E is already complete. Continue P to five, then V at 5-8 and R at 8-9. The new final margin is one hour. The changed estimate requires replanning the remaining preparation and its successors; E’s completed result remains available.
OPS.10.2:5.2 - A failed short-task priority is not an impossible deadline
Two jobs are ready at zero. U needs three hours of one specialist followed by seven hours of unattended equipment work. V needs two hours of that specialist followed by one unattended hour. The equipment is different for the two jobs, all resources are continuously available, and both results are required by hour ten.
Doing the shorter specialist task first gives V at 0-2, its equipment at 2-3, U at 2-5 and its equipment at 5-12. That plan misses the deadline.
Doing U first gives specialist intervals U at 0-3 and V at 3-5. U’s equipment runs at 3-10 and V’s at 5-6. Both dates are met. U’s own required chain takes ten hours, so the plan also attains the lower bound for the last completion.
In the first plan, the chosen resource relation V-before-U makes V part of the sequence controlling the final finish. In the second plan, V can finish well before U. That criticality was a consequence of the selected order. Five hours of specialist demand alone revealed neither the successful order nor the ten-hour completion.
OPS.10.2:5.3 - Shared attendance still permits machine overlap
Five orders arrive at zero. Each needs A for two hours and then B for three, with order 1-5 on each station. Each station has one continuously available machine; there are no setups, returns or other work. B completion makes an order ready for its customer. No operation is interrupted. Admit the first two at zero and the next order immediately when a B completion frees one of the two places.
With independent station resources, earliest A intervals are 0-2, 2-4, 5-7, 8-10 and 11-13. B finishes at 5, 8, 11, 14 and 17.
Now both stations use one operator. A requires continuous attendance; B requires attendance only in its first hour and holds its machine for all three hours. The old A intervals conflict with B attendance. Recovering the phases yields this revised plan:
| Order | Admission | A with operator | B with operator | B unattended | Completion |
|---|---|---|---|---|---|
| 1 | 0 | 0-2 | 2-3 | 3-5 | 5 |
| 2 | 0 | 3-5 | 5-6 | 6-8 | 8 |
| 3 | 5 | 6-8 | 8-9 | 9-11 | 11 |
| 4 | 8 | 9-11 | 11-12 | 12-14 | 14 |
| 5 | 11 | 12-14 | 14-15 | 15-17 | 17 |
At hour two, start B1 before A2; then place A2 inside B1’s unattended phase. Repeating that choice keeps B working continuously. The operator’s intervals do not overlap, and no more than two orders are admitted and unfinished.
B cannot begin before hour two and must process five orders sequentially for three hours each. Every completion therefore satisfies f_Bi >= 2+3i; the plan attains all five bounds. The shared operator changes starts at A without delaying any recipient result.
Customer times average eleven hours. Internal times are 5, 8, 6, 6 and 6 hours, averaging 6.2; the remaining average 4.8 hours occurs before admission. These quantities retain their different event boundaries.
OPS.10.2:5.4 - A calendar gap makes final margin unusable for a test
A maintenance test becomes ready at hour two. It needs a rig and an engineer together for three uninterrupted hours. A separate analyst then needs one hour to issue the acceptance result and is available throughout. The rig is available from two to ten; the engineer from zero to five and from six to ten. Acceptance is due at eight.
The test fits at 2-5 and acceptance work at 5-6. The final margin is two hours, but the test cannot be postponed by one hour: 3-6 crosses the engineer’s absence. The next complete test window starts at six, giving acceptance at ten. Within the original deadline, the margin can postpone the analyst’s work, not the test.
Before execution, the engineer’s first window is shortened to end at four. Common availability before the latest possible test finish at seven is 2-4 and 6-7: three hours in total, but no continuous three-hour interval. This excludes acceptance by eight. The earliest remaining test is 6-9 followed by acceptance at 9-10.
The obstruction identifies a useful remedy to investigate: restore attendance through five or obtain another qualified continuous window ending by seven. Merely reporting three available engineer-hours, or silently allowing the test to pause, does not answer the stated operation.
OPS.10.2:6 - Bias-Annotation
Finite deterministic schedules favor work whose remaining operations and durations can be specified. Discovery work or frequent unplanned returns can require scenarios, rolling revision or a different service model. Keep that uncertainty visible without withholding a useful known-date bound.
The examples assume that named people and machines are interchangeable only where stated. Human fatigue, location, recovery and skill conditions can change available occupation. Recover them when they alter the proposed plan and check that the reserved participant or resource can perform the work.
OPS.10.2:7 - Conformance Checklist
- The completion event, waiting origin, deadlines and any optimization preference are explicit.
- Required operations, precedence and partial resource occupations describe the work being planned.
- Resource sharing, capability, calendars and interruption conditions are jointly respected.
- A claimed feasible result includes an executable assignment of the required work.
- An impossibility or optimality conclusion has the necessary bound or complete-search basis.
- Float, feasible postponement windows and final margin retain their target and resource-order conditions.
- Protection has a named event, burden and delay basis, and the protected plan remains feasible.
- Revision follows shared-resource competition as well as precedence and preserves completed facts.
OPS.10.2:8 - Common Anti-Patterns and How to Avoid Them
| Mistake | Consequence | Repair |
|---|---|---|
| Schedule each department’s copy of one person independently | The plan double-books the actual person. | Constrain that person’s combined occupied intervals. |
| Keep the first priority rule after it misses a date | A poor sequence is presented as an impossible commitment. | Reconsider permitted orders or obtain an impossibility argument. |
| Spend each task’s float independently | Several tasks consume the same delivery margin. | Recompute their joint postponement. |
| Treat the original critical sequence as permanent | New resource competition or delay is missed. | Recalculate conditional criticality from the changed arrangement. |
| Deduct closed hours while allowing a continuous task to span them | A nominal working-time calculation produces an impossible operation. | Place the complete required occupation in a permitted window. |
| Add a buffer without rescheduling its feeders | Earlier work competes with existing reservations. | Check the full protected assignment. |
OPS.10.2:9 - Consequences
The planner can give the recipient a feasible schedule, the condition that excludes the deadline or the scheduling question still open. Conditional reserve also gives release and priority decisions something concrete to use.
Detailed scheduling costs inquiry and maintenance, and optimization may consume more effort than its possible benefit. A feasible plan remains dependent on the supplied work and access conditions. Reusing unaffected assignments and reopening consequential changes limits that burden without treating the first plan as permanent.
OPS.10.2:10 - Architectural Rationale
Precedence, resource competition and calendars enter together because each can exclude a superficially plausible plan. The precedence-only calculation remains a useful reduced case and lower bound when resources are relaxed. It becomes the full answer only when the omitted conditions do not invalidate its assignment.
Before relying on a time reserve, check that the schedule containing it meets the protected requirement. Reserve is then interpreted against a specific event and selected choices, allowing early and deferred policies to be compared.
The operating construction supplies phase occupations, appointments, available windows, receiving deadlines and the changed remainder. MMP.10 and CMP provide general formulation and search. Keeping criticality conditional also lets a planner revise a local sequence without mistaking it for the sustained-flow constraint of the whole service.
OPS.10.2:11 - SoTA-Echoing
For the question “Can this finite work meet its dates with shared resources?”, adopt explicit interval feasibility and sequence choices. The OR-Tools Job Shop account, variables and constraints supplies precedence and exclusive-resource alternatives; its CP-SAT result definitions distinguish a feasible answer, a proven optimum, proven infeasibility and an unresolved stop. Adapt these constructions in :4.2-4.3 to operating attendance phases and recipient deadlines. A precedence-only forward pass is cheaper and sufficient when resources do not bind. In :5.2 it cannot choose the specialist order, so explicit resource choices earn their added effort. Reconsider the formulation or search method when problem size or new operating constraints make its cost or representation inadequate.
For calendar feasibility, adopt the explicit distinction between elapsed interval and working duration in IBM’s Scheduling Tutorial, chapter 4. Its example permits suspension during days off and explains separate restrictions on starts, ends and occupied extent. Adapt :4.2 and :4.4 to choose the rule from the operation: :5.4 requires a whole uninterrupted occupation. Combining open hours would answer a different permitted-work question. The extra interval check is small and decides the example. Establish whether this test may pause from its operating conditions. Reopen when interruption, attendance or calendar rules change.
Goldratt, Critical Chain (1997), chapters 16–17, is a historical construction of moving protection from individual task estimates to project and feeding buffers, together with changed execution rules. Adopt the distinction between work estimates and deliberately placed protection in :4.1 and :4.5. Its halving example assumes already protected estimates; it does not establish a universal conversion of a task quotation into a duration or a completion probability.
For a known schedule or a named delay scenario, compare an explicit feasible plan with tested reserve against fixed critical-chain and percentage-buffer prescriptions. Herroelen and Leus, On the Merits and Pitfalls of Critical Chain Scheduling, PMI conference paper (2000), sections on critical sequences, buffers and computational experiments, supplies historical counterexample and experimental evidence. Adapt its attention to resource-dependent sequences and schedule revision; reject treating an initially selected chain or a fixed percentage as sufficient protection. This changes :4.4-4.6: preserve useful reservations, compare the delay actually being protected, and recheck resource feasibility after buffer placement. The cost is a more explicit comparison and possible coordination changes. The paper’s old software comparisons and experimental percentages are not present-day performance claims. Reopen when an applicable protection policy meets the same delivery and coordination requirements with better supported burden or outcomes; probabilistic protection requires its own uncertainty basis.
OPS.10.2:12 - Relations
OPS.10 selects the deadline or service question. OPS.10.1 constructs the capacity, mean or probability account when that question requires it. OPS.11.1 supplies the operating arrangement and resource identities; OPS.15.1 supplies event-defined time and occupancy quantities.
OPS.7 uses changed delivery consequences for priorities and commitments. OPS.8 uses feasible release times and protection; OPS.9 diagnoses what limits the stated result, including throughput or completion by a particular deadline. OPS.14 contributes financial consequences when the timing decision or the grounds for it depend on those financial consequences.
MMP.10 supplies the constraint formulation and its interpretation. CMP.4 supplies search with justified exclusions and CMP.5 supplies relaxation and bound reasoning when needed. C.29 returns the calculated schedule to its operating meaning; B.5.MPC coordinates changed subject premises, mathematics and computation. A.22.CGUS helps recover enabled alternatives before a sequence is fixed.
OPS.10.2:End
OPS.11 - Coordinate Interacting Operating Structures
Status: Stable
OPS.11:0 - Use This When
Use this Method when a proposed operating change depends on or affects another arrangement: material processing and order transactions, test work and release evidence, resource access and service commitments, or observation and supervisory decisions. Typical symptoms are a feasible local plan that cannot be completed in practice, a faster resource followed by more waiting elsewhere, or incompatible decisions by people responsible for different parts of the operation.
The first result identifies the couplings needed for the operating question, the feasible alternatives and their consequences, any decisions needed from other holders, and what would call for reconsideration. It can be a supported decision to keep the present arrangement, a coordinated change, a proposal or a precise missing input. Start from the operating question or proposed change.
Use OPS.8 for a queue-policy question that does not require wider coordination, OPS.9 for an unresolved constraint diagnosis, and OPS.10 for a capacity/service calculation. Product or organization redesign belongs to the corresponding engineering practice when that is the object being changed.
OPS.11:1 - Problem frame
An operation depends on several actual structures. Its resource participation, material transformation, case and commitment relations, information production/use, financial settlement and decisions may be described in different views. Those structures overlap through particular subjects and relations; the views need not be isomorphic.
Coordinate the change across the selected operating structures. Use their descriptions to trace the actual relations and establish who can decide each part.
OPS.11:2 - Problem
A local plan can omit a necessary coupling. Product is made but goods cannot be issued without documents. Tests complete but the evidence does not apply to the release configuration. Capacity exists but access is not granted in the required window. A resource-saving change transfers cost, risk or burden to another participant.
Start with the smallest set of actual couplings that can affect the proposed action or the grounds for relying on it. An extensive network description can add work without improving either answer.
OPS.11:3 - Forces
| Force | Practical tension |
|---|---|
| local clarity and cross-structure effects | A narrow view makes one decision easy while hiding a prerequisite or consequence elsewhere. |
| end-to-end coordination and independent authority | The result depends on several decisions, but their authority does not merge. |
| unlike quantities and comparison | Material, time, money, risk and human burden can all matter without having one valid scalar measure. |
| model detail and useful action | More represented relations can increase effort without improving the current choice. |
| stable agreements and changing conditions | A coordinated plan can become infeasible after access, evidence, demand or commitment changes. |
OPS.11:4 - Solution
OPS.11:4.1 - Start from the proposed operating change
Name the operating result, current arrangement, proposed change and horizon. State which consequence would make the change useful or unacceptable. Reuse the current OPS.1–OPS.4 account and a matching OPS.8–OPS.10 result where available.
Select affected Systems and participants by the consequences of the change. A supplier, customer, operator or neighboring service can matter without appearing inside the local department boundary.
If one direct pattern already settles the decision and its conclusion and conditions do not depend on any further cross-structure relation, use that result and stop.
OPS.11:4.2 - Identify the structures needed for this question
For each selected structure, recover the actual constituents, obtaining relations, applied constraints and use. Say what the current view shows and which material features it omits.
Use A.22 for the general structural question. Use E.18 for one transformation-flow structure and E.18.2 for a mathematical description when that lens is useful. Select an E.18.NET network only when at least two transformation-flow structures are independently identified and obtaining cross-flow relations connect their positions under the applicable constraints and use frame.
A branching process, several views of one flow, and several independently identified flows are different cases. Financial or decision relations need not be reclassified as a transformation flow to be relevant. If a required relation or identity cannot be recovered, retain the proposed description and name the missing basis.
OPS.11:4.3 - Recover the couplings that matter to the decision
For each coupling, state what depends on what, through which relation, under what condition and timing. Keep subject correspondence separate from production, supply, permission, evidence support, commitment or causal influence.
A useful working statement is: “This shipment can use this product only after these required documents are available”; “this test result applies to this configuration”; or “this provider grant permits this resource use during this interval.” Name the basis on which the receiving work can rely. Where a decision is required, identify its holder.
Distinguish an unsupported relation from evidence that it does not hold. For an action requiring permission, check any applicable authorization already in force. If permission remains unestablished, hold the dependent action and state what is known: the request may be unmade, pending or refused. A positive relation claim also needs the endpoints, scope and timing its use depends on.
Follow only the couplings that can affect the current decision or the conditions that justify it. If another step is unaffected, leave its details with its own account rather than reconstructing it here.
OPS.11:4.4 - Compare coordinated alternatives
Trace the finite change through the selected couplings. Compare the current arrangement with feasible alternatives, preserving the operating-result unit, horizon, acceptance conditions and protected consequences.
Include resource demand, service effects, financial timing, recovery, human burden and other consequences when they can affect the choice or its justification. Use applicable financial results or obtain the particular quantity and assumptions needed; a generic “value” label cannot stand in for cash, cost, obligation or benefit. Do not add unlike quantities into one score without an applicable comparison rule.
Check that the proposed decisions can coexist. A new release limit can overload a shared acceptance activity; a batch change can delay the information needed for another decision; an earlier delivery can require funding or access that has not been supplied. Use OPS.10 for the relevant load/service question and OPS.9 when the claimed limiting mechanism is still uncertain.
When the operating model itself needs to be built or reconciled, use OPS.11.1 to connect activities, shared resources, branch joins and completion at the required scales. Reuse an adequate model when the needed couplings are already represented.
Keep modeling assumptions and evidence limits visible. A simulation estimates a consequence for one arrangement or compares several under its assumptions. To rely on the result in operation, establish the relevant correspondence of relations and effects.
OPS.11:4.5 - Obtain or return the coordinated decisions
Name which operating policies can change within existing authority, which decisions must be obtained from other holders, and what remains held until an unresolved result is supplied. Distinguish an agreed coordinated plan, a proposed plan awaiting decisions, and the observed implementation.
Return the smallest actionable account: the supported disposition or remaining alternatives, operative couplings, affected decision-makers, conditions and sequence needed for compatibility, protected consequences, unresolved inputs and next review. Use the existing operating account where it can carry that meaning.
A coordination result can be a partial agreement plus an exact missing return.
OPS.11:4.6 - Observe the consequences and reopen the affected part
After authorized implementation, inspect the accepted result and the affected coupling assumptions. Reopen the relevant decision when a provider changes access, evidence applies to another configuration, an acceptance condition changes, a resource becomes unavailable or an affected party’s commitment changes.
When observation, actuation, supervision or feedback bears on the operating choice or its grounds, recover those relations and their delays through the current FPF control and temporal patterns.
An organization-design, capability-realization or product/service-engineering change returns to its owning practice. Keep a bounded operating adjustment local when that larger change is not needed.
OPS.11:5 - Archetypal Grounding
OPS.11:5.1 - PumpWorks: a rig plan is not a release decision
PumpWorks continues weekly evidenced controller releases while incident I73, release candidate R42, safety question S19 and provider change P8 coexist. In this constructed use, the four ready test packages carry eight rig-hours of estimated load. The current capacity comparison names actual usable rig windows rather than the number of board cards.
The question is whether a changed readiness and rig-access plan can support the release work without losing another necessary condition.
| Selected structure or relation set | Concrete coupling needed for the decision | Receiving action |
|---|---|---|
| rig-use arrangement | provider access, qualified operator and configuration jointly permit the specified test during the booked window | choose only feasible slots and return changed access to OPS.10 |
| test-evidence relations | T9’s result must concern the configuration used for R42’s release decision | preserve configuration/result correspondence; a result for another version does not close the evidence gap |
| release-supervision relations | ReleaseSupervisorTeam-S2 uses the required evidence and safety result to issue its authorized release, hold or other decision | obtain that decision separately from completing the test |
| existing service commitments | the evidenced-release horizon has parties, conditions and authority for revision | return changed feasibility to OPS.7 and the commitment holder |
Suppose lab-test permission is current and S19 concerns field release. Under that permission and once the needed provider access is in force, the responsible operator may run T9. Field release remains held pending S19 and the release decision. Request provider access if it is missing. If S19 also governs the lab test, that test lacks a sufficient permission basis and remains held too.
OPS.8 maintains the ready queue and keeps incomplete matters visible. OPS.9 distinguishes readiness loss from an unsupported rig-bottleneck claim. OPS.10 compares the usable windows with eligible load and recovery scenarios. Use OPS.11 to return the compatible decisions and identify any missing safety or provider result for the responsible holder.
If P8 reduces available rig time, reopen the capacity and dependent admission/release-policy decisions. Do not reinterpret a completed test as approval to bypass S19 or as evidence that the weekly service commitment has been fulfilled.
The selected permission, evidence, supervision and commitment relations are sufficient for the stated coordination question.
OPS.11:5.2 - Chemical make-to-order: material completion and document work
In a chemical make-to-order setting, goods issue depends on both available product and required commercial documents. The same order-processing resource can be needed for new-order transactions and invoicing. A material-only plan can therefore produce stock that cannot be shipped under the actual transaction conditions.
The first coordination result names that shared-resource and shipment-prerequisite coupling, then compares a compatible transaction/release policy with the local manufacturing plan. Actual commercial rules, financial consequences and authorization remain supplied inputs. The Perez et al. (2023) model compares this coupling under specified conditions. A claim about improvement at a particular plant needs evidence of its operation.
OPS.11:5.3 - AI-assisted operation: generation, acceptance and deployment
An AI-assisted software operation can generate candidate changes faster while human acceptance, test environments or deployment permissions remain unchanged. Candidate changes, tool calls, episodes, evidence and accepted releases have different identities and resource demands.
The practitioner follows only the relevant couplings: which configuration a test supports, who can accept the change, which provider/tool access is available, and what deployment conditions apply. A useful result might reduce admissions to the acceptance capacity, reserve a compatible test environment and return an unresolved release decision. Agent capability and software assurance require evidence about the work performed and the configuration assessed.
OPS.11:6 - Bias-Annotation
| Bias | Consequence | Countermeasure |
|---|---|---|
| diagram realism | A represented connection is treated as an obtaining relation. | Recover participants, relation basis, constraints and use. |
| one-flow reduction | Money, decisions, materials and evidence are merged because all are drawn as arrows. | State each relation and quantity under its own meaning. |
| department-boundary bias | A provider, customer or neighboring service consequence is omitted. | Select affected participants by the operating consequence. |
| local optimum confidence | A feasible local plan is treated as a feasible end-to-end plan. | Trace the necessary cross-structure conditions and shared resources. |
| authority aggregation | One coordinator appears able to grant every participating decision. | Use decisions already in force. Refer a decision still needed to its authority holder. |
OPS.11:7 - Conformance Checklist
- Is one operating change or conflict and its intended result clear?
- Are the selected actual structures distinguished from their views and mathematical descriptions?
- Does each consequential coupling have recoverable participants, relation, conditions, timing and basis?
- Are incompatible units and protected consequences retained in the comparison?
- Can the proposed decisions coexist under the actual resource, evidence and authority conditions?
- Does the result distinguish agreed change, proposed change, missing return and implementation evidence?
- Is it clear when a decision or its qualification needs reconsideration?
Recognition means a practitioner can produce this bounded coordination result. Assurance requires the obtaining relations, qualified consequences and authority on which the chosen action relies; a complete map supplies none of them by itself.
OPS.11:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Call every connected diagram a flow network. | Different structures and descriptions are collapsed. | Apply A.22/E.18/E.18.NET only to the object that meets the corresponding conditions. |
| Optimize material production while ignoring transaction prerequisites. | Product can accumulate without an admissible shipment. | Recover the actual goods-issue and shared-resource coupling. |
| Use evidence from the wrong configuration. | A completed test does not support the current release claim. | Bind the result to the exact subject and conditions. |
| Turn missing information into a negative world claim. | Lack of evidence is mistaken for evidence of absence. | Return the exact unresolved basis and its consequence for use. |
| Treat a coordinated diagram as permission. | The relevant decision-maker may not have authorized the action. | Establish whether a valid decision already covers the action. If permission is still needed, obtain it from the holder or report the gap. |
| Build an exhaustive enterprise map when a smaller account already settles the question. | Unneeded modeling work delays the useful result. | Select only relations that can affect the choice or the grounds for relying on it. |
OPS.11:9 - Consequences
The operation can coordinate a change without making local gains invisible to affected participants. A small coupling account can prevent incompatible schedules, unsupported release claims and displaced costs.
The cost is recovering the relations and obtaining any outstanding decisions across boundaries. Some outcomes remain partial because another practice owns a necessary result. That partial result is useful when it identifies the exact next decision and preserves what can already proceed.
OPS.11:10 - Rationale
Cross-structure coordination is needed because one operating result can depend on relations that no single view preserves. Trace the couplings needed to decide whether a concrete action and its conditions are supported.
Retaining different relation meanings also preserves responsibility. A financial consequence, a safety permission and a causal explanation can all constrain the same plan while requiring different evidence and different decisions.
OPS.11:11 - SoTA-Echoing
| Practice question and selected line | Serious alternative, trade-off and pattern change | Source roles, limits and reopen condition |
|---|---|---|
| How can a locally feasible plan fail at completion? Adapt coordination of actual material, transaction and shared-resource prerequisites. | A material-only or transaction-only plan is cheaper but can omit a condition that makes its result unusable. Sections 4.3–4.5 and 5.2 retain the coupling and compare only the detail needed for the decision. | Perez et al. (2023) supplies a coupled-scheduling candidate and modeled failure evidence. The modeled results depend on the chemical supply chain, business rules and objective studied. Reopen when the business rule, shared resource or material/transaction coupling changes. |
| How much cross-structure representation is useful? Adapt a question-relative selection of obtaining relations at the relevant scales. | One universal flow diagram loses relation meaning; an exhaustive enterprise map costs more than some local decisions warrant. Sections 4.1–4.3 and 5.1 use a small actual-coupling account and keep descriptions separate. | Wassick and Perez (2025), §§3.2–3.5, supplies the current network-of-networks perspective. A.22 and E.18.NET supply the exact structural distinction. The perspective does not establish realized autonomous coordination for a particular operation. Reopen for a missing decision-changing structure or a simpler adequate representation. |
| Can faster software generation be treated as faster service? Adopt subject-correct coupling of generation, evidence, acceptance and permission. | Counting episodes or artifacts is cheaper but can omit acceptance capacity and deployment conditions. Section 5.3 retains the accepted-result boundary while 4.4 traces resource and permission consequences. | The existing Operations subject/current-account Methods and current FPF evidence and relation patterns supply the governing distinctions. They do not establish model capability, software assurance or field performance. Reopen when the actual acceptance path, provider constraint or evidence binding changes. |
OPS.11:12 - Relations
OPS.1–OPS.4 supply the operating focus, relevant views, subject distinctions and qualified current claims. OPS.8–OPS.10 supply queue, diagnostic and capacity results that can require coordination. OPS.5–OPS.7 consume the resulting conditions within their own admission, continuation, priority and commitment questions.
Current FPF A.22, E.18, E.18.2 and E.18.NET govern selected structures and their descriptions; A.6.REL governs direct relation questions. C.11.CRC and C.11 govern finite comparison and choice. B.2.5 and the current control/temporal patterns apply when actual supervision, feedback and response timing affect the choice.
Organization Change Engineering supplies a relevant organization or coexistence Method only at its current scope; a case-specific result still has to exist. Engineering, clinical, safety, labor, legal, financial and other practices retain their direct decisions. OPS.12–OPS.18 provide their own human-condition, service, financial, account, Method-improvement, repertoire and quality Methods. OPS.19 consumes an OPS.11 coupling result only when several otherwise valid operating results conflict across subjects, scales, or horizons. OPS.16 local Method improvement and OPS.20 cultural continuation remain separate questions with their own evidence and authority.
OPS.11:End
OPS.11.1 - Construct and Reconcile Operating Models Across Scales
Type: Method pattern Status: Stable Normativity: Normative
OPS.11.1:1 - Problem frame
Use this when the operation needs a way to obtain a required result, or an operating change looks useful in one account of the work but its consequence cannot be recovered in another. A department appears to have spare capacity while the person doing its work is already occupied elsewhere. A laboratory reports completed samples while the customer needs a complete order. A team can describe individual tasks but cannot explain what controls delivery by the wider service.
Use an adequate existing arrangement and its model, or construct the missing arrangement or description. Connect the local and wider accounts needed for the question. Here a model is a description used to obtain an answer about the operation. A drawing, a set of conditions, a calculation or a simulation can serve that use. Keep the description distinct from the actual work and its arrangement.
First useful move. Choose one recipient’s result and the current difficulty in obtaining it. Recover an available way of doing the necessary work, or identify the missing professional contribution. Follow a present or proposed case through its resources and completion conditions, or recover what maintains the required service over its interval. Where two descriptions refer to the same worker, order or event, bring those references together before calculating.
Practical gain. The practitioner can compare feasible arrangements without mistaking local capacity for available shared capacity or local completion for delivery. The result may also identify the particular coupling that makes a proposed change fail.
The reader needs a usable account of the participants and events. They may identify them directly, use a qualified result, or obtain the missing information from a provider familiar with the work. The elementary cases below need arithmetic and time intervals. A more demanding calculation can be obtained from a modeling specialist.
Use an adequate existing operating model directly when its assumptions and retained detail answer the present question. A staffing total alone may settle a proposed start. This method is useful when choosing or reconciling the model can affect the answer or establish the grounds for it.
OPS.11.1:2 - Problem
Descriptions at different scopes can each look reasonable while making incompatible assumptions about the same operation. A resource appears once in each departmental plan and is then treated as two resources. An internal exit becomes the completion event of an external service, although acceptance still takes time. Several samples are aggregated to one order without retaining which sample prevents delivery.
A desired service can also lack an adequate operating arrangement. A deadline names the result but leaves open how work should be divided, prepared and provided. Comparing only schedules for the existing route can miss a useful change to that route; drawing a different route can hide the technical method or provision that it still needs.
Adding detail everywhere makes the account harder to build, interpret and maintain. Keeping only totals can erase the dependence that matters. The practitioner needs a way to construct an attainable arrangement and retain its consequential dependencies while leaving irrelevant detail out.
OPS.11.1:3 - Forces
| Force | Tension |
|---|---|
| Required result and available way | A desired service can motivate another arrangement, but a drawn operation supplies neither a qualified method nor its provision. |
| Local understanding and shared operation | Local accounts can represent the same resource or receiving condition under different names. |
| Compactness and useful distinction | An aggregate is easy to use until two cases with the same aggregate require different decisions. |
| Stable account and changing policy | A useful service approximation can cease to apply after routing, release or staffing changes. |
| Several working questions | An order deadline, machine load and cash receipt concern related but different subjects and events. |
| Timely decision and additional inquiry | An unresolved premise can matter, but obtaining more detail costs time and may leave the decision unchanged. |
OPS.11.1:4 - Solution
Specify the needed outside result, recover the work that obtains or maintains it, reconcile shared participants, and connect the quantities and events at each useful scale. Refine an account when an omitted distinction can affect the answer or its grounds. Return the resulting comparison with the conditions on which it depends.
OPS.11.1:4.1 - Fix the receiving result and the proposed change
State what the recipient must obtain and which event or continuing condition makes it available. For an order, this may require accepted components, transport and permission to use the result. For a machine service, it may be restored operation. An incident service can instead require qualified response to remain obtainable throughout a covered interval. Use the completion or service condition of the present or proposed operation and keep any proposed change to that condition explicit.
When comparing a change, name the alternative under consideration: another release time, a different allocation, a larger transfer batch, changed routing or another operating method. Identify the quantities that would make the alternative preferable and any conditions it must preserve. When no adequate arrangement has yet been proposed, construct alternatives through :4.2a from the result, available methods and missing contributions. OPS.1 supplies the operating focus and OPS.19 the wider reconciliation when several results govern the choice.
Retain the difference between a fixed input and a decision variable. If a contractor’s two-day turnaround is a commitment that cannot change, the present model can use it as an input. If the proposal changes how that contractor is used, recover the response to that change rather than assuming the same turnaround.
OPS.11.1:4.2 - Recover what obtains the result
For a case, follow its relevant arrival to its receiving completion. For a continuing service, identify the condition that must be maintained, the work that preserves it and the events that require a response. At each consequential action, identify the required input, what can happen next, the condition that enables it and what it produces. Include external work when the result depends on it, even if that work is absent from the organization chart.
Separate the route from the resources used along it. For each consequential operation, determine which resources it holds and for how long. A machine may hold a part throughout a cycle while needing an operator only for loading and unloading. A person may be shared between apparently separate stations. A pool may provide alternatives only when the members have the needed capability and access.
Recover joins and returns. Two component outputs may both be needed before acceptance; a correction may revisit a resource already assigned to new work. A release rule must then account for unfinished obligations as well as newly admitted cases.
Represent the relevant network of transformations and conditions. Distinguish an input or result passed to another operation, a resource used by several operations, and a condition that enables an operation. Label those relations in a diagram or state them in a table. An arrow without a stated meaning can hide whether a result is needed, a person is occupied or someone must authorize the action. A route may branch, join or return; it need not be one predetermined sequence.
Connect that network to the commitments and authority on which it relies. Identify who can request, promise, declare completion and accept the relevant result. Those acts can themselves take time and consume resources. Their organizational meaning and their resource demand answer different questions. Counting a person’s existing assignments establishes demand on that person; it does not establish or redesign the person’s authority.
Compare an alternative by stating what changes: a transformation, its required inputs or outputs, an enabling rule, resource occupancy, a commitment or an authority relation. Keep unchanged relations available for reuse. A changed release limit or route does not by itself establish a change to the organization’s roles. Conversely, leaving the boxes and job titles unchanged does not establish that people can exercise a newly assigned responsibility.
A.22.CGUS helps express available continuations and their conditions before fixing a sequence. OPS.8 supplies readiness and release policy. Use the existing description of those relations when it already conveys them; the work does not require a particular diagram.
OPS.11.1:4.2a - Construct alternatives when the arrangement is not given
Work back from the recipient’s required result to the contributions it needs. For each contribution, recover a qualified way of obtaining it, the input it requires, the result it supplies and the conditions under which the receiver can use it. Use the actual professional explanation or a competent provider’s result. Where no adequate way is available, return that method or research question through FPF C.39 and the relevant discipline. A box labeled with the desired outcome cannot yet support a resource estimate or a promise.
Start from the required contribution. If no suitable route exists, construct one from available professional methods, resources and receiving conditions. If a route exists, keep it as an alternative. Establish why a change is worth comparing: it may miss a requirement or meet it at a cost another arrangement could reduce. The following questions suggest ways to develop the comparison.
- What can be prepared before a particular request is known? Separate reusable preparation from work that depends on that request. Identify how long the prepared result remains usable, which later work consumes it and what can make it obsolete. Compare stock and preparation burden with the delay avoided after arrival.
- Where can a smaller contribution become useful? Choose work and transfer boundaries from readiness and receiving conditions. Compare smaller transfers with the setup, checking and coordination they add. Keep a required join even when its constituents travel separately.
- Which provision can change? Compare qualified alternative resources, routes or providers, including their setup, response, access and existing load. A shared preparation or support service can replace repeated work only when its result is usable in each receiving case.
- Where can the operation accommodate variation? Compare available capacity, suitable prepared inputs and permitted waiting for the same service question. Include the replenishment or recovery that makes the protection sustainable. Preserve the supplied limit when delay, storage or interruption is inadmissible.
Develop the alternative whose mechanism addresses the difficulty. In a familiar case, one changed allocation can suffice. When changes across methods, performers and means must be constructed together, FPF C.32.MWA.PP:4.3–4.7 supplies that comparison. This operating model then retains the particular unit, readiness, occupancy and timing relations needed to calculate its consequences.
Follow the proposed work forward. Show how each intermediate result becomes usable, how common preparation and recurring work are counted, where resources coincide or conflict, and how acceptance is reached or service is maintained. Count displaced work and the transition from the present arrangement. Sections :4.3–4.6 reconcile and compare these accounts. Reject a candidate that merely moves the missing contribution to another participant who cannot supply it.
Separate three possible returns. A rearrangement within established methods and authority can proceed to the operating choice. A changed reusable method needs the method comparison and evidence in OPS.16–OPS.17. Changed organizational contribution or authority relations need OCE.4, OCE.6 and their realization conditions. These contributions can cooperate, but the model keeps each proposed change conditional until its required result is available. When no feasible alternative remains, return the particular requirement or unavailable contribution to its decision maker; a more elaborate model need not be the next useful work.
OPS.11.1:4.3 - Reconcile shared participants and operating conditions
Compare the local accounts at their connections. Establish whether two resource names denote the same resource, interchangeable members of a pool, or different resources. Do the same for cases, batches, deliveries and completion events.
Apply the constraint once to the actual shared participant. If one operator serves two stations, both demands compete for that person’s available intervals. If one vehicle carries several orders together, those orders share the trip; their inclusion does not create several vehicle trips.
Compare calendars and eligibility. Six hours of available labor and six hours of eligible work can remain incompatible when they occur at different times or require different skills. Conversely, an unattended stage can permit another operation during part of the same elapsed interval.
Keep different receiving questions distinct. The project sponsor’s completed result, the performer’s completed assignment and the administrator’s settled expense can have different boundaries. Connect the relevant events instead of treating the shared word “completed” as an identity. OPS.3 supplies subject recovery; F.0.1 and F.9 help when local meanings or their correspondence remain unresolved.
OPS.11.1:4.4 - Connect the quantities and events across scales
Choose the relationship needed between the accounts. Sometimes a wider quantity is a sum of disjoint local quantities. Sometimes it is a union, a maximum, a rate over an interval or a conditional response. Derive that operation from the receiving question.
For example, an order requiring every component becomes ready at the latest required component completion, provided no further work remains. Adding component completion times would describe neither that event nor the elapsed time. Parts processed together in a feasible machine batch share its occupation; take the union of that machine’s occupied intervals when calculating its busy time.
When aggregating, preserve the condition under which the summary is usable. A department’s average service rate may help a sustained-load question but leave the deadline of a particular batch unresolved. A sample-count summary may omit which order is waiting for its final sample.
To construct a sufficient summary, first express the requested result in the quantities you propose to retain. Derive the answer from those quantities and their stated conditions. If an omitted detail still enters the answer, look for two allowed arrangements with the same summary and different answers. Such a pair disproves sufficiency; failing to find one does not establish it. Retain the distinguishing relation, derive a useful bound, or restrict the answer. In the laboratory case below, the sample-to-order relation and the latest required completion provide the order’s completion event; sample totals alone cannot. C.29.1 develops this construction and preservation question. MMP.18 constructs compatible exchanges when mathematical models must be coupled, including shared quantities, time scales, feedback and uncertainty.
OPS.11.1:4.5 - Refine the part on which the answer depends
Start from the smallest available account that addresses the question. Open a local part when a consequential result depends on its hidden timing, sharing, variation, return or completion condition.
A service block described by a fixed delay can be adequate for a question that leaves its load and resources unchanged. If the proposed release creates congestion inside that block, replace the fixed delay with the load-sensitive account needed for the comparison. Keep unaffected neighboring blocks at their sufficient level of detail.
Changing scope and changing detail are different moves. Adding a subcontractor widens the modeled operation. Showing the subcontractor’s internal batching adds detail. The first can be necessary while the second is irrelevant because the contract already supplies the required response.
Identify uncertainty separately from a deliberate simplification. “The loading time is unknown” calls for an estimate, range or observation if the answer depends on it. “We combine identical loading steps” is a modeling choice whose effect can be compared. C.11.DUA governs whether resolving an uncertainty is worth more than a restricted answer or a different action.
OPS.11.1:4.6 - Obtain and interpret the operating alternatives
Translate the recovered conditions into a form from which the requested result can be obtained. MMP.10 constructs constraints; OPS.10 selects the service and capacity question. Use a hand calculation when it suffices, or choose a computational procedure under C.29.2 and the relevant CMP methods.
Check the obtained alternative against the operating arrangement. Are the required performers, equipment and other resources available in the proposed intervals? Are the receiving inputs available together? Does the calculated completion make the result usable, or can the arrangement sustain the required service condition throughout its interval? A schedule can satisfy a mistaken model, so successful computation alone does not settle these questions.
For a comparison across scales, return the local change and its wider consequence together. Explain where a delay, burden or unfinished obligation moves. Use OPS.14 when financial consequences bear on the comparison or its grounds. Interpret each quantity for its period and use.
Stop with a sufficient comparison or the missing contribution that prevents one. Retain the assumptions a recipient needs to use the result. When routing, resources, calendars or acceptance changes, revise the affected account and propagate the change through the relationships that consumed it.
OPS.11.1:5 - Archetypal Grounding
OPS.11.1:5.1 - Two departments share one operator
Three units need preparation and then inspection. Each step takes two hours of one operator’s attention. Preparation and inspection are shown as separate departments, each with an eight-hour day. A departmental summary assigns six hours to each and appears to permit same-day completion.
Recovering the resource references shows that the same person performs both steps. The work needs twelve operator-hours. This excludes completion within eight hours under the stated arrangement, without needing a detailed simulation. Preparing and inspecting each unit in turn attains twelve hours if no other restrictions apply.
Now inspection changes: its first half-hour requires the operator, followed by one and a half hours of unattended machine operation. The operator demand becomes 7.5 hours, but that total alone does not prove an eight-hour schedule. With one inspection machine, a feasible sequence is:
| Unit | Preparation | Inspection with operator | Inspection unattended | Completion |
|---|---|---|---|---|
| 1 | 0–2 | 2–2.5 | 2.5–4 | 4 |
| 2 | 2.5–4.5 | 4.5–5 | 5–6.5 | 6.5 |
| 3 | 5–7 | 7–7.5 | 7.5–9 | 9 |
The machine’s final unattended interval extends beyond the operator’s work. Completion by hour eight is still impossible: preparing all three units and starting all three inspections needs 7.5 operator-hours, followed by the last inspection’s 1.5 unattended hours. The schedule attains that nine-hour bound. Separating resource occupancy from elapsed processing gives the next design question: what can shorten or overlap that final tail?
OPS.11.1:5.2 - Sample throughput does not determine order completion
A laboratory has one machine that processes up to two samples in a four-hour batch. Order U needs samples u1 and u2; both are ready at zero. Order V needs v1, ready at hour three. No other work remains after the required samples finish.
Starting U’s two samples at zero completes U at four. Processing V next completes V at eight. Waiting until hour three and batching u1 with v1 completes those samples at seven; u2 then completes at eleven. Both alternatives use two machine cycles and process three samples, yet the order completions differ: (4,8) versus (11,7).
For a promise U by five and V by nine, only the first alternative meets both. The model must retain the sample-to-order relation and the all-required completion condition. A total sample count cannot answer that promise. If partial results become useful to the customer, revise the receiving result rather than assuming the same all-required condition.
OPS.11.1:5.3 - An outside service can remain compact
A team must release a report by Friday. An external reviewer undertakes to return comments within one working day for the proposed submission class and volume. The team’s comparison changes its internal preparation sequence but leaves that submission within the commitment.
The model needs the external review step, its working calendar and the team’s response to comments. It can use the promised response as a conditional input without modeling the reviewer’s internal allocation. If the proposal instead triples submissions beyond the commitment, that input no longer answers the changed use. Return to the external capacity or commitment question before relying on the old delay.
OPS.11.1:5.4 - Change a report route while retaining its acceptance authority
A laboratory has promised an accepted report. Its operator produces an analysis record; a qualified reviewer examines that record and can require correction. Only the reviewer’s acceptance makes the report available for the promised use. The same person may hold both roles if the applicable rules allow it; their occupied intervals must then be reconciled as one person’s demand.
The solid arrows below pass named work products. The dotted links state conditions supplied by commitments, authority or resources; they do not pass the report or prescribe a sequence.
flowchart LR
S["Sample and required case data"] --> A["Analyze"]
A --> D["Analysis record"]
D --> R["Review"]
R --> P["Accepted report"]
R --> C["Correction request"]
C --> F["Correct the record"]
F --> D
K["Promised case and permitted start"] -. "enables" .-> A
L["Analyzer and eligible operator time"] -. "required during analysis" .-> A
V["Reviewer authority and available time"] -. "required for review and acceptance" .-> R
Suppose incomplete case data repeatedly occupy reviewer time. One proposal inserts an automated completeness check between the analysis record and review:
flowchart LR
D["Analysis record"] --> X["Check required fields"]
X --> Y["Record with required fields present"]
Y --> R["Review"]
X --> C["Missing-field report"]
C --> F["Complete the data"]
F --> X
R --> P["Accepted report"]
This second diagram shows only the changed route. The first diagram’s start conditions, review authority, substantive correction return and resource constraints still apply. The automated check establishes field presence, not correctness or acceptance. Add its computing demand and the operator’s completion work to the resource account; compare the saved review work with that added demand. The new route can be worse if it moves the bottleneck to a scarce operator. Use a simulation or trial when it could resolve a consequential uncertainty about the choice or its grounds at a justified cost.
These proposals change different things:
| Proposal | What changes and what must be obtained |
|---|---|
| Give an already qualified and authorized reviewer a different case or time slot. | Reconcile that person’s existing assignments and commitments through OPS.10–OPS.13 and OPS.19. The allocation need not change any authority relation. |
| Insert the completeness check under existing permission. | Compare the changed route and its resource consequences. OPS.16 can govern a useful trial; a locally usable operating arrangement can supply its conditions. |
| Let the operator accept reports without the previously required reviewer. | The proposed completion and authority relations change. Obtain the relevant professional acceptance decision and organization-design/assignment result before relying on the proposal. A faster route does not authorize it. |
| Introduce the route where staff cannot yet perform or sustain it. | Establish the needed capability, practice and support. Use the relevant development, Method-introduction or organization-change methods for that question; put their actual learning and support work into the same resource account. An unchanged organization chart does not supply those capabilities. |
The result is a comparison of identified changes and their consequences, with any missing decision left visible.
OPS.11.1:5.5 - Derive preparation and provision from a changed service requirement
Six orders for configured kits arrive together. The service must make all six kits available within two hours. One qualified technician and one workstation are available in that interval. The stipulated method needs, for each kit, 20 minutes of preparation usable for any order in the stated class and 10 minutes of case-specific finishing and acceptance. Both phases occupy the technician and workstation. There is no other work or transfer delay in this constructed comparison. Performing all six kits after arrival requires 180 minutes of each resource, exceeding the available 120.
The current method permits preparation before an order is known: each prepared item remains compatible with any kit in the stated class and usable for the whole day. Both the technician and workstation have an otherwise uncommitted two-hour window before order arrival. One candidate therefore prepares six items in that earlier window and performs the six ten-minute finishes after arrival. The last kit is accepted at minute 60. Total labor remains 180 minutes; the arrangement changes when the preparation is performed and what is held between performances. If fewer orders arrive, prepared items can remain unused, so inventory and obsolescence belong in the comparison. The two-hour service can be supported for this stipulated six-order case. If the workstation is unavailable in the earlier window, this candidate has no supported preparation slot; obtain another feasible slot or compare a different arrangement.
Now the product specification changes: preparation must use the actual ordered device’s serial-number data, which becomes available only on arrival. Preparation before the order is known is no longer usable. Keeping the previous stock does not remove the 180-minute post-arrival demand. Revise the service model because its preparation relation, work boundary and timing premise changed.
A second qualified technician with an independent workstation can provide a different arrangement, if both are actually available under the required authority. Each technician completes three thirty-minute kits; the last kits are accepted at minute 90. Compare the added provision and its displaced work with a later or smaller service offer. If the second provision is unavailable, retain the 180-minute bound for the existing arrangement and return the promise to its owner. Product engineering might supply a genuinely different preparation method, but that result must be obtained before counting its expected saving.
The unit design follows the same change. Initially an order-independent prepared item can exist before any customer case; after the change its preparation belongs to an identified order. OPS.3 preserves that correspondence, OPS.10 supplies the capacity and schedule, OPS.13 forms the possible service agreement and OPS.14 compares consequential payments and unused stock where those matter. Existing acceptance authority and the one-kit result can remain unchanged. Revise the affected capacity and delivery conclusions while keeping conditions that still hold.
OPS.11.1:5.6 - Model a continuing service when no case is completed
A facility buys readiness over a four-hour interval: a qualified responder must be able to begin an incident response within ten minutes of an incident’s arrival. The stipulated demand condition permits at most one active incident; the responder remains available for any response owed from that interval. Alerts arrive within one minute. The response method, access and equipment are already qualified.
One arrangement lets the responder perform a records audit while no incident is active. The audit can be left in a resumable state within one minute, and obtaining the response setup takes two more minutes. Even counting those delays consecutively, response can begin within four minutes. The operation can therefore obtain some audit work while preserving the stipulated readiness. A quiet four-hour interval with zero incident completions can still supply the purchased service.
Another proposal assigns the same person to a twelve-minute task that cannot be interrupted. An incident just after that task starts can leave almost fourteen minutes before response begins, including the two-minute setup. Low average incident demand does not make this arrangement satisfy the ten-minute condition. Move that task to other provision, change its interruption method if technically possible, or obtain a different service agreement. OPS.8.2 supplies the fuller release-and-restoration construction.
If demand changes to permit simultaneous incidents requiring separate responders, the single-responder premise fails even though the four-minute return remains attainable. Obtain the required qualified provision or revise the promise. The account keeps availability over an interval, work performed during quiet time and actual incident results distinct; a completed-case count alone cannot express all three.
OPS.11.1:6 - Bias-Annotation
Most examples favor discrete cases and identifiable completion events; :5.6 instead retains continuing availability. Continuous production can require amounts and rates. Choose the modeled subjects from the receiving result; a successful discrete-case model supplies no automatic transfer to every operation.
The method also favors consequential detail. That can miss an effect outside the initially named decision. When a participant identifies a plausible displaced burden or failure, include the affected relation before treating the local comparison as sufficient.
OPS.11.1:7 - Conformance Checklist
- The model answers a named operating question and uses the recipient’s completion or service condition.
- The arrangement uses sufficient professional contributions. For a proposed change, the affected dependency, preparation, recurring work and receiving connection are clear where they matter.
- Routes, resource occupancy, calendars and eligibility are distinguishable where they change feasibility.
- Shared participants remain shared across local accounts.
- Product dependencies, resource use, enabling conditions and authority relations retain their meanings; a proposed change identifies which of them changes.
- Each aggregate or cross-scale relationship has an operation and conditions appropriate to its receiving use.
- A refinement identifies a distinction on which the answer or its justification depends. Unaffected detail can remain compact.
- The returned result distinguishes the computed consequence from the assumptions about the operation that support it.
- A changed premise identifies the affected account and receiving consequences.
OPS.11.1:8 - Common Anti-Patterns and How to Avoid Them
| Observed or text-invited mistake | Consequence | Repair |
|---|---|---|
| Give each departmental box its own copy of a shared worker | Individually feasible plans compete for the same hours. | Reconcile resource references and impose the common occupancy constraint. |
| Sum or average local completions to obtain delivery | The result ignores joins and the final required contribution. | Derive the receiving completion event and its relation to local events. |
| Preserve a fixed service delay after changing its load | The comparison suppresses the congestion it may cause. | Reopen that service response under the proposed conditions. |
| Treat a changed route or a new assignment as proof of organizational redesign | Resource regulation becomes confused with changing who may promise or accept a result. | Compare the product, resource, commitment and authority relations separately, then obtain the result needed for each actual change. |
| Expand every box before comparing an alternative | Modeling consumes resources without improving the decision. | Refine the part whose omitted distinction affects the answer or the conditions that support it. |
OPS.11.1:9 - Consequences
The practitioner can construct an operating alternative as well as compare a supplied proposal. Local choices become comparable at the scope where their consequences matter. When a contribution is missing, the account identifies it, for example a qualified method, effective provision, occupancy interval, service response, completion relation or calculation.
The result remains conditional on the work description and model choices. A more detailed account can cost more without improving the decision; an omitted interaction can invalidate it. Keeping the relationships between accounts visible makes a later correction localizable.
OPS.11.1:10 - Architectural Rationale
Coordination uses several descriptions because the work supports several questions. Forcing them into a single hierarchy hides shared resources and cross-cutting relations. Leaving them disconnected permits incompatible assumptions. This method connects the quantities and participants needed for one operating decision while allowing the accounts to retain different purposes.
The outside result selects useful internal detail. The same principle also permits a return from an internal obstruction to a changed promise or wider arrangement. The direction is therefore iterative rather than a one-time decomposition.
The operating contribution is the construction of work boundaries, preparation and provision alternatives, routes, resource use, joins, calendars and completion relations. General mathematical coupling, constraint formulation and computation remain available through their own methods. Use those methods for the mathematical or computational contribution the operating question needs.
OPS.11.1:11 - SoTA-Echoing
To compare a change involving shared resources or several contributors to one result, choose the model’s scope and detail from the receiving question. Adopt that purpose-led selection from Robinson’s conceptual-modeling tutorial (2017), §§2–6, and adapt it to the route, resource and completion construction in :4.2–4.5. The selected answer retains the relations that determine the requested consequence and leaves the rest compact. Robinson supplies the distinction between scope, detail, assumptions and simplifications; the operating constructions here make that selection usable before deciding whether computer simulation is needed.
A serious default is to combine departmental capacity and output totals. In :5.1 those totals conceal competition for one person; in :5.2 total sample throughput does not determine either order’s completion. Recovering the shared resource and the sample-to-order join corrects those answers without describing every internal action. It costs an inquiry into the relevant identities and timing, but the first case can already be rejected by an arithmetic bound. Conversely, a detailed schedule of every supplier would add inquiry and maintenance without changing :5.3’s comparison: its conditional one-day commitment is sufficient. Sections :4.4–4.5 therefore construct or test a sufficient summary and refine only a consequential omission.
Hopp and Spearman, Factory Physics, third edition, supplies production reasoning about batches, capacity and variability for identifying these dependencies. Applying one of its relations to another kind of operation still requires recovering the corresponding subjects and events. Oliveira, Sagawa and Mušič (2025) offers a continuous, feedback-controlled workload account as another choice. For sustained aggregate regulation, a compact continuous account can avoid event-level detail; use it when its flow relation and capacity-control mechanism fit the operation. For an individual deadline, retain the individual completion relation or obtain a justified bound; continuous draining alone does not determine that event.
Dietz and Mulder’s Enterprise Ontology (2020), §§4.4.4–4.4.6, distinguishes acts that produce a result from acts that establish and discharge commitments, and distinguishes their coordination structure from one sequential flow. The useful contribution here is to preserve request, promise and acceptance relations while calculating the work and resources that carry them. This method does not adopt a universal tree structure, human-only agency or a claim that the organizational model alone determines every operating consequence. Section :5.4 keeps an unchanged authority arrangement while changing the product route; a different proposal changes the acceptance relation and therefore needs another supplying method.
Anderson’s Kanban (2010), chapter 1 and chapter 10’s capacity-allocation discussion, combines regulation of work in progress with an approach to introducing changed practice. The Kanban change principles explicitly distinguish change management from service delivery. Use the relevant operating rule and assess its introduction separately. In particular, allocating WIP slots among work classes does not by itself establish staffing, elapsed service time or the authority to change a commitment. Those remain modeled conditions.
Constructing an alternative requires more than predicting the incumbent. The production mechanisms compared in OPS.Reference:19.3 support :4.2a’s arrangement choices. Section :5.5 derives an alternative from the receiving conditions. C.32.MWA.PP supplies the general comparison of method, performer and provision; this pattern retains the operating dependencies and calculations.
Reconsider this choice when a changed promise, resource or policy makes an omitted relation affect the answer, or when an alternative construction obtains the same required answers with less inquiry and maintenance. Trace a newly observed coupling to the answers that depend on it.
OPS.11.1:12 - Relations
OPS.11 identifies interacting operating structures; this method constructs and reconciles the accounts needed to reason about their consequences. OPS.19 uses the result when several work scopes and outcomes constrain one choice.
OPS.3 recovers operating subjects. OPS.8 supplies readiness, release and protection; OPS.10 addresses capacity and service; OPS.15 and OPS.15.1 supply the event-defined account. OPS.16 uses the current and proposed operating networks to bound an improvement or trial. OCE.4 and OCE.6 supply contribution design and effective assignments when those organizational relations must change; OCE.11 coordinates an organization change with continuing service. Existing assignments and their resource consequences can be modeled here without redesigning those relations.
C.32.MWA supplies practice-architecture synthesis; C.32.MWA.PP constructs and compares performance and provision across methods, performers, means and allocations. Use C.39 to find or develop a missing way to obtain a required contribution. C.29 connects mathematical descriptions to their subjects; C.29.1 develops result preservation between mathematical accounts. MMP.18 constructs mathematical coupling, MMP.10 the joint constraints, and C.29.2 the computational formulation. B.5.MPC and its revision method coordinate a change crossing these contributions.
OPS.11.1:End
Part VII — Protect Human Conditions and Establish Service Commitments
OPS.12 - Protect Human Conditions in Operating Decisions
Status: Stable
OPS.12:1 - Problem frame
Use this when an operating choice changes people’s workload, exposure, attention, discretion, support or recovery. Typical situations include extending a service window, adding an urgent job, automating preparation, changing handovers or asking the same people to cover several services. It also applies when planning one’s own work and the usable time depends on an ordinary recovery arrangement that has yet to be found.
Begin with the affected work and the people who perform, receive and support it. Ask where the proposed gain creates additional work or removes a protected condition. The first useful result is a supported decision to retain or change the arrangement, a bounded proposal awaiting authority or evidence, or the specific condition that rules a proposal out, with its service effect and human consequences made explicit.
Operations practitioners can change demand, schedules, task arrangements and support within their authority. This pattern governs those operating interventions. Health assessment, clinical judgment, capability development, employment conditions and organization design require their own qualified work when the choice depends on them. An ordinary schedule correction under established conditions can proceed without a general assessment of people’s wellbeing. When the missing input is an ordinary, personally chosen arrangement of work and rest, §4.3.1 explains how to obtain and reconsider it. A supplied protection or clinical conclusion is preserved within that work.
In PumpWorks, an extra two hours of rig access is useful only if qualified people can cover it. Extending the same operator’s work would consume protected recovery and the preparation for incident duty. The practical choice is qualified relief, a different service promise or another feasible arrangement.
OPS.12:2 - Problem
An operating plan often counts the visible task while omitting the attention needed for interruptions, rework, coordination and recovery. A local gain then appears as spare capacity even though another service or group supplies the effort.
Averages can conceal that transfer. Lower mean workload can coexist with an unacceptable burden for the small group handling exceptions. Asking people to cope better leaves the operating source of the burden intact when demand, scheduling or missing support causes it.
OPS.12:3 - Forces
| Force | Practical tension |
|---|---|
| service demand and protected conditions | Urgent work may matter greatly while the proposed staffing arrangement remains infeasible. |
| aggregate benefit and affected groups | A faster main queue can increase effort for support staff, customers or people handling exceptions. |
| immediate relief and sustainable work | Temporary cover can contain a current problem while its recurring cause still requires a different arrangement. |
| useful evidence and collection burden | Existing records and participant accounts may settle the choice; a broad survey can delay action and create more work. |
| local discretion and professional judgment | An operating practitioner can revise a plan within authority while needing a specialist result for a disputed protection or capability claim. |
OPS.12:4 - Solution
OPS.12:4.1 - Recover the affected work and applicable conditions
Name the operating decision, service horizon, tasks and affected groups. Follow the work beyond the visible queue: who prepares inputs, handles failures, answers interruptions, supplies handovers and receives incomplete results? Include the work the proposed intervention would displace.
Recover the applicable conditions from current assignments, service arrangements and qualified protection or capability results. These may concern recovery, exposure, supervision, safe staffing, access to help or a limit on simultaneous responsibilities. Keep their scope clear. A condition supplied for one task, person group or environment may need reconsideration under another.
Use ordinary descriptions first. A roster, service log and conversation with affected practitioners can be enough to identify that an extra task overlaps existing duty. If a protection is known to be breached, take the permitted containment action promptly and seek any further authority needed.
OPS.12:4.2 - Inspect actual demand and burden
Compare planned work with what people have to do under normal and consequential adverse conditions. Distinguish assigned hours, time actually worked, interruptions, recovery opportunities and work left to someone else. Use affected people’s accounts of work the schedule or system record omits. Ask them about a consequential gap when needed.
Use existing permitted observations at the level needed by the decision. An exception log may show that a new intake policy creates repeated calls to one specialist. A participant’s report may identify an exposure or conflict that has not yet been measured. Preserve that report’s reach while deciding what action or further inquiry it warrants.
State the claim the evidence supports. A record of missed recovery is an operating observation. A report of exhaustion is the person’s account of their condition. A health diagnosis or a general causal estimate requires the appropriate professional method. A narrow uncertainty about health effects does not erase a supplied operating limit or an observed service conflict.
If a choice depends on missing information, identify the answer and the time by which it is needed. Use an applicable record or direct observation, or ask the responsible provider. For example, establish whether the next shift meets a named protection for the affected group. Work whose conditions are established may continue.
OPS.12:4.3 - Develop alternatives that change the source of burden
Begin with alternatives that reduce unnecessary demands or change the operating arrangement. Compare the current arrangement with a serious feasible alternative when that comparison matters. One supported correction or a binding protection can settle the question.
| Source of burden | Useful operating alternative | Condition to preserve |
|---|---|---|
| Collection or coordination work has no current use. | Remove or simplify the unnecessary work after checking its receiving decision, assurance and recovery use. | Retain the information or action that a real consumer still needs. |
| Admitted demand exceeds supported service. | Limit new admissions, change scope or renegotiate the service time. | Preserve existing commitments until the authorized parties revise them. |
| One person must serve incompatible duties. | Provide qualified relief, separate the duties or change their timing. | The relief must have the capability, assignment and support the receiving task requires. |
| Rework and handovers create repeated interruptions. | Repair the input, handover or support arrangement that creates the interruption. | Keep consequential exceptions visible and ensure that someone can handle them. |
| A changed task exceeds current capability. | Compare changing the task, supplying support and developing capability. Obtain the capability result if the chosen arrangement relies on it. | A training proposal must fit the actual learning need and available time. |
Personal support can be valuable when it answers a real need. It is inadequate as the sole response to an operating arrangement that continues to violate a protected condition. Where a structural change to the organization is needed, formulate that change question and its required consequence comparison for the responsible practitioners.
OPS.12:4.3.1 - Obtain an ordinary work-and-recovery arrangement when it is not yet known
Use this branch when a person can see nominally free time but does not yet know what arrangement of work, rest and other activities is manageable for the intended work. The result is a provisional arrangement with evidence for its use and conditions for reconsideration. It is not an estimate of the person’s maximum capacity. A person can use it for their own work; someone arranging others’ work must preserve their discretion over private leisure and obtain only the information needed for the operating decision.
Recover a few relevant occasions. Begin with the decision that is waiting: whether to add an evening session, retain an existing commitment or change when demanding work occurs. Use existing records or brief notes from occasions that expose that question. Recover actual starts and finishes, interruptions, remaining duties, rest or leisure that occurred, and the person’s account before and after it. Include preparation, travel and any burden shifted to someone else. A short description such as “answered service messages through the intended break; restarted twice; left the review unfinished” can be more useful than a general energy score. Choose observation length from the variation that matters, such as ordinary days and days with late duty. Stop collecting detail once the observations suffice for this decision.
Find what can change. Separate an unavailable opportunity for recovery from an available activity that the person did not find helpful. If work keeps occupying the intended time, compare reducing or moving that work, changing the response arrangement or obtaining real cover. Asking for a better leisure activity leaves that conflict unresolved. Where a genuine choice remains, ask what the person seeks: quiet, relief from work-related demands, enjoyable movement, company, or an activity they choose for its own interest. Use familiar, accessible options and consider a new one when it offers a plausible benefit worth trying. These are reasons to form alternatives, not guaranteed effects of an activity. An active hobby can add effort. Use the person’s preference and experience to judge what fits.
Construct one feasible change and its continuation. Specify the proposed activity or work arrangement, an actual opportunity for it, the effort of preparing it, and the work that will be reduced, moved or left unpromised. Include affected household or service arrangements; another person’s unagreed extra work is not free capacity. Compare the proposal with the current arrangement and any serious feasible alternative that addresses the source of burden. Preserve supplied protection, clinical advice and other binding conditions. If no feasible trial fits, reduce the proposed commitment or seek the particular support or decision needed to make one possible. Do not fill an uncertain recovery need with new work while waiting for proof of harm.
For a modest trial, choose the smallest change likely to answer the practical question. A person might reserve a familiar break before one kind of evening task, or move that task to an existing daytime window. Choose the occasions to try, what to observe and when to reconsider. Agree any changes affecting another person’s commitments with that person. Prefer one material change when learning which change helps matters. If several changes must be made together, the observation concerns that whole arrangement; it does not identify the separate effect of each part.
Observe both the experience and the receiving work. Check whether the opportunity and chosen activity actually occurred, whether the person found them restorative or otherwise worthwhile, and what happened in the relevant work: a completed usable result, repeated corrections, an interrupted attempt or work left for later. Keep these observations separate. Feeling better does not establish unchanged error rates or justify increasing workload. Rest and leisure may also be worthwhile without raising output. A missed trial is evidence about access or the arrangement, not evidence that the activity failed.
Revise the commitment at the reach of the evidence. A workable trial can support continuing the same bounded arrangement under comparable conditions. It does not establish that the activity caused an improvement, supply a clinical conclusion or warrant adding more hours. Retain a margin for the uncertainty that matters. If recovery remains insufficient or work still fails, return to the relevant alternative: less demand, another timing or activity, better support, or inquiry into a different cause. Keep an established useful part while changing the failed one.
Return the resulting actual work windows, retained recovery opportunities, remaining uncertainty and reconsideration condition to OPS.10 and OPS.10.2 before making a service or development commitment. Use an applicable qualified health conclusion when needed, or seek it from the appropriate practitioner. In particular, a known protection breach requires the response in §4.1 rather than completion of this trial. Reconsider when duty, household demands, access, task difficulty or the person’s reported condition changes. Once the arrangement is adequate for the decision, stop unnecessary observation.
OPS.12:4.3.2 - Fit a usable work product to the available window
Use this branch when a person has a manageable work window but the intended task is too loosely specified or too large to promise a useful result within it. An already clear task with a credible estimate needs no further decomposition. Use §4.3.1 when the work-and-recovery arrangement itself remains unresolved.
Choose the result from its next use. Name who will use the product, for which action or judgement, and what must be complete for that use. Include its location and edition when the recipient needs them. C.39 supplies the receiving-use test. A smaller product is a candidate only when it supports an actual continuation: a complete discrepancy list for one drawing revision can let its author correct the inputs; half of an unreviewed calculation may supply no such result.
Compare the required work with the real opportunity. Start from a few comparable performances using the intended Method and support. Include retrieving inputs, preparation, foreseeable interruptions, checking and preserving the product. Compare their relevant range with the available window, retaining a margin where uncertainty can change the promise. With no comparable history, estimate a known bounded operation provisionally from available inputs, or state what prevents a credible estimate; an unfamiliar Method calls for the particular explanation or help needed to perform it. A free calendar interval alone supplies neither an estimate nor that capability.
Adjust the product or the arrangement. Reduce scope only while preserving the named use. Alternatively obtain the missing support or a different window, or revise the commitment. If the Method requires a longer uninterrupted operation, preserve that condition; splitting its elapsed time does not create independently usable products. OPS.10.2 supplies scheduling when precedence, resources or deadlines need further comparison. A useful intermediate product leaves the larger commitment open.
Return the attempt to the next choice. At the end, check whether the product supports its promised use, preserve the actual result and compare actual work with the estimate. A partly completed product remains unfinished unless an independently useful narrower result is established. Use the mismatch to revise the next scope, estimate, support or window. Repeated overrun calls for changing the arrangement, not automatically extending work into retained recovery time.
In a constructed example, an engineer has a manageable 50-minute window. A complete design calculation needs about two hours under the known Method. The drawing author can first use a checked list of load mismatches for one named drawing revision. Comparable reviews of that scope took 20–25 minutes; retrieving the inputs and preserving the checked list need another 15 minutes. The engineer selects that complete intermediate result, with 10 minutes left for relevant uncertainty. If the inputs are unavailable, the estimate is no longer applicable: the engineer obtains them or revises the promise. Delivering the list enables input correction; it does not finish or validate the design calculation.
OPS.12:4.4 - Compare the consequences by affected group
Test protected conditions before weighing optional gains. Reject an alternative that violates an applicable condition. The decision maker can then compare the remaining service, burden, resource and financial consequences with an explicit preference.
For each material affected group, ask what work increases or decreases, when it occurs, what recovery or support remains, and which consequences matter to the decision or the grounds for it. A short comparison of two rosters can reveal the decisive conflict.
Consider adverse conditions that bear on the choice: an incident during the extension, a missing relief worker, additional rework or a failure in automated support. Keep the scenario’s assumptions visible. An arrangement that works only if no exception occurs can be selected only for a use whose required protection allows that condition.
Use OPS.13 for the resulting service commitment and OPS.14 when payment, displaced contribution or funding bears on the choice or its feasibility. A financial benefit is one consequence among those that remain after feasibility has been established.
OPS.12:4.5 - Authorize, observe and revise the intervention
When an intervention is selected, state who may authorize and perform it, what changes, when it starts and how existing service will continue. Identify the protected conditions and what would call for stopping, reversing or obtaining another decision. Use the existing means of communicating the outcome, including a decision to keep the present arrangement.
Choose a proportionate observation for the uncertainty that remains. Check, for example, that relief actually arrives, incident coverage obtains and the planned recovery can occur. A favorable report from one shift supports a claim about that shift and participating group. Broader continuation or causal claims need evidence appropriate to those uses.
Reopen the intervention when a change in demand, affected group, task, support, protection or observed burden affects its justification. If the same problem recurs, return the failed operating-method assumption to OPS.17 or the responsible method-change work. Temporary relief can remain useful while that separate question is addressed.
OPS.12:5 - Archetypal Grounding
OPS.12:5.1 - PumpWorks obtains relief or changes the promise
This constructed case concerns four ready test packages, each requiring two rig-hours. Six hours are available. In the adverse scenario, one planned package needs one additional two-hour test and then passes; all other planned packages pass first time. Two completions and the repeat fit six hours. Three completions and the repeat need eight.
The resource owner offers two more rig-hours. The supplied staffing arrangement requires the current operator to leave rig duty after hour six so that protected recovery and subsequent incident duty remain possible. The operation must maintain its stated incident coverage. The six-hour limit applies to this operator’s recovery and incident duties in the example.
| Alternative | Human and service consequence | Decision |
|---|---|---|
| Keep the current six-hour window. | The operator’s recovery and incident arrangement remain intact; the adverse scenario supports two completions. | Use this baseline while another feasible arrangement is unresolved. |
| Extend rig work using the same operator. | The extension conflicts with the supplied recovery and incident-duty conditions. | Reject this staffing arrangement. More completed tests cannot compensate for the conflict. |
| Extend to eight hours with qualified relief for the extra work. | The original operator’s conditions can remain intact, and three completions fit the stated adverse scenario. | Return a feasible staffing proposal, conditional on confirmed relief, the required handover, access and financial authorization. |
For the extension, the operating practitioner checks that qualified relief and the required handover are already provided or obtains the missing staffing decision. If cover or authority is unavailable, use a feasible service plan. Four completions with one repeat still require ten rig-hours.
For the extended plan, the immediate observations concern the actual relief, handover, recovery and incident coverage. A report that the shift was manageable adds one observation to the continuation decision, alongside evidence of actual cover and recovery. It cannot by itself establish a health effect or general safety of longer shifts.
Laboratory test permission and field release remain separate decisions. The extra person supplies operating capability; that assignment does not decide safety question S19 or authorize release candidate R42.
OPS.12:5.2 - A hospital changes an admission batch
In a constructed hospital operation, six already qualified routine service cases are scheduled to arrive together. The visible preparation task fits the main team’s hours, but the receiving support team reports that the batch overlaps another required duty and removes its planned recovery. Existing shift records confirm the overlap.
The coordinator compares adding qualified support, staggering the cases within their permitted service windows, and retaining the batch. Clinical priority and each patient’s care requirements are supplied by the responsible practitioners. Two groups of three can satisfy those conditions and the support arrangement; changing the timetable is within the coordinator’s authority.
The selected intervention staggers the arrivals and communicates the new times to the receiving team and affected service users. The next observation checks actual arrivals, support work and any delayed cases. An urgent clinical change returns to the qualified clinical decision and may reopen the operating plan.
OPS.12:5.3 - AI preparation transfers effort to readers
An assisted service triples draft production while keeping the same acceptance team. Readers report more interruptions and unfinished reviews. The relevant operating work includes checking outputs, resolving errors and answering requests, so draft count does not represent the whole burden.
The practitioner compares limiting generated drafts to the acceptance rate, obtaining qualified review capacity, and changing preparation so that fewer unusable drafts reach readers. An immediate admission limit can reduce the growing backlog under the existing service authority. A changed preparation method needs evidence that it preserves the required output quality; additional review capacity needs a real capability and staffing result.
The observation follows accepted results, rework, interruptions and the readers’ accounts over the chosen window. If fewer drafts leave service commitments unsupported, use OPS.13 to obtain the needed service decision from the responsible parties. Requiring readers to clear every generated draft by extending their work would recreate the original burden.
OPS.12:5.4 - A person obtains usable work windows before promising them
In this constructed case, a specialist sees eight apparently free hours: Monday and Wednesday 18:00–20:00 and Saturday and Sunday 10:00–12:00. They want to add development work and prepare a professional proposal. Current work and household commitments are otherwise arranged, but evening service messages often continue after 18:00. The person does not yet know whether the nominal evening windows support the new work.
Brief records from the relevant evenings show two different problems: messages occupy part of the intended break, and uninterrupted evening attempts still involve repeated restarts. The person reports wanting time away from work before starting another task. Neither observation diagnoses the cause of fatigue. They are enough to reject promising all eight hours as new work.
Within the current service agreement, the specialist can hand over unresolved messages before 18:00 and leave later routine messages for the next service window; urgent cover is already assigned elsewhere. This removes the spillover without silently dropping a service obligation. They compare two personal options: reserve the first evening hour for a familiar enjoyable walk or quiet reading, or leave evenings free, retain the existing weekend work and defer the new development commitment. The former preserves two short evening opportunities, but its usefulness is still to be tried. Travel and preparation fit the reserved hour; the choice creates no new household duty for another person.
For the next comparable week the person chooses the first option. Their four hours of planned work comprise a first attempt on Monday 19:00–20:00, feedback and correction on Wednesday 19:00–20:00, a fresh attempt on Saturday 10:00–11:00 and proposal preparation on Sunday 10:00–11:00. The needed feedback is available in its stated window. Two separate weekend hours remain unpromised. The apparent eight hours now contain two hours reserved for recovery, four hours of work and two hours of margin. The split margin cannot cover an operation requiring two continuous hours.
The person notes whether the handover and chosen activity happened, their experience, and whether the planned work produced the specified usable result. Suppose the activities occurred and felt worthwhile, while Wednesday’s correction still needed another half-hour when its window ended at 20:00. The one-hour duration assumed for correction was inadequate: satisfaction with the break cannot make the extra time available. The person retains the enjoyable activity, examines the correction task and uses OPS.10.2 to move or reduce the remaining work within actual available windows. A different observation in which the work fits supports continuing this same arrangement provisionally.
Now an additional household duty occupies Monday 19:00–20:00. The old arrangement no longer supplies that work hour. The person keeps the useful recovery choice where it remains available and reconstructs the remaining three work hours, or moves the missed attempt to a weekend margin if its timing still supports the dependent work. If the needed feedback or order of work cannot fit, they defer the dependent proposal rather than compressing recovery automatically. This changed condition returns to scheduling and commitment, not to a conclusion that the person has lost capability.
OPS.12:6 - Bias-Annotation
People with little control over schedules may find it difficult to report a conflict, while a manager sees only completed output. Use an appropriate channel for their account, drawing on one already given where sufficient. Compare it with the work arrangement; silence is weak evidence that no burden exists.
A productivity measure also favors the group whose work it counts. Follow exception handling and displaced work to the affected recipients before describing the intervention as a gain. Keep unlike observations visible when they support different decisions.
OPS.12:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The intervention concerns actual operating work. | Tasks, affected groups, demand, displaced work and horizon are recoverable. |
| Protected conditions have a valid basis. | Their source, scope and consequence for the proposed arrangement are clear. |
| Evidence has an appropriate reach. | Operating observations, participant accounts and professional conclusions remain distinguishable. |
| Alternatives change the relevant arrangement. | The comparison includes a source-level intervention or explains the specific result needed to create one. |
| The choice respects the protections that apply to each affected group. | Service benefit and transferred burden are visible, and protected conditions are checked before preference. |
| The action can be carried out and revised. | Authority, capability, communication, observations and stop or reversal conditions fit the chosen intervention. |
| An unknown ordinary recovery arrangement has not been assumed. | Where this input matters, the current basis connects actual opportunities, the person’s experience and relevant work results to a provisional commitment, or identifies what remains unresolved. |
OPS.12:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Treat unused calendar hours as available effort. | Recover actual duties, interruptions, required recovery and support for that time; use §4.3.1 when the ordinary recovery arrangement is still unknown. |
| Use feeling better as proof that more work can be promised. | Keep the person’s experience and the actual work result distinct; revise the commitment only at the reach of the evidence. |
| Average away the burden on the exception team. | Compare the material consequences for that team and the service it supplies. |
| Wait for a wellbeing survey before correcting a known breached condition. | Take the permitted operating response from the established condition and seek any missing authority. |
| Offer resilience training while leaving the incompatible assignment in place. | Repair demand, timing, duty or support; add learning work when an actual capability need calls for it. |
| Generalize a successful shift to all people and conditions. | Preserve the observed group and conditions, and obtain further evidence only for the broader intended use. |
OPS.12:9 - Consequences
Human conditions become explicit inputs to an operating choice. The service plan can use qualified relief, reduced demand or a different arrangement before hidden burden appears as delay, rework or loss of support. For personal work with an unknown recovery arrangement, a bounded trial can supply a provisional basis for the next commitment instead of assuming that every empty hour is usable.
A feasible intervention may reduce near-term completions or require additional resources. Participant inquiry and observation also consume time. Focusing on the actual choice and using existing evidence limits that effort while preserving necessary protection.
OPS.12:10 - Rationale
The operating arrangement is a practical point of intervention because it determines what work is admitted, who must handle it and what happens during exceptions. Following those consequences by affected group exposes transfers that an average throughput measure can conceal.
The separation between protection and preference keeps a necessary condition intact while leaving room for legitimate choices about service and resources. Separating observed burden from professional health claims permits useful operating action within the reach of the available evidence.
OPS.12:11 - SoTA-Echoing
The practice question is how to improve service when the proposed change alters people’s working conditions. For this question, the strongest supported starting line changes harmful demands and work arrangements at their source, then evaluates the actual consequences. It improves on an individual-coping response in the PumpWorks case because only a different duty arrangement preserves both recovery and service coverage.
HSE’s guidance on work demands relates workload and work patterns to capability and reported concerns. NIOSH’s hierarchy of controls for Total Worker Health, published in 2024, prioritizes eliminating, substituting or redesigning harmful conditions before relying on education and individual behavior. Sections 4.1–4.3 adapt these moves to a bounded operating decision. The sources do not supply one safe workload threshold for all people, tasks and jurisdictions; the applicable condition must come from the current professional and operating basis.
The serious alternative is a broader organizational intervention where authority, contribution arrangements or recurring staffing allocation cause the conflict. OCE.13’s consequence comparison helps when that is the actual subject. The local operating correction remains appropriate when it can resolve the problem within current authority at lower effort. Escalate the specific unresolved arrangement rather than making every schedule decision depend on organization redesign.
For an unknown ordinary recovery arrangement, two research results limit the operating promise. Albulescu and colleagues’ 2022 meta-analysis of micro-breaks distinguishes reported vigor and fatigue from performance; the overall performance result did not establish a general benefit, and task differences matter. It does not supply a universal break duration or establish an appropriate off-work routine. Kujanpää and Olafsen’s 2024 daily-diary study distinguishes shaping recovery activities from the experiences people report. Its associations among Norwegian knowledge workers, measured by self-report, do not establish that prescribing a particular activity causes recovery or better task performance.
Section 4.3.1 therefore uses accessible activities and personal preferences to construct a bounded operating trial, and keeps experience, actual opportunity and receiving-work results distinct. This is an operating synthesis, not a validated clinical intervention. The serious alternative of reserving a fixed generic break is simpler when its adequacy is already established for the work. When it is unknown, that rule leaves both fit and usable workload assumed. Conversely, a detailed personal experiment is unnecessary when removing an observed schedule conflict already settles the decision. The selected trial gains a revisable basis for the remaining choice at the cost of observation and delayed commitment; it does not promise an optimal regime.
Reopen the selected intervention when a changed population, demand pattern, protection result or better-supported method changes its feasible consequences.
OPS.12:12 - Relations
OPS.5 and OPS.7 supply admission and priority choices whose human consequences may need examination. Use OPS.10 to qualify capacity and OPS.10.2 to place remaining work in the actual available windows. The work and recovery arrangement obtained here supplies conditions for those calculations, not additional hours to count twice. Use OPS.13 to establish a supported service commitment with the authorized parties when that is the receiving need. OPS.14 supplies decision-specific financial consequences, and OPS.15 can provide the necessary operating account.
OPS.18 governs the continuation or recovery action when quality and reliability are at risk. OPS.17 helps reconsider the method whose assumptions created recurring burden. OCE.13 applies when the subject is an organization change; a Human Capability Development method is needed when the unresolved result concerns capability development. HCD.7 and HCD.15 can use the resulting work windows, retained recovery and reconsideration conditions when arranging support or continuing development. A changed available window reopens that arrangement without itself establishing a change in the person’s capability.
FPF C.16 supports measurement whose basis matters to the decision. A.10 keeps evidence reach distinct from the claim being made. A.11.OP helps remove work that has no contribution to the current decision, required assurance or recovery.
OPS.12:End
OPS.13 - Align Commitments, Resources, and Service Outcomes
Status: Stable
OPS.13:1 - Problem frame
Use this when a recipient needs a credible service promise, an existing commitment has become doubtful, or a resource change could alter what the operation can deliver. The question may concern test evidence by Friday, timely patient service, an incident response or accepted outputs from an assisted workflow.
Begin with the result the recipient needs and the promise being considered. Recover its scope and deadline, then test what work, resources and outside results it requires. The first useful result is a supported commitment agreed by the authorized parties, an explicit revision or refusal, or the specific missing input or decision that prevents a supported agreement. An existing commitment can be confirmed under the conditions already in force.
This pattern concerns service commitments within continuing operations. Capacity analysis supplies one input; the promise also depends on acceptance, protected conditions, dependencies and authority. If an individual job fits an already supported service arrangement, use the ordinary admission method. For a disputed engineering, clinical, staffing or safety result, use an applicable qualified determination or refer the remaining question to the responsible provider.
PumpWorks has four ready packages needing eight rig-hours and a six-hour window. Even extra rig access leaves questions about repeats, qualified cover and acceptance. A promise of test completion also has a narrower result than permission to release the controller into the field.
OPS.13:2 - Problem
A target can become a promise in conversation without the parties deciding what is included or whether the operation can support it. Average capacity can hide a missed time window, an unavailable skill or a downstream acceptance delay.
The reverse failure treats any uncertainty as a reason to avoid a useful commitment. The operation needs a promise whose scope and conditions fit the evidence, together with a clear action if those conditions change.
OPS.13:3 - Forces
| Force | Practical tension |
|---|---|
| recipient need and feasible service | The desired result can exceed the available work, resources or authority. |
| nominal capacity and usable windows | Enough total hours can coexist with an impossible sequence or conflicting assignments. |
| efficiency and recovery | Fully loading normal work can consume the reserve needed for an accepted adverse scenario. |
| stable promises and changing conditions | Resource loss or rework can require timely renegotiation while the existing obligation remains in force. |
| useful commitment and uncertainty | A bounded scenario can support a conditional plan; a probability claim needs a matching forecasting basis. |
OPS.13:4 - Solution
OPS.13:4.1 - Recover the service and the parties’ current position
Identify the promising party, recipient, accepted result, eligible demand, start and end events, horizon, required service level and any agreed exceptions. Use the recipient’s service boundary. Waiting that begins before an internal queue is visible can still matter to the promise.
Keep three statements distinguishable:
| Statement | Meaning and required basis |
|---|---|
| Forecast | An estimate of what may happen under stated demand, method and conditions, with uncertainty appropriate to the use. |
| Service objective | The level of service the relevant parties want the operation to achieve. |
| Commitment | An undertaking by identified parties, to an identified recipient, for a result under agreed conditions and authority. |
Recover outstanding commitments, including work already admitted and obligations to other recipients that a new plan would displace. A newly requested target does not silently replace them. When an existing promise is wider than the currently supportable result, keep the unresolved part explicit.
If the desired improvement or its comparison is still arbitrary, use OPS.21 to construct a meaningful aim. An ambition can exceed the current expectation while exposing a worthwhile improvement question. Establish its actual service promise here only after the work, resources and parties support it.
Ask what acceptance requires. A completed test attempt, a passed test with applicable evidence, the customer’s acceptance of that evidence and an authorized product release can occur at different times and under different authorities.
OPS.13:4.2 - Obtain the work, resource and dependency basis
Use the existing work account or trace the required work far enough to identify consequential dependencies and timing. Recover the remaining work on already admitted items, upstream readiness, actual resource windows, needed skills and configurations, setup, handover, recovery and downstream acceptance. Use OPS.10 when the capacity comparison needs development.
Check the resources’ availability for the required time, assignment and use. For provider resources, establish what the offer or existing agreement makes available and which further decision or condition, if any, is required. A person already assigned elsewhere supplies no additional simultaneous capacity merely because their skill is suitable.
Use OPS.12 where the proposed arrangement changes human conditions. Use an applicable professional result for a disputed capability, protection or release claim, or obtain the specific answer still needed. A forecast can state an unresolved condition, while a commitment that depends on it needs either the result or an explicit agreement about that condition.
Keep existing evidence when it fits this demand, configuration and horizon. If a historical service forecast excludes stalled items or concerns a different work mix, inspect that limitation before relying on it. OPS.15 helps reconstruct the eligible population and observation basis.
OPS.13:4.3 - Test the proposed promise at the required level
Start with a transparent load and time-window bound. If known work already exceeds usable resources before the deadline, report that bound. If the recipient needs a feasible route, compare a changed plan or resource arrangement. Where order matters, lay out a feasible sequence with the required resources available together.
Compare the normal case with adverse and changed-condition cases that can alter this service decision. Include relevant repeats, absence, arrival bursts, failed inputs or delayed acceptance. State how each case consumes resources and which result it supports. Reserve time protects a named scenario only while its location, capability and availability fit that scenario.
A finite set of cases establishes what those cases show. A time-plus-probability promise needs a defensible forecast for the eligible population under sufficiently matching conditions. Inspect model assumptions, data coverage, dependence and the consequence of errors. Obtain appropriate forecasting or statistical expertise when that claim exceeds the available method.
Preserve customer classes or conditions whose losses matter separately. A favorable overall service proportion can coexist with an unacceptable result for a protected class. The target and the permitted consequence come from the service decision; the forecast supplies evidence for that decision.
OPS.13:4.4 - Choose and agree a supported response
Consider the supported responses: keep the proposed promise, change its scope or time, change the resource arrangement, refuse the request or obtain a missing result. Compare consequential financial differences with OPS.14 when payment, displaced use or funding changes feasibility or preference.
State the selected result in the parties’ ordinary service terms. Include the conditions on which they rely, the relevant uncertainty and the observation that would require another decision. Make any requested recipient action explicit, such as timely provision of an input or acceptance by a specified date.
Apply the terms already in force to any change in an existing promise. If a proposed revision requires a new decision, obtain it from the authorized parties or report where it stands. Until an applicable revision takes effect, report the existing obligation and its current risk. An internal replan alone cannot discharge it.
A short confirmation in the existing service account can be sufficient. Add detail where the commitment’s consequences require it, such as several recipients, contractual terms or a consequential uncertainty. Qualified legal or commercial work supplies those terms when needed.
OPS.13:4.5 - Observe early enough to act
Choose the observations and review point from how quickly the plan can become infeasible and how long recovery takes. Confirm resource decisions before they are needed. Follow readiness, actual progress, repeats, acceptance and protected conditions where a change would affect the promise.
Work backward from the last time a useful response can start. Include detection, communication and the time to start and complete the remedy. If a separate decision is required, include routing to its holder and the decision time. An already authorized response can start when its trigger and execution conditions hold. Use OPS.10.2 when resource windows or other work affect the remedy’s timing. For a response intended to preserve the promise, the whole detection-to-remedy sequence must fit the remaining usable window. If no such response fits, use the early information to compare another remedy or a service revision. A percentage of reserve consumed can help direct attention; it supplies neither a delay probability nor the resources needed to respond.
Use this response timing to choose a periodic review, an event signal or both. A report of a consequential change can require action before a dashboard threshold is crossed. Where the current account supports continuation and no shared decision is needed, a status meeting need not interrupt the work. Preserve other purposes for meeting, such as learning or resolving an actual disagreement.
Compare the whole observation-and-response arrangement. For periodic review, count the reviews, the conditions that can be missed between them and the resulting latest response. For an event policy, obtain coverage, delivery and acknowledgement behavior, false or repeated notifications, reset behavior and the capacity needed to triage them. Include setup, maintenance and interruption of other work. In a recurring event service, a qualified multiwindow burn-rate policy can distinguish fast serious loss from slower deterioration; it needs a meaningful eligible-event population and service-specific parameters. A sparse discrete delivery may be better served by a direct readiness check. Retain the cheaper adequate policy, and reopen it when alert load or response availability defeats its timing.
When the basis changes, calculate the affected service consequence and inform the responsible parties in time for any remaining choice. If that window has closed, report the consequence and identify any remedy still available. Preserve what can still be performed under existing authority. Use observed delivery and acceptance to determine which promised results were fulfilled, and retain any remaining obligation. A changed forecast records the new outlook.
OPS.13:5 - Archetypal Grounding
OPS.13:5.1 - PumpWorks states what the rig plan supports
This constructed case concerns four ready packages requiring two consecutive rig-hours each, including normal setup. Rig access currently covers hours 0–6. Hours 6–8 are reserved for another use, and their owner can make a separate access decision that accounts for displacement.
The normal case has no repeat. In the adverse case, exactly one planned package needs one immediately available two-hour repeat and then passes; all other planned packages pass first time. The repeat need is known when its first attempt ends. Test permission and configuration are current. The stated schedules also require qualified coverage and any handover to fit within the available plan.
| Plan | Normal case | One-repeat case | Service consequence |
|---|---|---|---|
| Six hours; plan two packages and retain two hours for the repeat. | Two completions use four hours. | Two completions plus the repeat use six hours. | Two completions fit both stated cases. |
| Six hours; plan three packages with no reserve. | Three completions use six hours. | Three completions plus the repeat require eight hours. | The three-completion promise is unsupported for the stated adverse case. |
| Eight hours; plan three packages and retain two hours for the repeat. | Three completions use six hours. | Three completions plus the repeat use eight hours. | Three completions fit both cases if extra access and coverage are authorized. |
| Ten hours; plan four packages and retain two hours for the repeat. | Four completions use eight hours. | Four completions plus the repeat use ten hours. | This requires a further resource arrangement; it is not supplied by the two-hour extension. |
Reserve remains available for the repeat whenever it becomes necessary. Since all packages are ready, the repeat can follow its failed attempt without another dependency delay. A longer repeat, more than one repeat, later permission or lost access reopens these schedules.
OPS.12’s staffing comparison requires qualified relief for an extension that would otherwise consume the original operator’s protected recovery and incident coverage. The responsible parties must also settle the extension’s payment and funding. These inputs determine whether the eight-hour alternative is available for commitment.
Suppose the test-service authority and customer accept the two-case basis, the three-package scope and the evidence required for a completed test package. Once the additional access, relief and other prerequisites are confirmed, they can agree the three-completion service under those stated conditions. Before confirmation, that result remains a proposal. If only the six-hour arrangement is available, the supported proposal covers two completions under the same adverse-case requirement.
The calculation supplies no probability of the adverse event and no guarantee beyond its conditions. A customer requiring a quantified delivery probability needs a matching forecasting basis. An existing four-completion promise remains a live obligation until a revision takes effect under the governing terms.
OPS.13:5.2 - A test promise and a field-release promise differ
Field release of candidate R42 requires applicable T9 test evidence, the result of safety question S19 and the authorized release decision. A test-service commitment can establish when the agreed test result should be available. Its acceptance criteria concern that test service.
If S19 is still unresolved or T9 evidence does not apply to the configuration proposed for release, the release practitioner lacks a result needed for the wider promise. The operating response is to state the dependency and seek the particular evidence, safety result or decision still needed. The test work can continue where its laboratory permission and other conditions allow it.
If an earlier commitment promised field release, agreeing a narrower test service does not close it. The recipient needs an explicit revision, refusal or unresolved release position from the parties authorized to make that decision.
OPS.13:5.3 - Hospital room capacity and staffing support different counts
In a constructed routine service, two rooms are each available for four hours. One qualified team is available for four hours and each planned visit uses thirty minutes of that team’s time, including the required turnover work. The responsible clinical practitioners supply the eligible cases and the planning durations. Two visits are already committed.
Eight room-hours would appear to allow sixteen visits. The qualified-team bound allows eight in total and at most six additional visits under the normal assumptions. A supplied adverse scenario reserves one team-hour for an urgent case, reducing the plan to six routine visits in total and four additional visits.
The coordinator can propose four additional routine visits under both stated cases, obtain another qualified arrangement, or offer later appointments with the affected recipients’ agreement. A room booking alone cannot support the larger promise. The service decision preserves clinical priority and the team’s protected conditions; a changed clinical need can reopen the plan.
OPS.13:5.4 - An assisted service promises a review result
An assisted production service can generate sixty drafts per day. Each accepted output requires its own review decision, and staffing supports six such decisions per day. In the recent matching work mix, those reviews yielded four to six accepted outputs. A recipient requests ten accepted outputs tomorrow.
Even the normal review bound excludes ten accepted outputs from that staffing arrangement. Increasing generation cannot resolve the deficit. The service provider can propose a later accepted-output target, obtain qualified acceptance capacity, or offer six review decisions if that narrower result is useful to the recipient. The recent four-to-six range describes those observations; it supplies no stated probability for tomorrow.
If the recipient accepts the review service, the parties specify what a completed review includes and how rejected or revised drafts continue. They preserve the original accepted-output request as refused, revised or unresolved rather than counting review completion as acceptance.
OPS.13:5.5 - A review must leave time for the response
An accepted report is due at hour fourteen. Once its validated input is available, analysis needs three uninterrupted hours and release needs one more. These operations and their resources are available in that order until fourteen. The latest usable input is therefore hour ten.
At hour seven, an input failure occurs. A supplied recovery method needs two hours after authorization; its qualified performer and resources are available immediately. Authorization must occur by eight if recovery is to supply the input by ten. The next routine review at nine is too late: even immediate authorization then gives input at eleven, leaving analysis until fourteen and requiring release from fourteen to fifteen, outside its available window.
Instead, suppose detection takes at most fifteen minutes and conveying the result and deciding together take another fifteen. Recovery can start by 7.5, finish by 9.5, and be followed by analysis until 12.5 and release until 13.5. The response preserves half an hour before the deadline under these stated bounds. The signal needs to reach whoever can authorize recovery.
Now change one fact: the recovery resource cannot start before ten. Recovery could supply input at twelve, but the three-hour analysis would already overrun its availability until fourteen; release would require a further hour. Sixteen is only the arithmetic end if those windows were extended, not a supported delivery time. Faster notification alone cannot restore the promise. Obtain a different workable remedy or an agreed service revision. The earlier calculation remains valid only with its earlier availability premise.
OPS.13:5.6 - Compare the cost of obtaining a usable warning
Keep :5.5’s report, hour-14 deadline, two-hour recovery and four hours after input recovery. Consider ten daily repetitions with the same qualified resource windows. In this bounded planning comparison, an input failure is persistent until repaired and can arise only between 7 and 7.5. One readiness inspection completed at 7.5 finds it; communication and authorization then take at most fifteen minutes. Recovery starts by 7.75 and the report finishes by 13.75. This periodic policy is sufficient for these supplied conditions; detecting every failure as quickly as an event mechanism could is unnecessary for this promise.
Each inspection costs three staff-minutes, or thirty over ten days. A capable alternative uses the service’s existing event mechanism, checked to cover these failures and deliver an actionable warning within five minutes, with acknowledgement and escalation. Its adaptation takes 120 staff-minutes once, with qualified preparation time available before the ten-day service window; health/coverage checks take two per day. The supplied comparison trace also contains three nonactionable or repeated notifications per day after the policy’s normal grouping/reset handling, at four minutes each to triage. In that trace, the notifications are separated and the true-incident decision maker remains available. Its additional observation burden is therefore 120 + 10 × (2 + 12) = 260 minutes. The same true-incident decision and recovery work is required under both policies and is counted in their resource plans, not treated as a saving. Retain periodic inspection for this sparse service.
Now the same service undertakes twelve independently checked reports per day with staggered windows. Qualified analysis, recovery and release resources have been supplied for that population; verify that supply before relying on the increased volume. Manual inspection still needs three minutes per report: 36 per day. A qualified shared event arrangement retains the five-minute delivery bound, combined two-minute daily health check and the stated twelve-minute triage burden across that population. Over ten days, 360 observation minutes compare with 260, including the event policy’s setup. With only thirty daily minutes available for these observation tasks, the shared event policy is the usable candidate; staffing and protected response work must remain feasible as well. A burn-rate policy is a serious further option only if the promised service and its eligible-event volume support a loss-rate objective. A failed discrete report must not disappear in a favorable aggregate.
Test the changed condition that defeats this choice. Three spurious alerts queued ahead of a true one can consume twelve minutes; five-minute delivery plus twelve-minute triage wait plus fifteen-minute communication/decision gives 32 minutes. For a failure at 7.5, a 32-minute response reaches authorization at hour 8 plus two minutes, too late for the original remedy. A response taking 3 + 12 + 10 = 25 minutes meets the cutoff. The queued policy therefore loses the guarantee. The operating owner needs an effective priority/triage arrangement, additional cover, an earlier direct check or another service decision. Verify the actual response queue and affected report, retain unrelated reports whose basis still holds, and use the existing promise-revision authority if no workable response remains.
OPS.13:6 - Bias-Annotation
Urgency and commercial pressure can make a desired date feel like an established promise. Check what the parties have agreed, using the agreement already in force or confirming the result and conditions with them when needed.
Resource counts also favor what is easy to see: rooms, machines or generated drafts. Follow the binding skill, acceptance and time conditions before describing the service as feasible. Preserve the interests of recipients whose existing work would be displaced.
OPS.13:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The service has a recoverable meaning. | Parties, recipient, eligible demand, accepted result, time basis, level and conditions are clear. |
| Existing obligations remain visible. | Affected commitments and the authority to revise them can be identified. |
| Capacity is usable for this service. | Resources, capability, windows, sequence, dependencies and protected conditions support the plan. |
| Uncertainty matches the claim. | Scenario conclusions stay within their cases; probability claims have an appropriate forecasting basis. |
| The result is an actual decision or a clear gap. | Acceptance, refusal, requested revision or unresolved input is distinguished from the internal plan. |
| Change can be handled in time. | The observation and response times support the proposed remedy, or the result identifies a missed window and the remaining choices. |
OPS.13:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Turn a historical service forecast into a promise without agreement. | Recover the recipient, conditions and commitment authority, then test the receiving use. |
| Add nominal hours while the required skill is unavailable. | Use the time in which all required resources and conditions obtain together. |
| Count reserve twice, as both normal work capacity and protection against repeats. | Show the sequence and load for the actual normal and adverse cases. |
| Treat a planning update as release from an existing promise. | Apply the terms of revision, use or obtain any required decision, and retain outstanding obligations. |
| Count a narrower result as the promised outcome. | Keep test, customer acceptance, review decision and field release distinct wherever the service depends on them. |
OPS.13:9 - Consequences
The responsible parties can make a useful promise with explicit grounds, or offer a concrete alternative that the recipient can decide. Capacity, protected human conditions and acceptance become parts of one service choice.
The supported promise may be narrower, later or more expensive than the requested target. Some uncertainty can remain even after a sound decision. Timely observation and agreed responses make that uncertainty manageable without presenting the forecast as certainty.
OPS.13:10 - Rationale
A resource calculation answers what work can fit under its assumptions. A commitment also establishes who undertakes what for whom. Connecting these claims preserves both the practical scheduling evidence and the parties’ decision.
Starting with a simple bound prevents needless forecasting when the plan is already impossible. Adding scenario or statistical depth only for the required claim preserves an affordable first result while allowing stronger assurance where the consequence needs it.
OPS.13:11 - SoTA-Echoing
The practice question is how to make service commitments under uncertain demand and constrained resources. A workable comparison combines explicit work and time boundaries, a forecast appropriate to the claim, and a service decision by the responsible parties. Compared with a plan based on average utilization or an unqualified target, it exposes the answer-changing deficits shown by PumpWorks and the hospital case.
The Kanban Guide 2025.5 describes a service-level expectation through elapsed time and probability, informed by the relevant cycle-time history. Section 4.3 adopts that explicit forecast shape when a probabilistic claim is needed. It also asks whether the observed population and operating conditions fit the new promise. The guide’s workflow forecast does not itself provide resource authority or customer agreement.
The SRE Workbook’s service-objective guidance (2018) starts from user-relevant service behavior and distinguishes the intended indicator from how it is measured. Sections 4.1 and 4.2 adapt that distinction to the promised result, eligibility and acceptance evidence. This is a useful alternative to a resource-only account, while a software-service indicator remains insufficient for a clinical or engineering acceptance decision.
Steve Tendon, The Book of TameFlow (2022), printed pp. 215-220 and 259-269, connects reserve consumption, progress and management attention. Adopt its use of changing conditions to focus intervention, including information that arrives before a formal alarm. Section 4.5 adds the time and resource construction that tests whether a response can preserve the promise and exposes the need for another remedy or a revised agreement. The book’s heuristic conversion from a duration fraction to a delivery probability (p. 212), and its use of mean flow time as the 50th-percentile cutoff (p. 220), do not establish those probabilities. A probabilistic promise needs the applicable distribution; an alarm needs a workable response. Retain periodic meetings where they perform another needed function. Reconsider the observation policy when detection, authority, remedy duration or resource availability changes.
The SRE Workbook’s alerting comparison, chapter 5, supplies a capable alternative: choose for detection, precision, recall and reset behavior, using several windows/burn rates when the service signal supports them. It also exposes low-traffic and response-time limits. Sections 4.5 and 5.6 adapt that whole-choice reasoning to a discrete promise and count the work of handling notifications and the capacity available for response. They retain cheaper periodic inspection when it is adequate.
For a small known job set, a feasible sequence and explicit adverse case can answer the commitment question at lower effort than a stochastic model. PumpWorks uses that branch. A changed demand distribution, recurring service-level claim or consequential tail risk can justify the stronger forecasting work. Reopen the basis when work mix, windows, resources, acceptance or the promised result changes.
OPS.13:12 - Relations
OPS.5 guides admission under an existing service arrangement, and OPS.7 guides decisions about aging work and commitments that need attention. Use OPS.10 to qualify capacity, OPS.12 to compare human consequences and OPS.14 to compare operating and financial alternatives relevant to the promise.
OPS.15 helps construct an account whose event population and time basis support the service claim. OPS.18 guides the operating response to quality and reliability evidence. OPS.17 helps select or refresh the operating method when its assumptions no longer support the service.
FPF A.10 governs the fit between evidence and the claim relied on. C.16 supports the exact measure and uncertainty where those matter, while A.11.OP limits additional analysis to what can change the decision or supply required assurance or recovery.
OPS.13:End
Part VIII — Compare Operating Consequences and Build Useful Accounts
OPS.14 - Relate Throughput, Cash, and Operating Consequences
Status: Stable
OPS.14:1 - Problem frame
Use this when an operating alternative appears worthwhile because it raises output, lowers unit cost, releases capacity or brings money sooner. Examples include buying an extra resource window, changing a service mix, deferring work or automating preparation.
Begin with the actual alternatives and the horizon of the decision. Ask which accepted service, resource use, payments and receipts differ. The first useful result identifies the feasible alternatives, their differences and any missing financial or resource result. The responsible party can use that comparison to choose, accept a trade-off or retain the current arrangement.
This pattern governs the operating and financial consequences of a bounded operations choice. Use financial statements, investment appraisals or funding decisions supplied by qualified practitioners when the comparison needs them. If the comparison depends on a missing result, seek it from its responsible provider or state which conclusion remains conditional. An operating throughput calculation cannot settle them by itself.
In PumpWorks, completing a third test package now yields positive eventual net cash. Deferring the same package can yield more net cash over the same horizon, and the immediate option can still lack money for its advance payments. The comparison must make all three statements visible.
OPS.14:2 - Problem
A local efficiency measure can hide what the operation gains or loses. More completed attempts may create no accepted output; accepted output may have no paying demand; recognized revenue may arrive before cash; and lower allocated cost per unit may leave every actual payment unchanged.
Comparing only one attractive option compounds the problem. Its positive net cash gives no answer about the alternative, while a short horizon can make delayed receipts disappear from view.
OPS.14:3 - Forces
| Force | Practical tension |
|---|---|
| local output and accepted value | A faster resource can create unfinished work, rework or output the recipient does not accept. |
| resource contribution and complete feasibility | A useful contribution-per-hour ranking can fail when jobs are indivisible or several resources are scarce. |
| eventual net cash and funding | A positive result can require payments before the operation has authority or cash to make them. |
| current horizon and later consequences | A short decision window can obscure delayed receipts, commitments and recurring costs. |
| money and other operating conditions | Cash consequences matter within the service, human and quality conditions governing the choice. |
OPS.14:4 - Solution
OPS.14:4.1 - Name the alternatives and the operating change
State the decision, recipient of the comparison, alternatives and horizon. Include current practice or deferral when either is a real option. Establish which alternatives satisfy applicable service, protection and authority conditions; use OPS.12 and OPS.13 when their contribution is needed to establish or change those conditions.
Describe the operational difference: what accepted result changes, which demand it serves, what work and resources it requires, which work is delayed or displaced, and what happens after failure. Use a schedule or bounded scenarios when timing matters. Keep unresolved assumptions visible.
Follow the proposed gain to its receiving use. Saving preparation time can matter because it changes a payment, frees a resource for another accepted job or protects service. Name the actual consequence before attaching a monetary value to the saved time.
OPS.14:4.2 - Choose quantities that answer the decision
Keep the accounting basis with the quantity being compared.
| Quantity | What the practitioner needs to recover |
|---|---|
| Physical throughput | The physical output counted, its unit and period, keeping completed service results separate from the attempts needed to obtain them. |
| Monetary throughput or contribution | The selected model of proceeds less specified variable costs, with its cost assumptions and demand basis. |
| Recognized revenue or accounting profit | The accounting period and recognition rules supplied for that purpose. |
| Cash receipts and payments | Amounts received or paid for a historical account, or amounts expected to enter or leave under each alternative, with their timing, conditions and authority. |
| Released resource capacity | The usable time or capability released and the next service or avoided payment that could use it. |
Choose the quantities that support the comparison, including any common amount needed to establish whether an alternative can be funded. A throughput-accounting model can be useful for a short-horizon product or service mix when one resource is limiting and its assumptions fit. The common direct-material treatment presumes that other costs remain largely fixed over that horizon. Per-use cloud charges, contracted labor or changed support costs can defeat that presumption.
For a suitable model, compare contribution per unit of the scarce resource together with demand limits. With coupled resources, indivisible jobs, sequencing requirements or binding commitments, obtain the feasible schedule or corresponding optimization result. A ranking alone does not determine the feasible mix.
OPS.14:4.3 - Build the incremental financial comparison
For each alternative, identify future payments and receipts that differ because of the choice. State amount, time and the condition that produces the flow. The same unchanged amount in both alternatives cancels in their difference; keep it elsewhere if the receiving account needs the whole operation’s cash position.
Inspect avoidability. A historical payment is not saved by declining future work. An allocated share of rent may remain unchanged, whereas an additional contracted shift or per-use charge can be avoidable. A cost that is fixed this week can become avoidable at a later renewal, so use the period over which the decision can affect that payment.
Include displaced use when it is real. Identify the best relevant foregone alternative and its consequence, or state the qualified premise that no material contribution is displaced. Count that loss once. If the cash comparison already includes the missing receipts and avoided costs of displaced work, do not subtract the same foregone contribution again as an extra opportunity cost.
Connect receipts to demand, delivered service, acceptance and payment conditions. Consider adverse cases that could affect the choice or the conditions on which it rests, such as repeat work, delayed acceptance, nonpayment or a lost resource window. A claimed receipt needs its stated basis even when its arithmetic is simple.
When a reported contribution deducts labor that will still be paid after redeployment, recover the receipts and genuinely avoided payments behind it before using it as the foregone amount. Otherwise the comparison can treat a retained salary as if it were saved. A competent relevant-cost account already makes this correction; reuse it rather than adding another opportunity-cost line.
OPS.14:4.4 - Check timing, funding and horizon effects
Calculate each alternative’s net cash within the horizon, then the difference between alternatives. State the direction: completing now minus deferring, for example. Keep this difference distinct from the net cash of either option.
Lay out consequential advance payments and later receipts. Determine whether available authorized funds cover each payment when due, taking prior payments, receipt dates and other obligations on the same funds into account. A favorable final balance can coexist with an earlier funding gap.
Show material flows just outside the horizon and test whether extending it changes the conclusion. A timing advantage can be useful for the receiving cash decision; describe its duration and effect. For longer-lived assets, financing, taxes, discounting or statutory accounting, use an applicable qualified result or identify the remaining input needed for that use. The simple undiscounted comparison below does not answer those questions.
A fixed annual allocation can be an inadequate description of current need. Refresh the operating forecast and determine whether existing resource or funding authority still covers the proposed use. Seek a further decision if needed. A revised forecast itself grants no spending authority.
OPS.14:4.5 - Return the choice, trade-off or exact missing result
Present the feasible alternatives with the consequential service, resource, human, quality and financial differences. State any assumption that materially affects the ranking, timing or feasibility, and what would settle a remaining question.
If one alternative is better on the receiving decision’s criteria, recommend it with that basis. If earlier service costs more, make the price of that service visible to the authorized decision maker. Preserve mandatory conditions before comparing preferences.
A short account of the alternatives and their consequences can suffice. Use OPS.15 when the source events or definitions need repair. After action, compare actual flows and operating results with the assumptions needed for continuation; reopen the affected method or service decision if they change.
OPS.14:5 - Archetypal Grounding
OPS.14:5.1 - PumpWorks compares the same third package on one horizon
This constructed comparison runs from the start of month 1 through the end of month 2. Four test packages are ready. Each needs two rig-hours. In the supplied adverse case, one of the two packages retained in both alternatives needs one immediately available two-hour repeat and then passes. The third package passes first time in either alternative.
The two retained packages have the same costs and receipts in both alternatives, so they cancel in this incremental comparison. Their work uses the current six-hour window, including the repeat. The decision concerns when to complete the third package.
The customer permits either date below. It pays 900 currency units at the end of month 2 if the third package’s evidence meets the stated test-service acceptance criteria by day 20 of that month. Laboratory permission is supplied. Customer acceptance of this test service has its own scope; R42’s field release still requires applicable T9 evidence, S19’s safety result and release authority.
| Alternative | Work and acceptance | Payments that differ | Receipt | Net cash through month 2 |
|---|---|---|---|---|
| Complete now. | Extend from six to eight rig-hours in month 1; complete the two retained packages, their repeat and the third package. The third package’s evidence is accepted in month 1. | Pay 300 for extra rig access, 400 for qualified relief and 100 for consumables before the extra work in month 1: 800 total. | Receive 900 at the end of month 2. | 900 − 800 = +100. |
| Defer the third package. | Complete the two retained packages and repeat in the six-hour window. Use a confirmed two-hour spare slot on day 10 of month 2 for the third package; its evidence is accepted by day 20. | Pay 100 for consumables before the deferred test. The supplied resource account confirms that already-paid rig/staff arrangements stay unchanged and the spare slot displaces no accepted job or other foregone contribution. | Receive 900 at the end of month 2. | 900 − 100 = +800. |
Completing now minus deferring gives +100 − (+800) = −700 currency units over the stated horizon. Earlier test service costs 700 more under these assumptions. The financial comparison favors deferral; the responsible practitioner may still value earlier service enough to justify that cost if the governing conditions allow the choice.
The immediate option needs 800 before any receipt. Only 500 is currently available under the supplied cash allowance, so this option has a 300 funding gap. Its eventual +100 net cash does not fill that earlier gap. Report the gap. Proceeding with the immediate option requires additional authorized funding; the decision maker can also select a funded alternative. The deferred option still requires its 100 payment when due.
Qualified relief preserves the original operator’s recovery and incident coverage in the proposed extension. Its 400 payment is part of making that alternative feasible. The resource owner’s access and displaced-use decision is also required. Paying the fee cannot supply either the staffing result or permission to release the product.
OPS.14:5.2 - A moved receipt changes the short-horizon result
Now suppose the deferred package misses the month-2 acceptance cutoff and its 900 receipt moves to month 3. Keep every other fact the same.
| Comparison horizon | Complete now | Defer with month-3 receipt | Now minus defer |
|---|---|---|---|
| Start of month 1 through end of month 2 | +100 | −100 | +200 |
| Start of month 1 through end of month 3 | +100 | +800 | −700 |
The +200 difference is a cash-timing advantage inside the shorter horizon. The account shows the excluded 900 receipt and the cost of completing earlier. Extending the horizon reveals the original −700 difference; no lasting gain was created by ending the account sooner.
If the immediate package instead misses acceptance or payment, its 900 receipt also moves or disappears while the spent 800 remains. The practitioner therefore checks the acceptance and payment premise for both alternatives. A new failure or financing consequence requires a changed comparison rather than reuse of these totals.
OPS.14:5.3 - One resource can still require a discrete choice
Suppose two indivisible jobs compete for three usable machine-hours. Under the stated contribution model, job A yields 70 currency units and needs two hours; job B yields 100 and needs three. Demand exists for one of each, both are otherwise feasible, and partial jobs have no accepted result.
A has the higher ratio: 35 per hour versus approximately 33.33. Choosing A leaves one unusable hour and yields 70. Choosing B yields 100. Of the two feasible whole jobs, B earns the larger contribution.
With several scarce resources or service obligations, the practitioner uses the appropriate scheduling or optimization method. This small example establishes the effect of indivisibility.
OPS.14:5.4 - Hospital and assisted-service choices retain their purpose
A hospital can compare the payments required for two qualified staffing arrangements after the responsible practitioners establish clinical priority, care requirements and protected conditions. If one arrangement violates a required condition, a lower payment cannot make it feasible. If both satisfy the service, their resource and financial consequences can inform the operating choice. The comparison supports the hospital’s stated service purpose.
Consider one constructed working day with four accepted outputs due. Both options produce sixty charged drafts for the same demand under unchanged human and acceptance conditions; the salaried team completes six individual review decisions. All payments use the same currency.
| Generator | Generation payment | Additional rework payment | Accepted / rejected after six reviews |
|---|---|---|---|
| Current | 60 at 1 per draft | 0 | 4 / 2 |
| Alternative | 30 at 0.5 per draft | 10 | 2 / 4 |
Both leave fifty-four drafts unreviewed; rejected work and the paid rework remain unaccepted. The same 240 salary is paid today, with no other payment or receipt. Total payments are 300 versus 280: the alternative saves 20 cash, while payments per output accepted that day rise from 75 to 140. These are daily payment ratios; they do not close the unfinished work. The unchanged salary yields no cash saving, and qualified review capacity remains six decisions per day. Retain the current arrangement for the four due outputs under confirmed funding and decision authority; qualify any later generator or service change before relying on it.
OPS.14:5.5 - The deferred slot displaces an accepted job
Change :5.1’s no-displacement premise. The month-2 slot is now the only available way to complete previously committed job J on time. J would bring 1,100 at the end of month 2 and needs 200 of avoidable consumables before its service. The same 300 salary is paid in both alternatives, even if J is not performed. That unchanged payment has separate reserved funding; the 500 allowance in :5.1 remains available for the extension’s differing payments. No other contribution uses the slot. All figures use the earlier common horizon and currency.
Completing the third package now leaves the slot for J. Deferring it uses that slot and loses J’s receipt while avoiding J’s 200 consumables. For this comparison, J’s recipient has authorized cancellation without penalty if the slot is withdrawn; without that permission, the deferral is not an admissible choice merely because its cash total is attractive. Preserve the actual commitment until its agreed cancellation takes effect.
| Cash component through month 2 | Complete the third package now; perform J | Defer the third package; cancel J |
|---|---|---|
| Third package, unchanged from :5.1 | +100 | +800 |
| J receipt less its avoidable consumables | 1,100 − 200 = +900 | 0 |
| Salary retained in both alternatives | −300 | −300 |
| Total for these components | +700 | +500 |
Now minus defer is +200, so the financial preference reverses in favor of completing now, conditional on feasible service and funding. The same answer is the earlier −700 difference plus 900 of foregone J cash. A reported J contribution of 600 that already deducted the retained salary would understate the displacement by 300. The table includes J’s lost receipt and avoided consumables once; subtracting a further 900 “opportunity cost” would count the same loss twice.
The earlier 300 advance-funding gap for the immediate option remains. J’s later 200 payment also needs funds when due; the month-end receipts do not pre-fund it. If funding or cancellation authority is absent, return that constraint before acting. If J’s receipt is only 800 with the same 200 avoidable payment, its foregone cash is 600 and now minus defer becomes −100: the financial preference returns to deferral. This is a changed demand/payment premise, not a salary saving.
OPS.14:6 - Bias-Annotation
An attractive option is easier to defend when its comparator is absent. Describe the same service result, horizon and changed flows for every serious alternative, including deferral where it is real.
A budget category or unit-cost display can also dominate attention because it is already reported. Recover the amount that actually changes and the authority needed to act. Show a material delayed receipt even when it lies outside the chosen reporting window.
OPS.14:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The comparison has a real choice. | Alternatives, receiving decision, service result and horizon are explicit. |
| Quantities retain their meaning. | Physical output, contribution, accounting amounts, cash and released capacity have their own units and basis. |
| Operating feasibility is preserved. | For each alternative, the account states whether demand, resource windows, human conditions, acceptance, rework and displacement support it, or what remains unknown. |
| The incremental account is causal enough for the choice. | Changed payments and receipts follow from stated actions and conditions; unchanged amounts cancel only in the difference. |
| Timing is visible. | Advance payments, receipts, funding gaps and material flows outside the horizon are shown. |
| The result supports the actual decision. | The preference or trade-off, any material uncertainty or authority gap, and the conditions for reconsideration can be recovered. |
OPS.14:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Recommend an option because its own net cash is positive. | Calculate the same result for the actual alternatives over a common horizon. |
| Call reduced allocated cost an avoidable payment. | Recover what payment changes, when it changes and why. |
| Rank indivisible jobs only by contribution per hour. | Compare feasible whole-job combinations or obtain the needed scheduling result. |
| Subtract displaced contribution twice. | Trace whether the lost receipts and avoided costs already appear in the comparison. |
| Use an eventual receipt to justify an unfunded advance payment. | Identify the amount and authority required before work starts. |
| Treat a receipt outside the horizon as permanently lost. | Show its expected date and test a horizon adequate to the receiving decision. |
OPS.14:9 - Consequences
The practitioner can explain why an operating alternative changes service, resources or money and what premise could reverse the choice. A worthwhile release of capacity remains visible even when it does not immediately reduce payments.
The comparison can require information from resource owners, customers or finance. A wider horizon may need a different model. Keeping the account bounded to the live decision reduces unnecessary work while preserving material later consequences.
OPS.14:10 - Rationale
Accepted operating results, accounting recognition and cash occur through different events and rules. Following the actual consequences between them prevents a local production measure from standing in for the receiving financial decision.
Comparing alternatives on one basis makes an incremental claim intelligible. Separating final net cash from timing and funding then preserves the conditions under which the chosen work can actually begin.
OPS.14:11 - SoTA-Echoing
The practice question is how to choose operating work when output, scarce resources and financial timing interact. Compare future differences between the alternatives and identify any condition, such as timely funding, that must hold before an option can be used. Use a constrained-throughput model when its assumptions fit. The dated comparison explains both PumpWorks’ cheaper deferred service and its immediate funding gap.
ACCA’s treatment of relevant costs supplies the future incremental cash and opportunity-cost reasoning used in sections 4.3–4.4. PumpWorks adapts that reasoning to explicit acceptance dates and two alternatives. Section 5.5 additionally works the source’s redeployed-labor distinction: recover the retained payment before using a reported contribution, and count displaced cash once. The instructional model does not supply tax, financing permission, discounting or statutory recognition rules.
ACCA’s throughput-accounting treatment contributes the scarce-resource mix question under short-horizon cost assumptions. Section 4.2 retains the useful contribution comparison while the whole-job case shows a limit of using the ratio as a decision rule. Variable cloud or labor payments require the actual cost model.
The Beyond Budgeting principles, in a 2020-named handout citing Hope, Bunce and Röösli’s 2011 work, support resource decisions responsive to current need. Section 4.4 adapts that move when a fixed allocation no longer describes the operating situation. It preserves the separate funding decision; a refreshed forecast is not authorization.
For a money-bearing choice with significant long-term or financing effects, a qualified investment or financial model is the stronger alternative to this simple account. Use it when those consequences matter to the choice or the grounds for it. Reopen the comparison when demand, avoidability, acceptance, displacement, funding or horizon changes.
OPS.14:12 - Relations
OPS.10 helps establish the feasible resource alternatives. OPS.12 supplies a method for comparing human conditions, and OPS.13 guides the commitment and resource decisions that can make an alternative usable. OPS.15 helps construct the operating account where events or definitions need reconciliation.
OPS.18 guides action when quality or reliability changes the expected result or recovery work. OPS.17 helps select a different operating or financial method when the current model’s assumptions fail. Use the relevant qualified finance or accounting result for investment, financing, tax or statutory use.
FPF C.16 preserves comparison characteristics, units and model assumptions; A.10 keeps their evidence reach explicit. A.11.OP limits account detail to what contributes to the decision, required assurance or recovery.
OPS.14:End
OPS.15 - Build a Decision-Specific Operating Account
Status: Stable
OPS.15:1 - Problem frame
Use this when you need an account that answers an operating question. Figures may disagree, a denominator may exclude unfinished work, or a dashboard may combine events from different services. Establish what the observations support for the requested claim or decision.
Name the decision or operating claim the account must support. Identify its subject, population and time basis. Give the selected observations, their meaning and limits, and the conclusion they support. A short table, an existing record or a view in the current tool can suffice.
This pattern governs the construction and maintenance of that account within continuing operations. The responsible practitioner uses the account to make any operating decision required. Use an adequate existing account directly when its meaning and evidence fit. Statistical estimation, causal investigation or a professional acceptance judgment needs its own method when the receiving claim requires it.
Suppose forty service requests have all reached their due dates. Twenty-seven finished on time, three finished late and ten remain open. Reporting 27 out of 30 completed requests as “90% on time” leaves the overdue open work out of the service judgment. The due-request account shows 27 out of 40, or 67.5%. Recovering the question changes which of these true calculations is useful.
OPS.15:2 - Problem
Available records often reflect the tool that generated them. A board counts matters, a rig log counts attempts, an invoice records an amount due and a payment account records a receipt. Combining them without their subject and event meanings can produce an apparently precise but unusable conclusion.
More collection can increase reporting effort without settling the question. Identify the evidence the requested conclusion or choice needs, together with any separate assurance or recovery use.
OPS.15:3 - Forces
| Force | Practical tension |
|---|---|
| useful summary and retained meaning | A compact number can hide the population, exceptions or source loss that determines its use. |
| common subjects and unlike views | Several readers can need different accounts of the same operation. |
| current information and collection cost | Frequent refresh is useful when changes can affect the receiving result soon enough to matter. |
| comparable values and changed conditions | A new definition, work mix or measurement method can make old and new values incomparable. |
| sufficient decision evidence and unresolved detail | A bound can settle the choice even while some observations remain unknown. |
OPS.15:4 - Solution
OPS.15:4.1 - Identify the receiving question
Name who will use the account, the decision or claim at issue, and when the answer is needed. State the fact or comparison that could settle it. “Should we retain this service promise?”, “Did the due-date cohort meet its objective?” and “Which rig should receive the next ready package?” need different evidence.
Identify the operating subject and the result of concern. For each needed claim, recover its population: requests, test attempts, accepted packages, shifts, incidents or another explicitly defined set. Preserve the service boundary relevant to the recipient, including work that waits before entering the visible internal workflow.
Inspect existing accounts and observations before adding collection. Reuse one whose subject, conditions, time and definition fit. If a current qualified result already supports the requested claim or action, return it with its limit.
OPS.15:4.2 - Define the claims and measures
For each quantity needed for the account, make its meaning recoverable. A ratio needs its numerator, denominator and eligibility rule. A duration needs its start, end, unit and treatment of unfinished cases. A count needs its event or result identity, observation window and duplication rule.
Choose the interpretation with the receiving use. Completed-only cycle time may describe completed work; it cannot by itself describe how all admitted work is progressing. A due-date cohort contains work whose required completion date falls within the selected period. Open work whose deadline has passed differs from open work whose deadline lies in the future.
Use the following questions only where their answers affect the claim:
| Question | Consequence for the account |
|---|---|
| What belongs to the population? | Inclusion, exclusion, cancellations, diverted work and service classes change the denominator or reach. |
| When is the event observed? | Clock origin, cutoff, timezone where material, and reporting delay change the time claim. |
| What constitutes completion or acceptance? | Attempts, completed work, accepted service and a later release can be counted differently. |
| How is the value obtained? | Source, measurement rule, sampling and missing data determine what the number supports. |
| Can the values be compared? | Changed definitions, methods, mix or conditions may require recalculation on a common basis. |
Keep uncertainty explicit when it affects the claim or decision. Use an interval, separate unknown category or qualified estimate appropriate to the claim. A precise display does not remove missing observations.
OPS.15:4.3 - Reconcile source events and subjects
Trace the quantities to the events or observations that establish them. Recover which request, case, configuration, test, resource and result an event concerns. One event can concern several subjects, and one subject can have many events. Use their actual relationships when joining accounts. If the claim or decision depends on which configuration or provider relation held at a particular time, obtain evidence for that interval; a relation record alone may not supply it.
For example, a second test attempt may add rig-hours while leaving the number of accepted test packages unchanged. Issuing an invoice for a package and receiving its payment are different events. A release can depend on several test results and a safety decision. Counting these records as interchangeable “completed items” loses the question the account must answer.
Inspect material gaps at the boundary of the measuring system. Server logs can omit failures that occurred before a request reached the server. A queue view can omit rejected, diverted or blocked requests. Obtain another source or narrow the claim where that loss matters.
Use OPS.15.1 when the account needs intervals or aggregates derived from those events. Its construction retains shared batch occupancy, repeated visits, cancellations and the portions of unfinished visits inside an observation window. Reuse a quantity already derived on the required population and boundary.
Reconcile disagreement before aggregating it away. Recover whether two totals use different cutoffs, populations or definitions. If the underlying observations permit it, recalculate on a common basis. Otherwise preserve the disagreement and state the narrower supported comparison or missing result.
OPS.15:4.4 - Present the account for its actual readers
Lead with the conclusion supported for the receiving use, then show the observations and qualifications needed to assess it. Retain the source and time basis in the existing account at the detail the use requires. Distinguish observed state, an interpretation, a forecast and the decision made from them.
Several views can be useful. A coordinator needs current readiness and service risk; a finance practitioner needs accepted service, payable amounts and receipts; a release practitioner needs evidence applicable to a particular configuration. Keep the correspondence between their subjects explicit where the decision crosses views.
A shared table is appropriate when it preserves these meanings. Separate views are appropriate when they answer different questions.
OPS.15:4.5 - Stop when the evidence suffices and refresh when its grounds change
Ask whether unresolved detail can still affect the requested claim or decision. If even the favorable bound misses the criterion, the uncertainty need not be resolved for that conclusion. Other work may still need the detail for recovery, fairness, required assurance or a different decision; keep those uses separate.
Choose refresh timing from the decision window, rate of relevant change, observation delay and cost of stale information. A live incident can require rapid updates. A stable resource decision may need an update only when demand, configuration, access or another relied-on condition changes.
Remove recurring collection that has no current reporting, decision, assurance or recovery use, applying A.11.OP. Before stopping it, identify any real consumer that would lose a necessary result. Reuse a current observation only for the conditions and claims it still supports.
Return the account with the supported claim and any uncertainty material to its use. Obtain another observation only when a receiving use still needs it. If a decision on admission, commitments, finance or control follows, use the account with the corresponding operating method.
OPS.15:5 - Archetypal Grounding
OPS.15:5.1 - Forty requests produce two different service measures
In this constructed case, all forty uncancelled requests in the selected cohort have reached their due dates. At the observation cutoff, twenty-seven finished on time, three finished late and ten remain open. The local service objective concerns timely completion of this due-date cohort and is 90%.
| Observation or calculation | Value | Supported meaning |
|---|---|---|
| Requests completed by the cutoff | 27 + 3 = 30 | Thirty members of the cohort have a completion event. |
| On-time proportion among completed requests | 27 / 30 = 90% | 90% of requests completed by the cutoff finished on time. |
| On-time proportion among all requests due | 27 / 40 = 67.5% | The cohort received timely service on twenty-seven of its forty requests. |
| Still-open requests whose deadlines passed | 10 | These members have already missed the timely-service condition. |
The corrected account says that the due-date cohort missed its 90% objective. It retains the completed-only measure where someone actually needs that narrower description. The ten open requests remain visible for recovery and the recipients’ current service decisions.
A later completion of an overdue request changes its open/closed state but cannot make its original completion timely. If the parties revise a future commitment, preserve the original deadline where the historical comparison needs it. New requests with future deadlines belong to a separately defined current-work view, so they do not silently dilute this cohort’s result.
Use the existing service method to handle the overdue work and affected commitments. The account supports the missed-objective claim. It does not identify why the service failed or prove that a proposed staffing change will fix it.
OPS.15:5.2 - A favorable bound can settle the reporting decision
Consider a separate forty-request cohort with the same 90% objective. Thirty-one are known timely, seven are known late, and two have unresolved completion timestamps. The most favorable result is 33 / 40 = 82.5%, if both unknown requests were timely.
The cohort missed the objective under either interpretation of those two timestamps. Further lookup cannot change that classification. The practitioner reports the supported result and the remaining range, from 31 / 40 = 77.5% to 82.5%.
The missing timestamps may still matter to contacting those recipients, recovering service or correcting a source defect. Pursue that work when its separate use requires it without making it a prerequisite for the already settled cohort judgment.
OPS.15:5.3 - PumpWorks keeps four views connected
The operation’s board includes release candidate R42, incident I73, safety question S19 and provider change P8. A rig history records attempts and setup. The test service records completed packages and customer acceptance. Finance records invoices, payments and receipts. These accounts concern related work, but their rows do not share one universal item identity.
| Reader and decision | Account needed | Correspondence that must remain clear |
|---|---|---|
| Rig coordinator choosing the next slot | Eligible packages, required rig time, configuration and access | A repeat refers to its package and adds resource demand without adding another completed package. |
| Service coordinator handling a promise | The promised test result, recipient, due time, completion and acceptance | A package can be complete at the rig while the customer’s evidence acceptance remains pending. |
| Finance practitioner comparing now with deferral | The same third package, payments, acceptance condition and receipt date | The receipt follows the stated payment terms; completion in month 1 does not put cash in month 1. |
| Release practitioner deciding field use | T9 evidence applicable to R42’s configuration, S19’s result and release authority | Customer acceptance of a test service does not settle the separate release decision. |
For the immediate financial alternative in OPS.14, the third package is accepted in month 1 and its 900 receipt is due at the end of month 2. The account can show both events without calling them the same completion. The rig view retains the repeat among the two earlier packages, so the third package’s financial comparison does not acquire an extra test by a mistaken join.
If P8 changes a provider window, update the affected capacity and service claim. If the release configuration changes, reconsider applicability of T9 evidence. Refresh the accounts that depend on the changed subject or claim.
OPS.15:5.4 - Hospital and assisted-service accounts expose omitted work
A hospital coordinator asks whether all routine cases due today received the agreed service. A department’s completed-visit report omits patients transferred before the visit and cases still waiting. Recover the service definition and each case’s disposition from the qualified care and operating records. A transfer may count as fulfilled, redirected or unresolved depending on the actual agreed service; the report cannot choose that meaning by omission.
The resulting account preserves the eligible cases and reasons for unlike dispositions. It can support service coordination while clinical outcome claims remain with qualified clinical evidence. A different clinical priority can require a different operating action without erasing the earlier service history.
In an assisted production service, the system reports sixty generated drafts and six review decisions. The recipient asks for accepted outputs. Recover which review concerns which draft and request, whether revision created another attempt, and which results actually met acceptance. Counting generated versions or repeated reviews as new accepted results would overstate service.
A useful account shows current review decisions, accepted outputs, rework and outstanding requests with their own time bases. The capacity conclusion can then use review effort, while the recipient’s service claim uses accepted outputs. OPS.13 guides the commitment decision and OPS.18 guides a quality response when the evidence requires one.
OPS.15:6 - Bias-Annotation
Completed cases and successful transactions are easier to observe than abandoned, diverted or still-open work. Begin with the population the operating question concerns and inspect the places where observation can lose its members.
A measure already reported can also become the default objective. State the intended service value and why the selected observation bears on it. Keep a useful proxy qualified where direct observation is unavailable, and revisit it when its relationship to the value changes.
OPS.15:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The account serves a stated use. | The recipient, operating claim or decision, required time and relevant observation are clear. |
| Subjects and populations are stable. | The relevant work, events, results, inclusions and exclusions can be recovered. |
| Quantities have a meaning. | Units, numerator/denominator where needed, start/end rules, cutoff and interpretation are explicit. |
| Sources support the claim. | Observation method, missingness, delay and comparability fit the receiving use. |
| Views can be related without conflation. | Shared subjects and unlike event meanings are preserved where a conclusion or decision depends on more than one view. |
| Collection and refresh have a purpose. | Each retained observation serves a stated reporting, decision, assurance or recovery need, with a relevant change or expiry condition. |
OPS.15:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Use completed-only data to describe every due request. | Recover the due population and retain overdue open work in the service denominator. |
| Join every event to one arbitrary case identifier. | Preserve the actual relationships among requests, attempts, configurations and accepted results. |
| Add a second dashboard to reconcile a definition conflict. | Resolve the differing populations, dates or meanings before choosing a presentation. |
| Treat a current file as current evidence. | Recover the observation time and the conditions under which it remains applicable. |
| Collect every unresolved detail before making any decision. | Test whether its possible values can affect the requested conclusion or choice, while preserving other necessary uses. |
| Infer the cause of a failure from a descriptive difference. | Use the account to frame the causal question and use relevant causal evidence or identify the inquiry needed if a causal conclusion is requested. |
OPS.15:9 - Consequences
The reader can recover what a reported value establishes for the operating question. Different practitioners can use unlike views of the same work while retaining the connections needed for a service, resource or release choice.
Some apparent disagreements remain after their meanings are clarified because the evidence is incomplete or incomparable. The account exposes that limit. A smaller set of relevant observations can reduce recurring effort, although repairing a lost event population may require work on the source system.
OPS.15:10 - Rationale
A measure is useful through the claim it supports for the receiving use. Starting with that claim makes eligibility, event identity and time rules practical necessities rather than optional metadata.
Separate views preserve the different consequences of one piece of work. Bounds and directed refresh then reduce collection whose result cannot affect the current claim or choice, while retaining the observations needed for another real use.
OPS.15:11 - SoTA-Echoing
The practice question is how to obtain a trustworthy operating account without measuring everything. Start with the claim or decision, qualify the observed population and measurement procedure, and preserve event relationships across views. These distinctions explain the forty-request discrepancy and the different service, resource and cash events in PumpWorks.
The SRE Workbook’s guidance on service indicators distinguishes what service behavior an indicator should represent from how the measurement is implemented. Sections 4.2–4.3 adopt that distinction: a server log or completed-item table can omit events belonging to the service question. The source is a 2018 software-service treatment; the method here applies its observation-boundary reasoning to the constructed operating cases without deriving clinical or financial conclusions from it.
Kanban’s flow measures make work boundaries and elapsed-time evidence explicit. The account retains their useful defined-population discipline while choosing measures for the receiving question. The due-cohort example uses a service-deadline population that must be defined separately from a completed-item cycle-time population.
The OCEL 2.0 specification, sections 3–4, and van der Aalst’s 2023 account of object-centric process mining support preserving events’ relationships to several objects. Section 4.3 adopts that representation choice where one case identifier would lose the PumpWorks relationships. These sources describe representation and analysis; they do not establish the operating decision or the validity time of every relation. A larger measurement or process-mining system is appropriate when its result could materially improve the claim or decision at a justified cost; the simple account remains preferable where existing observations and a transparent bound suffice.
Use FPF A.11.OP to decide which observations to keep for a reporting, decision, assurance or recovery need. Reconsider the account when its use, population, event meaning, source coverage or observation method changes.
OPS.15:12 - Relations
OPS.4 guides shared operating attention using qualified state claims; this pattern helps construct the account when those claims are not yet supported. OPS.3 helps identify the operating subjects that source events concern.
OPS.5–OPS.10 provide admission, continuation, aging, queue, constraint and capacity questions that can select the account’s observations. OPS.12–OPS.14 provide human-condition, commitment and financial uses. OPS.18 guides the control action based on quality and reliability evidence, while OPS.17 helps reconsider a failed method assumption.
FPF C.16 governs the measurement characteristics, units and comparison basis used here. A.10 keeps evidence reach explicit, and E.13 helps examine a proxy when its relationship to the intended value is in question. A.11.OP limits recurring account work to its actual contribution.
OPS.15:End
OPS.15.1 - Derive Operating Quantities from Events
Type: Method pattern Status: Stable Normativity: Normative
OPS.15.1:1 - Problem frame
Use this when an operating claim or decision depends on waiting, unfinished work, output or resource use, but the available totals do not make clear what was counted. Two teams report different “cycle times”. A batch completion appears against several orders and inflates machine use. A short observation window excludes unfinished cases and makes service look faster.
Choose the operating subject and boundary events, construct the relevant intervals or counts, and aggregate them under a common clock and population rule. The first useful result can be a corrected comparison or a supported value or bound, including one that settles a decision despite an unknown event.
Start with one case. Identify the events that would start and end the proposed measurement, then locate what the records actually establish about them. A database timestamp can mark entry of a record rather than occurrence of the work event.
Practical gain. The practitioner can tell a change in service from a change in counting, find which records are needed for the requested result, and use partial observations without inventing a complete history.
The reader needs to identify the operation’s subjects and events and understand elementary intervals, rates and averages. Statistical inference requires additional methods when the intended claim goes beyond the observed cases.
Use an existing quantity directly when its definition and observations already fit the receiving question.
OPS.15.1:2 - Problem
An operating name can conceal several measurement constructions. Time from customer request, internal release, service start or approval produces different intervals. Counting orders, visits, samples or occupied resources produces different populations. A shared event can belong to several accounts without becoming several occurrences.
Aggregation can hide these differences. A mean over completed cases omits those still waiting. Summed task durations double-count overlapping occupation. Missing end events are silently treated as zero or as completion at the observation cutoff. The resulting number may be calculated correctly from the records while answering another question.
OPS.15.1:3 - Forces
| Force | Tension |
|---|---|
| Common indicators and different decisions | One familiar name is convenient, but recipients can need different event boundaries. |
| Case detail and shared work | Individual cases need their own histories while a batch or resource episode occurs once. |
| Timely feedback and unfinished cases | A short window supports prompt action but cuts through residence and service intervals. |
| Comparable aggregates and heterogeneous work | Counts are simple while resource demand, routes and acceptance conditions differ. |
| Additional observation and useful action | A missing timestamp may matter or may be irrelevant to the decision already supported. |
OPS.15.1:4 - Solution
Define the quantity from the operating question, reconstruct the events and their subjects, derive the intervals or count changes, and then aggregate. Keep incomplete observation visible in the result. Return the number with enough meaning to use or recompute it.
OPS.15.1:4.1 - Choose the quantity that answers the operating question
Name the subject and the quantity required. When comparing alternatives, state which consequence matters. A customer’s time to an accepted result, a machine’s occupied time and the number of service visits answer different questions even when they concern the same order.
Define membership of the counted population. State when a subject enters and leaves that population. For unfinished orders, choose the arrival and completion events for the service being considered. For a ready queue, include the conditions that make the next operation possible.
Separate unique cases from visits. A return for correction may create another visit to a station while the same customer case remains unfinished. If the case is closed and later reopened, decide whether the receiving question concerns separate episodes or one extended service. Use its operating meaning; do not decide from the number of log rows.
OPS.15 supplies the account needed for the operating question, and OPS.3 helps identify its subjects. A short statement of the chosen quantity is enough when it removes the ambiguity.
OPS.15.1:4.2 - Relate the records to the operating events
For the events used in the calculation, recover the subject, event meaning and occurrence time as far as the available information supports them. Distinguish occurrence time from recording time when their difference affects the result. Reconcile time zones, clock offsets and timestamp precision before comparing events from different systems.
Recover the relationships needed by the question. A dispatch can concern several order lines; one machine cycle can process several parts; one invoice can cover charges for several deliveries. Keep the common event identifiable while following each related subject. A row per event-subject relation is a useful representation, but its row count is not automatically an event count.
Check what the recorded label establishes. “Completed” may mean that a worker reported completion, that inspection accepted the result or that the customer received it. If the receiving comparison needs a later event, use evidence for that event when it is available, seek it if needed, or report the result under the available boundary.
Use MMP.7 when selection, censoring or the recording procedure affects an inference. Missing records do not by themselves show that the corresponding work did not occur.
OPS.15.1:4.3 - Construct the intervals and count changes
For each relevant subject or visit, pair the boundary events belonging to that episode. Its elapsed residence is end time minus start time. If only a range for an endpoint is known, propagate that range instead of selecting an unsupported point.
For resource use, reconstruct the intervals during which the resource is occupied under the chosen meaning. Occupied machine time, operator attention and reservation can differ. A machine can run unattended while its operator serves another machine.
Combine intervals according to the quantity. For a single resource’s occupied fraction, take the duration of the union of its occupied intervals; overlapping descriptions of the same occupation are counted once. To measure total occupied resource-hours across distinct resources, sum those resource-specific durations. To measure part residence during batch processing, retain each part’s interval.
Calendar time and available working time are also different quantities. For working time, intersect the interval with the relevant open-calendar intervals before adding durations. A calendar conversion does not remove a customer’s overnight wait from elapsed service time.
For counts, follow entries and exits of the chosen population. With fixed case identity and no splitting or merging, ending population equals starting population plus entries minus exits. Include cancellations or other exits under their own meanings. If the subject is split or combined, recover the changed counting unit before using that balance.
OPS.15.1:4.4 - Respect the observation window
Choose a positive-duration observation window for a time-average quantity. Include the subjects already present at its beginning and those still present at its end.
For a subject entering at a and leaving at d, its contribution within the window [u,v] is:
overlap = max(0, min(d,v) - max(a,u)).
For a subject known to remain present through v, use v as the overlap endpoint without asserting completion at v. An unknown arrival before u similarly contributes from u while leaving the full residence unresolved.
Add these overlaps to obtain the population-time area. Divide by v-u to obtain the mean population during that window. This is the area under the population count: each present subject contributes one unit for each unit of time it remains present.
For a fixed counting unit without splitting or merging, an empty-to-empty interval gives a useful relation. Its population-time area equals the sum of residence times of all episodes that leave. With at least one departure, mean population equals departure rate multiplied by mean residence of those same episodes. The departure rate is the successful completion rate only when every departure meets the chosen completion condition. If no episode occurs, the area and mean population are zero; a mean residence over zero departures is undefined.
For example, three cases enter at zero. One is cancelled at hour one; the others complete successfully at hours two and three. Area is 1+2+3=6 case-hours over three hours, so mean population is two. All three departures contribute to that relation. The two successful completions remain a separate result count.
On an arbitrary cut window, the departed-episode mean and departure rate alone generally omit the partial intervals. Calculate each present episode’s overlap with the window, including episodes still unfinished at its end.
This finite observation identity does not estimate an unseen tail, establish a long-run regime or explain what caused waiting. OPS.10 uses the appropriate capacity or queueing model when those further questions matter.
OPS.15.1:4.5 - Aggregate only compatible observations
Keep the population, event pair, clock and weighting rule consistent within the reported aggregate. For a case-weighted mean, combine the totals and case counts before dividing when group sizes differ. An unweighted mean of departmental means gives each department equal weight, not each case equal weight.
Choose the weighting from the question. A case-weighted mean gives each counted case equal weight. Resource-demand weighting describes a different burden. Retain classes when the proposed change affects them differently or an aggregate conceals a service commitment.
To compare policies, use the same recipient boundary unless changing that boundary is the point of the decision. If internal admission moves later, report upstream waiting together with internal residence before concluding that customers receive results sooner.
For uncertain or incomplete observations, derive the consequence they support. Residence between four and ten hours leaves compliance with an eight-hour limit open and establishes compliance with a twelve-hour limit. Use C.11.DUA when deciding whether the remaining question warrants another observation.
OPS.15.1:4.6 - Report the quantity for its intended use
Explain the result in terms the recipient uses: for example, “the machine was occupied for forty of the sixty available minutes” or “the shorter internal time excludes four hours of waiting before admission”.
Retain the definition and observations needed to reproduce a consequential quantity, using the existing account when it suffices. Distinguish a direct calculation from a model-based estimate or forecast. MMP.13 supplies inference when the result must generalize beyond the observed population.
When a check fails, localize the repair: a subject was counted twice, a boundary event was misidentified, a clock was shifted, an unfinished interval was excluded, or the aggregation rule answered another question. Correct the construction and reassess the conclusions or decisions that relied on it. A changed route, acceptance event or recording procedure reopens the affected quantity.
OPS.15.1:5 - Archetypal Grounding
OPS.15.1:5.1 - A window cuts through unfinished work
Observe an operation from hour zero to hour eight. Case A arrived at minus three and leaves at two. B arrives at one and leaves at four. C arrives at six and is still present at eight.
| Case | Full known residence | Residence inside [0,8] |
|---|---|---|
| A | 5 hours | 2 hours |
| B | 3 hours | 3 hours |
| C | At least 2 hours; unfinished | 2 hours |
The population-time area is seven case-hours, so mean population is 7/8. Counting departures gives two in eight hours. Their full residence mean is four hours; multiplying 2/8 by four gives one, not 7/8.
The departure cohort includes three hours of A before the observation window and excludes C’s two observed hours. Computing the clipped intervals answers the window question. C’s eventual completion is unnecessary for that result.
Now the question changes to the mean full residence of all three cases. C’s endpoint matters. If no later information is available, the sum is at least ten hours and the mean at least 10/3, with no supported finite upper bound. The earlier mean population does not fill that missing endpoint.
OPS.15.1:5.2 - One batch, several parts, one machine
A machine processes three parts together from minute zero to thirty. The completion event is linked to all three parts. The machine is otherwise available throughout a sixty-minute observation window.
The batch occupies thirty machine-minutes: utilization under this occupied-time definition is 30/60. The parts accumulate ninety part-minutes of batch residence. Copying the cycle interval into three part records preserves each part’s history but does not create ninety machine-minutes.
Part 2 requires another ten-minute cycle from minute forty to fifty. Machine occupation becomes forty minutes and utilization 40/60. There are three distinct parts and four processing visits. The returned part’s additional visit consumes capacity while its customer-level completion follows the acceptance rule.
If an operator attends only loading and unloading, machine occupation does not establish operator attention time. Recover those intervals before making a staffing claim.
OPS.15.1:5.3 - An unknown endpoint need not stop the decision
One uninterrupted processing episode starts at hour ten. A reliable observation shows it still in progress at fourteen and a later observation shows completion by twenty. The elapsed processing duration is bounded by four and ten hours; its precise endpoint is unknown.
Completion by eighteen remains unresolved. The observation at twenty establishes completion by twenty-two without a more precise endpoint. A claim about uninterrupted duration also requires grounds for continuity if an interruption could have gone unobserved.
OPS.15.1:6 - Bias-Annotation
Event logs privilege what the information system records. Unrecorded work, informal coordination and off-system waiting can disappear from an apparently complete account. Compare the chosen event meaning with the work when an omission could affect the requested claim or decision.
Case counting also privileges discrete populations. For continuous material, the corresponding subject may be an amount with changing inflow and outflow. Retain its unit and balance; a row count cannot replace the measured amount.
OPS.15.1:7 - Conformance Checklist
- The quantity has a subject, population, event boundaries, clock and receiving question.
- Common events remain identifiable when related to several subjects.
- Case, visit, part and resource counts are distinguished where their consequences differ.
- Interval combinations match the question, including overlap and calendars.
- A cut observation window retains initially present and unfinished subjects.
- Aggregation uses compatible definitions and an appropriate weighting rule.
- Missing observations produce supported bounds or an unresolved contribution at the stated boundary.
- A claimed service improvement retains the recipient’s waiting origin.
OPS.15.1:8 - Common Anti-Patterns and How to Avoid Them
| Mistake invited by ordinary records | Consequence | Repair |
|---|---|---|
| Count one event-subject row as one event | A shared batch or delivery is multiplied. | Count distinct occurrences or the intended subject relations explicitly. |
| Treat the observation cutoff as completion | Unfinished work receives a false short duration. | Clip its exposure to the window and retain its unresolved endpoint. |
| Sum overlapping resource intervals | Recorded occupation can exceed possible available time. | Form the union for each resource before calculating its occupied fraction. |
| Compare internal time after moving admission | A counting change appears as faster customer service. | Include upstream waiting under the unchanged recipient boundary. |
| Use a mean without its population and weights | Different mixtures masquerade as changed performance. | Reconstruct the aggregate from compatible totals and counts. |
OPS.15.1:9 - Consequences
Operating comparisons become reproducible and many apparent disagreements resolve into different measurement constructions. Partial observations can still support a useful decision.
Recovering event meaning can require domain knowledge that a data export does not contain. Some questions remain underdetermined, and some aggregations intentionally discard detail. Retaining those limits prevents an observed quantity from silently becoming a prediction or explanation.
OPS.15.1:10 - Architectural Rationale
Events establish boundaries from which intervals and populations can be constructed. The receiving question then determines how to combine them. This ordering lets one set of observations support several accounts without forcing all participants to use one completion event.
The method distinguishes an occurrence, its record and its participation in several subjects’ histories. That distinction preserves common work while avoiding duplicate counts. Window clipping follows the same principle: retain the part actually observed without inventing the unobserved rest.
General measurement and inference methods supply the epistemic conditions. The operating contribution is how arrivals, service, returns, delivery and resource occupation produce the quantities used by operating decisions.
OPS.15.1:11 - SoTA-Echoing
When a decision needs comparable quantities from shared events or a cut observation window, derive the interval contributions before averaging. Adopt the sample-path area construction from Sigman’s notes on Little’s Law and adapt the shared-event representation of OCEL 2.0, §§2–4. This is preferable to a completed-only average when a window cuts through visits: :5.1 obtains 7/8 for mean population where the departure shortcut gives one. Sections :4.3–4.4 retain partial exposure and all relevant exits. Sigman’s area argument supports that finite calculation; estimating an unseen tail or a long-run regime requires additional premises.
Summing a shared processing interval once per part overstates machine time. In :5.2 this would turn thirty machine-minutes into ninety. Keeping the common cycle identifiable while following its three parts preserves both the machine occupation and part residence. OCEL supplies qualified event-to-object and object-to-object relations and changing attributes. Its instantaneous records still require the interval interpretation in :4.2–4.3; the standard does not establish how much work occurred or whether a policy improved service.
The added effort is to recover a shared relationship or an interval boundary when the receiving quantity depends on it. A simple case table remains sufficient when events belong to one case and the table retains the boundaries needed for the calculation. A few shared-event references can handle a small batch. Sections :4.2–4.5 retain only the relationships, window contributions and weighting needed by the question.
Hopp and Spearman, Factory Physics, supplies the operating uses of flow, cycle-time and capacity quantities. This pattern reconstructs their populations and boundaries before applying those relations; a compatible average alone does not establish a cause. Reopen the construction when an event changes meaning, a recording change affects an interval or shared occurrence, the decision needs another population, or a simpler construction preserves the same required distinctions.
OPS.15.1:12 - Relations
Use OPS.15 to choose the account the operating question needs and this method to derive its quantities. OPS.3 supplies subject distinctions, OPS.8 consumes readiness and waiting quantities, and OPS.10 uses them in capacity and service models.
OPS.11.1 reconciles operating models whose inputs and outputs use these quantities. C.16 supplies common measurement, and F.0.1/F.9 recover and relate local meanings when needed.
MMP.7 accounts for the observation and recording law; MMP.13 supplies inference. C.11.DUA governs the worth of another observation. C.29 qualifies using a mathematical relation to answer the operating question.
OPS.15.1:End
Part IX — Improve Methods, Control Quality, Reconcile Work, and Continue Practice
OPS.16 - Decide Whether and How to Change an Operating Method
Status: Stable
OPS.16:0 - Use This When
Use this Method when delay, rework, recurring failure, burden or a changed condition raises a question about continuing or changing a way of operating. Identify whether the way is already admitted as U.Method or is provisionally identified through a source-traceable A.3.1.MR candidate account.
For an admitted Method, identify the Method and the version or U.MethodDescription relied on, its operating use, any proposed change, and the decision the available evidence supports. For a candidate, identify the proposed reusable way through its source-traceable account, with its live rivals, gaps and use limits. Neither a U.Method nor a U.MethodDescription has yet been established for that candidate. Existing grounds may suffice to revise, compare or retain the account, or to stop. Consider another observation or trial when its attainable contribution to the decision or its grounds justifies the work.
Use OPS.17 when the current question is which operating Method or candidate from a repertoire deserves comparison. Use OPS.18 when existing evidence already calls for one quality or reliability control response. Use OPS.19 when simultaneous Work across cases or scales must first establish a feasible trial and protected conditions. Use current A.3.1.WT–A.3.1.MV, C.11.MV and A.3.1.MI when the specialist question is trial design, coherence, fit, worth, lineage, introduction, or revision without the receiving Operations decision.
Recognition concerns a recurring way of working rather than only one case. Assurance establishes the selected status branch and the evidence for its bounded decision. Existing Work observations can supply that evidence when their subject and conditions fit. A newly performed trial needs a prospective plan; claims about actual Work need independent occurrence support and observations qualified for their use.
OPS.16:1 - Problem frame
Review an operating Method when changes in demand, services, constraints, technology, participants or protection conditions could affect its use. Use the evidence that bears on the proposed revision. Where performance matters, distinguish the Work supported by observations from what a prior plan, if available, shows was intended.
Improvement language often collapses those distinctions. A proposed way is named as a new version before its reusable semantics have been admitted. A trial schedule is reported as completed Work. A tool output is treated as the operating result. One successful case becomes proof of effectiveness or transfer. The resulting decision can widen an unsupported practice or discard a useful incumbent for the wrong reason.
Given an admitted Method or a status-preserved candidate account, what bounded operating decision is justified by the Work observations and other qualified grounds now available?
OPS.16:2 - Problem
An operating team needs to improve one way of working without turning local learning into an uncontrolled change. The team must preserve service, reliability, human recovery, permission, and other protected conditions while obtaining evidence that can distinguish current, revised, branched, stopped, and still-uncertain alternatives.
The evidence rarely arrives as one result. Actual Work can show that a readiness rule was followed, while service evidence remains too short to establish reliability, fit elsewhere is unknown, burden is only partly observed, and a changed provider invalidates a description. Combining these observations into one improvement score hides the decision boundary.
Before Method admission, a candidate account can guide a distinguishing observation while its reusable-way identity remains unsettled. Preserve that uncertainty instead of reporting Method adoption.
OPS.16:3 - Forces
| Force | Practical tension |
|---|---|
| learning and continuity | A trial must expose a useful difference while the continuing operation still needs service, recovery, safety, and support. |
| status and action | Practitioners need to act on a promising way, while a candidate account cannot be treated as an admitted Method. |
| plan and occurrence | A prospective plan specifies intended trial Work; existing observations and any available prior plan must be recovered without inventing what was intended or performed. |
| local evidence and wider use | One bounded trial can settle a local choice while leaving transfer, general reliability, practical worth, and causality unresolved. |
| change and lineage | A reusable semantic change can require a Method variant, while a changed tool, description, support, or departure may leave Method identity unchanged. |
| speed and assurance | A small trial can reduce delay, but it must stop if the required authority is missing or a protection condition no longer holds. |
| one decision and many observations | Service, flow, human condition, finance, burden, side effects, and missing evidence can all matter without becoming one score. |
OPS.16:4 - Solution
Preserve the distinction between an admitted Method and a candidate account from the initial question through the conclusion. Either branch can finish on sufficient current evidence. Under A.3.1.MR a candidate account may be revised, retained, compared or set aside. If the remaining question warrants a trial, state the change hypothesis and alternatives, establish the operating conditions and plan the Work. For existing observations and new ones, distinguish intended from performed Work, identify what was observed and establish its evidential reach. Make a decision within the authority and grounds available, or state what limits it.
OPS.16:4.1 - Fix the operating question and status branch
Name the operating System, Work family or service, current difficulty, receiving decision, decision maker, horizon, and protected conditions. Use the available identity and admission evidence to select the applicable branch.
| Starting branch | Required identity | First decision-facing statement |
|---|---|---|
| admitted Method | Exact U.Method, exact relied-on Method version or separately classified U.MethodDescription, current operating use, maintained claim, and evidence window | Does the evidence support continuing the present use, adopting, revising, branching or stopping, or making a further observation? |
| pre-admission candidate | Exact A.3.1.MR candidate-account episteme for the provisionally distinguished reusable way, source support, any live rivals and gaps, use limits and explicit non-admission; a distinguishing question only when it changes use | Which identity-test, account-revision, comparison, stop or selected further-observation result can this basis support? |
A candidate label such as “v2”, a checklist, a repeated local habit, or a repository entry does not move the second row into the first. When admission is needed, apply A.3.1 to the reusable way and A.3.2 to any separate description episteme. Use established results where available. A way without an established admission remains in the candidate branch.
Start with the existing improvement account. A competent PDSA record may already distinguish prediction, proposed test, actual observations, adaptation and later implementation. Reuse it. For the branch selected above, reuse any established identity and status; supply the missing Method or candidate-account distinctions needed by the receiving decision. Qualify a stronger evidence claim only when the decision uses it. Include the cost of maintaining these distinctions, obtaining support and displacing service in the comparison. If existing observations may settle the decision, recover the occurrences, their conditions and any prior plan available, then use :4.5–4.9 to judge their reach. Evidence of performance can suffice even when the prior intention is unknown. Use :4.3–4.4 to arrange new trial Work only for a remaining question whose obtainable answer warrants that work.
OPS.16:4.2 - State a bounded change hypothesis and alternatives
When a change is being examined, write the hypothesis in operating terms: for the named use and interval, changing the specified action or condition is expected to alter a named operating result without violating stated protections. Identify observations that could support or challenge the hypothesis, and how they would affect the decision or the grounds for it.
Use OPS.11.1 when the question requires reconstructing the current and proposed networks of transformations, resources and enabling conditions. Its :4.2a constructs alternative arrangements from a required result and their professional contributions when the proposed way has not yet been supplied. Compare that construction before treating a named change as the only trial candidate. State which operation, input, output, release rule, resource assignment or receiving commitment changes. Preserve the distinction between changing the operating route, changing the reusable way described, and establishing changed relations or capabilities in the organization. A change in one does not establish the other two.
Keep materially different, status-preserved alternatives in view:
- continue the current admitted Method or current observed practice for its supported use;
- use a revised admitted Method where its identity and description are already established;
- retain or test a candidate account without calling it a Method;
- branch an admitted Method by a real applicability or semantic difference;
- stop the proposed change or seek another observation.
Use OPS.17 if serious candidates still need to be found or compared. Use an OPS.19 result when it establishes or changes the feasible trial Work or a protected condition. In a trial, preserve the alternatives whose differences matter to the receiving choice or its grounds.
OPS.16:4.3 - Establish the conditions for running the trial
Recover the service, reliability, human-condition, access, permission, support, recovery, and resource conditions on which the trial relies. State the basis, interval and responsible party for each condition. Use existing resource, schedule and service results from OPS.10–OPS.13 or OPS.19 where they establish the required arrangement. Count existing assignments, trial work, learning and support against the same actual resources.
Use access, support and work allocations already provided under current arrangements. Obtain any missing contribution from its provider. Use an organization-change result when the proposal needs to change the contribution, responsibility or authority arrangement itself, rather than use it for another case. Granting already-permitted tool access can be an administration service; transferring responsibility for accepting a result needs the corresponding organizational and professional decisions. Use a sufficient authorized result directly; OCE supplies design or coordination where that question remains unresolved, and OCE.11 coordinates the organization change with continuing service when needed. Obtain any missing capability or practice support from its appropriate development or introduction method.
A conditional WorkPlan can name a missing arrangement and the decision needed to establish it. Before starting the dependent trial Work, confirm that its allocation, permitted overlap, service protection, support, recovery and hand-back conditions hold for the required interval. A prospective plan does not establish their availability. If a condition is missing, keep the affected trial Work closed, as an OPS.19 decision may require, and state what can still proceed.
OPS.16:4.4 - Plan new trial Work when needed
For a selected new trial, plan Work whose attainable contribution to the question justifies its burden. If a smaller trial would provide a sufficient answer, use it. Name intended tasks, proposed performers, admitted constituent Methods expected to be enacted, supports, protected conditions, observations, burdens, stop rules, hand-back and later receiving uses. Keep this WorkPlan prospective and identify the interval during which its premises must remain current. Existing Work is examined from its actual evidence and any plan available for it; do not write a retrospective intention as though it preceded the Work.
A compact plan can use these positions:
| Position | What to state |
|---|---|
| status-preserved subject | Exact admitted Method and relied-on description, or exact candidate account and its missing admission basis |
| operating question | Current use, proposed change, comparison, decision maker, and observation needed to decide or support the choice |
| intended Work | Tasks, proposed performers, expected admitted constituent Methods, containing System, and temporal window |
| conditions and stops | Authority, permission, support, service, recovery, human protection, fallback, and hand-back |
| observations | Direct subjects, measures or descriptions, collection point, burden, and later receiving use |
| return | Supported decision branches, limits on stronger uses, and any still-needed observation or revision condition |
A.15.2 governs this prospective WorkPlan; section 4.5 establishes what actually occurred.
OPS.16:4.5 - Establish actual Work and direct results separately
For existing observations or after a new trial interval, identify only Work that actually occurred. For each Work occurrence, recover the actual performer, temporal extent, containing System and enacted admitted Methods under A.15.1; identify a departure only against an established plan or applicable rule. Identify each direct result through its relevant domain owner. Keep later service Work, recovery Work, observation Work and decision Work as separate wholes where their identities require it.
Never record the candidate reusable way or its candidate account as enacted. In the pre-admission branch, actual Work may enact independently admitted constituent Methods and may supply observations relevant to the candidate account. It does not enact the candidate whole.
A completed task also does not prove a Method change. A changed board, prompt, tool, description, support arrangement, or local departure changes Method identity only when reusable Method semantics change under A.3.1. Keep the changed object and direct relation instead when they do not.
OPS.16:4.6 - Type observations by subject and receiving use
Keep the subject and evidential reach of each material observation visible in the decision.
| Observation position | Direct subject and use | Unsupported stronger reading to avoid |
|---|---|---|
| operating result | The named Work or operating System result for the selected interval | The changed Method caused a general improvement. |
| service or reliability | Eligible service events, accepted results, loss, recovery, or reliability condition | One completed case establishes broad reliability. |
| human condition | Affected participants, exposure, recovery, load, or support | Reported completion means burden was acceptable. |
| queue or constraint | Waiting, eligibility, admission, resource use, blockage, or displacement on its own population | Local utilization proves total-flow gain. |
| financial consequence | Incremental payment, receipt, cost, contribution, or horizon-specific consequence | A favorable accounting value authorizes the change. |
| side effect | A separately identified beneficial or harmful consequence | An observed side effect explains the whole result. |
| burden | Time, attention, coordination, training, observation, or apparatus required | Small trial effort proves affordable sustained use. |
| missing evidence | The absent observation, affected decision, and next way to obtain or stop | Absence may be filled by a nearby proxy. |
| Method or description claim | The exact reusable semantic or description claim that observations support or contradict | Every tool, wording, support, or local-use change creates a Method variant. |
Use OPS.15 when the observation population or event correspondence is not yet trustworthy. Use OPS.18 when the evidence calls for a quality or reliability control decision. Those results retain their own subjects and authority.
OPS.16:4.7 - Qualify the evidence through its current owners
Use applicable specialist results and obtain a missing contribution when the decision needs it. A.3.1.WT explains how to use matching observations of Work or design a representative trial that distinguishes alternatives. Use A.3.1.CC for coherence, A.3.1.FT for situational fit or transfer, C.11.MV for practical worth, A.3.1.MV for Method lineage and variant claims, and A.3.1.MI to distinguish the target, introduction strategy, actual Work, observations and bounded revision.
Use A.10 when the source-to-use account remains implicit or must remain replayable. Use C.16 for measurement validity and C.27.TA for the temporal window needed by the receiving decision. Use C.27 when the receiving use requires a temporal-claim adequacy check, and the C.28 causal-use result when the decision relies on a causal claim. Return temporal order, association or direct occurrence evidence at its supported strength, keeping the limits needed by the decision in the existing operating return. A broader claim about coherence, transfer, worth, sustained effectiveness or causality needs evidence for that claim.
Increase assurance effort when its attainable contribution to a consequential choice or condition of use justifies the effort. The extra identity and evidence distinctions are worthwhile when they prevent an unsupported start, branch, or stop. If a simpler observation settles the same bounded choice under the same protections, use it and leave stronger claims unresolved.
OPS.16:4.8 - Compare alternatives under authority and protected conditions
Compare feasible options for continuing, revising, branching or stopping under the same operating use, interval, result definition and protected conditions. Carry uncertainty as an interval, scenario or missing claim. When different operating uses matter, compare the options within each use and identify which options remain non-dominated there. Keep an unresolved comparison visible if the missing information could change which variant is retained.
Identify the Agent authorized to make the local operating decision and the predicate, scope, and basis of that authority. Clinical, safety, release, financial, employment, security, and other specialist decisions remain with their owners. Expertise, sponsorship, assignment, access, and a tool recommendation do not transfer authority.
A favorable trial result applies within the conditions that made the trial feasible. Stop or narrow the trial when permission, qualified support, fallback, recovery, evidence validity, or another protected condition is absent.
OPS.16:4.9 - Return a status-preserving operating decision
Use the branch selected in section 4.1.
| Branch | Permitted return | Required boundary |
|---|---|---|
| admitted Method | continue the established use, adopt, revise, branch, stop, or further observation | Bind the decision to the exact admitted Method and relied-on version or description, named operating use, conditions, evidence window, and authority. |
| pre-admission candidate | continue to the separate A.3.1 identity test; revise or retain competing candidate accounts; stop; or seek further observation | Keep the candidate reusable way inside its candidate-account episteme. Return no Method adoption, Method branch, or U.MethodDescription claim. |
For either branch, return the exact operating use, supporting evidence, any material limits on stronger uses, protected conditions, decision maker and relevant repertoire, lineage or reopen consequence. Include a next observation only for a selected further inquiry; a completed candidate-account revision or stop needs none. When the decision consumes a returned value from a governed operation application, A.6.1 binds that exact value and C.2.1 identifies its separate result episteme. Do not turn it into a generic Work result or produced entity. Keep the decision and any Method-lineage update separate from trial Work.
An adopt or branch return makes an admitted Method available only for the named operating use and conditions. It does not establish organization-wide adoption, cultural selection or retention, causal superiority, a new capability, or authorization elsewhere. Send a result to OPS.20 only as an admitted local Method variant with its exact relied-on description and bounded evidence, or as a status-preserved candidate-account or observed-practice variation.
OPS.16:4.10 - Keep the return short enough to decide from
A useful return lets the responsible practitioner answer four questions quickly: which admitted Method or candidate account was considered; which available sources support the result and, if a trial is claimed, what actual Work and observations occurred; what current account or decision is supported; and what remains unsupported or reopens the decision. Attach detailed evidence through its owning account rather than restating it.
The team can finish a supported candidate account or make a bounded operating decision. Service and authority conditions continue to govern its use.
OPS.16:5 - Archetypal Grounding
OPS.16:5.1 - PumpWorks branches an admitted package-admission Method
This constructed case continues the PumpWorks control-service operation. The incumbent package-admission Method is admitted PW-TestAdmission-v1. A source-traceable A.3.1.MR candidate-account episteme proposed adding current package readiness, required permission, qualified support, a downstream acceptance path, and a stop on new starts when incident margin is consumed. Before this trial, its EntityOfConcern was independently admitted as PW-TestAdmission-v2 : U.Method. Separate episteme PW-TestAdmission-Description-e2 : U.MethodDescription passed A.3.2 and is the exact description relied on here. The candidate account, admitted Method, and MethodDescription remain different objects.
The local hypothesis is that v2 will reduce avoidable setup and unsupported starts for the named control-service package family without damaging incident response or protected recovery. The alternatives are retain v1 for the whole family, use v2 for the named family, branch by an applicability condition, stop the change, or obtain further evidence. The control-service operations lead holds the local package-admission authority; safety and field-release decisions remain with their existing holders.
The prior OPS.19 result keeps the trial closed while incident coverage, recovery, support, permission or feasible rig use is absent. In the later trial interval, the service and resource owners confirm permitted overlap, retained incident coverage, manual fallback, a qualified support window, the stop on new starts and hand-back. Those conditions make a two-package trial feasible. The earlier plan could describe them while they were still unavailable; it could not authorize an unsupported start.
The WorkPlan for the two-package trial names two intended package-admission decisions, proposed coordinators, v2 as the admitted Method expected to be enacted, support and fallback, the service and recovery protections, the readiness and permission observations, the burden to record, and the stop. In the constructed later week, Coordinator-C17 performs PW-Admission-A-1 from 09:10 to 09:18 and Coordinator-C22 performs PW-Admission-B-1 from 10:05 to 10:12, both inside PumpWorks-ControlServiceOps. Each is separately admitted Work and enacts admitted v2.
| Actual occurrence | Work and direct result | Decision-relevant observation |
|---|---|---|
| package A admission | In PW-Admission-A-1, Coordinator-C17 confirms readiness and current permission and admits the package. Separate admitted test Work PW-Test-A-1 later completes and returns its accepted test result. | The readiness and permission branch is usable for this occurrence; the package result does not by itself establish why it succeeded. |
| package B admission | In PW-Admission-B-1, Coordinator-C22 finds that the permission basis is not current and holds the package. No test Work starts and no test result exists for this package. | The explicit hold prevents an unsupported start while preserving the package as pending demand. |
| continuing service | Incident coverage, manual fallback, and protected recovery remain available through the trial interval and hand-back. | The trial stayed within its supplied conditions; broader reliability remains untested. |
| burden and description | The account retains the additional readiness and permission checks, support use, departures, and exact description edition separately. | The bounded burden is visible; sustained affordability and description adequacy outside this use remain open. |
The observations support the readiness and permission branch for these two decisions. They do not establish transfer to another service, causal superiority over v1, general reliability, or practical worth across a broader horizon. The operating decision can rely on the actual occurrences, available service protection and observed hold. If a later decision asks whether v2 causes fewer unsupported starts than v1, these observations do not supply the needed C.28 comparison and inference basis. Return that causal-support gap while preserving the independently supported branch decision.
The selected return is branch. Retain admitted PW-TestAdmission-v2 under PW-TestAdmission-Description-e2 for the named control-service package family and the supplied support and service conditions. Keep admitted v1 for an unaffected family whose current facts still fit. Before widening the v2 branch, require a discriminating observation under provider unavailability. Record the authorized operating decision, Method-lineage update, and repertoire return separately from the trial Work. Reopen when permission, provider support, incident margin, package family, relied-on description, or the next discriminating observation changes.
Compare this same return with competent PDSA. A PDSA team can predict fewer unsupported starts, conduct the two bounded tests, observe A’s usable result and B’s proper hold, preserve service and adapt before wider implementation. Those are shared contributions. OPS.16 adds a useful result only for the receiving question that PDSA’s ordinary local report might leave open: which admitted reusable way and exact description may another package family rely on, and which family stays on v1? If that report already records the same identity, applicability, conditions and evidence limits, it is sufficient. The lineage and repertoire return then reuse it. Their ongoing maintenance and any extra qualifying observation must earn their cost.
OPS.16:5.2 - A hospital keeps a proposed readiness way pre-admission
A public-hospital emergency-flow team observes repeated handover clarification and proposes an information-checking way for transfers between clinical areas. Candidate account ED-Handover-Readiness-CA1 describes the proposed operations: recover the information required by the applicable qualified handover conditions, compare the available case information with those requirements, and refer a missing item or changed clinical condition to its qualified owner before the corresponding coordination decision. The clinical requirements and decision authority are supplied inputs. Brief delay notes leave unclear whether repeated clarification followed missing information or a new clinical finding despite complete information. The account leaves its applicability to changing clinical conditions unresolved. No U.Method or U.MethodDescription has been admitted.
To resolve that applicability question, suppose the team selects observation of two handover intervals under current staffing and safety conditions. Its bounded WorkPlan names the information to compare, qualified participants, privacy protection, stop and the candidate-account revision the evidence can change. When actual clinical and coordination Work occurs, it is admitted separately. Record as enacted only the independently admitted Methods used in those occurrences, such as triage, clinical assessment or handover. The proposed whole retains its candidate status.
Suppose the first record shows a required information item absent before clarification, while the second shows a new clinical finding after the required information was complete. These observations support distinct applicability returns in ED-Handover-Readiness-CA1: seek the missing information in the first condition and return the changed clinical condition to its qualified owner for the needed decision in the second. Completing the information check cannot establish readiness that still depends on that decision. Patient, clinical case, WorkPlan, actual Work, information observations, safety conditions and clinical decisions remain separate.
The current result is a revised candidate account with the proposed operations, their qualified clinical inputs and the newly distinguished applicability condition. That revision can finish the receiving question while retaining candidate status. If another use requires Method identification, compare the account with A.3.1 and name the particular missing identity condition before selecting further inquiry. Clinical priority, consent, privacy, safety, staffing and worker-health decisions remain with their qualified owners.
OPS.16:5.3 - An AI-assisted software operation stops at a provider boundary
A software operations group has independently admitted AI-ReleasePrep-v3 : U.Method for one release-preparation family. Exact AI-ReleasePrep-Description-e4 : U.MethodDescription states the human review, evidence capture, security check, fallback, and release-authority boundary. A prompt repository, model endpoint, and usage counter are supporting Systems or records; none is the Method or proof of enactment.
The trial WorkPlan compares the current human preparation route with admitted v3 for a small set of eligible low-risk changes. It names the proposed human reviewers, the admitted Method expected to be enacted, model and provider condition, security and software-assurance checks, fallback, review burden, evidence window, and a stop if the provider or model condition changes. Actual release-preparation and review Work is admitted separately. Model calls, traces, generated text, test results, security observations, human decisions, and release authorization retain their own subjects.
For eligible cases under the qualified provider and model condition, the observations can support a bounded adopt or branch decision if human review, assurance, service, and burden conditions remain current. If the provider changes the model to an unqualified edition during the interval, the existing evidence no longer supports that branch. The team stops AI-assisted starts for the changed condition and uses the named fallback while qualification is unresolved.
The return preserves the admitted Method and its exact description while narrowing its applicable branch. It establishes neither model capability in general, causal superiority, release authority for the tool, nor transfer to high-risk changes. Security, software assurance, model capability, employment, and release decisions remain with their owners.
OPS.16:6 - Bias-Annotation
| Recurring bias | Likely drift | Working repair |
|---|---|---|
| novelty and solution bias | The proposed change is named as a Method version before identity is established. | Begin from the admitted-Method or candidate-account branch and preserve it through the return. |
| success-story bias | One completed or favorable case becomes proof of effectiveness, fit, or worth. | Type the direct observations and state the limits material to the proposed use. |
| plan-completion bias | A scheduled trial or configured tool is reported as performed Work. | Keep WorkPlan, actual Work, supporting Systems, and direct results separate. |
| survivorship bias | Held, stopped, failed, or missing-evidence cases disappear from the trial account. | Account for each eligible case, its result or disposition, and the reason where the intended result was not obtained. |
| measurement availability bias | A visible cycle-time or usage measure becomes the improvement objective. | Start from the operating decision and qualify the measure’s subject and use. |
| rollout bias | Publication, training, access, or local use becomes organization-wide adoption. | Limit the return to the named operating use; use OPS.20 only for a separate population-level cultural question. |
| tool-change bias | A prompt, board field, model, or support change is called a new Method. | Apply the reusable-semantics identity test and retain the actual changed object otherwise. |
OPS.16:7 - Conformance Checklist
- The operating System, use, difficulty, receiving decision, decision maker, horizon, and protected conditions are explicit.
-
The starting branch names either an exact admitted
U.Methodand relied-on version orU.MethodDescription, or an exactA.3.1.MRcandidate account with source support, any live rivals and gaps, and explicit non-admission. A distinguishing question is required only when it changes the receiving use. - For a selected trial, the bounded hypothesis, current alternative, material change or branch, stop condition and expected observation are clear, including what the observation can establish for the decision. The plan identifies the status of each Method or candidate.
- A selected new trial uses applicable resource and service results; OCE.11 is selected for coexistence around an organization change. Conditions needed for the trial hold when its dependent Work starts; a conditional plan preserves any remaining gap.
-
New trial Work has a prospective
WorkPlannaming intended tasks, proposed performers, expected admitted constituent Methods, supports, observations, burdens, protections, stops, hand-back and later use. Existing evidence retains any available prior plan without inventing intention or occurrence. - Every actual Work occurrence has supported actual performers, enacted admitted Methods, extent, containing System and direct results; any claimed departure has an established comparison basis. No candidate whole or candidate account is enacted.
- Operating, service or reliability, human-condition, queue or constraint, financial, side-effect, burden, missing-evidence, and Method or description observations retain their direct subjects and uses.
- Coherence, fit or transfer, worth, evidence reliance, measurement validity, temporal window, and causal reach are qualified only where the receiving decision needs them and through their current owners.
- Alternatives use the same operating basis, preserve protected conditions, carry uncertainty, and remain within named authority.
- The return uses the permitted branch vocabulary, exact use, evidence window and limits, and relevant repertoire, lineage and reopen consequences. A next observation belongs only to a selected further inquiry, not to every completed account revision or stop.
-
A board, prompt, tool, description, support, or local departure changes Method identity only when reusable Method semantics changed under
A.3.1. - Any proposed wider use has its own cultural, causal, capability or authority basis; the local decision is not that basis.
OPS.16:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| “We trialled candidate v2, so the team enacted it.” | Keep the reusable way in its candidate account; record only actual Work and independently admitted constituent Methods as enacted. |
| “The rollout finished, therefore the new Method is adopted.” | Separate introduction Work, later operating Work, local decision, and any population-level cultural claim. |
| “The package passed, so the Method works.” | Retain the package result, service conditions, comparison, evidence window, and unsupported causal or transfer claim. |
| “The dashboard improved after the change.” | Recover the observation population, covarying conditions, validity window, and decision that the value can support. |
| “The new tool created a new Method.” | Test whether reusable inputs, operations, applicability, or result semantics changed; otherwise record the tool or description change directly. |
| “The trial must continue because learning is valuable.” | Stop when protection, authority, evidence validity, or a worthwhile contribution to the decision or its grounds is unavailable. |
| “One standard branch should replace every local variant.” | For each material operating use, compare the variants that can serve it. Give the grounds for retaining each branch or identify the unresolved comparison. |
| “No adverse event occurred, so reliability is established.” | State the exposure and observation window; keep broader reliability unresolved. |
OPS.16:9 - Consequences
Practitioners can improve an operating Method without losing track of what was planned, performed, observed, or decided. The two status branches let teams learn from a candidate reusable way before admission while preventing candidate language from becoming an enactment or adoption claim.
The method adds explicit identity, evidence, and authority work. That effort is concentrated on distinctions needed to justify continuing, starting, branching or stopping. Some useful trials end with further observation, a revised candidate account, or a narrower branch rather than a general improvement claim.
A bounded decision also preserves later learning. Lineage, repertoire, service evidence, and an OPS.20 cultural question can receive the exact result they need without inheriting a stronger claim.
OPS.16:10 - Rationale
The decision concerns whether to change a way of working under the relevant service conditions. Establish its subject, the grounds the choice depends on and the available authority. A comparison of descriptions can establish a conflict. A claim about performance needs evidence of the Work and result in question.
The status split prevents circular proof: a candidate is not admitted because a plan calls it a Method, and actual Work is not said to enact a candidate whose identity remains unsettled. The typed observation and specialist-return steps prevent one favorable outcome from silently supplying coherence, fit, worth, reliability, or causality.
Local decisions remain valuable even when stronger claims are open. A branch that works for one package family under one support condition can improve operation now while preserving the evidence needed to reconsider transfer or cultural continuation later.
OPS.16:11 - SoTA-Echoing
The question is what to change in a reusable way of operating, and what the evidence actually supports. Plan–Do–Study–Act (PDSA) provides a comparison for the worked case. The Institute for Healthcare Improvement’s testing guidance includes predictions, small tests, actual observations, unexpected effects, refinement and tests under varied conditions. Its implementation guidance distinguishes learning from a change from making it a lasting part of work. OPS adopts these contributions.
At the PumpWorks decision in section 5.1, both arrangements can retain A’s successful use, value B’s refusal to start without current permission, protect service and withhold a broader implementation claim. The residual OPS contribution arises when another service must recover the exact reusable way, distinguish its description from a changed tool or local adjustment, and decide which applicability branch it may use. Sections 4.1 and 4.5–4.9 connect that receiving decision to Method Engineering and FPF’s identity, occurrence, measurement and evidence distinctions. A candidate account can also finish with a supported revision or comparison without inventing a trial or asserting Method admission.
The whole added burden includes recovering Method identity, relating observations to the claims actually consumed, maintaining description and lineage, informing later users, and any specialist qualification or additional observation required by a stronger claim. Those tasks can exceed the cost of the local improvement test. Include the distinctions needed for a branch, stop, receiving claim or later use. Where PDSA is in use, an existing record may already preserve those grounds or need only the missing distinction.
Method Engineering’s trial, coherence, fit, worth, lineage and introduction contributions remain the direct suppliers. FPF A.3.1.MR, A.3.1, A.3.2, A.15.1, A.15.2, A.10, C.16, C.27.TA, C.28 and C.11 qualify the corresponding identity, Work, evidence and comparison questions; they do not set the operation’s service consequence or authority. An operating allocation can supply trial conditions without an organization change; OCE.11 is used when changed organizational relations require coexistence with continuing service.
For rapid feedback, DORA’s continuous integration, continuous delivery and risk-sensitive approval guidance supplies software contributions. The SRE error-budget example supplies a reliability stop. Zampetti et al., “Continuous Integration and Delivery Practices for Cyber-Physical Systems” (2022), provides transfer limits from heterogeneous pipelines. In §§4.3–4.8, choose feedback timing, automation and independent assurance to suit the service, available support and applicable protection conditions. Reopen when a changed family, observation window, candidate identity, support condition or capable incumbent changes the reuse decision or its total cost.
OPS.16:12 - Relations
Introduction and later-use support are supplied by FPF A.3.1.MI. Its result keeps the target practice, introduction strategy and support distinct.
OPS.15 supplies a decision-specific account when observations, populations, or event relations are not yet trustworthy. OPS.17 supplies status-preserved admitted Methods, repertoire claims, or candidate-account alternatives. OPS.18 supplies quality or reliability evidence and its control result.
OPS.10–OPS.13 supply the needed resource, schedule, human-condition and service contributions; OPS.19 supplies a cross-scale decision when trial feasibility or protection depends on its result. OCE.11 supplies coexistence around an organization change. Use each result within its supported scope and confirm the conditions needed for execution; a prospective arrangement remains conditional.
Current A.3.1.WT–A.3.1.MV, C.11.MV and A.3.1.MI govern representative trial evidence, coherence, fit or transfer, worth, lineage, introduction, observation, and bounded revision. A.3.1.MR, A.3.1, A.3.2, A.3.4, A.15.2, A.15.1, A.6.1, C.2.1, A.10, C.16, C.27.TA, C.27, C.28, C.11, and E.23 retain their direct identity, Work, result, evidence, choice, and improvement questions. This pattern composes their results for one Operations decision.
OPS.20 may receive an admitted local Method variant with its exact relied-on description and bounded evidence, or a status-preserved candidate-account or observed-practice variation. It independently supports the practitioner population, cultural predicate and bounded continuation decision. A new intervention or later observation is required only for the claim or selected work that needs it, with its own authority and evidence. A claim that the practice continued across a population needs evidence of that continuation.
OPS.16:End
OPS.17 - Compare and Refresh Operations Methods
Status: Stable
OPS.17:1 - Problem frame
Use this when the current way of running an operation repeatedly misses its purpose, a changed condition defeats one of its assumptions, or a serious alternative could improve a live operating decision. You may need to choose how ready work enters a queue, how an exceptional case continues, how a service responds to failures, or how repeated support develops usable knowledge.
Start with that decision and one family of Work: the actual work people and other systems perform to produce the operating result. Recover what the present method does and what would justify retaining or changing it for this use. The first useful result is a small repertoire of operating methods with their applicable uses, evidence, costs and reasons to reconsider them. A repertoire is a maintained selection of ways of working, with enough guidance to choose among them.
Operations management is the wider practice. This pattern governs the choice and maintenance of reusable operating methods within it. If an existing method already fits the situation and its conditions still hold, use it for the current decision. Replacing a display, repairing a tool or resolving one unusual case may need only that bounded action. A present comparison or traceable candidate account can be complete while a stronger operating-effect claim remains unsupported. Developing or testing that claim is separate work, selected only when its attainable contribution is worth the whole burden.
A PumpWorks board contains twelve matters, yet only four test packages are ready for the rig. Buying more rig time, restricting work in progress and repairing readiness can all sound like remedies. Their value depends on why work waits. Compare the moves and identify any remaining question about the cause of the wait before choosing a response.
OPS.17:2 - Problem
A named approach often bundles useful operations with assumptions about demand, resources, evidence and the purpose of the organization. Adopting the bundle can import an unsuitable objective or omit a condition that made its source example work. A local success also gives weak grounds for general use if the team cannot recover what was actually changed.
A catalogue creates a different difficulty: it preserves names but leaves every practitioner to reconstruct applicability. The needed knowledge is what each method lets the operation do, what it requires, and what observable change would defeat the claim.
OPS.17:3 - Forces
| Force | Practical tension |
|---|---|
| reuse and fit | A known method saves invention, while local demand, authority or capability can invalidate its assumptions. |
| improvement and adoption cost | A stronger response can consume training, observation and coordination effort that a simpler adequate response avoids. |
| local gain and operating result | Faster preparation can move unfinished work to acceptance or consume incident cover elsewhere. |
| comparison and preference | Several feasible methods can remain worthwhile for different service, burden and financial consequences. |
| consistency and exception | A stable work policy helps coordination; a justified urgent exception can require explicit displacement and recovery. |
OPS.17:4 - Solution
OPS.17:4.1 - Frame the choice in operating terms
Name the Work family, the result served, the receiving decision and its horizon. Describe the current method through a recent representative case: what triggered action, what inputs and resources were used, which participants acted and what they did, what result was accepted and where work or information waited. Use existing evidence first.
State the consequential discrepancy. “The board has twelve cards” is an observation. “Four ready packages cannot receive their required two-hour rig visits before Friday” names a service problem. If the mechanism is unresolved, state how that uncertainty affects the current choice. OPS.9 helps with a disputed constraint; OPS.15 helps when the existing account cannot make the distinction.
Keep current practice and the least costly adequate response in the comparison. A corrected readiness check may be enough when a wholesale planning change offers no further decision-relevant benefit.
OPS.17:4.2 - Recover candidate operations from their sources
Read each candidate at the level that could actually be reused. Recover its input, sequence or conditional rules, first useful result, required capability and support, evidence for the claimed effect, and conditions for stopping or changing its use. Retain the source and its relevant version or date when that changes the meaning.
For example, an explicit limit on started work requires a start/end definition and a policy for reaching the limit. A rule protecting a scarce resource requires evidence of the resource’s limiting role for the named demand and horizon. A case method requires conditions under which a practitioner may choose or change the next action. These are different claims even when one tool presents them together.
The following repertoire supplies starting comparisons. Use the rows that address the operating question. If none supplies the needed result, recover or construct the missing contribution through C.39 rather than selecting the nearest school name. OPS.11.1:4.2a can construct a different operating arrangement using adequate methods already available; a new reusable operation retains its candidate status until its own basis is established.
| Operating question | Candidate move | Evidence and limit that change its use |
|---|---|---|
| Too much work starts while eligible work waits | Define readiness, control work in progress and pull new work when the stated capacity is available, using the Kanban line. | Recover item boundaries, actual waiting and the start policy. A limit must protect the receiving service; its value is not inferred from the number of board cards. |
| A particular resource or dependency limits the result | Protect its useful time and feed it appropriately, using bounded moves from the Theory of Constraints (TOC) and TameFlow. | Establish the current limiting mechanism. Historical average utilization alone can miss starvation or short peak overloads. |
| New information changes an admitted case | Choose or revise the next action under case conditions, using CMMN case planning or declarative condition/response rules. | Recover prerequisites, pending obligations and practitioner discretion. A recurring subprocedure can remain fixed inside the case. |
| A customer-relevant service objective is missed | Relate eligible service events, observed loss and an authorized response through a service-level objective (SLO) and an error-budget policy that connects permitted loss to action. | Check event coverage and response timing. An aggregate can hide a severe short incident or an affected customer group. |
| Repeated production results change or a lot needs disposition | Use statistical monitoring for variation, or an acceptance plan for the particular lot. | The population, sampling basis and decision differ. A monitoring signal does not supply a lot-disposition decision. |
| More output appears financially worthwhile | Compare contribution per scarce resource under a suitable model, and compare actual incremental payments and receipts over the decision horizon. | Recover demand, variable costs, displacement, acceptance and timing. Coupled constraints and indivisible jobs can defeat a simple ranking. |
| Extra service consumes human recovery or attention | Remove avoidable demand, redesign the work pattern or provide qualified coverage before relying on individual coping. | Recover affected groups and supplied protection conditions. Use OPS.12 to choose the intervention. |
| Repeated support consumes expertise while useful answers are missed or remain inadequate | Compare direct use of a sufficient answer with KCS knowledge development within service work; use :4.2.1 for the source operations and receiving returns. | Distinguish the service interaction, applicable knowledge and receiving outcome. Supply qualified correction and maintenance; use patterns can justify a service-change question without proving its cause. |
A source’s example is evidence for what it demonstrates. Treat a proposed combination as a candidate whose compatibility and fit still need examination. A tool’s changed version is a reason to inspect its effect on the method, rather than sufficient evidence of a new Method variant.
OPS.17:4.2.1 - Choose how service work develops usable knowledge
Repeated requests can consume expert time even when useful answers already exist. They can also expose an answer whose conditions are unclear, a missing professional solution, or a costly workaround worth removing. Start with a representative receiving case and distinguish these possibilities before commissioning more articles, training or a new knowledge platform. The first useful result is a choice of what to reuse or change, with the professional contribution and support it needs.
Knowledge-Centered Success (KCS, formerly Knowledge-Centered Service) is a candidate when the service needs to develop shared working knowledge through its use. The Consortium for Service Innovation’s complete practices guide explains the professional practice: knowledge is reused and improved during service work, while analysis across uses changes content, workflow or the underlying service. An adequate manual, direct source or competent provider remains a serious alternative. Use it directly when it supplies the required result; a single unfamiliar case need not justify a continuing knowledge programme.
For a selected KCS use, obtain the particular operation from the following treatments and bring its result back to the operating choice. A practitioner familiar with the operation can reuse it; a performer new to it needs access to the explanation and any support required to perform it competently.
- Connect the request to a usable answer. Use Structured Workflow Integration and Track Reuse to retain the requester’s circumstances, find and judge existing knowledge, and associate the interaction with the knowledge actually used and what is known about its outcome. Professional diagnosis or investigation supplies an absent answer. Return the supported resolution, or the precise unresolved question and the qualified contribution needed next. A maintained external source can remain the answer rather than being copied into another authority.
- Make the reusable contribution discriminating and correctable. When material needs development, use selective creation to distinguish useful contextual capture from another article. The simple template and article-structure treatment explain how the question, environment and resolution support later discrimination, while requester-specific details stay in the interaction record under its access and retention rules. Use Article State for the separate confidence, audience and governance decisions. Reuse is Review connects actual application to correction by a capable contributor; opening or citing an article alone supplies no such judgement.
- Choose the receiving improvement. Use Knowledge Optimization when recurring uses can change which content, access, workflow or product problem deserves action. Preserve materially different conditions behind similar requests. Return the supported discrepancy and affected uses to the responsible practice; a recurring symptom motivates investigation without establishing its cause.
These returns determine which further contribution to obtain. For a sound answer that is hard to recover or maintain, use the relevant Knowledge-Corpus Access Engineering (KCAE) method: KCAE.MEMORY retains permitted episodes and conditional connections; KCAE.CHANGE maintains editions and affected derived results; KCAE.EVAL examines the usefulness of the access arrangement. A missing domain answer needs its professional supplier. Use OPS.22 when service observations need interpretation or an authorized response. Return a proposed reusable operating-method change to OPS.16. CB.14 is useful when a community actually wants to develop and maintain a joint repertoire.
Include the work that makes the chosen arrangement sustainable. Diagnosis, content correction and analysis across cases need suitable competence, time, permission and a receiving decision maker. The full KCS guide develops content standards, proficiency and coaching, and continuing organizational support; check which of those conditions are already available and what must still be provided. Use Roles and Proficiency for the rights model and its competency conditions. Content Health Indicators and Process Alignment Review distinguish article-standard checks from observations of case handling. Coaching for Success and Structuring Coaching Sessions explain how to arrange the coach’s contribution, the practitioner’s work and follow-up. Obtain missing support, revise the service promise or retain the simpler adequate arrangement. Compare the burden on contributors and recipients as well as the sponsor’s expected saving. New material can also be warranted before failure, when a forthcoming change and its professional evidence create a useful receiving question.
An agent can perform any of these contributions within its actual qualified capability and granted scope. If automation removes the capable observation that previously corrected an answer, arrange an adequate replacement for that contribution. It may be an agent check, suitable independent assessment, receiving-outcome evidence or qualified human work, according to the claim at issue. For tool integration and interrupted self-service, use the guide’s Technology Integration to preserve the context needed by the next performer. The changed division must still supply the service result and the knowledge correction on which future use relies.
OPS.17:4.3 - Compare feasible ways of working
First exclude options that violate a supplied protection, authority limit or necessary operating condition. For the remaining options, compare the consequences material to the choice or its grounds: accepted service, resource demand, delay, quality, human burden, financial effect and the effort to introduce and sustain the method.
Use the same Work family, horizon and result definition for each option. Carry uncertainty as an interval, scenario or unresolved claim suitable for the use. Separate an observed result from a forecast or causal explanation. A method tried on one team’s ordinary cases can enter another team’s repertoire as a candidate. To promise service on every incoming case, establish coverage for each type of case. If the choice of method depends on the type, show how staff can recognize it in time to choose. For a target such as serving 90% within a day, identify the incoming cases counted and the share the proposed routing and available staff can serve on time. Give the grounds for that share under the expected case mix, including uncertainty when it is estimated. Preserve protections that apply to each case. A partial service can identify the cases it accepts and what happens to the others. Permitting either method on any case needs grounds for both methods across the promised cases.
An option is dominated when another feasible option is at least as good on all consequential comparison characteristics and better on at least one, under the stated comparison. If each option has an established advantage over the other on a different characteristic, preserve the trade-off. Check that the evidence for the same operating use admits at least one joint scenario. Conflicting records require clarification before they can support this comparison. When every admissible scenario gives a method a dominating rival, it can be ruled out. Identifying a particular replacement is a separate decision. If one admissible scenario rules it out and another leaves it on the front, its standing is open. An option belongs to the non-dominated set once domination by every feasible rival has been ruled out. The authorized decision maker can choose among them by an explicit priority or justified trade-off. For example, earlier service may justify a higher payment; a weighted score cannot make a breached recovery condition acceptable.
Increase comparison effort when its attainable contribution warrants the burden. If every option needs the same staffing condition, a conditional comparison can show what the options would deliver. Establish that condition before relying on any option as executable; detailed scores can wait if they would add little.
OPS.17:4.4 - Compose compatible moves and state the usable result
Several moves can serve one operation. Readiness-based admission can coexist with case discretion and a reliability stop rule. Check the shared subject and the points at which one rule changes another rule’s permission, priority, resource use or stopping condition.
Resolve a consequential conflict before using the combination. An urgent incident may override a WIP policy under an existing service authority. The exception needs the displaced work, remaining protected conditions and recovery action to be clear. A general “urgent” label cannot supply those facts.
Return the selected use and the actual level of support: an applicable established method, a conditional alternative, a traceable candidate account with an unresolved operating claim, or an unsuitable use with its reason. On the available basis, the repertoire can retain current practice, keep or revise a candidate account, or reject a proposed use. Preserve the gap needed by a later stronger use in that same return. Keep any selected first action, its conditions and evidence limits, burden and reason to reopen close to the consequential choice. An existing operating note or method description can hold this result; maintaining a second catalogue adds value only if someone uses it to choose work.
OPS.17:4.5 - Refresh the affected method claim
Reconsider a method when a relied-on condition changes, its operating result deteriorates, or a credible alternative changes the comparison. Identify which claim or use the change affects. Reassess that part of the repertoire. A change in customer acceptance can affect a service forecast while leaving readiness checks useful.
Use A.3.1.MV when the reusable semantics change: inputs, operations, applicability or result may define a Method variant. Keep changes to the description, supporting tool and one local departure distinguishable. Preserve evidence only for the claims and conditions it still supports. A combination of previously admitted methods needs its own evidence where their interaction changes the claimed result.
Use the available qualified evidence, estimates and judgement to complete the comparison needed by the decision maker, or to document the proposed method’s origins and unresolved claims. Retain the adequate incumbent or bounded candidate account with its actual gap when no further inquiry can make a worthwhile attainable contribution. Use B.1.5.CM for the status of a proposed whole and C.11.MV for its practical worth. For admission, compatibility, fit, transfer or permission for operating use, retain the separate grounds the claim requires.
When an unresolved operating effect matters to the decision or its grounds, compare the attainable contribution of a new trial question or evidence acquisition with its whole burden: design, performance, interpretation, delay and displaced operating Work. Select it only when that contribution is obtainable and worth the burden. For a selected trial, return the effect to observe, protected conditions, authority, stop and comparison basis. When the question concerns competing explanations, include the observation that could distinguish them. A.3.1.WT can guide that trial. The repertoire choice itself establishes neither that the candidate was performed nor that it improved service.
OPS.17:5 - Archetypal Grounding
OPS.17:5.1 - PumpWorks chooses what to change
This constructed case concerns the engineering test service, PumpWorks-ControlServiceOps. Its board includes release candidate R42, incident I73, safety question S19 and provider change P8. They are unlike matters requiring different actions. Four packages are ready for testing and need eight rig-hours.
A historical forty-hour rig log contains twenty execution hours, four setup hours, four unavailable hours and twelve hours with no eligible job. The next service window has six usable rig-hours. The team compares three responses:
| Response | What the evidence supports | Result of the comparison |
|---|---|---|
| Extend the rig window immediately | The four ready packages exceed the current window; more usable time could help this peak. Historical idle time does not remove that fact. | Keep a capacity alternative for OPS.10 and OPS.13, conditional on actual access, qualified cover, rework and the service horizon. |
| Admit only test-ready packages to the rig queue and make the next eligible package visible | The board count mixes unlike matters; the log also shows lost opportunities when no eligible package was available. | Select the existing readiness criteria for queue admission and make readiness timestamps available for the next operating review. |
| Treat the rig as the persistent constraint and impose a new protective buffer | The supplied log does not settle whether readiness failures, peak demand or rig access limits accepted service over the relevant horizon. | Return the constraint question to OPS.9 before choosing the buffer policy. |
The result combines a usable admission move with an unresolved capacity choice. It does not erase the four-package peak. Readiness and rig-access evidence answer different parts of the problem, so both remain in the repertoire.
For the next window, use the established readiness criteria to populate the test queue; compare the six-hour plan with any authorized extension using OPS.13; reopen constraint protection if matched demand, readiness and rig-use histories show the rig consistently limiting accepted service. S19’s field-release decision remains with the authorized safety and release practitioners. A permission for laboratory testing has the scope supplied by those practitioners.
OPS.17:5.2 - A hospital continues an evolving discharge case
In a constructed hospital service, a standard checklist works for the recurring discharge subprocedure, but a newly discovered home-support need changes one patient’s case. Repeating the checklist cannot decide the next action. The practitioner compares a fixed sequence with conditional case planning.
The local care plan requires a qualified clinical decision and confirmation of necessary home support before discharge. The selected case rule allows the responsible practitioner to coordinate the required assessment and home support in the order the situation permits, while keeping both conditions visible. A change in support can reopen planning. The standard medication-check subprocedure remains applicable when the case reaches it.
This is a method comparison about continuing the case. The clinical judgment and the patient’s actual readiness come from their own qualified work. The case account supplies the conditions and the evidence needed by the operating decision.
OPS.17:5.3 - Faster AI drafting changes the constraint
Suppose an assisted drafting service generates twenty candidates per day while qualified readers can accept six. A tool update raises generation to sixty; the acceptance capability stays at six. The old rule of keeping every generator busy now adds unaccepted drafts to the queue; reviewing more of them would add reader work.
Compare a controlled generation rate, extra qualified acceptance capacity, and a changed acceptance method. Limiting starts to the demonstrated acceptance capacity can be a current operating response. The other two choices need capability, burden and quality evidence. OPS.12 checks the transferred reading burden, OPS.13 qualifies the service commitment and OPS.18 supplies the acceptance and reliability conditions.
The repertoire refresh concerns the claim that more generation improves accepted throughput. A.3.1.MV distinguishes a changed generation method from a support-only update. That distinction preserves what existing evidence still supports without assuming that either kind of update improves the whole service.
OPS.17:5.4 - A current comparison and a later worthwhile trial
For a later PumpWorks decision, admitted Method R continues to meet the package-admission requirements for the same permitted use. Proposed N combines its readiness check with a different sequencing rule. The sources and proposed interaction are traceable, but whether N preserves the permission-expiry hold while reducing repeat checks remains unsupported. No rig slot or trial permission is available before the decision window. The operating note retains R for current use and N as a candidate account with that precise gap. This completes the current comparison and lineage return.
Later, twenty-four planned package admissions make the repeated checking burden consequential. N now has a credible estimated saving of ten to fifteen minutes per admission, but preservation of the permission-expiry hold is still uncertain. A comparison of R and N on representative ordinary and expired-permission inputs can change the choice. A rig slot, qualified people and the appropriate trial permission are available. Design, performance, interpretation and return together need three of five available hours and displace no required operating Work; the estimated four to six hours saved across the planned admissions can justify the three-hour inquiry, given its ability to check the required hold.
The team selects the bounded comparison, with the permission-expiry hold as a required result and a stop if supplied support or permission ceases. R remains selected pending the result. The trial permission does not supply Method admission or authority for normal service use. Any later fit, transfer or causal claim still needs evidence adequate for that claim.
OPS.17:5.5 - An incident exception that does not repeal the start limit
Use the constructed PumpWorks choice in OPS.2:5.2. Recover the two rules before combining their labels. The normal rule chooses the oldest ready package; the incident rule changes order only when a supported response window would otherwise be lost. Both still require current readiness, permission, an available performer and room under the active-work limit.
At 09:00, T8 occupies one of two slots. I73-D can use the other with E18, while older P8-P can wait until its authorized afternoon review. The incident lead approves the exception and the resource owner confirms the displacement. The combination therefore starts I73-D without interrupting T8 or creating a third slot. If both slots were already occupied, the exception alone would not authorize another start: a safe, permitted completion or stop and a new capacity decision would be needed. Merely moving a suspended card out of sight would not free a still-occupied resource.
At 09:50, unavailable field contact removes the ground for reserving E18 for live verification. Keep the readiness and WIP rules, close only the unsupported exception and reconsider the eligible work. The combination costs the exception decision and its expiry check; when ordinary ready order already preserves the response window, keep that cheaper rule.
OPS.17:5.6 - Repeated support changes the knowledge and then the service
Consider a constructed service helping project teams import records into a shared platform. A qualified specialist has established that, for platform version P4 with a particular permission setting, duplicated rows on screen are a display problem: the stored records remain unique, and the documented view refresh restores the display. The current manual calls this a stale view. Users search for duplicate imports and often miss it. A different P5 import format has produced a similar report, but its mechanism and remedy remain unresolved. The current routine sends requests to specialists and batches manual updates at month end; it leaves later responders repeating already completed distinctions.
The service lead compares four moves for the next month: retain the current manual and expert response; improve access to the known answer; use KCS to maintain answers through subsequent service work; or change the platform. Bulk article production would not distinguish the two configurations. Immediate platform replacement would assume a wider cause and benefit than the supplied evidence establishes.
For P4, the specialist first checks the requester’s environment against the supported conditions. The answer can remain in the maintained manual. A discoverable entry associates the user’s duplicate-row wording with that answer and its P4 permission condition. Its resolution states the applicable refresh and the expected result: one displayed row for each stored record. The service interaction retains which edition was used and whether that result occurred. The reusable entry need not include the team’s private project data. This small access correction is enough for a familiar matching case.
The P5 request changes the selection. Similar wording does not make the P4 answer applicable. Preserve the new environment and unresolved question, and obtain the appropriate platform investigation. The known P4 resolution stays usable. The service responders can apply the KCS workflow, and their case-handling allocation includes capturing relevant context and linking the answer used. The lead selects that workflow for continuing support so that developing answers and their conditions become available during service work, instead of waiting for the monthly manual revision. The full source techniques in :4.2.1 supply that work. The choice provides a way of handling the gap, not a newly established P5 remedy.
The service already has a small, allocated maintenance interval that can supply the P4 access correction. Proposed weekly analysis across cases needs additional qualified time, while current response commitments occupy the remaining specialist capacity. The lead keeps the useful local correction and obtains a separate contribution or changes the relevant commitment before promising recurring analysis. Expected future savings cannot supply that missing hour.
Suppose later observations show that matching P4 users obtain the right answer but still incur substantial effort repeating the workaround. The next comparison concerns removing that burden through a platform change, changing the service offer, or retaining the workaround at its actual cost. The product owner needs the affected conditions and receiving burden; the engineer must supply the causal explanation and proposed remedy. OPS.22 interprets the supported service result, and OPS.16 is used if the selected response changes a reusable operating method. Better article retrieval remains useful, but it no longer answers the whole improvement question.
Now change the performer. A corporate agent configuration is qualified to distinguish the supported P4 condition, use the current answer, perform the permitted refresh and check the resulting display. It can replace the corresponding human service performance. P5 remains outside that qualified use until a suitable answer and performer are available. The replacement also needs to preserve error detection: if the agent merely repeats the article while never noticing a failed result, the previous specialist’s corrective contribution has been lost. Obtain an adequate outcome check or other qualified assessment for that gap; human approval is needed only where the particular judgement or authority requires it. If a qualified agent obtains an answer without using an article, preserve the actual basis rather than inventing an article-use event.
After the change, assisted contacts fall from 40 to 12 per interval and the system records 30 agent interactions. The difference is 28 contacts; it does not establish 28 avoided issues or attribute the change to the agent. One issue may span several interactions, and a failed answer may never return as a ticket. The KCS self-service measurement treatment helps recover the relevant issue population, observed outcomes and unobserved part. Bring that bounded account to OPS.22 and compare the receiving effort and service mix as well as contact counts. KCAE.EVAL can examine the access contribution within that whole comparison.
A later policy change forbids the old refresh for one protected class of records. The responsible policy authority supplies the effective rule. The service revises the affected answer and uses KCAE.CHANGE to remove or mark stale dependent current advice. Historical correctness of the P4 diagnosis remains different from permission to act now. A recipient’s personal assistant must likewise obtain its own permitted access and action scope; the corporate agent’s grant does not travel with a copied answer.
When a person wants to learn the diagnosis, use HCD to arrange the needed learning. A claim that the person has acquired the capability needs evidence from their own performance. If independent practitioners instead want to establish a novel shared method, CB.14 can organize that joint undertaking and its professional contributors; the frequency of support questions cannot establish the new method. These changed purposes preserve the useful service-knowledge contribution while changing what else must be obtained.
OPS.17:6 - Bias-Annotation
People who have invested in a school or tool can find its benefits easier to see than its operating costs. Include current practice and a simpler adequate response, and establish where the proposed gain would create additional work. Use measurements that cover that burden or obtain an affected practitioner’s account where the burden is known through their experience.
Available telemetry also favors measurable activity over accepted service. Inspect omitted work, blocked cases and receiving practitioners’ effort before choosing comparison characteristics. The repertoire can remain small when those observations identify the only live choice.
OPS.17:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The choice has a working purpose. | The Work family, receiving decision, discrepancy and horizon can be recovered. |
| Candidate content is actionable. | Inputs, operating moves, first result, needed capability/support and source limits are clear. |
| The comparison preserves feasibility and preference. | Protected conditions are checked before trade-offs; consequential differences and unresolved preferences remain visible. |
| Composition is usable. | Shared conditions, exceptions, displacement and stops are compatible for the selected use. |
| The returned claim has appropriate support. | Supported uses, current candidate accounts, actual evidence gaps and any selected worthwhile attainable trial are distinguished. |
| Refresh can be directed. | A changed condition can be traced to the affected method claim and its receiving decision. |
OPS.17:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Choose a school from a general maturity score. | Compare its actual moves against the current service problem at comparable adoption effort. |
| Protect the apparently busiest resource. | Establish which mechanism limits the named accepted result and horizon before choosing the protection. |
| Add an expedite lane while claiming an unchanged WIP policy. | State the exception authority, displaced work and recovery, and requalify the combined policy. |
| Keep evidence attached to a method name after its conditions change. | Reassess the affected applicability or effect claim and retain unaffected evidence. |
| Call a promising combination proven because its components are familiar. | Examine the available interaction evidence and keep the unproved claim as a gap in the current candidate account. Obtain more operating evidence only when its attainable contribution is worth the whole burden for the receiving decision. |
OPS.17:9 - Consequences
Practitioners can reuse a bounded operating move without importing a whole school’s objective or record system. The repertoire also makes changed conditions easier to address: the team can revise one admission rule or acceptance assumption while retaining useful neighboring methods.
The comparison takes effort, and some effect claims remain uncertain until local use. Maintaining only decision-relevant alternatives and finishing the supported comparison limits that cost. Further inquiry is selected for the contribution it can make at its full cost. Broader comparative effectiveness remains an empirical question.
OPS.17:10 - Rationale
Method-level comparison preserves the connection between a working problem and the action intended to change it. It is especially useful where several traditions overlap in vocabulary but act on different objects: a ready queue, a case, a scarce resource, a service-event population or a cash consequence.
The separate feasibility and preference steps preserve non-negotiable conditions while allowing a real choice among useful alternatives. Review then follows the affected claim, making evidence reuse possible without treating the method as timeless.
OPS.17:11 - SoTA-Echoing
The practice question is how to select and maintain operating methods when demand, constraints and evidence change. The cases combine work control, case continuation and evidence for the receiving decision where their conditions fit. Selecting the contributions separately preserves the ready-queue move, peak-capacity question, case discretion and acceptance bottleneck that whole-school adoption can obscure.
| Source contribution | Adopted or adapted move and serious alternative | Change in this pattern and limit |
|---|---|---|
| The Kanban Guide 2025.5 | Adopt explicit workflow boundaries, WIP control and elapsed-time evidence; compare with an unrestricted start policy. | Sections 4.2–4.4 require the item boundary and the consequence protected by a limit. The guide’s knowledge-work metric set is not imposed on every method. |
| Steve Tendon’s The Book of TameFlow (2022), pp. 25–27, 135 and 142, and Donald Reinertsen’s The Principles of Product Development Flow (2009), chapters 2–9 | Adapt constraint protection and cost-of-delay questions; compare with maximizing each resource’s utilization. | The PumpWorks comparison needs a diagnosed limiting mechanism and an actual service horizon. These are historical mechanisms; their age or continued use does not establish superiority. |
| CMMN 1.1 and the DCR condition/response line | Adopt explicit case conditions and permitted discretion where a fixed sequence cannot cover the evolving facts. | The hospital case preserves obligatory conditions while allowing a different next action. A notation does not supply clinical authority or evidence. |
| SRE service objectives, NIST process monitoring and lot acceptance | Select evidence by the operating question; compare with one aggregate quality dashboard. | Section 4.2 distinguishes service loss, recurring variation and lot disposition, with OPS.18 as the receiving control method. |
| ACCA relevant-cost comparison and throughput accounting | Retain constrained-resource contribution and incremental cash as different comparisons; compare with a general local-efficiency ranking. | Section 4.3 preserves horizon, actual costs and accepted demand. OPS.14 develops the financial consequence; statutory or investment uses need their own methods. |
| NIOSH’s hierarchy of controls for Total Worker Health | Prefer removal or redesign of harmful conditions to relying first on individual coping. | Feasibility and the OPS.12 receiving result preserve affected groups and supplied protections. |
| Consortium for Service Innovation, Knowledge-Centered Success practices guide, titled 2027, and its edition explanation | Use knowledge development within service work when an adequate manual or direct provider no longer supplies the needed continuing result. Compare access correction, knowledge correction and a change to the service. | Section 4.2.1 directs the professional execution to the complete source treatments; :5.6 develops the operating selection and returns under changed conditions. The guidance specifies professional practice. An estimate of local benefit needs evidence from the particular service. |
These sources contribute different strengths: formal rules, practitioner guidance, technical models and worked financial reasoning. The repertoire preserves those evidence limits. Reopen a selected claim when a better-supported competing move, changed source meaning or changed operating condition affects the choice.
OPS.17:12 - Relations
OPS.5, OPS.6, OPS.8 and OPS.9 supply the concrete admission, continuation, queue and constraint questions for which a repertoire entry can be selected. OPS.12–OPS.15 and OPS.18 supply human-condition, service, financial, account and control results needed by particular comparisons. Their use follows the live question.
For the service-knowledge choice, the KCS treatments linked in :4.2.1 supply the professional operations. The Knowledge-Corpus Access Engineering framework supplies KCAE.MEMORY, KCAE.CHANGE and KCAE.EVAL for retaining useful episodes, maintaining current knowledge and assessing the access arrangement. OPS.22 receives the service interpretation; CB.14 and HCD receive a joint repertoire or human-learning question when that is the intended result.
A.3.1.MV guides maintenance of Method variants and the evidence they can reuse. A.3.1.WT supplies a trial method for a selected worthwhile and attainable local comparison; A.3.1.FT and C.11.MV address fit and worth where those judgments are required. The full operating-Method-change question of OPS.16 and cultural continuation question of OPS.20 remain distinct from maintaining this repertoire.
Use FPF A.3.1 for a Method, A.3.2 for its description and A.15.1 for performed Work when the comparison relies on those claims. C.16 and G.5 support meaningful comparison characteristics and selection among alternatives. A.11.OP limits additional collection or apparatus to what contributes to the decision, needed assurance or recovery.
OPS.17:End
OPS.18 - Control Operating Quality and Reliability
Status: Stable
OPS.18:1 - Problem frame
Use this when an operating result may no longer meet its requirement, observed service failures exceed the agreed allowance, a recurring process changes, a lot needs acceptance or an incident raises a containment, recovery or recurrence-prevention question.
Begin with the result at risk, the affected population or configuration and the applicable requirement. Use evidence suited to the question. State what it establishes, including any scope or uncertainty. If a response is needed, identify the available action, authority and conditions, or what prevents a decision.
This pattern governs operating decisions about quality and reliability. A monitoring account is one input. A qualified product requirement, clinical decision, statistical method or engineering acceptance result may be another. If the question is only how to define and reconcile observations, use OPS.15. If a current response policy and adequate evidence already settle the action, apply them directly.
For example, twelve nonconforming items in a sample can trigger investigation under a process-monitoring rule. A lot-disposition decision still needs its own acceptance basis. Likewise, exhausting a software service’s error budget can pause discretionary changes while urgent restoration continues under the responsible authority.
OPS.18:2 - Problem
Different quality questions are often compressed into one status: the process looks stable, the customer objective was met, the lot passed or the service is restored. Each statement needs different evidence and supports a different action.
A dashboard can therefore look satisfactory while the actual service remains impaired. The opposite failure reacts to every fluctuation as a process change, consuming effort and destabilizing work without a suitable monitoring basis.
OPS.18:3 - Forces
| Force | Practical tension |
|---|---|
| prompt response and false signals | Earlier detection can help containment while unsuitable thresholds create unnecessary interventions. |
| stability and acceptability | A stable process can repeatedly produce results that fail the requirement. |
| aggregate service and local consequence | A good average can hide an affected customer group or a short severe incident. |
| restoration and causal understanding | Service may be recoverable before the cause is fully established, while recurrence prevention still needs investigation. |
| continuity and protected conditions | Urgent recovery work requires the capability, authority and protections of its actual operation. |
OPS.18:4 - Solution
OPS.18:4.1 - Recover the result, requirement and available action
State the operating result at risk: conforming output, correct responses, timely service, availability or restored operation. Recover the relevant population, configuration, period, requirement and consequence of failure. Name the authority for continuation, containment, acceptance and restart where those decisions differ.
Use the actual requirement. A product specification, an agreed service objective and a statistical control limit answer different questions. A control limit describes variation under its model. A requirement states what the result must satisfy. Recover each from its appropriate basis.
If a known violation already calls for a protective action, take that action under the current authority and pursue any diagnosis or recovery result still required. A broad data analysis is unnecessary before a response already required by the observed condition.
OPS.18:4.2 - Select the evidence branch
| Current question | Evidence method | First operating use |
|---|---|---|
| Has a recurring process changed from its established behavior? | A suitable statistical monitor with a qualified baseline, sampling rule and response policy. | Continue observation or investigate and contain the affected process/result. |
| Is event-based service meeting its objective? | Definitions of good and eligible events, observation coverage, reporting window and permitted loss. | Report the result against the objective. When a response is needed, apply the authorized policy or identify the missing decision. |
| Should a particular lot or result be accepted? | Its qualified acceptance plan, defect definitions, sampling basis and relevant risks. | Accept, reject, segregate, rework or obtain the missing acceptance result. |
| Can an impaired service be restored or restarted? | Evidence of the failure, containment or repair, and the required restart conditions. | Restore service when its conditions hold under the appropriate authority. Continue an investigation if the remaining question requires it. |
| What prevention does an incident or near miss need? | Reconstructed events, material explanations and sufficient support for feasible protective measures. | Select and verify prevention under :4.4, retaining the limits on the causal conclusion. |
Use the branches whose results affect the response or the grounds for relying on it. A monitoring signal, lot acceptance and authorization to restart each need evidence for that particular conclusion.
For recurring variation, check that the observations are comparable, the baseline is appropriate and the model fits the data. Changing sample size, seasonality, clustering, rare events or dependence can change the required monitor. When a simple chart is inadequate, use an applicable qualified design, develop one within your competence or obtain specialist help. Establish the defect or result definition, sampling, grouping, time order, baseline, plausible dependence or drift, costs of false and missed signals, and the latest useful response. A usable design identifies its population and model, detection and false-signal performance at specified changes, observation burden, and the rule the operator can execute.
For an event-based service, define the good and eligible events at the service boundary that matters to the recipient. Check omitted events, important subgroups and observation delay. A fast failure can require a timely alert before an end-of-window aggregate is available.
For acceptance, recover the lot or item, what counts as a defect, the sampling/inspection method, and the consequences of accepting unacceptable output or rejecting acceptable output. Obtain the qualified plan where it is missing. An operating practitioner can use a supplied plan without deriving its statistical design anew.
OPS.18:4.3 - Interpret the observation within its evidence limits
Calculate the selected quantity from its declared population. Use OPS.15 when event identity, coverage, time or missing observations need repair. Preserve any consequential uncertainty in the control decision.
A process-monitoring signal supports the action specified by its policy; it does not identify the cause by itself. An observation within the limits can still violate a product requirement. A capability claim needs the relevant stable-process and specification basis.
An error budget expresses permitted service loss for a stated objective and population. Compare observed loss with that allowance, then apply the authorized policy. Protected safety, human or clinical conditions remain applicable regardless of budget remaining.
A sample acceptance result supports the named lot decision under its plan and risks. It does not establish that every item conforms, that the process is stable or that a known failure mechanism has been corrected.
OPS.18:4.4 - Carry out containment or recovery and preserve continuing service
Select an action within the available authority: continue with observation, segregate affected output, pause a risky change, adjust admission, restore a known workable configuration, rework a lot or request the needed professional decision. State the affected scope and any service that must continue.
Establish that the required capability, access and human protections are in place. Obtain any missing contribution before starting work that relies on it. Use OPS.12 and OPS.13 if recovery competes with existing service or relies on extra cover. An urgent label can identify priority; the actual assignment and authority determine who may act.
Where containment restores service before the cause is known, state what remains unresolved. Enter the following inquiry when prevention still needs an explanation. Extending a correction to new operating conditions requires support for its protective effect there; a stronger causal claim needs evidence for that claim. Reuse sufficient existing results, and apply a qualified correction directly when they settle the action.
- Reconstruct the incident. Recover the failed result and requirement, affected occurrences and configurations, sequence, effects and containment already performed. Use sources that cover the events in question, such as observations, permitted records or participants’ accounts. Seek a missing contribution when the reconstruction needs it. Distinguish observations from inferred links and identify missing facts that could matter to prevention.
- Develop the material explanations. Follow contributing conditions beyond the immediate symptom, allowing several interacting conditions or rival accounts. Use B.5.2 when plausible explanations still need to be developed. For a disputed link, identify the existing observation, established mechanism or attainable test that could support or challenge it. C.28 helps qualify the causal conclusion; domain knowledge and evidence must supply the links in this incident.
- Choose supported prevention. Compare retaining adequate protection, a narrow configuration or access correction, a change to the reusable way of working and a larger redesign where these are credible alternatives. Assess future exposure and avoidable consequences together with the full effort, delay, displaced service and other burden of each change. C.11 governs the choice; use C.11.CRC when the contribution of a finite change to the present arrangement needs that comparison. Zero loss in a near miss does not remove the exposed future consequence.
- Assign and verify the chosen change. If a change is selected, name who will deliver it, the required result and its completion conditions. A recurring operating Method change belongs to OPS.16; choosing among ways to retain in an operating repertoire belongs to OPS.17. A local configuration, access or maintenance correction can finish as that correction. Verify completion separately from the restart conditions and later recurrence observations in :4.5.
Require sufficient support for the proposed protection under the relevant explanations that remain plausible. If they all support the same available correction, choosing a final causal account is unnecessary for that prevention decision. Retain the unresolved explanation wherever it limits a claim or later use. Obtain another observation when it can change the prevention, its permissibility or burden, or what the evidence warrants saying. If the worth or feasibility of that inquiry is itself unsettled, use C.11.DUA. Applicable protection and evidence requirements continue to govern the action.
OPS.18:4.5 - Verify restart and choose the next observation
Recover the condition under which service, normal production or discretionary change may resume. Use current evidence that establishes the required condition, or obtain the missing result. Depending on the condition, the basis can be applicable test evidence, a confirmed working configuration, restored service behavior, qualified acceptance or another required result.
Check the observation’s scope and time. A restarted process, a new reporting period or an empty incident queue is not itself evidence that the defect was corrected. Preserve residual uncertainty and a response if the condition fails again.
Choose follow-up from the consequence and detection need. Large isolated departures, small persistent drift and rapid incidents may need different observation rules. Retain enough evidence for the continuing decision, and end collection when its result no longer serves a decision, required operating claim, assurance or recovery.
Return the supported quality or reliability conclusion, its evidence and the affected population or configuration. If an operating response is required, state the action, its authority and any restart or monitoring conditions. The existing account or display can carry the result.
OPS.18:5 - Archetypal Grounding
OPS.18:5.1 - A process signal calls for containment and investigation
In this constructed recurring inspection operation, the supplied stable reference proportion of nonconforming items is p₀ = 0.02. Samples contain n = 200 independent, comparable items under the stated binomial basis. The local monitoring policy uses a three-standard-deviation p-chart rule and calls for segregation of the affected output and investigation when the upper limit is exceeded.
The upper limit is p₀ + 3√(p₀(1 − p₀)/n) = 0.02 + 3√(0.02 × 0.98 / 200), approximately 0.0497, or 4.97%. The corresponding lower value is negative and is truncated to zero.
The next sample contains twelve nonconforming items: 12 / 200 = 0.06, or 6%. This exceeds the specified upper limit. The practitioner applies the policy’s containment and investigation response and identifies the sampled output, source process and current configuration.
The arithmetic establishes the signal under that rule. It does not identify why the items failed, determine another lot’s disposition or show that the process is capable of meeting a product specification. The three-standard-deviation calculation defines the limit for this rule; it does not supply an exact confidence or false-alarm probability. With this low reference rate, a claim about false-alarm or missed-detection probability needs an appropriately qualified binomial or other statistical design.
Suppose the investigation finds a changed setup condition. Returning to the earlier setup and obtaining the required process and output evidence can support restart under the responsible authority. A single subsequent point below the limit is insufficient to establish every one of those claims. A persistent smaller shift may call for a monitor such as an exponentially weighted moving average (EWMA), which retains information from successive observations, if its detection properties fit the need.
Change the sampling premise. The 200 inspected items now come as fifty groups of four, sharing one setup within each group. In this constructed return, the qualified statistical supplier establishes a bounded model for the defect being monitored: all four items in a group share its conforming/nonconforming state; different sampled groups are independent; the stable reference probability is 0.02 per group. The sample’s twelve defects occupy three groups. The count is therefore 3 of 50 independent group outcomes, not 12 of 200 independent item outcomes. The original 4.97% limit is inapplicable. With this model, its apparent trigger would correspond to at least three defective groups, with a baseline false-signal probability of about 7.84% per sample.
The operating owner needs to protect this finite campaign and decide whether a recurring-shift monitor adds a useful further result. The current product rule already holds any known defective group’s output. The supplier is asked to compare early detection with the available inspection and response time, including a persistent rise from 2% to 6% defective groups. It returns these two explicit candidate rules under the stated independent-group model and fixed baseline:
| Candidate monitoring rule | Baseline false-signal probability | Detection probability if the group rate is 6% throughout the tested observations | Delay and use |
|---|---|---|---|
| Investigate at five or more defective groups in one fixed sample of 50. | approximately 0.321% per sample | approximately 17.94% per sample | Available after that sample; often misses this small persistent shift. |
| Investigate at ten or more in one prespecified, nonoverlapping block of four such samples, 200 different groups in total. | approximately 0.748% per block | approximately 76.57% per block | Uses four rounds of evidence; it does not provide an earlier warning. |
These exact-binomial tail calculations are a constructed statistical return, conditional on the supplied model; they are not lifetime false-alarm guarantees. Repeated blocks create repeated opportunities to signal. They do not authorize changing the baseline after seeing unfavorable observations or treating overlapping blocks as independent.
Suppose the next four rounds contain three defective groups each. No individual sample triggers the first rule; twelve of 200 groups triggers the second at the fourth round. The authorized response is a wider process investigation and containment at the supported scope. Each known defective group was held when found under the independent product rule; waiting for the fourth-round monitoring result cannot authorize its release. Unaffected output still uses its own acceptance basis.
Include the whole price and reuse observations already obtained. In this finite campaign each round’s fifty groups are all its output. A qualified full screen costs forty staff-minutes per round, 160 over four rounds, and fits the service window. That adequate product-protection rule applies with or without a process monitor; the monitoring rule does not replace it. Its observations already supply the group outcomes, so do not charge for a second sample. The monitor adds two minutes per round for group/time reconciliation, 120 once for qualification/setup and twenty for the wider investigation in the supplied signal trace: 148 additional minutes, or 308 including inspection, apart from protective handling common to both alternatives. Retain direct protection alone for this one-off use when no continuing exposure or other decision needs the separate recurring-shift answer. Where that answer is useful, compare its expected contribution with these added costs, actual signal workload and missed-loss consequences. The full screen protects this output without itself establishing the process-change claim. If action is needed before four rounds, request a qualified sequential design; the ordinary normal-data EWMA limits cannot simply be pasted onto these rare grouped counts. Correlation between groups, a changed defect mechanism or an unrepresentative baseline reopens this statistical return without canceling already supported containment.
OPS.18:5.2 - Service loss exceeds the agreed budget
In a constructed software service, the objective is 99.9% successful requests over the defined window. The account includes 1,000,000 eligible requests, with success and eligibility measured at the service boundary relevant to users. The allowance is:
- 1,000,000 × (1 − 0.999) = 1,000 unsuccessful requests;
- observed unsuccessful requests = 1,500;
- budget consumed = 1,500 / 1,000 = 150%.
The observed success proportion is 99.85%. The service has exceeded the stated allowance by 500 unsuccessful requests.
Its previously authorized local policy pauses discretionary feature releases when the budget is exceeded, permits the specified urgent recovery and security work, and requires investigation of the affected service. The practitioner applies that policy, names the eligible population and affected service, and directs the authorized recovery work. Another service needs its own objective and permitted response.
A total of 1,500 also needs timely interpretation. If most failures occurred in the last few minutes or affected one important user group, the aggregate alone can understate the current incident. Inspect the relevant time and group breakdown if it could change the containment or the scope supported by the evidence.
Now suppose a calendar boundary starts a new reporting window while the failing request path remains impaired. The operation still lacks restoration evidence. Later, the recovery team restores a known working configuration, verifies the previously failing user path and obtains the live observations required by the agreed restart criteria. The responsible service owner can then decide whether to resume discretionary changes. Keep any unresolved causal or recurrence question visible.
The responsible owner uses budget consumption in the stated service policy. Independent safety and acceptance conditions still apply, and recovery work requires a qualified, authorized performer for each action.
OPS.18:5.3 - The lot decision uses its own plan
A separate constructed supplier lot arrives after the process signal above. The supplied product-acceptance plan defines the lot, defects, sampling and disposition authority. For this illustration, it specifies a random sample of fifty items and acceptance only if at most one is nonconforming. Its qualification for the actual product and producer/consumer risks belongs to the supplied plan.
The sample contains two nonconforming items. The acceptance practitioner rejects or segregates the lot as the plan requires and obtains the prescribed rework or supplier response. Even if a process chart for that producer has no current signal, the lot fails this stated acceptance rule.
If the lot had passed, the result would support its disposition under the plan’s risks. It would not settle the earlier process investigation. If the plan or its risk qualification is missing for the actual use, obtain that result before relying on this sample rule; these illustrative numbers do not provide a general acceptance plan.
OPS.18:5.4 - Human service and AI assistance need their actual result
In a hospital operation, the due-request account can show missed service times while clinical priority changes the permissible response. The operating coordinator uses qualified clinical decisions and the current service authority to choose additional cover, rescheduling or another permitted intervention. A low average waiting time cannot clear an individual case whose required condition is unmet.
After an intervention, the coordinator observes the affected service and support work under the selected continuation conditions. A clinical outcome or health-effect claim requires its own evidence. OPS.12 helps preserve human conditions when recovery work adds demand.
In an assisted production service, a monitor may show fewer detected defects after a model change while the current sample excludes difficult requests. Recover that population before interpreting the improvement. Continue or contain the affected use according to the requirement and policy for accepted outputs.
A changed model can also alter the relevant failure modes. Qualification of the current acceptance method, actual accepted results and any affected customer promises may therefore need reconsideration. A passed sample from the earlier version is reusable only for the claims and conditions it still supports.
OPS.18:5.5 - An unresolved cause need not delay a supported correction
In this constructed print-shop incident, the customer approved proof P2, but the booklets reproduce P1. Records and participant accounts establish that the operator followed the work card containing P1; P2 was unavailable at the station, and the admission check asked only whether a proof was attached. The quality rule requires the affected order to be held.
Trace how P1 reached the station and why P2 was unavailable. Two explanations remain plausible: the preparer copied the earlier attachment, or the station received it from a stale synchronized folder. The records do not distinguish those paths. Both leave the same exposed condition: production can start without checking the proof against the customer’s approved edition.
For this case, a qualified proof-control procedure is available for both paths: retrieve the approved proof through the authorized source, check its edition at the station and require first-article acceptance before releasing the order. The responsible production manager has authority and the necessary staff and access to apply it; its effort fits the continuing service commitments.
The manager applies that correction. Staff verify that P2 is available, perform the edition check and obtain the required first-article acceptance for restart. Selecting between the copying and synchronization explanations is not a prerequisite to this adequately supported response. Their difference would become relevant if, for example, a proposed automatic retrieval change protected only one path; that proposal would need the missing discrimination or a protection covering both.
OPS.16 addresses any resulting decision to change the recurring operating Method; OPS.17 is needed only for a repertoire choice among competing ways. Completion of the proof-control change is observed separately from recurrence over the later orders and exposure that the prevention claim covers. A clean first article does not establish a long-term recurrence rate.
If the edition check catches P1 before printing, no booklets are spoiled: the check has protected this order. Whether further change is needed depends on the remaining exposure and available protection.
OPS.18:6 - Bias-Annotation
Visible control limits can look authoritative even when their model or baseline does not fit the operation. Keep the required product or service result beside the monitoring claim and inspect the assumptions before extending its use.
A recent repair can also encourage early closure. Verify restored service at the affected scope, and distinguish that result from identification of the cause and evidence about recurrence.
OPS.18:7 - Conformance Checklist
| Check | Evidence sufficient for the declared use |
|---|---|
| The requested result is clear. | Its requirement, population or configuration and consequence are recoverable. If a response is needed, so is its authority or the remaining gap. |
| The evidence method answers that question. | Monitoring, service-objective, acceptance, recovery and prevention uses retain their distinct bases. |
| The observation is interpretable. | Baseline, sample or event population, coverage, time, model and uncertainty fit the claim. |
| Any selected action follows the applicable rule. | Continuation, containment, acceptance, restoration or Method change uses the actual policy and protected conditions. |
| Any restart is supported. | Evidence or a qualified result establishes the required condition at the relevant scope and time. A reporting reset alone cannot support restart. |
| Remaining work is directed. | Unresolved cause, recurrence risk, missing professional result or changed method assumption has a concrete receiving use. |
| Prevention has sufficient support. | Further discrimination is sought when its attainable result matters to prevention, permissibility, burden or a required conclusion; a common adequately supported correction can proceed with the remaining explanation explicit. |
OPS.18:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| Treat statistical stability as product conformity. | Compare output with its requirement and obtain the applicable capability or acceptance result. |
| Use a chart signal as proof of a specific cause. | Contain as required. Pursue a causal investigation when its result is needed. |
| Let an error budget authorize every kind of loss. | Preserve independent safety, human, clinical and acceptance conditions. |
| Accept a lot because the process chart looks normal. | Apply the lot’s qualified acceptance plan and risks. |
| Resume normal work when the reporting window resets. | Verify the actual restart conditions and use the applicable continuation authority, obtaining a decision when the conditions require one. |
| Reuse an old monitor after the population or failure modes change. | Requalify the affected observation and detection method for the new use. |
OPS.18:9 - Consequences
The practitioner can connect quality and reliability evidence to a concrete operating response. The action remains scoped to the affected output, service or configuration, while necessary service can continue under its own conditions.
Monitoring and acceptance can incur false alarms, missed failures, inspection cost or delayed service. Recovery can restore operation while leaving a cause unresolved. Selecting the method and evidence by consequence makes these trade-offs visible for the operating question.
OPS.18:10 - Rationale
Monitoring, acceptance, restoration and prevention regulate different moves. Selecting the evidence from the current decision preserves the meaning of a statistical limit, a product requirement, a service objective and a supported protective change.
The separation between containment, restored service and causal knowledge also supports proportionate action. A practitioner can act on sufficient operating evidence while obtaining the stronger result needed for prevention, wider use or a more consequential commitment.
OPS.18:11 - SoTA-Echoing
Select quality and reliability evidence for the question being answered. A monitoring rule signals observations that meet its criterion under the stated model, a service indicator measures the agreed outcome, and acceptance and restart each require their own criteria. These distinctions determine what follows in the worked cases.
| Source and practice question | Selected move and alternative | Operative contribution and limit |
|---|---|---|
| NIST proportions control charts and process stability | Use a monitor suited to recurring variation, instead of reacting to every raw fluctuation. | Sections 4.2–4.3 and 5.1 preserve baseline, population and model. The original three-sigma signal and the changed group-count return answer different sampling conditions; exact tail risks are stated only for the latter’s supplied model. |
| NIST EWMA guidance | Consider a memory-bearing monitor when persistent small shifts matter more than one large point. | Sections 4.5 and 5.1 retain detection delay and assumptions as reasons to change the method. NIST’s ordinary EWMA limits assume independent data and their tabulated design assumes normality; grouped rare-event monitoring needs a qualified design, not merely the chart name. |
| NIST process capability and acceptance sampling | Select specification/capability or lot-disposition evidence for that question, instead of reusing a monitoring verdict. | Sections 4.2–4.3 and 5.3 keep the lot, defect and producer/consumer risk basis separate. |
| SRE service objectives, error-budget policy and alerting on SLOs | Relate user-relevant observed loss to an agreed action and timely detection, instead of using infrastructure availability alone. | The service case adopts the loss calculation and policy relation. Local targets, exceptions, authority and restart evidence are supplied for the actual service. |
| Ries, The Lean Startup (2011), chapter 11; Lean Enterprise Institute, Five Whys; Google SRE, Postmortem Culture (2016) | Recover contributing conditions and assign supported prevention, instead of stopping at the first symptom or treating a question count as causal proof. | Sections 4.4 and 5.5 adapt incident reconstruction, knowledgeable participation, countermeasure selection and follow-up. The historical accounts and practice guidance do not prove a particular causal chain or a recurrence reduction; those claims need their own evidence. |
The NIST handbook provides standing technical models. The SRE Workbook supplies software-service guidance and a dated 2018 policy example.
For an individual known failure, immediate qualified containment can be the stronger response than developing a new statistical monitor. For recurring uncertain behavior, a designed monitor can reduce reactive disturbance and improve timely detection. Reopen the selected method when the population, baseline, loss consequence, detection need or authorized policy changes.
OPS.18:12 - Relations
OPS.15 helps construct the observation account when its subjects, coverage or definitions are unresolved. OPS.4 guides shared attention to qualified operating state. OPS.5–OPS.7 guide admission, continuation and attention to aging work when those actions depend on the control result.
Use OPS.12 for human conditions and OPS.13 for service commitments and resource choices affected by containment or recovery. OPS.14 helps compare consequential operating and financial alternatives. OPS.16 evaluates a change to an operating Method; OPS.17 compares and refreshes the repertoire of ways available for operating work.
B.5.2 helps develop rival explanations of the incident; C.28 qualifies their causal support. C.11 and C.11.CRC support the choice and whole-burden comparison of preventive changes. C.11.DUA enters only when the contribution or feasibility of a requested inquiry remains in question.
FPF C.16 governs the measures and statistical assumptions relied on, and A.10 preserves evidence reach. A.11.OP limits additional monitoring or records to their decision, assurance or recovery contribution. Use the qualified acceptance, protection or restoration result for the domain. Obtain it from the appropriate source when it is missing.
OPS.18:End
OPS.19 - Reconcile Simultaneous Operating Work Across Cases and Scales
Status: Stable
OPS.19:0 - Use This When
Use this Method when several kinds of operating Work are present together and a locally sensible choice can harm another case or service, worsen an operating result, or move a result into a horizon where its consequence changes. Typical moments include keeping a busy resource utilized while incident coverage is thinning, completing one case sooner by moving delay to a shared acceptance queue, or starting improvement Work while current commitments and human recovery still need protection.
The first useful result is a short cross-scale operating account and decision. It names the local choice, the simultaneous Work and relations on which it depends, the conflicting results and measures on their own subjects, feasible alternatives, authority and protection conditions, the selected reconfiguration or bounded continuation, and the condition that reopens the decision. It may instead return one exact unresolved conflict when a necessary result or authority is missing.
Start here only when the decision genuinely crosses subjects, operating scopes, or time horizons. Use OPS.8 for one queue-policy question, OPS.9 for one current-constraint question, OPS.10 for one capacity-and-service comparison, and OPS.11 for one interacting-structure coordination question that those patterns can settle directly. Use current C.32.MWA.PP when the primary question is comparison of Method or candidate-account co-use rather than reconfiguration of continuing operating Work. Use OPS.16 when the current object is one operating Method change, and OPS.20 when the current claim concerns continuation or change of enacted practice in a practitioner population.
OPS.19:1 - Problem frame
Continuing operation brings several Work wholes and decision structures together. Customer or patient cases progress while shifts provide service, queues and constraints are coordinated, incidents or recovery Work consume margin, financial-control Work changes the feasible horizon, and Method-improvement Work may be planned or performed. These wholes can overlap without becoming parts of one master process.
A local measure sees only its own subject and scale. Rig utilization can rise while case completion, cash timing, incident resilience, or participant recovery worsens. Faster case admission can overload inspection or release. A change programme can meet its milestone while the continuing service loses a protected condition.
Here scale means the subject, operating scope, or time horizon on which a result is claimed. It does not imply a universal hierarchy of team, department, organization, or enterprise levels. Select the scales and relations needed to make or justify the current operating choice.
OPS.19:2 - Problem
Operations teams often receive several correct local accounts that recommend incompatible actions. A queue report says start now, a capacity account retains a recovery reserve, a service account says hold, a financial comparison favors deferral, and an improvement plan needs the same specialist. Combining the numbers into one dashboard does not reconcile their subjects, horizons, evidence, or authority.
An exhaustive enterprise model can describe many structures while leaving the practitioner unable to decide what to start, hold, reconfigure, or return. The practical need is a bounded decision that preserves each material result, exposes moved burden, and stops when an indispensable premise is missing.
OPS.19:3 - Forces
| Force | Practical tension |
|---|---|
| local action and wider consequence | A narrow choice is easy to execute, while its delay, risk, cash need, or burden may appear elsewhere. |
| immediate completion and retained resilience | Starting additional Work can consume recovery, incident or acceptance margin needed later. |
| unlike results and one decision | Service, cash, quality, human recovery, throughput, and evidence can all matter without one defensible common score. |
| simultaneous Work and sequence | Some Work has real order; other Work overlaps or remains a separate whole. One sequence can hide the conflict. |
| coordination and distributed authority | One operating decision needs several inputs, while clinical, safety, financial, service, and employment authority do not merge. |
| enough structure and timely action | Omitting a material relation makes the choice unsafe; mapping every relation delays the useful result. |
| current evidence and changing conditions | A previously justified decision can lose its basis when access, demand, commitments, support, or the evidence window changes. |
OPS.19:4 - Solution
Start with the local choice and the simultaneous Work it affects. Reuse an account that identifies the relevant relations, protection conditions and consequences across cases or horizons. If it leaves a consequential gap, establish the missing relation or identify the limit it creates. Use existing arrangements where adequate, construct a missing alternative when needed and compare materially different arrangements. Return a reconfiguration, a bounded continuation or the unresolved conflict within the available authority.
OPS.19:4.1 - Fix the operating question and exposed local choice
Name the operating System, the useful result or service that must continue, the receiving decision, the current horizon, and the exact local choice that exposed the conflict. State the local measure or reason supporting that choice and the consequence that could defeat it.
Examples are: start a third package to keep a rig utilized; release more cases into a diagnostic queue; extend a shift to clear backlog; defer inspection to protect a shipping date; or open a Method trial while incident coverage is reduced.
Reuse a current OPS.1 operating focus and OPS.3 subject account when they are available. If the subject, commitment, or decision cannot be identified, return that missing basis before comparing alternatives. If the local method already justifies the choice and no material consequence elsewhere remains to be reconciled, use its result and stop.
OPS.19:4.2 - Recover the simultaneous Work without forcing one whole
Identify the actual or intended Work whose relations matter to the decision. Check case Work, shift or continuing-service Work, queue or constraint coordination, incident and recovery Work, financial-control Work, and Method-improvement Work where they affect the choice, its grounds or its conditions of use.
For actual Work, preserve each independently supported Work whole and identify any supported parts or episodes separately. Record precedence, succession, or overlap only as relations among the identified Work. For intended Work, keep the WorkPlan and its conditions distinct from performed Work. Shared performers, timestamps, resources, labels, or diagrams do not establish parthood.
An admission–processing–inspection–delivery order can be real for one case while service coordination and improvement Work overlap it as separate wholes. Record both facts.
OPS.19:4.3 - Select the structures on which the choice depends
Select only the subjects, Work, Methods, resources, commitments, accounts, authority relations, and descriptions on which the choice or its conditions depend. Recover the exact obtaining relation or supported claim used from each structure.
Keep every process diagram, board, event log, financial model, and dashboard separate from what it represents. State what the representation preserves, what it omits, and which current decision uses it. Use C.32.MWA when the question needs several practice structures with different relations. Use its architecture evidence in the operating decision within the applicable authority.
Inspect a capable existing integrated account before assembling another. It may already preserve subjects, participants, production and coordination, resource calendars, promises and evidence. Reuse its supported results and establish any missing relation needed to compare, qualify or justify the choice. Count the cost of keeping that addition current, including specialist returns.
A compact working account can use these positions:
| Position | What to record |
|---|---|
| local choice | the proposed start, hold, sequence, allocation, or policy and the local reason for it |
| simultaneous Work | the independently identified Work wholes and only the part, order, episode, or overlap relations used by the choice |
| structures used in the decision | the cases, queues, constraints, resources, commitments, accounts, authority and descriptions whose relations matter to the choice or its conditions |
| conflicting results | each result or measure with its subject, scale, horizon, evidence, and protected condition |
| alternatives | materially different feasible arrangements, including bounded continuation and a truthful stop |
| return | authorized decision or exact unresolved conflict, together with its conditions and reopen trigger |
OPS.19:4.4 - Keep results and measures on their own subjects
State each decision-relevant result on the subject and scale it actually concerns. Case completion, total flow, service, current-constraint protection, resilience, cash, participant recovery, quality, and improvement evidence do not become one result because they appear on the same dashboard.
For every relied-on measure or claim, name its subject, scheme or interpretation, time window, evidence basis, and receiving use. Distinguish a direct observation from an association, contribution claim, forecast, or causal claim. Keep an unavailable result as a gap rather than filling it with a nearby proxy.
Use OPS.12 for human-condition evidence, OPS.14 for operating and financial consequences, OPS.15 for a decision-specific account, and OPS.18 for a quality or reliability control decision when their questions are current. Their results constrain this choice; they retain their own subjects and authority.
OPS.19:4.5 - Construct materially different operating alternatives
Compare the materially different arrangements already available, including the present arrangement and its limits. If they leave a material need, condition or conflict unresolved, try changing an allocation, sequence, start condition or service boundary to construct a practicable alternative. Check the resources, commitments, authority and protections it needs. Compare continuation, deferment, a hold or stopping where they have different consequences. If no feasible alternative can be found, state what excludes the options or which condition remains open.
For every alternative, expose where it moves delay, burden, evidence risk, cash need, service exposure, quality risk, or recovery cost. Ask which participant or operating scope receives that moved consequence and whether the required condition or authority is current there.
Preserve protected conditions before seeking a local gain. An alternative that requires unavailable access, unsupported overtime, missing clinical authority, consumed incident margin, or evidence from the wrong configuration is not yet feasible. Return the exact missing result instead of treating the alternative as available.
OPS.19:4.6 - Apply authority, commitment, evidence, and currentness conditions
Identify which operating policies can change within current authority and which decisions belong to another holder. Recover commitments, permissions, protection conditions, evidence windows, and stop rules that the selected alternative relies on.
Use C.11 for the bounded choice when the chooser, option set, rule, evidence, and authority are present. A coordination proposal, model optimum, or majority preference does not supply missing authority. A clinical, safety, legal, financial, employment, or release result remains with its professional owner.
When a required result is unavailable, decide only what can proceed without it and return the blocked remainder. Name the missing input and the decision that depends on it.
OPS.19:4.7 - Return the cross-scale operating decision
Return one of three useful results:
- Cross-scale reconfiguration. Change which Work starts or is held, or change allocation, sequence, support, or another operating relation so the material results can coexist under current authority and conditions.
- Bounded continuation. Keep the current arrangement for a named scope and interval when its consequences and protections justify doing so. A proposed change may consume a protected reserve or offer no justified improvement.
- Exact unresolved conflict. Name the incompatible results, missing evidence or authority, what can still proceed, and the result that must return before the decision can close.
Record the supported outcome, its conditions, preserved results and what would reopen it. Identify any deferred demand and who is responsible for a remaining decision. Do not infer implementation, later effectiveness, a changed Method, or cultural continuation from the decision.
Send the result to OPS.16 when trial feasibility or a protected trial condition relies on it. Send it to OPS.20 only as a candidate practice variation or consequence; that Method independently supports its population, predicate and continuation decision. Any selected intervention, needed authority or claimed later observation keeps its own basis.
OPS.19:4.8 - Keep the result short enough to use
The practitioner should be able to state the conflict, alternatives, decision, and reopen condition in a brief account. Add structural detail only when it changes feasibility, consequence, authority, or evidence reach.
Recognition is the ability to spot when a local operating choice is exporting harm or consuming another scope’s protected condition. Assurance requires supported Work and relation claims, qualified consequences, current authority, and explicit evidence limits.
The operator can identify the consequences across cases or horizons, compare feasible arrangements under their protections and return the authorized action or unresolved conflict.
OPS.19:5 - Archetypal Grounding
OPS.19:5.1 - PumpWorks: preserve incident coverage and recovery
In this constructed continuation of the PumpWorks control-service case, four ready test packages require two rig-hours each. Six rig-hours are currently available, and the retained adverse scenario includes one immediate two-hour repeat. A field incident consumes the change interval and two hours previously available from specialist E27 while exhausting the interruption reserve. No qualified relief is available for an extension.
The local utilization proposal would start all four ready packages and requires eight rig-hours. Preserving the retained two-hour repeat would require ten rig-hours, so an eight-hour plan silently displaces that repeat. The current financial comparison says only that qualified deferral of the third package is worth 700 more within the stated two-month horizon than immediate completion, while the service account protects incident coverage and E27’s recovery. No current priority, acceptance-window, or financial premise decides the fourth package.
| Decision-bearing item | Supported current fact | Conflict exposed |
|---|---|---|
| package cases and test Work | four ready packages, two rig-hours each, plus one retained two-hour repeat | two selected packages can complete and the repeat can remain reserved inside six hours; the third has a qualified deferral premise, while the fourth has no supported later disposition yet |
| incident and service Work | the incident consumes the change interval and interruption reserve | an extension removes protected response and recovery margin |
| rig and specialist resource use | the rig can appear locally available while qualified specialist support is not | rig utilization alone overstates feasible Work |
| financial consequence | qualified deferral of the third package is worth 700 more in the stated horizon | immediate completion is locally visible but financially worse under the current premises |
| proposed Method trial | its support, permission, service, and recovery conditions are not yet current | starting the trial would convert missing conditions into unsupported Work |
Compare a capable bounded integrated arrangement: its transaction account identifies the package request, promise, result and receiver; its schedule distinguishes test, incident and coordination Work, the six rig-hours, specialist E27 and the repeat reserve. The schedule fits two two-hour packages and reserves two more hours for a possible repeat. If the same arrangement also carries the third package’s qualified financial horizon and later agreement, the unresolved fourth-package disposition and E27’s recovery protection, reuse its complete return.
Where only the resource schedule is current, the needed addition is those exact receiving constraints. The available agreements and the current staffing result confirm the third package’s supported deferral and the absence of qualified specialist relief; the fourth package remains unresolved. These facts defeat an extension and keep the Method trial closed. Mapping them to the schedule costs source consultation, horizon checking and later refresh. That cost is warranted here because the proposed extension would consume a protected condition.
OPS.19 returns a bounded cross-scale reconfiguration: preserve incident coverage and E27’s recovery; complete the two selected packages and reserve the possible two-hour repeat inside six rig-hours; defer the third package to its qualified later slot; hold the fourth package’s start and return its later disposition as unresolved because no qualified priority, acceptance-window, or financial premise selects it; and keep the Method trial closed until service recovery, support, permission, and trial conditions are current. Reopen if qualified relief and access become available, the financial horizon or acceptance premise changes, a qualified fourth-package disposition basis returns, or the incident or service result changes.
This result does not decide the later Method change. It supplies OPS.16 only with the feasible trial boundary and protected conditions.
OPS.19:5.2 - Public-hospital emergency flow: bed occupancy is not the whole decision
A public-hospital emergency function can have a locally attractive bed-occupancy or diagnostic-throughput proposal while patient priority, diagnostic queues, room constraints, shift coverage, clinician recovery, and safety conditions recommend a different action. Use the applicable clinical and staffing judgments for those conditions.
The practitioner identifies the patient cases, current clinical decisions, queue and room relations, service commitments, staffing and recovery conditions, and the exact authority needed for the proposed change. A bounded result can reconfigure admissions or support only where those inputs permit it. If clinical priority, consent, safety, or staffing authority is missing, the result is the exact blocked decision and what can continue safely, not a utilization-driven substitute.
OPS.19:5.3 - AI-assisted software operation: generation rate is not release capacity
An AI-assisted software operation can raise candidate-change or ticket-completion counts while incident recovery, human review, test and assurance Work, release queues, provider or compute limits, and deployment authority remain unchanged. Model calls, tool episodes, candidate artifacts, accepted changes, release results, and user service are different subjects.
The practitioner compares the locally faster generation arrangement with alternatives that limit admission to acceptance capacity, reserve incident and recovery margin, or hold Work when provider or evidence conditions are stale. A cross-scale decision may reduce starts, reserve a compatible test environment, and return an unresolved release or assurance result. It does not infer model capability, accepted software, cultural adoption, or better service from more generated artifacts.
OPS.19:6 - Bias-Annotation
| Bias | Likely drift | Countermeasure |
|---|---|---|
| utilization bias | Busy resources are treated as the operating result. | State the useful service, case, cash, resilience, quality, and recovery consequences that can defeat utilization. |
| scale collapse | Case, shift, service, operating-System, and improvement results are added or averaged as though they share one subject. | Keep subject, scope, horizon, scheme, and evidence with every claim. |
| sequence bias | All simultaneous Work is forced into one process order. | Preserve independently grounded Work wholes and their actual order, episode, part, or overlap relations. |
| dashboard realism | A visible measure or diagram is treated as the obtaining operation. | Recover the represented subjects, relations, omissions, and receiving use. |
| scalarization bias | Unlike consequences are compressed into one ungrounded score. | Compare them through the applicable decision rule and protected conditions. |
| authority aggregation | One coordinator appears able to grant clinical, safety, financial, employment, and release decisions. | Name the actual decision holder and return missing authority. |
| action bias | Starting something is preferred to a bounded hold or unresolved result. | Keep defer, hold, stop, and exact missing return as legitimate alternatives. |
OPS.19:7 - Conformance Checklist
- Is the operating System, useful result, receiving decision, horizon, and exposed local choice clear?
- Are the simultaneous Work wholes and only their supported part, episode, order, or overlap relations identified?
- Are actual Work, intended Work, Methods, subjects, structures, descriptions, and records kept distinct?
- Does every selected structure or relation affect the choice, its conditions or its grounds?
- Are results and measures stated on their own subjects, scales, horizons, schemes, and evidence bases?
- Do the alternatives differ materially and expose moved delay, burden, evidence risk, cash, service exposure, quality risk, or recovery cost?
- Are protected conditions, commitments, authority, and currentness checked before an alternative is called feasible?
- Does the return clearly state reconfiguration, bounded continuation, or exact unresolved conflict?
- Are downstream Method-trial and cultural questions left to
OPS.16andOPS.20under their own entry conditions? - Can the receiving practitioner state the supported action or unresolved conflict, its scope and what would reopen it?
To recognize the situation, identify the material conflict and the operating scopes it connects. Assurance requires the obtaining relations, evidence reach, protection conditions, and authority used by the selected decision.
OPS.19:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Repair |
|---|---|---|
| Maximize the visible resource. | Local utilization consumes service, recovery, cash, or acceptance margin elsewhere. | Compare the resource choice with every material protected result and moved burden. |
| Treat a shared timeline as proof that distinct Work wholes are parts or successive steps of one process. | Overlap and separate Work identities are lost behind unsupported succession or part relations. | Recover each Work identity and the exact temporal or part relation actually used. |
| Balance everything in one score. | Unlike subjects, horizons, and uncertainties disappear behind weights. | Keep each consequence explicit and apply a grounded decision rule. |
| Let the dashboard define the situation. | Records and representations replace the operation and its missing facts. | Recover subjects, evidence, omissions, and current relations before relying on the display. |
| Build an exhaustive enterprise map when a smaller account already settles the choice. | Unneeded modeling work delays the useful result. | Use the structures needed to compare or justify the choice and its conditions. |
| Treat a feasible model as authorization. | Another holder’s permission or professional judgment is bypassed. | Obtain or return the exact authority-bearing result. |
| Call the reconfiguration a Method improvement. | One operating allocation decision silently changes Method identity. | Open OPS.16 only when reusable Method semantics and a bounded evidence question are current. |
| Call one successful continuation cultural adoption. | Local use becomes an unsupported population claim. | Use OPS.20 for the independently supported population and cultural predicate. Current grounds can suffice; new intervention and later evidence are conditional on the claim or selected work. |
OPS.19:9 - Consequences
The operation gains a decision that can preserve current cases, service, resilience, cash, human recovery, quality, and improvement conditions without pretending they are one measure. A bounded hold or exact missing return becomes an actionable result rather than evidence of weak coordination.
The cost is explicit recovery of several subjects, relations, evidence windows, and authority conditions. Some decisions remain partial. This cost is proportionate when a relation can materially change the choice or establish the grounds for relying on it. Leave other detail with its source.
OPS.19:10 - Rationale
Simultaneous operating Work creates a domain decision beyond generic several-structure synthesis. C.32.MWA can produce the architecture evidence, but it does not select the operating reconfiguration, apply Operations commitments and protected conditions, or return the service, cash, quality, recovery, and authority consequences.
The Method also remains distinct from OPS.11. Interacting-structure coordination can settle one concrete coupling, while OPS.19 opens when several otherwise valid operating results conflict across subjects, scopes, or horizons and must be reconciled in one authorized Operations decision.
OPS.19:11 - SoTA-Echoing
The decision is how to reconcile simultaneous work whose service, resource, financial and human results can disagree. A serious alternative is a bounded integrated operating arrangement. DEMO distinguishes models from modeled subjects and permits a selected Scope of Interest: see the primary 2024 chapter summaries for EE Model Theory and DEMO Methodology. Its historical production/coordination and commitment distinctions are useful inputs.
The competent comparator in section 5.1 is a constructed arrangement using those distinctions together with a supplied resource schedule and domain policies. It retains separate work and parties, protects the possible repeat and reaches the same six-hour allocation. OPS adopts its results. The residual question is whether the qualified financial horizon, receiving agreement and specialist recovery condition are actually connected to the proposed extension. Sections 4.2–4.8 add only a missing consequence or authority relation and return an actionable bounded reconfiguration. If the incumbent already carries all of them, use it as the operating account.
The integrated material, information and financial model of Perez et al. (2023) is another serious source line for coupled decisions. The worked case uses the supplied resource schedule and domain policies. A more detailed model can be worth its data and maintenance cost when resource interactions repeatedly change the schedule; it is not necessary for the simple arithmetic in this case. C.32.MWA supplies general structure selection and synthesis, while the operation retains its actual allocation, service obligations and authority.
The full incremental burden of the OPS synthesis is recovering missing owner results, aligning their subjects and horizons, checking that one benefit has not displaced another protected use, and maintaining the resulting correspondence. It can lose to a mature integrated practice that already does this. TameFlow’s distinct operational, financial, informational and human concerns and the historical constraint-accounting sources help expose moved burdens. Reopen when a newly established relation affects the choice or the conditions that justify it, a source assumption ceases to fit, or a simpler incumbent preserves the same commitments, protections and truthful unresolved remainder at lower total effort.
OPS.19:12 - Relations
- Receives from:
OPS.1andOPS.3for the operating System, commitments, subjects, cases, resources, records, and relation candidates; reidentify any subject or boundary whose current facts no longer support the earlier result. - Receives from:
OPS.11,OPS.12,OPS.15, andOPS.17for interacting-structure evidence, human-condition consequences, a decision-specific account, and applicable status-preserved Method or repertoire claims. An absent or stale result stays an exact gap. - Coordinates with:
OPS.8–OPS.10,OPS.13,OPS.14, andOPS.18when queue, constraint, capacity, commitment, operating-financial, quality, or reliability results affect the choice or its grounds; each pattern retains its own subject and result. - Uses: current
C.32.MWAfor general several-structure architecture evidence,C.11for a bounded choice when its conditions obtain, and the current FPF Work, structure, evidence, measurement, temporal, causal-use, and representation owners for the exact claims relied on here. None supplies the Operations reconfiguration or its domain authority. - Provides to:
OPS.16when the trial’s feasibility or protected conditions depend on the cross-scale result. The receiving trial independently establishes its subject status, evidence, alternatives, authority, and available return. - Provides to:
OPS.20only as a candidate practice variation or operating consequence. The cultural Method independently supports its bounded population, predicate and continuation decision; an intervention, needed authority or claimed later observation has its own basis. - Does not replace: clinical, safety, legal, financial, employment, software-assurance, release, product, organization, capability, or cultural decisions owned by their direct practices.
OPS.19:End
OPS.20 - Deliberately Continue and Change Operations Culture
Status: Stable
OPS.20:0 - Use This When
Use this Method when you need to establish whether an operating practice persisted or changed across a particular practitioner population, or decide how to support its continuation or change. Typical signs are that a method’s author or coach will leave, two shifts use the same carrier differently, an operating rule is visible but not followed independently, or a local improvement must survive handover without becoming a compulsory rollout.
The first useful result is an account of what continued, changed or remains unknown within the stated population and period. Identify the Operations Management Discipline or smaller practice, operating setting, relevant interval and the admitted Method or candidate or observed practice at issue. Give the cultural claim, its participants, applicability, test and evidence. Use an existing predicate when it fits. If a decision is requested, give the supported continuation, revision, branch, replacement, stop or remaining uncertainty. Pursue a new observation or intervention when its attainable contribution warrants the burden.
Use OPS.16 for a local Method-change decision, including trial Work when that decision needs it. Use OPS.17 to compare or refresh a repertoire of operating Methods. Use OPS.19 when simultaneous Work across cases or scales must first be reconciled. A publication, training event, tool rollout, local project decision, or one successful service episode stays with its direct owner unless a bounded population relation is also current.
Here Operations culture is ordinary practice wording for how the named population generates, transmits, recognizes, selects, remembers, retains, changes, or loses Operations practice. Identify the participants in the relation being claimed.
Recognition concerns continuation across practitioners. Assurance supports the selected population claim, with its status, participants and interval. A new intervention additionally needs feasible authorized work; a later-result claim needs later observations. Sufficient current grounds can finish the account without another experiment.
OPS.20:1 - Problem frame
Operations depend on practices that cross shifts, sites, providers, and generations of practitioners. Readiness checks, incident stops, acceptance rules, recovery routines, and case-specific judgment can disappear when one experienced person leaves, or persist only as a card that no longer guides actual Work.
Visible activity can overstate continuity. Handover attendance establishes participation in that event; receiving enactment requires evidence of the receiver’s operating Work under the conditions intended for that use. Keep support that belongs to the practice. Independence from a coach, retention after a specified interval or support change, and a causal service effect are stronger claims with their own evidence needs. A carrier or usage count may help locate those observations.
Which relation concerning the practice does the evidence support in this population and period? What might explain the observed successes or failures? If a decision is requested, determine what continuation or change is justified. A further observation or intervention earns its place through its attainable contribution to the required claim or decision.
OPS.20:2 - Problem
A team wants useful operating practice to continue and harmful or stale practice to change. It often responds with training, publication, a required field or a tool rollout because those actions are visible and easy to count. To determine what changed, identify the relation actually claimed, its participants and applicability, and apply its test to the available evidence.
Collapsing the practice, its description and the population claim also hides what remains unknown. A local successful use may be established while selection by another shift or retention after support ends is unresolved. Obtain a further observation when its attainable contribution to the receiving use warrants the effort.
Intervention adds a further boundary. An Operations lead may be permitted to change one handover or local carrier without authority over another shift, professional practice, employment condition, safety decision, or wider field. The proposed intervention, performed Work, changed subject, later cultural observation, and later operating consequence must therefore remain separately inspectable.
OPS.20:3 - Forces
| Force | Practical tension |
|---|---|
| continuity and change | Stable practice supports reliable handover, while stale practice can preserve yesterday’s assumptions. |
| carrier and enactment | Cards, descriptions, repositories, rules and training make practice recoverable, while enactment under the intended conditions still needs evidence of use. |
| local use and population claim | One practitioner can use a Method correctly, while the relation claimed for a population needs its own participants and evidence. |
| speed and retention | Receiving enactment can be observed soon, while retention and loss need later intervals. |
| explanation and action | A visible failure invites immediate retraining, while access, recognition, authority, applicability, or Method fit may explain it better. |
| service and cultural evidence | Service, reliability, flow, toil, adoption, and human-condition consequences matter, while they are not the cultural predicate. |
| authority and participation | A local Agent can alter an assigned carrier or handover, while wider professional or organizational change may remain outside its authority. |
| common language and status | School and community names help practitioners orient, while labels do not establish Method identity, enactment, or population adoption. |
OPS.20:4 - Solution
Bound the practice, practitioner population and period. Preserve the status of the practice and establish what the evidence supports about the cultural relation. Distinguish the relation from its description, supporting observations and operating consequences. If a continuation or change is requested, compare the credible options and explanations that matter to it. Propose a course to the decision holder or decide under the authority granted for the task. Carry out the decision when implementation is part of the task, preserving the required service protections. A new observation or intervention must justify its design, effort, delay and displaced work through the contribution it can make to the question.
OPS.20:4.1 - Bound the practice, population, and status branch
Name the current Operations Management Discipline result when it is available. Otherwise name the smaller practice and population under C.36 and keep the Discipline claim unresolved. State the operating System or service, place, period, qualification window, and the people or other actual participants meant by transmitting, receiving, recognizing, selecting, remembering, retaining, generating, or losing.
Then preserve the input status:
| Starting branch | Required input | Claim still missing |
|---|---|---|
| admitted Method | Exact admitted local U.Method variant, exact relied-on version or separately classified U.MethodDescription, and bounded evidence for the operating use | The practitioner population and cultural predicate remain independently supported claims. Any intervention, needed authority, or claimed later observation has its own basis. |
| candidate or observed practice | Exact candidate account or source-described practice variation, its status, actual claim-bearing materials, and independently supported Work facts | The account can support an observation about receiving use. Admission as a Method, classification of a MethodDescription and enactment of that Method each require their own grounds. |
An OPS.16 return may supply either row exactly. An OPS.17 repertoire may supply current alternatives and lineage claims. An OPS.19 result may supply a candidate variation or consequence when its cross-scale decision matters. None supplies the cultural claim by adjacency.
OPS.20:4.2 - Select one value and one testable cultural predicate
Choose the relation needed to answer the question about the population or support the requested decision. Recover its value, participants and applicability, then apply the existing predicate’s test. If no suitable predicate expresses the needed relation, develop its meaning and a discriminating positive and failed case before relying on it. The examples below illustrate these distinctions.
| Predicate family | Operations question | Example positive and discriminating negative |
|---|---|---|
| generation | Did the named practitioners originate a distinguishable operating variation during the stated interval? | A source-traceable variation and its generating Work are recoverable; the negative is a relabelled carrier with no changed practice claim. |
| receiving enactment or another transmission relation | Does the receiver perform eligible Work using the admitted Method or the observed practice within its stated scope under the intended conditions of support? | An eligible case is handled under the rule and stop with the permitted help; the negative is a completed handover followed by an unsupported start. Test without the source practitioner or coach only when the later use requires that independence. |
| recognition | Does the named population identify the practice or result as the one meant by the local term in applicable cases? | Practitioners distinguish the practice from its serious rival; the negative is agreement on the label with incompatible case judgments. |
| selection | Does a named selecting participant or population choose the value under an explicit applicability rule? | Actual eligible decisions designate and use the selected value; the negative is a mandatory field with no corresponding Work. |
| memory | Can the population or its identified memory arrangement recover the value and its applicability at the named interval? | Practitioners recover the current rule and stop from identified carriers; the negative is an archive entry that directs a stale or unsupported action. |
| retention | Does the same predicate remain supported after the stated interval under the conditions being claimed? | Positive cases recur under those conditions; a failed case no longer meets the predicate. A claim of retention after support ends specifically needs observations after that change. |
| loss | Has a previously supported relation ceased for the named participants and interval? | Eligible cases now fail the earlier predicate under otherwise applicable conditions; the negative is only a missing carrier record with no observation of practice. |
Use an existing adoption or incident account when it identifies the eligible cases, observations of receiving use and interval relevant to the question. Where assistance matters, distinguish support available from the assistance actually used. Add a distinction when it could affect the cultural claim, its limits or a decision to continue, extend or withdraw support. Include the added observation and maintenance burden.
Use the lightest truthful claim. Apply A.6.RCD only when a reusable or local compound predicate is needed; open A.6.REL occurrence identity only when a later use must distinguish relation occurrences. State a missing cultural result where it limits the requested claim or decision.
OPS.20:4.3 - Separate the practice, carriers, Work, claims, and consequences
Recover what each observation establishes for the selected predicate:
| Subject or evidence | Required meaning for this use |
|---|---|
| admitted Method or candidate account | The exact admitted reusable way, or a source-traceable account of the provisionally distinguished way with non-admission explicit. |
| description episteme and carrier | What the separate description says, and which carrier makes it available to which participant and when. Method, description and carrier retain their different identities. |
| publication or training Work | What was actually delivered or performed and who participated. |
| operating Work | What the receiving practitioners actually did, with admitted enacted Methods where supported and the relevant performance evidence. |
| local decision or rule | What an authorized chooser selected, for which use and participants. |
| cultural claim episteme | The separately stated proposition about the value, population, relation and interval. |
| operating consequence | The service, reliability, burden or other outcome for its own subject and interval. |
For the primary predicate, identify the relation claimed in practice, the episteme that states the claim and the evidence relied on. Preserve unknown where a required observation is absent. Publication, training and local rule selection can support their own rows without establishing receiving enactment or later retention. A later observation does not create an earlier occurrence or prove that the intervention caused the change.
OPS.20:4.4 - Identify the participants and arrangements on which the claim or decision depends
Name the carriers, Systems, Work occurrences, decision rules, forums, assignments, permissions, authority relations, support arrangements, and selected structures needed to establish the claim, compare live explanations or carry out a selected intervention. State which participant can act through each and which condition it changes.
Do not bundle a card, board, handover, coach, rule, repository, and practice into one cultural mechanism. A carrier can improve access, a forum can supply recognition Work, an assignment can locate responsibility, and an authority predicate can permit a change; their effects and evidence differ.
Use A.22 only when the organization of identified constituents and their relations matters to the claim or decision. Use C.30 only for a current architecture question. A compact plain account is enough when the intervention depends on one carrier or one Work occurrence.
OPS.20:4.5 - Compare explanations that matter to the claim or decision
Retain credible non-equivalent explanations whose different consequences could change the continuation or warranted claim. Do not invent another explanation to fill a fixed count. Common rivals include:
- the carrier and visible rule are sufficient under the intended support conditions;
- case replay, coaching, local authority, or a forum is needed for unfamiliar cases;
- practitioners cannot recognize applicability even though they can recover the content;
- required support or permission is absent;
- the Method no longer fits the changed operating condition.
For a needed comparison, state the consequences that differ and what an attainable observation could settle. Use sufficient current observations when they answer the receiving question. Select a new contrast only if its contribution warrants its whole cost, delay, practitioner burden and displaced service, including the effort of designing it; use C.11.DUA when that demand needs appraisal. Use B.5 and B.5.2 for a needed durable hypothesis account, C.27 for temporal adequacy, A.3.3 for a state-space and transition-law claim, and C.28 for causal reliance.
If the observations cannot distinguish the explanations, retain unknown for that explanatory question. An independently supported current continuation or local response can finish while the explanation remains unresolved. If a contrast is unavailable, state which claim remains open and what the other evidence still supports.
OPS.20:4.6 - Compare alternatives and bound the intended action
When the current arrangement leaves a receiving operation unavailable, use C.36.MC:4.5–4.6 to obtain the missing contribution. Start with the result the recipient needs, available inputs and intended support. Trace the operations and their conditions to the needed result using available explanations and observations. If a reason or operation remains missing, establish it through further observation or obtain it from a qualified source or practitioner. Compare the receiving condition with the demonstrated one, preserve the dependencies that still apply and change the affected operation, allocation or support. Follow that alternative back to its required inputs, participants and resources and forward to the receiving result.
If the recipient needs a capability change, use the development or technical method appropriate to that holder. Identify what the recipient needs for this operation. An existing source, procedure, retained state or tool can supply a missing input. Performance feedback may improve the operation of a service or support a person learning it. For human learning, provide the explanation, practice, feedback and variation the learner needs. Establish the time and support needed for the selected change. A familiar operation may need only a reminder. Keep a precise gap or restrict the offered use when the needed provider is unavailable.
When choosing a continuation or change, compare the alternatives that remain serious for the named population:
- retain the current carrier and selection arrangement;
- change one carrier, handover, forum, rule, or selection arrangement;
- branch the arrangement for a population, setting, case, or condition;
- replace the current means;
- stop or revert the intervention;
- preserve a relevant
unknown, selecting a discriminating observation only when it is useful and obtainable.
For the intended continuation or change where authorization is required, name the decision-making Agent and its assignment, permission, or authority predicate, participants, scope, positive basis, and protected conditions. A factual account creates no intervention to authorize. A selected change also states reversible exposure and its intended operating consequence. Expertise, sponsorship, attendance, tool ownership, assignment, permission, and authority are not interchangeable.
Keep service stops, safety, recovery, privacy, consent, security, release authority, employment conditions, and professional judgments with their current owners. A missing authority or protection returns an exact stop or narrower branch; it does not justify a broader rollout.
OPS.20:4.7 - Keep a selected change and its observed results distinct
When the task includes performing a selected change, use the direct Method under its actual authority and protections. Keep the following claims separate, using only those made by the result. A recommendation can finish as a warranted proposal; a claimed performed test or later cultural result cannot finish without its actual Work and observations.
| Claim | Basis when claimed |
|---|---|
| proposed intervention | Intended changed subject or relation, supported contribution, scope, needed authority, protection and stop; a later observation only for the selected inquiry or claim that needs it |
| intervention Work | Actual performers, enacted admitted Methods, history, interval, containing System, used Systems, any supported departures, and direct result |
| actual changed subject | The card, rule, handover, assignment, forum, carrier, or other subject that actually changed |
| later cultural observation | The same testable predicate applied to named participants at the named later interval |
| later operating consequence | Service, reliability, flow, toil, adoption, human condition, burden, non-use, rejection, or another direct result for its own subject |
An intervention can be performed without changing the intended subject. A changed subject can be followed by no change in the cultural predicate. A positive cultural observation can coexist with a poor operating consequence. Use the evidence and qualified judgment needed for each claim separately.
OPS.20:4.8 - Return the cultural account and any requested decision
State what the evidence supports about the selected practice and relation for the named participants, setting, period and qualification window. Identify its status and limits. If a decision is requested, return continue, revise, branch, replace, stop, a retained set or unknown, with the grounds, authority and protections needed for that outcome.
Include the following where they bear on the result:
- the available positive, negative, inapplicable, unknown, or missing-information observations, including later observations when a later claim is made;
- any serious alternatives and explanations still live;
- separate service, reliability, flow, toil, adoption, or human-condition consequences;
- population, authority, time, transfer, and causal limits;
- what change would warrant revisiting the conclusion and, for a selected inquiry, the next attainable observation.
Return a contradicted admitted-Method or lineage claim to its specific maintained result under OPS.16 or A.3.1.MV. When the receiving use warrants keeping a new reusable difference, send its changed operation or relation, origin, intended use and evidence limits to A.3.1.MV as a status-preserved candidate; the parent need not be false. Return repertoire implications to OPS.17. Return candidate or source material to its candidate account or source claim. Population spread alone changes none of those objects.
OPS.20:4.9 - Keep the first account small
A compact account states the bounded practice and population, subject status, selected cultural claim, applicable test, evidence and conclusion, including a continuation decision if requested. Keep the uncertainty, limits, operating consequences and grounds needed by its recipient. Develop new predicate cases, explanations, intervention details or later observations only when the current claim or selected work needs them.
An Operations lead can document how a practice continued, retain a supported bounded practice, repair a particular gap, or stop an unsupported branch without counting publication, attendance, fields or tool use as adoption. A selected worthwhile test still distinguishes its actual Work and results from unknown transmission, selection, retention or causality.
OPS.20:5 - Archetypal Grounding
OPS.20:5.1 - PumpWorks tests receiving enactment across two shifts
This constructed case continues the PumpWorks control-service operation. The bounded practitioner population is the coordinators of the named PW-Early and PW-Late shifts during the next six weeks. The admitted input is PW-TestAdmission-v2 : U.Method under exact PW-TestAdmission-Description-e2 : U.MethodDescription and the bounded OPS.16 evidence. That evidence includes one correct admission, one truthful hold for missing permission, preserved service conditions during the trial, and a branch decision. It establishes no population relation.
The value under test is the admitted package-admission Method for eligible control-service packages. The primary predicate is receiving enactment: after the initial author is absent, a shift coordinator independently applies v2 to an eligible package, records a truthful hold when a required condition is absent, and preserves the service stop. The discriminating negative is a completed handover followed by an unsupported start. Apply the claim distinctions in section 4.3: handover participation and a successful package result cannot substitute for independent receiving use.
For this decision, the existing handover account identifies the admitted v2 and exact description, the card and board support, performed replay and package decisions. It distinguishes supported receiving-enactment claims from open questions for the two shifts and six-week window, with the available observations linked to the claims they support. Service results remain separately qualified.
Two explanations remain live:
H-PW-1: the readiness card plus board field is sufficient for independent receiving enactment; it predicts correct unfamiliar as well as familiar decisions after access and handover.H-PW-2: replay of an incident or provider-handover case plus current local authority is needed for unfamiliar cases; it predicts correct familiar decisions but a false start or escalation failure when the unfamiliar case has not been replayed.
The control-service operations lead is the decision-making Agent for a bounded intervention. In this constructed case, current predicate PW-Handover-Change-Authority-1 permits the lead to add one case replay to the existing PW-Early handover for this six-week probe. It permits no change to field-release, safety, staffing, employment, or the PW-Late handover. Incident coverage, manual fallback, protected recovery, required permission, qualified support, and the stop on unsupported starts remain protected. The change is reversible by removing the added replay after the probe.
The selected intervention adds one familiar-case replay to PW-Early’s existing handover. The proposal, performed replay Work, revised handover content, and later package decisions are recorded separately. During the later interval, two coordinators independently apply v2 correctly in familiar eligible cases. A third coordinator starts a provider-unavailability case without the required support, satisfying the discriminating negative. The unsupported start is a failed receiving-enactment observation, not an authorized relaxation of the stop.
These observations do not isolate the card, board field, replay, authority reminder, practitioner background, or case familiarity as the cause. They also do not establish six-week retention: the observation window is still open. Service results from the three packages remain separate, and no favorable package outcome repairs the failed predicate.
Return revise for the unsupported provider-unavailability branch and retain the observed familiar-use contribution of the card-plus-replay arrangement for the named PW-Early coordinators. Keep the failed case, PW-Late, and longer retention distinct. Suppose another comparison would displace needed service without improving the grounds for continued use in the familiar cases. That bounded continue needs no new replay or causal explanation. The failed unsupported start remains failed and supplies no permission to repeat it.
Now suppose the next receiving use requires the provider-unavailability decision to be made independently. The current evidence does not support that extension. Select a provider-unavailability decision replay only if a qualified facilitator, participants, protected interval, and current permission for that additional replay are available and its attainable result justifies the effort of deciding whether the extension is supported. Permission for the trial does not authorize the extension. No unsupported operational start is part of that probe. The proposal completes the decision to test; a claimed tested extension still needs its actual result and independent later use. If the trial is unavailable or not worthwhile, withhold that extension while preserving the supported familiar branch. Reopen the affected result when the Method, description, population, authority, protection or receiving condition changes.
A capable adaptive SRE approach would also investigate the unsupported provider start, listen to the receiving coordinators and retain the useful familiar branch rather than mandate wider rollout. OPS adds the explicit receiving-enactment predicate only if the existing adoption account cannot distinguish the two supported familiar decisions from the failed unfamiliar decision, the unobserved Late shift and unobserved retention. If it already can, it suffices. Maintaining that distinction costs eligible-case observation, follow-up and communication; a further provider replay adds design, facilitation and displaced-service cost.
OPS.20:5.2 - A hospital keeps the cultural claim on the candidate branch
A public-hospital emergency-flow team carries proposed information-checking way ED-Handover-Readiness-CA1 from OPS.16:5.2 through its A.3.1.MR candidate account. Its operations compare available information with qualified handover requirements and return missing information or changed clinical conditions to their responsible owners. Method admission remains unestablished. The bounded population is the licensed transfer coordinators for one named emergency unit and shift over four weeks; the receiving-use conclusion applies to those coordinators and that interval.
The value being examined is the practice described by the candidate account, and the primary predicate is its receiving use under the stated support conditions, without a Method-culture claim. A positive case is an eligible transfer in which a coordinator performs the described information comparison and preserves the required return when information is missing or a clinical condition has changed. A negative case is a completed mandatory field followed by transfer Work with no recoverable check. The candidate account, checklist, field, training Work, actual clinical Work, patient case and population claim remain separate.
The support question is whether the checklist and field make those operations recoverable under the intended receiving conditions, or whether the coordinators also need qualified case discussion to recognize when the information check must return to clinical judgement. Retain a bounded receiving-use account when existing eligible-case evidence supports it. Select a comparison of ordinary handover and qualified case replay when its attainable contribution to the claim or decision justifies the licensed participation, support and time it needs. Any intervention stops until current clinical and administrative authority permits it and preserves consent, privacy, safety, staffing, worker health and medical priority.
The return can be a qualified continuation, a revision of the candidate account, or unknown for the unsupported population relation. It establishes neither Method admission nor clinical effectiveness. Return observations to the account and to a separate A.3.1 identity question only when that question is needed; clinical decisions and protections remain with their qualified owners.
OPS.20:5.3 - An AI-assisted software operation separates tool use from selection
A software operations group has admitted AI-ReleasePrep-v3 : U.Method and exact AI-ReleasePrep-Description-e4 : U.MethodDescription for one low-risk release-preparation family. A prompt repository, model endpoint, tool rollout, and usage counter are carriers, Systems, or records. They do not show that the on-call population selects or enacts v3.
The group bounds two named on-call rotations and one release interval. It tests one selection predicate: for an eligible low-risk change under the qualified provider and model condition, the responsible human practitioner selects v3 only when its human review, evidence capture, security check, fallback, and release-authority conditions are current. The negative is a logged tool invocation followed by release preparation that omits one required condition.
Credible rivals are that description plus repository access is sufficient, or that a case replay and explicit recognition of the provider/model qualification boundary are needed. Existing eligible-case observations can support a bounded current selection account under the unchanged qualified provider condition. Select a reversible provider-change replay for one rotation when its attainable result can materially improve the decision or its grounds at a cost justified by the use, with the participants, facilitator and protected time available, under current release and training authority. Actual handover, release-preparation, review, security and release Work remain separate, as do model calls, generated text, traces, test results, decisions and service consequences.
If the provider or model changes to an unqualified edition, the current branch stops and the named fallback applies. The result can retain one population-specific selection claim while returning the changed-provider branch as unknown or stop. Security, software assurance, model capability, release, employment, and governance consequences remain with their owners; usage count and one successful release establish none of them.
OPS.20:6 - Bias-Annotation
| Recurring bias | Likely drift | Working repair |
|---|---|---|
| rollout bias | Publication, training completion, access or a configured tool becomes population adoption. | Apply the needed population predicate to actual receiving use; develop a new predicate only when the existing one cannot express the claim. |
| label and school bias | A familiar community name, such as SRE or Kanban, substitutes for the practice being continued. | Recover the actual Method or candidate and the population claim needed here. |
| carrier bias | A maintained carrier is taken as evidence that the practice continues. | Recover receiving Work and the population predicate separately from access. |
| mandate bias | A required field or policy is read as selection and enactment by every practitioner. | Test actual eligible decisions and retain unsupported, copied, or bypassed cases. |
| organization-as-agent bias | “The organization adopted” hides selecting, receiving, and authorizing participants. | Bound the population and name the capable participant for each predicate and action. |
| success-story bias | A favorable service result proves transmission, retention, and causality. | Observe the cultural predicate and operating consequence separately; use C.28 only for causal reliance. |
| intervention bias | Performing training or changing a carrier is reported as successful cultural change. | Separate proposal, Work, changed subject, later predicate, and later consequence. |
| maturity bias | Several missing relations are averaged into an adoption stage. | Return supported predicates and explicit gaps, including unknown. |
OPS.20:7 - Conformance Checklist
- The Operations Management Discipline result or smaller practice boundary, operating System or service, setting, place, period, and qualification window are explicit.
- The practitioner population identifies the participants meant by transmitting, receiving, recognizing, selecting, remembering, retaining, generating, or losing.
- The input is either an exact admitted Method plus relied-on description and bounded evidence, or an exact status-preserved candidate or observed-practice account with no Method, MethodDescription, or enactment inflation.
- The selected value and cultural predicate have recoverable participants, applicability and a test. A new predicate has the positive and failed cases needed to distinguish its meaning.
- A missing cultural result is explicit when it limits the requested conclusion or decision. Support and independence conditions match the claim actually made.
- The account distinguishes the relation claimed in practice, the episteme stating it and the observations at the named intervals on which it relies.
- Each observation is used for the subject and claim it supports in section 4.3.
- A selected structure or architecture is opened when the claim or decision depends on how its constituents are organized.
- The account retains the credible explanations and uncertainty that affect the claim or decision. A new inquiry has an attainable contribution worth its whole burden, including design effort, and feasible participants, capability, access, resources, window and authorization.
- The intended action’s needed Agent, assignment, permission or authority predicate, participants, scope, positive basis and protected conditions are named. A selected intervention also bounds reversible exposure; a current account creates no new change to authorize.
- Where the account concerns an intervention, it distinguishes what was proposed, what Work occurred, what changed and what later evidence shows about the practice and its operating consequences.
- Operating consequences retain their own subjects; cultural and causal conclusions have the separate evidence they require.
-
The return states the supported cultural conclusion, its limits and any material gap or condition for reconsideration. For a decision it also states
continue,revise,branch,replace,stop, a retained set orunknown, with its grounds and material alternatives. A next observation appears only for a selected worthwhile inquiry; stronger later claims keep their own actual evidence.
OPS.20:8 - Common Anti-Patterns and How to Avoid Them
| Misuse | Working repair |
|---|---|
| “Everyone attended, so the Method was transmitted.” | Observe eligible receiving Work under its intended support conditions; require independence only for a use that needs it. |
| “The field is mandatory, so the population selected the practice.” | Test whether actual eligible decisions designate and use the value rather than merely complete the field. |
| “The repository has stable editions, so the culture retained the Method.” | Apply the retention predicate to the named practitioners, interval and support conditions; repository persistence and retained practice have different evidence. |
| “The service improved, so the intervention changed culture.” | Keep service evidence, cultural observation, and any causal claim separate. |
| “The school is popular, so its Method fits this operation.” | Use the school as a dated source or alternative and compare the exact operating move and conditions. |
| “The operations lead owns the process and may change every shift.” | Recover the actual assignment, permission, or authority predicate and its scope. |
| “One failed unfamiliar case means the practice should be replaced.” | Compare carrier, recognition, support, authority, and Method-fit explanations before choosing revise, branch, replace, or stop. |
| “No long study exists, so no local cultural claim can be made.” | Make the smallest bounded claim supported by current observations and state the limits on prevalence, causality and retention that remain on those grounds. |
OPS.20:9 - Consequences
Operations practitioners can deliberately continue or change practice without treating every rollout signal as culture. A testable predicate, bounded population and current evidence can establish what continued and support any decision now required; a new discriminating observation is selected when it can improve that use enough to warrant its feasible work.
The method also preserves useful local knowledge. A card, replay, field, forum, or authority reminder can remain in the retained set for the use it supports even when another shift, unfamiliar case, long-term retention, or causal explanation remains unknown.
The work takes time to identify the practice and obtain evidence that covers the claim. Retention and loss can require longer intervals, and separate service or human consequences may need specialist Work. Neither a current account nor an unavailable future observation authorizes an unsupported population change.
OPS.20:10 - Rationale
Cultural continuation concerns identified values and participants. Relating the claim to its applicable test and actual cases helps determine whether the next action should change access, recognition, support, authority, applicability or the Method itself.
Credible explanations can affect what the evidence establishes and whether a change would help. Carrier sufficiency and replay-plus-authority dependence can call for different observations, but distinguishing them is not required for every bounded continuation. A small reversible probe is selected when its attainable contribution warrants its burden, without claiming control of the whole practice or unsupported causality.
Keeping the Method, description, carrier, Work, claim, evidence, and consequence separate also preserves the earlier Operations results. OPS.16 can remain a valid local Method decision while OPS.20 finds that receiving enactment failed in one population. A population observation can inform the repertoire without silently rewriting Method identity or service authority.
OPS.20:11 - SoTA-Echoing
The question is how to continue a useful operating practice among its receiving practitioners, and when to change its support or scope. Adaptive SRE practice provides a comparison in the PumpWorks case. Google’s organizational-change account, especially “Common Tooling Adoption in SRE” describes attention to differing receiving needs, changes in staffing and support when an arrangement failed, migration cost and voluntary uptake. It also permits specialized solutions where a common one does not fit. These are practitioner case observations, not universal causal estimates.
Apply that capable approach to PumpWorks. It can keep the familiar practice, investigate the unsupported provider start, improve receiving support and avoid extending an arrangement whose local value does not justify migration. OPS adopts those moves. Its residual contribution is a more exact decision claim when “adoption” leaves the matter ambiguous: which practitioners independently enact which admitted practice in which eligible cases and interval, and which failed observation defeats the proposed extension? Sections 4.2–4.3 and 5.1 distinguish receiving enactment from participation, institutional selection, carrier availability and longer retention. Two correct familiar decisions and one failed unfamiliar decision support the bounded familiar branch, not both shifts or six-week retention.
This distinction changes the return only when the incumbent adoption account lacks it. If that account already separates eligible use, failed cases, population and interval, reuse it without a parallel cultural register. The full extra burden otherwise includes recovering the exact practice, observing relevant later decisions, retaining failures, communicating use limits and maintaining them when practitioners or support change. A new replay also needs case design, facilitation, permission and protected service time. Continued observation can cost more than the decision it might improve; section 4.5 permits a supported current decision to finish and selects further inquiry only for a worthwhile attainable contribution.
Current C.36 supplies cultural-relation distinctions and C.36.MC supplies their Method Engineering use. OPS adapts them to operating authority, service protection and repertoire consequences. The SRE postmortem-culture account provides a complementary account of learning from failure and making follow-up work actionable; it supplies neither proof of a population relation nor the cause of PumpWorks’ failed case. The directly cited primary accounts are the source returns for these contributions; publication or institutional endorsement of any description is not evidence of its enactment.
Reopen when a new eligible failure, changed support, authority, population or interval changes the bounded return; when evidence warrants or defeats the proposed extension; or when a capable incumbent preserves these decisions at lower total burden.
OPS.20:12 - Relations
C.20 supplies a Discipline result when one is needed. C.36 governs generation, transmission, recognition, selection, memory, retention, loss and intervention distinctions. C.36.MC supplies the admitted-Method and candidate branches, predicate use, receiving explanation and adaptation, human and technical support, authorization and bounded return. Its :4.5–4.6 develops the missing receiving contribution when recognition of a gap is not yet enough. OPS.20 retains the Operations practitioner population, operating input, authority, service and reliability conditions, consequences and repertoire return.
OPS.16 can supply the admitted-Method or candidate/observed-practice input with its existing status and evidence. OPS.17 can supply repertoire alternatives and lineage claims; OPS.19 can supply a practice variation or operating consequence. Use OPS.20 to establish the receiving population claim and, when requested, decide what to continue or change. Obtain intervention authority and later observations for the work or claim that needs them.
OPS.12, OPS.13, OPS.14, OPS.15, and OPS.18 retain human-condition, service, financial, account, quality, and reliability questions when the cultural account or decision relies on those consequences. An actual OCE.11 result may supply obtaining simultaneous-Work conditions; a plan or possible-future arrangement does not.
A.3.1 and A.3.2 govern Method and MethodDescription status. A.13 and A.15.1 govern actual performers and Work. A.6.RCD and conditionally A.6.REL govern the bounded relation claim and occurrence identity. A.10, C.16, C.27, and C.28 retain evidence, measurement, time, and causal questions. B.5 and B.5.2 govern durable hypotheses and consequences. C.11.DUA appraises a questionable inquiry demand, including design and whole burden; C.11 governs an already formed bounded choice. A.22 and C.30 apply when the required cultural claim or decision depends on the organization of the selected constituents and relations.
OPS.20:End
Part X — Choose Operating Aims and Interpret Performance
OPS.21 - Choose Operating Aims, Targets and Comparisons
Type: Method Status: Stable
OPS.21:1 - Problem frame
Use this when an operating team needs to decide what improvement to pursue and how to recognize it, or when a supplied target encourages the wrong work. A repair service can meet its count by selecting easy jobs while urgent equipment remains unusable. A support team can inherit a corporate cost ratio without knowing which contribution it should change.
Start with the continuing operation, its recipients and the result worth improving. Translate that result into the team’s contribution, choose what to observe and a meaningful comparison, and decide whether a numerical target would help. An aim and an interpretable comparison can support a next action, a proposal to the holder of a decision, or continued observation of an adequate condition. If agreement is blocked, identify the unresolved choice.
The wider practice is managing operating performance. This pattern constructs the aims, targets and comparisons used in that work. OPS.22 interprets subsequent performance; OPS.13 establishes what can actually be promised. Use an existing aim and comparison when they already answer the question. If the worthwhile direction itself remains unsettled, obtain that contribution through Strategy (STR.5) or problem structuring (PSDA.6) before refining its indicators.
The intended reader understands the operation and can use the evidence, professional criteria and decisions on which the aim depends. Obtain any missing criterion, commitment or permission from its qualified source or holder.
OPS.21:2 - Problem
An easily measured quantity can become the purpose of the work. Targets can also be selected by copying last year’s number, dividing an organization-wide ratio or bargaining down an ambition until it is easy to exceed. These moves can produce precise numbers without an explanation of why reaching them would help the recipients.
An ambitious target creates a different difficulty. It can identify a worthwhile gap while exceeding the present forecast or resources. Treating it as a promise conceals that gap; restricting every ambition to today’s expected output can conceal useful improvement. The practitioner needs to construct the aim and its use together.
OPS.21:3 - Forces
| Force | Tension in the work |
|---|---|
| Direction and local knowledge | A shared purpose needs compatible contributions, while each team sees conditions that a corporate ratio omits. |
| Ambition and credible action | A demanding aim can expose an improvement opportunity; an unsupported demand can induce concealment or unsafe shortcuts. |
| Comparability and unlike work | A common measure can aid learning while differences in demand, equipment, obligations or starting conditions defeat a ranking. |
| Visibility and burden | More observations can reveal a neglected consequence, but collecting them consumes operating capacity. |
| Local recognition and joint results | A team can improve its score by moving work, delay or cost to another participant. |
| Stability and revision | A retained aim guides effort; changed needs can make it irrelevant even when its number remains attainable. |
OPS.21:4 - Solution
OPS.21:4.1 - Recover the useful change and the team’s contribution
Name the recipients, continuing work and time horizon. Ask what should become better for them, what is already adequate and what must remain protected. A recent case can distinguish the recipient’s result from internal activity: restored equipment from closed repair tickets, for example. OPS.1 supplies a missing operating boundary.
Translate the wider direction through the actual contribution. If the organization needs dependable repairs, reception may improve the completeness of requests, technicians may reduce avoidable returns, and a shared specialist may supply difficult diagnosis. These are related contributions, not smaller numerical copies of one corporate target. Establish how the proposed contribution helps neighboring work and what it requires there. Use existing evidence or observe the receiving work. Obtain any missing judgement or commitment from the contributor or authority able to supply it.
When a condition is adequate, it may be enough to monitor it. Set an improvement aim if a changed need, a deterioration or an attainable opportunity makes improvement worthwhile.
OPS.21:4.2 - Choose evidence that could distinguish improvement from a better score
Describe an observable good result and a plausible case in which the proposed indicator improves but that result does not. A higher completed-job count can coexist with unaccepted work, repeated failures or delayed complex jobs. Retain the observation that distinguishes these cases: acceptance, later return, case mix or waiting of the affected cohort. OPS.15 develops the observation account when its population or meaning is missing.
State what is counted, whose cases are included, when observation begins and ends, and how unfinished work remains visible. Choose the horizon from the recipient’s need and the time in which action could change the result. An annual reporting date can remain while an urgent operating response needs a shorter interval.
Select observations that can establish or revise the interpretation or guide action. An early indicator can prompt intervention; a later result can test whether the intended benefit obtained. Where a numerical proxy is inadequate, describe the result to be examined and the evidence and competent judgement needed to recognize it. Do not invent a score to replace an unavailable professional criterion.
OPS.21:4.3 - Choose the comparison before choosing the number
Use the comparison whose meaning fits the aim and available evidence.
| Comparison | When it helps | What must remain visible |
|---|---|---|
| An absolute result by a relevant date | A known population, recipient need or required service gives the number a useful meaning. | Eligibility, quality, timing and the work needed to reach the result. |
| A range or a qualified milestone | Precision would exceed the available knowledge, or progress is better demonstrated through a usable contribution. | What counts as adequate progress, what uncertainty remains and how each material outcome will be interpreted or used. |
| A ratio such as accepted work per usable hour | The relation between input and output answers the operating question. | Definitions of both quantities, omitted quality and shifted work; a ratio is not a comparison with peers. |
| Comparison with other operations | Their work, constraints and receiving results are sufficiently comparable for the intended inference. | Differences in mix, assets, starting conditions, shared support and observation coverage that could reverse that inference. |
| Improvement from a relevant earlier condition | Absolute peer levels would conceal important structural differences. | The original basis and changes in it. A low starting point can make improvement easier; percentages alone do not equalize opportunities. |
| Observation without a numerical improvement target | A condition is already adequate, the work is exploratory, or a quota would distort the useful contribution. | The condition or contribution to examine and the event that calls for a response. |
Test the comparison against differences that matter to the intended judgement. Evidence from an affected participant or a plausible unlike case can expose them. If easier conditions could explain the apparent lead in a league table, narrow the comparison or use it to frame a learning question. Use a more complex adjustment only when its basis and likely improvement in the judgement justify the effort.
OPS.21:4.4 - Construct an ambition and expose what attaining it would require
Compare available aims and develop others when needed. Start from the useful change: the recipient need that remains unmet, a demonstrated improvement opportunity or a relevant comparison. Contrast them with continuing current performance. For each serious candidate, explain why the difference is worth pursuing and which action might produce it. Include displacement, quality and continuing-service conditions.
Use that comparison to select the degree of ambition. Establish the conditions of contributions on which it depends, including any agreement still needed from those who will supply them. A target can exceed the current expectation when there is a worthwhile, intelligible gap to work on. There is no generally correct percentage of stretch. A high number without a plausible way to achieve it is a demand for further construction, not an executable operating instruction. Where the way is unknown, a bounded learning contribution can be the current aim.
When the aim needs a conditional forecast, use an adequate one or develop it through MA.5. Where resource, capacity or payment implications are unresolved, use the relevant contributions from MA.1, MA.2 and OPS.10. A target of twelve repairs, an expectation of eight and resources for ten can be jointly intelligible: the differences locate work and decisions. They do not authorize promising twelve.
OPS.21:4.5 - Reconcile contributions and decide how the aim will be used
Check the consequential joins with other participants. Two teams can each claim a feasible target while relying on the same specialist window. A reception target can accelerate incomplete requests and burden technicians. Use OPS.19 for a joint demand or displaced contribution; return an unresolved direction conflict to whoever has authority to decide.
Establish who can choose the aim, assign the work, provide the resources, change a service promise or decide assessment consequences, as the intended use requires. Finance can supply an expectation while staffing remains with another authority. HR can advise on assessment while the operating unit controls assignments. Use decisions already in force and obtain any missing decision from its holder.
Agree the intended interpretation while the grounds are available: the aim, comparison, difficulty, material assumptions, protected conditions, proposed action and reason to reconsider. Explain what an unwelcome forecast will trigger. It should expose a response decision, not silently become a lower target or an automatic adverse judgement of the reporter. If an existing consequence rule defeats that use, take the conflict and proposed change to the holder of authority to change the rule, using OCE.10 when the arrangement needs development. Retain the honest account and the unresolved authority condition until that change is effective.
Use the ordinary working record or discussion that can carry these distinctions. The result may be an agreed aim, a proposal conditional on another participant’s decision, or a justified choice to monitor without a new target.
OPS.21:4.6 - Revise the affected object when conditions change
Ask which premise changed and what used it. New demand evidence can confirm or change the forecast. A resource decision changes available provision when it is actually implemented. A changed recipient need or an invalid comparison can justify revising the aim. A service commitment changes through the parties’ applicable agreement under OPS.13. None of these changes automatically performs the others.
A difficult but still useful ambition can remain while the team changes its action or requests support. An aim whose purpose disappeared should be replaced even if it remains easy to hit. Keep the earlier aim and its basis available for OPS.22; a justified revision helps interpret performance but does not turn a previous miss into a hit. Revisit only the affected contribution and preserve adequate neighboring work.
OPS.21:5 - Archetypal Grounding
OPS.21:5.1 - Derive a repair aim before negotiating resources
This constructed cooperative has twelve identified customers whose equipment could usefully return to service this month. Five have booked; seven have received qualified offers, and the available nonoverlapping demand evidence supports three further acceptances. The expected demand is eight. All twelve needs are suitable for the cooperative’s standard repair; each customer retains the choice to accept or decline. Restoring useful equipment, with customer acceptance and no omitted quality work, is the receiving result.
The team considers eight, ten, twelve and fourteen accepted repairs. Eight is the current expectation and leaves four identified needs beyond the expected result. Ten would serve two more needs and fits the base provision calculated below. Twelve would meet the complete known opportunity if all customers accept and the work can be supported. Fourteen has neither identified demand nor a way to achieve additional useful work in this case. The team provisionally selects twelve as a conditional ambition, with prompt clarification of the seven offers as its first action. It retains eight as the forecast. If customers decline because repair no longer serves them, manufacturing a repair sale would defeat the purpose; reconsider the affected aim.
The base arrangement supplies 36 usable hours after protecting continuing service. Setup needs six hours and each standard repair three. Eight repairs need 30 hours, ten need 36, and twelve need 42. One obtainable extra block of eight hours would give 44. The ambition exposes a resource decision; it does not establish that the block is staffed or funded. The dated financial comparison shows that twelve repairs with this block would leave 20 less in closing cash than ten using the base provision. The cooperative decides that serving the two additional customers is worth that difference, provided the funding needed before customers pay is obtained and continuing service remains protected. This explicit judgement sustains the ambition; if the difference were not worthwhile, ten would be a reasoned alternative. The resource holder still has to authorize and provide the block before anyone promises the additional work. The connected repair example (Engineering.Reference:7) carries this result through provision, cash, changed work and assessment.
OPS.21:5.2 - Decline a misleading ranking
Two archive teams report requests completed per hour. One receives indexed digital material; the other also locates damaged, incompletely described records and assists the first team with difficult cases. Ranking their ratios as performance would conflate different work and hide the shared contribution.
They retain the quantities for understanding demand, compare like cases only where that comparison has a sound basis, and examine whether recipients obtained usable material within the relevant dates. The second team’s improvement from its own earlier condition remains interpretable only with changes in mix and assistance visible. They choose a concrete improvement in unresolved locating work, while monitoring an already adequate response condition without a higher quota.
OPS.21:6 - Bias-Annotation
People who set targets may prefer what their own reporting can observe. Participants may negotiate an easy baseline or omit burdens borne by neighbors. Look for those effects in the receiving work and seek the receiving parties’ evidence where needed. Participation can improve the construction without establishing equal influence or eliminating conflicts of interest.
Ambition is a judgement about worthwhile effort under uncertainty. It is not evidence that people will be motivated, that an expected improvement is attainable or that a more demanding number is always better.
OPS.21:7 - Conformance Checklist
- The intended improvement refers to a recipient’s result and the team’s actual contribution.
- An adequate condition can remain monitored without a new improvement target.
- The observation and comparison preserve relevant population, timing, quality and unequal conditions.
- The selected ambition has a reason and exposes the work, support or inquiry it needs.
- Forecast, target, resource decision and service commitment keep their own meanings and revision conditions.
- A conflict over shared resources or assessment consequences reaches the participant able to act.
- A changed condition can revise the affected aim without rewriting its earlier basis.
OPS.21:8 - Common Anti-Patterns and How to Avoid Them
| Failure | Practical repair |
|---|---|
| Divide the corporate ratio into team quotas | Translate the wider result through each team’s contribution and its dependencies. |
| Choose the indicator because its data are free | Test whether it distinguishes useful improvement from a better score. |
| Make every target equal the forecast | Retain the gap and decide whether action, support, inquiry or a different ambition is worthwhile. |
| Make every forecast equal the target | Preserve the supported expectation so that a response can be chosen in time. |
| Treat a peer table as a fair ranking | Establish comparability for that inference or use a narrower learning comparison. |
| Lower the target after observing a miss | Preserve the original result and explain any warranted revision and its effective use. |
OPS.21:9 - Consequences
The team can choose what improvement matters, explain why its comparison is useful and return an exposed gap to a real decision. A supplied good target remains usable without repeating the construction. The work can also end with a monitoring condition or a bounded learning aim.
The choice requires knowledge of the receiving work. Discuss open contributions with their holders and keep a simple comparison when extra detail would add little to its use. Better target construction alone cannot supply resources or repair a consequence rule that the responsible participants leave unchanged.
OPS.21:10 - Architectural Rationale
Direction, observation, ambition and response are connected because each can defeat the others: a useful purpose can be measured badly, a sound measure can receive an arbitrary target, and a meaningful target can be used as an unsupported promise. The construction keeps these joins visible while allowing an adequate supplied result to enter directly.
A fixed quota is simpler when a stable, meaningful requirement and its use are already settled. A peer comparison can reveal opportunities that an internal baseline misses. A non-numerical contribution can guide work whose useful result is poorly represented by a count. Choose among them by the receiving decision and evidence.
OPS.21:11 - SoTA-Echoing
Bjarte Bogsnes, Implementing Beyond Budgeting, second edition (2016), chapter 4, printed pp.142–159, develops translation from direction to local contributions, indicator selection, target difficulty, peer comparison and the possibility of working without numerical targets. Sections 4.1–4.5 use those questions to work out what the comparison supports, what several teams need from the same source and which action their evidence supports.
The shared source discussion qualifies this line with the later study of budgets and forecasts. Keep a budget or reporting rhythm when its function remains useful. Reopen the selected construction when ordinary use shows that the aim no longer guides a useful contribution, the comparison conceals changed conditions, or its actual consequences again suppress the information needed for action.
OPS.21:12 - Relations
STR.5 and STR.8 supply a worthwhile direction and related contributions when these are unresolved. OPS.15 supplies observation meaning; OPS.10 and OPS.19 supply capacity and joint-work comparisons. MA.5–MA.6 preserve the conditional outlook and distinguish its use from ambition and authorization. OPS.13 establishes service commitments. OPS.22 interprets later performance against the retained basis. If the response requires a different organizational arrangement, use OCE to develop a proposal. Putting the change into effect requires the applicable authority and provision.
OPS.21:End
OPS.22 - Interpret Operating Performance and Decide the Response
Type: Method Status: Stable
OPS.22:1 - Problem frame
Use this when you need to interpret an operating result, or choose a response on that basis, but a target-attainment ratio or dashboard color cannot explain the contribution. One team may narrowly miss a demanding aim while another exceeds an easy one. A favorable total can conceal deferred work, deteriorating quality or another team’s unpaid effort. An adverse forecast may be treated as evidence of poor performance before its conditions are examined.
Begin with the judgement required by the recipient. Recover the aim, relevant observations, operating conditions and participants’ actions. Return what can be concluded and what remains uncertain. If a response is requested, identify the action or proposal and the authority it requires. Two needs may remain unmet even when a timely correction was useful and attribution is still open.
This pattern governs interpretation of operating performance. It does not determine a person’s capability, corporate liability or a pay entitlement from an output total. HCD.11 supplies a capability-assessment contribution; CGOV.13 supplies corporate oversight when that is the actual decision. A sufficient established interpretation can be used directly. An ordinary service-acceptance decision with an applicable clear rule can finish through OPS.18.
The reader needs sufficient domain knowledge and access to the evidence that bears on the result. Use a qualified technical or financial judgement already available, or obtain the missing contribution from a competent source.
OPS.22:2 - Problem
An observed outcome depends on the work performed, its support, prior conditions and events that participants did not control. A target adds a judgement of ambition; its attainment ratio therefore combines result and target choice. Counting that ratio as performance can reward easy targets, favorable circumstances or transferred burdens.
Replacing a formula with an unexplained managerial impression creates another failure. Participants cannot correct mistakes or understand what contribution matters. The needed interpretation must expose its grounds and uncertainty, including evidence that weakens a favorable account as well as evidence that qualifies a miss.
OPS.22:3 - Forces
| Force | Tension in the work |
|---|---|
| Accountability and uncertainty | An answer is needed while causal attribution may remain incomplete. |
| Ambition and comparability | A demanding aim can motivate useful work, while attainment percentages favor an easier target. |
| Joint work and individual consequences | A result may require several contributors whose shares cannot be inferred from the output count. |
| Timely learning and consequential judgement | Prompt feedback helps correction; reward or formal accountability decisions may need different evidence and authority. |
| Context and favoritism | Circumstances change interpretation; selective excuses or hindsight can make judgement arbitrary. |
| Present results and continuing capability | A short-term gain can consume maintenance, recovery or customer trust needed for later work. |
OPS.22:4 - Solution
OPS.22:4.1 - Identify the question and recover the comparison
Ask what the assessment should establish and who will use it. A recipient may need to understand past work, choose the next operating action, change provision or an aim, give feedback or recognition, or decide a reward under an existing rule. Use separate evidence and authority for questions that require them.
Recover the original aim and comparison from OPS.21 or a sufficient existing basis: intended contribution, population, horizon, difficulty, assumptions and protected conditions. Retain authorized changes with their timing and reasons. If the basis was never settled, say so and reconstruct what can be established from the actual undertaking; do not invent a retrospective promise.
Keep an ambition, forecast, resource authorization and service commitment distinct. Ten deliveries can miss an original ambition of twelve and satisfy ten legitimately revised promises. Both facts matter. The revision does not delete the original ambition or prove that the response was good.
OPS.22:4.2 - Establish what was obtained and what remains
Compare observed results with that basis. Keep unfinished cases, excluded populations, quality, timing and relevant later returns visible. Check whether a changed denominator, early closing or transferred task created the apparent gain. OPS.15 develops a missing operating account; MA.7 explains a monetary difference without deciding personal merit.
Follow the result into its intended use. Were repairs accepted and useful, or merely marked complete? Did a faster handover require the receiving team to redo it? Include a delayed consequence when it can change the assessment. A known current result can support action before every future consequence is observed; state what later evidence could reopen the judgement.
Record the gap plainly. Context can change what the gap implies; it does not change the observed count or discharge an outstanding obligation.
OPS.22:4.3 - Examine conditions, choices and the contribution to the whole
Use the following questions to explain the difference that matters to the assessment. Pursue evidence far enough to support the finding or response the recipient needs.
- Did the result contribute to the intended aim? Compare the indicator with the recipient’s actual result and the conditions it omitted. A financial gain obtained by postponing required maintenance can weaken an initially favorable assessment.
- How demanding was the aim on its original grounds? Compare the opportunity, starting condition, work mix and proposed way to achieve it. A low attainment percentage against an ambitious target is not directly comparable with a high percentage against an easy one. Ambition alone also earns no credit for ineffective action.
- What changed, favorably or adversely? Recover when the change became knowable, who could respond and which premise it affected. A market windfall needs the same scrutiny as an external disruption. Separate changed circumstances from a claimed causal effect of the team’s intervention.
- What did the participants do with the information and means available then? Examine promised and necessary actions, requests for support, timely warning, available alternatives and actual follow-through. Use what was reasonably available at the time; knowledge obtained later does not prove that an earlier choice was unreasonable.
- What did the result require from other work, and can it continue? Include shared assistance, displacement, quality losses, deferred obligations and consumed protection. Helpful cooperation can reduce one team’s local count while improving the joint result; taking another team’s resource does not create additional capacity.
Compare the explanations that remain plausible on the available evidence and could affect the requested finding or response. More completions might follow from a simpler work mix, overtime, transferred work or a better method. Use evidence to distinguish them far enough for the required conclusion; an established condition or sufficient bound can settle a narrower response. A modeled counterfactual remains conditional. Preserve unresolved attribution instead of assigning every residual to effort or competence.
OPS.22:4.4 - Form a judgement that the affected participants can examine
State the observed result, how it compares with the aim, which contextual findings change interpretation and what remains uncertain. Separate findings when their evidence, implications or resulting actions differ. An unmet receiving need calls for a response even when the team acted competently; a favorable outcome does not excuse concealment of a material risk.
Compare teams only at the scope the evidence supports. If different work or shared contributions prevent a ranking, assess each against its meaningful aim and compare specific practices for learning. Do not repair an invalid ranking by inventing weights or a difficulty multiplier. Use an established qualified comparison when one is available.
Give affected participants a real opportunity to correct consequential facts and explain their choices. Resolve a material disagreement against the evidence and agreed purpose, not by counting agreeing voices. Where the assessor’s interest or a disputed ground can change a consequential decision, obtain an appropriately independent competent judgement through the existing arrangement. The result can remain qualified or contested; when a decision is needed, its holder determines what those grounds allow.
A single score may be required by an existing system. Explain the translation and preserve the separate findings that the score cannot carry. Do not let the score silently determine every later development, recognition and reward decision.
OPS.22:4.5 - Select the needed response and identify who can act
When the work includes choosing or proposing a response, use the findings to identify an adequate action for the stated need. Examples include correcting a report, completing deferred service, retaining a useful action, changing an assignment or provision, revising an irrelevant aim, improving a method, or obtaining a needed capability-development result. Select the method for that change rather than asking people to try harder regardless of the cause.
Where the consequence arrangement is itself producing distorted forecasts or easy targets, identify its operative rule and holder. MA.9 examines the account’s behavioral contribution; OCE.10 develops an authorized change in access, workload, incentives or consequences. An adviser can propose the change without being able to make it effective.
Keep the operating assessment separate from the applicable reward decision. Use its relevant findings under the actual rule and authority; where that rule prevents the intended response, return the required rule change or exception to its competent holder. Apply the governing terms to establish any payment entitlement or outstanding obligation. If the task concerns human learning, use HCD to select the practice or assess the capability in question. A claim of acquired capability requires evidence from the person’s own work. For a question about a service’s capability, select the method appropriate to its operation.
For an unwelcome forecast, preserve the supported expectation and its earlier basis. If a response is needed, propose it to its holder or act under sufficient authority. Judge the report by its evidence and the participants’ actions, including any demonstrated concealment. The amount of a numerical decrease alone does not establish the reporter’s performance.
OPS.22:4.6 - Observe the response and reopen the affected judgement
When this work includes carrying out a response, identify its action, responsible participant and the observation needed to judge it. Establish whether the promised assignment, protection or consequence change occurred; a claim that the receiving work improved needs its corresponding evidence. An assessment can finish with the supported findings and their limits. For a proposal, also identify the response and any missing authority or provision.
Keep sound earlier findings when new evidence changes only one part. Later returns can invalidate a quality conclusion; a recovered resource decision can alter attribution; a changed recipient need can reopen the next aim. Use the retained original basis to explain the change. End the assessment when it answers the receiving question at the confidence the available evidence warrants, or makes the remaining consequential uncertainty explicit. Continue normal operating attention without requiring an indefinite inquiry into every cause.
OPS.22:5 - Archetypal Grounding
OPS.22:5.1 - Ten repairs after the work becomes harder
In the constructed case continued from OPS.21, all twelve customers eventually accept. One staffed eight-hour block is authorized and made available, giving 44 hours including six hours of setup. Three repairs then require five hours each instead of three. Twelve repairs would need 48 hours; no additional block can arrive before the promised dates. The coordinator reports the changed work promptly and obtains agreement to defer two standard repairs. Ten remaining repairs need 6 + 7 × 3 + 3 × 5 = 42 hours. Later arrangements retain the two deferred cases, their work and financial obligations.
Suppose acceptance evidence confirms all ten repairs and no omitted quality work. The initial assessment is a miss against the twelve-repair ambition, with two identified needs still outstanding. The work became six hours more demanding for the original twelve. The timely warning and agreed response preserved a feasible service arrangement; the revised promises did not retrospectively achieve the original ambition. Whether another response was better depends on the alternatives actually available then.
A second team reports ten standard repairs against a target of eight. Its 125% and the first team’s roughly 83% do not establish a performance ranking. The first team’s ten repairs required 42 hours with setup; the second team’s ten would require 36 under the same setup assumption. These hours explain a relevant difference in demand, not a complete value or effort score. Recover the second team’s original opportunity, means, quality and any assistance before making a consequential comparison.
The manager decides to keep the factual miss and recognize the first team’s supported corrective action in the operating account. Completion of the deferred work remains an action. If a reward policy nevertheless mandates a different consequence, this judgement is an input to that separate authorized decision, not a power to replace it.
OPS.22:5.2 - A favorable count obtained by borrowing protected support
An archive team exceeds its completion target after using a shared specialist for six extra hours. The initial report calls this an efficiency gain. Examination shows unchanged time per comparable request; the extra output came from the specialist’s time, and another team’s two due requests were postponed without its agreement.
The assessment retains the actual completions but rejects the unsupported efficiency claim and includes the displaced service. The resource holder arranges recovery of the affected requests and corrects the rule under which that time was taken. If the same assistance had instead been authorized, displaced no protected commitment and improved the joint result, cooperation could be a positive contribution. The local count alone cannot choose between those conclusions.
OPS.22:6 - Bias-Annotation
Hindsight can make an uncertain past choice appear obvious. Favoritism can make the same circumstance an excuse for one team and evidence against another. Apply the questions to favorable and adverse results, retain the evidence available at the time, and expose consequential disagreements.
Participants with less authority may bear burdens absent from the official account. Obtain their relevant evidence. A discussion is not proof that they could safely disagree or that every causal share is now known.
OPS.22:7 - Conformance Checklist
- The assessment answers an identified question. Its evidence fits that question and any proposed decision has an identified authority or an explicit authority gap.
- Original aims, forecasts, commitments and later revisions remain distinguishable.
- Observed results include the consequential unfinished work, quality and receiving effects.
- Difficulty, changed conditions and available actions are examined in both favorable and adverse cases.
- Shared contributions and displaced work affect the judgement where they change the whole result.
- Affected participants can correct consequential facts; unsupported attribution and rankings remain qualified.
- The assessment, reward decision and capability inference retain their distinct grounds.
- The recipient receives the supported findings and any requested proposal. A claim that a response took place or improved the work is supported by evidence of the action or its effect.
OPS.22:8 - Common Anti-Patterns and How to Avoid Them
| Failure | Practical repair |
|---|---|
| Rank teams by actual divided by target | Recover difficulty and comparable work, then qualify or decline the ranking. |
| Treat context as an excuse for every miss | Preserve the miss, test the explanation and examine available action. |
| Credit every gain to the manager | Examine favorable circumstances, shared work and rival explanations. |
| Replace the formula with an unexplained impression | State the evidence, interpretation, uncertainty and consequence. |
| Treat a lower forecast as poor performance | Examine its grounds and the response; retain earlier forecasts for learning. |
| Let a good narrative erase outstanding work | Keep the receiving need and obligations in the next operating action. |
OPS.22:9 - Consequences
The manager can distinguish a useful response under difficult conditions from a favorable number produced by easier work or transferred burden. Report the supported contribution and any unmet need. The findings can confirm the existing interpretation or guide the next action when needed.
The method requires judgement and access to relevant evidence. It cannot eliminate uncertainty, conflict or deliberate distortion. Use inquiry proportional to the required judgement or decision; a modest correction need not wait for a complete causal explanation.
OPS.22:10 - Architectural Rationale
The interpretation connects the original purpose, observations, contextual explanation and response because each answers a different question. Keeping only the ratio loses difficulty and joint work; keeping only a contextual narrative loses the actual result. The response remains subject to the powers and conditions of the decision it serves.
Targets and subsequent assessments are independently usable contributions. A team can start here with an adequate target supplied elsewhere, while OPS.21 can finish after constructing a next aim. Shared conditions and selective returns connect them without requiring every operating decision to pass through an annual appraisal cycle.
OPS.22:11 - SoTA-Echoing
Bogsnes, Implementing Beyond Budgeting, second edition (2016), printed pp.182–190, develops interpretation of indicator results through objectives, target difficulty, changed assumptions, responsive action and sustainability, together with the tensions among development and reward uses. Sections 4.2–4.5 adapt that connected historical treatment. The source’s particular rating scale, delivery/behavior weighting and bonus arrangements are not requirements of this method.
Keep causal uncertainty visible after the event. Use evidence about the affected work to establish who contributed, and identify the authority needed for any response. The shared source discussion explains why changing budgeting labels alone cannot establish changed use. Reopen the method or its support when repeated use still rewards transferred burdens, hides missed needs or leaves a consequential judgement unexplainable to its recipients.
OPS.22:12 - Relations
OPS.21 constructs aims and comparisons. OPS.15 and MA.7 develop operating and monetary accounts. OPS.13 preserves service obligations; OPS.19 reconciles affected joint work. MA.9 investigates behavioral effects of accounts, while OCE.10 changes the organizational conditions of a response. HCD.11 concerns demonstrated human capability under its own criteria. CGOV.13 supplies a governing response when the question belongs to corporate oversight.
OPS.22:End
Cross-Pattern Application
OPS.Application:1 - APP-OPS-01 — PumpWorks continuing control-service operation
PumpWorks must continue weekly evidenced controller releases while field incidents, provider changes, test-rig access, safety questions, and service commitments coexist. In this constructed case, a test-rig decision affects both incident coverage and release work.
OPS.1 bounds PumpWorks-ControlServiceOps by the continuing release-evidence and incident-response work. The controller product, field installation, coordination software and the rest of the company enter where that work depends on them. Identify the demand, commitments, subjects and units, authority and evidence gaps, and the control problem caused by different operating rates.
OPS.2 selects a case view for FieldIncident-I73, a process view for recurring release validation, a project/programme view for the time-bounded provider-platform migration, a queueing view for rig demand, and conditional control views. It preserves correspondences to the same subjects and commitments.
OPS.3 distinguishes ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, test-rig requests, Work items, queue membership, resource access, records, events, state claims, and direct relations. Use the ticket, trace, commit, test result, service log or dashboard for the claim its subject and evidence support.
OPS.4 maintains a current account of incident impact, release evidence, missing test T9, safety-return gap, provider-access conflict, release authority, service consequence, next permissible Work, and refresh conditions. Participants may see different authorized views, while subject and claim correspondence remains recoverable.
OPS.5 considers ReleaseCandidate-R42, FieldIncident-I73, SafetyQuestion-S19, ProviderChange-P8, and competing test-rig requests separately. The dispatcher admits work only when its identity, evidence, permission, authority, access, commitments and start conditions permit it. For deferred or rejected demand, give the reason and any condition for reconsideration. Return SafetyQuestion-S19 to the competent safety authority.
OPS.6 continues the admitted FieldIncident-I73 case under its current incident Method. It refreshes incident, deployed-controller, telemetry, T9, rig-access, provider, safety, and release evidence; identifies who can decide the next action, who can perform it and the authority required for each. Report any change in the incident state on evidence of what was done, or identify the condition still blocking progress.
OPS.7 relates the incident age and weekly evidenced-release horizon to service consequence, dependencies, current evidence, reversibility, recovery burden, and the existing commitments. The holder of priority authority decides the incident’s priority. Any change in an existing commitment goes to its own authorized holder or parties.
The wider operating question now concerns readiness, usable rig time and their coupling to the release decision. Across five eight-hour rig-access windows, the constructed log records 20 hours of test execution, 4 of setup, 4 of unavailability and 12 with no eligible job. At the final snapshot, twelve matters appear on local boards; four ready test packages require eight rig-hours. Snapshot membership and interval history remain different observations.
OPS.8 separates the four eligible packages from incomplete matters and selects readiness for the next test as the booking/dispatch condition. Future test evidence is not an input to the test that produces it. In the branch where lab-test permission for T9 is current and S19 concerns field release, T9 may enter the ready queue while R42’s release remains held. If S19 also governs the lab test, the test needs that permission basis too. Upstream and blocked waiting remains visible.
OPS.9 keeps the accepted-release result separate from test attempts and asks whether late prerequisites, insufficient usable rig time in a deadline window, or another relation explains the loss. Use the eligibility, access, start, result, return and acceptance times under comparable conditions to test these explanations. If they do not distinguish the causes, report what remains open and identify any attainable observation that would help. Twelve cards do not establish a rig constraint, and twelve starvation hours do not rule out a later peak capacity deficit.
OPS.10 compares the next actual resource window. Suppose the operation has continuous rig access during hours 0–6 of an eight-hour horizon; hours 6–8 are reserved for another use. Four packages at two consecutive rig-hours each require eight usable hours, so all four cannot fit the six available hours. Under a supplied scenario in which one planned package needs an immediately available two-hour repeat and then passes, planning three packages plus that recovery reserve requires eight usable hours. If the resource owner supplies hours 6–8 through an access decision that accounts for the displaced use, and the choice is to complete every planned package in both scenarios, plan three with the repeat reserve and return the fourth to OPS.5; affected existing commitments return to OPS.7. This is scenario-qualified test capacity, not a probability or release guarantee.
OPS.11 connects the plan to provider access, configuration/evidence correspondence, release supervision and existing commitments. A result for another configuration does not close R42’s T9 gap. A changed P8 access decision reopens the capacity and dependent policy; an unresolved S19 or missing release decision keeps the affected release held. The coordination result identifies which operating change can proceed and which professional return is still needed.
The product-side control view has plant FieldPumpInstallation-P4, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 only where their direct relations obtain. The operating-supervision view has reports from PumpWorks-ControlServiceOps and release, hold, rollback, or mode constraints returned by ReleaseSupervisorTeam-S2 only where both sides obtain. Use evidence for each timing claim on which the decision relies: sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change. Neither view is the operating account or Operations Method.
The next connected choice is whether to promise test completion, buy more resource time or change how the operation works. OPS.17 compares readiness-based admission, constraint protection and an extra rig window. Existing readiness criteria can be used now. A new constraint buffer needs the discriminating evidence from OPS.9; a peak-capacity alternative remains relevant even though earlier rig time was lost for lack of eligible work.
OPS.12 follows the staffing consequences. The supplied arrangement requires the current rig operator to stop that duty after hour six so protected recovery and subsequent incident coverage remain possible. Extending the same person’s rig work is infeasible under those conditions. Qualified relief can make the extension a usable staffing proposal; if relief is unavailable, use the shorter feasible plan. Establish the qualified cover, handover, access and financial authority before relying on the extension.
OPS.13 distinguishes the desired objective, a forecast and the parties’ commitment. In the stated one-repeat case, two completions and the repeat use six rig-hours; three completions and the repeat use eight; four completions and the repeat use ten. The repeat is immediately available after its failed attempt and then passes, while every other planned package passes first time. The two-hour extension therefore supports three completions under that case only when the staffing and other prerequisites obtain. A probability claim needs its own forecasting basis. Changing an existing wider promise requires the agreement or authority applicable to it; a new test-service promise leaves R42’s field release dependent on applicable T9 evidence, S19 and release authority.
OPS.14 compares the same third package from the start of month 1 through the end of month 2. In this financial case, the repeat occurs among the two packages retained in both alternatives; their costs and receipts cancel in the difference. The third package passes first time in either alternative. The customer permits either completion date and pays 900 at the end of month 2 for test evidence accepted by day 20 of month 2.
| Financial alternative | Work, acceptance and cash | Result through month 2 |
|---|---|---|
| Complete the third package now. | Extend to eight hours in month 1; pay 300 for rig access, 400 for qualified relief and 100 for consumables before the extra work. The third package’s evidence is accepted in month 1; receive 900 at the end of month 2. | Net +100. The 800 advance payment exceeds the available 500 allowance by 300. |
| Defer the third package. | Use six hours for two packages and the repeat. Complete the third in a confirmed two-hour spare slot on day 10 of month 2 and obtain acceptance by day 20. Pay 100 for consumables and receive 900 in month 2. The supplied resource account confirms unchanged already-paid rig/staff arrangements and no displaced accepted job or other foregone contribution. | Net +800. The incremental cash of completing now is −700. |
Earlier service must justify that extra 700 under the receiving decision. If the deferred receipt moves to month 3, its net cash through month 2 becomes −100 and the short-horizon difference becomes +200. Extending the account through month 3 restores −700, with all other facts unchanged. Delayed or failed acceptance of the immediate package likewise moves or removes its 900 receipt while the spent 800 remains. Resource, funding and field-release authorities retain their separate decisions.
OPS.15 connects the rig, service, finance and release views through their actual subjects and events. A repeat adds rig work without creating another accepted package. Test completion, customer acceptance, an invoice, a receipt and field release have different time and evidence bases. For a separate historical due-request cohort, forty requests have reached their deadlines: twenty-seven timely, three late-completed and ten still open. The completed-only measure is 90%; timely service to that due cohort is 67.5%. The latter answers the cohort service question.
OPS.18 identifies the quality or reliability question and any response that the governing policy requires. Test acceptance uses its qualified criteria; statistical monitoring addresses recurring variation; an incident needs containment and restoration evidence. If the release-related service fails a requirement, the permitted response and restart conditions follow that service and authority. Neither a passing test nor a new reporting window supplies the remaining safety or release result.
OPS.19 reconciles incident coverage, package demand, rig and specialist time, E27’s recovery, funding and the proposed Method trial. In the selected arrangement, two two-hour packages and a two-hour repeat reserve fit the six rig-hours while coverage and recovery remain protected. Schedule the third package in its qualified later slot. Hold the fourth because the current priority, acceptance window and financial terms give no reason to select it. Keep the Method trial closed until the promised service, recovery, support and permission conditions for the trial are met.
In a later interval, OPS.16 takes admitted PW-TestAdmission-v2 : U.Method under exact PW-TestAdmission-Description-e2 : U.MethodDescription and coexistence conditions confirmed by the service and resource owners: incident coverage, fallback, qualified support, the stop on new starts and hand-back. The two-package actual trial returns one correct admission and one truthful hold for missing permission while service and recovery remain protected. OPS.16 returns branch: retain v2 for the named control-service package family and supplied conditions, keep admitted v1 for the unaffected family, and require a provider-unavailability observation before widening. Use the two trial outcomes to judge this branch. Transfer to other conditions, causal superiority, general reliability and later population use require evidence for those claims.
OPS.20 bounds the coordinators of PW-Early and PW-Late over six weeks and examines receiving enactment of admitted v2, including a truthful stop when a required condition is absent. The constructed authorized replay remains limited to PW-Early. Two coordinators later use v2 correctly in familiar eligible cases; a third starts a provider-unavailability case without required support. Retain the supported familiar-use contribution and return revise for the failed branch, keeping PW-Late and longer retention unknown. That bounded current continuation needs no new experiment. Select a provider-unavailability decision replay only when a changed receiving use warrants its feasible, protected and authorized work; no unsupported operational start is part of it. The unsupported start remains part of the six-week record. A claim about what caused it needs separate evidence.
Enter at the method that answers the operating question and use any current inputs already established. Coordinating simultaneous work, improving a local Method and investigating how a practice continues each require different evidence and may support different decisions.
OPS.Application:2 - APP-OPS-02 — Public-hospital emergency flow probe
| Operating question | Contribution | Conditions and limits |
|---|---|---|
| operating focus | One emergency-care operating function, service commitments, patient and clinical-case subjects, horizon, authority, and evidence gaps. | Bound the operating System by the emergency service it provides and the work on which that service depends. |
| views | Case view for changing patient state, process view for recurring clinical/support Methods, queueing view for waiting and scarce beds/resources, project view for a time-bounded service change. | Clinical priority, treatment, consent, privacy, medical safety, and statutory authority remain specialist results. |
| subjects | Patient, clinical case, intervention Work, triage queue membership, bed/resource relation, clinician System, observation, record, and state claim remain distinct. | A patient is not a ticket or queue unit for every use; record closure is not clinical resolution. |
| current account | Qualified patient/case claims, evidence, uncertainty, permissions, disagreements, next decisions, and refresh. | Establish treatment authority from the applicable grant or rule. Use evidence of the patient’s outcome, including relevant patient reports and any clinical interpretation the claim requires. |
| admission | OPS.5 returns a bounded operating admission disposition for exact patient and clinical-case subjects from current authorized clinical and operating inputs, or names the missing specialist condition. | Waiting age is not clinical priority; Operations supplies no treatment, consent, privacy, medical-safety, labor, or statutory authority. |
| case continuation | OPS.6 states the next permissible clinical or operating Work, responsible performer, permission, stop or fallback, and evidence needed before the case-state claim changes. | A bed-board move, record transition, selected action, or elapsed wait proves no treatment, patient change, or clinical resolution. |
| aging and commitment | OPS.7 relates waiting age, deterioration evidence, service horizon, dependencies, consequences, and current commitments for the separately authorized priority and commitment decisions. | Use the applicable clinical and operating grounds and identify who can revise priority or change the commitment. |
| queues and buffers | OPS.8 coordinates a queue for a supplied clinical/service class and keeps patients awaiting other inputs visible in the wider account. | Queue membership does not supply clinical eligibility, triage, consent or treatment permission. |
| current constraint | OPS.9 distinguishes insufficient qualified service from delayed prerequisites, returns or timing using an admissible professional observation or probe. | A long wait or occupied bed is not a diagnosis or permission to change clinical work. |
| capacity and variability | OPS.10 compares usable resource windows, staffing/capability inputs, arrivals and recovery under the supplied service requirement. | A nominal bed count is not every care class’s capacity; clinical and labor premises remain qualified inputs. |
| interacting structures | OPS.11 coordinates the consequential bed, clinical/support, information and decision relations for one operating change. | A combined view grants no medical, privacy or statutory authority and establishes no patient outcome. |
| human conditions | OPS.12 compares actual duties, support work and recovery before selecting cover or a different arrival schedule. | Qualified clinical and human-condition inputs determine the feasible operating alternatives. |
| service commitments | OPS.13 relates the promised service to usable rooms, qualified team time, existing appointments and an urgent-case reserve. | The responsible parties decide any changed promise; clinical eligibility and priority remain supplied inputs. |
| operating consequences | OPS.14 compares payments and displaced service for the proposed staffing or timing alternatives, including any funding or feasibility gap. | The hospital’s service purpose and protected conditions govern the choice alongside cash consequences. |
| decision-specific account | OPS.15 recovers the due cases, transferred or still-waiting cases, completion events and the service definition. | A completed-visit measure and a due-cohort service measure answer different questions. |
| method improvement | OPS.16 keeps ED-Handover-Readiness-CA1 on its candidate-account branch, identifies the proposed information-checking operations and uses observed missing information or changed clinical conditions to revise their applicability. | The observations support revision of the candidate. Admission, clinical effectiveness, priority, consent, privacy, safety, staffing and worker health each require the applicable evidence or authority. |
| method repertoire | OPS.17 compares recurring subprocedures with conditional case planning when new patient or support facts alter the next action. | The selected operating method preserves the required clinical decisions and case conditions. |
| quality and reliability | OPS.18 connects missed service or recurring operating failures to a permitted response and actual continuation evidence. | Clinical outcomes, product acceptance and operating service evidence retain their own qualified methods. |
| simultaneous operating Work | OPS.19 reconciles patient cases, queues, rooms and qualified team time, service commitments, support burden, and recovery conditions for one bounded operating change. | Bed occupancy or diagnostic throughput cannot substitute for missing clinical priority, consent, safety, staffing, or authority. |
| cultural continuation | OPS.20 returns the receiving-use claim supported for licensed transfer coordinators in the named unit, shift and interval, preserving the handover candidate’s status and truthful stop. A new comparison is selected only for a useful attainable contribution within clinical and administrative authority. | The observations concern use of the proposed practice in this group and interval. A claim about an admitted Method, wider adoption, retention, transfer or clinical effectiveness needs evidence for that claim. |
In a constructed extension, two rooms are each available for four hours. One qualified team has four usable hours, and each planned routine visit requires thirty minutes including turnover work. The responsible practitioners supply eligibility, duration assumptions, clinical priority and protected conditions. Two visits are already committed, and six more are requested. Reserving one team-hour for the supplied urgent-case scenario leaves six routine visits in total: two existing commitments and four additional visits.
OPS.13 therefore supports a proposal for four additional routine visits under both the normal and stated adverse cases. Serving all six additional requests would need another qualified resource arrangement or an agreed later time. A room count cannot supply the missing team capacity. Any proposed deferral still needs to fit the clinical result and the recipient’s service agreement.
OPS.12 follows the support team’s work. Suppose the six routine visits can occur in two groups of three within their permitted windows, preserving the support team’s other duty and recovery. The coordinator can select that authorized schedule and observe actual arrivals, support work and delayed cases. OPS.14 compares the real payments and displaced service if the alternative is extra qualified cover. An allocated share of existing room or salary cost alone does not establish an avoidable payment.
OPS.15 makes the service report answer the recipient’s question. For a separate historical due-date cohort with twenty-seven timely, three late-completed and ten still-open requests, timely service is 27/40 = 67.5%; 27/30 = 90% describes only completed requests. Transfer and cancellation meanings come from the actual service agreement. The coordinator uses that account to handle overdue service while retaining any required clinical inquiry.
OPS.17 selects conditional case planning where changed clinical or home-support facts make the fixed next step inadequate; the recurring qualified subprocedure remains usable inside the case. OPS.18 selects the operating response to a missed service requirement and checks continuation conditions after the intervention. Those results coordinate the service; clinical assessment and treatment evidence come from the responsible practitioners.
OPS.16 can revise the proposed information-checking way while preserving the distinct return for a changed clinical condition. OPS.19 can reconfigure only operating relations supported by current clinical, staffing, service and recovery inputs. OPS.20 can finish with what the licensed coordinators did with the proposed handover practice. Select another probe only if it is authorized and the obtainable evidence justifies the work.
OPS.Application:3 - APP-OPS-03 — AI-assisted software-operation probe
| Operating question | Contribution | Conditions and limits |
|---|---|---|
| operating focus | One software operation, user/service commitments, issues and candidate changes, bounded concurrency, evidence, and stop. | Identify the service and its operating Agent. Distinguish them from the provider, model and tools they use and from the episode and trace under examination. |
| views | Case view for user issue, process view for recurring validation/release, queueing view for tool/context capacity, project view for a migration, conditional control view for observation/intervention loops. | Software engineering assurance, security, model capability, provider authority, and human authority retain their owners. |
| subjects | Issue, agent episode, candidate change, Work item, tool access, trace event, test result, human decision, and release record remain distinct. | Use a trace for the events it records and the Work those events support. A causal claim or a complete state account needs its own basis. |
| current account | Current candidate/evidence correspondence, uncertainty, permissions, next decision, bounded context and concurrency, refresh and handoff recovery. | For a claim about release, transfer, safety or effectiveness, use evidence of that result and any required authority. |
| admission | OPS.5 uses current context and tool capacity, bounded concurrency, integration burden, evidence needs, and established authority to decide which exact issue, episode, diagnostic, test, or change Work may start. | — |
| case continuation | OPS.6 handles an admitted issue under the software Method, selects or returns the next permissible Work, and reports issue or candidate progression only after performance evidence supports it. | — |
| aging and commitment | OPS.7 relates issue age, user and service consequence, dependencies, evidence, integration load, recovery burden, bounded concurrency, and promised horizon to a local priority or commitment disposition. | — |
| queues and buffers | OPS.8 distinguishes ready issues or test packages from matters awaiting inputs, and states the tool-access and protection conditions for the selected service. | Episode counts and board columns are not one interchangeable queue or delivered-result population. |
| current constraint | OPS.9 tests generation speed, acceptance capacity, missing evidence and rework as different explanations of lost accepted results. | A local benchmark or faster artifact generation does not establish whole-service improvement. |
| capacity and variability | OPS.10 compares usable tool/provider, test and acceptance capacity with burst, retry and recovery load. | Token/context limits, accessible hours and qualified human acceptance are different constraints; a scenario is not a service promise. |
| interacting structures | OPS.11 coordinates configuration/evidence bindings, provider access, acceptance and deployment decisions. | A passing run or complete dependency diagram grants no integration, security or release authority. |
| human conditions | OPS.12 follows review, rework, interruptions and support burden created by faster generation. | Protected recovery and capability remain inputs to any extra acceptance capacity. |
| service commitments | OPS.13 distinguishes draft production, review decisions, accepted outputs and the result promised to the recipient. | A larger generation rate supplies no additional qualified review time or automatic revision of an existing promise. |
| operating consequences | OPS.14 compares charges, additional payments, qualified time made available and accepted results over the same horizon. | A lower cost per generated draft can coexist with higher cost or burden per accepted result. |
| decision-specific account | OPS.15 relates requests, episodes, candidate versions, reviews, tests, acceptance and deployment through their actual subjects. | Repeated attempts remain distinguishable from new accepted service results. |
| method improvement | OPS.16 trials exact admitted AI-ReleasePrep-v3 under its relied-on description only for eligible low-risk changes and records actual release-preparation, review, evidence, burden, fallback, and stop conditions separately. | A provider or model change to an unqualified edition stops that branch; no general capability, causal superiority, high-risk transfer, security, assurance, or release authority is inferred. |
| method repertoire | OPS.17 compares controlled generation, additional qualified acceptance capacity and a changed preparation or acceptance method. | A support change and a semantic Method variant have different evidence-reuse consequences. |
| quality and reliability | OPS.18 returns the acceptance, service-monitoring or recovery finding needed. Take any required action under the applicable authority. | Software assurance, security, field effect and release authority remain separately established where needed. |
| simultaneous operating Work | OPS.19 reconciles generation, incident recovery, human review, test and assurance Work, release queues, provider limits, and deployment authority for one bounded change. | Draft, episode, or ticket counts do not establish accepted changes, releases, service improvement, or authority. |
| cultural continuation | OPS.20 returns the selection claim supported across the two named rotations and release interval, preserving human review, evidence, security, fallback and release conditions. A provider-change replay is selected only for a useful feasible inquiry; current evidence can suffice for an unchanged qualified branch. | Use evidence of selection in the named rotations. A claim that the selected Method was performed requires evidence of that performance. A changed-provider branch needs evidence for that provider condition. |
In a constructed extension, an assisted software-production service can generate sixty candidate drafts per day. Each accepted output requires its own review decision, and qualified staffing supports six such decisions per day. Recent matching days produced four to six accepted outputs from those reviews. A recipient asks for ten accepted outputs tomorrow. The review bound already excludes that request under the present arrangement; the observed range supplies no probability for tomorrow.
OPS.17 compares the current generation policy with limiting starts to supported acceptance work, obtaining qualified review capacity and changing preparation or acceptance. OPS.12 checks how each alternative changes reading, rework, interruption and recovery demands. Use an existing adequate admission policy for the immediate bound; a changed method needs evidence for the effect it claims.
With OPS.13, the responsible parties can offer a later accepted-output target, obtain another qualified arrangement or agree a narrower review service if it is useful to the recipient. They retain the original request as revised, refused or unresolved. The six available review decisions bound the number accepted. Acceptance of a change and authorization to deploy it require their own decisions.
For OPS.14, take a separate constructed day with four accepted outputs due. Each option generates sixty charged drafts for the same demand and uses six individual reviews. The current option costs 1 per draft with no extra rework payment; four outputs are accepted and two rejected. The alternative costs 0.5 per draft plus a 10 rework payment; two are accepted and four rejected. With the same 240 salary and no other payments or receipts that day, payments are 300 versus 280, or 75 versus 140 per output accepted that day. Both leave fifty-four drafts unreviewed; rejected work and paid rework remain unaccepted. The 20 cash saving adds no review capacity. Retain the current arrangement for the four due outputs under the existing human, acceptance, funding and authority conditions.
OPS.15 keeps the request, generated version, review attempt, test result, accepted output and deployment event related without counting them as one result. It also recovers difficult or rejected requests omitted by an apparently favorable acceptance sample.
For a deployed software service, suppose a separately defined account contains one million eligible requests against a 99.9% success objective, and 1,500 of those requests were unsuccessful. OPS.18 identifies a 1,000-request failure allowance consumed at 150%. Under the constructed authorized policy, discretionary feature releases pause while permitted urgent recovery and security work continues. Restart depends on actual service evidence under the agreed criteria. This event-based service result is distinct from acceptance of generated code; each retains its own population, requirement and authority.
OPS.19 can therefore reduce starts, reserve a compatible test environment, or hold release Work while preserving incident recovery and qualified review. OPS.16 can retain an admitted low-risk Method branch only under the exact provider and model condition; a changed, unqualified edition triggers its stop and applicable fallback. OPS.20 may retain a supported selection account for the named rotations without a new trial, but tool use is not cultural continuation and the changed-provider branch remains unknown or stop until qualified. Any new inquiry is selected for its useful attainable contribution; security, assurance, capability, release, employment and governance remain with their owners.
OPS.Application:End
Operations Management Principles Framework Sources and Edition Notes
OPS.Sources:1 - Bibliographic returns for shared sources
The source comparisons above and in the bodies use the following works. The dates identify the editions consulted; the contribution and applicability of each work are explained beside its use.
- Flow and operating trade-offs: Steve Tendon and Daniel Doiron, Tame your Work Flow (2020), and Steve Tendon, The Book of TameFlow (2022, ISBN 978-99957-44-13-7); Donald G. Reinertsen, The Principles of Product Development Flow (2009, ISBN 978-1-935401-00-1). The TameFlow publication page also carries later revisions. OPS uses the consulted books’ option, commitment, constraint and economic-flow mechanisms.
- Operating and financial consequences: Steven M. Bragg, Throughput Accounting: A Guide to Constraint Management (Wiley, 2007), and John A. Caspari and Pamela Caspari, Management Dynamics: Merging Constraints Accounting to Drive Improvement (Wiley, 2004). These historical sources explain the constraint-accounting mechanisms compared in OPS.14 and OPS.19.
- Organizational transactions: Jan L. G. Dietz and Hans B. F. Mulder, Enterprise Ontology: A Human-Centric Approach to Understanding the Essence of Organisation, first edition (2020) and second edition (2024). OPS draws on its production, coordination and commitment distinctions.
- Operating flow and its empirical use: Wallace J. Hopp and Mark L. Spearman, “To Pull or Not to Pull: What Is the Question?”, Manufacturing & Service Operations Management 6(2) (2004), 133–148; Song-Hee Kim and Ward Whitt, “Statistical Analysis with Little’s Law”, Operations Research 61(4) (2013), 1030–1045. Their distinct contributions and limits are explained in OPS.Reference:19.3.
- Coupled operating structures: Hector D. Perez, Kyle C. Harshbarger, John M. Wassick and Ignacio E. Grossmann, “Integrating information, financial, and material flows in a chemical supply chain”, Computers & Chemical Engineering 178 (2023), 108363. Its integrated supply-chain model supports the comparison of connected structures under the case’s assumptions.
- Case conditions and responses: Thomas Hildebrandt and Raghava Rao Mukkamala, “Declarative Event-Based Workflow as Distributed Dynamic Condition Response Graphs”, EPTCS 69 (2011), 59–73, and the DCR documentation. Read these alongside CMMN’s planning model when selecting a representation for case continuation.
- Layered control: Mung Chiang, Steven H. Low, A. Robert Calderbank and John C. Doyle, “Layering as Optimization Decomposition” (2007); Gautam Goel, Niangjun Chen and Adam Wierman, “Thinking Fast and Slow: Optimization Decomposition Across Timescales” (2017); Nikolai Matni, Aaron D. Ames and John C. Doyle, “Towards a Theory of Control Architecture” (2024). These papers supply models of decomposition and operating rates. Figure’s Helix report (2025) describes its own humanoid-control system.
- AI-assisted operation: DORA, State of AI-assisted Software Development (2025.2; see the errata); Hailin Zhong and Shengxin Zhu, AI Harness Engineering: A Runtime Substrate for Foundation-Model Software Agents (2026, v1); Ivan Belcic and Cole Stryker, “What Is Loop Engineering?” (17 July 2026). OPS compares the report, research proposal and provider explanation for their distinct contributions to context, tools, feedback and stopping in software work.
The shared architectural choices explain the contributions of these works and when a change to a source affects an operating decision or finding.
OPS.Sources:2 - Citation
Anatoly Levenchuk, with AI-assisted development and review.
Operations Management Principles Framework.
27 October 2026.
GitHub repository: https://github.com/ailev/FPF
Use the Architectural Reference to find the operating question, method and professional input you need.