Access control and time & attendance system Who enters, how long they work and how your site responds — in one system

HEZID controls doors, turnstiles and barriers, records working time and runs the actions you define on events and schedules. Controllers make decisions on their own and keep working even when the connection to the server is lost.

Diagram: workstations and integrations connect to the HEZID server; the server connects over the network to controllers; expansion boards connect to each controller and to doors, turnstiles, barriers, lifts, sensors and sirens.
Illustrative system diagram
Why HEZID

Six reasons you can verify on site

Works without the network

Each controller checks permissions itself and stores up to about 1 million cards and 16 million events. If the server connection drops, doors keep working and no records are lost.

Logic you define

With actions and decision tables the controller responds to readers, inputs, schedules and timers: it opens, locks, switches on a siren or lighting, or sends an email.

Access and working time together

One card swipe serves both the door and the timesheet. Shifts, flexible hours and night work are calculated from the same data.

Many doors, many sites

Up to 128 expansion boards and 256 readers per controller, and no limit on the number of controllers. Sites in different cities are managed from one database, with separate rights for each administrator.

Fits your environment

Active Directory synchronisation, employee import from Excel or SAP, a REST API, Modbus to building management and export to payroll systems.

Developed and supported in Bulgaria

Both hardware and software are made by Virtex. Support, training and custom development come from the team that builds the system.

How it works

From card to report

  1. Identification

    An employee, visitor or vehicle is identified by card, PIN, licence plate or a combination of these.

  2. Decision on site

    The controller checks the access level, schedule, card validity and anti-passback rule and decides immediately, without waiting for the server.

  3. Action

    The defined actions run: opening a door or barrier, a signal, an alarm, an email or a command to another system.

  4. Record

    The event reaches the server. Operators see it in real time, and access and time reports are ready to print or export.

Capacity of one controller

Scale without extra servers

1,048,576

cards in controller memory

16.7 M

events stored locally

128

expansion boards

4096

access levels

The system grows with any number of controllers on the same server. Full technical data

See the system in action

Describe your site and task. We will show HEZID with sample data and propose a configuration.