- Home
- Blog
- Glossary (EDGEBIC)
- What Is Operator Time Off in Scheduling? EDGEBIC D…
What Is Operator Time Off in Scheduling? EDGEBIC Definition
Operator time off is a leave, PTO, or training date range recorded against one operator that removes their hours from the labor pool for those days, inclusive of both ends. It is the people-equivalent of a machine holiday. While the range is active the operator does not count as available, so any routing step that depends on that person's skill is scheduled around the gap: it slides to the next window where a qualified operator has free hours. A person's absence becomes a scheduling fact the engine acts on automatically.
This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. To enter one, follow how to record operator time off.
How Operator Time Off Works
An operator's availability is built from two layers. The base layer is the weekly roster: the recurring pattern of which shifts the person works, maintained once and left alone. The exception layer is time off: specific date ranges when the person is out, entered as needed on top of the roster.
When the engine assembles each operator's hours for a scheduling run, it starts from the roster and then subtracts any time off that overlaps the horizon. During a time-off range the operator contributes zero available hours, so no step that needs that person can be placed there. Keeping absences as exceptions, rather than editing the roster date by date, keeps the recurring pattern clean and puts every leave in one place.
The effect on the plan appears on the next reschedule. Steps that require the absent operator's skill and would have fallen inside the range move forward to the next feasible window. If several people hold the skill, the work simply flows to a colleague; if only one person qualifies, or the step is pinned to the absent operator, the step slides until they return.
A Concrete Example
Joe is out Monday through Wednesday. The planner records a single time-off range for Joe covering those three days, inclusive on both ends.
On the next reschedule, every step that needs Joe's skill and had been sitting in Monday through Wednesday is re-evaluated. Where another certified operator is free, the work moves to them and the plan barely shifts. Where Joe is the only qualified person, or the step carries a pin to Joe, the step slides to Thursday, the first day Joe is back with free hours. The planner did not touch a single job by hand; recording the absence once was enough to re-plan the affected work around it.
How EDGEBIC Uses It
Operator time off is a record you attach to an operator, and it feeds directly into the engine's labor availability:
- The engine feed subtracts time-off ranges from each operator's rostered hours, so during a leave the operator supplies no schedulable hours for any step.
- Reschedules route around it. Not-yet-started steps that need the absent person move to the next window where a qualified operator is free, with no manual reassignment.
- Actuals are protected. Work the operator already started or finished keeps its recorded dates; only remaining, unstarted work is re-planned around the absence.
Time off decides whether an operator is available at all; once they are, their schedule operator assignment records which steps the current plan has them working. Read the two together to follow a person from absence, through availability, to a dispatched crew, and use how to record operator time off to enter a leave.
Operator time off is a leave, PTO, or training date range recorded against one operator that removes their hours from the labor pool for those days, inclusive of both the start and end dates. In EDGEBIC it is the people-equivalent of a machine holiday: during the range the operator does not count as available, so any routing step that needs that person's skill slides to a window where a qualified operator has hours again. It is how a person's absence flows into the plan automatically.
It is the same idea applied to a person rather than a machine. A work center holiday removes a machine's capacity for a range of days; operator time off removes a person's hours for a range of days. Both are exceptions to a normal weekly pattern rather than a re-entry of the whole calendar, and both cause the engine to route work around the gap on the next scheduling run. The difference is only which resource loses availability.
The roster is the recurring pattern of which shifts an operator normally works; time off is the exception that overrides it. Rather than editing the roster date by date, you leave the weekly pattern intact and record absences as time-off ranges on top of it. When the engine builds each operator's available hours, it starts from the roster and then subtracts any time off, so the pattern stays clean and the exceptions live in one place.
Expert Q&A: Deep Dive
Q: Joe is out Monday through Wednesday. Do I have to reassign his jobs by hand?
A: No. Record Joe out Monday through Wednesday as a time-off range, then run a reschedule. Any step that requires Joe's skill and would have landed in those three days automatically moves to the next window where a qualified operator, Joe or another certified person, has free hours. If Joe is the only one certified, or the step is pinned to him, it slides to Thursday. You maintain the absence once and the engine re-plans the affected work, so nothing depends on remembering to move each job manually.
Q: Does recording time off change work an operator has already started?
A: No. Actuals are immutable to the rescheduler, so any step the operator has already begun or completed keeps its recorded dates and crew. Time off only affects not-yet-started work that needs that person, sliding it out of the absence window. This mirrors how the engine treats every other change: history is preserved, and only the remaining, unstarted portion of the plan is re-optimized around the new constraint.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.
