COMOS 4 - Siemens · Legal information Legal information Warning notice system This manual contains...

�PipeSpec Designer�

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

COMOS

Process PipeSpec Designer

Operating Manual

08/2011 A5E03640238-01

Trademarks 1

Introduction 2

Getting started 3

Configuring the pipe spec 4

Using bolt sets 5

Miscellaneous information about pipe specs

6

Administration 7

Reference to the COMOS DB

8

"Error analysis for 3D objects" plugin

9

Legal information

Legal information Warning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens products Note the following:

WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY

A5E03640238-01 Ⓟ 08/2011

Copyright © Siemens AG 2011. Technical data subject to change

PipeSpec Designer Operating Manual, 08/2011, A5E03640238-01 3

Table of contents

1 Trademarks ............................................................................................................................................. 11

2 Introduction.............................................................................................................................................. 13

2.1 Welcome to the PipeSpec Designer module ...............................................................................13

2.2 Legal notice..................................................................................................................................14

2.3 General requirements ..................................................................................................................15

2.4 Classes managed in the PipeSpec Designer ..............................................................................15

3 Getting started ......................................................................................................................................... 17

3.1 Opening the PipeSpec Designer..................................................................................................17

3.2 The PipeSpec Designer interface ................................................................................................18

3.3 The "Load pipe spec" window......................................................................................................19 3.3.1 The interface of the "Load pipe spec" window.............................................................................19

3.4 Loading an existing pipe spec......................................................................................................20

3.5 Creating a new pipe spec ............................................................................................................21

3.6 Naming pipe specs ......................................................................................................................23

3.7 Deleting pipe specs......................................................................................................................23

3.8 Creating folders for structuring pipe specs ..................................................................................24

3.9 Tabs of the PipeSpec Designer ...................................................................................................24

4 Configuring the pipe spec ........................................................................................................................ 27

4.1 Workflow ......................................................................................................................................27

4.2 Requirements...............................................................................................................................27

4.3 "PipeSpec limits" tab....................................................................................................................28 4.3.1 Assigning a standardization .........................................................................................................28 4.3.2 Defining the nominal diameter range...........................................................................................29 4.3.3 Defining the use limits of the pipe spec .......................................................................................31 4.3.4 Defining the use limits of media...................................................................................................32 4.3.5 Defining the outer diameter and wall thickness ...........................................................................32

4.4 "Characteristics" tab.....................................................................................................................34 4.4.1 Defining the fluid parameters of the pipe spec ............................................................................34 4.4.2 Defining the fluid group according to the PED.............................................................................34 4.4.3 Defining other characteristics of the pipe spec ............................................................................35 4.4.4 Defining nominal-diameter-dependent parameters .....................................................................36

4.5 "Components" tab ........................................................................................................................38 4.5.1 The pipe part table .......................................................................................................................38 4.5.2 Assigning a new pipe part............................................................................................................40 4.5.3 Navigating to the pipe part ...........................................................................................................40 4.5.4 Setting the upper and lower limits of the DN range of a pipe part ...............................................41

Table of contents

PipeSpec Designer 4 Operating Manual, 08/2011, A5E03640238-01

4.5.5 Adding a component to the branch table .................................................................................... 41

4.6 "Nominal diameters" tab:............................................................................................................. 42 4.6.1 Preselected components............................................................................................................. 42 4.6.2 User interface reference.............................................................................................................. 42 4.6.3 Defining preselected components............................................................................................... 45 4.6.4 Refining nominal diameter ranges .............................................................................................. 46

4.7 "Branch table" tab ....................................................................................................................... 47 4.7.1 User interface reference.............................................................................................................. 47 4.7.2 Defining branch parts .................................................................................................................. 48 4.7.3 Adapting the legend .................................................................................................................... 51 4.7.4 Modifying the nominal diameter range........................................................................................ 51 4.7.5 Branch table for PDMS pipe specs ............................................................................................. 52 4.7.6 Miscellaneous ............................................................................................................................. 52

4.8 "Connector table" tab .................................................................................................................. 52 4.8.1 User interface reference.............................................................................................................. 52 4.8.2 Configuring the connector table .................................................................................................. 54 4.8.3 Configuring the table for special parts ........................................................................................ 54 4.8.4 Evaluation sequence................................................................................................................... 56 4.8.5 Example application in the engineering data .............................................................................. 56

4.9 "Diagram" tab .............................................................................................................................. 58 4.9.1 Content of the "Diagram" tab ...................................................................................................... 58

4.10 Other tabs.................................................................................................................................... 59 4.10.1 "Function" tab.............................................................................................................................. 59 4.10.2 "Remarks" tab ............................................................................................................................. 60 4.10.3 Other ........................................................................................................................................... 61

4.11 PipePart Finder ........................................................................................................................... 61 4.11.1 Introduction ................................................................................................................................. 61 4.11.2 Using template pipe class ........................................................................................................... 62

5 Using bolt sets ......................................................................................................................................... 63

5.1 Fundamentals of bolt sets ........................................................................................................... 63

5.2 Requirements.............................................................................................................................. 64

5.3 Workflow...................................................................................................................................... 65

5.4 Defining the strength grades of screws and nuts........................................................................ 65

5.5 Adding the bolt set to the pipe spec............................................................................................ 66

5.6 Adding screw parts to the pipe spec ........................................................................................... 66

5.7 Assigning the bolt set to a pipe part............................................................................................ 67

5.8 Bolt sets in the engineering data................................................................................................. 68

6 Miscellaneous information about pipe specs ........................................................................................... 69

6.1 Using project pipe specs............................................................................................................. 69 6.1.1 Requirements.............................................................................................................................. 69 6.1.2 Defining a project pipe spec........................................................................................................ 70

6.2 Using insulation classes.............................................................................................................. 71 6.2.1 Functional principle of insulation classes.................................................................................... 72

Table of contents


6.2.2 Insulation catalog .........................................................................................................................73 6.2.3 Workflow ......................................................................................................................................74 6.2.4 Configuring insulation classes .....................................................................................................75

6.3 Documenting pipe specs..............................................................................................................76

6.4 Creating a revision of pipe specs.................................................................................................76

7 Administration.......................................................................................................................................... 77

7.1 Administration workflow ...............................................................................................................77

7.2 Setting project properties .............................................................................................................77

7.3 Managing standard tables............................................................................................................78 7.3.1 Managing parameters ..................................................................................................................79 7.3.1.1 Note about parameter management............................................................................................79 7.3.1.2 Definition ......................................................................................................................................79 7.3.1.3 Amending parameters..................................................................................................................80 7.3.1.4 Creating a new parameter ...........................................................................................................80 7.3.2 Standard table for nominal diameters..........................................................................................81 7.3.3 Standard table for weld shapes ...................................................................................................81 7.3.4 Standard tables for screw parts and bolt sets..............................................................................82

7.4 Managing standardizations ..........................................................................................................84 7.4.1 Base object node .........................................................................................................................85 7.4.2 Requirements for working with standardizations .........................................................................85 7.4.3 Implementing a new standardization ...........................................................................................85 7.4.3.1 Workflow ......................................................................................................................................85 7.4.3.2 Adding the new standardization to the standard table for standards systems. ...........................86 7.4.3.3 Creating the new norm object ......................................................................................................86 7.4.3.4 Configuring the standardization ...................................................................................................87 7.4.3.5 Assigning the standardization......................................................................................................87 7.4.4 Configuration of the standardization ............................................................................................88 7.4.4.1 Using the standardization only once the configuration is complete.............................................88 7.4.4.2 Workflow ......................................................................................................................................88 7.4.4.3 Setting the standard unit ..............................................................................................................90 7.4.4.4 Defining the nominal diameter range...........................................................................................91 7.4.4.5 Defining the dimension range ......................................................................................................93 7.4.4.6 Adding parameters.......................................................................................................................94 7.4.4.7 Configuring the "Local Dimensions (DN1/DN2)" tab....................................................................95 7.4.4.8 Configuring the "Screw dimensions" tab......................................................................................96 7.4.4.9 Configuring the "Screw step lengths" tab ....................................................................................96 7.4.4.10 Updating the nominal diameters ..................................................................................................97 7.4.4.11 Excluded from the configuration ..................................................................................................99

7.5 Managing the standard catalog for geometry standards ...........................................................100 7.5.1 Note about managing and modifying the standard catalog for geometry standards .................100 7.5.2 Principle .....................................................................................................................................100 7.5.3 Base data ...................................................................................................................................101 7.5.4 Structure of the standard catalog for geometry standards ........................................................102 7.5.4.1 Structure objects and basic tables.............................................................................................102 7.5.4.2 Structure parameters .................................................................................................................102 7.5.4.3 Structuring by the "ParameterName" attribute...........................................................................103 7.5.4.4 Naming system ..........................................................................................................................105 7.5.4.5 The node for flange dimensions.................................................................................................106

Table of contents


7.5.4.6 The node for screw parts .......................................................................................................... 107 7.5.4.7 Attributes catalog of the standard catalog................................................................................. 109 7.5.4.8 Standard tables for the standard catalog .................................................................................. 110 7.5.5 Creating a new geometry standard or company standard........................................................ 110 7.5.5.1 Workflow.................................................................................................................................... 110 7.5.5.2 Example .................................................................................................................................... 111 7.5.5.3 Creating a standards system and standardization.................................................................... 111 7.5.5.4 Adding a standard to the corresponding standard table for standards..................................... 112 7.5.5.5 Amending the attributes catalog ............................................................................................... 112 7.5.5.6 Amending the standard catalog ................................................................................................ 113 7.5.5.7 Adding the standard to the range of values of the standardization .......................................... 115 7.5.5.8 Using the standard .................................................................................................................... 116 7.5.5.9 Creating a geometry standard or company standard for screw parts....................................... 118 7.5.6 Adding information to the "RU Standard table Parametrics" standard table ............................ 120 7.5.7 Adding EN/DIN / ANSI/ASME standards .................................................................................. 122 7.5.7.1 Creating a missing standard ..................................................................................................... 122 7.5.7.2 Supplementing values in the basic tables................................................................................. 124

7.6 Administering pipe part catalogs............................................................................................... 125 7.6.1 Structure of the pipe part catalogs ............................................................................................ 125 7.6.1.1 Naming system ......................................................................................................................... 127 7.6.1.2 Overview of the tabs and their inheritance sources.................................................................. 127 7.6.2 "VDS Part description" tab ........................................................................................................ 130 7.6.3 "VDD Part attribute" tab ............................................................................................................ 133 7.6.3.1 Control group "Pressure/temperature dependency" ................................................................. 134 7.6.3.2 Control group "Materials – List of objects" ................................................................................ 135 7.6.3.3 Control group "Technical Terms of Delivery" ............................................................................ 136 7.6.3.4 Control group "Remarks Supply Information" ........................................................................... 136 7.6.3.5 Control group "Component fabrication" .................................................................................... 136 7.6.3.6 Control group "Additional texts" ................................................................................................ 137 7.6.4 "VDM Data Sheet" tab............................................................................................................... 137 7.6.4.1 Control group "Manufacturer data" ........................................................................................... 138 7.6.4.2 NomPipeSize-Dependent Table ("V") ....................................................................................... 138 7.6.5 "StdVal Local Dimensions ..." tab ............................................................................................. 139 7.6.6 "VTX Text blocks" tab ............................................................................................................... 141 7.6.7 "VXC InterfaceCodes" tab......................................................................................................... 142 7.6.8 "SYSISO System information" tab ............................................................................................ 142 7.6.9 "CM3D Plant modeler devices" tab........................................................................................... 143 7.6.10 "DM Data Maintenance" tab...................................................................................................... 143 7.6.11 "FT Fabrication" tab .................................................................................................................. 143 7.6.12 "Nts Remarks" tab..................................................................................................................... 143 7.6.13 "E3D External 3D Interface" tab................................................................................................ 144 7.6.14 "GD 3D geometry" tab............................................................................................................... 144 7.6.14.1 General geometry attributes...................................................................................................... 145 7.6.14.2 Control group "Nominal diameter connect type straightway".................................................... 147 7.6.14.3 Dimension attributes ................................................................................................................. 148 7.6.14.4 Other attributes on the "3D geometry" tab ................................................................................ 149 7.6.15 "Display for nominal diameter range" tab.................................................................................. 150 7.6.16 Determining the pipe part geometry.......................................................................................... 152 7.6.16.1 Configuring the geometry attributes.......................................................................................... 152 7.6.16.2 Entering the calculation formula................................................................................................ 153 7.6.16.3 Using the "Define catalog access" window............................................................................... 154 7.6.16.4 Overview of the calculation formulae ........................................................................................ 155

Table of contents


7.6.16.5 The "CatStd()" function ..............................................................................................................155 7.6.16.6 The "Cat(...)" function.................................................................................................................159 7.6.16.7 The "Cat2(...)" function...............................................................................................................159 7.6.16.8 The "S(...)" function....................................................................................................................160 7.6.16.9 The "ElmS(...)" function..............................................................................................................160 7.6.16.10 The "CatExt(...)" function ......................................................................................................161 7.6.16.11 The "CatPC(...)" function.......................................................................................................162 7.6.16.12 The "Def(...)" function............................................................................................................162 7.6.17 The nominal diameter range of a pipe part................................................................................163 7.6.17.1 Validation of nominal diameter ranges ......................................................................................163 7.6.17.2 New calculation of the nominal diameter range.........................................................................163 7.6.17.3 Display nominal diameter range ................................................................................................164 7.6.17.4 Integration into existing databases ............................................................................................165 7.6.18 Expanding the pipe part catalog ................................................................................................165 7.6.18.1 Creating a new catalog ..............................................................................................................165 7.6.18.2 Creating a new pipe part............................................................................................................166

7.7 Creating a pipe part type............................................................................................................167

7.8 Managing bolt sets.....................................................................................................................168 7.8.1 Creating a bolt set......................................................................................................................168

7.9 Interaction P&ID-PPC-3D ..........................................................................................................169 7.9.1 Requirements.............................................................................................................................170 7.9.2 Technical implementation ..........................................................................................................170 7.9.2.1 Link between P&ID and PPC.....................................................................................................170 7.9.2.2 The pipe spec mapping sequence.............................................................................................171 7.9.2.3 Result of pipe spec mapping......................................................................................................171 7.9.3 Configuration workflow...............................................................................................................172 7.9.4 Configuring the standard table for P&ID function codes............................................................172 7.9.5 Configuring the standard table for PPC function codes.............................................................173 7.9.6 Configuring the project properties for P&ID-PPC-3D interaction...............................................175 7.9.7 Configuring the P&ID base objects............................................................................................177 7.9.7.1 Workflow ....................................................................................................................................177 7.9.7.2 Checking the attribute for the P&ID function code.....................................................................178 7.9.7.3 Implementing branches..............................................................................................................178 7.9.7.4 P&ID objects without function codes .........................................................................................179 7.9.8 Configuring the PPC base objects.............................................................................................179 7.9.8.1 Workflow ....................................................................................................................................179 7.9.8.2 Checking the attribute for the PPC function code......................................................................180 7.9.8.3 Retaining the request as the report object.................................................................................180 7.9.8.4 Outputting the symbol of the request on the report ...................................................................181

7.10 Configuring the PipePart Finder.................................................................................................182 7.10.1 Configuring queries....................................................................................................................182 7.10.2 Creating template pipe classes..................................................................................................183

8 Reference to the COMOS DB................................................................................................................ 185

8.1 Bolt types ...................................................................................................................................185

8.2 Algorithm for calculating the screw length .................................................................................187

8.3 Internal formulae for calculating component dimensions ..........................................................189

8.4 Properties of the example report for pipe spec documentation .................................................190

Table of contents


8.5 Properties of the example report for pipe part documentation.................................................. 191

8.6 Properties of norm objects ........................................................................................................ 191 8.6.1 "Characteristic Definition" tab.................................................................................................... 191 8.6.2 "StdVal1" and "StdVal2" tabs .................................................................................................... 195 8.6.3 "Screw dimensions" tab ............................................................................................................ 197 8.6.4 "Screw step lengths" tab ........................................................................................................... 198 8.6.5 "Screw lengths" tab ................................................................................................................... 200 8.6.6 "Washer dimensions" tab .......................................................................................................... 201 8.6.7 "Catalog Attributes" tab ............................................................................................................. 202

8.7 Properties of the objects in the standard catalog for geometry standards ............................... 205 8.7.1 The "Descriptions" tab............................................................................................................... 205 8.7.2 The "Dimensions" tab................................................................................................................ 206 8.7.3 Tabs of the geometry standards for screw parts....................................................................... 208

8.8 Properties of the pipe parts in the PPC..................................................................................... 208 8.8.1 Tabs and attributes ................................................................................................................... 208 8.8.2 Parameters dependent upon on the standards system............................................................ 209 8.8.2.1 Principle behind attributes which are dependent upon standards systems.............................. 209 8.8.2.2 Filtering parameter values of the standards system ................................................................. 209 8.8.2.3 Converting the parameter values for change of standards system .......................................... 210 8.8.2.4 Properties of a standards system attribute ............................................................................... 211 8.8.2.5 Properties of a dependent attribute........................................................................................... 212 8.8.3 GetDisplayValue() ..................................................................................................................... 213 8.8.4 Navigator description from pipe part attributes ......................................................................... 213 8.8.5 Reserved attribute names......................................................................................................... 214 8.8.6 Scripts for pipe spec mapping................................................................................................... 215 8.8.7 Inheritance of the nominal diameters and pipe spec ................................................................ 216

8.9 Properties of unit objects........................................................................................................... 220 8.9.1 General properties .................................................................................................................... 220 8.9.2 The "PSM001 Pipe spec management" tab.............................................................................. 220

8.10 Properties of P&ID objects ........................................................................................................ 221 8.10.1 "FillComboList" for the use of project pipe specs...................................................................... 221 8.10.2 Deactivating the standard check with "IsImplementationValid" and

"OnImplementationSet"............................................................................................................. 222 8.10.3 Scripts for pipe spec mapping................................................................................................... 222 8.10.4 Links for the attributes for nominal diameter and pipe spec ..................................................... 223 8.10.5 Link for the "Connector" attribute .............................................................................................. 224 8.10.6 Link for the "Nominal pressure" attribute .................................................................................. 224 8.10.7 Overview of data flow between P&ID object and PPC implementation.................................... 225

8.11 Properties of standard tables .................................................................................................... 226 8.11.1 Standard table for PPC function codes..................................................................................... 226

9 "Error analysis for 3D objects" plugin..................................................................................................... 227

9.1 Purpose..................................................................................................................................... 227

9.2 Calling the plugin....................................................................................................................... 227

9.3 The interface of the plugin......................................................................................................... 228

9.4 Checking the pipe geometry for errors...................................................................................... 232 9.4.1 Workflow.................................................................................................................................... 232 9.4.2 Displaying 3D attributes of a pipe part ...................................................................................... 233

Table of contents


9.4.3 Calculating the geometry of a pipe part .....................................................................................233 9.4.4 Error messages..........................................................................................................................234

9.5 Nominal-diameter-dependent check of the geometry................................................................235 9.5.1 Workflow ....................................................................................................................................235 9.5.2 Interrupting, resuming, or canceling the analysis ......................................................................236 9.5.3 Viewing the result of the analysis in the 3D Editor.....................................................................237 9.5.4 Switch to detail evaluation .........................................................................................................239

Table of contents



Trademarks 1Trademarks

Registered trademark: COMOS®

Trademarks



Introduction 22.1 Welcome to the PipeSpec Designer module

Purpose of the PipeSpec Designer module The technical requirements that are made to a pipe unit depends on the used fluids and the process conditions. The PipeSpec Designer is where you define all the classes you need to plan a pipe unit:

● Fluid classes (construction classes)

● Pipe specs

● Subclasses

● Insulation classes

● Classes imported from PDMS® by AVEVA

You can also define project classes.

The PipeSpec Manager component then allows you to use the classes in all aspects of pipe engineering.

The pipe parts that are assigned to the classes come from the pipe part catalog (PPC) supplied with the Comos DB. They reference a geometry standard, and thus are already equipped with the component geometry. To this end, geometry data for around 1000 components was set up in the Comos DB, complying with the geometry standards for DIN, EN, and ANSI/ASME. You can set up company standards if required.

The finished pipe spec definitions are documented in pipe spec reports; pipe parts are documented in pipe part reports.

Terminology The term pipe specs is used as a collective term in this document. In cases where information applies exclusively for a specific class type, specific mention is made of that type.

Purpose of the manual The manual provides you with a guideline for creating and managing pipe specs.

As administrator you find out what you need to do before you can start the process of creating pipe specs with the PipeSpec Designer.

Introduction 2.2 Legal notice


2.2 Legal notice

Legal position In the context of purchasing a license for a Viper product, the geometry standards are regulated as follows:

● The customer is not purchasing original documents or rights to geometry standards to DIN/EN/ISO or ANSI/ASME/ASTM and so forth.

● The standards in COMOS only contain geometry values taken from the original documents. They might contain incorrect values.

● The customer is responsible for checking the data before using it in the context of production.

● The standards in COMOS have the status of a standard "...to EN DIN <xyz>".

This means that although Siemens AG strives to supply correct data, it accepts no responsibility for data accuracy.

● Customers can set up their own geometry standards.

● The software maintenance contract grants the customer the right to receive updates to geometry standards, subject to the following conditions:

– Existing standards are not overwritten

– New geometry standards (EN 1092:2008, for example) are set up in separate nodes if necessary

– The standards are maintained in the context of project management with the assistance of the database manager

– PAS 1057 is not a geometry standard.

– As of now, the corresponding node is declared as "Draft with example structures", with the individual user having the right to enter data accordingly

– If PAS pipe specs are set up in the future, in accordance with norm 2009 without valves and fittings, data is written to the node accordingly

● COMOS Viper does not supply pipe specs which are compatible for production.

Introduction 2.3 General requirements


2.3 General requirements The following general requirements apply for working with the PipeSpec Designer:

● The properties of the current project have been fully configured.

See also chapter Setting project properties (Page 77).

● Your administrator has configured the following lists, standards and catalogs:

– Standard tables

See also chapter Managing standard tables (Page 78).

– Standardizations

See also chapter Managing standardizations (Page 84).

– Standard catalog for geometry standards

See also chapter Managing the standard catalog for geometry standards (Page 100).

– Pipe parts catalog

See also chapter Administering pipe part catalogs (Page 125).

– Bolt sets

See also chapter Managing bolt sets (Page 168).

2.4 Classes managed in the PipeSpec Designer

Pipe specs A pipe spec is a specified collection of all pipe parts that belong to a pipe. Within a pipe spec, the pipe parts assigned to a nominal pressure (PN) and pipe material are defined uniquely within a relevant configuration (dimensions and material).

A pipe spec that is defined in COMOS covers most of the constructional and design requirements for pipe engineering.

You are largely free to define the number and content of the pipe specs. You can, for example, create a subclass for valves, gaskets, fittings and flanges. Or you can include all these components in a single conventional PipeSpec.

Introduction 2.4 Classes managed in the PipeSpec Designer


A pipe spec comprises the following elements:

● Pipes

● Fittings, e.g.:

– Elbows

– Tees

– Reducers

– Branches

– Pipe connectors

– Screws

– Gaskets

● Optional:

– Valves

– Pipe supports

Fluid class In P&ID engineering, if the medium (fluid) is the determining variable for the pipe specs, you can combine a variety of classes in a single fluid class.

Example: A fluid class consisting of a pipe spec, a valve class, and a gasket class

Insulation classes See also chapter Using insulation classes (Page 71).

Project pipe specs See also chapter Using project pipe specs (Page 69).

PDMS pipe specs PDMS pipe specs imported with the "PDMS interface" COMOS plug-in are also managed in the PipeSpec Designer.

You find additional information on this topic in the "COMOS PDMS Integration" manual.

Nested classes You have the option of nesting classes. This is done by allocating a class that has already been defined (class A) to another class (class B). All components from class A are automatically available in class B and must not violate the defaults defined in class B. See also chapter The pipe part table (Page 38).


Getting started 33.1 Opening the PipeSpec Designer

Call Select the command "Administrator > Base data > Pipe specs" in the menu bar.

With the exception of project-specific pipe specs, all pipe specs are managed in the base project.

Result The "Pipe spec administration" tab of the PipeSpec Designer opens in the working area. The tab is empty because you have not loaded any pipe specs yet.

See also The PipeSpec Designer interface (Page 18)

Getting started 3.2 The PipeSpec Designer interface


3.2 The PipeSpec Designer interface

Structure The content of the PipeSpec Designer is determined by whether or not you have previously loaded a pipe spec:

● Interface without pipe spec loaded:

● Interface with pipe spec loaded:

Getting started 3.3 The "Load pipe spec" window


Control elements on the interface:

Number Control element Function

① "Pipe spec" field The pipe spec loaded in the PipeSpec Designer The field is empty when the PipeSpec Designer is first opened.

② Button Opens a list of all pipe specs you loaded during the COMOS session.

③ "…" button Opens the "Load pipe spec" window.

④ Tabs Tabs for configuring the pipe spec The area is empty when the PipeSpec Designer is first opened.

⑤ ">" button Button for scrolling through the tabs if your COMOS window is too small to display all of the tabs in the PipeSpec Designer.

⑥ - The content of the tab you have activated. See also chapter Tabs of the PipeSpec Designer (Page 24).

The area is empty when the PipeSpec Designer is first opened.

3.3 The "Load pipe spec" window The "Load pipe spec" window is where you create a new pipe spec and load it in the PipeSpec Designer so that it can be edited. Alternatively, you can load an existing pipe spec for editing in the PipeSpec Designer.

Call To open the "Load pipe spec" window, click the "..." button next to the "Pipe spec" field on the "Pipe spec administration" tab.

3.3.1 The interface of the "Load pipe spec" window The "Load pipe spec" window is divided into two areas:

Upper area The fields "Name" and "Description" display the name and the description of the node currently selected in the lower area.

Lower area The lower area is where you create a new pipe spec (in a structure tree) or select an existing pipe spec for loading in the PipeSpec Designer.

Getting started 3.4 Loading an existing pipe spec


Dependent upon whether you are working in the base project or in the engineering project, you will see one or two tabs:

● Base project: "Current project" tab

● Engineering project: "Base project" tab and "Engineering project" tab

"Current project" and "Base project" tabs The structure tree shows the node entered in the properties of the base object as the root node for the pipe spec definition.

This is where you define the basic classes/system classes.

Basic classes/system classes are created in the base project. They are available on a project-wide basis. They can be used as templates for project-specific pipe specs.

In engineering projects, basic classes/system classes are write-protected.

"Engineering project" tab The structure tree shows the node entered in the properties of the engineering project as the root node for the pipe spec definition.

This is where you define the pipe specs created locally in an engineering project. They are marked as local base objects in the structure tree.

You find more information on this topic in the "Basic Operation" manual, keyword "Additional object elements".

If the same node is entered in the engineering project as in the base project, you also see the basic classes/system classes.

3.4 Loading an existing pipe spec

Requirements A pipe spec has previously been created.

Procedure 1. Open the "Load pipe spec" window.

2. If you are working in an engineering project:

– To load a pipe spec created in an engineering project, select the "Engineering project" tab.

– To load a basic class/system class, select the "Base project" tab.

Note

Basic classes/system classes are write-protected in the engineering project.

Getting started 3.5 Creating a new pipe spec


3. If you are working in the base project, only the "Current project" tab is available to you. It shows the basic classes/system classes.

4. Select the required pipe spec in the structure tree.

5. Click the "OK" button.

3.5 Creating a new pipe spec

Principle You have the following options to create a new pipe spec:

● If you use a template, make a copy of an existing pipe spec and modify it according to your needs.

● If the new pipe spec differs considerably from the existing pipe spec, create a completely new pipe spec without template.

Requirements If you want to modify a pipe spec, it must have been created already.

Modifying a copy 1. Open the "Load pipe spec" window.

2. In the structure tree, select the pipe spec to be used as a template.

3. Select the "Copy" command in the context menu.

4. If you are working in an engineering project and the selected template is a basic class/system class, go to the "Engineering project" tab.

5. Select the root node in the structure tree followed by the "Paste" command from the context menu.

Result:

– A copy of the pipe spec is created in the structure tree and the base data.

– The name and description are generated for the new pipe spec.

6. Edit the automatically generated name and the description in the upper area of the "Load pipe spec" window to meet your needs.


Working without a template 1. Open the "Load pipe spec" window.

2. In the structure tree, select the node under which you wish to paste the new pipe spec.

Getting started 3.5 Creating a new pipe spec


3. Select one of the following commands from the "New" context menu:

– "…> COMOS pipe spec":

Creates the new pipe spec. Opening the pipe spec in the PipeSpec Designer loads all tabs relevant for pipe specs.

– "…> PDMS pipe spec":

Creates the new PDMS pipe spec. Opening the pipe spec in the PipeSpec Designer loads all tabs relevant for PDMS pipe specs.

The new pipe spec is created in the structure tree and the base data.

4. Edit the automatically generated name and the description.


Result The "Load pipe spec" window closes and the new pipe spec is loaded in the PipeSpec Designer.

Getting started 3.6 Naming pipe specs


3.6 Naming pipe specs

Definition The name of a pipe spec is composed of the following elements:

● The nominal pressure (PN) in accordance with DIN 2401 Sheet 1

● The ID character in accordance with DIN 2406 of the pipe materials group

ID character Materials group A Cast iron B Unalloyed steel C Heatproof steel D Heat-resistant steel E Compressed gaseous hydrogen-resistant steel F Low-temperature (carbon/alloy) steel G Surface-treated steel H Stainless steel K Non-ferrous metals L Plastics M Concrete N Ferroconcrete P Reinforced concrete Q Asbestos cement R Ceramics Z Other materials

● The pipe spec number (counter) that labels the series of pipe parts that have been assigned to one another

Examples "16B001" = unalloyed steel PN 16 flanged parts

"40H101" = stainless steel PN 40 threaded parts

3.7 Deleting pipe specs Do not delete pipe specs which are used in the engineering data.

Getting started 3.8 Creating folders for structuring pipe specs



2. Select the required pipe spec in the lower part of the window.

3. Select "Delete" from the context menu.

3.8 Creating folders for structuring pipe specs


2. In the structure tree, select the node under which you wish to paste a folder.

3. Select the "New > Folder" command in the context menu.

3.9 Tabs of the PipeSpec Designer

Overview Once you have loaded a pipe spec in the PipeSpec Designer, you see additional tabs in the "Pipe spec administration" tab.

Displaying a tab in an additional window

Use the button to display a tab of the PipeSpec Designer in an additional window. The additional window does not have additional functions but simplifies the configuration of the tabs.

Tabs Tab Restriction Description "Components" - Here you determine which pipe parts are members of the

pipe spec. "Nominal diameters"

- Here you define the nominal diameter range within which the pipe parts are available in the pipe spec.

"Selector" For PDMS pipe specs only

Here you manage the selectors.

"Branch table" - Here, based on the nominal diameter combinations, you determine which branch part is used if pipes are interconnected directly when constructing branches.

Getting started 3.9 Tabs of the PipeSpec Designer


Tab Restriction Description "Connector table" For COMOS pipe

specs only Here you determine which additional pipe parts are to be generated in the engineering data (for example, when working on an isometric drawing or with the Plant Modeler interface) when placing a pipe part. The table has a regulatory character. Example: Generation of counterpart flanges, gaskets, and weld seams when placing a valve.

"Diagram" - Here you find a diagram for the pressure/temperature rating of the pipe parts.

"Characteristics" - Here you determine the characteristics of the pipe spec. "PipeSpec limits" - Here you determine the application limits of the pipe spec. "Remark" - Here you can input additional information that documents

the pipe spec (optional). Supporting function. "Function" - Data for internal purposes is stored here. "External 3D Interface"

For PDMS pipe specs only

Here you make the settings that are required to export the pipe spec to PDMS.

Administrators can create additional user-defined tabs at the base object of the pipe spec which you are then also able to see in the PipeSpec Designer. See also chapter Configuring the pipe spec (Page 27).

Getting started 3.9 Tabs of the PipeSpec Designer



Configuring the pipe spec 44.1 Workflow

Configure the tabs in the following order:

1. "PipeSpec limits"

2. "Characteristics"

3. "Components"

4. "Nominal diameters"

5. "Branch table"

6. "Connector table"

7. If required: "Remark"

Preconfigured tabs ● "Diagram":

The PipeSpec Designer evaluates data configured at the pipe components and displays it on the tab. A configuration is not required.

● "Function":

The tab has already been configured in the COMOS DB.

4.2 Requirements ● You have loaded a pipe spec in the PipeSpec Designer.

See also chapter Loading an existing pipe spec (Page 20).

● The general requirements for working with the PipeSpec Designer have been met.

See also chapter General requirements (Page 15).

Configuring the pipe spec 4.3 "PipeSpec limits" tab


4.3 "PipeSpec limits" tab Name "C2" Description "PipeSpec limits" Inheritance source "@VIPER > @Y > @PC > C2 PipeSpec limits" Function Here you assign a standardization to the pipe spec. Afterwards, you refine and

supplement the application limits specified by the norm object.

4.3.1 Assigning a standardization

Procedure 1. Select the standardization for the pipe spec in the "Standard" field.

2. Save your entry.

Result The definition of the class and its components must be within the limits specified by the standardization.

Properties of the "Standard" attribute Attribute name "VSTD" Description "Standard" Standard table "@3D > 01 > NSYS Standards system" Script block "NormRootCDevice" Apply COMOS DB implementation: "@VIPER > @Y > @PC

> C2 > VSTD Standard"



4.3.2 Defining the nominal diameter range You are working in the "Nominal diameter range" control group.

Procedure To refine the nominal diameter range specified by the standardization for the pipe spec, proceed as follows:

1. Further refine the lower and upper limits defined by the standardization in the fields "From nominal diameter" and "To nominal diameter".

2. To filter individual values from the nominal diameter range, click the button:

A list of all nominal diameters meeting the following criteria is displayed:

– They are between the upper and lower limits defined in Step 1

– They are in the nominal diameter range of the standardization

There is an option on the left of each nominal diameter value.

3. To exclude a nominal diameter from the nominal diameter range of the pipe spec, deactivate the option next to the nominal diameter.

4. To add a nominal diameter to the nominal diameter range of the pipe spec, activate the option next to the nominal diameter.

5. After definition of the nominal diameter range, click the "Update NDs" button.

The nominal diameter range you defined is forwarded to:

– The rest of the tabs in the PipeSpec Designer

– The pipe spec elements

The pipe spec elements are available in the nominal diameter range specified by the pipe spec.

Note

Do not click on the "Update NDs" button again once you have entered values in the characteristics table relating to the nominal diameters on the "Characteristics" tab.

Reason: Updating the NDs can mix up the existing assignments between nominal diameters and other characteristics.

6. Save your entries.



Properties of the "From nominal diameter" and "To nominal diameter" attributes Name "NDMIN", "NDMAX" Description "From nominal diameter", "To nominal diameter" Standard table "@3D > 01 > 05 Nominal diameters" Script block "FillComboList"

Together with the "DependedSpecs" function of the "VSTD" attribute, the script block ensures that only values within the value range of the standardization are available for selection. The underlying principle is the same one used for attributes in the pipe part catalog which are dependent upon standards systems, where the dependent attributes implement the "FilterRow" function that fulfills the same purpose. Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PC > C2 > NDMIN" or "NDMAX"

Properties of the filter attribute Name "VC11" Description - Standard table "@3D > 01 > 05 Nominal diameters" Script block "FilterRow"

The script block ensures that the values displayed in the filter list constitute the intersection set of values from the current nominal diameter range of the standardization and the values specified in the pipe spec by "From nominal diameter" and "To nominal diameter". Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PC > C2 > VC11"

Properties of the "Update NDs" button Name "Update" Description "Update NDs" Script block "OnClick"

The script block forwards the current nominal diameter range: – PipeSpec Designer, "Characteristics" tab: To the nominal-diameter-

dependent characteristics table "V1 Characteristics" – PipeSpec Designer, "Branch table" tab The branch table reads its nominal

diameters from the nominal-diameter-dependent characteristics table. This updates the nominal diameter combinations displayed in the branch table.

– Pipe spec elements: Only nominal diameters from the current nominal diameter range of the pipe spec will be available at the pipe parts.

Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PC > C2 > Update"

An example of the content and updating of the nominal-diameter-dependent characteristics table appears in Defining nominal-diameter-dependent parameters (Page 36).

See also Principle behind attributes which are dependent upon standards systems (Page 209)



4.3.3 Defining the use limits of the pipe spec The table for the pressure/temperature rating in the "Class use limit" control group is used for pipe spec documentation. It is informational in character and independent of the pressure/temperature rating of the pipe parts.

The values entered here are evaluated on the "Diagram" tab and displayed in a diagram.

Procedure 1. In the "Temperature Range <°C>" row, enter a minimum and a maximum temperature in

the "Min" and "Max" columns.

2. In the "Pressure Range <bar>" row, specify the nominal pressure that can be used without any restrictions for the temperature range that has been set above.


Example

Blue line: Rating curve Red line: Impermissible rating point of the component Green line: Permissible rating point of the component

Note

If you are using fluid (construction) classes, you must make sure that the subordinate class complies with the use limits of the superordinate class. An automatic data comparison does not take place. If you require automatic data reconciliation, you must implement this using a script.

For example, a valve class must comply with the requirements of its superordinate subclass, and a subclass likewise with the requirements of its fluid class.

Properties of the table Name "V2" Description "Rating" Columns "P Pressure Range "

