Ensure data is identical between collective members
As a PI Administrator, I need to trust that the data is identical between my collective members. Currently, there is no way for me to be sure it is the same unless I do a side by side comparison. Data can be missing, or slightly off, and I have no easy way to understand this right now.
The architectural design of a PI Collective is such that there is no data synchronization between the collective members. We have established procedures to sync the data using PI to PI Interface. Is this a viable solution?
How does one know if one collective member has stopped receiving data from PI to PI? I guess the question is how do we ensure to our users that data is the same no matter what collective member they connect to? I understand your design, but seems like there needs to be a way then for PI to PI to verify data is arriving on all nodes, if not, back-fill or fix data to the single nodes that is impacted.
Since this was posted, we now have the PI connector. We would like to do more testing with that, but a bug took it back away from us earlier. Seems that the bug is fixed and well do some testing now.
PI to PI works to send data to another collective member when buffering is not or cannot be used. However the big hurdle for us at least with some of our manual entry data is that there is no way to delete from a secondary member without adding custom code. It would be nice if PI to PI or something else could handle the deletion of data.
100 % agree. I think there are other posting in regards to this.
[Deleted User] commented
PI Data Archive Collective - Real Time visualization of the updated values:
with a PI Collective, if an user is connected to the Primary server and the interface is not able to send data to this node but is able to send the data to another one, the user is not visualizing the realtime value from the scada: no synchronization of the data between the members of a PI Collective for the realtime values.