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

RELATED IDEAS

Under the "Event Frame Search" option, give users more options for triggering on Attribute Values

When setting a notification's trigger criteria and specifying the "Event Frame Search" option, give the user more options for triggering on Attribute Values. Current options: Equal, Not Equal Suggestions: Greater Than, Less Than, Greater Than Or Equal, etc. Additionally, allow the user to specify AND/OR clauses between multiple Attribute Value triggering criteria. Currently, this seems to be an implicit AND only.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    +1! We typically use the same event frame template for similar events - even if they are of different severity level - so being able to use >, <, etc logical operators would allow us to keep using a smaller set of event frame templates while providing flexibility on which events need to trigger a notification. Further, I can have multiple notification triggers that use the same event frame template but send to different groups based on these logical conditions. With only == and != operators, I am forced to either add several boolean attributes to my event frame as flags for each condition, or create and manage some kind of digital state attribute on the event frame. This feels like more complexity than necessary.
  • Guest
    Reply
    |     Aug 20, 2022
    This also applies to adding additional criteria to an SQC-analysis generated notification, since SQC analyses don't allow additional logic in the start triggers.