EN ISO 29481-3:2022

SLOVENSKI STANDARD
01-april-2023
Informacijski modeli stavb - Priročnik z informacijami - 3. del: Shema podatkov
(ISO 29481-3:2022)
Building information models - Information delivery manual - Part 3: Data schema (ISO
29481-3:2022)
Bauwerksinformationsmodelle - Handbuch der Informationslieferungen - Teil 3:
Datenschema und Klassifikation (ISO 29481-3:2022)
Modèles des informations de la construction - Protocole d'échange d'informations -
Partie 3: Schéma de données (ISO 29481-3:2022)
Ta slovenski standard je istoveten z: EN ISO 29481-3:2022
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 29481-3
EUROPEAN STANDARD
NORME EUROPÉENNE
October 2022
EUROPÄISCHE NORM
ICS 91.010.01; 35.240.67
English Version
Building information models - Information delivery
manual - Part 3: Data schema (ISO 29481-3:2022)
Modèles des informations de la construction - Bauwerksinformationsmodelle - Handbuch der
Protocole d'échange d'informations - Partie 3: Schéma Informationslieferungen - Teil 3: Datenschema und
de données (ISO 29481-3:2022) Klassifikation (ISO 29481-3:2022)
This European Standard was approved by CEN on 21 July 2022.

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

Contents Page
European foreword . 3

