oSIST prEN ISO 19650-3:2026

Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management - Part 3: Implementation of the information management process (ISO/DIS 19650-3:2026)

This document gives guidelines for the implementation of the information management process, in accordance with the requirements of ISO 19650-2.

Organisation und Digitalisierung von Informationen zu Bauwerken und Ingenieurleistungen, einschließlich Bauwerksinformationsmodellierung (BIM) - Informationsmanagement mit BIM - Teil 3: Umsetzung des Informationsmanagementprozesses (ISO/DIS 19650-3:2026)

Organisation et numérisation des informations relatives aux bâtiments et ouvrages de génie civil y compris modélisation des informations de la construction (BIM) - Gestion de l’information par la modélisation des informations de la construction - Partie 3: Titre manque (ISO/DIS 19650-3:2026)

Le présent document spécifie les exigences relatives à la gestion de l'information, sous la forme d'un processus de gestion, dans le contexte de la phase d'exploitation des actifs, ainsi que les échanges d'informations au cours de cette phase, au moyen de la modélisation des informations de la construction.
Le présent document peut être appliqué à tous les types d'actifs et par tous les types et tailles d'organismes impliqués dans la phase d'exploitation des actifs.
Les exigences du présent document peuvent être atteintes au moyen d'actions directes menées par l'organisme en question ou elles peuvent être déléguées à une autre partie.

Organizacija in digitalizacija informacij v gradbeništvu (BIM) - Upravljanje informacij - 3. del: Izvajanje procesa upravljanja informacij (ISO/DIS 19650-3:2026)

Ta dokument podaja smernice za izvajanje procesa upravljanja informacij v skladu z zahtevami ISO 19650-2.

General Information

• Status: Not Published
• Public Enquiry End Date: 29-Jul-2026
• ICS: 35.240.67 - IT applications in building and construction industry
• ICS: 91.010.01 - Construction industry in general
• Technical Committee: BIM - Building Information Modelling (BIM)
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 22-May-2026
• Due Date: 09-Oct-2026
• Ref Project: prEN ISO 19650-3 - Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management - Part 3: Implementation of the information management process (ISO/DIS 19650-3:2026)

Relations

• Revises: SIST EN ISO 19650-3:2020 - Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management using building information modelling - Part 3: Operational phase of the assets (ISO 19650-3:2020)
• Effective Date: 29-Jan-2025

Standards Content (Sample)

