ELE227 Service operation management

Service operation managementUnit 610 min read

Queuing Theory & Waiting Line Models: Systems, Metrics & Applications

Unit 6 of Service Operation Management covers queuing theory fundamentals—single/multi-channel systems, arrival patterns, service disciplines, and performance metrics (L, Lq, W, Wq)—with real-world applications in call centers, banks, and e-commerce, plus worked examples using Poisson and exponential distributions.

TAKEAWAYS

  • Queuing theory models waiting lines (queues) mathematically to optimize service efficiency, balancing cost and customer satisfaction.
  • Key metrics (L, Lq, W, Wq) measure queue length and waiting time using Poisson arrivals and exponential service times.
  • Single-channel vs. multi-channel systems differ in cost, flexibility, and performance—visualized via arrival/service rate trade-offs.
  • Real-world examples: eSewa’s payment queues, Ncell’s customer service calls, and Daraz’s order fulfillment use these models to reduce delays.
  • Exam focus: Case studies (e.g., BIROI’s customer care), control charts for queue stability, and assumptions of single-channel systems.

1. What is Queuing Theory?

Queuing theory is a mathematical framework that analyzes waiting lines (queues) to optimize service operations. It helps businesses:

  • Reduce customer wait times.
  • Minimize operational costs (e.g., staffing, infrastructure).
  • Improve resource utilization (e.g., servers, tellers, call agents).

Core Components

Poisson Distribution (λ)Arrival ProcessExponential Service (μ)Service MechanismFIFOLIFORandomQueue DisciplineSingle-ChannelMulti-ChannelSystem CapacityQueuing System
Hierarchical breakdown of queuing system components

2. Key Definitions and Notations

Term Symbol Definition
Arrival Rate λ Average customers arriving per unit time (e.g., 10 customers/hour).
Service Rate μ Average customers served per unit time (e.g., 8 customers/hour).
Utilization Factor ρ = λ/μ Probability the system is busy (ρ < 1 for stability).
Queue Length (L) L Average number of customers in the system (waiting + being served).
Waiting Line Length (Lq) Lq Average number of customers waiting in line.
Time in System (W) W Average time a customer spends in the system.
Waiting Time (Wq) Wq Average time a customer spends waiting in line.

Formula Relationships:


3. Types of Queuing Systems

A. Single-Channel vs. Multi-Channel Systems

Feature Single-Channel Multi-Channel
Example Single teller at a bank Multiple ATMs in a bank
Cost Low (one server) High (multiple servers)
Flexibility Inflexible (bottleneck at one point) Flexible (distributes load)
Performance Higher wait times if λ > μ Lower wait times (parallel processing)
Applications Small businesses, single-counter services Call centers, airports, hospitals

B. Arrival and Service Patterns

  1. Arrival Process:

    • Poisson Distribution: Random arrivals (e.g., customers at a café).
    • Deterministic: Fixed intervals (e.g., buses every 10 minutes).
  2. Service Time:

    • Exponential Distribution: Random service times (e.g., call durations).
    • Constant: Fixed service time (e.g., assembly line tasks).

4. The M/M/1 Queuing Model (Single-Channel)

The simplest model: 1 server, Poisson arrivals, exponential service.

TimeRate (customers/hour)OArrival Rate (λ)Service Rate (μ)ρ = λ/μλμ
Graph showing λ vs. μ in M/M/1 model (λ=5, μ=10)

Key Metrics

For ρ = λ/μ < 1 (stable system):

Worked Example: Ncell Customer Care

  • Given:
    • Arrival rate (λ) = 12 calls/hour.
    • Service rate (μ) = 15 calls/hour.
    • Question: What is the average wait time (Wq) for customers?
  • Solution: Interpretation: Customers wait 16 minutes on average before being served.
08:00 AMFirst call arrives(λ=10/min)08:05 AMAgent handles call(μ=12/min)08:10 AMQueue length Lq=208:15 AMAverage wait Wq=3min
Timeline of Ncell call center queue dynamics

5. The M/M/c Queuing Model (Multi-Channel)

For c servers, Poisson arrivals, exponential service: Where:

  • = Probability of 0 customers in the system.
  • = Number of servers.

