FprEN ISO 29481-3

Building information models - Information delivery manual - Part 3: Data schema and code (ISO/FDIS 29481-3:2022)

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.

Bauwerksinformationsmodelle - Handbuch der Informationslieferungen - Teil 3: Datenschema und Klassifikation (ISO/FDIS 29481-3:2022)

Dieses Dokument ist die technische Ergänzung zu der in ISO 29481 1 festgelegten Methodik. Es definiert eine Spezifikation zum Speichern, Austauschen und Lesen von IDM-Spezifikationen in einer standardisierten und maschinenlesbaren Weise.

Modèles des informations de la construction - Protocole d’échange d’informations - Partie 3: Schéma de données et code (ISO/FDIS 29481-3:2022)

Le présent document est le complément technique de la méthodologie exposée dans l’ISO 29481‑1. Il définit une spécification pour le stockage, l’échange et la lecture des spécifications du protocole d’échange d’informations (IDM) sous une forme normalisée et lisible par un ordinateur.

Informacijski modeli stavb - Priročnik z informacijami - 3. del: Shema podatkov in koda (ISO/FDIS 29481-3:2022)

General Information

• Status: Not Published
• ICS: 35.240.67 - IT applications in building and construction industry
• ICS: 91.010.01 - Construction industry in general
• Technical Committee: CEN/TC 442 - Building Information Modelling (BIM)
• Drafting Committee: CEN/TC 442 - Building Information Modelling (BIM)
• Ref Project: kSIST FprEN ISO 29481-3:2022 - Building information models - Information delivery manual - Part 3: Data schema and code (ISO/FDIS 29481-3:2022)

Standards Content (sample)

SLOVENSKI STANDARD
oSIST prEN ISO 29481-3:2021
01-november-2021

Informacijski modeli stavb - Priročnik z informacijami - 3. del: Shema podatkov in

koda (ISO/DIS 29481-3:2021)

Building information models - Information delivery manual - Part 3: Data schema and

code (ISO/DIS 29481-3:2021)
Bauwerksinformationsmodelle - Handbuch der Informationslieferungen - Teil 3:
Datenschema und Klassifikation (ISO/DIS 29481-3:2021)

Modèles des informations de la construction - Protocole d’échange d’informations -

