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.
I've noticed when a PI-Vision trend end time is not the same as the display end time, PI-Vision will request the full history of the trend at each display update. The historian cache ratio is affected as all the old data is repeatedly requested at the display scan rate.
Even trends with static start & end times will cause this behavior. There should be a way to cache that information in the IIS worker process as is done with trends/displays where the end time is the current time.