SIST EN ISO 23387:2025

SLOVENSKI STANDARD
01-december-2025
Nadomešča:
SIST EN ISO 23387:2020
Informacijsko modeliranje gradenj (BIM) - Podatkovne predloge za gradnike, ki se
uporabljajo v življenjskem ciklu gradbenega objekta (ISO 23387:2025)
Building information modelling (BIM) - Data templates for objects used in the life cycle of
assets (ISO 23387:2025)
Bauwerksinformationsmodellierung (BIM) - Datenvorlagen für Objekte während des
Lebenszyklus von Assets (ISO 23387:2025)
Modélisation des informations de la construction (BIM) - Modèles de données pour les
objets utilisés durant le cycle de vie des biens (ISO 23387:2025)
Ta slovenski standard je istoveten z: EN ISO 23387:2025
ICS:
13.020.60 Življenjski ciklusi izdelkov Product life-cycles
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.

EN ISO 23387
EUROPEAN STANDARD
NORME EUROPÉENNE
October 2025
EUROPÄISCHE NORM
ICS 35.240.67 Supersedes EN ISO 23387:2020
English Version
Building information modelling (BIM) - Data templates for
objects used in the life cycle of assets (ISO 23387:2025)
Modélisation des informations de la construction (BIM) Bauwerksinformationsmodellierung (BIM) -
- Modèles de données pour les objets utilisés durant le Datenvorlagen für Objekte während des Lebenszyklus
cycle de vie des biens (ISO 23387:2025) von Assets (ISO 23387:2025)
This European Standard was approved by CEN on 9 August 2025.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

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
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 23387:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 23387:2025) has been prepared by Technical Committee ISO/TC 59 "Buildings
and civil engineering works " in collaboration with Technical Committee CEN/TC 442 “Building
Information Modelling (BIM)” the secretariat of which is held by SN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by April 2026, and conflicting national standards shall be
withdrawn at the latest by April 2026.
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.
This document supersedes EN ISO 23387:2020.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: 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 the
United Kingdom.
Endorsement notice
The text of ISO 23387:2025 has been approved by CEN as EN ISO 23387:2025 without any modification.

International
Standard
ISO 23387
Second edition
Building information modelling
2025-09
(BIM) — Data templates for objects
used in the life cycle of assets
Modélisation des informations de la construction (BIM) —
Modèles de données pour les objets utilisés durant le cycle de vie
des biens
Reference number
ISO 23387:2025(en) © ISO 2025
ISO 23387:2025(en)
© ISO 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
ISO 23387:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Data template structure . 3
4.1 General .3
4.2 UML representation of a data template structure .4
4.3 URIs usage for ISO 23887 data model . .5
4.4 Data modelling .5
4.4.1 General .5
4.4.2 Reference document .5
4.4.3 Object type .5
4.4.4 Data template .6
4.4.5 Group of properties .6
4.4.6 Property .7
5 ISO 12006-3 representation . 9
5.1 General .9
5.2 Definition of subject kinds .9
5.3 Specialization of dictionary meta level subject kinds .10
5.4 Subject relationships .11
5.5 Property relationships . 12
5.6 Data template representation following ISO 12006-3 . 12
6 XML representations . 14
Annex A (informative) Examples, use cases and implementations .15
Annex B (informative) Creation of data templates .25
Annex C (informative) Data template concepts attributes with examples .27
Annex D (informative) Correct instantiation case of subtypeOf relationship .31
Annex E (informative) XSD representation .32
Annex F (informative) XML example .33
Bibliography .34