Partie 3: Schéma de données et code (ISO/DIS 29481-3:2021)
Ta slovenski standard je istoveten z: prEN ISO 29481-3
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
oSIST prEN ISO 29481-3:2021 en,fr,de

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN ISO 29481-3:2021
---------------------- Page: 2 ----------------------
oSIST prEN ISO 29481-3:2021
DRAFT INTERNATIONAL STANDARD
ISO/DIS 29481-3
ISO/TC 59/SC 13 Secretariat: SN
Voting begins on: Voting terminates on:
2021-08-31 2021-11-23
Building information models — Information delivery
manual —
Part 3:
Data schema and code
ICS: 35.240.67; 91.010.01
THIS DOCUMENT IS A DRAFT CIRCULATED
This document is circulated as received from the committee secretariat.
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
ISO/CEN PARALLEL PROCESSING
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 29481-3:2021(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. ISO 2021
---------------------- Page: 3 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2021

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved
---------------------- Page: 4 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(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) .......................................................................................................................................................... 5

7 Authoring ..................................................................................................................................................................................................................... 6

7.1 Changelog .................................................................................................................................................................................................... 8

7.2 Author ............................................................................................................................................................................................................. 8

7.3 Committee ................................................................................................................................................................................................... 9

7.4 Publisher ...................................................................................................................................................................................................... 9

8 Use Case ......................................................................................................................................................................................................................... 9

8.1 Summary ...................................................................................................................................................................................................11

8.2 Aim and Scope ......................................................................................................................................................................................12

8.3 Use ..................................................................................................................................................................................................................12

8.4 Standard project phase .................................................................................................................................................................12

8.5 Local project phase ...........................................................................................................................................................................12

8.6 Region ..........................................................................................................................................................................................................13

8.7 Construction entity ..........................................................................................................................................................................13

8.8 Business rule ..........................................................................................................................................................................................13

8.9 Actor ..............................................................................................................................................................................................................14

8.10 Benefits .......................................................................................................................................................................................................14

8.11 Limitations ...............................................................................................................................................................................................14

8.12 Required resources ..........................................................................................................................................................................15

8.13 Required competencies ................................................................................................................................................................15

8.14 Proposition ..............................................................................................................................................................................................15

8.15 Reference ..................................................................................................................................................................................................15

8.16 User defined property....................................................................................................................................................................15

8.17 Classification ..........................................................................................................................................................................................16

8.18 Outcomes ..................................................................................................................................................................................................16

8.19 Information Requirements ........................................................................................................................................................16

9 Business context map ...................................................................................................................................................................................16

9.1 Process map ............................................................................................................................................................................................18

9.1.1 Data object and ER ......................................................................................................................................................18

9.2 Interaction map ...................................................................................................................................................................................18

9.2.1 Transaction map............................................................................................................................................................18

9.3 Diagram ......................................................................................................................................................................................................19

9.3.1 Description .................. .................................................... ...................................................................................................19

10 Exchange requirement ................................................................................................................................................................................19

10.1 Information unit .................................................................................................................................................................................21

10.1.1 Examples ..............................................................................................................................................................................21

10.1.2 Corresponding external element ....................................................................................................................22

10.2 Constraint .................................................................................................................................................................................................22

10.3 Corresponding MVD ........................................................................................................................................................................22

11 IDM code generation rules ......................................................................................................................................................................23

© ISO 2021 – All rights reserved iii
---------------------- Page: 5 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

Annex A (informative) The idmXML schema Definition (idmXSD) ....................................................................................25

Annex B (informative) IDM document stages ...........................................................................................................................................26

iv © ISO 2021 – All rights reserved
---------------------- Page: 6 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(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 of information about construction works.
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.
© ISO 2021 – All rights reserved v
---------------------- Page: 7 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)
Introduction

This document defines the international standard for a machine applicable, readable and transferable

(SMART) data schema and code for the efficient development, management, and reuse of the

ISO 29481-1 (information delivery manual, IDM) specification. The information delivery manual (IDM)

specification sets out a methodology for describing the processes and data requirements for a defined

purpose within the development or management of a built facility. Due to the lack of a standard data

schema for exchanging and sharing the contents of IDMs in an electronic format, IDM documents have

historically been developed as either a static document file or as a data file specified in a proprietary

data format. Consequently, their contents could not be efficiently exchanged, shared, and reused. The

goal of ISO 29481-3 is to expedite the development and sharing of the IDM documents to meet the

rapidly increasing demand for various building information modelling (BIM) use cases.

ISO 29481-3 specifies a data schema for authoring, exchanging, and sharing an IDM document defined

by ISO 29481-1 in the XML (eXtensible Markup Language). The data schema is referred to as the idmXML

schema definition (idmXSD). idmXSD aims to allow users to electronically store, search, share and

exchange IDM documents and their contents, including meta-data such as authors, dates, languages,

revision history, 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.

This standard improves the interoperability of IDM documents and their contents, providing tight

digital links between the components of an IDM document; 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), ISO 21597-1 (Information Container for Linked Document

Delivery), and model view definitions (MVDs) of standard data schemas.
vi © ISO 2021 – All rights reserved
---------------------- Page: 8 ----------------------
oSIST prEN ISO 29481-3:2021
DRAFT INTERNATIONAL STANDARD ISO/DIS 29481-3:2021(E)
Building information models — Information delivery
manual —
Part 3:
Data schema and code
1 Scope

This part of ISO 29481 is the technical addition to the methodology set out in ISO 29481-1. It defines a

specification to store, exchange and read IDM documents 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 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/IEC Directives Part 1:2020 Procedures for the technical work

ISO 639-1:2002, Codes for the representation of names of languages — Part 1: Alpha-2 code

ISO 3166-1:2020, Codes for the representation of names of countries and their subdivisions — Part 1:

Country code

ISO 8601-1:2019, Date and time — Representations for information interchange — Part 1: Basic rules

ISO/IEC 9834-8:2005, Information Technology — Open Systems Interconnection

ISO 29481-1:2016, Building information models — Information delivery manual — Part 1: Methodology

and format

ISO 12006-2:2015, Building construction — Organization of information about construction works —

Part 2: Framework for classification

ISO 12006-3:2007, Building construction — Organization of information about construction works —

Part 3: Framework for object-oriented information

ISO 21597-1:2020, Information container for linked document delivery — Exchange specification — Part 1:

Container

ISO 22263:2008, Organization of information about construction works — Framework for management of

project information

ISO 23386:2020, Building information modelling and other digital processes used in construction —

Methodology to describe, author and maintain properties in interconnected data dictionaries

ISO 23387:2020, Building information modelling (BIM) — Data templates for construction objects used in

the life cycle of built assets — Concepts and principles
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 29481-1 and the following

apply.
© ISO 2021 – All rights reserved 1
---------------------- Page: 9 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
IDM code

identifier for an IDM document created based on the mandatory attributes of an IDM document

3.2
IDM document
instance of an IDM and its components
3.3
use case

description of an information use for a specific purpose by one or more actors and systems

3.4
business context map

description of the information flow in a business context represented, for example, 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.
— idm: information delivery manual
— uc: use case
— er: exchange requirement
— pm: process map
— im: interaction map
— tm: transaction map
— id: identifier

c) Elements that represent descriptions, a group, or a set shall be specified using a plural form.

