Inventory planning parameters, such as safety stock levels, reorder points, Min/Max settings, lead times, order quantities, and DDMRP buffers directly impact inventory spending and ability to meet customer demand. Based on these parameter settings, your ERP system makes daily purchase order suggestions.

Ensuring that these inputs are understood and optimized regularly will substantially reduce wasteful inventory spending and dramatically improve customer service levels.

Given the importance of getting these planning parameters right, we spend a lot of time during our consultations asking (1) how these parameter values are calculated and (2) how often they are updated. Most often the methods for calculating the parameter values are rule of thumb. You can read about why using rule of thumb approaches is so problematic here  – Beware of Simple Rules of Thumb for Managing Inventory.

This blog will focus on the frequency of updates. When we interview companies and ask them how often they update planning parameters, the answer we nearly always hear is “every day!” A follow up question or two most often reveals that this just isn’t true. What “every day” actually means in practice is this: Every day, the ERP system suggests dozens to hundreds of purchase orders and/or production jobs. The planner, let’s call him Peter, reviews these orders daily and decides whether to release, modify, or cancel them. If the order suggestion doesn’t “feel right”, Peter reviews the planning inputs and modifies the order if necessary. For example, Peter may feel there is already enough inventory on hand. To “fix” the issue, he will reduce the reorder point and cancel the order. Or if he feels that the order should have been placed weeks ago, Peter may expedite the order and increase the reorder point and order quantity to ensure there will be plenty of stock the next time.

The principal flaws with this approach are that it is reactive and incomplete. Here is why:

Reactive

It only assesses the handful of items marked for replenishment on any given day but not others. The trigger for reviewing an item is when the ERP suggests an order, and that will only happen when the reorder point or Min is breached. If the Min is too high and breaches earlier than it should have, an unneeded order will be placed unless caught by the planner. If the Min is too low, well, it is too late to fix the error. No matter how large the order suggestion is, you still have to wait to be resupplied and since the order was suggested late, a stockout during the replenishment period is highly probable. Where is the “planning” in such a process? As one customer put it, “Our former process was, in hindsight, spent managing the outputs and not the inputs.”

Incomplete

What about the thousands of other items that have a Min/Max, safety Stock, Reorder Point, or other parameters that isn’t being reassessed given the updated demand and supply data. The planner isn’t reviewing any of these items which means problems aren’t being identified in advance. Compounding the problem is that when Peter does make a change he doesn’t have any tools to assess the quality of his changes. If he modifies the min/max settings he doesn’t know the specific impact this will have on inventory value, ordering costs, holding costs, stock outs, and service levels. He only knows that an increase in inventory will likely improve service and increase costs. He doesn’t know for example whether his inventory has reached a point of diminishing returns. When inventory decisions are made with only a very rough understanding of the trade offs it creates more problems downstream. You wouldn’t want your carpenter making rough estimates of their measurements yet it’s commonplace for inventory planning professionals to do so with millions of dollars in inventory spend at stake.

How Often Do Most Companies Update Parameters?

So how often do most companies make system-wide updates to their planning parameters such as reorder points, safety stocks, Min/Max settings, lead times, and order quantities? Typically, mass updates occur quarterly, annually, and in some cases never – the only times changes are made are when an order is triggered by ERP. Not exactly agile.

The biggest reason given for not intervening more often is that it takes too much time. Most companies set these key parameters using very unwieldy Excel programs or ERP applications that simply aren’t designed to conduct systemic inventory planning. This is where inventory optimization software can help.

Using inventory optimization software and probability forecasting to update key planning parameters frequently, say every week or month instead of quarterly or annually, enables you quickly respond to changes in your business. You can seize on cost saving opportunities, as when demand turns down and you can reduce reorder points and/or order quantities and possibly cancel outstanding orders. Or you can respond to problems, as when demand increases threaten your service level commitments to customers, or supplier lead times increase and require re-computation of reorder points.

How to do it Right

The key is establishing an agreed upon set of performance and inventory value metrics and letting the software monitor the state of play in the background and alert you to exceptional situations. This is simply one more way of saying that, once systems have been established, you want to go forward using management by exception. You can set ranges within which things can bubble along as they normally do, but once a critical parameter like “stock out risk exceeds a pre-defined level” or “inventory value or costs exceeds a pre-defined level,” the software can provide a daily alert and can also recommend a response, such as raising a reorder point. With this level of automated assistance, it becomes possible to keep your finger on the pulse of the inventory without being overwhelmed by the sheer volume of data.