Worked Example: eSewa Payment Queue

  • Given:
    • λ = 20 transactions/hour.
    • μ = 10 transactions/hour per agent.
    • c = 3 agents.
    • Question: What is the average queue length (Lq)?
  • Solution: (Calculate numerically or use software.)

6. Queue Discipline and Applications

Discipline Definition Example
FIFO First-In-First-Out (standard) Bank queues, call centers
LIFO Last-In-First-Out (rare) Stacks (e.g., emergency exits)
Priority High-priority customers served first Hospitals (critical cases), airlines
Random Customers served in random order Some call centers

In the Real World

  1. eSewa (Nepal):

    • Uses M/M/c models to optimize payment processing queues during festivals (e.g., Dashain, Tihar).
    • How: Adjusts the number of payment agents (c) based on predicted arrival rates (λ) to minimize Wq.
  2. Ncell Customer Care:

    • Applies M/M/1 to analyze call wait times.
    • Case: During peak hours (6–9 PM), λ increases to 25 calls/hour, but μ remains 20 calls/hour. The system becomes unstable (ρ > 1), leading to long queues. Solution: Hire temporary agents or implement IVR (Interactive Voice Response) to reduce λ.
  3. Daraz Order Fulfillment:

    • Uses multi-channel queues for warehouse picking.
    • How: Orders are split across multiple pickers (c), reducing Lq for high-demand products (e.g., Diwali sales).

7. Assumptions of Single-Channel Queuing (M/M/1)

  1. Arrivals follow a Poisson process (random, independent).
  2. Service times are exponentially distributed (memoryless).
  3. The system has infinite capacity (no maximum queue length).
  4. Customers balk (leave if the queue is too long) or renege (leave while waiting) are ignored.
  5. First-Come-First-Served (FIFO) discipline.

When Assumptions Fail:

  • Example: A hospital emergency room has priority queues (not FIFO) and finite capacity (limited beds).
  • Solution: Use non-Markovian models (e.g., G/G/1) or simulation tools.

Queuing metrics (L, W) can be plotted on control charts to monitor stability:

  • Upper Control Limit (UCL) and Lower Control Limit (LCL) for L and W.
  • Example: BIROI’s customer care tracks Wq daily. If Wq exceeds UCL, it indicates understaffing.

Worked Example: Control Limits for Mean Chart Given sample means:

Sample Mean (X̄) Range (R)
1 15 7
2 17 4
... ... ...
  1. Calculate Center Line (CL):
  2. Calculate Control Limits (using A₂ and D₄ factors for n=5):
  3. Interpretation: If any X̄ falls outside [12.73, 20.27], the process is out of control (e.g., sudden increase in Wq).

Exam Tip

  1. Case Studies (30% weight):

    • Do: Analyze given scenarios (e.g., BIROI) using M/M/1 or M/M/c formulas.
    • Avoid: Memorizing formulas without applying them to real data.
    • Example Question:

      "A bank has λ=10 customers/hour and μ=12 customers/hour. Calculate L and W if they add a second teller." Solution: Switch to M/M/2, recalculate ρ and metrics.

  2. Assumptions (10% weight):

    • Must-know: List 5 assumptions of M/M/1 (e.g., Poisson arrivals, FIFO).
    • Exam Trap: Questions may ask, "Which assumption fails in a hospital ER?" → Answer: Priority discipline, finite capacity.
  3. Control Charts (20% weight):

    • Focus: Calculate CL, UCL, LCL for L or W using given data.
    • Tip: Use A₂, D₄ tables (provided in exams) for small samples.
  4. Real-World Applications (20% weight):

    • Link theory to practice: e.g., "How would Daraz reduce Wq during sales?" → Answer: Increase c (more pickers) or optimize λ (predictive demand).
  5. Short Answers (20% weight):

    • Key Terms: Define ρ, Lq, W, balking, reneging.
    • Formulas: Write M/M/1 metrics from memory.

mindmap
  root((Queuing Theory in Exams))
    Case Studies
      BIROI Electronics
      Bank Queues
      Hospital ERs
    Formulas
      M/M/1 Metrics
      M/M/c Metrics
      Control Limits
    Assumptions
      Poisson Arrivals
      Exponential Service
      FIFO Discipline
    Applications
      eSewa Payments
      Ncell Calls
      Daraz Orders

Based on the TU BBM syllabus for Service operation management (ELE227), unit 6.

Discussion

Loading…