BIM Requirements and Execution Planning

Introduction

Building Information Modelling (BIM) is not simply the production of a three-dimensional model. It is an information-management approach in which people, processes, standards and technologies are coordinated to create, exchange, validate and use reliable information throughout an asset’s life cycle. The quality of a BIM project therefore depends as much on clearly defined information requirements and responsibilities as on modelling software.

BIM requirements and execution planning translate organizational objectives into actionable information deliverables. They clarify what information is needed, why it is needed, when it is required, who produces it, how it will be checked and where it will be stored. Without this planning, project teams may produce detailed models that are inconsistent, excessive, poorly coordinated or unusable for operation.

This chapter uses the information-management logic associated with contemporary international practice, including the concepts of organizational information requirements, asset information requirements, project information requirements, exchange information requirements and BIM execution planning. Terminology varies among standards and jurisdictions, so contractual documents should always identify the governing standard and definitions.

Learning Objectives

By the end of this chapter, students should be able to:

1. distinguish organizational, asset, project and exchange information requirements;
2. relate information requirements to decisions across the asset life cycle;
3. develop the principal contents of a BIM execution plan;
4. prepare responsibility matrices and model production methods;
5. explain information delivery milestones, approvals and quality assurance;
6. evaluate practical, contractual, ethical and technological issues in BIM planning.

1. Information Requirements as a Management System

An information requirement is a statement of information that must be delivered to support a decision, activity or obligation. It should not be written merely as a list of model elements. A robust requirement identifies the purpose of the information, its required content, acceptable quality, format, timing, author, recipient and approval process.

For example, the statement “provide an HVAC model” is incomplete. A useful requirement might specify that the mechanical designer must provide spatially coordinated ducts and equipment at an agreed level of geometry, with equipment identifiers, capacities, maintainability zones and manufacturer data, in a native authoring format and an open exchange format, by the design coordination milestone.

Information requirements should be:

• necessary: information is requested because it supports a decision or process;
• proportionate: the effort and detail are appropriate to the project’s risks and value;
• unambiguous: terms, units, classifications and acceptance criteria are defined;
• verifiable: the recipient can check whether the requirement has been met;
• traceable: each requirement can be connected to an owner, deliverable and decision;
• secure: access, confidentiality and permitted use are controlled.

The information hierarchy

Requirements are commonly arranged from organizational objectives to individual exchanges:

These levels are related but not interchangeable. OIR describes strategic need; AIR focuses on asset operation; PIR addresses project decisions; EIR defines a specific information exchange; and TIDP/MIDP turn requirements into delivery commitments.

2. Developing Organizational, Asset and Project Requirements

Organizational information requirements

OIR are derived from the organization’s strategy, governance obligations and business processes. An organization may require information to support capital investment decisions, carbon reporting, statutory compliance, portfolio benchmarking, maintenance planning or emergency response.

A useful method is to identify strategic objectives and then ask what information is required to measure or achieve each objective. For example:

The organization should avoid requesting every possible data field. Excessive requirements increase procurement cost, reduce data quality and encourage teams to enter meaningless placeholder values.

Asset information requirements

AIR describe the information needed to manage an asset after handover and during operation, maintenance, refurbishment and eventual disposal. Their content depends on the asset type and the owner’s operating model. A hospital, railway, school and commercial office will not need identical asset information.

AIR commonly address:

• asset classification and unique identification;
• location, system and spatial relationships;
• technical characteristics and performance ratings;
• manufacturer, model, serial number and supplier;
• installation, commissioning and inspection records;
• warranty, replacement and expected service-life information;
• safety, statutory and environmental information;
• preventive maintenance requirements and task frequencies;
• links to manuals, certificates, drawings and photographs;
• cybersecurity, access and information-retention requirements.

The AIR should be developed with facilities managers and end users, not imposed solely by the design team. A facilities manager may value a structured equipment register and maintainability zones more than highly detailed architectural geometry.

Project information requirements

PIR specify information required to plan, procure, design, construct or authorize a project. They should reflect project decisions and risks. Typical PIR topics include site constraints, planning submissions, design options, cost planning, programme, constructability, safety, sustainability, logistics and handover.

A project information requirement should identify:

1. the decision or process being supported;
2. the information needed to support it;
3. the required level of information need;
4. the responsible author and reviewer;
5. the delivery date or milestone;
6. the format, naming and classification rules;
7. validation and acceptance criteria.

