Exchange Information

Requirements (EIR)
Template
BIM Toolkit | Exchange Information Requirements (EIR) 1
Template

Template content selection

This section is intended to assist with the selection of applicable template content, which is dependent
on the project and combined project delivery team’s building information modelling (BIM) experience.
The experience measures are aligned with the BIM toolkit overview (401428-MMD-ZZ-PW-ZZ-TK-
0001) BIM adoption journey table. Once the applicable answer is selected below, the template will
automatically populate the relevant content sections.

To begin populating the template, please select the answer from the dropdown menu that best relates
to your information requirements in response to the following question:

Have you established a clear set of objectives that are supported by building
information modelling (BIM) principles for appointment of the project delivery team?

Answer:

Select an answer

Answer selection criteria:

If your answer is ‘NO’, the template will be populated as low maturity exchange information
requirements (EIR). This is intended for users that have never used ISO 19650 principles
before or who have some experience in the use of models-based building information
modelling (BIM) or virtual design construction (VDC).

If your answer is ‘YES’, the template will be populated as high maturity exchange
information requirements (EIR). This is intended for advanced users that have experience in
creating information requirements and have a consistent and standardised level of building
information modelling (BIM).
BIM Toolkit | Exchange Information Requirements (EIR) 2
Template

Contents

Template content selection 1

1 Introduction 4
1.1 Exchange information requirements (EIR) purpose 4
1.2 Information management goals and objectives 4
1.2.1 Goals 4
1.2.2 Objectives 4
1.3 Information requirements hierarchy and progression 4
1.3.1 Information requirements hierarchy 4
1.3.2 Exchange information requirements (EIR) response requirements 4
1.3.2.1 Pre-appointment BIM execution plan (pre-BEP) 4
1.3.2.2 Supplementary documents 4
1.3.2.3 Delivery team’s BIM execution plan (BEP) 5

2 Information requirements 6
2.1 Information purpose 6
2.2 Plan of work 6
2.3 Information delivery milestones 6
2.4 Information security requirements 6
2.5 Spatial coordination requirements 6
2.6 Project information model (PIM) 8
2.7 Asset information model (AIM) 8
2.8 Information management key performance indicators (KPIs) 8
2.9 Health and safety and design construction risk management 8

3 Information standards, information production methods and procedures 10

3.1 Information standards 10
3.1.1 Project-specific standards 10
3.1.2 Information identification conventions 10
3.1.2.1 Information container identification 10
3.1.2.2 Common data environment (CDE) metadata requirements 10
3.1.3 Method of assignment for level of information need 11
3.1.4 Data authoring 11
3.1.4.1 Data exchange formats 11
3.1.5 Information software platforms 12
3.1.6 Information model quality 12
3.2 Information production methods and procedures 13
3.2.1 Information management functions 13
3.2.2 Information collaboration process 13
3.2.2.1 Common data environment (CDE) workflow 13
3.2.2.2 Information exchange frequency 13
3.2.2.3 Mobilisation 13
3.2.2.4 Training 13
BIM Toolkit | Exchange Information Requirements (EIR) 3
Template

3.2.3 Authorisation and acceptance process 13

3.2.4 Spatial coordination strategy 13
3.2.5 Legacy information and shared resources requirements 14
3.2.6 Capture of existing asset information 14
3.2.7 Information container breakdown structure 14
3.2.8 Lessons learnt 14

Tables
Table 2.1: Information delivery milestones 6
Table 2.2: Spatial coordination information requirements 7
Table 2.3: Key performance indicators (KPIs) 8
Table 2.4: Health and safety information requirements 9
Table 3.1: Preferred software authoring tools 11
Table 3.2: Required exchange formats 11
Table 3.3: Information software platforms 12
BIM Toolkit | Exchange Information Requirements (EIR) 4
Template

1 Introduction

1.1 Exchange information requirements (EIR) purpose

<Outline the purpose of the exchange information requirements (EIR) for the project and their intended
use.>

1.2 Information management goals and objectives

<Provide an overview of the appointing party’s commitment to their organisational BIM goals and
objectives.>

1.2.1 Goals

< Define the appointing party’s information management goals, for both the project delivery and asset
operation, relating to the organisational information requirements (OIR).>

1.2.2 Objectives

<Outline the project’s information management objectives; these should be considered, including
specific actions that are to be implemented on the project, in order to achieve the above goals, relating
to the project information requirements (PIR).>

1.3 Information requirements hierarchy and progression

<Outline the project documentation management process from procurement to handover.>

1.3.1 Information requirements hierarchy

<Provide an understanding of the information requirements hierarchy.>

1.3.2 Exchange information requirements (EIR) response requirements

<The pre-appointment BIM execution plan (pre-BEP) is produced at the tender stage by the prospective
delivery team in response to the invitation to tender. It should outline the delivery methodology that the
delivery team intends to implement in order to meet the information requirements. This section should
contain the minimum content that the appointing party expects to receive in response to the exchange
information requirements (EIR).>

1.3.2.1 Pre-appointment BIM execution plan (pre-BEP)

