CEN/TR 18093:2024

Framework and Implementation of Common Data Environment solutions and workflow, in accordance with EN ISO 19650

This New Work Item will extend the basic information given in the EN ISO19650 and in the "Guidance to EN ISO 19650". It will detail and structure the concept of a Common Data Environment (CDE) as a workflow for the collaborative process of managing the information and information containers as solutions that fit to the management and project processes inherent for BIM
It may be necessary to introduce further concept details as elements for understanding and implementation. Archiving and versioning of information containers can become very complex when considering various typical information situations of a project.
Further elements, rules and terminology for information management and digitisation may need to be explained and technically framed in the context of a CDE. It will be a large advantage developing at the same time the "Open API for CDE" in TC442 WG2
In particular this Work Item will describe
- how to link a CDE according to EN ISO 19650 to an already existing Asset Management Systems of the Asset Owner.
- how to maintain and manage "living documents" like Information Models (AIM, PIM)
- how to maintain, exchange and manage Information Requirements like (OIR, AIR, EIR) as well as BIM Execution Plans (BEP)
- how to use and implement Information Delivery Plans for the above entities (MIDP and TIDP in ISO 19650)
- how to manage and collaborate between various Information Containers like models, requirements, container states
- how to support Process Workflow by a CDE based on the IDM concept
It will simply have to describe how to provide "Common Data Environment" throughout the whole life cycle (horizontal aspect) and throughout the spectrum of management levels and stakeholders (vertical aspect).
In the work item proposed here, all important terms, processes and targets are to be expanded around the CDE concept. Relations to already existing normatives will be given.
Informative attachments such as templates and examples could be provided to the benefit of planner, supplier and operator as further guidelines.

Framework und Implementierung von Common Data Environment Lösungen und Workflow nach EN ISO 19650

Cadre et mise en oeuvre de solutions et flux de travaux pour un environnement de données commun (CDE) conformément à l’EN ISO 19650

Le présent document résume et explique le concept de « solution et flux de travaux pour un CDE », abrégé ci-après par « CDE ». Le concept de CDE est essentiellement défini, mais pas expliqué en détail dans la série EN ISO 19650. En raison de la nature même de la série EN ISO 19650 la définition et l’usage normalisés du CDE décrits dans cette dernière peuvent être trop abstraits pour une mise en œuvre directe. En expliquant le concept de CDE de manière plus détaillée, le présent document sert également de document d’orientation pour sa mise en œuvre.
Ce faisant, le présent document détaille des concepts suivants introduits par l’EN ISO 19650 :
—   flux de travaux en tant que processus collaboratif de gestion des informations et des conteneurs d’information ;
—   solutions pour soutenir les processus de gestion et de projets inhérents au BIM.
L’archivage et le contrôle de version des conteneurs d’information peuvent devenir très complexes au vu des multiples situations d’information types d’un projet. Des éléments, des règles et une terminologie supplémentaire pour la gestion la numérisation des informations doivent être expliqués et techniquement encadrés dans le contexte d’un CDE. En particulier, le présent document décrit :
—   le cadre établi par les concepts faisant partie du concept CDE et s’articulant autour de ce dernier, tel que défini dans l’EN ISO 19650 ;
—   la relation entre flux de travaux et solutions en faisant la distinction entre gestion des processus et des entités à l’aide du concept de couches ; et
—   le lien entre flux de travaux et solution en utilisant des plans de livraison d’informations
(MIDP et TIDP dans l’ISO 19650).
Le présent document donne ainsi aux participants du marché et aux utilisateurs du CDE des moyens de savoir :
—   comment gérer des processus de gestion collaborative des informations selon l’EN ISO 19650 ;
—   comment gérer des entités (par exemple des conteneurs d’information tels que des modèles, des exigences, des états de conteneurs) ;
—   comment tenir à jour et gérer des documents dynamiques tels que des modèles d’information (AIM pour modèle d’information d’actif, PIM pour modèle d’information du projet) ; et
—   comment tenir à jour, échanger et gérer des exigences d’information telles qu’OIR, AIR, EIR ainsi que des plans d’exécution BIM (BEP).
Le présent document identifie l’éventail de termes importants relatifs au concept CDE ainsi que les relations associées aux références normatives pertinentes.
Le présent document est accompagné d’une étude parallèle réalisée par le CEN/TC 442 qui définit l’interface de programmation applicative pour l’interfaçage de la gestion des informations entre plusieurs CDE et solutions CDE. La présente Norme européenne (en cours d’élaboration) intitulée « API ouverte pour le CDE » est élaboré au sein d’un groupe d’étude conjoint réunissant le CEN/TC 442/GT2 et le CEN/TC 442/GT 3.

