Skip to Main Content
AVEVA™ Products 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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Alarms should update group when the related point changes group

When a point generates an alarm, the alarm gets the same AOR Group as the point, and based on the AOR Group users can or cannot see the alarm and acknowledge it. But if after the alarm is generated the responsibility group is modified in the point, the group assigned to the alarm remains being the previous one, which could be no more controllable/viewable. This may result in a set of alarms not being able to be attended (acknowledged or even viewed).


  • Attach files
      Drop here to upload
    • Admin
      Jake Hawkes
      Reply
      |
      Oct 6, 2023

      My first question is around how often these groups change that would require active alarms to be re-assigned to the new group.

      AOR configuration is mostly static until assets change in the field, or there is a change to the operational paradiegm. Neither of these two situations would result in enough "stranded" alarms to warrant this change.