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 ference nce Man ual describes all the DESIGN commands Th e PDMS DE S IGN R efere in detail. It also describes how the Design database is structured, the Design database elements elements and their att ributes.

DESIGN is normally used interactively. The Graphical User Interface (GUI) provides discipli discipline-based ne-based a pplicat pplicat ions ions which h elp you you to creat e, check check a nd report on t he model. How to use t he ap plicat plicat ions ions is described in in u ser guides an d on-line on-line help. This manual is written for experienced users of PDMS DESIGN who need to use comm comm an ds; for for example, to write bat ch ma cros or to cust cust omise the GUI. If you you a re going going t o cust cust omise the GUI, you will also need to refer t o the Cadcentre S oftware Custom Custom isation isation Guide a n d Cadcentre S oftware Custom Custom isation Referenc Reference e Man ua l for info inform ation about P ML, the Cadcent Cadcent re pr ogramm ing language.

1.2

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

General Com Com m and s , describes Part 1 1,, General describes genera l DESIGN comm comm an ds, which ar e used, fo for example, for setting u p th e display, display, and querying and na vigating vigating around th e Desig Design n dat abase.

In par ticular, ticular, it describes describes how to use th e co comma nd s yn yn t a x g r a p h s , which ar e used t o show all the options available for for each comman comman d. •

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

•

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

•

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

For a compr ehensive list list of all PDMS att ributes a nd pseudo-att pseudo-att ributes, see the Cadcentre S oftw are Custom isation Reference 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 divided int int o th e fol follo lowing wing cha cha pter s:

1-2

•

Chapter 2 explains how to check Data Consistency.

•

Detection facilities. Chapter 3 describes the Clash Detection

•

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


2

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

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

2.

Conn Co nn ection ection types a re compa compa tible.

3.

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

4.

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

5.

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

6.

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

7.

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

8.

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

9.

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

10.

Lengths of structural Sections fall within predefined ranges.

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

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

•

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

•

Those which which sp ecif ecify y minimu m length s of tu be between ad jacent jacent piping components (norma lly lly dependent upon t he t ube diamet er) or or for rod between adjacent hanger components, the maximum acceptable angle for pipe bends, an d the minimum a nd ma ximu ximu m length length s of 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 Before you you in itiat e a da ta -checking -checking operat ion ion you mu st sp ecif ecify y whether th e resulting output is to be sent sent to your your term inal or or t o a fil file. e. The outpu t device device mu st be defined defined before th e deta iled iled checking checking is car ried out out , using the stan dar d ALPHA FILE comma nds described in in eference rence Man ual. Par t 1 of th e PDMS DE S IGN R efe

2.1.2 Checking Parts Parts of the Design Keywords:

CHECK

ATTACHECK

Description:

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

Examples: CHECK CHECK /ZONE/ZONE-1 1

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

Generat es selec selective tive report report on th e na med Bra nches only only TOL TO L AT ATTA TACH CHEC ECK K OF OFF F

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

2-2


Data Consistency Checking

