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 Event Frames (EF)
Created by cdawson
Created on Aug 20, 2022

RELATED IDEAS

Event Frame Generation for Step Changes

There does not seem to be a clear and concise way to trigger a new event frame (and end an old one) based on a step change in a tag. For example, if we had a tag, PHASE, that changed every time we entered a  new phase and remained at that value, I would like to end a previous EF and start a new EF anytime that tag changed. Currently, even with performance equations, there doesn't seem to be a clear way of doing this with an EF Analysis. You can do it with the EF generator interface, but it is clunky and difficult to scale.
  • ADMIN RESPONSE
    Aug 20, 2022
    PI Server 2018 has been released.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    I found I had to schedule as periodic rather than Event-Triggered, and use "Not HasValueChanged({Pi Point})", but this is still going to miss a small chunk of time based on my evaluation period.
  • Guest
    Reply
    |     Aug 20, 2022
    I learned it this way: create a boolean Pi Point attribute and use HasValuechanged to toggle this boolean value. Then create 2 event frame generation analysis for the same event frame template in which this newly created boolean attribute is the start trigger. In the first analysis start on TRUE, in the second start on FALSE. (no end trigger defined, so defaulted to the opposite value as it's a boolean) This will make sure that at any time 1 event frame is in progress: when the first analysis ends an event frame, the second analysis will immedialtely (no gaps) start a new one, and vice versa.
  • Guest
    Reply
    |     Aug 20, 2022
    In AF 2018, event frame generation for step changes will be natively supported so you don't have to create complicated analyses yourself.