Employer's information requirements (EIR)

The Employer's Information Requirements (EIR) outlines technical and commercial particulars that must be addressed throughout the project's lifecycle.

/live_board/v2/downloads?uid=bc5c1af4-d240-4697-bf4c-8cef3169f001&redirect=true

EMPLOYER’S INFORMATION REQUIREMENTS (EIR) Acceleration to Digital Excellence in Construction

EMPLOYER’S INFORMATION REQUIREMENT

This template is designed for you to personalize with your project’s unique details. Simply replace

the placeholders with your information, such as ‘Project Name’, ‘Project Type’ (like construction or

infrastructure development), and ‘Location’ (country or region). It’s quick, easy, and ensures that

all your project specifics are captured accurately.

CONTENTS TABLE OF

.INTRODUCTION 06

.PURPOSE 06

.PROJECT INFORMATION (GENERAL) 08

.STRUCTURE 09

.OTHER’S RESPONSIBILITY TOWARDS EIR 12

.BIM OBJECTIVES 14

.INFORMATION REQUIREMENTS 18

.EXCHANGES OF INFORMATION 18

.INFORMATION DELIVERY PLAN 23

.LEVEL OF DEFINITION, DETAIL AND INFORMATION

.CLASSIFICATION 26

.HEALTH & SAFETY AND CONSTRUC- TION DESIGN MANAGEMENT

.APPLICABLE STANDARDS 29

.INFORMATION MANAGEMENT ROLES & RESPONSIBILITIES

.COLLABORATION PROCESS 32

EMPLOYER’S INFORMATION REQUIREMENT

This template is designed for you to personalize with your project’s unique details. Simply replace

the placeholders with your information, such as ‘Project Name’, ‘Project Type’ (like construction or

infrastructure development), and ‘Location’ (country or region). It’s quick, easy, and ensures that

all your project specifics are captured accurately.

TABLE OF

CONTENTS

.PLANNING THE WORK AND DATA SEGREGATION 34

.SECURITY 36

.COORDINATION AND CLASH PREVENTION 37

.COMPLIANCE PLAN 39

.DELIVERY STRATEGY FOR ASSET INFORMATION 36

.TRAINING 39

.TECHNICAL 44

.SOFTWARE PLATFORMS 44

.SYSTEM PERFORMANCE 44

.DATA EXCHANGE FORMAT 45

.COORDINATES 46

.COMMERCIAL 45

.BIM EXECUTION PLAN 47

.BIM SPECIFIC COMPETENCE REQUIREMENTS 47

.PRODUCTION, OWNERSHIP AND USE OF THE MODELS

1. INTRODUCTION

1.1 PURPOSE This document confirms the Employer’s Information Requirements (EIR) within the broader context of the Employer’s Requirements or any equivalent contract documentation. It is designed to acquaint the Project Team of [Insert Project Name] or Supplier with the essential information requirements, the rationale behind these requirements, and the overarching purpose of facilitating the effective imple- mentation of Building Information Modelling (BIM).

INTRODUCTION TO INFORMATION REQUIREMENTS

The EIR outlines both technical and commercial particulars that must be addressed throughout the project’s lifecycle. These requirements encompass a comprehensive array of data, models, and docu- ments, all vital for the successful execution of BIM within the project.

INTEGRATION WITH PROJECT PHASES

The EIR is a foundational element of the Project BIM Implementation strategy. It plays a pivotal role in elucidating, to the Project Team or Supplier, the precise nature of information (including models, doc- uments, and data) expected at various stages of the project. These stages are delineated through the development of a stage-based Information Delivery Plan (IDP).

1. INTRODUCTION

Figure 1: Define Project BIM Standards for AEC Projects (According to the ISO 19650 Series), Source: Autodesk Customer Success

Hub

RESPONSIBILITY AND COMPLIANCE

It is essential to emphasize that the existence of this document does not absolve the Project Team, including Consultants, the Contractor, or its Specialists, of their responsibility to adhere to Project standards. This encompasses compliance with procedures related to the eventual handover of the com- pleted project. Please see Appendix A of this document for a RACI based responsibilities matrix sample.

FINAL DELIVERABLES AND BIM EXECUTION PLAN (BEP)

Specifics regarding deliverables from both consultants and contractors will be elaborated upon in the mutually agreed-upon project BIM Execution Plan (BEP). This BEP will serve as the guiding document for the production and delivery of a Project Information Model, which aligns precisely with the project’s unique requirements

PROJECT INFORMATION MODEL AS THE END PRODUCT

Central to the BIM methodology is the notion that the Project Information Model represents the ulti- mate deliverable from the supply chain. This goes beyond the physical asset itself and encompasses a comprehensive digital representation that is not only invaluable during the construction phase but also significantly enhances the asset’s lifecycle management.

1.2 PROJECT INFORMATION (GENERAL)

Employer [Insert Employer Name]

Project Name [Insert Project Name]

Project Description The [Insert Project Name] is a significant construction project situated in [city or region], [country]. This project represents a comprehensive [describe the nature of the project, e.g., infrastructure development, industrial facility, commercial complex] designed to [briefly explain the project’s purpose and objectives, e.g., meet growing demand, enhance operational efficiency, etc.].

Address (office, site)

Other

1. INTRODUCTION

Amus. Parum id entur,

90% 50%

RESPONSIBILITIES

REQUIREMENTS AND PROCESSES In this segment, the specific requirements for information deliverables are defined in detail.

It provides clarity on what data, models, documents, and other assets are expected, as well as

the processes and workflows necessary to create and manage them effectively.

METHODS AND PROTOCOLS This section elucidates the methodologies, standards, and protocols that must be followed

during the creation and exchange of information. It ensures consistency and compatibility

throughout the project.

1.3 STRUCTURE The foundation of the project’s information management strategy is built upon the Client’s definition of their Information Requirements, which are encapsulated within the Employer’s Information Requirements (EIR). It encompasses a wide spectrum of information delivera- bles, which encompasses not only digital models but also conventional project documents, surveys, reports, and appraisals as mandated by the Client. These have clearer definition in publishing processes under section 3.4.

This section delineates the roles and responsibilities of various stakeholders within the project

concerning the generation and management of project information. It specifies who is ac-

countable for producing, reviewing, and approving the information deliverables. Please see

Appendix A of this document for a RACI based responsibilities matrix sample.

RELEVANT BUSINESS PROCESSES Here, the document addresses how the information requirements align with the overarching

business processes of the project and the Client’s goals. It underscores the integration of in-

formation management into the project’s broader context.

SUPPORTING SOFTWARE REQUIREMENTS This section specifies the software tools and platforms required for the creation, management,

and exchange of information. It ensures that the Project Team or Supplier employs the appro-

priate technology stack to fulfil the Client’s Information Requirements.

Discipline / Scope Software Selection Responsibility Software Name

Architectural Design [Specify Responsibility Party] Revit 2024

S t r u c t u r a l E n g i n e e r i n g [Specify Responsibility Party] Advance Steel

MEP Engineering [Specify Responsibility Party] Revit 2024

Interior Design [Specify Responsibility Party] AEC Collection

Civil Engineering [Specify Responsibility Party] Civil 3D

P r o j e c t M a n a g e m e n t [Specify Responsibility Party] ACC Build

Cost Estimation [Specify Responsibility Party] ACC Build (Cost Management)

Energy Analysis [Specify Responsibility Party] Insight

3D Visualization [Specify Responsibility Party] Navisworks

F a c i l i t y M a n a g e m e n t [Specify Responsibility Party] Tandem

Field Progress T r a c k i n g [Specify Responsibility Party] ACC Build

1. INTRODUCTION

INFORMATION DELIVERY PLAN (IDP)

