Naming conventions used in AVEVA software

The following naming conventions are used in the AVEVA software :

• Tag name: The name of an object. For example, Reactor_002.

• Attribute name: The name of a variable exposed by an object. For example, ReactLevel.

• Attribute reference: The combination of a tag name and an attribute name. The format is:

  <TagName>.<AttributeName>

  For example, Reactor_002.ReactLevel

• Contained name: The name of an object with considerations to its place within the overall object hierarchy. By default, the contained name for an object is the same as its tag name. However, if you use the same object within other objects, you can change the contained name at each instance in the object hierarchy to reflect the unique context in which the object is used. For example, you might decide that the contained name for the object called "Reactor_002" should be "Reactor".

  In the Model and Deployment view of the System Platform IDE, the contained name is shown in brackets to the right of the object's tag name in the following format:

  <TagName> [<ContainedName>]

  For example:

  Reactor_002 [Reactor]

• Hierarchical name: The contained name for an object, preceded by the tag names of the containing objects in the hierarchy, in the following format:

  <ContainerNameN>.<ContainerName2>.<ContainerName1>.<ContainedName>

  For example, if an object whose contained name is Reactor is contained within an object whose tag name is R32, then the hierarchical name of the object is:

  R32.Reactor.

  In the Derivation view of the System Platform IDE, the hierarchical name is shown within brackets to the right of the object's tag name. For example:

  Reactor_002 [R32.Reactor]

You can then use the AVEVA Historian Client software to browse the replicated Model view hierarchy for groups and tags. For more information on replicating the object hierarchy, see the AVEVA Historian documentation.