| Course | MSHR 6610 Aligning Human Resources with Business Operations |
|---|---|
| Week | Week 3 |
| Paper type | Demand analysis |
| Length | About 770 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | MS in Human Resource Management |
| Updated | October 2026 |
Free sample paper for MSHR 6610 Week 3
What Arrives, When and How Long It Takes: A Demand Analysis of a Utility Contact Center's Calls by Half-Hour, Weekday and Billing Cycle, Separating Recurring Patterns From Storm Spikes
Student Name
Walden University
MSHR 6610: Aligning Human Resources with Business Operations
Instructor Name
Month Day, Year
What Arrives, When and How Long It Takes: A Demand Analysis of a Utility Contact Center's Calls by Half-Hour, Weekday and Billing Cycle, Separating Recurring Patterns From Storm Spikes
Why Demand Comes First
Requests for more agents at Northfork Power & Light's contact center usually begin with a supervisor's sense that the floor is busy. This analysis asks what the pattern behind that feeling is. It reads thirteen weeks of illustrative call history by half-hour interval, day of week and billing cycle, converts volume into workload and separates demand that recurs, which a roster should be built around, from demand that does not, such as storm outage calls. Aksin et al. (2007) describe forecasting call arrivals by interval as the foundation of call center staffing, since every later decision depends on it.
Volume by Interval and Day
Three patterns recur. Monday mornings carry the week's heaviest volume, as customers call about weekend problems. The two days after bills post bring a second peak, about 12 percent above an ordinary day, driven by billing questions. And the three hours after the dinner-time peak begins at five carry steady, substantial volume that falls off only slowly, since many residential customers call after work.
Table 1
Average Calls Offered per Half Hour, Selected Intervals, Thirteen-Week Average
| Interval | Monday | Wednesday | Two days after bills post | Saturday | |
|---|---|---|---|---|
| 8:00 to 8:30 a.m. | 210 | 165 | 235 | 95 (9:00) | |
| 12:00 to 12:30 p.m. | 160 | 140 | 185 | 70 | |
| 5:00 to 5:30 p.m. | 150 | 130 | 160 | Closed | |
| 6:00 to 6:30 p.m. | 135 | 120 | 145 | Closed | |
| 7:30 to 8:00 p.m. | 110 | 95 | 115 | Closed | |
Composite utility. Illustrative thirteen-week averages excluding the two storm days identified below.
From Volume to Workload
Calls do not take the same time at every hour. Daytime calls average about six and a half minutes, including after-call work. Evening calls are slightly longer, about seven minutes, because more involve payment arrangements. Multiplying calls by handle time gives workload in agent-hours per interval. A Monday 8:00 a.m. interval carries about 23 agent-hours of work in a half hour, needing about 46 agents' worth of talk time before any allowance for queuing; a Monday 6:00 p.m. interval carries about 16 agent-hours, or about 32 agents' worth. The evening workload is smaller than the morning peak but larger than the evening roster, which was built when evening volume was lower.
Outliers
Koole (2013) recommends removing such one-off events from the base forecast and planning for them separately. Two days in the thirteen weeks carried outage-driven volume three to four times normal, after a windstorm. Those calls were short, mostly people reporting outages and asking about restoration times, and most could be handled by the automated outage line. Including them in the averages would raise every interval's forecast and lead to a roster staffed for storms on ordinary days. The analysis excludes them from the recurring pattern and treats storm response as a separate plan, using cross-trained back-office staff and the automated line.
Seasonality and Trend
The thirteen weeks run from late winter into spring, when heating bills are high and disconnection notices peak. Summer volume is about 10 percent lower, except during heat waves. Over the past two years, total volume has grown about 3 percent a year, mostly in evening calls, as more customers work daytime hours away from home. That trend is part of why the evening roster has fallen behind: the roster was last rebuilt three years ago, when evening calls made up a smaller share of the day, and nobody has revisited it since.
What the Analysis Supports
Two smaller patterns are worth noting even though they do not change the roster. Lunch hours from noon to 1:30 p.m. carry a modest bump as customers call during their own breaks, and Friday afternoons are the lightest weekday interval, which makes them the natural time for training and team meetings that pull agents off the phones. Placing that off-phone time on Friday afternoons rather than Monday mornings would cost almost nothing and remove a self-inflicted shortfall the current schedule creates at the week's busiest hour. The analysis supports three conclusions for the staffing work that follows. Demand in the early evening is recurring, substantial and growing, and the roster should be built around it. The bill-posting peak is predictable and can be covered with scheduled overtime or shifted breaks on those days. Storm spikes should not shape the regular roster at all. Gans et al. (2003) caution that forecasts based on averages understate variation from one week to the next; the staffing model will therefore add a margin for normal variation but not for storms.
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 3 instructions, in plain terms
Week 3 asks you to analyze the demand your operation faces before proposing staffing changes. Use historical data to show volume by interval, day of week and any cycle that matters in your setting, such as billing dates or seasons. Convert volume into workload by multiplying by the time each unit of work takes. Identify recurring patterns and separate them from outliers, explaining how outliers should be handled instead of building them into the regular schedule. Note seasonality and trend. Close with the conclusions your analysis supports for staffing and the limits of your data, so the next stage of work can be built on a pattern rather than an impression.
Inside the MSHR 6610 Week 3 example
The analysis opens by explaining why demand comes first, citing Aksin and colleagues on forecasting. A table shows average calls per half hour for five intervals across four day types. A section identifies three recurring patterns. A section converts volume into agent-hours, showing that evening workload exceeds the evening roster. A section removes two storm days as outliers, citing Koole, and assigns them to a separate plan. A section notes seasonal and trend effects and the three-year-old roster. A closing section draws three conclusions, including scheduling off-phone time on Friday afternoons, citing Gans and colleagues on week-to-week variation. Each conclusion names the interval or day it applies to, which keeps the analysis tied to the roster.
MSHR 6610 Week 3 rubric: what earns full marks
Demand analyses earn credit for turning raw volume into a pattern the roster can follow. Showing volume by interval and day is weighted heavily. Converting volume into workload with handle times shows understanding of what drives staffing. Separating recurring demand from outliers, and explaining how outliers are handled, demonstrates judgment. Attention to seasonality and trend shows the analysis looks beyond one period. Conclusions tied directly to the data make the analysis useful for the staffing model that follows. Analyses that report daily totals only, include extreme days in averages or jump to a staffing recommendation without examining the pattern tend to receive lower marks. Clear labeling of illustrative figures is also expected.
Common MSHR 6610 Week 3 mistakes, and how to avoid them
Pull at least a quarter of history from your workforce or operations system and arrange it by interval and day. Look for the peaks that repeat and the ones that happen once. Multiply volume by average handle time to see workload, since a busy interval with short calls may need fewer staff than a quieter one with long calls. Remove one-off events and plan for them separately. Students often average everything together, which hides both peaks and quiet periods. Another frequent problem is building the roster around a crisis week. Write down what your data cannot show. If your system exports data in an awkward format, our writers can help you organize it into usable tables.
Get a MSHR 6610 Week 3 example written to your instructions
Share the demand analysis prompt with its rubric, plus any volume data your instructor posts; an illustrative dataset is built when none is supplied. The interval exhibits and workload conversion reach you in 24 to 48 hours, and your first sample costs nothing. Figures from your own employer are never requested.
More MSHR 6610 papers and MS in Human Resource Management samples
- MSHR 6610 Week 1: Two Ledgers Discussion Post
- MSHR 6610 Week 2: Service Request Workflow Map
- MSHR 6610 Week 4: Erlang C Staffing Model
- MSHR 6610 Week 5: Staffing Coverage Memo
- MSHR 6610 Week 6: Theory of Constraints Brief
- MSHR 6610 Week 7: Transition Gap Peer Replies
- MSHR 6610 Week 8: Turnover Cost Analysis
- MSHR 6610 Week 9: Operational Metrics Note
- MSHR 6610 Week 10: Schedule Change Rollout Plan
- MSHR 6610 Week 11: HR Operations Recommendation Memo
- MHRM 6902 Week 3: Analytical Aptitude Competency Map
- MHRM 6101 Week 3: Peak-Season Shortfall Case Memo
- MHRM 6901 Week 3: Stated Versus Actual Gap Analysis
- MHRM 6801 Week 3: Organizational Symptom Review
MSHR 6610 Week 3 questions, answered
Where can I find a free MSHR 6610 Week 3 sample paper?
The demand analysis is reproduced below and free to read.
What patterns does the MSHR 6610 Week 3 analysis find?
Monday morning peaks, a bill-posting bump and steady, growing evening volume.
How is volume converted to workload?
By multiplying calls by handle time, six and a half minutes by day and seven in the evening.
How are storm days handled?
They are removed from the recurring pattern and handled by a separate storm plan.
What does the analysis conclude?
The roster should be built around evening demand, with bill-day peaks covered by planned overtime.