To set a scenario priority level in EDGEBIC, open the quote's Scenarios view, select or create a scenario, and set Priority Level (1 to 10) in the Production Settings group, then click Save Changes and Run Simulation. A higher number makes the simulated job compete more aggressively for capacity. The default is 5, and it affects the scenario simulation only.
A scenario in EDGEBIC by User Solutions is a named what-if variant of a quote's simulation. Priority Level is the lever for testing "what if we treated this as a rush job," biasing how hard the simulated job fights the existing load for capacity. It changes no real job, so it is a safe way to see whether rush treatment would land a tight date before you promise 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 understand priority reorders, it does not add hours. If the constraint is full, priority alone will not land the date.
- You keep a baseline scenario. A Priority 5 Standard scenario is what you compare the rush test against.
- You will set real priority separately. Winning the work means setting a real order priority, which the scenario does not do.
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 Treat as rush.
Step 2: Find the Production Settings Group
On the Scenario Parameters tab, locate the Production Settings group. It holds the levers that shape how the simulated job schedules.
Step 3: Set the Priority Level
Set Priority Level (1-10):
| Priority Level | Simulates |
|---|---|
| 8 to 10 | A rush job that competes hard for capacity against existing load |
| 5 | The default, balanced competition |
| 1 to 4 | A low-urgency job that yields to other work |
Step 4: Save and Simulate
Click Save Changes, then 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 |
|---|---|---|
| Save Changes | The scenario's stored parameters | The quote, the schedule, any real job |
| Run Simulation | The scenario's stored dates, hours, and cost | The production schedule; no real priority moves |
How to Check It Worked
- Confirm Priority Level shows the value you set.
- Click Run Simulation and note the Estimated End Date.
- Open the Comparison Analysis tab, tick this scenario and a Priority 5 baseline, and read the Lead Time chart. A meaningful priority effect shows as a shorter bar; little movement means the constraint, not sequencing, is the limit.
- Confirm no real job changed: open your live schedule and verify job priorities are untouched.
Common Mistakes
Expecting priority to create capacity. Priority reorders the queue; it does not add hours. When the constraint is full, test a capacity override or extra shift instead.
Confusing it with a real order priority. The scenario value biases the simulation only. Set a real manufacturing order priority separately if you win the work.
Forgetting to save before simulating. Save Changes stores the setting, and Run Simulation applies it. A scenario edited but not simulated cannot be applied to the quote.
Reading only lead time. A rush that wins by starving other work is worth knowing about. Check the Utilization comparison tab too.
Next Steps
Priority is one of several scenario production settings. When the real limit is capacity, test how to boost a work center's capacity in a scenario, and set real order urgency with how to set a job priority. 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 customer asks whether we could hit a tight date if we treated their job as our top rush. How do I test that in a quote?
A: Build a scenario and, in the Production Settings group, raise Priority Level toward 10, then Save Changes and Run Simulation. The higher priority makes the simulated job compete more aggressively for capacity against the existing load, which is exactly the rush-job behavior you want to test. Compare the Estimated End Date against a Priority 5 baseline scenario on the Comparison Analysis tab. If the rush treatment lands the date, you can quote it honestly, knowing you would need to set the real order's priority high and manage the jobs it would push back.
Q: I cranked scenario priority to 10 but the finish date barely improved. Why?
A: Priority changes sequencing, not capacity. If the constraint machine is already full, moving the job to the front of the queue just delays other work rather than creating new hours, so the finish only improves as far as the constraint allows. When priority alone does not land the date, the real lever is capacity: test a work center capacity override or an extra shift in the scenario instead. Priority helps most when there is contention to reorder, not when the plant is simply out of hours.
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.