Background

This article will explain how can we synchronize the valve end conditions to the database field. By default END_CONDITION_DISPLAY property is on INLINE_VALVE class but the class is not mapped so we need to add END_CONDITION_DISPLAY property on VALVE class and then map it with DB field.

Steps to Accomplish

Changes in Schema

1. Open class editor and load OpenPlant_PID schema.
   
   
2. Supplement it with OpenPlant_PID_Supplemental_Imperial schema.
   
   
3. Locate VALVE class in the hierarchy or use search tool to find it.
   
   
4. Add new property END_CONDITION_DISPLAY on it.
   
   
5. Add Category custom attribute and fill the values as shown below.
   
   
6. Add one more custom attribute Extend Type and add the value 'ValveEndConditions' in Name field.
   
   
7. Now add Property Custom attribute and fill as shown below.
   
   
8. Now locate the class SPEC_VALVE_MAPPING_FOR_OPENPLANT_SPECS and change the highlighted values.
   
   
   
   Note: This change is required if you are using OpenPlant Specs to place the valves. The above change is to shorten the display name to be for example FLANGED instead of End_Condition_Flanged.
   
   
9. Save the changes in Schema.

Changes in Projdata.mdb file

1. Open the Projdata.mdb file MS-Access.
   
   
2. Go to VALVE table and open design view.
   
   
3. Add a new field VALVE_END_COND.
   
   
4. Save the changes in mdb file.
   
   
5. Now map the DB field with END_CONDITION_DISPLAY property. Click here for the steps to map EC property with DB field.

Steps to Verify

1. Launch OPPID and open a drawing.
   
   
2. Place some valves and assign end conditions to them.
   
   
3. Synchronize the drawing with DB.
   
   
4. Open the data manager and add the DB field in the view.
   
   
5. Check the end conditions in data manager.
   
   

Comments or Corrections?

Bentley's Product Advantage Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!