The Common Schema, also known as the Smart InterOp (SIO) Schema, defines all the objects and relationships supported for integration with HxGN SDx. Therefore, it covers objects from all applications that can integrate with SDx.
The following rules and principles outline how the integration schema was built and functions.
Top-down decomposition of the schema
The top-down decomposition of the schema is designed to make the Common Schema easier to understand. At its highest level, it consists of the following four types of objects:
Assets - typically plants or ships. The asset is the object at the top of the schema.
Breakdown structures - the various organizational decompositions of the asset's objects, based on the workflows performed throughout the lifecycles of the objects.
Connectivity model - general categorization of all the objects for the asset.
Documentation - all the documentation produced throughout the lifecycle of the asset.
Class, interface, and relationship definitions
All property definitions are exposed by interface definitions (never by class definitions), and all relationship definitions connect two interface definitions. Class definitions realize interfaces. Therefore, property and relationship definitions that apply to a class definition are defined by the set of interface definitions that it realizes.
Objects for an asset (like a plant or a ship) are organized into a variety of breakdown hierarchies, based on the needs of a design project, as well as the requirements for ongoing maintenance of the asset:
Plant (or asset) breakdown - includes system and specializations of systems, such as area, unit, equipment system, electrical system, and so forth.
Work breakdown - includes projects, WBS items, and work packages, as well as specializations of WBS items.
Assembly breakdown - includes assembly base and its specializations, such as planning assembly, planning block, and planning assembly block. Also includes spool and its specializations, like piping spool, duct spool, and so forth.
Common connectivity model
Rather than having separate connectivity models based on types of objects, the SDx integration schema uses a single connectivity model to describe all types of connection (except structural connections). This connectivity models recognizes the commonality across the various disciplines and tools and defines a single model (as opposed to multiple models in the Smart Plant Foundation integration) to describe all the objects for the asset. The connectivity model is tag-centric and port-centric with all the objects fitting into the model at or below the tag or port.
Many "tags" are objects that are not named, such as pipes.
Although integration with SDx is object-centric (you can share a single object rather than a document or packages of objects), documents are still an important piece of the overall approach. The Documentation model describes all the documents produced throughout the lifecycle of the asset. It includes the documents, files associated with the documents, and the folders that files are organized into.
The schema does not describe an object's graphics. However, the correlation of object graphics to the various object types is important to fully understand the schema.
Plug-in customer-specific or standard-specific schema
The schema is designed to be extendable by adding customer-specific or standard-specific schema.