Inventory Optimization > Scenario Results > Scenario Summary > Scenarios Page > Scenarios > Scenarios (Fields)
Scenarios (Fields)
The following table describes the items that appear on the page.
* 
Field names with an asterisk () are included in the default display setting.
Field
Description
ASL Strategy
The different ways to manage the ASL process. Valid options are:
• Respect External All - Inventory Optimization will not make ASL decision, it is input to the optimization whether the SKU is on/off ASL. The ASL decision could be made from ASL generation process.
• Respect External Non-ASL - Inventory Optimization will treat non-ASL decision as input, but it may take ASL SKUs off ASL.
• Optimize ASL - Inventory Optimization will make the ASL decision whether the SKU is on or off ASL. This is the recommended setting.
* 
The default value is Optimize ASL when the INVENTORY_OPTIMIZATION_MODE global setting is set to MIO or MEO.
Calculated Date
The time when the scenario was calculated or recalculated.
Calculated Version
The release version of Servigistics that was used to calculate the Scenario.
Category
A filtering label that is defined on the Category page.
Causal Forecast Scenario
The name of the Causal Forecast scenario. [more details]
Churn Control Method
The method of churn control. Valid options are:
• None — Churn control is not run as part of the calculation process.
• Use Inventory Balance with Reference Scenario — Use the most recently calculated non-churn scenario with the same scenario attributes (such as periods to be optimized, the same forecast source, optimization set, etc).
• Use Inventory Balance — Current inventory balance will be used first, and condemned forecast will be used for inventory burn down throughout the optimization horizon.
• Respect Production — ROP constraints can be set based on production values.
• Respect Previous Period —ROP constraints can be set based on optimization results from immediate prior optimization period.
* 
When using Churn Control Parameters on a scenario you can configure the parameters to allow a ROP = -1 to increase to 0 and a ROP = 0 to increase to 1 by setting a high control or threshold limit of greater than 100% for a Respect Production Parameter.
When the INVENTORY_OPTIMIZATION_MODE global setting is set to SIO, the Churn Control field is disabled.
Churn Control Reference Scenario
The most recently calculated scenario that contains all of the periods that are in the churn scenario, and has the same settings for the other scenario attributes that control function. This is the scenario that is considered when the Use Inventory Balance with Reference Scenario churn control method is selected for a scenario.
Complete Before Summarization
A multi-period calculation setting for a scenario on the Scenarios page. Yes is displayed in this column for the scenario on the Scenarios page when this option is selected for the scenario.
• When selected, the scenario calculation process is treated as two separate tasks; Calculate Stocking Levels and Calculate Summary Levels. This enables the visibility of the data as follows:
Calculate Scenario Step
After Completion
Calculate Stock Levels
1. You can view the output of the stock level calculations on these pages:
◦ SKU Summary
◦ SKU Detail Report
◦ Inventory Collaboration
◦ Part Supply Chain
2. You can run these AutoPilot processes:
◦ Make Production
◦ Generate Order Plan
3. The summary calculation for each interval begins processing in the background.
Calculate Summary Values
The summary values are updated on these pages after all intervals are summarized:
• Scenario Summary
• Part Summary
• Location Summary
• Segment Summary
• Service Group Results
• When this option is not selected, the stock level calculations and the interval summary calculations must all be completed before the data is visible on any page. No additional processing can begin until both steps of the calculation process complete.
* 
The recommended setting is Yes (selected).
Demand Rate Days Constant
The number of days to be added to the Daily Demand Rate. Calculated as
Demand Rate Days Constant + (Demand Rate Days Multiplier * SKU Resupply Lead Time Days)
* 
This is specified when the scenario is created or changed.
Demand Rate Days Multiplier
The multiplier applied to the SKU Resupply Lead Time Days when determining the Daily Demand Rate. Used in the calculation of standard deviation in the levels calculations.
Demand Rate Days Constant + (Demand Rate Days Multiplier * SKU Resupply Lead Time Days)
* 
This is specified when the scenario is created or changed.
Exception Criteria
In reference to a Scenario, this is the selected method to be used for including Exception Criteria in the calculation. Valid options are:
• Run exception criteria for all periods
• Run exception criteria for first period
• Do not run
* 
When creating a scenario, the default value is Run exception criteria for all periods.
Exception Criteria Comparison Scenario
The compare-to scenario to be used when performing the Exception Criteria process that can be specified by scenario on the Scenarios page. The default value is Production.
External Reporting Data Generated
A Yes/No indicator of whether the Generate External Reporting Data process was run for the scenario.
External Scenario
The name of the external scenario to be used in the calculation process, as defined in the External Scenario page.
Fill Rate Method
The method that is used to calculate the Fill Rate. Valid options are:
Method
Description
Fill Rate/Probability In Stock
Fill Rate as the probability of having positive stock on the shelf during the replenishment cycle.
Fill Rate/Probability In Stock, with Reorder Quantity Benefit
Fill Rate as the probability of having positive stock on the shelf during the replenishment cycle, considering the benefit of the batch order size (Reorder Quantity >1).
Approximate Fill Rate: 1– Expected Backorder (ROP+1) / Reorder Quantity
Fill Rate as the expected percentage of demand met from off the shelf stock during the replenishment cycle, from a supply perspective.
Approximate Fill Rate: 1– Expected Backorder (ROP+1) / Pipeline Forecast
Fill Rate as the expected percentage of demand met from off the shelf stock during the lead time, from a demand perspective.
Fiscal Interval
The timeframe of the fiscal period. Options are:
• Period
• Quarter
• Year
The default setting is Quarter when Fiscal Optimization is selected.
Fiscal Optimization
An indicator of when the Fiscal Optimization feature is used.
• On the Create/Edit Scenario page, this appears as a checkbox. Select the checkbox to use Fiscal Optimization
• On the Scenarios page, this appears as a Yes or No indicator. When the checkbox is selected on the Create/Edit Scenario page, then Yes is displayed.
When this option is selected on the Create/Edit Scenario page:
• The Number of Fiscal Years and Fiscal Interval fields are enabled
• The Horizon (periods) and Interval (periods) fields are disabled
When this option is not selected on the Create/Edit Scenario page:
• The Horizon (periods) and Interval (periods) fields are enabled
• The Number of Fiscal Years and Fiscal Interval fields are disabled
Forecast Type
The type of forecast used in the calculation. The options available are controlled by the ENABLE_FORECAST_APPROVAL global setting.
Generate Prioritized Buy List
An indicator of whether a prioritized buy list is generated for the scenario. It is defined when creating or modifying a scenario on the Create/Edit Scenario window.
• Do one of the following on the Create/Edit Scenario window:
◦ Select the checkbox to set the option to generate a prioritized buy list for the scenario.
◦ Clear the checkbox to have no prioritized buy list generated for the scenario.
• An indicator of the selection made when the Scenario was created or modified is displayed on the Scenarios page:
◦ If the Generate Prioritized Buy List option on the scenario was selected, Yes is displayed
◦ If the Generate Prioritized Buy List option on the scenario was not selected, No is displayed
Horizon
The number of slices to include in the calculation. For example, a customer site that is monthly:
• 48 means include 48 slices (4 years)
• 12 means include 12 slices (1 year)
The zero (0) slice in the Horizon is the End Of Production (EOP) date.
In Collaboration
Indicates whether a scenario or a segment is enabled for Inventory Collaboration.
• In relation to a scenario:
◦ Yes indicates that the Start Collaboration job was run on the scenario, and the scenario is available on the Inventory Collaboration page
◦ No indicates that the Start Collaboration job has not been run on the scenario, and the scenario is not available on the Inventory Collaboration page
• In relation to a segment:
◦ Yes indicates that the Start Collaboration job was run on the segment, and the segment is available on the Inventory Collaboration page
◦ No indicates that the Start Collaboration job has not been run on the segment, and the segment is not available on the Inventory Collaboration page
Interval
The time period being planned. For example, a customer site that is monthly:
• 3 means calculate every 3 periods (quarterly)
• 12 means calculate every 12 periods (once a year)
• 1 means calculate every 1 period (monthly)
Last Time Buy
In reference to a Scenario, this is the indicator of how the Scenario is used in the Inventory Optimization Last Time Buy Scenario Workflow. Valid options are:
Option
Description
No
The scenario is not associated with Last Time Buy.
Planning
The scenario is used to calculate Last Time Buy recommended quantities.
Monitoring
The scenario is used to monitor Last Time Buy part levels after Last Time Buy orders are issued.
* 
When creating a scenario, the default value is No.
Made Production Date
This field has different meanings depending on the usage:
• In the Inventory Optimization module, this is the date the Scenario was made production.
• On the SIOP Plans page, this is the most recent date any Forecast Scenario associated with the SIOP Plan was promoted to In Production. This date may update even if the SIOP Plan was already in the In Production state.
Mean Days to Remove and Replace
The number of days required to remove and replace the item. The value can contain up to 4 decimal places, but only 3 are displayed.
Multi-Period Approval
An indicator of whether all periods are approved or disapproved for pending SKU. It is defined when creating or modifying a scenario on the Create/Edit Scenario window.
• Select the checkbox to approve all periods.
• Clear the checkbox to approve one period at a time.
On the Scenarios page:
• If the Multi-Period Approval option on the scenario was selected, Yes is displayed.
• If the Multi-Period Approval option on the scenario was not selected, No is displayed.
* 
This option is selected by default when the INVENTORY_OPTIMIZATION_MULTI_PERIOD_APPROVE global setting is set to true.
Note
Informational text entered by the user.
Number of Fiscal Years
The number of years to consider for Fiscal Optimization.
Objective Benefit Criteria
The metric to be used as the Objective Benefit in the Bang for Buck calculation. Valid options are:
Option
Description
Fill Rate Increment
Evaluates SKUs based on an increase in Fill Rate.
EBO Reduction
Evaluates SKUs based on a decrease in EBO.
* 
If a SKU is in a Service Group has the Minimize Stockout Cost option selected, then the benefit is the reduced stockout costs.
* 
This is specified when the scenario is created or changed.
Objective Cost Criteria
The metric to be used as the Objective Cost in the Bang for Buck calculation. This indicates how the Objective Cost for a SKU is populated when a scenario is calculated. Valid options are:
Option
Description
Part Cost
The Objective Cost is populated with the Part Cost. This is the default selection.
Optimization Cost
The Objective Cost is populated with the Optimization Cost defined on the SKU or the Parts page. This enables customizable Part and SKU Optimization Cost inputs to be used as the Objective Cost. To ensure that all SKUs have an Objective Cost when Optimization Cost is selected, the following costs are referenced in priority order by the Bang for Buck calculation:
• Optimization Cost defined on the SKU
• Optimization Cost defined on the Part
• If no Optimization Cost is defined on the SKU or the Part then:
◦ Part Cost defined on the SKU
◦ Part Cost defined on the Part
Carbon Tax (Embodied) + Part Cost
The Objective Cost is populated with the (Embodied Carbon Per New Buy * Carbon Tax Rate) + Part Cost.
* 
Regardless of the Objective Cost Criteria selection:
• The New Buy Cost is the Objective Cost during the enforcement of Service Group New Buy Budget Constraints.
• The combined Repair Cost and New Buy Cost are the Objective Cost during the Availability with Repair Optimization algorithm.
Optimization Set
A collection of service groups that are assigned to a scenario. An optimization set can have any number of service groups. Optimization sets are defined on the Optimization Set page.
Parent Scenario
The scenario that was copied to create this scenario. If the scenario was not created by copying an existing scenario, then this field is blank.
Production Approval Type
Indicates whether a scenario SKU will be evaluated using holding thresholds or set to auto-approval. Valid options are:
• Approve All
• Pending All
• Exception Criteria
* 
When Exception Criteria is selected, the Exception Criteria field is populated with Run exceptions for all periods. This selection combination cannot be changed. To specify a different Exception Criteria method, select a different Production Approval Type.
Respect Override
A Yes/No indicator that controls if the SKU Override values that were entered on the SKU Overrides page and Post-Optimization SKU Constraints that were entered on the Service Group Parameters page are used in the calculation.
* 
This field is defined when a scenario is created or changed.
Run Forecast Pooling
A yes/no indicator that is set on a scenario that defines if the pooling phase is included in the calculation process.
* 
The pooling records that are defined on the Pooling Parameters page are used in the pooling phase of the calculation process.
Run Rotable Pooling
A yes/no indicator that is set on a scenario that defines if Rotable Pooling is included in the calculation process.
* 
The pooling records that are defined on the Rotable Pool Constraints page are used in the rotable pooling phase of the calculation process.
Scenario
The unique name given to a collection of inputs and results. Each scenario is a set of rules that govern the Inventory Optimization calculations performed on the Scenario page and performed by the AutoPilot calculation.
* 
The system generated scenario, named Production, is a read-only scenario that contains a summary of the production SKUs that are being planned by the system. This scenario cannot be deleted and jobs cannot be run against it.
Scenario Workflow Status
The transition steps during the calculation process when the Calculate before Summarization option is selected for a scenario on the Scenarios page. These are the valid status values:
Status
Description
Model Incomplete
The model has not reached a state that is eligible for review.
Making Stock Level Changes
Operations are modifying stock levels.
Candidate
The calculation process completed and the scenario can be promoted to production because it is either an external scenario or the Respect Override option is selected.
Non-Candidate
The calculation process completed but the scenario is not eligible to be promoted to production because it is a non-external scenario and the Respect Override setting is not selected.
Making Production
The Make Production job is running.
Promoted
The scenario values are promoted to the Production scenario.
Production
The scenario is the Production scenario.
Service Groups Include Non Stockable Items
Indicates if non-stock items (stockmax = 0) should be included in the service group calculation. If selected, the service group target may not be reached.
• When selected or Yes, then the non-asl SKU's demand is included in the service group optimization.
• When not selected or No, then the non-asl SKU's demand is excluded from the service group optimization.
Start Date
The start date that is used as the baseline date to determine the daily demand rates based upon start date plus look-ahead days.
State
The processing stage of a scenario. Valid states are:
State
Description
Completed
The scenario is not undergoing any processing and is in a usable condition.
Created
The scenario was defined, but has not been calculated.
Failed
The scenario experienced a runtime error and is not in a usable condition.
Needs Recalculation
The scenario was edited in such a way as to render previous results incompatible with current controlling attributes.
Production
The system managed collection of operational SKU values are bundled in the Production scenario.
Running
The scenario is being operated on by a job that may modify the output.
Waiting To Run
A calculation was requested for the scenario.
Waiting To Delete
A deletion of the scenario and the associated output was requested.
Waiting To Apply Overrides
Apply Overrides was requested for the scenario.
Waiting To Make Production
Make Production was requested to promote the scenario, using its values to create the Production scenario.
Promoted To Production
The scenario was used to Make Production and has at least one SKU that serves the Production scenario values.
* 
The IO_PROD_SKU_TRACKING global setting has an effect on the Promoted To Production state.
* 
The state is controlled by the system and cannot be modified by a user.
Summarize Excluded SKUs
Indicates when summary values include SKU that are not in the scenario coverage but are part of the scenario due to the replenishment hierarchy. In other words, indicates if non-optimized SKUs are included in the summary report.
• Yes indicates that both fill rate and optimized fill rate include non-optimized SKUs.
• No indicates that the definitions of all summary values do not include non-optimized SKUs.
Use External Values
The selected method for processing external values. Options are:
• None, which indicates that the values generated by the calculation are used.
• Use Inventory Position, which indicates that the calculation process should use the values and ordering entered in the Current Inventory Parameters page.
• Use External, which indicates that the calculation process should use the values entered in the External Scenario page, for the specified external scenario.
Use Line Fill Rate
An indictor of whether the Line Fill Rate or the Unit Fill Rate is used when calculating the Fill Rate metric. The resulting stock levels are multiples of the Customer Order Size. For example, if a shelf stock is 7 units, and a customer has an order for 10 units:
The Unit Fill Rate is 70%
The Line Fill Rate is 0%
• When this option is selected the Fill Rate metric is measured by Line Fill Rate and uses the Customer Order Size, which is based on the Customer Order Size Average (default 1), the Customer Order Size Standard Deviation (default 0), and the Line Fill Rate Safety Factor (default 0). The resulting stock levels (Safety Stock, ROP, and Stock Maximum) are multiples of the Customer Order Size.
• When this option is not selected, the Fill Rate metric is measured by Unit Fill Rate and the Customer Order Size is always equal to 1.
* 
The Customer Order Size that is used for Line Fill Rate calculations is not considered for availability models by Inventory Optimization. Therefore, the resulting stock level is not necessarily a multiple of the Customer Order Size.
What-If Model
The name of the What-If Model defined on the What-If Model page. When a scenario is created or changed using the Scenarios page, the What-If Model can be selected.
• If a What-If Model is selected, then that model is used during the Inventory Optimization calculation.
• If no What-If Model is specified for a Scenario, no model is used during the Inventory Optimization calculation.
• If the What-If Model selection is changed, the Scenario is flagged as needing to be recalculated.
Was this helpful?