Original Author: Gerd Eichler
Introduction
In this process you will modify the schema so as to pass the Service value from a pipeline to a pipe run and then onto a valve placed in that pipe run. This requires the modification of two separate schemas because SERVICE is not a property of a component but an associated item. The service is defined separately in the drawing settings and represents an object. This service object then is associated to the pipeline.
Review the use of the Notify property Custom Atribute
- Launch OPPID with the Imperial workspace
- From the Utilies menu launch the ECClassEditor
- Open the schema
C:\ProgramData\Bentley\PowerPID (SELECTseries3)\WorkSpace\Projects\Ansi\Data\resource\OpenPlant_PID_Supplemental_Imperial.01.01.ecschema.xml
-
Expand the classes tree and select the class Piping Network System
-
Select the PROPERTIES tab and browse for the properties and select Design Size
Note the Custom Attributes - bmf.01.00:Notify Related Component of Property Value Change. You will add the same custom attribute to Service but with a few different parameters
• While still in Piping Network System - Select the SERVICE property
o Pick on Custom Attributes and add the bmf.01.00: Notify Related Component of Property Value Change.
o Modify the custom attribute as shown below
o Save the changes
• Select the Piping Network Segment class
o Navigate to the Properties tab and then ADD>NEW property and name the new property as shown below.
o Save the Schema
• Modify the "OpenPlant_PID.01.02.ecschema.xml " schema
o While still in the Class Editor load the "OpenPlant_PID.01.02.ecschema.xml"
o Select the Pipe Run class in the left panel and then select the Properties tab and choose ADD>NEW. Add a new property named DESIGN_SERVICE and add the appropriate custom attributes as shown below.
o Save the changes and save the schema
• Modify the Gate Valve Class to display the SERVICE property.
o Browse in the left panel to the Classes>Valves>Single Way Valves>Gate Hand Valve class
o Select the Properties tab and locate the SERVICE Property.
o With the Service Property selected pick the OVERRIDE button.
o Add a Category and a Property Priority custom attribute to the SERVICE class. See below for changes. NOTE - The Category does not have to be as shown - it could be located under Operating Conditions for example.
o Save the changes and save the schema.
o Exit the Class Editor
• Modify LIST for Valves to include the String List from SERVICE
o While still in PID_ANSI schema migrate to the class LIST-> Associated Logical Item Classes for Valves
o Modify the String List custom attribute and add SERVICE as a list value.
o Save the changes and save the schema.
• Test the changes
o Load OpenPlant PowerPID, create a new file and add an Area value and two or more Services values.
o Place a Process Line and note that when the service is set for the Process Line and you pick on the Pipe Run P1 Business Key that "Design Service" for the run is populated and matches the same service selected for the process.
o Place the line in the PID
o Add a Gate Valve to the line
o Pick the Gate Valve and note that it has inherited the Service value from Process Line via the Pipe Run.
Explanation of how a pipe run inherits size from the pipeline (SS3)
- Schema: OpenPlant_PID.01.01.ecschema.xml
- Class: PIPING_NETWORK_SYSTEM
- Property: DESIGN_SIZE
- Custom Attribute: BMF_NOTIFY_RELATED_COMPONENT_OF_PROPERTY_VALUE_CHANGE
The Custom attribute on the DESIGN_SIZE property has the following:
- Get the relationship: <RELATIONSHIP_CLASS_NAME>PIPELINE_HAS_PIPE_RUN</RELATIONSHIP_CLASS_NAME>
- Get the class type to update: <RELATED_CLASS_NAME>oppid:PIPING_NETWORK_SEGMENT</RELATED_CLASS_NAME>
- Get the property to update <RELATED_CLASS_PROPERTY_NAME>SIZE</RELATED_CLASS_PROPERTY_NAME>
So the PIPING_NETWORK_SEGMENT.SIZE property is updating from the PIPING_NETWORK_SYSTEM. DESIGN_SIZE property.