Naming conventions for asset types and associated items
- Last UpdatedFeb 06, 2025
- 1 minute read
Instantiated items created by AVEVA Insight adhere to a standard set of rules for naming.
|
Rule |
Details |
|
Instantiated items are named in the format AssetName-ItemName. |
The AssetName only takes the relevant node from a full asset hierarchy. For example, if an instantiated item, ChartA, is generated for Chicago/Plant, then the name of the item will be Plant-ChartA. |
|
Specific entity types have unique character limitations. |
|
|
Instantiated items generated for multiple assets sharing the same name will be appended with a numerical suffix in the format AssetName-ItemName-NumberSuffix |
If a given solution has two Plant assets, Chicago/Plant and Houston/Plant, then the generated instantiated names will be Plant-ChartA-001 and Plant-ChartA-002. Note: If an asset is associated with an asset type, you will not be able to create entities with a name ending in a hyphen with a numerical suffix. |
|
Assets associated with an asset type cannot have special characters in their name. |
The name of an asset containing a source Guided Model cannot contain any of the following: [ ' \ ] The name of an asset containing a source alert cannot contain any of the following: \ ,' |