Batch Framework Interfaces - Officially support fanning tag data to a PI Collective
Unlike other PI interfaces, the Batch Framework Interfaces do not use buffering. If the interface loses connection to the PI Data Archive, the interface continues collecting data and stores it in its local cache. The PI Batch Database is primary-only so it did not make sense to fan data to other PI Collective members. However, this is no longer a consideration if Event Frames are being written. There should be an officially tested and supported way to fan tag data to a PI Collective.
This is a no brainer, definitely should be supported.
This would be a huge improvement. We are forced to use Tag Templates with our Werum PAS-X Batch Interface since the Business Integrator does not publish data until the event is closed and our records can remain open for 2+ weeks. We plan on publishing the same static attribute data generated to tags but not supporting buffering (essentially not support a collective) is a huge issue at our site.
It would be a great improvement for us too.
Brian Goldinger commented
Makes sense - I had a mfg site decline to implement a collective at first because they might be missing batch data if looking at the secondary server in the collective.
Joshua Biagio commented
We could definitely use this... that way my users won't have to worry about "missing" data when they are looking at the other collective members!!
Rene Dietzel commented
Writing tag data to secondary PI server via Batch Interface would be very helpful for us too!