Configuration and Rules

What This Section Controls

This configuration defines how the platform turns raw access events into:

• Employee IN/OUT status
• Net and brute working time
• Daily/weekly/monthly summaries
• Alerts and anomalies
• Lone worker monitoring views

Think of it as a pipeline:

Ownership and Responsibilities

• Administrators: Controllers, controller classification, global processing thresholds
• HR: Shift codes, shift assignments, department mappings (where relevant)
• Security / Operators: Monitor outcomes (Lone Workers Monitor), escalate issues, no rule changes

Access Controllers (The Foundation)

Access controllers are physical devices (turnstiles, doors, gates). Each controller must be classified correctly because classification changes calculations.

Controller Types

Site Gate

• Defines presence on site
• Drives employee IN/OUT status and "First entry / Last exit" presence window

Work Zone Controller

• Defines net working zones
• Used to calculate net time based on movement inside regulated/productive areas
• Work zones are selected in module "Departments"

Department Net Work Zones (Net Time Scope)

Departments are linked to one or more Work Zone Controllers.

What This Affects

• Which movements count toward net working time
• Why two employees in different departments can have different net results in the same building

Shift Codes (Planned Expectations)

Shift codes define the "expected day" context:

• Start and end times
• Expected brute and expected net hours
• Break rules (if used by your net calculation)
• Special statuses such as leave types (sick, paid, unpaid, maternity, paternity)

Constraints

• Only one "status-type" flag can be active per shift code (enforced by validation)

What Shift Codes Influence

• Expected hours in My Presence (week/month expected)
• Calendar "Achieved / Partial / Under" evaluation
• Tardiness and early departure flags (when enabled)

Shift Assignment (Schedule per Employee per Day)

Shift assignment attaches a shift code to an employee for a specific date.

Rules Enforced

• One shift per employee per day
• Must reference a valid shift code

Global Processing Thresholds (How Anomalies Are Flagged)

These are system-level parameters used when processing events into daily results.

Typical Thresholds

• Shift gap threshold: When consecutive events are too far apart, the system treats the day as interrupted or suspicious
• Long shift duration: Flags unusually long presence windows
• Tardiness (minutes): Flags late arrival vs shift start
• Early departure (minutes): Flags early exit vs shift end

What These Thresholds Affect

• Alerts shown in Recent Alerts
• "Has anomaly" marker in the calendar
• Exception reporting for HR and Security

Lone Workers Configuration (Who Is Monitored)

Lone workers are explicitly marked per employee.

What Happens When Enabled

• Their latest access events are tracked for the Lone Workers Monitor
• Their last known location is derived from controller events

Processing and Automation (How Data Becomes Visible)

Access data is processed automatically by a scheduled job.

What It Does

• Pulls new access events since the last run
• Updates daily summaries, status, alerts, and monitoring data
• Refreshes what users see in My Presence and Lone Workers Monitor

Typical schedule: runs every hour.