Okvir in implementacija rešitev skupnega podatkovnega okolja, v skladu z EN ISO 19650

Ta nova delovna postavka dopolnjuje osnovne informacije, podane v standardu EN ISO 19650 in v »Smernicah za standard EN ISO 19650«. V njej bo podrobno predstavljen in določen koncept skupnega podatkovnega okolja (CDE) kot potek dela za sodelovalni proces vodenja informacij in informacijskih vsebnikov kot ustreznih rešitev za upravljavske in projektne procese, značilne za informacijsko modeliranje gradenj (BIM).
Morda bo treba uvesti nadaljnje podrobnosti koncepta v obliki elementov za razumevanje in implementacijo. Če upoštevamo različne značilne informacijske situacije v projektu, lahko arhiviranje in nadzor različic informacijskih vsebnikov postaneta zelo kompleksna.
Dodatne elemente, pravila in terminologijo za vodenje informacij in digitalizacijo bo morda treba razložiti in tehnično oblikovati v kontekstu skupnega podatkovnega okolja. Velika prednost bo sočasen razvoj »odprtega API-ja za skupno podatkovno okolje« v okviru TC442 WG2.
Ta delovna postavka bo zlasti opisala:
– povezovanje skupnega podatkovnega okolja v skladu s standardom EN ISO 19650 z že obstoječimi sistemi upravljanja sredstev lastnika sredstva;
– vzdrževanje in upravljanje »živih dokumentov«, kot so informacijski modeli (AIM, PIM);
– vzdrževanje, izmenjavo in upravljanje zahtev glede informacij (OIR, AIR, EIR) ter načrtov izvedbe informacijskega modeliranja gradenj (BEP);
– uporabo načrtov dostave informacij za zgoraj navedene entitete (MIDP in TIDP v standardu ISO 19650);
– upravljanje in sodelovanje med različnimi informacijskimi vsebniki, kot so modeli, zahteve in stanja vsebnikov;
– podporo poteka dela procesov s skupnim podatkovnim okoljem, ki temelji na konceptu IDM.
Na preprost način bo moralo biti opisano zagotavljanje »skupnega podatkovnega okolja« v celotnem življenjskem ciklu (vodoravni vidik) ter v celotnem spektru ravni vodenja in deležnikov (navpični vidik).
V tukaj predlagani delovni postavki je treba vse pomembne izraze, procese in cilje razširiti okoli koncepta skupnega podatkovnega okolja. Podane bodo povezave z že obstoječimi predpisi.
V korist načrtovalca, dobavitelja in upravljavca se lahko kot dodatne smernice zagotovijo informativne priloge (npr. predloge in primeri).

General Information

• Status: Published
• Publication Date: 17-Sep-2024
• ICS: 35.240.67 - IT applications in building and construction industry
• ICS: 91.010.01 - Construction industry in general
• Technical Committee: CEN/TC 442 - Building Information Modelling (BIM)
• Drafting Committee: CEN/TC 442/WG 3 - Information Delivery Specification
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 18-Sep-2024
• Due Date: 20-Jul-2023
• Completion Date: 18-Sep-2024
• Ref Project: SIST-TP CEN/TR 18093:2024 - Framework and Implementation of Common Data Environment Solutions, in accordance with EN ISO 19650

