Does Your Demand Planning Process Include a “Quantitative Sanity Range Evaluation”?

There is a process that should be part of both your demand planning and your sales and operations planning.  The concept is simple – how do you find the critical few forecasts that require attention, so that planner brainpower is expended on making a difference and not hunting for a place to make a difference?  I have heard this process called a “Forecast Reality Check” and a “Forecast Reasonability Check”.  Just to be difficult, I’ll call it a Quantitative Sanity Range Evaluation (I have my own reasons.)  It may be similar in some ways to analyzing “forecastability” or a “demand curve analysis”, but different in at least one important aspect – the “sanity range” is calculated through bootstrapping (technically, you would be bootstrapping a confidence interval, but please allow me the liberty of a less technical name – “sanity range”).  A QSRE can be applied across industries, but it’s particularly relevant in consumer products, where I have seen a version of this implemented first hand by Allan Gray, a really smart gentleman – back when I worked with him for End-to-End Analytics – just so you know I didn’t think this all up on my own!

At a minimum, QSRE must consider the following components:

  1. Every level and combination of the product and geographical hierarchies
  2. A quality quantitative forecast
  3. A sanity range out through time
  4. Metrics for measuring how well a point forecast fits within the sanity range
  5. Tabular and graphical displays that are interactive, intuitive, always available, and current.

If you are going to attempt to establish a QSRE, then I would suggest five best practices:

1.  Eliminate duplication.  When designing a QSRE process (and supporting tools), it is instructive to consider the principles of Occam’s razor as a guide:

– The principle of plurality – Plurality should not be used without necessity

– The principle of parsimony – It is pointless to do with more what can be done with less

These two principles of Occam’s razor are useful because the goal is simply to flag unreasonable forecasts that do not pass a QSRE, so that planners can focus their energy on asking critical questions only about those cases.

2. Minimize human time and effort by maximizing the power of cloud computing.  Leverage the fast, ubiquitous computing power of the cloud to deliver results that are self-explanatory and always available everywhere, providing an immediately understood context that identifies invalid forecasts. 

3. Eliminate inconsistent judgments By following #1 and #2 above, you avoid inconsistent judgments that vary from planner to planner, from product family to product family, or from region to region.

4. Reflect reality.  Calculations of upper and lower bounds of the sanity range should reflect the fact that uncertainty grows with each extension of a forecast into a future time period.  For example, the upper and lower limits of the sanity range for one period into the future should usually be narrower than the limits for two or three periods into the future.  These, in turn, should be narrower than the limits calculated for more distant future periods.  Respecting reality also means capturing seasonality and cyclical demand in addition to month-to-month variations.  A crucial aspect of respecting reality involves calculating the sanity range for future demand from what actually happened in the past so that you do not force assumptions of normality onto the sanity range (this is why bootstrapping is essential).  Among other things, this will allow you to predict the likelihood of over- and under-shipment.

5. Illustrate business performance, not just forecasting performance with sanity ranges.  The range should be applied, not only from time-period to time period, but also cumulatively across periods such as months or quarters in the fiscal year.

If you are engaged in demand planning or sales and operations planning, I welcome to know your thoughts on performing a QSRE.

Thanks again for stopping by Supply Chain Action.  As we leave the work week and recharge for the next, I leave you with the words of John Ruskin:

“When skill and love work together, expect a masterpiece.”

Have a wonderful weekend!

Advertisements

Forecasting vs. Demand Planning

Often, the terms, “forecasting” and “demand planning”, are used interchangeably. 

The fact that one concept is a subset of the other obscures the distinction. 

Forecasting is the process of mathematically predicting a future event.

As a component of demand planning, forecasting is necessary, but not sufficient.

Demand planning is that process by which a business anticipates market requirements.  

This certainly involves both quantitative and qualitative forecasting.  But, demand planning requires holistic process that includes the following steps:

1.      Profiling SKU’s with respect to volume and variability in order to determine the appropriate treatment:

For example, high volume, low variability SKU’s will be easy to mathematically forecast and may be suited for lean replenishment techniques.  Low volume, low variability items maybe best suited for simple re-order point.  High volume, high variability will be difficult to forecast and may require a sophisticated approach to safety stock planning.  Low volume, low variability SKU’s may require a thoughtful postponement approach, resulting in an assemble-to-order process.  This analysis is complemented nicely by a Quantitative Sanity Range Evaluation, which should be an on-going part of your forecasting process.

