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.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Notifications
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Notifications for events in the past

Currently notifications are not triggered (send) by events that are more than 72 hours in the past. For me it is necessary to get notifications from events in the (endless) past. Ideally I would like to configure for each notification separately the time range (from now on backwards) in which the notification should be triggered.
  • Attach files
  • Yuriy Sadovskiy
    Reply
    |     Dec 5, 2024

    Dear Developers,

    It would be great to be able to configure the time range (from now on backwards) in which the notification should be triggered. Even if not for each notification (ideally), but for the whole Notification system. We work a lot with historical data, and I think we are not the only one. It should not be dangerous to give users the possibility to configure that, because there is always default value 72 hours. Could you please check this possibility? Thank you very much!

  • Gregory Malek
    Reply
    |     Jan 31, 2024

    It would be very useful to have the option to send out notifications for events more than 3 days old. Occasionally we need to manually correct certain PI data and regenerate a revised version of the original notification.

  • Guest
    Reply
    |     Aug 20, 2022
    It sounds like this may actually be a request about the creation of the Event Frame rather than the sending of the Notification. Or is it both? Also, if historical EFs are getting created, why is the preference to receive an e-mail instead of just using a client tool to look up the history?
  • Guest
    Reply
    |     Aug 20, 2022
    For a lot of TAGs we receive the data very late. For example, somewhen between 1st of May and 1st of June we receive a value for the timestamp 1st of April (this value is valid for the whole April). When the data comes in, I need to be informed that it is available in the PI-System so that we can do our monthly technical account for April. The event frame for this event is getting created, but the notification is not triggered, because the timestamp is too far in the past (>72h).
  • HolgerJoistOmv
    Reply
    |     Aug 20, 2022
    I'd like to have this feature for testing notification mails for situations that rarely occur.
  • Christoph Rose
    Reply
    |     Aug 20, 2022
    We are using Event Frames and the triggered notifications to a web service delivery endpoint in order to run more complex analyses outside of PI and return the results into the PI system. As notifications to the web service are no longer triggered when backfilling more than 72 hours in the past, we will have to create a separate solution for historical analyses and for live analyses. Being able to configure the time range within which the notification would be sent when backfilling would allow us to use a single solution for the running system/live analyses and also historical analyses.
  • LClark
    Reply
    |     Aug 20, 2022
    If you use PI Notifications to send for example daily reports and those reports are missed for more than 3 days, then you effectively have lost the ability to send the reports. You must manually create them using other PI client tools. It seems like when you are manually backfilling analyses that generate the notifications, there should be a simple configuration option to increase/decrease the 72 hour setting or disable it all together.
  • peheuvel
    Reply
    |     Aug 20, 2022
    Because of a serious incident in our DC the notification server was >72 hours not operational. We also would like to have this parameter to be set within a parameter.