What is a federated BIM model and why is it used on Irish NDP projects?

A federated BIM model is a combined 3D model that brings together separate discipline models (architectural, structural, MEP, ELV) into a single coordinated view for clash detection and coordination review. Federated models are used on Irish NDP projects because: each discipline team maintains its own authoring model (in Revit, Tekla or ArchiCAD) rather than working in a single shared model — this preserves each team's workflow and authoring tool freedom while enabling cross-discipline coordination. The federated model is typically assembled in Navisworks for clash detection and in the project CDE for issue management.

How is a federated BIM model different from a single combined model?

A federated model keeps each discipline's model separate — the architect, structural engineer, MEP engineer and ELV consultant each maintain their own model files in their own software. These files are referenced together in Navisworks for clash detection and coordination. A single combined model would have all disciplines in one file — which creates software compatibility problems, workflow conflicts (who is the model owner?) and version control issues. The federated approach is the ISO 19650 standard for Irish NDP projects.

What disciplines are typically in a federated model on an Irish hospital project?

An Irish hospital NDP project typically has a federated model combining: Architectural model (Revit or ArchiCAD); Structural model (Revit or Tekla); Mechanical model (Revit MEP — HVAC, pipework); Electrical model (Revit MEP — mains distribution, lighting); ELV model (Revit — fire alarm, security, structured cabling, nurse call); and potentially a Civil/site model for ground floor coordination. The ELV discipline model is ASDV's contribution to the federated set — issued in NWC format to Navisworks and in the agreed format to the project CDE.

What is the most common coordination failure in Irish federated models?

Incorrect or missing shared coordinates — where two or more discipline models are not using the same survey point or project base point, causing the models to be displaced from each other when federated in Navisworks. When models are displaced even slightly, all clash detection results are meaningless — every element appears to clash with everything in the adjacent model. Shared coordinate confirmation, documented in the BEP and verified before the first federation, is the most important setup step in Irish NDP BIM coordination.

How does ASDV's ELV model integrate into a federated model for Irish NDP projects?

ASDV's ELV Revit models use the project's confirmed shared coordinate origin from the BEP. Models are exported as NWC files in the agreed Revit version, named to the project's ISO 19650 naming convention, and published to the project CDE in the Shared status for coordination review. Clash tests are run against structural and MEP models in Navisworks by ASDV before each coordination review submission — so that the Irish design team receives pre-screened models rather than raw unclash-checked content.

Federated BIM Models Ireland — Combining Disciplines

The federated BIM model is the mechanism by which a dispersed Irish design team — architect in Dublin, structural engineer in Cork, MEP consultant in Galway, ELV specialist in New Delhi — produces a spatially coordinated building model. It is the technical foundation of ISO 19650 information management on Irish NDP projects, the platform for clash detection in Navisworks, and the digital representation of the building that the contractor prices from at tender stage. Understanding how federated models work — how they are set up correctly, what coordination failures look like, and how the ELV discipline integrates — is operationally important for every Irish project manager working on a BIM-mandated NDP commission.

What Is a Federated BIM Model?

A federated BIM model is a combined 3D model that brings together separate discipline models (architectural, structural, MEP, ELV) into a single coordinated view for clash detection and coordination review. Each discipline team maintains its own authoring model — in Revit, Tekla, ArchiCAD or whichever tool it uses — and those models are combined in Navisworks (or an equivalent clash detection platform) for coordination. The key characteristic of a federated model is that no single team owns or edits the federated set directly — the federated model is read-only, derived from the authoritative discipline models maintained in the project CDE.

How Federation Differs from a Single Unified Model

A federated model keeps each discipline's model separate. A single combined model would have all disciplines in one file — which creates: software compatibility problems (Revit cannot natively contain Tekla structural content); workflow conflicts (who is the model owner when the architect and structural engineer both need to work in the same file simultaneously?); and version control issues (any change by any discipline updates the shared file, creating potential for accidental overwrite). The federated approach is the ISO 19650 standard for Irish NDP projects — and in practice, is the only workable approach for multi-disciplinary Irish NDP commissions involving 6–10 design team members across multiple firms.

Incorrect shared coordinates — the most common federation failure on Irish NDP projects. When two discipline models are not using the same coordinate origin, every element appears to clash with everything in the adjacent model when federated in Navisworks, producing thousands of meaningless false clash results that take days to diagnose and correct. Shared coordinate confirmation at project inception is the most important federation setup step.

