Enable data quality
- Last UpdatedApr 24, 2025
- 2 minute read
RealTime record fields can be added as items to the Open Platform Communications (OPC) client program connected to the OPC server. You can configure the data quality to be returned as the quality of the connection or the quality of the data value.
For any analog, status, rate, or tank telemetered field added as an item to the OPC client, you can configure the OPC server to return the data quality as:
-
The quality of the connection between the AVEVA Enterprise SCADA OPC server and the PubSub Service for that point, or
-
The quality of the data value itself, as determined from the record's flag structure.
Once the OPC client receives the data and quality, it must display and/or process the quality.
Notes: If the connection between the OPC server and the PubSub Service for a given point
failed, the data quality for that point is NOT-CONNECTED, regardless of the data quality
of the point. For example, if you delete or remove a point added as an item to an
OPC client, the system marks the quality as NOT-CONNECTED for that point.
Because the OPC server provides its own data quality, ensure that you do not use the
Quality Bit field on the Input tab of the Row Edit dialog boxes for the RealTime database (RTDB)
records corresponding to the analog or rate points. Otherwise, the values and data
quality for those analog or rate points may not be as expected.
If enabled, the system provides the actual data quality of the following telemetered records:
|
Table |
Point |
|---|---|
|
Analog |
curval |
|
Status |
cursta |
|
cursta@raw |
|
|
Rate |
curate |
|
acccur |
|
|
Tank |
field.volume |
|
field.num_inc |
|
|
currentGO.volume |
|
|
currentGO.num_inc |
|
|
currentGS.volume |
|
|
currentGS.num_inc |
|
|
flevel |
|
|
GOflow_rate |
|
|
GSflow_rate |
|
|
Multistate |
inputCurRaw |