Anybody doing the job knows that managing inventory can be stressful. Common stressors include: Customers with “special” requests, IT departments with other priorities, balky ERP systems running on inaccurate data, raw material shortages, suppliers with long lead times in far-away countries where production often stops for various reasons and more. This note will address one particular and ever-present source of stress: demand variability.

Everybody Has a Forecasting Problem

Suppose you manage a large fleet of spare parts. These might be surgical equipment for your hospital, or repair parts for your power station. Your mission is to maximize up time. Your enemy is down time. But because breakdowns hit at random, you are constantly in reactive mode. You might hope for rescue from forecasting technologies. But forecasts are inevitably imperfect to some degree: the element of surprise is always present.  You might wait for Internet of Things (IOT) tech to be deployed on your equipment to monitor and detect impending failures, helping you schedule repairs well in advance. But you know you can’t meter up the thousands of small things that can fail and disable a big thing.

So, you decide to combine forecasting with inventory management and build buffers or safety stock to protect against surprise spikes in demand. Now you have to work out how much safety stock to maintain, knowing that too little means vulnerability and too much means bloat.

Suppose you handle finished goods inventories for a make-to-stock company. Your problem is essentially the same as in managing service parts: You have external customers and uncertain demand. But you may also have additional problems in terms of synchronizing multiple suppliers of components that you assemble into finished goods. The suppliers want you to tell them how much of their stuff to make so you can make your stuff, but you don’t know how much of your own stuff you’ll need to make.

Finally, suppose you handle finished goods in a build-to-order company. You might think that you no longer have a forecasting problem, since you don’t build until you are paid to build. But you do have a forecasting problem. Since your finished goods might be assembled from a mixture of components and sub-assemblies, you have to translate some forecast of finished goods demand to work out a forecast of those components. Otherwise, you will go to make your finished goods and discover that you don’t have a required component and have to wait until you can re-actively assemble everything you need. And your customers might not be willing to wait.

So, everybody has a forecasting problem.

What Makes Forecasting Difficult

Forecasting can be quick, easy and dead accurate – as long as the world is simple. If demand for your product is 10 units every week, month after month, you can make very accurate forecasts. But life is not quite like that. If you’re lucky and life is almost like that – maybe weekly demand is more like {10, 9, 10, 8, 12, 10, 10…} — you can still make very accurate forecast and just make minor adjustments around the edges. But if life is as it more often is – maybe weekly demand looks like {0, 0, 7, 0, 0, 0, 23, 0 …} – demand forecasting is difficult indeed. The key distinction is demand variability: it’s the zigging and zagging that creates the pain.

Safety Stock Takes Over Where Forecasting Leaves Off

Statistical forecasting methods are an important part of the solution. They let you squeeze as much advantage as possible from the historical patterns of demand your company has recorded for each item. The job of forecasts is to describe what is typical, which provides the base on which to cope with randomness in demand. Statistical forecasting techniques work by finding “big picture” features in demand records, such as trend and seasonality, then projecting those into the future. They all implicitly assume that whatever patterns exist now will persist, so 5% growth will continue, and July demand will always be 20% higher than February demand. To get to that point, statistical forecasting methods use some form of averaging to smother the “noise” in the demand history.

But then the rest of the job falls on inventory management, because the atypical, random component of future demand will still be a hassle in the future. This inevitable level of uncertainty has to be handled by the “shock-absorber” called safety stock.

The same methods that produce forecasts of trend and/or seasonality can be used to estimate the amount of forecast error. This has to be done carefully using a method called “holdout analysis”.  It works like this. Suppose you have 365 observations of daily demand for Item X, which has a replenishment lead time of 10 days. You want to know how many units will be demanded over some future 10-day period. You might input the first 305 days of demand history into the forecasting technique and get forecasts for the next 10 days, days 306-315.

The answer gives you one estimate of the 10-day total demand. Importantly, it also gives you one estimate of the variability around that forecast, i.e., the forecast error, the difference between what actually happened in days 306-315 and what was forecasted. Now you can repeat the process, this time using the first 306 days to forecast the next 10, the first 307 days to forecast the next 10, etc. You end up with 52 honest estimates of the variability of total demand over a 10-day lead time. Suppose 95% of those estimates are less than 28 units. Then 28 units would be a pretty safe safety stock to add to the forecast, since you will run into shortages only 5% of the time.

Modern statistical software does these calculations automatically. It can ease at least one of the chronic headaches of inventory management by helping you cope with demand variability.

In another 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.

1. Built-in ERP functionality is baked into Order Management.

