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