EDGEBIC Monthly Capacity Overrides Explained: Budgeting a Whole Season

EDGEBIC by User Solutions lets you state a work center's capacity as a total-hours budget across a date range, and the scheduler spreads that budget evenly across the available days in the window. This is the coarse dial in the capacity model. Where a single-day change answers "what can this machine do on the twelfth", a date-range override answers "how much can this machine deliver between June and August", which is the question a seasonal decision, a maintenance week, or a staffing change is usually made in.

The name says monthly, but the mechanism is a date range. A few days, two weeks, a quarter: any window you can name a start and an end for is valid.

A Budget, Not a Daily Number

The distinction that matters is what you are entering. A daily capacity override is a per-day figure: these are the hours available on this date. A date-range override is a total: this is what the resource can deliver across the whole window. EDGEBIC then distributes that total across the days inside the range that are actually available.

That distribution rule carries a consequence worth stating plainly. Non-working days get no share. If the window includes weekends the plant does not run, holidays, or dates the work center is otherwise closed, they are not counted when the budget is divided. A 400-hour budget over a calendar month is not 400 divided by 30. It is 400 divided by the working days inside that month for that machine, which is the honest arithmetic and the one that matches how the plant experiences the period.

Precedence: Most Specific Wins

Capacity for a work center on any given day resolves in a fixed order, and this chain is the single most useful thing to hold in your head when a number surprises you.

The first match wins outright. When a daily override exists for a date, the monthly override covering that same date is not blended, averaged, or partially applied. It is ignored for that day. That is deliberate: two numbers for one day need one winner, and the more specific statement is the one the planner made most recently and most deliberately about that exact date.

For the day-by-day walk of the whole calculation, including how holidays and downtime enter it, see how EDGEBIC resolves capacity day by day.

No Overlapping Ranges

Two date-range overrides on the same work center cannot cover the same day. There is no defined answer to "which budget owns this Tuesday" when two claim it, so EDGEBIC does not allow the ambiguity to exist. Saving a range that overlaps an existing one resolves the conflict by replacing what it overlaps rather than stacking a second claim on top.

The working rule is one budget statement per work center per stretch of calendar. If you need a different number for part of a window, either split the range at the boundary or, more often, leave the range alone and put a daily override on the days that differ.

When to Reach for It

Reach for a date-range override when the decision you are recording was made as a period, not as a day.

• A season. Summer reduced hours, a holiday-period slowdown, a peak-season push where the line is staffed heavier for eight weeks.
• A maintenance window. A machine running at partial capability for a stretch while a rebuild proceeds around production.
• A staffing change with a known end. A temporary crew, a training program, a contractor engagement that runs to a date.
• A commitment. A resource partly reserved for a customer program over a quarter, leaving a known remainder for everything else.

Reach for a daily override instead when the change is one date: an overtime Saturday, a half-day for training, one machine down for a shift. And reach for shifts and calendars when the change is the standing rule itself, not an exception to it.

Why Not Just Edit the Shift Pattern

Because a shift pattern is permanent until somebody edits it back, and a date range ends by itself.

A seasonal change entered into the shift calendar has no expiry. It changes every occurrence of that weekday, forever, which means the correctness of next winter's plan depends on a person remembering in September to undo something they did in June. That is not a control, it is a hope. A date-range override carries its own end date, so the day after the range closes the standing calendar resumes with no cleanup, no memory, and no risk that a temporary decision quietly became the shop's permanent baseline.

There is a second reason, which is that the override is a record. When someone asks in November why August was planned light, the range is sitting there with its dates and its reason. A shift pattern that was edited and later edited back preserves nothing.

Reading Whether It Landed

If a range does not appear to be doing anything, work the precedence chain from the top.

First, check for a daily override on the days you are looking at, because a daily figure silently wins and is the most common explanation for a range that seems ignored. Second, check the dates: a range that starts one day after the period you meant leaves the first day drawing from the standing calendar. Third, check the availability of the days inside the window, since the budget only spreads across days the work center actually runs, and a window heavy with holidays concentrates the same total into fewer days than you expected, raising the per-day figure rather than lowering it.

Then re-run the schedule and read the resource load view across the window. Capacity is permission, not compulsion: a lowered budget will push work out of the period, but a raised budget only gets used if there is work free to move into it.

Where It Fits

Date-range overrides are the middle layer of a three-layer capacity model. The shift calendar sets the standing supply, the range override states a period budget on top of it, and daily overrides handle the individual dates that break both. Each layer is more specific than the one below and wins where it applies.

Used that way, the model stays readable. The pattern explains the normal week, the range explains the season, and the daily override explains the twelfth. For how the rest of the system fits around them, the complete EDGEBIC guide maps the whole product, and /edgebic covers what the platform does.

The Point of a Period Budget

Plants do not only change one day at a time. They change for a season, for a program, for the duration of a rebuild, and a capacity model that can only speak in single days forces those decisions to be typed in one date at a time and then untyped later. The date-range override lets a period decision be entered as a period, spread honestly across the days that exist inside it, and expire on its own. That is what keeps a finite capacity plan aligned with how the business actually decided to run.