<Outline the expectations of the delivery team to highlight any potential risks associated with meeting
the delivery milestones and provide a description of how they intend to mitigate these risks.>

1.3.2.2 Supplementary documents

<Outline any supplementary pre-appointment BIM execution plan (pre-BEP) documents, which are
expected in response to the exchange information requirements (EIR).>
BIM Toolkit | Exchange Information Requirements (EIR) 5
Template

1.3.2.3 Delivery team’s BIM execution plan (BEP)

<Outline how the information requirements and information management documentation is progressed
throughout the project.>
BIM Toolkit | Exchange Information Requirements (EIR) 6
Template

2 Information requirements

2.1 Information purpose

<Provide an overview of the appointing party’s purpose for requiring the information specified below.>

2.2 Plan of work

<Define the principal stages in the design, construction work and maintenance of a project and identify
the main tasks.>

2.3 Information delivery milestones

<Specify when information is going to be delivered; see Table 2.1: Information delivery milestones),
which could be aligned with the plan of work. Provide actual delivery dates.>

Table 2.1: Information delivery milestones

Milestone

Work package/activity Deliverables Date

Stage
Work

<Insert <Insert work package/activity> <Insert deliverables> <Date>

milestone>
<Insert work <Insert
stage> milestone>
<Insert
milestone>

2.4 Information security requirements

<Provide the security requirements that have been identified for this project.>

2.5 Spatial coordination requirements

<Outline the expectations of how the delivery team are to ensure a coordinated design through clash
avoidance and detection. Use Table 2.2: Spatial coordination information requirements) to specify the
minimum frequency of clash rendition activities, how the delivery team should illustrate the clash
rendition workflow and the methodology of reporting clash resolutions.>
BIM Toolkit | Exchange Information Requirements 7
Template

Table 2.2: Spatial coordination information requirements

Acceptance
Milestone Description Supporting information Information requirements Information container Exceptions
criteria

<Milestone <Insert supporting <Insert information <Insert information <Acceptance

<Description> <Exceptions>
number> information> requirements> container> criteria>
BIM Toolkit | Exchange Information Requirements 8
Template

2.6 Project information model (PIM)

<Define the information deliverables required for the project information model (PIM), which should
include identifying the task team responsibilities.>

2.7 Asset information model (AIM)

<Define the information deliverables required for the collation of the asset information model (AIM),
which should include identifying the task team responsibilities. These should reflect the asset
information requirements (AIR).>

2.8 Information management key performance indicators (KPIs)

<Provide an outline of the specific key performance indicators (KPIs) (see Table 2.3: Key performance
indicators (KPIs)) that the lead appointed party is required to analyse and provide feedback on to the
appointing party at agreed intervals.>

Table 2.3: Key performance indicators (KPIs)

KPIs Description and outcome Frequency Project stage
<Project stage this
<KPI title> <Description> <Frequency>
applies to>

2.9 Health and safety and design construction risk management

<Identify the appointing party’s health and safety requirements, which could be a reference to an internal
or external standard, in Table 2.4: Health and safety information requirements. Describe how the
delivery team should approach utilising the information model, aligning with the work stages, to meet
these requirements. This could include, but not be limited to: access and maintenance, equipment
routes, site orientation/welfare, temporary works, designer risk assessment and risk scheduling. If the
model is not being used for this purpose, an explanation should be provided.>
BIM Toolkit | Exchange Information Requirements 9
Template

Table 2.4: Health and safety information requirements

Acceptance
Milestone Description Supporting information Information requirements Information container Exceptions
criteria

<Milestone <Insert supporting <Insert information <Insert information <Acceptance

<Description> <Exceptions>
number> information> requirements> container> criteria>
BIM Toolkit | Exchange Information Requirements (EIR) 10
Template

3 Information standards, information

production methods and procedures

<Outline the purpose of the information standards, information production methods and
procedures for the project and their intended use.>

3.1 Information standards

<Define the information standards that are to be adhered to on this project.>

3.1.1 Project-specific standards

<Define both the internal and external standards that all project information production and
management should adhere to. These should be reflected within the main body of the document.>

3.1.2 Information identification conventions

<Provide references to standards that define information containers, space and objects, naming
conventions that are to be adhered to on this project. Different countries might refer to local
standards or the standard that they are more comfortable with.>

3.1.2.1 Information container identification

<Provide the information metadata standards that the delivery team must comply with. Metadata
can refer to different characteristics of the files. It can include status code, revision code and
security classification owner, among others. All files shall be populated with the appropriate
metadata. This could include references to specific standards.>

3.1.2.2 Common data environment (CDE) metadata requirements

<Outline any further metadata requirements.>

Status and revision metadata

<Identify the status and revision metadata requirements for the project, which will depend on the
complexity of the project.>

Security classification
<If any security requirements have been identified on the project, provide references to any
classification standards that security metadata should adhere to.>

Information classification
<If any information classifications have been identified on the project, provide references to any
classification standards that security metadata should adhere to.>
BIM Toolkit | Exchange Information Requirements (EIR) 11
Template

3.1.3 Method of assignment for level of information need

<Provide further definition or reference to standards for both the level of detail (LOD) and level of
information (LOI):

