1. Built-in ERP functionality is baked into Order Management.

Consider what is meant by “demand management”, “demand planning”, and “forecasting”. These terms imply certain standard functionality for collaboration, statistical analysis, and reporting to support a professional demand planning process.  However, in most ERP systems, “demand management” consists of executing MRP and reconciling demand and supply for the purpose of placing orders, i.e., “order management.” It has very little to do with demand planning which is discrete process focused on developing the best possible predictions of future demand by combining statistical analysis with business knowledge of events, promotions, and sales force intelligence.   Most ERP systems offer little statistical capability and, when offered, the user is left with a choice of a few statistical methods that they either have to apply manually from a drop-down list or program themselves. It’s baked into the order management process enabling the user to possibly how the forecast might impact inventory.  However, there isn’t any ability to manage the forecast, improve the quality of the forecast, apply and track management overrides, collaborate, measure forecast accuracy, and track “forecast value add.” 

2. ERP planning methods are often based on simplistic rules of thumb.

ERP systems will always offer min, max, safety stock, reorder point, reorder quantity, and forecasts to drive replenishment decisions.  But what about the underlying methods used to calculate these important drivers?   In nearly every case, the methods provided are nothing more than rule-of-thumb approaches that don’t account for demand or supplier variability.  Some do offer “service level targeting” but mistakenly rely on the assumption of a Normal distribution (“bell-shaped curve”) which means the required safety stocks and reorder points recommended by the system to achieve the service level target are going to be flat out wrong if your data doesn’t fit the ideal theoretical model, which is often gravely unrealistic.  Such over-simplified calculations tend to do more harm than good.  

3. You’ll probably still use spreadsheets for at least 2 years after purchase.

Most often, if you were to implement a new ERP solution, your old data would be stranded.  So, any native ERP functionality for forecasting, setting stocking policy such as Min/Max, etc., cannot be used, and you will be forced to revert back to cumbersome and error-prone spreadsheets for at least two years (one year to implement at earliest and another year to collect at least 12 months of history).  Hardly a digital transformation.  Using a best-of-breed solution avoids this problem.  You can load data from your legacy ERP system and not disrupt your ERP deployment.  This means that on Day 1 of ERP go-live you can populate your new ERP system with better inputs for demand forecasts, safety stocks, reorder points, and Min/Max settings.

4. ERP isn’t designed to do everything

The “Do everything in ERP/One-Vendor” mindset was a marketing message promoted by ERP firms, particularly SAP, to get you, the customer, to spend 100% of your IT budget with them.  That marketing message has been parroted back to users by analyst groups, IT firms, and systems integrators, drowning out rational voices who asked “Why do you want to be so dependent on one firm to the point of using inferior forecasting and inventory planning technology?”  The sheer number of IT failures and huge implementation costs have caused many companies to rethink their approach to ERP.  With the advent of specialized planning apps born in the cloud with no IT footprint, the way to go is a “thin” ERP focused on the fundamentals – accounting, order management, financials – but supported by specialized planning apps. 

The expertise of ERP consultant’s lies in how their system is designed to automate certain business processes and how the system can be configured or customized.   Their consultants are not specialists in on proper approaches to planning stock, forecasting, and inventory planning.  So if you are trying to understand what demand planning approach is right for your business, how should you buffer properly, (e.g., “Should we do Min/Max or forecast-based replenishment?” “Should we use forecasting method X?”), you generally aren’t going to find it and if you do that resource will be spread quite thin. 

There’s a stale old joke: “There are two types of people – those who believe there are two types of people, and those who don’t.” We can modify that joke: “There are two types of people – those who know there are three types of supply chain analytics, and those who haven’t yet read this blog.”

The three types of supply chain analytics are “descriptive”, “predictive”, and “prescriptive.” Each plays a different role in helping you manage your inventory. Modern supply chain software lets you exploit all three.

Descriptive Analytics