Consider what is meant by “demand management”, “demand planning”, and “forecasting”. These terms imply certain standard functionality for collaboration, statistical analysis, and reporting to support a professional demand planning process.  However, in most ERP systems, “demand management” consists of executing MRP and reconciling demand and supply for the purpose of placing orders, i.e., “order management.” It has very little to do with demand planning which is discrete process focused on developing the best possible predictions of future demand by combining statistical analysis with business knowledge of events, promotions, and sales force intelligence.   Most ERP systems offer little statistical capability and, when offered, the user is left with a choice of a few statistical methods that they either have to apply manually from a drop-down list or program themselves. It’s baked into the order management process enabling the user to possibly how the forecast might impact inventory.  However, there isn’t any ability to manage the forecast, improve the quality of the forecast, apply and track management overrides, collaborate, measure forecast accuracy, and track “forecast value add.” 

2. ERP planning methods are often based on simplistic rules of thumb.

ERP systems will always offer min, max, safety stock, reorder point, reorder quantity, and forecasts to drive replenishment decisions.  But what about the underlying methods used to calculate these important drivers?   In nearly every case, the methods provided are nothing more than rule-of-thumb approaches that don’t account for demand or supplier variability.  Some do offer “service level targeting” but mistakenly rely on the assumption of a Normal distribution (“bell-shaped curve”) which means the required safety stocks and reorder points recommended by the system to achieve the service level target are going to be flat out wrong if your data doesn’t fit the ideal theoretical model, which is often gravely unrealistic.  Such over-simplified calculations tend to do more harm than good.  

3. You’ll probably still use spreadsheets for at least 2 years after purchase.

Most often, if you were to implement a new ERP solution, your old data would be stranded.  So, any native ERP functionality for forecasting, setting stocking policy such as Min/Max, etc., cannot be used, and you will be forced to revert back to cumbersome and error-prone spreadsheets for at least two years (one year to implement at earliest and another year to collect at least 12 months of history).  Hardly a digital transformation.  Using a best-of-breed solution avoids this problem.  You can load data from your legacy ERP system and not disrupt your ERP deployment.  This means that on Day 1 of ERP go-live you can populate your new ERP system with better inputs for demand forecasts, safety stocks, reorder points, and Min/Max settings.

4. ERP isn’t designed to do everything

The “Do everything in ERP/One-Vendor” mindset was a marketing message promoted by ERP firms, particularly SAP, to get you, the customer, to spend 100% of your IT budget with them.  That marketing message has been parroted back to users by analyst groups, IT firms, and systems integrators, drowning out rational voices who asked “Why do you want to be so dependent on one firm to the point of using inferior forecasting and inventory planning technology?”  The sheer number of IT failures and huge implementation costs have caused many companies to rethink their approach to ERP.  With the advent of specialized planning apps born in the cloud with no IT footprint, the way to go is a “thin” ERP focused on the fundamentals – accounting, order management, financials – but supported by specialized planning apps. 

The expertise of ERP consultant’s lies in how their system is designed to automate certain business processes and how the system can be configured or customized.   Their consultants are not specialists in on proper approaches to planning stock, forecasting, and inventory planning.  So if you are trying to understand what demand planning approach is right for your business, how should you buffer properly, (e.g., “Should we do Min/Max or forecast-based replenishment?” “Should we use forecasting method X?”), you generally aren’t going to find it and if you do that resource will be spread quite thin. 

1. The setup will be straightforward.

We just need to feed our demand histories into our new statistical methods, and we can start planning more effectively.  Not quite: it’s about the technology and the process. You are investing in a new business process to develop forecasts for driving business strategy and inventory planning decisions. It will take time to get all stakeholders involved: sales, marketing, procurement, operations, and maintenance/technicians (for spare parts inventory).  Who owns the forecast? What will your items’ forecast hierarchy look like?  Where will the most business knowledge come from?  Is there a consensus process that will use the business knowledge to customize the forecasts to your particular situation? Does everyone understand the statistical methods?   Is there agreement on the underlying values that balance holding, ordering and (especially) shortage costs? Are you prepared to make choices along the crucial tradeoff curve relating inventory costs to customer service levels?  How do you plan on measuring forecasting accuracy/error? Does management understand the concept of “forecast value add” whereby you track the error with each version of the forecast (statistical error vs. sales forecast error vs. consensus error).  Without this context and agreed upon participation from key stake holders, the system will still be implemented but used in silo

2. All I need is historical demand data, and then I can start forecasting.