The Information Delivery Plan (IDP) serves as a roadmap for the execution of the Client’s Information Requirements. It is typically drafted by the Client or their designated rep- resentative and must be adhered to by the Project Team or Supplier. The IDP serves as the cornerstone upon which the Task Information Delivery Plans and subsequent Master Information Delivery Plan are built. The progression of this information throughout the project’s lifecycle is commonly referred to as the Digital Plan of Works. These have clearer definition in publishing processes under section 3.4.

WITHIN THE IDP, YOU WILL FIND:

TASKS AND INFORMATION DELIVERABLES

o This section itemizes the specific tasks and associated information deliverables required at different project stages. It provides a clear, stage-by-stage breakdown of what is expected from the Project Team or Supplier.

LEVEL OF DEFINITION FOR EACH DELIVERABLE

o Here, the IDP defines the Level of Detail (LOD) and Level of Information (LOI) ex- pected for each deliverable. It clarifies the depth and granularity of information required, ensuring alignment with project goals.

THE INTENDED ROLE OR APPOINTED SUPPLIER o This section specifies who is responsible for generating each information deliv- erable. It designates the intended role or appointed supplier for each task, ensuring ac- countability and clarity within the project team.

1. INTRODUCTION

1.4 OTHERS’ RESPONSIBILITY TOWARDS EIR

RESPONSE THROUGH BIM EXECUTION PLANS (BEPs)

ACKNOWLEDGMENT AND ALIGNMENT

The Project Team and Suppliers bear the responsibility of translating the Client’s vision, as articulated in the EIR, into a practical and achievable plan through their BIM Execution Plans (BEPs). These plans not only serve as a blueprint for action but also form the basis for evaluation and progress measure- ment, ensuring that the project stays on course to meet its BIM objectives.

The EIR should not remain a static document but must be dynamic and actionable. Therefore, the Project Team or Suppliers are tasked with responding to and implementing the EIR through the creation of their BIM Execution Plans (BEPs). These BEPs serve as a bridge between the project’s overarching goals, as defined by the EIR, and the practical steps required to achieve them.

CLARITY AND REFERENCING In their BEPs, the Project Team or Suppliers must provide clear references to each section of the EIR. This ensures that the EIR’s directives are explicitly addressed and incorporated into the project’s execution plan. The BEPs should serve as a detailed roadmap for translating EIR requirements into actionable tasks.

COMPREHENSIVE CONSIDERATION The BEP is a comprehensive document that must carefully consider and respond to eight critical headings outlined below. It should also take into account the underlying BIM maturity Key Performance Indicator (KPI) measures where applicable:

BIM EXECUTION PLAN (BEP) REQUIREMENTS

FigurE 2: A Level 2 BIM Maturity-KPI assessment conceptual framework. Source: ID 122 A BIM MATURITY-KPI ASSESSMENT: LIT-

ERATURE REVIEW - Scientific Figure on ResearchGate.

BIM MATURITY KPI MEASURES 1. BIM Procurement / Employer Engagement 2. BIM Delivery 3. Data, Verification and Validation 4. Collaborative Working 5. Visualization / Stakeholder Engagement 6. Discipline-Based Model Authoring 7. Construction 8. Model-Based Estimating and Change Management

MINIMUM BEP CONTENT The BEP, as a minimum, should include the following key elements: • Project Information Model Delivery Strategy: A well-defined strategy for delivering the Project Informa- tion Model in alignment with the project’s goals and EIR requirements.

TENDER COMPLIANCE AND BEYOND A compliant BEP submitted in response to a project tender will be evaluated to assess how it addresses the re- quirements of each section of this EIR. The BEP’s alignment with the EIR will be a fundamental part of the tender scoring system, utilizing BIM Maturity KPIs. These measures will continue to be used consistently throughout the life of the project, extending into the handover phase. Please see the sample BIM Assessment Form in the Appen- dix B of this document.

1.5 BIM OBJECTIVES The Employer’s BIM vision and objectives underscore its commitment to achieving BIM and leveraging BIM meth- odologies to enhance project outcomes, optimize resource allocation, improve safety and security, and facilitate informed decision-making throughout the project’s life cycle. These objectives serve as a guiding framework for the integration of BIM into the project’s core processes and are integral to its overall success.

1. INTRODUCTION

• Response to Each Section of the EIR: A comprehensive response to every section of the EIR, as indicated by BEP guidance notes, demonstrating how the EIR’s directives will be fulfilled. • Specific Response to the IDP: Confirmation of the capability to deliver information requirements as out- lined in the Information Delivery Plan (IDP), ensuring adherence to the requested format and the correct Level of Information (LOI). • Project Goals for Collaboration and Information Modeling and Management: Clear articulation of the proj- ect’s objectives regarding collaboration and information modeling and management, aligning with the overarch- ing project vision. • Major Project Milestones: Identification of significant project milestones that are consistent with the construction program and the Information Delivery Plan (IDP). These milestones serve as markers of progress and ensure alignment with project timelines. • Comments on Over/Under Specifications: Where deliverables are either over or under-specified, or if it is deemed impractical to deliver as specified, alternative delivery proposals should be provided with clear justifica- tions.

Figure 3: Quality Assurance in Data Flow

COMMITMENT TO BIM

ELEVATING PROJECT OUTCOMES

The Employer’s unwavering commitment to attaining BIM reflects its dedication to elevating project outcomes. BIM is seen as a catalyst for enhanced collaboration, information management, and decision- making, resulting in significant improvements in project efficiency and quality.

APPLICATION OF BIM FOR ENHANCED PROJECT LIFECYCLE MANAGEMENT

STRUCTURED DATA TRANSFER AND COORDINATION

One of the primary objectives of BIM implementation is to improve the structured transfer of data, its availability, and coordination throughout the project’s life cycle. This encompasses the design and construction phases, as well as the critical handover into operations and occupancy. The integration of Computer-Aided Facility Manage- ment (CAFM), building control, monitoring, and management systems is also a key component of this objective.

OBJECTIVES OF EIR IN RELATION TO LIFECYCLE MANAGEMENT

BIM’s role extends beyond the construction phase. It is intended to facilitate the availability of critical information for lifecycle costing and investment planning. This ensures that decisions regarding maintenance, upgrades, and asset management are well-informed and aligned with the project’s long-term objectives.

KEY OBJECTIVES

The Employer has identified a set of key objectives that are central to its BIM vision:

DELIVER VALIDATED, VERIFIED, AND STRUCTURED INFORMATION

The first objective is to deliver information and data that are validated, verified, and structured. This data should be readily shareable across design teams, supporting project stage gate decisions, engaging project stakeholders, and integrating data repositories for Operations and Maintenance (O&M) manuals, Health and Safety (H&S) files, and Asset Information. The overall validation process encompasses four main areas: evaluating modeling attributes and procedures, con- ducting clash detection, checking code compliance, and verifying adherence to relevant regulations.

POPULATE THE EMPLOYER’S ASSET INFORMATION MODEL

The second objective is to deliver the project into the Employer’s Asset Information Model. This involves pop- ulating operational and line of business systems that will support strategic, operational, and asset manage- ment decision-making following the practical completion of construction works and installations. Detailed formats will be referenced in the AIR document.

AUTHORIZE MAIN CONTRACTOR’S TECHNICAL DESIGN USING BIM TOOLS

This objective emphasizes the use of BIM tools to authorize the Main Contractor’s Technical Design, ensuring that BIM is integrated into the design and construction phases effectively.

UNDERSTAND AND CONFIRM PROGRAM, SEQUENCE, AND LOGISTICS IMPLICATIONS

