How to Create Multi-Line Process Line

OpenPlant PowerPID

How to Create Multi-Line Process Line

Version1.0

January 19, 2019

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.

Document Version History

Version / Date / Author / Comments
1.0 / 06/01/2011 / Tony DeRosa / Initial Release
Reviewed By / Date / Approved By / Date

Software Versions

Application Name / Version
OpenPlant PowerPID / 08.11.08.22 and up
Bentley Class Editor / From PowerPID install

Table of Contents

Assumptions prior to starting

OpenPlant Power PID and Schema Editing

Class and Project Information

Objective

General Overview of Required Administrative Task

OpenPlant PowerPID Schemas

Creating New Line Style

Editing the PID_LineStyles_ANSI.rsc file

Adding New Line Type

Editing the OpenPlant_PID Schema and adding the new Duct Class

Adding New Class for Duct Line Type

Adding New Duct Class to the List for Line Types

Editing the Project DGNLIB files

Modifying the PIDProjectTemplates.dgnlib

Modifying the PIDProjectSymbols.dgnlib

Testing the Results

Creating a P&ID and Testing the New Line Type

Create the new line

Notes

Assumptions prior to starting

OpenPlant Power PID and Schema Editing

Class and Project Information

  • A general understanding and use of the Class Editor.
  • Editing of schemas in XML file editor a plus but not required.

Note:A good understanding of OpenPlant PowerPID schemas is also assumed.

Objective

This session will cover the creation of a new line type to be used as a PID Process Line. This will be of a Multi-Line style line type representing “duct” in lieu of pipe. For the sake of this exercise the new line type will write to the standard PROCESS table of the plant project database but could be synchronized to a new table if necessary. As a minimum in this procedure we will add a unique property to this class of component so that despite being written to the default process table, the lines that use this class can be easily segregated in reports.

General Overview of Required Administrative Task

OpenPlant PowerPID Schemas

  • Create the new line style in the PID_LineStyles_ANSI.rsc file.
  • Add a new class for the line in OpenPlant_PID schema and OpenPlant Supplemental schema
  • Add this line to the Pipelines list in the schema.
  • Modify the PIDProjectTemplates.dgnlib and add a new Level – and set the desired parameters
  • Modify the PIDProjectTemplates.dgnlib and add a new Element Template for the new line.
  • Modified the PIDProjectSymbols.dgnlib to have the new line in the task interface.

Creating New Line Style

Editing the PID_LineStyles_ANSI.rsc file

Adding New Line Type

  • Load the OpenPlant PowerPID
  • Load the project workspace and create a dummy drawing in which to make the new line type.
  • From the menu select Element -> Line Styles -> Edit.
  • In the Line Style Editor use File -> Open and browse and load the PID_LineStyles_ANSI.rsc file located in the project workspace\dataset\symb directory.
  • From the Menu select Edit -> Create -> Compound.
  • In the dialog and in the space as shown below name the new compound line component DUCT_ALL.
  • In the Sub-Components section of the dialog, pick on the Insert button.
  • In the Select Component dialog browse the list and look for the line of Type of Internal and a Description of Default solid line. Select OK.

  • Back in the Sub-Components section of the dialog make sure the line you just added is selected and enter an Offset value of 0.0625. This will be the “top” line in the compound line style.
  • Repeat the process and select Insert in the Sub-Components section, select the line of TypeInternal and Description of Default solid line. Select OK. This line will not get an offset as this will be the “middle” line in the compound line style.
  • Repeat the process again adding the same Default solid line but this time enter in an Offset of

-0.0625. NOTE – this is a NEGATIVE offset.

  • From the Line Style Editor dialog menu select Edit -> Create -> Name.
  • In the space shown below enter Duct.

  • From the menu in the Line Style Editor dialog select the Duct name in the Style panel and select the Compound - DuctAllentry in the Components panel.
  • From the Line Style Editor menu select Edit -> Link.

  • From the Line Style Editor dialog menu select File -> Save and then File -> Exit.

Editing the OpenPlant_PID Schema and adding the new Duct Class

