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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:05:20 UTC

OPS.10:11 - SoTA-Echoing

Practice question and selected lineSerious alternative, trade-off and pattern changeSource 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) supplies the mature mean-relation basis, not a deadline model. 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 only when that omission can reverse the decision.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 rather than selecting a universal utilization or pooling rule.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.