To reorder a step in a scenario in EDGEBIC, open the quote's Scenarios view, add a step override, set the Override Type to Reorder, and enter the new Sequence number, then click Run Simulation. The step moves to the new position inside that scenario only. The real routing keeps its original sequence.
A scenario in EDGEBIC by User Solutions is a named what-if variant of a quote's simulation. A Reorder step override is the lever for testing "what if the operations ran in a different order," for example moving inspection earlier so rework is caught sooner, or running a slow step first so downstream work overlaps it. The resequence is confined to the scenario, so you can test the idea before touching the real routing.
Before You Start
- A quote exists and has been simulated once. Scenarios are children of a quote, and the base simulation is your comparison baseline. See how to create a what-if scenario.
- You know the step and its new sequence number. Reorder needs the routing step and the position you want it in.
- You understand the dependency risk. Moving a step that feeds a later one can produce dates that are physically impossible.
- You keep a baseline scenario. A no-override Standard scenario is what you compare the resequence against.
Step 1: Open the Scenario View
On the Quote tab, select the quote and click Scenarios. The What-If Scenario Analysis view opens. Select an existing scenario or click Create New Scenario and name it after the lever, for example Deburr before paint.
Step 2: Add a Step Override
In the Production Step Overrides group, click Add Step Override. A new override row appears.
Step 3: Pick the Step and Set Reorder
Choose the Step, then set Override Type to Reorder. The sequence field becomes relevant.
| Override Type | Effect in this scenario | You also fill in |
|---|---|---|
| Reorder | The step moves to a new position in the sequence | Sequence # |
Step 4: Enter the New Sequence Number
Type the Sequence # that places the step where you want it. A lower number runs earlier in the routing; a higher number runs later. This is the position the scenario will simulate.
Step 5: Run the Simulation
Click Run Simulation. Read the Simulation Results: Estimated Start Date, Estimated End Date, Lead Time, Total Hours, and Estimated Cost. Each run overwrites this scenario's stored results, and nothing touches the shop plan.
What Changes When You Save
| Action | What changes | What does NOT change |
|---|---|---|
| Run Simulation | The scenario's stored dates, hours, and cost | The production schedule, the quote, the real routing |
| Apply to Quote | The parent quote's estimated numbers | The product's real step sequence |
How to Check It Worked
- Confirm the override row shows Reorder and the new sequence number.
- Click Run Simulation and note the new Estimated End Date.
- Sanity check the dates: make sure no step now simulates before an operation it truly depends on.
- Open the Comparison Analysis tab, tick this scenario and a Standard baseline, and read the Lead Time chart. Confirm the real routing sequence is unchanged in the BOR editor.
Common Mistakes
Breaking a dependency. Moving a step ahead of the operation it feeds lets that operation simulate too early. Always read the resulting dates for plausibility before trusting a reorder.
Reordering when a time or machine change is the real lever. If the goal is a faster step, use ModifyTime. If it is a different machine, use Replace. Reorder only changes position.
Forgetting to re-simulate. The override does nothing until you click Run Simulation.
Treating the scenario as a real change. Applying a winning scenario copies its numbers onto the quote only. Update the real routing sequence in the BOR editor before converting the quote.
Next Steps
Reorder is one of four scenario step overrides. To change a step's timing use how to change a step's time in a scenario, and when a resequence proves out, make it permanent with how to reorder routing steps. Compare your what-ifs with how to compare two scenarios side by side. More single-task recipes live in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: We think doing the deburr step before paint instead of after would let paint start sooner. Can I prove it without editing the routing?
A: Yes. Build a scenario and add a Reorder override on the deburr step, entering the Sequence number that places it ahead of paint. Run Simulation and compare the Estimated End Date against a no-override Standard scenario on the Comparison Analysis tab. If the resequence really pulls the finish in, you have a numbers based case. Because the override lives only in the scenario, your real routing and live schedule are untouched, so make the change in the BOR editor before converting the quote if you decide to adopt it.
Q: I reordered a step but the simulated dates look impossible, finishing earlier than physically makes sense. What happened?
A: Reordering can break a real dependency. If the step you moved fed a later operation, placing it after that operation lets the later step simulate as if its input were already available. The engine follows the sequence you gave it. Sanity check the resulting dates before quoting from the scenario, and only adopt a resequence that respects what actually depends on what. When dependencies are tight, a Replace or ModifyTime override is often the safer lever than reordering.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.