TimeSeries data quality attributes

When you invoke the collect module to record and store point values in the TimeSeries Historical database, there are up to 64 data quality attributes that can be collected and stored with the value of the point. These data quality attributes represent the meta state of the point at the time of collection.

Attributes are stored as a 64-bit integer mask that represents all the data qualities present at the time of collection.

The following image is an example of a bitmask:

Where:

• Position 1 is reserved to indicate whether the collected value has been manually edited. When a collected value is manually edited from HMI, the corresponding data quality flag mask is reset so that only position 1 is active.

• Position 2 is reserved to indicate that the collected value was initially missed and has been calculated by the system. This condition may happen when the complete system has been stopped for more than one hour.

• Position 12 is reserved to indicate that there is no extended data quality information available for this record. This position will be active when the data was collected using AVEVA Enterprise SCADA versions prior to 2023. In this instance, the corresponding data quality flag mask is reset so that only position 12 is active.

• Position 19 is reserved for trending use. The Business Logic Tier (BLT) objects used for trending (trend, interpTrend, and RTTRend) will consider this attribute as being active when there is no extended data quality information available (position 12 is active) and traditional data quality indicates that the value was manually edited or overridden ('M').

  Note: The positions of the bitmask are configured in the DQFlagConfiguration table of the RealTime database (RTDB). For more information, refer to volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.