Skip to Main Content
AVEVA Product Feedback


Status No status
Created by Guest
Created on Aug 20, 2022

Allow EventFrame("Duration") to be used as an EndTrigger

I want to stop my Event Frame after an amount of time that is stored in an AF Attribute. For my use case, the amount of time from the beginning of an Event Fame is an end triggering condition. One way to do this, would be to allow the EventFrame("Duration") function to be used as an end trigger.
  • Attach files
  • Guest
    Aug 14, 2025

    Event Frame Generation is made much more difficult if a specified time range cannot be selected, in industries that don't have SCADA systems or data is not constantly being sent by a device (LAB scale instruments), it makes it extremely hard to configure event frames, or your left configuring multiple additional analysis that could be rather easy with the setting. I would also consider this to extending it to also be able to use EventFrame("startTime") as well as duration and start time could be used in multiple ways to close and EF.

  • Guest
    Aug 20, 2022
    Created this from a Tech Support case, suggested to the customer to add more details concerning their use case.
  • Guest
    Aug 20, 2022
    For those interested in this, a workaround can be found here: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000027383
  • Guest
    Aug 20, 2022
    Would this attribute, with the EF duration, change over time or is it static?
  • Guest
    Aug 20, 2022
    In our use case, we want to create an event frame for a batch, the trigger is the batch ID attribute. Our ask is similar, but slightly different from this. We want to have a delay in the start of the EF after the Batch ID is written to insure that all of the other fields for the batch have been updates, ~12 attributes. The fear is that if we generate the EF when the batch ID is written, some of the others may not get updated and we would be capturing data in the EF from the previous batch.