What Is a Shift Operator Roster?

A shift operator roster is the weekly pattern of which shifts an operator normally works, expressed as rows that read operator X works shift Y on weekday Z. It is the availability half of the labor model: the roster tells the scheduler when a person is on the clock, so a routing step that needs a certified operator can only be staffed in a window that operator actually covers. It is a recurring weekly template maintained once, not a dated list, with absences recorded separately as time off.

This entry defines the shift operator roster and shows how it behaves inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the booking the engine generates against it, read what is a schedule operator assignment.

How it works

Scheduling labor needs two facts about a person: what they are qualified to do, and when they are available. Certifications answer the first. The roster answers the second. Without a roster, a certified operator contributes zero hours, because the engine has no window in which to place them.

The roster is deliberately a weekly pattern rather than a dated log. A day-shift operator who works Monday through Friday is described by five roster rows, one per weekday, each tying the person to a shift. Those five rows repeat every week, so you maintain them once instead of stamping a fresh entry for every calendar date. The pattern keys on the shift the whole plant already knows, the same shift template the machines run against, so a rostered operator lines up cleanly with the hours their work centers are open.

Because the roster is a stable pattern, real-life exceptions do not live in it. A vacation, a training day, or a sick day is recorded as time off, a dated range that overrides the roster for those days only. The pattern stays clean and readable, and the scheduler subtracts the time off when it works out who is genuinely present. This split keeps the recurring shape of a person's week separate from the one-off gaps in it.

At schedule time the engine combines all of this. It staffs a labor-constrained step only in a window where a qualified operator is rostered, is not on time off, and still has unbooked hours in that shift. The roster is the piece that opens or closes each window; the certification decides whether the person counts for the skill at all; the hours ledger stops any one person being oversold.

A concrete example

A welding shop has one operator, Joe, certified for a specialized weld. His roster is five rows: day shift, Monday through Friday. Those rows say nothing about any particular week; they are the shape of Joe's normal availability, and they hold true every week until someone changes them.

A job arrives with a step that requires the specialized weld. The engine looks for a qualified, present operator with hours to spare. Joe holds the certification, his roster puts him on the day shift that day, and he has no time off recorded, so the step can be staffed to him in that window. Three more of the same jobs land. Because Joe has only so many rostered hours in a shift, they cannot all run at once; they spread across the days his roster covers, and any that will not fit slide to the next day he is on.

Now Joe books a week of vacation. Rather than deleting his roster rows, the shop enters a time-off range for those dates. His weekly pattern is untouched, but for that week the scheduler treats him as unavailable, so specialized-weld steps slide to before or after his leave. When the week passes, his roster carries on exactly as before, with no rows to add back.

How EDGEBIC uses it

EDGEBIC models each operator as a finite secondary resource alongside the machines, and the roster is how it knows when that resource is on shift. You build the roster on the operator's Roster tab by ticking the shift and weekday cells the person works, and the engine reads those rows on every scheduling run to decide which windows are open for that operator. To build one from scratch, see how to build a weekly operator roster.

The roster works together with the rest of the labor model. A certification decides whether the operator counts for a required skill; operator time off records the dated exceptions to the pattern; and the schedule operator assignment is the booking the engine produces when a rostered, certified, present person is placed on a step. The roster is the recurring input that maintains itself; the assignment is the per-run output that reflects the current plan.

Keeping availability as a weekly template rather than a dated list is what makes the labor constraint practical to run. You describe how a crew normally works once, record only the exceptions, and let the engine turn that into a staffed schedule that never promises work no rostered, qualified person is present to do. For where the whole labor model sits in the product, see EDGEBIC.