How to Allow Parallel Processing in a Scenario in EDGEBIC
User Solutions TeamTo allow parallel processing in a scenario in EDGEBIC, open the quote's Scenarios view, tick Parallel Processing in the Production Settings group, set Max Parallel Centers, then click Save Changes and Run Simulation. The routing's parallel paths run at once inside that scenario only. Nothing on the real schedule changes.
A scenario in EDGEBIC by User Solutions is a named what-if variant of a quote's simulation. The Parallel Processing setting is the lever for testing "what if we ran the parallel paths in this routing at the same time," and Max Parallel Centers caps how many machines share the work. Because it is confined to the scenario, you can weigh the lead-time gain against the cost of staffing more machines before committing.
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.
- The routing has a parallel path. The toggle uses parallel work center paths that already exist in the routing. See how to make two operations run in parallel.
- You keep a baseline scenario. A Parallel-Processing-off scenario is what you compare the parallel run against.
- You will staff it for real if adopted. The scenario proves the idea; running the parallel path in production is a separate step.
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 Parallel milling.
Step 2: Find the Production Settings Group
On the Scenario Parameters tab, locate the Production Settings group.
Step 3: Tick Parallel Processing and Set the Cap
Tick Parallel Processing, then set Max Parallel Centers:
| Field | Default | Effect |
|---|---|---|
| Parallel Processing | Off | When on, parallel work center paths in the routing may be used at once |
| Max Parallel Centers | 2 | Caps how many machines may run concurrently |
Raise Max Parallel Centers to let more machines share the work when the routing supports it.
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, the real routing |
| Run Simulation | The scenario's stored dates, hours, and cost | The production schedule; no real capacity added |
How to Check It Worked
- Confirm Parallel Processing is ticked and Max Parallel Centers shows your cap.
- Click Run Simulation and note the Estimated End Date.
- Open the Comparison Analysis tab, tick this scenario and a Parallel-off baseline, and read the Lead Time chart. A working parallel path shows a shorter bar.
- If nothing moves, open the routing in the BOR editor and confirm a genuine parallel path exists for the setting to use.
Common Mistakes
No parallel path in the routing. The toggle only uses parallel paths that already exist. Add one in the routing first, or the setting has nothing to act on.
Targeting a non-bottleneck. Overlapping a step that is not the constraint rarely shortens the whole job.
Setting the cap too low. If Max Parallel Centers is 1, there is no concurrency to gain. Raise it to the number of machines you would actually staff.
Forgetting to save before simulating. Save Changes stores the settings, and Run Simulation applies them.
Next Steps
Parallel processing is one of several scenario production settings. To test more capacity another way, see how to boost a work center's capacity in a scenario, and set up a real parallel path with how to make two operations run in parallel. 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: Our routing can split a big operation across two machines, but we're not sure it is worth staffing both. How do I test it on a quote?
A: Build a scenario, tick Parallel Processing in the Production Settings group, and set Max Parallel Centers to 2. Save Changes and Run Simulation, then compare the Estimated End Date and Estimated Cost against a scenario with Parallel Processing off on the Comparison Analysis tab. If running both machines pulls the finish in enough to justify the second operator, you have a numbers based case. Because the scenario changes nothing real, you would then staff and run the parallel path for real if you win and adopt the plan.
Q: I ticked Parallel Processing but the finish date did not move. Why?
A: The most common reason is that the routing has no parallel path for the setting to use, so there is nothing to run concurrently. Check the routing in the BOR editor for a genuine parallel branch. The second reason is that Max Parallel Centers is capping the concurrency, or the parallel step is not the constraint, so overlapping it does not shorten the overall job. Confirm the parallel path exists and target the bottleneck before expecting a shorter lead time.
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.