Lesson 1, Topic 1
In Progress

BIM According to ISO 19650 Copy

Shown is the current ISO 19650 series from January 2019.

ISO 19650-1 – Part 1: Concepts and principles
An introduction to the concepts and principles of the information management process is expanded upon in the following parts.

Published December 2018. View standard.

ISO 19650-2 – Part 2: Delivery phase of assets
Details the process for the management and collaborative production of information during the delivery phase of assets.

Published December 2018. View standard.

ISO 19650-3 – Part 3: Operational Phase of assets

Sets out the information management process for the management and collaborative production of information during the operational phase of assets. Provides additional guidance for asset owners.
Published August 2020. View standard.

ISO 19650-4 – Part 4: Information exchange
Recommended concepts and principles for the exchange of information between parties throughout the lifecycle of an asset. For both receivers (appointing party) and providers (lead appointed party, appointed parties) of information.

In development (at time of publishing). View standard.

ISO 19650-5 – Part 5: Security-minded approach to information management
Provides a framework to assist organisations in adopting a security-minded approach to managing information relating to sensitive assets.

Published June 2020. View standard.
A set of region-specific requirements are recommended for the standard, providing opportunities to clarify how ISO 19650 should be implemented within that region. The national annex is generally the only standard applicable for use in that region: e.g., AS ISO 19650 series for Australia or BS ISO 19650 series for the UK.
Organisational Information Requirements describe the information required by an organisation for asset management systems and other organisational functions. That is, they are organisational-level information requirements rather than asset-level or project-level information requirements.

Asset Information Requirements (AIR) are part of the Building Information Modelling (BIM) process, defining the graphical and non-graphical data, information and documentation needed for the lifetime operation and management of a built asset. ISO 19650 defines AIR as ‘information requirements in relation to the operation of an asset’; an information requirement is defined as ‘specification for what, when, how and for whom information is to be produced.

An Asset Information Model (AIM) is a model that compiles the data and information necessary to support asset management; that is, it provides all the data and information related to or required for the operation of an asset.

An AIM can provide graphical and non-graphical data, information, documents, and metadata. It can relate to a single asset or a portfolio of assets. An AIM can be created from existing asset information systems, new information, or information in a Project Information Model (PIM) that was created to construct a new asset.

PIR focuses on information that the client requires at key decision points during a design and construction project delivery. While creating PIR, the client should consider the project plan of work and tie its key decision points with the schedule.

The exchange information requirements (EIR) define the information that the employer will require from both their own internal team and from suppliers for the development of the project and the operation of the completed built asset. Relevant extracts from the exchange information requirements are included in procurement documents for the appointment of each supplier appointed directly by the employer, which may include; advisors, consultants, contractors and so on.

The Project Information Model (PIM) is the information model developed during a project’s design and construction phase.’ The requirements for the Project Information Model are set out in Exchange Information Requirements (EIR); it is likely to consist of a federated building information model, non-graphical data and associated documentation.

The project information model is developed progressively as a design intent model rather than a virtual construction model.
The appointing party is the establisher of the work. This is often the client, asset owner or operator. They are the receivers of information and the works provided by the delivery team/s. There is only one appointing party per project.

Example: a government department or developer.
The lead appointed party is an organisation directly appointed (employed) by the appointing party to provide works, goods or services concerning an asset. This is often the engineering consultant, JV arrangement or contractor. The lead appointed party takes the role of coordinator between the delivery team and appointing party. They are providers of information, and there can be multiple lead appointed parties per project.

Example: an engineering consultancy, general contractor, project management consultancy.
Appointed Parties are organisations subcontracted by a lead appointed party to assist in providing works, goods or services. They are providers of information for the lead appointed party, not the appointing party.

Examples: designers, planners, project managers, surveyors, suppliers, vendors.
The appointment between parties is an agreed instruction for providing information concerning works, goods and services. This term is used whether or not there is a formal written appointment.
An appointing party is likely to have appointments (contracts) with multiple lead appointed parties throughout the project lifecycle and have their own appointments with multiple appointed parties.
The task team is a team (or an individual) responsible for performing specific tasks in the production and management of information. Task teams are often created around a discipline, for example, civil design, surveying, traffic/ signal, geotechnical or structural design. There are often multiple task teams within the delivery team.
The delivery team includes all individuals responsible for the creation and management of information. It is the lead appointed party and all its appointed parties. There may be multiple delivery teams on a project.
The project team is all parties involved in the delivery process of an asset, the appointing party, lead appointed party/ parties, and all appointed parties. This includes both receivers and creators of information. There is only one project team on the project.
Project team example.
Now that you understand the parties and teams on a project, I’ll now introduce you to the lifecycle of a project, known as the information management process.
The information management process has 8 stages which will be established below, and then covered in greater detail in the following slides.
1) Assessment and Need
The appointing party determines why works are to be carried out – e.g., improve a highway’s capacity and safety – and establishes the information requirements, information standards, and project milestones.
2) Invitation to Tender
The appointing party establish their tender response evaluation criteria and then issue a tender inviting organisations to formally bid for the works. E.g., a tender for the detailed design.
3) Tender Response
Prospective delivery teams prepare and submit a response demonstrating their approach to the works and assess their capability and capacity.
4) Appointment
Tenders are evaluated, and the successful delivery team is selected, known as the lead appointed party. The delivery team undergoes detailed planning and prepares a schedule outlining how works will be completed to meet the information requirements and milestones.
5) Mobilisation
The delivery team ensure they have the people, processes, and technology to deliver the works, and teams are trained to do so. Procedures and technology are tested and documented.
6) Collaborative Production of Information
Information is generated, coordinated, checked, reviewed, and approved by the delivery team for publishing with the appointing party. Information is generated by task teams, and then upon approval, shared to other task teams for reference. I.e., the road design is shared to the lighting and signals task team.
Project Information Model (PIM)
The output is the creation of a project information model (PIM). PIM is a collection of information that responds to the specific requirements set out in the appointing party’s exchange information requirements (EIR). It provides all the information required to carry out the delivery phase of an asset. Examples include 3D models, databases, spreadsheets, or documentation.
7) Information Model Delivery
The appointing party reviews the published information model against their acceptance criteria and either approves or rejects it as a contractual deliverable. This is repeated for each milestone and information deliverable on the project.
8) Project Close-out & Asset Information Model (AIM) Aggregation
Once approved, work is completed and the appointment(s) ends. The information is archived and aggregated into the asset information model (AIM) for the ongoing operation and maintenance of the asset.
Asset Information Model (AIM)
The ultimate output of the information management process is the creation of an asset information model (AIM)which provides all the information required to perform the operation phase of the asset. At the end of the project, some components of the PIM may be transferred to the AIM, while unnecessary data is archived. The AIM can include graphical models, non-graphical data and all necessary documentation for the ongoing maintenance, operation, and management of the asset.
Steps 1 & 8 occur only once per project.
Stages 2 to 7 are repeated for each appointment on the project. For example, once for an appointment with an engineering consultancy for the design phase, and then again for another appointment with a contractor for the construction phase.
The information management process is characterised by three phases, as outlined:

• Steps 2 to 3 are the procurement phase
• Steps 4 to 5 are the planning phase
• Steps 6 to 7 are the production phase