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
Status Reviewing
Portfolio area Enterprise SCADA Server
Created by Vitali Unke
Created on May 31, 2024

RELATED IDEAS

EPCO: Alternate Alarm Limit Enhancements

Big Picture User Experience

Enterprise is asking for the following enhancements to Alternate Alarm Limits:

  • 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

    • use case: TransGas have analogs have unique alarm limits in winter, but share a common alarm limit set in summer. Customer wants 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

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

    • agreed.

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

    • the ability to configure a single alarm limit set that can trigger from multiple states of the trigger point.


Detailed Description



Acceptance Criteria



Business Value

EPCO paid for this enhancement on their existing


Target Version

Target version for this feature: ES24SP1

Version the customer is on or consuming: 2018?


Customer, Project, and Deadline Details

Customers (names/projects) that will consume this: EPCO

Deadlines and Commitments: Plan to go live on ES24SP1

Commercial and/or Contractual Impacts: Yes

Is this a Customer Funding Candidate?: No - they paid for it once already


Customers System / Architecture

Size: Small, Med, Large

Topology: Single site, Multi Site, and Enterprise

Any Unique configuration to note?: unknown

Has this functionality been delivered before?: yes


Out of Scope


Assumptions



Dependencies


Upgradability



PSR - Performance, Scalability, Resilience

Important PSR aspects for this feature?

What if there are 10,000 of these? .

How quickly is this expected to react/respond? .

Does this impact failover / mode switch? .

Is this assumed to have performance impact, or not? .



NFR - Non-Functional Requirements

Documentation: .

Operating System: .

Other AVEVA products: .

3rd Party products: .

CPU / Memory / Disk requirements/constraints: .


Risks/Mitigations


Mock-up / Supporting Information


Architecture Review Required?

Unlikely.


Do we need a SPIKE?

Unlikely.


Links

Aha: .

Jira: http://tcjira.aveva.com/browse/PMFR-574

Class 5 Estimate: .

Implementation: .

  • Attach files