What Is a Work Center Availability Flag?

A work center availability flag is the switch on a resource's record that tells the scheduler to skip it entirely, paired with an effective date that keeps a machine out of the plan until the day it is commissioned. Together they answer a question capacity numbers cannot: not how many hours a machine has, but whether it should be in the plan at all. In EDGEBIC by User Solutions both sit on the work center editor's basic information tab, and both take effect on the next scheduling run rather than the moment you save.

How it works

A work center is a resource the scheduler books time on, and every routing step points at one. Before the scheduler asks how many hours a resource offers on a given date, it asks whether the resource is in play.

Two fields answer that:

The availability flag. On by default. When it is off, the scheduler skips the work center entirely. Nothing is placed there, and the jobs whose routings needed it behave in one of two ways: they move to a true alternate work center if the routing configures one, or they slide until the resource is available again. See what is a true alternate work center for the mechanism that turns an outage into a re-route rather than a delay.

The effective date. The scheduler treats the work center as unavailable before this date. That makes it the right tool for equipment that has been ordered, or is on the floor but not yet accepted: you can create the record, name it, set its rate, and even reference it from a routing, while it contributes zero capacity to any schedule or quote until the date arrives. Without it, a machine entered early quietly inflates capacity in every plan and every quoted promise made in the meantime.

Both are coarse, whole-resource controls. That is the distinction worth holding onto, because there are finer instruments for finer problems:

Per-day capacity overrides deserve a mention here because they cover a case the flag cannot. There is no separate screen in the current release for per-machine holiday rows, so a single-machine closure is modeled by entering reduced hours, or zero, on the affected dates through the per-day override grid. The advantage is that each override carries a reason and an overridden marker, so the plan explains itself later. The mechanism is described in what is a capacity override.

One more behavior matters. Saving any master data never reschedules. The flag and the date change what the next run will consider, and the existing plan stays put until you run the scheduler. That is why an outage is a two-step action: change the record, then reschedule.

A concrete example

A shop buys a second mill. It arrives in June and commissioning is booked for the first of July.

Entered without an effective date, the new mill contributes capacity from the day someone saves the record. Every June schedule and every June quote leans on a machine that is not making parts, and the promise dates that go out that month are optimistic by a whole machine. Entered with an effective date of the first of July, the record exists, the routing can already reference it, the rate is set, and no plan touches it until July. On the first scheduling run in July it simply joins the plant.

Six months later that same mill goes out for a rebuild. The planner unticks the availability flag and runs the scheduler. The mill's queued work either moves to the other mill, if the routing lists it as a true alternate, or slides to the far side of the outage. Nothing had to be dragged by hand, and the plan now describes the plant as it actually is.

Now vary the case. Suppose the rebuild is a half day rather than two weeks, and only Tuesday afternoon is affected. Turning availability off for a whole resource is the wrong shape: it removes the machine for an indefinite period and someone has to remember to restore it. A per-day capacity override on that Tuesday, set to the reduced hours with a reason noted, is precise, self-documenting, and expires on its own because it only covers the day it was entered.

How EDGEBIC uses it

The work center grid gives planners the surrounding context on one row: the identifier routings reference, the instance count, and whether the resource follows the plant-wide shift calendar or a custom one of its own. Availability and the effective date sit on the editor rather than the grid, so the everyday view stays about capacity while the in-or-out decision lives with the record.

The delete guard is the other half of the story. Removing a work center is blocked while any active routing, schedule or capacity override still references it, which prevents a routing being orphaned with a step that has nowhere to run. For equipment that is genuinely retired, the usual answer is not deletion but availability off, which leaves the historical references intact so completed jobs still read correctly.

Three habits keep this clean:

• Set an effective date on every machine entered before it runs. It costs one field and prevents a month of optimistic promises.
• Use the flag for whole outages and per-day overrides for partial ones. Overrides carry a reason and expire on their own; the flag does neither.
• Reschedule after changing either field. Master data changes are inert until the next run, which is a feature and also a step you have to take.

The related capacity questions, how many hours a work center offers and how they are computed, are separate from availability entirely. Those come from the shift calendar attached to the resource, described in what is a work center shift, and from how many identical machines stand behind one name, described in what is a machine instance in scheduling.

The takeaway

The availability flag and the effective date answer whether a resource belongs in the plan; capacity fields answer how much it can do once it does. Use the date for equipment that does not exist yet, the flag for a resource that is out, and per-day overrides for anything narrower, then run the scheduler so the plan catches up. To see the work center editor and its grid in a working plan, explore EDGEBIC, and if you are arriving from the older Resource Manager lineage, the move from RMDB to EDGEBIC maps the equivalents. For neighboring terms, read what is a plant holiday in scheduling and what is capacity type in a work center.