Access Control · Enterprise · Active

Employee access & gate management

Turning raw gate and access events into an operational system employees and administrators can actually work with.

Role: Architecture and delivery
Category: Access Control · Enterprise
Status: Active

The problem

Physical access systems produce a great deal of data and very little information. Gate events land in a database as rows: a credential, a reader, a timestamp. Answering an ordinary question — who was on site, was this person where they were supposed to be, does attendance reconcile — means someone writing SQL every time.

Approach

Sit a software layer between the access hardware's data and the people who need to act on it. Join gate events to employee identity, present them as operational views rather than log rows, and keep the underlying access-control system as the source of truth rather than trying to replace it.

What it does

Events joined to identity: Raw credential events become attributable to people, which is the step that turns a log into information.
Operational interface: Built for the administrators and supervisors who answer questions about presence, rather than for whoever is comfortable with a query tool.
Attendance and event views: Presence data presented in the shapes people actually ask for, instead of requiring a report to be written each time.

The hard parts

The hardware's data model is not yours: Access control systems store what the hardware needed, not what an application wants. Most of the work is the translation between those two views.
Reading without disturbing: The access-control system is life-safety adjacent. The integration reads from it carefully and does not become a dependency it has to rely on.
This data is sensitive: Presence data reveals a great deal about individuals. It needs the access controls and restraint that implies, which shapes what the interface is allowed to show and to whom.

Detail

Client confidentiality

I'm not naming the organisation, and I give no detail about the physical security configuration, site layout, credential scheme or access-control topology. Those are exactly the details that should not be public.

Where the engineering actually is

Not in the interface. It was in reconciling an access-control database designed for hardware with an employee directory designed for HR, and producing something coherent when the two disagree — which they do, constantly, because people join, leave, lose badges and get temporary credentials.

Stack