Summary

Smart Software’s advanced supply chain analytics exploits multiple advanced methods. Two of the most important are “statistical bootstrapping” and “Monte Carlo simulation”. Since both involve lots of random numbers flying around, folks sometimes get confused about which is which and what they are good for. Hence, this note. Bottom line up front: Statistical bootstrapping generates demand scenarios for forecasting. Monte Carlo simulation uses the scenarios for inventory optimization.

Bootstrapping

Bootstrapping, also called “resampling” is a method of computational statistics that we use to create demand scenarios for forecasting. The essence of the forecasting problem is to expose possible futures that your company might confront so you can work out how to manage business risks. Traditional forecasting methods focus on computing “most likely” futures, but they fall short of presenting the full risk picture. Bootstrapping provides an unlimited number of realistic what-if scenarios.

Bootstrapping does this without making unrealistic assumptions about the demand, i.e., that it is not intermittent, or that it has a bell-shaped distribution of sizes. Those assumptions are crutches to make the math simpler, but the bootstrap is a procedure,  not an equation, so it doesn’t need such simplifications.

For the simplest demand type, which is a stable randomness with no seasonality or trend, bootstrapping is dead easy. To get a reasonable idea of what a single future demand value might be, pick one of the historical demands at random. To create a demand scenario, make multiple random selections from the past and string them together. Done. It is possible to add a little more realism by “jittering” the demand values, i.e., adding or subtracting a bit of additional randomness to each one, but even that is simple.

Figure 1 shows a simple bootstrap. The first line is a short sequence of historical demand for an SKU. The following lines show scenarios of future demand created by randomly selecting values from the demand history. For instance, the next three demand might be (0, 14, 6), or (2, 3, 5), etc.

Figure 1: Example of demand scenarios generated by a simple bootstrap

Higher frequency operations such as daily forecasting bring with them more complex demand patterns, such as double seasonality (e.g., day-of-week and month-of-year) and/or trend. This challenged us to invent a new generation of bootstrapping algorithms. We recently won a US Patent for this breakthrough, but the essence is as described above.

Monte Carlo Simulation

Monte Carlo is famous for its casinos, which, like bootstrapping, invoke the idea of randomness. Monte Carlo methods go back a long way, but the modern impetus came with the need to do some hairy calculations about where neutrons would fly when an A-bomb explodes.

The essence of Monte Carlo analysis is this: “Our problem is too complicated to analyze with paper-and-pencil equations. So, let’s write a computer program that codes the individual steps of the process, put in the random elements (e.g., which way a neutron shoots away), wind it up and watch it go. Since there’s a lot of randomness, let’s run the program a zillion times and average the results.”

Applying this approach to inventory management, we have a different set of randomly occurring events: e.g., a demand of a given size arrives on a random day, a replenishment of a given size arrives after a random lead time, we cut a replenishment PO of a given size when stock drops to or below a given reorder point. We code the logic relating these events into a program. We feed it with a random demand sequence (see bootstrapping above), run the program for a while, say one year of daily operations, compute performance metrics like Fill Rate and Average On Hand inventory, and “toss the dice” by re-running the program many times and averaging the results of many simulated years. The result is a good estimate of what happens when we make key management decisions: “If we set the reorder point at 10 units and the order quantity at 15 units, we can expect to get a service level of 89% and an average on hand of 21 units.” What the simulation is doing for us is exposing the consequences of management decisions based on realistic demand scenarios and solid math. The guesswork is gone.

Figure 2 shows some of the inner workings of a Monte Carlo simulation of an inventory system in four panels. The system uses a Min/Max inventory control policy with Min=10 and Max=25. No backorders are allowed: you have the good or you lose the business. Replenishment lead times are usually 7 days but sometimes 14. This simulation ran for one year.

The first panel shows a complex random demand scenario in which there is no demand on weekends, but demand generally increases each day from Monday to Friday. The second panel shows the random number of units on hand, which ebbs and flows with each replenishment cycle. The third panel shows the random sizes and timings of replenishment orders coming in from the supplier. The final panel shows the unsatisfied demand that jeopardizes customer relationships. This kind of detail can be very useful for building insight into the dynamics of an inventory system.

Figure 2: Details of a Monte Carlo simulation

