Building Information Modelling - Level of Information Need - Part 1: Concepts and principles

This document specifies concepts and principles to establish a methodology for specifying level of information need and information deliveries in a consistent way when using Building Information Modelling (BIM).
This document specifies the characteristics of different levels used for defining the detail and extent of information required to be exchanged and delivered throughout the life cycle of built assets. It gives guidelines for principles required to specify information needs.
The concepts and principles in this document can be applied for a general information exchange and whilst in progress, for a generally agreed way of information exchange between parties in a collaborative work process, as well as for a contractually specified information delivery.
The level of information need provides methods for describing information to be exchanged according to exchange information requirements. The exchange information requirements specify the wanted information exchange. The result of this process is an information delivery.
The concepts and principles contained in this document are applicable to all those involved in the asset life cycle. This includes, but is not limited to, the asset owner/operator, the project client, the asset manager, the design team, the construction supply chain, the equipment manufacturer, the system specialist, the regulator, and the end-user.

Bauwerksinformationsmodellierung - Informationsbedarfstiefe - Teil 1: Konzepte und Grundsätze

Dieses Dokument legt Konzepte und Grundsätze fest, um eine Methodik für die Festlegung der Informationsbedarfstiefe und von Informationsbereitstellungen für die Anwendung von Building Information Modeling (BIM) in einer konsistenten Weise aufzustellen.
Dieses Dokument legt die Ausprägung verschiedener Stufen fest, die bei der Definition der Detaillierung und des Umfangs von Informationen angewendet werden, die über den gesamten Lebenszyklus von Bauwerken ausgetauscht und geliefert werden müssen. Es gibt Leitlinien für Grundsätze, die für die Festlegung des Informationsbedarfs erforderlich sind.
Die Konzepte und Grundsätze in diesem Dokument können für den allgemeinen Informationsaustausch angewendet werden und sorgen für eine im Allgemeinen vereinbarte Weise des Informationsaustauschs zwischen den Parteien in einem kollaborativen Arbeitsprozess sowie für eine vertraglich festgelegte Informationsbereitstellung.
Die Informationsbedarfstiefe bietet Methoden, um die auszutauschenden Informationen in Übereinstimmung mit den Austausch-Informationsanforderungen zu beschreiben. Die Austausch-Informationsanforderungen legen den gewünschten Informationsaustausch fest. Das Ergebnis dieses Prozesses ist eine Informationsbereitstellung.
Dieses Dokument gilt während des gesamten Lebenszyklus eines Gebäudes, einschließlich der strategischen Planung, des Erstentwurfs, der Ingenieurtechnik, der Entwicklung, der Dokumentation und der Konstruktion, des Betriebs im Alltag, der Instandhaltung, der Modernisierung, der Instandsetzung und des Lebensdauerendes.

Modélisation des Informations pour la Construction (BIM) - Niveau d’Information Requis - Concepts et Principes

Le présent document spécifie les concepts et les principes permettant d’établir une méthodologie de spécification cohérente du niveau du besoin d’information et des livraisons d’information à l’aide de la modélisation des informations de la construction (BIM).
Le présent document spécifie les caractéristiques des différents niveaux utilisés pour définir le détail et l’étendue des informations qu’il est nécessaire d’échanger et de livrer tout au long du cycle de vie des actifs bâtis. Il donne des lignes directrices sur les principes requis pour spécifier les besoins d’information.
Les concepts et les principes énoncés dans le présent document peuvent s’appliquer à un échange général d’informations et, dans le même temps, à un mode communément accepté d’échange d’informations entre des parties dans le cadre d’un processus de travail collaboratif, ainsi qu’à une désignation accompagnée d’une livraison d’informations spécifiée.
Le niveau du besoin d’information fournit des méthodes pour décrire les informations à échanger conformément aux exigences d’échange d’informations. Les exigences d’échange d’informations spécifient l’échange d’informations souhaité. Le résultat de ce processus est une livraison d’informations.
Le présent document s’applique à la totalité du cycle de vie d’un actif bâti, y compris la planification stratégique, la conception initiale, l’ingénierie, le développement, la documentation et la construction, l’exploitation quotidienne, la maintenance, la réhabilitation, la réparation et la fin de vie.

Informacijsko modeliranje gradenj - Raven informacijskih potreb - 1. del: Pojmi in načela

General Information

Status
Published
Public Enquiry End Date
12-Sep-2019
Publication Date
11-Jan-2021
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
16-Dec-2020
Due Date
20-Feb-2021
Completion Date
12-Jan-2021

Relations

Buy Standard

Standard
EN 17412-1:2021 - BARVE
English language
25 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day
Draft
prEN 17412:2019 - BARVE
English language
24 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 17412-1:2021
01-februar-2021
Informacijsko modeliranje gradenj - Raven informacijskih potreb - 1. del: Pojmi in
načela
Building Information Modelling - Level of Information Need - Part 1: Concepts and
principles
Modélisation des Informations pour la Construction (BIM) - Niveau d’Information Requis -
Concepts et Principes
Ta slovenski standard je istoveten z: EN 17412-1:2020
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 EN 17412-1:2021 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST EN 17412-1:2021

