Planning Processes
These processes are applicable to the Forecasting, Supply Planning, and Inventory Optimization modules.
Process | Description | ||||
|---|---|---|---|---|---|
ASL Generation | Calculates, for each location, which parts should be on the Authorized Stocking List for that location. The ASL Generation process can implement the Mid-Slice ASL Adjustment feature, when it is enabled. Mid-Slice ASL Adjustment lets the user add a part to the ASL (Authorized Stock List) if it meets the following criteria: • There is no non-zero demand history in any of the previous slices used in forecasting this SKU. • There is non-zero demand in current slice. • The part is stocked at a location which is above a specified Demand Accommodation (DA) threshold (which is defined in the MID_SLICE_ASL_DA_THRESHOLD global setting) The feature can be used to start stocking parts with the first occurrence of demand, without waitingt for the entire slice to complete before recognizing this demand and forecasting for this need. The Mid-Slice ASL Adjustment feature is controlled by the MID_SLICE_ASL_DA_THRESHOLD global setting. When a part is added to the Authorized Stocking List through the Mid-Slice ASL Adjustment feature, Mid-Slice ASL Adjustment is set to Yes on the Optimal Levels page. | ||||
BestFit Forecasting | Runs Best Fit Analysis. | ||||
Causal Forecast Detail | Run the Causal Forecast process. | ||||
Causal Forecasting Equipment Loader | For use with ThingWorx, to gather the equipment causal forecast data. NOTE: To enable, the IsManualProc flag in IPCS_AUTO_PILOT must be set to "y". | ||||
Causal Forecasting Equipment Rollup | For use with ThingWorx, to gather the equipment rollup causal forecast data.
| ||||
Copy Demand | Runs the copy demand process. | ||||
Delete Orphan Inventory Optimization Scenarios | Deletes the records from Inventory Optimization tables for scenarios that are not related to a scenario series. This process is also run by the Make Production process in order to automatically keep the record counts down. | ||||
Demand Aggregation (Cannot be executed by Segment) | Runs the Demand Aggregation and Forecast Disaggregation process. | ||||
Demand Detail Aggregation | Performs the rollup of Demand Detail to Demand History, using the values from these global settings: • DEMAND_DETAIL_AGGREGATION_SLICES • DEMAND_DETAIL_AGGREGATION_BY_SLICE • DEMAND_DETAIL_AGGREGATION_MODE | ||||
Demand History Management | Generates Outliers in the demand history.
| ||||
Disassembly | Runs the disassembly process that populates the Product Disassembly page. | ||||
Forecast Netting | Runs the forecast netting process. | ||||
Forecasting | Calculates the demand forecast for all parts and locations. | ||||
Forecasting-Calculate Metrics | Calculates the bias metrics.
| ||||
Frequent Data Load | Allows users to load stock amounts, sales orders, Order Plan, and Order Plan shipment data frequently throughout the day for SKUs in a process group. This process must run in coordination with the Gateway and Synchronize Database AutoPilot processes. Gateway and Synchronize Database can not start processing while the Frequent Data Load process is running. However, the Frequent Data Load process can run while Gateway or Synchronize Database processes are running, but cannot process data that belongs to the same group of locations being processed by the Gateway. | ||||
Generate Order Plan | Runs the Order Plan process which populates the Planner Worksheet. This process is comprised of multiple processes that run in succession. After the Post Review process completes, the Post Auto Approval Review process is run. This process has a Run Time Order of 5, which allows 5 custom review reasons to be configured to run after the auto approval process. These five Review Types are configured at installation for the Post Auto Approval Review process: • Part has new recommended repair orders (323) • Part has new recommended replenishment orders (324) • Part has new recommended balancing orders (325) • Part has new recommended procurement orders (326) • Part has new recommended excess recall orders (332) | ||||
High Margin Analysis (Cannot be executed by Segment) | Finds opportunities to add install base without increasing stocking levels by looking at fractional levels, before rounding, and processing iterations of adding install base units until the supporting stock level would actually increase by one unit. This process gives sales teams the opportunity to know that they can go into an area and sell a specific number of additional contracts without investing in additional inventory. | ||||
Make Forecast Production | The approved forecast is made production. | ||||
Inventory Optimization - MEO Make Production (Cannot be executed by Segment) | Updates the net forecast and stock level and makes the scenario associated with the selected segment production.
| ||||
Inventory Optimization - Run Supercession Changes | Moves overrides from a down-chain replaced part to a new Top Most Revision (TMR) part and updates SKU Overrides and stock levels for Part Chain changes. This process is run in two phases: 1. Update SKU Overrides due to Part Chain changes — Every time this step is run the process checks for SKU Overrides on a child part and merges them to the TMR part. a. Move SKU Override values to the TMR part ▪ If a TMR part has no SKU Overrides, a new SKU Override is added for the TMR part ▪ For child part SKU Override type, if no TMR part value exists the child SKU Override values are merged: ▪ The maximum value of all child SKU Overrides is applied for all Minimum SKU Overrides ▪ The minimum value of all child SKU Overrides is applied for all Maximum SKU Overrides ▪ The minimum value of all child SKU Overrides is applied for all Fixed SKU Overrides
b. The End Dates for the SKU Overrides on the child part are updated to yesterday. For example: ▪ TMR part has a SKU Override of Minimum ROP = 0 ▪ Child part has SKU Overrides of Minimum ROP = 1 and EOQ = 4 ▪ TMR SKU Overrides are updated to Minimum ROP = 0 and EOQ = 4 ▪ End Dates of the SKU Overrides on the child part are set to yesterday 2. Update Stock Levels a. Update the TMR part and child part stock levels of the Inventory Optimization production scenario b. Update the stock levels used by the Inventory Optimization module a. The following fields are summarized for the child parts and added to the TMR part: ▪ Customer Daily Forecast ▪ Customer Daily Forecast Variance ▪ Repairable Daily Forecast From Below ▪ Condemned Daily Forecast From Below ▪ Emergency Daily Forecast ▪ Backorder From Parent Location ▪ ShareAboveBackordersVariance ▪ Backorder From Components ▪ ShareComponentsBackordersVariance b. The EOQ of the TMR part is set to the maximum EOQ of the parts in the part chain. c. The pipeline forecast and variance for the TMR part is calculated using the following: ▪ The TMR part pipeline forecast and variance using the sum of the demand rates ▪ The demand variances using the TMR part composite lead time and TMR composite lead time variance ▪ The backorders from component parts ▪ The backorders from the parent location c. Update stock level fields used by the Supply Planning module ▪ If no record for the TMR part exists in the Inventory Optimization Production Scenario then the TMR part is added to the Production Scenario ▪ Update the demand and variance values ▪ Calculate the weighted average chain ROP of the TMR part using a fill rate target that is the weighted fill rate of the TMR part and child parts using total demand Set the ROP of the TMR part equal to the maximum of the weighted average chain ROP and the maximum ROP value in the chain Calculate other stocking levels, fill rate, and wait time based on the new ROP value of the TMR part d. Set the child ROP = -1 and update other stocking levels ▪ Demands and variances of the child part are not updated ▪ Part Relationship Type is set to 0 for child parts These are the recommend steps when using the Inventory Optimization-Run Supercession Changes 1. Run the Synchronize Database AutoPilot process 2. {Optional} Run the Forecasting AutoPilot process 3. Run the Inventory Optimization - Run Supercession Changes AutoPilot process 4. Run the Apply Overrides To Production job on the Scenarios page
| ||||
Merge SKU Overrides | Merges SKU Overrides, unique by Part, Location, Begin Date and Override Type, into a single record per Part, Location and Begin Date. This process is included as part of the Synchronize Database process.
| ||||
Multi-level BOM Synchronize Database | Flattens the product BOM, which can contain products and parts, to create part-to-part relationships. This information is used in downstream processes like forecasting. | ||||
Refresh Planner Home Page | Processes any new or changed data and refreshes the Planner Home Page with the updated data.
| ||||
Scheduled Event Detail | Calculates event forecast details by part and install site.ProcID(1208) must be enabled to see the Scheduled Event Detail process on the AutoPilot page. The Scheduled Event Detail AutoPilot process must be run before the Forecasting AutoPilot process. | ||||
Stock Level Generation | Calculates the optimal levels for each SKU. | ||||
Vendor Group Min Order Quantity | Runs the process to order based on vendor group min order quantity.
| ||||
Vendor Split | Runs the process to split orders by vendor.
|
