How to Turn Off a Plant Holiday Without Deleting It in EDGEBIC

To turn off a plant holiday in EDGEBIC by User Solutions without losing it, edit the holiday on the Plant Holidays page and untick Active. The record stays exactly as configured, and the scheduler stops honoring it from the next run onward. The hours come back, the audit trail survives, and one checkbox puts the closure back when you want it.

This matters more than it sounds. Holidays are usually entered once with Recurring each year ticked so they fire every year automatically. That is the right way to maintain them, and it is precisely why you should never delete one to open a single day. Deleting a recurring closure costs you the rule; deactivating it costs you nothing.

Before You Start

• Know whether the change is permanent or temporary. Temporary means deactivate. Permanent means delete, or edit the date if the closure simply moved.
• Know whether the holiday recurs. The Recurring column on the grid tells you. Deactivating a recurring holiday suspends it for every year, not just the one in front of you, so plan to reactivate it.
• Expect to reschedule. Nothing on the plan moves until you run Drive Schedule.

Step 1: Open the Plant Holidays Page

Open the Daily Hours tab from the main navigation, then select the inner Holiday tab. The Plant Holidays page opens, described in the app as plant-wide closures affecting all work centers and shifts.

The grid lists every closure with these columns: S.#, Name, Description, Date, Recurring, Scope, Window, Active, and Actions. Read Active before you change anything, because a holiday that never seemed to reduce capacity may already be switched off.

Step 2: Edit the Holiday and Untick Active

Click the edit control in the holiday's Actions column. The Holiday dialog opens with the record as you saved it.

Untick Active. Leave everything else alone: the Name, the Date, the Recurring each year checkbox, the Closes the whole day setting, and the Start Time and End Time of a partial window all stay put. That is the whole point of using the Active flag rather than editing the rule.

If it helps the next person, add a line to Description explaining the exception, for example Suspended for 2026 only, reinstate in December.

Click Save. The grid row now shows Active unticked.

Step 3: Rerun the Scheduler

Open Drive Schedule and run Schedule + Re-Schedule for the jobs whose plans should now use the reopened day. Until you do, the plan on screen still flows around a closure the calendar no longer contains.

What Changes When You Save

The restored amount depends on the holiday's scope. A whole-day closure removed the date entirely for every work center, so reactivating the day returns each work center's full shift hours x instances figure. A partial closure removed only the overlap between its window and each shift, so a 10:00 to 10:45 meeting was costing the day shift 0.75 hours per instance and costing a night shift nothing. Turning it off returns those 0.75 hours and nothing more. How to schedule a half-day holiday covers that arithmetic in full.

Deactivate, Delete, or Edit the Date

Three different situations, three different answers.

Deleting is done from the holiday's Actions column and is confirmed before it happens. It is the right call for a typo or a genuinely retired closure. It is the wrong call for a one-year exception, because a recurring rule has to be rebuilt by hand once it is gone.

How to Check It Worked

1. On the Plant Holidays grid, confirm the row still exists and Active is unticked.
2. Run Drive Schedule.
3. Open the Resource Calendar and read the Total Capacity row for a work center on that date. It should show its normal shift hours instead of zero (or, for a partial closure, the full shift hours rather than the reduced figure).
4. Look at the Gantt. Jobs that used to jump the date should now flow through it.

A Short Worked Sequence

Acme has a recurring whole-day closure on the Friday after Thanksgiving. This year the plant is working it to recover a late order.

1. Daily Hours, then the Holiday tab. The row shows Recurring ticked, Scope as Whole Day, Active ticked.
2. Edit it and untick Active. Leave Recurring each year alone. Add Working 2026 only, reinstate December to Description.
3. Save. The grid row stays, now marked inactive.
4. Run Drive Schedule. Every work center regains its normal shift hours x instances on that Friday. The late order picks up a full day of milling, and the jobs behind it move in with it.
5. In December, tick Active again. The recurring rule resumes untouched, and next year's Friday closes automatically like every year before it.

Total edits to the rule itself: none. That is what makes this the safe move rather than clearing the recurring flag or deleting the row.

Common Mistakes

• Deleting a recurring holiday to open one day. You lose the rule and will rediscover the problem next year, usually a week too late.
• Clearing the Recurring each year checkbox instead. That also changes the rule permanently, with the added confusion that the row still looks normal.
• Forgetting to reschedule. The capacity is back; the plan is not. Nothing moves until the next run.
• Forgetting to reactivate. A suspended recurring closure stays suspended forever. Reactivate as soon as the exception is over.
• Blaming the holiday when a capacity override is responsible. A per-day capacity override of zero closes a day just as effectively and beats the calendar formula. Check the work center's per-day dialog before you keep editing holidays. How to override capacity for one day shows where that lives.

Where to Go Next

If the change is permanent rather than temporary, the entry rules are in how to add a plant holiday, and bulk maintenance is covered by how to import plant holidays from a file. The rest of the task library is at the EDGEBIC How-To Library, and the platform overview is at EDGEBIC.