Re-Simulating a Quote After a Change in EDGEBIC

Re-simulating a quote in EDGEBIC re-runs the finite capacity engine against your current shop and re-stamps every estimated number, while a price you typed by hand is never overwritten. In EDGEBIC by User Solutions, a quote's dates and costs are a snapshot of the shop at the moment you last simulated. Routings get edited, rates get updated, and the schedule fills up. When any of that happens, the old quote is stale, and the fix is a re-run. This post covers when to re-simulate, what changes, and the one rule that trips people up: auto-markup fills the price only when it is zero.

A quote is a point-in-time snapshot

When you simulate a quote, EDGEBIC computes the estimated start, end, work hours, and the labor and material cost split from the routing and capacity as they stand at that instant. Nothing in a saved quote updates itself afterward. That is by design, because a quote is a record of what you promised on a given day, not a live dashboard.

The consequence is that a quote can silently drift out of date. Three things push it stale:

• The routing changed. You added a step, changed a work center, or adjusted a time. The quote's hours and cost were computed from the old routing.
• Rates changed. A work-center rate went up, so the labor line on the quote no longer reflects what the job costs.
• The shop filled up. More jobs are booked than when you first simulated, so the quoted dates, which competed against the old load, are now optimistic.

Any one of these means the numbers on the quote and the numbers the shop would produce have parted ways.

How to re-simulate

Re-simulating is the same action as the first run: open the quote and click Simulate. EDGEBIC runs the real scheduling engine against your current capacity, produces a fresh schedule for the quoted job, and overwrites the estimated start date, end date, work hours, and the cost split. Work hidden in sub-assemblies rolls up on the re-run just as it does on the first, so a product whose effort lives in child routings reports its true hours again.

The old simulation is not archived; it is replaced. If you need to preserve a prior promise for the record, that is what the converted order and the quote-versus-actual comparison are for, not a second saved simulation.

The one rule: a typed price survives

Here is the behavior that surprises planners. Auto-markup fills the unit price only when it is currently zero. Once you type a price, every later simulation leaves it alone.

That protects you from having a carefully negotiated price wiped out by a routine re-run. But it has a flip side: if the cost changes on a re-simulation and you had already typed a price, the price does not follow the cost. The cost line moves, the price stays, and the real margin quietly shifts.

So after a re-run, make a deliberate choice about price:

• Keep the typed price. Valid when you set it on purpose and still want it. Just confirm it against the new cost.
• Re-derive from the new cost. Clear the unit price to zero and re-simulate, or click Apply Markup to Unit Price. Either recomputes the price as effective cost times one plus the markup percent, divided by quantity.

The full cost math behind that price lives in pricing a quote from the schedule.

The refresh banner and expiry are your reminders

You do not have to remember all of this on your own. When rates or capacity change after a simulation, the quote view shows a banner asking you to refresh and re-run before you send. Treat the banner as a hard stop, not a suggestion.

Expiry is the slower-moving version of the same idea. The default quote expiry is 30 days because a cost and date computed against a month-old shop are unreliable. When a quote passes its expiry without a decision, its status can move to Expired, a signal that it needs a re-run before it goes back out. The reasoning is covered in quote expiry dates.

A short worked sequence

You quoted product SB-200 at 200 units three weeks ago: 34.75 work hours, roughly $1,400 cost, priced at $8.75 per unit with the default 25 percent markup. Since then the Drilling work center's rate rose, and two large jobs booked into the same week.

You open the quote and see the refresh banner. You re-simulate. The engine now competes the job against the fuller schedule, so the estimated end moves out by two days, and the higher Drilling rate lifts the cost to about $1,520. Your $8.75 price, typed weeks ago, is untouched, which means the margin has compressed.

You decide the new cost is right and you want your original markup back, so you clear the price to zero and re-simulate. The price re-derives to roughly $9.50. You confirm the new date against the customer's requirement, and send an honest quote instead of a stale one.

The takeaway

Re-simulating a quote is how you keep a promise honest as the shop moves under it. Re-run whenever the routing, the rates, or the load change, and let the refresh banner and the 30-day expiry catch what you forget. The engine re-stamps the dates, hours, and cost split from current reality, but it never overwrites a price you typed, so after every meaningful re-run decide whether to keep that price or clear it and let the markup re-derive. See the whole quoting flow in the EDGEBIC quoting guide, the capacity reasoning in finite versus infinite capacity scheduling, and the platform in full on the EDGEBIC overview.