Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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
Product PI Connectors
Created by sahilp
Created on Aug 20, 2022

Make data source redundancy config more flexible

Some SCADA vendors are still only natively implementing OPC Classic so if one wants to use OPC UA, then a wrapper is needed. If that SCADA is configured in a redundant pair, it is not always true that the wrapper is aware of that or not aware of his corresponding wrapper running on the redundant server. In such a case the Redundancy Support tag is 0-None and the Service Level tag (if present) has unknown behaviour. Right now the only way to manage that is by configuring two data sources and archive all tags twice (once each data source) and find a way to hide this complexity from the end-user (not to mention storage and licensing inefficiencies). It would be nice if the Connector could be made to monitor an alternate tag to determine data source health and switch to a second data source if needed. Probably some sort of heart beat tag would be used in a purely cold standby way (since it is not native to OPC UA we may want to wait a period of time to ensure that our heart is not beating).
  • Attach files