---------------------- Page: 2 ----------------------
SIST EN 17412-1:2021


EN 17412-1
EUROPEAN STANDARD

NORME EUROPÉENNE

November 2020
EUROPÄISCHE NORM
ICS 35.240.67
English Version

Building Information Modelling - Level of Information
Need - Part 1: Concepts and principles
Modélisation des informations de la construction - Building Information Modelling -
Niveau du besoin d'information - Partie 1 : Concepts et Informationsbedarfstiefe - Konzepte und Definitionen
principes
This European Standard was approved by CEN on 18 October 2020.

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

---------------------- Page: 3 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
Contents                                                             Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 General. 8
5 Framework to specify the level of information need . 8
5.1 General. 8
5.2 Consider the purposes . 8
5.3 Consider the information delivery milestones . 9
5.4 Consider the actors . 9
5.5 Consider the objects within a breakdown structure. 9
6 Definition of level of information need and its subdivision . 10
6.1 General. 10
6.2 Geometrical information . 11
6.2.1 General. 11
6.2.2 Detail . 11
6.2.3 Dimensionality . 13
6.2.4 Location . 14
6.2.5 Appearance . 14
6.2.6 Parametric behaviour . 15
6.2.7 Relationships of aspects of geometrical information and prerequisites . 16
6.3 Alphanumerical information . 16
6.3.1 General. 16
6.3.2 Identification . 17
6.3.3 Information content . 17
6.4 Documentation . 17
6.5 Relationship diagram on level of information need . 18
7 Verification and validation . 19
Annex A (informative) Overview of the main concepts related to information exchange . 20
Annex B (informative) Example of method to specify level of information need . 21
Bibliography . 25


2

---------------------- Page: 4 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
European foreword
This document (EN 17412-1:2020) has been prepared by 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 May 2021, and conflicting national standards shall be
withdrawn at the latest by May 2021.
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.
According to the CEN-CENELEC Internal Regulations, the national standards organisations 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, Turkey and the
United Kingdom.
3

---------------------- Page: 5 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
Introduction
This document sets out the concepts and principles for defining the level of information need and
information deliveries being part of the information exchange processes during the life cycle of built
assets when using building information modelling (BIM). Those concepts and principles can deliver
clear benefits to all participants in the various life cycle phases of built assets as they provide a common
understanding on the right level of information needed at a certain time. One purpose of defining the
level of information need is to prevent delivery of too much information. Information exchange should
ensure the right information to be delivered for the agreed purpose to facilitate verification and
validation processes.
This document provides methods for describing information to be exchanged according to exchange
information requirements. The exchange information requirements specify the wanted information
exchange. The result of this process is an information delivery.
There is a need that these concepts and principles are described in a common and comparable way to
allow services related to building information modelling to be procured and offered on a European
scale. The need has arisen by the fact that there are several conflicting terms, concepts and usages in
place, both internationally and across Europe, that hinder the objective of having a common
understanding and practise in describing the level of information need for a common European market.
It is therefore helpful not to use an acronym to refer to level of information need as this can
oversimplify these concepts.
The concepts and principles contained in this document are aimed at all those involved in the asset life
cycle. This includes, but is not limited to, the asset owner/operator, the client, the asset manager, the
design team, the construction team, an equipment manufacturer, a technical specialist, a regulatory
authority, an investor, an insurer and an end-user.
The information exchange, as well as related topics such as the exchange information requirements and
the information delivery are defined and explained in context of two related standards:
EN ISO 19650-1, Organization and digitization of information about buildings and civil engineering
works, including building information modelling (BIM) — Information management using building
information modelling — Part 1: Concepts and principles; and
EN ISO 29481-1, Building information models — Information delivery manual — Part 1: Methodology and
format.
4

---------------------- Page: 6 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
1 Scope
This document specifies concepts and principles to establish a methodology for specifying level of
information need and information deliveries in a consistent way when using building information
modelling (BIM).
This document specifies the characteristics of different levels used for defining the detail and extent of
information required to be exchanged and delivered throughout the life cycle of built assets. It gives
guidelines for principles required to specify information needs.
The concepts and principles in this document can be applied for a general information exchange and
whilst in progress, for a generally agreed way of information exchange between parties in a
collaborative work process, as well as for an appointment with specified information delivery.
The level of information need provides methods for describing information to be exchanged according
to exchange information requirements. The exchange information requirements specify the wanted
information exchange. The result of this process is an information delivery.
This document is applicable to the whole life cycle of any built asset, including strategic planning, initial
design, engineering, development, documentation and construction, day-to-day operation, maintenance,
refurbishment, repair and end-of-life.
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:2017, Building information models —Information delivery manual — Part 1:
Methodology and format (ISO 29481-1:2016)
ISO 6707-1, Buildings and civil engineering works — Vocabulary — Part 1: General terms
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN ISO 29481-1:2017, ISO 6707-1
and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at https://www.iso.org/obp
5

