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

Previous page Configuring the Monitoring fault tolerance  Data Loader for Monitoring Next page


On this page:

General information about special mode of Monitoring operation with ACFA Intellect

The special mode of Monitoring operation with ACFA Intellect allows to provide access to the object with the installed Agent Of Control using the user's access card, and to monitor the object status on the Server Of Control. This operating mode is relevant if the Monitoring and ACFA Intellect are not combined into a single system with a distributed architecture.

Configuring the special mode of Monitoring operation with ACFA Intellect on the Server Of Control side

The special mode of Monitoring operation with ACFA Intellect is configured on the Server Of Control side as follows:

  1. Create an AccessByCardEnable string registry key and set 1 as its value (for details, see Registry keys reference guide, for more information about working with the registry, see Working with Windows OS registry).
  2. Create the necessary number of access levels, which include one or more Partitions Of Control of the corresponding Agent Of Control objects, the access to which should be obtained. Do it as dollows:
    1. In the System Settings dialog box, go to the Programming tab (1).
    2. In the object tree, create an Access Level object (2) on the basis of the Access Levels object.
    3. On the settings panel of this object, specify one or more access points to which the Partitions Of Control on Server Of Control correspond (3).
    4. Click Apply (4).

  3. Create the necessary number of users who will be able to access objects, and assign an access card and access level to each user. Do it as dollows:

    1. In the System Settings dialog box, go to the Users tab (1).

    2. In the object tree, create a Department object (2), and then create a User object (3) on its basis.
    3. On the settings panel of the User object, specify the following parameters:
      1. In the field (4) enter the last name of the user.
      2. In the Name field (5), enter the first name of the user.
      3. In the Patronymic field (6), enter the middle name of the user.
      4. In the Object code field (7), enter the room code.

      5. In the Permanent card field (8) enter the card number.

        Attention!

        Both Object code and Permanent card fields should be filled in.

      6. If necessary, in the Valid til field (9), specify the date upon which access to the object will be restricted.

      7. Go to the Access Levels tab (10) and assign a previously created access level to the user (see step 2).

      8. Click Apply (11).

    Note

    Similar actions can also be performed using the Access Manager module, which is part of the ACFA Intellect software package (see Working with the Access Manager software module).

Configuring the special mode of Monitoring operation with ACFA Intellect on the Server Of Control side is complete.

Configuring the special mode of Monitoring operation with ACFA Intellect on the Agent Of Control side

The special mode of Monitoring operation with ACFA Intellect is configured on the Agent Of Control side as follows:

  1. Create an AccessByCardEnable string registry key and set 1 as its value (for details, see Registry keys reference guide, for more information about working with the registry, see Working with Windows OS registry).

  2. Install ACFA Intellect (see ACFA Intellect Installation Guide).

    Attention!

    The following is an example of configuring the interaction between the Monitoring and the Rovalant (A6, A16) integration module, which is part of the ACFA Intellect software package. The configuration guide for the Rovalant (A6, A16) integration module is available only in the Russian documentation for ACFA Intellect. Instead of the Rovalant (A6, A16) integration module, you can use any other integration module that supports user entry into the controller.

  3. Configure the Rovalant (A6, A16) integration module.

  4. In the System Settings dialog box, go to the Programming tab (1).

  5. To transfer the user data from the Server Of Control side to the Agent Of Control side, it is necessary to create script №1 in the object tree on the basis of the Scripts object (2) by copying the contents of an example of this script (see Sample script for configuring the interaction between the Monitoring and the Rovalant (A6, A16) integration module).

  6. To monitor the object status on the Server Of Control side, it is necessary to configure the alarm group (see Configuring alarms for monitoring the object state on the Agent Of Control side). As a result of this configuration, the script №2 will be created.

    Attention!

    If an integration module other than Rovalant (A6, A16) is used, it is necessary to modify the script examples for the corresponding integration module.

    Note

    For more information on creating scripts, see The Script object. Programming using the JScript language.

  7. Click Apply (3).

Configuring the special mode of Monitoring operation with ACFA Intellect on the Agent Of Control side is complete.

Operating procedure

At startup, and then every 15 minutes, Agent Of Control sends the hash of existing users to Server Of Control. Initially, there are no such users. At startup, Server Of Control receives the hash of all objects including users from the Intellect core, and puts them in a list that is updated if objects are edited or deleted. Server Of Control compares the user hash received from Agent Of Control with the value from the list and, if there is a mismatch, requests new data, and then transfers it to Agent Of Control. Agent Of Control, upon receiving this data (hash + configuration), updates the information about the users and generates the SPR_DATA_UPDATED event, which is processed in script №1. As a result, the users with the right to access the corresponding Agent Of Control will be loaded into the memory of the Rovalant (A6, A16) controller and will be able to access the object upon presenting of their access card.

Also at startup, and then every 15 minutes, Agent Of Control sends a GET_OBJECT_STATE event to the Intellect core. This event is processed in script №2, which generates an OBJECT_STATE_INFO event with the object status in the state field and the user's access card number used when arming/disarming the object in the card field. When arming an object using the user's access card, this script generates an OBJ_ARM event (alarm type: Armed object). When disarming an object using the user's access card, the same script generates the OBJ_DISARM event (alarm type: Attention! Service personnel are working!) and activates a long alarm Object disarmed.

Note

Only the user access card numbers are stored on the Agent Of Control side, the users' full names are not available. Therefore, in order to obtain the users' full names by the access card numbers, Server Of Control queries the Intellect database on the Server Of Control side.

As a result, when the access to an object is received, the access card number and the full name of the user who gained the access is displayed in the Event log as an additional information (see Event log).

  • No labels