Case Article—The SafeBirth Clinic
Bibliographic record
Abstract
The effective utilization of capacity is an important operational goal that managers strive to achieve. Most textbooks use the following simple “bottleneck formula” to illustrate the calculation of process capacity: the capacity of each resource is first calculated by examining that resource in isolation; process capacity is then taken as the smallest (bottleneck) among the resource capacities. The bottleneck formula is, in fact, an approximation of the true process capacity and correctly calculates capacity only in some straightforward settings, for example, in processes where each activity requires only one resource and in processes where each resource is dedicated to only one activity. However, when activities require multiple resources simultaneously (collaboration) and when resources are capable of doing multiple activities (multitasking), the simple formula can be significantly inaccurate. Further, several commonly held managerial insights related to process capacity and least-capacity resources that emerge from the formula can be misleading. The main goal of this case is to alert students that, for processes with collaboration and multitasking, the use of the bottleneck formula brings the potential danger of reaching incorrect conclusions about capacity and what constitutes a bottleneck of a process and may eventually lead to erroneous decisions with significant financial impact, for example, investing in procuring an expensive resource without being able to realize the presumed increase in capacity. More generally, the case illustrates the principles of process capacity and bottleneck structures and clarifies some often-repeated misunderstandings on the relationship between process capacity and least-capacity resources. The case also illustrates the importance of using Gantt charts for conveniently displaying schedules of activities.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.007 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.007 | 0.002 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.009 | 0.007 |
| Insufficient payload (model declined to judge) | 0.016 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".