One shared vocabulary for how detailed a model needs to be
Standard modeling capability: up to LOD 400, across every discipline.
| LOD | Milestone | Description |
|---|---|---|
| 200 | Approximate Geometry | Generalized systems and assemblies with approximate quantity, size, shape, location, and orientation. Enough to test the big moves and support early coordination. |
| 300 | Precise Geometry | Specific assemblies with accurate quantity, size, shape, location, and orientation. Suitable for construction documentation. |
| 350 | Coordination-Ready | LOD 300 plus the interfaces between systems: connections, supports, and clearances. This is the level clash detection needs in order to mean anything, and the level we coordinate the federated model at. |
| 400 | Fabrication-Ready | Detail sufficient for fabrication and installation: shop and fabrication drawings, spool sheets, installation details. Our standard modeling capability across all six core fields. |
STRATA delivers up to LOD 400 across all six core fields. There is no table of exceptions on this page because there are none - architectural work carries the same ceiling as MEPF, and there is no upcharge tier above it.
Coordination across the federated model is performed at LOD 350, the level at which the interfaces between systems are defined and clash detection means something. The discipline models being coordinated still carry to LOD 400 where fabrication requires it.
Settled before modeling, not during coordination
Naming conventions
Files, views, sheets, and families are named to your project's convention, confirmed in writing at specification alignment before modeling starts. Where a project has no convention, we propose one and document it, rather than adopting an internal standard silently and handing back a model nobody else can navigate.
Coordinate system
One shared coordinate system and project base point across every discipline model, agreed at kickoff and documented at handoff. This is the single decision that determines whether the models federate later, which is why it is settled before the first element is placed rather than discovered during coordination.
File handoff protocol
Deliverables are issued through your project platform - BIM 360/ACC, or whatever the project already runs on - with a change log describing what moved since the previous issue. Versions are additive: a handoff never overwrites the set it supersedes.
Every deliverable passes through the same eight stages.
STRATA models design intent supplied by your architect or engineer of record. We are not the architect or engineer of record on your project, and we do not stamp or seal drawings.
Ready to coordinate your next project?
Send your disciplines, LOD target, and project location. We come back with scope and next steps within 24 business hours.