"T Temperature Range"



4.3.4 Defining the use limits of media You are working in the "Medium" table of the "Medium use limit" control group. The table is used for pipe spec documentation and is purely informational in character.

Here you define the pressure/temperature rating of the medium based on various properties.

Note Comparing pipe part and pipe spec ratings

You can adapt the PipeSpec Designer so that the ratings for the pipe spec elements are tested against the pipe spec rating. Contact your customer service agent if you have any questions.

Procedure 1. For each row, define the pressure/temperature rating for a property, for example, the

"liquid" and "gas" properties.

2. Enter the temperature and the pressure in the "Temp<Counter>" and "Pres<Counter>" columns.


Properties of the table Name "V3" Description "Media"

4.3.5 Defining the outer diameter and wall thickness In the "Characteristics series" of the "Characteristics" tab, the values in the "Outer Diameter" and "Wall Thickness" columns are either entered by the user or taken from the standard catalog for geometry standards.

If the characteristics are to be taken from the standard catalog, specify which basic table is to be used on the "PipeSpec limits" tab.

Requirements "Characteristics" tab, "BOX100 Class Parameter Nominal-diameter-dependent" attribute: "OnShow" script block is implemented as in the COMOS DB. See also chapter Defining nominal-diameter-dependent parameters (Page 36).



Procedure 1. Click on the "..." button on the right of the "Catalog name for outer diameters" or "Catalog

name for wall thicknesses" field.

2. Select a basic table in the catalog.

See also chapter Structure of the standard catalog for geometry standards (Page 102).

3. Click "OK" to confirm.

A pointer to the basic table is entered in the "Catalog name <...>" field.

4. In the "Construction type" list, select the column of the basic table from which the dimension value is to be read.


Result The values are read from the basic table and written to the nominal-diameter-dependent characteristics table of the "Characteristics" tab.

Properties of the attributes Name "ADCat" Description "Catalog name for outer diameters"

Name "WDCat" Description "Catalog name for wall thicknesses"

Name "VS003" Description "Construction type" Standard table "@3D > 01 > 09 Outer diameter" Script block "FilterRow"

The script filters the available values based on the settings of the standardization.

Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02 > VS03"

Script block "GetDisplay-Value"

The script sets the value entered in the "Value 4" column of the standard table as the DisplayValue .

Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02 > VS03"

Configuring the pipe spec 4.4 "Characteristics" tab


Name "VS501" Description "Construction type" Script block "FillComboList"

Ensures that the columns from the basic table are displayed in the list. Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PC > C2

> VS501"

4.4 "Characteristics" tab Name "C1" Description "Characteristics" Inheritance source "@VIPER > @Y > @PC > C1 Characteristic" Function Here you determine additional characteristics of the pipe spec. For example,

define which nominal-diameter-dependent characteristics the pipe spec gives.

4.4.1 Defining the fluid parameters of the pipe spec You are working in the "Class fluid parameters" control group.

Procedure 1. Select the fluid type, the fluid key, and the fluid substance of the pipe spec.


Properties of the attributes Name Description Standard table "VS02" "Fluid Type" "VS03" "Fluid Key" "VS05" "Medium"

The corresponding standard tables under "@3D > 01 > 00 Fluid Management"

4.4.2 Defining the fluid group according to the PED You are working in the "Fluid group acc. to DGRL" control group ("DLRG" = pressure equipment directive). The control group is used for pipe spec documentation.



Procedure 1. Select a fluid group.


List properties Name "VS01" Description "Fluid group" Standard table "@3D > 01 > 00 > 02 Fluid groups (DGR)"

4.4.3 Defining other characteristics of the pipe spec You are working in the "Class parameters" control group.

Procedure 1. Select a material in the "Pipe material" field.

The corresponding material number is automatically transferred to the "WNr" attribute.

2. Enter the material density in the "Material density" field. The material density can be used for further calculations.

3. Select the primary contact face in the "Contact face" field.

4. Select the strength grade of screws in the "Strength grade screws" field and the strength grade of nuts in the "Strength grade nuts" field.


Properties of the attributes Name "L07" Description "Pipe material" Standard table "@3D > 01 > 07 Materials" Script block "OnChange"

The script evaluates which standard table entry has been selected and writes "Value 3" of this entry to the "WNr" attribute.

Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02 > L01"

Name "L08" Description "WNr" Standard table "@3D > 01 > 07 Materials"



Name "V4" Description "Material density"

Name "VS04" Description "Contact face" Standard table "@3D > 01 > 06 Contact faces" Script block "FilterRow"

The script filters the standard table so that only entries defined by the standardization are listed for selection.

Apply COMOS DB implementation: "@VIPER > @Y > @3D >@PP > 02 > VS04"

Name "VS06" "VS07" Description "Strength grade screw" "Strength grade nuts" Standard table Under "@3D > 01 > 19 > 03 Strength grades"

4.4.4 Defining nominal-diameter-dependent parameters In the "Classes characteristics nominal-diameter-dependent" control group define the nominal-diameter-dependent characteristics in a table.

The table is used for pipe spec documentation.

Exception: You enter pipe-spec-dependent outer diameters and wall thicknesses in a table and a pipe spec element is assigned its outer diameter and wall thickness via the calculation formula "CatPC". In this case, the pipe spec element uses the local dimensions of the pipe spec and the table is purely informational in character.

Requirements ● Do not configure the table until you have finished defining the nominal diameter range on

the "PipeSpec limits" tab.

Reason: Clicking on the "Update NDs" button to forward new values can mix up the assignment between nominal diameters and other parameters.

● Do not configure the "Nominal diameter range" row manually.

Reason: The "Nominal diameter range" row must always show the nominal diameter range defined on the "PipeSpec limits" tab.

When you click the "Update NDs" button on the "PipeSpec limits" tab, the current nominal diameter range is written to the characteristic-dependent table. This can mix up the assignment between nominal diameters and the other characteristics.



Procedure Enter the characteristics depending on the nominal diameter.

You have two options when configuring the "Outer Diameter" and "Wall Thickness" columns:

● Take the values from a basic table. To do this, create a pointer from the "PipeSpec limits" tab to a basic table, and specify a construction type.

● Enter the outer diameter for the pipe specs involved manually.

When you create a pointer from the "PipeSpec limits" tab to a basic table, and specify a construction type, your entries are overwritten.

Table parameters Column name Function "Nominal diameter range"

The nominal diameter range of the pipe spec Do not set manually

"Outer Diameter" Is evaluated if a pipe spec element gets the outer diameter via the "CatPC" formula

"Wall Thickness" Same as "Outer Diameter" "Wall thickness calculated"

Calculated by PROBAD in the case of a connection to PROBAD

"Minimum wall thickness" For COMOS Inspection "Corrosion allowance" For the nominal wall thickness "Minimum pipe length" For constructing with COMOS Isometrics and COMOS Plant Modeler "Adjusting length for x,y,z"

For constructing with COMOS Isometrics

"Bending radiuses" Self-explanatory.

Properties of the attributes Name "BOX100" Description "Class Parameter Nominal-diameter-dependent” Script block "OnShow" The script checks whether the following attributes are set:

– "C2.ADCat Catalog name for outer diameters" and "C2.VS003 Construction type"

– "C2.WDCat Catalog name for wall thicknesses" and "C2.VS501 Construction type"

If yes, it writes the values from the basic table to the "Outer diameter" and "Wall thickness" rows.

Values entered manually by the user are overwritten. Apply COMOS DB implementation: "@VIPER > @Y > @PC > C1

> BOX100"

Configuring the pipe spec 4.5 "Components" tab


Name "V1" Description "Characteristics" Column names and descriptions

"ND Nominal diameter range" "DA Outer Diameter" "S Wall Thickness" "SCLAC Wall thickness calculated" "KORR Corrosion allowance" "MINPIPE Minimum pipe length" "PL Adjusting length for x,y,z" "BEND Bending radiuses"

See also The "CatPC(...)" function (Page 162)

Defining the outer diameter and wall thickness (Page 32)

Defining the nominal diameter range (Page 29)

4.5 "Components" tab Description "Components" Inheritance source The tab is generated by the PipeSpec Designer. Function Here you define the pipe spec elements of the pipe spec and the upper and

lower limits of its nominal diameter range.

4.5.1 The pipe part table The pipe part table provides an overview of and a means of managing the pipe spec and/or its elements.

Underlying query The pipe part table is based on a query with the name "PCL" which must be located in the base data below the node "@System > @O > @PCL Oberfläche".

A deleted query is automatically recreated when you open the PipeSpec Designer. If columns are missing, they are also recreated.

The query defines which columns the pipe part table has.



Structure of the pipe part table The query preconfigured in the COMOS DB defines the following columns:

● Column for the pipe part type:

Groups the pipe spec elements into pipe part types by function code range.

See also section Creating a pipe part type (Page 167).

● Columns "Function code" and "Function":

Reads out the function code of the pipe part (numerical code and description).

● "Name":

The pipe spec element is initially assigned the name of the pipe part from the pipe part catalog. The name can be overwritten. It must be unique.

● "Description":

As with "Name".

● "Nominal diameterh from" and "Nominal diameter to":

Defines the nominal diameter range in which the pipe spec element is available in the pipe spec. Only nominal diameters from the current nominal diameter range of the pipe spec can be selected.

● "Branch parts":

This option is activated by default for pipes and branch parts depending on the function code. These components are copied to the branch table.

"Recursive on pipe specs" option This option is relevant when you are working with nested pipe specs.

Option Description disabled The following objects are visible in the pipe part table:

The pipe spec elements you assigned directly to the pipe spec loaded in the PipeSpec Designer.

The base object of the nested pipe spec.

Activated An additional column appears in the pipe part table: The "Pipe class" column which reads out the name of the pipe spec under which a pipe part is located in the base data.

The table lists the same objects as when the option is deactivated, plus the members of the nested pipe spec.



"Show filtered object query" option Option Description disabled Conventional creation of pipe spec with drag&drop Activated If you have prepared filtered queries for a pipe spec, the results are displayed in

the upper area of the "Pipe parts" tab. You can drag the pipe spec elements to the lower area with drag&drop and add it to the pipe spec. See also chapter Configuring queries (Page 182).

4.5.2 Assigning a new pipe part

Requirements ● The "Base objects" tab is open in the Navigator.

● The pipe part catalog is open.

Procedure 1. Select the desired pipe part in the Navigator.

2. Drag&drop it from the Navigator to the pipe part table.

3. Save.

Result ● A new base object is created in the base data under the pipe spec. The pipe spec

element

● The pipe spec element has a base object pointer to the pipe part from the pipe part catalog. This means that it inherits from the catalog part.

● The pipe spec element also has the "C2 limit pipe spec. component" tab. It stores data for the nominal diameter range of the pipe spec element. Inheritance source: "@VIPER > @Y > @PCOM > PCOM > C2"

Nested classes To embed one pipe spec in another pipe spec, drag&drop the corresponding base object from the Navigator to the "Components" tab.

4.5.3 Navigating to the pipe part You can navigate from the pipe part table to the base data.



Procedure 1. Select the pipe spec element in the pipe part table.

2. Select the following command from the context menu:

– To navigate to the pipe spec element: "Navigate - pipe spec"

– To navigate to the pipe part in the pipe part catalog on which the pipe spec element is based: "Navigate - original"

4.5.4 Setting the upper and lower limits of the DN range of a pipe part

Procedure 1. Select the pipe part in the pipe part table.

2. Define the lower limit in the "Nominal diameter from" column and the upper limit in the "Nominal diameter to" column.


Result The pipe spec element is only available within the upper and lower limits defined here. The upper and lower limits are saved at the pipe spec element in the following attributes: "C2.NDMIN" and "C2.NDMAX"

Excluding nominal diameters from the nominal diameter range On the "Nominal diameters" tab, you can exclude individual values from the range defined by "Nominal diameter from" and "Nominal diameter to".

See also "Nominal diameters" tab: (Page 42)

4.5.5 Adding a component to the branch table

Procedure 1. Add a new component from the pipe part catalog to the pipe part table.

2. Select the option in the "Branch parts" column for this component.

3. Specify the permitted nominal diameter combinations.

Configuring the pipe spec 4.6 "Nominal diameters" tab:


Result The component is displayed in the "Branch parts" tab as preselected component.

Removing components from the branch table 1. Select a branch pipe part in the pipe part table.

2. Deselect the option in the "Branch parts" column.

Resetting to standard selection of branch parts Select the command "Reset branch parts to standard" in the context menu of the table.

4.6 "Nominal diameters" tab: Description "Nominal diameters" Inheritance source The tab is generated by the PipeSpec Designer. Function Shows the permitted nominal diameters of the pipe spec elements and their

classification to pipe part types. Here you define a preselected component for each nominal diameter for each pipe part type. You can also refine the nominal diameters in which a pipe part is available.

4.6.1 Preselected components

Definition Preselected components are those pipe parts returned by COMOS as standard values when the pipe part type is addressed.

Example: A user is working on an isometric drawing and places a pipe part using the symbol bar of the isometric drawing. The user selects a pipe part type and places the pipe part that is set as preselected component for the pipe part type and the selected nominal diameter.

4.6.2 User interface reference

Structure The "Nominal diameter" tab contains a tab for each pipe part type. They are sorted by names (function code) of the pipe part types.



All tabs have the same structure and are divided into two areas:

● Upper area: For setting the preselected components

● Lower area: For refining the permissible nominal diameters of the pipe parts

The upper area Element Function Details Title The title tells you which display mode is

active See the "Show all components" option

Table The table shows which pipe parts are always available for a nominal diameter.

Here you set a preselected component for each nominal diameter

The table has two rows: Upper row:

The current nominal diameter range of the pipe spec Lower row:

Content depends upon display mode

See the "Show all components" option (deactivated) For pipe parts with two nominal diameters you see a cross-classified table.

"Show all components" option

The option controls the display mode of the table and, therefore, the content of the lower table row.

Option activated: "Existing components" display mode The lower row of the table shows all pipe parts available for

each nominal diameter. The legend descriptions of the pipe parts are displayed. The

color code is omitted. Option deactivated: "Preselected component" display mode The lower row of the table shows only the preselected

component set for each nominal diameter.

If you have not yet specified a preselected component, COMOS selects the pipe part with the lowest function code which is available for the nominal diameter.

The legend description of the preselected component is displayed. The cell color corresponds to the color code.

The lower area The table in the lower area meets the following functions:

● Provides an overview of the nominal diameters in which the pipe parts of the pipe part type are currently available.

● Provides an overview in which nominal diameters the pipe parts of the pipe part type are basically permitted.

● Changing the nominal diameter of the pipe parts.



The table is structured as follows:

● Left column: The legend descriptions of the pipe parts

● The remaining header columns: The current nominal diameter range of the pipe spec

Each row describes the nominal diameter range of a pipe part:

● White cell with check mark: The nominal diameter is currently available.

● White cell without check mark: The nominal diameter is always available.

● Gray cell: This nominal diameter cannot be within the nominal diameter range.

Context menus The context menu for the upper table contains the following entries:

● A list of all pipe parts which are available as preselected components for the current nominal diameter

● "Legend"

The context menu for the lower table contains the following entries:

● "Select"

● "Deselect"

● "Navigate"

See also Creating a pipe part type (Page 167)

Adapting the legend (Page 51)

Refining nominal diameter ranges (Page 46)

Defining preselected components (Page 45)



4.6.3 Defining preselected components

Procedure 1. Click the tab for the required pipe part type on the "Nominal diameters" tab.

The table listing the preselected components and the table for the nominal diameter ranges of the pipe parts are displayed.

2. Get an overview of which pipe parts can be set as preselected components for the nominal diameter. You have two options:

– Activate the "All components" option in the upper table.

The legend descriptions of all available pipe parts are displayed in the cell for the required nominal diameter.

– Check the lower table to see which pipe parts are available for the nominal diameter.

3. If you only wish to define a preselected component for one nominal diameter, proceed as follows:

– To display a list with all pipe parts that are available as preselected component for the current nominal diameter, open the context menu in the required cell of the upper table.

– Select a pipe part.

The pipe part is set as the preselected component.

– If the option "All components" is activated, deactivate the option to change into the display mode for preselected components.

4. To assign the same preselected component to several nominal diameters, proceed as follows:

– Press and hold down <Ctrl>, hold down the left mouse button, and drag out an area around the required nominal diameters in the upper table.

– To display a list of pipe parts which are available as preselected components for all selected nominal diameters, open the context menu.

– Select a pipe part from the list.

The pipe part is set as the preselected component.


Modifying the nominal diameters of a pipe part In the lower table, you can modify the nominal diameters in which the pipe parts are available. This means that you can even set pipe parts as preselected components which are not available as preselected components initially due to their nominal diameter range.

See also Refining nominal diameter ranges (Page 46)



4.6.4 Refining nominal diameter ranges

Introduction The nominal diameter range of a pipe spec element is formed by the average of the following quantities:

● The nominal diameter range of the pipe part from the pipe part catalog on which the pipe spec element is based.

● The nominal diameter range of the pipe spec.

In the PipeSpec Designer, you can further refine the nominal diameter range calculated in this way and define which nominal diameters are actually available.

Procedure 1. Select the tab of the pipe part type on the "Nominal diameters" tab.

You are working in the table for the nominal diameter ranges, in the row displaying the nominal diameter range of the pipe part.

The pipe parts are displayed with their legend description.

2. Optional: Open the legend in the table for preselected components and identify which legend description and color stands for which pipe part. See also chapter Defining preselected components (Page 45).

3. To exclude a nominal diameter, double-click a white cell with check mark.

The check mark disappears.

4. To add a nominal diameter once again, double-click a white cell.

A check mark appears in the cell.


Result ● The nominal diameter range is saved as an XML string at the base object of the pipe

spec element: "C2 PipeSpec limits" tab, "NDRange" attribute

● When the pipe spec is mapped, the pipe spec element is only available in the nominal diameter range defined in the XML string.

● If you have modified the upper or lower limit, the "Components" tab is updated accordingly.

Attribute for the nominal diameter range of a pipe spec element You will only find the attribute saving the nominal diameter range in the Navigator. The attribute is not placed on the "C2" tab.

You can embed the XML string on a tab. See also chapter Display nominal diameter range (Page 164).

Configuring the pipe spec 4.7 "Branch table" tab


See also The nominal diameter range of a pipe part (Page 163)

"Display for nominal diameter range" tab (Page 150)

4.7 "Branch table" tab Description "Branch table" Inheritance source

The tab is generated by the PipeSpec Designer.

Function Here you specify which branch part is used if pipes are interconnected directly when constructing branches. A unique entry is set for each nominal diameter combination. The table is not evaluated if you have already placed a branch part when constructing the branch. In this case, the component set as the preselected component for the pipe part type of the branch part is used.


Structure The "Branch table" tab is divided into two areas.

Upper half:

● The branch table and some options for controlling the display of the table and filtering its content.

● Purpose:

If pipes are interconnected directly during construction, you specify here which branch part is used based on the nominal diameter.

Lower half:

List of branch parts with legend. Use the [...] button to open the nominal diameter range.

Content of the upper half ● The branch table is a cross-classified table containing the nominal diameter combinations

of the pipe spec. It is generated from the nominal diameters entered on the "Characteristics" tab in the nominal-diameter-dependent characteristics table of the pipe spec.

– Horizontal axis: The nominal diameter of the branch

– Vertical axis: The main nominal diameter

● Each nominal diameter combination is stored with a list of all branch parts permitted for this nominal diameter combination.



● Either the names or the legend descriptions of the branch parts are listed in the branch table. The following options control the content and the display of the table:

Option Description "Show name" Shows the names of the branch parts. "Show legend" Shows a legend defined by the user (number or letters). "Show all available components" Shows all branch parts that are permitted for a nominal

diameter combination. "Only show preselected component" Shows only those branch parts that were set as

preselected components in the table.

● Each branch part is assigned a color. If you set a preselected component for a nominal diameter combination, the cell is displayed in the color assigned to the preselected component.

Content of the lower half Legend:

Column Description "Pipe spec element" Name and Navigator text of the branch parts

Shows the branch parts for which the option in the "Branch part" column on the "Pipe parts" tab is selected.

"Legend" The currently assigned legend description "Color" The currently assigned color "ND Range" Button that opens the nominal diameter table

Offered branch parts A pipe part will then only be displayed on the tab if it has been assigned to the pipe spec and meets one of the following requirements:

● Its function code is between "10011" and "11999" or between "71000" and "71999".

● The "GD.BranchPP" attribute of the "Checkbox" type is created at the pipe part with the value "1" (object allowed).

See also Modifying the nominal diameter range (Page 51)

Defining branch parts ()

Miscellaneous (Page 52)

4.7.2 Defining branch parts You are working in the branch table.



Requirements ● Display mode is "Only show preselected components".

● Branch parts have been assigned to the pipe spec.

Principle You have the following options to determine the branch parts:

● Assigning a branch part to each individual nominal diameter combination

● Assigning the same branch part to several nominal diameter combinations at once

● Applying the preselected components set on the "Nominal diameters" tab for all nominal diameter combinations

● Not assigning a branch part so that the default preselected component is used

● Using the option in the "Branch parts" column on the "Pipe parts" tab.

Assigning a branch part to a nominal diameter combination 1. Double-click the cell of the required nominal diameter combination.

The list stored in the cell is activated.

2. Open the list by clicking on the arrow button.

3. Select a branch part from the list.


When you connect a branch to a pipe and the nominal diameters of the pipes correspond to the nominal diameter combination you have selected, the set branch part is used.

Defining a branch part for multiple nominal diameter combinations at the same time 1. To select the cells, hold down <Ctrl> and drag out a rectangle covering the desired

nominal diameter combinations while holding down the left mouse button.

2. Select a branch part from the context menu.

When you select an invalid branch part, the window "Selected component is not valid for all nominal diameter combinations" opens.


Applying preselected components In the branch table, open the context menu and select "Set preselected components".



Result

● COMOS checks on the "Nominal diameters" tab of the pipe part type tee (function code 71XXX) for which nominal diameter combinations preselected components have been set and applies them in the branch table.

● In the absence of a matching tee, COMOS looks for a permitted branch part with multiple nominal diameters (function code range between 10011 and 11999) whose "GD.BranchPP" attribute is set to a value of "1" and uses it.

Using the standard branch If you do not use the branch table or do not enter a branch for a certain nominal diameter combination, COMOS uses the component set as the preselected component for the "71XXX" pipe part type. This is usually a tee, provided that the pipe spec contains a tee.

If COMOS is not able to find a preselected component, the first pipe part of the pipe spec with function code 711XX is offered as a branch part in the pipe spec mapping in accordance with the nominal diameter.

Invalid branch part selected If you assign a branch to multiple nominal diameter combinations at once, the branch you have selected might not be valid for all nominal diameter combinations. In this case, you define how COMOS should proceed for these nominal diameter combinations in the "Selected component is not valid for all nominal diameter combinations" window.

Activate one of the following options:

● "Apply value with error":

The pipe part is entered as the branch part, even though it is invalid. The text is displayed in red.

● "Use preselected component":

Instead of the invalid component, the preferred component is set.

● "Set value to empty":

A branch part is not set.

● "Cancel action":

Aborts the process.



4.7.3 Adapting the legend A character code and a color are assigned to every branch part.

Procedure 1. To assign a new legend description, proceed as follows:

– Double-click in a cell of the "Legend" column.

– Enter the new description in the cell.

2. To assign a new color, proceed as follows:

– Click with the left mouse button in a cell in the "Color" column.

– Select a new color in the "Color" window.

3. To save your entries, click the "Close" button.

4.7.4 Modifying the nominal diameter range The configuration of the nominal diameter range on the "Branch table" tab has the same effect as the configuration on the "Nominal diameters" tab.

Procedure 1. Click the [...] button of the required branch part in the "ND Range" column and select the

tab of the required branch part in the lower half of the "Branch table" tab.

The window with the nominal diameter table of the branch part opens.

2. To add a nominal diameter to the nominal diameter range, select the "Select" command in the context menu of an empty white cell.

3. To exclude a nominal diameter from the nominal diameter range, select the "Deselect" command in the context menu of an empty white cell.


Result The nominal diameter range of the branch part is modified accordingly:

● In the branch table

● On the "Nominal diameters" tab

Configuring the pipe spec 4.8 "Connector table" tab


4.7.5 Branch table for PDMS pipe specs When you load a PDMS pipe spec in the PipeSpec Designer, the following deviations apply compared to the COMOS pipe specs:

● Objects with the GTypes "TEE" and "OLET" are permitted as branches. The function code is irrelevant.

● There are no preselected components. This means there is only the "Show all available components" display mode.

4.7.6 Miscellaneous

Navigating from the branch table to a branch part 1. Open the window with the nominal diameter table using the [...] button.

2. In the nominal diameter table, open the context menu and select "Navigate > Object".

The corresponding pipe spec element is selected in the Navigator.

Resetting the branch table Precondition: Display mode is "Only show preselected component".

To reset the values in the branch table to the latest version, select the "Reset" command in the context menu of the branch table.

4.8 "Connector table" tab Description "Connector table" Inheritance source The tab is generated by the PipeSpec Designer. Function On the tab, you determine (from a design point of view) which pipe part is to be

used to connect two facing connection types in the engineering data. You can also specify for which pipe parts (special parts) additional pipe parts are added at the connectors during positioning.


Structure The "Connector table" tab is divided into two areas:

● Upper half: The connector table

● Lower half: The table for special parts



Connector table ● The table shows the contact faces and connection types set at the pipe spec elements

and lists them in a matrix.

● A list is stored with each table cell. For each connection type combination, COMOS analyzes which pipe spec elements match on at least one side and displays them in a list.

● You can filter or sort the table by means of the column headers.

● A context menu is available for each cell. You can use its commands to navigate to the pipe spec element, for example, or open its properties.

Table for special parts The table defines the pipe parts for which additional objects are added at the connectors. Example: Adding flanges at the connectors of a tee.

The table has the following columns:

● "Object":

– The special part at whose connectors additional pipe parts are added.

– It is displayed in the row for the first connector.

● "Connectors":

A row is added to the table for each connector of the pipe part.

● "Extra object":

The component added at this connector.

● "Definition applies":

Determines whether the definition is to be valid only for the pipe part drawn in the table or for a certain function code range.

Possible values:

– "For current object": What matters here is not the function code, but the SystemUID of the base object.

– "71100" to "71XXX": The function code ranges

Only available in the row in which the "Object" is set.

Configure the table via the context menu. See also chapter Configuring the table for special parts (Page 54).



4.8.2 Configuring the connector table You are working in the connector table.

Requirements You have assigned the following pipe spec elements to the pipe spec on the "Components" tab:

● The pipe parts to be connected.

● The connecting parts to be placed between the pipe parts.

Procedure 1. Open the context menu in the cell for the connection type combination and select "Edit

(F2)".

A list of pipe spec elements whose connection type matches on at least one side is displayed.

2. Select a suitable pipe spec element.


Result See also chapter Evaluation sequence (Page 56) or Example application in the engineering data (Page 56).

4.8.3 Configuring the table for special parts You are working in the table for special parts.

Requirements You have assigned the following pipe spec elements to the pipe spec on the "Pipe parts" tab:

● The pipe parts (special parts) at whose connectors additional objects are to be added.

● The objects to be added at the connectors of the special parts.



Procedure 1. Open the context menu in the table and select "Add".

The "Select CDevice object" window opens. The window contains a structure tree with the base object of the pipe spec set as its start node. The pipe spec elements are displayed underneath.

2. Select the pipe spec element you wish to register as the special part and close the window by clicking the "OK" button.

A row for each connector of the pipe spec element is added to the table.

The name of the special part is displayed in the "Name" column in the row for the first connector, and a link to the pipe spec element is entered.

3. Open the context menu in the "Definition applies" column in the row for the first connector and select "Edit (F2)".

A list opens.

4. In the list, determine whether the definition is valid only for the pipe part drawn in the table or for a certain function code range:

– "For current object" value: What matters here is not the function code, but the SystemUID of the base object.

– Values "71100" to "71XXX": The function code ranges

5. For each connector at which an additional object is to be added, proceed as follows:

– Open the context menu in the "Extra object" column in the row for the corresponding connector and select "Edit (F2)".

All pipe spec elements whose connection type matches that of the connector on at least one side are displayed.

– Select a pipe spec element.

A link to the pipe spec element is entered in the cell.


Result See also chapter Evaluation sequence (Page 56).

Entries in the context menu The following commands are available to configure the table with the context menu:

● "Edit (F2)"

● "Copy text"

● "Paste text"

● "Select"

● "Navigate"

● "Properties"



4.8.4 Evaluation sequence The "Connector table" tab is evaluated if two pipe parts belonging to the same pipe spec are interconnected in the engineering data.

Operational sequence 1. For both pipe parts, COMOS checks which connection types have been set on the "3D

geometry" tab.

2. COMOS uses the function code to check whether the pipe parts belong to the special parts.

Yes: COMOS determines which connection types are set at the pipe parts added at the connectors of the special part. To do this, COMOS uses the pipe parts referenced in the table for special parts, not the preselected components of the corresponding pipe part type.

3. The connection type pairs are determined.

4. COMOS does the following recursively for each connection type pair:

– The connecting part is determined by evaluating the connector table.

– COMOS checks whether the connecting part is a special part.

If yes: See Step 2.

– The pipe part type of the connecting part is determined.

– COMOS determines the preselected component of the pipe part type.

– The contact faces and connection types set at the preselected component are determined.

– The connection type pairs connected at the connecting part are determined.

Result ● COMOS connects the pipe parts and the connecting parts ascertained using the

connector table. If special parts have been defined, additional objects are created at their connectors.

● The special part is always created with the pipe parts specified in the special part table. It is not relevant which preselected components have been set in the engineering data.

● The preselected components of the corresponding pipe part types are used for the connecting parts ascertained using the connector table. These are not necessarily the pipe parts set in the connector table.

4.8.5 Example application in the engineering data A flanged valve ("valve") is placed on a pipe branch in an isometric drawing. This separates the pipe into two parts ("Pipe_1" and "Pipe_2").



Evaluation COMOS proceeds as follows to evaluate the "Connector table" tab in the engineering data:

Step Action Result 1 COMOS uses the function codes to check whether

the pipe or the valve is included in the list of special parts.

No

2 The connection types of the pipe are determined. At both connectors: "ButtWeld end" 3 The contact faces and connection types of the valve

are determined. Contact face at both ends: "EN form B2" Connection type at both ends: "Flanged ends"

4 COMOS checks which connecting part is set in the connector table of the subclass for this combination.

A weld neck flange

5 The function code of the flange is evaluated and the pipe part type is determined this way.

Function code: "31100" Pipe part type: Base objects "@VIPER > @PPT

> 31XXX Weld neck flange"

6 COMOS determines which preselected component is set for the weld neck flange pipe part type.

A flange with the base object "@VIPER > @PPC > 1 > 31 > 1 > 00 > 01 > 12 > B > 0010 > 03 > 01"

7 COMOS determines which connection types and contact faces are set at the preselected component.

Input: "ButtWeld end" Output: "Flanged ends", "EN form B2"

Step by step, COMOS then connects the pipe parts via their connectors. The connector tables are evaluated again in this step and the required connecting parts are created:

Connection type combination Connecting part in

connector table Result

Output of "Pipe_1": ButtWeld End Input of "Weld neck flange_1": ButtWeld

End

Construction weld COMOS determines the function code of the construction weld and inserts the preselected component of the corresponding pipe part type: "Construction weld_1"

Output of "Weld neck flange_1": Flanged ends/EN form B2

Input of "valve": Flanged ends/EN form B2

Flat gasket COMOS determines the function code of the construction weld and inserts the preselected component of the corresponding pipe part type: "Flat gasket_1"

Output of "valve": Flanged ends/EN form B2

Input of "Weld neck flange_2": ButtWeld End

Flat gasket COMOS determines the function code of the construction weld and inserts the preselected component of the corresponding pipe part type: "Flat gasket_2"

Output of "Weld neck flange_2": ButtWeld End

Input of "Pipe_2": ButtWeld End

Construction weld COMOS determines the function code of the construction weld and inserts the preselected component of the corresponding pipe part type: "Construction weld_2"

Configuring the pipe spec 4.9 "Diagram" tab


Result on the isometric drawing

4.9 "Diagram" tab Description "Diagram" Inheritance source The tab is generated by the PipeSpec Designer. Function The tab evaluates the pressure/temperature rating of the pipe spec and the

pipe spec elements and displays the corresponding information in a diagram. The diagram is for information purposes only.

4.9.1 Content of the "Diagram" tab

Evaluated data The diagram evaluates the following data:

● Pipe spec, "PipeSpec limits" tab, "Class use limit" control group: "Rating" table

● Pipe spec elements, "Part attribute" tab, "Pressure/temperature dependency" control group: Tables "T" and "P"

Configuring the pipe spec 4.10 Other tabs


Display X axis Temperature Y axis Pressure Legend Top right-hand corner of the diagram:

Red: The pipe spec Other colors: The pipe spec elements

No data available When you click on the tab, although a pressure/temperature rating has not been defined for the pipe spec and the pipe spec elements, the message "Diagram empty" is displayed.

4.10 Other tabs

4.10.1 "Function" tab Name "GD" Description "Function" Inheritance source "@VIPER > @Y > @PC > GD Function" Function Saves data for internal purposes.

Content Some of the information on the tab is preconfigured in the COMOS DB. It has the following attributes:

Attribute Function "Function code" Specifies that the base object defines a pipe spec.

Value: "Pipe spec" Do not change the value.

"Base object for pipe" Defines which base object is used for the first layer of the pipe structure. Overwrites the corresponding project property. See the "COMOS Administration" manual, keyword "Base object for pipe".

Within engineering (e.g. on an isometric drawing), it is possible to use pipe specs that work with different standardizations.

Default setting in COMOS DB: The same base object as in the project properties of the project

"Base object for pipe branch"

As above, only for pipe branches.

Configuring the pipe spec 4.10 Other tabs


Attribute Function "PipePart Finder" Reference to the start object of the catalog at which the PipePart Finder

starts to search. "XML file" For an imported pipe spec: The path to the file from which the pipe spec

was read in. "Selector" Pointer to the base object with the selector structure "Uses" A query which groups all nodes in which the pipe spec has been set as

the project pipe spec in the engineering data. "VREC" Option which enables the following functionality for pipe spec mapping

on a P&ID: If the PPC implementation requires that a more specific P&ID object

than the one used thus far serves as the request, the base object is changed at the P&ID request.

Properties of the attributes Name "VFCD" Description "Function code" Standard table Standard table "@3D > 01 > BC > 01 > 03 Function code"

Name "CPIPEOWNER" Description "Base object for pipe" Script block "GetScriptLinkObject"

If a pointer has not been set, the script ensures that the base object set in the project properties is used.

Apply COMOS DB implementation:

"@VIPER > @Y > @PC > GD > CPIPEOWNER"

Name "CSTREAM" Description "Base object for pipe branch" Script block "GetScriptLinkObject"

Same as "CPIPEOWNER". Apply COMOS DB implementation:

"@VIPER > @Y > @PC > GD > CSTREAM"

4.10.2 "Remarks" tab Name "C3" Description "Remark" Inheritance source "@VIPER > @Y > @PC > C3 Remark" Function Used for further documentation for the pipe spec

Configuring the pipe spec 4.11 PipePart Finder


Procedure Add details providing additional information about the pipe spec to the "Remarks" field.

4.10.3 Other The administrator can define additional tabs at the base object of the pipe spec, which are then likewise displayed and can be configured in the PipeSpec Designer.

4.11 PipePart Finder

4.11.1 Introduction The PipePart Finder is a tool that you can use to add pipe parts of a pipe class based on queries. It consists of two components:

● A query-based search through the pipe part catalog

● The option to define a template pipe class based on generic components.

See also chapter Assigning a new pipe part (Page 40).

Functionality All pipe part types are subordinated to a structure element that serves as container in the pipe part catalog. Structure elements are able to function as template components in the PipePart Finder. This means that they are only broken apart later in the pipe class and the subordinate pipe parts are determined according to specific criteria and added to a pipe class.

Template components and pipe parts are collected and made available based on filters using a template pipe class with one or several queries. If you use and break apart the template pipe class and the template components contained in a pipe spec, the pipe parts of all template components from the pipe part catalog are determined using the data on the "Characteristics" tab. The template components are broken apart and replaced by the matching pipe parts contained therein.

This means you do not assemble the pipe spec with drag&drop from the pipe part catalog, but define characteristics for all part types, such as pipes or flanges. This way you can find the specified pipe parts and component using the PipePart Finder and assign them to the pipe class.

Configuring the pipe spec 4.11 PipePart Finder


4.11.2 Using template pipe class

Requirements You have defined at least one template pipe class. See also chapter Creating template pipe classes (Page 183).

Procedure 1. Open the "Characteristics" tab of the pipe spec.

The information in the table "Classes characteristics nominal-diameter-dependent" is used by the filters on the "Pipe parts" tab of the template pipe class as comparison values for the selection of pipe parts.

2. Here you use values that are accepted as comparison value. If a value is used as comparison value for the selection of pipe parts is determined in the filters on the "Pipe parts" tab of the template pipe class.

Use the "*" symbol as a placeholder for values that are to be accepted by the respective attribute of the pipe class to which the component belongs.

3. Use drag&drop to drag a template pipe class to the "Pipe spec administration > Pipe parts" tab of a pipe spec.

4. Select the following command from the context menu of the template pipe class:

– "Solve pipe spec template > with tracing"

