Making the Best Use of Alerts in Forecasting
Last week I got the opportunity to present to the Oracle Retail User Group on the topic of Managing by Exception in Oracle Retail Demand Forecasting (RDF). The one topic that seemed to resonate the most in this area was the concept of using what I referred to as a Master Alert.
The premise behind the Master Alert is based on these principles:
- One alert/exception rule that combines all other key rules/exceptions
- The ability for a user to easily turn on and off which rules/exceptions are used in this master alert
- The ability to control the frequency of when the alert will next need to be checked
- The ability to sort/rank the product/location level forecasted by a key magnitude metric
Before I dig in, it’s important to note that I use exception and alert interchangeably to mean some type of defined rule or check that then produces a flag or notification within the system to pinpoint the user to troubled and/or out-of-tolerance occurrences. So yes, let’s dig in.
Those in retail that forecast/plan their business down at the Item/Store or SKU/Store level know that there are by far too many combinations for even a well staffed forecasting organization to review each forecast on a regular basis. In the good old days, when Ms. Pac-man was considered to have amazing graphics and forecasting systems ran on less disk space than that found on today’s iPod, the decision was made easy for us; forecast and manage our products at rolled-up/aggregate levels along the product or location hierarchy. And even at these aggregate levels with checks and balances in place to review and manage the profiles and forecasts, it still could be an overwhelming task. Read the rest of the article »

