Skip to content
CASE STUDY
OUR PRODUCTBiometric Workforce Platform

PRESENCE OS

Biometric devices record the moment. PRESENCE OS helps teams manage what happens next: attendance review, shift rules, employee requests, and payroll preparation, with workforce records stored locally.

PythonFastAPIPostgreSQLReactTypeScriptViteZKTeco ADMS
On-Premise Intranet Console • Port 4370
PRESENCE OS Preview
BUSINESS CONTEXT & PROBLEM

The job the software needed to do.

A terminal can record attendance, but HR still needs a usable record. PRESENCE OS brings device events, employee records, schedules, and review tasks into one local application, so the workflow continues beyond the clock-in.

Connect compatible ZKTeco terminals to a shared browser workflow while keeping workforce records in a customer-managed local database.

1

Move supported terminal records into the attendance workflow without repeated manual exports.

2

Apply consistent rules across rotating, overnight, and split shifts.

3

Give employees a place to review timesheets and submit supported requests.

4

Keep operational workforce storage on the customer’s server, separate from cloud license validation.

THE BUILD BOUNDARY

Support compatible terminals over the local network, store workforce data locally, and make deployment responsibilities clear for the customer’s IT team.

Confirm the terminal model, firmware, ADMS support, or standalone connection on port 4370.
Use local PostgreSQL 14+ storage with customer-managed access and backups.
Plan for local network availability, terminal buffering, and licensing connectivity.
Define employee, HR, finance, and administrative permissions.
SYSTEM ARCHITECTURE

How the pieces work together.

Separate device communication, data storage, attendance rules, and browser interfaces so each part has a clear job.

LAYER 01

Device gateway

FastAPI receives supported ADMS events and handles compatible standalone connections on port 4370.

LAYER 02

Local workforce database

PostgreSQL stores employee records, attendance events, and schedules, with migrations for application updates.

LAYER 03

Attendance rules

Configured policies pair punches, apply grace periods, and calculate regular and overtime hours for review.

LAYER 04

Management dashboard

HR and operations review attendance events, configure shifts, inspect department reports, and prepare exports in the browser.

LAYER 05

Employee self-service

A mobile-friendly browser portal lets employees check attendance, view timesheets, and submit supported requests.

DELIVERY SCOPE

The decisions behind the working product.

Terminal events in one feed

CAPABILITY

Receive attendance events from compatible ZKTeco devices.

PROBLEM ADDRESSED

Make device records available to the application without repeated manual exports.

TECHNICAL IMPLEMENTATION

Python and FastAPI handle ADMS endpoints and supported standalone device communication.

Why it matters: Give administrators a shared view of supported attendance events.
Scope: Compatible terminal firmware, network routing, and the agreed connection method.

Workforce data on your server

CAPABILITY

Store employee, attendance, and access records in local PostgreSQL.

PROBLEM ADDRESSED

Keep operational data within the customer-managed deployment.

TECHNICAL IMPLEMENTATION

PostgreSQL 14+ uses versioned migrations; Windows DPAPI protects stored credentials.

Why it matters: Let the customer manage database hosting, access, and backup arrangements.
Scope: A supported Windows host, available resources, and an agreed backup plan.

Shift rules that follow the working day

CAPABILITY

Evaluate rotating, overnight, split, and flexible shifts using configured policies.

PROBLEM ADDRESSED

Replace repeated manual calculations with a consistent rule-based review.

TECHNICAL IMPLEMENTATION

The rules layer pairs recorded punches and evaluates grace periods, early departures, and overtime.

Why it matters: Prepare attendance totals and CSV or PDF reports for payroll review.
Scope: Approved attendance policies and configured shift schedules.

Permissions and change history

CAPABILITY

Separate employee, HR, finance, and administrative access.

PROBLEM ADDRESSED

Restrict sensitive actions and make administrative changes easier to trace.

TECHNICAL IMPLEMENTATION

Server-side permission checks and audit records support the application’s access model.

Why it matters: Help teams understand who handled an adjustment and which actions their role allows.

Answers employees can find themselves

CAPABILITY

Provide personal attendance views, timesheets, and supported requests in the browser.

PROBLEM ADDRESSED

Give employees a shared record for routine attendance questions.

TECHNICAL IMPLEMENTATION

A responsive portal connects to the same local workforce platform.

Why it matters: Let employees review their records and request follow-up from one place.
Scope: Authorized access to the local application through the agreed network setup.

Licensing kept separate from workforce storage

CAPABILITY

Validate software licensing in the cloud with an offline grace period.

PROBLEM ADDRESSED

Allow for temporary internet interruptions in the licensing connection.

TECHNICAL IMPLEMENTATION

License validation uses a cloud check and a configured local grace period.

Why it matters: Keep licensing connectivity distinct from the local storage of workforce records.
Scope: Periodic internet access for license refresh; attendance still requires the local server and network.
DELIVERY & OUTCOMES

Built for a local deployment.

DEPLOYMENT

Local Windows deployment with a customer-managed PostgreSQL database.

The guided installer prepares the application and database components. Deployment planning covers server resources, network routes, permissions, backups, and licensing connectivity.

TESTING & RELIABILITY

Validation covers supported device communication, attendance rules, permissions, database changes, and browser workflows. The actual hardware and deployment configuration must be included in acceptance checks.

WHAT WAS IMPLEMENTED
Implemented a local device gateway and browser-based attendance workflow.
Combined recorded punches, shift rules, employee requests, and reports in one product.
Kept customer-held workforce storage separate from cloud license validation.
WHAT COMES NEXT

PRESENCE Connect is in development for iOS and Android. Additional multi-branch or cloud options require separate availability and scope confirmation.

Bring your workflow into the conversation.

Show us what happens today and what needs to work better. We’ll help turn the problem into a practical software plan.

ZKTeco is a registered trademark of its respective owner. PRESENCE OS is an independent software product and is not affiliated with, sponsored by, or endorsed by ZKTeco.