VMware ESXi and vSphere Cluster Management

Introduction to Time and Attendance Systems

Learn how time and attendance systems record work time, breaks, leave, and overtime, and how terminals, credentials, networks, and software work together.

A time and attendance (TA) system captures and manages employee attendance, worked hours, breaks, absences, and related reports. Instead of relying entirely on handwritten time cards or manually entered timesheets, an organization can collect attendance events electronically and apply configured schedules and policies.

This guide explains the purpose, components, operation, configuration, benefits, troubleshooting, and relationship between attendance tracking and physical access control. For a short overview, see this introduction to time and attendance systems.

What a Time and Attendance System Does

A TA system records when an employee starts work, ends work, takes a break, leaves for a personal or business reason, or records another configured attendance event. These events are used to create a timesheet, which is a record of attendance events and calculated work time.

Administrators can use the system to review:

Scheduled hours and actual arrival or departure times
Clock-in and clock-out events
Meal and other breaks
Personal departures and business-related absences
Medical leave and other leave-related events
Missed arrivals, missed departures, and duplicate events
Overtime, meaning work time beyond the normal scheduled or policy-defined amount

In a manual process, employees may write times on paper cards or submit spreadsheets that another person must enter and check. Electronic collection reduces repeated data entry and gives authorized staff faster access to attendance information. It does not eliminate the need for policy decisions or review: administrators still need to verify unusual events and approve attendance data before payroll processing.

Business Benefits

Faster visibility: Managers and HR staff can see worked time and possible overtime without waiting for paper records to be collected.
Fewer data-entry errors: A terminal records the time of an authenticated event directly, reducing transcription mistakes associated with handwritten cards.
More efficient payroll preparation: Automatically collected events can be calculated into work-time and overtime reports for review before payroll.
Consistent attendance practices: Employees use the same configured clocking process and policies within their group.
Exception alerts: The system can identify missed arrivals, excessive overtime, late events, or other conditions that need attention.
Less administration and paper: Electronic records reduce manual filing, paper handling, and repetitive spreadsheet work.

A TA system supports payroll preparation, but attendance software and payroll software are not necessarily the same system. The TA system supplies reviewed attendance information; payroll may apply additional pay, tax, benefits, and approval rules.

Attendance Events and Time Intervals

An attendance event is an action recorded at a particular time, such as starting work or ending a break. A time interval is a configured category of time used to describe a break, absence, leave period, or other departure from normal work.

Intervals can include rules such as:

Expected or maximum duration
Paid or unpaid treatment
Whether the interval counts toward worked time
How the interval appears in reports
Which departments or employee groups may select it
Whether an administrator must review or approve it

Common interval categories include meal breaks, personal departures, business-related absences, and medical leave. The exact treatment depends on organizational policy and applicable employment requirements.

Common Attendance Event Types

Event type: Work start. Typical use: Beginning a scheduled shift. Example action: Employee taps a badge or presents a fingerprint before working. Effect on timesheet: Starts or updates the calculated work period.

Event type: Work end. Typical use: Ending a scheduled shift. Example action: Employee authenticates when leaving work. Effect on timesheet: Ends the calculated work period or provides the departure time.

Event type: Meal break. Typical use: A scheduled meal interval. Example action: Employee selects the meal-break option. Effect on timesheet: Applies the configured paid or unpaid break rule.

Event type: Personal departure. Typical use: Leaving for a personal reason. Example action: Employee selects personal departure at the terminal. Effect on timesheet: Records an interval that may be excluded or treated according to policy.

Event type: Business-related departure. Typical use: Leaving the site for work activity. Example action: Employee selects the business-purpose event before attending an external meeting. Effect on timesheet: Records the reason for the absence and applies the configured reporting treatment.

Event type: Medical leave. Typical use: Recording an approved or reported medical absence. Example action: Employee or administrator records the medical-leave event. Effect on timesheet: Classifies the interval for attendance and leave reporting.

Practical Attendance Examples

Business-Related Departure

An employee leaves the site for a work meeting. At the terminal, the employee selects a business-related departure instead of a standard end-of-day departure. The system stores the event in the timesheet, allowing reporting and policy handling to distinguish work activity from a personal absence.

Different Departmental Schedules

Accounting employees may work a standard office schedule with one set of break rules. Warehouse employees may work an early, late, or rotating shift with different breaks and overtime thresholds. Each group should receive its own schedule and interval configuration so reports compare events with the arrangement the employees actually follow.

Overtime Exception

An employee remains clocked in beyond the configured shift end. The system identifies the extra time as a possible overtime or attendance exception. An administrator checks whether the additional work was authorized, whether the employee forgot to clock out, and whether the result should be sent to payroll.

Rules by Department and Employee

