Parsec timesheets, lateness and passes right in the chat

The agent works with the ParsecNET 3 integration service, which is installed on the access control server with the system. The connection takes the server address (port 10101 by default), the organisation and a ParsecNET operator. The service answers with that operator's rights: whatever the operator cannot see in Parsec, the agent cannot see either. The server usually sits on a local network, so requests go through your computer with the app running.

Timesheets and lateness are computed from the event archive: the agent opens a report for the period filtered by pass types, reads it in portions and closes it. For each employee and day it takes the first entry and the last exit and compares them with the intervals of the worktime schedule. A report without an explicit limit is cut by the server at five thousand events, so the agent sets the limit itself and checks the event count against the total.

Issuing a pass follows the same path as the Parsec application: the employee is created in a department, an editing session of their card is opened, and a card with an access group is issued in it. The agent shows every write in advance and performs it after your confirmation.

Opening a door, disarming and other hardware commands change physical access on site, so the agent sends them only on a separate explicit request for a specific door. The Parsec server can deliver event subscriptions only to an address on its own network, so the agent reads fresh events by polling the archive.