Library / Operations Management Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:30:10 UTC

OPS.8:11 - SoTA-Echoing

Practice question and selected lineSerious alternative, trade-off and pattern changeSource roles, limits and reopen condition
How should local completion and downstream readiness be coordinated? Adapt whole-operation ready-supply and complete-kit reasoning.Local column limits are cheaper but can miss joins; a complete-kit rule applied to the whole case can block useful investigation. Sections 4.1–4.4 and 5.1 instead bind readiness to the next service while retaining total waiting. The added input matching is justified when it changes dispatch or 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; no pool-all default is selected.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.