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.
We maintain a strict naming convention of PLC Tag → Plant SCADA Variable → PI Tag → Downstream Systems so users can easily find signals across all systems.
The problem is that when a source Plant SCADA variable is renamed, there is currently no easy way to identify which downstream systems are consuming the associated PI tag. This makes impact assessments and change management extremely difficult.
A built-in tag usage audit showing which clients access a tag, how often it is accessed, and from where would allow us to identify impacted systems, notify owners, and coordinate changes safely.
Today, the only way to obtain this information is through workarounds such as piartool analysis or network packet inspection. In large environments this is time-consuming and unreliable.
Since PI already tracks client connections and activity, exposing tag-level consumption statistics would provide huge value and improve change management.
It's 2026, having a database without query level audit feature is not great.
We have customers with hundreds of thousands of tags. Being able to find tags that are using resources, particularly those that are calculation outputs, but are never used, would help greatly in maintaining optimum system performance.