iii
ISO 23387:2025(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization
(WTO) principles in the Technical Barriers to Trade (TBT), see http://www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 59, Buildings and civil engineering works,
Subcommittee SC 13, Organization and digitization of information about buildings and civil engineering
works, including building information modelling (BIM), in collaboration with the European Committee
for Standardization (CEN) Technical Committee CEN/TC 442, Building Information Modelling (BIM), in
accordance with the Agreement on technical cooperation between ISO and CEN (Vienna Agreement).
This second edition cancels and replaces the first edition (ISO 23387:2020), which has been technically
revised.
The main changes are as follows:
— the data model has been harmonised with ISO 12006-3:2022;
— an XML Schema Definition has been provided.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
ISO 23387:2025(en)
Introduction
Building information modelling (BIM) provides a digital process for describing and displaying information
required in the planning, design, construction and operation of assets. This approach encompasses all
aspects of the built environment, including civil infrastructure, utilities and public space.
The ISO 19650 series sets out the concepts and principles for business processes across the built environment
sector in support of the management and production of information during the life cycle of assets when
using building information modelling (BIM). To support the management and production of information
in these business processes, standardization is of the highest importance. Machine-interpretable data are
essential to providing a reliable and sustainable exchange of information in an asset life cycle process.
Data templates provide a standardized data structure to describe the characteristics of objects enabling
seamless information exchanges of construction sector business semantics through the life cycle of assets.
This document enables data templates to be standardized and made available across the built environment
sector, and where applicable through data dictionaries based on ISO 12006-3.
Data templates can be used in conjunction with Industry Foundation Classes (IFC) in ISO 16739-1.
The target audience of this document is:
— software developers, for embedding the data structure in software, platform etc.;
— built environment sector domain experts appointed to create data templates based on sources describing
information needs;
— sector practitioners, as they provide the demand, use of data, and process etc.;
— authorities, as they review and check all relevant submissions;
— research and development personnel, as they support the innovation and continuous development of
data templates;
— educational institutions, as the concept of data templates, same as BIM, and digital information principles
should be merged into education and training programs;
— developers (asset owners), as they need a clearer vision on data template, hence to put this as part of the
tender documents.
v
International Standard ISO 23387:2025(en)
Building information modelling (BIM) — Data templates for
objects used in the life cycle of assets
1 Scope
This document provides the concept of data templates developed to enable machine interpretability based
on a standardized data structure, carrying the alphanumerical information for any object used in the life
cycle of assets.
This document provides a description of how data templates are implemented following ISO 12006-3.
This document provides a methodology to create and maintain data templates in data dictionary.
This document provides guidance for linking between data templates and classification systems within data
dictionaries based on ISO 12006-3.
This document provides an XML Schema Definition (XSD) representing an implementation of the ISO 23387
and ISO 12006-3 data models.
It is not within the scope of this document to provide the content of any data templates.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 23386, Building information modelling and other digital processes used in construction — Methodology to
describe, author and maintain properties in interconnected data dictionaries
ISO 12006-3, Building construction — Organization of information about construction works — Part 3:
Framework for object-oriented information
3 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
data dictionary
database that contains metadata
[SOURCE: ISO/IEC 2382:2015, 2121501, modified — The admitted term "information resource dictionary"
has been removed; notes to entry have been removed.]

ISO 23387:2025(en)
3.2
data template
data structure used to describe the characteristics of objects (3.4)
EXAMPLE 1 A data template offers a view tailored to a specific information requirement. For example, a heating,
ventilation and air conditioning (HVAC) system (3.11) designer may require descriptions of HVAC products that can be
imported into the design system.
EXAMPLE 2 A data template provides manufacturers with a standardized data structure that can be applied to
any internal system or process, or both, of handling product data. For example, one or several product information
management systems can apply or map to this structure to enable machine interpretability, both internally and with
any requests from any software using the same data template structure. An HVAC product manufacturer can then
answer the request from any stakeholder including the HVAC system designer.
Note 1 to entry: The relevant scope of the data template can be used together with the term “data template”. For
example, a data template for a product (3.8) can be named “product data template”; a data template for a system can
be named “system data template”.
Note 2 to entry: A data template can be used in an information exchange for a specific purpose for an object type (3.5)
in the inception, brief, design, production, operation and demolition of assets.
3.3
data sheet
data input in accordance with a data template (3.2), that represents a real-world product (3.8), asset or
requirement
EXAMPLE 1 Product using property (3.9) "thermal transmittance" with unit W/(m ⋅K) is of value 0,9.
EXAMPLE 2 Requirement using property "height" with unit mm is of value 600.
3.4
object
any part of the perceivable or conceivable world
EXAMPLE Instance of a “calcium silicate masonry unit” object type (3.5).
Note 1 to entry: An object may represent a design object, intermediate product (3.8), finished product, finishing tool or
equipment, system (3.11), assembly, space, building, etc.
[SOURCE: ISO 12006-2:2015, 3.1.1, modified — The original note 1 to entry has been replaced by a new one,
EXAMPLE has been added.]
3.5
object type
representation of objects (3.4) that share common characteristics
Note 1 to entry: The role of the object type is to classify the data template (3.2).
3.6
group of properties
collection of properties (3.9) enabling them to be prearranged or organized
[SOURCE: ISO 23386:2020, 3.14, modified — The definition has been updated to clarify that the collection is
for properties; notes to entry have been removed.]
3.7
machine-interpretable data
data that is in a specific context and format and can be read and stored in a computer system (3.11) such that
action can be taken based on the content of the data
[SOURCE: ISO 10303-232:2002, 3.5.3, modified — The preferred term has been changed from "computer
interpretable data" to "machine-interpretable data"; "may" has been replaced by "can"; EXAMPLE has been
removed.]
ISO 23387:2025(en)
3.8
product
item manufactured or processed for incorporation in construction works
[SOURCE: ISO 6707-1:2020, 3.4.1.2, modified — The preferred term "construction product" has been
removed; note 1 to entry has been removed.]
3.9
property
defined characteristic suitable for the description and differentiation of an object (3.4)
EXAMPLE Length according to EN 12058, sound reduction index according to ISO 10140-4.
Note 1 to entry: When a property is named together with reference to a technical specification, where the instructions
to assess the performance are available (usually standards), it is to be regarded as a specific property. The relationship
between the property and the specific property is modelled as a parent child relationship.
[SOURCE: ISO 22274:2013, 3.25, modified — The words "the objects in a class" have been replaced with "an
object"; EXAMPLE has been replaced; note 1 to entry has been added.]
3.10
reference document
publication that is consulted to find specific information, particularly in a technical or scientific domain
EXAMPLE EN 771-1:2011+A1:2015.
Note 1 to entry: A reference document can be associated with any data present in a data dictionary (3.1).
[SOURCE: ISO 23386:2020, 3.18, modified — EXAMPLE has been added.]
3.11
system
arrangement of parts or elements that together exhibit a stated behaviour or meaning that the individual
constituents do not
EXAMPLE The object “wall” which is composed of parts is a system.
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.46, modified — EXAMPLE has been added; notes 1 to 3 to entry have
been removed.]
4 Data template structure
4.1 General
The objective of data templates is a common way to exchange object data. Therefore, all data templates
follow the same general data structure (meta model). A data template is meant to provide a standardized
structure for a pre-defined information delivery – a data sheet – for an object type, for a specific use case or
any other purpose.
The data template structure consists of the concepts object type, data template, property, reference
document, and group of properties. Quantities, units and values are attributes of the properties, according
to ISO 12006-3, and therefore not modelled as separate concepts in the UML model in Figure 1.
Where relevant, the data template has a relationship to an object type. Depending on the purpose of the
information exchange, it is possible to create multiple data templates for one object type, having common or
disjoint properties.
Both data templates and groups of properties can be used for providing a pre-defined information delivery.
For example, the geometrical properties "width", "length" and "height" can be collected under the group of
properties "dimensions". Which of the concepts to use depends on the purpose of the information delivery
and the intended behaviour of the data sheet.

ISO 23387:2025(en)
All the concepts of a data template may have a relationship to an external document such as a standard, a
technical specification, report, guideline or similar. The reference document provides the definition of the
concept element. A few more relationships exist which are illustrated in Figure 1.
Object types, data templates, properties, groups of properties, and reference documents are all concepts
that are created, managed and stored within a data dictionary. The data dictionary implementation shall
be based on ISO 12006-3. All concepts in this document shall be created following the management rules to
author and maintain properties and groups of properties as defined in ISO 23386. The governance of data
dictionaries prevents duplication, while providing clear definitions of all concepts in data templates.
As ISO 12006-3 supports interconnections of data dictionaries, a data template can use concepts accordingly.
Therefore, a data template can be composed by concepts from different data dictionaries. This is illustrated
in Clause A.1.
A data template applies to both single object types and systems or compositions of object types. For example,
a data template applies to a window as a single object type, but also to a window with its components. It also
applies to a system incorporating the window, like an external wall system. An example of a wall system
with components is given in Clause A.4.
A data template applies to object types representing any part(s) of the object life cycle, from early design,
through specification, and for physical objects (products or system of products). Where applicable,
definitions of object types and properties should be reused throughout the object life cycle.
4.2 UML representation of a data template structure
The data template representation in Figure 1 uses the Unified Modelling Language (UML). Figure 1 provides
modelling rules for concepts and their relationships. In addition to UML relationships, names are added to
them to provide relationship semantics, corresponding to ISO 12006-3, explained in Table 3.
Figure 1 — UML representation of a data template structure

ISO 23387:2025(en)
4.3 URIs usage for ISO 23887 data model
This document introduces an additional attribute that is applicable to all concepts in a data template, the
URI, which can be used alongside the UUID which is mandatory in ISO 12006-3. UUIDs may be incorporated
into URIs where relevant, but this is not mandatory, particularly when URIs can include user-friendly
information.
UUIDs are primarily intended for internal references within a data dictionary, ensuring unique and
consistent identification. While UUIDs can serve as external references in scenarios where defining URIs is
impractical, this approach is not recommended. URIs are generally preferred for external references due to
their flexibility and ability to convey meaningful information. Consequently, URIs should be prioritized for
external referencing whenever feasible.
4.4 Data modelling
4.4.1 General
The data template structure consists of a data template that has an object type, properties, and groups of
properties, with reference documents providing the source of each of the concepts.
A data template is modelled within the context of one object type to provide a pre-defined information
delivery.
One object type may be assigned to several data templates. Each data template may contain one or more
properties, and within each data template the properties can be collected in different groups of properties.
The rules for modelling the data template structure with its concepts appy within the context of one data
template. The modelling rules in Figure 1 are described in 4.4.2 to 4.4.6.
Annex A provides examples of possible data modelling approaches, together with use cases and examples.
Annex B provides a possible workflow for creating data templates.
Annex C provides examples of data template concepts’ attributes.
4.4.2 Reference document
A reference document may be related to several object types, data templates, groups of properties, and
properties. Therefore, the modelling rules are zero to many (0.*) data templates, groups of properties, and
properties.
4.4.3 Object type
The object type:
a) should ideally be defined based on a standard (terminology standard, technical standard, etc.); however,
this is not mandatory as an object type may be defined in other sources than standards; the object
type can be defined in several reference documents; the modelling rule is zero to many (0.*) reference
documents;
b) needs a data template to relate properties to it; one object type can belong to multiple data templates;
the modelling rule is one to many (1.*) data templates;
EXAMPLE 1 An object type can belong to multiple data templates when it is part of a system. A more detailed
example is provided in Figure A.5.
c) can be composed of (has part relationship) other object types; the modelling rule is zero to many (0.*)
object types;
EXAMPLE 2 A wall is composed of layers of products.

