Big Picture User Experience
Improve SCADA Controller situational awareness by including prior state of the point when new alarm is generated.
Detailed Description
Currently, when analog point changes state to an abnormal state and results in alarm, the new alarm contains information in the description the current state and state the point transitioned from.
This request is standardize this behavior among Analog (already works as expected), Status, MultiState, Rate and RTString.
Business Value
Improves our situational awareness of SCADA Controllers
Customer, Project, and Deadline Details
Must be delivered no later then Q4 of 2026
Customers System / Architecture
Size: Med, Large
Topology: Single site, Multi Site, and Enterprise
Has this functionality been delivered before?: No
Out of Scope
Only the above mentioned tables.
Assumptions
None Identified.
Dependencies
None Identified
Upgradability
As always, the system change (if any) need to take into consideration for upgradability. Any impacts to a smooth and easy upgrade will be resolved as part of the feature.
PSR - Performance, Scalability, Resilience
PSR impact is not known.
NFR - Non-Functional Requirements
Release Vehicle: released as part of the larger product? Released independantly?
Compatibility: any explicit compatibility requirements?
Documentation: .
Operating System: .
Other AVEVA products: .
3rd Party products: .
CPU / Memory / Disk requirements/constraints: .
Risks/Mitigations
Does this seem risky? If so, tell us why.
Mock-up / Supporting Information
Have a screen already sketched out on a napkin? Snap a pic and put it here. Or get fancy and put a Visio or other mockup here.
SWANA captures? Existing Code? ADE/XOS screens?
Architecture Review Required?
Does it seem like this will need input from the Architecture team? Why?
Anything in particular the architecture team should keep in mind when reviewing this feature?
Do we need a SPIKE?
Links
Jira: http://tcjira.aveva.com/browse/PMFR-592