Level of information need

A common planning error is to use one-dimensional labels such as “Level of Development” for every information decision. Information need is multidimensional. It may include:

• geometrical information: size, shape, location and spatial relationships;
• alphanumerical information: properties, identifiers, classifications and performance data;
• documentation: specifications, certificates, photographs, manuals and approvals.

The required detail should be linked to the purpose of the exchange. A concept model may need approximate massing and area data, while construction coordination may require accurately located penetrations and access zones. A facility-management handover may require modest geometry but highly reliable identifiers, warranty data and maintenance documents.

3. Exchange Information Requirements

An EIR defines the information to be exchanged at a particular point in the project. It is both a technical and contractual instrument. A well-written EIR prevents disputes by establishing what is to be delivered and how compliance will be assessed.

An EIR normally covers:

• purpose and intended use of the information;
• information containers and their naming convention;
• required model views, drawings, schedules and documents;
• geometry, data and documentation requirements;
• classification systems and units of measurement;
• file formats, software versions and interoperability requirements;
• coordinate systems, survey control and geographic referencing;
• common data environment workflow and status codes;
• security, access permissions and information protocols;
• delivery dates, review periods and approval gates;
• model checking, issue management and acceptance criteria.

A requirement should specify an open exchange format where long-term access or multi-platform coordination is important. However, open formats do not automatically guarantee perfect interoperability. Exchange testing, agreed mappings and practical model review remain necessary.

Information containers and status

An information container is a named, persistent set of information, such as a model, drawing, schedule, report or document. Containers should have controlled metadata, including author, revision, status, classification, date and suitability.

A common workflow separates information into states such as:

• work in progress: controlled by the originating task team;
• shared: issued for coordination or review by other teams;
• published or authorized: approved for a defined purpose;
• archived: retained as a record of superseded or completed information.

Status is not the same as quality. A file can be shared but contain unresolved issues, or published for construction while still being unsuitable for facilities management. The purpose and permitted use of each status must therefore be explicit.

4. The BIM Execution Plan

A BIM execution plan (BEP) explains how the delivery team will meet the information requirements. It is a management plan, not merely a software list. Depending on procurement arrangements, a pre-appointment BEP may explain the tenderer’s proposed approach, while a post-appointment BEP confirms the agreed methods, responsibilities and deliverables.

Typical BEP contents

A practical BEP may include:

1. project objectives and BIM uses;
2. project team structure, contacts and decision authority;
3. information-management roles and responsibilities;
4. applicable standards, protocols and contract requirements;
5. information delivery milestones and review gates;
6. model production methods and modelling standards;
7. responsibility matrix and model element table;
8. software, versions, file formats and interoperability tests;
9. coordinate systems, units, tolerances and model origin;
10. naming, classification, revision and status conventions;
11. common data environment workflow;
12. coordination, clash detection and issue-management procedures;
13. quality assurance and quality-control checks;
14. security-minded information management;
15. training, resources, assumptions, exclusions and risks;
16. handover, archive and post-occupancy information strategy.

The BEP should be treated as a controlled project document. Changes to software, deliverables, responsibilities or milestones should be reviewed for effects on cost, programme, quality and contractual liability.

BIM uses

BIM uses describe the purposes for which information is created. Examples include:

• design visualization and communication;
• multidisciplinary coordination;
• quantity measurement and cost planning;
• construction sequencing and logistics;
• temporary works and site safety planning;
• fabrication and installation planning;
• progress monitoring;
• commissioning and handover;
• operation, maintenance and asset management;
• energy, carbon and performance analysis.

A project should select BIM uses based on decisions and benefits, not fashion. Each use requires defined inputs, a method, a responsible party, an output and an acceptance measure.

5. Responsibility Matrices and Model Production Methods

Responsibility matrices

A responsibility matrix assigns information responsibilities to organizations, disciplines or individuals. It should distinguish between producing, reviewing, coordinating, approving and accepting information. A simple RACI structure can be useful:

• Responsible: performs the work;
• Accountable: owns the outcome and approves it;
• Consulted: provides relevant expertise;
• Informed: receives progress or decisions.

RACI labels must be adapted to the contract. In particular, “accountable” should not be assigned casually where the person lacks authority or resources.

