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.

Status Reviewing
Portfolio area Enterprise SCADA Server
Products Alarms
Created by Guest
Created on Jul 10, 2023

User alarm limits should obey existing alarm deadbanding configuration

After configuring user alarms using the “user hi” and “user lo” functionality, alarms are being generated without consideration for the alarm level deadband configured for the point.

For example:

  • A user high alarm configured at 100 will ring into alarm at 100, and will clear at 99.
    This results in chattering of the user alarm, and modifying the deadband value does not affect this.

  • A high alarm (not a user alarm) configured at 200 with a deadband of 15 will ring into alarm at 200, and will not clear until the value drops down to 185.

Reducing nuisance alarms is a key part of our CRM thought leadership.

The operator chooses the user-alarm limits they desire, and the administrator sets the alarm-level deadband.

The operator does not require the ability to set the alarm-level deadband.



PMFR: http://tcjira.aveva.com/browse/PMFR-365

Expectation

User-alarm limits obey the alarm-level deadbands configured for the point.

The operator chooses the user-alarm limits they desire, and the administrator sets the alarm-level deadband.

The operator does not require the ability to set the alarm-level deadband.

Idea business value

A top initiative for MidStream to be the leading SCADA CRM provider for pipeline operators. Using user-alarms today could increase false alarms, which is undesirable.

Reducing nuisance alarms is a key part of our CRM thought leadership.


Idea Type Improvement
Idea priority 5 – Critical to my company
User Persona Pipeline Operator
Work in
OASYS-381 User alarm limits should obey existing alarm deadbanding configuration
Work status
  • Attach files