What Is a Capacity Override in Scheduling?

A capacity override is a planner-entered value that replaces a work center's normally calculated capacity for a specific day, or for a date range: instead of the engine computing available hours from the shift definition, it uses the number you entered for that cell. Set a Tuesday to zero to black out a machine for maintenance, or to six hours instead of eight to reflect a slow day, and both the scheduling engine and the capacity dashboard honor it. It is how you tell the plan about a one-off change without touching the recurring shift pattern.

This entry is part of the EDGEBIC glossary; see the manufacturing glossary for the wider vocabulary and the over-utilization check for the guardrail that watches capacity from the other side.

How a Capacity Override Works

A work center's capacity for any given day normally comes from a calculation: the shift definition says how many hours the cell runs, multiplied by how many machines it has. That formula is right most of the time, but reality has exceptions. A machine goes down for maintenance. A shift runs at reduced speed for a week. A single Saturday gets an overtime crew. Editing the recurring shift for a one-off change would be wrong, because the shift is supposed to describe the normal pattern.

A capacity override handles the exception instead. You enter a value for a specific cell, defined by work center, shift, and date, and that value replaces whatever the formula would have produced. A zero blacks the cell out entirely: no capacity, so the engine schedules nothing there. A smaller number reflects a partial day. The shift definition is untouched; only the targeted cells change.

Because the override is a real input to capacity, it flows to both the engine and the dashboard. The scheduler will not plan work into a zeroed cell, and the capacity view shows the day the way you set it. The two stay in agreement, which is what keeps the plan honest.

That agreement matters more than it first appears. A common failure in scheduling tools is a capacity change that shows up in one view but not the other: the dashboard says a machine is down Tuesday, but the engine still plans jobs onto it because the two read different sources. A capacity override is a single value that both surfaces consume, so what you see on the dashboard is exactly what the engine planned against. When you black out a day, the plan reflects the blackout, and there is no gap between the picture and the plan.

The Priority Order

Overrides come in two ranges of specificity, and there is a clear chain that decides which one applies to a given cell:

1. Day-specific override wins first. A value set for one exact date beats everything else.
2. Range override applies next. A value set across a date range (a whole month, say) applies to every day in that range that does not have a day-specific override.
3. Shift-formula capacity is the fallback. When no override covers the cell, the engine uses the normal calculated hours.

This layering is the point. You can set a broad rule (this month, shift two runs at six hours instead of eight) and still override individual days within it (except this one Tuesday, which is zero for maintenance). The most specific override always wins, so a single day's value overrides the month, which overrides the formula. It is a general rule with pinpoint exceptions, expressed cleanly.

A Concrete Example

The maintenance team books the press for all of Tuesday. Left alone, the scheduler would happily plan jobs onto the press that day, because the shift formula still shows a normal shift.

The planner enters a day-specific capacity override of zero hours for the press on Tuesday. The engine now sees no capacity in that cell and schedules nothing there; the capacity dashboard shows Tuesday blacked out. Because a day-specific override outranks any broader rule, it holds even if a month-level override or a normal shift also covers the press. When maintenance finishes, the planner clears the Tuesday override and the press reverts to its calculated hours automatically.

For the reduced-speed case, the same tool applies inverted: a range override across a month drops a shift to six hours, and day-specific overrides on the handful of full-speed days pin those back to eight. The month runs reduced except where a specific day says otherwise.

How EDGEBIC Applies a Capacity Override

In EDGEBIC by User Solutions, you enter a capacity override against a work center, shift, and date, setting the hours that cell should hold. A value of zero blacks the cell out. Both the scheduling engine and the capacity dashboard read the override, so the plan and the reported capacity agree. The override is a targeted change: it never edits the underlying shift, so clearing it returns the cell to its calculated value.

The most common use is blocking a machine for a specific day, which has its own recipe: see how to block a machine for a maintenance day and, for a bounded interruption rather than a whole day, how to schedule a downtime event for a machine. For giving a cell its own recurring pattern rather than a one-off change, see how to give one work center its own calendar and the broader shifts and calendars overview.

Capacity overrides are one of the tools that make finite capacity scheduling match the real plant: the engine plans against the hours a machine actually has that day, not a textbook average. Use them for the exceptions, keep the shift for the pattern, and the plan will reflect the floor as it truly runs.