Integration list#
Supported components#
Access allows you to add the following components to integrations (Table 3):
Table 1. Supported Components
| Type | Supported | Comments |
|---|---|---|
| VisionLabs software | LUNA PLATFORM | 5.10 or newer |
| LUNA CARS | Installer v.2.1.16 and up. The call is made to LUNA CARS Analytics | |
| FaceStream | 5.1.6 or newer | |
| ACS | APACS, Sigur, Bastion, Bolid, Parsec, PercoWeb, Strazh, RusGuard, Gate, Salto and Bars-X | Integration with BARS-X accurse with only pipeline |
| Devise | VisionLabs | Terminal: LUNA ACE, LUNA Fast 4A1, LUNA Fast 8A1 |
| Beward | Terminals: TFR80-210T1Q, TFR80-210 | |
| BioSmart | Terminal: Quasar | |
| Dahua | Camera: Camera | |
| Thermal camera: Thermo | ||
| Fortuna | Thermal camera: F315 | |
| Hikvision | Camera: DS-2CD3126G2-IS | |
| Terminals/Thermal camera: DS-K1TA70MI-T, DS-K1T671TM-3XF, DS-K5671-3XF/ZU | ||
| Terminals: DS-K1T341AMF, DS-K1T341AM, DS-K1T680D-E1 | ||
| Sunell | Thermal camera: SN-T5 (Panda) | |
| Uni-Ubi | Terminal/Thermal camera: Uface 8-C temp, Uface 8T - temp | |
| Hi-Tech Security | Terminal: VK-Vision-01 | |
| R20Face | Terminal: R20-Face-T8 |
Services version matching#
Access supports the following services and firmware versions(Table 4):
Table 2. Supported external services
| Name in Access | Name | Version | Comment |
|---|---|---|---|
| Apacs | APACS 3000 | 8.3.1.0 update 18 | |
| Bastion 2 | Elsys Bastion-2 | 2.1.11.2337 and up | |
| Bastion 3 | Elsys Bastion-3 | 0.23.3-17064 | |
| Bolid | Bolid-Orion Pro | 1.20.3 (build 11940) | |
| CbsMts | CBS MTS | - | |
| CbsAlpha | CBS Alpha | - | |
| LunaStreams | VisionLabs FaceStream | from 4.0 to 5.1.42 | |
| Gate | Gate | 1.22.95 | |
| Luna | VisionLabs LUNA PLATFORM | 5.10 and up | |
| LunaAceConverter | LUNA ACE | 1.2.23 | |
| LunaCars | VisionLabs LUNA CARS | ||
| LUNA CARS Installer | v.2.1.16 and up | ||
| LUNA CARS API | v.1.1.13 and up | ||
| LUNA CARS Stream | v.2.0.19 and up | ||
| LUNA CARS Analytics backend | v.3.0.28 and up | ||
| LUNA CARS Analytics frontend | v.2.0.12 and up | ||
| Parsec | Parsec (ParsecNet3) | 3.11.629 39 and up | |
| PercoWeb | PERCo-Web 2.0 | 4.30 | |
| Rusguard | RusGuard | 3.3.1 | |
| RusguardCBS | RusGuardCBS | 3.3.1 | |
| Salto | Salto | 6.6.3.0 | |
| Package 6.6.3.94 | |||
| Service 4.23.3.595 | |||
| Sigur | Sigur | 1.1.1.9.s and up | |
| SigurThroughDatabase | Sigur | 1.1.1.9.s and up | |
| Sigur WEB | Sigur | 1.2.0.5 | |
| Strazh | Rubezh Strazh | 1.2.211201.648 |
Device version matching#
Access supports the following devices and firmware versions (Table 5):
Table 3. Supported devices
| Device | Type | Version |
|---|---|---|
| Beward | TFR80-210T1Q, TFR80-210 | 1.2.13.0, 2.1.6.0 |
| BioSmart | BioSmart Quasar | 2.3.0.46 |
| DahuaThermo | - | 2.631.0000000.31.T |
| Fortuna315 | - | Camera: V4.02.00, Thermal imager: 2.20.0.0.R26130.alpha8, Hardware versions: V1.0, Versions of the algorithm: smart2.0.0-06-2020.06.17.16:06:42 |
| HikvisionCamera | DS-2CD3126G2-IS | V5.5.134 build 200430 |
| HikvisionCameraThermo | DS-2TD2617B-3/PA | V5.5.26 build 200317 |
| HikvisionRecognitionOnBoard | DS-K1T341AMF, DS-K1T341AM, DS-K1T680D-E1 | V3.2.30 build 220210 |
| HikvisionTerminalThermo | DS-K1TA70MI-T, DS-K1T671TM-3XF, DS-K5671-3XF/ZU | V3.2.32 build 210525 |
| LunaFast4A1 | DS-K1T680D-E1, DS-K1T341AMF, DS-K1T341AM, VL LUNA FAST 4A1, VL LUNA FAST 8A1, 671, DS-K1T671M, ACT-T1341M, DS-K1T680DF-E1, DS-K5671-ZU | V3.2.30 build 210415, V3.2.30 build 210525, V3.2.30 build 210526, V3.2.30 build 210812, V3.2.30 build 211025, V3.2.30 build 220607, V3.2.30 build 220803, V3.2.30 build 221027, V3.2.33 build 210816, V3.2.35 build 220415, V3.2.35 build 220817 |
| Panda | SN-T5/13, SN-F22-13 | v3.6.0825.1004.1.0.23.0.0, v3.6.0840.1004.1.45.1.0.2 |
| R20Face | R20-Face-T8 | GD-V31.6222, GD-V32.7267 |
| UniUbi | Uface 8-C temp, Uface 8T - temp, R20-Face-T8 | GD-V30.7219, GD-V32.7247, GD-V32.7267 |
| VKVision02 | VANCOR VK VISION 02 | v2156 |
| Controllers | ||
| Gate 8000 Ethernet | - | 8216/003 (4.06) |
| SigurController E900U | - | 37 |
| Strazh STR20-IP | - | 1.2.211201.648 |
| Strazh Rubezh STR20-IP | - | 0.21.1 |
| Strazh Rubezh STR1-AP | - | 0.33.2 |
| Bolid C2000-Ethernet | - | 2.60 |
| Bolid C2000-2 | - | 2.20, 2.50 |
| RusGuard ACS-103-CE | - | 6.20 |
| RusGuard ACS-102-CE V2.0 | - | 7.46 |
| Parsec NC-8000 | - | 3.8 |
| Parsec NC-60-K | - | 1.4 |
| Bastion Elsys MB-NET | - | 2.13 |
| Bastion Elsys MB-light | - | 2.74 |
| Bastion Elsys NG-800 | - | 4.11 |
| PercoController CTL14 | - | 2.2.37 |
| PercoController CT/L04.2 | - | 3.0.0.78; 3.0.0.79; 3.0.0.81 |
| Laurent-2 | - | L213 |
| UCM-2A | - | 6103 |
| AAM-LAN-8W | - | Only for APACS. |
| APOLLO AAN-100/AAN-32S/AAN-32N | - | Only for APACS. |
| Converters | ||
| Gate Ethernet/Wiegand | - | 04.06, 1.3.2003 |
| Gate 8000 Ethernet | - | 8216/003 (4.06) |
| S4A Wiegand to TCP/IP | - | 6005 |
Integration options#
Vehicle ACS#
Vehicle ACS - System for controlling access to the territory of vehicles using a barrier.
LUNA CARS transfers vehicle detection events to Access for further processing.
Each integration (Table 6) uses the LunaCars service.
Cameras are connected via LUNA CARS.
Table 4. Options for integrating the vehicle access control system
| Additional service | Pipeline |
|---|---|
| Sigur | SendCarsToSigur |
| LaurentController | SendCarsToLaurent |
Human ACS#
The facial 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 - a mechanism for the initial transfer of user data;
- synchronization - a mechanism for periodically transferring user data when the number of/data of users changes.
To configure synchronization/replication, see the service settings.
Each integration (Table 7) uses the Luna service.
Table 5. Options for integrating people's ACS
CBS#
The facial recognition device generates an event, Access passes the event to the CBS, the CBS processes the event and returns the result to Access for further processing.
Obtaining data from CBS in integrations (Table 8) users occurs using two mechanisms:
- replication - a mechanism for the initial transfer of user data from CBS to Access;
- synchronization - a mechanism for periodically transferring data from the CBS to Access when the number of/data of users changes.
To configure synchronization/replication, see the service settings.
Table 6. Integration options with CBS