How to Simulate Multiple Quotes at Once in EDGEBIC

To simulate several quotes at once in EDGEBIC by User Solutions, filter the quote grid to the set you want, leave every row checkbox unchecked, and click Run Simulation. With nothing checked, the run covers every quote in the current filter that has not yet been simulated, and a confirmation dialog tells you how many that is before anything starts.

This is the batch version of quote simulation, which produces finite capacity start and end dates plus labor and material cost for each quote. Running it across the pipeline is a Monday morning job rather than a per-quote one.

Before You Start

• A quote is only eligible if it is saved, has a product selected, and has a quantity greater than zero. Quotes missing any of those are excluded from the run.
• Products need routings. A quote for a product with no routing will fail, because there are no operations to schedule.
• Understand the selection rule, because it is what decides which quotes are included. It is the next section.

The Selection Rule

This is the whole trick, and it is worth getting right before you click anything.

Unchecked means catch up: bring the un-simulated quotes in this filter up to date. Checked means refresh: re-run these specific quotes and overwrite whatever they had.

Running the Batch

1. Open the Quotes screen.
2. Apply the filters that define your set. Filtering to Draft status, or to a single customer, are the two most useful.
3. Leave every row checkbox unchecked.
4. Click Run Simulation.
5. Read the confirmation dialog. It shows the eligible count. Check that number against what you expected before continuing.
6. Confirm.

While the batch runs, a progress message tracks which quote is being simulated and how far through the list it is. The quotes are simulated one at a time rather than in parallel, so a large batch takes proportionally longer. Forty quotes take about forty times one quote.

What Each Simulation Produces

Every quote in the batch comes back with the same set of results, which is what makes a batch worth running rather than eyeballing lead times.

• Estimated start and end dates, produced against finite capacity rather than a flat lead time.
• Estimated total hours, which is work hours rather than wall-clock elapsed time. A job that spans a weekend but only uses four hours of work on the Friday costs four hours, not forty-eight.
• Estimated labor cost, from the assigned work hours at each work center's rate. The rate on a routing step is used when one is set there, and the work center's own rate is the fallback.
• Estimated material cost, from the material-type work centers on the routing, falling back to the product's unit cost times quantity when the routing produces no material figure.

Two behaviors are worth knowing before you trust a batch. Simulation runs at full utilization, so a quote's dates can be tighter than the same job will get once it is a live order carrying a schedule-at-utilization cap below 100. And pricing is only calculated from markup when the quote's unit price is still zero, so a price somebody typed by hand is never overwritten by a batch run.

Reading the Summary

A single quote simulation opens the result window automatically. A batch does not, because forty result windows would be worse than none. Instead, one summary dialog appears at the end showing how many succeeded, how many failed, and the first few failures by name.

Work the failures from that list rather than hunting through the grid. Failures cluster: one missing routing on a popular product can account for most of a batch's failures on its own.

How to Check It Worked

Go back to the grid and look at the estimated dates and cost columns on the quotes you expected to change. Populated values are the confirmation, and the simulated flag on each row tells you which quotes now carry results.

Then open one quote and check its detail: see how to see the cost breakdown of a quote. Spot-checking one quote from a batch of forty is the cheapest way to catch a systemic problem, such as a work center with no rate set producing labor costs that look far too low.

A Quick Worked Example

A sales engineer has 46 open quotes on a Monday, and a customer review at eleven. Twenty-nine of them were entered last week and have never been simulated.

She filters the grid to Draft, leaves all checkboxes clear, and clicks Run Simulation. The confirmation says 29 eligible, which matches what she expected, so she confirms and goes to a different task.

The summary comes back with 26 succeeded and 3 failed. All three failures are the same product, which has no routing yet. She copies a routing from a similar item, then checks just those three rows and runs simulation again. This time the check is the point: checked rows run regardless of prior status, so the three re-run and complete.

By 10:15 all 46 quotes carry dates and costs, and the review works from real numbers rather than from three-week-old estimates.

Common Mistakes

Checking rows when you meant to catch up. Ticking rows narrows the run to those rows. If you want every un-simulated quote in the filter, clear the checkboxes.

Ignoring the eligible count. That number in the confirmation dialog is your last chance to notice that the filter was wrong. A count of 300 when you expected 30 means you are about to simulate the whole pipeline.

Reading the skipped count as excluded. Checked rows that were already simulated still run and still get overwritten. The count is informational.

Expecting the batch to be fast. Quotes run sequentially by design. Start a large batch when you can leave it alone.

Quoting from a stale simulation. A quote simulated before a routing change still carries the old numbers. Re-check those rows and run again: see how to build and price a quote.

Next Steps

For the single-quote version and how the dates are produced, see how to simulate a delivery date for a quote and EDGEBIC quote simulation explained. To clear the most common batch failure ahead of time, run how to find which products have no routing.

Once a quote is won, see how to convert a quote into a manufacturing order. For the full task library, see the EDGEBIC how-to hub, and for the platform overview, EDGEBIC.