Turning On Weekend Production in a Quote Scenario in EDGEBIC

Turning on weekend production in a quote scenario lets the EDGEBIC simulation use Saturday and Sunday shifts, spreading the same work across more days so the estimated finish moves earlier. In EDGEBIC by User Solutions, a scenario is a named what-if variant of a quote, and weekend production is one of its calendar levers. The standard shift calendar usually runs weekdays only, which parks a long job across the weekend. Allowing weekend shifts recovers those idle days. The key thing to understand is that it compresses the calendar span, not the work content: the hours are the same, the finish is sooner.

What the switch changes

A finite capacity simulation places work only on days the shift calendar says a work center is open. If that calendar covers Monday through Friday, a job that runs long enough to reach Friday evening waits until Monday to continue. Every weekend the job crosses adds two idle days to the span between start and finish.

Weekend production is the scenario switch that opens Saturday and Sunday. With it on, the simulation may place work on weekend shifts, so a job that would have paused across the weekend keeps going. The span between start and finish shrinks by the weekend days it recovers.

Nothing about this touches the live schedule. Scenario runs are in-memory and write nothing to real jobs. It is one more knob in the same family as a capacity boost or a custom start date, all bounded by what a scenario can and cannot change in EDGEBIC.

Hours stay the same, the date moves

This is the point planners most often get wrong, so it is worth stating plainly. Weekend production does not add work. The job still contains the same number of work hours. Those hours simply get to run on days that were previously closed.

Two consequences follow:

• The finish date moves earlier, because the calendar span between the first and last hour of work is shorter when fewer idle days sit in the middle.
• The cost stays roughly the same, because cost is work hours times work-center rates, and neither changed. It moves only if your weekend shifts are configured with different rates than weekdays.

So weekend production is a lever on the date, not the cost. That is different from boosting a work center's capacity, which can genuinely change how the hours land, covered in boosting a work center's capacity in a quote scenario.

When it helps and when it does not

Weekend production only recovers days the job would have lost to a weekend. If the whole routing runs and finishes inside a single work week, there was no weekend in the way, and enabling the switch changes nothing.

It also assumes something the simulation cannot: that you can staff and run those weekend shifts. The engine models the shifts as available; it does not find you a crew. Treat a weekend scenario as a test of whether lost weekend days are your constraint, then confirm the labor before you promise the date.

A worked example

A customer wants a ten-day job, and the standard weekday simulation shows it finishing on the 26th. The job starts on a Wednesday and straddles two weekends, so ten days of work stretches across a fourteen-day calendar span, with four idle Saturday and Sunday days baked in.

You build a scenario, turn on weekend production, and re-simulate. Now the four weekend days carry work too. The span collapses back toward the raw ten days of content, and the finish lands on the 22nd, four days earlier. The cost is essentially unchanged, because it is the same ten days of work at the same rates.

You take that to your floor supervisor, confirm you can crew both weekends, and quote the 22nd. Had the job instead finished on a Thursday within one week, the weekend scenario would have returned the same date as the base run, telling you the calendar was never the problem.

Read it forward, like every scenario

The weekend result, like every scenario output, is a forward simulation. It begins at the scenario's start date and reports when work finishes. For a finish-by promise, compare the weekend scenario's estimated end date against the customer's date yourself, since the just-in-time framing of a backward quote does not carry into scenarios.

The takeaway

Weekend production is the scenario switch that opens Saturday and Sunday shifts, recovering idle weekend days so a long job finishes sooner. It compresses the calendar span, not the work content, so the date moves earlier while the hours, and usually the cost, hold steady. It helps only when the job would otherwise sit across a weekend, and it assumes you can actually run those shifts. Test it as a what-if, confirm the crew, and quote the earlier date with confidence. See the full flow in the EDGEBIC quoting guide, the capacity fundamentals in finite versus infinite capacity scheduling, and the platform in full on the EDGEBIC overview.