Guidance for understanding and utilize EN/ISO 29481-1 Building information models - Information delivery manual - Part 1: Methodology and format

This document provides guidance on how to develop an information delivery manual (IDM) in compliance with EN ISO 29481-1 hereafter referred to as the “IDM standard”. This document explains the core components and development process of the IDM methodology in non-technical terms. This document aims to help users and software vendors understand and utilize the IDM standard in defining information requirements and deliverables.
The technical implementation of IDM in a data model, model view definition  (MVD), is excluded from this document’s scope. IDM standard introduces the MVD concept but does not specify it in detail.
This document also utilizes some transaction framework concepts introduced in EN ISO 29481-2. The technical XML- and XSD-schema definitions supporting the software solutions are excluded from this document.

Anleitung zum Verständnis und zur Umsetzung der EN/ISO 29481-1 Bauwerksinformationsmodelle - Handbuch der Informationslieferungen - Teil 1: Methodik und Format

Document d’orientation pour comprendre et utiliser l’EN/ISO 29481-1, Modèles des informations de la construction - Protocole d’échange d’informations - Partie 1 : Méthodologie et format

1.1   Généralités
Le présent document fournit des recommandations relatives à l’élaboration d’un protocole d’échange d’informations (IDM) conformément à l’EN ISO 29481 1 (par la suite désignée « la norme IDM »). Le présent document explique les principaux composants et le processus d’élaboration de la méthodologie IDM en termes non techniques. Le présent document vise à aider les utilisateurs et les distributeurs de logiciels à comprendre et utiliser la norme IDM afin de définir les exigences relatives aux informations et aux informations à livrer.
La mise en œuvre technique d’un IDM dans un modèle de données, désigné Définition de vue du modèle (Model View Definition , MVD) », n’entre pas dans le domaine d’application du présent document. La norme IDM présente le concept de MVD, mais sans entrer dans les détails.
Le présent document d’orientation reprend également plusieurs concepts de cadre de transaction présentés dans l’EN ISO 29481 2. Les définitions techniques des schémas XML et XSD pour guider des solutions logicielles sont exclues du présent document.
[…]

Navodila za razumevanje in uporabo EN/ISO 29481-1 Informacijski modeli stavb - Priročnik z informacijami - 1. del: Metodologija in oblika

General Information

Status
Published
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Due Date
22-Dec-2021
Completion Date
22-Dec-2021

Buy Standard

Technical report
-TP CEN/TR 17741:2022 - BARVE na PDF-str 7,20
English language
19 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TP CEN/TR 17741:2022
01-marec-2022
Navodila za razumevanje in uporabo EN/ISO 29481-1 Informacijski modeli stavb -
Priročnik z informacijami - 1. del: Metodologija in oblika

Guidance for understanding and utilize EN/ISO 29481-1 Building information models -

Information delivery manual - Part 1: Methodology and format
Anleitung zum Verständnis und zur Umsetzung der EN/ISO 29481-1

Bauwerksinformationsmodelle - Handbuch der Informationslieferungen - Teil 1: Methodik

und Format
Guide pour comprendre et utiliser EN/ISO 29481-1 Modèles des informations de la

