Optimize data traffic with COV modification

Introduction

Climatix IC writes a value to the cloud, if the configured COV (Change of Value) for a value is exceeded. The new value is then logged and rechecked during the next controller cycle as to whether the COV is exceeded, etc.

System data points are not monitored for COV.

Conclusion

Fast changing values (typically analog values) can result in increased data traffic/data volume and may result in higher mobile data network costs.

NOTICE

The following principle applies to modifying the COV to optimize data traffic:

1. Your controller is highly accurate, regardless of the settings for Climatix IC.
2. In other words, COV optimization deals with changes in the areas of operating and monitoring. You can lessen the accuracy of monitoring somewhat to save on data volume.

Where can you intervene?

In general, the SCOPE tool calculates a reasonable COV for individual values. The privilege is based on the engineering limits set by the developer in the SAPRO tool (see SAPRO help). The formulas are repeated here to simplify the explanation:

• For EngUnitHigh < 90, the COV= 5% per the formula ((engUnitHigh+10)/10)*0.05
• For EngUnitHigh < 1000), the COV= 25% per the formula ((engUnitHigh+50)/50)*0.25
• For EngUnitHigh >= 1000), COV= 15% as per the formula ((engUnitHigh+100)/100)*0.15

You conduct the COV analysis with the SCOPE function "COV measurement": Right-click multiple selections of watch items.

You can change the COV of a data point if you identify one that supplies data intensive values due to "too accurate" monitoring.

You overwrite the COV per item.

Procedure