AVEVA Product Feedback


Add a new idea Subscribe
Status No Status
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Variable True For parameter for Event Frame Analyses

As an AF Administrator, I want to configure an Analysis Template for Event Frames with a True For parameter that would have it's value stored in an AF Attribute (configuration item). The use case is that elements built from the template will have Event Frames that will require a different True For value. I would like to have the analysis both base off a template and with the possibility of having different True For values. It would also be nice to have a True For parameter for the End Time. This is already a request: https://feedback.osisoft.com/forums/555148-pi-server/suggestions/17648182-event-frame-end-trigger-time-true-functionality
  • Attach files
  • Guest
    Reply
    |     Jun 19, 2023

    The ability to set the True For in a Variable would allow for the customer to configure this based off there machines. Creating a event frame generation for downtime, we tried to implement a TimeGT function with a threshold variable that held the Start Trigger up until it had been at least the configured amount of time. With the Event Frame Generation being a event triggered analysis, this would not always correctly trigger a event frame. If the analysis goes to periodic, the start time of the event frame is the period instead of the trigger time of the start trigger. If the True For was configurable in an attribute, that would allow for better variability from different elements.

  • Guest
    Reply
    |     Aug 20, 2022
    We are considering migrating from another alerting system that supports a "grace period" which can be different across multiple assets/equipment of the same type (e.g. same template). The event frames true for can only be set on the template. As such, migrating to event frames/notifications will result in less granular configuration of "grace periods" and we would have to use a generic one to apply to all assets/equipment of the same template. We have a workaround in some cases, not all, by using the TimeGT etc. functions and referencing an attribute for the start time, but I suspect these functions are more expensive than using a native grace period like true for. There are other limitations as well such as not being able to use other functions such as Compare to implement deadbands more easily.