fpf.tools
DPF

Operations Management Principles Framework

28 patterns · 734 sections

Choose a heading to read that text in full, or open the complete publication.

Read full textSearch this publicationOriginal Markdown

Table of contents

Overview · All sections
  1. Operations Management Principles Framework
  2. Table of Contents
  3. Public units
  4. Part I — Bound the Operation and Select Coordination Views
  5. Part II — Recover Operating Subjects and Maintain Current State
  6. Part III — Admit Demand and Continue Cases
  7. Part IV — Revise Priority and Existing Commitments
  8. Part V — Coordinate Queues and Treat the Current Constraint
  9. Part VI — Qualify Capacity and Coordinate Operating Structures
  10. Part VII — Protect Human Conditions and Establish Service Commitments
  11. Part VIII — Compare Operating Consequences and Build Useful Accounts
  12. Part IX — Improve Methods, Control Quality, Reconcile Work, and Continue Practice
  13. Part X — Choose Operating Aims and Interpret Performance
  14. Operations Management Principles Framework Readme
  15. Practical entries
  16. OPS-PUMPWORKS — Find the next supported controller-service decision
  17. OPS-SERVICE-WINDOW — Offer service that rooms, people and commitments can support together
  18. OPS-ACCEPTED-RESULT — Faster generation still leaves the promised result unavailable
  19. OPS-PRACTICE-CHANGE — Change the way of working without treating publication as successful use
  20. OPS-RELEASE-AND-WAIT - Change admission without losing the customer’s wait
  21. OPS-PROTECT-AND-DEVELOP - Prepare or learn while preserving promised service
  22. OPS-PREPARE-AND-RESPOND - Prepare useful work and keep a response possible
  23. OPS-ADVICE-IN-USE - Follow an operating explanation into the user’s work
  24. OPS-AIMS-AND-PERFORMANCE — Set a meaningful aim and interpret what follows
  25. Operations Management Principles Framework Architectural Reference
  26. OPS.Reference:1 - Start from a difficulty in continuing operation
  27. OPS.Reference:2 - Competing demands on one operation
  28. OPS.Reference:3 - Work, descriptions, structures, and records remain distinct
  29. OPS.Reference:4 - Demand, commitments, subjects, and units remain distinct
  30. OPS.Reference:5 - Several management views can coexist on the same Work
  31. OPS.Reference:6 - Shared attention is stronger than visibility and weaker than consensus
  32. OPS.Reference:7 - The control branch is conditional
  33. OPS.Reference:8 - Pattern relations do not prescribe an operating lifecycle
  34. OPS.Reference:9 - Use the Methods together where their results meet
  35. OPS.Reference:10 - Conditions on a whole combination
  36. OPS.Reference:11 - Check the combined decision and its result
  37. OPS.Reference:12 - Architectural Rationale
  38. OPS.Reference:13 - Apply the repertoire in production and service settings
  39. OPS.Reference:14 - Gains, burden and limits of combined use
  40. OPS.Reference:15 - What this publication covers and leaves outside
  41. OPS.Reference:16 - Intended use and ordinary non-use
  42. OPS.Reference:17 - PatternID and reader order
  43. OPS.Reference:18 - Practical entry forms
  44. OPS.Reference:19 - Source use and shared architectural choices
  45. OPS.Reference:19.1 - Operating aims and performance sources
  46. OPS.Reference:19.2 - Shared source choices for the repertoire
  47. OPS.Reference:20 - FPF dependency and compatibility
  48. OPS.Reference:21 - Sibling-domain returns and availability
  49. OPS.Reference:22 - Available contributions
  50. OPS.Reference:23 - Representative case coverage
  51. OPS.Reference:24 - Edition return
  52. OPS.Reference:25 - Publication boundary
  53. OPS.Reference:End
  54. Part I — Bound the Operation and Select Coordination Views
  55. OPS.1OPS.1 - Identify the Operating System, Commitments, and Flow Units
  56. OPS.1:0 - Use This When
  57. OPS.1:0.1 - Working Distinctions
  58. OPS.1:1 - Problem Frame
  59. OPS.1:2 - Problem
  60. OPS.1:3 - Forces
  61. OPS.1:4 - Solution
  62. OPS.1:4.1 - Pattern-Use Unfolding
  63. OPS.1:4.2 - Record the Result
  64. OPS.1:4.3 - What Changes in Practice
  65. OPS.1:5 - Archetypal Grounding — PumpWorks Continuing Control Service
  66. OPS.1:6 - Bias-Annotation
  67. OPS.1:7 - Conformance Checklist
  68. OPS.1:8 - Common Anti-Patterns and How to Avoid Them
  69. OPS.1:9 - Consequences
  70. OPS.1:10 - Rationale
  71. OPS.1:11 - SoTA-Echoing
  72. OPS.1:12 - Relations
  73. OPS.1:End
  74. OPS.2OPS.2 - Select Work-Management Views and Coordination Methods
  75. OPS.2:0 - Use This When
  76. OPS.2:0.1 - Working Distinctions
  77. OPS.2:1 - Problem Frame
  78. OPS.2:2 - Problem
  79. OPS.2:3 - Forces
  80. OPS.2:4 - Solution
  81. OPS.2:4.1 - Pattern-Use Unfolding
  82. OPS.2:4.2 - Record the Result
  83. OPS.2:4.3 - What Changes in Practice
  84. OPS.2:5 - Archetypal Grounding — PumpWorks Mixed Operating Views
  85. OPS.2:5.1 - Identify the useful views
  86. OPS.2:5.2 - Choose and combine actual coordination rules
  87. OPS.2:6 - Bias-Annotation
  88. OPS.2:7 - Conformance Checklist
  89. OPS.2:8 - Common Anti-Patterns and How to Avoid Them
  90. OPS.2:9 - Consequences
  91. OPS.2:10 - Rationale
  92. OPS.2:11 - SoTA-Echoing
  93. OPS.2:12 - Relations
  94. OPS.2:End
  95. Part II — Recover Operating Subjects and Maintain Current State
  96. OPS.3OPS.3 - Distinguish Operating Subjects, Cases, Queues, Resources, and Records
  97. OPS.3:0 - Use This When
  98. OPS.3:0.1 - Working Distinctions
  99. OPS.3:1 - Problem Frame
  100. OPS.3:2 - Problem

Showing 1–100 of 734 entries. Source edition 8c72429c9a07.