Home » 2008 » July

We welcome Noha Tohamy of AMR Reaserch on August 26 for our next Best Practice Leardership Forum Web Seminar.  Hope you can join us as Noha summarizes the results of the resent study where Steelwedge has been identified as the Pure Play S&OP vendor.  For more information and to register simply click the link below.

http://www.steelwedge.com/news/index.php?z=events

Working Together: Bottom Up and Top Down Forecasting

Posted by Rick Blair | July 29, 2008 | Categories: Sales Forecasting

An effective S&OP program depends on solid, accurate demand forecasts. Best practice companies do three things well: statistical, top-down and bottom-up forecasting. Many companies are doing one or two of these, but few are doing all three well. Of course, some companies do none. Let’s just say these companies have a huge upside improvement potential.

A statistically generated forecast should use a “best fit” approach to select the mathematical algorithm that minimizes error (using mean absolute percentage error (MAPE)). The statistical engine should select the best algorithm for each time-phased data series or set of regression data. The resulting forecast should serve as a starting point for bottom-up and top-down forecasts.

Bottom-up forecasts are accumulated from many contributors. A distributed sales force may have hundreds or thousands of contributors. Each contributor has a specific area of expertise such as a specific customer, product or geographic area. The contributor enters her forecasts for her specific area of responsibility. Forecasts from all contributors are summed to capture an overall bottom-up forecast.

Conversely, a top-down approach applies a more centralized view. A small number of forecasters will look at various inputs and generate forecasts. Influencing factors may include market data, economic indicators, and general product and customer trends. Here, too, the statistically generated forecast is a good number from which to start.

The beauty of top-down and bottom-up forecasts is their ability to look at the world from differing vantage points. The folks in the “ivory tower” know important information, but they don’t know everything. The folks in the field have keen insights into their unique areas, but they only see their small piece. The challenge is to capture the small pieces without tainting the field forecaster’s view. In other words, don’t tell the field forecasters

The concept of a Planning Bill of Material (PBOM) has been around for many years to manage the relationships between independent and dependant demand items. Planning BOMs are used to forecast demand for components and options available for configured products. For example, a configured laptop may have an option for a wireless card that is either specified at order entry or purchased as part of an end item off the shelf. In this case, the attach rate is a function of how often the wireless card is purchased when a laptop is purchased. Another example might be the RAM option for a computer. In this example, RAM is included in all laptops, however, the consumer has an option to select a certain quantity of RAM (e.g. 128, 512, 1.2…). In the case of RAM, the attach rate represents the percentage of time each quantity of RAM is selected when a laptop is purchased and the attach rate for the different options of RAM must add to 1.

One of the advantages using PBOM is the ability to streamline and reduce complexity in the planning process so that rather than plan for multiple end items and components, planners can focus there attention on forecasting more aggregate level platforms or product groups and use attach rates to forecast the component level details associated with the platforms. Another benefit of using a PBOM is to improve the overall accuracy of the forecast. In many cases the actual demand level for component/options may be relatively low which makes it difficult to accurately forecast demand. Forecast accuracy at the aggregate level tends to be higher compared to component/option levels since volumes are relatively larger which results in higher accuracy using statistical methods. Once the aggregate level is determined, attach rates

Integrated Business Planning is poised to become the next big thing beyond S&OP. One of the key themes for IBP is linking Operational Plans to Financial Plans.  This linkage enables companies to understand how financial budgets and assumptions can impact operational plans and execution and visa versa.  One of the fundamental requirements for linking financial and operational plans is the ability to translate between units and revenues/margins.  This is certainly easier said than done.  As companies are faced with variable customer-specific pricing structures, rapidly changing prices, cost and promotional activities, simply using a static average selling price and COGS does not provide the level of accuracy needed to understand the true relationship between units and revenue.

One of the key differentiators in the Steelwedge solution is the ability to translate plans between units and renveues.  Steelwedge provides the ability to manage pricing information at various levels in a product hierarchy required to capture the true relationship between operational plans and revenue projections.  In addition, Steelwedge provides the ability to model pricing and cost information in a time-phased manner.  Once the operational plans are translated into revenue and margin projections, finance, operations and sales can begin to compare and reconcile plans on a periodic and exception basis.

To achieve the vision of IBP, companies must have the approporiate enabling technology to perform the basic building blocks for planning.  Accurate unit to revenue conversions is one of many building block that must be done well to realize the vision of IBP.

Integrated Business

Integrated Business Planning is poised to become the next big ...

How to Ensure Sales

Based on feedback from customers regarding the deep expertise the ...

How “One-Click-Pla

Steelwedge Software today announced a new product release ...

privacy policy  | terms of use Blog