European foreword
This document (EN ISO 29481-3:2022) 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 2023, and conflicting national standards shall be
withdrawn at the latest by April 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national standards
body/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 29481-3:2022 has been approved by CEN as EN ISO 29481-3:2022 without any
modification.
INTERNATIONAL ISO
STANDARD 29481-3
First edition
2022-09
Building information models —
Information delivery manual —
Part 3:
Data schema
Modèles des informations de la construction — Protocole d’échange
d’informations —
Partie 3: Schéma de données
Reference number
ISO 29481-3:2022(E)
ISO 29481-3:2022(E)
© ISO 2022
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 29481-3:2022(E)
Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Overview of the IDM schema . 2
4.1 Naming convention . 2
4.2 Restriction notation . 2
4.3 Overall structure of the IDM schema. 3
5 Information delivery manual .5
6 Specification identifier (specId) . .6
7 Authoring . 7
7.1 General . 7
7.2 Change log . 9
7.3 Author . 9
7.4 Committee . 10
7.5 Publisher . 10
8 Use case .11
8.1 General . 11
8.2 Summary . 13
8.3 Aim and scope . 13
8.4 Use . 13
8.5 Standard project phase .13
8.6 Local project phase . 14
8.7 Region . 14
8.8 Construction entity . 15
8.9 Business rule . 15
8.10 Actor . 16
8.11 Benefits . 16
8.12 Limitations . 16
8.13 Required resources . 16
8.14 Required competencies . 17
8.15 Reference . 17
8.16 User-defined property . 17
8.17 Classification . 18
8.18 Outcomes . 18
8.19 Information requirements . 18
8.20 Description . 19
8.21 Image . 19
9 Business context map .19
9.1 General . 19
9.2 Process map . 21
9.2.1 General . 21
9.2.2 Data object and ER . 21
9.3 Interaction map . 21
9.3.1 General . 21
9.3.2 Transaction map . 21
9.4 Diagram . 22
10 Exchange requirement .22
10.1 General .22
iii
ISO 29481-3:2022(E)
10.2 Information unit . 24
10.2.1 General . 24
10.2.2 Examples . 25
10.2.3 Corresponding external element . 25
10.3 Constraint . 25
10.4 Corresponding MVD .26
11 IDM code generation rules.26
Annex A (informative) The idmXML schema definition (idmXSD).28
Annex B (informative) IDM specification stages .29
Bibliography .30
iv
ISO 29481-3:2022(E)
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).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO’s adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/
iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 59, Buildings and civil engineering works,
Subcommittee SC 13, Organization and 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).
A list of all parts in the ISO 29481 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
v
ISO 29481-3:2022(E)
Introduction
This document specifies a machine applicable, readable and transferable (SMART) data schema for the
efficient development, management and reuse of information delivery manual (IDM) specifications
based on ISO 29481-1. ISO 29481-1 sets out a methodology for describing the processes and information
requirements for a defined purpose within the development or management of an asset. In the absence
of a standard data schema for exchanging and sharing the contents of IDMs in an electronic format, IDM
specifications have historically been developed as either a static document file or as a data file specified
in a proprietary data format. Consequently, their contents cannot be efficiently exchanged, shared
and reused. The goal of this document is to define a standard data schema in order to expedite the
development and sharing of the IDM specifications to meet the rapidly increasing demand for various
building information modelling (BIM) use cases (UCs).
Using extensible markup language (XML), this document specifies a data schema for authoring,
exchanging and sharing an IDM specification defined by ISO 29481-1. The data schema is referred to as
the idmXML schema definition (idmXSD). idmXSD aims to allow users to electronically store, search,
share, exchange and reuse IDM specifications and their contents, including metadata such as authors,
dates, languages, revision history and supported project phases, as well as detailed descriptions of each
information requirement. In addition, this document specifies the IDM code generation rules based on
their key properties.
Use of this document will improve the interoperability of IDM specifications and their contents,
providing tight digital links between the components of an IDM specification and to external data
definitions such as ISO 16739-1 (industry foundation classes, IFC), ISO 12006-3, ISO 19650-1, ISO 23386,
ISO 23387, EN 17412-1 (level of information need) and ISO 21597-1 (information container for linked
document delivery), as well as model view definitions (MVDs) of standard data schemas.
vi
INTERNATIONAL STANDARD ISO 29481-3:2022(E)
Building information models — Information delivery
manual —
Part 3:
Data schema
1 Scope
This document is the technical addition to the methodology set out in ISO 29481-1. It defines a
specification to store, exchange and read information delivery manual (IDM) specifications in a
standardized and machine-readable way.
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 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
ISO 22263, Organization of information about construction works — Framework for management of
project information
ISO 29481-1:2016, Building information models — Information delivery manual — Part 1: Methodology
and format
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 29481-1 and the following
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
attribute
XML construct that modifies or provides descriptive metadata about an element’s content
[SOURCE: ISO 20616-1:2021, 3.7, modified — The term “XML attribute” has been deleted. The phrase
“included within the start tag of an XML element” has been removed and “that element’s content” has
been replaced with “an element’s content”.]
3.2
information delivery manual code
IDM code
code for an IDM specification (3.3) created based on the key identifying features of an IDM specification
ISO 29481-3:2022(E)
3.3
information delivery manual specification
IDM specification
instance of an IDM and its components
3.4
use case
UC
description of an information use for a specific purpose by one or more actors and/or systems
3.5
business context map
description of the information flow in a business context represented in the form of a process map or
interaction map
4 Overview of the IDM schema
4.1 Naming convention
The naming convention shown below is used for the IDM schema elements.
a) The camel case convention shall be used for the naming of IDM schema elements.
b) Except for the terms below, all the terms shall be spelled out:
1) idm: information delivery manual;
2) uc: use case;
3) er: exchange requirement;
4) pm: process map;
5) im: interaction map;
6) tm: transaction map;
7) id: identifier.
c) Elements that represent descriptions, a group or a set shall be specified using a plural form.
EXAMPLE benefits, limitations, requiredResources, requiredCompetencies.
4.2 Restriction notation
The following XSD restriction notation is used for the IDM data schema.
— PK: primary key.
— Required: mandatory.
— Optional: not mandatory.
— The 1:1 restriction depicts that both the minimum and maximum occurrence of an element is 1. This
means there shall be one element.
— The 0:1 restriction depicts that the minimum occurrence of an element is 0 and the maximum
occurrence is 1.
— The 0:* restriction depicts the zero to many relationship, which is represented as minOccurs = "0"
to maxOccurs = "unbounded" in the XML schema.
ISO 29481-3:2022(E)
4.3 Overall structure of the IDM schema
The idmXSD consists of the idm element, its three core components (i.e. UC, business context map and
ER), and the relations and properties related to them.
— An IDM specification consists of a UC, business context maps and an ER.
— A UC shall include the header information specified in ISO 29481-1 and other metadata sufficient to
provide the context and the scope of an IDM.
— A business context map visually and formally represents the information delivery processes for a
UC. ISO 29481-1 requires the exchange method and process to be specified in one or more PM and/
or IM.
— An ER defines the information required by a specific UC at an individual information-unit level;
[19]
possibly with references to the elements of standard data schemas, such as CityGML , ISO 16739-1
[17]
(IFC), gbXML or ISO 12006-3.
Clauses 5 to 11 define the entities, relationships, attributes and restrictions of the IDM schema. Figure 1
illustrates a conceptual view of the IDM schema. A downloadable link to the full idmXSD is provided in
Annex A.
ISO 29481-3:2022(E)
Figure 1 — Conceptual view of the IDM schema in the unified modelling language (UML)
class diagram
ISO 29481-3:2022(E)
5 Information delivery manual
The idm element is a wrapper of core IDM components – namely UCs, business context maps and ERs
(see Figure 2). The constraints between them are as follows.
— The idm element shall be the single root element in the idmXSD.
— An idm element shall be associated with a single uc element and a single er element.
— An idm element may contain zero to many businessContextMap elements.
— The businessContextMap element and the er element may be left unspecified during the initial
development phase, to be detailed in a later version of the IDM specification as it is developed.
— An idm element may include zero to many subIdm elements. The other IDM components (i.e. the UC
element, the businessContextMap element and the er element) may also include zero to many sub-
elements.
This structure allows all the IDM components to be associated with multiple IDMs, UCs, business
context maps and ERs, which can be specified by external groups.