For example, you may choose an initial set of inventory parameters as the policy because you could see from the software that it meets your service level goals within your inventory budget. You may let the system prescribe service level targets for you and be comfortable with the settings because inventory value is within the budget. However, if demand gets less predictable than historically, you won’t be able to achieve the same level of service without an increase in inventory. An exception report will identify this and enable you to make an informed decision on what to do. You can decide to modify the policy or keep it the same. If you keep it the same, you now know the additional risks and change in inventory costs. This can be communicated to all stake holders so that there aren’t any surprises.

Plan Don’t React

Rather than being constantly in reactive mode, you can handle what really needs to be handled and still have some time to do forward thinking. For instance, you can do “what if” analyses on such issues as which supplier lead times would yield the biggest payoff if reduced, or whether service level targets should be adjusted to account for shifts in customer criticality, or similar policy issues. After all, it’s not as if you are not going to end up with a full daily agenda, it’s just a question of whether you can elevate that agenda to a more strategic level. So if you are spending all of your “planning” time managing the outputs of your ERP instead of constructively reviewing and optimizing the inputs, it is time to reassess your inventory planning process.

In our last blog we posed the question:  How can you be sure that you really have a policy for inventory planning and demand forecasting? We explained how an organization’s lack of understanding on the basics (how a forecast is created, how safety stock buffers are determined, and how/why these values are adjusted) contributes to poor forecast accuracy, misallocated inventory, and lack of trust in the whole process.

In this blog, we review 10 specific questions you can ask to uncover what’s really happening at your company. We detail the typical answers provided when a forecasting/inventory planning policy doesn’t really exist, explain how to interpret these answers, and offer some clear advice on what to do about it.

Always start with a simple hypothetical example. Focusing on a specific problem you just experienced is bound to provoke defensive answers that hide the full story. The goal is to uncover the actual approach used to plan inventory and forecasts that has been baked into the mental math or spreadsheets.   Here is an example:

Suppose you have 100 units on hand, the lead time to replenish is 3 months, and the average monthly demand is 20 units?   When should you order more?  How much would you order? How will your answer change if expected receipts of 10 per month were scheduled to arrive?  How will your answer change if the item is the item is an A, B, or C item, the cost of the item is high or low, lead time of the item is long or short?  Simply put, when you schedule a production job or place a new order with a supplier, why did you do it? What triggered the decision to get more?  What planning inputs were considered?

When getting answers to the above question, focus on uncovering answers to the following questions:

1. What is the underlying replenishment approach? This will typically be one of Min/Max, forecast/safety stock, Reorder Point/Order Quantity, Periodic Review/Order Up To or even some odd combination

2. How are the planning parameters, such as demand forecasts, reorder points, or Min/Max, actually calculated? It’s not enough to know that you use Min/Max.  You have to know exactly how these values are calculated. Answers such as “We use history” or “We use an average” are not specific enough.   You’ll need answers that clearly outline how history is used.  For example, “We take an average of the last 6 months, divide that by 30 to get a daily average, and then multiply that by the lead time in days.  For ‘A’ items we then multiply the lead time average by 2 and for ‘B’ items we use a multiplier of 1.5.” (While that is not an especially good technical approach, at least it has a clear logic.)

Once you have a policy well-defined, you can identify its weaknesses in order to improve it.  But if the answer provided doesn’t get much further past “We use history”, then you don’t have a policy to start with.   Answers will often reveal that different planners use history in different ways.  Some may only consider the most recent demand, others might stock according to the average of the highest demand periods, etc.  In other words, you may find that you actually have multiple ill-conceived “policies”.

3. Are forecasts used to drive replenishment planning and if so, how? Many companies will say they forecast, but their forecasts are calculated and used differently. Is the forecast used to predict what on hand inventory will be in the future, resulting in an order being triggered?  Or is it used to derive a reorder point but not to predict when to order (i.e. I predict we’ll sell 10 a week so to help protect against stock out, I’ll order more when on hand gets to 15)? Is it used as a guide for the planner to help subjectively determine when they should order more?  Is it used to set up blanket orders with suppliers?  Some use it to drive MRP. You’ll need to know these specifics.  A thorough answer to this question might look like this: “My forecast is 10 per week and my lead time is 3 weeks so I make my reorder point a multiple of that forecast, typically 2 x lead time demand or 60 unit for important items and I use a smaller multiple for less important items.  (Again, not a great technical approach, but clear.)

