Naming conventions

The following naming conventions are applied:

• PI AF element and attribute names are taken from the corresponding OPC UA object's property DisplayName.

• PI points are named according to the OPC UA variable's property NodeId.

The naming convention that PI Connector for OPC UA applies to PI points complies with the following pattern:

RegisteredConnectorName.DataSourceName.NodeIdNamespaceIndex.NodeIdIdentifier

The delimiter is dot '.'

For example, an OPC UA dynamic variable with a NodeId: ns=5;s=Counter1 created by a connector which was registered as OPC UA1 produces this PI point name:

OPC UA1.DataSource1.5.Counter1

You have the option to modify the described naming convention for PI point names in two places:

• Applying a formula that can be entered as the SourceId Pattern found under the Transformational Rules category of the Advanced Configuration. More additional information, see Transformational Rules.

• Explicitly re-name the default PI point names on the Tag Naming Worksheet configuration page of the PI Data Collection Manager.

Moreover, PI points are created with their Eng Units attribute set to the value of an OPC UA property called EngineeringUnits, their Zero and Span attributes adjusted to the OPC UA property EURange, and their Descriptor set to the value of the OPC UA property named Description.

Note: The referenced OPC UA properties are optional; that means that if they are not specified, PI points are created with the corresponding attributes having the default values.

Caution: OPC UA servers support more characters than do PI point, PI AF element, and attribute names. In order to mitigate this discrepancy, PI Connector for OPC UA replaces the unsupported characters with an underscore. The following characters are replaced: * ' ? ; { } [ ] | \ ` "

The following screenshot illustrates the definition and property values referenced to an Analog Item named FloatAnalogItem.

Property values example