The software provides two options for naming the piping objects that you create: DefaultNameRule or User Defined. This section illustrates the output from using the naming conventions.
The following illustration shows a piping hierarchy.
Use this option to let the software name the piping object. In general, the naming rules follow the patterns as for UserDefined names.
Use this option to define a custom name. You do not need to select this option explicitly. When you type text in the Name box, the UserDefined value is automatically set in the NameRule field. The following illustrations show user-defined names for a piping system.
This identifier does not necessarily need to be attached to its subordinates.
The pipeline could be a unit number + nominal pipe diameter. For example, 380105-MC5.
The pipe run contains the pipeline name plus additional information as shown here.
One example could be as follows:
The sequence number is generated using the name Counter and is associated with pipe run.
Piping parts need only an engineering tag, usually from the catalog, and a sequence number.
For example, the following naming rule would create the identifiers for the tenth (0010) air-operated control valve (AOP) placed into a system.
The naming rules are listed in the GenericNameRules.xls spreadsheet located in the appropriate folder: [Product Folder]\CatalogData\BulkLoad\DataFiles. For more information on creating naming rules, see Naming Rules Reference Data. Users can add naming rules to a class by specifying the class, the name rule name, and the ProgID of the name rule code in the GenericNamingrules.xls file via bulkload.