On any serious Australian commercial project, the “BIM model” you hand to the builder is never a single file. It’s a federated model — a live stitch-up of separate architectural, structural, mechanical, electrical, hydraulic, fire and civil models, each maintained by a different author but consumed together as one coordinated whole. Getting that federation right, and progressing it cleanly from an early LOD 100 massing study through to an LOD 500 as-built for facility management, is the quiet discipline that separates a buildable BIM deliverable from a model-shaped pile of problems. This guide walks through how we run a federated MEP BIM workflow in Australia, stage by stage.
What is a federated BIM model?
A federated BIM model is a composite view of multiple discipline models linked together so they can be coordinated, clash-checked and reviewed as a single virtual building. Critically, the discipline models stay separate at the file level — each author keeps ownership of their own geometry and data — but the federation layer lets coordinators, builders and clients see everyone’s work in one place.
Discipline models vs the federated whole
Each discipline authors inside its own environment. The architect models the building envelope, floors and partitions in Revit or ArchiCAD. The structural engineer models slabs, columns, beams and footings. MEP trades model ducts, pipes, cable trays, fittings, plant and services inside their own Revit MEP files. Civil consultants might be in Civil 3D, and specialist trades (facade, vertical transport, fire engineering) may deliver IFC only. None of these files “know” about each other until federation happens.
Federation is where a coordinator appends every discipline model — in whatever native or IFC format it comes in — into a single container. That container might be a Navisworks NWF, a Revit host model with links, a BIM 360 / ACC federated workspace, or a platform like Solibri. The federated model is then the single version of truth for clash detection, progress review, quantity checks and construction sequencing.
Host-vs-linked model strategy in Revit and Navisworks
Two federation patterns dominate on Australian projects. The first is the all-Revit linked model approach: a “coordination host” Revit file links every discipline’s RVT into one place, shared via Worksharing or BIM 360. This is fast to set up, preserves parametric data, and suits projects where every consultant is already on Revit. The second is the Navisworks federation approach, where an NWF appends RVT, IFC, DWG and NWC files into one lightweight container. Navisworks scales better for big files and heterogeneous consultants, which is why most mid-to-large commercial jobs end up running it alongside Revit. In practice, the two patterns coexist on the same project — Revit for in-discipline authoring and self-check, Navisworks for the federated coordination record.
LOD progression stages in an Australian MEP workflow
Level of Development (LOD) is the language we use to describe how much is actually committed in a model at any stage. The AIA/BIMForum LOD spec (LOD 100 – LOD 500) is the most common reference on Australian projects, and for a deeper breakdown you can read our companion guide on LOD 100 to LOD 500 for MEP. Here’s how those stages actually play out on a federated MEP workflow.
LOD 100 — concept / massing
At LOD 100 the MEP model barely exists as geometry. Plant rooms are represented as volumes, vertical service shafts are sketched as simple risers, and load estimates live in spreadsheets beside the model. The federated model at this stage is really an architectural mass plus a few placeholder MEP zones — enough to test that the building’s service cores have been reserved and that no-one has designed a 2 m deep transfer beam through the main riser.
LOD 200 — design development
At LOD 200 the MEP designer starts laying in main duct runs, chilled-water and heating-hot-water loops, switchboard locations, cable tray spines and hydraulic stack locations. Sizes are approximate — often generic or placeholder families — but routing is close to final. This is the stage where the federated model first earns its keep, because structural interferences with primary MEP routes must be resolved before construction documentation starts.
LOD 300 — coordinated documentation (IFC-ready)
LOD 300 is where most construction drawings are issued from. Every major component is modelled with correct geometry, type, size and connection, and the federated model is clash-coordinated to an agreed tolerance. At this stage the model is IFC-ready — consultants and trades who aren’t on Revit can receive it as an IFC 2×3 or IFC 4 export without losing coordination fidelity. This is the delivery milestone for a typical MEP BIM drafting service on Australian commercial projects.
LOD 400 — fabrication / shop-ready
At LOD 400 the MEP model becomes fabrication-aware. Duct lengths match sheet-metal shop limits, pipe spools carry weld and flange data, hanger and support families are real manufacturer parts, and every component carries enough information to order, cut and install. This is also where clash detection tightens up — tolerance drops to roughly 25 mm and the clash detection cadence typically moves from weekly to twice-weekly as shop drawings are issued.
LOD 500 — as-built / FM hand-off
LOD 500 is the post-construction state. The model is updated to reflect what was actually installed — verified against site surveys or a scan-to-BIM point cloud — and enriched with asset data, serial numbers, commissioning records and warranty information. The federation at this point becomes a handover deliverable for facility management, not a design-coordination tool.
Weekly federation and clash cycles
The federation itself is a rhythm, not a one-off event. On a typical Australian commercial project, discipline authors freeze and issue their work-in-progress models on an agreed day (Thursday is common), the coordinator federates Friday morning, runs the Clash Detective test suite, exports reports and BCF, and issues the federated model and clash list back to the disciplines on Friday afternoon. The disciplines then have the following week to resolve their assigned clashes before the next cycle.
As the project moves from LOD 300 toward LOD 400, that weekly cadence usually tightens to twice-weekly. In the final weeks before a critical shop-drawing milestone, daily federation is normal. A good coordinator will track open-clash counts week on week — it’s one of the most honest health indicators a BIM manager has.
BIM execution plan (BEP) checkpoints
None of this works without a written BIM Execution Plan. The BEP defines who authors what, which software versions are used, the shared coordinate system, model-split strategy, naming conventions, level of detail at each stage, the federation cadence, clash tolerance, BCF workflow and the LOD deliverable at each milestone. It is signed by every discipline before modelling starts and is revisited at every major stage gate.
The BEP is also where the federation deliverables are nailed down: which party owns the Navisworks NWF, who holds the master IFC, what file formats are acceptable for incoming consultant data, and when the model ownership hands over from designers to the contractor. For more background on how the BEP fits into the wider process, see our pillar guide on BIM in MEP construction in Australia.
Hand-off to facility management
The last federation is the one that outlives the build. At practical completion, the federated model is reconciled against actual site conditions, asset data is attached to every major plant item, and the whole package is exported to whatever asset-management system the client runs (COBie export for BIM 360 Ops, direct integration with Archibus, or a spreadsheet-plus-links hand-over for smaller clients). This LOD 500 federation is what gives the building owner a decade of return on the BIM investment — they can find a failed VAV box, see its original shop-drawing lineage, trace its warranty and order a replacement without opening a single paper file.
How Meter Built delivers federated MEP models
We run federated MEP BIM across every major Australian capital and every major vertical — commercial, healthcare, data centre, high-rise, education and industrial. Our standard workflow is Revit-native authoring, Navisworks federation, BCF issue tracking and a disciplined LOD progression tied to the project BEP. If you need a federated MEP BIM model delivered from LOD 100 concept through to an LOD 500 hand-over, talk to us about our MEP BIM drafting services — we’ll tailor the federation cadence and LOD milestones to your program and your consultant mix.