BIMVERSE360

BIMVERSE360 / PRACTICAL GUIDE

BIM Execution Plans,
made understandable.

Learn what a BEP does, how it supports ISO 19650 information management, and what your project team should agree before information production begins.

01

What is a BIM Execution Plan?

A BIM Execution Plan describes the delivery team’s approach to managing information for an appointment. It turns information requirements into agreed working methods: who is responsible, what information is needed, when it is exchanged, how it is checked and where it is shared.

A BEP is not just a template.

It should be specific to the appointment, proportionate to the project, and usable by the people producing and reviewing information.

02

Pre-appointment and delivery-team BEP

BEFORE APPOINTMENT

Show the proposed approach

The prospective lead appointed party explains how the delivery team intends to meet the appointing party’s information requirements. This provides evidence that the proposed team can manage information appropriately.

AFTER APPOINTMENT

Confirm the working method

The plan is reviewed, agreed and maintained as a practical delivery resource. Changes in teams, methods, responsibilities or exchange arrangements should be reflected through controlled revision.

03

What should a useful BEP contain?

01

Project and appointment context

Purpose, scope, milestones, parties and information requirements.

02

Roles and responsibilities

Information management functions, task-team ownership and approval responsibilities.

03

Information standards

Agreed naming, classification, status, revision and metadata conventions.

04

Production methods

Authoring, coordination, federation, checking and review procedures.

05

CDE workflow

How information moves through work in progress, shared, published and archived states.

06

Delivery planning

Information containers, authors, dependencies and planned exchange dates.

07

Technology and exchange

Software, versions, formats, interoperability and model federation approach.

08

Quality and acceptance

Checks, approvals, authorization, acceptance criteria and issue resolution.

04

How it fits the ISO 19650 process

ISO 19650 treats information management as a managed business process, not simply a modelling task. The BEP sits alongside capability and capacity assessment, mobilization planning, risk management and information delivery planning.

  1. RequirementsThe appointing party establishes why information is needed and defines exchange information requirements and acceptance criteria.
  2. ResponseThe prospective delivery team proposes how it will meet those requirements, including its pre-appointment BEP.
  3. AppointmentThe approach is confirmed with responsibilities, standards, methods, procedures and delivery plans.
  4. MobilizationPeople, technology, testing and shared resources are prepared before full information production.
  5. Collaborative productionTask teams produce, check, review and share information through the agreed common data environment workflow.
  6. Exchange and acceptanceInformation is authorized, submitted and reviewed against the agreed requirements and level of information need.

05

TIDP, MIDP and the BEP

The BEP explains the management approach. Delivery plans turn that approach into scheduled information containers and responsibilities.

TIDP

Task Information Delivery Plan

Prepared for a task team. It identifies the information containers to be delivered, responsible authors and planned dates, including dependencies where relevant.

MIDP

Master Information Delivery Plan

Brings the task-team plans together into the delivery team’s coordinated programme of information exchanges.

06

Eight questions before approval

  • Does the BEP respond directly to the appointment’s information requirements?
  • Are information management responsibilities clear and assigned?
  • Are naming, classification, status and revision rules agreed?
  • Are model federation and information container breakdown explained?
  • Are production, checking, review and approval methods practical?
  • Is the common data environment workflow understood by every task team?
  • Do delivery plans identify containers, owners, dependencies and dates?
  • Is the BEP controlled, accessible and maintained when the project changes?

Passing this checklist does not by itself prove contractual or ISO compliance. The project’s appointment documents, applicable national annexes and professional review remain decisive.

07

Common questions

Is a BEP required for every BIM project?

Where ISO 19650-2 is adopted for an appointment, the information management process includes a BIM execution plan response. Its depth should remain proportionate to the scale and complexity of the appointment.

Who prepares the BEP?

The prospective lead appointed party develops the pre-appointment BEP on behalf of the proposed delivery team. Following appointment, it is confirmed with the relevant parties and used by the delivery team.

Can we reuse a company template?

Yes, as a controlled starting point. It still needs to be tailored to the appointing party’s requirements, project risks, delivery teams, exchange strategy and actual working methods.

Is the BEP the same as the MIDP?

No. The BEP describes the management approach; the MIDP coordinates the planned delivery of information containers across task teams.

REFERENCE

Standards and guidance

This guide is an original educational summary, informed by the current published ISO 19650-2:2018 and the UK BIM Framework project-delivery guidance. ISO is developing a second edition; draft terminology and processes may change before publication.

PUT THE GUIDE INTO PRACTICE

Start with a structured BEP workspace.

Work through the project information, responsibilities, delivery planning and appendices in one guided environment.