Beruflich Dokumente
Kultur Dokumente
SUNIL CHOPRA
Background
Founded in 1989, Excel Logistics Services (ELS) was a wholly owned subsidiary of Excel and
Co., a large national retail chain. Prior to 1989, Excel handled its own logistics functions, including
warehousing and transportation. In 1989, ELS was spun off as a separate company with the sole
objective of providing logistics services. Initially, all of ELS’s business came from Excel. At present,
only 85 percent of ELS’s business came from the parent company, and ELS was actively seeking
business outside of Excel. Although ELS had plans for growth, it wanted to stay in the business of
providing logistics services to retail chains.
ELS operated a network of seven warehousing and distribution centers for Excel and Co. Each
WDC was assigned a region in which it served all Excel stores. Each WDC typically stocked all
items needed by stores in the region it served. Company buyers at Excel placed orders for
merchandise with suppliers. These orders were based on forecasted demand at retail stores and were
delivered to the WDCs where they were received and held in storage. When stores ran out of a
product, store managers placed replenishment orders for merchandise at the WDC. If the product was
available, the order was picked at the WDC and delivered to the stores. The stores primarily cared
about orders being delivered in the right quantity at the right time.
©2004 by the Kellogg School of Management, Northwestern University. This case was prepared by Professor Sunil Chopra. Cases are
developed solely as the basis for class discussion. Cases are not intended to serve as endorsements, sources of primary data, or
illustrations of effective or ineffective management. To order copies or request permission to reproduce materials, call 800-545-7685
(or 617-783-7600 outside the United States or Canada) or e-mail custserv@hbsp.harvard.edu. No part of this publication may be
reproduced, stored in a retrieval system, used in a spreadsheet, or transmitted in any form or by any means—electronic, mechanical,
photocopying, recording, or otherwise—without the permission of the Kellogg School of Management.
This document is authorized for use only in Prof. Arqum Mateen's Operation Management,,,,, at IIM Kozhikode - EPGP Kozhikode Campus from Dec 2018 to Jun 2019.
EXCEL LOGISTICS SERVICES KEL019
were allowed to place orders for quantities less than a full case because ELS broke open the cases
and shipped the items to the stores in smaller quantities. Thus, it was not unusual to have partial
cases of breakpack items in storage. For full-case items, stores were required to order at least a case.
For these items, ELS only needed to handle cases and did not break them into smaller units.
The WDC at Springfield had a total area of 1.1 million square feet and was divided into six
modules (see Exhibit 1). Breakpack items were stored in Module 1, while full-case items were
stored in Module 3. The other modules were used for sorting and the staging area. On average,
Springfield had an inventory worth $46 million, which corresponded to about a one-month demand
from stores in the region.
Margolis was hired as the general manager at the Springfield WDC in January of the previous
year. A portion of his bonus was based on a quarterly survey of store managers taken by ELS
management. The last survey prior to Margolis’s arrival indicated that store managers were very
dissatisfied with the performance of the Springfield WDC. Springfield was a poor performer and
ranked last within the ELS network. Customers (retail store managers) complained that orders were
late and not delivered in the right quantity.
Upon arriving, Margolis focused his attention on service quality at the WDC. Margolis quickly
realized that no performance data was available within the Springfield WDC. In fact, none of the
processes were well defined. He had to put an entire quality program in place and appointed Robin
Stalk as quality manager. Stalk had spent considerable time at Springfield and was knowledgeable
about the processes and problems. As a first step, Stalk and Margolis identified receiving, inventory
storage, order filling, and shipping as the four key processes at Springfield. Receiving referred to the
process of receiving deliveries from suppliers and putting them into storage at the WDC. Inventory
storage referred to the process of storing products at the WDC. Order filling referred to the process of
receiving a store order, picking required items from storage, and loading the delivery truck. Shipping
referred to the process of transporting the store order from the WDC and delivering it to the store.
These four processes were identified as key because any error in these processes impacted
Springfield’s ability to supply a store order on time and in the right quantity. An error in receiving or
inventory storage could result in an improper quantity of a particular product showing up in the
inventory system. As a result, the WDC could promise delivery to a store from stock, even though
the item was out of stock. This error would be detected when the WDC tried to fill the order and
found they could not. This would cause the delivery to the store to be late. Margolis’s objective was
to manage the four processes in the warehouse in such a way that store orders could be delivered in
the right quantity at the right time.
By June, detailed process flow maps were constructed for each of the four processes (see
Exhibit 2 for receiving) and key objectives were identified for each process. To identify the
objectives, Stalk and Margolis took into account store requirements in terms of delivery accuracy.
The process mapping and objective identification was done in coordination with the personnel
involved with each process. The operators were expected to follow procedures as described in the
process flow maps. The hope was that with more clearly defined processes, performance would
improve. To further motivate personnel, customer survey results for all WDCs were posted all over
the warehouse. Margolis hoped that employees would be motivated to avoid being at the bottom of
the list and encouraged to follow the process more carefully, resulting in better performance. These
actions bore fruit, and Springfield moved up to third place by the fourth quarter. Unfortunately, on an
absolute scale, performance was still quite bad with several dissatisfied store managers.
Margolis needed an approach to take quality to the next level. He had heard of Statistical Process
Control (SPC), and wanted to use the methodology to improve process performance at Springfield.
SPC had traditionally been used in manufacturing settings for measurable variables such as the
thickness of a plate. In a warehouse setting, it was hard to define how wrong a process had been but
easy to classify the outcome as being defective or not. Therefore, Margolis and Stalk decided to
measure whether different stages of a process had been defective or not. The initial focus was on the
receiving process.
• A guard who began the receiving process by checking trailer loads into the WDC yard
• A receiving officer who prepared the receiving packet and keyed received quantities into
the inventory system
• A yard driver who positioned drop trailers in the proper dock door and removed released
trailers to the carrier pickup area
• An unloader who removed the trailer and palletized the product
• A slotter who performed detailed receiving duties (to ensure proper PO, quantity count,
etc.), assigned inbound pallets to stocking locations, and also performed vendor
compliance audits
• A putaway driver who moved received palletized product from the receiving area to the
assigned stocking location
After talking to experienced people involved in the receiving process, Stalk used fishbone
diagrams to identify the following five sources of error that were likely to occur:
All errors that could not be assigned one of these five categories were grouped as “other.” Stalk
also decided to separate the performance data for Modules 1 (breakpack) and 3 (full case).
After 45 days, Stalk had plenty of data to look at (see Exhibits 3, 4, and 5). She still was not sure
how best to organize it and prepare a plan for action.
Discussion Questions
1. Help Stalk organize the data by preparing a run chart.
2. Prepare appropriate process control charts to see if the process is in control. Is the receiving
process in or out of control?
3. Customer service requirements determine that receiving process errors should never exceed 2
percent on any given day. What percentage of the days is likely to exceed 2 percent error,
given the current performance at receiving? Assume a total of 8,000 transactions per day,
4,000 in each module.
4. Prioritize the set of actions you would take to ensure that more than 99 percent of the days
have less than 2 percent receiving process error.
5. Can you think of a continuous improvement framework that Stalk can use as an engine to
improve performance in the receiving process and other processes at Springfield?
Shipping Area
Office
Area
Module
3
Module
1
Receiving Area
Y
Live Floor Compare quantity Return empty
Enter completed
unload? stack? to delivery pallets to
receipt to system
manifest unloading area
N N
Enter slotting Build pallets
Assign trailer to BuildbyPallets
item by Assign pallet to
reassignments to
receiving locat. item stocking location
system
Stage pallets in
File receiving Complete receiving
receiving apron
packet packet