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 Completed
Product AVEVA™ PI Server
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Use Event Frame attributes as inputs to Event Frame analysis in the Outputs at close section

It would be nice if it was possible to access Event Frame attributes in the Outputs at close section of an Event Frame analysis. Use case: I have an event frame generation analysis and I would like to write a few outputs to the event frame on close. I want to write outputs based on the duration of the event frame and whether someone has already edited the event frame while it was open.
  • ADMIN RESPONSE
    Aug 20, 2022
    The current release supports the EventFrame() function. There are 3 options: "StartTime", "EndTime" and "Duration". If an event frame was created by PI Analysis Service, we advise users not to use a different client to make changes to the event frame. There is a possibility that PI Analysis Service would not be able to close the event frame if a different client has it checked out.
  • Attach files
  • Steve Boyko
    Reply
    |     Aug 20, 2022
    This originated from my PI Square post. The ability to run an analysis on event frame close is useful, but I think it is pretty limited unless you can refer to other event frame attributes during that analysis. In the original post it was suggested that this could lead to a circular reference, but I don't think that should be an issue since the analysis is guaranteed to only run once, at event close.