ETSI ES 204 114 V1.1.1 (2025-10)

ETSI STANDARD
Access, Terminals, Transmission and Multiplexing (ATTM);
Meta-model entities/relationships opendthX
data/applications interoperability

2 ETSI ES 204 114 V1.1.1 (2025-10)

Reference
DES/ATTM-0020013
Keywords
application, data interoperability,
data management, intelligent homes & buildings,
interoperability, management, smart cities
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI ES 204 114 V1.1.1 (2025-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Executive summary . 5
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 12
3.3 Abbreviations . 12
4 Introduction to the data interoperability format for connected buildings . 13
5 Cases of information in the construction industry . 13
5.1 Inventory of players involved in construction data exchange . 13
5.2 Inventory of targeted use cases . 14
5.3 Inventory of types of construction data exchanged . 15
6 Lifecycle of an object as part of a construction project and its operation . 17
6.1 Introduction to the Object Lifecycle in the BIM process . 17
6.1.1 From Design to Operation: An Integrated Vision based on ISO 19650 Standards . 17
6.1.2 A Structuring Duality: PIM and AIM . 18
6.1.3 Progressive Maturation in PIM . 18
6.1.4 The Specific Object as the Foundation of AIM . 18
6.1.5 An integrated approach to optimizing the entire life cycle . 18
6.2 The Evolution of BIM Objects in the PIM Cycle: From Conceptual to Concrete . 19
6.2.1 Introduction. 19
6.2.2 Progressive Information Maturation . 19
6.2.3 Information continuity and traceability. 19
6.2.4 A collaborative, multi-stakeholder approach . 20
6.2.5 Conclusion: A Solid Foundation for the Full Life Cycle . 20
6.3 The Generic Object Model (GOM) . 20
6.3.1 Definition and role of the GOM . 20
6.3.2 Property group structure . 20
6.3.3 GOM Creation Process . 21
6.3.4 Transition to Later Phases . 21
6.3.5 The Importance of the GOM in the BIM Process . 21
6.4 The Generic Object: Making Requirements a Reality in the BIM Process Lifecycle . 22
6.4.1 From Abstraction to Concretization: The Evolution from GOM to Generic Object. 22
6.4.2 Collaborative Enrichment by Different Actors . 22
6.4.3 Property valuation mechanisms . 22
6.4.4 Interdependency and arbitrage management . 22
6.4.5 Position in the PIM Process . 23
6.4.6 Transition to Later Phases . 23
6.5 The Specific Object: Technical Realization in the BIM Process Lifecycle . 23
6.5.1 Transition from Requirement to Concrete Solution . 23
6.5.2 Dual Property Structure . 23
6.5.3 Selection and Specification Process . 24
6.5.4 Enrichment by Value Chain Actors . 24
6.5.5 Manufacturer data integration . 24
6.5.6 Managing variants and alternatives. 25
6.5.7 Preparing the transition to AIM . 25
6.5.8 Strategic position in the BIM process . 25
ETSI
4 ETSI ES 204 114 V1.1.1 (2025-10)
6.6 The Role of the Specific Object in the AIM Phase . 25
6.6.1 Transition from Specific Object to AIM . 25
6.6.2 AIM Information Foundation . 25
6.6.3 Enrichment and Evolution in AIM . 26
6.6.4 Maintenance Operations Support . 26
6.6.5 Contribution to Performance Analysis and Decision Making . 26
6.6.6 Preparing for Renewal and Evolution . 26
6.7 Conclusion: Towards integrated, continuous information management . 27
6.7.1 Overview of the BIM Object Lifecycle Approach . 27
6.7.2 Benefits an Integrated Approach . 27
6.7.3 Challenges. 27
6.7.4 Outlook . 28
6.7.5 The New Horizon of Digital Construction . 28
7 Data interoperability . 28
7.1 Challenges . 28
7.2 The advantages . 28
7.3 The benefits of dynamic dictionaries for the specific use case of data exchange . 29
8 Complementarities and synergies between opendthX and SAREF for connected buildings . 29
8.1 Introduction . 29
8.2 SAREF4BLDG Example . 31
9 Semantic, organizational and technical interoperability . 34
9.1 Semantic interoperability: The COPO method . 34
9.2 Organizational interoperability: CIQO process . 34
9.3 Technical interoperability . 36
9.3.1 Language construction . 36
9.3.2 IFC files: a first revolution in construction . 36
9.3.3 IFC files have several essential characteristics: . 36
9.3.4 File-based exchange: from XML to JSON-LD . 36
9.3.5 API exchanges: fluidity and responsiveness . 37
9.3.6 Converging and complementary approaches . 37
9.3.7 Future prospects . 37
9.3.8 Conclusion / opendthX meta-model . 38
9.3.8.1 opendthX metamodel JSON v3.0 . 38
9.3.8.1.1 Schema: . 38
9.3.8.1.2 Description of the datBIM v3 API. 38
9.3.8.2 Open REST API of the opendthX JSON v4.0 meta model . 42
9.3.8.3 opendthX meta model similar JSON LD self-discoverable V1.0. 42
9.3.8.4 Summary diagram . 43
9.3.9 OpenCDE . 43
Annex A (informative): Metamodel opendthX JSON-LD v1.0 . 47
Annex B (informative): Schematics . 52
Annex C (informative): Bibliography . 55
Annex E (informative): Change history . 56
History . 57

ETSI
5 ETSI ES 204 114 V1.1.1 (2025-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Access, Terminals, Transmission and
Multiplexing (ATTM).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
The opendthX open meta-model is designed to ensure interoperability between digital content and construction industry
software, enabling all parties involved in a construction project to contribute to the BIM process (see Figure B.1), in
particular for:
• access to all types of content via all types of applications, regardless of the tools used;
• enriching objects for advanced collaborative construction;
• standardize input data in construction software avoid the GIGO effect (i.e. Garbage In → Garbage Out) (see
Figure B.3);
ETSI
6 ETSI ES 204 114 V1.1.1 (2025-10)
• with the aim of creating a "CIQO-ready" collaborative environment: "Collaboration In → Quality Out" (see
Figure B.2):
- optimize data transfers using the concept of data on demand, thus meeting the need for digital sobriety;
- establish digital continuity throughout the lifecycle of the project: design-construction-operations,
including the use of connected objects.

ETSI
7 ETSI ES 204 114 V1.1.1 (2025-10)
1 Scope
The present document presents the opendthX entity/relationship meta-model for interoperability between data and
applications.
The purpose of the present document is to establish a framework to ensure interoperability between digital content and
software applications in the construction industry. It aims to facilitate access to various types of content through
different applications, regardless of the tools used, thereby promoting advanced collaborative construction practices.
The standard aims to standardize input data to construction software in order to avoid the "Garbage In Garbage Out"
(GIGO) effect, by ensuring that quality input data and applications result in quality output data.
The main objectives are to optimize data transfers through the concept of data on demand, which promotes digital
sobriety, and to establish digital continuity throughout the lifecycle of construction projects, from design and
construction to operation, including the use of connected objects. The standard introduces the opendthX open
meta-model, designed to enable seamless interoperability and collaboration between all stakeholders in a construction
project.
In addition, the standard addresses the integration of semantic, organizational and technical interoperability, providing
methodologies and frameworks such as the use Cases-use Objects-Properties-modelled Objects (COPO) method for
semantic interoperability and the Collaboration In Quality Out (CIQO) process for organizational interoperability. It
also covers technical aspects such as the context for using IFC files, JSON-LD and APIs for efficient data exchange.
Overall, the standard aims to improve the efficiency, sustainability and adaptability of the construction sector by
harnessing the full potential of the digital transformation from appli-centrism to open data-centrism through
data-application interoperability.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 673: "SmartM2M; SAREF Development Framework and Workflow, Streamlining
the Development of SAREF and its Extensions".
[2] ISO 16739-1:2024: "Industry Foundation Classes (IFC) for data sharing in the construction and
facilities management industries — Part 1: Data schema".
[3] ISO 23386:2020: "Building information modelling and other digital processes used in construction
— Methodology to describe, author and maintain properties in interconnected data dictionaries".
[4] ISO 19650 (all parts): "Organization and digitization of information about buildings and civil
engineering works, including building information modelling (BIM) — Information management
using building information modelling".
[5] ETSI TS 103 548: "SmartM2M; SAREF reference ontology patterns".
[6] buildingSMART: "Industry Foundation Classes (IFC) - Version 4 - Addendum 1".
[7] ETSI TS 103 410-3 (V1.1.1): "SmartM2M; Smart Appliances Extension to SAREF; Part 3:
Building Domain".
ETSI
8 ETSI ES 204 114 V1.1.1 (2025-10)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding but are not required for conformance to the present document.
[i.1] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on
public procurement and repealing Directive 2004/18/EC.
[i.2] French decree n 2018-1075 of December 3, 2018, Article R2132-10.
NOTE: The law authorizes the buyer to use electronic building data modelling tools.
In this case, it offers the means access mentioned in article R. 2132-14, until such time as these tools and
devices have become commonly accessible to economic operators.
[i.3] Under Belgian law: June 17, 2016 - Public Procurement Act.
[i.4] Legal approach to interoperability: Interoperability is a right of use within the meaning of article
L122-6-1 of the French Intellectual Property Code, in the version in force on November 26, 2021.
NOTE: Software is protected by copyright, except as interoperability.
[i.5] European Data Governance Act 30/05/2022.
[i.6] Proposal for European Data Protection Act - 23/02/2022.
[i.7] Study report on the comparative cost of creating a technical database of digital mock-up
components. BIM virtual workshop project carried out as part of the French government's digital
building transition plan. Version 2 of the document dated 11/04/2017.
NOTE See figures 4 and 5. Doc1_Etude2_ABV_BDD_20170411.pdf.
[i.8] Michel Léglise and Bernard Ferriès: "Evaluation of the costs of interoperability borne by
contractors, project owners and operators in the construction and operation of buildings". Final
report of study 08E86 commissioned by the FFB (Fédération Française du Bâtiment),
LAURENTI. December 2009.
NOTE: See figures 4 and 5. Doc2_Rapp_Final_FFB_35_cout_interoperability2009.pdf.
[i.9] "The Référentiel Général d'Interopérabilité Version 2.0", December 2015 developed by the French
government's Direction Interministérielle de l'Economie Numérique et du Système d'Information
et de Communication.
NOTE: This is a list of standards for given use cases.
Scope of exchanges:
 between administrations;
 between administrations and companies;
 between administrations and citizens. ®
[i.10] W3C Semantic Web: "Resource Description Framework (RDF)". ®
[i.11] W3C Recommendation 16 July 2020: "JSON-LD 1.1 - A JSON-based Serialization for Linked
Data". ®
[i.12] W3C editor's project: "The JSON-LD vocabulary".
[i.13] JSON for Linking Data.
ETSI
9 ETSI ES 204 114 V1.1.1 (2025-10)
[i.14] Schema.org.
[i.15] JDN: "Data centricity", 27/03/2019.
[i.16] ETSI TR 103 781 (V1.1.1): "SmartM2M; Study for SAREF ontology patterns and usage
guidelines".
[i.17] EN 13501-1: "Fire classification of construction products and building elements - Part 1:
Classification using data reaction to fire tests", (produced by CEN).
[i.18] NF XP P07-150 (12-2014): "Properties of products and systems used in construction - Definition
of properties, method of creation and managing properties in a harmonized system of reference".
[i.19] ISO 23387: "Building information modelling (BIM) — Data templates for construction objects
used in the life cycle of built assets — Concepts and principles".
[i.20] OPIIEC: "Study on skills, employment and training requirements for the digital twin in France",
05/01/2024.
[i.21] "Open formats, what for?", April.org.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
appli-centrism: IT development method based on developing an application using data that can only be used in that
application
NOTE: This characterizes a computer application development method which involves integrating input data via
a dedicated graphical interface for the processing envisaged by the application and rendering the
processing in a native format. In this case, the application acts as a data repository. In this logic, the user
should have as many data repositories as applications, and therefore as many use cases, which implies
re-entering information or developing specific connectors for each link envisaged.
attribute: data element used to describe a property or a group of properties a computer-suitable way
authorization: function specifying access rights to resources linked to information security and information systems
security in general, and to access in particular
NOTE: More formally, "authorizing" means defining an access policy.
Avis Technique (AT) (technical notice): document formalizing the opinion issued by a group of experts on the
suitability for use of innovative construction processes
NOTE: The CSTB is involved in the technical opinion procedure at several levels and provides the secretariat.
CSTB has carried out a study demonstrating the ability of the opendthX format to describe the AT.
Building Information Modelling (BIM): use of a shared digital representation of a built asset (buildings, bridges,
roads, factories, etc.) to facilitate the design, construction and operation processes and provide a reliable basis for
decision-making
NOTE: See ISO 19650 [4].
class: group of properties
computer object: instance of the class that can be considered as the digital representative of a construction object
NOTE: In the remainder of the present document, the object will be considered as a computer object. The object
or object model is defined for the purpose of exchanging data for a specific use case.
ETSI
10 ETSI ES 204 114 V1.1.1 (2025-10)
construction object: object of interest in a construction process
NOTE: In accordance with ISO 23387 [i.19].
data-centricity: IT development method involving the development applications using standardized data that can be
used in other applications
NOTE: Behind this name lies an approach that places data at the heart of the company and requires it to be
considered an asset in its own right, in the same way as patents, for example. It would be frustrating and
incomprehensible to create an entirely new business without mastering this asset. The data-centric
approach aims to turn the tables and make data the cardinal point of a company's strategy.
Source JDN 27/03/2019 [i.15].
©
datBIM : company that developed the opendthX format and then licensed it to the Alliance du bâtiment association to
govern and promote it
digital content: library or catalogue of objects that are collections of objects
digital twin: digital duplication of a physical entity or product
NOTE: The digital twin is the digital double of a real object, process or system, made up of interoperable
applications and data and developed to meet well-defined uses.
It is fed by data flows from the real entity at a defined frequency, to adjust to needs and uses in real
conditions. The digital twin makes it possible to understand, analyse and predict the behaviour of the real
entity, in order to support decision-making in its management and operation [i.20].
entity: thing capable of existing independently, uniquely identifiable and capable of storing data
NOTE: In the context of the entity-relationship model, an entity has properties or attributes.
eXtensible Markup Language (XML): subset of the Standard Generalized Markup Language (SGML)
NOTE: Its syntax is said to be "extensible" because it can be used to define different languages, each with its own
vocabulary and grammar, such as XHTML, XSLT, RSS, SVG, opendthX and so on.
Garbage In Garbage Out (GIGO): well-identified risk in systems engineering: poor-quality input data produces
poor-quality output data (results)
generic object: set of property/value pairs that are dissociated from a manufacturer's product brand and whose values
may be requirement values or correspond to generic, standard range values
generic object model or object description model: set of value-free properties that can also be assimilated to a class
identification: means of "knowing" the identity an entity
NOTE: Often by means of an identifier such a user name (distinct from identity , or authentication).
Industry Foundation Classes (IFC): standardized object-oriented file format [2] used by the construction industry to
exchange and share information between software programs
NOTE: Promoted by the international organization buildingSMART International and its national chapters.
integrity: state of data which, during processing, storage or transmission, is not altered or destroyed, whether
intentionally or accidentally, and retains a format that allows it to be used
NOTE 1: Data integrity comprises four elements completeness, precision, accuracy/authenticity and validity.
NOTE 2: Integrity is one of the basic requirements of IT security, document management and archiving.
JavaScript Object Notation (JSON): textual data format derived from the object notation of the JavaScript language
NOTE: It competes with XML for the representation and transmission of structured information.
ETSI
11 ETSI ES 204 114 V1.1.1 (2025-10)
JavaScript Object Notation for Linked Data (JSON LD): method encoding structured data using JSON
NOTE: The aim is to provide developers with a simple way of transforming existing JSON data into JSON-LD.
This enables data to be serialized in the same way as with traditional JSON. JSON-LD is a
recommendation of the World Wide Web Consortium and is therefore considered a standard. Source: ®
Wikipedia .
See [i.10], [i.11], [i.12], [i.13] and [i.14].
metadata: data used to define or describe another piece of data, determining its medium
NOTE: Term derived from the Greek prefix meta, meaning "beyond" or "about".
EXAMPLE: Metadata can indicate the date of creation or recording a piece of data, or the geographic
coordinates associated with a photograph.
opendthX: open data format designed to ensure interoperability between digital content and software in the
construction sector
NOTE This format is governed by the construction industry through the non-profit association Alliance du
bâtiment.
open format: freely usable data format
NOTE: Open format files can be read and modified by yourself or by third parties. Readability is guaranteed over
time. Open formats are freely usable in any software, making software interoperable. Open formats
promote freedom of choice by not favouring the format of a particular company (known as the native or
proprietary format), thus avoiding the monopoly of a publisher who would like to make users captive to
the proprietary format it has designed [i.21].
property: inherent or acquired characteristic of an element (project, system, product, etc.)
NOTE 1: ISO 23386 [3] (produced based on the French experimental standard NF XP P07-150 [i.18] published in
2015) provides an exhaustive list of 40 attributes used to manage a property in a data dictionary.
EXAMPLE: Reaction to fire measured in accordance with EN 13501-1 [i.17].
A property can be:
- Static: the value is predefined by the object designer.
- Configurable or parameterizable: the value is defined by the user.
- Dynamic: the value changes according to the object's physical state. Example: temperature measured by
a thermometer-type sensor.
- Relation: association.
NOTE 2: According to the entity-relationship model, a relationship is a link between two or more entities. A
relationship can have properties or attributes.
- Traceability: situation in which the necessary and sufficient information is provided to know (possibly
retrospectively) the composition of an object throughout its production, transformation and distribution
chain
property group: set of properties with no value
NOTE: According to ISO 23386 [3], there are different categories of property groups:
 Class.
 Compound property.
 Domain.
 Reference document.
 Other uses.
ETSI
12 ETSI ES 204 114 V1.1.1 (2025-10)
specific object: set of property/value pairs whose values are the performances of a manufacturer's product
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABV Atelier BIM Virtuel (Virtual BIM Workshop)
AI Artificial Intelligence
AIM Asset Information Model
APD Avant Projet Détaillé (detailed design)
API Advanced Programming Interface
APS Avant Projet Sommaire (Preliminary design)
AT Avis Technique (technical notice)
BIM Building Information Modelling
BMS Building Management System
CAD Computer-Aided Design
CIQO Collaboration In Quality Out
COPO use Cases, use Objects, Properties, modelled Objects
CRUD Create, Read, Update, Delete
CSTB Scientific and Technical Centre for Building
DatSPIN Données actualisées techniques pour une Stratégie du Patrimoine Immobilier Numérique
(pp-to-date technical data for a digitized real estate strategy)
DCE Dossier de Consultation des Entreprises (specification booklet)
DOE Dossier des Ouvrages Exécutés (completed works file )
DTU Unified Technical Documents
ERP Enterprise Resource Planning
FDES Fiche de Données Environnementales et Sanitaires
GDP Gross Domestic Product
GIGO Garbage In Garbage Out
GO Generic Object
GOM Generic Object Model
IFC Industries Foundation Classes
IOT Internet Of Things
JDN Journal Du Net
JSON JavaScript Object Notation
JSON-LD JavaScript Object Notation for Linked Data
opendthX Open Dictionnaire Technique Harmonisé eXchange (exchange of technical dictionaries
harmonized)
PCBIM Building Permit BIM
PIM Project Information Model or Product Information Management
POBIM Properties of BIM Objects
RSS Really Simple Syndication
SAREF Smart Applications REFerence ontology
SGML Standard Generalized Markup Language
SO Specific Object
SVG Scalable Vector Graphics
XHTML eXtensible HyperText Markup Language
XML eXtensible Markup Language
XP eXperimental Standards
NOTE: Identified by the prefix "XP".
XSLT eXtensible Stylesheet Language - Transformations
ETSI
13 ETSI ES 204 114 V1.1.1 (2025-10)
4 Introduction to the data interoperability format for
connected buildings
The digital transformation of the construction sector can accelerate its environmental transformation, provided that it
enables everyone to work together, which presupposes that data is interoperable with applications.
The specific characteristics of the construction sector that need to be taken into account to make this transformation a
success:
• A fragmented sector: A large majority of construction companies have fewer than 20 employees.
• The political stakes are high:
- the environment: the biggest consumer of energy and the biggest producer of waste;
- economic: exchanges of construction data represent 25 % of GDP in Europe, based on studies carried out
in France;
rd
- social: 3 in terms of direct recruitment, after services and industry.
• Digital modelling of construction projects is encouraged by public procurement regulations (see [i.1], [i.2] and
[i.3]), provided that this requirement does not create technological barriers for any of the players involved.
• The costs attributable to the lack of interoperability in Europe are estimated at over one hundred billion euros
per year, extrapolated from studies carried out in France (see [i.7] and [i.8]).
• The operating cost a building represents 70 to 80 % of its total cost.
• Convergence between buildings and telecommunications via the Internet of Things (IOT) or connected
objects.
• Numerous software applications: over 300 construction software publishers in France alone.
• The digital transition in the construction sector means moving from an application-centric to an open data-
centric [i.15] approach.
• The need to develop a common language to ensure data interoperability with applications, in line with the
principles of the European data directives (see [i.1], [i.5] and [i.6]) and the French initiative for a general
interoperability reference framework (see [i.9]).
5 Cases of information in the construction industry
5.1 Inventory of players involved in construction data exchange
The method consisted in defining a classification of some twenty families of players involved in the production and
consumption of construction data throughout the life cycle of the structure, with a view to consultation:
• Architects
• Insurance companies
• Engineering offices
• Control offices
• Technical centres
• Diagnosticians
• Distributors
ETSI
14 ETSI ES 204 114 V1.1.1 (2025-10)
• Economists
• Eco-organizations
• Companies
• Operators
• Manufacturers
• Land surveyors
• Project owners
• Notaries
• Financing organizations
• Programmers
• Urban planning authorization instruction services
• Building users
• IOT
5.2 Inventory of targeted use cases
A consultation some fifty stakeholders representing the categories identified enabled to produce a summary table
including:
• in the first column, information-providing players;
• in the front line, the same actors who receive information;
• the cells at the row/column intersection containing the type of information exchanged.
Table 1 summarizes the information exchanged.
Table 1
Information exchanged Computer application Input data
Deed of ownership Business software text/digital
Approval Business software text/digital
Project authorization Business software text/digital
Notice for execution Business software text/digital
Opinions on the work Business software text/digital
Technical notice Business software text/digital
Technical specifications Business software text/digital
Contract ERP text/digital
Agreement Business software text/digital
All-inclusive price breakdown Business software text/digital
Description for waste disposal Business software text/digital
Project description Business software text/digital
Quote ERP text/digital
Diagnostics (asbestos, lead, electrical, DPE, termites, PEMD, resources
(deconstruction re-use)) Business software text/digital
Qualification study of re-used materials Business software text/digital
Dimensioning studies (object requirements) Business software text/digital
Soil/fauna/flora surveys Business software text/digital
Invoice ERP text/digital
Environmental and health data sheet Business software text/digital
Product sheet Business software text/digital
Weather file Business software text/digital
Financing Business software text/digital
ETSI
15 ETSI ES 204 114 V1.1.1 (2025-10)
Information exchanged Computer application Input data
Application form for planning permission Business software text/digital
Information
...

SLOVENSKI STANDARD
01-december-2025
Dostop, terminali, prenos in multipleksiranje (ATTM) - Entitete/odnosi med
podatki/aplikacijami metamodela opendthX za medobratovalnost
Access, Terminals, Transmission and Multiplexing (ATTM) - Meta-model
entities/relationships opendthX data/applications interoperability
Ta slovenski standard je istoveten z: ETSI ES 204 114 V1.1.1 (2025-10)
ICS:
35.020 Informacijska tehnika in Information technology (IT) in
tehnologija na splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI STANDARD
Access, Terminals, Transmission and Multiplexing (ATTM);
Meta-model entities/relationships opendthX
data/applications interoperability

2 ETSI ES 204 114 V1.1.1 (2025-10)

Reference
DES/ATTM-0020013
Keywords
application, data interoperability,
data management, intelligent homes & buildings,
interoperability, management, smart cities
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI ES 204 114 V1.1.1 (2025-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Executive summary . 5
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 12
3.3 Abbreviations . 12
4 Introduction to the data interoperability format for connected buildings . 13
5 Cases of information in the construction industry . 13
5.1 Inventory of players involved in construction data exchange . 13
5.2 Inventory of targeted use cases . 14
5.3 Inventory of types of construction data exchanged . 15
6 Lifecycle of an object as part of a construction project and its operation . 17
6.1 Introduction to the Object Lifecycle in the BIM process . 17
6.1.1 From Design to Operation: An Integrated Vision based on ISO 19650 Standards . 17
6.1.2 A Structuring Duality: PIM and AIM . 18
6.1.3 Progressive Maturation in PIM . 18
6.1.4 The Specific Object as the Foundation of AIM . 18
6.1.5 An integrated approach to optimizing the entire life cycle . 18
6.2 The Evolution of BIM Objects in the PIM Cycle: From Conceptual to Concrete . 19
6.2.1 Introduction. 19
6.2.2 Progressive Information Maturation . 19
6.2.3 Information continuity and traceability. 19
6.2.4 A collaborative, multi-stakeholder approach . 20
6.2.5 Conclusion: A Solid Foundation for the Full Life Cycle . 20
6.3 The Generic Object Model (GOM) . 20
6.3.1 Definition and role of the GOM . 20
6.3.2 Property group structure . 20
6.3.3 GOM Creation Process . 21
6.3.4 Transition to Later Phases . 21
6.3.5 The Importance of the GOM in the BIM Process . 21
6.4 The Generic Object: Making Requirements a Reality in the BIM Process Lifecycle . 22
6.4.1 From Abstraction to Concretization: The Evolution from GOM to Generic Object. 22
6.4.2 Collaborative Enrichment by Different Actors . 22
6.4.3 Property valuation mechanisms . 22
6.4.4 Interdependency and arbitrage management . 22
6.4.5 Position in the PIM Process . 23
6.4.6 Transition to Later Phases . 23
6.5 The Specific Object: Technical Realization in the BIM Process Lifecycle . 23
6.5.1 Transition from Requirement to Concrete Solution . 23
6.5.2 Dual Property Structure . 23
6.5.3 Selection and Specification Process . 24
6.5.4 Enrichment by Value Chain Actors . 24
6.5.5 Manufacturer data integration . 24
6.5.6 Managing variants and alternatives. 25
6.5.7 Preparing the transition to AIM . 25
6.5.8 Strategic position in the BIM process . 25
ETSI
4 ETSI ES 204 114 V1.1.1 (2025-10)
6.6 The Role of the Specific Object in the AIM Phase . 25
6.6.1 Transition from Specific Object to AIM . 25
6.6.2 AIM Information Foundation . 25
6.6.3 Enrichment and Evolution in AIM . 26
6.6.4 Maintenance Operations Support . 26
6.6.5 Contribution to Performance Analysis and Decision Making . 26
6.6.6 Preparing for Renewal and Evolution . 26
6.7 Conclusion: Towards integrated, continuous information management . 27
6.7.1 Overview of the BIM Object Lifecycle Approach . 27
6.7.2 Benefits an Integrated Approach . 27
6.7.3 Challenges. 27
6.7.4 Outlook . 28
6.7.5 The New Horizon of Digital Construction . 28
7 Data interoperability . 28
7.1 Challenges . 28
7.2 The advantages . 28
7.3 The benefits of dynamic dictionaries for the specific use case of data exchange . 29
8 Complementarities and synergies between opendthX and SAREF for connected buildings . 29
8.1 Introduction . 29
8.2 SAREF4BLDG Example . 31
9 Semantic, organizational and technical interoperability . 34
9.1 Semantic interoperability: The COPO method . 34
9.2 Organizational interoperability: CIQO process . 34
9.3 Technical interoperability . 36
9.3.1 Language construction . 36
9.3.2 IFC files: a first revolution in construction . 36
9.3.3 IFC files have several essential characteristics: . 36
9.3.4 File-based exchange: from XML to JSON-LD . 36
9.3.5 API exchanges: fluidity and responsiveness . 37
9.3.6 Converging and complementary approaches . 37
9.3.7 Future prospects . 37
9.3.8 Conclusion / opendthX meta-model . 38
9.3.8.1 opendthX metamodel JSON v3.0 . 38
9.3.8.1.1 Schema: . 38
9.3.8.1.2 Description of the datBIM v3 API. 38
9.3.8.2 Open REST API of the opendthX JSON v4.0 meta model . 42
9.3.8.3 opendthX meta model similar JSON LD self-discoverable V1.0. 42
9.3.8.4 Summary diagram . 43
9.3.9 OpenCDE . 43
Annex A (informative): Metamodel opendthX JSON-LD v1.0 . 47
Annex B (informative): Schematics . 52
Annex C (informative): Bibliography . 55
Annex E (informative): Change history . 56
History . 57

ETSI
5 ETSI ES 204 114 V1.1.1 (2025-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Access, Terminals, Transmission and
Multiplexing (ATTM).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
The opendthX open meta-model is designed to ensure interoperability between digital content and construction industry
software, enabling all parties involved in a construction project to contribute to the BIM process (see Figure B.1), in
particular for:
• access to all types of content via all types of applications, regardless of the tools used;
• enriching objects for advanced collaborative construction;
• standardize input data in construction software avoid the GIGO effect (i.e. Garbage In → Garbage Out) (see
Figure B.3);
ETSI
6 ETSI ES 204 114 V1.1.1 (2025-10)
• with the aim of creating a "CIQO-ready" collaborative environment: "Collaboration In → Quality Out" (see
Figure B.2):
- optimize data transfers using the concept of data on demand, thus meeting the need for digital sobriety;
- establish digital continuity throughout the lifecycle of the project: design-construction-operations,
including the use of connected objects.

ETSI
7 ETSI ES 204 114 V1.1.1 (2025-10)
1 Scope
The present document presents the opendthX entity/relationship meta-model for interoperability between data and
applications.
The purpose of the present document is to establish a framework to ensure interoperability between digital content and
software applications in the construction industry. It aims to facilitate access to various types of content through
different applications, regardless of the tools used, thereby promoting advanced collaborative construction practices.
The standard aims to standardize input data to construction software in order to avoid the "Garbage In Garbage Out"
(GIGO) effect, by ensuring that quality input data and applications result in quality output data.
The main objectives are to optimize data transfers through the concept of data on demand, which promotes digital
sobriety, and to establish digital continuity throughout the lifecycle of construction projects, from design and
construction to operation, including the use of connected objects. The standard introduces the opendthX open
meta-model, designed to enable seamless interoperability and collaboration between all stakeholders in a construction
project.
In addition, the standard addresses the integration of semantic, organizational and technical interoperability, providing
methodologies and frameworks such as the use Cases-use Objects-Properties-modelled Objects (COPO) method for
semantic interoperability and the Collaboration In Quality Out (CIQO) process for organizational interoperability. It
also covers technical aspects such as the context for using IFC files, JSON-LD and APIs for efficient data exchange.
Overall, the standard aims to improve the efficiency, sustainability and adaptability of the construction sector by
harnessing the full potential of the digital transformation from appli-centrism to open data-centrism through
data-application interoperability.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 673: "SmartM2M; SAREF Development Framework and Workflow, Streamlining
the Development of SAREF and its Extensions".
[2] ISO 16739-1:2024: "Industry Foundation Classes (IFC) for data sharing in the construction and
facilities management industries — Part 1: Data schema".
[3] ISO 23386:2020: "Building information modelling and other digital processes used in construction
— Methodology to describe, author and maintain properties in interconnected data dictionaries".
[4] ISO 19650 (all parts): "Organization and digitization of information about buildings and civil
engineering works, including building information modelling (BIM) — Information management
using building information modelling".
[5] ETSI TS 103 548: "SmartM2M; SAREF reference ontology patterns".
[6] buildingSMART: "Industry Foundation Classes (IFC) - Version 4 - Addendum 1".
[7] ETSI TS 103 410-3 (V1.1.1): "SmartM2M; Smart Appliances Extension to SAREF; Part 3:
Building Domain".
ETSI
8 ETSI ES 204 114 V1.1.1 (2025-10)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding but are not required for conformance to the present document.
[i.1] Directive 2014/24/EU of the European Parliament and of the Council of 26 February 2014 on
public procurement and repealing Directive 2004/18/EC.
[i.2] French decree n 2018-1075 of December 3, 2018, Article R2132-10.
NOTE: The law authorizes the buyer to use electronic building data modelling tools.
In this case, it offers the means access mentioned in article R. 2132-14, until such time as these tools and
devices have become commonly accessible to economic operators.
[i.3] Under Belgian law: June 17, 2016 - Public Procurement Act.
[i.4] Legal approach to interoperability: Interoperability is a right of use within the meaning of article
L122-6-1 of the French Intellectual Property Code, in the version in force on November 26, 2021.
NOTE: Software is protected by copyright, except as interoperability.
[i.5] European Data Governance Act 30/05/2022.
[i.6] Proposal for European Data Protection Act - 23/02/2022.
[i.7] Study report on the comparative cost of creating a technical database of digital mock-up
components. BIM virtual workshop project carried out as part of the French government's digital
building transition plan. Version 2 of the document dated 11/04/2017.
NOTE See figures 4 and 5. Doc1_Etude2_ABV_BDD_20170411.pdf.
[i.8] Michel Léglise and Bernard Ferriès: "Evaluation of the costs of interoperability borne by
contractors, project owners and operators in the construction and operation of buildings". Final
report of study 08E86 commissioned by the FFB (Fédération Française du Bâtiment),
LAURENTI. December 2009.
NOTE: See figures 4 and 5. Doc2_Rapp_Final_FFB_35_cout_interoperability2009.pdf.
[i.9] "The Référentiel Général d'Interopérabilité Version 2.0", December 2015 developed by the French
government's Direction Interministérielle de l'Economie Numérique et du Système d'Information
et de Communication.
NOTE: This is a list of standards for given use cases.
Scope of exchanges:
 between administrations;
 between administrations and companies;
 between administrations and citizens. ®
[i.10] W3C Semantic Web: "Resource Description Framework (RDF)". ®
[i.11] W3C Recommendation 16 July 2020: "JSON-LD 1.1 - A JSON-based Serialization for Linked
Data". ®
[i.12] W3C editor's project: "The JSON-LD vocabulary".
[i.13] JSON for Linking Data.
ETSI
9 ETSI ES 204 114 V1.1.1 (2025-10)
[i.14] Schema.org.
[i.15] JDN: "Data centricity", 27/03/2019.
[i.16] ETSI TR 103 781 (V1.1.1): "SmartM2M; Study for SAREF ontology patterns and usage
guidelines".
[i.17] EN 13501-1: "Fire classification of construction products and building elements - Part 1:
Classification using data reaction to fire tests", (produced by CEN).
[i.18] NF XP P07-150 (12-2014): "Properties of products and systems used in construction - Definition
of properties, method of creation and managing properties in a harmonized system of reference".
[i.19] ISO 23387: "Building information modelling (BIM) — Data templates for construction objects
used in the life cycle of built assets — Concepts and principles".
[i.20] OPIIEC: "Study on skills, employment and training requirements for the digital twin in France",
05/01/2024.
[i.21] "Open formats, what for?", April.org.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
appli-centrism: IT development method based on developing an application using data that can only be used in that
application
NOTE: This characterizes a computer application development method which involves integrating input data via
a dedicated graphical interface for the processing envisaged by the application and rendering the
processing in a native format. In this case, the application acts as a data repository. In this logic, the user
should have as many data repositories as applications, and therefore as many use cases, which implies
re-entering information or developing specific connectors for each link envisaged.
attribute: data element used to describe a property or a group of properties a computer-suitable way
authorization: function specifying access rights to resources linked to information security and information systems
security in general, and to access in particular
NOTE: More formally, "authorizing" means defining an access policy.
Avis Technique (AT) (technical notice): document formalizing the opinion issued by a group of experts on the
suitability for use of innovative construction processes
NOTE: The CSTB is involved in the technical opinion procedure at several levels and provides the secretariat.
CSTB has carried out a study demonstrating the ability of the opendthX format to describe the AT.
Building Information Modelling (BIM): use of a shared digital representation of a built asset (buildings, bridges,
roads, factories, etc.) to facilitate the design, construction and operation processes and provide a reliable basis for
decision-making
NOTE: See ISO 19650 [4].
class: group of properties
computer object: instance of the class that can be considered as the digital representative of a construction object
NOTE: In the remainder of the present document, the object will be considered as a computer object. The object
or object model is defined for the purpose of exchanging data for a specific use case.
ETSI
10 ETSI ES 204 114 V1.1.1 (2025-10)
construction object: object of interest in a construction process
NOTE: In accordance with ISO 23387 [i.19].
data-centricity: IT development method involving the development applications using standardized data that can be
used in other applications
NOTE: Behind this name lies an approach that places data at the heart of the company and requires it to be
considered an asset in its own right, in the same way as patents, for example. It would be frustrating and
incomprehensible to create an entirely new business without mastering this asset. The data-centric
approach aims to turn the tables and make data the cardinal point of a company's strategy.
Source JDN 27/03/2019 [i.15].
©
datBIM : company that developed the opendthX format and then licensed it to the Alliance du bâtiment association to
govern and promote it
digital content: library or catalogue of objects that are collections of objects
digital twin: digital duplication of a physical entity or product
NOTE: The digital twin is the digital double of a real object, process or system, made up of interoperable
applications and data and developed to meet well-defined uses.
It is fed by data flows from the real entity at a defined frequency, to adjust to needs and uses in real
conditions. The digital twin makes it possible to understand, analyse and predict the behaviour of the real
entity, in order to support decision-making in its management and operation [i.20].
entity: thing capable of existing independently, uniquely identifiable and capable of storing data
NOTE: In the context of the entity-relationship model, an entity has properties or attributes.
eXtensible Markup Language (XML): subset of the Standard Generalized Markup Language (SGML)
NOTE: Its syntax is said to be "extensible" because it can be used to define different languages, each with its own
vocabulary and grammar, such as XHTML, XSLT, RSS, SVG, opendthX and so on.
Garbage In Garbage Out (GIGO): well-identified risk in systems engineering: poor-quality input data produces
poor-quality output data (results)
generic object: set of property/value pairs that are dissociated from a manufacturer's product brand and whose values
may be requirement values or correspond to generic, standard range values
generic object model or object description model: set of value-free properties that can also be assimilated to a class
identification: means of "knowing" the identity an entity
NOTE: Often by means of an identifier such a user name (distinct from identity , or authentication).
Industry Foundation Classes (IFC): standardized object-oriented file format [2] used by the construction industry to
exchange and share information between software programs
NOTE: Promoted by the international organization buildingSMART International and its national chapters.
integrity: state of data which, during processing, storage or transmission, is not altered or destroyed, whether
intentionally or accidentally, and retains a format that allows it to be used
NOTE 1: Data integrity comprises four elements completeness, precision, accuracy/authenticity and validity.
NOTE 2: Integrity is one of the basic requirements of IT security, document management and archiving.
JavaScript Object Notation (JSON): textual data format derived from the object notation of the JavaScript language
NOTE: It competes with XML for the representation and transmission of structured information.
ETSI
11 ETSI ES 204 114 V1.1.1 (2025-10)
JavaScript Object Notation for Linked Data (JSON LD): method encoding structured data using JSON
NOTE: The aim is to provide developers with a simple way of transforming existing JSON data into JSON-LD.
This enables data to be serialized in the same way as with traditional JSON. JSON-LD is a
recommendation of the World Wide Web Consortium and is therefore considered a standard. Source: ®
Wikipedia .
See [i.10], [i.11], [i.12], [i.13] and [i.14].
metadata: data used to define or describe another piece of data, determining its medium
NOTE: Term derived from the Greek prefix meta, meaning "beyond" or "about".
EXAMPLE: Metadata can indicate the date of creation or recording a piece of data, or the geographic
coordinates associated with a photograph.
opendthX: open data format designed to ensure interoperability between digital content and software in the
construction sector
NOTE This format is governed by the construction industry through the non-profit association Alliance du
bâtiment.
open format: freely usable data format
NOTE: Open format files can be read and modified by yourself or by third parties. Readability is guaranteed over
time. Open formats are freely usable in any software, making software interoperable. Open formats
promote freedom of choice by not favouring the format of a particular company (known as the native or
proprietary format), thus avoiding the monopoly of a publisher who would like to make users captive to
the proprietary format it has designed [i.21].
property: inherent or acquired characteristic of an element (project, system, product, etc.)
NOTE 1: ISO 23386 [3] (produced based on the French experimental standard NF XP P07-150 [i.18] published in
2015) provides an exhaustive list of 40 attributes used to manage a property in a data dictionary.
EXAMPLE: Reaction to fire measured in accordance with EN 13501-1 [i.17].
A property can be:
- Static: the value is predefined by the object designer.
- Configurable or parameterizable: the value is defined by the user.
- Dynamic: the value changes according to the object's physical state. Example: temperature measured by
a thermometer-type sensor.
- Relation: association.
NOTE 2: According to the entity-relationship model, a relationship is a link between two or more entities. A
relationship can have properties or attributes.
- Traceability: situation in which the necessary and sufficient information is provided to know (possibly
retrospectively) the composition of an object throughout its production, transformation and distribution
chain
property group: set of properties with no value
NOTE: According to ISO 23386 [3], there are different categories of property groups:
 Class.
 Compound property.
 Domain.
 Reference document.
 Other uses.
ETSI
12 ETSI ES 204 114 V1.1.1 (2025-10)
specific object: set of property/value pairs whose values are the performances of a manufacturer's product
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ABV Atelier BIM Virtuel (Virtual BIM Workshop)
AI Artificial Intelligence
AIM Asset Information Model
APD Avant Projet Détaillé (detailed design)
API Advanced Programming Interface
APS Avant Projet Sommaire (Preliminary design)
AT Avis Technique (technical notice)
BIM Building Information Modelling
BMS Building Management System
CAD Computer-Aided Design
CIQO Collaboration In Quality Out
COPO use Cases, use Objects, Properties, modelled Objects
CRUD Create, Read, Update, Delete
CSTB Scientific and Technical Centre for Building
DatSPIN Données actualisées techniques pour une Stratégie du Patrimoine Immobilier Numérique
(pp-to-date technical data for a digitized real estate strategy)
DCE Dossier de Consultation des Entreprises (specification booklet)
DOE Dossier des Ouvrages Exécutés (completed works file )
DTU Unified Technical Documents
ERP Enterprise Resource Planning
FDES Fiche de Données Environnementales et Sanitaires
GDP Gross Domestic Product
GIGO Garbage In Garbage Out
GO Generic Object
GOM Generic Object Model
IFC Industries Foundation Classes
IOT Internet Of Things
JDN Journal Du Net
JSON JavaScript Object Notation
JSON-LD JavaScript Object Notation for Linked Data
opendthX Open Dictionnaire Technique Harmonisé eXchange (exchange of technical dictionaries
harmonized)
PCBIM Building Permit BIM
PIM Project Information Model or Product Information Management
POBIM Properties of BIM Objects
RSS Really Simple Syndication
SAREF Smart Applications REFerence ontology
SGML Standard Generalized Markup Language
SO Specific Object
SVG Scalable Vector Graphics
XHTML eXtensible HyperText Markup Language
XML eXtensible Markup Language
XP eXperimental Standards
NOTE: Identified by the prefix "XP".
XSLT eXtensible Stylesheet Language - Transformations
ETSI
13 ETSI ES 204 114 V1.1.1 (2025-10)
4 Introduction to the data interoperability format for
connected buildings
The digital transformation of the construction sector can accelerate its environmental transformation, provided that it
enables everyone to work together, which presupposes that data is interoperable with applications.
The specific characteristics of the construction sector that need to be taken into account to make this transformation a
success:
• A fragmented sector: A large majority of construction companies have fewer than 20 employees.
• The political stakes are high:
- the environment: the biggest consumer of energy and the biggest producer of waste;
- economic: exchanges of construction data represent 25 % of GDP in Europe, based on studies carried out
in France;
rd
- social: 3 in terms of direct recruitment, after services and industry.
• Digital modelling of construction projects is encouraged by public procurement regulations (see [i.1], [i.2] and
[i.3]), provided that this requirement does not create technological barriers for any of the players involved.
• The costs attributable to the lack of interoperability in Europe are estimated at over one hundred billion euros
per year, extrapolated from studies carried out in France (see [i.7] and [i.8]).
• The operating cost a building represents 70 to 80 % of its total cost.
• Convergence between buildings and telecommunications via the Internet of Things (IOT) or connected
objects.
• Numerous software applications: over 300 construction software publishers in France alone.
• The digital transition in the construction sector means moving from an application-centric to an open data-
centric [i.15] approach.
• The need to develop a common language to ensure data interoperability with applications, in line with the
principles of the European data directives (see [i.1], [i.5] and [i.6]) and the French initiative for a general
interoperability reference framework (see [i.9]).
5 Cases of information in the construction industry
5.1 Inventory of players involved in construction data exchange
The method consisted in defining a classification of some twenty families of players involved in the production and
consumption of construction data throughout the life cycle of the structure, with a view to consultation:
• Architects
• Insurance companies
• Engineering offices
• Control offices
• Technical centres
• Diagnosticians
• Distributors
ETSI
14 ETSI ES 204 114 V1.1.1 (2025-10)
• Economists
• Eco-organizations
• Companies
• Operators
• Manufacturers
• Land surveyors
• Project owners
• Notaries
• Financing organizations
• Programmers
• Urban planning authorization instruction services
• Building users
• IOT
5.2 Inventory of targeted use cases
A consultation some fifty stakeholders representing the categories identified enabled to produce a summary table
including:
• in the first column, information-providing players;
• in the front line, the same actors who receive information;
• the cells at the row/column intersection containing the type of information exchanged.
Table 1 summarizes the information exchanged.
Table 1
Information exchanged Computer application Input data
Deed of ownership Business software text/digital
Approval Business software text/digital
Project authorization Business software text/digital
Notice for execution Business software text/digital
Opinions on the wo
...