A selection strategy is the rule the engine uses to pick which machine in a pool of interchangeable machines runs a given step, when several machines could all do the work. It turns a pool of options into a decision. The three strategies are earliest completion, primary first, and earliest start, and each optimizes for a different priority: shortest lead time, predictable routing, or fastest start. The strategy is set per pool, so different machine groups can behave differently in the same run.
EDGEBIC by User Solutions applies the strategy the moment a pooled step is resolved. This article defines the term and the three options. The full pool-explosion mechanism is in what is a work center group.
How It Works
When a routing step points at a pool of interchangeable machines rather than one specific machine, the engine explodes the pool into a primary plus a set of alternates, then hands the choice to the pool's selection strategy.
Earliest completion, the default, picks the candidate that finishes the operation soonest. It weighs each machine's own speed and its current queue depth, so a fast machine buried under a backlog can lose to a slower one that is free. This minimizes the individual job's lead time.
Primary first always tries the designated primary member and spills to the others only when the primary has no capacity on the target date. Routing stays predictable: work lands on the same machine until it is genuinely full. Earliest start picks the member that can begin soonest. It is day-granular, so a machine that can start today beats a faster machine that can only start tomorrow, and among same-day starters the earlier finisher wins.
A Concrete Example
Take a milling pool of three machines: Mill-1, a 2015 Haas designated as primary; Mill-2, a fast 2024 machine; and Mill-3, an older, slower unit. A job needs the pool, and the engine projects completion on each.
Under earliest completion, if all three are free Monday, Mill-2 wins because it finishes soonest at its faster speed. But if Mill-2 is booked solid until Wednesday, the fastest machine loses to the available one: Mill-1 finishes Monday and takes the job. The fast machine loses to the free machine, which is the entire point of capacity-aware pooling.
Under primary first, Mill-1 wins whenever it has capacity, even on a day where Mill-2 would finish two hours sooner. Predictable routing, familiar setups, spill to the others only when Mill-1 is full. Under earliest start, if Mill-3 can start Monday afternoon and Mill-2 only Tuesday morning, Mill-3's same-day start wins even though Mill-2 would finish first. Same three machines, same data, three different answers, because the strategy encodes what you value.
Choosing a Strategy
The three strategies map cleanly to three shop priorities. Choose earliest completion when cycle time is the goal: it will always route to whichever machine finishes soonest, accepting that jobs move around as loads shift. Choose primary first when consistency and operator familiarity matter more: work stays on the designated machine until it is full, so setups and routines stay predictable and the pool acts as pure overflow. Choose earliest start when visible momentum matters most: it favors getting work moving today over waiting for a faster slot tomorrow.
Because the strategy is per pool, you do not have to pick one rule for the whole shop. A precision milling pool can chase earliest completion for lead time, a paint pool can use primary first to keep changeovers disciplined, and a finishing pool can use earliest start to keep the queue short. Set each pool's strategy to the priority that governs that resource, and the engine resolves each one on its own terms in the same run. There is no universally correct strategy, only the one that matches what a given pool is optimized for.
How EDGEBIC Uses It
The strategy is a property of each machine pool. When the engine resolves a pooled step, it stamps the step with that pool's strategy and picks the member accordingly, so you can run one pool on earliest completion and another on primary first in the same schedule. The session log records which member won and under which strategy, so a routing decision is never a mystery.
The choice survives rescheduling. Started work stays on its machine, and only not-yet-started pooled steps re-shop across the members on the next run. The manufacturing glossary covers the related terms. To see how a pool is built and exploded, read what is a work center group, and for the configuration steps see how to set a pool selection strategy.
Expert Q&A: Deep Dive
Q: We pooled three mills of different ages and now jobs bounce between them run to run. Which strategy stops that?
A: Switch the pool from earliest completion to primary first. Earliest completion re-optimizes every run for the shortest lead time, so as loads shift, the winning machine changes and your jobs appear to bounce. Primary first pins work to the designated primary mill and only spills to the others when the primary is genuinely full on the target date. Designate your newest or most-trusted mill as the primary, and the pool becomes stable: the primary carries the work, the other two catch overflow, and operators stop seeing jobs move around for no visible reason. The cost is slightly longer lead time on busy days, which is usually worth the predictability.
Q: Our shop cares more about getting jobs started than about theoretical cycle time. Is there a strategy for that?
A: Yes, that is exactly what earliest start is for. It is day-granular: it picks the pool member that can begin soonest, so a machine free this afternoon beats a faster machine that cannot open until tomorrow, even if the faster machine would eventually finish first. Among machines that can all start the same day, the earlier finisher wins the tie. This suits shops where visible momentum on the floor and short queues matter more than minimizing each job's total run time. Set the pool's strategy to earliest start and the engine will favor moving work today over waiting for a faster slot.
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.