BIM capability
Federated BIM coordination integrating architectural, structural and MEP models through shared coordinate systems, link management and Navisworks aggregation for design review and clash preparation.
Model federation brings discipline-specific authoring models into a single coordinated environment for spatial review, clash detection preparation and design decision-making. Federation does not merge authoring files; it overlays linked or exported models positioned through a shared coordinate system agreed at project outset.
Multidisciplinary coordination sessions follow a structured agenda with defined viewpoints, responsibility matrices and documented outcomes. The BIM coordinator manages link versions, visibility sets and federation model currency so that review participants work from consistent, approved revisions.
Effective federation depends on upstream production quality — correctly positioned links, current revisions and consistent level and grid definitions. Coordination meetings surface spatial conflicts and design assumptions; resolution occurs in authoring models before re-federation at the next milestone.
Federation protocols define which models are mandatory at each coordination stage, acceptable link tolerances and the escalation path when disciplines issue non-concurrent revisions. Without governance, coordination sessions degrade into version disputes rather than spatial problem-solving.
On complex buildings, MEP routing depends on architectural ceiling zones, structural framing and facade build-ups that only become visible through federated review. Single-discipline modelling in isolation produces technically correct systems that cannot be installed in the available spatial envelope.
Coordination is a recurring process, not a one-time event. Federation models are refreshed at weekly or milestone intervals with tracked issue logs linking coordination findings to model revisions and responsible appointments.
Large projects may federate models by zone, phase or building segment to manage file size and session performance. The federation strategy is documented in the BIM execution plan with rules for partial federation when full building aggregation exceeds platform performance thresholds.
Survey point, project base point and true north alignment across all discipline models.
Overlay protocols, visibility rules and reload schedules documented in BEP.
Aggregated coordination model with discipline colour coding and search sets.
Scheduled multidisciplinary reviews with agenda, attendees and minutes.
Saved review locations for plant rooms, risers, ceiling voids and key interfaces.
Zone and system ownership documented for coordination action assignment.
Pre-session check confirming all linked models match current CDE issue.
Zone-based aggregation for large projects exceeding single-model performance limits.
Marked viewpoints, screenshots and action logs distributed after each session.
Penetrations, openings, sleeves and support zones reviewed at discipline boundaries.
Structured log linking findings to model elements and responsible appointments.
Updated aggregation following model revisions confirming closure of coordination items.
All appointments confirm shared coordinate benchmark before first model link.
Set up Navisworks aggregation with discipline appearance, search sets and default viewpoints.
Verify linked model revisions match CDE approved issues before coordination meeting.
Walk predefined zones with discipline leads documenting spatial findings and actions.
Assign findings to responsible appointments with target resolution dates.
Discipline teams resolve findings in source models following change control.
Refresh aggregation and confirm closure of tracked coordination items.
Document coordination completion status before construction issue gate.
Linked models positioned within agreed millimetre tolerance of shared coordinate benchmark.
Level names, elevations and grid labels consistent across federated models.
All links reloaded to current CDE revision within 24 hours of issue.
Aggregated model navigable at acceptable frame rate on coordination workstation specification.
Consistent appearance overrides applied per BEP discipline colour table.
All critical review zones covered by saved viewpoints before first coordination session.
Navisworks search sets correctly isolate discipline and system elements for targeted review.
Each coordination finding linked to model element identifier and responsible appointment.
Zone split planes documented and consistent across discipline exports.
NWC export parameters identical across disciplines for equivalent detail and origin.
Minutes include attendees, models reviewed, findings, actions and next session date.
Resolved items confirmed in re-federated model with screenshot or viewpoint reference.
Building shell envelope
Structural framing
Ceiling void MEP routing
Plant room layout
| Milestone | Element | Purpose | Responsible | Geometric | Alphanumeric | Documentation | LOD / LOIN | Control | Acceptance |
|---|---|---|---|---|---|---|---|---|---|
| First federation | Building shell envelope | Confirm spatial envelope for MEP routing | Architectural appointment | External walls, floors, roof | Level names, floor-to-floor heights | Architectural coordination model | LOIN 2–3 — schematic to coordination | Coordinate benchmark survey | All disciplines confirm link position |
| Design development coordination | Structural framing | Penetration and support coordination | Structural appointment | Beams, columns, slabs with openings | Member sizes, opening dimensions | Structural coordination model | LOIN 3 — coordination geometry | Interface checklist | Coordination session sign-off |
| MEP coordination | Ceiling void MEP routing | Spatial allocation and clash preparation | MEP BIM coordinator | All MEP systems in void zone | System types, sizes | Federated Navisworks model | LOIN 3 at coordination gate | Viewpoint walkthrough | No unresolved spatial conflicts |
| Construction coordination | Plant room layout | Installation sequence and access clearance | MEP BIM lead | Equipment, piping, cable tray | Equipment tags, maintenance zones | Plant room viewpoint set | LOIN 4 — detailed geometry | Full room verification | Construction issue readiness |
Federation coordination connects MEP routing decisions to structural penetration schedules and architectural ceiling height commitments. Early federated review of riser locations, plant room layouts and distribution corridors prevents costly redesign when construction sequencing begins.
Facade, roofing and underground works introduce external interfaces that MEP models must respect. Federation sessions include these appointments when their models affect MEP routing or support requirements.
Specialist subcontractors — lifts, kitchen equipment, medical gases — contribute federated models or dimensional surveys at defined milestones. The coordination matrix assigns review responsibility for each specialist interface to prevent gaps in the aggregated spatial review.
ISO 19650-2
BS 1192
PAS 1192-2
AIA LOD Specification
Autodesk Navisworks
ISO 16739
buildingSMART
Client BEP
| Standard / Reference | Full title | Organization | Application area | Relevance | Edition status |
|---|---|---|---|---|---|
| ISO 19650-2 | Organization and digitization of information about buildings and civil engineering works — Delivery phase | ISO | Coordination information exchange | Exchange information requirements for federated model delivery. | Published — confirm edition at project start |
| BS 1192 | Collaborative production of architectural, engineering and construction information | BSI | Collaborative production | Common data environment and spatial coordination conventions. | Published — confirm edition at project start |
| PAS 1192-2 | Specification for information management for the capital/delivery phase of construction projects using BIM | BSI | Coordination process | Coordination and clash detection process reference for UK projects. | Published (2013) — superseded by ISO 19650 |
| AIA LOD Specification | Level of Development Specification | AIA | Coordination readiness | Minimum LOD for meaningful federation at each stage. | Published edition — confirm at project start |
| Autodesk Navisworks | Navisworks Coordination Best Practice | Autodesk | Federation platform | Aggregation, viewpoint and clash preparation workflows. | Current platform version — confirm at project start |
| ISO 16739 | Industry Foundation Classes (IFC) for data sharing | ISO | Cross-platform federation | IFC-based federation where Revit links are not available. | Published — confirm edition at project start |
| buildingSMART | openBIM Coordination View (IFC) | buildingSMART | IFC coordination | IFC model view for federation without proprietary links. | buildingSMART specification |
| Client BEP | Project BIM Execution Plan | Project-specific | Federation protocol | Project-specific link strategy, meeting schedule and responsibility matrix. | Project issue — confirm at appointment |
Applicable standards depend on the project jurisdiction, information requirements, contract documents, delivery method and authority requirements. The adopted editions shall be confirmed at project commencement.
Link strategy, coordinate benchmark and aggregation rules per BEP.
Aggregated multi-discipline model with appearance and search sets.
Saved review locations for all critical coordination zones.
Session records with findings, actions and responsible appointments.
Zone and system ownership table for coordination action assignment.
Tracked findings with status, resolution date and verification reference.
Pre-session verification of linked model revision currency.
Penetration, sleeve and opening schedules from federated review.
Evidence of closure for resolved coordination items.
Formal acceptance of coordination completion at defined gates.
All federated models verified against CDE approved revisions before meeting.
Periodic survey confirming link positions within agreed tolerance.
All critical zones have saved viewpoints before session commencement.
Meeting records include all required fields per BEP template.
Every finding assigned to named appointment with target date.
Resolved items require re-federation screenshot or viewpoint confirmation.
Required appointments present or represented at coordination sessions.
Aggregated model meets navigability threshold on coordination hardware.
Discipline isolation sets tested for correct element selection.
Overdue coordination actions escalated per BEP defined timeline.
Sessions held per agreed BEP schedule.
100% of scheduled sessions
Coordination findings resolved by target date.
>= 90%
Sessions using current approved CDE revisions.
100%
Critical spatial conflicts identified before clash detection stage.
Trend reduction per phase
Predefined viewpoints used versus ad hoc navigation.
>= 80%
No. Federation overlays linked or exported models in a coordination environment. Authoring remains in discipline-specific files with positioning through shared coordinates.
Frequency is defined in the BIM execution plan — typically weekly during design development and bi-weekly at construction issue. Milestone gates may require additional sessions.
The session proceeds with available models and late revisions are flagged. Non-current models are excluded from sign-off until the appointment issues an approved CDE revision.
When full building aggregation exceeds platform performance limits, zone or phase federation is used. Boundaries are documented and consistent across all discipline exports.
Federation sessions resolve spatial and design conflicts through multidisciplinary review. Clash detection provides automated geometric conflict testing on the federated model after coordination review.
Let's plan the BIM scope, information requirements, delivery standards and coordination process in line with your project lifecycle.