Definition · Lateness, tardiness, and the four objectivesFor a job finishing at C_j with due date d_j, the lateness is L_j = C_j − d_j and may be negative; the tardiness is T_j = max(L_j, 0) and may not; and U_j is 1 when C_j > d_j.
The four objectives are L max (the worst lateness, which can be negative if everything finishes early), T max (the worst tardiness, which cannot), sum T (total tardiness) and sum U (the number of late jobs). They are four questions, not four spellings of one.
Theorem · Earliest due date minimises maximum latenessOrdering the jobs by d ascending minimises L max, and it also minimises T max.
Take any order and any adjacent pair a then b with d_a > d_b, starting at time t and finishing at t + p_a + p_b. Before the swap the two latenesses are t + p_a − d_a and t + p_a + p_b − d_b; the larger of the two is at least the second one.
After the swap they are t + p_b − d_b and t + p_b + p_a − d_a. The first of these is smaller than t + p_a + p_b − d_b because p_b < p_a + p_b; the second is smaller than t + p_a + p_b − d_b because d_a > d_b. So both new latenesses are below the old maximum of the pair.
No other job moved, so L max over the whole schedule did not increase. Repeating on any remaining out-of-order pair reaches the due-date order without ever increasing L max, so that order attains the minimum. T max is max(L max, 0), so the same order minimises it.
□
Notice what shape that argument has. The unweighted case gave an identity and a strict improvement; this one gives only that the swap does no harm. That is the normal situation for a maximum, and it is enough: a sequence of harmless swaps reaching the rule's order shows the rule's order is at least as good as where you started, whatever that was.
The rule, on five jobs, doing exactly what it promises
jobs A 6:8 B 4:4 C 5:12 D 3:6 E 7:20 p:d
EDD B D A C E
job p d C L T
B 4 4 4 0 0
D 3 6 7 1 1 late
A 6 8 13 5 5 late
C 5 12 18 6 6 late
E 7 20 25 5 5 late
L max 6 T max 6 sum T 17 late 4 of 5
best L max over all 120 orders: 6 EDD attains it
best T max over all 120 orders: 6 EDD attains it
L max = 6 is set by C, which finishes at 18 against a due date of 12. Seventeen hours of work are due by hour twelve and twenty-five hours of work exist, so something has to be late; the rule's achievement is that nothing is more than six hours late, and the enumeration confirms that no order does better.
The same order, on the objective it does not solve
EDD B D A C E T = 0, 1, 5, 6, 5 sum T 17 late 4
the best B D C A E T = 0, 1, 0, 10, 5 sum T 16 late 3
and its L max is 10, not 6
Moore–Hodgson late 2, which is the enumerated minimum
best sum T over 120 orders 16 best sum U over 120 orders 2
Example · Where the extra hour of tardiness wentThe order that attains sum T = 16 differs from EDD by one adjacent swap: C and A change places. C then finishes at 12 exactly on its due date and contributes nothing, while A slides from 13 to 18 and goes from 5 hours tardy to 10.
Total tardiness falls from 17 to 16 because one job was taken from 6 to 0 while another rose by 5. Maximum lateness rises from 6 to 10, because the worst job is now worse. Both orders are optimal — for different objectives — and choosing between them is a decision about whether a schedule is judged on its worst job or on all of them.
So EDD is optimal for two of the four due-date objectives and beaten on the other two: 17 against 16, and 4 late against 2. The second of those has a rule, and “Minimising the Number of Late Jobs” is it. The first does not, and the honest thing is to say so.
The boundary, stated rather than worked around
1 || sum T — one machine, minimise total tardiness — has no adjacent-exchange rule. Run the argument and see why: swapping a and b changes T_a and T_b, but each of those changes is a clipped quantity, so the amount depends on whether t + p_a sits above or below d_a, and the same swap moves the sum by different amounts in different parts of the schedule. There is no condition on the pair alone that decides it.
This is worth dwelling on because it is the one place on the course where the technique runs out, and a reader who has seen three rules fall out of one subtraction will expect a fourth. The lab's answer is to enumerate: it reports 16 and the order that attains it, and says that no rule here produced that order. On a larger instance the enumeration is not available either, and then the honest report is a heuristic value with a bound attached — which is the shape of answer “Integer Programming” is about.
One more warning about due dates, and it is about the model rather than the rule. A due date here is a number the objective is measured against, not a constraint. Nothing in this model refuses to run a schedule in which four of five jobs are late; the arithmetic prices it. If a date genuinely cannot be missed it is a constraint, the problem may be infeasible, and that is a different question from any of the four here.