Operations ResearchUnit 911 min read
Queuing Theory: Models, Metrics, and Real-World Applications
Unit 9 of Operations Research covers queuing theory fundamentals—arrival patterns, service disciplines, single/multi-channel models, and key performance metrics (L, W, λ, μ)—with solved examples, visuals, and ties to Nepalese services like eSewa, NTC, and Pathao.
TAKEAWAYS:
- Queuing theory models customer flow (arrivals, service times) to optimize wait times and resource use in systems like banks, hospitals, and ride-hailing apps.
- Kendall’s notation (e.g., M/M/1) encodes arrival/service distributions and server channels—critical for matching models to real problems.
- Little’s Law () links average queue length (), arrival rate (), and wait time ()—use it to solve for any unknown.
- Single-channel vs. multi-channel systems differ in stability (e.g., M/M/1 can have infinite queues, while M/M/c cannot).
- Cost-volume analysis balances service costs vs. wait-time costs to find the optimal number of servers (e.g., how many eSewa counters to open).
- Exam focus: Memorize formulas for , , , and ; recognize when to use M/M/1, M/M/c, or M/G/1; and interpret real-world scenarios (e.g., NTC call centers, Daraz delivery queues).
1. What is a Queue? Core Definitions
A queue is a line of entities (customers, data packets, vehicles) waiting for service from one or more servers. Queuing theory studies how to design systems to minimize waiting time and cost while maximizing throughput.
Key Terms Visualized
Real-World Analogy:
- eSewa counters: Customers (arrivals) wait for service (bill payment) at a single server (counter). If the counter is busy, the queue grows.
- Pathao drivers: Riders (arrivals) wait for drivers (servers) to accept their requests. The "service time" is the time from request to pickup.
2. Arrival and Service Patterns
Queuing theory assumes arrivals and service times follow probability distributions. The most common are:
| Distribution | Notation | Meaning | Example in Nepal |
|---|---|---|---|
| Markovian (Memoryless) | M | Exponential inter-arrival/service times | NTC call center calls arrive randomly. |
| Deterministic | D | Fixed time between arrivals/services | Bus arrivals at a stop (every 10 minutes). |
| General | G | Arbitrary distribution | Daraz delivery times vary by distance. |
| Poisson Process | λ (lambda) | Arrivals per unit time (e.g., 96 patients/24h) | Emergency clinic patients. |
Worked Example 1: Arrival Rate Calculation Problem: In a clinic, 96 patients arrive in 24 hours. What is the arrival rate () in patients per minute? Visual:
3. Queue Disciplines: How Customers Are Served
The queue discipline defines the order in which customers are served. Common types:
flowchart TD
A["Queue Discipline"] --> B["FIFO (First-In-First-Out)"]
A --> C["LIFO (Last-In-First-Out)"]
A --> D["SIRO (Service In Random Order)"]
A --> E["Priority"]
A --> F["Shortest Processing Time (SPT)"]
B -->|"Example"| G["eSewa counters"]
E -->|"Example"| H["NTC VIP calls"]
F -->|"Example"| I["Pathao driver assignment"]Comparison Table:
| Discipline | Description | Advantages | Disadvantages | Nepalese Example |
|---|---|---|---|---|
| FIFO | First come, first served. | Fair, easy to implement. | Long waits for early arrivals if service is slow. | Bank queues, NTC call centers. |
| Priority | High-priority customers served first. | Critical tasks handled urgently. | Low-priority customers may wait indefinitely. | Emergency rooms, Ncell VIP support. |
| SPT | Shortest job first. | Minimizes total wait time. | Long jobs may starve. | Daraz order processing (shortest delivery time first). |
| SIRO | Random order. | Reduces bias. | Unpredictable for customers. | Traffic police directing vehicles. |
4. Single-Channel Queuing Model (M/M/1)
The simplest model: one server, arrivals follow a Poisson process (rate ), service times are exponentially distributed (rate ).
Key Metrics
Worked Example 2: Clinic Queue Analysis Problem: A clinic has patients/minute and patients/minute (service time = 10 minutes). Find:
- Utilization (),
- Average queue length (),
- Average wait time ().
Solution:
- (stable, since ).
- patients.
- minutes (41 seconds).
Visual:
Real-World Tie-In:
- NTC Call Center: If calls arrive at calls/hour and each call takes calls/hour (10 minutes), (unstable! NTC needs more agents).
- eSewa Counter: If 10 customers/hour arrive and the agent processes 15/hour, (efficient, but occasional waits).
5. Multi-Channel Queuing Model (M/M/c)
Multiple servers (e.g., eSewa counters) reduce wait times. Key formulas:
Worked Example 3: Optimal Number of eSewa Counters Problem: eSewa has customers/hour. Each agent serves customers/hour. Find:
- Minimum for ,
- and for .
Solution:
- For : (unstable). For : (stable).
- Using Erlang C:
- .
- customers.
- minutes.
Visual:
Cost-Volume Analysis: eSewa must balance:
- Cost of adding a counter: Rs. 50,000/month per agent.
- Cost of waiting: Rs. 1,000/hour per customer (lost business). For , minutes → Rs. 27.5/hour/customer. Total wait cost = . If adding a 4th counter reduces to 0.5 minutes (Rs. 8.33/hour/customer), the savings may justify the cost.
6. Special Cases and Extensions
| Model | Description | When to Use | Example |
|---|---|---|---|
| M/M/1/K | Finite queue capacity (K). | Limited space (e.g., 5 seats in a taxi). | Pathao driver’s max passengers. |
| M/G/1 | General service time distribution. | Variable service times (e.g., Daraz orders). | Delivery times vary by distance. |
| M/M/c/K | Multi-server, finite queue. | Call centers with limited hold capacity. | NTC with 100-number limit. |
| M/M/∞ | Infinite servers (no queue). | Idealized (e.g., infinite doctors). | Not realistic! |
Worked Example 4: Pathao Driver Queue (M/M/1/K) Problem: A Pathao driver accepts requests with requests/hour and serves request/hour. Max passengers . Find:
- Probability the driver is idle (),
- Probability a rider is rejected (queue full).
Solution:
- .
- Probability of 3 riders: . Rejection rate = 2.5%.
Visual:
7. Queuing Theory in Nepal: Real-World Applications
mindmap
root((Queuing Theory in Nepal))
eSewa
"Single-server model (M/M/1) for counters"
"Multi-server (M/M/c) for peak hours"
NTC
"Call center: M/M/c with priority queues"
"Unstable if ρ > 1 (too many calls)"
Pathao
"Driver assignment: SPT discipline"
"Queue length depends on rider density"
Daraz
"Order processing: M/G/1 (variable delivery times)"
"Warehouse queues: M/M/c"
Banks
"ATM queues: M/M/1 with finite capacity"
"Teller queues: Priority for VIPs"
NEPSE
"Trading system: M/M/c with time limits"
"Queue discipline: FIFO for orders"Case Study: NTC Call Center Optimization
- Current: 50 agents, calls/hour, calls/hour/agent. (underutilized!).
- Problem: Long wait times due to inefficient routing.
- Solution:
- Reduce with IVR (auto-attendant).
- Add priority queues for VIP customers.
- Use Erlang C to optimize agent count.
Visual:
8. Exam Tip: How to Score Full Marks
Memorize Kendall’s Notation:
- Always state the model (e.g., "This is an M/M/1 queue") before solving.
- Example: "For the clinic, arrivals are Poisson () and service is exponential (), so it’s M/M/1."
Show All Steps:
- Write down every formula and substitution. Examiners reward clarity.
- Example:
Given: λ = 20/hour, μ = 10/hour, c = 3. Step 1: ρ = λ/(cμ) = 20/30 = 0.667. Step 2: Use Erlang C to find L_q.
Interpret Results:
- Don’t just compute ; explain: "This means the average queue length is 0.55 customers, so eSewa can reduce counters from 3 to 2 without significant wait increases."
Real-World Links:
- Tie problems to Nepalese services (e.g., "Like NTC call centers, this problem has unstable queues when ρ > 1").
- Use local examples in explanations (e.g., "Pathao drivers use SPT to minimize wait times").
Graphical Answers:
- Draw queue diagrams (even roughly) to show system structure.
- Plot cost vs. number of servers to justify optimal .
Common Pitfalls:
- Forgetting stability: Always check for M/M/1.
- Mixing L and L_q: = in system; = in queue only.
- Ignoring units: is per hour/minute; ensure consistency.
9. Practice Problems (Exam-Style)
Ncell Hotline: Calls arrive at calls/hour. Each call takes calls/hour.
- Is the system stable? If not, how many agents are needed for ?
- Find for the stable case.
Kathmandu Traffic Light: Cars arrive at cars/second. The light turns green every 30 seconds (service time = 20 seconds).
- Model this as M/D/1. Find and .
- Suggest improvements using queuing theory.
Daraz Warehouse: Orders arrive at orders/hour. Packing takes orders/hour.
- If Daraz adds 2 more packers (), what is the new ?
- Calculate the cost savings if wait-time cost is Rs. 500/order/hour.
10. Summary Table for Quick Revision
11. Final Visual: Queuing Theory in Action
Based on the TU BIT syllabus for Operations Research (ORS255), unit 9.
Discussion
Loading…