Makespan is the total span from the moment the first operation in a set of jobs starts to the moment the last operation finishes. It measures how long a whole batch of work takes to clear the floor. A shorter makespan means the plant finishes the same workload sooner and releases its resources earlier for the next batch.
EDGEBIC by User Solutions computes makespan as a scheduling KPI and can optimize for it directly. This article defines the term and shows how job sequence changes it.
How It Works
Makespan is a whole-schedule measure, not a per-job one. Take every operation across every job in the run, find the earliest start of any of them, find the latest finish of any of them, and the span between those two points is the makespan. It answers a simple question: from the first tool touching metal to the last part leaving the floor, how long did all of this take?
The number is driven by how jobs share work centers. When several jobs compete for the same machines, the sequence in which they claim those machines decides how much idle time creeps into the schedule. A poor sequence leaves expensive stations waiting; a good sequence keeps them fed. Because the workload is identical either way, makespan is one of the clearest measures of pure scheduling quality.
A Concrete Example
Take two work centers, a cutting station and a milling station, one machine each, sharing a single day shift. Three jobs are all released Monday morning. Job A cuts for six hours then mills for two. Job B cuts for two hours then mills for six. Job C cuts and mills for three hours each.
Schedule them in the order A, B, C and the mill sits idle all Monday morning while A's long cut blocks the saw. The batch does not finish until Wednesday morning, a makespan of about 17 working hours. Now sequence them B, A, C: B's short two-hour cut feeds the mill by mid-morning, the mill stays busy, and all three jobs finish Tuesday afternoon, a makespan of about 14 working hours. Same three jobs, same two machines, three working hours saved purely from the order.
How EDGEBIC Uses It
Makespan is one of the KPIs the scheduling engine reports for any plan, and it is one of the goals the optimizer can target. When you run the optimizer and pick the fastest-overall-finish goal, the engine searches alternative job sequences and scores each complete schedule by makespan, returning the sequence that finishes the batch soonest.
The optimizer is a sidecar: it proposes a complete alternative plan, shows the makespan next to the current plan and the other KPIs, and changes nothing until you accept. The multi-run search is clamped never worse than your current plan, so the makespan it reports can only match or beat what you already had. The mathematical solver goes further and can prove how close its makespan is to the theoretical best.
Makespan is one lens among several, and the fastest finish is not always the right call: a shorter makespan can occasionally finish a low-priority job early at the cost of a due date. That is why the optimizer shows makespan alongside tardiness and other KPIs, so you weigh the whole picture. The manufacturing glossary covers the related terms, and if you are new to why sequencing matters at all, start with job shop scheduling challenges.
Expert Q&A: Deep Dive
Q: Two schedules deliver the same jobs but one clears the floor a full day sooner. How is that possible without more machines?
A: It is the job sequence, not the capacity. Makespan depends heavily on the order in which jobs claim shared work centers. Consider three jobs across a cutting station and a milling station: if the job with the six-hour cut goes first, the mill sits idle all morning while the saw is busy, and the batch drags into a third day. Reorder so the two-hour cut goes first, and the mill starts by mid-morning and stays fed, so all three finish by early the next afternoon. Same jobs, same machines, one day saved, purely from sequencing. That is exactly the kind of gain the optimizer's fastest-finish goal searches for.
Q: When should I optimize for makespan instead of due dates?
A: Choose the fastest-overall-finish goal when your priority is clearing a backlog or freeing capacity as soon as possible, for example before a big incoming rush or a planned shutdown. Choose the on-time goal when hitting customer dates matters most, which is the usual default. The two are not always in conflict, but they can be: the shortest makespan sometimes finishes a low-priority job early at the cost of nudging a due-date-critical one. In EDGEBIC you pick the goal per run, review the makespan and tardiness deltas side by side, and accept only if the trade suits the week.
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.