Almost.  Getting good data isn’t easy.  Are your demand history data complete and correct? Are your supplier data (e.g., lead times) also complete and correct? Have you recognized the special needs of new and end-of-life items? Sure, IT could export a file of aggregated demand data (weekly or monthly), but how do you know it is correct?  When orders and shipments are booked, they fall under a variety of different transactions codes.  You have to be able to know how to compose your demand signal.  Orders or shipments? Include or exclude returns? What about warehouse transfers?  What about returns that occur many periods after initial shipment?  How will my ERP interpret the forecast?  But wait…we are using a solution with an ERP connector that promises data will flow back and forth seamlessly.  An ERP connector will certainly cover the transfer of historical data and forecast results between systems but it won’t improve bad data quality.  You also have to make sure the ERP connector has the flexibility of determining how to compose your demand history.  For example, if it is hard coded to pull certain transactions types that you may not want or require different transactions it doesn’t include, you’ll need customizations.  There is also the problem of product supersession and/or location changes – i.e., Product A gets phased out and becomes Product B, or now Product A ships from a different warehouse.   Sounds simple, but if this happens often across thousands of items then it must be accounted for as part of an automatic forecasting process.  Otherwise, your users are required to manually manage this constant updating. Then you lose economies of scale. More “data wrangling” means more hassle, more errors, and missed decision deadlines. Less frequent updates can mean less accurate forecasts, which leads to excess inventory for some items and insufficient inventory for others

3. If we get a better forecast, we’ll have the right inventory, reduce stockouts, and increase service.

The demand forecast is one component of a larger process.  If you have another department that applies incorrect buffers (too much or too little safety stock), then a lot of the benefit of a more accurate forecast goes out the window.  You have to look holistically at forecasting within the context of inventory management. You can’t get maximum benefit (and in some cases, any benefit) unless you account for all components including buffer levels such as safety stock and reorder points, ordering rules, and managing supplier/internal lead times. It is not uncommon for buyers to implement rules of thumb inventory policies such as ordering early or inflating the forecast to reduce the risk of running out.  The opposite behavior where an order signal triggered by the forecast is deferred to a later date to prevent an order from being placed “too early” is equally prevalent.  This type of behavior is based on a pain avoidance response that occurs within companies that have an ad-hoc inventory planning process that doesn’t holistically connect the forecast to inventory strategy.  

4. The more forecasting models the better.

 This is true in some cases. In an ironic twist, the more models to choose from sometimes means you’ll have a greater chance of picking the wrong one.  This occurs even when there is an automated system selecting the right method.  This is because most automated forecasting systems still make the mistake of selecting methods based on best fit to past demand. This backward-looking approach usually results in poor performance when looking forward in time; this can be tested by waiting a bit and then comparing forecasted versus actual demand (or, if you don’t want to wait, by hiding some of the recent data and forecasting it, in which case the actuals are already in hand). In principle, having more models might be useful, but what is important is understanding the approach for model selection.  Furthermore, most forecasting models produce a single-number forecast (“Demand for Product A will be 17 units next month”) without any indication of the forecast uncertainty or margin of error. Without knowing the margin of error, you cannot appreciate and rationally manage forecast risk.

In our software, we offer automated time series selection that chooses from dozens of proven techniques on the basis of estimated future performance, not fit to past data.  We also go beyond single-number forecasting using probabilistic methods to generate thousands of forecast scenarios to assess forecast uncertainty.  We’ve found that this approach is considerably more accurate for certain types of data than the traditional tournament selection.  So, in these situations the number of models we’d recommend using is “One!”  Does that it make inferior?  Of course not.  Take the time to fine-tune your models in order to see what works best for your business.

5. With the right software, anybody can do the job well.

Would that it were so. However, after our involvement in decades of implementations, it is clear that not everybody should be at the demand planning keyboard. The job doesn’t need a super-hero, but certain traits make for success:

• Having a company-wide perspective. So many problems in demand planning stem from stove-piped thinking. A proper planning process surfaces the need for all stakeholders’ involvement, so a user unable to think beyond his or her previous fiefdom can be a liability.
• Being innumerate. A user who is not comfortable with numbers will struggle.
• Appreciating randomness. This is similar to innumeracy but goes beyond. Most of the friction in demand planning and inventory optimization derives from randomness: in product demand, in supplier lead time, etc. Without a good feel for how randomness causes trouble, a user will often be puzzled at how poorly his or her decisions turn out
• Being incurious. Top-flight software encourages users to game out “what if?” scenarios to see how to tweak automatically computed solutions to get even better results. If the user never gets into a “what if?” mentality, they will under perform. Furthermore, playing with alternative scenarios is one of the best ways to build an instinctive feel for the randomness in the system.

