AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

Add a new idea Subscribe
Status No Status
Product AVEVA™ PI Vision™
Categories Administration
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Allow configuration of data update rate on a per display basis

As a display creator or PI Vision administrator, I would like to be able to set the tag and/or Event Frame update rate on a display-by-display basis.
  • Attach files
  • John_Gardner
    Reply
    |     Nov 30, 2022

    This is critical as Processbook is being retired. I need some screens to have a faster refresh rate.

  • Guest
    Reply
    |     Aug 19, 2022
    That is linked to the Tech Support case #781593 where a single PI Vision display consumed 70 times more SQL resources, frequently reaching at 100% CPU, than 20 other system databases with +500 active users. The PI Vision display was referencing data from multiple AF Elements with some of them having a tons of Event Frames. As a workaround, I disabled the EF Update and set the EF Update Rate to 30 mins (was 5 seconds) on the entire PI Vision system...  
  • Guest
    Reply
    |     Aug 19, 2022
    I think this is basically the same thing. To improve the response time, it would be great if you could set the number of samples pulled for a trend such that if you are zoomed in you can see 1 second data if available, but if trying to pull a year worth of data, it pulls data every 5 minutes (or something like that). PI should be able to calculate an appropriate interval. I have a lot of trends that include 1 second data needed for troubleshooting if we have an issue, but normally I don't need that much detail. However, there is not a way of reducing the sample period that I know of.