Piping Reference PDF

Piping
Reference
CADDS 5 15.0
DOC36806-015
Parametric Technology Corporation

Copyright 2007 Parametric Technology Corporation. All Rights Reserved.
User and training guides and related documentation from Parametric Technology Corporation and its
subsidiary companies (collectively PTC) is subject to the copyright laws of the United States and other
countries and is provided under a license agreement that restricts copying, disclosure, and use of such
documentation. PTC hereby grants to the licensed software user the right to make copies in printed form
of this documentation if provided on software media, but only for internal/personal use and in
accordance with the license agreement under which the applicable software is licensed. Any copy made
shall include the PTC copyright notice and any other proprietary notice provided by PTC. Training
materials may not be copied without the express written consent of PTC. This documentation may not be
disclosed, transferred, modified, or reduced to any form, including electronic media, or transmitted or
made publicly available by any means without the prior written consent of PTC and no authorization is
granted to make copies for such purposes.
Information described herein is furnished for general information only, is subject to change without
notice, and should not be construed as a warranty or commitment by PTC. PTC assumes no
responsibility or liability for any errors or inaccuracies that may appear in this document.
The software described in this document is provided under written license agreement, contains valuable
trade secrets and proprietary information, and is protected by the copyright laws of the United States and
other countries. It may not be copied or distributed in any form or medium, disclosed to third parties, or
used in any manner not provided for in the software licenses agreement except with written prior
approval from PTC.
UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL

DAMAGES AND CRIMINAL PROSECUTION.
For Important Copyright, Trademark, Patent, and Licensing Information: For Windchill products, select
About Windchill at the bottom of the product page. For InterComm products, on the Help main page,
click the link for Copyright 2007. For other products, select Help > About on the main menu for the
product.
UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGEND

This document and the software described herein are Commercial Computer Documentation and
Software, pursuant to FAR 12.212(a)-(b) (OCT95) or DFARS 227.7202-1(a) and 227.7202-3(a)
(JUN95), and are provided to the US Government under a limited commercial license only. For
procurements predating the above clauses, use, duplication, or disclosure by the Government is subject
to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software Clause at DFARS 252.227-7013 (OCT88) or Commercial Computer Software-Restricted
Rights at FAR 52.227-19(c)(1)-(2) (JUN87), as applicable. 02202007
Parametric Technology Corporation, 140 Kendrick Street, Needham, MA 02494 USA

Table of Contents
Preface
Related Documents _______________________________________ xxvii
Book Conventions ________________________________________ xxviii
Window Managers and the User Interface _________________ xxviii
Online User Documentation ________________________________ xxix
Online Command Help _____________________________________ xxx
Printing Documentation ____________________________________ xxx
Resources and Services ____________________________________ xxxi
Documentation Comments ________________________________ xxxi
Piping Design Overview

Piping Design Features ___________________________________________ 1-2
Generating Piping Specification Files ___________________________ 1-2
Constructing, Modeling, and Detailing Pipelines_________________ 1-3
Producing Isometric Drawings __________________________________ 1-5
Series A ____________________________________________________ 1-5
Series B ____________________________________________________ 1-6
Generating Piping and Instrumentation Reports _________________ 1-7
Extracting Useful Information for Analyses Programs _____________ 1-8
Pipe Reporting ___________________________________________________ 1-9

Interpreting Piping Networks ___________________________________ 1-9
Generating Report Data _____________________________________ 1-10
Properties and Part Properties ___________________________________ 1-11
Piping Reference Contents-iii

Part Properties _______________________________________________ 1-11
Property Libraries _____________________________________________ 1-11
Creating Properties ___________________________________________ 1-11
Properties and Part Properties Library _____________________________ 1-13

ABOVE ____________________________________________________ 1-14
ATTACHMENT______________________________________________ 1-14
AUTOANN _________________________________________________ 1-14
BRAD (Bend Radius) _______________________________________ 1-14
BRANCH __________________________________________________ 1-14
COMPNAME (Component Name) __________________________ 1-15
CONNECTOR ______________________________________________ 1-15
CUTSPOOL ________________________________________________ 1-15
EFFTXT ____________________________________________________ 1-15
ENDTYPE __________________________________________________ 1-15
EQUIP _____________________________________________________ 1-16
FITTYPE (Fitting Type) _______________________________________ 1-16
GASKET ___________________________________________________ 1-16
IGNORE ___________________________________________________ 1-16
INNERDIAM (Inner Diameter) _______________________________ 1-16
INSLOC (Instrument Location) ______________________________ 1-17
INSTR (Instrument Lines) ____________________________________ 1-17
INSULATION _______________________________________________ 1-17
INTERNAL _________________________________________________ 1-17
ITEMNO (Item Number) ____________________________________ 1-17
LASTLINK __________________________________________________ 1-17
LENGTH ___________________________________________________ 1-18
LPROP (Line Property)______________________________________ 1-18
NOBREAK _________________________________________________ 1-18
NOSEL (No Selection) ______________________________________ 1-18
NPS (Nominal Pipe Size) ____________________________________ 1-18
OPC (Off-page Connector) ________________________________ 1-19
OUTERDIAM (Outer Diameter) ______________________________ 1-19
PARTTYPE _________________________________________________ 1-19
PERMAPP (Permanent Appearance) _______________________ 1-20
PLEN (Parametric Length) __________________________________ 1-20
PLIST (Parameter List) ______________________________________ 1-20
PNAME (Procedure Name) _________________________________ 1-20
PROJNAME (Project Name) ________________________________ 1-20
PSCL (Parametric Scale) ___________________________________ 1-21
Contents-iv Piping Reference

SHAPECODE______________________________________________ 1-21
SHAPETYPE _______________________________________________ 1-21
SINGLE ___________________________________________________ 1-21
SKEW ____________________________________________________ 1-21
SNAME (Selection Name) _________________________________ 1-22
SPEC (Specification) ______________________________________ 1-22
SPECIAL __________________________________________________ 1-22
SPOOLIST _________________________________________________ 1-22
STOCKNO (Stock Number) ________________________________ 1-22
TAP ______________________________________________________ 1-23
TEMPLIN (Temporary Line) _________________________________ 1-23
TERMNAM (Terminus Name) _______________________________ 1-23
TITLENOD _________________________________________________ 1-23
TRIM _____________________________________________________ 1-23
WELD ____________________________________________________ 1-23
WELDTABL ________________________________________________ 1-24
XYZ ______________________________________________________ 1-24
Suggested Layering Conventions _______________________________ 1-25
Support Files ___________________________________________________ 1-26

Library Parts _________________________________________________ 1-26
Data Files ___________________________________________________ 1-26
Master Catalogs (MCATS) _________________________________ 1-27
Piping Specification Input Files (INFILES) ____________________ 1-27
Piping Specification (Autoselection) Files (ASFILES) _________ 1-27
Directory Files (DRFILES) ___________________________________ 1-28
Parameter Files (PAFILES) __________________________________ 1-28
Procedure Files ___________________________________________ 1-28
Description Files __________________________________________ 1-28
Execute Files _____________________________________________ 1-28
Routines _________________________________________________ 1-29
Designing a Pipeline ____________________________________________ 1-30

Basic Approach to Pipe Modeling ____________________________ 1-31
Generating Piping Specifications _____________________________ 1-32
Autoselection Process _______________________________________ 1-32
Parametric Procedure Files___________________________________ 1-34
Constructing Equipment ________________________________________ 1-36
Piping and Instrumentation Diagrams (P&IDs) ____________________ 1-37
Piping Reference Contents-v

Defining Projects ________________________________________________ 1-38
Producing Drawings _____________________________________________ 1-39
Generating Piping Reports _______________________________________ 1-40

Reporting from the Three-Dimensional Model _______________ 1-40
Reporting from the P&ID ___________________________________ 1-40
Piping Commands - Part 1

Explicit Modeling Piping Commands ______________________________ 2-2
Isometric Drawing Commands ______________________________ 2-3
Command Format _______________________________________________ 2-4

Description_________________________________________________ 2-4
Valid Modes _______________________________________________ 2-4
Syntax _____________________________________________________ 2-4
Modifiers ___________________________________________________ 2-4
ANNOTATE ISOMETRIC ____________________________________________ 2-5

Description_________________________________________________ 2-5
Valid Modes _______________________________________________ 2-5
Syntax _____________________________________________________ 2-5
Modifiers ___________________________________________________ 2-5
Example 1 ________________________________________________ 2-27
Example 2 ________________________________________________ 2-28
Example 3 ________________________________________________ 2-29
Example 4 ________________________________________________ 2-30
Example 5 ________________________________________________ 2-31
Example 6 ________________________________________________ 2-32
Example 7 ________________________________________________ 2-32
Example 8 ________________________________________________ 2-33
Example 9 ________________________________________________ 2-33
Example 10 _______________________________________________ 2-34
Example 11 _______________________________________________ 2-34
Example 12 _______________________________________________ 2-35
Example 13 _______________________________________________ 2-35
Example 14 _______________________________________________ 2-36
Example 15 _______________________________________________ 2-36
Example 16 _______________________________________________ 2-37
Example 17 _______________________________________________ 2-38
Contents-vi Piping Reference

Example 18 ______________________________________________ 2-39
Example 19 ______________________________________________ 2-40
Example 20 ______________________________________________ 2-41
Example 21 ______________________________________________ 2-42
Example 22 ______________________________________________ 2-43
Example 23 ______________________________________________ 2-43
Example 24 ______________________________________________ 2-44
Example 25 ______________________________________________ 2-44
Example 26 ______________________________________________ 2-45
Example 27 ______________________________________________ 2-45
Example 28 ______________________________________________ 2-46
Example 29 ______________________________________________ 2-46
Example 30 ______________________________________________ 2-47
Example 31 ______________________________________________ 2-47
Example 32 ______________________________________________ 2-48
Example 33 ______________________________________________ 2-48
Example 34 ______________________________________________ 2-48
Notes ____________________________________________________ 2-49
CHANGE PLINE (PIPELINE) _______________________________________ 2-50

Description _______________________________________________ 2-50
Valid Modes _____________________________________________ 2-50
Syntax ___________________________________________________ 2-50
Modifiers _________________________________________________ 2-51
Procedure 1 ______________________________________________ 2-52
Procedure 2 ______________________________________________ 2-52
Procedure 3 ______________________________________________ 2-52
CONSTRUCT PLINE (PIPELINE) ____________________________________ 2-53

Description _______________________________________________ 2-53
Valid Modes _____________________________________________ 2-53
Syntax ___________________________________________________ 2-53
Modifiers _________________________________________________ 2-54
Procedure 1 ______________________________________________ 2-56
Procedure 2 ______________________________________________ 2-56
Procedure 3 ______________________________________________ 2-56
Example _________________________________________________ 2-57
CREATE ISOMETRIC _____________________________________________ 2-59

Description _______________________________________________ 2-59
Valid Modes _____________________________________________ 2-59
Piping Reference Contents-vii

Syntax ____________________________________________________ 2-59
Modifiers __________________________________________________ 2-60
Procedure ________________________________________________ 2-66
Example 1 ________________________________________________ 2-66
Example 2 ________________________________________________ 2-67
DELETE BEND ____________________________________________________ 2-68

Description________________________________________________ 2-68
Valid Modes ______________________________________________ 2-68
Syntax ____________________________________________________ 2-68
Modifiers __________________________________________________ 2-68
Procedure ________________________________________________ 2-68
Example __________________________________________________ 2-69
DELETE FITTING __________________________________________________ 2-70
Description________________________________________________ 2-70
Valid Modes ______________________________________________ 2-71
Syntax ____________________________________________________ 2-71
Modifiers __________________________________________________ 2-71
Procedure ________________________________________________ 2-72
Example 1 ________________________________________________ 2-72
Example 2 ________________________________________________ 2-73
Example 3 ________________________________________________ 2-74
Example 4 ________________________________________________ 2-75
Example 5 ________________________________________________ 2-76
Example 6 ________________________________________________ 2-77
Example 7 ________________________________________________ 2-78
Example 8 ________________________________________________ 2-79
Example 9 ________________________________________________ 2-79
DELETE PENETRATION ____________________________________________ 2-80

Description________________________________________________ 2-80
Valid Modes ______________________________________________ 2-80
Syntax ____________________________________________________ 2-80
Modifiers __________________________________________________ 2-80
Procedure 1_______________________________________________ 2-80
Procedure 2_______________________________________________ 2-80
DELETE PLINE (PIPELINE) __________________________________________ 2-81

Description________________________________________________ 2-81
Valid Modes ______________________________________________ 2-81
Syntax ____________________________________________________ 2-81
Contents-viii Piping Reference

Modifiers _________________________________________________ 2-81
Procedure _______________________________________________ 2-82
Example _________________________________________________ 2-82
DELETE PSUPPORT (Pipe Support) ________________________________ 2-83

Description _______________________________________________ 2-83
Valid Modes _____________________________________________ 2-83
Syntax ___________________________________________________ 2-83
Modifiers _________________________________________________ 2-83
Procedure 1 ______________________________________________ 2-83
Procedure 2 ______________________________________________ 2-84
DIMENSION ISOMETRIC__________________________________________ 2-85

Description _______________________________________________ 2-85
Valid Modes _____________________________________________ 2-86
Syntax ___________________________________________________ 2-86
Modifiers _________________________________________________ 2-86
Procedure _______________________________________________ 2-86
Example _________________________________________________ 2-87
Notes ____________________________________________________ 2-89
DIMENSION PIPE ________________________________________________ 2-90

Description _______________________________________________ 2-90
Valid Modes _____________________________________________ 2-90
Syntax ___________________________________________________ 2-90
Modifiers _________________________________________________ 2-90
Procedure 1 ______________________________________________ 2-91
Procedure 2 ______________________________________________ 2-91
Example 1________________________________________________ 2-93
Example 2________________________________________________ 2-94
Example 3________________________________________________ 2-95
Example 4________________________________________________ 2-97
DRAW PSPOOL _________________________________________________ 2-99

Description _______________________________________________ 2-99
Valid Modes ____________________________________________ 2-101
Syntax __________________________________________________ 2-101
Modifiers ________________________________________________ 2-102
Reporting the Data for Spool Drawings in the Form Part _______ 2-108
Reporting the Flange Rotation Angle for the Pipe Spools ___ 2-108
Reporting the Rotation Angle for Pipe Spool Bending ______ 2-111
Piping Reference Contents-ix

Labeling Pipe Parts in Spool Drawing _____________________ 2-113
Matching Serial Numbers and the Contents of the Table in the
Form Part _______________________________________________ 2-114
Reporting the Bending Location of the Pipe Spools During Pipe
Bending ________________________________________________ 2-115
Reporting the Installation Position ________________________ 2-117
Reporting the Extra Clamp Length Required ______________ 2-119
Procedure 1_____________________________________________ 2-122
Procedure2 _____________________________________________ 2-123
Procedure 3_____________________________________________ 2-123
Example 1 ______________________________________________ 2-124
Example 2 ______________________________________________ 2-127
Example 3 ______________________________________________ 2-129
Notes ___________________________________________________ 2-129

GENERATE CLINE (Center Line) ____________________________________ 3-2
Description_________________________________________________ 3-2
Valid Modes _______________________________________________ 3-2
Syntax _____________________________________________________ 3-2
Modifiers ___________________________________________________ 3-3
Procedure 1________________________________________________ 3-5
Procedure 2________________________________________________ 3-5
Procedure 3________________________________________________ 3-5
Example 1 _________________________________________________ 3-6
Example 2 _________________________________________________ 3-8
Example 3 _________________________________________________ 3-8
Example 4 _________________________________________________ 3-9
Example 5 ________________________________________________ 3-10
GENERATE CSSYMBOL (Cut Section Symbol) ______________________ 3-11

Description________________________________________________ 3-11
Valid Modes ______________________________________________ 3-11
Syntax ____________________________________________________ 3-11
Modifiers __________________________________________________ 3-11
Procedure 1_______________________________________________ 3-13
Procedure 2_______________________________________________ 3-13
Procedure 3_______________________________________________ 3-13
Example __________________________________________________ 3-14
Contents-x Piping Reference

GENERATE EXPLICITPIPE _________________________________________ 3-16
Valid Modes _____________________________________________ 3-16
Syntax ___________________________________________________ 3-16
Modifiers _________________________________________________ 3-17
Example 1________________________________________________ 3-19
Example 2________________________________________________ 3-20
GENERATE ISOMETRIC___________________________________________ 3-21

Description _______________________________________________ 3-21
Valid Modes _____________________________________________ 3-21
Syntax ___________________________________________________ 3-21
Modifiers _________________________________________________ 3-22
Procedure _______________________________________________ 3-26
Example _________________________________________________ 3-26
Notes ____________________________________________________ 3-29
GENERATE MDF (Material Description File) _______________________ 3-31

Description _______________________________________________ 3-31
Valid Modes _____________________________________________ 3-31
Syntax ___________________________________________________ 3-31
Modifiers _________________________________________________ 3-32
Procedure _______________________________________________ 3-33
GENERATE PIPEDBASE ___________________________________________ 3-34

Description _______________________________________________ 3-34
Relating the 2D Schematic and 3D Model Pipeline Network_ 3-37
Valid Modes _____________________________________________ 3-38
Syntax ___________________________________________________ 3-38
Modifiers _________________________________________________ 3-38
Procedure 1 ______________________________________________ 3-44
Procedure 2 ______________________________________________ 3-44
Procedure 3 ______________________________________________ 3-45
Procedure 4 ______________________________________________ 3-45
Procedure 5 ______________________________________________ 3-46
Procedure 6 ______________________________________________ 3-46
Procedure 7 ______________________________________________ 3-46
Example 1________________________________________________ 3-47
Example 2________________________________________________ 3-47
Example 3________________________________________________ 3-47
Example 4________________________________________________ 3-48
Example 5________________________________________________ 3-48
Piping Reference Contents-xi

Example 6 ________________________________________________ 3-49
Example 7 ________________________________________________ 3-49
Example 8 ________________________________________________ 3-49
Example 9 ________________________________________________ 3-50
Example 10 _______________________________________________ 3-50
Example 11 _______________________________________________ 3-50
Example 12 _______________________________________________ 3-51
Example 13 _______________________________________________ 3-51
Notes 1 ___________________________________________________ 3-51
Notes 2 ___________________________________________________ 3-52
GENERATE PSFILE (Piping Specification File) _______________________ 3-53

Description________________________________________________ 3-53
Valid Modes ______________________________________________ 3-54
Syntax ____________________________________________________ 3-54
Modifiers __________________________________________________ 3-55
Procedure ________________________________________________ 3-58
Sample Infile ______________________________________________ 3-58
Sample Autoselection and Parameter Files _________________ 3-64
Notes _____________________________________________________ 3-67
GENERATE SPOOL _______________________________________________ 3-71

Description________________________________________________ 3-71
Valid Modes ______________________________________________ 3-74
Syntax ____________________________________________________ 3-75
Modifiers __________________________________________________ 3-76
Procedure 1_______________________________________________ 3-79
Procedure 2_______________________________________________ 3-79
Procedure 3_______________________________________________ 3-80
Procedure 4_______________________________________________ 3-80
Procedure 5_______________________________________________ 3-80
Procedure 6_______________________________________________ 3-81
Procedure 7_______________________________________________ 3-81
Procedure 8_______________________________________________ 3-81
Example 1 ________________________________________________ 3-82
Example 2 ________________________________________________ 3-84
Example 3 ________________________________________________ 3-85
Example 4 ________________________________________________ 3-87
Example 5 ________________________________________________ 3-89
Example 6 ________________________________________________ 3-90
Contents-xii Piping Reference

GENERATE SPSYMBOL (Slope Pipe Symbol) _______________________ 3-92
Description _______________________________________________ 3-92
Valid Modes _____________________________________________ 3-92
Syntax ___________________________________________________ 3-92
Modifiers _________________________________________________ 3-92
Procedure 1 ______________________________________________ 3-93
Procedure 2 ______________________________________________ 3-94
Procedure 3 ______________________________________________ 3-94
Example _________________________________________________ 3-94
HIDE INTERSECTION _____________________________________________ 3-96

Description _______________________________________________ 3-96
Valid Modes _____________________________________________ 3-96
Syntax ___________________________________________________ 3-96
Modifiers _________________________________________________ 3-97
Procedure 1 ______________________________________________ 3-99
Procedure 2 ______________________________________________ 3-99
Procedure 3 _____________________________________________ 3-100
Example 1_______________________________________________ 3-100
Example 2_______________________________________________ 3-104
HIGHLIGHT PLINE (Pipeline) _____________________________________ 3-107

Description ______________________________________________ 3-107
Valid Modes ____________________________________________ 3-107
Syntax __________________________________________________ 3-107
Modifiers ________________________________________________ 3-108
Procedure 1 _____________________________________________ 3-110
Procedure 2 _____________________________________________ 3-110
Example 1_______________________________________________ 3-111
Example 2_______________________________________________ 3-112
Example 3_______________________________________________ 3-113
Example 4_______________________________________________ 3-114
Example 5_______________________________________________ 3-115
INDICATE PENETRATION ________________________________________ 3-116

Description ______________________________________________ 3-116
Valid Modes ____________________________________________ 3-116
Syntax __________________________________________________ 3-116
Modifiers ________________________________________________ 3-117
Procedure 1 _____________________________________________ 3-118
Procedure 2 _____________________________________________ 3-119
Piping Reference Contents-xiii

Description______________________________________________ 3-119
Valid Modes ____________________________________________ 3-119
Syntax __________________________________________________ 3-119
Modifiers ________________________________________________ 3-120
Procedure ______________________________________________ 3-124
Example 1 ______________________________________________ 3-125
Example 2 ______________________________________________ 3-126
Example 3 ______________________________________________ 3-127
Example 4 ______________________________________________ 3-128
Example 5 ______________________________________________ 3-128

INSERT DATUM ____________________________________________________ 4-2
Description_________________________________________________ 4-2
Valid Modes _______________________________________________ 4-2
Syntax _____________________________________________________ 4-2
Modifiers ___________________________________________________ 4-2
Procedure _________________________________________________ 4-4
Example 1 _________________________________________________ 4-5
Example 2 _________________________________________________ 4-6
Example 3 _________________________________________________ 4-7
Notes ______________________________________________________ 4-9
INSERT FITTING ___________________________________________________ 4-10

Description________________________________________________ 4-10
Valid Modes ______________________________________________ 4-10
Syntax ____________________________________________________ 4-11
Modifiers __________________________________________________ 4-11
System Orientation Modifiers _______________________________ 4-26
Procedure 1_______________________________________________ 4-26
Procedure 2_______________________________________________ 4-27
Procedure 3_______________________________________________ 4-28
Procedure 4_______________________________________________ 4-28
Procedure 5_______________________________________________ 4-29
Procedure 6_______________________________________________ 4-29
Procedure 7_______________________________________________ 4-30
Examples _________________________________________________ 4-30
Example 1 ________________________________________________ 4-31
Example 2 ________________________________________________ 4-34
Contents-xiv Piping Reference

Example 3________________________________________________ 4-36
Example 4________________________________________________ 4-39
Notes ____________________________________________________ 4-39
INSERT PBREAK (Pipe Break) _____________________________________ 4-44

Description _______________________________________________ 4-44
Valid Modes _____________________________________________ 4-44
Syntax ___________________________________________________ 4-44
Modifiers _________________________________________________ 4-44
Procedure 1 ______________________________________________ 4-45
Procedure 2 ______________________________________________ 4-45
Procedure 3 ______________________________________________ 4-45
Example 1________________________________________________ 4-46
Example 2________________________________________________ 4-46
Example 3________________________________________________ 4-47
Notes ____________________________________________________ 4-48
INSERT PLABEL (Pipeline Label) __________________________________ 4-50

Description _______________________________________________ 4-50
Valid Modes _____________________________________________ 4-50
Syntax ___________________________________________________ 4-50
Modifiers _________________________________________________ 4-50
Procedure _______________________________________________ 4-51
Example 1________________________________________________ 4-51
Example 2________________________________________________ 4-51
Example 3________________________________________________ 4-52
Notes ____________________________________________________ 4-53
INSERT PSUPPORT (Pipe Support) _________________________________ 4-54

Description _______________________________________________ 4-54
Valid Modes _____________________________________________ 4-54
Syntax ___________________________________________________ 4-54
Modifiers _________________________________________________ 4-54
Example 1________________________________________________ 4-56
Example 2________________________________________________ 4-56
INSERT REFDIMENSION (Reference Dimension) ____________________ 4-57

Description _______________________________________________ 4-57
Valid Modes _____________________________________________ 4-57
Syntax ___________________________________________________ 4-57
Modifiers _________________________________________________ 4-58
Procedure _______________________________________________ 4-76
Piping Reference Contents-xv

Example 1 ________________________________________________ 4-76
Example 2 ________________________________________________ 4-78
Example 3 ________________________________________________ 4-79
Example 4 ________________________________________________ 4-80
Example 5 ________________________________________________ 4-81
Example 6 ________________________________________________ 4-82
Example 7 ________________________________________________ 4-83
Example 8 ________________________________________________ 4-84
Example 9 ________________________________________________ 4-85
Example 10 _______________________________________________ 4-86
Notes _____________________________________________________ 4-87

MODIFY PLINE (Pipeline) __________________________________________ 5-2
Description_________________________________________________ 5-2
Valid Modes _______________________________________________ 5-2
Syntax _____________________________________________________ 5-2
Modifiers ___________________________________________________ 5-3
Example 1 _________________________________________________ 5-6
Example 2 _________________________________________________ 5-7
Example 3 _________________________________________________ 5-9
Notes _____________________________________________________ 5-12
OFFSET PLINE (Pipeline) __________________________________________ 5-13

Description________________________________________________ 5-13
Valid Modes ______________________________________________ 5-13
Syntax ____________________________________________________ 5-13
Modifiers __________________________________________________ 5-14
Example __________________________________________________ 5-17
REFERENCE STRUCTURE __________________________________________ 5-18

Description________________________________________________ 5-18
Valid Modes ______________________________________________ 5-18
Syntax ____________________________________________________ 5-18
Modifiers __________________________________________________ 5-18
RELATE PLABEL (Pipeline Label) ___________________________________ 5-19

Description________________________________________________ 5-19
Valid Modes ______________________________________________ 5-19
Syntax ____________________________________________________ 5-19
Contents-xvi Piping Reference

Modifiers _________________________________________________ 5-19
Procedure _______________________________________________ 5-19
REPORT PIPE____________________________________________________ 5-20

Description _______________________________________________ 5-20
Valid Modes _____________________________________________ 5-20
Syntax ___________________________________________________ 5-20
Modifiers _________________________________________________ 5-21
Procedure 1 ______________________________________________ 5-29
Procedure 2 ______________________________________________ 5-29
Example 1________________________________________________ 5-29
Example 2________________________________________________ 5-32
Example 3________________________________________________ 5-32
Notes ____________________________________________________ 5-38
ROUTE PIPE _____________________________________________________ 5-40

Description _______________________________________________ 5-40
Valid Modes _____________________________________________ 5-40
Syntax ___________________________________________________ 5-40
Modifiers _________________________________________________ 5-41
Procedure _______________________________________________ 5-46
Example1 ________________________________________________ 5-46
Example 2________________________________________________ 5-47
Example 3________________________________________________ 5-48
Example 4________________________________________________ 5-49
Example 5________________________________________________ 5-50
Example 6________________________________________________ 5-51
Example 7________________________________________________ 5-52
Example 8________________________________________________ 5-53
Notes ____________________________________________________ 5-53
SAVE ANNOTATIONS ____________________________________________ 5-56
Description _______________________________________________ 5-56
Valid Modes _____________________________________________ 5-56
Syntax ___________________________________________________ 5-56
Modifiers _________________________________________________ 5-57
SELECT PPARAMETERS (Pipeline Parameters) _____________________ 5-67

Description _______________________________________________ 5-67
Valid Modes _____________________________________________ 5-67
Syntax ___________________________________________________ 5-67
Modifiers _________________________________________________ 5-68
Piping Reference Contents-xvii

Procedure ________________________________________________ 5-76
Example 1 ________________________________________________ 5-76
Example 2 ________________________________________________ 5-77
Example 3 ________________________________________________ 5-78
The CVPD/Directories File __________________________________ 5-79
Notes _____________________________________________________ 5-81
SPLIT PIPE _______________________________________________________ 5-82

Description________________________________________________ 5-82
Valid Modes ______________________________________________ 5-82
Syntax ____________________________________________________ 5-82
Modifiers __________________________________________________ 5-82
TRANSLATE EQUIPMENT __________________________________________ 5-83

Description________________________________________________ 5-83
Valid Modes ______________________________________________ 5-83
Syntax ____________________________________________________ 5-83
Modifiers __________________________________________________ 5-84
Procedure ________________________________________________ 5-86
Example 1 ________________________________________________ 5-87
Example 2 ________________________________________________ 5-88
Example 3 ________________________________________________ 5-90
TRANSLATE ISOMETRIC ___________________________________________ 5-91

Description________________________________________________ 5-91
Valid Modes ______________________________________________ 5-91
Syntax ____________________________________________________ 5-91
Modifiers __________________________________________________ 5-92
Procedure 1_______________________________________________ 5-94
Procedure 2_______________________________________________ 5-94
Example 1 ________________________________________________ 5-95
Example 2 ________________________________________________ 5-96
Example 3 ________________________________________________ 5-96
Example 4 ________________________________________________ 5-97
Example 5 ________________________________________________ 5-97
VERIFY DISTANCE ______________________________________________ 5-104

Description______________________________________________ 5-104
Valid Modes ____________________________________________ 5-104
Syntax __________________________________________________ 5-104
Modifiers ________________________________________________ 5-104
Procedure ______________________________________________ 5-105
Contents-xviii Piping Reference

Example 1_______________________________________________ 5-105
Example 2_______________________________________________ 5-107
Example 3_______________________________________________ 5-108
Piping Files
Modeling, Detailing, and Reporting Files __________________________ A-2
Piping RDBMS Tables

RDBMS Environment Variables Setup _____________________________ B-2
Linking CADDS Parts to a Project _________________________________ B-3
Project Information Tables _______________________________________ B-4

AEC Project Dictionary Table __________________________________ B-4
Script Files _________________________________________________ B-6
Syntax ____________________________________________________ B-6
Example __________________________________________________ B-7
AEC Project Component Table ________________________________ B-7
Script Files _________________________________________________ B-9
Syntax ____________________________________________________ B-9
Example __________________________________________________ B-9
AEC Application Object Type Table ___________________________ B-9
Script Files ________________________________________________ B-11
Syntax ___________________________________________________ B-11
Example _________________________________________________ B-12
AEC Application Object Dictionary Table _____________________ B-12
Script Files ________________________________________________ B-13
Syntax ___________________________________________________ B-14
Example _________________________________________________ B-14
AEC Object Table ___________________________________________ B-14
Script Files ________________________________________________ B-15
Syntax ___________________________________________________ B-15
Example _________________________________________________ B-16
AEC Measurement Unit Dictionary Table ___________________ B-16
Script Files ________________________________________________ B-17
Syntax ___________________________________________________ B-17
Example _________________________________________________ B-18
Piping Reference Contents-xix

AEC Measurement Unit Name Dictionary Table ____________ B-18
Script Files________________________________________________ B-19
Syntax ___________________________________________________ B-19
Example _________________________________________________ B-19
AEC Measurement Unit Conversion Table __________________ B-20
Script File ________________________________________________ B-20
Syntax ___________________________________________________ B-21
Example _________________________________________________ B-21
AEC Application Object Relation Type Table _______________ B-21
AEC Object LINK Relationship Table _______________________ B-21
Piping Standard Library RDBMS Tables ___________________________ B-23

Piping Coordinate Table _____________________________________ B-23
Script File ________________________________________________ B-23
Data files ________________________________________________ B-24
Syntax ___________________________________________________ B-24
Example _________________________________________________ B-24
Piping Drawing Information Table ____________________________ B-25
Script File ________________________________________________ B-25
Data files ________________________________________________ B-25
Syntax ___________________________________________________ B-26
Example _________________________________________________ B-26
Pipeline Information Table ___________________________________ B-26
Script File ________________________________________________ B-27
Data files ________________________________________________ B-27
Syntax ___________________________________________________ B-28
Example _________________________________________________ B-28
Pipe Specification Table _____________________________________ B-29
Script File ________________________________________________ B-29
Data files ________________________________________________ B-29
Syntax ___________________________________________________ B-30
Example _________________________________________________ B-30
Pipe Fabrication Material Table ______________________________ B-30
Script File ________________________________________________ B-31
Data files ________________________________________________ B-31
Syntax ___________________________________________________ B-32
Example _________________________________________________ B-32
Pipeline RDBMS Tables _________________________________________ B-33

Pipeline List Table ___________________________________________ B-33
Contents-xx Piping Reference

Syntax ___________________________________________________ B-34
Example _________________________________________________ B-34
Pipeline Element Table_______________________________________ B-34
Script Files ________________________________________________ B-36
Syntax ___________________________________________________ B-36
Example _________________________________________________ B-36
Pipeline Bend Table _________________________________________ B-37
Script File ________________________________________________ B-37
Syntax ___________________________________________________ B-38
Example _________________________________________________ B-38
Pipeline Item Number Information Table ______________________ B-38
Script File ________________________________________________ B-38
Syntax ___________________________________________________ B-39
Example _________________________________________________ B-39
Pipeline End Type Table______________________________________ B-40
Script File ________________________________________________ B-40
Syntax ___________________________________________________ B-40
Example _________________________________________________ B-41
Generating Project Information and Piping Tables________________ B-42

Top Level Script Files ______________________________________ B-42
Granting Permissions to More Users ________________________ B-44
Syntax ___________________________________________________ B-44
Example _________________________________________________ B-44
Spool Fabrication Drawing

Form Part
Creating a Sample Form Part ____________________________________ C-2
Parts in the Fitting Library (CVPD.F)

Introduction ____________________________________________________ D-2
Components ____________________________________________________ D-3
Component Properties __________________________________________ D-7
Piping Reference Contents-xxi

Library Parts (1 to 21)
Introduction _____________________________________________________ E-2
Library Parts (1 to 3) ______________________________________________ E-3

ANGV (ANGLE VALVE - FLANGED) ___________________________ E-3
BALV (BALL VALVE - FLANGED) ______________________________ E-3
BLFF (BLIND FLANGE - FLAT FACE) ____________________________ E-3

BLGR (BLIND FLANGE - GROOVED)___________________________ E-4
BLRF (BLIND FLANGE - RAISED FACE) _________________________ E-4
BLRJ (BLIND FLANGE - RING JOINT) ___________________________ E-4

BLTF (BLIND FLANGE - TONGUE) ______________________________ E-5
BRFS (BRANCH BY FULL COUPLING - SCREWED) _______________ E-5
BRFW (BRANCH BY FULL COUPLING - SOCKET WELD) __________ E-5
Library Parts (10 to 12) ____________________________________________ E-6

BRHS (BRANCH BY HALF COUPLING - SCREWED) ______________ E-6
BRHW (BRANCH BY HALF COUPLING - SOCKET WELD) _________ E-6
BTFY (BUTTERFLY VALVE) _____________________________________ E-6

BVBW (BALL VALVE - BUTT WELD)_____________________________ E-7
BVSC (BALL VALVE - SCREWED) ______________________________ E-7
BVSW (BALL VALVE - SOCKET WELD) _________________________ E-7

CAPP (CAPP - BUTT WELD)___________________________________ E-8
CASC (CAPP - SCREWED) ___________________________________ E-8
CASW (CAPP - SOCKET WELD) _______________________________ E-8

CHBW (CHECK VALVE - BUTT WELD) __________________________ E-9
CHKV (CHECK VALVE - FLANGED) ___________________________ E-9
CHKW CHECK VALVE _______________________________________ E-9

Introduction _____________________________________________________ F-2
Contents-xxii Piping Reference

Library Parts (22 to 24) ____________________________________________ F-3
CHSC (CHECK VALVE SCREWED) __________________________ F-3
CHSW (CHECK VALVE SOCKET WELD)______________________ F-3
CPFS (FULL COUPLING SCREWED) _________________________ F-3

CPFW (FULL COUPLING SOCKET WELD) ____________________ F-4
CPHS (HALF COUPLING SCREWED) ________________________ F-4
CPHW (HALF COUPLING SOCKET WELD) ___________________ F-4

CPRS (REDUCING COUPLING SCREWED) ___________________ F-5
CPRW (REDUCING COUPLING SOCKET WELD) ______________ F-5
CRED (CONCENTRIC REDUCER BUTT WELD) ________________ F-5

CROS (CROSS BUTT WELD) ________________________________ F-6
CRSC (CROSS SCREWED) _________________________________ F-6
CRSW (CROSS SOCKET WELD) _____________________________ F-6

CTRV (CONTROL VALVE FLANGED) ________________________ F-7
ELR3 (ELBOW 30 DEGREE LONG RADIUS BUTT WELD) ________ F-7

ELR4.TRIM (TRIMMED 45 DEGREE ELBOW) _____________________ F-8
ELR9.TRIM (TRIMMED 90 DEGREE BUTT WELD) _______________ F-9
ELT4 (TANGENT ELBOW 45 DEGREE
LONG RADIUS BUTT WELD) ________________________________ F-9
LONG RADIUS BUTT WELD) ________________________________ F-9
Library Parts (43 to 45) ___________________________________________ F-10

ERED (ECCENTRIC REDUCER BUTT WELD) __________________ F-10
ESC4 (ELBOW 45 DEGREE SCREWED)______________________ F-10
ESC9 (ELBOW 90 DEGREE SCREWED)______________________ F-10
Library Parts (46 to 48) ___________________________________________ F-11
Piping Reference Contents-xxiii

ESR9 (ELBOW 90 DEGREE SHORT RADIUS BUTT WELD) _______ F-11
ESW4 (ELBOW 45 DEGREE SOCKET WELD) _________________ F-11
ESW9 (ELBOW 90 DEGREE SOCKET WELD) _________________ F-11

Introduction ____________________________________________________ G-2
Library Parts (49 to 51) ___________________________________________ G-3

E5R9 (5 DIAMETER BEND 90 DEGREE) ________________________ G-3
E5R9.TRIM (5 DIAMETER BEND 90 DEGREE TRIMMED) __________ G-3
E518 (5 DIAMETER 180 DEGREE) _____________________________ G-3

GASK (GASKET) ____________________________________________ G-4
GATV (GATE VALVE FLANGED) ___________________________ G-4
GLBV (GLOBE VALVE FLANGED)__________________________ G-4

GLBW (GLOBE VALVE BUTT WELD) ________________________ G-5
GLSC (GLOBE VALVE SCREWED) _________________________ G-5
GLSW (GLOBE VALVE SOCKET WELD) _____________________ G-5

GVBW (GATE VALVE BUTT WELD) _________________________ G-6
GVSC (GATE VALVE SCREWED) __________________________ G-6
GVSW (GATE VALVE SOCKET WELD) ______________________ G-6

LFLB (LAP FACE FLANGE, TYPE B) ____________________________ G-7
LFLG (LAP FACE FLANGE, TYPE G) ___________________________ G-7
LFLV (LAP FACE FLANGE SHORT STUB END)___________________ G-7

LT18 (LONG TANGENT 180 DEGREE ELBOW) __________________ G-8
NEDV (NEEDLE VALVE FLANGED) _________________________ G-8
NIPL (PIPE NIPPLE VARYING END TYPES) ___________________ G-8

Introduction ____________________________________________________ H-2
Contents-xxiv Piping Reference

Library Parts (67 to 69) ___________________________________________ H-3
NLET (BRANCH NIPPLE NIPOLET) __________________________ H-3
PLBW (PLUG VALVE BUTT WELD) __________________________ H-3
PLGV (PLUG VALVE FLANGED) ___________________________ H-3

PLHX (HEXAGON HEAD PLUG SCREWED) __________________ H-4
PLRH (ROUND HEAD PLUG SCREWED)_____________________ H-4
PLSC (PLUG VALVE SCREWED) ___________________________ H-4

PLSQ (SQUARE HEAD PLUG SCREWED) ____________________ H-5
PLSW (PLUG VALVE SOCKET WELD) _______________________ H-5
REL9 (REDUCING ELBOW 90 DEGREE BUTT WELD) __________ H-5

RELV (RELIEF VALVE) _______________________________________ H-6
RTEE (REDUCING TEE BUTT WELD) _________________________ H-6
RTSC (REDUCING TEE SCREWED) _________________________ H-6

RTSW (REDUCING TEE SOCKET WELD) _____________________ H-7
SELT (SOCKET WELDED ELBOWLET)___________________________ H-7
SLET (SOCKOLET)___________________________________________ H-7

Introduction _____________________________________________________ I-2
Library Parts (82 to 84) ____________________________________________ I-3

SOFF (SLIP-ON FLANGE FLAT FACE) ________________________ I-3
SORF (SLIP-ON FLANGE RAISED FACE) _____________________ I-3
SORJ (SLIP-ON FLANGE RING JOINT) _______________________ I-3

STEE (STRAIGHT TEE BUTT WELD) ____________________________ I-4
STRN (STRAINER) ____________________________________________ I-4
STSC (STRAIGHT TEE SCREWED) ____________________________ I-4

SWFF (SOCKET WELD FLANGE FLAT FACE) __________________ I-5
SWRF (SOCKET WELD FLANGE RAISED FACE) _______________ I-5
Piping Reference Contents-xxv

TELT (THREADED ELBOWLET) _________________________________ I-5

THFF (THREADED FLANGE FLAT FACE) ______________________ I-6
THRF (THREADED FLANGE - RAISED FACE) _____________________ I-6
TLET (THREDOLET) ___________________________________________ I-6

TRAP (TRAP) ________________________________________________ I-7
UNSC (UNION SCREWED) _________________________________ I-7
UNSW (UNION SOCKET WELD) _____________________________ I-7

Introduction _____________________________________________________ J-2
Library Parts (97 to 99) ____________________________________________ J-3

WELT (WELDED ELBOWLET)___________________________________ J-3
WLET (WELDOLET) ___________________________________________ J-3
WNFE (WELD NECK FEMALE END FLANGE) ____________________ J-3
Library Parts (100 to 102) __________________________________________ J-4

WNFF (WELD NECK FLANGE FLAT FACE)____________________ J-4
WNFR (WELD NECK FEMALE END FLANGE, TYPE R) _____________ J-4
WNGR (WELD NECK FLANGE GROOVED) __________________ J-4

WNME (WELD NECK MALE END FLANGE) _____________________ J-5
WNMJ (WELD NECK MALE END JOINT FLANGE) _______________ J-5
WNMV (WELD NECK MALE END FLANGE, TYPE V)______________ J-5
WNRF (WELD NECK FLANGE RAISED FACE) _________________ J-6
WNLJ (WELD NECK LAP JOINT FLANGE) ______________________ J-6
WNRJ (WELD NECK FLANGE RING JOINT) __________________ J-6
WNTF (WELD NECK FLANGE TONGUE)______________________ J-7
Contents-xxvi Piping Reference

Preface
The Piping Reference describes commands developed exclusively for Piping

Specification Generation, Pipe line Construction, Pipe line Modeling, Isometric
Generation, and Pipe line Detailing products. It assumes that you are familiar with
Explicit Modeling commands, as well as piping engineering and design.
Related Documents
The following documents may be helpful as you use Piping Reference:
Piping Specification User Guide

Explains the creation and modification of part libraries needed to support
specifications for piping design.
Isometric Drawing User Guide
This guide presents a basic approach to the production of isometric drawings for
either fabrication or stress analysis.
Reports and Analysis Reference
Describes commands developed exclusively for the Pipe line Reporting, Project
Linkage, and Interference Checking products.
Intelligent PID Managers Guide
Describes the procedures for creating intelligent Piping and Instrumentation
Diagrams (P&IDs).
Visualization/Preparation Reference
Describes AEC visualization commands. It also provides information and
instruction on using procedure files and aectypes.
Piping Reference xxvii

Preface
Book Conventions
The following table illustrates and explains conventions used in writing about
CADDS applications.
Convention Example Explanation

Menu selections and options List Section option, Specify Layer Indicates a selection you must make from a
field menu or property sheet or a text field that you
must fill in.
User-selected graphic X , d1 or P1 Marks a location or entity selection in graphic
location examples.
User input in CADDS text cvaec.hd.data.param Enter the text in a CADDS text field or on any
fields and on any command command line.
line tar -xvf /dev/rst0
System output Binary transfer complete. Indicates system responses in the CADDS text
window or on any command line.
Variable in user input tar -cvf /dev/rst0 filename Replace the variable with an appropriate
substitute; for example, replace filename with an
actual file name.
Variable in text tagname Indicates a variable that requires an appropriate
substitute when used in a real operation; for
example, replace tagname with an actual tag
name.
CADDS commands and INSERT LINE TANTO Shows CADDS commands and modifiers as
modifiers they appear in the command line interface.
Text string "SRFGROUPA" or SRFGROUPA Shows text strings. You must enclose text string
with single or double quotation marks.
Integer n Supply an integer for the n.
Real number x Supply a real number for the x.
# # mkdir /cdrom Indicates the root (superuser) prompt on

command lines.
% % rlogin remote_system_name Indicates the C shell prompt on command lines.
-l root
$ $ rlogin remote_system_name -l Indicates the Bourne shell prompt on command
root lines.
Window Managers and the User Interface

According to the window manager that you use, the look and feel of the user
interface in CADDS can change. Refer to the following table:
Look and Feel of User Interface Elements
User Interface Common Desktop Environment (CDE) Window Manager Other Than CDE on
Element on Solaris and HP Solaris, HP, and Windows
Option button ON Round, filled in the center ON Diamond, filled
OFF Round, empty OFF Diamond, empty
xxviii Piping Reference

Preface
Look and Feel of User Interface Elements
User Interface Common Desktop Environment (CDE) Window Manager Other Than CDE on
Element on Solaris and HP Solaris, HP, and Windows
Toggle key ON Square with a check mark ON Square, filled
OFF Square, empty OFF Square, empty
Online User Documentation

Online documentation for each book is provided in HTML if the documentation
CD-ROM is installed. You can view the online documentation in the following
ways:
From an HTML browser

From the Information Access button on the CADDS desktop or the Local Data
Manager (LDM)
Please note: The LDM is valid only for standalone CADDS.
You can also view the online documentation directly from the CD-ROM without
installing it.
From an HTML Browser:
1. Navigate to the directory where the documents are installed. For example,
/usr/apl/cadds/data/html/htmldoc/ (UNIX)
Drive:\usr\apl\cadds\data\html\htmldoc\ (Windows)
2. Click mainmenu.html. A list of available CADDS documentation appears.
3. Click the book title you want to view.
From the Information Access Button on the CADDS Desktop or LDM:

1. Start CADDS.
2. Choose Information Access, the i button, in the top-left corner of the CADDS
desktop or the LDM.
3. Choose DOCUMENTATION. A list of available CADDS documentation appears.
4. Click the book title you want to view.
Piping Reference xxix

Preface
From the Documentation CD-ROM:
1. Mount the documentation CD-ROM.

2. Point your browser to:
CDROM_mount_point/htmldoc/mainmenu.html (UNIX)
CDROM_Drive:\htmldoc\mainmenu.html (Windows)
Online Command Help

You can view the online command help directly from the CADDS desktop in the
following ways:
From the Information Access button on the CADDS desktop or the LDM
From the command line
From the Information Access Button on the CADDS Desktop or LDM:
1. Start CADDS.
2. Choose Information Access, the i button, in the top-left corner of the CADDS
desktop or the LDM.
3. Choose COMMAND HELP. The Command Help property sheet opens
displaying a list of verb-noun combinations of commands.
From the Command Line: Type the exclamation mark (!) to display online
documentation before typing the verb-noun combination as follows:
#01#!INSERT LINE
Printing Documentation
A PDF (Portable Document Format) file is included on the CD-ROM for each
online book. See the first page of each online book for the document number
referenced in the PDF file name. Check with your system administrator if you
need more information.
You must have Acrobat Reader installed to view and print PDF files.
The default documentation directories are:
/usr/apl/cadds/data/html/pdf/doc_number.pdf (UNIX)
CDROM_Drive:\usr\apl\cadds\data\html\pdf\doc_number.pdf
(Windows)
xxx Piping Reference

Preface
Resources and Services

For resources and services to help you with PTC (Parametric Technology
Corporation) software products, see the PTC Customer Service Guide. It includes
instructions for using the World Wide Web or fax transmissions for customer
support.
Documentation Comments
PTC welcomes your suggestions and comments. You can send feedback
electronically to doc-webhelp@ptc.com.
Piping Reference xxxi

Chapter 1 Piping Design Overview
This chapter provides an overview of the piping functions. It describes operations

that are performed on piping design models.
It provides an overview of the following:
Piping Design Features

Pipe Reporting
Properties and Part Properties
Properties and Part Properties Library
Suggested Layering Conventions
Support Files
Designing a Pipeline
Constructing Equipment
Piping and Instrumentation Diagrams (P&IDs)
Defining Projects
Producing Drawings
Generating Piping Reports
Piping Reference 1-1


Explicit modeling piping design software gives you the ability to
Generate piping specification files

Construct, model, and detail pipelines and equipment
Produce isometric drawings for piping engineering and design
Generate piping and instrumentation diagrams and reports
Extract useful information for other analysis programs
Piping design models are primarily built using Cnodes (connect nodes), Tnodes
(text nodes), Nlines (nodal lines), and Nfigures (nodal figures) as well as basic
text. They can also have associated nongraphic information or properties. You
have direct access to the basic entities through the system commands.
The software automatically associates properties, or nongraphic information, with

the various elements of the pipeline. As you produce models and drawings, you
can check for accuracy in modeling and store, integrate, and report information
about piping models and projects.
Generating Piping Specification Files

Use the GENERATE PSFILE command and the master catalog files to
automatically generate piping specification (autoselection) and parameter files.
Master catalogs for the following standards are included in the Piping Design
product:
ANSI for the commonly used (ANSI) standard piping components and a
selected range of manufacturers pipes and fittings.
DIN/ISO for the commonly used metric (DIN/ISO) standard pipes and fittings.
Use these files to automatically insert, detail, and check interference of fittings.
You can also reference either single or multiple specification selection files, as
well as multiple parameter files to be used for components on different layers.
1-2 Piping Reference

Constructing, Modeling, and Detailing Pipelines

Constructing, modeling, and detailing pipelines is made easier and quicker by the
use of features such as
Pipeline routing
Route pipelines with a slope or an offset, label them, and align them to the
model axis, using the command ROUTE PIPE.
You can move already modeled pipelines using the command OFFSET
PIPELINE.
Automatic fitting insertion
You can insert single fittings, groups of fittings, and assemblies into pipelines or
into other fittings (such as taps). Automatically supply flanges and gaskets to
fittings to maintain joint integrity; insert 90-degree elbows at every corner of
specified pipelines; insert single- and double-reducing fittings; check for end
type and size consistency; parametrically scale specially prepared branch or
corner fittings with unequal leg lengths, using the commands
INSERT FITTING
INSERT BEND
MODIFY PLINE
Delete fittings, pipelines, or bends, using the commands
DELETE FITTING
DELETE PLINE
DELETE BEND
MODIFY PLINE
Precision formatting
You can model your piping system in either single- or double- precision part
format. However, all the elements of your system must be in the same format.
You cannot insert fittings or assemblies of one format into a part of another
format.
To maintain order, create separate libraries for your single and double precision
parts. Put each library into a separate CVPATH so it can be easily discriminated.
See Managing CADDS 5 for more information.
Design rules checking
You can check the following while modeling or reporting pipelines:
End type compatibility of adjacent fittings
Consistency of flow direction within the pipeline

Minimum spool length

Maximum spool length
Maximum number of bends in a spool
Agreement of size and specification from the pipelines label with
properties on the pipeline
Agreement of pipeline size with nozzle size
Existence of suitable fittings at corners
Size and end type compatibility at nozzles
Layering
Each type of piping component is assigned to a range of layers (such as nozzles
on layers 1-29), which in turn is associated with a parameter file (for example,
cvpd/nozl/parameters is located in the default directory file
cvpd/directories or cvpd/plant/directories).
Default parameters
You can establish default values for design conditions, using the command
SELECT PPARAMETERS.
Automatic detailing
Use Explicit Modeling visualization features to draw your pipeline.
Change the appearance of pipelines by producing, and/or deleting, double- and
single-line drawings, using the commands
CREATE DETAIL
DELETE DETAIL
Produce graphic surfaces, using the command CREATE SURFACE.
For complete information about CREATE DETAIL, DELETE DETAIL, and
CREATE SURFACE, see the Visualization/Preparation Reference.
Edit drawings more efficiently by removing clutter, using the commands
HIDE PIPE
UNHIDE PIPE
which are fully described in the Appearance and Hidden Line Removal
Reference.
Annotation
Interactively insert northings, eastings, and elevations with an extended witness
line, using the command INSERT DATUM.
Annotate pipelines with text labels whose size and specification you obtain
automatically from the pipeline, using the command INSERT PLABEL
(INSERT PIPELINE LABEL).

Add reports such as bills of materials to drawings, using the command INSERT
TFILE (INSERT TEXT FILE).
For more information about this command, see the online command reference
documentation.
Producing Isometric Drawings

This piping generation package automates the production of isometric drawings.
The Isometric Drawing User Guide gives step-by-step instructions for creating
isometric drawings.
The isometric drawing commands described in this book can be categorized into
two sets: Series A and Series B.
Series A
The Series A commands, described below, provide a full range of versatility for
isometric drawing. The commands are:
ANNOTATE ISOMETRIC
Annotates and dimensions isometrics in addition to those provided by CREATE
ISOMETRIC.
CREATE ISOMETRIC
Generates piping isometric drawings without dimensions, but with modifiers
that allow scaling operations.
SAVE ANNOTATIONS
Saves information relating to a series of pipelines for later use with the
ANNOTATE ISOMETRIC command.
TRANSLATE ISOMETRIC
Revises the dimensions and locations of Cnode and Nfigures on a piping
isometric drawing without altering the drawing graphics.

The Series A commands can produce isometrics that take advantage of a number
of additional commands that make minor but important modifications of piping
models. These commands generally provide information that is useful in modeling
(pipe supports can have associated procedure files that are useful in detailing and
interference checking), bill of materials production (REPORT PIPE), and in
isometric production (symbol annotation and dimensions are produced).The
commands are:
INDICATE PENETRATION
Associates a penetration symbol with the point on a pipeline that penetrates a
wall or floor. You can use the DELETE PENETRATION command to remove
penetration symbols from the isometric drawing.
INSERT PSUPPORT
Associates a pipe support symbol with the point on the pipeline. You can use
the DELETE PSUPPORT command to delete pipe support symbols from the
pipeline.
REFERENCE STRUCTURE
Associates the location and orientation of a structural member with a pipe or
fitting.
SPLIT PIPE
Provides easy insertion of field weld positions in the model.
GENERATE SPOOL
Provides the ability to introduce spool break points in the model or in the
extracted model (via CONSTRUCT PLINE) for isometric generation purposes.
Series B
Series B commands are provided for those who do not yet need the full range of
capability and want to make the transition gradually. The Series B commands are:
DIMENSION ISOMETRIC
Automatically dimensions piping isometric drawings.
GENERATE ISOMETRIC
Generates piping isometric drawings, without dimensions, from a scaled
three-dimensional model of a pipeline or piping network.
SAVE DIMENSIONS
Saves the dimensioning related to an isometric drawing.

Generating Piping and Instrumentation Reports

You can use the following piping features when checking and reporting
Bolting
You can include bolting in the specification files you automatically generate.
When you insert wafer fittings, or fittings that require gaskets, the bolting
information in the specification file is automatically referenced and can be
reported with the REPORT PIPE command.
Material description
You can create a material description file for pipeline components with the
GENERATE MDF command.
Pipeline reporting
Generate line lists, material estimation summaries, and instrument lists with the
REPORT PIPE command. The features of this command are more thoroughly
described in the command section of this manual.
Text file manipulation
Restructure reports, and total and tally report information, using the Explicit
Modeling commands
REARRANGE TALLY
TALLY FILE
TOTAL FILE
For more information about these commands, see the Data Extract/Data
Merge Reference.
The following features, which must be purchased separately, are also extremely
useful for checking and reporting:
Project development and reporting

Integrate the data common to a project and combine part intelligence to form a
single model, by using the commands
DEFINE LINKAGE
LINK PROJECT
Relate and compare arrangement, Piping and Instrumentation Diagrams,
isometric and spool drawings, using the command CHECK PROJECT.
Report, in their entirety, pipelines that cross part boundaries. Also, look up
stock numbers in the specification file at the time you link piping components
into the project, using the command REPORT PROJECT.

For more information about this command, see the Reports and Analyses
Reference.
Interference checking
Check for interference between selected piping components, using the
command CHECK INTERFERENCE.
For more information about this command, see the Reports and Analyses
Reference.
Equipment construction
Interactively construct pieces of equipment, and automatically generate the
procedure files needed for detailing and interference checking, using the
commands
CONSTRUCT EQUIPMENT
PREPARE EQUIPMENT
Reflect changes made to the equipment library in your piping models, using the
command UPDATE EQUIPMENT.
For more information about this command, see Visualization/Preparation
Reference.
Extracting Useful Information for Analyses Programs

Explicit Modeling must sometimes provide data to interface with piping analyses
programs.
The EXTRACT PIPE command reports data for piping systems in a neutral form
that can be used by piping stress-analyses programs. For more information, see the
Stress Analysis Interface Reference.

Pipe Reporting
Pipe Reporting
The REPORT PIPE command interprets piping networks and generates a great
variety of report data.
Interpreting Piping Networks

REPORT PIPE interprets piping networks as follows:
Pipelines
Cnodes with the TERMNAM property define boundaries between pipelines
(beyond which consistency checking does not go) even if they are not labeled.
Each unique pipeline label defines a pipeline.
The flow direction of the series is determined by the direction of the first and
last Nlines in the series.
You can repeat the same label within a pipeline to define the path of a main
extension through an ambiguous branch point.
Pipelines can have multiple sources and destinations defined by the sources and
destinations of their main extensions (except those internal to the pipeline
itself); branches are not included. Multiple sources and destinations are listed in
the overall pipeline information at the top of the report. There is no
correspondence between these sources and destinations (for example, the first
source listed does not necessarily go with the first destination).
Branches and main extensions
A main extension (ME) ends at a branch point that has more than one main exit.
A main extension continues through a branch with only one main exit.
Branches begin at branch exits and do not continue through branch points.
A Cnode can connect only two Nlines in a series.
Size and spec definition
Size and spec must be available at every point in a pipeline (implied unless
changed).
Although the pipeline size and spec may be initially defined by the pipeline
label, pipeline labels do not change size or spec.
Definitions change at components with LPROP (in P&IDs), or NPS and SPEC
properties (in 3D models). If LPROP is not found, NPS and SPEC are used (the
normal case in 3D models).

Pipe Reporting
Generating Report Data

The defaults for generating reports vary, depending on whether they are for P&IDs
(Piping and Instrumentation Diagrams), or for three-dimensional models and
Isometrics.
You can perform the following functions to produce report data:
Generate line lists and material estimation summaries.

List the instrument reports for P&IDs.
Sort and tally unique components in a bill of materials report and then write the
report into a specified text file.
Selectively include material descriptions for different types of items, such as
bolts, fittings, assemblies, flanges, valves, and so on.
Turn on and off messages that pinpoint problems in a 3D model.
Report diameter and length data in different units and formats.
Generate a diagnostic report showing the structure of a pipeline.
Report multiple pipeline sources and destinations.
Add labels and other information, taken from Tnodes (text nodes) and Ntext
(nodal text) on pipes, to the material descriptions for pipes and components.
Look up component stock numbers in the autoselection files rather than from
the STOCKNO property on the entity.
For a complete description see the REPORT PIPE command, in Chapter 5,

Piping Commands - Part 4..


Properties attach nongraphic information to Explicit Modeling parts and to the
entities that make up the part. Properties serve as a tag or label to identify various
types of information. Because they are nongraphic, properties do not lie on a layer
and are not visible on the screen. When a part is entered into a library, the property
becomes a part property.
Part Properties
Part properties are properties that are associated with library parts. When the
library part is used as a figure in modeling, the part property then becomes a
property on the Nfigure entity.
Property Libraries
Most of the important properties are built into the piping design libraries or are
automatically inserted by piping design commands. Properties serve the following
functions:
Logical functions. In the construction and maintenance of pipelines, properties

influence insertion, tracing, and reporting operations.
Classify entities. For example, an Nline with a GASKET property is a gasket.
Describe attributes of an entity. For example, the OUTERDIAM property
describes the outer diameter of pipe.
Link entities to external nongraphical descriptions. For example, the
STOCKNO on a fitting ties it to data in a parameter file. The PLIST property
links entities to the parameters needed to simulate their solid three-dimensional
appearance.
Use of the property conventions is essential to building functional piping systems.

You can also define conventions and use properties to store and extract any data
you want to associate with different components.
Creating Properties
Piping properties generally are created and maintained automatically and do not
require manipulation, with these exceptions:
Dimension properties (XYZ and LENGTH) created by the SAVE

DIMENSIONS and SAVE ANNOTATION command are not automatically
updated when you change your model.

Properties expressed in database units require careful attention. If you insert

entities from one part into another part with different database units, the
properties are not automatically updated. For example, when you route a pipe,
the property INNERDIAM is automatically inserted. The property stores the
inner diameter of the pipe. If that diameter is in inches and you insert the pipe
(as part of a part figure) into another part modeled in meters, the diameter is
interpreted as meters.
When you create library parts, you must insert part properties. For example, the
STOCKNO property gives the components stock number.
When a part is prepared as a figure, the part properties become associated with
the figure entity. A subfigure, for example a gate valve, can be inserted
repeatedly into piping design databases. However, the properties need only to
be associated with that subfigure once and are then inserted as part of the
subfigure. They then exist in all instances of that part as a figure.
Properties reference or store information by means of the values that they are
automatically assigned or, in some instances, assigned by you. The type of
properties used and the values associated with them depend on their intended
function.


To obtain a complete list of Explicit Modeling properties, use the LIST PROP ALL
command. The text file /usr/apl/cadds/data/_bcd/prop contains all legal
properties recognized by the system, and can be modified by the administrator.
There are four types of properties:
Null-valued: Type 0 needs no value.

Integer-valued: Type 1 requires an integer (number without a decimal point).
Real-valued: Type 2 requires a real value (number with a decimal point).
Text-valued: Type 3 requires delimited text.
The table below lists the properties and part properties according to their types.
Table 1-1 Types of Properties and Part Properties
Type 0 Type 1 Type 2 Type 3

Null Valued Integer Valued Real Valued Text Valued
BRANCH FITTYPE BRAD ABOVE
CONNECTOR INSLOC INNERDIAM ATTACHMENT
CUTSPOOL LPROP INSULATION AUTOANN
EFFTXT PARTTYPE OUTERDIAM COMPNAME
GASKET PLEN PERMAPP ENDTYPE
INSTR PSCL PLIST EQUIP
INTERNAL SHAPECODE TRIM LASTLINK
ITEMNO SHAPETYPE XYZ LENGTH
NOBREAK TITLETNOD NPS
NOSEL PNAME
OPC PROJNAME
SINGLE SNAME
SKEW SPEC
SPECIAL STOCKNO
SPOOLIST TERMNAM
TAP
TEMPNLIN
WELD
WELDTABL
The Piping design properties and part properties listed in the table above are
defined on the following pages.

ABOVE
A text-valued property that gives the nominal pipe size above which double-line
detail graphics are created.
ATTACHMENT
A text-valued property indicating that the parent fitting is the origin of a line
attachment assembly. The text value is the name of the line attachment.
AUTOANN
A text-valued property used for Piping & Instrumentation Diagram. It is used by
Data Extract in making instrument reports. The functional identification code
comes from the Tnode with the value TYPE and the loop number comes from the
Tnode with the value NUMBER.
BRAD (Bend Radius)

A real-valued property with three separate values. The first value is the bend
radius in database units. The second value is the tangent length, also in database
units. The final value is the MIPTR (Master Index Pointer) of the point entity
inserted at the bend vertex. The point can be used to aid the dimensioning process.
The MIPTR value is not automatically updated when you change the part database
with commands such as PACK DBASE or CHECK DBASE.
BRANCH
A null-valued property used to distinguish main extensions from branch lines at a
junction. For example, assume that a nodal line coming from a Cnode with three
or more nodal line connections has the BRANCH property. Then the pipe and
fittings connected to this line constitute a BRANCH instead of a main extension.
For the REPORT PIPE command, you must put the BRANCH property on the
Nline at the entrance or exit point to a branch in order to differentiate it from the
main entrance or exit.
REPORT PIPE does not report pipeline origins or destinations on branches.
For tees, crosses, and olets located in a library, BRANCH is assigned to the nodal
line that points along the y-axis. After inserting a branch fitting, you may delete
and reinsert the BRANCH property on another internal nodal line if you want a
different nodal line to be the branch. This is done automatically when tees are
inserted in Run-to-Branch (RTOB) or Branch-to-Run (BTOR) orientations.

COMPNAME (Component Name)

A text-valued property that stores the component name. The property provides the
name used by the CHECK INTERFERENCE and REPORT PIPE commands in
reports they generate. This name usually matches the last level of the entry in the
NAME field (nodal figure name) in the autoselection file.
CONNECTOR
A null-valued property assigned to only one connect node (Cnode) in a fitting. A
fitting must have at least one Cnode with the CONNECTOR property: otherwise,
REPORT PIPE omits the fitting from a component report. That Cnode must be on
the outside of the fitting and cannot be the center Cnode of a tee.
CUTSPOOL
A null-valued property on a Cnode which indicates a pipeline break point for
GENERATE SPOOL.
EFFTXT
A null-valued property that identifies instrument bubble Tnodes. It is used to
MARK the Tnodes and to center Ntext within the bubble. For more information,
see the Intelligent P&ID Managers Guide.
ENDTYPE
A text-valued property that stores the component face type. If not already present,
it is automatically inserted on component connect nodes by the INSERT FITTING
command, except when the STOCK option is on. It allows INSERT FITTING to
check for compatibility of end types of fittings against nozzles or adjacent fittings.
It is also used when automatic flange insertion is done by the INSERT FITTING
command. When a fitting with a flanged face is inserted next to one with a flanged
end type, an extra flange is not put between them.
You can define the end type properties and their compatibilities in an end type file
referenced by your directory file (see SELECT PPARAMETERS). However, there
are two restrictions. End types must be four characters or fewer; and all flanged
end types (and only flanged end types) must begin with the letter F (for example,
FLRF or F6RJ).
In the REPORT PIPE command, two adjacent Cnodes with ENDTYPE properties
that begin with the character F imply bolting. The bolting is looked up in the
autoselection file using the selected bolts name, and the size, specification, and end
type of the Cnodes.

EQUIP
This property is used by REPORT PIPE to get names from Tnodes belonging to
nodal figures. The first Tnode found with the EQUIP property or with no
properties is used to get Ntext.
FITTYPE (Fitting Type)

An integer-valued part property used by the piping design commands to
distinguish between different types of fittings, nozzles, structures, and equipment
items. In the REPORT PIPE command, the INCLUDE modifier relies on
FITTYPE to differentiate types of components. This part property is ignored if the
component has INSLOC. The codes for FITTYPE may be used on library parts
you create. For a description of these codes, see the Piping Specification User
Guide.
GASKET
A null-valued property, GASKET is located on the component nodal line to
identify that component as a gasket. Gaskets can be automatically inserted by the
INSERT FITTING command.
IGNORE
A property put on a Tnode you do not want used for naming equipment. It is used
specifically with the REPORT PIPE command for P&IDs. For more information,
see the Intelligent P&ID Managers Guide.
INNERDIAM (Inner Diameter)

A real-valued property that is automatically inserted by the command ROUTE
PIPE. It stores the true inner diameter of the pipe in database units. ROUTE PIPE
adds this property only when the part is identified as TYPE ARR with the
command SELECT PPARAMETERS.

INSLOC (Instrument Location)

An integer-valued part property that identifies an instrument and gives the location
(mounting) of an instrument on a P&ID.
Table 1-2 Instrument Location Properties
Value Location
0 Undetermined
1 - 10 Local mounted (sensing)
11 - 20 Behind local board
21 - 30 Behind the board
31 - 40 Local board mounted
41 - 50 Board mounted
51 - 60 Local mounted (controlling)
INSTR (Instrument Lines)

A null-valued property that identifies instrument lines in a P&ID. Lines identified
with this property are not reported as pipelines by the command REPORT PIPE.
INSULATION
A real-valued property that gives the thickness of insulation covering a component
or pipe in database units.
INTERNAL
A null-valued property that distinguishes between instream fittings and pipes when
assigned to nodal lines. Internal nodal lines (flowpaths) are included in fittings to
maintain flow through them. They are not included in calculations of cut lengths of
pipe, and their direction does not affect the direction of flow.
ITEMNO (Item Number)

A null-valued property, usually associated with valves. It is inserted on the text
node that is associated with the CONNECTOR Cnode. It can also be inserted on
nodal text related to pipes. With the LIST ITEM option on, REPORT PIPE reports
nodal text taken from the ITEMNO Tnode for components, and reports Ntext
marked by ITEMNO for pipes.
LASTLINK
A text-valued property used by the LINK PROJECT command to associate the
title block Tnode with the project name. The value of the property must match the

Ntext on the Tnode. If it does not, a warning message is displayed and you can
update the property by typing OK and entering a RETURN, or cancel the
command by only entering a RETURN.
LENGTH
A text-valued property similar to XYZ, except that it records the length of nodal
lines. It is created automatically by the SAVE ANNOTATIONS or SAVE
DIMENSIONS command. This property is not used by other commands, as XYZ
is, but it is useful in doing volume calculations.
LPROP (Line Property)

This property (used only in P&IDs) is put on both Cnodes of size and specification
break symbols to indicate a change in the size or specification of the pipeline. It
also indicates whether the two sizes are labeled with the same or with different
Ntext entities. This information is determined from its integer value.
Table 1-3 Line Properties
Value Change Description

0 Size One Ntext entity for both sizes. One Tnode shared by both Cnodes.
1 Size Separate Ntext for each size (unshared). Also use on a nozzle Cnode
with a related Tnode whose Ntext indicates the initial line size.
2 Specification Change in specifications.
NOBREAK
A null-valued part property assigned to branching fittings such as saddles,
weldolets, and sockolets that are inserted into pipelines so that pipe lengths are
correctly reported. The appropriate Nfigures in the CVPD library have been
prepared with this property.
NOSEL (No Selection)

When this null-valued part property is on a component, the LOOKUP modifier
does not use the autoselection file to find stock numbers. NOSEL overrides the
modifier LOOKUP in the REPORT PIPE and LINK PROJECT commands and
causes the stock number on the component to be used. This part property is very
useful for P&ID fittings.
NPS (Nominal Pipe Size)

A text-valued property used with three-dimensional models. The
INSERT FITTING command automatically updates the size value on all Cnodes

of reducing fittings when you use the modifiers NSIZE or BSIZE. NPS changes
line size at reducing components.
Pipeline construction rules require that every fitting that changes the line size have
the NPS property on every Cnode. Library parts have the property with a
temporary value of four periods. An exception to this are stubin branches, which
are not library parts. The NPS value of the branch pipeline is automatically added
to the cnode of the stubin when it is placed.
Each respective property should reflect the size of the adjacent pipe. For example,
a 6 inch 4 inch CRED has the NPS property with a value of 6 inches on the Cnode
adjacent to the 6-inch pipe and an NPS property with the value of 4 inches on the
Cnode adjacent to the 4-inch pipe.
OPC (Off-page Connector)

A null-valued property that project commands use to establish the connections for
data crossing more than one part. It must be on the Cnode at the end of a pipeline
that continues in another part. The MULTIPLE modifier with REPORT PIPE
combines the Ntext from OPCs and from the last link (or title block) Tnode. This
property is used by the LINK PROJECT command.
OUTERDIAM (Outer Diameter)

A real-valued property, analogous to the INNERDIAM property. OUTERDIAM is
automatically inserted by the ROUTE PIPE command when the part is identified
as TYPE ARR in the SELECT PPARAMETERS command.
The property stores the true outer diameter of the pipe. It is inserted in the same
manner as INNERDIAM. CREATE DETAIL uses this property to determine the
width of double-line graphics. CHECK INTERFERENCE also uses this property
to obtain the outer diameter of a pipe.
PARTTYPE
An integer-valued property that indicates the type of drawing.
Table 1-4 PARTTYPE Properties
Value Type of Drawing

0 Arrangement
1 Piping and instrumentation diagram
2 Isometric
3 Spool

The SELECT PPARAMETERS command assigns this property.
PERMAPP (Permanent Appearance)

A real-valued property inserted by the CREATE DETAIL command on the entities
defining a primitive shape. The property designates the permanently hidden
portions required to represent the shape itself. For example, the rectangular detail
string in a cylinder shape has the PERMAPP property to define its permanently
hidden end segments.
PLEN (Parametric Length)

An integer-valued property with two values (inserted with a space between them)
that indicates which parameters to use from a list (for example, a PLEN value of 5
2 points to the fifth and second parameters). Place PLEN on curved Nlines of
library parts that are to be scaled parametrically. The two values are used to get the
x- and y-coordinates of the outlet Cnode, relative to the inlet Cnode, in an
xy-plane.
PLIST (Parameter List)

A real-valued property that contains values for each variable in a components
procedure file. Insert it as a part property on the library part. Insert the library part
into the model and it becomes a property associated with the nodal figure. The
variables and PLIST entries must have a one-to-one correspondence. The variable
T1 should be listed first, T2 second, and so on, until all the variables in the
procedure have been assigned values.
PNAME (Procedure Name)

A text-valued property that stores the name of a components procedure file. You
can insert PNAME as a part property in each library component that requires
appearance graphics or interference checking. If the name of the procedure file is
the same as the name of the Nfigure, the procedure file is found automatically and
PNAME is not needed.
PROJNAME (Project Name)

A text-valued property that identifies a project and is used with project commands.
It is inserted as a part property on the library part. When the library part is inserted
into the model, it becomes a property associated with the Nfigure. This property is
used with LINK PROJECT and other project commands.

PSCL (Parametric Scale)

An integer-valued property used on library parts to be inserted parametrically.
Placed on the Cnodes of the part, its values indicate flow direction.
Table 1-5 Parametric Scale Properties
Value Flow Direction

1 On the inlet Cnode
2 On the outlet Cnode
3 On the branch outlet. If there is more than one branch,
only the one on the positive y -axis.
Placed on Nlines of the part, it points to a position in a list of parameters in the

Fitting Parameter File (for example, 5 points to the fifth parameter in the list). If
the Nline has more than one segment, the PSCL property has a value for each
segment, listed in the order of flow. The Nline is stretched by the value of PSCL.
Please note: This property has different uses on Nlines and Cnodes; the
values are totally independent even though the integers may be the same.
SHAPECODE
An integer-valued property that indicates the representational categories of shapes
created by the CONTRUCT EQUIPMENT command.
SHAPETYPE
An integer-valued property that indicates whether a shape created by
CONSTRUCT EQUIPMENT is a cylinder, cone, box, and so on.
SINGLE
A null-valued property automatically inserted on single-line detailing of pipes,
elbows, and bends.
SKEW
A null-valued property automatically placed by the INSERT FITTING command
on the first pipe Cnode downstream from an eccentric reducer if the pipe is
followed by a fitting or nozzle. REPORT PIPE reports the invalid pipe. The pipe is
automatically removed when the matching eccentric enlarger is inserted.

SNAME (Selection Name)

A text-valued property used for look-up by the reporting commands. The
component name you use with INSERT FITTING is assigned to the SNAME
property (if it is different than the value of the COMPNAME property).
SPEC (Specification)
A text-valued property used for three-dimensional models that stores a pipeline
specification code. It is inserted on both connect nodes of a component when the
NSPEC (new specification) modifier is used with the INSERT FITTING
command.
The upstream connect node indicates the old specification, and the downstream
connect node indicates the new specification in effect after (downstream from) the
fitting.
If the SPEC modifier is used to insert an out-of-spec fitting, the SPEC property is
inserted on the fitting nodal figure to indicate the specification it complies with.
SPECIAL
A null-valued property used to mark specially fabricated bends. With this
property, REPORT PIPE reports the bend as a separate piece of pipe (otherwise,
the bend and adjoining pipe are reported as one bent piece of pipe). This property
also causes CREATE DETAIL to put breaks at the transitions between the bend
and straight segments.
SPOOLIST
A null-valued property on a Tnode which specifies the location of the lower left
corner of the pipe spool legend table.
STOCKNO (Stock Number)

A text-valued property inserted as a part property on the library part. When the
library part is inserted into the model, it becomes a property associated with the
nodal figure. The INSERT FITTING command fills in the text during automatic
component selection.
The STOCKNO property is also inserted automatically on pipes by the ROUTE

PIPE command. In library components, a dummy STOCKNO part property (with
periods) speeds insertion by INSERT FITTING.

TAP
A null-valued property that indicates the fitting is nested within an inline
component. This causes the fitting to be treated as a branch point (for example,
elbowlet).
TEMPLIN (Temporary Line)

A null-valued property used to mark temporary Nlines left by the
DELETE FITTING command.
TERMNAM (Terminus Name)

A text-valued, optional property used at branch points to indicate the termination
(boundary) of a pipeline. This property is only needed by very complex systems
because REPORT PIPE recognizes pipeline boundaries by the presence of unique
pipeline labels. The text value can give the name of the pipeline owning the branch
point, or it can be blank.
If the text value is left blank, the label of the pipeline in which the branch point
occurs is used. TERMNAM breaks up networks of interconnected pipelines in
which some of the pipelines do not have labels.
TERMNAM limits the size of a network (the command can handle a maximum of
22 series per network), and defines boundaries for interference checking.
TITLENOD
An integer-valued property used with LINK PROJECT and other project
commands. It associates the text node with the title block. See the Reports and
Analyses Reference.
TRIM
A real-valued property used to identify a nodal figure as a trimmed elbow. The
value on the library part is the angle of the elbow from which the inserted elbow is
trimmed. The value on the nodal figure is updated to reflect the actual angle after
insertion.
WELD
A null-valued property used to identify a nodal line as a weld.

WELDTABL
A null-valued property on a Tnode which specifies the location of the lower right
corner of the weld table.
XYZ
A real-valued property that records the model space coordinates of points,
Cnodes, and Nfigures in database units. It is created or modified by the SAVE
DIMENSIONS or SAVE ANNOTATIONS command. INSERT LDIMENSION
uses the XYZ property to dimension nonscaled drawings with values from the
stored coordinates.


Layering is extremely useful in separating different types of components. It is also
useful for distinguishing piping design disciplines and for identifying the
parameter files used for detailing and interference checking.
The correspondence between layer ranges and parameter files is set up in your
directory file. The layering scheme shown in the following table is recommended.
It is compatible with the layering of fitting and structural parts. The colors can be
selected by running the execute file cvpd/m/x/ldis.
Table 1-6 Layering Convention for Piping Design
Layers Number-Color Purpose

0 03-White Drawing frame
1-29 26-Turquoise Equipment
30-59 15-Light pink Miscellaneous
60-69 30-Light gray Structural (footprint)
70-79 30-Light gray Structural (edges)
80-89 30-Light gray Structural (centerline)
90-99 31-Tan Foundations
100-109 32-Light cyan Piping - Group A
110-119 16-Bright pink Piping - Group B
120-129 09-Yellow Piping - Group C
130-159* TMP Fittings
160-250 03-White Miscellaneous
*Fittings
and their two-dimensional graphics are inserted on the same layers as the piping.
Three-dimensional (model) graphics are offset by 30 layers from the layer on which the fitting
is inserted. The colors of the offset layer ranges are set to match the colors of the corresponding
piping.

Support Files
Support Files
The previously described features are made possible by the piping commands (or
software) and supporting files that are part of the various piping products. A
complete list and brief description is included in Appendix A.
The file naming conventions presented here are used at Explicit Modeling level
only. Refer to the Explicit Modeling User Guide and Menu Reference for
information on file naming conventions used at the operating system level.
The following categories of files are included:
Library parts
Data files
Library Parts
A library part is a graphic representation (nodal figure) of a piping design element.
Library parts are provided for fittings (valves, flanges, elbows, and so on.),
nozzles, and support structures.
The libraries serve two main functions:
Provide a way to learn the software

Provide examples for constructing library parts that are compatible with the
software. The examples are the foundation on which you can build libraries for
your production needs.
The fitting library cvpd/f contains library parts for three-dimensional inline
piping.
Please note: Library figures are supplied in single precision format only. To
work in double-precision format, reformat all your libraries using the conv-lib
script described in Managing CADDS 5. Put your single- and double-precision
libraries in separate CVPATHs, so they can be easily discriminated.
Data Files
Data files are categorized as follows:
Master catalogs (MCATS)

Piping specification input files (INFILES)

Support Files
Piping specification (autoselection) files (ASFILES)

Directory files (DRFILES)
Parameter files (PAFILES)
Procedure files
Description files
Execute files
Routines
Master Catalogs (MCATS)

The master catalogs are a set of files that list standard or selected manufacturers
dimensions for a range of pipes and fittings; they also reference generic names and
library parts to use when inserting the fittings.
Piping Specification Input Files (INFILES)

Piping specification input files list your selection of standard components from the
master catalogs for a particular job; they are also the source of stock numbers for
components.
Piping Specification (Autoselection) Files (ASFILES)

Piping specification (autoselection) files based on an INFILE are generated by the
GENERATE PSFILE command. They contain your selection of standard
components from the master catalogs and make possible automatic selection and
insertion of these components. The files can be for single or multiple piping
specifications.
Several sets of autoselection files are provided. One is made from industry piping
specifications (A2A-D2B) and is important for training. Another provides a wider
selection of components, and is useful in learning how to use the autoselection
process. These specification files are only samples and are not intended for
production jobs.
You can also develop autoselection files for items such as nozzles and structures
(for an example, see cvpd/nozl/select). Create them using generic selection
names based upon some meaningful convention.

Support Files
Directory Files (DRFILES)

Directory files define the format of your pipeline label and specify the names of
the following kinds of files that provide information for various piping design
commands:
Specification catalogs, or multispecification files used for automatic selection
of components
Tables for checking the compatibility of fitting end types
Various parameter files assigned to layer ranges
Parameter Files (PAFILES)

Parameter files provide dimensional information used for detailing pipes and
components, modeling certain fittings, and checking interference. Use an execute
file such as cvpd/spec/cvm/_bcd/merge to sort the autoselection and
parameter files you create for fittings; then merge their parameter files into one.
Separate parameter files should exist for other types of components such as
nozzles and structures.
For efficiency, parametrically scaled fittings should also have separate parameter
files. These files should be designated as PFIT files in your DRFILE.
Procedure Files
Procedure files describe the three-dimensional geometry of fittings, duct fittings,
nozzles, vessels, and support structures. The geometry is presented in terms of
simple primitive shapes. The dimensions of the shapes can be defined from values
stored in a parameter file.
Description Files
Description files link components with additional information (such as material
type) not contained in the master catalogs, using the component stock numbers.
These files are not automatically generated; you create them as needed.
Execute Files
Execute files contain a sequence of commands that can be run repeatedly when
you issue a single command. They are provided to automate complicated
processes such as the generating, reformatting, and tallying of reports.

Support Files
Routines
CVMAC files are provided to facilitate such procedures as the placement of
fittings on skewed pipe. They use a sequence of piping design commands with
interactive input from you. They differ from the execute files in that they provide
for interactive data specification by you.

Many elements must be pulled together in order to design a pipeline. The figure on
the next page shows the flow of information of the major features involved.
The 3D model, the 2D Piping and Instrumentation Diagram (P&ID), and plans
and elevations, are the core of the procedure.
All figures to the left of the core represent data you supply to either the model or
the P&ID. This is your input.
All of the figures to the right of the core represent data and reports that are
generated by the system from the information supplied to it by the various files
that is your output.
The table below explains the meanings of the symbols used in the figure that
follows.
Table 1-7 Design Procedure Symbols
Symbols Definitions
Box (heavy dashed line) Explicit Modeling parts (3D model or P&ID)
Box (thin solid line) Software
S/W Software
Card Data files (text)
Cylinder Figure files (graphics)
Parallelogram Drawings plus reports

Figure 1-1 Piping Design Procedures
Basic Approach to Pipe Modeling

Libraries of parts and related data files are central to the basic approach used to
build an intelligent model or diagram a P&ID.
For three-dimensional modeling, a set of representations of fittings, nozzles, and

structural steel shapes are stored in libraries in the form of nodal figures.
Use INSERT FITTING to select and insert components from these libraries into
the model at the locations and scales you desire. Directory files activate and
deactivate the files that go with the different libraries. Equipment follows the same
principle, but because each piece is unique, you must construct the figure before it
is ready for the insertion software (INSERT NFIGURE).

You can model piping systems in either single- or double-precision part format.
Remember that all elements of your system must be in the same format. Fittings
and assemblies cannot be inserted into a part of a different format. To avoid error,
create separate libraries for your single- and double-precision parts. Place your
single- and double-precision libraries in separate CVPATHs, so they can be
discriminated easily. See Managing CADDS 5 for more information.
Procedure and parameter files let the inserted figures represent the true geometry
of the many parametric variations. The information in the files is used for
clearance checking and detailing.
For P&IDs, libraries of fitting and instrument symbols are important input. The
figures are defined as two-dimensional so they do not have associated procedure or
parameter files.
Generating Piping Specifications

Use the Master Catalogs and the parts library to create a piping specification for a
particular project. To make your piping specification work with the routing and
fitting insertion software, you must create two basic files.
One is a specification (autoselection) file. This is used primarily by the INSERT

FITTING and ROUTE PIPE commands to find and insert the fitting or pipe you
specify.
The other is a parameter file, used by the CREATE DETAIL, CREATE

SURFACE, and CHECK INTERFERENCE commands.
To make these files, create an INFILE. The INFILE and the Master Catalogs are
used by the GENERATE PSFILE command to create the ASFILE and the
PAFILE.
For a complete description of these commands refer to the appropriate books:

CREATE DETAIL and CREATE SURFACE in the Visualization/Preparation
Reference and CHECK INTERFERENCE in Appearance and Hidden Line
Removal Reference.
Autoselection Process
Autoselection (or specification) files serve a number of key functions in piping
design. When you route a pipeline, give it a label that includes size and
specification. This label is used to look in the autoselection file for the appropriate

pipe, to obtain its inner and outer diameters and stock number. This information is
associated with the pipe as a property.
After routing a pipe, insert fittings into the pipeline. The required fitting is
automatically selected from the autoselection file and inserted into the pipeline.
After a model is complete, the specification files obtain additional information

about components, including bolting and other information not incorporated
directly into the model.
The following figure shows the autoselection process. Use INSERT FITTING to
specify the fittings generic type. The pipe size and specification, taken from the
pipeline you select, is used by the command to select the appropriate fitting from
the specification file. The autoselection file provides the information for INSERT
FITTING to determine which figure to select from the fitting library, how to insert
and scale it, and what end type and stock number to associate with it.
Figure 1-2 Autoselection Process

Parametric Procedure Files

Parameter and procedure files help define the geometry of components for
clearance checking and detailing. For a particular variation of a component, obtain
the dimensions (T1, T2, T3...) for the procedure file either from the PLIST
property on the nodal figure or from the default parameter file. The PLIST
property is usually placed on unique items such as equipment; parameter files are
usually used for items such as fittings that vary by size.
Figure 1-3 shows the working of the parametric procedures. A component such as
a valve points to its procedure file; the name of the file is indicated by the PNAME
property. This file acts as input to the checking and detailing software.
The required parameters are obtained from the PLIST property or from the
appropriate parameter file using the stock number from the component as the
referencing key. The parameter file used is determined by the layer of the entity.
If the layer falls within the range for a parameter file, as specified in the DRFILE,
that parameter file is used; otherwise the default parameter file specified by
SELECT PPARAMETERS PAFILE is used.
The parametric process makes it possible for a few library figures to be scaled to
represent a range of components differing only in size. For fittings, nozzles, and
structures which vary parametrically, relatively small libraries of figures are
predefined.
Parameter files are not used for equipment items, as they are modeled individually.
This means that they are not scaled from predefined library figures.
The modeling, detailing, and reporting features include the parameters and
procedure files for the supplied library symbols. When you use the equipment
modeling software (CONSTRUCT EQUIPMENT and PREPARE EQUIPMENT),
procedure files are generated automatically. See the Visualization/Preparation
Reference for more information on these commands.

Figure 1-3 Parametric Procedures for Checking and Detailing

Construct unique equipment with the CONSTRUCT EQUIPMENT and
PREPARE EQUIPMENT commands. Insert any needed nozzles before you file
the completed piece of equipment in your equipment library. PREPARE
EQUIPMENT automatically creates and files the nodal figure and creates a
procedure file.
The figure on the previous page shows that the nozzle library and the equipment
construction software are both used in the construction process. The piece of
equipment is stored in an equipment library as a nodal figure that is ready for
insertion into the model using the INSERT NFIGURE command.


The P&ID and the three-dimensional model can be related and compared using the
project software; however, they have separate databases.
The P&ID is created directly, and is not derived from an intermediary model;
parametric procedures do not apply. The two-dimensional model is essentially the
drawing. The same insertion and routing software used for modeling serve for the
P&ID, but with options for the two-dimensional context.
There is no connection between the specification files and the routing software for
P&IDs in Figure 1-1, because you usually have not defined a lines size and
specification at routing time. For extensive documentation on procedures for
creating P&IDs, see the Intelligent P&ID Managers Guide.
The P&ID is related to piping specifications in two senses:
The process conditions you define in the P&ID provide information that help
you create your piping specification files.
Once created, the P&ID can retroactively access information in the
specification files you create (see the LOOKUP option in REPORT PIPE).
However, the autoselection process is not used to insert the P&ID symbols
automatically. Use a selection file such as cvpd/p/selection which references
generic names, but not size and specification.

Defining Projects
Defining Projects
When designing with the Explicit Modeling system, you create a number of
Explicit Modeling parts and drawings. The P&ID, the model, and the isometric
drawing are stored in separate databases. The model itself may be too large to
handle within a single part. You can break the model into areas, each of which is
modeled as a separate part.
The concept of a project brings these areas together. You define a project with the
project software (DEFINE LINKAGE and LINK PROJECT) and create a file to
store the data common to a project.
You can then use other project commands (CHECK PROJECT and REPORT
PROJECT) to compare P&IDs, isometrics, and the three-dimensional model. You
can also get reports from a model that spans multiple parts.
Warning
Project linkage does not work across mixed precision parts.
For example, single-precision P&ID will not check a project
correctly against a double-precision piping arrangement. To
avoid error, keep the precision of your parts consistent.

Producing Drawings
Producing Drawings
Piping design software produces finished orthographic and isometric drawings.
Detailing software uses model, procedural, and parametric files to create graphic
details. Changes made to the model are reflected in the drawings, but annotation to
the drawing has no effect on the model.
Scaled 3D model graphics of the pipeline are transformed into unscaled isometric
graphics, using the CREATE ISOMETRIC command.


Reports are generated from either the three-dimensional model or the P&ID.
Reporting from the Three-Dimensional Model

The three-dimensional model is the source of interference, pipe stress analysis,
material, and line list reports. Specialized reporting software produces these types
of piping reports automatically.
Bills of material for piping items are derived from the component descriptions in
reports produced with the REPORT PIPE command. For material reports
involving components such as pieces of equipment or structures, use a more
general purpose report generator called Data Extract.
Most of the information reported comes directly from the model, but other sources
can contribute. The line from the procedure files and the parameter file to the
reporting software reflects the parametric input that defines component geometry.
This is used for interference checking and detailing. The connection with the
project software shows that reports dealing with a whole project can be generated.
The specification files are connected to the reporting software to show they
provide information on bolting or materials (stock numbers).
You can create text files containing extended descriptions of components; then
merge this information into your reports using your stock numbers as a
referencing key. This reduces the amount of data that needs to be stored in your
part databases.
These description files are not generated automatically. You create them to suit
your needs.
Reporting from the P&ID

Use the REPORT PIPE command to get line lists, bills of material, and instrument
reports from the P&ID. You may not know the exact size and specification of lines
when routing them. For this reason, you can use LOOKUP to locate stock
numbers from a specification file when you want to report them. The size and
specification should be indicated on the line by then. This option is shown in
Figure 1-1 on page 1-31 by the line running below the P&ID connecting the
specification file and the reporting software.

LOOKUP depends on each fitting having a COMPNAME property that matches

the fitting type name used for automatic selection. For example, if a straight tee has
a COMPNAME of STEE but is found in the selection file using the type name
BRAN (meaning branch), the lookup fails. For more information, see the
Intelligent P&ID Managers Guide.

Chapter 2 Piping Commands - Part 1
This chapter describes the following piping commands. It explains the general
purpose and use of the command, the mode in which the command is used, its
syntax and modifiers.
Explicit Modeling Piping Commands

Command Format
ANNOTATE ISOMETRIC
CHANGE PLINE (PIPELINE)
CONSTRUCT PLINE (PIPELINE)
CREATE ISOMETRIC
DELETE BEND
DELETE FITTING
DELETE PENETRATION
DELETE PLINE (PIPELINE)
DELETE PSUPPORT (Pipe Support)
DIMENSION ISOMETRIC
DIMENSION PIPE
DRAW PSPOOL


The following commands, presented in alphabetical order, are the Explicit
Modeling Piping commands. The six identified by asterisks are used to automate
the production of isometric drawings.
*ANNOTATE ISOMETRIC
CHANGE PLINE (Pipeline)
CONSTRUCT PLINE (Pipeline)
*CREATE ISOMETRIC
DELETE BEND
DELETE FITTING
DELETE PENETRATION
DELETE PLINE (Pipeline)
*DIMENSION ISOMETRIC
DIMENSION PIPE
DRAW PSPOOL
GENERATE CLINE (Center Line)
GENERATE CSSYMBOL (Cut Section Symbol)
*GENERATE ISOMETRIC
GENERATE MDF (Material Description File)
GENERATE PSFILE (Piping Specification File)
GENERATE PIPEDBASE
GENERATE SPOOL
GENERATE SPSYMBOL (Slope Pipe Symbol)
HIDE INTERSECTION
HIGHLIGHT PLINE (Pipeline)
INSERT BEND
INSERT DATUM
INSERT FITTING
INSERT PBREAK (Pipe Break)
INSERT PLABEL (Pipeline Label)

INSERT PSUPPORT (Pipe Support)

INSERT REFDIMENSION (Reference Dimension)
MODIFY PLINE (Pipeline)
OFFSET PLINE (Pipeline)
REFERENCE STRUCTURE
RELATE PLABEL (Pipeline Label)
ROUTE PIPE
*SAVE ANNOTATIONS
SELECT PPARAMETERS (Pipeline Parameters)
SPLIT PIPE
TRANSLATE EQUIPMENT
*TRANSLATE ISOMETRIC
VERIFY DISTANCE
Isometric Drawing Commands

There are two sets of isometric drawing commands, called Series A and Series B.
Series A commands are identified by asterisks, and provide a higher level of
automation and should be used for any new work.
Series B commands are provided for users who want to make a gradual transition
to the new Series A commands.
See the Isometric Drawing User Guide for detailed information on the use of each
of these commands.

Command Format
Command Format
This section uses the following format conventions to describe each command:
Description
Explains the general purpose and use of the command.
Valid Modes
Specifies the mode(s), Model and/or Draw, in which you can use the command.
Syntax
Consists of two parts: (1) the verb/noun combinations with
modifiers and, in most cases, (2) getdata, which is the location information and/or
entity identification.
Modifiers
Lists and describes the valid modifiers for the command and specifies any default
modifier values. Included in this section is a modifier diagram.
To avoid duplication, MODFILE is not listed with each command, although it is

valid with most Explicit Modeling commands.
MODFILE filename incorporates the components of the modifier file filename into
the command. These components are executed in sequence after the modifier
preceding MODFILE, if any. For more information, see the Explicit Modeling
User Guide and Menu Reference.

ANNOTATE ISOMETRIC
ANNOTATE ISOMETRIC
Description
Use this command to add annotations to those already existing on your drawing.
You can combine specifications for dimensions and text within the one command
line.
Valid Modes
Model mode
Syntax
#n# ANNOTATE ISOMETRIC [modifiers]
Modifiers
The following diagram shows the flow of ANNOTATE ISOMETRIC modifiers.
An asterisk (*) denotes a default modifier. For a full explanation of modifier
diagrams, see the Preface.

ANNOTATE ISOMETRIC

ANNOTATE ISOMETRIC

ANNOTATE ISOMETRIC

ANNOTATE ISOMETRIC
Modifiers are listed alphabetically by level. When there are multiple levels of
modifiers, level is indicated by the left number. A description of each modifier
follows. First level modifiers and their submodifiers are grouped by a line.
1 ATTACHMENT
This modifier automatically annotates the vessel name with a nozzle

designation or a pipeline name at the origin and/or destination of a pipeline.
Any pipeline name of a branch connection in the pipeline network will also be
annotated. The attachment text comes from properties (FROMTO and
CONTLINE) created by the SAVE ANNOTATIONS command. The text is
similar to the header information on the from/to report created by the REPORT
PIPE command and located near the origin of the pipeline, the destination of the
pipeline, and the branch(es) of the connecting pipeline.
2 ON
An implicit default.
2 OFF
Deactivates annotations of attachments.
2 PREFIX text
Prefixes each attachment text with an input string. Default text is a blank.
Delimiters are needed when special characters (such as -, /) are used.
2 SUFFIX text
Suffixes each attachment text with an input string. Default text is a blank.
2 BOX
Produces a box around each attachment text.
2 NOBOX
(Default) No box appears around each attachment text.
2 CIRCLE
Produces a circle around each attachment text.

ANNOTATE ISOMETRIC
2 HEXAGON
Produces a hexagon around each attachment text.
2 TAIL
Produces a leader line from text to component. Use with modifier NOBOX.
2 NOTAIL
Produces a leader line from text to component. Use with modifiers

BOX,CIRCLE, and HEXAGON.
2 SUPPRESS
(Default) No leader lines appear.
2 ILAYER n
Inserts on the increment layer relative to active construction layer. (Default is

0.)
2 LAYER n
Inserts on specified layer. (Default is active construction layer.)
2 DISTANCE real
Specifies the distance in the current drawing units between the from-to
annotation and the annotated location. The final distance can vary due to the
overlap checking process. The Default is 1.13 drawing units.
1 DATUM
This modifier automatically annotates datum information (coordinate values
east, north, and elevation) at the beginning and end of the pipeline. It also
automatically annotates datum information (coordinate values for elevation
only) at every change in elevation. Locate the text near the origin or the
destination of the pipeline, above the Nline at the change in elevation (z
values).
2 OFF
Deactivates annotation of datums.

ANNOTATE ISOMETRIC
2 COORD
(Default) Annotates datum at the beginning and end of a pipeline. Only enters
elevation and coordinate values.
2 ELEVATION
Annotates datum (elevation values only) at every change in elevation.
2 ALL
Annotates all of the above.
2 ILAYER n
Inserts on the increment layer relative to the active construction layer. The
Default is 0.
2 LAYER n
Inserts on the specified layer. The Default is the active construction layer.
2 DISTANCE real
Specifies the distance in the current drawing units between datum annotation
and the annotated location. The final distance can vary due to the overlap
checking process. The Default is 0.75 drawing units.
1 DETAIL
Creates a detailed isometric drawing from some portion of the current isometric
drawing. The user has to identify the portion of the drawing to be blown up by
specifying a polygonal window. The polygon window must cut the pipeline in,
at most, two locations.
This modifier will, by default, copy the current drawing and create the
annotated detailed blowup on a new drawing. The user can specify the drawing
name or a drawing form part to be used for the detail.
Any valid pipeline isometric model that has been created by the CONSTRUCT
PLINE, SAVE ANNOTATIONS or CREATE ISOMETRIC procedure can be
used. A completed isometric is also acceptable as input.

ANNOTATE ISOMETRIC
2 DRAWNAME drawing name
Specifies the drawing name to give the new drawing. The DRAWNAME
modifier need not be entered if the drawing name is specified immediately after
the DETAIL modifier. The default name is the current drawing name with
-DETAIL appended to it.
2 FORM
Names the form part from which the information on drawing size, graphics,
and view definition is taken. The DRAW modifier is always required with
FORM regardless of the number of drawings in the form part. There is no
default for FORM.
3 DRAW form part drawing name
Specifies the associated drawing in the form part specified with the FORM
modifier.
1 DIMENSION
This modifier dimensions the isometric.
2 ALIGN
(Default) Aligns dimensions with one another, where possible, and also aligns
dimensions such that they are coplanar with the fitting graphics that are to be
dimensioned. Even if the pipe segments are not collinear, the dimension
between two piping components is made in the same plane and direction as
adjacent dimensions. In the case of planar sloped pipe segments, the
dimensions are made in a plane perpendicular to the plane of the pipeline
segment.
3 OFF
Deactivates alignment of dimensions.
2 ON
2 OFF
Deactivates dimensioning of the isometric.

ANNOTATE ISOMETRIC
2 ILAYER n

0.)
2 LAYER n
2 DISTANCE real
Specifies the distance in the current drawing units between the dimension
annotation and the annotated pipe. The final distance can vary due to the overlap
checking process. The default is 1 drawing unit.
2 BUTTWELD flag
Annotates the butt-welded fittings in the piping isometric drawings.
2 SUPPRESS flag
Suppresses both the dimension lines and the extension lines. When you use this
modifier without the DIMENSION or EXTENSION modifier, by default, both
the dimension and the extension lines are suppressed.
3 DIMENSION flag
Suppresses only the dimension lines.
3 EXTENSION flag
Suppresses only the extension lines.
1 DISTANCE real
Specifies the distance in the current drawing units between a general annotation
and the annotated object. The final distance can vary due to the overlap
checking process. The default is 0.75 drawing units.
General annotations are a pipeline label, reducer size, bend angle, or bend
radius.
1 ESYMBOL
This modifier automatically places a symbol at the end of a pipeline that

visually represents the type of connection the pipe is attached to. Locate/orient
the symbol in such a way that it matches the direction of the pipe.

ANNOTATE ISOMETRIC
2 OFF
2 ILAYER n

0.)
2 LAYER n
2 NOZZLE
Inserts a predefined nozzle symbol.
2 PIPE
Inserts a predefined pipe symbol.
1 EXCLUDE
Omits the annotation for some portion of a complicated isometric drawing. The
user has to identify the portion of the isometric to be excluded by specifying a
polygonal window. The portion of the isometric inside the window will not
have any annotation information.
1 FASTANNO
Displays the annotated isometric drawing with minimal overlap checking. The
speed for processing the annotated isometric drawing of complicated pipelines
is faster, but there is often much overlapping on the drawing, especially for
complicated pipelines.
The default is full overlap checking.
1 FITTYPE fittype number
When representing the graphics for a continuation fitting, the user can select
the scale of the graphics for the continuation fitting by using this modifier, and
the following second-level modifiers, in the same manner as with the CREATE
ISOMETRIC command. The value of modifier is the fitting type number or the
FITTYPE property of the fitting. The continuation fittings available are in the
CVPD.ISO.T and CVPD.F.SYM directories.

ANNOTATE ISOMETRIC
2 LENGTH x
Specifies the length (along the run) of the fitting symbols. The value of x is in
drawing units.
2 HEIGHT x
Specifies the height or radial size (perpendicular to the run) of the fitting
symbol. The value of x is in drawing units.
1 INSTRUMENT
This modifier automatically annotates instrument numbers. The instrument

number text is obtained from a text property (INSTRUM) created by the
INSTRUMENT modifier in the INSERT FITTING command or by using the
base Explicit Modeling command INSERT PROPERTY INSTRUM.
2 ON
2 OFF
Deactivates annotations of instrument numbers.
2 PREFIX text
Prefixes each instrument text with an input string. Default text is a blank. Text
delimiters are needed when special characters (such as -, /) are used.
2 SUFFIX text
Suffixes each instrument text with an input string. Default text is a blank. Text
2 BOX
Produces a box around each instrument text.
2 NOBOX
No box appears around each instrument text.
2 CIRCLE
(Default) Produces a circle around each instrument text.

ANNOTATE ISOMETRIC
2 HEXAGON
Produces a hexagon around each instrument text.
2 TAIL
2 NOTAIL
(Default) Produces a leader line from text to component. Use with modifiers
BOX, CIRCLE, and HEXAGON.
2 SUPPRESS
No leader lines appear.
2 ILAYER n

0.)
2 LAYER n
2 DISTANCE real
Specifies the distance in the current drawing units between the instrument
number annotation and the annotated fitting. The final distance can vary due to
the overlap checking process. The Default is 1.13 drawing units.
1 ITEM
This modifier automatically annotates pipeline components with item numbers.
The item number text comes from a text property (ITEMNUMB) created by the
SAVE ANNOTATIONS command, which also determines the item numbers to
be annotated.
2 ON
2 OFF
Deactivates annotations of item numbers.

ANNOTATE ISOMETRIC
2 PREFIX text
Prefixes each item text with an input string. Default text is a blank. Text
2 SUFFIX text
Suffixes each item text with an input string. Default text is a blank. Text
2 BOX
(Default) Produces a box around each item text.
2 NOBOX
No box appears around each item text.
2 CIRCLE
Produces a circle around each item text.
2 HEXAGON
Produces a hexagon around each item text.
2 TAIL
2 NOTAIL
(Default) Produces a leader line from text to component. Use with modifiers
BOX, CIRCLE, and HEXAGON.
2 SUPPRESS
No leader lines appear.
2 ILAYER n

0.)

ANNOTATE ISOMETRIC
2 LAYER n
2 DISTANCE real
Specifies the distance in the current drawing units between the item number
annotation and the annotated object. The final distance can vary due to the
1 ILAYER n

0.)
1 LAYER n
1 NOZZLE
Use to specify a change to the nozzle symbol values.
2 HEIGHT
Specifies the height (perpendicular to the run) of the nozzle. (Default is 0.5
drawing units.)
2 LENGTH
Specifies the length (along the run) of the nozzle. (Default is 1 drawing unit.)
2 HDLENRATIO
Specifies the head to length ratio (along the run) of the nozzle. (Default is 0.5.)
Note that all ratios are related to head height.
2 HGTRATIO
Specifies the scale factor for height (perpendicular to the run) of the nozzle.
(Default is 1.)
2 TAILRATIO
Specifies the tail ratio (along the run) of the nozzle. (Default is 1.)

ANNOTATE ISOMETRIC
2 INDENTRATIO
Specifies the indent ratio (perpendicular to the run) of the nozzle. (Default is
0.2.)
1 ORIENTATION
This modifier controls the types of dimensioning for skewed and offset
pipelines.
2 ON
2 OFF
Deactivates skewed dimensioning and creation of orientation box for skewed

pipeline segment.
2 BOX
(Default) Provides a box with dimensions for the skewed segments.
3 FULL
(Default) Provides a full box with dimensions for the skewed segments.
3 HALF
Provides a half box with dimensions for the skewed segments.
2 TRIANGLE
Provides a triangle with dimensions for the offset segments.
3 NOSHADE
(Default) No cross-hatching appears within the triangle.
3 SHADE
Provides cross-hatching within the triangle.

ANNOTATE ISOMETRIC
4 PATTERN text
File name for pattern hatch to be used in shading orientation triangles. The
default names are cvpd/iso/pha/inch and cvpd/iso/pha/mm.
5 SCALE x
This modifier changes the scale of the inserted pattern hatch.
5 INTERVAL x
This modifier specifies the distance between successive tiles of pattern hatches
along the construction X-axis. The default value of x is 0.0.
4 SPACING x
This modifier specifies the distance between successive tiles of hatching along
the construction Y-axis. This modifier must be used if the hatch units differ
from the part units. The default value of x is 0.0.
1 PIPE
Specifies a change to the pipe symbol values.
2 HEIGHT
Specifies the height (perpendicular to the run) of the pipe. (Default is 0.5
drawing units.)
2 LENGTH
Specifies the length (along the run) of the pipe. (Default is 1 drawing unit.)
2 HGTRATIO
Specifies the scale factor for height (perpendicular to the run) of the pipe.
(Default is 1.)
2 LENRATIO
Specifies the length ratio (along the run) of the pipe. (Default is 2.)
ALL modifiers (except NOZZLE and PIPE) will have the submodifiers LAYER
and ILAYER.

ANNOTATE ISOMETRIC
1 SLOPE
This modifier controls the types of dimensioning for sloped pipelines, so as to

annotate the direction of the sloped segment where specified.
2 ON
2 NOBOX
Deactivates sloped dimensioning and production of slope box or triangle.
2 DATUM
Provides elevation at each end of slope.
2 HORIZONTAL
Provides for dimensioning the sloped lines with horizontal values except for
major components (that is, valves) that use the true length.
2 BOX
(Default) Provides a box with dimensions for the sloped segments.
3 FULL
(Default) Provides a full box with dimensions for the sloped segments.
3 HALF
Provides a half box with dimensions for the sloped segments.
2 TRIANGLE
Provides a triangle with dimensions for the sloped segments.
3 NOSHADE
(Default) No cross-hatching appears within the triangle.
3 SHADE
Provides cross-hatching within the triangle.

ANNOTATE ISOMETRIC
4 PATTERN text
File name for pattern hatch to be used in shading orientation triangles. The
default names are cvpd/iso/pha/inch and cvpd/iso/pha/mm.
5 SCALE x
This modifier changes the scale of the inserted pattern hatch.
5 INTERVAL x
This modifier specifies the distance between successive tiles of pattern hatches
along the construction X-axis. The default value of x is 0.0.
4 SPACING x
This modifier specifies the distance between successive tiles of hatching along
the construction Y-axis. This modifier must be used if the hatch units differ
from the part units. The default value of x is 0.0.
1 SSYMBOL
This modifier automatically places a symbol at the beginning of a pipeline to

visually represent the type of connection the pipe is attached to. Locates and
orients the symbol in such a way that it matches the direction of the pipe.
2 OFF
2 NOZZLE
Inserts a predefined nozzle symbol.
2 PIPE
Inserts a predefined pipe symbol.
2 ILAYER n
Inserts on the increment layer relative to command level layer. (Default is 0.)
2 LAYER n

ANNOTATE ISOMETRIC
1 TERMSYM
Automatically inserts pipe or nozzle symbols at all branches and terminations

where the FROMTO or CONTLINE text properties exist (which are created by
the command SAVE ANNOTATIONS). The nozzle symbol is inserted at the
FROMTO property and the pipe symbol at the CONTLINE property.
2 DISTANCE x
Specifies the distance between the end of the pipeline and the termination
symbol. Default is 1 drawing unit.
2 ILAYER n
2 LAYER n
Please note: To highlight the results of the TERMSYM modifier, the

dimensions, vessel and pipeline name annotations, pipe component item numbers,
and weld numbers are turned off by the system.
1 TRIMELBOW
This modifier automatically annotates a trimmed elbow that has been trimmed
to an angle less than 90 degrees, or a 45 degree elbow that has been trimmed to
an angle less than 45 degrees. This information is already provided in the model
on the Figure with the property of TRIM and a numeric value created with the
command INSERT FITTING TRIM. The text is located near the trimmed
fitting.
2 ON
2 OFF
Deactivates annotations of trimmed elbows.
2 PREFIX text
Prefixes each trimmed elbow text with an input string. Default text is a blank.

ANNOTATE ISOMETRIC
2 SUFFIX text
Suffixes each trimmed elbow text with an input string. Default text is a blank.
2 BOX
Produces a box around each item text.
2 NOBOX
(Default) No box appears around each item text.
2 CIRCLE
Produces a circle around each item text.
2 HEXAGON
Produces a hexagon around each item text.
2 TAIL
2 NOTAIL
Produces a leader line from text to component. Use with modifiers BOX,
CIRCLE, and HEXAGON.
2 SUPPRESS
2 ILAYER n
2 LAYER n

ANNOTATE ISOMETRIC
2 DISTANCE real
Specifies the distance in the current drawing units between the trimmed elbow
annotation and the annotated elbow. The final distance can vary due to the
1 WELD
This modifier automatically annotates weld numbers at each shop weld and/or
field weld, sequentially and in the direction of flow of the pipeline from/to.
The weld number text comes from a text property (WELDNUMB) created by
the SAVE ANNOTATIONS command. A shop weld is drawn as a weld dot on a
Cnode where specified with the existing modifier ENDTYPE or a default of an
endtype property with a W in any of the characters. A field weld is drawn as a
weld dot on a Cnode with an x through it. (This Cnode has a fittype prop of 70).
The text is located close to each weld to be annotated, when the default
NOBOX modifier is used.
2 ON
2 OFF
Deactivates annotation of welds.
2 SHOPWELD
Annotates shopwelds.
3 OFF
Deactivates annotation of shopwelds.
3 PREFIX text
Prefixes each shopweld text with an input string. Default text is W.
3 SUFFIX text
Suffixes each shopweld with an input string. Default text is a blank. Text
delimiters are needed when special characters (such as -, /) are used in the text.
2 FIELDWELD
Annotates fieldwelds.

ANNOTATE ISOMETRIC
3 OFF
Deactivates annotation of fieldwelds.
3 PREFIX text
Prefixes each fieldweld text with an input string. Default text is FW.
3 SUFFIX text
Suffixes each fieldweld with an input string. Default text is a blank. Text
delimiters are needed when special characters (such as -, /) are used in the text.
2 NOBOX
(Default) No box appears around each weld text.
2 BOX
Produces a box around each weld text.
2 CIRCLE
Produces a circle around each weld text.
2 HEXAGON
Produces a hexagon around each weld text.
2 TAIL
2 NOTAIL
Produces a leader line from text to component. Use with modifiers

BOX,CIRCLE, and HEXAGON.
2 SUPPRESS
2 ILAYER n

ANNOTATE ISOMETRIC
2 LAYER n
2 DISTANCE real
Specifies the distance in the current drawing units between the weld number
annotation and the annotated weld. The final distance can vary due to the
1 WELDTABLE
Creates a weld table in the current isometric drawing. This modifier requires
that a draw mode text node, with the WELDTABL property, exists in the
drawing. The text node provides the location of the lower right hand corner of
the weld table. The WELD modifier must be selected in order for a weld table
to be generated.
Example 1
#n# ANNOTATE ISOMETRIC ATTACHMENT WELD OFF ITEM OFF DIMENSION OFF

ANNOTATE ISOMETRIC
Example 2
#n# ANNOTATE ISOMETRIC TRIMELBOW ATTACHMENT OFF WELD OFF ITEM OFF
DIMENSION OFF

ANNOTATE ISOMETRIC
Example 3
#n# ANNOTATE ISOMETRIC DATUM ALL ATTACHMENT OFF WELD OFF ITEM OFF
DIMENSION OFF

ANNOTATE ISOMETRIC
Example 4
#n# ANNOTATE ISOMETRIC DATUM COORDINATE ATTACHMENT OFF WELD OFF
ITEM OFF DIMENSION OFF

ANNOTATE ISOMETRIC
Example 5
#n# ANNOTATE ISOMETRIC DATUM ELEVATION ATTACHMENT OFF WELD OFF

ANNOTATE ISOMETRIC
Example 6
#n# ANNOTATE ISOMETRIC SSYMBOL NOZZLE ATTACHMENT OFF WELD OFF ITEM
OFF DIMENSION OFF
Example 7
#n# ANNOTATE ISOMETRIC SSYMBOL PIPE ATTACHMENT OFF WELD OFF ITEM
OFF DIMENSION OFF

ANNOTATE ISOMETRIC
Example 8
#n# ANNOTATE ISOMETRIC ESYMBOL NOZZLE ATTACHMENT OFF WELD OFF ITEM
OFF DIMENSION OFF
Example 9
#n# ANNOTATE ISOMETRIC ESYMBOL PIPE ATTACHMENT OFF WELD OFF ITEM
OFF DIMENSION OFF

ANNOTATE ISOMETRIC
Example 10
#n# ANNOTATE ISOMETRIC WELD ATTACHMENT OFF WELD OFF ITEM OFF
DIMENSION OFF
Example 11
#n# ANNOTATE ISOMETRIC WELD SHOP PREFIX WE FIELD OFF ATTACHMENT
OFF WELD OFF ITEM OFF DIMENSION OFF

ANNOTATE ISOMETRIC
Example 12
#n# ANNOTATE ISOMETRIC WELD SHOP OFF FIELD SUFFIX -50 TAIL
ATTACHMENT OFF WELD OFF ITEM OFF DIMENSION OFF
Example 13
#n# ANNOTATE ISOMETRIC ITEM ATTACHMENT OFF WELD OFF ITEM OFF
DIMENSION OFF

ANNOTATE ISOMETRIC
Example 14
#n# ANNOTATE ISOMETRIC ITEM NOBOX SUPPRESS ATTACHMENT OFF WELD OFF
Example 15
#n# ANNOTATE ISOMETRIC INSTRUMENT ATTACHMENT OFF WELD OFF ITEM OFF
DIMENSION OFF

ANNOTATE ISOMETRIC
Example 16
#n# ANNOTATE ISOMETRIC ORIENTATION BOX FULL ATTACHMENT OFF WELD
OFF ITEM OFF

ANNOTATE ISOMETRIC
Example 17
#n# ANNOTATE ISOMETRIC ORIENTATION BOX HALF ATTACHMENT OFF WELD
OFF ITEM OFF

ANNOTATE ISOMETRIC
Example 18
#n# ANNOTATE ISOMETRIC ORIENTATION TRIANGLE ATTACHMENT OFF WELD
OFF ITEM OFF

ANNOTATE ISOMETRIC
Example 19
#n# ANNOTATE ISOMETRIC ORIENTATION TRIANGLE SHADE ATTACHMENT OFF
WELD OFF ITEM OFF

ANNOTATE ISOMETRIC
Example 20
#n# ANNOTATE ISOMETRIC SLOPE NOBOX DATUM ATTACHMENT OFF WELD OFF
ITEM OFF

ANNOTATE ISOMETRIC
Example 21
#n# ANNOTATE ISOMETRIC SLOPE NOBOX HORIZ ATTACHMENT OFF WELD OFF
ITEM OFF

ANNOTATE ISOMETRIC
Example 22
#n# ANNOTATE ISOMETRIC DIMENSION OFF ATTACHMENT OFF ITEM OFF WELD
OFF TERMSYM
Example 23
OFF TERMSYM NOZZLE HEIGHT 1 LENGTH 2
Please note: You can rescale the flange in the pipeline using CREATE
ISOMETRIC COMPNAME WNRF HEIGHT 1 LENGTH 2. In order to highlight
the rescaled nozzle, the flange in this example was not rescaled.

ANNOTATE ISOMETRIC
Example 24
OFF TERMSYM PIPE HEIGHT 1 LENGTH 2
Example 25
OFF TERMSYM NOZZLE HDLENRATIO 1.5

ANNOTATE ISOMETRIC
Example 26
OFF TERMSYM PIPE HGTRATIO 3
Example 27
OFF TERMSYM NOZZLE HGTRATIO 3

ANNOTATE ISOMETRIC
Example 28
OFF TERMSYM PIPE LENRATIO 4
Example 29
OFF TERMSYM NOZZLE TAILRATIO 3

ANNOTATE ISOMETRIC
Example 30
OFF TERMSYM NOZZLE INDENTRATIO.4
Example 31
#n# ANNOTATE ISOMETRIC DIMENSION ON BUTTWELD ON

ANNOTATE ISOMETRIC
Example 32
#n# ANNOTATE ISOMETRIC DIMENSION ON SUPPRESS DIMENSION ON
Example 33
#n# ANNOTATE ISOMETRIC DIMENSION ON SUPPRESS EXTENSION ON
Example 34
#n# ANNOTATE ISOMETRIC DIMENSION ON SUPPRESS ON

ANNOTATE ISOMETRIC
Notes
The following general notes will help you further in using the ANNOTATE
ISOMETRIC command.
When using the SHADE submodifier with the ANNOTATE ISOMETRIC
command, you have a choice of pattern hatches designed for English or metric
parts. The modifier table for the ANNOTATE ISOMETRIC command is set up
with the English version by default. Your system administrator can change the
default as follows:
1. Locate the SHADE submodifier in the modifier table for the ANNOTATE
ISOMETRIC command. (Note that this submodifier appears twice, under
SLOPE and ORIENTATION.) Under the SHADE modifier is the PATTERN
modifier with two lines showing the English and metric defaults.
2. Comment out the line DEFAULT= CVPD.ISO.PHA.INCH.
3. Uncomment the line DEFAULT= CVPD.ISO.PHA.MM.
Alternatively, you can explicitly specify the appropriate pattern name each time the
command is used:
English units: ANNOTATE ISOMETRIC ORIENTATION/SLOPE TRIANGLE

SHADE PATTERN CVPD.ISO.PHA.INCH
Metric units: ANNOTATE ISOMETRIC ORIENTATION/SLOPE TRIANGLE

SHADE PATTERN CVPD.ISO.PHA.MM
Please note: You can use any previously defined pattern-hatch name for the
pattern, including any that you have prepared.

Description
Use this command to change the layer of pipe (Nlines), pipeline termini (Cnodes),
and inline components (Nfigures). Other related nodal entities are shifted
accordingly. The relative layering of the nodal entities within the inline
components is maintained, as is the layering of any Tnodes and Ntext related to
pipes and their termini.
The layering of the figure graphics of inline components is maintained. This

layering is used to separate three-dimensional model graphics from
two-dimensional isometric symbol graphics. The relative layering of detail
graphics and their associated model pipes or inline components is not maintained.
The layers of the detail graphics are changed directly.
You can select only one pipeline within a command.
Valid Modes
Model mode
Syntax
#n# CHANGE PLINE LAYER n [modifiers]: getdata
or
#n# CHANGE PLINE LINENO text LAYER n [modifiers]

Modifiers
The following diagram shows the flow of CHANGE PLINE modifiers. An asterisk
(*) denotes a default modifier. For a full explanation of modifier diagrams, see the
Preface.
follows.
1 LAYER n
Changes the layer of pipes, termini, and inline components to n, or by n, as

specified by the use of the modifiers ABSOLUTE and RELATIVE,
respectively. The range of n is 0-254 for ABSOLUTE, or +/- 1-254 for
RELATIVE. When the layer number of a nodal entity related to a pipe or inline
component goes out of bounds, wraparound occurs (255 is subtracted from the
number).
2 ABSOLUTE
(Default) All pipes, pipeline termini, and inline components are transferred to
layer n. For example, if pipes are on layer 10 and related Ntext is on layer 15, an
n of 100 results in pipes on layer 100 and Ntext on layer 105.
2 RELATIVE
All pipes, pipeline termini, and inline components are transferred by n layers.
For example, if pipes are on layer 10 and related Ntext on layer 15, an n of -5
results in pipes on layer 5 and related Ntext on layer 10.

1 LINENO text
(Line Number) Identifies a pipeline by its line number. You can specify any
subset of the fields in the pipelines label as defined in the directory file; for
example, P-101 from the label P-101-10-B6A. Only the first pipeline found
with the specified line number is identified.
1 SECTION
Changes layering within the section of the pipeline between the two selections.
Procedure 1
To move a pipeline to a different layer by digitizing,
1. Enter the command CHANGE PLINE, the modifier LAYER, and the number
of a layer (1-254).
2. Enter a colon. The system prompts MODEL ent. Digitize the pipeline to be
moved and press RETURN.
Procedure 2
To identify a pipeline by its number, and move it to a layer that you identify by
number,
1. Enter CHANGE PLINE, the modifier LINENO, and the pipeline number; enter
the LAYER modifier and the new layer number for the pipeline.
2. Press RETURN.
Procedure 3
To move a section of a pipeline by a relative, incremental amount,
1. Enter CHANGE PLINE, the modifier LAYER with a number specifying the
increment by which all layer numbers are shifted, and the modifiers
RELATIVE and SECTION.
2. Enter a colon. The system prompts MODEL ent. Select the ends of the
section within which relayering is to be done.
3. Press RETURN.

Description
Use this command to extract a pipeline or pipeline network from the active part
and file it as another part. Identify a pipe (Nline) on the desired pipeline or
network, or specify the pipeline by LINENO. The selected pipeline becomes a new
part, and must be given a new name, and the current part remains unchanged. This
new part can be processed by the Isometric Drawing commands.
The new part has the same drawings as the active part. When you construct an
isometric drawing, you do not need the other drawings associated with the model.
Delete these drawings with the command DELETE DRAWING.
The total number of entities for an extracted pipeline is 20,000.
CONSTRUCT PLINE facilitates the process of making drawings by using an

execute file. The file must include the modifier LINENO or MULTIPLE, which
allows you to identify the pipelines without stopping the automatic process. The
sequence of commands in such an execute file is:
SAVE ANNOTATIONS
CONSTRUCT PLINE LINENO
CREATE ISOMETRIC
ANNOTATE ISOMETRIC
Valid Modes
Model mode
Syntax
#n# CONSTRUCT PLINE partname [modifiers]: getdata

Modifiers
The following diagram shows the flow of CONSTRUCT PLINE modifiers. For a
full explanation of modifier diagrams, see the Preface.
follows.
1 DELETE
Overwrites an existing part identified by part name.
1 FIGNAME partname
(Required) Names the part to be constructed. The maximum length is 60

characters with a limit of 20 characters per level.

1 LINENO delimited text
(Line Number) Identifies a single pipeline to extract. You can specify any subset
of the fields in the pipeline label as defined in the directory file, for example,
CW-100. Only the first pipeline found with the specified line number is
extracted. When you use the LINENO modifier you do not select pipelines in
getdata. This modifier makes it possible to automate the process of making
isometric drawings. LINENO and MULTIPLE are mutually exclusive.
1 MLINENO
Constructs parts with multiple lines from the current active part.
2 MNEMONIC mnemonic name

Identifies the mnemonic name of pipelines. All the pipelines having this
mnemonic are extracted to the new part. This modifier and the LINENO
modifier are mutually exclusive.
2 LINENOS line numbers
Identifies pipelines to be extracted. You can specify any subset of the fields in
the pipeline label as defined in the directory file, for example, CW-100. Only
the first pipeline found with the specified line number is extracted. When you
use the LINENO modifier you do not select pipelines in getdata. Use a comma
(,) as a delimiter when specifying several line numbers.
1 MULTIPLE
Identifies and extracts a network of pipelines when you select a single pipeline
in the network. The network is traced in both directions and includes all
connecting pipelines until a connecting Cnode with the TERMNAM property is
encountered. You must remove the property if you want the next pipeline to be
extracted. Be sure to reinsert the TERMNAM property before you use the
reporting commands.
If you want more than one pipeline but not the entire network, insert the
TERMNAM property at the end of the last pipeline you want to extract.
LINENO and MULTIPLE are mutually exclusive.
1 ORIGIN
Specifies a new origin or base point for the constructed part. The
three-dimensional base point (X,Y,Z) so specified becomes the point of origin
(0,0,0) of the constructed part. If you do not specify a base point, the origin of
the active part (the 0,0,0 point) becomes the origin of the constructed part. With
ORIGIN, the first getdata prompt is MODEL loc.

You must use the following commands in the constructed part to reference the
coordinates of the model from which the pipeline was extracted:
#n# DEFINE CPL name: MODEL loc d
#n# SELECT CPL name
The MODEL loc you specify is the origin of the model from which the
pipeline is extended. This allows INSERT DATUM and other commands,
which verify locations to yield the correct coordinate values.
Procedure 1
To identify a pipeline by digitizing it, and extract it from the active part,
1. Enter the command CONSTRUCT PLINE and the name of the part.
2. The system prompts MODEL ent. Digitize a pipe (Nline) along the desired
pipeline.
3. Press RETURN.
Procedure 2
To identify a pipeline by specifying its line number, and extract it from a part that
you identify by name,
1. Enter the command CONSTRUCT PLINE, the name of the part, and identify
the pipeline with the LINENO modifier.
2. Press RETURN.
Procedure 3
To extract a pipe from a pipeline that you identify by digitizing, and give the new
part a different point of origin.
1. Enter the command CONSTRUCT PLINE, the name of the part, and the
modifier ORIGIN.
2. The system prompts MODEL loc. Select the new point of origin by
digitizing or by explicit coordinates, and enter a semicolon.
3. The system prompts MODEL ent. Select a pipe (Nline) along the desired
pipeline.
4. Press RETURN.

Example
CONSTRUCT PLINE is used here to extract pipeline O-8242-10-B3A from the
CVPDC plant model. This extracted line will also be used as an example in the
other commands used to create isometric drawings. To reduce visual clutter,
structures and many of the other pipelines are echoed off. Cnodes, Tnodes, and
Nfigure symbols are also echoed off. The model graphics are echoed off. Only the
isometric graphics of fittings are echoed on.
#n# CONSTRUCT PLINE CVPDC.00.ISO.O-8242: MODEL ent d


CREATE ISOMETRIC
CREATE ISOMETRIC
Description
Use this command to generate a piping isometric drawing from a
three-dimensional model of a pipeline or spool.
The model information should be saved beforehand with SAVE ANNOTATIONS.
A single pipeline can be extracted from a multi-pipeline model into its own part
using CONSTRUCT PIPELINE. Spools can be extracted into their own parts by
running GENERATE SPOOL followed by CONSTRUCT PLINE for each spool.
CREATE ISOMETRIC will rescale the model to make the isometric. There should
be only one pipeline or spool in the part where CREATE ISOMETRIC is run.
Use ANNOTATE ISOMETRIC to annotate and dimension the isometric. This will
use data stored in the model by SAVE ANNOTATIONS.
The command also blanks intervals in pipe segments that are hidden by other
pipes.
Valid Modes
Model mode
Syntax
#n# CREATE ISOMETRIC [modifiers]

CREATE ISOMETRIC
Modifiers
The following diagram shows the flow of CREATE ISOMETRIC modifiers. An
asterisk (*) denotes a default modifier. For a full explanation of modifier diagrams,
see the Preface.

CREATE ISOMETRIC
follows.
1 BEND x
Specifies the size of the bend symbol on the drawing. The default is 1 drawing
unit.
1 CHECKBOX
Checks the extent of the dimension box, which is generated in the case of
sloped pipeline segments. If necessary, the view scaling factor is adjusted to
ensure that the box extent fits completely within the view clipping frame.
2 ON
Enables checking of the dimension box extent.
2 OFF
(Default) Disables checking of the dimension box extent.
1 COMPNAME Component Name
Specify the size of fitting symbols by using various compnames. For example,
screwed and socket weld globe valves that have compnames of GLSC and
GLSW can be scaled differently from flanged or butt weld valves that have
compnames of GLBV and GLBW. This modifier overrides the modifiers
FITTYPE and FITTING.
2 HEIGHT x
Specifies the height or radial size (perpendicular to the run) of the compnames.
The default is 0.5 drawing units.
2 LENGTH x
Specifies the length (along the run) of the compnames. The default is 1 drawing
unit.
1 FITTING
Specifies the size of fitting symbols.

CREATE ISOMETRIC
2 HEIGHT x
symbols. The default is 0.5 drawing units.
2 LENGTH x
Specifies the length (along the run) of the fitting symbols. The default is 1
drawing unit.
1 FITTYPE n
Specifies the size of fitting symbols by using various fittypes. A gate valve that
has a fittype of 10 may require a different scaling than a wafer valve with a
fittype of 11.
2 HEIGHT x
2 LENGTH x
drawing unit.
1 FLANGE x
Specifies the length (along the run) of the flange symbol. Height is the same as
for fittings. The default is.25 drawing units.
1 FLOWARROWS
Specifies flowarrow parameters. Flowarrows are placed on the mainline and

each branchline, as near as possible to the middle pipe.
2 CLOSED
Specifies unfilled triangular arrows. This is mutually exclusive with FILLED

and OPEN.
2 FILLED
(Default) Specifies filled triangular arrows. This is mutually exclusive with

CLOSED and OPEN.

CREATE ISOMETRIC
2 LENGTH x
Specifies length of arrow (along the run). The default is 0.25 drawing units.
2 OFF
Deactivates drawing of flowarrows.
2 ON
(Default) Activates drawing of flowarrows.
2 OPEN
Specifies V-shaped unfilled flowarrows. This is mutually exclusive with

CLOSED and FILLED.
2 RATIO x
Specifies the ratio of the flowarrow length to width. The default is 3.0.
1 GASKET x
Specifies the length (along the run) of gap for gaskets. The default is 0.25
drawing units.
1 INSULSYMBOL
Creates an insulation symbol along the pipeline when the pipeline label (as
defined in the active directory file) has a value in the insulation field.
2 ON
(Default) Enables the creation of an insulation symbol along the pipeline if the
pipe label has a value in the insulation field.
2 OFF
Disables the creation of an insulation symbol.
2 LENGTH x
Specifies the length (along the run) of the insulation symbol. The default is 0.25
drawing units.

CREATE ISOMETRIC
2 RATIO x
Specifies the ratio of the length to the width of the insulation symbol. The
default is 3.0.
1 PIPE
Specifies the maximum and minimum lengths of pipe.
2 MAXIMUM x
Specifies the maximum length of pipe. The default is 5.0 drawing units.
2 MINIMUM x
Specifies the minimum length of pipe. The default is 2.0 drawing units.
1 ROTATION
Allows the automatic rotation of a pipeline when there is a pipe segment going
directly into or out of the view, or back-to-back pipe segments that appear
collinear in the drawing.
2 ON
(Implicit default) Allows automatic rotation of a pipeline when the command

CREATE ISOMETRIC is entered.
2 OFF
Deactivates automatic rotation of a pipeline, creating a hidden line view as if

the command GENERATE ISOMETRIC had been used.
1 WELD
Activates or deactivates shop and field weld symbols, and specifies size and
related property values for shop welds.
2 ENDTYPE delimited text
Specifies the text value of the ENDTYPE property to indicate shop welds. Shop
welds are drawn for all Cnodes that have the specified property value. The
default is to draw weld dots if any character of the ENDTYPE property is a W.
The text value has a limit of two characters.

CREATE ISOMETRIC
2 OFF
Deactivates display of welds.
2 ON
Activates display of welds.
2 FIELDWELD x
Specifies size of field weld symbol. The field weld symbol is the weld dot with
an X through it. Field welds are drawn for all Cnodes that have the property
FITTYPE with a value of 70. The default is 0.25 drawing units for the X
symbol.
2 SHOPWELD x
(Default) Centers and fits the annotated, rescaled pipeline to 70 percent of the
available area of the view window. The specified maximum and minimum pipe
and fitting lengths are reduced or increased when this modifier is used.
Specifies diameter of a shop weld symbol. The default is 0.125 drawing units
for the dot symbol.
1 ZOOM
Specifies that the isometric drawing is zoomed to include all the continuing
fitting symbols and reference structure. This modifier increases the size of the
border between the view boundary and pipeline and pipe component extents,
and therefore decreases the scale of the generated pipeline isometric.
2 ON
Activates the zoom function.
2 OFF
(Default) Deactivates the zoom function.

CREATE ISOMETRIC
Procedure
To create a piping isometric drawing from a pipeline model.
1. Prepare the model by adding annotations and dimensions using the

DIMENSION ISOMETRIC and ANNOTATE ISOMETRIC commands.
2. Save the annotations and dimensions using the SAVE DIMENSIONS and
SAVE ANNOTATIONS commands.
3. Enter the command CREATE ISOMETRIC.
4. Specify additional modifiers, text, and numbers.
5. Press RETURN.
Example 1
#n# CREATE ISOMETRIC COMPNAME GLSC, GLSW HEIGHT.38 LENGTH.38
COMPNAME GLBV, GLBW HEIGHT.75 LENGTH,75

CREATE ISOMETRIC
Example 2
#n# CREATE ISOMETRIC FITTYPE.60 LENGTH.60 FITTYPE 11 HEIGHT.25
LENGTH.25

DELETE BEND
DELETE BEND
Description
Use this command to delete bends inserted into a pipeline, and reconstruct the
pipeline as it was before the bends were inserted. Any related graphics used for
detailing are also deleted with the bend.
Point entities created at the pipeline vertices when bends are inserted are not
deleted when the bends are deleted.
Bend Nlines must have a BRAD (bend radius) property. All other Nlines are
ignored.
Valid Modes
Model mode
Syntax
#n# DELETE BEND: getdata
DELETE BEND PLINE: MODEL ent <n1 n2...>
where n1 and n2 are piping networks that you have selected for deleting the bends.
Modifiers
1 PLINE
Deletes multiple bends in the selected piping networks.
Procedure
To delete bends,
1. Enter the command DELETE BEND and a colon.

2. The system prompts MODEL ent. Digitize the bends you want to delete.
3. Press RETURN.

DELETE BEND
Example
#n# DELETE BEND: MODEL ent d1 d2

DELETE FITTING
DELETE FITTING
Description
Use this command to remove fittings from a pipeline and reconstruct the pipeline
as it was before the fittings were inserted. Fittings include pipe fittings, such as
mitres and diffusers, as well as component fittings. Associated entities, such as
gaskets or joints, are also deleted.
Using this command, you can delete
Fittings or taps, singly, by group, assembly, or pipeline

Components, such as equipment
Nested nodal figures (without deleting the parent)
Parent nodal figures (and the nested nodal figures with it)
Detail graphics, there by restoring model graphics
A piping component must meet the following criteria to be deleted:
Components must have from one to five Cnodes, up to four of them associated
with external Nlines.
A Cnode can not be associated with more than two external Nlines or four
internal Nlines.
Pipes in and out of the fitting must be in the same direction.
The command reconstructs the pipeline as follows:
No fitting on either side of the deleted fitting causes the upstream pipe to extend
to the downstream pipe.
When the deleted fitting is at the front or back of a group, the pipe extends to
the next fitting in line in the group.
When the deleted fitting is in the middle of a group, a temporary pipeline is
created in its place. This is replaced by a real pipe when all the fittings on either
side of the temporary pipeline are deleted.
When a branch fitting is removed from a junction, a Cnode replaces it and the
pipes extend to the Cnode.
A change in diameter across a deleted fitting causes the upstream diameter to
continue downstream until another fitting, or the end of the pipe, is reached.

DELETE FITTING
Valid Modes
Model mode
Syntax
#n# DELETE FITTING [modifier]: getdata
Modifiers
The following diagram shows the flow of DELETE FITTING modifiers.
ALL
Deletes all the fittings on selected pipelines. Only pipes and bends are left.
CHILD
Deletes nested nodal figures (for example, a nozzle or a tap) without deleting
the nodal figures they are nested in.
DETAIL
Deletes the detail graphics and restores the model graphics for identified
fittings. When used in combination with ALL, all fittings on the selected
pipelines are processed.

DELETE FITTING
GROUP
Deletes a group of fittings. A group is made up of contiguous fittings and

associated entities (for example, gaskets, joints, and taps) bound externally by
pipe Nlines.
GROUP is not needed to delete an assembly or line attachment that was
automatically selected and inserted by INSERT FITTING. Selecting any fitting
in the assembly, such as a vent, deletes the entire assembly.
Procedure
To delete fittings and their related entities, and reconstruct the pipeline,
1. Enter the command DELETE FITTING and any modifiers you want.
2. Enter a colon. The system prompts MODEL ent. Select the fittings to be
deleted.
3. Press RETURN.
Example 1
When an eccentric reducer is deleted, a skew may be left in the line. A skew is a
Cnode that is out of line with preceding pipe sections, and is treated as follows.
If there are no fittings or nozzles and no corners downstream from the eccentric
fitting, the Cnode at the end of the pipeline is adjusted to eliminate the skew, and
the upstream pipe is extended to meet the Cnode.
#n# DELETE FITTING: MODEL ent d

DELETE FITTING
Example 2
If there are fittings or corners downstream from an eccentric fitting, the skew is
moved downstream until it meets a Cnode attached to a fitting, or it meets a corner
in the same direction as the skew.
If the Cnode is met first, the skew is left in front of the fitting. When you use the
REPORT PIPE command, the skew is reported.

DELETE FITTING
Example 3
If the corner is met first, the corner is adjusted, and any remaining downstream
fittings and corners are unchanged.

DELETE FITTING
Example 4
A temporary Nline is created when one member of a group is deleted.

DELETE FITTING
Example 5
Delete a group of fittings using the modifier GROUP. One selection deletes the
entire group.
#n# DELETE FITTING GROUP: MODEL ent d

DELETE FITTING
Example 6
Delete a line attachment in the same way you delete a group, by selecting one of
the attachments members. No modifier is required.

DELETE FITTING
Example 7
Separate two pipelines by a TERMNAM property. This property is attached to the
weldolet at the end of line 0-8247-8-B2F (see INSERT FITTING and the
NLABEL modifier).
#n# DELETE FITTING ALL: MODEL ent d

DELETE FITTING
Example 8
Use the CHILD modifier to delete a nozzle without deleting the parent nodal
figure.
#n# DELETE FITTING CHILD: MODEL ent d
Example 9
Use the DETAIL modifier to delete the detail graphics and restore the model entity.
#n# DELETE FITTING DETAIL: MODEL ent d

DELETE PENETRATION
DELETE PENETRATION
Description
Use this command to remove a penetration symbol from an isometric drawing.
You can also use it to reconstruct the pipeline as it was before the symbol was
inserted.
Valid Modes
Model mode
Syntax
#n# DELETE PENETRATION: getdata
Modifiers
The following diagram shows the DELETE PENETRATION modifier.
Procedure 1
1. Enter the command DELETE PENETRATION.
2. Enter a colon. The system prompts MODEL ent. Select the penetration(s) to
be deleted.
3. Press RETURN.
Procedure 2
To delete all penetrations from a pipeline,
1. Enter the command DELETE PENETRATION ALL.

2. Enter a colon. The system prompts MODEL ent. Select the pipeline on which
all penetrations are to be deleted.
3. Press RETURN.

Description
Use this command to delete an entire pipeline. Pieces of equipment at the origin or
terminus of a pipeline are recognized. They are not deleted.
Valid Modes
Model mode
Syntax
#n# DELETE PLINE: getdata
or
#n# DELETE PLINE LINENO delimited text
Modifiers
The following diagram shows the DELETE PLINE modifier. For a full explanation
of modifier diagrams see Modifier Diagrams in the Preface.
LINENO delimited text
Identifies the pipeline to delete. You can specify any subset of the fields in the
pipelines label as defined in the directory file, for example, CW-100. Only the
first pipeline found with the specified line number is deleted.

Procedure
To delete a pipeline by digitizing or specifying its line number,
1. Enter DELETE PLINE and LINENO text if you are identifying the pipeline by
number.
2. If you identify the pipeline by digitizing, enter a colon instead of the modifier.
The system prompts MODEL ent. Select the pipelines to delete.
3. Press RETURN.
Example
Delete a pipeline, but not the equipment at either end.
#n# DELETE PLINE: MODEL ent d

Description
Use this command to delete pipe support symbols from a pipeline and the
database.
Valid Modes
Model mode
Syntax
#n# DELETE PSUPPORT: getdata
Modifiers
The following diagram shows the DELETE PSUPPORT modifier.
Procedure 1
To delete a pipe support by selection,
1. Enter the command DELETE PSUPPORT

2. Enter a colon. The system prompts MODEL ent. Select the pipe support
symbol(s) to be deleted.
3. Press RETURN

Procedure 2
To delete all pipe supports from a pipeline,
1. Enter the command DELETE PSUPPORT ALL.

2. Enter a colon. The system prompts MODEL ent. Select the pipeline on which
all pipe support symbols are to be deleted.
3. Press RETURN
Please note: Pipe support symbols inserted as trunnions, that is, pipe support
symbols with the CONNECT modifier, will not be deleted with the modifier ALL.
These instances have to be selected explicitly.

DIMENSION ISOMETRIC
DIMENSION ISOMETRIC
Description
Use this command to automatically dimension a piping isometric drawing.
Dimension lines are drawn in a chain parallel to the pipe, valve, and fitting
symbols.
Witness lines are drawn to the center lines of tees, corners of elbows, and faces of
flanges and valves.
Dimension lines are automatically placed facing outwards from the center, to
reduce visual clutter. For non-orthogonal runs, a rectangle or box is constructed
and dimension lines are placed along the sides and are diagonal.
Specify default characteristics such as text height and position, dimension line and
arrowhead type, and units with the SELECT TEXT and SELECT DIMENSION
commands (see the online command reference documentation).
Important SELECT DIMENSION command modifiers are:
PROPERTY
Required before using the GENERATE or DIMENSION ISOMETRIC
commands. Specifies the use of XYZ properties, instead of current (unscaled)
part geometry, to calculate dimensions.
SOLID
Specifies a solid dimension line with text above it.
LOCATION AUTOCENTER
Automatically centers text.
TEXT FORMAT FEET&INCHES FRACTION OFFSET
Specifies a feet/inches fractional text format with the numerator and
denominator of the fraction aligned horizontally.
NOCHECK
Prevents text from automatically flipping to the side of the dimension line when
there is not enough room in the middle.

DIMENSION ISOMETRIC
Before using GENERATE or DIMENSION ISOMETRIC, save the dimensions

you created by specifying the SAVE DIMENSIONS command.
Please note: A set of multiple interconnected pipelines can be dimensioned

as long as there are no TERMNAM properties separating the pipelines. The
different lines are defined by their unique line numbers.
Valid Modes
Model mode
Syntax
#n# DIMENSION ISOMETRIC
Modifiers
None
Procedure
To use the DIMENSION ISOMETRIC command,
1. Extract a pipeline from an Explicit Modeling model, using the CONSTRUCT

PLINE PROCEDURE command. File the extracted pipeline as a separate part.
2. Save the original model dimensions using the SAVE DIMENSIONS command.
3. Create an isometric drawing, without dimensions, using the GENERATE
ISOMETRIC command.
Perform any necessary edits to the drawing before dimensioning it.
4. Establish dimensioning parameters with the SELECT DIMENSION
PROPERTY command, along with any other dimensioning modifiers you want
to use to change the appearance of the dimensions. For example:
#n# SELECT DIMENSION PROPERTY SOLID PRECISION 8 TEXT
FORMAT FEET&INCHES FRACTION OFFSET LOCATION
AUTOCENTER NOCHECK
5. Enter DIMENSION ISOMETRIC.
6. Press RETURN.
The piping is automatically dimensioned.

DIMENSION ISOMETRIC
Example
Generate an isometric drawing of line O-8242 (from the CVPDC plant model).
The GENERATE ISOMETRIC command has already been used in the BEFORE
figure. Now set the text and dimension parameters.
Set text with the INSERT TEXT command. The dimension parameters are set as
follows:
#n# SELECT DIMENSION PROPERTY PRECISION 8 TEXT FORMAT FEET&INCHES
FRACTIONS OFFSET LOCATION AUTOCENTER NOCHECK
This is one of many combinations of selections.
Enter DIMENSION ISOMETRIC and press RETURN.
The system responds with the messages

(tracing pipeline)
(checking pipeline)
(dimension pipeline)
ARROWS FLIPPED TO INSURE VALID DIMENSION

DIMENSION ISOMETRIC
Dimensioning is accomplished as in the AFTER figure.

DIMENSION ISOMETRIC
Notes
The DIMENSION ISOMETRIC command does not dimension across fitting
groups correctly. Use the dimensioning capabilities of ANNOTATE ISOMETRIC
instead.

DIMENSION PIPE
DIMENSION PIPE
Description
Use this command to generate dimensions along a pipeline automatically. The
dimensions are created along the selected pipelines based on the specified criteria.
You can specify the pipeline to be dimensioned by its label or by graphically

selecting it. The selected pipeline is traced from the start point to the end point and
the dimensions are generated.
You can specify the location of the dimension text by either selecting a location or
by specifying its distance from the selected pipeline.
Valid Modes
Draw mode and Model mode
Syntax
#n# DIMENSION PIPE [modifiers]: getdata
Modifiers
The following diagram shows the flow of DIMENSION PIPE modifiers. An
see Modifier Diagrams in the Preface.
follows.

DIMENSION PIPE
DISTANCE x
(Default) Specifies the distance of the dimensions from the pipeline segment. It
is specified in current drawing units. The default is 10 mm. This modifier is
mutually exclusive with LOCATION modifier.
Identifies the pipeline to be dimensioned. You can specify any subset of the
fields in the pipelines label as defined in the directory file by the
LINENO-FORMAT, for example, CW-100. Only the first pipeline found with
the specified line number is dimensioned.
LOCATION
Indicates that the dimension is created at the graphically selected location. The
command highlights two points between which the dimension is to be generated
and you are required to select a point to specify the location of the dimension. If
you do not want dimensions for a specific pipe segment, press BACKSPACE or
DELETE and that particular segment is not dimensioned. This process
continues along the entire length of the pipeline. This modifier cannot be used
with the DISTANCE modifier.
Procedure 1
To dimension a pipe by selecting it,
1. Enter DIMENSION PIPE.

2. Specify the modifiers you want to use.
3. Enter a colon.
4. The system prompts PIPELINE MODEL ent.
5. Select the pipeline to be dimensioned.
6. Press RETURN.
Procedure 2
To dimension a pipe identified by its line number,
1. Enter DIMENSION PIPE.

3. Enter a colon and VIEW.
4. Select the view in which the pipeline is to be dimensioned.
5. Press RETURN.

DIMENSION PIPE
The selected pipeline is dimensioned. The dimensions are created as specified by

the modifiers DISTANCE or LOCATION.
When you select the LOCATION modifier, the system prompts you for the
locations for creating dimensions for each pipe segment. If you do not want
dimensions for a specific pipe segment, press BACKSPACE or DELETE. This
process is repeated for the entire length of the selected pipeline.

DIMENSION PIPE
Example 1
This example illustrates dimension generation for a pipeline. The distance of the
dimensions generated is, by default, 10 mm from the pipeline.
#n# DIMENSION PIPE: PIPELINE MODEL ent d

DIMENSION PIPE
Example 2
This example illustrates dimension generation for a pipeline. The distance of the
dimensions generated is 6 drawing units from the pipeline.
#n# DIMENSION PIPE DISTANCE 6: PIPELINE MODEL ent d

DIMENSION PIPE
Example 3
In this example the dimensions are generated specified by graphical selection.
#n# DIMENSION PIPE LOCATION: PIPELINE MODEL ent d1
(tracing pipeline)
>> Horizontal Dimension : DRAW loc d2
>> Vertical Dimension : DRAW loc DELETE
>> Vertical Dimension : DRAW loc d4
>> Vertical Dimension : DRAW loc d6

DIMENSION PIPE
Note that the dimension for the second segment is not created as the DELETE key
is used.

DIMENSION PIPE
Example 4
This example illustrates dimension generation for a pipeline specified by its line
number.
#n#DIMENSION PIPELINENO AA-02 : view d

DIMENSION PIPE
OR
#n# DIMENSION PIPELINENO AA-02: view DRAW PSPOOL

DRAW PSPOOL
DRAW PSPOOL
Description
DRAW PSPOOL command allows you to automatically generate pipeline spool
drawings by reading the pipeline spool information and additional project related
information from the specified external RDBMS tables.
The automatically generated pipeline spool drawings include the following details:
General project information

Top, front, right and isometric view of the pipeline spool or any combination of
these views as specified by the user.
Dimensions and annotations.
Component listing of the pipeline spool
Spool fabrication information
Pipe bending information for all the bends
Flange bolt hole straddle information
Terminal connection information
Use this command to
Establish and retain the connection to the external RDBMS tables.

Disconnect from the external RDBMS after the required operations have been
completed.
Select the appropriate external RDBMS tables for processing the pipeline
spool drawing generation by specifying an assembly name in the existing
hierarchical Project Component tree structure that is used to organize project
data in external RDBMS tables. Refer Appendix B, AEC Project Component
Table
Generate pipeline spool drawing with double line representation and optionally
represent the hidden portion of the pipes and piping components using dashed
line of specified length and spacing.
Generate pipe bending information for all the pipe bends.
Specify the units of RDBMS table fields and units of the parameters that appear
in the drawing.
Create fabrication drawings using the pipe bending information for all the pipe
bends.

DRAW PSPOOL
Create annotations for components in the fabrication drawing and generate the
detailed dimensioning for the drawing.
Specify a customizable form part as the template for the drawing generation.
Specify a CADDS drawing name and an optional extension number, and save
generated spool drawings as CADDS drawings using automatically generated
CADDS drawing names. Additional CADDS drawing names as required are
generated by incrementing the extension number.
Output the spool drawings directly to a specified printing device.
Create CGM (Computer Graphics Metafile) files of the generated spool
drawings for subsequent processing.
This command must be issued from an active CADDS part. For each pipeline
spool extracted and stored in the external RDBMS tables, a separate spool
drawing is generated by this command. Depending on the form part specified, the
active CADDS drawing accommodates one or more spool drawings.If the number
of spool drawings generated exceeds the number of slots in the active CADDS
drawing, the command either automatically reuses the currently active drawing or
generates a new active CADDS drawing based on the modifiers you specify.
Before using this command, you must properly set up the RDBMS related
environment variables and the necessary project application tables as described in
Appendix B, RDBMS Environment Variables Setup. You must also specify the
required units for various parameters, units of various fields of the standard library
tables, and the conversion factors for converting from one unit to another, in the
following tables.
AEC Measurement Units Conversion Table. Refer to Appendix B, AEC
Measurement Unit Conversion Table for more details.
AEC Measurement Units Dictionary Table. Refer to Appendix B, AEC
Measurement Unit Dictionary Table for more details.
AEC Measurement Unit Name Dictionary Table. Refer to Appendix B, AEC
Measurement Unit Name Dictionary Table for more details.
The pipeline spool data for generating the drawings are read from the external
RDBMS tables generated by the GENERATE PIPEDBASE command.
Apart from specifying the pipeline spools to be processed, you must also make
available the Piping standard library data in the following external RDBMS tables.
Piping coordinate information table

Piping drawing information table
Pipeline information table

DRAW PSPOOL
Pipe specification table

Pipe fabrication material table
Refer, Appendix B, Piping Standard Library RDBMS Tables for the table
structure details of the above standard tables.
The various script files to establish the necessary project information and Piping
RDBMS table formats should be run from the following directories,
/usr/apl/cadds/data/cvaec/dbms/scripts
/usr/apl/cadds/data/cvpd/scripts/
A set of standard library tables pertaining to Piping application is supplied with the
package. The supplied RDBMS tables can be edited to add additional data or
modified to suit your requirement, using the SQL commands of an RDBMS
software.
Valid Modes
Model mode
Syntax
DRAW PSPOOL USER <user_name> PASSWORD <password> ASSEMBLY
<assembly> FORMPART <part> FORMDRAW<drawing> DRAWNAME
<drawing> ALL [modifiers] <CR>
or
<assembly> FORMPART <part> FORMDRAW <drawing> DRAWNAME
<drawing>LINENO <line_nos> SPOOLNUM <spool_nos> [modifiers]
or
DRAW PSPOOL ASSEMBLY <assembly> FORMPART <part> FORMDRAW <drawing>
DRAWNAME <drawing> LABELFILE <filename>
or
DRAW PSPOOL DISCONNECT <CR>

DRAW PSPOOL
Modifiers
The following diagram shows the flow of DRAW PSPOOL modifiers. For a full
explanation of modifier diagrams, see the Preface.

DRAW PSPOOL
The modifiers are listed alphabetically within each logical grouping. The number
on the left indicates the modifier's level.
1 ALL flag
Specifies that all the pipeline spool labels from the specified external RDBMS
table are selected for spool drawing generation. The RDBMS table is identified
by the assembly name in the Project Component tree structure as specified by
the ASSEMBLY modifier. This modifier is mutually exclusive with the
LINENO modifier and LABELFILE modifiers.
1 ASSEMBLY assembly_name, limit=40
Specifies the assembly name that determines the names of RDBMS tables from
which the pipeline spool drawing generation is processed. The specified
assembly name should be available in the Project Component tree structure and
should be associated to the pipeline list and element RDBMS tables which are
described in Appendix B, Pipeline List Table and Appendix B, Pipeline
Element Table . This modifier is mandatory.
1 DISCONNECT flag
Specifies that the connection to the external RDBMS tables will be terminated
after the current command is executed. By default, the existing connection will
be retained for further operations. This modifier is mutually exclusive with
USERNAME modifier.
1 DOUBLE flag
Specifies that the pipeline spool drawings are generated using the double line
representation, with or without the hidden lines. By default, pipeline spools are
generated using the single line representation.
For pipe spool drawings with double line representation, you can create center
lines using the GENERATE CLINE command. Optionally you can draw hidden
lines with dashed line fonts of specified length and spacings using the following
submodifiers.
2 DASH flag
Specifies that the hidden portion of the pipeline and the components in the
pipeline spool fabrication drawing will be represented using dashed lines. The
default font is DASH with its default dash length and spacing. You can change
the dash line length and spacing using the following submodifiers.

DRAW PSPOOL
3 DLEN length
Specifies the dash length in absolute drawing units in order to represent the
hidden portion of the pipeline and its components. The default value is the
equivalent of 0.25 inches in the current drawing units.
3 SLEN length
Specifies the inter-dash length in absolute drawing units, in order to represent

the hidden portion of the pipeline and its components. The default value is the
equivalent of 0.25 inches in the current drawing units.
1 DRAWNAME drawing_name, limit=12, noname
Specifies the name of the CADDS drawing to be created and activated in the
current CADDS part for pipeline spool drawing generation.The created
CADDS drawing is based on the drawing template stored in the form part, as
specified by the FORMPART modifier and referred by the corresponding
FORMDRAW modifier. For details refer to Appendix C, Spool Fabrication
Drawing Form Part. This is a NONAME modifier.
Drawings created can be saved using the SAVEDRAW sub-modifier. If the
SAVEDRAW modifier is selected, drawing names are automatically generated
as <drawing_name><n>, <drawing_name><n+1>, and so on, where
<drawing_name> is the specified drawing name and <n> is the starting number
as specified by the sub-modifier EXTENSION.
Any existing drawing in the currently active CADDS part matching the
generated drawing names is overwritten.
2 SAVEDRAW flag
Specifies that the CADDS drawings created during the pipeline spool drawing
generation are to be saved in the currently active CADDS part. If this modifier
is not used, then a drawing with the name as specified by the higher level
DRAWNAME modifier is created and overwritten until all of he pipeline spool
drawings are generated and displayed. If this modifier is not specified, then you
can not save the individual spool drawings.
3 EXTENSION n
Specifies the starting number for generating unique CADDS pipeline spool
drawings. The first drawing name is generated by appending the specified
extension number to the drawing name as specified by the higher level
DRAWNAME modifier.

DRAW PSPOOL
Subsequent drawing names, are generated by incrementing the specified

extension number by 1 and appending it to the specified drawing name. The
default value for this modifier is 1.
For example, if the specified value for DRAWNAME modifier is PSPOOL
and that for EXTENSION is 4, then the automatically generated unique
CADDS drawing names in the currently active part are PSPOOL4,
PSPOOL5, PSPOOL6 and so on.
1 FORMPART formpart_name, limit=72
Specifies the name of the form part that contains the CADDS drawing to be
used for the pipeline spool drawing generation. You must specify this modifier,
else the command terminates with an error message.
Please refer the Piping UG for the instructions on form part preparation for
pipeline spool fabrication drawings.
2 FORMDRAW formpart_draw_name, limit=12
Specifies the name of the form part drawing stored in the CADDS part as
specified by the higher level modifier FORMPART. You must specify this
modifier, else the command terminates with an error message.
1 LABELFILE label_list_file_name, limit=72
Specifies the file name, which contains a list of all the spool labels to be
processed for spool drawing generation.This file can be manually created using
a text editor or automatically generated using the REPORT PIPE command and
suitably edited. This modifier is mutually exclusive with the ALL and LINENO
modifiers.
1 LINENO pipe_lineno, limit=40, list=10

Identifies the pipelines to be selected for drawing generation by their line
numbers. Enter the complete pipeline label or a subset of the fields in the
pipeline label, as specified in the LINENO-FORMAT field of the currently
active directory file. You can enter multiple line numbers separated by comma.
A maximum of 10 pipeline numbers can be specified.
The SPOOLNUM sub-modifier can be used to explicitly specify the pipeline
spools of the selected pipelines for processing.
This modifier is mutually exclusive with the ALL and LABELFILE modifiers.

DRAW PSPOOL
2 SPOOLNUM spool_number, limit=40, list=10
Specifies a pipeline spool number or a list of pipeline spool numbers for

drawing generation from pipelines selected by the LINENO modifier.
1 PAUSE flag
Specifies that the spool drawing generation process pauses for User interaction
after each drawing is generated. The system displays the prompt Issue Zoom
Options or Hit Carriage Return to Continue or Control E to Terminate: and
waits for your input. You can use the draw mode zoom options like ZOO,
ZOOM ALL and so on, to visually check the correctness of generated spool
drawings. On completion of visual checking, you can press RETURN to
continue the spool drawing generation process or press Control E to
terminate the spool drawing generation.
If spool drawing generation is continued, either a new drawing is activated or
the current drawing is overwritten, based on the DRAWNAME and
SAVEDRAW modifiers specified.
If this modifier is not used, then you can not get access to the draw mode zoom
options and the drawing generation process completes without a pause.
1 PLOT flag
Specifies that the generated pipeline spool drawings, in the currently active
CADDS drawing are output to a disk file or to a default device, based on the
DISKFILE or DEVICE destination sub-modifiers.
If none of the above destination sub-modifiers are selected, the default plot
output is written to a disk file in the CGM format. The disk file name is derived
by appending .cgm to the name of the currently active drawing.
2 DEVICE device_name, limit=12
Specifies the name of the plotting device for plotting the currently active
CADDS drawing. By default, drawings are output to a disk file if this modifier
is not selected. This modifier is mutually exclusive with the DISKFILE
modifier.
3 ROTATE flag
Specifies that the drawing is rotated by 90 degrees before being sent to the
output device as specified by the DEVICE modifier.

DRAW PSPOOL
2 DISKFILE diskfile_name, limit=72
Specifies the output file name for saving the graphics data of the active drawing
in the CGM format for subsequent plotting. The drawing can be plotted from
this file using the PLOT DRAW command. This modifier is mutually exclusive
with the DEVICE modifier.
This is the default modifier. If both the DEVICE and DISKFILE modifiers are
not selected, the default plot output is written to a disk file in the CGM format.
The disk file name is derived by appending ".cgm" to the name of the currently
active drawing.
This default mode is useful for processing single drawings one at a time. If
multiple drawings are processed, User should take care to specify the
SAVEDRAW and EXTENSION modifier to save the individual drawings under
unique disk file names. Otherwise drawings are over written and only the last
processed drawing are saved in the default .cgm file.
2 LAYER layer_name, copies=32
Maps the specified layer to a color index as specified by the sub-modifier

COLORINDEX. All the entities on the specified layer are plotted using the
color specified by COLORINDEX. The LAYER and COLORINDEX modifiers
must be used together.
3 COLORINDEX n
Plots all entities on the layer specified by the higher level modifier, LAYER
with the color value specified by <n>. On pen plotters, this number corresponds
to a pen number. The LAYER and COLORINDEX modifiers must be used
together.
2 QUALITY n
Specifies the relative resolution for stroking arcs and circles in the plotted
output.
Permissible integer values are 8-24, with 8 representing the coarsest resolution
and 24 the finest. The default value is 12.
1 USERNAME oracle_database_username, limit=30
Specifies the user login name for connecting to the external RDBMS software.
This modifier must be used with the PASSWORD sub-modifier once to
establish the RDBMS connection. The established connection is retained for
further RDBMS operations till it is terminated using DISCONNECT modifier.

DRAW PSPOOL
2 PASSWORD oracle_database_password, limit=30
Specifies the password for accessing the external RDBMS software for an
authorized user as specified by the USERNAME modifier. This modifier must
be used with the USERNAME modifier once to establish the RDBMS
connection. The established connection is retained until it is disabled using the
DISCONNECT modifier.
Reporting the Data for Spool Drawings in the Form

Part
The following sections explain how to obtain reports for the pipe spool drawings
in a form part.
Reporting the Flange Rotation Angle for the Pipe Spools

You can obtain the flange rotation angle of the pipe spool in the bend table of the
spool drawing before starting the bending operations.
The flange rotation angle is a relative axial angle between the hole configuration of
flanges that are welded on both ends of the pipe spool before starting the bending
operation.
To obtain the flange rotation angle report, you must create a form part. To create a
form part, see Appendix C, Spool Fabrication Drawing Form Part.
Procedure : To obtain a report of the flange rotation angle in spool drawings:
1. Assign a value of 2011 to the DWGOBJATTR property of the Tnode.

2. At the command line, use the DRAW PSPOOL command as follows to obtain
the flange rotation angle report in the NC bending information table of the
spool drawing.
<assembly> FORMPART <part>
The flange rotation angle is reported in the NC bending information table of the
spool drawing.
Example: The next example shows how you can obtain the flange rotation angle
of the pipe spools before the bending operations.

DRAW PSPOOL
Figure 2-1 Step 1:Two Flanges at Both Ends of the Spool.
Figure 2-2 Step 2: Flange B Is Moved Axially Upward from the Pipe Bend.

DRAW PSPOOL
Figure 2-3 Step 3: Flange B Is Moved Along the Centerline of the Pipe Bend.
Figure 2-4 Step 4: Flange B Is Moved Along the Pipe Bend.

DRAW PSPOOL
Figure 2-5 Step 5: Flange B Is Moved Along the Pipe Toward the Other Flange.
Figure 2-6 Step 6: Flange B Hole Configuration Is Projected on Flange A Plane, in 45

Degrees in This Case.
Reporting the Rotation Angle for Pipe Spool Bending

You can obtain a report of the rotation angle for each bending operation for the
pipe line spools in the forward or reverse direction. You can also start a bending
operation in the reverse direction of the spool in the spool drawings.
To obtain a report of the axial rotation angle for pipe bending, you must create a
form part. To create a form part, refer to Appendix C, Spool Fabrication Drawing
Form Part.

DRAW PSPOOL
Procedure: To obtain a report of the axial rotation angle for pipe bending in the
form part:
1. Assign a value of 2008 to the DWGOBJATTR property of the Tnode to report the
axial rotation angle in the forward direction.
2. Assign a value of 2039 to the DWGOBJATTR property of the Tnode to report the
axial rotation angle in the reverse direction.
the rotation angle in the forward and reverse directions:
Example : The following example shows how you can obtain the axial rotation
angle for pipe spool bending:
Figure 2-7 Required Spool.
Figure 2-8 Step 1: Bend the Pipe Spool Through 90 Degrees
Figure 2-9 Step 2: Rotate the Pipe Spool Axially Through 90 Degrees to Change the Plane
of Bend Before the Next Bend

DRAW PSPOOL
Figure 2-10 Step 3: Bend the Pipe Spool Through 90 Degrees
Figure 2-11 Step 4: Rotate Assembly Through 90 Degrees in the Reverse Direction
Labeling Pipe Parts in Spool Drawing

You can label spool elements with serial numbers in the isometric view of the
spool drawings form part. The serial numbers assigned to the spool elements are
reported in the spool element table.
To label the spool elements with serial numbers, you must create a form part. For
more information on creating a form part, refer to Appendix C, Spool Fabrication
Drawing Form Part.
Procedure: To label the spool elements with serial numbers in the form part, at
the command line, use the DRAW PSPOOL command as follows to view the
labeled spool elements in the isometric view:
DRAW PSPOOL USER <user_name> PASSWORD <password> ASSEMBLY <assembly>
FORMPART <part>

DRAW PSPOOL
Figure 2-12 The Spool Elements Now Have Serial Numbers.
Matching Serial Numbers and the Contents of the Table

in the Form Part
You can match the serial numbers of spool elements with the serial numbers in the
spool element data table. You can also match bend operations serial numbers for
the spools with bend operations in the bend data table in the spool drawing. You
do not need to manually assign serial numbers in the form part.
To match serial numbers for spool elements and bend operations, you must create
a form part. For more information on creating a form part, refer to Appendix C,
Spool Fabrication Drawing Form Part.
Procedure : To match the serial numbers of the spool elements and the serial
numbers in the spool element data table:
1. Assign a value of 2040 to the DWGOBJATTR property of the Tnode to match the
serial numbers of spool elements in the spool data table.
2. Assign a value of 2041 to the DWGOBJATTR property of the Tnode to match the
serial numbers of bend operations in the bend data table.
3. At the command line, use the DRAW PSPOOL command as follows to obtain a
report of the serial numbers:

DRAW PSPOOL
Reporting the Bending Location of the Pipe Spools

During Pipe Bending
You can specify the bend location for the spool according to the elasticity property
of the pipe material to avoid incorrect pipe bends during a bend operation.
During bend operations, when the bending force is relieved, the pipe material does
not revert to its original position but gains a springback, as shown in the next
figure.
Figure 2-13 The Pipe Is Elongated When the Bend Force Is Relieved.
To avoid elongation and springback of the pipe material during bend operations,
specify the bending length value and the cutting length value for pipe bends during
bend operations.
The location of the bending length and cutting length files are specified in the
PMANUFACTURE file. The PMANUFACTURE file contains the CUTTING_LENGTH
and BENDING_LENGTH variables as keywords, which specify the location of the
cutting and bending length files. The location of the PMANUFACTURE file is
specified in the directories file with a keyword, PMANINFO.
The following warning message is displayed if you do not specify the correct
keywords, file location, and values.
Unable to extract data from the cutting and bending length file for
the size and specification material.
Please note: The elongation and springback of the pipe material is not
considered if you receive this warning message.

DRAW PSPOOL
The following table shows the cutting length and bending length files as viewed in
the PMANUFACTURE file.
File Type Description

CUTTING_LENGTH Cutting length table file name. For example,
CPVD.M.SPEC.CUTTING-LENGTH-A-IN
BENDING_LENGTH Bending length table file name. For example,
CVPD.M.SPEC.BENDING-LENGTH-A-IN
The bending length table defines the bending length for the pipe size, bend radius,
and bend angle. You can specify the bending length for different pipe sizes, bend
radii, and bend angles in various combinations in the bending length table for the
selected pipe material.
Table 2-1 Combinations of Bend Radius and Bend Angles in the Bending Length Table
Field Name Description

Size The nominal diameter
Radius Bend angle
5 Bend angle of 5 degrees
The cutting length table defines the cutting length for pipe size, bend radius, and
bend angle. You can specify the cutting length for different pipe sizes, bend radii,
and bend angles in various combinations in the cutting length table for the selected
pipe material.
Table 2-2 Combinations of Bend Radius and Bend Angles in the Cutting Length Table
Field Name Description

Size The nominal diameter
Radius Bend angle
Please note: The cutting length and the bending length table contain
additional information about units.

DRAW PSPOOL
Figure 2-14 Cutting Length and Bending Length for a Pipe Bend
To obtain the bend location of the pipe spools during a bend operation, you must
create a form part. To create a form part, refer to Appendix C, Spool Fabrication
Drawing Form Part.
Procedure : To obtain the bend location with elasticity allowance of the pipe
material:
1. Assign a value of 2007 to the Tnodes that have the DWGOBJATTR property for
the forward bend direction.
2. Assign the value of 2042 to the Tnodes that have the DWGOBJATTR property for
the reverse bend direction.
the bend location of each bend of the pipe spools in the bend data table.
<assembly> FORMPART <part> ALL
Reporting the Installation Position

You can locate the installation position and assemble the spools of the pipeline on
the ship with the help of the installation position specified in the spool drawing.

DRAW PSPOOL
You can locate the installation position and assemble the spools either in the ship
coordinate system or the Cartesian coordinate system.
To report the installation position, you must create a form part. To create a form
part, refer to Appendix C, Spool Fabrication Drawing Form Part.
Procedure : To locate and assemble the spools with respect to the ship assembly
in the Cartesian coordinate:
1. Assign the value of 2019 to the DWGOBJATTR property of the Tnode in the form
part for the x-coordinate of the spool piece.
2. Assign the value of 2020 to the DWGOBJATTR property of the Tnode for the
y-coordinate of the spool piece.

DRAW PSPOOL
3. Assign the value of 2021 to the DWGOBJATTR property of the Tnode for the
z-coordinate of the spool piece.
Procedure : To locate and assemble the spools with respect to the ship assembly
in the ships coordinate system:
1. Assign the value of 2043 to the DWGOBJATTR property of the Tnode in the
longitudinal ship direction.
transverse ship direction.
vertical ship direction.
4. Use the DRAW SPOOL command as follows:
The DRAW SPOOL command reads the starting position of each spool in the main
ship assembly. The starting position of each spool in the main ship assembly is
reported in the spool drawings.
Reporting the Extra Clamp Length Required

Sufficient clamp length must be available for the start and end bending operations.
You can obtain the information of the extra pipe length required if the modeled
length of the last pipe segment is less than the required minimum clamp length.
Procedure: To obtain information about the extra pipe length required:
1. Specify the values for the pipe size, bend radius, minimum angle and maximum
angle for the pipe bends in the BEND_FILE.
2. Specify the values for the pipe size, start clamp length, mid-clamp length and
end clamp length for pipe bending in the BEND_MACHINE_FILE.
The location of BEND_MACHINE_FILE and BEND_FILE is specified in the

PMANUFACTURE file. The PMATINFO has a pointer to the PMANUFACTURE file,
which is set in the directories file.
Use the DRAW PSPOOL command as follows:

DRAW PSPOOL USER <user_name> PASSWORD <password> ASSEMBLY <assembly>
FORMPART <part>

DRAW PSPOOL
The start and end clamp length specified by you in the PMANUFACTURE file is
compared to the available length of the pipe. If the modeled length is less than the
predefined minimum clamp length, the extra length is shown by a dotted extension
line in the spool drawings along with the required dimension.
The extra clamp length is reported in the element table in the form part.
Please note: The extra length is shown by a dotted extension line in the spool
drawings along with the required dimensions only in the front view.
Example : The following example demonstrates how the routed model spool is
displayed in different views:
Figure 2-15 The Required Routed Model Spool.
The next figure shows the spool parts labeled in the ISO view of the spool
drawings.
Number 1 and 5 labels indicate that the spool is shorter than the required clamp
length. The extra required clamp length is shown on both ends of the spool in the
spool drawing. Specify the extra clamp depending on which side you want to start
the bending operation.

DRAW PSPOOL
Figure 2-16 Spool Is Shorter Than the Required Clamp Length.
Figure 2-17 Top View of the Spool in the Spool Drawing
Figure 2-18 Extra Length is shown by a Dotted Extension Line in the Spool Drawing in the
Front View.

DRAW PSPOOL
Figure 2-19 Right View of the Spool in the Spool Drawing.
Procedure 1
You must carry out the following steps before you are ready to invoke the DRAW
PSPOOL command.
1. Set up the RDBMS environment variables as explained in the Appendix B,

RDBMS Environment Variables Setup.
2. Create the project information tables as explained in the Appendix B, Project
Information Tables.
3. Create the piping standard library RDBMS tables as explained in Appendix B,
Piping Standard Library RDBMS Tables.
4. Create the pipeline spool and element tables as explained in Appendix B,
Pipeline RDBMS Tables.
5. Create the units related tables and fill in the units of fields of the pipe element
table in the AEC Units Dictionary Table and specify the conversion factors in
the AEC Measurement Unit Conversion Table as explained in Appendix B,
Project Information Tables
6. Create the pipeline spool fabrication drawing form part, as explained in the
Appendix C, Spool Fabrication Drawing Form Part
7. Activate the part and appropriate drawing in which the pipeline model exists.
8. Link the part with a project by specifying the project name in SELECT
RDBMS command as explained in Appendix B, Piping RDBMS Tables
9. Select the directory file which defines the SPOOL field in the LABEL format,
using the SELECT PARAMETERS PIPING command.
10. Generate the spool labels using GENERATE SPOOL command with
NOLEGEND modifier. Alternatively you can also generate the spool labels
without the NOLEGEND modifier and unblank the blanked pipeline spool
labels.
11. Extract the pipeline spool information and store them into the external RDBMS
tables using the GENERATE PIPEDBASE command.
12. Disable the drawing generation status for pipeline spools which you want to
exclude from the drawing generation process, if required.

DRAW PSPOOL
13. Activate the part in which you want to create the pipeline spool fabrication
drawings and link this part to the same project name, which was used in
pipeline database extraction above.
14. Select the same directory file as explained in the step 8 above.
15. Setup the text parameters for the dimension text using SELECT MODE
DRAW and SELECT TEXT command.
Using the pipeline spool information stored in the external RDBMS tables, you
can generate the pipeline spool fabrication drawings automatically, using the
below explained procedure.
Procedure2
To create pipeline spool fabrication drawings and save them for review before
plotting them,
1. Enter DRAW PSPOOL command.

2. Specify the user name and password for logging to the external RDBMS, if the
external RDBMS connection does not exist.
3. Specify the existing assembly name, with which the required pipeline spool
information is associated.
4. Specify the form part name and form part drawing name.
5. Specify the drawing name, save option and drawing extension number.
6. Specify the selection for pipeline spool drawing generation, either all the
pipeline spools from the external RDBMS tables, or only pipeline spools
specified by the line numbers and spool numbers or a list of line numbers
through a text file.
7. Specify the double line option and dashed hidden line options and pause option
if required.
8. Press RETURN.
Procedure 3
To create pipeline spool fabrication drawings and plot them directly,
1. Enter DRAW PSPOOL command.

2. Specify the user name and password for logging into the external RDBMS, if
the external RDBMS connection does not exist.
3. Specify the existing assembly name, with which the required pipeline spool
information is associated.
4. Specify the form part name and form part drawing name.

DRAW PSPOOL
5. Specify the drawing name

6. Select the plot option and specify the plotting device name and other plotting
options as required.
7. Specify the double line and dashed line hidden options if required.
8. Specify the selection for pipeline spool drawing generation, either all the
pipeline spools from the external RDBMS tables, or only pipeline spools
specified by the line numbers and spool numbers or a list of line numbers
through a text file.
9. Press RETURN.
Example 1
Creating spool fabrication drawing:
The figure shown above is the original model in which the pipeline TEST-01 has
been split into various spools using GENERATE SPOOL command. GENERATE
PIPEDBASE command must be run for all the spools before invoking DRAW
PSPOOL command.
DRAW PSPOOL psdraw SAVEDRAW EXTENTION 100 ASSEMBLY stage-01
USERNAME user1 PASSWORD ***** FORMPART cvpd.spool.form.a4x1
FORMDRAW A ALL <CR>

DRAW PSPOOL
This example explains creation of pipeline spool drawings in the currently active
part, for all the pipeline spools in the pipeline list and element external RDBMS
tables, associated with the specified assembly name STAGE-01. The automatically
generated CADDS drawings are named as psdraw100, psdraw101, etc. and are
saved in the current part.

DRAW PSPOOL
The following message is displayed.
Processing project "DEMO", assembly "STAGE-01"
Creating Pipe Spool TEST-01-SPOOL#1 in drawing psdraw100

DRAW PSPOOL
Spool TEST-01-SPOOL#4 has been disabled for drawing generation
Spool TEST-01-SPOOL#6 has been disabled for drawing generation
Note that the SPOOL#4 and SPOOL#6 are disabled from drawing generation.
Also note that drawing numbering sequence is not interrupted by the disabled
drawings.
Example 2
DRAW PSPOOL pspdraw ASSEMBLY block1 USERNAME user1 PASSWORD *****
FORMPART cvpd.spool.form.a4x1 FORMDRAW A LINENO O-8241 SPOOL SP1
DOUBLE <CR>
This example explains creation of a pipeline spool drawing in the currently active
part, for the spool identified by the numberSP1, belonging to the pipeline
identified by the line number O-8241. The spool drawing is created in a CADDS
drawing with the name dspdraw1 based on the information available in the
pipeline list and element RDBMS table, associated with the specified assembly
name BLOCK1.
Note that the pipeline has been represented using double line, since the modifier
DOUBLE has been specified.

DRAW PSPOOL
Creating Pipe Spool O-8241-SP1 in drawing psdraw

DRAW PSPOOL
Example 3
DRAW PSPOOL pspdraw ASSEMBLY stage-01 USERNAME user1 PASSWORD
***** FORMPART cvpd.spool.form.a4x1 FORMDRAW A LINENO TEST-01
SPOOL SPOOL#1 PLOT DEVICE CGMP QUALITY 18 <CR>
This example explains creation of a pipeline spool drawing in the currently active
part, for the spool identified by the numberSPOOL#1, belonging to the pipeline
identified by the line number TEST-01. The spool drawing is created in a
CADDS drawing with the name dspdraw1 based on the information available in
the pipeline list and element RDBMS table, associated with the specified assembly
name STAGE-01. The created drawing is sent to the plotting device CGMP with
the specified quality level.
Creating Pipe Spool TEST-01-SPOOL#1 in drawing psdraw
Plot sent to spooler
Notes
1. The number and type of views that appear in the pipeline spool drawings
generated by DRAW PSPOOL command depends on the form part and form
part drawing specified. The method of controlling the views while preparing the
form part has been discussed in detail in Appendix C, Spool Fabrication
Drawing Form Part.
2. The part in which DRAW PSPOOL command is run, must be linked to the same
project, to which the original CADDS part is linked. Based on the projected
name, the names of the project tables and piping tables are identified for reading
the project related information and pipeline spool information.
3. If NODRAW modifiers had been specified while extracting information of a
pipeline spool using GENERATE PIPEDBASE, then drawing is not generated
for that spool. In order to revoke the drawing status, user must activate the
original CADDS model and run GENERATE PIPEDBASE command for that
spool with the DRAW modifier in conjunction with the OVERWRITE modifier.

DRAW PSPOOL
4. The length of pipeline element and coordinates of pipe spool elements are
converted to current model unit, while generating pipeline spool drawing using
DRAW PSPOOL command,
5. The spool length and element co-ordinate values, stored in the external
RDBMS tables are normalized to the Meter linear units. The length of pipeline
element and coordinates of pipe spool elements are converted back to the
current model unit, while generating pipeline spool drawing using DRAW
PSPOOL command.
6. Pipelines are drawn in their original layer based on the information extracted
from the actual model, and hidden line removal (HLR) is performed based on
this layer information.

This chapter explains the general purpose and use of piping commands, their mode
of usage, the syntax and the modifiers.
The following commands are discussed under this chapter:

GENERATE EXPLICITPIPE
GENERATE ISOMETRIC
GENERATE PIPEDBASE
GENERATE SPOOL
HIDE INTERSECTION

Description
Use this command to generate center lines for pipelines, valves, equipment, and
nozzles in a piping drawing after hidden line removal.
The center lines created by this command are draw mode entities.
Valid Modes
Model mode and draw mode.
Syntax
#n# GENERATE CLINE [modifiers] ALL or PLINE LINENO or:getdata

Modifiers
The following diagram shows the flow of GENERATE CLINE modifiers. An
see the Preface.
follows.
1 ALL
Specifies that center lines are to be created for all the pipelines and equipment
in the selected view. This modifier is mutually exclusive with the PLINE
modifier.

1 EXTENSION x
Specifies the distance upto which the center lines could be extended, beyond
the end points of the pipeline or equipment. The distance is specified in
drawing units.
1 FONT delimited text
Specifies the font to be used for centerline generation. Fonts are defined in the
file /cadds/data/gen/data/_bcd/fontdefs. The default font for
centerline generation is COUNTY.
1 HORIZONTAL
Specifies that only the horizontal center line, or the centerline along the X axis
of the drawing, is to be created. This modifier is mutually exclusive with the
VERTICAL modifier.
1 LAYER x
Specifies the layer on which the centerline entities are to be created. The default
layer is the active layer.
1 NOBREAK x
Specifies that a centerline is generated for the hidden portions of the selected
pipelines and equipment. By default, a centerline is not generated for the
hidden portion.
1 PLINE
Specifies that center lines are to be created only for selected pipelines and/or
valves used with LINENO, VALVE and FITTYPE modifiers described below.
This modifier is mutually exclusive with the ALL modifier.
Specifies the line number of a pipeline for which the center lines are to be
created.
2 VALVE
Specifies that center lines are to be created for the stem of the valve
components in selected pipeline(s).

3 FITTYPE x
Specifies that valve stem center lines are to be created only for the valves with
the specified fitting type values.
1 VERTICAL
Specifies that only the vertical center line, or the centerline along the Y-axis of
the drawing, is to be created. This modifier is mutually exclusive with the
HORIZONTAL modifier.
Procedure 1
To generate center lines for all the entities in the view,
1. Enter GENERATE CLINE ALL.
3. Enter a colon.
4. The system prompts outdo select the view.
5. Select the view on which you want to generate center lines for all entities.
6. Press RETURN.
Procedure 2
To generate centerline for a pipe identified by its line number,
1. Enter GENERATE CLINE PLINE LINENO.

2. Enter the line number of a pipeline.
4. Enter a colon.
5. The system prompts you to select the view.
6. Select the view for generating center lines for the selected pipeline and its
components.
7. Press RETURN.
Procedure 3
To generate center lines for graphically selected entities,
1. Enter GENERATE CLINE.


3. Enter a colon. The system prompts view.

4. Select the view for generating center lines.
5. Enter a semicolon.
6. The system displays the prompt MODEL ent.
7. Select the entities for generating center lines.
8. Press RETURN.
Example 1
In this example, center lines are created for all entities in a view.

#n# GENERATE CLINE EXTENSION 0.1 ALL: view d1

Example 2
In this example a horizontal centerline is created.
#n# GENERATE CLINE EXTENSION 0.2 HORIZONTAL: view d1; Model ent
d2
Example 3
In this example a vertical centerline is created.
#n# GENERATE CLINE EXTENSION 0.2 VERTICAL: view d1; Model ent d2

Example 4
In this example center lines are created for all the entities in a view, without
specifying NOBREAK.
#n# GENERATE CLINE ALL: view d1

Example 5
In this example center lines are created for all the entities in a view, including
hidden portions.
#n# GENERATE CLINE NOBREAK ALL: view d1

Description
Use this command to create cut section symbols at the clipping points of pipe
segments, where they are clipped by a section view. Different cross section
symbols are created based on whether the pipe segment is clipped by the DMIN or
DMAX clipping plane of the view.
Valid Modes
Syntax
#n# GENERATE CSSYMBOL [modifiers] ALL or LINENO or:getdata
Modifiers
The following diagram shows the flow of GENERATE CSSYMBOL modifiers.
follows.

ALL
Specifies that cut section symbols are to be created for all the pipelines in the
selected view. This modifier is mutually exclusive with the LINENO modifier.
DMAX x
Specifies the maximum extent of depth clipping to be applied to the selected

view. A view clipping plane is placed at the given DMAX location and cut
section symbol are created at all pipe segments which are cut by this clipping
plane.
This value is in the model units of measurement. DMAX value is relative to the
current view and should be less than the current view ZMAX. If this modifier is
not specified or if the specified DMAX is greater than the view ZMAX, then
the ZMAX value of the view is used.
DMIN x
Specifies the minimum extent of the depth clipping to be applied to the view. A
view clipping plane is placed at the given DMIN location and cut section
symbols are created at all pipe segments which are cut by this clipping plane.
This value is in the model units of measurement. DMIN value is relative to the
current view and should be greater than the current view ZMIN. If this modifier
is not specified or if the specified value is less than the view ZMIN, then the
ZMIN value of the view is used.
DOWNSYMBOL delimited text
Specifies the sub-figure name to be used if a pipe segment is cut by the view
DMIN clipping plane. The default symbol sub-figure name is
CVPD.CSSYMBOL.DOWN.
LAYER x
Specifies the layer on which cut section symbols are to be created. The default
is the active layer.
Specifies the line number of a pipeline for which cut section symbols are to be
generated. This modifier is mutually exclusive with the ALL modifier.

UPSYMBOL delimited text
Specifies the sub-figure name to be used if a pipe segment is cut by the view
DMAX clipping plane. The default symbol sub-figure name is
CVPD.CSSYMBOL.UP.
Procedure 1
To generate cut section symbols for all the entities in the view,
1. Enter GENERATE CSSYMBOL ALL.

3. Enter a colon.
4. The system prompts you to select view.
5. Select the view for generating cut section symbols for all the pipelines in it.
6. Press RETURN.
Procedure 2
To generate cut section symbols for the pipe identified by its line number,
1. Enter GENERATE CSSYMBOL LINENO.

4. Enter a colon.
6. Select the view for generating cut section symbols for the selected pipeline.
7. Press RETURN.
Procedure 3
To generate cut section symbols for graphically selected entities,
1. Enter GENERATE CSSYMBOL.

3. Enter a colon.
5. Select the view for generating cut section symbols.
6. Enter a semicolon.

7. The system prompts MODEL ent.

8. Select the pipelines for generating cut section symbols.
9. Press RETURN.
Example
This example illustrates the generation of cut section symbols.
#n# GENERATE CSSYMBOL UPSYMBOL CVPD.PSMARK.UP DOWNSYMBOL
CVPD.PSMARK.DOWN DMIN 0.2 DMAX 0.8: view d1; Model ent d2

OR
#n# GENERATE CSSYMBOL UPSYMBOL CVPD.PSMARK.UP DOWNSYMBOL
CVPD.PSMARK.DOWN DMIN 0.2 DMAX 0.8 LINENO EXAMPLE-CS-100-XX: view
d1

Use this command to generate an explicit pipeline from a parametric pipeline.You
can also update the converted pipeline based on the changes made to the
associated original parametric pipeline.
The explicit pipelines generated using this command can be used to perform
further Explicit piping tasks such as Isometric Drawings, Spool Generation and so
on.
Please note: You can use the command ZOOM VIEW ALL before using the
above command to ensure that all the parametric pipelines are visible in the
conversion range.
Valid Modes
Model mode
Syntax
#n# GENERATE EXPLICITPIPE [modifiers]

Modifiers
The following diagram shows the flow of GENERATE EXPLICITPIPE modifiers.
follows:
1 ALL FLAG
Specifies that all the parametric pipelines in the active part are to be converted
to explicit pipelines.
This modifier is mutually exclusive with the getdata, Mnemonic and Number
modifiers.

1 FITLAYER
Specifies the layer number to be used for inserting the generated explicit pipe
fittings. If this modifier is not specified, the converted pipe fitting, by default, is
placed on the active layer.
Please note: The specified layer number must be echoed before executing the
above command.
1 MNEMONIC STRING
Specifies that the explicit pipelines will be generated from parametric pipelines
of specified mnemonic.
This modifier is mutually exclusive with the All and getdata modifiers.
1 NUMBER NUMERIC
Specifies that the explicit pipelines will be generated from parametric pipelines
of specified number.
This modifier is mutually exclusive with the All and getdata modifiers.
1 PIPLAYER
Specifies the layer number to be used for inserting the generated explicit
pipeline segments and bends. If this modifier is not specified, the converted
pipeline, by default, is placed on the active layer.
Please note: The specified layer number must be echoed before executing the
above command.

Example 1
This example illustrates the generation of an explicit pipeline for the specified
parametric pipeline on the currently active layer
#n# GENERATE EXPLICITPIPE : Model ent <getdata>
Figure 3-1 Parametric Pipeline Before Conversion

Figure 3-2 Explicit Pipeline Generated After Conversion
Example 2
This example generates explicit pipelines from two parametric pipelines in the
active part, with a mnemonic HYDRAULIC and pipeline numbers 8242 and 8042.
The pipelines are created on layer 10, and the pipe fittings are created on layer 20.
#n# GENERATE EXPLICITPIPE MNEMONIC HYDRAULIC NUMBER 8242 8042
PIPLAYER 10 FITLAYER 20

GENERATE ISOMETRIC
GENERATE ISOMETRIC
Description
Use this command to generate an undimensioned piping isometric drawing. Derive
the isometric from the scaled, three-dimensional model of a pipeline or piping
network.
Rescale the model and annotate it to produce the isometric drawing. Add the
dimensions using the DIMENSION ISOMETRIC command.
The pipelines, fittings, and valves are drawn in proportion and identified with
standard isometric symbols. The annotation process automatically indicates such
items as
Specification changes
Reducing fittings line attachments
Bend angles and radii
Roll angle between bends
Flow direction
Slopes less than 5 degrees
Shop and field welds
Nonstandard valve stem orientations
Proper bolt hole orientations
Valid Modes
Model mode
Syntax
#n# GENERATE ISOMETRIC [modifiers]

GENERATE ISOMETRIC
Modifiers
The following diagram shows the flow of GENERATE ISOMETRIC modifiers.
diagrams, see the preface.

GENERATE ISOMETRIC
follows.
1 BEND x
Specifies the size of the bend symbol on the drawing. The default is 1 drawing
unit.
1 FITTING
Specifies the size of fitting symbols.
2 HEIGHT x
2 LENGTH x
drawing unit.
1 FLANGE x
Specifies the length (along the run) of a flange symbol. Height is the same as for
fittings. The default is 0.25 drawing units.
1 FLOWARROWS
Specifies flowarrow parameters. Flowarrows are placed on the mainline and

each branchline, as near as possible to the middle pipe.
2 CLOSED
Specifies unfilled triangular arrows. Mutually exclusive with FILLED and

OPEN.
2 FILLED
(Default) Specifies filled triangular arrows. Mutually exclusive with CLOSED

and OPEN.
2 LENGTH x
Specifies length of arrow (along the run). The default is 0.25 drawing units.

GENERATE ISOMETRIC
2 OFF
Deactivates drawing of flowarrows.
2 ON
(Default) Activates drawing of flowarrows.
2 OPEN
Specifies V-shaped unfilled flowarrows. Mutually exclusive with CLOSED and

FILLED.
2 RATIO x
Specifies the ratio of the flowarrow length to width. The default is 3.0.
1 GASKET x
Specifies the length (along the run) of gap for gaskets. The default is 0.25
drawing units.
1 PIPE
Specifies the maximum and minimum permitted lengths of pipe. These lengths
are reduced or increased proportionately by the use of the modifier ZOOM.
2 MAXIMUM x
Specifies the maximum length of pipe. The default is 5.0 drawing units.
2 MINIMUM x
Specifies the minimum length of pipe. The default is 2.0 drawing units.
1 WELD
Activates or deactivates shop and field weld symbols, specifies size and related
property values (for shop welds).
2 ENDTYPE delimited text
Specifies the text value of the ENDTYPE property indicating shop welds. Shop
welds are drawn for all Cnodes that have the specified property value. The
default is to draw weld dots if any character of the ENDTYPE property is a W.
The text value has a limit of two characters.

GENERATE ISOMETRIC
2 OFF
Deactivates display of welds.
2 ON
Activates display of welds.
2 FIELDWELD x
Specifies size of field weld symbol. The field weld symbol is the weld dot with
an X through it. Field welds are drawn for all Cnodes that have the property
FITTYPE with a value of 70. The default is 0.25 drawing units for the X
symbol.
2 SHOPWELD x
Specifies diameter of shop weld symbol. The default is.125 drawing units for
the dot symbol.
1 ZOOM
Affects the size of the annotated, rescaled pipeline within the available area of
the view window. The available area excludes that for section boxes. The
default is to center and fit the pipeline to 70 percent of the available area of the
view window. This ensures room for later dimensioning.
2 OFF
Centers the annotated, rescaled pipeline within the available area of the view
window. The pipeline size is a function of the specified maximum and
minimum pipe lengths. If the maximum is too long, the pipeline may not fit in
the available area.
2 ON
(Default) Centers and fits the annotated, rescaled pipeline to 70 percent of the
available area of the view window. The specified maximum and minimum pipe
and fitting lengths are reduced or increased when this modifier is used.

GENERATE ISOMETRIC
Procedure
Use the GENERATE ISOMETRIC command as follows:
1. Activate the part with the pipeline or set of interconnected pipelines that you
want to use to make an isometric drawing. You may construct such parts or
extract them from the plant model using the CONSTRUCT PLINE command.
Save the original dimensions with the SAVE DIMENSIONS command.
2. Activate a drawing with an isometric view. Activate a standard format by using
the modifier FORM within the ACTIVATE DRAWING command (see the
Isometric Drawing User Guide).
3. Select a construction plane and text height for annotation. This plane affects all
of the model text, automatically inserted to annotate the drawing except for the
section box text.
Section boxes are created from drawing graphic entities and text to show bolt
hole orientations or nonstandard stem orientations. The height of a box is ten
times the selected text height.
4. Echo layers selectively with the ECHO LAYER command so that the fitting
model graphics are off and the fitting isometric graphics are on. You can do this
before or after executing GENERATE ISOMETRIC.
5. Echo off the Cnode, Tnode, and Nfigure symbols using the ECHO
APPEARANCE SYMBOL OFF command. You can still identify the entities
with the symbols echoed off.
6. If you want to include more than one pipeline in the isometric drawing, remove
the TERMNAM property from the Cnode(s) that connects them.
7. Insert the FITTYPE property with a value of 70 on Cnodes located at field
welds (interspool connection points) that you want called out by the field weld
symbol (x).
8. Enter the command GENERATE ISOMETRIC, together with any optional
modifiers to specify parameters of pipes, gaskets, fittings, flanges, flowarrows,
welds, and the size of the whole pipeline on the drawing (ZOOM).
9. Press RETURN.
Example
This example continues the process of generating an isometric drawing of line
O-8242 (from the CVPDC plant model) that began in the CONSTRUCT PLINE
example.

GENERATE ISOMETRIC
The new part created by CONSTRUCT PLINE has the same drawings that the
model does. You can delete them as you choose and set up a drawing for the
isometric. This is simplified by using a standard form drawing. It has the same
database units (feet) the model has. Use the SAVE DIMENSIONS command to
save the model geometry before rescaling the pipeline with GENERATE
ISOMETRIC.
The BEFORE drawing is an isometric view. The pipeline is zoomed and scrolled
to fit within the view. Then the view is set. This does not have to be exact as
GENERATE ISOMETRIC automatically rescales the pipeline to fit on the
drawing. You can influence the results, however, with the ZOOM, MAXIMUM,
and MINIMUM modifiers.
Cnode, Tnode, and Nfigure symbols are echoed off.
The view layers are echoed to turn on the isometric graphics within the fittings and
to turn off the model graphics within the fittings. The isometric graphics are on
layer 0 relative to the fitting Nfigure; the model graphics are on layer 30.
Now specify the GENERATE ISOMETRIC command together with the

appropriate modifiers:
#n# GENERATE ISOMETRIC FITTING LENGTH.20 HEIGHT.20 PIPE MINIMUM.4
MAXIMUM.4 WELD SHOP.02 FLAN.05 FLOW LENGTH.06 FILLEDGASKET.03
(tracing pipeline)
(rescaling pipeline)
(regenerating graphics)
To achieve the desired appearance, dispose of the gasket graphics by moving the
gasket Nlines to an invisible layer after executing GENERATE ISOMETRIC.
Establish text parameters with the SELECT TEXT command.

GENERATE ISOMETRIC
The result is shown in the following BEFORE and AFTER illustrations.

GENERATE ISOMETRIC
Notes
The following general notes will help you when using the GENERATE
ISOMETRIC command.
1. Draw the model at the approximate scale you want the isometric, and set the
view. If you do any additional view manipulation, such as zooming or scrolling,
reset or set the view before using DIMENSION ISOMETRIC.
2. To echo off gasket Nlines, use the MARK ENTITY command to identify them.
Then specify CHANGE LAYER or ECHO ENTITY OFF to make them
invisible. For example:
#n# MARK ENT CONDITION
IF(GASKET)
#n# BLANK ENT: MODEL ent MARK VWIN d
3. Section box graphics and text are drawing entities; all other graphics and text
are model entities.
4. This command uses the nodal figure graphics of fittings and flanges to obtain
standard isometric symbols. To get the results you want, the part must conform
to layering conventions.
The fittings and flanges in the CVPD component library demonstrate these
conventions. These components have their three-dimensional model graphics
on layer 30 and their two-dimensional isometric graphics on layer 0. For the
isometric drawing, echo on only the layers with pipes and isometric graphics.
5. The default values for the modifiers were selected with reference to a drawing
unit of inches. If your drawing units are different, you may want to change the
default values. To do this, edit the modifier table in the file
data/modtab/generate/isometric. Then recompile the table using the
operating system command MODCOMP.
6. The technique for producing the thick linework typical of an isometric depends
on the type of plotter. For dot matrix plotters, use groups of layers and assign
them different widths as follows:
#n# PLOT DOT LAYER n WIDTH n LAYER m WIDTH m
With pen plotters, use the modifiers PEN1, PEN2, and so on. Plot the graphics
on different layers with pens of different thickness assigned to the different
layers.
7. Before using the GENERATE ISOMETRIC command, select a suitable height
and construction plane for the text.
8. This command automatically scales pipeline labels to be consistent in size with
the generated annotation text; they are positioned right over the pipe (Nline) to
which they are related. Note that the roll angle between bends is automatically
annotated when their planes are not orthogonal.

GENERATE ISOMETRIC
9. A set of multiple interconnected pipelines can be processed as long as there are

no TERMNAM properties separating the pipelines. The different lines are
defined by their unique line numbers.
10. Flanges, valves, and free-stemmed tees reference auxiliary section boxes to
indicate nonstandard stem or bolt orientations.
11. Automatic zooming allows automatic isometric dimensioning to follow without
intervention. However, the sizes you select are scaled relative to the zooming
ratio. To ensure text height is precisely as you specify with SELECT TEXT, use
GENERATE ISOMETRIC with ZOOM off.
12. Use the following command to indicate field welds at selected Cnodes:
#n# INSERT PROP FITTYPE 70: MODEL ent CNODE d1...d

Description
Use this command to create a Material Description file for pipeline components
based on a given material description IN-file and a pipeline component size matrix.
Valid Modes
Model mode and Draw mode
Syntax
#n# GENERATE MDF [modifiers]

Modifiers
The following diagram shows the flow of GENERATE MDF modifiers. An
see the Preface.
follows:
1 INFILE
Specifies the name of the material description IN-file. This is the file which
contains a list of detailed material descriptions of various piping components.
(The default file name is CVPD.ISO.MDFINFILE-MM).

1 MATRIXFILE
SpecifIes the name of the material description IN-file. This is the file which
contains a list of detailed material descriptions of various piping components.
(The default file name is CVPD.ISO.MDFINFILE-MM).
1 SPECID
Specifies the pipe specification-ID that is to be printed in the Material

Description File.
1 DESTFILE
Specifies the name of the output file which stores all the records that are
generated. If you enter an existing filename, the records are appended to the
named file.
Procedure
To generate a material description file,
1. Enter GENERATE MDF.

2. The system prompts
Modifier Spec-Id has to be specified.
Specify the pipe specification-Id that is to be printed in the Material Description
File.
3. The system prompts
Name of Modifier Dest File has to be specified.
Specify the name of the output file that will store all the records that are
generated. If you enter an existing filename, the records is appended to the
named file.
For more information on the file formats and examples of the material description
IN-file and matrix files, see the Piping Specification User Guide.

GENERATE PIPEDBASE
GENERATE PIPEDBASE
Description
Use GENERATE PIPEDBASE command to generate external database for
pipelines or pipeline spools. You can extract the information of selected pipelines
or pipeline spools from an active CADDS part and write them into specified
external RDBMS tables using this command. You can store graphical and
non-graphical information of pipelines or pipeline spools from different CADDS
parts, into a common database.
Use this command to
Enable and retain the connection to the external RDBMS.

completed.
Create new project component relations in an existing Project Component tree
structure by specifying the assembly, sub-assembly and type of project
components and use it to store the pipeline spool information in external
RDBMS tables. You can also specify the appropriate external RDBMS tables
for storing pipeline spool information by specifying the assembly name in an
existing Project Component tree structure. (Refer to AEC Project Component
Table on page B-7 , for details of the tree structure)
The Project Component tree structure is a hierarchical logical structure of
project components. Each record in this table defines a project component like
ship, stage, block or panel, and the identification of its parent component.
Through a logical parent child relationship of the various project components a
tree structure of the project components can be established using this table. The
name of this table is as specified in the AEC_PROJECT_DICTIONARY_TBL
for a given project and against the keyword COMPONENT.
Extract the information for pipeline spools of 3D modeling mode or complete
pipelines of schematic, or 3D modeling mode.
Extract the information for 2D schematic mode and 3D modeling mode or
complete pipelines, automatically relate each 3D model piping components to
its corresponding object in 2D schematic and store them in an unified RDBMS
table. This automatic relation of piping components is enabled when 2D
schematic information is already in the external RDBMS table, while
extracting the corresponding 3D model pipeline.
Synchronize the pipeline information in the external RDBMS tables for the
active and viewed parts.
Delete the stored information from the specified external RDBMS for a
complete pipeline network.

GENERATE PIPEDBASE
Enable and retain the connection to the external RDBMS.

completed.
Execute a user-specified external script.
Enable and disable the fabrication drawing generation status in the specified
external RDBMS tables for selected pipeline spools.
Automatically relate the entire pipeline network and manually relate or unrelate
any one component in the schematic to the related component in the model.
Refer to Relating the 2D Schematic and 3D Model Pipeline Network on
page 3-37 for more details.
This command stores and manipulates the information in the following external
RDBMS tables:
The pipeline list table

The pipeline spool element table
The pipeline bend table
The pipeline item number information table
The pipe end type table
The names of these tables are determined from the table definitions specified in the
AEC_APPLICATION_TBL table based on the object type numbers. For details,
refer to AEC Application Object Dictionary Table on page B-12 .
The object type numbers corresponding to the table names are defined in the
AEC_OBJECTTYPE_TBL by the following keywords:
Pipeline list table: PIPE_LIST
Pipeline spool element table: PIPE_ELEMENT
Pipeline bend table: PIPE_BEND
Pipeline item number information table: PIPE_ITEM
Pipe end type table: PIPE_ENDTYPE

GENERATE PIPEDBASE
The extracted and stored information in the external RDBMS tables are used by
the DRAW PSPOOL command for the automatic generation of pipeline spool
drawings.
Please note: The command GENERATE PIPEDBASE extracts the relevant

information to the Pipeline bend table, Pipeline item number information table,
and the Pipe end type table only if the pipe spool is annotated using the SAVE
ANNOTATION command. The resultant annotated pipe elements have the
ITEMNUMB property.
Additionally, you can use the inherent SQL facilities of the external RDBMS
software to generate customized pipeline reports from the data extracted and
stored in the external RDBMS tables.
Refer to Pipeline RDBMS Tables on page B-33 , for details on the pipeline list,
pipeline element, pipeline bend, pipeline item number information and pipeline
end type tables.
Before using this command, you must properly set up the RDBMS related
environment variables and the necessary project and application tables. For details
refer to RDBMS Environment Variables Setup on page B-2 .
Execute the various scripts files to establish the necessary project information and
Piping RDBMS table formats from the following directories:
/usr/apl/cadds/data/cvaec/dbms/scripts/
Also, before using this command, you can optionally run the GENERATE SPOOL
command on pipeline networks to generate the individual pipeline spools with
associated unique labels. This command sequence is essential to ensure that the
data extracted and stored by GENERATE PIPEDBASE is useful for subsequent
execution of the DRAW PSPOOL command.
You must specify the units of various fields in the pipeline list table, pipeline
element table, and the pipeline bend table. You must also specify the conversion
factors for converting these units. Refer to Appendix B, Piping RDBMS Tables
for more details.

GENERATE PIPEDBASE
Relating the 2D Schematic and 3D Model Pipeline

Network
The schematic and the model pipeline networks are automatically related based on
certain pre-defined rules as given below:
The schematic pipeline network should be populated to the RDBMS before any
automatic relation is done and should be viewed in the 3D active model for the
command to relate the components before populating the 3D model network
components.
Please note: If any pipeline network has been populated in the RDBMS then
you need not issue the ASSEMBLY modifier while executing the command
repeatedly.
All the schematic components are considered as critical components and are
matched with the model components. The elbows, flanges and gaskets of the
model are considered as non-critical components and are related to the pipe of a
schematic network.
The command SELECT PPARAMETERS PIPING LINKFORMAT should be
specified with proper link format in order to relate the critical components. The
link format value is based on the property names for which the critical
components are checked. This is done in a sequential order. When all the
properties are matched, the critical components are related.
The flow direction should match for the schematic and the model pipeline
networks.
Those components which are not represented in the schematic but are present in
the model will be treated as unrelated components and will be related to the
nearest related previous 2D schematic component.
At the point of branches you should relate the branch pipelines manually
between the schematic and model.
The ends or the joints of the pipeline network can be related for nozzles or pipes
at the end locations. If a nozzle is present at the end of a pipeline network, the
nodal text value attached to the nozzle nfigure and the nodal text value of the
equipment to which the nozzle is attached, should be the same for both the
schematic and model, in order to relate the pipeline networks. In case of
equipments at the pipeline network end, the nodal text value of the equipment
should be the same. In case of another pipeline present at the current end
pipeline network, the pipeline labels should match for both the schematic and
model.
All critical inline components should have any one of the property and its value
specified in the SELECT PPARAMETERS PIPING LINKFORMAT command.

GENERATE PIPEDBASE
Valid Modes
Model
Syntax
GENERATE PIPEDBASE USER <user_name> PASSWORD <password> ASSEMBLY
<assembly> [modifiers]: Model ent <getdata>
GENERATE PIPEDBASE ASSEMBLY <assembly> [modifiers]: <CR>
GENERATE PIPEDBASE ASSEMBLY <assembly> LINENO <line_no>

SPOOLNUM <spool_no> [modifiers]: <CR>
GENERATE PIPEDBASE SYNCHRONIZE <CR>
GENERATE PIPEDBASE DISCONNECT <CR>
Modifiers
The following diagram shows the flow of GENERATE PIPEDBASE modifiers.

GENERATE PIPEDBASE
The modifiers are listed alphabetically within each logical grouping. The number
on the left indicates the modifier's level.

GENERATE PIPEDBASE
1 ALL flag
Specifies that all the pipelines or pipeline spools in the currently active part are
to be selected for database manipulation. This modifier is mutually exclusive
with the LINENO and LABELFILE modifiers.
1 ASSEMBLY assembly_name, limit=40
Specifies the assembly name to be used to categorize and relate the selected
pipelines or pipeline spools as components in the same assembly or
sub-assembly. This enables you to store information in the same set of external
RDBMS tables.
This modifier allows you to relate the selected pipelines or pipeline spools to
the specified assembly or sub-assembly, and their attributes are stored in the
external relational database.
If you use the second level modifier SUBASSEMBLY, the specified assembly
becomes the parent of the subassembly in the hierarchical project structure, and
the subassembly becomes the target assembly with which the selected pipeline
spools are to be associated.
In all cases, the specified assembly name must exist in the corresponding
Project Component Table.This modifier is mandatory and specifies the
assembly with which the selected pipelines or pipeline spools or subassembly
are to be associated.
Once the pipeline has been dumped to a specified assembly, the ASSEMBLY
modifier need not be specified on repeated execution of the command on the
same pipeline.
2 SUBASSEMBLY sub-assembly_name, limit=40
Specifies the name of the sub-assembly that contains the selected pipeline
spools in the external RDBMS tables. A sub-assembly is a logical object that
consists of a collection of sub-assemblies and/or pipeline spools, and is a child
to the assembly in the hierarchical project structure as specified in the first level
modifier, ASSEMBLY.
If the specified sub-assembly does not exist in the external relational database,
it is created and related as a child to the specified assembly in the hierarchical
project structure.
3 TYPE sub-assembly_type, limit=20
Specifies the type of the sub-assembly. This attribute is stored in the external
relational database along with the specified sub-assembly.

GENERATE PIPEDBASE
1 DELETE flag
Specifies that the information stored in the external RDBMS tables for the
selected pipeline spools or pipelines are to be deleted. This modifier enables
you to delete RDBMS table records from within an active part. This eliminates
the need to issue explicit SQL commands in the RDBMS software.
This modifier is mutually exclusive with OVERWRITE, DRAW and NODRAW
modifiers.
1 DISCONNECT flag
Specifies that the connection to external RDBMS software will be terminated

after the execution of the current command. By default the existing connection
is retained for further RDBMS operations.
This modifier is mutually exclusive with USERNAME modifier.
1 DRAW flag
Enables the status code for spool drawing generation of the selected pipeline
spools in the external RDBMS table. This status code is used by the DRAW
PSPOOL command for including the selected pipeline spools during drawing
generation. This modifier is mutually exclusive with DELETE and NODRAW
modifiers.
1 LABELFILE label_list_file_name, limit=72
Specifies the name of the file that contains a list of all the pipeline spool labels
to be processed for database generation or manipulation. This file can be
manually created using a text editor or automatically generated using the
REPORT PIPE command and suitably edited. This modifier is mutually
exclusive with the ALL and LINENO modifiers.
1 LINENO pipe_lineno, limit=40, list=10
Identifies the pipelines to be selected for database manipulation by their line

numbers. Enter the complete pipeline label or a subset of the fields in the
pipeline label, as specified in the LINENO-FORMAT field of the currently
active directory file. You can enter multiple line numbers separated by comma.
A maximum of 10 pipeline numbers can be specified and also there is no need
to digitize pipelines in getdata.
The SPOOLNUM sub-modifier can be used to explicitly specify the pipeline
spools of the selected pipeline for processing. This modifier is mutually
exclusive with the ALL and LABELFILE modifiers.

GENERATE PIPEDBASE
2 SPOOLNUM spool_number, limit=40, list=10
Specifies a pipeline spool number or a list of pipeline spool numbers to be

processed from a single pipeline selected by the LINENO modifier.
1 NODRAW flag
Disables the status code for spool drawing generation of the selected pipeline
spools in the external RDBMS table. This status code is used by the DRAW
PSPOOL command for excluding the selected pipeline spools during drawing
generation. This modifier is mutually exclusive with DELETE and DRAW
modifiers.
1 OVERWRITE flag
Overwrites the information in the spool and spool element RDBMS tables for
the selected pipeline spools. By combining this modifier with the ALL
modifier, you can synchronize the pipeline spool model information in the
active CADDS part and related RDBMS table. For details refer to Pipeline
RDBMS Tables on page B-33 .
If this modifier is not specified, the information is appended to the above
RDBMS tables for the selected pipeline spools. During the append process, the
pipeline spools whose information already exists in the external RDBMS tables
are excluded from the append operation and a warning message is issued. This
modifier is mutually exclusive with DELETE modifier.
1 RELATEITEM flag
Specifies that a digitized 2D schematic piping component will be related to the

digitized 3D model piping component in the external RDBMS table. The
related 2D and 3D piping components' RDBMS unique object uids will be
populated in the AEC Object Link Table with the relation type keyword value
PIPE_MANUAL, where the keyword PIPE_MANUAL is defined in the AEC
Relation Table.
This modifier is mutually exclusive with ASSEMBLY, LABELFILE, ALL,
OVERWRITE, DRAW, NODRAW, DELETE and UNRELATEITEM
modifiers.
Please note: The items which are related manually will be ignored during the
automatic linking process, since the manual linking has a higher precedence
during the process. You can use this option to force a link between a 2D piping
component and its instance in the 3D model. You can remove the manual relation
using the UNRELATEITEM modifier.

GENERATE PIPEDBASE
1 SCRIPT unix_shell_script_file
Executes a UNIX script in the directory where CADDS is invoked. This

modifier is case sensitive and hence the script name must match the case of the
UNIX path and filename. You can view this process in a CADDS IPC window
by setting the following environment variables in your.caddsrc file:
SETENV SCRIPTS_TOOL shelltool
SETENV SCRIPTS_PROCESS YES
The specified script will be executed at the end of the command. This modifier
can be used with any other database processing modifiers like DELETE,
OVERWRITE, DRAW and NODRAW.
1 SYNCHRONIZE flag
Specifies that the information stored in the external RDBMS tables for the
obsolete pipelines or pipeline spools, that no longer exist in the active part will
be deleted. This modifier enables you to delete RDBMS table records from
within an active part. This eliminates the need to issue explicit SQL commands
in the RDBMS software. This modifier can be used to manually synchronize the
RDBMS tables with the model graphics of active part. This operation will
always be executed at the end of the command. It can be used with any other
database processing modifiers like DELETE, OVERWRITE, DRAW and
NODRAW
1 UNRELATEITEM flag
Specifies that a digitized 2D schematic piping component will be unrelated to

the digitized 3D model piping component in the external RDBMS table. The
related 2D and 3D piping components relation record will be deleted from the
AEC Object Link Table.
This modifier is mutually exclusive with ASSEMBLY, LINENO, LABELFILE,
ALL, OVERWRITE, DRAW, NODRAW, DELETE and RELATEITEM
modifiers.
Please note: The items which are manually related will be ignored during the
automatic linking process as the manual link has a higher precedence, and these
items have to be unrelated using the UNRELATEITEM modifier for the command,
to do the automatic relating process.
1 USERNAME oracle_database_username, limit=30
Specifies the login user name for connecting to the external RDBMS tables.
This modifier must be used with the PASSWORD sub-modifier once to
establish the RDBMS connection. The established connection is retained until it
is disabled using DISCONNECT modifier.

GENERATE PIPEDBASE
2 PASSWORD oracle_database_password, limit=30
Specifies the password for accessing the external RDBMS software for an
authorized user as specified by the USERNAME modifier. This modifier must
be used with the USERNAME modifier once to establish the RDBMS
connection, else the command terminates with an error message.
Procedure 1
You must carry out the following steps before you are ready to invoke the
GENERATE PIPEDBASE command.
1. Set up the RDBMS environment variables as explained in the RDBMS

Environment Variables Setup on page B-2 .
2. Create the project information tables as explained in the Project Information
Tables on page B-4 .
3. Create the pipeline list table, element table, bend information table, item
number information table, and endtype table as explained in Pipeline RDBMS
Tables on page B-33 .
4. Activate the part and appropriate drawing in which the pipeline model exists.
5. Link the part with a project by specifying the project name in SELECT
RDBMS command as explained in Linking CADDS Parts to a Project on
page B-3
6. Select the directory file which defines the SPOOL field in the LABEL format,
using the SELECT PPARAMETERS PIPING command.
7. Generate the spool labels if required, using GENERATE SPOOL command
with NOLEGEND modifier. Alternatively you can also generate the spool
labels without the NOLEGEND modifier and unblank the blanked pipeline
spool labels.
After creating the pipeline spools with associated spool labels as explained above,
you can follow the procedures below to extract pipeline spool information, store
and manipulate them in the external RDBMS tables.
Procedure 2
To create a new sub-assembly in a Project Component tree structure,
1. Enter GENERATE PIPEDBASE command.

2. Specify the user name and password for logging to the external RDBMS.
3. Specify the existing assembly name, which will be the parent of the
sub-assembly to be created.

GENERATE PIPEDBASE
4. Specify the sub-assembly name and its type.

5. Press RETURN.
Procedure 3
To append/overwrite/delete information of digitized pipeline spools,

3. Specify the assembly name, to which the information is to be associated.
4. To overwrite existing pipeline or pipeline spool information, select
OVERWRITE modifier. To delete existing pipeline or pipeline spool
information, select DELETE modifier. If none of these modifiers are selected
then pipeline spool information will be appended.
5. Enter colon.
6. Digitize the labels of the pipeline spools, to identify them for database
extraction or manipulation.
7. Press RETURN.
Procedure 4
To append/overwrite/delete information of pipeline spools, specified using pipeline
numbers,

3. Specify the assembly name, to which the information is to be associated to.
4. To overwrite existing pipeline or pipeline spool information, select
OVERWRITE modifier. To delete existing pipeline or pipeline spool
information, select DELETE modifier. If none of these modifiers are selected
then pipeline or pipeline spool information will be appended.
5. Specify the line numbers and spool numbers to identify the pipeline or pipeline
spool for processing. Alternatively, you can supply a list of line numbers
through a text file using the label file option.
6. Press RETURN.

GENERATE PIPEDBASE
Procedure 5
To enable/disable drawing generation status for digitized/specified pipeline
spools,
3. Specify the assembly name, which the information is to be associated to or
already associated with.
4. To enable the drawing generation status, select DRAW modifier. To disable the
drawing generation status, select NODRAW modifier. In order to
enable/disable the drawing status for existing pipeline spools, OVERWRITE
modifier can be specified simultaneously.
5. Specify the line numbers and spool numbers to identify the pipeline spools for
processing. Alternatively, you can supply a list of line numbers through a text
file using the label file option.
6. Press RETURN.
Procedure 6
To manually relate a 2D schematic component and its 3D model instance,
1. Activate a 2D schematic part

2. Enter GENERATE PIPEDBASE command to extract the information of 2D
pipelines into external RDBMS.
3. Activate a 3D model part.
4. View the 2D schematic part inside the 3D model part.
5. Enter GENERATE PIPEDBASE RELATEITEM: <dig1> <dig2>. Digitize the
2D schematic pipeline component first and then the corresponding 3D instance
to be manually related.
6. Press RETURN.
Procedure 7
To automatically relate a 2D schematic pipeline and its 3D model instance,
1. Activate a 2D schematic part

2. Enter GENERATE PIPEDBASE command to extract information of 2D
pipelines into external RDBMS.
3. Activate a 3D model part.
4. View the 2D schematic part inside the 3D model part.

GENERATE PIPEDBASE
5. Enter GENERATE PIPEDBASE: <dig1> Digitize the 3D model pipeline which

is to be automatically related to its 2D instance. You can also specify the ALL,
LINENO, LABELFILE modifiers to indicate the pipeline selection. All the
components in the selected pipelines will be related to their 2D instance, except
the components that have been manually related.
6. Press RETURN.
Example 1
Establishing the external RDBMS connection:
GENERATE PIPEDBASE ASSEMBLY Stage-01 USERTNAME user1 PASSWORD
***** <CR>
This example explains the method of logging into the external DBMS software
using the specified user name and password. The following message appears when
the correct password has not been issued:
External RDBMS login failed. Error: -1017
Example 2
Linking current part to the project DEMO:
SELECT RDBMS USER user1 PASSWORD user1 PROJECT DEMO <CR>
LINK RDBMS <CR>
This example explains the linking of a part to a specified project. The current
CADDS part must be linked to a project before using the GENERATE
PIPEDBASE command.
Example 3
Creating Ship T-58 as a component in the Project Component tree:
GENERATE PIPEDBASE ASSEMBLY cv SUBASSEMBLY t-58 TYPE ship<CR>
This example explains creation of a component named T-58 with the component
type SHIP, as a child of the existing higher level component CV, in the Project
Component relational database table. The following message will appear on
successful completion of the above command.
Project component T-58 has been written to RDBMS

GENERATE PIPEDBASE
Example 4
Creating Stage STAGE-01 as a component in the Project Component tree:
GENERATE PIPEDBASE ASSEMBLY t-58 SUBASSEMBLY stage-01 TYPE
stage<CR>
This example explains creation of a component named STAGE-01 with the

component type STAGE, as a child of the existing higher level component
T-58.The following message will appear on successful completion of the above
command.
Project component STAGE-01 has been written to RDBMS
Example 5
Creating spool database:
GENERATE PIPEDBASE ASSEMBLY stage-01 USERNAME user1 PASSWORD **

ALL <CR>

GENERATE PIPEDBASE
This example explains reading all the pipeline spools in the currently active part
and writing the extracted information into the external RDBMS tables, which are
associated with the project component STAGE-01.The following message will
appear on successful completion of the above command.
Spool number TEST-01-SPOOL#1 Appended
Example 6
Revoking drawing generation status:
GENERATE PIPEDBASE ASSEMBLY stage-01 USERNAME user1 PASSWORD *****
DRAW: Spool Label Model ent d1
In this example the digitized pipeline spool is identified in the pipeline spool
external RDBMS table. Its drawing generation flag is marked for inclusion.The
following message will appear on successful completion of this command.
Spool Number TEST-01-SPOOL#1 Drawing status enabled
Example 7
Disabling drawing generation:
NODRAW: Model ent d1
In this example the digitized pipeline spool is identified in the pipeline spool
external RDBMS table. Its drawing generation flag is marked for exclusion.The
following message will appear on successful completion of this command.
Spool Number TEST-01-SPOOL#1 Drawing status disabled
Example 8
Extracting the complete pipeline information:
GENERATE PIPEDBASE ASSEMBLY stage-01 USERNAME user1 PASSWORD
****** LINENO TEST-01 <CR>

GENERATE PIPEDBASE
This example explains the method of reading the complete information of the
pipeline identified by TEST-01 and storing the information in the existing
pipeline RDBMS tables which are associated with the project component
STAGE-01. The following message appears:
Pipeline number TEST-01 Appended
Example 9
Synchronizing the RDBMS for obsolete pipeline spools or pipelines:
ALL SYNCHRONIZE <CR>
This example explains the method of reading all the pipeline spools in the
currently active part and writing the extracted information into the existing
pipeline RDBMS tables, which are associated with the project component
STAGE-01. The information for the obsolete pipelines or pipeline spools are
removed. The following message appears on successful completion of the above
command:
Synchronizing the RDBMS database against the active part ....
RDBMS database synchronization completed. 5 obsolete objects

deleted .
Example 10
Deleting the pipeline network from the external database:
GENERATE PIPEDBASE LINENO Test-2-4-A7A DELETE:<CR>
This example explains the removal of information for the specified pipeline
network along with its components from the external RDBMS tables.
Example 11
Relating the pipe components in the external RDBMS:
GENERATE PIPEDBASE RELATE :d1,d2 <CR>
This example relates the digitized 2D schematic and 3D model pipe component in
the external RDBMS link tables.

GENERATE PIPEDBASE
Example 12
Executing the external unix shell script:
GENERATE PIPEDBASE SCRIPT
/usr/apl/cadds/data/cvaec/hvac/scrips/rep_line_list.sh <CR>
This example executes the external units shell script rep_line_list.sh and displays
the execution in the CADDS IPC window.
Example 13
Terminating the external RDBMS connection:
GENERATE PIPEDBASE DISCONNECT <CR>
This example explains the method of terminating the existing RDBMS connection.
Notes 1
1. The project related RDBMS tables will be a common database, which is
accessed by many other AEC applications like, HVAC, Advanced Structural
Modeling (ASM), Electrical Cable Design, and so on. Since any modification of
these tables may affect the other applications, it is advisable to restrict the
access rights for these tables to non-administrative and un-authorized users. In
a typical user environment the above restriction should also apply to, all the
system supplied scripts pertaining to the project related RDBMS table creation
and manipulation. See Project Information Tables on page B-4 for details of
project related RDBMS tables.
2. The DELETE modifier offers a certain level of functionality to synchronize the
CADDS model data and the external data stored in RDBMS tables. The
DELETE modifier should be used to correct minor errors like wrong pipeline
digitize, wrong input of assembly value, etc. It can be used in instances where
individual pipeline spools are deleted from the CADDS model and the
corresponding data in the RDBMS tables need to be deleted.
3. The DRAW and NODRAW modifiers offer the functionality to selectively
include / exclude the pipeline spools while processing for spool drawing
generation. Using these modifiers User will have the flexibility to exclude
design incomplete pipeline spools, from batch mode drawing generation
process.
4. The GENERATE PIPEDBASE command has a limit of 40 pipeline spool
elements per pipeline spool. Spools with larger number of elements should be
suitably broken down to smaller spool lines using the FITTYPE (value 70) and
CUTSPOOL properties at appropriate location on the pipeline spool.

GENERATE PIPEDBASE
5. The spool length and element co-ordinate values, stored in the external
RDBMS tables are normalized to the Meter linear units. Users intending to use
these extracted values in customized SQL commands should apply applicable
conversions to represent these values in the desired units.
Notes 2
1. The project related RDBMS tables will be a common database, which is
accessed by many other AEC applications link Advanced Structural
Modeling(ASM), Electrical Cable Design, etc... Since any modification of
these tables may affect the other applications, It is advisable to restrict the
access of these tables to un-authorized users.
2. DELETE modifier option can be used, clean up the RDBMS tables in
accordance with the model. Before a pipeline spool is deleted from the CADDS
model, the pertinent information in the pipeline spool and spool element
RDBMS tables can be deleted using this option.
3. DRAW and NODRAW modifiers can be utilized to control the pipe spool
drawing generation process. A pipeline spool for which the design is not yet
frozen, can be excluded from drawing generation using the NODRAW option.
After the design is frozen, DRAW modifier can be used to include the pipeline
spool for drawing generation.
4. The length of pipeline element and coordinates of pipe spool elements are
converted to meter, and stored in the pipeline spool and element tables.
5. The layer of the pipeline spool is extracted and stored in the pipeline spool
table. In DRAW PSPOOL command, pipelines will be draw in their original
layer based on this information, so that the hidden line removal(HLR) can
identify the category of the AEC component it is processing.

Description
Use this command to create both a specification (autoselection) and a parameter
file for the components required by your job specification.
A specification file lists components by generic name, pipe specification, size,

and end type; it is used by the command INSERT FITTING to automatically
select, scale, orient, and insert fittings into a pipeline.
A parameter file gives the dimensional data needed to define the
three-dimensional representation of each component used for detailing,
clearance checking, or surface generation. In the case of fittings whose
representations are parametrically scaled, a parameter file specifies the scales
used by the INSERT FITTING command.
First create an INFILE (pipe specification input file) from your pipe specification
sheet. This INFILE specifies the content and format of the specification and
parameter files created by GENERATE PSFILE.
A set of master catalogs is also required, containing all the data needed to define a
fitting for use by the following kinds of products:
pipeline construction
pipeline modeling
pipeline reporting
AEC Hidden Line Removal
Master catalogs list component information in accordance with ANSI and

DIN/ISO standards; you are provided some information in the cvpd/mcat
catalog. See the Piping Specification User Guide for more information on creating
piping specification files and master catalogs.
The GENERATE PSFILE command
1. Reads the INFILE and stores the information coded for a component.
2. Goes to the specified MCAT for additional dimensional data.
3. Provides the component information to the specification and parameter
(ASFILE and PAFILE) files being created.
4. Lists, in a nonmatching file (NMFILE), the components that are not found.

The following figure illustrates this process.
Figure 3-3 GENERATE PSFILE Process
Valid Modes
Model mode and Draw mode
Syntax
#n# GENERATE PSFILE ASFILE filename INFILE filename NMFILE filename
PAFILE filename [modifiers]

Modifiers
The following diagram shows the flow of GENERATE PSFILE modifiers. An
see the Preface.
follows.

1 ASFILE filename
(Default) (Required) (Autoselection File) Specifies the autoselection file to be

created or modified. Its contents are matching items: piping specification
entries that match those in the specified catalogs. The file name is limited to 60
characters. You can enter a file name as the first modifier; the system then
assumes it is an ASFILE name.
2 APPEND
Adds entries to the specified existing autoselection file. Since there is already a
header line on the existing file, do not include one in your input file.
2 DELETE
Replaces the specified existing autoselection file filename with a newly
generated autoselection file with matching items.
1 DIAGNOSE
Performs a diagnostic run on the input specification file. You can key in the
other modifiers as you normally would, but NMFILE and PAFILE are not
required. ASFILE is still required, although the ASFILE is not created. The file
name you specify is used to construct the name of the temporary file,
filename/_bcd/_asfn, where n is your task number.
1 INFILE filename
(Required) (Input File) Identifies the pipe specification input file. This file must
exist before the command can be used. The INFILE contains coded information
for creating an autoselection file with component entries for a pipe
specification. The file name is limited to 76 characters.
1 LISTIN
Lists each line of the INFILE before processing.
1 LISTREC
(List Record) Lists each reformatted line of input by showing the autoselection
line without scales or part names.
1 NDIAGNOSE
(Default) Deactivates the diagnostic usage of the command.

1 NLISTIN
(Default) INFILE lines are not listed.
1 NLISTREC
(Default) Reformatted input lines are not listed.
1 NMFILE filename
(Nonmatching File) Specifies the file to be created or modified for all

components not described in the master catalogs. Its contents are pipe
specification entries that do not match those in the specified catalog. You must
use the APPEND or DELETE modifier if the named file already exists. The file
name is limited to 60 characters.
2 APPEND
Adds entries to the specified nonmatching file.
2 DELETE
Replaces the specified, existing nonmatching file with the newly created
nonmatching file.
1 NVERIFY
(Default) Status report on files and modifiers is not provided.
1 PAFILE filename
(Parameter File) Specifies the parameter file to be created or modified. You

must use the APPEND or DELETE modifier if the named file already exists.
The file name is limited to 60 characters.
2 APPEND
Adds entries to the specified parameter file. When appending to an existing

PAFILE its header line is used. Do not include the header line at the top of your
input file.
2 DELETE
Replaces the specified existing parameter file with a newly created one.

1 VERIFY
Lists all the files and modifiers you have selected for use by GENERATE
PSFILE.
Procedure
The following is the procedure for using the GENERATE PSFILE command:
1. Create an INFILE from the pipe specification sheet.

Enter the command:
#n# GENERATE PSFILE ASFILE filename INFILE filename NMFILE filename
PAFILE filename [modifiers]
2. Specify GENERATE PSFILE, ASFILE and the names of the autoselection file,
INFILE, NMFILE, and PAFILE with their respective filenames. Use APPEND
or DELETE with any of the files that already exist. Add any optional modifiers.
3. Press RETURN.
The system responds:
TO CHANGE MODIFIER INPUT, ENTER A C. PRESS RETURN KEY
TO CONTINUE.
4. Press RETURN.
The command begins processing. After successfully generating stock numbers,
the system issues the following message:
GENERATE PSFILE EXECUTING CATALOG LOOKUP PHASE
When the processing is complete, the following message appears:
GENERATE PSFILE HAS EXECUTED SUCCESSFULLY.
The following is a piping specification INFILE for specification D2B,

corresponding to the piping specification sheet shown before. For information on
creating the INFILE, see the Piping Specification User Guide. The INFILE
references the master catalogs, as shown in the lines beginning with CATALOG
NAME =. These catalogs define the components used in the Piping Design
package. They reside in the cvpd/mcat catalog.
Sample Infile
Because of line length limitations in this book, the following two lines represent
the first header line of the INFILE.
TYPE SPEC SIZE ENDT SCLX SCLY SCLZ IFC#...
...NAME STK# &

This is one line header, 93 characters wide. NAME starts in column 61. In the
example above, the dots (....NAME) show where the two lines connect. Note that
this header contains the SIZE field header, which is sufficient for fittings involving
only a single-size reduction. An INFILE that codes double-reducing fittings would
contain NSIZ and BSIZ field headers between the SIZE and ENDT columns.
The rest of the INFILE is shown as it appears. The asterisks * in the sample
INFILE indicate comment lines, which help to explain the file.
STK# PARM & &
*
PIPE SPECIFICATION FILE
*
CC SIZE CODES = 0D, 0F, 01, 1D, 02, 03, 04, 06, 08, 10, 12
*
USERS TEXT CODES = 1/2, 3/4, 1, 1 1/2, 2, 3,4, 6, 8, 10,
12
SIZE CODES = 0D, 0F, 01, 1D, 02, 03, 04, 06, 08, 10, 12
*
CC ELBOW = ELR4, ELR9, ESR9, ESW4, ESW9
CC ANGLE VALVE = RVAL, ANGV
CC FIELD WELD = FWEL
CC TEE = STEE, RTEE, SLET,WLET,CROS
CC FLANGE = BLRJ, WNRJ
CC PIPE = PIPE
CC GASKET = GASK
CC VALVE = CHKV, GATV, GLBV
CC BOLT = STUD
CC GENERAL = CAPP, CPFW, CPRW, CRED, ERED, NIPL, PLHX, UNIO
*ELBOW = ELR4, ELR9, ESR9, ESW4, ESW9
*
ANGLE VALVE = RVAL, ANGV
FIELD WELD = FWEL
TEE = STEE, RTEE, SLET,
WLET, CROS
FLANGE = BLRJ, WNRJ
PIPE = PIPE
GASKET = GASK
VALVE = CHKV, GATV, GLBV
BOLT = STUD
* WAFER = BUTV
RELIEF VALVE = RVAL
GENERAL = CAPP, CPFW, CPRW, CRED, ERED, NIPL,
PLHX, UNIO, CPRC, FLAN, BRAN
ASSEMBLY = VENT, DRAN, PI, TI
*
CC ENDS = BW, RJ, RJ, BE, PE, SW, PBE, POE, TOE, SC
*
ENDS = BW,RJ,RJ,BE,PE,SW,PE,P,T,SC
*
ENDT TEXT CODES = BW, F6RJ, G6RJ, BE,PE, SWF, PBE, POE, TOE, SCF
*
* SCHEDULE/PR VALUES

*
CC SCHEDULE/RATING = 40,80,600,1500,6000,STD
*
SCHEDULE/RATING = 40,80,600,1500,6000,STD
*
INPUT RECORD FORMAT
INPUT = SNAME,SR/TC,END,RATE,MAT
STOCK NUMBER FORMAT
*
* THE FOLLOWING STATEMENT DEFINES THE STOCK NUMBER TO BE IN
* THE FORMAT WHICH IS NO LONGER REQUIRED.
*
STK NO = SNAME,END,NEND,RATE,MAT,DELIM1,SIZE,NSIZE
*
DELIM1 = -
*
SPECIFICATION =D2B
*
*
WNRJ, 0D-12, F6RJ#BW, 600, BE
/S
BLRJ, 0D-12, F6RJ, 600, BE
* VALVES
*
CATALOG NAME = CVPD.MCAT.CHKV
*
CHKV, 02-12, BW, 600, BB
CHKV, 0D-1D, SWF, 1500, BE
*
CATALOG NAME= CVPD.MCAT.GATV
*
GATV, 0D-1D, SWF, 1500, BE
GATV, 02-12, BW, 600, BB
*
CATALOG NAME= CVPD.MCAT.GLBV
*
GLBV, 02-06, BW, 600, BB
GLBV, 0D-1D, SWF, 1500, BE
*
* GASKETS
*
CATALOG NAME = CVPD.MCAT.GASKET
*
GASK, 0D-12, G6RJ, 600, BC
*
* BOLTS
*
CATALOG NAME = CVPD.MCAT.STUDBOLT
*
STUD, 0D-12, F6RJ, 600, AE
*
* FITTINGS
*
CATALOG NAME = CVPD.MCAT.SWFITT

*
UNIO, 0D-1D, SWF, 6000, BE
*
SELECTION NAME = CPLG
CPFW, 0D-1D, SWF, 6000, BE
/S
ESW4, 0D-1D, SWF, 6000, BE
ESW9, 0D-1D, SWF, 6000, BE
*
SELECTION NAME = BRAN
STEE, 0D-1D, SWF, 6000, BE
/S
**
CATALOG NAME =CVPD.MCAT.SCFITT
*
CAPP, 0D-1D, SCF, 6000, BE
*
* BUTT WELD FITTINGS
CATALOG NAME = CVPD.MCAT.PIPE

*
PIPE, 0D-1D, PE, 80, BA
PIPE, 02-12, BE, 40, BA
NIPL, 0D-1D, PBE, 80, BA
NIPL, 0D-1D, POE#TOE, 80, BA
*
*FLANGES
CATALOG NAME = CVPD.MCAT.FLANGE
*
SELECTION NAME FOR FLANGES = FLAN
*
CATALOG NAME = CVPD.MCAT.BWFITT
*
ELR9, 02-12, BW, TMP, BD
ESR9, 02-12, BW, TMP, BD
ELR4, 02-12, BW, TMP, BD
*
STEE, 02-12, BW, TMP, BD
/S
CAPP, 02-12, BW, TMP, BD
*
* REDUCING FITTINGS
*
TABLE = BR
*
* R=SW REDUCING TEE
* S=SOCKOLET
* W=WELDOLET
*
A B C D E F G HIJK*
*
*
0D - A

0F - B R
01 - C R R
1D - D R R R
02 - E S S S S
03 - F S S S S W
04 - G S S S S W W
06 - H S S S S W W W
08 - I S S S S W W WW
10 - J S S S S W W WWW
12 - K S S S S W W WWW W*
TABLE = RE
*
* C=REDUCING COUPLING
* R=CONCENTRIC OR ECCENTRIC REDUCER
*
A B C D E F G HIJK*
*
*
OD - A
OF - B C
01 - C C C
1D - D C C C
02 - E R R R
03 - F R R
04 - G R R R
06 - H R R
08 - I RR
10 - J RRR
12 - K RR R
*
/T
*
CATALOG NAME =CVPD.MCAT.SWFITT
USE TABLE = BR
RTEE, R, SWF, 6000, BE
/T
CATALOG NAME=CVPD.MCAT.OLET
*
USE TABLE = BR
*
SLET, S, SWF, 6000, BE
WLET, W, BW, STD, BD
/T
/S
CATALOG NAME = CVPD.MCAT.SWFITT
USE TABLE = RE
*
CPRW, C, SWF, 6000, BE
/T
*
CATALOG NAME =CVPD.MCAT.BWFITT
*

USE TABLE=RE
*
CRED-ERED, R, BW, TMP, BD
/T
*
* ASSEMBLIES
*
DRAN, 0D, DA1,,
DRAN, 0F, DA2,,
DRAN, 01, DA3,,
DRAN, 1D, DA4,,
DRAN, 02-12, DA5,,
VENT, 0D, VA1,,
VENT, 0F, VA2,,
VENT, 01, VA3,,
VENT, 1D, VA4,,
VENT, 02-12, VA5,,
PI, 0D, PA1,,
PI, 0F, PA2,,
PI, 01, PA3,,
PI, 1D, PA4,,*
PI, 02-12, PA5,,
TI, 03-12, TA1,,
*
ASSEMBLY LIST SECTION
*
DA1,BRAN NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE SCF
DA2,BRAN BSIZE 0D NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE
SCF
DA3,BRAN BSIZE 0D NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE
SCF
DA4,BRAN BSIZE 0F NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE
SCF
DA5,BRAN BSIZE 0F NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE
SCF
*
VA1,BRAN NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE SCF
VA2,BRAN BSIZE 0D NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE
SCF
VA3,BRAN BSIZE 0D NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE
SCF
VA4,BRAN BSIZE 0F NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE
SCF
VA5,BRAN BSIZE 0F NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE
SCF
*
PA1,BRAN NIPL FACE PBE CPRW NSIZE 01 NIPL FACE PBE GATV NIPL FACE
PBE FLAN
PA2,BRAN NIPL FACE PBE CPRW NSIZE 01 NIPL FACE PBE GATV NIPL FACE
PBE FLAN
PA3,BRAN NIPL FACE PBE GATV NIPL FACE PBE FLAN
PA4,BRAN BSIZE 01 NIPL FACE PBE GATV NIPL FACE PBE FLAN
PA5,BRAN BSIZE 01 NIPL FACE PBE GATV NIPL FLAN
*

TA1,BRAN BSIZE 1D NIPL FACE PBE FLAN

/A
* EOF
Sample Autoselection and Parameter Files

Using the following command, create both an autoselection and a parameter file
from the coded pipe specification file (INFILE):
#n# GENERATE PSFILE INFILE EXAMPLE.INFILE.D2B ASFILE

EXAMPLE.ASFILE.D2B PAFILE EXAMPLE.PAFILE.D2B NMFILE
EXAMPLE.NMFILE.D2B
The command uses the information in the INFILE and refers to the catalogs
named in that file to create the piping specification files.
The components not covered by those catalogs are listed in the NMFILE. The
command creates the single-size autoselection and parameter files shown in part
on the following pages. See the Piping Specification User Guide for an example of
a three-size specification (autoselection) file with double-reducing fittings.
The system responds:

TO CHANGE MODIFIER INPUT, ENTER A C. PRESS THE RETURN KEY TO
CONTINUE.
PSFILE EXECUTING CATALOG LOOKUP PHASE
GENERATE PSFILE HAS EXECUTED SUCCESSFULLY
The example/asfile/d2b autoselection file (shown in part below) results.

Note that the file is not automatically sorted.
TYPE SPEC SIZE ENDT SCLX SCLY SCLZ IFC# NAME STK#
&****SNAM-END-NEND-RATE-MAT-DELI-SIZE-NSIZ-
****04-02-02-01-02-02-
PIPE D2B 1/2PE0.550.84 0 P G PIPE PIPEPE80BA-OD

PIPE D2B 3/4PE0.741.05 0 P G PIPE PIPEPE80BA-OF
PIPE D2B 1PE0.96 1.32 0 P G PIPE PIPEPE80BA-01
PIPE D2B 1.1/2PE1.501.900 P G PIPE PIPEPE80BA-1D
PIPE D2B 2BE2.07 2.38 0 P G PIPE PIPEBE40BQ-02
PIPE D2B 3BE3.07 3.50 0 P G PIPE PIPEBE40BA-03
PIPE D2B 10BE10.0210.750 P G PIPE PIPEBE40BA-10
PIPE D2B 12BE11.9412.750 P G PIPE PIPEBE40BA-12
NIPL D2B 1/2PBE4.000.840 G CVPD.F.NIPLNIPLPE80BA-0D
NIPL D2B 3/4PBE4.001.050 G CVPD.F.NIPLNIPLPE80BA-0F
NIPL D2B 1PBE4.001.35 0 G CVPD.F.NIPLNIPLPE80BA-01

NIPL D2B 1.1/2PBE4.00.900 G CVPD.F.NIPLNIPLPE80BA-1D

NIPL D2B 1/2POE TOE4.00.0840 G CVPD.F.NIPLNIPLPT80BA-0D
NIPL D2B 3/4POE TOE4.001.050 G CVPD.F.NIPLNIPLPT80BA-0F
NIPL D2B 1POE TOE4.001.320 G CVPD.F.NIPLNIPLPT80BA-01
NIPL D2B 1.1/2POE TOE4.001.900 G CVPD.F.NIPLNIPLPT80BA-1D
FLAN D2B 1/2F6RJ BW2.283.750 FF G CVPD.F.WNRJWNRJRJBW600BE-0D
FLAN D2B 3/4F6RJ BW2.504.630 FF G CVPD.F.WNRJWNRJRJBW600BE-0F
FLAN D2B 1F6RJ BW2.694.880 FF G CVPD.F.WNRJWNRJRJBW600BE-01
FLAN D2B 1.1/2F6RJ BW3.006.130FF G CVPD.F.WNRJWNRJRJBW600BE-1D
FLAN D2B 4F6RJ BW3.8110.750 FF G CVDP.F.WNRJWNRJRJBW600BE-04
FLAN D2B 10F6RJ BW5.1920.000 FF G CVDP.F.WNRJWNRJRJBW600BE-10
BLRJ D2B 1/2F6RJ0.783.750 FF G CVPD.F.BLRJBLRJRJ600BE-0D
BLRJ D2B 3/4F6RJ0.884.630 FF G CVPD.F.BLRJBLRJRJ600BE-0F
BLRJ D2B 1F6RJ0.944.88 0 FF G CVPD.F.BLRJBLRJRJ600BE-01
BLRJ D2B 1.1/2F6RJ1.136.130 FF G CVPD.F.BLRJBLRJRJ600BE-1D
BLRJ D2B 2F6RJ1.316.50 0 FF G CVPD.F.BLRJBLRJRJ600BE-02
BLRJ D2B 3F6RJ1.568.25 0 FF G CVPD.F.BLRJBLRJRJ600B2-03
BLRJ D2B 4F6RJ1.8110.750 FF G CVPD.F.BLRJBLRJRJ600BE-04
CHKV D2B 2BW11.502.38 0 V G CVPD.F.CHBWCHKVBW600BB-02
Because the INFILE contains assemblies, GENERATE PSFILE creates an

assembly file called example/asfile/d2b/assembly (see below). An
assembly file is required for the automatic selection and insertion of assemblies.
DA1 BRAN NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE SCF
DA2 BRAN BSIZE 1/2 NIPL FACE PBE GATV NIPL FACE POE#TOE CAPP FACE
SCF
SCF
SCF
SCF
VA1 BRAN NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE SCF
VA2 BRAN BSIZE 1/2 NIPL FACE PBE GLBV NIPL FACE POE#TOE CAPP FACE
SCF
SCF
SCF

SCF
PA1 BRAN NIPL FACE PBE CPRW NSIZE 1 NIPL FACE PBE GATV NIPL FACE
PBE FLAN
PA2 BRAN NIPL FACE PBE CPRW NSIZE 1 NIPL FACE PBE GATV NIPL FACE
PBE FLAN
PA3 BRAN NIPL FACE PBE GATV NIPL FACE PBE FLAN
PA4 BRAN BSIZE 1 NIPL FACE PBE GATV NIPL FACE PBE FLAN
PA5 BRAN BSIZE 1 NIPL FACE PBE GATV NIPL FLAN
TA1 BRAN BSIZE 1.1/2 NIPL FACE PBE FLAN
The parameter file example/pafile/d2b (shown in part) is also created by the

command. Sort the file before you use it for detailing or interference checking. Be
sure to stay within the maximum column width of 132 characters.
STK# PARM
PIPEPE80BA-0D0.55 , 0.84
PIPEPE80BA-0F0.74 , 1.05
PIPEPE80BA-010.96 , 1.32
PIPEPE80BA-1D1.50 , 1.90
PIPEBE40BA-022.07 , 2.38
PIPEBE40BA-033.07 , 3.50
PIPEBE40BA-044.03 , 4.50
PIPEBE40BA-066.07 , 6.63
PIPEBE40BA-087.98 , 8.63
PIPEBE40BA-1010.02,10.75
PIPEBE40BA-1211.94,12.75
NIPLPE80BA-0D4.00 , 0.84
NIPLPE80BA-0F4.00 , 1.05
NIPLPE80BA-014.00 , 1.32
NIPLPE80BA-1D4.00 , 1.90
NIPLPT80BA-0D4.00 , 0.84
NIPLPT80BA-0F4.00 , 1.05
NIPLPT80BA-014.00 , 1.32
NIPLPT80BA-1D4.00 , 1.90
WNRJRJBW600BE-0D2.28 , 3.75, 0.78, 0.84
WNRJRJBW600BE-0F2.50 , 4.63, 0.88, 1.05
WNRJRJBW600BE-012.69 , 4.88, 0.94, 1.32
WNRJRJBW600BE-1D3.00 , 6.13, 1.13, 1.90
WNRJRJBW600BE-023.19 , 6.50, 1.31, 2.38
WNRJRJBW600BE-033.56 , 8.25, 1.56, 3.50
WNRJRJBW600BE-043.81 ,10.75, 1.81, 4.50
WNRJRJBW600BE-064.38 ,14.00, 2.19, 6.63
WNRJRJBW600BE-084.94 ,16.50, 2.50, 8.63
WNRJRJBW600BE-105.19 ,20.00, 2.81,10.75
WNRJRJBW600BE-125.69 ,22.00, 2.94,12.75
BLRJRJ600BE-0D0.78 , 3.75
BLRJRJ600BE-0F0.88 , 4.63
BLRJRJ600BE-010.94 , 4.88
BLRJRJ600BE-1D1.13 , 6.13
BLRJRJ600BE-021.31 , 6.50
BLRJRJ600BE-031.56 , 8.25
BLRJRJ600BE-041.81 ,10.75

BLRJRJ600BE-062.19 ,14.00
BLRJRJ600BE-082.50 ,16.50
BLRJRJ600BE-102.81 ,20.00
BLRJRJ600BE-122.94 ,22.00
CHKVBW600BB-0211.50, 2.38
CHKVBW600BB-0314.00, 3.50
CHKVBW600BB-0417.00, 4.50
CHKVBW600BB-0622.00, 6.63
CHKVBW600BB-0826.00, 8.63
Items from the pipe specification file that do not match catalog entries would be
sent to the nonmatching file example/nmfile/d2b. Since there are no
nonmatches, this file is empty.
Notes
The following general notes will further help you to use the GENERATE PSFILE
command.
1. The GENERATE PSFILE command creates an Insert Fitting Code (IFC#) that
it writes to the ASFILE. The code identifies
Orientation component
Location component
End type component
Automatic insertion of flanges and gaskets
The Insert Fitting Code is under the heading IFC#. There are four columns to the
code. Each column contains a single character that represents
Component type (Column one)

A single character in column one identifies the type of component. The
following table lists the recognized types of components, the classification
of each, and the single character that identifies that component in column
one of the IFC#.
Table 3-1 Component Types for the Insert Fitting Code
Component Type Component Classification Type Code

Bolts BOLT B
Elbows ELBOW E
Tees, branch connections TEE T
Assemblies ASSEMBLY A
Valves VALVE V
Flanges FLANGE F
Gaskets GASKET G

Table 3-1 Component Types for the Insert Fitting Code
Component Type Component Classification Type Code

Angle Valves, Corner Valves ANGLE VALVE C
Field Welds FIELD WELD S
Pipe PIPE P
Any other type GENERAL blank
End type (Column two)

A single character in column two identifies the end type.
F represents a flanged end.
W represents a welded end.
Wafered or relief valve (Column three)
A single character in column three identifies the valve type.
W represents a wafered component
R represents a relief valve
L represents an elbowlet
Gaskets, yes or no (Column four)
A character is inserted into column four only if the component requires
flanges.
G appears if a gasket is required.
For example, an IFC# of EFRG represents an elbow (E) with a flanged end (F)
that has a relief valve (R) requiring a gasket (G).
2. The autoselection file for fittings contains either one or three columns for size
data. The maximum width is 148 for either; all nonsize headers are the same.
The following rules apply to three-size files:
a. There is an 18-character maximum for the size
fields (SIZE, NSIZ, BSIZ).
b. The SIZE field can contain only one size.
c. SIZE must always be greater than NSIZ.
d. BSIZ can be greater or less than SIZE.
The following table lists the storage limits for GENERATE PSFILE. There is a
132-character limit that can prevent all the available characters from being used in
a single field.

Table 3-2 Storage Limits for GENERATE PSFILE
Max. No Max No. Characters

Keywords Codes per Codes Comments
Any Input line 132 characters
ELBOW 24 8 Note 1
ELBOWLET 7 8 Note 1
ANGLE VALVE 10 8 Note 1
FIELD WELD 7 8 Note 1
TEE 30 8 Note 1
ASSEMBLY 40 8 Note 1
FLANGE 50 8 Note 1
PIPE 7 8 Note 1
GASKET 7 8 Note 1
VALVE 60 8 Note 1
WAFER 10 8 Note 1
BOLT 8 8 Note 1
GENERAL 50 8 Note 1
CC ENDS 45 4 Note 1
ENDT 45 12 Note 1
ENDS 45 12 Note 1
CC SIZE CODES 40 8
USERS TEXT CODES 40 12
SIZE CODES 40 12
INPUT 120 Note 2
STK NO 120 Note 3
DELIM1 to DELIM9 9 16 Must be on one line
SPECIFICATION 1 30 Must be on one line
TABLE - 56
USE TABLE - 56
USE STD TABLE - 56 (filename) Must be on one line
PART NAME - 30
SELECTION NAME - 30 Must be on one line
CATALOG NAME - 70 (filename)
INSERT - 70 (filename)
SCHEDULE/RATING 25 8 Note 1
Please note: STK NO cannot exceed the length of stock number that is
allowed by field width as defined in the header line of your ASFILE (specification
file).

The maximum number of codes is based on four-character codes. The maximum

number of codes varies with code length.
The maximum number of fields is ten, including NGASK.

GENERATE SPOOL
GENERATE SPOOL
Description
Use this command to automatically break a pipeline into spool pieces. Each spool
piece will have an associated label and will therefore become an independent
pipeline. The command automatically generates a spool piece label and increments
the spool number based on user input and/or default values. Size and specification
changes are automatically reflected in the newly created pipeline labels.
This command also allows you to combine the individual pipeline spools and
reconstruct the original pipeline, from which the individual spools were created.
These spool legends that were created using default spool generation values, will
automatically be deleted.
The pipeline spool pieces with the associated labels are used by the GENERATE
PIPEDBASE command for external database generation and DRAW PSPOOL
command for automatic pipeline spool fabrication drawing generation.
The GENERATE SPOOL command places the TERMNAM property at the

corresponding connect nodes under the following circumstances:
Flanged Fittings: A fitting with a cnode having an ENDTYPE property that starts
with F indicates a pipeline break point.
Screwed Fittings: A fitting with a cnode having an ENDTYPE property that

starts with S indicates a pipeline break point.
Field Welds: A cnode with a FITTYPE property of 70 indicates a pipeline break

point.
CUTSPOOL property: Any cnode with the CUTSPOOL property indicates a

pipeline break point.
A spool is a single piece of pipe comprising of straight segments and bends.
Hence, you can also spool pipelines by defining the following parameters:
The maximum spool length

The maximum number of bends in a spool
Please note: Spool a pipeline using the above parameters only if the
SPOOLMAX or the BENDMAX modifiers of the commands GENERATE
SPOOL or SELECT PPARAMETERS CHECK are set.

GENERATE SPOOL
If the values of both the SPOOLMAX and the BENDMAX modifiers are
specified, the GENERATE SPOOL command spools the pipeline based on the
cutting location that is calculated automatically. This is decided by the above two
modifiers. Reconstruct the spooled pipeline using the GENERATE SPOOL
RECONSTRUCT command.
Calculate the cutting location based on the following rules:
The length of the pipe between its starting point and the calculated cutting
location should not be greater than the maximum spool length. The
SPOOLMAX modifier of the command GENERATE SPOOL or SELECT
PPARAMETERS sets the maximum spool length.
The pipe length of the generated pipe pieces after spooling should not be less
than the minimum spool length.
The number of bends in a pipe between the starting point to the calculated
cutting location should not be greater than the maximum number of bends. The
BENDMAX modifier of the command GENERATE SPOOL or the SELECT
PPARAMETERS command sets the maximum number of bends.
The calculated cutting location should not be located on the bend piece.

GENERATE SPOOL
The calculated cutting location should have a minimum clearance of the

distance equal to the clamp length of the bends on both the sides.
While reconstructing the pipeline, the TERMNAM property placed on the connect
nodes by the spool generation is removed. The individual pipeline spool labels are
deleted and the reconstructed pipeline has the original label. Also, if the pipeline is
broken at the calculated cutting location by defining the maximum spool length or
the maximum number of bends, the connect nodes inserted on the pipeline will be
removed during reconstruction.
The GENERATE SPOOL command automatically creates a new pipeline label for
the pipe spool. The label format must be defined in the currently selected directory
file (drfile). The required format in the directory file can be one of the following:
SIZE-SPEC-MNEMONIC-NUMBER-INS-SPOOL
SIZE-SPEC-MNEMONIC-NUMBER-SPOOL-INS
The SPOOL field should only be used when creating spools using the GENERATE
SPOOL command. The default spool field string is SPOOL#1, as defined in the
modifier table. This default can be changed in the modifier table, or can be
overridden by user input using command modifiers.
The spool string must contain a numeric value in order to be automatically

incremented by the command. If no numeric value exists, then the string value will
not be incremented. If more than one numeric value exists in the string, then only
the first is incremented. For example, the following strings are incremented
accordingly:
SPOOL#1 -> SPOOL#2
SPOOL -> SPOOL
SPO1OL-> SPO2OL
S1POO2L-> S2POO2L

GENERATE SPOOL
The following original pipeline labels will generate the corresponding results:
Input Pipe Label -> Resulting Pipe Spool Label

100-AB16-PIPE-001 -> 100-AB16-PIPE-001-SPOOL#1 etc.
100-AB16-PIPE-001-INSUL -> 100-AB16-PIPE-001-INSUL-SPOOL#1 etc.
Please note: The optional fields in the label format like INS and SPOOL
shall be specified only at the end of the label format.
To reduce drawing clutter, the pipe spool labels are blanked and replaced by draw
mode label text, which contains the text of the spool field only. For example, in the
above cases a draw mode label of the format SPOOL#1 would be attached to the
beginning of the pipeline spool.
In order to correlate the pipeline spool labels with the draw mode label text, a pipe
spool legend is automatically created. This legend is a draw mode list of all the
pipe spool labels generated for the part. An example legend is as follows:
100-AB16-PIPE-001-SPOOL#1
100-AB16-PIPE-001-SPOOL#2
80-AB16-PIPE-001-SPOOL#3 (in the case of a size change) etc.
The text attributes can be set by a text node with the SPOOLIST property, using
SELECT TEXT or by modifier input. In the first case, the tnode will also provide
the location of the lower left hand corner of the pipe spool legend table.
Optionally, generate the complete pipeline spool labels using the modifier
NOLEGEND. In this case the draw mode label text legend is not created.
For reconstructing a pipeline, specify the pipelines either by digitizing a

component of the pipeline spool, or by specifying the line number. Optionally,
reconstruct all the pipeline spools in the active part.
Any pipeline segment (nodal line) can be digitized and multiple digitizes are
allowed. Additionally, the window getdata modifier (WIN) can be used to specify
pipelines that are inside or pass through the identified window area are processed.
Valid Modes
Model mode

GENERATE SPOOL
Syntax
#n# GENERATE SPOOL SPOOLMAX <spoolmax> BENDMAX <bendmax>
[modifiers]: Model ent <getdata>
#n# GENERATE SPOOL ALL SPOOLMAX <spoolmax> BENDMAX <bendmax>

[modifiers] <CR>
#n# GENERATE SPOOL LINENO SPOOLMAX <spoolmax> BENDMAX <bendmax>

<line_number> [modifiers] <CR>
#n# GENERATE SPOOL RECONSTRUCT [modifiers]: Model ent <getdata>
#n# GENERATE SPOOL RECONSTRUCT ALL <CR>
#n# GENERATE SPOOL RECONSTRUCT LINENO <line_number> [modifiers]

<CR>

GENERATE SPOOL
Modifiers
The following diagram shows the flow of GENERATE SPOOL modifiers. An
see the Preface.

GENERATE SPOOL
1 ALL flag
Specifies that all the pipelines in the current part are to be processed.
1 BENDMAX n
Specifies the maximum number of bends allowed for spooling the pipeline. This
modifier accepts any positive integer value.
This modifier is mutually exclusive with the RECONSTRUCT modifier.
1 HGT text height
Specifies the text height in drawing units. By default, text height value set using
the SELECT TEXT command is used. This modifier is mutually exclusive with
the NOLEGEND modifier.
1 INCR increment
Specifies the value to be used when incrementing the pipe spool field. The
default is 1.
1 INTERACTIVE flag
Inserts the spool cut mark on the pipeline for creating a spool. When you use
this modifier, you are prompted for the confirmation, modification, or rejection
of each spool cut mark that is calculated for creating a spool on the pipeline at
the command line.
1 LAYER layer
Specifies the layer of the created pipeline labels and pipe spool legend.
1 LINENO pipeline label, limit=40, list=10
Identifies the pipelines to be split into spools by their line numbers. Enter the
complete pipeline label or a subset of the fields in the pipeline label, as specified
in the LINENO-FORMAT field of the currently active directory file. You can
enter multiple line numbers separated by comma. A maximum of 10 pipeline
numbers can be specified. This modifier is mutually exclusive with the ALL
modifier.

GENERATE SPOOL
1 NOLEGEND flag
Specifies that the pipeline spool label legend need not be created. When this
modifier is used, full format labels are created according to the LABEL format
specified in the currently active directory file. These labels are model mode
entities and are placed near the first nodal line of each newly created pipe
spools.
This modifier is mutually exclusive with HGT and WDT modifiers. The
pipeline spool labels are created in model mode, based on the current model
mode text parameters, as specified using the SELECT TEXT command.
1 EXTENDMAX flag
Checks if part of the pipe extending from the center of the guide of the bending
machine is likely to collide any other component or part of the machine in the
vicinity of the bending machine while constructing spools.
1 RECONSTRUCT flag
Specifies that the selected pipeline spool will be combined with the rest of its
peer spools to reconstruct the original pipeline. The individual pipeline spool
labels will be removed and the original parent pipeline label will be assigned to
the first nodal line of the reconstructed pipeline.
This modifier is exclusive with HGT, INCR, LAYER, NOLEGEND, START
and WDT.
1 SPOOLMAX x
Specifies the maximum spool length allowed for spooling the pipeline. This
modifier accepts any positive double value equivalent in the active part model
units.
1 START start spool field
Specifies the starting pipeline spool field to be used in the pipeline spool label.
The default is SPOOL#1.
1 WDT text width
Specifies the text width in drawing units. By default, text width value set using
the SELECT TEXT command is used. This modifier is mutually exclusive with
the NOLEGEND modifier.

GENERATE SPOOL
Procedure 1
You must carry out the following steps before you are ready to invoke the
GENERATE SPOOL command.
1. Activate the part and appropriate drawing with the required pipeline model.
2. Select the Model mode.
3. Specify the directory file name which defines the label format with the SPOOL
field for pipeline spool creation, using the SELECT PPARAMETERS PIPING
DRFILE option.
4. At locations where you want to force a spool piece generation, insert the
FITTYPE property with a value of 70 or insert the CUTSPOOL property. Note
that flange locations with an ENDTYPE property value starting with a F
character will be automatically selected as spool piece termination location.
5. To generate short form labels with a legend, using the draw mode text
parameters for label text creation, use the SELECT MODE DRAW and SLECT
TEXT commands to specify the draw mode text parameters.
6. To generate full format labels in the model mode, using the model mode text
parameters, use the SELECT MODE MODEL and SELECT TEXT commands
to specify the model mode text parameters.
Procedure 2
To generate pipeline spools with short form labels and to create a label legend, by
digitizing pipelines,
1. Enter GENERATE SPOOL command.
2. Specify the draw mode text width and height, using the WDT and HGT
modifiers respectively. If these modifiers are not issued, the currently active
DRAW mode text parameters will be used.
3. Enter other modifiers like, START, LAYER etc.,.
4. Enter a Colon.
5. Digitize the pipelines to be split into spool pieces.
6. Press RETURN.

GENERATE SPOOL
Procedure 3
To generate pipeline spools with short form labels and to create the label legend,
by specifying pipeline numbers,
2. Specify the draw mode text width and height, using the WDT and HGT
modifiers respectively. If these modifiers are not issued, the currently active
DRAW mode text parameters will be used.
3. Enter the LINENO modifier and specify upto 10 line number values separated
by comma. Line number values can be full pipeline label strings or label strings
as specified by the LINENO-FORMAT field of the active directory file.
5. Press RETURN.
Procedure 4
To generate pipeline spools with full format labels and no legend, by digitizing
pipelines:
2. Enter the NOLEGEND modifier.
4. Enter a Colon.
5. Digitize the pipelines to be split into spool pieces.
6. Press RETURN.
Procedure 5
To generate pipeline spools with full format labels and no legend, by specifying
pipeline numbers:

5. Press RETURN.

GENERATE SPOOL
Procedure 6
To generate pipeline spools with no legend by specifying the maximum spool
length and the maximum number of bends.
1. Enter the GENERATE SPOOL command.
2. Enter the SPOOLMAX modifier and specify a positive double value.
3. Enter the BENDMAX modifier and specify a positive integer value.
by comma.
6. Enter other modifiers which include START and LAYER.
7. Press RETURN.
Procedure 7
To reconstruct the original pipeline from the individual pipeline spools:

2. Enter the RECONSTRUCT modifier.
3. Enter a Colon.
4. Digitize any one of the pipeline spools whose parent pipeline needs to be
reconstructed.
5. Press RETURN
Procedure 8
To check during bending that a part of the pipeline extending from the center of the
guide of the bending machine does not collide or hit with the ground or any other
component or part of the machine in the vicinity of the bending machine:

OR
Enter the ALL modifier to specify that all the pipelines in the current part are to
be processed.
3. Enter the INTERACTIVE modifier to insert the spool cut mark on the pipeline
for creating a spool.

GENERATE SPOOL
4. Enter the NOLEGEND modifier, if required.

5. Enter other modifiers like, START, INCR, and so on.
6. Enter the EXTENDMAX modifier and specify a positive integer value.
7. Press RETURN.
Example 1
Spool labels with legend:
GENERATE SPOOL START SPOOL#1 HGT 2 WDT1.5:Model ent d1 <CR>
This example illustrates breaking of the digitized pipeline into individual spool
pieces and creation of the short form of the label with only the SPOOL field
(SPOOL#1, SPOOL#2, etc.), near the first nodal line of each spool.

GENERATE SPOOL
A legend having all the created pipeline spool labels will be placed at the lower left
corder of the drawing by default. If a text node with SPOOLIST property is
available in the part, then the lower left corner of the legend will be positioned at
the text node location.
Note the size change in the SIZE field of the created labels.

GENERATE SPOOL
Example 2
Spool labels without legend:
GENERATE SPOOL START SPOOL#1 NOLEGEND: Model ent d1 <CR>
This example illustrates breaking of the digitized pipeline into individual spool
pieces and creation of spool labels. Since NOLEGEND option is selected, the
short form labels and legend table are not created. Instead complete pipeline spool
labels will be generated and placed near the first nodal line of each spool.
The first spool label consists of SPOOL field value as SPOOL#1 and the
subsequent SPOOL field values will be SPOOL#2, SPOOL#3, etc.
Note the size change in the SIZE field of the created labels.

GENERATE SPOOL
Example 3
Spool labels with legend
GENERATE SPOOL RECONSTRUCT:Model ENT d1 <CR>
This example illustrates connecting of the digitized pipeline spools with other
individual spool pieces and reconstructing the original pipeline. The original
pipeline label is attached to the first nodal line of the first spool.
The legend texts associated with the selected spools that were created with default
legend option will be deleted.

GENERATE SPOOL
The following figure shows the pipeline reconstructed from the individual pipeline
spools.

GENERATE SPOOL
Example 4
Spool labels without legend.
GENERATE SPOOL RECONSTRUCT:Model ent d1 <CR>

GENERATE SPOOL
This example illustrates the connection of the digitized pipeline spools with other
individual spool pieces and reconstructing the original pipeline. The original
pipeline label is attached to the first nodal line of the first spool.

GENERATE SPOOL
Example 5
Spool labels with legend. Spooling the pipeline by specifying the maximum spool
length and the maximum number of bends.
GENERATE SPOOL SPOOLMAX 10.0 BENDMAX 1 LINENO <TEST-01> <CR>
This example illustrates the breaking of the pipeline based on the values specified
by the SPOOLMAX and the BENDMAX modifiers. The length specified by the
SPOOLMAX modifier exceeds the length at the point of clamp length, before the
start of the second bend. The bend value is specified by the BENDMAX modifier.
Hence, the cutting location is decided by the BENDMAX modifier. The pipeline is
spooled at a distance of the clamp length before the start of the second bend piece.

GENERATE SPOOL
The following figure shows a single bend piece. The length of the resulting pipe
segment is less than the value specified by the SPOOLMAX modifier.
Example 6
Spool labels without legend. Spooling the pipeline by specifying the maximum
spool length and the maximum number of bends.
GENERATE SPOOL SPOOLMAX 7.5 BENDMAX 1 LINENO NOLEGEND <TEST-01>
<CR>

GENERATE SPOOL
In this example, the length specified by the SPOOLMAX modifier is less than the
length at the point of clamp length before the start of the second bend. The value of
the bend is specified by the BENDMAX modifier. Hence the cutting location is
based on the value specified by the SPOOLMAX modifier.

Description
Use this command to insert pipe slope symbols in the pipe segments which are
travelling or sloped at an angle in or out of the current view.
You can specify the radius of the arc symbol and interval between adjacent
symbols. The orientation of the inserted slope symbols indicates the direction of
sloping.
Valid Modes
Syntax
#n# GENERATE SPSYMBOL [modifiers] ALL or LINENO or:getdata
Modifiers
The following diagram shows the flow of GENERATE SPSYMBOL modifiers.


follows.
ALL
Specifies that pipe slope symbols are to be created for the sloped segments of all
the pipelines in the selected views. This modifier is mutually exclusive with the
LINENO modifier.
INTERVAL x
Specifies the distance to be maintained between two adjacent slope pipe

symbols in a pipe segment. This distance is specified in the drawing units. The
default value is 10 mm.
LAYER x
Specifies the layer on which the slope pipe symbols are to be created. The
default is the active layer.
Specifies the line number of a pipeline for which slope pipe symbols are to be
created. This modifier is mutually exclusive with the ALL modifier.
RADIUS x
Specifies the radius of the slope pipe symbol to be created. The radius is
specified in the drawing units. The default value is 2 mm.
Procedure 1
To generate slope pipe symbols for all the pipelines in the view,
1. Enter GENERATE SPSYMBOL ALL.

4. Select the view for generating slope pipe symbols for all the pipelines in it.
5. Press RETURN.

Procedure 2
To generate slope pipe symbol for the pipeline identified by its line number,
1. Enter GENERATE SPSYMBOL LINENO.

5. Select the view for generating slope pipe symbols for the selected pipeline.
6. Press RETURN.
Procedure 3
To generate slope pipe symbols for graphically selected pipelines,
1. Enter GENERATE SPSYMBOL.

4. Select the view for generating slope pipe symbols.
5. Enter a semicolon. The system prompts MODEL ent.
6. Select the pipelines for generating slope pipe symbols.
7. Press RETURN.
Example
This example illustrates generation of slope pipe symbols for the sloped segments
of a selected pipeline.
#n# GENERATE SPSYMBOL RADIUS 2 INTERVAL 15: view d1; Model ent
d2

OR
#n# GENERATE SPSYMBOL RADIUS 2 INTERVAL 15 LINENO
EXAMPLE-1-100-XX: view d1

HIDE INTERSECTION
HIDE INTERSECTION
Description
Use this command to change the appearance of piping and instrument lines at
intersections so they appear not to touch each other. This is done by blanking an
interval on one of the lines.
This command is designed primarily for P&ID diagrams and piping isometric
drawings, but works with any set of nodal lines (Nlines) that do not have related
detail graphics.
For drawings such as isometrics (three-dimensional), the position of the Nlines

(which is in back relative to the screen) determines which Nline is blanked. For
P&IDs use modifiers and getdata selection to specify what you want. For example,
to gap vertical lines, specify the modifier VERTICAL to blank the Nline nearest to
vertical at intersections.
Valid Modes
Model mode or Draw mode
Syntax
#n# HIDE INTERSECTION [modifiers] [:getdata]

HIDE INTERSECTION
Modifiers
The following diagram shows the flow of HIDE INTERSECTION modifiers. An
see the Preface.
The flowchart shows the modifiers to be in three groups, and mutually exclusive
within each group. If you select more than one within a group, the last one
specified is the one that is used.
The modifiers reference two sets of identified Nlines, the first containing Nlines to
be blanked, and the second containing the Nlines that are to be compared to the
Nlines in the first set. Nlines of the second set are not themselves blanked, but
determine which Nlines of the first set are to be blanked.
Intersections involving Nlines not specified in either set are ignored. The second
set can be explicitly defined in getdata, or as an Nline in the part, using the ALL
modifier.
follows.

HIDE INTERSECTION
ADD
(Default) Adds intervals (gaps) to Nlines.
ALL
Compares a set of Nlines you identify, against each other and against a second
set of all the other Nlines in the part. If you do not specify which Nlines
comprise the first set, then all the Nlines in the part are considered to be first
set, and are compared against each other.
EITHER
For piping isometric drawings, when an Nline from set one is behind another
identified Nline, the Nline from set one is gapped.
For P&IDs, which Nlines are gapped depends on which sets of Nlines intersect.
Sets Nlines Gapped

Set 1 vs. Set 1 Horizontal Nlines
Set 1 vs. Set 2 Set 1 Nlines
GAP x
Specifies a hypothetical Nline width that determines the length of blank

intervals (gaps). Figuratively speaking, the solid Nlines appear to cut a path x
units wide through the Nlines they cross.
When Nlines are perpendicular, the length of the gap equals x. However, as the
angle between the Nlines diverges from perpendicular, the gap length increases.
The default is
x = 0.25 inches on the drawing regardless of the drawing units. Input is
expressed in drawing units.
HORIZONTAL
Creates gaps in the following Nlines depending on which sets of Nlines

intersect.
Sets Nlines Gapped

Set 1 vs. Set 1 Horizontal Nlines
Set 1 vs. Set 2 Horizontal, Set 1, Nlines

HIDE INTERSECTION
ONLY
(Default) Compares the Nlines of only one set against each other.
REPLACE
Replaces gaps on Nlines (restores the Nline).
VERTICAL
Creates gaps in the following Nlines depending on which sets of Nlines

intersect.
Sets Nlines Gapped

Set 1 vs. Set 1 Vertical Nlines
Set 1 vs. Set 2 Vertical, Set 1, Nlines
To compare all the Nlines in the part against each other.

#n# HIDE INTERSECTION ALL
Procedure 1
To compare against each other, all the Nlines that you specify by selecting them.
1. Enter the command HIDE INTERSECTION and any modifiers you desire,
except ALL. Enter a colon.
2. In response to the system prompt, digitize the Nlines to be compared and press
RETURN.
The system considers the selections to all be part of set one and only compares
them with each other.
Procedure 2
To compare two sets of Nlines with each other.
Proceed as in earlier procedure, except enter the modifier ALL. The system
compares the Nlines you identify by digitizing as set one, with a second set
consisting of all the remaining Nlines in the part.

HIDE INTERSECTION
Procedure 3
To compare Nlines that you identify as set one, with another group of Nlines that
you identify as set two.
Proceed as in earlier procedure. After the colon, identify the Nlines of set one by
digitizing them, except enter a semicolon (;) instead of RETURN. Digitize the
Nlines you want to be the second set; then press RETURN.
The system compares the Nlines of set one against the Nlines of set two, but not
any Nline that is not specified as being in either of those groups.
Example 1
In this example, HIDE INTERSECTION is used to do the following to a P&ID:
Blank instrument lines, when an instrument line crosses a pipe.

Blank the pipe or instrument line that is closest to vertical, when two pipes or
two instrument lines cross.

HIDE INTERSECTION
The P&ID is illustrated here, before any blanking occurs. The instrument lines (the
lines with tics) are on layer 41. The pipes are on layer 21.
Hide the intersection of two instrument lines.
The modifier VERTICAL ensures that the line nearest to vertical is the one that is
blanked.
The modifier REPLACE ensures that old intervals are erased.

#n# HIDE INTERSECTION VERTICAL REPLACE: MODEL ent NLIN LAY 41
VWIN view NAME ONE

HIDE INTERSECTION
The system responds with a message:

- ERASING INTERVALS TO BE REPLACED -
- SORTING 8 SEGMENTS -
Hide instrument lines against pipes.
The instrument lines are identified as set one, and after a semicolon (;) is entered,
the pipes are identified as set two.
#n# HIDE INTERSECTION: MODEL ent LAY 41 VWIN view NAME ONE;
MODEL ent LAY 21 VWIN view NAME ONE

HIDE INTERSECTION

- SORTING 20. SEGMENTS -
Hide pipes against each other.
The modifier VERTICAL ensures that the vertical pipes are the ones that are
blanked.
#n# HIDE INTERSECTION VERTICAL: MODEL ent LAY 21 VWIN view NAME
ONE

HIDE INTERSECTION

Example 2
The P&ID used in Example 1 is changed by moving a horizontal segment of a
pipeline upward.
The following command adds breaks to the pipe and instrument lines where they
now cross the altered pipeline:
#n# HIDE INTERSECTION: MODEL ent d1d2; MODEL ent d3

HIDE INTERSECTION

Delete the gap left when the pipeline was moved.
The combination of modifiers VERTICAL REPLACE ALL ensures that

intersections not visible on the screen are also affected.
#n# HIDE INTERSECTION VERTICAL REPLACE ALL: MODEL ent d


HIDE INTERSECTION
Please note: To erase gaps that have been introduced into an Nline, you can
use the ERASE APPEARANCE INTERVAL ALLVIEWS command. It restores
the Nline to its appearance before any hiding of intersections was done.
However, never use CHANGE APPEARANCE INTERVAL BLANK in

combination with HIDE INTERSECTION on the same entity; the blank intervals
these two commands create can interfere with each other.

Description
Use this command to highlight and mark pipes or pipeline entities for easy visual
identification. You specify what you want to highlight
Within getdata, by selecting pipes or pipeline entities

Outside getdata, by using the LINENO (line number) modifier and the line
number of a pipeline
Outside getdata, by using the MIPTR (Master Index Pointer) modifier and the
MIPTR of the pipeline entity
Components of a pipeline in the direction of the flow.
Using this command you can also optionally highlight the 2D reference objects in
the schematic drawing for selected pipeline components in the 3D model and vice
versa. You can also highlight the pipeline label associated with the selected
pipeline using the HIGHLIGHT PLINE command.
Valid Modes
Model mode, Draw mode
Syntax
#n# HIGHLIGHT PLINE [modifiers]: getdata
or
#n# HIGHLIGHT PLINE [LINENO or MIPTR] [modifiers]

Modifiers
The following diagram shows the flow of HIGHLIGHT PLINE modifiers. An
see the Preface.

follows.
1 DETAIL flag
(Default) Highlights everything (Cnodes, Nfigs, Nlines, and detail entities)

associated with the pipeline or entity you specify.
1 ENTITY flag
Highlights only the pipeline entity(s) you specify. Detail entities associated with
the specified pipeline are included unless the NODETAIL modifier is entered.
1 FLOW flag
Highlights the components of the selected pipeline in the direction of flow.
Highlights an entire pipeline whose line number you enter. Only one line
number can be specified at a time.
To highlight the cross-relationship between the entire pipelines use the
LINENO modifier together with the RELATION modifier.
1 MIPTR n1, n2, n3...
Highlights an entity when you enter its MIPTR. When you enter multiple
MIPTRs in one command line, separate the numbers with commas and no
spaces.
1 NODETAIL flag
Detail entities created with CREATE DETAIL are not highlighted; see the
Visualization/Preparation Reference.

1 RELATION flag
Highlights the cross-relationship between a specified 2D schematic component

and its corresponding 3D component. For this modifier to be executed, The 2D
schematic pipeline network should be viewed in the active 3D model pipeline
network part or vice-versa. Also the 2D schematic pipeline network and 3D
model pipeline network should have been dumped to the external RDBMS
tables using the command GENERATE PIPEDBASE and the connection to the
external RDBMS tables should exist.
Please note: If the schematic pipeline network is not viewed then the related
group of 3D model components alone are highlighted based on the relationship
which exists in the external RDBMS tables.
Procedure 1
To highlight specific entities on a pipeline by selecting them,
1. Enter the HIGHLIGHT PLINE command and the modifier ENTITY. Enter a
colon.
2. The system prompts MODEL ent.Select the entities to be highlighted.
Procedure 2
To highlight a pipeline, identifying it by number.
Enter the command, either the LINENO or MIPTR modifier, and either the line
number or MIPTR numbers of the entities to be highlighted, and press RETURN.

Example 1
Highlight a pipeline, by selecting a part of it or by using the LINENO modifier.
Enter either of the two commands:
#n# HIGHLIGHT PLINE: MODEL ent d1
or
#n# HIGHLIGHT PLINE LINENO 0-8242

Example 2
Highlight individual selected entities. In this example, a section of pipe, and not
the entire pipeline, is highlighted.
#n# HIGHLIGHT PLINE ENTITY: MODEL ent d

Example 3
Highlight the components in the direction of flow. In this example the components
of the pipeline are highlighted in the direction of the flow.
#n# HIGHLIGHT PLINE FLOW: MODEL ent d
Please note: Turn off all the highlighting in a part with the commands
HIGHLIGHT NET OFF or MARK ENTITY CLEAR.
Turn off selected highlighting with the command MARK ENTITY CLEAR:
getdata (selecting the entities to have their highlighting turned off).

Example 4
In this example, a section of pipe from the pipeline is highlighted. The label
associated with the selected pipe is not highlighted.

Example 5
In this example, a section of pipe from the pipeline is highlighted along with the
the label associated with the selected pipe.

Description
Use this command to insert a penetration symbol along a pipeline to indicate the
location where the pipeline penetrates a wall or a floor. There are two different
penetration symbols, a wall penetration symbol and a floor penetration symbol.
Both symbols can be found in the CVPD.ISO.T directory. The name of the wall
penetration symbol is PENW and the floor penetration symbol is PENF. Both
symbols can graphically be altered according to the users needs.
The location of a penetration symbol may be determined by a location modifier

which specifies either the X-coordinate or Y-coordinate or Z-coordinate of the
penetration symbol depending on which modifier was used. If no location modifier
is specified, then a digitized location determines the coordinates where the
penetration symbol is to be inserted.
Selection modifiers provide an efficient way to insert the penetration symbols,

with the same x-coordinate/y-coordinate/z-coordinate values, along single or
multiple pipelines with a single execution of the command.
If a fitting already exists at the selected pipeline location, then the existing fitting
is highlighted in red and a warning message is given.
If a penetration symbol is to be inserted at a location where a penetration symbol

already exists or the distance between the two symbols is too small (less than 10
mm or 0.3937 inch), the existing penetration symbol is highlighted in green, if the
modifier MARK is used. The default is to not highlight the existing symbol, but a
message is given.
Valid Modes
Model mode
Syntax
#n# INDICATE PENETRATION name [modifiers]: getdata

Modifiers
The following diagram shows the flow of INDICATE PENETRATION modifiers.
follows.
1 HEIGHT x
Determines the location of the penetration symbol along a selected pipeline in

the Z direction of the model coordinates system. If this modifier is not specified,
then the penetration symbol is inserted along the pipeline at the digitized
location.
1 MARK
If a penetration symbol already exists at the selected pipeline location, then the
existing penetration symbol is highlighted in green and a warning message is
given.

2 ALL
All pipelines are traced and penetration symbols inserted at all possible
locations, matching the value input for the HEIGHT, XLOC, or YLOC
modifiers.
2 LINENO pipeline label
Processes the pipeline that matches the input pipeline label. The entire pipeline
is traced and penetration symbols inserted at all possible locations, matching
the value input for one of the HEIGHT, XLOC, or YLOC modifiers.
2 PLINE
Processes the selected pipeline. The entire pipeline is traced and penetration
symbols inserted at all possible locations, matching the value input for one of
the HEIGHT, XLOC, or YLOC modifiers.
1 XLOC x

the X direction of the model coordinates system.
1 YLOC x

the Y direction of the model coordinates system.
Procedure 1
To insert penetration symbols for the selected pipelines,
1. Enter INDICATE PENETRATION, the penetration symbol name, and,

optionally the HEIGHT, XLOC, or YLOC modifier and its value.
2. Enter a colon. The system prompts MODEL ent. Select the pipeline(s) on
which you want the penetration to be inserted. In the case of the HEIGHT,
XLOC, YLOC modifiers, the digitize is used to indicate the pipeline segment.
In the case of the modifier PLINE, the digitize will indicate which pipeline
network to process.
3. Press RETURN.

Procedure 2
To insert penetration symbols for all pipelines or for a pipeline by line number.
1. Enter INDICATE PENETRATION, the penetration symbol name, and,

optionally the HEIGHT, XLOC, or YLOC modifier and its value.
2. Enter either LINENO pipeline label or ALL.
3. Press RETURNINSERT BEND
Description
Use this command to insert bends at specified vertices of identified pipelines.
Pipeline bends are multivertex nodal lines assigned INNERDIAM, OUTERDIAM,

STOCKNO, and BRAD (bend radius) properties. Every bend consists of from five
to a maximum of twenty segments that make up a curve. The curve is inserted
tangentially in the same plane and on the same layer as the pipeline to which it
connects. Its first and last segments are collinear with the pipeline. A point entity is
also inserted at the pipeline vertex on the same layer as the pipeline. It is
independent of the bend entity.
Define the bend radius in one of three ways:
1. Explicitly, by giving the bend radius with the BRAD modifier

2. Implicitly, by giving the ratio of the bend radius to the pipelines nominal
diameter with the BRAT modifier
3. Automatically, by using the preset BRAD or BRAT value established with the
command SELECT PPARAMETERS. Only one can be set; the other has a zero
value. The automatic technique defaults to BRAT = 5 if you do not set either
with the command SELECT PPARAMETERS.
Valid Modes
Model mode
Syntax
#n# INSERT BEND [modifiers]: getdata

Modifiers
The following diagram shows the flow of INSERT BEND modifiers. An asterisk
Preface.
follows.
1 AUTOSELECT
Inserts pipe bends according to their own bend radius specifications. The data is
divided into two files, one for the geometrical data and one for material data.
Access to this data is set via the current plant design directory file.

The PBENDINFO file correlates pipe diameter to clamp length and bend radius
information. The total final bend radius is the sum of the bend radius and clamp
length fields in this file. If no clamp entry is present or if it is zero, then the total
bend radius is equal to the bend radius in the PBENDINFO file. The default
PBENDINFO file is CVPD.M.SPEC.PBENDINFO. PBENDINFO files must
be sorted before use.
The effect of different pipe materials may also be considered and used to
determine the bend radius selection through the Material Code entry in the
PMATINFO file. The pipe specification (from the pipeline label) is used to select
a two-character material code. This two-character material code is used as a key
to select the appropriate bend radius/clamp length fields in the PBENDINFO file.
Therefore, different materials can point to different pipe bend radius
information. The default PMATINFO file is CVPD.M.SPEC.PMATINFO.
Depending on the number of bends in a pipe spool, the AUTOSELECT
modifier also checks for the clamp lengths. The clamp length is checked
automatically using the values you have specified in the BEND_FILE and the
BEND_MACHINE_FILE.
The PMANINFO variable, which has a pointer to the PMANUFACTURE file, is
set in the directories file that is present in the
usr/apl/cadds/data/plant directory. The PMANUFACTURE file has a path
to the BEND_FILE and the BEND_MACHINE_FILE. For a defined material, there
is a pointer to the specific bend machine and the clamp length files. For
example, for steel, with the units in inches, the BEND_FILE has the information
in the BEND-STEEL-A-IN file.
If the PMANINFO and the PBENDINFO variables are defined in the
directories file, then by default, the PMANUFACTURE file is accessed for
clamp length checking. If you want the PBENDINFO file to be accessed for bend
radius and clamp length values to check for a single clamp length, you must
comment the PMANINFO variable setting in the directories file.
The BEND_MACHINE_FILE contains the bend information for pipe sizes
associated with a specific pipe material. You can specify the values for the
following variables in the BEND_FILE:
SIZE - the pipe diameter.
RADIUS - the bend radius.
RATIO - the ratio between the bend radius and the pipe diameter.
MIN_ANGLE - the minimum bend angle.
MAX_ANGLE - the maximum bend angle.
Please note: You can specify the value for the radius or the ratio in the
BEND_FILE. If you specify values for the radius and the ratio in the bend file, only
the value of RADIUS is used as the bend radius.

Specify the values for the following variables in the BEND_FILE:

SIZE - the pipe diameter.
START_CLAMP_LEN - the minimum clamp length that is required before
the first bend. The length of the start segment must be equal to or longer
than the start clamp length value.
MID_CLAMP_LEN - the minimum clamp length required between two
bends. The length of the middle segment must be equal to or longer than
this value.
END_CLAMP_LEN - the minimum clamp length after the last bend of the
pipe spool. The length of the end segment should be equal to or longer than
this value.
2 ALL
Processes all the pipelines in the current part.
2 LINENO pipeline label
Processes only the pipeline with the input label and traces the whole pipeline
network to find all possible insertion points.
2 PLINE
Processes only the selected pipeline and traces the whole pipeline network to
find all possible insertion points.
1 BRAD x
(Bend Radius) Specifies the radius of the pipeline bend. The range is all
positive real numbers in database units. Choose this modifier or the BRAT
modifier to specify the bend radius. You can also not enter either and use the
default value of the one set by using the SELECT PPARAMETERS command.
Choose this modifier with the ALL modifier to insert bends on all vertices of
the existing piping networks in the part.
1 BRAT x
(Bend Ratio) Specifies the ratio of the radius of the bend to the diameter of the
pipeline into which it is being inserted. The range is all positive real numbers in
database units. Choose this modifier or the BRAD modifier to specify the bend
radius. You can also not enter either and use the default value of the one set by
the SELECT PPARAMETERS command. Choose this modifier with the ALL
modifier to insert bends on all vertices of the existing piping networks in the
part.

2 OUTERDIA
Specifies the bend radius with respect to the outer diameter of the pipe. If this
option is not selected, the bend radius is calculated with respect to the nominal
diameter of the pipe.
1 LINENO text
Identifies the pipeline on which you want bends inserted. You can specify any
subset of the fields in the pipelines label as defined in the directory file (for
example, CW-100). Only the first pipeline found with the specified line number
is identified. The use of this modifier automatically activates PLINE; this means
that you do not have to identify the locations of the bends.
1 NOPLINE
(Default) Bends are not automatically inserted at all vertices of pipelines. They
are only inserted at selected vertices.
1 PLINE
Inserts a bend at every vertex of the identified pipelines. You can still use the
modifier PLINE if you have already put some bends in the line.
1 SPECIAL
Indicates that a pipeline bend is not standard, but is specially made. This
modifier inserts the property SPECIAL on the bend. Bends with this property
are reported by REPORT PIPE as separate entities (as bends rather than as
pipes).
1 MINBENDANG real
Specifies the bend angle limits. You can specify the bend angle limit within 0 to
180 degrees. An error message is displayed if the angle is specified beyond this
range.
Please note: This modifier is not available with the AUTOSELECT modifier.

Procedure
To insert a bend,
1. Enter the command INSERT BEND.

2. Specify either the modifier BRAD or BRAT and a value, or omit the modifier in
favor of the default bend ratio of 5. You can also accept a default value that you
have previously established by use of the command SELECT
PPARAMETERS.
3. Enter a colon. The system responds with MODEL ent. Digitize the vertices
at which you want bends inserted.
4. Press RETURN.

Example 1
Insert bends with a BRAD of 2, established as the default value using the SELECT
PPARAMETERS command.
#n# SELECT PPARAMETERS BRAD 2
#n# INSERT BEND: MODEL ent d1d2d3

Example 2
Insert a bend at every vertex of a line, using the PLINE modifier. The default
BRAD of 2 is specified by the command SELECT PPARAMETERS.
#n# SELECT PPARAMETERS BRAD 2
#n# INSERT BEND PLINE: MODEL ent d

Example 3
Insert a bend at every vertex of the line by specifying the modifier LINENO and
identifying it as PIPE-SAMPLE. The ratio of the radius of the bend to the diameter
of the pipe being bent produces a BRAT of 1.5.
#n# INSERT BEND BRAT 1.5 LINENO PIPE-SAMPLE

Example 4
Inserting bends when there are more than one bends in a pipe spool.
If the PMANUFACTURE file is accessed, the INSERT BEND command checks

for three types of clamp lengths. If you want the PBENDINFO file to be accessed
for bend radius and clamp length values to check for a single clamp length, you
must comment the PMANINFO variable setting in the directories file.
#n# INSERT BEND AUTOSELECT PLINE : MODEL ent d
Example 5
Inserting one bend in a pipe spool.
When the PMANUFACTURE file is accessed, even for a single bend, the INSERT
BEND command checks for two types of clamp lengths, the start segment and the
end segment length.
#n# INSERT BEND AUTOSELECT PLINE : MODEL ent d
Please note: Select a maximum of 50 different pipelines when using the

PLINE modifier.

Select a maximum of 50 vertices if you are not using the PLINE modifier. The
selected locations for bends must be close to the vertices of the pipelines. The use
of VERT in getdata is helpful.
The bend angle must be between one and 179 degrees.
The point entity created is not associated with the bend entity.

This chapter explains the general purpose and use of the piping commands, their
mode of usage, the syntax and the modifiers.
INSERT DATUM
INSERT FITTING

INSERT DATUM
INSERT DATUM
Description
Use this command to annotate the coordinates for northings, southings, eastings,
westings, and elevations. The command applies to plan, elevation, and isometric
drawings.
Valid Modes
Model mode, Draw mode
Syntax
#n# INSERT DATUM [modifiers]: getdata
Modifiers
The following diagram shows the flow of INSERT DATUM modifiers. An asterisk
Preface.
follows.

INSERT DATUM
ALL
(Default) Annotates locations of northings, southings, eastings, westings, and

elevations.
BOP
(Bottom of Pipe) Adjusts the value of coordinates in the -Z direction by a

distance of minus one-half of the pipes outer diameter. With this modifier the
extension line still points to the centerline of the pipe. The letters BOP appear
with the dimension. BOP does not apply if EW or NS is chosen. Use of BOP
excludes TOP.
ELEVATION
Inserts an elevation datum.
EW
(Easting Westing) Inserts an easting or a westing datum.
ISOX
(Default) Places the extension line and datum text along the model x-axis.
ISOY
Places the extension line and datum text along the model y-axis.
NS
(Northing Southing) Inserts a northing or a southing datum.
PREFIX delimited text
Adds text you define in front of the datum text.
SUFFIX delimited text
Adds text you define to the end of the datum text.

INSERT DATUM
TOP
(Top of Pipe) Adjusts the value of coordinates in the +Z direction by a distance

of plus one-half of the pipes outer diameter. With this modifier the extension
line still points to the centerline of the pipe. The letters TOP appear with the
coordinate. TOP does not apply if EW or NS is chosen. Use of TOP excludes
BOP.
Procedure
To insert a datum,
1. Enter the command SELECT TEXT and specify the text parameters.
2. Enter the command INSERT DATUM and any modifiers.
3. The system prompts Model ent. Select (d1), a Cnode or Nfigure whose
origin is the datum point and also the start point of the extension line. The
system prompts Model loc.
4. Optionally, select (d2), the other end point of the extension line. This point is
adjusted to make the extension line parallel to the model x- or y-axis,
depending on which direction modifier is in effect. If selections d1 and d2 are
incompatible with the specified direction, the extension line and text are
oriented on the best axis.
5. Select (d3) as the location for the origin of the datum text. If you do not specify
the location, the system selects the end of the extension line.
6. Press RETURN.

INSERT DATUM
Example 1
Annotate the location of the flange face at the start of the pipeline with all datums.
Place the datum text along the y-axis. The extension line goes from the Cnode to a
point derived by dropping a perpendicular from d2 to a line running through the
Cnode along the specified axis. To change position later, translate the line with
TRANSLATE ENTITY. The origin of the text is placed at d3.
#n# SELECT TEXT HGT .075 WDT .075 FONT 2
#n# INSERT DATUM ISOY: MODEL ent CNOD d1 MODEL loc d2d3

INSERT DATUM
Example 2
Use a plan view and put in an easting and a northing.
#n# INSERT DATUM EW: MODEL ent d1 MODEL loc d2d3
#n# INSERT DATUM NS ISOY: MODEL ent d4 MODEL loc d5d6

INSERT DATUM
Example 3
This example illustrates the use of the modifiers TOP, BOP, and PREFIX in an
elevation (front) view. Note that the datum text is edge-on to the screen after
insertion because it is put in the XY (TOP) plane.
Use the ROTATE ENTITY command to orient the text in the front view.
Reference the first extension line (END d2) when inserting the second BOP datum.
Use the DELETE ENTITY command to remove an extra extension line (d5) as two
are created in the same location.

INSERT DATUM

#n# INSERT DATUM TOP EL: MODEL ent NFIG d1 MODEL loc d2d3
#n# INSERT DATUM BOP EL: MODEL ent NFIG d1 MODEL loc END d2
LOC d4
#n# DELETE ENTITY: MODEL ent d5
#n# INSERT DATUM EL PREFIX NOZL: MODEL ent CNOD d6 MODEL loc
d7d8

INSERT DATUM
Notes
The following general notes will help you when using the INSERT DATUM
command.
1. Before generating an isometric drawing, use the SAVE DIMENSIONS
command to save the model coordinates as XYZ properties. INSERT DATUM
uses the XYZ properties if they exist; otherwise, it uses model coordinates.
2. Before using INSERT DATUM, you may want to define a construction plane
(CPL) with an origin offset from the model origin. To do this, use the DEFINE
CPL and then SELECT CPL commands. When you select such a CPL, the
difference between a locations model coordinate and the origin of the selected
CPL determines the datum. This means that a CPL with an origin at X -500, Y
-500 feet, and a model coordinate ten feet east of the model origin, produces an
easting of 510 feet.
3. The selected CPL does not affect placement of text and extension lines. They
are oriented on the view plane for the standard six views. For an isometric view,
the XY- or YZ- plane is used. The text is always placed so it is readable. If the
direction axis in effect is incompatible with the permanent view plane, the
direction axis is ignored. Avoid temporary view orientations produced by
DYNAMIC VIEW rotation.
4. The parameters set with the SELECT TEXT command define the datum text
parameters.
5. Conventional compass directions are used:
North = +Y
South = -Y
East = +X
West = -X
6. The unit of the datum is the same as the model units of the part unless you use
the SELECT DIMENSION command to specify a different unit. The format of
datum unit is listed in the following table.
Table 4-1 Datum Format
Unit Datum Format

Feet, inches Feet, inches
Millimeters Whole number
Centimeters Number to one decimal place
Meters Number to three decimal places
7. The extension line and datum text are view specific. Use SELECT MODE
DRAW VIEW: view d before modifying or deleting them.

INSERT FITTING
INSERT FITTING
Description
Use this command to insert single fittings, groups of fittings, and assemblies (line
attachments such as vents and drains) into pipelines or into other fittings (taps).
Also insert nozzles and structural elements such as beams. The command has
many powerful piping-related features such as:
Automatically supplying flanges and gaskets to fittings to maintain joint

integrity
Inserting 90-degree elbows at every corner of specified pipelines
Inserting single- and double-reducing fittings
Checking for end type and size consistency
Parametrically scaling specially prepared branch or corner fittings with unequal
leg lengths
To select, scale, and insert components, the command references an autoselection

file (named in the directory file that you specify with SELECT PPARAMETERS).
For automatic insertion to work properly, the command must recognize the type of
fitting and its facing or end type. End type information is stored in the ENDT (end
type) field of the autoselection file and in an end type file. Other generic
information about the fitting is stored in the Insert Fitting Code (IFC#) of the
autoselection file. The command still recognizes this information for selection
based on the stock number if you use an old autoselection file without the IFC#
and the ENDT fields.
Note that fittings must be of the same precision as the part. See Managing CADDS
5 for information about the double-precision format.
Valid Modes
Model mode

INSERT FITTING
Syntax
#n# INSERT FITTING name [modifiers]: getdata
name (40-character limit) is either the fittings generic name, stock number, or
library part name, depending upon the modifiers in effect:
With SEL, use a generic component name (for example, BALV)
With STOCK, use a stock number (for example, BALVRFAD150-06)
With NOSEL, use a full part name (for example, CVPD.F.BALV).
name is required as the first modifier in the command. If you insert a group of
fittings, you must specify a name after each AND modifier.
If the name you enter differs from the value stored in the components
COMPNAME property, it is stored in the SNAME property which is inserted on
the component.
Modifiers
This command has two kinds of modifiers: group and individual. Group modifiers
apply to all appropriate fittings in the group and are entered only once, anywhere
within the command. Some, such as LAYER, apply to all fittings; others, such as
FLANGE, apply to only certain fittings in the group. These modifiers specify
tolerances, collinear checking, hooking, flanges, size changes, and justification.
You can insert several fittings (a group) at the same time by separating each fitting
and its associated modifiers with the AND modifier.
An individual modifier applies to a single fitting; if it is used in a group, it applies

to the fitting it follows. These modifiers specify such characteristics as the size,
stem orientation, and end type.
The following table lists the group modifiers and indicates which are selected with
SELECT PPARAMETERS and which are active by default.
Table 4-2 Group Modifiers for INSERT FITTING
SELECT
Group Modifier Default PPARAMETERS
CHECK X X
NOCHECK X
COLINEAR X
NOCOLINEAR
FLANGE X X
NOFLANGE X
GASKET X X

INSERT FITTING
Table 4-2 Group Modifiers for INSERT FITTING
SELECT
Group Modifier Default PPARAMETERS
NOGASKET X
HOOK X X
NOHOOK X
LAYER X
SELECT X X
NOSELECT X
TOLERANCE X
BTOR
RTOB
TAP

INSERT FITTING
The following diagram shows the flow of INSERT FITTING modifiers. An

see the Preface.

INSERT FITTING

INSERT FITTING
Both group and individual modifiers used with INSERT FITTING are described in
this section.
An (S) identifies those modifiers that can be set or changed by use of the
SELECT PPARAMETERS command.
(Default) identifies default modifiers.
Both group modifiers and individual fitting modifiers listed without (Default) or
(S) are in effect only when used explicitly within the command.
follows.
AND
Used between names of fittings and their associated single-fittings modifiers
when a group is inserted with one command. The name of the fitting follows
each instance of AND. The maximum number of fittings in a group is ten.
Please note: For insertion of groups, HOOK must be in effect.
BSIZE text
(Branch Size) Specifies the size of the fittings branch (ten-character limit). If
the entered value is equal to the run size, a nonreducing branch is inserted
automatically. This modifier serves the same purpose for branch fittings (for
example, reducing tees and olets) as NSIZE does for nonbranching reducers.
BSIZE supplies one of the sizes needed to select the fitting automatically; the
pipeline supplies the other.
The modifier automatically marks the branch size with a nominal pipe size
(NPS) property using the text you specify. This property is inserted on the
Cnode of the fittings branch. In special cases involving the use of BSIZE and
BTOR together, BSIZE specifies the size of the line leaving the fittings run
side.
This modifier is required when TAP is used. It specifies the size of a
nonbranching tap or the smaller size of a branching tap (the larger size is taken
from the parent fitting).
BTOR
(Branch-to-Run) Similar to RTOB except that the fitting branch is parallel to the
pipe inlet, and the fitting run is parallel to the pipe outlet.

INSERT FITTING
BSIZE applies to the outlet pipe that comes from the branch of the fitting in the
RTOB case, and from its run in the BTOR case. After a BTOR or RTOB fitting
is inserted, the unhooked Cnode becomes a point from which to route a
branchline.
CENTER
Places the center of the fitting at the insertion location or at the center of the
selected fitting when TAP is used.
CENTER is similar to FAR and NEAR in that it applies to only one fitting in a
group and does not apply to face-to-face or corner insertions. CENTER,
NEAR, and FAR are mutually exclusive. CENTER affects the fitting it follows;
other fittings are positioned relative to the CENTERed fitting.
CENTER is the default for taps. The tap is placed in the center of the fitting (at
the surface for nonbranch fittings or at the centerline for branch fittings).
CHECK
(Default) (S) Activates end type and minimum spool length checking. End
types are checked between adjacent fittings during group or face-to-face
insertions. Length of pipe from the inserted fitting to the next fitting or corner is
checked.
NOCHECK
(S) End type and minimum spool length are not checked.
COLLINEAR
(Default) Performs collinear checking after you have inserted fittings. If they do
not pass the collinear test, they are not hooked into the pipeline and are deleted
from the part. Use the modifier TOLERANCE to set the parameters of the test.
NOCOLLINEAR
Inserts and hooks fittings into pipelines, regardless of whether their connection
points fall on or close to the pipeline.

INSERT FITTING
CORNER
Controls the insertion of fittings onto corners. This modifier traps selections that
you place anywhere along a pipe to the nearest corner (vertex). CORNER also
sets up the correct frame of reference for hooking and automatic orientation.
Please note: The CORNER modifier is automatically activated under these

conditions:
When you use the PLINE or LINENO modifier

When you insert elbows and corner fittings with proper IFC code
When you use the BTOR and RTOB modifiers (for control over orientation) to
insert tees
Since the VERT modifier in getdata traps a selection to a vertex (corner) but
does not activate the modifier CORNER, do not use VERT with INSERT
FITTING as a substitute for CORNER.
NOCORNER
(Default) For straight inline fittings. The fittings are inserted at the location you
specify.
ENDT text
Selects a fitting with the specified face or end type (for example, FIRF) as well
as size and specification (nine-character limit). This modifier is useful for
selecting alternative fittings in specifications that are of the same type and size.
Please note: This modifier is only valid with the SELECT modifier.
FAR
Inserts the downstream side of the fitting at the insertion location or at the outlet
of the parent fitting for taps. FAR is similar to CENTER and NEAR in that it
does not apply to face-to-face or corner insertions.
You can use FAR with only one fitting in a group. You can use only one of these
justification modifiers, FAR, CENTER, and NEAR, in any group.
FAR affects the fitting it follows; the locations of other fittings in the group are
adjusted accordingly. The default for inline fittings is to place the origin of the
fitting (or first fitting of a group) at the insertion point.
When FAR is used with TAP, the origin of the tap is placed at the outlet of the
parent fitting (at the surface for nonbranching taps or at the centerline for
branching taps).

INSERT FITTING
FITNAME text
Specifies the name of the fitting to be inserted. When you enter the name of a
fitting immediately after the INSERT FITTING command, or after the modifier
AND, this modifier is on by default (you do not need to enter it). See the Syntax
section of this command for rules about fitting names.
FLANGE
(Default) (S) Automatically includes necessary flanges as fittings are inserted.

When autoflange/gasket insertion is in effect, the modifiers NEAR, CENTER,
and FAR position the fitting relative to the selected location and place the
flange and gasket accordingly. The ENDTYPE property is inserted on flange
Cnodes. An end type with an F indicates bolting; the reporting software does a
lookup on BOLT or STUD depending on which has been selected with
SELECT PPARAMETERS.
NOFLANGE
(S) Flanges are not automatically inserted. Use NOFLANGE when you make
P&IDs and when you insert components that do not require hooking (for
example, nozzles). NOFLANGE occurs automatically with the STOCK
method of component selection.
FLIP
Rotates fittings 180 degrees about their y-axis before inserting them. In effect,
they are flipped in place so that insertion location is not changed. Flipping can
occur automatically when, for example, the automatic flange feature puts a
closing flange on, or when you insert fittings with an NSIZE bigger than the
line size. Do not use FLIP with flow dependent fittings (check valves) or size
change fittings (reducers) since this can interfere with the automatic flipping
feature.
GASKET
(Default) (S) Automatically inserts required gaskets.
NOGASKET
(S) Gaskets are not inserted automatically; you must insert the necessary
gaskets.
HOOK
(Default) (S) Hooks fittings onto selected pipelines.

INSERT FITTING
NOHOOK
(S) Inserts components such as nozzles and beams that do not require hooking
at specified locations. You cannot insert taps with NOHOOK.
You can use NOHOOK with SELECT or STOCK, as well as with NOSELECT.
With SELECT, you must specify the size and specification with the SIZE and
SPEC modifiers, because that information is not obtained from a pipeline label.
INSTRUMENT text
Inserts a text value property (INSTRUM) that is necessary for the ANNOTATE
ISOMETRIC command. The text value (maximum of 12 characters) is an
instrument type and number assigned for a particular type valve or assembly,
for example, VG-101. The dash delimiter causes the drawing annotation to
appear as a number (101) under the alpha (VG) instrument type, both within a
circle. For instance,
#n# INSERT FITTING GATV INSTRUMENT VG-101: MODEL ent d
will insert an instrument number text value property of VG-101 on a designated
gate valve.
Please note: This can also be achieved by using the base Explicit Modeling
command INSERT PROPERTY INSTRUM.
LAYER n
Inserts fittings on the specified layer. The default is the layer set with SELECT
PPARAMETERS. With HOOK, a value of -1 selects the layer of the pipeline.
With NOHOOK, a value of -1 selects the active construction layer.
LINENO text
Inserts elbows at all 90-degree vertices in the specified line. This modifier is
similar to PLINE except that you enter the entire pipeline label (or any
contiguous fields in the label, as defined in the directory file) instead of
selecting the pipeline. No getdata is allowed with LINENO.
NEAR
(Default) Inserts the upstream side of the fitting at the insertion location or at
the inlet of the fitting for taps. NEAR is similar to CENTER and FAR in that it
does not apply to face-to-face or corner insertions.
You use NEAR with only one fitting in a group. You use only one of these
justification modifiers, NEAR, CENTER, and FAR, in any group.

INSERT FITTING
NEAR affects the fitting it follows; the locations of other fittings in the group
are adjusted accordingly. For inline fittings, the origin of the fitting (or first
fitting of a group) is placed at the insertion location.
When NEAR is used with TAP, the origin of the tap is placed at the outlet of the
parent fitting.
NLABEL text
(New Label) Specifies that a new, separate line originates at the fitting; that is,
the new line is not a continuation or branch of the old line. NLABEL places the
TERMNAM property at the origin of this new line. The value of the property is
two blanks. If the fitting is a reducer, the modifier inserts the new label (nodal
text) on the downstream line. If the fitting is a branch fitting, the new label
(nodal text) is ignored, and you must insert the label when you route the new
line. For best results, use a simple dummy label such as A, B or C. In either
case, the REPORT PIPE command reports the new line as starting from the old
line. There is a 40-character limit.
Please note: You only need to use NLABEL when your networks become too
complicated, have too many series, or when you want to define bounds for
consistency checking. Pipelines can be identified by the mere presence of a label
(nodal text). The TERMNAM property is not mandatory, but does define a hard
boundary between pipelines that limits the activities of other commands such as
CONSTRUCT PIPELINE.
NSIZE text
(New Size) Specifies the new size the fitting introduces into the line
(18-character limit). NSIZE supplies one of the sizes needed to select the fitting
automatically; the pipeline supplies the other size. If the NSIZE is larger than
the old line size, the reducer is flipped to become an enlarger.
The modifier automatically marks the change in the line size with a nominal
pipe size (NPS) property using the text you enter. This property is inserted on
the fittings outlet Cnode. The NPS property with the old size is put onto the
inlet Cnode. This modifier eliminates the need to insert nodal text each time the
line size changes.
If you use NOSEL, the NSIZE modifier updates the DUCTSIZE property on
the outgoing duct Nline.
NSPEC delimited text
(New Specification) Specifies the change in specification that the fitting

introduces into the line (18-character limit). This modifier changes the pipeline
specification with a SPEC property using the text you enter. This property is

INSERT FITTING
inserted on the fittings outlet Cnode. The old specification is put onto the inlet
Cnode. The new pipe specification is in effect downstream from the fitting to
which you apply this modifier.
OFFSET x
Offsets the origin of the tap x distance (in the direction of flow) along the
internal Nline (centerline) of the parent fitting. The PROJECTION modifier
positions the tap origin along a perpendicular at the offset point. When an offset
is specified, it must be in database units.
OFFSET is only used in conjunction with the TAP modifier and can only be
entered immediately after either the TAP or PROJECTION modifier in the
command line. OFFSET is mutually exclusive with NEAR, CENTER and FAR,
and the explicit coordinate method of insertion (see the TAP modifier
description). The default offset is the center of the parent fitting.
PLINE
(Pipeline) Restricted to 90-degree elbows; inserts a specified elbow at every

90-degree vertex in the selected pipeline. PLINE cannot be used with TRIM.
Please note: Only one pipeline can be processed per command, and only one
selection is accepted.
PROJECTION x
Positions the tap x distance out from the centerline of the parent fitting (on the
perpendicular that starts at the offset point). The OFFSET modifier determines
the location of the perpendicular along the centerline; the direction of the
perpendicular is determined by the current stem direction (which can be
changed with the STEM or ROTATION modifiers). Specify the ending point
(and thus the origin of the tap) by entering the distance from the centerline of
the parent fitting to the far end of the tap. When a projection is specified, it must
be in database units.
PROJECTION can only be used in conjunction with TAP and can only be
entered immediately after either TAP or OFFSET in the command line.
PROJECTION is mutually exclusive with the explicit coordinate method of
insertion (see the TAP modifier description).
INSERT FITTING automatically orients the x-axis of fittings relative to the
pipeline, and you can use the STEM, ROTATE, and FLIP modifiers to orient the
+y axis of the fitting (for example, a branch or stem). System orientation
modifiers are useful with NOHOOK and for insertion of taps. When using the
system orientation modifiers to orient an explicitly located tap, it may help to

INSERT FITTING
define and activate a CPL orthogonal to the pipeline. System orientation

modifiers cannot be used with groups or in combination with STEM, ROTATE,
or HOOK.
If you do not use PROJECTION (or explicit coordinates), the default value of
zero for olet-type branch fittings places the tap on the centerline of the parent
fitting; the default value for nonbranch fittings places the tap at the surface of
the parent fitting (the radius of the cylinder or cone).
ROTATE x
Rotates the fittings model y-axis about the pipeline x degrees. This modifier is
most useful when the desired orientation is not parallel to one of the six
compass or orthogonal directions. The angle is measured clockwise (looking in
the direction of the flow) as follows:
From the top of the pipe (+Z), or vertically for all pipe segments except
straight vertical ones (that run along the z-axis)
From +X for straight vertical segments
From the direction specified with the STEM modifier
For taps, this angle specifies the direction the tap will point (the orientation of
the y-axis for branch taps and of the x-axis for nonbranch taps). The default is
zero degrees.
RTOB
(Run-to-Branch) Inserts branch fittings at pipe corners so that the fittings run is
parallel to the pipe inlet and the branch is parallel to the pipe outlet.
SCALE x
Scales fittings uniformly along x-, y-, and z-axes. The default is 1.0.
SELECT
(Default) (S) Selects components automatically from the autoselection file.
NOSELECT
(S) Automatic selection is not done.

INSERT FITTING
SIZE text
Specifies the nominal pipe size to use for autoselection (18-character limit).
Neither the pipeline label nor the nearest NPS property is used to get size
information. The modifier is most useful in conjunction with SELECT and
SPEC when NOHOOK is on.
Note that size is specified as a text string, not as an integer or real number, so it
is important to use the same format here as you use in the size field of your
autoselection file.
SPEC text
Identifies a fitting specification or classification (18-character limit). Neither the

pipeline label nor the nearest SPEC property is used to get specification
information. SPEC is most useful when you use the modifiers SIZE and
SELECT with NOHOOK on.
STEM
Aligns the components model y-axis with the specified direction.

Select one of the six major compass or orthogonal directions as follows:
NORTH Along the positive y-axis
SOUTH Along the negative y-axis
EAST Along the positive x-axis
WEST Along the negative x-axis
UP Along the positive z-axis
DOWN Along the negative z-axis
Only the first letter is required.
North (+Y) is the default direction for P&IDs, and Up (+Z) is the default
direction for three-dimensional models. For three-dimensional models, the
default is +X if the pipe is vertical. For P&IDs, the default is -X, regardless of
flow direction, when the pipe runs along the y-axis.
The default orientation for taps is perpendicular to the flow (to the tangent of the
flow for elbows). If you use STEM to indicate a direction not perpendicular to
the flow, you will get an error message. If you want a nonperpendicular
orientation, use the orientation modifiers.
STOCK name
(S) Selects a component from the stock number file. When you use STOCK, in
the case of a selection file such as that for P&IDs, the specification for name
must be a valid stock number or a generic name, (see CVPD.P.SELECTION).

INSERT FITTING
With this modifier, automatic flange and gasket insertion is not done, and
changes in end type, size, and specification are not automatically recorded on
the line. If you want to use the ENDTYPE, NPS and/or SPEC properties, insert
them on the fitting or nozzle Cnodes with the INSERT PROPERTY command.
Or, in the case of the ENDTYPE property, add an ENDT field to your stock
number file. (See the Data Extract/Data Merge Reference for more information
on this command.)
TAP
Indicates that the fitting (or the first fitting of a group of fittings) is to be
inserted as a tap (attached to an existing fitting). It is entered once per
command, anywhere within the modifiers. Note that you cannot use TAP, with
NOHOOK. Any fitting or group of fittings can be inserted with TAP except
groups whose first fitting has more than two Cnodes or groups that contain
assemblies. Elbowlets can only be inserted at elbows.
The BSIZE modifier is required for autoselection. The size of the tap fitting
(and the group of fittings inserted with it) is determined by the value of the
BSIZE property and, for branching tap fittings, by the size of the pipeline to
which the parent fitting is hooked. Nonbranch tap fittings (modeled along the
x-axis in the library part) use the value of BSIZE as the size of the tap; branch
fittings (modeled along the y-axis in the library part) take their larger size from
the parent fitting and the smaller size from BSIZE.
To locate the tap along the centerline of the parent fitting, use the OFFSET
modifier or the justification modifiers, NEAR, CENTER, and FAR. The default
offset is at the center of the centerline. To locate the fitting a distance away
from the centerline, in the plane perpendicular to the centerline, use the
PROJECTION modifier. The default projection for branching fittings is zero,
which places the origin at the centerline of the parent fitting; the default for
nonbranching fittings is the radius of the cylinder or cone in the library part,
which places the origin at the surface of the fitting.
With OFFSET and PROJECTION distances set, the orientation of the tap
determines the exact location of the tap on the parent fitting. The default
orientation plane for taps is perpendicular to the flow. For branching fittings
(modeled on the y-axis), this is the same as for non-TAP insertions. For
nonbranching fittings (modeled on the x-axis), the fitting is rotated so its x-axis
is perpendicular to the pipeline. Elbowlets, inserted only on elbows, are
oriented in the direction of flow. The tap (and fittings inserted with it) point in
the direction specified by the STEM and ROTATION modifiers, in the plane
perpendicular to the centerline as determined by the OFFSET modifier.
Instead of using OFFSET and PROJECTION (or their defaults), you can use
explicit coordinates to position the tap. After identifying the parent fitting, use a
semicolon in getdata and enter a location for the origin of the tap. This method
of insertion is mutually exclusive with OFFSET and PROJECTION and fully

INSERT FITTING
defines the location of the tap on the parent fitting. The orientation of the
centerline of the tap (y-axis for olet-type fitting, x-axis otherwise) is then
determined by the STEM and ROTATON modifiers or the system orientation
modifiers. Because the angles you specify with the orientation modifiers are not
relative to the direction of the pipeline, you can point the tap in a direction that
is nonorthogonal to the radial or longitudinal axes of the parent fitting.
The NPS and TAP properties are placed on the Cnodes of the tap fitting (the first
fitting if TAP is used to insert a group of fittings). These properties affect
pipeline reporting. Other fittings that are hooked to the tap are treated as
components on the branch line originating at the tap.
TOLERANCE x
(S) Sets the fabrication tolerance or limits for adjacent fittings to pass the
collinearity check. The default is.05 database units, unless another value is set
by SELECT PPARAMETERS.
TRIM
Inserts an elbow and trims it to the bend angle of the corner. You can only select
one vertex per command. The /net elbow has the same stock number as an
untrimmed elbow of the same size, spec, and type.
The modifier TRIM is only used with elbow fittings that have the TRIM
property with an angle value equal to the angle of the elbow before trimming;
for example, those provided for ELR9 and ELR4.
When you use TRIM, enter the fitting name as usual (for example, ELR9). The
command looks for the appropriate fitting with TRIM appended to the name
(for example, CVPD.F.ELR9.TRIM). A nodal figure with a multisegmented
internal Nline is automatically constructed.
The curvature of the internal Nline equals the bend angle. The value of the
TRIM property is updated to equal the angle after trimming. A 90-degree elbow
can be trimmed to less than 45 degrees, but a 45-degree elbow cannot be
trimmed to greater than 45 degrees.
XSCALE x
Scales the fitting along the x-axis of the model Nfigure (see the conventions
under ZSCALE).
YSCALE x
Scales the fitting along the y-axis of the model Nfigure (see the conventions
under ZSCALE).

INSERT FITTING
ZSCALE x
Scales the fitting along the z-axis of the model Nfigure. When fittings are not
selected automatically (NOSELECT), these conventions are used:
If you do not enter a scale modifier, uniform scaling is performed on all
axes; the default scale is 1.
Enter only one scale modifier, and the command assumes that scaling is
uniform on all axes.
If you enter XSCALE and YSCALE, ZSCALE is equal to YSCALE.
If you enter XSCALE and ZSCALE, YSCALE is equal to ZSCALE.
If you enter YSCALE and ZSCALE, XSCALE is equal to YSCALE.
When fittings are selected automatically (SELECT), the values you enter
with the scale modifiers replace those from the specification files.
System Orientation Modifiers

AX AY AZ CPLANE PX PY PZ MX MY MB ANG MODEL FROMVU TOVU
VECTOR TX TY TZ VIEW
These modifiers let you orient a component manually. For a full description of
their use, refer to the command ROTATE ENTITY (see the online command
documentation).
The following procedures use the selection files in the CVPD.M.SPEC catalog.
These are activated by the directory CVPD.DIRECTORIES. This directory is the
default. The command SELECT PPARAMETERS can be used to specify another
directory.
Piping specification B7A is used in the following sample procedures.
Procedure 1
For inline insertion,
1. Enter INSERT FITTING, the component name, and any other modifiers.
When you use the modifier SELECT, specify the name of the component, for
example, BALV or ELR9. SELECT is a default in SELECT PPARAMETERS.
When you use the modifier NOSELECT, specify the name of a library part, for
example, CVPD.F.BALV.
When you use the modifier STOCK, specify the stock number or name, for
example, BALVRF300AD-02.

INSERT FITTING
2. Enter a colon. The system prompts MODEL ent. Select the pipeline(s) (Nlines)
on which you want the fitting to be inserted. These locations can be on the same
or different pipelines.
3. Press RETURN.
In the above procedure, hooking (HOOK) is the default. Hooking connects an

inserted fitting to an existing pipeline. For automatic selection of components from
an autoselection file, you must insert a component into a pipeline with a label, or
specify the SIZE and SPEC modifiers.
This inline method breaks the pipeline at the point of insertion. Properties on the
original pipe are automatically applied to the resulting pipes.
You can insert a single fitting or group of fittings at multiple locations, including
corners. The insertion can be on the same or on different pipelines that you specify
with selections or coordinates. The Reference and Pline methods of insertion
described on the following pages are special cases.
Procedure 2
For face-to-face insertion,
When you use the modifier SELECT, specify the name of the component; for
2. Enter a colon. The system prompts MODEL ent. Enter CNODE to ensure
that your selections go to the correct nodes.
3. Select the Cnodes at the faces of fittings or nozzles or at pipe ends to attach the
face of the named fitting. The inserted fitting is automatically positioned in
relation to the existing pipeline component. For example, the new fitting is put
in front or behind an existing fitting, depending on which side you select. This
applies to groups as well; in that case, the whole group is positioned
appropriately.
4. Press RETURN.

INSERT FITTING
The face-to-face method attaches the inserted fitting to an existing fitting and
hooks the fitting into any adjacent pipe. A zero-length piece of pipe is created to
connect the two fittings and establish connectivity.
Please note: You do not always have to enter the CNODE mask. If your
selection along a pipe is within an inch and not more than two percent of the
pipelines length away from a Cnode, face-to-face insertion occurs. This automatic
trapping is not affected by any selected system tolerances or traps.
Procedure 3
For tap insertion,
1. Enter INSERT FITTING and a component or group of components.

If you are not using an autoselection file (NOSELECT or STOCK), only
olet-type branch fittings can be inserted as taps. Otherwise, any fitting or any
group of fittings that does not contain more than two Cnodes on the first fitting
of the group can be inserted. There is a limit of ten fittings per tap group.
2. Enter the TAP modifier and any other modifiers you want to apply. You cannot
use NOHOOK with TAP. With autoselection, you must use the BSIZE
modifier. Use OFFSET and PROJECTION to position the tap or explicitly
locate it in getdata. Use the STEM, ROT, or system orientation modifiers to
define the orientation of the tap (see the TAP modifier description).
3. Enter a colon. The system prompts MODEL ent. Select the parent fittings nodal
figure to which the tap (or tap group) is to be attached. If you are using the
explicit coordinate method, enter a semicolon in getdata and specify a location
for the origin of the tap.
Only nodal figures and bends can be specified. There is a limit of ten taps per
fitting or bend. Taps cannot be inserted on taps.
4. Press RETURN.
By default, the origins of branching taps are centered along the x-axis
(centerline) of the parent fitting; the origin of nonbranch taps are centered along
the x-axis at the surface of the parent fitting. The default orientation of the tap is
perpendicular to the flow.
Procedure 4
For referencing insertion,
When you use the modifier SELECT, specify the name of the component, for

INSERT FITTING
2. Enter a colon. The system prompts Model ent. Select the pipe into which
you want the fitting inserted.
3. Enter a semicolon (;) to continue the command.
4. The system prompts MODEL loc. Specify the exact location along the pipe
where you want the fitting to go. It is helpful to use the getdata modifier REF
and the CNODE mask to identify a reference point (in this case the Cnode at the
face of the fitting). Enter the getdata modifier LOC to deactivate the CNODE
mask.
Increment from the reference point using Cartesian incremental coordinates
(IX, IY, IZ) for a location on the selected pipe parallel to a major axis. Use
incremental polar coordinates (IR) for a skewed pipe. The specified location
must fall on the same piece of pipe as the first selection.
Instead of using explicit coordinates, you can select along the pipeline.
However, your selection must be at the correct depth or it will not lie on the
pipe.
5. Press RETURN
Procedure 5
For pipeline (Pline) insertion,
1. Enter INSERT FITTING and the name of a 90-degree elbow such as ELR9.
2. Enter PLINE and any other modifiers.
3. The system prompts MODEL ent. Select a pipeline where you want 90-degree
elbows.
4. Press RETURN.
Only one pipeline can be processed per command.
Procedure 6
For group insertion with group modifiers,
1. Enter INSERT FITTING, the names of fittings, and the group modifiers you
want to use. Separate the fitting names with the modifier AND.
2. Enter a colon. The system prompts Model ent. Select the pipeline or pipelines
(Nlines) where you want the group of fittings inserted. The insertion locations
can be on the same or different pipelines.

INSERT FITTING
Since NOFLAN is a group modifier, no flanges are placed on any of the fittings
in the group (which only affects BALV and CHKV in this example).
3. Press RETURN.
Procedure 7
For group insertion with nongroup modifiers,
1. Enter INSERT FITTING, the name of fittings, and the nongroup modifiers you
want to use. Separate the fitting names with the modifier AND.
2. Enter a colon. The system prompts MODEL ent. Select the pipeline(s) (Nlines)
where you want the group of fittings inserted. These locations can be on the
same or different pipelines.
3. Press RETURN.
Because of its position, STEM N applies only to the BRAN.
Examples
The following examples show how to construct line 0-8242-10-B3A from the
CVPDC plant model.
The set of autoselection files in the catalog CVPDC.ASFILE is accessed with the
SELECT PPARAMETERS DRFILE CVPDC.DRFILE command.
Automatic selection and flange/gasket insertion are on. The part type is
arrangement.

INSERT FITTING
To give you a frame of reference, the complete route of the line is shown before
fitting insertion. The dashed boxes (Example 1, Example 2, Example 3) show the
portions of the line involved in the examples.
Example 1
Put the initial flange face-to-face with the Cnode at the origin of the line. The line
does not start at a nozzle, but the initial Cnode has the ENDTYPE property that a
nozzle Cnode would have. This affects the automatic flange insertion and end type
compatibility checking.
#n# INSERT FITTING FLAN: MODEL ent CNODE d1

INSERT FITTING
Insert 90-degree long radius elbows at every corner (with room). When there are
reductions in line size, wait to use the PLINE modifier until after you have
inserted the reducers.
#n# INSERT FITTING ELR9 PLINE: MODEL ent NLIN d2
Move the two elbows, and the pipe between them, down so the initial elbow is
flush with the flange. This can be easier than routing the line so the elbows fit
exactly.
#n# TRANSLATE ENTITY: MODEL ent NFIG d3d4;CNODE d5d6

INSERT FITTING

INSERT FITTING
Example 2
The following set of commands puts in branch fittings, valves, flanges, and a line
attachment. Several command features are shown:
Specifying that a new separate line originates at a fitting (NLABEL).
NLABEL A, represents any text that you choose. Here the label only serves to
get the TERMNAM property. Later, when you route the branch from the fitting,
use the correct label.
Selecting different branch fittings (WLET vs SLET) by using the generic name
BRAN.
Orienting fittings with STEM and ROTATE.
Inserting groups using AND (GATV and CHKV).
Automatically inserting flanges/gaskets.
#n# INSERT FITTING BRAN BSIZE 4 NLABEL A STEM N: MODEL ent d7
#n# INSERT FITTING GATV ROTATE y45 AND CHKV: MODEL ent CNODE d8
#n# INSERT FITTING DRAN STEM D: MODEL ent d9
#n# INSERT FITTING BRAN BSIZE 1 NLABEL A STEM E: MODEL ent d10

INSERT FITTING
The first branch fitting (d7) is a weldolet, and the second (d10) is a sockolet, as
called for by specification B3A.

INSERT FITTING
Example 3
The following set of commands illustrates some additional features:
The next two commands replace the elbow at d11 with a tee.
#n# DELETE FITTING: MODEL ent d11

#n# INSERT FITTING BRAN RTOB: MODEL ent d12
The next command attaches a reducer to the unhooked Cnode at the tee. A new
separate line is to start from the reducer. Label the line when you route it.
#n# INSERT FITTING CRED NSIZE 8: MODEL ent CNODE d13
Put the center of the valve at the selected location d14. Opening and closing
flanges are put on automatically. STEM N orients the y-axis of the valve in the
North direction.
#n# INSERT FITTING GATV CENTER STEM N: MODEL ent d14
Position a flange in front of the selected location d15 and automatically place an
opening flange in front of it because automatic flange/gasket insertion is on. It may

INSERT FITTING
be easier to put the trimmed elbow (d16) in first and then select the Cnode at its
inlet so that the flange will go in face-to-face with the elbow.
#n# INSERT FITTING FLAN FAR: MODEL ent d15
Trim and insert a 45-degree elbow on a 44.23-degree corner.
#n# INSERT FITTING ELR4 TRIM: MODEL ent d16
Put a 90-degree short radius elbow on the last corner. An earlier command
specified 90-degree long radius elbows at every corner. That earlier command
failed at this corner because of lack of room. The line has been routed exactly so
that the elbows will fit on these last two corners.
#n# INSERT FITTING ESR9: MODEL ent d17
Insert a flange at the end of the line. The command does not insert two flanges as it
did at d15 because the Cnode has an ENDTYPE property of F3RF. The property
causes the Cnode to be treated as the face of a nozzle.

INSERT FITTING
#n# INSERT FITTING FLAN: MODEL ent CNODE d18

INSERT FITTING
Example 4
Insert a tap (a BRAN) with a nipple, gate valve, and cap, attached to it. The
enlargement in the inset shows this more clearly.
#n# INSERT FITTING BRAN TAP BSIZE 1 AND NIPL AND GATV AND CAPP:
MODEL loc d
Notes
The following general notes will help you when using the INSERT FITTING
command.
1. You can activate a grid as an aid to routing pipes:
#n# SELECT GRID DG scale
#n# ECHO GRID
2. To specify a location for INSERT FITTING, select the grid. The fitting is
inserted on the pipeline at the point perpendicular to your selection.

INSERT FITTING
3. The default generic gasket and flange names used by INSERT FITTING are
FLAN for flanges and GASK for gaskets. You can change either of these values
with the following command naming the flanges or gaskets you want:
#n# SELECT PPARAMETERS FNAME name GNAME name
4. If the insertion point for a fitting is within the trapping distance (less than an
inch and not more than two percent of the pipes length) of an existing
component, the point is adjusted so that the new fitting is attached to the nearest
face of the existing fitting.
5. Eccentric reducers have an eccentricity factor (of minus one-half of the
difference between the smaller and the larger outer diameters) in the SCLZ
field of the autoselection file. This is used to shift the downstream pipeline until
a fitting or nozzle is reached. Any improper alignment created is marked with a
SKEW property, which is reported by the REPORT PIPE command. The
property is removed when you use INSERT FITTING to insert a matching
eccentric enlarger.
6. The master catalogs use outer diameters in order to get an eccentricity for all
schedules of pipe. However, there may be critical conditions where the inner
diameter must be used in calculating the eccentricity. In those cases, you should
change the master catalogs to meet your specifications.
7. INSERT FITTING assumes library fitting parts that are modeled as follows:
In the inch (IN) unit.
With unitized dimensions: the origin is on the left side (or center); the main
axis is in the +X direction; and stems or branches are in the +Y direction.
With elbows oriented like an L in the XY plane.
With reducers from large to small end (left to right).
With flanges from neck (weld-end) to face (left to right).
So that fittings that do not break the pipe (saddles, olets) have the part
property NOBREAK.
So that the fittings length along the pipe after insertion equals SCLX (or
twice SCLX for tees and crosses).
With internal Nlines that have an INTERNAL property and an additional
BRANCH property if they are a branch.
Fittings to be inserted parametrically are modeled the same as regular
fittings, but are prepared with additional properties.
Inlet Cnodes (upstream) have the property PSCL with a value of 1.
Outlet Cnodes (downstream) have the property PSCL with a value of 2.
Branch outlets (only one per fitting) have the property PSCL with a value of
3. When there is more than one, the PSCL property is placed on the +Y
branch.

INSERT FITTING
Each dimensioned internal Nline has the property PSCL with a single
integer value for a straight Nline or multiple integer values for a
multi-segmented Nline, listed in order in the direction of flow. These values
point to positions in the list of parameters for that component, for example.,
a PSCL value of 3 points to the third number.
Each curved Nline has the property PLEN with two values (inserted with a
space between them) that indicate which parameters to use from a list (for
example, PLEN values of 5 and 2 point to the fifth and second parameters).
The two values are used to get the X- and Y- coordinates of the outlet
Cnode, relative to the inlet Cnode, in an XY- plane. INSERT FITTING
places the elbow origin at the corner and orients the elbow so that the
Cnodes lie on the pipe. The legs are scaled to equal the X and Y parameters;
this determines the final location of the Cnodes on the pipe (the path of the
Nline is adjusted accordingly).
8. A maximum of 35 fittings can be inserted in one command. This excludes
automatically inserted gaskets, but includes automatically inserted flanges.
9. Only one fitting (no groups) can be inserted on a Cnode that has more than two
connecting pipes (junction), or on a Cnode that has two nonparallel connecting
pipes (corner).
10. The AND modifier can be used upto a limit of nine times in a command.
11. NOHOOK is incompatible with AND.
12. The x-scale value in the component directories equals the fitting length (or half
its length for tees and crosses). The y-scale is the height of the component. For
standard fittings, these dimensions come from the x-scale and y-scale columns
in the autoselection file. The width (z-scale) is by default equal to the height.
Parametric fittings have a P in the z-scale column to indicate that dimensions
from the fitting parameter file are used for scaling. The PSCL property value(s)
on each Nline in the library part tells the command which dimension(s) to use.
(A PSCL value of 3 points to the third dimension in the list.) See the Piping
Specification User Guide for a description of parametric fitting symbol library
(CVPD.FP).
13. A group or a single fitting involving a change of size or specification can be
inserted only once per pipeline per command unless the net change of size
and/or spec is zero. For example, on a 4 line, the group CRED NSIZE 6 AND
STEE AND CRED NSIZE 4 can be inserted at multiple locations; whereas the
group CRED NSIZE 6 AND STEE AND CRED NSIZE 8 can be inserted
once.
14. If you select an internal Nline, the fitting you insert is face-to-face with the
nearest Cnode attached to the internal Nline.
15. Component names are limited to 40 characters. If you use the modifier STOCK,
your stock numbers are limited to 40 characters also. Size and spec fields have a
limitation of 18 characters, including spaces.

INSERT FITTING
16. When inserting elbows with the PLINE option you must identify a pipeline by
digitizing or by explicit coordinates. You cannot use WIN, VWIN, or TAG
names.
17. Specification files (autoselection) created with the GENERATE PSFILE
command have an IFC# (Insert Fitting Code) that is used by INSERT FITTING
to insert tees, line attachments, elbows, corner fittings in general, gaskets, and
flanges.
18. If
a fitting does not have a FITTYPE property, the IFC# is used to determine an
appropriate FITTYPE which is inserted on the fitting. See the Piping
Specification User Guide for a table of FITTYPE values.
19. INSERT FITTING automatically inserts and/or updates the following
text-valued properties:
ENDTYPE
DUCTSIZE
NPS
SPEC
STOCKNO
With the exception of SPEC, the library components are created with these
properties. The properties have filler text (periods), which is replaced with the
appropriate information as the component is inserted. To speed updating, the
filler text should be the same length as the text to be inserted.
20. The autoselection file for fittings can contain either one or three columns for
size data. The first type of autoselection file can specify single-reducing
fittings, with both the header size and new size (or branch size for reducing tees
or olets) in the SIZE field. The second type of autoselection file can specify
both single- and double-reducing fittings.
For the two types of files, the total width can be up to 148 columns, and all
nonsize headers are the same. The following rules apply to three-size files:
a. The size fields (SIZE, NSIZ, BSIZ) can each contain a maximum of 18
characters.
b. The SIZE field can contain only one size.
c. SIZE must always be greater than NSIZ.
d. BSIZ can be greater than, less than, or equal to SIZE.
See the Piping Specification User Guide for more information on preparing the
autoselection file.
21. The standard model representations inserted by INSERT FITTING are
uniformly scaled according to the X and Y dimensions from the autoselection
file. This uniform scaling is appropriate for many types of components. If more
accurate dimensioning is required for specific components (such as a branch

INSERT FITTING
fitting with unequal inlet and outlet or branch legs), you can parametrically
scale specially prepared library parts. The dimensions for these parts are
obtained from a fitting parameter file rather than interactively or from the
autoselection file.
Prepare a fitting parameter file if you want to insert parametric fittings
efficiently; otherwise, INSERT FITTING has to search through the whole
fitting parameter file. The P in the z-scale column of the autoselection file
prepared by GENERATE PSFILE tells the INSERT FITTING command to go
to a fitting parameter file to get the scales for the component.
If your directory file references a PFIT file, that is used; if not, INSERT
FITTING searches the fitting parameter files assigned to layer ranges and
finally the default PAFILE. See the Piping Specification User Guide for detailed
instructions on preparing a special parametric fitting parameter file.
22. Thetext entered for the size and specification modifiers (SIZE, NSPEC,
BSIZE) does not need to be delimited unless it begins with a special character
(for example, 5 does not need delimiters, but.5 does).

Description
Use this command to create pipe break symbols on pipes that have been detailed
by CREATE DETAIL. Break symbols can be inserted on either single or double
line pipe. You can create a single break symbol at the end of a pipeline or a pair of
break symbols in the middle of a piece of pipe. When two symbols are created, the
detail graphics between them is automatically blanked.
Break symbols are detail graphics, specific to the view in which they are created.
They are automatically placed on the same layer as the pipe detail graphics.
Valid Modes
Model mode, Draw mode, or Draw View mode
Syntax
#n# INSERT PBREAK [modifier]: getdata
Modifiers
The following diagram shows the flow of INSERT PBREAK modifiers. For a full
A description of the modifier follows.
XHA
Creates crosshatching in the closed portion of the pipe break symbol.

Procedure 1
To insert break symbols at the selected location on a pipeline,
1. Enter the command INSERT PBREAK. Use the optional modifier XHA if you
want to crosshatch the break symbols.
2. Enter a colon. The system prompts MODEL ent. Select the pipe that you want
to break. It must have been previously detailed using the CREATE DETAIL
command.
3. The system prompts MODEL loc. Select the two points along the pipe where
you want break symbols. The line between them is automatically blanked.
4. If you want to place more break symbols, use a colon or semicolon instead of a
RETURN to reenter Step 3.
5. Press RETURN.
Procedure 2
To insert break symbol at the end of the selected pipeline,
2. Enter a colon. The system prompts MODEL ent. Select the pipe whose end
you want the break symbol on. It must have been previously detailed using the
CREATE DETAIL command.
3. The system prompts MODEL loc. Select one point at or near the end where you
want the break symbol to be placed. A single break symbol is placed at the end
of the pipe that is nearest to the selection on the drawing.
4. If you want to place more break symbols, use a colon or semicolon instead of a
RETURN to reenter Step 3.
5. Press RETURN.
Procedure 3
To insert break symbols at the end of all the pipelines that are perpendicular to the
view,
2. Enter a colon. The system prompts MODEL ent. Select the pipe whose end
you want the break symbol on. It must have been previously detailed using the
CREATE DETAIL command.

3. A single break symbol is placed at the end of any pipe that is perpendicular to
the view. When the command determines that the pipe is perpendicular, it does
not prompt MODEL loc to ask for the location. When the MODEL ent
prompt again appears, you can select another pipe, if you wish.
4. To turn off the XHA modifier within the command, use a period instead of
pressing RETURN to get back to the modifier processor. Then enter a colon to
initiate getdata.
5. Press RETURN.
Example 1
Insert break symbols on a pipe with single-line graphics that have been created
with the command CREATE DETAIL and the modifier SINGLE.
#n# INSERT PBREAK: MODEL ent d1 MODEL loc d2d3
Example 2
Place a break symbol at the end of a double-line pipe (d1). The crosshatched break
symbol is entered at the end of the pipe that is nearer to the second selection (d2).

The third selection adds a pipe break symbol to the end of a pipe that is
perpendicular to the screen (d3).
#n# INSERT PBREAK XHA: MODEL ent d1 DRAW loc d2 ; d3
Example 3
Insert a pair of break symbols in a mid section of a detailed pipe, and a single
break symbol at the end. After the pair of symbols is inserted (d2d3), a colon is
entered. In response to the MODEL ent prompt (d4), select the pipe again. Enter a
single selection in response to the MODEL loc prompt (d5). The break symbol is
placed at the end that is nearer to the single selection.

#n# INSERT PBREAK XHA: MODEL ent d1 MODEL loc d2d3: MODEL ent
d4 MODEL loc d5
Notes
The following general notes will help you further in using the INSERT PBREAK
command.
1. Break symbols for both double and single line detail graphics take their size
from the outer diameter of the pipeline.
2. If a selection for a break symbol location is not directly on a pipe, a
perpendicular is dropped from the selection to the nearest point on the pipe.

3. Break symbols are detail graphics (B-splines) that are related to the pipe. They
are automatically oriented within the plane of the view in which you select the
model entity. You can create symbols in multiple views within the same
command; just select the entities you want in each view.
4. Delete pipe break symbols by using the DELETE ENTITY command in Draw
View mode. To restore the blanked pipe between the symbols, use SELECT
RELATIONSHIP ON and the UNHIDE PIPE command (with the PWIN
modifier if you want to limit the area of unblanking). See the
Visualization/Preparation Reference for more information about UNHIDE
PIPE.
5. INSERT PBREAK does not need SELECT RELATIONSHIP ON to identify
detailed pipe. The command automatically uses the relationship between the
details and the pipe nodal line so that you can identify the pipe by selecting any
of its details.

Description
Use this command to annotate pipelines, placing drawing text labels at specified
locations. The size and specification for the label come from the point on the
pipeline that you select.
Valid Modes
Draw mode
Syntax
#n# INSERT PLABEL [modifiers]: getdata
Modifiers
The following diagram shows the flow of INSERT PLABEL modifiers. For a full
follows.
CREC
(Capped Rectangle) Draws a rectangle with rounded ends around the text.
REC
(Rectangle) Draws a rectangle around the text.

Procedure
The following is the procedure for using the INSERT PLABEL command.
1. Specify SELECT TEXT with the modifiers HEIGHT, WIDTH, or ANGLE or

accept the defaults for these parameters. The centering and spacing defaults for
INSERT PLABEL (LJT and USPACE) cannot be changed.
2. Enter the INSERT PLABEL command with either the REC or the CREC
modifier if you want to use it. The default is to place no rectangles around the
text. Enter a colon.
3. The system prompts MODEL ent. Select the pipeline that you want to label.
4. The system prompts DRAW loc. Select a location for the label. The text is
always left-justified from the point of the selection.
5. If you want to place more labels on the same or a different pipeline, use a colon
or a semicolon instead of a RETURN to reenter Step 3.
6. Press RETURN.
Example 1
The first selection identifies the pipe to be labeled and the second gives the location
for the text. The default is to place the text along the horizontal.
#n# INSERT PLABEL: MODEL ent d1 DRAW loc d2
Example 2
Use the modifier CREC to create a Capped Rectangle around the label text. The
colon repeats the command with the CREC modifier still in effect.
#n# SELECT TEXT HEIGHT .15 WIDTH .15 FONT 1

#n# INSERT PLABEL CREC: MODEL ent d1 DRAW loc d2: MODEL ent d3
DRAW loc d4
Example 3
Insert labels at different angles so that they go in the same direction as the pipes.
SELECT TEXT ANGLE lets you change the default orientation of the label text.
This is particularly useful for placing a series of labels in the same orientation.
You can also use ROTATE ENTITY to change the orientation of an individual
label after it has been inserted.
Use the following commands to place two pipe labels: ANGLE 90 is used to place
the first (d2) and ANGLE 30 to place the second (d4).
#n# SELECT TEXT ANGLE 90

#n# INSERT PLABEL REC: MODEL ent d1 DRAW loc d2
#n# SELECT TEXT ANGLE 30

#n# INSERT PLABEL REC: MODEL ent d3 DRAW loc d4
Notes
The following general notes will help you further in using the INSERT PLABEL
command.
1. The origin of the label is at the left end of the text. This means that the label is
left-justified from the point that you select.
2. The default is to place text labels with no rectangles. To turn off the rectangle
modifiers (REC and CREC) within the command, use a period (.) instead of
RETURN to get back to the modifier processor, then immediately enter the
colon.
3. By default, labels are inserted horizontally. To insert labels at other angles, use
the command SELECT TEXT with the modifier ANGLE before INSERT
PLABEL. To correct labels after INSERT PLABEL, use the command
ROTATE ENTITY with the modifier ANGLE.
4. You can move the pipeline labels (model text) to a layer that can be excluded for
plotting (such as layer 230) so that only drawing text labels are visible in the
finished drawing.

Description
Use this command to insert pipe support symbols into a pipeline at the specified
location(s).
Valid Modes
Model mode
Syntax
#n# INSERT PSUPPORT [modifiers]: getdata
Modifiers
The following diagram shows the flow of INSERT PSUPPORT modifiers. For a
full explanation of modifier diagrams, see the Preface.
follows.

1 NAME text
Use of this modifier is compulsory. It gives the name of the pipe support to be
used. The name of the modifier itself can be omitted. The name cannot exceed
40 characters.
1 SPEC text
Gives the specification for the pipe support. It gives the name of the
autoselection file while the directory containing the autoselection file can be
selected using SELECT PPARAMETER command. The name cannot exceed
18 characters.
1 STEM
Aligns the pipe support symbols local y-axis in the specified direction.
One of the major compass or orthogonal directions can be selected as follows:
NORTH. Along the positive y-axis.
SOUTH. Along the negative y-axis.
EAST. Along the positive x-axis.
WEST. Along the negative x-axis.
UP.Along the positive z-axis.
DOWN. Along the negative z-axis.
Only the first letter needs to be specified.
Up (+Z) is the default direction. The default is +X, if the pipeline segment is
vertical.
The default orientation when the CONNECT modifier is used is perpendicular
to the flow (to the tangent of the flow for elbows). If you use STEM to indicate
a direction not perpendicular to the flow, you will get an error message. If you
want a non-perpendicular orientation, use the orientation modifiers.
1 ROTATE angle
Rotates the pipe supports local y-axis about the pipeline by the specified angle
(in degrees). This modifier is most useful when the desired orientation is not
parallel to one of the six compass or orthogonal directions. The angle is
measured clockwise (looking in the direction of the flow) as follows:
From the top of the pipe (+Z), or vertically for all pipe segments except
straight vertical ones (that run along the z-axis)
From +Y for straight vertical segments
From the direction specified with the STEM modifier

When the CONNECT modifier is used, this angle specifies the direction in
which the y-axis of the pipe support symbol will point. The default is zero
degrees.
1 CONNECT
Indicates that the pipe support symbol is to be attached to an existing fitting,

rather than being attached to the pipeline. It is entered once per command,
anywhere within the modifiers.
Example 1
This example inserts a pipe support symbol with the selection name PS+01,
which is specified in the autoselection file SFSI. The support symbols y-axis is
rotated 45 degrees about the pipeline.
#n# INSERT PSUPPORT PS+01 SPECIFICATION SFSI ROTATE 45.0: MODEL
ent d
Example 2
This example inserts a pipe support with the selection name PS-22, which is
specified in the autoselection file SFSI. The support is attached to a fitting, so the
fitting should be selected instead of the pipeline itself.
#n# INSERT PSUPPORT PS-22 SPECIFICATION SFSI CONNECT: MODEL ent d

Description
Use this command to create linear dimensions between different pipe segments
and between pipe segments and other entities supported by INSERT
LDIMENSION.
The linear dimensions between the selected entities can be created with the
following orientations
Horizontal
Vertical
Point to point
The default dimensioning parameters can be set using the SELECT DIMENSION
command. To check the current default dimensioning parameters use the LIST
DIMENSION command.
Valid Modes
Draw Mode and Model Mode
Syntax
#n# INSERT REFDIMENSION [modifiers]: getdata

Modifiers
The following diagram shows the flow of INSERT REFDIMENSION modifiers.
For a full explanation of modifier diagrams, see the Preface.


follows.
1 ALIGN
Aligns the dimension line with that of an existing dimension. To align a

point-to-point dimension, the angle of the imaginary line between the two
points being dimensioned must be equal to the angle for the existing
point-to-point dimension.

1 ANGLE x
Measures the distance between two points projected onto an axis which is at an
angle of x with respect to horizontal.
1 ARROWHEAD
Indicates that dimension lines end in an arrowhead. The following second- and
third-level modifiers specify the arrowhead type and characteristics.
2 CIRCLE
Creates the arrowhead as an unfilled circle, useful when creating an ANSI

dimension origin.
2 DIAMETER x
Specifies the diameter of a dot or circle arrowhead (Default is 0.05 in or 1.25

mm.) DOT or CIRCLE must be specified to see the diameter specification.
3 BOTH
Applies the given diameter to both the first and second entities selected. When
BOTH is assumed, the specified diameter value is retained on both arrowheads
(whether or not that arrowhead is a circle or dot).
3 FIRSTDIAMETER
Specifies that the DIAMETER modifier changes the arrowhead at the first
selected entity. FIRST CIRCLE or FIRST DOT must be specified with
DIAMETER x FIRSTDIAMETER.
3 SECONDDIAMETER
Specifies that the DIAMETER modifier changes the arrowhead at the second
selected entity. SECOND CIRCLE or SECOND DOT must be specified with
DIAMETER x SECONDDIAMETER.
2 DOT
Specifies dot arrowheads corresponding to both the first and second selected
entities.

2 FILLED
Specifies filled triangular arrowheads corresponding to both the first and

second selected entities.
2 FIRST
Defines the first arrowhead corresponding to the first selected entity, as

described by the following third-level modifiers.
2 LENGTH x
Specifies the arrowhead length (default is.15 in or 4 mm). 2
2 NONE
Specifies no arrowheads corresponding to the first and second selected entities.
2 OPEN
(JIS default) Specifies open arrowheads corresponding to both the first and
second selected entities.
2 RATIO x
Specifies the ratio x of the arrowhead length to the base width (default is 3).
2 SECOND
Defines the second arrowhead corresponding to the second selected entity, as

described by the following third-level modifiers.
3 CIRCLE
Creates the arrowhead as an unfilled circle, useful when creating an ANSI
dimension origin.
3 DOT
Specifies a dot arrowhead.
3 FILLED
Specifies a filled triangular arrowhead.

3 NONE
Specifies no arrowhead.
3 OPEN
(JIS default) Specifies an open arrowhead.
3 SLASH
Specifies an arrowhead that has the form of a boldface slash cutting through the
extension line at a 45-degree angle and a short continuation of the dimension
line beyond the extension line.
4 CENTER
Specifies a slash-center arrowhead that is the same as a slash arrowhead with

the omission of the short continuation of the dimension line beyond the
extension line. This prevents overlapping on an adjacent dimension line.
4 END
(Default) Specifies a slash-end arrowhead that is the same as the slash

arrowhead.
3 STANDARD
(Default) Specifies the standard unfilled triangular arrowhead.
2 SLASH
Specifies an arrowhead that has the form of a boldface slash cutting through the
extension line at a 45-degree angle and a short continuation of the dimension
line beyond the extension line.
3 CENTER
Specifies a slash-center arrowhead which is the same as a slash arrowhead with

the omission of the short continuation of the dimension line beyond the
extension line. This prevents overlapping on an adjacent dimension line.
3 END
(Default) Specifies a slash-end arrowhead which is the same as a slash

arrowhead.

2 STANDARD
(Default) Specifies the standard unfilled triangular arrowheads corresponding

to both the first and second selected entities.
1 ARROWS
Specifies placement of the dimension arrows according to the following

second-level modifiers.
2 IN
(Default) Places the dimension lines and arrows inside the extension lines.
2 OUT
Places the dimension lines and arrows outside the extension lines.
1 CHAIN
Creates a chain of linear dimensions. This permits you to select a number of

points to be dimensioned and the location for the corresponding collinear
dimension lines. The dimension value is centered automatically and aligned
between the extension lines for each dimension. You must identify the entities
to be dimensioned in the proper order.
2 CUMULATIVE
Creates a chained continuous set of cumulative linear dimensions from the

identified start to end points.
2 TOTAL
Also creates a total dimension for the identified start and end point. If this
modifier is selected, you must additionally select a location for creating total
dimension.
1 CIRCLE
Inserts dimension of a circles diameter in a linear dimension format outside the

circle.
1 DTANGENT
Finds approximate tangency points to arcs or B-splines for dimensioning

distance between such entities.

With associative linear dimensions, DTANGENT automatically maintains the

tangency condition if the entity where the tangency exists is modified.
1 DUAL
Specifies that the dual dimensioning units are located in the manner indicated
by the following second-level modifiers.
2 ABOVE
Places the primary dimension value above the secondary (positional method) or
the bracketed dimension value above the unbracketed (bracket method).
2 BELOW
Places the primary dimension value below the secondary (positional method) or
the bracketed dimension value below the unbracketed (bracket method).
2 LEFT
Places the primary dimension value to the left of the secondary (positional
method) or the bracketed dimension value to the left of the unbracketed (bracket
method).
2 OFF
Turns dual dimensioning off.
2 RIGHT
Places the primary dimension value to the right of the secondary (positional
method) or the bracketed dimension value to the right of the unbracketed
(bracket method).
1 FIRSTDATUM
Selects the first datum location depending on the following second level
modifiers. Default datum location is the center of the identified pipe segment.
2 INSIDE
Creates the dimension from the inside or near side of the selected pipe segment
diameter.

2 OUTSIDE
Creates the dimension from the outside or far side of the selected pipe segment
diameter.
1 GAP
Specifies the gap between the extension line and entity.
2 BOTH x
(Default) Specifies the gap x on both extension lines.
2 FIRST x
Specifies the gap x on the first extension line.
2 SECOND x
Specifies the gap x on the second extension line.
1 HORIZONTAL
(Default) Measures the horizontal distance between identified start and end
points.
1 ISOMETRIC
Specifies that an isometric dimension is created according to the following

second-level modifiers. These second-level modifiers are used to insert linear
dimensions into isometric drawings. The dimensions are true values, not
projections onto the isometric view plane. The XAXIS, YAXIS, ZAXIS, and
ABSOLUTE modifiers identify auxiliary directions which are used to
determine the direction of the extension lines for the dimension.
2 ABSOLUTE
(Default) Specifies that the extension lines are chosen automatically to lie
parallel to the isometric view and perpendicular to the actual point-to-point
distance being dimensioned.
2 PARALLEL
Specifies that dimension text is not parallel to the extension line. The
dimension text is parallel to the x-axis.

2 STANDARD
(Default) Specifies that dimension text is parallel to the inclined extension lines
to show three-dimensional effects.
2 XAXIS
Specifies that the extension lines are parallel to the x-axis. The dimension is the
actual perpendicular distance between these lines.
2 YAXIS
Specifies that the extension lines are parallel to the y-axis. The dimension is the
2 ZAXIS
Specifies that the extension lines are parallel to the z-axis. The dimension is the
1 LEADER
Specifies leader characteristics according to the following second-level

modifiers.
1 MODFILE filename
Incorporates the components of the modifier file filename into the command.
These components are executed in sequence after the modifier that precedes
MODFILE, if any.
1 NOCIRCLE
Turns off the CIRCLE modifier.
1 NODTANGENT
(Default) Cancels search for tangency points on selected entities to be

dimensioned. Nullifies the DTANGENT modifier.
1 NOTTOSCALE
Underlines dimensions not to scale. Underlines all main text, including

tolerances, fractions, and dual dimensions.

2 OFF
Turns off the underline.
2 ON
Turns on the underline.
1 PARALLEL
Measures the distance between two points projected onto an axis which is
parallel to a specified line, Nline, or string segment.
1 PERPENDICULAR
Measures the distance between two points projected onto an axis which is
perpendicular to a specified line.
2 END
Draws the leader to the end of the dimension value. Used only for
non-horizontal dimensions of ANSI standards.
2 HEAD
(Default) Draws the leader to the beginning (head) of the dimension value.
Used only for non-horizontal dimensions of ANSI standards.
1 PPOINT
Measures the straight line (point-to-point) distance between two points. The
dimension line is parallel to the straight line between the two points.
1 PRECISION
Specifies the number of digits to the right of the decimal point for a decimal
format, or the denominator value (n=1, 2, 4, 8, 16, 32, or 64) for fractional
format.
PRECISION takes the following second-level modifiers.
2 BOTH n
(Default) Sets both primary and secondary dimensioning precision to n decimal

places (default is 3).

2 PRIMARY n
Sets primary dimension precision to n decimal places (default is 3).
2 SECONDARY n
If dual dimension is specified, sets secondary dimension precision to n decimal

places (default is 3).
1 SECONDDATUM
Selects the second datum location depending on the following second level
modifiers. Default datum location is the center of the identified pipe segment.
2 INSIDE
Creates the dimension to the inside or near side of the selected pipe segment
diameter.
2 OUTSIDE
Creates the dimension to the outside or far side of the selected pipe segment
diameter.
1 SUPPRESS
Suppresses the specified dimension and/or dimension lines (by the order of the
selections).
2 DIMENSION
Suppresses the selected dimension line(s).
2 EXTENSION
(Default) Suppresses the selected extension line(s).
3 BOTH
Suppresses both dimension/extension lines.
3 FIRST
Suppresses the dimension line to the first extension line, or suppresses the
extension line off the first selected end point.

3 NEITHER
(Default) Specifies that none of dimension/extension line is suppressed.
3 SECOND
Suppresses the dimension line to the second extension line, or suppresses the
extension line off the second selected end point.
3 THIRD
Suppresses the third dimension line for solid dimensions with ARROWS OUT.
Used only with the DIMENSION modifier for JIS and ISO standards.
1 TEXT
Controls the characteristics and placement of dimension text according to the

following second- and third-level modifiers.
2 APPENDED delimited text
Appends text to the dimension value or main text. The dimension text is
appended whether the dimension text was computed automatically or keyed in
after the TEXT MAIN modifiers. Enclose the text in delimiters if other
modifiers are to follow or if the text itself includes blank spaces or special
characters.
2 AUTOMATIC
(Default) Specifies that dimension values are calculated automatically.
2 FIXED
Specifies that dimension text values remain fixed even if the geometry changes.
The dimension values are not associative. For example, if the part is created
with a dimension of 4.0 and the model is later reduced down to 1.25, the text
still appears as 4.0.
2 HEIGHT x
Defines the text height (default is the current text height selected).
2 HORIZONTAL
Specifies horizontal text. Used for ISO and JIS dimensions.

2 JUSTIFICATION
Positions the text by creating and using an imaginary box, which encloses the
main text, to describe nine location options. These location options work in
conjunction with the location of the cursor in the graphics area. The x is used
below to approximate the box and the locations.
LJT CJT RJT

TJT x x x
MJT x x x
BJT x x x
Combinations of two third-level modifiers describe each of these locations. You

can use TJT, MJT, or BJT with one of the following LJT, CJT, or RJT.
Text justification applies only to a dimension which has nonsolid dimension
lines (ANSI standard).
The justification may be changed if the system moves the text to maintain a
legal dimension (such as placing the text outside when it will not fit inside the
extension lines).
3 BJT
Bottom justification. The selected location for text indicates the bottom edge of
the text box.
3 CJT
Center justification. The selected location for text indicates the middle of the
left and right edges of the text box. Applies only to dimension text between two
extension lines.
TEXT JUSTIFICATION MJT CJT, which is the default, locates the text origin
at the center of the text box.
3 LJT
Left justification. The selected location for text indicates the left side edge of
the text box. Applies only to dimension text between two extension lines.
3 MJT
Midheight justification. The selected location for text indicates the line parallel
to the text line, that passes through the midheight point. MJT and CJT are the
default for dimension text that is between two extension lines.

3 RJT
Right justification. The selected location for text indicates the right edge of the
text box. Applies only to dimension text between two extension lines.
3 TJT
Top justification. The selected location for text indicates the top edge of the text
box.
2 LOCATION
Draws the text leader line to the location indicated by the following third-level
modifiers, with respect to the dimension text.
3 AUTOCENTER
Centers the dimension text between the extension lines.
3 MANUAL
(Default) Specifies that you position text manually.
2 MAIN delimited text
Suppresses the calculated dimension value including TOLERANCE. You

supply the main dimension text. Enclose the text in delimiters if other modifiers
are to follow or if the text itself contains blank spaces or special characters.
2 ORIENTATION
Orients dimension text as directed by one of the third-level modifiers below.

Currently, ORIENTATION applies only to some dimensions that have nonsolid
dimension lines like those in ANSI standard.
3 HORIZONTAL
Sets dimension text horizontal. TEXT ORIENTATION HORIZONTAL is the

default for nonsolid dimensions.
3 PARALLEL
Sets dimension text parallel to the dimension lines. PARALLEL is the default
for a dimension having a solid dimension line.

3 PERPENDICULAR
Sets dimension text perpendicular to the dimension lines.
3 VERTICAL
Specifies that dimension text is vertical.
2 PREFIXED delimited text
Attaches the dimension text to the beginning of the dimension value of the main
text. Enclose the text in delimiters if other modifiers are to follow or if the text
itself includes blank spaces or special characters.
2 SYMBOL
Prefixes symbols to the dimension value, as specified by the following

third-level modifiers. You cannot use this modifier if you used the TEXT MAIN
modifier combination to specify the main dimension text.
3 DIAMETER
Inserts a diameter symbol in front of the dimension text.
3 NONE
(Default) Specifies no symbol.
3 SQUARE
Inserts a square in front of the dimension text.
2 TANGENT
(Default) Specifies text tangent (parallel) to the dimension line. Used for ISO
and JIS dimensions.
1 TILTANGLE x
Specifies that the extension lines for the inserted linear dimension be created at
the specified angle. The range of the angle is between -80.0 and +80.0 degrees.
The default is 30.0. Cannot be used with ANGLE, PARALLEL, and
PERPENDICULAR.

1 TOLERANCE
Creates tolerance text. A tolerance is zero unless second- and third-level

modifiers set another value.
2 BOTH x
(Default) Sets both positive and negative values to x for the primary and
secondary dimensions. The secondary values are converted to the secondary
units, if dual dimensioning is specified.
2 OFF
Turns tolerance off.
2 NEGATIVE x
Sets negative tolerance values to x for either primary or secondary dimensions.

The secondary negative tolerance value is x converted to the secondary units, if
dual dimensioning is specified. Note that x must be a positive value. Keying in a
negative value causes that value to become positive. (-)x(-)=(+)
2 POSITIVE x
Sets positive tolerance values to x for either primary or secondary dimensions.

The secondary positive tolerance value is x converted to the secondary units, if
dual dimensioning is specified.
2 PRECISION n
Specifies the number n of digits to the right of the decimal point for decimal
format, or the denominator value (n=1, 2, 4, 8, 16, 32, or 64) for a fractional
format. ISO and JIS standards require TRAILING0 in SELECT DIMENSION
or CHANGE DIMENSION to get decimal zeroes in a dimension value
requiring only an integer.
Precision is specified according to the following third-level modifiers.
3 BOTH n
(Default) Sets both the primary and secondary dimensioning precisions to n

decimal places (default is 3).
3 PRIMARY n
Sets primary dimensioning precision to n decimal places (default is 3).

3 SECONDARY n
If dual dimension is specified, sets secondary dimensioning precision to n

decimal places (default is 3).
2 PRIMARY x
Sets the primary dimension tolerances according to the following third-level

modifiers.
2 SECONDARY x
If dual dimension is specified, sets the secondary dimension tolerances

according to the following third-level modifiers.
3 BOTH x
(Default) Sets both positive and negative values to x for the primary/secondary
dimension.
3 NEGATIVE x
Sets a negative tolerance value to x for the primary/ secondary dimension. Note
that x must be a positive value. Keying in a negative value causes that value to
become positive.
3 POSITIVE x
Sets a positive tolerance value to x for the primary/ secondary dimension.
2 TYPE
Controls tolerance type according to the following third- level modifier
3 DASHED
Specifies dashed tolerance.
3 INCREMENTAL
(Default) Specifies incremental tolerance.
3 LIMIT
Specifies limit tolerance.

3 ROUNDED
Specifies limit tolerance with the minimum necessary to distinguish between

the tolerance values.
1 VERTICAL
Measures the vertical distance between the identified start and end points.
Procedure
To insert reference dimensions,
1. Enter INSERT REFDIMENSION.

3. Enter a colon. The system prompts DRAW/MODEL ent-end.
4. Select two points on the pipelines or entities to be dimensioned.
5. The system prompts DRAW loc.
6. Select a point to specify the location of the dimensions.
7. Select more points for dimension creation if required.
8. If you have specified TOTAL modifier, the system prompts DRAW loc.Select a
point to specify the location of the total dimension.
9. Press RETURN.
Example 1
This example illustrates the creation of linear dimensions using the default
parameters. The dimension measures the horizontal distance between the entity
end points selected by d1 and d2. The dimension is placed at the location specified
by d3 and the dimension line is horizontal.

#n# INSERT REFDIMENSION: DRAW/MODEL ent-end d1d2 DRAW loc d3

DRAW/MODEL ent-end

Example 2
This example illustrates the dimension creation in the vertical direction.
#n# INSERT REFDIMENSION VERTICAL: DRAW/MODEL ent-end d1d2 DRAW loc
d3 DRAW/MODEL ent-end

Example 3
This example illustrates the dimension creation from point to point.
#n# INSERT REFDIMENSION PPOINT: DRAW/MODEL ent-end d1d2 DRAW loc
d3 DRAW/MODEL ent-end

Example 4
This example illustrates the creation of a chained set of dimensions.
#n# INSERT REFDIMENSION CHAIN: DRAW/MODEL ent-end d1d2 DRAW loc d3
DRAW/MODEL ent-end d4d5d6

Example 5
This example illustrates the creation of a cumulative set of chained dimensions.
#n# INSERT REFDIMENSION CHAIN CUMULATIVE: DRAW/MODEL ent-end d1d2
DRAW loc d3 DRAW/MODEL ent-end d4d5d6

Example 6
This example illustrates the creation of chained dimensions along with the total
dimension.
#n# INSERT REFDIMENSION CHAIN TOTAL: DRAW/MODEL ent-end d1d2 DRAW
loc d3 DRAW/MODEL ent-end d4d5d6 DRAW loc d7

Example 7
This example illustrates the creation of dimensions with the first datum at the near
side or inside the selected pipelines.
#n# INSERT REFDIMENSION FIRSTDATUM INSIDE: DRAW/MODEL ent-end d1d2
DRAW loc d3 DRAW/MODEL ent-end

Example 8
This example illustrates the creation of dimensions with the first datum at the far
side or outside the selected pipelines.
#n# INSERT REFDIMENSION FIRSTDATUM OUTSIDE: DRAW/MODEL ent-end
d1d2 DRAW loc d3 DRAW/MODEL ent-end

Example 9
This example illustrates the creation of dimensions with both the first datum and
second datum at the near side or inside the selected pipelines.
#n# INSERT REFDIMENSION FIRSTDATUM INSIDE SECONDDATUM INSIDE:
DRAW/MODEL ent-end d1d2 DRAW loc d3 DRAW/MODEL ent-end

Example 10
This example illustrates the creation of dimensions with the first datum at the near
side or inside the selected pipeline and the second datum outside the selected
pipeline.
#n# INSERT REFDIMENSION FIRSTDATUM INSIDE SECONDDATUM OUTSIDE:
DRAW/MODEL ent-end d1d2 DRAW loc d3 DRAW/MODEL ent-end

Notes
The following general notes will help you further in using the INSERT
REFDIMENSION command.
1. The CHAIN modifier suppresses one extension line at each common end point
of adjoining dimensions (to prevent overplotting). It also suppresses overplotted
arrowheads and changes the type of arrowhead, when necessary, to conform to
drafting standards. When the first arrowhead is SLASH END and the second is
either SLASH END or SLASH CENTER, each common end point of adjoining
dimensions are changed to one SLASH CENTER arrowhead (with one
suppressed arrowhead). The second arrowhead of the last dimension is SLASH
END. When both the first and second arrowheads are DOT or both are SLASH
CENTER, one of the two arrowheads is suppressed at each common end point
of adjoining dimensions. When the first arrowhead is STANDARD, FILLED, or
OPEN and the second arrowhead is STANDARD, FILLED, OPEN, or DOT and
the drafting standard selected is JIS or ISO, each common end point of
adjoining dimensions are changed to a DOT arrowhead. The second arrowhead
of the last dimension is the same as the first arrowhead of the first dimension.
2. To keep the dimensions in a chained set, the first datum of a dimension is
always the second datum of the previous dimension. This is true for all the
dimensions from the second one to the last, no matter what modifiers have been
selected for second datum.
3. When using the DTANGENT modifier, you must specify the arc or B-spline
before you select a line. Failure to do so will cause the dimension to shift to the
other end of the line when you execute the REGENERATE DIMENSION
command. The tangency condition can be negated to either entity by a
user-response of END,ORG, VERT, etc. If a point-to-point entity modifier is
used for the first entity, the prompt Tangent to is issued again. If a tangency
condition cannot be met, a system message is issued.
4. When using the PRECISION modifier, ISO and JIS standards require
TRAILING0 in SELECT DIMENSION or CHANGE DIMENSION to get
decimal zeroes in the dimension value requiring only an integer.
For ANSI Standards, when a precision value is to be rounded to fewer digits
than the total number available, the procedure should be as follows.
When the first digit discarded is less than 5, the last digit retained should not
be changed. For example, 3.46324, if rounded to four digits, would be
3.463; if rounded to three digits, 3.46.

When the first digit discarded is greater than 5, or if it is a 5 followed by at

least one digit other than 0, the last figure retained should be increased by
one unit. For example, 8.37652, if rounded to four digits, would be 8.377; if
rounded to three digits, 8.38.
When the first digit discarded is exactly 5, followed by zeros, the last digit
retained should be rounded upward if it is an odd number, but no
adjustment made if it is an even number. For example, 4.365, if rounded to
three digits, would be 4.36. The number 4.355, if rounded to three digits
would also be 4.36.
5. For dimension text you can add tolerance (feature control) symbols to a linear
dimension value when you create the dimension by using font 9 dimension text
and control characters. A superscript or subscript should have only one line of
text and the same angle as the major text.
The system accepts up to 502 characters in a text string, but graphically
produces a maximum of 477 characters.

This chapter explains the general purpose and use of the piping commands, their
mode of usage, the syntax and the modifiers.

REFERENCE STRUCTURE
REPORT PIPE
ROUTE PIPE
SAVE ANNOTATIONS
SPLIT PIPE
TRANSLATE EQUIPMENT
TRANSLATE ISOMETRIC
VERIFY DISTANCE

Description
Use this command to modify a pipeline and pipeline components. It provides the
following features:
Add a reducing fitting and automatically propagate the change along the
pipeline.
Delete a reducing fitting and automatically propagate the change along the
pipeline.
Change the size of an entire pipeline and pipeline components.
Change the size of a pipeline branch and branch line components.
Change the size of a reducing fitting and automatically propagate the change
along the pipeline.
Change the spec of an entire pipeline and pipeline components.
Change the size and spec of a pipeline and automatically propagate the change
along the pipeline.
Change the size of a pipeline without any change in branch line sizes and
without any interactive input.
Delete an entire pipeline branch.
Change a pipeline number.
Check all pipeline segment lengths against the minimum spool length as set by
SELECT PPARAMETERS PIPING SPOOL.
Scroll the view/drawing if a fitting to be modified requires interactive input,
such as a size reducing fitting, and if the fitting is outside the current
view/drawing boundary.
Execute various combinations of the above modifiers.
Valid Modes
Model mode
Syntax
#n# MODIFY PLINE [modifiers]: getdata

Modifiers
The following diagram shows the flow of MODIFY PLINE modifiers. For a full

follows.
1 ADD
Adds a reducing fitting to a pipeline and propagates the resulting changes along
the pipeline.
2 NSIZE new size
Specifies the new size of the reducing fitting.
2 NOBEND
Restricts bend insertion (the original bends are deleted).
2 NOELBOW
Restricts elbow insertion (the original elbows are deleted).
2 STEM select
Aligns the components model y-axis with the specified direction.

Select one of the six major compass or orthogonal directions as follows:
NORTH Along the positive y-axis
SOUTH Along the negative y-axis
EAST Along the positive x-axis
WEST Along the negative x-axis
UP Along the positive z-axis
DOWN Along the negative z-axis
Only the first letter needs to be specified.
Up (+Z) is the default direction. The default is +X if the pipe is vertical.
1 CHECK
Activates minimum spool length checking. If the proposed pipeline changes

violate the minimum spool length, a report is generated and the command
terminates without any change to the original pipeline.

1 CHG
Indicates a change in the pipeline and pipeline components according to the

following second level modifiers.
2 BRANCH new branch size
Indicates the new branch size of a branch fitting.
2 LABEL pipe label
Indicates a change in the pipeline label.
2 LINENO pipeline number

Used to identify a pipeline by line number.
2 REDUCER reducing fitting new size
Specifies the new size of the reducing fitting.
2 PSIZE pipeline new size
Specifies the new size of the pipeline.
2 PSPEC pipeline new spec
Specifies the new specification of the pipeline.
2 NOBEND
2 NOELBOW
1 DEL
Indicates the deletion of either a reducing fitting or a branch pipeline, depending

on the second level modifiers selected.
2 BRANCH
Indicates the deletion of a branch pipeline. Also processes an Nfig branch and a
stubin branch.

2 REDUCER
Indicates the deletion of a reducing fitting.
2 NOBEND
2 NOELBOW
1 NOCHECK
Indicates not to check for minimum spool length. This modifier is mutually
exclusive with CHECK modifier.
1 SAMEBSIZE
Preserves all branch sizes without any interactive input.
1 SCROLL
Scrolls the view/drawing until the fitting appears inside the current
view/drawing boundary, if a fitting to be modified requires interactive input,
such as a size reducing fitting, and if the fitting is outside the current
view/drawing boundary.
Example 1
This example illustrates the minimum spool length checking while modifying a
pipeline. The command is terminated with generation of a report as the minimum
spool length condition is not met.
#n# SELECT PPARAMETERS PIPING SPOOL 0.4
#n# MODIFY PLINE CHG PSIZE 10 CHECK LINENO PIPE-01
(tracing pipeline)
The highlighted pipe segment is too short.

pipe segment miptr = 8

pipe segment length = 0.235
minimum spool length = 0.4
Example 2
This example illustrates the result of the command in the previous example with
minimum spool checking disabled.
#n# SELECT PPARAMETERS PIPING SPOOL 0.4
#n# MODIFY PLINE CHG PSIZE 10 NOCHECK LINENO PIPE-01

(tracing pipeline)

Example 3
This example illustrates the scrolling of view during the process of interactive
input. The pipeline model as shown in the figure below is to be modified.

#n# MODIFY PLINE CHG PSIZE 8 SCROLL: MODEL ent d1


Notes
The following general notes will help you further in using the MODIFY PLINE
command.
The MODIFY PLINE command does not handle eccentric reducers properly in
some small percentage of cases. Before making any modification to eccentric
reducers, it is advisable to save your part in the event that this problem occurs.

Description
Use this command to offset a pipeline or pipeline segment (including pipeline
components) in a selected direction and distance.
The pipeline segment(s) to be offset must be perpendicular to the offset direction

specified. For example, when the offset direction is EAST, pipeline segments
parallel to the X-axis will not be eligible for offset.
Adjacent pipeline segments are extended/shortened by the appropriate distance.
Please note: Only the compass directions of EAST (+X), WEST (-X),
NORTH (+Y), SOUTH (-Y), UP (+Z) and DOWN (-Z) are supported.
Valid Modes
Model mode
Syntax
#n# OFFSET PLINE [modifiers]: MODEL ent d1.... dn

Modifiers
The following diagram shows the flow of OFFSET PLINE modifiers. For a full
follows.
The direction modifiers are mutually exclusive and are based on the model
coordinate system.

1 BOP
Moves the selected pipe segments and makes their bottom (current CPL-Z)
elevation the same as a selected reference pipes bottom elevation.
1 COP
Moves the selected pipe segments and makes their center elevation the same as
a selected reference pipes center elevation.
1 CHECK

1 WOP
Moves the selected pipe segments and makes their west (current CPL -X) side
the same as a selected reference pipes west side.
1 DOWN
Offsets the identified pipeline segments in the -Z direction.
1 DIST distance in database units
Offsets the identified pipeline segments by the specified amount in the specified
direction.
The default is half of the pipe outer diameter.
1 EAST
Offsets the identified pipeline segments in the +X direction.
1 EOP
Moves the selected pipe segments and makes their east (current CPL +X) side
the same as a selected reference pipes east side.
1 NOCHECK
Indicates not to check for minimum spool length. This modifier is exclusive
with CHECK modifier.

1 NOP
Moves the selected pipe segments and makes their north (current CPL +Y) side
the same as a selected reference pipes north side.
1 NORTH
Offsets the identified pipeline segments in the +Y direction.
1 PLINE
Offsets the entire pipeline in the specified direction by the specified amount.
1 SOP
Moves the selected pipe segments and makes their south (current CPL -Y) side
the same as a selected reference pipes south side.
1 SOUTH
Offsets the identified pipeline segments in the -Y direction.
1 TOP
Moves the selected pipe segments and makes their top (current CPL+Z)
elevation the same as a selected reference pipes top elevation.
1 UP
Offsets the identified pipeline segments in the +Z direction.
1 WEST
Offsets the identified pipeline segments in the -X direction.

Example
This example illustrates offsetting pipe segments such that their bottom elevation
is made the same as that of a selected reference pipe.
#n# OFFSET PLINE BOP: MODEL ent d1 MODEL ent d2d3d4

REFERENCE STRUCTURE
REFERENCE STRUCTURE
Description
Use this command to save SMS, SSM and SDDP element information such as
type, position and orientation, and store this information as properties of a plant
design element such as an end CNODE of a pipeline or the nodal figure of a
pipeline fitting.
This information can then be subsequently used by the CREATE ISOMETRIC

and ANNOTATE ISOMETRIC commands to generate a reference dimension to
the selected structure. Use the command SELECT VPMODE or getdata to enable
referencing of viewed parts.
Valid Modes
CADDS level, with a part and drawing active.
Syntax
#n# REFERENCE STRUCTURE: Pipe/Fitting MODEL ent d1 Structure MODEL
ent d2
Modifiers
None

Description
Use this command to change the pipe or pipe section (nodal line) that a pipeline
label (nodal text) is associated with. The label is automatically unrelated from the
original nodal line and then related to the nodal line you identify in getdata.
Valid Modes
Model mode
Syntax
#n# RELATE PLABEL: MODEL ent d 1 MODEL ent d2
Modifiers
None
Procedure
To relate a label,
1. Enter RELATE PLABEL.

2. In response to the first MODEL ent prompt, select the pipeline label (Ntext).
3. In response to the second MODEL ent prompt, select the Nline you want to
relate the label to.
4. Enter RETURN.
Please note: You cannot use this command to change the label on a section of
pipeline or to associate a section of pipe with more than one label.

REPORT PIPE
REPORT PIPE
Description
Use this command to produce a variety of piping and instrumentation reports for
three-dimensional models and P&IDs. These reports contain two kinds of
information: overall pipeline descriptions, and material (or component)
descriptions. Pipeline descriptions are the pipeline label, size, specification,
insulation, and its sources and destinations, excluding branches. Material
descriptions consist of the items that make up the pipelines, such as pipes,
components, or bolt sets.
Valid Modes
Model mode
Syntax
#n# REPORT PIPE [modifiers] ALL or LINENO or: getdata

REPORT PIPE
Modifiers
The following diagram shows the flow of REPORT PIPE modifiers. An asterisk
indicates a default modifier. For a full explanation of modifier diagrams, see the
Preface.

REPORT PIPE
follows.

REPORT PIPE
1 ALL
Examines the part and reports all pipelines found. The default when you use
ALL is to report both labeled and non labeled pipelines. You must use ALL,
LINENO, or getdata to identify pipelines to report.
2 LABELS
Reports only labeled pipelines.
2 NOLABELS
Reports only nonlabeled pipelines.
1 FIELDS text
Controls the format of the pipeline label in the report. You can specify the fields
to include, and their order, in the report.
Use dashes (1-2-S-C-3) to delimit the field designators. Use the character C for
class (specification) and S for size. These characters do not increase the number
value of the fields that follow them (1-2-3-S-C-4-5). The left to right sequence
of the numbers of the fields determines the left to right positioning of the fields
in the report.
The default is 1-2-3-4-5-6-7-8-9. The maximum number of fields allowed is 9
including C and S.
1 FILE filename
Specifies a text file to receive the report. You must use the APPEND or
DELETE modifiers if the file already exists. The file name is limited to 76
characters.
2 APPEND
Adds the report to the specified text file. Items in the report are not tallied with
the items in the file.
2 DELETE
Replaces the contents of an existing text file with the report.
2 LIST
Lists the report while it is being written into the file.

REPORT PIPE
1 FWIDTH n
Specifies the width of the fields in the report. The default is 18. The maximum
field width is 38 and the minimum is 11. The QTY/ITEM field is half the size
of the other fields.
1 IFNONE
If no label appears on the pipeline, then the name of its origin, the name of a
piece of equipment at its origin, or the name of an interconnected pipeline, is
used as the label. The default is to indicate missing labels with asterisks.
1 INCLUDE
Indicates the types of information to include in the materials section of the

report. The default is PIPE COMPONENT SERIES MESSAGES for
three-dimensional models, and COMPONENT SERIES for P&IDs.
When you do not want these defaults, enter INCLUDE followed by one, or
more, or none, of its submodifiers to specify the type of information you want
reported. Only the items specified by the submodifiers are included.
If you enter none of the submodifiers, then none of the corresponding type of
information is included. Only overall pipeline information is reported.
2 BOLT
Includes material descriptions for bolt sets. Use submodifiers to specify

diameter units (Dunits) or length units (Lunits) in millimeters (MM) or inches
(IN). Units symbols (mm if the MM modifier is used and in if the IN modifier is
used) are included in the SPEC field of the pipeline report (for example, 19mm
120mm).
The submodifier FRACTION applies to either Dunits or Lunits that are
specified in inches. The default for metric databases is MM. The default for
english databases is IN FRACTION 16.
3 DUNITS
Diameter units.
4 IN
Inches.
5 FRACTION n
Sets the denominator of the fraction for precision. The default value of n is 16.

REPORT PIPE
4 MM
Millimeters.
3 LUNITS
Length units.
4 IN
Inches.
5 FRACTION n
4 MM
Millimeters.
2 COMPONENT
(Default) Includes material descriptions for components. Use one or more

submodifiers to specify the types of components you want to include. The
different types of components are distinguished by their FITTYPE properties
(see the Piping Specification User Guide for a complete list). If you enter
COMPONENT without any of its submodifiers, the default is to include all
types.
3 ASSEMBLY
Includes material descriptions of assemblies (for instance, FITTYPE 90).
3 FITTING
Includes material descriptions of fittings (any FITTYPE other than those for
assemblies, flanges, valves, and insulation).
3 FLANGE
Includes material descriptions of flanges (FITTYPE 30-38, 20 for gaskets).
3 INSTRUMENT
Includes material descriptions of instruments.

REPORT PIPE
3 VALVE
Includes material descriptions of valves (FITTYPE 10-19, 80-81).
2 MESSAGES
(Three-dimensional default) Includes messages in the report pointing out

design considerations such as inconsistencies in flow, and missing flanges or
elbows, which may or may not be a problem (depending on whether the context
is a P&ID or a three-dimensional model). Serious errors in pipeline
construction that prevent successful reporting are reported whether
MESSAGES is used or not.
2 PIPE
(Three-dimensional default) Includes material descriptions for pipes.
3 UNITS
Specifies the units in which pipe lengths are reported. The default units of
length are meters for metric databases, and decimal feet for English databases.
If dimension properties resulting from SAVE DIMENSIONS exist, they are
automatically used. Use submodifiers to specify the unit and format.
4 FT
Decimal Feet.
4 FTIN
Feet and Inches format.
5 FRACTION n
5 IBELOW n
(If Below) Sets an upper limit for reporting lengths in inches. Lengths above
this limit are in FTIN format. The default limit is 12. Any value between 12 and
zero has the same effect. A negative value for IBELOW reports all lengths in
inches.
4M
Meters.

REPORT PIPE
4 MM
Millimeters.
2 SERIES
(Default) In addition to the overall information, reports each series (sequence of

pipes and components with a single source/destination) separately. This shows
how the command breaks up pipelines into main extensions and branches. Do
not use SERIES with LIST, TALLY, or MULTIPLE.
1 KEY
Generates a unique key in the DESC field for each pipe or component. The
KEY combines the drawing name from the title block Tnode (if available) with
the MIPTR (master index pointer) of the entity.
1 LINENO text
Identifies the pipeline(s) to report. Include complete label, or a combination of

pipeline label fields as defined by LINENO-FORMAT in the directory file.
If the LINENO-FORMAT is not specified in the directory file, then all the
pipelines having the specified string as a subset of their labels are reported.
A set of pipelines can be reported by entering a list of line numbers, separated
by comma. If a space exists in a given pipeline label, then it must be enclosed in
double quotes, that is, a space should be represented as .
1 LIST
Adds one or two fields to the report, depending on the submodifiers used. Do
not use LIST with SERIES, MULTIPLE, or TALLY.
2 ITEM
Adds an ITEM field. For components, this field contains nodal text taken from
the ITEMNO Tnode. This Tnode has an ITEMNO property and is associated
with the components CONNECTOR Cnode. For pipes, nodal text marked by
an ITEMNO property is used.
2 LABEL
Adds a LABEL field containing the pipeline label for each component and pipe
entry. This is used when you to want to merge the resulting report with other
reports, such as Data Extract reports. If there is no label and you use the
IFNONE modifier, the origin name of the pipeline is used.

REPORT PIPE
1 LOOKUP
Based on the type, size, and specification, looks up the components stock
number in the selected autoselection file.
The command determines the type name to be used for lookup by searching the
component, in the following order, for an SNAME property, for the nodal text
on a Tnode, and finally for a COMPNAME property.
If the component cannot be found in the autoselection file, **NOT FOUND**
(rather than a stock number) is printed in the DESC field. If the NOSEL
property is on the fitting, no lookup is done and the value of the STOCKNO
property is printed.
1 MULTIPLE
Formats the report so that line list reports can be combined across multiple
parts. The format of the report is:
Every line starts with a label
Report has no header
Only pipeline descriptions are reported
From/to labels are taken from off page connectors (where applicable),
prefaced by the characters *O
The drawing name from the LASTLINK Tnode is added to the pipeline
description and the from/to labels
Do not use MULTIPLE with LIST, TALLY, or SERIES.
1 PROPERTY text
Puts the value of the specified property in the DESC field. The default is to use
the property STOCKNO. If the indicated property is null-valued or real-valued,
only the name of the property is printed in the DESC field.
1 SPEC text
Determines the material descriptions that go into the SPEC field. The text looks
like that for FIELDS, but only the characters C (class) and S (size) are allowed.
The order of these characters from left-to-right determines the left-to-right
positioning of the class and size fields in the report. Use a dash (-) between the
characters C and S to have class and size side-by-side, connected by a dash
(-) in the report. Use a space between C and S to have class and size in separate
columns in the report. Use a single delimited space if you do not want anything
to appear in the SPEC field. The default is S-C.

REPORT PIPE
1 TREETABLE
Stores the pipeline data in XML format. This XML data is presented in the Java
tree table format, and the report is presented in the user-customized format.
1 TALLY
Adds up the lengths of pipe. It also sorts and tallies the components in a single
pipeline or in a whole piping network. The components are grouped by type
(that is, the values, flanges, gaskets, fittings and bolts are listed together). Do
not use TALLY with LIST, MULTIPLE, or SERIES.
Procedure 1
To generate a pipe report by selecting the pipelines,
1. Enter REPORT PIPE and any desired modifiers. Enter a colon.

2. The system prompts MODEL ent.Select at any point on the pipelines you want
reported.
3. Press RETURN.
The system traces the pipelines in both directions to find their sources and
destinations.
Procedure 2
To specify the pipelines to be reported,
1. Enter REPORT PIPE.

2. Enter the modifier LINENO and the label of the pipeline you want reported, or
ALL, and have all the pipelines reported. Specify any other desired modifiers.
3. Press RETURN.
Example 1
Produce a series report in addition to an overall report for the pipeline. The overall
report lists two sources (P-104A and P-104B) and two destinations (PRODUCT
and C-102) in the FROM and TO columns. No diagnostic messages about missing
elbows are given because the MESSAGES modifier is off for P&IDs.
By default, REPORT PIPE is equivalent to REPORT PIPE INCLUDE SERIES

COMPONENT and includes a listing of components in the order in which they are
encountered in the series; sizes are given in decimal format.

REPORT PIPE
The report is organized by main and branch extensions in the order in which they
are encountered in the tracing. This organization makes it easy to follow the
pipeline when a more detailed analysis is desired.
Neither the order of the series nor the arbitrarily assigned branch numbers will
necessarily be the same if you repeat the command and select in a different place.
The source and destination for each series is listed, even though they are branch
points and therefore not included in the overall report (for example, main
extension 3 goes from P-104B to:2).
#n# REPORT PIPE: MODEL ent d

REPORT PIPE
LABEL FROM TO SIZE SPEC INSUL

107 P-104APRODUCT
P-104BC-102
QTY SPEC NAME DESC

ME #1 P104A :1
PI-414 INSTO
CHKV CHKV
GATV GATV
ME #2 :1 PRODUCT
GATV GATV
CONV CONV
GATV GATV
ME #3 P-104B:2
PI-416 INSTO
CHKV CHKV
GATV GATV
BR #1 :3 :5
GLBV GLBVNC
BR #2 :4 GATV
GATV GATV
ME #4 :1 C-102
FT-409 ORIF3
GATV GATV
CONV CONV
GATV GATV
BR #3 :6 :8
GLBV GLBVNC
BR #4 :7 GATV
GATV GATV

REPORT PIPE
Example 2
Create a simple line list:1, reporting only the sources and destinations of all the
labeled pipelines in the part, according to the Ntext on the Tnodes (from P832B to
EXCHANGER).
No component information is listed because the COMPONENT modifier is not

specified.
#n# REPORT PIPE INCLUDE ALL LABELS
LABEL FROM TO SIZESPECINSUL

OIL-2 P832B EXCHANGER
P832A
OIL-1 RESERVOIRP832A
OIL-2 P832B
Example 3
Produce a materials estimation summary, sorted by types (FLANGE, FITTINGS,
and BOLTS), and totaled using the TALLY modifier.
Bolts are included in the report. The FILE modifier writes the report to the
specified file and displays the message:
PIPELINES SUCCESSFULLY PROCESSED:
Hyphens are not allowed in the file name.

REPORT PIPE
#n# REPORT PIPE INCLUDE BOLT COMPONENT TALLY FILE MAT.0.8340:

MODEL ent d
PIPELINES SUCCESSFULLY PROCESSED:

0-8241
QTY SPEC NAME DESC
1 10-D2BGASK GASKRJ600BC-10
1 12-D2BGASK GASKRJ600BC-12
1 10-D2BWNRJ WNRJRJBW600BE-10
1 12-D2BWNRJ WNRJRJBW600BE-12
1 12-D2BCRED CREDBW40BD-1210
4 10-D2BELR9 ELR9BW40BD-10
16 1 1/4 X 8 3/4STUDSTUDRJ600AE-10
16 1 1/4 X 9STUDSTUDRJ600AE-12
Please note: The following properties affect the REPORT PIPE command.
BRANCH
You must put the BRANCH property on the Nline at the entrance or exit point
to a branch in order to differentiate it from a main entrance or exit.
CONNECTOR
All inline piping components or instruments to be reported must have a Cnode
with the CONNECTOR property.
The Cnode with the CONNECTOR property must be on the outside of the
fitting and must not be the center Cnode of a tee.
ENDTYPE
Two adjacent connect nodes with ENDTYPE properties that begin with the
character F specify bolting. The bolting information is looked up in the
specification (autoselection) file using the selected bolt name, and the size, spec,
and end type of the connect nodes.

REPORT PIPE
EQUIP
To report the name of a component or an equipment Nfigure, put this property
on a Tnode. The name of the item is reported from the first Tnode found with
the EQUIP property, unless a Tnode that does not have any property is found
first.
FITTYPE
The INCLUDE modifier relies on FITTYPE to differentiate types of
components such as equipment, structures, and nozzles from types of inline
piping components such as reducers, valves, elbows, etc. The INSLOC
property, rather than the FITTYPE modifier, is used to differentiate instrument
components.
IGNORE
This property is put on a text node you do not want to use for naming
equipment.
INSLOC (Instrument location)
This property identifies instrument components and gives their location
(mounting) according to the following integer values:
0 Undetermined
1-10 Local mounted (sensing)
11-20Behind local board
21-30Behind board
31-40Local board mounted
41-50Board mounted
51-60Local mounted (controlling)
INTERNAL
This property identifies nodal lines that are internal to inline piping components
(rather than external pipe Nlines).
ITEMNO
LIST ITEM uses this property to identify nodal text for reporting. For
components, Ntext is taken from the Tnode related to the CONNECTOR
Cnode that is marked by the ITEMNO property. For pipes, the Ntext marked by
ITEMNO is used
LASTLINK
This property is put on the title block Tnode. Its text value is usually the
drawing or project name. When you use the modifier MULTIPLE, the Ntext
from this Tnode is combined with Ntext from OPCs.

REPORT PIPE
LPROP (Line Property)

Used only in P&IDs. This property is put on both Cnodes of size and spec break
symbols to indicate a change in the size or spec of the pipeline. It also indicates
whether the two sizes are labeled with the same or with different nodal text
entities.
This information is determined from its integer value:
0 Size change one nodal text entity for both sizes; one Tnodeshared by
both Cnodes
1 Size change separate nodal text for each size; one Tnode for each
Cnode (unshared). Also used on a nozzle Cnode with a related Tnode whose
Ntext is to indicate the initial line size.
2 Spec change Change in specification values.
NOBREAK
Put this property on piping components such as olets that do not break the
pipeline so that pipe lengths are reported correctly.
NOSEL (No Selection)
When this property is on a component, the LOOKUP modifier does not use the
autoselection file to find stock numbers. The stock number on the component is
used so that you can report out of spec components.
NPS (Nominal pipe size)
Use this property in three-dimensional models to indicate changes in pipeline
size on fitting and nozzle Cnodes. The command INSERT FITTING
automatically updates the text value on each reducing component Cnode with
the corresponding size.
OPC (Off-page connector)
This property is used on source and destination Cnodes to indicate an off-page
connection. The MULTIPLE modifier combines the Ntext from OPCs and from
the last link (or title block) Tnode.
SPEC
Use this property in three-dimensional models to indicate changes in pipeline
specifications on fitting and nozzle Cnodes. The command INSERT FITTING
automatically updates the text value on each Cnode of a component affected by
the spec changes and puts the property on the component nodal figure when the
component is inserted with the SPEC modifier.
TERMNAM (Terminus Name)
This property can be used at branch points to indicate the termination
(boundary) of a pipeline.

REPORT PIPE
REPORT PIPE also recognizes pipeline boundaries by the presence of unique

pipeline labels. The text value can give the name of the pipeline owning the
branch point, or it can be left blank. If it is blank, the label of the pipeline in
which the branch point occurs is used.
TERMNAM breaks up networks of interconnected pipelines in which some of
the pipelines do not have labels. It limits the size of a network (the command
handles a maximum of 22 series per network), and defines boundaries for
consistency checking.
REPORT PIPE uses the following conventions to name the sources and
destinations of series which terminate, or originate, at a branch point or at an end
point (Cnode connected to only one Nline).
Branch Point
If the branch Cnode has the TERMNAM property, it is used; otherwise
If the branch point is within the pipeline to which the series belongs, a
number, preceded by a colon, is arbitrarily assigned to the branch point and
used by REPORT PIPE.
If the branch is owned by another pipeline, the name of that pipeline is
used.
Endpoint of Series
If the terminus Cnode has a TERMNAM property, it is used; otherwise, the
following hierarchical procedures apply:
If the Cnode is not related to any Nfg:fullC, the Ntext from a Tnode directly
related to the Cnode is used; otherwise, no name is available and asterisks
are substituted.
If the Cnode is related to a nonnested Nfg:fullC, the name is derived by first
getting:
Ntext from a Tnode directly related to the terminus Cnode (unless the
Tnode or Cnode have the ITEMNO property).
Then getting Ntext from a Tnode belonging to the Nfigure (the first Tnode
with no properties or the EQUIP property).
If Ntext is obtained from both sources, it is combined into one name with
the Nfigure name on the left and a hyphen in between.
The COMPNAME property of the Nfigure is used if there is no Ntext
associated with either the Nfigure or the Cnode. If there is Ntext associated
only with the Cnode, it is combined with COMPNAME; in such a case, the
COMPNAME is on the left and there is no hyphen in between.
The Nfigure name is used if none of the above information is available.

REPORT PIPE
If the Cnode is related to a nested Nfigure (terminus Nfigure is nested in another

Nfigure, which may in turn be nested, etc.), the names from the sources are
combined from left-to-right in terms of their logical distance from the terminal
Cnode, the one on the right being the most closely related. If no Ntext is
obtained from any of the Nfigures above the terminus Nfigure, the name is
derived in the same way as in the nonnested situation described above.
REPORT PIPE interprets piping networks as follows:
Pipelines
Cnodes with the TERMNAM property define boundaries between pipelines
(beyond which consistency checking does not go) even if they are not labeled.
Each unique pipeline line number defines a pipeline. The flow direction of the
series is determined by the direction of the first and last Nlines in the series.
You can repeat the same line number within a pipeline to define the path of a
main extension through an ambiguous branch point.
You can use layering to define the path of a main extension through an
ambiguous branch point. REPORT PIPE assumes that a branch on the same
layer as the pipeline is a continuation of that pipeline.
Pipelines can have multiple sources and destinations defined by the sources and
destinations of their main extensions (except those internal to the pipeline
itself); branches are not included. In the overall pipeline information at the top
of the report, multiple sources and destinations are listed. There is no
correspondence between these sources and destinations (that is, the first source
listed does not necessarily go with the first destination).
Branches and Main Extensions
A main extension (ME) ends at a branch point that has more than one main exit.
It also continues through a branch with only one main exit.
Branches begin at branch exits and do not continue through branch points. A
Cnode can connect only two Nlines in series.
Size and Spec Definition
Size and spec must be available at every point in line (implied unless changed).
Although the pipeline size and spec may be initially defined by the pipeline
label, pipeline labels do not change size or spec. Definitions change at
components with LPROP (in P&IDs), or NPS and SPEC properties (in
three-dimensional models). If LPROP is not found, NPS and SPEC are used
(the normal case in three-dimensional models).

REPORT PIPE
Notes
The following general notes will assist you in using this command:
1. The format of the report is primarily determined by the modifiers SERIES,

LIST, TALLY, and MULTIPLE. These modifiers are mutually exclusive.
2. When you use SERIES, source and destination information, as well as selected
(INCLUDE) component information, is reported for each series.
3. Each series is designated by ME (for a main extension) or BR (for a branch
extension).
4. There is only one source and destination listed for each series (including
branches), although multiple sources and destinations (excluding branches) are
included in the overall report for the pipeline.
5. Names for sources and destinations are defined by:
End Points (for example, an equipment name such as H-108).
Branch Points. Designated by arbitrary (for reference only) sequence
numbers assigned by REPORT PIPE (such as:2). When the series
terminates at a branch point on another pipeline, the reporting name is
formed from the combination of that pipelines label and a sequence
number.
For a complete discussion of the conventions and hierarchies ROUTE PIPE
uses for naming sources, destinations, and components, see the Intelligent
P&ID Managers Guide.
6. The format of pipeline labels is defined in the header of the DRFILE.
7. The REPORT PIPE command has the following limits:
A network of interconnected pipelines not separated (bounded) by
TERMNAM properties can have a maximum of 22 series.
A pipeline can have a maximum of 10 sources and destinations.
8. Use the TERMNAM property to break up a piping network with more than 22
series.
9. The submodifier PIPE includes bends; bends are totaled with straight pipe. An
asterisk (*) indicates the presence of bent pipe.
10. REPORT PIPE only reports instruments that are related to inline piping
components designated with the INSLOC property.
11. The insulation reported in the overall pipeline description is obtained from an
insulation symbol (nodal figure inserted into the pipeline) that has a FITTYPE
of 91. This symbol should not have the CONNECTOR property on a connect
node so as not to be included in component descriptions. Insulation is only
reported for P&IDs.

REPORT PIPE
12. The size and specification reported in the SIZE and SPEC columns of the
overall pipeline description are those that occur most frequently for the
components on the pipeline. They may differ from the size or the specification
of the pipeline).
13. When a pipeline has multiple origins or destinations, the labeled origins or
destinations are reported and the unlabeled origins or destinations are not. A
single unlabeled origin or destination is reported with asterisks.
14. Assemblies are handled differently than other typesof inline components. Upon
insertion, the ENDTYPE properties on their connect nodes are not updated. The
command REPORT PIPE does not include assemblies when you use TALLY.
Also, loose material such as bolting cannot be reported on assemblies.
15. Taps are reported under their parent fittings, indented two spaces. If there is
more than one tap per fitting, the tap lists are separated by a blank line. No
bolting is reported for taps.
16. When there is a main extension or branch that could belong to more than one
pipeline, it belongs to the one that is on the same layer.

ROUTE PIPE
ROUTE PIPE
Description
Use this command to construct pipelines (nodal lines). The pipeline is displayed
as you route it. Modifiers let you adjust the pipeline for elbow room; align and
lock pipelines to the model axes; route pipelines with an offset; and route with a
slope or drop.
Valid Modes
Model mode
Syntax
#n# ROUTE PIPE [modifiers]: getdata
This command uses the following special punctuation and error correction:
COLON (:)
In getdata, a colon returns you to modifier specification. Enter the colon,
specify new modifiers and reenter getdata by typing another colon. Then
continue routing from where you left off.
SEMICOLON (;)
This creates a routed pipeline. The system prompts MODEL loc. You can now
route a new pipeline without exiting the command.
DELETE or RUBOUT
Each press of the key deletes the section of pipe back to the last vertex.
DELETE or RUBOUT is used only in getdata.

ROUTE PIPE
Modifiers
The following diagram shows the flow of ROUTE PIPE modifiers. An asterisk (*)
denotes a default modifier. For a full explanation of modifier diagrams, see the
Preface.
follows.
ALIGN
Aligns and extends a pipeline from the previous segment to the nearest XY, YZ,
or XZ plane of the selected point before routing to that point. This occurs only
if the alignment direction is towards the point.

ROUTE PIPE
When the first pipeline segment is attached to an existing pipeline, fitting, or

nozzle, the pipeline is extended, if possible, in the same direction as the item to
which it is attached. Then the pipeline is routed to the first selected point. The
same procedure is repeated from point to point within the pipeline, with new
segments aligning with previous ones. The last segment, however, does not
align with the item it is attached to.
ATTACH
(Default) Attaches the beginning or end of the pipeline to a nearby connect

node in a pipe, fitting, or nozzle. If there is no pipe, fitting, or nozzle connect
node available, the attachment is made to a nearby nodal line and creates a
connect node at the attachment point. Nozzle or fitting connect nodes already
attached to a pipeline cannot again be attached.
When the beginning of a pipeline is attached, the size, specification, and
alignment are taken from the item it is attached to. If the pipeline is attached to
another pipeline, the two are joined into one pipeline. When such joining
occurs, adjustment for elbow room is done automatically.
BELOW
Routes a pipe below selected locations in the YZ direction. This requires that
the outer diameter of the pipeline be obtained from the autoselection file. The
pipeline is then offset by one half of its outer diameter in the direction
indicated.
BOP
(Bottom of Pipe) Routes the bottom of the pipeline so that the centerline is
above the selected locations in the +Z direction. Incremental coordinates used
when an offset modifier is in effect reference the previous coordinate; the offset
is not used as the reference point for increments.
BRANCH flag
Routes a branch stub-in. When the branch pipe is inserted, Connect nodes
(Cnodes) are created on the branch line and at the intersection of the main line
and to the branch line. A dummy Nodal line (Nline) is inserted between these
two Cnodes. This Nline has a branch property associated to it. This ensures that
it is not included in the pipe length reporting. If the main and the branch lines
have the same diameter, only one Cnode is created at the intersection of the
main and the branch lines.

ROUTE PIPE
BSIZE text
Specifies the branch size. A branch pipeline is inserted only if the specified size
is available in the specification file and is less than or equal to the size of the
main pipeline.
BSPEC text
Specifies the branch specification file.
CENTER
Deactivates the offset modifiers BELOW, BOP, EAST, WEST, NORTH,

SOUTH. When these directions are not in use, no offset is applied.
CLASS text
Specifies the type of item to be looked up in the specification file. There is a

limit of 40 characters. If you do not use this modifier or if you do not enter text,
the routed pipe is selected from the category PIPE, the first field in the
autoselection file.
DROP x
Drops the end of a completed pipeline in the Z direction by x and distributes the
drop distance among the pipe segments. This distribution is proportional to the
distance each pipe travels on the XY plane; vertical segments are also dropped.
The variable x is a real number in database units. Positive numbers move the
end downward; negative numbers move the end upward; zero (0) turns the
modifier off.
EAST
Routes a pipe to the east of the selected location. EAST is the +X direction.
This modifier requires that the outer diameter of the pipeline be obtained from
the autoselection file. The pipeline is then offset by half its outer diameter in the
direction indicated.
ELBOW name
(Default) With LONG, SHORT, or BEND, selects the ratio that is applied to
pipe size to determine the bend radius used for elbow room checking. LONG
and SHORT specify ratios of 1.5 and 1.0, respectively. BEND, the default if
ELBOW is not used, specifies the value of BRATIO or BRAD (whichever is not
zero), as set by SELECT PPARAMETERS.

ROUTE PIPE
The ratio and nominal pipe size (taken from the pipeline label) are used to
obtain the bend radius. Once the radius is known, elbow room can be
determined automatically. If the pipeline does not have a valid label, no elbow
checking is done, and this message appears: ZERO RADIUS USED.
The following applies to route points, whether they are selected or they result
from aligning, offset, or locking operations. When a segment defined by two
points is not long enough to accommodate the tangent length of a pipe bend (or
elbow), the segment is adjusted according to these conditions:
If a segment is less than one half of the tangent length, only the first point is
accepted. In effect, the segment is not inserted.
If a segment is greater that one half of the tangent length, the second point
is adjusted to make the segment long enough to accommodate the bend.
LABEL text
Creates a label (nodal text) using selected text parameters and associates it with
the pipeline. The label must be in the same format as the label heading in the
DRFILE. When you use CHECK and then route from a nozzle, the line size
must be consistent with the size defined in the NPS property on the nozzle
Cnode.
The pipeline size and specification taken from the name are used to look up the
matching pipe item in the autoselection file. For example, from LABEL
1-1-6-B7A, the size (6) and specification (B7A) are used as references. Then
the pipes inner and outer diameters and stock number are taken from their
respective fields in the autoselection file: SCLX, SCLY, and STK#.
LOCK XYZ
(XZY, YXZ, YZX, ZXY, ZYX) Locks pipeline along the three model axes in
the order indicated (you need designate only the first two). If you mistype, the
value defaults to XYZ.
If you use both LOCK and ALIGN, note that alignment is performed before
locking.
NOALIGN
(Default) Indicates that no alignment is done. Use this modifier if you want to
route directly between selected points.
NOATTACH
Does not attach the beginning or end of a pipeline to an eligible Cnode, but
connect nodes are automatically created when this modifier is in effect.

ROUTE PIPE
NOELBOW
No checking for elbow room is done.
NOLOCK
(Default) Indicates no locking.
NORTH
Routes a pipe to the north of a selected location. North is the +Y direction. This
modifier requires that the outer diameter of the pipeline be obtained from the
autoselection file. The pipeline is then offset by half its outer diameter in the
direction indicated
NOSLOPE
(Default) Sloping is not done.
SLOPE x TO y
At each selected location, slopes a pipeline downward by y for every length x

traveled parallel to the XY plane. The derived points are offset from the selected
points by a distance that increases cumulatively until a vertical (z-axis) segment
is encountered. At this point the process starts over. Vertical segments are
shortened by a negative slope and lengthened by a positive slope. The variables
x and y are real numbers in database units. (Default is no slope, that is, SLOPE
1 TO 0.)
SOUTH
Routes a pipe to the south of a selected location. South is the Y direction.

This modifier requires that the outer diameter of the pipeline be obtained from
the autoselection file. The pipeline is then offset by half its outer diameter in the
WEST
Routes a pipe to the west of a selected location. West is the X direction. This
modifier requires that the outer diameter of the pipeline be obtained from the
autoselection file. The pipeline is then offset by half its outer diameter in the

ROUTE PIPE
Procedure
To route a pipe,
1. Enter ROUTE PIPE. Specify any modifiers you want to use.

2. Enter a colon. The system prompts MODEL loc. Select the locations through
which the pipeline will run.
3. Press RETURN
Example1
The following examples use the line in Example 1 as a starting point. Its label is
used to obtain size and specification.
The size and specification are then used to check for elbow room and to insert
INNERDIAM and OUTERDIAM properties on the routed pipe.
The line is deliberately not parallel to the x-axis so as to illustrate the use of
ALIGN. Route and label a short pipeline.
#n# ROUTE PIPE LABEL 0-802-6-B7A: MODEL loc d1d2

ROUTE PIPE
Example 2
This example shows ROUTE PIPE in its simplest form, similar to INSERT
NLINE. NOALIGN and NOLOCK are specified. The command routes directly
from selection to selection.
Because the modifier NOATTACH is specified, the newly routed pipe is not joined
to the existing pipeline. A Cnode, created at the start of the routed pipe, lies on top
of the Cnode at the end of line O-802. Therefore, there are two Cnodes in the same
location.
The pipelines label is not available to obtain size and specification information.
Therefore, elbow checking is not done, as indicated by the message (zero
radius used). Properties are not inserted automatically.
However, you can associate a label using the INSERT NTEXT command, and
assign properties using the INSERT PROPERTY command.
#n# ROUTE PIPE NOATTACH NOALIGN NOLOCK: MODEL loc CNODE d (zero
radius used) IX4IY4IZ4

ROUTE PIPE
Example 3
Route a pipe from a nodal line. The modifier ATTACH is on by default. ROUTE
PIPE breaks the Nline, creates a connect node, and attaches the pipe to it.
#n# ROUTE PIPE LABEL O-802-6-B7A: MODEL loc d1d2

ROUTE PIPE
Example 4
In this example ALIGN is on and LOCK is off.
ALIGN extends pipe segments to the plane of the next selected point before
routing directly to that point. Except for extending for elbow room, no other
extension is done if the plane is behind the aligning segment.
Because neither LABEL nor NOATTACH is used, the new pipe is considered a
continuation of line O-802 and is joined to it to create one line.
#n# ROUTE PIPE ALIGN NOLOCK: MODEL loc CNODE d IX4IY4IZ4

ROUTE PIPE
Example 5
In this example, ALIGN is off and LOCK is on.
The locking sequence is set to YZX. This routes the pipe parallel to the model
axes in the order Y, Z, and then X direction.
#n# ROUTE PIPE NOALIGN LOCK YZX: MODEL loc CNODE d IX4IY4IZ4

ROUTE PIPE
Example 6
In this example, ALIGN and LOCK are both on.
The first segment is aligned and extended to the closest plane (YZ) that the point
defined by IX4IY4IZ4 falls in. Then the pipe is routed along the model axes using
the YZX sequence.
The pipe is extended in the direction of the x-axis first because aligning occurs
before locking.
#n# ROUTE PIPE ALIGN LOCK YZX:MODEL loc CNODE d IX4IY4IZ4

ROUTE PIPE
Example 7
This example shows an adjustment for elbow room. This is required because of
the large bend ratio selected.
With ELBOW BEND, the ratio specified with SELECT PPARAMETERS is used
to check for room for bends. The point entity is inserted to provide visual
indication of the adjustment.
#n# SELECT PPARAMETERS PIPING BRAT 10
#n# ROUTE PIPE NOALIGN LOCK YZX ELBOW BEND: MODEL loc CNODE D1
POI D2 loc adjusted for elbow room

ROUTE PIPE
Example 8
#n# ROUTE PIPE BRANCH BSIZE size 4 BSPEC A7A: model loc dd
Figure 5-1 Main Pipe Diameter is Greater Than the Branch Pipe Diameter
Figure 5-2 Main Pipe and Branch Pipe Diameter is the Same
Notes
The following general notes will help you in using the ROUTE PIPE command.
1. The pipeline is created after approximately 100 routed positions. Additional

locations begin a new pipeline and attach it to the end of the pipeline just
created. The new pipeline has the same properties as the preceding one.
2. Getdata location modifiers such as END, ORG, POI, and VERT are not cleared
after each selection. You need not type them again.
3. The end of a pipeline must be visible on the screen for any attaching process.
4. When using DYNVIEW, ZOOM, REPAINT, or other display manipulations
while in getdata, the path of the routed pipeline disappears from the screen. To
restore the image, press the colon twice.
5. When you want the INNERDIAM, OUTERDIAM, and STOCKNO properties
on the pipeline, use the LABEL modifier to give the size and specification;
otherwise, you must route from a pipeline with that information. When the size
and specification are obtained and a matching stock number is found in the

ROUTE PIPE
autoselection file, the command inserts these properties. However, these

properties are not inserted if you have used SELECT PPARAMETERS
PIPING TYPE P&ID.
6. When ALIGN is on, the last segment will not be automatically aligned if it is
attached to a nozzle or pipeline.
7. If two pipe segments meet at an angle greater than 177 degrees, the two
segments are merged.
8. By convention, the directional modifiers have these equivalences:
EAST=+X
WEST=-X
NORTH=+Y
SOUTH=-Y
BOP=+Z
BELOW=-Z
Use these modifiers to route and offset pipeline from racks, walls, corners, and
other structures, thereby allowing room for the pipeline diameter. These
modifiers are effective only if the diameter can be obtained from the
autoselection directory.
In addition, you can combine the directional modifiers. For example, to offset a
location in the northeast direction, use both NORTH and EAST. You can
change the combination by entering a colon to return to modifier specification.
The offset modifiers previously entered stay in effect. To change the
combination, use CENTER to deactivate previously selected offsets; then enter
the new combination.
9. ROUTE PIPE differs from INSERT NLINE as follows:
Has alignment and three-dimensional locking; INSERT NLINE has only
two-dimensional locking.
Has adjustment for elbow room.
Can create a label (nodal text) and associate it with the pipe within the same
command.
Can insert both diameter and stock number properties using information
stored in the autoselection files.
Selected Nline properties are not put on routed pipe.
10. When the ATTACH modifier is used, the pipe is attached to a nearby Cnode. If
there is a pipe, fitting, or nozzle Cnode nearby (with no other attached pipe),
the new pipe is attached to it. If not, the pipe is hooked to a nearby non-internal
Nline at an existing Cnode.
If no Cnode is available, ROUTE PIPE ATTACH breaks the Nline, creates a
Cnode, and hooks the routed pipe to it.

ROUTE PIPE
11. When you use the direction modifiers (EAST, WEST, etc.), the coordinate
derived from an offset is not used as the reference point for increments. Instead,
the coordinate in effect before the offset is used as the reference point.
12. Youcan set the default values for some of these modifiers with the SELECT
PPARAMETERS PIPING command. If you give new values within the ROUTE
PIPE command, they override the default values.
13. Use SELECT APPEARANCE FONT to change the default font used for routed
pipe.
14. If
you want to prevent short segments from being routed on a P&ID, use
SELECT PPARAMETERS PIPING BRADIUS n, where n is the model units
corresponding to 1/8 inch on the drawing.
15. Theflow direction of a pipe is determined by the direction of routing. Use the
command EDIT NLIN REVERSE if you want to change the direction of the
pipe after it is routed.

SAVE ANNOTATIONS
SAVE ANNOTATIONS
Description
Use this command to save a variety of information relating to a series of pipelines
for subsequent use with the ANNOTATE ISOMETRIC command. Typical of
information that is saved is
ITEM NUMBERS for pipes, fittings, and gaskets

WELD NUMBERS (field and shop)
FROM/TO information
Valid Modes
Model mode
Syntax
#n# SAVE ANNOTATIONS [modifiers]
or
#n# SAVE ANNOTATIONS [modifiers]: getdata
or
#n# SAVE ANNOTATIONS [modifiers] LINENO text

SAVE ANNOTATIONS
Modifiers
The following diagram shows the flow of SAVE ANNOTATIONS modifiers. An
see the Preface.

SAVE ANNOTATIONS

SAVE ANNOTATIONS
1 ATTACHMENT
Generates the FROMTO text property at the beginning and/or end of a pipeline
with the from/to text if the attachment is a valid defined termination; and the
CONTLINE text property if the attachment is a connection to another pipeline.
2 FULL
Enables the user to save the complete identification including the size and
specification of the pipelines.
2 ON
Implicit default.
2 OFF
Deactivates saving from/to information at start or end of pipeline, and

continuation information at the branch connections.

SAVE ANNOTATIONS
1 DIMENSION
Saves the true geometry (XYZ property) of the pipelines in a model.
2 OFF
Deactivates saving dimensions.
2 ALL
(Default) Processes all Cnodes, Nfigures, and Nlines, even if they are blanked
or are on a layer that is not echoed on. This modifier does not include point
entities.
2 CNODE
(Default) Records the coordinates of connect nodes as XYZ properties.
2 NOCNODE
Deactivates recording the coordinates of connect nodes as XYZ properties.
2 DECIMAL
(Default) Expresses the length in decimal format.
2 FEETINCHES n (FTIN n)
Expresses LENGTH in feet and inches. The value n equals the denominator
value (n=1, 2, 4, 8, 16, 32, or 64) for any fractional portion. The last numeric
modifier entered supersedes any previous entries. Entering n=0 deactivates the
modifier and reactivates the modifier DECIMAL.
2 FRACTION n
Expresses LENGTH in the database unit and its fractions. The value n equals
the denominator value (n=1, 2, 4, 8, 16, 32, or 64) for any fractional portion.
The last numeric modifier entered supersedes any previous entries. Entering
n=0 deactivates the modifier and reactivates the modifier DECIMAL.

SAVE ANNOTATIONS
2 INFT n
(Inches per Foot) Expresses LENGTH as feet/inch fraction, but units are
assumed to be in inches. The value n equals the denominator value
(n=1, 2, 4, 8, 16, 32, or 64) for any fractional portion. The last numeric modifier
entered supersedes any previous entries. Entering n=0 deactivates the modifier
and reactivates the modifier DECIMAL.
2 NFIGURE
(Default) Records the coordinates of the origins of nodal figures (components)

as XYZ properties.
2 NONFIGURE
Deactivates recording the coordinates of nodal figures (components) as XYZ
properties.
2 NLINE
(Default) Records the length of nodal lines as the LENGTH property.
2 NONLINE
Deactivates recording the length of nodal lines as the LENGTH property.
2 POINT
Records the coordinates of points as XYZ properties.
2 NOPOINT
(Default) Deactivates recording the coordinates of points as XYZ properties.
1 DOEXIST
(Default) Creates or modifies the XYZ or LENGTH properties.
1 GROUP
Enables the user to group the item numbers for each component in the pipeline.
All items with the same stock number will have the same item number. All
selected pipeline components will have their item numbers grouped. Fittings
will have a separate numerical sequence from bolts and gaskets. Bolts and
gaskets are itemized together, with item numbers for gaskets being prefixed by

SAVE ANNOTATIONS
the letter G and item numbers for bolts being prefixed by the letter B, by
default. This can be changed in either the modifier table or by the third level
modifier, START.
2 SINGLE
Saves only the first item number of each group, significantly reducing the
number of annotations on a complicated drawing.
1 ITEM
Generates and counts item numbers by inserting a text property (ITEMNUMB)

on the items sequentially in the direction of flow of the pipeline (from/to). The
prefix or suffix for the item number is specified with the ANNOTATE
ISOMETRIC ITEM command.
2 BOLT
Enables the user to select item numbers for bolts.
3 METHOD string
Counting method for bolts. Specify INTEGER or ALPHA only. Default is

INTEGER.
3 START string
The INTEGER or ALPHA to start the item number count with. Default is B1.
3 INCREMENT n
The increment of the count method. Default is 1.
3 OFF
Deactivates counting of bolts.
3 ON
Implicit default.
2 ON
Implicit default.

SAVE ANNOTATIONS
2 METHOD text
Counting methods for items. Specify INTEGER or ALPHA only. Default is

INTEGER.
2 START text
The INTEGER or ALPHA to start the count with. Default is 1.0.
2 INCREMENT text
The increments of the count method. Default is 1.0.
2 PIPE
Selects pipe to be included with ITEM number count.
3 ON
Implicit default.
3 OFF
Deactivates counting of pipe.
2 FITTING
Selects fittings to be included with ITEM number count.
3 ON
Implicit default.
3 OFF
Deactivates counting of fittings.
2 GASKET
Selects gaskets to be included with ITEM number count.
3 METHOD string
Counting method for gaskets. Specify INTEGER or ALPHA only. Default is

INTEGER.

SAVE ANNOTATIONS
3 START string
The INTEGER or ALPHA to start the item number count with. Default is G1.
3 INCREMENT n
The increment of the count method. Default is 1.
3 OFF
Deactivates counting of gaskets.
3 ON
Implicit default.
2 OFF
Deactivates counting of items.
1 LINENO
Identifies a single pipeline whose annotation information is to be saved. When

you use the LINENO modifier you do not select pipelines in getdata. (A
maximum of ten line numbers can be selected with one command, and each
line number must be separated by a comma).
1 NOTEXIST
Creates property types XYZ or LENGTH only for entities that do not have
them already; existing property types XYZ or LENGTH are not overwritten.
1 VISIBLE
Processes only visible entities.
1 WELD
Generates and counts weld numbers. Both shopwelds and fieldwelds are
counted and saved by generating a text property (WELDNUMB) on the
relevant Explicit Modeling entity. The welds are counted sequentially in the
direction of flow (from/to), for each separate pipeline. All welds are identified
by a endtype property value on the Cnode. This value, used to identify a Cnode
as a weld, can be user defined. The default is a W within the text string. Field

SAVE ANNOTATIONS
welds are further identified by having a fittype property of 70. The prefix or
suffix for the weld numbers is specified using the WELD modifier with the
ANNOTATE ISOMETRIC command.
2 ALL
(Default) Counts all shop and field welds in a sequential manner for each
individual pipeline.
3 METHOD text
Counting method for welds. Specify INTEGER or ALPHA only. Default is

INTEGER.
3 START text
The INTEGER or ALPHA to start the count with. Default is 1.0
3 INCREMENT text
The increment of the count method. Default is 1.0
2 SHOPWELD
Counts shop welds only, sequentially.
3 ON
Implicit default.
3 METHOD text
Counting method for shop welds. Specify INTEGER or ALPHA only.

Default is INTEGER.
3 START text
The integer or alpha to start the count with. Default is 1.0
3 INCREMENT text
3 OFF
Deactivates counting of shopwelds.

SAVE ANNOTATIONS
2 FIELDWELD
Counts field welds only, sequentially.
3 ON
Implicit default.
3 METHOD text
Counting method for field welds. Specify INTEGER or ALPHA only. Default
is INTEGER.
3 START text
The increment of the count that INTEGER or ALPHA start with. Default is 1.0
3 INCREMENT text
3 OFF
Deactivates counting of fieldwelds.
2 ENDTYPE text
Specifies the text value of the ENDTYPE property indicating welds. If any
character of the ENDTYPE property is a W, the text value has a limit of two
characters by default.

Description
Use this command to define a set of parameters used in creating a piping model.
This command is also used, with a different set of modifiers, in HVAC (Heating,
Ventilating, and Air Conditioning) design. For information about HVAC see the
Heating, Ventilating, and Air Conditioning Reference.
Valid Modes
Model mode
Syntax
#n# SELECT PPARAMETERS [modifiers]

Modifiers
The following diagram shows the flow of SELECT PPARAMETERS modifiers.


follows.
The first four modifiers apply to the SELECT PPARAMETERS command overall.
1 DRFILE filename
Specifies a file or directory which lists files that specify

End type compatibility
Single or multiple specification files for automatic selection of components
A parameter file for fittings that are to be parametrically inserted
The default is cvpd/directories.
1 MINBENDANG <real>
Specifies the bend angle limits. You can specify the bend angle limit within 0 to
180 degrees. An error message is displayed if the angle is specified beyond this
range.
Please note: This modifier is not available with the AUTOSELECT modifier.
1 LIST
Lists currently selected piping parameters. You can make changes and then use
LIST again to see the new parameters.
2 ALL
Lists piping and directory information.
2 IDNAME name
Used with the LIST modifier this allows you to list selected piping parameters
for any or all viewed parts. This lists the values and option selected for use in
the viewed part.
1 PAFILE
Specifies the default parameter file used for appearance/clearance procedures.

If your directory file specifies different parameter files for different layer
ranges, this default parameter file should contain the parameters for items on
layers other than specified in the DRFILE. The default is
cvpd/m/fit/parameters.

1 PIPING
Specifies that the following modifiers are specific to piping.
2 ABOVE
Associates the property ABOVE with the part. ABOVE generates double line
representation above the nominal pipe size during detailing. The size is a text
string in the same format as the size data in the autoselection file. It is used by
CREATE DETAIL with the modifier SINGLE.
For pipes at or below the specified size ABOVE, and the SINGLE modifier of
the CREATE DETAIL command, generate a single line representation when
detailed, and a double line representation if above the value. The default is zero
(0).
2 ALIGN
Aligns each new pipe segment with the previous segment, attached pipe, nozzle,
or fitting. The last segment is not aligned with any nozzle or pipe to which it is
attached.
2 BENDMAX n
Specifies the maximum number of bends allowed for spooling the pipeline. The
GENERATE SPOOL command uses this modifier along with the CHECK flag
for spooling the pipeline. The Default is 4. This modifier accepts any positive
integer value.
Please note: The pipeline is spooled using the BENDMAX modifier only if
the CHECK flag is active.
2 BOLT
Specifies type of bolt used. The type is reported with the command REPORT
PIPE. Two types are available:
BOLT - machine bolts
STUD - stud bolts (Default is STUD.)
2 BRADIUS x
(Bend radius) Specifies the radius of pipe bends in database units. The default is
0.0. This modifier is mutually exclusive with BRATIO.

2 BRATIO x
(Bend ratio) Specifies the ratio of the radius of pipe bends to the diameter of the
pipeline into which the pipe bends are inserted. The default is 5.0.
2 CHECK
(Default) Activates design rule checking. This checks the following:

Size consistency at the nozzles which is also checked by the command
ROUTE PIPE.
End type compatibility which is also checked by the command INSERT
FITTING.
Minimum spool length and tolerance which are also checked by the
commands INSERT FITTING, ROUTE PIPE, and GENERATE SPOOL.
Maximum spool length and maximum number of bends which are also
checked by the command GENERATE SPOOL for spooling.
2 ELBOW name
(Default) Used with LONG, SHORT, or BEND to specify the ratio of the bend
radius to the pipeline diameter. This ratio is used to check the elbow. LONG
equals a ratio of 1.5; SHORT equals a ratio of 1.0; BEND equals the BRATIO
or BRAD, whichever is not zero (0). Default is LONG.
2 EXPLICIT
Used in conjunction with the commands ROUTE PIPE and INSERT FITTING.
Explicitly specifies 3-D locations in getdata to identify specific Cnodes that
may appear coincident, or within epsilon, in a specific view.
2 FLANGE
(Default) Adds required flanges automatically when fittings are inserted.
2 FNAME name
(Flange name) Identifies the flange in the autoselection file for automatic
insertion. (Default name is FLAN.)
2 GASKET
(Default) Inserts the required gaskets automatically.

2 GNAME name
(Gasket name) Specifies the gasket in the autoselection file for automatic
insertion. Default name is GASK.
2 HOOK
(Default) Hooks fittings into existing pipelines or face to face with other
fittings.
2 LAYER n
Specifies the construction layer (0-254) for pipes and fittings. The default, -1,
has the following effect:
With HOOK, the component goes to the layer of the pipeline
With NOHOOK, the component goes to the active construction layer
2 LINKFORMAT text, limit =100
Specifies that the value declared here will be used by the command
GENERATE PIPEDBASE to process the automatic linking between the 2D
schematic pipeline network and the 3D model pipeline network. Default string
is FITTYPE. The values specified here must be valid property names, separated
by a comma in between them.
2 LOCK
Locks the pipeline along the three model axes (X,Y,Z) in the order specified. If
you use LOCK and ALIGN, alignment is performed before locking.
2 NOALIGN
(Default) Specifies no alignment.
2 NOCHECK
Does not activate design rules checking.
2 NOELBOW
Does not check for elbow room.

2 NOEXPLICIT
(Default) Specifies that the command ROUTE PIPE traps to (finds within the
specified tolerance) entities such as Cnodes and Nlines.
2 NOFLANGE
Does not automatically insert flanges; you must insert them.
2 NOGASKET
Gaskets are not automatically inserted; you must insert them.
2 NOHOOK
Inserts components at specified locations without hooking.
2 NOLOCK
(Default) Specifies no locking.
2 NOSELECT
Specifies that autoselection look-up is not done to insert fittings.
2 PROJECT name
Associates a project name with the active part and creates or changes the part
property PROJNAME. (Default is NONE.)
2 SELECT
(Default) Specifies automatic selection of fittings from the autoselection file.
2 SPOOL n
Specifies the minimum length (in database units) of spool used for design rules
checking. Default is 0.0

2 SPOOLMAX x
Specifies the maximum spool length in the current part units allowed for the
automatic spooling of the pipeline. The GENERATE SPOOL command uses
this modifier along with the CHECK flag for spooling the pipeline. This
modifier accepts any positive double value. The default value is the equivalent
of 6.0 meters in the current part units.
Please note: The pipeline is spooled using the SPOOLMAX modifier only if
the CHECK flag is active.
2 STFILE filename
Names the stock number file for automatic selection. The default is
cvpd/stru/stocknos/base.
2 STOCK
Specifies the automatic selection of components from the stock number file
named with STFILE.
2 TOLERANCE x
Specifies the maximum alignment deviation allowed when a component is

inserted. The tolerance value must be a positive real number. The default value for
a new part is an equivalent of 0.05 inch, in the part database units. The specified
tolerance value is used for collinear checking and hooking. The command
GENERATE SPOOL uses this value for generating or reconstructing the pipeline
spools.
2 TYPE name
Specifies the type of part/drawing created by associating the property
PARTTYPE with the part. Valid type names and their integer values are
ARRANGEMENT (0), P&ID (1), ISOMETRIC (2), and SPOOL (3). Entering
the first two characters of the name is sufficient.
Entering SELECT PPARAMETERS PIPING TYPE P&ID sets the following
modifiers automatically:
NOFLAN
NOGASK
NOELBOW
ALIGN
STOCK

NOCHECK
LOCK YX
STFILE CVPD.P.SELECTION
Entering SELECT PPARAMETERS PIPING TYPE not P&ID sets the following
modifiers automatically:
FLAN
GASK
NOALIGN
SELECT
CHECK
NOLOCK
ELBOW LONG
STFILE CVPD.STRU.STOCKNOS.BASE
Procedure
To setup pipeline parameters,
1. Enter the command SELECT PPARAMETERS.

2. Enter any modifiers you want, to specify the parameters of the pipeline you are
modeling.
3. Press RETURN.
Example 1
This example shows the use of the LIST modifier with default values.
#n# SELECT PPARAMETERS PIPING LIST
*** GENERAL PARAMETERS ***

PAFILE : CVPD.M.FIT.PARAMETERS
DRFILE : CVPD.DIRECTORIES
*** PIPING AND EQUIPMENT PARAMETERS ***
LAYER = 1
TOLERANCE = 0.05
MINIMUM SPOOL LENGTH = 0.0
MAXIMUM SPOOL LENGth = 236.220472
MAXIMUM NUMBER OF BENDS = 4
Flags : NOALIGN CHECK NOEXPLICIT
FLANGE GASKET HOOK SELECT

ELBOW CHECKING = LONG (RATIO = 1.5)

BEND RADIUS = 0.0
BEND RATIO = 5.0
LOCKING = OFF
INSPEC FLANGE= FLAN
INSPEC GASKET= GASK
BOLT = STUD
TYPE = ARRANGEMENT
ABOVE = 0
LINK FORMAT =
STFILE : CVPD.P.SELECTION
*** CURRENT DIRECTORIES FILE: CVPD.DIRECTORIES
MNEMONICNUMBERSIZESPECINS
INFO DIRY
LINENO-FORMAT MNEMONIC-NUMBER-INS
*
*PIPING PARAMETERS
*
* 1 2 3 4 5 6 *
*2345678901234567890123456789012345678901234567890123456789012
SPEC CVPD.M.SPEC/
ENDTYPES CVPD.M.SPEC.ENDTYPES
PFITTING USERS.PFITTING.FILE
PBENDINFO CVPD.M.SPEC.PBENDINFO
PMATINFO CVPD.M.SPEC.PMATINFO
*
CURRENT PIPING LAYERING CONVENTION
*
LAYER/1-29 CVPD.NOZL.PARAMETERS
LAYER/30-99 CVPD.STRU.PARAMETERS
LAYER/100-159 CVPD.M.FIT.PARAMETERS
*
*HVAC LAYERING CONVENTION:
*
*LAYER/160-200 CVAEC.HVAC.DATA.PARAMETERS
Example 2
This example shows the use of the SPOOLMAX and the BENDMAX modifiers.
#n# SELECT PPARAMETERS PIPING CHECK SPOOLMAX 3.25

BENDMAX 5 LIST

LAYER = -1
TOLERANCE = 0.05
MINIMUM SPOOL LENGTH = 0.0
MAXIMUM SPOOL LENGTH = 3.25
MAXIMUM BENDS IN SPOOL = 5
Flags : NOALIGN CHECK NOEXPLICIT
FLANGE GASKET HOOK SELECT
ELBOW CHECKING = LONG (RATIO = 1.5)
BEND RADIUS = 0.0
BEND RATIO = 5.0
LOCKING = OFF
INSPEC FLANGE= FLAN
INSPEC GASKET= GASK
BOLT = STUD
TYPE = ARRANGEMENT
PROJECT = NONE
ABOVE = 0
LINK FORMAT =
*** CURRENT DIRECTORIES FILE FOR PIPING: CVPD.DIRECTORIES

-MNEMONIC-NUMBER-SIZE-SPEC-INS
INFO DIRY
LINENO-FORMAT MNEMONIC-NUMBER-INS
*
* 1 2 3 4 5 6
*
*2345678901234567890123456789012345678901234567890123456789012
SPEC CVPD.M.SPEC/
ENDTYPES CVPD.M.SPEC.ENDTYPES
PFITTING USERS.PFITTING.FILE
PBENDINFO CVPD.M.SPEC.PBENDINFO
PMATINFO CVPD.M.SPEC.PMATINFO
*
*CURRENT PIPING LAYERING CONVENTION
*
LAYER/1-29 CVPD.NOZL.PARAMETERS
LAYER/30-99 CVPD.STRU.PARAMETERS
LAYER/100-159 CVPD.M.FIT.PARAMETERS
*
*HVAC LAYERING CONVENTION:
*
LAYER/160-200 CVAEC.HVAC.DATA.PARAMETERS
Example 3
This example shows the use of modifiers by changing some of the parameters of
Example 1 on page 5-6. INSPEC GASKET GSKT specifies the selection name
to use in looking up gaskets in your specification file. GSKT is changed from the
default name GASK using the GNAME modifier.

#n# SELECT PPARAMETERS DRFILE CVPD.NOZL.DRFILE PIPING LOCK

XYZ PROJECT TODAY SPOOL 2.6 ABOVE 4 TYPE P&ID BOLT GNAME
GSKT LIST
LAYER = 1
TOLERANCE = 0.05
MINIMUM SPOOL LENGTH= 2.6
MAXIMUM SPOOL LENGTH = 3.25
MAXIMUM BENDS IN SPOOL= 5
Flags : ALIGN NOCHECK NOEXPLICIT
NOFLANGE NOGASKET HOOK STOCK
ELBOW CHECKING = OFF (RATIO = 0.0)
BEND RADIUS = 0.0
BEND RATIO = 5.0
LOCKING = XYZ
INSPEC FLANGE= FLAN
INSPEC GASKET= GSKT
BOLT = BOLT
TYPE = P&ID
PROJECT = TODAY
ABOVE = 4
LINK FORMAT =
*** CURRENT DIRECTORIES FILE FOR PIPING: CVPD.NOZL.DRFILE

SIZESPEC
INFO DIRY
*
* POINTER TO NOZZLE SELECTION FILE
*
* 1 2 3 4 5 6 *
*2345678901234567890123456789012345678901234567890123456789012
*-------------------------------------------------------------
SPEC CVPD.NOZL.SELECT
The CVPD/Directories File

The command INSERT FITTING requires a directory to identify the files that are
used to select components for insertion, and check the end type compatibility.
These files are also used by REPORT PIPE and the LINK PROJECT commands
when you select the LOOKUP modifier. Also, bolting is checked in your
specification file.

The entries in the file cvpd/directories are described below:
The first line defines the format of pipeline labels. The first character is the
delimiter. You can vary the field labels, their order, and the delimiter. There is
one restriction: two of the field labels must be SIZE and SPEC.
The second line contains the headers for the two fields in the file: INFO and
DIRY.
The type of file is classified under INFO. The name of the file or catalog is
listed under DIRY. For example, ENDT, a type of file, is listed under INFO.
The name of the file cvpd/m/spec/endtypes is listed under DIRY.
With the single specification catalog, the command INSERT FITTING locates
the specification file by appending the specification code from the pipeline
label to the catalog name.
For example, the catalog name for specification files is cvpd/m/spec. The fact
that it is a catalog of single specification files and not a multi-specification file
is indicated by the slash (/) at the end of the catalog name. For spec B7A, the
file cvpd/m/spec/b7a would be used.
If you have multiple specifications in a single file, INSERT FITTING uses the
specification file named under DIRY. In this case, give the complete file name
(no slash included).
The lines beginning with LAYER/ set up a correspondence between a layer
range and a parameter file. When the detailing or clearance checking software
needs parameters for an entity, it looks to see if the entitys layer falls into one
of the specified layer ranges. If so, the corresponding parameter file is used.
If the entitys parameters cannot be found in that file, the default parameter file
(SELECT PPARAMETERS PAFILE) is used. This file is also used in the first
place if no layer-range-specific files are listed in the directory. The PAFILE
should contain items that reside on layers other than those specified in the
directory.
The parameter file for fittings (that is, cvpd/m/fit/parameters) combines
the various parameter files created by GENERATE PSFILE for different
specifications. The execute file cvpd/spec/var/merge combines them
automatically.
If you have a special file for parametric wire frame fittings, put PFIT under
INFO and the file name under DIRY.

Notes
The following general notes will help you further in using the SELECT
PPARAMETERS command.
1. The table below lists the maximum number of characters allowed for names
used with particular modifiers:
Table 5-1 Maximum Characters Allowed with Some Modifiers
Modifier Characters
ABOVE 12
DRFILE 40
FNAME 14
GNAME 14
PAFILE 40
PROJECT 40
STFILE 40
BOLT 6
2. Use SELECT PPARAMETERS to associate the part properties PARTTYPE,

ABOVE, and PROJAME with your part before you use a command that
references any of these properties.
3. The parameters you specify with SELECT PPARAMETERS are stored with the
part. This allows you to exit a part, reactivate it, and continue work on the part
without having to specify parameters such as the directory file name, etc.
4. The maximum number of parameter files that can be referenced in your
DRFILE is 12.

SPLIT PIPE
SPLIT PIPE
Description
Use this command to split a pipeline at a specified location (or multiple locations)
along the pipeline. A cnode is automatically created with the NOBREAK,
FITTYPE 70 (which stands for a field weld) and ENDTYPE BW properties
added. The first selection will identify the pipeline to be split and subsequent
selections will specify the split points.
After the pipelines are split, spool pieces can be created using the GENERATE
SPOOL command.
Valid Modes
Model mode
Syntax
#n# SPLIT PIPE: getdata
Modifiers
None
This example splits the selected pipeline at two locations.

#n# SPLIT PIPE: MODEL ent d Model loc d1 Model loc d2

TRANSLATE EQUIPMENT
TRANSLATE EQUIPMENT
Description
Use this command to translate equipment and/or pipelines and fittings from one
location to another. All the pipelines, fittings and other entities in the network are
properly translated together.
The equipment or pipe or fittings to be translated must be explicitly selected. The

translation vector can be defined by a modifier or by graphical selection.
Valid Modes
Model Mode
Syntax
#n# TRANSLATE EQUIPMENT [modifiers]: getdata

TRANSLATE EQUIPMENT
Modifiers
The following diagram shows the flow of TRANSLATE EQUIPMENT modifiers.
follows.

TRANSLATE EQUIPMENT
1 CHECK

1 DISTANCE x
Specifies the distance for translating the selected equipment in database units in
the specified direction.
1 DOWN
Translates the equipment in the current CPL -Z direction.
1 EAST
Translates the equipment in the current CPL +X direction.
1 NOCHECK
Indicates not to check for minimum spool length. This modifier is exclusive
with CHECK modifier.
1 NORTH
Translates the equipment in the current CPL +Y direction.
1 SOUTH
Translates the equipment in the current CPL -Y direction.
1 STOP select
Specifies that the translation of pipelines attached to the selected equipment
stops when a translation termination condition is met. This applies to pipe
segments preceding and succeeding the affected pipe segment. This modifier is
mutually exclusive with WLINE.
The translation termination conditions are is specified by one of the following
second level modifiers. The default is NORMAL.
2 NORMAL
(Default) Indicates that the translation termination condition is met at the first
occurrence of any pipe segment that is not perpendicular to the translation
vector.

TRANSLATE EQUIPMENT
2 PARALLEL
Indicates that the translation termination condition is met at the first occurrence
of any pipe segment that exactly parallel to the translation vector.
1 UP
Translates the equipment in the current CPL +Z direction.
1 VECTOR
Specifies the direction and distance for translating the selected equipment. If
the DISTANCE modifier is also selected, then the translation is done by the
specified distance along the specified vector direction.
1 WEST
Translates the equipment in the current CPL -X direction.
1 WLINE
Translates the entire pipeline attached to the selected equipment. This modifier
is mutually exclusive with STOP.
Procedure
To translate equipment,
1. Enter TRANSLATE EQUIPMENT.

3. Enter a colon. The system prompts Model ent.
4. Select the equipment to be translated.
5. Press RETURN.

TRANSLATE EQUIPMENT
Example 1
This example illustrates translation of equipment along a specified vector.
#n# TRANSLATE EQUIPMENT VECTOR: Model ent d1; Model loc d2 IY-5

TRANSLATE EQUIPMENT
Example 2
This example illustrates translation of equipment towards east (+X direction) by a
specified distance.
#n# TRANSLATE EQUIPMENT EAST DISTANCE 2: Model ent d1
(tracing pipeline)

TRANSLATE EQUIPMENT

TRANSLATE EQUIPMENT
Example 3
This example illustrates translation of equipment in the DOWN (+X) direction by
a specified distance along with the entire attached pipelines.
#n# TRANSLATE EQUIPMENT DOWN DISTANCE 10 WLINE: Model ent d1
(tracing pipeline)

TRANSLATE ISOMETRIC
TRANSLATE ISOMETRIC
Description
Use this command to revise the true dimensions and locations of items (Cnodes
and Nfigures) on a piping isometric drawing without altering the drawing graphics.
Dimension text is automatically updated.
Only the XYZ properties of the items you select are adjusted. You can also add
XYZ properties, recording true model locations, onto items inserted after the
isometric is generated.
For example, you can use this command to revise an old isometric and to produce a
new bill of materials, despite the fact that the drawing is out of scale.
TRANSLATE ISOMETRIC saves you from having to redraw the isometric.
Valid Modes
Model mode
Syntax
#n# TRANSLATE ISOMETRIC AXIS X, or Y, or Z: getdata
#n# TRANSLATE ISOMETRIC VECTOR x [modifiers]: getdata
Please note: All coordinates must come from the XYZ properties on Cnode
and Nfigure entities. Therefore, you are only allowed to select MODEL ents
(Cnodes and Nfigures) and not MODEL locs, as TRANSLATE ENTITY allows.
The command always involves two independent processes:
Defining a translation
Applying the translation
You can use different modifiers to define the translation, but there is only one way
to apply the translation. Note that an entity used to define the translation does not
itself have to be translated.

TRANSLATE ISOMETRIC
Modifiers
The following diagram shows the flow of TRANSLATE ISOMETRIC modifiers.
follows.
1 AXIS
Uses the distances along axes specified by X, Y, and Z submodifiers to

determine a translation.
2 X x, Y y, Z z
Defines positive or negative distances along x-, y-, and z-axes. There is no
change along the axes which are not specified.

TRANSLATE ISOMETRIC
2 DISPLACE
Displaces items by the specified distances along the x-, y-, and z-axes.
Please note: You cannot use DISPLACE to add XYZ properties to an entity
inserted onto a generated isometric.
2 POSITION
Defines a translation that will move an entity to the coordinate specified by the
X, Y, and Z submodifiers.
Use this when you know the position you want something moved to. If you
want to add XYZ properties to an entity inserted onto a generated isometric,
enter all three submodifiers: X, Y, and Z.
2 REFERENCE
Defines a translation that will move an entity to a location defined by the

distances along the x-, y-, and z-axes, from a reference entity.
Use this to move something to a position that is a known offset from an existing
item. If you want to add XYZ properties to an entity inserted onto a generated
isometric, the reference entity must have the XYZ property.
1 SHOW
Displays the translation vector. SHOW prints the translation vector before you
apply it to any entities.
1 VECTOR x
Uses the direction and distance you indicate to determine a translation. Specify
direction in getdata by selecting two entities (Cnodes or Nfigures) that have
XYZ properties.
2 DISPLACE
(Default) Displaces items x units in the given direction.
2 REFERENCE
Determines a translation that will move a given entity to a destination x units

away from another given entity in a given direction.

TRANSLATE ISOMETRIC
Procedure 1
To translate items along an axis,
1. Enter TRANSLATE ISOMETRIC with the modifier AXIS.

2. Specify one of the following modifiers:
DISPLACE moves your item along an axis x distance.
POSITION moves your item to coordinates (X, Y, Z).
REFERENCE moves your item a given distance along the specified axes.
3. Enter X, Y, and/or Z, either as a distance or as a set of coordinates.
4. The system prompts according to the submodifier you entered. If you specified
DISPLACE, the system prompts translate MODEL ent. Select the
item(s) to move.
POSITION, the system prompts position MODEL ent. Select the item
to be moved to the coordinates specified by the X, Y, and Z modifiers. The
system prompts translate MODEL ent. Select your item and any other
entities to be moved along with it.
REFERENCE, the system prompts reference from MODEL ent;
select the first reference point.
The system prompts to MODEL ent; select the other reference point. The
system prompts translate MODEL ent; select the entities you want to
move.
The final prompt is always translate MODEL ent.
5. Press RETURN.
Procedure 2
To translate items along a vector,
1. Enter TRANSLATE ISOMETRIC with the modifier VECTOR.

2. Specify the distance x to be used.
3. Specify one of the following modifiers:
DISPLACE moves your item along the vector x distance.
REFERENCE defines a translation that moves the second reference point to
a position x distance away from the first reference point along the specified
direction.

TRANSLATE ISOMETRIC
4. The system prompts according to the last modifier you entered. If you specified
Both DISPLACE and REFERENCE, the system prompts vector from
MODEL ent; select the first point. The system prompts to MODEL ent;
select the second point. The direction is from the first to the second point.
DISPLACE, the system prompts translate MODEL ent; select the
entities you want to move.
REFERENCE, the system prompts reference from MODEL ent;
select the first reference point.
The system prompts to MODEL ent; select the second reference point.
The system prompts translate MODEL ent; select the entities you
want to move.
The final prompt is always translate MODEL ent.
5. Press RETURN.
Example 1
Increase the length of a pipe going in the x direction by two inches. Digitize the
Cnode at the right end of the pipe.
#n# TRANSLATE ISOMETRIC AXIS DISPLACE X 2: translate MODEL ent
d1

TRANSLATE ISOMETRIC
Example 2
Move entity B to a position five units above entity A. Digitize (d1) entity A as the
base entity. Digitize (d2) entity B as the entity to be moved.
#n# TRANSLATE ISOMETRIC AXIS REFERENCE Z 5:reference from MODEL

ent d1 to MODEL ent d2 translate MODEL entd2 (d3...dn)
Example 3
Lengthen a pipe, going in an unspecified direction, by five inches. Digitize (d1)
the first Cnode as the end that is stable. Digitize (d2) the second Cnode as the end
to be lengthened in a vector direction away from the first Cnode.
#n# TRANSLATE ISOMETRIC VECTOR 5 DISPLACE:vector from MODEL ent
d1 to MODEL ent d2 translate MODEL ent d2

TRANSLATE ISOMETRIC
Example 4
Position an entity five inches from another entity. It should be placed in such a way
that its direction parallels with that of another pair of entity.
1. Select the two entities that establish the direction (d1, d2.) The order of selection
establishes the direction of the vector.
2. Select the base entity (d3); select the entity to be positioned (d4.)
3. Press RETURN.
Example 5
This example creates a series of translations within the same isometric drawing.
STEP 1: Move a Cnode 10 units along the y-axis

#n# LIST PROPERTY: MODEL ent: d1
PROPERTIES ATTACHED TO ENTITY ARE
XYZ 0.000
0.000
0.000
(XYZ properties are listed before the translation for illustrative purposes only.)
#n# TRANSLATE ISOMETRIC AXIS DISPLACE Y 10 SHOW:
The TRANSLATION VECTOR IS 0.000 10.000 0.000
translate MODEL ent: d1
1 ENTS WERE SUCCESSFULLY TRANSLATED
#n# LIST PROPERTY: MODEL ent d
XYZ X 0.000
Y 10.000
Z 0.000

TRANSLATE ISOMETRIC
(The XYZ property is listed after translation for illustration only. Note the
changed dimension in the illustration.)
STEP 2: Stretch the pipe along the y-axis

#n# TRANSLATE ISOMETRIC AXIS REFERENCE Y +50 SHOW: reference
from MODEL ent d1 to MODEL ent d2
THE TRANSLATION VECTOR IS 0.000 40.000 0.000
translate MODEL ent d2

TRANSLATE ISOMETRIC
STEP 3: Stretch the pipe, although its orientation is unknown

#n# TRANSLATE ISOMETRIC VECTOR 100 REFERENCE SHOW: vector from
MODEL ent d1 to MODEL ent d2
reference from MODEL ent d 3 to MODEL ent d4
THE TRANSLATE VECTOR IS 0000 50.00 0.000
translate MODEL ent d5

TRANSLATE ISOMETRIC
STEP 4: Assign XYZ properties with POSITION

#n# INSERT NFIGURE CVPD.F.ERED: MODEL loc d1
#n# TRANSLATE ISOMETRIC POSITION X 1 Y 2 Z 3 SHOW: position MODEL
ent d1 SELECTED ENT DOES NOT HAVE XYZ-PROPERTY
THE TRANSLATION VECTOR IS -205.779 -375.374 3.00 translate
MODEL ent WIN DRAW loc d 2d3d4
(For purposes of illustration, the fourth selection identifies an item that already has
the XYZ property.)
The 3 ENTS WERE SUCCESSFULLY TRANSLATED
1 ENTS WERE IGNORED BECAUSE OF (MISSING) XYZ PROP
The XYZ property was assigned to the first three entities but not to the fourth; this
ignored item is highlighted and marked.
#n# LIST PROPERTY: MODEL ent d1
LIST PROPERTY shows that TRANSLATE ISOMETRIC has assigned the XYZ
property with the specified value. (For illustrative purposes, only the XYZ
property listing is shown here.)

TRANSLATE ISOMETRIC

XYZ 1.000
2.000
3.000
STEP 5: Assign XYZ properties with VECTOR REFERENCE

#n# INSERT FITTING CHKV: MODEL ent d1
#n# TRANSLATE ISOMETRIC VECTOR 25 REFERENCE: vector from MODEL
ent d2 to MODEL ent NFIG d1
reference from MODEL ent d 3 to MODEL ent NFIG d4 SELECTED
ENT DOES NOT HAVE XYZ
translate MODEL ent WINDOW DRAW loc d 5d6

TRANSLATE ISOMETRIC
Note the warning message indicating that the entity does not have the XYZ
property.
XYZ 25.000
100.000
0.000
STEP 6: Translate an item with AXIS REFERENCE

#n# TRANSLATE ISOMETRIC AXIS X 0 Y 0 Z 30 REFERENCE SHOW:
reference from MODEL ent d1 to MODEL ent d2
The TRANSLATION VECTOR IS 1.00 98.000 27.000
translate MODEL ent WIN DRAW loc d 3d4
XYZ 0.000
100.000
30.000

TRANSLATE ISOMETRIC
Please note: TRANSLATE ISOMETRIC uses the standard getdata

punctuation.
In addition, TRANSLATE ISOMETRIC uses the semicolon in a nonstandard way.
The semicolon (;) is used to execute the current command and come back to
getdata just as if the same verb, noun, and modifiers were entered, the same
translation vector calculated, and the user is ready to select entities for the
translation.

VERIFY DISTANCE
VERIFY DISTANCE
Description
Use this command to verify the distance between the visible edges of two AEC
objects or between a visible edge of a selected AEC objects and other entities, in a
given view.
This command is valid for all objects supported by the command CREATE
DETAIL.
You must explicitly identify the two objects between which the distance is to be
measured. If the identified objects are AEC objects then the command creates
temporary detail graphics for them in the selected view. Once the temporary detail
graphics are generated, you are required to select two objects between which the
distance is to be measured.
After the command is terminated, the temporary detailed graphics are deleted.
Valid Modes
Model Mode
Syntax
#n# VERIFY DISTANCE [modifiers]: Model ent getdata
Modifiers
The following diagram shows the flow of VERIFY DISTANCE modifiers. An
see the Preface.

VERIFY DISTANCE
follows.
1 HORIZONTAL
Reports the horizontal distance between the identified points.
1 VERTICAL
Reports the vertical distance between the identified points.
1 PPOINT
(Default) Reports the point to point distance between the identified points.
Procedure
To verify the distance between two entities,
1. Enter VERIFY DISTANCE.

3. Enter a colon. The system prompts Model ent.
4. Select the entities to measure the distance between them.
5. Enter a semicolon. If the selected entities are AEC objects then detailed
graphics are generated for the selected objects. The system prompts Model
loc.
6. Select two points between which the distance is to be measured.
7. The distance between the selected points is displayed. The system again
prompts Model loc.
8. If you want to verify another distance, select two more points.
9. After all the required distances are verified, press RETURN.
Example 1
This example illustrates the verification of horizontal distance between the selected
objects.
#n# VERIFY DISTANCE HORIZONTAL: MODEL ent d1 d2;
MODEL loc NEAR d3 d4
Horizontal Distance = 7.6665
MODEL loc

VERIFY DISTANCE

VERIFY DISTANCE
Example 2
This example illustrates the verification of vertical distance between the selected
objects.
#n#VERIFY DISTANCE VERTICAL : MODEL ent d1 d2 ;
Vertical Distance = 9.665208
MODEL loc

VERIFY DISTANCE
Example 3
This example illustrates the verification of point to point distance between the
selected objects.
#n#VERIFY DISTANCE PPOINT : MODEL ent d1 d2 ;
Point to Point Distance = 11.867122
Point to Point Distance = 29.067857
MODEL loc

Appendix A Piping Files
This appendix lists files used with piping commands. A description of the features
of the directory or file is given in the left column of the table. The name of the
directory or file follows, in the right column.
Modeling, Detailing, and Reporting Files
Piping Reference A-1

Piping Files
Table A-1 Modeling, Detailing, and Reporting Files
Features Directory and File Names
Plant Design directory cvpd
Directory for pipe specification files cvpd/_bcd/directories
Parameters for items on layers other than those cvpd/_bcd/parameters

specified by _bcd/directories
Convert feet and inches into decimal format. These cvpd/dmenu/ftin16/_bcd/input

files are activated by entering the Explicit Modeling cvpd/dmenu/ftin16/dir
command
cvpd/dmenu/ftin16/doc
#n# ACTIVATE DMENU CVPD.DMENU.FTIN16
cvpd/dmenu/ftin16/exec
Fitting files, referenced by CVPD, that include cvpd/f

procedure, Nfigure, and part files
Modeling and miscellaneous files cvpd/m
Parameters for fittings compatible with the cvpd/f/fit/_bcd/parameters

cvpd/m/spec file. The layer range for these fittings is
100-159.
Plant Design course directory cvpdc
Directory for pipe specification files cvpdc/_bcd/drfile
Directory of fitting end types cvpdc/endtypes
Specification or auto selection files used to build the cvpdc/endtypes/asfile/_bcd/a2a

H&G model. The files were created using the cvpdc/endtypes/asfile/a2a/_bcd/assembly
GENERATE PSFILE command.
cvpdc/endtypes/a2f
cvpdc/endtypes/a3a
cvpdc/endtypes/b2a
cvpdc/endtypes/b2f
cvpdc/endtypes/d2b
Fittings parameter file. The directory cvpdc/drfile cvpdc/fit/pafile

assigned layers 100-159 to this file
A-2 Piping Reference

Piping Files
Table A-1 Modeling, Detailing, and Reporting Files
Features Directory and File Names
Formpart for isometric drawings cvpdc/form/isoc/_nfig

cvpdc/form/isoc/_pd
Declaration/Classification section of INFILE showing cvpdc/infile/_bcd/example

all the components in the ANSI master catalog
Input files to generate specs A2A-D2B cvpdc/genpsf/infile/_bcd/a2a

cvpdc/genpsf/infile/_bcd/a2f
cvpdc/genpsf/infile/_bcd/a3a
cvpdc/genpsf/infile/_bcd/b2a
cvpdc/genpsf/infile/_bcd/b2f
cvpdc/genpsf/infile/_bcd/d2b
INFILE that is the source of other INFILES cvpdc/genpsf/infile/_bcd/long
H & G model directory model
Part and drawing directory before modeling cvpdc/model/phase0/_pd

cvpdc/model/phase0/a
After piping is added cvpdc/model/phase3/_pd

After detailing is done cvpdc/model/phase4/_pd

Structural steel framing plans, and equipment cvdpc/model/plotplan/_pd

location plans for the cvdpc model cvdpc/model/plotplan/a
Execute files cvpdc/x
Master execute file to run files 0 - n cvpdc/x/_bcd/0-n
Layout drawing file cvpdc/x/_bcd/0
Pipeline routing file cvpdc/x/_bcd/3
File to create a dimensioned isometric drawing cvpdc/x/_bcd/4
Material description in-file cvpd/iso/mdfinfile-mm
Matrix file cvpd/iso/table-mm
Piping Reference A-3

Appendix B Piping RDBMS Tables
This Appendix describes the various RDBMS related information. This includes
the detailed steps for setting up the RDBMS Environment Variables, Linking
CADDS Parts to a Project for the execution of RDBMS related commands,
description of the Project Information RDBMS tables that are accessed by AEC
commands, and details of the table names and field structure for the Standard
Library RDBMS tables pertaining to Piping application.
The various sections providing the above information are
RDBMS Environment Variables Setup

Linking CADDS Parts to a Project
Piping Standard Library RDBMS Tables
Pipeline RDBMS Tables
Generating Project Information and Piping Tables
Piping Reference B-1

Piping RDBMS Tables

To invoke the GENERATE PIPEDBASE and DRAW PSPOOL commands,
various environment variables must be set. These variables define the various
system parameters required to establish a connection between CADDS and the
external RDBMS software and are set prior to invoking the above RDBMS related
commands.
The environment variables that must be set in the various resource files is
discussed below. The following discussion presents the resource file names,
environment variable names and sample representative values for the RDBMS
related environment variables. The appropriate values for a particular User
environment should be determined by the System Administrator User.
~/.cshrc file:
# ORAKITPATH is used by SQL*Forms30, SQL*Menu50, and
# Oracle*Terminal.
setenv ORAKITPATH.
# ORATERMPATH is used by Oracle*Terminal.
setenv ORATERMPATH.
setenv ORACLE_SERVER
~/.login file:
setenv ORACLE_HOME '/usr2/oracle'
setenv ORACLE_HOST ' machine_name'
setenv ORACLE_SID sin
setenv ORACLE_TERM sun5
set path=($path $ORACLE_HOME/bin)
if (`hostname`!= "$ORACLE_HOST") then
setenv TWO_TASK "t:${ORACLE_HOST}:${ORACLE_SID}"
else
unsetenv TWO_TASK
endif
~/.caddsrc-local file:
setenv DBMS_HOST $ORACLE_HOST
setenv DBMS 300007
setenv DBMS_ARRAY_SIZE 100
B-2 Piping Reference

Piping RDBMS Tables

In order to execute the following RDBMS related pipeline spool commands,
GENERATE PIPEDBASE
DRAW PSPOOL
Every CADDS part that stores piping model data for a particular project requires
linking to the specific project. This link is established using the appropriate EDM
Information commands and is done prior to executing the RDBMS related
commands.
The steps to perform linking of CADDS parts to a specific project, using EDM
Information commands are as follows,
1. Invoke CADDS in the explicit mode.

2. ACTIVATE PART <CADDS part name>
3. SELECT ADBMS USER <user_name> PASSWORD <password> PROJECT
<project_name> <CR>
4. LINK ADBMS <CR>
The above sequence of commands creates an entry in the external RDBMS table,
CV_PART_TBL and registers the active CADDS part name against the specified
project name. Using this link, the application specific RDBMS related commands
automatically identify the project name for a currently active part from which the
commands are invoked.
The project name thus determined by these commands and the values input using
the ASSEMBLY, SUBASSEMBLY and TYPE modifiers of these respective
commands is used in conjunction with the data in the hierarchical Project
Component structure and table names specified in the
AEC_PROJECT_DICTIONARY_TBL, to select the appropriate external RDBMS
table names for manipulation.
The details of the external RDBMS table name determination by the above
RDBMS related commands, are explained later in this appendix.
For additional details, see the EDM Information Administrators Guide.

Piping RDBMS Tables

The Project Information Tables, is a set of RDBMS tables that is common to all
AEC application commands that employ the external RDBMS link. These tables,
together offer a hierarchical data organization scheme for several projects that may
be concurrently handled in a given User environment. This section explains the
various RDBMS tables that make up the set of project information tables.
In order for the RDBMS related commands to execute properly, the database
administrator must plan and define their database architecture based on the
requirements of various applications, and create/setup their relational database
tables in advance.
A set of SQL script files are supplied with this package to create the basic field
structure and to fill records for these tables. These script files are available under
the directory,
/usr/apl/cadds/data/cvaec/dbms/scripts/
The details for running the individual script files is explained together with the
appropriate table descriptions below.
The details for running an alternate single top level script is explained in the
section, Generating Project Information and Piping Tables. This script file when
invoked runs all the related individual script files and establishes a set of RDBMS
tables for executing the Piping RDBMS commands.
AEC Project Dictionary Table

This table is a project dictionary that specifies the RDBMS tables names used by
various projects to organize the data pertaining to multiple projects. In this table,
the RDBMS table names pertaining to various projects is stored against the project
name and a table type that represents the overall type of project data that is stored
in the individual tables.
This table determines the name of the RDBMS tables used for a given project.
Based on the project name and table type, the name of the RDBMS table is
extracted from this table.
The name of this table, AEC_PROJECT_DICTIONARY_TBL, is hard coded in

the software.

Piping RDBMS Tables
The field structure of the this table is as follows,

Table B-1 AEC Project Dictionary Table - AEC_PROJECT_DICTIONARY_TBL
Data Field Name Data Type Description

AEC_PROJ_PROJID NOT NULL VARCHAR(8) Project name
AEC_PROJ_TABLETYPE NOT NULL VARCHAR(20) Table type
AEC_PROJ_TABLENAME NOT NULL VARCHAR(40) Database table name
The AEC_PROJ_PROJID field stores the project name. The software correlates
this project name with the corresponding project name stored in the
PART_PROJID field of the CV_PART_TBL table, created by the procedure that
links CADDS parts to a project. Refer Linking CADDS Parts to a Project for
details of the linking procedure.
The AEC_PROJ_TABLETYPE field stores the table type of the RDBMS table
specified in the AEC_PROJ_TABLENAME field.
The table types used by the Piping RDBMS commands are as follows,
APPLICATION - Application Object Dictionary Table.

COMPONENT - Project Component Table. (hierarchical tree structure)
TYPE - Object Type Table.
OBJECT - Object Table.
The above table type values, i.e. APPLICATION, COMPONENT, TYPE, and
OBJECT are hard coded in the software.
The AEC_PROJ_TABLENAME field stores the RDBMS table name. The actual
field structure of the table represented by this table name, depends on the table
type stored in the AEC_PROJ_TABLETYPE field. The details of the field
structure for the above table types is discussed in the subsequent sections in this
appendix.
The creation/insertion of records in this AEC_PROJECT_DICTIONARY_TBL is

an RDBMS administration task and should be handled only by an RDBMS
administrator. The actual creation/insertion of records can be performed using the
appropriate RDBMS software commands outside CADDS, or by executing the
script files supplied with this package.
For the application users using the GENERATE PIPEDBASE and DRAW
PSPOOL commands, this project dictionary table is available only in the read-only
mode.

Piping RDBMS Tables
A typical project dictionary table is as follows,

Table B-2 Sample AEC_PROJECT_DICTIONARY_TBL
AEC_PROJ_PROJID AEC_PROJ_TABLETYPE AEC_PROJ_TBLNAME

PROJECT1 COMPONENT AEC_COMPONENT_TBL
PROJECT1 APPLICATION AEC_APPLICATION_TBL
PROJECT1 TYPE AEC_OBJECT_TYPE_TBL
PROJECT1 OBJECT AEC_OBJECT_TBL
PROJECT1 UNIT AEC_UNAME_DICTIONARY_TBL
PROJECT1 CONVERSION AEC_UNIT_CONVERSION_TBL
PROJECT1 UNAME AEC_PUNIT_DICTIONARY__TBL
PROJECT1 RELATION AEC_RELATION_TBL
PROJECT1 LINK AEC_LINK_TBL
PROJECT2 COMPONENT AEC_COMPONENT_TBL
PROJECT2 APPLICATION AEC_APPLICATION_TBL
PROJECT2 TYPE AEC_OBJECT_TYPE_TBL
PROJECT2 OBJECT AEC_OBJECT_TBL
PROJECT2 UNIT AEC_UNIT_DICTIONARY_TBL
PROJECT2 CONVERSION AEC_UNIT_CONVERSION_TBL
PROJECT2 UNAME AEC_UNAME_DICTIONARY_TBL
PROJECT2 RELATION AEC_RELATION_TBL
PROJECT2 LINK AEC_LINK_TBL
Script Files
Directory location: /usr/apl/cadds/data/cvaec/dbms/scripts/
create_project_dictionary_table.sh can be used to create basic field structure for the project
dictionary table.
fill_project_dictionary_table.sh: can be used to fill in a row of data into the project dictionary
table.
grant_user_tables.sh: can be used to grant permission to a piping user for
accessing the project dictionary table.
Syntax
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_project_dictionary
_table.sh -l <dba_admn_user_name> -p <dba_admn_password>
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_project_dictionary_t
able.sh -l <dba_admn_user_name> -p <dba_admn_password> -P
<project_name> -t <aec_table_type> -T <aec_table_name>

Piping RDBMS Tables
%/usr/apl/cadds/data/cvaec/dbms/scripts/grant_user_tables.sh -l
<dba_admn_user_name> -p <dba_admn_password> -L <pipe_user_name> -P
<pipe_password> -t <aec_proj_table_type> -T <aec_proj_table_name>
Example
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_project_dictionary
_table.sh -l admn_user -p admn_pass
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_project_dictionary_t
able.sh -l admn_user -p admn_pass -P DEMO -t COMPONENT -T
AEC_COMPONENT_TBL
This example illustrates the insertion of the first row of data in the sample table
shown above. Subsequent rows for TYPE, APPLICATION and OBJECT can be
inserted similarly, using the above script file.
% /usr/apl/cadds/data/cvaec/dbms/scripts/grant_user_tables.sh -l
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PROJECT -T
AEC_PROJECT_DICTIONARY_TBL
AEC Project Component Table

This table defines the hierarchical logical structure of project components. Each
record in this table defines a project component like ship, stage, block or panel, and
the identification of its parent component. Through a logical parent child
relationship of the various project components, a tree structure of the project
components can be established using this table.
The name of this table is as specified in the

AEC_PROJECT_DICTIONARY_TBL, for a given project as described above.
The field structure of the this table is as follows,

Table B-3 AEC Project Component Table - AEC_COMPONENT_TBL

AEC_COMP_COMPNAME NOT NULL VARCHAR(40) Project component name
AEC_COMP_PROJID NOT NULL VARCHAR(8) Project name
AEC_COMP_COMPID NOT NULL NUMBER Component unique identifier
AEC_COMP_COMPTYPE NOT NULL VARCHAR(20) Component type
AEC_COMP_PARENTID NUMBER Parent component identifier
AEC_COMP_PARTID NUMBER Related part identifier

Piping RDBMS Tables
The AEC_COMP_COMPNAME field stores the logical name of a project

structure component instance. Value for this field is specified by the User, using
the SUBASSEMBLY sub-modifier of the GENERATE PIPEDBASE command.
The AEC_COMP_PROJID field stores the name of the project that the component
belongs. This field is associated with the PART_PROJID field of CV_PART_TBL,
created by procedure that CADSS part to a project, as described in Linking
CADDS Parts to a Project .
The AEC_COMP_COMPID field stores the unique identifier number of the

project component. The identifier is generated using the RDBMS sequence
facility.
The AEC_COMP_COMPTYPE field stores the user defined type of the project
component. In the shipbuilding terminology, this can be SHIP, STAGE, BLOCK,
PANEL,...etc. The value for this field is specified by the User using the TYPE
sub-modifier of the GENERATE PIPEDBASE commands.
The AEC_COMP_PARENTID field stores the unique identifier of the component

instances parent as defined in the project hierarchical structure. This field is
associated with the AEC_COMP_COMPID field in the same table.
The AEC_COMP_PARTID field stores the part identifier of the CADDS part
associated to the project component, where appropriate. The part identifier is
associated with the PART_PARTID field in the CV_PART_TBL Table, created by
linking the part to a project, as described in Linking CADDS Parts to a Project
Table B-4 Sample AEC_COMPONENT_TBL
AEC_COM AEC_COM
AEC_COMP_ AEC_COMP P_COMPI AEC_COMP_ P_PAREN AEC_COMP
COMPNAME _PROJID D COMPTYPE TID _PARTID
CV DEMO 1 NULL NULL NULL
T-58 DEMO 2 SHIP 1 NULL
STAGE-01 DEMO 3 STAGE 2 NULL
STAGE-02 DEMO 4 STAGE 2 NULL
T-59 DEMO 5 SHIP 1 NULL
BLOCK1 DEMO 6 BLOCK 5 NULL
BLOCK2 DEMO 7 BLOCK 5 NULL

Piping RDBMS Tables
Script Files
create_component_table.sh can be used to create basic field structure for the project
component table.
fill_component_table.sh can be used to fill in a row of data into the project component
table.
grant_user_tables.sh can be used to grant permission to a piping user for accessing
the project component table.
Syntax
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_component_table.sh
-l <dba_admn_user_name> -p <dba_admn_password> -t <table_name>
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_component_table.sh -l
<dba_admn_user_name> -p <dba_admn_password> -t <table_name> -P
<project_name> -T <parent> -C <new_component>
<pipe_password> -t <table_type> -T <table_name>
Example
% /usr/apl/cadds/data/cvaec/dbms/scripts/create_component_table.sh
-l admn_user -p admn_pass -t AEC_COMPONENT_TBL
% /usr/apl/cadds/data/cvaec/dbms/scripts/fill_component_table.sh
-l admn_user -p admn_pass -t AEC_COMPONENT_TBL -P DEMO -T ROOT -C
CV
shown above. Subsequent rows can be created using the GENERATE
PIPEDBASE command or by using this script.
admn_user -p admn_pass -L pipe_user -P pipe_pass -t COMPONENT -T
AEC_COMPONENT_TBL
AEC Application Object Type Table

This table defines the application object types that are used to specify application
tables names in the AEC_APPLICATION_TBL. The application table names
specified using these object types are identified and used by the appropriate AEC
RDBMS application commands to store and manipulate extracted data from the

Piping RDBMS Tables
model. The name of this object type table itself, should be specified in the
AEC_PROJECT_DICTIONARY_TBL table as described above.
This tables stores a unique identification number for each of the different types of
application objects.
The records in this table should be inserted by the database administrator outside
CADDS, using the set of script files supplied with this package. This table is
available in the read-only mode for the GENERATE PIPEDBASE command.
Table B-5 AEC Application Object Type Table - AEC_OBJECT_TYPE_TBL

AEC_OBJECT_TYPENAME NOT NULL VARCHAR(20) Object type name
AEC_OBJECT_TYPEID NOT NULL NUMBER Object type unique
identification number
The AEC_OBJECT_TYPENAME field stores the object type names for different
types of application objects. These object type names are hard coded in the
software for the individual AEC applications. The hard coded object types for
Piping application are as follows:
Piping Application Object Types:
PIPING_COORD - Piping coordinate table.

PIPING_DRAW - Piping drawing information table
PIPE_LINE - Pipeline information table
PIPE_SPEC - Pipe specification table.
PIPE_MAT - Pipe fabrication material table.
PIPE_LIST - Pipeline list table.
PIPE_ELEMENT - Pipeline spool element table.
PIPE_BEND - Pipeline bend table.
PIPE_ITEM - Pipeline item number information table.
PIPE_ENDTYPE - Pipe end type table.
The AEC_OBJECT_TYPEID field stores the unique identification number for

each of the application object types. This field corresponds to the
AEC_APPL_OBJTYPE field of AEC_APPLICATION_DICTIONARY_TBL
discussed in the following section. This unique identification number can be
modified by the user if required, for each of the application object types.

Piping RDBMS Tables
A typical application object type table is as follows

Table B-6 Sample AEC_OBJECT_TYPE_TBL
AEC_OBJECT_TYPENAME AEC_OBJECT_TYPEID
PIPING_COORD 101
PIPING_DRAW 102
PIPE_LINE 103
PIPE_SPEC 104
PIPE_MAT 105
PIPE_LIST 51
PIPE_ELEMENT 52
PIPE_BEND 55
PIPE_ITEM 56
PIPE_ENDTYPE 57
Script Files
create_object_type_table.sh can be used to create basic field structure for the application
object type table.
fill_object_type_table.sh can be used to fill in a row of data into the application object
type table.
application object type table.
Syntax
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_object_type_table.
sh -l <dba_admn_user_name> -p <dba_admn_password> -t <table_name>
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_object_type_table.sh
-l <dba_admn_user_name> -p <dba_admn_password> -t <table_name> -O
<table_type> -N <table_type_id>

Piping RDBMS Tables
Example
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_object_type_table.
sh -l admn_user -p admn_pass -t AEC_OBJECT_TYPE_TBL
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_object_type_table.sh
-l admn_user -p admn_pass -t AEC_OBJECT_TYPE_TBL -O PIPING_COORD
-N 101
shown above. Subsequent rows can be inserted similarly, using the above script
file.
admn_user -p admn_pass -L pipe_user -P pipe_pass -t TYPE -T
AEC_OBJECT_TYPE_TBL
AEC Application Object Dictionary Table

This table defines the RDBMS table names that are used by AEC applications to
store the attributes of the various AEC application objects. The name of this
application object dictionary table itself, should be specified in the
AEC_PROJECT_DICTIONARY_TBL table as described above. Using the
project name, the project structure component name and the type of an application
object. the software determines, the application object attribute table name from
this AEC Application Object Dictionary Table.
The records in this table should be inserted by the database administrator outside
of CADDS, using the set of script files supplied with this package. This table is
available in the read-only mode for the GENERATE PIPEDBASE command.
Table B-7 AEC Application Object Dictionary Table - AEC_APPLICATION_TBL

AEC_APPL_PROJID NOT NULL VARCHAR(8) Project name
AEC_APPL_COMPNAME NOT NULL VARCHAR(40) Project structure component
name
AEC_APPL_OBJTYPE NOT NULL NUMBER Object type unique
identification number
AEC_APPL_TABLENAME NOT NULL VARCHAR(40) Object table name
The AEC_APPL_PROJID field stores the project name. This project name should
be specified in the PART_PROJID field of the CV_PART_TBL table, created by
linking the CADDS part to the project, as described in Linking CADDS Parts to a
Project .

Piping RDBMS Tables
The AEC_APPL_COMPNAME field stores the name of the project structure

component to which the object belongs. The corresponding project structure
component name should be defined in the Project Component Table (Refer AEC
Project Component Table ) and associated with the AEC_COMP_COMPNAME
field.
The AEC_APPL_OBJTYPE field stores the unique object type number of the
application object. This number must be specified in the AEC_OBJECT_TYPEID
field of the AEC_OBJECT_TYPE_TBL discussed above.
The AEC_APPL_TABLENAME field stores the RDBMS table name that is

accessed by the various RDBMS related commands to store/read the attributes of
the corresponding application object type. The tables for Piping application are
discussed in the subsequent sections.
A typical application object dictionary table is as follows

Table B-8 Sample AEC_APPLICATION_TBL Table
AEC_APPL_ AEC_APPL_COM AEC_APPL_TABLENA

PROJID PNAME AEC_APPL_OBJTYPE ME
DEMO T-58 101 PIPE_COORD_TBL
DEMO T-58 102 PIPE_DRAW_TBL
DEMO T-58 103 PIPE_LINE_TBL
DEMO T-58 104 PIPE_SPEC_TBL
DEMO T-58 105 PIPE_MAT_TBL
DEMO T-58 51 PIPE_LIST_TBL
DEMO T-58 52 PIPE_ELEM_TBL
DEMO T-58 55 PIPE_BEND_TBL
DEMO T-58 56 PIPE_ITEM_TBL
DEMO T-58 57 PIPE_ENDTYPE_TBL
Script Files
create_application_table.sh can be used to create basic field structure for the application
object dictionary table.
fill_application_table.sh can be used to fill in a row of data into the application object
dictionary table
grant_user_tables.sh can be used to grant permission to a piping user for
accessing the application object dictionary table.

Piping RDBMS Tables
Syntax
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_application_table.
sh -l <dba_admn_user_name> -p <dba_admn_password> -t <table_name>
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_application_table.sh
-l <dba_admn_user_name> -p <dba_admn_password> -t <table_name> -P
<project> -C <component> -O <appl_tbl_type_id> -T <appl_tbl_name>
Example
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_application_table.
sh -l admn_user -p admn_pass -t AEC_APPLICATION_TBL
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_application_table.sh
-l admn_user -p admn_pass -t AEC_APPLICATION_TBL -P DEMO -C
STAGE-01 -O 101 -T PIPE_COORD_TBL
shown above. Subsequent rows can be inserted similarly, using the above script
file.
admn_user -p admn_pass -L pipe_user -P pipe_pass -t APPLICATION
-T AEC_APPLICATION_TBL
AEC Object Table

This table stores an unique object identifier OBJECT_UID for each object. The
unique object identifier is generated based on the RDBMS sequence facility. The
name of this table should be defined in the AEC_PROJECT_DICTIONARY_TBL
table as described above. Refer to AEC Project Dictionary Table .
Table B-9 AEC Object Table - AEC_OBJECT_TBL

OBJECT_PARTID NOT NULL NUMBER CADDS part identifier
OBJECT_CADDSUID NOT NULL NUMBER CADDS entity unique identifier
OBJECT_UID NOT NULL NUMBER AEC object unique identifier
OBJECT_COMPID NOT NULL NUMBER Project component ID to which the object
belongs.
OBJECT_TYPE NOT NULL NUMBER AEC object type

Piping RDBMS Tables
The OBJECT_PARTID is the unique identifier of CADDS part in which the object
resides. This identifier is associated with the PART_PARTID field in the
CV_PART_TBL table, created by linking the CADDS part to the project as
described in Linking CADDS Parts to a Project .
The OBJECT_CADDSUID is the unique CADDS entity identifier of the Piping

object.
The OBJECT_UID is the unique object identifier and is associated with the
OBJECT_UID field in the Pipeline Spool and Pipeline Spool Element Table.
The OBJECT_COMPID is the identification number of the project component, to

which the piping object belongs. This field has a value, as defined in the
AEC_COMP_COMPID field of the AEC Project Component Table .
The OBJECT_TYPE is the unique object type number of the AEC application
object. For piping application, it takes the following values.
OBJECT_TYPE = 51, if the object is a pipeline spool label
OBJECT_TYPE = 52, if the object is a pipeline spool element
OBJECT_TYPE = 55, if the object is a pipe bend
OBJECT_TYPE = 56, if the object is a pipe item
OBJECT_TYPE = 57, if the object is a pipe endtype element
Script Files
create_object_table.sh can be used to create basic field structure for the application
object table.
the application object table.
Since data is stored in the application object table by GENERATE PIPEDBASE

command, there is no script file for filling data into this table.
Syntax
% /usr/apl/cadds/data/cvaec/dbms/scripts/create_object_table.sh -l
<dba_admn_user_name> -p <dba_admn_password> -t <table_name>

Piping RDBMS Tables
Example
% /usr/apl/cadds/data/cvaec/dbms/scripts/create_object_table.sh
-l admn_user -p admn_pass -t AEC_OBJECT_TBL
admn_user -p admn_pass -L pipe_user -P pipe_pass -t OBJECT -T
AEC_OBJECT_TBL
AEC Measurement Unit Dictionary Table

This table stores the records which define the measurement unit to be used for data
field in the corresponding application database table. The name of this table
should be defined as table type UNIT in the
AEC_PROJECT_DICTIONARY_TBL table.
The records in this table are to be inserted by the database administrator outside
CADDS before executing GENERATE STDBASE command, and this table is
read-only to the GENERATE STDBASE command. This table is optional.
Table B-10 Measurement Unit Dictionary Table

AEC_UNIT_TABLE NOT NULL VARCHAR(40) Table name
AEC_UNIT_FIELD NOT NULL VARCHAR(40) Field name
AEC_UNIT_NAME NOT NULL VARCHAR(40) Measurement unit name
AEC_UNIT_DIMENSION NUMBER Measurement unit
dimension
The AEC_UNIT_TABLE field stores the name of the database table in which the
target attributes are to be stored.
The AEC_UNIT_FIELD field stores the name of the data field or column in the
database table in which the target attributes are to be stored.
The AEC_UNIT_NAME stores the measurement unit name of the corresponding

attribute. The measurement unit as defined in this field should match that of the
AEC_UNIT_SOURCE or the AEC_UNIT_TARGET field of the AEC
Measurement Unit Conversion Table in order to locate the conversion factor as
defined in the AEC_UNIT_FACTOR field in the same table to be used to convert
the numeric data for the specific attribute.
The AEC_UNIT_DIMENSION field stores the dimension of the base

measurement as stated in the AEC_UNIT_NAME.

Piping RDBMS Tables
The measurement unit as defined in the AEC_UNIT_NAME field in this table

should match the measurement unit as defined in the AEC_UNIT_SOURCE or
AEC_UNIT_TARGET field of the AEC Measurement Unit Conversion Table, in
order to locate the conversion factor as defined in the AEC_UNIT_FACTOR field,
in the same table which is used to convert the numeric data for the specified
attribute.
If the current measurement unit is not defined in the AEC Measurement Unit
Conversion Table, it could be that the measurement unit is dependent on the part
model unit. In such a case, the current measurement unit should be read as the
measurement unit selection name as defined in the AEC Measurement Unit Name
Dictionary Table so that the correct measurement unit name can be extracted
which can be used to read from the AEC Measurement Unit Conversion Table.
The database administrator should use the script files in the directory
/usr/apl/cadds/data/cvaec/dbms/scripts/ to setup the measurement
unit dictionary table prior to executing the GENERATE PIPEDBASE command.
Script Files
create_unit_dictionary_table.sh can be used to create the measurement unit dictionary table.
fill_unit_dictionary_table.sh can be used to fill records into the measurement unit dictionary
table.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_unit_dictionary_table.sh
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_unit_dictionary_table
.sh -l <dba_admn_user_name> -p <dba_admn_password> -L
<hvac_user_name> -P <hvac_password> -t <table_type> -T
<table_name> -F <field_name> -U <unit_name> -D <dimension>

Piping RDBMS Tables
Example
%
/usr/apl/cadds/data/cvpd/scripts/create_unit_dictionary_table.sh
-l admn_user -p admn_pass -t AEC_UNIT_TBL
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_unit_dictionary_table
.sh -l admn_user -p admn_pass -L pipe_user -P pipe_pass -T
PIPE_ELEMENT_TBL -F IN_AREA -U MM -D 2.
AEC Measurement Unit Name Dictionary Table

This table contains the records which define the measurement unit names
associated with the corresponding CADDS part unit. Given the measurement unit
selection name and the part unit of the given part in which the corresponding
object resides, the measurement unit name of the corresponding attribute can be
read from the field AEC_UNIT_UNAME.
If the measurement unit as defined in the field AEC_UNIT _NAME in the AEC
Measurement Unit Dictionary Table is not defined in the AEC Measurement Unit
Conversion Table, then the desired measurement unit part is part unit dependent.
In that case the desired measurement name should be read as the measurement
unit selection name in order to extract the actual target measurement name as
defined in the field AEC_UNIT_UNAME. The name of the AEC Measurement
Unit Name Table should be defined as table type UNAME in the
The records in this table are to be inserted by the database administrator outside
CADDS prior to the execution of GENERATE STDBASE command, and the
table is read-only for the GENERATE STDBASE command. This table is
optional.
Table B-11 CADDS Part Measurement Unit Dictionary Table
DATA FIELD NAME DATA TYPE DESCRIPTION

AEC_UNIT_SNAME NOT NULL VARCHAR(40) Measurement unit selection
name
AEC_UNIT_NAME NOT NULL VARCHAR(2) CADDS part unit (MM, CM, M,
KM, IN, FT, MI)
AEC_UNIT_UNAME NOT NULL VARCHAR(40) Measurement unit name
The AEC_UNIT_SNAME field stores the selection name of the measurement unit
of the corresponding attribute.
The AEC_UNIT_NAME field stores the part unit of the part in which the
associated object resides. It must have one of the following values.

Piping RDBMS Tables
MM - millimeter
CM - centimeter
M - meter
KM - kilometer
IN - inch
FT - foot
MI - mile
The AEC_UNIT_UNAME field defines the measurement unit name of the

corresponding attribute.
Script Files
create_uname_dictionary_table. can be used to create the AEC Measurement Unit Name

sh Dictionary Table
fill_uname_dictionary_table.sh can be used to fill in records into the existing Unit Name
Dictionary Table
Syntax
%
/usr/apl/cadds/data/cvpd/scripts/create_uname_dictionary_table.sh
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_uname_dictionary_tabl
e.sh -l <dba_admn_user_name> -p <dba_admn_password> -L
<hvac_user_name> -P <hvac_password> -t <table_type> -T
<table_name>
Example
%
/usr/apl/cadds/data/cvpd/scripts/create_uname_dictionary_table.sh
-l admn_user -p admn_pass -t AEC_PUNIT_TBL
%
/usr/apl/cadds/data/cvaec/dbms/scripts/fill_uname_dictionary_tabl
e.sh -l admn_user -p admn_pass -L pipe_user -P pipe_pass -S
<selection name> -P <part unit> -U <unit name>

Piping RDBMS Tables
AEC Measurement Unit Conversion Table

This table defines the measurement unit conversion factor or the multiplier stored
in the AEC_UNIT_FACTOR field which can be used to convert the numeric data
from measurement unit as defined in the AEC_UNIT_SOURCE field to one as
defined in the AEC_UNIT_TARGET field. The name of the measurement unit
conversion table should be defined as table type CONVERSION in the
The records in this table are to inserted by the database administrator outside
CADDS before executing GENERATE STDBASE command. This table is
optional.
Table B-12 Measurement Unit Conversion Table

AEC_UNIT_SOURCE NOT NULL VARCHAR(40) Measurement unit to be
converted from
AEC_UNIT_TARGET NOT NULL VARCHAR(40) Measurement unit to be
converted to
AEC_UNIT_FACTOR NOT NULL NUMBER Conversion factor to be used
The AEC_UNIT_SOURCE field stores the source measurement unit for the
conversion to be performed.
The AEC_UNIT_TARGET field stores the target measurement unit for the
conversion to be performed.
The AEC_UNIT_FACTOR field stores the measurement unit conversion factor

which can be used to convert from the source measurement unit to the target.
Script File
create_unit_conversion_table.sh can be used to create the ARC Measurement Unit Conversion

Table
fill_unit_conversion_table.sh can be used to insert records into the AEC Measurement Unit
Conversion Table.

Piping RDBMS Tables
Syntax
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_unit_conversion_ta
ble.sh -l <dba_admn_user_name> -p <dba_admn_password> -t
<table_name>
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_unit_conversion_tabl
e.sh -l <dba_admn_user_name> -p <dba_admn_password> -t
<measurement unit conversion table> -S <source measurement unit>
-T <target measurement unit> -F <measurement unit conversion
factor>
Example
%/usr/apl/cadds/data/cvaec/dbms/scripts/create_unit_conversion_ta
ble.sh -l admn_user -p admn_pass -t AEC_CONVERSION_TBL
%/usr/apl/cadds/data/cvaec/dbms/scripts/fill_unit_conversion_tabl
e.sh -l admn_user -p admn_pass -t AEC_UNIT_CONVERSION_TBL -S MM -T
M -F 0.001
AEC Application Object Relation Type Table

Table B-13 AEC Application Object Relation Type Table

AEC_RELATION_TYPENAME NOT NULL VARCHAR(20) Relationship type name
AEC_RELATION_TYPEID NOT NULL NUMBER Relationship identifier
The AEC_RELATION_TYPENAME field stores the application object link or the

relationship name.
The AEC_RELATION_TYPEID field stores the object link or the relationship

type identifier number.
Please note: You should set up your own numbering scheme for the supported
object link or relationship types of the corresponding application, as long as each
object type identifier is unique.
AEC Object LINK Relationship Table

This table defines the relationship between two objects. Each entry of this table
contains a unique identifier of each of the two objects which are related to each

Piping RDBMS Tables
other. The name of the table should be defined as table type LINK in the
AEC_Project _Dictionary_TBL.
Table B-14 Object Relationship or Link Table

LINK_OBJ1_UID NOT NULL NUMBER First AEC object unique
identifier
LINK_OBJ2_UID NOT NULL NUMBER Second AEC object unique
identifier
LINK_TYPE NUMBER Object link type number
The LINK_OBJ1_UID and LINK_OBJ2_UID fields are associated with the

OBJECT_UID field in the Object Table and the LINK_TYPE field is associated
with the AEC_LINK_TYPEID field in the AEC Application Object Link Type
Table.

Piping RDBMS Tables

The GENERATE PIPEDBASE and DRAW PSPOOL command require certain
additional information, apart from the graphical and non-graphical information
extracted from the CADDS model. This information should be made available by
the User in a standard library of RDBMS tables using the following standard
RDBMS table names and specified format.
A set of SQL script files are supplied with this package to create the basic field
structure and to fill sample records for these tables. This script files are available
under the following directories,
/usr/apl/cadds/data/cvpd/scripts/load/
Piping Coordinate Table

This table provides the identification name of the structural members at the
specified location in X, Y and Z direction in a plant or a ship co-ordinate system.
The name of this table is specified in AEC Application Object Dictionary Table ,
using the unique identification number for the PIPING_COORD keyword, as
specified in AEC Application Object Type Table .
Table B-15 Piping Coordinate Table
FIELD TYPE DESCRIPTION REMARK

MBR_NAME NOT NULL Item name (FRxxx, L/Sxxx,
VARCHAR2(5)) DKxxx)
DIRECTION NOT NULL VARCHAR2(1) X/Y/Z Direction KEY FIELD
LOCATION NOT NULL NUMBER Item position KEY FIELD
Script File
Directory location: /usr/apl/cadds/data/cvpd/scripts/
create_pcoord_table.sh can be used to create basic field structure for the piping
coordinate table.

the piping coordinate table.

Piping RDBMS Tables
Data files
Directory location: /usr/apl/cadds/data/cvpd/scripts/load
pcoord.ctl control file that defines the column format for the text data file
and specifies the table name.
pcoord.dat data file that contains rows of piping structural member
coordinate data with the column format as defined in the
control file.
Representative sample data is available in the supplied data file. You can load this
data into the table using the sqlload command as explained in the example below.
However, if you want to add or modify the supplied data, follow the steps below.
Make a copy of pcoord.dat and pcoord.ctl file to your local directory.

Add or modify the data in the pcoord.dat file, using the exact column format as
specified in pcoord.ctl file.
Modify the table name in pcoord.ctl.
Load the data from pcoord.dat using sqlload command as explained below.
Syntax
%/usr/apl/cadds/data/cvpd/scripts/create_pcoord_table.sh -l
%sqlload <dba_admn_user_name>/<dba_admn_password>
control=<control_file> data=<data_file>
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pcoord_table.sh -l
admn_user -p admn_pass -t PIPE_COORD_TBL
% sqlload <dba_admn_user_name>/<dba_admn_password>
control=pcoord.ctl data=pcoord.dat
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPING_COORD
-T PIPE_COORD_TBL

Piping RDBMS Tables
Piping Drawing Information Table

This table provides the information about the installation and fabrication drawing
numbers for the pipeline spool drawings, based on the project name and assembly
name as specified in the AEC Project Component Table .
Table B-16 Piping Drawing Information Table

PROJ_NAME NOT NULL Project Number KEY FIELD
VARCHAR2(10)
ASSEMBLY_NAME NOT NULL Component Tree Assembly KEY FIELD
VARCHAR2(10) Name
INSTDWG_NUMBER NOT NULL Install Standard Number
VARCHAR2(20)
FABDWG_NUMBER NOT NULL Fabrication Standard Number
VARCHAR2(20)
using the unique identification number for the PIPING_DRAW keyword, as
specified in AEC Application Object Type Table .
Script File
create_pdraw_table.sh can be used to create basic field structure for the piping
drawing information table.
grant_user_tables.sh can be used to grant permission to a piping

user for accessing the piping drawing
information table.
Data files
pdraw.ctl control file that defines the column format for the data file and
specifies the drawing information table name.
pdraw.dat data file that contains rows of piping drawing information data
with the column format as defined in the control file.
data into the drawing information table using the sqlload command as explained in
the example below.

Piping RDBMS Tables
Make a copy of pdraw.dat and pdraw.ctl file to your local directory.

Add or modify the data in the pdraw.dat file, using the exact column format as
specified in pdraw.ctl file.
Modify the table name in pdraw.ctl.
Load the data from pdraw.dat using sqlload command as explained below.
Syntax
%/usr/apl/cadds/data/cvpd/scripts/create_pdraw_table.sh -l
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pcoord_table.sh -l
admn_user -p admn_pass -t PIPE_DRAW_TBL
control=pdraw.ctl data=pdraw.dat
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPING_DRAW
-T PIPE_DRAW_TBL
Pipeline Information Table

This table provides pipeline information based on the pipeline number. The
information provided by this table includes details of the internal and external
painting, galvanizing, acid cleaning, oiling, steam tracing, insulation, hydro test
and non-destructive test requirements.

Piping RDBMS Tables
using the unique identification number for the PIPE_LINE keyword, as specified
in AEC Application Object Type Table .
Table B-17 Pipeline Information Table

LINE_NUMBER NOT NULL Pipeline Number KEY FIELD
VARCHAR2(20)
PIPE_SIZE NOT NULL VARCHAR2(6) Pipeline Size KEY FIELD
PIPE_SPEC NOT NULL Pipeline Spec KEY FIELD
VARCHAR2(18)
OUT_PAINT VARCHAR2(5) Out Area Paint Code
(K1/K2)
IN_PAINT VARCHAR2(2) In Area Paint Code
GALVANIZING VARCHAR2(1) Galvanizing Flag
ACID_CLEANING VARCHAR2(1) Acid Cleaning Flag
OILING VARCHAR2(1) Oiling Flag
INSUL_TYPE VARCHAR2(1) Insulation Type (A,B,C)
STEAM_TRACING VARCHAR2(1) Steam Tracing Flag
COAT_TYPE VARCHAR2(4) Coating Type
HYDRO_TEST VARCHAR2(6) Hydro Test Value
NDT_METHOD VARCHAR2(6) NDT test Method
Script File
create_pline_table.sh can be used to create the piping line information table.

pipeline information table.
Data files
pline.ctl control file that defines the column format for the data file and
specifies the pipeline information table name.
pline.dat data file that contains rows of pipeline information data with
the column format as defined in the control file.

Piping RDBMS Tables
data into the pipeline information table using the stalled command as explained in
the example below.
Make a copy of pline.dat and pline.ctl file to your local directory.

Add the data in the pline.dat file, using the exact column format as specified in
pline.ctl file.
Modify the table name in pline.ctl.
Load the data from pline.dat using sqlload command as explained below.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pline_table.sh -l
Example
admn_user -p admn_pass -t PIPE_LINE_TBL
control=pline.ctl data=pline.dat
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPE_LINE -T
PIPE_LINE_TBL

Piping RDBMS Tables
Pipe Specification Table

This table provides the information about the pipe material, certification class and
grade, design temperature and pressure for a given pipe specification.
using the unique identification number for the PIPE_SPEC keyword, as specified
Table B-18 Pipe Specification Table

PIPE_SPEC NOT NULL VAR CHAR(18) Piping Spec Code KEY FIELD
CERT_CLASS VAR CHAR2(14) Certification Class
DESIGN_TEMP VARCHAR2(10) Design Temperature
DESIGN_PRESS VARCHAR2(10) Design Pressure
Script File
create_pspec_table.sh can be used to create the piping specification table.

the pipe specification table.
Data files
pspec.ctl control file that defines the column format for the data file and
specifies the pipe specification table name.
pspec.dat data file that contains rows of pipe specification data with the
column format as defined in the control file.

Piping RDBMS Tables
data into the pipe specification table using the sqlload command as explained in
the example below.
Make a copy of pspec.dat and pspec.ctl file to your local directory.

Add or modify the data in the pspec.dat file, using the exact column format as
specified in pspec.ctl file.
Modify the table name in pspec.ctl.
Load the data from pspec.dat using sqlload command as explained below.
Syntax
%/usr/apl/cadds/data/cvpd/scripts/create_pspec_table.sh -l
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pspec_table.sh -l
admn_user -p admn_pass -t PIPE_SPEC_TBL
control=pspec.ctl data=pspec.dat
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPE_SPEC -T
PIPE_SPEC_TBL
Pipe Fabrication Material Table

This table provides the information about the weight, material, internal and
external area, welding length and cost code of pipe material based on stock
number.
The name of this table is specified in AEC Application Object Dictionary Table
, using the unique identification number for the PIPE_MAT keyword, as specified

Piping RDBMS Tables
Table B-19 Pipe Fabrication Material Table

STOCK_NUMBER NOT NULL VARCHAR2(40) Material Code KEY FIELD
ALLOC NOT NULL VARCHAR2(6) Material Allocation
MATERIAL VARCHAR2(12) Material
UOM NOT NULL VARCHAR2(2) Code for Unit of
Measurement (Metric -
MT or Imperial - IM)
WEIGHT NUMBER Weight of per unit
element. For pipe
segments this
represents weight per
unit length in specified
UOM.
OUT_AREA NUMBER Outer Area
IN_AREA NUMBER Inner Area
WELD_LENGTH NUMBER Equivalent Welding
Length based on
UOM.
DESCRIPTION NOT NULL VARCHAR2(40) Description
Script File
create_pmat_table.sh can be used to create the piping fabrication material table.

the pipe fabrication material table.
Data files
pmat.ctl control file that defines the column format for the data file and
specifies the pipe fabrication material table name.
pmat.dat data file that contains rows of pipe fabrication material data
with the column format as defined in the control file.
data into the pipe fabrication material table using the sqlload command as
explained in the example below.

Piping RDBMS Tables
Make a copy of pmat.dat and pmat.ctl file to your local directory.

Add or modify the data in the pmat.dat file, using the exact column format as
specified in pmat.ctl file.
Modify the table name in pmat.ctl.
Load the data from pmat.dat using sqlload command as explained below.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pmat_table.sh -l
Example
admn_user -p admn_pass -t PIPE_MAT_TBL
control=pmat.ctl data=pmat.dat
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPE_MAT -T
PIPE_MAT_TBL

Piping RDBMS Tables

The command GENERATE PIPEDBASE generates the following:
The pipeline list table

The pipeline spool element table
The pipeline bend table
The pipeline item number information table
The pipeline end type table
These tables store the model information for all the pipeline spools of a particular
project. The information is extracted from the various CADDS parts related to the
project.
Pipeline List Table

on page 12, using the keyword PIPE_LIST.
Table B-20 Pipeline List Table

SEQ_NO NOT NULL NUMBER Object Sequence Number KEY FIELD
generated by RDBMS
Software.
PARENT_SEQ NUMBER Parent Pipeline Label sequence
number. i.e label of the parent
of the current pipeline spool.
LINE_LABEL NOT NULL Pipeline or Pipe Spool Label
VARCHAR2(71)
LINE_LAYER NOT NULL NUMBER Pipeline Layer
LINE_SIZE NOTNULLVARCHAR2( Representative Line/Spool Size
6)
LINE_SPEC NOT NULL Line/Spool Spec
VARCHAR2(18)
START_XLOC NOT NULL NUMBER Spool Location (frame)
START_ YLOC NOT NULL NUMBER Spool Location (long)
START_ZLOC NOT NULL NUMBER Spool Location (deck)
OUT_PAINT VARCHAR2(5) Outer area Paint Code
IN _PAINT VARCHAR2(2) Inner area Paint Code
QUANTITY NOT NULL NUMBER Spool Quantity
DRAW_STATUS NUMBER Draw Spool Processing Status

Piping RDBMS Tables
Table B-20 Pipeline List Table

REV_NUMBER NOT NULL Pipeline Revision Number
VARCHAR2(2)
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_plist_table.sh -l
Example
% /usr/apl/cadds/data/cvpd/scripts/create_plist_table.sh -l
admn_user -p admn_pass -t PIPE_LIST_TBL
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPE_LIST -T
PIPE_LIST_TBL
Pipeline Element Table

on page 12, using the unique identification number for the PIPE_ELEMENT
keyword, as specified in AEC Application Object Type Table on page 9.
Table B-21 Pipeline Element Table

UID_2D NOT NULL NUMBER Object unique identification number
defined in AEC Object Table
UID_3D NOT NULL NUMBER Object unique identification number
defined in AEC Object Table, for
the objects 3D instance
REF_SEQ_NO NOT NULL NUMBER Reference sequence number as KEY FIELD
referred by the SEQ_NO of the
Pipeline List Table .
ELT_2D_NUMBE NOT NULL NUMBER 2D Pipe element sequence Number
R
ELT_3D_NUMBE NOT NULL NUMBER 3D Pipe element sequence Number
R
ELT_QUANTITY NOT NULL NUMBER Element Quantity
ELT_SNAME NOT NULL Element Selection Name
VARCHAR2(5)

Piping RDBMS Tables

ELT_NAME NOT NULL Element Component Name
VARCHAR2(5)
FIGURE_NAME NOT NULL Element NFigure name
VARCHAR2(20)
ELT_SPEC NOT NULL Element Spec
VARCHAR2(6)
ELT_SIZE NOT NULL Element Size
VARCHAR2(6)
NEW_SIZE VARCHAR2(6) New Size
STOCK_NUMBE VARCHAR2(40) Material Code (STKNO)
R
FR_2D_FITT NOT NULL NUMBER Previous 2D Fitting Number
TO_2D_FITT NOT NULL NUMBER Next 2D_Fitting Number
FR_3D_FITT NOT NULL NUMBER Previous 3D Fitting Number
TO_3D_FITT NOT NULL NUMBER Next 3D_Fitting Number
PIPE_ODIA NOT NULL NUMBER Pipe Out Diameter (for N/C)
PIPE_IDIA NOT NULL NUMBER Pipe In diameter (for N/C)
ELT_SCEB NOT NULL NUMBER Nfig origin code.(S-1,C-2,E-3,B-4) Future
SLOC_X NOT NULL NUMBER X co-ord of Element start location
SLOC_Y NOT NULL NUMBER Y co-ord of Element start location
SLOC_Z NOT NULL NUMBER Z co-ord of Element start location
CLOC_X NOT NULL NUMBER X co-ord of Element center location
CLOC_Y NOT NULL NUMBER Y co-ord of Element center location
CLOC_Z NOT NULL NUMBER Z co-ord of Element center location
ELOC_X NOT NULL NUMBER X co-ord of Element end location
ELOC_Y NOT NULL NUMBER X co-ord of Element end location
ELOC_Z NOT NULL NUMBER X co-ord of Element end location
BLOC_X NOT NULL NUMBER X co-ord of Element branch location
BLOC_Y NOT NULL NUMBER Y co-ord of Element branch location
BLOC_Z NOT NULL NUMBER Z co-ord of Element branch location
FLIP_TYPE NUMBER Fitting Flip type code
PIPE_LENGTH NUMBER Pipe Length
ELT_WEIGHT NUMBER Element Weight Future
OUT_AREA NUMBER Out Area Future
IN_AREA NUMBER In Area Future
WELD_LENGTH NUMBER Welding Length Future
ECC_CENTER NUMBER Eccentricity from center
ROTATE_ANGLE NUMBER Pipe/Fitting Rotation Angle

Piping RDBMS Tables

CORNER_ANGL NUMBER Pipe Bend/Elbow fitting angle
E
BEND_RADIUS NUMBER Bending radius
BEND_MARGIN NUMBER Bending Margin length
TRIM_STATUS NUMBER Elbow Trim status
SCALE_X NOT NULL NUMBER Fitting X scale
SCALE_Y NOT NULL NUMBER Fitting Y scale
SCALE_Z NOT NULL NUMBER Fitting Z scale
FIT_TYPE NUMBER Fitting type code(Elbow-40, etc)
INSERT_TYPE NUMBER Insertion type (Inline/RTOB/BTOR)
PLATE_LABEL VARCHAR2(10) Hole Plate label Future
FROMTO_DESC VARCHAR2(71) Continuation Line Description
Script Files
create_pelem_table.sh can be used to create basic field structure for the pipe spool
element table.
Directory location: /us/all/cards/data/caved/dbms/scripts/

the pipe spool element table.
Since data is stored in the pipe spool element table by GENERATE PIPEDBASE
command, there is no script file to fill in the data for this table.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pelem_table.sh -l
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pelem_table.sh -l
admn_user -p admn_pass -t PIPE_ELEMENT_TBL

Piping RDBMS Tables
admn_user -p admn_pass -L pipe_user -P pipe_pass -t PIPE_ELEMENT
-T PIPE_ELEMENT_TBL
Pipeline Bend Table

This table provides the information required to fabricate the bends of pipelines in a
given assembly.
on page 12 using the keyword PIPE_BEND, as specified in AEC Application
Object Type Table on page 9.
Table B-22 Pipeline Bend Information Table
FIELD NAME DATA TYPE DESCRIPTION

UID_3D NOT NULL Number Object unique identification
number defined in AEC Object
Table, for the 3D instance of
the object.
REF_SEQ_NO NOT NULL Number Reference sequence number,
as referred by the SEQ_NO
field of Pipeline List Table
BEND_PIECE_NUMBER NOT NULL Number Bend pipe piece number.
SLOC_X NOT NULL Number Relative X coordinate of bend
location.
SLOC_Y NOT NULL Number Relative Y coordinate of bend
location.
SLOC_Z NOT NULL Number Relative Z coordinate of bend
location.
CUM_LENGTH Number Cumulative length upto the
start of the bend.
BEND_RADIUS Number Bending Radius
BEND_MARGIN Number Bending Clamp Margin length
BEND_ANGLE Number Angle of the bend
ROTATION_ANGLE Number Relative rotation angle of the
bend with respect to the first
bend
Script File
create_pipe_bend_table.sh creates basic field structure for a pipeline bend

information table.

Piping RDBMS Tables
Directory location: /usr/apl/cadds/data/cvaec/dbms/scripts
grant_user_tables.sh grants permission to a PIPING user for accessing a

pipeline bend information table.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_bend_table.sh -l
<admn_username> -p <admn_password> -t <table_name>
<admn_username> -p <admn_password> -L <username> -P <password> -t
<table_type> -l <table_name>
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_bend_table.sh -l
admn_user -p admn_pass -t PIPE_BEND_TBL
admn_user -p admn_pass -L piping_user -P piping_pass -t PIPE_BEND
-T PIPE_BEND_TBL
Pipeline Item Number Information Table

This table provides the required item number information of each element of the
pipe spool.
on page 12 using the keyword PIPE_ITEM, as specified in AEC Application
Object Type Table on page B-9 .
Script File
Table B-23 Pipeline Item Number Information Table

REF_SEQ_NO NOT NULL Number Reference sequence number, as referred by
the SEQ_NO field of Pipeline List Table.
ITEM_NUMBER NOT NULL Number Number based on ITEMNUMB property
attached to pipe element.
ELT_3D_NUMBER NOT NULL Number 3D pipe element sequence number.
create_pipe_item_table.sh creates basic field structure for the Pipeline Item Number
Information Table.

Piping RDBMS Tables
grant_user_tables.sh grants permission to a PIPING user for accessing the

pipeline item number information table.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_item_table.sh -l
<admn_username> -p <admn_password> -t <table_name>
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_item_table.sh -l
admn_user -p admn_pass -t PIPE_ITEM_TBL
admn_user -p admn_pass -L piping_user -P piping_pass -t PIPE_ITEM
-T PIPE_ITEM_TBL

Piping RDBMS Tables
Pipeline End Type Table

This table provides information about the pipe end type in a given assembly, to
which the table is associated.
on page 12 using the keyword PIPE_ENDTYPE, as specified in AEC
Application Object Type Table on page 9.
Table B-24 Pipeline Fitting End Type Information Table

REF_SEQ_NO NOT NULL Number Reference sequence number, as referred by the
SEQ_NO field of Pipeline List Table
ITEM_NUMBER NOT NULL Number Number based on ITEMNUMB property attached to
the pipe piece
START_ENDTYPE VARCHAR2(10) The end type at the start of the pipe.
END_ENDTYPE VARCHAR2(10) The end type at the end of the pipe.
Script File
create_pipe_endtype_table.sh creates basic field structure for a pipeline end type

information table.
grant_user_tables.sh grants permission to a PIPING user for accessing a

pipeline end type information table.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_endtype_table.sh
-l <admn_username> -p <admn_password> -t <table_name>

Piping RDBMS Tables
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_endtype_table.sh -l
admn_user -p admn_pass -t PIPE_ENDTYPE_TBL
admn_user -p admn_pass -L piping_user -P piping_pass -t
PIPE_ENDTYPE -T PIPE_ENDTYPE_TBL

Piping RDBMS Tables

This section explains the procedure to run a set of top level script files supplied
with the package. Using these script files the creation of basic field structure for all
the required RDBMS tables, filling representative rows of data into the appropriate
project information and application specific read only tables and granting
permission to users for accessing these tables can be simplified.
This section covers the purpose and syntax of the top level script files with
examples.
Top Level Script Files

create_project_tables.sh Used to register a set of project tables for a specified project

in AEC_PROJECT_DICTIONARY_TBL and create the basic
structure for the specified project tables.
You can recreate the AEC_PROJECT_DICTIONARY_TBL
optionally using the -R option.
Please note: Use the -R option only if the existing

AEC_PROJECT_DICTIONARY_TBL needs to be dropped and recreated.
create_pipe_list_tables.sh The top level script that establishes all necessary tables for
running the piping RDBMS commands.This script also grants
permission for a piping user for all these tables.
You can recreate the project tables optionally using the -R
option.
Directory location: /usr/apl/cadds/data/cvpd/scripts.
The create_pipe_list_tables.sh top level script invokes the individual

table scripts and performs the following tasks.
Creates the basic field structure for all project Information tables for a project
DEMO and component SHIP1 and fills the necessary rows of data into these
tables.
Creates the basic field structure for all piping standard library tables and load
the data available in the text data files into these library tables.
Creates the basic field structure for pipeline list and element tables.
Grants permission to a piping user for accessing the project information and
piping tables.

Piping RDBMS Tables
Optionally recreates the project tables using the -R option.
In the above script file, following statements define the project, component and
various table names. User can modify these statements to suit his/her requirement,
before running the script file.
# Define the project name and assembly name under which all the tables are to
be registered.
project="DEMO"
assembly="SHIP1"
# Define project specific table names.
appl_tbl="AEC_APPLICATION_TBL"
comp_tbl="AEC_COMPONENT_TBL"
objtype_tbl="AEC_OBJECT_TYPE_TBL"
obj_tbl="AEC_OBJECT_TBL"
link_tbl="AEC_LINK_TBL"
reltype_tbl="AEC_RELATION_TBL"
prop_tbl="AEC_PROPERTY_DICTIONARY_TBL"
unit_tbl="AEC_UNIT_DICTIONARY_TBL"
uname_tbl="AEC_UNAME_DICTIONARY_TBL"
conv_tbl="AEC_UNIT_CONVERSION_TBL"
# Define pipe spool application table names
pcoord_tbl="PIPE_COORD_TBL"
pdraw_tbl="PIPE_DRAW_TBL"
pline_tbl="PIPE_LINE_TBL"
pspec_tbl="PIPE_SPEC_TBL"
pmat_tbl="PIPE_MAT_TBL"
plist_tbl="PIPE_LIST_TBL"
pelem_tbl="PIPE_ELEMENT_TBL"
pbend_tbl="PIPE_BEND_TBL"
pitem_tbl="PIPE_ITEM_TBL"
pendtyp_tbl="PIPE_ENDTYPE_TBL"

Piping RDBMS Tables
Granting Permissions to More Users

Using the top level script described above, set up all the tables and grant
permission for only one piping user. In order to grant permission for more users,
use the following script.
grant_project_tables.sh Used for granting permissions to a specified RDBMS user for

accessing the AEC_PROJECT_DICTIONARY_TBL and other
specified project tables.
grant_pipe_list_tables.sh Script file that grants permission for a new piping user for
accessing all necessary tables for running the piping RDBMS
commands.
The grant_pipe_list_tables.sh script invokes the individual scripts for

granting permission and performs the following tasks:
Grants permission to a new piping user to access all project Information tables,
Piping standard library tables, pipeline list and pipeline element table.
In this script file, all the tables names are defined. User can modify these table
names before invoking the script file.
Syntax
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_list_tables.sh -l
<dba_admn_user_name> -p <dba_admn_password> -d <script_dir_parh>
% /usr/apl/cadds/data/cvpd/scripts/grant_pipe_list_tables.sh -l
<pipe_password> -d <script_dir_path>
Example
% /usr/apl/cadds/data/cvpd/scripts/create_pipe_list_tables.sh -l
admn_user -p admn_pass -d /usr/apl
% /usr/apl/cadds/data/cvpd/scripts/grant_pipe_list_tables.sh -l
admn_user -p admn_pass -L pipe_user -P pipe_pass -d /usr/apl

Appendix C Spool Fabrication Drawing
Form Part
This appendix describes the spool fabrication drawing form part which is a
CADDS part that is supplied with the software. This form part serves as a template
for pipe line spool drawing generation. The form part is designed using a
procedure that is described below in this section. The content of the form part
determines the layout of the drawings generated by DRAW PSPOOL command.
The type and number of views required, the location of various textual objects and
their parameters are controlled by placing various text nodes in the form part, and
inserting the DWGOBJATTR and DWGOBJIDX properties with appropriate
values associated with these Tnodes.
Creating a Sample Form Part
Piping Reference C-1

Spool Fabrication Drawing Form Part

A step by step method for constructing a sample form part is described below.
1. Activate a CADDS part with the part name you want to store the form part.
(e.g. CVPD.SPOOL.FORM.A4X1).
2. Activate a CADDS drawing with a drawing name you want to store the form
drawing (e.g. A)
3. Issue SELECT MODE DRAW command to select the drawing mode of graphic
creation.
4. Create the form part outlines using CADDS commands.
5. Insert drawing extent Tnodes at the lower left and upper right corner of the
drawing.
The following legend applies for subsequent discussions:
d1 - drawing extents lower left location
d2- drawing extents upper right location
INSERT PROPERTY DWGOBJATTR 1: Draw Ent d1, d2
INSERT PROPERTY DWGOBJIDX 1: Draw Ent d1, d2
If there are multiple drawings within a single form part, then insert the
DWGOBJIDX with incremental values like 2, 3, 4, etc. for the subsequent
drawing extent Tnodes, keeping the DWGOBJATTR as 1 for all the Tnodes.
6. Insert the Tnodes at the lower left and upper right corner of the graphic extent
for all the drawings.
The following legend applies for subsequent discussions:
d3 - graphic extents lower left location
d4- graphic extents upper right location
INSERT PROPERTY DRWOBJATTR 1: Draw Ent d3, d4.
7. The value of the DWGOBJIDX property in the graphic extent Tnodes controls
the drawing view type and number of views that are created. For example if
TOP(CPL 1), FRONT(CPL 2), RIGHT(CPL 3) and ISO view (CPL 4) are
required, issue the following command.
INSERT PROPERTY DWGOBJIDX 1 2 3 4: Draw Ent d3
The DWGOBJIDX property for graphic extend can be inserted on, either in the
lower left Tnode or the upper right Tnode or both. For example, issuing the
following commands,
INSERT PROPERTY DWOBJIDX 1 2: Draw Ent d3
INSERT PROPERTY DWGOBJIDX 3 4: Draw Ent d4
C-2 Piping Reference

has the same effect as that of the previous command that inserted all the four
CPL values onto the graphic extents lower left Tnode.
If only isometric view is required, issue the following command.
INSER PROPERTY DWGOBJIDX 4: Draw Ent d3
8. Insert the all other textual Tnodes at the required locations on the drawing and
insert the DWGOBJATTR and DWGOBJIDX property as listed in the table
below. The height and width attribute of these text nodes controls the text
objects that are generated by the DRAW PSPOOL command.
9. Issue the following command after all the Tnodes are inserted, to save the
currently active drawing as a nodal figure,
FILE PART NFIG DRAW <drawname>
Save and exit the active form part.
EXIT PART FILE
A typical form part appears as shown in the following figure.
In the figure presented below the following are highlighted to clarify the
procedure explained above:
Drawing extent and graphic extent Tnodes are shown.
The values of the DWGOBJATTR and DWGOBJIDX properties are printed
separated by comma.
If the DWGOBJIDX property is not applicable, only the value of
DWGOBJATTR property is printed.
Please note: The property values of the various Tnodes are printed only for
illustration purpose and they do not appear as text entities in the actual form part .

Figure C-1 Pipe Line Spool Fabrication Drawing

Table C-1 DWGOBJATTR and DWGOBJIDX Properties
Description DWGOBJATTR DWGOBJIDX

Drawing Extent (lower left and upper 1 1 to n
right extent)
Graphic generation extend (lower left 2 1234
and upper right extend) 1 - Top view
2 - Front view
3 - Right view
4 - Iso view
Pipe spool element description 2001 1 to n
Pipe spool element size 2002 1 to n
Pipe spool element material 2003 1 to n
Pipe spool element length 2004 1 to n
Pipe spool element material location 2005 1 to n
Pipe Spool element remark 2006 1 to n
Bend start location in the forward 2007 1 to n
direction
Bend start location in the reverse 2042 1 to n
direction
Bend rotation angle in the forward 2008 1 to n
direction
Bend rotation angle in the reverse 2039 1 to n
direction
Bend corner angle 2009 1 to n
Bend radius 2010 1 to n
Flange straddling angle 2011 1 to n
Remark 2012 -
Drawing number 2013 -
Revision number 2014 -
Installation standard drawing number 2015 -
Fabrication standard drawing number 2016 -
Project name 2017 -
Assembly name 2018 -
Spool start location X axis member 2019 -
name
Spool start location Y axis member 2020 -
name
Spool start location Z axis member 2021 -
name
Design temperature 2022 -
Design pressure 2023 -
Insulation code 2024 -
Coating 2025 -

Description DWGOBJATTR DWGOBJIDX

Outside paint code 2026 -
Inside paint code 2027 -
Galvanizing type 2028 -
Oiling method 2029 -
Acid sealing status 2030 -
Steam tracing status 2031 -
Hydro test water pressure 2032 -
Non-destructive test method 2033 -
Certification class 2034 -
Total spool outer area 2035 -
Total spool inner area 2036 -
Total spool weight 2037 -
Total spool weld length 2038 -
Spool start location X in ship 2043 -
coordinate system
Spool start location Y in ship 2044 -
coordinate system
Spool start location Z in ship 2045 -
coordinate system
Flange Angle 2046 1 to n
Reverse Flange Angle 2047 1 to n
X-Coordinate of the end location 2048 1 to n
Y-Coordinate of the end location 2049 1 to n
Z-Coordinate of the end location 2050 1 to n
Longitudinal Datum of the end location 2051 1 to n
Transverse Datum of the end location 2052 1 to n
Water Plane Datum of the end location 2053 1 to n

Appendix D Parts in the Fitting Library
(CVPD.F)
This appendix lists the library parts that are referenced in the CVPD master
catalogs. It also includes illustrations of these components.
Introduction
Components
Component Properties
Piping Reference D-1

Introduction
Introduction
The following are the examples of figures in this appendix, which are listed in
alphabetical order by component name:
Angle Valve, Flanged - CVPD.F.ANGV

Ball Valve, Flanged - CVPD.F.BALV
Blind Flange, Flat Face - CVPD.F.BLFF
A complete listing of the library parts is given in the following sections of this
appendix. The illustrations of each of the components are available in Appendix C
to Appendix H.
The illustrations are of library parts that represent components referenced in the
CVPD master catalogs (ANSI standard and range of manufacturers pipe and
fittings). Some parts for the DIN/ISO standard are also included in the CVPD.F
parts library. The illustrations are similar to the ANSI ones; only the size and
specifications differ.
Each illustration shows the model isometric and top detail graphics. The graphics
are annotated with required parameters (Text codes).
The x-, y-, and z-scale listed in each model figure represents the amount the
illustration has been enlarged to make it more visible.
Library figures are supplied in single-precision format only. If you want to work in
double-precision format, reformat all your libraries using the script described in
Managing CADDS 5.
Your single- and double-precision libraries should be placed in separate CVPATHs

so they can be discriminated easily.
Please note: The procedure files of the library parts can be found in the
cadds/data/cvpd/f/_bcd directory.
D-2 Piping Reference

Components
Components
A list of standard components and the corresponding file names is given below
Table D-1 Standard Component List
Component Description Filename

BEND, 5 DIAMETER 180 DEGREE E518
BEND, 5 DIAMETER 90 DEGREE E5R9
BEND, 5 DIAMETER 90 DEGREE TRIMMED E5R9,TRIM
BRANCH, BY FULL COUPLING - SCREWED BRFS
BRANCH, BY FULL COUPLING - SOCKET WELD BRFW
BRANCH, BY HALF COUPLING - SCREWED BRHS
BRANCH, BY HALF COUPLING - SOCKET WELD BRHW
CAPP - BUTT WELD CAPP
CAPP - SCREWED CASC
CAPP - SOCKET WELD CASW
COUPLING, FULL - SCREWED CPFS
COUPLING, FULL - SOCKET WELD CPFW
COUPLING, HALF - SCREWED CPHS
COUPLING, HALF - SOCKET WELD CPHW
COUPLING, REDUCING - SCREWED CPRS
COUPLING, REDUCING - SOCKET WELD CPRW
CROSS - BUTT WELD CROS
CROSS - SCREWED CRSC
CROSS - SOCKET WELD CRSW
ELBOW, 30 DEGREE LONG RADIUS - BUTT WELD ELR3
ELBOW, 45 DEGREE - SCREWED ESC4
ELBOW, 45 DEGREE - SOCKET WELD ESW4
ELBOW, 90 DEGREE - SCREWED ESC9
ELBOW, 90 DEGREE SHORT RADIUS - BUTT WELD ESR9
ELBOW, 90 DEGREE - SOCKET WELD ESW9
ELBOW, LONG TANGENT 180 DEGREE LT18
ELBOW, TANGENT 45 DEGREE LONG RADIUS - BUTT WELD ELT4
ELBOW, TANGENT 90 DEGREE LONG RADIUS - BUTT WELD ELT9
ELBOW, TRIMMED 45 DEGREE ELR4.TRIM
ELBOW, TRIMMED 90 DEGREE - BUTT WELD ELR9.TRIM
ELBOW, REDUCING 90 DEGREE - BUTT WELD REL9

Components

ELBOWLET, SOCKET WELDED SELT
ELBOWLET, THREADED TELT
ELBOWLET, WELDED WELT
FLANGE, BLIND - FLAT FACE BLFF
FLANGE, BLIND - GROOVED BLGR
FLANGE, BLIND - RAISED FACE BLRF
FLANGE, BLIND - RING JOINT BLRJ
FLANGE, BLIND - TONGUE BLTF
FLANGE, LAP FACE SHORT STUB END LFLV
FLANGE, LAP FACE TYPE B LFLB
FLANGE, LAP FACE TYPE G LFLG
FLANGE, SLIP-ON - FLAT FACE SOFF
FLANGE, SLIP-ON - RAISED FACE SORF
FLANGE, SLIP-ON - RING JOINT SORJ
FLANGE, SOCKET WELD - FLAT FACE SWFF
FLANGE, SOCKET WELD - RAISED FACE SWRF
FLANGE, THREADED - FLAT FACE THFF
FLANGE, THREADED - RAISED FACE THRF
FLANGE, WELD NECK FEMALE END WNFE
FLANGE, WELD NECK FEMALE END TYPE R WNFR
FLANGE, WELD NECK LAP JOINT WNLJ
FLANGE, WELD NECK MALE END WNME
FLANGE, WELD NECK MALE END JOINT WNMJ
FLANGE, WELD NECK MALE END TYPE V WNMV
FLANGE, WELD NECK - FLAT FACE WNFF
FLANGE, WELD NECK - GROOVED WNGR
FLANGE, WELD NECK - RAISED FACE WNRF
FLANGE, WELD NECK - RING JOINT WNRJ
FLANGE, WELD NECK - TONGUE WNTF
GASKET GASK
NIPPLE, BRANCH - (NIPOLET) NLET
NIPPLE, PIPE - VARYING END TYPES NIPL
PLUG, HEXAGON HEAD - SCREWED PLHX
PLUG, ROUND HEAD - SCREWED PLRH
PLUG, SQUARE HEAD - SCREWED PLSQ
REDUCER, CONCENTRIC - BUTT WELD CRED
REDUCER, ECCENTRIC - BUTT WELD ERED

Components

SOCKOLET SLET
STRAINER STRN
TEE, REDUCING - BUTT WELD RTEE
TEE, REDUCING - SCREWED RTSC
TEE, REDUCING - SOCKET WELD RTSW
TEE, STRAIGHT - BUTT WELD STEE
TEE, STRAIGHT - SCREWED STSC
TEE, STRAIGHT - SOCKET WELD STSW
THREDOLET TLET
TRAP TRAP
UNION - SCREWED UNSC
UNION - SOCKET WELD UNSW
VALVE, ANGLE - FLANGED ANGV
VALVE, BALL - FLANGED BALV
VALVE, BALL - BUTT WELD BVBW
VALVE, BALL - SCREWED BVSC
VALVE, BALL - SOCKET WELD BVSW
VALVE, BUTTERFLY BTFY
VALVE, CHECK CHKW
VALVE, CHECK - BUTT WELD CHBW
VALVE, CHECK - FLANGED CHKV
VALVE, CHECK - SCREWED CHSC
VALVE, CHECK - SOCKET WELD CHSW
VALVE, CONTROL - FLANGED CTRV
VALVE, GATE - BUTT WELD GVBW
VALVE, GATE - FLANGED GATV
VALVE, GATE - SCREWED GVSC
VALVE, GATE - SOCKET WELD GVSW
VALVE, GLOBE - BUTT WELD GLBW
VALVE, GLOBE - FLANGED GLBV
VALVE, GLOBE - SCREWED GLSC
VALVE, GLOBE - SOCKET WELD GLSW
VALVE, NEEDLE - FLANGED NEDV
VALVE, PLUG - BUTT WELD PLBW
VALVE, PLUG - FLANGED PLGV
VALVE, PLUG - SCREWED PLSC
VALVE, PLUG - SOCKET WELD PLSW

Components

VALVE, RELIEF RELV
WELDOLET WLET

Following table lists the fittype properties of the standard components.
Table D-2 Properties
Name FITTYPE
ANGV 80
BALV 10
BLFF 30
BLGR 30
BLRF 30
BLRJ 30
BLTF 30
BRFS 51
BRFW 51
BRHS 51
BRHW 51
BTFY 12
BVBW 10
BVSC 10
BVSW 10
CAPP 39
CASC 39
CASW 39
CHBW 10
CHKV 10
CHKW 11
CHSC 10
CHSW 10
CPFS 62
CPFW 62
CPHS 62
CPHW 62
CPRS 62
CPRW 62
CRED 60
CROS 52
CRSC 52
CRSW 52
CTRV 10

Name FITTYPE
ELR3 40
ELR4 40
ELR4.TRIM 40
ELR6 40
ELR9 40
ELR9.TRIM 40
ELT4 40
ELT9 40
ERED 61
ESC4 40
ESC9 40
ESR9 40
ESW4 40
ESW9 40
E5R9 40
E5R9,TRIM 40
E518 40
GASK 20
GATV 10
GLBV 10
GLBW 10
GLSC 10
GLSW 10
GVBW 10
GVSC 10
GVSW 10
LFLB 30
LFLG 30
LFLV 30
LT18 40
NEDV 10
NIPL 63
NLET 51
PLBW 10
PLGV 10
PLHX 39
PLRH 39

Name FITTYPE
PLSC 10
PLSQ 39
PLSW 10
REL9 40
RELV 80
RTEE 50
RTSC 50
RTSW 50
SELT 51
SLET 51
SOFF 30
SORF 30
SORJ 30
STEE 50
STRN 60
STSC 50
STSW 50
SWFF 30
SWRF 30
TELT 51
THFF 30
THRF 30
TLET 51
TRAP 60
UNSC 62
UNSW 62
WELT 51
WLET 51
WNFE 30
WNFR 30
WNLJ 30
WNFF 30
WNGR 30
WNME 30
WNMJ 30
WNMV 30
WNRF 30

Name FITTYPE
WNRJ 30
WNTF 30

Appendix E Library Parts (1 to 21)
This appendix contains the following illustrations.
Introduction
Piping Reference E-1

Introduction
Introduction
The following library parts are illustrated in this appendix.
ANGV (ANGLE VALVE - FLANGED)

BALV (BALL VALVE - FLANGED)
BLFF (BLIND FLANGE - FLAT FACE)
BLGR (BLIND FLANGE - GROOVED)
BLRF (BLIND FLANGE - RAISED FACE)
BLRJ (BLIND FLANGE - RING JOINT)
BLTF (BLIND FLANGE - TONGUE)
BRFS (BRANCH BY FULL COUPLING - SCREWED)
BRFW (BRANCH BY FULL COUPLING - SOCKET WELD)
BRHS (BRANCH BY HALF COUPLING - SCREWED)
BRHW (BRANCH BY HALF COUPLING - SOCKET WELD)
BTFY (BUTTERFLY VALVE)
BVBW (BALL VALVE - BUTT WELD)
BVSC (BALL VALVE - SCREWED)
BVSW (BALL VALVE - SOCKET WELD)
CAPP (CAPP - BUTT WELD)
CASC (CAPP - SCREWED)
CASW (CAPP - SOCKET WELD)
CHBW (CHECK VALVE - BUTT WELD)
CHKV (CHECK VALVE - FLANGED)
CHKW CHECK VALVE
E-2 Piping Reference

ANGV (ANGLE VALVE - FLANGED)
BALV (BALL VALVE - FLANGED)
BLFF (BLIND FLANGE - FLAT FACE)

BLGR (BLIND FLANGE - GROOVED)
BLRF (BLIND FLANGE - RAISED FACE)
BLRJ (BLIND FLANGE - RING JOINT)

BLTF (BLIND FLANGE - TONGUE)
BRFS (BRANCH BY FULL COUPLING - SCREWED)
BRFW (BRANCH BY FULL COUPLING - SOCKET WELD)

BRHS (BRANCH BY HALF COUPLING - SCREWED)
BRHW (BRANCH BY HALF COUPLING - SOCKET WELD)
BTFY (BUTTERFLY VALVE)

BVBW (BALL VALVE - BUTT WELD)
BVSC (BALL VALVE - SCREWED)
BVSW (BALL VALVE - SOCKET WELD)

CAPP (CAPP - BUTT WELD)
CASC (CAPP - SCREWED)
CASW (CAPP - SOCKET WELD)

CHBW (CHECK VALVE - BUTT WELD)
CHKV (CHECK VALVE - FLANGED)
CHKW CHECK VALVE

Appendix F Library Parts (22 to 48)
Introduction
Piping Reference F-1

Introduction
Introduction
The following library parts are illustrated in this appendix
CHSC (CHECK VALVE SCREWED)

CHSW (CHECK VALVE SOCKET WELD)
CPFS (FULL COUPLING SCREWED)
CPFW (FULL COUPLING SOCKET WELD)
CPHS (HALF COUPLING SCREWED)
CPHW (HALF COUPLING SOCKET WELD)
CPRS (REDUCING COUPLING SCREWED)
CPRW (REDUCING COUPLING SOCKET WELD)
CRED (CONCENTRIC REDUCER BUTT WELD)
CROS (CROSS BUTT WELD)
CRSC (CROSS SCREWED)
CRSW (CROSS SOCKET WELD)
CTRV (CONTROL VALVE FLANGED)
ELR3 (ELBOW 30 DEGREE LONG RADIUS BUTT WELD)
ELR4.TRIM (TRIMMED 45 DEGREE ELBOW)
ELR9.TRIM (TRIMMED 90 DEGREE BUTT WELD)
ELT4 (TANGENT ELBOW 45 DEGREE LONG RADIUS BUTT WELD)
ELT9 (TANGENT ELBOW 90 DEGREE LONG RADIUS BUTT WELD)
ERED (ECCENTRIC REDUCER BUTT WELD)
ESC4 (ELBOW 45 DEGREE SCREWED)
ESR9 (ELBOW 90 DEGREE SHORT RADIUS BUTT WELD)
ESW4 (ELBOW 45 DEGREE SOCKET WELD)
F-2 Piping Reference

CHSC (CHECK VALVE SCREWED)
CHSW (CHECK VALVE SOCKET WELD)
CPFS (FULL COUPLING SCREWED)

CPFW (FULL COUPLING SOCKET WELD)
CPHS (HALF COUPLING SCREWED)
CPHW (HALF COUPLING SOCKET WELD)

CPRS (REDUCING COUPLING SCREWED)
CPRW (REDUCING COUPLING SOCKET WELD)
CRED (CONCENTRIC REDUCER BUTT WELD)

CROS (CROSS BUTT WELD)
CRSC (CROSS SCREWED)
CRSW (CROSS SOCKET WELD)

CTRV (CONTROL VALVE FLANGED)

ELR4.TRIM (TRIMMED 45 DEGREE ELBOW)

ELR9.TRIM (TRIMMED 90 DEGREE BUTT WELD)

LONG RADIUS BUTT WELD)

LONG RADIUS BUTT WELD)

ERED (ECCENTRIC REDUCER BUTT WELD)

ESR9 (ELBOW 90 DEGREE SHORT RADIUS BUTT WELD)

Appendix G Library Parts (49 to 66)
Introduction
Piping Reference G-1

Introduction
Introduction
The following library parts are illustrated in this appendix:
E5R9 (5 DIAMETER BEND 90 DEGREE)

E5R9.TRIM (5 DIAMETER BEND 90 DEGREE TRIMMED)
E518 (5 DIAMETER 180 DEGREE)
GASK (GASKET)
GATV (GATE VALVE FLANGED)
GLBV (GLOBE VALVE FLANGED)
GLBW (GLOBE VALVE BUTT WELD)
GLSC (GLOBE VALVE SCREWED)
GLSW (GLOBE VALVE SOCKET WELD)
GVBW (GATE VALVE BUTT WELD)
GVSC (GATE VALVE SCREWED)
GVSW (GATE VALVE SOCKET WELD)
LFLB (LAP FACE FLANGE, TYPE B)
LFLG (LAP FACE FLANGE, TYPE G)
LFLV (LAP FACE FLANGE SHORT STUB END)
LT18 (LONG TANGENT 180 DEGREE ELBOW)
NEDV (NEEDLE VALVE FLANGED)
NIPL (PIPE NIPPLE VARYING END TYPES)
G-2 Piping Reference

E5R9 (5 DIAMETER BEND 90 DEGREE)
E5R9.TRIM (5 DIAMETER BEND 90 DEGREE TRIMMED)
E518 (5 DIAMETER 180 DEGREE)

GASK (GASKET)
GATV (GATE VALVE FLANGED)
GLBV (GLOBE VALVE FLANGED)

GLBW (GLOBE VALVE BUTT WELD)
GLSC (GLOBE VALVE SCREWED)
GLSW (GLOBE VALVE SOCKET WELD)

GVBW (GATE VALVE BUTT WELD)
GVSC (GATE VALVE SCREWED)
GVSW (GATE VALVE SOCKET WELD)

LFLB (LAP FACE FLANGE, TYPE B)
LFLG (LAP FACE FLANGE, TYPE G)
LFLV (LAP FACE FLANGE SHORT STUB END)

LT18 (LONG TANGENT 180 DEGREE ELBOW)
NEDV (NEEDLE VALVE FLANGED)
NIPL (PIPE NIPPLE VARYING END TYPES)

Appendix H Library Parts (67 to 81)
Introduction
Piping Reference H-1

Introduction
Introduction
NLET (BRANCH NIPPLE NIPOLET)

PLBW (PLUG VALVE BUTT WELD)
PLGV (PLUG VALVE FLANGED)
PLHX (HEXAGON HEAD PLUG SCREWED)
PLRH (ROUND HEAD PLUG SCREWED)
PLSC (PLUG VALVE SCREWED)
PLSQ (SQUARE HEAD PLUG SCREWED)
PLSW (PLUG VALVE SOCKET WELD)
REL9 (REDUCING ELBOW 90 DEGREE BUTT WELD)
RELV (RELIEF VALVE)
RTEE (REDUCING TEE BUTT WELD)
RTSC (REDUCING TEE SCREWED)
RTSW (REDUCING TEE SOCKET WELD)
SELT (SOCKET WELDED ELBOWLET)
SLET (SOCKOLET)
H-2 Piping Reference

NLET (BRANCH NIPPLE NIPOLET)
PLBW (PLUG VALVE BUTT WELD)
PLGV (PLUG VALVE FLANGED)

PLHX (HEXAGON HEAD PLUG SCREWED)
PLRH (ROUND HEAD PLUG SCREWED)
PLSC (PLUG VALVE SCREWED)

PLSQ (SQUARE HEAD PLUG SCREWED)
PLSW (PLUG VALVE SOCKET WELD)
REL9 (REDUCING ELBOW 90 DEGREE BUTT WELD)

RELV (RELIEF VALVE)
RTEE (REDUCING TEE BUTT WELD)
RTSC (REDUCING TEE SCREWED)

RTSW (REDUCING TEE SOCKET WELD)
SELT (SOCKET WELDED ELBOWLET)
SLET (SOCKOLET)

Appendix I Library Parts (82 to 96)
Introduction
Piping Reference I-1

Introduction
Introduction
SOFF (SLIP-ON FLANGE FLAT FACE)

SORF (SLIP-ON FLANGE RAISED FACE)
SORJ (SLIP-ON FLANGE RING JOINT)
STEE (STRAIGHT TEE BUTT WELD)
STRN (STRAINER)
STSC (STRAIGHT TEE SCREWED)
SWFF (SOCKET WELD FLANGE FLAT FACE)
SWRF (SOCKET WELD FLANGE RAISED FACE)
TELT (THREADED ELBOWLET)
THFF (THREADED FLANGE FLAT FACE)
THRF (THREADED FLANGE - RAISED FACE)
TLET (THREDOLET)
TRAP (TRAP)
UNSC (UNION SCREWED)
UNSW (UNION SOCKET WELD)
I-2 Piping Reference

SOFF (SLIP-ON FLANGE FLAT FACE)
SORF (SLIP-ON FLANGE RAISED FACE)
SORJ (SLIP-ON FLANGE RING JOINT)

STEE (STRAIGHT TEE BUTT WELD)
STRN (STRAINER)
STSC (STRAIGHT TEE SCREWED)

SWFF (SOCKET WELD FLANGE FLAT FACE)
SWRF (SOCKET WELD FLANGE RAISED FACE)
TELT (THREADED ELBOWLET)

THFF (THREADED FLANGE FLAT FACE)
THRF (THREADED FLANGE - RAISED FACE)
TLET (THREDOLET)

TRAP (TRAP)
UNSC (UNION SCREWED)
UNSW (UNION SOCKET WELD)

Appendix J Library Parts (97 to 109)
Introduction
Piping Reference J-1

Introduction
Introduction
WELT (WELDED ELBOWLET)

WLET (WELDOLET)
WNFE (WELD NECK FEMALE END FLANGE)
WNFF (WELD NECK FLANGE FLAT FACE)
WNFR (WELD NECK FEMALE END FLANGE, TYPE R)
WNGR (WELD NECK FLANGE GROOVED)
WNME (WELD NECK MALE END FLANGE)
WNMJ (WELD NECK MALE END JOINT FLANGE)
WNMV (WELD NECK MALE END FLANGE, TYPE V)
WNRF (WELD NECK FLANGE RAISED FACE)
WNLJ (WELD NECK LAP JOINT FLANGE)
WNRJ (WELD NECK FLANGE RING JOINT)
WNTF (WELD NECK FLANGE TONGUE)
J-2 Piping Reference

WELT (WELDED ELBOWLET)
WLET (WELDOLET)
WNFE (WELD NECK FEMALE END FLANGE)

WNFF (WELD NECK FLANGE FLAT FACE)
WNFR (WELD NECK FEMALE END FLANGE, TYPE R)
WNGR (WELD NECK FLANGE GROOVED)

WNME (WELD NECK MALE END FLANGE)
WNMJ (WELD NECK MALE END JOINT FLANGE)
WNMV (WELD NECK MALE END FLANGE, TYPE V)

WNRF (WELD NECK FLANGE RAISED FACE)
WNLJ (WELD NECK LAP JOINT FLANGE)
WNRJ (WELD NECK FLANGE RING JOINT)

WNTF (WELD NECK FLANGE TONGUE)

Index
A B
Add, annotation 2-5 Bend
Analysis programs, data 1-8 deleting 2-68
Analysis, assembly 5-20 inserting 2-68, 3-119
Annotate radius of 3-119, 3-122
datum 2-10 Bolting 1-7, 1-33, 1-40, 4-18
fieldwelds 2-25 Bolts 3-67
instrument numbers 2-15 Boundaries 1-23
item numbers 2-16 BRAD property 3-119, 3-122
orientation 2-19 Branch, fittings 4-24
shopwelds 2-25
slope 2-21
trimmed elbow 2-23
welds 2-25 C
Annotation 1-4, 1-39 CADDS part to a project, linking B-3
add 2-5 Change layer 2-52
dimension 2-5 Clearance
saving 1-5 checking 1-32
ANSI (American National Standards Clearance checking 1-32, 1-34, 1-40
Institute) 3-53
Code, IFC 4-10
ANSI standard 1-2
Commands
Assembly
ANNOTATE ISOMETRIC 2-5
analysis 5-20
CHANGE PLINE 2-50
file 3-65
CONSTRUCT PLINE 2-53
inserting 4-19
CREATE DETAIL 1-19
Automatic detailing 1-4
CREATE ISOMETRIC 2-59
Autoselection 1-33, 4-10
DELETE BEND 2-68
file 3-53, 3-64, 3-68
DELETE FITTING 2-70, 2-71
GENERATE PSFILE 3-53, 3-65
DELETE PENETRATION 2-80
process 1-27, 1-32, 1-33, 1-37, 3-54
DELETE PLINE 2-81
DELETE PSUPPORT 2-83
DIMENSION ISOMETRIC 2-85, 2-86
DIMENSION PIPE 2-90
Piping Reference Index-1

Index
DRAW PSPOOL 2-98, 2-99 Corner, fittings 4-17

GENERATE CLINE 3-2
GENERATE CSSYMBOL 3-11
GENERATE EXPLICITPIPE 3-16
GENERATE ISOMETRIC 3-21 D
GENERATE MDF 3-31 Data extract 1-14, 1-40
GENERATE PIPEDBASE 3-34 Datum
GENERATE PSFILE 1-27, 1-32, 3-53 annotate 2-10
GENERATE SPOOL 3-71 coordinate 4-3
HIDE INTERSECTION 3-96 Deleting
HIGHLIGHT PLINE 3-107 bends 2-68
INDICATE PENETRATION 3-116 downstream fittings 2-73
INSERT BEND 3-119 groups of fittings 2-72
INSERT DATUM 4-2 line attachment 2-72
INSERT FITTING 1-15, 1-16, 1-18, 1-31, 1-32, 4-10, 4-11 Description files 1-27, 1-28, 1-40
INSERT PBREAK 4-44 Design rules 1-3
INSERT PLABEL 4-50 Detailing
INSERT PSUPPORT 4-54 automatic 1-4
INSERT REFDIMENSION 4-57 single-line 1-21
LINK PROJECT 1-18 Dimensioning, OFF 2-12
MODIFY PLINE 5-2 Dimensions, annotating 2-5
OFFSET PLINE 5-13 DIN/ISO standard 1-2
REFERENCE STRUCTURE 5-18 Directory file 1-15, 1-25, 1-27, 1-28, 5-81
RELATE PLABEL 5-19 Documentation, printing from Portable
REPORT PIPE 5-20 Document Format (PDF) file 1-xxx
ROUTE PIPE 1-16, 1-19, 1-22, 1-32, 5-40 Drawing
SAVE ANNOTATIONS 5-56 isometric 1-5
SELECT PIPE 1-34 production 1-39
SELECT PPARAMETERS 1-15, 1-16, 1-19, 5-67 Drawing arrangement, isometric 2-12
SPLIT PIPE 5-82 DUCTSIZE property 4-20, 4-42
TRANSLATE EQUIPMENT 5-83
TRANSLATE ISOMETRIC 5-91
VERIFY DISTANCE 5-104
COMPNAME property 4-11 E
Component
Eastings 1-4
end type 3-68
Eccentric enlarger 1-21
flange 3-67
Elbow 4-10
gasket 3-67
elbowlet 1-23, 4-24
relief valve 3-68
inserting 3-67, 4-17, 4-19, 4-21, 4-23, 4-32
types 3-67
trimmed 1-23
wafered valve 3-68
trimming 4-25
Components, standard D-3
Elbow fitting 4-36
properties D-7
Elevations 1-4
CONNECTOR property 5-33
End segments, hidden 1-20
Coordinate
End type 4-10, 4-11, 4-16, 4-17, 4-18, 4-24, 4-31
datum 4-3
ENDTYPE property 4-18, 4-24, 4-31, 4-37
explicit 4-21, 4-24, 4-27, 4-42
EQUIP property 5-36
incremental 4-29
Equipment 1-34
PLEN 4-41
construction 1-8, 1-36
polar 4-29
Index-2 Piping Reference

Index
library changes 1-8 properties D-7

shapes 1-21 reducing 1-19, 4-15
Execute files 1-27, 1-28, 2-53 tap 4-10, 4-15
Exit, main 1-9 tee 1-41, 3-67, 4-15
FITTYPE property 5-25, 5-34
Flange 3-67
F Flow arrows 2-25
Flow direction 1-9, 1-21, 5-37
Fieldwelds Form part, sample C-2
annotate 2-25
Files
assembly 3-65
Autoselection 4-10
G
autoselection 3-53, 4-10 Gasket, bolted 3-67
autoselection (ASFILES) 1-27 Generate
data 1-26 piping reports 1-7, 1-40
description 1-27 piping specification 3-53
Directory 1-27 piping specification files 1-2
directory 1-25, 1-28 project information and piping tables B-42
execute 1-27, 1-28, 2-53 report data 1-10
input (INFILES) 1-26, 1-27 Graphics
master catalogs (MCATS) 1-26, 1-27 detail 2-50
naming conventions 1-26 double-line 1-19
nonmatching 3-53
parameter 1-27, 1-28, 3-53
piping A-1
piping specification 1-2 I
routine 1-27, 1-29
IFC Code 3-67, 4-10, 4-17
support 1-26
INFILE 3-64
Fitting library D-1
sample 3-58
parts D-1
Information
Fittings 2-70
flow 1-30
automatic insertion of 1-3
input 1-30
branch 1-14, 1-18
output 1-30
branching 4-24, 4-28
INNERDIAM property 3-119
corner 4-10, 4-17, 4-42
Insert
deletion of 1-3
bend 2-68
double reducing 1-3, 3-59, 3-64, 4-10
elbow 4-21
downstream 2-73
Insert Fitting Code (IFC) 3-67, 4-10
eccentric 2-72
INSLOC property 5-34
elbow 3-69
Instrument
flange 1-3
lines 1-17
library 1-26, 1-33, 4-11, 4-24
location 1-17
line attachment 1-14, 3-68, 4-10, 4-34
Instrumentation
parametric 4-10
generating reports 1-7
parts library
Insulation 1-17
illustrations E-1, F-1, G-1, H-1, I-1, J-1
Interference checking 1-2, 1-8, 1-15, 1-19, 1-20, 1-25,
standard components D-3 1-28

Index
INTERNAL property 4-40, 5-34 Nodal figure (Nfigure), nested 2-50

Isometric 1-10 Nodal line
annotating 1-5 internal 1-17
create drawing 1-5 Node
drawings, producing 1-5 connect 1-17
piping text 1-17
dimensioning 1-6 Northings 1-4
translating 1-5 Nozzle 1-15, 1-34
NPS property 5-35
L O
Labels, pipeline 5-27, 5-36, 5-37, 5-80
LASTLINK property 5-28, 5-34 OPC (Off-Page connector) property 5-35
Layering 1-4
changing 2-50, 2-52
conventions 1-25
parameter files 1-25
P
Library J-1 P&IDs 1-10
figures D-2 PAFILE 1-28
fitting D-1 PAFILES 1-27
fittings 4-11 Parameter 1-34
parts D-1, E-1, F-1, G-1, H-1, I-1, J-1 default 1-4
Linking CADDS part to a project B-3 files 1-27, 1-28, 1-34
LPROP property 5-35 Parameter file 3-53, 3-66
Parameters 5-67
Parametric
M fittings 1-34
length 1-20
Master catalogs 1-27 procedures 1-34
requirement 3-53 scale 1-21
standards 1-2 Parametric scaling 3-53
MIPTR 3-107 Part
Modeling, piping design properties 1-11 precision 1-3
properties 1-11
text file 1-13
N PARTTYPE property 5-81

Permanent appearance 1-20
Networks Pipe line
reconstruct 2-70
construction parameters 1-9
Pipeline
generating reports 1-10
designing 1-30
interpreting piping 1-9
drawings 1-4
Nfg, fullC 1-31, 1-36
editing 1-4
Nfigure 1-31
NMFILE (Nonmatching file) 3-53, 3-56 routing 1-3
NOBREAK property 4-40, 5-35 Pipeline definitions
Nodal label 5-80
line routing 5-40
internal 1-17 Piping

Index
design features 1-2 TRIM 4-25

design procedures 1-31 types of 1-11, 1-13
Files A-1
reports, generating 1-7
specification 1-32
INFILE 1-33 R
Piping and instrumentation diagrams (P&ID) 1-37 RDBMS, environment variables setup B-2
Piping RDBMS tables B-1 Reconstruct, pipe line 2-70
Piping specification Reporting
file, (Autoselection) 3-53, 3-56 clearance/interface 1-40
generating 3-53 Data extract 1-40
sheet 3-58 from model 1-40
Primitives 1-20 origin 5-20
Printing documentation from Portable P&ID 1-40
Document Format (PDF) file 1-xxx
stress analysis 1-40
Procedure
Reports, generating 1-10, 1-40
file 1-20, 1-28, 1-34, 1-40 Resource file
name 1-20
RDBMS environment variables
Process
.caddsrc-local B-2
autoselection 1-27
.cshrc B-2
Project name 1-20
.login B-2
Project, linking to a CADDS part B-3
Rotation 4-24
Properties 1-2, 1-4
Routine files 1-27
ABOVE 5-81
BRAD 3-119, 3-122
COMPNAME 4-11
component D-7
CONNECTOR 5-33
S
DUCTSIZE 4-20 Sample, infile 3-58
ENDTYPE 4-18 Scale conventions 4-10, 4-22, 4-25
EQUIP 5-34 Selection name 1-22
FITTYPE 5-25 Setup RDBMS environment variables B-2
INNERDIAM 3-119 Shape
INSLOC 5-34 code 1-21
INTERNAL 4-40 type 1-21
ITEMNO 5-34 Sheet, piping specification 3-58
LASTLINK 5-28 Shopweld, annotate 2-25
Line 5-35 Skew 2-72
NOBREAK 4-40 SNAME property 4-11
NPS 5-35 SPEC 1-22
OPC 5-35 Special fabrication 1-22
OUTERDIAM 3-119 Specification
part 1-11 file 1-33, 1-40
PARTTYPE 5-81 generating 1-32
PROJNAME 5-81 Spool Fabrication
SNAME 4-11 drawing form part C-1
STOCKNO 3-119 Standard components, fitting parts library
TERMNAM 2-78, 5-35 properties D-7
text file 1-13 Stick fg, fullC 1-31

Index
Stock number 1-12, 1-18, 1-22

STOCKNO property 3-119, 5-28
Structures 1-16, 1-27, 1-40
Support
files 1-26
structures 1-26
Symbols, for isometric drawings 2-32
T
Tables
generating project information B-42
pipe line spool RDBMS B-33
piping RDBMS B-1
piping standard library RDBMS B-23
pipe fabrication material B-30
pipe line information B-26
pipe specification B-29
piping coordinate B-23
piping drawing Information B-25
project information B-4
AEC application object dictionary B-12
AEC application object type B-9
AEC object B-14
AEC project component B-7
AEC project dictionary B-4
Tap 1-23
fittings 4-15
nested fitting 1-23
Tee, fittings 4-15
Temporary Nline 1-23
Termination point 1-23
Terminus name 1-23
TERMNAM property 1-9, 2-78, 5-35
Text files, manipulating 1-7
Text node 1-23
Text, annotating 2-5
Title block 1-23
Trim, elbow 4-25
W
Weld 1-23
annotate 2-25

Piping Reference PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Piping Reference PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Piping

Parametric Technology Corporation

UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL

UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGEND

Parametric Technology Corporation, 140 Kendrick Street, Needham, MA 02494 USA

Piping Design Overview

Pipe Reporting ___________________________________________________ 1-9

Properties and Part Properties ___________________________________ 1-11

Piping Reference Contents-iii

Properties and Part Properties Library _____________________________ 1-13

Contents-iv Piping Reference

Suggested Layering Conventions _______________________________ 1-25

Support Files ___________________________________________________ 1-26

Designing a Pipeline ____________________________________________ 1-30

Constructing Equipment ________________________________________ 1-36

Piping and Instrumentation Diagrams (P&IDs) ____________________ 1-37

Piping Reference Contents-v

Producing Drawings _____________________________________________ 1-39

Generating Piping Reports _______________________________________ 1-40

Piping Commands - Part 1

Command Format _______________________________________________ 2-4

ANNOTATE ISOMETRIC ____________________________________________ 2-5

Contents-vi Piping Reference

CHANGE PLINE (PIPELINE) _______________________________________ 2-50

CONSTRUCT PLINE (PIPELINE) ____________________________________ 2-53

CREATE ISOMETRIC _____________________________________________ 2-59

Piping Reference Contents-vii

DELETE BEND ____________________________________________________ 2-68

DELETE PENETRATION ____________________________________________ 2-80

DELETE PLINE (PIPELINE) __________________________________________ 2-81

Contents-viii Piping Reference

DELETE PSUPPORT (Pipe Support) ________________________________ 2-83

DIMENSION ISOMETRIC__________________________________________ 2-85

DIMENSION PIPE ________________________________________________ 2-90

DRAW PSPOOL _________________________________________________ 2-99

Piping Reference Contents-ix

Piping Commands - Part 2

GENERATE CSSYMBOL (Cut Section Symbol) ______________________ 3-11

Contents-x Piping Reference

GENERATE ISOMETRIC___________________________________________ 3-21

GENERATE MDF (Material Description File) _______________________ 3-31

GENERATE PIPEDBASE ___________________________________________ 3-34

Piping Reference Contents-xi

GENERATE PSFILE (Piping Specification File) _______________________ 3-53

GENERATE SPOOL _______________________________________________ 3-71

Contents-xii Piping Reference

HIDE INTERSECTION _____________________________________________ 3-96

HIGHLIGHT PLINE (Pipeline) _____________________________________ 3-107

INDICATE PENETRATION ________________________________________ 3-116

Piping Reference Contents-xiii

Piping Commands - Part 3

INSERT FITTING ___________________________________________________ 4-10

Contents-xiv Piping Reference

INSERT PBREAK (Pipe Break) _____________________________________ 4-44

INSERT PLABEL (Pipeline Label) __________________________________ 4-50

INSERT PSUPPORT (Pipe Support) _________________________________ 4-54

INSERT REFDIMENSION (Reference Dimension) ____________________ 4-57

Piping Reference Contents-xv

Piping Commands - Part 4

OFFSET PLINE (Pipeline) __________________________________________ 5-13

REFERENCE STRUCTURE __________________________________________ 5-18

RELATE PLABEL (Pipeline Label) ___________________________________ 5-19

Contents-xvi Piping Reference