Using BIM tools, the Employer seeks to gain a comprehensive understanding of program, sequence, and logistics implications, including future Planned Preventive Maintenance (PPM) requirements.

FORM THE BASIS FOR POST-OPERATIONAL PERFORMANCE EVALUATION

BIM tools will serve as the foundation for post-operational performance evaluation and continuous learning, en- abling the refinement of future projects based on data-driven insights.

1. INTRODUCTION

BIM tools will be employed to assess and address safety and security issues comprehensively, enhancing overall project safety.

ASSESS AND ADDRESS SAFETY AND SECURITY ISSUES

Using BIM tools, the project scope will be rigorously compared against briefing requirements, ensuring alignment with the initial project vision.

The final objective is to consolidate all individual repositories and building information into a single repository. This unified approach ensures the correct drawing is accessed when needed and enforces proper change and access control.

CHECK PROPOSED SCOPE AGAINST BRIEFING REQUIREMENTS

CONSLIDATED BUILDING INFORMATION INTO A SINGLE REPOSITORY

This section outlines the crucial details regarding the timing, content, and alignment of information exchanges between the Project Team/Supplier and the Employer. It also specifies how these exchanges correspond to the various work stages of the project. Information flow may occur bidirectionally to facilitate efficient collaboration.

Information exchanges will adhere to the guidelines set forth in the RIBA Plan of Work. The responsibility for de- fining these exchanges lies with the Supplier and will be documented in the BIM Execution Plan (BEP).

The exchanges will align with the following project stages: • Stage 1: Preparation and Brief • Stage 2: Concept Design • Stage 3: Developed Design • Stage 4: Technical Design • Stage 5: Construction • Stage 6: Handover • Stage 7: In Use

2. INFORMATION REQUIREMENTS

2.1 EXCHANGES OF INFORMATION Sales PlacesPerson

RIBA PLAN OF WORK ALIGNMENT

2.1.1 TIMING AND ALIGNMENT WITH RIBA PLAN OF WORK

Figure 4: RIBA OUTLINE PLAN OF WORK (RIBA 2007)

OUR STATISTICS

ADDITIONAL INFORMATION EXCHANGE

Any requirement for additional Information Exchanges beyond those established in the RIBA Plan of Work should be explicitly stated within Information Delivery Plan (IDP), providing a clear roadmap for the project’s information exchange needs.

2.1.2 FORMAL PUBLISHED INFORMATION DELIVERABLES

While information can be shared at any time during a stage, formal published information deliverables must be ex- changed before the conclusion of a stage. This timely exchange ensures that critical decision gateways, as outlined in the project IDP, can be informed and executed efficiently. These have clearer definition in publishing processes under section 3.4.

2. INFORMATION REQUIREMENTS

Information deliverables required at each information exchange will be as defined by the project IDP. These de- liverables must comply with any standards referenced or defined by the project BIM Execution Plan (BEP). The formats may include: • 3D Geometry Models – Native to authoring tool, unfederated. • 3D Geometry Models – Open standard IFCXxX, unfederated. • 2D Drawings – All 2D drawings, whether PDF or DWG format must be generated from the 3D authoring software such as Revit and other software referred to in section 1.3. • Structured data – BIM model needs to delivered with the COBie data embedded. • Structured data – Digital Project handover that includes the BIM models with a path to Digital twin using Autodesk Tandem

2.1.3 INFORMATION DELIVERABLES FORMATS

COMPLIANT WITH PROJECT STANDARDS

When new project works interface with existing built assets owned and operated by Owner, such as refurbishment works to existing buildings, the appointed contractor is responsible for incorporating legacy asset information with the new works as required. The format and delivery of this information must be discussed further with the Owner or an appointed representative on a project-specific basis. This ensures that the level of detail and format of information collected aligns with its intended use. The following activities will typically be required unless otherwise specified: • Surveying existing/legacy built assets, including laser scanning if necessary (e.g., when 3D modeling is not feasible using existing drawings/asset information). • 3D modeling of building systems for existing/legacy assets that will be linked to or affected by new works. This includes all floor, ceiling, and wall-mounted plant and accessories, as well as all plant and riser spaces. • Production of drawings in PDF and DWG format.

2.1.4 INTERFACE WITH EXISTING BUILT ASSETS

9. Accessibility: It’s accessible through digital platforms, making it user-friendly and easy to implement. 10. Industry Adoption: It is widely adopted in the UK’s facilities management sector, promoting consistency and professionalism in building maintenance. • Adherence to code of practice for facilities management: • It is a standard guiding facilities management (FM) during the design and construction phases of a building’s lifecycle:

• Production of structured data, derived from models or other sources, in compliance with Standard that focus- es on the collaborative production of information during the construction phase of a building project. It provides guidelines for the structure and naming of electronic information exchanged between parties involved in the con- struction process, emphasizing consistency and clarity in data organization. The standard outlines requirements for information exchanges, including file naming conventions, data structures, and metadata, ensuring that digital information is well-organized and easily accessible by project stakeholders. It aims to facilitate efficient data shar- ing, reduce errors, and improve collaboration among construction professionals, ultimately contributing to more streamlined project delivery.

The information delivered to Owner must be in the required format and data structure to enable the Employer to effec- tively manage and operate their assets. This includes: • Compliance with maintenance standards: • It is a comprehensive maintenance standards framework used in facilities management. It provides standard- ized guidance for maintaining various building assets, equipment, and systems: 1. Scope: Covers a wide range of building assets, including HVAC systems, electrical equipment, and plumbing. 2. Standardization: It offers standardized maintenance schedules and procedures to ensure consistent and effi- cient maintenance practices. 3. Categories: Categorizes maintenance tasks into codes, making it easy to identify specific tasks for different systems. 4. Compliance: Helps organizations comply with legal requirements and industry regulations related to building maintenance. 5. Flexibility: Users can tailor maintenance schedules to match the specific needs of their facilities. 6. Cost-Efficiency: It promotes cost-effective maintenance by reducing the risk of unexpected breakdowns. 7. Benchmarking: Allows organizations to benchmark their maintenance practices against industry standards. 8. Updates: The standards are regularly updated to incorporate changes in technology and best practices.

2.1.5 ASSET INFORMATION DELIVERY

2. INFORMATION REQUIREMENTS

1. Scope: Outlines principles for FM professionals and stakeholders involved in building design and con- struction. 2. Lifecycle Focus: It emphasizes the importance of considering FM needs throughout the entire building lifecycle. 3. Collaboration: The standard promotes collaboration between design, construction, and FM teams to en- hance building performance. 4. Information Requirements: It specifies information requirements, including asset data and documenta- tion, for seamless transition from construction to FM. 5. Roles and Responsibilities: Clarifies the roles and responsibilities of different parties involved in FM planning. 6. Cost Savings: The standard helps reduce FM costs by addressing maintenance needs at the design and construction stages. 7. Sustainability: It supports sustainability objectives by considering energy efficiency and environmental impacts. 8. Continuous Improvement: Encourages ongoing performance evaluation and improvement of building assets. 9. Adaptability: The standard accommodates changes in building use and occupancy over time. 10. Industry Application: Widely used and contributes to more effective FM practices and better building performance throughout its lifecycle. • Production of digital O&M manuals, inclusive of required health and safety (H&S) information: • The production of digital Operation and Maintenance (O&M) manuals, including mandatory health and safety (H&S) information, is essential for effective facility management and safety compliance: 1. Documentation Compilation: Digital O&M manuals compile crucial documentation related to building assets and systems. 2. Accessibility: Digital formats enhance accessibility and ease of reference for maintenance personnel. 3. Comprehensive Information: These manuals provide comprehensive information on equipment, mainte- nance procedures, and safety protocols. 4. Asset Management: They support efficient asset management, helping facilities run smoothly. 5. Legal Compliance: Inclusion of H&S information ensures legal compliance and safeguards against acci- dents. 6. User-Friendly: Digital manuals are user-friendly, offering easy navigation and search functions. 7. Timely Updates: Digital formats facilitate timely updates to reflect changes in equipment or regulations. 8. Remote Access: They enable remote access to critical information for quick decision-making. 9. Training Tool: Digital O&M manuals can serve as valuable training tools for maintenance staff. 10. Overall Efficiency: These manuals contribute to the overall efficiency, safety, and longevity of building assets.