2.       Validating of qualitative forecasts from among functional groups such as sales, marketing, and finance
3.       Estimation of the magnitude of previously unmet demand
4.       Predicting underlying causal factors where necessary and appropriate through predictive analytics
5.       Development of the quantitative forecast including the determination of the following:

  • Level of aggregation
  • Correct lag
  • Appropriate forecasting model(s)
  • Best settings for forecasting model parameters
  • Deducting relevant consumption of forecast

6.      Rationalization of qualitative and quantitative forecasts and development of a consensus expectation
7.      Planning for the commercialization of new products
8.      Calculating the impact of special promotions
9.      Coordinating of demand shaping requirements with promotional activity
10.    Determination of the range and the confidence level of the expected demand
11.    Collaborating with customers on future requirements
12.    Monitoring the actual sales and adjusting the demand plan for promotions and new product introductions
13.    Identification of sources of forecast inaccuracies (e.g. sales or customer forecast bias, a change in the data that requires a different forecasting model or a different setting on an existing forecast model, a promotion or new product introduction that greatly exceeded or failed to meet expectations).

The proficiency with which an organization can anticipate market requirements has a direct and significant impact on revenue, margin and working capital, and potentially market share.  However, as an organization invests in demand planning, the gains tend to be significant in the beginning of the effort but diminishing returns are reached much more quickly than in many other process improvement efforts.

This irony should not disguise the fact that significant ongoing effort is required simply to maintain a high level of performance in demand planning, once it is achieved.

It may make sense to periodically undertake an exercise to (see #1 above) in order to determine if the results are reasonable, whether or not the inputs are properly being collected and integrated, and the potential for additional added value through improved analysis, additional collaboration, or other means.

I’ll leave you once again with a thought for the weekend – this time from Ralph Waldo Emerson:

“You cannot do a kindness too soon, for you never know how soon it will be too late.”

Thanks for stopping by and have a wonderful weekend!

Metrics, Symptoms and Cash Flow

Metrics can tell us if we are moving in the right or wrong direction and that, in itself, is useful.  However, metrics by themselves do not help us assess our competitive position or aid us in prioritizing our efforts to improve.

To understand our competitive position, metrics need to be benchmarked against comparable peers. Benchmarking studies are available, some of them free.  They tell us where we stand relative to others in the industry, provided the study in question has sufficient other data points from your industry (or sub-industry segment).

Many times, getting relevant benchmarks proves challenging.  But once we have the benchmarks, then what?

Does it matter if we do not perform as well as the benchmark of a particular metric?  If that metric affects revenue growth, margins, return on assets, or available capital, it may matter significantly.

But, we are left to determine how to improve the metrics and with which metrics to start.  

Consider an alternative path.  Begin with the undesirable business symptoms that keep you up at night and give you that bad feeling in the pit of your stomach.

Relate business processes to symptoms and map potential root causes within each business process to undesirable business symptoms.

Multiple root causes in multiple business processes can relate to a single symptom.  On the other hand, a single root cause may be causing multiple undesirable symptoms.  Consequently, we must quantify and prioritize the root causes.

“Finding the Value in Your Value Network” outlines a straightforward, systematic approach to prioritizing and accelerating process improvements.  I hope you will take a look at that article and let me know your thoughts.

Thanks for having a read.  Remember that “You cannot do a kindness too soon, for you never know how soon it will be too late.”

Have a wonderful weekend!

Thoughts from IBF Conference

I just left the IBF’s Leadership Business Planning & Forecasting Forum and the Supply Chain Planning & Forecasting:  Best Practices Conference in Orlando, Florida.  I’ll share a few of the thoughts that struck me as helpful here in the hopes that they will help you.

From a panel discussion on organizational design at the Forum, I compiled this key point (adding in my own twist):   S&OP is all about integrated decision-making, understanding inter-related tradeoffs, driving toward bottom-line metrics with cause/effect accountability.

Rick Davis from Kellogg pointed out that  “Integrated planning is less about function than about process.

Rick also emphasized managing the inputs, particularly since data and technology are moving at the “speed of mind”.  Decision-makers need to ask themselves, “Will competitors leverage information better than I will?”

A few keys to success in S&OP include the following (see Ten Sins of S&OP for what NOT to do):

1)      Scenario analysis

