14 - Modeling Service Systems
14 - Modeling Service Systems
C H A P T E R
14 MODELING SERVICE
SYSTEMS
“No matter which line you move to, the other line always moves faster.”
—Unknown
14.1 Introduction
A service system is a processing system in which one or more services are pro-
vided to customers. Entities (customers, patients, paperwork) are routed through
a series of processing areas (check-in, order, service, payment) where resources
(service agents, doctors, cashiers) provide some service. Service systems exhibit
unique characteristics that are not found in manufacturing systems. Sasser, Olsen,
and Wyckoff (1978) identify four distinct characteristics of services that distin-
guish them from products that are manufactured:
1. Services are intangible; they are not things.
2. Services are perishable; they cannot be inventoried.
3. Services provide heterogeneous output; output is varied.
4. Services involve simultaneous production and consumption; the service
is produced and used at the same time.
These characteristics pose great challenges for service system design and man-
agement, particularly in the areas of process design and staffing. Having dis-
cussed general modeling procedures common to both manufacturing and service
system simulation in Chapter 7, and specific modeling procedures unique to
manufacturing systems in Chapter 12, in this chapter we discuss design and
operating considerations that are more specific to service systems. A description
is given of major classes of service systems. To provide an idea of how simula-
tion might be performed in a service industry, a call center simulation example is
presented.
357
Harrell−Ghosh−Bowden: I. Study Chapters 14. Modeling Service © The McGraw−Hill
Simulation Using Systems Companies, 2004
ProModel, Second Edition
powerful strategic and competitive weapon. Here are some typical internal per-
formance measures that can be evaluated using simulation:
• Service time.
• Waiting time.
• Queue lengths.
• Resource utilization.
• Service level (the percentage of customers who can be promptly serviced,
without any waiting).
• Abandonment rate (the percentage of impatient customers who leave the
system).
Just taking a customer order, moving it through the plant, distributing these require-
ments out to the manufacturing floor—that activity alone has thirty sub-process steps
to it. Accounts receivable has over twenty process steps. Information processing is a
whole discipline in itself, with many challenging processes integrated into a single
total activity. Obviously, we do manage some very complex processes separate from
the manufacturing floor itself.
This entire realm of support processes presents a major area of potential applica-
tion for simulation. Similar to the problem of dealing with excess inventory in
manufacturing systems, customers, paperwork, and information often sit idle in
service systems while waiting to be processed. In fact, the total waiting time for
entities in service processes often exceeds 90 percent of the total flow time.
The types of questions that simulation helps answer in service systems can be
categorized as being either design related or management related. Here are some
Harrell−Ghosh−Bowden: I. Study Chapters 14. Modeling Service © The McGraw−Hill
Simulation Using Systems Companies, 2004
ProModel, Second Edition
service force, or the servicing policies and procedures can be modified to run
additional experiments.
usually have both front-room and back-room activities with total service being
provided in a matter of minutes. Customization is done by selecting from a menu
of options previously defined by the provider. Waiting time and service time are
two primary factors in selecting the provider. Convenience of location is another
important consideration. Customer commitment to the provider is low because
there are usually alternative providers just as conveniently located.
Examples include banks (branch operations), restaurants, copy centers, bar-
bers, check-in counters of airlines, hotels, and car rental agencies.
process. For large items such as furniture or appliances, the customer may have to
order and pay for the merchandise first. The delivery of the product may take
place later.
Examples include department stores, grocery stores, hardware stores, and
convenience stores.
process, then the service time is short. If the service is a technical support process,
then the service time may be long or the call may require a callback after some
research.
Examples include technical support services (hotlines) for software or hard-
ware, mail-order services, and airline and hotel reservations.
14.7.1 Background
Society Bank’s Information Technology and Operations (ITO) group offers a “help
desk” service to customers of the ITO function. This service is offered to both in-
ternal and external customers, handling over 12,000 calls per month. The client
services help desk provides technical support and information on a variety of tech-
nical topics including resetting passwords, ordering PC equipment, requesting
phone installation, ordering extra copies of internal reports, and reporting main-
frame and network problems. The help desk acts as the primary source of commu-
nication between ITO and its customers. It interacts with authority groups within
ITO by providing work and support when requested by a customer.
The old client services help desk process consisted of (1) a mainframe help
desk, (2) a phone/local area network help desk, and (3) a PC help desk. Each of
the three operated separately with separate phone numbers, operators, and facili-
ties. All calls were received by their respective help desk operators, who manually
logged all information about the problem and the customer, and then proceeded to
pass the problem on to an authority group or expert for resolution.
Because of acquisitions, the increased use of information technologies, and the
passing of time, Society’s help desk process had become fragmented and layered
with bureaucracy. This made the help desk a good candidate for a process redesign.
It was determined that the current operation did not have a set of clearly defined
goals, other than to provide a help desk service. The organizational boundaries of the
current process were often obscured by the fact that much of the different help desks’
work overlapped and was consistently being handed off. There were no process per-
formance measures in the old process, only measures of call volume. A proposal was
made to consolidate the help desk functions. The proposal also called for the intro-
duction of automation to enhance the speed and accuracy of the services.
call level. Level 1 calls are resolved immediately by the help desk, Level 1A calls
are resolved later by the help desk, and Level 2 calls are handed off to an author-
ity group for resolution.
Historically, calls averaged 2.5 minutes, lasting anywhere from 30 seconds
to 25 minutes. Periodically, follow-up work is required after calls that ranges from
1 to 10 minutes. Overall, the help desk service abandonment rate was 4 to 12 per-
cent (as measured by the percentage of calls abandoned), depending on staffing
levels.
The help desk process was broken down into its individual work steps and
owners of each work step were identified. Then a flowchart that described the
process was developed (Figure 14.1). From the flowchart, a computer simulation
model was developed of the old operation, which was validated by comparing
actual performance of the help desk with that of the simulation’s output. During
the 10-day test period, the simulation model produced results consistent with
those of the actual performance. The user of the model was able to define such
model parameters as daily call volume and staffing levels through the use of the
model’s Interact Box, which provided sensitivity analysis.
Joint requirements planning (JRP) sessions allowed the project team to col-
lect information about likes, dislikes, needs, and improvement suggestions from
users, customers, and executives. This information clarified the target goals of the
process along with its operational scope. Suggestions were collected and priori-
tized from the JRP sessions for improving the help desk process. Internal bench-
marking was also performed using Society’s customer service help desk as a ref-
erence for performance and operational ideas.
FIGURE 14.1
Customer problem, Client notification
Flow diagram of
query, or change and escalation
client services.
Customer self-service
Automated resolution
alternative staffing
levels. 0.14 600 calls per day
0.12 550 calls per day
0.10 500 calls per day
0.08 450 calls per day
0.06 400 calls per day
0.04
0.02
0
5 6 7 8 9 10
Operators staffed
Harrell−Ghosh−Bowden: I. Study Chapters 14. Modeling Service © The McGraw−Hill
Simulation Using Systems Companies, 2004
ProModel, Second Edition
will change when the average daily call volume or the number of operators varies.
The importance of this graph is realized when one notices that it becomes increas-
ingly harder to lower the abandonment rate once the number of operators increases
above seven. Above this point, the help desk can easily handle substantial
increases in average daily call volume while maintaining approximately the same
abandonment rate.
After modeling and analyzing the current process, the project team evaluated
the following operational alternatives using the simulation model:
• The option to select from a number of different shift schedules so that
staffing can easily be varied from current levels.
• The introduction of the automated voice response unit and its ability to
both receive and place calls automatically.
• The ability of the automated voice response unit to handle device resets,
password resets, and system inquiries.
• The incorporation of the PC and LAN help desks so that clients with
PC-related problems can have their calls routed directly to an available
expert via the automated voice response unit.
• The ability to change the response time of the ASIM problem-logging
system.
Additionally, two alternative staffing schedules were proposed. The alterna-
tive schedules attempt to better match the time at which operators are available for
answering calls to the time the calls are arriving. The two alternative schedules
reduce effort hours by up to 8 percent while maintaining current service levels.
Additional results related to the Alternative Operations simulation model were
• The automated voice response unit will permit approximately 75 percent
of PC-related calls to be answered immediately by a PC expert directly.
• Using Figure 14.2, the automated voice response unit’s ability to aid in
reducing the abandonment rate can be ascertained simply by estimating
the reduction in the number of calls routed to help desk operators and
finding the appropriate point on the chart for a given number of operators.
• Improving the response time of ASIM will noticeably affect the operation
when staffing levels are low and call volumes are high. For example, with
five operators on staff and average call volume of 650 calls per day, a
25 percent improvement in the response time of ASIM resulted in a
reduction in the abandonment rate of approximately 2 percent.
14.7.3 Results
The nonlinear relationship between the abandonment rate and the number of op-
erators on duty (see Figure 14.2) indicates the difficulty in greatly improving per-
formance once the abandonment rate drops below 5 percent. Results generated
from the validated simulation model compare the impact of the proposed staffing
changes with that of the current staffing levels. In addition, the analysis of the
Harrell−Ghosh−Bowden: I. Study Chapters 14. Modeling Service © The McGraw−Hill
Simulation Using Systems Companies, 2004
ProModel, Second Edition
effect of the automated voice response unit can be predicted before implementa-
tion so that the best alternative can be identified.
The introduction of simulation to help desk operations has shown that it can
be a powerful and effective management tool that should be utilized to better
achieve operational goals and to understand the impact of changes. As the au-
tomation project continues to be implemented, the simulation model can greatly
aid management and the project team members by allowing them to intelligently
predict how each new phase will affect the help desk.
14.8 Summary
Service systems provide a unique challenge in simulation modeling, largely due
to the human element involved. Service systems have a high human content in the
process. The customer is often involved in the process and, in many cases, is the
actual entity being processed. In this chapter we discussed the aspects that should
be considered when modeling service systems and suggested ways in which
different situations might be modeled. We also discussed the different types of
service systems and addressed the modeling issues associated with each. The ex-
ample case study showed how fluid service systems can be.
References
Aran, M. M., and K. Kang. “Design of a Fast Food Restaurant Simulation Model.” Simu-
lation. Norcross, GA: Industrial Engineering and Management Press, 1987.
Collier, D. A. The Service/Quality Solution. Milwaukee: ASQC Quality Press, 1994.
Harrell−Ghosh−Bowden: I. Study Chapters 14. Modeling Service © The McGraw−Hill
Simulation Using Systems Companies, 2004
ProModel, Second Edition