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.
I've been working with the PI Monitor templates that the PI team created a few years ago. There were some templates that had a standard Status Attribute. In this case, it just covered preventing the generation of Event Frames.
If the Notifications Suppressed attribute = True, then the Event Frame triggers would be set to False.
IF Suppressed=True, then the Event Frame Variable Send_Notifcations = FALSE.
Each Trigger contains "AND Send_Notifcations"
They also added a Analytics that looked at the Parent element for the same Attribute and/or the Operational Status of the Parent. Either could disable the child Elements. If you set your elements up hierarchically, this Status eventually flows down to the bottom elements.
I added a table that can match all the element under a sub-tree. A function allows all the children to set Notifications Suppress = False at the same time. With a time stamp, I can do the same thing that the OSI NOC could do. i.e. quiet alarms until a certain date. This prevents the notification suppression from being forgotten.