-
Accessing the application
-
Application security
-
Devices and communication protocol
-
Application access control levels
-
Employees, departments and device users
-
Time & Attendance Functionality
-
Access control
-
Batches & payroll integration
-
Binary City Time API (Application Programming Interface)
-
Binary City Time integration with BioTime Technical Documentation
Data stored on the devices
The devices store the following biographical data of employees:
Field | Description |
Device ID | ID that is allocated to each employee in sequence, when employee is create in Binary City Time software. |
Name | The employee name as specified when created in Binary City Time, is stored. |
Surname | The employee name as specified when created in Binary City Time, is stored. |
Priviledge | The employee's device privilege on the system. Please refer to "Device Users" for a detailed explanation of how this works, but effectively, a user can either be:
|
Fingerprint templates | All fingerprints that are enrolled for each employee, is stored on the device to allow for authentication when the employee puts his or her finger on the biometric device. This is stored in a ZKTeco proprietary format that can only be used by ZKTeco devices making use of their fingerprint template algorithm. |
Pin codes | If an employee has a pin code registered, this is stored on the device (Typically this is more an exception than a rule, and is an option we offer to employees that has difficulty having their fingerprints read by the biometric reader). |
RFID Card Registered | If an employee has a RFID card registered, this is stored on the device (Just as per the pin codes above, typically this is more an exception than a rule, and is an option we offer to employees that has difficulty having their fingerprints read by the biometric reader). |
The When the system is used for access control, these device ids, are also linked to timezone groups, but this is not effective when using the system for time & attendance only.
The following transactional data (as staff clock on the system) is stored on the device:
Field | Description |
Device ID | ID that is allocated to each employee in sequence, when employee is create in Binary City Time software. |
State | This refers to clocking in or out |
Date & Time | The date and time that the staff member clocked |
None of the backend functions of the device is available to any user who has not been enrolled as an administrator from the Binary City Time software.
There are no comments for now.