Skip to main content
Apr 26, 2017 1:20 AM UTC
Question

Forecast Accuracy Reporting

How do you people currently report Forecast Error/ Accuracy?  How do you bucket it ?

What parts do you report it on - only the planned parts or on all the parts ? 

What metric do you use: Forecast error %, MAD, RMSE, MAPE, Tracking signal or Bias ?

We have about 5 million part numbers in our system but we plan only for about 5000 pairs in total maybe , so doesn't make sense to report forecast accuracy on those parts, so I am trying to see what other companies / industries are doing. 

The data we can use is ipcs_forecasted_data.forecastamount and ipcs_demand_history.historyamount  will give you the recorded forecast & the actual demand history for a month when you join by partid, locid & historybegdate and forecastslicedate


Looking at the Demand Planning Cycle the first step is forecasting - pretty much with SVG under time phased planning - your forecast drives the parts that are being planned


Thanks

Regards

Natarajan J


2 replies

May 5, 2017 3:37 AM UTC

Forecasting accuracy (FA) comes in with a lot of variety.

each industry uses its own norms for forecast accuracy. sometimes even within an industry, clients prefer different ways to measure the FA.

i will share what i have experienced- we used to archive the latest forecast calculation for current month; archived in monthly buckets. (you can archive at pair level, or stream pair level or product level if using SEM)

we then used several logics to compare the forecast generated over different buckets.

Some clients prefer to have  ahigh level analysis- say forecast accuracy by part type/ class. So it need not be always the most granular level of pair-stream. tricky question is how to roll up FA from a granular level to a higher level. this is where a lot of logics come in. for example we had this logic that for some part class, a forecast vs actual difference of +-2 units is still a success, and we rolled it to a higher level as a success.

May 11, 2017 11:21 PM UTC

Thanks for sharing your experience and ideas Atul !