A Scenario Override Did Not Apply: Causes and Fixes

A scenario override that seems to do nothing almost always traces to one of three causes: you are reading the base quote instead of the scenario result, the override targets a step the routing does not contain, or it is a change a scenario cannot make. EDGEBIC by User Solutions runs a scenario as a separate what-if simulation, so its overrides shape only that scenario's own result and never touch the base quote or the live schedule until you apply them.

This post sits in the EDGEBIC troubleshooting guide and is the what-if companion to what a scenario can and cannot change and how to apply a scenario to a quote.

What You Are Seeing

You built a what-if scenario (boost a work center's capacity, add a shift, substitute an alternate work center, change a step's time), and the result looks identical to the baseline. The date did not move, the constraint did not shift, the original work center is still in use. The override is there, but it appears to have had no effect.

Why It Happens

A scenario is a self-contained simulation, and an override only bites inside it and only when it targets something real.

• You are reading the base quote, not the scenario. The override shapes the scenario's own run. If you compare the base quote's date, you are looking at the run the override never touched. This is the single most common cause.
• The override targets a step the routing does not have. A step override matches a specific step. A mistyped or stale step reference matches nothing, so the override is silently inert.
• The change is one a scenario cannot make. Scenarios can adjust things like capacity, shifts, step times, step order, and work-center substitution within what the model supports. A change outside that set does not apply.
• The overridden work center is not the constraint. Boosting capacity or swapping a work center that is not the limiting step changes nothing, because the bottleneck is elsewhere. The override applies, but it moves no date.

The scenario is deliberately isolated so you can compare options against the baseline without changing anything real. That isolation is exactly why an override read from the wrong place looks inert.

How to Fix It

Work from where you are looking, to what the override targets, to whether it is the constraint.

1. Read the scenario's own result. Open the scenario and compare its simulated date and schedule against the base, not the base against itself. The override's effect lives in the scenario run.
2. Confirm the override targets a real step. For a step override or a work-center substitution, verify the step exists in the product's routing and that any alternate is a valid choice for that step. A reference to a step the routing does not have does nothing.
3. Check the change is one a scenario supports. Capacity, shifts, step time, step order, and work-center substitution are the levers a scenario pulls. What a scenario can and cannot change lists them.
4. Confirm you changed the constraint. If the override is on a work center with spare capacity, the date will not move. Compare the scenario to the base to see which step shifts; if none does, apply the change to the real bottleneck instead.
5. Apply the scenario when it is the one you want. A scenario stays a what-if until you apply it to the quote. Until then, the live schedule and base quote are unchanged by design.

How to Prevent It

• Compare scenario to base, always. Read the two side by side so the override's effect (or absence) is visible immediately, rather than reading one number in isolation.
• Target overrides against the current routing. Build step overrides and substitutions from the product's actual routing so a reference always matches a real step.
• Change the constraint, not a spare resource. Identify the limiting step first, then override there. Boosting a work center that is not the bottleneck is effort with no date change.
• Know the scenario's levers. Keep to the changes a scenario supports, so you do not spend time on an override that cannot apply.
• Apply deliberately. Remember a scenario is a what-if until applied. If you want the change on the quote, apply the scenario; if you want to compare, leave it as a scenario and read its result.

If instead the scenario applied but the quoted date does not match the real schedule, that is a different symptom covered in the quote promised date does not match the real schedule.