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.
Hello,
It's the same problem with the OPC UA adapter.
And we have the same problem with 3rd party OPC server, for the attribute Eng Unit and zero/SPAN
Can you please provide an update, this request was submitted 2 years ago, also as per below will this also be implemented in the Adapter.
Hi,
The item is now marked "In development". Can someone from AVEVA please provide an expected completion date?
Thanks,
The same idea needs to be implemented in the adapter, or at the time of migrating all the connector users will be back to square one.
https://pisystem.feedback.aveva.com/ideas/PIADAPTERS-I-36
Please fix this. You can't expect SCADA descriptions to always be useful for the end users. I understand the power of the OPC UA server being able to hold all this meta data. But PI being a separate client that extracts the data should have the ability to choose whether or not it wants any of that information.