SIST EN ISO 7817-1:2024

SLOVENSKI STANDARD
01-september-2024
Nadomešča:
SIST EN 17412-1:2021
Informacijsko modeliranje gradenj - Raven informacijskih potreb - 1. del: Pojmi in
načela (ISO 7817-1:2024)
Building Information Modelling - Level of Information Need - Part 1 Concepts and
principles (ISO 7817-1:2024)
Bauwerksinformationsmodellierung - Informationsbedarfstiefe - Teil 1: Konzepte und
Grundsätze (ISO 7817-1:2024)
Modélisation des informations de la construction (BIM) - Niveau du besoin d'information -
Concepts et principes (ISO 7817-1:2024)
Ta slovenski standard je istoveten z: EN ISO 7817-1:2024
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 7817-1
EUROPEAN STANDARD
NORME EUROPÉENNE
July 2024
EUROPÄISCHE NORM
ICS 35.240.67; 91.010.01 Supersedes EN 17412-1:2020
English Version
Building Information Modelling - Level of Information
Need - Part 1 Concepts and principles (ISO 7817-1:2024)
Modélisation des informations de la construction (BIM) Bauwerksinformationsmodellierung -
- Niveau du besoin d'information - Concepts et Informationsbedarfstiefe - Konzepte und Grundsätze
principes (ISO 7817-1:2024) (ISO 7817-1:2024)
This European Standard was approved by CEN on 18 June 2024.

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

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 7817-1:2024 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 7817-1:2024) has been prepared by Technical Committee ISO/TC 59 "Buildings
and civil engineering works" in collaboration with Technical Committee CEN/TC 442 “Building
Information Modelling (BIM)” the secretariat of which is held by SN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by January 2025, and conflicting national standards shall
be withdrawn at the latest by January 2025.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 17412-1:2020.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 7817-1:2024 has been approved by CEN as EN ISO 7817-1:2024 without any
modification.
International
Standard
ISO 7817-1
First edition
Building information modelling —
2024-06
Level of information need —
Part 1:
Concepts and principles
Modélisation des informations de la construction (BIM) — Niveau
du besoin d’information —
Partie 1: Concepts et principes
Reference number
ISO 7817-1:2024(en) © ISO 2024

ISO 7817-1:2024(en)
© ISO 2024
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
ISO 7817-1:2024(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 General . 3
5 Framework to specify the level of information need . 3
5.1 General .3
5.2 Consider the purposes .4
5.3 Consider the information delivery milestones .4
5.4 Consider the actors .4
5.5 Consider the objects within a breakdown structure .5
6 Definition of level of information need and its subdivision . 5
6.1 General .5
6.2 Geometrical information .6
6.2.1 General .6
6.2.2 Detail .6
6.2.3 Dimensionality .9
6.2.4 Location .10
6.2.5 Appearance .10
6.2.6 Parametric behaviour .11
6.2.7 Relationships of aspects of geometrical information and prerequisites . 12
6.3 Alphanumerical information . 12
6.3.1 General . 12
6.3.2 Identification . 13
6.3.3 Information content . 13
6.4 Documentation . 13
6.5 Relationship diagram on level of information need .14
7 Verification and validation . 14
Annex A (informative) Overview of the main concepts related to information exchange .16
Annex B (informative) Examples of methods to specify level of information need .18
Bibliography .23

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

iv
ISO 7817-1:2024(en)
Introduction
This document sets out the concepts and principles for defining the level of information need and information
deliveries which form part of the information exchange processes during the life cycle of built assets when
using building information modelling (BIM). These 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 required information
to be delivered at the agreed time 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 global scale. The need
has arisen by the fact that there are several conflicting terms, concepts and usages in place, internationally,
that hinder the objective of having a common understanding and practise in describing the level of
information need. 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.
These include, but are 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 ISO 19650-1 and ISO 29481-1.

v
International Standard ISO 7817-1:2024(en)
Building information modelling — Level of information need —
Part 1:
Concepts and principles
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 while
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.
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.
ISO 29481-1, Building information models — Information delivery manual — Part 1: Methodology and format
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 ISO 29481-1, ISO 6707-1 and the
following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
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.

ISO 7817-1:2024(en)
Note 2 to entry: Naming of an information container should be according to an agreed naming convention.
[SOURCE: ISO 19650-1:2018, 3.3.12, modified — Note 1 to entry has been removed; subsequent notes to
entry have been renumbered.]
3.2
information delivery milestone
scheduled event for a predefined information exchange (3.3)
[SOURCE: ISO 19650-2:2018, 3.1.3.2]
3.3
information exchange, verb
act of satisfying an information (3.11) requirement or part thereof
[SOURCE: ISO 19650-1:2018, 3.3.7]
3.4
information model
set of structured and unstructured information containers (3.1)
[SOURCE: ISO 19650-1:2018, 3.3.8]
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: ISO 19650-1:2018, 3.3.16]
3.6
verification
confirmation, through the provision of objective evidence, that specified requirements have been fulfilled
[SOURCE: ISO 9000:2015, 3.8.12, modified — Notes 1 to 3 to entry have been removed.]
3.7
validation
confirmation, through the provision of objective evidence, that the requirements for a specific intended use
or application have been fulfilled
[SOURCE: ISO 9000:2015, 3.8.13, modified — Notes 1 to 3 to entry have been removed.]
3.8
breakdown structure
decomposition of a defined scope into progressive levels
[SOURCE: ISO 21511:2018, 3.13 modified — The word “work” has been deleted from the term; “scope of the
project and programme” has been replaced with “scope”; “progressively lower levels consisting of elements
of work” has been 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 to entry has been removed.]