Adding New Class for Duct Line Type

  • Load the Class Editor
  • From within the Class Editor load the OpenPlant_PID.01.02.ecschema.xml file. (Your version of the schema may vary depending on version of OpenPlant PowerPID being run.)
  • Select the OpenPlant_PID schema in the left hand panel.
  • Right click on the name and from the context menu select Supplement Schema…
  • In the Specify Supplemental Schemas dialog use the Add button and browse to the project workspace schema directory (same directory as the schema you are editing) and pick the OpenPlant_PID_Supplemental_Imperial.01.02.ecschema.xml file. Pick Open.
  • Back in the Specify Supplemental Schema dialog select OK. The schema is now supplemented.
  • Expand the tree and locate the PIPING_NETWORK_SYSTEM class (display label Pipeline).
  • Right click on this class and from the context menu select Add Derived Class.
  • Name the new class as shown below. Add the two Custom Attributes and fill them as shown.

NOTE – The Element Template name of Piping\Pipeline\Duct_Pipeline has not yet been added to the element template in the DGNLIB file. You will do this later. This name and syntax is CRITICAL.

  • Switch to the Properties tab of the new class.
  • From the right hand panel select Add… and then New.

  • Name the new Property as shown below. Also add the custom attribute to set a default value for the property.

NOTE – Make sure to set the correct schema location for the attribute. Note the schema in the picture above and below.


  • Save the schema.

Adding New Duct Class to the List for Line Types

  • Continuing in the Class Editor.
  • In the left hand panel browse the schema and locate the PIPELINE_LIST class (display label Pipeline list) Select the class.
  • In the right hand panel, Class tab locate the custom attribute Class Name Display List.
  • Edit this to include the new DUCT_LINE class. Right click on the “Items” and from the context menu select Add element. Add the DUCT_CLASS as shown below.
  • Save the schema.
  • Exit the Class Editor.

Editing the Project DGNLIB files

Modifying the PIDProjectTemplates.dgnlib

  • Launch OpenPlant PowerPID.
  • When prompted to select a file switch the file type to DGN Library Files (*.dgnlib) and browse to the project workspace\dataset\dgnlibs directory.
  • Select the PIDProjectTemplates.dgnlib file.
  • When the file loads from the menu select Settings -> Levels -> Manager.
  • In the Level Manager dialog add a new level named Duct Pipeline.
  • Set the Color as desired (red for example) and set the Style and Weight to 0.
  • Close the LevelManager dialog.
  • From menu select Element -> Element Templates.
  • In the Element Templates dialog expand the tree to PIDProject Templates.dgnlib -> Piping -> Pipeline.
  • Right click on the Pipeline node and from the context menu select New Template.
  • Name the Template as shown below. Pay attention to all settings especially Line Style Scale.


NOTE – This name must match the template name created back in the schema editing section.

  • Exit the DGNLIB file.

Modifying the PIDProjectSymbols.dgnlib

  • Launch OpenPlant PowerPID.
  • When prompted to select a file switch the file type to DGN Library Files (*.dgnlib) and browse to the project workspace\dataset\dgnlibs directory.
  • Select the PIDProjectSymbols.dgnlib file.
  • From the menu select Workspace -> Customize.
  • In the Customize dialog, Tools tab, expand the tree until you locate Major Pipeline.
  • Right click on Major Pipeline and from the context menu select Copy.
  • Pick on the Piping node, right click and from the context menu select Paste.
  • Select the newly copied tool and rename it to Duct Pipeline.
  • With the new Duct Pipeline tool selected pick in the Properties category, Key-in field and change the class name to duct_line. (Matches the class name defined for the new line type in the schema.)
  • Pick on the Balloon Text field and change this to Duct Pipeline.

NOTE – The icon needs to be created and changed in the task. This can be accomplished using an icon creation tool. This is not covered in this document.

  • In the right hand panel expand the Task category.
  • Expand the tree and locate the Piping Task.
  • From the left hand panel drag and drop the Duct Pipeline tool over and place it under the Piping Task in the right hand panel.
  • Exit the DGNLIB file.

Testing the Results

Creating a P&ID and Testing the New Line Type

Create the new line

  • Load OpenPlant PowerPID.
  • Create a new drawing or load an existing drawing.
  • Apply a Plant Area value.
  • From the Task select Process > Piping > Duct Pipeline.

NOTE – The icon will match the existing Major Pipeline because we have not modified the icon.

  • Set the parameters as required and draw the line.
  • Add a few items in and on the line as shown below to verify it is working correctly.

Notes

Version 1.0 / Copyright © 2010Bentley Systems, Inc.
January 19, 2019 / Page 1 of 16 / Do Not Duplicate