v2.65Latest
Line loading no longer says “no feasible plan” above the plan it found when some orders are already past due.
- FixedWhen orders on a line were already past their due time, Scheduling → Line loading headed its result in red “No feasible plan — the constraints conflict” and disabled Save as a scenario — then showed a plan below, with the changeover hours it gives back and the late orders named per machine. That plan is now headed for what it is: the least-late plan, because no plan can meet every due time within the machines’ hours. A machine with too few hours for its work is still “no feasible plan”.
- FixedPredictive Maintenance → Preventive interval: a machine family with one breakdown of its own reads “plant-wide fit (1 own life)”, not “1 own lives”.