Overview

CEN/TR 18093:2024 provides a practical framework for the Common Data Environment (CDE) and its implementation in accordance with EN ISO 19650. The technical report explains CDE concepts, workflow and solution layers, metadata, versioning and archiving of information containers, and the connection between processes and digital tools. It is intended as implementation guidance to help make the abstract CDE requirements of EN ISO 19650 directly usable in projects and asset management.

Key topics and technical requirements

• CDE as a workflow and solution: Clarifies the CDE layer model (workflow layer, connection layer, solution layer) and shows how workflows host processes composed of activities.
• Information containers & entity management: Describes management of models, documents and other information containers used for collaborative BIM information management.
• Versioning and archiving: Highlights the complexity of archiving and version control for information containers across project situations and life‑cycle stages.
• Metadata and Information Delivery Plans (IDP): Details metadata concepts and how to implement MIDP and TIDP (ISO 19650) to link workflow and solution.
• Living documents: Guidance on maintaining and managing Information Models (AIM, PIM) and other continually updated documents.
• Information Requirements and plans: Explains management and exchange of OIR, AIR, EIR and BIM Execution Plans (BEP).
• CDE-Asset Owner integration: Describes how to link a CDE (per EN ISO 19650) with existing Asset Management Systems for operational use.
• Process support using IDM: Shows how a CDE can support process workflows using the Information Delivery Manual/IDM concepts.
• Open API coordination: Notes concurrent work on an “Open API for CDE” to support interoperability and integration between CDE solutions.

Applications and users

CEN/TR 18093:2024 is practical for organizations implementing BIM-based information management:

• BIM managers and information managers - for defining CDE workflows and metadata.
• Project teams and planners - to structure information exchanges, MIDP/TIDP, and BEP/OIR workflows.
• Asset owners and facility managers - to integrate CDE outputs with Asset Management Systems (AIM).
• CDE vendors and IT integrators - to design solutions that support ISO 19650 processes and an Open API.
• Suppliers and operators - to adopt standardized container versioning, archiving and collaboration practices.

Related standards

• EN ISO 19650 series (primary normative reference)
• EN ISO 19650-1 and -4 (clauses referenced)
• DIN SPEC PAS 91391 (earlier CDE guidance)
• EN ISO 29481 (IDM guidance), EN ISO 16739-1, ISO 10303-11 and EN ISO 9000 are noted for conceptual alignment

Keywords: Common Data Environment, CDE, EN ISO 19650, BIM information management, Information Delivery Plan, information container, AIM, PIM, EIR, BEP, Asset Management, Open API for CDE.

Standards Content (Sample)

SLOVENSKI STANDARD
01-november-2024
Okvir in implementacija rešitev skupnega podatkovnega okolja, v skladu z EN ISO
Framework and Implementation of Common Data Environment Solutions, in accordance
with EN ISO 19650
Rahmenbedingungen und Umsetzungen gemeinsamer Datenumgebungslösungen nach
EN ISO 19650
Cadre et mise en œuvre de solutions et flux de travaux pour un environnement de
données commun (CDE) conformément à l’EN ISO 19650
Ta slovenski standard je istoveten z: CEN/TR 18093:2024
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.

