Byggnadsindustrin

Ämnesområden: Byggnadsindustrin: allmänt
Kommittébeteckning: SIS/TK 269 (Bygg- och förvaltningsdokumentation)
Källa: CEN
Svarsdatum: den 21 okt 2018
Se merSe mindre
 

The primary purpose of this International Standard is the provision of data structures for electronic

product catalogues to transmit building services product data automatically into models of building

services software applications. This includes a meta model for the specification of product classes

and their properties and a meta model for the product data which is exchanged in product catalogues.

Product data has to follow the specifications for their product groups.

The standard series is split into two areas:

— Basic concepts like conceptual models, languages, geometry representations, and XML schemas for data

exchange are provided in the Conceptual Parts of the standard series (Parts with a one digit number).

— Using these resources, the Content Parts of this International Standard define for various product

groups of building services concrete models for the description and the exchange of products.

The basic concepts which are provided by the standard series include the following:

— resources for the specification of selection properties and a selection property tree guiding the

selection process to identify the appropriate product variant from a parametric electronic catalogue;

— resources for the specification of dependent properties and their computational functions to

compute their values in dependency from installation parameters;

— resources for the specification of composition relationships between products which can be used to

model structures like bill of materials or accessory relationships;

— resources for a parametric constructed solid geometry (CSG) based geometry representation containing

specific CSG elements geometrical elements which are typical for building services products.

This part of ISO 16757 specifies

— the underlying concepts,

— a generic model specifying the available modelling elements and their relationships, and

— a framework for the specification of the Content Parts by describing the elements which are to be

provided by these Parts.

Not in scope of this part of ISO 16757 are the following:

— a detailed description of the used geometrical primitives;

NOTE Geometry is described in ISO 16757-2.

— a specification of the script language used to exchange algorithms for computing the values of

dependent and computable properties;

NOTE The script language is described in ISO 16757-3.

— a specification of the XML Schema specifying the data structures for the catalogue exchange;

NOTE The XML schema is described in ISO 16757-5.

— a description of the relationships to standards of the area of buildingSMART;

NOTE The relationships to standards of the area of buildingSMART is described in ISO 16757-4.

— definition of models for specific product groups.

NOTE 1 Definitions of models for specific product areas are described in ISO 16757-10 et. seq., the Content

Parts of ISO 16757.

NOTE 2 All parts are still under development.

Ämnesområden: Byggnadsindustrin: allmänt
Kommittébeteckning: SIS/TK 269 (Bygg- och förvaltningsdokumentation)
Källa: CEN
Svarsdatum: den 21 okt 2018
Se merSe mindre
 

This part of ISO 16757 describes the modelling of building services product geometry. The description is optimized for the interchange of product catalogue data and includes

— shapes for representing the product itself,

— symbolic shapes for the visualization of the product’s function in schematic diagrams,

— spaces for functional requirements,

— surfaces for visualization, and

— ports to represent connectivity between different objects.

The shape and space geometry is expressed as Constructive Solid Geometry (CSG) based on geometric primitives concatenated to boundary representations by Boolean operations. This part of ISO 16757 uses the applicable primitives from ISO 10303-42 and from ISO 16739 and adds primitives which are required for the special geometry of building services products. For symbolic shapes, line elements are also used.

This part of ISO 16757 neither describes the inner structure and internal functionality of the product nor the manufacturing information because this is typically not published within a product catalogue.

Building services products can have millions of variant dimensions. To avoid the exchange of millions of geometries, a parametric model is introduced which allows the derivation of variant-specific geometries from the generic model. This is necessary to reduce the data to be exchanged in a catalogue to a manageable size. The parametric model will result in smaller data files, which can be easier transmitted during data exchanges.

The geometry model used does not contain any drawing information such as views, line styles or hatching.

Kommittébeteckning: SIS/TK 269 (Bygg- och förvaltningsdokumentation)
Källa: CEN
Svarsdatum: den 16 nov 2018
Se merSe mindre
 

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

1. a published bidding package,

2. required project deliverables at a specific project stage,

3. shared information as background or for further development, or

4. 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.

Kommittébeteckning: SIS/TK 269 (Bygg- och förvaltningsdokumentation)
Källa: CEN
Svarsdatum: den 16 nov 2018
Se merSe mindre
 

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:

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

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

3. Add the ability for exchanging systems engineering information

4. Link to product requirement libraries

5. Add semantic links (i.e. meaningful links) to and between information provided using

existing standards like PLCS, IFC and GML

6. Link to an ontology for Units and Measures, like QUDT

7. 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.