Auto Naming Settings
- Last UpdatedAug 21, 2025
- 2 minute read
Specification Components (SPCO) are automatically named based on the catalog or template reference name. Each specification component must be assigned a unique name in the database.
Catalog and specification items in ACP follow a strict naming convention which allows for easy management of specification items. AVEVA recommends that a similar convention is followed for user specifications, this makes identification of components easier, and ensures unique names.
For example, a Catalog Joint from ACP is named:
JOIN: /J1S1_WEL_ANGL_ANGL_A_001
The name is derived using various identifiers:
J1 - Specification Type is Beam to Beam Joints.
S1 - Sub-Type is Equal Size Beams.
WEL - The Joint Specific Type is Welded.
ANGL_ANGL - The Owning Section (Generic Type - GTYPE) and Attached Section GTYPE are both ANGL.
A - The letter indicates there are multiple categories which have the same criteria as above. This joint is type A.
001 - This is the first Joint in this category.
The corresponding Spec Component for this joint is:
SPCO: /J1S1-WEL-ANGL-ANGL-A-001
This is the same name as the catalog element, except all underscores are replaced with hyphens. This convention is followed for all structural specification components in ACP.
Use the Configure Auto Naming window to define the auto naming rules.

By default, the Configure Auto Naming window displays the Spec Components tab.
Note:
The specification component name must not exceed 50 characters. A specification component
name with more than 50 characters causes the specification component to fail the validation
check.
|
Naming Convention |
A name for each specification component name is generated based on a given category name. |
|
Replace Underscores with Hyphens |
Underscores in the category name are replaced by hyphens in the specification component name. |
|
Remove Underscores |
Underscores in the category name are removed in the specification component name. |
|
Prefix |
A prefix can be specified which is added to the start of each specification component name. |
|
No Prefix |
A prefix is not added to the start of each specification component name. |
|
Spec Name |
Adds the specification name to the start of each specification component name. The specification name is denoted with a * until the specification is written, to allow for modification of the name. |
|
Custom Prefix |
Adds a specified custom text prefix to the start of each component name. |
|
Suffix |
A suffix can be specified which is appended to each specification component name. |
|
No Suffix |
A suffix is not appended to each specification component name. |
|
Incremented Index |
A four-digit number is appended to each specification component name. The number is incremented by one each time a component is named. If components with existing numbers are deleted, the numbers can be re-used. |
|
Custom Suffix |
Specify a custom text suffix to append to each component name. |
|
Example Name |
Displays an example name for the SPCO using the current settings. |