EDGEBIC How-To

How to Add a Plant Holiday in EDGEBIC (Including Recurring Ones)

User Solutions TeamUser Solutions Team
|
6 min read

To add a plant-wide holiday in EDGEBIC, open the Daily Hours tab, select the inner Holiday tab, and click Add Holiday. Enter a Name and a Date, leave Closes the whole day ticked, and save. Every work center on every shift now shows zero capacity for that date, and the next scheduling run flows every job around it.

A plant holiday is the bluntest calendar instrument available: it closes the whole plant. That makes it the right tool for national holidays and annual shutdowns, and the wrong tool for a single machine's maintenance day. This page covers the whole-day case. For the full calendar setup sequence, read how to set up shifts and holidays in EDGEBIC by User Solutions.

Before You Start

  • You have the date. For recurring holidays, the exact month and day matter and the year does not.
  • You know it closes everything. A holiday affects every work center and every shift. Single-machine closures use a different tool (how to block a machine for a maintenance day).
  • You know whether the closure is a whole day or part of one. Part-day closures use the partial holiday route.
  • You can rerun the schedule. Existing jobs stay put until you do.

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 with the subtitle "Plant-wide closures affecting all work centers and shifts."

The grid columns are S.#, Name, Description, Date, Recurring, Scope, Window, Active, and Actions. Scan the existing rows before adding: duplicate holiday records are common and harmless, but they clutter an audit.

Step 2: Click Add Holiday

Click Add Holiday. The Holiday dialog opens.

Step 3: Fill In the Fields

FieldRequiredWhat it does
NameYesThe name shown in the grid and used for audit. Independence Day
DateYesThe calendar day. For recurring holidays, only the month and day matter
Recurring each yearNoWhen ticked, the closure fires on the same month and day every year
Closes the whole dayNoTicked closes the entire day for every work center. Untick to specify a window instead
DescriptionNoA free-text note. Use it: National holiday, Annual shutdown day 3 of 5
ActiveNoUntick to keep the record but stop the scheduler honoring it

For a whole-day closure, leave Closes the whole day ticked and ignore the time fields entirely.

Step 4: Decide Whether It Recurs

Tick Recurring each year for fixed-date public holidays and fixed annual shutdown dates. One record then covers every future year, which is much safer than maintaining a row per year and discovering the gap in January.

Leave it unticked for anything that moves: a shutdown week tied to a particular weekday, a one-off closure, an inventory count day. Those need a fresh record each year, entered during an annual calendar review.

Step 5: Save

Click Save. The holiday appears in the grid with Scope set to Whole Day.

What Changes When You Save

SurfaceEffect
Plant Holidays gridUpdates immediately, showing Scope = Whole Day
Available capacity on that dateDrops to zero for every work center and every shift
Resource Calendar and capacity dashboardsShow the closed day when refreshed
Existing schedules and promised datesUnchanged. Bars stay exactly where they are
Next Drive Schedule runSkips the date entirely and flows every job around it
Quote simulationsRun through the same calendar, so quoted dates already account for the closure

That last row matters more than it looks. Quotes and production schedules share one engine and one calendar, so a holiday you add today is reflected in tomorrow's promise dates without any separate quoting setup.

How to Check It Worked

  1. Find the new row on the Plant Holidays grid. Confirm Date, Recurring, Scope = Whole Day, and Active ticked.
  2. Open the Resource Calendar and read any work center's total capacity on that date. It should be zero.
  3. Run Drive Schedule.
  4. Open the Gantt and confirm no allocation sits on the closed date. If one still does, see job scheduled on a holiday for the short list of causes.

Common Mistakes

Adding the holiday and not rerunning. The plan on screen was computed against the old calendar. Until Drive Schedule runs, the Gantt happily shows production on a day the plant is closed, and it is not wrong: it is stale.

A recurring holiday saved on the wrong month or day. Only the month and day are used for recurrence, so a one-day typo repeats forever. Audit the recurring rows once a year.

Using a plant holiday for one machine. A holiday closes the whole plant. Blocking a single machine for a teardown or certification day is a per-day capacity override on that work center, which leaves the rest of the plant running.

Forgetting next year's non-recurring holidays. A missing record means the scheduler plans production through a closed plant and promises a date nobody can hit. Build the annual calendar review into December.

Next

Whole-day closures are the easy case. When the plant loses only part of a day (an all-hands meeting, an early release, a union assembly), use a partial holiday so each shift is charged only its own overlap: how to schedule a half-day holiday. To stop the scheduler honoring a holiday while keeping the record, see how to turn off a plant holiday without deleting it. 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 shut down for the first full week of July every year. Is that seven holiday records or one?

A: It is one record per closed calendar day, so a Monday-to-Friday shutdown is five records and a full seven-day closure is seven. There is no date-range holiday, and a holiday is a single-date entry. The saving grace is Recurring each year: if the shutdown always lands on the same calendar dates, tick it on each record and you never enter them again. If your shutdown floats (the week containing the fourth of July, for instance) leave Recurring unticked and add next year's dates during your annual calendar review, because a missing record means the scheduler will happily plan production through a closed plant.

Q: Our Christmas holiday fired on the wrong day this year even though it is marked recurring. What happened?

A: For a recurring holiday only the month and day of the Date field are used, so the record was almost certainly saved with the wrong month or day when it was first created. Check the Date column on the Plant Holidays grid: if it reads 12/24 when you meant 12/25, every year has been off by one and nobody noticed until a job landed badly. Edit the holiday, correct the Date, and rerun Drive Schedule for any job whose plan crosses that week. Recurring records deserve one deliberate audit each December for exactly this reason.

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