CEN/TR 18093
TECHNICAL REPORT
RAPPORT TECHNIQUE
September 2024
TECHNISCHER REPORT
ICS 35.240.67; 91.010.01
English Version
Framework and Implementation of Common Data
Environment solutions and workflow, in accordance with
EN ISO 19650
Cadre et mise en oeuvre de solutions et flux de travaux Rahmenbedingungen und Umsetzungen gemeinsamer
pour un environnement de données commun (CDE) Datenumgebungslösungen nach EN ISO 19650
conformément à l'EN ISO 19650
This Technical Report was approved by CEN on 19 August 2024. It has been drawn up by the Technical Committee CEN/TC 442.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 18093:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviations . 8
3.1 Terms and definitions . 8
3.2 Abbreviations . 10
4 Information management according to EN ISO 19650 . 10
4.1 Information management in the normative environment . 10
4.2 Domain view . 11
5 CDE concepts and principles . 16
5.1 CDE terms and definitions . 16
5.2 CDE as an agreed source of information (see EN ISO 19650-1:2018, 3.3.15) . 16
5.3 CDE layer concept . 17
5.4 CDE metadata concept . 18
6 CDE workflow layer . 22
6.1 CDE workflow . 22
6.2 CDE process . 24
6.3 CDE activity . 26
6.4 CDE processes in EN ISO 19650 . 27
6.5 Notation of CDE workflow management systems . 31
7 CDE connection layer . 32
7.1 Metadata. 32
7.2 Information Delivery Plan (IDP) . 33
8 CDE solution layer and information container . 34
8.1 Information containers in the CDE solution layer . 34
8.2 CDE information requirements and information models . 35
8.3 CDE information container versioning and archiving . 36
Bibliography . 37

European foreword
This document (CEN/TR 18093:2024) has been prepared by Technical Committee CEN/TC 442 “Building
Information Modelling (BIM)”, the secretariat of which is held by SN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
Introduction
About the normative landscape:
EN ISO 19650 is the framework on collaborative Information Management in BIM. Its first parts were
published in the end of 2018.
To enable the market CEN/TC 442 is delivering various standards and guidelines on some of the concepts
introduced by the EN ISO 19650 series (e. g. EN ISO 7817-1 “Level of Information Need”, CEN/TR 17741
“Guidance to Information Delivery Manual IDM (based on EN ISO 29481), CEN/TR 17654 “Guidance to
EIR/BEP” - cf. Bibliography).
The UK BIM Framework serves as another example on how to enable its market. It is a collaborative effort
from British Standards Institution and NIMA (formerly the UK BIM Alliance) providing guidance on
implementation of the EN ISO 19650 series and on the transition from previous national BIM standards.
This document covers the concept of the “Common Data Environment solution and workflow (CDE)” to
support collaborative Information Management in BIM.
Preliminary work to explain what a CDE is and how it can be implemented has previously been done by
a national initiative within the German mirror committee of CEN/TC 442 in DIN. The result was published
in March 2019 as DIN SPEC PAS 91391 “CDE”.
This document is accompanied by a work item on “Open Application Programming Interface (API)”
defining a technical interface for a CDE. This work is launched in parallel in CEN/TC 442/WG 2.
Enabling market:
The EN ISO 19650 series of standards requires implementers to have at least a base level of
understanding of concepts and options and on how to apply the processes in practice. Market participants
applying and engaging in information management with BIM according to EN ISO 19650 therefore face a
range of approaches. The CDE component is particularly challenging as it is often falsely only considered
to be a technology requirement rather than consistent work process obligation. They can have the option
to manage workflow or include integration of application programming interfaces (API) to various CDE
solutions. Exchanging information containers (cf. EN ISO 19650-1:2018, 3.3.12) and exercising process
management will need a suitable metadata concept. Avoiding inconsistency of deployment from project
to project, from asset to asset requires a functionally sound CDE already at the start of the project. This
document will provide guidance for users. The work item on CDE Open API will provide further details
on how to implement respective interfaces in a CDE solution.
Understanding semantics:
The EN ISO 19650 series provides and defines a collection of new terms, concepts and principles (cf. part
1). At the same time, it also provides rules, requirements and conditions attached to them. The present
Technical Report illustrates the semantics of these elements in a stringent way using a combined schema
notation. The semantic schemata used in this document combine (see figure 1 and figure 2):
— a class diagram according to UML to visualize the entity relationships with (dotted lines),
— a triple graph according to RDF to visualize the process interdependencies (full lines) - while actor-
action-artefact/target can be seen as an specific example of subject-predicate-object.
Key
RDF triple concepts are composed of full lines with the predicate on the line

Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