Conclusion

The five reasons outlined here show why implementing a forecasting, demand planning, or inventory optimization system isn’t as simple as turning on the software, importing your historical data, and getting some user training on how to operate the software.  You are implementing a new process for planning your business and determining stocking policy that will drive spending on inventory and impact your ability to capture sales.  However, the effort is well worth it.  Per an Institute of Business Forecasting (IBF) blog, a 1% reduction in under-forecast error at a $50 Million company yields a savings as much as $1.52M.  Conversely, the benefits of a 1% reduction in over-forecast error were $1.28M yielding an average benefit of $1.4M.  This means you stand to save your business $260,000 annually for every $10 Million in revenue! 

You can’t properly manage your inventory levels, let alone optimize them, if you don’t have a handle on exactly how demand forecasts and stocking parameters (such as Min/Max, safety stocks, and reorder points, and order quantities) are determined.

Many organizations cannot specify how policy inputs are calculated or identify situations calling for management overrides to the policy.   For example, many people can say they rely on a particular planning method such as Min/Max, reorder point, or forecast with safety stock, but they can’t say exactly how these planning inputs are calculated.  More fundamentally, they may not understand what would happen to their KPI’s if they were to change Min,Max, or Safety Stock. They may know that the forecast relies on “averages” or “history” or “sales input”, but specific details about how the final forecast is arrived at are unclear.

Often enough, a company’s inventory planning and forecasting logic was developed by a former employee or vanished consultant and entombed in a spreadsheet.  It otherwise may rely on outdated ERP functionality or ERP customization by an IT organization that incorrectly assumed that ERP software can and should do everything. (Read this great and, as they say, “funny because it’s true,” blog by Shaun Snapp about ERP Centric Strategies.)  The policy may not have been properly documented, and no one currently on the job can improve it or use it to best advantage.

This unhappy situation leads to another, in which buyers and inventory planners flat out ignore the output from the ERP system, forcing reliance on Microsoft Excel to determine order schedules.  Ad hoc methods are developed that impede cohesive responses to operational issues and aren’t visible to the rest of the organization (unless you want your CFO to learn the complex and finicky spreadsheet).  These methods often rely on rules of thumb, averaging techniques, or textbook statistics without a full understanding of their shortcomings or applicability.  And even when documented, most companies often discover that actual ordering strays from the documented policy.  One company we consulted for had on hand inventory levels that were routinely 2 x’s the Max quantity!  In other words, there isn’t really a policy at all.

In summary, many current inventory and demand forecast “systems” were developed out of distrust for the previous system’s suggestions but don’t actually improve KPI’s.  They also force the organization to rely on a few employees to manage demand forecasting, daily ordering, and inventory replenishment.

And when there is a problem, it is impossible for the executive team to unwind how you got there, because there are too many moving parts.  For example, was the excess stock the fault of an inaccurate demand forecast that relied on an averaging method that didn’t account for a declining demand?  Or was it due to an outdated lead time setting that was higher than it should’ve been?  Or was it due to a forecast override a planner made to account for an order that just never happened?  And who gave the feedback to make that override?  A customer? Salesperson?

Do you have any of these problems?  If so, you are wasting hundreds of thousands to millions of dollars each year in unnecessary shortage costs, holding costs, and ordering costs.  What would you be able to do with that extra cash?  Imagine the impact that this would have on your business.

This blog details the top 10 questions that you can ask in order 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.

Most demand forecasts are partial or incomplete: They provide only one single number: the most likely value of future demand. This is called a point forecast. Usually, the point forecast estimates the average value of future demand.  Interval forecasts provide an estimate of the possible future range of demand (i.e. demand has a 90% chance of being between 50 – 100 units).  Probabilistic forecasts take it a step further and provide additional information.  Knowing more is always better than knowing less and the probabilistic forecast provides that extra information so crucial for inventory management. This video blog by Dr. Thomas Willemain explains each type of forecast and the advantages of probabilistic forecasting.

[inbound_button font_size=”20″ color=”#00a429″ text_color=”#ffffff” icon=”” url=”http://www.screencast.com/t/Ut4I5dOY8″ width=”” target=”_blank”]Watch Now[/inbound_button]
 

Point forecast (green) shows what is most likely to happen.  The Interval Forecast shows the range (blue) of possibilities.

Probability Forecast shows the probability of each value occurring