BIM Execution Plan: The Document That Defines How a Project Team Actually Uses BIM

Building Information Modeling has become routine on major construction projects. But 'using BIM' means different things to different teams. One contractor's BIM means comprehensive coordination across all trades with laser-scanned existing conditions. Another contractor's BIM means the architect delivered a model that sat unused. The difference is often whether a BIM Execution Plan (BEP or BxP) defined how BIM would actually be used.

BEPs align project teams on BIM purpose, scope, standards, and deliverables. Without a BEP, BIM expectations diverge and coordination fails. With a thorough BEP, teams execute consistently. This post covers BEP contents and development.

BEP Purpose

BEP defines BIM use for the project:

BEP is reference document team consults throughout project. Without it, team members guess at expectations and often guess differently. With it, expectations are documented and disagreements surface early.

BIM Goals

BIM goals drive specific uses:

Not every project uses BIM for every purpose. Selecting specific goals focuses effort. A project using BIM only for design coordination needs different BEP contents than a project using BIM through facility management handoff.

Level of Development (LOD)

LOD specifies model element detail:

LOD clarifies what model elements should include. A structural element at LOD 300 has specific size and location but not detailed connections. At LOD 400, it has fabrication-level detail. BEP specifies which elements reach which LOD at which project phase.

Software and Standards

Software specifications enable collaboration:

Standards enable teams using different software to exchange models. Without them, time is lost converting formats and resolving coordinate mismatches. With them, files open correctly and align.

Coordination Process

Coordination process defines how conflicts resolve:

Coordination process turns BIM from static representation into collaborative tool. Without process, models exist but conflicts persist. With process, models drive conflict identification and resolution before construction.

Roles and Responsibilities

Roles must be assigned:

Roles prevent gaps and overlaps. When everyone assumes someone else federates the model, no one does. When multiple teams think they own clash detection, conflicting efforts result. Explicit assignment resolves this.

Deliverables

BEP specifies BIM deliverables:

Deliverables clarify what teams owe. Without specified deliverables, the question of whether a team's BIM obligation is met becomes subjective. With deliverables, obligation is defined.

BEP Development Timing

BEP develops across project:

BEP isn't fixed at project start. It develops as more information becomes available and team composition finalizes. Regular updates keep BEP aligned with actual project execution.

Contractor Participation

Contractor role in BEP varies:

Contractor's BEP role varies by delivery method. On design-build and CMAR, contractor typically shapes BEP substantially. On design-bid-build, contractor operates within owner-designer framework.

Bottom Line

BIM Execution Plan defines how BIM is used on a specific project — goals, software, LOD, coordination process, deliverables, and responsibilities. Projects with well-developed BEPs get BIM value; projects without often waste BIM investment. LOD framework clarifies model detail at each project phase. Coordination process drives BIM's highest value — clash detection and resolution before construction. Roles prevent gaps. Deliverables clarify obligations. Contractor participation depends on delivery method. BEP is reference document team uses throughout project. Investment in BEP development pays back many times over through coordinated execution and reduced field conflicts. Projects using BIM without BEP are effectively hoping BIM works; projects with BEP are making it work.