Attendance configuration should reflect actual work arrangements rather than applying one rule set to everyone. Schedules and policies can be assigned by employee type, role, shift, or department.

Employee group: Office/accounting staff. Schedule pattern: Standard daytime office schedule. Applicable intervals: Office meal break, personal departure, business absence, and relevant leave categories. Why separate rules are needed: Office hours and break expectations may differ from operational or shift work.

Employee group: Warehouse or shift staff. Schedule pattern: Early, late, rotating, or overnight shifts. Applicable intervals: Shift-specific breaks, handover periods, business absences, and leave categories. Why separate rules are needed: Shift boundaries, permitted breaks, and overtime calculations may differ from office staff.

Employee records normally include a department or group assignment, an assigned schedule, and one or more authentication identities. When a person changes role or shift, review the group, schedule, interval permissions, and overtime rules together.

Core System Components

A typical on-premises TA deployment combines devices, communications hardware, and software:

Attendance terminal: A device at an entry, exit, or designated clocking point where an employee authenticates and records an event.
Employee credential: An RFID card, contactless badge, or other identity method associated with an employee profile.
Biometric reader: A terminal that verifies a physical characteristic, such as a fingerprint.
Power infrastructure: Hardware and cabling that provide operating power to terminals and communications equipment.
Controller or communication converter: Hardware that supports terminal communications and translates them for delivery over a network.
RS-485 link: A serial connection commonly used between terminals and the controller or converter.
TCP/IP network: The IP-based network that carries attendance data from the converter to the software host.
Time and attendance software: The application that manages employees, schedules, intervals, events, reports, and alerts.
Management computer or server: The local computer or server hosting the application in an on-premises deployment.

Component Relationships

Component: RFID terminal. Primary role: Read a contactless credential and record a clocking event. Typical technology: RFID reader and terminal display. Connection: Serial connection to the controller or converter.

Component: Fingerprint terminal. Primary role: Verify an enrolled fingerprint and record an event. Typical technology: Fingerprint sensor. Connection: Serial connection to the controller or converter.

Component: Employee badge or card. Primary role: Provide an employee identifier. Typical technology: RFID credential. Connection: Read wirelessly by the terminal.

Component: Controller or converter. Primary role: Support terminal communications and convert the connection for the network. Typical technology: RS-485 interface and TCP/IP interface. Connection: Between terminals, the network, and management software.

Component: RS-485 link. Primary role: Carry serial data between terminals and controller hardware. Typical technology: Multi-device serial cabling. Connection: Terminal to controller or converter.

Component: TCP/IP network. Primary role: Carry data over an IP network. Typical technology: Ethernet or another IP network. Connection: Converter or controller to the software host.

Component: Time and attendance software. Primary role: Store events, apply rules, and produce reports. Typical technology: Web-based management interface. Connection: Receives data through the network and presents it to administrators.

Component: Management PC or server. Primary role: Host the application and its data in an on-premises deployment. Typical technology: Local server or administrator workstation. Connection: Runs or accesses the attendance software over the network.

Attendance Terminals and Authentication

To create a clocking event, an employee identifies themselves at a terminal. The terminal verifies the credential or biometric identity, records the current time, and may ask the employee to select an event type.

RFID Badge Authentication

RFID means radio-frequency identification. An RFID card or badge contains an identifier that a compatible reader detects without physical contact. The attendance application associates that identifier with an active employee profile. The employee typically taps or presents the badge, and the terminal records the event.

Fingerprint Authentication

Biometric authentication verifies identity using a physical characteristic. At a fingerprint terminal, an employee presents an enrolled fingerprint. The terminal compares it with the stored biometric enrollment according to the device's design, then creates an event when the identity is accepted.

Fingerprint recognition can reduce the possibility of one employee lending a badge to another, but organizations must consider privacy, consent, security, accessibility, and a fallback method for failed recognition. RFID badges may be simpler to replace, while biometric systems require careful enrollment and governance.

Event Selection at the Terminal

A terminal may provide dedicated selections such as work start, work end, meal break, personal departure, business-related departure, or another configured interval. This allows the event to record not only who acted and when, but also why the interval occurred.

Power, RS-485, and Network Conversion

Terminal infrastructure may deliver power and carry communications through separate or shared cabling arrangements, depending on the equipment design. The installation must provide reliable power and a communications path between each terminal and the management software.

RS-485 is a serial communications standard often used for terminal-to-controller connections. It is suitable for connecting devices over structured cabling and can support communication with more than one device in an installation when designed correctly.

The controller or communication converter bridges two communication environments:

The terminal sends attendance data over the RS-485 serial link.
The controller or converter receives the serial data and translates or forwards it.
The converted data travels over TCP/IP through the organization's IP network.
The attendance software on a local computer or server receives and stores the event.

