Queueing Models of Case Managers
Bibliographic record
Abstract
Many service systems use case managers, servers who are assigned multiple customers and have frequent, repeated interactions with each customer until the customer’s service is completed. Examples may be found in healthcare (emergency department physicians), contact centers (agents handling multiple online chats simultaneously) and social welfare agencies (social workers with multiple clients). We propose a stochastic model of a baseline case-manager system, formulate models that provide performance bounds and stability conditions for the baseline system, and develop two approximations, one of which is based on a two-time-scale approach. Numerical experiments and analysis of the approximations show that increasing case throughput by increasing the probability of case completion can lead to much greater waiting-time reductions than increasing service speed. Many systems place an upper limit on the number of customers simultaneously handled by each case manager. We examine the impact of these caseload limits on waiting time and describe effective, heuristic methods for setting these limits. This paper was accepted by Yossi Aviv, operations management.
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.004 | 0.012 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.005 | 0.002 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.009 | 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".