How to Take Maintenance Hours Out of a Machine's Day in EDGEBIC

There is no downtime events screen on a work center in the current release of EDGEBIC by User Solutions. Downtime is part of how the engine computes a day's capacity, but the way you actually take hours out of a machine's day is a per-day capacity override, or a partial plant holiday when the loss hits the whole site.

If you came looking for a downtime tab, this page saves you the search and covers the two routes that work today, including the honest cost of modeling a standing weekly window.

Before You Start

• The work center and its shift exist (how to add a work center).
• You know the window: which dates, which shift, and how many hours are genuinely lost.
• You know how wide the loss is. One machine and the whole plant take different routes.

Route A: One Machine Loses Part of a Day

This is the common case and the per-day capacity override is the tool.

1. Open the Workcenter tab and select the machine.
2. Open its per-day capacity dialog.
3. Select the shift the loss falls on and find the date.
4. Enter the capacity as the hours the machine can genuinely offer: an eight-hour shift losing two hours becomes 6, and a machine out all day becomes 0.
5. Add a reason, such as "weekly line clean" or "bearing replacement".
6. Repeat for every affected date, and for every shift if the machine runs more than one.

The step-by-step version with screenshots is how to block a machine for a maintenance day, which covers the full-day case; a partial day is the same dialog with a number other than zero.

Route B: The Whole Site Loses the Same Hours

When the window hits everything, a partial plant holiday does it in one entry. You define the window once and every shift is charged only its own overlap with it, so a 10:00 to 10:45 all-hands meeting costs the day shift 45 minutes and costs an evening shift that never touches those hours nothing at all.

That makes it right for site-wide events: a utility outage, a safety stand-down, a company meeting. It is wrong for one machine, because it reduces every work center in the plant. See how to add a plant holiday.

What About a Recurring Window?

Recurring windows and closures scoped to a single shift are supported by the scheduling engine but have no configuration screen today. A standing weekly slot is therefore entered as per-day overrides on the affected dates rather than as one repeating rule.

It is better to know that than to hunt for a menu that is not there. Two practical notes. Enter them in batches, a quarter at a time, rather than week to week. And do not reach for the tempting shortcut of shortening the shift: that moves the start or end time and tells the scheduler the machine is closed at a time it is actually running, which distorts every other calculation that reads the shift.

What Changes When You Save

A worked case: a milling cell on an eight-hour day shift with a two-hour Monday maintenance window is entered as 6 for that Monday. If a seven-hour job was landing there, the next run places six hours and spills the last hour into Tuesday.

How to Check It Worked

1. Reopen the per-day capacity dialog and confirm the date carries your number and its reason.
2. Read the machine's available hours for that day in the capacity view: a one-instance eight-hour shift with two hours removed should read 6.
3. Run the schedule and confirm no bars sit inside the protected hours.

Common Mistakes

• Looking for a downtime tab. There is none in the current release. The override dialog is where the hours come out.
• Entering the loss on one shift only. A machine running days and nights needs the entry on both, or half the day stays bookable.
• Using a plant holiday for one machine. It closes every work center on every shift, which is a large and very visible mistake.
• Shortening the shift instead. It misrepresents when the machine is open and affects everything else that reads the calendar.
• Forgetting to rerun. Capacity is read at planning time, so bars already on the plan sit through the window until a run happens.
• Leaving the entry in place afterward. A stale override quietly starves a machine that is back in service.

Next

For the model behind all of this, read downtime explained and how EDGEBIC calculates work center capacity. For where maintenance cadence belongs, see how to handle preventive maintenance for a machine. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at EDGEBIC.