What Is a Work Center Shift in Scheduling?

A work center shift assigns a specific shift, optionally with override hours, to a specific work center, letting one machine's working hours differ from the global default. A shift by itself is a reusable template, a named pattern of working hours per day of week such as Day Shift running Monday to Friday from eight to four. The work center shift is the link that attaches that template to a particular machine, and it can adjust the hours for that machine alone. It is the mechanism that lets the milling area keep to one shift while the finishing area adds a night shift, without forcing every resource onto the same calendar.

This entry defines the work center shift and shows how it behaves inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the template it attaches, read what is shift time in production scheduling.

How it works

There are two objects here, and keeping them apart is what makes the model flexible. The shift is the definition: a template of start and end times per day of week, meant to be reused across many machines. The work center shift is the assignment: a link that says this particular work center runs this shift, and here are its hours if they should differ.

Without the assignment layer, every machine would have to share one calendar, which no real plant does. A furnace might run continuously; a finishing cell might run two shifts; a mill might run one. By assigning shifts per work center, each machine carries exactly the shifts it actually works, and the scheduling engine plans each one against its own hours rather than a plant-wide fiction.

The override hours on the assignment handle the finer case where a machine works the same shift as everyone else but for a different length of time. Perhaps a night crew on one line runs six hours instead of eight. Rather than clone the shift template, the planner sets override hours on that machine's assignment, so the machine differs from the default while still sharing the template's shape. Edits to the template flow to the machines that inherit its hours; machines with overrides keep their own figure.

A concrete example

A small shop runs a standard Day Shift, Monday to Friday, eight to four, defined once as a template. The two mills use it as is, so their work center shift assignments simply point at Day Shift with no override, and they run eight hours a day.

The finishing area is busier. It needs a night crew, so the planner defines a Night Shift template and assigns it to the finishing machines only, alongside their Day Shift assignment. Now the finishing area has sixteen working hours a day available while the mills have eight. Later, the finishing night crew is trimmed to six hours to save cost. The planner sets override hours of six on the finishing Night Shift assignment. The template still reads eight, the mills are untouched, but the finishing machines now offer six night hours. Each machine ends up with precisely the calendar it really works, all built from two shared templates plus one override.

How EDGEBIC uses it

In EDGEBIC, shifts are defined as reusable templates and attached to machines through work center shift assignments, so the plant can maintain a handful of shift patterns centrally and still give each work center the calendar it actually runs. A machine's assigned shifts, with any override hours, are what the scheduling engine reads when it computes available capacity for that machine on a given day.

This assignment layer feeds straight into the capacity calculation. The hours a work center offers on a date come from the shifts assigned to it, then get adjusted by the availability percentage and any daily or monthly capacity overrides. Because each machine carries its own shifts, the engine never assumes a uniform plant calendar: a job routed to a night-capable machine can be placed at night, while a job routed to a day-only machine cannot, and both are simply respecting their assigned shifts.

The override hours give the last degree of freedom, letting one machine differ from the global shift without duplicating the template. Central templates keep the common case simple; per-machine overrides handle the exceptions; the engine reads whatever each machine ends up with. To see the template a work center shift attaches, read what is shift time in production scheduling, and for the daily exceptions that layer on top of shift hours, read what is a capacity override. For how these hours become placed work, see what is available capacity in scheduling.