How to Configure OpenPlant PowerPID for an AutoPLANT · PDF file ·...

OpenPlant PowerPID

How to Configure OpenPlant PowerPID for an AutoPLANT PID Conversion

Version 1.0

Initial Release May 15, 2014


Version 1.0 Copyright © 2010 Bentley Systems, Inc. May 15, 2014 of 35 Do Not Duplicate

Trademarks

Bentley, the “B” Bentley logo, MicroStation, ProjectWise and AutoPLANT are registered trademarks of Bentley Systems, Inc or Bentley Software, Inc.

Microsoft, Windows and SQL Server are registered trademarks of Microsoft Corporation.

AutoCAD is a registered trademark of Autodesk, Inc.

Oracle 11g, 10g and Oracle 9i are registered trademarks of Oracle Corporation.

Other brands and product names are the trademarks of their respective owners.

Copyrights

© 2010 Bentley Systems, Incorporated

No part of this document may be reproduced, translated, or transmitted in any form or by an means, electronic or mechanical, for any purpose without the express written permission of Bentley Systems, Inc, and then only on the condition that this notice is included in any such reproduction. No information as to the contents of this document may be communicated to any third party without the prior written consent of Bentley Systems, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of Bentley Systems, Inc. Bentley Systems, Inc. is not liable for errors contained in this document or for incidental or consequential damages in connection with furnishing or use of this material.

Including software, file formats, and audiovisual displays; may only be used pursuant to applicable software license agreement contains confidential and proprietary information of Bentley Systems, Inc. and/or third parties which is protected by copyright and trade secret law and may not be provided otherwise made available without proper authorization.

RESTRICTED RIGHTS LEGENDS

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Right in Technical Data and Computer Software clause in DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software – Restricted Rights in 48 CFR 52.227-19 as applicable.

Unpublished – rights reserved under the Copyright Laws of the United States and International treaties.

Downloaded files from Bentley-related Internet websites and files included on MySELECT CDs are subject to the legal terms, conditions, policies and usage restrictions posted on the website(s), which may significantly alter the rights granted in the license agreement included with these materials.



TABLE OF CONTENTS Document Version History............................................................................................................................................. 5

Software Versions .......................................................................................................................................................... 5

Modified and New Files ................................................................................................................................................. 6

Modified .................................................................................................................................................................... 6

New ............................................................................................................................................................................ 6

Tools used to perform edit ............................................................................................................................................ 6

Configuring OpenPlant PowerPID to Convert AutoPLANT PID ...................................................................................... 7

PART 1 - Limitations and Information of the AutoPLANT to OpenPlant Conversion ................................................. 8

Conversion Limitations .......................................................................................................................................... 8

AutoPLANT PID Conversion ............................................................................................................................... 8

AutoPLANT General Conversion Limitations ..................................................................................................... 8

AutoPLANT Specific Conversion Limitations .................................................................................................... 10

APPID Tower Tag Limitations ........................................................................................................................... 10

APPID Reducer Conversion Configuration ....................................................................................................... 11

Additional Conversion Information ..................................................................................................................... 11

APPID Class Mapping ....................................................................................................................................... 11

Mapping Considerations .................................................................................................................................. 11

Class Names starting with a Numerical Value ................................................................................................. 11

Class Names with a Dash ................................................................................................................................. 12

Block Names for Mapping................................................................................................................................ 12

Equipment ....................................................................................................................................................... 12

Valve, Control Valve, Flow Elements and PSV ................................................................................................. 13

Alternate Target Class mapping ....................................................................................................................... 13

Pressure Safety Valves ..................................................................................................................................... 14

Attribute Block text special cases .................................................................................................................... 16

Setting default associated item values ............................................................................................................ 17

Relationship Creation ...................................................................................................................................... 18

APPID and OPPID TAGTYPE mismatch and sync to database .......................................................................... 18

Do Not Convert block list ................................................................................................................................. 19

PART 2 – Configure OpenPlant to Convert Default AutoPLANT PIDs ...................................................................... 20

Preliminary Setup Requirements ......................................................................................................................... 20

Changes to the Project PCF File. ...................................................................................................................... 20

Other changes .................................................................................................................................................. 20

Graphics and DGNLib Files, Element Templates, Levels and Text Styles ............................................................. 20



DGNLib Files ..................................................................................................................................................... 21

Levels ............................................................................................................................................................... 21

Text Styles ........................................................................................................................................................ 21

Changes to Default Component Classes .............................................................................................................. 22

Modification to enable AT_EQTWR class ........................................................................................................ 22

Modify the OpenPlant_PID.01.0x.ecschema.xml Schema ........................................................................... 22

Modify the AutoPLANT_PID_CONVERSION.01.01.ecschema.xml Schema .................................................. 22

Modify the PIDProjectSymbols.dgnlib ......................................................................................................... 23

APPID Reducer Conversion Configuration ....................................................................................................... 24

Remove the Parser Regular Expression ....................................................................................................... 25

OPPID Tag Format change for Pipeline (Process Line) ..................................................................................... 25