ISO 23387:2025(en)
d) can be part of the composition of another object type; within the context of one object type, this can be
maximum one object type; the modelling rule is zero to one (0.1) object type.
4.4.4 Data template
The data template:
a) defines a complete and unique information delivery within a context or with a specific purpose;
b) has a list of unique properties; the modelling rule is zero to many (0.*) properties;
EXAMPLE 1 A design specification is a data template.
EXAMPLE 2 A delivery ticket is a data template
c) may have groups of properties to allow for categorization of properties within the data template to
provide subsets of the template properties, fulfil part(s) of the data template overall purpose, or fulfil
any other specific information need, the modelling rule is zero to many (0.*) groups of properties;
d) can be related to an object type, the modelling rule is zero to one (0.1) object types;
e) can be based on one or more reference documents, the modelling rule is zero to many (0.*) reference
document;
EXAMPLE 3 A reference document for a template can be a design or product standard, or another technical
specification.
f) can be composed of (has part relationship) other data template concepts; the modelling rule is zero to
many (0.*) data template;
EXAMPLE 4 A data template can be composed of other data template e.g. when a wall is composed of layers of
materials or products. An example is provided in Figure A.5.
g) can be part of the composition of another data template concept, within the context of one data template,
this can be maximum one data template concept; the modelling rule is zero to one (0.1) data template
concepts.
4.4.5 Group of properties
The group of properties:
a) defines a common context or purpose for a collection of properties;
EXAMPLE 1 Properties within one data template relevant to different domains or recipients, such as technical,
financial and environmental properties, can be collected in different groups of properties based on the domain.
EXAMPLE 2 Within a data sheet, properties necessary at different times or stages during a construction
process may be collected in groups of properties if the property values remain constant over time or across stages.
b) shall at a minimum have one property, the modelling rule is one to many (1.*) properties;
c) shall be related to a data template and it can be related to multiple data templates; the modelling rule is
one to many (1.*) data templates;
d) can be based on one or more reference documents, e.g. a design or product standard, or another technical
specification; the modelling rule is zero to many (0.*) reference documents;
e) can be composed of (has part relationship) other groups of properties, the modelling rule is zero to
many (0.*) groups of properties;
f) can maximum be part of one group of properties, within the context of one group of properties; the
modelling rule is zero to one (0.1) groups of properties.