Descriptive Analytics are the stuff of dashboards. They tell you “what’s happenin’ now.” Included in this category are such summary numbers as dollars currently invested in inventory, current customer service level and fill rate, and average supplier lead times. These statistics are useful for keeping track of your operations, especially when you track changes in them from month to month. You will rely on them every day. They require accurate corporate databases, processed statistically.

Predictive Analytics

Predictive Analytics most commonly manifest as forecasts of demand, often broken down by product and location and sometimes also by customer. These statistics provide early warning so you can gear up production, staffing and raw material procurement to satisfy demand. They also provide predictions of the effect of changes in operating policies, e.g., what happens if we increase our order quantity for Product X from 20 to 25 units? You might rely on Predictive Analytics periodically, perhaps weekly or monthly, when you look up from what’s happening now to see what will happen next. Predictive Analytics uses Descriptive Analytics as a foundation but adds more capability. Predictive Analytics for demand forecasting requires advanced statistical processing to detect and estimate such features of product demand as trend, seasonality and regime change.  Predictive Analytics for inventory management uses forecasts of demand as inputs into models of the operation of inventory policies, which in turn provide estimates of key performance metrics such as service levels, fill rates, and operating costs.

Prescriptive Analytics

Prescriptive Analytics are not about what is happening now, or what will happen next, but about what you should do next, i.e., they recommend decisions aimed at maximizing inventory system performance. You might rely on Prescriptive Analytics to best posture your entire inventory policy. Prescriptive Analytics uses Predictive Analytics as a foundation then adds optimization capability. For instance, Prescriptive Analytics software can automatically work out the best choices for future values of Min’s and Max’s for thousands of inventory items. Here, “best” might mean the values of Min and Max for each item that minimize operating cost (the sum of holding, ordering, and shortage costs) while maintaining a 90% floor on item fill rate.

Example

The figure below shows how supply chain analytics can help the inventory manager. The columns show three predicted Key Performance Indicators (KPI’s): service level, inventory investment, and operating costs (holding costs + ordering costs + shortage costs).

 Figure 1: The three types of analytics used to evaluate planning scenarios

The rows show four alternative inventory policies, expressed as scenarios. The “Live” scenario reports on the values of the KPI’s on July 1, 2018. The “99% All” scenario changes the current policy by raising the service level of all items to 99%. The “75 floor/99 ceiling” scenario raises service levels that are too low up to 75% and lowers very high (i.e., expensive) service levels down to 95%. The “Optimization” scenario prescribes item specific service levels that minimizes total operating costs.

The “Live 07-01-2018” scenario is an example of Descriptive Analytics. It shows the current baseline performance. The software then allows the user to try out changes in inventory policy by creating new “What If” scenarios that might then be converted to named scenarios for further consideration. The next two scenarios are examples of Predictive Analytics. They both assess the consequences of their recommended inventory control policies, i.e., recommended values of Min and Max for all items. The “Optimization” scenario is an example of Prescriptive Analytics because it recommends a best compromise policy.

Consider how the three alternative scenarios compare to the baseline “Live” scenario. The “99% All” scenario raises the item availability metrics, increasing service level from 88% to 99%. However, doing so increases the total inventory investment from $3 million to about $4 million. In contrast, the “75 floor/99 ceiling” scenario increases both service level and reduces the cash tied up in inventory by about $300,000. Finally, the “Optimization” scenario achieves an 80% service level, a reduction from the current 88%, but it cuts more than $2 million from the inventory value and reduces operating costs by more than $400,000 annually. From here, managers could try further options, such as giving back some of the $2 million savings to achieve a higher average service level.

Summary

Modern software packages for inventory planning and inventory optimization should offer three kinds of supply chain analytics: Descriptive, Predictive, and Prescriptive. Their combination lets inventory managers track their operations (Descriptive), forecast where their operations will be in the future (Predictive), and optimize their inventory policies in response in anticipation of future conditions (Prescriptive).

There’s a stale old joke: “There are two types of people – those who believe there are two types of people, and those who don’t.” We can modify that joke: “There are two types of people – those who know there are three types of supply chain analytics, and those who haven’t yet read this blog.”

