Finite Capacity Planning & Scheduling (APS)

This is a build-to-order module, not an off-the-shelf apps.odoo.com download, so there is no instant download. After purchase we run a short scoping call to capture your work centers, routings, shift calendars and sequencing rules, then build, install and validate the module on your Odoo 17, 18 or 19 environment. Typical lead time is 2 to 4 weeks depending on the number of work centers, changeover complexity and any MES/BI integration. You will get a written delivery timeline during scoping.

Every engagement includes a post-launch support window covering bug fixes and compatibility with Odoo minor releases on your major version. Because the module is built on standard models and writes back to native date_planned fields, it stays compatible when you patch within a major version. Moving between major versions (for example 17 to 18) is an upgrade we scope separately. An optional ongoing support and enhancement plan covers new sequencing rules, added work centers and priority changes over time.

Odoo core schedules with infinite capacity: it back-schedules work orders from the deadline as if each work center had unlimited concurrent capacity, so plans can show multiple jobs on the same cell at once. That looks on-time in the MO but overloads the floor and forces manual re-sequencing. This module adds a real finite-capacity solver that respects concurrent-capacity limits, shift calendars, setup and changeover time, and order priority — giving you dates you can actually commit to.

Both. The module is built on manufacturing (mrp), routings and resource.resource_calendar, which exist in Community and Enterprise. We target Odoo 17, 18 and 19. On Enterprise we can align with the native Planning/Gantt look and feel; on Community we ship our own OWL drag-and-drop Gantt so the planner experience is the same. We confirm your exact edition and version during scoping.

No. The engine writes its results back to the standard mrp.workorder date_planned_start and date_planned_finished fields rather than a parallel shadow schedule, so MRP, deliveries and native reporting read the same dates you plan. It layers on top of your existing routings and BoMs without replacing them, and access is scoped with ir.model.access.csv and record rules so it does not change what other users can see or do.

Yes. The planning model is reachable over Odoo's XML-RPC and JSON-RPC API, so an MES can pull the finalized sequence and push actual start/finish times back, and tools like Power BI can read work-center load and utilization. We can also add automated actions or an ir.cron job to re-run the solver automatically when new MOs are confirmed. Integration scope is agreed during the initial call.