ConceptualModel¶
Overview¶
Class
The conceptual content of a DexpiModel, i.e., engineering information independent from its graphical representation.
Attributes (composition)
Name |
Multiplicity |
Type |
|---|---|---|
* |
||
* |
||
0..1 |
||
* |
||
* |
||
* |
||
* |
||
* |
Implementation in Proteus Schema
There is no direct implementation of ConceptualModel in Proteus Schema. A ConceptualModel is a container for the conceptual information in a DexpiModel (as opposed to graphical representation in a Diagram), but there is no such distinction in Proteus Schema.
If and only if the top-level <PlantModel> element in an XML document contains at least one of these elements,
<ActuatingSystem><Drawing><Equipment><InstrumentationLoopFunction><MetaData><PipingNetworkSystem><PlantStructureItem><ProcessInstrumentationFunction><ProcessSignalGeneratingSystem>
then the DexpiModel corresponding to the <PlantModel> contains a ConceptualModel.
Example
Implementation in Proteus Schema
The XML fragment contains one of the elements listed above. Hence, DexpiModel corresponding to the <PlantModel> element contains a ConceptualModel, which contains a PipingNetworkSystem corresponding to the <PipingNetworkSystem> element.
<PlantModel>
...
<PipingNetworkSystem ...>
...
</PipingNetworkSystem>
...
</PlantModel>
ActuatingSystems¶
Attribute (composition)
The ActuatingSystems of the ConceptualModel.
Implementation in Proteus Schema
For each ActuatingSystem, the corresponding <ActuatingSystem> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<ActuatingSystem
ID="actuatingSystem1"
ComponentClass="ActuatingSystem"
ComponentClassURI="http://sandbox.dexpi.org/rdl/ActuatingSystem"
...>
...
</ActuatingSystem>
...
</PlantModel>
InstrumentationLoopFunctions¶
Attribute (composition)
The InstrumentationLoopFunctions of the ConceptualModel.
Implementation in Proteus Schema
For each InstrumentationLoopFunction, the corresponding <InstrumentationLoopFunction> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<InstrumentationLoopFunction
ID="instrumentationLoopFunction1"
ComponentClass="InstrumentationLoopFunction"
ComponentClassURI="http://sandbox.dexpi.org/rdl/InstrumentationLoopFunction"
...>
...
</InstrumentationLoopFunction>
...
</PlantModel>
MetaData¶
Attribute (composition)
The MetaData of the ConceptualModel.
Implementation in Proteus Schema
The <MetaData> element corresponding to the MetaData is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<MetaData
ID="metaData1"
ComponentClass="MetaData"
ComponentClassURI="http://sandbox.dexpi.org/rdl/MetaData"
...>
...
</MetaData>
...
</PlantModel>
PipingNetworkSystems¶
Attribute (composition)
The PipingNetworkSystems of the ConceptualModel.
Implementation in Proteus Schema
For each PipingNetworkSystem, the corresponding <PipingNetworkSystem> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<PipingNetworkSystem
ID="pipingNetworkSystem1"
ComponentClass="PipingNetworkSystem"
ComponentClassURI="http://data.posccaesar.org/rdl/RDS270359"
...>
...
</PipingNetworkSystem>
...
</PlantModel>
PlantStructureItems¶
Attribute (composition)
The PlantStructureItems of the ConceptualModel.
Implementation in Proteus Schema
For each PlantStructureItem, the corresponding <PlantStructureItem> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
As the value type PlantStructureItem is abstract, we consider ProcessPlant as an arbitrary concrete subclass.
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<PlantStructureItem
ID="processPlant1"
ComponentClass="ProcessPlant"
ComponentClassURI="http://data.posccaesar.org/rdl/RDS7151859"
...>
...
</PlantStructureItem>
...
</PlantModel>
ProcessInstrumentationFunctions¶
Attribute (composition)
The ProcessInstrumentationFunctions of the ConceptualModel.
Implementation in Proteus Schema
For each ProcessInstrumentationFunction, the corresponding <ProcessInstrumentationFunction> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<ProcessInstrumentationFunction
ID="processInstrumentationFunction1"
ComponentClass="ProcessInstrumentationFunction"
ComponentClassURI="http://sandbox.dexpi.org/rdl/ProcessInstrumentationFunction"
...>
...
</ProcessInstrumentationFunction>
...
</PlantModel>
ProcessSignalGeneratingSystems¶
Attribute (composition)
The ProcessSignalGeneratingSystems of the ConceptualModel.
Implementation in Proteus Schema
For each ProcessSignalGeneratingSystem, the corresponding <ProcessSignalGeneratingSystem> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<ProcessSignalGeneratingSystem
ID="processSignalGeneratingSystem1"
ComponentClass="ProcessSignalGeneratingSystem"
ComponentClassURI="http://sandbox.dexpi.org/rdl/ProcessSignalGeneratingSystem"
...>
...
</ProcessSignalGeneratingSystem>
...
</PlantModel>
TaggedPlantItems¶
Attribute (composition)
The TaggedPlantItems of the ConceptualModel.
Implementation in Proteus Schema
For each TaggedPlantItem, the corresponding <Equipment> element is a child of the <PlantModel> element that corresponds to the DexpiModel containing the ConceptualModel. See also Proteus Schema Implementation of ConceptualModel.
Example
As the value type TaggedPlantItem is abstract, we consider Vessel as an arbitrary concrete subclass.
Implementation in Proteus Schema
<PlantModel>
<!--
The DexpiModel implemented by this PlantModel element implicitly
contains the ConceptualModel conceptualModel1.
-->
...
<Equipment
ID="vessel1"
ComponentClass="Vessel"
ComponentClassURI="http://data.posccaesar.org/rdl/RDS414674"
...>
...
</Equipment>
...
</PlantModel>