Skip to Main Content
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.

Status No Status
Categories User Experience
Created by jmjackson
Created on Aug 18, 2022

Ad Hoc Workspace Trends Should Default to NOW

It appears that by default when adding data points to the Ad Hoc Workspace (AHWS) that the time range is set to the interval shown in the time bar (ex. 1H, 8H, etc) and the End Time is set to the current date/time (as of PI Vision 2021 patch 1). If close the AHWS, add more data points to the AHWS, then open the AHWS again the time range is still set to whatever the start and end times where when the original AHWS was opened (without NOW active). This can be confusing to users when Ad Hoc trending as they may think the AHWS is showing a real time trend when it is not. The user can click the NOW button and then for the rest of their PI Vision session the AHWS will show a real time trend with NOW active, but if they close the PI Vision session and open a new one they will have to remember again to click the NOW button so that all trends in the AHWS show real time data. It seems like the better behavior would be to have the AHWS default to NOW when adding tags instead of defaulting to the End Time of when the AHWS was originally opened/created. I can see the "static" start and end times persisting between the addition of tags to the AHWS being useful but seems like that should only occur when the user manually sets the start and end times on the AHWS. If the user doesn't manually set the start and end times of the AHWS might be better to default to NOW so that users will always by default trend real time data when adding tags to the AHWS.
  • Attach files