Difference between revisions of "uaCap:AlarmsConditions Alarms"

From UaCapabilities
Jump to: navigation, search
 
Line 1: Line 1:
 
{{CapabilityUri|/Alarms}}
 
{{CapabilityUri|/Alarms}}
 
'''Description'''
 
'''Description'''
<br>Support the Alarm information model and the notification mechanisms about the Alarm state. It also include a complete information model for management of the transition between various states by an alarm, such as shelving, acknowledgement, confirmation and the addition of comments The alarm model includes support for either or both an exclusive or nonexclusive alarm state model. In the exclusive state model, only one sub-state can be active at a time while in the non-exclusive state model more than one sub-state can be active at a tim.e
+
<br>Support the Alarm information model and the notification mechanisms about the Alarm state. It also includes the management of transitions between various states by an alarm, such as shelving, acknowledgement, confirmation and the addition of comments.  
<br>The Alarm model build on the condition model and provide all aspects of the condition model.
+
<br>The Alarm model builds on the condition model.
  
 
'''Usage Considerations'''
 
'''Usage Considerations'''
<br>Indicate areas of the process that require immediate attention. Areas of interest include (but are not limited to); safety limits of equipment, event detection, and abnormal situations. In addition to operators, other client applications may collect and record alarm information for later audit or correlation with other historical data.
+
<br>Indicate areas of the process that require immediate attention. Examples are:
 +
* safety limits of equipment
 +
* event detection, and
 +
* abnormal situations.
 +
In addition to operators, other client applications may collect and record alarm information for later audit or correlation with other historical data.
  
{{uaConformance|TBD <!-- Client -->|
+
{{uaConformance|
TBD <!-- Server -->
+
[http://opcfoundation.org/UA-Profile/Client/ACAlarm '''Ability to handle alarms''']
<!-- Example
+
|
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
+
[http://opcfoundation.org/UA-Profile/Server/ACAlarm '''Conditions with active/inactive state''']
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
+
-->
+
 
}}
 
}}

Latest revision as of 13:44, 16 February 2015

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

Description
Support the Alarm information model and the notification mechanisms about the Alarm state. It also includes the management of transitions between various states by an alarm, such as shelving, acknowledgement, confirmation and the addition of comments.
The Alarm model builds on the condition model.

Usage Considerations
Indicate areas of the process that require immediate attention. Examples are:

  • safety limits of equipment
  • event detection, and
  • abnormal situations.

In addition to operators, other client applications may collect and record alarm information for later audit or correlation with other historical data.


Conformance Testing

Client Server

Ability to handle alarms

Conditions with active/inactive state