Employees, passes and the access log of Orion Pro right in the chat
Connect the Bolid Orion Pro access control system to the AI agent: employees, passes, access levels and the pass log. The agent computes timesheets and lateness.
How the agent works with Орион Про
The agent works with the Orion Pro integration module, a separate paid Bolid program installed next to АРМ Orion Pro that reads its database directly. The exchange runs over JSON-RPC: employees and visitors, keys of every kind (cards, PINs, fingerprints, faces, QR), access levels with time windows, company and department directories, devices and zones, the event log.
The access control server sits in your local network, so the agent reaches it through the app on your computer, the same way it reaches an on-premise 1C. While the computer is on and can see the server, the agent works with it directly; a refused connection is reported as a network failure, not as missing data.
The agent reads the log in pages for a period or from the last event it read, so long exports never stop silently. It builds a timesheet from the pass direction rather than from any event, and checks holidays, vacations and sick leave against the absence reasons stored in Orion.
For writes the agent creates and edits employees, issues and blocks keys and edits access levels, each time showing what it will write and waiting for your confirmation. Deleting from the database cannot be undone, so by default a dismissed employee is archived or blocked. Door and alarm control happens only on your direct request, naming the door or zone and the consequence.
Integration scenarios
A timesheet from door events
The agent collects each employee's first entry and last exit per day from the log and shows late arrivals and early leaves against the schedule you name.
A pass for a new hire
The agent creates the employee card, binds the card and access level in one call and shows exactly what it will write before you confirm.
A lost card
The agent finds the employee by surname or personnel number, shows their keys and blocks the right card, leaving the others alone.
Who was where
The agent pulls the passes through the doors you choose for a period and names who entered the room and when.
Denied access
The agent goes through denied events and names the reason for each: no rights, an expired card, an antipassback or time window violation.
Reconciling with HR records
The agent compares the Orion employee list with an export from your HR system and shows dismissed people who still hold active cards.
Орион Про examples
За неделю 7 опозданий у 4 сотрудников, в сумме 2 ч 05 мин.
- 3 из 7 опозданий у одного сотрудника, в среднем по 24 минуты
- В 2 днях нет события выхода: дверь пропустила выход, это не переработка
Считал только проходы с направлением входа и без отказа доступа, а время сверил с журналом АРМ по одному известному проходу.
How to connect
Before you connect
- The Orion Pro integration module (bought from Bolid separately)
- АРМ Orion Pro 1.12 or later, 1.20.3 or later for door control
- A computer with the app in the same network as the module server
- A Remote control password in the access database for door control
- 1
Install the Orion Pro integration module
The module is bought from Bolid separately and installed next to АРМ Orion Pro: unpack IntegrServ.zip and run integrServ.exe, preferably as a service.
- 2
Check the module's settings.ini
In settings.ini set the Orion database in [DBMS] and the port in [Sockets] (ListenPort=8090). The [HttpAuth] login and password matter only if IsNeedAuth=1.
- 3
Create a remote control password
For doors, alarms and secondary authorization add a password of the Remote control type on the Passwords tab of the access database. АРМ 1.20.3+ is required.
- 4
Open the module port on the site network
The computer you connect from must see the module server: allow port 8090 (8091 for HTTPS) in Windows Firewall on the server.
FAQ
With the integration module address and port (http://server-address:8090 by default). If primary authorization is on in the module's settings.ini, add its login and password; for door control and when secondary authorization is on, add the remote control login and password from the access database.
Employees and visitors, their keys and access levels, doors, zones and devices, the event log with passes and alarms, and absence reasons. The module serves no time tracking reports: the agent computes the timesheet itself from the pass log.
It can when the connection carries a remote control password and АРМ is 1.20.3 or later, but only on your direct request and after confirmation: it is a physical action on site.
The module pushes events only to an address inside your network and cannot reach the cloud. So the agent picks up new events by polling the log from the last one it read.