MSHR 6610 Week 4 Erlang C Staffing Model Example

Aligning Human Resources with Business Operations Walden University Free custom sample in 24 to 48h

This MSHR 6610 Week 4 staffing model example converts call demand into agents on the phones and then into agents on the schedule, printing every assumption next to the number it produces. Walden MSHR 6610 introduces queuing by name at this point, so the composite utility's model runs Erlang C, described by Gans, Koole and Mandelbaum, for seven intervals against an 80 percent within thirty seconds target: 52 agents for the Monday 8:00 a.m. peak, 37 at 6:00 p.m., 31 at 7:30 p.m. A separate step applies 35 percent shrinkage, so 37 agents on the phones means about 57 scheduled. An assumptions table gives each input's source and what happens if it is wrong, such as three more agents for each extra thirty seconds of handle time. Limits are named, citing Koole, in a model written for the MS in Human Resource Management.

CourseMSHR 6610 Aligning Human Resources with Business Operations
WeekWeek 4
Paper typeStaffing model
LengthAbout 820 words, 5 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramMS in Human Resource Management
UpdatedOctober 2026

Free sample paper for MSHR 6610 Week 4

1

From Calls to Seats to People: An Erlang C Staffing Model for a Utility Contact Center That Converts Agents Needed on the Phones Into Agents Scheduled, With Every Assumption Printed Beside Its Number

Student Name

Walden University

MSHR 6610: Aligning Human Resources with Business Operations

Instructor Name

Month Day, Year

What this page is doingThe title names the two conversions the model performs and its rule about showing assumptions.
2

From Calls to Seats to People: An Erlang C Staffing Model for a Utility Contact Center That Converts Agents Needed on the Phones Into Agents Scheduled, With Every Assumption Printed Beside Its Number

The Model

The demand analysis established how many calls Northfork Power & Light's contact center receives in each half hour and how long they take. This model asks how many agents each interval needs. It uses Erlang C, the queuing formula most commonly used to staff inbound call centers (Gans et al., 2003). Erlang C treats calls as arriving at random and waiting in a single queue until an agent is free. Given the number of calls, the average handle time and a number of agents, it estimates the share of calls that will wait and how long they will wait. The model is run with increasing numbers of agents until the result meets the service target. Here the target is the center's existing standard: 80 percent of calls answered within thirty seconds.

What this page is doingThe queuing model is named and its central idea explained, because staffing by rule of thumb is what the model replaces.
3

Agents Needed on the Phones

The workload column is the number of agents that would be needed if every agent were busy every second; the extra agents in the next column are what it takes to keep waits short when calls arrive unevenly. The gap is proportionally larger in smaller intervals, which is why evening and Saturday intervals need relatively more agents per unit of workload than the Monday morning peak.

Table 1

Erlang C Results for Selected Intervals

IntervalCalls per half hourAverage handle timeWorkload in agentsAgents needed for 80/30Predicted service levelOccupancy |
Monday 8:00 a.m.2106.5 min45.55284 percent88 percent |
Monday 12:00 p.m.1606.5 min34.74081 percent87 percent |
Monday 5:00 p.m.1507.0 min35.04184 percent85 percent |
Monday 6:00 p.m.1357.0 min31.53783 percent85 percent |
Monday 7:30 p.m.1107.0 min25.73184 percent83 percent |
Bill day 8:00 a.m.2356.5 min50.95781 percent89 percent |
Saturday 9:00 a.m.956.5 min20.62581 percent82 percent |

Composite utility. Inputs are illustrative; outputs calculated with the Erlang C formula for a 30-second target.

From Seats to People

Agents needed on the phones are not the same as agents on the schedule. Some scheduled time is always lost to breaks, training, team meetings, coaching and absence. The center's records put this shrinkage at about 35 percent of scheduled time. To have 37 agents on the phones at 6:00 p.m., the center must schedule about 37 divided by 0.65, or 57 agents. For the Monday 8:00 a.m. peak, it must schedule about 80.

Table 2

Assumptions Behind the Model

AssumptionValue usedSourceEffect if wrong |
Service target80 percent within 30 secondsCenter's standardA stricter target needs more agents |
Handle time, daytime6.5 minutesThirteen-week averageEach extra 30 seconds adds about 3 agents at the peak |
Handle time, evening7.0 minutesThirteen-week averageAs above |
Shrinkage35 percentCenter's scheduling recordsEach 5 points adds about 5 scheduled agents at 6:00 p.m. |
Calls arrive at randomAssumedStandard for Erlang CBunched arrivals worsen waits |
Callers do not hang upAssumed by Erlang CModel limitationReal abandonment makes the model somewhat conservative |

Composite utility. Sensitivities are approximate.

What this page is doingShrinkage is applied as a separate, visible step, because it is where staffing models most often hide optimistic assumptions.
4

Limits of Erlang C