---------------------- Page: 7 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
3.1
information container
named persistent set of information (3.11) retrievable from within a file, system or application storage
hierarchy
EXAMPLE Including sub-directory, information file (including model, document, table, schedule), or distinct
sub-set of an information file such as a chapter or section, layer or symbol.
Note 1 to entry: Persistent information exists over a timescale long enough for it to have to be managed, i.e. this
excludes transient information such as internet search results.
Note 2 to entry: Naming of an information container should be according to an agreed naming convention.
[SOURCE: EN ISO 19650-1:2018, 3.3.12 modified — cross reference has been adapted to be consistent
with internal numbering system. Note 1 has been removed and Notes 2 and 3 have been renumbered]
3.2
information delivery milestone
scheduled event for a predefined information exchange
[SOURCE: EN ISO 19650-2:2018, 3.1.3.2]
3.3
information exchange, verb
act of satisfying an information requirement or part thereof
[SOURCE: EN ISO 19650-1:2018, 3.3.7 modified — cross reference related to “information requirement”
has been removed]
3.4
information model
set of structured and unstructured information containers (3.1)
[SOURCE: EN ISO 19650-1:2018, 3.3.8 modified — cross reference has been adapted to be consistent
with internal numbering system]
3.5
level of information need
framework which defines the extent and granularity of information (3.11)
Note 1 to entry: One purpose of defining the level of information need is to prevent delivery of too much
information.
[SOURCE: EN ISO 19650-1:2018, 3.3.16 modified — cross reference has been adapted to be consistent
with internal numbering system]
3.6
verification
confirmation, through the provision of objective evidence, that specified requirements have been
fulfilled
[SOURCE: EN ISO 9000:2015, 3.8.12 modified — Notes 1 to 3 and cross references have been removed]
6

---------------------- Page: 8 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
3.7
validation
confirmation, through the provision of objective evidence, that the requirements for a specific intended
use or application have been fulfilled
[SOURCE: EN ISO 9000:2015, 3.8.13 modified — Notes 1 to 3 and cross references have been removed]
3.8
breakdown structure
decomposition of a defined scope into progressive levels
[SOURCE: ISO 21511:2018, 3.13 modified — “work” has been deleted in the term, “scope of the project
or programme” replaced with “scope”, “progressively lower levels consisting of elements of work”
replaced with “progressive levels”]
3.9
object
any part of the perceivable or conceivable world
[SOURCE: ISO 12006-2:2015, 3.1.1 modified — Note 1 has been removed]
3.10
geometry
information regarding shape and location of an object
[SOURCE: ISO/IEC 13249-3:2016, 3.1.2.27 modified — “information regarding” has been added,
“geographic location” replaced with “location”, “feature” replaced with “object”]
3.11
information
meaningful data
[SOURCE: EN ISO 9000:2015, 3.8.2 modified — cross reference has been removed]
3.12
geometrical information
description of detail and extent of information that can be expressed using shape, size, dimension, and
location
3.13
alphanumerical information
description of detail and extent of information that can be expressed using characters, digits and
symbols or tokens such as mathematical symbols and punctuation marks
3.14
documentation
collection of documents related to a given subject
[SOURCE: EN 62023:2012, 3.2.3 modified — Notes to entry 1 to 4 deleted]
7

---------------------- Page: 9 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
4 General
To support information exchange, level of information need should be used.
The level of information need describes the granularity of information exchanged in terms of
geometrical information, alphanumerical information and documentation. Different purposes have
their own needs of geometrical information, alphanumerical information and documentation.
The level of information need should be used to discuss and agree on the information delivery between
two or more actors.
The level of information need describes information requirements that can be human and machine
interpretable.
5 Framework to specify the level of information need
5.1 General
To specify the level of information need and how information is going to be delivered the following
useful prerequisites shall be considered:
— purposes for the use of the information to be delivered;
— information delivery milestones for the delivery of the information;
— actors who are going to request and actors who are going to deliver the information;
— objects organized in one or more breakdown structures.
The specification of level of information need is informed by but does not include the listed
prerequisites.
See Annex A for more information related to the relationships between EN ISO 29481-1 and level of
information need.
5.2 Consider the purposes
When the level of information need is specified, the purposes for information delivery shall be
considered.
The purposes should be specified to clarify why the information is needed. The level of information
need should be used for the purposes it has been required for.
The level of information need does not specify the purposes.
To achieve the same purpose, the geometrical information, alphanumerical information and
documentation can vary for different objects.
EXAMPLE 1 To perform an accessibility analysis, requirements such as the clear opening width of a door, its
location, the position and shape of the handle are needed. Other properties, such as the name of the manufacturer
and the acquisition cost, are not relevant to fulfil the purpose. On the other hand, for cost analysis purpose, the
acquisition cost of a door is needed, but the appearance of the handle is not relevant. For rendering purpose, the
geometrical appearance of a door is relevant, while the name of the manufacturer and the acquisition cost are not.
During an information delivery milestone, the same level of information need required for an object can
be used for different purposes.
EXAMPLE 2 In concept design, the same geometry and information of a block can be used for clash detection
and quantity take off.
8