Changing the Tag Format in OpenPlant_Supplemental_Tagging Schema ................................................... 26

PART 3 – Configure OpenPlant to Convert Custom AutoPLANT PIDs ...................................................................... 26

Adding Custom Components to OPPID Schemas............................................................................................. 26

Adding the new Parallel Slide Gate Valve .................................................................................................... 27

Adding the new Mist Eliminator .................................................................................................................. 28

Modifying the AutoPLANT PID Conversion Schema ........................................................................................ 30

Adding the mapping for the Parallel Slide Gate Valve ................................................................................. 30

Adding the Mapping for the Mist Eliminator ............................................................................................... 32

Notes ........................................................................................................................................................................... 35



Document Version History

Version Date Author Comments

1.0 05/15/2014 Tony DeRosa

Initial release. Compiled from Help Files, and executing the conversion process. Special thanks to Ed Krkoska and Denny Roberts for hammering through some of the user specific issues while working on a conversion with our AutoPLANT users.

Reviewed By Date Approved By Date

Software Versions

Application Name Version

OpenPlant PowerPID V8i SELECTseries 5 08.11.10.202 and higher

Process & Instrumentation V8i SELECTseries 5 08.11.10.182



Modified and New Files Modified

File Name

OpenPlant_PID

OpenPlant_PID_Supplemental_Imperial

OpenPlant_Supplemental_Tagging

AutoPLANT_PID_Conversion

New

File Name

NONE

Tools used to perform edit

File Name

OpenPlant PowerPID

Bentley Class Editor V8i

XML Text Editor

AutoPLANT PID SELECTseries 5 (For Reference only)



Configuring OpenPlant PowerPID to Convert AutoPLANT PID This document defines the preliminary steps required to convert an AutoPLANT PID drawing(s) to OpenPlant PowerPID drawings. The first part will define current limitations and what does not convert as well as a section on general conversion information. Part 2 will step you through configuring OpenPlant PowerPID in terms of minimal requirements to properly convert an out of the box AutoPLANT PID file. This includes minimum set up for tagging differences and a look at the DGNLib files to control proper graphical styles. Part 3 will cover configuring OpenPlant PowerPID to convert new, custom classes and components from an AutoPLANT PID environment and mapping these types of components so they too are converted. Please note that some of this information comes from the OpenPlant PowerPID Help file and is added here as a reference. Information from the help file will be marked as indicated in the margin to the left. Changes required that are not defined in the Help file and are additional requirements discovered during testing are identified as indicated in the margin to the left. This is an involved process and should not be done without the following skill set.

Full understanding of the OpenPlant PowerPID schemas.

Full use of the Class Editor.

Editing of XML files in a text editor.

An understanding of AutoPLANT PID and its underlying structure. You do not have to have a complete administrator’s skill set in AutoPLANT PID. No configuration inside of AutoPLANT will be performed.

This process will be using the existing Baytown Chemical dataset. It is being supplied along with this document. Included is data consisting of three workspaces and related databases, Baytown_OOTB – Baytown Chemical out of the box, Baytown_CUST – Baytown Chemical with customized AutoPLANT components and Baytown_CUST_UNC – Baytown Chemical with customized AutoPLANT components to be used as a backup. The combined zip file, Baytown_APPID_Conversion, is located here: https://bentley.sharefile.com/doremotedownload.aspx?type=direct&id=fib8874a-3d66-6823-9ce5-8531331e3566 It consists of the following:

PROJECT WORKSPACE ZIP FILE PACKAGED PLANT PROJECT ZIP FILE

Baytown Out of the box Baytown_OOTB_Workspace Baytown_OOTB

Baytown Customized Baytown_Cust_Workspace Baytown_Cust

Baytown Customized Backup Baytown_Cust_UNC_Workspace Baytown_Cust_UNC

https://bentley.sharefile.com/doremotedownload.aspx?type=direct&id=fib8874a-3d66-6823-9ce5-8531331e3566



PART 1 - Limitations and Information of the AutoPLANT to OpenPlant Conversion

Conversion Limitations AutoPLANT PID Conversion

The AutoPLANT PID conversion process differs from the PSPID and AXSYS conversions in the fact that both drawing and project database information are being converted to the OpenPlant format. When a drawing is converted, the database information is also converted at the same time. Each time you convert a different drawing from the same project database, the database will be further modified as well. So before converting an AutoPLANT PID project, there are some recommendations to follow:

Before starting the conversion it is recommended not to do a conversion on a live project. Use one of these suggestions to ensure original documents and data are not lost.

Backup all of your files. (This means the complete project - data and drawings.)

Work on an AutoPLANT project that is wither in a testing location or in a “non-production” environment.

Review all documentation before beginning the conversion process.

NOTE – The information above is why you are being provided three workspaces and an additional 4 packaged project. These are serving as your backups. Once the conversion is run on a specific file the conversion process will not be invoked when the same file is loaded in PowerPID a second time.

