01
Discipline models
Native (.rvt / .ifc) per discipline, properly LOD-tagged, federation-ready.
01 · MODELING BIM Modeling.
We author and document architectural, structural, MEP, landscape, and interiors models — tagged to the right LOD, federated cleanly, and handed off in formats your downstream teams can actually consume.
Typical engagement
3–12 mo
Disciplines
A · S · MEP · L · INT
LOD range
100 → 400
Standards
ISO 19650
Section 01 · The problem
Why "just give us the Revit file" almost never works.
A model that opens cleanly in the modeler's machine and a model that survives federation, contractor handoff, and as-built revisions are not the same model. The gap is mostly discipline — naming conventions, LOD consistency, parameter hygiene, sheet management, shared-coordinate alignment — and the cost of the gap is paid in site coordination meetings six months later.
We author models with the downstream user in mind: the coordinator who needs to federate it, the contractor who needs to extract quantities from it, and the facility manager who'll maintain the building from it.
A model is a tool, not a deliverable. It earns its keep at federation — not in the modeler's machine.
Section 02 · Our approach
Five steps from kick-off to handoff.
Establish the BIM execution plan
LOD by element, sheet conventions, file naming, shared coordinates, federation cadence — all written down before the first wall goes in.
Set up the template
Project template, shared parameters, view templates, and family library tuned to the project — not the modeler's defaults.
Author by discipline
Architectural, structural, MEP authored in parallel with shared-coordinate sync. Daily commits, weekly federation runs.
Document to sheet set
Plans, sections, elevations, schedules — drawn in-model, annotated to standard, version-controlled.
Hand off to coordination
Federation export (IFC + native), data dictionary, COBie if required. Downstream team can pick up and run.
Each step has a published exit criterion. Nothing moves forward until the criterion is met — which sounds like overhead, but in practice eliminates 80% of the coordination thrash that happens when modelers are graded on what's visible in their files rather than what survives federation.
Section 03 · Deliverables
What you receive.
02
Sheet set
Plans, sections, elevations, schedules — drawn in-model, exported PDF + DWG.
03
Data dictionary
Shared parameters, naming conventions, classification matrix.
04
Quantity take-off
Element counts, areas, volumes — exported to CSV / contractor format.
05
COBie data drop
When required: equipment & asset data structured for FM handoff.
06
Issue log & sign-off
Documented review cycles, sign-off per phase, version archive.
Section 04 · Tools & standards
What we author in.
Our default stack — adjusted per project to match the client's coordination environment.
Revit 2025
ArchiCAD 28
Civil 3D 2025
Rhino + Grasshopper
Dynamo
Standards we author to — happy to apply your in-house standard instead.
ISO 19650-1/2
BS 1192
PAS 1192-3
COBie 2.4
IFC 4
Section 05 · Recent work
A modeling engagement in practice.
Case study · 04 of 6
Renaatus Irumathi
HulhumaléMaldivesMixed-use2025
Eleven storeys, three disciplines, single coordination model. Authored A·S·MEP in parallel with weekly federation runs from week two. Final handoff: native models, IFC export, full sheet set, and data dictionary keyed to the contractor's QTO workflow.
Read the case study
Discuss this pillar
Need a model
Need a model
you can actually use?
Send us scope, timeline, and discipline mix. We respond within 24 hours.