InteractiveMap of Operations Research
Back to Uncertainty & Stochastic Systems
TheoryIntermediate03.02
Uncertainty & Stochastic Systems

Queueing Theory

Waiting lines, service systems, and congestion.

Overview

Queueing Theory focuses on waiting lines, service systems, and congestion. In the map of OR, it connects Arrival process, Service process, Traffic intensity to decisions that must be modeled, solved, explained, and revised as evidence changes.

Estimate waiting time, utilization, and capacity needs. Little's Law and M/M/c models give powerful first answers. The practical use case is clearest in Hospitals, Call centers, Cloud, Airports, Manufacturing, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

Arrival process

Arrival process is a core checkpoint for Queueing Theory: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Service process

Service process is a core checkpoint for Queueing Theory: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Traffic intensity

Traffic intensity is a core checkpoint for Queueing Theory: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Little's Law

Links average work-in-process, throughput, and flow time under broad steady-state conditions.

M/M/c

M/M/c is a core checkpoint for Queueing Theory: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with Hospitals: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into Arrival process, Service process, and Traffic intensity; define units and data sources for each one.
  3. 3Build a small instance of Queueing Theory that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

HospitalsCall centersCloudAirportsManufacturing
  • Hospitals: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Call centers: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Cloud: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Airports: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Manufacturing: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.

Common pitfalls

  • Applying Queueing Theory because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating Arrival process as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources