What Is the Capacity Override Resolution Chain?

The capacity override resolution chain is the fixed priority order that decides how many hours one work center, shift, and date cell offers to the schedule: a daily override first, then a monthly override, then the standard shift formula. The first rule that matches produces the number and the remaining rules are never consulted. EDGEBIC by User Solutions uses this single chain everywhere capacity is quoted, so the number a planner sees on a calendar cell is the same number the scheduling engine books against.

How it works

Every capacity figure in the plant resolves down to one question asked of one cell: for this machine, on this shift, on this date, how many hours are available? The chain answers it in three steps.

The first step looks for a daily capacity override, a planner-entered value attached to that exact combination of work center, shift, and date. If one exists, its hours are the answer and the search stops immediately. This is the sharpest instrument available, because it names a single cell and nothing else.

The second step, reached only when no daily override exists, looks for a monthly capacity override whose date range covers the date in question. A monthly override is the broad brush: it says something about a stretch of days rather than one of them. If one applies, its hours become the answer.

The third step is the fallback and the normal case. With no override of either kind, the shift formula computes the capacity from the shift's working hours for that day of week, less any holiday or downtime that removes hours, then scaled by the work center's utilization percentage and multiplied by the number of machine instances. Most cells in a healthy plant resolve here, which is why the formula is worth understanding even when overrides are rare.

The important property of a chain is that it is exclusive rather than additive. Levels do not stack, blend, or average. Exactly one of them produces the number. That is what makes capacity explainable: for any cell you can name the single rule responsible, and if the number is wrong you know precisely which rule to change.

A concrete example

Think of a shop's posted opening hours. The default sign on the door says weekdays nine to five, and that is the general rule everyone works from. In December the owner tapes up a notice saying the shop closes at three all month for the holiday season. And on one particular Tuesday, a handwritten card on the glass says closed today, engineer visiting.

A customer arriving that Tuesday reads the handwritten card and goes home. They do not average the three notices together, and they do not follow the December notice because a more specific one is in front of it. The following Wednesday, with no card on the glass, they follow the December notice and arrive before three. In January, with both the card and the December notice gone, they are back to the standard sign.

The handwritten card is the daily override, the December notice is the monthly override, and the posted opening hours are the shift formula. Same chain, same rule: the most specific notice present is the one that counts.

In a plant, that Tuesday card is a planner setting the press to zero hours because maintenance has it. The December notice is a month of reduced second-shift hours entered once as a range. And every other cell in the year quietly resolves from the shift formula.

How EDGEBIC uses it

The chain runs behind both the planning screens and the scheduling engine, which is the point: the Resource Calendar, the capacity views, and the engine all resolve a cell the same way, so nobody plans against a number the scheduler will not honor. The day by day walkthrough is in how EDGEBIC resolves capacity day by day.

The two override levels have their own glossary entries. The sharpest one is capacity override, and the broad range version is monthly capacity override. Setting a single day is walked through in how a daily capacity override replaces the formula, and the most common confusion the chain causes is diagnosed in a daily capacity override was ignored.

Because the chain is exclusive, troubleshooting capacity is a matter of identifying the matching level rather than editing every level at once. For the wider vocabulary, see the manufacturing glossary, and to see capacity resolved against a live plan, explore EDGEBIC.