SLOVENSKI STANDARD
01-julij-2026
Organizacija in digitalizacija informacij v gradbeništvu (BIM) - Upravljanje
informacij - 3. del: Izvajanje procesa upravljanja informacij (ISO/DIS 19650-3:2026)
Organization and digitization of information about buildings and civil engineering works,
including building information modelling (BIM) - Information management - Part 3:
Implementation of the information management process (ISO/DIS 19650-3:2026)
Organisation und Digitalisierung von Informationen zu Bauwerken und
Ingenieurleistungen, einschließlich Bauwerksinformationsmodellierung (BIM) -
Informationsmanagement mit BIM - Teil 3: Umsetzung des
Informationsmanagementprozesses (ISO/DIS 19650-3:2026)
Organisation et numérisation des informations relatives aux bâtiments et ouvrages de
génie civil y compris modélisation des informations de la construction (BIM) - Gestion de
l’information par la modélisation des informations de la construction - Partie 3: Titre
manque (ISO/DIS 19650-3:2026)
Ta slovenski standard je istoveten z: prEN ISO 19650-3
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
International
Standard
ISO/DIS 19650-3
ISO/TC 59/SC 13
Organization and digitization
Secretariat: SN
of information about buildings
Voting begins on:
and civil engineering works,
2026-05-13
including building information
modelling (BIM) — Information
Voting terminates on:
management —
2026-08-05
Part 3:
Implementation of the information
management process
ICS: 93.010; 91.010.01; 35.240.67
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This document is circulated as received from the committee secretariat.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
ISO/CEN PARALLEL PROCESSING
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS.
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION.
Reference number
ISO/DIS 19650-3:2026(en)
ISO/DIS 19650-3:2026(en)
© ISO 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
ISO/DIS 19650-3:2026(en)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Guideline on transitioning to ISO 19650-2:2026 from ISO 19650-2:2018 and ISO 19650-
3:2020 . 1
5 Guideline on complete vs partial implementation of the information management
process . 2
5.1 General .2
5.2 Implementation for only some assets .2
5.3 Implementation by only some organizations in a project team .2
6 Implementation throughout the asset life cycle . 3
6.1 General .3
6.2 Trigger events and asset-related projects .4
6.3 Projects leading to information production .5
6.4 Types of trigger event .5
6.5 Planned trigger events .5
6.6 Unplanned trigger events .6
6.7 Asset acquisition trigger events.6
7 Implementation dependent on the complexity of the asset-related project . 7
7.1 General .7
7.2 Information management process for micro asset-related projects .8
7.3 Information management process for small asset-related projects .8
7.4 Information management process for large asset-related projects .9
7.5 Information management process for major programmes .9
8 Implementation dependent on the complexity of the team .10
8.1 General .10
8.2 Information being provided outside of appointments .10
8.3 Different sized teams or organizations .11
9 Implementation on different forms of procurement.12
9.1 Overview . 12
9.2 Design and build . . 13
9.3 Design-bid-build .14
9.4 Integrated project delivery .16
9.5 Frameworks and long-term arrangements .16
10 Implementation parties . 17
10.1 General .17
10.2 Appointing parties .17
10.3 Lead appointed parties .18
10.4 The information management team .19
10.5 Appointed parties .19
10.6 Third parties – roles and responsibilities .19
10.7 Examples where organizations can take multiple party types . 20
10.8 External organizations.21
11 Aligning information requirements and information production schedules .21
12 Implementing a common data environment .23
12.1 General guidelines . 23
12.2 Information production workflow . 23
12.2.1 General guidelines . 23

iii
ISO/DIS 19650-3:2026(en)
12.2.2 Aligning the information production workflow with the information production
activities .24
12.2.3 Configuring workflow state controls and permissions .24
12.2.4 Assigning the status of information containers within each workflow state . 25
12.3 Enabling technologies . 26
12.3.1 General guidelines . 26
12.3.2 Establishing functional and non-functional requirements . 26
12.3.3 Maintaining information container ID’s and properties.27
12.3.4 Implementing an information production journal .27
12.3.5 Implementing an information production archive .27
12.4 Deploying enabling technologies . 28
12.4.1 Deployment option A . 28
12.4.2 Deployment option B . 29
12.4.3 Deployment option C . 29
12.4.4 Advantages and disadvantages of each deployment option . 30
12.5 Linking and distributing information .31
12.5.1 Linking enabling technologies with enterprise systems .31
12.5.2 Distributing information containers outside of the common data environment .32
13 Guidelines on aggregating information models into the asset information model .32
14 Guidelines on federating information and implementing an information container
breakdown structure.33
14.1 Approaches to federating information . 33
14.2 Approach to federating information – example 1 . 33
14.3 Approach to federating information – example 2 . 34
14.4 Approach to federating information – example 3 . 34
14.5 Information container breakdown structure - general . 34
14.6 Information container breakdown structure – example 1 . 34
14.7 Information container breakdown structure – example 2 . 35
15 Guidelines on implementation of the information production standard and information
production methods and procedures .35
15.1 Implementation of an information production standard . 35
15.2 Implementation of information production methods and procedures . 36
16 Implementation guideline for level of information need .37
Annex A (informative) Transitional guideline on terminology .38
Annex B (informative) Hypothetical case study of the information management process during
the life cycle of an asset . 41
Bibliography .46

