Configuration for associating events with certain alarm groups

By default, for the Access Control and Detection Tools alarm groups, no data is sent from Agent of Control. These alarm groups, as well as Hardware and Fire/Security System, can be used for designating their respective alarm types.

To classify events of an object as belonging to a particular alarm group, create an object (if it does not exist already) in the device tree. For example, if you want for the signal from the Abandoned Object Detection Tool to be displayed in Monitoring in the Detection Tools alarm group, create a Detector Zone object and configure it (select the Abandoned Object Detection Tool type, specify the detection area and sensitivity, etc.; for more details, see the document Intellect Software Package: Administrator's Guide.

To associate the events with particular alarm groups, do the following:

Go to the configuration panel for the Partition Of Control object.
Click the Monitoring... button. The Add/Edit events for Monitoring window opens.
To add an event, click the Add... button. The event configuration window opens.
In the form that appears, from the Type drop-down list (1), select the type of device. This list contains the types of all objects created on the Hardware tab of the System settings window that have recorded events.
Example: In the case of the Abandoned Object Detection Tool, select the Detector Zone type.
From the Number drop-down list (2), select an ID number for the object of the selected type from which you want to get events. If you want to get events from all devices of this type, leave this field blank.
From the Event drop-down list (3), select the event type. The available event types depend on the selected object type. System type of the event in brackets is for use in scripts and programs (see Guide for creating scripts (programming) and The Script object. Programming using the JScript language).
For example, for the Abandoned Object Detection Tool triggering event, select Alarm in the zone (MD_START).
From the Group of alarms drop-down list (4), select an alarm group and indicate in which alarm group you want for Monitoring to display alarms for this event.
It is possible to get confirmation of alarm acceptance from the Server of Control. To do this, from the Confirmation drop-down list (5), select the type of confirmation:
1. No – no confirmation is sent.
2. Simple – Agent of Control sends confirmation when an alarm is confirmed by the operator.
1. Complex – when accepting an alarm the operator must confirm it in the confirm box and after that the confirmation is sent.
Note.
- The Agent of Control sends the "Confirmed: Monitoring event" message to Intellect core when there is the confirmation of alarm acceptance on the Server of Control. Scripts that use this event can be created in Intellect – see Sample scripts for processing alarm confirmations.
- Confirmation sending can be disabled on the side of the Server of Control – see Sending confirmations of alarm acceptance.
If it is necessary to attach video data to alarms, click the Video data button (6). As a result, the Select configurations for video data transmitted window will open.
Note
Configuration of the transmitted video data is described in the section Setting up the configurations for transferred video data
1. Move the required configurations using the button (1) from the left list to the right. Remove a configuration from the right list to the left one by using the button (2).
  Attention!
  Multiple configurations cannot be used for the same camera.
2. Click the Apply changes and close button (3). The selected configurations will be listed in the non-editable Video data field.
In the Message field (7), enter the text message, that will appear in the Device column of the Alarm Reaction dialog form (see the document Monitoring Software Package: Operator's Guide).
If the object identifier is not specified, the following variables can be used in the Message field to detail the message:
1. <id> – identifier of the object from which the event came.
2. <name> – the object name.
  Attention!
  <id> and <name> are to be in lower case.
  After substitution of variables values the message must not be longer than 60 characters. If the resulting message is longer, extra characters will be dropped.
  Example.
  When the Disarmed event appears at the Camera 1, the “Camera 1 disarmed” message is sent.
To search for additional information in messages from a device of this type (for the substring "param0<>"), select the Capture detailed data check box (8).
Click OK to save changes (9).

This means that when integrating a new device into Intellect, if a developer wants to be able to send more detailed information to Monitoring, when generating an event from the device, the developer should add detail in the param0<> parameter. For example, if there is a Motherboard Control module that has the Alarm event, the following values could be included in param0<>: "processor cooler", "BIOS battery", etc. If you enter "Motherboard" in the Message field and select Capture detailed data, the following text may appear in the Device column of the Alarm Reaction dialog form: "Motherboard (CPU cooler)".

Similarly, it is possible to monitor messages from other objects created in the Intellect device tree, on the Hardware tab.

Configuration for associating events with certain alarm groups is now complete.

Page tree

Documentation for Monitoring 12.0. Documentation for other versions of Monitoring is available too.