Consulting Design Engineer
Building services design and its information deliverables for the design team
Consulting Design Engineer: clarifying incomplete information requirements on a public building
The scenario
A Consulting Design Engineer in a small, single-discipline building services engineering consultancy, acting as an Appointed Party for all stages of a €14 million extension and refurbishment of a post-primary school for an Education and Training Board. The Architect is appointed as Lead Appointed Party (LAP) and Information Manager, acting on behalf of the Appointed Parties (APs) in the Design Team. The project is within the scope of the CWMF BIM mandate.
The challenge comes from the shortfall in the Level of Information Need specified in the Exchange Information Requirements (EIR) for the Design Team LAP and AP appointments. The Appointing Party's information requirements lack asset-specific detail and consistency, particularly around the core BIM requirements of the CWMF BIM mandate. EIRs issued at Design Stage are generally template-based, with contradictory and sporadic project information requirements: for example, specifying COBie as a deliverable without providing a maintainable asset list or any detail on how asset information should be structured, validated or delivered. Uniclass requirements give no direction on which coding tables or classification strategy to adopt. The EIR refers to both NBS and AIA conventions, and uses PAS 1192 terminology alongside ISO 19650 terminology. Project-specific file naming, container and code requirements are not defined from the project start, which creates confusion, duplication and delays when issuing information. The result is inconsistent asset data across the project team.
The Design Stage LAP has attempted to produce a Design Stage BIM Execution Plan (BEP), but lacks the resources and the direction from the Appointing Party to develop a comprehensive, coordinated information management strategy. Design team BIM documentation is therefore delayed, inconsistent and short on useful detail. Significant project time goes on interpreting requirements, seeking clarifications and aligning differing stakeholder expectations rather than on delivering the contractual requirements, and decisions are at risk of being challenged at Construction and Handover, when the Appointing Party's asset information requirements become clearer.
The engineer needs to engage with the client where information requirements are incomplete, ambiguous or inconsistent with ISO 19650 principles: raising clarification requests, agreeing discussion points and developing the missing requirements collaboratively, so that unnecessary delays and additional costs are avoided for both the Appointing Party and the engineer. Useful guidance includes the ACEI MEP and Structural Advice Notes and the ACEI Position Paper on the CWMF BIM Requirements.
Incomplete or inconsistent information requirements are clarified early with the client and the Lead Appointed Party, so asset information is produced consistently.
How you will know
- Gaps and inconsistencies in the EIR are raised as clarification requests early in Design Stage.
- Classification, COBie and Level of Information Need are agreed with the client and the Lead Appointed Party.
- File naming and container requirements are agreed before information is first issued.
- The engineer's contribution to the BEP reflects the agreed requirements.
- Asset information is produced consistently, avoiding rework at Construction and Handover.
By 01/07/2027.
A Consulting Design Engineer, when appointed to the design team of a €14 million post-primary school extension and refurbishment whose information requirements are incomplete and contradictory, must clarify the Appointing Party's information requirements (EIR).
Activity flow diagram
Choose Vertical to follow the flow from top to bottom on a narrow screen.
Scroll sideways to follow the flow. With the diagram focused, use the Left and Right arrow keys.
- Consulting Design Engineer
- Lead appointed party (architect)
- Appointing party (client)
- Issue
- Submit
- Accept
- Reject
- Inform
- Returns work to amend and resubmit
Explore the flow by stage
6 stages · 1 decision with 3 optionsChoose a stage to see what each party does in it, the hand-offs between them and any decision that follows. A decision's options are listed under it. The hand-off numbers match the numbered arrows on the diagram.
Each stage below shows what each party does in it, the hand-offs between them and any decision that follows. A decision's options are listed under it. The hand-off numbers match the numbered arrows on the diagram. Each stage's checklist is in the Full Scenario Record.
Decision after stage 1How will the gaps in the EIR be resolved?One option applies.
Stage 1: Review the client's EIR for gaps and inconsistencies
Consulting Design Engineer
On appointment to the €14 million school extension and refurbishment, the Consulting Design Engineer reviews the template-based Exchange Information Requirements (EIR), identifying gaps in Uniclass coding, conflicting PAS 1192 and ISO 19650 terminology, and unlisted COBie maintainable assets.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 1
Review the client's EIR for gaps and inconsistencies
Then decides: How will the gaps in the EIR be resolved?
- Receives 1: EIR and project information standard from Lead appointed party (architect) (issue)
Lead appointed party (architect)
ISO 19650 party
- Sends 1: EIR and project information standard to Consulting Design Engineer (issue)
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Appointing party (client).
Hand-offs at this stage
1EIR and project information standard
- From
- Lead appointed party (architect)
- To
- Consulting Design Engineer
- Hand-off
- Issue
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 1 | Lead appointed party (architect) | Consulting Design Engineer | Issue | EIR and project information standard |
Decision: How will the gaps in the EIR be resolved?
After stage 1: Review the client's EIR for gaps and inconsistencies. One option applies. Marks show how well each option meets a criterion. They are not scores, and they are not added up or ranked.
| Criterion | Option 1.1Formal clarification through the architect | Option 1.2A joint workshop with the client | Option 1.3Proceed on documented assumptions |
|---|---|---|---|
| Contractual alignmentDoes this approach follow established lead appointed party communication channels under the appointment? Evidence: E1 Master Information Delivery Plan (MIDP)
| +Strong Follows traditional appointment lines by routing formal requests via the architect. Evidence: E1 Master Information Delivery Plan (MIDP)
| ~Depends Requires agreement from the architect and appointing party to convene directly. Evidence: E1 Master Information Delivery Plan (MIDP)
| –Weak Proceeding without client acceptance breaches formal EIR alignment principles. Evidence: E1 Master Information Delivery Plan (MIDP)
|
| Speed of resolutionHow quickly does this route resolve inconsistencies and gaps to prevent project delays? | –Weak Iterative written clarification through an intermediary can cause significant delays. | +Strong Direct discussion enables instant resolution of terminology and asset list queries. | +Strong Design work proceeds immediately without waiting for client clarification. |
| Collaborative clarityDoes this method enable direct alignment on client expectations, classification, and asset requirements? Evidence: E2 Identify the foreseeable trigger events for which information shall be managed
| ~Depends Depends on whether the client and architect fully understand the technical BIM queries. | +Strong Fosters direct mutual understanding of maintainable assets and EIR expectations. Evidence: E2 Identify the foreseeable trigger events for which information shall be managed
| –Weak Lacks direct stakeholder consensus on client expectations and asset data. |
| Design team risk exposureTo what extent does this route minimise consultant liability regarding unverified requirements? Evidence: E1 Master Information Delivery Plan (MIDP)
| +Strong Maintains a formal contractual audit trail protecting against liability. Evidence: E1 Master Information Delivery Plan (MIDP)
| +Strong Agreed workshop outcomes can be formally captured and confirmed in the appointment. Evidence: E1 Master Information Delivery Plan (MIDP)
| –Weak Exposes the engineer to rework and liability if assumptions contradict client intent. Evidence: E1 Master Information Delivery Plan (MIDP)
|
Option 1.1
Formal clarification through the architect
- Option 1.1: Raise clarification requests through the architect
Rejoins at stage 2: Clarify governance under the CWMF mandate.
- Contractual alignment
- +StrongFollows traditional appointment lines by routing formal requests via the architect.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
- Speed of resolution
- –WeakIterative written clarification through an intermediary can cause significant delays.
- Collaborative clarity
- ~DependsDepends on whether the client and architect fully understand the technical BIM queries.
- Design team risk exposure
- +StrongMaintains a formal contractual audit trail protecting against liability.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Consequences
- Formal RFIs are issued via the architect, ensuring compliance with appointment channels.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
- Resolution of terminology, Uniclass, and COBie gaps may take longer due to indirect communication.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Option 1.2
A joint workshop with the client
- Option 1.2: Agree the missing requirements at a joint workshop
Rejoins at stage 2: Clarify governance under the CWMF mandate.
- Contractual alignment
- ~DependsRequires agreement from the architect and appointing party to convene directly.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
- Speed of resolution
- +StrongDirect discussion enables instant resolution of terminology and asset list queries.
- Collaborative clarity
- +StrongFosters direct mutual understanding of maintainable assets and EIR expectations.
Evidence: E2 Identify the foreseeable trigger events for which information shall be managed
Identify the foreseeable trigger events for which information shall be managed · Action Statement · Verified
identify the foreseeable trigger events for which information shall be managed
See the full evidence entry
- Design team risk exposure
- +StrongAgreed workshop outcomes can be formally captured and confirmed in the appointment.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Consequences
- Client, architect, and engineer directly align on Uniclass schemas and COBie asset scopes.
Evidence: E2 Identify the foreseeable trigger events for which information shall be managed
Identify the foreseeable trigger events for which information shall be managed · Action Statement · Verified
identify the foreseeable trigger events for which information shall be managed
See the full evidence entry
- Decisions must be formally recorded and incorporated into the revised appointment documentation.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Evidence: E1 Master Information Delivery Plan (MIDP); E2 Identify the foreseeable trigger events for which information shall be managed
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entryIdentify the foreseeable trigger events for which information shall be managed · Action Statement · Verified
identify the foreseeable trigger events for which information shall be managed
See the full evidence entry
Option 1.3
Proceed on documented assumptions
- Option 1.3: Proceed on documented assumptions, flagged as risks
Rejoins at stage 2: Clarify governance under the CWMF mandate.
- Contractual alignment
- –WeakProceeding without client acceptance breaches formal EIR alignment principles.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
- Speed of resolution
- +StrongDesign work proceeds immediately without waiting for client clarification.
- Collaborative clarity
- –WeakLacks direct stakeholder consensus on client expectations and asset data.
- Design team risk exposure
- –WeakExposes the engineer to rework and liability if assumptions contradict client intent.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Consequences
- Design progression continues immediately under logged assumptions.
- Rework or reclassification may be required if the appointing party rejects the assumed standards.
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Evidence: E1 Master Information Delivery Plan (MIDP)
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry
Checklist
0 of 7 ticked- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
- Assess the suitability of reference information and existing asset data · Action Statement · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Assess the suitability of reference information and existing asset data - Existing asset information and shared resources · Information Use · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Existing asset information and shared resources
- Assess the suitability of reference information and existing asset data · Action Statement · Verified
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps - Assess the suitability of reference information and existing asset data · Action Statement · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Assess the suitability of reference information and existing asset data - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps
Option 1.1: Raise clarification requests through the architect
Consulting Design Engineer · an option of the decision after stage 1: Review the client's EIR for gaps and inconsistencies
Raise numbered clarification requests through the Lead Appointed Party, each naming the requirement, the gap and the proposed answer.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out option 1.1
Raise clarification requests through the architect
Lead appointed party (architect)
ISO 19650 party
No part in this stage.
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Lead appointed party (architect), Appointing party (client).
Hand-offs at this stage
No hand-offs at this stage.
Checklist
0 of 6 ticked- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard - Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP) - Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
- Identify changes that need to be made to the project’s information production methods and procedures · Action Statement · Verified
identify changes that need to be made to the project’s information production methods and procedures and the project’s information standard to best achieve the information requirement.Instruction
See the evidence: Identify changes that need to be made to the project’s information production methods and procedures - Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
- Identify changes that need to be made to the project’s information production methods and procedures · Action Statement · Verified
identify changes that need to be made to the project’s information production methods and procedures and the project’s information standard to best achieve the information requirement.Instruction
See the evidence: Identify changes that need to be made to the project’s information production methods and procedures
Option 1.2: Agree the missing requirements at a joint workshop
Consulting Design Engineer · an option of the decision after stage 1: Review the client's EIR for gaps and inconsistencies
Agree discussion points with the client and the architect at a workshop, and develop the missing requirements together.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out option 1.2
Agree the missing requirements at a joint workshop
Lead appointed party (architect)
ISO 19650 party
No part in this stage.
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Lead appointed party (architect), Appointing party (client).
Hand-offs at this stage
No hand-offs at this stage.
Checklist
0 of 7 ticked- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps
- Existing asset information and shared resources · Information Use · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Existing asset information and shared resources - Assess the suitability of reference information and existing asset data · Action Statement · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Assess the suitability of reference information and existing asset data
- Existing asset information and shared resources · Information Use · Verified
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria - Cross-disciplinary coordinated model · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Cross-disciplinary coordinated model - Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Coordinate building services delivery dates in the task information delivery plan with the lead appointed party's master information delivery plan (MIDP) · Action Statement · Suggested – reviewSee the evidence: Coordinate building services delivery dates in the task information delivery plan with the lead appointed party's master information delivery plan (MIDP)
- Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the evidence: Master Information Delivery Plan (MIDP)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
Option 1.3: Proceed on documented assumptions, flagged as risks
Consulting Design Engineer · an option of the decision after stage 1: Review the client's EIR for gaps and inconsistencies
Where answers will not come in time, proceed on stated assumptions recorded in the BEP and the risk register, so later changes can be costed.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out option 1.3
Proceed on documented assumptions, flagged as risks
Lead appointed party (architect)
ISO 19650 party
No part in this stage.
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Lead appointed party (architect), Appointing party (client).
Hand-offs at this stage
No hand-offs at this stage.
Checklist
0 of 6 ticked- Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the evidence: Master Information Delivery Plan (MIDP)
- Master Information Delivery Plan (MIDP) · Information Use · Verified
- BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- BIM Execution Plan (BEP) · Information Use · Verified
- Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Project's Information Production Methods and Procedures · Information Use · Verified
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria
- Exchange Information Requirements (EIR) · Information Use · Verified
- Cross-disciplinary coordinated model · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Cross-disciplinary coordinated model
- Cross-disciplinary coordinated model · Information Use · Verified
Stage 2: Clarify governance under the CWMF mandate
Consulting Design Engineer
Under the CWMF BIM requirements, which apply to design teams on projects over €5 million from 1 July 2026, the engineer issues structured clarification requests through the Lead Appointed Party and agrees the governance points that the EIR leaves open.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 2
Clarify governance under the CWMF mandate
- Sends 2: Clarification requests on the EIR to Lead appointed party (architect) (submit)
Lead appointed party (architect)
ISO 19650 party
- Receives 2: Clarification requests on the EIR from Consulting Design Engineer (submit)
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Appointing party (client).
Hand-offs at this stage
2Clarification requests on the EIR
- From
- Consulting Design Engineer
- To
- Lead appointed party (architect)
- Hand-off
- Submit
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 2 | Consulting Design Engineer | Lead appointed party (architect) | Submit | Clarification requests on the EIR |
Checklist
0 of 7 ticked- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party · Action Statement · Suggested – reviewSee the evidence: Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard
- Identify changes that need to be made to the project’s information production methods and procedures · Action Statement · Verified
identify changes that need to be made to the project’s information production methods and procedures and the project’s information standard to best achieve the information requirement.Instruction
See the evidence: Identify changes that need to be made to the project’s information production methods and procedures - Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Identify changes that need to be made to the project’s information production methods and procedures · Action Statement · Verified
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
- Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
- BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP) - Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard
Stage 3: Agree building services Level of Information Need
Consulting Design Engineer
The engineer collaborates with the Lead Appointed Party and client to establish an information delivery strategy, defining building services Level of Information Need, Uniclass tables, and exchange schemas.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 3
Agree building services Level of Information Need
- Receives 3: Clarified requirements and Level of Information Need from Appointing party (client) (inform)
Lead appointed party (architect)
ISO 19650 party
No part in this stage.
Appointing party (client)
ISO 19650 party
- Sends 3: Clarified requirements and Level of Information Need to Consulting Design Engineer (inform)
No part in this stage: Lead appointed party (architect).
Hand-offs at this stage
3Clarified requirements and Level of Information Need
- From
- Appointing party (client)
- To
- Consulting Design Engineer
- Hand-off
- Inform
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 3 | Appointing party (client) | Consulting Design Engineer | Inform | Clarified requirements and Level of Information Need |
Checklist
0 of 6 ticked- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Review the Appointing Party's exchange information requirements for internal contradictions and gaps - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR)
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps · Action Statement · Verified
- Propose and agree the level of information need for building services elements at each design stage · Action Statement · Verified
| EIR-04 | Project Manager | Cost Driven Design.\nCost report | level of information need\n<URL LINK>\n | Acceptance criteria\n<URL LINK> | The supporting document outlining the objective of target value design as part of the key purposes of using BIM is available on the CDE as background information\n<URL LINK> | Every second Monday through the design stages of the project.\nFirst exchange DD-MM-YYYY | | EIR-05 | Project Manager | Commissioning report\nDocument building and information is accorInstruction › EIR
See the evidence: Propose and agree the level of information need for building services elements at each design stage - Exchange Information Requirements (EIR) · Information Use · Verified
The appointing party establishes exchange information requirements (EIR) for each lead appointed party appointment, considering, where appropriate, the organizational information requirements (OIR), asset information requirements (AIR) and project's information requirements (PIR) (see EN ISO 19650-1:2018, 5.1, Figure 2 and explanations in EN ISO 19650-1:2018, 5.2 to 5.7). The requirements for the EIR are specified in EN ISO 19650-2:2018, 5.2.1. An EIR is made available for all prospective lead a
See the evidence: Exchange Information Requirements (EIR) - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria - Cross-disciplinary coordinated model · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Cross-disciplinary coordinated model - Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange
- Propose and agree the level of information need for building services elements at each design stage · Action Statement · Verified
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response · Action Statement · Suggested – reviewSee the evidence: Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
- Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Contribute building services input to the delivery team's information delivery strategy · Action Statement · Verified
**Table 1 – Scope of documentation covered in this guidance according to EN ISO 19650-2:2018 clause reference** | | Invitation to tender EIR | Tender response pre-appointment BEP | Appointment BEP | | --- | --- | --- | --- | | In scope | 5.2.1 Appointing party’s exchange information requirements a) information requirement b) level of Information Need c) acceptance Criteria d) supporting Information e) information delivery dates | 5.3.2 Delivery team’s (pre-appointment) BIM execution plan a) info1 Scope
See the evidence: Contribute building services input to the delivery team's information delivery strategy - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- Contribute building services input to the delivery team's information delivery strategy · Action Statement · Verified
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria - Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
Stage 4: Contribute building services to the BEP and TIDP
Consulting Design Engineer
The engineer contributes the building services response to the BIM Execution Plan and formulates the MEP Task Information Delivery Plan (TIDP), defining the scope of production delivery and aligning milestone exchange dates with the Lead Appointed Party's Master Information Delivery Plan (MIDP).
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 4
Contribute building services to the BEP and TIDP
- Sends 4: Building services BEP input and TIDP to Lead appointed party (architect) (submit)
Lead appointed party (architect)
ISO 19650 party
- Receives 4: Building services BEP input and TIDP from Consulting Design Engineer (submit)
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Appointing party (client).
Hand-offs at this stage
4Building services BEP input and TIDP
- From
- Consulting Design Engineer
- To
- Lead appointed party (architect)
- Hand-off
- Submit
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 4 | Consulting Design Engineer | Lead appointed party (architect) | Submit | Building services BEP input and TIDP |
Checklist
0 of 7 ticked- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP) - Define the scope of production delivery · Action Statement · Verified
define the scope of production delivery
See the evidence: Define the scope of production delivery
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP) - Existing asset information and shared resources · Information Use · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Existing asset information and shared resources - Assess the suitability of reference information and existing asset data · Action Statement · Verified
| Supporting Information | | | | |---|---|---|---| | 2.1 d) establish the supporting information | | | | | – existing asset information, | | | | | – shared resources, | | | | | – supporting documents or guidance material, | | | | | – references to relevant international, national or industry standards, and | | | | | – exemplars of similar information deliverables; | | | | | 2.2 Assemble reference information and shared resources | | | | | – reference information or shared resources identified du
See the evidence: Assess the suitability of reference information and existing asset data - Project's Information Production Methods and Procedures · Information Use · Verified
| Additions or Amendments | | | | | | | |---|---|---|---|---|---|---| | 5.3.2 e) any proposed additions or amendments to the project’s information production methods and procedures that the delivery team require to facilitate the effective: | | | | | | | | – capture of existing asset information, | | | | | | | | – generation, review, approval and authorization of information, | | | | | | | | – security and distribution of information, and | | | | | | | | – delivery of information to the appointiInstruction › Amendments BEP
See the evidence: Project's Information Production Methods and Procedures
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
- Define the scope of production delivery · Action Statement · Verified
define the scope of production delivery
See the evidence: Define the scope of production delivery - Develop methodologies of information delivery · Action Statement · Verified
Develop methodologies of information delivery
See the evidence: Develop methodologies of information delivery - Contribute building services input to the delivery team's information delivery strategy · Action Statement · Verified
**Table 1 – Scope of documentation covered in this guidance according to EN ISO 19650-2:2018 clause reference** | | Invitation to tender EIR | Tender response pre-appointment BEP | Appointment BEP | | --- | --- | --- | --- | | In scope | 5.2.1 Appointing party’s exchange information requirements a) information requirement b) level of Information Need c) acceptance Criteria d) supporting Information e) information delivery dates | 5.3.2 Delivery team’s (pre-appointment) BIM execution plan a) info1 Scope
See the evidence: Contribute building services input to the delivery team's information delivery strategy - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- Define the scope of production delivery · Action Statement · Verified
- Define the scope of production delivery · Action Statement · Verified
define the scope of production delivery
See the evidence: Define the scope of production delivery - Develop methodologies of information delivery · Action Statement · Verified
Develop methodologies of information delivery
See the evidence: Develop methodologies of information delivery - Contribute building services input to the delivery team's information delivery strategy · Action Statement · Verified
**Table 1 – Scope of documentation covered in this guidance according to EN ISO 19650-2:2018 clause reference** | | Invitation to tender EIR | Tender response pre-appointment BEP | Appointment BEP | | --- | --- | --- | --- | | In scope | 5.2.1 Appointing party’s exchange information requirements a) information requirement b) level of Information Need c) acceptance Criteria d) supporting Information e) information delivery dates | 5.3.2 Delivery team’s (pre-appointment) BIM execution plan a) info1 Scope
See the evidence: Contribute building services input to the delivery team's information delivery strategy - BIM Execution Plan (BEP) · Information Use · Verified
The appointing party shall take account of the following, in that they are included within the completed appointment documents for the lead appointed party and managed via change control throughout the duration of the appointment: - the appointing party's exchange information requirements; - the project's information standard (including any agreed additions or amendments); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Execution pla5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.6 Complete lead appointed party's appointment documents
See the evidence: BIM Execution Plan (BEP)
- Define the scope of production delivery · Action Statement · Verified
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP)
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP) - Coordinate building services delivery dates in the task information delivery plan with the lead appointed party's master information delivery plan (MIDP) · Action Statement · Suggested – reviewSee the evidence: Coordinate building services delivery dates in the task information delivery plan with the lead appointed party's master information delivery plan (MIDP)
- Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the evidence: Master Information Delivery Plan (MIDP)
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP) - Define the scope of production delivery · Action Statement · Verified
define the scope of production delivery
See the evidence: Define the scope of production delivery - Develop methodologies of information delivery · Action Statement · Verified
Develop methodologies of information delivery
See the evidence: Develop methodologies of information delivery - Contribute building services input to the delivery team's information delivery strategy · Action Statement · Verified
**Table 1 – Scope of documentation covered in this guidance according to EN ISO 19650-2:2018 clause reference** | | Invitation to tender EIR | Tender response pre-appointment BEP | Appointment BEP | | --- | --- | --- | --- | | In scope | 5.2.1 Appointing party’s exchange information requirements a) information requirement b) level of Information Need c) acceptance Criteria d) supporting Information e) information delivery dates | 5.3.2 Delivery team’s (pre-appointment) BIM execution plan a) info1 Scope
See the evidence: Contribute building services input to the delivery team's information delivery strategy
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
Stage 5: Verify building services model containers
Consulting Design Engineer
The engineer produces services design models and verifies the information containers against the agreed exchange schema, file naming standard, and COBie asset data format before federation into the cross-disciplinary coordinated model.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 5
Verify building services model containers
- Sends 5: Building services model containers for checking to Lead appointed party (architect) (submit)
Lead appointed party (architect)
ISO 19650 party
- Receives 5: Building services model containers for checking from Consulting Design Engineer (submit)
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Appointing party (client).
Hand-offs at this stage
5Building services model containers for checking
- From
- Consulting Design Engineer
- To
- Lead appointed party (architect)
- Hand-off
- Submit
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 5 | Consulting Design Engineer | Lead appointed party (architect) | Submit | Building services model containers for checking |
Checklist
0 of 4 ticked- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format - Project's Information Standard · Information Use · Verified
The appointing party may have specified the project's information standard. For more information refer to 5.4.2 of this guidance. The prospective lead appointed party has to communicate their response to the requirements. They can accept or reject the use of the appointing party's project's information standard and suggest additions or amendments to them. Information shall be produced in line with the project's information standard to ensure successful exchange with other technologies, using ope6.7 Project's information standard
See the evidence: Project's Information Standard
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format - Cross-disciplinary coordinated model · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Cross-disciplinary coordinated model
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria - Cross-disciplinary coordinated model · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Cross-disciplinary coordinated model - Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
Stage 6: Confirm design-stage asset data acceptance
Consulting Design Engineer
The engineer verifies that building services deliverables satisfy the agreed information delivery acceptance criteria, securing sign-off from the Lead Appointed Party and preventing costly handover disputes at Construction Stage.
Responsible: Consulting Design Engineer
Who does what at this stage
Consulting Design Engineer
The role
Carries out stage 6
Confirm design-stage asset data acceptance
- Receives 6: Containers that fail checks: amend and resubmit from Lead appointed party (architect) (reject)
- Receives 7: Design-stage asset data accepted from Lead appointed party (architect) (accept)
Lead appointed party (architect)
ISO 19650 party
- Sends 6: Containers that fail checks: amend and resubmit to Consulting Design Engineer (reject)
- Sends 7: Design-stage asset data accepted to Consulting Design Engineer (accept)
Appointing party (client)
ISO 19650 party
No part in this stage.
No part in this stage: Appointing party (client).
Hand-offs at this stage
6Containers that fail checks: amend and resubmit
- From
- Lead appointed party (architect)
- To
- Consulting Design Engineer
- Hand-off
- Reject, returns to stage 5: Verify building services model containers
7Design-stage asset data accepted
- From
- Lead appointed party (architect)
- To
- Consulting Design Engineer
- Hand-off
- Accept
| No. | From | To | Hand-off | Item |
|---|---|---|---|---|
| 6 | Lead appointed party (architect) | Consulting Design Engineer | RejectReturns to stage 5: Verify building services model containers | Containers that fail checks: amend and resubmit |
| 7 | Lead appointed party (architect) | Consulting Design Engineer | Accept | Design-stage asset data accepted |
Checklist
0 of 5 ticked- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria
- Check the information container against the chosen exchange schema and data format · Action Statement · Verified
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
establish, and maintain throughout its appointment, a task information delivery plan (TIDP).5.3.1 Nominate individuals to undertake the information management function › 5.4 Information management process – Appointment › 5.4.2 Establish the delivery team's detailed responsibility matrix
See the evidence: Establish a task information delivery plan (TIDP)
- Establish a task information delivery plan (TIDP) · Action Statement · Verified
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria - Check the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Check the information container against the chosen exchange schema and data format - Verify the information container against the chosen exchange schema and data format · Action Statement · Verified
The information reviewer shall check the information container against the chosen exchange schema and data format.
See the evidence: Verify the information container against the chosen exchange schema and data format
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Clarify acceptance criteria for digital asset deliverables at each information exchange - Information delivery acceptance criteria · Information Use · Verified
| EIR reference | EIR description | Level of information need | Supporting information | Acceptance criteria | Date to be delivered/frequency | | --- | --- | --- | --- | --- | --- | | EIR-02 | Cross-disciplinary coordinated geometry | Reference to level of information need specification. (See example of level of information need Table B.8) | N/A | N/A | Bi-weekly coordination exchange. Delivery 25.09.2020. See MIDP | | EIR-03 | Cost consultant cost plan | N/A | N/A | N/A | Delivery 25.09.2020. S
See the evidence: Information delivery acceptance criteria
- Clarify acceptance criteria for digital asset deliverables at each information exchange · Action Statement · Verified
Evidence for the flow
- E1
Master Information Delivery Plan (MIDP) · Information Use · Verified
The lead appointed party shall take account of the following, in that they are included within the appointment documents for each appointed party and managed via change control throughout the duration of the appointment: - the lead appointed party's exchange information requirements; - the project's information standard (including any agreed additions or amendments) (see 5.1.4); - the project's information protocol (including any agreed additions or amendments); - the delivery team's BIM Executi5.2.1 Establish the appointing party's exchange information requirements › 5.4 Information management process – Appointment › 5.4.7 Complete appointed party's appointment documents
See the full evidence entry - E2
Identify the foreseeable trigger events for which information shall be managed · Action Statement · Verified
identify the foreseeable trigger events for which information shall be managed
See the full evidence entry
Need this flow in your own tooling? Take an editable copy. It is a one way extract, so edits will not sync back to this report.
Download editable diagramKey actions
Open an Action Statement in the Record using its link icon. Each opens in a new tab.
1 headline and 16 detailed Action Statements are recorded. 6 key detailed actions are shown here, with accepted actions first. Read all Action Statements in the Full Scenario Record (opens in a new tab)
What this role works with
Information Uses recorded for this scenario. Review their suitability for the intended organisation and project.
- 1Existing asset information and shared resources
- 2BIM Execution Plan (BEP)
- 3Project's Information Production Methods and Procedures
- 4Exchange Information Requirements (EIR)
- 5Master Information Delivery Plan (MIDP)
- 6Information delivery acceptance criteria
- 7Project's Information Standard
- 8Cross-disciplinary coordinated model
How the scenario unfolds
6 stages · 1 decision with 3 optionsOpen a stage to see its activities and decisions. Guidance links open the matching section of the Record in a new tab.
On appointment to the €14 million school extension and refurbishment, the Consulting Design Engineer reviews the template-based Exchange Information Requirements (EIR), identifying gaps in Uniclass coding, conflicting PAS 1192 and ISO 19650 terminology, and unlisted COBie maintainable assets.
Proposed responsibility: Consulting Design Engineer
How will the gaps in the EIR be resolved?
Formal clarification through the architect.
- Raise clarification requests through the architect. Raise numbered clarification requests through the Lead Appointed Party, each naming the requirement, the gap and the proposed answer.
Rejoin at Clarify governance under the CWMF mandate in the Record (opens in a new tab).
A joint workshop with the client.
- Agree the missing requirements at a joint workshop. Agree discussion points with the client and the architect at a workshop, and develop the missing requirements together.
Rejoin at Clarify governance under the CWMF mandate in the Record (opens in a new tab).
Proceed on documented assumptions.
- Proceed on documented assumptions, flagged as risks. Where answers will not come in time, proceed on stated assumptions recorded in the BEP and the risk register, so later changes can be costed.
Rejoin at Clarify governance under the CWMF mandate in the Record (opens in a new tab).
Under the CWMF BIM requirements, which apply to design teams on projects over €5 million from 1 July 2026, the engineer issues structured clarification requests through the Lead Appointed Party and agrees the governance points that the EIR leaves open.
Proposed responsibility: Consulting Design Engineer
Read practical guidance for Clarify governance under the CWMF mandate (opens in a new tab)
The engineer collaborates with the Lead Appointed Party and client to establish an information delivery strategy, defining building services Level of Information Need, Uniclass tables, and exchange schemas.
Proposed responsibility: Consulting Design Engineer
Read practical guidance for Agree building services Level of Information Need (opens in a new tab)
The engineer contributes the building services response to the BIM Execution Plan and formulates the MEP Task Information Delivery Plan (TIDP), defining the scope of production delivery and aligning milestone exchange dates with the Lead Appointed Party's Master Information Delivery Plan (MIDP).
Proposed responsibility: Consulting Design Engineer
Read practical guidance for Contribute building services to the BEP and TIDP (opens in a new tab)
The engineer produces services design models and verifies the information containers against the agreed exchange schema, file naming standard, and COBie asset data format before federation into the cross-disciplinary coordinated model.
Proposed responsibility: Consulting Design Engineer
Read practical guidance for Verify building services model containers (opens in a new tab)
The engineer verifies that building services deliverables satisfy the agreed information delivery acceptance criteria, securing sign-off from the Lead Appointed Party and preventing costly handover disputes at Construction Stage.
Proposed responsibility: Consulting Design Engineer
Read practical guidance for Confirm design-stage asset data acceptance (opens in a new tab)
Does the mandate apply?
Ireland – CWMF / Public Works. Applies
Design team (lead appointed / appointed parties) on a public works project: the CWMF milestone in force at the 22/10/2026 commencement (over €5m, effective 01/07/2026) covers this project.
Source: CWMF – Public Sector BIM Adoption Timeline. https://cwmf.gov.ie/en/resources/bim/public-sector-bim-adoption-timeline/
Build Digital materials
The material selection and source metadata recorded for this issue. Proposed uses explain how each material supports the workflow; source availability may change.
Supporting materials
This project information standard provides spreadsheet templates and guidance for naming project information in accordance with the Irish National Annex to ISO 19650-2. The support includes the core file-naming workbook, a hyperlink checker, a presentation and a demonstration.
Standard · XLSX
Provide standard spreadsheet templates and rules for information container naming in line with the Irish National Annex to ISO 19650-2.
Directly resolves the scenario requirement where project-specific file naming, container, and code requirements were missing, ensuring building services containers are compliant before issue.
Included resources
- Project Information Standard – File Naming · primary · XLSX
BD-MAT-3093 · Source revision f3c82554ee73f2db7a730a64ee511aa2d002510d36418243848f00bee156214a
- Check the information container against the chosen exchange schema and data format
- Verify the information container against the chosen exchange schema and data format
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
This delivery-team information management plan provides tenderers with a structured set of templates for responding to a project tender in line with ISO 19650. It covers the delivery team’s information-management function, delivery strategy objectives, federation approach, responsibilities, acceptance criteria, capability, mobilisation and risk planning.
Plan · XLSX
Offer structured templates for delivery-team information management planning, TIDP formulation, and acceptance criteria.
Supports the engineer in establishing an MEP task information delivery plan and formalizing acceptance criteria and delivery strategies when the client EIR is sparse.
Included resources
- Information Management Plan – Delivery Team · primary · XLSX
BD-MAT-3121 · Source revision db789419d913153580cb910c037258fcbf872dafd37dcea0d40bca035b865374
- Clarify acceptance criteria for digital asset deliverables at each information exchange
- Coordinate building services delivery dates in the task information delivery plan with the lead appointed party's master information delivery plan (MIDP)
- Define the scope of production delivery
- Develop methodologies of information delivery
- Contribute building services input to the delivery team's information delivery strategy
- Establish a task information delivery plan (TIDP)
This support presents the CWMF-to-ISO 19650-2 process workflows, including the Stage (i) feasibility study and preliminary report workflow. It is published as a single PDF support for information-management activities across appointing and appointed parties.
Workflow · PDF
Clarify the alignment between CWMF procurement stages and ISO 19650-2 delivery workflows.
Gives the engineer procedural authority to align the governance clarification steps under the CWMF mandate and the milestone exchanges with Irish public sector process standards.
Included resources
- Process Workflows CWMF to ISO 19650-2 · primary · PDF
BD-MAT-3134 · Source revision 099ea73d72c1bff960041a4c46f4926277c1ebf1c4af142aefa52b661fedde73
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps
- Identify changes that need to be made to the project’s information production methods and procedures
Guidance for applying Uniclass within Irish BIM mandate and project-delivery requirements.
Guide · PDF
Provide specific guidance for adopting and implementing Uniclass classification within Irish public projects under the CWMF BIM mandate.
Resolves the scenario problem where Uniclass was required by the EIR without specifying appropriate tables or application strategies for building services.
BD-MAT-3875 · Source revision 71f4db228cc803bf2d1fc1fda445fdffb1ae14abe2efe8cff1e072145352236b
- Review the Appointing Party's exchange information requirements for internal contradictions and gaps
- Propose additions and amendments to the project's information standard to clarify building services classification and property parameters, to the lead appointed party for inclusion in the delivery team's response
- Propose and agree the level of information need for building services elements at each design stage
Technical guidance for implementing exchange information requirements and BIM execution plans.
Guide · PDF
Supply technical implementation guidance for formulating exchange information requirements and responding via BIM execution plans.
Assists the engineer and LAP in structuring additions and amendments to the BEP and project information production methods.
BD-MAT-3265 · Source revision 87e6a518efbf6d81f7ff5eb871565b1b50e421c751902d875effedc8d2edae7d
- Clarify the exchange information requirements (EIR) of the Appointing Party and the Lead Appointed Party
- Develop methodologies of information delivery
- Contribute building services input to the delivery team's information delivery strategy
- Propose additions and amendments to the project's information production methods and procedures to the lead appointed party for inclusion in the delivery team's response
Landing page for the nine-lesson first-party guide to IFC concepts and principles.
Guide · HTML
Guide open data exchange and IFC principles across building services disciplines.
Ensures the consulting engineer can verify open standard data containers and IFC schema exports in accordance with defined project exchange criteria.
BD-MAT-3277 · Source revision 1ae489af18f778ec64cea407b9e2049c95de13c963efefc838c96829c4fa1233