COMOS creates a log file and displays it. Save this file manually, if desired.

– "Solve pipe spec template > without tracing"

COMOS does not create a log file.

Result COMOS searches for matching pipe parts when breaking up the template pipe class based on the following information in the properties of the pipe spec:

● Information on the "Characteristics" tab

● Filter settings on the "Pipe parts" tab

If pipe parts are found based on a template component, they are listed and the template component is removed. If no pipe parts are found, the template component remains in the list. If no pipe parts are found, it may be that the filter criteria from the "Pipe parts" tab are too restrictive.


Using bolt sets 55.1 Fundamentals of bolt sets

Definition A bolt set always refers to the drilling pattern of a flange plate. Dependent upon the pressure stage and standard, it defines N bolts of dimension DIM. Bolt sets can contain mixed bolted joints.

Principle Bolt sets are defined base objects with assigned screw parts.

The bolt parts included in the bolt set are assigned to a pipe spec and apply to a specific nominal diameter range in the pipe spec.

When you use a flanged pipe part in the engineering data, COMOS determines the appropriate bolt set and calculates the bolts. Bolt sets are created below the pipe branch. One bolt set is created for each flange plate and counterpart flange plate. You will find detailed information on the components of the bolt set in the properties of the bolt set.

Selecting the right bolt set in the engineering data Whether or not the flanged pipe part has been assigned a bolt set determines which bolt set is used in the engineering data:

No bolt set assigned (standard procedure):

● COMOS determines the pipe spec and nominal diameter of the pipe part.

● COMOS checks which bolt sets are available in the pipe spec for the nominal diameter:

– With a matching bolt set: The bolt set is used.

– With several matching bolt sets: COMOS uses the bolt set that was set as the preselected component for the nominal diameter.

Bolt set assigned:

● If a bolt set has been assigned to the pipe part in the pipe part catalog or at the pipe spec element, COMOS uses the assigned bolt set.

Using bolt sets 5.2 Requirements


Rules for different bolt sets Joint Rule Flange - flange Both bolt sets must be identical.

The bolt set found first is used. Flange - valve - flange The bolt set of the valve is used. Contiguous flange group with clamp part

The bolt set of the clamp part is used.

Selectors as selection criterion Use selectors to control which bolt set is used.

The selectors are defined at the pipe spec and evaluated at the pipe branch in which the flanged pipe part is installed. The value supplied by the pipe branch determines which bolt set is used.

Example: A "temperature" selector is defined at the pipe spec. Another bolt set is used dependent upon the temperature of the pipe branch.

Contact your customer service agent if you have any questions.

Screws calculation The data required to calculate the bolted joint is taken from the following sources:

● The geometry standards for the flanges

● The geometry standards for the screw parts

The type of bolted joint set at the flange pipe part determines which algorithm COMOS uses to calculate the screw lengths.

See also Algorithm for calculating the screw length (Page 187)

Bolt sets in the engineering data (Page 68)

5.2 Requirements Requirement for using bolt sets in pipe specs:

● The standard tables required for screw parts are complete.

See also chapter Standard tables for screw parts and bolt sets (Page 82).

● The standardization on which the pipe spec is based makes provision for screw parts


Using bolt sets 5.3 Workflow


● The important geometry standards for screw parts, flanges, and gaskets are included in the standard catalog for geometry standards


● The pipe part catalog contains screw parts, flanges, and gaskets


● Bolt sets have been prepared in the base data

See also chapter Creating a bolt set (Page 168).

5.3 Workflow To use a bolt set, proceed as follows:

1. In the pipe spec, define the characteristics for the strength grades of screws and nuts.

See also chapter Defining the strength grades of screws and nuts ().

2. Add the bolt set to the pipe spec and define the nominal diameter range within which the bolt set is available.

See also chapter Adding the bolt set to the pipe spec (Page 66).

3. Add the screw parts in the bolt set to the pipe spec and define the dimensions in which the screw parts in the bolt set are available.

See also chapter Adding screw parts to the pipe spec (Page 66).

4. Optional: Assign the bolt set to a flanged pipe part, either in the pipe part catalog or in the pipe spec.

See also chapter Assigning the bolt set to a pipe part (Page 67).

5.4 Defining the strength grades of screws and nuts

Requirements You have loaded the pipe spec in which you wish to use the bolt set in the PipeSpec Designer.

Procedure 1. Select the "Characteristics" tab.

You are working in the "Class parameters" control group.

2. Select the strength for screws and nuts in the list of the same name.


Using bolt sets 5.5 Adding the bolt set to the pipe spec


5.5 Adding the bolt set to the pipe spec

Requirements ● You have loaded the pipe spec in which you wish to use the bolt set in the PipeSpec

Designer.

● The "Base objects" tab is open in the Navigator.

Procedure 1. Go to the "Components" tab.

2. Open the node "@VIPER > @BoltSet bolt sets" in the Navigator.

3. Drag&drop the required bolt set from the Navigator to the "Components" tab.

4. The bolt set now belongs to the pipe spec. The bolt sets are listed in the pipe part table under the node with the function code "100XX".

5. Enter the upper limit of the nominal diameter range for the bolt set in the "Nominal diameter from" column and the lower limit in the "Nominal diameter to" column.


5.6 Adding screw parts to the pipe spec

Background The evaluating reports which document the pipe spec only contain information about the screw parts in the bolt set if the screw parts have been added to the pipe spec.

Requirements ● You have loaded the pipe spec in which you wish to use the bolt set in the

PipeSpec Designer.


Procedure 1. Select the base object of the bolt set in the Navigator.

2. Open the properties of the bolt set and click the "Attributes > Bolt set" tab.

All screw parts which are part of the bolt set are displayed in the tables of the "Screw parts" and "Stud hole screw parts" control group.

Using bolt sets 5.7 Assigning the bolt set to a pipe part


3. To add the screws and screw parts to the pipe spec, proceed as follows:

– Select a screw part from the table "Screw parts" or "Stud hole screw parts".

– Select "Navigate > Object" from the context menu.

The base object is selected in the Navigator under the open pipe part catalog.

– Drag the base object of the screw part from the Navigator with drag&drop to the "Pipe parts" tab of the PipeSpec Designer.

The screw part is assigned to the pipe spec. In the component table, the screw parts are grouped under the node with the function code "XXXXX".

The columns "Nominal diameter from" and "Nominal diameter to" show you which upper limit

and which lower limit the standardization gives for the screw parts.

– To limit the specified upper limit and lower limit, click the "Nominal diameter from" and "Nominal diameter to" columns and change the dimension in the list.

4. Change to the "Nominal diameters > XXXXX" tab.

5. Refine the dimensions in which the screw parts are available in the "Nominal diameter range" control group.


See also "Nominal diameters" tab: (Page 42)

5.7 Assigning the bolt set to a pipe part

Aim Instead of using the standard procedure, you define which bolt set is used for a flanged pipe part.

Requirements The required bolt set is displayed on the "Base objects" tab in the Navigator.

Procedure 1. If the bolt set is to be used at all times, regardless of which pipe spec the pipe part

belongs to, navigate to the base object of the pipe part in the pipe part catalog and open its properties.

2. If the bolt set is only to be used for a certain pipe spec, navigate to the base object of the pipe spec and open the properties of the pipe spec element of the pipe part.

3. Click on the "Attributes > 3D geometry" tab.

Using bolt sets 5.8 Bolt sets in the engineering data


4. Drag the base object of the bolt set to the "VD#6 Screw types #", field, where "#" stands for the index number of the connector.


5.8 Bolt sets in the engineering data

Principle When you use a flanged pipe part in the engineering data, the following happens:

● The matching bolt set is determined.

● The bolt set is calculated.

● The bolt set is created below the pipe branch under which the pipe part is located.

Properties of the calculated bolt set You can find out more about the result of the calculation in the properties of the bolt set on the "Attributes > For bolt calculation" tab.

The following information will be displayed:

● Importance of screw parts for the parts list and screw name

● Number of screws

● Dimensions

● Selected length

● Calculated length

See also chapter Algorithm for calculating the screw length (Page 187).


Miscellaneous information about pipe specs 66.1 Using project pipe specs

Restricting the use of pipe specs You can always restrict which of the pipe specs available in an engineering project may be used in the engineering data. The pipe specs which are then actually available are called project pipe specs.

See also sections Requirements () and Defining a project pipe spec (Page 70).

Scope The following applies depending on the configuration of the database:

● The pipe specs are valid for the entire engineering project or only for certain unit nodes.

● The project pipe specs are valid for all or just certain pipe parts.

6.1.1 Requirements

Database To restrict the use of pipe specs to project pipe specs, the database must meet the following requirements:

● Unit objects:

Unit objects have the "Pipe spec administration" tab, as it is defined in the COMOS DB: "@VIPER > @Y > CHP > VIPER > PSM001 Pipe spec administration"

● Pipe parts which are only to use project pipe specs:

Properties of the pipe part > "Technical data" tab > "Pipe spec" attribute > script block "FillComboList(Combobox)": ": The script block is implemented as stored in the COMOS DB as an example for pipe branches: "@10 > PID > 3 > 01 > PI030 > 01 > PI030 > PIA012 Pipe Spec" node

See also The "PSM001 Pipe spec management" tab (Page 220)

"FillComboList" for the use of project pipe specs (Page 221)

Miscellaneous information about pipe specs 6.1 Using project pipe specs


6.1.2 Defining a project pipe spec

Procedure To restrict the pipe specs available in an engineering project, proceed as follows:

1. Open the engineering project.

2. Switch to the "Units" tab in the Navigator.

3. Navigate to the level as of which the project pipe specs are to apply, for example, a part unit.

4. Open the properties of the unit object.

5. Go to the "Attributes > Pipe spec administration" tab.

6. Click on the "Base objects" tab in the Navigator.

7. Navigate to the node under which the base objects of the pipe specs are located.

8. For all pipe specs which are to be project pipe specs: Drag&drop the base object of the pipe spec to the "Pipe specs" table on the "Pipe spec administration" tab.

The name of the pipe spec is displayed in the table and the pipe spec is added to the list of project pipe specs.

9. To remove a project pipe spec from the table, select it and choose "Remove pointer" from the context menu.


If the project pipe specs are to apply for the entire engineering project, repeat steps 4 through 10 for all unit objects directly underneath the project root.

Result ● The node at which the project pipe spec was set is saved at the base object of the project

pipe spec: "Attributes > Function" tab, "Uses" query

● If you want to set the pipe spec at a pipe part configured accordingly in the engineering data, COMOS runs a recursive check to see whether the owner of the pipe part defines project pipe specs. If this is the case, the search is aborted and the project pipe classes are offered for selection.

If more than one unit object of the owner structure defines project pipe specs, only the definition on the lowest layer applies.

Miscellaneous information about pipe specs 6.2 Using insulation classes


6.2 Using insulation classes

Properties of insulation classes Insulation classes are base objects with the following properties:

● Type of insulation:

– Cold insulation

– Warm insulation

– Touch protection

● Insulating material:

– Mineral wool

– PU foam

– Foam glass

● Shell material:

– Zinc-plated sheet

– Stainless steel sheet

– Aluminum foil

● Media temperature:

The insulation class is valid for a media temperature.

● Insulating strength:

The insulating strength depends on the nominal diameter. It contains a table with the permitted nominal diameter range and the corresponding insulation strengths.

Trace heating and cooling are also managed in the insulation class. The properties of the heating are also required for this purpose.

● Heating type (medium):

– Steam/condensate

– Electric trace heating

– Frost protection

● Heating temperature

● Maximum temperature

● DN of the trace pipes/cross section of the pipes

● Number of pipes

● Reference object for trace pipes/hoses



Base object and function code ● The insulation classes are located in the base data under the "@VIPER > @SPEC

> @ISOLIERUNG Insulation Classes" node.

● The insulation classes have a different inheritance source than the base objects of the pipe specs, i.e. the base object "@VIPER > @Y > @PCI Base object insulation classes".

● Insulation classes have the function code "Insulation class" (10002).

Modules which use insulation classes ● COMOS PipeSpec Designer

● COMOS Isometrics

● COMOS Plant Modeler

6.2.1 Functional principle of insulation classes

Principle ● Insulations are made available via insulation classes.

● The insulation class defines the default settings for the insulations.

● Insulation classes are managed in the PipeSpec Designer.

● Only insulations are permitted to belong to insulation classes (pipe insulation types, flange caps, valve caps).

The insulations come from a special branch of the pipe part catalog.

● The insulation class belongs to a pipe spec. The pipe spec elements of the pipe spec can use the insulation class.

● The insulations are created under the pipe parts in the engineering data. They only save data that is relevant for an insulation. They do not replace the actual pipe part.

● To calculate the geometry of the insulation, COMOS adds the density of the insulating material to the standard pipe part dimensions. To do this, COMOS evaluates the nominal-diameter-dependent characteristics table of the insulation class.

Use on isometric drawings ● To define which components are insulated, users use insulation flags during the

construction process. This creates insulations under the components.

● The insulations come from the pipe part catalog.

● The insulation flags save the insulation class and the insulation size.



● All pipe parts within the flags are insulated. The insulation information is passed from component to component within the flags.

● The dimensions of the flags determine the actual length of the insulation for the list of objects.

Use in the Plant Modeler ● During the construction process, users decide whether insulation is to be used. The

selected type of insulation is then used for all objects created during the construction process. This creates insulations under the components.

● A user who specifies the insulation information at a pipe branch retrospectively or modifies this information can forward it to all connected pipe branches which have the same pipe spec and nominal diameter.

● The insulations come from the pipe part catalog.

● You find additional information on this topic in the "Plant Modeler" manual.

6.2.2 Insulation catalog The insulation catalog is a subnode of the pipe part catalog. In the COMOS DB, this is the "@VIPER > @PPC > Isolierung Component catalogs" node.

The structure of the insulation catalog can be freely selected.

Central properties of insulation objects ● Function code: Same function code as the corresponding pipe component.

● GeoType: "Insulation"+"<GeoType of the pipe component>".

● Calculation formula in dimension attributes: CatPC("S", 1)*2.

This means that at the insulation class, row "S" of the nominal-diameter-dependent table is evaluated on the "Characteristics" tab. It saves the insulation sizes.

● For all attributes necessary for the calculation of the component geometry, COMOS proceeds as follows:

– The attribute is evaluated at the owner of the insulation at the pipe component.

Example: "V001 OutD1"

– COMOS evaluates the corresponding "I" attribute at the insulation.

Example for "V001 OutD1": "IV001 Insulation height"

– COMOS adds the values of the owner attribute and the "I" attribute.

– If a value deviating from the insulation class has been entered for the insulation size, COMOS uses the corresponding "IX" attribute and not the "I" attribute.

● Pipe insulations have a dedicated length.



● Insulations have their own connection types.

● An insulation is only connected if the connection types are the same.

Tabs Name Description Comment "C2" "PipeSpec limits" Saves information about the nominal diameter and the pressure/temperature

rating. Inheritance source: The insulation class base object

"CM3D", "DM"

"Plant Modeler components", "Data Maintenance"

Same inheritance source and function as at the other pipe parts in the pipe part catalog. See also chapter Overview of the tabs and their inheritance sources (Page 127).

"GD" "Geometry" The tab is customized for the requirements of insulations. Inheritance source: "@VIPER > @Y > CHP > Isolierung > GD Geometry"

6.2.3 Workflow

Requirements ● The insulation catalog contains all necessary insulations.

● The insulations are fully configured.

● There is a pipe spec which is to use the insulation class.

Workflow for using insulation classes 1. Open the PipeSpec Designer and create an insulation class. See also chapter Creating a

new pipe spec (Page 21).

2. Configure the tabs for the insulation class in the following order:

– "PipeSpec limits"

– "Characteristic"

– "Components"

See also chapter Configuring insulation classes (Page 75).


4. Load the pipe spec which is to use the insulation class in the PipeSpec Designer.

5. Go to the "Components" tab.

6. Drag&drop the base object of the insulation class from the Navigator to the pipe part table.

The insulation class and its insulations are assigned to the pipe spec.




See also Assigning a new pipe part (Page 40)

6.2.4 Configuring insulation classes

Requirements ● You have loaded the insulation class in the PipeSpec Designer.


Procedure 1. Click on the "PipeSpec limits" tab in the PipeSpec Designer.

2. Configure the "Standard" field and the "Nominal diameter range" control group.

Proceed as described for the pipe specs.

3. Go to the "Characteristics" tab and configure the attributes:

Control group Configuration "Insulation class characteristics"

Select the insulation system, the insulating material, and the insulant casing.

"Electric heating" Select the heating system and heating type. Define the electric heating.

"Trace heating" Define the type of trace heating. Define the trace heating pipe.

Nominal-diameter-dependent characteristics table

Enter the following parameters dependent upon the nominal diameter: Insulation outer diameter Insulating material density Substructure density Heating layer density Cover layer density Number of trace heating pipes Nominal diameter of trace heating pipes

4. Go to the "Components" tab.

5. Open the insulation catalog in the base data.

6. Drag&drop the required insulations to the "Components" tab.


Miscellaneous information about pipe specs 6.3 Documenting pipe specs


See also "PipeSpec limits" tab (Page 28)

6.3 Documenting pipe specs

Example reports The COMOS DB contains two ready-to-use examples of evaluating reports which document pipe specs in full:

● A pipe spec report:

You find the pipe spec report on the "Base objects" tab in the Navigator, directly underneath the base object of the pipe spec.

● A component report for each pipe part belonging to the pipe spec:

You find the component report in the @VIPER > @SPEC" node on the "Base objects" tab in the Navigator, underneath the pipe spec elements of the pipe specs.

6.4 Creating a revision of pipe specs After you have assembled the pipe spec and assigned all required pipe parts to the pipe spec, you can change the properties of the pipe parts at a later time. You can do this by inheritance, for example, if attributes of a pipe part are changed in the pipe part catalog.

To prevent that a pipe part changes in a pipe spec at a later time, you can create a revision of the pipe spec and its pipe parts. This revision stores all properties of the pipe parts that were present when the pipe class was created.


Administration 77.1 Administration workflow

Workflow Before users can create and manage pipe specs in the PipeSpec Designer, the following preparatory administrative tasks have to be completed.

1. In the properties of the base object, make the settings necessary for working with the PipeSpec Designer.

See also chapter Setting project properties ().

2. Complete the standard tables in the database, if necessary.

See also chapter Managing standard tables (Page 78).

3. Complete the standardizations used by the pipe spec in the database, if necessary.


4. Configure and complete the standard catalog for geometry data in the database, if necessary.


5. Configure and complete the pipe part catalog (PPC) in the database, if necessary.


6. Create bolt sets.

See also chapter Managing bolt sets (Page 168).

7. If you require different settings in an engineering project, overwrite the default settings from the base project.

7.2 Setting project properties

Introduction In the project properties, set the parameters required by the PipeSpec Designer to work with the database on the "Viper" tab.

These values are preset in the base object "SO1" of the COMOS DB. The settings from the base project are automatically taken over by all engineering projects.

Overwrite the preset values of an engineering project, if necessary. If an engineering project is only to use project-specific pipe specs, group the project-specific pipe specs under a dedicated (sub)node and enter this (sub)node under "Definition of PipeSpecs".

Administration 7.3 Managing standard tables


Project parameters of the "Viper" tab Field Description Default User-defined

configuration "Standardizations" Pointer to the base object node in

which norm objects are searched. "@VIPER > @STD"

"Definition of PipeSpecs"

Pointer to the base object node in which pipe specs are searched.

"@VIPER > @Spec"

"Basic Tables, Industrial Standards"

Pointer to the base object node in which the standard catalog for the geometry standards is searched.

"@VIPER > @CATSTD"

Standard table "Nominal diameters"

Pointer to the node in which the standard table with the permitted nominal diameters is located.

"@3D > 01 > 05"

"Pipe part types" Pointer to the base object node in which pipe part types are defined.

"@VIPER > @PPT"

If the structure of your database differs from that of the COMOS DB: Enter a pointer to the corresponding node.

"Rating for the raster router"

Not relevant for the PipeSpec Designer.

"@VIPER > @3D > 2 > AR" -

"Default coding for XML import"


"ISO-8859-1 ISO-Kodierung für westeuropäische Sprachen"

-

"Start OpenGL in software mode"


Active -

7.3 Managing standard tables

Purpose The administration of data in standard tables is part of the standard functionality of COMOS.

Standard tables are used for the following reasons in the PipeSpec Designer:

● It facilitates or forces the selection of certain attribute values.

● To administer parameters and their characteristics.

You can find additional information on this topic in the "COMOS Administration" manual, keyword "Standard tables".

COMOSDB The standard tables necessary for working with the PipeSpec Designer are located in the COMOS DB under the "@3D > 01 Piping" node and specifically in the "… > 03 Standards" subnode.

Customer database Import the "@3D > 01 Piping" standard tables node and its subnodes into the database.



See also Definition ()

7.3.1 Managing parameters

7.3.1.1 Note about parameter management

Note Data inconsistencies if parameters are not managed correctly

Not managing parameters correctly can lead to data inconsistencies in the database and take up significant additional time and effort. Seek advice from your account manager before you enter the following parameters: Nominal diameters Nominal pressure Types of gasket Connection types Function codes

7.3.1.2 Definition Many of the standard tables managed in the "@3D > 01 Piping" node are parameters.

Parameters are properties of a pipe part which are relevant to pipe specs. Their possible values are restricted:

● By the standardization assigned to the pipe part

● By the pipe spec to which the pipe part belongs

The values (characteristics) permitted in principle for this parameter are listed in the standard table. Each value corresponds to a standard table entry.

The standardization and the pipe spec restrict which standard table entries are actually available for selection at the pipe part.

Example parameters:

● Nominal pressure

● Nominal diameter

● Material

● Material standard

● Technical norm

● Flange standard



7.3.1.3 Amending parameters

Amending parameters by adding characteristics Expand the standard tables by adding additional characteristics, if necessary. You find additional information on this in the "COMOS Administration" manual, keyword "Creating standard tables".

When entering the properties of a new standard table entry, please note the following points:

● "Name" field:

The entries in a standard table are listed in the PipeSpec Designer and in the properties of the engineering and base objects sorted by the values entered in the "Name" field.

● "Description" field

– A user who expands a list stored with this standard table in the interface sees the texts entered in the "Description" fields.

– If the standard table contains standards: Enter the name of the standard as a long text and use a "-" to separate the name of the standard and the descriptive text.

Example: "DIN 3754/T1-It Plates for Gaskets"

● Field "Value 3"

– If the standard table is assigned to an attribute which implements the "GetDisplayValue" script block as it is preconfigured in the COMOS DB, the user sees the value entered in the "Value 3" field in the interface.

– If the standard table contains standards: Enter the name of the standard as a short text.

Example: "DIN 3754/T1"

See also GetDisplayValue() (Page 213)

7.3.1.4 Creating a new parameter

Procedure 1. Create a new standard table.

2. Create standard table entries.

See also chapter Adding parameters (Page 94).

3. Configure the standard table entries.

4. Use the standard table in the standardization.



7.3.2 Standard table for nominal diameters

Purpose All nominal diameters available in COMOS are grouped in the standard table that is defined in the project properties.

The nominal diameters in the ""@3D > 01 > 05 Nominal diameters" standard table are grouped in the COMOS DB.

Structure The standard table for nominal diameters is structured in accordance with the following rules:

● Both DIN and ANSI values are managed in the standard table.

● New nominal diameters are appended to the end of the list.

● Existing nominal diameters must not be deleted or moved.

As a result, the DIN and ANSI values in the list are neither maintained as contiguous blocks nor are they sorted continuously in ascending order: At the top of the standard table, you find the nominal diameters for DIN/EN, followed by nominal diameters for ANSI/ASME, and at the end of the table you can once again find values for DIN/EN.

Note Loss of data if the table is not managed correctly

Not managing the standard table for nominal diameters correctly can lead to data inconsistencies in the database and take up significant additional time and effort, in particular in the standard catalog for geometry standards.

Therefore, you should seek advice from your account manager before editing the standard table for nominal diameters.‎

7.3.3 Standard table for weld shapes

Purpose The weld shapes in the ""@3D > 01 > BC > 04 Weld shapes" standard table are grouped in the COMOS DB. Point to these standard tables in the base objects of welds on the "Attributes > 3D geometry" tab, "Weld shape" field.

Note

You may only change the description of the weld shape.



7.3.4 Standard tables for screw parts and bolt sets You need the following standard tables when you use bolt parts and bolt sets.

Standard table for function codes ● Check whether the standard table for function codes contains the following entries for

screws, nuts, and washers:

Standard table entry for... "Name" field "Description" field Field "Value 1" Screws "91100" "Screw" "91100" Nuts "91800" "Nut" "91800" Washers "91900" "Washer" "91900" Bolt set "10009" "Bolt set" "10009"

● In the COMOS DB, you find the standard table under "@3D > 01 > BC > 01 > 03 Function Code".

● The standard table is used in the pipe part catalog, on the "3D geometry" tab.

See also chapter Standard table for PPC function codes (Page 226).

Standard table of standards for screws and nuts ● Check whether the standard table exists and is complete.

● Node in COMOS DB: "@3D > 01 > 03 > 09 Screw standards".

● The standard table is used in the following places:

– As a parameter in the standardizations, on the "Attributes > Characteristics" tab.

– In the properties of screws and nuts, "Attributes > Part description" tab.

Standard table of dimensions of screws and nuts ● Check whether the standard table exists and is complete.

● Node in COMOS DB: "@3D > 01 > 19 > 01 > 1 Screw dimensions to EN/DIN".

● Similar to the standard table for nominal diameters, the following applies:

– In the standard table, the dimensions are managed as DIN and ANSI values.

– New dimensions are appended to the end of the list.

– Do not move or delete existing entries.


– As a parameter in the standardizations, on the "Attributes > Characteristic Definition", "... > Screw dimensions", "... > Screw lengths" tabs.

– In the standard catalog for geometry standards.

– At the screws and nuts and washers in the pipe part catalog.



Standard table for screw lengths ● Check whether the standard table exists and is complete.

● Node in COMOS DB: "@3D > 01 > 19 > 02 Screw lengths".

Standard table for screw lengths to DIN/EN and ASME.

● Similar to the standard table for nominal diameters, the following applies:

– You can expand the list before the standardizations are configured.

– New values are appended to the end of the list.

– Do not move or delete existing entries.


– In the standardizations on the "Attributes > Screw lengths" tab

– In the standard catalog for geometry standards.

– At the screws and nuts and washers in the pipe part catalog.

Standard table of strength grades for screws and nuts ● Check whether the standard table exists and is complete.

● Node in COMOS DB: "@3D > 01 > 19 > 03 Strength grades screws/nuts ...".

Subnode for strength grades to DIN/EN and ASME and subnodes for individual standards.


– In the PipeSpec Designer on the "Characteristics" tab.

– In the properties of screws and nuts, "Attributes > Part description" tab.

Standard table for types of bolted joint ● Check whether the standard table exists and is complete.

● Node in COMOS DB: "@3D > 01 > BC > 03 Bolted joint types".

Subnode for strength grades to DIN/EN and ASME and subnodes for individual standards.

● The standard table is used in the flanges of the pipe part catalog, on the "3D geometry" tab.

Administration 7.4 Managing standardizations


7.4 Managing standardizations

Principle

Note Data inconsistency if standardizations are not managed correctly

Not managing norm objects correctly can lead to data inconsistencies in the database and take up significant additional time and effort.

This is true in particular if you modify standardizations which are already in use.

Seek the assistance of or instructions from your account manager before modifying the standardizations supplied with the COMOS DB.

Implement a standardization only in coordination with your account manager.

Definition A standardization defines the parameters on which the pipe specs to which this standardization has been assigned are based, and the values which the characteristics of the parameters are permitted to adopt. This default is also valid for the members of the pipe spec.

If you assign a standardization directly to a pipe part attribute, you should also define the permissible range for the attribute values.

The standardization defaults also apply to the standard catalog for geometry standards where the following points are concerned:

● Nominal diameter range

● Nominal diameter combinations

● Dimensions

● Screw step lengths

Implementation of standardizations in COMOS There is a base object for every standardization. A "from/to" range is defined for each parameter in the properties of the norm object.

The standardization also specifies which nominal diameter combinations and screw step lengths are permitted.

The COMOS DB contains default standardizations for the DIN/EN and ANSI/ASME standard systems.

Configuring norm objects You can modify the norm objects supplied with the COMOS DB or create new standardizations.



See also Implementing a new standardization ()

Configuration of the standardization (Page 88)

7.4.1 Base object node In the COMOS DB, you find the standardizations in the node:

"@VIPER > @STD Standardizations"

7.4.2 Requirements for working with standardizations

Requirements To work with standardizations, the database must meet the following requirements:

● There are standard tables for the parameters used by the standardization.

● The standard tables feature the characteristics necessary for the standardization.

See also Managing standard tables (Page 78)

7.4.3 Implementing a new standardization

7.4.3.1 Workflow

Procedure 1. Add the standardization to the standard table for standards systems.

See also chapter Adding the new standardization to the standard table for standards systems. (Page 86).

2. Create a base object for the standardization.

See also chapter Creating the new norm object (Page 86).

3. Configure the base object.

See also chapter Configuring the standardization (Page 87).

4. Assign the standardization.

See also chapter Assigning the standardization (Page 87).



7.4.3.2 Adding the new standardization to the standard table for standards systems.

Procedure 1. Open the standard table in which the standards systems are managed.

In the COMOS DB, this is the @3D > 01 > NSYS Standards system" standard table.

The standard table already includes entries for standardizations in the node:

"@VIPER > @STD Standardizations"

2. Create a new standard table entry and input the following data:

– "Name" field: Sequential unique counter

– "Description" field: Name of the standardization

– Field "Value 1": Same as "Name"

– Field "Value 3": Abbreviation for standardization


The entry could look as follows for a company-specific standardization:

● "Name": "6"

● "Description": "Company standard METRIC"

● "Value 1": "6"

● "Value 3": "COMPS_M"

7.4.3.3 Creating the new norm object

Requirements Base object node, under which the standardizations are managed, "Attributes > Characteristic Definition" tab, "Standard" attribute: The attribute has the implementation of the "OnChange" script block preconfigured in the COMOS DB.

Procedure 1. Click on the "Base objects" tab in the Navigator.

2. Select the node "@3D > @STD Standardizations" in the COMOS DB.

This node is defined in the project properties.

3. Select "New > New base object" in the context menu.

A new norm object is created.

4. Open the properties of the new norm object and click on the "Attributes > Characteristic Definition" tab.



5. "Standard" list:

The attribute is stored with the standard table for standards systems.

Select the entry for the new standardization from the standard table.

Previously selected standard table entries cannot be selected.


Result The standardization is assigned to the norm object. The "OnChange" script block writes the name and the description of the standard table entry you selected to the properties of the norm object:

"System" tab, "General" control group, "Name" and "Description" fields.

Only one norm object can be created for each entry from the standard table for standards systems.

See also Setting project properties (Page 77)

7.4.3.4 Configuring the standardization

Procedure See also chapter Configuration of the standardization (Page 88).

7.4.3.5 Assigning the standardization

Procedure You have the following options to assign a new standardization:

● Assigning standardization to a pipe spec

See also chapter Assigning a standardization (Page 28).

● Assigning standardization to individual pipe part attributes

See also chapter Principle behind attributes which are dependent upon standards systems (Page 209).



7.4.4 Configuration of the standardization

7.4.4.1 Using the standardization only once the configuration is complete

Principle Usually you will create a standardization, configure it, and use it only once you have completed the full configuration. Standardizations are used in the following places:

● In the pipe parts from the pipe part catalog

● In the basic tables from the standard catalog for geometry standards

● In pipe specs

Modifying standardizations which are already in use When you modify a parameter of a standardization which is already in use, the current settings at the pipe parts, basic tables, and pipe specs remain unchanged. However, only the new value ranges will be available to you for future modifications.

Seek the assistance of and follow the instructions from your account manager when modifying the value ranges of the following parameters in particular, as they affect numerous locations in the database and can lead to data inconsistencies and take up significant additional time and effort:

● Nominal diameter range

● Nominal pressure range

● Contact faces

7.4.4.2 Workflow

Note

In the control groups, start by configuring each of the "from" attributes, followed by the "to" attributes, and finally the list for filtering.

Requirements The attributes of the standardization have the same properties and scripts as in the COMOS DB. See also chapter Properties of norm objects (Page 191).



Procedure To configure a norm object, proceed as follows:

1. Configure the parameters on the "Attributes > Characteristic Definition" tab in the correct order:

– "Standard Unit" attribute

– Attributes of the "Nominal diameter range" control group:

Define which nominal diameters are permitted by the standardization.

– Attributes of the "Nominal pressure range" control group:

Define which nominal pressures are permitted by the standardization.

– Attributes of the "Contact faces" control group:

Define which contact faces are permitted by the standardization.

– Attributes of the "Screw and nut dimensions" control group:

Define which dimensions are permitted by the standardization for screws and nuts.

– The remaining attributes in any order

2. On the "Attributes > Local Dimensions (DN1/DN2)" tab, enter which nominal diameter combinations are permitted by the standardization for components with two nominal diameters.

3. Enter the dimensions of the screws on the "Attributes > Screw dimensions" tab.

4. Enter the screw step lengths on the "Attributes > Screw step lengths" tab.

5. Click the "Update NDs" button on the "Attributes > Characteristic Definition" tab.

Excluded from the configuration The following standardization tabs are excluded from the standardization configuration:

● "Local Dimensions (DN)"

● "Screw lengths"

● "Washer dimensions"

● "Catalog attributes"



See also Setting the standard unit ()


Defining the dimension range (Page 93)

Adding parameters (Page 94)

Configuring the "Local Dimensions (DN1/DN2)" tab (Page 95)

Configuring the "Screw dimensions" tab (Page 96)

Configuring the "Screw step lengths" tab (Page 96)

Updating the nominal diameters (Page 97)

Excluded from the configuration (Page 99)

7.4.4.3 Setting the standard unit

Purpose The "Standard Unit" attribute determines the unit in which the local dimensions for the component geometry are specified in the pipe part catalog.

If you change the attribute at the standardization, this change is automatically forwarded to the pipe part catalog: In the nominal-diameter-dependent table on the "Local Dimensions" tab, all columns in which no values have been input yet in the pipe part catalog are switched to the new unit.

Users must then input the local dimensions in this unit.

If local dimensions have already been input in a column, the following applies:

● The unit of the column does not change.

● The values already input do not change.

The unit is always output in the column header, behind the column name.

Procedure 1. Open the properties of the standardization.

2. Click on the "Attributes > Characteristic Definition" tab.

3. Click the arrow button to the right of the "Standard Unit" field.

4. Select the required unit from the list.




Detailed description of the switch algorithm If you set a new standard unit at the standardization, this change is automatically forwarded to the pipe part catalog. In detail, the following happens:

● COMOS searches all of the standardization tabs for tables called "V".

There are tables with this name on the "StdVal1 Local Dimensions" through "StdVal6 Washer dimensions" standardization tabs.

● The new unit is written to all table columns in these tables which have not yet been checked in in the database – in other words, columns in which values have not yet been input.

At the standardization, these are all columns with length dimensions but not the columns in which nominal diameters and dimensions are input.

● The standardization inherits the nominal-diameter-dependent tables to the "Local Dimensions" tab in the pipe part catalog, for example,

where all columns in which no values have been input yet are switched to the new unit. Users must then input the local dimensions in this unit.

If local dimensions have already been input in a column, the following applies:

– The unit of the column does not change.

– The values already input do not change.

See also "Characteristic Definition" tab (Page 191)

7.4.4.4 Defining the nominal diameter range

Purpose of the "Nominal diameter range" control group Here you define the upper limit and lower limit of the nominal diameter range.

You can also exclude individual nominal diameters located between the upper and lower limit from the nominal diameter range.

The nominal diameter range is inherited to the following objects by the standardization:



● To the pipe specs which use the standardization.

● To the pipe parts from the pipe part catalog which belong to a corresponding pipe spec.

● Basic tables of the standard catalog for geometry standards.

Note Proceed with care with standardizations which are already in use

Changes to the nominal diameter range of the standardization affect numerous locations in the database. They can lead to data inconsistencies and take up significant additional time and effort. This is true in particular if a standardization is already in use.

Change the nominal diameter range only in coordination with your account manager.



You are working in the "Nominal diameter range" control group.

3. "from" and "to" lists:

Select the lower limit of the nominal diameter range from the "from" list and its upper limit from the "to" list.

The list starts with metric values, followed by inches, and then once again metric values. It is thus possible that the range of values defined by "from" and "to" can also contain values that you actually want to exclude from the nominal diameter range.

4. Click the button with the filter.

A list of all nominal diameters between the upper and lower limits is displayed. There is an option on the left of each nominal diameter value.

5. For all nominal diameters which are to be within the nominal diameter range:

– To add a nominal diameter, select the option.

– To exclude a nominal diameter, deselect the option.


Example To define a nominal diameter range in steps of ten from DN 40 to DN 100, proceed as follows.

1. "from" list: Set "40" as the starting value.

2. "to" list: Set the entry "70" as the upper limit.

All nominal diameters located between the entries "40" and "70" in the standard table for nominal diameters are now available for the nominal diameter range.

This range also includes inch dimensions and metric nominal diameters which are not required.



3. To further refine the nominal diameter range specified by the upper and lower limits, click the button with the filter:

A list of all nominal diameters between the upper and lower limits is displayed.