EXAMPLE benefits, limitations, requiredResources, and requiredCompetencies
4.2 Restriction notation
The following XSD restriction notation is used for the IDM data schemas.
— PK: Primary Key
— Required: Mandatory
— Optional: Not mandatory
2 © ISO 2021 – All rights reserved
---------------------- Page: 10 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

— 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.
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 consists of a UC, a business context map, 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

use case. 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;

possibly with references to the elements of standard information schemas, such as cityGML,

ISO 16739-1 (IFC), gbXML, or ISO 12006-3.

The following clauses define the entities, relationships, attributes, and restrictions of the IDM schema.

Figure 1 illustrates a conceptual view of the IDM schema. The full idmXSD is presented in Annex A.

© ISO 2021 – All rights reserved 3
---------------------- Page: 11 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

Figure 1 — A logical view of the IDM schema in the unified modelling language (UML) class

diagram
4 © ISO 2021 – All rights reserved
---------------------- Page: 12 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)
5 Information Delivery Manual

The IDM element is a wrapper of core IDM components—namely UCs, business context maps, and ERs.

The constraints between them are as follows:
— The IDM element shall be the single root element in the idmXSD.
— An IDM shall be associated with exactly one UC.
— An IDM may contain zero to many business context maps and/or ERs.

— Business context map and ER components may be empty, to be detailed in a later revision.

— An IDM may include zero to many sub-IDMs. The other IDM components (i.e. UCs, business context

maps, and ERs) 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 might have been specified by external groups.
Figure 2 — An XSD diagram of the IDM element
Table 1 lists the elements, types, and restrictions of the IDM element.
Table 1 — The IDM’s elements
Name Type Restriction Description
specId element 1:1 The specification identification information
(see Clause 6 for the details)
authoring element 1:1 The author and change log information (see
Clause 7 for the details)
subIdm element 0:* A subset of an IDM.
uc element 1:1 An associated UC
businessContextMap element 0:* Associated business context maps
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 document and its sub-UC, business context

map, and ER shall use four types of identifiers: GUID, IDM code, and user-defined full and short titles

© ISO 2021 – All rights reserved 5
---------------------- Page: 13 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

(guid, idmCode, fullTitle, and shortTitle, respectively). These are referred to as the specId attribute

group. The specId attribute group shall include the following:
Figure 3 — An XSD diagram of the specId
Table 2 — The specId’s attributes
Name Type Restriction Description
guid string PK A globally unique identifier (GUID)
shortTitle string optional A running title or byname for an IDM document;
neither machine-interpretable, nor unique
fullTitle string required A full name of an IDM document; neither machine-in-
terpretable, nor unique
subTitle string optional A supplementary title for an IDM document; not unique
idmCode string required A human-readable and machine-readable identifier,
generated based on the mandatory metadata items
of an IDM document (see Clause 11 “IDM Code Gen-
eration Rules” 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 document; from the initiation

stage to the official release stage. The documentStatus
can be either one of NP (New Proposal), WD (Working
Draft), PUB (Publication), or WDRL (Withdrawal)
(See Annex B for details.)

localDocumentStatus string optional The status of an IDM document according to the local

document release status
version string optional A combination of numbers and/or strings, which
record the development of an IDM document
7 Authoring

The authoring element stores the author information and the change history of IDM documents,

including the changed contents, the principal or organization who created and changed the contents,

and the change date. An IDM document shall be written by at least one author or one committee. Authors

6 © ISO 2021 – All rights reserved
---------------------- Page: 14 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)

can belong to one or more committees. The authoring element is composed of author, committee,

changeLog, and publisher.
Figure 4 — An XSD diagram of the authoring attributes
© ISO 2021 – All rights reserved 7
---------------------- Page: 15 ----------------------
oSIST prEN ISO 29481-3:2021
ISO/DIS 29481-3:2021(E)
Table 3 — The authoring’s attributes and elements
Name Type Restriction Description

copyright string required A description about the copyright ownership and/or license

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.1 for the details)
author element 0:* A person who creates or modifies a specification (see 7.2 for
the details)

committee element 0:* The authoring group of the IDM document (see 7.3 for the details)

publisher element 0:1 The publisher of the IDM document (see 7.4 for the details)

NOTE The XML elements are shaded in grey. XML elements with sub-elements are depicted separately.

7.1 Changelog

The changeLog consists of id, changeDateTime, changeSummary (content), changedBy (the author who

made a change) and change. The IDM user or developer can track the changes in the IDM documents

through the attributes in changeLog.
Table 4 — The changelog’s attributes and elements
Name Type Restriction Description
id string PK A unique identifier assigned incrementally or se-
quentially to an item to uniquely identify it
changeDateTime dateTime required The date and time when the changes were made.
The format is defined by ISO 8601-1:2019
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 ref-
erence to an id of the a
...