ISO 7817-1:2024(en)
3.10
geometry
shape, size and location of an object (3.9)
[SOURCE: ISO/IEC 13249-3:2016, 3.1.2.27, modified — The word “size” has been added; “geographic location”
has been replaced with “location”; “feature” has been replaced with “object”.]
3.11
information
meaningful data
[SOURCE: ISO 9000:2015, 3.8.2]
3.12
geometrical information
information (3.11) expressed using geometry (3.10)
3.13
alphanumerical information
information (3.11) expressed using characters, digits and symbols or tokens
EXAMPLE Mathematical symbols and punctuation marks are such tokens.
3.14
documentation
collection of documents related to a given subject
[SOURCE: IEC 82045-1:2001, 3.2.4, modified — Notes 1 to 4 to entry have been removed.]
3.15
information deliverable
information container (3.1) used to fulfil an appointment
4 General
To support information exchange, level of information need should be used.
The level of information need provides a framework for describing 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 exchange between two
or more actors.
The level of information need describes information requirements that can be human-readable and machine-
interpretable.
5 Framework to specify the level of information need
5.1 General
In specifying the level of information need and how information is going to be delivered, the following
prerequisites shall be considered:
— purposes of the information to be delivered;
— information delivery milestones for the delivery of the information;
— actors who are either information receivers or information providers of the information;
— objects organized in one or more breakdown structures.

ISO 7817-1:2024(en)
The specification of level of information need is informed by but does not include the listed prerequisites
(see also Figure 8 in 6.5 for the relationship between the prerequisites and the level of information need).
See Annex A for more information related to the conceptual relationships between this document,
ISO 19650-1 and ISO 29481-1.
5.2 Consider the purposes
In specifying the level of information need, 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, properties 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.
At 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.
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.
NOTE The purposes can be extracted from organizational information requirements, project information
requirements and asset information requirements as described in ISO 19650-1:2018. 5.2, 5.3, 5.4 and
ISO 19650-2:2018, 5.1.2.
5.3 Consider the information delivery milestones
In specifying the level of information need, 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
In specifying the level of information need, actors who receive and provide the information shall be
considered.
The level of information need does not specify the actor (actors).
NOTE 1 The same level of information need can be required by different actors at the same milestone to fulfil
different purposes.
ISO 7817-1:2024(en)
NOTE 2 Different level of information need can be required by different actors at the same milestone to fulfil the
same purpose.
NOTE 3 At different milestones, e.g. especially in the early phase, it is possible that the actor responsible for
delivering specified level of information need is not specified.
EXAMPLE 1 A client can 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 4 Different actors can be responsible for different level of information need at the same information delivery
milestone to fulfil the same purpose.
EXAMPLE 2 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
In specifying the level of information need, 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.
To be able to specify the level of information need, the considered objects within a breakdown structure
should be specified, identifying the semantic, functional and/or spatial
...