Figure 1 — Key to the combined semantic schema

Key
RDF triple concepts are composed of full lines with the predicate on the line

Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

(3.3.12) References to EN ISO 19650-1:2018 are given by the clause number in "normal" brackets.
[3.3.12] References to EN ISO 19650-4:2022 are given by the clause number in squared brackets.
Figure 2 — Example of a combined semantic schema visualizing entity relationship (is type of)
and activity triple (subject-predicate-object/actor-action-artifact, e.g. “party expresses
specification”)
The combination of part of/type of relations with process semantics provides a more holistic view. This
view suits better to understand the combination of information entities and processes managed by the
workflow of CDE.
Workflow concept in the CDE concept:
Workflow is a term being used in the title of clause 12 in EN ISO 19650-1:2018, but it is only superficially
defined within EN ISO 19650 series. There are several ISO based definitions for workflow specific for and
within the environment in which they are being used. Generalizing them results in the following:
Workflow is the main concept hosting processes (see figure 3). Processes are being made up by activities
(reference ISO 12651-2 and EN ISO 9000:2015, 3.4.1). In a way an activity as the basic element of
workflow can be compared with an information container being the basic element of information
management.
Figure 3 — Workflow as a combination of processes composed by activities
Entity concept in terms of CDE:
Entity management in a CDE explained here uses the concept of information container (EN ISO 19650-
1:2018, 3.3.12). It is slightly different to the entity concept used in EN ISO 16739-1. The entity concept in
EN ISO 16739-1 is embedded in an object-orientated environment (model language of ISO 10303-
11:2004). The entity concept in EN ISO 19650 series rather uses entity as a static concept in contrast to
the dynamic concept of a process. Information container used in ISO 19650 and this document can be
understood as a type of an entity in the general semantic meaning of entity.
1 Scope
This document summarizes and explains the concept of “CDE solution and workflow” - hereby
abbreviated by ”CDE”. The concept of CDE is primarily defined but not extensively explained in EN ISO
19650 series. Due to the very nature of the EN ISO 19650 series the standardized definition and usage of
CDE described in the very series can be too abstract for direct implementation. By explaining the CDE
concept in more detail this document will also serve as an implementation guidance.
Doing so this document will detail the following concepts introduced by EN ISO 19650:
— workflow as a collaborative process of managing the information and information containers,
— solutions to support the management and project processes inherent for BIM.
Archiving and versioning of information containers can become very complex when considering various
typical information situations of a project. Further elements, rules and terminology for information
management and digitisation needs to be explained and technically framed in the context of a CDE. In
particular this document describes:
— the framework established by the concepts in and around the CDE concept of EN ISO 19650,
— the relation between workflow and solution by differentiating between process and entity
management using the layer concept and
— the connection between workflow and solution by using Information Delivery Plans (MIDP and TIDP
in ISO 19650).
This document enables thereby the market participant and CDE user on:
— how to manage processes in collaborative information management according to EN ISO 19650,
— how to manage entities (e.g. Information Containers like models, requirements, container states),
— how to maintain and manage “living documents” like Information Models (AIM, PIM) and
— how to maintain, exchange and manage Information Requirements like (OIR, AIR, EIR) as well as BIM
Execution Plans (BEP).
This document identifies the range of important terms related to the CDE concept and associated
relationships to relevant normative references.
This document is accompanied by a parallel work item within CEN/TC 442 defining Application
Programming Interface for the information management interfacing between various CDE and CDE
solutions. This European standard (under development) named “Open API for CDE” is being developed
within a Joint Task group of CEN/TC 442/WG2 and CEN/TC 442/WG 3.
2 Normative references
There are no normative references in this document.
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology 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/
3.1.1
activity