2)      Leadership buy-in

3)      Quality feeder processes (my point of view)

4)      Remembering that financial targets and demand plans are different

Rafal Porzucek defined supply chain agility this way:  “The speed to react with predictable costs and service delivery.”  I thought that was pretty good.

The consumer products executives felt that the effort to leverage social media for forecasting was in the data collection phase.  In a couple of years, it may be useful for generating more accurate forecasts.

Mark Kremblewski and Rafal Porzucek from P&G made a compelling case for enabling innovation through standardization – and it made great sense.

Mark also shared a profound understanding of how the key numbers of business objective, forecast and actual shipments relate to each other.

I hope some of these points stimulate your thinking as they did mine.

There were other speakers who shared some great insights.  The absence of mention here is not meant to diminish their contribution.

This week, in the theme of anticipating the future, I leave you with the words of the English novelist and playwright, John Galsworthy, who won the 1932 Nobel Prize in Literature, “If you do not think about the future, you cannot have one.

Have a wonderful weekend!

Protected: Five Best Practices for a Demand Plan Sanity Check

This content is password protected. To view it please enter your password below:

An S&OP Insignt in 45 Seconds

I decided, in the end, to make a post this Friday, but of a slightly different nature.  Click on the picture to watch 45 seconds of my interview with Supply Chain Brain from September.  This may be something you haven’t thought about before.  

Thanks again for stopping by. 

For those in the U.S., I hope that you and yours are enjoying a really good Thanksgiving time.

My Thoughts from the IBF Leadership Conference in Las Vegas

Although it is not yet Friday, I want to take this opportunity to share my thoughts on what I heard at the Institute of Business Forecasting and Planning’s Leadership Business Planning and Forecasting Forum.  I was privileged to spend a couple of days with a rather distinguished group of practitioners, software vendors, academics, and consultants exploring three major areas of interest to most supply chain managers and planners – best practices in Leveraging Integrated Demand Signals, Sales and Operations Planning and Demand Planning.  I managed to leave my notes in my hotel room, but here are a few of my thoughts in no particular order that you may find immediately useful (some completely original, some borrowed, some modified from something I heard):

  • Make use of syndicated data as a leading indicator.  More and more of this is available.  Determine what is available and match it to your business needs, leveraging econometric models.
  • Collaboration is still partly a function of bargaining position.
  • Before you collaborate, make sure you have done your analytical homework so that you understand the total opportunity and how much you need to capture and how much you can afford to give away.
  • A “forecastability” or “reasonability” analysis allows demand planners to be more efficient by highlighting areas where they can engage their education, training, and experience rather than sifting through data is becoming a best practice. 
  • Two key performance indicators that might not have been in your textbook probably ought to be part of your demand planning process:

              √ Forecast Value Added (mean absolute percentage error for new forecast approach  – mean absolute percentage error for old (or possibly naive) forecast approach)

              √ Cost of Inaccuracy (margin and lost goodwill * units underforecasted less safety stock) + (cost of holding inventory * units overforecasted) all summed over the relevant time period

  • Consider engaging finance in the demand planning process.
  • Know the difference between your financial or sales objective and the demand plan.
  • Many companies struggle with the harmonizing of qualitative and quantitative forecasting.  A generally helpful concept here is that qualitative input tends to be best from a top-down  perspective and allocated down;  quantitative forecasting tends to be at a lower, if not the lowest level and rolled up.
  • Forecast both shipments and end-customer consumption and the difference.  In  the consumer goods industry, this is essentially “trade inventory”.
  • Microsoft Excel is still the predominant planning software.  It is how people and organizations innovate quickly.  However, building models in Excel, itself, is problematic in terms of scale, maintenance and process standardization.  A useful improvement would be getting IT or a consultant to create your model in Visual Basic, leveraging Excel as the user interface. 
  • Enterprise software is useful, but customers and users need to demand more from their software vendors.
  • Fit both your model and your metrics to the nature of the business and the data.

While we are on the topic, allow me to also point you to my blog post of a few days ago (September 9) where I outline some of the differences between forecasting per se and a robust demand planning process.

%d bloggers like this: