Why the Least Setup Time Goal Is Missing From Your Optimizer
User Solutions TeamThe Least setup time goal is missing from your optimizer because it appears only once sequence-dependent setup data is configured, and it joins the dropdown automatically as soon as one work center has a setup matrix. In EDGEBIC by User Solutions the goal list normally reads On-time first, Fastest overall finish and Fewest changes, with the setup goal withheld rather than disabled. This is a data dependency, not a license tier or a setting in Options.
What the dropdown is telling you
Open the Goal dropdown on the Optimizer tab with no setup matrix in place and you see three entries. The fourth is not hidden silently: the interface states the condition, noting that the goal becomes available once sequence-dependent setup data is configured.
That phrasing is deliberate. There is nothing to switch on, no permission to request, and no component to install. The goal is a function of your data, and it turns up on its own the moment the data exists.
Why a flat setup time is not enough
This is the part worth understanding, because it explains why the answer is not simply "use the setup times we already maintain".
A routing step can carry a flat setup number, and a work center can carry a default. Both are real and both are used. But a flat number says the same thing regardless of what ran before, and that is precisely the information a setup-reducing optimizer needs. Consider a paint booth:
| Sequence | Real changeover | What a flat 60-minute setup claims |
|---|---|---|
| White then cream | near zero | 60 minutes |
| White then black | 60 minutes | 60 minutes |
| Black then white | 240 minutes | 60 minutes |
| Black then black | zero | 60 minutes |
With flat setup times, every possible order of those jobs costs the same total setup. There is no better sequence to find, so a goal promising to find one would be promising something the data cannot deliver. Withholding the goal is more honest than offering a button that cannot work.
Once a matrix exists, the same four jobs have sequences that differ by hours, and reordering becomes worth doing.
What "configured" actually means
The requirement is a sequence-dependent setup matrix on at least one work center. Building one is a per-machine job with four steps, in this order:
- Families. Create the groups that drive changeover, such as Light Colors and Dark Colors.
- Product families. Assign each product to a family.
- Family matrix. Add a FROM and TO cell for each direction that exists, with the time in minutes.
- Product overrides. Only for specific pairs that break their family rule.
Families are what keep this small. One hundred products in eight families need at most sixty-four cells rather than ten thousand, and the same product back to back is always zero changeover automatically. The full sequence is covered in migrating your setup matrix, and the mechanism itself in the EDGEBIC setup matrix explained.
One machine is enough to make the goal appear. Start with whichever work center loses the most hours to changeover order rather than waiting to model the plant.
What to use in the meantime
The absence of the setup goal does not make the optimizer less useful today. The other three goals reorder work against measures your current data does support:
- On-time first protects due dates above everything else, and is the right default most days.
- Fastest overall finish compresses the plan end to end, which suits working through a backlog.
- Fewest changes improves the plan while disturbing a committed floor as little as possible.
All three carry the same guarantees as the setup goal: never worse than your current plan, nothing saved until you press Accept, and recorded work left untouched. Trying one costs seconds, which is the argument in working the optimizer into your scheduling routine.
After the goal appears
Two things change once your matrix is live and the goal is selectable.
Setup becomes a measurable row. The comparison table gains a Setup row showing current against proposed hours, so the gain is a number you can read rather than an inference.
The engine choice starts to matter more. The multi-run search tries many job orderings through the real scheduler and keeps the best complete result, reported as the best of N schedules tried. The mathematical solver goes further for this particular goal, because it treats changeovers as part of the sequence it is optimizing rather than as a cost it discovers afterward, and it can report how close the result is to the best theoretically possible. The engine is chosen in Options, and choosing the optimizer engine covers the trade.
Bear in mind that the quality of the result tracks the quality of the matrix. The optimizer can only avoid the changeovers your data describes, so an incomplete matrix gives an incomplete answer. Verify yours is firing by checking the Setup Reason column on scheduled rows: entries reading Matrix, whether family or product, confirm the data is in play.
Common misreadings
| What people conclude | What is actually true |
|---|---|
| The goal is a paid or licensed extra | It is data-dependent, with nothing to buy or enable |
| It is missing because of a permission | Goals are not permission-gated; this one is data-gated |
| Our flat setup times should count | They are used for scheduling, but carry no sequence information |
| We need the whole plant modeled first | One work center with a matrix makes the goal appear |
| Something is broken | The dropdown is stating a prerequisite, not reporting a fault |
The takeaway
The Least setup time goal is missing because sequence-dependent setup data does not exist yet, and it appears automatically once at least one work center has a setup matrix. Flat setup times cannot unlock it, because they carry no information about what ran before, which is the only thing a setup-reducing reorder can act on. Build a matrix on your worst changeover machine, keep it small with families, and use On-time first or Fewest changes in the meantime. See the platform on the EDGEBIC overview, the upgrade path on the RMDB to EDGEBIC guide, and pair this with how the optimizer cuts total setup time and how the optimizer ranks goals in strict order.
Expert Q&A: Deep Dive
Q: Our paint booth loses hours to color changes. What is the shortest path from here to a setup-reducing optimizer run?
A: Populate the matrix for that one machine, then run the goal. The work is smaller than it sounds because setup families keep it small: walk the booth with the person who knows it, write down the changeover minutes in the direction they occur, and look for the pattern rather than the pairs. If the real driver is color tone you have two families, light and dark, and four family cells covering every product you will ever add. Enter the families, assign each product to one, fill the four cells in minutes, and save. The goal then appears in the dropdown automatically, with no setting to switch on, and the optimizer can start grouping compatible work. One machine is enough to unlock it, so do not wait until you have modeled the whole plant. The setup matrix editor is per work center, which means this is a single afternoon on your worst offender rather than a project.
Q: Once the goal appears, does it behave differently from the other goals?
A: It carries the same guarantees and one extra dependency. Like every goal, it will never hand you a plan worse than your current one, it changes nothing until you press Accept, and it leaves completed and in-progress work untouched. The dependency is that its quality tracks the quality of your matrix: the optimizer can only avoid the changeovers your data describes, so a half-entered matrix produces a half-useful result. There is also a difference between the two engines worth knowing. The multi-run search reorders whole jobs and keeps the best complete schedule it finds. The mathematical solver treats changeovers as part of the sequence itself, which is where the setup goal becomes genuinely powerful, because the sequence and the changeover cost are optimized together rather than one after the other.
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 Nearest Challenger Line in an Optimizer Result
When the optimizer says your plan is still the best, it often names the runner-up and how far behind it was. That one line tells you how close the decision was and whether to look again.
What Happens When the CP-SAT Solver Is Not Installed
You selected the mathematical solver in Options but the badge still says best of N tried. That is a deliberate fallback, not a fault, and here is how to confirm it and what you keep.
What the Optimizer Needs Before Its First Run
Four prerequisites, only one of which is mandatory. Here is the short checklist before your first optimizer run, and the two messages that tell you a prerequisite is missing.