Future Direction: Project-Wide IFC Control Across All Discipline Models

Most IFC comparison starts with one model.

A piping model has several revisions. An architectural model has several revisions. A subcontractor delivers another series.

Each series can be compared separately.

But an EPC or multidisciplinary project raises a more powerful question:

What if we analyse all IFC files of the project together?

This is a future Model Bridge direction, not a feature of the first release.

The project already contains the data

Large projects naturally generate repeated model deliveries.

For example:

• architecture;
• structure;
• piping;
• HVAC;
• electrical;
• equipment;
• vendor packages;
• civil works;
• subcontractor models.

These models are often federated for coordination, but their revision histories can also be treated as data.

Each file represents the state of one part of the design at a specific point in time.

Taken together, they can form a project-level design history.

From model KPI to project KPI

The current comparator can analyse a sequence of revisions from one model and report unique represented 3D elements, categories and changes.

The future idea is to preserve that model-level history and add an aggregation layer.

Conceptually:

Project

→ Discipline / package

→ Model

→ Revision

→ Engineering category

→ Object

At project level, a manager could see the total represented 3D content and how much each package contributes.

At model level, the BIM team could still inspect the exact revision changes.

Questions a project-wide dashboard could answer

A whole-project IFC history could support questions such as:

• Which discipline changed most this week?
• Which subcontractor has not issued an updated IFC recently?
• Where is most new model content being added?
• Which package is showing repeated large deletion/re-addition cycles?
• Is one discipline stabilising while another remains highly volatile?
• How many represented 3D objects exist across the current project state?
• Which revisions introduced the largest cross-project changes?

These are not answers available from a single federated-model screenshot.

They require time history.

Why federated models are only part of the answer

Federation is essential for spatial coordination.

It allows architecture, structure and MEP or plant models to be reviewed together.

But federation primarily answers:

How do the current models fit together?

Revision analytics answers:

How did these models arrive at the current state?

The two concepts are complementary.

A future Model Bridge project dashboard could sit beside the federated coordination workflow rather than replace it.

Mixed authoring systems

Project-wide analysis becomes especially interesting when disciplines use different native applications.

For example:

• AVEVA E3D for plant;
• Revit for building/MEP;
• SolidWorks/3DEXPERIENCE for mechanical packages;
• other IFC-capable applications for specialist contractors.

This is why current source-aware comparison work is important.

The future system would need to preserve authoring-specific semantics while normalising high-level KPIs.

A model-based evidence layer for EPC

EPC progress reporting often combines schedules, document registers, engineering deliverables and subjective status assessments.

IFC revision history could add another independent source of evidence:

what the 3D deliverables actually contain.

It would not replace earned value, document progress or engineering planning.

It could complement them.

For example, a package reported as nearly complete but still showing major geometry turnover might deserve attention.

Conversely, a model with stable geometry may still have ongoing non-geometric engineering work, so the KPI must be interpreted carefully.

The first release is the foundation

Project-wide control requires several difficult capabilities:

• stable revision matching;
• clear chronology;
• reliable counting policy;
• source-aware classification;
• caching for large model sets;
• discipline/package ownership;
• project-level aggregation;
• scalable reporting.

The current multi-revision IFC comparator establishes the first five foundations.

The project-wide concept is therefore not a separate idea.

It is the next level of the same architecture.

First: understand one model across time.

Next: understand the whole project across time.