Pipework Design User Guide

Pipework Design

User Guide

DisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaimany and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct described in this publication may be incorporated into any third-party software, product,machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective licence agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries 2007

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthoriseduse of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solutions Ltd

Pipework Design User Guide

Contents Page


Pipework DesignRead this First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Scope of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1About the Tutorial Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

How the Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Further Training in Using PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:3

Introducing AVEVA PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Introducing the Structure of PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Strengths of PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1PDMS Piping Network Design Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2

Setting Up the PDMS Database Hierarchy . . . . . . . . . . . . . . . . . . . . 3:1How PDMS Stores Design Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1PDMS Design Data Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

Logging In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3PDMS Startup Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Creating some Administrative Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:4

Creating Some Equipment Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1How Equipment Items are Represented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1

12.0© 2007 AVEVA Solutions Ltd i


Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Using Predefined Templates for Standard Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

Creating a Storage Tank to a Standard Design. . . . . . . . . . . . . . . . . . . . . . . . . . 4:3Adding a Nozzle to the Storage Tank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:8Viewing the Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9Defining what Appears in the View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:9Manipulating the Displayed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:11

Creating Some More Equipment Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13Creating a Vertical Vessel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:13Naming the Nozzle in the Base of the New Vessel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:14Creating a Standard Design Pump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:15Changing the Orientation of an Equipment Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:16Tidying Up Afterwards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:18

Routing a Sequence of Piping Components . . . . . . . . . . . . . . . . . . 5:1Design-to-Catalogue Cross-Referencing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1How Piping Networks are Represented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1Pipes and Branches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Piping Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2

Starting the Pipework Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3Setting a Default Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3Creating a Simple Pipework Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:4Modifying Pipe Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:10

Creating a Second Pipework Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:32Quick Pipe Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:39QPR Facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:39Cases of Ill-defined Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:40Entering and Leaving QPR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:40The Pipe Routing Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:41The Extend Route Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:41Nudging the Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:43Cardinal Direction Handles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:44Free Rotation Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:44Direction and Rotation Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:45Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:52Popup Menus on the QPR Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:55Hotkeys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:59

Deleting Pipe Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:65

12.0© 2007 AVEVA Solutions Ltd ii


Pipework Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1Pipework Component Bore and Specification Modification . . . . . . . . . . . . . . . 6:1Modify Components Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:2Component Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:3Modifying Component Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:5Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6Choosing a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:6Multiple Component Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8Modifying Component Bore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:8Modifying Insulation and Tracing Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:11

Pipe Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:12Multiple Mode Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:14Splitting Pipes with a Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:16Single Mode Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:22Component Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:23Feature Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:25

Checking and Outputting Design Data . . . . . . . . . . . . . . . . . . . . . . . 7:1Checking for Design Data Inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1Design Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2

Checking for Clashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4Obstruction Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4Extent of Clashing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:4Clash Detection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:5

Generating a Data Output Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:6Generating Isometric Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:7

Automatic Pipe Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Automatic Pipe Routing using PDMS Router . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1Basic Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:9Positioning and Locking Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:19Creating and Using Routing Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:27Using Routing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:32Creating and Using Routing Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:36Creating and Using Pipe Racks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:44Pipe Packing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:55Importing a P&ID File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:57

Automatic Pipe Routing Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:59

12.0© 2007 AVEVA Solutions Ltd iii


Routing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:59Creating and Editing Routing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:75Placing Pipes on Racks and Planes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:81Importing Data from P&ID Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:86Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:92Special Router Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:99

Pipework Spooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Database Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:13D Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Spooling Volume Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Drawing Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2

Setting Up the Database Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3Logging In to Start a SPOOLER Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3Creating Some Administrative Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:4

Controlling the 3D View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:5Setting up a 3D View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:6Manipulating the Displayed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:8Saving and Restoring a View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:9

Preparing the Site for Spooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:10Checking the Design Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:10Inspecting the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:11Measuring the Pipe Lengths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:12Inserting Welds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:13Splitting a Tube with a Weld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:15

Spooling the Piping Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Pipework Spooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Creating Spool Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Numbering the Spool Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:18Selecting Adjacent Field Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:18

Advanced SPOOLER Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:19Checking the Spool Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:19Selecting the Numbering Update Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:20Changing the Shop/Field Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:22Forcing a Spool Break at a Joint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:23

12.0© 2007 AVEVA Solutions Ltd iv


Outputting Spool Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:24Plotting the Spool Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:24Isometric Drawing Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:26Drawing Annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:27

Pipe Piece and Pipe Spool Production Checks . . . . . . . . . . . . . . . 10:1Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Pipe Piece . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1Pipe Spool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1

Pipe Production Checks Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2Generating Spools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:5

Options on the Pipe Production Checks Form . . . . . . . . . . . . . . . . . . . . . . . . . 10:8Setting Up Production Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:10Define Auto-Resolve Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:11Define Auto-Naming Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:11Define Stock Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:12Running a Production Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:13

Renaming Spools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:22Individual renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:22Group renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:23

Automatic Flange Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:23

Pipe Sketches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1Creating Pipe Sketches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1How to Use the Pipe Sketches Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3Created Sketches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:6

Pipe Sketch Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:9Drawing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:9Backing Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:10Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:11Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:14Common Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:14Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:16How to Define Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:16Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:17Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:18Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:19

Piping Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1

12.0© 2007 AVEVA Solutions Ltd v


Creating Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1Assembly Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:5Building and Maintaining Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:7Creating the Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:8Building an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:9Non-Graphical Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:12Primary and Secondary Origins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:13Piping Assembly Component Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:14STYPE Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:15Position Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:17Orientation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:17Bore Selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:18

Key Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:19

Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1

The Equipment and Piping DESIGN Database . . . . . . . . . . . . . . . . .A:1

SPOOLER Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . .B:1Spool Breaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B:1Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B:1Weld and Joint Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:2Types of Welds and Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:2

Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B:3Shop Flag Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:3Leave Tubes of Welds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:3Welds for OLETs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B:4

Pipe Piece and Pipe Spool Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1Pipe Piece Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1PML Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1

Pipe Piece . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1Pipe-Piece Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1Pipe-Piece Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:2Pipe-Piece Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:3

Pipe Spool Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:4PML Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4

12.0© 2007 AVEVA Solutions Ltd vi


Pipe Spool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:4Pipe Spool Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4Pipe Spool Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:5Pipe Spool Methods (not implemented) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:5Pipe Spool Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:6Pipe Spool Pseudo Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:6

Pipe Spool Reporting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:6MTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:6Assembly Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:6Bending Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:9Welding Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:10Spool Extents/End Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:10

Fabrication Machine Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:1Fabrication Machine Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:1Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:1BendingMachineResult . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:4WeldingMachineResult. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:5BendingTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:6BendActivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:6WeldingTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:6

Database Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:7FMWL - Fabrication Machine World Top Level Element . . . . . . . . . . . . . . . . . . . . . . . . . . . D:7FMGRP - Fabrication Machine Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:7FMBEND - Fabrication Machine - Bending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:7FMBPLN - Fabrication Machine - Bending - Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:8FMBDIM - Fabrication Machine - Bending - Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:8FMBSST - Fabrication Machine - Bending - Springback/Stretch Factor . . . . . . . . . . . . . . . D:8FMWELD - Fabrication Machine - Welding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:9FMWSK - Fabrication Machine Welding - SKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:9

Automatic Flange Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D:9New Attribute for PTCA, PTAX, PTMI, PTPOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:9New Pseudo Attributes for Branch Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:9Connection Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:10New Datacon Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D:10

Other Relevant Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .E:1PDMS Introductory Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1AVEVA PDMS Reference Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1

12.0© 2007 AVEVA Solutions Ltd vii


General Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2

Sample Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F:1

12.0© 2007 AVEVA Solutions Ltd viii

Pipework Design User GuideRead this First

1 Read this First

1.1 Scope of this GuideThis guide introduces some of the facilities provided by the AVEVA Plant DesignManagement System (PDMS) for designing and documenting interconnected pipingnetworks for a wide range of process and related Plant Design industries, both on-shore andoff-shore. It explains the main concepts underlying PDMS and its supporting applications,and shows how you can apply these to your own design projects.

A number of the chapters of this guide take the form of hands-on tutorial exercisescombined with frequent explanation of the underlying concepts. As you work progressivelythrough the exercises, you will gain practical experience of the ways in which you can usePDMS while learning about the powerful facilities it provides.

1.1.1 Intended AudienceThis guide has been written for engineers familiar with piping design practices, who may ormay not have prior knowledge of PDMS.

1.1.2 AssumptionsFor you to use this guide, the sample PDMS project, Project SAM, must be correctlyinstalled on your system, and you must have read/write access to the project databases.

It is assumed that:• you know where to find PDMS on your computer system• you know how to use the Windows operating system installed on your site• you are familiar with the basic Graphical User Interface (GUI) features as described in

the AVEVA document Introduction to Common Functionality.

Contact your systems administrator if you need further help in either of these areas.

1.1.3 About the Tutorial ExercisesAll the steps of the exercises are numbered throughout the guide.

1.1.4 Further ReadingYou can find a list of relevant AVEVA documentation in the appendices of this guide.

1.2 How the Guide is OrganisedThis guide is divided into chapters and appendices, as follows:

12.0 1:1© 2007 AVEVA Solutions Ltd


Read this First introduces this guide and summarises its scope.

Introducing AVEVA PDMS

gives a general overview of the main design facilities providedwithin the pipework application.

Setting Up the PDMS Database Hierarchy

explains how PDMS stores its design data and shows you how toorganise your data. Also describes the logging in procedure andhow to create some administrative elements. A running example,which begins in this chapter and concludes in Chapter 6,illustrates the essential concepts of pipework design.

Creating Some Equipment Items

demonstrates how to create some simple items of equipment.Although not strictly part of the piping design process, the stepsdescribed in this chapter introduce you to the ways in which thedesign applications work and result in some reference pointsbetween which to route pipe runs in later parts of the exercise.

Routing a Sequence of Piping Components

explains the key features of piping design using PDMS andshows you how to build up a piping sequence component bycomponent.

Checking and Outputting Design Data

shows how to check your design for errors and inconsistencies,and how to generate reports and isometric plots directly from thedesign data. It concludes the first worked example.

Pipework Modification

explains how pipework can be modified in terms of componentspecification and bore size, and by pipe splitting.

Automatic Pipe Routing

demonstrates the facility of automatically routing pipes anddetails the administrative aspects of the facility. Includes anumber of worked examples to illustrate the concepts of routing.

Pipework Spooling explains how pipework spooling is carried out using theSPOOLER module. Includes a running worked example toillustrate the essential concepts of spooling.

Pipe Piece and Pipe Spool Production Checks

shows how to carry out pipe piece and pipe spool productionchecks.

Pipe Sketches explains the creation and administration of pipe sketches.

Piping Assemblies explains how piping assemblies can be created from fixedconfigurations of components for reuse in a design.

The Equipment and Piping DESIGN Database

summarises the database hierarchy which PDMS uses to storepiping design data.

SPOOLER Reference Information

gives SPOOLER module reference information.

Pipe Piece and Pipe Spool Data

provides pipes piece and pipe spool data relevant to pipeproduction checks.



1.3 Further Training in Using PDMSThis guide teaches you to about the key features of using PDMS for piping designs only.

If you wish to learn more about the wide-ranging facilities of PDMS, AVEVA provides a widerange of training courses, covering all levels of expertise and all design disciplines. Fordetails of courses, and to arrange course attendance, contact your nearest AVEVA supportoffice.

Fabrication Machine Data

details fabrication machine data for use in pipe productionchecks.

Other Relevant Documentation

identifies other sources of information which supplement, andexpand upon, the brief details given in this guide.

Sample Plots contains some examples of the types of isometric plot, includingmaterial take-off lists, which can be produced easily by usingPDMS.


Pipework Design User GuideIntroducing AVEVA PDMS

2 Introducing AVEVA PDMS

This chapter introduces:• the structure of PDMS• the strengths of PDMS• PDMS piping network design features.

2.1 Introducing the Structure of PDMSPDMS comprises the following functional parts:

• modules • applications.

A module is a subdivision of PDMS that you use to carry out specific types of operation. Thisguide covers the following modules:

• DESIGN, which you use for creating the 3D design model• SPOOLER, which allows you to split the pipework design into logical sections (spools)

ready for fabrication• ISODRAFT, which you use for generating annotated and dimensioned isometric

drawings of your design.

An application is supplementary program that has been tailored to provide easy control ofoperations that are specific to a particular discipline. The applications you will use for pipingdesign work in this guide are:

• Equipment• Pipework.

You can switch quickly and easily between different parts of PDMS.

2.2 Strengths of PDMSIn AVEVA PDMS, you have a powerful suite of facilities, designed by piping engineers forpiping engineers, for creating, analysing, and documenting logically interconnected pipingnetworks.

The emphasis is on maximising both design consistency and design productivity:• The design modelling functions incorporate a degree of apparent intelligence that

enables them to make sensible decisions about the consequential effects of many ofyour design choices. This allows you to implement a sequence of related decisions witha minimum of effort.

• You can incorporate modifications into your design at any stage without fear ofinvalidating any of your prior work, because data consistency-checking is an integral


Pipework Design User GuideIntroducing AVEVA PDMS

part of the product. PDMS automatically manages drawing production, material take-offreports, and so on, by reading all design data directly from a common set of databases,to prevent errors from being introduced by transcribing information between differentdisciplines.

• The applications let you check all aspects of your design as work progresses. Thisincludes on-line interdisciplinary clash detection, so the chances of errors andinconsistencies reaching the final documented design are reduced to an exceptionallylow level.

• The applications are controlled from a GUI. This means that all design, drawing andreporting operations are initiated by selecting choices from menus, and by enteringdata into on-screen forms. For ease of use, many common actions are alsorepresented by pictorial icons.

2.3 PDMS Piping Network Design FeaturesThe AVEVA PDMS pipework applications offer the following key benefits:

• The applications are designed to use specification data when selecting pipingcomponents from the Catalogue database, so that design consistency and conformityto standards are ensured. It is important, therefore, that the Piping Cataloguedatabases are properly maintained: a Specification Generator facility is provided toenable this to be achieved with a minimum of effort.

• You can name piping elements in accordance with a predefined set of rules, so thattheir positions in the database hierarchy are always obvious without you having toenter specific texts during the design process.

• You can create pointers to define the storage areas in which specific types of designelement are to be held in the database hierarchy. This, especially when combined withthe rule-based naming facility, minimises the amount of data which you have to enterexplicitly as you build up your design model.

• You can set up temporary lists of elements, so that you can carry out a designoperation on all elements within the list simultaneously. This can avoid a great deal ofrepetitive work when you carry out commonly-repeated design modifications.

• The applications incorporate a number of geometric design aids, such as 3Dpositioning grids, design pins and 2D routing planes, to make it easy for you to positionpiping elements accurately within the design model. In most cases you can specify thepoints at which design items are to be positioned using the pointer to pick the requiredpoints in a 3D model view.

• At any stage of your work, you can create reports listing specified data from the currentdatabase. You can specify a standard report template, so you can derive lists ofcommonly-required information very quickly, or you can design a one-off report formatto suit special needs. The resultant output, which can include data from any designdiscipline, sorted in any way you require, can be either displayed on your screen orsent to a file (for storage and/or for printing).


Pipework Design User GuideSetting Up the PDMS Database Hierarchy

3 Setting Up the PDMS Database Hierarchy

In this chapter, you will learn:• about the PDMS database hierarchy• how PDMS stores design data• how to login to PDMS and begin the first tutorial exercise• how to create some administrative elements.

Although this guide is about the design of piping networks, in practice you will usually needto route your pipe runs between predefined design points such as equipment nozzles. Youwill therefore learn how these other items are defined in PDMS as well as learning how toconnect sequences of piping components between them.

In this chapter you will look at the ways in which equipment data and piping design data isstored by PDMS, and you will create some administrative data elements to enable you toorganise your detailed design in a logical way.

3.1 How PDMS Stores Design DataAll PDMS data is stored in the form of a hierarchy. A PDMS DESIGN database has:

• a top level, World (usually represented by the symbolic name /*)• two principal administrative sublevels, Site and Zone.

The names used to identify database levels below Zone depend on the specific engineeringdiscipline for which the data is used. For piping design data, the lower administrative levels(and their PDMS abbreviations) are:

• Pipe (PIPE)• Branch (BRAN).

Each Pipe can represent any portion of the overall piping network, but is usually usedto group items with a common specification. Each Branch within a Pipe represents a single sequence of piping components runningbetween two, and only two, points:

• Branch Head• Branch Tail.

The data which defines the physical design of the individual piping components is heldbelow Branch level.

In the basic configuration, equipment design data has only one administrative level belowZone: the Equipment (EQUI). The data which defines the physical design of eachequipment item is represented by a set of basic 3D shapes known as Primitives (Box,Cylinder, etc.) held below Equipment level. Connection points are represented by Nozzles(NOZZ).



Together, these hierarchic levels give the following overall format:

3.1.1 PDMS Design Data DefinitionsAll data is represented in the database (DB) as follows:

• Each identifiable item of data is known as a PDMS element.• Each element has a number of associated pieces of information which, together,

completely define its properties. These are known as its attributes.

Every element is identified within the database structure by an automatically-allocatedreference number and, optionally, by a user-specified name. Additional items of informationabout an element which can be stored as attribute settings include, the:

• element type• element physical dimensions and technical specifications• element physical location and orientation in the design model• element connectivity.

Some attribute settings must be defined by you when you create a new element, otherswill be defined automatically by PDMS.

When you are modifying a database (for example, when you are creating new elements orchanging the settings of their attributes), you can consider yourself to be positioned at aspecific point within the hierarchy. The element at this location is called the current element(usually abbreviated to CE).

In many cases, commands which you give for modifying the attributes of an element willassume that the changes are to be applied to the current element unless you specifyotherwise, so you must understand this concept and always be aware of your currentposition in the database hierarchy. The Design Explorer displays this informationcontinuously.

The vertical link between two elements on adjacent levels of the database hierarchy isdefined as an owner-member relationship. The element on the upper level is the owner ofthose elements directly linked below it. The lower level elements are members of theirowning element. Each element can have many members, but it can have only one owner.

You can navigate from any element to any other, thereby changing the current element, byfollowing the owner-member links up and down the hierarchy.

WORLD (/*)

SITE

ZONE

PIPE

BRANCH

Design data defining individual piping components

SITE

ZONE

EQUIPMENT

Design data defining equipment shapes (primitives)and connection points (nozzles)

(elbows, bends, tees, valves, etc.)



3.2 Logging InThis is the first step of the tutorial exercise

Exercise begins:

1. In the PDMS Login form give the name of the Project in which you want to work: enterSAM.

2. Give your allocated Username: enter PIPE.

3. Give your allocated Password: enter PIPE.

4. Give the part of the project Multiple Database (MDB) you want to work in: enter PIPE.

5. Give the name of the Module you wish to use: select Design.Make sure that you leave the Read Only box unchecked, so that you can modify thedatabase as you work.When you have entered all the necessary details, the form looks as shown:

Click OK.

3.3 PDMS Startup DisplayWhen PDMS has loaded, your screen looks as shown:



As labelled above, the display comprises the following:• Title Bar - shows the current PDMS module, and its sub-application if applicable.• Main Menu Bar - the area you use to make menu selections. • Main Tool Bar - has a number of icon buttons and drop-down lists that offer shortcuts

to a selection common PDMS operations and standard settings.• Design Explorer - shows your current position in the PDMS database hierarchy. To

move to a different point in the database, you click on the appropriate item in the list. • 3D Graphical View - the window in which you display the design model graphically as

you build it. A pop-up menu (which you access with the right-hand mouse button)enables you to control how the model is represented. This window also has its own toolbar.

• Status Bar - displays information about the current status of your operations.

You can reposition or minimise these windows at any time using standard windowmanagement facilities.

3.4 Creating some Administrative ElementsYou are now ready to create some administrative elements at the top of the PDMS DESIGNdatabase hierarchy, as previously explained.

Exercise continues:

6. Make sure that you are at World level in the Design Explorer, then select Create>Site.On the displayed Create Site form, enter PIPESITE in the Name text box, and pressthe Enter key to confirm the name.The system automatically adds a / prefix to this name so that it conforms to the internalPDMS file naming conventions: /PIPESITE.



7. Click OK to create the Site element. Your first new element appears in the DesignExplorer as the current element.

8. You will now create two Zones named PIPEZONE (to hold piping data) and EQUIZONE(to hold equipment data). Both are to be owned by PIPESITE.

9. Now choose Create>Zone. On the displayed Create Zone form, enter PIPEZONE.

10. Click OK to create the Zone element. Again, the new element appears in the DesignExplorer as the current element, and you can see that it is owned by PIPESITE.

11. To create another Zone owned by PIPESITE (and not PIPEZONE), click on PIPESITEin the Design Explorer to make it the current element. Now create a second Zone,EQUIZONE, in the same way as before.Your top part of the Design Explorer will now look like this:

Note: If you or other users have accessed this database before, the list may also containother elements.

In the next chapter you will create some standard equipment items, to give somereference points between which you can subsequently route your sample pipingsequences.


Pipework Design User GuideCreating Some Equipment Items

4 Creating Some Equipment Items

In this chapter you will:• learn how equipment items are represented in PDMS• create some simple equipment items, to predefined designs. These will form the basis

for routing your piping network.

4.1 How Equipment Items are Represented

4.1.1 Basic PrinciplesEach equipment item is defined geometrically in PDMS as a collection of basic 3D shapes.These shapes are known as primitives. The primitives used for piping connections toequipment items are nozzles (which are standard components which you select from thePDMS catalogues). So, for example, a simple storage vessel might be built up from thefollowing primitives:

• a cylinder for the main body• two dishes for the ends• two boxes for the support legs • a nozzle for the piping connection:

The position of the equipment item as a whole, and the relative positions of its componentprimitives are specified in terms of its origin.

The orientation of the equipment item is specified by aligning the X,Y,Z axes of its primitiveswithin the E,N,U (East, North, Up) coordinate system of the design model (more accurately,the E,N,U coordinate system of the item owning Zone).

Primitives: Dishx2

Cylinderx1

Boxx2

Nozzlex1



You will look in more detail at the principles of positioning and orientating items within thePDMS design model when you start to create piping components.

4.1.2 Using Predefined Templates for Standard EquipmentYou do not have to build up each item of equipment from its component primitives becausePDMS has range of predefined equipment types from which you can choose. Thesestandard equipment types, some of which will have been supplied with the originalapplication and some of which may have been added by your company, are stored asparameterised Design Templates (TMPL). The master copies of these design templates arestored in a special part of the DESIGN database.

When you select a design template for inclusion in your design:• a copy of the design template is created below the parent equipment element • all primitives defining the template geometry are stored below the template copy• any variable dimensions and so on, needed to fully specify the equipment in the design

are stored as Design Data (DDAT) elements below a Design Dataset (DDSE) owned bythe template.

All the above are jointly referred to as the design element properties.

To enable a template designer to reuse standard configurations of primitives within anequipment design, the Equipment element is sometimes subdivided into Sub equipment(SUBE) elements. In such situations an extended hierarchy is formed. An example of anextended hierarchy is as follows:

EquipmentOrigin

Z

XY



Note: For the purposes of the current exercise, you do not need to fully understand theimplications of this alternative method of storing design data. The concepts havebeen introduced to enable you to recognise some of the new elements that will beadded into your Design Explorer as you progress through the steps of the exercise

4.2 Creating a Storage Tank to a Standard DesignIn this section you will create a storage tank using one of the standard designs supplied withPDMS.

Exercise continues:

12. To start the Equipment application, select Design>Equipment from the DesignGeneral Application menu bar. When loading is complete, the main menu bar and the tool bar (which now has asecond row) show some extra options which give you access to the whole range offunctions needed to create and position equipment items:

13. Make sure that EQUIZONE (the zone you created for storing equipment items) is yourcurrent element.

14. Display the Create Standard Equipment form in one of the following ways:• Select Create>Standard from the menu bar

• Click on the toolbar button.



15. In the Name text box of the Create Standard Equipment form enter tank1.The Specification Data area of the form enables you to narrow down your choice ofstandard equipment by a progressive question-and-answer sequence. At each stage ofthe search, you select from the options in the lower list (whose title changes to reflectits content) and the progress of the search is summarised in the Current Selection list.

16. From the Specification drop-down list, select CADC Advanced Equip.

17. From the CADCENTRE Advanced list, select Vessels. This selection is copied to the Current Selection list, while the lower list now showsthree Vessel Type options.

18. Select Vertical Vessels.

19. Select Storage Vessel with Dished Top & Bottom.

20. Select VESS 001 - Dished both Ends.The lower list title now says Selection complete and the list itself is now empty. TheCurrent Selection list shows the fully-specified equipment:



21. At this stage, the equipment has the default dimensions defined by the templatedesigner. To specify your own dimensions, click the Properties… button to display aModify Properties form listing all parameterised dimensions assigned to theequipment definition.



22. Enter the following parameters:

• Height: 3000

• Diameter: 2800

• Dish Height: 300

• Knuckle Radius: 100

• Support type: NONE



The dimensioned plot view in the lower part of the Modify Properties form shows thesignificance of the dimensions.

Note: If you cannot see the plot view, select Settings>Properties from the main menu barand, in the resultant Properties Settings form, select Display Plotfile. Click OK andthen re-display the Modify Properties form to show the plot view. Alternatively, clickthe Plotfile button on the Create Standard Equipment form or Modify Propertiesform to display the plot in a separate window at any time.

If you wish to zoom in so that you can read the text on the plot view, position the pointerin the plot area, hold down the middle mouse button, drag out a rectangle enclosing theregion of interest, and release the button. To zoom out, position the pointer over thecentre of interest of the plot and click the middle mouse button.

23. Click OK on the Modify Properties form.

24. Click Apply on the Create Standard Equipment form.The Positioning Control form now appears automatically:

This is because you must specify the position of equipment before it can be added intothe database. In a normal design situation, you would position the equipment relative to part of anexisting plant structure. At the moment your view is empty, so you cannot pick anyexisting reference point. You must therefore give an explicit position.

25. Click the button on the Positioning Control form.

26. On the Explicit Position form that displays, enter the coordinates:

27. Click Apply.The tank is added into the 3D View, but the current view settings mean that you cannotsee it in clear detail. You will rectify this a little later. The Design Explorer now shows an Equipment (EQUI) element, which owns a DesignTemplate (TMPL), which in turn owns some primitives and property-defining elementsrepresenting the equipment geometry.

28. Dismiss the Explicit Position form.

29. Dismiss the Create Standard Equipment form.

• East: 7275

• North: 2350

• Up: 100



4.3 Adding a Nozzle to the Storage TankThe standard vessel design does not incorporate any nozzles. In this section, you will add anozzle that you will later use to connect your pipework to the storage tank.

Exercise continues:

30. Ensure you have EQUI Tank-1 selected in the Design Explorer as the currentelement. Select Create>Primitives, and click Apply to accept the default details in theresultant form:

31. On the Create Nozzle form displayed, enter the following parameters:

32. Click the Nozzle Type button. Define the nozzle type by entering the followingparameters in the displayed Nozzle Specification form:

33. Click Apply, and then Dismiss. You will see in more detail how catalogues are used when you start to select pipingcomponents.

34. The settings on the Create Nozzle form now look as shown:

• Name: Tank-1-N1

• Position: West

North

Up

1675

0

250

• Orientate P1 is: W (Sets the direction of the nozzle flanged face).

• Height: 300 (The height of a nozzle is the length of itsconnecting tube).

• Specification: #300.R.F

• Generic Type: Ansi_flanged

• Nominal Bore: 150



Click Apply and then, if you have not already done so, Dismiss any remaining formsinvolved in creating the nozzle.

4.4 Viewing the DesignIn order to see what your design looks like as you build it up, and to enable you to identifydesign items by simply pointing to them rather than by navigating to them in the DesignExplorer, you will now display your current design in a 3D View window, and learn how tomanipulate this display.

4.4.1 Defining what Appears in the ViewIn this section you will identify your equipment zone as the contents of the graphical display,and view isometrically.

Exercise continues:

35. The Design Explorer will now look like this:



36. You can see the list of elements that will appear in the View by looking at the DrawList. To view the Draw List, select the option Display>Draw List from the main menubar. You should get something like this:

37. To remove the elements currently in the Draw List, right-click each one in turn andselect Remove from the shortcut menu. To set the Draw List so that you can see eachequipment item as you create it, you need to select your equipment Zone. Do this byclicking on EQUIZONE in the Design Explorer.

38. Now click on EQUIZONE and select 3D View>Add from the shortcut menu.



39. Now, in the 3D View tool bar, click on the Limits CE button, . This adjusts thescale of the view automatically such that it corresponds to a volume just large enoughto hold the chosen element(s); in this case, the Zone.

40. To set an isometric view direction, position the pointer in the 3D View window andselect Isometric>Iso 3 from the shortcut menu.

41. Display horizontal and vertical border sliders by selecting View>Settings>Borders orpress Function Key F9.

42. Experiment with the shortcut menu options Look, Plan, and Isometric, to see differentview directions, and then revert to Isometric>Iso 3.

4.4.2 Manipulating the Displayed ViewYou can manipulate the displayed model view in a number of ways. The three viewmanipulation modes are:

• Rotate the view• Pan the view across the display area• Zoom in or out to magnify or reduce the view.

The current manipulation mode is shown in the status line at the bottom of the 3D Viewwindow, and is currently set to Rotate, as shown in the previous illustration.



To change the view manipulation mode, use the 3D View tool bar buttons, or the functionkeys, as follows:

You can also choose these view manipulation options, from the shortcut menu availablewithin the 3D view.

Exercise continues:

43. Select , (note that this is the default state).Position the cursor in the view area and hold down the middle mouse button, thenmove the mouse slowly from side to side while watching the effect on the displayedmodel.

44. The initial direction of movement determines how the view appears to rotate; startingwith a left or right movement causes the observer’s eye-point to move across the view.

45. Now release the mouse button, hold it down again and move the mouse away from youand towards you; this time the observer’s eye-point appears to rotate up and downaround the model.

46. Repeat the rotation operations while holding down the Ctrl key. Note that the word Fastappears in the status line and that the rate of rotation is increased.

47. Repeat the rotation operations, but this time hold down the Shift key. Note that theword Slow appears in the status line and that the rate of rotation is decreased.For an alternative way of rotating the model, first press the F9 function key to displaythe horizontal and vertical sliders, and then try dragging the sliders to new positionsalong the view borders. You can rotate the model in this way at any time, regardless ofthe current manipulation mode.

48. Select .

49. Position the cursor in the view area and hold down the middle mouse button, thenmove the mouse slowly in all directions.

Note: It is the observer’s eye-point which follows the mouse movement (while the viewingdirection remains unchanged), so that the displayed model appears to move in theopposite direction to the mouse; in effect, you move the mouse towards that part ofthe view which you want to see.

50. Repeat the pan operations while holding down first the Ctrl key (to increase thepanning speed) and then the Shift key (to decrease the panning speed).

51. Select .

52. Position the cursor in the view area and hold down the middle mouse button, thenmove the mouse slowly up and down.

or F2 selects Zoom mode

or F3 selects Pan mode

or F5 selects Rotate mode.



Moving the mouse away from you (up) zooms in, effectively magnifying the view;moving the mouse towards you (down) zooms out, effectively reducing the view. Notethat these operations work by changing the viewing angle (like changing the focallength of a camera lens); they do not change the observer’s eye-point or the viewdirection.

53. Repeat the zoom operations while holding down first the Ctrl key and then the Shiftkey.

54. Position the cursor at the top of the tank and click (do not hold down) the middle mousebutton. Notice how the view changes so that the picked point is now at the centre of theview. Whenever you click the middle button, whatever the current manipulation mode,you reset the centre of interest. Set the centre of interest to the face of the nozzle,then zoom in for a close-up view. You will find this a very useful technique when makingsmall adjustments to the design.

55. To restore the original view when you have finished, make sure that your current

element is EQUIZONE and click on the Limits CE button, and reselectIsometric>Iso 3 from the shortcut menu.

4.5 Creating Some More Equipment ItemsYou need to have several equipment items between which to route piping components, so,in this section, you will now create a different design of vertical storage vessel and a pump,using similar procedures to those you used to create the first vessel.

Exercise continues:

4.5.1 Creating a Vertical Vessel

56. Navigate to EQUIZONE and click , or select Create>Standard.

57. On the displayed Create Standard Equipment form set the following:• In the Name text box enter Tank-2 • From the Specification drop-down list, select CADC Advanced Equip • From the CADCENTRE Advanced list, select Vessels • This selection is copied to the Current Selection list, while the lower list now

shows three Vessel Type options • Select Vertical Vessels • Select Storage Hoppers • Select VESS 002 - Dished Top and Coned Bottom. This design includes provision for one nozzle at the bottom of the conical base.

58. Click the Properties button, and in the displayed Modify Properties form enter thefollowing parameters:

• Height: 2500

• Diameter: 1500

• Dish Height: 250

• Radius: 75



59. Click OK on the Modify Properties form.

60. Click Apply on the Create Standard Equipment form.

61. Click the button on the Positioning Control form, and in the displayed ExplicitPosition form enter the coordinates:

62. Click Apply, and observe the relative positions and orientations of the two vessels inthe graphical view. EQUIZONE is now larger than when you last set the viewing scale,

so navigate to /EQUIZONE and click to reset the limits.

63. Dismiss the Create Standard Equipment form.

64. Dismiss the Explicit Position form.

4.5.2 Naming the Nozzle in the Base of the New Vessel65. Navigate to the nozzle on /Tank-2 using the Design Explorer:

66. Select Modify>Name and name the nozzle Tank-2-N1. Click Apply, and then Dismiss.

• Height: 750

• Nozzle Height: 250

• Nozzle Type: #300.R.F. 150mm NS

• Support type: NONE

• East 2600

• North 7000

• Up 2600



67. Navigate back to Tank-2 and add a second nozzle using the same sequence aspreviously detailed and give it the following description:

Note: This nozzle has a smaller bore than the other nozzles. You may need to rotate theview to see all of the nozzles simultaneously.

4.5.3 Creating a Standard Design Pump

68. Click on , and give the pump the following definition:

Set the parameters as follows:

• Name: Tank-2-N2

• Position: East

North

Up

1000

0

2000

• Orientate P1 is: E (Sets the direction of the nozzle flanged face).

• Height: 250 (The height of a nozzle is the length of itsconnecting tube).

• Specification #300.R.F

• Nozzle Type ANSI-flanged

• Nominal Bore 100

• Name: /Pump-1

• Specification: CADC Advanced Equip CADCENTRE Advanced

• Pumps, Pump Type Centrifugal Pumps

• Specific Type: Centreline Mounted Centrifugal Pumps

• Selection: PUMP 005 - Pump Centreline Mounted TangentialOutlet.

• Baseplate Length 1600

• Baseplate Width: 510

• Distance Origin to Baseplate 175

• Distance to Suction Nozzle: 240

• Distance Bottom to Centreline 340

• Discharge Nozzle Height 180

• Suction Nozzle to Coupling 700

• Distance Discharge Nozzle 135



69. Create the pump and position it at:

4.5.4 Changing the Orientation of an Equipment ItemThe orientation of the pump is as defined by the template default settings.

70. Click on the button on the main tool bar to display the Define Axes form. On thisform, select Cardinal Directions:

An E,N,U axes symbol is displayed at the origin of the current element. The horizontalsuction nozzle points north.

71. To change the orientation of the pump so that it points West, click on the Model Editor

button on the main toolbar or select Edit>Model Editor from the main menu bar.

72. Using the left-hand mouse button, click on the pump to display the drag handles.

• Suction Nozzle Type #300.R.F. 150mm NS

• Discharge Nozzle Type #300.R.F. 150mm NS.

• East 4700

• North 5000

• Up 350



73. With the pointer over the horizontal rotation handle (see above), press and hold downthe left-hand mouse button and move the cursor (which changes shape) in ananticlockwise direction until the following pump orientation is achieved:

74. The pump now points West. Click anywhere in the graphics area to remove the draghandles.



75. Other methods of changing orientation are explained below. (Move the pump back its

original orientation first by clicking on the Undo button ( ) on the main toolbar.

Click again to leave Model Editor mode.

76. To change the orientation of the pump so that it points West, either click on the button, or select Orientate>Rotate. The Rotate form enables you to rotate theequipment through a specified angle about a defined axis. The default axis is up,through the origin, and is correct, so just set Angle to 90:

77. Click Apply, and then Dismiss the Rotate form, and select Close>Retain axes on theDefine Axes form. This leaves the axes symbol in the 3D View: you will find this usefulfor reference in the rest of the exercise.

4.5.5 Tidying Up Afterwards78. Navigate to each pump nozzle in turn and rename:

• the horizontal nozzle: /Pump-1-SUCTION • the vertical nozzle: /Pump-1-DISCHARGE.

79. Check the layout of the three equipment items in the graphical view:



In the next chapter, you will add to the design model by creating some piping components.


Pipework Design User GuideRouting a Sequence of Piping Components

5 Routing a Sequence of Piping Components

In this chapter you will:• learn how some of the items which make up the design are represented and accessed

in the PDMS databases;• route some pipes between the three items of equipment which currently make up your

design model;• position a selection of piping components within the pipe runs.

5.1 Design-to-Catalogue Cross-ReferencingTo ensure design consistency and conformity with predefined standards, the basicdefinitions of all items that you can use in the pipework design are held in a Cataloguedatabase. This holds definitions of:

• all available configurations and materials for each type of piping component• all types of nozzle for connecting pipe fittings to equipment items.

When you add an item to your design model, you store the position, orientation etc. for theitem in the PDMS DESIGN database, but you specify the physical properties of the item bysetting up a cross-reference (Specification Reference or SpecRef) which points to anappropriate entry in the Catalogue database.

The dimensions of each item are defined in the catalogue by parameters whose values areset only at the design stage, so that a single catalogue entry can represent a whole family ofdesign components which differ only in their dimensions.

You have already used this concept when creating the equipment nozzles in the previouschapter. In each case, you:

• selected the required type of nozzle by setting its catalogue specification, (ANSIflanged, with raised face, suitable for 300 pound working pressure, with 150mmnominal bore, for example)

• specified the length of the nozzle tube (defined in the catalogue as a parameteriseddimension) by setting its Height attribute.

5.2 How Piping Networks are RepresentedPiping networks are represented by the following:

• pipes and branches• piping components.

Each of these is explained in turn below.



5.2.1 Pipes and BranchesYou have already learnt that the principal administrative elements of a Zone are Pipes andtheir subordinate Branches. Each Pipe can represent any portion of the overall pipingnetwork, while each Branch represents a single section of a Pipe which runs between two,and only two, points (the Branch Head and the Branch Tail).

The individual piping components (defined in terms of their catalogue specifications) arestored as Branch members. So, a Pipe that incorporates a Tee, for example, must own atleast two Branches to achieve the necessary three connection points.

The following configurations show two ways of achieving this (solid lines represent part ofBranch 1; dotted lines represent part of Branch 2):

5.2.2 Piping ComponentsEach piping component is represented in the PDMS catalogue by three types of data:

• The physical shape of the component is defined by a set of geometric primitives (likethe ones used to represent equipment items introduced in the previous chapter).

• So that the component can be manipulated and linked to adjacent piping items, allprincipal points needed to define its position, orientation and connectivity are identifiedby uniquely-numbered tags. These tags, which have both position and direction, arecalled p-points (or Design Points). Each p-point is identified by a number of theformat P0, P1, P2 etc., while the principal inlet and outlet points for the logical flowdirection through the component are identified as p-arrive and p-leave. P0 alwaysrepresents the component origin position, while in normal pipe routing mode (Forwardsmode) P1 is the same as p-arrive and P2 is the same as p-leave.

• The settings of all variables needed to distinguish a component from others with thesame geometry and p-point sets are defined by parameters. The values of these aredefined to suit the specific design requirements.

For example, a Tee component might be represented in the PDMS catalogue as follows:



where the two cylinder primitives form the component geometry set and the four p-pointsform its point set (the fourth p-point, P3, lets you specify the orientation of the side arm whenyou incorporate the tee into your design). The dimensions of the tee are represented in thecatalogue by parameters whose values are determined by the nominal bore required to suitthe design.

5.3 Starting the Pipework ApplicationExercise continues:

80. Change from the Equipment application to the Pipework application, by selectingDesign>Pipework. The menu bar for the Equipment application is replaced by that for the Pipeworkapplication. The menu bars for both applications are superficially similar, but the lattergives you access to options with specific relevance to creating and manipulating pipingcomponents.The Default Specifications form, which is displayed automatically, is described in thenext section.

5.4 Setting a Default SpecificationWhen you select components from the piping catalogue as described earlier in this chapter,you do so by stating which Specification the components must match. To avoid having tospecify this data again for each component, you can set a Default Specification at Pipe orBranch level. This will be used automatically at lower levels unless you override it (thedefault specification is said to be cascaded down the hierarchy).

As an example, the specifications which form part of the sample project within which you areworking include:

• A1A: ANSI Class 150 Carbon Steel• A3B: ANSI Class 300 Carbon Steel• F1C: ANSI Class 150 Stainless Steel

For the purposes of your design exercise, you will use the A3B specification to select allcomponents.

Exercise continues:

81. On the Default Specifications form, select the Piping specification A3B.



82. The project specifications include some choices for pipework Insulation, but no traceheating specifications (as shown by the None Available entry in the Tracing option list).You do not want to use insulation or trace heating, so make sure that both of them areunselected.When you click OK, the current default specification is shown in the second row of thetool bar:

5.5 Creating a Simple Pipework SequenceIn the next part of the exercise you will create a sequence of piping components connectedbetween the nozzles /Tank-1-N1 and /Pump-1-SUCTION. The initial sequence will include atee to which you will later connect another pipework sequence.

The configuration which you will create (with all components in a horizontal plane) is asshown:

You will represent both this and the next sequence by a single Pipe element in the DESIGNdatabase, but you must subdivide this into two Branch elements to allow the flows into thepump to combine at the tee. You will define the branches as follows:

Nozzle/Tank-1-N1

Nozzle/Pump-1-SUCTION Gasket 1

Flange 1

Elbow 1

Flange 2Flange 3

Tee1

Gasket 2

Gasket 4

Gasket 3

Valve 1(withh dwheel)

Flange 4

(Pump)(Tank)

flowflow

L

N

E

SW

FromsecondBranch



• Branch 1 will have its Head at nozzle /Tank1-1-N1 and its Tail at nozzle /Pump-1-SUCTION. It will consist of the following components, listed in head-to-tail order:

• Gasket 1• Flange 1• Elbow 1• Flange 2• Gasket 2• Valve 1 (which includes flanges in its catalogue definition)• Gasket 3• Flange 3• Tee 1• Flange 4• Gasket 4.

Note that the flow through the tee will enter at P1 and leave at P3 (that is, p-arrive will be P1and p-leave will be P3).

• Branch 2, which you will create in a later part of the exercise, will have its Headpositioned at Nozzle /Tank-2/N1 and its Tail at the third arm of the tee (P2), (rememberthat flow direction is always from head to tail).

Note: The tubing running between the piping items (shown by the dotted lines in thediagram), is added and adjusted automatically by PDMS to suit the positions andspecifications of the components. You do not have to create it explicitly; it is referredto as implied tube.

Refer back to the sequence in the diagram when necessary to understand the logic of thefollowing steps for creating this in the design model.

Exercise continues:

83. Navigate to /PIPEZONE in the Design Explorer and click the Pipe Creation icon inthe Pipework toolbar:

84. The Create Pipe form displays:



You can use this form to characterise the pipe you want to add to your design. For now,name the pipe Pipe-1, set the Bore to 150, and the Insulation to K.

85. Click on Apply to create the pipe.

86. The Create Pipe form changes to allow you to access and modify the branch’s Headand Tail information.



Note: how the new branch is named automatically from its owning pipe as Pipe-1/B1. Notealso that the branch’s Head and Tail connections are undefined. To define them youclick on the respective Change button and make the appropriate choices.

87. For this exercise, you will connect both the head and tail of the branch to existingnozzles. First, click the Change button in the Head Connection part of the form.

The form now displays as shown:



88. Click the Pick button and use the cursor to select the Nozzle N1 on Tank-1 (namedNOZZ Tank-1-N1).When you select the nozzle, the form changes to reflect your choice:

89. To confirm your selection and connect the head of the branch to the nozzle, click theConnect button.The main Create Pipe form will once more be displayed, but now the Head Detail hasbeen filled in:



90. Now click the Change button in the Tail Connection part of the form:

A form displays that is virtually identical to the one you used to select the branch’shead:



91. Click the Pick button and use the cursor to select /Pump-1-SUCTION (the horizontalnozzle on the pump). As before, the form changes to reflect your choice.

92. Click the Connect button to confirm your selection and connect the tail of the branch tothe pump nozzle.Notice how the route of the branch is shown in the graphical view by a broken line. Asyou have not yet introduced any components, this runs directly from the head to thetail.You will now build up the component sequence by creating individual piping items.

93. First, Dismiss the Create Pipe form by clicking the cross, , in the top right-handcorner of the form.

5.5.1 Modifying Pipe SequencesIf you want to modify a pipe component once you have created it, you can select the pipe inthe graphical view or the Design Explorer, and click the Pipe Modification icon on thePipework toolbar:

The exact appearance of the form displayed depends on what you have selected. If youhave selected an entire pipe you will get a form that allows you to modify the pipe as awhole; if you have selected a branch, then you will also get the options that allow you tomodify the branch.

If you click the icon and you have not selected a valid pipe component, you get an error thatlooks like this:



Exercise continues:

94. Make the Branch you created previously the current element by clicking on Pipe-1/B1in the Design Explorer.

95. Click the Pipe Component Creation icon on the Pipework toolbar:

The Component Creation form displays as shown:



The Component Creation form allows you create a component or component groupthat is either connected or positioned along the route of a pipe. The system will automatically try to create a set of predetermined adjacent componenttypes when certain component types are created, e.g. when creating a valve, thesystem will try to create the appropriate adjacent gaskets and flanges. This allows youto define the major components of the pipe route, with the system creating thesecondary components automatically.

96. From the Component Types list select Flange. The form changes in response:

97. From the Filter By drop-down list, select type WN. Ensure that the With Flow icon isselected, and both the Auto. Create Adjacent and Skip Connected Compscheckboxes are both checked.

98. Click the Connect button. You will see that the new Flange has been added to thebranch and appears both in the Design Explorer and the graphical view; you will alsonotice that the Auto Create Adjacent facility has automatically created and added aGasket between the Flange and the Nozzle. This appears in the Design Explorer butis too thin to show up in the graphical view.



99. You can modify a component once you have added it, preserving its connections toadjoining components wherever possible.First, select the Pipe Component Selection icon from the Pipework toolbar:

The Component Selection form displays:



Using this form you can change the selected component’s specification, and in somecircumstances the component’s type. Clicking the Reconnection button will reconnectall the associated components. You can also view any errors caused by doing so. If youcheck the checkbox in the top-left of the form, the form will track the specification of theCE.Experiment with this form and see what effect it has on your design. When you havefinished, restore the original settings. Dismiss the form using the cross in the top right-hand corner and return to the Component Creation form.

100. The next step is to add an Elbow to the pipe route. Click on the Choose button todisplay the Component Types list and select the Elbow option.



101. From the Filter By drop-down list, select type E. Ensure that the With Flow icon isselected, and both the Auto. Create Adjacent and Skip Connected Compscheckboxes are both checked:



102. Click the Connect button. The elbow will be added to the flange thus:

You will notice that the elbow is both pointing the wrong way and positioned flushagainst the flange:

While the auto-connect function positions and orientates the elbow so that its p-arrivepoints towards the preceding flange, the application has no way of knowing which waythe p-leave of the elbow is to be directed, so it assumes the default direction as set inthe catalogue.To change this you can use Component Modification in the Model Editor.

103. Click the Model Editor icon in the main toolbar:

104. Select the Elbow in the graphical view using the cursor. Immediately you select it, theElbow will be encircled by the Component Modification Handles, shown in magenta.

Nozzle/Tank-1-N1

Nozzle/Pump-1-SUCTION

Gasket 1

Flange 1

(Pump)(Tank)

N

E

SW

Elbow 1



These handles allow you to rotate and move the selected component or components.As you move the cursor over the handles, they change to indicate what actions you canperform on them. In addition, you can choose a number of context-dependent optionsfrom the right-click pop-up menu.

105. Rotate the view and zoom in on the Elbow until you are looking directly into the NozzleTank-1-N1. Hover the cursor over any part of the arc and two arrows will appear andthe cursor changes to an arrowed-semicircle, indicating that you can left-click, drag thehandle and rotate the Elbow:

Experiment for a few moments seeing how the Elbow rotates in response to yourmouse movements.

106. When you have finished experimenting, rotate the Elbow fully 180 degrees so it ispointing the other way. The angle you have turned the Elbow through is clearlyindicated as you drag the handle:



Alternatively, right-click and select the Enter Value option from the pop-up menu.

This allows you to enter the value you want to rotate the Elbow by in degrees; you canalso click the Preview button to see how it will look. If you click the Cancel button, therotation is cancelled and the Elbow returns to its original orientation:



107. You also want to position the elbow at a specified distance from Flange 1. Todemonstrate a new feature, you will line it up with the lower nozzle on /Tank-2.To do this, zoom the view out again so you can see once more both the Elbow and thelower Nozzle on Tank-2. Although you can reposition the Elbow to any viewing angle, itis easier to see exactly what is happening if you rotate the view so you are looking at itfrom below.When you hover the cursor over the movement handle marked X, the handle willchange indicating you can drag the Elbow to the West:



108. Display the right-click pop-up menu with the following options:

Select the Align with Feature option.This will allow you to align the Elbow with an existing item that you identify by picking itwith the cursor in the graphical view.Move the cursor so it is over the P1 direction of the Nozzle. Your display should besimilar to that shown:

Note: the system moves the Elbow as a preview to how it will look if you click on the featureand accept the move.

109. Click on the P1 point of the Nozzle Tank-2-N1. The system moves the Elbow andinserts the appropriate length of implied tubing:



The Elbow is repositioned as follows:

You will look in more detail at the ways of positioning and orientating items in somelater parts of the exercise.Your design, in Iso 3 view, should now look as shown.

Nozzle/Tank-1-N1


Gasket 1

Flange 1

(Pump)(Tank)

N

E

SW

Elbow 1

Implied tubeadded automatically

P-leave aligned with nozzle /Tank-2/N1



110. Click the Pipe Component Creation icon on the Pipework toolbar to display theComponent Creation form. Select the Valve option from the Component Types list:

111. Select the GATE option from the Filter By drop-down list and click the Connect button:



112. From the drop-down list on the next part of the form, select the Flange WN option andclick the Done button:



113. Your design should now look as shown:

From the Design Explorer you will see that the system has added the Valve as a fullassembly and has automatically included two Gaskets and Flanges:



114. As before, you want to reposition the valve so it is better placed for pipe-routing. To dothis, leave the Valve assembly selected, and click on the Model Editor icon on themain toolbar.

115. On the X axis, right-click and select the Enter Value option from the pop-up menu. Inthe displayed Move Selection form, type the value 1600 in the text box for the X value(note that the Y and Z boxes are disabled), and click the Preview button. The system shows you what the proposed move looks like:

116. Click the OK button and the system will complete the move and add a length of impliedtubing between the Elbow and the Valve assembly:



Note: that the handwheel on the Valve is pointing upwards by default; this is what isrequired for this design, but it could be easily changed by using the Model Editor andthe Component Modification Handles in a similar manner to how they were used forrotating the Elbow.

The piping network now looks like this:

117. Now create a Tee. Click the Pipe Component Creation icon and select Tee from the list. On the form thatappears next, select the T option from the drop-down list, and then in the filtered listbelow it, select the option with a Bore of 1. This represents an equal tee, where thebore of the P2 and P3 arms is set automatically to match that of the P1 arm (shown atthe top of the form as 150 in this case).In the Connection Information section of the form, select the second of the threeConfig icons as shown:

Nozzle /Tank-1-N1

Nozzle/Pump-1-

Gasket 1Flange 1

Elbow 1

(Pump)(Tank)

N

E

SW

Flanged Valve Set



Selecting this option makes the Tee a “branch off” Tee, where the Tee outlet (p-leave) isP3 rather than P2.

118. Click the Connect button. Your Tee will be added to the Valve. It should look as shown:



When created, the Tee is positioned and orientated as follows:

119. To orientate the Tee, select the Tee in the Model Editor and rotate it in the same wayyou rotated the Elbow using the Component Modification Handles. Alternatively, you can select Modify>Component>General from the main menu anduse the Orientate or Rotate option on the Piping Components form, rotating the Teeso its P3 direction is East:

Whichever method you use, the Tee should now look like this:

Nozzle/Tank-1-N1

Nozzle/Pump-1-

Gasket 1Flange 1

Elbow 1

(Pump)(Tank)

N

E

SW

Tee 1

P3 points Up

Flange 2Flange 3Gasket 2Gasket 3

Valve 1

P-leave=P2

Orientate options

Rotate options



120. The next thing you need to do is align the Tee’s branch off point with the Nozzle Pump-1-SUCTION. The easiest way to do this is to use the Movement Handles.First, select the Tee in the Model Editor and hover the cursor over the X axis:

121. Right click and choose the Align with Feature option from the pop-up menu:



122. Select the P1 point of the Pump-1-N2 feature:

123. Left-click to align the Tee. Note the system moves the Tee and inserts a length ofimplied tube to complete the connection:

124. You can also use one of the Position options on the Piping Components form to alignthe Tee with the pump nozzle:



You can use the Position options in several ways. Use any one of the following:• Select Thro Tail or Thro Next (these are the same, since the tail is effectively

the next item in the branch list).• Select Thro ID Cursor and, when prompted, pick the nozzle in the graphical

view.• Select Thro Point and, when prompted, pick the p-point at the centre of the

nozzle flange.

125. Whichever method you use, the resulting pipework layout now looks like this:

Position Options



Note: A length of implied tube is now shown between the Tee outlet and the branch tail,even though the final components have not yet been inserted. This confirms that thealignment and bore sizes of the Tee outlet and branch tail are compatible.

126. Complete the branch by adding a weld-neck flange and gasket, connected to thebranch tail. Click the Piping Component Creation icon and select a WN Flange fromthe list. Enter Pipe Component Modification mode and drag the newly added Flangeand Gasket until they are against the Nozzle Pump-1-SUCTION.The result should look like this:

Schematically, the piping now looks like this:

5.6 Creating a Second Pipework SequenceTo allow you to practice and reinforce the techniques learned in creating the precedingpipework sequence, you will now create a similar branch, also part of /Pipe-1, which runsfrom the nozzle /Tank-2/N1 to the open connection on the Tee of your existing branch, asfollows:

Nozzle/Tank-1-N1


(Pump)(Tank)

N

E

SW

flowflow

Branch Head

Branch Tail



The broken line marks a change of view direction:• components to the left are shown looking East (they lie in a vertical plane through the

tank nozzle)• components to the right are shown looking Down (they lie in the same horizontal plane

as your existing Branch 1).

Exercise continues:

127. Navigate to /Pipe-1 and click on the Pipe Modification icon on the Pipework toolbar todisplay the Modify Pipe form:

Nozzle/Tank-2/N1 (Pump)

(Tank)

N

E

SW

flow

Branch 2 HeadBranch 1 Tail

Branch 2 Tail

N

U

SD

existingbranch



128. Click the New Branch button to create a second branch, /Pipe-1/B2.



129. Select the new Branch in the list as above, and using a similar approach to the oneoutlined previously, connect its Head to Nozzle /Tank-2/N1 and connect its Tail to theTee in Branch /Pipe-1/B1. Notice how the branch route goes automatically to the free connection on the Tee; youdo not have to pick any particular point on the Tee when you connect the tail.

130. Create a Gasket and Flange connected to the branch head:



131. Click the Piping Component Creation icon on the Pipework toolbar and add a WNFlange to the branch head.

132. Using the same Component Creation form, create an Elbow of type E. Orientate andposition the Elbow so its leave connection is aligned with the branch.Implied tube is now shown between the Elbow and the Tee, confirming that thealignment and connecting bore sizes are correct:

133. Still using the Component Creation form, create a Valve and its associated Flangesand Gaskets. Select Valve type GATE and Flange type WN.



Note: that the Valve is flush against the Elbow.

134. Using Pipe Component Modification handle, move the Valve along the pipe routetowards the Tee so it is flush against it. If you click on the Valve in the Model Editor, youwill see that the Movement Handles are slightly different from the ones seen before:

This form of the Handles tells you that you can move or rotate the component in a set ofprescribed directions. In this case you can either move along the direction of the piperoute or rotate the Valve around the pipe route’s axis.

135. Select the Align with Feature option on the right-click pop-up menu. When the cursorchanges, move it anywhere on the Tee, and observe how the system shows you apreview of what it will look like if you accept the move.



136. Left-click to accept the change:

137. Zoom in on the pipework to see your completed design model.

This completes the introduction to the basic pipe routing operations. In the followingparts of the exercise you will look at some ways of checking the design model andoutputting some design data derived from the database settings.



5.7 Quick Pipe RoutingQuick Pipe Routing (QPR) enables you to define graphically the route of a Pipe by using themouse pointer to specify changes in direction of the route either in absolute terms or inrelation to model features. Elbows or Bends (as specified) are automatically inserted wherethe route changes direction. QPR would typically be used where the Head and Tail of aBranch have been defined but the route between them has not.

QPR is entered automatically when you click on an ill-defined route, which is displayed asa dotted line (instead of implied tube) between two Components.

Clicking on the dotted line brings up the Routing Handle:

You can switch the Routing Handle to the other end of an ill-defined route by picking theEnd Route Handle.

Where there is an ill-defined end, then there will be no End Route Handle.

5.7.1 QPR FacilitiesWhen defining a route, you can control:

• Orthogonal and non-orthogonal leg definition• Positioning

• Increment snapping• Explicit positioning• Feature highlighting:

• Centre line• Offsetting by OD of tube (including insulation)

• Automatic completion of route• Where completion is predictable

• UNDO/REDO changes.



Where an extremity of a route is undefined, then you can assign the end to the last definedpoint within the route or to designate an appropriate element to connect the extremity to.

5.7.2 Cases of Ill-defined RoutesIn general terms an ill-defined route is where instead of cylinder being shown for impliedtube, a dashed line is shown. A common case of this would be where the Head and Tail of aBranch have been defined but the route between them has not.

Other cases are detailed below.

• Bad Alignment Between Two ComponentsThis is where the leave direction and arrive direction of adjacent elements do not match.This could be due to the current Design tolerance settings, i.e. offset, angle and ratio.

• Arrive or Leave where Head or Tail is UndefinedThis is where the end directly adjacent to a Component is unset or ill-defined. An “unset”end is where the Head or Tail has its attributes left in the default state, whereas an ill-definedend is where, when the reference is set, the position is not coincident with the referenceitem or when the end reference is not set, hence the end connection is unset.

• Abandoned RoutesA route can be abandoned at any time. For example, you may with to abandon the route soyou can continue routing it from the other end. You can access the point from where theroute was abandoned to continue routing.

In the case of an ill-defined end of a route, the end is positioned at the last point defined.However, the end can still to be set as ill-defined, even if you set the end connection to apermissible type.

5.7.3 Entering and Leaving QPRQPR is accessed via the selection of the dashed line (representing an ill-defined route)when in Model Editor Mode. The selection of an ill-defined route is mutually exclusive to anyother element selected, i.e. selecting anything else takes you out of QPR.

When a dashed line is selected, the Routing Access Handles are shown at the ends of theill-defined route. Where there is an ill-defined end (for example if the Pipe Head is definedbut not the Pipe Tail) only one access handle is shown.

You exit QPR either by exiting Model Edit Mode or by changing the current selection set, i.e.by picking another item in the display.



5.7.4 The Pipe Routing HandleThe Pipe Routing handle has three parts:

• the Extend Route Handle - used to extend the route in the direction indicated by thehandle.

• the Cardinal Direction Handles - used to change the direction of routing to one of thecardinal directions for the current frame of reference.

• the Rotation Handles - allow you to direct interactively the Extend Route Handle.

5.7.5 The Extend Route HandleThis is used to change the position of the handle along the current route direction. Thefollowing operations can be performed on the handle.

• DraggingThe Extend Handle can be dragged by either using the left-hand or right-hand mousebuttons, in the direction of or in the opposite direction to the extend direction.

By default, i.e. if no special actions are active (e.g. feature highlighting), the handle moves inmultiples of the currently defined linear increment.

When dragging using the right-hand mouse button, you are presented with a contextsensitive popup menu on button up. The menu displays the available options which relate tothe drag and, when in a special action mode, the target, if applicable.

By default, i.e. when no special actions are active, you are given the option to maintain thedragged extension or cancel the operation, and the handle returns to the previous position.

• Feature HighlightingFeature highlighting allows you to position the handle using other elements with the model.With Feature Highlighting ‘on’, dragging with the left-hand mouse button held down causesfeatures such as p-points or p-lines to be highlighted when the pointer moves across them.Highlighted features can then be ‘snapped' to.



Feature highlighting can be activated either from the F ‘hotkey’ or via the Selection pull-down menu on the main menu bar. The system reverts to its previous mode once a featurehas been selected or the action aborted

When feature highlighting is active, the handle follows the pointer using the defaultincrements, until a feature is identified. When a feature is identified, the handle moves to thederived intersection point.

Where there is more than one point that can be snapped to, built-in default behaviour isused to derive the initial position (see Distance from Origin). However, it is possible to cyclethrough the derived points (which are usually with respect to the intersection of the routingline and a plane) and choose the desired one. The P hotkey is used for this.

Subsequent feature identification within the same drag uses the last solution type to derivethe point, where possible. If there is no solution point to the feature selection, the systemreverts to its default behaviour, (see below).

• OffsettingWhere a position has been derived using feature highlighting, you can offset the position by½ OD of the tube (including insulation) to either side of the plane.

An example of offsetting tube from steelwork is shown below:



When the offset handle (the symbol) appears near the pointer, the offset is performed bymoving the pointer over the sphere corresponding to the side of the feature you want tooffset. (In the example above the pointer would be moved over the top sphere.) Note thefeedback giving the position where the current selection is to be positioned relative to thesteelwork Beam. See Feedback for more details of feedback.

It is possible to cycle through the derived positions, i.e. either side offset and back to theoriginal centreline position, in a similar manner to that for cycling through the intersectionwith a plane.

Subsequent feature identification within the same drag uses the last selected offsetmechanism where possible, i.e. if the last position was offset behind a plane, subsequentidentifications will also be offset behind the plane.

5.7.6 Nudging the HandleOnce a drag has been started using the left- or right-hand mouse button, you can finelyadjust the positioning of the handle using ‘hotkeys’. You can ‘nudge’ the manipulationhandle when dragging in a linear direction, using the arrow keys on the numeric keypad (orthe numeric keypad 2 and 8 keys when Num Lock is ‘off’.

When defining a route you may need to nudge the position of the handle by the defaultlinear increment for major positioning, and a fine value for accurate positioning, e.g.clearance from surfaces. To facilitate this a ‘fine nudge’ setting is available, where thegranularity of the movement is less than that of the current linear increments.

Linear increments are controlled from the Set Increments form.

Similar to the nudging using the + and - hotkeys, the fine adjustment uses the 2 and 8 keyson the numeric keypad.

Once a nudge has been performed, then dragging has no effect, but the mouse button muststill be held down. Where a nudge is applied to a position which is not derived from a snapto feature, then the offset value will be either positive or negative in the direction ofmovement.

With a position that has been derived by the intersection of the route line and a feature, thenudge will offset the solution plane to derive a new position. This allows you to position a legbehind or in front of a feature, and then apply a clearance.



5.7.7 Cardinal Direction HandlesThese handles allow you to select quickly one of the cardinal directions for defining the nextleg of the route. The Extend Route Handle will not be enabled until you select a cardinaldirection with either the left- or right-hand mouse button.

The same popup menu is available from a cardinal direction handle as is available from theExtend Route handle itself.

5.7.8 Free Rotation HandlesThe free rotation handles allow you to rotate interactively the Extend Route Handle aboutthe vertical axis and from the horizontal plane.

• DraggingThe rotation handle can be dragged using either the left- or right-hand mouse button, andallows a full 360° rotation about the relevant axis of rotation.

On dragging either of the Free Rotation Handles, feedback is given showing the direction ofthe Extend Handle (see below).



If no special actions (e.g. feature highlighting) are active, the handle rotates in multiples ofthe currently defined angular increments.

Dragging the handles with the right-hand mouse button is the same as using the left-handbutton, but you are presented with a pop-up menu giving the available options which relateto the drag.

Selecting a Free Rotation Handle using the right-hand mouse button presents you with acontext sensitive menu which relates to the direction and rotation of the handle, see PopupMenus on the QPR Handle.

• Feature HighlightingWhen performing a free rotate, if feature highlighting (see Feature Highlighting) is active, butno feature is identified, the rotation uses the currently defined angular increment value.When a feature is identified, the handle is aligned in the appropriate manner, dependent onthe feature identified.

• Nudging the HandleYou can adjust the Handle by a derived angular offset using the currently defined angularincrement using the + and - hotkeys for the rotation handle.

As with moving, if a direction is derived from an alignment with a feature, using the nudgeincrements the rotation from the derived direction.

5.7.9 Direction and Rotation CharacteristicsNote: All modifications to the length or direction of a route leg can be undone or redone

using the UNDO/REDO buttons. Changes which modify the direction of the handlecannot be undone/redone.

• Extend Route HandleYou can position the change in direction freely, relatively or by using other elements in themodel to derive a position.

The following are the various methods by which you can position the change in direction,other than by ‘freehand’ dragging of the handle, which is the default method of positioningthe handle.

• Explicit OffsetsThere two methods of performing a relative offset of the routing handle:

• Specifying a leg length• Offsetting from the previous position of the handle



These options are accessed from the popup menu on the handle, see Popup Menus on theQPR Handle.

In each case you are presented with a form which allows you to enter an appropriate length;you can also “preview” the effect of the specified value before committing the change. Alloffset distances are along the routing vector.

Leg Length

This method allows you to position the change in direction by specifying the length of theroute leg. A negative value positions the change in direction in the opposite direction to thatof the extend arrow.

Offset

This method allows you to position the change in direction by a distance that the handle is tobe offset from its current position.

• Distance from OriginThis method allows you to position the change in direction by a distance that the handle is tobe offset from the position of the previous component in the leg.



• Feature HighlightingFeature highlighting allows you to position the handle using other elements within themodel.

Feature highlighting options are available from the shortcut menu on the handle and fromthe ‘hotkeys’, see Popup Menus on the QPR Handle and Hotkeys respectively. All positionsprojected onto the routing vector are derived from a constructed plane.

By default the derived plane will be vertical or horizontal dependent on the approach routingvector. However, it is possible to cycle through derived solutions using the (Shift) hotkey,see Hotkeys.

Offset by OD of Type

By default when a feature is selected, the derived position is taken to be that of thecentreline of the tube. You can modify the derived position of the change in direction by ½the OD of the tube, including insulation. This offset will be applied normal to the solutionplane that is currently active.

It is possible to cycle through the three possible solution planes for the offset, i.e. in front,behind or through the relevant solution plane using the ‘O’ hotkey.



Orient to Feature

It is possible to direct the route extension handle to an identified feature. This is selectablefrom an option on the popup menu available on the handle, see Popup Menus on the QPRHandle.

The way in which the extension handle is oriented depends on the feature identified.Identification of a point feature directs the extension handle directly to the identified pointfeature.

Identification of a linear feature rotates the Extension Handle about the vertical axis of theRouting Handle (maintaining the angle from the horizontal) and directing the ExtensionHandle at a projected point on the projected linear feature.



Where it is not possible to derive a direction from the identified feature, or the featureproduces a 180° change in direction, then the feature is not displayed.

Alignment with Feature

It is possible to direct the Route Extension Handle so that it is parallel with an identifiedlinear feature, using the Align with Direction… popup menu option on the handle.

It is possible to toggle (using the Shift key) between the initial derived direction of theidentified feature and the opposite direction.

It is not possible to select a direction which is directly opposite to the leg preceding theRouting Handle, i.e. 180° changes in direction are not possible.

When identifying a Branch leg, whether the one being defined or in another Pipe, then thedefault direction is the flow direction of the Pipe.

• Explicit DirectionThe direction of the Extension Handle can be set to an explicit direction, using the ExplicitDirection… popup menu option on the handle.

The Enter Direction For <direction> Axis form is displayed which allows you to specify thedirection with respect to the current frame of reference.



It is not possible to specify a direction which is opposite to that of the leg preceding therouting handle.

• CompleteWhen using the right-hand mouse button to identify a feature, if the End Route Handle isidentified as a linear feature, you are given the option to complete the route.

The End Route Handle can be interpreted as either a point or direction (linear feature). Forthis reason the option of completing the route is only available when the handle is identifiedas a linear feature.

Where the leg being extended and the End Route Handle physically intersect, theComplete option will create a leg between the derived position of the alignment and the endof route.

When the leg being extended and the End Route Handle do not intersect, the Completeoption will create two legs, one being the shortest distance between the extend route andend route vector, the other being from the End Route Handle and the mapped position onthe end route vector.

Where the End Route Handle is directed into the last leg, then QPR aborts, as there is no ill-defined pipe remaining in the route. If the End Route Handle points out of the last leg, youwill remain in QPR.

• ConnectWhere an end of the route is undefined, you can designate an appropriate element as thepoint the end is to be connected to.

There are two possible ways in which you can define a connection for the free end of aroute, these are:

Using the pointer - this allows you to identify a permissible connection without modifyingthe route. This is accessed by an option on the pop-up menu for the handle.



Identifying an appropriate feature - as this requires you to make a decision once anappropriate feature has been identified, this option is only available when dragging theExtend Handle using the right-hand mouse button.

A permissible connection is defined as an element that can have a Branch Head or Tailconnected to it, and which does not have a connection already associated with it.

When in feature highlighting mode, the permissible connections are the p-points ofComponents which are unconnected. If a p-point is already connected to, then it is handledas any other feature and the Connect option is not available.

Where the pointer is being used to identify a Connection, you only need to identify elementswhich have a free Connection. The appropriate point on the element to which theConnection is to be made is automatically determined. However, where an element hasmore than one Connection, e.g. CROSS, PCOM, etc. the system either tries to determinethe appropriate p-point from the pick or highlights the p-point which can be connected to.

• Rotation Handles

You can freely direct the Extend Route Handle about the vertical or horizontal using theRotation Handles. The Rotation Handles have their own popup menus for direction, seePopup Menus on the QPR Handle.

By default, dragging either handle rotates the Extend Route Handle about the appropriateaxis by the currently defined Angular Increments.

Feature Highlighting

Where feature highlighting is active, then the derived direction for the Extend Route Handleis constrained about the appropriate axis of rotation.

This means that when rotating using the “vertical” handle, the direction derived will betowards the identified feature, but the angle from the horizontal is maintained. When usingthe “horizontal” handle, the projected direction of the Extend Route Handle on the horizontalplane is maintained and the angle from the horizontal will be derived.



5.7.10 Feedback

There are several types of feedback, which relate to the handles. These are:• Highlighting - used to inform you which handle is beneath the pointer, which will be

selected when picked. Its representation is a highlighted version of the dragginghandle.

• Dragging - this uses a stylised version of the selected handle, adapting to variationson a theme depending on the position, state, etc. All routing handle sub-handlesdisappear while this handle is active

• Informational - when performing a drag, any alphanumeric information relating to theoperation (for example, ‘Leg length 500.0’ above) is presented to you.

• Extend Route Handle

Highlighting

Passing the pointer over the handle when not performing an action causes the pointersymbol to change and, the Extend Route Handle will highlight to differentiate it from theother components of the routing handle. In addition, the current direction of the handle willbe displayed.

• DraggingWhen dragging the handle, the system displays only the stylised handle. The CardinalDirection and Free Rotation handles disappear.

Once the handle is moved from its original position, then the offset from the original positionis displayed adjacent to the handle. Where the original position necessitates a change indirection, the length of the leg will also be displayed.



Where the original position does not result in a change in direction, or start of a Branch, thenthe length of the leg is shown half-way along the leg being extended.

• SnappingWhen identifying a feature, the supplied feedback informs you of the type of solution planeand the derived position.

Information Feedback

In addition to the feedback of the feature identified and the distances moved, feedback isgiven to inform you of any extra information used to derive the position.

Where a reference plane has been shown, the feedback informs you of the type of planeused, i.e. horizontal, vertical or normal along with any offset applied. The plane type isdisplayed as a text string at the mid-point between the pointer position on the feature andthe derived position on the plane.

Where the plane is offset, the system gives a representation of the offset applied:



Offsetting Planes

On identifying a feature which displays a reference plane, an offset handle is displayed toenable you to modify the offset of the plane.

The handle is shown at the pointer at the initial point on the feature when it is selected. Theorientation of the handle is normal to the reference plane displayed, therefore if the type ofplane is changed, e.g. from horizontal to vertical, then the handle is redisplayed at thepointer and in the correct orientation.

Moving the cursor over the “blob” at the end of the handle offsets the plane to the relevantside of the original derived position. The highlighted feature and handle remain the same,but the plane will be offset to the correct position.

Losing focus on the handle, but returning to the original identified feature or moving over thejoining line between the two blobs, will reposition the derived plane back to its originalposition.

• Cardinal Direction Handles

Highlighting

By default when the pointer passes over one of Cardinal Direction Handles when notperforming an action, the cardinal direction is highlighted and the original Extend Route



Handle disappears. Where the focus is lost from the handle, then the original Extend RouteHandle will reappear.

On selecting the cardinal direction, the Routing Handle changes to suit the selecteddirection.

• Free Rotation Handles

Highlighting

When you pass the pointer over one of the handles when not performing an action, thepointer changes and the handle is highlighted to show the rotation direction of the handle.The current direction of the handle is also displayed.

Dragging

When dragging the handle about the horizontal or vertical axes, only the Rotation Handle isdisplayed, all other handles are removed.

5.7.11 Popup Menus on the QPR Handle

• Extend Handle

Before Drag

The following options are available on the Extend Handle before a drag.



Menu available where both ends of the ill defined route are well defined:

Option Description

Enter Offset… Gives a form which lets you enter an offset from thecurrent handle’s position in the current routing direction.

Enter Leg Length… Gives a form which lets you enter an absolute distance ofthe handle from the last previous change in the direction’sposition.

Distance From Origin… Displays a form which allows you to enter an absolutedistance of the handle from the previous Component’sorigin position.

Extend Through Feature… Allows you to identify features with which to align, alongthe current route direction.

Orient to Point… Directs the handle either directly to a point feature orrotates about the vertical axis, maintaining horizontaloffset, when a linear feature is identified.

Align with Direction… Allows you to identify features with which the handle is tobe aligned.

Explicit Direction… Displays an input form which allows you to explicitlyspecify the direction of the handle.

Component Choice > Allows you to select the type of Component that is createdby the Routing Handle when a change in direction occurs.The Component can be set to either Elbows or Bends.

Distance Feedback > Allows you to select how the Routing Handle displaysdistance feedback. This can be set to either Offset (offsetfrom the previous handle’s position), Leg Length(distance of the handle from the last previous change indirection’s position), or From Origin (distance of thehandle from the previous Component’s origin position).



The following options are only available where the end being routed to is ill-defined, i.e.there is no End Route Handle displayed:

On Completion of a Drag

The following options are available on the Extend Handle on completion of a drag, i.e. whenthe secondary mouse button has been used to drag the handle.

The following options are the defaults when no special actions are active:

The following options are available when in “snap to feature mode” and the end beingrouted to is ill-defined or unconnected and the identified feature is a connectable p-point ofan item to which an end can be connected, e.g. a Nozzle with no connection reference set:

The following options are available when in “snap to feature mode” and the end beingrouted to is well-defined and the identified feature is the End Route Handle:

Show Rotation Handles… Allows you to show/hide the rotation handles.

Cancel Returns the handle back to its original state before thedrag

Option Description

Connect To… Allows you to use the pointer to select an element whichthe route end can be connected to, e.g. unconnectedNozzles, Tees, etc.

Option Description

Extend Leaves the handle at the shown position

Cancel Returns the handle back to its original state before the drag

Option Description


Connect Leaves the handle at the shown position and connects the ill-definedend to the identified target.

Connect and Complete

Establishes a connection to the identified item and completes the routeand aborts the route mode when applicable,


Option Description


Complete Completes the route and aborts the routing mode when applicable.


Option Description



• Free Rotation Handle

Before Drag

The following options are available on the Free Rotate Handles before a drag.

On Completion of a Drag

Option Description

Enter Value… Displays a form which allows you to enter an angle for thecurrent Rotation Handle.

Orient to Point… Directs the handle either directly to a point feature orrotates about the vertical axis, maintaining horizontal offset,when a linear feature is identified.

Align with Direction… Allows you to identify features with which the handle is tobe aligned.

Explicit Direction… Gives a form which allows you to enter an explicit directionfor the z-axis of the handle.

Component Choice Á Allows you to select the type of Component that is createdby the Routing Handle when a change in direction occurs.The Component can be set to either Elbows or Bends.

Distance Feedback Á Allows you to select how the Routing Handle displaysdistance feedback. This can be set to either Offset (offsetfrom the previous handle’s position), Leg Length (distanceof the handle from the last previous change in direction’sposition), or From Origin (distance of the handle from theprevious Component’s origin position).

Show Rotation Handles… Allows you to show/hide the rotation handles.




5.7.12 HotkeysThe following ‘hotkey’ options are available for Routing Handle manipulation options:

Exercise continues:

138. Select Design>Equipment from the main menu. Add a third tank to the design usingthe same method as that used previously to create the first storage tank. Thedifferences are that the Explicit Position form should look like this:

Option Description

Rotate Leaves the extend handle at the shown direction.

Cancel Returns the handle back to its original state before the drag.

Hotkey Handle Description

Esc All Aborts the current operation in the correct manner.

All Cycles through derived directional alignments.

D All Cycles through Offset/Leg Length/From Origindistance feedback options.

F All and when in ModelEdit mode

Toggle switch for feature highlighting (orSelection>Feature Highlighting).

O Extend Route Cycles through the offsets when aligning withfeature highlighting.

P Extend Route Cycles through the solutions for the derivedposition when aligning using feature highlighting.

+ All Increment linear offset or angular rotation bydefault increment setting.

- All Decrement linear offset or angular rotation bydefault increment setting.

Extend Route Increment linear offset from current position by“fine linear increment” value.

Extend Route Decrement linear offset from current position by“fine linear increment” value.



And on the Create Nozzle form your input data should be:

Your design should now look as shown:

139. You will now route a pipe between Nozzles Pump-1-DISCHARGE and Tank-3-N1.Select Design>Pipework from the main menu.

140. Using a similar process to that described previously, create a new pipe, called Pipe-2,between Nozzles Pump-1-DISCHARGE and Tank-3-N1, setting Pump-1-DISCHARGEas the Head and Tank-3-N1 as the tail:

• Name: Tank-3-N1

• Position: West 1675

North 0

Up 2750

• Orientate P1 is: W

• Height: 300



Note: The dotted line that represents the pipe route between the two nozzles.

141. Select in the Design Explorer the Branch you have just created and add a Flange andassociated Gasket.

142. Enter the Model Editor and click anywhere on the dotted line that represents the piperoute for Pipe-2. When you select the line, you will see the Routing Access Handlesdisplayed at either end of the route:



If you select the End Route Handle, then the handles will switch about. Note that if youhave an ill defined end there will be no End Route Handle.

143. Right-click on the West axis Quick Routing Handle at the Tail of the route and choosethe Extend Through Feature option from the pop-up menu:

This allows you to select a Feature that defines the plane to which the pipe extends:

144. Click on point P2 of the Flange. The system will extend the pipe to the defined planeand insert an Elbow with implied tubing attached:



145. Viewing from a different angle, you will see that the pipe has extended exactly the rightamount to bring it level with the nozzle on the pump:

146. Right-click on the South axis of the Quick Routing Handle and choose the ExtendThrough Feature option from the pop-up menu. Click on point P2 of the Flange. Thesystem will extend the pipe to the defined point and insert an Elbow with implied tubingattached



147. Right-click on the Down axis of the Quick Routing Handle and choose the ExtendThrough Feature option from the pop-up menu. Click on point P2 of the Flange. Thesystem will extend the pipe to the defined point and insert an Elbow with implied tubingattached:

148. You can complete the route by adding a Flange to the Elbow nearest Tank-3 andensuring the Skip Connected Comps checkbox on the Component Creation form isunchecked. When you have added the Flange, drag it to the Nozzle in the Model Editor. Your final design should look as shown:



5.8 Deleting Pipe RoutesIt is possible to select graphically contiguous components of the same pipe or branch by thefirst and last component of the range and then delete them in one operation.

Exercise continues:

149. Click the Delete Range of Piping Components icon on the Pipework toolbar:

150. Select the first component in the range you want to delete:



151. Select the last component on the range you want to delete. The system will highlightthe components between the first and last ones and ask you to confirm you want themdeleted:



152. Click the Yes button and the system will delete the components you selected:


Pipework Design User GuidePipework Modification

6 Pipework Modification

This chapter shows how pipework components can be modified and the way in which pipescan be split.

6.1 Pipework Component Bore and Specification ModificationThis utility provides facilities for you to modify the bore or specifications of one or all of thecomponents in a pipe or branch. In addition to these modifications, the utility also allows thesetting of insulation and tracing specs. The utility does not modify the branch or pipespecifications. The same Modify Components form is used for modifying both componentspecification and bore.

To display the Modify Components form, in Design - Pipework Application navigate tothe required pipe or one of its branches and select Modify>Pipe>Component bore/Specification or Modify>Branch>Component bore/Specification from the main menubar.



6.1.1 Modify Components Form

The Modify Component form is a multi function form able to change both specificationsand bores. When it first shown, the form contents are based on the contents of the currentbranch or pipe depending on which was selected from the menu.

Component List tab - with this selected the following are available:

Current Element button - allows you to move to another pipe or branch and select itscontents instead.

Select from graphics button - accepts a group of components selected graphically andhighlights them in the Component List.

Insulation Spec check box - checking shows the insulation settings in a separate columnon the form.



Tracing Spec check box - checking shows the tracing settings in a separate column on theform.

The scrollable list panel has the following columns:

Apply changes to like components check box - checking applies one component changeto all like instances in the Component List.

6.1.2 Component SelectionA series of components can be selected graphically using the fencing selection method.Clicking the Select from graphics button accepts the selection and highlights thecomponents in the Component List.

Components can be added or removed by holding down the Control key and graphicallyselecting or deselecting individual elements.

• Design Element - The components in the selected branch or pipe

• Component Description - A description of the component

• ABORE - The bore at the p-point where the flow enters thecomponent

• LBORE - The bore at the p-point where the flow leaves thecomponent

• PBORE - The bore at any of the p-ponts regardless of theflow direction

• Spec Component - Current specification of the component

• New Spec Component - New specification of the component

• New ComponentDescription

- A description of the new component



Modification Options

The options available are accessed by right clicking over a selected field to display a pop-upmenu. In each case the modify option applies only to the selected list highlighted on theform.

The options are:

• Modify Specification - Modifies the specification of the componentsselected in the list

• Modify Bore - Modifies the bore of the components selected inthe list

• Modify Insulation Spec - Modifies the insulation specification of thecomponents selected in the list



6.1.3 Modifying Component SpecificationTo modify the specification of a set of components, the Modify Specification option isselected from the pop-up menu. The Select Piping Spec form displays, prompting the userwith a drop-down list of available specifications.

Note: Normally any items which are not in the same spec as the current branch are ignoredby this process. This allows for items such as pipe supports and special componentsto remain untouched.

Apply changes to out of spec check box - checking forces the selection process to look atall components regardless of their original specification.

A new specification (e.g. A300) is selected from the drop-down list and clicking OK actionsthe search process to find equivalent components in the selected specification. TheComponent List is refreshed to show the new components.

At this point the form only contains a suggestion of what the new components will be and itdoes not make any changes to the design.

• Modify Tracing Spec - Modifies the tracing specification of thecomponents selected in the list

• Choose component - Allows you to choose an equivalent componentwhere the modification process fails to offer acomponent complying with the new specification orbore

• Select All - Selects all of the components in the list

• Clear componentselection

- Deselects all the selected components in the listallowing you to restart the selection process



Any items which could not be found in the new specification are listed as having ‘Noselection available’ and will not be changed if the other changes are applied.

A selection summary panel is displayed at the bottom of the form to show the results of thespecification selection process.

6.1.4 Error Messages With the Error Messages tab selected, the Modify Components form lists the componentselected for modification which produce an error in the selection process. When theselection process takes place, each selected item is scanned to find an equivalent in thenew specification. Where an item cannot be found, an error is indicated with a description inthe error list.

An example is shown:

6.1.5 Choosing a ComponentFor items where no selection is available, you may opt to choose the component by right-clicking over the component field and selecting the corresponding option available from thepop-up menu.



This displays the CHOOSE OPTION form as shown:

The Specs tab is selected first to set the new specification. The Components tab is thenselected so that an equivalent item can be chosen from a scrollable list of suitablecomponents.



Clicking OK adds the selected equivalent component to the Component List on the ModifyComponents form. Once the selection is complete, clicking the Apply button changes thecomponents for ones complying with the new specification.

These component changes are shown in the graphical view.

The before and after graphical views are as shown:

If the changes are unacceptable, the Undo button reverts back to the original design.

6.1.6 Multiple Component ChangesYou may wish to apply one component change to all like instances in the list where noalternate selection is available.

To do this the 'Apply changes to like components' check box should be checked. Withthis option applied component changes will automatically be applied to all elements in thelist that have the same type as the one being changed via the above process.

6.1.7 Modifying Component BoreTo modify the bore of a set of components, navigate to the required pipe or branch andinvoke the Modify Components form from the main menu bar as previously described. Theform once again shows a Component List based on the selected pipe or branch.



The components required for bore change are selected graphically, which highlights them inthe Component List as before. The Modify Bore option is selected from the right-click pop-up menu to display the Select Bore form, with a drop-down list of available bore sizes.

The required bore is selected from the list and clicking OK populates the Component Listwith the new bore size.

If the results are satisfactory, clicking the Apply button, accepts the changes. Selecting theError Messages tab will display a list showing any anomalies and these can the becorrected by inserting or deleting reducers.



If the above process results in some items having no selection available, you can opt tochoose the component using the same method as in modifying the ComponentSpecification.

Selecting the “Choose component” option form the right-click pop-up menu displays theCHOOSE OPTION form as shown.

Specs tab selected:

Components tab selected:



6.1.8 Modifying Insulation and Tracing SpecificationsThe insulation and tracing settings are not shown on the form by default because they arenot the most commonly used functions. To activate these and show the current values, theInsulation Spec and Tracing Spec check boxes need to be selected.

Here there is no insulation on the visible components so '-' is inserted in the list.

When you wish to change an insulation or tracing specification, the appropriate option ischosen from the right-click pop-up menu. A list of available specs is shown in the displayedform and the required one is selected. Clicking OK automatically changes the spec andrefreshes the Component List. In this case, there is no requirement to click the Applybutton on the Modify Components form.

After clicking OK, the new Insulation spec list is as shown.



6.2 Pipe SplittingThis utility allows pipes to be split at a defined point. Pipes may be split into segments withinthe same branch, new branches or new pipes. At split points, the system allows breakcomponents such as flanges sets, couplings etc to be inserted. Multiple pipes may be spliton single plane.

To display the Split Pipe form, in Design - Pipework Application select Utilities>PipeSplitting...

The split utility form displays as shown.



6.2.1 Multiple Mode Splitting

Elements to Split

In multiple mode, the system allows the user to collect a group of pipes in the graphicswindow using a variety of methods. These methods are only available when the user wantsto split a group of pipes using a plane.

Add CE

Allows you to navigate to any element in the hierarchy and add it or any pipes underneaththe current element to the splitting list.

Add Selected

Allows you to select a number of pipes in the graphical window by dragging a crossingwindow across the required pipes with the mouse cursor. The selected pipes are then addedto the splitting list by clicking the Add Selected button.

ID Selection

This method is similar to the above method, however, you can dynamically update the list bypicking any pipe component. To add pipes to the list, the ID Selection button is clicked and



then the mouse cursor used to identify pipes to add to the list. When you have finishedselecting pipes to add, the escape button is clicked to end selection.

Clear all

Clicking this button empties the entire Elements to Split list.

Modifying the Splitting List

Individual pipes can be removed from the splitting list by clicking the right mouse button overan element to be removed from the list. This displays a Remove from list button.

Clicking the Remove from list button removes the pipe from the splitting list.

Split Pipe Options

The next part of the form allows you to select what happens to the pipes when they are split.

There are three options:

1. Split pipes on a plane - split the pipe by inserting an assembly component at theplane intersection point

2. Split pipes into segments - split the pipe into a number of segments using userdefined dimensions. The splitting is defined between two points that are selected byyou, (selection of these points can be achieved by using either the feature picking orcomponent picking option).



3. Split pipe by moving Component - split the pipe at the split point and insert anassembly component at that point. The remaining components in the branch will thenbe added to a new branch

Component Creation Options

When splitting a pipe there are a number of options for specifying where new componentsare created.

Existing - components are inserted at the split position in the currently selected branch.

New Pipe - Components are inserted into a new pipe in the hierarchy.

New Bran - Components are inserted in a new branch under the current pipe hierarchy

6.2.2 Splitting Pipes with a Plane

Plane definition

Having decided how to deal with the split, the next phase is to create a split plane by clickingthe Create Plane button. The first prompt is to identify the leg of any of the pipes to be splitin the direction of the split. This determines the direction of all of the other pipes cutting theplane. The next prompt is to build the plane itself using the graphical interaction control todefine the plane. All the standard pick operations are available, including Graphics to pick asurface, or intersections to define the intersection points of two objects or lines. Thefollowing example uses the intersection of two steelwork members.



By default the plane is shown as a wireline representation centred around the defined planeorigin. To enable you to visualise the plane better, it can be increased in size and filled usingthe Plane Size and Fill options. In the example below, the plane is increased in size andfilled.



After the plane has been defined it may be adjusted so that it is in front or behind the derivedposition by a given distance. The options are shown:

In the example, the plane is moved in front of the original position by a distance of 500mm.



Filter Assemblies By

The items used to split the pipe are selected from the assembly list. In the example, onlyone is available so when the split is performed, a flange set will be added at the split point.



Assembly Build Origin

The final option available for plane splitting is the assembly build point; you need todetermine whether to build to the primary or secondary origin of the assembly.

The primary and secondary origin points allow some control over where the assembly ispositioned relative to the splitting point.

One of the most common types of assembly is likely to be a set of break flanges where therelevant points for positioning the assembly are on either flange face. In this case theprimary origin point would be defined as the the leave point (upstream flange face) and thesecondary origin would be defined as being the arrive point (downstream flange face). Arepresentation of the splitting procedure is as shown:

Further information on Assembly creation and usage is provided in Piping Assemblies.



Applying Splits

When a suitable plane has been created, you are free to start the pipe splitting process.There are two ways pipes can be split. These are as follows.

Using the List of Defined Elements

When there is a defined list of pipes, clicking the Split button splits the pipes.

At this point you are prompted to confirm if the split points are acceptable and the changescan be accepted or rejected. If rejected, the process is restarted.

The resulting split is shown:



ID Splitting

You can also split pipes using a defined plane by directly picking pipes using the mousecursor. To do this click the ID Split button and then use the mouse cursor to select pipes thatwill be split relative to the existing plane.

The Undo button enables you to undo any changes that have been made to the model.

6.2.3 Single Mode SplittingIn addition splitting on a plane, a single branch may be split into segments of a given length.This option is selected in the Split Pipe Options panel and allows splitting to be done byeither Component picking or Feature picking. As a result of this, the branch list is greyed outand Plane definition panel is replaced by the Split Pipe Length panel as shown:



Split Pipe Length

This option allows pipes to be split into segments of a particular length between selectedcomponents or selected features that are adjacent to the pipe. Again the split is made byinserting split components into the branch. In this case, the downstream components ateach split may be inserted into the existing branch, a new branch or a new pipe dependingon the Move down-stream components to setting. If a new branch or pipe is requested,the new items are given a default name based on the pipe name.

Minimum Final Tube Length - restricts the length of the final tube to the final length value.If the final tube length is below this value, the previous spools are adjusted to make the finallength within its tolerance.

6.2.4 Component Picking

To make a split, enter the required split length and then click the Split button. You are thenprompted to select a start and end component between which the pipe will be split. In theabove pipe, the start and end flanges are selected. The result is shown:



Accepting the splitting arrangement results in flanges being inserted at the split points asshown:



The split length is defined as tube length (Segment Length) or spool length (Cut-pipeLength) so in this case, it is either the length from face to face of the flanges or the tubelength between flanges. Tube length around bends and elbows is calculated as thecentreline length.

6.2.5 Feature Picking Feature picking is very similar to component picking except the start and end points of thesplitting operation can be determined by reference to other parts of the model such asstructural steelwork.



The user starts the splitting process in the same manner as for component picking.

In this example splitting is to be done between the connecting flange from the mountedequipment to the neutral axis of of steelwork A.

The process is started by clicking the Split button at the bottom of the Split Pipe form, youare then prompted to pick the branch that the splitting will be applied to.

A feature or component can be picked for either the start or end point of the splitting. In thiscase the connecting flange on the equipment is picked.

This displays the starting point for the split and also gives an indication of current flowdirection (it is possible to split from either end of a pipe).



The end position to split to can now be picked. This will be a feature on steelwork A so thissteelwork is identified by hovering the mouse cursor over it and pressing (and holding) themouse button.

It will be noticed that the display of the steelwork has changed to show the individual Plinesthat make up the profile shape of the member being selected. The neutral axis has beenchosen for this piece and the selection is displayed in the upper left corner of the windowabove. Releasing the mouse button finlises the selection.

The splitting function will now prompt you to select the piece of tubing that the end point willintersect with. (In this case it is the horizontal section of tube that passes steelwork A)



The function will now insert an assembly at the intersection between the selected feature onthe steelwork and the selected tube and will continue to split between the start and end pointas per the component splitting method.


Pipework Design User GuideChecking and Outputting Design Data

7 Checking and Outputting Design Data

In this chapter you will learn about:• methods of checking for errors and inconsistencies in the pipework layout• checking for clashes (spatial interferences) between design elements• how to output a design data report derived from the piping model• how to generate an isometric plot.

Note: These facilities are available from all DESIGN applications, so you can readily checkand output data from any combination of DESIGN disciplines.

7.1 Checking for Design Data InconsistenciesThe Data Consistency Checking Utility reports the following types of occurrence (andother similar errors) in the design:



7.1.1 Design TolerancesThe misalignment between adjacent components can be measured using any of threeparameters:

• the offset distance between their p-arrive and p-leave axes• the displacement angle between their p-arrive and p-leave axes• the ratio of the offset to the projected distance between the p-arrive and p-leave p-

points (equivalent to the tangent of the angle parameter).

You can specify maximum permissible values for any of these parameters, as well asminimum acceptable lengths of tube between components. (You can specify differentminimum lengths for different bores if you wish.) If any part of the design falls outside thecurrent limits, an error message will be displayed.

Exercise continues:

153. To check your design for data consistency errors, select Utilities>Data Consistency.The Data Consistency Check form displays as shown.

x = OFFSET

y

RATIO = x/y = tan(ANGLE)

ANGLE

p-arrive

p-leave

connect ingtube



154. View the default values for piping design tolerance settings by clicking the Parameters:Piping… button to display the Piping Consistency Check Options form. You will usethe default values for all piping design tolerance settings, so have a look at them thenCancel the form.

155. You can send the error report either to your screen or to a file. You will view it onscreen, so select the Output: Screen button.

156. The Check list lets you specify how much of the design model you want to check in asingle operation. You will check each branch separately, so select Branch from the list.

157. Navigate to the branch /Pipe-1/B1 and click Apply to initiate the data checkingprocess.The resulting diagnosis is shown in the scrollable text area at the bottom of the form.There may be messages about unknown SKEYs, but ignore these.

158. Repeat the check as described for branch /Pipe-1/B2. The result overwrites the preceding report.

It is good practice to run a data consistency check whenever you have created or modifiedany significant amount of the design, typically before you choose Design>Save Work.



It is particularly important for your design to be free from data consistency errors before yougenerate isometric plots for fabrication and/or erection purposes, otherwise you could getsome very confusing results.

7.2 Checking for ClashesThe types of clash identified depend on two factors:

• The obstruction levels of the clashing elements• The current touch and clearance tolerances

7.2.1 Obstruction LevelsAll design primitives and all catalogue primitives have an obstruction attribute (OBST) whichdefines the physical type of obstruction which the primitive represents:

• A hard obstruction (OBST=2) represents a rigid and impenetrable object, such as asteel beam or a plant vessel.

• A soft obstruction (OBST=1) represents a volume which is not solid but which needs tobe kept clear for access.

• Any primitive with OBST=0 represents a freely accessible volume and is ignored forclash checking purposes.

7.2.2 Extent of ClashingAs well as distinguishing between hard and soft clashing items, the checking utilityrecognises three categories of clash between them, depending on how far the two primitivesintrude on each other’s allocated space. These categories are:

• A physical clash: the primitive volumes overlap by more than a specified amount. Thisusually means that a definite interference exists.

• A touch: the primitives either overlap by less than the amount needed to cause a clashor are separated at their closest point by less than a specified distance. This maysimply mean that one item is resting upon another as intended, or it may indicate aproblem.

• A clearance: the primitives are separated at their closest point by more than theamount necessary to constitute a touch but less than a specified clearance distance.This represents a near miss, which you may want to investigate.

These three classes are illustrated below for the clash specifications:• Touch limits: 5mm overlap to 2mm gap• Clearance limit: 8mm

so that the following criteria apply:• If the items overlap by more than 5mm, a clash is reported• If the items overlap by less than 5mm, a touch is reported• If the items do not overlap but are separated by less than 2mm, a touch is reported• If the items are separated by more than 2mm but less than 8mm, a clearance is

reported• If the items are separated by more than 8mm, no interference is found



7.2.3 Clash Detection ProcessEach element which is to be checked for clashes has its own geometry checked against thatof all other elements which are specified by a current obstruction list. Items which are notin the obstruction list are ignored during the clash checking operations. By default, theobstruction list includes all elements in the database, so that each element to be clashchecked is tested against every other element. To control the amount of checking carriedout in a large database, you can restrict the obstruction list to a few specific elements and/oryou can specify a 3D volume (the clash limits) within which the clash checking is to beconfined.

To highlight the locations where clashes are found, the clashing and obstruction items areshown in contrasting colours in the graphical view (two shades of red, by default).

Exercise continues:

159. Use the default values for all clash checking settings. To see what these are, selectSettings>Clasher>Defaults to display the Clash Defaults form. Think about themeaning of each setting shown (refer to the preceding introduction); then Cancel theform.

160. Check all of your piping components (that is, the whole of /PIPEZONE) for clashesagainst the three equipment items (in /EQUIZONE). The default obstruction list (allelements in the current DESIGN database) includes both piping and equipment items (/PIPESITE). To edit this, select Settings>Clasher> Obstruction>List. This displaysthe Add/Remove Obstruction Items form. Remove all current entries and then Addthe equipment zone.• Select All in the Obstruction List and click Remove• Select EQUIZONE in the hierarchy and click Add• To close the form select Control>Close

161. Navigate to the piping zone which you want to check and select Utilities>Clashes.The Clash Display form appears. The left-hand side of this form controls the clashchecking process; the right-hand side consists of a 3D view in which you can look indetail at any clashes diagnosed. Select Control>Check CE from the form menu bar torun the clash checking process and, when completed, study the Clash List whichshows any clashes found.In your case this should simply say None.

Note: If the Auto Clash button (in the main toolbar) is in the ‘On’ state, each new elementthat you create is checked immediately for clashes as the design is built up. This canslow down progress when you are adding many new elements, but is very usefulwhen you want to add a few new items to an existing design which has already beenchecked for clashes.

overlap > 5mm overlap < 5mm 2mm < gap < 8mm

a physical clash touches a clearance

gap < 2mm



7.3 Generating a Data Output ReportThe reporting utility lets you read selected information from the database and present theoutput in a tabulated format. Each report can be customised by specifying some or all of thefollowing:

• Where the output is to appear (on the screen or in a file ready for printing).• Any introductory header which is to appear at the beginning of the report.• The page length (if the report is to be paginated).• The page layout, including number and positions of columns, column headings, etc.• Any headers and footers which are to appear at the top and bottom of each page.• The selection criteria which define which data settings are to be included in the report.

Once such a report has been designed, its specification can be saved for future use inthe form of a report template file. The ways in which you define how a given report isto be generated and presented are beyond the scope of this exercise, but you will lookat the results of the process by using a pre-prepared template which outputs a materialtake-off list showing the length of tube needed to build your design. (You will probablyuse your company standard templates for most reports anyway, in which case this isthe method you would normally use in practice.)

Exercise continues:

162. Select Utilities>Reports>Run to initiate the reporting process. This displays FileBrowser listing all files in the current reporting directory (specified by your SystemAdministrator as part of the project set-up procedure).

163. Navigate to the ...\REPORTS\TEMPLATES directory by clicking on it in the Sub-directories window. All files with a .tmp suffix are report templates.

164. Select pipe_mto.tmp, which has been designed to produce a material take-off reportlisting all components, including tubing, in the piping design.

165. Click OK on the File Browser.The Report Details form that displays requires you to specify:• where the report is to appear• what part of the database hierarchy is to be read when extracting the required types

of data.

166. Complete the Report Details form as follows:• Leave the Filename text box empty (this sends the report automatically to the

screen).• In the Hierarchy text box, enter /PIPESITE (this lists the tubing requirement for the

whole of the piping design model).• Click OK to run the report.

A tabulated report output is displayed in a Command Output window which isopened automatically.



This report shows the number of each type of component used in the design and thetotal length of tube needed to interconnect them. (Do not worry if part of the headingseems inappropriate for your project; this wording is written into the template simply asan example of the type of heading which you might want to use.)

7.4 Generating Isometric PlotsThe isometric plotting module of PDMS provides very powerful facilities for generating anyspecified isometric view of all or part of the pipework design, with associated parts lists andannotation, with a very high degree of user control over the output format. You will use just asmall part of this power to produce a plot of your design using the default settings only.

Note: Before you proceed further, you must have carried out the data consistency checksspecified previously and achieved an error-free report.

Exercise continues:

167. To change to the isometric plotting module (called ISODRAFT) , selectDesign>Modules>Isodraft>Macro Files. Click YES to confirm that the database is to be updated to save any design changes;ISODRAFT then loads and the screen changes to show the ISODRAFT menu bar, anExplorer window and an empty 2D View window.



This menu bar gives you access to a wide range of facilities for generating customisedisometric plots to suit all likely purposes. For the purposes of this exercise, you willsimply generate a standard isometric for the whole pipe (i.e. both branches) usingdefault settings for all options.

168. Navigate to /Pipe-1 in the Explorer and then select Isometrics>Standard. TheStandard Isometric form displays which lets you specify which parts of the pipingdesign are to be detailed in the plot and which of the standard drawing formats is to beused. Select Standard iso option: BASIC.MET.



169. Click Apply to initiate the isometric plotting process.The status bar displays the message Please wait, detailing in progress while theisometric view is composed, the dimensioning annotations are calculated, and thematerial take-off report is compiled. On a large process plant model this could take afew minutes, but with your very simple model it should take only seconds. Whenprocessing is complete, the following new windows are displayed:• Isodraft Messages shows a log of the detailing process, including reports of any

potential problems encountered:

• Display List shows all isometric plots which have been created so far and whichare available for display. In your case there is only one, so it is selected for displayautomatically, thus:

• Display Isometric consists of a 2D graphical view showing the plot currentlyselected in the Display List. The current display should look like this:



The same data is also sent automatically to a file in your current operating systemdirectory, ready to be sent to a plotter if a hardcopy version is required. Such filesare named by default with a sequential number of the format plot00x, where x isincremented from 1 in this case plot001

170. Using the same standard layout, generate separate isometric plots for each of thebranches /Pipe-1/B1 and /Pipe-1/B2. Compare the information on each of these withthe overall plot of /Pipe-1.

Note: Printed plots of all three isometrics are in Sample Plots.


Pipework Design User GuideAutomatic Pipe Routing

8 Automatic Pipe Routing

8.1 Automatic Pipe Routing using PDMS Router

8.1.1 IntroductionPDMS Router is a rule-based tool which enables you to route pipe networks automaticallyand to position piping components.

Before you can start to use the PDMS Router, you must create the Pipes you need, andconnect or position their Heads and Tails. PDMS Router begins routing from the head of apipe and ends the route at the pipe’s tail. The flow direction is always forwards (from Headto Tail).

When you route a pipe, PDMS Router will automatically:• Create clash-free orthogonal routes which use the minimum length of pipe and as few

elbows and bends as possible. You can include non-orthogonal sections of pipemanually.

• Add elbows, reducers, flanges, gaskets and welds, providing they are available in thecatalogue.

• Position piping components such as valves.

• Work-pointsWhen you add a pipe to PDMS Router, it is given a head and tail work-point. These are thepoints where a route begins and ends. PDMS Router positions work-points at a distancefrom the branch head or tail which allows for any connection components that are required.For example, if the head of a branch is a flanged nozzle, then PDMS Router willautomatically add a gasket and a flange. PDMS Router will then begin routing the pipe fromthe end of the flange, as shown in Figure 8:1.: Example of a work-point.

W ork-p oint Wo rk-poin

Tube added if speci fied in COC O table



Figure 8:1. Example of a work-point

• How PDMS Router Finds a RouteThe PDMS Router creates a route using an algorithm which minimises material cost whileavoiding clashes with other objects. The algorithm has three modes of operation, describedas Level 1, Level 2 and Level 3 modes. PDMS Router first searches for a route using Level1 mode. If no clash-free Level 1 route is found, a search is made using Level 2 mode, and ifno Level 2 route is found Level 3 mode is used.

The details of the three levels are explained in the following sections.

- Level One Mode

In level one mode, PDMS Router searches for an orthogonal route between the head andtail work-points of a pipe, using the minimum number of bends or elbows. Figure 8:2.: LevelOne routes shows examples of the routes available in level one mode.

Box 1

The default route is ABC, as this requires only twobends. If this route is blocked, PDMS Router willtry route ADE which uses three bends.

Box 2

If PDMS Router cannot find a route using theroutes shown on box one, it will attempt the routesshown on box two, where route ABC uses threebends, and ADE uses four bends.

Box 3

Finally, if it is still unsuccessful in finding a route,PDMS Router will attempt the routes shown onbox three, where both routes use four bends.

Figure 8:2. Level One routes

A

C

D

E

PH

PT

AC

D

E

P H

PT

A

CD

E

PH

PT

A

CD E

PH

PT



Figure 8:3.: Example of a Level One route shows a level one route in which the head work-point is facing up.

Figure 8:3. Example of a Level One route

- Level Two Mode

If all first level routes are blocked, PDMS Router will attempt to find second level routes. Insecond level mode, PDMS Router will withdraw the route into the box by a distance whichenables the pipe to bypass the obstruction. PDMS Router then attempts the same routingpatterns as those used in level one mode. An example of a level two route is shown.

Figure 8:4. Example of a Level Two route

- Level Three Mode

If PDMS Router cannot find a clash-free route using first and second level routes, it willattempt to find a third level route. In third level mode, PDMS Router extends the boxoutwards until it bypasses the obstruction and then attempts to route the pipe using levelone routing principles. An example of a level three route is shown in Figure 8:5.: Example ofa Level Three route.



Figure 8:5. Example of a Level Three route

• Adding Components to a RouteOnce PDMS Router has worked out a route, it constructs the Branch by adding whateverElbows (or Bends) are needed.

Note: To be efficient, PDMS Router imposes a low upper limit on the number of Elbows itwill add to a Branch: it does not attempt to be a maze solver.

You can specify components in a Branch before routing, for example by importing a P&IDfile as described in Importing a P&ID File. You can also modify a routed Branch by addingother components, for example, Valves or Instruments, by selecting Modify>Branch andcreating the components in the normal way.

Only the principal piping components need to be added. PDMS Router will add Flanges,Gaskets, lap joint stub ends and Welds as necessary, using the COCO (ConnectionCompatibility) tables to create the correct types.

Components can be locked into a given position, in which case they will not be moved,even if the Branch is re-routed. See Locked Components for more information about usinglocked components.

If there are particular constraints that must be placed on a Branch, for example, passingthrough a given point or plane, then you must use one of the techniques described inConstraining a Route.

- Insertion of Reducers at Bore Changes

Before PDMS Router positions any components on a Branch, it checks the Branch to see ifit contains any components whose bore is different from the preceding component. If one isfound, then by default the PDMS Router will select the first suitable Reducer that it finds inthe catalogue, regardless of whether it is concentric or eccentric.

Blocked vector ismoved outwards tobypass the obstruction



You can set rules to specify whether concentric or eccentric Reducers are used. SeeCreating and Using Routing Points for information about routing rules.

Note: PDMS Router treats bores as being equal if they are the same within 5mm.

• How PDMS Router Routes to Free Tails

If a Branch has a free Tail, that is, if the Tail is not connected to another Branch or you havenot specifically defined the Tail position, PDMS Router will automatically position the Tailonce it has positioned all of the components in the Branch and applied all constraints.

If this fails, for example, because there is a clash or a component positioning rule cannot besatisfied, then it will introduce an Elbow after the constraint, before the first component.PDMS Router will then position the elbow in a direction that results in a clash-free route, andwhich satisfies component positioning and orientation rules.

If the Branch does not have any constraints, the position of the Tail depends on the positionand orientation of the Branch Head. Often, this may be a Tee. Tee positioning is explained inthe next section.

Tail direction: Note that the TDIR attribute for a free tail is never set if the last constraint isa plane or a rack. In all other cases, TDIR is taken from the direction of the last component.

• How the PDMS Router Positions TeesPDMS Router checks each Branch for connections to other Branches, that is it looks forTees or other components which have a CREF or CRFA attribute set.

• If the Branch which connects to the Tee has a free Tail, then the Tee is treated the sameas any other component.

• In all other cases, the Tee will influence the route taken by the original Branch. Ingeneral, PDMS Router will select the closest route to any constraints in the connectingBranch. If there are none, then it will select the route closest to the other end of theconnecting Branch.

• Tees which can be balanced will then be positioned. See Balanced Tees. • Where a Branch contains more than one Tee, the first Tee in the Branch will influence

the route taken. PDMS Router will position any subsequent Tees as close as possibleto the next constraint, or the other end of the connecting branch.

You can control the position of a Tee by locking it in position, or by constraining the route,using a routing point. Routing points are described in Creating and Using Routing Points.

- Balanced Tees

PDMS Router will try to position a Tee to achieve balanced flow. • The Tee must be symmetric about a plane through P-arrive. The PDMS Router will

change the arrive p-point to achieve this if the bores on the p-points are equal. It willthen check the leave-bore and connect-bore. If the bores are equal then PDMS Routerwill assume that the Tee is T-shaped.



• The Tail directions of /B1 and /B2 must either be equal and not in the axial directionbetween the Tail positions of the branches or opposite and in the axial directionbetween the Tail positions of the branches:

• There must be no locked components on branch /B2, nor any after the Tee on branch /B1.• If there are multiway components in the Branches after the Tee, the Branches

connected to them:• Must have equivalent lists of component specifications, • Must be unconstrained • Must have free tails

• The Tail positions of /B1 and /B2 must be equal in two of the three orthogonal co-ordinates:

P2P1

P3 = PA

Branch B1

Branch B1

Branch B2



• The specifications of the positionable components after the Tee on /B1 must be thesame as the specifications of the components on branch /B2.

• The Tee will be positioned so that:• The Tee is clash-free• There is enough room for all components between the Tee and the end of the

Branch• This position does not result in a route to the Tee with an elbow close to the Tee.

• If any of these conditions are not satisfied, PDMS Router will try moving the Tee backalong the arrive direction (or forward along the leave direction).

• Covered Nozzles

When the PDMS Router is routing a Branch there may be several others waiting to berouted. The best route for the current Branch may take the Pipe straight in front of otherNozzles. This is most likely to happen when routing from a line of Vessels. It can be avoidedby:



• Changing the order for routing Pipes, see Changing the Order in which Pipes areRouted.

• Ensuring that the Nozzles or Equipment owning them have obstruction volumesextending beyond their Nozzles. This prevents other Pipes crossing in front of theNozzle. The Branch connected to the Nozzle will ignore this clash and successfullyroute onto the Nozzle.

Note: The obstruction volumes should be defined in the Catalogue: defining them inDESIGN may result in less satisfactory routes.

• Constraining a RouteExcept in very simple cases, you will probably find that you need to give PDMS Router moreinformation about the route required to achieve a satisfactory route. You can constrain aroute using the following:

• Locked components• Routing Points• Routing Rules• Routing Planes• Pipe Racks

These constraints are described briefly in the following sections, and described in detail inlater sections.

- Locked Components

A locked component is a component whose position has been fixed before routing takesplace. PDMS Router will route the Branch through the component. Locked components canbe used to manually modify the route taken.

In cluttered areas, PDMS Router may not be able to find a clash-free route, in which case itwill put in the simplest clashing route and inform you about the clash. You will then need tomodify the route to obtain a clash-free route, by moving components away from clashes,locking them and re-routing. Both principal Piping components and Router-createdcomponents (for example, Elbows), can be moved and locked.

- Routing Rules

One of the principal features of PDMS Router is its built-in rule engine. You can use routingrules to control the selection, position and orientation of piping components, and to controlhow pipes use routing planes and pipe racks. For further information about using Rules, seeUsing Routing Rules.

For information about creating your own rules, see Automatic Pipe Routing Administration.

- Routing Points

Routing Points are points through which a pipe must pass. You can specify the position of arouting point, and the direction in which a pipe arrives at and leaves a routing point. Forfurther information, see Creating and Using Routing Points.

- Routing Planes

Routing planes are orthogonal planes which attract pipes to them and then guide the pipesin the direction of the plane. Routing planes are useful, for example, where you want to



group pipes together, perhaps along a wall or ceiling. For further information, see Creatingand Using Routing Planes.

- Pipe Racks

In PDMS Router, a pipe rack is composed of a group of routing planes which enables you tomodel the route used on a physical pipe rack. There are two ways in which you can create apipe rack. You can create pipe racks on existing steelwork structures or model them simplyas a group of planes. You may find the second method useful when you are working on aconceptual design and do not want to spend time creating steelwork structures. Once youhave created a pipe rack, you can use routing rule to specify how different sorts of pipe runon the rack. For further information, see Creating and Using Pipe Racks.

• Before You Start Using PDMS RouterBefore you start using PDMS Router with one of your own projects, you will need to performthe following tasks:

• Set up the Catalogues and Specifications you want to use. • Ensure that you have specified which components you want PDMS Router to choose

by default. You must specify the default bends and elbows. You must have defaultLeave-side Tubes (LSTU).

• Define any obstruction volume required to avoid covered Nozzles, see CoveredNozzles.

• Caution: Do not use design parameters for components that PDMS Routerautomatically creates, for example, bends and elbows.

• Set up routing rules. For further information, see Automatic Pipe RoutingAdministration.

• Define all the equipment and other obstructions used in your design, If you are going toallow for flanges when packing Pipes on routing planes and Pipe Racks, you mustensure that there is a default Flange set in the catalogue, as the width of the defaultFlange will be used in calculating the spacing.

• Create the Branches, without any components added, which you are going to route.Alternatively, you can load a P&ID file from within PDMS Router. For information aboutimporting P&ID files into PDMS Router, see Importing a P&ID File.

- Branches and Component Attributes

Before you can use PDMS Router, you must ensure that the following are set.• Define the starting position of each Branch you are going to route, either by connecting

it or by setting the Head position, orientation and bore.• You will usually want to define where the Branch is going to, either by connecting the

Tail, or by setting the Tail position, direction and bore. You can route to a free tail, butthe Tail bore must be set.

• If the Branch contains components, these must be selected.

8.1.2 Basic RoutingIn this section, you will learn how to:

• define the head and tail of pipes • route the pipes using PDMS Router.

The tutorials use the sample project SAM supplied with AVEVA PDMS.



• Starting to Use PDMS Router

Exercise begins:

1. For the purpose of running the tutorials in this section of the guide, login to AVEVAPDMS as follows:

2. Enter PDMS DESIGN, and select the Pipework application. When you are prompted toselect a piping specification, select A1A.

3. Go to the Site /ROUTERSITE, and add the Zones to the Drawlist. You are going toroute Pipes between the Equipment at the South-West corner of the Site, that is thePumps PMP-1 and PMP-2, and vessels VESS-1 and VESS-2.

4. To access PDMS Router select Utilities>PDMS Router, to display the PDMS Routerform:

• PDMS Router DefaultsPDMS Router is supplied with defaults which you can change if you wish. This sectionexplains the defaults, which are accessed from the PDMS Router Defaults form. You canwork through the tutorials using the supplied defaults.

5. From the PDMS Router form, select Settings>Defaults.The PDMS Router Defaults form is displayed, as shown. You can save and loaddefault settings using the options under File on the menu.

• Project: enter SAM

• Username: enter PIPE

• Password: enter PIPE

• MDB: enter PIPE

• Module: select Design



6. Enter the path of the directory where you want to store the message file in theDirectory field.

7. Enter the name of the message file in the Filename field.

8. Click on the Overwrite/Append option button and select Overwrite if you want newerror messages to overwrite those currently in the file or, Append if you want PDMSRouter to add each new message to the end of the file.

9. To specify the action taken by PDMS Router in the event of an error occurring, selectone of the following from the Action on error option button:• Stop - Stops all further routing.• Pause - Displays an alert box which you must acknowledge before PDMS Router

can continue routing.• Continue - Continues routing, even if an error occurs

10. To specify the method used to change the direction of pipes, select an option from theChange direction using button:



• Bend • Elbow• Rule If you set the Rule option, PDMS Router will look for a rule which defines which type ofcomponent to use. You must create the rule as described in Using Routing Rules.

11. You can set a default rule set for all Branches by entering the name of the Rules set inthe Default rule set world text box. The rule set or rule world will be automaticallyassigned as a low priority rule set. If there is a set of company-wide rules you couldenter the name here. For more information, see Using Routing Rules.

12. PDMS Router can automatically associate routing planes and pipe racks with a branchto route the pipe on. To do this it searches for routing planes and pipe racks betweenthe branch head and tail. You can ask PDMS Router to extend the search outside thisvolume by entering the distances in the In Z Direction (vertical) and In X/Y Directions(horizontal) fields. PDMS Router will only automatically use a routing plane or pipe rack to route a pipe ifthe distance that it will travel along the plane or rack is greater than a minimum traveldistance. Enter the minimum distance, in the Minimum Travel Distance field.

13. In the Pipe Rack Spacing area of the form, you can specify the minimum Pipe gapbetween pipes on racks (and other planes). You can also specify in the Pipe gaprounding field the extent to which the gap size will be rounded, which can helpminimise construction errors.

• Defining the Head and Tail of a PipeIn this section, you will define the heads and tails of two pipes which you will later route.Start by defining the head and tail of the pipe between the pump PMP-1 and the vesselVESS-1.

Exercise begins

1. Navigate to the Zone ROUTERSITE/PIPES.

2. Select Create>Pipe from the Pipework Application main menu bar. The Create Pipeform is displayed.

3. Enter the name P1 in the Name textbox. The Create Pipe form should now look asshown:



4. Click OK on the Create Pipe form. The Create Branch form will be shown.

5. Set the Head/Tail Setting to Connect. This will enable you to connect both head andtail of the branch to existing nozzles. The Create Branch form should now look asshown:

6. Click OK to create the branch. The Connect Branch form is displayed.

7. Set the Connect Branch form to show that you want to connect the Head to a Nozzle,thus:



8. Click Apply. When you are prompted to select a nozzle, select the vertical nozzle ontop of the pump PMP-1.

9. Set the Connect Branch form to show that you want to connect the Tail to a Nozzle,then click Apply. When prompted, select the vertical nozzle on the top of the vesselVESS-1.

10. Create a pipe between the pump PMP-2 and the vessel VESS-2. Name the pipe /P2.Again, connect the head of the pipe to the vertical nozzle on the pump and the tail tothe vertical nozzle on the vessel. Dismiss the Connect Branch form.

• Routing Pipes

In this section, you will add the pipes which you have created in Defining the Head and Tailof a Pipe to the PDMS Router form, and then route the pipes. You can add pipes individuallyor in groups. In this exercise, you will add the pipes individually.

Note: By default, the PDMS Router routes pipes in the order in which you add them to thePDMS Router form. The routing order can have an effect on the route taken by pipes.This is explained further in Changing the Order in which Pipes are Routed.

Exercise continues:

11. From the Explorer select the pipe /P1.

12. From the PDMS Router form, select the Add : CE option to add the pipe to the PDMSRouter form.

Note that the Network option under Add loads the selected branch and any otherbranches on which the branch is dependent, or which are dependent on it.

13. Repeat the two previous steps for the pipe /P2. The PDMS Router form should nowlook as shown:



14. From the PDMS Router form, select the pipes or branches you want to route, in thisinstance, /P1 and /P2, then select the Route : Selected option. PDMS Router routes the selected pipes, adding elbows, gaskets and flanges, asrequired.

Note: A small form with a Cancel button is displayed: if you are routing several Branches,and realise that you have made a mistake, pressing the Cancel button will stop theprocess after the next Branch has been routed. It will not stop the process in themiddle of routing a Branch.

The routes created by PDMS Router are shown in Figure 8:6.: Automatically Routed PipesP1 and P2.

Figure 8:6. Automatically Routed Pipes P1 and P2

P1

P2



- Checking the Status of a Branch

Select Display>Status Summary from the menu on the PDMS Router form. The StatusSummary form is displayed, showing that two Branches have been routed successfully.

Note: The Undo and Redo buttons at the bottom of the PDMS Router form can be used toundo or redo a series of routing operations, changing settings as required, back tothe last save work.

• Changing the Order in which Pipes are RoutedPDMS Router routes pipes in the order in which you add them to the PDMS Router form.You may need to change the routing order of particular pipes if:

• You want to ensure that PDMS Router routes your most expensive pipes first. • You are working with pipes that are in close proximity to one another or where pipes

cross paths.

The routing order is changed using the options under Modify>Routing Order from thePDMS Router form.

Exercise continues:

15. Select Modify>Routing Order >Manual>Pipes from the PDMS Router form. On thePDMS Router - Reorder Pipes form, select P1 in the Reorder text pane, set the optionbutton to After, and select P2 in the right-hand window. Click Apply. Reselect Pipesand click Selected.The route obtained is shown in Figure 8:7.: Result of changing the routing order (P2routed before P1). In this instance, PDMS Router first routed the pipe P2. The routetaken by P2 has blocked the most practical route for the pipe P1, which has had to takea more complex route.



Figure 8:7. Result of changing the routing order (P2 routed before P1)

The other options under Modify>Routing Order are as follows:• Auto - automatically reorders branches according to routing dependencies, that is,

if a pipe is dependent on another pipe, then that pipe will be routed first. Select thisoption, for example, after you reorder by bore.

Note: This option only affects piping networks: It will have no effect on unconnected Pipes.

• Manual>Pipes - enables you to manually specify the order in which the PDMSRouter routes each pipe, using the Reorder Pipes form.

• Manual>Branches - enables you to manually specify the order in which the PDMSRouter routes each branch, using the Reorder Branches form.

• By Attribute - enables you to reorder pipes according to particular attributes, usingthe Reorder by Attribute form.

P1

P2



The Reorder by Attribute form, has the following option buttons:• Head Bore• Tail Bore• Temperature • Other - Select this button if you want to specify an alternative attribute to those

available on the form.

To reorder pipes according to their specification, select the Group by specification checkbox. This reorders the pipes so that they are displayed in alphabetical order of theirspecification names, for example, all pipes which use the specification A150, followed by allpipes which use the specification B150, and so on. You can use this option in conjunctionwith the attribute radio buttons. You may, for example, reorder pipes so that all PDMSRouter displays all pipes which use the specification A150 in descending order of their headbore, followed by all B150 specification pipes.

• Routing MessagesAs PDMS Router routes a pipe, it examines each branch and generates a message aboutany routing errors that it finds. These messages can help you understand and correct errors.You can view these messages both during and after pipe routing, providing you have set upa file in which to store the messages, as described previously.

To view routing messages, select Display>Routing Messages.

The Routing Messages form is displayed, as shown. The form will be empty if PDMSRouter routes all pipes without any errors.



• The Branch Detail Form

PDMS Router enables you to view details of the components and constraints in a branch,using the Branch Detail form. From this form, you can select options which enable you toconstrain the route taken by a branch. For example, you can lock components in position,create routing points and add routing planes and pipe racks to the constraint list. All of thesefacilities are explained in later sections.

To display the Branch Detail form, select one of the routed Branches from the PDMSRouter form and click the Branch Detail button. The Branch Detail form, which containsdetails of the selected branch, is displayed as shown:

The information on this form is discussed in Positioning and Locking Components.

8.1.3 Positioning and Locking ComponentsIn this section you will learn how to:

• add components to Branches after they have been routed• control where the components are positioned.



The effect that positioning and locking components will have when a Branch is re-routed isalso considered.

Note that you can set up rules to control the selection, positioning and orientation ofcomponents, and these are described in Using Routing Rules.

• Deletable, Positionable and Locked ComponentsPDMS Router sees all piping components as deletable, positionable or locked. If youdisplay the Branch Detail form for a Branch that has been routed by the PDMS Router, youwill see that all the components are listed as deletable.

• The components that PDMS Router creates in a Branch are described as Deletable. Ifyou re-route the Branch, PDMS Router will delete all the components that it hascreated and re-create them.

• After a Branch has been routed, you can add components manually in the normal way:make sure that you are in the correct place in the Members list and selectCreate>Component. These components are described as Positionable. If you re-route the Branch, these components will not be deleted, but they may be moved to fiton the new route.

• Positionable components can be locked into a given position, in which case they willnot be moved, even if the Branch is re-routed.

The order of Positionable components in the Branch Members list will be maintained, and sowill their order relative to any constraints in the Branch. For example, if you add a Valvebefore a Locked Tee, the Valve will not be moved past the Tee.

You may wish to make changes to a Branch, and then re-route it. You can keep some or allof the components that PDMS Router has added by making them positionable, rather thandeletable. You can also lock them.

To change the status of a component, select it in the list on the Branch Detail form, andthen select one of the options under the Modify menu on the form. The choices are:Constraint, Toggle Head Lock, Toggle Tail Lock, Lock Position, Make Positionable,Make Deletable, Toggle Head/Tail Relative, Head W-P, and Tail W-P.

• Positioning Relative to the Head or TailEach component in a branch is positioned relative to the head or tail of the branch.

• If a component is head relative, then PDMS Router will place that component as closeas possible to the head of the branch, allowing for other components and anyconstraints.

• If a component is tail relative, then that component is positioned as close as possibleto the tail of the branch.

PDMS Router routes a pipe from head to tail and so all components are initially createdhead relative.

You can change the head/tail relative property of any positionable component. Select it inthe list on the Branch Detail form, and then select Modify>Toggle Head/Tail Relative.

- Head and Tail Work-points

Each Branch has a Head Work-point and a Tail Work-point. You can insert componentsbetween the Head (or Tail) and its work-point, which can be used, for example, to position aValve directly onto a Nozzle.



• Positioning a Component Close to the Head or Tail

In this exercise, you will learn how to position piping components relative to the head or tailof a branch.

Exercise begins:

1. Create a valve on the pipe /P2. Your view should look like Figure 8:8.: Head-relativeValve position. Notice that the valve is positioned close to the head of the pipe.

Figure 8:8. Head-relative Valve position

2. On the PDMS Router form, select the Branch Detail button to display the BranchDetail form.

3. Select VALV 1 from the list of Components/Constraints, then select Modify>ToggleHead/Tail Relative.

4. From the PDMS Router form, select the Route : Selected option.PDMS Router re-routes the Pipe and positions the Valve close to the Tail of the Pipe,as shown in Figure 8:9.: Tail-relative Valve position.



Figure 8:9. Tail-relative Valve position

• Moving the Head or Tail Work-point

You can position the Head W-P after a particular component in a Branch, or, you canposition the Tail W-P before a particular component.

In this exercise, you will add a Valve to the Pipe /P1 and then position the Tail Work-point ofthe Branch before the Valve. This will enable you to position the Valve directly onto theNozzle of vessel /VESS-1, then re-route the Pipe without affecting the position of the Valve.

Exercise begins:

1. Create a Valve on the pipe /P1.Your view should now look like Figure 8:10.: The Valve positioned at the Head of P1:



Figure 8:10. The Valve positioned at the Head of P1

2. From the PDMS Router form, select the Branch Detail button to display the BranchDetail form.

3. From the Branch Detail form, select Modify>Tail W-P. The Modify Tail W-P form isdisplayed.

4. From the Modify Tail W-P form, select VALVE 1, then click OK.

5. From the PDMS Router form, select the Route : Selected option.PDMS Router re-routes the Pipe from the Head Work-point to the Tail Work-point,which is now positioned before VALV 1, as shown below.



To check the position of the valve, display the Branch Detail form for the branch, thenscroll to the bottom of the Components/Constraints list. The details should now lookas shown:

Note: The Tail Work-point is now positioned after VALVE 1

• Locking and Unlocking a Component

PDMS Router enables you to lock piping components in position. You may need to do this,for example, to ensure that a branch component remains in its current position, even if youre-route the branch.

To lock a component in position:

1. From the Branch Detail form, select the component that you want to lock in position.2. Select Modify>Lock Position.

To unlock a locked component, select Modify>Make Positionable for main pipingcomponents, or Modify>Make Deletable for PDMS Router generated components.

Valve is positioned beforethe Tail Work-point



• Manually Routing Non-orthogonal Sections

PDMS Router is an orthogonal router, and so if you want non-orthogonal sections of pipe ina branch you will have to route these sections by hand. You can then lock all thecomponents in this section (including the start and end bend or elbow) and route theremainder of the pipes using PDMS Router.

Aligned, locked, non-orthogonal components• If two locked components with non-orthogonal arrive and/or leave direction are aligned,

with no intervening components, so that a straight piece of tube can run between themwithout clashing, PDMS Router will use this route. This will also happen if the firstcomponent is aligned with the head or the last component is aligned with the tail.

• If the straight, non-orthogonal routes clash, only orthogonal routes will be considered toavoid the clash.

• In all other cases PDMS Router will try to insert a bend or elbow to turn into anorthogonal direction as close as possible to the component.

Non-aligned non-orthogonal components• If non-orthogonal components are not aligned, only orthogonal routes between them

will be considered.

This is the default orthogonal routebetween the pump and the vessel.

Using aligned and locked elbows togive a non-orthogonal route.

Non-aligned components will still givean orthogonal route.



Non-orthogonal sections with unlocked components

If there are other, positionable, components between non-orthogonal locked components,orthogonal routing will be used. Router may add connection components on to the lockedcomponents, but note that no bore change (which would require the addition of a reducer)will be permitted.

Example 1

You can lock several non-orthogonal components in a row. For example, you can lock two45 degree elbows to give a non-orthogonal section of pipe and place a locked valve on thissection of pipe. PDMS Router will then not route any part of the Branch between the elbows,providing that straight pipe does not clash; and it will add any necessary connectioncomponents to the valve. However, the valve must be locked: if it is positionable PDMSRouter will route orthogonally between the elbows.

A positionable Tee has been insertedin the Branch, which has causedPDMS Router to revert to anorthogonal route, using additionalElbows

Detail of the area close to the Tee.

The route achieved with the TeeLocked.



Example 2

It may be better to continue in a non-orthogonal direction from a nozzle until a route haspassed an obstruction, because this might give a shorter route with fewer elbows. Youwould lock the elbow at ‘A’ to give this route:

• Using Rules for Minimum Tube Length

You may find that components such as Olets and Stub-in Tees will be positionedimmediately next to another component, if your COCO tables allow. You can use theUpstream and Downstream Rules provided with PDMS Router to specify minimum lengthsof Tube. See Using Routing Rules for more information about using rules.

8.1.4 Creating and Using Routing Points

In this section you will learn how to use Routing Points to constrain a route. Routing pointsare points through which a branch will pass. You can define the coordinates of a point andthe direction in which a branch arrives at and leaves a point.

You can add as many routing points as you want. You must create routing points at thecorrect position in the sequence of constraints.

• Creating a Routing PointYou will now add a routing point to the pipe /P2, which you routed previously. The routingpoint will ensure that PDMS Router routes the pipe so that it is parallel with pipe /P2.

In this exercise, you will create a routing point, relative to an existing element.

Exercise Begins:

To create the routing point:

1. Add the pipes /P1 and /P2 to the PDMS Router form, if you have not already done so.

2. Select the branch /P2/B1, then select the Branch Detail button. The Branch Detailform is displayed.

3. Select Create>Routing Point. The Create Routing Point form is displayed. You cansimply enter the coordinates on the Create Routing Point form or use the options onthe menu, which are similar to the normal PDMS positioning options.



4. For this exercise, you will specify the position of the routing point relative to an existingcomponent. You can only position routing points after positionable or locked components.Select Cursor>Element, then pick elbow 3 of the pipe /P1/B1, as shown in theillustration.



5. PDMS Router creates a routing point at the position of the elbow. You will now movethe routing point so that it is 1000mm west of the elbow. From the Create Routing Point form, select Move>Distance. The Move Point form isdisplayed. Enter W (West) in the Direction field. Enter 1000 mm in the Distance field.Click Apply to confirm the move, then Dismiss the form.You can lock the point at the specified positions using the Lock check boxes on theCreate Routing Point form, if required.

6. To ensure that pipe /P2 travels parallel with pipe /P1, you will define the direction inwhich pipe /P2 arrives at and leaves the routing point. In common with PDMS DESIGN,the arrive direction should point to the head, and the leave to the tail. From the Create Routing Point form, select the Arrive/Leave option button. Enter N(North) in the Arrive direction field and S (South) in the Leave direction field.

7. Ensure that the After option button is set to Head W-P. The form settings should now look as shown.

Select elbow 3using Cursor > Element



When you click OK, PDMS Router creates the routing point at the position shown.

Position ofrouting point

NU

E



When you route the Pipe again, PDMS Router routes the pipe via the routing point, asshown.

By specifying a different arrive and leave direction, you will cause a bend or elbow to beinserted at the position of the routing point. If you do not want a change of direction,select the Through Direction and specify the direction that you would like the pipe totake at that point. If you leave the direction unset, PDMS Router will select the bestdirection to minimise the number of bends or elbows used.

• Using DATUMs as Routing Points

There is an option on the Create Routing Point form which allows you to use an existingDATUM point as a routing point. Two branches should not use the same Datum point as aconstraint since they would then clash. If you want to use a Datum where two branchesmeet, just one of the branches should have the point as a constraint. For example, Branch /P1/B1 ends at a Battery Limit and Branch P2/B1 connects to its Tail. Branch /P1/B1 shouldhave the Datum as the last constraint and a Free Tail. The Head of Branch /P2/B1 will bepositioned at the Tail of /P1/B1.

• Moving a Routing Point

You can modify the position of a routing point, at any time. To do this:

1. From the PDMS Router form, select the branch you want to modify, if you have notalready done so.

2. Click the Branch Detail button. The Branch Detail form is displayed.3. Select the routing point you want to modify from the Components/Constraints list.4. Select Modify>Constraint. The Modify Routing Point form is displayed.5. Select one of the following options, depending on the type of modification you want to

make:• Move>Distance

Position ofrouting point



to move a routing point a distance in a specified direction either from the currentlocation, or relative to another element which you can identify using the cursor oranother method.

• Move>Towardsto move the point a specified distance towards another element, which you canidentify using the cursor, by specifying a named element or, which may be the head,tail or, the next element in the branch.

Note: Make sure that the routing point is still in a sensible position in the list of constraints,otherwise a very convoluted route may be obtained.

If you have used a DATUM as a routing point, you can use the standard AVEVA PDMSpositioning options to modify its position.

8.1.5 Using Routing Rules

Routing Rules are special AVEVA PDMS rules which are used to control:• How components are selected, positioned and orientated as Branches are routed.• How Pipes are packed on Pipe Racks and Routing Planes.

In this section you will learn how to use the sample routing rules supplied with the PDMSRouter. You can also define your own routing rules as described in Automatic Pipe RoutingAdministration.

Note: For more general information about defining rules for setting attributes, see thePDMS DESIGN Reference Manual.

You can apply routing rules to individual branches or all branches within a particular site,zone, or pipe. You can also apply rules to individual components and remove rules fromindividual components, as required.

• Expressions

A routing rule consists of AVEVA PDMS expressions. AVEVA PDMS expressions aredescribed in detail in the Software Customisation Guide. The examples in this chaptershould give you a starting point for writing the expressions needed for routing rules.

AVEVA PDMS expressions consist of the following:• AVEVA PDMS element types. For example, VALV, BRAN, TEE. This also includes

OWNER and MEMBER.• AVEVA PDMS attributes and pseudo-attributes. For example, HDIR, ABOR.

For a list of AVEVA PDMS attributes, see the Software Customisation Guide.• Logical operators. The operators available are

• EQ equal to• NE not equal to• GE greater than or equal to• GT greater than • LE less than or equal to• LT less than

• Keywords. There are a wide variety of keywords, illustrated in the rest of this chapter.For example, ALL, WITH, UP, IS.



• Applying a Rule Set to a Branch

Once you have created a rule set, you can apply it to a branch. The rules will then takeeffect on the components in the branch. To do this:

1. From the Members List form, select the branch with which you want to associate a ruleset.

2. From the PDMS Router form, select Settings>Apply Rules>To Branch. The ApplyRules form is displayed.

3. Select the rule world which contains the rule sets you want to apply to the branch fromthe RULE WORLD option list.

4. Note that the Apply to list contains all the Branches selected on the PDMS Routerform.

5. Select the rule set that you wish to apply in the Rule sets available in current worldlist.

6. You can add the rule set as high priority or low priority. PDMS Router first checks to seeif there are any rules that will apply to a component from the high priority rule sets. Ifthere are none then PDMS Router checks if there are any rules that will apply in the lowpriority rule sets.Click the Add HIGH button to add the rule set to the High Priority Sets list or the AddLOW button to add the rule set to the Low Priority Sets list.

7. Click Apply.8. Route the branch to apply the rules.

Note: The Settings>Apply Rules options on the PDMS Router form allow you to apply therule sets to a site, zone or pipe. In these cases all branches which are below them inthe hierarchy will also have the rule sets applied, unless they have rule setsspecifically applied.



Important: If you apply rules to an element which contains many Branches, for example, aZone, then each time you route a Branch, PDMS Router will check everyBranch to see if the rules apply. This may take some time.

By default, PDMS Router applies all the rules in the specified sets to a branch, providingthey are appropriate. You can, however, remove a rule from a particular component in abranch, or add one from another rule set.

• Removing a Rule SetTo remove a rule set:

1. From the Members List form, select the branch from which you want to remove a ruleset.

2. Select Settings>Apply Rules>To Branch. The Apply Rules form is displayed.3. Select the rule set you want to remove, then click on the Remove HIGH or Remove

LOW button as appropriate.4. Click Apply.

If a Rule Set has applied to a Pipe, Site or Zone, it will be removed from all Branches in thatPipe, Site or Zone.

• Including a Rule from another Rule Set or World

If you would like to apply a rule to a component from another rule world or rule set:

1. From the PDMS Router form, select the branches you want to apply the rule to.2. Click on the Branch Detail button.3. Click on the Component Rules button on the Branch Detail form.

The Component Rules form is displayed which you can use to add additional rulesfrom the available rule sets, or from another rule world.



4. From the Current Component option list, select the component that the rule will beapplied to. The letter that precedes the rule description in the Rules applying to currentcomponent list shows where the rule was originally applied. The letters used are: • B Branch• PPipe• Z Zone• S Site

5. From the Rules available list, select the rule you want to apply to the selectedcomponent, then click on the Include button. The rule is added to the list of rules whichapply to the component.

6. Click Dismiss.

• Disabling a Rule from a Component

To prevent PDMS Router from applying a rule to a particular component in a branch:

1. From the PDMS Router form, select the branch with which you want to work.2. Click on the Branch Detail button to display the Branch Detail form.3. From the Branch Detail form, select the component from which you want to exclude

the rule.4. Click on the Component Rules button. The Component Rules form is displayed.5. From the list of rules that apply to the current component, select the rule you want to

disable from the component, then click on the Disable button.PDMS Router places an asterisk (*) to the left of the rule description to indicate that therule is now excluded from being used.

If you want to re-enable a disabled rule, select the rule, then select the Enable button.



The rule will now appear in the Rules applying to current component list, preceded by aplus sign (+) indicating that it has been included.

• Querying Rules

You can query which rules are applied to a Branch, which you may find useful if you areusing many rules, and the result is not what you expect. Display the command line byselecting Display>Command Line from the main Pipework Application menu, and thentype:

Q ROBRRU

This command is only valid if the current element is a Pipe, a Branch or a Branch Member.

8.1.6 Creating and Using Routing PlanesIn this section you will learn how to:

• create a routing plane• use a routing plane to route branches

• Introduction to Routing Planes

Routing planes are rectangular planes which are used to guide pipes along their length. Youwill find routing planes useful, for example, in routing groups of pipes along a wall or ceiling,or simply to group pipes close together. Figure 8:11.: Example of using routing planesshows an example of how you could use two routing planes, one above the other, to groupall north/south pipes together and all east/west pipes together.

Figure 8:11. Example of using routing planes

You can use one or more single routing planes. Note that a Pipe Rack is defined as a groupof routing planes for PDMS Router. Pipe Racks are described in the next section.

• How PDMS Router Uses a PlanePDMS Router will ensure that pipes take the best route available from the previousconstraint to the routing plane. If the most direct route to the plane is blocked, PDMS Router



will select an alternative route which ensures that the pipe enters the plane at the earliestopportunity, which is usually just after the obstruction. The pipe will exit from the plane at thepoint which enables it to take the most direct route to the next constraint. If the most directroute to the next constraint is blocked, the pipe will exit from the plane just before theobstruction.

• Pipes are routed along the length of a routing plane.

You can set whether the centre, top or bottom of pipes will be aligned on the routing plane. Ifa pipe is insulated, the plane will automatically take the insulation into account bypositioning the pipe at a height which allows for the insulation. Note that you can also makeallowance for shoe heights using a SHOE rule. See Automatic Pipe Routing Administration.

• Using More Than One Plane to Route a Branch

You can use more than one routing plane to route a branch. However:• You should have routing points or locked components between the planes. If you do

not do this, PDMS Router may encounter difficulties in deciding when to leave oneplane and enter another.

• You should not use two adjacent planes with the same travel direction and noperpendicular offset between them.

• For turns in the same plane, planes should touch, within 100cm, corner to corner, butnot overlap.

You can use groups of routing planes to create Pipe Racks. How you do this is described inCreating and Using Pipe Racks.

• Creating Some Pipes for the Exercise

Exercise begins:

Before you create and use a routing plane, you need to create the pipes which you will laterroute via the plane.

1. Create the pipes shown in the following illustration:

2. Add the pipes to the PDMS Router form in the order ROUTE-3, followed by ROUTE-4and finally, ROUTE-5.You may like to route the pipes before you create and add the routing plane. This willenable you to see the effect that the routing plane has on the route taken by the pipes.To do this:

3. Select the pipes, then select the Route : Selected option.The route taken should look as shown:

PMP-3

PMP-4

PMP-5

VESS-3

VESS-4

VESS-5

ROUTE-3

ROUTE-4

ROUTE-5



• Creating a Routing Plane

Exercise continues:

To create a routing plane:

4. Navigate to the zone ROUTERSITE/STRU.

5. From the PDMS Router form, select Create>Routing Plane. The Create RoutingPlane form is displayed.

6. Enter the name Plane-1 in the Name field. This is the name that is displayed in theMembers List and the Branch Detail form.

7. Enter a description of the routing plane, in the Description field. This text is not usedelsewhere in AVEVA PDMS, but you may find it useful for keeping a record of theplane’s purpose for future reference.

6. Set the Pipe Positioning option list to Centre of pipe. This will position the centre ofthe pipe along the routing plane. The other options available and their actions are:• Top of pipe



Positions the top of the pipe on horizontal routing planes, or in front of verticalrouting planes adjusting for any insulation

• Bottom of pipePositions the side of the pipe below horizontal routing planes, or behind verticalrouting planes, adjusting for any insulation

Note: Top is the Z direction of the Plane which is shown with an arrow.

The Pipe to Pipe Gap and Packing Method options control how Pipes are packed onthe plane. See Pipe Packing.

8. Click OK. The Routing Plane Dimensions form is displayed.

9. Set the Anchor option list to Centre. The anchor is the position from which the routingplane takes its dimensions. There are two options available, centre and corner. Set thecoordinates to:East 45000mmNorth 300mmUp 1100mm

10. Enter 15500mm in the Length field, then set the Dir option to the left of the field to E(east). This will cause pipes to be routed along the east/west direction of the plane.

11. Enter 1200mm in the Width field, then set the Dir option button to the left of the field toN (north).

12. The Routing Planes Dimensions form should now look as shown.



7. Click Apply to create the plane.

Note: You can create a vertical routing plane by setting one of the Dir fields to be U or D(up or down). The up/front direction of the plane will be indicated by a constructionarrow in the graphical view which is drawn perpendicular to the plane. To reverse thedirection, reverse either of the length or width directions, for instance from E to W.

• Using a Routing Plane to Route Branches

Exercise continues:

To route a branch via a routing plane, you must add the routing plane to the constraint list forthe branch. To do this:

13. From the PDMS Router form, select the branch /ROUTE-3/B1, then click on theBranch Detail button. The Branch Detail form is displayed which contains details ofthe branch /ROUTE-3/B1.

14. Select Add>Routing Plane>Selection.The Add Routing Plane form is displayed. The scrollable list displays the availableplanes.



15. From the Plane list, select the plane that you created in the previous exercise.

16. Ensure that the Insert After list is set to Head W-P.The Last on Plane toggle allows you to specify that positionable components will beplaced on the plane.

17. Click OK. The routing plane is added to the constraint list for the branch.

18. Repeat the procedure for the branches /P4/B1 and /P5/B1.

19. Route the branches, using the PDMS Router form.PDMS Router routes the branches via the routing plane. The route taken by thebranches should now look as shown.

• Adding Routing Planes Automatically

PDMS Router provides facilities to automatically add pre-defined routing planes to a branch.This could be useful if for instance you wish to run all north/south running pipes at oneelevation, and all east/west pipes at another.



PDMS Router can add either one vertical plane, or two horizontal planes, providing thehorizontal planes are oriented perpendicular to one another.

The routing planes will be added at the head of the branch. The planes must be able to bereached directly from the head for them to be included. If there are more planes than arerequired, the closest ones to the head will be chosen.

If there are constraints in the branch, such as routing points, or locked components, anadditional two horizontal or one vertical plane will be searched for at the tail of the branch.These must be reachable directly from the tail and will be added to the Components/Constraints list as the last constraints before the tail.

Planes will be searched for in a box defined by the head and tail of the branch. The box willbe extended by the values specified in the PDMS Router Defaults form. Only pipes thattravel along routing planes a distance greater than the Minimum Travel Distance will beconsidered.

To add routing planes automatically:

1. From the PDMS Router form, select the branch that you wish to add routing planes to,then click on the Branch Detail button.

2. Select Add>Routing Plane>Automatically. Names appear in the Command Input &Output window but not on the Status bar.

3. The Components/Constraints list on the Branch Detail form will be updated with theselected routing planes.

• Components on PlanesThe Last on Plane toggle on the Add Routing Plane form (and the Last on Rack toggleon the Add Pipe Rack form) allows you to specify that positionable and locked componentswill be placed on the plane. When it is switched on, the neighbouring list will show all thepositionable and locked components in the Branch: select the one required: all thepositionable and locked components after the Plane, up to and including the componentgiven as Last on Plane, will be positioned on the plane.

• You can have several positionable components on a plane or rack. • You can also have more than one locked component on a rack providing they are

aligned. • Reducers are not permitted as positionable or locked components on a plane.

- Locked Straight-through Components

You can place locked components on planes, but note the following conditions:• Locked components will define the slot on the plane for the Branch. If there is more

than one locked component for a branch on a plane or rack, all of these componentsmust lie in the same slot.

• You must have sufficiently wide gaps on the plane to fit in any component required.This could be achieved, for example, by using a large enough basic gap, or using WF /FF spacing with large enough flange widths.

• The arrive and leave directions must be along the travel direction.

- Locked Bends and Elbows

Since locked bends or elbows define the start or end of the slot:• Locked bends and elbows will define the start or end of the slot on the travel plane as

well as the slot itself. Hence there can be at most one entry bend/elbow and one exitbend/elbow.



• For a locked bend or elbow used to enter the travel plane from the entry plane, thearrive-direction must be from the entry-plane and the leave-direction along the travelplane

• For a locked bend or elbow used to leave the travel plane, the arrive direction must bealong the travel plane and the leave-direction must be to the exit plane.

If there are no rules about choosing entry/exit planes, PDMS Router will use the entry andexit bend/elbow to help it to choose suitable entry/exit planes.

Exercise begins:

1. Create a Pipe, P99. Create a Branch, B1, with its Head connected to NOZZ1 of PMP-3and its Tail connected to NOZZ1 of VESS-4.

2. Create a Tee in Branch B1.

3. Create a Branch, B2, with its Head connected to the Tee and its Tail connected toNOZZ1 of VESS-3.

4. Add the Plane PLANE-1 to the constraints list for Branch B1, specifying the Tee asLast on Plane.

5. Route both the Branches, and you will see the result shown below.

The constraints list on the Branch Detail form, is as shown:



8.1.7 Creating and Using Pipe Racks

In PDMS Router, the term pipe rack is used to describe a group of routing planes whichenable you to automatically model the routing patterns used on a physical pipe rack.

In this section, you will learn how to:• Create pipe racks• Route pipes via a pipe rack

• Introduction to Pipe RacksA pipe rack is made up of routing planes (RPLAs) created within a routing plane group(RPLG). The planes represent travel planes and entry/exit planes.

You can create pipe racks with several levels, that is several travel planes. For each levelof a pipe rack, you must create a travel plane to control the direction in which pipes travelalong the rack and at least one entry/exit plane to ensure that pipes enter onto and exit fromthe rack perpendicularly, either from above or below. Each pipe rack must have at least onetravel plane and at least one entry/exit plane.

• The direction of travel is the X direction (length) for travel planes and the Y direction(width) for entry and exit planes.

PDMS Router assumes that the RPLAs in an RPLG have their centres on a vertical line.The entry and exit planes must be:

• At least as long (in the X direction) as the travel Plane(s) • Wider (in the Y direction) than the travel planes• At least twice the bend length.

When you create entry/exit planes, you must specify the distance by which they overhangthe travel planes. The overhang ensures that the vertical legs of pipes which enter and exitthe rack are clear of the pipe rack structure.

A pipe rack may have an upper entry/exit plane, a lower entry/exit or both, depending on theway in which you want pipes to enter and exit a pipe rack. In a pipe rack that has severallevels, an entry/exit plane can be used by more than one level. An example is shown inFigure 8:12.: Examples of Routing Plane Groups.



Figure 8:12. Examples of Routing Plane Groups

You can manually associate a pipe rack with individual branches or you can tell PDMSRouter to automatically search for and make use of any pipe racks which exist within thesearch volume of a branch or branches. The default search volume is the volume betweenthe head and tail of a pipe, as shown in Figure 8:13.: Search Volume for Automatic PipeRacks, and it can be extended as specified on the PDMS Router Defaults form.

Figure 8:13. Search Volume for Automatic Pipe Racks

PDMS Router will select the closest pipe rack to the head in the search volume, whosedirection will take the pipe closer to the tail, and providing that when using it, the pipe willtravel on the rack for longer than the Minimum Travel Distance as defined on the PDMSRouter Defaults form.

Pipe Tail

Pipe HeadExtended searchvolume

Default searchvolume



• Rack or Plane as Last ConstraintIf you are responsible for one area of a plant and a different designer is responsible for anadjacent area, a branch may run out of the first area on a pipe rack. You want to put the rackin the constraint list and run the branch to your limits. You can do this using the free tailoption from the branch details. A branch has a free tail when the tail is either not connectedor is directly connected to another branch; and the tail is not locked.

A free tail can be specified immediately after a pipe-rack or plane. When a branch has aplane or rack as its last constraint and a free tail, PDMS Router will route the branch ontothe plane or rack. It will travel in the direction implied by the tail direction until it reaches theedge of the plane or rack. This will then become the tail position.

Example

User-A is responsible for one area of a plant and User-B is responsible for an adjacent area.A branch /P100/B1 runs out of the User-A's area on a pipe-rack. User-A puts the rack in theconstraint list with the end of the travel plane at the limits, and specifies the tail direction andthat the tail is free. PDMS Router will pack the pipe onto the rack and run it to the end of therack.

User-B connects the head of a Pipe /P200/B1 to the tail of /P100/B1 and begins routing fromthis point. User-B must ensure that the position of the head of branch /P200/B1 is initiallyunset. PDMS Router will use the Branch Lock so that the head /P200/B1moves if theconnected tail moves. If the pipe starts by travelling along an extension of the rack in User-A's area then User-B has a rack with its starting edge at the limit to represent this.

• How Pipes are Routed on a Pipe RackBy default, PDMS Router avoids pockets by first finding the travel plane. If the Head isabove the plane, the Pipe will enter from above the plane. If the Head is below the plane, thePipe will enter from below the plane. Exit from the plane is similarly controlled by theposition of the Tail relative to the plane.

There are three routing rules which enable you to set which planes are used as entry, exit ortravel planes on pipe racks. The rules are:

• Pipe rack travel plane selection Use this rule to specify which level of a multi-level pipe rack you want to use to route aparticular type of branch.

• Pipe Rack entry plane selection Use this rule to specify the way in which pipes enter onto a rack, based on the contentsof the pipe. In order to use this rule, you must set up an attribute which defines thepipe’s contents, for example vapour or liquid.

• Pipe Rack exit plane selection Use this rule to specify the way in which pipes exit from a rack, based on the contentsof the pipe. In order to use this rule, you must set up an attribute which defines thepipe’s contents. If no rule exists, the entry plane will be used.

- Pipe Packing Defaults

By default, PDMS Router will run pipes along Routing planes with the wall-to-wall Pipe Gap,with any rounding factor for the positioning, as given on the PDMS Router Defaults form.For more information about how Pipes are packed on Planes and Racks, see Pipe Packing.



• Methods for Creating Pipe RacksYou can create a pipe rack using either of the following methods:

• Convert an existing steelwork structure into a pipe rack, using elements of thesteelwork as reference points for the position and dimensions of the planes.

• Create the routing planes which model the behaviour of a pipe rack and then add thesteelwork later, once you are satisfied with the route. In PDMS Router, this is referredto as a conceptual pipe rack. See Creating a Conceptual Pipe Rack.

• Converting a Steelwork Structure to a Pipe Rack

In this section, you will learn how to create a pipe rack, using elements of a steelworkstructure as reference points to position the planes. You will create the pipe rack, using thesteelwork FRMW ROUTERSITE/PR1.

- Creating Some Pipes for the Exercise

Exercise begins:

Before you create a pipe rack, you need to create some pipes to route via the pipe rack.

1. Create the pipes shown in the illustration below. If you can not remember how to dothis, see Basic Routing. Connect the heads of the pipes at the pump nozzles and thetails to the vessel nozzles.

You may like to route the pipes before you create and add the pipe rack. This will allowyou to see the effect of the routing plane on the route taken by the pipes. To do this:

2. Add the pipes to the PDMS Router form, as described in Defining the Head and Tail ofa Pipe.

3. Select the pipes, then select the Route : Selected option. The route taken by the pipesshould look similar to this:



- Creating the Pipe Rack

To create the pipe rack:

4. Navigate to the STRU element ROUTERSITE/PRACK1. Note that you can only createrouting plane groups inside a STRU element, and so the current element must be aSTRU, FRMW or SBFR.

5. From the PDMS Router form, select Create>Pipe Rack Planes. The Create PipeRack form is displayed.



6. Enter a name for the pipe rack, in the Name field. For the purpose of this exercise,enter the name PR-1. Note that the name of the STRU element which owns the piperack elements is shown under the Name.

7. Click on the Convert button. Pick an element in the steelwork in response to theprompt. The Positioning Control form is displayed to help you control which elementis picked if necessary.

8. The other thing that happens when you click Convert... is that the Pipe RackDefinition form is displayed:



This form allows you to define values which apply to all the planes in the Rack. Whenyou are creating a pipe rack in this way, the following parameters have been derivedfrom the existing structure and you cannot change them at this point:• Elevation of Anchor Plane• Elevation between planes• Number of Travel Planes• Number of Entry/Exit Planes

Note: The Anchor Plane is the lowest travel plane in the rack.

You can change the Overhang of Entry/Exit planes: see Figure 8:12.: Examples ofRouting Plane Groups. The default value is set on the PDMS Router Defaults form.You can set any Options you want to apply to all planes in the Rack. For moreinformation on Pipe to Pipe Gap and Packing Method, see Pipe Packing.Click OK on the Pipe Rack Definition form.

Note: Routing planes are added with transparency. You can control the degree oftransparency on the Drawlist.

The Create Pipe Rack form now appears as shown:



9. PDMS Router has automatically filled in the Rack Direction, and the Dimensions ofthe rack. The details of the Planes will be shown in the list of Planes at the bottom ofthe form. The Plane attributes area of the form, the values shown are those for theplane selected in the Planes list. You can edit the Plane Attributes for individual planesby changing the values in the form and then clicking Include to create a new plane orReplace to replace the plane selected in the list.

• Adding a Pipe Rack to a Branch

In this section, you will route the pipes you created previously via the pipe rack PR-1.

There are two ways in which you can associate branches with a pipe rack. You can:• Manually add a pipe rack to the list of constraints for a branch. You can do this either

from the PDMS Router form or from the Branch Detail form. • Tell PDMS Router to automatically make use of any pipe racks that exist within a

certain area between the head and tail of a branch.

- Automatically Adding Pipe Racks to a Branch

To tell PDMS Router to automatically make use of pipe racks, select the branches /ROUTE6/B1, /ROUTE7/B1 and /ROUTE8/B1 from the PDMS Router form and then selectModify>Branch>Add Pipe Rack>Automatically.



The status line tells you which rack is being added to the constraints lists for the selectedbranches.

- Manually Adding Pipe Racks to a Branch

To manually add a pipe rack to the list of constraints for a branch:

1. From the PDMS Router form, select the branch /P9/B1, then select theModify>Branch>Add Pipe Rack>Selection.The Add Pipe Rack form is displayed which contains a list of the pipe racks that areavailable for selection.

2. Select the rack that you created in the previous exercise. This form is very similar to theAdd Routing Plane form.

3. Click OK to add the rack to the constraint list for the selected branch.4. Route all of the branches, using the PDMS Router form. The route taken by the pipes

should look like this:



The default route creates pockets in three of the Pipes. By default, PDMS Routerroutes all pipes that you associate with a pipe rack along the first travel plane that itfinds in the routing plane group (RPLG).

Note: You can use routing rules to achieve a better route: see Automatic Pipe RoutingAdministration.

• Creating a Conceptual Pipe Rack

In this section, you will learn how to create a conceptual pipe rack, that is, a pipe rackwithout any associated steelwork. The steelwork can be added later.

- Creating Some Pipes for the Exercise

Exercise begins:

Before you create a conceptual pipe rack, you need to create some pipes to route via therack.

Create the pipes shown in the illustration below. If you cannot remember how to do this, seeBasic Routing. Connect the heads of the pipes to the pump nozzles and the tails to thevessel nozzles.



You may like to route the pipes before you add the pipe rack. This will allow you to see theeffect of the routing plane on the route taken by the pipes.

• Creating the Pipe RackYou can only create routing plane groups inside a STRU element. To create a conceptualpipe rack:

1. Navigate to the zone ROUTERSITE/STRU.

2. From the PDMS Router form, select Create>Structure for Planes. The NameStructure for RPLG form is displayed.

3. Enter the name PRS-2 for the structure in the Name field, then click OK.

4. From the PDMS Router form, select Create>Pipe Rack Planes. The Create PipeRack form is displayed.

5. Enter the name PR-2 for the pipe rack in the Name field.

6. Set the Rack Direction option to North/South.7. Define the Dimensions of the plane

Select Corner 1 from the drop-down list, then enter 63500mm East, 16000mm Northand 6000mm Up. Select Corner 2 from the drop-down list, then enter 60000mm East and 6000mmSouth.Note that the Length of Rack and Width of Travel Planes are calculatedautomatically.

PMP-11

PMP-10

VESS-7VESS-8



8. The Create Multiple planes button will now be active: Click it to display the Pipe RackDefinition form. In this case all the options on this form will be active.Keep the default of 0mm in the Elevation of Anchor Plane box: this value is definedrelative to the Pipe Rack.• Enter -1000mm in the Elevation between planes box: this will create the Entry/Exit

plane 1000mm below the Anchor (travel) plane.• The other options can be left at their default values. Click OK on the Pipe Rack

Definition form. PDMS Router creates an outline of all the planes for the rack anddisplays an arrow on the travel planes to indicate the travel direction of the rack.This enables you to check whether the plane is how you want it to be.

9. Add the pipe rack to the Branches, and route the pipes The route taken by the pipeswill look as shown:

8.1.8 Pipe PackingIn this section you will learn how to specify the gaps between Pipes on Routing Planes,which includes Routing Planes defining Pipe Racks.

This section only deals with setting values for pipe packing using the PDMS Router forms.You can also control pipe packing by means of Rules, which are described in AutomaticPipe Routing Administration.

• Pipe Packing Defaults

By default, PDMS Router will run pipes along Routing planes with the wall-to-wall Pipe gapgiven on the PDMS Router Defaults form.

• Gaps only apply to pipes on planes or racks. You should use obstruction volumes tomodel clearance of pipes from columns, etc.

• Gaps will always be the sideways displacement: any vertical difference between thecentrelines of pipes will not affect packing. Very small pipes will not be packed underthe edge of very large diameter pipes.



The Pipe Gap is calculated as follows:

With a 50mm wall-to-wall gap, the centre of a branch of OD 200mm will be placed 225mmfrom the centre of an adjacent branch of OD 150mm.

The PDMS Router Defaults form also has a Pipe gap rounding option. This optionensures that the centres of pipe are positioned at rounded coordinates relative to the edgeof the routing plane. Coordinates are always rounded up. If no rounding is required, leavethis value as 0. PDMS Router obtains values from the OD (for the current Pipe) or thegeometry (for adjacent Pipes), and assume that these are consistent.

For example, consider two Pipes, OD 145mm and 60mm, on a plane for which the gap is100mm. If the rounding factor is set to 10, the centre of the first Pipe will be placed at 80(rather than 72.5). The centre-to-centre distance will be:

72.5 + 100 + 30 = 202.5

which will be rounded up to 210. Hence the centre of the second Pipe will be placed at 290:

150200

50

225

60145

80 210



• Flanges on Routing Planes

If you need to run sections of Pipes which include Flanges along routing planes, you canspecify that the gap value will be applied as a wall-to-flange (WF) gap, if the flanges can bestaggered, or as a flange-to-flange (FF) gap, if the flanges are side-by-side on the plane.The default is wall-to-wall (WW) spacing. The spacing is controlled by the PLWW attribute ofthe RPLA. PLWW can be set to WW, WF or FF.

The Flange spacing options can be set in the following ways:• For single routing planes

set the options on the Create Routing Plane form, displayed when you selectCreate>Routing Plane on the PDMS Router form menu. You can also change thesettings for an existing routing plane on the RPLA Specification form, displayed whenyou select Modify>Routing Plane>Specification on the PDMS Router form.

• For pipe racksset the options on the Pipe Rack Definition form, displayed when you click OK on theCreate Pipe Rack form. You can also change the settings for an existing Pipe Rack onthe Modify Pipe Rack form, displayed when you select Modify>Pipe Rack on thePDMS Router form.

The flange width is the width of the default flange (i.e. the flange which is obtained with aSELECT command) for the branches at their current bore, even if there are other flanges onthe pipe rack.

Notes:

The flange width is taken as 0 if:• No rule is applied.• If you try to specify WF or FF spacing between branches either of which does not have

a default flange.

If necessary you can change the spacing using the additional pipe-specific gap on thePDMS Router Defaults form.

• When wall-to-flange spacing is used, the greater of the flange widths for the currentpipe and the adjacent pipe will be added to the wall-to-wall spacing.

• When flange-to-flange spacing is used, the flange width of both pipes will be added tothe wall-to-wall gap.

The size of flanges is found using the Flange Width (FLWI) rule, which is applied to thedefault flange for each branch at its current bore. See Automatic Pipe RoutingAdministration for more information about routing rules.

8.1.9 Importing a P&ID File

If your P&ID system is configured so that it is capable of outputting data for use in AVEVAPDMS, you can load your P&ID file into PDMS Router.

See Importing Data from P&ID Files for information about configuring P&ID output so that itis suitable for input to PDMS Router.

Exercise begins:

1. Navigate to the site or zone where you want to load the pipes from your P&ID. From thePDMS Router form, select Create>Add New Pipes from P&ID. The Import P&ID formis displayed.



2. Enter the directory and file name of the P&ID file that you want to load in the ImportFile text box. Alternatively, select the Browse button to display the File Browser whichcontains a list of the available files, then select the file that you require.

3. If you would like to keep a copy of the log file produced during import, enter a file namein the Log File text box. Alternatively, select the Browse button to display the FileBrowser which contains a list of the available files, then select the file that you require.

4. Set the Options you require:• Modify Elements, do not ask.

If you select this option, PDMS Router will modify Pipes and Branches which are inboth the existing model and the P&ID file. If you do not select this option you will beprompted to decide whether to modify the element or not. Minor elements (Valves,Tees etc.) will be made unnamed if they already exist, whether this button is on oroff.

• Do NOT delete generated macro. During import, a macro is created to generate all the components. Normally this fileis deleted after import, but if you select this option it will be kept.

• Show log file after import Displays the log file. The log file can be displayed later using the Display>Log fileoption on the menu at the top of the form.

• Unname tees after import. If an element has a name in DESIGN, Design Manager will try to find the name inPEGS. Tees do not exist in PEGS, and so each Tee found will generate an error ifthis option is not selected.

5. Select the Run Import button.The Modified Pipes & Branches list will show any existing Pipes and Branches thathave been modified when the P&ID was read in. As far as possible, PDMS Router willtry and keep any attributes that have already been set in the model, and anyconstraints that have been added to Branches. However, if the P&ID file requirescomponents to be re-ordered, elements will be deleted and re-created in PDMS,resulting in attribute settings and constraint associations to be lost.



Messages generated are also output to the Command Input & Output window, if it isdisplayed. The log contains messages relating to the progress of the import operation,and any errors or warnings. In particular, you must position the Branch Head, if theHREF is not set.The import file is processed in two passes:• Pass 1 will look for any components that appear more than once. For example, in

PEGS, a three-way valve will appear on three branches. The import process willremove the Valve from the branches that have the component set as a TREF,leaving it as a member of the main branch only.

• Pass 2 will generate the macro to create the elements.• If there is no Piping specification set in the P&ID file, PDMS Router will use the

default Piping specification set in the Default Specification form, selected from thePipework Application main menu bar.

8.2 Automatic Pipe Routing Administration

8.2.1 Routing Rules

Routing Rules are special AVEVA PDMS rules which are used to control, for example, howPDMS Router selects, positions and orientates components as Branches are routed, andalso how Pipes are packed on Pipe Racks and Routing Planes.

Note: For more general information about defining rules for setting attributes, see theAVEVA PDMS DESIGN Reference Manual.

You can apply routing rules to individual branches or all branches within a particular site,zone, or pipe. You can also apply rules to individual components and remove rules fromindividual components, as required.

• Routing Rule Purposes

There are different types of routing rules, which are used for different controls on the route.Rules are identified by their Purpose (PURP) attribute, and unlike other elements in AVEVAPDMS, you cannot create different, user-defined purposes for routing rules.

The routing rules available are listed below, identified by their PURP attribute, and with ashort description. The purpose is set to a four-letter code, but it is sometimes shown as amore descriptive text on the PDMS Router forms. How each rule is applied is described indetail in How Routing Rules are Applied.

Pre-processing

PRPR All rules with this Purpose will be executed before a Branchis routed.

Selection

BEND Bend or elbow selection: controls whether a bend or elbowis used for changing the direction of a pipe

REDU Reducer type: specified when concentric or eccentricreducers are used



• How Routing Rules are Constructed

Routing rules consist of PDMS expressions which define:• Selection: the elements to which the rule applies.

All rules must have a selection expression.• A Logical test which evaluates to TRUE or FALSE. For example, (ATTRIB ADIR EQ D)

specifies that the arrive direction is down.

Positioning

DNSM Downstream pipe requirement: the length of pipe requireddownstream to the next component

UPSM Upstream pipe requirement: the length of pipe requiredupstream from the previous component

ELEV Component elevation: absolute or relative elevation of acomponent

LOCA Component location: 3D position of a component

Orientation

MAJO Orientate on major axis: positioning on vertical or horizontalpipe segment.

MINO Orientate on minor axis: such as the orientation of ahandwheel

Clash exclusion

CLEX These rules are used to allow specified types of element toclash.

Pipe racks (and routing planes)

TRAV Pipe Rack travel plane selection: controls which pipe racktravel plane is used to route a particular type of branch

ENTR Pipe Rack entry plane selection: controls which pipe rackentry plane is used to route a particular type of branch

EXIT Pipe Rack exit plane selection: controls which pipe rack exitplane is used to route a particular type of branch

SHOE Shoe height requirement

WEIG Identify heavy pipe

ADGP Extra gap required on plane or rack

FLWI Flange width on plane or rack

Post-processing

POPR All rules with this Purpose will be executed after a Branchhas been routed.



Rules which use logical expressions are called logical rules. A Rule which does not have alogical expression is called a real rule, because its action (see below) is a real expression.

• The Action which AVEVA PDMS will carry out. The actions for logical rules will becarried out if the Logical test evaluates to False. For example, (AXES PP 3 IS N) orientates a valve so that the P3 axis is in the north direction.

- Actions

The Logical expression in a rule tests whether or not the component satisfies the rule. If not,that is, if the logical expression evaluates to False, and the rule has an action, the action willbe applied. PDMS Router will then re-test the component. If the logical expression stillevaluates to False, the Action will be reversed.

• Logical rules may or may not have actions. • Real rules must always have actions.

Of the logical rules, the following use actions:• Minor axis• Elevation. If no action is specified, and the rule fails, a message is output. • Location. If no action is specified, and the rule fails, a message is output.• Upstream pipe requirement• Downstream pipe requirement• Pre-processing• Post-processing

If you do not define an action for these rules, then the default action is taken, which dependson the rule.

• Using PML Functions in Routing Rules

The Logical and Action expressions in Routing rules can call PML functions. This allows youto define much more complex logical tests and actions than can be done using simpleexpressions. A function is called by setting the rule action to a text string which is the nameof the .pmlobj file. This file will contain the object definition, followed by a method definition.

The function must be defined using fixed names for the following elements:

Examples of calling PML functions are given in the following sections:

CEREF The DBREF of the element the rule applies to.

RESULT The returned boolean result. (Logical parts of rules only.)

RULEMETHOD The method which is applied.

OBSREF The DBREF of the Element clashing with the Branch. (Clashexclusion rule only).

Pre-processing rules See Pre-processing

Minor Axis orientation See Orientation

Clash exclusion See Clash Exclusion

Post-processing rules See Post-processing



• How Routing Rules are AppliedThe following sections describe in detail which expressions are required by each type ofrule, and how the rules are applied. Most of the examples are taken from Rules suppliedwith the product. To see more examples, select Settings > Routing Rules from the PDMSRouter form menu, which will display the Routing Rules form. Select a Rule Set, thenselect a Rule from the list. To see the expressions in the rule, select Modify, and the RuleAttributes form will be displayed.

- Pre-processing

All rules with this Purpose will be executed before a Branch is routed. The Action willnormally be a PML function, which must have been defined before the rule is applied.

This type of rule will typically be used where it s simpler to have a single rule to create,position and orientate several components rather than have individual rules. For example:

• To build pipes of fixed geometry using a single rule to position and orientate all thecomponents.

• To build templates for parts of branches, for example, a control loop at the start of abranch.

The Selection part of the rule will identify a key component: for example, you could identifyValves which will require control loops by setting a UDA to a certain value, and then settingthe selection expression to select all the Valves with the given attribute value.

The PML function will then create, position and orientate the components and finally set thehead working point attribute to the last component covered by the rule. PDMS Router willthen take over and route the Branch.

A suitable PML function is shown following. Note that at the end of the positioning andorientating commands, the RLOC attribute is set to 0 (Locked).

define object PREPROCESS member .CEREF is DBREF endobjectdefine method .RULEMETHOD() if ( !THIS.CEREF.owner.phdir.east gt 0 ) then prev tee ori and p3 is n dist 200 rloc 0 $!THIS.CEREF ori pa is w pos polar e dist 350 from prev tee rloc 0 next tee ori pa is w and p3 is n pos polar e dist 250 from pl of $!THIS.CEREF rloc 0 valv 1 of cref ori pa is w and p3 is up at w 500 wrt $!THIS.CEREF rloc 0

Pre-processing (PRPR) Logical, will have Action



elseif ( !THIS.CEREF.owner.phdir.east lt 0 ) then prev tee ori and p3 is s dist 200 rloc 0 $!THIS.CEREF ori pa is e pos polar w dist 350 from prev tee rloc 0 next tee ori pa is e and p3 is s pos polar w dist 250 from pl of $!THIS.CEREF rloc 0 valv 1 of cref ori pa is e and p3 is up at w 600 wrt $!THIS.CEREF rloc 0elseif ( !THIS.CEREF.owner.phdir.north lt 0 ) then prev tee ori and p3 is e dist 200 rloc 0 $!THIS.CEREF ori pa is n pos polar s dist 350 from prev tee rloc 0 next tee ori pa is n and p3 is e pos polar s dist 250 from pl of $!THIS.CEREF rloc 0 valv 1 of cref ori pa is n and p3 is up at w 500 wrt $!THIS.CEREF rloc 0elseif ( !THIS.CEREF.owner.phdir.north gt 0 ) then prev tee ori and p3 is w dist 200 rloc 0 $!THIS.CEREF ori pa is s pos polar n dist 350 from prev tee rloc 0

next tee ori pa is s and p3 is w pos polar n dist 250 from pl of $!THIS.CEREF rloc 0 valv 1 of cref ori pa is s and p3 is up at w 500 wrt $!THIS.CEREF rloc 0 endifendmethod

The input to PDMS Router would be Pipes with a main Branch with the following sequenceof components defined:

• Tee



• Valve with Stype CH • Tee

There would also be a second Branch, owning a Valve, with the Branch Head and Tailconnected to the two Tees in the main Branch, which will form the control loop.

The rule to call the function could be defined as shown:

The rule is applied to the elements required in the normal way. An example of the controlloop created is shown in the following picture.

Note: PDMS Router will lock the Tees and the Valves in position, so that they cannot bemoved by any rules which are subsequently applied.

• Selection

Bend or elbow selection (BEND) Logical, no Action



This rule will choose the type of component used to change direction. For example, theselection expression could be:

ALL BRAN MEM WITH ATTRIB ABORE LE 65

and the logical:

( ATTRIB TYPE EQ ’BEND’ )

This will ensure that all Branches with bores less than or equal to 65 will use Bends ratherthan Elbows.

Note: This rule will only be applied if you set the Change direction using option on thePDMS Router Defaults form to Rule.

This rule will specify whether concentric or eccentric reducers are selected. For example, ifthe default reducers in a specification are eccentric, and you want concentric reducers invertical sections of pipe but eccentric reducers in horizontal sections, the Selectionexpression in the rule could be:

ALL REDU WITH ( ATTRIB ADIR EQ U AND ATTRIB ADIR EQ D )

The logical expression to specify eccentric reducers in all the selected cases would be:

( ATTRIB STYP EQ ‘CON’ )

The default method of changing direction, set on the PDMS Router Defaults form, isusing Elbows.

The default method of changing direction, set on the PDMS Router Defaults form, isusing a Rule. The rule specifies that small bore pipes change direction using Bends

Reducer Selection (REDU) Logical, no Action



• PositioningThere are two pseudo-attributes which are particularly useful in positioning expressions:

The lengths are measured from the component up to one of the following:• A change of direction• A change of bore• The start or end of the branch• One of the following components: VALV, VFWA, VTWA, FILT, PCOM, TEE and

CROSS. (Any connection components such as flanges or gaskets are ignored.)

This rule controls the length of straight pipe which is downstream from the previouscomponent. If the rule logical fails, the action, if it exists, will be applied. The action shouldbe an expression that moves the component a distance from the previous to ensure astraight length of pipe. For example:

Selection

ALL TEE WITH ( ATTRIB APOS EQ ATTRIB LPOS )

Logical

( ATTRIB STLE GT ATTRIB ABORE * 10 )

You can omit the action by setting the Action field on the form to unset, but the result maybe unpredictable, particularly if other rules are being applied, and it is not recommended. Ifno action exists, and component positioning is head relative, the component will be moved2/3 the distance along the leg, and then re-tested. If component positioning is tail relative,the preceding component will be moved if necessary when it is positioned.

The default reducer in the Specificationis eccentric.

The rule specifies that reducers on verticallegs are concentric

STAP is the length of straight tube before the component.

STLE is the length of straight tube after the component.

Downstream pipe requirement (DNSM) Logical, can have Action



This rule controls the length of straight pipe which is upstream from the next component.

Selection

ALL TEE WITH ( ATTRIB APOS EQ ATTRIB LPOS )

Logical

ATTRIB STAP GT ATTRIB ABORE * 10

An example of an action is:

POLAR AXES PREVPP DIST 4 IN FROM PREVPP

where the POLAR AXES keywords are used to specify a position in terms of a distance in agiven direction from a point, and PREVPP is the previous p-point.

You can omit the action by setting the Action field on the form to unset, but the result maybe unpredictable, particularly if other rules are being applied, and it is not recommended. Ifno action exists, and component positioning is tail relative, the component will be moved 1/3of the upstream distance, and then re-tested. If component positioning is head relative, thefollowing component will be moved if necessary when it is positioned.

A Tee is positioned by default.

The rule is applied and the Tee is moved 2/3 of the distance along the leg between theElbow and the Routing Plane

Upstream pipe requirement (UPSM) Logical, can have Action

Elevation (ELEV) Logical, can have Action



This rule controls the elevation of a component. The following example uses the CLOSESTkeyword in the logical expression to specify that components must be positioned at a heightgreater or equal to 0.61m vertically above an EQUI whose purpose is FLOO.

Selection

ALL BRANCH MEMBERS

Logical

ATTRIB UP WRT CLOSEST EQUI WITH ( PURP EQ ’FLOO’ ) DOWN GE.61M

A position on the closest vertical segment of pipe equal to the required elevation will befound. If no position on the existing pipe can be found, the action will be applied with theposition adjusted to minimise the use of bends or elbows.

If the logical test is False, any action set will be applied.

This rule is used to position a component at a given location. The following example is a testfor a component in a sub-branch being positioned at p-point 4 of the connecting componentin the owning branch:

ATTRIB APOS EQ ATTRIB PPOS 4 OF HREF OF OWNER

If the logical test fails, the action will be applied and the test repeated. If it fails again, amessage is output.

The corresponding action expression would be:

ATTRIB PPOS 4 OF HREF OF OWNER

This will position the component at p-point 4 of the connecting component in the owningbranch.

• Orientation

This rule controls the major orientation of the component, which is the arrive/leave axis. Forexample:

ATTRIB ADIR EQ D

If this fails, the component will be moved to each leg in turn until one is found that passes.No action is allowed.

This rule controls the minor orientation of a component, which is the axis perpendicular tothe arrive/leave axis. Frequently this axis is the direction of a valve handwheel. Forexample:

ATTRIB P3 DIR EQ D

Location (LOCA) Logical, can have Action

Major axis Logical, no Action

Minor axis Logical, can have Action



If the rule logical fails, the action will be applied. If the logical then fails, the component willbe moved to another leg, and re-tested. If the component clashes, it will be moved along theleg and then re-tested.

If there is no action, the component will be rotated in increments of 90 degrees to find a non-clashing orientation which passes the rule. If after four attempts it still fails, the componentwill be moved along the leg and retried. If no suitable positions are found on the leg, thecomponent will be moved to the next leg and the procedure repeated.

Examples using PML Functions

The following example shows how you could call PML functions from the Logical and Actionexpressions in a Minor Axis rule for positioning a Valve at and angle of 45 degrees.

First, the Logical expression will be set to ( 'minological' ), which will call the following PMLfunction:

define object MINOLOGICAL member .CEREF is DBREF member .RESULT is BOOLEAN endobjectdefine method .RULEMETHOD() !THIS.RESULT = false if ( !THIS.CEREF.ADIR.east ne 0 ) then !THIS.RESULT = ( !THIS.CEREF.PDIR[3].up eq -

0.707107 and !THIS.CEREF.PDIR[3].north lt 0 ) elseif ( !THIS.CEREF.ADIR.north ne 0 ) then !THIS.RESULT = ( !THIS.CEREF.PDIR[3].up eq -0.707107 and !THIS.CEREF.PDIR[3].east gt 0 ) . . . . . . endif endmethod

If the Logical test evaluates to False, that is, if P3 does not have the specified orientation,the Action will be carried out.

The Action expression is set to ( 'minoaction' ), which orientates the P3 direction of thecomponent:

define object MINOACTION member .CEREF is DBREF endobjectdefine method .RULEMETHOD() if ( !THIS.CEREF.ADIR.east ne 0 ) then ORI and p3 is s 45 d elseif ( !THIS.CEREF.ADIR.north ne 0 ) then ORI and p3 is e 45 d endifendmethod

• Clash Exclusion

Clash Exclusion (CLEX) Logical



A Clash Exclusion rule allows certain clashes to be approved in advance. A use for this isspecifying that only non hazardous pipes are allowed in certain areas. Clash exclusion rulescan use expressions or functions.

Example using Expressions

For example, the following rule can be used where two groups of elements are alwaysallowed to clash. In this case, Branches carrying radioactive material have their PURPattribute set to RADI. All Zones which are safe for humans to enter have their PURP set toHUMA. The rule allows all Branches whose PURP is not set to RADI to pass through allhuman zones:

Selection

ALL BRAN MEM WITH ( PURP OF BRAN NEQ ‘RADI’ )

Logical

( PURP OF ZONE EQ ‘HUMA’ )

The selection part of the rule is used to identify the Branch or Branch member which isclashing and the logical applies to the obstruction clashing with the Branches.

Example using a PML Function

If a more complicated solution is needed, use a PML function. A simple example is

define object CLASH member .CEREF is DBREF member .OBSREF is DBREF member .RESULT is BOOLEAN endobjectdefine method .RULEMETHOD() !THIS.RESULT = false if ( !THIS.CEREF.owner.name eq '/ROUTE2-1' and !THIS.OBSREF.owner.name eq '/OBSTR42' ) then !THIS.RESULT = true endifendmethod

• Pipe Racks and Routing PlanesAutomatic routing along Pipe Racks is described in Creating and Using Pipe Racks. Insummary, PDMS Router sees a Pipe Rack as a group of routing planes. Each plane willhave its FUNCTION attribute set, for example to UTIL for planes which are going to routeutilities pipes. You should also ensure that Branches which will be routed along Pipe Rackshave their PURPOSE attribute set appropriately, so that you can identify which Branchesshould be routed along a given plane.

Note: In these rules, the selection expression selects Branches. The logical test is appliedto the Planes on the Pipe Rack.

This rule will control which travel plane of a pipe rack is used to carry a particular branch. Anexample of the selection expression, which would apply the rule to all Branches to withPurpose set to COOLING, is:

Travel Plane Selection Logical, no Action



ALL BRAN WITH ( PURP EQ ’COOLING’)

An example of the logical test, which will route the selected Branches along the Plane withits Function set to UTIL would be:

FUNCTION EQ ’UTIL’

Note: It is important to use the FUNCTION attribute in rule writing for the rule logical sincethe PURPOSE attribute is used internally.

This rule will determine which entry plane is used to control a branch as it enters a pipe rack.Normally there will be one above and one below, to allow for branches with both liquid andvapour contents to use the rack. An example of the selection might be:

ALL BRAN WITH ( PURP EQ ’COOLING’ AND :CONT EQ ’GAS’)

Note that both the PURPOSE and :CONTENT attributes would need to be set on the branchfor the rule selection to take effect. An example of the test could be:

FUNCTION EQ ’UTIL’.

This would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.

Note: It is important to use the FUNCTION attribute in rule writing for the rule logical sincethe PURPOSE attribute is used internally.

This rule will determine which exit plane is used to control a branch as it exits a pipe rack.Normally there will be one above and one below, to allow for branches with both liquid andvapour contents to use the rack. An example of the selection might be:

ALL BRAN WITH ( PURP EQ ’COOLING’ AND :CONT EQ ’GAS’)

Note that both the PURPOSE and :CONTENT attributes would need to be set on the branchfor the rule selection to take effect. An example of the test could be:

FUNCTION EQ ’UTIL’

This would cause pipes containing gas for cooling to use the upper entry/exit plane to get to/from the UTIL travel plane.

Branches routed via planes or pipe-racks can be offset by a user-specified distance from theplane to allow for shoe-heights. The shoe-height is specified using rules with PURPoseSHOE. For example:

Selection:

( ALL BRAN ALL BRAN MEM ) WITH ( ISPEC OF BRAN NE NULREF )

Action:

(PH OD * 0.25 )

Entry Plane Selection Logical, no Action

Exit Plane Selection Logical, no Action

Shoe Height Real



Note: The Action specifies the distance from the Pipe OD. Subtract the insulation thicknessif the shoe height if measured from the bottom of the Pipe.

You can specify that heavy pipes are placed at the edges of routing planes and light ones atthe centre. When you choose this packing method, the PLPM attribute of the plane will beset to WEIG, and PDMS Router will look for a weight rule to determine whether pipes arelight or heavy.

The logical expression will evaluate to False if the pipe is to be placed at the edge of therack. For example:

Selection:

ALL BRAN MEM

Logical:

( ATTRIB ABOR LT 300 MM)

All Pipes with Bore greater than 300mm will be placed at the edge of the rack.

See Packing Methods for more details of Pipe packing methods.

This rule allows you to specify an additional gap between some pipes, for example, very hotpipes.

Additional gaps are determined by rules applied to the default bend or elbow of a branch.For example, for branches with temperature greater than 500 degrees, the following rule willgive an additional gap of 0.2 times the arrive bore of the component:

Selection:

ALL BRAN MEM WITH ( TEMP OF OWNER GE 500 )

Action:

( ATTRIB ABOR * 0.2)

For more details of additional gaps, see Additional Gaps.

Flange width rules are used to set the gap between Pipes on Routing Planes and PipeRacks when the Pipe run on the plane includes Flanges. The rule is applied to the defaultFlange for the Pipe. The gap can be calculated in several ways.

Example 1

Selection:

ALL FLAN

Action:

( 0.25 * ATTRIB ABORE )

Heavy Pipe Logical, no Action

Extra Gap Real

Flange Width (FLWI) Real



Example 2

Uses flange parameters:

Selection:

ALL FLAN

Action:

ACTION ( CPARA[2] + CPARA[3] )

Example 3

The next example uses a property of the Flange, which would be specified in a dataset asfollows:

Owner /FLANGE.DATA.SETDescription Flange width PropertyDKEY FLWIPtype BOREPproperty ( ATTRIB ABOR * 1.5 )Dproperty 0Purpose unsetNumber 0Dtitle unsetPunits mmRuse 0

The rule could then be:

Selection:

ALL FLAN WITH ( PSPE EQ /A150)

Action:

ACTION ( PROP FLWI )

For more detailed information about how Flange widths are calculated, see Flanges onRouting Planes.

• Post-processing

All rules with this Purpose will be executed after a Branch has been successfully routed.They can be used to add extra details to a Branch such as Drains and Vents or slope theline. The Action will normally be a PML function, which must have been defined before therule is applied.

The following example creates an expansion loop:

define object POSTPROCESS member .CEREF is DBREF endobjectdefine method .RULEMETHOD() exit

Post-processing (POPR) Logical, will have Action



$!THIS.CEREF new elbo select ori and pl is up dist 1000

rloc 2 new elbo select ori and pl is $!THIS.CEREF.LDIR dist 300 rloc 2 new elbo select ori and pl is d dist 300 rloc 2 new elbo select ori and pl is $!THIS.CEREF.LDIR dist 300 rloc 2 routerendmethod

The following illustrations show a Branch, with and without the Post-processing Ruleapplied.

Figure 8:14. The Branch without Post-processing



Figure 8:15. The Branch after Post-processing, with expansion loops inserted.

8.2.2 Creating and Editing Routing RulesAVEVA PDMS stores rules within a hierarchy. There are two administrative elements withinthe hierarchy:

• Rule World, whose type is RLWL

• Rule Set, whose type is RLST

AVEVA PDMS stores routing rules, whose type is GRUL, within a rule set. When you createa new rule, you define the type of rule you want by selecting the correct purpose. You thencreate the rule by defining the expressions within it. Then you can apply the rule to individualbranches or all the branches in a particular site, zone or pipe.

By default, all rules in the rule sets applied to a branch will be considered to be applied toeach component in the branch. However, you can also disable any of the rules, or applyrules from other rule sets, to any individual component.

A sample set of rules is provided with PDMS Router in the Sample Project. The Rule Worldis named /PIPES-RULES, and it owns several rule sets. The rules in the rule sets areexamples which you can use to build your own set, and do not necessarily represent goodengineering practise.

Exercise begins:

To create a rule world:

1. From the PDMS Router form, select Settings > Routing Rules. The Routing Rulesform is displayed.

2. Select Create > Rule World. The Create Rule World form is displayed.

3. Enter a name for the world in the Name field, then click OK.The rule world is created and is displayed in the Members List. You can now create a ruleset within the rule world.

To create a rule set:

1. Ensure that you are currently at the level of the Rule World in which you want to createthe rule set.



2. From the Routing Rules form, select Create > Rule Set. The Create Rule Set form isdisplayed.

3. Enter a name for the set in the Name field.

4. Enter the function of the rule set, in the Function field. The function is simply adescriptive term which enables you and other users to identify the purpose of the rulescontained within the rule set.

5. Click OK. The set is displayed in the Members List. You can now create routing rulesand store them within the rule set.

• Creating a Routing Rule

Exercise begins:In the following procedure, you will create a rule to ensure that the default orientation of allgate valves is North.

1. From the PDMS Router form, select Settings > Routing Rules. The Routing Rulesform is displayed.

2. Select where the rule is to be stored by first selecting the rule world from the CurrentRule World option list, and then the rule set from the Current Rule Set option list.

3. Select Create > Rule > New to create a new rule.You will notice that there is a Copy option available from the Create Rule menu. Thisoption enables you to select an existing rule and use its details as the starting point fora new rule. To create a copy rule, you simply select the rule you want to copy, thenselect Create > Rule > Copy. You can then modify the details to suit your purpose. Youdo not want to do this in this exercise. Instead, you will continue to create a new rule. The Create Rule form is displayed.

4. Enter a name for the rule in the Name field. This is the name of the rule element(GRUL) that will be displayed in the Members List.

5. Click OK. The Rule Attributes form is displayed, as shown.



Note: When you create a copy of a rule, the Rule Attributes form is displayed, filled inwith the details of the copied rule. You can then simply edit the details of the rule.

6. Enter a description of the rule in the field at the top of the form. The description will bedisplayed in the Routing Rules form.

7. Set the Purpose option list to Orientate on minor axes.

8. Enter the expression ALL VALV WITH (ATTRIB STYP EQ ‘GATE’), in the Selectionfield. This expression tells PDMS Router that the rule is applicable to all valves thathave their attribute STYP set to GATE, that is, all gates valves.

9. Enter the expression ( ATTRIB PDIR 3 EQ N ), in the Logical field. This expressionchecks whether or not the direction of P3 on each gate valve is set to north. If it is, thenthe gate valve meets the criteria of the rule and no action is taken. If the direction of P3is not north, then PDMS Router performs the action expression described in the nextstep.Enter the expression (AXES PP 3 IS N AND AXES PL IS AXES PL OF PREV), in theAction field. This expression tells PDMS Router to change the direction of P3 to north,and make the leave direction the same as for the previous component.

10. The Rule Attributes form should now look as shown.

11. Click Apply. PDMS Router creates the routing rule. You can now apply the rule to aBranch in the usual way.



12. You can test the rule before you use it. Set the Test Rule drop-down list to the extent ofthe test. This will perform the selection operation defined for the rule, then perform thelogical test for each component selected, and report which components passed andwhich failed.

• Modifying a Routing RuleThis section describes how to edit a routing rule, using as an example the sample rulessuppied in the rule set TRAVEL-RULES. The rules are modified to give a better route for thepipe rack example in Creating and Using Pipe Racks.

• Using Rules to Specify How Pipes Use a Pipe Rack

You can specify the type of pipes you want to route on each level of a pipe rack, usingrouting rules. For example, you can tell PDMS Router to place all process pipes on thebottom level of a rack and all utility pipes on the top level of a rack. If you have more thanone entry/exit plane, you can specify the way in which pipes enter onto and exit from aparticular level. You may, for example, have all liquid utility pipes climbing onto a travelplane and all gas utility pipes dropping onto the same travel plane.

In this exercise, you will edit the example pipe rack rules that are supplied with PDMSRouter and apply them to avoid the pockets created by the default route.

Exercise begins:

1. From the PDMS Router form, select Settings > Routing Rules.The Routing Rules form is displayed. The Rules available are supplied in the sampleproject. Make sure that the Current Rule World is set to PIPE-RULES and theCurrent Rule Set is TRAVEL-RULES.

There are three Rules supplied: a Travel Plane Rule, an Entry Plane rule and an ExitPlane rule.

2. To see the expressions in the rules, select a rule in the list and then select Modify >Rule on the Routing Rules form. You will see the Rule Attribute form. The display forthe Travel Rule as shown.



On this form, note that:• The Selection text box contains the expression

ALL BRAN WITH ( ATTRIB PURP OF OWNER EQ PROC )

This means that the Rule can be applied to all Branches owned by Pipes whosePURP attribute is set to PROC.

• The Logical text box contains the expression:

( ATTRIB FUNC EQ 'PROCESS' )

This means that the Travel Planes must have their FUNC attribute set toPROCESS.

• To see the expressions in other rules, select the rule in the list on the RoutingRules form and click Current Rule on the Rule Attributes form.

• The Entry and Exit Plane rules as supplied both have their Logical expressions setto:

( ATTRIB FUNC EQ 'ENTRY' )

The next step is to change the Logical expression for the Exit Rule.

3. Select the Exit rule in the list on the Routing Rules form and click Current Rule on theRule Attributes form. Change the Logical expression to be:

( ATTRIB FUNC EQ 'EXIT' )

4. Before you can test the rules, you must set the Pipe PURP attribute to PROC. • Make Pipe 2001 the Current Element• Select Modify > Attributes Global from the Pipework Application main menu bar.• When the Global Attribute Change form is displayed:

• Select Purpose from the list of attributes• Set the All attribute data option button• Enter PROC into the with text box.



• Click Apply on the Global Attribute Change form.

5. Now back to the Rule Attributes form to test, for example, the exit plane rule. Selectthe exit Plane rule in the list and make sure that Pipe 2001 is the Current Element. Setthe Test Rule option button to Pipe. The Rule Testing form will be displayed, whichshould tell you that 1 Branch has been selected for the rule but 0 Plane. No Planeshave been selected because there are no Planes with Function set to EXIT.

6. Modify the Functions of the Planes in the Pipe Rack as follows. Make the Pipe Rackthe current element and select Modify > Pipe Rack from the PDMS Router form menu.On the Modify Pipe Rack form, change the Function of the planes as follows:

7. Associate the Rule with the Branches required. Select the Branch 2001/B1 on theRouting Rules form. Select Settings > Branch Rules from the menu on the PDMSRouter form. On the Branch Rules form, set Apply rule sets to All SelectedBranches. Select HIGH, and the rule will be added to the form.

Now re-route the Pipe. A more satisfactory route will be obtained.

• Deleting a Rule World, Rule Set or Routing Rule

To delete a rule world, rule set, or routing rule:

1. Navigate to the rule world and rule set you want to delete from the Current Rule Worldand Current Rule Set drop-down lists.

2. If you are deleting a rule, select the rule you wish to delete from the routing rules list.3. Select Delete > Rule World, Delete > Rule Set or Delete > Rule, as required. You can

also use the Delete options on the Pipework Application main menu bar.

Level 1 Upper Entry/Exit Plane: EXIT

Level 1 Travel Plane: PROC

Level 1 Lower Entry/Exit Plane: ENTRY



8.2.3 Placing Pipes on Racks and Planes This section describes how to set up rules which control:

• How spacing between Pipes on pipe racks and routing planes is calculated fromFlanges on the Pipes.

• How the weight of a Pipe can affect Pipe Rack Packing.• Shoe Height.

• Flanges on Routing Planes

By default, PDMS Router will run pipes along Routing planes with the wall-to-wall Pipe Gapgiven on the PDMS Router Defaults form. See Automatic Pipe Routing using PDMS Routerfor details.

If you need to run sections of Pipes which include Flanges along routing planes, you canspecify that the gap value will be applied as a wall-to-flange (WF) gap, if the flanges can bestaggered, or as a flange-to-flange (FF) gap, if the flanges are side-by-side on the plane.The default is wall-to-wall (WW) spacing. The spacing is controlled by the PLWW attribute ofthe RPLA. PLWW can be set to WW, WF or FF.

If WW or WF spacing is specified, the PDMS Router will look for rules of type FLWI andapply them. The size of flange is found using the Flange Width (FLWI) rule, which is appliedto the default flange (i.e. the flange which is obtained with an AVEVA PDMS SELECT) foreach branch at its current bore, even if there are other flanges on the pipe rack.

• When wall-to-flange spacing is used, the greater of the flange widths for the currentpipe and the adjacent pipe will be added to the wall-to-wall spacing.

• When flange-to-flange spacing is used, the flange width of both pipes will be added tothe wall-to-wall gap.

Note:

The flange width taken as 0 if:• No flange width rule is applied.• Either branch does not have a default flange.

If necessary you can also specify an additional pipe-specific gap, for example, for veryhot pipes.

- Example of Wall-to-Flange Spacing

If a rule is used, so that the flange width is set to 1.5 x bore, then wall-to-flange spacing iscalculated as follows.

The constant gap is set to 50mm. Then the centre of an insulated branch of OD 200mm,bore 100mm would be placed 435mm from the centre of an adjacent branch of OD 150mm,bore 140mm.



- Example of Flange-to-Flange Spacing

If the rule sets the flange width to 1.5 x bore, then flange-to-flange spacing is calculated asfollows:

½ OD Pipe A 100

Flange width Pipe A 150

Gap 50

Flange width Pipe B 210

½ OD Pipe B 75

Total 585



• Packing Methods

There are two packing methods available. PDMS Router will either place a pipe on a planeas near as possible to the edge of the plane, or pack heavy pipes at the edges of racks andlight ones at the centre. The packing method is an attribute of the Routing Plane. It can beset for the Travel Plane of pipe-racks and for individual planes.

If you select the By Weight method, the PLPM (Plane Packing Method) attribute of the planewill be set to WEIG, and PDMS Router will look for a weight rule, (PURP set to WEIG), todetermine whether pipes are light or heavy.

You can use weight rules to determine whether pipes are packed at the top or bottom ofvertical planes

- Horizontal Routing Planes

In the weight-related packing method on horizontal planes, for heavy pipes PDMS Routerwill search inwards from both edges looking for a free slot with a large enough gap betweenit and any adjacent pipe. The heavy pipe will be placed closest to whichever edge a slot isfound. For light pipes Router will first look in the middle of the plane or rack to see if this slotis free. Router will then search in both directions outwards looking for a free slot and use thecloser to the centre. Pipes for which no rule exists will be treated as light pipes and placed inthe centre of the rack or plane.

- Vertical Routing Planes

The weight-related packing method can also be applied to vertical routing planes with ahorizontal travel direction. If the weight-related packing method is used then, for light pipes,PDMS Router will search downwards from the top edge of the routing plane edges lookingfor a free slot with a large enough gap between it and any adjacent pipe. For heavy pipesPDMS Router will search upwards from the bottom edge of the plane. Pipes for which norule exists will be treated as light pipes.



• You cannot use weight-related packing for a vertical plane with a vertical traveldirection.

Example of Weight-related Packing

If the third and sixth pipes to be packed on a rack are ‘heavy’ and the others are light, theplacement of pipes will be:

- Additional Gaps

Sometimes certain pipes need to be placed further than others from their neighbours.Process pipes might need to be separated more than utility pipes. Extra-hot pipes, or pipeswhich will need tracing where the tracing has not been represented by the insulation, shouldhave wider gaps beside them.

The size of any additional space required can be found using an additional gap rule(Purpose ADGP) applied to the default bend or elbow of each branch at its current bore.

Example

Assume WF spacing is used, with a rule that that the flange-width is 1.5 x bore and that theuser has a constant 50mm gap. Then the centre of an insulated branch of OD 200mm, bore100mm, extra gap 20mm would be placed 465mm from the centre of an adjacent branch ofOD 150mm, bore 140mm extra gap 10mm.

15

3 6

2 4 7



• Shoe Heights

Branches routed via planes or pipe-racks can be offset by a user-specified distance from theplane to allow for shoe-heights. The user specifies the shoe-height using rules.

The Rules should have PURPose ‘SHOE’. Rules with purpose ‘SHOE’ do not have a logicalpart. Their action is a real expression giving the shoe height.

Note: The Shoe Height is calculated from the bottom of the pipe not the insulation

The real value (h) returned from a shoe height rule is used to specify the height, above arack or plane, of the bottom of the insulation. However, you may wish to specify a shoeheight (H) with respect to the bottom of the pipe itself. This is shown in the followingdiagram:



Using the shoe height rule, you can specify the shoe height as the expression:

h = H - ½ ( Insulation parameter[1])

Example

Rule with shoe height H of 200mm:

Selection:

( ALL BRANCH ALL BRANCH MEMBERS ) WITH ( NOT UNSET ( ATTRIB IPAR[1] ) )

Action:

( 200mm - 0.5 * ATTRIB IPAR[1] )

8.2.4 Importing Data from P&ID FilesIf your P&ID system is configured so that it is capable of outputting data for use in AVEVAPDMS, you can load your P&ID file into PDMS Router. This section describes whichattributes must be set before the P&ID data can be imported, and also the P&ID file format.

Note: The P&ID file is imported by selecting Create > Add New Pipes From P&ID. TheP&ID Import form is displayed.

• Attribute SettingsYou must ensure that the following branch and component attributes are set.

Rack or Plane

Shoe

h H

PipeInsulation

½ ( Insulation parameter[1] )



Branch Attributes:

Alternatively, you can leave both Ltail, Tdir, and Tpos unset. In this case, PDMS Router willcalculate the position based upon the components in the branch, and any component andtube rules that apply.

Component Attributes

You must set the Spref attribute.

• The Neutral Description LanguageThis Section describes a neutral description language which you can use to extract anintermediate ASCII file from your P&ID system. You can then use the file to recreate theP&ID in AVEVA PDMS for use with PDMS Router.

Before you attempt to create a neutral flat file, be aware of the following points:• All characters must be in upper case, except for names of elements, which can be

standard AVEVA PDMS format (/Pipe-1-B2).

Pspec Piping Specification to use

Ispec Insulation Specification to use

If the head connects to another branch, set:

Href Name of the element to which the head connects.

If the head is unconnected (Href is unset), set:

Hbor The bore of the head.

Hcon Connection type of the head.

Lhead TRUE - indicates that Hpos is a valid position.

Hpos The position of the head.

Hdir Direction of the head.

If the tail connects to another branch, set:

Tref The name of the element to which the tail connects.

If a tail is unconnected, set the following attributes:

Tcon Connection type of the tail.

Tbor The bore of the tail.

If the tail is unconnected (Tref is unset), then you do not need to set its position. If thetail’s position is fixed, set:

Ltail TRUE - indicates that Lpos is a valid position.

Tpos Position of tail

Tdir The direction of the tail.



• All comments take up one line and have two hyphens and a space as the first threecharacters.

• You can insert blank lines, if required.• You can use the space bar and tab to create space between fields and commands.

When you create a pipe or branch, the first command you must enter is START, whichenters set-up mode. Any elements that you create while you are in set-up mode belong tothe significant element specified in the last START command.

The general format of the file is as follows:

START PIPE /pipe_name... START BRANCH /branch_name... ...elements... END START BRANCH /branch_name... ...elements... ENDEND

Where element can be one of the following types:

CAP INST REDU TEE VALV VENT OLET

For example:

-- Here is a simple example of a neutral flat file.

START PIPE /Pipe2 PSPEC /DDD BORE 200 ISPEC /A1D START BRANCH /branch-1 HREF /PUMP1/N1 TREF /VESS1/NOZZ2 BORE 150 TEE /TEE3 80 VALV /VALVE2 GLOBE ENDEND

Before you perform an import, you must create the equipment that you require. This enablesthe pipes to set the HREF and TREF on the nozzles of the equipment. It is assumed that thenozzle names are the same in both the P&ID and AVEVA PDMS.

Each file must contain one or more pipes. Each pipe must have one or more branches. It isup to the P&ID system to decide what is a branch and what is a pipe. The following figureshows a simple P&ID.



The diagram could be represented as:• PipeA, PipeB, PipeC and PipeD

or• Pipe1/B1 (A), Pipe 1/B2 (B), Pipe1/B3 (C) and Pipe1/B4 (D).

- Command Syntax for P&ID Neutral Flat Files

Anything in lower case is one of the following:

PIPE>-START PIPE /pipe_name -+------------------. | | ‘-PSPEC pipe_spec -+-------------. | | ‘- BORE value +--contcontinued >--+- ISPEC -- insulation_spec . | | |- TSPEC -- tracing_spec ----| | | |- PSPEC -- pipe_spec -------| | | |- INSU -- value ------------| | | |- PRES -- value ------------| | | |- attribute -- value -------| .--------. | | / | ‘----------------------------+- nl -*- branch -+- END ->

Pump 1

Vessel 3

Vessel 1

Vessel 2

A

B

C D

value Positive or negative real number

integer Positive integer

logical TRUE or FALSE

nl New line



BRANCH>-- START BRANCH /branch_name HREF /name ---> continued

continued ---+-----------------------------. | | |- BORE integer --------------| | | |- PSPEC pipe_spec -----------| | | |- ISPEC insulation_spec -----| | | |- TSPEC tracing_spec --------| | | |- INSU insulation thickness -| | | |- PRES -- value -------------| | | |- attribute -- value --------| | | |- TREF /name ----------------’ | | | .-------<-------. |/ | *---- element ----' | ‘---------------- nl -- END ->

where element is any of the following:

Note• The STYPE set for each element can be omitted if a default STYP is set in the

specification. For example, a Tee could be specified by either:TEE /tee-1 T-Type 200

or

TEE /tee-1 200

where branch is the syntax to define a branch,see below

attribute is any Pipe attribute

INSU value is the thickness of the insulation.

CAP /pipe_name/cap_name stype

REDU /pipe_name/reducer_name stype value

TEE /pipe_name/tee_name stype value

VALV /pipe_name/valve_name stype

VENT /pipe_name/vent_name stype

INST /pipe_name/inst_name stype

OLET /pipe_name/olet_name stype



if the default STYP is set to T-Type. It is recommended that specifications are set up withdefault STYPs so if the STYP is missing in the flat file a valid component will still beselected and Router can route it.

In each case, element can optionally be followed by options from one or both of thefollowing:>----+--- PBOre integer ---------. | | |--- ANgle -----------------| | | |--- RAdius ----------------| | | |--- ABOre -----------------| | | |--- ISPEC insulation_spec -| | | |--- TSPEC tracing_spec ----| | | |--- LBOre -----------------| | | |--- PREssure --------------| | | |--- TEMperature -----------| | | ‘--- RATing ----------------+--- uval --> >----+--- STYpe -----------------. | | |--- TYpe ------------------| | | |--- ACOnn -----------------| | | |--- LCOnn -----------------| | | |--- PCOnn integer ---------+--- word --. | | ‘--- word ------------------+-- value --| | | ‘-- word ---+--->

• value is the new bore of the pipe for a Reducer (or enlarger), and the P3 bore for a Tee.Any change in bore along a branch can be specified by the BORE keyword. Forexample:

START PIPE /P-1 BORE 200 START BRANCH /B-1 BORE 100 REDU /R-1 BORE 50 ENDEND

• The bores at P1, P2 and P3 can be set individually. For example:

TEE /T-1 PBORE1 100 PBORE2 50 PBORE3 50

• If a component is at a different bore to the rest of the pipe, for example, a reducingvalve, its PBORE0 can be set. PDMS Router will insert a reducer automatically whenrouting the pipe. An example of this syntax is:

BRANCH /B-1 HREF /NOZZ-1 BORE 100 VALV /V-1 GATE PBORE0 50END

If the PBORE0 is set on a REDU along with the BORE, it will be ignored.



• The tracing and insulation specifications can be set with the syntax:

element TSPEC /tspec-1 ISPEC /ispec-1

• Elements that appear in more than one branch will only be created once. For example:Valve /V-1 is included in branch /B-1 and /B-2. Branch /B-1 has its TREF set to /V-1 sothe valve will not appear in /B-1. It is assumed /V-1 is an inline component for /B-2.

- Example of a Neutral Flat File

Below is an example of a typical neutral flat file. Different style layouts are shown for eachpipe.-- File to test import from P&ID to VANTAGE PDMS Design —- Pipes from Sheet X

START PIPE /PIPE1 PSPEC /A3B BORE 300 ISPEC /XXX INSU 100 START BRANCH /first_branch HREF VESSEL1/NOZZ1/ TREF PUMP1/NOZZ1 VALV /VALVE1 GATE REDU /REDU1 200 TEE /TEE 200 TEE /Tee-2 PBORE3 200 VALV /VALVE2 GLOBE CAP /CAP1 OPEN END START BRANCH /second_branch HREF VESSEL1/NOZZ2 TSPEC /t-spec VALV /GATE_VALVE GATE REDU /REDU2 CONC 200 ISPEC /I-spec TSPEC /T-spec END ENDSTART PIPE /PIPE2 PSPE /A1D BORE 200 ISPEC /DDD INSU 50 START BRANCH /branch-1 HREF /NOZZ3 TREF PUMP1/NOZZ3 BORE 150 TEE /Tee3 TEE-TYPE PBORE3 50 END START BRANCH /branch-2 HREF VESSEL1/NOZZ4 TREF PUMP1/NOZZ4 VALV /Valve-safety1 GLOBE REDU /R-1-1 BORE 100 END END

8.2.5 Command SyntaxThis section describes the syntax used in PDMS Router. Its purpose is to allow customers tobuild Router into their own systems, especially batch input, and to adapt the standardApplicationware. For most users, this should not be necessary as all important functionalityis available via Applicationware.

These commands can only be used in ROUTER mode. To switch from standard DESIGN toRouter, give the command:

ROUTER

The following errors will result if Router is not available...

(61,701) Cannot open router DSO due to:- <TEXT>

(71,702) Incorrect Router Library version. It is <INT> but should be <INT>

(61,791) No licences available for Piperouter

(61,792) Piperouter security error <INT>

(61,792) Piperouter security error



To return to DESIGN, give the command:

EXIT

Note on element identifiers

You should try to use AVEVA PDMS names as element identifiers.• If a reference is output and then re-input, it can result in an invalid reference. • Avoid referring to Elbows using “ELBO n of /B1”: PDMS Router re-creates Elbows

every time a Branch is re-routed, and the numbering can easily get changed.

• Conventions Used in the Syntax GraphsThe commands described in this chapter are presented in the form of syntax graphs.

• Commands are shown in a combination of uppercase and lowercase letters, wherethe capital letters indicate the minimum abbreviation. (Note: This convention doesnot mean that the second part of the command must be typed in lowercase letters;commands may be entered in any combination of uppercase and lowercase letters.)

• For example, the command ICONSTraint can be input in any of the following forms:

ICONSTICONSTRICONSTRAICONSTRAIICONSTRAINICONSTRAINT

• Commands shown in all uppercase letters cannot be abbreviated.• Command arguments are shown in lowercase letters. These are just descriptions of

what you need to enter. For example:

CLEAR n

• means that to remove the constraint number 3 , you enter:

CLEAR 3

• Syntax graphs are read from top left to bottom right. The start point is shown by >, andyou can follow any path through the graph until the exit point, shown by >, is reached.

• Points marked with a plus sign (+) are option junctions which allow you to input anyone of the commands to the right of the junction. For example:

>----+--- ABC -----. | | |--- PQR -----| | | ‘-------------+--->

• means you can type in ABC or PQR or just press Enter to get the default option.• Text in angle brackets <. . . > is the name of another syntax graph. This convention is

used for syntax which occurs in many places. The graphs referred to are described atthe end of this section. For example:

>----+--- ABC -----. | | |--- PQR -----| | | |--- <dia> ---|



| | ‘-------------+--->

• means you can type in ABC or PQR or any command allowed by the syntax given indiagram <dia> or just press Enter to get the default option.

• Points marked with an asterisk (*) are loop back junctions. Command optionsfollowing these may be repeated as required. For example:

.-----<-------./ |

>---*--- option1 ---|| ||--- option2 ---|| |‘--- option3 ---+--->

• means that you can enter any combination of option1 and/or option2 and/or option3,where the options can be commands, other syntax diagrams, or command arguments.

• The simplified format:.----<------.

/ |>---*--- name ----+--->

• means that you may type in a list of AVEVA PDMS names, separated by at least onespace.

Standard Syntax Graphs

Some graphs contain references to other, standard syntax graphs which are widely usedthroughout AVEVA PDMS DESIGN. References to standard syntax graphs are shown inangle brackets:

<example>

For more information, refer to the AVEVA PDMS DESIGN Reference Manual.

Ordering and Routing Branches

Ordering is required when routing a number of branches so that the main branches arerouted first before sub-branches such as drains and vents. This requires two commands:

ORDER---<SELATT>-+--<SELATT>---. | | ‘-------------+-->

and then

VAR <VARNAME> ROUTE ORDer

Can give the following error

(61,723) Could not order <REF> for routing

The ORDER command returns a collection of branch references sorted so that the mainbranches are first.

A network of branches for a given branch can also be found with the command:

VAR <VARNAME> ROUTE NETwork name

And then to route the branches:



ROUTE --- <SELATT>-+--<SELATT>---. | | ‘-------------+-->

If no branches or pipes are in the selection you get the following error:

(2,563) Wrong element type

Branch constraintsA route can be constrained to pass through points, along planes or to use pipe racks withthe following syntax. The current element must be a Branch.

PointsNEW POINT -+- AT <DOPE>-+-DIRection <DOPE>-+-LEAVedir <DOPE>-+-AFTER name -.

| | | | |‘- name -----+------------------+-----------------+-------------+-->

This creates a point in space with optional arrive and leave directions after either the head ofthe bran or one of its members.

Planes and RacksNEW PLANE name AFTER name --+-- LAST name ---. | | ‘----------------+-->

A plane should be defined by referencing a RPLA . When using a RPLA, the direction oftravel is fixed as the X direction for single planes and travel planes and Y direction for entryand exit planes.

For a rack the first name should be an RPLG which owns at least one RPLA with PURPPREX (that is, an entry/exit plane) and at least one RPLA with PURP not set to PREX (thetravel plane).

To remove a constraint use:

CLEAR -+---- n ----. | | ‘---ALL ----+-->

To move one constraint after another in the branch list.

REORDer -- n ---+--AFTER---. | | ‘--BEFORE--+--<INT> ->

To move a constraint to after a different component in the branch list.

EDIT -- n ---+--AFTER--- name ->

To query constraints:

Q ICONSTraint NUMBer

will return the number of point and plane constraints for a branch.

Q ICONSTraint TYPE <INT>

will return the type for a given constraint.Q ICONSTraint POINt <INT>-+--POSition ---------------------------. | | |--DIRection --------------------------| | |



|--LEAVdirection ----------------------| | | |--COMPonent --------------------------| | | |--RELAtion ---------------------------| | | |--ACTUal-+--POSition------. | | | | | | |--DIRection-----| | | | | | | ‘--LEAVdirection-+-WRT name -| | | | | ‘--------------------------------------+->

This allows the component parts of a point constraint to be queried. As the position anddirections can be stored as expressions, the ACTUAL command returns the calculatedvalues.

Note: RELATION and FIXED need not be queried as they are always respectively AFTERand FIXED.

If a DATUm is used as a point constraint, its position can be found by exiting from Routerand querying its attributes in the normal manner.Q ICONSTraint PLANe n ---+-- STARt --------------------------------. | | |-- FINIsh -------------------------------| | | |-- DIRection ----------------------------| | | |-- COMPonent ----------------------------| | | |-- LAStconent ---------------------------| | | |-- RELAtion -----------------------------| | | |-- RPLAne -------------------------------| | | |-- ACTUal -+--STARt ---. | | | | | | |--FINIsh --+-- WRT name -. | | | | | | ‘--DIRection -------------+---| | | |-- ACTUal -------------------------------| | | |-- FIXed --------------------------------| | | ‘-----------------------------------------+-->

Since a plane is defined using a RPLA, its dimensions are found by exiting from Router andquerying its attributes in the normal manner.

ConfigurationThis allows the behaviour of Router to be modified. It has the following syntax:CONFiguration -+-- ERROR <WORD> ------|

| ||-- DIRection <WORD> --|| ||-- PRSP <REAL> -------|| ||-- PRRO <REAL> -------|| ||-- ORDER <WORD> ------|| |



|-- MODE <WORD> -------|| |‘-- ITERation-- n -----+-->

ERROR can be set to MESS, in which case extra diagnostic messages are output duringrouting.

DIRECTION can be set to BEND, ELBO or RULE and allows the change of directionelements to be specified.

PRSP is the basic gap for pipe-rack spacing.

PRRO is the gap rounding value for pipe-rack spacing.

ORDER, MODE and ITERATION are not curretnly used n core PDMS Router, but can beused for the appware.

To query configuration setting, use:Q CONFiguration -+-- ERROR -------.

| ||-- DIRection ---|| ||-- PRSP --------|| ||-- PRRO --------|| ||-- ORDER -------|| ||-- MODE --------|| ||-- ITERation ---|| |‘----------------+-->

General Rule SettingThe following syntax is for setting the SELECTION, LOGICAL and ACTION attributes ofGRULES. The current element must be a GRULE.

GENEral RULEs SELEction <SELATT>

GENEral RULEs LOGIcal <EXPZL>

GENEral RULEs ACTIon <EXPRG>

GENEral RULEs ACTIon UNSET

To query the attributes set:

Q GENEral RULEs SELEction

Q GENEral RULEs LOGIcal

Q GENEral RULEs ACTIon

Rules can be used for routing in two ways. They can be SET, which means that a selectionof GRULEs are set and then used in subsequent routing during the design session.Alternatively, rules can be STORED, which means that the same GRULES will be used infuture routing, thus maintaining design intent. To specify which:GENEral RULEs USE --+--SET-----.

| |‘--STOREd--+-->

To SET rules:



GENEral RULEs SET -+-HIGH-.| ||-LOW--|| |‘------+-APPEnd------.

| ||-OVERWrite---|| |‘-------------+-<SELATT>-+-<SELATT>-.

| | | ‘----------+----------+->

The defaults are LOW priority and OVERWRITE.

Rules can then be UNSET with the following syntax...GENEral RULEs UNSET --<SELATT>--+--<SELATT>---. | | ‘-------------+-->

To query the set rules, the following syntax will return an array of GRULE references andtheir priority.

VAR <VARNAME> GRULEs SET

To STORE rules, the current element must be either a Bran, Pipe, Zone or Site. The storedrules will then apply to branches owned by that element. However, when determining whichrules to use, the program navigates up until it finds some rules to apply. Thus, if rules havebeen saved for Zone and Site say, then only the Zone rules will be used.GENEral RULEs SAVE -+-HIGH-.

| ||-LOW--|| ||------+-<SELATT>-+-OVERWrite --.| | || |--APPEnd ----|| | || ‘-------------|| |‘-- SET ------------------------+-->

The defaults are LOW priority and OVERWRITE.

To query the rules saved:

Q GENEral RULEs SAVED

To remove the saved rules for a particular element:

GENEral RULEs UNSAVE

Rule TestingAs writing rules is not always straightforward, the following functionality is provided toprovide feedback.

To test a branch member to see what rules apply to it and whether it passes them:VAR <VARNAME> GRULEs TEST --+--<WORD>---.

| |‘-----------+-->

The word is the type of rule to be tested, MAJO, MINO etc, and if not specified, all rules aretested.



To test plane rules the current element needs to be the branch to be tested.

VAR <VARNAME> GRULEs PLANE name

where the GID is the RPLG to be tested. The returned results are the travel, entry and exitplanes.

A branch member can also be tested by applying the action part of a rule to it with:

GENEral RULEs APPLY WORD

The word is the type of rule to be tested, MAJO, MINO etc. Note if the element passes therule already, then no action is carried out.

Router BannerPDMS Router has its own banner which can be queried (in Router mode) with thecommand:

Q BANNer

8.2.6 Special Router Attributes

There are a number of special attributes used by PDMS Router. These are described below.

RLOC

Attribute of branch members. Determines whether element is to be deleted or repositionedby Router.

HREL

Attribute of branch members. Logical. Determines if component should be placed as near toHead as possible (TRUE) or as close to Tail as possible (FALSE). If a component is tail-relative it will force all components between it and the next locked component or constrainttowards the Tail. The default is TRUE.

BRLO

Attribute of branch set and used by PDMS Router. Users should not normally set BRLO. Ifyou are routing a branch which has already been positioned, it is better to unset BRLO andthen set LHEAD and LTAIL as appropriate. Indicates whether the head and /or tail of branchis fixed or free. If the head / tail is connected to a nozzle or a piping component the value ofBRLO is ignored.

If the HREF is unset then the head must be positioned (LHEAD true) and the head of thebranch is fixed. Thus the head lock is only relevant when the head is connected to the tail ofanother branch. If the head is fixed the tail of the connected branch will be positioned wherethe head of this branch is, but if the head is not fixed the head of this branch will bepositioned at the tail of the connected branch.

RLOC = -1 Unset

RLOC = 0 Non-deletable and positionable.

RLOC = 1 Locked

RLOC = 2 Deletable



If TREF is unset the tail can be positioned and the tail of the branch fixed; or the tail can befree -when Router will calculate a position for it. When the tail is connected to the head ofanother branch it will be positioned where the head of that branch is unless the tail is fixed.

( N.B. Router does not consider the possibility of branches connected head-to-head or tail-to-tail)

If BRLO is not set before calling Router, then HREF, LHEAD, TREF and LTAIL attributes areused to set to a suitable value.

BRSTATUS

The setting of the BRSTATUS (Branch Status) attribute shows the routed status of theBranch. These values can be used in Autocolour rules so that Branches can be displayed indifferent colours according to whether they have been routed successfully or not. Thevalues are as follows:

PLPP

Attribute of RPLA. Shows where on a plane to place branches.

BRLO = 0 unset; Router will use LHEAD / LTAIL to calculate BRLO if necessary

BRLO = 4 free head and free tail

BRLO = 5 fixed head and free tail

BRLO = 6 free head and fixed tail

BRLO = 7 fixed head and fixed tail

0 Not Routed

1 Routed successfully

2 All routes clash - Using default

3 Clash using route

4 Route breaks rule

5 Routed ignoring invalid constraint list

6 Cannot find required component - Datacon will fail

7 System error - Unable to route branch

8 Serious data error - Unable to route branch

9 Error whilst routing branch

10 Route violates minimum tube length

PLPP = ABOV place above the plane

PLPP = BELO place below the plane

PLPP = CENT place at the centre of the plane



The default is CENT.

PURP - (RPLA)

For pipe racks, indicates which are entry/exit planes.

PURP = PREX - Entry/exit plane

If not set to PREX, then it is assumed to be a travel plane.

PURP - (GRUL)

The PURP attribute of a GRULE indicates the type of rule.


Pipework Design User GuidePipework Spooling

9 Pipework Spooling

9.1 IntroductionSPOOLER is the pipework spooling module for AVEVA PDMS. It allows you to split thepipework design into logical sections (spools) ready for fabrication. The spool data can thenbe output as isometric drawings using ISODRAFT.

SPOOLER works with Spool Drawings (SPLDRGs), which are created by selecting aninterconnected network of piping components to be added to the drawing. Once you haveselected the elements, the application checks that your selections form a valid pipingnetwork.

Spool Drawings contain a number of complete Spool and Field elements, divided by SpoolBreaks, where a SPOOL is defined as a run of piping components and tube that will beconnected during fabrication and a FIELD is an individual or group of piping componentsthat will be connected on-site during the erection phase. Spools cannot be split across SpoolDrawings.

Spool Breaks are normally defined by the software, when the application detects a changein the status of the Shop Flag (where the Shop Flag indicates whether the component will beincluded in a fabricated assembly (SHOP) or fitted during the erection phase (FIELD)). Youcan also force spool breaks manually, at joints where the Shop Flags are the same on allsides, and add Welds, to split pipes, in the design.

By setting the SFLimit (Spool/Field Limit) attribute for a SPLDRG to either BRAN, PIPE,ZONE or SITE, a spool break will be enforced at any change at the corresponding elementlevel.

For additional information on some important aspects of the SPOOLER module seeSPOOLER Reference Information.

9.1.1 Database UsageSPOOLER uses two databases:

• Fabrication database - This contains all your spooling data.• DESIGN database - This contains all the design data for the project.

SPOOLER has full read/write access to the Fabrication database but has only limitedaccess to the DESIGN database, only being allowed to change attributes relevant to thefabrication of the pipework (e.g. specifying Field Welds).

9.1.2 3D GraphicsThe pipework design or spooling models can be viewed at any angle or scale, includingstandard orthogonal and isometric views, in the 3D View windows. The windows can be set



to navigation only mode, allowing you to move around the displayed model and selectelements, or Design mode, to carry out actions on the model. Design mode makes use ofthe Event Driven Graphics (EDG) mode, which allows cursor picks to be used interactivelyas part of an operation, rather than just for navigation and element selection.

9.1.3 NumberingOnce you have defined the contents of your drawings, you can automatically number: parts,welds, spools, fields, bends and non-welded joints. The numbering always starts from oneof the end spools; the start point can be changed using the Reorder facility.

Part numbers can be created either across a complete spool drawing or to individual spools.

9.1.4 NamingDatabase elements can be given unique names using the Autonaming facility. Thisrecognises sets of rules which can be set up by a system administrator, from the Main Menuoptions. You can use this facility to both name new elements, as you create them, and toname existing elements, retrospectively.

9.1.5 Spooling Volume CalculationSPOOLER can calculate the shipping volume of a spool for you, enabling you to easilycheck its size. This could be used to check that a spool is not going to be too large for thefabrication plant or transportation.

9.1.6 Drawing OutputOnce you have defined your spool drawings, you can produce them as isometric plots,using ISODRAFT.

9.2 Setting Up the Database HierarchyIn this section, you will learn:

• about the databases used by SPOOLER• about the database hierarchies• how to login and start the tutorial exercise• how to create some administrative elements

Before you start to create any spool data, it is important that you know how such data isstored and accessed in the PDMS Databases, so that you will understand the terminologywhich you will encounter in the tutorial.

SPOOLER uses two databases: • Fabrication database, which stores all the spooling data• DESIGN database, which holds all the design data for the project.

SPOOLER has full access to the Fabrication database allowing you to set-up the hierarchyand add or delete elements at will. Whereas, SPOOLER has only limited access to theDESIGN database, to make changes that are relevant to the fabrication of the piping.



9.2.1 Database StructureThe Fabrication database structure descends from the World level (usually represented bythe symbolic name /*). The administrative levels below this (and their PDMS abbreviations)are Department (ISODEP) and Registry (ISOREG).

The database level below Registry (and its PDMS abbreviation) is the Spool Drawing(SPLDRG). This is the main operational unit of the database. Each Spool Drawing canrepresent a continuous network of piping components and tube within the overall pipingdesign The Spools and Fields that make up the Spool Drawing are held directly below it inthe database hierarchy.

The PDMS DESIGN database also descends from the World level, below which are theadministrative sub-levels Site and Zone. In the case of piping design data, the loweradministrative levels (and their PDMS abbreviations) are Pipe (PIPE) and Branch (BRAN).

Together, these hierarchic levels give the following overall format:

Figure 9:1. Database Hierarchies

9.2.2 Logging In to Start a SPOOLER SessionIn this section you will begin a hands-on tutorial exercise which gives a step-by-steppractical introduction to the ways in which you might use the SPOOLER module. The tutorialis based on the sample project, SAM, supplied with AVEVA PDMS.

You can go directly to SPOOLER when you first start PDMS or you can switch to it fromanother PDMS module. The method used to start PDMS depends on your operatingsystem.

The first step of the tutorial exercise starts with the logging in procedure.

Exercise Begins:

1. In the PDMS Login form give the name of the Project in which you want to work: enterSAM.

2. Give your allocated Username: enter PIPE.

Design Database Isodraft DatabaseWORLD (/*)

SITE

ZONE

PIPE

BRANCH

Design data defining individualpiping components

DEPARTMENT (ISODEP)

REGISTRY (ISOREG)

SPOOL DRAWING (SPLDRG)

Spool data defining individualspools and fields

WORLD (/*)



3. Give your allocated Password: enter PIPE.

4. Give the part of the project Multiple Database (MDB) you want to work in: enter PIPE.

5. Give the name of the Module you wish to use: select SPOOLER.Make sure that you leave the Read Only box unchecked, so that you can modify thedatabase as you work.

6. Click OK to start SPOOLER.

When SPOOLER has loaded, your screen looks as shown.

Figure 9:2. Application Screen

9.2.3 Creating Some Administrative ElementsYou will now create some administrative elements at the top of the Fabrication databasehierarchy, as previously explained.

Exercise continues:

7. Select Department from the drop-down list on the left of the SPOOLER tool bar and

click the Create button . The Create form is displayed, allowing you to name thedatabase element.

Note: This function can also be carried out by selecting Create>Department from the mainmenu bar.

8. On the Create form:



• In the Name text box enter “department1” and press the Return/Enter key, toconfirm the name.

• Click OK to create the element.

Note: That the new element appears in the Fabrication Explorer as the current element.

9. You will now create two Registries, under department1, by selecting Registry from thedrop-down list and clicking on the Create button.Name this registry ‘condensate_pumps’ on the Create form.

10. Create another Registry and name it ‘condensor_network’.Navigate back to department1, by clicking on it in the Fabrication Explorer, whichshould now look as shown:

Figure 9:3. Database Hierarchy

9.3 Controlling the 3D ViewIn this section you will learn how to:

• set up a 3D View window• manipulate the 3D View

3D View windows can be used to display all or part of the design model. These windows arecontained within the application window, and allow you to select an element by simplyclicking on it, which navigates to it in the database making it the current element (CE), oruse the cursor picks as part of an Event Driven Graphics (EDG) routine.

More than one 3D View window can be displayed at any time, allowing you to have differentviews of the model. The views can be controlled individually using the menu and buttonoptions on the forms or more than one view can be changed simultaneously from the ViewControl form.



Figure 9:4. 3D View Window

9.3.1 Setting up a 3D View WindowWhen you first start SPOOLER or when you create a new 3D View, the display window isempty. You must set it up to show the elements and view you wish to see. This involvessetting up 3 functions of the view:

The following sections describe how to set up these functions.

• View ContentsThe elements that are displayed in a 3D View window must first be added to the Drawlist.This can be done as follows:

• Select Display>Drawlist from the main menu bar, to display the Drawlist form andthen add the required elements.

• Select the required option from the 3D View shortcut menu.

• Select the required element in the Explorer and then click the Add CE button onthe main tool bar.

View Function Menu Option

View contents Drawlist

View limits Limits

Type of view Look or Iso



Note: Only one Drawlist can be defined, for all 3D View windows.

The elements are normally added to the Drawlist and displayed in the colour defined by the‘Autocolour’ rules. These can be set up by your system administrator. Alternatively, you canadd elements using specific colours. This can be done by either clicking the Colour buttonon the Drawlist form or by selecting Drawlist>Add CE with colour. This displays astandard colour selection form allowing you to select the required colour.

Additionally, you can apply a transparency factor to elements you are adding from theDrawlist form. This allows you to make structures semi-transparent, so that you can seeitems inside or behind them. This can be done by selecting the required degree oftransparency from the drop-down list beside the Colour button on the Drawlist form.

• View LimitsHow much of the Drawlist contents are actually shown in that window can be controlled bysetting the view limits. This can be set from the Limits options on the 3D View shortcutmenu. You can select anything from a single element up to the complete Drawlist orexplicitly define a 3D box, by entering the co-ordinates of two opposite corners. Alternatively

the limits can be set to the current element by clicking on the ‘CE Limits’ button on theleft of the 3D View window.

• Type of ViewThe type of view for that window, orthogonal or isometric, can be selected from the Look orISO options on the 3D View shortcut menu. These allow you to select from a wide range oforthogonal and isometric views or define a particular view.

You will now set-up a view of the complete design model.

Exercise continues:

11. As the Fabrication database is empty at this time you need to switch to the DESIGNdatabase to add elements to the Drawlist. • Select Display>Design Explorer from the main menu bar.

This switches you to the World (*) level in the DESIGN database.• Select ‘SITE SPOOLER-SITE’ in the Design Explorer.

• Click on the Limits CE button on the left of the view window, to set the viewlimits to enclose the complete site.

12. You will now add the base of the site to the Drawlist and display it.• Click on ‘ZONE SPOOLER-CIVIL’ to make it the CE and then select 3D View>Add,

from the shortcut menu.The base appears in the view window in the default colour and orthogonal view.

• Select Iso>Two from the 3D View menu to set the required viewing direction.

13. Now add the structures to the Drawlist using a different colour, to help differentiatebetween the types of element, and set a degree of transparency so that you can seeother elements under and behind the structures.• Navigate to ‘ZONE SPOOLER-STRUC’, and select it to make it the CE.• Select Display>Drawlist from the main menu bar, to display the Drawlist form.• Click on the Colour button to display a colour selection form and select a suitable

colour (e.g. Dark Grey; top row, fourth from right) by clicking on it.



Note: By default, SPOOLER uses Cyan and Green to represent Spools and fields,respectively. So these colours should be avoided when adding elements.

• Set the transparency level by clicking on the drop-down list beside the Colourbutton and selecting 50%.

• Click the Add CE button, to add the structures to the display with the selectedsettings.

• Close Drawlist form.

14. You can now add the equipment (ZONE SPOOLER-STRUC) and pipes (ZONESPOOLER-PIPE) to the display in different colours.

The complete site is now displayed in isometric view. The 3D View should now looksomething like Figure 9:5.: Isometric View of SPOOLER Sample Project, which has themain equipment annotated.

Figure 9:5. Isometric View of SPOOLER Sample Project

9.3.2 Manipulating the Displayed ViewWhen a 3D View has been set-up it can be easily manipulated, using the mouse (either byitself or in combination with the function keys), to show exactly the view you require at anytime. This includes tools for: zooming, panning and rotating the model.

The condensate pumps piping network is located at the left side of the model, as you nowsee it. You are going to manipulate the view so that this network fills the window, giving amuch better view of it. For information on using the Zoom, Pan and Rotate modes seeManipulating the Displayed View.

Exercise continues:

15. Zoom in so the model fills the display window.

16. Centre the outlet network in the view using the Pan mode.

17. Using the Rotate mode, rotate the model, to show it from a better angle:

SurfaceCondensor

HeatExchanger

SurgeTank

CondensatePumps

Centre LineMounted Pumps



18. Having obtained the required view, at this point it is not possible to see the completepiping network clearly, because the pipe rack is in the way. To remove the pipe rackfrom the view:• Right click on ZONE SPOOLER-STRUC in the Drawlist and select 3D

View>Remove from the shortcut menu.The 3D View should now look something like Figure 9:6.: Condensate Pumps PipingNetwork.

Figure 9:6. Condensate Pumps Piping Network

9.3.3 Saving and Restoring a ViewPDMS allows you to save up to four views of the model, which can then be restored bysimply clicking on the appropriate view control button to the left of the display.

You will now save two views of the model and then restore the view to its current setting.

Exercise continues:

19. To save the current 3D view as View 1:

• Right click on the Restore view 1 button to the left of the display.• Move the mouse over the Save 1 pop-up, so that it is highlighted and then release

the mouse button.The current view is now saved as View 1.

20. You will now change the view so that you can see the Condensate pumps pipingnetwork from the other direction. This makes it easier to see the inlet to the pumps andthe outlet from the heat exchanger.• Select Iso>Four from the 3D View menu. This shows the model from the opposite

direction to Iso 2.• Manipulate the view so that you can clearly see the required parts of the piping

network. The view should now look something like Figure 9:7.: Iso 4 View.

Heat Exchanger

CondensatePumps

Condensate PumpsOutlet Pipes

Outlet PipesHeader

Heat ExchangerOutlet Pipe

Condensate PumpsInlet Pipe



Figure 9:7. Iso 4 View

• Save this view of the model as View 2.

21. Restore the view to the previously saved settings by clicking (with the left mousebutton) on the Restore view 1 button.

9.4 Preparing the Site for SpoolingIn this section you will learn

• about inspecting a site• how to measure pipe lengths• how to insert welds

Before you begin spooling a site you should always check that the design data in the designmodel is consistent. It is also worth making any changes to the design model (e.g. insertingshop or field welds) that will obviously be needed, to save work later.

9.4.1 Checking the Design DataThe consistency of the data should have been checked before the model was sent forspooling. But, you can also check it in SPOOLER.

Exercise continues:

22. To check the data:• Navigate to the ZONE SPOOLER-PIPE zone in the Design Explorer.• Select Utilities>Data Consistency, from the main menu bar. This displays the

Data Consistency Check form.• Select Zone from the Check: scrollable list box and click Apply.

The main window will show the progress of the check, including any errors orwarnings.

SPOOLER will not run properly if there are errors in the consistency check. Warnings willnot affect the operation of SPOOLER.


CondensatePumps Inlet Pipe



9.4.2 Inspecting the SiteIf you spool the site and then make changes to the model (e.g. inserting field welds) youthen have to update the numbering, some of which may then not be in order. So, it makessense to try and make any changes to the model before spooling it, thus reducing the workinvolved.

The easiest way of doing this is to do a visual check of the site looking for any possibleproblems (e.g. very long pipes or complex networks) and for any parts you know will bewanted separately, for test purposes. You can then insert any required welds and spoolbreaks before spooling the network.

As the spools are completely assembled before they are shipped to the erection site, theymust be small enough to be transported. The maximum acceptable size for this exercise is12 x 2.5 x 2.5 metres. The length of the supplied pipe is 6 metres, so any lengths greaterthan this in one spool will have to be joined with a Shop weld.

You will now do a check of the condensate pumps piping network and insert any welds thatare obviously necessary.

Exercise continues:

23. To carry out a visual check of the site:• Restore the view so that you can see the complete site, from the Iso 2 direction.

Figure 9:8. Visual Check of Spooling Site

• A quick visual inspection of the network, see Figure 9:8.: Visual Check of SpoolingSite, shows that:

• The heat exchanger outlet pipe (Pipe 2007) appears to be to larger than ourmaximum shipping size.

• Also, the length of the bottom section of the heat exchanger outlet pipe appears tobe too long to be constructed from a single length of pipe (6 metres).

Note: The measurements of these pipes can be checked using the Measure facility,explained in the next section.

Outlet PipesHeader

Long Pipe




It is also known that the high pressure Outlet Pipes Header, see Figure 9:6.: CondensatePumps Piping Network, will require testing as a separate unit before any other pipes areadded to it.

9.4.3 Measuring the Pipe LengthsThe visual check of the condensate pumps piping network showed the probability that theheat exchanger outlet pipe (Pipe 2007) was:

• Too large to be shipped as a single spool.• The bottom length of pipe between elbows 3 & 4 was too long to be created from a

single length of tube.

To check these assumptions and work out where to insert welds you need to measure thepipe.

Exercise continues:

24. Restore saved View 2, so that you have a clear view of the heat exchanger outlet pipe.

25. Click the Measure button , to activate the measure facility.This displays the Measure and Positioning Control forms and an EDG prompt isdisplayed instructing you to pick the start point for the measurement.You will start by checking the length of the bottom length of pipe.• Manipulate the view so that the lower pipe is clearly visible.• Set the Type field, in the Positioning Control form, to p-point and the Option field

to Snap. The cursor changes to a small square.• Pick point P1 of Elbow 4, see Figure 9:9.: Picking the Start Measurement Point.

A message showing the selected start point is displayed in the 3D View and theEDG prompt changes, instructing you to pick the end point for the measurement.

Figure 9:9. Picking the Start Measurement Point

• Pick P2 of Elbow 3. The software calculates the distance and displays it in the 3DView and in the Measure form.

• This shows the length of the tube to be 7415.9 mm. Confirming that it is too long tobe fabricated from a single length of tube.

26. To measure the complete outlet pipe (Pipe 2007):



• Zoom out so that you can see the whole of the pipe.• Using the same settings as for the previous measurement, pick point P2 of Elbow 1.• Change the Type setting in the Positioning Control form to Graphics, allowing

you to select any graphical element The cursor in the 3D View changes to astandard arrow.

• Pick the very end of the outlet pipe, as shown in Figure 9:10.: Selecting the End ofthe Outlet Pipe.

• The distance between the two points is shown in the view and on the Measureform, along with the lengths in the X, Y and Z directions.

Figure 9:10. Selecting the End of the Outlet Pipe

27. Comparing the two measurements you made shows that splitting the bottom tube, atthe end nearest the heat exchanger, will divide the pipe into two manageable spools.

9.4.4 Inserting WeldsSPOOLER allows you to insert Shop and Field welds to split up the piping network. Fieldwelds can be used to cut a pipe into shorter lengths or break up a network where there areno convenient joints, these welds will be made at the erection site. Shop welds can be usedto separate parts or assemblies that need to be fabricated and tested before being attachedto other parts of the spool. Welds can be inserted to break a piping network at a p-point of aparticular component or at some defined point along a length of a pipe.

Note: Any welds you create are added to the DESIGN database.

• Inserting a Weld at a Design PointWhere possible, welds should be inserted at a p-point (Design Point) of a weldedcomponent, because the component is attached to the pipe by a weld anyway, so it is not



creating any extra work just moving the location for the work from the Fabrication Shop tothe Erection Site.

For more information on p-points (Design Points) see Piping Components.

• Separating the Header PipeYou will now insert welds to separate the outlet pipes header from the outlet pipes of thecondensate pumps.

Exercise continues:

28. The header pipe (part of Pipe 2006/B1 & B2) consists of 3 TEE components with twoend CAPs. The header, together with its outlet pipe, will be tested in the fabricationshop before shipping. It will then be connected to its inlet pipes from the condensatepumps at the erection site. Therefore you need to insert Field welds between the inletpipes and the header.To insert a Field weld between the header and one of its inlet pipes:• Zoom in so that the header pipe fills most of the viewing window, see Figure 9:11.:

Positioning a Field Weld on P3 of 2006/B2.• Select Create>Weld, from the main menu bar. This displays the Create Weld form.• Select Field from the Type drop-down list and check that the At drop-down list is

set to Design Point (p-point). Then click Apply. The 3D View switches to the create weld mode and displays the EDG instruction -‘Pick a Design Point for WELD’. The cursor changes to a small square with a pointin the middle.

• Position the cursor over one of the inlet TEE components (TEE 1 of 2006/B1 orTEE 1 of 2006/B2) then press and hold the left mouse button. The outline of the component is highlighted and the p-points are shown as dots,see Figure 9:11.: Positioning a Field Weld on P3 of 2006/B2.

• Move the cursor over a p-point. When you are exactly on top of it, a highlightedmessage is appended to the instruction at the top of the window telling you thename of the Design Point you are over.

• Move the cursor over Design Point P3, see Figure 9:11.: Positioning a Field Weldon P3 of 2006/B2, and release the button. The CHOOSE form is displayed allowingyou to select the type of weld you wish to insert.



Figure 9:11. Positioning a Field Weld on P3 of 2006/B2

• Select a suitable type of weld and click OK.The weld is created at P3 and the 3D View window returns to navigation mode.

Note: The Create Weld form remains displayed allowing you to easily create further welds.

29. Now insert a Field weld on the P3 of the other inlet TEE.

9.4.5 Splitting a Tube with a Weld If a pipe is too long to be fabricated from a single length of pipe, one or more Shop welds arenormally defined in its length to show the fabricators where to join the lengths. Also, if a pipehas to pass through an opening at the erection site it may need to be split with a weld.

The bottom tube of the heat exchanger output pipe (leave tube of ELBO 3) is longer than astandard length of pipe (6 metres) and the complete outlet pipe is too large for a singlespool. Splitting the bottom tube, at the end nearest the heat exchanger, with a field weld willdivide the pipe into two manageable spools, that can then be joined at the erection site.

Exercise continues:

30. To split the heat exchanger outlet pipe (Pipe 2007):• Select Field and In-tube on the Create Weld form. This activates the Position in

Tube frame, allowing you to set the position in the tube you want to insert the weld. • Select Behind Item in the drop-down list and enter the value 6000 into the

distance text box and then click Apply.The 3D View switches to EDG mode and prompts you to pick the tube in which toinsert the weld.

• Pick anywhere on that length of tube. You are then prompted to pick the elementfrom which to measure the distance.

• Pick Elbow 3 in Pipe 2007. This inserts the weld 6000mm back from the elbow.



9.5 Spooling the Piping NetworkIn this section you will:

• look at the principles of using SPOOLER • learn how to split the pipes at the Condensate Pumps piping network into Spool

Drawings, using the default Shop Flag settings.

9.5.1 Pipework SpoolingSPOOLER works with spooling networks, which are created by selecting pipework elementsto be added to a spool drawing (SPLDRG) . The selected elements must form aninterconnected piping network but are not limited to a single branch or pipe in the designmodel.

Spooling networks consist of interconnected spools and fields. Where a SPOOL is definedas a run of piping components and tube that will be connected during fabrication and aFIELD is an individual or group of piping components that will be connected during theerection phase.

Spools and fields are defined by picking an element in the 3D View window. If the elementhas been defined as a fabrication element (i.e. the SHOP Flag is true) it generates aSPOOL. Whereas, if the selected element has been defined as being fitted on site (i.e. theSHOP Flag is false) it generates a FIELD.

When an element is picked, the software searches all connected piping components andtube and then adds all adjacent components that have the same SHOP Flag status to thatspool or field. The ends of the spools, called SPOOL BREAKS, occur when the SHOP Flagstatus changes.

You can also force SPOOL BREAKS by defining Field Welds or Joints at the required pointin the SPOOL. Field welds can be used to split a piping section at a particular component orat some defined point along a length of tube. The forced spool break is used to create abreak at joint that does not have a field element in it (for example: a flanged joint with nogasket).

By setting the SFLimit (Spool/Field Limit) attribute for a SPLDRG to either BRAN, PIPE,ZONE or SITE (the default is WORLD), a spool break will be enforced at any change at thecorresponding element level.

SPOOLING NETWORKS can be defined by picking each SPOOL and FIELD in sequence,to add to the SPOOL DRAWING or by picking two ends of a continuous piping network.SPOOLER checks that it is an interconnected network before it adds all the spools andfields to the SPOOL DRAWING.

9.5.2 Creating Spool DrawingsYou will now create some Spool Drawings and spool the pipes between the condensatepumps and the heat exchanger (Pipes 2004, 2005 and 2006), into one of them.

Exercise continues:

26. Go to the Fabrication database, by selecting Display>Fabrication Explorer from themain menu bar and navigate to the ‘Condensate_Pumps’ registry. Now create three Spool Drawings, as follows:• Select Create>Spool Drawing from the main menu bar (or select Spool Drawing

from the drop-down list in the main toolbar and click the Create button) and namethe Spool Drawing ‘Inlet_Pipe’.



This becomes the Current Element (CE) in the Fabrication Explorer and isdisplayed as the active Spool Drawing in the text box on the SPOOLER tool bar.

• Now create two more Spool Drawings, named ‘Outlet_Network’ and‘Heat_Exch_Outlet’.

27. You will now start to spool the piping network between the Condensate pumps and theHeat Exchanger:• Navigate to the ‘Outlet_Network’ Spool Drawing, making this the CE.• Zoom in on the condensate pumps outlet network, as shown in Figure 9:12.: Adding

the First Spool.

• Click on the Add to Spool Drawing button in the SPOOLER tool bar. Note how the mode of the 3D View window changes, as indicated by the text in theprompt bar, see Figure 9:12.: Adding the First Spool. The next element you pick in the 3D View will be added to the Spool Drawing.

• Pick one of the flanges between the valve and the condensate pump, as shown inFigure 9:12.: Adding the First Spool. The flange and its leave tube change to thedefault spool colour and are added to the Explorer hierachy as SPOOL 1.

Figure 9:12. Adding the First Spool

• Pick the gate valve and then the elbow following the selected flange in the pipe.They are added to the Spool Drawing as FIELD 1 and SPOOL 1, respectively.

These steps illustrate how items can be added sequentially to a Spool Drawing.• Click further along this piping branch before it reaches the header pipe. The control

valve and the complete length of the pipe, as far as the Field weld you inserted inSeparating the Header Pipe, are added to the Spool Drawing.

• Pick the input pipe to the heat exchanger. The piping is now spooled between the firstcondensate pump and the heat exchanger, including the complete header pipe.

These steps show how the elements in between the existing spools and the picked elementare added automatically - as long as they form a continuous network.

• Add the rest of the network from the header pipe to the second condensate pump, tothe Spool Drawing.



9.5.3 Numbering the Spool DrawingSPOOLER allows you to generate numbers automatically for spools, welds, joints, bendsand parts. The numbering is normally used to provide full accountability and repeatabilitythrough design changes. The Parts Numbers can be applied to complete Spool Drawings,the default setting, or the parts can be numbered for each spool individually.

Although the spools and fields you have created are shown in the Fabrication Explorerthere is as yet no numbering applied to the components. You will now generate thenumbering for the Spool Drawing.

Exercise Continues:

28. To define what elements of the spools you wish to be numbered, selectSettings>Numbering from the main menu bar. This displays the Numbering Settingsform.This form contains three sections allowing you to:• Select what numbering data to maintain.• Select the part numbering option and define a spool prefix.• Select the default update numbering method.

You will leave the settings as they are at present, so close the form by clicking onCancel.

29. To generate the numbering, click the Update/Number button in the SPOOLERtool bar (or select Numbering>Update from the main menu bar).The software carries out a check of the Spool Drawing numbering (Note this will take afew seconds) and then displays the Update/Number Spool Drawing form, with theresults of the check shown in the Status section.

Note: The choices in the Update Choice Handling section do not affect you at this stage.

• To generate the numbers, click Apply. The numbering is generated and the data inthe Status section is updated to show the actions that have been carried out. Extraelements, including the Weld and Joint groups, are added to the Explorer hierarchy.

• Click Dismiss to remove the form.

Note: You should ALWAYS update the numbering after you have defined or modified aSpool Drawing.

9.5.4 Selecting Adjacent Field ComponentsGaskets on the ends of pipes (e.g. between a flange and the nozzle of an equipment)cannot be picked in the 3D View and therefore cannot be manually added to a SpoolDrawing. To overcome this problem, you can automatically include adjacent fieldcomponents, as separate FIELDs, when you add a spool to a Spool Drawing.

You will now use this option to add the gaskets at the ends of the pipes to the SpoolDrawing.

Exercise continues:

30. You will now correct the missing gaskets from the end of the pipe. This involves firstremoving that spool from the drawing and then adding it with the adjacent gasket.• In the Fabrication Explorer navigate back to the ‘Outlet_Network’ Spool Drawing.



• Click the Remove from Spool Drawing button , on the SPOOLER tool bar.The text in the Prompt bar changes to indicate the current operating mode.

• Pick anywhere on the pipe going up to the heat exchanger, to removes it from theSpool Drawing.

• Select the Include Adjacent Field Components button on the SPOOLER toolbar.Any spools you now add or remove from the Spool Drawing will automatically add/remove any adjacent field elements, such as the gasket on the end of the pipe.

• Click on the Add to Spool Drawing button and pick anywhere on the pipe going upto the heat exchanger, again. The spool is added and a FIELD is automaticallycreated for the gasket.

• Update the Spool Drawing numbering.• Navigate to the GASKet in the DESIGN database and check that it has been added

to the Spool Drawing.

31. Correct the omission of the gaskets on the other ends of this piping network (Pipes2004/B1 and 2005/B1), adjacent to the Condensate Pumps.

32. Now spool the inlet pipe to the Condensate Pumps and the outlet from the HeatExchanger into the appropriate Spool Drawings.

9.6 Advanced SPOOLER FeaturesIn this section you look at the advanced features of SPOOLER that allow you to check andmake further changes to the spooling model.

9.6.1 Checking the Spool SizeWhile it may be logical to have a long pipe as one spool, if that pipe is too large to betransported the spool may need to be split. The size of a spool can be checked inSPOOLER by querying the spool shipping volume.

Exercise continues:

37. To check the size of SPOOL 1 of the ‘Inlet_Pipe’ Spool Drawing:• Navigate to that spool in the Design Explorer.• Select Query>Spool Shipping Volume from the main menu bar.

This displays the Spool Shipping Volume form showing the name of the selectedspool and its dimensions, see Figure 9:13.: Shipping Volume of a Spool.



Figure 9:13. Shipping Volume of a Spool

This shows that the spool is too large to be transported according to thespecifications (12 x 2.5 x 2.5 metres) and will need to be split into sections forshipping.

• Split the pipe by inserting a Field weld on Elbow 1, but do not update the SpoolDrawing at this stage.

9.6.2 Selecting the Numbering Update OptionsThe numbers shown in the Design Explorer are for indication purposes only. They onlymatch the real spool numbers when the Spool Drawing is first numbered. When you updatethe numbering after you have changed something (e.g. inserted a field weld to split a spool)the members list numbers get out of synchronisation with the real numbers.

For example; if you have set up the following spool drawing:

and you then split ‘Spool 2’. When you update the numbering, it may look like this(depending on the Update Choice handling option you have chosen):

Explorer Numbering

SPOOL 1 SPL1

FIELD 1

SPOOL 2 SPL2

FIELD 2

SPOOL 3 SPL3

Explorer Numbering

SPOOL 1 SPL1

FIELD 1

SPOOL 2 SPL2

FIELD 2



The three options available when updating the numbering are:• Use first available data - The first spool in which the data has changed will

automatically pick up the first available number. When there are no more existingnumbers new data is generated for any remaining spools. (See the example above.)

• Always generate new data - Existing numbers are ignored and new data is generatedfor all affected spools. In the above example, SPOOL 2 would be SPL4 and SPOOL 3would be SPL5.

• Manual data selection - A form is displayed allowing you to decide which existingnumber to use for which of the affected spools or whether to generate new data. Youcould decide that either SPOOL 2, SPOOL 3 or neither of them uses the existingnumber (SPL2) in the above example.

These options can be set as a default, on the Numbering Settings form, or for each timeyou use them, on the Update/Number Spool Drawing form

You will now update the numbering on the ‘Outlet_Pipe’ Spool Drawing.

Exercise continues:

38. You must now return to and Update the Spool Drawing. • The WELD element is not in the Spool Drawing at this point, so to return to the

Spool Drawing, select Display>Fabrication Explorer from the menu bar.When you update the numbering, the Update Choice Handling options, on theUpdate/Number Spool Drawing form, now become important.

• Click the Update/Number button • Select Manual data selection in the Update Choice Handling section and click

Apply.The software starts to update the numbering, then when a choice has to be madethe Select Data for Spool Elements form is displayed allowing you to select thedata to apply to which spool.

SPOOL 3 SPL4

FIELD 3

SPOOL 4 SPL3

Explorer Numbering



Figure 9:14. Selecting Data for Updating Spool Numbering

• To apply the displayed attribute data, select SPOOL 1 in the Spool numberswindow and select the data in the right hand window, then click the Use SelectedData button.You will see that a new FIELD and second SPOOL have been created. The FIELDis the WELD element.

Note: In this case, once you have applied the data to SPOOL 1, the software willautomatically generate new data for SPOOL 2.

• Click OK on the Update Complete alert form.

9.6.3 Changing the Shop/Field SettingWhen an element is picked, the software searches all connected piping components andtube and adds all the components that have the same SHOP Flag status to that spool orfield. The ends of the spool are called SPOOL BREAKS and they occur where the ShopFlag status changes.

If the Shop Flag is true the selected components are added as a Spool. Whereas, if theShop Flag status is false the components are added as a Field.

The Shop Flag status for a piping component is normally set by its attributes in the DESIGNcatalogue, but this may have been changed by the designer or from within SPOOLER. Thiscould be used to break up a spool or to remove a spool break, where you want the wholeassembly to be fabricated as one piece in the shop.

Note: Any changes you make to the Shop Flag settings are added to the design model inthe DESIGN database.

The valves immediately after the Condensate Pumps are all welded and are going to beassembled with the tubing in the fabrication shop, not on site.

Exercise continues:

39. To change the Shop Flag status of the welded valves:• Switch to Navigate mode and select one of the gate valves next to a Condensate

Pump, this becomes the CE.



• Select Modify>Shop/Field from the main menu bar, this displays the Shop/Fieldform, which allows you to check and change the Shop Flag setting for any elementin the piping network.The Piping component frame at the top of the form shows the identity of thecurrently selected element and allows you to scroll through the elements in theBRANch using the Right and Left Arrow buttons. The Right Arrow button takesyou to the Next element in the list (downwards) and the Left Arrow takes you to theprevious element (upwards).

• Change the status of the Shop Flag by selecting Fabrication Material from thedrop-down list box and then clicking Apply.

• Use the Left Arrow button to move up the list and change the Shop Flag of thecontrol valve.

Note: The Shop Flag can only be changed on one piping component at a time.

• Repeat this procedure for the valves next to the other Condensate Pump.• Update the Spool Drawing and note the colour of the valves change to the spool

colour and the associated fields disappear from the Explorer hierarchy.

9.6.4 Forcing a Spool Break at a JointYou can also split spools by defining SPOOL BREAKS at Joints in the network, even thoughthe Shop Flags on either side of the joint are the same. e.g. a flanged joint with no gasket asshown in Figure 9:15.: Example of Using a Forced Spool Break.

Figure 9:15. Example of Using a Forced Spool Break

The Spool Break is forced by changing the CSFBREAK attributes for the selected pipingcomponents to True. When SPOOLER finds two adjacent True CSFBREAK or TSFBREAKattributes it inserts a Spool Break between them.

This function could be used to split pipes at any component, but this would create problemsduring the Erection phase because no method of connecting the two parts would be shownon the drawings.

Note: Any Spool Breaks you define changes the flags of those components in the DESIGNdatabase.

Shop True Shop True

CSFBREAKFalse

CSFBREAKFalse

Spool Break

Spool X Spool Y

CSFBREAKTrue

CSFBREAKTrue

All included in single Spool



Forced Spool Breaks can also be removed by selecting Delete>Spool Break from the mainmenu bar. You are then prompted to select the two piping components that you wish to resetthe C/TSFBREAK attributes on.

• Forcing a Spool Break at a Specified Element LevelTo force a spool break at any change of Branch, Pipe, Zone or Site, set the SFLimit (Spool/Field Limit) attribute for the SPLDRG to BRAN, PIPE, ZONE or SITE, respectively. Thedefault setting is WORLD.

9.7 Outputting Spool DataIn this section you will learn how to plot annotated spool drawings.

Drawings have to be produced for the fabrication of the spools. This is done using thePDMS ISODRAFT module which provides very powerful facilities for plotting any specifiedisometric view of all or any of the Spool Drawings. The views are annotated to show theupdated numbering and connection information and have an associated parts list. The list issplit into two sections:

• Fabrication materials• Erection materials.

9.7.1 Plotting the Spool DrawingsTo plot the Spool Drawings you need to: switch to the ISODRAFT module; select therequired Spool Drawings and then generate the plots.

Exercise continues:

40. To switch to the PDMS ISODRAFT module:• Select Spooler>Modules>Isodraft>Macro files from the main menu bar and click

OK to any confirmation dialogues.When loading finishes, the Application window and the ISODRAFT Explorer for theISODRAFT application are displayed on the screen.

Note: There are no tool bars on the ISODRAFT Application Window.

The menu bar gives you access to a wide range of facilities for generatingcustomised isometric plots. For the purposes of this exercise, you will simplygenerate isometric plots of the spool drawings using the supplied options files.

41. To generate isometric plots of the Spool Drawings:• Switch to the Fabrication Explorer and navigate to the ‘Outlet_Network’ Spool

Drawing.• Select Isometrics>Standard from the ISODRAFT main menu bar.

The Standard Isometric form is displayed allowing you to specify which plottingoptions to use.

• Select Company from the Options drop-down list and then selectADVANCED.MET (advanced metric) from the Standard iso options list, seeFigure 9:16.: Standard Isometric Options Form. Click Apply to start the isometricplotting process.



Figure 9:16. Standard Isometric Options Form

ISODRAFT: composes and annotates the PLOT files and compiles the materialtake-off lists. The time taken is related to the number and complexity of the PLOTfiles being created.When processing is complete, the following new ISODRAFT windows aredisplayed:

• Display List - Lists all the isometric plots created in this session, that are availablefor display, with the currently displayed plot highlighted, see Figure 9:17.: DisplayList Form.

Figure 9:17. Display List Form

• Display Isometric - This form is shown within the Application window. It shows thePLOT file currently selected on the Display List form, see Figure 9:18.: DisplayIsometric Form.



Figure 9:18. Display Isometric Form

• Isodraft Messages - this shows a log of the PLOT file process, including details ofany problems encountered, see Figure 9:19.: Isodraft Messages Form.

Figure 9:19. Isodraft Messages Form

Exercise Ends

9.7.2 Isometric Drawing ContentsThe content of each isometric drawing is calculated using complex algorithms to bestdisplay all of the required data in the available space. The algorithms are controlled by theStandard iso options selected before plotting the drawing.

The drawings are NOT TO SCALE (see the two sides of the U-bend in Figure 9:20.:Zoomed View of an Isometric Plot) but are displayed so as best to show the information.



Pipes with no components attached to them, at the end of the Spool Drawing, may even beabbreviated with just the annotation showing the true length.

The annotation data shown is also controlled by the selections made in the SPOOLERNumbering >Settings form. Any options deselected on this form are not included on theplotted drawings.

Figure 9:20. Zoomed View of an Isometric Plot

9.7.3 Drawing AnnotationsFigure 9:20.: Zoomed View of an Isometric Plot shows a zoomed view of an isometric plot,illustrating the annotation data. A ‘Key’ to the markings is shown in the table below.

Annotation Key Remarks

Dimension Value shown in break indimensioning line, or directedto line by arrow.

Spool Number Number in a double box withthe spool prefix.

Arrow points at the firstcomponent in the spool.

Part Number Number in a rectangular box,along pipe or arrow pointingto component.

Flanged components also showthe Gasket (Gxx) and Bolt set(Bxx) numbers.



For a full description of all the symbols used in the plots refer to the ISODRAFT ReferenceManual.

Weld Number Number in a circle Key for different types of weld isshown on the plot.

Joint Number Number in a diamond,prefixed by letter showingtype of joint.

F = Flanged joint S = Screwed joint C = Compression joint

Annotation Key Remarks


Pipework Design User GuidePipe Piece and Pipe Spool Production Checks

10 Pipe Piece and Pipe Spool Production Checks

AVEVA PDMS allows you to check pipe pieces and pipe spools for production readinessagainst welding machines, bending machines, pipe cut lengths on drawings and reports,and defined stock-lengths of tubing.

• Production checks run against available stock length and fabrication machines.• Fabrication machines are currently limited to bending and auto welding.

For more infomation about the production checks and the machines that carry them out seePipe Piece and Pipe Spool Data and Fabrication Machine Data.

10.1 Definitions

10.1.1 Pipe PieceA pipe-piece is the lowest level of fabricated item in the pipe. It relates to a continuous pieceof pipe tube that can be fabricated from stock material.

The pipe piece holds references to the components at the start and end of the piece. Thesystem derives pipe-pieces: users cannot create or delete them.

10.1.2 Pipe SpoolA pipe spool is a prefabricated part of a pipe or branch, often welded together in a workshopbefore being sent to be fitted on-site. Pipe spools typically comprise a bent pipe with weldedflanges at each end, but they can also be more complicated fabrications with branches,reducers, valves, and other components. AVEVA PDMS does not include gaskets in thespool.



The system derives spools: users cannot create or delete them.

10.2 Pipe Production Checks FormTo check pipe spools for production readiness, you need to be in the DESIGN module andrunning the Pipework application. To display the Production Pipe Checks form, selectUtilities>Production Checks from the main menu bar:



How the form appears initially depends on whether or not you have selected a pipe or pipeelement before you invoke the form.



No Pipe or Pipe Element Selected

Pipe or Pipe Element with No Spools Selected



Pipe or Pipe Element with Spools Selected

10.2.1 Generating SpoolsTo generate the spools for a pipe, select it in the Design Explorer and click GenerateSpools on the Pipe Production Checks form:



Alternatively select a part of the pipe in the 3D View and click Generate Spools on the PipeProduction Checks form to get the same result:



In each case the form tracks the currently selected pipe or pipe element.

10.3 Options on the Pipe Production Checks FormThe form has five sections that allow you to control different aspects of the production checkon the pipe and its spools:



Pipe Spools - Lists the spools for the currently selected pipe and shows their ProductionStatus.

Pipe Tasks• Validate Pipe - Runs the production checks against the entire pipe. The checks run for

each spool in the pipe that requires validating.• View Production Information - Displays the production information currently

associated with each pipe spool and pipe-piece.• Remove Machine Info - Removes machine fabrication information for all pipe spools

and pipe-pieces in the pipe.

Spool Tasks• Validate Spool - Runs the production checks against the selected spool.



• View Production Information - Displays the production information currentlyassociated with the spool and the pipe-pieces it contains.

• Remove Machine Info - Removes machine fabrication information for the selectedspool.

Navigation• View Spool in Graphics - Sets up the 3D View so the selected spool fits in it.

Setup Production Checks• Select Default Fabrication Machines - Allows the user to define the fabrication

machines to use when running production checks against the pipe spools.• Define Auto-Resolve Preferences - Sets options for automatically adding any excess

needed as a result of a check against a bending machine.• Define Auto-Naming Preferences - Enables auto-naming of new spools when they

are generated.• Define Stock Length - Sets up the stock length used in checks.

10.3.1 Setting Up Production ChecksProduction checks are run against fabrication machines and tube stock lengths definedusing the options on the Setup Production Checks section of the Pipe ProductionChecks form.

Select Default Fabrication Machines

If a pipe-piece does not have a bending- or welding-machine associated with it when theproduction checks run, the system checks the pipe-piece against all machines selected inthe default machine list. This allows the system to identify and assign fabrication machines.

To define the default bending- and welding-machines to use in production checks, clickSelect Default Fabrication Machines. The lower pane now displays a selectable list of theavailable fabrication machines.

Select the machine you want to use and click Apply; if you want to cancel the operation,click Back.



To avoid choosing incompatible machines, you can pick out fabrication machines that canhandle the pipe tubing in the selected spool. The system checks the bore, material, andlength of the tubes to see which machines can handle the spool.

To do this below Indentify Suitable Machines click For Spool x, (where x is the number ofthe selected spool) and the lower pane changes to display a list of the machines that canhandle the pipe tube in the selected spool:

Select the machines you want to use from the list and then either append them to thecurrent default machine list by clicking Append to Default Machine List or replace theentire list by clicking Replace Default Machine List.

Clicking Back will take you back to the previous screen.

10.3.2 Define Auto-Resolve PreferencesTo define auto-resolve preferences click Define Auto-Resolve Preferences. The lowerpane changes to display the available preferences:

If you check Include End Excess, the system adds excess pipe to the end of the pipe-pieceif needed.

If you check Include Feed Excess, the system adds feed excess to the pipe-piece ifneeded.

10.3.3 Define Auto-Naming PreferencesAuto-naming enables the automatic naming of new spools when they are generated. Whenselected, each newly created spool will be automatically named using the auto-naming



rules. If auto-naming is turned off then spools will be given default names (Spool1,Spool2...).

To define auto-naming preferences click Define Auto-Naming Preferences. The lowerpane changes to display the Use Auto Naming Rules checkbox.

To turn auto-naming on, check Use Auto-Naming Rules and click Apply. Click the Backbutton to return to the Setup Production Checks section of the Form. Naming rules can besetup by clicking on Define Naming Rules.... Feedback is given next to the Define Auto-Naming Preferences link to indicate whether auto-naming is currently ON or OFF.

10.3.4 Define Stock LengthThe system checks the final cut length of a pipe-piece against the available stock length.

To define the stock length click Define Stock Length. This opens an edit-box you can useto change the stock-length value:

Enter the new value then click Apply to accept the value, or Back to cancel and reset theform to the previous value.



10.3.5 Running a Production CheckTo run a production check against every spool in the pipe you want to validate, clickValidate Pipe; to run the checks against a single spool click Validate Spool. These optionsrun the production checks and show the results in the lower pane of the form.

Production checks run using the fabrication machines associated with the individual pipe-pieces of the spool.

If no machines are associated with a pipe-piece, then the system checks it against allmachines defined in the default machine list:

When the checks have run the spool list at the top of the form displays the results of thecheck for each spool. This can be one of the following three states:

• Successful - Production checks were successful.• Failed - Some part of the production check failed.• Valid for production - Spool had already been validated so was not rechecked.

The lower part of the form shows the results for each pipe-piece of the selected spool. A listof pipe-pieces shows the production check results per piece, and each piece also has oneof the three states above associated with it.



Selecting a pipe-piece from the list displays the detailed results of the check below the pipe-piece list. The information displayed in this part of the form depends on the results of thecheck. Some examples of different results follow.

Successful Check with no Modifications

You will see this result where the check succeeded against both bending- and welding-machines, if these machines were required, and the pipe-piece did not have to be modified.

The Results panel shows which, if any, bending machine was used and which flanges, ifany, can be pre-welded. In the example below, you can see no bending was required, andthe leave flange can be machine-welded by Wm1.

Successful Check with Modifications

In the different example below, you can see the check succeeded against both bending- andwelding-machines, and some excesses were needed to make the pipe-piece pass thechecks.



As well as the bending and welding machine information there is a list of excesses the piperequired. In the example above, you can see Bm1 is suitable for bending the tube, noflanges can be pre-welded, and both the arrive and the leave of the tube required excesses.For each excess there is a link-label for the type of excess.

If you click on this link the excess shows a tag in the graphics view so you can see where itapplies to the pipe-piece:

Failed Check with Modifications Required

If the pipe-piece requires excesses to pass the checks but you have set up the auto resolvepreferences not to include excess automatically, then the check will fail. In this case theresults display the excess required. You can accept these excesses to make the pipe-piecepass the checks.



You can also set the pipe to be manually bent and so ignore bending checks.

Non Resolvable Failure

The pipe-piece may fail the production checks for a more serious reason. For example, itmay not be possible to find a bending machine that can handle the pipe tubing the pipe-piece uses.



In this case the results panel shows the system cannot resolve the failure by adding excess.To overcome this, you can set the pipe-piece to be manually bent:

Stock Length Failure

If the pipe-piece also fails a stock length check then this is reported in the lower part of thepanel.

Expanding Machine Results Panel

You may be able to expand the bending machine and welding machine results in the resultspanel, to display more information. If there is more information to view then the Expand iconappears by the Bending Machine Result title. Clicking the title or the icon expands thebending machine results.



Modifying Production Information

You can also modify the production information applied to the pipe-piece. Click ModifyProduction Information… to display the required panel.

Use this panel to change the bending or welding machines and modify the end excesses orapply minimum feed to a leg.

Changing or Assigning a Machine

To change or assign a bending or welding machine click the appropriate link. If no machineis associated with the pipe-piece then Change bending machine… will read AssignBending machine….

If the tube is straight then there are no bending machine options. If there are no pre-weldedflanges then there are no welding machine options.



Select the required machine then click Apply. To cancel any changes and go back to theprevious panel, click Back.

After selecting a new machine click Accept Changes at the bottom of the panel to acceptthe changes.

Editing End Excess

To edit the end excess first expand the collapsible panel by clicking End Excess.

You can add your own end-excess by entering a value in the User Defined text box.

Click Accept Changes to accept the new value.

Applying a Minimum Feed to a Leg

To view the feed excesses applied to a leg between two bends, click Feed Excess toexpand collapsible panel.



For each leg there is an editable text box in which you can enter a minimum feed value forthe leg. If you enter a new minimum feed value for the leg then the system recalculates thefeed excess the next time it checks the pipe-piece.

Revalidating the Pipe Piece

After changing the production information you can revalidate the pipe-piece by clickingRevalidate Pipe Piece. This runs a production check on the pipe-piece with the newvalues.

Finishing Viewing Results

To finish viewing the results of the production checks click Finish Viewing Results to returnto the top level of the form.

Viewing Production Information

You can view the production information assigned to pipe-pieces of a spool without havingto go through a production check.

To do this click on View Production Information for either the pipe or a spool. This displaysa view of the production information assigned to each pipe-piece in the same way as doesclicking on Modify Production Information from the production check results panel.



Removing Machine Information

To remove all machine information associated with a pipe spool or all the spools on a pipeclick Remove Machine Info for either the pipe or the selected spool:



10.4 Renaming Spools

10.4.1 Individual renamingIndividual spools can be renamed by right-clicking on the spool to be renamed and selecting"Rename Spool" from the popup menu. A form will be displayed which allows you to enter anew name or reset the name, i.e. unset the name back to default.



10.4.2 Group renamingAll spools for a specified pipe can be renamed by right-clicking on any spool and selecting"Rename All". If auto-naming is turned on then spools names will be set using auto-namingrules, otherwise spool names will be set to default.

10.5 Automatic Flange AlignmentFor pipe-pieces and pipe spools that have been set up to be machine-welded, the systemensures it correctly orientates the piping model so flange-holes and spools align whenassembled.

The system checks flange-alignment as part of the pipe-checking and Datacon functionality.See Pipe Piece and Pipe Spool Data for more details.


Pipework Design User GuidePipe Sketches

11 Pipe Sketches

11.1 Creating Pipe SketchesPipe Sketches can be produced automatically in Automatic Drawing Production (ADP) usingproduction-checked pipe-spool data from the Design application. The sketches includedimensioned and scale drawings of a pipe spool along with tables of relevant manufacturingdata. For more on the details of how the sheets look and how you can customise them foryour own purposes see Pipe Sketch Administration.

To produce pipe sketches:

In DRAFT - General select DRAFT>Auto Drawing Production.

Then in DRAFT - Automatic Drawing Production, use the Explorer to navigate to therequired pipe and select:

Create>HVAC Sketches

The Pipe Sketches form is displayed and docked to the right-hand side of the window bydefault. The form can be undocked and moved as required.



The Pipe Sketches form can be resized such that list and text fields expand with it.



11.1.1 How to Use the Pipe Sketches Form



• Search CriteriaIn the Pipe Sketches form, the search criteria are entered for the spool using any or all ofthe following:

• Design Element to search under This is the name of the design element. You can populate the field using the CE buttonor by typing in the name.

• Filter the spools using Allow the user to filter the spools.

• All or part of the spool name Enter the spool name, either wholly or partially in the text box.

• Production Status Offers three options in a drop-down list:• Any - Matches all spools, both validated and not validated• Valid - Matches only spools valid for production• Not Valid - Matches only spools not valid for production.

• Sketch Status Offers three options in a drop-down list:• Any - Matches all spools, both with and without pipe sketches• Created - Matches only pipe spools with pipe sketches• Not Created - Matches only pipe spools without pipe sketches

Search

Click to action the search. The results obtained using the search criteria will be displayed inthe Search Results pane.

• Search ResultsLists all the pipe spool elements.

The list has four columns:

The Search Results pane has a popup menu which can be accesssed by right-clicking.

1. Name The name of the pipe spool

2. Valid True or False, depending on whether the spool has beenvalidated.

3. Sketch If a sketch has been created, this field displays the name ofthe resulting drawing, if a sketch has not been created, thisfield displays FALSE.

4. Drawn This field gives the date the drawing was created. If nodrawing exists the field displays ‘ - ‘



The options are:• Select All - Selects all pipe spools in the list• Clear Selection - Unselects all pipe spools in the list• Print Sketch - Print dialog to print all selected spool sketches• Delete Sketch - Deletes each selected spool sketch

Any number of spools can be selected from the list for sketch creation.

Now it is necessary to select the template to be used for the sketch, a storage area for thecreated sketch and a log file name. This is done by using the Sketch Creation Options partat the bottom of the form.

• Sketch Creation Options

This part of the form has the following:

Sketch Template - This must be an existing DRWG element that can be used as a templatefor the pipe sketch drawings.

CE button — This top CE button (denoted DRWG) allows for quick capture of the currentdrawing.

Create Sketches in Registry — The named element must be an existing REGIstry elementinto which the system puts all new pipe sketch drawings.

CE button — This bottom CE button (denoted REGI) allows for quick capture of the currentregistry.

Log File — The system records progress of the creation process as text that can be writtento file. This field shows the file name the system will write to. The system overwrites this fileif it already exists.

Browse button - Invokes a standard browse form to let you select a log file.

When the options have been entered, the sketches can be created and displayed by:



• Create Sketches - Actions the sketch creation, refreshing the Search Results pane toshow the spool sketch has been created and the date on which it was drawn.

• Display - Displays the selected spool sketch and adds it to a working list of sheets fordisplay, although it is only possible to display one sheet at a time. The up and downarrow icons can be used to navigate up and down the list.

11.1.2 Created SketchesWhen the system has created the pipe sketches it adds them to the DRAFT Explorer:

Selecting a created sketch from the list on the Pipe Sketches form and clicking the Displaybutton, displays the pipe sketch in the Main Display area.

The 3D View shows the model representation of the spool:



And a typical example pipe sketch drawing of a pipe spool looks like this:



11.2 Pipe Sketch Administration

11.2.1 Drawing Template

Every Pipe Sketch drawing is based on a Template Drawing used as the basic definition ofthe Pipe Sketch.

The Template Drawing contains views and layers like any other Draft Template drawing; forother Drawing information the Template Drawing references a Backing Sheet.



11.2.2 Backing Sheet

The Pipe Sketch references the Backing Sheet, which is generally user-defined.

It is a standard backing sheet containing the drawing title block, with drawing data displayedvia intelligent text e.g. #DATE<FR DRWG> and #:UDA_Name etc.

In addition to the standard title block, the backing sheet is used to identify and locate‘TABLES’ that are to be used on the Pipe Sketch.



These tables are identified by:

11.2.3 TablesIn database terms the Table is a NOTE of the Backing Sheet (BACK).

There are two notes required, one for the Table headings and one for the Table cells. Bothnotes are positioned at the same point. For example:

BACK named /DRA/MAS/BACKS/PipeSketch/A4 SETST

NOTE named */ExampleTable function ‘ENDPOINT SpPurpose ‘TABLE’

NOTE named */ExampleCells function ‘ENDPOINT SpPurpose ‘CELLS’

MaterialTakeOff function ‘MTO’ SpPurpose‘TABLE’

or SpPurpose‘CELLS

Bending Table function ‘BENDING’ SpPurpose‘TABLE’


Bending Activies

function ‘BENDINGA SpPurpose‘TABLE’


Welding function ‘WELDING SpPurpose‘TABLE’


Assembly function ‘ASSEMBLY SpPurpose‘TABLE’


End Points function ‘ENDPOINT SpPurpose‘TABLE’




The above is an example of a table defined on a backing sheet. Although this table is visiblein the view, it will in practice have its visibility flag (LVIS) set to false. The reason being thatthis table is copied onto the Pipe Sketch Drawing then the cells of the table are populatedwith data from the actual Pipe Spool.

The figure below shows the table in situ on the final pipe Sketch Drawing.

• MTO Tables

The above figures show the MTO/Material Take-off tables first on the backing sheet andthen on the finished drawing. On this type of table the ‘cells’ data need to be attributes of thePipe Spool elements. E.g. DTXR and MTXR attributes as used in the Description andMaterial columns.



• Bending Tables

• Bending Activities Tables

• Automatic Welding Tables



• Assembly Activities Tables

• End Points Tables

11.2.4 StylesAll Drawing Styles and Representations are inherited from the template drawing.

These include the View Representations, text colours and font size for Labels andDimensions.

11.2.5 Common ObjectThe system uses one object that does all the work to produce Pipe Sketch Drawings. This isso you do not have to use the form and graphics mode to produce a batch of drawings.

The common object is a global instance of a pipeSketches object called !!pipeSketch.

Example:

VIEWRrsf /DRA/PRJ/RERP/GEN/BASICLAYERTSIZE 3mm

etc



• The Key Members:

• Optional members

• Other Members set and used in the background by the system:

Member Type Comment

!!pipeSketch.createIn DBREF Must be an existing Registry - REGI element

!!pipeSketch.selectedTemplate

DBREF Must be an existing Drawing - DRWGelement.

!!pipeSketch.pipeSpool DBREF Must the an existing Pipe Spool - PSPOOLelement.

Member Type Comment

!!pipeSketch.logFile FILE The Form or User must write and read this file.

!!pipeSketch..drawingPrefix

STRING Default is ‘DR’.

!!pipeSketch..sheetPrefix STRING Default is ‘S’.

Member Type Comment

!!pipeSketch..type STRING Will always be ‘drawing’ or ‘drtmpl’.

!!pipeSketch..pipePieces ARRAY System records the Pipe Pieces of the PipeSpool.

!!pipeSketch..drawing DBREF System records the new drawing.

!!pipeSketch..sheet DBREF System records the new sheet.

!!pipeSketch..backingSheet

DBREF System records the backing sheet being used.

!!pipeSketch..mtoHeadings

ARRAY Array of strings read from backing sheet MTOtable.

!!pipeSketch..logData ARRAY Array of comment strings that user or form canread)



• An Example

11.2.6 Log MessagesTo write any message to the Log Data from any PML function use :

!!pipeSketchesLog(‘Text of your choice’)

To clear the messages from the Log Data use:

!!pipeSketch.emptyLogData()

To write to the log file use:

11.2.7 How to Define TablesUnder a Backing Sheet

BACK /ExampleBack SETST

Create NOTEsNEW NOTE */---Table SETSTFUNC ‘---’ (‘---‘ can be MTO, BENDING, BENDINGA, WELDING, ENDPOINT or ASSEMBLY)SpPurpose TABLE

Set the XYpos and usual attributes for text size colour etc.

Create and name TEXP and STRA elements under NOTE. In the example below there are4 TEXP elements and 7 STRA elements (Shown in Black) NEW NOTE */---Cells SETSTFUNC ‘---’ (‘---‘ can be MTO, BENDING, BENDINGA, WELDING, ENDPOINT or ASSEMBLY)SpPurpose TABLE

Set the XYpos and usual attributes for text size colour etc.

Create and name TEXP and STRA elements under NOTE.

!!pipeSketch.createIn = object DBREF (‘/MyRegistry’)

!!pipeSketch.selectedTemplate = object DBREF (‘/MyTemplateDrawing’)

!!pipeSketch.pipeSpool = object DBREF (‘/MyPipeSpool’)

--Then to create the sketch

!!pipeSketch.apply()

!!pipeSketch.logFile = object FILE(‘%PDMSUSER%/pipeSketches.txt’)

!!pipeSketch.openLogFile()

!!pipeSketch.writeLogFile() - This write the contents of .log Data to the .logFile

!!pipeSketch.closeLogFile()



In the example below there are 3 TEXP elements and 1 STRA element (Shown in Red)

11.2.8 Dimensions Dimensioning is controlled from the Template Drawing:

A VIEW will only be dimensioned if it has a LAYER with a PURPose of ‘DIMA’.

If this layer exists then the dimensions go into that layer.



The style of the dimension will be cascaded from the owning layer.

11.2.9 TagsTagging is controlled from the Template Drawing:

A VIEW will only be tagged if it has a LAYER with a PURPose of ‘LABA’.

If this layer exists then the tags will go into that layer.

The style of the tag will be cascaded from the owning layer, or taken from a symbol templatein the case of component tags.

A typical symbol may look like this:

To control how the components of the Pipe Spool are tagged.

Firstly:

Example:LAYERTASK

TKPARA

FUNC ‘TEMPLATE’ TKPARA ‘/MySymbol’

TKPARA

FUNC ‘OFFSET’ TKPARA ’10 10’

TKPARA

FUNC ‘TPEN’ TKPARA ‘1’

TKPARA

FUNC ‘FPEN’ TKPARA ‘11’

A LAYER with PURPose of ‘LABA’

Must own a TASK element with a SpPurpose of ‘TAGDEF’,

Which owns 4 Task Parameter elements (TKPARA)

With FUNCtion equal to ‘TEMPLATE’, ‘OFFSET’, ‘TPEN’ and ‘FPEN’

And suitable TPVALUEs.



When tagging views the system will create a Symbolic Label (SLAB) for each component,using the attributes of the above task parameters.

Secondly:

A LAYER with PURPose of ‘LABA’

Must own a TASK element with a SpPurpose of 'ARRLAB'

Which owns 6 Task Parameter elements (TKPARA)

And specific FUNCtions and suitable TPVALUEsExample:LAYERTASK

TKPARA

FUNC ‘Top Side’ TKPARA ‘On’

TKPARA

FUNC ‘Bottom Side’ TKPARA ‘Off’

TKPARA

FUNC ‘Left Side’ TKPARA ‘On’

TKPARA

FUNC ‘Right Side TKPARA ‘On’

TKPARA

FUNC ‘Margin’ TKPARA ‘5’

TKPARA

FUNC ‘Minimum Gap’ TKPARA ‘1’

When tagging views the system will now arrange the Label around the view, using theattributes of the above task parameters.

11.2.10 DefaultsUsers will generally have their own Sketch Templates for Pipe Sketches.

The very first time you display this form there will be a default AVEVA Template in theTemplate field and a default log file name in the log file field.

When the form is applied the current setting of the Registry, Template and Log File arewritten to a defaults file named %pdmsuser%/PipeSketches.pmldat

These values are used as the default next time the form is displayed.


Pipework Design User GuidePiping Assemblies

12 Piping Assemblies

Building pipes in PDMS is often a case of building single components into a complexstructure of branches and components. In engineering there are often fixed configurations ofcomponents which can be reused many times in a design and these form the basis ofassemblies.

An assembly in PDMS is a series of components and branches in a predefined configurationwhich may be copied into the Design many times. Alternatively, an assembly definition maybe created to access existing macros or forms. A typical piping assembly is shown above.

12.1 Creating AssembliesAssemblies are accessed from the Component Creation form in the Piping application inthe same way as any other component type. For an explanation of how the ComponentCreation form is displayed see Modifying Pipe Sequences.

Part of the Component Creation form is shown:



When the Assemblies entry is selected from Component Types, a list of assembly typesand subtypes is shown on the Component Creation form. For copy-base assemblies, theoriginal assembly is shown in a graphical view.

The Component Creation form now looks as shown:



Filter By option - allows various categories of assembly to be selected and then each subselection selects an individual assembly type.

When an appropriate selection has been made, you will be able to insert an instance of theassembly in a straight tube or connected to a component by clicking the Place... button orConnect button respectively.

If the assembly contains directional or multi bore components, you will be asked to supplythe relevant details via the CHOOSE form during the building process.

The graphical view is updated after each component to show you where the currentcomponent is. For example the above form shows a tee with a flange. This can be appliedon any line with any direction and bore so you are prompted at each point.



The Input form is shown to ask you in which direction to orientate P3 of the tee. The defaultdirection shown in the form is that of the original assembly. Changing the direction to Westand clicking OK completes the sequence and the assembly is built.



In this case a new branch has been created but the branch tail is left for completion later. Itis also possible for the assembly to be completed with the tail at the leave of the gasket.This happens automatically if the offline branch of the assembly has a connection type ofOPEN, CLOS, VENT or DRAN.

A similar result would be achieved using the Connect button on the Component creationcreation form, but in this case, the tee would be connected to the previous component to theinsertion point.

Origins

By default, assembly origins are at the arrive point of the first component in the first branchof the assembly. Certain assemblies need to be positioned using a different position, so it ispossible to define an assembly origin at some other point in the assembly. For example asimple assembly consisting of a flange, gasket and flange may need to be positioned by theflange face of the first flange. The assembly origin point is configurable using the assemblyapplication, so if an origin has been defined, it will automatically be used to position theassembly. If an assembly is connected to a component then the position is derived byconnecting the first component to the existing one.

User interaction

For example when a reducer is part of an assembly, the arrive end is determined by the sizeof pipe at the insertion point. The leave of the reducer cannot be determined automaticallyby the copy process as it may be a number of different values.

The same applies for a reducing tee where the branch size may be determined by theheader size.

Another problem arises when the first component in the assembly is a directionalcomponent like an elbow, tee, eccentric reducer etc. These all have to be orientated toensure that they are inserted in the correct position and orientation.

When the system cannot decide the orientation or size of a component automatically, youare prompted to enter a value or to choose a component from the specification.

12.2 Assembly HierarchyIn order to separate Assemblies and other design template type items from the main designdata, a separate hierarchy is available. At DESIGN World level a separate World type calledan "Application Data World" can be created. The concept of an Application Data World is to



provide a storage area for design type items which are not part of the design model but formsome kind of reference model or starting point for real design items. The benefit of a separehierachy is that the Application Data World is separated from the normal design, and realdesign, items will not be clash checked against a set of assemblies.

Note: This sounds like the Template structure but Templates (TMPLs) are generallyconsidered as single entities. In contrast application data provides a reference modelwhich is built using conventional design tools.

Templates may also be part of the application data structure.

The Application Data World hierarchy (APPLDW) is as follows

The Application Data World owns Application Data Area (APPDAR) which in turn ownApplication Data (APPLDA) elements.

From the point of view of assemblies, each individual assembly will be an Application Dataelement owning a ZONE, PIPE, DDSE (Design Data Set) and one or more branches.

Note: an assembly may be as little as a single component but it must be part of a standardpipe/branch structure. Every piping assembly must have an owning Zone and Pipefor administration purposes.

Each assembly also has a Design Data Set as part of its structure. This is used to storerules associated with the assembly and its individual components. The Design Point Set(DPSE) is not used by this utility.

Piping assemblies are evaluated at branch level where the head of the first branch is thestarting point for the assembly. The components of the first branch are considered to be in-line so the first branch itself is not replicated. All other branches are copied as new branchesin the pipe.

Instances of assemblies in the piping design are a series of components which are replicacopies of the original assembly components but utilising the same piping specifications andbore of the host pipe.



For example a FLAN GASK FLAN combination as an assembly could be used on any sizeor any specification provided that the appropriate components exist and the STYPEs remainconstant. In this situation a single assembly could be utilised for all cases.

This principle is not applicable for all types of assembly as a simple copy may not beenough to satisfy the design requirements and you may need to enter some values.

12.3 Building and Maintaining AssembliesThe assembly building and maintenance application is accessed by selecting Utilities >Pipe Assemblies from the main menu bar in the Piping application.



The displayed Pipe Assembly Manager form enables the building and editing ofassemblies

The Pipe Assembly Manager form is split into separate panes with different functions:• The top pane allows the assembly hierarchy (World Area and Assembly) to be created.• The Explorer view shows the assembly hierarchy (except for the DDSE and its

members)• The Assembly Rules pane is context sensitive to create and edit rules for both the

assembly and its members.• The bottom pane is a 3D view to show the assembly contents.

12.3.1 Creating the Hierarchy.The top part of the Assembly Manager form allows you to create and move around theAssembly hierarchy.



• Display Name/Description - option to show assemblies by name or description forconvenience. In applying Assemblies in the design, only the description is displayed.

• CE button - aligns the form with the currently selected assembly. • Application World, Application Area and Assemblies drop-down lists are user

defined and show a list of what has been created.• Create World, Create Area and Create Assembly links - each displays the

appropriate create form to create the Assembly hierarchy.

The Purpose option of Piping Assembly is selected, which sets a purpose attribute of PASY.This type of form is also used to create assembly areas and assemblies.

12.3.2 Building an AssemblyBuilding an assembly is in two stages. In the first stage you create the basic assemblyhierarchy using the Create Assembly form.



This creates the basic hierarchy with an appropriate zone, pipe and data elements. In thenext stage the assembly design is created.

Although it is possible to build assemblies using standard piping commands, the easiestway to create an assembly is to identify some existing design and copy it into the pre-builtassembly using the Copy Design button on the Pipe Assembly Manager form.

A typical example is shown below

First all of the components to be copied into the assembly are selected. This can be donegraphically by holding the right hand mouse button down and enclosing all of the items in aselection box or alternatively selecting individual items in conjunction with the control key.

Once the appropriate design elements have been selected, they can be copied into theassembly using the Copy Design button. This copies all of the selected elements into oneor more branches depending on the configuration. If more than one branch is involved, thecopy process prompts the user to identify the main branch, before the copy takes place. For



example in the vent shown above, the main branch is the one containing the Tee becausethis must be in place before the second branch is built.

After the Copy Design process has completed, the form’s Explorer View and 3D View showthe assembly contents.

Note: Branch1 has a Tee (sockolet) as its only member and the head and tail of the branchis connected to each end of the Tee. When the assembly is inserted into a pipe, thehead and tail are ignored and the first component to be built will be the Tee.



The assembly is now complete although it is possible to add additional rules for selectionorientation and positioning.

12.3.3 Non-Graphical AssembliesIn order to cater for users who have existing functions or forms to create assemblies it ispossible to build an assembly which either runs a function or shows a form. The execution isdone from the Connect or Place buttons on the Component Creation form. These do notinstigate any other operation other than starting the function or showing the form, so all userinteraction is done via the user called routines.

To enable an assembly to call a function or show a form, a basic assembly needs to becreated and you need to add the appropriate input to the assembly rules panel as shownbelow:

To enable the assembly to run a function, the Function line in the Assembly Rules box isselected and the New button is clicked.



In the displayed Pipe Assembly Rules form, the Function Name is entered without the "!!"or the extension .pmlfnc.

When the OK button is clicked, the function name is added to the Assembly Rules andstored in the Assembly Design Data Set so that it can be run each time the assembly isused. The same method is used to store form names.

12.3.4 Primary and Secondary OriginsOne of the most common types of assembly is likely to be a set of break flanges where therelevant points for positioning the assembly are on either flange face. To enable anassembly to be positioned by some other feature, it is possible to set Primary andSecondary origins.

When the option to insert an assembly in a section of tube is selected, the arrive point of thefirst component is used to position the assembly. If a primary origin is present, this is usedinstead. If you choose to connect an assembly, the first component is positioned at the leaveof the selected item.

Note: Secondary origins are used in pipe splitting to derive correct spool lengths withoutthe thickness of the gasket. See Assembly Build Origin.

To set a primary or secondary origin, the appropriate line in the Assembly Rules pane isselected and the New button is clicked to display the Pipe Assembly Rules form.



The PICK button can be used to pick a point in the graphics view or alternatively theElement name or reference number and the required PPOINT number can be entered onthe form.

All values may be edited or deleted by selecting the rule value and using the Edit or Deletebuttons accordingly.

12.3.5 Piping Assembly Component RulesAs well as rules on the assembly itself, each component may also have rules.

Note: there are no rules for pipe and branch levels

Component rules are necessary to add greater flexibility to assemblies in general use. Theconcept of copying an assembly instance has limitations where specifications have differentSTYPEs (see STYPE Rules), because the selection will fail. For example in the AVEVAsample project, the STYPE for a gasket in one specification is RF where in another it is G.One solution to this problem would be to have two assemblies to cater for both cases butthis is dealt with by having rules in the assembly template.

Assembly rules cover multiple STYPEs, Positions, Orientation, and restricting the STYPE toa particular SPEC/STYPE combination.

Each component in the assembly may have instances of all rule types associated with it.When the component is copied into a design instance the rules are evaluated in place of thedefault actions. If no rules are present then a new item is created using the same relativeposition and orientation as that of the original. The distinct actions for each component are:



The addition of rules enables the default actions to be supplemented or overridden asdescribed below:

12.3.6 STYPE RulesSTYPE rules are a mechanism to allow an assembly to work with different specifications bysupplying a list of alternative STYPES. STYPE rules are in two parts, a specification and anSTYPE. For example, for spec /A3B the STYPE for a Gasket is G so if the assemblycomponent has a different STYPE then the rules will be evaluated to find the STYPE for thecurrent SPEC. If no rule is present then the assembly instance will fail. To make theassembly work in this instance a new rule could be added so that a gasket in spec /A3Balways looks for STYPE G.

This is done as follows:

First navigate to a gasket which needs the rule. Next select the Stype line in theComponent Rules panel and click the New button. The Pipe Assembly Rules formdisplays configured for STYPE rules.

1) Selection - SEL WITH STYP RF

2) Positioning - DIST 200 FROM PREV

3) Orientation - ORI Y IS N WRT PREV

4) Bore Selection - Use PL of PREV ELBO



To set the rule, enter the following two parts:• The Specification where the STYPE rule applies• The actual STYPE

By checking the Apply to Similar Items box, the rule is applied to all similar items in theassembly.

An alternative STYPE rule mechanism is to force the assembly to use a particularspecification and stype regardless of the pipe specification where the assembly is beingbuilt. For example certain instrument items may only exist in an Instrument specification sothe system needs to be forced to look in a specific place rather than try to find an equivalent.

To make this work, the Force this SPEC./STYPE checkbox is checked.

After clicking the OK button, a new rule is built and shown in the Component Rules list. Toedit or delete this, select it and then click the appropriate button.



12.3.7 Position RulesPosition and Orientation rules are essentially a replacement of the default action in the formof a command line. In practice a position rule may be a through command such as THROPT or Dist 1000. These lines will be executed as complete positioning commands in place ofthe default position derived from the relative position in the assembly.

12.3.8 Orientation RulesOrientation rules can be in two forms, first as a single command in place of the defaultorientation, or as a trigger to prompt the user for orientation.

The command could be for example "ORI and P3 is D" for a tee in a Drain to always force itto point down. Otherwise, you could enter the keyword 'PROMPT' to force the system to askfor the appropriate orientation when the assembly is being built.

In the example shown, the selected Valve will always trigger a prompt to ask for the handwheel orientation.



12.3.9 Bore Selection RulesIn the assembly shown above, there are five points where the bore changes. When thisassembly is being built in the design, you will be prompted 5 times to select the appropriatecomponent bore. Whilst at least one size will need to be entered, other sizes can be derived.For example the reducers either side of the control valve will be the same size but withreversed flow. To reduce the amount of selection which you need to do, bore selection rulescan be put in place to use other components as a reference.

In the example, the leave point of a component is being set to have the same bore size asthe arrive point of the previous reducer. This means that when the component is selected,



the system will look at the previous reducer to obtain the leave bore rather than prompting orinstigating a choose operation. The rule is shown in the Component Rules list:

Note: For a tee the bore selection is applied to P3.

12.4 Key ElementsAssemblies such as Control sets are often built around a single elbow in the design as alocating item but with our previous example this is in the middle of the assembly and cannotbe used as a positioning item. The concept of a Key element is provided to allow an existingelement in the design to directly replace an element in an assembly such that the assemblyis built around the existing design element as if it was part of the assembly. In effect a designcomponent is used as a positioning and orientation component for the rest of the assembly.



Because there can only be one Key element, this is set by a right mouse click on theassembly design Explorer window. To set the Key element, navigate to the required elementand select the right-click option to set this as the Key element.

The 3D window displays which element has been selected.


Pipework Design User GuideConclusion

13 Conclusion

This concludes both the tutorial exercises and this introduction to some of the ways in whichAVEVA PDMS applications can help you in your piping design work. You should now havean insight into the potential power of AVEVA PDMS and sufficient confidence to exploresome of the more advanced options on your own.

For further technical details, refer to the sources of information listed in Other RelevantDocumentation.

If you have not already done so, you are strongly advised to attend one or more of thespecialised AVEVA PDMS training courses, which will show you how to get the maximumbenefits from the product in your own working environment (see Further Training in UsingPDMS).


Pipework Design User GuideConclusion


Pipework Design User GuideThe Equipment and Piping DESIGN Database

A The Equipment and Piping DESIGN Database

This appendix shows the part of the PDMS DESIGN database hierarchy which holdselements relevant to equipment and piping design. (Elements shown in italics, BOX forexample, are Equipment items).

ZONE

PIPE EQUIPMEN T *

ROUTING PLANE GROUP

ROUTING PLANEBRANCH

(EQUI)(P IPE)

(RPLG)

(RPLA)(BRAN)optional S UBEQUIPMEN T

(S UBE)

N OZZLE LOAD POIN Tprim itives

designcomponents

piping

BOX

CYLIN DER

PY R AMID

DIS H

CON E

S N OUT

CIR CULAR T OR US

R ECTAN GULAR TOR USS LOPE-BOT T OMED CY LIN DER

POLYHEDR ONELBOW (ELBO)

BEND (BEND)

TEE (TEE)

VALVE (VALV)

REDUCER (REDU)

FLANGE (FLAN)

VENT (VENT)

OLET (OLET)

CAP (CAP)BLIND FLANGE (FBLI)

STANDARD HOOK-UP (SHU)

FIXED LENGTH TUBE (FTUB)

LAP-J OINT STUB END (LJ SE)

THREE-WAY VALVE (VTWA)

FOUR-WAY VALVE (VFWA)

GENERAL PIPE COMPONENT (PCOM)

FILTER (FILT)

COUPLING (COUP)CLOSURE (CLOS)

GASKET (GASK)

DUCTING (DUCT)

WELD (WELD)

UNION (UNIO)TRAP (TRAP)

ATTACHMENT POINT (ATTA)

CROSS (CROS)

INSTRUMENT (INST)

(All prim itive shapes have anegative equ ivalen t thatm ay be owned by a positiveelem ent.

(N OZZ) (LOAP)

12.0 A:1© 2007 AVEVA Solutions Ltd

Pipework Design User GuideSPOOLER Reference Information

B SPOOLER Reference Information

This appendix provides additional information on some important aspects of the SPOOLERmodule. This information is intended for experienced users and system administrators, toenable them to modify existing databases and catalogues making them compatible withSPOOLER.

B.1 Spool BreaksA Spool Break is the changeover point between SHOP and FIELD components. It occurs atthe junction of two piping components (or implied TUBE) that fulfils one of the followingcases:

1. The Shop Flag status of the two components is different. i.e. True-to-False or False-to-True. The Shop Flag status of elements in the DESIGN database can be changed inSPOOLER using the Modify>Shop/Field function.

2. If a component is the end of the piping network (e.g. connected to an EQUIpment item)it is automatically the end of the Spool/Field and the Spool Drawing.

3. BOTH piping components have their spool break attributes set to true (CSFBREAK fora piping component and TSFBREAK for the leave tube). This condition can be forcedusing the Create>Spool Break function in SPOOLER.

Note: TSFBREAK is an attribute of the piping component not the leave tube. Although itseffect is on the leave tube.

B.2 Connection TypesThe p-points of every piping component have associated connection types, derived fromtheir catalogue definitions. These are used in conjunction with the Connection Compatibility(COCO) tables, in the database, to check if two components may be legally connected toeach other.

Note: The connection type for the arrive and leave points of a TUBI component are alwaysderived from p-point P1 of the tube catalogue element.

This functionality has been extended for SPOOLER so that it also specifies what type ofconnection it is. The type of connection is identified by the Ckey attribute, which is added to

12.0 B:1© 2007 AVEVA Solutions Ltd


the COCO element definition. The Ckey attribute can be set to any of the standardISODRAFT end connection types:

If the Ckey attribute is left unset, the connection is assumed to be ‘Plain’.

B.2.1 Weld and Joint ConnectionsConnections between piping components (and tube) come in two forms: welds and non-welded joints (e.g. flanged, screwed or compression connections). The welds and joints aregrouped in the fabrication database in the WLDGRP (Weld Group) and JNTGRP (JointGroup) elements, respectively. These groups are created, by default, when numbering isfirst inserted into the Spool Drawing.

A connection is considered to belong to a Spool Drawing if:• Both piping components involved in the connection belong to that Spool Drawing.• The downstream piping component in the connection is on one end of the piping

network in that Spool Drawing.• In the case of a flanged joint with a gasket, the flange owning the gasket is on that

Spool Drawing.

B.2.2 Types of Welds and JointsSPOOLER uses three types of weld definitions and one type of joint definition. These are:

The types of welds and joints are described in the following sections.

• Implied WeldsIWELD components provide a link in the Fabrication database to the position of a weld thatmust be inserted to join two piping components or tubes. For example: fit a flange onto theend of a tube. You do not have to explicitly define these welds as they are implied by thenature of the components involved.

A connection can have an IWELD element associated with it if:

Ckey Connection Type

BW Butt weld

SW Socket weld

SC Screwed connection

CP Compression

FL Flanged

PL Plain

Definition Description

IWELD Implied weld

RWELD Real weld

AWELD Attached weld

IJOINT Implied joint



• It has a Ckey (Connection key) of types BW or SW.

Note: If you have explicitly defined a weld (RWELD element) to connect the twocomponents, the software will not insert a implied weld at that point.

• Real WeldsRWELD components link to explicitly defined Shop or Field welds in the DESIGN database.They are normally inserted in AVEVA PDMS DESIGN but can also be added in SPOOLER,to break up a spool.

• Attached WeldsAWELD components provide a method for numbering the welds required for weldedattachments. Typically these are used to secure the piping network to the supportATTAchments. The number of welds on each attachment can be defined in SPOOLER,using the Modify>Attached Welds function.

• Implied JointsIJOINT components define the connection between two non-welded piping components ortubes (e.g. bolted flanges, compression joints or screwed connections). You do not have toexplicitly define the details of these joints as they are implied by the nature of thecomponents involved.

A connection can have an IJOINT element associated with it if:• It has a Ckey (Connection key) of types CP, FL or SC.• Neither of the components are Gaskets.

B.3 Special CasesThe following sub-sections contain descriptions of some special cases within SPOOLER.

B.3.1 Shop Flag StatusThis section describes some of the special cases for the Shop Flag. These can effect theplacement of Spool Breaks and the handling of some elements.

• ATTAchmentsWhile ATTAs do have a Shop Flag, its status is ignored when spooling a piping network. Forexample: a shop false ATTA will not break a spool.

Note: The leave tube of a spec break ATTA (SPECBR attribute is True) still has an activeShop Flag.

B.3.2 Leave Tubes of WeldsIf you break a spool by inserting a field weld into the leave tube after the last component in apipe, the section between the weld and the end of the tube is reassigned as the leave tubeof the weld. Inserting a field weld is a modification to the DESIGN database and immediatelyafter its creation the weld and its leave tube are not in the Spool Drawing.

You can add the weld and its leave tube by updating the numbering of the Spool Drawing, inthe normal way.



B.3.3 Welds for OLETsAn OLET element has 3 p-points: P1 (p-arrive) and P2 (p-leave) in the main tube and P3 inthe off-line leg. P1 and P2 are coincident and are normally treated as a single point.

A problem could occur if points P1 and P2 have Ckeys of BWD or SWD. By default thisshould give two welds, one for each point, but the software recognises the OLET as aspecial case and only allocates one weld.


Pipework Design User GuidePipe Piece and Pipe Spool Data

C Pipe Piece and Pipe Spool Data

This Appendix contains the detailed system-specific information about pipe pieces and pipespools. It includes the underlying objects and functionality and the database attributes andpseudo-attributes.

C.1 Pipe Piece Manager

C.1.1 PML MethodsThe pipe-piece manager has no exposed functions.

C.1.2 Functionality

C.2 Pipe Piece

C.2.1 Pipe-Piece Functionality

Function Description

Delete pipe pieces


Invalidate all verified Set appropriate validation attributes

Query bend activities Returns bending activities

12.0 C:1© 2007 AVEVA Solutions Ltd


C.2.2 Pipe-Piece Attributes

Attribute Type Default Get Set Remarks

User Spool

Mngr

Pipe

Mngr

Fab.

Mngr

Bend

M/C

Weld

M/C

Stock

Len.

Machine Bent BOOLEAN False May not berequired

BendingMachineReference

DBREF

Bending withflow

BOOLEAN True

Auto WeldedStart

ENUM

Auto WeldedEnd

ENUM

WeldingMachineReference

DBREF

User StartExcess

REAL 0

The system should always remember user excesses. Start/End excesses are used only where the relevantstart/end flanges are manually welded. The cut length calculation should always user the greater value ofthe user or bend machine excess.

Bend M/C StartExcess

REAL 0

User EndExcess

REAL 0

Bend M/C EndExcess

REAL 0

Feed Excess REALARRAY

Stock LengthValue

REAL 0 Holds thestocklength thatwascheckedagainst

Pipe pieceverified

BOOLEAN False Invisible touser

Pipe piecemodified

BOOLEAN True Invisible touser

Pipe piececontains bends

BOOLEAN False Invisible touser



C.2.3 Pipe-Piece Pseudo Attributes

Attribute Comment Attribute Name

Arrive position HPOS on branch or LPOS of first component APOS

Leave position TPOS on branch or APOS of last component LPOS

Arrive direction HDIR on branch or LDIR of first component ADIR

Leave direction TDIR on branch or ADIR of last component LDIR

Arrive connectiontype

LCON of start component ACON

Leave connectiontype

ACON of end component LCON

Arrive component The first component of the Pipe Piece PPAREF

Leavecomponent

The Last Component of the Pipe Piece PPLREF

Arrive flange reqwelding

Returns whether the start flange should beconsidered for pre-welding, i.e. shop = true andloose = false

Leave flange reqwelding

Returns whether the end flange should beconsidered for pre-welding, i.e. shop = true andloose = false

Nominal bore HBOR on branch or LBOR of start component PPNBOR

Outside diameter HOD on branch or LOD of start component PPOUTD

Material Returns the MATR attribute of the spec of the firstcomponent

MATREF

Specification HSTU on branch or LSTU of first component SPRE

Wall thickness The wall thickness of the implied tube of the pipepiece. Uses the OUTD and ACBO attributes fromthe property database.

WALLTH

Cut length Calculated using relevant information PPCUTL

Finished length MTCL PPFINL

Bend radii Array of radius of bends for pipe piece PPBRAD

Bend ratio Array of Ratio of radius to OD of bends for pipepiece Ratio of radius to OD

PPBRAT

Angle betweenflanges

The required angle between flanges at pipe pieceends before the pipe piece is bent.

PPANFL

Get pipe piececomponents

Returns all the components within the pipe piece PPAREF



C.3 Pipe Spool Manager

C.3.1 PML Methods

C.3.2 Functionality

C.4 Pipe Spool

C.4.1 Pipe Spool Functionality

Fabricationmachine verified

True/False - verifies if modified flag is true PPFMCV

Stock lengthverified

True/False - verifies if modified flag is true PPSTOV

Attribute Comment Attribute Name

Name Result Description

.generatePipeSpools(DBREF)

.getPipePieces(DBREF) ARRAY

.getBranchElements(DBREF) ARRAY Returns all the pipe elementscontained in the spool. This includestubes.

.getMTOElements(DBREF) ARRAY Returns the pipe pieces and othercomponents need in

.getBendingTables(DBREF) ARRAY

.getWeldingTables(DBREF) ARRAY

.getActivityTables(DBREF) ARRAY


Autonaming


MTO

Fabrication activities

Bending information



C.4.2 Pipe Spool Members

C.4.3 Pipe Spool Methods (not implemented)

Welding information

End points 2D array of start and end points of the segments of a pipe spool


Name Type Description

.pipeSpool DBREF Pipe Spool element

Name Type Description

.getMtoTables(DB_Element)

ARRAY of Pass an array of attributes.

Results in a table / 2 dimensional array:

Rows = all elements in the pipe spool.

Columns = Attribute values requested.

.getAssemblyTables() ARRAY Results in a table / 2 dimensional array:

Table of information to put on the pipe sketchAssembly Activities Table

.getEndpointTable() ARRAY Results in a table / 2 dimensional array:

Connection number and X, Y and Z positionsfor the open ends of the pipe spool

.getEndPointTags() ARRAY Results in a table / 2 dimensional array:

PPoint/Element and text to allow this text to betagged on the pipe sketch.

The tags correspond to the.EndPointTable() for cross-reference

.getPlaneTags() ARRAY Results in a table / 2 dimensional array: PPoint/Element and text to allow this text to be taggedon the pipe sketch.

The tags correspond to the Planes referencedon the .getAssembly() table for cross-reference



s

f the

f thements

C.4.4 Pipe Spool Attributes

C.4.5 Pipe Spool Pseudo Attributes

C.5 Pipe Spool Reporting Data

C.5.1 MTOThis is a query that returns the components and pipe pieces for a pipe spool. The defaultorder of the list is in hierarchical sequence order.

C.5.2 Assembly ActivitiesArray of activities for each of the components in the pipe spool

Flanges

Activity object definition for orienting a flange component.

Attribute Type Default Get Set Remark

User Spool

Mngr

Pipe

Mngr

Fab.

Mngr

Bend

M/C

Weld

M/C

Stock

Len.

Name name UNSET

PSARFA ArrayDB_Element

UNSET Array oarriveelements

PSLRFA ArrayDB_Element

UNSET Array oleave ele

Attribute Comment

PPRFA List of pipe pieces within the spool, will NOT generate pipe pieces

BELRFA List of piping elements within the spool

BELTYP List of piping elements types within the spool

MELRFA List of MTO components needed to construct the pipe spool

PSVLD If all the pipe pieces are valid this is true.



Branch Pieces

Activity object definition for defining branch connection, tee, olet, etc. to another branch.

Elbow

Activity object definition for defining elbow component.

Attribute Type Description

Component DBREF Component activity relates to

Offset Angle REAL Offset angle of flange from reference plane(Rotation)

Reference PlaneComponent

DBREF Component used to define reference plane

Plane Direction DIRECTION Direction of the plane acting through the referencecomponent



Offset Angle REAL Offset angle of connection from reference plane(Turn)

Rotation Angle REAL Only relevant for straight branch pieces ending ina flanged connection

The reference plane for the flange rotation isdefined by the branch piece and the main pipe.

Inclination Angle REAL The inclination is the angle between the branchpiece and the main pipe measured in thedirection towards the reference component

BranchConnection

ENUM Type of connection of branch piece to main pipe



Plane Direction DIRECTION Direction of the plane acting through thereference component



Offset Angle REAL Offset angle with respect to reference plane(Turn)



Mitre (Single Cut)

Activity object definition for defining elbow component.

Cut

Activity object definition for defining cut at start/end of a pipe piece.

Split

Activity object definition for defining split in a pipe piece.






Offset Angle REAL Offset angle with respect to reference plane(Turn)

Cut Angle REAL Angle pipe is cut (Inclination)





Component DBREF Pipe piece activity relates to

End ENUM End cut is related to (Inclination)

Final Length REAL Final cut length from reference component

ReferenceComponent

DBREF Reference component final cut is measured from






Thread

Activity object definition for defining threading at start/end of a pipe piece.

Insert

Activity object definition for defining inserts at the end of a pipe piece.

C.5.3 Bending Table

Feed Excess REAL Excess removed from feed tube following referencecomponent

ReferenceComponent

DBREF Reference component preceding feed excess isremoved from



End ENUM End threading is related to (Inclination)

Thread Length REAL Length of threading required

Thread ? Threading information



Insert Length REAL Length of insertion into following pipe piece



Pipe Piece DBREF Pipe piece bending table relates to

Bending Machine DBREF Bending machine reference

Clutch arrive tube BOOLEAN True if the bending machine clutches the arrivetube

Check Sum ? NOT IMPLEMENTED

Activities Bend ActivityArray

Array with bending activities for the pipe piece



Bending Activity

C.5.4 Welding TableManaged by attributes and pseudo attributes of pipe piece.

C.5.5 Spool Extents/End PointInformation derived from Pipe Spool to determine the positions at the start and end of thefirst branch/section of branch of a spool:

Start equates to APOS of PSSRFA[1]

End equates to LPOS of PSERFA[1]


Feed REAL Feed activity value

Rotate REAL Rotation activity value

Bend REAL Bend activity value


Pipe Piece DBREF Pipe piece welding table relates to

Welding Machine DBREF Welding machine reference

Arrive Flange DBREF Flange at arrive of pipe piece

Arrive FlangeWelded

Boolean True if welding machine set, arrive flange can bewelded and arrive flange is pre-welded

Leave Flange DBREF Flange at leave of pipe piece

Leave FlangeWelded

Boolean True if welding machine set, leave flange can bewelded and leave flange is pre-welded

Angle Real Angle between the arrive flange and leave flangewhere both pre-welded


Pipework Design User GuideFabrication Machine Data

D Fabrication Machine Data

The system can check pipe pieces for production readiness against bending machines,welding machines and the defined stock length of tubing.

Production test requests are made to a Fabrication Machine Manager controlling thefabrication machines. Information about the welding/bending machine operation and theircorresponding activity tables can be obtained from the Manager.

D.1 Fabrication Machine Manager

D.1.1 Methods

Name Result Purpose

SetMaximumMaterialLength(REAL length)

NO RESULT Sets the maximum materiallength.

GetMaximumMaterialLength( ) REAL Gets the maximum materiallength.

SetBendingMachine(DBREF bendingMachine)

NO RESULT Sets the current bendingmachine. Future fabricationtests will use this bendingmachine.

GetBendingMachine( ) DBREF Gets the current bendingmachine.

SetWeldingMachine(DBREF weldingMachine)

NO RESULT Sets the current weldingmachine. Future fabricationtests will use this weldingmachine.

GetWeldingMachine( ) DBREF Gets the current weldingmachine.

12.0 D:1© 2007 AVEVA Solutions Ltd


ValidatePipePiece(DBREF pipePiece)

BOOLEAN Checks if the given pipe piececan be fabricated by thecurrent combination of bending/ welding machines.Information about fabricationfor the bending/weldingmachine can be obtained byrequesting the correspondingbending/welding result objects.

SetAddExcessBetweenBends(BOOLEAN add)

NO RESULT Tells the fabrication machinemanager if excesses betweenbends can be added to thepipe piece in order to satisfybending machine fabricationrequirements.

GetAddExcessBetweenBends( ) BOOLEAN Gets the current add excessbetween bends setting.

SetAddEndExcess(BOOLEAN add)

NO RESULT Tells the fabrication machinemanager if excesses at theends of the pipe piece can beadded in order to satisfybending machine fabricationrequirements.

GetAddEndExcess( ) BOOLEAN Gets the current add endexcess setting.

SetChangeFlangeToManual(BOOLEAN change)

NO RESULT Tells the fabrication machinemanager if flanges at the endof the pipe piece can bechanged to manually welded inorder to be able to fabricate thepipe piece.

GetChangeFlangeToManual( ) BOOLEAN Gets the current change flangeto manual setting.

SetCheckStockLength(BOOLEAN check)

NO RESULT Tells the fabrication machinemanager if the current stocklength must be checked duringfabrication.

GetCheckStockLength( ) BOOLEAN Gets the current check stocklength setting.

SetFirstFeedNegative (BOOLEAN firstNegative)

NO RESULT The first feed in the bendingmachine will be negative (thepipe is inserted into thebending machine)

Name Result Purpose



GetFirstFeedNegative ( ) BOOLEAN Gets the FirstFeedNegativesetting of the fabricationmachine manager.

GetBendingMachineResult( ) BENDINGMACHINERESULT

Gets aBendingMachineResultobject with information aboutthe bending machine for thelast fabrication test.

GetWeldingMachineResult( ) WELDINGMACHINERESULT

Gets aWeldingMachineResultobject with information aboutthe welding machine for thelast fabrication test.

SetClutchEndPriority(STRING priority)

NO RESULT Informs the fabricationmachine manager about whichend should be inserted in thebending machine clutch.Priority can take the followingvalues:

‘FLANGED’

‘NONFLANGED’

‘NOPREFERENCE’

GetClutchEndPriority( ) STRING

‘FLANGED’,‘NONFLANGED’,‘NOPREFERENCE’

Gets the current clutch endpriority.

SetMaterialStretchConfig(STRING config)

NO RESULT Sets the stretching parametersof the bending machine for thefollowing fabrication tests.Config can take the values :

‘SYSTEMDEFAULT’

‘MACHINE’

‘MATERIAL’

‘NOSTRETCH’

GetMaterialStretchConfig( ) STRING

“SYSTEMDEFAULT”,“MACHINE”,“MATERIAL”,“NOSTRETCH”

Gets the current materialstretch configuration.

Name Result Purpose



D.1.2 BendingMachineResult

BendingMachineAcceptsPipePiece(DBREF pipePiece)

BOOLEAN Quick check to establish if thecurrent bending machineaccepts the given pipe piece.

WeldingMachineAcceptsPipePiece(DBREF pipePiece)

BOOLEAN Quick check to establish if thecurrent welding machineaccepts the given pipe piece.

Name Result Purpose

Name Result Purpose

BendingMachine( ) DBREF Bending machine used

PipePiece( ) DBREF Pipe piece being checked

Pass( ) BOOLEAN Whether pipe piece haspassed bending machinechecks

ValidMaterial( ) BOOLEAN The Bending Machine can dealwith the pipe piece material.

ValidOD( ) BOOLEAN The Bending Machine can dealwith the pipe piece OD.

ValidWallThickness( ) BOOLEAN The Bending Machine can dealwith the pipe piece wallthickness.

ValidInitialFeedLength( ) BOOLEAN First leg doesn’t excess theinitial feed of the bendingmachine

ValidBendRadius( ) BOOLEAN The Bending Machine can dealwith the bend radius of the pipepiece.

AllBendsSameRadius( ) BOOLEAN All the bends in the pipe piecehave the same radius.

WithinCollisionPlanes( ) BOOLEAN The pipe piece does not collidewith the Bending Machinecollision planes.

FailureIsResolvable( ) BOOLEAN Modifications to pipe piecedefinition is required to passthe bending machine checks

PipePieceStartExcess( ) REAL Start excess required.

PipePieceEndExcess( ) REAL End excess required.

PipePieceFeedExcess( ) REALARRAY

Array of feed excessesrequired.



D.1.3 WeldingMachineResult

PipePieceStart FlangeManuallyWelded( )

BOOLEAN Start flange required to bemanually welded.

PipePieceEndFlangeManuallyWelded( )

BOOLEAN End flange required to bemanually welded.

PipePieceCutLength( ) REAL Length of material beforefabrication.

PipePieceFinishedLength( ) REAL As above, but with excessesremoved.

EndsExcessPassed( ) BOOLEAN Check against preference forchange in state.

FeedExcessPassed( ) BOOLEAN Check against preference forchange in state.

FlangeModifiedPassed( ) BOOLEAN Check against preference forchange in state.

BendingDirectionForward( ) BOOLEAN Bend in direction of flow.

Name Result Purpose

Name Result Purpose

Welding machine( ) DBREF Welding machine used

PipePiece( ) DBREF Pipe piece being checked

Pass( ) BOOLEAN Whether pipe piece haspassed welding machinechecks

ValidMaterial( ) BOOLEAN The Welding Machine can dealwith the pipe piece material.

ValidOD( ) BOOLEAN The Welding Machine can dealwith the pipe piece OD.

ValidMinimumLength( ) BOOLEAN The length of the pipe piece isgreater than the minimumlength of the welding machine.

ValidMaximumLength( ) BOOLEAN The length of the pipe piece issmaller than the maximumlength of the welding machine.

ValidStartFlangeGroup( ) BOOLEAN The flange at the start of thepipe piece is accepted by thewelding machine.



D.1.4 BendingTable

D.1.5 BendActivity

D.1.6 WeldingTable

ValidEndFlangeGroup( ) BOOLEAN The flange at the end of thepipe piece is accepted by thewelding machine.

MaxWeldedFlanges( ) REAL Maximum number of weldedflanges the can be handled bywelding machine

Name Result Purpose

PipePiece( ) DBREF Pipe piece bending tablerelates to

BendingMachine( ) DBREF Bending machine reference

ClutchArriveTube( ) BOOLEAN True if the bending machineclutches the arrive tube

CheckSum( ) ? NOT IMPLEMENTED

Activities( ) BENDACTIVITY ARRAY

Array with bending activities forthe pipe piece

Name Result Purpose

Feed( ) REAL Feed activity value

Rotate( ) REAL Rotation activity value

Bend( ) REAL Bend activity value

Name Result Purpose

PipePiece( ) DBREF Pipe piece welding tablerelates to

WeldingMachine( ) DBREF Welding machine reference

ArriveFlange( ) DBREF Flange at arrive of pipe piece

ArriveFlangeWelded( ) BOOLEAN True if welding machine set,arrive flange can be weldedand arrive flange is pre-welded



D.2 Database SupportThe database ddl supports the following new objects to support fabrication machines.

D.2.1 FMWL - Fabrication Machine World Top Level Element

D.2.2 FMGRP - Fabrication Machine Group

D.2.3 FMBEND - Fabrication Machine - Bending

LeaveFlange( ) DBREF Flange at leave of pipe piece

LeaveFlangeWelded( ) BOOLEAN True if welding machine set,leave flange can be weldedand leave flange is pre-welded

Angle( ) REAL Angle between the arriveflange and leave flange whereboth pre-welded

Name Result Purpose

Attribute Description Type Default

NAME Name name unset

DESC Description text unset



PURP Purpose text unset


FUNC Function text unset



STFP Constant Stretch Factor real 1.0

STFC Proportional Stretch Factor real 0.0

MAXLP Maximum Length of Pipe real 6000.0



D.2.4 FMBPLN - Fabrication Machine - Bending - Plane

D.2.5 FMBDIM - Fabrication Machine - Bending - Dimension

D.2.6 FMBSST - Fabrication Machine - Bending - Springback/Stretch Factor



MINPLN Plane Minimum Point real[3] {0.0, 0.0, 0.0}

MAXPLN Plane Maximum Point real[3] {0.0, 0.0, 0.0}



OD Outside Diameter real 0.0

WTHICK Wall Thickness real 0.0

GRIP Grip Measure real 0.0

MLEF Minimum Length ExcludingFlanges

real 0.0

MLIF Minimum Length IncludingFlanges

real 0.0

FCMEAS Flange Correction Measure real 0.0

BRAD Bend Radius real 3.0



OD Outside Diameter real 0.0

WTHICK Wall Thickness real 0.0

MATREF Material reference real 0.0

ANGSPA Angle At 20 Degrees real 20.0

ANGSPB Angle At 120 Degrees real 120.0

STFP Constant Stretch Factor real 1.0

STFC Proportional Stretch Factor real 0.0



D.2.7 FMWELD - Fabrication Machine - Welding

D.2.8 FMWSK - Fabrication Machine Welding - SKEY

D.3 Automatic Flange AlignmentThis development allows piping components to be connected so that by default their Zdirections are aligned. This is particularly useful for ducting and other BOXI piping.

The functionality comprises the following:• An attribute on the different ppoint elements in the catalogue.• A set of pseudo attributes to allow it to be queried in the design.• An enhanced connect command to take account if set.• Datacon check.

D.3.1 New Attribute for PTCA, PTAX, PTMI, PTPOS

D.3.2 New Pseudo Attributes for Branch MembersAll these pseudo attributes are valid for Branch members.



MINOD Minimum Outside Diameter real 0.0

MAXOD Maximum Outside Diameter real 0.0

MINLP Minimum Length of Pipe real 0.0

MAXLP Maximum Length of Pipe real 6000.0




SKEY Flange group skey text unset


PZAXI Z direction Direction

unset



D.3.3 Connection CommandThe command syntax is unchanged.

However, it now uses valid alignment directions in place of a default orientation. It checksthat a PZAXI is set for the relevant ppoint of the current element and for the ppoint it isconnecting to.

If the element being connected to is a gasket or a weld and does not have a set PZAXI thenthe ppoint of the next element is used instead. If there is either one or two unset alignmentdirections then the connection command functions exactly as before.

Also if an orientation is specified as well such as CONNECT AND P3 IS UP then thisoverrides the alignment direction.

D.3.4 New Datacon Warning MessagesThe following warnings are now generated. They are not output if the branch is badlyrouted.

D850 BAD ARRIVE ALIGNMENT GEOMETRY, ANGLE IS 15D850 BAD LEAVE ALIGNMENT GEOMETRY, ANGLE IS 45

Attribute Comment

PZDIR Alignment direction for specified ppoint.

AZDIR Alignment direction for arrive ppoint

LZDIR Alignment direction for leave ppoint..

PQAANG Angle between alignment direction for specified ppoint and adjacentcomponent.

AQAANG Angle between alignment direction for arrive ppoint and previouscomponent.

LQAANG Angle between alignment direction for leave ppoint and nextcomponent.


Pipework Design User GuideOther Relevant Documentation

E Other Relevant Documentation

This guide is intended only as an introduction to those parts of AVEVA PDMS most relevantto Pipework design. As such, it describes only the main concepts needed to get you started.Should you need more detailed information about any topic, the following documents areavailable.

E.1 PDMS Introductory GuidesThe following guides introduce the principal AVEVA PDMS facilities to new users (thisPipework guide forms part of the set):

• Introduction to Common FunctionalityIntroduces PDMS and related products

• HVAC Design User Guide• Accommodation User Guide• Structural Design Using PDMS User Guide• Pipework Support Design User Guide• Introduction to Templates• ISODRAFT User Guide• Drawing Production User Guide

Introduces the range of facilities available in the DRAFT module.• Reporting

Introduces the database reporting utility available from within most AVEVA PDMSapplications, including the use of expressions to select relevant data.

• Graphical Model Manipulation GuideIntroduces the DESIGN Model Editor, which enables you to position and orientateselected Plant items using the mouse pointer.

E.2 AVEVA PDMS Reference ManualsThe full PDMS documentation set includes a number of reference manuals which givedetailed explanations of all the technical concepts involved. These manuals also describethe underlying command syntax which can be used to control AVEVA PDMS directly (thusbypassing the forms and menus interface).

Those particularly relevant to Pipework design include:• DESIGN Reference Manual

Covers concepts and commands for all design disciplines.

12.0 E:1© 2007 AVEVA Solutions Ltd

Pipework Design User GuideOther Relevant Documentation

• ISODRAFT Reference ManualExplains how to create customised piping isometric plots.

• DRAFT Reference ManualExplains the commands for the PDMS 2D drafting facilities.

• Catalogues and Specifications Reference ManualExplains how to set up a PDMS Catalogue and create tabulated specifications.

E.3 General GuidesThe following guides are intended for use only by experienced PDMS users who want towrite their own applications:

• Software Customisation GuideExplains how to write your own application macros using PML (AVEVA’sProgrammable Macro Language) and how to design your own forms and menusinterface.

• Software Customisation Reference ManualSupplements the Customisation Guide. Includes a list of PML 2 Objects, Membersand Methods. For forms and Menus objects, the command syntax relating to theobjects is included.

12.0 E:2© 2007 AVEVA Solutions Ltd

Pipework Design User GuideSample Plots

F Sample Plots

This appendix comprises some examples of typical (though relatively simple) plots showingthe sorts of piping design outputs that can be created using with the AVEVA PDMS pipeworkapplication.

12.0 F:1© 2007 AVEVA Solutions Ltd

Index


Numerics0 . . . . . . . . . . . . . . . . . . . . . . . 11:10, 11:123D Graphics . . . . . . . . . . . . . . . . . . . . . . 9:13D View . . . . . . . . . . . . . . . . . . . . . . 4:9, 9:5

AAdd . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:17Add CE with colour . . . . . . . . . . . . . . . . . 9:7Add to spool drawing . . . . . . . . . . . . . . 9:17Adjacent field components . . . . . . . . . . 9:18Administrative elements:creation . . 3:4, 9:4Aligning components . . . . . . . . . . . . . . . 5:30Always generate new data . . . . . . . . . . 9:21Application:definition . . . . . . . . . . . . . . . . 2:1Application:Equipment . . . . . . . . . . . . . . 4:3Application:Pipework . . . . . . . . . . . . . . . . 5:3Applying rules . . . . . . . . . . . . . . . . . . . . 8:33Assemblies:creation . . . . . . . . . . . . . . . 12:1Assembly build origin . . . . . . . . . . . . . . 6:20Assembly hierarchy . . . . . . . . . . . . . . . . 12:5Attached welds . . . . . . . . . . . . . . . . . . . . B:3Attribute:definition . . . . . . . . . . . . . . . . . . 3:2Attributes, routing . . . . . . . . . . . . . . . . . 8:99Autocolour . . . . . . . . . . . . . . . . . . . . . . . . 9:7Automatic flange alignment . . . . . 10:23, D:9Automatic pipe routing . . . . . . . . . . . . . . 8:1Automatic pipe routing:administration . . 8:59Auto-naming preferences

defining . . . . . . . . . . . . . . . . . . . . . 10:11Auto-resolve preferences:defining . . . 10:11AWELD . . . . . . . . . . . . . . . . . . . . . . . . . . B:3

BBacking sheet . . . . . . . . . . . . . . . . . . . 11:10Behind item . . . . . . . . . . . . . . . . . . . . . 9:15Bend numbers . . . . . . . . . . . . . . . . . . . 9:18Bores:nearly equal . . . . . . . . . . . . . . . . . 8:5Bores:selection rules . . . . . . . . . . . . . 12:18Branch components . . . . . . . . . . . . . . . 8:19Branch constraints . . . . . . . . . . . . . . . . 8:19Branch details . . . . . . . . . . . . . . . . . . . 8:19Branch head . . . . . . . . . . . . . . . . . . . . . . 5:2Branch head:connecting . . . . . . . . . . . 8:13Branch head:definition . . . . . . . . . . . . . . 3:1Branch rules:Querying . . . . . . . . . . . . . 8:36Branch tail . . . . . . . . . . . . . . . . . . . . . . . 5:2Branch tail:connecting . . . . . . . . . . . . . 8:13Branch tail:definition . . . . . . . . . . . . . . . . 3:1Branch:definition . . . . . . . . . . . . . . . 3:1, 9:3

CCardinal direction handles . . . . . . 5:44, 5:54Catalogue database . . . . . . . . . . . . . . . . 5:1CE . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2, 9:5CE limits button . . . . . . . . . . . . . . . . . . . 9:7Choose form . . . . . . . . . . . . . . . . . . . . . 9:14Ckey attribute . . . . . . . . . . . . . . . . . . . . . B:1Clash checking:checking process . . . . . 7:5Clash checking:clash limits . . . . . . . . . . 7:5Clash checking:extent of clash . . . . . . . . 7:4Clash checking:obstruction levels . . . . . 7:4Clash checking:obstruction list . . . . . . . . 7:5Clash checking:principles . . . . . . . . . . . . 7:4Clash limits . . . . . . . . . . . . . . . . . . . . . . . 7:5Clash:definition . . . . . . . . . . . . . . . . . . . . 7:4

12.0© 2007 AVEVA Solutions Ltd Index page i


Clashing extent . . . . . . . . . . . . . . . . . . . . 7:4Clearance:definition . . . . . . . . . . . . . . . . 7:4Colour selection . . . . . . . . . . . . . . . . . . . 9:7Colours . . . . . . . . . . . . . . . . . . . . . . . . . . 9:7Command syntax . . . . . . . . . . . . . . . . . 8:92Component positioning . . . . . . . . . . . . . 8:27Component:aligning . . . . . . . . . . . . . . . 5:30Component:choosing . . . . . . . . . . . . . . . 6:6Component:creating . . . . . . . . . . . . . . . 5:12Component:modifying bore . . . . . . . . . . . 6:8Component:modifying specification . . . . 6:5Component:picking . . . . . . . . . . . . . . . . 6:23Component:selection . . . . . . . . . . . . . . . 6:3Component:setting attributes . . . . . . . . 8:87Conceptual pipe rack . . . . . . . . . . . . . . 8:53Connection types . . . . . . . . . . . . . . . . . . B:1Continuous network . . . . . . . . . . . . . . . . 9:3Covered Nozzles . . . . . . . . . . . . . . . . . . . 8:7Create 3D View . . . . . . . . . . . . . . . . . . . . 9:6Create weld form . . . . . . . . . . . . . . . . . . 9:14Current element . . . . . . . . . . . . . . . . . . . 9:5Current element:definition . . . . . . . . . . . . 3:2

DData consistency . . . . . . . . . . . . . . . . . . 9:10Data consistency checking:principles . . . 7:1Database . . . . . . . . . . . . . . . . . . . . . 9:1, 9:2Database hierarchy . . . . . . . . . . 3:2, 9:2, 9:3DATUMs as routing points . . . . . . . . . . 8:31DB . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1, 9:2Default specification:setting . . . . . . . . . . 5:3Deletable components . . . . . . . . 8:20, 8:24Delete spool breaks . . . . . . . . . . . . . . . 9:24Department:creating . . . . . . . . . . . . . . . . 9:4Department:definition . . . . . . . . . . . . . . . 9:3Design Data element . . . . . . . . . . . . . . . 4:2Design data:checking . . . . . . . . . . . . . . . 7:1Design database . . . 3:1, 9:1, 9:2, 9:13, A:1Design Dataset element . . . . . . . . . . . . . 4:2Design Explorer . . . . . . . . . . . . . . . . . . . 3:4Design point . . . . . . . . . . . . . . . . 9:13, 9:14Design templates . . . . . . . . . . . . . . . . . . 4:2Direction of travel:on routing planes . . . 8:44Direction of view . . . . . . . . . . . . . . . . . . . 9:7Display isometric . . . . . . . . . . . . . . . . . . 9:25Display list . . . . . . . . . . . . . . . . . . . . . . . 9:25Drawing annotations . . . . . . . . . . . . . . . 9:27Drawing contents . . . . . . . . . . . . . . . . . 9:26Drawing Template . . . . . . . . . . . . . . . . . 11:9Drawlist . . . . . . . . . . . . . . . . . . . . . . . . . . 9:6

EEDG . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:14Element:definition . . . . . . . . . . . . . . . . . . 3:2Equipment:creating . . . . . . . . . . . . . . . . 4:3Equipment:definition . . . . . . . . . . . . . . . . 3:1Equipment:representation . . . . . . . . . . . 4:1Equipment:standard designs . . . . . . . . . 4:3Erection . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Error messages . . . . . . . . . . . . . . . . . . . 6:6Event driven graphics . . . . . . . . . . . . . . . 9:5Expressions . . . . . . . . . . . . . . . . . 8:32, 8:60Extend route handle . . . . . . . . . . . 5:41, 5:52

FFabrication . . . . . . . . . . . . . . . . . . . 9:1, 9:16Fabrication database . . . . . . . . . . . . 9:1, 9:2Fabrication machine data . . . . . . . . . . . . D:1Fabrication machine manager . . . . . . . . D:1Feature highlighting . . . . . . . . . . . 5:41, 5:51Feature picking . . . . . . . . . . . . . . . . . . . 6:25Field . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Field weld . . . . . . . . . . . . . . . . . . . . . . . 9:13Fields . . . . . . . . . . . . . . . . . . . . . . . . 9:1, 9:3Flange spacing:on racks and planes . . 8:81Flanges:on routing planes . . . . . . 8:57, 8:81Forced spool breaks . . . . . . . . . . . . . . . 9:16Forced spool breaks: at Branch/Pipe changes

9:24Forced spool breaks: at Joints . . . . . . . 9:23Free tail:with Pipe racks or planes . . . . 8:46Free Tails . . . . . . . . . . . . . . . . . . . . . . . . 8:5

GGeometry set . . . . . . . . . . . . . . . . . . . . . 5:3Graphical view . . . . . . . . . . . . . . . . . . . . 3:4Graphical views . . . . . . . . . . . . . . . . . . . 9:5

HHard obstruction . . . . . . . . . . . . . . . . . . . 7:4Head See Branch head . . . . . . . . . . 3:1, 5:2Head work-point . . . . . . . . . . . . . . . . . . 8:22Head-relative positioning . . . . . . . . . . . 8:20

IIJOINT . . . . . . . . . . . . . . . . . . . . . . . . . . B:3Implied joints . . . . . . . . . . . . . . . . . . . . . B:3Implied welds . . . . . . . . . . . . . . . . . . . . . B:2Importing P&IDs . . . . . . . . . . . . . . . . . . 8:57In tube weld . . . . . . . . . . . . . . . . . . . . . 9:15

12.0© 2007 AVEVA Solutions Ltd Index page ii


Include adjacent field components . . . . 9:19Inserting a weld . . . . . . . . . . . . . . . . . . . 9:13Inspecting the site . . . . . . . . . . . . . . . . . 9:11Insulation specifications:modifying . . . . 6:11ISO option . . . . . . . . . . . . . . . . . . . . . . . . 9:7Isodraft . . . . . . . . . . . . . . . . . . . . . 9:1, 9:24Isodraft application window . . . . . . . . . . 9:24Isodraft messages . . . . . . . . . . . . . . . . . 9:26Isometric drawing contents . . . . . . . . . . 9:26Isometric drawings . . . . . . . . . . . . . . . . . 9:1Isometric Plots . . . . . . . . . . . . . . . . 9:2, F:1Isometric plots:generating . . . . . . . . . . . . 7:7Isometric plotting . . . . . . . . . . . . . . . . . . . 7:7Isometric view . . . . . . . . . . . . . . . . 4:11, 9:7IWELD . . . . . . . . . . . . . . . . . . . . . . . . . . . B:2

JJNTGRP . . . . . . . . . . . . . . . . . . . . . . . . . B:2Joint connections . . . . . . . . . . . . . . . . . . B:2Joint group . . . . . . . . . . . . . . . . . . . . . . . B:2Joint numbers . . . . . . . . . . . . . . . . . . . . 9:18Joint types . . . . . . . . . . . . . . . . . . . . . . . . B:2Joints . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:23

KKey elements . . . . . . . . . . . . . . . . . . . 12:19

LLimits:setting for view . . . . . . . . . 4:11, 4:13Locked components . . . . . . . 8:8, 8:20, 8:24Locking:components . . . . . . . . . . . 8:8, 8:24Logging in . . . . . . . . . . . . . . . . . . . . . . . . 3:3Look option . . . . . . . . . . . . . . . . . . . . . . . 9:7

MManipulating a 3D View . . . . . . . . . . . . . 9:8Manual data selection . . . . . . . . . . . . . . 9:21Measure . . . . . . . . . . . . . . . . . . . . . . . . 9:12Measuring a pipe . . . . . . . . . . . . . . . . . 9:12Member:definition . . . . . . . . . . . . . . . . . . 3:2Members list . . . . . . . . . . . . . . . . . . . . . . 9:6Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Messages, routing . . . . . . . . . . . . . . . . . 8:18Minimum tube . . . . . . . . . . . . . . . . . . . . 8:27Misalignment:checking . . . . . . . . . . . . . . 7:1Misalignment:tolerances . . . . . . . . . . . . . 7:2Modify Components Form . . . . . . . . . . . . 6:2Module:definition . . . . . . . . . . . . . . . . . . . 2:1Multiple 3D Views . . . . . . . . . . . . . . . . . . 9:5Multiple mode splitting . . . . . . . . . . . . . 6:14

NNaming . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2Network . . . . . . . . . . . . . . . . . . . . . 8:14, 9:3Non-graphical assemblies . . . . . . . . . 12:12Non-orthogonal routing . . . . . . . . . . . . 8:25Nozzle (NOZZ):definition . . . . . . . . . . . . 3:1Nozzle:creating . . . . . . . . . . . . . . . . . . . 4:8Nozzle:definition . . . . . . . . . . . . . . . . . . . 4:1Nozzles, covered . . . . . . . . . . . . . . . . . . 8:7Numbering . . . . . . . . . . . . . . . . . . . 9:2, 9:18Numbering settings form . . . . . . . 9:18, 9:21Numbering update . . . . . . . . . . . . . . . . 9:20Numbering update options . . . . . . . . . . 9:20

OObstruction levels . . . . . . . . . . . . . . . . . . 7:4Obstruction list . . . . . . . . . . . . . . . . . . . . 7:5Order, routing:changing . . . . . . . . . . . . 8:16Orientation rules . . . . . . . . . . . . . . . . . 12:17Orthogonal view . . . . . . . . . . . . . . . . . . . 9:7Outputting spool data . . . . . . . . . . . . . . 9:24Owner:definition . . . . . . . . . . . . . . . . . . . 3:2

PP&ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:57P&ID files:neutral description language 8:87Packing methods . . . . . . . . . . . . . . . . . 8:83Packing methods: height . . . . . . . . . . . 8:83Packing methods: weight . . . . . . . . . . . 8:83Packing pipes on Racks . . . . . . . . . . . . 8:46Packing:on racks and planes . . . . 8:55, 8:81Panning view . . . . . . . . . . . . . . . . . . . . 4:11Parameters:catalogue components . . . . 5:2P-arrive . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Part numbers . . . . . . . . . . . . . . . . . . . . 9:18PDMS Router . . . . . . . . . . . . . . . . . . . . . 8:1PDUV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:iPhysical clash:definition . . . . . . . . . . . . . 7:4Picking . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Pipe gap rounding . . . . . . . . . . . . . . . . 8:56Pipe Packing . . . . . . . . . . . . . . . . . . . . 8:46Pipe packing methods . . . . . . . . . . . . . 8:83Pipe packing:additional gap . . . . . . . . . 8:84Pipe piece:definition . . . . . . . . . . . . . . . 10:1Pipe Production Checks form:options . 10:8Pipe Racks . . . . . . . . . . . . . . . . . . . . . . 8:44Pipe Racks:adding to Branch constraints 8:51Pipe Racks:conceptual . . . . . . . . . . . . . 8:53Pipe racks:direction of travel . . . . . . . . 8:44Pipe Racks:packing . . . . . . . . . . . 8:55, 8:81Pipe Racks:rules . . . . . . . . . . . . . . . . . 8:78

12.0© 2007 AVEVA Solutions Ltd Index page iii


Pipe Racks:steelwork for . . . . . . . . . . . 8:47Pipe routes:deleting . . . . . . . . . . . . . . . 5:65Pipe routing handle . . . . . . . . . . . . . . . . 5:41Pipe sketches . . . . . . . . . . . . . . . . . . . . 11:1Pipe sketches:administration . . . . . . . . 11:9Pipe sketches:creating . . . . . . . . . . . . . 11:1Pipe splitting . . . . . . . . . . . . . . . . . . . . . 6:12Pipe spool . . . . . . . . . . . . . . . . . . . . . . . 10:1Pipe Spool Manager . . . . . . . . . . . . . . . .C:4Pipe:definition . . . . . . . . . . . . . . . . . 3:1, 9:3Pipes splitting with a plane . . . . . . . . . . 6:16Pipework . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Pipework spooling . . . . . . . . . . . . . . . . . 9:16Pipework:modification . . . . . . . . . . . . . . . 6:1Piping Assemblies . . . . . . . . . . . . . . . . . 12:1Piping Assembly Component Rules . . 12:14Piping component:aligning . . . . . . . . . . 5:30Piping component:creating . . . . . . . . . . 5:12Piping Network . . . . . . . . . . . . . . . 9:1, 9:16P-leave . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2Plot view:manipulating . . . . . . . . . . . . . . 4:7Plotting . . . . . . . . . . . . . . . . . . . . . . . . . 9:24Plotting facilities . . . . . . . . . . . . . . . . . . . 7:7Plotting options . . . . . . . . . . . . . . . . . . . 9:24Plotting spool drawings . . . . . . . . . . . . . 9:24Plotting:isometrics . . . . . . . . . . . . . . . . . . 7:7PML functions . . . . . . . . . . . . . . . . . . . . 8:61PML functions:in Rules . . . . . . . . . . . . . 8:69Point set . . . . . . . . . . . . . . . . . . . . . . . . . 5:3Popup Menus on the QPR Handle . . . . 5:55Position options . . . . . . . . . . . . . . . . . . . 5:31Position rules . . . . . . . . . . . . . . . . . . . 12:17Positionable components . . . . . . 8:20, 8:24Positioning components . . . . . . . 8:21, 8:27Positioning Control form . . . . . . . . . . . . 9:12P-point . . . . . . . . . . . . . . . . . . . . . . . . . . 9:13P-point:definition . . . . . . . . . . . . . . . . . . . 5:2P-point:p-arrive . . . . . . . . . . . . . . . . . . . . 5:2P-point:p-leave . . . . . . . . . . . . . . . . . . . . 5:2P-point:point set . . . . . . . . . . . . . . . . . . . 5:3Preparing a site . . . . . . . . . . . . . . . . . . . 9:10Primary origin . . . . . . . . . . . . . . 6:20, 12:13Primitive:creating . . . . . . . . . . . . . . . . . . 4:8Primitive:definition . . . . . . . . . . . . . . 3:1, 4:1Primitive:geometry set . . . . . . . . . . . . . . 5:3Production Check:running . . . . . . . . . . 10:13Production Checks . . . . . . . . . . . . . . . . 10:1Production Checks:setting up . . . . . . . 10:10Properties:parameterised dimensions etc. 4:2Pulled bend numbers . . . . . . . . . . . . . . 9:18PURP attribute . . . . . . . . . . . . . . . . . . . 8:59Purposes:Routing rules . . . . . . . . . . . . . 8:59

QQuerying:Branch rules . . . . . . . . . . . . . 8:36Quick Pipe Routing . . . . . . . . . . . . . . . 5:39

RReal welds . . . . . . . . . . . . . . . . . . . . . . . B:3Reducers:rules . . . . . . . . . . . . . . . . 8:5, 8:65Registry:creating . . . . . . . . . . . . . . . . . . 9:5Registry:definition . . . . . . . . . . . . . . . . . . 9:3Remove CE . . . . . . . . . . . . . . . . . . . . . . 9:9Remove from Spool Drawing . . . . . . . . 9:19Reports:templates . . . . . . . . . . . . . . . . . 7:6Restore View . . . . . . . . . . . . . . . . . . . . . 9:9Rotating view . . . . . . . . . . . . . . . . . . . . 4:11Rotation handles . . . . . . . . 5:44, 5:51, 5:55Routing messages . . . . . . . . . . . . . . . . 8:18Routing order . . . . . . . . . . . . . . . . . . . . 8:16Routing pipes . . . . . . . . . . . . . . . . . . . . 8:14Routing Planes . . . . . . . . . . . . . . . . . . . 8:36Routing Planes: . . . . . . . . . . . . . . . . . . 8:40Routing Planes:adding to branches . . . 8:40Routing planes:creating . . . . . . . . . . . . 8:38Routing Planes:finding automatically . . 8:41Routing Planes:multiple . . . . . . . . . . . . 8:37Routing Planes:packing . . . . . . . . 8:55, 8:81Routing Points . . . . . . . . . . . . . . . . . . . 8:27Routing points: Using Datums . . . . . . . 8:31Routing points:position . . . . . . . . . . . . . 8:31Routing rules . . . . . . . . . . . . . . . . 8:32, 8:59Routing rules:constructing . . . . . . . . . . 8:60Routing rules:purposes . . . . . . . . . . . . 8:59Rule Set . . . . . . . . . . . . . . . . . . . . . . . . 8:75Rule World . . . . . . . . . . . . . . . . . . . . . . 8:75Rules for Pipe Racks . . . . . . . . . . . . . . 8:70Rules:applying . . . . . . . . . . . . . . . . . . . 8:33Rules:Bends or Elbows . . . . . . . . . . . . 8:65Rules:Clash exclusion . . . . . . . . . . . . . 8:70Rules:deleting . . . . . . . . . . . . . . . . . . . 8:80Rules:Downstream pipe requirement (DNSM)

8:66Rules:Elevation (ELEV) . . . . . . . . . . . . 8:68Rules:Entry Plane (ENTR) . . . . . . . . . . 8:71Rules:Exit Plane (EXIT) . . . . . . . . . . . . 8:71Rules:Extra Gap (ADGP) . . . . . . . . . . . 8:72Rules:Flange Width . . . . . . . . . . . . . . . 8:72Rules:Heavy Pipe (WEIG)) . . . . . . . . . 8:72Rules:including from another set or world 8:34Rules:Location (LOCA) . . . . . . . . . . . . 8:68Rules:logical . . . . . . . . . . . . . . . . . . . . . 8:61Rules:Orientation on major axis (MAJO) 8:68Rules:Orientation on minor axis (MINO) 8:68Rules:Pipe Racks . . . . . . . . . . . . . . . . . 8:78

12.0© 2007 AVEVA Solutions Ltd Index page iv


Rules:PML functions in . . . . . . . . . . . . . 8:61Rules:Ptr-processing (PRPR) . . . . . . . . 8:62Rules:real . . . . . . . . . . . . . . . . . . . . . . . 8:61rules:real expressions in . . . . . . . . . . . . 8:85Rules:reducers . . . . . . . . . . . . . . . 8:5, 8:65Rules:removing from component . . . . . 8:35Rules:Selection . . . . . . . . . . . . . . . . . . . 8:65Rules:Shoe height (SHOE) . . . . . 8:71, 8:85Rules:Travel Plane (TRAV) . . . . . . . . . . 8:70Rules:Upstream pipe requirement (UPSM) 8:67RWELD . . . . . . . . . . . . . . . . . . . . . . . . . . B:3

SSave View . . . . . . . . . . . . . . . . . . . . . . . . 9:9Searching . . . . . . . . . . . . . . . . . . . . . . . 9:16Secondary origin . . . . . . . . . . . . 6:20, 12:13Select data for spool elements form . . . 9:21Setting up a 3D View . . . . . . . . . . . . . . . 9:6SFLimit attribute:Spool breaks 9:1, 9:16, 9:24Shoe height . . . . . . . . . . . . . . . . . . . . . . 8:85Shoe height rule . . . . . . . . . . . . . . . . . . 8:71Shoe heights . . . . . . . . . . . . . . . . . . . . . 8:85Shop . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Shop Flag . . . . . . . . . . . . . . . 9:1, 9:16, 9:22Shop Flag status . . . . . . . . . . . . . . . B:1, B:3Shop/Field setting . . . . . . . . . . . . . . . . . 9:22Single Mode Splitting . . . . . . . . . . . . . . 6:22Site:creating . . . . . . . . . . . . . . . . . . 3:4, 3:5Site:definition . . . . . . . . . . . . . . . . . 3:1, 9:3Sketch creation options . . . . . . . . . . . . . 11:5Soft obstruction . . . . . . . . . . . . . . . . . . . . 7:4Specification reference (SpecRef):definition 5:1Specification:default . . . . . . . . . . . . . . . . 5:3Specification:selecting equipment . . . . . . 4:4SPLDRG . . . . . . . . . . . . . . . . . . . . 9:1, 9:16Spool . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:16Spool breaks . . . . . . . . . . . . . . . . . 9:22, B:1Spool data:outputting . . . . . . . . . . . . . . 9:24Spool drawing . . . . . . . . . . . . . . . . . . . . 9:16Spool Drawing:definition . . . . . . . . . . . . . 9:3Spool Drawings . . . . . . . . . . . . . . . . . . . . 9:1Spool numbers . . . . . . . . . . . . . . 9:18, 9:20Spool shipping volume . . . . . . . . . 9:2, 9:19Spool size . . . . . . . . . . . . . . . . . . . . . . . 9:19Spool/field limit attributeSee SFLimit attribute

9:1, 9:16, 9:24Spooler . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Spooling . . . . . . . . . . . . . . . . . . . . . . . . 9:16Spooling networks . . . . . . . . . . . . . . . . . 9:16Spools . . . . . . . . . . . . . . . . . . . . . . . 9:1, 9:3Spools:renaming . . . . . . . . . . . . . . . . . 10:22Standard isometrics . . . . . . . . . . . . . . . 9:24STAP pseudo-attribute . . . . . . . . . . . . . 8:66

Starting . . . . . . . . . . . . . . . . . . . . . . . . . . 9:3Starting:SPOOLER session . . . . . . . . . . 9:3Startup display . . . . . . . . . . . . . . . . . . . . 3:3Status bar . . . . . . . . . . . . . . . . . . . . . . . . 3:4Status summary form . . . . . . . . . . . . . . 8:16STLE pseudo-attribute . . . . . . . . . . . . . 8:66Stock length:defining . . . . . . . . . . . . . 10:12STYPE Rules . . . . . . . . . . . . . . . . . . . 12:15Subequipment element . . . . . . . . . . . . . 4:2Switching modules . . . . . . . . . . . . . 9:3, 9:24

TTables . . . . . . . . . . . . . . . . . . . . . . . . 11:11Tail See Branch tail . . . . . . . . . . . . . 3:1, 5:2Tail work-point . . . . . . . . . . . . . . . . . . . 8:22Tail-relative positioning . . . . . . . . . . . . 8:20Tees, positioning . . . . . . . . . . . . . . . . . . 8:5Title bar . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Tool bar . . . . . . . . . . . . . . . . . . . . . . . . . 3:4Touch:definition . . . . . . . . . . . . . . . . . . . 7:4Tracing specifications:modifying . . . . . 6:11Transparency . . . . . . . . . . . . . . . . . 8:50, 9:7Type of view . . . . . . . . . . . . . . . . . . . 9:6, 9:7Types of joints . . . . . . . . . . . . . . . . . . . . B:2Types of welds . . . . . . . . . . . . . . . . . . . . B:2

UUndo . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:16Unlocking components . . . . . . . . . . . . . 8:24Update . . . . . . . . . . . . . . . . . . . . . . . . . 9:20Update choice handling . . . . . . . . 9:20, 9:21Update/Number button . . . . . . . . . . . . . 9:18Update/Number spool drawing form 9:18, 9:21Use first available data . . . . . . . . . . . . . 9:21

VView contents . . . . . . . . . . . . . . . . . . . . . 9:6View control form . . . . . . . . . . . . . . . . . . 9:5View direction . . . . . . . . . . . . . . . . . . . . 4:11View limits . . . . . . . . . . . . . . . . . . . . 9:6, 9:7View:3D/graphical . . . . . . . . . . . . . . 3:4, 4:9View:centre of interest . . . . . . . . . . . . . 4:13View:panning . . . . . . . . . . . . . . . . . . . . 4:11View:rotating . . . . . . . . . . . . . . . . . . . . 4:11View:zooming . . . . . . . . . . . . . . . . . . . . 4:11Viewing direction . . . . . . . . . . . . . . . . . . 9:7

WWeld connections . . . . . . . . . . . . . . . . . . B:2Weld numbers . . . . . . . . . . . . . . . . . . . 9:18

12.0© 2007 AVEVA Solutions Ltd Index page v


Weld types . . . . . . . . . . . . . . . . . . . . . . . B:2Welds . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1Welds:inserting . . . . . . . . . . . . . . . . . . . 9:13WLDGRP . . . . . . . . . . . . . . . . . . . . . . . . B:2Work-points . . . . . . . . . . . . . . . . . . 8:1, 8:22World:definition . . . . . . . . . . . . . . . . 3:1, 9:3

ZZone:creating . . . . . . . . . . . . . . . . . . . . . 3:5Zone:definition . . . . . . . . . . . . . . . . 3:1, 9:3Zooming view . . . . . . . . . . . . . . . . . . . . 4:11

12.0© 2007 AVEVA Solutions Ltd Index page vi

Pipework Design User Guide

Documents

Transcript of Pipework Design User Guide