00001 eir

My Project
2021-08-30
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

01
EIR
Exchange Information Requirements (EIR) - the
EIR are detailed information requirements shared
with Lead Appointed Parties for tender and
Appointment

Status:

IN PROGRESS: 43

SHARED: 0

PUBLISHED: 0

EIR

powered by plannerly.com 1
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

01
1 Introduction
1.1 Exchange Information Requirements (EIR)
1.2 ISO 19650 Hierarchy of Information Requirements
2 Project Information
2.1 Appointing Party Contact Details
2.2 Project Details
2.3 Project Scope
2.4 Project Constraints
2.5 High Level Purpose of Information
2.6 Information Delivery Milestones
2.7 Key Decision Points
2.8 Key Questions

EIR

powered by plannerly.com 2
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

1 Introduction

01
1.1 Exchange Information Requirements (EIR)
Exchange Information Requirements (EIR) specify our base requirements for Building Information
Modeling (BIM) in line with ISO 19650.

We seek standardized good quality information that can be exchanged, integrated and interrogated during
project delivery and following Handover.

The EIR contains our strategy, Key Performance Indicators, BIM Uses, and desired outcomes from the use
of BIM on our project.

The EIR has sections completed by us as the Appointing Party (or by a Representative, Advisor or
Consultant that we have appointed) to identify our project specific requirements.

Our information requirements resources include the following documents:

WHERE TO FIND
NAME WHAT IT IS
IT

The OIR presents our mission, vision, values

Organizational Information
and the primary reasons why we require see Plan > OIR
Requirements (OIR)
specific information to run our business.

The PIR shares project goals, existing project

Project Information
information, key decision points and defines see Plan > PIR
Requirements (PIR)
our expectations for project delivery.

Exchange Information The EIR are detailed information requirements see Plan > EIR +
Requirements (EIR) filtered for each appointment tender package. Scope

The AIR lists the assets along with their

Asset Information Requirements
information requirements necessary to deliver see Scope > AIR
(AIR)
the goals of the OIR, PIR and EIR.

The Responsibility Matrix is a chart describing

Responsibility Matrix tasks and deliverables with accountable team see Scope
and responsible team member assignments.

These milestones mark predefined information

Project Milestones exchanges for deliverables with descriptions to see Scope
explain the purpose of each.

Legal appointment documents to ensure that

see Plan >
Information Protocol our requirements become a contractual for all
Appointment
Appointed Parties.
EIR

powered by plannerly.com 3
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

1.2 ISO 19650 Hierarchy of Information Requirements

01
EIR

powered by plannerly.com 4
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

2 Project Information

01
2.1 Appointing Party Contact Details
APPOINTING
DETAILS
PARTY

Company Name:

Company Website:

Company Address:

Main Contact
Name:

Main
Contact Email:

Main
Contact Phone:

2.2 Project Details

ITEM DESCRIPTION

Facility Name:

Site Name:

Facility
Description:

Site Description:

Project Status:

Note: Project Title, Project Type, Address, Description, Language and Standard are found on the
Project Dashboard / report Cover Pages

2.3 Project Scope

EIR

powered by plannerly.com 5
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

WHAT WILL BE BUILT:

01
Project scope analysis:

ITEM DESCRIPTION

Project Justification
(business need that this
project is undertaken to
address):

Project Description (brief

summary of the project):

Project Deliverables
(summarized list of
required deliverables):

Out-of-scope Items (any

items that will remain out
of scope):

Project Objectives
(quantifiable criteria
considered for success):

Cost Objectives:

Schedule Objectives:

Acceptance Criteria:

Assumptions (list of
assumptions governing the
conduct on the project):

2.4 Project Constraints

Details about the fundamental constraints that could impact the project time, cost and quality.

CONSTRAINT DETAILS

Budget

Quality
EIR

Performance

powered by plannerly.com 6
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

CONSTRAINT DETAILS

01
Equipment

Personnel

Regulatory

2.5 High Level Purpose of Information

Per ISO 19650-1 "5.1 Principles" we describe in the table below the high level purposes of information
required to support our organizational and/or project objectives.

Any Appointed Party can suggest the addition of their own information requirements to this list.

The resultant requirements from this list will form the Information Delivery Milestones at certain Stages in
the project Scope.

Where information exchange within a delivery team is necessary some of the information requirements
can be passed to their own appointed parties through the assignment in the Scope.

The reasons why information is required during the project are listed below:

PURPOSE DESCRIPTION

Information on the recommended maintenance tasks, including planned

For Example: Maintenance
preventative maintenance, should be provided to help anticipate and plan
and Repair
for costs of maintenance.

Information on the expected replacement service life and costs to

anticipate the costs of replacement; recycling of the physical assets should
For Example: Replacement
be supported with detailed information relating to the principal
constituent materials.

EIR

powered by plannerly.com 7
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

PURPOSE DESCRIPTION

01
2.6 Information Delivery Milestones
The project Information Delivery Milestones have been defined through the consideration of the following:

1. High Level Purposes of Information

2. Appointing party’s key decision points
3. Appointing Party's information delivery obligations (if any)
4. The nature and substance of information to be delivered at each key decision point
5. The date(s) relative to each key decision point that the information model is to be delivered

Information Delivery Milestones along with their dates and descriptions are captured as structures
information in the Scope:

START
STAGE/PHASE NAME/TITLE END DATE DESCRIPTION
DATE

2.7 Key Decision Points

ACTIVITY START END OWNER

Preparation and brief

Invitation to tender

Tender response

Appointment of design consultant

Delivery of brief

Acceptance of brief

Mobilization
EIR

Collaborative production of
information

powered by plannerly.com 8
Document ID: -JBLWQRX15K67PW3L6NUBA

Free Version www.plannerly.com

ACTIVITY START END OWNER

01
Delivery of developed design

Appointment of main contractor

Delivery of technical design

Information model delivery

2.8 Key Questions

Portfolio Planning questions related to: Statutory Approvals, Maintenance, Operations, Space
Utilization and Portfolio Modifications

QUESTION ANSWER

Asset Management questions related to: Asset Registration, Life Cycle Cost, Risk Assessment and Asset
Replacement

QUESTION ANSWER

Strategic Business Operation questions related to: Health and Safety, Environmental, Sustainability and
Capital Investment

QUESTION ANSWER
EIR

powered by plannerly.com 9