actor-action-artifact triple
[SOURCE: RDF W3C - w3.org/TR/PR-rdf-syntax, WfMC - wfmc.org]
3.1.2
activity

description of a piece of work that forms one logical step within a process
Note 1 to entry: Activity is the basic unit of work within a process. Presumably work can be subdivided into units
- smaller than a given activity, but it is not meaningful for the organization to track work down to that level of detail.
Note 2 to entry: Synonyms of activity are node, step, and task.
[SOURCE: ACM - Adaptive Case Management, Swenson, Keith D. (2010), modified]
3.1.3
action
verbal noun (gerund) relating to the predicate in the subject-predicate-object triple of an activity
[SOURCE: WfMC - wfmc.org]
3.1.4
actor
person, organization or organizational unit involved in a construction process
[SOURCE: EN ISO 19650-1:2018, definition 3.2.1]
3.1.5
artifact
work item as target of an action in an activity
[SOURCE: WfMC - wfmc.org]
3.1.6
process
< Workflow Managment Coaltion (WfMC) - wfmc.org context>
set of one or more linked activities that realize an objective or policy goal, normally within the context of
an organizational structure defining functions and relationships
Note 1 to entry: A process consists of activities.
[SOURCE: ACM - Adaptive Case Management, Swenson, Keith D. (2010), modified]
3.1.7
process
< Workflow Managment Coaltion (WfMC) - wfmc.org context>
set of activities
[SOURCE: WfMC - wfmc.org]
3.1.8
process instance
data structure that represents a particular instance of running of a process
Note 1 to entry: A process instance has associated context information that can be used and manipulated by the
process.
Note 2 to entry: A process instance plays a role in a business process management system (BPMS) that is very
similar but not exactly the same as a case in a case management system. A particular case can have more than one
process instance associated with it.
[SOURCE: ACM - Adaptive Case Management, Swenson, Keith D. (2010)]
3.1.9
workflow
< Workflow Managment Coaltion (WfMC) - wfmc.org context>
logical and sequential schema allowing to design, execute, monitor, change and optimise one or more
processes in its logical sequence in combination with CDE functions
Note 1 to entry: A CDE workflow can be part of a business case like information technology, roles and projects.
Note 2 to entry: Synonyms include process definition.
EXAMPLE: A CDE workflow can describe the passing of documents, information or tasks from one participant to
another according to a given set of procedural rules.
[SOURCE: WfMC - wfmc.org, modified]
3.1.10
workflow
< Workflow Managment Coaltion (WfMC) - wfmc.org context>
automation of a process, in whole or part during which documents, information or tasks are passed from
one participant to another for action according to a set of procedural rules
Note 1 to entry: Synonyms include process definition.
[SOURCE: ACM - Adaptive Case Management, Swenson, Keith D. (2010), modified]
3.2 Abbreviations
A list of abbreviated terms is given in table 1.
Table 1 — abbreviated terms
abbreviation source URI
WfMC Workflow Management Coalition wfmc.org
Mastering the Unpredictable: How
Adaptive Case Management Will
ACM Adaptive Case Management Revolutionize the Way That
Knowledge Workers Get Things
Done, Swenson, Keith D. (2010)
RDF W3C Resource Description Framework w3.org/TR/PR-rdf-syntax
4 Information management according to EN ISO 19650
4.1 Information management in the normative environment
This document is rooted in the EN ISO 19650 series. Clauses 11 and 12 of EN ISO 19650-1:2018 introduce
the concept of “Common Data Environment - solution and workflow (CDE)” as an indispensable
component of information management according to the EN ISO 19650 series. The following schema (see
figure 4) lists more concepts of information management introduced with EN ISO 19650 series. Along the
dotted line the normative references and relations are given as quoted within EN ISO 19650-1:2018.
Key
RDF triple concepts are composed of full lines with the predicate on the line

Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