4. Activate only those values that actually belong to the required nominal diameter range:

Select value Nominal diameter X 40 X 50 65 X 80 X 90 X 100 125 150 175 200 250

The "Update NDs" button Use this button once you have fully configured the standardization.



7.4.4.5 Defining the dimension range

Purpose of the "Screw and nut dimensions" control group Here you define the dimensions in which screws and nuts based on this standardization are available.

The permitted range of values is inherited to the following objects by the standardization:



● To the pipe specs which use the standardization.

● To the screws and nuts from the pipe part catalog which are based on the standardization.

● To the nodes in the standard catalog for geometry standards, in which the basic tables for screws and nuts are managed.

Note Proceed with care with standardizations which are already in use

Changes to the "Screw and nut dimensions" control group affect numerous locations in the database. They can lead to data inconsistencies and take up significant additional time and effort. This is true in particular if a standardization is already in use.

Change the value range of the control group only in coordination with your account manager.



You are working in the "Screw and nut dimensions" control group.

3. Proceed exactly as described in section Defining the nominal diameter range (Page 91) for the definition of the nominal diameter range.

Note

As with the standard table for nominal diameters, DIN and ANSI values relating to the standard table for dimensions are managed in the same list and new entries are appended to the end of the list.

It is thus possible that the range of values defined by "from" and "to" can also contain values that you must exclude using the "Filter" button.


7.4.4.6 Adding parameters You can add additional parameters, such as the characteristic screw lengths, during standardization.

Requirements The standard table in which the characteristics of the parameter are managed exists and its content is complete.




2. Click the "Characteristic Definition" tab.

3. Select "Design mode" from the context menu.

4. Copy the attributes of an existing control group:

– "from" attribute

– "to" attribute

– "Filter" attribute

As the attributes have been copied, they already have all the settings and scripts necessary for working with pipe specs.

5. Paste the attributes.

6. Enter a new name and a new description.

7. Assign the standard table in which the characteristics of the parameter are managed to the attributes.

7.4.4.7 Configuring the "Local Dimensions (DN1/DN2)" tab

Purpose You define which nominal diameter combinations are permitted by the standardization on the "Local Dimensions (DN1/DN2)" tab.

The tab also serves as the inheritance source for the tab in which you enter the local dimensions of pipe parts with two nominal diameters in the pipe part catalog.


2. Click on the "Attributes > Local Dimensions (DN1/DN2)" tab.

3. Enter the permitted nominal diameter combinations in columns "DN1" and "DN2":

– "DN1": Main nominal diameter

– "DN2": Nominal diameter of the branch

– Only values located within the nominal diameter range displayed on the "Characteristic Definition" tab are available.

– If the standardization is already in use, local dimensions already entered in the pipe part catalog must not be moved or mixed by deleting a row or by inserting a new one in the middle. Therefore, you should append new entries to the end of the list and not move or delete existing ones.

See also chapter "StdVal1" and "StdVal2" tabs (Page 195).



7.4.4.8 Configuring the "Screw dimensions" tab

Purpose You define which dimension values are valid for screws, nuts, and washers based on this standardization on the "Screw dimensions" tab. See also chapter "Screw dimensions" tab (Page 197).

The tab and its attributes serve as inheritance sources:

● "V.VC11 DIM" attribute:

– The attribute is an inheritance source for the following attribute of the standardization:

"Screw lengths" tab, "V.VC11 DIM" attribute.

It is from there that the dimensions are inherited to the standard catalog for geometry standards, to the "Screw lengths" tab in the node for screws, where you enter the screw step lengths for the dimensions.

– The attribute is an inheritance source for the following attribute of the standardization:

"Washer dimensions" tab, "V.VC11 DIM" attribute.

It is from there that the dimensions are inherited to the standard catalog for geometry standards, to the "Washer dimensions" tab in the node for nuts, where you enter the nut height, the overlap, and the pitch.

● The tab is inherited to the pipe part catalog, to the node for nuts, There you can enter the local dimensions.


2. Click on the "Attributes > Screw dimensions" tab.

3. Enter the dimensions in the "DIM" column of the dimension-specific table:

– Only select values from the dimension range specified by the "Characteristic Definition" tab.

– If the standardization is already in use, local dimensions entered in the standard catalog for geometry standards must not be moved or mixed by deleting a row or by inserting a new one in the middle. Append new entries to the end of the list and do not move or delete existing ones.


7.4.4.9 Configuring the "Screw step lengths" tab

Purpose The "Screw step lengths" tab serves as the inheritance source for the standard catalog for geometry standards, where you enter the weights and material numbers of the screws based on their length. See also chapter "Screw step lengths" tab (Page 198).



Simply enter the lengths/screw step lengths at the standardization.


2. Click on the "Attributes > Screw step lengths" tab.

3. Enter the lengths in the "LEN" column of the length-specific table.


7.4.4.10 Updating the nominal diameters

Note

If the standardization is already being used, seek advice from your account manager before using the "Update NDs" button.

Requirements The standardization is fully configured.

Purpose This passes the nominal diameter range of the norm object on to the nominal-diameter-dependent tables of the norm object, the catalog for geometry standards, and the pipe parts catalog.

The nominal diameters in the nominal-diameter-dependent tables are updated without the existing entries being mixed up or deleted. Nominal diameters added to the standardization are always appended to the bottom of the tables.



3. Click the "Update NDs" button.



Result The following graphic illustrates how the "Update NDs" button forwards the nominal diameters to the nominal-diameter-dependent tables of the standardization, the standard catalog for geometry standards, and the pipe part catalog:

In detail, the following happens:

No. Action Object Tab > Attribute 1 The new nominal diameters added

to the nominal diameter range of the standardization are forwarded to:

The standardization: "CatSpec Catalog attributes" tab, "NomPipeSize-Dependent Table" table: Column "V.VC11" The pipe parts catalog and the catalog for geometry standards are also updated indirectly as a result. See 2, 3, and 4 in this table.

2 The values of "CatSpec.V.VC11" are forwarded via several stages to:

The standard catalog for geometry standards:

"StdVal Dimensions" tab, "NomPipeSize-Dependent Table" table: Column "V.VC11"



No. Action Object Tab > Attribute 3 The values of "CatSpec.V.VC11"

are forwarded via several stages to:

The pipe part catalog, to pipe parts with one nominal diameter:

"StdVal Local Dimensions (DN)" tab, "NomPipeSize-Dependent Table" table: Column "V.VC11"

Pipe parts with one nominal diameter: "VDM Data Sheet (DN1)" tab

4 The values of the "CatSpec.V.VC11" column are forwarded via several stages to:

The pipe part catalog:

Pipe parts with two nominal diameters: "VDM Data Sheet (DN1/DN2)" tab


"Catalog Attributes" tab (Page 202)


Setting the upper and lower limits of the DN range of a pipe part (Page 41)

7.4.4.11 Excluded from the configuration The following tabs of the standardization are not configured:

● "Local Dimensions (DN)" tab:

The tab is inherited to the pipe part catalog. There you can enter the local dimensions. See also chapter "StdVal Local Dimensions ..." tab (Page 139).

● "Screw lengths" tab:

The tab is inherited to the standard catalog for geometry standards, to the node in which the geometry of the screws is managed. There you enter the screw step lengths for the dimensions. See also chapter Creating a geometry standard or company standard for screw parts (Page 118).

● "Washer dimensions" tab:

The tab is inherited to the standard catalog for geometry standards, to the node in which the geometry of the washers is managed. There you enter the height of the washer for each dimension. The tab is also inherited to the pipe part catalog, There you define the local dimensions for washers.

● "Catalog attributes" tab:

The tab defines a table which serves as the inheritance source for the nominal-diameter-dependent tables of the standardization, the standard catalog for geometry standards, and the pipe part catalog. See also chapter "Catalog Attributes" tab (Page 202).

See also Updating the nominal diameters (Page 97)

"StdVal1" and "StdVal2" tabs (Page 195)

Administration 7.5 Managing the standard catalog for geometry standards


7.5 Managing the standard catalog for geometry standards

7.5.1 Note about managing and modifying the standard catalog for geometry standards

Note Follow the configuration rules

The standard catalog for geometry standards is managed by Siemens AG.

Only make modifications to the standard catalog for geometry standards if you know the configuration very well. Not managing the standard catalog correctly can lead to data inconsistencies in the database and take up significant additional time and effort.

7.5.2 Principle

Definition The standard catalog for geometry standards is one of the sources from which pipe parts can get their dimensions.

Standard catalog for geometry standards in the COMOS DB The COMOS DB is supplied with a catalog in which geometry standards based on DIN/EN and ANSI/ASME have been set up.

It is possible to define manufacturer-related geometry standards and factory standards, add missing DIN or ANSI standards, or amend existing standards.

Implementation of geometry standards in COMOS Geometry standards are implemented in COMOS in the form of base objects that contain basic tables. The actual dimensions are listed in basic tables in relation to the nominal diameter. See also chapter Structure objects and basic tables (Page 102).

If a pipe part uses a geometry standard, the attributes in which the dimensions are saved reference this type of basic table. In the engineering data, the dimensions of the pipe part are then read from the basic table and written to the attributes.

Parameterized access The standard catalog for geometry standards is parameterized by standards system, connection type, nominal pressure, and so forth. See also chapter Structure parameters (Page 102).



You do not usually link the pipe part directly to a basic table. Instead, you generate a calculation formula which returns the path to a basic table. The corresponding dimension is then read from the basic table.

The calculation formula comprises fixed and variable components. The variable components evaluate the structure parameters. The values of these parameters at the pipe part determine the basic table from which COMOS reads the dimensions for a pipe part.

See also chapter The "CatStd()" function (Page 155).

User-defined access versus internal calculation formulae COMOS uses internal calculation formulae in the following cases:

● 3D attributes required for calculation of the component dimensions are not set.

● The attributes are not set up at the "GD 3D geometry" tab.

See also chapter Internal formulae for calculating component dimensions (Page 189).

See also Legal notice (Page 14)

Base data ()

Adding EN/DIN / ANSI/ASME standards (Page 122)

Creating a new geometry standard or company standard (Page 110)

Structure of the standard catalog for geometry standards (Page 102)

Determining the pipe part geometry (Page 152)

7.5.3 Base data

Root node The standard catalog for geometry standards is managed in the base project on the "Base objects" tab.

You define the node underneath which it is located in the project properties.

In the COMOS DB The standard catalog is available under the node "@VIPER > @CATSTD Basic Tables, Industrial Standards".

Separate catalogs for piping and structural steelwork The geometry standards for piping and structural steelwork are managed in separate subnodes.



The manual describes only the structure of the "@VIPER > @ CATSTD > PP Piping" subnode.


7.5.4 Structure of the standard catalog for geometry standards

7.5.4.1 Structure objects and basic tables

Principle The standard catalog for geometry standards comprises two types of object:

● Structure objects: The nodes in the Navigator tree

They structure the catalog, based on is structure parameters. The function performed by the structure object differs dependent upon the layer on which it is located.

● Basic tables: The leaves in the Navigator tree

They save the dimensions of the pipe parts.

See also Structure parameters ()

7.5.4.2 Structure parameters

Overview The following parameters structure the standard catalog:

● Standards system (DIN, EN, ANSI, etc.)

● Flange standards system (DIN, EN, ANSI, etc.)

● Connection types

● Part types such as certain flanges, reducers, etc.

● Construction types such as various elbow radii

● Nominal pressure level

● Nominal diameter series

See also Adding information to the "RU Standard table Parametrics" standard table (Page 120)



7.5.4.3 Structuring by the "ParameterName" attribute

Note

Incorrect changes to the "ParameterName" attribute can lead to data inconsistencies and take up significant additional time and effort in the database.

Only make changes to the configuration of the "ParameterName" attribute if you have adequate training in this context.

Principle The standard catalog for geometry standards is structured by the "BMP.Rule ParameterName" attribute. Every object in the standard catalog has this attribute. Its value is dependent upon the function of the object.

COMOS evaluates the attribute in the following cases:

● Whenever a pipe part gets its dimensions via the "CatStd()" calculation formula and the calculation formula has been generated automatically by means of inputs in the "Define catalog access" window.

● Whenever the fixed programmed calculation formula is used for the dimensions of flange ends with a contact face

COMOS uses "ParameterName" to convert the calculation formula into the path entry for the basic table.



Values of "ParameterName" Assigned standard table: "@3D > 01 > RU Standard table Parametrics"

The following table shows which values "ParameterName" takes on for different layers of the standard catalog for geometry standards:

Function of the structure object Value of

"ParameterName" Type of geometry standard: The individual types of the geometry standard are located below the node "@VIPER > @CATSTD > PP Piping": 10 Basic geometry pipes 16 Basic geometry pipe parts 19 Face-to-face instrumentation 21 Basic geometry elbows 22 Basic geometry reducing elbows 30 Contact face dimensions 31 Flange dimensions 32 Blind flange dimensions 40 Thread/sleeve depths 41 Weld dimensions

"- - -"

Standards system: The standards are one or two layers underneath the geometry standard type: "... > 10 > 1 Rohraußendurchmesser": 1 acc. to DIN/EN 2 acc. to ANSI "... > 31 Flanschabmessungen": 1 acc. to DIN/EN 2 acc. to ANSI/ASME...

"Standard"

Flange standards system: "... > 31 > 1 nach DIN/EN": 1 Flange standards acc. to DIN ... 2 Flange standards acc. to EN 1092/T1 (2001) 4 Flange standards acc. to EN 1092/T1 (2007)

"Flange standard"



Function of the structure object Value of "ParameterName"

Connection type: "... > 31 > 1 > 1 Flanschnormen nach DIN...": 1 Face to face dimensions standard flange types acc. to DIN ... 2 Dimensions flared types acc. to DIN ... 100 Standard flange sheet (weld neck flange) acc. to DIN 2501/T1 101 Flange sheet with blind holes acc. to DIN 28117 140 Plain collar flange acc. to DIN... 200 Lap joint stub end loose flange acc. to DIN... 210 Lap joint stub end loose flange acc. to DIN... 220 Lap joint stub end loose flange acc. to DIN...

"Connection type"

Pressure stage: "... > 31 > 1 > 1 > 1 > 00 Vorschweißflansche nach DIN ...": 01 PN 1 similar DIN 2630 04 PN 2.5 similar DIN 2630 08 PN 6 similar DIN 2631 10 PN 10 similar DIN 2632 12 PN 16 similar DIN 2633 14 PN 25 similar DIN 2634 16 PN 40 similar DIN 2635 18 PN 63 similar DIN 2636

"Nominal pressure"

Other objects for structuring of catalog: For example: structure objects for construction lengths, pipe schedules, outside diameters.

"- - -"

See also The "CatStd()" function (Page 155)

Adding information to the "RU Standard table Parametrics" standard table (Page 120)

7.5.4.4 Naming system The objects in the catalog have a fixed naming system:

Function of the structure object Name Type of geometry standard The first two digits of the value entered for the corresponding

component type in the "Value 1" column of the "@3D > 01 > BC > 03Function code" standard table.

Standards system The value entered for the corresponding standards system in the "Value 1" column of the "@3D > 01 > NSYS Standards system" standard table.



Function of the structure object Name Flange standards system The value entered for the corresponding flange standards

system in the "Value 1" column of the "@3D > 01 > BC > 01 > 04 Flange standards system" standard table.

Connection type The value entered for the corresponding connection type in the "Value 1" column of the "@3D > 01 > BC > 02 Connection type" standard table.

Pressure stage ("0") + "<The value entered for the pressure stage in the "Value 1" column of the "@3D > 01 > 04 Nominal pressures" standard table> Examples: "04", "10"

Other objects for structuring of catalog.

Free, usually a counter.

7.5.4.5 The node for flange dimensions In the COMOS DB, flange dimensions are managed in the "@VIPER > @CATSTD > PP > 31 Flange Dimensions" node of the standard catalog for piping.

Structure of the node for flange dimensions No. Node Description 1 "31 Flange dimensions" Type of geometry

standard 2 "1 acc. to DIN/EN..." Standards system 3 "1 Flange standards acc. to DIN ..." Flange standards system 4 "1 Face to face dimensions standard flange types acc. to

DIN ..." Connection type

5 "00 Weld neck flanges acc. to DIN ..." Overall lengths 5 "05 Threaded flanges acc. to DIN ..." Overall lengths 5 "10 Rolled (socket) flange acc. to DIN ..." Overall lengths 5 "40 Plain collar flange acc. to DIN ..." Overall lengths 4 "2 Dimensions flared types acc. to DIN ..." Connection type 5 "00 Weld neck flanges acc. to DIN ..." Overall lengths 5 "10 Weld neck flange acc. to DIN ..." Overall lengths 5 "21 Slip-on lap joint lap joint acc. to supplier" Overall lengths 5 "30 Plain collar stub end flange acc. to DIN ..." Overall lengths 4 "100 Standard flange sheet (weld neck flange) acc. to DIN

..." Connection type

4 "101 Flange sheet with blind holes acc. to DIN 28117" Connection type 4 "140 Plain collar flange acc. to DIN ..." Connection type 4 "200 Lap joint stub end loose flange acc. to DIN..." Connection type 4 "210 Lap joint stub end loose flange acc. to DIN..." Connection type 4 "220 Lap joint stub end loose flange acc. to DIN..." Connection type 4 "221 Lap joint stub end loose flange acc. to ..." Connection type



No. Node Description 4 "230 Lap joint collar loose flange acc. to DIN..." Connection type 4 "401 Intermediate flange blade -> @Viper|@CATST" Connection type 3 "2 Flange standards acc. to EN 1092/T1 (2001)" Flange standards system 3 "4 Flange standards acc. to EN 1092/T1 (2007)" Flange standards system 2 "2 acc. to ANSI/ASME..." Standards system

7.5.4.6 The node for screw parts In the COMOS DB, the dimensions of the screw parts for piping are managed in the "@VIPER > @CATSTD > PP > 91 Basic Geometry Screw Catalog" node.

Structure of the node and structure by "ParameterName" The "... > 91 Basic Geometry Screw Catalog" node has the following structure:

Subnode layer 1 Subnode layer 2 Value of "ParameterName" "... > 01 Screws" "- - -" "... > 1 Screws to DIN/EN" "Standard" "... > 2 Screws to ASME" "Standard" "... > 02 Nuts" "- - -" "... > 1 Nuts to DIN/EN" "Standard" "... > 2 Nuts to ASME" "Standard" "... > 03 Washers" "- - -" "... > 1 Washers to DIN/EN" "Standard" "... > 2 Washers to ASME" "Standard" "... > 04 Extension sleeves" In progress -

For all nodes below the standards system layer, "ParameterName" has the value "- - -".

Structure of the node for screws acc. to DIN/EN There are subnodes for the screw types underneath the "... > 91 > 01 > 1 Screws to DIN/EN" node:

● "... > 01 Screws to DIN/EN"

● "... > 02 Screw bolts to DIN/EN"

● "... > 03 Stud bolts to DIN/EN"



The subnode has the following structure:

Layer Node Description Layer 1 The nodes for screw

geometry (step lengths) Define the screw geometry (step lengths). On the "Screw lengths" tab, enter the permissible screw step lengths dependent upon dimension. If no material numbers are required, the nodes on lower layers can be ignored.

Layer 2 The nodes for strength grades

This node is used if screws are assigned a material number dependent upon strength grade. In the COMOS DB, screws are defined without strength grades. Name: Same as "Value 1" from the corresponding standard table under "@3D > 01 > 19 > 03 Strength grades screws/nuts ...".

Layer 3 The base objects of basic tables

There is one base object per screw dimension. On the "Screw step lengths" tab, enter the weight and material number dependent upon length.

Structure of the node for nuts acc. to DIN/EN The "> 91 > 02 > 1 Nuts to DIN/EN" node has the following subnodes:

Layer Description Layer 1 The nodes for nut types, e.g. hexagonal nut. Layer 2 The nodes for nut standards.

On the "Screw dimensions" tab, enter the nut height, the overlap, and the pitch dependent upon dimension.

Layer 3 Nuts for screw bolts and stud bolts: The nodes for specific nut types On the "Screw dimensions" tab, enter the nut height, the overlap, and the pitch dependent upon dimension.

Structure of the node for washers acc. to DIN/EN The "... > 91 > 03 > 1 Washers acc. to DIN/EN" node has the following subnodes:

Node for the washer standard: On the "Washer dimensions" tab, enter the height of the washers dependent upon dimension.



Inheritance source of the tabs ● Screws:

– "BMP Descriptions" tab:

"@VIPER > @STD > CatTab > 91 > BMP Descriptions"

– "StdVal screw lengths" tab:

"@VIPER > @STD > <Name of norm object> > StdVal3 Screw lengths"

– "StdVal Screw step lengths" tab:

"@VIPER > @STD > <Name of norm object> > StdVal5 Screw step lengths"

The tab is added at the layer for strength grades.

● Nuts:



– "StdVal Screw dimensions" tab:

"@VIPER > @STD > <Name of norm object> > StdVal4 Screw dimensions"

● Washers:



– "StdVal Washer dimensions" tab:

"@VIPER > @STD > <Name of norm object> > StdVal6 Washer dimensions"

7.5.4.7 Attributes catalog of the standard catalog

Purpose The attributes catalog defines the tabs used in the standard catalog for geometry standards:

● The "Descriptions" tab:

Contains a cross-section drawing of the component and some managed attributes.

● The "Dimensions" tab:

– Defines a table in which the actual dimensions are entered in the basic tables as nominal-diameter-dependent values.

– The columns/geometry parameters in the table vary dependent upon pipe part type.

– The available columns are specified by the geometry parameters in the cross-section drawing.

Screw parts The tabs for screw parts are defined at the standardization, not in the attributes catalog.

The node which exists in the screw parts attributes catalog is reserved for future functions.



In the COMOS DB The attributes catalog is located in the "@VIPER > @STD > CatTab > CatStd Tabs Basic Tables" node.

Structure The structure of the attribute catalog is similar to the structure of the standard catalog. The layer for basic tables is missing.

See also Properties of the objects in the standard catalog for geometry standards (Page 205)

7.5.4.8 Standard tables for the standard catalog The following standard tables are relevant for the standard catalog:

● "@3D > 01 > RU Standard table Parametrics"

● "@3D > 01 > BC > 03 Function code"

● "@3D > 01 > NSYS Standards system"

● "@3D > 01 > BC > 01 > 04 Flange standards systems"

● "@3D > 01 > BC > 02 Connection types"

● "@3D > 01 > 04 Nominal pressures"

● "@3D > 01 > 05 Nominal diameters"

● "@3D > 01 > 03 > 10 Company standards"

● "@3D > 01 > 19 > 03 Strength grades screws/nuts ..."

● "@3D > 01 > 19 > 01 > 1 Screw dimensions to EN/DIN"

● "@3D > 01 > 19 > 02 Screw lengths"

7.5.5 Creating a new geometry standard or company standard

7.5.5.1 Workflow

Note

Only create a new geometry standard or company standard if you know the configuration of the standard catalog for geometry standards very well.



Procedure 1. In the database, check whether there is an entry in the standard table for standards

systems and a norm object for the new geometry standard or company standard. Create these if necessary. See also chapter Creating a standards system and standardization ().

2. For every standard you wish to implement, proceed as follows:

3. In the standard table for standards, create an entry for the standard.

See also chapter Adding a standard to the corresponding standard table for standards (Page 112).

4. In the attributes catalog of the standard catalog, create tabs for the new standard.

Not applicable for screw parts. See also chapter Amending the attributes catalog (Page 112).

5. In the standard catalog, add a node under which you manage the new standard underneath the node for the pipe part type. Manage the structure objects and basic tables here.

See also chapter Amending the standard catalog (Page 113).

6. Add the standard implemented in the standard catalog in Step 5 to the range of values for the standardization. See also chapter Adding the standard to the range of values of the standardization (Page 115).

7. Check whether the pipe part catalog has a node for the standard implemented in Step 5. If it does not, create the node and the required pipe parts underneath it.

See also chapter Expanding the pipe part catalog (Page 165).

8. Use the new standard in the pipe part catalog.

See also chapter Using the standard (Page 116).

7.5.5.2 Example

Implementing a company standard for welded pipes The following sections describe how to add new geometry standards or company standards to the standard catalog based on an example:

Implementing a company standard for welded pipes

To implement a company standard for welded pipes, you must enter the geometry standards for pipe outer diameters and pipe wall thicknesses.

7.5.5.3 Creating a standards system and standardization

Standards supplied with the COMOS DB In the COMOS DB, the standard catalog contains geometry standards based on the DIN/EN and ANSI/ASME standards systems.



Procedure If your engineering is to be based on a standards system other than DIN/EN or ANSI/AMSE (e.g. a company standard), you must check whether the standard table for standards systems already contains an entry for the corresponding company standard and whether a corresponding norm object exists.

Create these if necessary. See also chapter Implementing a new standardization (Page 85).

7.5.5.4 Adding a standard to the corresponding standard table for standards

Procedure Add an entry for the new geometry standard to the corresponding standard table for standards.

Example To add the company standards for welded pipes to the standard table of pipe standards, proceed as follows:

1. Open the "@3D > 01 > 03 > 02 Pipe standards" standard table.

2. Create two new entries there: one for the series of wall thicknesses of the company standard; another for the outer diameters of the company standard.

See also Amending parameters (Page 80)

7.5.5.5 Amending the attributes catalog Add tabs for the corresponding standard to the attributes catalog of the standard catalog for geometry standards.

The specific procedure you should follow is described based on the example of implementing a company standard for welded pipes.

Procedure 1. Select the "Base objects" tab in the Navigator.

2. Open the attributes catalog of the standard catalog.

In the COMOS DB, this is the "@VIPER > @STD > CatTab > CatStd Tabs Basic Tables" node.

3. Start by creating the tabs for the series of outer diameters. Proceed as described in Steps 4 through 8.



4. Select the "… > 10 > 1 Pipe Outer Diameters" node under "… > CatStd Tabs Basic Tables".

There are already standards system structure objects under this node, underneath which the tabs for geometry standards based on EN/DIN and ANSI/ASME have been defined.

5. Select one of the standards system structure objects, followed by "Copy" from the context menu.

6. Select the "… > 10 > 1 Pipe Outer Diameters" node, followed by "Paste" from the context menu.

COMOS creates a copy of the structure object and its tabs.

7. Open the properties of the new object and edit the following properties:

– "Name":

Enter the name of the standardization on which the company standard is based.

– "Description":

Enter a description, e.g. "Acc. to <description of the company standard>".

– "Attributes > Descriptions" and "Attributes > Dimensions" tabs:

The cross-section drawing and the geometry parameters of the nominal-diameter-dependent table are the same for all standards systems. Therefore, it is not usually necessary to define new columns in the nominal-diameter-dependent table on the "Dimensions" tab, or load a new legend on the "Descriptions" tab.

If necessary, change the unit of the geometry parameters on the "Attributes > Dimensions" tab: Right-click with the mouse in the column header and select the desired unit from the list.

8. Save your changes.

9. Start by creating the tabs for the series of pipe wall thicknesses. Proceed as described in Steps 10 and 11.

10. Under "… > CatStd Tabs Basic Tables", select the

"… > 10 Basic Geometry Pipes > 2 Pipe Wall Thicknesses" node.

11. Continue as described for the pipe outer diameters starting at Step 4.

7.5.5.6 Amending the standard catalog You create the structure objects and basic tables of the geometry standard or company standard in the node of the corresponding pipe part type.

The specific procedure you should follow is described based on the example of implementing a company standard for welded pipes.




2. Open the standard catalog for geometry standards. You can look up the node in which the standard catalog is located in the project properties.

In the COMOS DB, this is the "@VIPER > @CATSTD Basic Tables, Industrial Standards" node.

3. Start by creating the geometry standard for the pipe outer diameters. Proceed as described in Steps 4 through 11.

4. Select the node in which the geometry standards for the pipe outer diameters are managed.

In the COMOS DB: "@VIPER > @CATSTD > PP > 10 > 1 Pipe Wall Outer Diameters".

5. Select one of the underlying standards system structure objects, followed by "Copy structure" from the context menu.

The "Copy structure to ..." window opens.

6. Select the "@VIPER > @CATSTD > PP > 10 > 1 Pipe Wall Outer Diameters" node in the window and click the "OK" button.

The standards system structure object is copied and pasted under "…> 1 Pipe Wall Outer Diameters" along with the underlying structure objects and basic tables.

7. Open the properties of the new node and edit the following properties:

– "Name":

Enter the name of the norm object on which the company standard is based.

– "Description":


– "Descriptions" and "Dimensions" tabs:

Set the tabs from the attributes catalog as the inheritance source: Properties of the tabs, "General" tab, "Catalog tab" field

See also chapter Amending the attributes catalog (Page 112).

8. Open the properties of the structure objects one after the other underneath the new standards system node and edit the following properties:

– "Name"

– "Description"

– If necessary, the "Descriptions" tab, "WMF" attribute: The cross-section drawing



9. Open the properties of the basic tables one after the other and modify their properties:

– "Name":

Enter a name.

"ParameterName" of the object equal to "- - -": Name can be selected at will

"ParameterName" not equal to "- - -": Only values which can have the attribute addressed with "ParameterName" are permitted.

– "Description":

Enter the description of the pipe standard which you added to the standard table for pipe standards. See also chapter Adding a standard to the corresponding standard table for standards (Page 112).

– The "Dimensions" tab:

In the nominal-diameter-dependent table, delete the dimensions that were taken from the template and input the desired values.

Do not delete the nominal diameter values. The nominal diameters are inherited from the standardization. Do not interrupt the inheritance by inputting nominal diameters manually.

– "Descriptions" tab:

A cross-section drawing is displayed on this tab. The drawing shows which column/abbreviation of the basic table corresponds to which geometry parameter.

"Output", "Revision", and "Remarks on the standard" fields: Enter the corresponding management data.


11. Delete the structure objects and basic tables that are not required.

12. Create the geometry standards for the pipe wall thicknesses. Proceed as described in Steps 13 and 14.

13. Select the node in which the geometry standards for the pipe wall thicknesses are managed:

"@VIPER > @CATSTD > PP > 10 > 2 Pipe Wall Thickness Series"

14. Continue as described for the pipe outer diameters starting at Step 4.

7.5.5.7 Adding the standard to the range of values of the standardization


2. Navigate to the standardization and open its properties.


4. If the control group of the corresponding parameter is not in the visible area, move the sliders until it becomes visible.



5. Check whether the standard you added is within the range of values defined by the "from" and "to" fields.

If necessary, change the settings in the "from" and "to" fields.

6. Click the "Filter" button.

7. In the filter list, activate the option next to the entry for the standard you created.

Example To add the company standard for welded pipes to the range of values for the standardization, work in the "Pipe standards" control group, where you add the company standards for the outer diameters and the wall thickness series to the range of values for the standardization.

7.5.5.8 Using the standard The company standard for welded pipes is used as an example to describe how to use the geometry standard you have created.

Principle A geometry standard is used if the following conditions are met:

● There is a pipe part catalog which is based on the same standards system as the geometry standard.

For the example: There is a catalog for the company standard under "@VIPER > @PPC Pipe Part Catalogs".

● The pipe part catalog has a node for the geometry standard: the standards node

For the example:

There are nodes in which the geometry standards for the pipe outer diameters and the pipe wall thicknesses of the company standard are managed under "@VIPER > @PPC > <Company Standard> > 10 > 11 > 1 > 10 Welded Pipes".

● The standard node must have the following properties:

– Name: Counter

– Description: Name of the geometry standard

For the example: "<Name of the company standard>"

– Properties, "Attributes > Part description" tab, "Geometry description" control group:

"VSTDVS040 NSys" attribute: The standards system of the company standard is selected.

"VS040 <Pipe part type> standard" attribute: The geometry standard is selected in the assigned standard table. See also chapter Adding a standard to the corresponding standard table for standards (Page 112).



● The substructure of the standard node must be complete.

● The base objects for the actual pipe parts must be located on the lowest layer under the standards node. The pipe parts have a pointer to one of the basic tables of the geometry standard.

For the example:

– "OutD1 (AD)" attribute: Assign the basic table for outer diameters.

– "Wall thickness1 (WD)" attribute: Assign the basic table for wall thicknesses.

The "CatStd()" function (Page 155) describes how to proceed to assign the basic table.

Procedure 1. Check whether a pipe part catalog for the company standard already exists and if the

catalog is complete. This means:

– The pipe part catalog has a node for the pipe part type for which you have implemented a geometry standard.

– The node for the pipe part type has a subnode for the geometry standards you have implemented.

– The subnodes of the node for the geometry standard are complete.

– The nodes have the properties described above.

Please be sure to set a pointer to one of the basic tables containing the dimensions of the standard on one of the layers underneath the standard node.

2. Amend the pipe part catalog if necessary.




Result When you create a pipe part in the engineering data which uses your geometry standard and set its nominal pressure and the nominal diameter, COMOS evaluates the calculation formulae of the geometry attributes to determine which basic tables should be used. Depending on which nominal diameter has been set at the pipe part, COMOS reads the actual dimension values from the table and writes them to the pipe part:

1. Geometry attributes at the base object:

2. Geometry attributes at the engineering object before the nominal diameter is set:

3. Geometry attributes at the engineering object after the nominal diameter is set:

7.5.5.9 Creating a geometry standard or company standard for screw parts The workflow for creating a new geometry standard or company standard for screw parts differs in some ways from the workflow for the other pipe part types. The procedure you should follow is described using the example of a company standard for screw parts.

Procedure 1. Check to see if the standards system and standardization exist. Create them if

necessary. See also chapter Implementing a new standardization (Page 85).

2. In the standard table for standards, create an entry for the new standard.

For screw parts, this is the "@3D > 01 > 03 > 09 Screw standards" standard table. See also chapter Adding a standard to the corresponding standard table for standards (Page 112).

3. Make a copy of one of the nodes under which the geometry standards based on EN/DIN and ANSI/ASME are based in the standard catalog for geometry standards. See also chapter Amending the standard catalog (Page 113).

Example: To create a company standard for screws, copy one of the standards system structure objects under "@VIPER > @CATSTD > PP > 91 > 01 Screws".



4. Edit the newly created standards system structure object.

Set the following properties:

– "Name" property:

Enter the name of the norm object on which the company standard is based.

– "Description" property:


– Save your entries.

5. The subsequent steps depend upon whether you are creating a standard for screws, nuts, or washers. They are described in detail below.

6. As with the other pipe part types, add the new geometry standard to the range of values of the standardization. See also chapter Adding the standard to the range of values of the standardization (Page 115).

7. Assign the geometry standard to an appropriate screw part. Amend the pipe part catalog first if necessary.

Proceed as described in chapter Using the standard (Page 116) for the other pipe part types.

The attributes catalog does not have to be amended.

Creating a geometry standard for screws Proceed as described above. Once you have completed Step 4, do the following:

1. Open the node of the standards system structure object you created in Step 4 above.

You see the structure objects for the screw types (e.g. screws, screw bolts).

2. For each structure object which defines a screw type: Open the properties and enter a description, e.g. "<screw type> acc. to <description of the company standard>".

3. For each structure object which defines a screw type: Open the node.

You see the objects defining the geometry standards of the screws.

4. For each object which defines a geometry standard:

– Open the properties.

– Modify the name and description.

– Enter the screw step lengths on the "Attributes > Screw step lengths" tab.


5. For each object which defines a geometry standard: Open the subnodes for the strength grades.

You see the basic tables.



6. For each basic table:

– Open the properties.

– On the "Attributes > Screw step lengths" tab, enter the weight in the "WT" column and the material number in the "ID" column.

It is standard practice to enter the weight per thousand items.


7. Continue as described at the start of the section under "Procedure", starting at Step 6.

Creating a geometry standard for nuts and washers Proceed as described above. Once you have completed Step 4, do the following:

1. Open the node of the standards system structure object you created in Step 4 above.

For nuts:

– You see the structure objects for the nut types.

For washers:

– You see the objects defining the geometry standards (basic tables).

2. For nuts:

– For each structure object which defines a nut type: Open the properties and enter a description, e.g. "<nut type> acc. to <description of the company standard>".

– For each structure object which defines a nut type: Open the node.

You see the objects defining the geometry standards for nuts (basic tables).

3. For each basic table: Open the properties.

For nuts: Enter the following data for all dimensions on the "Attributes > Screw dimensions" tab:

– "M" column: The nut height

– "UEB" column: The overlap

– "P" column: The pitch

For washers:

Enter the height of the washer in the "M" column on the "Attributes > Washer dimensions" tab.


5. Continue as described at the start of the section under "Procedure", starting at Step 6.

7.5.6 Adding information to the "RU Standard table Parametrics" standard table You can add new parameters to the "@3D > 01 > RU Standard table Parametrics" standard table. COMOS then takes these parameters into account when calculating the basic tables.



Procedure 1. Create a new entry in the standard table:

– "Name": Sequential counter, assigned automatically

– "Description": Description of the parameter, e.g. "Contact face 2"

– "Value 1": Name of the attribute evaluated by the calculation formula. For the example Contact face 2: "VC24

2. Assign the new entry to all structure objects from the standard catalog for geometry standards corresponding to the structure characteristic created in Step 1.

Do not modify the layers of the standard catalog which define the following structure characteristics:

– Standard

– Flange standard

– Connection type

– Nominal pressure

3. In the pipe part catalog, generate a calculation formula which uses the new parameter.

Result When using the calculation formula to access the standard catalog, COMOS also takes the parameters you have defined into account.

