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 Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

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
    Reply
    |     Aug 20, 2022
    Created this from a Tech Support case, suggested to the customer to add more details concerning their use case.
  • Guest
    Reply
    |     Aug 20, 2022
    For those interested in this, a workaround can be found here: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000027383
  • Guest
    Reply
    |     Aug 20, 2022
    Would this attribute, with the EF duration, change over time or is it static?
  • Guest
    Reply
    |     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.