Configuration
General
To set up an alarm group, it must be assigned a name. This name will be used later for devices or alarm messages, which is why it should be as unique and descriptive as possible. The position of the new alarm group in the system is determined by selecting the parent alarm group. To make the subordinate devices of this alarm group less conspicuous when armed, stealth mode can be activated, which turns off the LEDs (does not affect the Ethernet port). If an alarm group is a particularly sensitive area, it is possible to extend its signaling range to the entire system. In the event of an alarm, the configured alarm would be triggered on all devices in the system.
Notifications
When a warning or alarm occurs in an alarm group or a subordinate alarm group, authorized users are notified through the configured channels. These settings can be configured separately for each alarm group or inherited from the parent alarm group. Only users who have been assigned to this alarm group will be notified. This setting must be made in the corresponding user accounts.
For each alarm type (Armed-Active, Always-Active, Fire, Sabotage, System Message), you can specify whether notifications should also be sent for warnings. It can also be decided whether the number of notifications of an alarm type per hour should be limited.
Arming
When an alarm group is armed, this activates the evaluation of armed-active alarms.
In case the secured area still needs to be exited after arming, a delay can be configured, which means the arming will only be carried out after the set time.
The duration of the acoustic signaling during arming can be changed or completely deactivated if needed.
During normal operation, pending alarms prevent an alarm group from being armed. This can be bypassed for external sensors using the "Always arm" button.
This function offers the possibility to prevent open windows from preventing alarm groups from being armed.
Automatic Acknowledgment
When an alarm is triggered, a user must normally respond and acknowledge it. If an alarm is not acknowledged, it cannot be triggered again, meaning any multiple occurring alarms of the same type (e.g. temperature alarm) will not be reported. Automatic acknowledgment prevents this by acknowledging all acknowledgeable alarms from devices in the alarm group at a fixed interval.
Alarm Settings
If a device in the alarm group triggers an alarm, this is signaled acoustically via the buzzer.
If a secured area needs to be entered before it is disarmed, pre-alarming can be activated. All devices in the alarm group that have a configured alarm delay of 5s or more will now acoustically signal that the alarm group must be disarmed.
For the different alarm types, you can configure how long a triggered alarm should be signaled via the device buzzer.
Sabotage Message
To prevent device failures in the system, the behavior of devices in an alarm group can be configured when potential sabotage is detected.
The set times indicate how long a device can be unreachable before a sabotage alarm is triggered.
Active Power
An alarm group can display and record the total active power of all subordinate SmartPDUs and SmartMeters. This can be activated separately for the power supply lines.
To enable active power recording, consumption recording and display must also be active.
Apparent Power
An alarm group can display and record the total apparent power of all subordinate SmartPDUs and SmartMeters. This can be activated separately for the power supply lines.
To enable apparent power recording, consumption recording and display must also be active.
Consumption
An alarm group can display and record the total consumption of all subordinate SmartPDUs and SmartMeters. This can be activated separately for the power supply lines.
Power Usage Effectiveness
Power Usage Effectiveness (PUE) is a metric for the energy efficiency of a data center. It indicates the ratio between the total power consumption of the data center and the power consumption of the IT equipment. The alarm group can display and record this value in the DetailView.
Airlock
An alarm group can control the transition between adjacent alarm groups as an airlock to achieve e.g. isolation.
The airlock function is available from KentixONE plan level L
Anti-Passback
When area change detection has been activated in the KentixONE system, alarm groups can be equipped with extended functions.
Using passages, it can be tracked which area (alarm group) a person last entered or left. When no person is registered in an alarm group anymore, it can be automatically rearmed.
DoorLock
A DoorLock can be assigned to an alarm group. This DoorLock is displayed in the KentixONE apps as a quick access for the alarm group.
External Alarm System
An alarm group in KentixONE can represent the monitored area of an external alarm system.
Via the external sensors and switching outputs of the extension modules KIO7052 and KIO7060, the feedback channel, arming readiness (optional) and switching signal of the external alarm system can be connected to KentixONE.
If the external alarm system is controlled via pulses, the use of a KIO7060 is recommended as it has output relays. If a KIO7052 is to be installed, it may be necessary to connect a multifunction relay between its switching output and the inputs of the alarm system. This converts the high/low level of the KIO7052 into the pulses required by the alarm system.
Event Profile (Automatic Arming/Disarming)
To have an alarm group automatically armed and disarmed, a previously created event profile can be assigned to it. This defines at which times the alarm group should be armed and disarmed.
Webhooks
Webhooks bieten in KentixONE die Möglichkeit, bei Eintritt eines Events eine HTTP-Anfrage an einen externen Server zu versenden. Hierzu können systemweite Webhooks angelegt werden. Ein solcher Webhook kann beliebig vielen Events zugewiesen werden.
Webhooks bieten auch die Möglichkeit, über die KentixONE SmartAPI Funktionen abzubilden, die nicht über die Standardkonfiguration verfügbar sind.
So könnten bspw. beim Auftreten eines Brandalarms die Schaltausgänge eines AccessManagers aktiviert werden, um die angeschlossenen Motorschlösser zu entriegeln.
Events
| Name | Beschreibung |
|---|---|
| Alle Alarme | Bei jedem aufgetretenen Alarm wird der Webhook verschickt. |
| Scharf-Aktive Alarme | Wenn ein scharf-aktiver Alarm auftritt, wird der Webhook verschickt. |
| Dauer-Aktive Alarme | Wenn ein scharf-aktiver Alarm auftritt, wird der Webhook verschickt. |
| Brandalarme | Wenn ein Brandalarm auftritt, wird der Webhook verschickt. |
| Sabotagealarme | Wenn ein Sabotagelarm auftritt, wird der Webhook verschickt. |
| Systemmeldungen | Wenn eine Systemmeldung ausgelöst wird, wird der Webhook verschickt |
| Vor Scharfschaltung | Der Webhook wird verschickt, wenn eine Alarmgruppe scharfgeschaltet werden soll.(1) |
| Nach Scharfschaltung | Der Webhook wird verschickt, nachdem eine Alarmgruppe scharfgeschaltet wurde. |
| Vor Unscharfschaltung | Der Webhook wird verschickt, wenn eine Alarmgruppe unscharfgeschaltet wurde.(1) |
| Nach Unscharfschaltung | Der Webhook wird verschickt, nachdem eine Alarmgruppe unscharfgeschaltet wurde. |
| Änderung des Schaltstatus (Scharf- oder Unscharfschaltung) | Wenn die Alarmgruppe geschaltet wird, wird der Webhook verschickt. |
| Zyklisch (5 Min, 10 Min, 15 Min, 30 Min) | Der Webhook wird zyklisch verschickt. |
(1) Der Webhook wird verschickt, wenn ein Schaltbefehl entweder von einem Benutzer oder der automatischen Scharfschaltung ausgelöst wurde. Bsp: (Un-)Scharfschaltbefehl durch Benutzer → Webhook wird verschickt → (Un-)Scharfschaltung wird ausgeführt