This is part 2 of 3, as Seth Pacha, our demand planning guru outlines data integrity elements and system automation.
Data – clean and aligned to system configuration
- Do accurate lead-times exist with alignment to the planning system?
- Are correct suppliers established within the system?
- Are key fields for planning populated such as standard cost, lead-time, minimum buys, order multiple, packaging quantity, supersession, critical part indicator, bill of material for kitting, customer information, supplier information, etc.
- Are fields manually updated or driven by integration to WMS/ERP solutions? Integration is key between the inventory planning solution and the source of the master data. Establishing daily checks that monitor key fields for accurate data helps uncover the true source of the data as well as integration and process issues. For example, a simple job to look for circular supersessions might highlight issues with engineering or with master data teams.
System – proper configuration to drive 90-95% automation
- Are the lead-time components setup correctly? •Are planning horizons established properly when determining what to order?
- Do proper rules exist for determination of whether to plan the part in inventory?
- Does the understanding exist of how safety stock generates for each part?
- How frequently does the data refresh and does that align with the execution of the various system modules?
Some systems contain multiple, key configurations to execute properly. These key configurations need continuous review to see performance over time. If the system has “what-if” capability allowing the understanding of the results of changing these configurations before implementing into a live production environment, make sure the organization understands the full impact of the changes. Does the system project performance just for a given point in time or does the system highlight the expected performance for the next year? If a system does not have “what-if” capability, then building similar capability through a process is paramount. As an example, configurations that determine whether to plan the part in inventory or not are key in determining warehouse size and the size of the workforce. A process to review before making any changes to this key configuration is a great sanity check for operations as well as purchasing. Finally, comparing the system results to the expected value proposition from the system provider is also necessary. Make sure before purchase that the provider derives the value proposition from actual data, not generic results from similar clients. This establishes a baseline for comparisons to performance from a data, process, and system perspective.