iv
ISO/DIS 19650-3:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see ww.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent
rights identified during the development of the document will be in the Introduction and/or on the ISO list of
patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 59, Buildings and civil engineering works,
Subcommittee SC 13, Organization and digitalization of information about buildings and civil engineering
works, including building information modelling (BIM).
This second edition cancels and replaces the first edition (ISO 19650-3:2020), which has been technically
revised.
The main changes are as follows:
— the requirements from ISO 19650-3:2020 have been incorporated into ISO 19650-2;
— this document sets out some guidelines for implementing the requirements of ISO 19650-2 under a range
of different circumstances; and
— this document also sets out some guidelines for implementing some of the specific requirements of
ISO 19650-2 concerning common data environment, aggregating information models, federating
information, information production standard, information production methods and procedures, and
level of information need.
A list of all parts in the ISO 19650 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

v
ISO/DIS 19650-3:2026(en)
Introduction
This document supports the implementation of the information management process defined in ISO 19650-2.
This document does not provide detailed guidelines to support other parts of ISO 19650, but other parts are
mentioned in the text when they are relevant.
The range of assets, asset-related projects and trigger events to which ISO 19650-2 can be applied is
extremely broad. One of the key objectives of this document is to indicate how ISO 19650-2 can be applied in
a way that is proportionate and appropriate to their scale and complexity.
Some topics concerning information management have been covered in detail in ISO 19650-1 and this detail
is not duplicated in this document. Instead, this document focuses on describing scenarios recognisable
in real case asset management and project management of asset-related projects, explaining how the
information management process can be applied.
The topics for which guidelines have been provided in this document are as follows:
— implementation throughout the asset life cycle;
— implementation for different types of trigger event;
— implementation dependent on the complexity of the asset-related project;
— implementation dependent on the complexity of the team;
— implementation for different forms of procurement;
— implementation parties;
— aligning information purposes and information production;
— implementing the common data environment; and
— aggregating information from a project into the asset information model.
There are many standards providing specifications or recommendations concerning different types of
information containers that are relevant for asset management and asset-related project management.
Examples are:
— ISO 22057:2022 Sustainability in buildings and civil engineering works – Data templates for the use of
environmental product declarations (EPDs) for construction products in building information modelling
(BIM); and
— ISO 21597-1:2020 Information container for linked document delivery – Part 1: Container, and
ISO 21597-2:2020 Information container for linked document delivery – Part 2: Link types.
However, guidelines on producing specific types of information containers in accordance with ISO 19650-2
is outside the scope of ISO 19650-3.

vi
DRAFT International Standard ISO/DIS 19650-3:2026(en)
Organization and digitization of information about buildings
and civil engineering works, including building information
modelling (BIM) — Information management —
Part 3:
Implementation of the information management process
1 Scope
This document gives guidelines for the implementation of the information management process, in
accordance with the requirements in ISO 19650-2.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 19650-2, Organization and digitization of information about buildings and civil engineering works –
Information management using building information modelling – Part 2: Information management process
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Guideline on transitioning to ISO 19650-2:2026 from ISO 19650-2:2018 and ISO
19650-3:2020
All parties involved in information management should establish their position regarding transition from
the documents published in 2018 and 2020 to those published in 2026.
One approach is to continue to use 2018 and 2020 documents in all appointments that have already started,
and to use 2026 documents in all new appointments that start from date of publication onwards. Practical
considerations can cause this transition date to be later than the date of publication, say 6 months after
publication.
While an appointing party is engaged in information management activities using both sets of documents,
then each formal communication relating to ISO 19650 activities should make clear which documents are
being used and include the mapping table from ISO 19650-1 Annex B.

