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 Events (EF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Event Detail Trend Time Buffer

Ability to set a default lookback and look forward period on event detail trend. if the event is 30 minutes long and my lookback and lookfoward period is 30 minutes then the trend timeline would be [event start time]-30m to [event end time]+30m. This gives the user context to what happened leading up to the event and after the event in the trend.
  • Attach files
  • Brent Bregenzer
    Reply
    |     Feb 8, 2024

    It would be good if the Event Details display, which has a URL like, https://<Vision Server>/PIVision/#/EventDetails?server=<AF Server>&eventid=<Event Frame GUID>, also accepted the query parameters starttime & endtime and allowed them to override the start and end times of the EF shown in the display.

    As a workaround, you can use URI builder attribute on the EF template to construct a link to a standard or ad hoc Vision display and dynamically pass adjusted start and end times using the query parameters. See the below articles for more details.

    Configuring Notification Emails to Link to PI Vision Displays with Event Frame Time Range

    How to use URI Builder for Event Frames with delayed Attributes

  • Guest
    Reply
    |     Aug 19, 2022
    agreed - I do this with the hyperlink function in excel - will pull a bunch of events in and let the user build the before/after offsets so that they can see before the event started and after the event ended. It would be nice to have some native functionality like this.
  • Guest
    Reply
    |     Aug 19, 2022
    I currently use Custom symbols that take an Event (e.g a batch), determine chart start- and end-times from the batch start- and end-times (+/- several minutes), and plot a chart based on those times. But that's quite a big piece of custom code. I think showing just a small percentage before and after should not be a major deal to implement.
  • Guest
    Reply
    |     Aug 19, 2022
    This is indeed something that I miss as well. The option to have a rootcause event is not convenient, because of the double amount of Event Frames that will be generated by this. For scaleablity sake, it is not the solution that we are looking for.
  • Guest
    Reply
    |     Aug 19, 2022
    In response to Roger Palmen, "I currently use Custom symbols that take..." Thinking even further, we currently have absolute time, and relative time in PI. Relative time is than related to a fixed point in time (like *, y, t, etc.). Ideally we could have a time relative to the EventFrame start and end: Event.Start-10s to place on the timebar... this splits the functionality into two parts where the first part allows to place an EventFrame in the timecontext of a display (and not just the timerange).
  • Guest
    Reply
    |     Aug 19, 2022
    I disagree - as sometimes, the ONLY thing I care about is the root cause. Maybe your suggestion should be that we need one or the other, or both? Right now, you get the event, or both. I would love a shot to just get the root cause events.
  • Guest
    Reply
    |     Aug 19, 2022
    Currently when i visualize and EventFrame in PI Vision, the trend does not show the exact 'change' that leads to starting or ending the EventFrame, as the exact start and end times are used. To properly see the 'change' that led to the EventFrame i want to see just some small time before and after the EventFrame. As events can differ between seconds and hours, this would ideally be a percentage.