PipeRun - Intergraph Smart P&ID - 10.0 - Administration & Configuration - Hexagon PPM

Intergraph SmartPlant Enterprise Adapter for Smart P&ID

Language
English
Product
Intergraph Smart P&ID
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
Smart Electrical Version
10
Smart P&ID Version
10
Smart Engineering Manager Version
11

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 process data for 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, the fluid. Furthermore, the SmartPlant Schema has several classes that are used to publish a Stream and its associated process data on a PFD. The 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 objects can be retrieved onto the Smart P&ID PipeRun object.

Select Criteria – The Select Criteria field on the MapProperty is used to indicate to the SmartPlant Adapter how to handle each property for both publish and retrieve. The format of the Select Criteria field is:

  • Select Criteria = <Retrieve Path>%<Publish Path>

  • <Retrieve Path> – A string that 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 this property has a value, 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> – A string that indicates where the property goes to during publish. If this value is empty, it means that the property is published to the primary object (PIDPipingConnector). If this property has a value (it should be equal to ‘ProcessPoint’), it means that this property is published to the related PIDProcessPoint object.