Key Concepts¶
The users and permissions of EnOS Alarm Management are inherited from EnOS Application Portal. Before starting, you should learn about the key concepts of EnOS Application Portal. Under an OU that has obtained and authorized Work Management, you can create a ticket response through Alarm Management and access Work Management to view the ticket details, so you also need to learn about the key concepts of Work Management.
Below are the key concepts of Alarm Management.
Alarm¶
An alarm is a record generated when the asset data value or the device status meets a set condition. For example, when the measurement point value of a certain device is greater than a specified threshold, an alarm will be triggered.
Metadata Relation¶
A metadata relation defines the mapping between a site type and an alarm group. Based on the mapping, Alarm Management identifies the current asset type and displays only the corresponding alarm groups, which keeps the alarm data of different business scenarios isolated. For example, users in a photovoltaic scenario see only the alarm groups related to photovoltaics.
Metadata relations are either public or private. Public relations are provided by the EnOS platform and cover generic industry scenarios such as wind power, photovoltaic, and energy storage. Private relations are used for user-defined scenarios such as buildings and campuses.
Alarm Group¶
Alarm groups are group types based on the site types to which the assets belong. Different alarm groups correspond to different alarm severities and alarm types. For example, you can configure the Solar group for assets of the solar site type, and the Storage group for assets of the storage site type.
Alarm Severity¶
Alarm severities are the level classification for different alarms according to the severities and handling priorities of events. For example, in Alarm Management, the following alarm severities can be configured for devices in the Solar group: Fault, Info, and Warning.
Alarm Type¶
Alarm types are types set for different alarms according to the different status of devices or the reasons for triggering the alarms. For example, in Alarm Management, the following types of alarms can be configured for devices in the Solar group: Performance Alarm, Device Alarm, and Status Alarm.
Alarm Tag¶
Alarm tags support bulk management of alarm severities, alarm types, and alarm trigger rules. They identify and categorize alarm metadata in different domains. Alarm Management lists the tag keys available to an OU. When adding a tag to a project, you can enter custom content as its value.
Active Status¶
An active status is used to define the current status of the alarm and Alarm Management has the following status:
Active: The alarm was triggered but has not been recovered. For example, when the value of a certain measurement point is continuously greater than the set threshold, the alarm is triggered and remains active.
Inactive: The alarm was triggered and recovered. For example, the first value of the measurement point was greater than the set threshold, an alarm was triggered, when the second value of the current measurement point does not meet the trigger condition, the alarm will be recovered and in an inactive status.
Acknowledgment Status¶
An acknowledgment status is used to define whether the alarm has been acknowledged and includes acknowledged and unacknowledged status:
Acknowledged: The alarm has been acknowledged.
Unacknowledged: The alarm has not been acknowledged and the acknowledgment operation can be performed on the alarm.
Alarm Trigger Rule¶
An alarm trigger rule is the alarm trigger condition configured for the KPI or measurement point of the asset. When the data value or status of the KPI or measurement point meets the configured condition, the alarm will be triggered.
Discrete Alarm¶
A discrete alarm is a feature that can be enabled when defining an alarm trigger rule. When a discrete alarm is triggered, the system generates an alarm record and immediately stops monitoring the event. When the trigger condition is met again, the system generates a new, independent alarm record that is not affected by the same alarm events before or after it.
Discrete alarms are typically used for device status monitoring. For example, configure an alarm to trigger when the temperature exceeds 40°C and enable discrete alarms. When the device temperature first exceeds 40°C, the system generates an alarm record. If the temperature continues to exceed 40°C for a short period, the system does not trigger the same alarm again, avoiding duplicate notifications. A new alarm record is generated only after the temperature falls and subsequently exceeds 40°C again.
Alarm Notification Rule¶
An alarm notification rule defines the alarm notification method after the alarm is triggered. In Alarm Management, you can set the notification by email, SMS, and pop-up window for the alarm.
Alarm Response Rule¶
Alarm response rules define how alarms are handled. In Alarm Management, the following two response methods can be configured for alarms:
Acknowledgment Response: After the alarm is triggered, the alarm can be acknowledged.
Ticket Response: A work order or service request can be created for the triggered alarm under an OU that has obtained and authorized Work Management.