This document defines and example of creating a valve tag format that uses two properties from the pipeline in which the valve is inserted. You will add a new property to Pipeline and then pass this property to the Pipe Run along with the existing number property. From this the two properties mapped over to the run will be used in the tag format for a valve. Additionally a new tag format will be created for Pipeline and when modified will pass on to the run and ultimately onto the inline valves. Tag formats in the project database will also be addressed.It is assumed you know how to edit schemas using the Bentley Class Editor.
You will add the new property that is to be used in the tag for Pipeline as well as the tag for the valve. You will also configure this property to pass to the Pipe Run so it can be used in the tag for valve.
Now you will modify the PIPING_NETWORK_SEGMENT class and add the new properties to hold the Commodity Code and Number values passed to Pipe Run from Pipeline.
Now you will modify the VALVE class and add a new property to hold the Commodity Code and Number values passed to Pipe Run from Pipeline. You will need this value later when defining the Valve Tag Type in the database. This property does not need to be displayed as it only used for writing a calculated value to the valve database table.
Now you will load and modify the OpenPlant_Supplemental_Tagging schema and modify the tag formats for Pipeline and Valve. Pipeline will be changed to have the new Commodity Code property in the tag and Valve will have the Pipelines Commodity Code and Number included in its tag.
You will modify the Tag Format for the AT_PROCESS and AT_HVALVE tag types in the Plant Project Database. This is performed with the Project Administrator. This will require the addition of new tag codes.
You will modify the Plant Project Database and add the new fields for Commodity Code in the PROCESS table and the combined Pipeline Commodity Code/Pipeline Number field to the Valve table. Instructions defined here are for a SQL Server format database.
The last part of the database configuration is to modify the Line List and Valve List views. You will modify the views to display the Commodity Code and related Commodity Code/Number fields.
Now that the schemas and database have related properties and fields and tag types are set in the database you will map the schemas changes to the database tables.
Based on an earlier post to the Plant Design & Engineering forum with a question on how to have a pipeline property appear as part of the tag for an inline valve I have created a How To document. The attached document will help you to define a Commodity Code on Pipeline that passes to the Pipe Run and the onto a valve placed in that line. The valve tag will be Area-Pipeline Commodity Code and Number-Valve Device Type Code and Valve Number
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!