Fixed programmed attributes For compatibility reasons, numbers rather than attribute names are entered in the "Value 1" column in the COMOS DB for the standard table entries listed below. The following attributes are assigned to the numbers in the software:

"Name" column "Description" column "Value 1" column Attribute "1" "Standard" "1" "GD.VSTD Standard" "2" "Flange standard" "2" "GD.VFLG Flange

standard" "3" "Connection type" "3" "GD.VC#3 Connection

type" "4" "Nominal pressure" "4" "GD.VC#2 Nominal

pressure"

You can enter the attribute names instead of the numbers. If you do this, you must reset the value in the standard catalog for geometry standards wherever one of these values was set for "ParameterName".

See also Structuring by the "ParameterName" attribute (Page 103)

The "CatStd()" function (Page 155)



7.5.7 Adding EN/DIN / ANSI/ASME standards

7.5.7.1 Creating a missing standard The standard catalog contains numerous standards based on EN/DIN and ANSI/ASME. If a standard is missing, you can create it.

Note

Seek instructions from your account manager before amending the standards based on EN/DIN and ANSI/ASME.

Procedure 1. Click on the "Base objects" tab in the Navigator.

2. Add the new geometry standard to the corresponding standard table for standards. See also chapter Adding a standard to the corresponding standard table for standards (Page 112).

3. Open the node of the pipe part type in the standard catalog for geometry standards.

4. Dependent upon how the node of the pipe part type is structured: Open the node of the standards system on which the new geometry standard is to be based and navigate to the layer on which the standards are managed.

5. Select an existing standards node, followed by "Copy" from the context menu.

6. Select the superordinate node, followed by "Paste" from the context menu.

COMOS creates a copy of the standard node, its structure objects and basic tables.

7. Open the properties of the copy and give the new standard a suitable name and description. If necessary, load a new cross-section drawing on the "Descriptions" tab, in the "WMF" attribute.

8. Edit the structure objects underneath the new standard node:

– Change the name and the description.

– Create new structure objects or delete nodes if necessary.

Example: Delete nodes for invalid pressure stages on the nominal pressure stage layer or amend the layer by adding more pressure stages.

9. For the basic tables:

– Open the properties and click on the "Dimensions" tab.

– Transfer the dimensions from the standard to the basic table.

10. Add the new standard to the range of values of the standardization. Proceed as described for the implementation of a company standard. See also chapter Adding the standard to the range of values of the standardization (Page 115).

11. Assign the standard to a suitable pipe part from the pipe part catalog. See also chapter Using the standard (Page 116).



Procedure for screws 1. Proceed as described under "Procedure" for the other pipe part types up to Step 4.

Example for a node under which screw standards are managed:

"@VIPER > @CATSTD > PP > 91 > 01 > 1 > 02 Screw bolts to DIN/EN"

2. Open the node for the screw standards.

You see the structure objects of the existing standards.

3. Copy one of the standard structure objects and paste the copy.

4. Edit the following properties of the copy:

– "Name": Enter the name of the new screw standard.

– "Description": Enter the description of the new screw standard.

– "Attributes > Screw lengths" tab: Enter the screw lengths.

5. Open the node of the new standard. You will see the structure objects for the strength grades.

6. If required: Edit the structure objects for the strength grades. Create new strength grades or delete some.

7. For all strength grades: Open the node for the strength grade.

You see one basic tables for each dimension.

8. For all basic tables: Open the properties and enter the weight and the material number on the "Attributes > Screw step lengths" tab ("M" and "ID" columns of the dimension-specific table).

Procedure for nuts 1. Proceed as described under "Procedure" for the other pipe part types up to Step 4.


"@VIPER > @CATSTD > PP > 91 > 02 > 1 > 01 Hex. nuts/overlaps to DIN/EN"

2. Copy the node of an existing standard structure object as described above, paste the copy, and edit the following properties:

– "Name": Enter the name of the new geometry standard for nuts.

– "Description": Enter the description of the new geometry standard for nuts.

– "Attributes > Screw dimensions" tab: Enter the nut height and the overlap for all dimensions in the "M" and "UEB" columns. Optional: Enter the pitch in the "P" column.



Procedure for washers 1. Proceed as described under "Procedure" for the other pipe part types up to Step 4.


"@VIPER > @CATSTD > PP > 91 > 03 > 1 Washers to DIN/EN"

2. Copy the node of an existing standard structure object as described above, paste the copy, and edit the following properties:

– "Name": Enter the name of the new standard for washers.

– "Description": Enter the description of the new standard for washers.

– "Attributes > Washer dimensions" tab: Enter the height of the washer for all dimensions in the "M" column of the dimension-specific table.

See also Creating a new geometry standard or company standard (Page 110)

7.5.7.2 Supplementing values in the basic tables

Note

Seek instructions from your account manager before amending the basic tables for the standards based on EN/DIN and ANSI/ASME.

Do not enter the nominal diameter values manually. Only use the nominal diameters taken from the standardization.

Do not delete or move rows in the nominal-diameter-dependent table.

Principle You can supplement the dimensions entered in the basic tables.

This is necessary, for example, if you have expanded the nominal diameter range of the standardization and pressed the "Update NDs" button on the "Characteristic Definition" tab: The values updated by COMOS include the nominal diameter values entered in the basic tables in the "V.VC11 Nominal diameters" column on the "Dimensions" tab. The new nominal diameters are appended to the bottom of the basic tables (the rows in the nominal-diameter-dependent table are not moved or deleted).

Procedure Enter the dimensions for the new nominal diameters in the basic tables on the "Dimensions" tab.

See also Updating the nominal diameters (Page 97)

Administration 7.6 Administering pipe part catalogs


7.6 Administering pipe part catalogs

Overview The COMOS DB is supplied with pipe spec suitable pipe part catalogs or "PPC". The catalogs are located in the node:

"@VIPER > @PPC Pipe part catalogs".

The catalogs are nominal-diameter-independent. The nominal-diameter-dependent values are parameterized so that one base object bundles the characteristics for all nominal diameters.

The nominal-diameter-dependent values are entered in the engineering data as soon as a user actually assigns a nominal diameter to a component. This minimizes the time and effort required to maintain the base data.

Insulation catalog See also chapter Insulation catalog (Page 73).

Use of pipe part catalogs ● In the COMOS VIPER product family

● In the P&ID module for pipe spec mapping

7.6.1 Structure of the pipe part catalogs

Principle ● The pipe part catalogs have the following basic structure:

Standards system > Pipe part type > Connection type > Material > Pipe parts

This means the pipe part catalogs are administered separately by standards system.

The COMOS DB is supplied with catalogs based on the standards systems DIN/EN and ANSI/ASME.

● The flange node has the following structure: Connection type > Pressure stage > Material

Example The following are excerpts of the structure from the catalog to EN/DIN:



Pipes "@VIPER > @PPC > 1 > 10 Pipes":

"11 Standard pipes" "1 General pipes" "10 Welded pipes" "01 DIN EN 10220 Pipes" "02 DIN 2448 Pipes" "B carbon steel" "01 Welded pipe [ ][ ]-Pipe seamless-DIN 2448" "2 Welded pipe [ ][ ]-Pipe seamless-DIN 24" "3 Welded pipe [ ][ ]-Pipe seamless-DIN 24" "4 Welded pipe [ ][ ]-Pipe seamless-DIN 24" "5 Welded pipe [ ][ ]-Pipe seamless-DIN 24"

Valves "@VIPER > @PPC > 1 > 60 Valves":

"61 2-way valves" "11 Strainer" "12 Filter" "13 Steam trap" "14 Sight glass" "15 Hose coupling" "30 Valves" "10 Welded" "20 Flanged" "40 Thread" "01 DIN 3202" "A casting" "B unalloyed" "0010 Valve[ ][ ]-Stop valve, thread inside DIN ..." "01 Valve[ ][ ]-Stop valve, thread inside DIN ..."

See also Legal notice (Page 14)



7.6.1.1 Naming system The naming system for pipe part catalogs facilitates orientation within the base data. The catalogs use the following system:

Layer Name Standards system Standard table "@3D > 01 > NSYS Standards system": The value entered for

the corresponding standards system in the "Value 1" column. Pipe part type Standard table "@3D > 01 > BC > 01> 03 Function code": The first two digits

entered for the corresponding pipe part type in the "Value 1" column. Subsequent layers

No fixed system. The naming structure is loosely based on the function code of the pipe parts for better orientation. The number of digits in a name which are based on the function code varies. Examples: Base object node for weld neck flanges:

Function code = "31100"

Name = "@3D > @PPC > 1 > 31 > 1 > 00" Base object node for compensators:

Function code = "55110

Name = "@3D > @PPC > 1 > 54 < 55 > 02" Pressure stage (only for flanges)

Standard table "@3D > 01 > 04 Nominal pressures": The value of the corresponding pressure stage entered in the "Value 1" column If "value 1" < 10: "0" as prefix.

7.6.1.2 Overview of the tabs and their inheritance sources The tabs for the pipe parts are already created at the root node of the pipe part catalogs. Some tabs are still empty on this layer; their inheritance source is set lower down.

Inheritance sources There are the following inheritance sources:

● The subnodes of "@VIPER > @Y > CHP > PP Tabs Piping":

Name Description "GD" "3D geometry" Inheritance source: Set on the connection type layer "FT" "Fabrication" "NDRange" "Display for nominal diameter

range" "SYSISO" "Local Dimensions (DN)" "VDD" "Part attribute" "VTX" "Text blocks" "VXC" "Interface codes"

Inheritance source: Set in the root node of the pipe part catalogs



Name Description

Inheritance source: Set on the standards system layer On the pipe part type layer, the following attributes are added to the "Geometry description" control group. All types with the exception of "... > 81 Secondary supports" and ... > 91 Screw parts": Name: "VS040"

Description: Type-specific: "Pipe standard", "Form st. standard", "Flange standard" or "Valve standard"

Name: "VSTDVS040"

Description: "Standard" For pipes and elbows: Name: "VS010"

Description: "Construction type" Name: "VSTDVS010"

Description: "Standard"

"VDS" "Part description"

For flanges: Control group "Connector description straightway" For the input:

Name: "VS013"

Description: "Input" For the output:

Name "VS023"

Description: "Output" For the connection types:

Names: "VS015", "VS025"

Description: "Norm AnschlForm 1" Standards system for the connection types:

Name: "VSTDVS015"

Description: "Standard" For contact face 1 and/or contact face 2:

Names: "VS014", "VS024"

Description: "Contact face" For the standard of the first and second contact face:

Names: "VS050", "VS055"

Description: "ContactFaceStandard1" For the standards system of the contact face:

Name: "VSTDVS050"

Description: "Standard"



Name Description For branches: Control group "Connector description branch" For outputs 3 and 4:

Names: "VS033", "VS043"

Descriptions: "Output 3", "Output 4" For the standard of the third and fourth connection type:

Names: "VS035", "VS045"

Descriptions: "StdConnType 3", "StdConnType 4"

● "@VIPER > @STD > CatTab > VDM Tab Data Sheet":

The node is the inheritance source for the following tab:

Name Description "VDM" "Data Sheet" Inheritance source: Set on the pipe part type layer

Inheritance source for pipe parts with one nominal diameter:

"@3D > @STD > CatTab > VDM > 1 > 1 > VDM Data Sheet (DN1)" Inheritance source for pipe parts with two nominal diameters:

"@3D > @STD > CatTab > VDM > 1 > 2 > VDM Data Sheet (DN1, DN2)"

● "@VIPER > @STD Standardizations":

Name Description "StdVal1" "Local Dimensions

(DN)" Inheritance source: Set on the standards system layer After setting the inheritance source, delete the "1" from the name of the tab manually.

"StdVal2" "Local Dimensions (DN1/DN2)"

Only for pipe part types with two nominal diameters. Overwrites the inheritance source set on the standards system layer on the pipe part types layer. After setting the inheritance source, delete the "2" from the name of the tab manually.

● "@PDMS > @Y > @CHP > 03 > 03 Comos PPC Object":

Name Description "E3D" "External 3D Interface" The inheritance source is set at the root node of the pipe part catalogs.

You only need the tab if you are also using the pipe part catalog in the COMOS PDMS Integration module.

● "PLM > Y > CTAB Microstation Catalog Tabs":

Name Description "CM3D" "Plant modeler

devices" The inheritance source is set at the root node of the pipe part catalogs. You only need the tab if you are working with the Plant Modeler.



● "@VIPER > @PPC Pipe Part Catalogs":

Name Description "DM" "Data Maintenance" The tab is created at the root node of the pipe part catalogs. "Nts" "Remark" The tab is created at the root node of the pipe part catalogs.

See also "VDS Part description" tab ()

"VDD Part attribute" tab (Page 133)

"VDM Data Sheet" tab (Page 137)

"StdVal Local Dimensions ..." tab (Page 139)

"VTX Text blocks" tab (Page 141)

"VXC InterfaceCodes" tab (Page 142)

"SYSISO System information" tab (Page 142)

"FT Fabrication" tab (Page 143)

"E3D External 3D Interface" tab (Page 144)

"GD 3D geometry" tab (Page 144)

7.6.2 "VDS Part description" tab Name "VDS" Description "Part description" Inheritance source See also chapter Overview of the tabs and their inheritance sources (Page 127). Function You describe the pipe part here. Attribute scripts Scripts for standards system attributes and their dependent attributes: See

also chapter Parameters dependent upon on the standards system (Page 209).

"GetDisplayValue": See also chapter GetDisplayValue() (Page 213).



"Part description" control group Name Description Function "VXPGR" "Part group" Standard table: "@3D > 01 > BC > 01 > 01 Group"

Seek advice from your account manager before making any changes to the entries in the standard table.

"VS080" "<Type>] type" (pipe type, flange type, etc.)

Standard table: The standard table of the corresponding pipe part type under "@3D > 01 > BC > 01 > 02 Types"

Seek advice from your account manager before making any changes to the entries in the standard tables.

"VS06", "VS07", "VS08", "VS09"

"Part name", "Part variant", "Part option", "Part description"

You can create variants of a pipe part. The variants can have options.

Script block "OnChange": – Purpose: Integration of attribute values into the Navigator

description text – Implementation: See also chapter Navigator description

from pipe part attributes (Page 213).

"Norm description" control group Name Description Function "VSTDVS041" "Standard" Standards system to control dependent attributes

Registered as dependent attribute: "VS041"

"VS041 " "Technical norm"

Dependent upon on the standards system Standard table: "@3D > 01 > 01 Technical norms"

"VS046" "Configuration" Self-explanatory

"Geometry description" control group Name Description Function "VS0#2" "Nominal

pressure" Standard table: "@3D > 01 > 04 Nominal pressures" Script block "OnChange()":

– Purpose: Forwarding of a new nominal pressure to the "GD.VC0#2 Nominal pressure" attribute

– Take over implementation from the COMOS DB, from the standards system layer of the pipe part catalog

"#" stands for the index number of the connector. "VSTDVS017" "NSys" Standards system to control dependent attributes

Registered as dependent attribute: "VS017"



Name Description Function "VS017" "Standard" General standard that corresponds to the geometry

description, dependent upon the standards system Standard table: "@3D > 01 > 03 Standards"

"VSTDVS040" "NSys" Standards system to control dependent attributes Registered as dependent attribute: "VS040"

"VS040" "Pipe standard", "Form st. standard", "Flange standard" or "Valve standard"

Dependent upon on the standards system Standard table: Table of the corresponding pipe part type

under "@3D > 01 > 03 Standards"

"VSTD010" "Standard" Standards system to control dependent attributes Registered as dependent attribute: "VS010"

"VS010" "Construction type"

Standard table: "@3D > 01 > 10 > 01 Construction type elbows metric"

"VS500" "WThickness" Standard table: "@3D > 01 > 08 > 09 > 2 > 01 Schedule for welded and seamless pipes"

For pipes and elbows Name Description Function "VSTDVS010" "NSys" Standards system to control dependent attributes

Registered as dependent attribute: "VS010" or "VS101"

Pipes: "VS010"

Elbows: "VS101"

Pipes: "Construction type"

Elbows: "Construction type"

Dependent upon on the standards system Standard table:

– Pipes: "@3D > 01 > 09 Outer diameter" – Elbows: "@3D > 01 > 10 Construction type elbows

metric" For pipes: Script block "OnChange"

– Purpose: Integration of attribute values into the Navigator description text

– Implementation: See also chapter Navigator description from pipe part attributes (Page 213).



For flanges: Control group "Connector description straightway" Name Description Function "VS013" "Input" Description of the input "VS023" "Output" Description of the output VSTDVS015" "Standard" Standards system to control dependent attributes

Registered as dependent attributes: "VS015", "VS025", "VS035", "VS045"

"VS015", "VS025"

"StdConnType1", "StdConnType2"

Dependent upon on the standards system Standard table: "@3D > 01 > 03 > 07 Connector standards"

"VS014", "VS024"

"Contact face 1","Contact face 2"

Dependent upon on the standards system Standard table: "@3D > 01 > 06 Dichtformen" Script block "OnChange()":

– Purpose: Forwards the value to the "GD.VC14" and "GD.VC24" attributes.

– Take over implementation from the COMOS DB, from the pipe part types layer of the pipe part catalog

For branches: Control group "Connector description branch" Name Description Function "VS013" "Outlet 3" Description for outlet 3 "VS23" "Outlet 4" Description for outlet 4 "VS035", "VS045"

"StdConnType3""StdConnType4"

Dependent upon on the standards system Standard table: "@3D > 01 > 03 > 07 Connector standards"

7.6.3 "VDD Part attribute" tab Name "VDD" Description "Part attribute" Inheritance source See also chapter Overview of the tabs and their inheritance sources

(Page 127). Attribute scripts For all standards system attributes and their dependent attributes: See also

chapter Parameters dependent upon on the standards system (Page 209). "GetDisplayValue" see GetDisplayValue() (Page 213).



7.6.3.1 Control group "Pressure/temperature dependency"

Purpose The tables in the control group save the data for the temperature rating of the pipe part.

The values entered here are evaluated on the "Diagram" tab in the PipeSpec Designer and displayed in a diagram.

Attributes ● Table"VS100 T":

Column name Column description "TMIN" "Tmin" "TMAX" "Tmax" "T1" to "T6" "Temp1" to "Temp6"

● Table "VS101 P":

Column name Column description "PN1" "NominalPressure1" "PN2" "NominalPressure2" "P1" to "P6" "Pressure1" to "Pressure6"

Example:

● Blue line: Rating curve

● Red line: Impermissible rating point of the component

● Green line: Permissible rating point of the component



7.6.3.2 Control group "Materials – List of objects"

Attributes Name Description Function "VSTDVS001" "Standard" Standards system attribute to control dependent attributes

Registered as dependent attributes: "VS001", "VS002" Standard table: "@3D > 01 > NSYS Standards systems".

"VS001" "Wst.Norm" The material standard, depending on the standards system. Standard table: "@3D > 01 > 03 > 01 Material standards".

"VS002" "WSt The material, depending on the standards system Standard table: "@3D > 01 > 07 Materials". Script block "OnChange":

– Purpose: Sets the material number "VST004 Mat.code" depending on "VS002" and adds the material to the Navigator description.

– Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02"

– See also chapter Navigator description from pipe part attributes (Page 213).

"VS004" "Mat. code" The material number Standard table: "@3D > 01 > 07 Materials": Value 3 of the

standard table entry set in "VS002 Mat."

"VS015" "Pos" Table in which the individual parts of the pipe part are described.

Note Set pointer to material object

You can adapt the database so that the materials are made available as objects instead of in a standard table. In this case, you set a pointer to a material object. If you wish to do this, please consult your account manager.


Parameters dependent upon on the standards system (Page 209)



7.6.3.3 Control group "Technical Terms of Delivery"

Purpose The control group describes the individual parts of the pipe part with regard to their delivery conditions.

Attributes Name Description Function "VS120" "Rem." Comment field "VSTDVS114" "Standard" Standards system attribute to control dependent

attributes Registered as dependent attribute: "VS114" Standard table: "@3D > 01 > NSYS Standards

system"

"VS114" "Standard" The standard for the technical terms of delivery, depending on the standards system

Standard table: "@3D > 01 > 02 Technical Terms of Delivery"

"VS106" "No." Table in which the individual parts of the pipe part are described with regard to their technical terms of delivery.

See also Parameters dependent upon on the standards system (Page 209)

7.6.3.4 Control group "Remarks Supply Information" The control group contains a memo field (ASCII) for further notes concerning the technical terms of delivery.

Name: "VS047"

Description: "Rem."

See also Parameters dependent upon on the standards system (Page 209)

7.6.3.5 Control group "Component fabrication"

Purpose The control group contains manufacturer information about the pipe part.



Attributes Name Description Function "VS112" "Product type" The product type "VSTDVS113" - Standards system attribute to control dependent attributes

Registered as dependent attribute: "VS113" Standard table: "@3D > 01 > NSYS Standards system"

"VS113" "Standard" The fabrication standard, depending on the standards system

Standard table: "@3D > 01 > 03 Standards"

"VS111" "Identification" The identification. "VS110" "Standard" The identification standard, depending on the standards

system Standard table: "@3D > 01 > 03 Standards"

"VSTDVS110" - Standards system attribute to control dependent attributes Registered as dependent attribute: "VS110" Standard table: "@3D > 01 > NSYS Standards system"


7.6.3.6 Control group "Additional texts"

Attributes The control group contains auxiliary fields, which can be used in reports, for example:

Name Description Function "VS108" "List of objects" "VS107 " "Designation" "VS109" "Remark"

Self-explanatory. No special properties.

7.6.4 "VDM Data Sheet" tab Name "VDM" Description "Data Sheet" Inheritance source "@Viper > @STD > CatTab > VDM -Data Sheet Tab" Function Saves part-specific data dependent upon the nominal diameter



See also Overview of the tabs and their inheritance sources (Page 127)

7.6.4.1 Control group "Manufacturer data"

Attributes The control group contains auxiliary fields, which can be used in reports, for example:

Name Description Function "VS115" "Name" "VS116" "Type" "VS117" "Identification" "VS118" "Test

certification" "VS119" "Remarks"

Information on the manufacturer. No special properties.

7.6.4.2 NomPipeSize-Dependent Table ("V")

Content of the nominal-diameter-dependent component table The table saves part-specific data dependent upon the nominal diameter:

● Physical data (weight, volume, friction losses)

● Norm object data for linking with ERP systems (part number, overall material number for Merian, SAP-specific data)

● Other data that is relevant for the interfaces (material class, part ID, storage number, order numbers, STYPE).

Properties of the nominal diameter column(s) The properties and values of the nominal diameter column(s) are inherited. Do not change the values directly at the pipe part.

● Properties and values in the "VC11 Nominal diameter" column are inherited via several layers by the standardization: "CatSpec" tab, "V.VC11 " attribute.

● For pipe parts with two nominal diameters:

Properties and values in the "VC11" and "VC21" columns are inherited from the attributes catalog, where they had been input manually on the catalog tab:

"@3D > @PPC > @Normierung > CatTab > VDM > 1 > 2 > VDM Data Sheet (DN1,DN2)".



Properties of the table and its columns ● Name of the table: "V"

● Description of the table: "Nominal-diameter-dependent table"

● Column "V.BESTNR": Order no.

● Column "V.BTID": Part

● Column "V.BTNR": Component number

● Column "V.CV": Losses due to friction

● Column "V.GEW": Weight

● Column "V.GMNR": Overall material number from Marian

● Column "V.LAGERNR": Stock no.

● Column "V.LMATKLASSE": Material class

● Column "V.SAP"

● Column "V.VOL": Volume

● Pipe parts with one nominal diameter: Column "V.VC11": Nominal diameter DN1

● Pipe parts with two nominal diameters: Column "V.VC21": Nominal diameter DN2"

See also "Catalog Attributes" tab (Page 202)

7.6.5 "StdVal Local Dimensions ..." tab Name "StdVal" Description For pipe parts with one nominal diameter:

"Local Dimensions (DN)" For pipe parts with two nominal diameters:

"Local Dimensions (DN1/DN2)" Inheritance source See also chapter Overview of the tabs and their inheritance sources (Page 127). Function Saving local dimensions



Attributes Name Description Function "VSTD" "Standard" Not relevant. "VS200" "Table import" Table for the Isometrics interface (not for nuts and bolts). "V" "Nominal-diameter-

dependent table" You manage deviations from the dimensions entered in the geometry standards and for the pipe specs in this table. The local dimensions of the pipe part are used if you enter the calculation formula "Cat()" in the geometry attributes on the "3D geometry" tab. The table is inherited from the norm object. All columns that are required have already been defined at the norm object.

Columns in the nominal-diameter-dependent table for pipe parts with one nominal diameter Name Descripti

on Function Comment

"VC11" Nominal Diameter 1"

The nominal diameters are inherited from the norm object and may not be changed at the pipe part. If the "Update NDs" button is pressed at the standardization, any new nominal diameters that have been added are appended to the bottom end of the column. Old entries are not deleted or moved. See also chapter Updating the nominal diameters (Page 97).

Values input automatically

"L", "L1"

"L", "L1"

Part lengths

"T", "T1"

"T", "T1"

Part lengths

"R" "R" Radius "d1", "d2"

"d1", "d2"

Auxiliary geometry parameters (depending on the pipe part)

"s2", "h3", "BD"

"s2", "h3", "BD"

Weld neck flange parameters

"exz" "exz" Eccentricity "a1", "b1", "a2", "b2"

"a1", "b1", "a2", "b2"

Auxiliary parameters for drives

"P1" to "P10"

"P1" to "P10"

Other dimensions

Values input by the user

The column caption corresponds to the legend of the cross-section drawing on the "3D geometry" tab.



Columns in the nominal-diameter-dependent table for pipe parts with two nominal diameters The table has the same columns as for pipe parts with one nominal diameter, plus the following column:

Name Description Function Comment "VC21" "DN2" The nominal diameters are inherited from the

standardization and may not be changed at the pipe part: New values are inherited to the pipe parts catalog as soon as they are input at the standardization on the "StdVal2" tab.

The user inputs values at the standardization.

See also "Catalog Attributes" tab (Page 202)

7.6.6 "VTX Text blocks" tab Name "VTX" Description "Text blocks" Inheritance source See also chapter Overview of the tabs and their inheritance sources

(Page 127). Function Saving texts describing components

Control group "Additional texts" Name Description Function "VST02" "Standardization" To create a norm object key "VST03" "List of objects (pipe

spec) text" Self-explanatory

"VST05" "Order text" Self-explanatory



Control group "Component created text" Name Description Function "VST01" "Description" Parameterizable text which creates a string describing the

part by concatenating the values of various pipe part attributes. An expression consisting of TValue calculation formulae is input in the field. Pipe part attributes are passed to the calculation formulae. The attribute values are then evaluated and linked with each other. You can use the resulting string as a description in the Navigator. See also chapter Navigator description from pipe part attributes (Page 213).

"Btn01" "Update component description"

Button to update the component description

Notation:

● "=": Introduces the expression

● "TValue": The function call

● "(...)": String parameter of TValue

● "&": AND-operator to concatenate the resulting substring

● "_": Line break which is ignored in the resulting string

The specific attributes read out depend upon the component and are usually linked to the standard. Some attributes are not set until the engineering data stage.

TValue calculation formula You find more information on this topic in the "System Type Properties" manual, keyword "TValue".

7.6.7 "VXC InterfaceCodes" tab Name "VXC" Description "Interface codes" Inheritance source See also chapter Overview of the tabs and their inheritance sources

(Page 127). Function Saving interface-related data

7.6.8 "SYSISO System information" tab The tab is used in the Isometrics module.



You find more information on this topic in the "Isometrics" manual, keyword "SYSISO System information".

7.6.9 "CM3D Plant modeler devices" tab Name "CM3D" Description "Plant modeler devices" Inheritance source See also chapter Overview of the tabs and their inheritance sources

(Page 127). Function Speeds up navigation to a pipe component placed in Microstation® 3D by

Bentley.

Attributes Name Description Function "DGN" "DGN" The DGN file in which the component has been saved. "ID" "ID" The cell ID of the component in Microstation. "Model" "Model" The model of the DGN file from "DGN".

Using the SystemUID to search for missing tab If the tab is missing, the SystemUID is used as the basis for navigation. All files, models and cells are scanned in this process. Navigation can take some time if larger quantities of data are searched.

7.6.10 "DM Data Maintenance" tab The tab is used for data management.

7.6.11 "FT Fabrication" tab The tab is used in the Isometrics module.

You find more information on this topic in the "Isometrics" manual, keyword "FT Production".

7.6.12 "Nts Remarks" tab You can enter remarks about the pipe part here.



7.6.13 "E3D External 3D Interface" tab This tab is used to exchange data between COMOS and PDMS from AVEVA. It is only valid as of COMOS 8.2 AddOnB.

You find additional information on this topic in the "COMOS PDMS Integration" manual.


7.6.14 "GD 3D geometry" tab Name "GD" Description "3D geometry" Inheritance source "@Viper > @Y > CHP > PP > GD 3D Geometry" Function The attributes of the tab are of importance for pipe spec administration and

for the generation of 3D objects.

Setting for all 3D attributes 3D mode must be activated for all 3D attributes:

Properties of the attribute, "Link" tab, "3D Mode": "On"

Reserved attribute names Some attribute names are reserved by the software for 3D attributes. See also chapter Reserved attribute names (Page 214).




7.6.14.1 General geometry attributes The "3D geometry" tab has the following general geometry attributes:

Name Description Function "VSTD" "Standard" List for the definition of the standard system

Controls the attributes which are dependent upon standards systems: – Fixed programmed: All attributes on the "3D geometry" tab – Tab "VDS": Nominal pressure ("VS012") and contact face 1 to

4 ("VS0#4") Standard table: "@3D > 01 > NSYS Standards system" Script blocks: See also chapter Properties of a standards system

attribute (Page 211).

"UseSym-bolOnly"

"In the report, only use the symbol for the requirement"

Option which is relevant for P&ID plans if the P&ID catalog is linked to the pipe part catalog. See also chapter Retaining the request as the report object (Page 180).

"VGEO" "GeoType" List for the definition of the GeoType

The corresponding GeoTypes have already been entered in the PPC.

The GeoType is evaluated when the drawing procedure of the pipe part is called in the 3D model.

Seek advice from your account manager before entering new GeoTypes.

3D attribute

"VFCD" "Function code" List for the definition of the function code Evaluated in the P&ID, Isometrics, and PipeSpec Designer

modules, as well as in the 3D environment. Standard table: "@3D > 01 > BC > 01 > 03 Function code"

"Layer" "Layer" List specifying a group of objects that are hidden and shown as a group in 3D space.

Standard table: "@3D > 00 > Layers Layers" 3D attribute

"VCOL" "Color" Button specifying the color in which the object is to be displayed in 3D space.

3D attribute Script block "OnClick()": Take over the implementation of the

COMOS DB from the "@VIPER > @Y > @3D > @PP > 01 > VCOL" node.

"WMF" - Cross-section drawing with the legend for the dimensions



Name Description Function "VPCL" "Pipe spec" List from which the pipe spec is selected in the engineering data.

3D attribute Script block "OnEdit": See also chapter Scripts for pipe spec

mapping (Page 215). Script block "FillComboList":

Filters which pipe specs appear in the list. Script block "GetLinkedSpecification"

During pipe spec mapping, ensures that the pipe spec is taken from the P&ID request.

Implementation of the "OnEdit", "FillComboList", and "GetLinkedSpecification" script blocks: Take over the implementation of the COMOS DB from the "@VIPER > @Y > @3D > @PP > 01 > VPCL" node.

"VC#2" "#" stands for the index number of the connector.

"Nominal pressure"

List defining the nominal pressure. The value is usually taken from the "VDS.VS0#2" attribute using

the "OnChange" script block. Statically linked with "VDS.VS0#2". In other words, if a value

deviating from "VDS.VS0#2" is input, it changes color to orange automatically.

Properties of the attribute, "Link" tab: – "Link type": "Own object" – "Attribute": "VDS.VS0#2" – "Value": "Static" – "Operator": "="

3D attribute Script block "FilterRow":

– Purpose: Filters which nominal pressures appear in the list. – Take over the implementation of the COMOS DB from the

"@VIPER > @Y > @3D > @PP > 01 >VC2" node.

"VFLG" "Flange standards sys."

Standard table: "@3D > 01 > BC > 01 > 04 Flange standards systems"

3D attribute

"VSUI" - Only visible in the Navigator, not in the properties. Use: To modify the report bar in interactive reports. Not directly

PipeSpec-relevant. You find additional information on this topic in the "Reports -

Basic Operation" manual, keyword "VSUI".

See also Standard table for PPC function codes (Page 226)



7.6.14.2 Control group "Nominal diameter connect type straightway" The "Nominal diameter connect type straightway" control group defines the following attributes for the input and output of the pipe part:

Name Description Function "VC#1" "Nominal diameter" List for the definition of the nominal diameter

Is not set until the engineering data stage. If pipe spec mapping has been performed, the PPC object adopts the nominal diameter of the P&ID object.

Properties of the attribute, "Link" tab – "Link type": "Via script function <GetLinkedAttribute>" – "Value": "Static" – "Operator": "="

3D Mode: On Standard table: "@3D > 01 > 05 Nominal diameters" Script block "OnEdit":

When the nominal diameter is changed in the engineering data, the script checks whether the new nominal diameter is within the range specified in the pipe spec for the pipe part.

Script block "FillComboList":

The attribute only offers the nominal diameters which are within the range of values of the standardization entered in the "VSTD " attribute for selection.

Script block "GetLinkedSpecification":

The script writes the nominal diameter set at the P&ID object to the PPC pipe part.

Implementation of the "OnEdit", "FillComboList", and "GetLinkedSpecification" script blocks: Take over the implementation of the COMOS DB from the "@VIPER > @Y > @3D > @PP > 01 >VC11" node.

"VC#3" "Connection type" 3D attribute Standard table: "@3D > 01 > BC > 02 Connection types"



Name Description Function "VC#4" "Contact face" The value is usually taken from the "VDS.VS0#4" attribute using

the "OnChange" script block. Statically linked with "VDS.VS0#4". If a value deviating from

"VDS.VS0#4" is input, it changes color to orange automatically. Properties of the attribute, "Link" tab

– "Link type": "Own object" – "Attribute": "VDS.VS0#4" – "Value": "Static" – Operator: "="

3D attribute Standard table: "@3D > 01 > 06 Contact face" Script block "OnChange":

– Integration of attribute values into the Navigator description text

– Implementation: See also chapter Navigator description from pipe part attributes (Page 213).

Script block "FilterRow": – Filters which nominal pressures appear in the list. – Take over the implementation of the COMOS DB from the

"@VIPER > @Y > @3D > @PP > 01 >VC#4" node.

"VD#3" "Bolted joints" For flanged pipe parts only. List in which the type of bolted joint of the pipe part is defined and

thus the algorithm for calculating the screw length. 3D attribute Standard table: "@3D > 01 > BC > 03 Bolted joint types"

"#" stands for the index number of the connector.

7.6.14.3 Dimension attributes The dimensions of the pipe part are defined in the following control groups:

● "General Geometric Description"

● "Additional and alternative connection description"

3D attributes are defined in the control groups depending on the pipe part.

A legend for the parameters can be found in the cross-section drawing added in the "Descriptions" control group.

Configuration of the attributes See also chapter Determining the pipe part geometry (Page 152).



"Navigate" context menu If you have entered the "CatStd(...)" calculation formula in the geometry attribute, you can navigate to the basic table defined by the formula via the attribute context menu: "Navigate > Norm definition > ..."

7.6.14.4 Other attributes on the "3D geometry" tab

Other attributes on the "3D geometry" tab Name "PSDP" Description "Pipe-spec-dependent" Function Is evaluated if the "CatPC" calculation formula has been called for the pipe part.

Is evaluated while the nominal diameter range is calculated for "NDRange". "CatPC" sets the attribute to the value "1". This means the pipe part counts as

3D calculated.

Name "BranchPP" Description - Function Type: Checkbox

Value "1": The object is permitted as a branch part. The attribute even allows you to use pipe parts as branches whose function

code is not within the function code range for branches. It is not created in the COMOS DB. You have to create it yourself, if necessary.

Name "NDRange" Description - Function The attribute saves the nominal diameter range of the pipe part as an XML

string. Reason: Calculating the nominal diameter range of the pipe part takes up

processing power. COMOS creates the attribute automatically when it requires the nominal

diameter range for the first time. The nominal diameter range is calculated during the creation process. If the attribute has been deleted, it is recreated.

If you are working with working layers, you have to create the attribute yourself. Create it on the layer for connection types. If you do not do this, you might experience problems with the SystemUID when you enable working layers.



See also "Display for nominal diameter range" tab ()

Validation of nominal diameter ranges (Page 163)

7.6.15 "Display for nominal diameter range" tab Name "NDRange" Description "Display for nominal diameter range" Inheritance source See also chapter Overview of the tabs and their inheritance sources

(Page 127). Function Here you restrict the nominal diameter range of the pipe part.

User interface reference The tab contains the following elements:

● A table displaying the nominal diameter range of the pipe part

– The table is based on an object query. See also chapter Display nominal diameter range (Page 164).

– It includes all nominal diameters from the nominal diameter range of the standardization that are assigned to the pipe part. It is reduced by the nominal diameters for which COMOS cannot determine the parameters required for calculation of the component geometry.

– A table cell is displayed in white if the nominal diameter for the pipe part is permitted according to the standardization, and in gray if not.

– An option in the white table cells determines whether the nominal diameter belongs to the nominal diameter range of the pipe part.