---------------------- Page: 10 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
In some cases, the purpose should not be explicit to all actors (e.g. for security reasons). In those cases,
the purpose should be considered as “not disclosed” and only authorized actors should be informed.
EXAMPLE 3 The purposes can be extracted from organizational information requirements, project information
requirements and asset information requirements as described in EN ISO 19650-1:2018 5.2, 5.3, 5.4 and
EN ISO 19650-2:2018, 5.1.2.
5.3 Consider the information delivery milestones
When the level of information need is specified, information delivery milestones shall be considered.
The information delivery milestones should be specified to clarify when the information is needed.
The level of information need does not specify the information delivery milestones.
At the same information delivery milestone, the geometrical information, alphanumerical information
and documentation can vary for different objects.
EXAMPLE 1 To do accessibility analysis, usually the same level of information need is required at different
milestones.
EXAMPLE 2 To do energy analysis, different level of information need is required at different milestones.
5.4 Consider the actors
When the level of information need is specified, actors who require and deliver the information shall be
considered.
The level of information need does not specify the actor.
EXAMPLE 1 The same level of information need can be required by different actors at the same milestone to
fulfil different purposes.
EXAMPLE 2 Different level of information need can be required by different actors at the same milestone to
fulfil the same purpose.
NOTE 1 At different milestones, e.g. especially in the early phase, the actor responsible of delivering specified
level of information need might not be specified.
EXAMPLE 3 A client might ask for a specific level of information need for an object at an agreed information
delivery milestone without specifying who needs to deliver it. In this case the supply chain is free to assign
responsibilities as preferred.
NOTE 2 Different actors can be responsible for different level of information need at the same information
delivery milestone to fulfil the same purpose.
NOTE 3 For design purposes, at an agreed information delivery milestone, a wall in a project can be made up of
a structural element, architectural cladding and an air duct penetration with an air duct passing through the
penetration. Mechanical, electrical and plumbing engineers are responsible for providing reliable information
concerning the sizing of the duct and associated desired penetration sizing so that the structural and architectural
teams can continue their work to respectively validate the wall structure and cladding design.
5.5 Consider the objects within a breakdown structure
When the level of information need is specified, the objects within a breakdown structure for the
information delivery shall be considered.
The level of information need does not specify the objects within a breakdown structure.
9

---------------------- Page: 11 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
To be able to specify the level of information need, one or more objects within a breakdown structure
should be specified, identifying the semantic, functional and/or spatial decomposition of the project
into objects (e.g. construction elements and spaces are identified).
NOTE 1 Based on the purpose, the level of information need can be related to:
1) Construction results (spaces, construction complexes, construction entities and construction
elements);
2) Construction information (information model, building model, specification, documentation, diagram).
NOTE 2 Breakdown structures can follow a classification system, systems engineering principles or a
federation strategy.
NOTE 3 Different purposes can require different breakdown structures and derived decompositions.
EXAMPLE 1 To fulfil the purpose of cost estimation during the construction phase, a breakdown structure can
be different from a breakdown structure required for scheduling.
6 Definition of level of information need and its subdivision
6.1 General
The level of information need is the framework which defines the extent and granularity of information
to be exchanged. In accordance with this standard the level of information need should be described by
different concepts: geometrical information, alphanumerical information and documentation.
The level of information need can be answered by a combination of geometrical information,
alphanumerical information and/or documentation (see Annex B).
Information contained within documentation, geometrical information and alphanumerical information
can overlap and/or be contradictory, which can create consistency problems within the information
model. A clear hierarchy of the information provided within different information containers should
then be established.
Level of information need can either be predefined or can be defined for a particular information
delivery.
NOTE 1 A predefined level of information need can be included in regulations, standards, plans of work,
recommendations or specific project requirements; while other level of information need can be project specific.
If an aspect of level of information need is not relevant, ‘not applicable’ can be used.
EXAMPLE 1 For building permission purpose during the briefing, the geometrical information and
alphanumerical information can be ‘not applicable’ if only documentation is required.
The level of information need identifies the wanted presence of geometrical information,
alphanumerical information and/or documentation to address a specific purpose at a specified
information delivery milestone or agreed date.
The aspects of level of information need for all identified objects at specific information delivery
milestones should be combined to ensure that all identified purposes are met. This implies that
geometrical information, alphanumerical information or documentation to be delivered for certain
objects can be higher than what is strictly required for one particular identified purpose, because it is
required by another identified purpose at the same information delivery milestone.
The status, tolerance, accuracy and reliability associated to the aspects of level of information need shall
be considered to be managed through metadata.
10

---------------------- Page: 12 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
NOTE 2 Metadata are initially indicated by its author and then amended by the following approval and
authorization processes. ISO 19650-1 describes the use of metadata of information containers. In this document
the use of metadata is related to the specified geometrical information, alphanumerical information and/or
documentation associated to objects.
6.2 Geometrical information
6.2.1 General
To specify the geometrical information of an object or a set of objects, the following independent
aspects should be specified:
— Detail;
— Dimensionality;
— Location;
— Appearance;
— Parametric behaviour.
NOTE 1 Figure 1 to Figure 7 illustrate the existence of the variation in a continuum within one aspect.
NOTE 2 Geometrical information contains several aspects from current different industry practices elaborating
upon existing terms such as level of detail and level of geometry.
6.2.2 Detail
Detail as an aspect of geometrical information describes the complexity of the object geometry
compared to the real-world object. This is a continuum ranging from simplified to detailed.
More refined geometric representations can contain more features, and/or be more decomposed,
thereby being a better approximation of the shape of the real-world object.
EXAMPLE 1 In a project, the detail of the door can be different, depending on the required purpose and/or
information delivery milestones. In early design, the door can be represented as a hole in the wall to support
structural analysis (A) or with a simplified box representing the door panel for asset management during
operation (B). Higher detail adds the different components, such as the threshold and casing for clash detection
(C), or even the door handle and glazing for visualization (D) (Figure 1).

