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 Display Management / Displays Page
Created by Guest
Created on Aug 18, 2022

RELATED IDEAS

Allow editing of Vision display start time and end time together..

It would be great if Vision display start time and end time could be configured together. Whenever I change start/end time of a trend, PI Vision immediately requests for data from PIDA even though I haven't finished entering the start/end times. For example I have a trend with last 8 hours of data. Then I want to check data back in January 2010. When I enter 1-Jan-2010 into the start time field and click on end time field to set the end time of the trend to 1-feb-2010, PIVision already fires a query to PI Data Archive before I have the chance to change end time of the time range. This means that PI Vision asks for data between 1-Jan-2010 and now. This can be a very expensive query which can run for a very long time. If this repeats multiple times, PIDA can get overloaded.
  • Attach files
  • Guest
    Reply
    |     Aug 18, 2022
    I agree this feature is needed. It was explained with the original submission but to reiterate. Say I need to look at a 1 hour range of data that occurred 1 year ago. The only way to do this (at least to my knowledge) is to load the entire 1 year range of data. This is at best very wasteful and at worst impossible depending on the type of data. Edit: One potential workaround for those trying to do this would be to use a relative time reference for the end time. Typing "*-1y" to offset the end time will retain the previous time range. editing the time string in the end time will cause the range to change as described before. This is not ideal since sometimes you want to zoom in on a specific time and doing relative time can make that more difficult but it should get you in the ballpark.