How to Skip a Step in a Scenario in EDGEBIC

To skip a step in a scenario in EDGEBIC by User Solutions you add a production step override, pick the routing step, and choose the Skip override type, then re-simulate. The control is the Production Step Overrides group on the scenario's Scenario Parameters tab. Skip removes the step from the routing for that scenario only, so you can model outsourcing or an omitted operation without touching the real routing or the production schedule.

For the full picture of what a scenario can and cannot change, read what a scenario can and cannot change. This task is documented behavior of EDGEBIC, and the full task library is in the how-to hub. If the scenario does not exist yet, start with how to create a what-if scenario. To move a step to a new sequence position rather than drop it, see how to reorder a step in a scenario.

Before You Start

• A scenario exists on the quote.
• You know which routing step you are altering and whether anything downstream depends on it.

Step 1: Open the Step Overrides

On the scenario's Scenario Parameters tab, scroll to the Production Step Overrides group. Click Add Step Override.

Step 2: Pick the Step and the Override Type

In the new override, pick the Step (the routing step to alter) and choose the Override Type:

For a true skip, choose Skip. To outsource, choose Replace and pick the vendor work center.

Step 3: Re-Simulate

Click Run Simulation to re-simulate with the override applied. The Simulation Results group updates with the new dates, hours, and cost.

Skip vs Replace vs ModifyTime: Choosing the Right Type

The four override types answer four different questions, and picking the wrong one is the most common scenario mistake.

• Skip answers "what if this operation disappears entirely?" It removes the step and all its time. Use it only when the operation genuinely does not happen in the variant you are quoting, and check the dates afterward because Skip does not reconnect what depended on the step.
• Replace answers "what if this operation runs somewhere else?" The step stays in the routing but on a different machine, which is how you model outsourcing. The operation and any downstream dependency are preserved, so it is the safe choice whenever the work still has to happen.
• ModifyTime answers "what if this step is faster or slower?" The step stays in place; only its setup and process times change. Use it for a machine upgrade, a faster tool, or a vendor whose cycle time differs.
• Reorder answers "what if this step runs at a different point in the sequence?" It moves the step to a new position.

Worked Example: Two Ways to Hit the Date

A customer will accept a Widget-A variant without the deburr step. You create a scenario named No Deburr, add a step override on deburr, and set the type to Skip. Run Simulation returns shorter dates and lower cost because the operation is gone. Before quoting from it, you confirm no later step waited on deburr, because Skip does not rewire dependencies and could otherwise let a downstream step start earlier than reality allows.

Contrast that with outsourcing CNC machining to a faster, pricier vendor. Here the operation still happens, so Skip would be wrong: it would delete the CNC time and badly understate the job. Instead you create a scenario, add a step override on the CNC step, set the type to Replace, and pick the vendor work center as the alternative, optionally setting the vendor's setup and process times. Run Simulation returns the vendor's dates and cost, with the routing dependency intact. Same goal, two different override types, and the choice hinges on one question: does the operation still happen?

What Changes When You Save

Saving stores the override on the scenario. The simulation stores the scenario's new results. Neither changes the real routing on the product, the quote, or the production schedule. The override only shapes the scenario's own simulation.

How to Check It Worked

Confirm the override appears in the Production Step Overrides group with the right step and type. After Run Simulation, the scenario's estimated hours and cost should drop for a Skip (the operation is gone) or change to reflect the vendor for a Replace.

Then do the sanity check that a Skip specifically demands. Look at the routing the scenario ran and ask whether any step that came after the skipped one used to wait on it. If it did, compare the downstream step's simulated start against when its inputs would physically be ready. Because Skip removes the step without reconnecting the dependency, the simulation can schedule that later step as if its predecessor never needed to happen, which produces a finish that is too good to be real. If the dates look impossibly early, that is the signal to switch from Skip to Replace or ModifyTime, which keep the step and its dependency in place. Never send a customer a promise off a skip scenario you have not walked step by step.

Common Mistakes and Gotchas

• Skip does not rewire dependencies. It drops the step without reconnecting what relied on it, so a downstream step can simulate earlier than is possible. Check the dates before quoting from a skip scenario.

• Outsourcing is Replace, not Skip. An outsourced operation still happens elsewhere. Skip would delete the time entirely and understate the job. Use Replace with an alternative work center.

• A scenario override is not a routing change. It shapes the scenario simulation only. If the customer accepts an outside-vendor scenario, make the real routing change in the routing editor before converting the quote, or the live run uses the old machine.

• Applying does not make it real. Writing scenario numbers onto the quote does not alter the routing or capacity. Follow through in the real data first.

• Reorder and ModifyTime are the quieter tools. When the question is not whether a step happens but where it runs in the sequence, or how long it takes, reach for Reorder or ModifyTime instead of stretching Skip or Replace to fit. Matching the override type to the actual change keeps the scenario honest and the result easy to explain.

Once your step overrides and any capacity changes are set, line the scenarios up against each other in how to compare two scenarios side by side.