Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our new 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.

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

Trigger analysis on events since time creation of new version AF element.

Situation: Attribute of an AF element is one of the triggers for Event Frame analysis for sending critial Notifications. Currently: After creating a new version of an AF Element and setting a new value for the attribute the changed value will possibly not trigger the (Event Frame) analysis (if start trigger is true). This results in missing critical Notifications. Reason is that the analysis is restarted after a new version is created and the value may be changed before the analysis is operational again. The analysis doesn't see the changed value as an event than. Periodic triggering may not be a work-around since this will give extra load when frequency and number of analysis is high. Solution could be: evaluate start trigger on start of analysis.
  • Attach files