BIM Execution Plan for Data Centers: What It Must Actually Cover

This is a delivery-method resource, not project-specific design. Electrical protection, cable sizing, cooling capacity, fire strategy and structural loads require the appointed designers and the applicable codes. Technical review of this cluster by a named senior BIM/MEP lead is pending; do not treat it as sealed guidance.

The BIM Execution Plan is the working contract for information production on a project. It answers how the appointed parties will meet the information requirements — who does what, when, in which tools, under which rules, with what checks. On a data-centre programme, the BEP must also handle congestion, prefabrication interfaces and a coordination cadence that matches the speed of MEP decisions.

Why a BEP exists

An appointing party (client, developer, main contractor) sets information requirements — what information is needed, why, at what exchanges. Appointed parties (designers, specialists, fabricators, BIM service providers) respond with a plan for meeting those requirements. That plan is the BEP. Without it, five disciplines arrive with five naming conventions, three coordinate origins and no agreement on what coordinated means.

ISO 19650 context — honest summary

ISO 19650-1 establishes concepts and principles for information management using BIM. ISO 19650-2 covers delivery-phase management — appointing parties, information requirements, common data environment, information delivery planning, BEP and related exchanges. The UK BIM Framework guidance interprets these for UK practice but does not invent additional mandatory clauses.

• Organizational / asset / project information requirements (OIR, AIR, PIR) — why information is needed.
• Exchange information requirements (EIR) — what is delivered at each exchange.
• BEP — how the delivery team will produce and manage that information.
• CDE — the agreed container, state model and access rules for shared information.
• Information delivery planning (MIDP/TIDP in UK language) — who delivers what, by when.

What data-centre projects demand from a BEP

Generic BEP templates written for office fit-outs rarely survive contact with a data centre. The congestion is higher, the prefabrication content is greater, the coordination cadence is faster, and the handover data requirements (if any) are more specific. A DC BEP must address at least the following.

Anatomy of a useful BEP

Roles and contacts

Named individuals, not just company names. BIM manager, discipline leads (electrical, mechanical, structural, architectural, fire, controls), federation coordinator, CDE administrator. If an external team provides modelling or coordination capacity, their point of contact and reporting line belong here.

Model structure and coordinates

One origin strategy, documented. A single defining coordinate file — typically a site or building host — from which other disciplines acquire shared coordinates. File-split diagram: which models, which links, which worksets. Units (metric/imperial) and tolerance assumptions. Model-size limits if the hardware constrains federation.

CDE and states

The platform (ACC, ProjectWise, SharePoint, client bespoke). The state model (WIP / Shared / Published / Archived or equivalent). What triggers promotion. Who may publish. How superseded files are handled.

Information exchanges

Exchange schedule tied to project programme. Format requirements — native, IFC version, COBie if specified. Acceptance checks — geometry, data, naming — and who signs off.

Coordination process

Federation cadence, test matrix (hard clashes, clearance clashes, independence tests for redundant routes), issue register location, status definitions (New / Active / Resolved / Closed), escalation path for disputes. This section is the BEP centre of gravity on a congested DC.

QA and governance

A BEP without QA gates is an intent document without enforcement. Define what happens before Shared (internal discipline check) and before Published (cross-discipline or client check). Define who may reject, on what grounds, and how rejection is recorded.

Common BEP failures

FAQ

Is a BEP legally binding?

It depends on the appointment. In many contracts, the BEP is referenced by the professional-services or construction agreement and becomes a contractual deliverable. In others, it is a working document that sits alongside the contract. Check your appointment.

Who writes the BEP?

Typically the lead appointed party (designer or contractor BIM manager), responding to the appointing party information requirements. If multiple firms are appointed separately, a single BEP may be federated from multiple pre-appointment BEPs or a master BEP may be authored collaboratively.

Should the BEP specify LOD for every element?

ISO 19650 language has moved toward level of information need — specify the geometry and data actually required for each exchange and use (coordinate, fabricate, operate). Blanket LOD numbers often over-specify or under-specify.

How does prefabrication affect the BEP?

Prefabricated modules and skids enter the model before site installation. The BEP should state when vendor models are required, what coordinate and naming rules they must follow, who coordinates against them, and who owns the interface.