A Work Center Is Booked Past Its Shift Design: Causes and Fixes

A warning that a work center's daily bookings exceed its shift-design cap means the plan is physically possible but exceeds the working pattern you described: the sum of the shifts' maximum daily hours multiplied by the machine unit count. EDGEBIC by User Solutions reports it as a warning rather than an error, because a day that runs past its designed hours is a decision to review, not a defect to repair.

Read it as one of two statements: either the working pattern on file understates what the plant really works, or the schedule is planning overtime nobody agreed to. This post separates the two, alongside the other capacity symptoms in the EDGEBIC troubleshooting guide. For the harder version of the same family see a work center shows more hours than it has, and for the concept see what is an overtime allowance in shift scheduling.

What You Are Seeing

The anomaly report shows a warning on a work center for one or more dates, saying the daily booking exceeds the shift-design cap. The machine is not over-booked in the physical sense: nothing claims more hours than the units could run. It simply carries more hours than the shift pattern says a day should hold.

Why It Happens

Cause 1: The Shift Pattern Understates the Real Working Day

The design cap comes from the maximum daily hours on each shift, multiplied by the machine unit count. If that figure was set once as an eight-hour default and the plant actually runs nine or ten with the overtime it plans for, every busy day exceeds the cap and reports.

How to tell: the warning appears routinely, on many days and several work centers, and the excess is small and consistent.

Cause 2: The Schedule Is Planning Overtime You Did Not Authorize

The mirror image of the first cause. The pattern is accurate and the plan is genuinely asking for more hours than the shop has agreed to work. That is a real finding: someone has to either approve the hours or move work.

How to tell: the excess appears in a burst around a busy period rather than continuously.

Cause 3: A Per-Day Capacity Override Raised the Day

A per-day capacity override replaces the shift formula outright for the days it covers, and the figure typed in is used exactly as entered. Approve a Saturday, or raise a Wednesday for a push, and the engine will book those hours quite correctly while the standing shift pattern still describes a shorter day. The warning is then comparing real bookings against a cap the override deliberately stepped over.

How to tell: open the per-day capacity dialog for that work center and look at the overridden days count and the reason column. The excess tracks the days that carry an override.

Cause 4: A Synchronized Parallel Mirror Pushed the Day Over

A machine acting as a mirror in a synchronized parallel group copies its parent's window. Those copied hours can carry a day past the design cap on their own, without any second job being scheduled.

How to tell: the work center is configured as a dependent partner in a parallel group.

What the Warning Is Not

It is not the physical over-utilization finding. That one says the bookings exceed what the machines could run at all in a day, and it is a defect worth treating as a wiring problem. When physical over-utilization fires on a work center and date, the shift-design warning is suppressed for the same rows so you work the harder problem first. If both concepts are new, what is a scheduling anomaly check sets out how severity is meant to be read.

It is also not affected by the overtime allowance flag on a shift, which is informational and not enforced by the engine. Changing that flag changes nothing about what gets booked.

How to Fix It

• If the pattern is wrong, correct it. Raise the shift's maximum daily hours to the day you actually run, and the warning stops reporting a truth you already knew.
• If the pattern is right, treat the rows as a decision. Approve the overtime, add a machine unit, add a second shift, or move lower-priority work out of the window.
• Check for per-day capacity overrides before changing anything else, since an override replaces the shift formula for the days it covers and is honored as typed.
• Confirm the parallel configuration if the work center is a mirror, because those hours arrive by copy rather than by allocation.
• Re-run scheduling and re-scan so the report reflects the change rather than the previous plan.

How to Diagnose It, in Order

1. Check whether physical over-utilization also fired. If it did, fix that first and re-scan.
2. Read the detail on the row, which carries the booked hours against the cap and the size of the excess.
3. Compare the shift's maximum daily hours against the real working day, and the machine unit count against the real machine count.
4. Open the per-day capacity dialog and read the overridden days count for that work center.
5. Decide: pattern change or overtime decision, and record which one you chose.

How to Prevent It

• Keep the shift pattern honest. A maximum daily hours figure that has not been reviewed since setup is the most common source of continuous warnings.
• Keep the machine unit count accurate, because the cap scales with it and an understated count makes normal loading look excessive.
• Treat repeated warnings on one work center as a capacity signal, not as noise. A machine that exceeds its design cap most days is telling you it needs another shift or another unit rather than another warning.
• Separate the review from the fix. Read the warning rows once a week alongside your critical checks, as in clearing scheduler anomalies before publishing, and decide deliberately rather than reacting run by run.