In essence, this section outlines the systematic approach to information exchanges and project deliverables, en- suring that the right information is exchanged at the right time and in the appropriate format to support effective project management, collaboration, and long-term asset management. For more information please refer to AIR document

This section outlines the key aspects of the IDP, its relationship with the Employer’s Information Requirements (EIR), and the details it should encompass. It also highlights the importance of meeting key performance indica- tors (KPIs) related to information delivery. These have clearer definition in publishing processes under section 3.4, Here’s a summarized version: 1. IDP Creation: Owner or a designated representative will create a project-specific Information Delivery Plan. This plan is closely linked to the EIR and serves as the tool for managing information delivery. 2. Review and Confirmation: The Design Team or Supplier must review the IDP and confirm their capac- ity to provide information as per the plan’s requirements. This involves assessing the resources, formats, and stage-specific decision gates. 3. Foundation for Master Plan: The IDP is intended to serve as the foundation for the Supplier’s Master Information Delivery Plan. It guides the preparation and submission of information to the Employer at the appro- priate stages of the project. 4. IDP Contents: The IDP includes the following components:

• A list of information deliverables to address the Employer’s ‘Plain Language Questions.’ • Specifications for format, constraints, or scope for each deliverable. • Definition of the Level of Detail (LOD) and Level of Information (LOI) required for each deliverable. • Identification of the intended role or appointed supplier for each information deliverable. • Handling of sensitive information, including any specific security requirements.

5. KPI Alignment: The IDP should align with key performance indicators (KPIs) related to information deliv- ery, ensuring that the project meets specified performance goals. • KPI 1 (Addressing Employers’ ‘Plain Language Questions’): This KPI measures the project’s ability to pro- vide information deliverables that effectively answer specific queries posed by the employer or stakeholders. It is calculated by evaluating the completeness, relevance, and accuracy of the provided information in response to these questions, typically through scoring or grading of individual deliverables and aggregating the results to determine an overall performance score. • KPI 2 (Specifying Level of Information - LOI): This KPI assesses the project’s adherence to specified Level of Information (LOI) requirements, particularly in terms of COBie data at different work stages. Calculation in- volves verifying that the delivered information aligns with the required LOI standards and guidelines.

2.2 INFORMATION DELIVERY PLAN

2. INFORMATION REQUIREMENTS • KPI 3 (Defining Format Requirements, Constraints, or Scope): This KPI evaluates how well the project defines and adheres to format requirements, constraints, or scope for each information deliverable. Calcula- tion focuses on ensuring that the delivered information complies with the established criteria. • KPI 4 (Identifying Intended Role or Appointed Supplier): This KPI measures the project’s success in identifying and assigning the intended role or appointed supplier for each information deliverable. Calculation involves confirming that the responsible party for delivering each piece of information is clearly designated. • KPI 5 (Supporting CDM Regulations via BIM Approach): This KPI assesses how well the project sup- ports obligations under the Construction (Design and Management) Regulations by implementing a BIM ap- proach, especially concerning Health & Safety (H&S) and Construction Design Management (CDM) require- ments. Calculation involves evaluating the effectiveness of BIM in fulfilling these obligations and ensuring compliance.

This section underscores the significance of a well-defined IDP in guiding information delivery throughout the project and ensuring adherence to performance metrics and security requirements.

2.3 LEVEL OF DEFINITION, DETAIL AND INFORMATION The “Level of Definition; Detail and Information” section provides clarification on the terms Level of Detail (LOD) and Level of Information (LOI) as they relate to model objects within the project. It also outlines the guidance and considerations regarding these levels. Here’s a summarized version: 1. Definition of Level of Definition (LOD): The term “Level of Definition” encompasses both Level of Detail (LOD) and Level of Information (LOI) for a model object. It communicates the expected level of development for model objects at a specific project stage. 2. LOD and LOI Explanation: LOD pertains to the geometric aspects of an element, focusing on its visual representation and geometry. LOI, on the other hand

· LOD 100: Modeled elements are at a conceptual point of development. Information can be conveyed with massing forms, written narratives, and 2D symbols.

· LOD 200: Modeled elements have approximate relationships to quantities, size, location, and orientation. Some information may still be conveyed with written narratives.

· LOD 300: Modeled elements are explained in terms of specific systems, quantities, size, shape, location, and orientation.

· LOD 400: Continuation of LOD 300 with enough information added to facilitate fabrication, assembly, and installation.

· LOD 500: Modeled elements are representative of as installed conditions and can be utilized for ongoing facilities management.

Source: Project Phases & Level of Development, Autodesk Support

, relates to the associated information, encompassing non-geometric data such as specifications, perfor- mance details, and metadata. 3. Guidance for LOI: The following link provides guidance on the necessary LOI for each model object, particularly concerning COBie data requirements, at various work stages: https://interoperabili- ty.autodesk.com/cobieextension/downloads/SampleCOBieSpreadsheet.xlsx. The Excel sheet needs to be looked at in conjunction with the below figure 5.

Figure 5: Information Requirements Placements

This ensures that the right level of information accompanies each model object. 4. Maximum LOD and LOI for Sensitive Assets: For sensitive assets and systems, the maximum expected levels of LOD and LOI are specified at each work stage. These specifications align with the requirements outlined in the Built Asset Security Information Requirements (BASIR). This ensures the appropriate handling and protection of sensitive asset information, as indicated by relevant KPIs.

This section provides essential guidance on LOD and LOI, ensuring that model objects are appropriately defined, documented, and secured, particularly in cases involving sensitive assets and systems.

2.4 CLASSIFICATION 1. Classification Adoption: The Project and its supply chain partners aim to use Classification, a universal classification system in construction, for categorizing geometry model objects and project documentation. The system is widely embraced in the industry for its uniformity. 2. Reference to Project Requirements: Specific requirements related to Classification adoption are de- tailed for this the project.

Figure 6: Standardize Data Tool for Revit

An example of the LOI and LOD requirements of Dubai Building Permits department can be found in Appendix C (4-EIR Appendix C - Government of Dubai - Appendix A Model Element Matrix.pdf)

Figure 6: Standardize Data Tool for Revit

3. Element References: Element references may also be assigned to modeled components. These refer- ences aid in cost estimating and cost planning for capital building works. They follow standards that adopts Rules of Measurement, which is a comprehensive standard used in the construction industry for the mea- surement and quantification of building works. It provides a structured framework for estimating and cost planning by categorizing construction elements and work items, allowing for consistent measurement and pricing. It also offers guidelines for organizing and classifying elements, sub-elements, and cost items within a construction project, aiding in the accurate assessment of construction costs. This standard plays a crucial role in facilitating cost management, budgeting, and procurement processes in the construction sector, ensuring clarity and consistency in measurement practices.

This section emphasizes the utilization of standardized classification systems to ensure consistency and clarity in categorizing model objects and project documentation. Additionally, it highlights the use of element refer- ences for cost-related purposes when necessary.

For more information about standardization and classification in Revit, click here.

2.5 HEALTH & SAFETY AND CONSTRUCTION DESIGN MAN- AGEMENT The “Health & Safety and Construction Design Management” section addresses the integration of Building In- formation Management (BIM) principles and digital technologies to enhance safety and compliance through- out the project lifecycle. Here’s a summarized version:

