Biometric Device Management
Aiden connects to the biometric readers Pakistani businesses already own — ZKTeco over ADMS push and Oculus over WebSocket — maps device users to employees, and recovers punches when a connection drops.
What it does
- ZKTeco ADMS push and Oculus WebSocket protocols
- Device user mapping and roster sync
- Offline log import for disconnected sites
- Punch recovery for connection outages
Two protocols, handled properly
ZKTeco and Oculus devices speak entirely different languages, and treating them the same is how attendance silently stops. Aiden routes each device to its own protocol subsystem based on the brand and connection mode recorded against it: ZKTeco pushes over HTTP to the ADMS endpoints, Oculus maintains a persistent WebSocket connection.
Mapping people to fingerprints
Every punch carries a device enrolment ID, not a name. Aiden keeps a mapping between device users and employees, and treats the device as the authority on what is enrolled: a punch from an unknown enrolment creates a pending device user rather than being discarded, so nothing is lost while mapping catches up.
Employees are never created by a device — only the import wizard creates people — which prevents a misconfigured reader from populating your HR system with phantom staff.
When the line drops
Connectivity in an industrial area is not guaranteed. Devices buffer, and Aiden can pull historical logs for a date range to backfill a gap, or import an exported log file from a site that has no connection at all. Unmapped punches are staged and converted automatically once the mapping appears.
Moving servers without losing attendance
Push-mode devices hold the server address in their own configuration. If the platform moves and the readers are not re-pointed on site, they keep pushing into the void — and attendance stops silently, which is the worst kind of failure because nobody notices until payroll.
Aiden records each device's connection mode so a migration plan can list exactly which readers need a physical visit and which will reconnect on their own.
Recovering a day of lost punches
- 1A network outage severs the connection to a plant reader for most of a day.
- 2The device keeps recording locally, as these readers are designed to.
- 3Once the link returns, a historical log pull for that date range backfills every missed punch.
- 4Attendance re-materialises for the affected days, and payroll inputs are correct again without manual entry.
What it connects to
- Attendance & Time Tracking — consumes the punches as scheduled days
- Employee Records — holds the people devices are mapped to
Questions about biometric device management
Which biometric attendance machines does Aiden support?
Aiden connects to ZKTeco devices over ADMS push and Oculus devices over WebSocket — the readers most widely used in Pakistan — and can also import device logs from disconnected sites.