AutoPLANT General Conversion Limitations The following is a list of limitations currently in the AutoPLANT PID to OpenPlant PowerPID Ss5 conversions. These limitations will be addressed in future releases. Tag Formats: The APPID tag formatting may have to be changed to match OPPID tag format (calculated expression).This especially true for Pipelines: the format for OPPID contains 4 fields as APPID contains only 1 field. APPID stores the Alpha and numeric values in the PROCESS.PNUM field. Be careful doing a DB->DGN as these values could be updated and parsed correctly. Text Styles: RealDWG does not support text justification in a text style, does support a text justification defined in a PIDProjectTemplates.dgnlib. OPPID relies on the justification to be defined in a text style. The APPID conversion requires the use of OPPID Text Styles. The mapping allows for different text styles to be set on individual classes. Currently there is an overall text style set on the "APPID_CLASSES" class. Instrument bubble and bubble breaks: OPPID uses text background to sit on top graphics; this allows the text to "break" the instrument bubble. This is accomplished by the text overlay. The DGN format supports this but the DGN (ReadDWG) currently does not. NOTE: This is being investigated by development and may change soon. APPID Instrument bubble extra lines: The extra lines on Instrument bubbles will not be converted. These lines are drawn in APPID but have no identifying xdata. In the conversion they are not deleted and left as unintelligent elements. To have intelligent lines, they should be redrawn.



Components that have extents that are larger than the pipe run line break: These types of components will be converted but will not break the line. Future enhancements may add connection points. Do Not Convert block list: These types of components will be converted but will not break the line. Future enhancements may add connection points. Specialty Item and Tie-In: These components use a parametric bubble to draw. In APPID, the leader line is not defined in the xdata. Instruments (AT_INST) and bubble annotation for control valves have this variable defined correctly. The xdata for the leader line is stored in the -17004 field: ("AT_" (1070 . -17004) (1005 . "420")). AT_SPEC_ITEM and AT_TIEN do not have this xdata. There is no way to tell what the leader line is for AT_SPEC_ITEM and AT_TIEN. After conversion the leader line can be turned on. Instrument Lines: APPID Instrument lines have no intelligence. There is no xdata associated with instruments, for the Ss5 release they will remain native MS line elements. NOTE – This limitation means that the related instrument data in the properties of an instrument will not be displayed. If you select the instrument you will not see the controlling and controlled related instruments. Design History: Native MicroStation does not support design history in DWG mode. The drawing can be ”Saved As” DGN to get design history functionality. NOTE – Design History was excluded from PowerPID in the Ss5 time frame. The fix for this limitation will be applicable when Design History is added back to OpenPlant PowerPID. Control Valve Actuator List: Some actuators cause the pipe run break to be to too large. This is due to the fact that the overall extents are greater than the valve body. This list below contains actuators that will be created but separate from the control valve body.

DIFF-12

D-SPR-3

D-POS-4

C-POS-12

BACK-13

FRWD-10 Steam Trap: The APPID Steam Trap is defined as a valve. In OPPID Steam Trap is defined as a Piping Component. Piping Components do not have a DB mapping. In APPID, a Steam Trap has database values in the RUN_CONN table. This causes issues with the DB->DGN sync so the conversion mapping defines a Steam Trap as a generic, ”INLINE_VALVE”.



Nozzles: In the current mapping all nozzles will be replaced with the OPPID class graphics. This is done for manipulation purposes. Angle Valves: In the current mapping all angle valves will be replaced with the OPPID class graphics. This custom attribute is defined on the ”BASE_ANGLE_VALVE” class. Angle valves require connection points to have valid placement and manipulation. The cell graphics can be modified to match by updating the Valves.cel library. This would be done by locating the conversion class in the <TARGET_CLASSNAME>ANGLE_VALVE</TARGET_CLASSNAME> Locate that class in the OpenPlant_PID_Supplemental_Imperial.01.03.ecschema.xml file and modify the Cell Name: Pipeline Tag Format: The APPID and OPPID tag formats are different in the default base packages.

APPID tag format uses only one field: NUMBER (PID-P1, PID-P2).

OPPID format uses four fields: UNIT-SERVICE-NUMBER-SPEC: (U-S-0001-A1A) One of the tag formats needs to be changed to conform to the other. Not doing so will cause synchronization issues with the tag number. NOTE – More on this process to follow. In the delivered workspaces the OPPID tag format for process line has been changed to be NUMBER only to match the tag format from default APPID. Pipeline Flow Arrows Pipeline flow arrows do not convert and do not stay attached to the line on which they are placed. This means that if a line is moved in the PID after the conversion the flow arrows will also have to be moved. NOTE – See base conversion requirements Part-2 for more information on adjusting the default OPPID flow arrows. AutoPLANT Specific Conversion Limitations The following is a list of specific limitations currently in the AutoPLANT PID to OpenPlant PowerPID Ss5 conversions and how to work around them. APPID Tower Tag Limitations By default, when converting APPID drawings, the AT_EQTWR tag type is forced to use the AT_EQVES tag type. This is required for database synchronization and manipulation behavior because the behavior class associated with the TOWER class in OpenPlant PowerPID has a PID_VESSEL_PARAMETRIC instead of the PID_EQUIPMENT_CELL behavior class the AutoPLANT PID AT_EQTWR class needs. The result of this is seen when generating equipment reporting lists, the converted AT_EQTWR will be listed under the Vessels instead of Towers. However, modifications can be made to the OpenPlant_PID.01.03.ecschema.xml and AutoPLANT_PID_Conversion.01.01.ecschema.xml files before converting your APPID projects that will allow the converted AT_EQTWR tags to use a TOWER_CELL tag type. NOTE – How to resolve this issue is defined under configuration Part 2.



