Class Library

The default class model library (Conceptual Data Model) as supplied conforms to engineering information standards including but not limited to ISO15926 (Part 4). The Conceptual Data Model is a fully configurable and hierarchical data model.

The default model library contains:

The ontology of the default class model library can be seen as three dimensional in nature:

• Conceptual physical characteristics are grouped at each level in the tree (1D)

• These become more specialized as you go down the tree (2D).

• Finally, relationships across classes traverse across the tree (3D).

The gradient goes from abstract collections, type categories, functional collections (PFD type classes) & on to specialized physical classes (P&ID type classes).

The basic physical ontology is based on ISO 15926, with mappings to CFIHOS, PCA, StepLib, ISO 14224 and others can be added. No single standard is totally suited to a real usage in a design tool and modifications were needed to suit the real world. The base model needed to be supplemented with attributes from deliverables such as API/ISA datasheets as well as symbology from the various symbols’ standards.

It is important to stress that the design was scoped for multi-disciplinary workflows, including:

• Simulation import

• PFDs/P&IDs

• Datasheets

• Hook-ups

• Loop schematic

For these deliverables, ISO 15926 gave the granularity and decomposition needed as seen on an API datasheet. If we wish to use this in the digital twin in a different context it needs to be componentized. This approach is used as the physical categorization is the only one that can be applied easily to other categorization contexts that are not physical, but context based e.g., CFIHOS and 14224.

The model can be extended; however, it is important to try and stick to default model standards, inheritance from the upper ontology helps guarantee some functionality and business logic.

Model Vocabulary

The application vocabulary provides the ability to map model classes and attributes to the concepts required by a specific application functionality.

The default class model is fully configured and validated using the vocabularies listed below. The model classes and attributes must always be validated against these specified vocabularies.

Model Build Process

The Build process compiles the conceptual data model into DABACON schema for use by AVEVA Unified Engineering. Instantiated data in DABACON can be viewed using the Dictionary Explorer.

It is recommended that the Build process is initiated after first validating the Vocabularies as described above to ensure errors are discovered and resolved prior to creation. Below is an example showing the results of a completed built model definition.