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.

Add a new idea Subscribe
Portfolio area Enterprise SCADA Server
Products Alarms
Created by Guest
Created on Dec 7, 2023

RELATED IDEAS

Alternate alarm limits: support status, multiple trigger states, and a zero-state set to revert to

Configuration Audit

Opening the point's events on a record's control panel should show: changes made to the almlimit, and the almlimitset record that it was is assigned to (otherwise changes to limits can be made affecting the point, but they would not show up in the point's event history)

  • enhancement - must have: when the alarm limit set modifies a point's alarm limits, these changes should show up in the configDataMod summary for the point in question, and indicate the alarm limit set that caused the changes

Zero-set to revert to

Customers have analogs with unique alarm limits for winter, but share a common alarm limit set in summer. Customers want to create a single "summer" alarm limit set, and when it is not active, the points should fall back to using their unique alarm limits. Currently, users should create two alarm limit sets: one for summer and one for winter.

  • enhancement - should have: after an alarm limit set is un-applied, analogs should revert back to their original alarm limits as they were before the alarm limit set was applied

Support Status as a trigger

  • enhancement - should have: almlimitset should accept status (it currently only accepts multistate)

Support multiple alarm limit

To reduce the number of alarm limit set and alarm limit records needed, it is requested that the current 1-to-1 relationship be expanded to a many to one relationship, where in a single alarm limit set can be linked to multiple alarm limits, such that different states of the trigger point related to corresponding alarm limits.

  • enhancement - nice to have: almlimit should be able to accept multiple states (eliminating the need for multiple records)

Expectation

See description
Idea business value

Audit

Since this is a change to configuration, and especially as it relates to alarming, any changes to a point's alarm limits, however made, should be audited in the configuration audit log for future audits and analysis.

Revert Set

This would reduce by half the number of configuration records required for a simple winter/summer mode of operation.

Support Status Trigger

Not sure what the problem to solve is with this one

Support multiple alarm limit

The would further reduce the number of records to create and maintain.
Idea Type Improvement
  • Attach files
  • +1