EDGEBIC How-To

How to Block a Time Window Across a Whole Shift in EDGEBIC

User Solutions TeamUser Solutions Team
|
6 min read

To block a time window across a whole shift in EDGEBIC by User Solutions, add a partial plant holiday for that window. Open the Daily Hours tab, then the Holiday tab, click Add Holiday, untick Closes the whole day, and enter the start and end time. The scheduler charges each shift only its own overlap with the window, which is what makes one plant-wide record behave correctly shift by shift.

This is the right tool for an interruption that stops the whole crew at once: an all-hands meeting, a safety stand-down, a utility power cut. For one machine's maintenance you want a per-day capacity override instead, which is a different page.

Why a Partial Holiday and Not a Downtime Record

Worth clearing up first, because the instinct is to look for a downtime tab on the shift.

EDGEBIC's scheduling engine understands shift-scoped closures and standalone downtime records, and it honors them if they exist. What the current release does not provide is a screen to create either one. There is no Downtime Events tab on a shift and no downtime editor anywhere else.

The partial plant holiday covers this case properly, and arguably better. Because the engine subtracts the overlap between the holiday window and each shift's own hours, a single record lands different amounts on different shifts without you doing anything:

blocked hours = max(0, min(shift end, holiday end) − max(shift start, holiday start))

A 09:00 to 11:00 meeting against an 08:00 to 16:00 day shift blocks two hours. Against a 16:00 to 00:00 night shift it blocks nothing, because the windows never touch. One entry, correct per shift.

Before You Start

  • You know the window: the date and the exact start and end time.
  • You know it hits every machine whose shift overlaps that window. That is the point, and it is also the limitation covered at the end of this page.
  • You can rerun the scheduler so jobs move out of the window.

Step 1: Open the Plant Holidays Page

Open the Daily Hours tab, then the inner Holiday tab. The Plant Holidays page lists closures affecting all work centers and shifts.

Step 2: Add the Holiday

Click Add Holiday. Enter a Name that explains the block for the audit trail, such as All-hands meeting or Utility power interruption, and set the Date.

Step 3: Untick "Closes the Whole Day"

This is the step that turns a full closure into a window. Unticking it reveals the Start Time and End Time fields.

Step 4: Enter the Window

Type the start and end time of the interruption, for example 09:00 to 11:00. Save.

The grid shows Scope = Partial with the window in the Window column. Every shift that overlaps those hours now loses the overlap on that date.

Step 5: Reschedule

Run Schedule / Re-Schedule so the jobs that would have run in the window slide out of it. Adding the holiday changes the calendar; it does not move existing bars until you rerun.

What Changes When You Save

SurfaceEffect
Every shift overlapping the windowLoses its own overlap hours on that date
Shifts that do not overlapUnaffected, automatically
Multi-instance work centersLose the overlap per machine, so the block scales with the size of the resource
Existing schedulesNot moved until you rerun

That third row matters more than it looks. The subtraction happens before the instance multiplier, so a two-hour meeting on a three-machine work center removes six hours of schedulable capacity, exactly as it does in the building.

How to Check It Worked

  1. Reopen the Plant Holidays page and confirm the record shows Scope = Partial with the right date and window.
  2. Check capacity for that date across a couple of work centers and confirm it is reduced by the overlap, multiplied by their instance counts.
  3. Confirm a shift that should not be affected, such as nights for a morning meeting, still shows its normal hours.
  4. Rerun the scheduler and confirm no work is planned inside the blocked window.

Common Mistakes

Looking for a downtime tab on the shift. There isn't one in this release. The partial plant holiday is the mechanism for a crew-wide window.

Using a partial holiday when only one of two overlapping shifts stops. The record charges every overlapping shift. If the window straddles both shifts and only one crew is in the meeting, use per-day capacity overrides on the affected shift instead.

Using a partial holiday for a full day. Tick Closes the whole day instead. Carving 8 hours out of an 8-hour shift works, but the whole-day flag says what you mean.

Forgetting to rerun. The calendar shows the block, but existing bars stay until a reschedule moves them.

Next

A partial plant holiday blocks a window across the plant and charges each shift its own overlap, which is the tool for an event that stops the crew rather than one machine. For a single machine's maintenance window, read how to block a machine for a maintenance day. For a full day off for one crew, read how to close one shift for a holiday, and for the full calendar picture, the shifts and holidays setup guide. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.

Expert Q&A: Deep Dive

Q: We have a two-hour all-hands meeting Friday morning that stops every machine. How do I model it?

A: Add a partial plant holiday for that Friday. Open the Daily Hours tab, then the Holiday tab, click Add Holiday, name it All-hands meeting, set the date, untick Closes the whole day, and enter the start and end time of the meeting. Every shift whose hours overlap that window loses the overlap, so a morning meeting takes two hours off every machine on the day shift automatically, and a night shift starting at 16:00 loses nothing because the windows do not touch. That is exactly the behavior you want and it is one record rather than one per machine. Then rerun the schedule so the jobs that would have run in that window slide out of it.

Q: The meeting window overlaps both our shifts, but only the day crew attends. What then?

A: A partial plant holiday cannot tell the two crews apart: it charges every shift its own overlap with the window, so the night crew would lose hours it is actually working. When the window genuinely straddles two shifts and only one is stopping, use per-day capacity overrides instead, entered on the day shift for each affected work center with the reduced hours and a reason. It is more entries, but it lands the loss on the right crew. There is no shift-scoped closure record in the current release, which is why this case falls back to overrides.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together