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.
Currently, there is no native mechanism to track who created, modified, or deleted a display, when those changes occurred, or what was changed. This creates several real-world challenges:
Unauthorized or accidental modifications to production displays can go undetected until an operator notices something wrong during a shift — by which time the root cause may be difficult to trace.
During incident investigations or process deviation reviews, there is no audit trail to determine whether a display change may have contributed to a misread or missed alarm.
In regulated environments (e.g., refinery operations, environmental reporting), the inability to demonstrate configuration control over critical visualization assets is a compliance and audit risk.
Administrators lack the ability to manage display sprawl — identifying stale, orphaned, or unauthorized displays without manually reviewing content.
2.Ideally, PI Vision would maintain a native audit log accessible to administrators that captures the following at a minimum:
Display creation — who created it, timestamp, and initial display name/path
Display edits — who made the change, timestamp, and ideally a summary of what was modified (symbol added/removed, data reference changed, display renamed, permissions altered, etc.)
Display deletion — who deleted it and when
Permission changes — changes to display access rights or ownership
Access to this log should be role-based (PI Vision Administrator only) and available through either the PI Vision Admin portal or exportable via a report/API query. Integration with existing AVEVA infrastructure such as PI System Explorer audit trails or Windows Event Logs would be a significant added value. A simple query/filter interface (by user, date range, display name, or action type) would make the log actionable rather than just informational.
3. PI Vision Administrators — primary beneficiaries who need to maintain governance and accountability over display configurations across potentially dozens of sites and hundreds of displays.
Operations Supervisors and Process Engineers — who need confidence that the displays operators rely on are accurate and have not been inadvertently changed.
IT Security and Compliance Teams — who require evidence of configuration control over operational technology systems as part of internal audits or regulatory reviews.
Incident Response Teams — who need to correlate display changes with operational events during root cause analysis.
This enhancement would meaningfully close a governance gap that exists in most PI Vision deployments today and aligns well with the broader operational discipline expected in critical infrastructure environments.
Version control - what changed, who did it, when did it happen
Possibly like a document management system - i.e. has a version number and it is possible to retrieve an older version and conduct a compare (an automated compare would be awesome), the ability to roll-back easily to another version would also be great.
System admins would benefit because they would be able to see what changes were made, and when, and find out the why (enabled by knowing the who), this would help with troubleshooting issues with PI Vision displays. The owner of the display would also be able to see what changes they had made and possibly revert to an older version if they'd made an error.
Would be a very helpful feature when ask to provide some "forensic" details.
This would be very beneficial enhancement that is much needed.
Please make this a priority. Thank you.
I believe this could save time in trying to find who made changes and find out what was changed. Auditing is an essential part of any application.
In Life Science implementation, auditing is essential: who and when the change was applied: creation, change and deletion. The Audit Trail should be easy to use.
Since only few displays are for official use (GMP use), it would be nice to enable/disable the audit for each display and not for the entire PI Vision. This can reduce the number of audits and make the retrieval easier.
Absoulutely mandatory nowadays, one must be able to track changes (e.g. in case of Audits one has to be able, to clearly follow up, what was changed and who has changed anything to a display). This should have been integrated in all PI Software parts from the beginning and in a usable and professional way (not the one e.g. used for AF Audit Trail with MS SQL CDC, this is unusable!!).
One must be able to have a new Version of a display with a clear Audit Trail for the Changes (who/when/why (the why could be in a free text comment field).
PI Vision Audit Trail: It would be good to see who created, edited or deleted a PI Vision display and when. And a versioning and comment function for displays would be ideal (example: "Version 2.0, ITOT Change Request #123456, New reactor position 10 added to display").