Figure 2 shows only one of the countless ways that the year could play out. Generally, we want to average the results of many simulated years. After all, nobody would flip a coin once to decide if it were a fair coin. Figure 3 shows how four key performance metrics (KPI’s) vary from year to year for this system. Some metrics are relatively stable across simulations (Fill Rate), but others show more relative variability (Operating Cost= Holding Cost + Ordering Cost + Shortage Cost). Eyeballing the plots, we can estimate that the choices of Min=10, Max=25 leads to an average Operating cost of around $3,000 per year, a Fill Rate of around 90%, a Service Level of around 75%, and an Average On Hand of about 10

Figure 3: Variation in KPI’s computed over 1,000 simulated years

In fact, it is now possible to answer a higher level of management question. We can go beyond “What will happen if I do such-and-such?” to “What is the best thing I can do to achieve a fill rate of at least 90% for this item at the lowest possible cost?” The mathemagic  behind this leap is yet another key technology called “stochastic optimization”, but we’ll stop here for now. Suffice it to say that Smart’s SIO&P software can search the “design space” of Min and Max values to automatically find the best choice.

Managing spare parts presents numerous challenges, such as unexpected breakdowns, changing schedules, and inconsistent demand patterns. Traditional forecasting methods and manual approaches are ineffective in dealing with these complexities. To overcome these challenges, this blog outlines key strategies that prioritize service levels, utilize probabilistic methods to calculate reorder points, regularly adjust stocking policies, and implement a dedicated planning process to avoid excessive inventory. Explore these strategies to optimize spare parts inventory and improve operational efficiency.

Bottom Line Upfront

​1.Inventory Management is Risk Management.

2.Can’t manage risk well or at scale with subjective planning – Need to know service vs. cost.

3.It’s not supply & demand variability that are the problem – it’s how you handle it.

4.Spare parts have intermittent demand so traditional methods don’t work.

5.Rule of thumb approaches don’t account for demand variability and misallocate stock.

6.Use Service Level Driven Planning  (service vs. cost tradeoffs) to drive stock decisions.

7.Probabilistic approaches such as bootstrapping yield accurate estimates of reorder points.

8.Classify parts and assign service level targets by class.

9.Recalibrate often – thousands of parts have old, stale reorder points.

10.Repairable parts require special treatment.

Do Focus on the Real Root Causes

Intermittent Demand

• Slow moving, irregular or sporadic with a large percentage of zero values.
• Non-zero values are mixed in randomly – spikes are large and varied.
• Isn’t bell shaped (demand is not Normally distributed around the average.)
• At least 70% of a typical Utility’s parts are intermittently demanded.

Normal Demand

• Very few periods of zero demand (exception is seasonal parts.)
• Often exhibits trend, seasonal, or cyclical patterns.
• Lower levels of demand variability.
• Is bell-shaped (demand is Normally distributed around the average.)

Don’t rely on averages

• OK for determining typical usage over longer periods of time.
• Often forecasts more “accurately” than some advanced methods.
• But…insufficient for determining what to stock.

Don’t Buffer with Multiples of Averages

Example:  Two equally important parts so let’s treat them the same.
We’ll order more  when On Hand Inventory ≤ 2 x Avg Lead Time Demand.

Do use Service Level tradeoff curves to compute safety stock

Standard Normal Probabilities

OK for normal demand. Doesn’t work with intermittent demand!

Don’t use Normal (Bell Shaped) Distributions

• You’ll get the tradeoff curve wrong:

– e.g., You’ll target 95% but achieve 85%.

– e.g., You’ll target 99% but achieve 91%.

• This is a huge miss with costly implications:

– You’ll stock out more often than expected.

– You’ll start to add subjective buffers to compensate and then overstock.

– Lack of trust/second-guessing of outputs paralyzes planning.

Why Traditional Methods Fail on Intermittent Demand: 

Traditional Methods are not designed to address core issues in spare parts management.

Need: Probability distribution (not bell-shaped) of demand over variable lead time.

• Get: Prediction of average demand in each month, not a total over lead time.
• Get: Bolted-on model of variability, usually the Normal model, usually wrong.

Need: Exposure of tradeoffs between item availability and cost of inventory.

• Get: None of this; instead, get a lot of inconsistent, ad-hoc decisions.

Do use Statistical Bootstrapping to Predict the Distribution:

Then exploit the distribution to optimize stocking policies.

How does Bootstrapping Work?

24 Months of Historical Demand Data.

Bootstrap Scenarios for a 3-month Lead Time.

Bootstrapping Hits the Service Level Target with nearly 100% Accuracy!

• National Warehousing Operation.

