Framework Boundary and Refresh

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.

Do not use it merely because a project exists, a process is documented, a board has cards, a dashboard is visible, a controller exists, or a management school is familiar. Return product or asset engineering, organization change, one human’s capability, strategy, finance, governance, administration, safety, legal, medical, ecological, security, and other specialist results to their owners.

PatternID and reader order

OPS.* is this framework’s PatternID namespace. The numbers are stable addresses. The ten Parts organize twenty-eight pattern bodies for reading, including six nested methods. A result dependency applies when one decision needs the matching result; actual Work can overlap, branch, repeat or start from existing inputs.

Practical entry forms

The following stable example keys select ordinary practical entries in the Readme. Each appears there once. They support direct choice and explicit worked continuations; no Practical-Use Card or separate mantra is selected. Questions outside these examples use the Table of Contents and the full pattern bodies.

Source use and currentness

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. No source school organizes the framework. Each body names the contribution it uses, its current limit, and the observation that reopens that use.

The decision-bearing current comparisons are in OPS.1:11 through OPS.7:11: operating-focus selection versus workflow-first entry; question-relative multi-view coordination versus one canonical or ungoverned mode; subject/relation-first accounts versus case-ID or log-first accounts; qualified shared attention versus a dashboard or latest-record default; bounded admission versus rank or state as start permission; evidenced situation-responsive case continuation versus workflow or automated transition as progress; and decision-relative temporal and commitment disposition versus age or score as automatic rank and authority. Each comparison names its governed loci and smallest reopen condition. 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 actual cross-structure coordination. 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.

Refresh the affected pattern when a source changes its practitioner action, identity, relation, view, account, or stop. 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.19:11 and OPS.20:11 add current comparisons for cross-scale operating reconciliation and bounded population-level cultural probes. They use several-structure, workflow, operating-financial, service-change, and cultural-continuation sources only for their stated mechanisms and limits. Neither pattern 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 actually available.

Queueing and scheduling provide complementary constructions in OPS.10.1/.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.

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–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 supports inspecting actual uses and permitting qualified combinations, not a universal verdict for or against budgeting. One author disclosed a board position. The case supplies no general causal estimate of performance gains. OPS.21–22 retain the functional distinctions and reopen the arrangement when practice contradicts its intended use.

The forecasting text’s distinction between forecasting, goals and planning supports keeping expectation, intended result and action separate. It does not choose the operation’s aim or settle an assessment. The repertoire therefore combines those supplied distinctions with a developed construction of the aim and subsequent judgement, rather than asking a forecast to perform every management function.

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 body’s SoTA-Echoing section retains the more specific mechanism, worked distinction and reopen condition.

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; it is a different relation from a method’s constituent and encompassing 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 actually be released and restored. 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 correspondences are source-supported reasons for the Methods’ organization, not evidence that the complete OPS repertoire outperforms every other arrangement. 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. A changed source title or publication date alone does not establish that gain.

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.
• 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.

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. Retain a permanent link or copy of the edition actually used. 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.

Sibling-domain returns and availability

The patterns have no mandatory sibling-DPF result for every displayed use. The FPF contributions and direct Operations sources needed for each displayed use are named in its pattern body. Clinical, safety, legal, privacy, security, finance, product-release, capability, and other domain results remain direct returns rather than sibling frameworks silently imported into the edition.

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. The supplying methods are available at their own scope. A case-specific capability, staffing, coexistence, cultural, or consequence result must still be established for the receiving Operations 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 available current return, a qualified direct source, or an explicit missing-result blocker.

The following direct returns help when the operating question exposes work owned by a neighboring framework. They are conditional discovery routes, not additional prerequisites for every OPS use. The supplied guidance remains external to this edition; a case-specific result must still satisfy the receiving OPS conditions.

Use the linked contribution only while its current content still 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.

Available packages

These package labels keep the questions and returned results distinct. They do not prescribe an operating lifecycle, maturity ladder, or reader sequence; start from the current question and use the smallest body or exact cooperating set that can change the decision.

Representative case coverage

Edition return

This publication contains the Readme, Table of Contents, Preface, ten Parts, nine connected practical entries, three extended applications, framework boundary and the pattern bodies listed in the contents.

Use any of the twenty-eight 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.

Use the package table and each body’s conditions to locate the Operations result that can change the current decision.

Publication boundary

Pattern bodies are the authoritative working references. The Readme, Preface, Table of Contents, practical entries, and applications help readers enter and combine them; they do not replace conditions, evidence boundaries, stops, or specialist returns.

This is a domain framework Reference carrier. It is neither an educational Guide nor the Engineering DPF Suite Reference. A Guide is organized for learning and memory formation; this Reference is organized for lookup and direct pattern use.

Citation

Anatoly Levenchuk, with AI-assisted development and review.
Operations Management Principles Framework.
2 October 2026.
GitHub repository: https://github.com/ailev/FPF