ISO 23387:2025(en)
4.4.6 Property
A property:
a) may be based on a reference document; the modelling rule is zero to many (0.*) reference documents;
b) shall be related to a data template; the modelling rule is one to many (1.*) data templates;
c) may be grouped in a group of properties; the modelling rule is zero to many (0.*) groups of properties;
d) can be specialized; where a property is a specialization of another more generic property; the
specializing property’s value shall be a valid value of the target property; where a property is defined as
the specialization of another more generic property, the modelling rule is zero to one (0.1); inversely, a
property can be specialized by zero to many (0.*) more specific properties;
EXAMPLE 1 The property “length” can be used for generic use cases, and specialized later when the need to
refer to a specific reference standard applies.
e) may be dependent on other properties; the modelling rule is zero to many (.*) properties.
EXAMPLE 2 To calculate the U-value of a window, the thermal transmittance of the glass is needed.
There are three main kinds of dependencies where all three may be combined:
— context parameters;
— proxy properties;
— function dependencies.
Context parameters are connected properties where the value of the target properties describe the context
of the current property. Context parameters with multiple target properties can be additive or combinative.
Context parameters shall be used to provide context for properties with table values.
Proxy properties are connected properties where the value of one of the target properties shall be used
directly to represent the current property. The current property inherits the quantity kind and type of value
from the target property.
Function dependencies are connected properties where the values of the target properties serve as inputs
variables or parameters to a set of instructions where the value of the current property is the output.
The relationship may be defined as logical operations, algebraic functions or any other set of instructions
different from proxy properties. Function dependencies may be used to populate each table entry for a
property table value.
Table 1 provides definitions of different dependencies.

