Getting BIM right isn’t just about the software—it’s about matching the type of model to the phase of the project and the information needs of your stakeholders. Use the wrong model at the wrong time, and you’ll either overspend on detail you don’t need or under-deliver information that downstream teams rely on.
In this article, we’ll map three core model types—Design BIM Model, Fabrication BIM Model, and Digital Twin (As-Built)—to the typical phases of a construction project: Design, Analysis, Construction Documents, Bidding, Construction, and Management (post-occupancy). We’ll go through what each model is for, what it should contain, who uses it, and how it can be aligned to LOD/LOIN so you can deliver the right value at the right time.
The core ideas behind each BIM model version:
Design Model
Supports concept-to-bidding and coordination.
Fabrication Model
Supports constructability, sequencing, shop-level detail, and cost/time control.
Digital Twin (As-Built)
Supports operations with accurate spatial structure and asset data aligned to the employer’s and FM’s requirements
Project phases in general
We’ll use a general sequence most teams recognize:
- Design (concept/schematic to developed design)
- Analysis (performance, compliance, options)
- Construction Documents (coordinated design docs for permitting & procurement)
- Bidding (pricing, contractor input, clarifications)
- Construction (fabrication, installation, commissioning)
- Management (post-handover operations and maintenance)
Different jurisdictions can use different names or there can be more phases in between, but the idea is consistent: intent → documentation → procurement → build → operate.
The Design BIM Model
A Design BIM Model enables the overall design and analysis of a project and supports the stakeholder group from Design through Bidding. It defines and specifies the project at a level where decisions can be made confidently, cost can be estimated, and risk can be coordinated away early.
You’ll use this model to:
- Develop the architecture/engineering intent across all disciplines.
- Run analyses (energy, daylight, structural, MEP sizing, code checks).
- Coordinate across trades and detect clashes at a system level.
- Prepare Construction Documents and support Bidding with consistent quantities and scope clarity.
- Capture information required by the Employer’s Information Requirements (EIR) and the BIM Execution Plan (BEP).
The phases that this model is used on are: Design, Analysis, Construction Documents, Bidding.
It is the project’s “single source of design truth” up to procurement.
The usual stakeholders are the lead designer(s), such as the Architect and Engineers. Also BIM coordinators, cost consultants, Owner representatives, and sometimes the General Contractor offering pre-construction services.
What it should contain
- Geometry: Accurate enough to represent design intent and build a coordinated set of documents.
- Information: Parameters fulfilling the EIR—classification codes, system assignments, design specifications, key performance criteria, and quantities for cost plans.
- Coordination structure: A federated or linked setup covering architecture, structure, MEP, and site/civil as needed.
- Issue tracking & approvals: Decisions and changes are logged; clashes are resolved at system level.
Workflow overview
Responsible: Design authors (arch/struct/MEP), design BIM coordinator
Accountable: Lead designer/Principal-in-charge, Owner’s rep
Consulted: Cost consultant, GC (precon), key trades (for buildability input)
Informed: Owner, permitting authorities
The Fabrication BIM Model
A Fabrication BIM Model is used to control the construction sequence, plan phased work, and provide shop-level detail for manufacturing and installation. Its focus is constructability, cost (labor and materials by phase), time, and high-detail clash detection.
The Fabrication Model derives from and respects the approved design intent of the Design BIM Model, but it resolves constructability details and installation sequences that are outside design scope.
When the project is finished, this Fabrication Model is a key source to validate the As-Built/Digital Twin version of the Design BIM Model.
The phase that this model is used on: Construction, with inputs sometimes starting late in Bidding for early packages.
The usual stakeholders are: Trade contractors and fabricators, the General Contractor, BIM/VDC managers, project coordinators, sometimes the architect for intent confirmation.
What it should contain
- Work packaging: Breakdowns by zones, levels, rooms, and sequences aligned with the schedule (4D) and cost codes (5D).
- Installation logic: Access, temporary works, lifts, hoists, logistics paths, scaffolding, and tie-ins.
- Coordination at high detail: Clash detection down to supports, sleeves, and penetrations; “last responsible moment” checks before issuing fabrication.
- Change control: RFI references, approved submittals, and shop drawing status.
Workflow overview
Responsible: Trade contractors/fabricators, VDC manager
Accountable: General contractor / construction manager
Consulted: Architect/engineer (for intent compliance), suppliers
Informed: Owner’s rep, scheduler, cost control
What to work on
- Labor & material by phase: Granular quantities aligned to work packages and schedule tasks.
- 4D/5D simulation: Visualize the sequence, verify logistics, and forecast cash flow.
- QA/QC: Track tolerances and sign-offs. Reduce rework by installing virtually before physically.
The Digital Twin
A Digital Twin—previously referred to as the As-Built – supports operations and maintenance after handover. It contains the information used to monitor, maintain, and update building data according to the Employer’s Information Requirements and the facility manager’s needs.
The digital twin should be lean and purposeful. Overloading it with design-only parameters increases the upkeep burden without adding O&M value. It’s better to include the right fields, correctly labeled, than to inherit every parameter from the design or fabrication models.
Crucially, it does not need to mirror all the design data. It must be reliable, maintainable, and relevant to operations.
The phase that this model is used on: Management/Operations (post-construction), plus commissioning and handover.
What it should contain
- Spatial hierarchy: Sites → buildings → levels → zones → rooms (spaces). This is the backbone for locating and managing assets.
- Key assets and systems: Equipment with IDs, categories, locations, and system assignments.
- Operations metadata: Manufacturer, model, serial, expected life, maintenance intervals, warranty dates, responsible contacts, replacement cost, and critical spare parts.
- Connections & dependencies: What feeds what; how alarms propagate; shut-off points; sensor mapping where applicable.
- Change/update workflows: A practical method for capturing updates after moves/adds/changes so the twin stays trustworthy.
Workflow overview
Responsible: GC or Architect during handover; FM integrator for CMMS/CAFM mapping
Accountable: Owner/Facility Manager
Consulted: Designers (for intent), commissioning agent
Informed: O&M vendors, energy team, occupants (where relevant)
Additional information:
Have a look at the ISO Standard
The Industrial Digital Twin Association
The Building Digital Twin Association
Tips for workflows and handoffs
Start with the EIR (and make it specific)
The Employer’s Information Requirements define what data is needed, when, and in what format. This governs the entire chain. If the EIR is vague, expect friction later. Clarify:
- Spatial structure and naming (levels, zones, rooms).
- Asset classes to be handed over and minimum fields (e.g., “Pump: ID, location, system, manufacturer, model, service interval, warranty end date, responsible vendor”).
- Exchange formats (native, openBIM, COBie, PDFs) and approval points.
- Update responsibilities post-handover.
Build a BEP that maps model types to phases
Your BIM Execution Plan should state:
- Which model type is authoritative for each decision (design intent vs. fabrication detail vs. O&M).
- LOIN by discipline and milestone.
- Coordination frequency and issue management tools.
- File structure, naming standards, and shared parameters.
- Handover schedule and acceptance criteria for the twin.
Validate at every gate
Design → Bidding: System-level clashes closed; quantities stable; scope packages clear.
Bidding → Construction: Approved submittals align with design; shop model creation plan agreed.
Construction → Handover: Installed equals recorded; asset fields complete and verified; spatial IDs consistent.
Keep the twin maintainable
- Provide a data dictionary and update SOPs for FM teams.
- Restrict fields to what will actually be maintained.
- Integrate with CMMS/CAFM rather than making the model a data silo.
- Establish a simple change log for moves/adds/changes.
Some FAQs
Is the Fabrication Model just a “more detailed” Design Model?
Not exactly. It extends design intent into constructability, adding prefabrication and installation detail that design doesn’t carry. It is purpose-built for building, not for documenting design intent.
Should the Digital Twin include all the fabrication detail?
No. The twin should be fit for operations. Carry the assets and fields FM needs, not every nut and bolt. Over-detailed twins are harder to maintain.
What if we’re using LOD instead of LOIN?
Not good—LOIN is about defining the exact information need by purpose and time. The general mapping above (Design ≈ LOD100–300/350, Fabrication ≈ LOD400, Digital Twin ≈ LOD500) remains a useful shorthand, but your EIR/LOIN should be the authority.
Who owns updates after handover?
Define this in the EIR/BEP. Typically the Owner owns the model, and the FM manages the twin with a process to update data after maintenance, replacements, or tenant improvements.