(3.3.12) References to EN ISO 19650-1:2018 are given by the clause number in "normal" brackets.
Figure 4 — Concepts of information management described in more detail in EN ISO 19650-
1:2018 and related standards (CC-BY-NC-SA 3.0)
4.2 Domain view
4.2.1 General
Information management according to the EN ISO 19650 series can be grouped into the domains formed
by the concepts established in the EN ISO 19650 series (see figure 5). These concept domains can be
— appointment,
— information production and
— information exchange.
Within these domains, specific terms and processes cluster around these main concepts. This clustering
is visualized in this document. The domains are connected and covered by the overall concept of CDE.
Elements mainly used in one domain can though also be used in another domain.

Figure 5 — CDE information management by process domains (CC-BY-NC-SA 3.0)
4.2.2 Appointment domain
The appointment process of EN ISO 19650-1:2018 initiates information management. EN ISO 19650-2
and EN ISO 19650-3 detail setting up the CDE prior to the appointment. The appointment domain
contains various entities and concepts visualized using the semantics explained in introduction (see
figure 6).
Key
RDF triple concepts are composed of full lines with the predicate on the

line
Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

(3.3.12) References to EN ISO 19650-1:2018 are given by the clause number in
"normal" brackets.
Figure 6 — Appointment process described in more detail in EN ISO 19650-1:2018 (CC-BY-NC-SA
3.0)
4.2.3 Information production domain
Information production is instructed by the appointment process. Although used as terms within the
normative text - “task” and “project” are not defined in EN ISO 19650-1:2018, Chapter 3 “Terms and
definitions”. Usage of task and project is visualized in figure 7 in terms of dependent processes.
Key
RDF triple concepts are composed of full lines with the predicate on the line

Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

(3.3.12) References to EN ISO 19650-1:2018 are given by the clause number in "normal" brackets.
Figure 7 — Information production and related processes described in more detail in
EN ISO 19650-1:2018 (CC-BY-NC-SA 3.0)
4.2.4 Information exchange domain
Information exchange is described in detail in EN ISO 19650-4:2022. EN ISO 19650-4:2022 uses slightly
different terms than EN ISO 19650-1, EN ISO 19650-2 and EN ISO 19650-3. Based on the sequence of
information container states (cf. metadata concept above) an information exchange (see figure 8) is
managed by:
— actors (provider, receiver, reviewer) generalizing e.g. appointing and appointed party,
— sub processes (execute, check, deliver, etc.) generalizing e.g. appointment process and
— criteria (conformance, continuity, etc.) generalizing e.g. information requirement.
Key
RDF triple concepts are composed of full lines with the predicate on the line

Directed process/activity
"is part of" relations set definitions

"is type of" relations class definitions