TCP/IP refers to network communication protocols used to transmit data across an IP network. It does not authenticate the employee by itself; it transports the event between the communications hardware and the software.

Time and Attendance Software Functions

The management application is where raw terminal events become usable attendance information. Common functions include:

Creating, editing, deactivating, and removing employee records
Assigning RFID badges, cards, or biometric identities
Assigning employees to departments or other groups
Defining schedules, shifts, breaks, leave intervals, and overtime rules
Controlling which event types each group can select
Reviewing individual attendance events and timesheets
Calculating work time and potential overtime
Generating attendance, work-time, and overtime reports
Monitoring exceptions and sending or displaying alerts
Providing a web-based interface for authorized management access

Software may store the original event and a calculated interpretation separately. This is useful because an administrator can correct or explain an event while retaining an audit trail, depending on the application's capabilities and organizational policy.

End-to-End Workflow

An employee presents an RFID badge or fingerprint at an attendance terminal.
The terminal verifies the identity and records the identity, time, terminal location, and selected event type.
The terminal sends the event through its RS-485 serial connection.
The controller or converter relays the data from the serial connection to TCP/IP.
The network delivers the event to the time and attendance software on a local computer or server.
The software stores the event and applies the employee's department, schedule, interval, and overtime rules.
The application updates the employee's timesheet and reporting data.
Administrators review exceptions, investigate unusual results, and verify the information before payroll processing.

Badge or fingerprint
        |
Attendance terminal
        |
     RS-485
        |
Controller / converter
        |
     TCP/IP network
        |
TA software on PC or server
        |
Timesheets, alerts, and reports

Configuration Checklist

Employee Records

Create an employee profile.
Assign an RFID badge, card, or enrolled biometric identity.
Assign the employee to the correct department or employee group.
Deactivate or remove former employees so their credentials cannot create new events.

Attendance Policies

Create normal schedules by employee group.
Define break, personal departure, business activity, and medical-leave intervals.
Set paid or unpaid treatment and reporting behavior where applicable.
Specify which event types are available to each group.
Set overtime thresholds and missed-clock-in alert conditions.

Terminal and Communications Setup

Place terminals near relevant doors or designated clocking points.
Connect terminals to the controller or converter through RS-485.
Provide reliable terminal power through the applicable infrastructure.
Connect the controller or converter to the TCP/IP network.
Configure the attendance software to receive data from the intended terminals.

Reporting and Review

Review individual timesheets and raw attendance events.
Run work-time and overtime reports.
Investigate alerts and attendance exceptions.
Correct or document missing, duplicate, or incorrectly classified events.
Prepare verified attendance data for payroll processes.

Attendance and Physical Access Control

Physical access control determines whether a credential holder may enter a door, area, or facility. A TA system records work-time events. These systems can work alongside one another, but their purposes are different.

An organization may reuse employee badges, identity records, terminals, or credential databases across both systems. For example, one RFID badge might identify an employee at an attendance terminal and also be presented to a door reader.

However, a recorded attendance event does not automatically mean that entry was authorized. Attendance answers a question such as “When did this employee record starting work?” Access control answers “May this credential open this protected door now?” A system can record a clock-in at one location while separately denying access to a restricted room.

Troubleshooting

Attendance Event Does Not Appear in the Software

Confirm that the employee used a registered badge or enrolled fingerprint.
Verify that the terminal has power and is operating.
Check the RS-485 connection between the terminal and controller or converter.
Check the TCP/IP connection from the controller or converter to the software host.
Confirm that the terminal is configured to send data to the intended attendance system.

Work-Time Calculation Is Incorrect

Verify the employee's department or employee-group assignment.
Review the assigned schedule and applicable intervals.
Check whether the correct event type was selected at the terminal.
Review the event history for missing or duplicate entries.

Overtime Totals Are Unexpectedly High

Check for a missed clock-out event.
Review configured shift hours and overtime thresholds.
Confirm that the employee is assigned to the correct schedule.
Determine whether a business-related absence or another interval was recorded correctly.

Badge Authentication Fails

Confirm that the RFID credential is assigned to an active employee profile.
Test whether the card or badge is damaged.
Verify terminal reader operation and communications.
Confirm that the employee has access to the required terminal event options.

Key Exam and Design Notes

A TA system records and manages attendance events; it does not by itself define every payroll result.
Clock-in and clock-out are examples of attendance events, while a time interval categorizes a period such as a break or leave.
RFID uses a contactless credential; fingerprint authentication uses a physical characteristic.
RS-485 commonly connects terminals to a controller or converter, while TCP/IP carries data across the IP network to software.
Schedules and interval rules should be assigned according to actual employee groups, shifts, and departments.
Attendance recording and permission to enter a protected area are separate functions, even when they share credentials or hardware.