Access control — Doors and controlled remote opening

The platform only ever asks the access control system for a momentary opening. It has no hold-open, unlock, lockdown or schedule functions, never sends a lock command and never drives a lock relay, so it can never override or block a fire-alarm door release.

Doors and events

• Doors, video door stations and turnstiles from the access control system: open or closed, locked, forced open and held open, plus fire release, lockdown and faults reported by the system.
• Each door can be linked to cameras: a live view and a snapshot taken before the door is opened.
• Event log, device health and a connection test for each access control system; supported systems can be recognized during a network scan.

Controlled remote opening

• One momentary opening at a time, 1–10 seconds per door (5 seconds by default); the access control system relocks the door itself.
• Only people a manager has made door operators can open doors (nobody by default; granting it needs an e-signature), and every opening needs a reason.
• Important doors also need the opener's e-signature or confirmation by a second door operator within 3 minutes.
• Rate limits: once every 10 seconds and 12 times an hour per person, once every 20 seconds per door, 60 times an hour per site.

Doors that stay closed

• Doors marked as fire doors, egress doors or restricted areas cannot be opened remotely by default; a manager's signature is the only exception.
• Opening is refused when the access control system reports fire release, lockdown or a fault, or when the lock state cannot be trusted.
• Life-safety, protection, emergency-power and medical equipment always stays read-only; this rule cannot be relaxed.

Approval, read-back and audit

• Every opening goes through the 8-step change flow with a one-time execution ticket: the gateway re-reads the door before opening and reads back that it unlocked, and the platform then checks that it relocked on time.
• If the read-back or the relock check does not match, the result is marked uncertain and a critical alarm is raised.
• Who opened which door, when and why, which camera image was viewed, and the access control system's receipt and result are written to the hash-chained audit log.

Supported systems

• Drivers: UniFi Access (local Open API), ONVIF Profile C door control (for example Axis A1001 / A1601), the 2N HTTP API and the Gallagher Command Centre REST API.
• Implemented, not yet validated on site: each driver is tested against a simulator built from the vendor's published interface, and the demo's doors use these simulators. Each real installation is checked item by item during commissioning.
• Other access control makes are recorded in the model library for monitoring and project planning; remote opening needs one of the drivers above.

Industries

• Biopharma & life sciences
• Data centers
• Logistics & warehousing
• Commercial buildings
• Healthcare

Related