Rules for automatic naming and coloring

This topic describes the rules for HVAC automatic naming and automatic coloring features.

Rules for automatic naming of SPCOs

If auto naming is enabled and there is a valid naming rule for SPCOs, any unnamed SPCO is renamed when data is written to the specification.

The name of the Specification Component SPCO is limited to 50 characters. If the auto generated name is more than 50 characters long, the application tries to rename the SPCO using the specification name and piping component SCOM name. If this name also is too long, the SPCO remains unnamed when the data is written to the specification. This means that the Name column on the specification form will contain the database reference number that belongs to the SPCO.

A ‘/’ suffix is added to the Specification Name.

Any ‘x’ (lower case) and ‘–‘ characters are removed from the SCOM Name.

Naming example:

Note:
The SPCOs in the AVEVA supplied specifications have been manually named and are therefore not compliant with the automatic naming convention mentioned here.

If an action is performed that results in the SPCO being moved to the LIMBOSPEC, any subsequent writing of data to the specification can result in an unnamed SPCO. This occurs if a SPCO with the same name already exists in the LIMBOSPEC.

For more information about how to rename specifications and specification components, refer to 4.3 HVAC Specification form.

Rules for automatic coloring of components

When rules for automatic coloring of new components are set up, the applied coloring rules are prioritized in the order in which the rules appear in the des-col.pmldat file.

Coloring rules for lower level element types are applied before higher level element types. For example, rules for BRAN type elements are applied before HVAC type elements.