A model element responsibility matrix may identify who is responsible for walls, doors, structural frames, plant, fire systems, spaces and external works at each stage. It should also identify interfaces. For example, an architect may model a door opening, a structural engineer may verify the wall interface, and a specialist supplier may provide door hardware data. Responsibility for geometry does not automatically mean responsibility for design performance.

Model production methods

The model production method describes how information is authored, coordinated, exchanged and controlled. It should address:

• model breakdown by discipline, zone, building or system;
• authoring applications and approved versions;
• file linking and referencing rules;
• shared coordinates and origin strategy;
• naming and classification;
• worksharing and permissions;
• model segmentation and file-size management;
• object libraries and content approval;
• geometry tolerances and modelling conventions;
• data schemas and parameter requirements;
• federation and coordination frequency;
• issue creation, assignment, closure and verification.

A federated model combines separately authored models for review. Federation does not mean that all disciplines must work in one file. Separate models can preserve discipline ownership, improve performance and make contractual responsibility clearer, provided interfaces and coordinates are controlled.

Model coordination

Coordination should combine automated and human review. Automated checks can identify geometric intersections, duplicate elements, missing properties, invalid classifications and naming errors. Human review is still required for access, sequencing, constructability, design intent, maintainability and safety.

Clash detection itself is not the objective. The objective is to reduce avoidable uncertainty and coordinate interfaces before work is affected. A clash matrix should establish which combinations of systems are tested, at what tolerance, with what priority and by whom.

6. Delivery Planning: TIDP and MIDP

The TIDP is prepared by each task team. It lists the information containers that team members will deliver, together with authors, reviewers, dates, formats, status and dependencies. The MIDP integrates the TIDPs into one project-level schedule.

A delivery plan should show more than a final handover date. It should include progressive exchanges aligned with decisions, such as concept approval, planning submission, spatial coordination, procurement, construction release, commissioning and handover.

Information delivery should be risk-based. High-risk interfaces, safety-critical systems and long-lead equipment may require earlier or more frequent exchanges than low-risk elements. A delivery plan should also allow review time; a file submitted on the date of a decision is not useful if reviewers have no opportunity to assess it.

7. Quality Assurance, Validation and Acceptance

Quality assurance concerns the planned system for producing reliable information. Quality control concerns checking particular deliverables. A BIM quality plan may include the following checks:

1. visual checks: inappropriate views, missing elements, graphical errors or accidental duplication;
2. geometric checks: coordinates, levels, tolerances, clearances and intersections;
3. data checks: required properties, valid values, units, identifiers and classifications;
4. document checks: references, certificates, specifications and revision consistency;
5. process checks: naming, status, approvals, permissions and audit trail;
6. fitness-for-purpose checks: whether the information supports the intended decision.

The percentage of populated fields is not, by itself, a measure of information quality. A fully populated field containing inaccurate or invented data is worse than an explicitly identified unknown. Requirements should distinguish “not applicable,” “not yet known” and “to be confirmed.”

Acceptance criteria should be measurable where possible. Examples include: all maintainable assets have unique identifiers; the model uses the approved coordinate system; required spaces are classified; unresolved high-priority coordination issues are below an agreed threshold; and documents are linked to the correct asset records.

8. Applied Case: Illustrative University Science Building

Background

A university commissions a four-storey science building. The client intends to use BIM for design coordination, construction planning and facilities management. The building contains laboratories, specialist ventilation, hazardous-material storage and complex mechanical services.

Problem

The initial procurement documents request “a coordinated BIM model at handover” but do not define asset data, exchange dates, model responsibility or acceptance criteria. During design, the architectural and mechanical teams use different origins. The contractor receives a model containing geometry but no reliable equipment identifiers, warranty information or maintenance zones.

Analysis

The client’s strategic needs are reduced energy use, safe laboratory operation and predictable maintenance. These needs generate OIR relating to performance reporting and compliance. AIR then identify required information for air-handling units, fume cupboards, valves, sensors and safety systems. PIR identify design coordination, cost, construction sequencing and commissioning decisions. EIR define the specific information to be exchanged at design review, construction release and handover.

The project team discovers that requiring highly detailed geometry for every fitting would increase modelling effort without improving operations. Instead, detailed access zones and equipment data are required for maintainable assets, while small concealed components are represented at a lower geometric detail.

Approach and solution

The client issues an information protocol and appoints an information manager. The team agrees a shared coordinate system, model breakdown, naming convention, classification and CDE workflow. A responsibility matrix assigns laboratory equipment data to specialist suppliers, spatial coordination to the relevant design disciplines and final verification to the contractor and owner’s representative.

