To change a step's time in a scenario in EDGEBIC, open the quote's Scenarios view, add a step override, set the Override Type to ModifyTime, and enter a new Setup Time and/or Process Time in hours, then click Run Simulation. The step uses the new times inside that scenario only. The real routing keeps its original values.
A scenario in EDGEBIC by User Solutions is a named what-if variant of a quote's simulation. A ModifyTime step override is the lever for testing "what if this operation were faster" (or slower): a proposed fixture that cuts setup, a better tool that speeds the run, or an honest allowance for a slower vendor. The change is confined to the scenario, so you can test a claim before spending money on it.
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 the new times. ModifyTime needs the routing step and the new setup and/or process hours.
- You know which step is the constraint. Cutting time on a non-bottleneck step rarely moves the finish date.
- You keep a baseline scenario. A no-override Standard scenario is what you compare the change 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 New mill fixture.
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 ModifyTime
Choose the Step, then set Override Type to ModifyTime. The time fields become relevant.
| Override Type | Effect in this scenario | You also fill in |
|---|---|---|
| ModifyTime | The step's times are changed | Setup Time and/or Process Time (hours) |
Step 4: Enter the New Times
Type the new Setup Time and/or Process Time, in hours. Change one or both:
- Lower Setup Time to model a quicker changeover or a new fixture.
- Lower Process Time to model a faster method or tool.
- Raise either to model an honest allowance, for example a slower outside vendor.
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 routing times |
How to Check It Worked
- Confirm the override row shows ModifyTime and the new times you entered.
- Click Run Simulation and note the new Total Hours and Estimated End Date.
- Open the Comparison Analysis tab, tick this scenario and a Standard baseline, and read the Lead Time and Cost charts. The change should show a different bar.
- Confirm the real routing is unchanged: open the product's routing in the BOR editor and verify the step still carries its original setup and process times.
Common Mistakes
Aiming at the wrong step. Reducing time on a non-bottleneck step adds slack there but rarely pulls the finish in. Target the constraint, which the Work Center Utilization report identifies.
Entering minutes instead of hours. Both fields are in hours. A 30-minute setup is 0.5, not 30.
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 in the BOR editor before converting the quote so the schedule can reproduce the gain.
Next Steps
ModifyTime is one of four scenario step overrides. To reroute a step to another machine use how to replace a work center in a scenario, and when the improvement is real, make it permanent with how to change the hours on a routing step. 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: A tooling vendor claims a new fixture will cut our setup on the mill step from 2 hours to 30 minutes. How do I prove it is worth buying before we commit?
A: Build a scenario and add a ModifyTime override on the mill step. Leave Process Time as is and set Setup Time to 0.5 hours. Run Simulation and compare the Estimated End Date and Estimated Cost against a no-override Standard scenario on the Comparison Analysis tab. If the shorter setup pulls the finish in enough to matter across the jobs that touch that mill, you have a numbers based case for the fixture. Remember the override only changes the scenario, so once you buy the fixture you update the real routing's setup time in the BOR editor to make the gain permanent.
Q: I lowered process time on a step but the finish date hardly moved. Why?
A: The step you changed is probably not the constraint. If another work center is the bottleneck, shaving hours off a non-bottleneck step just adds idle time there without pulling the whole job in. Check the Work Center Utilization report to find the real bottleneck, then aim your ModifyTime override at a step that runs on it. Reducing time where there is already slack rarely changes the promised date, which is the classic lesson of scheduling around a constraint.
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.