How to Quote a Rush Order in EDGEBIC

To quote a rush order in EDGEBIC by User Solutions you first test the date with a backward finish-by simulation, then build a scenario that adds the capacity needed to hit it, and finally re-price for the expedite. The quote simulation runs the real engine against your current load and throws the temporary job away: it does not hold capacity. So a rush quote is an honest what-if, and protecting the promise means making the capacity change real before you convert.

For the scheduling side once a rush order is already on the board, read how to schedule a rush order. This task is documented behavior of EDGEBIC, and the full task library is in the how-to hub.

Before You Start

• The quote exists and is simulated once as a baseline, so you know the standard date and cost.
• You know the customer's requested date and which work center gates the job.
• The product's work centers have rates, so the expedited cost prices correctly.

Step 1: Test the Date Backward

Open the quote in edit mode. Set Scheduling Direction: to Backward and Target Start Date: to the customer's requested date. Click ▶️ Simulate. Backward schedules the job as late as possible while finishing on or before that date, with an earliest start of today.

Read the result:

• End Date on or before the requested date: the standard plan already fits. Quote it.
• End Date after the requested date: the backward plan did not fit and the engine fell back to forward. You need a capacity lever. This is the honest "not as-is, and here is where it lands."

The backward mechanism is explained in how EDGEBIC turns a quote into a promise date.

Step 2: Build a Capacity Scenario

When the standard plan misses, open 📊 Scenarios on the quote and create a scenario named after the lever, such as 2nd Shift on Mill. Add a Work Center Capacity Override on the bottleneck and set Capacity % to 150 for a second-shift equivalent, or tick Weekend Production: for a weekend push. Click Run Simulation.

Step 3: Confirm and Compare

Read the scenario's Estimated End Date: against the requested date. Build one or two alternative levers (weekend vs second shift) and compare them on the Comparison Analysis tab, watching the Utilization chart so the winning plan still has slack for a breakdown.

Step 4: Apply and Re-Price

Select the winning scenario and click Apply to Quote. Its dates and cost land on the quote. Because the expedite likely raised cost, re-price: set a Manual Cost Override to the all-in figure or raise Markup %, then apply markup to the unit price.

Worked Example: 200 Units, Wanted by August 8

Acme wants 200 units of Widget-A by August 8. You already have the quote simulated as a baseline: forward, start July 20, end August 14, cost $9,230. That is six days late, so the standard plan does not fit.

First you confirm it with a backward test. You set Scheduling Direction: to Backward, Target Start Date: to August 8, and simulate. The end date comes back after August 8, which means the backward plan did not fit and the engine fell back to forward. That is your unambiguous "not as-is."

Next you find the lever. The cost breakdown shows CNC-Mill-1 carrying 101 of the 151.5 hours, so it is the bottleneck. You open 📊 Scenarios, create 2nd Shift on Mill, add a Work Center Capacity Override on CNC-Mill-1, and set Capacity % to 150 (eight hours a day becomes twelve). Run Simulation returns end August 5 at cost $9,830, which clears August 8 with three days of margin.

You check the Utilization tab to be sure the plan is not running a machine flat out with zero slack, then select the scenario and click Apply to Quote. The quote now carries August 5 and $9,830. Because the expedite raised cost, you re-price: the margin at $85 a unit is still 42.2%, comfortably green, so you leave the price and note the higher cost. Finally, before converting, you arrange the real second shift on CNC-Mill-1 in the capacity data, because the quote never held that capacity for you and the live run reproduces the standard plan until the shift is real.

What Changes When You Save

Applying the scenario writes its dates, hours, and cost onto the quote. Re-pricing updates the unit price and margin. None of this holds capacity or changes the real calendar. The scenario capacity boost is a what-if only. To honor the rush date, you must make the second shift or override real in the capacity data, then convert and schedule the order.

Why the Quote Does Not Hold the Slot

The most important honesty about rush quoting: the simulation does not reserve capacity. It runs the real engine against your current load, reads the dates and cost, and deletes the temporary job. No slot is held. There is no capacity-reservation mechanism, so quoting the rush does not block that machine time against other work that comes in tomorrow. If two quotes both simulate into the same open window, both will report it as available, because neither one took it.

That is why the last step is never optional. To actually honor a rush date you place and schedule the order, which is the act that commits the capacity, and you make any capacity change real in the calendar first. Treat the simulated promise as an honest estimate of what the shop could do, not a guarantee that the shop has set the time aside. The estimate is trustworthy; the reservation is something you create by scheduling.

How to Check It Worked

Confirm the quote now carries the scenario's end date on or before the requested date, and that the margin at the re-priced number still clears your floor (green above 20%). Before converting, verify the real capacity change is in place, because the live scheduling run reproduces the standard plan until it is.

Common Mistakes and Gotchas

• The quote does not reserve the slot. No capacity is held. Another job can still take the capacity you assumed. Place and schedule the order to protect the date.
• Backward that misses fell back to forward. An end date after the target on a backward quote means it did not fit. Treat it as a no, then add a lever.
• Applying a scenario is paper only. It updates the quote's numbers, not real capacity or the routing. Arrange the real shift or vendor change first.
• Do not quote standard cost on a rush. Price from the expedited scenario's cost. In the documented example a second shift moved cost from $9,230 to $9,830; pricing from the higher number keeps the margin honest.

The lever most rush quotes need is capacity. The mechanics of adding it live in how to add an extra shift in a scenario.