Flowcasting The Retail Supply Chain PDF
Flowcasting The Retail Supply Chain PDF
Flowcasting The Retail Supply Chain PDF
Flowcasting: Introduction
I N T R O D U C T I O N
➫
I magine that you’re a race car driver, and you’re minutes away from
the most important event of your Formula 1 racing career. Your
world class pit crew has prepped your car from front to end, and
everything in between. All systems are go. Your team pushes your car
into place at the starting line, and you climb in. The steering wheel
is locked into place. The countdown begins, and the first starting
light flashes. Then the second, followed by the third, fourth, and
finally the fifth. The lights simultaneously flicker off indicating the
start of the race. Your engine roars, and then you discover something
terrible: the steering wheel isn’t connected to anything, and you’re
out of the race.
This is an apt analogy for what happens in retail supply chains
today. The retailer may have great wholesale and manufacturing
partners, but if the retail store is disconnected from its trading part-
ners, the retail supply chain will never win the race to cut costs while
offering the best customer service. Instead, the retail supply chain
will function like the race car with the disconnected steering wheel -
- it will have tremendous brute force to push forward, but it will have
little ability to steer a course, react to changing "road" conditions, or
carry out a well-executed plan.
Because of this disconnect, the retail store is often considered
the weakest link in the retail supply chain -- a notion supported by
19
0 introduction 4/4/06 1:00 PM Page 2
Flowcasting: Introduction
1
Flowcasting is a new concept and is derived from the DRP Process created and
implemented by André Martin at Abbott Laboratories in the mid 1970’s
20
0 introduction 4/4/06 1:00 PM Page 3
Flowcasting: Introduction
21
0 introduction 4/4/06 1:00 PM Page 4
Flowcasting: Introduction
22
0 introduction 4/4/06 1:00 PM Page 5
Flowcasting: Introduction
23
0 introduction 4/4/06 1:00 PM Page 6
Flowcasting: Introduction
it possible to plan and execute promotions that are profitable for all
trading partners involved in the exercise.
24
0 introduction 4/4/06 1:00 PM Page 7
Flowcasting: Introduction
25
0 introduction 4/4/06 1:00 PM Page 8
Flowcasting: Introduction
26
0 introduction 4/4/06 1:00 PM Page 9
Flowcasting: Introduction
by 6 cents on the dollar (which represents the high end of the range)
would generate savings of over $600 billion (USD) to be shared by
trading partners and the consumer.
As you’ll see throughout this book, Flowcasting opens remark-
able opportunities for cutting costs while boosting profitability and
customer service.
But…Does It Work
At this point you might be thinking, "Yes….but can you really elimi-
nate forecasting everywhere but at the retail store level?" The answer
is a resounding "yes." To test the Flowcasting concept, we conducted
several simulations and pilots. Our latest simulation involved gener-
ating 378 different sales forecasts at the store/SKU level at a Fortune
100 Consumer Goods Manufacturer. To provide a context for the
results of the simulation, we chose a study conducted by Georgia
Tech’s Marketing Analysis Laboratory. The study provides data,
summarized in Figure 1, about the state-of-the-art in forecasting
accuracy.
27
0 introduction 4/4/06 1:00 PM Page 10
Flowcasting: Introduction
forecast total corporate sales for the year than it is to forecast sales at
the strategic business unit or specific product (SKU) level. Yet fore-
casting at the business unit, SKU, and SKU by location (retail, whole-
sale and manufacturing DCs) must be done. And the lower the level,
the less accurate the forecast. Now what if, as a manufacturer, you
had to forecast at the store/SKU level as well? Would your forecast-
ing accuracy improve? Actually, it would most likely continue to
deteriorate below the level reported in the study (67 percent to 70
percent), even though no statistics on forecast accuracy are available
at the store/SKU level.
Can we improve on the current state-of-the-art? Let’s return to
our simulation for an answer. The objective for the manufacturer in
our simulation was to use Flowcasting to forecast what one of its
retail trading partners, also a Fortune 100 company (which we’ll
refer to as "Retailer X"), would sell during a given month for a sam-
ple of six products. The products included two high-volume SKUs,
two medium-volume SKUs, and two low-volume SKUs sold across a
group of 63 stores. The simulation would then subsequently forecast
what Retailer X would purchase from the manufacturer for that
month.
The simulation was performed on November 12, 2005. First, a
sales forecast for December 2005 and the following eleven months
was created for every product (SKU) in every store for a total of 378
separate forecasts. Then, the Flowcasting system netted store inven-
tories (inventory on store shelves and back room) the morning of
November 12, considered store/SKU safety stock requirements, and
used each store’s ordering rules (minimum ship quantities, lead
times, and shipping schedules) to create a model of what each store
would most likely order by day and week for the next twelve months.
The results were accumulated for the six products across all 63
stores and aggregated to show what Retailer X would specifically buy
from the manufacturer during December. The information was kept
for seven weeks. Then, in early January 2006, when the December
2005 orders from Retailer X had been received and shipped, a com-
parison was made between orders received in December and the fore-
cast made seven weeks earlier for December.
28
0 introduction 4/4/06 1:00 PM Page 11
Flowcasting: Introduction
29
0 introduction 4/4/06 1:00 PM Page 12
Flowcasting: Introduction
30
0 introduction 4/4/06 1:00 PM Page 13
Flowcasting: Introduction
André Martin
Mike Doherty
Jeff Harrop
May 2006
31
0 introduction 4/4/06 1:00 PM Page 14
Flowcasting
32
0 introduction 4/4/06 1:00 PM Page 15
Flowcasting
Section 1:
Flowcasting Basics
33
0 introduction 4/4/06 1:00 PM Page 16
Flowcasting
34
Flowcasting: Chapter 1
C H A P T E R 1
➫
B ack in 1958, Jay Forrester, then a professor at MIT, wrote a
groundbreaking article stating that a volume increase of 10 per-
cent at the retail store level actually cascades and translates into a 40
percent increase at the manufacturing level. His findings, which
originally appeared in the Harvard Business Review, were later doc-
umented and published in a book entitled Industrial Dynamics.
Forrester’s work focused on the behavior of the flows of money,
orders, materials, personnel, and capital equipment across what we
refer to today as "retail supply chains." He found that these five flows
were integrated by an information network. This information net-
work gave retail supply chains their own dynamic characteristics.
Interestingly, Forrester calculated that the four-fold increase at
the manufacturing level would take six months to manifest itself.
This makes sense, given the fact that in those days, most business
was done by snail mail.
Fast forward to the 21st century. Remarkably, the multiplier
between retailer and manufacturer is still the same: four-fold. The
only difference is that the ripple effect takes days or weeks, not
months, to materialize thanks to the use of communication tech-
nologies that form the life blood of today’s networked supply chains.
The elapsed time may have shrunk, but the volume amplifier effect
remains because we still manage the nodes in a supply chain inde-
35
Flowcasting: Chapter 1
36
Flowcasting: Chapter 1
usually functions in a vacuum. The same holds true for the RDC,
which looks at the needs of the stores it supports as an aggregate sum
that’s computed on the basis of history such as warehouse with-
drawals. It is only a coincidence if the aggregate forecasts at the RDC
level relate at all to what is actually happening on the retail shelves.
At the next downstream level in the supply chain, from the
manufacturing DCs to the factory floor, you’ll typically see tighter
planning and data integration due to the use of MRPII and ERP. But
even the most exquisite choreography among the manufacturing
nodes won’t improve supply chain management unless all the various
nodes are connected with actual demand at the retail store level.
Nonetheless, few retailers today actually forecast at store level;
instead, forecasting typically starts at the RDC, and is ultimately done
throughout the supply chain. The farther from the consumer that
the forecasting takes place, the less accurate the forecasts are likely
to be. And depending on what’s being forecasted, inaccuracies can
have a significant impact on a business. Inaccurate sales forecasts
across a given retail supply chain translate into increased operating
costs and lower customer service levels for all trading partners. In
addition, inaccurate sales forecasts lead directly to:
• Lost sales
• Dissatisfied customers
• Too much inventory
• Increased selling costs
• Increased distribution costs
• Increased manufacturing costs
• Increased purchasing costs
• Obsolescence
To appreciate the roots of forecasting inaccuracies, consider a
typical retail supply chain (see Figure 1.1), which consists of two sep-
arate legal entities, a retailer and a manufacturer.
The retailer owns the first two nodes, which consist of the retail
store and the RDC and the manufacturer owns the last two nodes, the
manufacturing DC (MDC) and the plant. In an effort to generate the
best forecast, both the retailer and manufacturer must forecast at
multiple levels. Let’s start with the forecasting on the retailer’s side.
mus test of a "good" plan is financial. Will the plan generate enough
cash from operations to meet our targets? Will we have to borrow to
support store expansions, and store renovations and closings?
In other words, the planning, by definition forecasting, is relat-
ed more to the blessings or condemnation of Wall Street than to the
planned flow of product from manufacturer to retailer to consumer.
And therein lies the problem; these higher-level forecasts are not
linked to the day-to-day business activities and lower level forecasts
that drive replenishment into the stores, which in turn drives replen-
ishments (purchases from suppliers) into the distribution centers. As
a result, it would be a remarkable coincidence if the sum of the store
and DC forecasts were to add up to the corporate sales forecast!
39
Flowcasting: Chapter 1
41
Flowcasting: Chapter 1
Dependent Demand
Years ago in the auto industry, people realized that once you fore-
casted how many of a particular car model you would assemble and
then sell, you could easily calculate the demand for tires, steering
wheels, hubcaps and a variety of other parts. These item level fore-
casts were based on "dependent demand" -- that is, they depended
entirely on another item’s forecast (the assembly schedule).
Dependent demand is important in retail planning as well.
Consider the supply chain shown in Figure 1.4. It consists of a dis-
tribution channel (or network) with four levels: a factory, a manufac-
turer’s distribution center (MDC1), two retail distribution centers
(RDCs 1 and 2) and four retail stores. At every node of this distribu-
tion channel, a customer/supplier relationship has been created. For
example, the factory has one customer, MDC1. MDC1 plays a dual
role -- it is the customer of the factory and the supplier to RDC1 and
RDC2. RDCs 1 and 2 also play dual roles; each is a customer of MDC1,
and each is a supplier to a specific number of stores (two each in this
example).
42
Flowcasting: Chapter 1
43
Flowcasting: Chapter 1
44
Flowcasting: Chapter 1
45
Flowcasting: Chapter 1
Figure 1.6: POS Forecast based on retail DC that supports more than 100 stores.
Figure 1.7 shows the effect of yet another factor that diminish-
es the value of RDC level forecasts: shelf resets at store-level.
The area of the graph on the left, beginning just before 9/28,
represents the additional demand on the RDC as the number of fac-
ings for this product is increased at the stores. These changes are
scheduled to occur on different dates at the different stores.
The area in the middle of the graph, beginning at 11/23, repre-
sents the depressed demand on the RDC that results from returning
the number of facings to the original level at the end of the selling
season. Again, these changes are scheduled to occur on different
dates at the different stores.
Notice that there is a significant difference between the two
curves, showing that the product forecasted has excess inventory at
the stores that will take some time to sell off. This situation is repre-
sented by the lower dependent demand curve which, over the course
of a year, finally catches up to the POS forecast curve. The point is
that any calculation that does not take inventory at the stores into
account on a store-by-store basis will provide the supplier with an
incorrect picture of the future.
46
Flowcasting: Chapter 1
Summary
In this first chapter, we’ve looked at the traditional retail supply chain
model in which hundreds of forecasts are generated by various func-
tional trading partner groups. We’ve also commented on the prob-
lems associated with that model. Here are the key points to remem-
ber:
47
Flowcasting: Chapter 1
48
chapter 2 4/4/06 1:05 PM Page 1
Flowcasting: Chapter 2
C H A P T E R 2
From Forecasting to
Flowcasting
The New Art and Science of
Managing a Retail Supply Chain
➫
A Brief History of Supply Chain Technology
Since the advent of the industrial revolution, manufacturers built
distribution facilities to match their unique needs. As they grew,
manufacturing businesses found that it made sense to build distrib-
ution centers in geographic areas with heavy customer concentra-
tions. Doing so enabled them to achieve economies of scale; they
could manufacture products in a specific city, then ship full or near-
ly full truckloads to a given distribution center in another city, there-
by reducing transportation, handling and warehousing costs. This
approach not only saved money through newfound efficiencies, but it
enabled manufacturers to improve customer service.
Wholesalers and retailers followed a similar course. Retailers,
for example, found that it made sense to build distribution centers in
geographic areas with a heavy concentration of retail stores. The
motivation was the same as with manufacturers: achieving
economies of scale in transportation, handling and warehousing
costs, and improving service to retail stores and consumers. As mar-
kets further expanded, wholesalers and retailers began to look for
additional opportunities to reduce their distribution costs. This led to
the beginning of warehouse automation projects, many of which are
still going on today.
49
chapter 2 4/4/06 1:05 PM Page 2
Flowcasting: Chapter 2
50
chapter 2 4/4/06 1:05 PM Page 3
Flowcasting: Chapter 2
51
chapter 2 4/4/06 1:05 PM Page 4
Flowcasting: Chapter 2
period -- typically one full year to capture the entire business cycle.
It calculates dependent demand to predict how much inventory RDCs
must ship to the stores, and when specified quantities of product
must arrive in order to meet consumer demand from several days to
weeks into the future. Flowcasting repeats this process for every sup-
ply chain node that a product will flow through on its way from the
factory floor to the retail store shelf. Figure 2.1 shows the power of
this approach within the first two nodes of a retail supply chain. The
detailed logic and mechanics of flowcasting will be discussed in later
chapters, beginning with Chapter 3.
The ability to Flowcast the inflow and outflow of products
across each node in a given retail supply chain enables the transla-
tion of information into the various languages of the key functional
areas within a retail company. For example, as shown in Figure 2.2,
planned receipts (into a store or RDC) can be converted to receiving
hours in order to plan receiving capacity. The capacity plan for
receiving can also be expressed in terms of the number of trucks that
need to be received in a given retail store or RDC, thereby trans-
forming the typical appointment system into a forward looking sys-
tem in which valid delivery dates can be stated on planned purchas-
es before purchase orders (or supplier schedules, covered in Chapter
Figure 2.1: Flow of products in and out of retail stores and DCs.
52
chapter 2 4/4/06 1:05 PM Page 5
Flowcasting: Chapter 2
Flowcasting: Chapter 2
Flowcasting: Chapter 2
55
chapter 2 4/4/06 1:05 PM Page 8
Flowcasting: Chapter 2
Flowcasting: Chapter 2
Retailers
57
chapter 2 4/4/06 1:05 PM Page 10
Flowcasting: Chapter 2
Wholesalers
Manufacturers
58
chapter 2 4/4/06 1:05 PM Page 11
Flowcasting: Chapter 2
59
chapter 2 4/4/06 1:05 PM Page 12
Flowcasting: Chapter 2
60
chapter 2 4/4/06 1:05 PM Page 13
Flowcasting: Chapter 2
egory plans are not directly connected to the systems that purchase
and replenish products (see Figure 2.8).
Top-level plans are developed, but a reorder point system orders
products when the inventory at a particular location drops to the
trigger point. If the sum of these purchases adds up to the dollar
amount on the category plans, it’s just coincidental.
A Flowcasting system creates a direct connection between top-
level plans and the execution systems that buy products. The same
direct connection is also in place with respect to the systems that are
used to make decisions about hiring full- or part-time associates,
negotiate freight rates and/or increase the fleet size, and project prof-
it and inventory levels into the future.
In a Flowcasting environment, the business planning process is
similar to that used in manufacturing operations. Flowcasting, how-
ever, adds components to both demand management and resource
planning that make it possible to link business plans with a single
time-phased forecast that starts at the retail store end.
The left column of Figure 2.9a shows the overall business plan-
ning process. First the business plan, which is developed in the cur-
rency of choice, would be agreed upon. Next, product plans at a high
level in the merchandise hierarchy or at the category level would be
developed to support the business plan. These high-level plans would
be translated into the demand side of the business; that is, what the
consumers are expected to buy. At the "atomic" level (the store/SKU
level), the plans are aggregated to confirm, or change and realign,
higher level plans.
The right column of Figure 2.9a shows the four basic compo-
nents of demand management that Flowcasting integrates. (These
components, which will be described in detail in Chapters 3 through
5, enable effective demand management in a retail setting.)
61
chapter 2 4/4/06 1:05 PM Page 14
Flowcasting: Chapter 2
62
chapter 2 4/4/06 1:05 PM Page 15
Flowcasting: Chapter 2
63
chapter 2 4/4/06 1:05 PM Page 16
Flowcasting: Chapter 2
Flowcasting: Chapter 2
65
chapter 2 4/4/06 1:05 PM Page 18
Flowcasting: Chapter 2
Retailer data will flow daily from their repository into the
Flowcasting systems, which will contain distribution patterns (facto-
ry to MDC to RDC to store, for example) for every product found on
retail store shelves. Flowcasting will use the distribution patterns to
model the total product flow from factories to store shelves, thus
serving as a bridge between the retailer and the wholesaler or manu-
facturer’s ERP system. Figure 2.12 offers a preview of the information
flow.
66
chapter 2 4/4/06 1:05 PM Page 19
Flowcasting: Chapter 2
67
chapter 2 4/4/06 1:05 PM Page 20
Flowcasting: Chapter 2
Summary
In this chapter, we demonstrated the power of Flowcasting, a time-
phased system for planning the flow of product throughout the entire
retail supply chain. Key points include the following:
68
chapter 2 4/4/06 1:05 PM Page 21
Flowcasting
Section 2:
Flowcasting the Retail
Supply Chain:
From Store to Factory
69
chapter 2 4/4/06 1:05 PM Page 22
Flowcasting
70
chapter 3 4/4/06 1:07 PM Page 1
Flowcasting: Chapter 3
C H A P T E R 3
➫
I n the previous chapters we introduced a revolutionary concept:
forecasting can be done at the retail store level, and the results of
a store-level forecast can be used to drive the entire supply chain in
a time-phased manner. The results of such Flowcasting are impres-
sive, and can include massive lead time reductions (70 percent or
more for some hard lines), a doubling of inventory turns, and major
reductions (30 to 50 percent) in inventory investment. And these
benefits accrue while improving customer service levels to as high as
99 percent. Because Flowcasting is a completely different approach,
the "service/inventory tradeoff" of old no longer applies. Simply put,
there can be major improvements in both.
In the next three chapters, we’ll take a closer look at how the
numbers all "foot" – how the bottom line numbers of the retail store
forecast become the top line inputs to the DC forecasts, and how the
bottom line DC forecasts become inputs to forecasts at the manufac-
turing plants. This chapter focuses on where the forecasting all starts
-- the retail store. Before we delve into the specifics of forecasting at
the retail store, it’s important to understand how the fundamental
nature of operational forecasting changes in a Flowcasting environ-
ment. While the basic act of forecasting remains the same – using
current data and history to predict the future based on patterns – in
71
chapter 3 4/4/06 1:07 PM Page 2
Flowcasting: Chapter 3
In a traditional retail supply chain, each partner has its own invento-
ry, lead-time offsets, policies, and constraints. As a result, everybody
spends a great deal of time and effort trying to forecast the demands
of the immediate customers. This leaves little time to really think
about the end consumers, because the link to them is indirect at best.
As much as a manufacturer would like to stay on top of store-level
demand for their products in real time, the fact of the matter is that
the orders that will fulfill consumer demand in a few weeks need to
72
chapter 3 4/4/06 1:07 PM Page 3
Flowcasting: Chapter 3
be shipped to the DCs today -- that’s the split loyalty. The manufac-
turer is forced to try to forecast the needs of its DCs and its customers
DCs explicitly, just to keep the supply chain running.
By contrast, in a Flowcasting environment, all of the forecast-
ing focus is squarely on the end consumer. By modeling the "chain
reaction" of demand from the store shelf back to the factory floor, it’s
no longer necessary to forecast the needs of the next supply chain
partner/customer. The reason for this is that the visibility afforded by
a Flowcasting process allows us to answer the question "Who is the
customer?" separately from "Where to ship?" (see Figure 3.2).
73
chapter 3 4/4/06 1:07 PM Page 4
Flowcasting: Chapter 3
Figure 3.3: Some of the forecasting activities that can be eliminated by Flowcasting.
Flowcasting: Chapter 3
75
chapter 3 4/4/06 1:07 PM Page 6
Flowcasting: Chapter 3
Flowcasting: Chapter 3
• Daily POS
• Daily store and DC on hand balances and in transits
• Stores’ and DCs’ replenishment lead-times
• Minimum store shelf displays and DC safety stock quantities
• Minimum store and DC ordering quantities
• Shipping and receiving schedules
Daily POS
Most retailers today use barcode scanners to track daily sales by item.
Ideally, an historical archive of two to three years’ worth of scan data
should be available as inputs to the Flowcasting process. The data
should be tracked by product and by store, in daily or weekly time
periods. Also, each item would be scanned discretely by size, color,
flavor, and other key replenishment attributes.
Flowcasting: Chapter 3
the source, but have not yet been received into stock at the destina-
tion.
Replenishment Lead-Times
For each product, source location, and destination location, the
repository should store the elapsed time from the time an order is
received at the source until the time the product is received at the
destination. For example, if a retail store can get a delivery 3 days
after placing an order on its DC, then the lead-time between the store
and DC is 3 days. Similarly, if the DC can get a delivery 10 days after
placing an order with a supplier, then that is the lead-time between
these points.
Flowcasting: Chapter 3
Flowcasting: Chapter 3
4 Many forecasting packages of this type exist on the market. While they can vary
in complexity and user functionality, they all have some method of performing
these basic calculations.
80
chapter 3 4/4/06 1:07 PM Page 11
Flowcasting: Chapter 3
we are working solely with pure end consumer demand at the store
shelf, there will be specific forecasting rules and guidelines that will
apply (see Appendix D for more details).
Flowcasting: Chapter 3
2. Review and analyze the POS sales results from past promo-
tions for the item.
3. Develop new promotional consumer forecasts for the item,
ideally in collaboration with suppliers and a sampling of
store managers.
4. Allocate the forecast to participating stores, based on each
store’s volume contribution by item or category.
82
chapter 3 4/4/06 1:07 PM Page 13
Flowcasting: Chapter 3
83
chapter 3 4/4/06 1:07 PM Page 14
Flowcasting: Chapter 3
84
chapter 3 4/4/06 1:07 PM Page 15
Flowcasting: Chapter 3
extended supply chain -- not only for replenishment purposes, but for
capacity planning, resource scheduling, and budgeting as well.
Flowcasting: Chapter 3
86
chapter 3 4/4/06 1:07 PM Page 17
Flowcasting: Chapter 3
In Figure 3.13, you can see that our current on hand balance is
18 units. On day 1, we are forecasting that we will sell 1 unit, leaving
us with a Projected On Hand of 17 units at the end of that day.
Our forecast is to sell an additional 2 units on day 2, but we also
have an in transit quantity of 12 units that’s expected to arrive on
that day from RDC1. Therefore, our projected on hand at the end of
day 2 is 17 – 2 + 12 = 27 units, and so on. Using this logic, we can see
87
chapter 3 4/4/06 1:07 PM Page 18
Flowcasting: Chapter 3
that our projected on hand will drop below our minimum display
quantity on day 7, if more stock does not arrive on, or before, this day.
So now we also know than on, or before, day 7, we will need to sched-
ule a Planned Arrival of stock into store 108.
88
chapter 3 4/4/06 1:07 PM Page 19
Flowcasting: Chapter 3
89
chapter 3 4/4/06 1:07 PM Page 20
Flowcasting: Chapter 3
Flowcasting: Chapter 3
tional 28 units of sales, which will put our projected on hand balance
at 14, as illustrated in Figure 3.16.
As Figure 3.16 shows, the arrival on day 8 needs to be at least
34 units, in order to ensure our projected on hand is at least 48 at the
end of day 9 (see Figure 3.17).
Flowcasting: Chapter 3
6 Once the replenishment lead time is reached, there is only enough time left to
get it on the truck at RDC1 and transport it to the store. At this point, the ship-
ment is considered to be en route to the store, so it’s too late to change the dates
or quantities.
92
chapter 3 4/4/06 1:07 PM Page 23
Flowcasting: Chapter 3
Continuous Re-Planning
Of course, not all plans will happen exactly as expected. On any given
day, you may sell more than your forecast or you may sell less – and
if you get it exactly right, it’s probably a coincidence. That’s why, in
order to Flowcast properly, the foundational data needs to be
refreshed daily. On a net change basis7, if any of the foundational data
has changed for the item/store, then the rest of the planning steps
will be executed again, resulting in a plan that not only stretches out
an entire year, but is constantly being kept up to date with the most
recent information.
Recall, for example, the plan we just created for Product
#01234567 in store 108 (see Figure 3.19). Suppose that on day 1,
instead of selling the 1 unit that was forecast, you actually sold 5. In
other words, you oversold your forecast by 4 units. Here’s what would
happen: after day 1 had passed, you would begin a new planning cycle
(day 2). Between day 1 and day 2, your Current On Hand Balance
would have dropped from 18 units to 13 units. Assuming that the
forecast for the next 52 weeks doesn’t change overnight (typically the
forecast would change weekly if required), the Flowcasting logic
would completely refresh the plan as shown in Figure 3.20):
Because the forecast was oversold on day 1, the impact of this
change automatically updates the entire 52-week planning horizon,
starting now from week 2. In this particular example, the planned
arrival on day 8 increased from 36 units to 48 units as a result.
7 Net change planning is what makes huge retail data volumes manageable.
The time-phased plans will only change if one of the input variables changes.
Therefore, it’s only necessary to re-plan product/locations that have experienced a
change from one day to the next.
93
chapter 3 4/4/06 1:07 PM Page 24
Flowcasting: Chapter 3
Summary
We have illustrated how Demand Management and Resource
Planning converge at the retail store level in the supply chain, and
have discussed some of the key inputs required to make Flowcasting
work. We also described a high-level forecasting process used to pre-
dict consumer demand at the store level. We demonstrated how,
using this forecast, on hand balances, planned arrivals, and planned
orders can be time phased into the future. Here are the key points to
remember:
94
chapter 3 4/4/06 1:07 PM Page 25
Flowcasting: Chapter 3
95
chapter 3 4/4/06 1:07 PM Page 26
Flowcasting
96
chapter 4 4/3/06 4:02 PM Page 1
Flowcasting: Chapter 4
C h a p t e r 4
➫
T o paraphrase the old saw, "no RDC is an island." The RDC’s activ-
ities are wholly dependent on the needs of the retail stores.
Without stores, there would be no need for RDCs to exist. Yet today,
most retailers today have one system for replenishing their stores
and another for replenishing their RDCs. Flowcasting reconnects
the stores and RDCs, as they should be connected. This means more
than drawing from a centralized data repository; it means that the
final replenishment plans from the stores actually become the top-
line inputs for the RDCs. In this way, the forecasts cascade through
the first two levels of the supply chain, starting with the only point of
true demand: the store shelves.
In this chapter, we’ll extend the logic described in Chapter 3
from the store level to the RDC. As in the examples used in Chapter
3, we’ll focus on an individual item. Remember, it doesn’t matter
whether we’re forecasting one SKU or 10,000 SKUs; the logic
remains the same. The Flowcasting process crunches the numbers
and makes the complexity manageable.
97
chapter 4 4/3/06 4:02 PM Page 2
Flowcasting: Chapter 4
Figure 4.1: A 52-week ordering plan for product 01234567 in store 108.
If store 108 was the only retail sales venue in the supply chain,
life would be simple. But, of course, supply chains are dynamic enti-
ties consisting of numerous nodes. For the sake of illustration, we’ll
expand the model (see Figure 4.2) to include two stores to demon-
strate how Flowcasting can tightly integrate retail stores and RDCs
within the supply chain.
In Chapter 3, we determined the replenishment needs of store
108 (Figure 4.1). But to compute RDC1’s shipping requirements,
we’ll also need a time-phased plan for another retail node in the sup-
98
chapter 4 4/3/06 4:02 PM Page 3
Flowcasting: Chapter 4
Figure 4.2: Using Flowcasting to integrate retail stores and retail DC.
Figure 4.3: A 52-week ordering plan for product 01234567 in store 602.
99
chapter 4 4/3/06 4:02 PM Page 4
Flowcasting: Chapter 4
Now that we’ve calculated the planned orders for the next 52
weeks for stores 108 and 602, it’s very easy to determine the demand
that RDC1 will need to satisfy over that time period. All we need is
the following information:
100
chapter 4 4/3/06 4:02 PM Page 5
Flowcasting: Chapter 4
The total store planned orders line now becomes the dependent
demand that RDC1 must satisfy.
Figure 4.5: Dependent demand and basic replenishment data for RDC1.
In Figure 4.5:
101
chapter 4 4/3/06 4:02 PM Page 6
Flowcasting: Chapter 4
102
chapter 4 4/3/06 4:02 PM Page 7
Flowcasting: Chapter 4
will need to be scheduled for day 5, the first available date prior to
when the arrival is actually needed. Figure 4.7 below summarizes
this simple logic:
Figure 4.7: Scheduling the first arrival at RDC1 to maintain projected on hand
above safety stock.
By calculating and tracking the projected on hand at RDC1, we
have the ability to continue planning forward for as far out as we have
Store Planned Orders. Figure 4.8 below illustrates a 52-week arrival
based plan for RDC1:
103
chapter 4 4/3/06 4:02 PM Page 8
Flowcasting: Chapter 4
Figure 4.9: A 52 week ordering and arrival based replenishment plan at RDC1.
As Figure 4.9 shows, on day 1, RDC1 will need to order 144 units
from MDC1 to ensure that it arrives on day 5, and so on through the
year.
We now have a complete 52-week plan for RDC1, including
planned store demand, projected on hand balances, planned arrivals
into stock, and planned ordering activity. All three were determined
without having to forecast requirements at RDC1. Put another way,
the item/store level forecast of consumer demand that we created in
Chapter 3 is now directly driving two full echelons of the supply
chain.
Whether you use a Flowcasting business process or not, there is
a chain reaction of demand from consumers through to the factories.
Consumer buying behavior directly impacts store replenishment
which, in turn directly impacts RDC replenishment. By modeling
this reality explicitly, not only does the amount of energy required for
forecasting decrease, but the plans will be far more accurate as well.
104
chapter 4 4/3/06 4:02 PM Page 9
Flowcasting: Chapter 4
105
chapter 4 4/3/06 4:02 PM Page 10
Flowcasting: Chapter 4
Figure 4.11: A network change resulting in store 760 being replenished from RDC1.
106
chapter 4 4/3/06 4:02 PM Page 11
Flowcasting: Chapter 4
Flowcasting: Chapter 4
Figure 4.13: Revised replenishment plan for RDC1 using new store
planned orders stream.
Flowcasting: Chapter 4
Supplier Scheduling
The output of the Flowcasting process at RDC1 (and any other RDCs)
is a projection of what suppliers must sell and ship to the retailer, 52
weeks into the future (i.e., a stream of Planned Orders). By sharing
the Planned Orders with wholesalers and manufacturers, the retailer
can eliminate the need for these suppliers to forecast what the retail-
er is going to buy – information about demand is disseminated and
refreshed daily as conditions change in retail stores and RDCs.
Flowcasting also not only reduces forecasting efforts, but it pro-
vides vastly superior forecast quality at the downstream echelons.
Less effort is required because the entire supply chain is planned with
the consumer demand forecast at the store shelf. The forecast quali-
ty is superior, because every constraint and inventory pool upstream
from the consumer is considered in the projection -- there’s no need
to guess the demand at each echelon of the supply chain.
The sharing of planned orders is commonly known in manu-
facturing and distribution circles as Supplier Scheduling, and will be
discussed in more detail in Chapter 5. Even without further discus-
sion, it should be obvious that supplier scheduling represents a radi-
cal departure from the way retailers, wholesale distributors, and
manufacturers have traditionally conducted business.
Summary
In this chapter, we extended the Flowcasting business process from
the retail store to the RDC echelon in the supply chain. We demon-
109
chapter 4 4/3/06 4:02 PM Page 14
Flowcasting: Chapter 4
110
chapter 4 4/3/06 4:02 PM Page 15
Flowcasting: Chapter 4
111
chapter 4 4/3/06 4:02 PM Page 16
Flowcasting
112
chapter 5 4/3/06 4:05 PM Page 1
Flowcasting: Chapter 5
C h a p t e r 5
➫
S o far, we’ve seen how Flowcasting links retail stores and RDCs
through a single store-level forecast. The key is dependent
demand, which specifies how much product must be shipped and
when is the product needed, taking into account all relevant con-
straints. That information is "actionable" at every node in the retail
supply chain, which means that the dependent demand can be used
directly by the next partner upstream, with no translation or inter-
pretation necessary.
In this chapter, we’ll describe how dependent demand can
extend beyond the retailer’s organization (stores and RDCs) and
transform business relationships and planning processes with whole-
sale distributors, manufacturers and raw material suppliers. It will
also describe how manufacturers that utilize ERP systems can inter-
nalize Flowcast-generated dependent demand provided by key cus-
tomers. If all this seems like a tall order, bear in mind that
Flowcasting reduces uncertainty between nodes in the supply chain.
And the more you can reduce uncertainty, the less the need for indi-
vidual nodes to guess (forecast) what’s needed today, tomorrow, and
a year out.
113
chapter 5 4/3/06 4:05 PM Page 2
Flowcasting: Chapter 5
The completed product flow plan for RDC1 based on this net-
work is shown in Figure 5.2.
Flowcasting: Chapter 5
But as we can see from Figure 5.1, a planned order stream also
needs to be created for RDC2 so that MDC1 can have complete visi-
bility into its dependent demand. To do so, we need to create a
Flowcasting plan for RDC2 in addition to the one for RDC1. First, we
collect and sum the planned order streams from the stores that are
serviced by RDC2 (see Figure 5.3):
Flowcasting: Chapter 5
our example RDC1 and RDC2 are the only two customers of MDC1 -
- see Figure 5.5):
116
chapter 5 4/3/06 4:05 PM Page 5
Flowcasting: Chapter 5
117
chapter 5 4/3/06 4:05 PM Page 6
Flowcasting: Chapter 5
of planned orders to the next node in the retail supply chain, the fac-
tory instead takes its dependent demand from MDC1 and produces a
Recommended9 Master Production Schedule (MPS)10.
The now familiar Flowcasting method of planning supply to
meet demand is no different for a factory than it was in the retail
stores or distribution centers discussed in Chapters 3 and 4. The only
difference is a change in terminology, specifically:
• "Manufacturing Lot Size" represents the amount of product
that is made in a single production run and is used instead
of "Minimum DC Ordering Quantity."
• "Manufacturing Lead Time" represents the amount of time
needed to produce a single lot and is used instead of
"Replenishment Lead Time."
• "Work in Process" represents product that has begun a pro-
duction run but not yet finished. It is used in place of "In
Transits."
• "MPS Available" represents when finished goods are needed
to be available off the production line and is used instead of
"Planned Arrivals."
• "MPS Start" represents when production needs to begin in
order to have finished goods available by the MPS Available
date and is used instead of "Planned Orders."
Flowcasting: Chapter 5
materials and capacities are or can be made available). With the MPS
stated and agreed upon within a given planning horizon, the pur-
chasing department within the factory knows when production runs
for the 01234567 Deluxe Widget are planned to start. By taking this
projection and multiplying it through the bill of material (BOM) for
the Deluxe Widget, the factory can plan its purchases of the raw
materials that will be necessary to support the master production
schedule .
For example, suppose that a finished 01234567 Deluxe Widget
is comprised of the following components:
• 6 oz. blue plastic pellets
• 1.5 ft. nylon tubing
• 3 metal washers
• 1 packages boxes
With the quantities and timing provided by the "MPS Start" line
as shown in Figure 5.8 and the conversion table provided by the
Figure 5.8: A 52-week recommended master production schedule (MPS) at the factory.
119
chapter 5 4/3/06 4:05 PM Page 8
Flowcasting: Chapter 5
Figure 5.9: Using the MPS and BOM to drive dependent demand for
raw material components.
BOM, we now know when raw materials and packaging supplies will
be needed by the factory to produce the Deluxe Widgets11 (see Figure
5.9).
We have now closed the loop by creating a 52-week plan of
demand, supply, and inventory for every retail store, distribution cen-
ter, and factory in the supply chain. And remember, all of these plans
were generated without any forecasting beyond the forecast we cre-
ated at store level in Chapter 3.
While everything that has been described from the beginning of
Chapter 3 until now may seem intuitive, it is assumed that the com-
munication links between nodes have already been firmly estab-
lished. Between retail stores and RDCs, communication is relatively
easy to set up, since all of these nodes are generally a part of the same
company. Within the retailer’s organization a single, self-contained
system would be used to plan both the stores and the RDCs simulta-
neously.
11 In a factory that produces several products sharing some (or all) of their raw
materials or component parts in different proportions, the MPS will need to be
exploded through all bills of material before a purchasing plan can be calculated.
120
chapter 5 4/3/06 4:05 PM Page 9
Flowcasting: Chapter 5
Supplier Scheduling
Without the Flowcasting process, the manufacturer must inde-
pendently determine the items and quantities it must ship out to
meet the retailer’s demands. Specifically, it must figure out which
Flowcasting: Chapter 5
days it must ship on and the location is must ship to, several weeks
or even months into the future. This is done today at great time and
expense through key account sales forecasting and order booking.
But as we’ve already seen, planned order streams can be effort-
lessly calculated at any level in the supply chain with a Flowcasting
business process. And no matter where you look in the supply chain,
planned orders always represent the same thing: which items need to
ship, the quantities needed, and the specific ship dates and locations,
52 weeks into the future. Flowcasting answers all of these questions
-- what, where, how much, and when, at the required level of detail.
And the information produced at one echelon in the supply chain
requires no additional interpretation by the next.
In a Flowcasting world, the demand requirements on the sup-
plier have already been scheduled within the retailer’s planning
process (hence, the term "supplier scheduling"). The ramifications of
having this information on tap are highly significant for all suppliers:
122
chapter 5 4/3/06 4:05 PM Page 11
Flowcasting: Chapter 5
Flowcasting: Chapter 5
124
chapter 5 4/3/06 4:05 PM Page 13
Flowcasting: Chapter 5
125
chapter 5 4/3/06 4:05 PM Page 14
Flowcasting: Chapter 5
Flowcasting: Chapter 5
127
chapter 5 4/3/06 4:05 PM Page 16
Flowcasting: Chapter 5
Flowcasting: Chapter 5
Our Promised Orders (that is, supply that has been protected
for Retailer A and Retailer B) between now and day 4 is 432 units (288
on day 2 and 144 on day 3). The difference between the Planned
Supply and Promised Orders over the next 3 days represents the
Available To Promise: 1226 – 432 = 794.
Put another way, if a customer other than Retailer A or Retailer
B wants product from MDC1 over the next 3 days, MDC1 can only sell
794 units to that customer, even though they will have 1226 units in
supply.
Because the Promised Orders and Planned Supply are calculat-
ed over a long time horizon in a Flowcasting environment, the ATP
calculation can be extended as far out as is needed. For example, on
day 4, additional supply of 576 units is planned, and the Promised
Orders are 288 units. The ATP in the previous period was 794 units.
So the cumulative ATP on day 4 is 794 + 576 – 288 = 1082, and so on.
The key point is that a Flowcasting relationship between part-
ners requires a high level of trust and co-operation to make it work.
If retailers make the necessary investments to provide schedules to
suppliers, they will expect a high level of service with no excuses from
suppliers. Conversely, if suppliers are to reserve inventory without a
firm purchase contract locked in, they expect retailers to follow their
schedules.
129
chapter 5 4/3/06 4:05 PM Page 18
Flowcasting: Chapter 5
130
chapter 5 4/3/06 4:05 PM Page 19
Flowcasting: Chapter 5
Summary
In this chapter, we "closed the loop" by continuing the same
Flowcasting process that began in Chapter 3 beyond the walls of the
retail organization to their upstream supply partners. We demon-
strated that the inventory planning problem can be universally solved
with the same planning method, whether the operation is a retail
store, a distribution center or a factory. Here are the key points to
remember:
131
chapter 5 4/3/06 4:05 PM Page 20
Flowcasting: Chapter 5
This concludes Section 2 of this book. In the third and final sec-
tion, the proverbial rubber will "hit the road." The chapters in
Section 3 show how Flowcasting can be used to solve some of retail's
most common (and most frustrating) challenges: managing promo-
tions, product introductions and discontinuations, seasonal prod-
ucts, slow moving items, and operational and financial planning.
Finally, we present a high-level plan for implementing Flowcasting in
today's networked retail supply chains.
132