The MIDP includes progressive exchanges: concept validation, laboratory-service coordination, construction release, commissioning records and verified asset handover. The EIR requires unique asset identifiers, manufacturer data, commissioning results, warranty dates and links to approved documents. A sample asset audit is carried out before handover rather than waiting until project completion.

Outcome

Design coordination identifies major service conflicts before construction. Facilities staff receive a structured asset register linked to relevant documents. Some minor data fields remain unknown at early stages, but their status and responsibility are recorded. The project avoids paying for unnecessary model detail while improving the reliability of information that supports operation.

Learning points

The case demonstrates that BIM value comes from connecting information to decisions. It also shows that requirements must be developed with operational users, that model detail should be proportionate to purpose, and that handover quality cannot be created at the last minute.

9. Governance, Ethics, Security and Emerging Practice

BIM planning creates governance questions concerning ownership, liability, privacy and access. Contracts should clarify who may rely on information, who is responsible for errors, how reliance changes after approval, and how information may be reused. A model author is not automatically responsible for every use made of the model by another party.

Security-minded planning is essential for critical infrastructure, public buildings and sensitive facilities. Teams should control access, avoid unnecessary disclosure of security-sensitive layouts, manage personnel permissions and define retention and destruction rules. Personal information embedded in documents or asset records should be handled according to applicable privacy law.

Ethically, practitioners should not create false precision. A model that visually implies certainty when survey information is uncertain can mislead decision-makers. Assumptions, exclusions and confidence levels should be recorded. Automated checking and artificial intelligence can assist classification, clash prioritization, data validation and issue detection, but outputs require professional review. AI-generated information may contain errors, reproduce bias or create unclear intellectual-property and accountability issues.

Contemporary BIM practice is moving toward structured information environments, open data exchange, digital twins, automated rule checking, reality capture, common classification systems and operational analytics. These developments do not remove the need for requirements planning. They increase it, because more connected information requires clearer semantics, governance, cybersecurity and responsibility.

10. Best-Practice Workflow

A disciplined workflow can be summarized as follows:

1. identify organizational objectives and asset decisions;
2. consult operators, maintainers, designers, constructors and other information users;
3. write measurable OIR, AIR and PIR;
4. convert project needs into milestone-specific EIR;
5. select BIM uses based on benefits, risks and resources;
6. define information standards, security controls and CDE processes;
7. prepare responsibility matrices and model production methods;
8. compile TIDPs and integrate them into the MIDP;
9. test software, exchange formats, coordinates and sample data early;
10. review, validate and accept information progressively;
11. record assumptions, issues, decisions and changes;
12. verify handover information against operational requirements.

The central principle is to plan information before modelling begins. Modelling is an information-production activity; it should be governed by purpose, responsibility and evidence of fitness for use.

Chapter Summary

BIM requirements and execution planning establish the link between organizational objectives and reliable project information. Organizational information requirements express strategic needs; asset information requirements support operation and maintenance; project information requirements support project decisions; and exchange information requirements define specific deliverables at agreed milestones. TIDPs and MIDPs convert these requirements into coordinated delivery commitments.

A BIM execution plan sets out BIM uses, roles, standards, model production methods, coordination procedures, quality controls, security requirements and handover arrangements. Responsibility matrices clarify who produces, reviews, coordinates and accepts information. Model production methods define model breakdown, coordinates, naming, data structures, federation and issue management. Quality assurance must assess not only geometry but also data accuracy, documentation, process compliance and fitness for purpose.

Effective planning is proportionate and user-oriented. It avoids unnecessary detail, manages uncertainty honestly, protects sensitive information and uses automation or AI under professional governance. The success of BIM is ultimately measured by whether trustworthy information enables better decisions throughout the asset life cycle.

Key Terms

Organizational information requirements (OIR): Strategic information needs of an organization.

Asset information requirements (AIR): Information needed to operate, maintain and manage an asset.

Project information requirements (PIR): Information needed to make decisions and deliver a project.

Exchange information requirements (EIR): Requirements for a defined information exchange or milestone.

BIM execution plan (BEP): Plan explaining how the delivery team will meet information requirements.

Information container: A named and controlled set of information, such as a model, drawing or schedule.

Common data environment (CDE): Managed environment for collecting, sharing, approving and archiving information.