1. BIM’s Collaborative Approach: BIM, or Building Information Management, represents a collaborative approach that leverages digital technologies to improve the efficiency of designing, delivering, and maintain- ing physical built assets. 2. H&S and CDM Information: Information related to Health & Safety (H&S) and Construction Design Management (CDM) is specified in the Information Delivery Plan. It plays a crucial role in managing both the Employer’s and Supplier’s H&S/CDM obligations. 3. BIM Support for Regulations: Suppliers must confirm how they will use a BIM approach to support their obligations under the Construction (Design and Management) Regulations. This alignment is tracked as Key Performance Indicator (KPI 5).

2. INFORMATION REQUIREMENTS

4. External References: Publicly Available Specification that focuses on Health and Safety (H&S) information requirements within the context of Building Information Modeling (BIM) for construction projects. It provides guidelines for embedding H&S-related data into digital models, enabling better risk management throughout the project’s lifecycle, from design and construction to operation and maintenance. It emphasizes the integration of H&S information into BIM processes and models, pro- moting safer construction practices and enhancing the health and safety management of built assets. It serves as a valuable reference for ensuring that H&S considerations are effectively addressed within the BIM framework.

5. Embedding H&S Information: H&S information provided by the Supplier should be embedded within the digital models, ensuring compatibility with The Project Health and Safety File format as per Regulations, These are a set of health and safety regulations that apply to construction projects. These regulations aim to improve the overall management of health, safety, and welfare throughout all phases of construction projects, from planning and design to construction and maintenance. Key aspects of Regulations include the appointment of competent duty holders, risk assessment, commu- nication and cooperation among project stakeholders, and the development of a Health and Safety File. The regulations prioritize the identification and mitigation of health and safety risks, ensuring that construction work is carried out safely and that the well-being of workers and the public is protected.

Figure 7: Main causes of worker fatalities in construction. (HSE) Source: BIM for Health and Safety in Construction, https://www.autodesk.

com/autodesk-university/de/node/610

6. Consideration of BIM Safety Software: The use of BIM Safety Software to manage H&S risks throughout the design, construction, operation, and maintenance phases, should be considered to en- sure effective H&S risk management.

3. MANAGEMENT 3.1 APPLICABLE STANDARDS This section specifies the BIM standards that are integrated into the Information Requirements. It provides a list of standards that apply to the use of Building Information Modeling (BIM) in the project, outlining the guidelines and criteria that must be adhered to for consistency and compliance throughout the project lifecy- cle. 1. Information Management for Construction Project Capital Phase using BIM: This standard outlines guidelines for effectively managing information during the initial construction phase of projects employing Building Information Modeling (BIM).

Figure 8:Adapted MacLeamy curve. Source: BIM for Health and Safety in Construction, https://www.autodesk.com/autodesk-university/de/

node/6100

2. Information Management for Asset Operational Phase using BIM: This standard focuses on managing information during the operational phase of assets utilizing BIM, ensuring efficient maintenance and performance throughout their lifecycle. 3. Security-Oriented BIM, Digital Environments, and Smart Asset Management: This standard emphasizes security considerations for BIM, digital environments, and intelligent asset management systems, addressing safety and data protection. 4. Collaborative Production of AEC Information: This standard promotes collaborative creation of architec- tural, engineering, and construction (AEC) information, enhancing cooperation among project stakeholders. 5. Fulfilling Employer’s Information Exchange Requirements with COBie: It guides the fulfilment of the em- ployer’s information exchange requirements using the Construction Operations Building Information Exchange (COBie) standard, which streamlines data exchange in construction. 6. Design and Construction Briefing: Facilities Management Code of Practice: This standard provides a code of practice for briefing processes in design and construction, ensuring alignment with facilities management needs. 7. Library Objects: Identification and Classification: It focuses on the identification and categorization of library objects used in BIM, facilitating consistent organization of resources. 8. Library Objects: 2D Symbols for Building Elements in BIM: This standard recommends 2D symbols for var- ious building elements, enhancing their representation in BIM models.

3. MANAGEMENT

Amus. Parum id entur,

90% 50%

9. Library Objects: Shape and Measurement: It deals with the shape and measurement aspects of

library objects used in BIM, ensuring accuracy in representation.

Figure 9: Define Project BIM Standards for AEC Projects (According to the ISO 19650 Series), Source: Autodesk Customer Success hub

3.2 INFORMATION MANAGEMENT ROLES AND RESPONSIBILITIES The purpose of this section is to highlight the allocation of roles related to the management of

both the model and project information to the project team.

The specific roles themselves are detailed in dedicated appointments and Employer’s Require-

ments (ERs). The current version of the Project Execution Plan is expected to define the overall

responsibility and scope of these appointments.

Certain roles associated with BIM are directly assigned by the employer and may include:

• Information Manager (IM)

• Project Officer (PO)

• Information Security Manager (ISM)

• Soft Landings Champion

It is the responsibility of the Supplier to confirm the parties and named individuals who will

assume the role of overseeing information modeling and management for the project. This

confirmation should provide a clear description of the activities that each individual will per-

form and the authorities they will hold, in accordance with Key Performance Indicator (KPI) 4

10. Library Objects: Attributes for Specification and Assessment: This standard defines at- tributes for specification and assessment of library objects, promoting consistent use and eval- uation. 11. Library Objects: Product and Facility Declarations: It provides guidelines for declarations related to products and facilities in BIM, assisting in documentation and data management. 12. Soft Landings Strategy: A Soft Landings strategy shall be applied to ensure a smooth transition from construction to occupation, utilizing the soft landings framework and principles of BIM.

This section serves to define the methods, locations, and timelines for sharing project information.

Autodesk BIM Collaborate Pro having an intrinsic functionality compliant with ISO 19650 provides the

standard collaboration structure which in its simplest form has Work in Progress, Shared and Pub-

lished container that ensures secure transfer of information.

The Project Team is responsible for managing the Project Common Data Environment (CDE) through-

out each project stage. The management and system providing this service may change as different

Project Teams are appointed for various stages or phases. However, only one Project CDE will be ac-

tive at any given time to prevent duplication of information.

Competency and capability in the collaboration process must be demonstrated in the Pre-Contract

BIM Execution Plan, with comprehensive process details expected in the completed Post BIM Execu-

tion Plan.

The KPI that are directly correlated with Collaboration are:

• Frequency and format of milestone information exchanges

• Strategies for managing data and information sharing restrictions based on the Employer’s

security requirements

3.3 COLLABORATION PROCESS

• Methods to meet and track the Information Delivery Plan requirements • Details of model review workshops and collaborative practices, including model federation and coordination during design and site meetings • Frequency and methods for design/UCL client team reviews using federated mod- els/data • Recording and sharing of pertinent GSL (Geospatial and location) activities throughout the project at specified data exchange points.

The Supplier is required to confirm their chosen collaboration tool and its intended oper- ation to support the Common Data Environment in alignment with owner requirements. This confirmation should include details on how Archive information will be transferred to the employer upon the Practical Completion of the construction works and installations.

3.4 PLANNING THE WORK AND DATA SEGREGATION

THE FOLLOWING STRATEGIES ARE REQUIRED AMONG THE BASICS FOR DATA

This section outlines the requirements for discipline-based model authoring and data segregation. Information management should adhere to the processes outlined in BEP.

If Owner has specific work management requirements, including security considerations, these should be identified on a project-specific basis or included in the Information Delivery Plan (IDP). The Information Delivery Plan (IDP) specifies the information delivery, formats, and exchange re- quirements for models, documents, and data.