● The "Refresh" button

– It recalculates the nominal diameters listed in the table.

Restricting the nominal diameter range of the pipe part To exclude nominal diameters from or add them to the nominal diameter range which is available in principle at the pipe part, click once with the left mouse button in a cell:

● Option was activated: The option is deactivated. The nominal diameter is no longer in the nominal diameter range.

● Option was deactivated: The option is activated. The nominal diameter is within the nominal diameter range.

You can only edit the white cells.



Result ● You have defined the nominal diameter range in which the pipe part is available.

● The nominal diameter range is saved at the pipe part as an XML string in the "GD.NDRange" attribute.

Recalculating the nominal diameter range Click the "Refresh" button to recalculate the nominal diameter range.

This is necessary primarily if you have made changes on the "GD 3D geometry" tab or to the basic tables from the standard catalog for geometry standards.

Note

Clicking the "Refresh" button to recalculate the nominal diameter range overwrites all manual changes you have made to the nominal diameter range in the table.

Inheriting the tab to pipe spec elements The tab is also inherited to the pipe spec elements that are based on the pipe parts from the pipe part catalog. It serves informational purposes in this context.

If the "CATPC" calculation formula is input at a geometry attribute, the nominal diameter range of the pipe part cannot be calculated in the pipe part catalog. The pipe spec element is used in this case.

Properties of the attributes Name Description Comment "Show" - Uses the following query: "@VIPER > @Q > Range Query Query

Attributes" "Calculate" "Refresh" Script block "OnClick":

Purpose: Used to recalculate the nominal diameters. Take over the implementation of the COMOS DB from the

"@VIPER > @Y > CHP > PP > A0 > NDRange > NDRange > Calculate" node.

See also Other attributes on the "3D geometry" tab (Page 149)



7.6.16 Determining the pipe part geometry

7.6.16.1 Configuring the geometry attributes

Principle ● The base objects from the pipe part catalog are not multiplied out by nominal diameter.

They do not save the true values for the dimensions.

● The pipe part dimensions are determined in the properties of the pipe part.

On the "3D Geometry" tab in the attributes of the control groups:

– "General Geometric Description"

– "Additional and alternative connection description"

● Instead of actual dimensions, calculation formulae are input in the attributes in the base objects. They determine:

– The source from which the pipe part gets its dimensions

– How the actual values are calculated

– What the actual values are

● The calculation formulae are evaluated in the engineering data.

Reason: Some attributes used for calculation are not set until the engineering data stage; these include the construction angle or the component length for components with variable lengths.

Consequence: When a user changes the properties of a pipe part in the engineering data and inputs a new nominal pressure, for example, the geometry dimensions are adapted automatically.

Possible sources for dimensions Depending on the calculation formula that was entered, the dimensions are taken from one of the following sources:

● The standard catalog

● The pipe part:

– The dimension comes from the local dimensions.

– The dimension adopts the value of a different attribute.

– The dimension is calculated from different attribute values.

● An element of the pipe part

● The local dimensions saved in the nominal-diameter-dependent characteristics table of the pipe spec

● A default value is defined for each calculation formula. It serves as the starting value in the engineering data.



Parameterized access The calculation formulae with "Cat" in their name read the dimension from a table. Their access to the table is parameterized via the nominal diameter: The value entered from the table in the geometry attribute depends upon the nominal diameter of the pipe part in the engineering data.

You can only define a parameter other than the nominal diameter in the case of "Cat2(...)".

Fixed calculation formula for flange ends with contact face If the attributes for connection type and contact face are missing or have not been set, a fixed programmed calculation formula is used for flange ends with a contact face. It takes the dimensions from the standard catalog.

See also Dimension attributes (Page 148)

Internal formulae for calculating component dimensions (Page 189)

Using the "Define catalog access" window (Page 154)

7.6.16.2 Entering the calculation formula

Procedure You only enter calculation formulae for the outer diameter, wall thickness, and part lengths of the weld ends of the pipe part.

There are two ways to enter a calculation formula:

1. Manually:

2. Via the "Define catalog access" window

Manually: Only enter a calculation formula manually if you have extensive experience of configuring dimension attributes.

References to the sections describing the individual calculation formulae appear if there are any special features which have to be taken into account when entering formulae manually.

The "Define catalog access" window The "Define catalog access" window helps you to define a correct calculation formula. The software generates a calculation formula from the user inputs and writes it to the geometry attribute automatically.

See Using the "Define catalog access" window (Page 154).



Components of a calculation formula A calculation formula consists of the following parts:

● Name of the function that is called

● Parameters list

7.6.16.3 Using the "Define catalog access" window

Interface

Number Control element Function 1 "Object" This shows the object and attribute for which you called the

window. 2 "Function" A list of calculation formulae 3 <Name of the

calculation formula> Control elements you can use to specify the parameters of the selected calculation formula

4 "Result" The new calculation formula defined using 2 and 3 5 "Old value" The old calculation formula

Procedure To define the calculation formula using "Define catalog access", proceed as follows:

1. Open the properties of the PPC base object and click the "Attributes > 3D geometry" tab.

2. To open the "Define catalog access" window, click the field of the required attribute and press the "F2" key.



3. Select the calculation formula in the "Function" field.

4. Define the parameters of the calculation formula in the offered control group.

See also chapter Overview of the calculation formulae ().

You find detailed information about the calculation formulae in the following chapters:

– The "CatStd()" function (Page 155)

– The "Cat(...)" function (Page 159)

– The "Cat2(...)" function (Page 159)

– The "S(...)" function (Page 160)

– The "ElmS(...)" function (Page 160)

– The "CatPC(...)" function (Page 162)

– The "CatExt(...)" function (Page 161)

– The "Def(...)" function (Page 162)


7.6.16.4 Overview of the calculation formulae "CatStd(...)" The value is taken from the standard catalog. It is determined based on the nominal

diameter parameter. "Cat(...)" The value is taken from the local dimensions defined at the pipe part. It is determined

based on the nominal diameter parameter. "Cat2(...)" The value is taken from a pipe part table you specify. It is determined based on a

parameter you define. "S(...)" The geometry attribute adopts the value of the pipe part attribute you specify. "ElmS(...)" Like "S()", but the attribute comes from an element of the pipe part. "CatExt(...)" The value is taken from a pipe part table you specify. It is determined based on the

nominal diameter parameter. "CatPC(...)" The value is taken from the local dimensions defined in the pipe spec. It is

determined based on the nominal diameter parameter. "Def(...)" Sets a default value that is used as the starting value in the engineering data.

7.6.16.5 The "CatStd()" function

Requirements ● You have selected the "CatStd(...)" function in the "Function" field of the "Define catalog

access" window.

● You have followed the naming system of the standard catalog.



Functional principle of "CatStd(...)" The "CatStd(...)" function reads the dimension value from the standard catalog for geometry standards from the basic table calculated by the calculation formula.

"CatStd(...)" expects the following parameters:

● Parameter 1: A formula which evaluates the path to a basic table in the engineering data.

● Parameter 2: The name of the column from the basic table from which the dimension value is read.

● Parameter 3: The index number of the connector for which the first nominal diameter is valid.

● Parameter 4: If the component has two nominal diameters: The index number of the connector for which the second nominal diameter is valid

Using "CatStd(...)" 1. In the "Define catalog access" window, click the "..." button next to the "Standard catalog"

field.

The "Catalog selection" window opens. It shows the node in which the standard catalog for geometry standards is managed.

2. Navigate through the structure objects of the standard catalog until you reach a basic table.

3. Select the basic table and click the "OK" button.

Note

By selecting a basic table, you define a formula. The formula is evaluated in the engineering data at the pipe part and returns the path to a basic table. Although you select an actual basic table, the formula does not necessarily calculate the basic table you selected in the engineering data.

4. "Column" field: Specify from which column of the basic table the dimension value is read.

5. "Nominal diameter of connector" and "2. Nominal diameter of connector" fields: Specify for which component connector the value is valid.

If the pipe part has only one nominal diameter: Select "Ignore" for "2. Nominal diameter of connector".


Result The calculation formula is created as follows:



First parameter

● For every structure object and the basic table, COMOS evaluates the value of the "BMP.Rule ParameterName" attribute and uses it to compile the formula that is used to calculate the path to the basic table in the engineering data.

● The formula comprises a number of elements. Each element corresponds to a layer of the standard catalog for geometry standards.

● A period (".") is used as a separator between each element.

● Every element is either made up of a fixed value or a variable:

– Value of "ParameterName" equal to "- - -":

The name of the object is added to the formula (fixed value).

– Value of "ParameterName" not equal to "- - -":

The name of the attribute corresponding to the entry set in "ParameterName" is added to the formula (variable):

Value of "ParameterName" Name of the variable Assigned attribute "Standard" "VSTD" "GD.VSTD Standard" "Flange standard" "VFLG" "GD.VFLG Flange standard" "Connection type" "VC#3" "GD.VC#3 Connection type" "Nominal pressure" "VC#2" "GD.VC#2 Nominal pressure"


The variables are enclosed in "%" characters.

Example: "%VSTD%"

Second to fourth parameters

Self-explanatory.

Message "Error in catalog selection" COMOS checks the path entry when you close the "Catalog selection" window. If COMOS does not find a basic table in the location specified by the path, it opens the "Error in catalog selection" window. Here you decide if you want to use the entries anyway. After all, just because a path does not lead to a basic table in the base data, it does not mean that it will not lead to a basic table in the engineering data.

Reason:

● Not all relevant attributes have yet been set at the base object.

● Different attribute values may be set at the engineering object than at the base object.



"CatStd(...)" in the engineering data "CatStd(...)" is executed as follows in the engineering data:

1. COMOS reads the current nominal diameter of the pipe part from the "GD.VC#1 Nominal diameter" attribute.

2. COMOS evaluates the formula provided in parameter 1:

– The attributes behind the variables in the calculation formula are evaluated at the pipe part.

– They are combined with the fixed values to create a string - the path to the basic table to be used.

3. COMOS goes from the basic table specified by parameter 1 to the column specified by parameter 2, from where it retrieves the dimension of the nominal diameter set at the pipe part.

4. COMOS writes this value to the dimension attribute.

Example The following calculation formula is entered in the "OutD1 (AD)" attribute at the base object of a weld neck flange: CatStd("PP.10.1.%VSTD%.10","AD1")

1. COMOS calculates the current nominal diameter of the flange.

2. COMOS replaces the "%VSTD%" variable in the calculation formula with the value of the "GD.VSTD" attribute in the engineering data at the flange:

– Tag: "%VSTD%"

– Assigned attribute "GD.VSTD"

– DisplayValue of "GD.VSTD": "EN/DIN Metric"

– Value of "GD.VSTD": "1"

3. COMOS compiles the path to the basic table: "PP.10.1.1.10"

4. COMOS searches the standard catalog for the basic table.

5. COMOS takes the value entered for the current nominal diameter from column "AD1" and writes it to the "OutD1 (AD)" attribute.

Entering the calculation formula manually If you enter the calculation formula manually, you are free to decide where a variable is used and where a fixed name is used in parameter 1.



See also Configuring the geometry attributes (Page 152)

Using the "Define catalog access" window (Page 154)

Structuring by the "ParameterName" attribute (Page 103)

Naming system (Page 105)

Adding information to the "RU Standard table Parametrics" standard table (Page 120)

7.6.16.6 The "Cat(...)" function

Requirements You have selected the "Cat(...)" function in the "Function" field of the "Define catalog access" window.

Functional principle of "Cat(...)" ● In the engineering view, the dimension value is taken from the local dimensions that are

maintained at the pipe part: Properties of the pipe part, "Local Dimensions" tab, nominal-diameter-dependent table "V"

● The value is determined based on the nominal diameter parameter.

Using "Cat(...)" 1. "Column" field: Specify from which column of the nominal-diameter-dependent table the

value is read.

2. "Nominal diameter of connector" and "2. Nominal diameter of connector" fields: Specify for which component connector the value is valid.



7.6.16.7 The "Cat2(...)" function

Requirements You have selected the "Cat2(...)" function in the "Function" field of the "Define catalog access" window.

Functional principle of "Cat2(...)" ● The "Cat2(...)" function reads the dimension value from a pipe part table you specify.

● The value is determined based on the parameter you define.



Using "Cat2(...)" 1. Click the "..." button next to the "Table" field.

The "Catalog selection" window opens. You see the base object of the pipe part and its tabs.

2. Select the required table and click the "OK" button.

3. "Result column" field: Specify from which column of the table the dimension value is read.

4. "Search column 1" field: Specify the column to be used as the search parameter.

5. For pipe parts with two nominal diameters: Specify the column of the second search parameter in the "Search parameter 2" field.

6. "1st attribute with search value" field: Specify which attribute of the pipe part is evaluated to find the correct search row in the search column.

7. "2nd attribute with search value" field: For pipe parts with two nominal diameters. Same as above.


7.6.16.8 The "S(...)" function

Requirements You have selected the "S(...)" function in the "Function" field of the "Define catalog access" window.

Functional principle of "S(...)" The "S(...)" function uses the value from another pipe part attribute as the dimension.

Using "S(...)" 1. "Attribute" field: Click the "..." button next to the field.

The "Attribute selection" window opens. You see the base object of the pipe part and its tabs.

2. Select the required attribute and click the "OK" button.

3. In the "Define catalog access" window, click the "OK" button.

7.6.16.9 The "ElmS(...)" function

Requirements You have selected the "ElmS(...)" function in the "Function" field of the "Define catalog access" window.



Functional principle of "ElmS(...)" The "ElmS(...)" function uses the value from an attribute of a pipe part element as the dimension.

Using "ElmS(...)" 1. "Element" field: Click the "..." button next to the field.

The "Element selection" window opens. You see the base object of the pipe part and the subordinate elements.

2. Select the required element and click the "OK" button.

3. "Attribute" field: Click the "..." button next to the field.

The "Attribute selection" window opens. You see the base object of the element and its tabs and attributes.

4. Select the required attribute.

5. In the "Define catalog access" window, click the "OK" button.

See also The "S(...)" function (Page 160)

7.6.16.10 The "CatExt(...)" function

Requirements You have selected the "CatExt(...)" function in the "Function" field of the "Define catalog access" window.

Functional principle of "CatExt(...)" ● The dimension is read at the pipe part from a table you specify.


Using "CatExt(...)" 1. "Table" field: Click the "..." button next to the field.

The "Catalog selection" window opens. You see the base object of the pipe part and its tabs.

2. Select the required table and click the "OK" button.

3. Continue as described for the "Cat(...)" function.




See also The "Cat(...)" function (Page 159)

7.6.16.11 The "CatPC(...)" function

Requirements You have selected the "CatPC(...)" function in the "Function" field of the "Define catalog access" window.

Functional principle of "CatPC(...)" ● The dimensions are read from the local deviations that are maintained in the pipe spec:

"Characteristic" tab, nominal-diameter-dependent characteristics table "V1"


Using "CatPC(...)" 1. Click the "..." button to the right of the "Pipe spec" field.

The "Element selection" window opens.

2. Select a pipe spec and click "OK".

3. "Column" field: Specify which column the value is taken from.

4. In the "Nominal diameter of connector" and "2. Nominal diameter of connector" fields, specify the component connector for which the value is valid.



7.6.16.12 The "Def(...)" function You can only input the "Def(...)" calculation formula manually.

Procedure Pass a value as a parameter that serves as the starting value and can be replaced by another value at a later stage in the engineering data.

Example:

Def(2500)

Result If the base object is changed in the engineering data, the attribute value that was input at the pipe part is always retained.



In contrast, if you input the starting value directly into the attribute in the base data, when the base object is changed, the attribute value input at the object is replaced by the value defined at the new base object.

7.6.17 The nominal diameter range of a pipe part

7.6.17.1 Validation of nominal diameter ranges The base objects of the pipe parts from the pipe part catalog are almost completely specified template objects that are parameterized according to nominal diameter. This means that a manufacturer device can be assigned by setting the nominal diameter.

PPC objects are assigned to standardizations. A nominal diameter in the nominal diameter range of a standardization cannot be assigned to a pipe part if the nominal diameter in the pipe part norm is not permitted.

COMOS validates the permitted nominal diameter ranges of a pipe part and saves them at the corresponding object. Regarding the nominal diameter, a pipe part counts as permitted if the following requirements are met:

● All 3D attributes of the "3D geometry" tab entered via the user interface have to be calculable.

● The values that are relevant for calculating the geometry have to be calculable.

The calculated nominal diameter range is saved at the pipe part as an XML string in the "NDRange" attribute on the "3D geometry" tab. See also chapter Other attributes on the "3D geometry" tab (Page 149).

The nominal diameter range of a pipe part can also be displayed on the user interface. See also chapter Display nominal diameter range (Page 164).

For pipe-spec-dependent pipe parts for which the function "CatPC" has been set, the XML string is created underneath the pipe spec element.

7.6.17.2 New calculation of the nominal diameter range

Initial situation If changes are made to the attributes of a pipe part which affect its nominal diameter range, the nominal diameter range has to be recalculated.



Procedure Select one of the following options:

● Delete the "GD.NDRange" attribute.

It is automatically created as soon as it is requested by the system. When you drag a pipe part into a pipe spec, for example.

● Select the pipe part in the base data, followed by "Recalc ND Range" from the context menu.

Precondition: The "OnMenuCreate" script block is implemented at the root node of the pipe part catalog in the same way as in the COMOS DB for the "@VIPER > @PPC Pipe part catalogs" base object.

● Use a button whose "OnClick" script block starts the calculation, e.g. the "Refresh" button on the "NDRange Display for nominal diameter range" tab from the COMOS DB.

Problems with missing rights COMOS might not be able to save the nominal diameter range in the "NDRange" attribute, e.g. due to a missing right or because you are in another project.

In this case the XML string is not available; it is recalculated every time it is needed. See also chapter Integration into existing databases (Page 165).

7.6.17.3 Display nominal diameter range

Procedure 1. To create a query for attributes, select "New > New query > Standard > Attributes" from

the context menu.

In the COMOS DB, you find the query under the "@VIPER > @Q > Range Query" node: Specifications"

2. Open the query. Open the "Options" window in the query and switch to the "Administration" tab.

Enter the value "ComosPCOMRange.NDRangeExtender" in the "Extension object" field.

3. Create a tab called "NDRange Display for nominal diameter range" and on this tab an attribute of the type "Object query".

4. Link the attribute to the query under "Properties > Attribute display".

To update the permitted nominal diameter ranges at the touch of a button, create a button whose "OnClick" script block starts the calculation, e.g. the "Refresh" button on the "NDRange Display for nominal diameter range" tab from the COMOS DB.

Display on the "Display for nominal diameter range" tab In the COMOS DB, the nominal diameter range in the pipe part catalog has been integrated on the "Display for nominal diameter range" tab. See also chapter "Display for nominal diameter range" tab (Page 150).



7.6.17.4 Integration into existing databases If you are already working with an existing database and the "GD.NDRange" attribute and associated XML strings have not yet been generated for its pipe part base objects, you should convert the base objects of the pipe parts once only.

If you do not convert the base objects in the base project, COMOS cannot create the attribute in the engineering data. The permitted nominal diameter range must always be recalculated every time it is called. This can lead to a decrease in performance.

Note

The time taken to complete the conversion depends upon the number of pipe parts. Run the conversion overnight if necessary.

Script for conversion To run the conversion, implement the following script at the structure object of the pipe part catalog or execute it via the object debugger: "Set Checklib = CreateObject ("ComosPPCObjectCheck.Lib") CheckLib.NDRangeForCDevice Me,Nothing"

"Me" is equivalent to the start object.

The conversion is conducted recursively.

7.6.18 Expanding the pipe part catalog

7.6.18.1 Creating a new catalog The COMOS DB contains two pipe part catalogs: one catalog based on DIN/EN and one based on ANSI/ASME.

You can create more catalogs, e.g. manufacturer catalogs.

Requirements The standards system on which the new catalog is to be based already exists in the database:

● The standard table for standards system contains an entry for the corresponding standards system.

● The corresponding standardization is fully configured.

● The standard catalog for geometry standards implements all necessary geometry standards.




2. Open the root node of the pipe part catalogs. In the COMOS DB, the pipe part catalogs are located under the @VIPER > @PPC Pipe Part Catalogs" node.

3. Create the structure object for the new catalog. Dependent upon the extent to which the new catalog differs from existing catalogs, create it from scratch or use an existing catalog as a template:

– From scratch: Select the root node of the pipe part catalogs, followed by "New > New base object" from the context menu.

– Using a template: Select a catalog underneath the root node, followed by "Copy" from the context menu. Select the root node, followed by "Paste" from the context menu.

4. Open the properties of the new catalog. You are working in the "General" control group on the "System" tab.

5. "Name" field: Enter the value for the corresponding standards system in the "Value 1" column of the @3D > 01 > NSYS Standards system" standard table.

6. "Description" field: Enter a description, e.g. "General components <name of the manufacturer>".

7. Complete the substructure of the catalog. Dependent upon whether the catalog is completely new or based on a template, proceed as follows:

– From scratch: Create the substructure of the catalog as far as the actual pipe parts.

– Using a template: Rename nodes, create new nodes, edit the properties, or delete nodes (e.g. nodes for pipe part types which are not produced by the manufacturer), if necessary.

7.6.18.2 Creating a new pipe part

Procedure We recommend using an existing pipe part as a template when adding a new pipe part to an existing pipe part catalog. Proceed as follows:

1. Open the pipe part catalog and navigate to the pipe part you are using as a template.

2. Select the pipe part, followed by "Copy" from the context menu.

3. Select the node underneath which the new pipe part is to be located, followed by "Paste" from the context menu.

4. Open the properties of the new pipe part and modify them.

Administration 7.7 Creating a pipe part type


7.7 Creating a pipe part type

Definition A pipe part type is a category of pipe parts whose function is identical to the name of the pipe part type. The "X" in the name of the pipe part type is a placeholder.

The pipe part type "21XXX Elbow pipe" covers, for example, all pipe parts of a pipe spec whose function code consists of the number "21" and any other three digits.

Base objects of pipe part types The "Viper" tab in the project properties shows where you find the base objects of the pipe part types in the database.

Structuring pipe part types Structure pipe part types so that you can access all pipes or elbows of a pipe spec, for example, using the pipe part type. Each PipeSpec element should only be sorted into one category. Exception: The "XXXX" pipe part type is also permitted.

Creating a new pipe part type 1. Select the root node for the pipe part types in the base data.


3. Open the properties of the new object and click on the "System" tab.

4. "Name" field: Enter the initial digits of the function code as the name. For the characters which are variable, set an "X". Example: 21XXX. The name has to contain five characters.

5. "Description" field: Enter the function type.

6. "Pointer" control group: In the "Base object" field, set a pointer to a base object whose function code lies within the pipe part type.

Note

The function code of the linked base object is used, for example, in the Isometrics module to control the display of the VSUI bar.


Standard table for PPC function codes (Page 226)

Administration 7.8 Managing bolt sets


7.8 Managing bolt sets

7.8.1 Creating a bolt set

Requirements The "Base objects" tab is selected in the Navigator.

Procedure 1. In the Navigator, open the node under which the bolt sets are located.

In the COMOS DB, the bolt sets are located under the "@VIPER > @BoltSet Bolt Sets" node.

2. The bolt sets are managed separately by standards system. Select the node of the required standards system.


COMOS creates the base object for the new bolt set.

4. Open the properties of the bolt set.

5. Enter the name and the description of the bolt set in the "General" control group on the "System" tab.

6. Go to the "Attributes > Bolt set" tab.

You see two tables in the "Bolt table" control group.

7. In the Navigator, select the base object of the screw which is to belong to the bolt set.

8. Drag&drop the screw from the Navigator to the table at the top of the "Bolt table" control group.

9. In the Navigator, select the base object of the nut which is to belong to the bolt set.

10. Drag&drop the nut from the Navigator to the table at the bottom of the "Bolt table" control group.

11. Enter the number of nuts in the "Quantity" column of the lower table.

Example: "2" stands for "2 x N nuts"

12. For washers, proceed as described for nuts in Steps 9 through 11.

13. If you do not want to add screw parts in the parts list, deactivate the option in the "BOMrelevance" column.

14. "Standards table" pointer:

Only set a pointer to a basic table for screws if a pointer has not been entered in the "GD.VBolt Screw bolts standard table" attribute at the base object of the screw.

If pointers have been entered at both the bolt set and the screw, the pointer entered at the screw takes priority.

Administration 7.9 Interaction P&ID-PPC-3D


15. If the bolt set is to have stud hole screws and screw parts, work in the "Stud hole screw parts" control group.

– Drag the stud hole screw to the table at the top of the "Stud hole screw parts" control group and the stud hole screw parts to the table at the bottom.

– Configuring the "Standards table" pointer: Same as Step 13.

16. Go to the "Attributes > Geometry" tab.

17. Check that the "Bolt set" entry is selected in the "Function code" list.


7.9 Interaction P&ID-PPC-3D

Aim If the P&ID catalog is linked with the pipe part catalog or "PPC"), users have the option to start working in the P&ID module based on pipe specs.

The link also creates a seamless transition between the individual project phases: from P&ID engineering through the creation of isometric drawings and beyond to 3D engineering.

Principle If the P&ID catalog is linked to the pipe part catalog, R&ID engineering can be carried out based on pipe specs:

● COMOS starts pipe spec mapping as soon as a user assigns a pipe spec and nominal diameter to a P&ID object.

● The user selects a suitable object from a range of possible PPC objects.

● The P&ID user continues to work with the P&ID object.

● The much more complex and 3D-capable PPC object is managed as an implementation in the background. It can be used later on during engineering, for example, to create an isometric drawing or plan an installation in the COMOS Plant Modeler module.

● The symbol of the PPC object object is output on the P&ID.

COMOS DB The link is already implemented in the COMOS DB.



7.9.1 Requirements Before you link the P&ID catalog to the pipe part catalog, check that the following requirements have been met:

● The PPC has been imported into the base project.

● The base project features a standard table for the P&ID function codes.

● The base project features a standard table for the PPC function codes.

● The project must have certain project parameters.

See also chapter Configuring the project properties for P&ID-PPC-3D interaction (Page 175).

● The P&ID base objects must have certain properties and attributes.

See also chapter Configuring the P&ID base objects (Page 177).

● The PPC base objects must have certain properties and attributes.

See also chapter Configuring the PPC base objects (Page 179).

7.9.2 Technical implementation

7.9.2.1 Link between P&ID and PPC

Implementation ● The database features a standard table grouping the function codes of the P&ID objects.

● A P&ID function code from this standard table is assigned to each P&ID base object.

● The database features a standard table grouping the function codes of the objects from the pipe part catalog.

● A PPC function code from this standard table is assigned to each PPC base object.

● The P&ID function codes and the PPC function codes are assigned to one another via the link code entered in the standard table for PPC function codes.

There can be any number of suitable PPC objects for each P&ID pipe part category (ratio 1:N).

● Every P&ID object has attributes which save the pipe spec and nominal diameter.

● When a user assigns a pipe spec and a nominal diameter to a P&ID engineering object, COMOS starts pipe spec mapping based on the pipe spec, the nominal diameter, and the P&ID function code.

● In the course of pipe spec mapping, the P&ID object is assigned an implementation pointer to a PPC object.



See also Scripts for pipe spec mapping (Page 222)

The pipe spec mapping sequence ()

Result of pipe spec mapping (Page 171)

7.9.2.2 The pipe spec mapping sequence Pipe spec elements are always objects from the pipe part catalog (PPC).

Procedure 1. COMOS reads out the pipe spec set at the P&ID object and searches for the base object

of the corresponding pipe spec.

2. COMOS reads out the P&ID function code of the P&ID object.

3. COMOS searches the standard table for PPC function codes and compares the values or masks entered in the "Value 2" column with the function code of the P&ID object.

4. For all entries with a matching value:

– COMOS searches the pipe spec for all pipe spec elements with a matching PPC function code.

– For the pipe spec elements, COMOS checks whether the nominal diameter set at the P&ID object corresponds to the nominal diameter range of these pipe spec elements.

– If it does, COMOS makes the pipe spec elements available to the user for selection during pipe spec mapping.

5. The user selects the required object from the list of possible PPC objects.

7.9.2.3 Result of pipe spec mapping ● The P&ID object is retained as the request. The P&ID user continues to work with the

P&ID object.

● The PPC object selected by the user is created in the engineering data as an implementation underneath the P&ID object.

Users can move the PPC object to a different location later on in the engineering process.

● The P&ID object gets an implementation pointer to the PPC object.

● The connection type of the P&ID object is determined by the connection type of the PPC object.

● The nominal pressure at the pipe is linked with the pipe spec nominal pressure.

● The symbol of the PPC object object is used on the P&ID. However, the P&ID object remains the report object.



7.9.3 Configuration workflow To link the P&ID catalog to the pipe part catalog, proceed as follows:

1. Standard table for the function codes of P&ID objects: Enter the P&ID function codes.

See Configuring the standard table for P&ID function codes ().

2. Standard table for the function codes of PPC objects: Enter the link code for the P&ID objects.

See Configuring the standard table for PPC function codes (Page 173).

3. Project properties: Configure the following tabs:

– "Options > Process engineering"

– "Viper"

See Configuring the project properties for P&ID-PPC-3D interaction (Page 175).

4. Configure the properties of the P&ID base objects. See Configuring the P&ID base objects (Page 177).

Configure the properties of the PPC base objects. See Configuring the PPC base objects (Page 179).

7.9.4 Configuring the standard table for P&ID function codes

Requirements ● The base project is open.

● The standard table containing the P&ID function codes is open.

In the COMOS DB, you find the standard table under "P > Y > 0 > 4 > 01 P&ID Function Code". It contains entries for numerous component categories by default.

Content of the standard table Every entry in the standard table represents a P&ID component category. The entry defines the function code of the component category.

Procedure You can enter as many component categories as you like in the standard table.



To create a new component category, proceed as follows:

1. Create a new standard table entry.

2. "Name" property: Enter the name of the component category.

The names are based on the following default descriptions:

Name (prefix) Component FLANGE Flanges PIPE Pipes BRANCH Tees and branches GASKET Gaskets NOZZLE Nozzles REDU Reducers VALVE Valves of all types WELD Welds

3. "Description" property: Enter the description of the component category.

4. "Value 1" property: Enter the abbreviation of the component category.

– The abbreviation is used as a link code in the standard table for PPC function codes. In other words, COMOS searches the standard table for PPC function codes using the abbreviation.

– You can work with the following placeholder characters: "*"

COMOS then searches the standard table for PPC function codes with a LIKE comparison.

Example for P&ID function code with placeholders Abbreviation in the standard table for P&ID function codes: "V2W***"

All entries in the standard table for PPC function codes whose link code in the "Value 2" column is six characters in length and starts with "V2W" count as hits (for example: " V2WARM", "V2WSVA", "V2WORI").

7.9.5 Configuring the standard table for PPC function codes

Note Only configure the "Value 2" column

With the exception of the "Value 2" column, you must seek advice from your account manager before configuring the standard table.




● The standard table for PPC function codes is open.

In the COMOS DB, you find the standard table under "@3D > 01 > BC > 03 > 01 Function Code".

It contains entries for numerous component categories by default.

● The standard table for P&ID function codes is open.

In the COMOS DB, you find the standard table under "P > Y > 0 > 4 > 01 P&ID Function Code".

It contains entries for numerous component categories by default.

Structure Every entry in the standard table represents a pipe part catalog component category. The entry defines the function code of the component category.

Procedure To link the P&ID objects to the PPC objects, proceed as follows for every entry in the standard table for P&ID function codes:

1. Select an entry.

2. Click twice with the left mouse button in the field for the "Value 1" column, so that the mouse pointer is positioned in the cell.

3. Copy the value from the "Value 1" column - the link code - to the clipboard.

4. Go to the standard table for PPC function codes and select the entry for the corresponding component category.

5. Click twice with the left mouse button in the field for the "Value 2" column, so that the mouse pointer is positioned in the cell.

6. Paste the link code from the clipboard into the "Value 2" column.

Example To link a 2-way ball check valve from the P&ID catalog to a 2-way ball check valve from the pipe part catalog, proceed as follows:

1. In the standard table for the P&ID function codes, go to the following entry:

– Name: "Valve2WayBallCheckValve"

– Description: "2-way ball check valve"

– Value 2: "V2WBCV"

2. Copy the value from the "Value 2" column to the clipboard.



3. In the standard table for the PPC function codes, go to the following entry:

– Name: "61830"

– Description: "2-way ball check valve"

– Value 1: "61830"

4. Paste the value from the clipboard into the "Value 2" column.

See also Standard table for PPC function codes (Page 226)

7.9.6 Configuring the project properties for P&ID-PPC-3D interaction

Note Modify scripts when defaults change

If you enter values in the project properties which differ from the default values set in the base project in the COMOS DB ("Options > Process engineering" tab, "Link between P&ID and PPC" control group), you must modify all scripts which, for performance reasons, use fixed attribute names instead of accessing the project properties. You find a list of these scripts in Inheritance of the nominal diameters and pipe spec (Page 216).


● The properties of the base project are open.

Procedure To link the P&ID catalog to the pipe part catalog, proceed as follows:

1. Click on the "Options > Process engineering" tab.

2. Deactivate the "Only apply values linked through the GD tab" option.



3. Configure the properties of the "Link between P&ID and PPC" control group as described in the following table:

Description Function Default Configuration "Pipe spec" Defines which attribute

saves the pipe spec of a P&ID object.

"PI030.PIA012" Enter the attribute that saves the pipe spec of the P&ID objects in your database. Every P&ID object must have the attribute entered here.

"Nominal diameter specification for the first connector (input)"

Defines which attribute saves the input nominal diameter of the P&ID object.

"PI030.PIA008" Same as above.

"Nominal diameter specification for other connector (output)"

Defines which attribute saves the output nominal diameter of the P&ID object.

"PI030.PIA008a" Same as above.

"Attribute for P&ID function code"

Defines which attribute saves the P&ID function code of the P&ID object. See also chapter Checking the attribute for the P&ID function code (Page 178).

"SYS.PIA600" Same as above.

"Attribute for PPC function code"

Defines which attribute saves the PPC function code of the PPC object. See also chapter Checking the attribute for the PPC function code (Page 180).

"GD.VFCD" Fixed programmed. Changes have no effect.

These properties are defined in the system project of the COMOS DB, in the "@PROPAR.PFD Process Engineering" node. If the control group does not exist in your database, import it into your system project from the COMOS DB.

4. Click on the "Viper" tab.

5. Configure the attributes on the "Viper" tab as described in Setting project properties (Page 77).

The "Viper" tab is defined in the base project of the COMOS DB in the "@J > VIPER Viper" node. If the tab does not exist in your database, import it into your system project from the COMOS DB.



7.9.7 Configuring the P&ID base objects

7.9.7.1 Workflow The P&ID catalog supplied with the COMOS DB contains all settings necessary for the link between P&ID, PPC, and 3D.

Procedure If you have created your own P&ID catalog or made major changes or additions to the catalog supplied with the COMOS DB, you must ensure that all objects have the settings necessary for the link.

To do this, proceed as follows for every P&ID base object:

1. Check whether the P&ID base object is defined as a request:

Properties, "System settings" tab, "Implement requests" control group: The "Request" option is activated.

2. If the P&ID base object has the "GD 3D geometry" tab, delete or rename it.

Reason: The 3D functionality should not be derived from the P&ID object but instead from the PPC implementation.

3. Check the attribute for the P&ID function code.

See also chapter Checking the attribute for the P&ID function code (Page 178).

4. Check that the scripts required for pipe spec mapping are available. See also chapter Scripts for pipe spec mapping (Page 222).

5. Check that each of the attributes for the nominal diameter and the pipe spec are linked correctly.

See also chapter Links for the attributes for nominal diameter and pipe spec (Page 223).

6. Optional: If the P&ID object is to adopt the connection type of the PPC object, you must link the attribute for the connector.

See also chapter Link for the "Connector" attribute (Page 224).

7. Optional: If the P&ID pipe is to adopt the nominal pressure of the pipe spec, you must link the attribute for the nominal pressure.

See also chapter Link for the "Nominal pressure" attribute (Page 224).

8. Deactivate the standard checks for the implementation link carried out automatically by COMOS through the "IsImplementationValid(Device)" and "OnImplementationSet(Oldvalue)" script blocks.

See also chapter Deactivating the standard check with "IsImplementationValid" and "OnImplementationSet" (Page 222).



7.9.7.2 Checking the attribute for the P&ID function code

Requirements You know which attribute the P&ID function code is saved in. You can check which attribute this is in the project properties. See also chapter Configuring the project properties for P&ID-PPC-3D interaction (Page 175).

Procedure 1. Open the properties of the P&ID base object.

In the COMOS DB, you find the catalog with the P&ID base objects under the "@01 > PID Pipe and Instrumentation" node:

2. Check whether the attribute for the P&ID function code exists on the tab specified by the project properties and has the correct name.

Create the attribute if necessary.

3. Check whether the standard table for P&ID function codes defined in the project properties has been assigned to the attribute.

Make the assignment if necessary.

4. Check whether a feasible P&ID function code has been set at the attribute.

Set one if necessary.

Repeat these steps for each P&ID base object.


7.9.7.3 Implementing branches

Initial situation A branch has been drawn in on a P&ID which is implemented via a dynamic connector and not via a branch part, such as a tee, for example.

Pipe mapping for branches without branch part If you have drawn in a branch on the P&ID without a branch part such as a tee, for example, you can still store a PPC object at the associated connector for the detail engineering.

