Production planners running Odoo Community — and even many Enterprise teams — hit the same wall when they try to schedule the shop floor from the standard mrp.production and mrp.workorder list and calendar views. You can see that work orders exist, but you cannot see how they collide: which work center is over-booked on Tuesday, which order slips because its predecessor ran long, or where a two-hour gap could absorb a rush job. Odoo Community ships no drag-and-drop Gantt for manufacturing at all (the Gantt widget is an Enterprise component), and even where a timeline exists, it rarely reflects real work-center capacity, dependency chains, or your own scheduling rules. Planners end up rebuilding the picture in a spreadsheet every morning, which is exactly the manual, error-prone process Odoo was meant to replace.

This is a build-to-order module that ECOSIRE designs, builds, installs, and supports for your specific Odoo instance — it is not an existing apps.odoo.com download you install yourself. We deliver an interactive Gantt web view, rendered as an OWL component, that reads directly from your mrp.workorder and mrp.production records and lays them out on a horizontal timeline grouped by work center (or by manufacturing order, resource, or a custom group_by you choose during scoping). Each bar is driven by the order's date_planned_start / date_planned_finished (or date_start / date_finished) fields; dragging or resizing a bar writes the new schedule back through the standard ORM write() so every downstream compute — @api.depends duration rollups, state transitions, and capacity checks — stays consistent. We add compute fields and, where you need them, @api.constrains guards so the view refuses moves that break dependency order or exceed a work center's capacity.

Technically, the module is a clean, self-contained addon: a proper __manifest__.py declaring dependencies on mrp (and web), models extending mrp.workorder/mrp.production with any scheduling fields your rules require, an OWL client component plus its XML template registered as a new view type or a dedicated action, and QWeb assets bundled through the manifest's assets section. Access is governed by ir.model.access.csv and record rules so a planner sees only the work centers or manufacturing operations their groups permit — the Gantt never becomes a data-leak surface. Optional automated actions (server actions / base automation) can fire on reschedule to notify a team or re-run planning, and everything the view does is also reachable over the XML-RPC / JSON-RPC API, so external MES or forecasting tools can read and write the same schedule. We build and test against your target series — Odoo 17.0, 18.0, or 19.0 — and account for the Community-vs-Enterprise differences up front (on Enterprise we can integrate with the native Gantt renderer; on Community we ship a self-contained OWL timeline so you are not forced to upgrade edition).

Delivery is build-to-order and starts with a scoping call to confirm your Odoo version, edition, which models and date fields drive the bars, your grouping and capacity rules, and any dependency or constraint logic. We then build on a staging copy of your database, run UAT with your planners, and go live with a rollback plan and a post-go-live support window; typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company setups, deeper capacity/finite-scheduling logic, extra integrations (MES, APS, custom forecasting), and larger data-migration or reconfiguration volume increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.