What Is a Plant Holiday in Production Scheduling?

A plant holiday is a non-working day that removes scheduling capacity from every work center in the plant at the same time. It models a company-wide closure such as a public holiday, an annual maintenance shutdown, or a bridge day when nobody is on the floor. Because a plant holiday applies to the whole site with one entry, the scheduling engine treats that date as zero available hours everywhere, and no job can be placed to run on it. EDGEBIC by User Solutions uses plant holidays as the top layer of a three-level calendar so a single closure protects your entire schedule.

How it works

A plant holiday is the broadest of three holiday levels, and each level answers a different question. A plant holiday closes the site. A shift holiday closes one shift, so the night shift can be off on Christmas Eve while the day shift still runs. A work center holiday closes one machine or resource, such as a furnace down for calibration on the fourth and fifth of the month, while the rest of the plant keeps producing.

When the engine calculates how many hours a work center has on a given day, it checks all of these together. If the date is a plant holiday, capacity is zero regardless of what the shift template says. That is why one plant holiday is safer than editing the calendar of every machine by hand: you cannot forget a work center, because the rule is global. If hours do end up booked on a closed date, the off-calendar booking check reports it against the job that assumed them.

Holidays remove capacity before the schedule is ever placed. On the next scheduling run, the engine simply has no hours to book on those dates, so it walks forward in time to the next working day and places the operation there. This is the same forward search that handles a fully booked bottleneck, only the cause is a closed calendar rather than competing work.

A concrete example

Think of the plant calendar the way a school treats its term timetable. A national holiday closes the whole school: no class runs anywhere that day, and every lesson that would have fallen on it moves to the next school day. That is a plant holiday.

Now suppose only the science lab is closed for a fume-hood repair while every other classroom runs normally. That is a work center holiday: one room dark, the rest of the school open. And if only the after-school session is cancelled on a given day while morning classes go ahead, that is a shift holiday.

In manufacturing terms, Christmas Day is a plant holiday because no shift runs anywhere. Furnace number two offline July fourth and fifth is a work center holiday. The night shift off on Christmas Eve, with the day shift still running, is a shift holiday. Each maps to the level that matches the real closure.

How EDGEBIC uses it

Plant holidays live in the calendar setup alongside your shifts. You add each closure date, and from that point the engine removes those hours from every work center automatically. The step-by-step is covered in how to add a plant holiday in EDGEBIC, and half-day closures follow the same idea in how to schedule a half-day holiday.

Because holidays feed the same capacity math as shifts and overrides, they show up wherever capacity does: the Gantt shows no bars on a closed date, and the capacity views read zero hours. If a closure did not have the effect you expected, the causes are almost always a level mismatch or a missing reschedule, which is why the walkthrough in how a schedule accounts for holidays and downtime and the fix in a holiday did not reduce capacity are worth a read before you trust a closed day.

The broader distinction, a closed calendar versus a machine that is down for a reason, is captured by the companion term downtime event. For the full vocabulary of scheduling terms, see the manufacturing glossary, and to see holidays inside a working calendar, explore EDGEBIC.