What Is an Objective Preset in Scheduling Optimization?

An objective preset is a named, ordered combination of optimization goals that the scheduling optimizer compares tier by tier. Rather than blending goals with weights, a preset ranks them: the top goal is satisfied first, the next goal breaks ties among the options that are equal on the first, and so on down the list. The default preset protects due dates above everything else. Others favor the fastest overall finish, the least changeover, or the fewest changes to the committed plan. A preset is a single dropdown choice that tells the optimizer what a good schedule means for this particular run.

This entry defines the objective preset and shows how it behaves inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the measure of how close a result is to the proven best, read what is an optimality gap in production scheduling.

How it works

A schedule can be good in several ways at once: it can hit due dates, finish early overall, avoid setup, and leave the existing plan undisturbed. These goals often conflict, so an optimizer needs to know which matters most. An objective preset answers that by ranking the goals in a fixed order rather than mixing them into a single weighted score.

The ranking is lexicographic, which means strictly tier by tier. The optimizer first finds the schedules that do best on the top goal. Among only those, it picks the ones that do best on the second goal. Among only those, it applies the third, and so on. A lower-ranked goal can never override a higher-ranked one; it can only decide among options that already tie above it. That is what makes a preset predictable: if due dates are the top tier, no amount of setup saving will trade a due date away.

This is deliberately different from weighting goals with coefficients. Weights can let a small improvement in one goal quietly outrank a large loss in another, and they are hard to reason about. Ranking keeps the trade-off explicit: you are choosing an order of priorities, and the optimizer honors that order exactly.

The common presets each encode a different priority order. On Time First puts due dates at the top and is the default, because for most shops a late order is the worst outcome. A makespan preset aims for the fastest overall completion. A setup preset minimizes changeover time and becomes available once the setup matrix has real data to optimize against. A stability preset minimizes how much the new plan moves versus the committed one, protecting the floor from churn.

A concrete example

Suppose a planner runs the optimizer on a busy week with the On Time First preset. The top tier is due-date performance, so the optimizer first narrows to the set of schedules where every order that can be on time is on time. Only within that set does it look at the next tier, perhaps stability, choosing among the on-time plans the one that disturbs the committed schedule least. Setup reduction, lower still, breaks any remaining ties.

Now the planner switches to the setup preset for a paint-heavy week where changeover dominates. Here setup sits above the middle tiers, so the optimizer groups compatible colors to cut changeover, accepting more plan movement to do it, but still only among schedules that respect whatever the preset ranks above setup. The two runs produce different schedules from the same jobs because the planner told the optimizer a different order of priorities. Nothing was hidden in weights; the preset made the trade explicit.

How EDGEBIC uses it

EDGEBIC exposes objective presets as a single choice for an optimizer run: On Time First as the default, plus presets for fastest finish, least setup, and greatest stability. Each preset is a registered, named goal ordering with its own definition, not a hidden switch, so a planner can see exactly what each one optimizes for. The setup preset appears once the sequence-dependent setup matrix has data to work from, since there is nothing to minimize before then.

Whatever preset is chosen, two guardrails hold. The optimizer runs beside the standard scheduling engine rather than replacing it, using the existing plan as its starting point, and it is bound by a never-worse rule: after solving, the candidate is compared against that baseline under the chosen objective, and if it is not strictly better the baseline is kept. So a preset can only steer the optimizer toward a better plan by its own definition of better, never toward a worse one. The optimizer also reports how close its result is to the proven best available, so the planner sees the quality of the schedule rather than assuming it is optimal.

Because the result is held for review and applied only when the planner accepts it, choosing a preset is a safe way to ask the same jobs a different question. To see the measure of solution quality it reports, read what is an optimality gap in production scheduling. For the capacity a shift loses when an operation only becomes eligible partway through it, read what is a late-start penalty in scheduling. For the rule that keeps a run from ever worsening the plan, read what is the never-worse clamp in scheduling optimization. And for how the optimizer sits alongside the main engine, see what is an optimizer sidecar in scheduling.