The Fastest-Overall-Finish Optimizer Preset Explained

The Fastest overall finish goal compresses a schedule end to end so the plant clears its workload and frees capacity as soon as possible. In EDGEBIC this preset, known internally as MinMakespan, ranks makespan first, then weighted tardiness, then schedule stability. It will accept a single job finishing later if that shortens the overall plan, because its whole purpose is to open machine time sooner. When you are working through a backlog, or when freeing capacity matters more than any one due date, it is the goal to pick.

EDGEBIC by User Solutions expresses each optimizer goal as an ordered list of tiers compared one at a time, so the top tier decides most comparisons. This post covers what makespan means, how this preset ranks a plan, when it beats the default, and a worked example. For the whole goal menu, see the optimizer goals and presets explained.

What makespan measures

Makespan is the span from the earliest operation start to the latest operation finish across the whole plan, counted in working hours. It answers a single question: how long until the plant has finished everything currently on the schedule? Minimizing it packs the work as tightly as capacity allows so the current load clears and the machines are free for what comes next.

Makespan is the classic throughput measure on a fixed set of jobs. It says nothing about individual due dates, which is exactly why this preset ranks weighted tardiness on a lower tier rather than ignoring it. The concept sits alongside broader ideas in production schedule optimization.

The three tiers, in order

The optimizer compares two plans by walking this list from the top. If plan A has a shorter makespan by more than a small tolerance, plan A wins, whatever the lower tiers say. Only when two plans tie on makespan does weighted tardiness break the tie, and stability breaks the tie after that.

This is the mirror image of On-time first, which puts weighted tardiness on top and makespan at the bottom. The two goals genuinely disagree about what to protect, which is the point of having both.

When to reach for it

Fastest overall finish is the right pick when the calendar, not the customer, is the pressure:

• Clearing a backlog before a period close when no single job carries a tight date.
• Freeing a bottleneck machine so next week's work can start sooner.
• Consolidating a light week into the front of the shift pattern to open time for maintenance or a rush order you expect.

It is the wrong pick when a specific customer date is the thing at stake. Then the top tier should be due dates, and On-time first is the goal. Because both carry the same never-worse guarantee, you can run one, read it, and try the other at no cost. See what the never-worse guarantee means for planners.

A worked example

One shared day shift, one saw and one mill, three jobs released Monday morning with loose due dates late in the week:

The current plan runs A, B, C. Job A's long cut holds the saw all Monday morning while the mill idles, so the whole plan stretches out and finishes on Wednesday morning, a makespan of 17 working hours.

Run the optimizer with Fastest overall finish. It reorders the jobs so the short cut feeds the mill first, B, A, C, keeping both machines busy. The mill starts by mid-morning Monday instead of the afternoon, and the plan finishes Tuesday afternoon.

Three working hours come off the plan, which is capacity freed for whatever runs next. Because the dates were loose, ranking makespan first cost nothing on delivery, and the second tier improved as a side effect. Read the whole comparison in how to run and read an optimization in EDGEBIC.

Why compressing a plan frees real capacity

The value of a shorter makespan is not abstract. When the base scheduler idles a machine early in a plan because a long first operation blocks the feeder, that idle time is capacity you paid for and did not use. Compressing the plan reclaims it. Three working hours off a plan is three hours the machines are free for the next batch, the maintenance window you have been deferring, or the rush order you expect on Thursday.

This is why Fastest overall finish pairs so naturally with bottleneck thinking. If one work center is your constraint, the makespan of everything routed through it governs how soon it can start the next wave of work. Ranking makespan first tells the optimizer to keep that constraint busy and to clear its current load as tightly as capacity allows. The related discipline of production bottleneck identification explains why the constraint deserves that attention: an hour lost at the bottleneck is an hour lost for the whole plant, and an hour reclaimed there is an hour of throughput gained. Fastest overall finish is the goal that turns that principle into a job order.

Reading the trade honestly

Because makespan is the top tier, this goal can accept a job finishing later than it would under On-time first, if that shortens the overall plan. The comparison screen shows this plainly. Read the key performance indicator table top to bottom: the makespan row shows the hours saved, and a lower row may show a late job the goal accepted to win the compression. The whole proposal is still clamped never-worse than your current plan under the makespan-first ranking, so it will never hand you something worse on its own goal.

If a late job that this trade produced is unacceptable this week, switch to On-time first and the priority reverses. This is not a flaw in either goal; it is the honest fact that speed and due dates sometimes pull in different directions, and you get to choose which wins.

Where it lives

Fastest overall finish appears in the Goal dropdown on the Optimizer tab, labeled for what it does. Select it, pick a time budget, and click Run. The verdict typically leads with the working hours it compressed off the plan. Nothing saves until you Accept, and the audit record captures the goal so anyone reviewing later knows the plan was chosen for speed, not dates.

For the broader optimizer picture, see the EDGEBIC optimizer guide. To weigh this goal against stability, see why schedule stability can beat schedule optimality. To explore the platform, visit EDGEBIC.

Pairing it with the mathematical solver

Makespan is a goal where the mathematical solver often earns its badge, because packing operations tightly across machines is exactly the kind of combinatorial problem a solver is built for. On a set of plain single-instance sequential jobs, the CP-SAT engine can frequently prove the makespan it found is optimal, so the badge reads "proven optimal" rather than "best of N tried." That proof is worth having when you are compressing a plan to free a bottleneck: you learn not just that the plan is tighter, but that no tighter plan exists.

Where jobs carry features the solver locks, the multi-run search is the more reliable choice, because it reorders whole jobs regardless of routing features. As always, both engines honor every capacity constraint and both are clamped never-worse, so the choice is about whether you want a proof or the broadest reordering, not about safety. Picking the engine is covered in how to choose the optimizer engine in EDGEBIC.

The bottom line

Fastest overall finish is the goal for clearing work and freeing capacity. It ranks makespan first, weighted tardiness second, and stability third, so it compresses the plan end to end and will accept a single job finishing later to do it. Reach for it when the pressure is the calendar and no one customer date is on the line. Run it, read the makespan row, check for any late job it accepted, and Accept when the trade suits the week. When dates matter more, On-time first is one dropdown away.