Setting alarm priority thresholds for requiring MVE electronic signatures and MVE annotations - Metasys - LIT-12011953 - Server - Metasys UI - 7.0.50

Metasys UI Help

Brand
Metasys
Product name
Metasys UI
Document type
User Guide
Document number
LIT-12011953
Version
7.0.50
Revision date
2024-03-19
Product status
Active
Language
English

When an alarm occurs, it is assigned an alarm priority of 255 (lowest) to 0 (highest) based on how the alarm is configured. If the alarm occurs for an object that requires an MVE electronic signature and/or MVE annotation, the alarm will conditionally require the same MVE electronic signature and/or MVE annotation, depending on the configuration of the site object’s alarm priority threshold attributes.

Note: You can configure different priorities for each alarm priority threshold. As a result, even if the object for which the alarm occurred requires both an MVE electronic signature and MVE annotation, the alarm may require only an MVE electronic signature, only an MVE annotation, both, or neither.
Signature Alarm Priority Threshold: When alarm occurs for an object that requires an MVE electronic signature, the alarm occurrence also requires an MVE electronic signature if the alarm’s priority is at or above the value configured for the site object’s Signature Alarm Priority Threshold attribute. The default value for Signature Alarm Priority Threshold is 140, so that alarms with lower priorities (141 to 255) will not require an MVE electronic signature. Change the value of the Signature Alarm Priority Threshold if you wish to use a different threshold for requiring MVE electronic signatures.
Note: When an alarm occurs for an object that does not require an MVE electronic signature, the alarm will also not require an MVE electronic signature regardless of the alarm’s priority.

Annotation Alarm Priority Threshold: When an alarm occurs for an object that requires an MVE annotation, the alarm occurrence also requires an MVE annotation if the alarm’s priority is at or above the value configured for the site object’s Annotation Alarm Priority Threshold attribute. The default value for Annotation Alarm Priority Threshold is also 140, so that alarms with lower priorities (141 to 255) will not require an MVE annotation. Change the value of the Annotation Alarm Priority Threshold if you wish to use a different threshold for requiring MVE annotations. See the following tables for examples.

Note: When an alarm occurs for an object that does not require an MVE annotation, the alarm will also not require an MVE annotation regardless of the alarm’s priority.
Note: To modify the Signature Alarm Priority Threshold or Annotation Alarm Priority Threshold attribute, click or tap the value of the attribute to open its edit field.
Table 1. Alarm priority threshold examples
Signature Alarm Priority Threshold Annotation Alarm Priority Threshold Alarm priorities for MVE electronic signature required 1 Alarm priorities for MVE annotation required 2
140 140

Required: 0 to 140

Not required: 141 to 255

Required: 0 to 140

Not required: 141 to 255

120 80

Required: 0 to 120

Not required: 121 to 255

Required: 0 to 80

Not required: 81 to 255

95 110

Required: 0 to 95

Not required: 96 to 255

Required: 0 to 110

Not required: 111 to 255

1 An MVE electronic signature is required only if the alarm is for an object that requires an MVE electronic signature.
2 An MVE annotation is required only if the alarm is for an object that requires an MVE annotation.