A time and attendance system collects clock-in and clock-out times from card readers and fingerprint or face recognition terminals and combines them in one database. Overtime, late arrivals, and leave calculations rest on that record, and the monthly timesheet comes from it. If the server stops, records are not collected, and the missing hours have to be filled in by hand at month end.
We do not sell PDKS devices or software. You choose the software; we build and operate the server, database, network, and backups it runs on. The software vendor manages the application, and we manage the infrastructure.
When you need it
- The PDKS server runs on a desktop PC in a branch or in a small server room.
- Devices at factories and branches send data to head office over the internet without protection.
- You do not know whether past clock-in records have a backup if that computer fails.
- You cannot show where fingerprint or face data is stored and who accesses it.
- You move timesheet data to payroll by carrying files across every month.
- A new branch or factory is opening and its devices need to connect to head office.
Rules that shape the infrastructure
Biometric data such as fingerprints and face scans is a special category of personal data under Article 6 of Law No. 6698 on the Protection of Personal Data (KVKK). As the employer and data controller, you decide the legal basis on which you process it. We do not make that decision and we do not give legal advice.
The law also requires the measures set by the Personal Data Protection Board to be in place when special category data is processed. On the infrastructure side, we build the technical part of those measures:
- Data stays in Turkey, on infrastructure we run in a data center in Istanbul.
- Role-based access: an HR specialist sees only the records of their own department, and a system administrator reaches the server, not the application data.
- Encryption of the database and backups, and device traffic to head office carried in an encrypted tunnel.
- Access logs that show who accessed which record and when.
- Backups kept in a separate logical area, the isolated backup area.
Scope
- Server and database. We install the PDKS application and database server and apply patches on a schedule. Before installation we confirm the operating system and database versions the software requires in the vendor's documentation.
- Device connectivity. We set up the path from the readers at branches and factories to the central server. We keep the device network in its own VLAN and write firewall rules that let it talk only to the PDKS server. A VLAN splits one physical network into logical parts, so computers and cameras stay outside the segment where the terminals sit.
- Backup. We back up the database and configuration files to the isolated backup area on ARGE Cloud. We test restores and report the result in writing.
- High availability. Optionally, we build a cluster in which a second server takes over if one fails. The need depends on your device count and shift pattern.
- Access and monitoring. We collect server and firewall logs in a central log system (SIEM). We monitor the server, disks, the database service, and backup results, and the infrastructure is monitored 24/7. Monitoring hours and response scope are written in the contract.
- ERP and HR connection. We set up the path that carries timesheet data to payroll, described below. For the payroll software's own servers, see HR and payroll infrastructure.
How devices connect to head office
Devices at head office and branches reach the PDKS server in one of three ways. The right one depends on the type of line and the number of branches.
- Your carrier's MPLS line. Your internet service provider's MPLS line links head office and branches. MPLS is a private line that carries traffic without crossing the internet.
- MPLS with a private link to ARGE Cloud. The same line is extended to ARGE Cloud. Even when the server is in the cloud and the devices are at a branch, the data does not cross the internet.
- IPsec when there is no MPLS. Over the existing internet line, we set up an encrypted IPsec tunnel with SD-WAN capable routers and firewalls. SD-WAN manages several lines and steers traffic to the better one.
Most devices keep records in their own memory when the connection drops and send them to the server once it returns. Memory capacity differs by device, so for long outages we confirm what happens in the vendor's documentation. We also assess together whether a branch needs a backup line. Our page on connecting head office and branches explains the options.
Moving timesheet data to ERP and payroll
The clock-in, clock-out, and overtime data PDKS produces goes into the HR system before payroll. The route depends on the ERP.
- Logo has no PDKS program of its own; the attendance data management module in Logo Edge HR (j-HR) records clock-in and clock-out, leave, and overtime, and builds the timesheet.
- Canias and Workcube import device data from files.
- Nebim integrates with external PDKS systems.
When the ERP and PDKS run in the same VPC, the transfer stays inside the VPC and never crosses the internet. Configuring the integration and functional support belong to the ERP and PDKS vendors; we provide the network the two servers use to reach each other and the environment where the scheduled transfer runs.
Out of scope and limits
We do not sell PDKS software licenses or devices, we do not provide functional support for the software, and we are not an authorized partner of PDKS vendors. Installing turnstiles and readers is outside our scope. The legal basis for processing biometric data, the privacy notice, and employee consent are legal matters, so please consult your legal counsel. Building the infrastructure alone does not meet your obligations under KVKK.
How we work
- We map where the PDKS server runs today, the number of devices, the branches, and the lines connecting them.
- We confirm the software vendor's server and network requirements in its documentation and propose a design in writing.
- Before moving, we back up the database and test the restore. Outside working hours we point the devices to the new server address and watch that records arrive during the first days.
- We report backup results and capacity trends; the reporting frequency is written in the contract.
Service models
- On ARGE Cloud: The PDKS server runs as a cloud server on infrastructure we operate in a data center in Istanbul, in a VPC dedicated to you. The data stays in Turkey.
- In your environment (on-prem): We build and operate the server, database, and backups in your server room.
- Combined: The server runs at your site, and backups go to the isolated area on ARGE Cloud.
Technologies we use: Windows Server · Linux · Microsoft SQL Server · VLAN · IPsec · SD-WAN · MPLS · SIEM
For hosting the ERP side, see our ERP infrastructure services.
Frequently asked questions
Does fingerprint and face data leave Turkey? Data for a PDKS server on ARGE Cloud is kept in the Istanbul data center, in a VPC dedicated to you. If we build the server in your environment, the data stays in your building. If the software lets the vendor connect remotely or sends data to its own cloud, we ask the vendor before installation.
Does this service make us compliant with KVKK? No. As the employer, you decide on what basis biometric data is processed. We only build the infrastructure measures: data stays in Turkey, role-based access, encryption, access logs, and an isolated backup.
Do devices keep recording when the internet goes down? Most devices keep records in their own memory and send them to the server when the connection returns. Memory capacity differs from device to device, so we confirm it for your device in the vendor's documentation.
Can you move our current PDKS software? We can if the vendor supports the server and database version. Installing and configuring the software stays with the vendor; we prepare the server, back up and move the data, and handle the network side of pointing devices to the new address.
How does timesheet data reach payroll? It depends on the ERP. Logo uses the attendance module in Logo Edge HR, Canias and Workcube use file import, and Nebim uses its external PDKS integration. If the ERP and PDKS share a VPC, the transfer does not cross the internet.