uKnowva’s Biometric Integration Architecture

Objective

To define a scalable and flexible biometric integration capable of integrating both virtual and physical biometric devices for attendance data, with data synchronization into the uKnowva HRMS attendance modules.

Summary of the Flow:

Employees mark attendance via biometric or virtual methods.
Data is collected in real-time to the central attendance server/DB.
A client utility facilitates secure transfer to uKnowva.
uKnowva’s cron job processes and syncs this data.
Final punches are displayed on each employee’s attendance calendar.

1. Employee Interface

This is where attendance logging begins.

Physical Biometric: Traditional biometric devices (fingerprint/face ID) are used by employees to log attendance.
Virtual Biometric [uKnowva Instance]: Used in remote/WFH setups where employees log attendance digitally via the uKnowva platform (browser or app).
Both methods push data in real time to the data collection layer via LAN/Wi-Fi.

2. Data Collection Layer

The data from the physical/virtual biometric sources is pushed in real-time to:

Attendance Server: Collects raw punch data received from physical biometric
Attendance Database of uKnowva: Acts as a central repository to store attendance records received from virtual biometric.
This layer ensures a unified, real-time capture of employee punches before integration into uKnowva.

3. Client Utility

This is a setup required on the client’s infrastructure to enable data transfer from the attendance server to uKnowva.

Includes:

Whitelist IPs and allow gateway (ADMS) access – ensures network-level access.
Provide DB details – if uKnowva is connecting directly to the client’s attendance DB.
API details – if data sync is done over secure APIs.
Install utility on client server – uKnowva attendance utility fetches punch data periodically.

This enables flexibility to sync data via:

Direct DB access
API
uKnowva Attendance Utility

4. uKnowva ’s Integration Methods

4.1 Integration with ESSL Machines using ADMS Option

If the client is using an ESSL biometric device and agrees to update its configuration settings, the machine can be directly integrated with uKnowva HRMS using the ADMS feature.

Steps:

Enable the ADMS feature in the ESSL device settings.
This is the most straightforward method if the device supports ADMS and is connected to the internet.

4.2 Integration via Matrix Machine Plugin

uKnowva provides a ready-made plugin for integrating Matrix biometric devices.

Steps:

Download and install the plugin from the uKnowva Extension Store.Matrix Attendance Plugin
Enter the following API credentials:

Bio-Metric API URL
API Username
API Password

Save and test the connection.

Ideal for clients already using Matrix hardware and APIs.

4.3: Integration via Client Database Connectivity

If biometric punch data is stored in the client's internal database, uKnowva can fetch the data directly using secure database access.

Required Database Connection Details:

DB_TYPE (e.g., MySQL, MSSQL)
DB_DRIVER
DB_IP_ADDRESS
DB_USERNAME
DB_PASSWORD

Additional Requirement:

The client must whitelist the uKnowva server IP (provided by the uKnowva team) for secure access.
This method avoids changes to the biometric machine itself and works well when clients prefer data-level integration.

4.4: Integration via uKnowva Attendance Utility

For clients who prefer not to expose their database or configure machines directly, uKnowva can provide a client-side utility.

Key Highlights:

The utility is installed on the client’s server or local machine.
It fetches punch data from the biometric device or database.
Sends data securely to uKnowva HRMS at scheduled intervals.

To Deploy:

Contact helpdesk@uknowva,com for setup and configuration support.

Note: Utility is built based on the client’s biometric data source and server environment.

5. uKnowva’s Sync Mechanism

Once the data is received:

It is saved in uKnowva’s internal attendance database.
A cron scheduler is responsible for:

Periodically processing raw data.
Syncing punches to employee calendars.
Displaying final IN/OUT records as per shift policies.

This final sync ensures punches are visible in the Attendance Calendar for HR & Employees, enabling further workflows like payroll, compliance, and reporting.

Summary Comparison

Method	Device Type	Internet Required	DB Access Needed	uKnowva Plugin/Tool
Direct with Biometric Device	ESSL (ADMS)	✅ Yes	❌ No	❌ Not required
API Method	API	✅ Yes	❌ No	✅ Plugin
Databas Connectivity	Any (DB-backed)	✅ Yes	✅ Yes	❌ Not required
With uKnowva Utility	Utility Based	✅ Yes	❌ No	✅ uKnowva Utility