For the Access Control and Detection Tools alarm groups, by default 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 (Fig. 4.3 – 4.3—15) 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.
Fig. 4.3 – 4.3—15 Detector Zone object
To associate various events with particular alarm groups:

  1. Go to the configuration panel for the Partition Of Control object (Fig. 4.3 – 4.3—16).


Fig. 4.3 – 4.3—16 Monitoring button...

  1. Click the Monitoring button (see Fig. 4.3 – 4.3—16). The Add/Remove Monitoring Events window opens (Fig. 4.3 – 4.3—17).


Fig. 4.3 – 4.3—17 Adding/removing events for Monitoring

  1. To add an event, click the Add... button (see Fig. 4.3 – 4.3—17). The event configuration window opens (Fig. 4.3 – 4.3—18).


Fig. 4.3 – 4.3—18 Event configuration

  1. In the form that appears, in the Type drop-down list, select the type of device (see Fig. 4.3 – 4.3—18, 1). 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.

  1. Select an ID number for the object of the selected type from which you want to get events (see Fig. 4.3 – 4.3—18, 2). If you want to get events from all devices of this type, leave this field blank.
  2. In the Event drop-down list, select an event type (see Fig. 4.3 – 4.3—18, 3). The available event types depend on the selected object type.
  3. In the Alarm group drop-down list, select an alarm group and indicate in which alarm group you want for Monitoring to display alarms for this event (see Fig. 4.3 – 4.3—18, 4).
  4. Enter text in the Message field (see Fig. 4.3 – 4.3—18, 5). The text entered in this field will appear in the Device column of the Alarm Reaction dialog form (see the document Monitoring Software Package: Operator's Guide).
  5. To search for additional information in messages from a device of this type (for the substring "param0<>"), select the Intercept detail check box (see Fig. 4.3 – 4.3—18, 6).

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 Intercept detail, the following text may appear in the Device column of the Alarm Reaction dialog form: "Motherboard (CPU cooler)".
Example of how to configure the message for the Abandoned Object Detection Tool (Fig. 4.3 – 4.3—19).
Fig. 4.3 – 4.3—19 Configuring message for the Abandoned Object Detection Tool
In the example shown with the Abandoned Object Detection Tool, when the detection tool is triggered a indicator corresponding to the Detection Tools alarm group becomes red in the Control Panel (Fig. 4.3 – 4.3—20).
Fig. 4.3 – 4.3—20 Reaction to triggering of detection tool in the Control Panel
Click this indicator to view the Alarm Reaction window, which indicates that the Abandoned Object Detection Tool has been triggered (Fig. 4.3 – 4.3—21).
Fig. 4.3 – 4.3—21 Alarm Reaction window for the Abandoned Object Detection Tool
Similarly, it is possible to monitor messages from other objects created in the Intellect device tree, on the Hardware tab.
Configuration for associating different events with certain alarm groups is now complete.