How to Set Reduced Capacity Across a Date Range in EDGEBIC

The date-range capacity override that would cover a whole month in one entry has no visible entry point in the current release of EDGEBIC by User Solutions. To reduce a machine's hours across a range of dates today, you enter per-day capacity overrides on each affected date and shift. Each one replaces the shift formula for its date and is read by the very next scheduling run.

If you came here looking for a monthly overrides panel, this page saves you the search, explains what the range override actually does when it is reachable, and covers the route that works now.

Before You Start

• The work center exists and is saved.
• You know the dates, the shifts, and the hours each affected day should offer.
• You know how wide the change is. A few machines and the whole site take different routes.

The Route That Works: Per-Day Overrides

1. Open the Workcenter tab and select the machine.
2. Open its per-day capacity dialog.
3. Select the shift, find the date, and enter the capacity in hours for that day.
4. Add a reason, such as "summer reduced crew", so the entries explain themselves later.
5. Repeat for every date in the range, and for every shift the machine runs.
6. Run the schedule.

The detail people miss is the shift dimension. Overrides are per day and per shift, so a machine running days and nights needs both entries or half of every day stays at full capacity. The single-day walkthrough is how to override capacity for one day.

What the Range Override Actually Does

It is worth being precise about the feature you cannot currently reach, because it is not simply a bulk version of the per-day entry.

A date-range override spreads a total-hours budget evenly across a period: 60 hours across a retooling week, for example. A per-day override states the hours for one specific date and shift. Those are different mechanisms, and a plan built from one is not the same as a plan built from the other. If you have been picturing a monthly override as "type one number and every day gets it," that is the per-day behavior repeated, not the range behavior.

How Precedence Resolves

Every scheduling run resolves a day's capacity in the same fixed order:

So a per-day entry always wins on any date it covers. That is what lets a broad reduction coexist with a handful of day-specific exceptions, and it is why a leftover per-day entry can mask a broader setting you thought you had applied.

When a Plant Holiday Is the Better Tool

If the reduction applies to the entire site rather than selected machines, a partial plant holiday says it in one entry. You define the window once and each shift is charged only its own overlap with it, so a daily reduction across a period may be expressed far more honestly that way than as machine-by-machine numbers.

Reach for it only when the loss really is plant-wide, because it reduces every work center. See how to add a plant holiday.

What Changes When You Save

Each entry replaces the shift formula for its date and shift on that work center, and the change is honored by the very next scheduling run. Existing bars do not move on their own: capacity is read at planning time, so run the schedule and then check the affected jobs. Work already started keeps its logged actuals, because a reschedule replans only what has not begun. Other machines are unaffected unless you enter overrides for them too.

How to Check It Worked

Open the capacity view for the work center and read the days in your range. They should show the numbers you entered rather than the formula value, on every shift you meant to change. Then run the schedule and confirm the machine is planned against the reduced hours for those dates. A day still showing the old number was either missed or was entered on only one of its shifts.

Common Mistakes

• Looking for a monthly overrides panel. It has no entry point in the current release; per-day entries are the route today.
• Entering only the day shift. A two-shift machine needs both, or the nights stay at full capacity.
• Assuming a range override sets a per-day number. It spreads a total budget across the period, which is a different result.
• Using a plant holiday for a few machines. It reduces every work center in the plant.
• Forgetting to reschedule. The entries are read at planning time, so the plan only reflects them after a run.
• Leaving entries in place afterward. Stale overrides quietly starve a machine long after the reason has passed.

Next

For a permanent reduction rather than a temporary one, see how to set a work center to run at reduced capacity. To understand the chain the overrides sit at the top of, read how EDGEBIC calculates work center capacity and daily capacity overrides explained. More recipes are in the EDGEBIC how-to hub, and the platform overview is at EDGEBIC.