Levels Included in Inventory Optimization - Run Supercession Changes AutoPilot Process
In prior releases, the Inventory Optimization — Run Supercession Changes AutoPilot process only moved SKU Overrides from a down-chain replaced part to a new Top Most Replaced (TMR) part. With the 12.2.1.0 release, this process was expanded to update SKU Overrides and stock levels for Part Chain changes.
The following changes were made to the Inventory Optimization — Run Supercession Changes AutoPilot process:
New AutoPilot Parameters
Two new AutoPilot parameters were added to the AutoPilot.properties file.
|
Property
|
Description
|
Default Setting
|
|---|---|---|
|
servigistics.io.tmr.overrides
|
When this property is set to true the Inventory Optimization — Run Supercession Changes process updates SKU Overrides due to Part Chain changes
|
true
|
|
servigistics.io.tmr.levels
|
When this property is set to true the Inventory Optimization — Run Supercession Changes process updates the stock levels
|
true
|
 |
Both properties should remain set to true.
|
Updated AutoPilot Job
The Inventory Optimization — Run Supercession Changes AutoPilot process was updated to 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
 |
Important things to remember:
• This process does not resolve conflicts in merging child SKU Overrides. The calculation follows the priority rules outlined in the How is the priority determined section of the SKU Constraints and Overrides FAQs topic.
• If you manually edit the SKU Override, the application will prompt you to resolve any conflicts before saving your changes.
|
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
Recommended Workflow
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
 |
Running Make Production will reset the level values based on the Part Chain at the time the Scenario was calculated.
|