Task: Forecast inventory stocking levels for 12,000 intermittently demanded SKUs at 95% & 99% service levels

Results:

At 95% service level, 95.23% did not stock out.

At 99% service level, 98.66% did not stock out.

This means you can rely on output to set expectations and confidently make targeted stock adjustments that lower inventory and increase service.

Set Target Service Levels According to Order Frequency & Size

Recalibrate Reorder Points Frequently

• Static ROPs cause excess and shortages.
• As lead time increases, so should the ROP and vice versa.
• As usage decreases, so should the ROP and vice versa.
• Longer you wait to recalibrate, the greater the imbalance.
• Mountains of parts ordered too soon or too late.
• Wastes buyers’ time placing the wrong orders.
• Breeds distrust in systems and forces data silos.

Do Plan Rotables (Repair Parts) Differently

Summary

1.Inventory Management is Risk Management.

2.Can’t manage risk well or at scale with subjective planning – Need to know service vs. cost.

3.It’s not supply & demand variability that are the problem – it’s how you handle it.

4.Spare parts have intermittent demand so traditional methods don’t work.

5.Rule of thumb approaches don’t account demand variability and misallocate stock.

6.Use Service Level Driven Planning  (service vs. cost tradeoffs) to drive stock decisions.

7.Probabilistic approaches such as bootstrapping yield accurate estimates of reorder points.

8.Classify parts and assign service level targets by class.

9.Recalibrate often – thousands of parts have old, stale reorder points.

10.Repairable parts require special treatment.

1. Forecasting is an art that requires a mix of professional judgment and objective statistical analysis. Successful demand forecasts require a baseline prediction leveraging statistical forecasting methods. Once established, the process can focus on how best to adjust statistical forecasts based on your own insights and business knowledge.

2. The forecasting process is usually iterative. You may need to make several refinements of your initial forecast before you are satisfied. It is important to be able to generate and compare alternative forecasts quickly and easily. Tracking accuracy of these forecasts over time, including alternatives that were not used, helps inform and improve the process.

3. The credibility of forecasts depends heavily on graphical comparisons with historical data.  A picture is worth a thousand words, so always display forecasts via instantly available graphical displays with supporting numerical reports.

4. One of the major technical tasks in forecasting is to match the choice of forecasting technique to the nature of the data. Effective demand forecasting processes employ capabilities that identify the right method to use.  Features of a data series like trend, seasonality or abrupt shifts in level suggest certain techniques instead of others. An automatic selection, which selects and uses the appropriate forecasting method automatically, saves time and ensures your baseline forecast is as accurate as possible.

5. Successful demand forecasting processes work in tandem with other business processes.   For example, forecasting can be an essential first step in financial analysis.  In addition, accurate sales and product demand forecasts are fundamental inputs to a manufacturing company’s production planning and inventory control processes.

6. A good planning process recognizes that forecasts are never exactly correct. Because some error creeps into even the best forecasting process, one of the most useful supplements to a forecast are honest estimates of its margin of error and forecast bias.

Sales forecasts are often inaccurate simply because the sales team is forced to give a number even though they don’t really know what their customer demand is going to be. Let the sales teams sell.  Don’t bother playing the game of feigning acceptance of these forecasts when both sides (sales and supply chain) know it is often nothing more than a WAG.   Do this instead:

• Accept demand variability as a fact of life. Develop a planning process that does a better job account for demand variability.

• Agree on a level of stockout risk that is acceptable across groups of items.

• Once the stockout risk is agreed to, use software to generate an accurate estimate of the safety stock needed to counter the demand variability.

• Get buy-in. Customers must be willing to pay a higher price per unit for you to deliver extremely high service levels.  Salespeople must accept that certain items are more likely to have backorders if they prioritize inventory investment on other items.

• Using a consensus #safetystock process ensures you are properly buffering and setting the right expectations with sales, customers, finance, and supply chain.

When you do this, you free all parties from having to play the prediction game they were not equipped to play in the first place. You’ll get better results, such as higher service levels with lower inventory costs. And with much less finger-pointing.

What’s all the hoopla around the term “probabilistic forecasting?” Is it just a more recent marketing term some software vendors and consultants have coined to feign innovation? Is there any real tangible difference compared to predecessor “best fit” techniques?  Aren’t all forecasts probabilistic anyway?