4.  What technique is actually used to generate the forecast? Is it an average, a trending model such as double exponential smoothing, a seasonal model? Does the choice of technique change depend on the type of demand data or when new demand data is available? (Spare parts and high-volume items have very different demand patterns.) How do you go about selecting the forecast model? Is this process automated?  How often is the choice of model reconsidered?  How often are the model parameters recomputed? What is the process used to reconsider your approach?  The answer here documents how the baseline forecasts are produced.  Once determined, you can conduct an analysis to identify whether other forecasting methods would improve forecast accuracy.  If you aren’t documenting forecast accuracy and conducting “forecast value add” analysis then you aren’t in a position to properly assess whether the forecasts being produced are the best that they can be.  You’ll miss out on opportunities to improve the process, increase forecast accuracy, and educate the business on what type of forecast error is normal and should be expected.

5. How do you use safety stock? Notice the question was not “Do you use safety stock?” In this context, and to keep it simple, the term “safety stock” means stock used to buffer inventory against supply and demand variability.  All companies use buffering approaches in some way.  There are some exceptions though.  Maybe you are a job shop manufacturer that procures all parts to order and your customers are completely fine waiting weeks or months for you to source material, manufacture, QA, and ship.  Or maybe you are high-volume manufacturer with tons of buying power so your suppliers set up local warehouses that are stocked full and ready to provide inventory to you almost immediately.  If these descriptions don’t describe your company, you will definitely have some sort of buffer to protect against demand and supply variability.  You may not use the “safety stock” field in your ERP but you are definitely buffering.

Answers might be provided such as “We don’t use safety stock because we forecast.”  Unfortunately, a good forecast will have a 50/50 chance of being over/under the actual demand.  This means you’ll incur a stock out 50% of the time without a safety stock buffer added to the forecast.  Forecasts are only perfect when there is no randomness. Since there is always randomness, you’ll need to buffer if you don’t want to have abysmal service levels.

If the answer isn’t revealed, you can probe a bit more into how the varying replenishment levers are used to add possible buffers which leads to questions 6 & 7.

6. Do you ever increase the lead time or order earlier than you truly need to?
In our hypothetical example, your supplier typically takes 4 weeks to deliver and is pretty consistent. But to protect against stockouts your buyer routinely orders 6 weeks out instead of 4 weeks.  The safety stock field in your ERP system might be set to zero because “we don’t use safety stock”, but in reality, the buyer’s ordering approach just added 2 weeks of buffer stock.

7. Do you pad the demand forecast?
In our example, the planner expects to consume 10 units per month but “just in case” enters a forecast of 20 per month.  The safety stock field in the MRP system is left blank but the now disguised buffer stock has been smuggled into the demand forecast.  This is a mistake that introduces “forecast bias.”  Not only will your forecasts be less accurate but if the bias isn’t accounted for and safety stock is added by other departments, you will overstock.

The ad-hoc nature of the above approaches compounds the problems by not considering the actual demand or supply variability of the item. For example, the planner might simply make a rule of thumb that doubles the lead time forecast for important items.  One-size doesn’t fit all when it comes to inventory management.  This approach will substantially overstock the predictable items while substantially understocking the intermittently demanded items. You can read “Beware of Simple Rules of Thumb for Managing Inventory” to learn more about why this type of approach is so costly.

The ad-hoc nature of the approaches also ignores what happens the company is faced with a huge overstock or stock out. When trying to understand what happened, the stated policies will be examined. In the case of an overstock, the system will show zero safety stock.  The business leaders will assume they aren’t carrying any safety stock, scratch their heads, and eventually just blame the forecast, declare “Our business can’t be forecasted” and stumble on. They may even blame the supplier for shipping too early and making them hold more than needed. In the case of a stock out, they will think they aren’t carrying enough and arbitrarily add more stock across many items not realizing there is in fact lots of extra safety stock baked into process.  This makes it more likely inventory will need to be written off in the future.

