Project Gantt Pro
The project management office upgrade for Project Gantt: server computed critical path with slack, named baselines with variance, split task segments, a resource histogram, earned value analytics, completion notifications, and export across eight formats including PDF, Excel, Microsoft Project XML, Primavera P6 XML and printable HTML.
Store price is USD 298 all-in: installing this also pulls the 1 paid ERP Heritage module it depends on.
Why this module
Genuinely new capability, not unlocked features.
Critical path that cannot disagree with the schedule
The backward pass runs over the exact dependency and working time graph the Community forward scheduler builds, so early and late dates, total slack and the critical flag are always consistent with the plan. The critical chain is highlighted and slack is a column, computed on the server.
Baselines, variance and earned value
Capture named snapshots manually or on a cron, then report start, finish and duration variance against them with comparison bars on the chart. Schedule performance (planned value, earned value, the schedule performance index) is derived from effort and progress, an early read on slippage.
Resource histogram and eight format export
A per resource load profile across the working calendar shades over allocation in red. The whole schedule exports on the server to PDF, Excel, CSV, Microsoft Project XML, Primavera P6 XML, iCalendar, JSON and printable HTML, so it works headless, respects record rules, and opens in the tools your stakeholders already use.
The PMO layer in detail
The reporting a project office actually runs on.
Keep more than one baseline and report variance against each
Capture as many named snapshots as the plan needs, each stamped with who took it and when. Comparison bars sit under the live bars and start, finish and duration variance columns quantify the drift, the foundation of honest progress reporting.
Pause and resume a task as named segments on one row
Work that stops and restarts is modelled as ordered, dated, non contiguous pieces and rendered as multiple bars on a single task row, so the timeline shows the real shape of the effort instead of one misleading continuous block.
Over allocation warnings across the working calendar
A per resource load profile aggregates every assignment across the calendar and shades any day a resource is committed beyond a hundred percent in red, with its peak load, so reassignment decisions rest on evidence rather than guesswork.
A quantitative read on whether you are behind
Budget at completion, planned value and earned value are derived from effort and progress against the plan, and the schedule performance index falls below one the moment the project slips behind its planned pace, an early warning long before a deadline is missed.
See which tasks have no float
A deterministic backward pass over the same working time graph the Community scheduler builds produces early and late dates, total slack and a critical flag for every task, so the chain with zero float is highlighted and slack is exposed as a column you can sort on.
Eight formats, from PDF to Primavera P6
The whole schedule exports on the server to PDF, Excel, CSV, Microsoft Project XML, Primavera P6 XML, iCalendar, JSON and printable HTML, so it runs headless and from the API, honours record rules, and opens in the steering pack and the client tools your stakeholders already use. Excel falls back to CSV when the spreadsheet writer is unavailable.
Export and notify
Eight export formats, and progress that reaches people on its own.
Combined with the JSON, iCalendar and PNG the planner already produces, the Pro layer takes the schedule into every format a stakeholder is likely to ask for, and raises a mail notification the moment a task or project crosses a completion threshold, so a milestone reaches the inbox without anyone watching the board.
Day in the life
Status meeting, answered from one screen
Before the weekly review a planner presses Critical Path, and the chain with no float lights up red. They press Baseline to snapshot the agreed plan, then drag two late tasks; the baseline bars stay put underneath so the slip is obvious and the variance columns quantify it. The resource panel shows a lead at a hundred and thirty percent for the sprint, so work is reassigned on the spot. The schedule performance index in the toolbar reads below one, confirming the project is behind the planned pace. They export the whole thing to PDF for the steering pack, to Microsoft Project XML and Primavera P6 XML for the two client teams, and to an iCalendar feed for the delivery leads, all generated on the server. When a key task tips over its completion threshold later that week, the stakeholders get a mail notification without anyone going back to the board.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Because the backward pass reuses the forward scheduler graph builder, total slack and the critical flag are derived from the same dates the plan was scheduled with; the two passes can never drift apart and report a critical task that the schedule contradicts.
A resource assigned beyond a hundred percent across overlapping tasks is shaded red in the histogram with its peak load, instead of the over commitment hiding inside individual task bars.
All eight formats, PDF, Excel, CSV, Microsoft Project XML, Primavera P6 XML, iCalendar, JSON and printable HTML, are generated on the server, so exports run in batch and from the API and honour the same record rules as the screen, rather than depending on what a single browser can see. Excel falls back to CSV when the spreadsheet writer is unavailable.
An administrator can push one Gantt layout to every user, but the action is gated behind a dedicated group, so a normal user cannot overwrite everyone else's saved view.
What is inside
Built to do the job, end to end.
- Critical path (engine reuse). A backward pass fills early and late start and finish and total slack and flags zero slack tasks, run over the Community engine inputs and stored on project.task for use as columns and on the timeline.
- Baselines and segments. eh.project.task.baseline stores named snapshots with captured by and on, driving variance columns and comparison bars; eh.project.task.segment models split tasks as ordered, dated pieces rendered on one row.
- Histogram, earned value and exports. A per resource daily load profile from assignments and calendars; budget at completion, planned value, earned value and the schedule performance index on project.project; and server side PDF (QWeb), Excel, CSV, Microsoft Project XML, Primavera P6 XML and printable HTML exporters returning a download, alongside the iCalendar, JSON and PNG the Community planner already produces.
- Governance and automation. eh.gantt.user.config keeps one upserted layout per user with an admin shared default behind a group; crons capture baselines weekly and raise task at risk activities for overdue and approaching deadlines; and a mail notification fires when a task or project crosses a completion threshold.
Honest about the edges
What this does not do, so nothing surprises you.
- Requires the Project Gantt module, which provides the planner, the data service and the scheduling engine this add on extends.
- Earned value is computed from effort and progress against the schedule, so the schedule performance index is fully derived; a cost performance index that needs posted actuals is only meaningful when timesheets are configured.
- The resource histogram profiles assignments across the working calendar; it is a load and over allocation view, not an automatic resource levelling solver that moves tasks for you.
- Microsoft Project and Primavera P6 export are one way XML documents carrying tasks, dates, progress and milestones; they are not a full round trip of every field in those tools, and import from Microsoft Project or Primavera P6 is not included.
- The completion notification fires by mail when a task or project crosses a configured completion threshold; it uses the standard Odoo mail layer, so delivery depends on your outgoing mail server being configured.
Odoo critical path, project baseline variance, multiple named baselines, resource histogram capacity planning, over allocation warnings, earned value SPI Odoo, schedule performance index, export MS Project Odoo, primavera p6 export odoo, gantt PDF export, gantt excel export, gantt csv export, gantt html export, gantt ical calendar export, gantt completion notification, split task segments Odoo, slack float analysis, PMO project office Odoo, project portfolio scheduling, gantt baseline snapshot, over allocation resource, Odoo project management pro, critical chain Odoo
A closer look at the PMO layer.
The PMO boardCritical path, schedule performance index and conflict flagging on one timeline.
Export to eight formatsPDF, Excel, CSV, HTML, JSON, iCalendar, Microsoft Project and Primavera P6, straight from the toolbar.
Baselines and resource histogramStacked named baseline lanes, variance, and a daily resource load profile that turns red on over allocation.
Import a plan back inRound trip a schedule from Excel or JSON through the import wizard.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Project (project) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 5987 |
| Technical Name |
eh_project_gantt_enterprise |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module