Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Adapter for OPC UA

Metadata

  • Last UpdatedJun 26, 2025
  • 2 minute read

Metadata for data streams

Certain metadata are sent with each stream created. Metadata is only sent for streams created by the ingress components. The endpoints that persist sent metadata are CONNECT data services and Edge Data Store.

The following metadata, created by any AVEVA adapter, is available for streams:

  • datasource: This specifies the data source and corresponds to componentId in the adapter configuration. The componentID for this adapter is set by the customer.

  • AdapterType: This specifies the type of adapter and corresponds to the componentType in the adapter configuration. The componentType for this adapter is OPCUA.

To add and configure a new adapter component, see Configure system components.

Note: All supported endpoints (Edge Data Store, CONNECT data services and PI Server) use datasource. However, any other metadata is only supported on Edge Data Store and CONNECT data services. If you use PI Server as the data endpoint, the Point Source field on a PI point reflects the metadata value.

The following metadata is specific to this adapter:

  • BrowseName: The browse name as provided by the OPC UA server.

  • SourceId: Specifies the information used to uniquely identify the stream on the source system.

    The metadata level in the System/General facet controls the amount of metadata written to an adapter stream and defines the amount of metadata sent to the OMF endpoints. It can be set in Manage adapter-wide settings to one of the following values:

    Metadata Level

    Description

    Metadata for Data items

    Metadata for Events

    None

    No metadata

    None

    None

    Low

    Includes only framework related information

    AdapterType and datasource

    AdapterType and datasource

    Medium

    Includes adapter specific information that is considered not sensitive

    AdapterType, datasource, BrowseName, and LocalName

    AdapterType, datasource, and SourceId

    High

    All metadata (including potentially sensitive information and control addresses)

    AdapterType, datasource, BrowseName, LocalName, and SourceId

    AdapterType, datasource, BrowseName, and SourceId

Each stream created for a given OPC UA item has a unique identifier (stream ID). If you specify a custom stream ID for the OPC UA item in data selection configuration, the adapter uses that stream ID to create the stream. If the stream ID is not specified, the adapter the OPC UA item node ID to construct the stream ID:

<AdapterComponentID>.<NamespaceIndex>.<Identifier>

<NamespaceIndex> refers to the number specified in the ns keyword in the NodeId parameter of the data selection configuration item. For more information, see Configure data source.

Note: The naming convention is affected by StreamIdPrefix, DefaultStreamIdPattern and DefaultEventStreamIdPattern settings in the data source configuration.

Metadata for health and diagnostics streams

If you configure a health endpoint, the adapter sends both health and diagnostics streams by default with the following metadata:

  • datasource

  • AdapterType

For more information around Health and Diagnostics, including the list of streams, see Health and diagnostics.

To manage your diagnostics and metadata settings, see Manage adapter-wide settings.

In This Topic
TitleResults for “How to create a CRG?”Also Available in