What Is a Load Factor in Constraint Scheduling?

A load factor is the ratio of the hours one job demands from a work center to the hours that work center can supply in a single day, so a value of 1.0 means the job consumes exactly one day of that resource and 3.0 means it consumes three. The ratio is computed per job and per quantity, not once per machine, which is what makes it useful: it answers "which step does this particular order lean on hardest?" rather than "which machine is generally busy?" EDGEBIC by User Solutions computes a load factor for every work center in a job's routing whenever a job is scheduled against a pinned constraint, and uses the comparison to confirm which resource is genuinely the tightest for that order.

How it works

The calculation has two halves, and both are plain arithmetic.

The numerator is demand: the hours this job asks of this work center. That is the step's run time per unit multiplied by the order quantity, plus the step's setup time. A step running 0.16 hours per piece on a 50 piece order with a 0.5 hour setup demands 8.5 hours.

The denominator is daily supply: the hours the work center can deliver on a normal working day. That comes from the shift calendar attached to the work center, multiplied by the number of machine instances it runs. A single machine on one eight hour shift supplies 8 hours a day. Two machines on the same shift supply 16.

Divide demand by supply and you get the load factor. Because the numerator scales with order quantity and the denominator does not, the ratio is a property of the pairing of a job and a work center, never of the work center alone.

The comparison is where the value sits. The engine computes the ratio for every work center that appears in the job's routing and then looks for the maximum. When a planner has pinned a job's operation to a constraint work center, the engine checks whether that pinned resource carries the highest load factor in the routing, within a tiny rounding tolerance. If it does, the planner's identification is confirmed for this job. If some other step carries a higher ratio, the pin is still honored, but the engine has quietly recorded that the tightest resource for this order is somewhere else.

Nothing about the ratio changes how hours are placed on the calendar. Capacity, shifts, holidays, and machine instances still govern placement. The load factor is a diagnostic that tells the engine, and by extension you, where a job's schedule is most fragile.

A concrete example

Take the sample plant: Day Shift 08:00 to 16:00, eight hours, one machine each on Saw-1, CNC-Mill-1, and Paint-Booth-1. A job for 50 brackets runs all three in sequence.

CNC-Mill-1 carries the maximum. If the planner pinned this job's milling operation to the mill as the plant constraint, the engine confirms it: for this job at this quantity, the mill is the tightest resource, and the job's finish date is more sensitive to a lost mill hour than to a lost saw hour.

Now change one thing. Add a second machine to the mill, so it supplies 16 hours a day instead of 8. The demand stays 8 hours, so the mill's load factor halves to 0.50. Saw-1 is unchanged at 0.25 and the paint booth at 0.375. The mill is still the maximum, but the margin has narrowed sharply, and a slightly larger paint operation would flip which step is tightest.

Change quantity instead. At 200 brackets rather than 50, the mill demands 32 hours against 8 supplied, a load factor of 4.0, while the saw rises to 1.0 and the booth to 1.5. Same routing, same machines, a completely different shape of risk. This is the whole reason the ratio is recomputed for every job instead of stored as a work center attribute.

How EDGEBIC uses it

The load factor is an internal validation, not a field you type. It sits underneath constraint scheduling, where a planner marks one work center as the plant constraint and pins a job's operation there so the schedule is built outward from that point. The mechanics of that pin are covered in what is an anchor step in scheduling, and the reasoning behind choosing one constraint is covered in what is a bottleneck work center.

When a pinned job is scheduled, the engine builds the ratio table above and records whether the pinned resource holds the maximum. That verdict then feeds how tightly the constraint's capacity is packed, because a genuine constraint is worth protecting with a different allocation preference than an ordinary step. The related theory of constraints practice of protecting exactly one resource is what makes the check meaningful: marking half the plant as constraints dilutes it to nothing.

The two inputs are worth understanding on their own. Daily supply depends on machine count, which is explained in per instance capacity in scheduling, and the plant-wide version of the same demand-versus-supply question is covered in load versus capacity in scheduling.

The takeaway

A load factor turns a vague question, which machine matters most on this job, into one number per work center that you can compare on a single line. It is per job and per quantity by design, because a step that is comfortable on a small order can be the tightest resource on a large one, and that shift is invisible if you only track how busy machines are in general. Understanding it makes constraint scheduling feel less like a ritual and more like arithmetic. To see the same demand-versus-supply logic across a whole plan, read load versus capacity in scheduling and what is capacity utilization in scheduling, then explore EDGEBIC or, if you are coming from the legacy product, RMDB to EDGEBIC.