Interactive drag-and-drop Gantt for Odoo work orders and work centers — reschedule, sequence dependencies, and spot overloads in one view. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Uygulama manifestosu
İş akışınıza göre tasarlandı
Interactive drag-and-drop Gantt for Odoo work orders and work centers — reschedule, sequence dependencies, and spot overloads in one view.
Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.
Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.
ECOSIRE, Odoo ortamınızda geliştirir, yapılandırır ve kurar.
Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.
Odoo's Manufacturing app tracks work orders and routings well, but the moment your production plan lives across a dozen machines and shifting due dates, the standard list and Kanban views stop telling you the truth. Schedulers end up rebuilding the plan in a spreadsheet, hand-checking which operation feeds which, and discovering machine overloads only after the floor is already jammed.
The Work Order Gantt Scheduler is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports specifically for your plant. It is NOT an instant download — after purchase our team scopes your routings, work centers and shift calendars, then delivers a production-ready module for Odoo 17, 18 or 19 (Community or Enterprise) in a typical 2–4 week window.
At its core the module extends the standard mrp.workorder and mrp.workcenter models and layers an interactive Gantt UI on top. Work orders render as draggable bars grouped by work center, so a scheduler sees the whole shop floor on one timeline. Drag a bar to move a work order to a new machine or time slot and the change writes straight back to date_planned_start / date_planned_finished through the Odoo ORM — no exports, no re-keying. Operation sequence and dependencies (derived from the manufacturing order routing) are drawn as link lines, so you can see at a glance that cutting must finish before assembly begins. A compute layer (@api.depends on planned dates and work-center capacity) recalculates load in real time and highlights overloaded windows and scheduling conflicts in color, right where the collision happens.
Because we build it against your data model, we respect your reality: your shift calendars, your work-center capacities, your MO priority scheme, your Community-vs-Enterprise edition. Security follows Odoo conventions — access enforced through ir.model.access.csv and record rules so planners can reschedule while operators stay read-only. Everything is delivered as a clean, upgrade-safe addon with a proper __manifest__.py, versioned for your Odoo release, plus documentation, admin training and a post-go-live support window.
The result: your scheduler stops fighting spreadsheets and starts driving the plan from a single, live, drag-and-drop picture of the floor — inside the Odoo you already run.
Owns the daily and weekly plan across multiple machines. Lives in the drag-and-drop Gantt: moves work orders between work centers, resolves overloads before they hit the floor, and keeps due dates realistic without rebuilding the plan in Excel.
Needs a single live picture of shop-floor load and bottlenecks. Uses the timeline's color coding and overload highlighting to see where capacity is tight, judge whether a rush order fits, and hold shift handovers with a printable QWeb plan.
Responsible for a maintainable, upgrade-safe Odoo. Values that the module extends standard mrp models cleanly, ships with proper manifest and security config (ir.model.access.csv + record rules), and comes with docs and source handover rather than a black-box binary.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Interactive drag-and-drop Gantt for work orders by work center | Purpose-built, tailored to your routings and shift calendars | Possible but you design and build the UI from scratch | Sometimes, but generic and rarely matched to your plant | |
| Operation dependency & sequence visualization | Link lines drawn from your MO routing, built to your logic | Buildable, but dependency logic must be coded and tested by you | Varies by app; often absent or basic | |
| Overload / conflict highlighting vs work-center capacity | Real-time via @api.depends compute against your capacities | Requires you to build and maintain the capacity compute logic | Rarely capacity-aware to your shift calendars | |
| Fit to your data model, edition & version | Built for your Odoo 17/18/19, Community or Enterprise | Fully custom, but on your time, budget and risk | One-size app; you adapt your process to it | |
| Security roles (planner edit vs operator read-only) | Configured via ir.model.access.csv + record rules to your teams | You must design and verify the access model yourself | Generic roles; may need rework to fit your org | |
| Upgrade-safety & maintainability | Clean addon, proper __manifest__.py, source handover + docs | Depends entirely on your team's discipline | Black-box; you rely on the vendor's release cadence | |
| Delivery & support model | Built, installed, trained and supported by ECOSIRE (2–4 wks) | You staff, build and support it internally | Download + community forum; support quality varies |
No. This is a build-to-order module. ECOSIRE designs, develops, installs and supports it specifically for your plant's routings, work centers and Odoo edition. There is no instant download — you receive a production-ready addon that we build and deploy for you.
Typical delivery is 2–4 weeks from purchase and requirements sign-off. The exact timeline depends on the complexity of your routings, shift calendars and any integrations. We start with a short scoping call, validate on a staging environment, then deploy to production — so you see it working before go-live.
Every build includes a post-go-live support window for bug fixes and adjustments. We deliver the module versioned to your Odoo release with upgrade-safe code and documentation, and you receive the source for handover. Ongoing support, feature additions, and version-migration (e.g. moving from Odoo 17 to 18 or 19) are available as continued engagements — just tell us your target version.
We build for Odoo 17, 18 and 19, on both Community and Enterprise. The module extends the standard mrp.workorder and mrp.workcenter models, so it works with your existing Manufacturing app. We confirm your exact version and edition during scoping and ship a manifest versioned to match.
We build the module the Odoo way — a clean addon with a proper __manifest__.py, standard model inheritance, and security via ir.model.access.csv and record rules rather than hacks. That keeps it upgrade-safe and reduces conflicts with other apps. When you plan a major version upgrade, we can migrate the module as a follow-on engagement.
Yes. Because rescheduling writes to standard Odoo fields through the ORM, the same data is reachable over Odoo's XML-RPC and JSON-RPC APIs. External MES systems, shop-floor terminals or dashboards can read the schedule and push changes back, and we can scope specific integrations as part of the build.
Access is role-scoped using Odoo's native security model. We configure ir.model.access.csv and record rules so schedulers and planners can drag and reschedule, while operators and viewers get read-only access to the same Gantt. Roles are mapped to your team during setup.
Interactive drag-and-drop Gantt for Odoo work orders and work centers — reschedule, sequence dependencies, and spot overloads in one view.