Figure 2 — XSD diagram of the IDM element
Table 1 lists the elements, types and restrictions of the IDM element.
Table 1 — IDM’s elements
Name Type Restriction Description
specId element 1:1 The specification identification information
(see Clause 6 for details).
authoring element 1:1 The author and change log information
(see Clause 7 for details).
subIdm element 0:* A subset of an IDM.
uc element 1:1 An associated UC.
businessContextMap element 0:* Associated business context maps.
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
ISO 29481-3:2022(E)
TTabablele 1 1 ((ccoonnttiinnueuedd))
Name Type Restriction Description
er element 0:1 An associated ER.
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
6 Specification identifier (specId)
Each IDM component shall have a set of identifiers. An IDM specification and its sub-UC, business
context map and ER shall use four types of identifiers: a globally unique identifier (GUID), an IDM code,
and user-defined full and short titles (guid, idmCode, fullTitle and shortTitle, respectively). Since an
IDM specification can be specified in any language, the short title shall be provided in English. These
are referred to as the “specId attribute group”. The specId attribute group shall include the attributes
specified in Figure 3 and Table 2.

Figure 3 — XSD diagram of the specId
ISO 29481-3:2022(E)
Table 2 — specId’s attributes
Name Type Restriction Description
guid string PK A globally unique identifier.
shortTitle string required A running title or byname for an IDM specification in
English.
localShortTitle string optional A running title or byname for an IDM specification in a local
language.
fullTitle string required A full name of an IDM specification.
subTitle string optional A supplementary title for an IDM specification.
idmCode string required A human- and machine-readable code, generated based
on the core metadata items of an IDM specification (see
Clause 11 for details).
localCode string optional A legacy identifier or a supplementary IDM identifier
generated according to a local code generation rule.
documentStatus string required The status of an IDM specification, from the initiation stage
to the official release stage.
The documentStatus shall be either one of NP (new
proposal), WD (working draft), PUB (publication) or
WDRL (withdrawal) (see Annex B for details).
localDocument- string optional The status of an IDM specification according to the local
Status document release status.
version string optional A combination of numbers and/or strings, which record the
development of an IDM specification.
7 Authoring
7.1 General
The authoring element stores the author information and the change history of IDM specifications,
including the changed contents, the principal or organization who created and changed the contents,
and the change date. An IDM specification shall be written by at least one author or one committee.
Authors can belong to one or more committees. The authoring element is composed of author,
committee, changeLog and publisher. The authoring’s attributes and elements are specified in Figure 4
and Table 3.
ISO 29481-3:2022(E)
Figure 4 — XSD diagram of the authoring attributes
ISO 29481-3:2022(E)
Table 3 — Authoring’s attributes and elements
Name Type Restriction Description
copyright string required A description about the copyright ownership and/or licence
information.
changeLog element 1:* The history of a specification: a chronological list of who
created and changed the specification, as well as when the
specification was created and changed (see 7.2 for details).
author element 0:* A person or organization that creates or modifies the IDM
specification (see 7.3 for details).
committee element 0:* The authoring group of the IDM specification (see 7.4 for
details).
publisher element 0:1 The publisher of the IDM specification (see 7.5 for details).
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
7.2 Change log
The changeLog consists of id, changeDateTime, changeSummary (content), changedBy (the author who
made a change) and changes. The IDM user or developer can track the changes in the IDM specifications
through the attributes in changeLog. The changeLog’s attributes and elements are specified in Tables 4
and 5.
Table 4 — changeLog’s attributes and elements
Name Type Restriction Description
id string PK A unique identifier assigned incrementally or
sequentially to an item to uniquely identify it.
changeDateTime dateTime required The date and time when the changes were made.
The format shall be “YYYY-MM-DD” as specified
by ISO 8601-1.
changeSummary string required A description of the change summary made in a
specification.
changedBy element 1:1 The author who created or made changes.
A reference to an id of the author element
(see 7.3 for details).
change element 0:* Each change instance in the changeLog.
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
Table 5 — Change’s attributes
Name Type Restriction Description
changedElement string required A metadata element that
was changed.
changedFrom string required A value before each
element has changed.
7.3 Author
The author element represents general information about the IDM creator and/or editor, such as
emailAddress, name (firstName, middleName and lastName), affiliation and id. An author can be a
person or an organization. The author’s attribute and elements are specified in Table 6. The person’s
attributes are specified in Table 7. The organization’s attributes are specified in Table 8.
ISO 29481-3:2022(E)
Table 6 — Author’s attribute and elements
Name Type Restriction Description
id string PK The unique identifier for
representing each author.
person element 1:* A person who authors an
IDM specification.
organization element 1:* An organized body of
people who author an IDM
specification.
NOTE  The XML elements are shaded in grey.
Table 7 — Person’s attributes
Name Type Restriction Description
firstName string required The first name of the author.
middleName string optional The middle name(s) of the author.
lastName string optional The last name of the author.
emailAddress string optional An email address of the author.
affiliation string optional The affiliations of the author.
Table 8 — Organization’s attribute
Name Type Restriction Description
name string required, unique The name of an organization.
7.4 Committee
The committee element shall be used when an IDM specification is developed by a named committee
of authors. The committee element includes name, leader, member, etc. The committee’s attribute and
elements are specified in Table 9.
Table 9 — Committee’s attributes and elements
Name Type Restriction Description
name string PK The name of an authoring group.
leader element 0.* The author who leads an IDM specification author team
(a reference to the identifier of an author who belongs
to a committee) (see 7.3 for details).
member element 0.* A reference to the identifier of an author who belongs to
a committee (see 7.3 for details).
NOTE  The XML elements are shaded in grey.
7.5 Publisher
The publisher element represents the entity that published the IDM specification. It is composed of the
name and location. The publisher’s attributes are specified in Table 10.
Table 10 — Publisher’s attributes
Name Type Restriction Description
name string required The entity that published the IDM specification.
location string optional The region (a country or a city) where the IDM specification
was published.
ISO 29481-3:2022(E)
8 Use case
8.1 General
The UC element in the IDM schema can be understood as a collection or an extension of the overview
information of a PM and an ER specified in ISO 29481-1. The UC attributes and elements are specified in
Figure 5 and Table 11 to Table 32.

