91.010.01 - Construction industry in general
ICS 91.010.01 Details
Construction industry in general
Bauwesen im allgemeinen
Industrie de la construction en général
Gradbeništvo na splošno
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 91.010.01 - Construction industry in general
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems.
This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary.
In scope of this document are:
— processes for the provision and exchange of product catalogues;
— rules for the geometrical representation of products;
— representation of products, product classes, ports, in/outlets, components and accessories by using IFC;
— representation of properties in IFC and the use of IFC constraints for the representation of product variants;
— representation of parametric geometry and the generation of IFC geometries for selected variants;
— calculation of article number.
The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system.
The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools.
Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard98 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains:
— subject kinds that allow to distinguish:
— product subjects representing products in product catalogues;
— catalogue subjects comprising meta data of product catalogues;
— various kinds of blocks that collect properties of complex product features, including ports and in/outlets;
— relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock;
— property kinds to distinguish between:
— static properties describing products by providing property values in product catalogues;
— dynamic properties that describe the behaviour of products;
— external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties.
This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level.
Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements.
This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the concept of data templates developed to enable machine interpretability based on a standardized data structure, carrying the alphanumerical information for any object used in the life cycle of assets.
This document provides a description of how data templates are implemented following ISO 12006-3.
This document provides a methodology to create and maintain data templates in data dictionary.
This document provides guidance for linking between data templates and classification systems within data dictionaries based on ISO 12006-3.
This document provides an XML Schema Definition (XSD) representing an implementation of the ISO 23387 and ISO 12006-3 data models.
It is not within the scope of this document to provide the content of any data templates.
- Standard43 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems.
This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary.
In scope of this document are:
— processes for the provision and exchange of product catalogues;
— rules for the geometrical representation of products;
— representation of products, product classes, ports, in/outlets, components and accessories by using IFC;
— representation of properties in IFC and the use of IFC constraints for the representation of product variants;
— representation of parametric geometry and the generation of IFC geometries for selected variants;
— calculation of article number.
The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system.
The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools.
Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard98 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains:
— subject kinds that allow to distinguish:
— product subjects representing products in product catalogues;
— catalogue subjects comprising meta data of product catalogues;
— various kinds of blocks that collect properties of complex product features, including ports and in/outlets;
— relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock;
— property kinds to distinguish between:
— static properties describing products by providing property values in product catalogues;
— dynamic properties that describe the behaviour of products;
— external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties.
This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level.
Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements.
This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard34 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes how product catalogue data for building services products is exchanged by means of ISO 16739-1 (Industry Foundation Classes, IFC) and EN 17549-2 from manufacturers to designers of building services systems. This document specifies how the product catalogue structures and content are set up using the definitions stored in a data dictionary. In scope of this document are: — processes for the provision and exchange of product catalogues; — rules for the geometrical representation of products; — representation of products, product classes, ports, in/outlets, components and accessories by using IFC; — representation of properties in IFC and the use of IFC constraints for the representation of product variants; — representation of parametric geometry and the generation of IFC geometries for selected variants; — calculation of article number. The resulting product catalogue can be used by designers to select the desired products and integrate them into their model of the building services system. The expected audience of this document are software providers for the built environment sector and professionals working in the sector who create product catalogues or use product catalogues by means of software tools. Not in scope of this document is the representation of properties in data dictionaries. The use of data dictionaries is described in ISO 16757-4.
- Standard89 pagesEnglish languagesale 15% off
- Standard96 pagesFrench languagesale 15% off
This document specifies requirements for data dictionaries that are used by product catalogues for building services to provide the semantics of their definitions and data modelling. For this purpose, it defines an overall model that contains: — subject kinds that allow to distinguish: — product subjects representing products in product catalogues; — catalogue subjects comprising meta data of product catalogues; — various kinds of blocks that collect properties of complex product features, including ports and in/outlets; — relationship types that allow to distinguish between different kinds of relationships like isSubtypeOf, hasPart, or hasBlock; — property kinds to distinguish between: — static properties describing products by providing property values in product catalogues; — dynamic properties that describe the behaviour of products; — external properties that represent external conditions that influence the behaviour of the product by influencing the values of dynamic properties. This document also describes a mapping of the overall model to the data dictionary model of ISO 12006-3 by introducing a dictionary meta level. Finally, to overcome deficiencies of the standards underlying ISO 16757-5 in capturing all aspects of product catalogues, this document provides some rules and recommendations for required data dictionary elements. This document does not describe how product catalogues have to be organized, and it does not describe any formats for the exchange of product catalogues. Product catalogues are described in ISO 16757-5.
- Standard25 pagesEnglish languagesale 15% off
- Standard26 pagesFrench languagesale 15% off
This document provides the concept of data templates developed to enable machine interpretability based on a standardized data structure, carrying the alphanumerical information for any object used in the life cycle of assets.
This document provides a description of how data templates are implemented following ISO 12006-3.
This document provides a methodology to create and maintain data templates in data dictionary.
This document provides guidance for linking between data templates and classification systems within data dictionaries based on ISO 12006-3.
This document provides an XML Schema Definition (XSD) representing an implementation of the ISO 23387 and ISO 12006-3 data models.
It is not within the scope of this document to provide the content of any data templates.
- Standard43 pagesEnglish languagesale 10% offe-Library read for1 day
The scope of this document is primarily focused on EN ISO 19650-1, EN ISO 19650-2, EN ISO 19650-3, EN ISO 19650-4 and EN ISO 19650-5. In the text these are referred to collectively as "the EN ISO 19650 series". This document highlights and describes the way to use the standards, without extending or contradicting the scope and content. This document aims to provide supporting text to achieve a basic understanding and ability to implement the EN ISO 19650 series. In each country, each client and each delivery team can use this document to provide the best response to information management in each project or asset management activity.
This document explains the terms and definitions, concepts and principles and how to use them, and gives practical examples with clear explanations.
It should be noted that in this document, information management is considered as a part of project management, asset management and security management.
This document is intended to demonstrate how the EN ISO 19650 series works at the European level in a neutral way that is applicable to any project or asset regardless of:
- the nature of contracts, e.g. public, private, alliances, global, partnership;
- the actors' functions, e.g. through the programming, design, construction phases, regardless of organization size including SMEs;
- the diversity of tendering processes and commissioning practices, e.g. one main contractor (lead appointed party) on one client (as appointing party) vs. one client and multiple contracts with individual appointed parties;
- the types of works, e.g. new, refurbished, housing, infrastructure;
- the complexity of the project, asset, or activities.
- Technical specification77 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies concepts and principles for classifying, sharing and delivering health and safety information collaboratively, to secure the economic, environmental and social benefits.
This document:
a) specifies requirements for the collaborative sharing of structured health and safety information throughout project and asset life cycles;
b) supports the digitization of structured health and safety information in project and asset life cycles progressively from the outset;
c) provides specification on how health and safety information is shared for use throughout project and asset life cycle;
d) sets out a health and safety information cycle framework for the identification, use, sharing and generalization of health and safety information through information management processes.
This document is applicable to individuals and organizations that contribute to and influence the procurement, design, construction, use (including maintenance) and end-of-life of building and infrastructure assets.
The principles and requirements of this document can be applied equally to delivery or in-use phases not using BIM.
- Standard33 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies concepts and principles for classifying, sharing and delivering health and safety information collaboratively, to secure the economic, environmental and social benefits.
This document:
a) specifies requirements for the collaborative sharing of structured health and safety information throughout project and asset life cycles;
b) supports the digitization of structured health and safety information in project and asset life cycles progressively from the outset;
c) provides specification on how health and safety information is shared for use throughout project and asset life cycle;
d) sets out a health and safety information cycle framework for the identification, use, sharing and generalization of health and safety information through information management processes.
This document is applicable to individuals and organizations that contribute to and influence the procurement, design, construction, use (including maintenance) and end-of-life of building and infrastructure assets.
The principles and requirements of this document can be applied equally to delivery or in-use phases not using BIM.
- Standard33 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies concepts and principles for classifying, sharing and delivering health and safety information collaboratively, to secure the economic, environmental and social benefits. This document: a) specifies requirements for the collaborative sharing of structured health and safety information throughout project and asset life cycles; b) supports the digitization of structured health and safety information in project and asset life cycles progressively from the outset; c) provides specification on how health and safety information is shared for use throughout project and asset life cycle; d) sets out a health and safety information cycle framework for the identification, use, sharing and generalization of health and safety information through information management processes. This document is applicable to individuals and organizations that contribute to and influence the procurement, design, construction, use (including maintenance) and end-of-life of building and infrastructure assets. The principles and requirements of this document can be applied equally to delivery or in-use phases not using BIM.
- Standard24 pagesEnglish languagesale 15% off
- Standard26 pagesFrench languagesale 15% off
This document provides an index of typical existing information on the concept, assessment and strategy for seismic resilience of buildings and civil engineering works.
- Technical report13 pagesEnglish languagesale 15% off
The scope of this document is primarily focused on EN ISO 19650-1, EN ISO 19650-2, EN ISO 19650-3, EN ISO 19650-4 and EN ISO 19650-5. In the text these are referred to collectively as "the EN ISO 19650 series". This document highlights and describes the way to use the standards, without extending or contradicting the scope and content. This document aims to provide supporting text to achieve a basic understanding and ability to implement the EN ISO 19650 series. In each country, each client and each delivery team can use this document to provide the best response to information management in each project or asset management activity.
This document explains the terms and definitions, concepts and principles and how to use them, and gives practical examples with clear explanations.
It should be noted that in this document, information management is considered as a part of project management, asset management and security management.
This document is intended to demonstrate how the EN ISO 19650 series works at the European level in a neutral way that is applicable to any project or asset regardless of:
- the nature of contracts, e.g. public, private, alliances, global, partnership;
- the actors' functions, e.g. through the programming, design, construction phases, regardless of organization size including SMEs;
- the diversity of tendering processes and commissioning practices, e.g. one main contractor (lead appointed party) on one client (as appointing party) vs. one client and multiple contracts with individual appointed parties;
- the types of works, e.g. new, refurbished, housing, infrastructure;
- the complexity of the project, asset, or activities.
- Technical specification77 pagesEnglish languagesale 10% offe-Library read for1 day
This document (part 2) provides extended standard semantic modelling patterns for (at least) the following domain-specific asset aspects:
- support for distinction between two subtypes of physical objects: spatial regions and real ("tangible") objects; the latter being discrete or continuous ("bulk matter");
- support for the materialization of physical objects, adding generic chemistry aspects directly relevant for the built environment dealing with materials like concrete, steel, wood and asphalt;
- support for the interaction between objects including connections, interfaces and ports. Interactions being defined as activities where material, information, energy or forces are transferred;
- support for the definition of unstructured, human-interpretable, requirements, coming from appointing party needs, laws and regulations or sector recommendations;
- support for implicit groups having no explicit members (to model situations like "all main girders of some steel bridge");
- support for the explicit modelling of measurements reusing the existing W3C SOSA ontology (as a lightweight but self-contained SSN core ontology);
- support for spatial geometry (location/shape) reusing OGC GeoSPARQL (GML/WKT) and the WGS84_pos ontology (GPS).
- Standard69 pagesEnglish languagesale 10% offe-Library read for1 day
This document (part 2) provides extended standard semantic modelling patterns for (at least) the following domain-specific asset aspects:
- support for distinction between two subtypes of physical objects: spatial regions and real ("tangible") objects; the latter being discrete or continuous ("bulk matter");
- support for the materialization of physical objects, adding generic chemistry aspects directly relevant for the built environment dealing with materials like concrete, steel, wood and asphalt;
- support for the interaction between objects including connections, interfaces and ports. Interactions being defined as activities where material, information, energy or forces are transferred;
- support for the definition of unstructured, human-interpretable, requirements, coming from appointing party needs, laws and regulations or sector recommendations;
- support for implicit groups having no explicit members (to model situations like "all main girders of some steel bridge");
- support for the explicit modelling of measurements reusing the existing W3C SOSA ontology (as a lightweight but self-contained SSN core ontology);
- support for spatial geometry (location/shape) reusing OGC GeoSPARQL (GML/WKT) and the WGS84_pos ontology (GPS).
- Standard69 pagesEnglish languagesale 10% offe-Library read for1 day
This New Work Item will extend the basic information given in the EN ISO19650 and in the "Guidance to EN ISO 19650". It will detail and structure the concept of a Common Data Environment (CDE) as a workflow for the collaborative process of managing the information and information containers as solutions that fit to the management and project processes inherent for BIM
It may be necessary to introduce further concept details as elements for understanding and implementation. Archiving and versioning of information containers can become very complex when considering various typical information situations of a project.
Further elements, rules and terminology for information management and digitisation may need to be explained and technically framed in the context of a CDE. It will be a large advantage developing at the same time the "Open API for CDE" in TC442 WG2
In particular this Work Item will describe
- how to link a CDE according to EN ISO 19650 to an already existing Asset Management Systems of the Asset Owner.
- how to maintain and manage "living documents" like Information Models (AIM, PIM)
- how to maintain, exchange and manage Information Requirements like (OIR, AIR, EIR) as well as BIM Execution Plans (BEP)
- how to use and implement Information Delivery Plans for the above entities (MIDP and TIDP in ISO 19650)
- how to manage and collaborate between various Information Containers like models, requirements, container states
- how to support Process Workflow by a CDE based on the IDM concept
It will simply have to describe how to provide "Common Data Environment" throughout the whole life cycle (horizontal aspect) and throughout the spectrum of management levels and stakeholders (vertical aspect).
In the work item proposed here, all important terms, processes and targets are to be expanded around the CDE concept. Relations to already existing normatives will be given.
Informative attachments such as templates and examples could be provided to the benefit of planner, supplier and operator as further guidelines.
- Technical report39 pagesEnglish languagesale 10% offe-Library read for1 day
This New Work Item will extend the basic information given in the EN ISO19650 and in the "Guidance to EN ISO 19650". It will detail and structure the concept of a Common Data Environment (CDE) as a workflow for the collaborative process of managing the information and information containers as solutions that fit to the management and project processes inherent for BIM
It may be necessary to introduce further concept details as elements for understanding and implementation. Archiving and versioning of information containers can become very complex when considering various typical information situations of a project.
Further elements, rules and terminology for information management and digitisation may need to be explained and technically framed in the context of a CDE. It will be a large advantage developing at the same time the "Open API for CDE" in TC442 WG2
In particular this Work Item will describe
- how to link a CDE according to EN ISO 19650 to an already existing Asset Management Systems of the Asset Owner.
- how to maintain and manage "living documents" like Information Models (AIM, PIM)
- how to maintain, exchange and manage Information Requirements like (OIR, AIR, EIR) as well as BIM Execution Plans (BEP)
- how to use and implement Information Delivery Plans for the above entities (MIDP and TIDP in ISO 19650)
- how to manage and collaborate between various Information Containers like models, requirements, container states
- how to support Process Workflow by a CDE based on the IDM concept
It will simply have to describe how to provide "Common Data Environment" throughout the whole life cycle (horizontal aspect) and throughout the spectrum of management levels and stakeholders (vertical aspect).
In the work item proposed here, all important terms, processes and targets are to be expanded around the CDE concept. Relations to already existing normatives will be given.
Informative attachments such as templates and examples could be provided to the benefit of planner, supplier and operator as further guidelines.
- Technical report39 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard31 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard31 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard23 pagesEnglish languagesale 15% off
- Standard24 pagesFrench languagesale 15% off
This document specifies requirements for defining structure and content for library objects to support project inception, brief, design, tendering, construction, operations, use and demolition, supporting the development of information throughout the process, in connection with building information modelling (BIM) and the organization of the objects into libraries.
This document does the following:
Establishes requirements for defining template objects, generic objects and product objects in data-driven library and design processes.
Establishes requirements for graphical symbols and other graphic conventions for use on drawings for the built environment, giving principles and definitions for the symbolic and simplified visual presentation of objects. It also describes a rationale of symbolism which establishes rules for the design of graphical symbols and other graphic conventions and gives recommendations for the application of those rules and the ways in which symbolism should be used.
Defines the purposes of characterizing the shape and measurement of library objects.
Defines the purposes of specifying and assessing properties for library objects. It defines the information appropriate for specific uses, including specification of the desired outcome (typically by designers and engineers) and the selection of identified products (typically by contractors and subcontractors). It also gives recommendations for the application of assemblies in integrated BIM working.
Refers to the Industry Foundation Classes (IFC) schema as a common object model.
This document is applicable to all professionals and service providers who produce and use library objects with generic and product-specific information. This group includes, but is not limited to, product manufacturers and suppliers, library authors, designers and engineers, contractors, owners, maintainers and commissioners.
- Standard47 pagesEnglish languagesale 10% offe-Library read for1 day
This document is applicable to construction processes where the usual surveyor’s control points are to be used not only for geometry control, but other applications such as laser scanning, localization of autonomous vehicles, photogrammetry, or VR/AR applications.
It provides a framework for making accurate survey point information available to digital applications and other trades. This includes the layout of markers, a naming convention for markers and a common digital interface for the read-out-data of markers.
The document builds on existing standards and conventions and collates them where applicable.
The document is intended to be used on construction sites and in existing buildings by planners (architects, civil engineers,…), surveyors, construction companies, software providers, UXV operators, BIM stakeholders, and on site machines/devices/systems.
The survey point information may be utilised not only during the construction but also during maintenance throughout the life of the facility.
- Technical report24 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for defining structure and content for library objects to support project inception, brief, design, tendering, construction, operations, use and demolition, supporting the development of information throughout the process, in connection with building information modelling (BIM) and the organization of the objects into libraries.
This document does the following:
Establishes requirements for defining template objects, generic objects and product objects in data-driven library and design processes.
Establishes requirements for graphical symbols and other graphic conventions for use on drawings for the built environment, giving principles and definitions for the symbolic and simplified visual presentation of objects. It also describes a rationale of symbolism which establishes rules for the design of graphical symbols and other graphic conventions and gives recommendations for the application of those rules and the ways in which symbolism should be used.
Defines the purposes of characterizing the shape and measurement of library objects.
Defines the purposes of specifying and assessing properties for library objects. It defines the information appropriate for specific uses, including specification of the desired outcome (typically by designers and engineers) and the selection of identified products (typically by contractors and subcontractors). It also gives recommendations for the application of assemblies in integrated BIM working.
Refers to the Industry Foundation Classes (IFC) schema as a common object model.
This document is applicable to all professionals and service providers who produce and use library objects with generic and product-specific information. This group includes, but is not limited to, product manufacturers and suppliers, library authors, designers and engineers, contractors, owners, maintainers and commissioners.
- Standard47 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies requirements for defining structure and content for library objects to support project inception, brief, design, tendering, construction, operations, use and demolition, supporting the development of information throughout the process, in connection with building information modelling (BIM) and the organization of the objects into libraries. This document does the following: Establishes requirements for defining template objects, generic objects and product objects in data-driven library and design processes. Establishes requirements for graphical symbols and other graphic conventions for use on drawings for the built environment, giving principles and definitions for the symbolic and simplified visual presentation of objects. It also describes a rationale of symbolism which establishes rules for the design of graphical symbols and other graphic conventions and gives recommendations for the application of those rules and the ways in which symbolism should be used. Defines the purposes of characterizing the shape and measurement of library objects. Defines the purposes of specifying and assessing properties for library objects. It defines the information appropriate for specific uses, including specification of the desired outcome (typically by designers and engineers) and the selection of identified products (typically by contractors and subcontractors). It also gives recommendations for the application of assemblies in integrated BIM working. Refers to the Industry Foundation Classes (IFC) schema as a common object model. This document is applicable to all professionals and service providers who produce and use library objects with generic and product-specific information. This group includes, but is not limited to, product manufacturers and suppliers, library authors, designers and engineers, contractors, owners, maintainers and commissioners.
- Standard37 pagesEnglish languagesale 15% off
- Standard40 pagesFrench languagesale 15% off
The digital transformation of the construction industry includes also the digital transformation of the supply chaine of construction products. With EN ISO 16739-1 exists an open language to design, transfer and maintain construction models. The construction models (e.g. of a building) contain a digital twin of real-life products. The data of these products should be transported in a digital format on the way from the factory to the building owner.
This product data should be expressed also in an easy and open way. The creators of product data files should be able to do this manually or automatically, as they like it. The users of product data should be able to use it to:
• Express their requirements related to products
• Describe configurable products
• Import product data easily in the BIM models at any stage of the project (design, construction, operation)
• Export product data easily from the BIM models at any stage of the project (design, construction, operation)
These scenarios fit in the business models of manufacturers, planners, construction companies and facility managers.
The working group 4 of CEN-TC442 has published proposals for creating new work items in the sector of CEN regarding the storage and the transport of product data in the sector of building information modelling (BIM):
EN ISO 16739-1:2018: Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries- Part 1: Data schema
EN ISO 12006-3: Building construction – Organization of information about construction works – Part 3: Framework for object-oriented information
prEN ISO 23386: Building information modelling and other digital processes used in Construction – Methodology to describe, author and maintain properties in interconnected dictionaries
prEN ISO 23387: Data templates for construction works entities, Part 1: Objects, collections, and relationships defining the general structure of data templates
This standard defines a format to negotiate product data templates, express requirements and describe configurable products and therefore fills the missing link between the product data sources (e.g. catalogs) from the manufacturers and the BIM models of the designers, builders, and owners.
- Standard212 pagesEnglish languagesale 10% offe-Library read for1 day
This document is the technical addition to the methodology set out in ISO 29481-1. It defines a specification to store, exchange and read information delivery manual (IDM) specifications in a standardized and machine-readable way.
- Standard39 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the detailed process and criteria for decision makings when executing an information exchange as specified by the ISO 19650 series to ensure the quality of the resulting project information model or asset information model. It details the implementation of the concepts in ISO 19650-1 and is applicable to any information exchange within the delivery stages covered by ISO 19650-2 and operational trigger events covered by ISO 19650-3.
This document is applicable to assets of all sizes and all levels of complexity. This includes portfolios of buildings, campuses, infrastructure networks, individual buildings and pieces of infrastructure. The requirements in this document should be applied in a way that is appropriate to the scale and complexity of the asset. This document makes use of the phrase “shall consider”. This phrase is used to introduce a list of items that the person in question is required to think about carefully in connection with the primary requirement described in the subclause. The amount of thought involved, the time taken to complete it, and the need for supporting evidence depend on the complexity of the asset, the experience of the person(s) involved, and the requirements of any national policy on introducing building information modelling. On a relatively small or straightforward asset, it can be possible to complete, or dismiss as not relevant, some of these “shall consider” items very quickly. One way to help identify which of the “shall consider” statements are relevant can be to review each statement and create templates for assets of different sizes and complexity.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
This document addresses syntactic and semantic interoperability for information describing assets going through their life cycle in the built environment. It assumes the underlying technical interoperability provided already by the Internet/World Wide Web (WWW) technology-stack. The syntactic aspects relate to the Linked Data (LD)/Semantic Web (SW) formats and the SPARQL direct access method provided. The semantic aspects relate to the LD/SW-based information models in the form of thesauri and ontologies giving meaning to the information.
The following information architecture (Figure 1) applies.
This document specifies:
- a conceptual "L1: Information language" with four RDF-based language bindings being SKOS, RDFS, OWL and SHACL, including:
- a choice of 'linked data'/RDF-based formats (to be used for all modelling and language levels); and
- a generic Top Level Information Model of a total "M1: Information model", here "an upper ontology", including:
- a set of generic information modelling patterns for identification, annotation, enumeration datatypes, complex quality/quantity modelling, decomposition and grouping.
This modelling approach for information models and information sets is relevant within the built environment from multiple perspectives such as:
- Building information modelling (BIM);
- Geographical information systems (GIS);
- Systems engineering (SE);
- Monitoring & control (M&C); and
- Electronic document management (EDM).
Annex E discusses in an informative way how the information models and sets relevant for these different worlds can be linked together using LD/SW technology.
This document does not specify a full meta-'information model', sometimes referred to as a 'Knowledge Model (KM)'. EN ISO 12006-3 provides such an often used model for the built environment. In Annex D, Subclause D.3 it is shown how this existing model can be made compliant to this document. The only direct support for this meta level comes in the form of the possibility to define 'types' (enumeration types or concept types) and 'objectifications' as metaconcepts.
This document does not specify a meta-'information language' since this is already provided by the concrete RDF-based language bindings (being RDFS).
The scope of this document in general excludes the following:
- Business process modelling;
- Software implementation aspects;
- Information packaging and transportation/transaction aspects already handled by ISO TC59/SC13 Information container for linked document delivery (ICDD) ([13]) respectively various information delivery manual (IDM) / information exchange requirements (EIR)-related initiatives; and
- Domain-specific (here: 'built environment'-specific) content modelling in the form of concepts, attributes and relations at end-user level (the actual ontologies themselves) beyond a generic top level information model ('upper ontology') and modelling and linking patterns.
- Standard97 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes a framework for providing specifications for the internal commissioning and implementation of building information modelling (BIM) during both delivery and operational phases. It identifies a structured approach so as to encourage clarity during development, management and checking processes for use by organizations that develop and apply these specifications. This document does not provide specific content but it does provide examples. It is applicable to buildings, infrastructure, facilities and managed landscapes, of any size or complexity.
- Standard22 pagesEnglish languagesale 15% off
This document is the technical addition to the methodology set out in ISO 29481-1. It defines a specification to store, exchange and read information delivery manual (IDM) specifications in a standardized and machine-readable way.
- Standard39 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a language-independent information model which can be used for the development of dictionaries used to store or provide information about construction works. The model is extended by instantiating content, such as further objects and their relationships, allowing the content to serve as an ontology, taxonomy, meronomy, lexicon and thesaurus.
NOTE 1 Lexicons are resources for comprising lexical entries for a given language
NOTE 2 Meronomies are type of hierarchies which deals with part-whole relationships
NOTE 3 Ontologies are formal, explicit specification of a shared conceptualizationIt enables classification systems, information models, object models, data templates and process models to be cross-referenced from within a common framework.
This document provides the description of an API allowing the interconnection of data dictionaries as described in ISO 23386.
- Standard52 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the detailed process and criteria for decision makings when executing an information exchange as specified by the ISO 19650 series to ensure the quality of the resulting project information model or asset information model. It details the implementation of the concepts in ISO 19650-1 and is applicable to any information exchange within the delivery stages covered by ISO 19650-2 and operational trigger events covered by ISO 19650-3.
This document is applicable to assets of all sizes and all levels of complexity. This includes portfolios of buildings, campuses, infrastructure networks, individual buildings and pieces of infrastructure. The requirements in this document should be applied in a way that is appropriate to the scale and complexity of the asset. This document makes use of the phrase “shall consider”. This phrase is used to introduce a list of items that the person in question is required to think about carefully in connection with the primary requirement described in the subclause. The amount of thought involved, the time taken to complete it, and the need for supporting evidence depend on the complexity of the asset, the experience of the person(s) involved, and the requirements of any national policy on introducing building information modelling. On a relatively small or straightforward asset, it can be possible to complete, or dismiss as not relevant, some of these “shall consider” items very quickly. One way to help identify which of the “shall consider” statements are relevant can be to review each statement and create templates for assets of different sizes and complexity.
- Standard20 pagesEnglish languagesale 10% offe-Library read for1 day
This document is the technical addition to the methodology set out in ISO 29481-1. It defines a specification to store, exchange and read information delivery manual (IDM) specifications in a standardized and machine-readable way.
- Standard30 pagesEnglish languagesale 15% off
- Standard31 pagesFrench languagesale 15% off
This document specifies the detailed process and criteria for decision makings when executing an information exchange as specified by the ISO 19650 series to ensure the quality of the resulting project information model or asset information model. It details the implementation of the concepts in ISO 19650-1 and is applicable to any information exchange within the delivery stages covered by ISO 19650-2 and operational trigger events covered by ISO 19650-3. This document is applicable to assets of all sizes and all levels of complexity. This includes portfolios of buildings, campuses, infrastructure networks, individual buildings and pieces of infrastructure. The requirements in this document should be applied in a way that is appropriate to the scale and complexity of the asset. This document makes use of the phrase “shall consider”. This phrase is used to introduce a list of items that the person in question is required to think about carefully in connection with the primary requirement described in the subclause. The amount of thought involved, the time taken to complete it, and the need for supporting evidence depend on the complexity of the asset, the experience of the person(s) involved, and the requirements of any national policy on introducing building information modelling. On a relatively small or straightforward asset, it can be possible to complete, or dismiss as not relevant, some of these “shall consider” items very quickly. One way to help identify which of the “shall consider” statements are relevant can be to review each statement and create templates for assets of different sizes and complexity.
- Standard12 pagesEnglish languagesale 15% off
- Standard13 pagesFrench languagesale 15% off
This document specifies a language-independent information model which can be used for the development of dictionaries used to store or provide information about construction works. The model is extended by instantiating content, such as further objects and their relationships, allowing the content to serve as an ontology, taxonomy, meronomy, lexicon and thesaurus.
NOTE 1 Lexicons are resources for comprising lexical entries for a given language
NOTE 2 Meronomies are type of hierarchies which deals with part-whole relationships
NOTE 3 Ontologies are formal, explicit specification of a shared conceptualizationIt enables classification systems, information models, object models, data templates and process models to be cross-referenced from within a common framework.
This document provides the description of an API allowing the interconnection of data dictionaries as described in ISO 23386.
- Standard52 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a language-independent information model which can be used for the development of dictionaries used to store or provide information about construction works. The model is extended by instantiating content, such as further objects and their relationships, allowing the content to serve as an ontology, taxonomy, meronomy, lexicon and thesaurus. NOTE 1 Lexicons are resources for comprising lexical entries for a given language NOTE 2 Meronomies are type of hierarchies which deals with part-whole relationships NOTE 3 Ontologies are formal, explicit specification of a shared conceptualizationIt enables classification systems, information models, object models, data templates and process models to be cross-referenced from within a common framework. This document provides the description of an API allowing the interconnection of data dictionaries as described in ISO 23386.
- Standard43 pagesEnglish languagesale 15% off
- Standard58 pagesFrench languagesale 15% off
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.
- Technical report19 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Technical report19 pagesEnglish languagesale 10% offe-Library read for1 day
This document deals with the processes involved in the procurement and delivery of information to planning and construction projects, specifically with exchange information requirement (EIR) and BIM execution plan (BEP), considering the administrative processes. This document takes into account international standards and specifications as well as recommended practice.
This document is relevant for all parties involved in the tendering of information deliverables. Including both those that require and those that deliver the information. The required information can be relevant for all processes in the life cycle such as design, construction, operation and maintenance and end-of-life processes. It applies above all to e.g. client, asset owners/operators, architects, engineer, contractors, subcontractors etc.
This document provides methodology to appointing parties on how to require and agree the right amount, quality and level of information needs.
It is also important for appointed parties to be able to assess the quality of existing EIRs and identify possible over-specification or gaps. Based on this, it is possible to estimate and calculate the necessary effort for data creation.
This document operationalizes the tendering and appointment process of information deliverables as specified in EN ISO 19650-2:2018. This document does not cover all clauses of EN ISO 19650-2:2018. Its main goal is to provide template examples and guidance for all activities conditioning specification of requirements and deliverables in the production of exchange information requirements and BIM execution plan. Specifically, it covers the “shall” and “shall consider” requirements in EN ISO 19650-2:2018, 5.2.1 (EIR), 5.3.2 (pre-appointment BEP) and 5.4.1 (confirmed BEP). For specification of Scope and out of scope see Table 1 (see Annex A for which part of EN ISO 19650-2:2018 is supported by templates).
- Technical report55 pagesEnglish languagesale 10% offe-Library read for1 day
2021-07-14 - TC origine - Update of unit for "Eutrophication aquatic freshwater" in Tables 3 and C.1
- Corrigendum4 pagesEnglish languagesale 10% offe-Library read for1 day
This document deals with the processes involved in the procurement and delivery of information to planning and construction projects, specifically with exchange information requirement (EIR) and BIM execution plan (BEP), considering the administrative processes. This document takes into account international standards and specifications as well as recommended practice.
This document is relevant for all parties involved in the tendering of information deliverables. Including both those that require and those that deliver the information. The required information can be relevant for all processes in the life cycle such as design, construction, operation and maintenance and end-of-life processes. It applies above all to e.g. client, asset owners/operators, architects, engineer, contractors, subcontractors etc.
This document provides methodology to appointing parties on how to require and agree the right amount, quality and level of information needs.
It is also important for appointed parties to be able to assess the quality of existing EIRs and identify possible over-specification or gaps. Based on this, it is possible to estimate and calculate the necessary effort for data creation.
This document operationalizes the tendering and appointment process of information deliverables as specified in EN ISO 19650-2:2018. This document does not cover all clauses of EN ISO 19650-2:2018. Its main goal is to provide template examples and guidance for all activities conditioning specification of requirements and deliverables in the production of exchange information requirements and BIM execution plan. Specifically, it covers the “shall” and “shall consider” requirements in EN ISO 19650-2:2018, 5.2.1 (EIR), 5.3.2 (pre-appointment BEP) and 5.4.1 (confirmed BEP). For specification of Scope and out of scope see Table 1 (see Annex A for which part of EN ISO 19650-2:2018 is supported by templates).
- Technical report55 pagesEnglish languagesale 10% offe-Library read for1 day
This document contains the terms and definitions of general concepts to establish a vocabulary applicable to buildings and civil engineering works.
It comprises:
a) fundamental concepts, which can be the starting point for other, more specific, definitions;
b) more specific concepts, used in several areas of construction and frequently used in standards, regulations and contracts.
- Standard6 pagesEnglish languagesale 15% off
- Standard171 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard307 pagesEnglish and Russian languagesale 15% off
This document provides the opportunity to add information about the contents of a container by further specializing the generic types of links specified in ISO 21597-1. The defined link types have been chosen to enhance the use of the container by allowing the addition of semantic relationships that are human interpretable to provide greater clarity about those links.
- Standard29 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides terms and definitions for facility management in relation to buildings and civil engineering works. These terms and definitions reflect standardized terminology relevant to construction works needed by those having a responsibility for facility management.
- Standard25 pagesEnglish languagesale 15% off
This document specifies requirements for information management, in the form of a management process, within the context of the operational phase of assets and the exchanges of information within it, using building information modelling.
This document can be applied to all types of assets and by organizations of all types and sizes involved in the operational phase of assets.
The requirements in this document can be achieved through direct actions carried out by the organization in question or can be delegated to another party.
- Standard43 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the principles and requirements for security-minded information management at a stage of maturity described as "building information modelling (BIM) according to the ISO 19650 series", and as defined in ISO 19650-1, as well as the security-minded management of sensitive information that is obtained, created, processed and stored as part of, or in relation to, any other initiative, project, asset, product or service.
It addresses the steps required to create and cultivate an appropriate and proportionate security mindset and culture across organizations with access to sensitive information, including the need to monitor and audit compliance.
The approach outlined is applicable throughout the lifecycle of an initiative, project, asset, product or service, whether planned or existing, where sensitive information is obtained, created, processed and/or stored.
This document is intended for use by any organization involved in the use of information management and technologies in the creation, design, construction, manufacture, operation, management, modification, improvement, demolition and/or recycling of assets or products, as well as the provision of services, within the built environment. It will also be of interest and relevance to those organizations wishing to protect their commercial information, personal information and intellectual property.
- Standard40 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the opportunity to add information about the contents of a container by further specializing the generic types of links specified in ISO 21597-1. The defined link types have been chosen to enhance the use of the container by allowing the addition of semantic relationships that are human interpretable to provide greater clarity about those links.
- Standard29 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides the opportunity to add information about the contents of a container by further specializing the generic types of links specified in ISO 21597-1. The defined link types have been chosen to enhance the use of the container by allowing the addition of semantic relationships that are human interpretable to provide greater clarity about those links.
- Standard21 pagesEnglish languagesale 15% off
- Standard21 pagesFrench languagesale 15% off
This document defines an open and stable container format to exchange files of a heterogeneous nature to deliver, store and archive documents that describe an asset throughout its entire lifecycle.
It is suitable for all parties dealing with information concerning the built environment, where there is a need to exchange multiple documents and their interrelationships, either as part of the process or as contracted deliverables. The format is intended to use resources either included in the container (such as documents) or referenced remotely (such as web resources). A key feature is that the container can include information about the relationships between the documents. Relevant use-cases reflect the need for information exchange during the entire life cycle of any built asset and can include, but are not limited to, the handover of
- a published bidding package,
- required project deliverables at a specific project stage (e.g. when proposing different design scenarios),
- shared information as background or for further development,
- published approval packages, or
- information about versions between partners to provide a means to reference particular states of the information and track changes.
- Standard49 pagesEnglish languagesale 10% offe-Library read for1 day