Why a Quote Scenario Respects Maintenance Downtime in EDGEBIC

A quote scenario in EDGEBIC reads the same maintenance downtime, holidays, and daily capacity overrides that the production scheduler uses, so a what-if runs against your real constrained calendar rather than an idealized one. In EDGEBIC by User Solutions, it is tempting to assume a simulation shortcuts reality to give a fast answer. It does not. A scenario honors the configured days a machine is down, the plant holidays, and any per-day capacity change, exactly as a live scheduling run would. That is precisely why the date it returns is one you can send to a customer.

The trap a what-if could fall into

A quote is a promise, and a promise is only as honest as the calendar behind it. The classic way estimating goes wrong is a lead-time rule of thumb: take the work content, divide by a nominal daily rate, and call it a date. That method ignores the days the shop is not fully running, so it consistently promises finishes the floor cannot hit.

A simulation that ran against an unconstrained calendar would make the same mistake in fancier clothing. If a what-if pretended every machine was available every day, it would hand you a date that looks precise and is still fiction, because it skipped the maintenance window and the holiday sitting right in the middle of the job.

EDGEBIC avoids this by giving the scenario the same calendar the real schedule obeys.

One calendar, two consumers

Maintenance, holidays, and per-day capacity changes are configured once, as plant holidays and per-day capacity overrides. Two things read that configuration: the production scheduler that plans real jobs, and the scenario simulation that answers what-ifs. There is no second quoting calendar to keep in sync.

Worth naming the mechanism precisely, because "maintenance downtime" sounds like its own record. The current release has no downtime screen, so a machine's maintenance day reaches the calendar as a per-day capacity override on that work center, shift, and date. That is the thing the scenario reads.

Concretely, a scenario reads:

Because both consumers share the source, marking a machine down once is enough. Every future scenario reflects it automatically, with no extra step at quoting time. When the base quote simulation loads plant holidays, and a scenario additionally loads the daily and monthly overrides, the what-if is running on the same constrained ground as production.

Why this makes the promise credible

The payoff is a date that already accounts for the days the shop is not fully running. You do not simulate a clean calendar and then mentally add two days for the maintenance you remembered. The two days are in the number.

This is the difference between a date that survives contact with the floor and one that collapses on the first weekend or holiday. It is the same reason a real finite capacity plan beats a rule of thumb, explored in what makes a promise date credible in EDGEBIC. A scenario inherits that credibility because it inherits the calendar.

A worked example

A customer wants a rush job that needs the mill, and you want to test whether a second-shift capacity boost gets it done in time. You build a scenario, add the capacity override, and re-simulate.

The mill, though, is down for two days of preventive maintenance next week, zeroed in the calendar with per-day overrides weeks ago. The scenario reads that reduction. So even with the capacity boost active on the days the mill is running, the simulation leaves the two maintenance days empty and schedules the work around them. The estimated finish includes the two-day gap.

That is the honest answer. Had the scenario ignored the maintenance, it would have promised a date two days too early, and the job would have run into a locked-out machine. Instead you get a date that a planner can defend, because it already respects the downtime that is really coming.

If the finish comes back later than you expected and the shop looked open, the same mechanism is usually the reason: a holiday, a reduced-capacity training day, or a maintenance window that is configured but not front-of-mind. Open the calendar for the work centers on the routing, find the constraint, and the date makes sense. If the constraint is stale, fix it in the calendar and re-simulate, and the scenario moves with it.

Keep constraints in the calendar, not in your head

The practical discipline follows directly. Enter maintenance, holidays, and capacity changes as soon as you know them, using the plant holiday screen for site-wide closures and per-day overrides for anything narrower. That is the single source both the schedule and every quote read. A maintenance window remembered only in someone's head is invisible to the simulation, and a quote built without it will promise a date the shop cannot keep.

Kept in the calendar, the same fact protects both your live schedule and your quotes, with no double entry and no chance the two disagree.

The takeaway

A quote scenario is not a shortcut around reality; it reads the same maintenance downtime, holidays, and daily capacity overrides the production scheduler reads, so a what-if runs against your real calendar. That is what lets a scenario's date be a promise rather than a guess: the days the shop is down are already in the number. Keep every constraint configured in the calendar, and both your schedule and your quotes will tell the same honest story. See the full flow in the EDGEBIC quoting guide, the constraint fundamentals in production bottleneck identification, and the platform in full on the EDGEBIC overview.