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.
IIn PI Vision we have plant displays showing overall status of plants, detailed displays on subsystems and even more detailed displays on component levels. All of these have event tables.
On plant level we want to see active events for the entire plant, on subsystem active events for entire subsystem and on component levels we want to see all events that have been active in the timebar duration independent of status. In all cases we want filter (within the search criteria) by the hierarchy, showing data from the selected level and all levels below.
Our problem today is that the nearest option to get what we want is to filter by “Assets on Display”, this works fine for component level and most subsystems. However, we do add attributes to displays which are not that relevant to meet the criteria “Assets on Display”. On plant level we miss out relevant events based on that we can’t have alle assets on a display.
One of the main selling points for the PI System is the functionality around the AF hierarchy. I find it strange that a hierarchy filter like this is not part of the PI Vision search criteria to utilise the strength of the AF hierarchy.
Had to split my single asset into a hierarchy due to performance issues within Pi due to the number of analyses running, causing Pi to run slow/stall for minutes at a time. Now that I have done that, the only way to see the events at the child level to the parent is to view all, which brings through all the events for all the machines created under that Asset template. Seriously frustrating that i cannot use the parent ID to filter, and still see the event frames that reside under that parent ID.