COMOS interprets the dynamic connector as a branch. With pipe spec mapping, the user can select a PPC object for the detail engineering. COMOS determines the branch part from the branch table or through function code 71xxx. A D3 implementation pointer is set for the dynamic connector.

If you want to display the symbol of the implemented PPC object on the P&ID report, you must give the symbol of the implementation the "D3IMPLEMENTATION" symbol type.



7.9.7.4 P&ID objects without function codes

Virtual element "@3D" as implementation Objects that have no P&ID function codes, such as equipment, are likewise created as requests. They are assigned a suitable 3D base object with the name "@3D" as a virtual element; this then serves as the implementation.

The following also applies here: Because the implementation pointer is diverted from its intended use, the standard checks that are carried out automatically by COMOS must be deactivated.

Example for vessels

See also Deactivating the standard check with "IsImplementationValid" and "OnImplementationSet" (Page 222)

7.9.8 Configuring the PPC base objects

7.9.8.1 Workflow The pipe part catalog supplied with the COMOS DB contains all settings necessary for the link between P&ID, PPC, and 3D.

Procedure If you create your own pipe part catalog, you must check the necessary settings for the link.



Proceed as follows for each PPC object:

1. Check the attribute for the PPC function code.

See also chapter Checking the attribute for the PPC function code ().

2. Make sure that the P&ID object remains the report object.

See also chapter Retaining the request as the report object (Page 180).

3. Make sure that the attributes for "pipe spec" and "nominal diameter" implement the "OnEdit()" script block as described in the reference.

See also chapter Scripts for pipe spec mapping (Page 215).

4. Make sure that the attributes for "pipe spec" and "nominal diameter" are linked as described in the reference.

See also chapter Inheritance of the nominal diameters and pipe spec (Page 216).

7.9.8.2 Checking the attribute for the PPC function code

Procedure 1. Check that the attribute for the PPC function code exists: "Attributes > 3D geometry" tab,

name "VFCD".

Create the attribute if necessary.

2. Check whether the standard table for PPC function codes defined in the project properties has been assigned to the attribute.

Make the assignment if necessary.

3. Check whether the correct PPC function code has been set at the attribute.

Set it if necessary.

7.9.8.3 Retaining the request as the report object

Modification of standard procedure for requests and implementations The standard procedure for requests and implementations designates the implementation as the report object. This means:

● The symbol of the implementation is used on the report.

The symbol of the request is only used if the implementation does not define a symbol script.

● In the context menu of the report, the "Navigate > Object" command navigates to the implementation.

In the COMOS DB, the PPC is configured in such a way that the standard procedure is modified and the P&ID object remains the report object.



Consequence:

● In the context menu of the report, the "Navigate > Object" command navigates to the request.

● The "Navigate > Implementation" command navigates to the implementation.

However, the symbol of the implementation continues to be used on the report.

Settings in the PPC To modify the standard procedure, the PPC objects or @3D objects must have the following setting:

Properties, "Attributes > 3D geometry" tab, "UseSymbolOnly In the report, only use the symbol for the requirement" option: Active

Deactivating the option activates the standard procedure.

Evaluating the symbol script at the request or implementation The text placeholders are evaluated at the request or implementation dependent upon which text placeholder has a symbol script - regardless of whether the symbol script is defined at the implementation or the request.

Text placeholders evaluated at the request Text placeholders evaluated at the

implementation *V*P S: *V*P SI: *V*P E: *V*P EI: *V*P E:SYMBOL *V*P EI:SYMBOL

You can use the placeholders evaluated at the implementation, for example, to display the drive of the implementation on the P&ID report.

You can find more information on this topic in the "Reports - Basic Operation" manual, keyword "Subsymbols" or "Additional symbols".

7.9.8.4 Outputting the symbol of the request on the report

Procedure To output the symbol of the P&ID object on the P&ID report following pipe spec mapping, you must delete the symbol script for the corresponding drawing type at the PPC object.

Administration 7.10 Configuring the PipePart Finder


7.10 Configuring the PipePart Finder

7.10.1 Configuring queries You create all queries that you use in the PipePart Finder under one object in the base data. You enter this object in the template pipe spec on the "Function" tab in the "PipePartFinder" field.

Requirements If you want to use an attribute value of the pipe spec for a pipe part search, you must enter "*" as attribute value in the corresponding attribute of the used structure element in the pipe part catalog.

Procedure 1. Create a new query as usual for base objects. The name of the query must exactly match

the following property of the pipe part type that is to be processed:

– In PDMS pipe specs: GType

Example: "BEND"

– In COMOS pipe specs: Function code

Example: "21xxx"

2. Set the required structure object as start object of the query.



3. Create the required columns in the query by dragging the attributes to the table header using drag&drop. The column names must have the following structure:

<Tab>.<Attribute name> of the attribute whose content is to be displayed in the column.

4. Define filter criteria.

When you define filter criteria, the filter values are offered during creation of the template pipe spec on the "Pipe parts" tab.

Possible filter values:

– Value of the attribute linked with the column

– "<All>": During creation of the template pipe spec, you can select all values of the attribute of the objects below the start object that is linked to the column.

– "Val("<1st value>", <Connector>, "<2nd value>")":

1st Value: Table row on the "Characteristics" tab of the pipe spec in which a template pipe spec is used. This tab is searched for a value for the specified attribute. If a "*" is entered in this cell, COMOS jumps to the row specified in <2nd value>. This value describes the row for the pipe and contains a fixed value.

Example: "Val("C1.V1.SCH",1,"C1.V1.SCALC")"

Connector: If there are several connectors, it indicates to which connector of a component this syntax refers. Depending on the nominal diameter of the connector, the value is applied in the table on the "Characteristics" tab.

Alternatively: Direct access to a cell of the table on the "Characteristics" tab.

Example: "C1.V1.SCALC"

7.10.2 Creating template pipe classes

Requirements The queries of the structure element you want to use have been configured.

Procedure 1. Create a new pipe spec as usual.

2. Specify the nominal diameters and the standard on the "PipeSpec limits" tab.

3. Select the "Template pipe spec" entry from the "Function code" list on the "Pipe spec administration" tab.

4. Set the base object in the "PipePart Finder" field which contains the queries for the component search.



5. On the "Pipe spec administration > Pipe parts" tab choose the "Show filtered object query" option.

A tab is shown for each used query in the upper area of the "Pipe parts" tab. Which queries are actually used is determined by the object which you have specified beforehand in the "PipePart Finder" field on the "Function" tab.

6. On the right side of each tab set the filter criteria used to search for components. The offered filter criteria are determined by the information in the filters of the query.

Possible values:

– "<All>": No filter is used for this attribute.

– "*": No filter is used for this attribute. The attribute value is applied to the pipe.

– Val("<1st value>", <Connector>, "<2nd value>"): 1st Value: Row on the "Characteristics" tab that searches for a value for the corresponding attribute. If a "*" is entered here, COMOS jumps to the 2nd value. This value describes the row for the pipe and contains a fixed value.

Connector: Indicates to which connector of a component this syntax refers.

– <Fixed value>: Taken from the pipe part catalog.

Result: The query lists all matching base objects in the upper area of the "Pipe parts" tab.

7. Double-click one or more container objects of the pipe parts.

The container objects are moved to the lower area of the "Pipe parts" tab. These objects serve as start object in the search for pipe parts when using the template.

Result The template has been configured and can be used.


Reference to the COMOS DB 88.1 Bolt types

Overview The following bolt types are stored in the COMOS DB:

● Normal bolted joint

● Constant bolted joint

● Clamp bolted joint

● Blind hole bolted joint

● Mixed bolted joints:

– Clamp and blind hole bolted joint

– Normal and blind hole bolted joint

Matching entries in the "Bolted joint types" standard table The bolt types correspond to the following entries in the "@3D > 01 > BC > 03 Bolted joint types" standard table:

Bolt type Description of the standard table

entry "Value 1" of the standard table entry

Normal bolted joint "Normal" "1" Blind hole bolted joint "Blind hole" "2" Clamp bolted joint "T-branch" "3" Clamp and blind hole bolted joint "T-branch(LK) with blind hole(LK)" "4" Normal and blind hole bolted joint "T-branch(LK1) and blind hole(LK2)" "5" Constant bolted joint For extension -

Reference to the COMOS DB 8.1 Bolt types


Normal bolted joint Normal bolted joint is used as standard.

Different types of bolts can be used for a normal bolted joint, e.g. screw bolts with two nuts.

Example: DIN 601, ISO 4016***

Hexagon bolt Mxx

1 x nut Mxx

Optional: 2 x washers

Blind hole bolted joint Blind hole bolted joints are used when flange plates have blind holes. This means that the bolt cannot be pushed through. Different types of bolts can be used, e.g. hexagon bolts (without nuts), stud bolts (with nut).

Example:

Stud bolt Mxx

1 x nut Mxx

Optional: 1 x washer

Clamp bolted joint Clamp bolted joints are used with clamping parts (adapter flange parts or wafer types), e.g. long hexagon bolts with a nut.

Example: DIN 2510

Screw bolt Mxx

2 x nuts Mxx


Reference to the COMOS DB 8.2 Algorithm for calculating the screw length


Mixed bolt types The following mixed bolt types are available:

● Clamp and blind hole bolted joint

● Normal and blind hole bolted joint

Constant bolted joint Constant bolted joints require bolt types with fixed screw lengths. The screw length is not calculated. The bolts must be defined locally at the pipe part.

Example: DIN 601, ISO 4016***

Hexagon bolt Mxx with L = constant

1 x nut Mxx


8.2 Algorithm for calculating the screw length The type of bolted joint set at the flange determines which algorithm COMOS uses to calculate the screw lengths: "Attributes > 3D geometry" tab, "VD#3 Bolted joint" attribute, where "#" stands for the index number of the connector.

If the "constant bolted joint" type has been set, the screw lengths are fixed. The screw length is not calculated.

Screw length calculation for the normal bolted joint Example: Two flanges with gasket and normal bolted joint

Reference to the COMOS DB 8.2 Algorithm for calculating the screw length


SL = Screw length

The screw length is calculated as follows:

1. The clamping length is calculated.

2. The screw parameters are determined.

3. The theoretical screw length is calculated.

Calculation of the clamping length The clamping length is determined from the 3D model on the basis of topology.

Formula: Clamping length = Sheet thickness + gasket height + sheet thickness

● Gasket height: Is read out from the properties of the gasket, "3D geometry" tab, "Length (L)" attribute.

● Sheet thickness: Is read out from the properties of the flange, "3D geometry" tab, "Flange sheet height" attribute.

If the attribute is missing or blank, the internal calculation formula is used to determine which basic table the sheet thickness is read out from.

Determining the screw parameters ● The screw parameters listed in the following table are taken from the geometry standard

for flanges, from the nominal-diameter-dependent table on the "Dimensions" tab.

COMOS determines which basic table is used during runtime by evaluating parameters, such as the connection type and pressure stage of the flange.

Column Parameters Purpose "LK" Hole circle Checking "D" Outer diameter flange Checking "N" Number of screws For the number of screws on the list of

objects "DIM" Dimension for screws and nuts Search criterion "b" Hole diameter Checking

● Nut height and overlap are determined as follows:

– COMOS reads out the nominal diameter of the flange.

– COMOS reads out the corresponding dimension from the "DIM" column of the basic table containing the screw parameters.

– COMOS then refers to the basic table for nuts to determine which nut height and which overlap have been specified for this dimension.

● The height of the washers is determined as follows:

Same as nuts. COMOS takes the height of the washers from the basic table for washers.

Reference to the COMOS DB 8.3 Internal formulae for calculating component dimensions


Calculation of the theoretical screw length Now all parameters required to calculate the theoretical screw length are known.

Formula: Screw length = Hole circle + 2* height of the washer + nut height + overlap

COMOS searches the basic table for screws for the dimension specified by the basic table for flanges in order to find the value equal to the calculated screw length, or failing that the next highest value.

This value is the calculated screw length.

See also Fundamentals of bolt sets (Page 63)

Using bolt sets (Page 63)

8.3 Internal formulae for calculating component dimensions

Background It may be the case that 3D attributes required by COMOS to calculate the component dimensions have not been set or not even created on the "GD 3D geometry" tab.

In this case, COMOS uses internal calculation formulae which are fixed programmed in the software to calculate the dimension attributes.