construction - Protocole d`échange dìnformation - Partie 1: Méthodologie et format

Ta slovenski standard je istoveten z: CEN/TR 17741:2021
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
SIST-TP CEN/TR 17741:2022 en,fr,de

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

---------------------- Page: 1 ----------------------
SIST-TP CEN/TR 17741:2022
---------------------- Page: 2 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741
TECHNICAL REPORT
RAPPORT TECHNIQUE
December 2021
TECHNISCHER BERICHT
ICS 91.010.01; 35.240.67
English Version
Guidance for understanding and utilize EN/ISO 29481-1
Building information models - Information delivery
manual - Part 1: Methodology and format

Document d'orientation pour comprendre et utiliser Anleitung zum Verständnis und zur Umsetzung der

l'EN/ISO 29481-1 Modèles des informations de la EN/ISO 29481-1 Bauwerksinformationsmodelle -

construction - Protocole d'échange d'informations - Handbuch der Informationslieferungen - Teil 1:

Méthodologie et format Methodik und Format

This Technical Report was approved by CEN on 5 December 2021. It has been drawn up by the Technical Committee CEN/TC

442.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,

Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,

Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey 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

© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 17741:2021 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
Contents Page

European foreword ....................................................................................................................................................... 3

1 Scope .................................................................................................................................................................... 4

1.1 General ................................................................................................................................................................ 4

1.2 Background ....................................................................................................................................................... 4

1.3 Users of this guidance document ............................................................................................................... 5

1.4 Relation to EN ISO 19650.............................................................................................................................. 5

1.5 How to use this guidance document ......................................................................................................... 5

2 Normative references .................................................................................................................................... 6

3 Terms and definitions ................................................................................................................................... 6

4 What is an Information Delivery Manual (IDM) ............................................................................... 10

4.1 General ............................................................................................................................................................. 10

4.2 Structure of IDM ........................................................................................................................................... 10

4.3 Use case ............................................................................................................................................................ 11

4.4 Process definition ........................................................................................................................................ 11

4.4.1 General ............................................................................................................................................................. 11

4.4.2 Process map ................................................................................................................................................... 12

4.4.3 Interaction map ............................................................................................................................................ 12

4.4.4 Transaction map ........................................................................................................................................... 13

4.5 Exchange requirement ............................................................................................................................... 14

4.5.1 General ............................................................................................................................................................. 14

4.5.2 Geometrical information ........................................................................................................................... 15

4.5.3 Alphanumerical information ................................................................................................................... 15

4.6 Model View Definition (MVD) .................................................................................................................. 16

5 How to create an IDM .................................................................................................................................. 16

5.1 General ............................................................................................................................................................. 16

5.2 Defining the use case .................................................................................................................................. 16

5.3 Finding a suitable approach ..................................................................................................................... 17

5.3.1 General ............................................................................................................................................................. 17

5.3.2 Reverse engineering ................................................................................................................................... 17

5.3.3 Information constraint customization ................................................................................................. 17

5.3.4 Process discovery ......................................................................................................................................... 18

5.4 Defining the exchange requirement ...................................................................................................... 18

Bibliography ................................................................................................................................................................. 19

---------------------- Page: 4 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
European foreword

This document (CEN/TR 17741:2021) has been prepared by Technical Committee CEN/TC 442 “Building

Information Modeling”, the secretariat of which is held by SN.

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. CEN shall not be held responsible for identifying any or all such patent rights.

Any feedback and questions on this document should be directed to the users’ national standards body.

A complete listing of these bodies can be found on the CEN website.
---------------------- Page: 5 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
1 Scope
1.1 General

This document provides guidance on how to develop an information delivery manual (IDM) in

compliance with EN ISO 29481-1 hereafter referred to as the “IDM standard”. This document explains the

core components and development process of the IDM methodology in non-technical terms. This

document aims to help users and software vendors understand and utilize the IDM standard in defining

information requirements and deliverables.

The technical implementation of IDM in a data model, model view definition (MVD), is excluded from

this document’s scope. IDM standard introduces the MVD concept but does not specify it in detail.

This document also utilizes some transaction framework concepts introduced in EN ISO 29481-2. The

technical XML- and XSD-schema definitions supporting the software solutions are excluded from this

document.
1.2 Background

This document primary reference is the IDM standard part 1 (EN ISO 29481-1:2017) (hereafter referred

to as IDM standard). This document helps in understanding and using the IDM standard to describe

information delivery. This document also uses some concepts described in part 2 of the IDM standard

series (EN ISO 29481-2:2016). Considerable efforts have been made to align this document with the

terminology and concepts introduced in EN ISO 19650-1 and EN ISO 19650-2.

Information delivery manual specification (hereafter referred to as the IDM specification) provides help

in getting the full benefit from building information modelling (BIM). When the required information is

available using BIM to support a construction process or use case, and the quality of information is

satisfactory, the process itself is much improved. The IDM standard provides a method to create the

specification.

A complete IDM specification should support two perspectives: user requirements and technical

solutions. User requirements describe the needed information delivery and the overall process in which

information exchange occurs. The technical solution defines an exchange requirement model using a

harmonized data schema.

EN ISO 29481-1 provides a methodology and a harmonized format to specify information requirements.

It offers a framework and method to determine the needed information delivery with process maps and

exchange requirements.

EN ISO 29481-2 specifies an interaction framework and format to describe “coordination acts” between

actors or parties within an appointment. It facilitates interoperability between software applications

used in the construction process to promote digital collaboration between actors in the building

construction process. Also, it provides a basis for accurate, reliable, repeatable, and high-quality

information exchange.

An MVD defines a data model or a subset of an existing data model that is necessary to support one or many specific data

exchange requirements. MVDs are used in software development and should have a machine-readable representation. An MVD

that is dedicated to a single IDM can be used to filter information in software tools to a specific exchange requirement. [SOURCE:

EN ISO 29481-1:2017, 5.6.4].
---------------------- Page: 6 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
1.3 Users of this guidance document

This document is intended for clients, architects, engineers, contractors, surveyors, authorities, and other

parties who need to specify or implement information delivery. Originally, the IDM standard was focused

on defining model-based deliverables, but the possible application of the standard is much broader. It can

be used to specify any requirement for information delivery.

Although software developers and technology adapters are not the primary audiences of this document,

it may help them better understand existing IDMs and develop their own IDMs.
1.4 Relation to EN ISO 19650

The IDM standard is a process-oriented methodology used to describe the information exchange

requirements for a particular purpose which may complement the information-management approach

outlined in the EN ISO 19650 series. Simultaneously, the IDM standard pre-dates EN ISO 19650 and has

a broader scope of application beyond model-based information exchanges.

Figure 1 — IDM specifications can support the definition of the information requirements and to

verify the information deliverables

The scope of EN ISO 19650-1 stipulates that information deliverables “should be described clearly within

the OIR, PIR, AIR or EIR”. Figure 1 depicts how IDMs can support the definition of information

deliverables for these requirements. The figure also shows how the IDM standard can be applied to use

cases outside of the EN ISO 19650 series scope. These use cases may include information requirements

for regulatory processes or other common demands such as national information standards. In addition,

Figure 1 presents how the IDM that is used to specify the exchange requirement can be used to verify the

information delivery.
1.5 How to use this guidance document
This document is split into two sections:

— The first section explains the IDM components and can be used to get a better understanding of the

IDM structure.

— The second section gives and overview of the IDM methodology and steps through how to create an

IDM.
In both sections the IDM standard can be used in parallel to this document.

Several similar terms are used in this document, the following list helps clarify these terms:

— IDM standard: this is the EN ISO 29481-1 standard itself (as indicated in 1.2 above);

---------------------- Page: 7 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)

— IDM specification: this is information delivery manual specification (as indicated in 1.2 above); and

— IDM method: This is the general method of developing an IDM.

As noted above, this document has references to part 2 of the IDM standard series (EN ISO 29481-2). To

avoid confusion, in these cases the standard code is mentioned in its full length i.e. EN ISO 29481-2.

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.

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

format (ISO 29481-1)

EN ISO 29481-2, Building information models — Information delivery manual — Part 2: Interaction

framework (ISO 29481)
3 Terms and definitions

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

EN ISO 29481-2 and the following apply.

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

— IEC Electropedia: available at https://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
3.1
activities
tasks that are needed to complete deliverables
[SOURCE: EN 15221-5:2011, 3.1]
3.2
actor
person, organization or organizational unit involved in a construction process

Note 1 to entry: Organizational units include, but are not limited to, departments, teams.

Note 2 to entry: In the context of this document, construction processes take place during the delivery phase and

the operational phase.

[SOURCE: EN ISO 29481-1:2017, 3.1, as modified by EN ISO 19650-1:2018, 3.2.1: The words “such as a

department, team, etc.” have been removed; Note 1 and 2 to entry have been added.]

3.3
appointment

agreed instruction for the provision of information concerning works, goods or services

Note 1 to entry: This term is used whether or not there is a formal appointment between the parties.

[SOURCE: EN ISO 19650-1:2018, 3.2.2]
---------------------- Page: 8 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
3.4
asset
item, thing or entity that has potential or actual value to an organization

[SOURCE: ISO 55000:2014, 3.2.1, as modified by EN ISO 19650-1:2017, 3.2.8: Note 1, 2 and 3 to entry

have been removed.]
3.5
business process

partially ordered set of enterprise activities that can be executed to achieve some desired end-result in

pursuit of a given objective of an organization
[SOURCE: ISO/IEC/IEEE 24765:2017, 3.445]
3.6
BIM execution plan

plan that specifies in detail how the information management aspects of the appointment will be carried

out by the delivery team

Note 1 to entry: The pre-appointment BIM execution plan focuses on the delivery team’s proposed approach to

information management, and their capability and capacity to manage information.
[SOURCE: EN ISO 19650-2:2018, 3.1.3.1]
3.7
end user
person receiving facility services
Note 1 to entry: A visitor could also be an end user.
[SOURCE: EN 15221-5:2011, 3.4]
3.8
exchange information requirements
EIR
information requirements in relation to an appointment
[SOURCE: EN ISO 19650-1:2018, 3.3.6]
3.9
Industry Foundation Classes
IFC

conceptual data schema and exchange file format for building information modelling (BIM) data

Note 1 to entry: See EN ISO 16739-1:2020.
3.10
information

interpretable representation of data in a formalized manner suitable for communication, interpretation

or processing
Note 1 to entry: Information can be processed by human or automatic means.
[SOURCE: EN ISO 19650-1:2018, 3.3.1]
---------------------- Page: 9 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
3.11
information requirement
specification for what, when, how and for whom information is to be produced
[SOURCE: EN ISO 19650-1:2018, 3.3.2]
3.12
level of information need
framework which defines the extent and granularity of information
[SOURCE: EN ISO 19650-1:2018, 3.3.16]
3.13
process

set of interrelated or interacting activities that use inputs to deliver an intended result

Note 1 to entry: Whether the “intended result” of a process is called output, product or service depends on the

context of the reference.

Note 2 to entry: Inputs to a process are generally the outputs of other processes and outputs of a process are

generally the inputs to other processes.

Note 3 to entry: Two or more interrelated and interacting processes in series can also be referred to as a process.

Note 4 to entry: Processes in an organization are generally planned and carried out under controlled conditions

to add value.

Note 5 to entry: A process where the conformity of the resulting output cannot be readily or economically

validated is frequently referred to as a “special process”.

Note 6 to entry: This constitutes one of the common terms and core definitions for ISO management system

standards given in Annex SL of the Consolidated ISO Supplement to the ISO/IEC Directives, Part 1. The original

definition has been modified to prevent circularity between process and output and Notes 1 to 5 to entry have been

added.
[SOURCE: EN ISO 9000:2015, 3.4.1]
3.14
business process model and notation
BPMN

graphical representation for specifying dynamic business processes in a business process model

[SOURCE: ISO/IEC 19510:2013]
3.15
project information requirements
PIR
information requirements in relation to the delivery of an asset
[SOURCE: EN ISO 19650-1:2018, 3.3.5]
---------------------- Page: 10 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
3.16
purpose

context and conditions of data/record use at a specific point in time, and within a specific setting

[SOURCE: ISO/TS 21089:2018, 3.117.1]
3.17
organization information requirements
OIR
information requirements in relation to organizational objectives
[SOURCE: ISO 19650-1:2018, 3.3.3]
3.18
requirement
need or expectation that is stated, generally implied or obligatory

Note 1 to entry: “Generally implied” means that it is custom or common practice for the organization and

interested parties that the need or expectation under consideration is implied.

Note 2 to entry: A specified requirement is one that is stated, for example in documented information.

[SOURCE: ISO/IEC 27000:2018, 3.56]
3.19
reverse engineering

design process that consists in analysing the shape, dimensions and function of a finished part or

prototype and using this information to produce a similar product
[SOURCE: ISO/TS 14253-4:2010, 3.1]
3.20
specification
document stating requirements

EXAMPLE Quality manual, quality plan, technical drawing, procedure document, work instruction.

Note 1 to entry: A specification can be related to activities (e.g. procedure document, process specification and

test specification), or products (e.g. product specification, performance specification and drawing).

Note 2 to entry: It can be that, by stating requirements, a specification additionally is stating results achieved by

design and development and thus in some cases can be used as a record.
[SOURCE: EN ISO 9000:2015, 3.8.7]
3.21
use case

textual and graphical depiction of the actors and operations that address information

exchange in the context of a set of specific tasks for a workflow performed by different systems or devices

[SOURCE: ISO/TR 28380-1:2014, 2.13]
---------------------- Page: 11 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
3.22
use case

typical application stated at a high level for the purposes of extracting

technical considerations or comparing usages across fields
[SOURCE: ISO/IEC TR 20547-2:2018, 3.2.1]
4 What is an information delivery manual (IDM)
4.1 General

The term IDM is used both for the standardized method that describes information requirements for a

specific purpose, and the actual specification that is the outcome of the development process that utilizes

the IDM methodology. The IDM methodology is described in Clause 5.

Harmonized IDM specifications help all project actors understand the actual information needs. The IDM

specification supports these actors to deliver the correct information in the correct format at the correct

time. This leads to fewer errors and results in productivity improvements. IDM specifications can be used

to specify the information exchange requirements in the appointment process – both in the invitation to

tender and in contractual documents – as well as guidance during project execution. For software

vendors, an IDM is the initial data for software development that combines a definition of the business

needs and precise requirements for the information exchange.

IDMs can support the information requirement definitions presented in Figure 1. The detail level of the

exchange requirement may vary in different use cases. For example, on the project and asset level, most

if not all of the requirements should be very specific. At the same time, on the organizational level, some

of the requirements can be more general, reflecting the strategic goals of the organization.

4.2 Structure of IDM specification

The IDM specification is a technical document (physical or digital) that describes business needs,

activities and transactions and information exchange requirement for a specific purpose that, in this

context, is a synonym to use case. An IDM specification is a way to record and share use cases in a

harmonized way.

The activities and transactions fulfilling the objectives of the use case are outlined with process,

transaction and interaction maps. The information exchange requirements should be explained in a non-

technical way. A technical description may be considered to support machine-readable data exchange.

In short, an IDM has three core elements (see Figure 2):

— The first element of IDM is use case which summarizes the business need of the information

exchange. It is a description of information used for a specific purpose and scope;

— The second element is process definition which outlines the activities and transactions between

different actors. These are represented with different types of process, transaction and interaction

maps;

— The third element and the end result of the IDM development process is exchange requirement (ER)

that describes the alphanumerical and geometrical information requirements for the use case. These

properties may be presented in non-technical terms but should be specific.
---------------------- Page: 12 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)
Figure 2 —The core elements of IDM development

To support machine-readable data exchange, the exchange requirement may be further developed to a

model view definition (MVD) which is a technical description of the needed data.
4.3 Use case

The use case is the starting point of the IDM development. It describes the purpose and the scope for the

information exchange together with the ideal scenario, goals, and success criteria. The different parties

and their responsibilities are specified with actors and roles. Use case also outlines the initial activities of

the parties in the information exchange. Agreements, contracts, standards etc. deal with the external

conditions that may have an effect on the objectives or deliverables of the information exchange.

The use case should describe:
— Who are the actors, and what are their roles and interests?
— How can the information exchange be prepared and handled? and

— How existing agreements, contractual conditions, standards, etc. will support the information

exchange?

When collecting this information, it is necessary to identify who is able to describe these needs. The use

case preparation ends with an assessment of whether it is possible to reach the business needs stated by

the goals and success criteria. If the assessment is positive, the actual IDM development can be initiated.

If the assessment is negative, the use case may need to be revised.

A use case can also be used as an independent concept without further development to an IDM. In this

case the use case is established without developing a process map or defining the exchange requirement.

EXAMPLE Calculating rental areas is a process that provides the client with information about the projects

potential return on investment costs. In this use case, the income calculation is based on room areas in the

architect's design model. For a successful outcome, both the design model and the rentable area calculation need to

meet the criteria provided by the tenant manager.

The purpose of information delivery is the income calculation based on rentable areas. The initial information for

calculation is the IfcSpace geometry exported from the design model, and all changes to the geometry are handled

in the design model. The actors and roles are client as the appointing party, tenant manager as the business case

owner, architect as the designer, the BIM manager responsible for the IFC quality assurance and area manager who

extracts the rentable areas from the room geometry and provides the calculations. Some of these roles can be

appointed to a single actor.

The calculation frequency is based on the appointment contracts, and the output should be in a harmonized format

provided by the client.
4.4 Process definition
4.4.1 General

Activities and transactions describe the process of information production and exchange points within

the use case. The process definition needs to specify the tasks and responsibilities of each actor. The IDM

standard proposes several methods that can be used to describe the process: process map, interaction

map and transaction map. A process map provides the overall representation of the process, whereas the

---------------------- Page: 13 ----------------------
SIST-TP CEN/TR 17741:2022
CEN/TR 17741:2021 (E)

interaction map may be used to support, or in some cases, to replace the process map. Transaction maps

describe interactions in detail. Each map type is described below with an example.

4.4.2 Process map

A process map is an activity-based diagram that describes the activities that lead to information exchange.

In IDM development, process maps are presented using Business Process Model and Notation (BPMN)

graphical representation.

EXAMPLE Continuing the use case example above, the client asks the project team to calculate rental profits

from the current design alternative. The tenant manager provides the calculation criteria to the architect who

updates the design BIM following the criteria and exports the IFC model. The BIM manager checks that the IFC

model meets the criteria. If it does, the BIM manager delivers the model to the area manager who calculates the

rentable areas based on the IFC model and the criteria provided by the tenant
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.