The labor constraint is the one most schedules ignore: they check whether the machine is free and assume a qualified person is standing at it. EDGEBIC by User Solutions can treat people as a finite resource, so a routing step that names a required skill is scheduled only into a window where a certified, rostered, present operator still has unbooked hours. That single rule closes the gap where a plant with one certified welder gets shown five simultaneous jobs and nobody notices until the shift starts.
This post is about the delivery and trust outcome of modeling labor. For the full model, see operator and skill scheduling. This post sits under the EDGEBIC results guide.
The Failure Machine-Only Scheduling Cannot See
A machine-only scheduler asks one question: does this work center have free hours? If Weld-A and Weld-B both show eight free hours on Monday, two Inconel jobs both get Monday. The plan prints, the supervisor prints it, and at 08:00 one certified welder discovers he is expected in two places.
Nothing there is a software defect. The scheduler answered the question it was asked. The problem is that the question was incomplete, and the cost is silent slip. The plan degrades quietly, dates move without anyone deciding they should, and after a few weeks the floor stops trusting the printed schedule and runs from memory. Skilled-labor availability is one of the constraints that separates a plan from a wish, a standard concern in job shop labor scheduling.
Modeling a Person as Real Capacity
With the labor constraint configured, EDGEBIC asks both questions at once: is the machine available, and is there a qualified person with hours left to stand at it. The model has six parts:
| Piece | What it is |
|---|---|
| Skill | A named certification such as TIG-Weld or CMM Inspection. A routing step requires exactly one |
| Operator | A shop-floor person with a name, a badge or payroll code, and an active flag |
| Certification | The link between an operator and a skill, with an optional date, expiry, and proficiency |
| Roster | A weekly pattern: which operator works which shift on which weekday |
| Time off | Absence ranges, the person's version of a work center holiday |
| Step labor fields | The required skill, operator attention, and an optional pin to one named person |
Two design choices explain most of the behavior. People carry hours, not presence: each operator holds a budget of hours per shift per day, so a person certified in three skills still has one budget, and booking them through welding leaves fewer hours for inspection. A per-skill pool would sell the same person into three pools at once, which is the double-count in a new costume. And the roster is a weekly pattern with absences as exceptions, which mirrors how plants actually staff. See how EDGEBIC books operator hours for the arithmetic.
Machine and Human Compose on One Step
A routing step can carry both a machine target and a labor requirement, and they answer different questions. The work center, or the work center group, answers which machine. The required skill answers which qualified person. The step schedules only when both answers exist in the same window, which is exactly what operator skills constraining a schedule enforces.
That composition is the whole outcome. The machine constraint and the labor constraint are checked together, so the plan cannot promise a machine you have while quietly assuming a person you do not.
The Outcome, Measured Two Ways
Modeling labor pays back on two numbers that shops feel immediately.
Fewer silent slips. The double-booking that used to surface at shift start now surfaces at planning time, weeks earlier, as a job that simply did not fit the qualified operator's hours. You resolve it with a decision (train a second operator, move the date, add a shift) instead of a scramble. That is the difference between managing capacity and reacting to it, the same shift described in ending the daily firefight.
A schedule the floor believes. When the plan stops promising one welder to two jobs, the floor stops overriding it. Trust is the quiet return here, and it compounds: a schedule people follow is a schedule that produces the on-time numbers it predicted. For why that trust is fragile and how it is earned, see getting the floor to trust the schedule.
What the Labor Constraint Cannot Do
It cannot train operators. The schedule shows you that one certified welder is your constraint and that his hours are the ceiling on Inconel work. Deciding to certify a second person is a management call. The plan makes the case with weeks of warning; it does not make the hire.
It cannot cover a roster you never entered. If the certifications, rosters, and time off are not maintained, the constraint is blind, and the plan reverts to machine-only behavior. The model is only as honest as the roster behind it, which is why maintaining it is part of the daily rhythm, not a one-time setup.
It cannot decide that a skill requirement is optional. If a step names a required skill, the scheduler treats it as mandatory. Loosening that (allowing an uncertified hand under supervision, say) is a process decision you make by editing the step, not something the scheduler guesses.
It cannot model a person as being in two places by working faster. Hours are hours. If the work genuinely needs more qualified-person hours than exist, the plan will show the shortfall rather than hide it, and that visibility is the point.
Want to see where your skilled labor is the real constraint? Bring your operator list and a set of skill-gated jobs to a demo and we will show where the plan quietly assumed a person you do not have free.
Modeling operator skills matters because a machine-only schedule can promise the same certified person to several jobs at once, and the plan degrades silently until the shift starts. In EDGEBIC a routing step that names a required skill is scheduled only into a window where a certified, rostered, present operator still has unbooked hours. That closes the oldest gap in machine-only planning, where a plant with one qualified welder is shown five simultaneous jobs and nobody notices until the floor cannot cover them.
EDGEBIC gives each operator a budget of hours per shift per day, not a yes-or-no availability flag. A person certified in three skills still holds one budget, so booking them through welding leaves fewer hours for their inspection work, exactly like reality. Certifications link an operator to a skill with an optional expiry, rosters set the weekly pattern of who works which shift, and time off is the person's version of a work center holiday.
No. You add the labor constraint only where skilled-person availability genuinely gates the work, such as certified welding, inspection, or a validated operator-attended process. A routing step requires exactly one skill, and steps that any available hand can run carry none. The point is to model the constraint that actually limits you, not to attach a person to every operation and drown the plan in labor rows that never bind.
Expert Q&A: Deep Dive
Q: Our schedule shows two Inconel jobs on Monday and we only have one certified welder. How does the software stop that?
A: It asks two questions per step instead of one. A machine-only scheduler asks whether Weld-A and Weld-B have free hours, sees that both do, and puts both jobs on Monday. With the labor constraint configured, EDGEBIC also asks whether a qualified person with hours left can stand at each machine. If your one certified welder has eight hours and both jobs need him, only one lands on Monday and the other moves to the first window where he has hours or a second certified operator is rostered. The double-booking never prints, so it never becomes a Monday-morning surprise.
Q: A certification lapsed and the job ran anyway. Can scheduling actually catch that?
A: Yes, because a certification carries an optional expiry date and the scheduler treats an expired certification as a person who no longer holds the skill. A step requiring that skill will not schedule into a window covered only by the lapsed operator; it waits for someone current or flags that nobody qualified is available. That turns an audit finding into a planning constraint, so the schedule refuses to quietly route regulated work to someone whose paperwork ran out.
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
What a Plan Built on Yesterday's Data Costs You
A schedule is only as current as its last data refresh. What goes wrong when that refresh depends on someone remembering, what an automatic sync changes, and the limits worth knowing before you trust it.
The Furnace Does Not Care How Many Hours Are Left
Batch equipment takes one job per chamber per day whatever the clock says. Scheduling it as pooled hours over-promises the constraint by a factor you can calculate.
How an Adherence Percentage Becomes an Investigation List
A percentage tells you the plan is not being followed and nothing else. The count of operations behind it is a finite work list, and pairing it with attainment tells you which of two problems you have.