How do concurrent operations correctly modify property values？

[AX_9054610]

Using Thingworx to connect to kepserver, I want to monitor the alarm status of a device. I use properties to store the alarm status, create event subscriptions for multiple tag, and modify the status properties through the subscription, but the properties results are only sometimes incorrect, I think the multiple tag are caused by concurrent alarms,  any other solutions or suggestions?

[PaiChung]

Usually Kepware will send values as they change, these value changes then can trigger your alarm evaluation.

So as there is a 'datachange' you would look at all required property values and determine if there is an alarm or not.

Because it is on data change, even if one value comes in first and another comes in later, then the later data change 

should still determine there is an alarm situation, as long as you aren't resetting the earlier value at the same time.

Not sure if that helps, since I don't know you full situation.