How a Daily Capacity Override Replaces the Formula

A daily capacity override is a per-date value that replaces the standing capacity formula for one work center, shift, and day. When an override exists, EDGEBIC by User Solutions uses that number as the available hours instead of computing them from base shift, utilization, and instances, and it honors the override at a single point that both the scheduler and the capacity dashboards read. It is the surgical way to model a one-off overtime day, a short-staffed day, or any single date whose real capacity differs from the routine, without disturbing the calendar that governs every other day.

The standing capacity formula is excellent at describing a normal day: base shift hours, minus downtime and holidays, scaled by utilization and machine count. But real shops have days that are not normal. An authorized Saturday. A training morning that halves the crew. A machine you decide to run three shifts on for one week only. Editing the standing setup to model these would change every day, which is exactly wrong. The override exists so the exception can be handled as an exception.

Formula by default, override by exception

For any work center, shift, and date, EDGEBIC first asks a simple question: is there an override for this exact slot? If not, it computes capacity from the formula as usual. If there is, it uses the override number and ignores the formula for that slot.

This is a replace, not an add. The override does not layer on top of the computed hours; it stands in for them. That is what makes it precise. You are stating, for this one date, "the available hours are exactly this," and the engine takes you at your word. Everywhere you have not placed an override, nothing changes and the formula governs as before.

There is a natural precedence when several capacity rules could apply. A per-date override is the most specific statement about a slot, so it wins over a monthly capacity pattern, which in turn wins over the base formula. Specific beats general, the same principle that runs through the rest of the engine.

One number, two consumers

The design choice that makes overrides trustworthy is that they are honored at a single chokepoint. Both the scheduling engine and the capacity dashboards resolve a slot's capacity through the same path, so an override changes both at once. The hours the scheduler plans against are the hours the load chart shows, always.

This matters more than it sounds. Without a single source, it would be easy to have a scheduler that plans work into an authorized overtime shift while the capacity dashboard still shows the machine closed, or a dashboard that promises capacity the scheduler quietly will not use. By routing every capacity question through one resolution point, EDGEBIC guarantees the plan and the picture of the plan agree. This is the same cross-surface consistency discipline that keeps holidays and downtime aligned between the schedule and the load views.

A worked example: a one-off Saturday

Take a machining center that normally runs Monday to Friday, a single 8-hour day shift, three instances, 80 percent utilization. The standing formula for a weekday gives roughly 8 minus break, scaled, times three, and Saturdays are closed entirely because the shift calendar has no Saturday hours.

A rush order needs more capacity, and the plant authorizes one Saturday day shift on this center at full effort. Rather than adding Saturday to the standing calendar, which would open every Saturday, the planner sets a daily capacity override for this work center, the day shift, and that one Saturday date, entering the authorized hours, say 21 hours for three machines at full utilization.

Now the scheduler sees real capacity on that Saturday and can place work there. Every other Saturday remains closed because the standing calendar is untouched. The capacity dashboard shows the same 21 hours available on that date, so the planner watching the load chart sees exactly what the engine will fill. When the rush is over, the planner deletes the override and the center returns to its Monday-to-Friday normal with nothing drifted.

Run the same idea in reverse for a short-staffed day. If half the crew is out next Tuesday, an override entering the reduced hours for that Tuesday tells the schedule to plan less work into that day and push the overflow forward, while every other day keeps its normal capacity.

When to reach for an override

Use a daily override whenever a single date's real capacity differs from the routine and you do not want that difference to leak into other dates. Authorized overtime, a one-off closure that is not a standing holiday, a temporary extra shift, a reduced-staffing day: all are per-date facts, and the override is the per-date tool. For a change that is genuinely permanent, such as adding a machine or moving to a new shift pattern, edit the standing setup instead, because you want that to apply going forward.

The rule of thumb is scope. If the change is "this date only," override. If the change is "from now on," edit the calendar or the work center. Mixing them up is how a one-off Saturday accidentally becomes every Saturday, or a permanent second shift has to be re-entered every week.

The override sits inside the same finite-capacity discipline as everything else: a real number, honored consistently, that the multi-shift allocator fills like any other bucket. For why respecting that bucket matters, finite versus infinite capacity scheduling makes the case, and the complete scheduling engine guide shows where capacity resolution sits in the pipeline. To model your own overtime and exception days against your real load, explore the EDGEBIC engine or bring your data to a demo.