ISO 23387:2025(en)
Table 1 — Definitions of property dependency relations
Dependency Definition
Additive context relationship to one or multiple target property(ies) where the current property value depends
parameters on the target property value(s), and where the current property value does not depend on com-
binations of any target property values
Combinative con- relationship to one or multiple target property(ies) where the current property value depends
text parameters on the target property value(s), and where the current property value depends on all possible
combinations of multiple target property values
Reference proxy relationship to one target property defined as the preferred proxy property in the presence of
property multiple proxy properties, and where the target property value is communicated as the current
property’s value
Alternative proxy relationship to multiple target properties where no single target property is preferred to the
properties other target properties of the relationship, and where one of the target property values is com-
municated as the current property’s value
Function depend- relationship to one or multiple target property(ies) where the current property value is found
ency following a set of instructions specified by the relationship and where the target property val-
ue(s) serve(s) as input variable(s) or parameter(s)
Where context parameters have own context parameters, parameters on the different levels shall be combined with a combinative
approach.
Where multiple context parameters are combined, the target properties of each relationship shall first be handled according to
the relationship definition, and then combined with a combinative approach.
EXAMPLE 3 Single additive or combinative context parameter: To declare the global warming potential (GWP) of a
product, it is necessary to also declare the life cycle stage (information module) to which the GWP belongs. See Table 2.
Table 2 — Single additive or combinative context parameter
Context parameter: Information module
Context parameter value: A1-A3 A4 A5 B1 … B7 C1 … C4 D
Current property: glob-
al warming potential
EXAMPLE 4 Additive context dependencies: The amount used of a given type of material in the maintenance, repair,
replacement and refurbishment stages for EPDs (B2–B5) is declared for each information module B2–B5, and modelled
as an additive context parameter where the target properties for each information module is independent on each
other. See Table 3.
Table 3 — Additive context parameters
Context parameters: Material type for Material type for Material type for Material type for
maintenance repair replacement refurbishment
Context parameter Paint Replacement window
values: unit (half unit)
Current property: mate- 0,55 kg 27,7 kg
rial amount (mass)
EXAMPLE 5 Combinative context dependencies: Compressive strength of cement can be modelled as being
dependent on the age of the test specimen combined with a dependency on a property specifying if the lower limit,
average or upper limit measurement is declared. See Table 4.

