How a Work Center Inherits or Overrides Its Calendar

A work center in EDGEBIC by User Solutions either inherits the plant's global calendar or defines its own. It can use the global shifts that the whole plant runs, or carry its own shift pattern; and separately, it can observe the global holiday list or keep its own. That inherit-or-override choice decides when the capacity search will find the resource open, because the engine only ever places work on shifts a machine actually has, on days it is not closed. It is the mechanism that lets one plant hold a shared calendar while individual resources that keep different hours still schedule against their own reality.

Every finite capacity plan needs to know when each resource is open. The simple answer, one calendar for the whole plant, is right for most machines and wrong for a few, and the inherit-or-override model is how both are true at once.

The default is the plant calendar

Most work centers keep plant hours. They run the same shifts as everyone else and observe the same holidays. For them, inheriting the global calendar is exactly right: define the plant's shifts and holidays once, and every inheriting work center picks them up. When the plant adds a shift or declares a holiday, those resources follow automatically, with no per-machine editing.

This shared default is what keeps a plant's calendar maintainable. A shop with dozens of machines does not want to set the same Monday-to-Friday day shift on every one of them, or add next year's holidays machine by machine. The global calendar is entered once and inherited broadly.

Overriding when a resource keeps different hours

Some resources do not keep plant hours, and forcing them onto the global calendar would make the schedule wrong in one of two directions: idle capacity the machine actually has, or promised capacity it does not.

A bottleneck furnace might run a Saturday shift or a third shift the rest of the plant skips, to squeeze out more of the constraint's time. If it inherited the plant's Monday-to-Friday calendar, the engine would never find it open on Saturday, and that real capacity would be invisible. Overriding the furnace's shifts to include Saturday lets the capacity search find and use that day for the furnace, and only the furnace.

The reverse happens with holidays. A packaging line might have a crew that works through a plant holiday to catch up, while every other resource is closed. If the line inherited the global holidays, the engine would treat it as closed that day and miss the catch-up capacity. Giving the line its own holiday list that omits that date keeps it open when the rest of the plant is not.

In both cases the override exists so that each resource's true availability, not a plant-wide assumption, drives where work can land.

Shifts and holidays inherit independently

The choice to inherit or override is made separately for shifts and for holidays, because they answer different questions. Shifts say when the resource normally runs. Holidays say which specific days it is closed regardless of the shift pattern.

A machine can inherit global shifts, keeping the plant's daily rhythm, while carrying its own holiday list, observing different closures. Or it can run its own shift pattern while inheriting the global holidays. Any combination is valid. Keeping the two independent means a resource that merely observes a different holiday does not have to redefine its whole shift schedule, and a resource that runs a special shift does not have to restate the plant's holidays.

How this reaches the capacity search

None of this changes how the engine schedules; it changes what the engine sees as open. When the capacity search walks the calendar forward, for each day it asks whether this work center is open, which shifts it runs, and how much capacity those shifts offer, exactly as why a scheduler searches forward in time for capacity describes. The answer comes from that work center's resolved calendar: its own shifts if it overrides, the global shifts if it inherits, minus its own or the global holidays.

So the same forward search, unchanged, finds the furnace open on Saturday and the mill closed, because their calendars differ. The removal of holiday and closed days from available capacity is the same mechanism covered in how a schedule accounts for holidays and downtime; the inherit-or-override model simply decides which holidays and shifts apply to which resource.

A worked example: two resources, two calendars

A plant runs a global Monday-to-Friday day shift, 08:00 to 16:00, and observes a holiday on a Friday.

Mill-1 inherits everything. It is open Monday to Thursday that week, closed Friday for the holiday, and closed the weekend. A job on Mill-1 that is not done by Thursday evening resumes the following Monday.

Furnace-1 overrides its shifts to add a Saturday day shift and overrides its holidays to omit that Friday, because its crew works both. It is open Monday through Thursday, open Friday despite the plant holiday, and open Saturday. A job on the furnace can keep running Friday and Saturday while the rest of the plant is dark.

The capacity search finds each resource open exactly on its own days. A routing that flows from the furnace to Mill-1 can exploit the furnace's Friday and Saturday, then wait for Mill-1 to reopen Monday, and the plan reflects both realities without any special handling in the routing.

Getting the calendars right

Inherit the global calendar for every resource that keeps plant hours, which is most of them, so the plant's shifts and holidays are maintained in one place. Override only the resources that genuinely differ, and override shifts and holidays independently so you only restate what actually changes. The payoff is a schedule where each machine's availability is honest, so the forward search finds open time exactly where it really exists.

Calendar resolution is one of the inputs that make the capacity search trustworthy, and it plugs into the wider pipeline in the scheduling engine guide. It serves the same goal as everything in finite versus infinite capacity scheduling: a plan that models the floor as it really runs. To set your own resources' calendars and watch the search respect each one, explore the EDGEBIC engine or bring your data to a demo.