Posts Tagged ‘MAPE’

Calculating MAPE – special cases: Obsolete Stock

Friday, February 5th, 2010

When calculating MAPE what is recommended when actuals are positive but forecast is 0 (for example when clearing obsolete stock)?  Can you make the forecast match the actual quantity so as not to penalize the forecaster for something that was not forecastable. Is this the correct way to measure these scenarios?

Our recommendation is to exclude the Obsolete Skus from measurement and in computing the aggregate MAPE as a performance measure for the planner or for the Sales Manager responsible.  Clearing obsolete stock is a supply management activity not a demand forecasting activity.

Demand Plans are externally focused and are a representation of what the market wants.  The obsolescence of stock may be a result of inferior demand forecasting in the past but has nothing to do with the demand for such stock in the current period.  In essence, there is no demand for that stock – either it is sold for scrap or just donated.

Making the Forecasted quantity match the actual demand for such obsolete stock will have a downside as well.  This will artificially inflate the forecast performance of the planner on a weighted basis and hence hide poor forecasting on active open stock items.

For example, you sell 25K units of active SKU for which you forecasted only 5K.  Then you have 100K of obsolete stock you sell.   Under your measure the MAPE will result in a 16% error or an 84% accuracy.  In reality the MAPE on your active SKU is 80% or 20% accuracy.  The 100% accuracy on the obsolescence is a manufactured number but wrongly aggregates to influence the divisional MAPE.

Forecast Alerts

Thursday, August 20th, 2009

Popular software packages have forecast alert monitors. Each software may term it differently:

  1. Manugistics calls them lists
  2. APO and Dematra call them as alerts

An overworked demand planner typically plans in the order of 1000+ skus each month.  That is where these alerts come in handy.  You set a pre-determined alert based on the condition meeting a threshold……. Voila!  As soon as the month-end job runs and re-creates the models, the alerts kick in and do their job.

You get a report, perhaps emailed to you at night comprised of all those items that exceeded your threshold.  Then your job becomes a tad easier.  You walk in to the office with your day planned out thinking to yourself:

“I am going to address those 45 SKUs that show a MAPE above 30% first, then address the next 100 that are above 20%”.

Typically the alerts are set using a comparison of new model values to the in-sample historical values.  In essence, they address the model fit issue and alert you to specific situations where the models are insufficient or just plain wrong.  Quite possibly, the history may have an anamoly as well.

Now ironically I have seen many planners complain that they are getting too many alerts from the software making them practically not very useful.  One planner mentioned that his system was spitting out 9000 alerts for a total of 1000 skus?!

This only underscores the importance of thresholds and correct definitions.  If you note this cardinal rule, then you will be well on your way to leveraging the exception capabilities of your software:

  1. Automated alert measures can only be set for relative performance meausres – MPE, MAPE, or RMSE relative to Average demand, not for absolute measures such as MAD.
  2. The settings are just as good as your understanding of the business – the thresholds have to be reasonable in comparison to historical standards.

Also remember that Alerts can be used for another important monthly activity:  comparing the difference between two successive forecast runs.  DemandPlanning.Net calls it the Delta ratio.  Perhaps you are interested in all items where the forecast delta is 25% or above!

Until next time,

Mark C

    Is MAPE controversial?

    Friday, July 10th, 2009

    MAPE = Mean Absolute Percent Error.  This is the common error measure used by the Supply Chain profession.  Demand Planners and Demand Forecasters spread across the manufacturing sector use MAPE to measure the performance of their demand forecasts.  This is used cross-sectionally across several items or SKUs for the previous month using a forecast that was created a few months earlier (1, 2, 3 or even 6 month lags are possible).
    However, there is raging debate over what to use in the denominator while calculating this sacro-sanct MAPE measure.
    Traditional MAPE measure = (Absolute Error)/Actual demand.
    Why dont we divide the error by forecast value instead of dividing by Actual sales?  This also introduces a potential forecasting bias.  To reduce MAPE, the planner can actually over-forecast.
    Here is what we need to keep in mind:
    1.  Whatever we use as denominator, we need to be consistent across the score-card, division, and company as a whole. So the denominator does NOT depends on the level.  It needs to be the same across everything.

    2.  Zero demand may result in an ugly “DivbyZero” error in Excel when you use Actuals as the denominator. The practical solution is to set the error percent to a high number such as 9999%. Note the error is not Zero!! Mathematically the error is infinite (but infinity is not a practical supply chain concept).

    3.  Setting the individual item error as a high number when demand is zero, should not affect the overall MAPE, since the overall MAPE is NOT a simple average of individual MAPEs.

    4.  The denominator problem disappears if in general forecast errors are lower, that is when Forecast is closer to the Actuals; but note that most supply chain issues and demand side biases also disappear when forecast error is smaller!

    5. The point is planners/managers/companies should spend less time worrying/arguing about how large the error is when the error exceeds a certain threshold say 50-60%. Although mathematically it matters between 90% and 900%, from a supply chain perspective a 90% error is disastrous! A 900% error is just plain silly and perhaps shows either there is a metrics process flaw or we are chasing after the wrong rat!

    6. In summary, we can definitely perform sensitivity analysis on how the division performance will change based on a denominator change. In some instances we have even used the mid-point between actual and forecast. There is a potential to underforecast when the denominator is Actuals.  So you can use a mid-point to what is called as the Symmetric MAPE.

    7. Calculating with reference to the Budget is a good practice to measure the attainment of sales goals with reference to the plan targets – so using Budget as the denominator makes sense for measuring sales force performance.  However, note that this is not absolute error in the sense of MAPE and we are answering a different question. So we should stay away from this confusion.