Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No status
Categories Data Archive
Created by ErikJansson
Created on Aug 20, 2022

Make failback function optional

In the DA collective there is a function called "Failback". The function is described as: << When the collective member which the client application was connected to becomes unavailable, the client connection starts monitoring when the member becomes available again. When it happens, it should switch back to that member. This is done by the client application (it is not anyhow forced by the server) and it is done to: Honor connection priorities Restore connection distribution (if member priorities are equal). >> The problem with this is that if primary has been down for a while the buffer needs to fill the gap. The client can not access real time data until the buffer is backfilled. I would like the failback function to be optional. In that way the clients can have real time data continiously.
  • Attach files