Bolid ACS#
Hardware and software integration required for communication between the LP5/CBS and the Bolid ACS software to ensure control of the connected device (C-2000 series devices or other devices compatible with the Bolid software).
Supports Bolid version 1.20.3, Orion Pro integration module version 1.4.
Information interaction is provided through the Orion Pro automated workplace software.
The Orion PRO licensed integration module must be installed and launched.
The integration module is a SOAP web service accessed via the HTTP/HTTPS protocols. The description of the web service complies with the WSDL version 2.0 specification.
The service runs under Windows 7/8/8.1/10 (32 bit or 64 bit).
Supported integration options for Bolid ACS#
The face recognition device generates an event, Access passes the event to LP5, LP5 processes the event and returns the result to Access for further processing.
User data is transferred from ACS to LP5 using two mechanisms:
- replication - the mechanism for the initial transfer of user data;
- synchronization - the mechanism for periodic transfer of user data when the composition/data of users changes.
For the synchronization/replication settings, see the service settings.
Each integration with LP5 (Table 40) uses the Luna service.
If the terminal does not have data output means (for example, a screen), the SendToDevice pipeline is not required.
Table 40. LP5 integration options
Each integration with CBS (Table 41) uses the CBS service.
Table 41. CBS integration options
Standard integration using Bolid#
When integrating with Bolid, standard Access components (Figure 66) and (Table 42) are used.
When using 1f integration (without a card) components, transferring the card number to Access is not required.
Table 42. Integration description
| Component | Description |
|---|---|
| Person | A person wishing to pass through a passage point. |
| Passage point | A set of components used to control human access. More than one passage point can be connected, limited by the ACS license. A passage point can be used for both entry and exit. Each direction uses its own reader and video data source. |
| Reader | A device for receiving access card data. |
| Controller | A passage point control board. |
| Turnstile | A barrier device for access control |
| Bolid ACS | Central software for working with Bolid. Stores employee data and makes a decision on granting access. |
| Bolid Service | Access component for exchanging data with ACS |
| GateController | Access component for interacting with the ACS controller. |
| BS Service | Access component for interaction with the BS: for LP5 it is Luna, for CBS - the corresponding CBS service. |
| Video data source | A device for extracting a frame of a person's face. It can be either a biometric terminal (LUNA FAST 4A1 and others) or a camera connected via FaceStream. |
| Device ... | An Access component for receiving data from a video data source. Selected based on the device used. |
| Custom2FA Pipeline | Access Component implementing the logic when working in 2f mode. |
| MatchByPhoto Pipeline | Access Component for interaction with CBS. When working with a biometric terminal, it is necessary to additionally connect the SendToDevice pipeline |
| SendToController Pipeline | Access Component for interaction with CBS |
Setting Bolid ACS#
Preparatory actions with Orion Pro software#
To launch and configure Bolid, you need to perform preparatory steps with the Orion Pro software:
1․ Launch the Orion Pro Central Server application.
2․ Launch the Orion Shell application.
3․ Launch the ADB module on the Orion Shell panel (Figure 67):
4․ Launch the Orion Pro Integration Module.
5․ Launch the Operational Tasks (OT) on the Orion Shell panel if they do not start automatically.
Adding an employee in Orion Pro#
1․ Add a new employee. Fill in the required fields (Figure 68) according to the rules for creating employees at the facility:
2․ Go to the Employees section
3․ Click the "add" button
4․ Fill in the required employee fields
Select the "Administrator" status, or another department with employees who have full access to the system.
5․ Add the "Maximum" access level to the new user and set a password (Figure 69).
6․ Go to the Access section;
7․ Click Add;
8․ Select the desired employee, enter the password
9․ Select the Maximum access level
Adding devices to Orion Pro#
1․ Add a new section (Figure 70):
2․ Select the "System structure" tab;
3․ Select "sections";
4․ Select all "Sections";
5․ Add a new section with standard parameters and name it.
6․ Link devices to the newly created section (Figure 71):
7․ Select a section.
8․ Click the "Add" button.
9․ Go to the list of devices and select the required ones (Figure 72):
10․ Select it and click the [>>] button to move it to the active field;
11․ Confirm the changes by clicking [OK];
12․ Click the "Save" button.
13․ Edit the orion.ini file in the folder with the installed Orion Pro application (located by default: C:\BOLID\ARM_ORION_PRO1_20_3), adding the following parameters (if they are missing):
[Checkerdb]
Remarks=1
timechecker=5
Logon=1
RemoteCmd=1
CmdOn=1
[ChangeDB]
on=1
14․ Restart all Orion Pro applications.
Configuring the “ORION PRO INTEGRATION MODULE” application#
To configure the “ORION PRO INTEGRATION MODULE” application, follow these steps:
1․ Download the official distribution kit of the “ORION PRO INTEGRATION MODULE” application (link).
2․ Run the installation. After the installation is complete, launch the module, check the database connection settings. If everything works correctly, close the module.
3․ Install the module to run as a service. To do this, run the command in the terminal as administrator in the folder with the installed module (for example: C:\BOLID\IntegrServ):
IntegrServ.exe /INSTALL
4․ In the system control panel, find the installed service and run it by clicking the right mouse button and selecting “Start” (Figure 73).
Methods of interaction with Bolid#
An API is used тo exchange data with the ACS (Table 43).
Table 43. Bolid methods
| Task | Operation | Description |
|---|---|---|
| Get information about ACS | GetServiceInfo | Get ACS version to check compatibility and display in UI. Check ACS availability (every minute). |
| Get authorization status | GetDbChangeLogItemsCount | Get the status of correct login/password entry for an account in ACS. |
| Log in | GetLoginToken | Authorization of Access in ACS. Authorization occurs when adding a service and before token expiration (10 minutes) |
| Extend token | ExtendTokenExpiration | When executing requests, the token lifetime is checked. The request is executed if the token lifetime is about to expire |
| Get employees | GetPersons | Replication and synchronization of employees (person_id, full name, status, photo, date and time of the last update) from the ACS to the local storage. Iteratively by 500 rows. |
| Get employee information | GetPersonById | Getting employee data from the ACS (person_id, full name, status, photo, date and time of the last update) |
| Get card number | GetKeys | Getting PROXIMITY cards for all employees. The most recent ones are selected for each employee |
| Get events | GetDbChangeLogItemsCount | Getting employee events (adding, changing or deleting) every 5 seconds. |
Bolid Interaction Process Diagrams#
Bolid Service Connection#
Sequence diagram (Figure 74).
1․ The user added the Bolid service to Access. 2․ Access sends a request to obtain information about the ACS. 3․ The ACS returns information. Access checks the availability of the ACS and uses the ACS version to check compatibility and user information in the UI. 4․ Access sends a request for the correctness of the login/password pair from the account in the ACS. 5․ The ACS returns the account activity status. If the record is active, then work continues. 6․ Access sends an authorization request to the ACS. 7․ The ACS returns a token for authorization. The token has a lifetime, after which Access re-performs authorization. 8․ Access sends a request to obtain information about employees to replicate data to the local storage. 9․ The ACS returns person_id, full name, status, photo, date and time of the last update. 10․ Access sends a request with employee photos to the BS to retrieve descriptor_id (face_id). 11․ The BS returns descriptor_id. 12․ Access saves information on each employee in local storage.
Event processing with 1 factor#
Sequence diagram (Figure 75).
1․ Employee at the biometric terminal at the checkpoint. 2․ The terminal sends the best shot of the employee to Access. 3․ Access sends a photo of the employee to the Biometric System (BS). 4․ BS compares the photo from the terminal and the one saved in the database. 5․ BS returns descriptor_id to Access. 6․ Access looks for the employee's card number by correlating descriptor_id and person_id. 7․ Access sends the card number to GateController. 8․ GateController sends the card number to ACS. 9․ ACS makes a decision to allow the employee through.
Event processing with 2 factors#
Sequence diagram (Figure 76).
1․ Employee at the biometric terminal at the checkpoint. 2․ The terminal sends the best shot of the employee to Access. 3․ Access sends the employee's photo to the Biometric System. 4․ The BS compares the photo from the terminal and the one saved in the database. 5․ The BS returns the descriptor_id to Access. 6․ Access looks for the employee's card number by correlating the descriptor_id and person_id. 7․ The employee applies the card (the card use subprocess does not depend on photo processing, but, as a rule, the photo arrives first). 8․ The ACS sends the card number to Access. 9․ Access compares the card numbers received in steps 6 and 8. 10․ Access sends the card number to the GateController. 11․ GateController sends the card number to the ACS. 12․ The ACS makes a decision to open.
Bolid FAQ#
1․ Why can't I add an employee photo larger than 100 kb?
- In Orion Pro, the maximum permissible photo size may be reset to 100 kb. You need to go to ADB Orion Pro Settings > Settings > Employees > "Maximum size of employee photos, kb" and set it to 10240 kb (10 MB) or more.