## 5 BIM-Enabled Asset Information Delivery Process  
In this section, the asset information delivery process is presented by breaking it down into eight key activities that are further explained with examples from project A. Although the examples are from project A, the presented process was the same as proposed for projects B and C. Figure 6 presents a schematic representation of key components and activities in the asset information delivery process. The project phases are defined separately here for simplification. However, there are overlaps between them that can vary according to the delivery method employed. 1. _Definition of the Information Requirements_  
The first step focuses on identifying the relevant assets that will be tracked to support FM activities, what kind of information will be collected for each of these assets during the design and construction phases, and how this information should be structured in the models. ISO 19650 suggests the development of the information requirements in three distinct documents, the OIR, AIR, and Exchange Information Requirements (EIR), starting with the development of OIR, which should contain the information requirements at an organizational level. Although the owners had elements of an OIR in their Statement of Requirements, there was no document specifically developed as an OIR. Therefore, the scope of the analysis of the requirements in this case study was limited to the project level. The elements expected in the AIR and EIR were presented together in a set of documents called BIM Requirements. The overall goal defined by the owner for BIM implementation was to: \"Utilize a BIM process to derive consistent digital data that can be used to drive downstream uses during the entire life cycle of the facility, from design, through construction and on into Facility Maintenance and Operations.\" In practical terms, there were three main purposes of BIM in the project: (a) To facilitate design review and communication of design intent through 3D visualization of the model, (b) To allow virtual coordination within and between disciplines to identify and address design and constructability issues before construction, and (c) To collect asset data to support FM activities. In this paper, we focus on the third purpose, which was the owner's priority: the collection of asset data to feed their new CMMS, Maximo(r), to support FM activities. The BIM requirements documentation comprised three main documents:  
1. Owner Standard Requirements (OSR).--A standardized document used by the health authority (owner), to describe their goals and processes and establish the minimum BIM requirements in their projects. The OSR covered legal aspects, specific modeling requirements for the different disciplines, an accuracy table, virtual coordination workflows, etc. 2. BIM Project Execution Plan (BEP).--A guideline for the coordination of the BIM development process in this specific project. The BEP was meant to be a roadmap to facilitate the reuse of the models in the future. It was prepared in collaboration between the BIM consultants and the design build teams. The content included modeling strategies, quality control protocols, and collaboration tools. It was required to be updated over time to reflect the reality of the process during the design. 3. BIM Data and Geometry Specification (DGS).--This document established the information requirements for each category of objects through the specification of parameters to be added and populated in the model. A total of 130 different data parameters were specified. It also provided the Level of Development (LoD) for each category of objects. This document also included an Object List spreadsheet containing 217 different types of assets required in the model along with their importance for FM, category specification, discipline, and naming convention. To convey asset information for FM, virtual objects employed in BIM during design are used as containers, which are here defined as digital assets.