Metadata

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 when sending data to CONNECT data services and Edge Data Store. The componentID for this adapter is set by the customer. When sending data to the PI Server, the Point Source uses the datasource value

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

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

The following metadata is specific to this adapter:

• Device: The Device Id of the BACnet device

• SourceId: SourceId is constructed using the following pattern: {DeviceId}.{ObjectType}{ObjectId}.{PropertyIdentifier}

• LocalName: The BACnet ObjectName as provided by the BACnet object

  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. The metadata levels are defined as follows:

  Metadata Level	Description	Metadata
  None	No metadata
  Low	Includes only framework related information	AdapterType and datasource
  Medium	Includes adapter specific information that is considered not sensitive	AdapterType, datasource, and Schedule
  High	All metadata (including potentially sensitive information and control addresses)	AdapterType, datasource, Schedule, Device, LocalName and SourceId

When the adapter is initially installed, the metadata level defaults to Medium. You can reconfigure the metadata level through the adapter-wide settings.

Note: If a scheduleId is not specified when configuring data selection items (see Configure data selection), metadata will not be sent for the associated streams until the scheduleId is specified and the adapter process is restarted.

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.