Figure 1 — Example of the concept of “continuum” associated to the detail of a door
11

---------------------- Page: 13 ----------------------
SIST EN 17412-1:2021
EN 17412-1:2020 (E)
EXAMPLE 2 For facility management purposes the detail of a boiler can be simplified and reduced to a box
including the volume of the operational space.
EXAMPLE 3 For clash detection purpose the detail of a boiler can be simplified and reduced to its outer shell.
EXAMPLE 4 For visualization purpose the detail of a boiler can use the detailed geometry from the
manufacturer.
EXAMPLE 5 For 2D drawing production the detail of a door can be different based on the information delivery
mi
...

SLOVENSKI STANDARD
oSIST prEN 17412:2019
01-september-2019
Informacijsko modeliranje gradenj - Raven informacijskih potreb - Pojmi in načela
Building Information Modelling - Level of Information Need - Concepts and principles
Modélisation des Informations pour la Construction (BIM) - Niveau d’Information Requis -
Concepts et Principes
Ta slovenski standard je istoveten z: prEN 17412
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 17412:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
oSIST prEN 17412:2019

---------------------- Page: 2 ----------------------
oSIST prEN 17412:2019


DRAFT
EUROPEAN STANDARD
prEN 17412
NORME EUROPÉENNE

EUROPÄISCHE NORM

June 2019
ICS 35.240.67
English Version

Building Information Modelling - Level of Information
Need - Concepts and principles
Modélisation des Informations pour la Construction Modélisation des Informations pour la Construction
(BIM) - Niveau d'Information Requis - Concepts et (BIM) - Niveau d'Information Requis - Concepts et
Principes Principes
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 442.

If this draft becomes a European Standard, 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.

This draft European Standard was established by CEN 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and United Kingdom.

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.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.


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

---------------------- Page: 3 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 General . 8
5 Framework to specify the level of information need . 8
5.1 General . 8
5.2 Identify the purposes . 9
5.3 Identify the information delivery milestones . 9
5.4 Identify the actors . 9
5.5 Identify the objects within a breakdown structure . 10
6 Definition of level of information need and its subdivision . 10
6.1 General . 10
6.2 Level of geometry . 12
6.3 Level of information . 16
6.4 Documentation . 17
7 The role of verification and validation . 18
Annex A (informative) Overview of the main concepts related to information exchange . 19
Annex B (informative) Example of method to specify level of information need . 20
Bibliography . 24

2

---------------------- Page: 4 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019
European foreword
This document (prEN 17412:2019) has been prepared by Technical Committee CEN/TC 442 “Building
Information Modelling (BIM)”, the secretariat of which is held by SN.
This document is currently submitted to the CEN Enquiry.
3

---------------------- Page: 5 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
Introduction
This document sets out the concepts and principles for defining the level of information need and
information deliveries being part of the information exchange processes during the life cycle of built
assets when using Building Information Modelling (BIM). Those concepts and principles can deliver
clear benefits to all participants in the various life cycle phases of built assets as they provide a common
understanding on the right level of information needed at a certain time preventing both a costly
overproduction of information as well as a risky underproduction. Information exchange ensures the
right information to be delivered for the agreed purpose to facilitate verification and validation
processes.
There is a need that these concepts and principles are described in a common and comparable way to
allow services related to Building Information Modelling to be procured and offered on a European
scale. The need has arisen by the fact that there are several conflicting terms, concepts and usages in
place, both internationally and across Europe, that hinder the objective of having a common
understanding and practise in describing the level of information need for a common European market.
This document applies to the information management during the whole life cycle of a built asset,
including strategic planning, initial design, engineering, development, documentation and construction,
day-to-day operation, maintenance, refurbishment, repair and end-of-life.
The information exchange, as well as related topics, such as the exchange information requirement, and
the information delivery are defined and explained in context of two related standards:
— EN ISO 19650-1, Organization of information about construction works — Information management
using building information modelling — Part 1: Concepts and principles; and
— EN ISO 29481-1, Building information models – Information delivery manual – Part 1: Methodology
and format.
4

