0

Wiki title

A Survey of Industry Data Models and Reference Data Libraries

This survey reviews existing industry data models and reference data libraries across four major application areas—buildings; geospatial (“things in landscape”); manufactured things; and process plants & electrical networks—to inform the development of a Foundation Data Model for the National Digital Twin. It summarizes each model’s defining organization, objectives, scope, structure, extensibility, documentation, maintenance, and industrial usage.

Key Concepts

Top-Level Ontology vs. Pragmatic Models
Although most models predate formal top-level ontologies (TLOs), they exhibit practical, field-validated structures. Understanding how these models map to a chosen TLO is crucial for integration.


Application Schema / Protocol
Models such as IFC (ISO 16739-1) and STEP APs (e.g., AP 242, AP 239) define domain-specific schema—analogous to OGC application schemas for GML.


Reference Data Libraries
Domain-agnostic vocabularies (e.g., ISO 15926 RDL, Core Industrial Data Set, eCl@ss, IEC CDD) supply standardized term definitions and hierarchical classifications that underpin multiple data models.


Versioning, Extensibility, Documentation
Large-scope models demand structured maintenance and extension methodologies, with clear EXPRESS-G, UML, or XML-schema documentation for domain experts.


Temporal & Spatial Parts
Process-plant models (ISO 15926-2, MIMOSA CCOM) track lifecycle events—installations and replacements—using temporal whole-part relations, extending 4D ontologies to maintenance contexts; GIS models (GML, CityGML) capture spatio-temporal features.

Mechanisms

Building Information Models

  • IFC (bSI / ISO 16739-1): UML/EXPRESS schema—root class PRODUCT; distinguishes spatial elements vs. building elements; supported by IDM, MVD, BCF, bSDD.

  • Uniclass-2015 (NBS): Excel-based classification tables spanning complexes to roles; widely used in UK BIM projects.

  • Brick & BOT: OWL-DL schemas for semantic control-system descriptions (Brick) and minimal building topology (BOT) with subclass mappings to IFC and Brick.

Geospatial & Smart City Models

  • GML (OGC/ISO 19136): UML-derived XML schemas for Features, Geometry, Topology, with time-slicing via dynamic feature collections.

  • CityGML (OGC): 3D urban object schema with Levels of Detail (LOD 0–4); covers buildings, terrain, transport, vegetation.

  • LandInfra (OGC): Core conceptual model for land & civil infrastructure—facilities, projects, alignments, road/rail, surveys, land division.

  • INSPIRE (EU Directive 2007/2/EC): Mandatory EU spatial data infrastructure with theme-specific application schemas, GML implementation, and a centralized Feature Concept Dictionary.

Industrial & Manufacturing Data

  • STEP APs (ISO 10303): AP 242/209 for 3D engineering; AP 239 (PLCS) for lifecycle support; core geometry/topology in Part 42; published in EXPRESS, XML, OWL.

  • MoSSEC (ISO 10303-243): Manages simulation-context metadata (who, what, where, when, how, why) as a STEP AP.

  • Core Industrial Data Set (ISO TC 184/SC 4): Proposed ~80-term intermediate vocabulary to bridge domain-specific reference data and multiple top-level models.

Metrology and Simulation

  • QIF (ANSI/NIST/DMSC): XML schemas for measurement plans, results, PPM, statistical analysis; references ISO 10303 for part geometry.

  • OpenDRIVE (ASAM): UML/XML specification for analytical road & rail network descriptions—geometry, lane camber, junction paths—for vehicle dynamics simulation.

  • ISO 14812 (ITS Terminology): UML taxonomy for ITS, including vehicle automation, roadway networks, and functional vs. physical ITS objects.

Process Plant & Utilities

  • ISO 15926-2: 4D top-level ontology for lifecycle integration; EXPRESS-G definitions for physical objects and temporal whole-part.

  • ISO 15926 RDL (-4): ≈11 000 classes across modules (e.g., piping, instrumentation, UoM) published as Excel, with emerging OWL/SKOS representations.

  • MIMOSA CCOM: XML model tracking asset installations (“segments”) and ownership events; underpins OpenO&M SCADA data flows.

  • EPRI CIM (IEC 61970-301): UML-based domain model for electrical transmission & distribution; profiles and RDF/XML or CIMXML implementations.

  • ILAP (ISO 15926-13): Scheduling ontology and XSD for asset-planning exchange among tools; bridges ISO 15926-2 community & external views.

Examples

  1. Vehicle-Wheel Analogy: A wheel (“asset”) installed as a role (“system element”) within a vehicle system, illustrating temporal part relationships across standards (CCOM, CIM, ISO 15926, STEP, QIF).

  2. Point Cloud in LandInfra: External file reference for LiDAR point clouds with optional imagery overlay, aligning with ISO 10303-42’s structured data.

  3. CityGML LOD: A LOD 3 building includes detailed wall/roof surfaces with openings, textures, and thematic differentiation to support 3D visualization.

References

  • ISO 16739-1:2018 Industry Foundation Classes (IFC) [buildingSMART International]

  • BS EN ISO 19650 series on BIM (NBS Uniclass-2015)

  • OGC Geography Markup Language (GML 3.2.1)

  • OGC CityGML 2/3, LandInfra 15-111r1, PipelineML Core (2019)

  • IEC 61970-301 CIM Base; IEC 61970-501 CIM RDF; IEC 61970-452 profiles

  • ISO 10303-242 Managed Model-Based 3D Engineering; ISO 10303-239 PLCS

  • ISO 15926-2 Data Model; ISO 15926-4 RDL; ISO 15926-12/13 OWL ontologies

  • QIF 2.2 (DMSC / ANSI)

  • ASAM OpenDRIVE 1.6 (2020)

  • INSPIRE Directive 2007/2/EC and data specifications (2010–2021)

  • eCl@ss v11.0 and IEC 61360/IEC CDD platforms

  • A Survey of Industry Data Models and Reference Data Libraries - Digital Twin Hub

Comments (0)

You must be logged in to comment.

No comments yet.