IFC Comparison Reports for BIM Managers, Design Managers and Project Teams
A model-comparison tool is only as useful as the decisions it helps people make.
For this reason, an IFC comparison report should not be designed for one type of user.
A BIM Coordinator, BIM Manager, Design Manager and Project Engineering Manager need different levels of detail.
The management layer
The first layer should answer the fastest questions.
For a revision series:
- How many represented 3D elements exist?
- How has that number changed?
- Which categories increased or decreased?
- Which revision contains the largest change?
- Are changes accelerating or stabilising?
A visual HTML dashboard is well suited to this level.
It provides context before the user opens a detailed object list.
The coordination layer
A BIM Coordinator needs to know what produced the KPI.
That requires counts of:
- added elements;
- deleted elements;
- modified elements;
- placement changes;
- ambiguous identity groups.
The report should allow a user to move from a graph point to the underlying engineering change.
The engineering-object layer
For detailed investigation, object identity matters.
Useful fields may include:
- IFC class;
- source name/type;
- engineering category;
- GlobalId;
- source-specific identifier;
- owner/hierarchy information;
- geometry or placement change;
- revision dates.
The exact fields depend on the originating system.
An AVEVA E3D export may expose information that has no direct Revit equivalent, and vice versa.
Why Excel is still useful
Dashboards are excellent for communication.
Excel remains useful because engineering teams often need to filter, sort, copy, annotate and combine results with project information.
For that reason, Model Bridge currently produces both a visual HTML report and a detailed Excel output.
Structured JSON is also retained for future automation.
Reports should preserve uncertainty
A professional comparison report should not hide ambiguous matches.
If identifiers are duplicated or changed, the report should show that the result requires review.
This is especially important when model changes may have contractual or coordination consequences.
The software can support engineering judgement.
It should not impersonate it.
A report as a coordination meeting input
Before a coordination meeting, a BIM Manager can review the high-level timeline.
If one revision shows an unusual change, the team can open the detailed table.
This makes the discussion more focused.
Instead of asking “did anything major change?”, the team can ask:
- Why were 420 represented elements deleted?
- Why did piping modification activity increase?
- Why did the equipment count stay flat for three revisions?
- Was a GUID regeneration event caused by export settings?
That is a much more evidence-driven conversation.
From individual reports to a project dashboard
Today, a report may describe one revision series.
A future project-level system could generate the same hierarchy at a larger scale:
project → discipline/model → revision → engineering category → object
That would allow senior management to see the whole project while specialists retain traceability to individual IFC deliveries.
This is the natural next step for Model Bridge.
The first release establishes the model-level comparison and reporting foundation.
The future vision is a complete design-history evidence layer built from the IFC files the project already produces.