---------------------- Page: 6 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019
1 Scope
This document specifies concepts and principles to establish a methodology for specifying level of
information need and information deliveries in a consistent way when using Building Information
Modelling (BIM).
This document specifies the characteristics of different levels used for defining the detail and extent of
information required to be exchanged and delivered throughout the life cycle of built assets. It gives
guidelines for principles required to specify information needs.
The concepts and principles in this document can be applied for a general information exchange and
whilst in progress, for a generally agreed way of information exchange between parties in a
collaborative work process, as well as for a contractually specified information delivery.
The level of information need provides methods for describing information to be exchanged according
to exchange information requirements. The exchange information requirements specify the wanted
information exchange. The result of this process is an information delivery.
The concepts and principles contained in this document are applicable to all those involved in the asset
life cycle. This includes, but is not limited to, the asset owner/operator, the project client, the asset
manager, the design team, the construction supply chain, the equipment manufacturer, the system
specialist, the regulator, and the end-user.
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)
prEN ISO 23386:2019, Building information modelling and other digital processes used in construction —
Methodology to describe, author and maintain properties in interconnected dictionaries
prEN ISO 23387, Building Information Modelling (BIM) - Data templates for construction objects used in
the life cycle of any built asset - Concepts and principles (ISO 23387)
ISO 6707-1, Buildings and civil engineering works — Vocabulary — Part 1: General terms
3 Terms and definitions
For the purposes of this document, the terms and definitions given in EN ISO 29481-1, ISO 6707-1 and
following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
5

---------------------- Page: 7 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
3.1
information container
named persistent set of information retrievable from within a file, system or application storage
hierarchy
EXAMPLE Including sub-directory, information file (including model, document, table, schedule), or distinct
sub-set of an information file such as a chapter or section, layer or symbol.
Note 1 to entry: Structured information containers include geometrical models, schedules and databases.
Unstructured information containers include documentation, video clips and sound recordings.
Note 2 to entry: Persistent information exists over a timescale long enough for it to have to be managed, i.e. this
excludes transient information such as internet search results.
Note 3 to entry: Naming of an information container should be according to an agreed naming convention.
[SOURCE: EN ISO 19650-1:2018, 3.3.12 modified – reference (3.3.1) to (3.11) to be consistent with
internal numbering system]
3.2
information delivery milestone
scheduled event for a predefined information exchange
[SOURCE: EN ISO 19650-2:2018, 3.1.3.2]
3.3
information exchange, verb
act of satisfying an information requirement or part thereof
[SOURCE: EN ISO 19650-1:2018, 3.3.7 modified – cross reference (3.3.2) related to “information
requirement” has been removed]
3.4
information model
set of structured and unstructured information containers
[SOURCE: EN ISO 19650-1:2018, 3.3.8 modified – cross reference (3.3.2) related to “information
requirement” has been removed]
3.5
level of information need
description of the information deliverable to fulfil a specific purpose for which the information is
required
Note 1 to entry: One purpose of defining the level of information need is to prevent delivery of too much
information
[SOURCE: EN ISO 19650-1:2018, 3.3.16 modified – definition has been changed, same NOTE 1 to entry]
3.6
verification
confirmation, through the provision of objective evidence, that specified requirements have been
fulfilled
[SOURCE: EN ISO 9000:2015, 3.8.12]
6

---------------------- Page: 8 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019
3.7
validation
confirmation, through the provision of objective evidence, that the requirements for a specific intended
use or application have been fulfilled
[SOURCE: EN ISO 9000:2015, 3.8.13]
3.8
breakdown structure
decomposition of a defined scope into progressive levels
[SOURCE: ISO 21511:2018, 3.13 modified – deletion of “work” from the title and “of the project or
programme”, “lower” and “consisting of elements of work” from the definition]
3.9
object
any part of the perceivable or conceivable world
[SOURCE: ISO 12006-2:2015, 3.1.1]
3.10
geometry
information that can be perceived from shape, position, scale, orientation and reflection of
representation of an object
Note 1 to entry: An object can be geometrically described through form, size, dimensions, and location – in
space or to other objects.
EXAMPLE 1 Information can be derived from geometry, e.g. the dimensions of an object, the distance between
interrelated objects etc.
EXAMPLE 2 Documentation can be derived from geometry, e.g. views extracted from an information model
and recorded as an external document.
EXAMPLE 3 Geometry can be represented by square, cube, cylinder, ball, cone, triangle, curve, straight line,
object placed within an object, etc.
EXAMPLE 4 Geometry can be used for 3-dimensional (3D) consistency to visualize, generate views, quantity
take off, clash detection, etc.
3.11
information
meaningful data
Note 1 to entry: Information can be expressed using characters, digits and symbols or tokens such as
mathematical symbols and punctuation marks.
EXAMPLE 1 Information can be contained within a brief, a budget, a specification, an energy calculation, a
product data sheet, a technical report, an operation and maintenance manual, etc.
EXAMPLE 2 Information can be used to create geometrical form, shape and size.
EXAMPLE 3 Information can be used to create documents and documentation.
EXAMPLE 4 Information can be used to filter, sort, check, compare and analyse objects.
[SOURCE: ISO 22263:2008, 2.6 modified – NOTE 1 to entry and EXAMPLES added]
7

