MRP L3 — APS Scheduling (Finite Capacity)

MRP N3 — APS Scheduling (DYONYSOS)

Confirmed manufacturing orders in Odoo Community are scheduled at infinite capacity: the plan does not account for what is already queued at a work center, nor customer priorities, nor time lost on changeovers. This app adds a finite-capacity scheduling layer on top of Manufacturing, without replacing it:

• Scenarios: a scenario captures a snapshot of the proposed plan (nothing is changed on the actual MOs until it is applied). “Compute” / “Recompute” regenerates the lines from the current state of the MOs.

• Heuristic algorithm (greedy, NOT a linear or constraint programming solver): on each work center, eligible MOs are sorted by priority then by due date (earliest first in case of a tie), then placed one after another in the next available slots of the center's calendar, adding a flat changeover time whenever the product changes from one MO to the next.

• Before / after comparison: each scenario line shows, side by side, the current sequence of the manufacturing order and the proposed sequence, the difference, a delay signal relative to the due date, and the added changeover time.

• Controlled application: an “Apply scenario” button with an explicit confirmation step (no blocking wizard) that copies the proposed dates onto the actual manufacturing orders; restricted to APS managers.

• Customer priority: priority field on the MO, automatically filled from the selected customer's default priority.

Acknowledged and documented limitation (see README and doc/PITCH.md): this is a sequencing heuristic, not a combinatorial optimization solver. Complementary to the dyo_mrp_scheduling app (load / capacity, MPS) — both rely on the dyo_mrp_common foundation and may be connected by a future bridge module.

Demo data: a contract machining shop with several manufacturing orders competing for the same work centers, with different priorities and due dates.