v73–v75 · ENTERPRISE PLATFORM
Sequence work against due windows and available hours.
Model duration, priority, due hours and changeover groups, then flag predicted lateness before the queue is released.
✓ Due-window model✓ Priority-aware queue✓ Late-job flags
Practical workflow
Model a queue before it becomes late
Example
Enter realistic productive duration rather than calendar duration. A job that needs four press hours and two hours of curing should be modeled according to the resource that is actually constrained; otherwise the queue can appear feasible while the downstream process is overloaded.
Interpretation
The simple optimizer orders by due window and priority, then exposes the predicted start and finish. A job whose finish passes its due hour is marked LATE immediately, giving the planner time to split the run, move work, approve overtime or renegotiate the deadline.
Boundary
Changeover groups are a reminder that sequence affects capacity. Similar stocks or processes may be cheaper to run together, but the tool does not override a tighter due date merely to minimize changeovers.
Why this module exists
Production context around the calculation.
A heuristic is not a shop-floor promise
The optimizer uses entered duration, priority and due windows. It cannot know an unentered breakdown, cure time or staffing constraint.
Changeovers have a cost
Grouping compatible jobs can reduce switching, while due dates can still justify breaking the group.
Late prediction is actionable
A predicted late job is surfaced before release so capacity, overtime, outsourcing or due-date decisions can be made deliberately.