The following strategies are required among the basics for data:

• Model Management: Details of quality assurance processes. • Volumes, Zones, and Areas: Definitions of zones and the management of adjacency within discipline models; confirmation of the project volume structure; naming convention for volumes or spaces; require- ments for separate project volumes for sensitive assets and systems

Figure 10: Typical collaboration workflow

• Naming Conventions: Adoption of a single project file naming convention, agreed asset naming and num- bering methodology using consistent language for asset function and identification; agreement on logical and consistent names for zones and spaces. • Purpose of Issue (Suitability Codes): When a CDE platform lacks the feature to assign file suitability meta- data, document naming standards should be used to communicate the file’s intended purpose.

• Publishing Processes: o Definition of contents for stage Information Exchanges by the lead designer pre-contractor appoint- ment through Task Information Delivery Plans (TIDP); scheduling of Information Exchanges by the contractor post-contractor appointment via the Master Information Delivery Plan (MIDP); sharing of project information to the appropriate CDE by the Supplier Information Manager for the delivery stage; notification by the Supplier Information Manager to the Employer Information Manager upon uploading all required stage deliverables to the CDE; validation of shared project information and asset data by the Employer Information Manager, followed by the production of a Red Amber Green (RAG) acceptance report for the Supplier Information Manager; acceptance of only Green packages into the CDE Published file area, along with corresponding data outputs and file linkages; remediation of Amber or Red packages by the Supplier; clarification that accepting failure and resubmitting deliv- erables in line with the Information Delivery Plan is unlikely to result in a variation or compensation event.

CDE

Client

Architect

Engineer

Supplier

Contracto r

Subs

Operator

Client

Architec t

Engineer

Supplier

Contract or

Subs

Operato r

3.5 SECURITY The purpose of this section is to outline the security measures necessary to safeguard personal and commercial information on behalf of Owner.

Specific security measures related to information exchange for all built assets will be determined on a project-spe- cific basis and will be communicated to the supply chain.

Any file uploaded to the Supplier Common Data Environment (CDE) or shared, disclosed, published, or exchanged in any manner must adhere to security standards.

The methods for monitoring and managing compliance to ensure adherence to these security requirements are among:

o The definition of contents for stage Information Exchanges starts during the pre-contractor appointment as task delivery. However, scheduling of Information Exchanges by the contractor post-contractor appointment will be done within the appropriate Common Data Environment (CDE) by the Supplier Information Manager for the delivery stage. Notification by the Supplier Information Manager to the Employer Information Manager upon uploading all required stage deliverables to the CDE will be intelligently automated. o Validation of shared project information and asset data by the Employer Information Manager, followed by the production of an acceptance report for the Supplier Information Manager o Acceptance of only approved packages into the CDE Published file area, along with corresponding data outputs and file linkages.

o Remediation of rejected packages by the Supplier, clarification that accepting failure and resubmitting deliverables in line with the Information Delivery Plan is unlikely to result in a variation or compensation event.

3.6 COORDINATION AND CLASH PREVENTION A comprehensive plan for coordination and clash prevention, the supplier ensures that potential clashes and con- flicts are proactively identified and resolved, contributing to the overall quality control of the project. • Associated Software: Detail the specific software tools and applications that will be used for coordination and clash prevention. This includes Building Information Modeling (BIM) software and any specialized clash de- tection tools. • Process Overview: Provide an overview of the coordination and clash prevention process. This should include the key steps involved in identifying and resolving clashes or conflicts in the project. • Responsibilities: Clearly define the roles and responsibilities of each team member involved in coordina- tion and clash prevention. This ensures that everyone understands their part in the process. • Outputs: Describe the expected outputs of the coordination process, which may include reports, clash detection reports, and updated project models. These outputs should be aligned with project requirements.

1. Regular Audits: Conduct periodic security audits of the Common Data Environment (CDE) and the overall information exchange processes. These audits can assess whether security protocols are being followed and iden- tify any vulnerabilities or breaches. 2. Access Controls: Implement robust access controls within the CDE, including user authentication, au- thorization levels, and role-based permissions. Regularly review and update these controls to align with project requirements. 3. Logging and Tracking: Maintain detailed logs of all activities within the CDE, including file uploads, access requests, and changes made to sensitive information. These logs can serve as a record of security-related events. 4. Incident Response Plan: Develop an incident response plan that outlines steps to be taken in the event of a security breach or incident. Define roles and responsibilities for addressing security issues promptly. 5. Security Training: Ensure that all project team members receive proper training on security best practices. This includes awareness of potential threats, password management, and secure data sharing. 6. Security Compliance Checks: Regularly review and assess compliance with security standards, including ISO security standards, and compare the actual security measures in place with the required security standards. 7. External Testing: Consider conducting penetration testing or vulnerability assessments by external secu- rity experts to identify weaknesses in the security infrastructure and address them proactively. 8. Documentation and Reporting: Maintain comprehensive documentation of security measures and inci- dents. Create regular security reports to provide project stakeholders with visibility into the state of security compliance. 9. Continuous Improvement: Establish a feedback loop for security improvements. Analyze security inci- dents or audit findings to identify areas for enhancement and update security policies accordingly. 10. Third-Party Assessments: If applicable, engage third-party security assessors to evaluate the security posture of the project, providing an unbiased assessment of security practices.

Figure 11: Sample clash matrix from Autodesk BIM Collaborate Pro

• Proposed Workflow and Systems: Outline the workflow for verifying and validating project data. Specify how generated and received data will be checked for clashes and coordination issues. • Tolerance Strategy: Define the tolerance levels for clashes and coordination issues. This helps in setting acceptable limits and expectations for resolving conflicts. • Clash Resolution Process: Explain the step-by-step process for resolving clashes. This should include procedures for communication, issue tracking, and resolution timelines. • Verifying Technical Queries: Describe how technical queries related to files and data will be verified with the supplier. Ensure that the suitability of data content is validated, and any discrepancies are addressed prompt- ly. • Quality Assurance: Present a proposal for quality assurance measures during the coordination process. Explain how the Client or end users will be involved when incorporating Project Information Model (PIM) data into the Asset Information Model (AIM) for Facility Management (FM) operations and Owner Asset Management purposes. • Alignment with Contractual and Process Requirements: Discuss how the coordination and clash preven- tion process aligns with the employer’s contractual obligations and process requirements. Highlight any ongoing or periodic technical reviews that will be conducted to ensure compliance. • Volume Strategy: Define the strategy for managing project volumes, including how different project areas or zones will be coordinated to avoid clashes. • Tolerance Strategy: Reiterate the tolerance strategy for clashes and coordination issues within the con- text of the coordination and clash avoidance processes. • Technical Query Workflows: Elaborate on the workflows for raising and resolving technical queries related to coordination and clashes. • Software Support: Specify the software tools and applications that will support coordination and clash avoidance efforts. Explain how these tools will be used effectively. • Outputs: Outline the specific outputs generated through coordination and clash avoidance processes, such as clash reports, updated models, and documented resolutions.

By providing a comprehensive plan for coordination and clash prevention, the supplier ensures that potential clashes and conflicts are proactively identified and resolved, contributing to the overall quality control of the proj- ect.

• Internal Model File and Data Standards: The supplier specifies their internal model file and data standards, ensuring that all project-related information adheres to these standards. This includes referenc- es to relevant industry and project-specific standards and compliance software tools.

The supplier outlines how they will ensure the integrity and quality of the model and associated data sources are maintained throughout the project. Here’s an elaboration on this section:

Quality Assurance/Control Procedure: The supplier details their quality assurance and control pro- cedures, highlighting the processes in place to verify and maintain the quality of data, models, and documents. This ensures that all project-related information meets the specified standards and re- quirementsquirements.

