Exchange Information Requirements Explained
How Asset Owners turn information needs into clear, measurable project deliverables
An Asset Owner may know what information the organisation needs.
They may have defined their Organisational Information Requirements (OIR) and Asset Information Requirements (AIR).
But there is still an important question:
How do we make sure the project team actually delivers that information?
This is where Exchange Information Requirements (EIR) become important.
EIR provide the bridge between what the Owner needs and what the project team must exchange, produce and deliver during the project.
The principle is simple:
The Owner defines what matters. The project requirements define what must be delivered. Validation provides evidence that it has been delivered correctly.
From Organisational Need to Project Delivery
The relationship can be viewed as a chain:
Each level answers a different question.
OIR
What information does the organisation need?
AIR
What information do we need about our assets?
EIR
What information must the project team provide, when and in what form?
This distinction is important because the Asset Owner should not expect consultants and contractors to determine the organisation's information needs themselves.
They are responsible for delivering against clearly defined requirements.
What Should an EIR Achieve?
An effective EIR should remove ambiguity from the project's information deliverables.
It should establish expectations around matters such as:
What information is required
Which assets or elements require it
When information must be delivered
Who is responsible for producing it
Which information standards apply
What format should be used
How information will be exchanged
How compliance will be assessed
This changes the conversation from:
Please provide a BIM model.
to something much more precise:
At this project stage, these assets must contain these information attributes, using these naming and classification standards, delivered in this agreed format, and capable of passing these validation rules.
That is a much more useful requirement.
EIR Should Be Measurable
One of the weaknesses of poorly defined BIM requirements is that they can be difficult to measure.
For example:
Weak requirement:
The contractor must provide complete asset information.
What does "complete" mean?
Different people may have different interpretations.
A stronger requirement might establish:
Asset: Air-handling unit
Required information:
Asset ID
Asset type
Manufacturer
Model number
Serial number
Location
Warranty information
Maintenance interval
System served
Delivery stage: Commissioning / handover
Responsible party: Contractor / MEP subcontractor
Validation: Required fields populated; asset ID unique; location valid.
Now the requirement can actually be tested.
EIR Connects the Project Team to the Owner's Needs
This is particularly important because consultants and contractors are the providers of the information.
The Owner remains the party that determines what information is required to support its business and asset-management objectives.
For example:
Owner objective
Improve preventive maintenance.
↓
AIR
Maintainable assets require reliable maintenance information.
↓
EIR
The project team must provide defined maintenance information for specified asset classes at agreed project stages.
↓
Validation
The information is checked for completeness, consistency and compliance.
↓
Handover
Validated information is transferred into the operational environment.
The EIR therefore creates the contractual and delivery connection between need and supply.
EIR Should Define When Information Is Required
Information should not necessarily be delivered only at the end of the project.
Different information becomes valuable at different stages.
For example:
Stage | Example Information Need |
Planning | Project and asset requirements |
Concept Design | Spaces, systems and preliminary asset information |
Developed Design | Systems, classifications and coordinated information |
Technical Design | Detailed asset and specification information |
Construction | Installed equipment and construction status |
Commissioning | Serial numbers, test results and warranties |
Handover | Validated operational asset information |
This is important because information quality should be managed throughout the project, rather than attempting to correct everything at handover.
EIR and Information Validation
An EIR becomes particularly powerful when its requirements can be converted into measurable validation rules.
For example:
EIR Requirement
Every maintainable asset must have a unique Asset ID.
↓
Validation Rule
Asset ID must not be blank.
↓
Validation Rule
Asset ID must be unique.
↓
Validation Rule
Asset ID must conform to the agreed naming convention.
↓
Compliance Result
PASS / FAIL
This is the foundation for automated BIM compliance.
EIR Are Not Just About BIM Models
This is another important distinction.
An EIR should not be interpreted as simply:
What needs to be in the Revit model?
The Owner may require information that exists outside the model.
For example:
Commissioning records
Product data
Warranty certificates
Maintenance manuals
Test certificates
Asset registers
Photographs
Compliance documentation
GIS information
Spreadsheets
Structured databases
The objective is not to force every piece of information into a BIM model.
The objective is to ensure that the right information is delivered in a form that can actually be used.
This becomes especially important for infrastructure projects where information may span BIM, GIS, CAD, databases and other systems.
EIR and Legacy Assets
There is also a significant implication for existing infrastructure.
Not every asset has a BIM model.
An Asset Owner may have:
Old CAD drawings
Scanned drawings
PDFs
Equipment schedules
Spreadsheets
Photographs
GIS information
Paper records
The organisation still has information requirements.
The absence of a BIM model does not eliminate the need for reliable asset information.
This is why the same requirements philosophy can eventually be applied to Legacy Asset Information Activation:
What information does the Owner need?
↓
What information exists?
↓
What is missing?
↓
What needs to be extracted or captured?
↓
How should it be structured?
↓
How will it be validated?
↓
How can it be activated for asset management?
This creates a common information strategy for both new and existing assets.
From EIR to Automated Compliance
The real opportunity is to make EIR increasingly machine-readable and testable.
A future-oriented workflow could look like:
OIR
↓
AIR
↓
EIR
↓
Information Specification
↓
BIM / GIS / Asset Data
↓
Automated Validation
↓
Compliance Dashboard
↓
Issue Resolution
↓
Validated Information
↓
FM / Asset Management
This is where technologies such as IDS can become particularly valuable.
Instead of relying entirely on a person to interpret a document and determine whether information complies, requirements can increasingly be expressed in a structured form that software can test.
The EIR Is Where Requirements Become Deliverables
The progression from OIR to AIR to EIR is therefore fundamental:
OIR
Why do we need the information?
AIR
What information do we need about the assets?
EIR
What must the project team deliver?
Validation
Did they deliver it correctly?
Operations
Can the organisation use it?
This creates accountability throughout the information lifecycle.
It also makes it much easier to identify where a problem originates.
If information is missing, we can ask:
Was the requirement defined?
Was it communicated?
Was responsibility assigned?
Was it delivered?
Was it validated?
This is far more effective than discovering at handover that "the model is missing information."
The Asset Owner Still Has the Key Role
The most important point is that the EIR should not become a technical BIM document disconnected from the organisation.
The process should always start with the Owner.
The Owner establishes the organisational objectives.
The organisation identifies its information needs.
Asset and FM requirements are developed.
Project information requirements are established.
Consultants and contractors deliver the information.
BIM teams manage and coordinate it.
Validation provides evidence of compliance.
And the organisation ultimately uses the information to manage its assets.
The EIR is therefore not the beginning of the information journey.
It is the point where the Owner's information needs become project delivery requirements.
Good information management is not about asking project teams to provide "more BIM."
It is about being precise about what information is needed, why it is needed, who must provide it, when it must be provided and how compliance will be demonstrated.
That is the real value of Exchange Information Requirements.
They turn:
Organisational Need
into
Asset Information Requirements
into
Project Deliverables
into
Validated Information
into
Better Asset Management Decisions.
For Asset Owners and Infrastructure Authorities, this is the critical connection between strategy and delivery.
And once that connection exists, BIM Compliance becomes much more than checking models.
It becomes a mechanism for ensuring that the project delivers the information the organisation actually needs.
About Dabisa Consulting
At Dabisa Consulting, we help Asset Owners and Infrastructure Authorities connect OIR, AIR and EIR with practical BIM Compliance, Data Validation and Digital Handover processes.
Our objective is simple:
From BIM Models to Trusted Asset Information.
Next in the Series
Not Every Asset Has a BIM Model - So What?
Comments