|
Modeling Input / Change Type
|
Comparison Scenarios
|
What‑If Model
|
|---|---|---|
|
Compare stock levels, external scenario settings, optimization parameters
|
This is the primary usage of Comparison Scenarios. For example, changing fixed inventory and evaluating it against the production ROP. |
Stock level comparisons are not supported. |
|
Change availability service group hierarchies
|
Achieve this by changing the service group hierarchy directly and then recalculate the Comparison Scenarios to pull in the modified service group hierarchy data. |
Service group hierarchy comparisons are not supported. |
|
Run reporting comparisons like Scenario Summary, or Budget Reports
|
This is also a primary usage of Comparison Scenarios. |
The reporting comparisons use the scenario copies, but the what-if model influences the Comparison Scenario results. |
|
Make forecast adjustments applied at a model level
|
Achieve this by modifying the scenario settings. However, the output it is not reusable or segment-scoped. |
Achieve this by using the What-If Model, and the output is reusable and can be segment-scoped. For example, set the model to have a +5% forecast for a segment. |
|
Change the resupply hierarchy to test alternate location relationships
|
A Comparison Scenario cannot override the resupply hierarchy without making changes to the production data. |
Achieve this by modifying the hierarchy without changing the production data. |
|
Change the part‑level modeling inputs, such as structural or master data related
|
Part‑level overrides are not supported. |
Achieve this by changing the part-level inputs on the model for selected SKUs only. |
|
Apply changes to selected SKUs
|
Selective SKU-scoping is not supported. A Comparison Scenario applies to the entire scenario population. |
This is a primary usage of What-If Models. Achieve this by applying the model only to SKUs in an assigned segment. |
|
Test operational or structural changes without altering production data
|
Production master data is updated with a Comparison Scenario. |
This is also a primary usage of What-If Models. |
|
Reuse the same changes across multiple scenarios consistently
|
Manually intensive to keep each Comparison Scenario aligned. |
A What-If Model can be attached to many scenarios to ensure consistent inputs. |
|
Experiment with hierarchy changes before adopting in production
|
A Comparison Scenario cannot isolate hierarchy experimentation outside of production. |
This is also a primary usage of What-If Models. Hierarchy changes should not be made production until validated. |
|
Comparison Scenarios
|
These are the scenarios created by copying the Baseline Scenario and modifying selected inputs. Each Comparison Scenario can be calculated with an assigned What‑If Model, producing results that can be evaluated side‑by‑side to understand the impact of those modeling changes.
|
|
Segments
|
These will define the SKU population affected by the What-If Model.
|
|
Resupply Hierarchy
|
This is the relationship structure that will be used to propagate demand and calculate the pipeline forecasts.
|
|
Availability Service Groups
|
These will control which hierarchy is used during the Optimization process.
|
|
|
If you have to create or modify the segment, then you will need to run the Synchronize Database AutoPilot process before proceeding to the next step.
|
|
|
The number of copies you make depends on the number of comparisons you plan to review. If you have three possibilities to explore then create three copies — one for each possibility.
|