How to Set a Work Center to Run at Reduced Capacity in EDGEBIC

To run a work center at reduced capacity across a period in EDGEBIC by User Solutions, enter a smaller-than-usual figure in the per-day capacity override for each day in the range. The scheduler honors the reduced number ahead of the shift formula, so a retooling week, a partial-crew stretch, or a machine limping on temporary parts is planned against what it can really deliver.

Reducing is not blocking. A block sets a machine to zero for a full day, covered in how to block a machine for a maintenance day. Reducing keeps the machine running at a lower rate. And it is not a single-day tweak either, which is how to override capacity for one day. This page is the sustained, multi-day, non-zero case. For the resolution order behind every capacity number, read how EDGEBIC calculates work center capacity.

Before You Start

• The work center already exists and normally schedules at full capacity.
• You know the period and the reduced level: the start and end dates, and roughly how many hours the machine can offer each day during it.
• You know why. Common cases are a retooling or partial-maintenance week, a stretch with one crew instead of two, or a machine running below spec while it waits for parts.

Step 1: Open the Per-Day Capacity Dialog

On the work center's row, click the 📊 per-day capacity button. The Per-Day Capacity dialog opens, showing a stacked bar per day: Loaded, Free, and Over capacity, with a summary card above.

Step 2: Set the Date Range

Adjust the From: and To: range to cover the reduced period. The grid below lists every day in the range with its Shift default (h) and an editable Capacity (h) column.

Step 3: Enter the Reduced Hours per Day

For each affected day, type the reduced figure in the Capacity (h) column. Enter the total hours for the machine that day, not per-instance hours: on a three-instance work center, "each machine gets four hours" is a Capacity of 12. Add a short Reason, such as "Retooling" or "One crew," so the audit trail explains the light load. The change saves as you type, and the Overridden column ticks for each day you set.

If you want an even spread of a total budget, divide it across the working days. Sixty hours across five days is 12 per day. This mirrors EDGEBIC's internal date-range override, which spreads a total across the available days in a window; the per-day dialog is the reliable way to enter that spread.

Step 4: Confirm and Close

Check the summary card: Overridden days should show the count you set. Click Close.

What Changes When You Save

A worked case: a welding shop that normally offers 48 hours a day is set to 12 across a five-day retooling week. The next run places far less work in that week and pushes the rest forward, and every downstream step of the affected jobs moves accordingly.

How to Check It Worked

1. In the per-day dialog, confirm the Overridden tick and the reduced Capacity (h) on each day of the range.
2. Open the Resource Calendar and read the machine's capacity across the period. It should show your reduced figures, not the shift default.
3. Run Drive Schedule and confirm the machine carries less work during the period and normal load before and after it.

Common Mistakes

Entering per-machine hours on a multi-instance work center. The override is used as-is and is not multiplied by the instance count. Enter machines times hours, or you will get a fraction of the capacity you intended.

Reducing on the wrong shift. Overrides are shift-specific. A machine that runs day and night needs the reduced figure entered on both shifts, or the untouched shift keeps promising full hours.

Forgetting to reset. A reduced override persists until you clear it. When the crew or the tooling returns, reset the days so the machine goes back to its shift default; otherwise it runs light indefinitely.

Reaching for a shift edit instead. For a temporary reduction, an override carries a reason and reverts cleanly. Save shift edits for a permanent change in the machine's pattern.

Next

Reduced capacity is how you tell EDGEBIC the truth about a machine that is running but not at full stride. Use zero overrides to block a machine entirely, and honest shift hours for a permanent change. To confirm the effect, how to read the Work Center Capacity Detail grid puts total, assigned and available hours in one table. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.