LOD – Level of detail refers to the amount of geometry shown in the graphical digital
representation at a particular stage of the project; and

LOI – Level of information refers to the amount of information (data) contained within, or
associated with, the model at a particular stage of the project.>

3.1.4 Data authoring

<Specify the compatibility requirements of file formats that each task team are to comply with.
There should be an explanation of how the delivery team are expected to comply. This could be
references to specific software for the BIM model authoring. Table 3.1 (Preferred software
authoring tools) provides a list of desirable software for graphical model and drawing authoring.>

Table 3.1: Preferred software authoring tools

Discipline Software Version Format

Architecture <Native file formats> <Version> <Format>

Civil <Native file formats> <Version> <Format>
Structural <Native file formats> <Version> <Format>
Mechanical <Native file formats> <Version> <Format>
Drainage <Native file formats> <Version> <Format>

3.1.4.1 Data exchange formats

<Specify the file formats required for specific information containers. The formats of each file type
should be defined within Table 3.2 (below).>

Table 3.2: Required exchange formats

Relevant data
Type Native file formats Version Rendition formats
drops
MS Office <Native file
<Version> <Rendition formats> <Data drops>
documentation formats>
Models and <Native file
<Version> <Rendition formats> <Data drops>
drawings formats>
<Native file
GIS models <Version> <Rendition formats> <Data drops>
formats>
<Native file
Cost plans <Version> <Rendition formats> <Data drops>
formats>
<Native file
Programmes <Version> <Rendition formats> <Data drops>
formats>
Photos, videos, <Native file
<Version> <Rendition formats> <Data drops>
animations formats>
BIM Toolkit | Exchange Information Requirements (EIR) 12
Template

3.1.5 Information software platforms

<Specify the software that the appointing party will use throughout the project and operation, if
applicable. The delivery team is required to consider the interoperability of these platforms; see
Table 3.3: Information software platforms.>

Table 3.3: Information software platforms

Purpose Software Version
Non-graphical data <Software name> <Software version>
management system (e.g.
common data environment for
non-graphical PDF and Office
files)
Drawing and model viewers <Software name> <Software version>
Document <Software name> <Software version>
viewing/authoring/editing

3.1.6 Information model quality

<Provide the minimum quality assurance requirements that each aspect of the information model
should adhere to.>
BIM Toolkit | Exchange Information Requirements (EIR) 13
Template

3.2 Information production methods and procedures

<Define the information production methods and procedures that are to be adhered to on this
project.>

3.2.1 Information management functions

<Specify the parties’ responsibilities for the information management activities identified in ISO
19650–2:2018.>

3.2.2 Information collaboration process

<Define an overview of the expectations for collaboration on this project, describing the required
frequency of information sharing. This should include both digital information exchanges and
meetings for the whole delivery team. The subsections below should outline detailed processes
for collaboration.>

3.2.2.1 Common data environment (CDE) workflow

<Provide an overview of the common data environment (CDE) procedures. Define the
responsibilities of the delivery team, determining who will be responsible for hosting and
managing the common data environment (CDE). Describe how it should be used to share all
project information, including the quality assurance requirements at each step.>

3.2.2.2 Information exchange frequency

<State the minimum frequency of information exchanges expected of the delivery team. This
should include periodical model sharing.>

3.2.2.3 Mobilisation
<Set the expectation that the delivery team is to identify all training, tests and checks that will be
performed before any project work begins.>

3.2.2.4 Training
<Define, if any, the training requirements for each task team involved in the production and
management of information. Identify who will be responsible for providing training at relevant
project stages, which can include specific references to standards, teaching techniques and best
practice.>

3.2.3 Authorisation and acceptance process

<Define the appointing party’s information approval process. Provide a workflow that outlines how
the delivery team should submit information for approval and for the review procedure and which
includes both successful and unsuccessful outcomes. All approval processes should be via the
common data environment (CDE).>

3.2.4 Spatial coordination strategy

<Identify the minimum requirements that the delivery team should comply with when creating the
federation strategy; see Table 3.3: Required exchange formats. This should explain the criteria
for defining the information container sets; it could be set on discipline, clash avoidance, file size
limits or task team responsibilities. Minimally, there should be at least one volume per discipline.>
BIM Toolkit | Exchange Information Requirements (EIR) 14
Template

3.2.5 Legacy information and shared resources requirements

<Explain any legacy information and shared resources that have been provided and their intended
usage.>

3.2.6 Capture of existing asset information

<Describe how the delivery team are to capture existing asset information throughout the project.
This may be through using traditional survey techniques or more sophisticated techniques such
as 3D scanning and photogrammetry.>

3.2.7 Information container breakdown structure

<Identify the minimum requirements that the delivery team should comply with when creating the
federation strategy. This should explain the criteria for defining the information container sets; it
could be set on discipline, clash avoidance, file size limits or task team responsibilities. Minimally,
there should be at least one volume per discipline.>

3.2.8 Lessons learnt

<Stipulate when lesson learnt reviews should occur and how the feedback should be adopted by
the current delivery team, if appropriate.>