MVE and non-MVE Annotations for MVE on Metasys UI - 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

On an MVE site, MVE annotations are the annotations you are required to provide within the MVE Validation window, while non-MVE annotations are any optional or non-required annotations that you separately add to an alarm or audit.

Non-MVE optional annotations: On an MVE site, you can use System Activity to add optional non-MVE annotations to non-discarded audits and alarms. This functionality is also available on non-MVE sites. Refer to System Activity for more details.

What permissions do I need to add non-MVE annotations? To add optional non-MVE annotations to alarms, you must have the Manage Item Events permission for the alarm's authorization category.

To add optional non-MVE annotations to an audit, you must have the Manage Audit History system privilege.

Non-MVE forced annotations: The Metasys UI's Forced Annotations feature for non-MVE annotations is available only on non-MVE sites. Refer to Annotations for more details.

Also refer to Metasys System Preferences and Site Settings for more details.

Annotations when commanding: On only non-MVE sites, the Commanding window provides a field for entering a non-MVE annotation when sending a command to one or more objects. The non-MVE annotation is then associated with the audits for the command.

On an MVE site, the Commanding window opens the MVE Validation window and prompts you for an MVE annotation when required. You can use System Activity to add a non-MVE annotation to the audits for the command after the Commanding window is closed.

Annotations when acknowledging alarms: On only non-MVE sites, the Acknowledge window provides a field for entering a non-MVE annotation when acknowledging one or more alarms. The non-MVE annotation is then associated with the acknowledged alarms.

On an MVE site, the Acknowledge window opens the MVE Validation window and prompts you for an MVE annotation when required. Use System Activity to add a non-MVE annotation to one or more alarms before opening the Acknowledge window or after the Acknowledge window is closed.

Annotations when discarding alarms and audits: On only non-MVE sites, the Discard window for audits and alarms provides a field for entering a non-MVE annotation when discarding one or more alarms, audits, or a combination of alarms and audits. The non-MVE annotation is then associated with the discarded alarms and audits.

On an MVE site, the Discard window opens the MVE Validation window and prompts you for an MVE annotation when required. Use System Activity to add a non-MVE annotation to alarms and audits before opening the Discard window.
Note: Once an audit or alarm is discarded, no more annotations can be added to it.