Attendance Setup - Biometric / Smart-card attendance recording
Integration of the Biometric / Smartcard systems is done with the help of a windows Sync Service - which is installed on the same machine where the timestamps are stored. Using this service EazeWork's servers synchronize with the database at a defined frequency and update the timestamps automatically. The architecture diagram is shown below.
There are different ways in which Biometric / Smartcard data is fetched from databases to EazeWork servers depending upon the way the data is stored in the databases. Some scenarios are detailed below -
1. There are multiple offices across different cities and swipes of biometric / smartcard is stored in separate databases then the synchronization program will have to be installed separately for each database
2. If data for all locations is being brought to one central location then a single synchronization program would be able to capture all the data
3. When a new location is added in setup the system needs to be updated to map this location with the synchronization id. This activity needs to be done by the Account Manager
4. Till the location is not mapped with the synchronization id it cannot be used as Office location for an employee whose attendance method is Biometric / Smartcard
5. If Work location feature is activated then the Biometric / Smartcard data is always taken from the Work location
6. If synchronization between the databases and EazeWork servers stops then Biometric
/ Smartcard data is not received anymore. This leads to the following-
a) Out-time is not received and if auto time out is not enabled then the day's
attendance record becomes pending
b) When backlog of data is synchronized sometimes later data stamps are received
by EazeWork servers before and earlier data stamps are received later. For example
a timestamp of 18:15 of 12-Aug is received on 10:01 on 14-Aug and then a timestamp
of 17:55 of 12-Aug is received at 10:02 on 14-Aug. In such a scenario the timestamp
of 17:55 is not considered for processing attendance. It is strongly recommended that swipe data should be synchronized in the order of which it is generated.
Refer to the article on Trouble Shooting Biometric / Smart-card Integration for more details of checking and resolving integration issues..
Biometric data is maintained for 3 months in EazeWork servers and is used for
backdated shift corrections.
Related Articles
Trouble Shooting Biometric / Smart-card Integration
As Application Administrator you would be able to check the status of biometric / smartcard synchronization of EazeWork servers. Refer to the article on Attendance Setup - Biometric Smart-card attendance recording for more details on managing the ...Attendance setup
Menu Path : Setup > HR Setup > Attendance Setup > Processes tab Accessible to : Application Administrator In this section the setup relevant to attendance module is managed by the Application Administrator. 1. Processes Tour Feature/ OD Feature/ Work ...Attendance updation setup
Menu Path: Setup > HR Setup > Attendance Setup > Attendance Updation tab Accessible to: Application Administrator On this tab the setup for Attendance Updation processes can be configured. 1. Request Initiators - the roles selected in the table shown ...Onboarding setup
Menu Path: Setup > HR Setup > Onboarding Accessible to: Application Administrator Onboarding process helps you to manage the complete cycle of a new joiner on boarding. This module tracks the activities to be done by Employee, HR manager and other ...Tour setup
Menu Path: Setup > HR Setup > Attendance Setup > Tour setup tab Accessible to: Application Administrator On this tab the setup for Tour process can be configured. 1. Holiday counted - if this parameter is selected then Holidays falling within a Tour ...