View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004792 | 10000-009: Alarms and Conditions | Spec | public | 2019-06-21 22:54 | 2022-05-17 15:41 |
Reporter | Alex Johnson | Assigned To | Paul Hunkar | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.05.02 RC1 | ||||
Summary | 0004792: Abnormal Situation Management / Situational Awareness and the OPC UA Alarm Model | ||||
Description | Modern operator interfaces use techniques originally described in the ASM's Guidelines (Effective Console Operator HMI Design Practices (ISBN: 978-1514203859)) and elaborated in High Performance HMI Handbook (https://www.amazon.com/High-Performance-HMI-Handbook/dp/0977896919) depend on consolidating alarm state. The current representation of alarms does a fine job of support a "Current Alarm Display" and it lacks the ability to do alarm consolidation / roll-up. For example, an object at the lowest level may have multiple alarms of different types and severities. A mechanism to summarize them is needed for Situational Awareness graphics. Likewise, a given object, which may consist of other objects with alarms), should be able to not only have its own alarms, but also represent the alarm state of the objects that compose it. I discussed this at the OPAF meeting with Paul Hunkar and Jeff Harding and there was agreement that the OPC Foundation should give this consideration. | ||||
Steps To Reproduce | N/A | ||||
Additional Information | N/A | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
Continuing my study of FF Alarming vs. OPC UA alarming, I found that FF has a rather complex parameter - ALARM_STA, see FF-890 Section 4.4.3.12 - that can represent the current state of 16 process alarms, i.e., it is an alarm summary in the block. For each of the 16 alarms, it can retain/store the current alarm state, the state of acknowledgement, the state of reporting, and the disabled state. |
|
from other discussion it may also be import to show the highest priority and highest unacked priority in the summary variable (probably need to define an interface that can be added to anything that summaries what is available in the hierarchy below the object that added the interface (also need to consider a variable also) - note: hierarchy would require a notifier hierarchy |
|
Added a new section describing an AlarmStateVariableType, that would provide an alarm summary. |
|
Agreed to changes edited in Telecon. |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-06-21 22:54 | Alex Johnson | New Issue | |
2019-06-22 15:19 | Jim Luth | Severity | major => feature |
2019-06-22 15:20 | Jim Luth | Target Version | => 1.05 |
2019-06-22 15:21 | Jim Luth | Assigned To | => Paul Hunkar |
2019-06-22 15:21 | Jim Luth | Status | new => assigned |
2019-07-05 18:29 | Alex Johnson | Note Added: 0010464 | |
2019-12-26 05:56 | Paul Hunkar | Description Updated | |
2020-11-19 19:51 | Paul Hunkar | Note Added: 0013281 | |
2022-02-21 05:43 | Paul Hunkar | Note Edited: 0013281 | |
2022-04-26 03:34 | Paul Hunkar | Status | assigned => resolved |
2022-04-26 03:34 | Paul Hunkar | Resolution | open => fixed |
2022-04-26 03:34 | Paul Hunkar | Fixed in Version | => 1.05.02 |
2022-04-26 03:34 | Paul Hunkar | Note Added: 0016624 | |
2022-05-17 15:41 | Jim Luth | Status | resolved => closed |
2022-05-17 15:41 | Jim Luth | Fixed in Version | 1.05.02 => 1.05.02 RC1 |
2022-05-17 15:41 | Jim Luth | Note Added: 0016721 |