ISO 23387:2025(en)
Table 4 — Combinative context parameters
Current property: Compres- Context parameter 1: age of test specimen
sive strength
Upper limit
Target value
Lower limit
EXAMPLE 6 Proxy properties: Thermal transmittance for insulating glazing units are calculated according to
EN 673 (reference proxy) and, if and only if calculation is not possible, according to measurements according to EN 674
or EN 675 (alternative proxies).
EXAMPLE 7 Function dependencies: Classification of compressive strength for concrete requires the tested
compressive strength of a test specimen with age 28 days exceeds a certain limit value.
EXAMPLE 8 Function dependencies: The volume of a quadrilateral object is calculated as the product of the length
of the three dimensions.
5 ISO 12006-3 representation
5.1 General
ISO 12006-3 specifies a language-independent object-oriented information model which can be used for the
development of data dictionaries and implementation of data dictionary systems. The model in ISO 12006-3
is referred to as the meta level.
The ISO 12006-3 model includes many of the concepts in this document and in ISO 23386, but it lacks
definitions for the concepts data template, object type and group of properties. These three concepts are
used in data dictionaries and shall be modelled as kinds of xtdSubject.
The ISO 12006-3 model does not provide attributes intended to differentiate between different kinds of
xtdSubject on the dictionary level.
5.2 Definition of subject kinds
To identify the different kinds of subjects used in this document, a dictionary meta level is introduced. In data
dictionary implementations, dictionary meta level xtdSubjects shall be instantiated using the standardized
instances defined in Table 5. The dictionary meta level xtdSubject instances shall refer to this document as
the reference document, as exemplified in 5.6.
Table 5 defines the dictionary meta level subjects used to identify the kind of xtdSubject in and across data
dictionaries and data dictionary implementations.
Table 5 — Identification, naming and definition of dictionary meta level subjects
UUID Name Definition
f72aefe1-cb39-4af3-8455-2fd- Data template Kind of subject that can be assigned to an object type,
fe891734c and can contain other data templates, groups of prop-
erties and/or properties
b7b1cd0b-b515- 4252-a083- bb5d- Object type Kind of subject that can be composed of other object
dee073c8 types, but shall not contain data templates, group of
properties or properties
7c9ffe6e-3c8b-4cd2- b57b- Group of properties Kind of subject that contains properties and/or other
4cd102325603 groups of properties, but shall not contain data tem-
plates and shall not be assigned to an object type

Context
parameter 2:
type of test
result
ISO 23387:2025(en)
A data template is a kind of subject that may be assigned to an object type, and may have other data
templates, groups of properties or properties. On the dictionary meta level, different kinds or specializations
of data templates may be defined. On the dictionary level, a data template may be a subtype of another data
template.
An object type is a kind of subject that may be composed of other object types, but shall not contain
data templates, groups of properties or properties itself. On the dictionary meta level, different kinds or
specializations of object types may be defined. On the dictionary level, an object type may be a subtype of
another object type.
A group of properties is a kind of subject that shall contain properties or other groups of properties. Groups
of properties shall not contain data templates or be assigned to object types. A property may be included in
multiple groups of properties, also within the same data template
...