What Is a Secondary Resource in Manufacturing Scheduling? EDGEBIC Definition
User Solutions TeamA secondary resource in manufacturing scheduling is a second finite constraint, most often the operator, that must be available at the same moment as the primary resource, the machine, for a step to run. The machine is the primary resource that has always driven finite scheduling; a qualified operator is the second resource layered on top. A step can only be placed in a window where the machine has capacity and a certified, rostered, not-on-leave operator has unbooked hours. It is how EDGEBIC schedules people alongside equipment instead of pretending a machine can run itself.
This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary. To bring a person into the model, start with how to add an operator.
How a Secondary Resource Works
Classic finite capacity planning treats one thing as scarce: machine hours. That is enough when anyone can run any machine. It breaks down the moment the work needs a specific person, because the machine calendar looks free while the qualified human does not exist.
The secondary-resource model fixes that by requiring two green lights before a step is scheduled. The primary resource, the machine or work center, must have capacity, exactly as before. The secondary resource, a qualified operator, must also have hours free in the same window. If either is unavailable, the step waits. The operator becomes a constraint with its own finite hours, not an afterthought.
The trigger is the routing step's required skill. When a step names a skill, the engine looks for operators who hold that skill, are rostered on the shift, and are not on time off. Those operators carry a finite pool of hours per shift, and once that pool is spent the step must find another window. The person is scheduled as carefully as the machine.
A Concrete Example
Consider Joe, the only Inconel-certified welder in a three-welder shop. Five Inconel jobs land on the board for Monday. A machine-only schedule sees a Welding work center with plenty of instance hours and books all five Monday, because it never asks who is qualified.
With the operator modeled as a secondary resource, the engine asks a second question for each Inconel step: is a certified welder free here? Since Joe is the only one, and Joe has one shift of hours on Monday, the five jobs cannot all run Monday. There is only one Joe. The engine keeps whatever fits in Joe's Monday hours and slides the rest to the next windows where he has room. The schedule now tells the truth about the plant's real capacity for Inconel work, which is limited by a person, not a machine.
How EDGEBIC Uses It
The operator is EDGEBIC's built-in secondary resource. A few product behaviors follow from treating people as finite:
- The engine feed is assembled from active certifications, weekly rosters, and recorded time off, so an operator only counts as available when all three line up for a window.
- The operator-hours ledger caps each person at their shift's hours. No matter how many skills someone holds or how many machines could use them, an operator can never be booked past the hours their shift actually contains.
- The attend fraction tunes how much operator time a running step consumes, from fully attended down to a lights-out cell where the machine runs alone after setup.
The engine's plan for who works which step surfaces as a schedule operator assignment, the current run's crew list. Read that alongside this entry to see how the secondary-resource decision becomes a printable dispatch, and use how to add an operator to put your first person into the model.
A secondary resource is a second finite constraint, most often the operator, that must be available at the same moment as the primary resource, the machine, for a step to run. In EDGEBIC the machine is the primary resource and a qualified operator is the second constraint: a step can only be scheduled in a window where both the machine has capacity and a certified, rostered operator has unbooked hours. Modeling people this way stops the schedule from assuming a machine can run itself when nobody is available to staff it.
Because machine hours alone overstate capacity whenever the work needs a specific, limited person. If a plant has three welders but only one is certified for a given alloy, a machine-only schedule will happily book three of those jobs at once. Treating the operator as a finite secondary resource makes the engine respect that there is only one qualified person, so the plan reflects who can actually do the work, not just how many machines exist.
No. A step only takes on a labor constraint when its routing requires a skill. A step with no required skill is scheduled against machine capacity alone, exactly as it was before operators existed, which keeps the model backward compatible. The secondary resource comes into play only where a planner has said the work needs a qualified person, so you add labor constraints deliberately, step by step.
Expert Q&A: Deep Dive
Q: Our lights-out cell runs unattended overnight. Does the operator constraint block that?
A: No, as long as you set the operator's involvement correctly. A step's attend fraction controls how much operator time the running phase consumes per machine-hour. A lights-out cell would have a low or zero attend fraction on the run phase, meaning the operator is booked to set the job up and then the machine runs on its own. The operator is a finite secondary resource for the setup, but not for the unattended run, so the engine schedules exactly the human time the work really needs and no more.
Q: How does the engine know an operator is unavailable?
A: It builds a per-run picture of every operator's available hours from three inputs: their certifications for the required skill, their weekly roster of which shifts they work, and any recorded time off. An operator who is not certified, not rostered on that shift, or on leave does not count as available for that window. The step then only lands in windows where a qualifying operator still has hours free, which is what makes the operator a true finite constraint rather than an assumption.
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.