Difference between revisions of "uaCap:AlarmsConditions PreviousStates"

From UaCapabilities
Jump to: navigation, search
Line 4: Line 4:
  
 
'''Usage Considerations'''
 
'''Usage Considerations'''
<br>This is a requirement in specific domains, where all transition in an alarm model must be individually responded to by one or more operators.
+
* Domains, where all transition in an alarm model must be individually responded to by one or more operators.
 +
* Safety critical systems that require that all Alarms be acknowledged even if it the original problem goes away and the Alarm returns to the inactive state.
  
{{uaConformance|TBD <!-- Client -->|
+
{{uaConformance|
TBD <!-- Server -->
+
[http://opcfoundation.org/UA-Profile/Client/ACPreviousInstances '''Ability to list and acknowledge states that are older than the current state''']
<!-- Example
+
|
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
+
[http://opcfoundation.org/UA-Profile/Server/ACPreviousInstances '''Acknowledgement of prvious states required''']
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
+
-->
+
 
}}
 
}}

Revision as of 10:42, 16 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Alarms/PreviousStates

Description
An extension of the Alarm model where previous states of Alarms will be retained until they are acknowledged and/or confirmed.

Usage Considerations

  • Domains, where all transition in an alarm model must be individually responded to by one or more operators.
  • Safety critical systems that require that all Alarms be acknowledged even if it the original problem goes away and the Alarm returns to the inactive state.

Conformance Testing

Client Server

Ability to list and acknowledge states that are older than the current state

Acknowledgement of prvious states required