What Is a Schedule Operator Assignment?

A schedule operator assignment is the record of the engine's operator booking for one scheduled operation: which operator, on which date and shift, for how many hours. It represents the current plan's crew, the people the schedule expects to staff each step. It is regenerated wholesale on every scheduling run, so it always reflects the latest plan, and it is never a timesheet or a payroll record. It is the planned staffing behind a scheduled operation, produced by the engine when it treats operators as a finite secondary resource alongside the machines.

This entry defines the schedule operator assignment and shows how it behaves inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the fraction of attention a step demands from its operator, read what is attend fraction in operator scheduling.

How it works

Scheduling is usually thought of as placing machines, but many operations also need a qualified person, and people are finite too. When the engine schedules a step that requires labor, it does not just book a machine; it books an operator. A schedule operator assignment is the record of that booking: this person, this date, this shift, this many hours, on this operation.

The mental picture is the printed dispatch list a supervisor pins up at the start of the day: Tuesday day shift, this operator on this job's step for four hours. That list is the plan's crew. It tells everyone who is expected where, and it is exactly what the assignments express, one row per planned booking.

Crucially, assignments are plan, not fact. They are generated by the engine as it schedules and are rebuilt from scratch on every run, so as operations move to new times or machines the crew is recomputed to match. That is why an assignment is never treated as an actuals or payroll record: it is a proposal for staffing that can change on the next reschedule, whereas actuals recorded on the floor are immutable once captured.

A concrete example

A welding shop has one operator, Joe, certified for a specialized weld, plus other welders who are not. A job routes through a step that requires that certification. When the engine schedules the job, it looks for a qualified, available operator with hours to spare. Only Joe holds the certification, he is rostered for the day shift, and he is not on time off, so the engine books him: a schedule operator assignment for Joe, Tuesday day shift, four hours, on that step.

Later, three more jobs needing the same weld arrive. Because Joe has only so many hours in a shift, the engine cannot assign all of them to him at once; the assignments spread across the days he has capacity, and jobs that cannot be staffed slide until he does. On the next reschedule, all of these assignments are regenerated to reflect the new plan. The dispatch list the supervisor prints always shows the current crew, and none of it is confused with what Joe actually clocked, which is captured separately as the work happens.

How EDGEBIC uses it

EDGEBIC generates schedule operator assignments when the engine staffs labor-constrained steps. A routing step can require a skill, which narrows the pool to operators holding an active certification for it; the engine then honors each operator's shift roster and time off, and their finite hours, booking only where a qualified person genuinely has unbooked capacity. If a step is pinned to one named operator, only that person qualifies, and the step slides visibly through their absence rather than silently substituting someone else.

Because these bookings are the current plan's crew, they are regenerated wholesale on every reschedule, never carried over as stale rows and never posted as actuals or payroll. That separation keeps the plan honest: assignments express who the schedule expects, while the kiosk captures who actually worked, and the two are reconciled but never conflated. The assignments read directly as a dispatch list for a work center or shift, giving supervisors a clear, always-current view of the planned crew.

Modeling operators as a finite secondary resource is what turns a machine-only schedule into one that also respects the people who run it, so a plan cannot promise work that no qualified, available person can staff. To see how much operator attention a step consumes, read what is attend fraction in operator scheduling. For the per-station run queue these bookings feed, see what is a work center dispatch list. And for how the engine preserves recorded work when it regenerates the plan, read what is actuals preservation on reschedule.