Pdms Design

PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3

pdms1131/man31/doc2 Issue 181200

PLEASE NOTE: Cadcentre has a policy of continuing product development: therefore, the information contained in this document may be subject to change without notice. CADCENTRE MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. PURPOSE. While every effort has been made to verify the accuracy of this document, Cadcentre shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance or use of this material.

This manual provides documentation relating to products which you may not have access to or which may not be licensed to you. For further information on which products are licensed to you please refer to your licence conditions.



Copyright 1990 through 2001 Cadcentre Limited

All rights reserved. No part of this document may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of Cadcentre. The software programs described in this document are confidential information and proprietary products of Cadcentre Ltd or its licensors.

For details of Cadcentre's worldwide sales and support offices, see our website at

http://www.cadcentre.com/location

Cadcentre Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK

Contents 1 1.1 1.2 1.2 1.3

Introdu Introducti ction on ........ ............ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ .......1-1 ...1-1 About th is Man ua l..... l........ ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ..... 1-1 Organisatio Organisation n of the DESIGN Ref Reference erence Manual .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...1.1-1 1 Organisat ion ion of this Manu al .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...1-2 .1-2

2

Data Data Consis Consisten tency cy Checki Checking....... ng........... ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ......2-1 ..2-1

2.1

Specif Specifyi ying ng t he Checking Checking Pr ocedures... ocedures..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....2..2-2 2 2.1.1 2.1.1 Specify Specifying ing t he Out put Devic Device for Diagnostic Messages ...... ......... ...... ...... ...... ...... ...... ...... ...... ..... 2-2 2-2 2.1.2 Checkin g Pa r ts of th e Design .......... ............... .......... ......... ......... .......... .......... .......... .......... ......... ......... .......... .......... .........2-2 ....2-2 Setting Geometr Geometr ic Err or Limits Limits .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....2..2-3 3 2.2.1 Pip ing/Ha nger s ......... ............. ......... .......... ......... ......... .......... ......... ......... .......... .......... ......... ......... .......... ......... ......... .......... ......... ......... ....... 2-3 2.2.2 St r uctu ra l Sections .......... ............... .......... ......... ......... .......... .......... .......... ......... ........ ......... ......... ......... .......... .......... .......... ......... .......2-4 ...2-4 2.2.3 St ru ctu ra l J oints ......... .............. .......... ......... ......... .......... .......... .......... ......... ......... .......... .......... .......... .......... ......... ......... .......... ..........2-6 .....2-6 2.2.4 St ru ctu ra l Fitt ings ......... .............. ......... ......... .......... .......... .......... ......... ......... .......... .......... .......... .......... ......... ......... .......... .......... ....... .. 2-7 Minimum Minimum Tube Tube and Ro Rod Leng Lengths ths aand nd Maxi Maximum mum Bend Bend Angl Angles. e s....... ...... .... ........ ...... .... .... ......22-8 8 2.3.1 2.3.1 Specify Specifying ing Minimu m Length s Irr espective of Bore ...... ......... ...... ...... ...... ...... ...... ...... ...... ...... ...... .....2-8 ..2-8 2.3.2 2.3.2 Specify Specifying ing Bo Bore-Dependen re-Dependen t Minimu m Length s ...... ......... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ..... 2-9 2-9 2.3.3 2.3.3 Specify Specifying ing Ma ximum Angles for Ben ds an d Elbows Elbows ...... ......... ...... ...... ...... ...... ...... ...... ...... ...... ..... 2-10 2-10 Combi Co m bined ned Pipew Pipewo orrk k Tol Tolerance erance and Tube Leng L ength th Optio Options ..... ...... .... ........ ...... .... .... .... ........ .....2. 2-11 11 Specif Specifyi ying ng Minimum Minimum and Maxi Maximum mum Sectio Section n Lengths Lengths .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...2-1 .2-12 2 Specif Specifyi ying ng User-D User-Def efine ined d SKEY SKEYss Ac Acceptable eptable in Data Data Checks Checks .... ...... .... .... .... .... .... .... .... .... ....2..2-14 14 Diagno Diagnostic stic Message Messagess from from Data Data Consistenc Consistency y Chec Checks ks .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....2..2-15 15 2.7.1 Global Diagn ostics............. ostics................. ......... .......... ......... ......... .......... ......... ......... .......... ......... ......... .......... ......... ......... .......... .........2-15 ....2-15 2.7.2 Br an ch-Specific ch-Specific Diagn ostics........... ostics................ .......... ......... ......... .......... .......... .......... ......... ......... .......... .......... .......... ........2-15 ...2-15 2.7.3 Componen t-Specific t-Specific Diagn ostics ........ ............. .......... ......... ........ ......... .......... .......... .......... ......... ........ ......... .......... ....... 2-19 2.7.4 St r uctu re-Sp ecific ecific Diagn ostics ......... .............. .......... .......... .......... .......... .......... .......... .......... .......... ......... ........ ......... ....... 2-23

2.2

2.3 2.3

2.4 2.4 2.5 2.5 2.6 2.6 2.7 2.7

3

Clash Clash Detect Detection....... ion........... ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ......3-1 ..3-1

3.1 3.2 3.3 3.4 3.5 3.5 3.6 3.6 3.7 3.8 3.9

Ent ering Clash Detectio Detection n Mode... Mode..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...3-3 .3-3 Defining Defining t he Obstru ction tion List List .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...3-3 .3-3 Defining Defining t he Regio Region n of In terest .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...3-6 .3-6 Defining Defining Touches Touches an d Clear Clear ances... ances..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3..3-8 8 Ignoring Ignoring Clashes Clashes Within Within Specif Specifie ied d E lement lement Types.. Types.... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3..3-9 9 Ignoring Ignoring Clashes Clashes at Steelwo Steelwork rk J unctio unctions .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...3-1 .3-10 0 Ignoring Touches Touches ...... ......... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ......3-11 ...3-11 Cont Co nt rolli rolling ng th e Report Report ed Clash Positio Position n .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3-1 ..3-11 1 Specif Specifyi ying ng How Bran ches Are Are Checked... Checked..... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...3-12 .3-12 3.9.1 Rules Applicable Dur ing Type B Checks .......... ............... .......... .......... .......... .......... .......... .......... .......... ....... .. 3-13 3.10 Checking For Clashes........ Clashes........... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ......3-16 ...3-16 3.10.1The Principles..............................................................................................3-16 3.10.2 Ru nn ing a Fu ll Compon ent Check ........ ............ ........ ........ ......... ......... ........ ........ ......... ......... ........ ........ ......... ........3 ...3 -17 3.10.3 Ru nn ing a n Obst ru ction Box Check ........ ............ ......... ......... ........ ........ ......... ......... ........ ........ ......... ......... ........3-18 ....3-18 3.10.4 Adding Checked I tem s to th e Obstr uction List ......... .............. .......... .......... ......... ......... .......... .........3-18 ....3-18 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3

Contents-i

Contents

3.11

3.19 3.19

