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.

183 VOTE
Status No Status
Created by Willy Seah Wei Liat
Created on Aug 20, 2022

Automatic Recalculation of Event Frame in PI Analysis

As a user, I would like to have the option to automatic recalculation of event frame for out-of-order input events in AF analysis. The option is available for expression analysis in PI Analysis  2017 R2 but not for event frame generation analysis.
  • Attach files
  • MattBa
    Reply
    |
    Jun 14, 2024

    Why are these just remaining stale with no status after years?

  • MattBa
    Reply
    |
    May 3, 2024

    100 percent agree.

  • Nathan Anderson
    Reply
    |
    Feb 8, 2024

    The inability for the system to auto recalculate EF based analysis is a significant hurdle when dealing with qualified systems. After dealing with multiple deviations because of OOO data not triggering the generation of EF's that are used in integrations with validated MES systems, we're left with few options - abandoning event frames seems likely for this use case since we cannot reliably maintain a qualified data stream.

  • meierke1
    Reply
    |
    Aug 20, 2022
    is there a statement on this?
  • Guest
    Reply
    |
    Aug 20, 2022
    One of my big customers has many intermittent connections, so there is much out-of-order data, upon which they need to generate event frames for reporting.
  • Guest
    Reply
    |
    Aug 20, 2022
    Customer had Out-Of-Order values for inputs on an EF Analysis. This resulted in either No Event Frames being created, or Event Frames opened for a long time. Customer was backfilling the Analysis regularly but is very repetitive. This feature would definitely saving the customers some effort.
  • Guest
    Reply
    |
    Aug 20, 2022
    We have the same situation where events sometimes arrive out-of-order of tags that are input of an expression analysis with Recalculate analysis for out-of-order input events. As this output is used for an end trigger of an Event Frame, the event does not get closed sometimes. A manual recalc/backfill of the Event Frame analysis or a recapture of the created event frame manually fixes it. So if the same option for recalculation for out-of-order(and for relative analysis) was available for Event Frame analysis, problem solved. ;)
  • Guest
    Reply
    |
    Aug 20, 2022
    I think this is the same as; https://feedback.osisoft.com/forums/555148-pi-server/suggestions/34695688-automatic-recalculation-of-event-frame-in-pi-analy
  • Guest
    Reply
    |
    Aug 20, 2022
    we have the same demand for this feature to get implemented! I voted for it:)
  • Guest
    Reply
    |
    Aug 20, 2022
    This could be an optional value a per event frame that could be configurable as a Boolean. If enable kick the automatic recalculation if any attribute change.
  • rfesler
    Reply
    |
    Aug 20, 2022
    We have a situation where lab data may be delayed in being passed into PI. Therefore, it's imperative that either simultaneous event frames need to happen (which is not a current option) or automatic backfill needs to occur. One of these options is a must have!
  • wrighpat
    Reply
    |
    Aug 20, 2022
    I need this for EFs, I have long running EFs that are not being closed due to OOO events.
  • Guest
    Reply
    |
    Aug 20, 2022
    I would need this for EF as well - many EF's aren't being closed because of ooo events.
  • Guest
    Reply
    |
    Aug 20, 2022
    Create event frames that did not exist before the OOO events came in. Flag them as OOO to make clear why they did not trigger notifications at the time. For event frames that would not have been created if the OOO events had come in at the time, rather than deleting them, flag them as ‘obsolete’ or ‘superseded’
    1 reply
  • meierke1
    Reply
    |
    Aug 20, 2022
    As as PI Admin I want that a EF is automatically changed if for example the Trigger Tag is changing in the archived values from my PI system. It could happen that we completly remove the start end trigger for a specific event in the archive. Correspontenly the EF should also removed automaticaly. This is at least affecting the EF Generator
  • Guest
    Reply
    |
    Aug 20, 2022
    Need this as well. This is a must have!
  • Guest
    Reply
    |
    Aug 20, 2022
    As a user, I also would like to have this feature of PI Analysis. I am using a PI Connector to gather data with a specific past timestamp , and I need to trigger an EF based on those new coming data with old timestamps, but if the timestamp is too old, I cannot do trigger the EF based on the function HasValueChanged. We found other ways to do it, but with an automatic recalculation, it would be easier.
  • Matt Voll
    Reply
    |
    Aug 20, 2022
    this seems like a pretty big miss . . . a nearly 4 year old idea with a relatively high vote count . . . and no update?!?!
    1 reply
  • Guest
    Reply
    |
    Aug 20, 2022
    Very important this is fixed!
  • Guest
    Reply
    |
    Aug 20, 2022
    It's a critical limitation for EF. The automatic recalculation of EF in case of OOO shoud act on EF modifying them where necessary, saving the existing ID
    1 reply
  • Load older comments
  • +83