Alarm Data Settings (Alarms node)
When you configure alarm data settings, specify the following:
Alarm Data Levels tab
Priorities
Name | Description |
|---|---|
Level | Add new priorities with level numbers of your choosing or use/edit the default priority levels (numbers 1, 2 or 3). These priority levels are used to configure the Initial alarm priority setting. |
Name | Enter a name for the entity. You can create as many as you like. |
Sound | Select the sound to be associated with the alarm. Use one of the default sounds or add more in Sound Settings. |
Repeat sound | Decide whether the sound should play only once or repeatedly until in XProtect Smart Client, the operator clicks the alarm in the alarm list. |
Enable desktop notifications | For each alarm priority, you can enable or disable desktop notifications. If you are using an XProtect VMS that supports Smart Client profiles, you must also enable notifications on the required Smart Client profiles. |
States
Name | Description |
|---|---|
Level | In addition to the default state levels (numbers 1, 4, 9 and 11, which cannot be edited or reused), add new states with level numbers of your choosing. These state levels are only visible in the XProtect Smart Client's Alarm List. |
Categories
Name | Description |
|---|---|
Level | Add new categories with level numbers of your choosing. These category levels are used to configure the Initial alarm category setting. NoteLevel 99 is reserved for the Emergency Alert alarm in XProtect Mobile client. |
Name | Enter a name for the entity. You can create as many as you like. |
Alarm List Configuration tab
Name | Description |
|---|---|
Available columns | Use > to select which columns should be available in the XProtect Smart Client's Alarm List. Use < to clear selection. When done, Selected columns should contain the items to be included. |
Reasons for Closing tab
Name | Description |
|---|---|
Enable | Select to enable defining a reason and comment when closing alarms. You can edit each individual alarm definition to either make defining a reason and/or a comment mandatory when closing an alarm or to exempt the alarm definition from defining a reason or comment when closing an alarm. |
Reason | Add reasons for closing the user can choose between when closing alarms. Examples could be Solved-Trespasser or False Alarm. You can create as many as you like. All reasons will be displayed as a drop-down list in the Apply reason form when closing alarms. Field restrictions
|
Comment | This field is optional. Add a comment to provide additional details about the reason the alarm was closed, for example: “Alarm triggered by an attempt to access a restricted area.” or “Triggered by mistake or without an actual security threat.” This value will be displayed as the default comment in the Apply reason form when the user selects the reason the comment is associated to. The user can edit the comment in the Apply reason form and define additional information to the comment. You can enter multiple lines of comments (CR and LF control characters can be used). Field restrictions
|
Custom Data | This field is optional. Specify a value in this field if you need to integrate your alarms with an access control plug-in. for example to automatically close alarms in the access control system. The value in this field helps map the user-friendly value in the Reason field to a value better suited for access-control plug-in integration. The field value does not need to be unique. Field restrictions
|