Reporting th e Clashes Foun d...... d......... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... .....3-19 ..3-19 3.11.1The Principles..............................................................................................3-19 3.11.2 Cus tom ising t he Report Hea der .......... ............... .......... .......... .......... .......... .......... .......... .......... .......... .......... ..........3-20 .....3-20 3.11.3 Cus tom ising t he Ma in Body of th e Report ........ ............. ......... ......... .......... ......... ......... .......... ......... ........3-21 ....3-21 3.11.4 Cus tom ising t he Repor t Su mm ar y ........ ............. .......... .......... .......... .......... .......... .......... .......... .......... .......... ........3 ...3 -24 Querying Clash Clash Data Directly Directly .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3-2 ..3-25 5 3.12.1 Qu eryin g In dividu al Clash es ......... ............. ......... .......... .......... ......... ......... .......... .......... ......... ......... .......... .......... .........3-25 ....3-25 3.12.2 Qu eryin g Clash St at ist ics ics ......... .............. ......... ......... .......... .......... ......... ......... .......... .......... ......... ......... .......... .......... .........3-26 ....3-26 Report Report ing With With out Fur ther Clash Clash Checking Checking .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3-2 ..3-26 6 3.13.1 Gen er at ing a Report from Exist ing Clas Clas h Dat a ......... .............. .......... .......... ......... ......... .......... ........3 ...3 -27 3.13.2Suppressing Clash Repetition in Reports...................................................3-28 Appr oving oving Clashes........ Clashes........... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... .....3-28 ..3-28 3.14.1The Principles..............................................................................................3-28 3.14.2 Adding Clash es to th e Approval List ......... .............. .......... .......... .......... .......... .......... .......... .......... ......... ........ ...... 3-29 3.14.3 Rea pp r oving Moved Clas h es .............................. ............................................. .............................. ..........................3 ...........3 -31 3.14.4 Removing Cla sh es fr om t he Approval List ......... .............. ......... ......... .......... .......... ......... ......... .......... ....... .. 3-31 3.14.5 Ou tp ut tin g t he Appr oval oval List ......... ............. ......... ......... ........ ......... .......... ......... ........ ......... ......... ........ ......... ......... .......3-32 ...3-32 Saving a nd Restoring Restoring Clash Clash Data .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 3-33 3-33 3.15.1Saving Data to a File...................................................................................3-33 3.15.2 Rest oring Dat a from a File............ File................. ......... ......... .......... .......... .......... .......... ......... ......... .......... .......... .......... .........3-34 ....3-34 Creating Macro Macro Files Files Incorporat Incorporat ing Clash Data .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....3-3 ..3-35 5 3.16.1The Principles..............................................................................................3-35 3.16.2 Gen er at ing Macro-Style Out pu t .......... ............... .......... .......... .......... .......... .......... .......... .......... .......... .......... ......... ...... 3-36 Displaying Clashes Visua lly ...... ......... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ......3-39 ...3-39 Aut omat ic (Co (Continu ntinu ous) Clash Detectio Detection n .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 3-40 3-40 3.18.1 Specifying Specifying Autom at ic Clash Det ection Mode ........ ............. ......... ......... ......... ......... ......... ......... ......... ...... 3-40 3.18.2 Logging t h e Clas h es .................................. ................................................... ................................... .................................3-41 ...............3-41 Er ror Messages Messages in Clash Clash Detectio Detection n Mode Mode .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... 3-41 3-41

4

Copyi Copying ng Model Model Data Data from from PDMS PDMS to REVIEW REVIEW.... ........ ........ ........ ........ ........ ........ ........ ........ ........ ........ ......4-1 ..4-1

3.12 3.12

3.13 3.13

3.14

3.15 3.15

3.16 3.16

3.17 3.18 3.18

4.1 4.2 4.3 4.4 4.5

The Model Model File....... File.......... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... ...... .....4-1 ..4-1 Objec Objectt Selectio Selection n a nd Colo Colour Setting .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...4-2 .4-2 Cont Co nt rolli rolling ng th e Representat ion ion of of Holes Holes .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....4-3 ..4-3 Copyi Co pying ng Dat a to th e Model Model File .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....4..4-3 3 The EXPORT EXPORT Co Comm mm and - Fu ll Syntax .... ...... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ...4-4 .4-4

Index


Contents-ii

1

Introduction

1.1

About this Manual Th e PDMS DE S IGN R eference Man ual describes all the DESIGN commands in detail. It also describes how the Design database is structured, the Design database elements and their att ributes. DESIGN is normally used interactively. The Graphical User Interface (GUI) provides discipline-based a pplicat ions which h elp you to creat e, check a nd report on t he model. How to use t he ap plicat ions is described in u ser guides an d on-line help. This manual is written for experienced users of PDMS DESIGN who need to use comm an ds; for example, to write bat ch ma cros or to cust omise the GUI. If you a re going t o cust omise the GUI, you will also need to refer t o the Cadcentre S oftware Custom isation Guide an d Cadcentre S oftware Custom isation Reference Man ua l for inform ation about P ML, the Cadcent re pr ogramm ing language.

1.2

Organisation of the DESIGN Reference Manual Th e DES IGN Reference Manu al has four parts: •

Part 1, General Com m and s , describes genera l DESIGN comm an ds, which ar e used, for example, for setting u p th e display, and querying and na vigating around th e Design dat abase. In par ticular, it describes how to use th e comma nd s yn t a x g r a p h s , which ar e used t o show all the options available for each comman d.

•

Part 2, Creatin g the Model, describes the commands for creating database elements a nd setting their at tributes.

•

Part 3, Elements an d Attributes, conta ins det ails of all th e elemen ts which can be creat ed in th e Design dat abase, th eir position in th e database hierarchy and th eir attr ibutes.

•

Pa rt 4 (th is volume) describes th e DESIGN Ut ilities for da ta consist ency checking and clash detection, and for exporting DESIGN data to progra ms su ch a s REVIEW.

For a compr ehensive list of all PDMS att ributes a nd pseudo-att ributes, see the Cadcentre S oftw are Custom isation Reference Man ua l. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3

1-1

Introduction

1.3

Organisation of this Manual This ma nu al, Par t 4, is divided int o th e following cha pter s:

1-2

•

Chapter 2 explains how to check Data Consistency.

•

Chapter 3 describes the Clash Detection facilities.

•

Chapter 4 gives det ails of th e EXPORT comma nd, wh ich Copies Model Data from PDMS to RE VIEW .


2

Data Consistency Checking This cha pter describes the comma nds used for t he P DMS Design Dat a Consistency Checking Utility (DATACON). The checks include the following: 1.

Adjacent item s ar e connected an d no gaps exist.

2.

Conn ection types a re compa tible.

3.

Conn ected components ar e not sk ewed with respect to one a nother.

4.

Pipe bores or ha nger r od diameter s ar e consistent.

5.

Bran ch a nd equipment conn ections a re properly term inated.

6.

Ha ngers a re corr ectly conn ected t o Fittings an d Attas.

7.

Tubes or rods joining components are not less than minimum acceptable lengths.

8.

Angles of pulled Bends a nd E lbows fall within th e limits s et in t he relevant Specifications.

9.

Str uctur al Sections an d J oints ar e corr ectly positioned with respect to each other and are properly connected.

10.

Lengths of structural Sections fall within predefined ranges.

The comm an ds for checking for dat a inconsist encies fall into th ree gener al categories: •

Those which s pecify th e design ar eas t o be checked an d how diagnostic messages will be output.

•

Those which specify the ma ximum m isalignmen ts or positiona l errors allowed between adjacent componen ts. N o errors will be report ed below th ese limits.

•

Those which sp ecify minimu m length s of tu be between ad jacent piping components (norma lly dependent upon t he t ube diamet er) or for rod between adjacent hanger components, the maximum acceptable angle for pipe bends, an d the minimum a nd ma ximu m length s of str uctura l Sections.


2-1

Data Consistency Checking

1.1

Specifying the Checking Procedures

2.1.1 Specifying the Output Device for Diagnostic Messages Keywords:

ALPHA FILE

(APPEND OVERWRITE)

Description:

Before you in itiat e a da ta -checking operat ion you mu st sp ecify whether th e resulting output is to be sent to your term inal or t o a file. The outpu t device mu st be defined before th e deta iled checking is car ried out , using the stan dar d ALPHA FILE comma nds described in Par t 1 of th e PDMS DE S IGN R eference Man ual.

2.1.2 Checking Parts of the Design Keywords:

CHECK

ATTACHECK

Description:

Th e CHECK command initiates a full Component-by-Component data consistency check of specified par ts of th e Design. Up to 10 element s ma y be specified in a single CHECK command. ATTAs will be checked in t he sa me wa y as n orma l componen ts if the ATTACHECK ON option is in for ce. They will be ignor ed if ATTACHECK OFF is in force. You can store er ror r eferen ces an d (optionally) err or codes in P ML ar ra ys, if requ ired. If you do this, you can t hen u se th e ENHANCE command to highlight the problems on the display. See the Cadcentre S oftware Custom isation Guide for m ore inform at ion on PML an d arrays.

Examples: CHECK /ZONE-1

Genera tes full consistency report on every componen t in t he n am ed Zone CHECK /BRAN1 /BRAN2 /BRAN3

Generat es selective report on th e na med Bra nches only TOL ATTACHECK OFF

ATTAs will be ignored in su bsequen t checks C om m a n d S yn t a x : .----<-----. / | >-- CHeck --*-- --+-- -- []--. | | ‘---------------------------+----> >-- TOLerance ATTACheck --+-- ON* --. | | ‘-- OFf --+-->

2-2


Data Consistency Checking

Where is the P ML arr ay used t o store references of an y element s with errors, and th e (option) is the a rr ay th at stores th e error codes. Querying: >-- Query TOLerance ATTACheck --> 2.2 Setting Geometric Error Limits 2.2.1 Piping/Hangers Note: All references to pipe component s an d tu be in th is section app ly equally to han ger components and rod. The extent of the misalignment between two adjacent piping components may be measured using any of th ree para meters: the offset distance between th eir respective p-ar rive an d p-leave axes; the displacement a n g l e between th eir respective p-ar rive an d p-leave axes; or t he r a t i o of the offset to the projected distance between the arrive and leave p-points (which is equivalent to the tan gent of the an gle par amet er). See Figure below. p-arrive x = OFFSET ANGLE p-leave y RATIO = x/y = tan(ANGLE) Keywords: TOLERANCE OFFSET ANGLE RATIO MAXANGLE Description: Th e TOLERANCE comm an ds sp ecify th e ma ximum offset, a ngle or ratio misalignments that will be allowed between adjacent components before a diagnostic message is out put . Examples: TOL OFFSET 1 (Default) Maximum pipe misalignmen t is 1 mm offset TOL OFF 1/4 INCH Maximum pipe misalignmen t is 0.25 inch offset TOL ANGLE 0.0573 (Default) Maximum angular misalignment is 0.0573 degrees (i.e. 0.01 radians) TOL RATIO 0.001 (Default) Maximum offset/separ at ion r at io is 0.001 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-3 Data Consistency Checking TOL ANG 1.5 TOL RAT 0.0262 These are equivalent an gular sett ings, since 0.0262 is t he t angent of the an gle 1.5 degrees TOL DEF Resets a ll misalignm ent toleran ces (Offset, Angle an d Rat io) to th eir default values TOL MAXANG 90 (Default) Maximum permitt ed design a ngle for pulled bends and elbows can be set to values from 0° (stra ight t ube) to 180° (U-bends). C om m a n d S yn t a x : >-- TOLerance --+-| |-| |-| |-| ‘-- OFFset --. | ANGle ---| | RATio ---+-- --> DEFault --> MAXANGle -- value --> Querying: >-- Query TOLerance --+-| |-| |-| ‘-- OFFset ----. | ANGle -----| | RATio -----| | MAXANGle --+--> >-- Query TOLerance OPTions --> (also outputs ATTACHECK an d TUBE settings) 2.2.2 Structural Sections Misalignmen ts of Sections in str uctur al designs ar e defined in similar t erms to th ose used for p ipework , na mely in ter ms of an offset d i s t a n c e , a misalignment a n g l e or a r a t i o (the tangent of the angle). These are together referred to as th e Section’s e c c e n t r i c i t y . Distan ce and a ngu lar offsets a re mea sur ed from th e logical line between Nodes, while additional checks a re m ade u sing the a tta ched Neu tr al Points of th e Section an d th e corr esponding Nodes. The ter minology is illust ra ted in t he following F igur e. 2-4 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking NODE Position NODE Position Logical Line b a Neutral Axis (Extended) a SANP (Reference only) POSE SANP (Reference only) POSS SANP = Section Attached Neutral Point a = Eccentricity angle a,b = Eccentricity distances (both ends of Section) Keywords: ECCENTRICITY SECTION DISTANCE ANGLE RATIO (TOLERANCE) Description: Th e ECCENTRICITY SECTION comm an ds specify th e ma ximum offset dista nce, an gle or ra tio misa lignm ent s th at will be allowed between a Section’s Neu tr al Axis a nd th e Logical Line bet ween N odes before a diagnostic message is output. Examples: ECC SECT DIST 1 (Default) Maximu m offset for either end of Section is 1 m m ECC SECT DIST 0.5 INCH Maximu m offset for either end of Section is 0.5 in ECC SECT ANGLE 0.0573(Default) Maximum an gular m isalignment is 0.0573 degrees ECC SECT RATIO 0.001 (Default) Maximu m offset/node separ at ion r at io is 0.001 ECC SECT ANG 1.5 These are equivalent a ngular settings, since ECC SECT RAT 0.0262 0.0262 is th e ta ngent of the an gle 1.5 degrees ECC SECT DEF Resets a ll misalignmen t eccent ricities (Offset dista nce, Angle an d Ra tio) to th eir default values PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-5 Data Consistency Checking C om m a n d S yn t a x : >-- ECCentricity -- SECTion --+-| | | |-| |-| | | ‘-- DISTance --+-- --> | ‘-- DEFault --> ANGle --. | RATio --+-- value --> | ‘-- DEFault --> DEFault --> Querying: Q TOLerance ECCentricity --- SECTion ---+--- DISTance ---. | | |--- ANGle ------| | | |--- RATio ------| | | ‘----------------+---> Note: Th e TOLERANCE keyword is u sed here t o distinguish between th e eccent ricity limit wh ich you h ave specified an d t he actual eccentricity derived from t he st ru ctu ral m odel. 2.2.3 Structural Joints The positional er rors for J oints a re m easur ed as divergences of the J oint positions from their owning Nodes. The maximum permissible errors are defined, a s for Sections, in ter ms of a J oint ’s e c c e n t r i c i t y . Note: J oint eccent ricities ar e defined separately for Pjoint (Prima ry J oint) and Sjoint (Secondary Joint) elements. Keywords: ECCENTRICITY PJOINT SJOINT Description: Th e ECCENTRICITY PJOINT an d ECCENTRICITY SJOINT commands specify th e maximu m per missible dista nce between th e position of a Pr imary J oint or a Secondar y J oint, respectively, and th at of its ownin g Node before a diagnostic message is outpu t. Examples: ECC PJOINT 1 (Default) Maximum error in P rimar y Joint position is 1 mm ECC SJOINT 1 (Default) Maximum error in Secondary Joint position is 1 mm ECC PJOIN 0.1 INCH Maximu m er ror in P rimar y J oint position is 0.1 inch 2-6 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking ECC PJOIN DEFAULT Resets perm issible Pr imary J oint err or t o 1 mm ECC SJOIN DEF Resets permissible Secondary Joint error to 1 mm C om m a n d S yn t a x : >--- ECCentricity ---+--- PJOInt ---. | | ‘--- SJOInt ---+--- ----. | | ‘--- DEFault ---+---> Querying: Q ECCentricity ---+--- PJOInt ---. | | ‘--- SJOInt ---+---> 2.2.4 Structural Fittings The positiona l errors for Fittings a re m easur ed as divergences of th e Fitt ing positions from t he N eutr al Points of the a tt ached Sections. The maximum perm issible err ors ar e defined, a s for S ections, in ter ms of a Fitt ing’s eccentricity . Keywords: ECCENTRICITY FITTING Description: Th e ECCENTRICITY FITTING command specifies the maximum perm issible distan ce between th e position of a F ittin g and t ha t of its at ta ched Section before a dia gnostic messa ge is outpu t. Examples: ECC FITTING 1 (Default) Maximum error in Fitting position is 1 mm ECC FITT 0.5 INCH Maximum err or in Fitt ing position is 0.5 inch ECC FITT DEF Resets perm issible Fitt ing position error t o 1 mm C om m a n d S yn t a x : >--- ECCentricity --- FITTing ---+--- ----. | | ‘--- DEFault ---+---> Querying: Q ECCentricity FITTing PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-7 Data Consistency Checking 2.3 Minimum Tube and Rod Lengths and Maximum Bend Angles Note: All references to pipe component s an d tu be in th is section app ly equally to han ger components an d r od. In order to warn you about potential problems in the practical assembly of pipework sections, th e dat a consist ency checks outpu t a diagnostic message if th e lengt h of tu be joinin g any pa ir of componen ts is less tha n a p rescribed minimum . The minimum allowed will norm ally be dependent upon th e tube diameter. An incorrectly positioned ATTA (off the implied tube) may also give rise to a ‘minim um tu be length ’ err or. You will also be warn ed if the design a ngle for a va riable-angle bend or elbow exceeds a prescribed maximum. 2.3.1 Specifying Minimum Lengths Irrespective of Bore Keywords: TOLERANCE TUBE Description: Th e TUBE comma nd, u sed alone, specifies the m inimu m a ccepta ble tu be lengt h wh ich is app licable to all tu be diameter s which h ave not been more specifically set. Examples: TOL TUBE 100 (Default) Minimum accepta ble length is 100 mm TOL TUBE DEFAULT Minimum accepta ble length is 100 mm TOL TUBE 6 INCH Minimu m a ccepta ble length is 6 inches C om m a n d S yn t a x : >-- TOLerance TUbe --+-- ---. | | ‘-- DEfault --+--> Querying: >-- Query TUbe --> >-- Query TOLerance OPTions --> (also outputs ATTACHECK an d misalignm ent sett ings; see Sections 2.1.2 an d 2.2.1, resp ectively) 2-8 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking 2.3.2 Specifying Bore-Dependent Minimum Lengths Keywords: TOLERANCE TUBE BORE MINIMUM Description: Th e TUBE BORE comma nd allows you to specify differen t min imum tu be lengt hs for differen t r an ges of bore diam eter. Ea ch r an ge of tu be size is specified by a m inimu m a nd m aximu m bore (not necessarily in th at order), followed by th e minimu m tu be length allowed for t ha t range. Up t o ten differen t r an ges may be specified. If a t ube diam eter falls out side any specified r an ge, then th e cur rent default length is applied (100 mm, un less t his ha s been overridden by prior use of the TUBE comman d). If two or m ore r an ges overlap, you a re war ned but th e ra nges are n ot rejected. Tube length checks ar e applied in the order in wh ich t hey ha ve been sp ecified. Thus , if the bore of a section of tu be lies within more th an one specified ran ge, its length will pass or fail the toleran ce test det ermined by th e first valid r an ge only. Examples: TOL TUBE BORE 15 25 MIN 150 All tubes with bores in t he r ange 15-25 mm m ust be at least 150 mm long TOL TU BO 25 15 150 The sam e as th e preceding examp le. The ma ximum bore is given before th e minimum bore a nd th e optional MINIMUM (length) comma nd word has been omitted. TOL TU BO 2 IN 4 IN MIN 12 IN All tu bes with bores in th e ran ge 2-4 inches mu st be at least 12 inches long INCH DIST TOL TU BO 2 4 MIN 12 The same as th e preceding example, except th at t he cur rent distance un its ar e now inches TOL TUBE DEFAULT Resets minimum length t o 100 mm for all bore sizes regar dless of an y ranges previously defined separately C o m p l e x E x a m p le : The following s equ ence: TOL TOL TOL TOL TUBE 500 TUBE BORE 15 25 MINIMUM 100 TU BO 25 50 MIN 150 BO 50 TU BO 200 400 750 100 MIN 300 would cau se subsequent checks to report tu be lengths less tha n t he permitt ed minim a in th e following circumst an ces: • For bores between 15 mm a nd 25 mm , if length is <100 mm PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-9 Data Consistency Checking • For bores between 25 mm a nd 50 mm , if length is <150 mm • For bores between 50 mm a nd 100 mm , if length is <300 mm • For bores between 200 mm a nd 400 mm , if length is <750 mm • For a ll oth er (un specified) ran ges, if length is <500 mm The latter case would apply to bores less than 15mm, greater t ha n 400mm, and within th e ran ge 100mm to 200mm. C om m a n d S yn t a x : .------------------------<------------------------. / | >-- TOLerance TUbe --*-- BOre --+-- MINimum --. | | | | | | ‘-------------+-- --| | | ‘-- DEfault ----------------------------------------+--> Querying: >-- Query TUbe --> >-- Query TOLerance OPTions --> (also out put s ATTACHECK an d misalignment sett ings) 2.3.3 Specifying Maximum Angles for Bends and Elbows Keywords: MAXANGLE Description: The design an gle for ea ch pu lled bend or elbow, tak en from th e settin g of its ANGL attribute, is checked against a predefined maximum an gle. A diagn ostic messa ge is out put if th e design an gle is too lar ge. The defau lt setting for th e maximum permitt ed an gle is 90°, but you ma y specify any limit with in th e ra nge 0° (i.e. str aight tu be only) to 180° (i.e. U-bend s a llowed). Examples: MAXANGLE 45 C om m a n d S yn t a x : >--- MAXANGLE --- value ---> Querying: Q MAXANGle 2-10 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking 2.4 Combined Pipework Tolerance and Tube Length Options Keywords: TOLERANCE OPTIONS DEFAULT Description: Th e OPTIONS comma nd a llows you t o reset defau lts for, or qu ery, all dat a cons istency checking options for Tu bes at t he sa me time. Examples: TOL OPTIONS DEFAULT Resets the following data-checking parameters: • Offset toleran ce to 1 m m • Angle tolerance to 0.0573 degrees • Rat io toleran ce to 0.001 • Maxan gle sett ing to 90 degrees • Minimum tu be length for a ll bores to 100 mm • ATTACHECK option t o ON C om m a n d S yn t a x : >-- TOLerance OPTions DEFault --> Querying: >-- Query TOLerance OPTions --> Outpu ts th e cur rent settings for all data checking param eters. The para meters are output in the curr ent units. Q u e r y i n g E x a m p l e s: With all defau lt sett ings in force, the outpu t r esultin g from a Q TOL OPT comman d will show one of th e following sets of values (depend ing u pon t he current units): M M Bo r e s a n d D is t a n c e s : Minimum tube length Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 : : : : : : 100 mm 1 mm 0.0573 0.001 90 ON 2-11 Data Consistency Checking I N CH B o r e s a n d D i s t a n c e s : Minimum tube length Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking : : : : : : 3.9 in 0 in 0.0573 0.001 90 ON F I N C H B o r e s a n d D is t a n c e s : Minimum tube length Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking 2.5 : : : : : : 3.15/16 0.1/32 0.0573 0.001 90 ON Specifying Minimum and Maximum Section Lengths The derived lengths of structural Sections are checked against predefined minimum an d ma ximum values and a diagnostic message is output if an actual length falls outside these limits. Keywords: SECTION DEFAULT RESET Description: Th e SECTION comm an d allows you t o specify minim um an d ma ximum accepta ble lengths for Sections. You ma y set a single ra nge of accepta ble length s for all unspecified types of Section by usin g th e SECTION DEFAULT option, or you m ay set different ranges for one or more specific types of Section (up to a maximum of ten nam ed types). The standa rd default ra nge of perm issible length s for all un specified t ypes of Section is from zero minimum t o 10000 mm maximum . Examples: SECTION DEFAULT 1000 9500 Length s of all types of Section mu st be in t he r an ge 1000–9500 mm u nless separ at ely specified by a SECT generic_type option (as illust ra ted in t he following exa mp les) SECT COLUMN 1500 7500 Column lengths mu st be in th e ra nge 1500–7500 mm ; lengths of other types of Section m ust be with in th e cur rent defau lt ra nge SECT BEAM 42 IN 9 FT Beam lengt hs m ust be in t he r an ge 42 inches to 9 feet; length s of other types of Section m ust be with in th e cur rent defau lt ra nge 2-12 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking SECT COLUMN 0 12500 BEAM 8750 1000 Column lengths must be in t he ra nge 0–12500 mm; Beam lengths mu st be in th e ra nge 1000–8750 mm; length s of all oth er t ypes of Section mu st be with in the cur rent default ran ge Note: As illustr ated in th e last example, you m ust always enter tw o values (a m inimum an d a maximum setting), even if one of th ese is a cur rent default valu e (0 mm , say). You ma y, however, enter th em in eith er order (i.e. minim um value first or maximu m value first). SECT DEF RESET Length s of all types of Section mu st be in t he r an ge 0–10000 mm u nless separ at ely specified by a SECT generic_type option (i.e. this comm an d r esets th e original default set tings) SECT COLUMN RESET Column lengths mu st be in th e ran ge 0–10000 mm; the cur rent settings for other t ypes of Section ar e not cha nged by this comm an d SECT COL RESET BEAM RESET Column a nd Beam lengths mu st be in the ra nge 0–10000 mm (Note th at t he RESE T comma nd word m ust be repea ted for ea ch type of Section) SECT RESET Lengths of all types of Section mu st be in t he r an ge 0–10000 mm (i.e. this resets the original default settings and cancels any individual settings for specific types of Section) C om m a n d S yn t a x : .---------------------------------------. / | >--- SECTion ---+---*--- DEFault ---. | | | | | | ‘--- word ------+--- --- ---| | | | | ‘--- RESet ---------------+---> ‘--- RESet ---> where word is an y valid Section GTYPE which conform s with th e Design DB. Querying: .----------. / | Q SECTion ---+---*--- word ---+---. | | |--- DEFault --------| | | ‘--------------------+---> Q u e r y i n g E x a m p l e s: Q SECT DEFAULT Gives settings for cur rent defau lt ra nge Q SECT BEAM Gives sett ings for Bea ms only PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-13 Data Consistency Checking 2.6 Q SECT BEAM STRU COL Gives settings for th e th ree n amed t ypes of Section Q SECT Gives settings for any specifically-defined types plus defau lt sett ings app licable to oth er Sections Specifying User-Defined SKEYs Acceptable in Data Checks The symbol used by ISODRAFT to repr esent a par ticular piping componen t on an isometr ic dra wing is determ ined by its s y m b o l k e y (SKEY att ribute sett ing). (See th e IS ODRAFT Reference Manual for a full explana tion of th is concept.) Keywords: TOLERANCE CATALOGUE SKEY Description: When a d at a consistency check is carr ied out , th e SKEY (if an y) for each componen t is checked to see if it is of a st an dar d t ype. This synt ax lets you specify user -defined SKE Ys so th at th ey do not genera te er rors du ring da ta consistency checks. Examples: TOL CATA SKEY ’JIM’ ’FRED’ ... Componen ts with th e us er -defined S KEYs ‘J IM’, ‘FRE D’ etc. will not generate errors caused by unrecognised SKEYs. C om m a n d S yn t a x : .--------. / | >-- TOLerance CATAlogue SKEY --*-- text --+--> (Note tha t text is case-sensitive; SKEYs ar e usu ally, but not n ecessar ily, uppercase chara cters.) Querying: >-- Query TOLerance CATAlogue SKEY --> Outpu ts cur rent list of user-defined SKEYs t o be ignored du ring da ta consistency checks. 2-14 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking 2.7 Diagnostic Messages from Data Consistency Checks When th e CHECK comma nd is given, DESIGN scans th e relevan t DBs t o extr act the a ppropriate Design an d Cata logue inform ation and carr ies out th e deta iled checking opera tions described in th e preceding sections. Whenever a design inconsist ency or er ror is foun d, a diagnostic message is out put to th e screen (REQUESTS r egion) or to a file. It is t hese m essages which ar e explained in th is section. Note: The diagnostic messa ges will often incorp orat e specific referen ces (nam e, referen ce nu mber et c.) to the element s found t o be in error (although t he tr ue err ors m ay be due to adjacent elements). These specific referen ces ha ve genera lly been omitt ed from th e examp le messa ges listed in t he following subsections. If th e checking procedur es ar e completed with out an y errors being detected, the message *--* NO DATA INCONSISTENCIES *--* will be out put . 2.7.1 Global Diagnostics R 10 BAD OWNER REFERENCE The owner reference refers eith er t o a n onexisten t element or to one which does not cont ain t he r equired element in its list par t. The occur ren ce of th is error implies th at corr upt ion of one or m ore DBs h as t aken place. 2.7.2 Branch-Specific Diagnostics Branch Head Errors The following diagn ostics a pply only to th e Hea d of a Bra nch: A 10 HEAD REFERENCE NOT SET The H ead r eferen ce should only be un set (i.e. nu ll) if th e Hea d Connection Type HCONN is set to OPE N, VENT, CLOS or DRAN. A 20 HEAD REFERENCE POINTS TO NONEXISTENT ELEMENT This err or would r esult from th e deletion of a componen t, such a s a N ozzle, to which th e Head of the Bra nch was originally connected. A 30 BAD HEAD RETURN REFERENCE The Hea d is connected to an element which does not refer back to the Bra nch. This can occur when t he H ead of a Br an ch is conn ected t o another Bran ch, implying th at a Tee should be placed somewh ere along the second Br an ch. The PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-15 Data Consistency Checking error can also occur when two or more branches are inadvertently connected to the same t erminal. A100 HEAD TERMINAL PROBLEM WITH SPREF Either the Head t erminal has an unset SPREF or th e SPREF points to a nonexistent SPCOM. A110 HEAD TERMINAL PROBLEM WITH CATREF Either t he Head t ermina l has an un set CATREF or t he CATREF points to a nonexistent Catalogue component. A120 HEAD TERMINAL PROBLEM IN ACCESSING P-POINTS Ther e is a Ca ta logue problem in accessing th e p-point s of th e Head t erm inal. A130 HEAD TERMINAL PROBLEM, P-POINT NO.n DOES NOT EXIST A requ ired p-point of the Hea d ter min al does not exist in th e set of p-point s. A200 DIRECTION HDIR NOT SAME AS TERMINAL DIRECTION If th e Head is conn ected t o a t erm inal, such as a Nozzle or Tee, then th e direction H DIR should always be identical to th at of th e appr opr iate p-point of the term inal. A210 POSITION HPOS NOT SAME AS TERMINAL POSITION If th e Head is conn ected t o a t erm inal, such as a Nozzle or Tee, then th e position HP OS should always be identical to th at of th e appr opriate p-point of the term inal. A220 HBORE NOT SAME AS TERMINAL BORE If th e Head is conn ected t o a t erm ina l, such a s a Nozzle or Tee, then t he bore HBORE sh ould always be ident ical to tha t of th e appr opriate p-point of th e terminal. A230 CONNECTION TYPE HCONN NOT SAME AS TERMINAL CONNECTION TYPE If th e Head is conn ected t o a t erm inal, such as a Nozzle or Tee, then th e connection type HCONN should always be identical to that of the appropriate p-point of the terminal. A300 REFERENCE HSTUBE UNSET There is more th an 1mm of tu be between th e Head an d th e p-arr ive of th e first Component (or t he Tail), but HSTUBE is u nset. A310 REFERENCE HSTUBE REFERS TO A NONEXISTENT SPCOM This m ay occur if par t of the S pecificat ion h as been deleted. A320 HSTUBE PROBLEM, CATREF IN SPCOM IS UNSET This indicates an err or in th e Specificat ion. A330 HSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NONEXISTENT Catalogue COMPONENT This ma y occur if par t of th e Cat alogue h as been d eleted or if the CATREF is unset. 2-16 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking A340 HSTUBE PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SET TO TUBE The componen t pointed t o by HSTUBE is n ot of type TUBE in t he Cat alogue. A350 HSTUBE PROBLEM IN ACCESSING P-POINT There is a Ca ta logue problem in accessing a p-point of the tu be pointed t o by HSTUBE. A400 HBORE NOT SAME AS BORE OF HSTUBE The bore of any tube leading from the Head, determined from the Catalogue, should always be ident ical to HBORE. A410 HCON NOT COMPATIBLE WITH CONNECTION TYPE OF HSTUBE The connection t ype of an y tube leading from t he H ead, deter mined from th e Cat alogue, should be compat ible with HCONN . A420 ISPEC REFERENCE POINTS TO NONEXISTENT ELEMENT This er ror would occur if, for examp le, the In sula tion Specificat ion point ed to by ISPEC ha d been deleted. A430 INSULATION CANNOT BE SELECTED USING HBORE Ther e is no suita ble insu lation in th e Cata logue for the combina tion of temperature TEMP a nd bore HBORE. Branch Tail Errors The following diagn ostics apply only to th e Tail of a Bra nch: B 10 TAIL REFERENCE NOT SET The Ta il referen ce sh ould only be un set (i.e. zero) if the Ta il connection type TCONN is set to OPEN , VENT, CLOS or DRAN. B 20 TAIL REFERENCE POINTS TO NONEXISTENT ELEMENT This err or would r esult from th e deletion of a componen t, such a s a N ozzle, to which t he Ta il of the Br an ch wa s origina lly connected. B 30 BAD TAIL RETURN REFERENCE The Tail is connected to an elemen t wh ich does not r efer ba ck t o the Bra nch. This can occur when t he Tail of a Br an ch is conn ected t o an other Br an ch, implying th at a Tee should be placed somewh ere along the second Br an ch. The error can also occur when two or more branches are inadvertently connected to the same t erminal. B100 TAIL TERMINAL PROBLEM WITH SPREF Either th e Tail terminal has an unset SPREF or t he SPREF points to a nonexistent SPCOM. B110 TAIL TERMINAL PROBLEM WITH CATREF Either t he Tail terminal has an un set CATREF or the CATREF point s to a nonexistent Catalogue component. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-17 Data Consistency Checking B120 TAIL TERMINAL PROBLEM IN ACCESSING P-POINTS Ther e is a Cata logue pr oblem in a ccessing th e Tail p-point s. B130 TAIL TERMINAL PROBLEM, P-POINT NO.n DOES NOT EXIST A requ ired p-point of th e Tail term inal does not exist. B200 DIRECTION TDIR NOT SAME AS TERMINAL DIRECTION If the Tail is connected to a ter mina l, such a s a N ozzle or Tee, then th e direction TDIR sh ould always be identical to th at of th e appr opriate p-point of the term inal. B210 POSITION TPOS NOT SAME AS TERMINAL POSITION If the Tail is connected to a ter mina l, such a s a N ozzle or Tee, then th e position TPOS sh ould always be ident ical to tha t of th e appr opr iate p-point of th e terminal. B220 TBORE NOT SAME AS TERMINAL BORE If the Tail is connected to a ter mina l, such a s a N ozzle or Tee, th en t he bore TBORE should always be identical to th at of th e appr opriate p-point of th e terminal. B230 CONNECTION TYPE TCONN NOT SAME AS TERMINAL CONNECTION TYPE If the Tail is connected to a ter mina l, such a s a N ozzle or Tee, then th e connection t ype TCONN sh ould alwa ys be identical to th at of th e appr opriate p-point of the terminal. Plain Branch Errors The following diagn ostics can occur only for Br an ches with no piping components: C500 TUBE TOO SHORT BETWEEN HEAD AND TAIL The distance between the Head position, HPOS, and the Tail position, TPOS, is great er th an zero and less tha n t he specified minimu m tu be length (defau lt: 100mm). C510 BAD HEAD TO TAIL GEOMETRY Eith er t he Hea d position, HP OS, does not lie at a positive distan ce along the line t hr ough TPOS in t he dir ection TDIR or t he Tail position, TPOS, does not lie at a positive distan ce along th e line th rough H POS in t he direction H DIR. The following illust ra tion sh ows some t ypical exam ples: 2-18 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking C520 HBORE NOT SAME AS TBORE When th ere ar e no components on t he bra nch, the H ead bore, HBORE, should be identical to th e Tail bore, TBORE. C530 HCONN IS NOT COMPATIBLE WITH TCONN This implies tha t t he H ead is conn ected dir ectly to the Ta il with n o Tube or piping componen ts in between; hence the H ead conn ection type, HCONN, mu st be compa tible with th e Tail connection t ype, TCONN. C540 THIS BRANCH HAS NO COMPONENTS This does not necessarily indicate a n er ror. It is merely out put as a warn ing to the designer. 2.7.3 Component-Specific Diagnostics The following err ors ap ply to ind ividua l piping component s an d, in some cases, to th eir adjacent conn ections. Some of th e err ors also apply to han ger componen ts an d/or to Nozzles. All-Component Diagnostics These ar e applicable to any componen t, regar dless of its position in th e network: D100 REFERENCE SPREF UNSET This probably mean s th at the designer h as forgotten to select t he piping component. D110 REFERENCE SPREF REFERS TO A NON-EXISTENT SPCOM This m ay occur if par t of the s pecificat ion ha s been deleted. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-19 Data Consistency Checking D120 SPREF PROBLEM, CATREF IN SPCOM IS UNSET This indicates an err or in th e Specificat ion. D130 SPREF PROBLEM, CATREF IN THE SPCOM REFERS TO NON-EXISTENT CATALOGUE COMPONENT This ma y occur if par t of th e Cat alogue h as been d eleted or if the CATREF in the SPCOM is unset . D130 SPREF PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SAME AS TYPE OF DESIGN DATA COMP0NENT The GTYPE of the Cat alogue component must be th e same as t he t ype of the piping Component in th e design dat a. D150 CATREF PROBLEM IN ACCESSING P-POINTS An er ror h as been found in accessing th e p-points of the Cat alogue componen t point ed t o by CATREF. D160 REFERENCE CATREF UNSET This ap plies only to Nozzles, for which th e CATREF m us t be set . D170 REFERENCE CATREF REFERS TO A NON-EXISTENT CATALOGUE COMPONENT This ma y occur if par t of th e Cata logue ha s been deleted. It a pplies only to Nozzles. D200 ARRIVE P-POINT NOT IN PTSET OF CATALOGUE COMPONENT The ar rive p-point n umber does not exist in th e PTSET of th e Cata logue Component. D210 LEAVE P-POINT NOT IN PTSET OF CATALOGUE COMPONENT The leave p-point nu mber d oes not exist in t he P TSET of th e Cata logue Component. D300 REFERENCE CREF NOT SET Multi-way Componen ts ma y be left u nconn ected only if the conn ection type of th e relevant p-point is OP EN, CLOS, VENT, DRAN or NULL. D310 REFERENCE CREF POINTS TO NON-EXISTENT BRANCH This ma y occur if th e Bran ch wh ich is pointed t o by the CREF ha s been deleted. D320 BAD CREF RETURN REFERENCE This ma y occur if th e Bran ch wh ich is pointed t o by the CREF ha s been reconn ected t o another term inal. D330 2-20 REFERENCE CRFA n NOT SET An en tr y in th e conn ection reference arr ay ma y only remain un set if the correspondin g p-point in t he Ca ta logue does not exist or if th e connection t ype of th e correspondin g point is VENT, OPE N, CLOS or N ULL. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking D340 REFERENCE CRFA n POINTS TO NON-EXISTENT BRANCH This ma y occur if the Bra nch pointed t o by the n th reference in t he conn ection reference arr ay ha s been deleted. D350 BAD CRFA n RETURN REFERENCE This ma y occur if th e elemen t pointed t o by the n th reference in t he conn ection reference arr ay ha s been reconn ected to a t hird Br anch. D400 ARRIVE TUBE [ROD] LESS THAN TUBE [ROD] MINIMUM. ACTUAL TUBE [ROD] LENGTH IS ... The dista nce between t he ar rive p-point of th is componen t a nd t he leave ppoint of the previous component (or Head) is greater th an zero an d less th an th e specified minimu m t ube [rod] length (defau lt: 100mm ). D410 BAD ARRIVE GEOMETRY + details of geometric errors The position a nd direction of the a rr ive p-point of th is component ar e not correct with respect t o the leave p-point of th e previous component (or H ead). The er ror could be cau sed by incorr ect p ositioning of th is component , th e previous component (or H ead) or both . The following illust ra tion sh ows some t ypical exam ples: D420 BAD ARRIVE BORE [ROD DIAMETER] The bore of th e ar rive p-point of th is component is not equa l to the bore of th e preceding tu be or, if this componen t is n ot preceded by tube, to th e bore of th e leave p-point of th e pr evious componen t (or HBORE ). D430 BAD ARRIVE CONNECTION TYPE The conn ection t ype of the a rr ive p-point of th is component is not compa tible with t he pr eceding tu be or, if th is componen t is not pr eceded by tube, to th e connection type of the leave p-point of th e pr evious componen t (or HCONN ). PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-21 Data Consistency Checking D500 REFERENCE LSTUBE [LSROD] UNSET The user ha s probably forgotten to select t he piping/ha nger Component . D510 REFERENCE LSTUBE [LSROD] REFERS TO A NON-EXISTENT SPCOM This m ay occur if par t of the S pecificat ion h as been deleted. D520 LSTUBE [LSROD] PROBLEM, CATREF IN SPCOM IS UNSET This indicates an err or in th e Specificat ion. D530 LSTUBE PROBLEM, CATREF IN THE SPCOM REFERS TO NON-EXISTENT CATALOGUE COMPONENT This ma y occur if par t of th e Cat alogue h as been d eleted or if the CATREF in the SPCOM is unset . D540 LSTUBE PROBLEM, GTYPE OF CATALOGUE COMPONENT IS NOT SET TO TUBE The componen t pointed t o by LSTUBE is not of type TUBE in t he Cat alogue. D550 LSTUBE [LSROD] PROBLEM IN ACCESSING PPOINTS Ther e is a Cat alogue pr oblem in a ccessing a p-point of th e tu be/rod point ed to by LSTUBE [LSROD]. D600 LEAVE BORE [DIAMETER] NOT SAME AS BORE [DIAMETER] OF LSTUBE [LSROD] The bore of th e leave p-point of th is Componen t is n ot th e sam e as t he bore of th e tu be/rod following th e Componen t. D610 LEAVE CONNECTION TYPE NOT COMPATIBLE WITH CONNECTION TYPE OF LSTUBE [LSROD] The conn ection t ype of the leave p-point of th is Componen t is n ot compat ible with t he t ube/rod following th e component . D620 INSULATION CANNOT BE SELECTED USING LEAVE BORE Ther e is no suita ble insu lation in th e Cata logue for th e combinat ion of tempera tu re TEMP and th e bore of th e leave p-point. D630 ATTACHMENT TYPE INVALID - MUST BE ONE OF FLOW, XXXX, SSSS, CCCC, CCNN, NUL OR NULL You ha ve set an incorr ect TYPE at tr ibute for a n ATTA. D740 ANGLE OF COMPONENT IS GREATER THAN MAXIMUM ANGLE SPECIFIED IN SPREF The designed a ngle of a Pu lled Bend, E lbow or Weld is great er t ha n is a llowed by th e SPECs. D740 ANGLE OF COMPONENT IS LESS THAN MINIMUM ANGLE SPECIFIED IN SPREF The designed a ngle of a Pu lled Bend, E lbow or Weld is less th an is allowed by the SPECs. 2-22 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking D740 ANGLE GREATER THAN m DEGREES. ACTUAL ANGLE IS n. The designed an gle of a Pu lled Bend or E lbow is greater t ha n t he ma ximu m an gle specified by th e user (see TOLERANCE MAXANGLE ). End-Component Diagnostics These ar e applicable only to the last componen t in a Br an ch: E700 LEAVE TUBE LESS THAN TUBE MINIMUM. ACTUAL TUBE LENGTH IS ... The distance between the leave p-point of th e cur rent component a nd t he ta il position, TPOS, is greater th an zero and less th an th e specified minimum t ube length (defau lt: 100mm). E710 BAD LEAVE GEOMETRY The position a nd direction of the leave p-point of th is componen t a re n ot correct with resp ect t o the position, TPOS, a nd direction, TDIR, of the t ail. The er ror could be cau sed by incorr ect p ositioning of th is componen t, t he Ta il, or both . E720 LEAVE BORE NOT SAME AS TBORE The bore of the leave p-point of th is componen t is not t he sa me a s th e ta il bore, TBORE. E730 LEAVE CONNECTION TYPE NOT COMPATIBLE WITH TCONN The conn ection t ype of th e leave p-point of th is componen t is not compat ible with t he t ail connection t ype TCONN. 2.7.4 Structure-Specific Diagnostics The following abbreviat ions a re u sed th roughout th is section to represen t specific identifiers with in th e out pu t m essages: struc_elem A nam ed st ru ctu ra l elemen t (a specific Section, J oint , or Fitting) word A qua lifying PDMS word; usu ally an a tt ribut e of a str uctura l element in the curren t cont ext Catalogue/Connectivity Errors SC010 Catref/Specref of struc_elem unset The SPREF for t he n amed st ru ctu ral Section, J oint or F itting does not point to a valid componen t in t he Cat alogue. SC020 Pline word of struc_elem does not exist The p-line of th e given n am e can not be accessed in t he Ca ta logue description of th e elemen t. Eith er th is p-line does not exist in t he Cat alogue description or the st ru ctu ral element points to th e wrong Cata logue element. SC030 POSL of struc_elem unset The Positioning Line (POSL) attribute has not been set in the Design DB. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-23 Data Consistency Checking SC040 POSL of struc_elem_1 refers to non existent Pline in struc_elem_2 The Positioning Line within the named Secondary Joint or Fitting does not refer t o a valid p-line in th e owning Section. SC050 Incompatible Connection types between struc_elem_1 and struc_elem_2 Self-explanatory. SC060 Incompatible Connection references between struc_elem_1 and struc_elem_2 Self-explanatory. SC070 struc_elem is not connected Self-explanatory. SC080 Incompatible GTYPE of struc_elem : word_1 in Design, word_2 in Catalogue The Gener ic Type used to classify th e str uctu ra l element in th e Design DB is not th e same as t ha t u sed in the r eferenced Cata logue description. SC090 Jline of struc_elem unset The nam ed stru ctu ra l element does not h ave its J oining Line att ribute set, so its position a nd/or orient at ion with respect to a conn ected componen t can not be defined. SC100 INCOMPATIBLE ROD DIAMETER BETWEEN name AND name FOR HANGER HEAD AND TAIL The Fitting an d th e Atta between wh ich t he h an ger is to be conn ected h ave incompatible diameters. SC110 TBORE [HBORE] NOT SAME AS BORE OF name The Head/Tail diameter of th e han ger is not t he sam e as th at of the Fitting to which it is to be conn ected. SC120 Catref/Specref of struc_elem refers to a non-existent element The SPREF for t he n amed st ru ctu ral Section, J oint or F itting does not point to a valid componen t in t he Cat alogue. Positional Errors SP010 Discrepancy between ends of Jlines: word of struc_elem_1 and word of struc_elem_2 The sta rt /end of th e J oining Line for th e na med Section does not ha ve the same point locat ion as t he end of the J oining Line for th e na med J oint. SP020 Positions of struc_elem_1 and struc_elem_2 misaligned Self-explanatory. SP030 struc_elem_1 lies off the beginning or end of owning Section struc_elem_2 The nam ed J oint or Fitting, which a re mean t t o be conn ected to the n am ed Section, is not positioned with in t he der ived length of th e Section. 2-24 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking Directional Errors SD010 Normal to Cutting plane word of struc_elem_1 is perpendicular to Neutral axis of struc_elem_2 This is equivalent to saying tha t t he end-cut ting plane of a Section th rough th e point of connection is effectively para llel to th e neu tr al a xis of tha t Section. This is not possible, since the in ter section point needed t o define th e position of th e connection would th en be at infinity. SD020 Normal to Cutting plane word of struc_elem_1 is perpendicular to Origin plane of struc_elem_2 This is equivalent to saying tha t t he end-cut ting plane of a Section th rough th e point of connection is effectively parallel to the origin plane of that Section. This is not possible, since the in ter section point needed t o define th e position of th e connection would th en be at infinity. SD030 Cutting planes word of struc_elem_1 and word of struc_elem_2 misaligned The star t an d end cut ting planes of th e named elements ar e not par allel. SD040 Check Beta angles of struc_elem_1 and struc_elem_2 The Beta Angle for t he n am ed Section should be the sa me as t he Beta Angle for t he conn ected J oint . SD060 Normal to cutting plane word of struc_elem not in general direction of other end of section The star t a nd end cut ting plane normals should point in t he general direction of the oth er en d of th e Section. Eccentricity Errors SE010 Struc_elem diverges from logical model: eccentricity out of range The linear displacement between t he Attached Neutr al Point s on th e extended Neut ra l Axis of the n am ed Section an d th e logical line joining th e Node positions exceeds the permitted distance. SE020 Struc_elem diverges from logical model: angle out of range The angular deviation between th e Neutr al axis of th e nam ed Section a nd t he logical line joining t he N ode positions exceeds th e perm itted am ount . Length Errors SL010 Length of struc_elem is out of range. Actual length is ... The derived length of the na med Section is not within t he perm issible range applicable to its type. SL020 Logical length of struc_elem is zero Self-explanatory. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-25 3 Clash Detection DESIGN’s clash detection ut ility a llows you t o check a ny s pecified par ts of th e Design database for clashes (interferences) between individual elements and to report on th e results. The t ypes of clash ident ified by DESIGN depend on two factors: • Th e o b s t r u c t i o n le v e ls of th e clash ing elemen ts • The cur rent t o u c h a n d c l e a r a n c e tolerances 1. O b s t r u c t i o n Le v e ls All design pr imitives and a ll cat alogue pr imitives have an obstru ction level att ribut e (OBST) which ha s an integer va lue of 2, 1 or 0. The value of th e OBST att ribut e defines th e physical type of obstr uction wh ich t he primitive represents. For positive pr imitives th e effects ar e a s follows: OBST = 2 A h a r d o b s t r u c t i on ; the pr imitive repr esents a solid volume, such as a steel beam or a plan t vessel, which has rigid an d impenetr able surfaces. OBST = 1 A s o ft o b s t r u c t i o n ; the pr imitive represents a volume which is not solid bu t wh ich n eeds to be kept clear for access pur poses, such a s an operat ing space aroun d th e cont rol wheel of a valve. O BS T = 0 N o o b st r u c t io n ; the pr imitive represent s a freely accessible volum e, or is simply a r epresen ta tive symbol. In addition to the obstru ction types defined by the OBST at tr ibutes, Insu lation is treat ed as a special obstru ction t ype in its own right. 2. Exten t of Clashing As well as r ecognising t he t hr ee types of clash ing item (har d, soft an d insu lation), DESIGN recognises th ree class es of clash between t hem , depending upon th e degree to which th e two primitives intr ude u pon each other’s allocated space. These classes are as follows: • (normal) c l a s h ; th e primitive volumes overlap by more tha n a specified am oun t. • A t o u c h ; th e primitives either overlap by less tha n a specified amount or ar e separat ed at t heir closest point by less tha n a specified distance. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-1 Clash Detection • A c l e a r a n c e ; the primitives ar e separa ted at their closest point by more tha n th e amount n ecessary to constitu te a touch but less than a specified clear an ce dista nce. These th ree classes a re illustr at ed in Figur e 3-1 for th e clash specificat ions: Touch limits: 5 mm overlap to 2 mm gap Clear an ce limit: 8 mm so tha t t he following criter ia ap ply: • If the pr imitives overlap by m ore t han 5 mm , a clash is report ed • If the pr imitives overlap by less th an 5 mm , a t ouch is reported • If the primitives do not overlap bu t a re separa ted by less tha n 2 m m, a touch is reported • If th e primitives are separa ted by more th an 2 mm but less tha n 8 mm , a clear an ce is report ed • If the primitives ar e separa ted by more tha n 8m m, no interference is found N O T E : The clear an ce dista nce, if set, m u s t be great er tha n th e touch gap. Sett ing th e cleara nce distan ce to zero switches off the clear an cechecking function. overlap > 5mm A Clash Figur e 3-1 3. overlap < 5mm gap < 2mm Touches 2mm < gap < 8mm A Clearance Clash es, Touches an d Cleara nces T h e C la s h D e t e c t i o n P r o c e s s The locat ions an d dimen sions of all design element s ar e defined, for clash detection pur poses, by reference to a s p a t i a l m a p which holds simplified descriptions of th e componen t geometr ies (see Section 5.7 in P ar t 1). Ea ch elemen t wh ich is to be checked for clashes h as its own geometr y checked a gainst th at of all oth er element s which ar e specified by a current o b s t r u c t i o n li s t . Items which a re n ot in t he obstruction list ar e ignored du rin g the clash checking opera tions. 3-2 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.1 Entering Clash Detection Mode Keywords: DESCLASH EXIT Description: Th e DESCLASH comman d pu ts you into Clash Det ection mode. While in Clash Det ection mode, all comman ds which you ent er ar e inter pret ed as being specific to the clash checking an d report ing fun ctions, ra th er th an as general Design mode comma nds. To ret ur n from Clash Detection m ode to Design mode, use th e EXIT command. Note: 3.2 All clash -detection option s ett ings ar e stored globally, so tha t t hey rem ain in effect from one DESCLASH session to anoth er. Once defined, you n eed not resp ecify any of th e option sett ings un less you wish t o chan ge them (or u nless you leave and th en ret ur n t o DESIGN). Defining the Obstruction List Keywords: OBSTRUCTION EXCLUDE REMOVE Description: The list of obstr uctions, defining th ose items in t he spa tial ma p again st wh ich clash es ar e to be checked, may be built u p in sta ges. You may ad d items t o, or remove item s from, th e cur ren t list in an y of th e following wa ys: • By addin g one or more specified Design elements • By adding implied tube or r od between piping or str uctura l components • By excluding one or more member s owned by element s in th e list • By removing items from th e cur ren t obstru ction list an d/or from th e cur ren t exclusion list Note that th e cur rent obstru ctions a nd exclusions a re stored as t wo separa te lists, the effective obstru ction list being th e differen ce between the two. The OBSTRUCTION an d EXCLUDE comma nds add specified items t o those lists, bu t do not overwrite a ny existing conten ts. To remove item s from th e obstr uction a nd/or exclusion lists, you m ust do so explicitly and sepa ra tely for each list by u sing th e REMOVE command. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-3 Clash Detection When you add any element to the obstru ction list, all elements and prim itives below the specified item (tha t is, all of its m embers ) are au tomat ically incorpora ted int o th e list. By defau lt, the obstr uction list cont ain s all design elements in th e cur rent MDB. If a Bra nch (or h igher) element is added t o th e obstr uction list, implied tu be with in th e Branch is trea ted as pa rt of th e obstru ction. If, however, individua l piping componen ts a re a dded to th e list, implied tu be connected to those components is n ot included au toma tically and mu st be a dded specifically if requ ired. The sa me pr inciples apply to implied rod, an d also to implied tube or rod with in Groups. Only items which ha ve previously been ad ded to th e obstr uction or exclusion lists may be specified in a REMOVE comman d. Removing an obstr uction d oes n ot au tomat ically remove any exclusions which were specified when t ha t obstru ction was a dded to th e list. Examples: OBST ALL Adds every item from every Design DB in cur ren t MDB t o obstr uction list (default) OBST /PUMP1 /PUMP2 /VESS1 Adds individua lly ident ified elemen ts t o obstr uction list. OBST /GROUP.MOD2 Adds all element s in na med group t o obstr uction list. OBST LEAVE TUBE FROM /FLAN2 OBST HEAD ROD OF /HANG1 OBST LEAVE /VALV3 IARRIVE /VALV5 TAIL /BRAN1 Adds ind ividu al length s of implied tube or r od to obstr uction list. EXCL /BRAN3 /BRAN5 Excludes in dividu ally ident ified element s from cur ren t obstr uction list (by add ing th em t o exclusion list). Note: The nam ed elements m ust be members of items already in the obstr uction list. EXCL LEAVE TUBE FROM /FLAN2 EXCL HEAD ROD OF /HANG1 EXCL LEAVE /VALV3 IARRIVE /VALV5 TAIL /BRAN1 Exclud es individu al length s of implied tube or r od from curr ent obstru ction list. REM OBST ALL Empties obstruction list. REM OBST /PUMP2 /VESS1 Removes individua lly identified element s from obstru ction list. REM OBST LEAVE TUBE FROM /FLAN2 REM OBST HEAD ROD OF /HANG1 REM OBST LEAVE /VALV3 IARRIVE /VALV5 TAIL /BRAN1 Removes individual lengt hs of implied tu be or rod from obstr uction list. 3-4 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection REM EXCL ALL Em pties exclusion list. REM EXCL /BRAN3 /BRAN5 Removes in dividua lly ident ified element s from exclusion list. REM EXCL LEAVE TUBE FROM /FLAN2 REM EXCL HEAD ROD OF /HANG1 REM EXCL LEAVE /VALV3 IARRIVE /VALV5 TAIL /BRAN1 Removes individua l length s of implied t ube or rod from exclusion list. C om m a n d S yn t a x : .-----<------. / | >---+--- OBStruction ---+---*--- ---+---. | | | | ‘--- ALL --------------| | | | .-----<------. | | / | | ‘--- EXClude -----------*--- ---+---+---> >--- REMove ---+--- OBStruction ---. .-----<------. | | / | ‘--- EXClusion -----+---*--- ---+---. | | ‘--- ALL --------------+---> where (clash ing item identifier) is >---+--- ILEAve ---. | | |--- IARRIVE --| | | |--- HEAD -----| | | |--- TAIL -----+--- TUBe ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘----------------------------------------+--- ---> Querying: Q CLASH OBStruction Lists cur rent obstru ction list. Q CLASH EXClusion Lists curr ent exclusion list. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-5 Clash Detection 3.3 Defining the Region of Interest Keywords: LIMITS AUTOLIMITS Description: By defau lt, all par ts of th e design model relevant to the curr ent obstr uction list will be checked for inter feren ces dur ing subsequ ent clash -checking ru ns. If you d o not wa nt to check th e ent ire design, you may define a restricted region of interest represented by a 3 D l im i t s b ox. For a clash t o be report ed, both items involved in th e clash m ust lie wholly or p ar tly within th e limits box. A clash between item s which lie par tially with in th e limits box will always be reported, even if th e point at which th e clash occur s lies out side th e box. You ma y set u p a limits box in one of two ways: • E x p l i c i t l y , using the LIMITS comman d, by defining t he p ositions of two diam etr ically opposed corn ers (either as explicit coordinat es or a s t he origins of specified element s). • I m p l i c i t l y , using the AUTOLIMITS command, by identifying one or more element s an d allowing DESIGN to calculate th e appr opriate box which includ es th em. The limits box is calculat ed so as t o include the whole of each na med element ; it is not deter mined by th e origins of th e elemen ts. Examples: LIMITS N2560 E12150 U2150 TO S6530 W2135 U4200 Sets corners of box to explicit coordinates. LIMITS /STR6 TO /PUMP1 Sets corner s of box to origins of na med elements . LIMITS S0 E1300 U0 FROM /NOZZ3 TO N650 E175 D50 FROM /VESS2 Sets corner s of box to point s r eferen ced from origins of na med elemen ts. AUTO /PUMP1 /PUMP2 /VESS2 Calculat es box enclosing na med element s. AUTO /GROUP1 Calculat es box enclosing all element s in n am ed group. AUTO HEAD OF /BRAN1-2 TAIL OF /BRAN3-1 AUTO /VESS1 /VESS2 LEAVE TUBE FROM /FLAN2 Calculates box enclosing na med element s an d implied tube or rod. LIMITS NONE Removes any curr ent limits box, th us restoring defau lt sta te in which whole design model is checked. 3-6 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om m a n d S yn t a x : >---+--- LIMits ---. | | | +--- NONe ------------------------. | | | | ‘--- --- TO --- ---| | | | .-----<------. | | / | | ‘--- AUTOlimits ---*--- ---+--------------+---> where (clash ing item identifier) is >---+--- ILEAve ---. | | |--- IARRIVE --| | | |--- HEAD -----| | | |--- TAIL -----+--- TUBe ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘----------------------------------------+--- ---> an d (absolute/relative position) is >---+--- ---+--- FROM --- ---. | | | | ‘----------------------| | | ‘--- --------------------------+---> Querying: Q CLASH LIMits Gives coordina tes for curr ent limits box. Q VOLume element_id(s) Gives coordin at es for limits box enclosing specified design item (s). Q WINdow TO Gives n am es of all element s with in limits box specified by th e two positions; for example: Q WIN N2560 E12150 U2150 TO S6530 W2135 U4200 Q WIN /STR6 TO /PUMP1 Q WIN S0 E1300 U0 FROM /NOZZ3 TO N650 E175 D50 FROM /VESS2 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-7 Clash Detection 3.4 Defining Touches and Clearances Keywords: TOUCHING CLEARANCE Description: These comman ds jointly define th e tolera nces which det erm ine whether an y given clash is r eport ed as a clash , a t ouch or a clear an ce (see Figur e 3-1). DESIGN report s a t o u c h if two primit ives either : • Overlap by less tha n a specified t o u c h o v e r l a p distance • Are sepa ra ted by less tha n a sp ecified t o u c h g a p distance The touch overlap sett ing mu st be positive: th e touch gap mu st be positive an d less th an the curr ent sett ing for t he cleara nce distance. The default settings ar e for a t ouch overlap of 2mm an d a t ouch gap of zero. DESIGN reports a c l e a r a n c e if two primitive volumes a re sepa ra ted at their closest point by more th an th e cur rent ly defined touch gap bu t by less t ha n a specified c le a r a n c e d i s t a n c e . The cleara nce distan ce must be positive an d greater th an t he cur rent setting for th e touch gap. By defau lt th e clearan ce distance is undefined, so that no clearances will be found. DESIGN reports a c l a s h if two primitives overlap by more th an th e touch overlap d istan ce. Examples: TOUCH OVER 3 Sets touch overlap; cur rent un its assum ed to be mm. TOUCH OVER 0.2 INCH Sets t ouch overlap in specified un its. TOUCH OVER OFF Effectively sets touch overlap to zero. TOUCH GAP 2 Sets touch gap; cur rent un its assum ed to be mm. TOUCH GAP 0 Resets t he t ouch gap t o its default value. TOUCH GAP OFF Effectively sets touch gap to zero. CLEARANCE 10 Sets clearan ce; cur rent un its assum ed to be mm. CLEARANCE 0.25 INCH Sets cleara nce in specified un its. CLEARANCE 0 CLEARANCE OFF 3-8 Unsets clearan ce distan ce (defau lt sta te) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om m a n d S yn t a x : >---+--- TOUching ---+--- GAP -------. | | | | |--- OVErlap ---| | | | | ‘---------------+ | | | | ‘--- CLEarance ------------------+--- ---. | | ‘--- OFF ------+---> Querying: Q CLASH TOUching OVErlap Q CLASH TOUching GAP Q CLASH TOUching Q CLASH CLEarance 3.5 Ignoring Clashes Within Specified Element Types Keywords: NOCHECK WITHIN Description: By defau lt, no checks ar e ma de for clash es between item s owned by the sam e Stru ctu re, Substru ctu re, or Equipmen t. In addition, you ma y use the NOCHECK an d WITHIN comm an ds to tell DESIGN t o ignore all clash es with in one or m ore oth er s pecific types of elemen t. All clashes below each element of the specified types will be ignored dur ing th e checking opera tion, what ever th e hiera rchic level of th e clash ing items. Clashes specified in th is way are ignored dur ing th e actua l clash -checking opera tion an d ar e not th erefore ava ilable in memory for inclusion in su bsequent outpu t reports. Examples: NOCHECK WITHIN BRAN Ignores clashes within individual Branches (but still reports clashes between items in different Branches). NOCHECK FRMW Ignores clashes within individual F ram eworks (but still report s clashes between items in different Fr ameworks). WITHIN FRMW Restores clash checking with in Fr am ework s; tha t is, it cancels a pr evious NOCHECK F RMW comm and. WITHIN EQUI Restores clash checking within individua l item s of Equ ipment (which ar e not checked by default ). PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-9 Clash Detection C om m a n d S yn t a x : >---+--- NOCheck ---+--- WIThin ---. | | | | ‘--------------+ .----<------. | | / | ‘--- WIThin -------------------+---*--- ---+---> where (significant element) is any of the following: SITes STRu ct u r es PTRack s 3.6 ZONes SUBStr u ct u r es FRMWor k s P IPes H ANGer s SBFRMwor k s BRAn ch es E QUipm en t s RE STRa in t s Ignoring Clashes at Steelwork Junctions Keywords: INCLUDE IGNORE CONNECTIONS ALL WITH SPECIFICATIONS Description: This facility allows you to control checking at steelwork junctions. (Clash es between sections a nd a tt ached joints et c. ar e ignored automatically.) Fr equently, you may wish t o leave end prepa ra tions a t st eelwork joint s un til late in th e design pr ocess. If you d o this, you can inh ibit clash reporting using t he comma nds described here. Examples: INCLUDE CONNECTIONS Includes all steelwork conn ections dur ing subsequen t clash checking. IGNORE CONNECTIONS Ignores st eelwork conn ections du rin g checking. IGNORE CONNECTIONS WITH SPECIFICATIONS Ignores only those connections which have specifications.. C om m a n d S yn t a x : >-- INClude -- CONnections --> >-- IGNore --+-- ALL --. | | ‘---------+-- CONnections --> >-- IGNore -- CONnections -- WIth -- SPEcifications --> 3-10 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.7 Ignoring Touches Keywords: IGNORE INCLUDE TOUCHES Description: Even t hough t he curr ent t ouch overlap s ett ing may be non-zero, you ma y tell DESIGN t o ignore all touches dur ing subsequ ent clash checks. Touches ignored in t his wa y ar e not a vailable in m emory for in clusion in subsequ ent out put report s. If you a re likely to want to check touches later , it is better to include th em in th e clash -checking operat ion (which is the default situ at ion) an d th en t o inh ibit their inclusion in t he r eport if necessar y. Examples: IGNORE TOUCHES Ignores all touches during subsequent clash checking. INCLUDE TOUCHES Restores th e defau lt situat ion, where t ouches are det ected an d stored with th e cur rent clash list. C om m a n d S yn t a x : >---+--- IGNore ----. | | ‘--- INclude ---+--- TOUches ---> Querying: Q CLASH IGNore 3.8 Controlling the Reported Clash Position Keywords: MIDPOINT Description: By defau lt, the r eported position for a clash d epends on which par t of th e overlapp ing r egion is first detected by th e checking pr ocess: in most cases, this somewhat arbitrary position identifies the clash sufficiently accurately. The MIDPOINT option lets you specify th at th e reported position is always at the centr e of a box sur rounding th e overlappin g region, giving more r eproducible (but slower) resu lts. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-11 Clash Detection C om m a n d S yn t a x : >-- MIDpoint --+-- ON ---. | | ‘-- OFF --+--> Querying: Q CLASH MIDpoint Q CLASH OPTions 3.9 Specifying How Branches Are Checked Keywords: BRANCH ACHECK BCHECK Description: Assuming th at you have n ot specified NOCHECK BRANCHES (see Section 3.5), you ma y check for clash es with in pipe br an ches in eith er of two wa ys: • As a full primitive-by-primitive check of every component within each br anch - known a s a T y p e A c h e c k (or A C H E C K) • As a simplified check which ignores the possibility of clashes between certa in pa irs of components within t he br an ches - kn own as a T y p e B c h e c k (or B C H E C K) (Clashes between adjacent components and attachments within a Bran ch are ignored a ut omat ically.) The pu rpose of th e BCHECK option is t o elimina te from th e clash report spu rious clashes wh ich result when zero-length components (such a s welds and olets) separ at e oth er componen ts or tu bing. If you sp ecify a BCHECK, the warn ing message *** BRANCH CHECKING - OPTION B *** will be output as par t of the report header. This is becau se, although most of th e clash es ignored by Type B checking rea lly ar e spu rious, some genu ine clash es ma y also be ignored. The lat ter , exam ples of which ar e given in Section 3.9.1, will be mostly due t o design err ors, man y of which should have been diagnosed a t a n ea rlier st age by mea ns of a da ta consisten cy check (see Cha pter 2). Th e d e f a u l t check is t he ACHE CK option, sin ce th is is a fail-safe check for all potential clashes. Examples: BRANCH B BRANCH A 3-12 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om m a n d S yn t a x : >--- BRANCh ---+--- Acheck ---. | | ‘--- Bcheck ---+---> Querying: Q CLASH CHECK Q CLASH OPTions 3.9.1 Rules Applicable During Type B Checks The following sections define t he r ules which DESIGN a pplies dur ing th e clash -checking pr ocess when th e BCHECK option is in force. They includ e examples of the sorts of design errors which would remain undetected in the clash report . The ter m ‘clash ’ is used in th ese examples t o refer t o all types of inter feren ce; in pr actice, some of th ese ma y be reported a s touches, dependin g upon th e t ouch specificat ions in force. Clashes Within a Single Branch Rule: If th e leave point (p-leave) of an u pstr eam component or tube coincides with th e ar rive point (p-arr ive) of a downstr eam component, an d th ere is no inter vening Tube, th e two component s will not be checked for clashes between them. This ru le is inten ded to suppr ess clashes when two components or tu bes with in a br anch a re separ ated by one or m ore zero-length components which ha ve no Geomset. For example: ELBOW ACHECK: Tube/elbow clash BCHECK: No clashes TUBE Weld Weld TUBE TUBE ACHECK: Tube/tube clash (the weld and the zero-length bend have no geomsets) BCHECK: No clashes Zero-length variable angle bend to cause direction change at weld PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-13 Clash Detection Clashes Between a Branch and a Nozzle Rule: If a branch head or tail and a nozzle are properly connected an d th e p-ar rive or p-leave of th e final componen t coincides with t he br an ch h ead or t ail, then no clash will be reported. This ru le is inten ded to suppr ess clashes when a n ozzle and a pipe component or tube are separated by one or more zero-length components. For example: NOZZLE REDUCER ACHECK: Nozzle/reducer clash BCHECK: No clashes Weld The rule would, however, cause the following (unlikely) clash to be ignored: NOZZLE ACHECK: Nozzle/reducer clash Nozzle/tube clash REDUCER Weld Note: Reducer wrongly orientated BCHECK: Nozzle/tube clash only Nozzle/reducer clash i ignored Clashes Between Two Branches R u l e 1 If two bra nches ar e connected together end-to-end an d th e p-ar rive/p-leave of two componen ts or tu bes coincide with t heir r espective bran ch h ead/tail (whichever is th e connected end), th en n o clash will be reported. This ru le is inten ded to suppr ess clash es similar t o th ose described for clash es with in a single bran ch, except th at the r elevant components or t ubes ma y now be from differen t, bu t conn ected, br an ches. For example: BRANCH 1 Tail Head BRANCH 2 ACHECK: Valve/reducer clash REDUCER BCHECK: No clashes VALVE Weld Rule 1 would, however, a llow some clash es due t o routing err ors to be ignored. For example: 3-14 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection BRANCH 2 ACHECK: Tube/tube clash TUBE BCHECK: No clashes TUBE Weld BRANCH 1 R u l e 2: 2 : If th e head /ta il tu be of of one bran ch is conn conn ected ected t o a set-on tee or or olet olet (having no geo geometr y other other tha n a sphere) in in a seco second br an ch a n d th e p-ar rive/p-l rive/p-leave eave of th e connected connected component component in th e main bra nch coinci coincides des with t he p-ar rive/prive/pleave of of the t ee’d ee’d componen componen t in t he side br an ch a n d th e latter point is also th e HP OS or or TPOS of th e side bran ch, th en n o clash es will will be report ed between th e head/ta il tu be of of th e tee’d tee’d compo componen nen t an d th e tu be on on eith er side of of th e tee/o tee/olet let in the m ain br an ch. This ru le is is inten ded to suppr ess clashes clashes when a side bra nch is conn conn ected ected t o a zerozero-le length ngth component in a nother bran ch. For example: SIDE BRANCH P3 ACHECK: Two tube/tube clashe at tee position (between side branch and tube each side tee in main branch) TUBE SET-ON-TEE MAIN BRANCH BCHECK: No clashes Rule 2 would, however, allow the following clash to be ignored: SET-ON-TEE TUBE P3 ACHECK: Tube/tube clash at tee position BCHECK: No clashes Note: Side branch on tee has wrong DDANGLE PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-15 Clash Detection 3.10 Checking For Clashes 3.10.1 The Principles Having set up th e obstr obstr uction uction list list an d defined defined a ny n on-default n-default clash specifi specificcat ions ions (touch (touch a nd cleara nce sett ings, rest ricted region region of int int erest , Bra nch BCHE CK option, option, etc.), etc.), you you can now tell DESIGN wh ich ich d esign items you you wa nt it to check check (the c h e c k l is is t ). The clash clash -checking -checking process process is car car ried out in t wo sta ges, as illustr at ed in th e follo following wing F igur e: Stage 1: Obstruction limit boxes overlap. Potential clash diagnosed. Stage 2: Component primitives do not overlap. No actual clash reported. Figur e 3-2 Diagnosis of potentia l/rea l/rea l clash es • I n S t a g e 1, 1 , th e obstr obstr uction uction limit boxes which which en close lose th e individual design design elements elements (as r epresented in th e spat ial map) ar e checked checked fo for overlapp overlapp ing. If no overlap overlap occ occur s between th e obstru ction limit boxes of two elemen elemen ts, t hen no clash clash can exist. If, however, however, t he boxes do overlap, overlap, then a potential clash exists an d t he second second sta ge of of checking checking is car car ried out. • I n S t a g e 2, 2 , the deta iled iled geomet geomet ry of th e elemen elemen ts with in overlap overlap ping obstru ction limit boxes boxes (as (as r epresen ted in t he Geometr ic Modelli Modelling ng Librar y) is checked checked to see if an y of of the const const ituen t p rimit ives ives overla overla p. If th ey do, do, then a n a ppropriate clash clash is report report ed. To confirm onfirm th e absen ce of of clash clash es in a proven design, or to ru n a sup erficial erficial check on a n ew design, design, you you can car ry out just th e first first s ta ge of of th e checking checking process, process, known a s a b o x c h e c k . Note, however, however, th at if you you r un only a box box 3-16 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection check on on a n u npr oven oven design, you you a re likely to gener gener at e a report cont cont ainin g man y spurious clashes clashes resu lting from from situa tions tions su ch a s th e one one illust illust ra ted in Figure 3-2. 3-2. The The extra t ime taken to ana lyse lyse the outpu t r eport eport can out weigh weigh th e time sa ved by run nin g the simp lified lified checking checking procedur procedur e, so use t his option option with with car e. 3.10.2 Running a Full Component Check Keywords: CHECK Description: Th e CHECK comma nd initiat es a full two-sta two-sta ge check check for for clash es between specified specified items (the check list) list) an d th e cur cur ren t obstr uction list. Examples: CHEC CH ECK K AL ALL L Checks all item item s in th e design design m odel (within (within an y restr ictions ictions defined defined as in Sections Sections 3.3 to 3.9) 3.9) against th e obstr obstr uction uction list. CHECK /ZONE1.PIPES /ZONE1.PIPES CHEC CH ECK K /P /PUM UMP1 P1 /P /PUM UMP2 P2 /V /VESS ESS2 2 CHECK /GROUP.MOD2 /GROUP.MOD2 CHEC CH ECK K LE LEAV AVE E TU TUBE BE FR FROM OM /FLAN /FLAN2 2 IA IARR RRIV IVE E TU TUBE BE TO /V /VAL ALV5 V5 Checks only only specifi specified ed items a gainst th e obstr obstr uction uction list. C om o m m a n d S yn yn t a x : .-----<------. / | >-->--- CHEck CHEck ---*----*--- ---+----+---. -. | | ‘--- ALL -----------------+--+---> --> where (clash (clash ing item ident ifier) ifier) is >---+-->---+--- ILEAve ILEAve ---. | | |--|--- IARRIV IARRIVE E --| | | |--|--- HEAD HEAD -----| -----| | | |--|--- TAIL TAIL -----+ -----+----- TUBe TUBe ---. ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘--------------------‘--------------------------------------------------+---------+--- ---> PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-17 Clash Detection 3.10.3 Running an Obstruction Box Check Keywords: BOXCHECK Description: Th e BOXCHECK comman d init iates only a sim plified plified (Stage 1) check check for for clashes bet ween specifi specified ed items (th e check check list) an d th e cur cur ren t obstr obstr uction uction list. Examples: BOXCHE BOXCHECK CK ALL Checks all item item s in th e design design m odel (within (within an y restr ictions ictions defined defined a s in Sections Sections 3.3 to 3.9) 3.9) against th e obstr obstr uction uction list. BOXCHECK BOXCHECK /ZONE1.PIPES /ZONE1.PIPES BOXCHE BOXCHECK CK /PUMP1 /PUMP1 /PUMP2 /PUMP2 /VESS2 /VESS2 BOXCHECK BOXCHECK /GROUP.MOD2 /GROUP.MOD2 BOXC BO XCHE HECK CK LE LEAV AVE E TU TUBE BE FR FROM OM /F /FLA LAN2 N2 IA IARR RRIV IVE E TU TUBE BE TO /V /VAL ALV5 V5 Checks only only specifi specified ed items a gainst th e obstr obstr uction uction list. C om o m m a n d S yn yn t a x : .-----<------. / | >-->--- BOXCHe BOXCHeck ck ---*----*--- > ---+----+---. -. | | ‘--- ALL -----------------+--+---> --> where (clash (clash ing item ident ifier) ifier) has t he synt ax sh own own in S ection ection 3.10.2. 3.10.4 Adding Checked Items to the Obstruction List Keywords: CHECKADD Description: Th e CHECKADD comma nd builds builds u p t he obstruction obstruction list list in a progressive way as th e checking checking p rocess rocess pr oceeds. oceeds. The first first item specified specified in th e check check list is added t o th e cur cur ren t obstruction list (which may initially be empty) and that item is then checked hecked a gainst t he cumu lative lative obstr obstr uction uction list list th us creat ed. This process process is repeat ed for for each item in th e check check list list in t ur n. (Yo (You can achieve similar similar r esults by including th e requir ed items in both both the initial obstru obstru ction tion list an d th e check check list list when u sing the CHECK command.) Examples: CHEC CH ECKA KADD DD /A /B /C /D This builds builds up th e obstru obstru ction tion list in four four separa te sta ges and checks checks t he next specif specifie ied d element element against th e cur cur rent list list a t each st age, thus: 3-18 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection S t a g e 1 : /A is added t o th e (empt y) obstr uction list a nd /A is checked against it, thu s checking for clashes between t he elements: /A/A S t a g e 2 : /B is added to th e obstr uction list, which t hen comprises /A /B, and /B is checked again st t his n ew list, th us checking for clash es between t he following pairs of elements: /A/B /B/B S t a g e 3 : /C is a dded t o the obstr uction list, which th en compr ises /A /B /C, an d /C is checked again st t his n ew list, t hu s checking for clashes bet ween th e following pa irs of element s: /A/C /B/C /C/C S t a g e 4 : /D is added t o the obstruction list, which t hen compr ises /A /B /C /D, and /D is checked a gainst th is new list, th us checking for clashes between t he following pair of element s: /A/D /B/D /C/D /D/D Note: This ha s th e same overall effect a s th e comman d sequen ce: OBSTRUCTION /A /B /C /D CHECK /A /B /C /D which creat es t he obstr uction list /A /B /C /D an d t he check list /A /B /C /D and checks for clash es between t he pa irs /A/A /A/B /A/C /A/D /B/B /B/C /B/D /C/C /C/D /D/D.) C om m a n d S yn t a x : .-----<------. / | >--- CHECKAdd ---*--- ---+---. | | ‘--- ALL ----------+---> where (clash ing item ident ifier) has t he synt ax sh own in S ection 3.10.2. 3.11 Reporting the Clashes Found 3.11.1 The Principles A report is sent a ut omat ically to the Request region each t ime you r un a clash check; th at is, each time you enter a CHECK, BOXCHECK or CHECKADD comma nd. You can cha nge th e forma t for such a report before r un ning th e clash check if necessar y. In addit ion, you m ay send out put to a file by usin g the ALPHA FILE or ALPHA LOG comma nds in th e usua l way. The default report format comprises the following three parts: • T h e r e p o r t h e a d e r : Deta ils of the pr ogra m vers ion in u se; th e types of clash report ed; an y non-defau lt checking options a nd limits; th e touch an d clear an ce limits; an y special reportin g options in u se. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-19 Clash Detection • T h e m a i n b o d y : Deta ils of the clashes foun d, includin g th e clash type an d extent an d th e identifiers of th e two design items involved. The clashes ar e grouped int o s e c t i o n s , one for each significant element which cont ain s an inter feren ce. Wher e space permits, each clash is reported on a single line. • T h e c la s h s u m m a r y : Lists th e total nu mber of clash es of each type found; the total number of elements checked during the run covered by th e report; th e nu mber of element s found t o be free of an y int erferences. All dat a r esultin g from a clash -checking ru n is h eld in t he compu ter ’s mem ory un til overwritten by da ta from a later r un (or u nt il you chan ge modules). This allows you to genera te furt her reports derived from th e sam e dat a, possibly usin g differen t r eporting options from th ose in force for t he original r eport. 3.11.2 Customising the Report Header Keywords: REPORT HEADER Description: The standard header comprises the following: • The program version an d the dat e and time at t he star t of the check. • The types of clash es being reported a nd t he element s specified in the check-initiation command. • The touch and clearance definitions, the current Branch checking option, a nd a ny n on-default options which ma y be in force. Examples: REPORT HEADER OFF Suppr esses entire header REPORT HEADER REPORT HEADER ON Reinstates header if previously suppressed (ON is the default) REP OBSTRUCTION REP OBSTRUCT ON Outpu ts obstruction list as pa rt of header REP OBSTR OFF Suppr esses obstru ction list in header (th e default) C om m a n d S yn t a x : .---------------<-----------------. / | >--- REPort ---*--- HEAder --------. | | | | ‘--- OBStruction ---+--- ---| | | ‘---------------+---> 3-20 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection Querying: Q CLASH REPort HEAder Q CLASH REPort OBStruction Q CLASH REPort List a ll report sett ings (header + ma in + summ ary) 3.11.3 Customising the Main Body of the Report Keywords: REPORT MAIN SECTION PRIMARY SIGNIFICANT REMOVE POSITION FIRST REF NUMBER SECOND BOTH Description: The stan dar d forma t sh ows each clash on a sepa rat e line, with full details of the clashing items an d th e nat ur e of the clash. The reported clashes ar e grouped int o s e c t i o n s , each of which lists all clashes within a single significan t element , the na me of which is usua lly shown only at th e beginn ing of th e section t o avoid excessive repetition of dat a (th e na me of th e second clash ing elemen t is always sh own in full to avoid an y am biguity). The following deta ils may a lso be included in th e report : • The clash p o s i t i o n , in eith er S ite or World coord inat es (to cont rol how t his position is calculated, see Section 3.8). • The PDMS r e f er e n c e n u m b e r s of th e clash ing elements , as well as their names. • Sequential c la s h n u m b e r s , used t o ident ify individua l clash es in other commands (such as when approving clashes). By defau lt, all types of clash , touch an d clear an ce ar e report ed. You ma y rest rict th e report to one or m ore specified clash types (e.g. ha rd/ha rd only, touches only, etc.). Examples: REPORT MAIN OFF Sup pr esses ma in body of report REPORT MAIN REPORT MAIN ON Reinsta tes ma in body if previously sup pr essed (ON is th e default) REPORT POSITION SITE Shows clash positions in Site coordinat es REPORT POSITION WORLD Shows clash positions in World coordin at es REPORT POSITION OFF Suppresses clash positions (the default) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-21 Clash Detection REPORT REF REPORT REF ON Outpu ts reference num bers of clashing items REPORT REF OFF Suppr esses reference numbers (the default) REPORT NUMBER REPORT NUMBER ON Outputs sequential clash numbers. REPORT NUMBER OFF Suppr esses clash n umbering (the defau lt) REPORT FIRST List clash only under first item in DB hierar chy (the default) REPORT SECOND List clash only und er second item in DB hierar chy REPORT BOTH List clash t wice, once under each item in DB hiera rchy REPORT PRIMARY REPORT PRIMARY ON Report s only first or highest pr iority clask foun d between two significan t elements (i.e. suppresses multiple clashes) but also shows actual number of clash es which would have been r eported if this option were n ot in force. REPORT PRIMARY 500 Suppr esses multiple clash r eport s if clash positions ar e less t ha n 500 m m apart (if curr ent un its are mm) REPORT PRIMARY OFF Report s all clash occur ren ces, including t hose between differen t p rimit ives of th e sam e pairs of significan t element s (the default ) REPORT SIGNIFICANT REPORT SIGNIFICANT ON Lists a ll significan t elemen ts wh ich h ave been checked, not just t hose for which clash es ha ve been det ected. REPORT SIGNIFICANT OFF Report s only those significan t elemen ts wh ich in volve clash es (the defau lt) REMOVE SECTIONS SUBS STRUC Sup press es th e labelling of th ose sections of th e report wh ich r epresen t Substr uctur es and Str uctures. Clashing items in th ese sections will be identified by their full nam e on each line (in th e same way th at t he second clashing element is always shown) SECTIONS SUBS STRU Reinstates labelling of specified sections 3-22 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om m a n d S yn t a x : .---------------<-----------------. / | >--- REPort ---*--- POSition ---+--- SIte ----. | | | | | | |--- WOrld ---| | | | | | | ‘--- OFF -----+----| | | |--- REF -----------. | | | | |--- NUMber --------| | | | | |--- MAIN ----------| | | | | |--- PRImary -------| | | | | |--- SIGnificant ---+--- ---| | | | | ‘---------------| | | |--- PRImary --- ------------| | | |--- FIRst -------------------------| | | |--- SECond ------------------------| | | |--- BOTh --------------------------’ | | .-----<-------. | / | |---*--- ---| | | | | ‘--- NP --------+---. .-------<--------. | | / | |--- ALL ---------------+---*--- CLAshes ------| | | | | |--- TOUches ------| ‘---> | | |--- CLEarances ---| | | ‘------------------+---> >---+--- REMove ---. .----<------. | | / | ‘--------------+--- SECtions ---*--- ---+---> where (significant element) is any of the following: SITes STRu ct ur es F RMWor k s ZONes PIP es SUBSt ru ct ur es H ANGer s S BF RMwor k s BRAn ch es RE STRa in ts E QUipm en t s P TRa ck s Querying: Q CLASH REPort MAIN Q CLASH REPort POSition Q CLASH REPort REF Q CLASH REPort NUMber PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-23 Clash Detection Q CLASH REPort PRImary Q CLASH REPort SIGnificant Q CLASH REPort DUPlication Shows u nd er wh ich sections clash es will be reported (i.e. First , Second or Both) Q CLASH REPort LEVel Lists clash types t o be report ed on Q CLASH REPort List all report settings (header + main + summ ar y) 3.11.4 Customising the Report Summary Keywords: REPORT SUMMARY Description: The standard summa ry, output at the end of the clash r eport, comprises a list showing: • The t otal nu mber of clash es foun d of each type • The total n umber of significan t elements checked du ring th e ru n covered by t he r eport • The n um ber of element s foun d to be free of an y inter feren ces This summa ry is headed *** ACTUAL CLASH SUMMARY ***. If REPORT PRIMARY ON has been specified (see Section 3.11.3), tw o report summaries will be produced; one headed *** PRIMARY CLASH SUMMARY *** and one headed *** ACTUAL CLASH SUMMARY ***. Examples: REPORT SUMMARY OFF Suppr esses out put of report summ ary REPORT SUMMARY REPORT SUMMARY ON Reinst ates report su mma ry if previously suppr essed (ON is th e defau lt) C om m a n d S yn t a x : >--- REPort --- SUMmary ---+--- ---. | | ‘---------------+---> Querying: Q CLASH REPort SUMmary Q CLASH REPort List all report settings (header + main + summ ar y) 3-24 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.12 Querying Clash Data Directly You m ay quer y some of th e clash da ta directly, with out genera ting a r eport. 3.12.1 Querying Individual Clashes Keywords: FIRST SECOND TYPE POSITION Description: These options a llow you to qu ery ind ividua l par ts of specified clashes. The clashes are identified in each case by their clash numbers. Examples: Q CLASH 2 FIRST Out put s n am e of first clash ing element (the ‘clash er’) for clash nu mber 2 Q CLASH 2 SECOND Out put s n am e of second clash ing element (the ‘clash ee’) for clash nu mber 2 Q CLASH 2 TYPE Out put s type of clash (e.g. HH TOUCH ) Q CLASH 2 POSITION Out put s position of clash in coord inat e system curr ent ly set for r eporting (i.e. Site or World ) Q CLASH 2 ALL Out put s all of th e preceding da ta ; for exam ple: Clash number: 2 Clasher: CONE 1 of EQUI /VESS1 Clashee: SLCY 1 of STRU /V1.PL Type: HH TOUCH Position: W 10000mm N 18000mm U 2200mm C om m a n d S yn t a x : >--- Query --- CLASH --- clash_no ---+--| |--| |--| |--| ‘--- PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 FIRST ------. | SECOND -----| | TYPE -------| | POSition ---| | ALL --------+---> 3-25 Clash Detection 3.12.2 Querying Clash Statistics Keywords: COUNT CLASHES TOUCHES CLEARANCES NOTPROVEN Description: These options allow you to quer y th e tota l nu mber of clash es of each type (excluding app roved clash es). Examples: Q CLASH COUNT CLASHES Q CLASH COUNT TOUCHES Q CLASH COUNT CLEARANCES Q CLASH COUNT NOTPROVEN Q CLASH COUNT ALL Out put s nu mber of clash es of each type; for example: Total Total Total Total Clashes: 30 Touches: 116 Clearances: 218 Not proven: 37 C om m a n d S yn t a x : >--- Query --- CLASH --- COUNT ---+--| |--| |--| |--| ‘--- CLASHes ------. | TOUCHes ------| | CLEARances ---| | NOTProven ----| | ALL ----------+---> 3.13 Reporting Without Further Clash Checking All clash da ta derived dur ing a clash-checking ru n is r etained in th e comput er’s memory un til overwritt en by data from a s ubsequent ru n (or u ntil you cha nge modules). This allows you t o out put furt her report s derived from th at dat a, usin g modified report ing options an d/or a differen t outp ut device if required. 3-26 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.13.1 Generating a Report from Existing Clash Data Keywords: OUTPUT Description: The report generated in r esponse to an OUTPUT comma nd ha s exactly the sa me form at, determ ined by any cur rent reporting options wh ich you h ave set, as tha t generat ed in response to a CHECK command. The differen ce is tha t t he check options, touch an d clear an ce values, obstru ction list etc. which a pply to th e Outpu t r eport ar e those cur rent wh en the clash ru n w as carried out ; th ese need n ot be cur rent when th e OUTPUT comma nd is given. Examples: OUTPUT CLASHES /ZONE1.PIPES OUTPUT /PUMP1 /PUMP2 /VESS2 OUTPUT /GROUP.MOD2 OUTPUT LEAVE TUBE FROM /FLAN2 IARRIVE TUBE TO /VALV5 These comm an ds outp ut report s of kn own clashes in volving t he sp ecified items in ea ch case OUTPUT Outpu ts a complete report of all clash da ta cur rent ly held in m emory C om m a n d S yn t a x : >--- OUTput ---+--- CLAshes ---. | | ‘---------------+--- ---> where (clash ing item ident ifier) is >---+--- ILEAve ---. | | |--- IARRIVE --| | | |--- HEAD -----| | | |--- TAIL -----+--- TUBe ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘----------------------------------------+--- ---> PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-27 Clash Detection 3.13.2 Suppressing Clash Repetition in Reports Keywords: REPORT FIRST Description: When u sed before an OUTPUT comma nd, the REPORT FIRST option allows you to genera te a sequen ce of report s from a single set of clash data such th at each clash is report ed once only thr oughout t he complete sequen ce. Examples: REPORT FIRST ALL OUTPUT /ZONE.PIPES OUTPUT /ZONE.STEELW Assum e th at you have just ru n a clash check wh ich includes piping an d steelwork items am ong t he elements checked. Then th is sequence generat es two separate reports; the first (from OUTPUT /ZONE.PIPES) shows all clash es involving pipework elements , including th ose between pipework a nd steelwork; the second (from OUTPUT /ZONE.STEELW) shows all clashes involving steelwork elements except t hose which wer e included in t he first report (i.e. th e second report omits clash es between pipework a nd steelwork. C om m a n d S yn t a x : >--- REPort FIRst ALL ---> 3.14 Approving Clashes 3.14.1 The Principles You ma y specify one or m ore clash es which, alth ough r eal int erferences, are t o be omitted from subsequent clash r eport s. Such clash es ar e referr ed to as a p p r o v e d c la s h e s . The obstru ction limits boxes for all approved clash es, as repr esent ed in th e spatial map, ar e identified in a sepa ra te list kn own as th e a p p r o v a l l is t . This ena bles the pr ogra m t o check which item s ha ve been m oved with in th e design after appr oval, and t herefore t o alert you to the fact th at some clash appr ovals ma y no longer be valid. 3-28 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.14.2 Adding Clashes to the Approval List Keywords: APPROVE Description: Adds clashes to th e ap proval list in a ny of the following ways: • By specifically identifying a kn own clash between t wo nam ed items • By specifically identifying a kn own clash by mea ns of its r eferen ce nu mber in the latest clash r eport • By gener ally referr ing to actua l or poten tial clash es between na med items; eith er before or a fter ru nn ing a check t o see what clash es exist • By specifying actua l or poten tial clash es within a single nam ed element Appr oved clash es will be omitt ed from clash report s r egard less of which way round t he int erfering items a re specified in th e obstr uction list and the check list in subsequent clash-checking runs. Examples: APPROVE HS TOUCH BOX1 OF /EQUI1 WITH /GASK1 OF /BRAN2 Appr oves ha rd/soft t ouch between n am ed items (and a ny lower level touches; e.g. HI, SS etc.) APPROVE 5 Appr oves th e fifth clash in most r ecent clash report APPROVE SIGNIF 5 Appr oves fifth clash in most r ecent clash report at significan t elemen t level, ra th er th an at primitive level; where th e significan t elements a re: Sites, Zones, Pipes, Branches, Equipments, Str uctures, Subst ru ctu res, Hangers, Restraints, Ptracks, Frameworks, and Subframeworks APPROVE II CLASH /BRAN1-1 WITH /ZONE.EQUIP Appr oves all Insulat ion/Insu lation clash es between an y element s below /BRAN1-1 an d a ny elemen ts below /ZONE.E QUIP APPROVE /ZONE.EQUIP WITH /ZONE.STEELW Approves all types of clash between m embers of th e na med zones APPROVE HS CLASH /ZONE.EQUIP WITH /ZONE.EQUIP Appr oves all har d/soft clash es between m embers of /ZONE.E QUIP (an d an y lower level clash es, touches or cleara nces) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-29 Clash Detection C om m a n d S yn t a x : >-- APProve --+- -+- CLAsh -----. | | | | |- TOUch -----| | | | | |- CLEarance -| | | | | ‘-------------| | | |- NP --------------------+- -+-- WITh --. | | | | ‘----------+ --> | |--- SIGnificant ---. .------<-------. | | / | ‘-------------------+---*--- clash_no ---+--> where (clash ing t ype) is one of th e following: HH HS HI SS SH SI II IH IS NP an d (clash ing item identifier) is >---+--- ILEAve ---. | | |--- IARRIVE --| | | |--- HEAD -----| | | |--- TAIL -----+--- TUBe ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘----------------------------------------+--- ---> Note: 3-30 Clashin g type H(ard ) aut omat ically includes S(oft) an d I(insulat ion). CLASH au tomat ically includes TOUCH a n d CLEARANCE . PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.14.3 Reapproving Moved Clashes Keywords: REAPPROVE Description: When a n item in volved in an app roved clash h as been m oved within th e design, the clash es involving th at item m ay be rea ppr oved (if you are su re th at such appr oval is still valid) without th e need to reenter th e full clash d eta ils. The resu lt is tha t t he n ew obstr uction boxes for those items, in t he spat ial map, ar e stored with th e existing appr oved clash details. Examples: REAPPROVE 5 6 12 Reappr oves clash es specified by th eir nu mber s in th e appr oved clash list. REAPP ALL Reappr oves th e whole appr oval list. C om m a n d S yn t a x : .-----<------. / | >--- REApprove ---+---*--- app_no ---+---. | | ‘--- ALL --------------+---> 3.14.4 Removing Clashes from the Approval List Keywords: REMOVE Description: Removes specified clash es, or clash es between items which ha ve been moved in t he design since their ap pr oval, from th e appr oval list. Examples: REMOVE APPROVED /ZONE.EQUIP WITH /ZONE.STEELW Removes appr oval of clash es between na med element s. REM APP 5 6 12 Removes app roval of clash es specified by their n um bers in t he a ppr oved clash list. REM APP MOVED REMOVE MOVED Removes a ppr oval of clash es for which one or both clash ing items ha ve been moved in t he design. REMOVE APPROVED ALL Empt ies the appr oval list. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-31 Clash Detection C om m a n d S yn t a x : >-- REMove --+-- APProved --+-- ALL ------------------------| | | | | |-- MOVed ----------------------| | | | | |-- -- WITh -- ---| | | | | | .-----<------. | | | / | | | ‘--*--- app_no ---+-------------| | | ‘-- MOVed -------------------------------------+---> 3.14.5 Outputting the Approval List Keywords: OUTPUT REPORT APPROVED MOVED Description: Out put s th e cur ren t a ppr oval list in a choice of form at s (which you set as for t he clash report listings sum ma rised in Section 3.11.3). Examples: OUTPUT APPROVED Outpu ts full appr oval list OUTPUT MOVED OUTP APPR MOV Out put s only those appr oved clash es which ar e affected by items wh ich ha ve moved in th e design sin ce appr oval. OUTP APPR /ZONE.EQUIP Out put s list of approved clash es involving element s or prim itives with in specified Zone OUTP MOVED /ZONE.EQUIP OUTP APPR MOV /ZONE.EQUIP Out put s ap proved clash es involving only element s or pr imitives in specified Zone which h ave moved in th e design since appr oval REPORT APPROVED REPORT APPROVED ON Causes su mma ry of appr oved clashes to be appended t o all subsequent clash reports REPORT APPROVED OFF Suppr esses summa ry of approved clashes in subsequent reports (the default) 3-32 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection Command Syntax: >-- OUTput --+-- APProved --+-- MOVed --. | | | | ‘-----------+--. | | ‘-- MOVed --------------------+-- --. | | ‘------------+--> >-- REPort -- APProved --+-- --. | | ‘-------------+---> 3.15 Saving and Restoring Clash Data You m ay save the resu lts of the cur rent clash ru n t o a file and t hen r estore tha t dat a for u se later in the sam e session or dur ing another session. 3.15.1 Saving Data to a File Keywords: SAVE Description: Th e SAVE options a llow you to sa ve an y or all of th e following t ypes of dat a t o a n am ed file. In ea ch case you can overwrite a n existing file by appending the OVER comma nd t o th e file nam e in the u sual way. • The cur rent s et u p p a r a m e t e r s : • The obstr uction list • The limits box coordinat es • The touch an d cleara nce settings • Wheth er or n ot t he m idpoint positioning option is in force • Any checking options currently specified (e.g. NOCHECK , IGNORE, ACHECK / BCHECK options) • Any r eporting options cur ren tly specified • Th e c la s h d e t a i l s resulting from the most recent clash-checking run, including the relevant checking options and obstruction list for inclusion in fut ur e reports • The cur rent list of a p p r o v e d c la s h e s Examples: SAVE SETUP /CLASH1 SAVE SET /CLASH1 OVER Saves setu p pa ra met ers, as listed in th e above description, to file /CLASH1 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-33 Clash Detection SAVE CLASHES /CLASH2 SAVE CLA /CLASH2 OVER Saves clash deta ils, including checking options a nd obstru ction list, to file /CLASH2 SAVE APPROVED /CLASH3 SAVE APP /CLASH3 OVER Saves curr ent app roval list t o th e file /CLASH3 SAVE ALL /CLASH4 SAVE ALL /CLASH4 OVER Saves setup parameters, clash details and approval list to file /CLASH4 Note: While the SAVE ALL option is often convenient, bear in min d th at you can not later restore only part of the da ta with out affecting th e rest. This could m ean th at when th e file is restored you will overwrit e some settings which you wish to reta in. C om m a n d S yn t a x : >--- SAVe ---+--| |--| |--| ‘--- 3.15.2 SETup ------. | CLAshes ----| | APProved ---| | ALL --------+--- filename ---+--- OVer ---. | | ‘------------+---> Restoring Data from a File Keywords: RESTORE Description: Th e RESTORE comma nd a llows you t o rea d back clash d at a from a file. Dat a r estored in t his way is available for fur th er r eferen ce as th ough generat ed during the cur rent DESIGN session. The effects of th e thr ee types of dat a which ma y be rest ored ar e as follows: • S e tu p d a t a overwrites any cur rent clash para meter settings. The restored dat a a pplies to all subsequent clash checking an d reporting operations. • C la s h d a t a overwrites all current clash information. The original clash nu mbers, saved with t he data , are retained. • Ap p r o v a l s d a t a is added to the current approvals list. Approved clashes added in t his way ar e given new appr oved clash n um bers. Examples: RESTORE /CLASH4 Restores a ll clash-related dat a from t he n amed file 3-34 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om m a n d S yn t a x : >--- REStore --- filename ---> 3.16 Creating Macro Files Incorporating Clash Data You can crea te a file incorporat ing clash d at a in a forma t su itable for input as a m acro to another P DMS module, such as DRAFT. 3.16.1 The Principles The process operat es by merging the clash dat a with informa tion read from a pre-prepared t e m p l a t e fi le an d then outpu tting the result of th is merger to th e requir ed macro file. The templat e file mu st cont ain a ll necessar y comma nds for th e module to which th e dat a is t o be tran sferred, with coded k e y w o r d s ma rk ing th e locat ions int o which th e clash da ta is to be loaded. DESIGN then su bstitut es its clash r eport d ata for t hese keywords. The keywords t o be used in t he t emplat e file, each of which is identified by $... $ markers, are as follows: $CLA1$ $CLA2$ $CL ATYP E$ $CL AP OS$ $CLATEXT$ First clashing item Second clashing item Clash type Clash position in World coordinat es Clash description as outpu t in a sta nda rd report; for example HH TOU BOX 1 of /VESS1 with HEAD TUBE of /BRAN1 $CLANUM$ $CLAOWN1$ $CLAOWN2$ $$ Note: Clash number Significan t elemen t owning first clashin g item Significan t elemen t owning second clash ing item Used to represent a single $ cha racter in th e ma cro file The us e of the $ character in this context identifies these keywords as escape codes, as defined in P ar t I of th e CADCentre Software Custom isation R eference Guid e. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-35 Clash Detection 3.16.2 Generating Macro-Style Output Keywords: REPORT MACRO Description: The comm an d for specifying ma cro-style outp ut from DESIGN ’s Clash Detection m ode is an extension of th e REPORT command options described in Section 3.11. Th e REPORT MACRO comman d mu st be followed by th e na me of a valid templat e file. If the na med file can not be rea d by DESIGN, or if th ere is an err or in t he forma tting of its keyword cont ent, th en th e MACRO option is ignored a nd su bsequent r eport s will be out put in th e standar d way. To genera te a ma cro file, having first given a valid REPORT MACRO template_file comma nd, use the ALPHA FILE synt ax to direct your outp ut to the r equired macro file na me. Then output your clash r eport in an y of the usu al ways (th at is, by using a CHECK, BOXCHECK, CHECKADD or, more pr obably, OUTPUT command). When a report is out put in m acro mode, th e following conditions a pply: • The header and su mmar y are not output , so tha t only the ma in body data is merged with t he t emplate file • Section identifiers are not output • Th e REF a n d NUMBER options , if in force, are in cluded in th e $CLATEXT$ locations • Th e BOTH/FIRST/SECOND a n d PRIMARY options, if in force, ar e taken into account when working out which clashes to output Examples: This example illust ra tes h ow you m ight creat e a DRAFT inpu t m acro for plott ing clashing items identified by DESIGN. It a ssum es some u nderst anding of th e use of DRAFT, alth ough you n eed not un derst an d th e pur pose of all of th e DRAFT comm an ds in order t o follow th e basic prin ciples. A tem plat e file cont ain ing th e necessary comm an ds for DRAFT to display an d plot four views of clashing items might be as follows: 3-36 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection $$( $CLANUM$: $CLATEXT$ $$) $$( NEW DEPT /DEPT-1 NEW REGI /REGI-1 NEW DRWG /DRWG-1 NEW LIBY /LIBY-1 NEW DLLB /DLLB-1 NEW RPLB /RPLB-1 NEW STYL /STYL-1 TU ON CL OFF DLEV6 NEW RRST /RRST-1 NEW RRUL /RRUL-1 USE /STYL-1 FOR ALL $$) /DLLB-1 NEW IDLI /IDLI-$CLANUM$ ADD $CLAOWN1$ $CLAOWN2$ /DRWG-1 NEW SHEE /CLASH-SHEET1-$CLANUM$ SIZE A4 NEW VIEW /VIEW1-$CLANUM$ VREG XR 0.46 YR TO XR 0.9 YR 1 IDLN /IDLI-$CLANUM$ VTYPE UNIV RRSF /RRST-1 VSCA 1/40 THPOS $CLAPOS$ DIR N NEW VIEW /VIEW2-$CLANUM$ VREF XR 0 YR 0.1 TO XR 0.44 YR 0.55 IDLN /IDLI-$CLANUM$ VTYPE UNIV RRSF /RRST-1 VSCA 1/40 THPOS $CLAPOS$ DIR E 0.01 D NEW VIEW /VIEW3-$CLANUM$ VREG XR 0.46 YR 0.1 TO XR 0.9 YR 0.5 IDLN /IDLI-$CLANUM$ VTYPE UNIV RRSF /RRST-1 VSCA 1/40 THPOS $CLAPOS$ LOOK D NEW VIEW /VIEW4-$CLANUM$ VREG XR 0 YR 0.6 TO XR 0.44 YR 1 IDLN /IDLI-$CLANUM$ VTYPE UNIV PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-37 Clash Detection RRSF /RRST-1 VSCA 1/40 THPOS $CLAPOS$ ISO 3 SHEE NEW NOTE NEW TEXP AT X137 Y32 ALIGN HB JUST C CHEI 4 FONT 1 BTEX ’$CLANUM$: $CLATEXT$’ SHEE UPDATE DESI PLOT SHEE FILE /$CLASHPLOT$CLANUM$ $$(---------------------------------------------------$$) You could nam e th is templa te file /DRAFT.TEM an d th en m erge existin g clash dat a with it to crea te a DRAFT ma cro inpu t file /DRAFT.MAC, thu s: REPORT MACRO /DRAFT.TEM specifies ma cro mode a nd tem plat e file ALPHA FILE /DRAFT.MAC specifies mer ged outpu t file (th e ma cro) $P ’$$( DRAFT macro created using DRAFT.TEM $$)’ $P ’’ leaves blank line after header OUTPUT out put s all cur rent clash dat a to macro $P ’$$.’ adds macro end mar ker $. APLHA FILE END closes output file REPORT MACRO OFF reverts to norm al out put The resulting macro /DRAFT.MAC will comprise multiple copies of the DRAFT comma nds with t he appr opriate dat a subst itutions for each clash output . If you ru n th is ma cro, th e specified four views will be plotted for each pa ir of clash ing items dia gnosed and outpu t by DESIGN . Each set of views will be sent to a plotfile nam ed /CLASHP LOT n , where n is the clash n um ber allocated by DESIGN. C om m a n d S yn t a x : >--- REPort --- MACro ---+--- template_filename ---. | | ‘--- OFF -----------------+---> Querying: Q CLASH REPort MACro Gives na me of tem plat e file (or OFF ) 3-38 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 3.17 Displaying Clashes Visually Keywords: REPORT GRAPHICS COLOUR CLASH OBST RESETHIGHLIGHT Description: In a ddition t o alpha nu meric reporting of clash da ta (to your term inal or to a file), DESIGN can show t he locat ions of clash es gra phically by highlighting the clashing elements on the display. When gr aph ical report ing is switched on, for each clash foun d, th e element in t he obstr uction list (the ‘clash ee’) is displayed in th e CLASH colour an d t he element in t he check list (th e ‘clash er’) is displayed in t he OBST colour . If a clash ing elemen t is alr eady in th e dra wlist (i.e. already displayed), it will be highlight ed by a cha nge to th e appr opriate colour . If th e element is not curr ent ly displayed, it will be added to th e dra wlist au toma tically (in t he defau lt visible colour) an d will th en be highlighted in the appropriate colour. The element stays h ighlighted un til another clash check is r un , or un til you rem ove all gra phical highlighting specifically by using t he RESETHIGHLIGHT command. Examples: REPORT GRAPHICS ON REPORT GRAPHICS OFF Highlights clashes on the graphical display Clashes not highlighted on the graphical display (the default) RESET Removes gra phical highlightin g from a ll Volume views C om m a n d S yn t a x : >--- REPort --- GRAphics --- ---> >--- COLour -+- CLASH -. | | ‘- OBST --+- colour_name --------------. | | ‘- MIX RED n GREen n BLUe n -+-> >--- RESEThighlight ---> Querying: Q CLASH REPort GRAphics PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-39 Clash Detection 3.18 Automatic (Continuous) Clash Detection As an altern ative to interm ittent clash checking on dema nd, as a ssumed by th e preceding comma nd syn ta x in t his chapt er, you m ay check for clash es au toma tically each time you modify th e design. 3.18.1 Specifying Automatic Clash Detection Mode Keywords: AUTOCLASH Description: When a ut omat ic clash checking is switched On, a clash check is car ried out at th e end of every comma nd line in which a n element h as been m odified in some way th at could cau se a clash to occur ; tha t is: • When a n ew element ha s been creat ed • When a n element ’s position a nd/or orienta tion has been chan ged • When a n element ’s geomet ry ha s been cha nged Each clash check is car ried out u sing the curr ent option settings (obstruction list, limits box, etc.), the modified element being included automatically in an implied DESCLASH command (see Section 3.1). The r esults of each clash check r eplace those of an y previous checks, so th at an y reported clash es m u s t resu lt from t he actions of th e last comman d. Your a tt ent ion will alrea dy be focussed on th e cur ren t element, so tha t it is usu ally most convenien t t o rely on gra ph ical highlighting to show th e clash (as explained in S ection 3.17), rat her tha n t o out put th e clash dat a t o a file. You can u se the OUTPUT comman d to see more deta ils of the clash if requ ired. Aut omat ic clash checking is switched Off by defau lt. C om m a n d S yn t a x : >--- AUTOCLASH --- ---> Querying: Q AUTOCLASH Note: In order t o avoid spurious clash r eport s when a new Bran ch is created, th e last s ection of implied tube in a Br an ch is checked only if th e Bran ch LTAI at tr ibute is set t o Tru e. (The LTAI at tr ibute is set au toma tically by DESIGN wh en th e Bran ch Tail is positioned.) The clash-checking r ules a re as follows: 1. If the cur rent element is a Piping Component an d is the last component in t he Br an ch, then its leave tu be is checked only if th e Bran ch LTAI at tr ibute is set t o Tru e. 3-40 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection 2. If the curr ent element is a Bran ch which h as no members, then t he tu be which const itut es th e Bran ch is checked only if th e Bran ch LTAI at tr ibute is set to True. 3.18.2 Logging the Clashes Keywords: CLASHLIST Description: In order t o pr ovide an a udit t ra il of th e effect of th e cur ren t session, th e system k eeps a list of all elemen ts for wh ich it h as carr ied out an au toma tic clash check. You ma y review th e effect of your design chan ges by rerun ning a clash check on a ll the element s in t his list. Note tha t t he r esults of th e checks der ived from t he clash list in th is way will be based on th e cur ren t option set tings, which may n ot be th e sam e as th ose in force when th e original checks were m ade. Examples: CLASHLIST DISPLAY Reru ns a clash check on a ll elements in t he clash list CLASHLIST EMPTY Removes all element s from th e clash list 3.19 Error Messages in Clash Detection Mode The following err or mess ages a re th ose which ar e specific to DESIGN’s Clash Detection mode. (69:4) May only specify tube on piping or hanger components You ha ve tr ied to specify implied tube conn ected t o an in appr opr iate t ype of element (see Section 3.2 for examples of the synt ax). (69:5) Must be a BRANCH or HANGER to specify HEAD or TAIL tube You have tr ied to specify a h ead or ta il tu be connected to an ina ppr opriate type of elemen t (see Section 3.2 for exam ples of th e synt ax). (69:7) name/refno has not been fully mapped The specified element ha s not h ad its positiona l data upda ted in t he spat ial map. (69:8) name/refno is already in the obstruction list You have tr ied to add an element to the obstru ction list which is a lready present in t he list. Use the Q CLASH OBSTRUCTION comma nd t o check th e current list if necessary. (69:9) name/refno is not in the spatial map The specified element ha s not h ad its positiona l data upda ted in t he spat ial map. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-41 Clash Detection (69:11) name/refno is not in the obstruction list You ha ve tried to rem ove or exclud e an elemen t from th e obstr uction list which is not present in th e list. Use the Q CLASH OBSTRUCTION command to check th e cur ren t list if necessar y. (69:12) Approved clash number integer is not in approval list You ha ve tried to remove or r eappr ove a clash by referr ing to an a ppr oved clash id which is n ot pr esent in t he list. Use the OUTPUT APPROVED comma nd if necessar y to check th e cur ren t list. (69:13) Element type word is not currently a section header You ha ve tried t o remove a section from th e ma in body of the r eport wh ich is not presen t in t he list of sections. Use th e Q CLASH REPORT MAIN comma nd t o check th e cur ren t sections if necessar y. (69:16) Maximum number of element types for the NOCHECK option exceeded The ma ximum nu mber of element types which you m ay specify in a NOCHECK comm an d is 20. (69:17) Element type word is not in the list of those set for NOCHECK You h ave tried to use th e WITHIN comma nd t o reinsta te an element t ype which ha s n ot been pr eviously specified in a NOCHECK command. (69:18) Clearance value must be positive You ha ve specified a negat ive ar gumen t in a CLEARANCE command. You mu st specify eith er a positive value (which m ust be greater t ha n t he curr ent touch gap) or zero (which switches the clearance option off). (69:19) (69:20) (69:21) (69:22) (69:23) Clearance value must be greater than touching gap Touching gap must be positive Touching gap may not be greater than current clearance Touching overlap must be positive Invalid element type for an approved clash See Section 3.14.2 for the valid ways of specifying approved clashes. (69:24) Approved clash already exists You have tr ied to add a clash t o th e appr oval list wh ich is alrea dy presen t in th e list. Use th e OUTPUT APPROVED comma nd to check t he curr ent list if necessary. See Section 3.14.2. (69:25) integer is not a valid approved clash number You ha ve tried to remove or r eappr ove a clash by referr ing to an a ppr oved clash id which is n ot pr esent in t he list. Use the OUTPUT APPROVED comma nd if necessar y to check th e cur ren t list. See Section 3.14.2. (69:26) There are no items in the obstruction list You cann ot r un a clash check unt il you h ave added at least one element to the obstruction list. (69:27) Maximum number of element types for the SECT option exceeded The ma ximum nu mber of element types which you m ay specify in a REMOVE SECTIONS comma nd is 20. 3-42 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection (69:28) Clashes cannot be saved as no clash run has been made Th e SAVE CLASHES command can only save clash data currently held in mem ory from th e most recent clash -checking ru n. Ther e is no valid data in memory. (69:29) Error in file format You have pr obably tried to restore da ta from a file which was not wr itten to by a DESIGN (or CLASHER) SAVE command. (69:33) No clash run has been made Th e SAVE CLASHES command can only save clash data currently held in mem ory from th e most recent clash -checking ru n. Ther e is no valid data in memory. (69:34) File filename already exists. Output defaulted to terminal You can only overwrite t he cont ent s of an existin g file by using eith er t he FFILE comma nd or th e FILE ... OVER option. Your FILE comma nd h as been ignored a s a pr otection a gainst accidenta lly overwr iting th e nam ed file. (69:35) File filename is in use. Output defaulted to terminal You have specified a file which is already open (or which is otherwise inaccessible for writ ing t o). Your outpu t will th erefore be sent to your ter mina l un til you s pecify a valid file nam e. (69:36) File filename does not exist The file from wh ich you a re t rying t o read is n ot accessible from t he OS directory from wh ich you ent ered P DMS. Do you need to give th e full path na me for th e file? (69:37) File filename already exists You can only overwrite t he cont ent s of an existin g file by using eith er t he FFILE comma nd or th e FILE ... OVER option. (69:38) File filename is in use You have specified a file which is already open (or which is otherwise inaccessible for writing to). (69:39) Page width may not be less than 50 characters A page width of less tha n 50 char acters will be too na rr ow to accommodate th e clash dat a lines in th e report . (69:40) Page length must be between 20 and 200 lines The page length m ust be of a su itable length t o accommodate a s ensible top an d bottom ma rgin an d a r easonable nu mber of report lines. (69:41) Page margin must be between 0 and 20 The mar gin width must be positive and must allow enough rema ining line length to accommodate a typical report line. (69:43) No spatial map exists for DB containing name/refno The specified element form s par t of a DB for wh ich a spa tial ma p ha s not yet been crea ted. The positiona l data for t he element is t her efore un available for clash checking. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-43 Clash Detection (69:47) The leave tube for name/refno is not in the spatial map The specified element ha s not h ad its positiona l data upda ted in t he spat ial map since it was conn ected t o the n ext downst ream component. (69:48) No approved clashes exist between name/refno and name/refno You ha ve tried to rea ppr ove one or more clash es between n am ed items for which no ap pr oved clash es ha ve been specified. (69:56) Unable to open file filename The s pecified file can not be foun d. Check t ha t you ha ve specified its correct path na me an d t hat th e directory cont aining it is accessible from th e directory from which you ent ered P DMS. (69:57) Line integer of macro template filename is too long The specified comma nd line in your t emplat e file is of such a length th at , when t he clash -checking keywords h ave been replaced by th e correspondin g clash da ta, it exceeds the m aximum per mitted length for a PDMS comma nd line. (69:58) Line integer of macro template filename does not have matching dollar signs Ea ch k eyword in a ma cro templa te file must be enclosed between a pa ir of $ escape characters. The $ cha ra cter s in th e specified file do not form properly matched pairs. (69:59) Line integer of macro template filename has unrecognised keyword See Section 3.16 for a list of valid keywords for u se in ma cro tem plat e files. (69:60) Macro template filename has no keywords Ther e are n o identifiable locat ions in t he tem plat e to which clash da ta can be tra nsferred. DESIGN cannot check th e comma nd synt ax in th e template an d it is m ost likely th at the enclosing $ characters have simply been omitted from t he k eywords . See Section 3.16. (69:61) Spatial map marked as incomplete ( for DB integer ) The positiona l data h as not been updat ed in t he spatial map since the specified DB was las t a ccessed from a d esign module. En tr y to a design module with m ap m aint ena nce off will cau se th e ma p to be flagged as incomplete if an y design chan ge is made, even if no clash es ar e affected. (69:66) No obstruction list. Use ‘OBS ALL’ or ‘OBS id1 id2 ... idn’ You cann ot r un a clash check unt il you h ave added at least one element to the obstruction list. (69:67) Currently OBS ALL. Specifying additional obstructions has no effect Since the obstruction list already comprises all relevant elements in the Design DB, th ere is no point in tr ying to add specifically nam ed element s to th e list. 3-44 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection (69:68) No template file has been specified for macro output When using th e REPORT MACRO option you m u s t specify th e na me of th e tem plat e file from wh ich t he st ru ctur e of th e macro is to be rea d. This is quite in dependen t of the specificat ion of the out put file (FILE or FFILE comman d) which defines wher e th e final ma cro is to be sent . (69:79) ALL not valid for EXCLUDE command The mem bers of obstru ction list elemen ts wh ich a re t o be excluded from th e list mu st be individua lly specified. EXCLUDE ALL would effectively eliminate t he en tire obstruction list (use REMOVE OBSTRUCTION ALL if you r eally wan t t o do th is). (69:80) name/refno is already in the exclusion list You have tr ied to add a n element to the exclusion list which is already present in t he list. Use the Q CLASH OBSTRUCTION comma nd t o check th e current list if necessary. (69:81) name/refno is not in the exclusion list You ha ve tr ied to remove an elemen t from t he exclusion list wh ich is n ot present in t he list. Use the Q CLASH OBSTRUCTION comma nd t o check th e current list if necessary. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-45 4 Copying Model Data from PDMS to REVIEW This chapt er t ells you h ow to use t he DESIGN EXPORT comma nd to identify a list of objects which a re to be r eviewed gra phically (usin g Cad cent re’s RE VIEW product r an ge) an d to define how they are t o be represent ed. EXPORT extracts from th e PDMS Design dat abase t he r elevant da ta for t he pr imitives which will make u p t he display, including th e Design h ierarchy, and st ores it in an inter mediat e file (a m o d e l fi le ) for u se by REVIE W. 4.1 The Model File To specify th e na me of the m odel file to which design da ta is to be copied, use one of the comm an ds: EXPORT FILE filename EXPORT FILE filename READ Opens an existin g file in r ead-only mode, allowing its cont ent to be queried but n ot overwritten. EXPORT FILE filename OVERwrite Overwrites a n existing file of th e same n am e. EXPORT FILENote text Adds a line of user-supp lied text to th e model file header . For example, EXPORT EXPORT EXPORT EXPORT FILE /TESTFILE FILE /TESTFILE READ FILE /TESTFILE OVER FILENOTE ’Platform PA2 REVIEW Data’ To quer y the na me of th e cur ren t m odel file, use th e comma nd Q EXPORT FILE (similarly Q EXPORT FILENote to query the header text) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 4-1 Copying Model Data from PDMS to REVIEW 4.2 Object Selection and Colour Setting Elemen ts t ha t a re t o be copied to the model file ar e held in a d r a w l i st . Elemen ts ma y be specified explicitly or by usin g a P ML expression to define s e le c t i o n c r i t e r i a . For inform ation about P ML, see th e Cadcentre Software Customisation Reference Manual. Only s i g n i fi c a n t e l e m e n t s , such a s BRAN, EQUI , SUBS, HANG, STRU, PTRA, etc., ma y be added t o or r emoved from th e dra w list. If you t ry t o add or rem ove an element below a significant element (th at is, a primit ive), the wh ole of its owning significan t elemen t will be added t o or r emoved from th e dra w list. Colour s to be used t o display th e differen t elemen t t ypes can be specified explicitly or by usin g th e A u t o c o l o u r selection ru les - see th e AUTOCOLOUR comma nd in P ar t 1 of th e PDMS DE S IGN R eference Man ual . Examples: EXPORT /VESS1 COLOUR 2 Specifies colour of exported element directly. EXPORT AUTOCOLOUR COLOUR 10 ALL BOXES WITH (XLEN GT 100) EXPORT AUTOCOLOUR ALL BRAN MEMBERS COLOUR (:ICOLOR OF SPREF) Specifies using AUTOCOLOUR rules. The colour nu mber, wheth er given as an integer or a s an expression, refers to th e colour n um ber to be used in REVIEW. The order in which r ules are given is importa nt , becau se they ar e evaluat ed in this order u ntil a ru le is encoun tered for which th e selection criteria a re sat isfied. This is th e ru le from wh ich t he colour is ta ken . If no ru le is sat isfied, or if no colour r ules h ave been given, or if th e selection is inva lid for some rea son, then colour 0 is used. Rules ma y be reorder ed, removed and cont rolled by the following commands: EXPORT AUTOCOLOUR ON Tur ns th e use of Aut ocolour in E XPORT m ode on. Th e ru les will be ignored unt il tur ned on. EXPORT AUTOCOLOUR OFF Tur ns th e us e of Autocolour in E XPORT m ode off. EXPORT AUTOCOLOUR RESET Clears t he curr ent s election by rem oving all rules. EXPORT AUTOCOLOUR REMOVE 4 Removes r ule 4. EXPORT AUTOCOLOUR REORDER 4 TO 99 Reord ers r ule 4 t o position 99. 4-2 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Copying Model Data from PDMS to REVIEW Querying: A maximum of 200 Autocolour r ules a re a llowed a t p resen t. Th e following queries are also available: Q EXPORT AUTOCOLOUR NUM Return s the num ber of ru les. Q EXPORT AUTOCOLOUR MODE Retu rn s th e mode stat e (on or off). Q EXPORT AUTOCOLOUR integer Returns the selection criteria for rule integer. Q EXPORT AUTOCOLOUR FOR identifier Retu rn s colour to be selected for ident ified element. 4.3 Controlling the Representation of Holes Holes may be represented realistically, with colour shaded inner surfaces, and ma y be ‘seen t hr ough’. To contr ol th e app ear an ce of holes, use t he comm an ds EXPORT HOLEs ON HOLEs OFF (default) HOLEs SOLID EXPORT HOLES SOLID repr esent s h oles as s olids in colour 1, which by defau lt is black. Solid holes cann ot be seen th rough. The sta te of the hole settings ma y be queried using Q EXPORT HOLES Note: Since holes are const ru cted u sing facets wh ich involve a lar ge amoun t of geometric data, switching holes ‘on’ will increase the computational overh ead when processing. The more holes in th e model, the longer t he model file will ta ke t o gener at e, and th e more slowly it will be drawn in RE VIEW. Note tha t other represent ation settings, such a s Tube, Cent reline, Obstruction, Insulat ion a nd Dr awing Level, are t aken from th e cur rent DESIGN settings. 4.4 Copying Data to the Model File To tr an sfer dat a a bout th e primitives owned by all elements in t he cur rent dra w list int o the curr ent model file, use th e comma nd EXPORT FINish This comma nd does not cha nge the curr ent d ra w list. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 4-3 Copying Model Data from PDMS to REVIEW 4.5 The EXPORT Command - Full Syntax >-- EXPORT --+-| | | | | |-| |-| | | | | | | | | |-| | | | | |-| ‘-- Note: 4-4 HOLES --+-- ON -----. | | |-- OFF ----| | | ‘-- SOLID --+--> FILENote FILE text --> name --+-- TEXT --. | | ‘----------+-- READ -------. | | |-- OVERwrite --| | | ‘---------------+---> .-------<----. / | --*-- --’ | |-- COLour integer --> | ‘--> FINish --> --> is the general selection syntax. is t h e AUTOCOLOUR command For more inform ation, see Part 1 of th e PDMS DES IGN R eference Manual. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Index ACHECK command clash detection, 3-12 ANGLE command data consistency checking, 2-3 APPROVE command clash detection, 3-29 ATTACHECK command, 2-2 AUTOCLASH command clash detection, 3-40 AUTOCOLOUR command, 4-2 clash detection, 3-3 ECCENTRICITY command data consistency checking, 2-5 EXPORT command, 4-1 HOLES command (EXPORT), 4-3 IGNORE command clash detection, 3-10 INCLUDE command clash detection, 3-10 LIMITS command AUTOLIMITS command clash detection, 3-6 clash detection, 3-6 MAXANGLE command BCHECK command clash detection, 3-12 BOXCHECK command clash detection, 3-18 data consistency checking, 2-3, 2-10 MIDPOINT command clash detection, 3-11 Model file (for use by REVIEW), 4-1 CHECK command, 2-2 NOCHECK command clash detection, 3-17 clash detection, 3-9 CHECKADD command clash detection, 3-18 Clash position, 3-11 Clash reports, 3-19 Clashing extent clash detection, 3-1 CLASHLIST command clash detection, 3-41 OBSTRUCTION command clash detection, 3-3 Obstruction level clash detection, 3-1 OFFSET command data consistency checking, 2-3 RATIO command data consistency checking, 2-3 CLEARANCE command REAPPROVE command clash detection, 3-8 clash detection, 3-31 COUNT command clash detection, 3-26 DESCLASH command PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Reports clash detection, 3-19 SECTION command Index-1

Pdms Design

Recommend Documents