Erlang C assumes that callers never hang up and that every agent can take every call. Neither is true here. Callers who wait too long abandon, which lowers the load the remaining agents face, so the model tends to overstate the agents needed slightly when service is poor. More importantly, calls involving balances need a billing-certified agent, and only some agents are certified. Koole (2013) describes how skill-based routing complicates staffing models; this model treats all agents as interchangeable, so it understates the need for certified agents on billing-heavy intervals. The constraint brief later in the course addresses that directly.

Checking the Model

The model's predictions can be checked against last quarter's actual results. On evenings when about 33 agents were on the phones at 6:00 p.m., the center recorded service levels in the high thirties, close to what the model predicts for that staffing. That agreement gives some confidence in the inputs, though a single interval is a narrow test.

What the Model Shows

The model confirms what the demand analysis suggested. Evening intervals need about 31 to 41 agents on the phones, or about 48 to 64 scheduled, while the current evening roster schedules about 50 at 5:00 p.m. and fewer later. Mornings are adequately covered. The shortfall is concentrated in the evenings, and it is a scheduling problem as much as a hiring one. Aksin et al. (2007) note that staffing and scheduling are usually solved together; the next step is to compare the model's requirements with the actual schedule, interval by interval.

References

Aksin, Z., Armony, M., & Mehrotra, V. (2007). The modern call center: A multi-disciplinary perspective on operations management research. Production and Operations Management, 16(6), 665-688. https://doi.org/10.1111/j.1937-5956.2007.tb00288.x

Gans, N., Koole, G., & Mandelbaum, A. (2003). Telephone call centers: Tutorial, review, and research prospects. Manufacturing & Service Operations Management, 5(2), 79-141. https://doi.org/10.1287/msom.5.2.79.16071

Koole, G. (2013). Call center optimization. MG Books.

MSHR 6610 Week 4 instructions, in plain terms

Week 4 asks you to build a staffing model for the operation you analyzed. Name the model you use and explain its central idea in plain language. Calculate the staff needed in each interval to meet a stated service target, showing inputs and outputs in a table. Convert staff needed on the work into staff needed on the schedule by applying shrinkage as a visible, separate step. List every assumption with its source and how the result would change if it were wrong. Discuss the model's limits honestly, especially those that matter in your setting, and close with what the model shows about where your current schedule falls short.

How the MSHR 6610 Week 4 example is put together

The model opens by naming Erlang C and its logic, citing Gans and colleagues. A table shows calls, handle time, workload, agents needed, predicted service and occupancy for seven intervals. A paragraph explains why small intervals need proportionally more agents. A section applies 35 percent shrinkage, converting 37 agents on the phones into 57 scheduled. A second table lists six assumptions with sources and sensitivities. A section checks the model against last quarter's results. A limits section covers abandonment and skills, citing Koole. A closing section confirms the evening shortfall, citing Aksin and colleagues on solving staffing and scheduling together. Every number in the first table can be traced to an input in the second.

Where the marks sit in the MSHR 6610 Week 4 rubric

Staffing models earn credit for transparency. Naming the model and explaining it plainly is expected. A table showing inputs and outputs for each interval is weighted heavily. Applying shrinkage as a separate, visible step shows care, since that is where optimistic assumptions often hide. Listing assumptions with sources and sensitivities demonstrates rigor and makes the model checkable. Discussing limits that matter in the setting, such as skill-based routing, shows depth. Checking the model against actual results shows good practice. Models that use rules of thumb without a stated method, hide shrinkage or present outputs without assumptions tend to receive lower marks from instructors in this program. A short check against recent actual results strengthens confidence in the model.

Common MSHR 6610 Week 4 mistakes, and how to avoid them

Gather calls per interval, average handle time and your service target. Use an Erlang C calculator or spreadsheet to find the smallest number of agents that meets the target in each interval, and record the predicted service level. Then divide by one minus your shrinkage rate to get scheduled staff. Write down every number you assumed and where it came from. Students often skip shrinkage or bury it, which leads to schedules that look adequate on paper and fail on the floor. Another frequent gap is ignoring skills when only some staff can handle certain work. Check your model against a recent week if you can. If you need help setting up the calculation, our writers can build a template with you.

Get a MSHR 6610 Week 4 example written to your instructions

Upload the staffing model instructions, the rubric and whatever demand figures earlier weeks produced; the model is built on those or on labeled stand-ins. Interval table, shrinkage step and sensitivity test return in 24 to 48 hours, free the first time. Any calculator you are required to use can be named in the request.

More MSHR 6610 papers and MS in Human Resource Management samples

MSHR 6610 Week 4 questions, answered

Where can I find a free MSHR 6610 Week 4 sample paper?

Both tables and the full staffing model are open to read here without charge.

Which model does the MSHR 6610 Week 4 paper use?

Erlang C, the standard queuing formula for inbound call centers.

How many agents does 6:00 p.m. need?

About 37 on the phones, or about 57 scheduled after 35 percent shrinkage.

Why is shrinkage a separate step?

It is where staffing models most often hide optimistic assumptions.

What are the model's main limits?

It ignores callers who hang up and treats all agents as able to take every call.