VECTA Subsystems

Permissions

Any operation with configuration object is checked for operator rights. If the operator doesn’t have the right for executing such operation on this object, this operation will be declined or prohibited.

The following types of rights can be controlled for all the objects:

Viewing object – the operator can view the object in the configuration tree and receive messages about events from the object
Editing object – the operator can edit object settings
Deleting object – the operator can delete the object
Editing permissions for object – the operator can edit object permission settings
Adding an object to object – the operator can add subobjects to the object
Control commands executing – the operator can issue control commands on the object
Register events from object – the operator can register events coming from the object

Rights Control is processing on Server, therefore permission subsystem reliability increases. Rights Inheritance from the parent objects to subobjects can be used for operator rights definition (this is made to avoid the situation when same rights are assigned to different objects). High productivity and fast right configuration process are achieved by means of settings inheritance. Objects, used in Cardholder Configuration application (Cardholder, Card, Issue, Global Access Level), are subobjects for Folder object in Cardholder Configuration.

Once rights for Folder of Cardholder Configuration are assigned and Rights Inheritance is used, the operator can get the rights for working with all objects in Cardholder Configuration. Therefore, integrity of rights subsystem of any object is achieved.

Audit of operator’s actions

VECTA ACS has an audit subsystem, designed for controlling operator’s actions on the system objects. All the operator’s actions on the configuration objects can be stored as events in the database, setting the fact of any command execution.

The main Audit feature is that conditions of operator’s actions control can be established:

In case of successful command execution
In case of unsuccessful command execution
In case of both successful and unsuccessful command execution

Same rights subsystem, audit subsystem works on server and can also use audit settings inheritance for subobjects.

Selective audit settings allow storing important actions on configuration objects and not creating needless events in database.

All audit events can be easily received in Reporter application.

Event Acknowledgment

Some configuration object events can be so important, that it’s necessary to have a mode, helping duty operator to acknowledge such events, and write down own comments on this event. That is why application suite allows setting the Event Acknowledgment subsystem. This subsystem helps to point a group of events, received from definite system objects, and helps to select operator, who must acknowledge the events receipt.

The acknowledgement window view and its work modes can be adapted to a concrete operator. Comment entry obligation and opportunity of running other windows can be selected, while unconfirmed events exist.

Automation

A new Automation subsystem, which allows configuring non-standard operation algorithms necessary for concrete object of access control system, is used in VECTA ACS application suite. Automation allows determining the system reactions to definite events and executing control commands on object or group of objects.

The following functions can be realized by means of Automation:

Sound alert on system events
Playing video from the video capture card
Compound algorithms of equipment control and etc.

Automation subsystem supports VBScript script-writing. Accordingly, system administrator can use all the VBScript opportunities for writing scripts: arrays, control operators, object properties enumeration, string operation functions, error handling. As a result suite is easily adapted to concrete ACS requirements, because administrator can create various automation scripts.

Automation accesses COM-objects by means of script and this allows using opportunities of different applications. For example, using opportunities of Microsoft Office applications, interactive event and object reports can be composed in MS Word and MS Excel. Conditions, which are used for checking up events, and sequence of system operations are defined by one script. After script is loaded, it’s executed automatically by system and doesn’t need duty operator. This script is called as response script.

As script allows issuing commands to a system object, administrator can issue his own control commands to objects or group of objects. Command execution is determined by operator. Scripts, which are used for issuing commands to system object or group of objects and executed by operator decision, will be called as macro.

Macros, specified by administrator, are displayed as Automation shortcut menu items in the main menu of Alarm Mode application. Operator selects correct macro and command is executed in system.

For example, all the system readers must be switched to an Open Mode at a certain situation. In order to not execute Open command at every single reader, macro can be issued. And its execution will make all readers switch to the open mode. Therefore, duty operator has the opportunity for fast reaction to events, happening in the system, and controls it.