To provide some background, every node in the OPC UA Server is uniquely identified by a NodeId. The OPC UA Connector uses the XML notation.

ns=<namespaceIndex>;<identifiertype>=<identifier>

where

<namespace index>

The namespace index formatted as a base 10 number. If the index is 0, then the entire “ns=0;” clause is omitted.

<identifier type>

A flag that specifies the identifier type. The flag has the following values:

Flag

Identifier Type

i

NUMERIC (UInteger)

s

STRING (String)

g

GUID (Guid)

b

OPAQUE (ByteString)

<identifier>

The identifier encoded as string. The identifier is formatted using the XML data type mapping for the identifier type. Note that the identifier may contain any non-null UTF8 character including whitespace.

The identifier part of a NodeId uniquely identifies a node within a namespace, but it is possible that the same identifier is used in different namespaces for different nodes. Hence only the namespace plus the identifier forms a fully qualified identifier.

That information (namespace index and identifier) are used to generate the PI Point Name.

You could simply use native excel function or 'Find and Replace' to list the identifier + namespace index. If you find it more useful to store it in the instrumenttag, feel free to change the pointclass to 'classic' and manually store the information in there (copy and paste the tagname to instrumenttag, then remove the <PIPointPrefix>.<DataSourceName> part).

OPC UA works with NodeID's and would suggest you to export the definitions from OPC UA connector Admin to check the tag configuration related to PI Point. Tags created by OPC UA does not contain any instrument tag.

Yes I can do that. I can also work through the CSV files (Data Access Filter File) imported during the configuration of the datasource in the OPC UA Connector, but it would be nice if I could make a list of the InstrumentTags using PI builder, like you can for a PI interface.

To provide some background, every node in the OPC UA Server is uniquely identified by a NodeId. The OPC UA Connector uses the XML notation.

ns=<namespaceIndex>;<identifiertype>=<identifier>

where

<namespace index>

The namespace index formatted as a base 10 number. If the index is 0, then the entire “ns=0;” clause is omitted.

<identifier type>

A flag that specifies the identifier type. The flag has the following values:

Flag

Identifier Type

i

NUMERIC (UInteger)

s

STRING (String)

g

GUID (Guid)

b

OPAQUE (ByteString)

<identifier>

The identifier encoded as string. The identifier is formatted using the XML data type mapping for the identifier type. Note that the identifier may contain any non-null UTF8 character including whitespace.

The identifier part of a NodeId uniquely identifies a node within a namespace, but it is possible that the same identifier is used in different namespaces for different nodes. Hence only the namespace plus the identifier forms a fully qualified identifier.

That information (namespace index and identifier) are used to generate the PI Point Name.

You could simply use native excel function or 'Find and Replace' to list the identifier + namespace index. If you find it more useful to store it in the instrumenttag, feel free to change the pointclass to 'classic' and manually store the information in there (copy and paste the tagname to instrumenttag, then remove the <PIPointPrefix>.<DataSourceName> part).

I understand this, we a csv file, as Data Access Filter file. Which also controls/limits the tag creation. So we have the NodeID information on the connector and in the project folders of past projects. We would just like to have this information also in the PI Point where it can be fould for interface tags.

I will look into changing the pointclass to 'classic and filling the instrumenttag attribute, sounds like a good option.

Yes I have that information on the Connector node. But the Node Identifier is not available in PI builder, so it's more work me to answer simple questions about if certain PLC Tags are available in PI or not. There is no reference in the PI Point anymore.