PipeRun - Intergraph Smart P&ID - Help - Intergraph

Intergraph Smart P&ID Help

Language
English
Product
Intergraph Smart P&ID
Search by Category
Help
Smart P&ID Version
9 (2019)
Smart Engineering Manager Version
10 (2019)
SmartSketch Version
10.0(2018)

In Smart P&ID there is a single class for PipeRun. This class has properties describing aspects of the physical pipe and other properties that describe the fluid flowing through that pipe. In the SmartPlant schema there are two relevant classes: PIDPipingConnector for the pipe itself and PIDProcessPoint for the process data. Furthermore, the SmartPlant schema has several classes that are used to publish a stream and its associated process data on a PFD. The Smart P&ID tool schema has one MapClass for PipeRun.

Publish

Each Smart P&ID PipeRun is published as a PIDPipingConnector and a PIDProcessPoint with a relationship between the two. Some of the properties from the PipeRun are mapped to the PIDPipingConnector and others are mapped to the PIDProcessPoint.

Retrieve

When an object is retrieved with the IPipingSystemConnector interface, it is recognized as a Stream and is retrieved using the PipeRun MapClass to create or update a PipeRun. The ProcessDataCaseComposition relationship is traversed to obtain objects that realize the IProcessDataCase interface. From those objects, the ProcessDataBulkComposition relationship is traversed to obtain objects that realize the IProcessDataBulkPhase interface. Properties from all of these SmartPlant schema objects can be retrieved onto the Smart P&ID PipeRun object.

Select Criteria

In the Schema Editor, the Select Criteria option on the MapProperty is used to indicate to the adapter how to handle each property for both publish and retrieve. The format of the Select Criteria option is: Select Criteria = <Retrieve Path>%<Publish Path>

<Retrieve Path>

Indicates where the property comes from during retrieve. If this value is empty, it means that the property comes from the primary object being retrieved (IPipingSystemConnector). If a value exists, it means that this property comes from one of the secondary objects that is related to the primary object by means of a relationship.

<Publish Path>

This is a string that indicates where the property goes during publish. If this value is empty, it means that the property is published to the primary object (PIDPipingConnector). If this property is has a value (it should be equal to ProcessPoint), it means that this property is published to the related PIDProcessPoint object.