Applies To Product(s): OpenPlant PID Version(s): 08.11.10.XXX (SS5) | 08.11.11.XXX (SS6) Environment: Windows 7/8.1/10 (64 bit) Area: Customization Subarea: Original Author: Jaya Tiwari, Bentley Product Advantage Group Background This article will cover how user can bring pipeline number on a valve class and use that in Valve Tag. For this example we will create a property PIPELINE_NUMBER for example. Steps to Accomplish: Launch Bentley Class Editor. Open OpenPlant.01.07 schema. Path : C:\ProgramData\Bentley\OpenPlantPID(SS6)\WorkSpace\OPPID\Schemas Supplement OpenPlant.01.07 schema with OpenPlant_Supplemental_Tagging.01.07 Schema. Expand Piping component class, navigate to Fluid Regulator . Add new property as ‘PIPELINE_NUMBER’ and fill details as below. Add ‘Category’ custom Attribute to PIPELINE_NUMBER property. Enter details in Category as shown below. Switch to Properties tab and select Add/Remove to add Custom Attribute on NAME property as shown below. Add “ Calculated ECProperty Specification ” custom attribute on NAME Property. Change the Expressions as given below. ECExpression : this. DEVICE_TYPE_CODE & “-“ & this.PIPELINE_NUMBER & “-“ & this.NUMBER Parser regular expression : ^(? .*)-(? .*)-(? .*)|(? .*) Close OpenPlant schema Open OpenPlant _PID.01.07 of desired project, say here Metric. Supplement it with OpenPlant_PID_Supplemental_Imperial.01.07 schema as shown below. Navigate to Pipeline Class and select NUMBER property. Right Click the NUMBER property. Select Custom Attribute> Add/Remove. Add Notify Related Component of Property Value Change on NUMBER property as shown below. Key-in the values in respective fields as shown below Switch to PIPE RUN class and Add PIPELINE_NUMBER property Add Notify Related Component of Property Value Change ” custom attribute to PIPELINE_NUMBER property Key-in the values in respective fields as shown below. Save all the settings and check result. See Also 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!
↧