Historical Data Access

From UaCapabilities
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search

Introduction

Historical Data Access addresses the handling of historical time series data. The AddressSpace of HDA Servers contains Historical Nodes representing the history of Variables and Properties. HDA Clients deal with historical data by accessing these Nodes with the HistoryRead and HistoryUpdate Services. There are several types of Historian servers. Some key types supported by OPC UA are:

  • Simple trend data servers, providing little other than simple raw data storage. (Data would typically be the types of data available from a Data Access server.
  • Complex data compression and analysis servers, providing data compression as well as raw data storage. They are capable of providing summary data or data analysis functions, such as average values, minimums and maximums etc. They can support data updates and history of the updates. They can support storage of annotations along with the actual historical data storage.

Note – Historical Access is specified in OPC UA Part 11, Aggregates are specified in OPC UA Part 13.

Historical Data Access Capabilities

Base Access

URN:          https://opcfoundation.org/wiki/index.php/Historical_Data_Access#Base_Access

Discovery ID: HD


Description
The AddressSpace includes Variables that represent historized Variable values. Read access is provided via ReadHistory.

Usage Considerations
Simple trending packages that just desire values over a given time frame or they may produce complex reports that require data in multiple formats.


Conformance Testing

Client Server

Aggregation

URN:          https://opcfoundation.org/wiki/index.php/Historical_Data_Access#Aggregation

Discovery ID: HD


Description
Aggregates are used to derive values from raw data over a defined time range. There are several defined aggregates as well as the ability for vendors to provide custom aggregates.

Usage Considerations

  • Interpolated data is required.
  • Raw historical data needs to be normalized before it can be used.
  • Summarized trending and reporting.

Conformance Testing

Client Server

Read from history by specifying one of the supported aggregates

Support aggregate processing

Insert-Update

URN:          https://opcfoundation.org/wiki/index.php/Historical_Data_Access#Insert-Update

Discovery ID: HD


Description
Ability to modify existing historized Variable values or add historized Variable values that are not in time series order.

Usage Considerations

  • Storage of data received late.
  • Correction of incorrect value.

Conformance Testing

Client Server

Support the following profiles:

also recommended:

Support the following profiles:

Delete

URN:          https://opcfoundation.org/wiki/index.php/Historical_Data_Access#Delete

Discovery ID: HD


Description
Ability to permanently remove historized Variable values.

Usage Considerations

  • Removal of out of service data.
  • Removal of redundant data.

Conformance Testing

Client Server

Use HistoryUpdate Service to delete historical data values

Supports deleting historical values

Annotations

URN:          https://opcfoundation.org/wiki/index.php/Historical_Data_Access#Annotations

Discovery ID: HD


Description
Annotations are additional meta data (notes) that can be inserted into an archive at a specific time.

Usage Considerations
Record, alongside the data, abnormal conditions or readings such as when maintenance or recalibration was done.


Conformance Testing

Client Server

Clients is able to retrieve and insert annotations

Support storage and retrieval of annotations