ISO/DIS 19650-3:2026(en)
5 Guideline on complete vs partial implementation of the information management
process
5.1 General
All parties should implement all the requirements ISO 19650-2 places on them in full, to obtain the maximum
level of benefit from the information management process.
If complete implementation cannot happen then it is possible for some benefit to still be obtained. Partial
implementation can exist in two distinct ways.
1. An appointing party did not apply the information management process to all its assets that would
benefit from the process (see clause 5.2).
2. Some organizations involved in asset management or asset-related projects did not participate in
information management according to ISO 19650-2 (see clause 5.3).
5.2 Implementation for only some assets
Although an appointing party is expected to apply the information management process to as many of its
assets as would benefit from the process, it can be impractical to do this immediately. This can be because
of lack of personnel or funding to understand and apply the ISO 19650-2 requirements across all relevant
assets simultaneously.
Instead, the information management process can be adopted gradually over an agreed period of time. This
approach should be explained in the appointing party’s information management strategy (ref. ISO 19650-2
clause 5.1.1).
There are many different approaches to a partial implementation of ISO 19650-2 across an appointing
party’s asset portfolio, including:
— Selection of one or a few assets as pilots;
— Selection of a particular asset type as the first phase of wider roll-out; or
— Selection of a particular asset location as the first phase of wider roll-out.
Once the initial assets have been selected, there are different approaches to partial implementation in
relation to asset-related projects, including:
— Selection of asset-related projects in relation to a cost threshold, either above a threshold to be worth the
effort of implementing the ISO 19650-2 requirements or below a threshold to keep initial implementation
simple;
— Selection of asset-related projects based on the type of work involved; or
— Selection of asset-related projects that will involve particular organizations as lead appointed party,
based on their demonstrated understanding of the information management process.
The information management strategy should include details of how the roll-out of the information
management process is expected to expand over time, and how the roll-out should incorporate lessons
learned (ref. ISO 19650-2 clause 5.9.2).
5.3 Implementation by only some organizations in a project team
The information management process for a project, in ISO 19650-2 clauses 5.3 to 5.9, assumes that each
organization in the project team completes the required activities according to which type of party they are.
This is confirmed in ISO 19650-1 clause 4.2.
If one or more organizations decide not to fulfil the requirements of ISO 19650-2 then the effectiveness of
the information management process will be affected, as indicated in Table 1.

ISO/DIS 19650-3:2026(en)
Table 1 — – Examples of adverse effects of partial implementation of ISO 19650-2 requirements
Party type Risks associated with non-participation Potential outcomes from non-participation
Appointing party Lack of strategic thinking on information No direction given to lead appointed parties.
management.
No assessment of lead appointed party or
No input into defining information re- information production team capabilities
quirements or information constraints. regarding information management.
Loss of whole life focus on asset informa- No benefits for the appointing party.
tion.
Lead appointed party No oversight or coordination of appoint- Information deliverables do not meet the
ed parties or of the information they needs of the appointing party.
produce.
Information is not produced to meet the
No planning or scheduling of information appointing party’s milestones.
production.
Appointed party No implementation of information con- Information is incompatible with the ap-
straints to regulate how information is pointing party’s enterprise systems.
produced or presented.
Information is incompatible with outputs
from other appointed parties.
If the organization who would be expected to carry out the requirements of the appointing party is not
doing so, then a lead appointed party can still obtain benefit from information management activities under
its control. In this situation, a lead appointed party can still:
— coordinate the information production activities of its appointed parties;
— establish information production requirements (but these will be for its own benefit rather than to
benefit the appointing party); and
— establish an information production standard and a set of information production methods and
procedures to determine how information is expected to be produced within its information production
team (but loses the opportunity for formal collaboration with parties outside its information production
team).
6 Implementation throughout the asset life cycle
6.1 General
ISO 19650-2 defines information management activities for the whole life cycle of any asset in the built
environment, which gives a very broad range of situations where information management can be applied.
Appropriate application of the information management process is one of the key principles of ISO 19650,
and therefore different information management responses can be applied in different circumstances.
Steps one and two in the information management process need to be applied by the appointing party
to align the information management process with its asset portfolio and with the need for information
relating to its assets. See Figure 1. These steps are specified in ISO 19650-2 clauses 5.1 and 5.2. These two
steps should be repeated or revisited regularly so that this strategic alignment is maintained over time, as
the asset portfolio changes or as the appointing party’s objectives change, or as the business and regulatory
context changes.
Then steps three to nine in the information management process need to be applied within the context of
steps one and two, no matter how large or small the project is and no matter which business unit within the
appointing party’s organization initiates the project. See Figure 1. These steps are specified in ISO 19650-2
clauses 5.3 to 5.9.
ISO/DIS 19650-3:2026(en)
Key
1-2 Organizational strategy, establish and maintain the AIM
3 Project initiation
4-7 Appointment preparation, selection, appointment and mobilization
8 Information production
9 Project completion
A Trigger events, either planned for in advance or responded to when they occur
B Activities for each project
C Activities for each appointment of a lead appointed party
Information management throughout the asset life cycle
Repeat as planned
Figure 1 — The information management process
6.2 Trigger events and asset-related projects
Trigger event is the generic term for something that occurs during the life cycle of the asset that changes
or will change it physically or in an abstract way, and for which the asset information model needs to be
updated. See item A in Figure 1.
The response to a trigger event is an asset-related project in which work related to the asset is done. During
this work new information for the asset information model is produced. Specifying, procuring and producing
this information is a project for the purposes of ISO 19650-2 (see this document clause 6.3).
Asset-related projects include:
— the on-going events to keep an asset operational during its lifetime, such as inspections, surveys,
maintenance, repairs, replacement of components or equipment; and
— more substantial works to create, upgrade, refurbish, deactivate, dismantle, recycle or demolish an asset,
which can also include maintenance or repair works.
Asset-related projects representing on-going events can represent:
— a single instance of the on-going event (e.g. a single maintenance visit);