List of internal formulae Attribute name Description Calculation formula "VC#5" Flange sheet height CatStd("PP.31.%VSTD%.%VFLG%.%VC#3%.%VC#2%","H

",#) "VC#6" Flange sheet diameter CatStd("PP.31.%VSTD%.%VFLG%.%VC#3%.%VC#2%","D

",#)

Reference to the COMOS DB 8.4 Properties of the example report for pipe spec documentation


Attribute name Description Calculation formula "VC#7" Height of flange For flange connections "VC13" = {100, 101, 140}

and "VC14" = {210, 220,310, 320, 410, 420, 510, 610, 810, 910}:

CatStd("PP.30.%VSTD%.%VFLG%.%VC#4%.%VC#2%"

,"f",#) For "VC13" ={710}:


,"f1",#) For loose flange connections "VC13" ={200, 220}:


,"s2",#) For loose flange connections "VC13" ={210, 221,

230}:


,"h3",#) "VC#8" Diameter of flange

flare/collar VC#6 * 0.9

"VC#9" Thread CatStd("PP.31.%VSTD%.%VC#3%","G1",#)

"LK1#", "LK2#" Hole circle diameter CatStd("PP.31.%VSTD%.%VFLG%.%VC#3%.%VC#2%","LK",#)

"N1#", "N2#" Number of screws CatStd("PP.31.%VSTD%.%VFLG%.%VC#3%.%VC#2%","N",#)

"DIM1#", "DIM2#" Screw dimension CatStd("PP.31.%VSTD%.%VFLG%.%VC#3%.%VC#2%","DIM",#)

See also The "CatStd()" function (Page 155)

8.4 Properties of the example report for pipe spec documentation The COMOS DB contains a preconfigured example report for pipe spec documentation.

The report was created at the following node from where it is inherited to all pipe spec base objects:

"@VIPER > @SPEC Pipe Specs"

Base object "@02 > 120 > PD > PDA > PDARK Data Sheet Pipe Spec"

Report template "CRp > @0 > PD > PDA > 013 Pipe Spec Component Documentation"

Reference to the COMOS DB 8.5 Properties of the example report for pipe part documentation


Script A list which implements the "OnCreate" script is placed on the report template. Do not delete this script.

8.5 Properties of the example report for pipe part documentation The COMOS DB contains a preconfigured example report documenting the pipe spec elements.

The report was created at the following node from where it is inherited to all base objects of the pipe spec elements:

"@VIPER > @PPC Pipe Part Catalogs"

Base object "@02 > 120 > PD > PDA > PDARK Data Sheet Pipe Spec"

Report template "CRp > @0 > PD > PDA > 014 Component Report"

Scripts The report template has a list which implements the following scripts:

● "OnCreate()"

● "GetAllParts(StartObj)"

● "CheckForGood(Obj)"

● "OK(Obj1)"

Do not delete the implementation.

8.6 Properties of norm objects

8.6.1 "Characteristic Definition" tab Name "Definition" Description "Characteristic Definition" Inheritance source "@VIPER > @STD > Definition Characteristic Definition" Function In the attributes of the tab, you define the ranges of values of the parameters

of the standardization.

Reference to the COMOS DB 8.6 Properties of norm objects


Properties of the attributes In the COMOS DB, the properties of the attributes are fully preconfigured. Do not change the preconfigured settings.

General properties of the attributes The following statements are valid for all attributes of the tab, with the exception of the following attributes:

● "NSYS Standard"

● "Unit Standard Unit"

General properties:

● There are the following attributes for each parameter:

– "from"

– "to"

– "Filter"

Use "from" and "to" to define a range of values. Then use a filter attribute to exclude individual values from the range of values.

● The attributes "from", "to", and the filter are each stored with the same standard table.

● All filter attributes implement the "FilterRow()" script block. The implementation dynamically adjusts the content of the filter list so that only entries that are located in the standard table between the entries set in "from" and "to" can be selected.

All filter attributes have the same implementation in the COMOS DB.

Properties of the attributes in detail The following subsections describe which standard tables and scripts the attributes must have in addition to the properties listed in "General properties of the parameters".

The order corresponds to the order in the properties.

"Standards system" attribute ● Name: "VSTD"

● Description: "Standards system"

● Purpose: Assigns a standards system to the norm object.

See also chapter Creating the new norm object (Page 86).

● Assigned standard table: "@3D > 01 > NSYS Standards system"

● Script block "OnChange()":

– Applies name and description of the standard table entry set here as name and description of the norm object.

– Apply COMOS DB implementation: "@VIPER > @STD > Definition > VSTD".



"Standard Unit" attribute ● Name: "Unit"

● Description: "Standard unit"

● Purpose: Defines the standard unit for the local dimensions at the pipe parts.

See also chapter Setting the standard unit (Page 90).

● Assigned units group: "M01 Length"

● Script block "OnChange()":

– Transfers the unit to the nominal-diameter-dependent tables of the standardization.

– Apply COMOS DB implementation: "@VIPER > @STD > Definition > Unit".

"Nominal diameter range" control group Assigned standard table: "@3D > 01 < 05 Nominal diameters"

"from" and "to" attributes:

● Name: "NDMin" and "NDMax"

● Description: "from" and "to"

● Purpose: Define the lower limit and the upper limit of the nominal diameter range.

● Script block: "OnChange ()"

– The script deletes the hidden attribute "Definition.V.VC11" by buffering the nominal diameter range for internal purposes.

– Apply COMOS DB implementation: "@VIPER > @STD > Definition > NDMin" and "... > NDMax".

Filter attribute:

● Name "NDRange"

● Description: "Filter"

● Purpose: Button which opens a list. In the list, filter nominal diameters of your choosing out of the nominal diameter range defined by the "from" and "to" attributes.

"Update NDs" button:

● Name: "Update"

● Description: "Update NDs"



● Purpose: Forwards the nominal diameters defined by "NDRange".

● Script block: "OnClick()"

– If values have already been input in the nominal-diameter-dependent tables manually, these values must not be moved and mixed by deleting a nominal diameter or by inserting one in the middle.

The script updates the nominal diameters in the nominal-diameter-dependent tables without deleting old entries and always appends new nominal diameters to the bottom end of the table.

– Apply COMOS DB implementation: "@VIPER > @STD > Definition > Update"

See also sections "Catalog Attributes" tab (Page 202) and Updating the nominal diameters (Page 97).

Attributes of other control groups Control group Name of the

attribute "from" Name of the attribute "to"

Name of the filter attribute

Standard table

"Nominal pressure range" "NPMin" "NPMax" "NPRange" "@3D > 01 > 04 Nominal pressures""Contact faces" "DFMin" "DFMax" "DFRange" "@3D > 01 > 06 Contact faces" "Technical norm" "VS041Min" "VS041Max" "VS041Range" "@3D > 01 > 01 Technical norms" "General norms" "VS017Min" "VS017Max" "VS017Range" "@3D > 01 > 03 Standards" "Material standards" "VS001Min" "VS001Max" "VS001Range" "@3D > 01 > 03 > 01 Material

standards" "Base materials" "VS115Min" "VS115Max" "VS115Range" "@3D > 01 > 07 > 01 Base

materials pipe specs" "Materials" "VS002Min" "VS002Max" "VS002Range" "@3D > 01 > 07 Materials" "Technical supply conditions"

"VS114Min" "VS114Max" "VS114Range" "@3D > 01 > 02 Technical Terms of Delivery"

"Connector standards" "VS015Min" "VS015Max" "VS015Range" "@3D > 01 > 03 > 07 Connector standards"

"Contact face standards" "VS050Min" "VS050Max" "VS050Range" "@3D > 01 > 03 > 06 Contact face standards"

"Pipe standards" "VS051Min" "VS051Max" "VS051Range" "@3D > 01 > 03 > 02 Pipe standards"

"Fitting standards" "VS052Min" "VS052Max" "VS052Range" "@3D > 01 > 03 > 03 Fitting standards"

"Valve standards" "VS053Min" "VS053Max" "VS053Range" "@3D > 01 > 03 > 04 Valve standards"

"Flange standards" "VS054Min" "VS054Max" "VS054Range" "@3D > 01 > 03 > 05 Flange standards"

"Outer diameter" "VS003Min" "VS003Max" "VS003Range "@3D > 01 > 09 Outer diameter" "Construction type elbows" "VS005Min" "VS005Max" "VS005Range" "@3D > 01 > 10 > 01 Construction

type elbows metric" "Valve series" "VS011Min" "VS011Max" "VS011Range" "@3D > 01 > 11 Dimension

Schedules Instruments"



Control group Name of the attribute "from"

Name of the attribute "to"

Name of the filter attribute

Standard table

"Schedule for welded and seamless pipes"

"VS081Min" "VS081Max" "VS081Range" "@3D > 01 > 08 > 09 > 2 Schedule for welded and seamless pipes"

"Dimensions of screws and nuts"

"VS1911Min" "VS1911Max" "VS1911Range" "@3D > 01 > 19 > 01 > 1 Screw dimensions to EN/DIN"

"Standard for screws and nuts"

"VS1912Min" "VS1912Max" "VS1912Range" "@3D > 01 > 03 > 09 Screw standards"

8.6.2 "StdVal1" and "StdVal2" tabs Name "StdVal1" "StdVal2" Description "Local Dimensions (DN)" "Local Dimensions (DN1/DN2)" Inheritance source

"@VIPER > @STD > StdVal1 Local Dimensions (DN)"

"@VIPER > @STD > StdVal2 Local Dimensions (DN1/DN2)"

Function Inheritance source for pipe parts from the pipe part catalog with one nominal diameter, "StdVal Local Dimensions" tab This is where you manage the local dimensions of the pipe part.

Definition of the permissible nominal diameter combinations

Inheritance source for pipe parts from the pipe part catalog with two nominal diameters, "StdVal2 Local Dimensions (DN1/DN2)" tab. This is where you manage the local dimensions of the pipe part.

Properties of the attributes In the COMOS DB, the properties of the attributes are fully preconfigured. Do not change the preconfigured properties.

The following is an overview of the properties and scripts of the attributes.

"Standard" list ● Name: "VSTD"

● Description: "Standard"

● Standard table: "@3D > 01 > NSYS Standards system"

● Purpose: Used internally. Do not configure the attribute.

"Nominal-diameter-dependent table" table ● Name: "V"

● Description: "Nominal-diameter-dependent table"

● Purpose: Defines geometry parameters based on the nominal diameter.



● Display properties:

"Row display": "Extend dynamically", as otherwise you cannot update the table subsequently in order to add new rows.

● Columns:

The standardization defines all the geometry parameters/columns that are required for the pipe parts. No new columns are added in the pipe part catalog.

"V.VC11" and "V.VC21" columns:

● Description: "Nominal diameter" and "Nominal diameter2"

● Purpose: Defines the nominal diameter or nominal diameter combination for which the remaining parameter values are valid.

● Values for the "StdVal1" tab:

– All nominal diameters which have ever belonged to the standardization.

– Inheritance source: "CatSpec.V.VC11"

– Do not set the values manually. The values are updated via the standardization: "Characteristic Definition" tab, "Update NDs" button

● Values for "StdVal2":

– All nominal diameter combinations which have ever been entered for the standardization.

– The values are entered manually.

– "VC11": The main nominal diameter

– "VC21": The nominal diameter of the branch

– Type: Edit field (editable combo box)"

– Standard table: "@3D > 01 > 05 Nominal diameters"

– Scripts: "FillComboList" and "FilterRow"

See also chapter "Catalog Attributes" tab (Page 202).

Other columns:

● Remain blank at the standardization. You can enter local dimensions in the table in the pipe part catalog.

● Unit: Specified at the standardization in the "Standard Unit" attribute on the "Characteristic Definition" tab.

● Column name: The name matches the legend of the cross-section drawing located at the pipe part on the "GD 3D geometry" tab and in the geometry basic tables on the "BMP Descriptions" tab.

See also chapter Configuring the "Local Dimensions (DN1/DN2)" tab (Page 95).



See also Excluded from the configuration (Page 99)

"StdVal Local Dimensions ..." tab (Page 139)

Setting the standard unit (Page 90)

8.6.3 "Screw dimensions" tab Name "StdVal4" Description "Screw dimensions" Inheritance source "@VIPER > @STD > StdVal4 Screw dimensions" Function Defines which dimension values are valid for screws, nuts, and washers

based on this standardization. The dimensions are inherited to the "Screw lengths" tab of the

standardization. The tab is inherited to the standard catalog for geometry standards, to the node for screws.

The dimensions are inherited to the "Washer dimensions" tab of the standardization. The tab is inherited to the standard catalog for geometry standards, to the node for washers.

Inheritance source for the tab in which you enter the nut height, overlap, and pitch in the standard catalog for geometry standards: "StdVal Screw dimensions"

Inheritance source for nuts from the pipe part catalog, "StdVal4 Screw dimensions" tab

This is where you manage the local dimensions for nuts.


The following subsections provide an overview of the properties and scripts of the attributes.







"Dimension-dependent table" table ● Name: "V"

● Description: "Dimension-dependent table"

● Purpose: Defines the geometry parameters of nuts based on dimension.



● The standardization defines all necessary columns. No new columns are added to the standard catalog for geometry standards or the pipe part catalog.

● "DIM" column:

– Name: "VC11"

– Description: "DIM"

– Purpose: Here you define the dimension values for screws, nuts, and washers.

– Standard table: "@3D > 01 > 19 > 01 > 1 Screw dimensions to EN/DIN"

● Other columns:

Name Description Purpose Configuration "M" "M" Nut height "UEB" "UEB" Overlap "P" "P" Pitch

Remain blank at the standardization. You can enter local dimensions in the table in the pipe part catalog.

8.6.4 "Screw step lengths" tab Name "StdVal5" Description "Screw step lengths" Inheritance source "@VIPER > @STD > StdVal5 Screw step lengths5" Function Specifies the screw step lengths by geometry standard.

Inheritance source for the tab in which you enter the weights and material numbers of the screws at the basic tables in the standard catalog for geometry standards. "StdVal5 Screw step lengths"









"Length-dependent table" table ● Name: "V"

● Description: "Length-dependent table"

● Purpose: Specifies the screw step lengths by geometry standard. Remains blank at the standardization.



● Columns:

The standardization defines all necessary columns. No new columns are added in the standard catalog for geometry standards.

● Column: "V.VC11"

– Description: "LEN"

– Purpose: Here you define the screw lengths permitted in the geometry standards.

– Standard table: "@3D > 01 > 05 Nominal diameters"

● "WT" column:

Name: "V.WT"

Description: "WT"

Purpose: Remains blank at the standardization. Here you enter the weight at the basic tables in the standard catalog for geometry standards.

● "ID" column:

Name: "V.ID"

Description: "ID"

Remains blank at the standardization. Here you enter the material numbers at the basic tables in the standard catalog for geometry standards.



8.6.5 "Screw lengths" tab Name "StdVal3" Description "Screw lengths" Inheritance source "@VIPER > @STD > StdVal3 Screw lengths" Function Inheritance source for the node of the standard catalog for geometry

standards, which saves the geometry of the screws. This is where you enter which screw step lengths are permitted for which dimensions on the layer which defines the screw standard.







"Length-dependent table" table ● Name: "V"

● Description: "Length-dependent table"

● Purpose: Defines which lengths are permitted on the basis of the dimensions.



● The standardization defines all necessary columns. No new columns are added to the standard catalog for geometry standards or the pipe part catalog.

● The table is not configured at the standardization.



● "DIM" column:

– Name: "VC11"


– Purpose: The dimensions


– Inheritance source: "Screw dimensions" tab of standardization, "V.VC11" attribute

– Values: Adopted automatically by the inheritance source.

● "L<counter>" column:

– Name: "L<counter>"

– Description: "L<counter>"

– Purpose: The length

– Values: Remain blank at the standardization. In the standard catalog for geometry standards, enter the screw lengths on the layer which defines the screw standard.

8.6.6 "Washer dimensions" tab Name "StdVal6" Description "Washer dimensions" Inheritance source "@VIPER > @STD > StdVal6 Washer dimensions" Function Inheritance source for the tab in which you enter the heights of the washers in

the standard catalog for geometry standards: "StdVal6 Washer dimensions"







"Dimension-dependent table" table ● Name: "V"

● Description: "Dimension-dependent table"



● Purpose: Defines the height of the washers based on dimension.



● The standardization defines all necessary columns. No new columns are added in the standard catalog for geometry standards.

● The table is not configured at the standardization.

● "DIM" column:

– Name: "VC11"


– Purpose: The dimensions


– Inheritance source: "Screw dimensions" tab of standardization, "V.VC11" attribute

– Values: Adopted automatically by the inheritance source.

● "M" column:

– Name: "M"

– Description: "M"

– Purpose: The height of the washer

8.6.7 "Catalog Attributes" tab Name "CatSpec" Description "Catalog attributes" Inheritance source "@STD Standardizations" Function The tab defines a nominal-diameter-dependent table.

The table maps the nominal diameter range of the standardization. It serves as the inheritance source for the nominal-diameter-dependent tables of the standardization, the standard catalog for geometry standards, and the pipe part catalog.

Table contents Do not configure the table manually. The table remains blank at the standardization, with the exception of the "V.VC11 Nominal diameter" column.

When you press the "Update NDs" button at the standardization on the "Characteristic Definition" tab, the "Nominal diameter" column is automatically filled or updated as appropriate. Values that are no longer valid are not deleted. New values are always appended at the bottom end of the table.



Reason: If the nominal diameter range of a standardization is changed after standard catalog entries have been made for this standardization, the dimension values entered in the standard catalogs cannot be moved or mixed by deleting a nominal diameter or inserting a new one in the middle. The same applies to any local dimension that had already been maintained.

Properties of the table Name "V" Description "Nominal-diameter-dependent table" Display properties "Row display": "Extend dynamically" as COMOS cannot update the

table and add new rows otherwise. "VC11Nominal diameter" column:

Standard table: "@3D > 01 > 05 Nominal diameters"



Data flow The table serves as the inheritance source for the following nodes:

● Standard catalog for geometry standards, "StdVal Dimensions" tab, "V" table:

– The basic tables

– The attributes catalog is an intermediate stage for inheritance: "@3D > @STD > CatTab > CatStd Tabs Basic Tables"

– Depending on the type of geometry standard, columns for other geometry parameters are added to the table.

● Pipe part catalog, "StdVal Local Dimensions (DN1)" or "... (DN1/DN2)" tab respectively:

– The nominal-diameter-dependent table "V" in which the local dimensions are entered

– The "StdVal1 Local Dimensions (DN)" and "StdVal2 Local Dimensions (DN1/DN2)" tabs of the standardization are intermediate stages for inheritance

● Pipe part catalog, pipe parts with one nominal diameter, "VDM Data Sheet" tab:

– Nominal-diameter-dependent table "V", in which various nominal-diameter-dependent component data items are entered.

– The attributes catalog is an intermediate stage for inheritance: "@3D > @STD > CatTab > VDM Tab Data Sheet"

This is where the table is extended by several columns in which the nominal-diameter-dependent physical data, standardization data, and interfaces of the pipe part are then maintained:

Note Pipe parts with two nominal diameters

The table does not serve as the inheritance source for the "VDM Data Sheet" tab of pipe parts with two nominal diameters.

In the case of pipe parts with two nominal diameters, you must enter the nominal diameter combinations manually in the nominal-diameter-dependent table on the "Data Sheet" tab.

If you change the nominal diameter range of the standardization, you must also forward the changes to the derived nominal-diameter-dependent tables:

Click the "Update NDs" button on the "Characteristic Definition" tab.

The button updates the "Nominal diameters" column of the table. The inheritance chain in the database forwards this update to the basic tables and the pipe parts.

The inheritance chain must not have been broken by nominal diameters being added to the column manually on one of the levels. This would prevent the update.

See also Attributes catalog of the standard catalog (Page 109)

The "Dimensions" tab (Page 206)


Reference to the COMOS DB 8.7 Properties of the objects in the standard catalog for geometry standards


8.7 Properties of the objects in the standard catalog for geometry standards

8.7.1 The "Descriptions" tab Name "BMP" Description "Descriptions" Inheritance source The subnode of "@VIPER > @STD > CatTab Kenngrößenreihen abhängige

Tabellen (CatStd, VDM, VWD) ", which corresponds to the node from the standard catalog. Example: For "@VIPER > @CATSTD > PP > 31 > 1 > 1 > 101 > 10 PN 10 to DIN 28117": The inheritance source is "@VIPER > @STD > CatTab > 31 > 1 > 101 > BMP Designations".

Function Contains a cross-section drawing of the component and some managed attributes.

Attributes In the COMOS DB, the properties of the attributes are fully preconfigured. Do not change the preconfigured settings.

The tab has the following attributes:

Name Description Purpose "Rule" "ParameterName" List to structure the standard catalog. Do not

change the values of the catalog supplied with the COMOS DB. Assigned standard table: "@3D > 01 > RU Standard table Parametrics".

"VS123" "VS123" "VS125"

"Remarks on the standard" "Output" "Revision"

Document the geometry standard, management function.

"WMF" / The cross-section drawing of the pipe part with the dimension designations. The cross-section drawing serves as a legend for the geometry parameters of the nominal-diameter-dependent table on the "Dimensions" tab.



8.7.2 The "Dimensions" tab The tab has a different description and a different inheritance source for screws and screw parts. See also chapter Tabs of the geometry standards for screw parts (Page 208).

Name "StdVal" Description "Dimensions" Inheritance source The subnode of "@VIPER > @STD > CatTab Kenngrößenreihen abhängige

Tabellen (CatStd, VDM, VWD) ", which corresponds to the node from the standard catalog. Example: For "@VIPER > @CATSTD > PP > 31 > 1 > 1 > 101 > 10 PN 10 to DIN 28117": The inheritance source is "@VIPER > @STD > CatTab > 31 > 1 > 101 > StdVal Dimensions".

Function Defines the dimensions of the pipe part based on the nominal diameter.

Attributes In the COMOS DB, the properties of the attributes are fully preconfigured. Do not change the preconfigured settings.



The tab has the following attributes:

Name Description Purpose "VS010" "to standard" Do not use. "V" "Nominal-

diameter-dependent table"

Defines the geometry parameters of the pipe part based on the nominal diameter. "V.VC11 Nominal diameter" column and for pipe parts with two

nominal diameters "V.VC12 Nominal diameter 2" column The nominal diameters

The values are taken from the standardization when the "Update NDs" button is pressed on the "Characteristic Definition" tab.

For pipe parts with two nominal diameters:

"V.VC12 Nominal diameter 2" column Remaining columns: The geometry parameters

The columns are defined in the attributes catalog of the standard catalog.

The actual dimensions are only entered on the lowest layer of the standard catalog, in the basic tables.

The column names match the names of the geometry parameters from the cross-section drawing on the "Descriptions" tab.

"Update" "Update" Button which deletes the dimensions stored in the buffer and reloads the dimensions from the nominal-diameter-dependent table.

If you have edited a value in the table, use the button to update the 3D objects which use this basic table.

Script block "OnChange": Apply COMOS DB implementation.

See also Attributes catalog of the standard catalog (Page 109)

Structuring by the "ParameterName" attribute (Page 103)

"Catalog Attributes" tab (Page 202)

Reference to the COMOS DB 8.8 Properties of the pipe parts in the PPC


8.7.3 Tabs of the geometry standards for screw parts The nodes for screws, nuts, and washers have the following tabs:

Screws Nuts Washers "BMP Descriptions" tab: See also chapter The "Descriptions" tab (Page 205). "StdVal Screw lengths": Inheritance source: "StdVal3 Screw

lengths" tab of the corresponding standardization

Is configured on the layers for screw standards.

See also chapter "Screw lengths" tab (Page 200).

"StdVal Screw dimensions": Inheritance source: "StdVal4 Screw

dimensions" tab of the corresponding standardization

Is configured on the layers for nut standards.

See also chapter "Screw dimensions" tab (Page 197).

"StdVal Washer dimensions": Inheritance source: "StdVal6

Washer dimensions" tab of the corresponding standardization

Is configured on the layers for washer standards.

See also chapter "Washer dimensions" tab (Page 201).

"StdVal5 Screw step lengths": Inheritance source: "StdVal5 Screw

step lengths" tab of the corresponding standardization

Is configured at the basic tables. See also chapter "Screw step

lengths" tab (Page 198).

- -

8.8 Properties of the pipe parts in the PPC

8.8.1 Tabs and attributes Administering pipe part catalogs (Page 125) contains an overview of the tabs and attributes of the pipe parts from the pipe part catalog and how they are configured.



8.8.2 Parameters dependent upon on the standards system

8.8.2.1 Principle behind attributes which are dependent upon standards systems

The concept behind dependent attributes Some parameters must meet the following requirements for the configuration of a pipe part:

● The values listed for selection shall always be determined by the standards system.

In other words, the user should not be offered all of the values from the assigned standard table for selection. The list should be filtered so that the user only sees the values located within the range of values of the standardization assigned to the standards system.

● If the user sets a different standards system, only the values located within the range of values of the assigned standardization should automatically remain available for selection. The value already set should be converted automatically to a value corresponding to the new standardization.

To meet this requirement, two attributes must be managed:

● The standards system attribute:

It defines which standards system is valid.

● The dependent attribute:

Its values vary within the framework specified by the standards system.

The attributes must have certain properties. In particular, they must implement various scripts.

Examples for dependent attributes ● Flange standard

● Connection type

See also Properties of a standards system attribute (Page 211)

Properties of a dependent attribute (Page 212)

8.8.2.2 Filtering parameter values of the standards system

Initial situation A user clicks the button next to a parameter which is a dependent attribute to view the list of possible values.



Requirements The dependent attribute and the standards system attribute have the properties required for this functionality.

Principle When a user expands the dependent attribute list, COMOS searches for a matching standards system attribute on the same tab.

An attribute whose name comprises the following components counts as matching:

"VSTD" + "<name of the dependent attribute>"

If COMOS finds such an attribute, it filters the list and only displays values which are located in the range of values of the standardization set in the standards system attribute.

If COMOS is unable to find such an attribute, it checks whether the attribute is registered as a dependent attribute in the "DependentSpecs()" function of another standards system attribute. To do this, COMOS searches all tabs of the pipe part.

If the attribute is registered as a dependent attribute in the "DependentSpecs()" function of another standards system attribute, COMOS filters the dependent attribute on the basis of the standardization entered in that standards system attribute.

See also Properties of a standards system attribute (Page 211)

Properties of a dependent attribute (Page 212)

8.8.2.3 Converting the parameter values for change of standards system

Initial situation A user changes the standards system at a standards system attribute, although a value has already been entered at a dependent attribute.

Requirements ● The dependent attribute and the standards system attribute have the properties required

for this functionality.

● The "Mapping QuerySet" link table is located underneath the standardization assigned to the standards system originally set. Queries defining which value is assigned to the parameter when the standards system changes are located underneath the link table.

Principle COMOS searches for the "Mapping QuerySet" link table underneath the standardization assigned to the standards system originally set.



Queries for important parameter standard tables have been prepared underneath the link table. Here the user defines which value is to be set when the standards system is changed.

COMOS assigns the values defined by the queries to all attributes registered as dependent attributes at the standards system attribute in the "DependedSpecs()" function.

Queries underneath the "Mapping QuerySet" link table The start object of the queries is the standard table assigned to the parameter at the norm object.

The query displays all entries in the standard table which are located within the range of values specified by the standardization.

In the columns for the other standardizations, enter the value to which the parameter is to be converted when the standards system changes. The value must originate from the range of values designated by this standardization for the parameter.

8.8.2.4 Properties of a standards system attribute So that parameters can be managed on the basis of a standards system, the standards system attributes must be configured as described in this section.

General properties ● Assigned standard table:

"@3D > 01 > NSYS Standards system"

● Name:

– Starts with the characters "VSTD"

– If the standards system attribute does not implement the "DependedSpecs()" function:

"VSTD" + "<name of the dependent attribute>"

Example: "VDS.VS040 Valve standard" and "VDS.VSTD040 Standard"

Restriction: The dependent attributes must be located on the same tab as the standards system attribute.

Function "DependentSpecs()" ● Properties, "Script" tab, "UserScriptBlock1()" script block, "DependentSpecs()" function

● Call:

– A user clicks the button next to the dependent attribute to view the list of possible values.

– A new value is assigned to the standards system attribute.

● Goal: Register random attributes of the pipe part as dependent attributes in the array Arr.

● Example implementation:



Function DependentSpecs() ReDim Arr(4) Arr(1) = "VS015" Arr(2) = "VS025" Arr(3) = "VS035" Arr(4) = "VS045" DependentSpecs = Arr End Function

Script block "IsValueValid(ValueStr)" ● Properties, "Script" tab, "IsValueValid(ValueStr)" script block

● Call: A new standards system is assigned to the standards system attribute.

● Goal: Convert the value of the dependent attributes automatically, so that a matching value from the range of values specified by the new standardization is set.

● Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02 > VSTD"

● Effect: When a new standards system is set, the script saves the old standards system so that the software is able to convert the values of the dependent attributes correctly using the mapping query.

Script block "OnChange()" ● Properties, "Script" tab, "OnChange()" script block

● Call: A new standards system is assigned to the standards system attribute.

● Goal: Convert the value of the dependent attributes automatically, so that a matching value from the range of values specified by the new standardization is set.

● Apply COMOS DB implementation: "@VIPER > @Y > @3D > @PP > 02 > VSTD"

● Effect: When a new standards system is set, a search is carried out for the "Mapping QuerySet" object under the new standards system. Underneath it are queries defining the value a parameter should be set to in the event that the standards system of the parameter changes.

8.8.2.5 Properties of a dependent attribute So that parameters can be managed on the basis of standards system, the dependent attributes must be configured as described in this section.

Script block "FilterRow(StdTabItem)" Properties, "Script" tab, "FilterRow(StdTabItem)" script block: Apply the implementation of the COMOS DB.

Example attribute with this type of implementation: "@VIPER > @Y > @3D > @PP > 02 > VS012"



8.8.3 GetDisplayValue()

Requirements An attribute of the pipe part has been saved with a standard table.

Principle When you click on the button next to the attribute to view the list of possible values, you see the description of the standard table entries. This text is sometimes very long, e.g. in the case of standard tables for standards.

Long descriptions are not suitable as "DisplayValue", as they sometimes cannot be displayed in full in the user interface.

In this case, use the text from "Value 3" of the standard table entries. Use the implementation of the "GetDisplayValue()" script block described below for this purpose.

When you expand the list you continue to see the description.

Implementation of the "GetDisplayValue()" script block Properties of the attribute, "Scripts" tab, "GetDisplayValue()" script block: Apply the implementation of the COMOS DB.

Example attribute with this type of implementation:

"@VIPER > @Y > @3D > @PP > 02 > VS041"

8.8.4 Navigator description from pipe part attributes

Principle "Text blocks" tab, "Component created text" control group, "VST01 Description" attribute: The values of the attributes entered in the "TValue" calculation formula can be compiled to form a string describing the pipe part.

If the pipe part and the attributes used in the calculation formula implement the scripts described below, this string is automatically set as the description of the pipe part and is also displayed in the Navigator.

Requirements Properties of the pipe part, "System" tab, "General" control group: A description has not yet been entered in the "Description" property.



Script of the pipe part Properties of the pipe part, "Script" tab, "UserScriptBlock1" script block, "SetCDeviceDescription()" function: Take over the implementation of the COMOS DB from the "@VIPER > @PPC" node.

Attributes script If the value of one of the attributes evaluated in the "TValue" calculation formula changes, this change should be taken into account immediately. For this to happen, the attributes must implement the "OnChange" script block as in the COMOS DB.

Example attribute with this type of implementation:

"@VIPER > @Y > @3D > @PP > 02 > VS006"

See also "VTX Text blocks" tab (Page 141)

"VDS Part description" tab (Page 130)

8.8.5 Reserved attribute names

Attribute names reserved for 3D attributes on the "3D geometry" tab The following table lists all attribute names which are reserved on the "GD 3D geometry" tab in the pipe part catalog for 3D attributes. Some of the names are parameterized on the basis of connectors. "#" stands for the index number of the connector to which the attribute relates:

Attribute name Description/Function "DIM1#" Screw dimension "DIM2#" Screw dimension with mixed bolted joint "Layer" Layer "LK1#" Hole circle diameter "LK2#" Hole circle diameter with mixed bolted joint "N1#" Number of screws "N2#" Number of screws with mixed bolted joint "VC#1" Nominal diameter "VC#2" Nominal pressure "VC#3" Connection type "VC#4" Contact face "VC#5" Flange sheet height "VC#6" Flange sheet diameter "VC#7" Height of flange "VC#8" Diameter of flange



Attribute name Description/Function "VC#9" Thread "VCOL" Color "VD#1" Alternative catalog with flange sheet dimensions "VD#2" Alternative catalog with flange dimensions "VD3#" Bolted joint type "VD4#" Integral gasket height "VD5#" Integral gasket diameter "VD6#" Reserved "VD7#" Blind hole depth "VFLG" Flange standard "VGEO" Geometry "VSTD" Standardization

See also "GD 3D geometry" tab (Page 144)

8.8.6 Scripts for pipe spec mapping

Application area You can use the interaction between P&ID, PPC and 3D to execute, for example, a pipe spec mapping in a P&ID report. See also chapter Interaction P&ID-PPC-3D (Page 169).

Implementing the "On Edit()" script block To establish interaction between P&ID, PPC, and 3D, the attributes for the pipe spec and the nominal diameter of the PPC object must implement the "On Edit()" script block as described below.

The scripts must not be deleted, even if pipe spec mapping is not required in a P&ID.

Attribute Script

Name: "GD.VPCL" Description: "Pipe spec"

Script block "OnEdit": Take over the implementation of the COMOS DB from the "@VIPER > @Y > @3D > @PP > 01 > VPCL" node.

Attribute Script

Name: "GD.VC#1", where #" stands for the index number of the connector.

Description: "Nominal diameter"

Script block "OnEdit": Take over the implementation of the COMOS DB from the "@VIPER > @Y > @3D > @PP > 01 > VC#1" node.



8.8.7 Inheritance of the nominal diameters and pipe spec

Application area Interaction between P&ID, PPC, and 3D.

Introduction The component dimensions are parameterized through the nominal diameter, nominal pressure, connection type, and contact face. The nominal pressure, connection type, and contact face have already been defined for the PPC components. The nominal diameter of the PPC object is inherited from one of the following sources:

● From the request, as long as it is a P&ID object with function code

● For objects which are both P&ID objects and PPC objects at the same time, i.e. for P&ID objects with the "GD" tab: From some entries from the "PI030 Technical data" tab.

● For PPC objects, for which there is no direct P&ID equivalence, as is the case with pipes, elbows, and bends, for example: From the pipe branch

Static link for nominal diameters and pipe spec The attributes for the nominal diameter ("GD.VC#1", where "#" stands for the index number of the connector) and for the pipe spec ("GD.VCPL") must have a static link.

Link type:

● "By script function <GetLinkedSpecification()>"

● For experienced users: "Via navigation assistant"



Implementation of the "GetLinkedSpecification()" script block Use the implementation below. Dependent upon which attribute you link, assign the following value to the "LinkSpecName" variable:

Attribute name Value of "LinkSpecName" "GD.VC11" "PI030.PIA008" "GD.VC21","GD.VC31" "PI030.PIA008a" "GD.VPCL" "PI030.PIA012" Function GetLinkedSpecification() 'Script function to determine a linked attribute 'Static links: Always accept differences for object... ' Return value: Specification object LinkSpecName = "PI030.PIA012" Set specowner = GetSpecOwner() If specowner.SystemType <> 8 Then Exit Function DynConn = false Set BackPointerColl = specowner.backpointerdeviceswithimplementation If BackPointerColl.Count = 0 Then Set BackPointerColl = specowner.BackPointerConnectorsWithD3Implementation DynConn = true End If If BackPointerColl.Count > 0 Then 'Request Set dev = BackPointerColl.Item(1) If DynConn Then Set GetLinkedSpecification = dev.owner.spec(LinkSpecName) If GetLinkedSpecification Is Nothing Then 'Branch segmented Set GetLinkedSpecification = dev.owner.owner.spec(LinkSpecName) End If Else Set GetLinkedSpecification = dev.spec(LinkSpecName) End If Else 'Old default, try at own object Set GetLinkedSpecification = specowner.spec(LinkSpecName) If GetLinkedSpecification Is Nothing Then 'Pipe segment Set GetLinkedSpecification = specowner.owner.spec(LinkSpecName) End If End If End Function



Attribute link through DisplayValues Before COMOS version 8.2 there were problems with the static linking of attributes for nominal diameters.

Reason: If the nominal diameter attributes for a P&ID object and for a PPC object use different standard tables, the Values of the standard table entries will usually also differ.

Therefore, from version 8.2 onwards there is a new, general method that allows the scripted linking of attributes through DisplayValues instead of through Values:

● Open the properties of the attribute.

● Select the "Link" tab. Make the following settings:

– "Link type": "By script function <GetLinkedSpecification()>"

– "Value" input group: "Static"

– "Value/range" input group, "Own" field: "Operator" has the value "Script"

Implement the "CheckStaticLinkValues" and "GetStaticLinkSetValue" scripts on the "Script" tab as described in the examples.

Example 1: Nominal diameters ("GD.VC#1") Here the link is simulated by means of the DisplayValue. The source attribute can have another standard table or no standard table:

● Script block "CheckStaticLinkValues": Function CheckStaticLinkValues (Value1, Value2) 'Will be called when using the operator 'Script' at a static link ' Input: Value1, Value2 -> Values to compare CheckStaticLinkValues = True Set LinkSpec = Me.GetStaticLinkedSpecification If LinkSpec Is Nothing Then Exit Function CheckValue = LinkSpec.DisplayValue CheckStaticLinkValues = (CheckValue = Me.DisplayValue) End Function

● Script block "GetStaticLinkSetValue": Function GetStaticLinkSetValue (value, spec) 'Will be executed on updating of a static link ' Input: Value ->linked value ' Input: Spec -> Link source ' Output: Value to set on the target specification 'The return value is String GetStaticLinkSetValue = "" If spec Is Nothing Then Exit Function LinkDisplayValue = spec.DisplayValue If LinkDisplayValue = "" or LinkDisplayValue = "-" Then Exit Function Set StdTable = Me.StandardTable If StdTable Is Nothing Then Exit Function GetStaticLinkSetValue = Me.GetValueFromStandardValueDescription(LinkDisplayValue) End Function



Example 2: Nominal pressures ("GD.VC#2") ● Script block "CheckStaticLinkValues": Function CheckStaticLinkValues (Value1, Value2) 'Will be called when using the operator 'Script' at a static link ' Input: Value1, Value2 -> Values to compare Value2 = "PN " + Value2 CheckStaticLinkValues = (me.GetValueFromStandardValueDescription(Value2)=Value1) End Function

● Script block "GetStaticLinkSetValue":

Function GetStaticLinkSetValue (value, spec) ' Will be called when updating a static link ' Input: Value -> linked value ' Input: Spec -> link source ' Output: Value to be set at the target attribute ' The return value is of type string Value2 = "PN " + spec.DisplayValue GetStaticLinkSetValue = me.GetValueFromStandardValueDescription(Value2) End Function

Example 3: Connector ("PI030.PIA013") 1:N links are possible for connectors.

● Script block "CheckStaticLinkValues": Function CheckStaticLinkValues (Value1, Value2) 'Will be called when using the operator 'Script' at a static link ' Input: Value1, Value2 -> Values to compare CheckStaticLinkValues = false Select Case Value2 Case "0" CheckStaticLinkValues = (Value1 = "00") Case "100","101","120","130","140","200","210","220","221","230" CheckStaticLinkValues = (Value1 = "FL" or Value1 = "11" or Value1 = "12") Case "410" CheckStaticLinkValues = (Value1 = "410") 'Welded Case "406","407" CheckStaticLinkValues = (Value1 = "40") 'Bolted Case "404" CheckStaticLinkValues = (Value1 = "404") 'Internal thread Case "405" CheckStaticLinkValues = (Value1 = "405") 'External thread End Select End Function

● Script block "GetStaticLinkSetValue": Function GetStaticLinkSetValue (value, spec) ' Will be called when updating a static link ' Input: Value -> linked value ' Input: Spec -> link source

Reference to the COMOS DB 8.9 Properties of unit objects


' Output: Value to be set at the target attribute ' The return value is of type string PPCValue = spec.value Select Case PPCValue Case "0" GetStaticLinkSetValue = "00" Case "100","101","120","130","140","200","210","220","221","230" GetStaticLinkSetValue = "FL"'Flanged ' StaticLinkSetValue = "11"'Groove ' StaticLinkSetValue = "12"'Spring Case "410" GetStaticLinkSetValue = "410" 'Welded Case "406","407" GetStaticLinkSetValue = "40" 'Bolted Case "404" GetStaticLinkSetValue = "404"'Internal thread Case "405" GetStaticLinkSetValue = "405"'External thread End Select End Function

See also Interaction P&ID-PPC-3D (Page 169)

8.9 Properties of unit objects

8.9.1 General properties In the COMOS DB, the unit objects have all tabs necessary for standard procedures. If the unit objects are to deviate from standard procedures, additional tabs or attributes and settings can be added.

You find additional information on this topic in the "COMOS Administration" and "P&ID" manuals.

8.9.2 The "PSM001 Pipe spec management" tab Name "PSM001" Description "Pipe spec administration" Inheritance source "@VIPER > @Y > CHP > VIPER > PSM001 Pipe spec

administration" Function Here users define project pipe specs in the engineering data.

The pipe parts underneath the unit object may only use the project pipe specs.

Reference to the COMOS DB 8.10 Properties of P&ID objects


Attributes of the tab:

Name Description Purpose "PSMQuery" "Selected pipe

specs" Query which groups the pointers to the pipe specs permitted in the substructure (project pipe specs)

"PSMA<counter>" / Pointer to the base object of the project pipe spec Created dynamically as soon as you drag&drop the base

object of a pipe spec to the query. Is displayed in the "Pipe spec" column of the "PSMQuery"

query.

See also Using project pipe specs (Page 69)

8.10 Properties of P&ID objects This section contains information about the properties and scripts of P&ID objects which are significant in conjunction with pipe specs and the link between the pipe part catalog and the P&ID catalog.

The P&ID objects are preconfigured accordingly in the COMOS DB.

You find additional information on this topic in the "COMOS Administration" and "P&ID" manuals.

See also Using project pipe specs (Page 69)

8.10.1 "FillComboList" for the use of project pipe specs

Background If you implement "FillComboList" as described below, the user can only assign project pipe specs to the P&ID object in the engineering data.

Implementation of "FillComboList" "PI030.PIA012 Pipe spec" attribute, "FillComboList" script block:

The script block must have the same implementation as was saved in the COMOS DB as an example for pipe branches in the "@10 > PID > 3 > 01 > PI030 > 01 > PI030 > PIA012Pipe spec" node.



8.10.2 Deactivating the standard check with "IsImplementationValid" and "OnImplementationSet"


See also chapter Interaction P&ID-PPC-3D (Page 169).

Introduction When you link the P&ID catalog to the pipe part catalog, the implementation link is diverted from its intended use. Therefore, it is necessary to deactivate the standard checks carried out automatically by COMOS.

Deactivating standard check Properties of the P&ID object, "Scripts" tab, "IsImplementationValid(Device)" and "OnImplementationSet(Oldvalue)" script blocks:

Deactivate the standard checks by applying the implementations of the "@01 > PID > 01 > 03 Pipes" node from the COMOS DB.

8.10.3 Scripts for pipe spec mapping


Scripts for carrying out pipe spec mapping If pipe spec mapping is to be possible for a P&ID object, the P&ID object must implement the following scripts as described in the table.

Delete or deactivate the scripts if you do not require pipe spec mapping.



Attribute Script block Implementation The attribute specified in the project properties. In the COMOS DB: "PI030.PI012 Pipe spec" Required to create the implementation.

"OnChange" Apply the implementation of the COMOS DB: "@10 > PID > 0 > 01 > PIA012"

The attribute specified in the project properties. In the COMOS DB: "PI030.PI008 Nominal diameter input" and "PI030.PI008a Nominal diameter output" These are the attributes specified in the project properties. Required to create the implementation.

"OnChange" Apply the implementation of the COMOS DB: "@10 > PID > 0 > 01 > PIA008"

Name: "PI030.Update3D" Button to apply changes after the initial creation of the implementation.

"OnClick" Sub OnClick() 'Event: After pressing the button Set RILib = owner.Workset.Lib.ri RILib.PipeClassExecute GetSpecOwner,"" End Sub

See also Configuring the project properties for P&ID-PPC-3D interaction (Page 175)

8.10.4 Links for the attributes for nominal diameter and pipe spec


Introduction If the P&ID catalog and the PPC are linked, changes to the nominal diameter and the pipe spec must trigger renewed pipe spec mapping. For this purpose, the attributes of the nominal diameters ("PI030.PI008", "PI030.PI008a") and the pipe spec ("PI030.PI012") must be linked statically via the connector.

Procedure In order to change the type of link, open the properties of the attribute and go to the "Link" tab. Set the "Value" field there to "Static".



Starting pipe spec mapping without static link If the links are not static, the "OnChange" script block is not called. In this cases the PipeSpec mapping must be forced. This can be done as follows:

● Via the context menu of a COMOS object

To do this, implement the "OnMenuCreate" and "OnMenuExecute" scripts at the object.

● Via a button

Implement the "OnClick" script for the button.

See also Scripts for pipe spec mapping (Page 222)

8.10.5 Link for the "Connector" attribute


Static link via "GetLinkedSpecification" If the P&ID object is to adopt the connection type of its PPC implementation following pipe spec mapping, you must link the attributes for the connectors statically:

● Attribute at the P&ID object: "PI030.PIA0#3"

– Link type: "By script function <GetLinkedSpecification()>"

– Script block "GetLinkedSpecification": Apply the implementation of the COMOS DB: "@10 > PID > 0 > 01 > PIA0#3"

● Linked attribute at the PPC object: "GD.VC#3"


See also Inheritance of the nominal diameters and pipe spec (Page 216)

8.10.6 Link for the "Nominal pressure" attribute




Static link via "GetLinkedSpecification" If the nominal pressure of the P&ID pipe is to adopt the permitted nominal pressure of the pipe spec, the "PI030.PIA009" attribute at the P&ID pipe must implement the "GetDisplayValue" script block as follows: Function GetDisplayValue() Set PCSpec = GetSpecOwner.Spec("PI030.PIA012") 'PipeSpec If PCSpec is Nothing Then Exit Function If PCSpec.Value = ""Then Exit Function PCName = PCSpec.Value Set PipeClass = lib.StdValues3D(Project).pcGetPipeClass(PCName) If PipeClass is nothing Then Exit Function Set CDev = PipeClass.Cdevice Set Sp = CDev.Spec("C2.V2.P") 'C2.V2.P: List specification 'P: Calls column P, in in which the second value ("Row") is fetched using GetXValue(1). If not SP is Nothing then GetDisplayValue = SP.GetXValue(1) End Function

See also Workflow (Page 177)

8.10.7 Overview of data flow between P&ID object and PPC implementation


Data flow The following table provides an overview of data flow between the P&ID object and PPC implementation. The data is forwarded via static links:

Pipe spec Nominal diameter

1 Nominal diameter 2 Connector Nominal pressure

Object for pipe spec

"C2.V2.P.GetXValue(1)"

Object for pipe branch

"PI030.PIA012" "PI030.PIA008" "PI030.PIA008a" "PI030.PIA009"

Reference to the COMOS DB 8.11 Properties of standard tables


P&ID object "PI030.PIA012" "PI030.PIA008" "PI030.PIA008a" "PI030.PIA013"

PPC object "GD.VPCL" "GD.VC11" "GD.VC21","GD.VC31"

"GD.VC13"

8.11 Properties of standard tables

8.11.1 Standard table for PPC function codes

Purpose of function codes Function codes are keys which are used to categorize pipe parts when working with pipe specs.

The function codes are grouped in a standard table. The standard table is assigned to an attribute of the pipe parts. Which attribute this is is defined in the project properties:

"Options" > Process engineering" tab, "Link between P&ID and PPC" control group, "Attribute for PPC function code" field.

COMOS DB The standard table for function codes is available in the "@3D > 01 > BC > 01> 03 Function code" node.

Editing the standard table for function codes Some of the function codes are fixed programmed in COMOS.

Furthermore, certain function code ranges are reserved for specific component types.

Example:

● The function code range between 10000 and 10010 is reserved for types of pipe spec.

● The function code range between 11100 and 11199 is reserved for general pipes.

Therefore, you should seek advice from your account manager before editing the standard table for function codes.‎

See also chapter Configuring the standard table for PPC function codes (Page 173).



"Error analysis for 3D objects" plugin 99.1 Purpose

Missing attributes or erronous entries in attributes can lead to the geometry of a pipe part being calculated incorrectly or not at all. This can have the following consequences:

● The pipe part is not exported to PDMS

● The pipe part cannot be displayed in the 3D view or is displayed incorrectly

● Reports are incomplete or empty

The "Error analysis for 3D objects" plugin checks whether the geometry of pipe parts can be calculated.

The plugin offers you the following analysis options:

● Analysis of an individual pipe part

All of the attributes required for geometry calculation are analyzed for a nominal diameter. The analysis returns a list containing detailed information about the attributes.

● Analysis of several pipe parts at once

The attributes required for geometry calculation are analyzed for all nominal diameters at once. This allows you to compare the geometry results for the pipe parts directly.

You can view the results of the calculation in a 3D Editor.

9.2 Calling the plugin

Procedure Select "Plugins > Basic > Error analysis for 3D objects" from the menu bar.

Result ● The plugin is opened in the working area on the "Error analysis for 3D objects" tab.

● The "Detail evaluation" tab is active when the plugin opens.

See also The interface of the plugin (Page 228)

"Error analysis for 3D objects" plugin 9.3 The interface of the plugin


9.3 The interface of the plugin

Structure The "Error analysis for 3D objects" plugin has two tabs:

● "Detail evaluation" tab:

Analyze the attributes of a pipe part required for geometry calculation in relation to a single nominal diameter.

● "Bulk analysis" tab:

Check whether the geometry can be calculated correctly for multiple pipe parts and for all available nominal diameters.

Structure of the "Detail evaluation" tab The "Detail evaluation" tab has the following structure:

● "Base object" field:

– Pointer to the base object of the pipe part whose geometry calculation you are checking

– Even if you drag the base object of a pipe spec element to the field, the corresponding base object from the pipe part catalog is still evaluated.

– You can view a list of all base objects you have dragged to the field. To do this, click the arrow button to the right of the field.

● "Calculate" button:

Starts the calculation of the pipe part properties.



● Tool bar:

In the toolbar, set the values necessary to calculate the geometry.

The toolbar contains the following control elements:

– "Activate nominal diameter filter" button:

The filter is only applied if you have dragged the base object of a pipe spec element to the "Base object" field.

Disabled: In the toolbar, you see the nominal diameter range set at the pipe spec in the field for the nominal diameter.

Active: The base object comes from the base object of the pipe part from which the pipe spec element is derived, from the "Display for nominal diameter range" tab.

– All attributes referenced in the "GD.VSUI" attribute of the pipe part, e.g. the attributes for the pipe spec and the nominal diameter.

– "Specify insertion point" list

Do not use.

– "Fix nominal diameter" option:

Do not use.

● Table at the top:

Contains all attributes from the "3D geometry" tab whose 3D mode is active.

Column name "Attribute name" Self-explanatory. "Description" Self-explanatory. "Value" Self-explanatory.

This field normally includes concrete values or calculation formulae.

"Result" The result of the geometry calculation for the attribute

"Error message" Type of error if the attribute could not be calculated

● Table at the bottom:

Contains the 3D attributes required for which a corresponding attribute could not be found at the pipe part. The values can be drawn from standard tables or are optional and do not have to be created at the object itself.



Structure of the "Bulk analysis" tab The "Bulk analysis" tab has the following structure:

● Field "Start object":

A pointer to one of the following base objects:

– Pipe part from the pipe part catalog

– Structure object from the pipe part catalog

– Pipe spec element

– Pipe spec

If there are no base objects underneath the start object, the start object is analyzed.

If there are more base objects underneath the start object, they are analyzed recursively.

● "Unit location" field:

– Pointer to an engineering object of the "Device" system type, whose creation mode is "Free" and which has the "World" tab

– Optional

– Precondition: "Create 3D" option is activated.

– The 3D objects generated are created underneath the object linked here.

● "Error geometry" field:

– Pointer to a 3D base object

– Optional

– Precondition: The "Create 3D" option is activated and the "Unit location" pointer is set.

– For objects whose geometry could not be calculated or could not be calculated correctly, 3D objects are generated with the base object linked here.



● "Create 3D" option:

– Optional

– Precondition: "Unit location" pointer is set.

– Active: 3D objects are created for all objects, even objects whose geometry was not calculated correctly. The 3D objects can be displayed in the Viper 3D Editor.

● "Invalid only" option:

– Optional

– Precondition: "Create 3D" option is activated.

– Active: 3D objects are only created for the objects whose geometry could not be calculated correctly.

● "Start analysis" button

Starts the analysis. Data is written to the results table even while the analysis is still in progress.

● "Pause/Resume" button:

Interrupts or resumes the analysis.

● "Cancel" button:

Cancels the analysis.

● Results table:

– The table analyzes whether the geometry can be calculated:

Green check mark: Geometry calculated correctly

Red "X": Geometry not calculated correctly

– If the start object is a pipe spec or the base object of a pipe spec element: The geometry for the nominal diameter range specified by the pipe spec is checked.

– If the start object comes from the pipe part catalog: The geometry for the nominal diameter range specified by the pipe part on the "Display for nominal diameter range" tab is checked.

● Area underneath the table:

Displays a progress bar and outputs the status of the analysis.

See also Error messages (Page 234)

"Error analysis for 3D objects" plugin 9.4 Checking the pipe geometry for errors


9.4 Checking the pipe geometry for errors

9.4.1 Workflow

Procedure To check whether the geometry attributes of a pipe part have been calculated correctly for a given nominal diameter, proceed as follows:

1. Open the "Error analysis for 3D objects" plugin. The "Detail evaluation" tab is active.

2. Show the attributes of the pipe part.

3. Set the important values for the geometry calculation via the plugin's toolbar.

4. Start the calculation.

5. Use the results to identify the error sources.

6. For attributes which have not been calculated at all or have been calculated incorrectly:

– Correct the value entered in the "Value" column.

– If required: Correct the important values for the geometry calculation in the plugin's toolbar.

– Check your entries by restarting the calculation.

Repeat these steps until the geometry is calculated correctly.


Note

Changes to the attributes of a pipe part should be made at the base object from the pipe part catalog and not at the base object of the pipe spec element, because COMOS usually references the pipe part catalog.

See also Calling the plugin (Page 227)

Displaying 3D attributes of a pipe part (Page 233)

Calculating the geometry of a pipe part (Page 233)



9.4.2 Displaying 3D attributes of a pipe part

Procedure 1. Select a base object from the pipe part catalog on the "Base objects" tab in the Navigator.

2. Drag&drop the base object to the "Base object" field on the "Detail evaluation" tab.

Result ● The attributes of the pipe part are read in and output in the table underneath the base

object:

– All attributes on the "3D geometry" tab for which the following applies are read in: Properties of the attribute, "Link" tab, "3D" control group, "Mode" list: Value "On"

– The "Attribute name", "Description", and "Value" table columns are read in.

● A toolbar appears above the table. Use the toolbar to set the attribute values necessary to calculate the geometry of the pipe part.

Base object of a PipeSpec element It is advisable to analyze the pipe spec elements if the attributes used to calculate the geometry get their values via the "CatPC" formula. They are then calculated on the basis of the pipe spec.

When you drag a pipe spec element into the "Base object" field, it is the base object from the pipe part catalog from which the pipe spec element is derived that is displayed in the "Base object" field. The base object of the pipe spec element is displayed grayed out underneath:

The results table evaluates the base object from the pipe part catalog. Only the pipe spec is read out of the pipe spec element.

See also The "CatPC(...)" function (Page 162)

The interface of the plugin (Page 228)

Calculating the geometry of a pipe part ()

9.4.3 Calculating the geometry of a pipe part

Procedure 1. In the tab toolbar, set the values necessary to calculate the geometry, e.g. the nominal

diameter in the "DN1" list.

2. Click the "Calculate" button.



Result The following table columns are filled:

● "Result" column:

Contains the result of the geometry calculation. The result may materialize as follows:

– Adoption of the attribute value.

– Result from the formula that stands in the attribute value.

– Value from a catalog with standard values if the attribute is not set.

If the value "<error>" is displayed here, then an error occurred during calculation. The error is further explained in the column "Error message".

● "Error message" column:

Type of error that occurred during the calculation.

See also Error messages ()

The interface of the plugin (Page 228)

Displaying 3D attributes of a pipe part (Page 233)

9.4.4 Error messages The following notes and error messages can appear in the column "Error message":

● "Geometry type is not set. Object cannot be calculated."

Refers to the attribute "GD.VGEO."

● "Parameter is not used in the geometry function."

● "Parameter optional"

Value from the parameter which is only used if available and valid.

● "Invalid value"

The calculation offers an invalid value for geometrics.

● "Parameter error. Connection with this index does not exist: CONNECTION NUMBER."

● "Nominal pressure is not set."

● "Nominal pressure is not set. Use ATTRIBUTENAME of another connection."

For an unset nominal pressure, COMOS uses the nominal pressure of the specified attribute.

● "Attribute CHAPTER.NAME.ATTRIBUTENAME not found."

During the use of CatExt().

● "ATTRIBUTENAME not found."

During the use of S().

"Error analysis for 3D objects" plugin 9.5 Nominal-diameter-dependent check of the geometry


● "Error in expression."

Syntax in the calculation formula is wrong.

● "Invalid catalog name CATALOGNAME"

● "Invalid or empty value in CATALOGNAME for ND1 with index NOMINALWIDTHSINDEX1."

● "Invalid or empty value in CATALOGNAME for ND1 with index NOMINALWIDTHSINDEX1 and ND2 with index NOMINALWIDTHSINDEX2."

● "Column COLUMNAME in SYSTEMFULLNAME_OF_THE_OBJECT not found."

● "Catalog not found: CATALOGNAME -> <PATH_UNTIL_ERROR>."

● "Column COLUMNAME in catalog CATALOGNAME not found."

● "Connection CONNECTIONNUMBER not found."

● "PipeSpec is not set. Object SYSTEMFULLNAME_OF_THE_OBJECT."

● "Parameter error. Attribute not found: ATTRIBUTENAME."

● "Catalog attribute not found."

9.5 Nominal-diameter-dependent check of the geometry

9.5.1 Workflow

Procedure To check for one or more pipe parts the nominal diameters in which the geometry of the objects is calculated correctly, proceed as follows:

1. Open the plugin "Error analysis 3D objects" and change to the "Bulk analysis" tab.

2. Click on the "Base objects" tab in the Navigator and select the base object you wish to analyze.

The following base objects are permitted:

– A pipe part from the pipe part catalog

– A structure object from the pipe part catalog

Example: The structure object underneath which the welded pipes are located

– A pipe spec element

– A pipe spec

3. Drag&drop the base object to the "Start object" field.



4. Optional: To view the geometry following analysis in the Viper 3D Editor, make the following settings:

– In the Navigator, click on the "Units" tab and select the object underneath which the 3D objects are to be created.

Precondition: The object has the "World" tab.

– Drag&drop the object to the "Unit location" field.

– Activate the "Create 3D" option.

5. Optional: Define which base object is used for pipe parts whose geometry is not calculated correctly,

– Precondition: The "Create 3D" option is activated and the "Unit location" pointer is set.

– Click on the "Base object" tab in the Navigator and select the base object to be used as the template.

– Drag&drop the object to the "Error geometry" field.

6. Optional: If you only want 3D objects to be created for pipe parts whose geometry is not calculated correctly, activate the "Invalid only" option.

7. Click the "Start analysis" button.

Result ● If the start object is a pipe spec element or a pipe part from the pipe part catalog, the start

object is analyzed.

● If the start object is a pipe spec or a structure object from the pipe part catalog, the subordinate objects are analyzed recursively. The time taken to complete the analysis depends upon the number of objects.

● If the start object is the base object of a pipe spec element, the geometry for the nominal diameter range specified by the pipe spec is checked.

● If the start object comes from the pipe part catalog, the geometry for the nominal diameter range specified by the pipe part on the "Display for nominal diameter range" tab is checked.

● For each pipe part, a status is determined for each nominal diameter:

– Green check mark: The geometry of the pipe part has been calculated correctly.

– Red cross: The geometry of the pipe part has not been calculated correctly.

9.5.2 Interrupting, resuming, or canceling the analysis Dependent upon how many objects are analyzed, the analysis may take some time.

Interrupting the analysis Click the "Pause" button.



Resuming the analysis Click the "Resume" button to resume the analysis.

Canceling the analysis To terminate the analysis prematurely, click on the "Cancel" button.

9.5.3 Viewing the result of the analysis in the 3D Editor

Requirements A bulk analysis has been carried out, the "Create 3D" option was activated, and the "Unit location" field was set.

Procedure You can view the geometry of the pipe parts in the COMOS Viper 3D Editor.

1. In the Navigator, select the object entered in the plugin in the "Unit location" field on the "Bulk analysis" tab.

2. Select "Extra > Viper 3D Editor > 3D Piping" from the menu.



Result The 3D Editor opens. All 3D objects located underneath the object selected in the Navigator are rolled out in the 3D Editor, with all nominal diameters:

● Pipe parts with one nominal diameter:

X axis: The pipe parts that have been analyzed

Y axis: The nominal diameters for which the geometry has been calculated

For each pipe part: For each nominal diameter

● Pipe parts with two nominal diameters:



9.5.4 Switch to detail evaluation

Initial situation If the geometry of a pipe part has not been calculated in the bulk analysis, you can switch to the detail evaluation and analyze the reason for this.

Procedure 1. Open the node of the required object in the results table on the "Bulk analysis" tab.

2. Click with the left mouse button on the nominal diameter for which you want to start the detail analysis.

3. Select "Check values" from the context menu.

– The plugin switches to the "Detail evaluation" tab.

– The tab adopts all the settings from the object being checked with regard to pipe spec and nominal diameter.

4. Click the "Calculate" button to start the evaluation.

COMOS 4 - Siemens · Legal information Legal information Warning notice system This manual contains...

Documents

Transcript of COMOS 4 - Siemens · Legal information Legal information Warning notice system This manual contains...