Where is the P ML arr ay used t o store references of of an y element element s with with errors, and th e (o (option) ption) is the a rr ay th at stores th e error codes. codes. Querying: >-- Query Query TOLera TOLerance nce ATTACh ATTACheck eck --> 2.2 Setting Geometric Error Limits 2.2.1 Piping/Hangers Note: All references to pipe component component s an d tu be in th is section section app ly equally to han ger co components and rod. The extent of the misalignment between two adjacent piping components may be measured using any of of th ree para meters: the offset distance between between th eir eir respective p-ar p-ar rive an d p-leave p-leave axes; the displacement a n g l e between between th eir respective p-ar p-ar rive an d p-leave p-leave axes; or 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 gle par amet er). See See Figure below. 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 comm an ds sp ecif ecify y th e ma ximum offset, ffset, a ngle or ratio misalignments that will be allowed between adjacent components before before a diagnostic message is out out put . Examples: TOL TO L OF OFFS FSET ET 1 (Defau (Default lt) ) Maximum pipe misalignmen t is 1 mm offse offsett TOL TO L OF OFF F 1/ 1/4 4 IN INCH CH Maximum pipe misalignmen t is 0.25 inch offset offset TOL ANGLE ANGLE 0.0573 0.0573 (Defau (Default) lt) Maximum angular misalignment is 0.0573 degrees (i.e. 0.01 radians) TOL TO L RA RATI TIO O 0. 0.00 001 1 (Def (D efau ault lt) ) Maximum offset/ offset/separ separ at ion ion r at io is 0.001 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-3 Data Consistency Checking TOL TO L AN ANG G 1. 1.5 5 TOL TO L RA RAT T 0. 0.02 0262 62 These are equivalent equivalent an gular sett ings, since since 0.0262 0.0262 is is t he t angent of the an gle 1.5 1.5 degrees TOL TO L DE DEF F Resets a ll misalignm misalignm ent toleran ces ces (Offset, (Offset, Angle Angle an d Rat io) io) to th eir default values TOL MAXANG 90 (Def ault ) Maximum Maximum permitt ed design design a ngle fo for pulled pulled bends and elbo elbows can can be set to values from 0° (stra ight t ube) to 180° (U-bends). (U-bends). C om o m m a n d S yn yn t a x : >-- TOLera TOLerance nce --+---+-| |-|-| |-|-| |-| ‘-- OFFset OFFset --. | ANGl ANGle e ---| ---| | RATi RATio o ---+ ---+--- l> --> --> DEFaul DEFault t --> MAXANG MAXANGle le -- value --> Querying: >-- Query Query TOLera TOLerance nce --+---+-| |-| |-| ‘-- OFFse OFFset t ----. ----. | ANGle ANGle -----| -----| | RATio RATio -----| -----| | MAXANG MAXANGle le --+--> --+--> >-- Query Query TOLera TOLerance nce OPTion OPTions s --> (also outputs ATTACHECK a n d TUBE settings) 2.2.2 Structural Sections Misalig Misalignmen nmen ts of Sec Sections tions in str uctur al designs designs ar e defined defined in similar t erms to th ose used for for p ipework ipework , na mely in ter ms of an offset 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’ Section’ss e c c e n t r i c i t y . Distan ce and a ngu lar offse offsets ts a re mea sur ed from from th e logic logical al line between Nodes, Nodes, while while additional additional checks checks a re m ade u sing the a tta ched Neu tr al Points of th e Section Section an d th e co corr esponding Nodes. The ter minology minology is is illust illust ra ted in t he follo following wing 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 comm an ds specify specify th e ma ximum offset offset dista nce, an gle or ra tio misa lignm lignm ent s th at will will be allowed allowed between a Section’ Section’ss Neu tr al Axis Axis a nd th e Logic Logical al Line bet ween N odes odes before before a diagnostic message is output. Examples: ECC EC C SE SECT CT DIST DIST 1 (Def (D efau ault lt) ) Maximu m offset offset for either end of Section Section is 1 m m ECC EC C SE SECT CT DI DIST ST 0. 0.5 5 IN INCH CH Maximu m offset offset for for either end of Section Section is 0.5 in ECC SECT SECT ANGLE ANGLE 0.0573(Defa 0.0573(Default ult) ) Maximum Maximum an gular m isalignment isalignment is 0.0573 0.0573 degrees degrees ECC EC C SE SECT CT RA RATI TIO O 0. 0.00 001 1 (D (Def efau ault lt) ) Maximu m offse offset/node t/node separ at ion ion r at io is 0.001 0.001 ECC EC C SE SECT CT AN ANG G 1. 1.5 5 These are equivalent a ngular settings, since since ECC EC C SE SECT CT RA RAT T 0. 0.02 0262 62 0.0262 is is th e ta ngent of the an gle 1.5 degrees degrees ECC EC C SE SECT CT DE DEF F Resets a ll misalignmen t ecc eccent ricities ricities (Offset (Offset dista nce, Angle Angle an d Ra tio) to th eir eir default default values PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-5 Data Consistency Checking C om o m m a n d S yn yn t a x : >-- ECCent ECCentric ricity ity -- SECTio SECTion n --+---+-| | | |-|-| |-| | | ‘-- DISTan DISTance ce --+---+-- --> | ‘-- DEFault --> ANGl ANGle e --. --. | RATio RATio --+---+-- value --> | ‘-- DEFault --> DEFaul DEFault t --> Querying: Q TOLera TOLeranc nce e ECCent ECCentric ricity ity --- SECTi SECTion on ---+----+--- DISTan DISTance ce ---. ---. | | |--|--- ANGle ANGle ----------| -| | | |--|--- RATio RATio ----------| -| | | ‘----------------+---> Note: Th e TOLERANCE keyword keyword is u sed here t o distinguish distinguish between th e ecc eccent ricity ricity limit wh ich ich you you h ave specifi specified ed an d t he actual eccentricity derived derived from from t he st ru ctu ral m odel. 2.2.3 Structural Joints The positio positional nal er rors for for J oints a re m easur ed as divergenc divergences es of of the J oint positions from their owning Nodes. The maximum permissible errors are defined, defined, a s for for Sections, Sections, in ter ms of a J oint oint ’s e c c e n t r i c i t y . Note: J oint oint ecc eccent ricities ricities ar e defined defined separately for Pjoint Pjoint (Prima ry J oint) and Sjoint (Secondary Joint) elements. Keywords: ECCENTRICITY PJOINT SJOINT Description: Th e ECCENTRICITY PJOINT a n d ECCENTRICITY SJOINT commands specify specify th e maximu m per missible dista dista nce between th e position position of of a Pr imary J oint or a Seco Secondar y J oint, respective respectively ly,, and th at of its its ownin g Node befo before re a diagnostic message is outpu t. Examples: ECC EC C PJ PJOI OINT NT 1 (Defau (Default lt) ) Maximum Maximum error in P rimar y Joint positio position n is 1 mm ECC EC C SJ SJOI OINT NT 1 (Defau (Default lt) ) Maximum error in Secondary Joint position is 1 mm ECC EC C PJ PJOI OIN N 0. 0.1 1 IN INCH CH Maximu Maximu m er ror in P rimar y J oint positio position is 0.1 inch inch 2-6 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking ECC EC C PJ PJOI OIN N DE DEFA FAUL ULT T Resets Resets perm issible issible Pr imary J oint err or t o 1 mm ECC EC C SJ SJOI OIN N DE DEF F Resets permissible Secondary Joint error to 1 mm C om o m m a n d S yn yn t a x : >-->--- ECCent ECCentric ricity ity ---+----+--- PJOInt PJOInt ---. ---. | | ‘--‘--- SJOInt SJOInt ---+----+--- ----. ----. | | ‘--- DEFault DEFault ---+---> ---+---> Querying: Q ECCent ECCentric ricity ity ---+----+--- PJOInt PJOInt ---. ---. | | ‘--- SJOInt SJOInt ---+---> ---+---> 2.2.4 Structural Fittings The positio positiona na l errors for for Fittings a re m easur ed as divergenc divergences es of th e Fitt ing positio positions ns from t he N eutr al Points of the a tt ached Sectio Sections. ns. The maximum perm issible issible err ors ar e defined, defined, a s for for S ections, ections, in ter ms of a Fitt ing’s ing’s eccentricity . Keywords: ECCENTRICITY FITTING Description: Th e ECCENTRICITY FITTING command specifies the maximum perm issible issible distan ce between th e positio position n of a F ittin g and t ha t of its at ta ched Section Section before before a dia gnostic messa ge is is outpu t. Examples: ECC FITTING 1 (De fault ) Maximum Maximum error in Fitting positio position n is 1 mm ECC EC C FI FITT TT 0. 0.5 5 IN INCH CH Maximum err or in Fitt ing positio position n is 0.5 inch inch ECC EC C FI FITT TT DE DEF F Resets perm issible issible Fitt ing position position error t o 1 mm C om o m m a n d S yn yn t a x : >-->--- ECCent ECCentric ricity ity --- FITTi FITTing ng ---+----+--- ----. ----. | | ‘--- DEFault DEFault ---+---> ---+---> Querying: Q ECCentri ECCentricity city FITTing 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 component s an d tu be in th is section section app ly equally to han ger co components an d r od. In order to warn you about potential problems in the practical assembly of pipework pipework sections, sections, th e dat a consist consist ency checks checks outpu t a diagnostic message if th e lengt lengt h of tu be joi joinin nin g any pa ir of componen omponen ts is less tha n a p rescribed minimum . The minimum allowed allowed will will norm norm ally be dependent dependent upon th e tube diameter. An incorrectly positioned ATTA (off the implied tube) may also give rise to a ‘minim ‘minim um tu be length length ’ err or. You will will also be warn ed if the design a ngle for 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, specif specifies ies the m inimu m a ccepta ccepta ble tu be lengt lengt h wh ich ich is app licable licable to all tu be diameter s which which h ave not been more specifically set. Examples: TOL TO L TU TUBE BE 10 100 0 (Defau (Default lt) ) Minimum accepta accepta ble length is 100 mm TOL TO L TU TUBE BE DE DEFA FAUL ULT T Minimum accepta accepta ble length is 100 mm TOL TO L TU TUBE BE 6 IN INCH CH Minimu m a ccepta cepta ble length length is 6 inches inches C om o m m a n d S yn yn t a x : >-- TOLera TOLerance nce TUbe TUbe --+---+-- ---. ---. | | ‘-- DEfaul DEfault t --+--> --+--> Querying: >->-- Quer Query y TUbe TUbe --> --> >-- Query Query TOLera TOLerance nce OPTion OPTions s --> (also outputs ATTACHECK an d misalignm misalignm ent sett ings; see Sections Sections 2.1.2 an d 2.2.1, resp ectively) 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 allows you to specify specify diffe differen ren t min imum tu be lengt lengt hs for for differen differen t r an ges of of bore bore diam eter. Ea ch r an ge of of tu be size is specif specified ied by a m inimu m a nd m aximu m bore (not necessarily in in th at order), fol follo lowed wed by th e minimu m tu be length length allowed allowed fo for t ha t range. Up t o ten differen differen t r an ges may be specifi specified. ed. If a t ube diam eter falls falls out side any specif specifie ied d r an ge, then th e cur cur rent default default length length is applied applied (100 mm, un less less t his ha s been overridden overridden by prior use of the TUBE comman comman d). If two or m ore r an ges overlap, overlap, yo you a re war ned but th e ra nges are n ot rejected. rejected. Tube length checks ar e applied in the order in wh ich ich t hey ha ve been sp ecif ecified. ied. Thus , if the bore of a section section of tu be lies within more th an one specif specified ied ran ge, its length will will pass or fail the toleran ce test det ermined by th e first first valid valid r an ge only. only. Examples: TOL TO L TU TUBE BE BO BORE RE 15 25 MI MIN N 15 150 0 All tubes with with bores bores in t he r ange 15-25 15-25 mm m ust be at least 150 mm long long TOL TU BO 25 15 150 The sam e as th e preceding preceding examp le. The ma ximum bore is given given before t h e minimum bore bore a nd th e optio optional MINIMUM (length) (length) co comma nd word word has been omitted. TOL TU BO 2 IN 4 IN MIN 12 IN All tu bes with with bores in th e ran ge 2-4 inches mu st be at least 12 inches long long INCH DI INCH DIST ST TOL TU BO 2 4 MIN 12 The same as th e precedi preceding ng example, example, except except th at t he cur cur rent distance un its ar e now inches TOL TO L TU TUBE BE DE DEFA FAUL ULT T Resets Resets minimum length t o 100 100 mm for a ll bore sizes sizes regar dless of an y ranges previously defined separately C o m p l e x E x a m p le : The followi following ng s equ ence: TOL TOL TOL TOL T TU UBE 500 TUBE BORE 15 25 MINIMUM 100 TU BO 25 50 MIN 150 BO 50 TU BO 200 400 750 100 MIN 3 00 would would cau cau se subsequent checks checks to report tu be lengths lengths less tha n t he permitt ed minim a in th e follo following wing circumst circumst an ces: ces: • For bores between 15 mm a nd 25 mm , if 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 if length is <150 mm • For bores between 50 mm a nd 100 mm , if if length is <300 mm • For bores between 200 mm a nd 400 mm , if if length is <750 mm • For a ll oth oth er (un specifi specified) ed) ran ges, if if length length is <500 mm The latter case would would apply to bo bores less than 15mm, greater t ha n 400mm, and within th e ran ge 100mm to 200mm. C om o m m a n d S yn yn t a x : .------------------------<------------------------. / | >-- TOLerance TUbe --*-- BOre --+-- MINimum --. | | | | | | ‘-------------+-- --| | | ‘-- DEfault ----------------------------------------+--> Querying: >->-- Quer Query y TUbe TUbe --> --> >-- Query Query TOLera TOLerance nce OPTion OPTions s --> (also out put s ATTACHECK an d misalignment misalignment sett ings) 2.3.3 Specifying Maximum Angles for Bends and Elbows Keywords: MAXANGLE Description: The design an gle for for ea ch pu lled lled bend or elbow, elbow, tak en from th e settin g of its ANGL attribute, is checked against a predefined maximum an gle. A diagn diagn ostic messa ge is out out put if th e design an gle is is too lar lar ge. The defau defau lt setting for for th e maximum permitt ed an gle gle is 90°, 90°, but you you ma y specif specify y any limit with in th e ra nge 0° (i.e (i.e.. str aight tu be only) only) to 180° (i.e. (i.e. U-bend s a llowed). llowed). Examples: MAXANG MAXANGLE LE 45 C om o m m a n d S yn yn t a x : >-->--- MAXAN MAXANGLE GLE --- value ---> Querying: Q MAXANGle 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 llows you you t o reset defau lts for, for, or qu ery, all dat a cons cons istency checking checking options options for for Tu bes at t he sa me time. Examples: TOL OPTION OPTIONS S DEFAUL DEFAULT T Resets the following data-checking parameters: • Offset Offset toleran ce to 1 m m • Angle tolerance to 0.0573 degrees • Rat io toleran toleran ce to 0.001 • Maxan gle sett ing to 90 degrees degrees • Minimum tu be length length for for a ll bores to 100 100 mm • ATTACHECK option option t o ON C om o m m a n d S yn yn t a x : >-- TOLer TOLeranc ance e OPTion OPTions s DEFau DEFault lt --> Querying: >-- Query Query TOLera TOLerance nce OPTion OPTions s --> Outpu ts th e cur cur rent settings fo for all data checking checking param eters. The The para meters are output output in the curr curr ent units. Q u e r y i n g E x a m p l e s: s: With With all defau defau lt sett ings in forc force, e, the outpu t r esultin g from from a Q TOL OPT comman d will show one one of th e follo following wing sets of values (depend ing u pon t he current units): M M Bo B o r e s a n d D is is t a n c e s : Minimu Mini mum m tu tube be le leng ngth th Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 : : : : : : 100 mm 100 1 mm 0 .0 573 0 .0 01 90 ON 2-11 Data Consistency Checking I N CH CH B o r e s a n d D i s t a n c e s : Mini Mi nimu mum m tu tube be le leng ngth th Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking : : : : : : 3.9 3. 9 in 0 in 0.05 73 0.00 1 90 ON F I N C H B o r e s a n d D is is t a n c e s : Minimu Mini mum m tu tube be le leng ngth th Tolerance Offset Tolerance Angle Tolerance Ratio Maximum Angle Atta checking 2.5 : : : : : : 3.15/1 3.15 /16 6 0. 1/32 0.05 73 0.00 1 90 ON Specifying Minimum and Maximum Section Lengths The derived lengths of structural Sections are checked against predefined minimum an d ma ximum ximum values and a diagnostic diagnostic message is is output if an actual length falls outside these limits. Keywords: SECTION DEFAULT RESET Description: Th e SECTION comm comm an d allows allows you you t o specify specify minim um an d ma ximum accepta accepta ble lengths for for Sections. Sections. You ma y set a single ra nge of accepta accepta ble length length s for for a ll unspecified types of Section Section by usin g th e SECTION DEFAULT option, 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). types). The standa rd default ra nge of of perm issible issible length s for for all un specifi specified ed t ypes of Section Section is from zero minimum t o 10000 10000 mm maximum . Examples: SECT SE CTIO ION N DE DEFA FAUL ULT T 10 1000 00 95 9500 00 Length s of all types of of Sec Section mu st be in t he r an ge 1000–9500 1000–9500 mm u nless separ at ely specif specified ied by a SECT generic_type option ption (as illust illust ra ted in t he follo following wing exa mp les) SECT SE CT CO COLU LUMN MN 15 1500 00 75 7500 00 Column lengths Column lengths mu st be in th e ra nge 1500–750 1500–7500 0 mm ; lengths lengths of other other types of Sec Section tion m ust be with with in th e cur cur rent defau defau lt ra nge SECT BEAM 42 IN 9 FT Beam lengt hs m ust be in in t he r an ge 42 inches to 9 feet; length length s of other types of of Sec Section tion m ust be with with in th e cur cur rent defau defau lt ra nge 2-12 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking SECT SE CT CO COLU LUMN MN 0 12 1250 500 0 BE BEAM AM 87 8750 50 10 1000 00 Column lengths must be in Column in t he ra nge 0–12500 0–12500 mm; Beam lengths mu st be in th e ra nge 1000–8750 mm; length length s of all oth oth er t ypes of of Section Section mu st be with with in the cur cur rent default ran ge Note: As illustr illustr ated in th e last example, yo you m ust always enter t w o values (a m inimum an d a maximum setting), setting), even even if one one of th ese is is a cur rent default valu e (0 (0 mm , say). say). You You ma y, however, however, enter th em in eith er order (i.e. (i.e. minim um value first first or maximu m value first). SECT SE CT DE DEF F RE RESE SET T Length s of all types of Section Section mu st be in t he r an ge 0–10000 0–10000 mm u nless separ at ely specif specified ied by a SECT generic_type option option (i.e. (i.e. this comm comm an d r esets th e original original default set tings) SECT SE CT CO COLU LUMN MN RE RESE SET T Column lengths Column lengths mu st be in th e ran ge 0–100 0–10000 00 mm; the cur cur rent settings fo f or other t ypes of of Section Section ar e not cha cha nged by this comm comm an d SECT SE CT CO COL L RE RESE SET T BE BEAM AM RE RESE SET T Column a nd Beam lengths mu st be in the ra nge 0–10000 Column 0–10000 mm (Note (Note th at t he RESE T comma comma nd word m ust be repea ted for for ea ch type of Section) Section) SECT SECT RESET RESET Lengths of a ll types of Section Section mu st be in t he r an ge 0–10000 0–10000 mm (i.e. (i.e. this resets the original default settings and cancels any individual settings for specific types of Section) C om o m m a n d S yn yn t a x : .---------------------------------------. / | >--- SECTion ---+---*--- DEFault ---. | | | | | | ‘--- word -----------+-+--- --- ---| ---| | | | | ‘--- RESet ---------------+---> ‘--‘--- RESet RESet ---> ---> where word is an y valid Section Section GTYPE GTYPE which confo conform rm s with th e Design DB. Querying: .----------. / | Q SECTion SECTion ---+---* ---+---*----- word ---+---. | | |--- DEFault DEFault ---------------| | | | ‘--------------------+---> Q u e r y i n g E x a m p l e s: s: Q SE SECT CT DE DEFA FAUL ULT T Gives Gives settings fo for cur rent defau defau lt ra nge Q SE SECT CT BE BEAM AM Gives Gives sett ings for for Bea ms only PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-13 Data Consistency Checking 2.6 Q SE SECT CT BE BEAM AM ST STRU RU CO COL L Gives Gives settings fo for th e th ree n amed t ypes of of Section Q SE SECT CT Gives settings for any specifically-defined types plus defau lt sett ings app licable licable to oth oth er Sections Sections Specifying User-Defined SKEYs Acceptable in Data Checks The symbol used by ISODRAFT ISODRAFT to repr esent a par ticular piping componen componen t on an isometr isometr ic dra wing is is determ ined by its s y m b o l k e y (SKEY att ribute Reference nce Manual for sett ing). ing). (See (See th e IS ODRAFT Refere for a full explana tion of th is concept.) Keywords: TOLERANCE CATALOGUE SKEY Description: When a d at a consistency check check is carr ied out out , th e SKEY (if (if an y) for for each componen componen t is checked to see if it is of a st an dar d t ype. This synt ax lets you specify specify user -defined -defined SKE Ys so th at th ey do not not genera genera te er rors du ring da ta consistency chec checks. ks. Examples: TOL TO L CA CATA TA SK SKEY EY ’J ’JIM IM’ ’ ’F ’FRE RED’ D’ .. ... . Componen ts with th e us er -defined -defined S KEYs ‘J ‘J IM’, IM’, ‘FRE ‘FRE D’ etc. will not generate errors caused by unrecognised SKEYs. C om o m m a n d S yn yn t a x : .--------. / | >-- TOLera TOLerance nce CATAlo CATAlogue gue SKEY SKEY --*---*-- text --+--> (Note tha t text is case-sensitive; case-sensitive; SKEYs ar e usu ally, but not n ecessar ecessar ily, ily, uppercase chara cters.) Querying: >-- Query Query TOLera TOLerance nce CATAlo CATAlogue gue SKEY SKEY --> Outpu ts cur rent list list of user-defined user-defined SKEYs SKEYs t o be igno ignored red 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 When th e CHECK comma nd is give given, n, DESIGN scans th e relevan relevan t DBs t o extr extr act the a ppropriate Design Design an d Cata logue logue info inform ation and carr ies out out th e deta iled iled checking checking opera tions described in th e preceding sections. sections. Whenever a design inconsist inconsist ency or or er ror is foun foun d, a diagnostic message is out out put to th e screen (REQUESTS r egion) egion) or to a file. file. It is t hese m essages which ar e explained in th is section. section. Note: The diagnostic messa ges will often often incorp incorp orat e specific specific referen referen ces (nam e, referen referen ce nu mber et c.) c.) to the element s found found t o be in error (although t he tr ue err ors m ay be due to adjacent adjacent elements). These These specifi specificc referen referen ces ha ve genera lly been been omitt ed from th e examp le messa ges listed listed in t he follo following wing subsections. If th e checking checking procedur procedur es ar e completed completed with with out an y errors being detected, the message *--* *-* NO DAT DATA A INCO INCONS NSIS ISTE TENC NCIE IES S *--* *-* will will be out out put . 2.7.1 Global Diagnostics R 10 BAD OWNER REFERENCE The owner owner reference refers refers eith er t o a n onexisten onexisten t element or to one one which does not cont cont ain t he r equired element in its list par t. The occ occur ren ce of of th is error implies implies th at corr upt ion ion of one one or m ore DBs h as t aken place. place. 2.7.2 Branch-Specific Diagnostics Branch Head Errors The foll followi owing ng diagn ostics ostics a pply only only to th e Hea d of a Bra nch: A 10 HEAD REFERENCE NOT SET The H ead r eferen eferen ce should only be un set (i.e. (i.e. nu ll) if th e Hea d Connection Connection Type HCONN is set to OPE N, VENT, VENT, CLOS or DRAN. DRAN. A 20 20 HEA HEAD REFE REFERE RENC NCE E POIN POINTS TS TO TO NONE NONEXI XIST STEN ENT T ELE ELEME MENT NT This err or would would r esult from th e deletion deletion of a componen componen t, such a s a N ozzle ozzle,, to which th e Head of the Bra nch was originally connected. connected. A 30 BAD HEA HEAD RE RETURN REFE EFERENC ENCE The Hea d is connected connected to an element which does does not refer back to the Bra nch. This can can occur when t he H ead of a Br an ch is co conn ected ected t o another Bran ch, implying implying th at a Tee should be placed placed somewh somewh ere along the second second Br an ch. The 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 100 HEA HEAD TER TERMI MINA NAL L PRO PROBL BLEM EM WITH WITH SPRE SPREF F Either the Head t erminal has an unset SPREF or th e SPREF points points to a nonexistent nonexistent SPCOM. A110 110 HEA HEAD TER TERMI MINA NAL L PROB PROBLE LEM M WITH WITH CATR CATREF EF Either t he Head t ermina l has an un set CATREF CATREF or or t he CATREF CATREF points points to a nonexistent Catalogue component. A120 HEA HEAD TERM TERMIN INAL AL PROBL PROBLEM EM IN IN ACC ACCESS ESSIN ING G P-POI P-POINT NTS S Ther e is a Ca ta logue logue problem in accessing accessing th e p-poi p-point nt s of th e Head t erm inal. A130 HEA HEAD TERMI TERMINA NAL L PROB PROBLEM LEM,, P-POIN P-POINT T NO.n NO.n DOES DOES NOT NOT EXIST EXIST A requ ired p-point p-point of the Hea d ter min al does not exist exist in th e set of p-point p-point s. A200 200 DIRECT DIRECTION ION HDIR HDIR NOT NOT SAME SAME AS AS TERMI TERMINA NAL L DIREC DIRECTI TION ON If th e Head is conn conn ected ected t o a t erm inal, such as a Nozzle Nozzle or Tee, Tee, then th e direction direction H DIR should always be identical to th at of th e appr opr iate p-point p-point of the term inal. inal. A210 POSIT POSITION ION HPOS HPOS NOT NOT SAME SAME AS AS TER TERMIN MINA AL POSI POSITI TION ON If th e Head is conn conn ected ected t o a t erm inal, such as a Nozzle Nozzle or Tee, Tee, then th e position position HP OS should always be identical to th at of th e appr opriate p-point p-point of the term inal. inal. A220 220 HBOR HBORE E NOT NOT SAME SAME AS TER TERMI MINA NAL L BOR BORE E If th e Head is conn conn ected ected t o a t erm ina l, such a s a Nozzle Nozzle or or Tee, then t he bore HBORE sh ould always be ident ical ical to tha t of th e appr opriate p-point p-point of th e terminal. A230 A230 CONNECT CONNECTION ION TYPE TYPE HCONN HCONN NOT SAME SAME AS AS TERMIN TERMINAL AL CONNECT CONNECTION ION TYPE TYPE If th e Head is conn conn ected ected t o a t erm inal, such as a Nozzle Nozzle or Tee, Tee, then th e connection type HCONN should always be identical to that of the appropriate p-point of the terminal. A300 REFE EFERENC ENCE HST HSTU UBE UN UNSET SET There is more more th an 1mm of tu be between between th e Head an d th e p-arr p-arr ive ive of of th e first first Component Co mponent (or t he Tail), Tail), but HSTUBE is u nset. A310 310 REFER REFERENC ENCE E HSTU HSTUBE BE REF REFERS ERS TO A NONE NONEXIS XISTE TENT NT SPCOM SPCOM This m ay occ occur if par t of the S pecif pecific icat at ion ion h as been deleted. A320 320 HSTU HSTUBE BE PRO PROBL BLEM EM,, CATR CATREF EF IN IN SPCO SPCOM M IS UNS UNSET ET This indicates an err or in th e Specif Specific icat at ion. ion. A330 330 HSTUB HSTUBE E PROBL PROBLEM, EM, CA CATR TREF EF IN THE THE SPCOM SPCOM REFE REFERS RS TO TO NONEXI NONEXIST STENT ENT Catalogue COMPONENT This ma y oc occur if par t of th e Cat alogue alogue h as been d eleted or or if the CATREF is unset. 2-16 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking A340 A340 HSTUBE HSTUBE PROBLEM, PROBLEM, GTYPE GTYPE OF OF CAT CATAL ALOGUE OGUE COMPONEN COMPONENT T IS IS NOT NOT SET TO TUBE The componen componen t pointed t o by HSTUBE is n ot of of type TUBE in t he Cat alogue. alogue. A350 350 HSTU HSTUBE BE PROB PROBLE LEM M IN ACCES CCESSI SING NG P-PO P-POIN INT T There is a Ca ta logue logue problem in accessing accessing a p-point p-point of the tu be pointed pointed t o by HSTUBE. A400 400 HBOR HBORE E NOT NOT SAME SAME AS BOR BORE E OF OF HST HSTUB UBE E The bore of any tube leading from the Head, determined from the Catalogue, should always be ident ical ical to HBORE. A410 410 HCON HCON NOT NOT COMPA COMPATI TIBL BLE E WITH WITH CONN CONNECT ECTION ION TYPE TYPE OF HST HSTUB UBE E The connectio connection n t ype of of an y tube leading from from t he H ead, deter mined from th e Cat alogue, alogue, should be compat compat ible ible with HCONN . A420 420 ISPEC ISPEC REFERE REFERENC NCE E POIN POINTS TS TO NONEXI NONEXIST STEN ENT T ELE ELEMEN MENT T This er ror would occ occur if, if, for for examp le, the In sula tion Specifi Specificcat ion ion point point ed to by ISPEC ha d been deleted. A430 430 INSUL INSULAT ATION ION CANN CANNOT OT BE SELECT SELECTED ED USING USING HBORE HBORE Ther e is no suita ble insu lation in th e Cata logue logue for for the combina combina tion of of temperature TEMP a nd bore HBORE. HBORE. Branch Tail Errors The follo following wing diagn ostics apply only to th e Tail of a Bra nch: B 10 TAIL REFERENCE NOT SET The Ta il referen referen ce sh ould only be un set (i.e. i.e. zero) if the Ta il connectio connection n type TCONN is set to OPEN , VENT, VENT, CLOS or DRAN. DRAN. B 20 TAIL TA IL REF REFER EREN ENCE CE POI POINT NTS S TO NONE NONEXI XIST STEN ENT T ELE ELEME MENT NT This err or would would r esult from th e deletion deletion of a componen componen t, such a s a N ozzle ozzle,, to which which t he Ta il of of the Br an ch wa s origina origina lly lly connected. connected. B 30 BAD TAIL RET RETU URN REF REFERENC ENCE The Tail is connected connected to an elemen t wh ich ich does not r efer efer ba ck t o the Bra nch. This can can occur ccur when t he Tail of of a Br an ch is conn conn ected ected t o an other Br an ch, implying implying th at a Tee should be placed placed somewh somewh ere along the second second Br an ch. The The error can also occur when two or more branches are inadvertently connected to the same t erminal. B100 B100 TAIL TA IL TERM TERMIN INA AL PRO PROBL BLEM EM WITH WITH SPRE SPREF F Either th e Tail Tail terminal has an unset SPREF or t he SPREF points points to a nonexistent nonexistent SPCOM. B110 B110 TAIL TER TAIL TERMI MINA NAL L PROB PROBLE LEM M WITH WITH CATR CATREF EF Either t he Tail terminal has an un set CATREF CATREF or the CATREF CATREF point point s to a nonexistent Catalogue component. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-17 Data Consistency Checking B120 B120 TAIL TA IL TERMI TERMINA NAL L PRO PROBL BLEM EM IN IN ACC ACCESS ESSIN ING G P-POI P-POINT NTS S Ther e is a Cata logue logue pr oblem oblem in a ccessing th e Tail p-poi p-point nt s. B130 B130 TAIL TA IL TERM TERMINA INAL L PROB PROBLEM LEM,, P-POIN P-POINT T NO.n NO.n DOES DOES NOT NOT EXIST EXIST A requ ired p-point p-point of th e Tail term inal does not exist. exist. B200 B200 DIRECT DIRECTION ION TD TDIR IR NOT NOT SAME SAME AS AS TERMI TERMINA NAL L DIRE DIRECT CTION ION If the Tail is connected connected to a ter mina l, such such a s a N ozzl ozzlee or or Tee, then th e direction direction TDIR sh ould always be identical to th at of th e appr opriate p-point p-point of the term inal. inal. B210 B210 POSIT POSITION ION TPOS TPOS NOT NOT SAME SAME AS AS TER TERMIN MINA AL POSI POSITI TION ON If the Tail is connected connected to a ter mina l, such such a s a N ozzl ozzlee or or Tee, then th e position position TPOS sh ould always be ident ident ical ical to tha t of th e appr opr iate p-point p-point of th e terminal. B220 B220 TBOR TB ORE E NOT NOT SAME SAME AS TER TERMI MINA NAL L BOR BORE E If the Tail is connected connected to a ter mina l, such a s a N ozzle ozzle or Tee, th en t he bore TBORE should always be identical to th at of th e appr opriate p-point p-point of th e terminal. B230 B230 CONNECT CONNECTION ION TYPE TYPE TCONN TCONN NOT SAME SAME AS AS TERMIN TERMINAL AL CONNECT CONNECTION ION TYPE TYPE If the Tail is connected connected to a ter mina l, such such a s a N ozzl ozzlee or or Tee, then th e connection onnection t ype TCONN TCONN sh ould alwa ys be identical to th at of th e appr opriate p-point of the terminal. Plain Branch Errors The follo following wing diagn ostics ostics can occur occur only for for Br an ches with no piping components: C500 C500 TUBE TOO TUBE TOO SHO SHORT RT BETW BETWEE EEN N HEA HEAD AND AND TA TAIL The distance between the Head position, HPOS, and the Tail position, TPOS, is great great er th an zero zero and less tha n t he specif specified ied minimu minimu m tu be length length (defau (defau lt: 100mm). C510 C510 BAD BAD HEA HEAD D TO TO TA TAIL GEOM GEOMET ETRY RY Eith er t he Hea d position, position, HP OS, does does not lie at a positive positive distan ce along the line line t hr ough TPOS in t he dir ection ection TDIR or or t he Tail position, position, TPOS, does does not lie lie at a positive positive distan ce along along th e line line th rough H POS in t he direction direction H DIR. The follo following wing illust illust ra tion sh ows ows some t ypical ypical exam ples: 2-18 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking C520 HBORE ORE NOT NOT SAME AS TB TBORE When th ere ar e no co components on t he bra nch, the H ead bore, HBORE, should be identical to th e Tail bore, bore, TBORE. C530 C530 HCON HCONN N IS IS NOT NOT COMP COMPA ATIBL TIBLE E WIT WITH H TCO TCONN NN This implies tha t t he H ead is conn conn ected ected dir ectly ectly to the Ta il with n o Tube or piping compo componen nen ts in between; hence the H ead conn conn ection ection type, HCONN, mu st be compa compa tible with with th e Tail connectio connection n t ype, TCONN. TCONN. C540 C540 THIS TH IS BRA BRANCH NCH HAS HAS NO COMP COMPON ONEN ENTS TS This does does not necessarily necessarily indic indicate ate a n er ror. It is merely out out put as a warn ing to the designer. 2.7.3 Component-Specific Diagnostics The follo following wing err ors ap ply to ind ind ividua ividua l piping component component s an d, in some cases, to th eir adjacent conn conn ections. ections. Some Some of th e err ors also apply to han ger componen omponen ts an d/or d/or to Nozzles. Nozzles. All-Component All-Component Diagnostics These ar e applicable applicable to any componen componen t, regar dless of of its its position position in th e network: D100 REFE EFERENC ENCE SP SPREF UNSET NSET This probably probably mean s th at the designer designer h as forgo forgotten tten to selec selectt t he piping component. D110 D110 REFER REFERENC ENCE E SPREF SPREF REFERS REFERS TO A NONNON-EXI EXIST STENT ENT SPCOM SPCOM This m ay occur occur if par t of the s pecif pecific icat at ion ion ha s been deleted. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-19 Data Consistency Checking D120 D120 SPRE SPREF F PROB PROBLE LEM, M, CA CATR TREF EF IN IN SPCO SPCOM M IS UNS UNSET ET This indicates an err or in th e Specif Specific icat at ion. ion. D130 D130 SPREF SPREF PROB PROBLEM LEM,, CATR CATREF EF IN THE THE SPCOM SPCOM REFE REFERS RS TO NON NON-EX -EXIST ISTEN ENT T CATALOGUE COMPONENT This ma y oc occur if par t of th e Cat alogue alogue h as been d eleted or or if the CATREF in the SPCOM is is unset . D130 SPREF SPREF PROBL PROBLEM, EM, GTYPE GTYPE OF CATA CATALOGU LOGUE E COMPON COMPONENT ENT IS NOT NOT SAME SAME AS AS TYPE OF DESIGN DATA COMP0NENT The GTYPE GTYPE of the Cat alogue alogue co component must be th e same as t he t ype of of the piping piping Component Component in th e design design dat a. D150 D150 CATR CATREF EF PRO PROBL BLEM EM IN IN ACC ACCES ESSI SING NG P-P P-POI OINT NTS S An er ror h as been found in accessing accessing th e p-points p-points of the Cat alogue alogue componen componen t point point ed t o by CATREF. CATREF. D160 D160 REFE REFERE RENC NCE E CAT CATREF REF UNSE UNSET T This ap plies only only to Nozzle Nozzles, s, for for which th e CATREF CATREF m us t be set . D170 D170 REFERENC REFERENCE E CAT CATREF REF REFERS REFERS TO A NON-EXIS NON-EXISTEN TENT T CATA CATALOGU LOGUE E COMPONENT This ma y occ occur ur if par t of th e Cata logue logue ha s been deleted. deleted. It a pplies only to Nozzles. D200 D200 ARRIVE RRIVE P-PO P-POINT INT NOT IN PTS PTSET ET OF OF CATA CATALO LOGUE GUE COMP COMPONE ONENT NT The ar rive p-po p-point int n umber does does not exist exist in th e PTSET of th e Cata logue logue Component. D210 D210 LEA LEAVE P-PO P-POIN INT T NOT NOT IN PTSET PTSET OF CA CATA TALO LOGUE GUE COMPO COMPONEN NENT T The leave p-poi p-point nt nu mber d oes oes not exist exist in t he P TSET of th e Cata logue logue Component. D300 REF REFERENC ENCE CRE CREF F NO NOT SET SET Multi-way Componen Componen ts ma y be left left u nconn nconn ected ected only if the conn conn ection ection type of th e relevant p-point p-point is OP EN, CLOS, VENT, VENT, DRAN DRAN or NULL. D310 D310 REFER REFERENC ENCE E CREF CREF POINT POINTS S TO TO NONNON-EXI EXIST STENT ENT BRANC BRANCH H This ma y occ occur ur if th e Bran ch wh ich ich is pointed t o by by the CREF ha s been deleted. D320 D320 BAD BAD CRE CREF F RET RETUR URN N REF REFER EREN ENCE CE This ma y occ occur ur if th e Bran ch wh ich ich is pointed t o by by the CREF ha s been reco reconn ected ected t o another term inal. D330 D330 2-20 REFE REFERE RENC NCE E CRF CRFA n NOT NOT SET SET An en tr y in th e co conn ectio ection n reference reference arr ay ma y only only remain un set if the correspondin g p-poi p-point nt in t he Ca ta logue logue does not exist or if th e connectio connection n t ype of th e correspondin correspondin g point point is VENT, VENT, OPE N, CLOS or or N ULL. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking D340 D340 REFER REFERENC ENCE E CRFA CRFA n POINT POINTS S TO NON-EX NON-EXIST ISTENT ENT BRA BRANCH NCH This ma y oc occur if the Bra nch pointed t o by the n th reference in in t he conn conn ection ection reference reference arr ay ha s been deleted. D350 D350 BAD BAD CRF CRFA A n RET RETURN URN REF REFER EREN ENCE CE This ma y oc occur if th e elemen elemen t pointed t o by the n th reference in in t he conn conn ection ection reference reference arr ay ha s been reconn reconn ected ected to a t hird Br anch. D400 D400 ARRIVE ARRIVE TUBE TUBE [ROD] [ROD] LESS LESS THAN THAN TUBE TUBE [ROD] [ROD] MINIMUM. MINIMUM. ACTUA ACTUAL L TUBE TUBE [ROD] LENGTH IS ... The dista nce between between t he ar rive p-poi p-point nt of th is compo componen nen t a nd t he leave ppoint point of the previous previous component (or Head) is greater th an zero zero an d less th an th e specif specified ied minimu m t ube [rod] length (defau (defau lt: 100mm 100mm ). D410 D410 BAD BAD ARR ARRIVE IVE GEOMET GEOMETRY RY + detai details ls of of geom geometr etric ic erro errors rs The position position a nd direction direction of the a rr ive p-poi p-point nt of th is component component ar e not correct with respect t o the leave p-point p-point of th e previous previous component (or (or H ead). The er ror could could be cau sed by incorr incorr ect ect p ositioning ositioning of th is component component , th e previous previous component (or (or H ead) or or both . The follo following wing illust illust ra tion sh ows ows some t ypical ypical exam ples: D420 D420 BAD BAD ARRIV RRIVE E BOR BORE E [RO [ROD D DIA DIAME METE TER] R] The bore of th e ar rive p-point p-point of th is component component is not equa l to the bore of th e preceding tu be or, if if this componen componen t is n ot preceded by tube, to th e bore bore of th e leave p-point p-point of th e pr evious evious componen componen t (or (or HBORE ). D430 D430 BAD BAD ARR ARRIV IVE E CON CONNE NECT CTIO ION N TYP TYPE E The conn conn ection ection t ype of of the a rr ive p-poi p-point nt of th is component component is not compa compa tible with t he pr eceding eceding tu be or, or, if th is compo componen nen t is not pr eceded eceded by tube, to th e connection onnection type of the leave p-point p-point of th e pr evious evious componen componen t (or (or HCONN ). PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-21 Data Consistency Checking D500 D500 REFE REFERE RENC NCE E LSTU LSTUBE BE [LSR [LSROD OD]] UNSE UNSET T The user ha s probably fo forgotten to selec selectt t he piping/ha piping/ha nger Component . D510 D510 REFER REFERENC ENCE E LSTUBE LSTUBE [LS [LSROD ROD]] REFERS REFERS TO TO A NON-E NON-EXIS XISTE TENT NT SPC SPCOM OM This m ay occ occur if par t of the S pecif pecific icat at ion ion h as been deleted. D520 D520 LSTU LSTUBE BE [LS [LSROD ROD]] PROB PROBLEM LEM,, CATR CATREF EF IN IN SPCOM SPCOM IS UNSE UNSET T This indicates an err or in th e Specif Specific icat at ion. ion. D530 D530 LSTUBE LSTUBE PROBLEM, PROBLEM, CATRE CATREF F IN IN THE THE SPCOM SPCOM REFER REFERS S TO TO NON-EX NON-EXIST ISTENT ENT CATALOGUE COMPONENT This ma y oc occur if par t of th e Cat alogue alogue h as been d eleted or or if the CATREF in the SPCOM is is unset . D540 LSTUBE LSTUBE PROBLEM, PROBLEM, GTYPE GTYPE OF OF CAT CATAL ALOGUE OGUE COMPONEN COMPONENT T IS IS NOT NOT SET TO TUBE The componen componen t pointed t o by LSTUBE is not of of type TUBE TUBE in t he Cat alogue. alogue. D550 D550 LSTU LSTUBE BE [LSRO [LSROD] D] PROBL PROBLEM EM IN IN ACC ACCESS ESSIN ING G PPOI PPOINT NTS S Ther e is a Cat alogue alogue pr oblem oblem in a ccessing a p-point p-point of th e tu be/rod be/rod point point ed to by LSTUBE [LSROD]. D600 D600 LEAVE LEAVE BORE BORE [DIAMETE [DIAMETER] R] NOT NOT SAME SAME AS BORE [DIAMETE [DIAMETER] R] OF LSTUBE LSTUBE [LSROD] The bore of of th e leave p-poi p-point nt of th is Componen Componen t is n ot th e sam e as t he bore of th e tu be/rod be/rod follo following wing th e Componen Componen t. D610 D610 LEAVE LEAVE CONN CONNECT ECTION ION TYPE TYPE NOT NOT COMPA COMPATIB TIBLE LE WITH WITH CONNECT CONNECTION ION TYPE TYPE OF LSTUBE [LSROD] The conn conn ection ection t ype of of the leave p-point p-point of th is Componen Componen t is n ot compat ible ible with t he t ube/rod fol follo lowing wing th e component component . D620 D620 INSUL INSULAT ATION ION CANN CANNOT OT BE BE SELECT SELECTED ED USIN USING G LEA LEAVE BORE BORE Ther e is no suita ble insu insu lation in th e Cata logue logue for for th e combinat combinat ion ion of tempera tu re TEMP and th e bore bore of th e leave leave p-po p-point. int. D630 D630 ATTACHME ATTA CHMENT NT TYPE TYPE INVA INVALID LID - MUST MUST BE ONE OF FLOW, FLOW, XXXX, XXXX, SSSS, SSSS, CCCC, CCNN, NUL OR NULL You ha ve set an incorr incorr ect ect TYPE at tr ibute for for a n ATTA. ATTA. D740 D740 ANGLE ANGLE OF COMPON COMPONENT ENT IS GREA GREATER TER THAN THAN MAXIMU MAXIMUM M ANGLE ANGLE SPECIFIE SPECIFIED D IN SPREF The designed a ngle of of a Pu lled lled Bend, E lbow lbow or Weld Weld is great er t ha n is a llowed llowed by th e SPECs. D740 D740 ANGL ANGLE E OF COMPO COMPONEN NENT T IS LESS LESS THA THAN MINIMU MINIMUM M ANGL ANGLE E SPECI SPECIFIE FIED D IN SPREF The designed a ngle of of a Pu lled lled Bend, E lbow lbow or or Weld is less th an is allowed allowed by the SPECs. 2-22 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking D740 D740 ANGLE NGLE GREA GREATE TER R THA THAN m DEGREE DEGREES. S. ACT ACTUA UAL L ANG ANGLE LE IS n. n. The designed designed an gle gle of of a Pu lled lled Bend or or E lbo lbow is greater t ha n t he ma ximu ximu m an gle specif specified ied by th e user (see TOLERANCE MAXANGLE ). End-Component Diagnostics These ar e applicable applicable only only to the last componen componen t in a Br an ch: E700 LEAVE LEAVE TUBE TUBE LESS THAN THAN TUBE TUBE MINIMUM. MINIMUM. ACTUA ACTUAL L TUBE TUBE LENGTH LENGTH IS ... ... The distance between between the leave p-po p-point int of th e cur cur rent component a nd t he ta il positio position, n, TPOS, is is greater th an zero and less less th an th e specif specified ied minimum t ube length (defau (defau lt: 100mm). E710 BAD LE LEAVE GE GEOMETRY The position position a nd direction direction of the leave p-point p-point of th is co componen t a re n ot correct with resp ect ect t o the position, position, TPOS, a nd direction, direction, TDIR, of of the t ail. The er ror could could be cau sed by incorr incorr ect ect p ositioning ositioning of th is compo componen nen t, t he Ta il, il, or both . E720 E720 LEA LEAVE BORE BORE NOT NOT SA SAME AS TBO TBORE RE The bore of of the leave p-poi p-point nt of th is compo componen nen t is not t he sa me a s th e ta il bore, TBORE. E730 E730 LEAVE LEAVE CON CONNEC NECTI TION ON TYPE TYPE NOT NOT COMP COMPAT ATIB IBLE LE WIT WITH H TCO TCONN NN The conn conn ection ection t ype of th e leave p-point p-point of th is componen componen t is not compat ible ible with t he t ail connectio connection n t ype TCONN. TCONN. 2.7.4 Structure-Specific Diagnostics The follo following wing abbreviat ions ions a re u sed th roughout th is section section to represen t specifi specificc identifiers identifiers with in th e out out pu t m essages: struc_elem A nam ed st ru ctu ra l elemen elemen t (a specific specific Section, Section, J oint oint , or or Fitting) word A qua lifying lifying PDMS word; word; usu ally an a tt ribut e of of a str uctura l ele element ment in the curren t cont cont ext ext Catalogue/Connectivity Catalogue/Connectivit y Errors SC01 SC010 0 Catr Catref ef/S /Spe pecr cref ef of of struc_elem unset The SPREF for t he n amed st ru ctu ral Sectio Section, n, J oint or F itting does does not point point to a valid co componen t in t he Cat alogue. alogue. SC020 Pline word of struc_elem does not exist The p-line p-line of th e given given n am e can can not be accessed accessed in t he Ca ta logue logue description of th e elemen elemen t. Eith er th is p-line p-line does does not exist exist in t he Cat alogue alogue description or or the st ru ctu ral element element points points to th e wrong wrong Cata logue logue element. 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 p-line in th e owning Section. Section. SC050 SC050 Incompa Incompatible tible Connect Connection ion types types between between struc_elem_1 and struc_elem_2 Self-explanatory. SC060 SC060 Incompat Incompatible ible Connect Connection ion refer reference ences s between between struc_elem_1 and struc_elem_2 Self-explanatory. SC070 struc_elem is not connected Self-explanatory. SC080 SC080 Incom Incompat patib ible le GTYPE GTYPE of struc_elem : word_1 in Design, word_2 in Catalogue The Gener ic Type used to classify classify th e str uctu ra l element element in th e Design Design DB is not th e same as t ha t u sed in the r eference eferenced d Cata logue logue descriptio description. n. SC090 Jline of of struc_elem unset The nam ed stru ctu ra l element element does not not h ave its its J oining Line Line att ribute set, so its position position a nd/or orient orient at ion ion with respect to a conn conn ected ected componen componen t can not be defined. SC100 SC100 INCOMPA INCOMPATIB TIBLE LE ROD ROD DIA DIAMETE METER R BETWEEN BETWEEN name AND name FOR HANGER HEAD AND TAIL The Fitting an d th e Atta Atta between between wh ich ich t he h an ger is to be be co conn ected ected h ave incompatible diameters. SC110 SC110 TBORE TBORE [HBOR [HBORE] E] NOT NOT SAM SAME E AS AS BORE BORE OF OF name The Head/Tail Head/Tail diameter diameter of th e han ger is not not t he sam e as th at of the Fitting to which it is to be conn conn ected. ected. SC12 SC120 0 Catr Catref ef/S /Spe pecr cref ef of of struc_elem refers to a non-existent element The SPREF for t he n amed st ru ctu ral Sectio Section, J oint or F itting does does not point point to a valid co componen t in t he Cat alogue. alogue. Positional Errors SP010 SP010 Discrep Discrepancy ancy between between ends ends of of Jlines Jlines:: word of struc_elem_1 and word of struc_elem_2 The sta rt /end of th e J oining Line Line for for th e na med Sectio Section n does does not ha ve the same point loc locat ion ion as t he end of the J oining Line Line for for th e na med J oint. SP02 SP020 0 Posi Positi tion ons s 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 which a re mean t t o be be co conn ected ected to the n am ed Section, Section, is not positioned positioned with in t he der ived ived length of th e Section. Section. 2-24 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Data Consistency Checking Directional Errors SD010 SD010 Norma Normall to Cu Cutti tting ng plane plane word of struc_elem_1 is perpendicular to Neutral axis of struc_elem_2 This is equivale equivalent nt to saying tha t t he end-cut end-cut ting plane of a Section Section th rough th e point point of connection onnection is effec effectively tively para llel llel to th e neu tr al a xis of of tha t Section. Section. This is not possible, since the in ter section section point point needed t o define define th e position position of th e connectio connection n would th en be at infinity. infinity. SD020 SD020 Norma Normall to Cu Cutti tting ng plane plane word of struc_elem_1 is perpendicular to Origin plane of struc_elem_2 This is equivale equivalent nt to saying tha t t he end-cut end-cut ting plane of a Section 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 section point point needed t o define define th e position position of th e connectio connection n would th en be at infinity. infinity. SD03 SD030 0 Cutt Cuttin ing g plan planes es word of struc_elem_1 and word of struc_elem_2 misaligned The star t an d end cut cut ting planes of of th e named elements ar e not not par allel. allel. SD04 SD040 0 Chec Check k Beta Beta ang angle les s of struc_elem_1 and struc_elem_2 The Beta Angle for for t he n am ed Section Section should be the sa me as t he Beta Angle for for t he conn conn ected ected J oint oint . SD060 SD060 Norma Normall to cuttin cutting g plan plane e 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 point in t he general directio direction n of the oth er en d of th e Section. Section. Eccentricity Errors SE010 Struc_elem diverges from logical model: eccentricity out of range The linear linear displace displacement ment between between t he Attached Neutr al Point Point s on th e extended extended Neut ra l Axis Axis of of the n am ed Section Section an d th e logic logical al line joining joining th e Node positions exceeds the permitted distance. SE020 Struc_elem diverges from logical model: angle out of range The angular deviation deviation between between th e Neutr al axis of of th e nam ed Sectio Section n a nd t he logic logical al line joining joining t he N ode positio positions ns exceeds exceeds th e perm itted am ount . Length Errors SL010 Length of of struc_elem is out of range. Actual length is ... The derived derived length of the na med Sectio Section n is not within t he perm issible issible range applicable to its its type. SL02 SL020 0 Lo Logi gica call leng length th of struc_elem is zero Self-explanatory. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 2-25 3 Clash Detection DESIGN’s DESIGN’s clash detection detection ut ility ility a llows llows you t o check check a ny s pecif pecified ied par ts of th e Design database for clashes (interferences) between individual elements and to report on on th e results. The t ypes of clash ident ified ified by DESIGN depend on two factors: factors: • Th e o b s t r u c t i o n le l e v e ls l s of th e clash clash ing elemen elemen ts • The cur 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 L e v e ls ls All design design pr imitives and a ll cat alogue alogue pr imitives have an obstru ction level level att ribut e (OBST) (OBST) which ha s an integer va lue of 2, 1 or or 0. The value of th e OBST att ribut e defines defines th e physical physical type of obstr obstr uction uction wh ich ich t he primitive represents. For positive positive pr imitives th e effec effects ts ar e a s follo follows: ws: OBST = 2 A h a r d o b s t r u c t i on o n ; the pr imitive imitive repr esents a soli solid d volume, volume, such as a steel beam or a plan t vessel, which has rigid rigid an d impenetr able surfaces. surfaces. OBST = 1 A s o ft ft o b s t r u c t i o n ; the pr imitive imitive represents a volume volume which is not solid solid bu t wh ich ich n eeds to be kept clear clear for for access access pur poses, poses, such such a s an operat ing space space aroun d th e cont cont rol wheel of a valve. O BS BS T = 0 N o o b st s t r u c t io i o n ; the pr imitive imitive represent s a freely accessible accessible vol volum um e, or or is simply a r epresen ta tive symbol. symbol. In addition addition to the obstru ction tion types defined defined by the OBST at tr ibutes, Insu lation lation is treat ed as a special special obstru obstru ction tion t ype in in its own own right. 2. Exten t of Clashing As well well as r ecog ecognising nising t he t hr ee types of of clash clash ing item (har d, soft soft an d insu lation), DESIGN recognises recognises th ree class class es of of clash clash between t hem , depending upon th e degree to whic which th e two primitives primitives intr ude u pon pon each other’s allocated space. These classes are as follows: • (normal) c l a s h ; th e primitive volumes volumes overlap by more tha n a specifi specified ed am oun t. • A t o u c h ; th e primitives either overlap overlap by less tha n a specifi specified ed amount or ar e separat ed at t heir clo closest sest point point by less 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 primitives ar e separa ted at their clo closest point point by more tha n th e amount n ecessary ecessary to co constitu te a touch but less than a specifi specified ed clear clear an ce dista nce. These th ree classes classes a re illustr at ed in Figur e 3-1 3-1 for for th e clash clash specif specificat icat ions: ions: Touch Touch limits: 5 mm overlap overlap to 2 mm gap Clear Clear an ce limit: limit: 8 mm so tha t t he follo following wing criter criter ia ap ply: • If the pr imitives imitives overl overlap ap by m ore t han 5 mm , a clash clash is report report ed • If the pr imitives imitives overlap overlap by less less th an 5 mm , a t ouch is reported • If the primitives primitives do not overl overlap ap bu t a re separa ted by less less tha n 2 m m, a touch is reported • If th e primitives primitives are separa ted by more more th an 2 mm but less less tha n 8 mm , a clear clear an ce is report ed • If the primitives primitives ar e separa ted by more tha n 8m m, no interference interference is found N O T E : The clear clear an ce dista nce, if if set, m u s t be great great er tha n th e touch touch gap. Sett ing th e cleara cleara nce distan ce to zero switches switches off off the clear 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 Touches an d Cleara nces T h e C la la s h D e t e c t i o n P r o c e s s The locat locat ions ions an d dimen sions sions of all design element s ar e defined, defined, for for clash detection detection pur poses, by reference to a s p a t i a l m a p which holds simplified descriptions descriptions of th e componen componen t geometr ies (see (see Section Section 5.7 in P ar t 1). 1). Ea ch elemen elemen t wh ich ich is to be checked checked for for clashes h as its own own geometr y checked checked a gainst th at of all oth oth er element s which ar e specif specified ied by a current o b s t r u c t i o n li li s t . Items which which a re n ot in t he obstruction obstruction list ar e ignored ignored du rin g the clash clash checking opera 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 ection mode. While While in Clash Det ection ection mode, all comman comman ds which you you ent er ar e inter pret ed as being specif specific ic to the clash clash checking checking an d report ing fun ctions, tions, ra th er th an as general Design Design mode co comma nds. To ret ur n from Clash Detection Detection m ode to Design Design mode, use th e EXIT command. Note: 3.2 All clash clash -detection -detection option option s ett ings ar e stored globally, globally, so tha t t hey rem ain in effec effectt from one DESCLASH session to anoth er. Once defined, defined, you you n eed not resp ecif ecify y any of th e option option sett ings un less you you wish t o chan ge them (or (or u nless you you leave and th en ret ur n t o DESIGN). DESIGN). Defining the Obstruction List Keywords: OBSTRUCTION EXCLUDE REMOVE Description: The list of of obstr obstr uctions, defining defining th ose items in t he spa tial ma p again st wh ich ich clash clash es ar e to be be checked, checked, may be built built u p in sta ges. You may ad d items t o, or remove item item s from, from, th e cur cur ren t list in an y of of th e follo following wing wa ys: • By addin g one one or more specified specified Design Design elements • By adding implied implied tube or r od between piping or or str uctura l components • By exc excluding one or more member s owned owned by element s in th e list list • By removing removing items from th e cur cur ren t obstru ction ction list an d/or d/or from th e cur cur ren t exclusion exclusion list list Note that th e cur cur rent obstru ctions tions a nd exclusio exclusions ns a re stored as t wo separa te lists, lists, the effective obstru ction list being th e diff differen ce between the two. The OBSTRUCTION a n d EXCLUDE comma nds add specifi specified ed items t o those lists, lists, bu t do not overwrite a ny existing conten ts. To remove item item s from th e obstr obstr uction uction a nd/or nd/or exclusion exclusion lists, you you m ust do so explic explicitly and sepa ra tely for for each list list by u sing th e REMOVE command. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-3 Clash Detection When you you add any element to the obstru ction tion list, list, all elements elements and prim itives below below the specified specified item (tha t is, all of its m embers ) are au tomat ically ically inco incorpora rpora ted int o th e list. list. By defau defau lt, the obstr uction uction list list cont cont ain s a ll design design elements in th e cur cur rent MDB. If a Bra nch (or (or h igher) element element is added t o th e obstr obstr uction uction list, implied tu be with with in th e Branch is trea ted as pa rt of th e obstru obstru ction. tion. If, If, however, however, individua l piping piping componen componen ts a re a dded to th e list, list, implied tu be connected connected to those components components is n ot included included au toma tically tically and mu st be a dded specific specifically ally if requ ired. The sa me pr inciples inciples apply to implied rod, an d also to implied tube or rod with with in Groups. Only items which ha ve previously previously been ad ded to th e obstr obstr uction uction or exclusion lists may be specified in a REMOVE comman d. Removing Removing an obstr obstr uction uction d oes oes n ot au tomat ically ically remove any exclusions exclusions which were specif specified ied when t ha t obstru ction tion was a dded to th e list. Examples: OBST OB ST AL ALL L Adds every item from from every Design DB in cur ren t MDB t o obstr obstr uction uction list (default) OBST OB ST /P /PUM UMP1 P1 /P /PUM UMP2 P2 /V /VES ESS1 S1 Adds individua individua lly ident ified ified elemen elemen ts t o obstr obstr uction list. OBST /GROUP.MOD2 /GROUP.MOD2 Adds all element s in na med group t o obstr obstr uction uction list. OBST LE OBST LEAV AVE E TU TUBE BE FR FROM OM /F /FLA LAN2 N2 OBST OB ST HE HEAD AD RO ROD D OF /H /HAN ANG1 G1 OBST OB ST LE LEAV AVE E /V /VAL ALV3 V3 IARRI IARRIVE VE /V /VAL ALV5 V5 TA TAIL IL /B /BRA RAN1 N1 Adds ind ividu ividu al length s of implied tube or r od to obstr obstr uction uction list. EXCL EXCL /BRAN3 /BRAN3 /BRAN5 /BRAN5 Excludes Excludes in dividu dividu ally ident ident ified ified element element s from cur cur ren t obstr uction uction list (by add ing th em t o exc exclusion lusion list). list). Note: The nam ed elements elements m ust be members of items already in the obstr obstr uction uction list. EXCL LE EXCL LEAV AVE E TU TUBE BE FR FROM OM /F /FLA LAN2 N2 EXCL EX CL HE HEAD AD RO ROD D OF /H /HAN ANG1 G1 EXCL EX CL LE LEAV AVE E /V /VAL ALV3 V3 IARRI IARRIVE VE /V /VAL ALV5 V5 TA TAIL IL /B /BRA RAN1 N1 Exclud Exclud es individu individu al length s of implied tube or r od from from curr ent obstru ction list. REM RE M OB OBST ST AL ALL L Empties obstruction list. REM RE M OB OBST ST /P /PUM UMP2 P2 /V /VESS ESS1 1 Removes Removes individua lly lly identified identified element s from obstru ction ction list. REM OB REM OBST ST LE LEAV AVE E TU TUBE BE FR FROM OM /F /FLA LAN2 N2 REM RE M OB OBST ST HE HEAD AD RO ROD D OF /H /HAN ANG1 G1 REM RE M OB OBST ST LE LEAV AVE E /V /VALV ALV3 3 IA IARR RRIV IVE E /V /VAL ALV5 V5 TA TAIL IL /B /BRA RAN1 N1 Removes Removes individual lengt hs of implied implied tu be or rod from from obstr uction uction list. 3-4 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection REM RE M EX EXCL CL AL ALL L Em pties exclusion exclusion list. REM RE M EX EXCL CL /B /BRA RAN3 N3 /B /BRA RAN5 N5 Removes Removes in dividua dividua lly ident ident ified ified element s from exclusio exclusion n list. REM EX REM EXCL CL LE LEAV AVE E TU TUBE BE FR FROM OM /F /FLA LAN2 N2 REM RE M EX EXCL CL HE HEAD AD RO ROD D OF /H /HAN ANG1 G1 REM RE M EX EXCL CL LE LEAV AVE E /V /VAL ALV3 V3 IARRI IARRIVE VE /V /VAL ALV5 V5 TA TAIL IL /B /BRA RAN1 N1 Removes Removes individua l length s of implied implied t ube or rod from exclusion exclusion list. C om o m m a n d S yn yn t a x : .-----<------. / | >---+-->---+--- OBStruct OBStruction ion ---+---* ---+---*----- ---+---. ---+---. | | | | ‘--- ALL --------------| | | | .-----<------. | | / | | ‘--- EXClude EXClude ------------------* ---*----- ---+---+ ---+---+---> ---> >-->--- REMo REMove ve ---+ ---+---- OBSt OBStru ruct ctio ion n ---. ---. .--.------<<--------. -. | | / | ‘--- EXClusio EXClusion n -----+------+---*--*--- ---+---. ---+---. | | ‘--- ALL ------------------------+--+---> --> where (clash (clash ing item identifier) identifier) is >---+-->---+--- ILEAve ILEAve ---. | | |--|--- IARRIV IARRIVE E --| | | |--|--- HEAD HEAD -----| -----| | | |--|--- TAIL TAIL -----+ -----+----- TUBe TUBe ---. ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘--------------------‘--------------------------------------------------+---------+--- ---> Querying: Q CLASH CLASH OBStru OBStructi ction on Lists Lists cur rent obstru ction tion list. list. Q CL CLAS ASH H EX EXCl Clus usio ion n Lists curr ent exclusio exclusion n 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 defau lt, a ll par ts of th e design design model relevant relevant to the curr ent obstr obstr uction uction list will be checked checked for for inter feren feren ces ces dur ing subsequ ent clash -checking -checking ru ns. If you you d o not not wa nt to check check th e ent ire design, you you may define a restricted region of interest represented by a 3 D l im im i t s b ox. For a clash t o be report report ed, both items involved involved in th e clash clash m ust lie wholly wholly or or p ar tly within th e limits limits box. box. A clash clash between item s which lie par tially with with in th e limits limits box will will always be reported, even if th e point point at which th e clash clash occ occur s lies out out side th e box. box. You ma y set u p a limits box in in one of two ways: • E x p l i c i t l y , using the LIMITS comman d, by defining defining t he p ositions ositions of two diam etr ically ically opposed opposed corn corn ers (either as explic explicit coordinat coordinat es or a s t he origins origins of specifi specified ed element s). • I m p l i c i t l y , using the AUTOLIMITS command, by identifying one or more element element s an d allowing allowing DESIGN to calc calculate ulate th e appr opriate box which includ includ es th em. The limits box is is calculat calculat ed so as t o include the whole of each na med element ; it is not deter mined by th e origins origins of th e elemen elemen ts. Examples: LIMI LI MITS TS N2 N256 560 0 E1 E121 2150 50 U2 U215 150 0 TO S6 S653 530 0 W2 W213 135 5 U4 U420 200 0 Sets corners of box to explicit coordinates. LIMI LI MITS TS /S /STR TR6 6 TO /P /PUMP UMP1 1 Sets corner s of box box to origins origins of na med elements . LIMI LI MITS TS S0 E1 E130 300 0 U0 FR FROM OM /N /NOZ OZZ3 Z3 TO N6 N650 50 E1 E175 75 D5 D50 0 FR FROM OM /V /VES ESS2 S2 Sets corner s of box to point point s r eferen eferen ced from origins origins of na med elemen ts. AUTO AU TO /P /PUM UMP1 P1 /P /PUM UMP2 P2 /VESS /VESS2 2 Calculat Calculat es box enclosing enclosing na med element s. AUTO AUTO /GROUP /GROUP1 1 Calculat Calculat es box box enclo enclosing sing all element element s in n am ed group. AUTO HE AUTO HEAD AD OF /B /BRA RAN1 N1-2 -2 TA TAIL IL OF /B /BRA RAN3 N3-1 -1 AUTO AU TO /V /VES ESS1 S1 /V /VES ESS2 S2 LEAVE LEAVE TU TUBE BE FR FROM OM /F /FLA LAN2 N2 Calculates box enclosi enclosing ng na med element s an d implied tube or rod. LIMITS LIMITS NONE NONE Removes Removes any curr ent limits limits box, box, th us restoring defau defau lt sta te in which which whole whole design model is checked. 3-6 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om o m m a n d S yn yn t a x : >---+-->---+--- LIMits LIMits ---. | | | +--- NONe ------------------------. | | | | ‘--- --- TO --- ---| | | | .-----<------. | | / | | ‘--- AUTOlimi AUTOlimits ts ---*-----*--- ---+------+--------------------+--+---> --> where (clash (clash ing item identifier) identifier) is >---+-->---+--- ILEAve ILEAve ---. | | |--|--- IARRIV IARRIVE E --| | | |--|--- HEAD HEAD -----| -----| | | |--|--- TAIL TAIL -----+ -----+----- TUBe TUBe ---. ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘--------------------‘--------------------------------------------------+---------+--- ---> a n d (absolute/relative position) is >---+>---+---- ---+----+--- FROM FROM --- ---. ---. | | | | ‘----------------------| | | ‘--- -----------------------------------------------+---> ----+---> Querying: Q CL CLAS ASH H LI LIMi Mits ts Gives Gives coordina coordina tes for curr ent limits box. Q VO VOLu Lume me element_id(s) Gives coordin coordin at es for for limits box enclosing specified specified design item (s). (s). Q WI WINd Ndow ow > TO s> Gives Gives n am es of all element s with in limits box specifi specified ed by th e two positions; positions; for for example: Q WI WIN N N2 N256 560 0 E1 E121 2150 50 U2 U215 150 0 TO S6 S653 530 0 W2 W213 135 5 U4 U420 200 0 Q WI WIN N /S /STR TR6 6 TO /P /PUM UMP1 P1 Q WI WIN N S0 E1 E130 300 0 U0 FR FROM OM /N /NOZ OZZ3 Z3 TO N6 N650 50 E1 E175 75 D5 D50 0 FR FROM OM /V /VES ESS2 S2 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 comman ds jointly jointly define define th e tolera tolera nces which which det erm ine whether an y given given clash clash is r eport eport ed as a clash clash , a t ouch or a clear lear an ce (see Figur e 3-1). 3-1). DESIGN report s a t o u c h if two primit ives ives either : • Overlap by less tha n a specifi specified ed t o u c h o v e r l a p distance • Are sepa ra ted by less tha n a sp ecif ecified ied t o u c h g a p distance The touch overlap overlap sett ing mu st be positive: positive: th e touch gap mu st be positive positive an d less th an the curr ent sett ing fo for t he cleara cleara nce distance. The default default settings ar e for for a t ouch overlap overlap of 2mm an d a t ouch ouch gap of zero. DESIGN reports a c l e a r a n c e if two primitive volumes volumes a re sepa ra ted at their clo closest point point by more more th an th e cur cur rent ly def defined touch touch gap bu t by less less t ha n a specifi specified ed c le l e a r a n c e d i s t a n c e . The cleara cleara nce distan ce must be positiv positivee an d greater th an t he cur cur rent setting fo for th e touch touch gap. By defau defau lt th e clearan clearan ce distance is undefined, undefined, so that no clearances will be found. DESIGN reports a c l a s h if two primitives overlap overlap by more th an th e touch overlap overlap d istan ce. Examples: TOUC TO UCH H OV OVER ER 3 Sets touch touch overlap; overlap; cur cur rent un its assum ed to be be mm. TOUC TO UCH H OV OVER ER 0. 0.2 2 IN INCH CH Sets t ouch ouch overlap in specifi specified ed un its. TOUC TO UCH H OV OVER ER OF OFF F Effectively sets touch overlap to zero. TOUC TO UCH H GA GAP P 2 Sets touch touch gap; cur cur rent un its assum ed to be mm. TOUC TO UCH H GA GAP P 0 Resets Resets t he t ouch gap t o its its default value. TOUC TO UCH H GA GAP P OF OFF F Effectively sets touch gap to zero. CLEARA CLEARANCE NCE 10 Sets clearan clearan ce; cur rent un its assum ed to be be mm. CLEARA CLEARANCE NCE 0.25 0.25 INCH INCH Sets cleara nce in specifi specified ed un its. CLEARA CLEARANCE NCE 0 CLEARA CLEARANCE NCE OFF 3-8 Unsets clearan ce distan ce (defau defau lt sta te) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om o m m a n d S yn yn t a x : >---+-->---+--- TOUching TOUching ---+-----+--- GAP -------. -------. | | | | |--- OVErlap ---| | | | | ‘---------------+ | | | | ‘--- CLEaranc CLEarance e -------------------------------+--+---- ---. | | ‘--- OFF ------+------+---> --> Querying: Q CL CLAS ASH H TO TOUc Uchi hing ng OV OVEr Erlap lap Q CL CLAS ASH H TO TOUc Uchi hing ng GA GAP P Q CL CLAS ASH H TO TOUc Uchi hing ng Q CL CLAS ASH H CL CLEa Eara ranc nce e 3.5 Ignoring Clashes Within Specified Element Types Keywords: NOCHECK WITHIN Description: By defau defau lt, no checks checks ar e ma de for for clash clash es between item s owned owned by the sam e Stru ctu re, Substru ctu re, or or Equipmen t. In addition, addition, you you ma y use the NOCHECK a n d WITHIN comm comm an ds to tell DESIGN t o ignore all clash clash es with in one or m ore oth oth er s pecif pecific ic types of elemen elemen t. All clashes below each element of the specified types will be ignored dur ing th e checking checking opera opera tion, what ever th e hiera rchic level level of of th e clash ing items. Clashes specifi specified ed in th is way are ignored dur ing th e actua l clash clash -checking -checking opera opera tion an d ar e not th erefore erefore ava ilable in memory fo for inclusio inclusion n in su bsequent outpu t reports. Examples: NOCHEC NOCHECK K WITHIN WITHIN BRAN BRAN Ignores clashes within individual Branches (but still reports clashes between items in different Branches). NOCHEC NOCHECK K FRMW FRMW Ignores Ignores clashes within individual individual F ram eworks eworks (but still report report s clashes clashes between between items in diff different Fr ameworks). WITHIN WITHIN FRMW FRMW Restores clash clash checking checking with in Fr am ework ework s; tha t is, it it cancels a pr evious evious NOCHECK F RMW co comm and. WITHIN WITHIN EQUI EQUI Restores clash clash checking within individua l item item s of of Equ ipment (which (which ar e not checked by default ). PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-9 Clash Detection C om o m m a n d S yn yn t a x : >---+>---+---- NOChec NOCheck k ---+----+--- WIThin WIThin ---. ---. | | | | ‘--------------+ .----<------. | | / | ‘--- WIThin WIThin --------------------------------+ ---+---* ---*----- ---+---> ---+---> where (significant element) is any of the following: S I T es S T R u ct u r e s P T R a ck s 3.6 ZO N e s S U B S t r u ct u r e s F R M Wor k s P I P es H AN G e r s S B F R M w or k s B R An ch e s E Q U ip m e n t s R E S T R a 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 (Clash es between sections sections a nd a tt ached joints joints et c. ar e ignored ignored automatically.) Fr equently, yo you may wish t o leave leave end prepa ra tions tions a t st eelwo eelwork rk joi joint nt s un til late in th e design pr ocess. cess. If yo you d o this, you you can inh ibit ibit clash reporting using t he comma comma nds described described here. Examples: INCLUDE INCLUDE CONNECTIONS CONNECTIONS Includes all steelwork steelwork conn conn ections ections dur ing subsequen t clash checking. checking. IGNORE CONNECTIONS CONNECTIONS Ignores st eelwork eelwork conn conn ections ections du rin g checking. checking. IGNORE IGNORE CONNEC CONNECTIO TIONS NS WITH WITH SPECIF SPECIFICA ICATIO TIONS NS Ignores only those connections which have specifications.. C om o m m a n d S yn yn t a x : >-- INClud INClude e -- CONnec CONnectio tions ns --> >->-- IGNo IGNore re --+--+-- ALL ALL --. --. | | ‘------‘---------+--+-- CONnecti CONnections ons --> >-- IGNore IGNore -- CONnec CONnectio tions ns -- WIth WIth -- SPEcif SPEcifica icatio tions ns --> --> 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 ouch overlap overlap s ett ing may be non-zero, non-zero, you you ma y tell DESIGN t o ignore ignore all touches dur ing subsequ ent clash checks. Touches Touches ignored in t his wa y ar e not a vailable in in m emory for for in clusion in subsequ ent out put report s. If you you a re likely to want to check check touches later , it it is better to include include th em in th e clash clash -checking -checking operat ion ion (which which is the default situ at ion) ion) an d th en t o inh inh ibit ibit their inclusion inclusion in t he r eport if necessar necessar y. Examples: IGNORE IGNORE TOUCHE TOUCHES S Ignores all touches during subsequent clash checking. INCLUDE INCLUDE TOUCHES TOUCHES Restores Restores th e defau defau lt situat ion, ion, where t ouches are det ected ected an d stored with th e cur cur rent clash list. list. C om o m m a n d S yn yn t a x : >---+-->---+--- IGNore IGNore ----. ----. | | ‘--‘--- INclud INclude e ---+----+--- TOUch TOUches es ---> ---> Querying: Q CL CLAS ASH H IG IGNo Nore re 3.8 Controlling the Reported Clash Position Keywords: MIDPOINT Description: By defau defau lt, the r eported position position for for a clash d epends on which par t of th e overlapp overlapp ing r egion egion is first first detected by th e checking checking pr ocess: ocess: in in most cases, this somewhat arbitrary position identifies the clash sufficiently accurately. The MIDPOINT option option lets you specify specify th at th e reported positio position n is always at the centr e of a box box sur rounding th e overlappin g region, giving giving more r eproducible eproducible (but slower) slower) resu lts. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-11 Clash Detection C om o m m a n d S yn yn t a x : >->-- MIDp MIDpoi oint nt --+--+-- ON ---. ---. | | ‘-- OFF --+--> --+--> Querying: Q CL CLAS ASH H MI MIDp Dpoi oint nt Q CL CLAS ASH H OP OPTi Tion ons s 3.9 Specifying How Branches Are Checked Keywords: BRANCH ACHECK BCHECK Description: Assuming th at you have n ot specified NOCHECK BRANCHES (see Section Section 3.5), 3.5), you you ma y check check for 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 each br anch - known known a s a T y p e A c h e c k (or A C H E C K) K) • As a simplified check which ignores the possibility of clashes between between certa in pa irs of co components within t he br an ches - kn own a s a T y p e B c h e c k (or (or B C H E C K ) (Clashes between adjacent components and attachments within a Bran ch are ignored ignored a ut omat ically ically.) .) The pu rpose of of th e BCHECK option option is t o elimina elimina te from th e clash clash report spu rious rious clashes wh ich ich result when zerozero-length length components (such (such a s welds and olets) separ at e oth oth er componen componen ts or tu bing. If you you sp ecify ecify a BCHECK, the warn ing message *** *** BRAN BRANCH CH CHEC CHECKI KING NG - OPTI OPTION ON B *** *** will will be be output as par t of the report header. This is becau becau se, although most of th e clash clash es ignored by Type Type B checking checking rea lly lly ar e spu rious, some genu genu ine clash clash es ma y also be ignored. ignored. The lat ter , exam exam ples of of which ar e given given in Section Section 3.9.1, will will be mostly due t o design design err ors, man y of of which which should have been diagnosed diagnosed a t a n ea rlier rlier st age by mea ns of a da ta consisten cy check check (see Cha pter 2). Th e d e f a u l t check check is t he ACHE CK option, option, sin ce th is is a fail-safe fail-safe check for for a ll potential clashes. Examples: BRAN BR ANCH CH B BRAN BR ANCH CH A 3-12 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om o m m a n d S yn yn t a x : >-->--- BRANCh BRANCh ---+----+--- Acheck Acheck ---. ---. | | ‘--- Bcheck Bcheck ---+---> ---+---> Querying: Q CL CLAS ASH H CH CHEC ECK K Q CL CLAS ASH H OP OPTi Tion ons s 3.9.1 Rules Applicable During Type B Checks The follo following wing sections sections define define t he r ules which DESIGN a pplies dur ing th e clash -checking -checking pr ocess ocess when th e BCHECK option is in force. force. They includ e examples of the sorts of design errors which would remain undetected in the clash report . The ter m ‘c ‘clash ’ is used in th ese examples t o refer refer t o all types of inter feren feren ce; ce; in pr actice, actice, some some of th ese ma y be reported a s touches, dependin g upon th e t ouch ouch specifi specificcat ions ions in force. force. Clashes Within a Single Branch Rule: If th e leave leave point point (p-l (p-leave) eave) of an u pstr eam component component or tube co coincides incides with th e ar rive point point (p-arr (p-arr ive) ive) of of a downstr downstr eam component, component, an d th ere is no inter vening Tube, th e two component component s will not be checked checked for for clashes between them. This ru le is is inten ded to suppr ess clashes clashes when two co components or tu bes with with in a br anch a re separ ated by one one or m ore zero-le zero-length ngth components which 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 or tail and a nozz nozzle le are properl properly y co connected nnected a n d th e p-ar p-ar rive or or p-leave p-leave of of th e final final componen componen t coinci coincides des with t he br an ch h ead or t ail, then no clash clash will will be reported. This ru le is is inten ded to suppr ess clashes clashes when a n ozzle zzle and a pipe co 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 connected together end-to-end end-to-end a n d th e p-ar rive/p-l rive/p-leave eave of two compo componen nen ts or tu bes coi coincide ncide with with t heir r espective espective bran ch h ead/tail (whichever (whichever is th e connected connected end), th en n o clash clash will will be reported. This ru le is is inten ded to suppr ess clash clash es similar t o th ose described for for clash clash es with with in a single single bran ch, except except th at the r elevant elevant components or t ubes ma y now be from from differen differen t, bu t conn conn ected, 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, would, however, however, a llow llow some clash clash es due t o routing err ors to be ignored. 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 (empt y) obstr obstr uction list list a nd /A is checked checked against it, thu s checking checking for for clashes between t he elements: /A/A S t a g e 2 : /B is added to th e obstr obstr uction list, which which t hen comprises /A /B, /B, and /B /B is checked checked again st t his n ew list, list, th us checking for for clash clash es between t he following pairs of elements: /A/B /B/B S t a g e 3 : /C is is a dded t o the obstr obstr uction list, which th en compr compr ises /A /B /C, /C, an d /C is checked checked again st t his n ew list, list, t hu s checking checking for for clashes bet ween th e follo following wing pa irs of element s: /A/C /B/C /C/C S t a g e 4 : /D is added t o the obstruction obstruction list, list, which which t hen compr ises ises /A /B /C /C /D, /D, and /D is is checked checked a gainst th is new list, th us checking checking for for clashes between t he follo following wing pair of element s: /A/D /B/D /C/D /D/D Note: This ha s th e same overall effe effecct a s th e comman comman d sequen ce: OBSTRU OBST RUCT CTIO ION N /A /B /C /D CHECK /A /B /C /D which creat es t he obstr obstr uction list /A /B /B /C /D /D an d t he check list /A /B /B /C /C /D /D and checks for for clash clash es between t he pa irs /A/A /A/A /A/B /A/B /A/C /A/C /A/D /A/D /B/B /B/C /B/D /C/C /C/D /D/D.) C om o m m a n d S yn yn t a x : .-----<------. / | >-->--- CHECKA CHECKAdd dd ---*----*--- ---+----+---. -. | | ‘--- 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.11 Reporting the Clashes Found 3.11.1 The Principles A report is sent a ut omat ically ically to the Request region region each t ime you you r un a clash clash check; th at is, each time you enter a CHECK, BOXCHECK or CHECKADD comma nd. Yo You can cha nge th e forma forma t for for such a report befo before r un ning th e clash check if necessar y. In addit ion, ion, you you m ay send out put to a file file by usin g the ALPHA FILE or ALPHA LOG comma nds in th e usua l way. 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 of the pr ogra m vers ion ion in u se; th e types of clash report ed; an y non-defau non-defau lt checking checking options options a nd limits; th e touch an d clear clear an ce limits; limits; an y special special reportin g options 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 Deta ils of of the clashes foun foun d, includin includin g th e clash clash type an d extent an d th e identifiers identifiers of th e two design items involved. involved. The clashes ar e grouped grouped int o s e c t i o n s , one for for each significant significant element which cont cont ain s an inter feren feren ce. ce. Wher Wher e space permits, each clash clash is reported on a single line. line. • T h e c la la s h s u m m a r y : Lists th e total nu mber of clash clash es of of each 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 found t o be free free of an y int int erferences. All dat a r esultin g from from a clash -checking -checking ru n is h eld in in t he compu compu ter ’s mem ory un til overwritten overwritten by da ta from a later r un (or (or u nt il yo you chan ge modules) modules).. This allows allows you you to genera genera te furt her reports derived from from th e sam e dat a, possibly possibly usin g diffe differen ren t r eporting options from th ose in in force force for 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 program version version an d the dat e and time at t he star t of the check. • The types of clash clash es being reported a nd t he element s specifi specified ed in the check-initiation command. • The touch and clearance definitions, the current Branch checking option, option, a nd a ny n on-default on-default options which ma y be in force. force. Examples: REPO RE PORT RT HE HEAD ADER ER OF OFF F Suppr esses entire header REPORT REPORT HEADER HEADER REPO RE PORT RT HE HEAD ADER ER ON Reinstates header if previously suppressed (ON is the default) REP OBSTRUCTION OBSTRUCTION REP RE P OB OBST STRU RUCT CT ON Outpu ts obstruction obstruction list as pa rt of header REP RE P OB OBST STR R OF OFF F Suppr esses obstru obstru ction tion list list in header (th e default) default) C om o m m a n d S yn yn t a x : .---------------<-----------------. / | >--- REPort ---*--- HEAder --------. | | | | ‘--‘--- OBStru OBStructi ction on ---+----+--- > ---| ---| | | ‘---------------+---> 3-20 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection Querying: Q CL CLAS ASH H RE REPo Port rt HE HEAd Ader er Q CL CLAS ASH H RE REPo Port rt OB OBSt Stru ructi ction on Q CL CLAS ASH H RE REPo Port rt List List a ll report sett ings (header (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 forma t sh ows each each clash on a sepa rat e line, line, with with full details of of the clashing clashing items an d th e nat ur e of of the clash. clash. The reported clashes ar e grouped grouped int o s e c t i o n s , each of which lists all clashes within a single signifi significcan t element , the na me of which is usua lly shown only at th e beginn beginn ing of th e section section t o avoid avoid excessive excessive repetition of dat a (th e na me of th e second second clash clash ing elemen elemen t is always sh own own in full to avoid avoid an y am biguity). biguity). The follo following wing deta ils may a lso be included included in th e report : • The clash p o s i t i o n , in eith er S ite or World coo coord rd inat es (to co cont rol how t his position position is calculated, see Section Section 3.8). 3.8). • The PDMS r e f er e r e n c e n u m b e r s of th e clash clash ing elements , as well as their names. • Sequential c la la s h n u m b e r s , used t o ident ident ify ify individua individua l clash clash es in other commands (such as when approving clashes). By defau defau lt, all types of clash , touch an d clear clear an ce ar e report ed. You You ma y rest rict th e report to one one or m ore specif specified ied clash clash types (e.g. (e.g. ha rd/ha rd only, touches only, etc.) etc.).. Examples: REPO RE PORT RT MA MAIN IN OF OFF F Sup pr esses ma in body of report REPORT REPORT MAIN MAIN REPO RE PORT RT MA MAIN IN ON Reinsta tes ma in body body if if previously sup pr essed (ON (ON is th e default) REPORT REPORT POSITI POSITION ON SITE SITE Shows clash clash positions positions in Site coordinat coordinat es REPORT REPORT POSITI POSITION ON WORLD WORLD Shows clash clash positions positions in Wo World rld coordin coordin at es REPORT REPORT POSITI POSITION ON OFF Suppresses clash positions (the default) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-21 Clash Detection REPORT REPORT REF REPO RE PORT RT RE REF F ON Outpu ts reference reference num bers of clashing clashing items REPO RE PORT RT RE REF F OF OFF F Suppr esses reference reference numbers (the default) REPORT REPORT NUMBER NUMBER REPO RE PORT RT NU NUMB MBER ER ON Outputs sequential clash numbers. REPO RE PORT RT NU NUMB MBER ER OF OFF F Suppr esses clash clash n umbering (the defau defau lt) REPORT REPORT FIRST FIRST List List clash only under first item in DB hierar chy (the default) REPORT REPORT SECOND SECOND List clash clash only und er second second item in DB hierar chy REPORT REPORT BOTH BOTH List clash clash t wice, wice, once once under each item in DB hiera rchy REPORT REPORT PRIMAR PRIMARY Y REPO RE PORT RT PR PRIM IMAR ARY Y ON Report Report s only first first or highest pr iority iority clask foun foun d between two signific significan an 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. force. REPORT REPORT PRIMAR PRIMARY Y 500 Suppr esses multiple clash clash r eport eport s if clash clash positio positions ar e less less t ha n 500 m m apart (if curr ent un its are mm) REPORT REPORT PRIMAR PRIMARY Y OFF Report Report s all clash clash occur ccur ren ces, ces, including including t hose between differen differen t p rimit ives ives of th e sam e pairs of signific significan an t element s (the default ) REPORT SIGNIFICANT SIGNIFICANT REPORT REPORT SIGNIF SIGNIFICA ICANT NT ON Lists a ll signif signific ican an t elemen ts wh ich ich h ave been checked, not just t hose for for which clash clash es ha ve been been det ected. ected. REPORT REPORT SIGNIF SIGNIFICA ICANT NT OFF Report Report s only those signific significan an t elemen ts wh ich ich in volve volve clash clash es (the defau lt) REMOVE REMOVE SECTIO SECTIONS NS SUBS STRUC STRUC Sup press es th e labelling labelling of of th ose sections sections of th e report wh ich ich r epresen t Substr uctur es and Str uctures. Clashing items in th ese sectio sections ns will be identified identified by their full nam e on on each line (in (in th e same way th at t he second second clashing element is always shown) SECTIO SECTIONS NS SUBS SUBS STRU STRU Reinstates labelling of specified sections 3-22 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om o m m a n d S yn yn t a x : .---------------<-----------------. / | >-->--- REP REPor ort t ---* ---*---- POSi POSiti tion on -----++---- SIt SIte e -------. . | | | | | | |--- WOrld ---| | | | | | | ‘--- OFF -----+----| | | |--- REF -----------. | | | | |--- NUMber --------| | | | | |--- MAIN ----------| | | | | |--- PRImary -------| | | | | |--- SIGnific SIGnificant ant ---+-----+--- ---| | | | | ‘---------------| | | |--|--- PRImar PRImary y --- --------------------| -| | | |--- FIRst -----------------------------------------------| --| | | |--- SECond ---------------------------------------------| --| | | |--- BOTh -----------------------------------------------’ ----’ | | .-----<-------. | / | |---*--|---*--- ---| | | | | ‘----- NP ------------++----. . .--.-------< ---<------------. . | | / | |--- ALL -------------------------+ ---+---* ---*----- CLAshes CLAshes ------| ------| | | | | |--- TOUches ------| ‘---> | | |--- CLEaranc CLEarances es ---| | | ‘------------------+---> >---+--- REMove ---. .----<------. | | / | ‘------‘-----------------+ ---+----- SECtions SECtions ---*-----*--- ---+---> ---+---> where (significant element) is any of the following: S I T es S T R u ct ct ur u r es es F RM RM W or k s ZO N e s P I P es S U B S t ru r u ct ct ur u r es es H AN AN G e r s S BF BF RM RM w or k s B R An ch e s R E ST ST R a in in ts ts E Q U ip m e n t s P TR TR a ck ck s Querying: Q CL CLAS ASH H RE REPo Port rt MA MAIN IN Q CL CLAS ASH H RE REPo Port rt PO POSi Siti tion on Q CL CLAS ASH H RE REPo Port rt RE REF F Q CL CLAS ASH H RE REPo Port rt NU NUMb Mber er PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-23 Clash Detection Q CL CLAS ASH H RE REPo Port rt PR PRIma Imary ry Q CL CLAS ASH H RE REPo Port rt SI SIGni Gnifi fica cant nt Q CL CLAS ASH H RE REPo Port rt DU DUPli Plica cati tion on Shows u nd er wh ich ich sections sections clash clash es will be reported (i.e. (i.e. First , Second Second or Both) Q CL CLAS ASH H RE REPo Port rt LE LEVel Vel Lists clash clash types t o be be report ed on Q CLAS CLASH H RE REPo Port rt List a ll report settings (header (header + main + summ ar y) 3.11.4 Customising the Report Report Summary Summary Keywords: REPORT SUMMARY Description: The standard summa ry, output output at the end of the clash clash r eport, eport, comprises a list showing: • The t otal nu mber of clash clash es foun foun d of each type • The total n umber of signif signific ican an t elements checked hecked du ring th e ru n covered overed by t he r eport • The n um ber of element s foun foun d to be free free of an y inter feren feren ces *** * AC ACTU TUAL AL CL CLAS ASH H SU SUMM MMAR ARY Y ** ***. *. This summa ry is headed ** If REPORT PRIMARY ON has been specified (see Section 3.11.3), 3.11.3), t w o *** * PR PRIM IMAR ARY Y CL CLAS ASH H report summaries will be produced; one headed ** SUMMAR SUMMARY Y *** and one headed ** *** * AC ACTU TUAL AL CL CLASH ASH SU SUMM MMAR ARY Y ** ***. *. Examples: REPORT REPORT SUMMAR SUMMARY Y OFF Suppr esses out put of report summ ary REPORT REPORT SUMMAR SUMMARY Y REPO RE PORT RT SU SUMM MMAR ARY Y ON Reinst Reinst ates report su mma ry if previo previously suppr essed (ON (ON is th e defau defau lt) C om o m m a n d S yn yn t a x : >-->--- REPor REPort t --- SUMmar SUMmary y ---+----+--- > ---. ---. | | ‘---------------+---> Querying: Q CL CLAS ASH H RE REPo Port rt SU SUMma Mmary ry Q CLAS CLASH H RE REPo Port rt List a ll report settings (header (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 some of th e clash clash da ta directly, directly, with with out genera ting a r eport. 3.12.1 Querying Individual Clashes Keywords: FIRST SECOND TYPE POSITION Description: These options a llow llow you to qu ery ind ividua ividua l par ts of specifi specified ed clashes. The clashes are identified in each case by their clash numbers. Examples: Q CL CLAS ASH H 2 FI FIRS RST T Out put s n am e of of first first clash ing element (the ‘c ‘clash er’) er’) for for clash clash nu mber 2 Q CL CLAS ASH H 2 SE SECO COND ND Out put s n am e of second second clash clash ing element (the ‘c ‘clash ee’) ee’) for for clash clash nu mber 2 Q CL CLAS ASH H 2 TY TYPE PE Out put s type of clash (e.g. (e.g. HH TOUCH ) Q CL CLAS ASH H 2 PO POSI SITI TION ON Out put s position position of of clash in coord coord inat e system curr ent ly set for for r eporting (i.e. (i.e. Site or Wo World rld ) Q C L A SH 2 A L L Out put s all of of th e preceding preceding da ta ; for for exam ple: Clash Clas h nu numb mber er: : 2 Clas Cl ashe her: r: CO CONE NE 1 of EQ EQUI UI /V /VES ESS1 S1 Clas Cl ashe hee: e: SL SLCY CY 1 of ST STRU RU /V /V1. 1.PL PL Type Ty pe: : HH TO TOUC UCH H Posi Po siti tion on: : W 10 1000 000m 0mm m N 18 1800 000m 0mm m U 22 2200 00mm mm C om o m m a n d S yn yn t a x : >-->--- Quer Query y ----- CLAS CLASH H ----- clash_no ---+-----+--| |--|--| |--|--| |--|--| ‘--- PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 FIRST FIRST ------. ------. | SECOND SECOND -----| -----| | TYPE TYPE -----------| --| | POSiti POSition on ---| ---| | ALL ---------------+--+---> > 3-25 Clash Detection 3.12.2 Querying Clash Statistics Keywords: COUNT CLASHES TOUCHES CLEARANCES NOTPROVEN Description: These options allow yo you to quer y th e tota l nu mber of clash es of each type (exc (excluding luding app roved clash clash es). Examples: Q CL CLAS ASH H CO COUN UNT T CL CLAS ASHES HES Q CL CLAS ASH H CO COUN UNT T TO TOUC UCHES HES Q CL CLAS ASH H CO COUN UNT T CL CLEA EARAN RANCE CES S Q CL CLAS ASH H CO COUN UNT T NO NOTP TPROV ROVEN EN Q CL CLAS ASH H CO COUN UNT T AL ALL L Out put s nu mber of clash es of of each each type; for for example: Total Tota l Total Total Total Total Tota To tal l Clashe Clas hes: s: 30 Touche Touches: s: 116 Cleara Clearance nces: s: 218 Not No t pr prov oven en: : 37 C om o m m a n d S yn yn t a x : >-->--- Query Query --- CLASH CLASH --- COUNT COUNT ---+----+--| |--| |--| |--| ‘--- CLASHe CLASHes s -----------. . | TOUCHes TOUCHes ------| ------| | CLEARanc CLEARances es ---| | NOTProve NOTProven n ----| ----| | ALL -----------------+--+---> --> 3.13 Reporting Without Further Clash Checking All clash clash da ta derived derived dur ing a clash-c clash-checki hecking ng ru n is r etained in th e comput er’s er’s memory un til ove overwritt rwritt en by data from a s ubsequent ru n (or (or u ntil you you cha nge modules). This allows allows you you t o out out put furt her report s derived from from th at dat a, usin g modifi modified ed report ing options options an d/or d/or a diffe differen ren t outp ut device 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 report generated in r esponse esponse to an OUTPUT comma nd ha s exactly exactly the sa me form form at, determ ined by any cur cur rent reporting optio options ns wh ich ich you you h ave set, as tha t generat ed in response to a CHECK command. The differen differen ce is tha t t he check options, options, touch an d clear clear an ce values, obstru ction tion list etc. which which a pply to th e Outpu t r eport eport ar e those cur cur rent wh en the clash clash ru n w as carried carried out out ; th ese need n ot be cur cur rent when t h e OUTPUT comma nd is given. given. Examples: OUTPUT OUTPUT CLASHE CLASHES S /ZONE1 /ZONE1.PIP .PIPES ES OUTPUT OUTPUT /PUMP1 /PUMP1 /PUMP2 /PUMP2 /VESS2 /VESS2 OUTPUT /GROUP.MOD2 /GROUP.MOD2 OUTP OU TPUT UT 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 These comm comm an ds outp ut report s of kn own own clashes in volvi volving ng t he sp ecif ecified ied items in ea ch case case OUTPUT Outpu ts a complete report report of all clash da ta cur rent ly held held in m emory emory C om o m m a n d S yn yn t a x : >-->--- OUTput OUTput ---+----+--- CLAshe CLAshes s ---. ---. | | ‘------‘---------------------+--+--- ---> 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-27 Clash Detection 3.13.2 Suppressing Clash Repetition in Reports Keywords: REPORT FIRST Description: When u sed before before an OUTPUT comma nd, the REPORT FIRST option allows allows you you to genera te a sequen ce of report s from a single set of clash clash data such th at each each clash clash is report report ed once once only only thr oughout t he complete sequen ce. Examples: REPORT REPO RT FI FIRS RST T AL ALL L OUTPUT /ZONE.PIPES /ZONE.PIPES OUTPUT /ZONE.STEELW /ZONE.STEELW Assum e th at you you have just ru n a clash clash check heck wh ich ich includes includes piping piping an d steelwo steelwork items am ong t he elements checked. hecked. Then th is sequence sequence generat es /ZONE.PIPES) shows all two separate reports; the first (from OUTPUT /ZONE.PIPES clash es involvi involving ng pipework pipework elements , including including th ose between between pipework a nd /ZONE.STEELW) shows all clashes steelwork; the second (from OUTPUT /ZONE.STEELW involving involving steelwork steelwork elements except except t hose which which wer e included included in t he first report (i.e. (i.e. th e second second report omits clash clash es between between pipework pipework a nd steelwork. C om o m m a n d S yn yn t a x : >-->--- REPo REPort rt FIRs FIRst t ALL ALL ---> ---> 3.14 Approving Approving Clashes 3.14.1 The Principles You ma y specif specify y one one or m ore clash clash es which, alth ough r eal int erferences, are t o be omitted omitted from subsequent clash r eport eport s. Such clash clash es ar e referr referr ed to as a p p r o v e d c la la s h e s . The obstru ction limits limits boxes for for all approved clash clash es, as repr esent ed in th e spatial map, ar e identif identified ied in in a sepa ra te list list kn own as th e a p p r o v a l l is is t . This ena bles the pr ogra ogra m t o check which which item s ha ve been been m oved with with in th e design design after appr oval, and t herefore herefore t o alert alert you you to the fact th at some some clash clash appr ovals ma y no longer 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 follo following wing ways: • By specif specific ically ally identifying identifying a kn own own clash between t wo nam ed items • By specif specific ically ally identifying identifying a kn own own clash by mea ns of its r eferen eferen ce nu mber in the latest clash clash r eport eport • By gener gener ally referr referr ing to actua l or or poten tial clash clash es between na med items; eith eith er befo before or a fter ru nn ing a check check t o see see what clash es exist • By specif specifying ying actua l or or poten tial clash clash es within a single nam ed element Appr oved oved clash clash es will be omitt omitt ed from clash clash report s r egard less of of which way round t he int erfering items a re specifi specified ed in th e obstr obstr uction uction list and the check list in subsequent clash-checking runs. Examples: APPR AP PROV OVE E HS TO TOUC UCH H BO BOX1 X1 OF /E /EQU QUI1 I1 WI WITH TH /G /GAS ASK1 K1 OF /B /BRA RAN2 N2 Appr oves oves ha rd/soft rd/soft t ouch ouch between n am ed items (and a ny lower lower level level touches; e.g. HI, SS etc.) APPR AP PROV OVE E 5 Appr oves oves th e fif fifth th clash in most r ecent ecent clash report APPR AP PROV OVE E SI SIGN GNIF IF 5 Appr oves oves fifth fifth clash in most r ecent ecent clash report at signific significan an t elemen t level, level, ra th er th an at primitive leve level; l; where th e signif signific ican an t elements a re: Sites, Zo Zones, Pipes, Branches, Equipments, Str uctures, Subst ru ctu res, Hangers, Restraints, Ptracks, Frameworks, and Subframeworks APPR AP PROV OVE E II CL CLAS ASH H /B /BRA RAN1N1-1 1 WI WITH TH /Z /ZON ONE. E.EQ EQUI UIP P Appr oves oves all Insulat ion/Insu ion/Insu lation clash clash es between an y element element s below below /BRA /BRAN1-1 N1-1 an d a ny elemen elemen ts below below /ZONE.E /ZONE.E QUIP APPROV APPROVE E /ZONE. /ZONE.EQU EQUIP IP WITH /ZONE. /ZONE.STE STEELW ELW Approves a ll types of clash clash between m embers of th e na med zones APPROV APPROVE E HS CLASH CLASH /ZONE.E /ZONE.EQUI QUIP P WITH WITH /ZONE. /ZONE.EQU EQUIP IP Appr oves oves all har d/soft d/soft clash clash es between m embers of /ZONE.E /ZONE.E QUIP (an d an y lower lower level level clash clash es, touches or cleara nces) PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-29 Clash Detection C om o m m a n d S yn yn t a x : >-- APProv APProve e --+--+- > -+- CLAsh CLAsh -----. -----. | | | | |- TOUch -----| | | | | |- CLEarance -| | | | | ‘-------------| | | |- NP ----------------------------------++- -+--+-- WITh WITh --. | | | | ‘----------+ --> | |--|--- SIGn SIGnif ific ican ant t ---. ---. .--.-------< -<----------. -. | | / | ‘-------------------+---*--- clash_no ---+--> where (clash (clash ing t ype) is one of th e follo following: wing: HH HS HI SS SH SI II IH IS NP a n d (clash (clash ing item identifier) identifier) is >---+-->---+--- ILEAve ILEAve ---. | | |--|--- IARRIV IARRIVE E --| | | |--|--- HEAD HEAD -----| -----| | | |--|--- TAIL TAIL -----+ -----+----- TUBe TUBe ---. ---. | | | | |--- ROD ----| | | | | ‘------------+--- OF -----. | | | | |--- FROM ---| | | | | |--- TO -----| | | | | ‘------------+ | | ‘--------------------‘--------------------------------------------------+----------+--- ---> Note: 3-30 Clashin g type H(ard ) aut omat ically ically includes includes S(oft) S(oft) an d I(insulat ion). ion). CLASH au tomat ically ically includes 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 volved in an app roved clash clash h as been m oved oved within th e design, the clash clash es involvi involving ng th at item m ay be rea ppr oved oved (if (if you you are su re th at such appr oval is is still valid) valid) without without th e need to reenter th e full full clash clash d eta ils. The resu lt is tha t t he n ew obstr obstr uction uction boxes for for those items, in in t he spat ial map, ar e stored with with th e existing existing appr oved clash details. Examples: REAP RE APPR PROV OVE E 5 6 12 Reappr oves oves clash clash es specif specified ied by th eir nu mber s in th e appr oved oved clash clash list. REAP RE APP P AL ALL L Reappr oves oves th e whole whole appr oval oval list. C om o m m a n d S yn yn t a x : .-----<------. / | >--- REApprov REApprove e ---+---* ---+---*----- app_no ---+---. | | ‘--- ALL ------------------------+--+---> --> 3.14.4 Removing Clashes from the Approval List Keywords: REMOVE Description: Removes Removes specifi specified ed clash clash es, or or clash es between items which ha ve been moved in in t he design since their ap pr oval, oval, from from th e appr oval oval list. Examples: REMOVE REMOVE APPROV APPROVED ED /ZONE. /ZONE.EQUI EQUIP P WITH WITH /ZONE. /ZONE.STE STEELW ELW Removes Removes appr oval oval of clash es between na med element s. REM APP 5 6 12 Removes Removes app roval of of clash es specifi specified ed by their n um bers in t he a ppr oved oved clash list. REM RE M AP APP P MO MOVE VED D REMOVE REMOVE MOVED MOVED Removes Removes a ppr oval oval of clash es for for which one or both clash ing items ha ve been moved in in t he design. REMOVE REMOVE APPROV APPROVED ED ALL Empt ies the appr oval list. list. PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-31 Clash Detection C om o m m a n d S yn yn t a x : >-- REMove REMove --+---+-- APProved 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 cur ren t a ppr oval oval list in a choic choicee of of form form at s (which (which you you set as for for t he clash clash report listings sum ma rised in Section Section 3.11.3). 3.11.3). Examples: OUTPUT APPROVED APPROVED Outpu ts full appr oval list list OUTPUT OUTPUT MOVED MOVED OUTP OU TP AP APPR PR MO MOV V Out put s only those appr oved oved clash clash es which ar e affec affected ted by items wh ich ich ha ve moved moved in th e design design sin ce appr oval. oval. OUTP OUTP APPR APPR /ZONE. /ZONE.EQUI EQUIP P Out put s list of of approved clash clash es involvi involving ng element s or prim itives with with in specified Zone OUTP OUTP MOVED MOVED /ZONE. /ZONE.EQUI EQUIP P OUTP OU TP AP APPR PR MO MOV V /Z /ZON ONE.E E.EQU QUIP IP Out put s ap proved clash clash es involving involving only only element s or pr imitives in specifi specified ed Zone which which h ave moved in th e design since appr oval oval REPORT APPROVED APPROVED REPORT REPORT APPROV APPROVED ED ON Causes su mma ry of appr oved clashes clashes to be appended t o all subsequent subsequent clash reports REPORT REPORT APPROV APPROVED ED OFF Suppr esses summa ry of of approved approved clashes clashes in subsequent reports (the default) 3-32 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection Command Syntax: >-- OUTpu OUTput t --+---+-- APProv APProved ed --+---+-- MOVed MOVed --. | | | | ‘-----------+--. | | ‘-- MOVed MOVed ------------------------------------+-+-- --. | | ‘------------+--> >-- REPor REPort t -- APProv APProved ed --+---+-- > --. | | ‘-------------+---> 3.15 Saving and Restoring Clash Data You m ay save the resu lts of of the cur cur rent clash ru n t o a fil filee and t hen r estore estore tha t dat a for for u se later later in the sam e sessio session or dur ing another session. session. 3.15.1 Saving Data to a File Keywords: SAVE Description: Th e SAVE options a llow llow you to sa ve an y or all of th e follo following wing t ypes of dat a t o a n am ed file. file. In ea ch case you you can overwrite a n existing file file by appending the OVER comma nd t o th e fil filee nam e in the u sual way. • The cur cur rent s eett u p p a r a m e t e r s : • The obstr uction uction list • The limits box co coordinat es • The touch touch an d cleara cleara nce settings • Wheth er or n ot t he m idpoint idpoint positioning positioning option option is in force orce • Any checking options currently specified (e.g. NOCHECK , IGNORE, ACHECK / BCHECK BCHECK options) • Any r eporting options cur ren tly specifi specified ed • Th e c la l a 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 for inclusion inclusion in fut ur e reports • The cur cur rent list list of a of a p p r o v e d c la la s h e s Examples: SAVE SAVE SETUP SETUP /CLASH /CLASH1 1 SAVE SA VE SE SET T /C /CLA LASH SH1 1 OV OVER ER Saves setu p pa ra met ers, as listed in th e above description, to file file /CLA /CLASH1 SH1 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-33 Clash Detection SAVE SAVE CLASHE CLASHES S /CLASH2 /CLASH2 SAVE SA VE CL CLA A /C /CLA LASH SH2 2 OVER OVER Saves clash deta ils, including including checking checking options a nd obstru ction list, to file file /CLASH2 SAVE SAVE APPROV APPROVED ED /CLASH3 /CLASH3 SAVE SA VE AP APP P /C /CLA LASH SH3 3 OVER OVER Saves curr ent app roval list list t o th e file file /CLA /CLASH3 SH3 SAVE AL SAVE ALL L /C /CLA LASH SH4 4 SAVE SA VE AL ALL L /C /CLA LASH SH4 4 OVER OVER Saves setup parameters, clash details and approval list to file /CLASH4 Note: While the SAVE ALL option option is often often convenient, bear in min d th at you you can not later restore only only part of the da ta with with out affec affecting ting th e rest. This could could m ean th at when th e fil filee is restored you will will overwrit overwrit e some some settings which which you wish to reta in. C om o m m a n d S yn yn t a x : >-->--- SAVe SAVe ---+----+--| |--|--| |--|--| ‘--- 3.15.2 SETup SETup -----------. . | CLAshe CLAshes s ----| ----| | APProv APProved ed ---| ---| | ALL ---------------+--+--- filename ---+----+--- OVer OVer ---. ---. | | ‘------------+---> Restoring Data from a File Keywords: RESTORE Description: Th e RESTORE comma nd a llows llows you you t o rea d back clash clash d at a from a file. file. Dat a r estored in t his way is available for for fur fur th er r eferen eferen ce as th ough generat ed during the cur cur rent DESIGN sessio session. The effe effeccts of th e thr ee types of of dat a which ma y be rest ored ar e as follows: • S e tu t u p d a t a overwrites any cur cur rent clash para meter settings. The The restored dat a a pplies pplies to all subsequent clash checking checking an d reporting operations. • C la l a s h d a t a overwrites all current clash information. The original clash nu mbers, saved saved with 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 given new appr oved clash clash n um bers. Examples: RESTORE RESTORE /CLASH4 /CLASH4 Restores Restores a ll clash-rel clash-related ated dat a from t he n amed file ile 3-34 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection C om o m m a n d S yn yn t a x : >-->--- REStor REStore e --- filename ---> 3.16 Creating Macro Files Incorporating Clash Data You can can crea te a file file incorporat incorporat ing clash clash d at a in a forma t su itable for for input as a m acro to another P DMS module, module, such as DRAFT. DRAFT. 3.16.1 The Principles The process process operat operat es by merging the clash dat a with info informa tion tion read from a pre-prepared t e m p l a t e f i le le an d then outpu tting the result of th is merger to th e requir ed macro file file.. The templat e file file mu st cont cont ain a ll necessar y comma nds for th e module to which which th e dat a is t o be tran sferred, sferred, with coded coded k e y w o r d s ma rk ing th e loc locat ions ions int o which th e clash clash da ta is to be loaded. loaded. DESIGN then su bstitut es its its clash clash r eport eport d ata for t hese keywo keywords. The keywords t o be used in t he t emplat e file, file, each each of which is identified identified by $... $ markers, are as follows: $CLA1$ $CLA2$ $CL ATYP ATYP E$ $CL AP OS$ $CLATEXT$ First clashing item Second Second clashing item Clash type Clash position position in World coordinat coordinat es Clash descriptio description n as outpu t in a sta nda rd report; TOU U BO BOX X 1 of /V /VES ESS1 S1 wi with th for for example HH TO HEAD HE AD TU TUBE BE of /B /BRA RAN1 N1 $CLANUM$ $CLAOWN1$ $CLAOWN2$ $$ Note: Clash Clash number Signific Significan an t elemen t owning first clashin g item Signific Significan an t elemen t owning second second clash ing item Used to represent a single single $ cha cha racter in th e ma cro file file The us e of of the $ character in this context identifies these keywords as escape escape codes, codes, as defined in P ar t I of th e CADCentre Software Custom isation R eferenc eference e Guid 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 comm an d for for specify specifying ing ma cro-style ro-style outp ut from DESIGN ’s Clash Detection Detection m ode is is an extension of th e REPORT command options described in Section 3.11. Th e REPORT MACRO comman d mu st be follo followed wed by th e na me of a valid templat e file. file. If the na med file file can can not be rea d by DESIGN, or if th ere is an err or in t he forma forma tting of its keyword keyword cont cont ent, th en th e MACRO option ption is ignored ignored a nd su bsequent r eport eport s will will be out out put in th e standar d way. way. To genera te a ma cro file, file, having first first given given a valid REPORT MACRO template_file comma nd, use the ALPHA FILE synt ax to direct your your outp ut to the r equired macro fil filee na me. Then output your your clash r eport eport in an y of of the usu al ways (th (th at is, by using a CHECK, BOXCHECK, CHECKADD or, more pr obably, obably, OUTPUT command). When a report is out out put in m acro mode, th e follo following wing conditio conditions ns a pply: • The header and su mmar y are not output output , so tha t only the ma in body body data is merged with t he t emplate file file • Section identifiers are not output • Th e REF a n d NUMBER options options , if in force, force, are in cluded in th e $CLATEXT$ locations • Th e BOTH/FIRST/SECOND a n d PRIMARY options, if in force, force, ar e taken into account when working out which clashes to output Examples: This example illust illust ra tes h ow you you m ight creat e a DRAFT DRAFT inpu t m acro for for plott plott ing clashing clashing items identified identified by DESIGN. DESIGN. It a ssum es some some u nderst anding of th e use of DRAFT, DRAFT, alth ough you you n eed not un derst an d th e pur pose of of all of th e DRAFT DRAFT comm comm an ds in order t o fol follo low w th e basic prin ciples. A tem plat e file file cont cont ain ing th e necessary comm comm an ds for for DRAFT to display 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 $$( $CLANU $CLANUM$: M$: $CLATE $CLATEXT$ XT$ $$) $$( $$ ( NE NEW W DE DEPT PT /D /DEP EPTT-1 1 NEW NE W RE REGI GI /R /REG EGII-1 1 NEW NE W DR DRWG WG /D /DRW RWGG-1 1 NEW NE W LI LIBY BY /L /LIB IBYY-1 1 NEW NE W DL DLLB LB /D /DLL LLBB-1 1 NEW NE W RP RPLB LB /R /RPL PLBB-1 1 NEW NE W ST STYL YL /S /STY TYLL-1 1 TU ON CL OFF DLEV6 NEW NE W RR RRST ST /R /RRS RSTT-1 1 NEW NE W RR RRUL UL /R /RRU RUL-1 L-1 USE US E /S /STY TYLL-1 1 FO FOR R AL ALL L $$) /DLLB-1 NEW IDLI IDLI /IDLI/IDLI-$CL $CLANUM ANUM$ $ ADD $CLAOW $CLAOWN1$ N1$ $CLAOWN $CLAOWN2$ 2$ /DRWG-1 NEW SHEE /CLASH-SHEET /CLASH-SHEET1-$CLAN 1-$CLANUM$ UM$ SIZE SI ZE A4 NEW VIEW VIEW /VIEW1 /VIEW1-$C -$CLAN LANUM$ UM$ VREG XR 0.46 YR TO XR 0.9 YR 1 IDLN /IDLI-$CLANU /IDLI-$CLANUM$ M$ VTYPE VTYPE UNIV UNIV RRSF RRSF /RRST/RRST-1 1 VSCA VS CA 1/ 1/40 40 THPOS THPOS $CLAPO $CLAPOS$ S$ DIR N NEW VIEW VIEW /VIEW2 /VIEW2-$C -$CLAN LANUM$ UM$ VREF XR 0 YR 0.1 TO XR 0.44 YR 0.55 IDLN /IDLI-$CLANU /IDLI-$CLANUM$ M$ VTYPE VTYPE UNIV UNIV RRSF RRSF /RRST/RRST-1 1 VSCA VS CA 1/ 1/40 40 THPOS THPOS $CLAPO $CLAPOS$ S$ DIR E 0.01 D NEW VIEW VIEW /VIEW3 /VIEW3-$C -$CLAN LANUM$ UM$ VREG XR 0.46 YR 0.1 TO XR 0.9 YR 0.5 IDLN /IDLI-$CLANU /IDLI-$CLANUM$ M$ VTYPE VTYPE UNIV UNIV RRSF RRSF /RRST/RRST-1 1 VSCA VS CA 1/ 1/40 40 THPOS THPOS $CLAPO $CLAPOS$ S$ LOOK LO OK D NEW VIEW VIEW /VIEW4 /VIEW4-$C -$CLAN LANUM$ UM$ VREG XR 0 YR 0.6 TO XR 0.44 YR 1 IDLN /IDLI-$CLANU /IDLI-$CLANUM$ M$ VTYPE VTYPE UNIV UNIV PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 3-37 Clash Detection RRSF RRSF /RRST/RRST-1 1 VSCA VS CA 1/ 1/40 40 THPOS THPOS $CLAPO $CLAPOS$ S$ ISO 3 SHEE NEW NE W NO NOTE TE NEW NE W TE TEXP XP AT X1 X137 37 Y3 Y32 2 ALIGN HB JUST C CHEI 4 FONT 1 BTEX BTEX ’$CLAN ’$CLANUM$ UM$: : $CLATEX $CLATEXT$’ T$’ SHEE UPDATE UPDATE DESI DESI PLOT PLOT SHEE SHEE FILE FILE /$CLASH /$CLASHPLO PLOT$C T$CLAN LANUM$ UM$ $$(---------------------------------------------------$$) You could could nam e th is templa te file file /DRA /DRAFT.TEM FT.TEM an d th en m erge existin existin g clash clash dat a with it to crea crea te a DRAFT ma cro inpu t file file /DRA /DRAFT.MA FT.MAC, C, thu s: REPORT REPORT MACRO MACRO /DRAFT. /DRAFT.TEM TEM specifi specifies es ma cro mode mode a nd tem plat e file file ALPHA ALPHA FILE FILE /DRAFT /DRAFT.MAC .MAC specifi specifies es mer ged outpu t file (th (th e ma cro) $P ’$ ’$$( $( DR DRAF AFT T ma macr cro o cr crea eate ted d us usin ing g DR DRAF AFT. T.TE TEM M $$ $$)’ )’ $P ’ ’ leaves blank line after header OUTPUT out put s all cur rent clash dat a to macro $P ’$ ’$$. $.’ ’ adds macro end mar ker $. APLH AP LHA A FI FILE LE EN END D closes output file REPO RE PORT RT MA MACR CRO O OF OFF F reverts to norm norm al out 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 fo for each clash clash output . If you you ru n th is ma cro, cro, th e specifi specified ed four four views views will be plotted plotted for for each pa ir of clash ing items dia gnosed and outpu t by DESIGN . Each set of views views will be sent to a plotfile plotfile nam ed /CLA /CLASHP SHP LOT n , where n is the clash n um ber alloc allocated by DESIGN. C om o m m a n d S yn yn t a x : >-->--- REPor REPort t --- MACro MACro ---+----+--- template_filename ---. | | ‘--- OFF ------------------------------+--+---> -> Querying: Q CL CLAS ASH H RE REPo Port rt MA MACro Cro Gives Gives na me of tem plat e file file (or (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 ddition t o alpha alpha nu meric reporting of of clash clash da ta (to your your term inal or to a file) file),, DESIGN can show t he locat locat ions ions of clash clash es gra phically by highlighting the clashing elements on the display. When gr aph ical ical report ing is switched switched on, for for each clash clash foun foun d, th e element in t he obstr uction uction list (the ‘c ‘clash ee’) ee’) is is displayed in th e CLASH CLASH colour olour an d t he element in t he check list (th e ‘c ‘clash er’) er’) is displayed in t he OBST colo colour ur . If a clash clash ing elemen elemen t is alr eady in th e dra wlist wlist (i.e. (i.e. already displayed), it will will be highlight highlight ed by a cha cha nge to th e appr opriate colo colour ur . If th e element is not curr ent ly displayed, it it will be added to th e dra wlist wlist au toma tically tically (in (in t he defau lt visible visible col colour) our) an d will th en be highlighted in the appropriate colour. The element element stays h ighlig ighlighted hted un til another clash check check is r un , or or un til you you rem ove ove all gra phical highlighting specific specifically ally by using t he RESETHIGHLIGHT command. Examples: REPORT REPORT GRAPHI GRAPHICS CS ON REPORT REPORT GRAPHI GRAPHICS CS OFF Highlights clashes on the graphical display Clashes not highlighted on the graphical display (the default) RESET Removes Removes gra phical highlightin g from a ll Vo Volume views views C om o m m a n d S yn yn t a x : >-->--- REPort REPort --- GRAphi GRAphics cs ----- > ---> ---> >-->--- COLo COLour ur -+-+- CLAS CLASH H -. | | ‘- OBST --+- colour_n colour_name ame ------------------------. --. | | ‘- MIX MIX RED n GREen REen n BLUe LUe n -+-> +-> >--- RESEThig RESEThighlig hlight ht ---> Querying: Q CL CLAS ASH H RE REPo Port rt GR GRAp Aphi hics cs 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 checking on on dema nd, as a ssumed by th e preceding comma comma nd syn ta x in in t his chapt er, you you m ay check check for for clash clash es au toma tically tically each time you modify modify th e design. 3.18.1 Specifying Automatic Automatic Clash Detection Mode Keywords: AUTOCLASH Description: When a ut omat ic clash clash checking checking is switched On, a clash clash check check is car ried out out at th e end of every every comma comma nd line in which which a n element h as been m odified dified in some way th at could cau cau se a clash to oc occur ; tha t is: • When a n ew ele element ment ha s been creat creat ed • When a n element ’s positio position n a nd/or nd/or orienta tion has been chan ged • When a n element ’s geomet geomet ry ha s been cha cha nged Each clash clash check is car car ried out u sing the curr ent option ption 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 clash check r eplace those of an y previous previous checks, so th at an y reported reported clash clash es m u s t resu lt from from t he actions of th e last comman d. Your Your a tt ent ion ion will alrea dy be foc focussed ussed on th e cur cur ren t element, so tha t it is usu ally most most convenien convenien t t o rely on on gra ph ical ical highlighting to show th e clash clash (as explained explained in S ection ection 3.17), 3.17), rat her tha n t o out out put th e clash clash dat a t o a file file.. Yo You can u se the OUTPUT comman d to see more deta ils of of the clash clash if requ ired. Aut omat ic clash clash checking is switched Off Off by defau defau lt. C om o m m a n d S yn yn t a x : >-->--- AUTOC AUTOCLAS LASH H --- > ---> ---> Querying: Q AUTOCL AUTOCLASH ASH Note: In order t o avoid avoid spurious clash clash r eport eport s when a new Bran ch is created, th e last s ection ection of implied tube in a Br an ch is checked only only if th e Bran ch LTAI LTAI at tr ibute is set t o Tru Tru e. (The (The LTAI LTAI at tr ibute is set au toma tically tically by DESIGN wh en th e Bran ch Tail is positioned.) positioned.) The clash-checking clash-checking r ules a re as follo follows: ws: 1. If the cur cur rent element element is a Piping Component Component a n d is the last component in t he Br an ch, then its leave tu be is checked only only if th e Bran ch LTAI LTAI at tr ibute is set set t o Tru 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 which h as no members, then t he tu be which which const const itut es th e Bran ch is checked checked only only if th e Bran ch LTAI LTAI at tr ibute is set to True. 3.18.2 Logging the Clashes Keywords: CLASHLIST Description: In order t o pr ovide ovide an a udit t ra il of th e effe effecct of th e cur cur ren t session, th e system k eeps a list of of all elemen elemen ts for for wh ich ich it h as carr ied out out an au toma tic clash clash check. check. You You ma y review th e effec effectt of your your design chan ges by rerun ning a clash check check on a ll the element element s in t his list. Note tha t t he r esults of th e chec checks ks der ived ived from from t he clash clash list list in th is way will will be based on th e cur cur ren t option option set tings, which may n ot be th e sam e as th ose in force force when th e original original checks checks were m ade. Examples: CLASHLIST CLASHLIST DISPLAY DISPLAY Reru ns a clash check on on a ll elements in t he clash clash list CLASHLIST CLASHLIST EMPTY Removes Removes all element s from th e clash clash list list 3.19 Error Messages in Clash Detection Mode The follo following wing err or mess ages a re th ose which which ar e specifi specificc to DESIGN’s DESIGN’s Clash Detection Detection mode. (69: (69:4) 4) May May on only ly spec specif ify y tube tube on pipi piping ng or hang hanger er comp compon onen ents ts You ha ve tr ied to specif specify y implied tube conn conn ected ected t o an in appr opr iate t ype of of element (see Section Section 3.2 for for examples of the synt ax). (69: (69:5) 5) Must Must be a BRA BRANC NCH H or or HA HANGER NGER to spec specif ify y HEA HEAD D or or TA TAIL tube tube You have tr ied to specify specify a h ead or ta il tu be connected connected to an ina ppr opriate type of elemen elemen t (see (see Section Section 3.2 for for exam ples of th e synt ax). (69:7) name/refno has not been fully mapped The specif specifie ied d element element ha s not h ad its positio 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 element to the obstru ction tion list list which which is a lready present in t he list. list. Use the Q CLASH OBSTRUCTION comma nd t o check check th e current list if necessary. (69:9) name/refno is not in the spatial map The specif specifie ied d element element ha s not h ad its positio 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 or exclud exclud e an elemen t from th e obstr obstr uction uction list which which is not present in th e list. list. Use the Q CLASH OBSTRUCTION command to check check th e cur cur ren t list if necessar y. (69:12) Approved cl clash nu number integer is not in approval list You ha ve tried to remove or or r eappr ove ove a clash clash by referr referr ing to an a ppr oved oved clash id which which is n ot pr esent in t he list. Use the OUTPUT APPROVED comma nd if necessar necessar y to check th e cur cur ren t list. (69:13) Element type word is not currently a section header You ha ve tried t o remove a section section from th e ma in body of of the r eport wh ich ich is not presen t in t he list of sections. sections. Use th e Q CLASH REPORT MAIN comma nd t o check check th e cur cur ren t sections sections if necessar necessar y. (69:16 (69:16)) Maximu Maximum m num numbe berr of of eleme element nt typ types es for the NOCHE NOCHECK CK op optio tion n exc exceed eeded ed The ma ximum nu mber of element element types which you you m ay specify specify in a NOCHECK comm 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 eviously specif specified ied in a NOCHECK command. (69: (69:18 18)) Clea Cleara ranc nce e val value ue mu must st be po posi siti tiv ve You ha ve specif specified ied a negat ive ar gumen t in a CLEARANCE command. You mu st specif specify eith eith er a positiv positivee value (whic (which h m ust be greater t ha n t he curr ent touch gap) or zero (which switches the clearance option off). (69: (69:19 19)) (69: (69:2 20) (69:21 (69:21)) (69: (69:22 22)) (69: (69:23 23)) Clea Cleara ranc nce e val value ue mus mustt be gre great ater er tha than n touc touchi hing ng gap gap Touching ing ga gap mu must be be po positi sitiv ve Touch To uchin ing g gap gap may no nott be be grea greater ter than than curr current ent cleara clearance nce Tou ouch chin ing g ov overla erlap p mus mustt be be pos posit itiv ive e Inva Invali lid d ele eleme ment nt type type for for an an app appro rove ved d cla clash sh See Section 3.14.2 for the valid ways of specifying approved clashes. (69: (69:24 24)) App ppro rov ved clas clash h alre alread ady y exis exists ts You have tr ied to add a clash t o th e appr oval oval list list wh ich ich is alrea dy presen t in th e list. list. Use th e OUTPUT APPROVED comma nd to chec check k t he curr ent list 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 or r eappr ove ove a clash clash by referr referr ing to an a ppr oved oved clash id which which is n ot pr esent in t he list. Use the OUTPUT APPROVED comma nd if necessar necessar y to check check th e cur cur ren t list. See Section Section 3.14.2. 3.14.2. (69: (69:26 26)) There Ther e are are no item items s in in the the obs obstr truc ucti tion on list list You cann ot r un a clash clash check unt il you you h ave added at least least one element to the obstruction list. (69:27 (69:27)) Maximu Maximum m num number ber of elemen elementt types types for the SECT SECT opti option on exceed exceeded ed The ma ximum nu mber of element element types which you you m ay specify specify in a REMOVE SECTIONS comma nd is 20. 3-42 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection (69: (69:28 28)) Clas Clashe hes s cann cannot ot be be save saved d as no cla clash sh run run has has bee been n made made Th e SAVE CLASHES command can only save clash data currently held in mem ory from from th e most recent clash clash -checking -checking ru n. Ther e is no valid data in memory. (69:29) Error in in fi file fo format You have pr obably obably tried to restore da ta from a file file which was not wr itten to by a DESIGN (or (or CLASHER) SAVE command. (69: (69:3 33) No clash lash run run has been made ade Th e SAVE CLASHES command can only save clash data currently held in mem ory from from th e most recent clash clash -checking -checking ru n. Ther e is no valid data in memory. (69:34) File filename already exists. Output defaulted to terminal You can can only overwrite overwrite t he cont cont ent s of an existin existin g fil filee by using eith er t he FFILE comma nd or th e FILE ... OVER option. Your FILE comma nd h as been ignored ignored a s a pr otection tection a gainst accidenta accidenta lly overwr overwr iting th e nam ed file 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 inaccessible for for writ ing t o). o). Your Your outpu t will will th erefore erefore be sent to your your ter mina l un til you you s pecif pecify y a valid file file nam e. (69:36) File filename does not exist The file file from from wh ich ich you a re t rying t o read is n ot accessible accessible from from t he OS directory from from wh ich ich you you ent ered P DMS. Do you you need to give give th e full path na me for for th e fil file? e? (69:37) File filename already exists You can can only overwrite overwrite t he cont cont ent s of an existin existin g fil filee 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: (69:39 39)) Page Page width width may may no nott be be les less s tha than n 50 50 cha chara ract cter ers s A page width of less tha n 50 char acters will be too na rr ow to accommodate accommodate th e clash clash dat a lines in in th e report report . (69: (69:40 40)) Page Page leng length th mu must st be betwe between en 20 and and 200 200 line lines s The page length m ust be of of a su itable length t o accommodate accommodate a s ensible top top an d bottom bottom ma rgin an d a r easonable nu mber of report lines. lines. (69: (69:41 41)) Page Page marg margin in mu must st be betw betwee een n 0 and and 20 20 The mar gin gin width must be positiv positivee and must allow allow enough rema ining line line length to accommodate accommodate a typical typical report line. (69: (69:43 43)) No spat spatia iall map map exis exists ts for for DB con conta tain inin ing g name/refno The specifi specified ed element form form s par t of a DB for for wh ich ich a spa tial ma p ha s not yet been crea crea ted. The positiona positiona l data for for t he element is t her efore efore un available for for clash checking. 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 specif specifie ied d element element ha s not h ad its positio positiona l data upda ted in t he spat ial map since since it was conn conn ected ected t o the n ext downst downst ream component. (69: (69:48 48)) No appr appro oved ved cla clash shes es exis existt bet betwe ween en name/refno and name/refno You ha ve tried to rea ppr ove one one or more clash clash es between n am ed items for for which no ap pr oved oved clash clash es ha ve been specifi specified. ed. (69:56) Unable to to op open fi file filename The s pecif pecified ied file file can can not be foun foun d. Check t ha t you you ha ve specifi specified ed its correct path na me an d t hat th e directory directory co cont aining it is accessib accessible le from from th e directory directory from which which you ent ered P DMS. (69:57) Line integer of macro template filename is too long The specifi specified ed comma comma nd line in your t emplat e file file is of of such such a length th at , when t he clash clash -checking -checking keywords keywords h ave been replaced by th e correspondin correspondin g clash da ta, it exceeds exceeds the m aximum per mitted length for a PDMS co comma nd line. (69:58) Line integer of macro template filename does not have matching dollar signs Ea ch k eyword eyword in a ma cro templa te file file must be enclo enclosed sed between a pa ir of $ of $ escape characters. The $ cha ra cter s in th e specifi specified ed file file do not form form properly matched pairs. (69:59) Line integer of macro template filename has unrecognised keyword See Section Section 3.16 for for a list of valid valid keywords for u se in ma cro tem plat e files. files. (69:60) Macro template filename has no keywords Ther e are n o identifiable loc locat ions ions in t he tem plat e to which which clash clash da ta can be tra nsferred. DESIGN DESIGN cannot check check th e co comma nd synt ax in th e template an d it is m ost likely likely th at the enclo enclosing sing $ characters have simply been omitted from t he k eywords eywords . See Section Section 3.16. (69: (69:61 61)) Spat Spatia iall map map mark marked ed as inco incomp mple lete te ( for for DB integer ) The positio positiona na l data h as not been updat ed in in t he spatial map since the specifi specified ed 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 off will will cau cau se th e ma p to be flagged flagged as incomplete if a n y design chan ge is made, even if no clash clash es ar e affec affected. ted. (69:66 (69:66)) No ob obstr struc uctio tion n list list.. Use Use ‘OBS ‘OBS ALL ALL’’ or or ‘OBS ‘OBS id1 id2 id2 ... ... idn idn’’ You cann ot r un a clash clash check unt il you you h ave added at least least one element to the obstruction list. (69:67 (69:67)) Currentl Curre ntly y OBS OBS ALL ALL.. Specif Specifyi ying ng add additi ition onal al obstr obstruct uctio ions ns has has no effect effect Since the obstruction list already comprises all relevant elements in the Design Design DB, th ere is no point point in tr ying to add specifi specificcally nam ed element s to th e list. list. 3-44 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3 Clash Detection (69: (69:68 68)) No tem templ plat ate e file file has has bee been n spec specif ifie ied d for for macr macro o outp output ut When using th e REPORT MACRO option you m u s t specify specify th e na me of th e tem plat e file file from from wh ich ich t he st ru ctur e of of th e macro is is to be rea d. This is is quite in dependen t of the specific specificat at ion ion of the out put file file (FILE or FFILE comman d) which which defines wher e th e final final ma cro is to be be sent . (69: (69:79 79)) ALL no nott val valid id for for EXC EXCLU LUDE DE comm comman and d The mem bers of obstru ction list elemen elemen ts wh ich ich a re t o be excluded excluded from th e list mu st be individua lly specif specified. ied. EXCLUDE ALL would effectively eliminate eliminate t he en tire obstruction obstruction list list (use REMOVE OBSTRUCTION ALL if you you r eally wan wan t t o do th is). is). (69:80) name/refno is already in the exclusion list You have tr ied to add a n element to the exclusio exclusion n list which is already present in t he list. list. Use the Q CLASH OBSTRUCTION comma nd t o check 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 exclusion list wh ich ich is n ot present in t he list. list. Use the Q CLASH OBSTRUCTION comma nd t o check 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 chapt er t ells ells you you h ow to use t he DESIGN EXPORT comma nd to identify a list list of objec objects ts which a re to be r eviewed eviewed gra phically (usin (usin g Cad cent re’s re’s RE VIEW product product r an ge) an d to define define how they are t o be be represent ed. EXPORT extracts from th e PDMS Design Design dat abase t he r elevant elevant da ta for t he pr imitives imitives whic which will will make u p t he display, incl including uding th e Design Design h ierarchy, and st ores it in an inter mediat e file file (a (a m o d e l fi f i le l e ) for for u se by REVIE W. 4.1 The Model File To specif specify y th e na me of the m odel file file to which which design da ta is to be copied, copied, use one of of the comm comm an ds: EXPORT FILE filename EXPORT FILE filename READ Opens an existin existin g file file in r ead-only ead-only mode, allowing allowing its cont cont ent to be queried but n ot overwritten. overwritten. EXPORT FILE filename OVERwrite Overwrites a n existing file file of of th e same n am e. EXPORT FILENote text Adds a line of of user-supp lied lied text to th e model file file header . For example, EXPORT EXPORT EXPO EX PORT RT EXPO EX PORT RT EXPO EX PORT RT FILE FILE /TESTF /TESTFILE ILE FILE FI LE /T /TES ESTF TFIL ILE E READ READ FILE FI LE /T /TES ESTF TFIL ILE E OVER OVER FILE FI LENO NOTE TE ’P ’Pla latf tform orm PA PA2 2 RE REVI VIEW EW Da Data ta’ ’ To quer y the na me of th e cur cur ren t m odel file file,, use th e comma 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 copi copied ed to the model file file ar e held in a d r a w l i st st . Elemen ts ma y be specif specified ied explic explicitly itly or or by usin g a P ML expression to define define s e le l e c t i o n c r i t e r i a . For inform inform ation about P ML, see see th e Cadcentre Software Customisation Reference Manual. Only s i g n i fi fi c a n t e l e m e n t s , such a s BRAN, BRAN, EQUI , SUBS, HANG, STRU, PTRA, etc., etc., ma y be added t o or or r emoved emoved from th e dra w list. If you you t ry t o add or rem ove ove an element below a signifi significant cant element (th at is, a primit ive), ive), the wh ole ole of its owning signific significan an t elemen t will be added t o or or r emoved emoved from th e dra w list. Colour Colo ur s to be used t o display display th e diffe differen ren t elemen t t ypes can can be specifi specified ed explic explicitly or or by usin g th e A u t o c o l o u r selection selection ru les - see th e AUTOCOLOUR ference nce Man ual . comma nd in P ar t 1 of th e PDMS DE S IGN R efere Examples: EXPORT EXPO RT /V /VES ESS1 S1 CO COLO LOUR UR 2 Specif Specifies ies colour colour of export exported ed elemen element t direct directly. ly. EXPORT EXPO RT AU AUTO TOCO COLO LOUR UR COLO CO LOUR UR 10 ALL AL L BO BOXE XES S WI WITH TH (X (XLE LEN N GT 10 100) 0) EXPO EX PORT RT AUTOCO AUTOCOLO LOUR UR ALL BRAN BRAN ME MEMB MBER ERS S CO COLO LOUR UR (:ICOL (:ICOLOR OR OF SPREF) SPREF) Specifies using AUTOCOLOUR rules. The co colour lour nu mber, wheth er given given as an integer or or a s an expressio expression, refers to th e col colour our n um ber to be used in REVIEW. The order order in which which r ules are given given is importa importa nt , bec becau se they ar e evaluat evaluat ed in this order u ntil a ru le is is encoun encoun tered for for which which th e selec selectio tion n criteria a re sat isfied. isfied. This This is th e ru le from from wh ich ich t he colo colour ur is ta ken . If no ru le is is sat isfied, isfied, or if no col colour our r ules h ave been given, or if th e selection selection is inva lid for for some rea son, then colo colour ur 0 is used. Rules ma y be reorder reorder ed, removed and cont cont rolled rolled by the following commands: EXPORT EXPORT AUTOCO AUTOCOLOU LOUR R ON Tur ns th e use of Aut ocol ocolo our in E XPORT m ode on. on. Th e ru les will will be ignored ignored unt il tur ned on. on. EXPORT EXPORT AUTOCO AUTOCOLOU LOUR R OFF Tur ns th e us e of Autocol Autocolour our in E XPORT m ode off off.. EXPORT EXPORT AUTOCO AUTOCOLOU LOUR R RESET RESET Clears t he curr ent s election election by rem oving oving all rules. EXPO EX PORT RT AU AUTO TOCO COLO LOUR UR REMOV REMOVE E 4 Removes Removes r ule 4. EXPO EX PORT RT AU AUTO TOCO COLO LOUR UR REORD REORDER ER 4 TO 99 Reord Reord ers r ule 4 t o positio position n 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 Autocol Autocolour our r ules a re a llowe llowed d a t p resen t. Th e follo following wing queries are also available: Q EX EXPO PORT RT AU AUTO TOCO COLO LOUR UR NU NUM M Return s the num ber of of ru les. Q EX EXPO PORT RT AU AUTO TOCO COLO LOUR UR MO MODE DE Retu rn s th e mode stat e (on (on or or off) off).. Q EXPORT EXPORT AUTOCO AUTOCOLOU LOUR R integer Returns the selection criteria for rule integer. Q EX EXPO PORT RT AU AUTO TOCO COLO LOUR UR FO FOR R identifier Retu rn s colo colour ur to be selected selected for ident ified ified element. 4.3 Controlling the Representation of Holes Holes may be represented realistically, with colour shaded inner surfaces, and ma y be ‘seen ‘seen t hr ough’. ough’. To contr contr ol th e app ear an ce of of holes, holes, use t he comm comm an ds EXPORT HOLEs ON HOLEs OFF (default) HOLEs SOLID EXPORT HOLES SOLID repr esent s h oles oles as s olids olids in colo colour ur 1, which which by defau lt is black. black. Solid Solid holes holes cann ot be seen th rough. The sta te of the hole hole settings ma y be queried using Q EXPORT HOLES Note: Since holes are const const ru cted u sing facets facets wh ich ich involve involve a lar ge amoun t of geometric data, switching holes ‘on’ will increase the computational overh ead when processing. processing. The more holes holes in th e model, model, the longer longer t he model file file will will ta ke t o gener gener at e, and th e more slowly slowly it it will be drawn in RE VIEW. Note tha t other represent ation settings, such such a s Tube, Cent Cent reline, reline, Obstruction, Obstruction, Insulat ion ion a nd Dr awing Leve Level, l, are t aken from th e cur cur rent DESIGN settings. 4.4 Copying Data to the Model File To tr an sfer sfer dat a a bout bout th e primitives primitives owned owned by all elements elements in t he cur cur rent dra w list list int o the curr ent model file, ile, use th e co comma nd EXPORT FINish This co comma nd does not cha cha nge the curr ent d ra w list. 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 >->-- EXPO EXPORT RT --+--+-| | | | | |-| |-| | | | | | | | | |-| | | | | |-| ‘-- Note: 4-4 HOLE HOLES S --+--+-- ON --------. -. | | |-- OFF ----| | | ‘-- SOLID --+--> FILENote FILENote FILE FILE text --> name --+---+-- TEXT TEXT --. | | ‘----------+-- READ -------. | | |-- OVERwrite --| | | ‘---------------+---> .-------<----. / | t> --*---*-- t> --’ | |-- COLour integer --> | ‘--> FINish FINish --> l> --> is the gene general ral sel selec ectio tion n syntax. syntax. i s t h e AUTOCOLOUR command eference rence For more inform inform ation, see Part 1 of th e PDMS DES IGN R efe 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 Index data consistency checking, 2-12 Spatial map clash detection, 3-2 data consistency checking, 2-3, 2-8 TOUCHING command clash detection, 3-8 TOLERANCE command Index-2 PDMS DESIGN Reference Manual Part 4: Utilities Version 11.3

Pdms Design

Recommend Documents