EDGEBIC Daily Capacity Overrides Explained: Change One Day's Hours

EDGEBIC by User Solutions lets you override a single work center's capacity for a single day, raising it for overtime or lowering it for a short shift, without touching the standing shift calendar, and the override wins for exactly the day and machine it names. Real plants are full of one-off exceptions: an overtime Saturday, a half-day for training, an extra machine online for a rush, a partial closure. The daily capacity override is the mechanism for telling the scheduler about those exceptions surgically, so the exception stays an exception.

This sits on top of the normal shifts and calendars that define your standing pattern. The pattern handles the rule; the override handles the day the rule does not apply.

One Day, One Machine

An override names a specific work center and a specific date, and sets that resource's available hours for that date. Everything about how the day is otherwise scheduled follows the normal rules; only the supply number for that one day on that one machine is replaced.

That precision is the entire value, and it is best understood against the alternative. The shift calendar is a repeating pattern: Mondays look like this, Saturdays look like that. If you edit the pattern to cover one overtime weekend, you have changed every weekend, and the scheduler will plan overtime you do not have on all of them. An override changes exactly one date and leaves the pattern intact, so next Saturday is still a normal Saturday.

Precedence: The Override Wins Where It Applies

Capacity for a work center on a given day comes from a fixed order of precedence, and knowing it removes any doubt about which number the scheduler used. A daily override for that exact date and work center takes priority. Absent that, a broader monthly-level override applies. Absent both, the normal shift-calendar formula produces the number. For the full walk of that calculation, see how EDGEBIC resolves capacity day by day.

The rule is simple to hold in your head: the most specific statement wins. The override you set for one day is the most specific statement there is, so it governs that day, and nothing else you did not touch changes.

Either Direction

An override can raise or lower capacity, and both directions are legitimate representations of reality.

Lower it when supply genuinely shrinks: a short shift, reduced staffing, a partial holiday, a machine down for part of the day. The scheduler then books less that day and pushes the overflow to days with room. Raise it when supply genuinely grows: an overtime shift, an extra instance you are bringing online. The scheduler is then allowed to book more that day. What the override never does is let you wish capacity into or out of existence dishonestly; it is a record of a real change in what the machine can do on that date.

Why It Is Its Own Mechanism

It would seem simpler to just edit the shift for the day, and the reason EDGEBIC does not fold overrides into shift editing is worth stating. First, surgical scope: editing a repeating pattern changes every occurrence, while an override changes one date. Second, a visible record: the override is a deliberate, inspectable statement that this specific day was different, which a quietly edited and then re-edited pattern never preserves. When you later ask why the schedule planned overtime on the twelfth, the override is the answer sitting right there.

That combination, precise scope plus a durable record of intent, is why the override is a first-class mechanism rather than a shortcut through the calendar.

Reading Whether It Worked

A common surprise is adding an overtime day and finding the schedule did not fill it. Usually that is correct behavior, not a fault. Capacity is permission, not compulsion: if the work that would fill the extra hours cannot move into that day because of dependencies, material timing, or an upstream due-date constraint, the hours sit available and unused. The override raised the ceiling; nothing was free to rise to it.

The way to confirm is the resource load view. After re-running the schedule, read that day for the machine: if the hours now show available and jobs have moved in, the override did its job. If the hours show available but empty, the constraint was never that machine's capacity, and adding more will not help. Also check the obvious, that the override landed on the right work center and the right date, because an override on the wrong resource raises capacity where nothing was waiting.

Where It Fits

Daily overrides are the fine adjustment layer of the capacity model. The shift calendar sets the standing supply, work center groups pool it, and overrides handle the day-by-day exceptions on top. For the whole configuration surface, scheduling policy and shift setup cover the standing rules, and the complete EDGEBIC guide maps the whole system.

The Point of a Surgical Exception

A capacity model that could only be changed by editing its repeating rules would force you to choose between an inaccurate plan and a corrupted pattern. The daily override resolves that: it lets one day be different, honestly and visibly, while every other day keeps following the rule. That is what makes finite capacity planning survive contact with a real plant, where the exception is not the exception, it is Tuesday.

Want to model your overtime and short shifts without breaking your calendar? Bring an export to a demo and we will set up a few overrides.