Figure 5 — XSD diagram of the UC element
ISO 29481-3:2022(E)
Table 11 — UC’s elements
Name Type Restriction Description
specId element 1:1 The IDM specification identification information
(see Clause 6 for details).
authoring element 1:1 The author and changeLog information (see
Clause 7 for details).
subUc element 0:* A subset of a UC.
summary element 1:1 A brief of the aim and scope, benefits, and other
aspects of an IDM specification (see 8.2 for de-
tails).
aimAndScope element 1:1 The purpose and coverage of an IDM specification
(see 8.3 for details).
language element 1:1 The language used to define an IDM specification,
which shall be in accordance with ISO 639-1.
use element 1:* A method of utilizing information in a project for a
specific purpose (see 8.4 for details).
standardProjectPhase element 1:* The phase or stage of a project that an IDM speci-
fication is targeting in accordance with ISO 22263
(see 8.5 for details).
localProjectPhase element 0:* The phase or stage of a project that an IDM spec-
ification is targeting, based on a project life cycle
classification system chosen by the authors (e.g.
Generic Process Protocol (GPP), the American In-
stitute of Architects (AIA) or the Royal Institute of
British Architects (RIBA)) (see 8.6 for details).
region element 1:* A geographical area where a specified document
will be used (see 8.7 for details).
constructionEntity element 0.* A type of construction product by function
(see 8.8 for details).
businessRule element 0:* Operation, definition or constraint that can be
applied to a set of data used within a particular
process or activity (see 8.9 for details).
actor element 0:* The role or discipline of the project participant
who is sending and receiving information
(see 8.10 for details).
benefits element 0:1 A description of the advantages that can be gained
from a UC (see 8.11 for details).
limitations element 0:1 A description of the weaknesses, scope or distinc-
tive characteristics of a UC (see 8.12 for details).
requiredResources element 0:1 A description of the resources that are prerequi-
sites to begin a UC (see 8.13 for details).
requiredCompetencies element 0:1 A description of the competencies required by a
team member to conduct the activities specified in
a UC (see 8.14 for details).
scopeKeyword element 0:* A keyword that describes the scope of a UC.
benefitKeyword element 0:* A keyword that describes the advantages that can
be gained from a specified UC.
reference element 0:* An external source, such as a standard, to which
an IDM specification refers (see 8.15 for details).
userDefinedProperty element 0:* An additional property to further describe a UC
(see 8.16 for details).
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
ISO 29481-3:2022(E)
8.2 Summary
An overall summary of the purpose, scope, benefits and other aspects of an IDM specification shall be
specified using the summary element. A summary can be specified in multiple languages. However, the
first (default) summary shall be specified in English for international readers. The summary’s element
is specified in Table 12.
Table 12 — Summary’s element
Name Type Restriction Description
description element 1:* A textual or visual explanation.
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
8.3 Aim and scope
The purpose and coverage of an IDM specification shall be specified using the aim and scope element.
The aim and scope’s element is specified in Table 13.
Table 13 — Aim and scope’s element
Name Type Restriction Description
description element 1:* A textual or visual explanation.
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
8.4 Use
The use element is a high-level classification of information uses within an asset’s life cycle. If the
specified information use is based on any information-use classification system, the classification
system can be specified using the classification element. The name of a use shall be defined in the form
of a verb plus a noun, as specified in ISO 29481-1:2016, Table 1, Naming rule 3. The use’s attribute and
element are specified in Table 14.
EXAMPLE ModelWall, EstimateCost, CheckModelCompliance.
Table 14 — Use’s attribute and element
Name Type Restriction Description
name string required, unique The name of a use.
classification element 0:1 The classification system on which the
specified information use is based (see
8.17 for details).
NOTE  The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.
8.5 Standard project phase
The standardProjectPhase’s attributes represent the targeting life cycle phases of the IDM specifications.
In particular, the standard project phase, which follows ISO 22263, shall be specified for the design
coordination or cooperation between international companies or institutions. ISO 22263 classifies
a project life cycle into six phases: inception, brief, design, production, maintenance and demolition.
An IDM can target one or more phases. Additionally, the outcomes and the information requirements
of each phase can be described. The standard project phase’s attribute and elements are specified in
Table 15.
ISO 29481-3:2022(E)
Table 15 — standardProjectPhase’s attribute and elements
Name Type Restriction Description
name enumeration required, The name of the targeted life cycle phase
unique based on ISO 22263: an enumeration of
inception, brief, design, prod
...