A demonstration of the coordination reporting GIRIH X builds for delivery teams: clash burndown, a discipline-pair clash matrix, resolution status, ageing and responsibility, tracked across every discipline through to closure. All data below is synthetic.
What this demonstrates
Coordination BI on live model data. How GIRIH X turns Navisworks and Revizto exports into a standing dashboard for delivery teams: burndown, matrix, ageing and responsibility through to closure.
Synthetic demo data. Client deployments read live clash and BCF data from the CDE.
Illustrative pipeline for a production deployment
Federated model (Revit / ACC)
Structure, mechanical, hydraulic, electrical and fire models federated
Clash tests (Navisworks / Revizto)
Hard and clearance clash results per discipline pair
BCF issues
Assigned issues with responsible party, status and due date
CDE metadata
Model revisions so clashes tie to the current federation
Coordination BI pipeline
Output
Clash resolution dashboard
Burndown, discipline-pair matrix, status, ageing and responsibility, refreshed each cycle
Synthetic pipeline for illustration. Every clash traces to its BCF issue and the federation revision it was found in.
Open clashes
312
Resolved (30 days)
486
Avg age (open)
9.4 d
Overdue
28
| Struct | Mech | Hyd | Elec | Fire | |
|---|---|---|---|---|---|
| Struct | 96 | 54 | 22 | 31 | |
| Mech | 96 | 71 | 44 | 38 | |
| Hyd | 54 | 71 | 29 | 18 | |
| Elec | 22 | 44 | 29 | 12 | |
| Fire | 31 | 38 | 18 | 12 |
Darker cells carry more clashes. Mechanical × Structure and Mechanical × Hydraulic are the heaviest coordination fronts.
How these demos relate to the systems we build for clients.
Clash resolution across the whole coordination programme: how many clashes are open, how fast they are being closed, which discipline pairs carry the most, how they age, and who is responsible. It turns raw clash counts into a managed, reportable workflow.
No, every figure here is synthetic. Client dashboards read live clash results from Navisworks or Revizto and BCF issues from the common data environment, so the numbers update automatically each federation cycle.
Because clashes are a relationship between two disciplines, not a property of one. The pair matrix shows where the real coordination effort sits, so leads can focus the right two trades on the right interface instead of chasing a single number.
The detective is where a coordinator inspects and resolves individual clashes in the model; this dashboard is where the programme is managed and reported. Together they cover detection through to closure.
Everything in the Playground is built with the same stack we deploy for clients: configurators driven by real product masters, planners connected to BIM data, and AR experiences served straight from the product catalogue.
Start a Conversation