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.
It would be really nice if AVEVA would come out with an OPC UA Interface. While there are advantages to using Data Connectors in some situations, Interfaces are a time tested and simple solution to collect and send data to the DA. I appreciate the simple communication path of interface directly to DA over one TCP port. Data Connectors require multiple pieces of software, inbound and outbound ports, etc that make them not the ideal choice in some scenarios. I've also had reliability issues with the OPC UA connector in several cases. With the lack of a PI OPC UA Interface we typically resort to using a middleware such as Kepware to interface to the OPC UA server, and then use the PI OPC DA interface to get the data into PI from Kepware. This method works great and is a simple setup but adds additional software and expenses. A PI OPC UA Interface would solve a lot of problems and provide a simple solution for OPC UA communications since it is becoming more and more the standard.
AVEVA is there any updates about this topic??