The three types of supply chain analytics are “descriptive”, “predictive”, and “prescriptive.” Each plays a different role in helping you manage your inventory. Modern supply chain software lets you exploit all three.

Descriptive Analytics

Descriptive Analytics are the stuff of dashboards. They tell you “what’s happenin’ now.” Included in this category are such summary numbers as dollars currently invested in inventory, current customer service level and fill rate, and average supplier lead times. These statistics are useful for keeping track of your operations, especially when you track changes in them from month to month. You will rely on them every day. They require accurate corporate databases, processed statistically.

Predictive Analytics

Predictive Analytics most commonly manifest as forecasts of demand, often broken down by product and location and sometimes also by customer. These statistics provide early warning so you can gear up production, staffing and raw material procurement to satisfy demand. They also provide predictions of the effect of changes in operating policies, e.g., what happens if we increase our order quantity for Product X from 20 to 25 units? You might rely on Predictive Analytics periodically, perhaps weekly or monthly, when you look up from what’s happening now to see what will happen next. Predictive Analytics uses Descriptive Analytics as a foundation but adds more capability. Predictive Analytics for demand forecasting requires advanced statistical processing to detect and estimate such features of product demand as trend, seasonality and regime change.  Predictive Analytics for inventory management uses forecasts of demand as inputs into models of the operation of inventory policies, which in turn provide estimates of key performance metrics such as service levels, fill rates, and operating costs.

Prescriptive Analytics

Prescriptive Analytics are not about what is happening now, or what will happen next, but about what you should do next, i.e., they recommend decisions aimed at maximizing inventory system performance. You might rely on Prescriptive Analytics to best posture your entire inventory policy. Prescriptive Analytics uses Predictive Analytics as a foundation then adds optimization capability. For instance, Prescriptive Analytics software can automatically work out the best choices for future values of Min’s and Max’s for thousands of inventory items. Here, “best” might mean the values of Min and Max for each item that minimize operating cost (the sum of holding, ordering, and shortage costs) while maintaining a 90% floor on item fill rate.

Example

The figure below shows how supply chain analytics can help the inventory manager. The columns show three predicted Key Performance Indicators (KPI’s): service level, inventory investment, and operating costs (holding costs + ordering costs + shortage costs).

 Figure 1: The three types of analytics used to evaluate planning scenarios

The rows show four alternative inventory policies, expressed as scenarios. The “Live” scenario reports on the values of the KPI’s on July 1, 2018. The “99% All” scenario changes the current policy by raising the service level of all items to 99%. The “75 floor/99 ceiling” scenario raises service levels that are too low up to 75% and lowers very high (i.e., expensive) service levels down to 95%. The “Optimization” scenario prescribes item specific service levels that minimizes total operating costs.

The “Live 07-01-2018” scenario is an example of Descriptive Analytics. It shows the current baseline performance. The software then allows the user to try out changes in inventory policy by creating new “What If” scenarios that might then be converted to named scenarios for further consideration. The next two scenarios are examples of Predictive Analytics. They both assess the consequences of their recommended inventory control policies, i.e., recommended values of Min and Max for all items. The “Optimization” scenario is an example of Prescriptive Analytics because it recommends a best compromise policy.

Consider how the three alternative scenarios compare to the baseline “Live” scenario. The “99% All” scenario raises the item availability metrics, increasing service level from 88% to 99%. However, doing so increases the total inventory investment from $3 million to about $4 million. In contrast, the “75 floor/99 ceiling” scenario increases both service level and reduces the cash tied up in inventory by about $300,000. Finally, the “Optimization” scenario achieves an 80% service level, a reduction from the current 88%, but it cuts more than $2 million from the inventory value and reduces operating costs by more than $400,000 annually. From here, managers could try further options, such as giving back some of the $2 million savings to achieve a higher average service level.

Summary

Modern software packages for inventory planning and inventory optimization should offer three kinds of supply chain analytics: Descriptive, Predictive, and Prescriptive. Their combination lets inventory managers track their operations (Descriptive), forecast where their operations will be in the future (Predictive), and optimize their inventory policies in response in anticipation of future conditions (Prescriptive).