Odoo's project.project and project.task models handle a single project well, but multi-tier delivery breaks the native reporting story. Once a program is split into a parent engagement with several subprojects — each carrying its own tasks, timesheets, and deadlines — there is no core object that represents "this project and everything beneath it." Managers end up exporting timesheet lines to a spreadsheet to answer basic questions: how many hours has the whole program consumed, how does logged effort compare across sibling subprojects, and which branch of the tree is drifting past its planned hours. The native Project analysis views and the timesheet grid stop at a flat, per-project grouping; they do not aggregate recursively across a hierarchy.

Project Analysis is a made-to-order Odoo module that ECOSIRE designs and builds around your project structure. We add an explicit parent/child relationship to project.project (a parent_id self-reference plus a stored complete_name and a parent_path hierarchy field) so a project can own subprojects to any depth. On top of that we build computed roll-up fields — total logged hours, effort by subproject, planned-vs-actual variance, and progress — as stored @api.depends computes that recurse over the child set and sum the related account.analytic.line timesheet records. Because the aggregates are stored and indexed, they drive fast pivot, graph, and list reporting views, and they respect the same access rules your users already have.

Technically, the build is a clean custom addon with its own __manifest__.py (depending on project and hr_timesheet, and optionally sale_timesheet if you bill from these hours). We ship the hierarchy fields and recursive computes in models/, a dedicated analysis model (a models.Model or a SQL-backed report view) that flattens the tree into one queryable dataset for the pivot/graph, QWeb PDF summaries per parent project, and — where useful — an automated action that flags a subproject when its actual hours cross a configured percentage of plan. Security is handled properly with ir.model.access.csv entries and record rules so a project manager only sees their own hierarchy, and every new field is exposed through XML/OWL view extensions rather than overriding core views destructively. Everything is compatible with Odoo 17.0, 18.0, and 19.0, and works on both Community and Enterprise (with the richer analytic/billing tie-ins lighting up on Enterprise where sale_timesheet and advanced accounting are present). The same roll-up data is reachable over the XML-RPC/JSON-RPC API for external dashboards.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, map your real project hierarchy and timesheet practice, then build, test on a staging database with your data, and run UAT before touching production. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company consolidation, deep analytic-account and billing integration, additional custom KPIs, and heavy historical-data migration each increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.