Standards Development

Scope

The scope of this guidance is the content of the EN ISO 19650-series, highlighting and describing the manner in which to use it – and not extending or contradicting the scope and content of the standard. Further this document revises the existing guideline-document and aims simply to provide minimum supporting text to achieve a basic understanding and ability to implement EN ISO 19650-series. In each country, each client, each team can use this guidance to provide the best response to information management in each project.

This document explains the terms and definitions, explains the concepts and principles and how to use them, and gives typical examples with clear explanations.

It should be noted that in this guidance, Information Management is considered as a part of the Project Management.

This guidance is intended to demonstrate how the standard works at European level, which is neutral, agnostic, and applicable to any of the following circumstances:

— the nature of contracts: e.g. public; private, alliances, global, partnership,

— the actors' functions: e.g. through the programming, design, construction phases, from small agencies, SMEs to large firms, large companies,

— the types of works: e.g. simple, complex, new, rehabilitated, housing, infrastructure.

Purpose

WI 442038 prCEN/TR 17439 rev is abandoned due to the proposed change of deliverable from TR to TS. This NWIP is a proposal for a CEN/TS covering the same scope as WI 442038.

The scope of this guidance is the content of the EN ISO 19650-series, highlighting and describing the way to use it – and not extending or contradicting the scope and content of the standard.

How to interpret KEY Concepts to clarify:

 Appointed/Appointing parties Differentiation of two parties having a formal appointment and two parties being information provider/receiver without any formal appointment. Differentiation of being at one hand an information provider and the other hand an information receiver.

The status of being an information provider or an information receiver depends on the roles and tasks (e.g. as an architect, sometimes I am an information provider and sometimes I am an Information receiver)

 Information delivery (vertical/horizontal)

 Hierarchy of information requirements:

From the Organizational Information Requirements (OIR), over the Project Information Requirements (PIR) and the Exchange Information Requirements (EIR) to the Project Information Model (PIM) and Asset Information Management (AIM) figure 2, EN ISO 19650-1)

 Common Data Environments different solutions, depending on the project size and contractual solution

 Relation of information management and project management, Information Management as support process to project management

 Scalability to small and medium projects

 Expanding the scope of the existing guideline-document towards the operational phase of projects according to EN ISO 19650-3

 Explaining security minded information management concepts as presented in EN ISO 19650-5

 Introducing quality of data as described in EN ISO 19650-4.

Open list to be completed if necessary (probably around interpretation/translation issues and elaboration of use cases)

How to implement

How to use the EN ISO 19650-series in an European context:

 with references to the examples special item for functions/roles

 Use cases to define depending on:

 Nature of projects

 Type of clients

 Size of projects

 Phase of projects (CAPEX/OPEX)

 Different kinds of delivery teams/functions

 Security requirements

 Schemas for each use case

 Stories for each use case

 Stories for the different phases/stages

 Stories for different security aspects

 Stories for each type of client

 Non-generic examples of possible processes (from initiation to handover) for each use case