3.7 COMPLIANCE PLAN

Accessing the Autodesk Interoperability Tools for Revit

The Autodesk Interoperability Tools for Revit installer includes the COBie Extension, Equipment Data Tool, Model Checker, Room & Area Sync, Shared Parameters Tool, and Standardized Data Tool. The Model Checker Configurator is now a separate installation.

The tools can be downloaded from manage.autodesk.com, or installed directly through Autodesk Access (formerly the Autodesk Desktop App).

Figure 12: Model Health Power BI Report. Source: Autodesk Interoperability Tools

• Associated Software: Mention the software tools and applications that will be used to support quality as- surance and control efforts. These tools must be BIM integrated, along with ability to handle Inspection test plans and quality checklist forms. • Period of Aftercare: If applicable, the supplier specifies the duration of the aftercare period during which the model and associated data should be managed and maintained. This period may vary depending on proj- ect-specific requirements and is typically defined in consultation with Owner. • Security and Information Assurance Requirements: The compliance plan includes details regarding se- curity and information assurance requirements. It ensures that data security measures are in place to protect sensitive project information in accordance with relevant standards and regulations. • Access for Compliance Monitoring: The employer or the Employer Project Information Manager (PIM) is granted reasonable access to the Supplier Common Data Environment (CDE) for compliance monitoring and audits. This access allows them to ensure that compliance with standards and procedures is being upheld. • Quality Assurance Processes: The supplier confirms their quality assurance processes for data, models, and documents. This includes procedures for reviewing, verifying, and validating project- related information to maintain high quality throughout the project lifecycle. Dashboard such as the below are essential to monitor the process and performance.

Sales Places

3.8 DELIVERY STRATEGY FOR ASSET INFORMA- TION This section outlines the requirements for exchanging asset information, ensuring that the employer receives pro- posals for the delivery of asset information into the Facilities Management (FM) environment. Here’s an elabora- tion on this section: • Information Exchange Requirements: This section defines the specific requirements for exchanging asset information. It allows the employer to request and receive proposals for how asset information will be delivered and integrated into the FM environment.

• Aftercare Period: If aftercare is required, the contractor specifies the duration of this period, indicating the number of years the model and associated data will be managed following project handover. Aftercare ensures that the model remains accurate and up-to-date during its operational phase.

• Data Format for Asset Information Model (AIM): The data format provided to the Asset Information Model (AIM) adheres to the specifications outlined in the Information Delivery Plan (IDP). This data is transmitted and stored in the designated information exchange formats mentioned earlier, along with any associated exchange information files.

Figure 13: How COBie is organized. Source: COBie and Classification Systems in Revit, T.J. MEEHAN, JASON KUNKEL, Autodesk

University.

Figure 14: COBie extension for Revit. Source: How COBie is organized. Source: COBie and Classification Systems in Revit,

T.J. MEEHAN, JASON KUNKEL, Autodesk University

• COBie Data Deliverable: COBie (Construction Operations Building Information Exchange) serves as the default data exchange format for asset information, regardless of whether 3D modeling is involved. The IDP defines the specific COBie tabs that must be completed at each RIBA work stage, ensuring comprehensive asset information delivery. • IFC Data Deliverable: Asset information is also delivered in the Industry Foundation Classes (IFC) for- mat. This format includes geometry models that feature UCL-listed assets as data-rich objects with custom pa- rameters. These parameters align with the Level of Information (LOI) specified by the IDP.

• Owner DCT Data Deliverable: Data Collection Template (DCT) is another data deliverable format. It com- prises a spreadsheet file generated and/or populated by 3D model authoring software, including custom param- eters specified in the IDP. • Compliance with Standards: Asset information delivery complies with the details described in recog- nized standards. These standards ensure that asset information is structured, organized, and exchanged consis- tently and in alignment with industry best practices.

By employing these templates, the section aims to establish a structured and consistent approach to information coordination and project planning. The MIDP and Project Plan help streamline communication and alignment among project stakeholders, while the IDP serves as a fallback reference when a detailed Project Plan is not in place. This ensures that information delivery remains organized and synchronized throughout the project lifecycle. • Master Information Delivery Plan (MIDP): The Supplier is responsible for creating the Master Information Delivery Plan (MIDP) in response to the Information Delivery Plan (IDP). The MIDP follows a similar or related format to the IDP and serves as a structured document that outlines how and when information will be delivered throughout the project. It ensures that all project stakeholders are aligned regarding information exchange and delivery timelines. These have clearer definition in publishing processes under section 3.4. • IDP: All team members are expected to rely on the Information Delivery Plan (IDP) for managing and monitoring project progress and information delivery. The IDP becomes the primary reference document for coor- dinating information exchanges and ensuring that the project stays on track in terms of information management. • EDI: It is recommended that stakeholders agree on electronic data interface procedure to define the var- ious data templates to exchange information both direction.

3.9 TEMPLATE PROVISION

This section emphasizes the importance of training to ensure that all project stakeholders are proficient in using the tools and systems necessary for effective project management and collaboration. It also highlights the need for security awareness and outlines how information should flow between the Supplier and Employer CDEs. • Training Details: The purpose of this section is to provide bidders with comprehensive information about the training that will be offered concerning project systems. Additionally, it specifies any training requirements that the bidder is expected to deliver as part of their appointment or contract. • Supplier’s Training Responsibilities: The Supplier is required to confirm the training they will provide for the tools and systems that the Employer and other project stakeholders will use. This ensures that users have the necessary skills to effectively utilize the provided tools and systems. • Information Handling and Access Training: The Supplier is responsible for delivering training on appropri- ate information handling and access to all interfacing parties, including Employer staff. This training is essential for effectively operating and accessing the Supplier Common Data Environment (CDE). • Employer’s Training Responsibilities: Training related to access and operation of the Employer’s CDE will be provided by the Employer to interfacing Supplier staff as needed. This ensures that Supplier staff can effective- ly interact with the Employer’s systems. • Model Viewing Software: If the Supplier proposes the use of proprietary model viewing software that dif- fers from what the Employer holds, the Supplier must provide reasonable access and training at no cost to ensure seamless collaboration.

3.10 TRAINING

• Security Awareness: Any general security awareness and induction requirements, as well as role- based security requirements, will be communicated to the Supplier on a project-specific basis. • Information Sharing: Information should be progressively shared and published from the Supplier’s CDE to the Employer’s CDE. In normal circumstances, the Employer should not require ac- cess to the Supplier’s CDE, except for compliance purposes. This ensures that data flows efficiently between the parties and compliance is maintained.

4. TECHNICAL 4.1 SOFTWARE PLATFORMS This section emphasizes the flexibility and openness in software selection while providing clear guidance on how software platforms and versions will be documented, how COBie data will be gen- erated, and how data will be prepared and published for effective project collaboration and infor- mation exchange. Disciplined Approach: Owner encourages a discipline approach to digital project delivery, minimiz- ing conversion issues. The software used need to be compliant and integrated with the owner CDE. • List of Platforms and Versions: The known software platforms and versions used by Owner in their projects are specified. These include Autodesk Products and others. Project-specific authoring, reviewing software, or collaborative platforms need to integrate with ACC. Please refer to section 1.3 of this document. • Supply Chain Software: The BIM Execution Plan (BEP) must provide a list of software and plugins, along with their versions, that will be utilized by the supply chain. The BEP should also de- fine the processes for working with these platforms and address potential interoperability issues, ensuring smooth collaboration. • COBie Data Generation: The BEP should outline the process for generating COBie data from the geometry models. This ensures that relevant data is accurately extracted and organized. • Data Preparation and Publication: The Supplier is responsible for confirming how data and information from their authoring software will be prepared and published to make it accessible and usable by the Employer. This includes defining the steps for data transformation and sharing.