Level of information need: Proportionate specification of required geometry, data and documentation.

Federated model: Combined view of separately authored discipline or system models.

Responsibility matrix: Table assigning information production, review, coordination and approval duties.

RACI: Responsibility framework using Responsible, Accountable, Consulted and Informed roles.

Task information delivery plan (TIDP): Task-team schedule of planned information deliverables.

Master information delivery plan (MIDP): Integrated project schedule of information deliveries.

Model production method: Agreed procedure for authoring, coordinating, exchanging and controlling models.

Clash detection: Automated or manual identification of spatial or system conflicts.

Information validation: Checking information against defined requirements and acceptance criteria.

Asset identifier: Unique reference assigned to an asset for tracking and management.

Information protocol: Contractual or procedural document defining information-management rules.

Information security: Protection of information from unauthorized access, alteration, loss or disclosure.

Digital twin: A connected digital representation that may combine asset information with operational data.

Review Questions

Short Answer Questions

1. Distinguish between AIR and PIR.
2. What is the purpose of an EIR?
3. Name four typical contents of a BIM execution plan.
4. What is the difference between a TIDP and an MIDP?
5. Why is a federated model often preferable to one shared authoring file?

Long Answer Questions

1. Explain how OIR, AIR, PIR and EIR form a connected information-requirements hierarchy.
2. Describe how a responsibility matrix can reduce ambiguity and contractual risk.
3. Discuss the principal components of a BIM execution plan and their relationship to project delivery.
4. Explain why level of information need should include geometry, alphanumerical data and documentation.
5. Evaluate the role of quality assurance and quality control in BIM information delivery.

Analytical / Application Questions

1. A hospital project requests a highly detailed model but has no asset-data requirements. Identify the likely risks and propose a revised requirements-development process.
2. Develop a short EIR outline for the handover of air-handling units in a university building, including information fields, format, responsible parties and acceptance checks.
3. Two discipline models are correctly located but contain conflicting equipment identifiers. Explain how the BEP, responsibility matrix and validation process should address the problem.

Multiple Choice Questions with Answers

Question 1

Which requirement level expresses an organization’s strategic information needs?

A. Organizational information requirements

B. Exchange information requirements

C. Task information delivery plan

D. Asset information requirements

Correct Answer: A. Organizational information requirements

Question 2

Which document integrates task-team information delivery schedules into one project schedule?

A. Asset information model

B. Master information delivery plan

C. Clash matrix

D. Object library

Correct Answer: B. Master information delivery plan

Question 3

Which item is primarily an alphanumerical information requirement?

A. Wall thickness shown in a section

B. Three-dimensional equipment location

C. Unique asset identifier

D. Rendered perspective view

Correct Answer: C. Unique asset identifier

Question 4

What is the principal purpose of a BIM execution plan?

A. To replace the construction contract

B. To explain how information requirements will be met

C. To guarantee that all models use one software application

D. To eliminate the need for design reviews

Correct Answer: B. To explain how information requirements will be met

Question 5

In a RACI framework, who performs the work?

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: A. Responsible

Question 6

Which statement best describes a federated model?

A. A single model authored by every discipline simultaneously

B. A combined view of separately authored models

C. A model containing only architectural geometry

D. An archived model that cannot be revised

Correct Answer: B. A combined view of separately authored models

Question 7

Why should information requirements be proportionate?

A. To ensure every object has maximum geometric detail

B. To reduce all information exchanges to one final delivery

C. To match information effort and detail to its intended purpose

D. To avoid involving facilities-management personnel

Correct Answer: C. To match information effort and detail to its intended purpose

Question 8

Which activity is a data-quality check?

A. Checking whether required asset properties contain valid values

B. Changing the building’s design without approval

C. Rendering a marketing image

D. Deleting unresolved issues from a report

Correct Answer: A. Checking whether required asset properties contain valid values

Question 9

Who should help develop asset information requirements?

A. Only the software vendor

B. Facilities managers and operational users, among others

C. Only the planning authority

D. Only the visualization specialist

Correct Answer: B. Facilities managers and operational users, among others

Question 10

What is a major ethical risk of false precision in a BIM model?

A. The model becomes easier to federate

B. Decision-makers may mistake uncertain information for reliable information

C. The model uses an open exchange format

D. The project has a responsibility matrix

Correct Answer: B. Decision-makers may mistake uncertain information for reliable information