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.
Totally agree. This is the solution and easy to program
10 years ago, we implemented a two-step alarm acknowledgement process and all controllers quickly adapted to it as they recognized the value of not inadvertently acknowledging the wrong alarm when you are busy, that then disappears.
How it works. Acknowledging the alarm in the alarm bar clears the alarm and then the pop up comes up as a reminder of what you just acknowledged. The pop-up stays on the screen until acknowledged. The pop-up can display info like an 8-hr. graph, recent events and even a button that classifies the alarm as a false alarm, critical for complying with 192.631/195.446(e)(2). Once you are done with the alarm, then clear the pop up. See the sample image.
The business value is eliminating accidental alarm acknowledgement which can and does lead to failure to investigate, outages and safety issues. An additional benefit is documenting the delta between the time the alarm is received, alarm is acknowledged, and the alarm is finished. Great data for workload studies required by 192.631/195.446(e)(5).