MBA Bullwhip Effect Concept Card Template
Bullwhip effect card: four causes, variance and CV ratios, Chen et al. formula, multi-stage sharing, step response, batching data, remedies, examples, self-test
उपयोग कैसे करें: Use it in a supply chain elective or when a supplier complains about erratic orders. Fill matched demand and order data for one stage first, then measure the ratio and name the cause before the remedy. The main pitfall is treating every swing as a forecasting problem when batching or promotions cause it.
प्रीव्यू
Bullwhip Effect Concept Card: [Your course or supply chain]
A concept card for the supply chain elective: why order variability grows as orders move upstream from the shelf to the factory, how to measure it, how much of it a forecasting and ordering rule creates on its own, and which remedies remove which cause. It builds on the inventory models of the operations core (reorder point, safety stock, order-up-to levels): read mba/mba-inventory-card first, because this card uses its notation and does not re-teach it. It is for MBA students taking a supply chain elective and for managers in retail, distribution, manufacturing and healthcare supply who see erratic orders from customers or send them to suppliers. One example is fully solved, one is half solved and one is left for you, and the self-test answers sit in a separate key. Source basis: Forrester (1961) for the dynamics, Sterman (1989) for the behavioural evidence, Lee, Padmanabhan and Whang (1997) for the four causes, and Chen, Drezner, Ryan and Simchi-Levi (2000) for the formula, all written up in original words with fictional data (Northfield Outdoor Co. and Tallow Creek Medical Center are invented organisations). Replace every [bracketed] value and every row marked Example.
Document control
| Field | Value |
|---|---|
| Course or project | [Supply chain elective, coordination sessions / client project] |
| Learner or analyst | [Your name] |
| Chain and stage analysed | [Northfield stores, Northfield distribution centre, headlamp supplier (fictional) / your chain] |
| Demand data | [Point-of-sale or consumption data, period length, YYYY-MM-DD to YYYY-MM-DD] |
| Order data | [Purchase orders placed by the stage, same period length and dates] |
| Tool | [Excel / Google Sheets / simulation tool] |
| Reviewed by | [Study group / tutor / mentor] |
| Last updated | YYYY-MM-DD |
| Version | [0.1] |
When to use it
One-sentence rule: use this card whenever the orders a stage receives vary more than the demand of the final customer, and you have to decide whether the cause lies in forecasting, lead times, batching, rationing or pricing.
| Situation | What this card gives you |
|---|---|
| A supplier complains about erratic orders while store sales look stable | A measurement (variance or CV ratio) and a list of candidate causes |
| A planning team wants to change its forecasting window or review period | The size of the amplification the change creates or removes |
| A retailer and a manufacturer negotiate data sharing or vendor-managed inventory | What sharing end-customer data is worth, stage by stage |
| A promotion calendar or quantity discount is being redesigned | The forward-buying mechanism and its cost upstream |
| A shortage is coming and customers start to over-order | The rationing game and allocation rules that defuse it |
| A course case or the beer distribution game debrief | The theory behind what the teams just experienced |
| Use when | Do not use alone when |
|---|---|
| You have matched demand and order data for the same stage and period | You only have orders: you cannot separate demand swings from amplification |
| Demand is roughly stationary over the window you measure | Demand has strong seasonality: deseasonalise first or compare like periods |
| The question is about variability and the inventory and capacity it costs | The question is about the average level of inventory only (see mba/mba-inventory-card) |
| Stages forecast and order on their own | The chain is already run by one planner on shared data (the effect is smaller, but still check lead times) |
The idea in plain language
Picture a chain of four stages: a store, the retailer's distribution centre, a wholesaler and a factory. Shoppers buy roughly the same number of headlamps every week. Yet the factory sees orders that jump from very large to almost nothing. That amplification of order variability as orders travel upstream is the bullwhip effect: a small flick at the handle becomes a large swing at the tip.
Forrester (1961) showed with simulation models that delays and feedback in a production-distribution system create such swings. Sterman (1989) ran the beer distribution game with managers and students and found that players under-weight the orders already in the pipeline: they keep ordering when the shelf is low even though shipments are on the way, and the overshoot follows. Lee, Padmanabhan and Whang (1997) then showed that the effect also arises when every manager acts rationally on the information each one has, and named four causes:
- Demand signal processing. Each stage forecasts from the orders it receives, not from final demand, and resets its order-up-to level every period. A small rise in demand raises the forecast, and the stage orders the demand plus the increase in its target stock. The longer the lead time, the bigger the adjustment.
- Order batching. Stages order in full trucks, pallets or at month end because each order has a fixed cost (the EOQ logic in mba/mba-inventory-card). Steady demand becomes lumpy orders.
- Price variations. Promotions and quantity discounts make buyers forward-buy: they buy far more than they need when the price is low and nothing afterwards.
- The rationing game. When supply is short and the supplier allocates in proportion to orders, customers inflate their orders to get a bigger share, then cancel when the shortage ends. The supplier reads the phantom orders as demand.
Behaviour adds a fifth driver on top of the four: the under-weighting of the supply line that Sterman documented. It is not a separate cause in the 1997 classification, but it is why the effect in a classroom game is larger than any formula predicts.
The cost is real: upstream stages hold more safety stock, build capacity for peaks that never come from final demand, pay overtime and idle time in turn, and deliver worse service because they plan on noise.
Formulas and notation
Measuring the effect. For one stage, compare the variance of the orders it places with the variance of the demand it faces, over the same periods:
means the stage amplifies. When the mean of orders and the mean of demand differ over the window (a growing business, a stock build), use the coefficient-of-variation ratio .
The amplification created by forecasting and lead times (Chen, Drezner, Ryan and Simchi-Levi 2000). Demand is independent from period to period. At the end of each period the stage forecasts mean demand as the moving average of the last observations, sets an order-up-to level equal to periods of forecast demand, and orders what it sold plus the change in that level:
With a safety-stock term based on an estimated standard deviation, Chen et al. (2000) show this expression is a lower bound, so real amplification is at least this large. For demand that is correlated over time (an AR(1) process with coefficient ) the bound becomes .
Several stages (same paper). If every stage with lead time forecasts from the orders it receives (decentralised), the amplification multiplies. If every stage forecasts from final customer demand (centralised information), the lead times add inside one expression:
Sharing data reduces the effect but does not remove it: lead times still amplify. Both expressions are lower bounds. In the centralised case the bound is exact when no safety-stock term is estimated. The decentralised product is a strict lower bound even then, because the orders an upstream stage receives are correlated over time; the true amplification without shared data is larger, so the value of sharing is larger than the product suggests (Worked example A3).
The cost upstream. The supplier sizes its safety stock on the variability it sees (mba/mba-inventory-card):
| Symbol | Meaning | Unit |
|---|---|---|
| , , | Demand the stage faces in period , its mean and standard deviation | units per period |
| , , | Order the stage places at the end of period , its mean and standard deviation | units per period |
| , | Bullwhip ratio (variance ratio) and coefficient-of-variation ratio | none |
| Number of periods in the moving-average forecast | periods | |
| , | Replenishment lead time of the stage, of stage | periods |
| , | Forecast of mean demand, order-up-to level | units per period, units |
| Correlation of demand with demand one period earlier | none | |
| , CSL, | Supplier lead time, cycle service level, its standard normal quantile | periods, %, none |
Conventions. Chen et al. place an order at the end of period that arrives periods later; some textbooks count the review period inside . Check your course convention: it changes the numbers, not the logic.
Excel equivalents. Variance ratio: =VAR.S(orders)/VAR.S(demand). CV ratio:
=(STDEV.S(orders)/AVERAGE(orders))/(STDEV.S(demand)/AVERAGE(demand)). Formula: =1+2*L/p+2*L^2/p^2.
Assumptions and limits
| Assumption | What breaks it | What to do |
|---|---|---|
| Demand independent from period to period | Trends, seasonality, autocorrelation | Deseasonalise, or use the AR(1) form; forecast with a method that fits (academic/stats-time-series-arima) |
| Moving-average forecast | Exponential smoothing or a planner's judgement | The direction is the same; Chen, Ryan and Simchi-Levi (2000) treat exponential smoothing; simulate your own rule |
| Order every period, any quantity | Truckloads, pallets, minimum order quantities | Measure batching separately from data (Worked example A5) |
| Negative orders allowed (returns) | Real orders cannot be negative | Negative orders rarely arise when swings are small; when they are large, real orders are cut off at zero, which changes the variance, so simulate your own rule |
| Fixed, known lead time | Lead time varies with congestion | Variable lead times raise both safety stock and amplification |
| Stages act on their own information | Shared data, joint planning | Use the centralised form; it is a lower bound, not zero |
| Rational, consistent ordering | Supply-line under-weighting, panic, gaming | Expect more than the formula; the beer game shows by how much |
The formula is a lower bound under the stated policy. It explains why a longer lead time and a shorter forecasting window amplify, and why sharing demand data helps. It does not capture batching, promotions or rationing, which you measure directly.
How managers use it
| Cause | What managers change | Example practice | Who must agree |
|---|---|---|---|
| Demand signal processing | Share point-of-sale or consumption data; plan from end demand; shorten lead times; smooth the order-up-to update | Collaborative planning, forecasting and replenishment (CPFR); vendor-managed inventory (VMI); continuous replenishment | Retailer and supplier, IT on both sides |
| Order batching | Lower the fixed cost per order; order smaller and more often; mixed-product trucks; third-party logistics consolidation; stagger customers' order days | Electronic ordering, milk runs, consolidated loads | Logistics, procurement, the carrier |
| Price variations | Stable pricing (everyday low price), promotions paid on sell-through rather than on sell-in, limits on forward-buy quantities | Pay-for-performance trade promotions, scan-based trading | Sales, marketing, key accounts |
| Rationing game | Allocate scarce supply on past sales, not on current orders; restrict cancellations; share capacity information | Turn-and-earn allocation, firm-order windows | Sales, supply planning, customers |
| Supply-line under-weighting (behavioural) | Show orders in transit on planning screens; decision rules that count the pipeline; training with the beer game | Planning dashboards with inventory position, not on-hand stock | Planners and their managers |
Finance cares because amplified orders cost working capital and capacity upstream; the supplier usually prices that cost into its offer. The Cachon and Fisher (2000) analysis of shared information is a useful caution: in their model, faster and cheaper order processing and smaller batches were worth more than the information itself, so test which remedy pays before you sign a data-sharing programme.
Diagnosing the cause
Start with data, then look for the pattern each cause leaves in the order history: steps in orders after demand changes (signal processing), regular spikes and zeros (batching), spikes before price changes (promotions) and spikes during shortages followed by cancellations (rationing).
Worked example A (fully solved): Northfield headlamp chain
Situation (Example, fictional). Northfield Outdoor Co. sells the Trailhead 400 headlamp in its stores and online. Weekly customer demand is independent from week to week, with mean = 500 and standard deviation = 80 units. The Northfield distribution centre (DC) forecasts with a 4-week moving average ( = 4) and its supplier delivers in = 2 weeks. The supplier's own factory plans components with a 4-week moving average of the orders it receives and a 3-week lead time.
A1. One stage.
| Quantity | Result | Excel |
|---|---|---|
| Variance ratio at the DC | 2.5000 | =1+2*2/4+2*2^2/4^2 |
| SD of DC orders | 126.49 units | =80*SQRT(2.5) |
| CV of demand | 0.1600 | =80/500 |
| CV of DC orders | 0.2530 | =126.49/500 |
The DC does nothing wrong: it forecasts sensibly and orders up to two weeks of forecast demand. Yet the supplier sees orders whose variance is 2.5 times that of customer demand.
A2. How the forecasting window and the lead time drive it. Variance ratio for each pair
(=1+2*L/p+2*L^2/p^2):
| Forecast window (weeks) | 1 | 2 | 4 | 8 | 12 | 26 |
|---|---|---|---|---|---|---|
| = 2 weeks | 13.0000 | 5.0000 | 2.5000 | 1.6250 | 1.3889 | 1.1657 |
| SD of orders at = 2 | 288.44 | 178.89 | 126.49 | 101.98 | 94.28 | 86.37 |
| = 4 weeks | 41.0000 | 13.0000 | 5.0000 | 2.5000 | 1.8889 | 1.3550 |
Two lessons. A longer forecasting window smooths the forecast and damps the bullwhip, at the cost of reacting more slowly to real changes in demand. And the ratio depends only on : doubling the lead time is undone by doubling the window, which is why cutting lead times is such a powerful remedy.
A3. Two stages: what sharing demand data is worth.
| Quantity | Result | Excel |
|---|---|---|
| Factory stage alone ( = 3, = 4) | 3.6250 | =1+2*3/4+2*3^2/4^2 |
| Decentralised: factory forecasts from DC orders (lower bound) | 9.0625 (SD 240.83 units) | =2.5*3.625 and =80*SQRT(9.0625) |
| Decentralised, exact for this order rule (no safety-stock term) | 11.0313 (SD 265.71 units) | =2.625^2+2^2+0.375^2, the squared weights on , , |
| Centralised: factory forecasts from store sales, total lead time 5 | 6.6250 (SD 205.91 units) | =1+2*5/4+2*5^2/4^2 and =80*SQRT(6.625) |
Sharing point-of-sale data cuts the factory's variance ratio to 6.63: about 27% below the decentralised bound of 9.06, and about 40% below the exact 11.03 for this rule (the factory's order is once the DC rule is substituted into the factory rule). It does not bring it back to 1: the lead times still amplify. The rest of the gain has to come from shorter lead times or longer forecasting windows.
A4. A step in demand. Customer demand rises from 500 to 550 a week in week 7 and stays there. The DC follows the
rule above ( = 4, = 2); the factory follows it on the DC's orders ( = 4, = 3). Weeks before week 1 are at
500. Orders: DC =D_t+(2/4)*(D_t-D_{t-4}), factory =q_t+(3/4)*(q_t-q_{t-4}).
| Week (Example) | 1 to 6 | 7 to 10 | 11 to 14 | 15 onwards |
|---|---|---|---|---|
| Customer demand | 500 | 550 | 550 | 550 |
| DC orders to the supplier | 500.00 | 575.00 | 550.00 | 550.00 |
| Factory production orders | 500.00 | 631.25 | 531.25 | 550.00 |
A 10% rise in demand becomes a 15% jump at the DC and a 26.25% jump at the factory, followed by an undershoot to 531.25 while the factory's forecast catches up. Add batching and a second distributor and the swing becomes a production crisis. This is the pattern teams produce in the beer game.
A5. Measuring batching from data. Weekly demand at one store cluster for camp-fuel canisters and the DC's orders, which go out in full pallets of 1,200:
| Week (Example) | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Demand | 480 | 525 | 470 | 560 | 505 | 455 | 540 | 515 | 490 | 550 | 470 | 520 |
| Orders | 1,200 | 0 | 1,200 | 0 | 0 | 1,200 | 0 | 1,200 | 0 | 0 | 1,200 | 0 |
| Quantity | Result | Excel |
|---|---|---|
| Mean and SD of demand | 506.67 and 34.07 | =AVERAGE(B2:M2), =STDEV.S(B2:M2) |
| Mean and SD of orders | 500.00 and 617.91 | =AVERAGE(B3:M3), =STDEV.S(B3:M3) |
| Variance ratio | 328.98 | =VAR.S(B3:M3)/VAR.S(B2:M2) |
| CV ratio | 18.38 | =(STDEV.S(B3:M3)/AVERAGE(B3:M3))/(STDEV.S(B2:M2)/AVERAGE(B2:M2)) |
The moving-average formula would predict a ratio of a few units; the measured ratio is over 300. Almost all of it is batching. The remedy is in logistics (smaller, mixed pallets, more frequent deliveries), not in forecasting.
A6. What it costs the supplier. The supplier holds safety stock for a 95% cycle service level with a 3-week lead time and a holding cost of USD 4 per unit per year.
| Variability the supplier plans on | Safety stock | Annual holding cost | Excel |
|---|---|---|---|
| Customer demand, SD 80 (shared POS data and a pass-through order rule) | 227.92 units | USD 911.67 | =NORM.S.INV(0.95)*80*SQRT(3) |
| DC orders, SD 126.49 | 360.37 units | USD 1,441.48 | =NORM.S.INV(0.95)*126.49*SQRT(3) |
The amplified orders raise the supplier's safety stock by 132.45 units, a factor of 1.5811 (), on one item. Across thousands of items, and in the capacity the factory keeps for peaks, this is the money that funds a data-sharing or VMI programme.
Worked example B (half solved): Tallow Creek gloves
Situation (Example, fictional). Tallow Creek Medical Center's central store replenishes nitrile gloves to the wards. Ward consumption is independent from week to week with mean 400 boxes and SD 60. The central store forecasts with a 2-week moving average and orders from a distributor with a 1-week lead time. The distributor forecasts from the hospital's orders with a 2-week moving average and a 2-week lead time from the manufacturer.
- Variance ratio at the central store: = [ ] (
=1+2*1/2+2*1^2/2^2); SD of its orders = [ ] boxes (=60*SQRT([ ])). - The store moves to a 6-week moving average. New ratio = [ ]; new SD = [ ] boxes.
- Back to = 2. Distributor stage alone: ratio = [ ]. Decentralised bound at the distributor = [ ] x [ ] = [ ]; SD of distributor orders = [ ] boxes.
- If the distributor plans on ward consumption data (centralised, total lead time 3 weeks, = 2): ratio = [ ]; SD = [ ] boxes.
- Which remedy does more for the distributor here: sharing consumption data, or the longer window in step 2? Explain in two sentences, and name one clinical risk of a longer forecasting window for a critical supply.
Exercise C (unsolved): a supplier's complaint
A regional distributor tells Northfield that its weekly orders for trekking-pole tips are "impossible to plan" (Example, fictional). Northfield's store sales and its orders to the distributor for eight weeks:
| Week | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
|---|---|---|---|---|---|---|---|---|
| Store demand (units) | 310 | 290 | 335 | 300 | 280 | 320 | 305 | 295 |
| Northfield orders (units) | 600 | 0 | 300 | 600 | 0 | 300 | 600 | 0 |
- Compute the mean and SD of demand and of orders, the variance ratio and the CV ratio.
- Which of the four causes fits this pattern best? What evidence in the table supports it?
- Propose two remedies, say who in each firm must agree, and how you would re-measure success.
- Separately, for the forecasting part of Northfield's process ( = 2 weeks), what is the shortest moving-average window that keeps the variance ratio from forecasting at or below 1.5? What does Northfield give up by choosing it?
- The distributor proposes vendor-managed inventory. List three data items and two contract terms you would need before agreeing.
Connections to other cards
- mba/mba-inventory-card (core): safety stock, reorder points and the order-up-to logic this card builds on; EOQ is the source of batching.
- mba/mba-operations-guide (core): the session on supply chain coordination and the beer game.
- mba/mba-supply-chain-guide: where this card sits in the elective; contracts, risk pooling and the Northfield mini-case.
- mba/mba-network-design-card: the number and place of stocking points decides lead times, and lead times drive the amplification.
- mba/mba-sourcing-procurement-card: contract terms (minimum order quantities, discounts, allocation rules) that create or remove batching and rationing.
- mba/mba-supply-chain-resilience-card: shortages trigger the rationing game; resilience planning should include allocation rules.
- mba/mba-pricing-card and mba/mba-revenue-management-card: promotions and price changes that cause forward buying.
- academic/stats-time-series-arima: forecasting methods and autocorrelation ( in the AR(1) form).
Common mistakes and misconceptions
- Comparing orders with orders. The bullwhip ratio compares the orders a stage places with the demand it faces. A supplier comparing its own orders with its customer's orders measures only its own stage.
- Blaming irrational planners. Lee, Padmanabhan and Whang (1997) show the effect arises with rational behaviour; fix the structure (information, lead times, batching, pricing, allocation), not only the people.
- Expecting data sharing to remove the effect. Centralised information still leaves the lead-time term (Worked example A3).
- Using the formula for batching. The variance formula covers forecasting with lead times only; batching and promotions must be measured from data (Worked example A5).
- Mixing sample and population variance.
VAR.SandVAR.Pdiffer; use the same one for orders and demand. - Ignoring seasonality. A seasonal pattern in demand inflates both variances; compare deseasonalised series or like-for-like periods.
- Using the variance ratio when means differ. In a growing business or a stock build, compare coefficients of variation instead.
- Treating a longer forecasting window as free. It damps the bullwhip but reacts late to real changes, a cost in fashion and in critical supplies.
- Counting on-hand stock instead of inventory position. Orders in the pipeline must be counted, or planners re-order what is already on the way (Sterman 1989).
- Assuming the effect is always bad to the same degree. Some smoothing costs service; the goal is lower total cost across the chain, which needs a contract that shares the gains.
Self-test
- Define the bullwhip effect in one sentence and name the four causes from Lee, Padmanabhan and Whang (1997).
- A stage forecasts with a 4-period moving average and has a 1-period lead time. Compute the variance ratio.
- Same window, lead time 4 periods. Compute the ratio and explain the change.
- Two stages each with = 1 and = 4. Compute the ratio at the second stage with decentralised and with centralised information.
- Demand SD is 100 units a week. With the ratio of question 2, what is the SD of the stage's orders?
- Why does the ratio depend only on ?
- A stage's orders have SD 90 and its demand SD 30, with equal means. What is the variance ratio?
- Which cause does each remedy address? (a) Allocation on past sales. (b) Everyday low pricing. (c) Mixed-product trucks. (d) Sharing point-of-sale data.
- What behavioural finding did Sterman (1989) report from the beer distribution game?
- When should you use the CV ratio instead of the variance ratio?
- Cachon and Fisher (2000) compared the value of shared information with other improvements. What did they find?
- Interleaving: which card first? (a) A hospital asks how many vaccine doses to buy before flu season. (b) A supplier sees orders that spike every fourth week. (c) A retailer asks how many DCs it needs.
My notes and next steps
| Item | My entry |
|---|---|
| Confidence with the bullwhip effect (1 = lost, 5 = could teach it) | [ ] |
| A chain I know where orders swing more than demand, and the likely cause | [ ] |
| Questions for my study group or professor | [ ] |
| Mistakes logged in mba/mba-error-log | [Date and short description] |
| Next review date (spacing: +2 days, +1 week, +1 month) | YYYY-MM-DD |
| Next card to study | [mba/mba-network-design-card / mba/mba-sourcing-procurement-card] |
Sources and further reading
- Forrester, J. W. (1961). Industrial Dynamics. MIT Press.
- Sterman, J. D. (1989). Modeling managerial behavior: misperceptions of feedback in a dynamic decision making experiment. Management Science, 35(3), 321-339.
- Lee, H. L., Padmanabhan, V., and Whang, S. (1997). Information distortion in a supply chain: the bullwhip effect. Management Science, 43(4), 546-558.
- Lee, H. L., Padmanabhan, V., and Whang, S. (1997). The bullwhip effect in supply chains. Sloan Management Review, Spring 1997. Reprinted in IEEE Engineering Management Review (2015), 43(2), 108-117.
- Chen, F., Drezner, Z., Ryan, J. K., and Simchi-Levi, D. (2000). Quantifying the bullwhip effect in a simple supply chain: the impact of forecasting, lead times, and information. Management Science, 46(3), 436-443.
- Chen, F., Ryan, J. K., and Simchi-Levi, D. (2000). The impact of exponential smoothing forecasts on the bullwhip effect. Naval Research Logistics, 47(4), 269-286.
- Cachon, G. P., and Fisher, M. (2000). Supply chain inventory management and the value of shared information. Management Science, 46(8), 1032-1048.
- Dejonckheere, J., Disney, S. M., Lambrecht, M. R., and Towill, D. R. (2003). Measuring and avoiding the bullwhip effect: a control theoretic approach. European Journal of Operational Research, 147(3), 567-590.
- Textbooks (further reading, by name only): Simchi-Levi, Kaminsky and Simchi-Levi, Designing and Managing the Supply Chain; Chopra and Meindl, Supply Chain Management: Strategy, Planning, and Operation; Sterman, Business Dynamics: Systems Thinking and Modeling for a Complex World.
- Open resources: MIT OpenCourseWare, 15.762J Supply Chain Planning (Spring 2011), https://ocw.mit.edu/courses/15-762j-supply-chain-planning-spring-2011/, and 15.871 Introduction to System Dynamics (Fall 2013), https://ocw.mit.edu/courses/15-871-introduction-to-system-dynamics-fall-2013/.
Answer key
Worked example B. (1) Ratio 2.5000; SD 94.87 boxes (=60*SQRT(2.5)). (2) = 6: ratio 1.3889
(=1+2*1/6+2*1^2/6^2); SD 70.71 boxes. (3) Distributor alone ( = 2, = 2): ratio 5.0000. Decentralised bound: 2.5 x 5
= 12.5000; SD 212.13 boxes (=60*SQRT(12.5)). (4) Centralised, = 3, = 2: ratio 8.5000 (=1+2*3/2+2*3^2/2^2);
SD 174.93 boxes. (5) Sharing consumption data cuts the distributor's ratio from 12.5 to 8.5; the longer window at the
store alone cuts the store's ratio from 2.5 to 1.39 and, decentralised, the distributor's from 12.5 to 6.94 (1.3889 x
5). Both help; together with a longer window at the distributor they help most. Clinical risk: a long window reacts
slowly to a real surge (an outbreak), so pair it with an override rule for critical items.
Exercise C. (1) Demand: mean 304.38, SD 17.41, variance 303.125. Orders: mean 300.00, SD 277.75, variance 77,142.86.
Variance ratio 254.49 (=VAR.S(orders)/VAR.S(demand)); CV ratio 16.19. (2) Order batching: orders come only in
multiples of 300 with zero weeks in a regular three-week cycle, while demand barely moves. (3) Example remedies:
smaller order multiples or mixed cartons (logistics and the distributor's warehouse must agree); a fixed weekly
delivery slot with electronic ordering (procurement and the distributor's sales team). Re-measure the variance ratio
and the distributor's forecast error over the next 8 to 12 weeks. (4) gives = 9.66, so = 10 weeks (ratio 1.4800). Northfield reacts slowly to real changes in demand, a risk for
seasonal items. (5) Data: daily or weekly store sales by item, on-hand and in-transit stock, promotion calendar.
Terms: service level and stock ownership (who owns stock at the store until sale), limits and penalties for
overstock or stock-outs.
Self-test.
- The growth of order variability as orders move upstream. Causes: demand signal processing, order batching, price variations, rationing game.
- = 1.6250.
- = 5.0000. The order-up-to level covers four periods, so every change in the forecast is multiplied by four in the order.
- Decentralised: 1.625 x 1.625 = 2.6406 (a lower bound; the exact value for this rule is 2.8359). Centralised: total lead time 2, so 2.5000.
- = 127.48 units.
- The order adds to demand: lead time scales the adjustment and the window divides it.
- = 9.00.
- (a) Rationing game. (b) Price variations. (c) Order batching. (d) Demand signal processing.
- Players under-weighted the supply line (orders placed but not yet received), so they over-ordered and created large oscillations even though final demand changed only once.
- When the mean of orders and the mean of demand differ over the measured window, as in growth or stock building.
- In their model, shared demand information lowered costs, but faster and cheaper order processing (shorter lead times, smaller batches) lowered them more.
- (a) Newsvendor (mba/mba-inventory-card). (b) This card, batching. (c) mba/mba-network-design-card.
Revision history
| Version | Date | Author | Change summary |
|---|---|---|---|
| 0.1 | YYYY-MM-DD | [Your name] | First draft from the template |
| 0.2 | YYYY-MM-DD | [Your name] | Example: Replaced Northfield data with own order and POS data, batching measured |
Standard and licence note
Based on the published supply chain literature, chiefly Forrester (1961), Sterman (1989), Lee, Padmanabhan and Whang (1997) and Chen, Drezner, Ryan and Simchi-Levi (2000); all text, data and examples are original and fictional, and textbooks are named as further reading only. The beer distribution game is named as a teaching exercise; no game material is reproduced. This template is not affiliated with or endorsed by any business school, publisher or course. Check your course materials for the lead-time convention your professor uses. Template licence: MIT.
संबंधित टेम्पलेट
Accretion and Dilution Concept Card Template
Full merger EPS model: payment mix, cash on hand, debt, PPA amortisation, synergy phase-in, break-even synergies, EPS-neutral price, leverage, ownership
MBA और बिज़नेस स्कूलMBA Activity-Based Costing Concept Card Template (ABC, TDABC)
ABC card: cost hierarchy, two-stage ABC versus plant-wide rate, time-driven ABC with capacity cost rate and time equations, cost to serve, whale curve
MBA और बिज़नेस स्कूलMBA AI Decision-Making Concept Card Template
Human in the loop, automation bias, calibration, confusion matrix, precision and recall, cost-based thresholds, A/B tests of AI features, when not to use AI