(3.3.12) References to EN ISO 19650-1:2018 are given by the clause number in "normal" brackets.
[3.3.12] References to EN ISO 19650-4:2022 are given by the clause number in squared brackets.
Figure 8 — Information exchange described in more detail in EN ISO 19650-4:2022 - referenced
clauses numbered in squared brackets [.] (CC-BY-NC-SA 3.0)
5 CDE concepts and principles
5.1 CDE terms and definitions
This document uses terms and their definitions when information management uses a common data
environment solution and workflow (CDE). Main concepts have been introduced in the
EN ISO 19650 series. Missing definitions are covered by this document.
— workflow, process, and activity (developed by the Workflow Management Coalition) and
— metadata (detailed by various normatives within specific environments).
EN ISO 19650 series knows two types of elements:
— entities aka information containers (e.g. information models) and
— information processes (e.g. information exchange).
Information containers and information processes are the fundamental elements of a CDE solution and
workflow. Information processes constitute the CDE workflow. The CDE solution provides the
technological implementation to manage the workflow.
Information containers are immaterial, intangible existences. A typical example of an information
container is an information model described in more detail in EN ISO 19650-1:2018, 3.3.8. A typical
example of an information process is the information exchange is described in more detail in EN ISO
19650-1:2018, 3.3.7, and EN ISO 19650-4:2022.
5.2 CDE as an agreed source of information (see EN ISO 19650-1:2018, 3.3.15)
This technical report uses terms and their definitions when information management uses a common
data environment solution and workflow (CDE). Main concepts have been introduced in the
EN ISO 19650 series. Missing definitions are covered by this document.
CDE solution and workflow is defined as an “agreed source of information for any given project or asset,
for collecting, managing and disseminating each information container through a managed process”, with
a note that “A CDE workflow describes the processes to be used and a CDE solution can provide the
technology to support those processes” (ISO 19650-1:2018, 3.3.15).
The purpose of a CDE is to provide a trusted source so that all parties have access to the most up-to-date
and accurate information. This can be delivered through a “Project and asset in-use CDE” solution.
However, it is possible for a CDE to have multiple solutions, depending on the way it is configured and
used. For example, if a CDE is set up to allow multiple teams to work on the same project using different
solutions, each team can have its own source that can be trusted to provide the most up-to-date and
accurate information.
Additionally, supporting other parties need for trusted information can be challenging to implement in
practice, as it requires all parties involved in the project to consistently and accurately update, track and
maintain information across solutions. Parties not having access to the most up-to-date and accurate
information a workflow transition does not complete as planned. This can be difficult to achieve in
complex and dynamic construction projects, where different teams may have different priorities and
objectives.
5.3 CDE layer concept
This document uses terms and their definitions when information management uses a common data
environment solution and workflow (CDE). Main concepts have been introduced in the
EN ISO 19650 series. Missing definitions are covered by this document.
The CDE concept has evolved from an entity-focused project data management system (PDMS) of the
British Standard BS 1192:2007 and UK PAS 1192-2:2013 to a more process-oriented solution and
workflow management system of EN ISO 19650-1:2018. “Common Data Environment (CDE) solution and
workflow" covers both the process for collecting, managing and distributing information containers, and
the technology which supports this process (ISO 19650-1:2018, Chapter 11 and 12). Whereas
information containers are regarded as entities.
This definition of a Common Data Environment can be visualized by a layer concept. A layer concept is an
abstract model to understand a system by modularizing its components. Whereas an element of an upper
layer needs the support of the lower layer - like a higher building storey cannot exist without the stories
below.
A Common Data Environment can be envisioned by a three-layer system - the upper layer hosting
workflows and processes and the lower layer supporting these workflows - the solution. An intermediate
connection layer is introduced between these two layers to specify a potential interface between
workflow and solution (see figure 9).

Figure 9 — CDE supplying process management and technology support (CC-BY-NC-SA 3.0)
Workflow Management is process management. The CDE Workflow layer is a process management layer.
Components of a CDE workflow are
— process(es) being designed, executed, monitored, changed and optimized and
— function(s) being defined and given by a project environment of the CDE.
The CDE solution layer must provide a solution for information container management. This CDE solution
layer will provide
— one or more information container management systems and
— control/application interface instances to the process management layer.
Key
G decision gateway (trigger event)
P process (logically consecutively numbered)
IC information container (with GUID/UUID)
V version (numbered in timeline sequence)
Figure 10 — CDE solution and workflow - process and entity management (CC-BY-NC-SA 3.0)
A CDE solution (see figure 10) manages one or many processes as a part of the CDE workflow including
processes to meet the needs of general or specific requirements for various purposes, such as
coordination, clash detection, and quantity take-off (e.g. modelers, viewers or authoring tools).
5.4 CDE metadata concept
5.4.1 General
Metadata (or meta-information) is structured data containing information about a larger information
repository. A short but incomplete definition is “metadata is data on data”. Metadata is used to classify
the content of a larger data repository. This allows
...