---------------------- Page: 9 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
3.12
level of geometry
LOG
description of detail and extent of geometry
Note 1 to entry: Deprecated term: level of detail
3.13
level of information
LOI
description of detail and extent of information
3.14
document
fixed and structured amount of information that can be managed and interchanged as a unit between
users and systems
[SOURCE: EN 82045-1:2001, 3.2.3]
3.15
documentation
DOC
collection of documents related to a given subject
[SOURCE: EN 62023:2012, 3.2.3 modified – NOTES to entry 1 to 4 deleted, “DOC” added]
4 General
To support information exchange, level of information need should be used.
The level of information need describes the granularity of information exchanged in terms of geometry,
information and documentation. Different purposes, have their own needs of geometry, information
and documentation.
The level of information need should be used to discuss and agree on the information delivery between
two or more actors.
5 Framework to specify the level of information need
5.1 General
To specify the level of information need and how information is going to be delivered, the following
useful prerequisites should be identified:
— purposes for the use of the information to be delivered;
— information delivery milestones for the delivery of the information;
— actors who are going to request and deliver the information;
— objects in one or more breakdown structures.
The definition of level of information need is independent from the listed prerequisites.
See Annex A for more information related to the relationships between EN ISO 29481-1 and level of
information need.
8

---------------------- Page: 10 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019
5.2 Identify the purposes
When the level of information need is specified, the purposes for information delivery shall be
identified.
The purposes should be specified to clarify why the information is needed. The level of information
need should be used only for the purposes it has been required for.
The level of information need does not specify the purposes.
To achieve the same purpose, the geometry, information and documentation can vary for different
objects.
EXAMPLE 1 To perform an accessibility analysis, requirements such as the clear opening width of a door, its
location, the position and shape of the handle are needed. Other properties, such as the name of the manufacturer
and the acquisition cost, are not relevant to fulfil the purpose. On the other hand, for cost analysis purposes, the
acquisition cost of a door is needed, but the appearance of the handle is not relevant. For rendering purposes, the
geometrical appearance of a door is relevant, while the name of the manufacturer and the acquisition cost are not.
During an information delivery milestone, the same level of information need required for an object can
be used for different purposes.
EXAMPLE 2 In concept design, the same geometry and information of a block can be used for clash detection
and quantity take off.
NOTE In some cases, the purpose does not need to be explicit to all actors (e.g. for security reasons). In those
cases, the purpose will be considered as “not disclosed” and only authorized actors will be informed.
5.3 Identify the information delivery milestones
When the level of information need is specified, information delivery milestones shall be identified.
The information delivery milestones should be specified to clarify when the information is needed.
The level of information need does not specify the information delivery milestones.
At the same information delivery milestone, the geometry, information and documentation can vary for
different objects.
EXAMPLE 1 To do accessibility analysis, usually the same level of information need is required at different
milestones.
EXAMPLE 2 To do energy analysis, different level of information need is required at different milestones.
5.4 Identify the actors
When the level of information need is specified, actors who require and deliver the information shall be
identified.
The level of information need does not specify the actor.
EXAMPLE 1 The same level of information need can be required by different actors at the same milestone to
fulfil different purposes.
EXAMPLE 2 Different level of information need can be required by different actors at the same milestone to
fulfil the same purpose.
NOTE 1 At different milestones, e.g. especially in the early phase, the actor responsible of delivering specified
level of information is not always specified.
EXAMPLE 3 A client could ask for a specific level of information need for an object at an agreed information
delivery milestone without specifying who needs to deliver it. In this case, the supply chain is free to assign
responsibilities as preferred.
9

---------------------- Page: 11 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
NOTE 2 Different actors can be responsible for different level of information at the same information delivery
milestone to fulfil the same purpose.
NOTE 3 For design purposes, at an agreed information delivery milestone, a wall in a project can be made up of
a structural element, architectural cladding and an air duct penetration with an air duct passing through the
penetration. Mechanical, electrical and plumbing engineers are responsible for providing reliable information
concerning the sizing of the duct and associated desired penetration sizing so that the structural and architectural
teams can continue their work to respectively validate the wall structure and cladding design.
5.5 Identify the objects within a breakdown structure
When the level of information need is specified, the objects within a breakdown structure for the
information delivery shall be identified.
The level of information need does not specify the objects within a breakdown structure.
To be able to specify the level of information need, one or more objects within a breakdown structure
should be specified, identifying the semantic, functional and/or spatial decomposition of the project
into objects e.g. construction elements and spaces is identified.
NOTE 1 Based on the purpose, the level of information need can be related to:
1) Construction results (spaces, construction complexes, construction entities and construction
elements);
2) Construction information (information model, building model, specification, documentation, diagram).
NOTE 2 Breakdown structures can follow a classification system, systems engineering principles or a
federation strategy.
NOTE 3 Different purposes can require different breakdown structures and derived decompositions.
EXAMPLE To fulfil the purpose of cost estimation during the construction phase, a breakdown structure can
be different from a breakdown structure required for scheduling.
6 Definition of level of information need and its subdivision
6.1 General
The level of information need (LOIN) describes the extent and detail of information exchange in terms
of geometry, information and documentation. In accordance with this document, the level of
information need (LOIN) should be described by different concepts: level of geometry (LOG), level of
information (LOI) and documentation (DOC).
The level of information need can be answered by a combination of geometry, information and/or
documentation.
Level of information need can either be predefined or can be defined for a particular information
delivery.
NOTE 1 A predefined level of information need can be included in regulations, standards, plans of work,
recommendations or specific project requirements; while other level of information need can be project specific.
If an aspect of level of information need is not relevant, ‘not applicable’ can be used.
EXAMPLE For building permission purpose during the briefing, the level of geometry and level of
information can be ‘not applicable’ as only documentation is required.
The level of information need identifies the wanted presence of geometry, information and/or
documentation to address a specific purpose at a specified information delivery milestone or agreed
date.
10

