We required model element reuse across DD and IFC. MEP teams couldn’t duplicate or redraw fixtures — had to maintain object ID through every model version. Painful early, but meant perfect data inheritance in FM.

In our urban mixed-use project, we split models by public vs. private domain — not by trade. Shared spaces (lobbies, lifts) were modeled independently, which helped when swapping out facade strategies at 75% DD without crashing the whole file.

We use model slices based on load path rather than floor. Each load-bearing element is grouped into gravity or lateral frames — makes it easier to verify continuity. Let MEP split by zone if they must, but structure should be structural logic–driven.

We built a shared model segmentation diagram early — think of it like a site logistics plan but for Revit logic. It showed each consultant where their model started and ended, and defined object ownership rules. Huge coordination time-saver.

FM can’t use your model if zones don’t align with asset lifecycle logic. We now require one Revit file for maintainable components per floor. It bloats the front end, but asset tags, COBie fields, and QR codes all align perfectly after handover.

Be careful of the BIM performance cliff. We once had a model split by floor AND trade — created hundreds of links and crashed our coordination sessions. Limit to one hierarchy: spatial OR discipline, never both unless scripted.

Specs team needs to see the same object breakdown as FM team. We wrote model breakdown into our project execution plan: any element that appears in spec, O&M, or COBie needed to exist as a discreet Revit object.

We switched to model by construction package — not by trade. So slab, core, envelope, and MEP shafts were each in their own file. It made phasing easier and forced consultants to think in terms of deliverables, not software habits.

We once required consultants to tag every model object with a 'discipline-source-LOD' prefix. That gave us a federated model with traceability, even when consultants used wildly different model splits. We also demanded shared coordinate systems and grid anchoring.

We use a rule-based file segmentation strategy: by system type and construction sequence. For example, MEP gets one model per vertical zone, structure by slab level, and arch by building wing. Then we federate in Navisworks using standard container naming logic that makes every clash traceable.