Best practices for editing the Collectable Data Quality Attributes table

During initial system configuration or upgrade, you can configure the Collectable Data Quality Attributes table.

After the initial configuration, however, modifying the attribute and the position configured for the data quality is strongly discouraged. Any additional modification after the initial configuration will invalidate previously collected data.

If you want to modify any field other than Name or Description in the collectable DQ configuration row, you must delete the desired record and then create a new record with the updated values.

For example, consider the following scenario: In a system, bit X is used to store the High-High data quality attribute. Later, bit X is changed to store instrument failure status. When the older data is retrieved from the TimeSeries database, the value of the data quality attribute at bit X will indicate as an instrument fail rather than as a High-High alarm.

If the same data quality attribute is common to a number of tables, it is recommended that you configure similar attributes under the same position.

For example, an instrument fail data quality attribute is represented differently among tables, such as analog, rate, multistate, and tank. The schema definition among these tables is also different. As such, the default configuration includes individual records to define the instrument failure for each table but sets the position to the same value in all of them.

Important: AVEVA reserves the right to use the first 32 attributes. This reservation of attributes means that the configuration of these attributes should not be altered in any way. Positions 33–64 are available for definition of custom data quality attributes.

For more information, refer to Work with the Data Quality Attribute Selector.