8. What is the exact inventory terminology used? Define what you mean by safety stock, Min, reorder point, EOQ, etc.  While there are standard technical definitions it’s possible that something differs, and miscommunication here will be problematic.  For example, some companies refer to Min as the amount of inventory needed to satisfy lead time demand while some may define Min as inclusive of both lead time demand and safety stock to buffer against demand variability. Others may mean the minimum order quantity.

9. Is on hand inventory consistent with the policy? When your detective work is done and everything is documented, open your spreadsheet or ERP system and look at the on-hand quantity. It should be more or less in line with your planning parameters (i.e. if Min/Max is 20/40 and typical lead time demand is 10, then you should have roughly 10 to 40 units on hand at any given point in time.  Surprisingly, for many companies there is often a huge inconsistency. We have observed situations where the Min/Max setting is 20/40 but the on-hand inventory is 300+.  This indicates that whatever policy has been prescribed just isn’t being followed.   That’s a bigger problem.

10. What are you going to do next?

Demand forecasting and inventory stocking policy need to be well-defined processes that are understood and accepted by everybody involved.  There should be zero mystery.

To do this right, the demand and supply variability must be analyzed and used to compute the proper levels of safety stock.   Adding buffers without an implicit understanding of what each additional unit of buffer stock is buying you in terms of service is like arbitrarily throwing a handful of ingredients into a cake recipe.  A small change in ingredients can have a huge impact on what comes out of the oven – one bite too sweet but the next too sour.  It is the same with inventory management.  A little extra here, a little less there, and pretty soon you find yourself with costly excess inventory in some areas, painful shortages in others, no idea how you got there, and with little guidance on how to make things better.

Modern inventory optimization and demand planning software with its advanced analytics and strong basis in forecast analysis can help a good deal with this problem. But even the best software won’t help if it is used inconsistently.

In my previous post in this series on essential concepts, “What is ‘A Good Forecast’”, I discussed the basic effort to discover the most likely future in a demand planning scenario. I defined a good forecast as one that is unbiased and as accurate as possible. But I also cautioned that, depending on the stability or volatility of the data we have to work with, there may still be some inaccuracy in even a good forecast. The key is to have an understanding of how much.

This topic, managing uncertainty, is the subject of post by my colleague Tom Willemain, “The Average is not the Answer”. His post lays out the theory for responsibly confronting the limits of our predictive ability. It’s important to understand how this actually works.

As I briefly touched on at the end of my previous post, our approach begins with something called a “sliding simulation”. We estimate how accurately we are predicting the future by using our forecasting techniques on an older portion of history, excluding the most recent data. We can then compare what we would have predicted for the recent past with our actual real world information about what happened. This is a reliable method to estimate how closely we are predicting future demand.

Safety stock, a carefully measured buffer in inventory level we stock above our prediction of most likely demand, is derived from the estimate of forecast error coming out of the “sliding simulation”. This approach to dealing with the accuracy of our forecasts efficiently balances between ignoring the threat of the unpredictable and costly overcompensation.

In more technical detail: the forecasts errors that are estimated by this sliding simulation process indicate the level of uncertainty. We use these errors to estimate the standard deviation of the forecasts. Now, with regular demand, we can assume the forecasts (which are estimates of future behavior) are best represented by a bell-shaped probability distribution—what statisticians call the “normal distribution”. The center of that distribution is our point forecast. The width of that distribution is the standard deviation of the “sliding simulation” forecast from the known actual values—we obtain this directly from our forecast error estimates.

Once we know the specific bell shaped curve associated with the forecast, we can easily estimate the safety stock buffer that is needed. The only input from us is the “service level” that is desired, and the safety stock at that service level can be ascertained. (The service level is essentially a measure of how confident we need to be in our inventory stocking levels, with increasing confidence requiring corresponding expenditures on extra inventory.) Notice, we are assuming that the correct distribution to use is the normal distribution. This is correct for most demand series where you have regular demand per period. It fails when demand is sporadic or intermittent.

In the next piece in this series, I’ll discuss how Smart Forecasts deals with estimating safety stock in those cases of intermittent demand, when the assumption of normality is incorrect.

Nelson Hartunian, PhD, co-founded Smart Software, formerly served as President, and currently oversees it as Chairman of the Board. He has, at various times, headed software development, sales and customer service.