4.2 SYSTEM PERFORMANCE

This section provides clarity on any system-related constraints or requirements that may impact the project. It emphasizes the importance of system performance considerations, adoption of perfor- mance requirements, and compliance with employer-side IT system restrictions and security mea- sures.

Constraints and IT Requirements: The primary purpose of this section is to inform potential bidders of any constraints within the employer’s systems or specific IT requirements that might necessitate addi- tional resources or non-standard solutions. This ensures that bidders are aware of any potential chal- lenges related to system performance. • Adoption of System Performance Requirements: The BIM Execution Plan (BEP) will confirm the adoption of system performance requirements, indicating that these requirements are an integral part of the project execution. This is a key performance indicator (KPI) to be met. • Employer-Side IT System Restrictions: The section lists specific IT system restrictions and re- quirements on the employer’s side that must be considered when developing the BEP. These include: o Model Size: While there is no strict physical size restriction, practical considerations limit mod- el sizes to a maximum of around 100 megabytes (MB). Bidders and project teams should be mindful of these limitations when working with project models. o Security Issues: The security section of the document outlines any security-related issues or requirements that must be adhered to. These measures are essential for safeguarding sensitive project information.

4.3 DATA EXCHANGE FORMAT

This section outlines the various formats used for Information Exchanges, emphasizing that the choice of format is influenced by project-specific requirements and standards such as CO- Bie, PDF, IFC2x3, and BASIR for sensitive assets and systems when applicable. Defining Exchange Formats: The primary purpose of this section is to specify the formats that will be used to convey Information Exchanges. These formats are determined at the project lev- el, based on the requirements detailed in the Information Delivery Plan and any project-spe- cific needs. • Output Formats: The section lists various potential output formats that may be re- quired for Information Exchanges: • Native 3D Model Files: This includes the original, un-federated 3D discipline model files used for design and analysis. These files are typically in their native format. Please refer to section 1.3 of this document for mandated software. • COBie Format: Information Exchanges may need to comply with standard for COBie. This format includes references to exchanged documents and files, facilitating efficient data exchange. • PDF Files: PDF documents are a common output format. The section specifies that PDFs should not be older than 2 years by default. This ensures compatibility and readability of doc- uments.

Figure 15: Setting coordinate and elevations in Revit

• Open Standard Files: Industry Foundation Class (IFC) files, which are open standard files commonly used in the construction and building industry, may be required for specific purposes. • Sensitive Asset Information: If the project follows a standard that deals with security information, any data related to sensitive assets and systems will need to adhere to the format specified in the Security Informa- tion Requirements.

4.4 COORDINATES

This section serves the purpose of promoting the adoption of a common coordinate system for all BIM data, ensuring uniformity across all models. It defines specific requirements for this common coordinate system. The minimum requirement for spatial coordination is stated as follows: • Intersection of grids XX and YY: This specifies a particular point where the grid lines labelled XX and YY intersect. The coordinates for this intersection point are defined as xxxxxx.xxxE (Easting) and xxxxxx.xxxN (North- ing), indicating the location in an east-west and north-south direction. • Intersection of grids AA and BB: Similarly, this requirement identifies another intersection point where grid lines AA and BB intersect. The coordinates for this intersection point are defined as xxxxxx.xxxE and xxxxxx. xxxN. • Ground floor Finished Floor Level (FFL): This requirement sets the elevation of the ground floor Finished Floor Level at xxx.xxx units.

Additionally, the BIM Execution Plan should include other coordination standards, including: • Origin rotation: If necessary, specify any rotation of the coordinate system’s origin. • Offsets: Define any offsets that need to be applied to the coordinates. • Datum information: Clarify the datum (reference point) used for establishing the coordinate system. • Units to be used: Specify the units of measurement to be employed for the coordinates. Furthermore, the plan should ensure that 3D geo-location coordinates are displayed with no less accuracy than 10mm (0.01m) in all directions. This level of precision is essential for maintaining accurate spatial information across the project’s models

5. COMMERCIAL 5.1 BIM EXECUTION PLAN This section outlines the requirements and expectations related to the BIM Execution Plan (BEP) for the project. • Supplier Responsibility: The Supplier is responsible for the creation, delivery, and maintenance of the BIM Execution Plan. This plan should align with the specified Employer Information Requirements. • Regular Review: The Supplier must perform regular reviews of their BEP. Additionally, any changes to the contract should trigger a review and potential update of the plan. • Pre and Post Contract Plans: The Supplier is required to provide both Pre and Post contract BIM Execution Plans. These plans should address the specific details outlined in the Employer›s Information Requirements and present the Supplier›s proposals for each clause. It›s important to note that the Pre contract BIM Execution Plan will be evaluated and scored as part of the tender submission, emphasizing the significance of this planning document in the project›s overall execution. displayed with no less accuracy than 10mm (0.01m) in all directions. This level of precision is essential for maintaining accurate spatial information across the project's models

5.1 BIM SPECIFIC COMPETENCE REQUIREMENTS This section outlines the information that bidders must provide as part of their submission to demonstrate their capability, capacity, and experience in Building Information Modeling (BIM), in alignment with standard. • BIM Approach and Culture: Bidders must describe their organizational approach to BIM and the prev- alent BIM culture within their organization. • BIM Experience: This includes detailing the organization’s experience, capabilities, and competencies related to BIM. This should encompass the level of skill and expertise within the organization.

• Outsourcing of BIM Roles: If any BIM-related roles are outsourced, bidders should disclose this information. • BIM Toolset and Processes: Bidders should confirm the BIM tools they utilize and describe the processes and procedures that constitute their BIM and information management toolkit, ensuring compliance with the standards specified in this EIR. • Resource Allocation: This section requires bidders to provide a resource matrix, specifying the levels, numbers, and utilization of resources for the project. Additionally, any outsourcing details or services should be included. • Principal Supply Chain Capabilities: Bidders must explain how their principal supply chain part- ners will integrate into the BIM process and how this integration will be assessed. Key supply chain partners, expected outputs, and the assessment process should be detailed in the response.

Please see sample BIM Assessment Form in Appendix B of this document.

This section outlines the policies and protocols regarding the production, ownership, and utilization of

models in the context of BIM for the project.

• Implementation of BIM Protocol: Stake holders will adhere to the BIM Protocols, for projects

adopting specified BIM level. This protocol places obligations on parties involved in the project to pro-

vide specified elements of their work or services using models.

• BIM Protocol in Contracts: All parties engaged in activities related to the creation, utilization, or

delivery of models for the project are required to have a BIM Protocol attached to their contracts. This

protocol outlines the specific terms and conditions governing BIM-related activities.

• Information Reuse: Owner standard practice includes requiring a license for the reuse of infor-

mation. This license specifies the permitted purposes for which the information can be reused, as de-

fined within the BIM Protocol. This ensures that data is used in accordance with predefined guidelines

and restrictions.

• Previous BIM Projects: Bidders should provide examples of past projects that were executed in accordance with the standards referenced in this EIR. • Security Expertise: Bidders must showcase their understanding, capability, competence, and prior experience in implementing security measures related to BIM.

5.3 PRODUCTION, OWNERSHIP AND USE OF MODELS

6.1 APENDIX A - ROLES AND RESPONSIBILITIES - SAMPLE (RACI MATRIX BASED)

6. APPENDIXES

Please see the Excel sheet 4 - EIR Appendix B - RACI Matrix.xlsx

6.2 APPENDIX B

BIM ASSESSMENT FORM - SAMPLE ONLY

Employer's information requirements (EIR)

Item Type: pdf