Why Federated Models Are Used on Irish NDP Projects

Cross-discipline clash detection — ELV containment vs structural elements and MEP ducts; MEP pipework vs architectural finishes; structural elements vs architectural openings
Builder's work information — Structural openings for services risers and penetrations extracted from the federated model rather than drawn manually
Tender quantity take-off — Material quantities extracted from coordination-complete LOD 300 models at Stage 4
Construction programme information — Sequence models produced from the federated set to plan construction logistics
ISO 19650 compliance — The federated model is the delivery vehicle for the coordinated information required by HSE, OGP and DoE EIRs at each RIAI stage gate

The Federation Workflow — From Discipline Models to Coordinated Set

Confirm Shared Coordinates Across All Disciplines

The most critical step. All discipline models must reference the same survey point and project base point — typically set by the lead designer (architect) at project inception and confirmed in the BEP. ASDV receives the shared coordinate file from the lead designer and confirms correct alignment before any ELV Revit content is modelled.

Combine Discipline Models in Navisworks

All discipline models exported as NWC files (from Revit) or IFC (from other tools) are combined in a Navisworks NWF file. The NWF references the discipline models but does not embed them — when a discipline updates its model, the NWF automatically picks up the updated content at the next reload.

Run Clash Detection and Issue Reports

Clash tests run against specific discipline pairs: ELV vs Structural, ELV vs MEP, MEP vs Structural, Architectural vs all. ASDV runs internal ELV clash tests before submitting to the coordination review — ensuring the Irish project team receives pre-screened models rather than raw unclash-checked content.

Update, Re-Federate and Re-Check

Design teams update their discipline models to resolve clashes. The federated model is updated with the revised NWC files. Clash detection is re-run to confirm resolution. The cycle continues through the Stage 3 coordination phase until all hard clashes are resolved and the model is Stage 4-ready.

Common Federation Problems on Irish Projects

Incorrect shared coordinates — The most expensive coordination failure: all clash results are meaningless until corrected
Stale discipline models — Navisworks loaded with superseded model versions rather than current CDE-published content
Missing ELV discipline model — ELV content not federated, so ELV/MEP clashes are not detected until site
File format incompatibility — Tekla or ArchiCAD content not successfully converted to NWC or IFC for federation
Model size/performance issues — Federated model too large to run efficiently, slowing coordination review cycles

ASDV participates in federated model coordination for Irish NDP projects. See our BIM support services Ireland and clash detection Navisworks guide for the broader coordination context.

FAQs — Federated BIM Model Ireland

A federated model combines separate discipline models (architectural, structural, MEP, ELV) into a single coordinated view for clash detection and coordination review. It is used because it preserves each discipline's authoring tool workflow while enabling cross-discipline coordination — the ISO 19650 standard for Irish NDP projects.

A federated model keeps discipline models separate, referenced together in Navisworks for clash detection. A single combined model has all disciplines in one file — creating software compatibility problems, workflow conflicts and version control issues. The federated approach is the only workable standard for multi-disciplinary Irish NDP commissions.

Architectural (Revit/ArchiCAD), Structural (Revit/Tekla), Mechanical MEP (Revit), Electrical MEP (Revit), ELV (Revit — fire alarm, security, cabling, nurse call). The ELV discipline model is ASDV's contribution — issued in NWC format to Navisworks and in the agreed format to the project CDE.

Incorrect shared coordinates — discipline models using different coordinate origins, causing models to be displaced when federated. Every element appears to clash with everything, producing thousands of meaningless false clash results. Shared coordinate confirmation in the BEP before any modelling begins is the most important federation setup step.

ASDV's ELV Revit models use the project's confirmed shared coordinate origin. Models are exported as NWC files, named to the project's ISO 19650 naming convention, and published to the project CDE. ASDV runs internal ELV clash tests before each coordination review submission — so the Irish team receives pre-screened models.

Get a Free Federated BIM Coordination Assessment for Your Irish Project

ASDV integrates ELV discipline models into your federated BIM set — shared coordinates, CDE issue and pre-screened clash reports.

Request Free Assessment

Or: +91-8800334308 · WhatsApp Us

ASDV Design Team

BIM Coordination Specialists — ASDV Consultant Ireland

ASDV integrates ELV discipline models into federated BIM sets for Irish NDP projects — shared coordinates, CDE publication and pre-screened Navisworks clash reports. Remote delivery from New Delhi.