Though the quality tag on Kepwere is BAD, the remoteThing display is Good

[Abhi10217691]

The quality tag in Kepwere appears to be showing a Bad tag, while the thingworx shows a good tag. Why is this the case, and how can this be fixed?

[geva]

It is possible that the change of data quality is not seen as a data change event and is hence not updating the ThingModel.  My recollection of the code does not compare quality between updates.  There is however another change to add quality data change configuration as well as storage to value streams in an upcoming release (check under property Advanced settings when it is out).  You can validate this by toggling the quality ONLY and see if you see your value in ThingWorx change.  If you DO NOT, then you can change the default DataChange type from VALUE to ALWAYS -- meaning that it will update the ThingModel at each new value (1 GOOD versus 1 BAD is not a change in VALUE, but a change in QUALITY).

[geva]

Support for logging quality as well as time and value has been added in ThingWorx Foundation version 9.5.  There are now a number of updates to APIs (Add, Query, etc.) in order to make this work, and performance testing has been done on the various persistence providers.

ThingWorx 9.5.0 What's New

Note that as there is more data being stored, queried, processed; this inevitably has an impact on performance which needs to be factored into software, application, and infrastructure architecture decisions and planning.  An example of what I mean, if you presently have a solution using large amounts of logged value stream data and wish to start leveraging stored quality attribute, your infrastructure will take more load and this could require scaling up resources, or adapting the application design to offset it.  As always such architecture decisions need to be weighed and are implementation choices not software product issues.