- Home
- Blog
- EDGEBIC How-To
- How to Schedule a Half-Day Holiday in EDGEBIC (Par…
How to Schedule a Half-Day Holiday in EDGEBIC (Partial Closures)
To schedule a half-day holiday in EDGEBIC, add a plant holiday and untick Closes the whole day. Start Time and End Time fields appear, you enter the blocked window, and each shift loses only the hours that overlap it. The grid marks the record Scope = Partial and shows the window.
This is the right tool for an early release, a plant-wide meeting, a union assembly, or a shortened day before a public holiday. It is also the cleanest way to document a recurring plant break. For the whole-day case, read how to add a plant holiday.
Before You Start
- You know the exact window, not just "the afternoon". The scheduler works in times.
- You know which shifts the closure genuinely affects. Only overlapping hours are removed.
- The closure applies to the whole plant. A single machine's half-day is a per-day capacity override instead.
- You can rerun the schedule afterward.
Step 1: Open the Plant Holidays Page
Open the Daily Hours tab, then select the inner Holiday tab. The Plant Holidays page opens.
Step 2: Click Add Holiday and Name It
Click Add Holiday. In the Holiday dialog, enter a Name that says what happened: Quarterly All-Hands, Christmas Eve early release, Safety stand-down. Enter the Date.
Step 3: Untick Closes the Whole Day
Untick Closes the whole day. The Start Time and End Time fields appear.
Step 4: Enter the Blocked Window
Type the window the plant is genuinely not producing. For a 45-minute all-hands: Start Time 10:00, End Time 10:45.
Be literal. If the meeting runs 10:00 to 10:45 but the line does not restart until 11:00, enter 10:00 to 11:00. The scheduler charges exactly what you enter.
Step 5: Save
Click Save. The grid shows Scope = Partial and the Window column displays the time range.
How the Scheduler Counts It
The subtracted amount is the overlap between the holiday window and each shift's window, computed per shift and per work center. In plain terms: take the later of the two start times, take the earlier of the two end times, subtract, and floor the result at zero. No overlap means no reduction.
Worked through with Day Shift 08:00 to 16:00 (8 hours) and an all-hands at 10:00 to 10:45:
| Shift | Shift window | Overlap | Hours available per instance |
|---|---|---|---|
| Day Shift | 08:00–16:00 | 10:45 − 10:00 = 0.75 h | 8 − 0.75 = 7.25 h |
| Night Shift | 16:00–00:00 | 0 h | 8 h, unchanged |
A work center with 2 instances on Day Shift therefore offers 7.25 × 2 = 14.5 hours on that date instead of 16.
Two things follow from this. First, the reduction is applied before the instance and utilization multipliers, so a partial holiday scales with the size of the work center, the same way scheduled downtime does. Second, a night crew that never attends the morning meeting is never charged for it. That is why partial holidays are configured once, plant-wide, rather than machine by machine. The full priority chain is in how EDGEBIC calculates work center capacity.
What Changes When You Save
| Surface | Effect |
|---|---|
| Plant Holidays grid | Shows Scope = Partial with the Window immediately |
| Overlapping shifts on that date | Lose exactly their overlap, per instance |
| Non-overlapping shifts | Unaffected |
| Resource Calendar and dashboards | Show the reduced day when refreshed |
| Existing schedules | Unchanged until Drive Schedule runs |
How to Check It Worked
- Confirm the row on the Plant Holidays grid reads Scope = Partial with the correct Window.
- Open the Resource Calendar and read a work center's total capacity on that date. Do the arithmetic yourself first: shift hours minus overlap, times instances. If the screen and your arithmetic agree, the record is right.
- Run Drive Schedule.
- Check the Gantt. The affected date should show a shorter total of allocated hours, and downstream steps should have shifted by the difference.
Common Mistakes
Using a partial holiday to shave routine losses. A partial holiday is a dated event with a name. If the plant reliably loses time every day to changeover drift or cleanup, that belongs in honest shift hours, not in a holiday record you have to recreate every week. Better to enter the shift net of the loss.
Expecting a partial holiday to hit every shift. It hits only what it overlaps, and that is by design. If a closure genuinely applies to both crews, enter two records, one per window.
Forgetting the reduction happens before the multipliers. On a four-instance work center, a one-hour partial holiday removes four hours of capacity, not one. That is usually correct (every operator is in the room), but it surprises planners the first time.
Adding it and not rerunning. Same as every other calendar change. The plan on screen keeps the old numbers until Drive Schedule runs, which is a recurring theme in our shift and calendar mistakes list.
Next
Partial holidays close part of a day for the whole plant. When the loss belongs to one machine rather than the plant, use a per-day capacity override instead: how to override capacity for one day. 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 release everyone at noon on Christmas Eve. Half-day holiday or a shift edit?
A: A partial holiday, with the blocked window running from noon to the end of the latest shift. Editing the shift would shorten every Tuesday (or whichever weekday it falls on) for the whole year, which is not what you mean. Enter it as a holiday named Christmas Eve early release with Closes the whole day unticked and Start Time 12:00, End Time set past the end of your last shift. Each shift is then charged only its own overlap: a day shift ending at 16:00 loses 4 hours, and a night shift starting at 16:00 loses all of its hours if your window runs to midnight.
Q: Our two-instance press has 16 hours on a normal Monday. What does it show on a Monday with a 45-minute all-hands?
A: 14.5 hours. The reduction is applied to the shift hours before the instance multiplier, not after, so the arithmetic runs 8 hours minus 0.75 equals 7.25 per instance, then 7.25 times 2 instances equals 14.5. That ordering matters because it means a partial holiday scales with the size of the work center, exactly like scheduled downtime does. A four-instance work center loses 3 hours to the same 45-minute meeting, which is usually the right answer since every operator on every machine is in the room.
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
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.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