To answer this question, it is helpful to think about what the forecast really is telling you in terms of probabilities.  A “good” forecast should be unbiased and therefore yield a 50/50 probability being higher or lower than the actual.  A “bad” forecast will build in subjective buffers (or artificially depress the forecast) and result in demand that is either biased high or low.  Consider a salesperson that intentionally reduces their forecast by not reporting sales they expect to close to be “conservative.” Their forecasts will have negative forecast bias as actuals will nearly always be higher than what they predicted.   On the other hand, consider a customer that provides an inflated forecast to their manufacturer.  Worried about stockouts, they overestimate demand to ensure their supply.  Their forecast will have a positive bias as actuals will nearly always be lower than what they predicted. 

These types of one-number forecasts described above are problematic.  We refer to these predictions as “point forecasts” since they represent one point (or a series of points over time) on a plot of what might happen in the future.   They don’t provide a complete picture because to make effective business decisions such as determining how much inventory to stock or the number of employees to be available to support demand requires detailed information on how much lower or higher the actual will be!  In other words, you need the probabilities for each possible outcome that might occur.  So, by itself, the point forecast isn’t probabilistic one.   

To get a probabilistic forecast, you need to know the distribution of possible demands around that forecast.  Once you compute this, the forecast becomes “probabilistic.”  How forecasting systems and practitioners such as demand planners, inventory analysts, material managers, and CFOs determine these probabilities is the heart of the question: “what makes a forecast probabilistic?”     

Normal Distributions
Most forecasts and the systems/software that produce them start with a prediction of demand.  Then they figure out the range of possible demands around that forecast by making incorrect theoretical assumptions about the distribution.  If you’ve ever used a “confidence interval” in your forecasting software, this is based on a probability distribution around the forecast.  The way this range of demand is determined is to assume a particular type of distribution.  Most often this means assuming a bell shaped, otherwise known as a normal distribution.  When demand is intermittent, some inventory optimization and demand forecasting systems may assume the demand is Poisson shaped. 

After creating the forecast, the assumed distribution is slapped around the demand forecast and you then have your estimate of probabilities for every possible demand – i.e., a “probabilistic forecast.”  These estimates of demand and associated probabilities can then be used to determine extreme values or anything in between if desired.  The extreme values at the upper percentiles of the distribution (i.e., 92%, 95%, 99%, etc.) are most often used as inputs to inventory control models.  For example, reorder points for critical spare parts in an electrical utility might be planned based on a 99.5% service level or even higher.  While a non-critical service part might be planned at an 85% or 90% service level.

The problem with making assumptions about the distribution is that you’ll get these probabilities wrong.  For example, if the demand isn’t normally distributed but you are forcing a bell shaped/normal curve on the forecast then how can then the probabilities will be incorrect.  Specifically, you might want to know the level of inventory needed to achieve a 99% probability of not running out of stock and the normal distribution will tell you to stock 200 units.  But when compared to the actual demand, you come to find out that 200 units only filled demand entirely in 40/50 observations.  So, instead of getting a 99% service level you only achieved an 80% service level!  This is a gigantic miss resulting from trying to fit a square peg into a round hole.  The miss would have led you to take an incorrect inventory reduction.

Empirically Estimated Distributions are Smart
To produce a smart (read accurate) probabilistic forecast you need to first estimate the distribution of demand empirically without any naïve assumptions about the shape of the distribution.  Smart Software does this by running tens of thousands of simulated demand and lead time scenarios.  Our solution leverages patented techniques that incorporate Monte Carlo simulation, Statistical Bootstrapping, and other methods.  The scenarios are designed to simulate real life uncertainty and randomness of both demand and lead times.  Actual historical observations are utilized as the primary inputs, but the solution will give you the option of simulating from non-observed values as well.  For example, just because 100 units was the peak historical demand, that doesn’t mean you are guaranteed to peak out at 100 in the future.  After the scenarios are done you will know the exact probability for each outcome. The “point” forecast then becomes the center of that distribution.  Each future period over time is expressed in terms of the probability distribution associated with that period.

Leaders in Probabilistic Forecasting
Smart Software, Inc. was the first company to ever introduce statistical bootstrapping as part of a commercially available demand forecasting software system twenty years ago.  We were awarded a US patent at the time for it and named a finalist in the APICS Corporate Awards of Excellence for Technological Innovation.  Our NSF Sponsored research that led to this and other discoveries were instrumental in advancing forecasting and inventory optimization.    We are committed to ongoing innovation, and you can find further information about our most recent patent here.