ISO/DIS 19650-3:2026(en)
— a limited sequence of repeated instances of the on-going activity (e.g. maintenance visits for five years);
or
— the complete set of anticipated instances of the on-going activity (e.g. maintenance visits for the remaining
life of the asset).
6.3 Projects leading to information production
The information management aspect of each asset-related project is a project as specified in ISO 19650-2
clause 5.3. Each project contains at least one event triggering the production of information (see ISO 19650-2
Figure 1, item B). The number and arrangement of these events is determined by the information
requirements and by the scale and complexity of the asset-related project.
In projects supporting more substantial asset-related projects, the events triggering information production
are often associated to project management work stages.
Annex A shows an example of applying the information management process to a hypothetical asset during
its life cycle.
6.4 Types of trigger event
A trigger event can be a standalone single event, such as a new design and construction works, or a set of
repeating events, such as a series of regular maintenance inspections. The way in which the information
management process is implemented can be adjusted according to the type of trigger event that is taking
place. The three different types of trigger event are planned trigger events, unplanned trigger events and
asset acquisition trigger events (see clauses 6.5, 6.6 and 6.7).
Each project established to support the response to a trigger event will contain one or more events triggering
the production of information. The appointing party should take account of the time required to complete
steps 3 to 7 in the information management process, which represent the time-lag between a trigger event
being identified, or taking place, and information being produced.
Where a planned or unplanned trigger event involves an existing asset, then the information management
process should include consideration of all relevant legacy information as well as consideration of newly
produced information.
ISO 19650-2 clause 5.1.6 refers to foreseeable trigger events. These are the trigger events that the appointing
party can identify in relation to its assets. Most foreseeable trigger events will fall into the category of
planned trigger events. But there might also be foreseeable trigger events that the appointing party decides
to treat as unplanned trigger events because their occurrence is so unlikely.
In addition, there can also be unforeseeable trigger events. By definition these fall into the category of
unplanned trigger events.
6.5 Planned trigger events
A planned trigger event represents an event in the life cycle of the asset that is predictable, whether or not
the precise date is known, or an event that the appointing party decides will need an urgent response.
EXAMPLES The failure of a critical component in the asset (this is predictable but the precise date of
occurrence is not known).
The service and maintenance date of a passenger lift (this is predictable and the date of
occurrence is known).
Damage to a motorway road surface during a traffic accident or damage to a shop window
during an act of vandalism or flooding of a critical asset located next to a river (these
events can be anticipated but their date of occurrence is not known, and each would need
an urgent response).
ISO/DIS 19650-3:2026(en)
For planned trigger events, the information management activities in ISO 19650-2 clauses 5.3 to 5.7 can
be undertaken well in advance of the time when information production will take place. In the case of
predictable trigger events, this means that substantial amounts of time can be saved in the response to
the trigger event because the information production teams can immediately commence the information
production activities.
Although it is helpful to identify as many planned trigger events as possible when the information
management process is first applied to the asset during ISO 19650-2 clauses 5.1 and 5.2, the appointing
party can identify additional planned trigger events at any time, as the activities in these clauses should be
applied continuously during the asset life cycle.
6.6 Unplanned trigger events
Unplanned trigger events represent events in the life cycle of the asset where the information management
activities in ISO 19650-2 clauses 5.3 to 5.7 are not completed in advance of the trigger event happening. This
can be because the trigger event has not been predicted or it is considered so irregular or unlikely that it is
not economical to spend time and resources to select and mobilize information production teams in advance
of the trigger event happening.
EXAMPLES Unforeseeable emergency situations e.g. fire or unexpected flooding.
Failure of non-critical equipment.
Major asset-related projects such as creation of a new asset or expansion of an existing asset
due to changes in business operation, changing user needs or new legislative requirements.
The nature of these unplanned trigger events means that it is only sensible, and in some instances only
possible, to carry out the project-level and appointment-level activities in ISO 19650-2 clauses 5.3 to 5.7
once the trigger event has taken place. In deciding whether a foreseeable trigger event should be treated as
planned or unplanned, the time required to carry out the selection, information planning and mobilization
activities should be taken into account.
Furthermore, some unplanned trigger events can be identified on a hypothetical basis, but not sufficiently
to enable the procurement and information planning activities to be carried out efficiently and effectively.
This is because parameters such as the scale of the project, cannot be adequately determined ahead of time.
Once an unplanned trigger event has taken place, the appointing party can subsequently treat it as a planned
trigger event if it is decided that it meets the criteria explained in clause 6.5.
6.7 Asset acquisition trigger events
Asset acquisition is different from both planned and unplanned trigger events because it only involves
appointing parties taking part in a property transaction.
The new owner, as an appointing party, should establish their information purposes and information
requirements related to the asset. They should also identify their information constraints such as preferred
data structures or file formats. However, whether they receive the information they require, or receive it
in the desired form or structure, is dependent on the information held by the existing owner who is also
an appointing party. The existing owner should decide whether or not to respond to the new owner’s
information requirements, as part of the asset acquisition transaction.
If the existing owner is not able to provide information that satisfies the new owner’s information
requirements, then the new owner should treat this situation as a new unplanned trigger event. The new
owner should then initiate projects to produce the missing information. Where an asset has multiple types
of “ownership” such as a multi-occupancy building where each occupant has their own lease and the freehold
is owned by a separate organization, then different approaches can be adopted. On the one hand, each
“owner” can be a separate appointing party going through asset acquisition. Each appointing party should
only use the information management process to develop an asset information model that aligns with their
ownership. On the other hand, all “owners” can collaborate as a single appointing party. The information

ISO/DIS 19650-3:2026(en)
management process should be used to specify asset information for the collective needs and access to
different parts of the asset information model should be restricted to each relevant “owner”.
In the case of an asset acquisition, only the information management activities in ISO 19650-2 clauses 5.1,
5.2, 5.8.7, 5.8.8 and 5.9 can be carried out. This is because the trigger event takes place between the existing
asset owner (the seller) and the new asset owner (the buyer), both of whom are appointing parties. No lead
appointed parties are involved in the transaction. The information management process is illustrated in
Figure 2.
Key
Trigger event occurs
Information management activities
1 Organizational strategy
2 Establish and maintain the asset information model
8 Information production (only activities 8.8 and 8.9 apply)
9 Project completion
Figure 2 — Information management process for an asset acquisition trigger event
7 Implementation dependent on the complexity of the asset-related project
7.1 General
Applying the ISO 19650-2 information management process in a proportionate and appropriate way is a
key principle of the standard. In the text of ISO 19650-2 this is enabled by using “shall consider” statements
to support many of the principal requirements. Details of any “shall consider” statements not
...