APPID Reducer Conversion Configuration The reducer component has some limitations with regards to auto orientation and a deficiency with updating the display text. Auto orientation of reducer will be addressed in a later release. The display text issue involves the removal of the inch mark (") from the reducer display during the conversion process. This issue can be solved by modifying the OpenPlant_PID_Supplemental_Imperial.01.03.ecschema.xml schema in the Bentley Class Editor. To get a consistent reducer size display when converting an APPID drawing, the Parser Regular Expression must be removed from the Calculated ECProperty Specification custom attribute. NOTE – How to resolve this issue is defined under configuration Part 2. NOTE – Reducers will convert but are not treated as OPPID reducers. They do break the line but if moved or deleted the lines will break in the new location nor will they mend in the old location. If a user intends on editing reducers he will have to delete them, fix the runs using the Run Manipulation Tools and then replace them with OPID reducers.

Additional Conversion Information The information below is given to provide a backbone of how the conversion system works and handles differences between the two applications. These are not limitations but methods created to bridge the differences between the two applications. APPID Class Mapping By default, all of the standard AutoPLANT PID (APPID) components have been mapped to their OPPID equivalent class. There are some restrictions involved when mapping components and these should be taken into consideration when mapping custom APPID components. Mapping Considerations The PowerPID application ships with an AutoPLANT_PID_Conversion.01.01.ecschema.xml which includes mappings of all of the default AutoPLANT PID classes. This schema is located in the following location: %LOCAL%\WORKSPACE\PROJECTS\OPPOWERPID_IMPERIAL\DATASET\SCHEMAS\. Conversion schema files are included for the OPPOWERPID_METRIC and OPPOWERPID_ISO projects as well. Any Custom Classes will need to be mapped in the respective conversion schema using the Bentley Class Editor. There are certain naming conventions for classes which must be followed in order to convert an APPID class. Look to the sections below for specific mapping considerations as it applies to the different types of APPID components: Class Names starting with a Numerical Value EC Schemas do not allow a class name to start with a numeric value. Since APPID has block names that start with numeric values such as 22300, 32500, etc., the conversion alternately searches for the prefix AP_ on all classes names. So any APPID class that starts with a numeric value MUST have the "AP_ prefix as shown below.



All of the standard APPID components have been mapped already to include the "AP_" prefix. This will need to be added to any custom components that have a class name that starts with a numeric value. Class Names with a Dash The OpenPlant EC Schema files do not allow a class name to have a dash in the name. In APPID, certain block names have dashes in them such as BLIND-0 and 8BLIND-C. To accommodate this, the conversion alternately searches for any dashes and replaces them with underscores on all class names. So any APPID class that has a dash MUST be replaced with an underscore as shown below. BLIND_0, AP_8BLIND_C As seen below the 8BLIND-C has a combination of Numeric starting value and a dash. So the “AP_” prefix and underscore to replace the dashes are applied.

Block Names for Mapping The Conversion uses these block names to map components. The data storage for APPID to identify a unique component is ambiguous at best. This is complicated by how APPID stores specific types. Equipment Equipment is by far the most diverse in the APPID setup. There is several equipment Tag Types that allow for specific types to be set. OPPID has very specific classes for equipment. The block name and the EINIT1 field allow for these to be set.



Valve, Control Valve, Flow Elements and PSV These inline components have signally defined TAG Types to handle multiple types of components.

Valves: AT_HVALVE

Control Valves: AT_CVALVE, AT_PSV

Flow Elements: AT_INST_FO, AT_INST_ORI, AT_INST_CS. It is not valid to rely on this one attribute to do the mapping. The VINIT1, IINIT1 could be used, but this field is very unreliable. The value in this field could change depending on the end condition, whether or not it is a Control valve and other circumstances. An Example of this is a Gate and Gate Control valve with an end condition: GATE, GATE1, GATE2, GATE3, CGATE, CGATE1, and CGATE4. Multiple mappings would have to be created, and multiple records added by users to cover all of these potential types. To remove these variances the block name inserted is used. See Alternate Target Class mapping below. Alternate Target Class mapping The ALTERNATE_SEARCH_TAG_TYPES list, which can be found under the Supports Lists node in the Bentley Class Editor, defines Tag types to be used in determining whether or not an Alternate mapping is to be used. Each mapping has the potential of having an alternate Class and property mapping defined. This is used for Valves and Control valves. The same block name used for a valve is used for a control valve.

Example of a Gate Valve:

1. A Gate Valve with the name of 32500 is inserted APPID. 2. The conversion process is run and this component is processed. 3. This component has a Tag Type of AT_HVALVE. 4. The conversion finds the mapping class "AP_32500." (The 'AP_' prefix has been added in the conversion

schema.) 5. The AT_HVALVE is not defined in the ALTERNATE_SEARCH_TAG_TYPES list. 6. OPPID uses the Target Class of GATE_VALVE.



Example of a Gate Control Valve: 1. A Gate Control Valve with the name of 32500 is inserted APPID. 2. The conversion process is run and this component is processed. 3. This component has a Tag Type of AT_CVALVE. 4. The conversion finds the mapping class "AP_32500." 5. AT_CVALVE is defined in the ALTERNATE_SEARCH_TAG_TYPES list.

(This flags this component to use the Alternate Target class.) 6. OPPID uses the Alternate Target Class of GATE_CONTROL_VALVE.

Pressure Safety Valves APPID PSV valves have all the same characteristics as an APPID Control Valve. The only difference is the TAG_TYPE: AT_PSV. OPPID PSV valves are data change components (two Pipe Runs). APPID PSV valves are single way components (single connection to Pipe Runs). APPID Angle PSV valves can be linked to two Pipe Runs, but only in the RUN_CONN table. No run terminators are used. An OPPID PSV is a Data Change Component while an APPID PSV is not. To accommodate this in OPPID, new classes have been added to OpenPlant_PID.01.03.ecschema.xml. New OPPID Classes: INLINE_PRESSURE_SAFETY_VALVE_APPID GATE_PRESSURE_SAFETY_VALVE_APPID ANGLE_PRESSURE_SAFETY_VALVE_APPID GLOBE_PRESSURE_SAFETY_VALVE_APPID BALL_PRESSURE_SAFETY_VALVE_APPID



BUTTERFLY_PRESSURE_SAFETY_VALVE_APPID NEEDLE_PRESSURE_SAFETY_VALVE_APPID PINCH_PRESSURE_SAFETY_VALVE_APPID PLUG_PRESSURE_SAFETY_VALVE_APPID ROTARY_PRESSURE_SAFETY_VALVE_APPID DIAPHRAGM_PRESSURE_SAFETY_VALVE_APPID The INLINE_PRESSURE_SAFETY_VALVE_APPID class inherits from the pid:BASE_CVALVE_INLINE class which allows for single inline behavior. The angle PSV valve inherits from the pid:BASE_CVALVE_ANGLE class. To map these PSV's requires the mapping class PRESSURE_SAFETY_VALVE_MAPPING_LIST which is already defined in the AutoPLANT_PID_Conversion.01.01.ecschema.xml file. As explained in Alternate Target Class Mapping and Block Names for Mappings sections above, one APPID block can be used for multiple Tag Types. Do not to alter these existing custom attribute structures which several applications use, this mapping is a supplement to define a PSV valve. The mapping process works as follows:

1. The block name "AP_32500" is found on a component in the conversion process. (The Tag Type of AT_PSV is defined for this component.)

2. This Tag Type ( AT_PSV) is defined in the ALTERNATE_SEARCH_TAG_TYPES list. 3. The Alternate Tag class is used which is GATE_CONTROL_VALVE. 4. The PRESSURE_SAFETY_VALVE_MAPPING_LIST is then checked to see if there is a match. (There is a

match as seen below.) 5. The match returns the class name of GATE_PRESSURE_SAFETY_VALVE_APPID 6. This class is used to create the correct OPPID PSV component.



Attribute Block text special cases Sometimes there is an attribute that does not have a database field name such as the size annotation on a valve etc. In this case, you can add the attribute name to the specific mapping. Valves: The PSZ is stored on the attribute and not in any mapping. The PSZ value is from the PIPERUN and in APPID that was filled out with a lisp function (valve_size). This is done mostly for valves. If you check the annotation properties you'll find they are stored on the annotation and not on the intelligent APPID component. Need to do this here because the mapping name "PSZ" is on the attribute text. Specialty Items and Tie-Ins (AT_SPEC_ITEM, AT_TIEIN): These components do not have specific Database fields that match the Text attribute. In the SPEC_ITEM table there are no STYP or SNUM columns. In the TIE_IN table there are no TTYP or TNUM columns. This list allows for these fields to be matched and updated. Examples of Attribute Block special cases:



Setting default associated item values Add the custom attribute to the component that would use the default associated item. When set the converted component would use the default associated item. See below.



NOTE – This is used on AT_PROCESS because the AT_PROCESS component in APPID does not store the PLANT AREA in the database for the pipeline. So the rule is to use this custom attribute when the related associated item property is not stored on the record in the respective table. Relationship Creation APPID_RELATIONSHIP_CLASS_MAPPING_LIST contains the list of relationships that will be created during the conversion process based on tag types and database storage foreign keys: Assigns relationships to components based on tag type and database storage foreign keys. In the image below the “Foreign Key to be queried for” of NEQUIP comes from the Plant Project Schema 01.04 AutoPLANT_PIW schema. Locate the EQUIPMENT_HAS_NOZZLE relationship class and note the “Source Key” field.

APPID and OPPID TAGTYPE mismatch and sync to database APPID might have a tag type that does not match what is defined in OPPID database mapping. EXAMPLE: A FURNACE in APPID is defined as AT_EQEXC, but in OPPID it is defined as AT_EQUIP. When a FURNACE is placed in an APPID drawing, the KEY_LINK, EQP_LNK and TAG_REG tag type values are set to AT_EQEXCH. However, OPPID needs a ”FURNACE” class to be defined with a Tag type of AT_EQUIP. The Force_TagType value custom attribute allows AT_EQUIP to be set in the TAG_TYPE fields thereby forcing the FURNACE to use the AT_EQUIP tag type. This is needed for database syncing with no error.



Do Not Convert block list This list is used to identify block parts to not convert. This is used for Control valve and actuators. The actuator can make the extents larger the valve. This causes the break to be larger than the inrun component. Any custom block name that will not convert should be added here.



PART 2 – Configure OpenPlant to Convert Default AutoPLANT PIDs In this part you will learn how to configure OpenPlant PowerPID to convert an out of the box AutoPLANT PID. This is the minimum level of configuration necessary in order to convert a PID drawing.

Preliminary Setup Requirements Preliminary setup requirements are defined below. These have already been configured in the workspaces provided and are listed here for reference. NOTE – The path in the PCF file will have to be adjusted to match your AutoPLANT project location. Changes to the Project PCF File.

1. Load the respective PCF file into a text editor. 2. Locate the MS_DEF variable and set this to match the location of your plant project installs.

MS_DEF < C:\PlantProjects\Baytown_Cust\P&ID\Drawings/

3. Locate the “#Default value for Border” variable and change it as shown below. # Default value for border BMF_BORDER = None

4. In order to use the default PID Project specifications you need to adjust the OpenPlant Spec configuration variables. Make the changes as indicated below. Modify: OPM_SPECPLUGIN_CURRENTSOURCE = PDW Add: OPM_SPECPLUGIN_PDW_SPECFOLDER = C:\PlantProjects\Baytown_Cust\Specs NOTE – The path to the specs folder will need to change to match your install.

5. Add the lines below to the project PCF file. This will suppress the standard OpenPlant PowerPID startup dialog. # To Suppress the default Project Properties Dialog when starting OPPID. PID_SUPPRESS_STARTUP_DIALOG=1

6. Save the file. Other changes REFERENCE THE HELP FILE FOR SPECIFIC REQUIREMENTS FOR METRIC PROJECTS.

Graphics and DGNLib Files, Element Templates, Levels and Text Styles AutoPLANT PID relied on a PID-SUP.lsp routine to set layers, color, line types and the other settings. OpenPlant

PowerPID relies on DGNLib files to do the same. Based on the default out of the box settings for AutoPLANT PID

changes need to be made to the default files.



The workspaces that go along with this document already incorporate these changes but they are defined here for

your reference.

DGNLib Files The dgnlib files contain tasks, levels, templates and other in drawing settings. To match layer name to level names the PIDProjectTemplates.dgnlib must be edited. PowerPID uses multiple Element Templates which contain multiple element configurable attributes. Below is a chart that defines the default OPPID DGNLib templates and their settings along with the new setting required to match the settings defined in an AutoPLANT PID-SUP file. This requires some new levels to be generated and have these level properties adjusted accordingly. To set these

to match new levels were created and the Element Templates were adjusted to use them.

The three spreadsheets can be found here:

https://bentley.sharefile.com/doremotedownload.aspx?type=direct&id=fidcce01-2ff9-0045-57a4-0ad23a22e743

Templates.xlsx

Levels The changes to the level structure are defined in the attached spreadsheet. The new levels were created to match that of an out of the box AutoPLANT PID level structure.

Levels.xlsx

Text Styles The dgnlib file also contains the text styles used by OpenPlant PowerPID. These needed to be altered to use the AutoCAD ROMANS font. See the attached spreadsheet that outlines the changes made to the text styles.

TextStyles.xlsx

https://bentley.sharefile.com/doremotedownload.aspx?type=direct&id=fidcce01-2ff9-0045-57a4-0ad23a22e743



Changes to Default Component Classes The default classes for AutoPLANT PID and OpenPlant PowerPID are a match in most regards except for a Tower class. This requires special adjustments to be made in order to properly sync to the database after being converted to OpenPlant PowerPID. Modification to enable AT_EQTWR class Because modifying the TOWER class in OpenPlant PowerPID standard application would cause compatibility issues with previous releases, the SS5 release of PowerPID includes a TOWER_CELL class which can be modified to accommodate the AT_ Because a change to the TOWER class in OpenPlant_PID.01.03.ecschema.xml schema would cause a compatibly issue with previous release, modifications to the TOWER hierarchy can be made to the schemas and DGNLIB to support the use of the AT_EQTWR tag type. NOTE - This can only be done if this is a new implementation of OpenPlant PowerPID or no TOWERS have been placed in existing drawings.

Modify the OpenPlant_PID.01.0x.ecschema.xml Schema

1. Open the OpenPlant_PID.01.03.ecschema.xml schema in a text editor. Schema files are located in the ...\WorkSpace\Projects\%PROJECT%\Dataset\schemas DIRECTORY.

2. Find the TOWER and TOWER_CELL classes, (they should be together.) 3. Replace TOWER and TOWER_CELL classes with the following:

<ECClass typeName="TOWER" description="A recepatacle, container or part of a structure designed and manufactured to keep solids or liquids." displayLabel="Tower" isDomainClass="True"> <BaseClass>VESSEL</BaseClass> <BaseClass>op:TOWER</BaseClass> </ECClass> <ECClass typeName="TOWER_PARAMETRIC" description="A recepatacle, container or part of a structure designed and manufactured to keep solids or liquids." displayLabel="Tower Parametric" isDomainClass="True"> <BaseClass>TOWER</BaseClass> <BaseClass>PID_VESSEL_PARAMETRIC</BaseClass> </ECClass> <ECClass typeName="TOWER_CELL" description="A recepatacle, container or part of a structure designed and manufactured to keep solids or liquids. Used in APPID Conversion" displayLabel="Tower Cell" isDomainClass="True"> <BaseClass>TOWER</BaseClass> <BaseClass>PID_EQUIPMENT_CELL</BaseClass> </ECClass>

4. Save the changes and close the file.

Modify the AutoPLANT_PID_CONVERSION.01.01.ecschema.xml Schema

1. Open the AutoPLANT_PID_Conversion.01.01.ecschema.xml in the Class Editor. Schema files are located in the ...\WorkSpace\Projects\%PROJECT%\Dataset\schemas DIRECTORY.

2. Find the AT_EQTWR class. 3. Remove the Force_TagType custom attribute (Displayed in red below).



4. Save the changes and close the file.

Modify the PIDProjectSymbols.dgnlib Once you have modified the schema files, you will need to modify the TOWER Key-in command in the PIDprojectSymbols.dgnlib file.

1. Launch PowerPID and when prompted with the Open File dialog navigate to and open the PIDProjectSymbgols.dgnlib file.

This file is located in the ...\Workspace\Projects\%PROJECT%\Dataset\dgnlibs directory. 2. Select Workspace > Customize to display the Customize dialog. 3. In the Tools tab, under the User Tools node, navigate to the Equipment > Tanks & Vessels > Tower

symbol.



4. In the Command Data section change the Key-in value to: pid insert OpentPlant_PID TOWER_PARAMETRIC

5. Close the dialog when finished. APPID Reducer Conversion Configuration The reducer component has some limitations with regards to auto orientation and a deficiency with updating the display text. NOTE – The auto orientation of the reducer will be addressed in a later release.

The display text issue involves the removal of the inch mark (") from the reducer display during the conversion

process. This issue can be solved by modifying the OpenPlant_PID_Supplemental_Imperial.01.03.ecschema.xml

schema in the Bentley Class Editor.

To get a consistent reducer size display when converting an APPID drawing, the Parser Regular Expression must be

removed from the Calculated ECProperty Specification custom attribute. See the example below:



Remove the Parser Regular Expression

1. Open Bentley Class Editor. 2. Load the OpenPlant_PID_Supplemental_Imperial.01.03.ecschema.xml schema.

This file is located in the %Local_Install%\WorkSpace\Projects\%Project%\Dataset\schemas directory. 3. Expand the Classes node and locate the PIPE_REDUCER class. 4. Click the Properties tab and select the SIZE property.

5. In the Calculated ECProperty Specification attribute, remove the value in the Parser regular expression field.

6. Save the changes and exit. OPPID Tag Format change for Pipeline (Process Line) The tagging schema: OpenPlant_Supplemental_Tagging.01.02.ecschema.xml would be modified to match existing APPID values. The APPID tagging definition codes can be found in the TAG_TYPE table in Schema.Mdb Most all of the tagging is similar with the exception of the Pipeline tag (APPID Process tag). OPPID uses the PIPING_NETWORK_SYSTEM for its tagging. The tag format must be changed in either the OPPID system or the APPID system. The Pipeline tagging format differs between OPPID and APPID in the following ways:

OPPID Pipeline is made up of four parts: Unit-Service-Number-Specification.

APPID Pipeline is made up of one part: Number



Changing the Tag Format in OpenPlant_Supplemental_Tagging Schema

1. In the OpenPlant_Supplemental_Tagging schema find the PIPING_NETWORK_SYSTEM class. On that class find the NAME property.

2. Change the ECExpression and the Parser Regular Expression as shown below.

3. Save the schema and exit the Class Editor.

PART 3 – Configure OpenPlant to Convert Custom AutoPLANT PIDs In this part you will learn how to configure OpenPlant PowerPID to convert a customized AutoPLANT PID. This requires Part-2 above to be configured first. This will include new mappings for a new inline valve (Parallel Slide Gate Valve) and a new piece of equipment (Mist Eliminator). Both new components have already been added to the PIDs in the Baytown_CUST workspace and project. In this part you learn how to add the components to the AutoPLANT PID Conversion schema. The addition of the components to the root OpenPlant PID schema is not covered but will be illustrated for the purpose of making the additions to the AutoPLANT Conversion schema clearer. Customization of AutoPLANT PID is not covered. Adding Custom Components to OPPID Schemas Below are the two components that were added to the AutoPLANT environment as custom components. I selected one inline component, the Parallel Slide Gate Valve and one piece of equipment, the Mist Eliminator. The Mist Eliminator also has a custom attribute tag block XDE_MIS which must be included in the mapping schema.



Before mapping the custom AutoPLANT PID components new component classes had to be created in OpenPlant PowerPID. This was done following standard procedures to add the new classes.

Adding the new Parallel Slide Gate Valve A new class was created under Plant Base Object > Named Item > Device > Piping Component > Fluid Regulator > Valve > Inline Valve > Gate Valve class. See below and note that the new class PSLIDE_GATE_VALVE was assigned a new cell.



Adding the new Mist Eliminator A new class was created under Plant Base Object > Named Item > Device > Equipment > Fluid Transform Device > Filter > class. See below and note that the new class MIST_ELIMINATOR was assigned a new cell…

The custom component in AutoPLANT was created with a custom tag type of AT_EQMIS. As a result the Database

mapping had to be modified to map the new component and tag type to the database.

The OpenPlant_PID schema was loaded and the Database Mapping loaded and the new class was mapped as

shown below.

NOTE – As a reference TANK was used to determine property mappings.



Modifying the AutoPLANT PID Conversion Schema In this section are the detailed steps to map the new classes added to the OpenPlant schemas to the custom classes coming in from AutoPLANT PID project. NOTE – The included workspace, Baytown_CUST, has already been modified as shown below, the procedure is explained here for clarity.

Adding the mapping for the Parallel Slide Gate Valve

1. Load the Class Editor. 2. Load the AutoPLANT_PID_Conversion schema located in the

“…workspace\Projects\Baytown_CUST\Dataset\schemas” directory. 3. Browse to the AT_HVALVE class. Right click on the AT_HVALVE class and from the context menu pick Add

Derived Class. 4. Add the new Parallel Slide Gate valve as shown below. You will also have to add the Class Mapping

Custom Attribute and fill it in as shown. NOTE – The class Name MUST MATCH the symbol name from AutoPLANT PID. In this case the valve was added as PSLIDE.



5. The Class Mapping Custom Attribute fields are explained in the tables below.

Field Value Description

Target Class Name PSLIDE_GATE_VALVE Is the description of the OpenPlant PID class for the new valve.

Property Mapping Class Name VALVE_MAPPING This is the class that will be used to determine what properties will be mapped from the AutoPLANT component to the new OpenPlant component.

Alternate Property Mapping Class Name

INSTRUMENT_MAPPING This is the class that will be used to determine what properties will be mapped from the AutoPLANT component to the new OpenPlant component if the custom valve is being used as a Control Valve.




Alternate target class GATE_CONTROL_VALVE This defines the alternate class to use if the valve is being used as a control valve.

InRun flag True Identifies the component as an inline components and should be flagged accordingly.

6. Save the schema.

Adding the Mapping for the Mist Eliminator

1. Continuing in the Class Editor and the AutoPLANT_PID_Conversion schema. 2. Browse to the AT_EQUIP class. Right click on the AT_EQUIP class and from the context menu pick Add

Derived Class. 3. Add the new MISTELIM class as shown below. You will also have to add the Class Mapping Custom

Attribute and fill it in as shown. NOTE – The class Name MUST MATCH the symbol name from AutoPLANT PID. In this case the equipment was added as MISTELIM.



4. The Class Mapping Custom Attribute fields are explained in the tables below.


Target Class Name MIST_ELIMINATOR Is the description of the OpenPlant PID class for the new piece of equipment.

Property Mapping Class Name EQUIPMENT_MAPPING This is the class that will be used to determine what properties will be mapped from the AutoPLANT component to the new OpenPlant component.



5. Browse to the Classes > Support Lists > AutoCAD Attribute Block Names class. 6. To the String Collection custom attribute add the new XDE_MIS attribute block name that was created as

a custom attribute block in AutoPLANT PID when the Mist Eliminator was added. The system uses this to map the actual on drawing tag to the properties that make up the tag. NOTE – We did not have to do this for the Parallel Slide Gate Valve because it used the same default XDHV as the standard valves in AutoPLANT PID.

7. Save the schema.



Notes

How to Configure OpenPlant PowerPID for an AutoPLANT · PDF file ·...

Documents

Transcript of How to Configure OpenPlant PowerPID for an AutoPLANT · PDF file ·...