Running a Weekend on a Capacity Override to Hit a Due Date in EDGEBIC

Running a weekend on a capacity override in EDGEBIC by User Solutions means opening a single closed day for one work center so the engine can place work there and hit a due date, without touching the recurring shift calendar. This walkthrough recovers a job that would finish late over a closed weekend by adding one Saturday override, and watches the engine create a synthetic override-day slot to hold the work. It is one of the worked examples we publish so the mechanics are visible in numbers.

An override is the lighter touch next to a permanent second shift, covered in adding a second shift to break a bottleneck. For the calendar model underneath both, shifts and calendars explained is the companion.

The Cast: One Assembly Job, One Closed Weekend

Brightwater Assembly has a job that the calendar is about to make late:

Step 1: See the Late Result

Run Drive Schedule as it stands. ASSY-1 can offer 8 hours Friday, nothing on the closed weekend, then 8 hours Monday and 4 hours Tuesday:

The job finishes Tuesday. It is due Monday. The weekend gap is real calendar time that costs zero machine-hours, and it pushed the finish a day past the due date. The whole shortfall is those two closed days.

Step 2: Open Saturday With an Override

Rather than add a permanent Saturday shift, open just this one Saturday for just this one machine. Add a capacity override of 8 hours for ASSY-1 on this Saturday. You can double-click the capacity cell for ASSY-1 and that date on the Dashboard, or open the capacity chart from the Work Center grid and enter the hours there.

An override is read at top priority. The engine resolves a day's capacity in a fixed order: a per-day override first, then a broader date-range override, then the shift formula. So the 8 hours you entered for Saturday are used verbatim, regardless of the fact that Saturday has no shift in the recurring calendar.

Step 3: Watch the Synthetic Slot Appear

Reschedule. At the start of the run, the engine rebuilds its capacity slots. Because the override covers a day that has no configured shift, it creates a synthetic override-day slot for Saturday: a slot with no regular shift attached, carrying the 8 override hours. This synthetic slot is considered after the regular-shift candidates, so the engine reaches for it exactly when it needs the extra day.

Now the job flows:

The job runs 8 hours Friday, 8 hours on the Saturday override, and its last 4 hours Monday morning, finishing Monday at noon. On time. One override for one date recovered the due date, and the recurring calendar is untouched: next weekend ASSY-1 is closed again unless you add another override.

Step 4: The Same Dial, Three Directions

The override is not only for opening closed days. Because it wins over the shift formula, it sets a day's capacity in any direction:

• Open a closed day. The weekend case above: a day with no shift gets a synthetic slot and real hours.
• Raise a working day. Enter more than the normal shift hours for a crunch day, and the engine offers the higher number for that date. An override above the normal clock window still contributes its full hours.
• Lower a working day. Enter fewer hours for a partial closure, a training morning, or planned maintenance, and the engine offers only that.

All three are one-time, per work center, per date, and none of them edit the recurring calendar. For a broad, planned capacity change across a range of dates you would use a date-range override; for a single day, the per-day override is the precise tool.

What This Walkthrough Proves

1. An override sets one day's capacity exactly. It is read ahead of both the date-range override and the shift formula.
2. A closed day can be opened for one run. The engine creates a synthetic override-day slot for a day with no shift and places work there.
3. The synthetic slot is used when needed. It is considered after regular-shift candidates, so the engine reaches for it to hit a due date.
4. The recurring calendar is untouched. The override is a one-time, per-date change, not a new shift.
5. The dial goes both ways. The same override opens a closed day, raises a busy one, or lowers a partial-closure day.

If a capacity override does not seem to take effect on the next run, the two usual causes are that it is on the wrong work center or date, or that the work never reaches that day because earlier shifts absorbed it. Both, along with the subtler timing cases, are covered in a daily capacity override was ignored.

From One Override to a Responsive Plant

A capacity override is the surgical capacity move: one day, one machine, no permanent change. It sits alongside the blunter levers of a second shift or a new work center. When the shortfall is a real weekly pattern rather than a one-off, adding a second shift to break a bottleneck is the durable answer, and when a job is late because of a disruption rather than a closed calendar, the machine breakdown reschedule walkthrough shows the recovery path.

User Solutions has helped manufacturers flex capacity to hit dates since 1991, work that took GE Railcar from 30 percent to 90 percent on-time. Contact us for a demo and bring one at-risk due date: we will find the day worth opening with you.