---------------------- Page: 12 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019
Level of information need does not describe the status or reliability of the information. The status and
reliability of information about the information needed should follow the methodologies described in
prEN ISO 23386 and prEN ISO 23387-1.
NOTE 2 Metadata are initially indicated by its author and then amended by the following approval and
authorization processes. ISO 19650-1 describes the use of metadata of information containers. In this document,
the use of metadata are related to the specified geometry, information and/or documentation associated to
objects.
Figure 1 shows the level of information need framework and the relation with the prerequisites
illustrated in Clause 5.

Figure 1 — Level of information need framework (draft version)
11

---------------------- Page: 13 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
6.2 Level of geometry
To specify the level of geometry of an object or a set of objects, the following aspects should be
specified:
a) Detail: description of the complexity of the object geometry compared to the real-world object. This
is a continuum ranging from symbolic over simplified to detailed.
More refined geometric representations can contain more features, and/or be more decomposed,
thereby being a better approximation of the shape of the real-world object.
EXAMPLE 1 For facility management purposes, the detail of a boiler can be symbolic as a box including the
volume of the operational space.
EXAMPLE 2 For clash detection purposes, the detail of a boiler can be simplified and reduced to outer shell.
EXAMPLE 3 For visualization purposes, the detail of a boiler can use the detailed geometry from the
manufacturer.
EXAMPLE 4 For 2D drawing production, the detail of a door can be different based of the information delivery
milestone (see Figure 2).

Figure 2 — Example of symbolic (A), simplified (B) and detailed (C) graphical representation of a
wall for 2D drawing production purpose
EXAMPLE 5 For the same purposes at different information delivery milestones, the detail of a building can be
different (see Figure 3) as well as the one of a bed (see Figure 4).

Figure 3 — Example of symbolic (A), simplified (B) and detailed (C) graphical representation of a
building for 3D modelling to support master planning (A), early light analyses (B) and detail
light analyses (C)
12

---------------------- Page: 14 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019

Figure 4 — Example of symbolic (A), simplified (B) and detailed (C) graphical representation of a
bed for early space planning (A), early design (B) and detail design (C)
EXAMPLE 6 The same existing column can have different graphical representations at the same information
delivery milestone to support different purposes (see Figure 5).

Figure 5 — Example of detailed graphical representations of a column at the same information
delivery milestone for different purposes: (A) visualization, (B) degradation analysis
b) Dimensionality: number of spatial dimensions that characterize the object.
Dimensionality can be zero-dimensional - 0D (location point), one-dimensional - 1D (e.g. line, curve,
path), two-dimensional - 2D (e.g. surface, face) or three-dimensional - 3D (e.g. body, volume).
EXAMPLE 7 For quantity take off purposes, in a 3D environment the dimensionality of a pipe can be 1D to
extract pipe lengths.
EXAMPLE 8 For clash detection purposes, the dimensionality of a pipe can be 3D.
EXAMPLE 9 For the parcel management, the dimensionality of a road can be 2D also in a 3D environment.
13

---------------------- Page: 15 ----------------------
oSIST prEN 17412:2019
prEN 17412:2019 (E)
EXAMPLE 10 For 2D representation, the dimensionality of a bed can be 2D, for quantity take off it can be 3D at
the same information delivery milestone (see Figure 6).

Figure 6 — Example of dimensionality 2D (A) and 3D (B) of a bed at the same information
delivery milestone for different purposes: 2D representation (A) and quantity take off (B)
c) Location: description of the position and orientation of an object. Location can be absolute (e.g. geo-
location) or relative (e.g. in reference to another object or to a requirement).
EXAMPLE 11 Relative location can be e.g. linear alignment, grid, transformation of coordinate system or local
placement.
EXAMPLE 12 Relative location can be described in terms of semantic relationships with other objects, e.g. “is
part of” or “decomposes”.
d) Appearance: description of the visual representation of an object. This is a continuum ranging from
symbolic over simplified to realistic compared to the real-world.
More refined appearances can contain more shading attributes (e.g. diffuse colouring,
transparency, reflectance, emissivity), thereby being a better approximation of the visual
characteristic of the real-world object. Shading attributes can be expressed in many ways e.g. as
colours and/or texture maps (see Figure 7).
EXAMPLE 13 For communication purposes, the appearance of a plumbing pipe can be symbolic using red or
blue colours describing the water temperature.
EXAMPLE 14 For coordination purposes, the appearance of a plumbing pipe can be simplified using the colour
of the material.
EXAMPLE 15 For visualization purposes, the appearance of a plumbing pipe can be realistic using colours and
texture from the manufacturer.
14

---------------------- Page: 16 ----------------------
oSIST prEN 17412
...

Questions, Comments and Discussion

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