Navrhování budov

Oblast zaměření: Navrhování budov
Komise : CEN/TC 442 (Building Information Modelling (BIM))
Původce: CEN
K připomínkám do: 30.10.2018
Zobraz více Zobraz méně
 

This Part 2 of the ICDD standard adds functionality to the container format specified in Part 1. Part 1 defines a generic container format to store documents using various formats and structure and the ability to provide links between documents or between referable subsets of these documents (documents and datasets are the payload of the container). Building on that foundation, Part 2 of this standard adds the possibility of adding more semantic (meaningful) information to the contents of the container, as well as to the links between pieces of information in the container using Linked Open Data technology.
 
This standard does not prescribe the structure or format of the documents in the payload.
 
This standard is suitable for industry sectors such as the built environment, where many different standards are used, where there is a mixture of digital representations of proposed or existing built and natural assets (in open or proprietary formats), requiring the use of legacy systems and the application of different classification systems. This part adds the ability to link, in a semantic and meaningful way, those islands of data represented using different formats and structure. This standard is not meant to replace other standards such as ISO 16739 which is recognized as the standard for describing building objects.

This standard provides two conformance classes. Both conformance classes open the ability to specialize the container for use cases not otherwise handled.

In Conformance Class A, the container format of Part 1 is expanded with an ontology dynamic semantics, providing basic support for creating an information model that captures the required semantics of project, organization or sector standards and agreements. By doing so, it provides building blocks that make it easier to link different sources of information. This is achieved by introducing support for typed entities, typed entity properties and typed relationships between those entities (such as the relationship between an assembly and its parts or between a physical entity and its associated requirements). There is also support for defining provenance, versioning and creating libraries.

In Conformance Class B, the user is offered complete freedom to add user defined ontologies to the container, with the sole condition that it is expressed in RDF/OWL.

The use cases are in line with those of Part 1, but may include numerous extensions. The following list gives some examples:

Make use of asset type libraries describing the required properties per asset type

Link to a specific classification system, e.g. CoClass, Uniclass or OmniClass™

Add the ability for exchanging systems engineering information

Link to product requirement libraries

Add semantic links (i.e. meaningful links) to and between information provided using existing standards like PLCS, IFC and GML

Link to an ontology for Units and Measures, like QUDT

Link to one or more Product Catalogues

Since this standard capitalizes on Linked Open Data technology, the header file, along with any additional RDF/OWL files, forms a suite that may be directly queried by software using standard techniques such as SPARQL.

 

 

Oblast zaměření: Navrhování budov
Komise : CEN/TC 442 (Building Information Modelling (BIM))
Původce: CEN
K připomínkám do: 30.11.2018
Zobraz více Zobraz méně
 

This standard defines a generic container format to store a delivered set of documents, including a means to link otherwise disconnected data. In this context, the term document refers to any digital resource that provides information about the built or natural environment, including, but not limited to, any 2D or 3D representation or model, spreadsheet, image or text-based digital resource.

This standard 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 may include, but is not limited to, the handover of

a published bidding package,

required project deliverables at a specific project stage,

shared information as background or for further development, or

published approval packages.

The container format includes a header file and optional link files that define relationships by including references to the documents, or to elements within them. The header file uniquely identifies the container and its contractual or collaborative intention. This information is defined using the RDF and OWL semantic web standards.

The header file, along with any additional RDF/OWL files or resources, forms a suite that may be directly queried by software. Where it includes link references into the content of documents that don’t support standardized querying mechanisms, their resolution may depend on third party interpreters. Alternatively, the link references may be interpreted by the recipient applications, or reviewed interactively by the recipient.

The format can also be used to deliver multiple versions of the same document with the ability to convey the known differences or priority between them.