How the Shift Operator Roster Works in EDGEBIC

The operator roster in EDGEBIC by User Solutions is a weekly pattern that records which operator works which shift on which weekday, and it keys onto global shifts so one roster row covers every work center that mirrors that shift. It is the labor-side twin of a shift's weekly hours: a recurring pattern, with absences recorded separately as time off. The roster is what turns a certified operator into available capacity on a given day, and it is a foundational part of the shop floor labor model.

A certification says a person is qualified. A roster says when they are actually at work. The scheduler needs both to place a skill-gated step: qualified is not the same as present. This article explains how the roster is built, why it keys on global shifts, how time off overrides it, and the one configuration trap that silently starves staffing.

A Weekly Pattern, Not Per-Date Rows

The roster is deliberately a weekly pattern. For each operator you pick a shift and tick the weekday cells they work it (Monday through Sunday), and that pattern repeats every week. If a person rotates between shifts, you add another row for the second shift with its own weekday ticks.

This mirrors how machine calendars work: a shift carries weekly hours, and exceptions are recorded separately. Per-date roster rows would mean thousands of entries across a planning horizon, so EDGEBIC records the recurring pattern and treats absences as exceptions. That keeps the data small and the intent clear: this is the normal week, and time off is the deviation.

Keyed on Global Shifts

The roster keys onto global shifts, and this is the design decision that makes staffing maintainable. When a work center uses a calendar derived from a global shift, it inherits that global shift's roster automatically. Roster Joe once on Day Shift, and he covers every work center that mirrors Day Shift. You do not roster a person separately for each machine they might run.

This composes cleanly with the machine calendar chain. A work-center shift derived from a global parent shift picks up the parent's roster; the operator's availability then stacks on top of the machine's own availability. For how that availability becomes a scheduling gate, see how operator skills gate work center assignment.

Time Off Overrides the Pattern

Absences are recorded as time-off ranges, inclusive on both ends, so a range that starts and ends on the same Thursday covers that one day and the person is back Friday. A time-off range overrides the roster for the days it covers: on those days, a rostered operator's available hours drop to zero, so any step that needed them slides.

One rule to internalize: recording time off changes nothing until the next scheduling run. EDGEBIC does not auto-replan. Enter the vacation as soon as it is approved, then run a schedule, and steps that depended on that person's hours will move. A vacation entered but never rescheduled protects nothing.

The Qualified Pool, Assembled

The roster, certifications, and time off come together into the qualified pool the scheduler consults. For a skill on a date and shift, the pool is every operator who is certified and unexpired, rostered for that shift on that weekday, and not on time off, each contributing their remaining hours. If the pool has hours, the window is usable for a step needing that skill; if it is empty, the window is skipped. The Resource Calendar's operator lens shows this pool over time, which is where you look when a step scheduled later than a machine's free hours suggested.

The Parentless-Shift Trap

Here is the configuration mistake that silently starves staffing. Because the roster keys on global shifts, a work-center shift that is not derived from any global shift, a fully custom, parentless shift, can never match a roster row. Its skill pool is always zero, and skill-gated steps routed there visibly fail to schedule.

EDGEBIC treats this as a loud failure, not a silent pass, on purpose. A silent pass here would let a step schedule with no real staffing behind it, which is exactly the one-welder-two-machines fiction the labor constraint exists to prevent. The fix is always to derive the custom work-center shift from a global parent shift, or to roster people on the global shift the work center mirrors, never to relax the check.

A Worked Example

Day Shift runs 08:00 to 16:00, Monday through Friday. Joe is certified in TIG-Weld and rostered Day Shift Monday through Friday. Mary is certified and rostered the same. Sam is rostered but not certified.

A weld step needs 6.5 hours on Weld-1 Thursday:

• Base case. Joe and Mary both have 8 Thursday hours in the pool, so the step runs Thursday with room to spare. Sam's presence changes nothing: rostered is not the same as qualified.
• Joe on PTO Thursday, Mary not yet certified. Enter Joe's Thursday time off. Now the Thursday pool is empty, because Joe is out and Sam is not qualified. Reschedule, and the step slides to Friday, Joe's first day back.
• Certify Mary and reschedule. Mary's Thursday hours refill the pool, and the step returns to Thursday, staffed by Mary.

Every movement traces to the roster and time off feeding the pool. Nothing about the machine changed.

Where the Roster Shows Up

You build the roster on the operator's Roster sub-tab in the Operators manager, ticking shift-by-weekday cells. The resulting plan surfaces on the Dispatch tab as a printable per-person daily work list, and on the Resource Calendar's operator lens as availability versus booked hours. These are plan surfaces; who actually worked still comes from kiosk punches and actual dates.

The Bottom Line

The shift operator roster is a weekly, shift-by-weekday pattern that turns a certified person into available capacity, keyed onto global shifts so one row covers every mirroring work center. Time off overrides the pattern by date, and nothing moves until you reschedule. The one trap to avoid is a parentless custom work-center shift, which can never be staffed and fails loudly by design. Together the roster, certifications, and time off assemble the qualified pool that governs skill-gated production scheduling. Explore the labor model in the shop floor execution guide, and see the platform at EDGEBIC.