Access control controllers connect software and identity decisions to real doors, gates, elevators, and monitored points. This reference covers controller architecture, downstream modules, inputs and outputs, communications, offline operation, capacity, enclosure design, cybersecurity, and commissioning.
Return to the complete system-parts reference.
What the controller does
A controller receives credential data, evaluates stored rules or coordinates with a host, operates relays, supervises inputs, records events, and reports status. Many controllers continue to make local decisions when a server or internet connection is unavailable, but the exact retained functions and database size vary.
Common architecture layers
- Host or cloud service: provides administration, reporting, integrations, and system-wide policy.
- Intelligent controller: stores configuration and makes field decisions.
- Reader or door module: connects readers, contacts, request-to-exit devices, locks, and auxiliary relays.
- I/O module: adds supervised inputs or outputs for gates, elevators, interlocks, alarms, and building interfaces.
- Power and enclosure: protects electronics and supplies calculated operating and standby power.
Capacity must be calculated, not assumed
Record licensed and physical capacity for doors, readers, cardholders, credentials per person, access levels, schedules, stored events, inputs, outputs, elevators, floors, and integrations. Reserve capacity for realistic growth. A panel with unused terminals may still be limited by licensing, current draw, database size, or downstream-bus rules.
Offline behavior
Confirm what happens during loss of host, cloud, LAN, WAN, DNS, time service, or controller-to-module communication. Test whether valid users can enter, changes queue, events buffer, schedules continue, doors follow their last state, alarms operate locally, and events upload correctly after restoration. Document the expected behavior instead of relying on the word “offline.”
Inputs, outputs, and supervision
Inputs commonly monitor door position, request to exit, lock status, enclosure tamper, emergency release, gate position, and equipment trouble. Outputs may operate locks, sounders, indicators, gates, elevators, or interface relays. End-of-line supervision can distinguish normal, alarm, open-circuit, and short-circuit conditions when supported and wired correctly.
Reader communications
Confirm supported reader protocols, port count, topology, distance, cable, termination, addressing, and secure-channel capability. OSDP readers may allow bidirectional supervision and updates. Proprietary buses can provide additional functions but may affect replacement options. Wiegand may support legacy devices while offering less visibility and protection.
Network and cybersecurity checklist
- Dedicated owner and documented administrator roles
- Supported firmware and secure update process
- Unique credentials; no retained default accounts
- Encrypted management and controller communications where supported
- Network segmentation, firewall rules, and approved remote access
- Certificate, DNS, time, and backup dependencies
- Logging for configuration changes and authentication
- End-of-life, vulnerability, and replacement notification process
Panels and enclosures
Panel location affects cable length, voltage drop, network resilience, service access, environment, and tamper risk. Provide working space, labeling, grounding or bonding as required, branch-circuit identification, battery clearance, heat management, separation of voltages, surge protection, and secure access. Avoid locations exposed to water, uncontrolled heat, public traffic, or routine obstruction.
Retrofit and open-hardware questions
Some software platforms support widely used third-party intelligent controllers; others use proprietary field hardware. Either approach can be appropriate, but owners should understand which components can be retained during a platform change, who can obtain replacements, what certification the integrator needs, and how firmware and licensing are controlled.
Commissioning record
For each controller, record model, serial number, firmware, network identity, enclosure, power supply, battery, modules, addresses, reader ports, doors, inputs, outputs, relay ratings, licensing, administrator ownership, offline test, event-buffer test, tamper test, and backup date. Label field wiring consistently with the drawings and software names.
Questions before selection
- How many openings and users are required now and in five years?
- Which decisions remain local during every expected outage?
- Are controllers shared across buildings, floors, or tenants?
- Can doors be migrated in phases without a complete cutover?
- Are spare modules, power capacity, and enclosure space available?
- Which integrations depend on a particular controller or firmware?
- Who owns licenses, accounts, backups, and cryptographic keys?
Continue with credentials and readers, door monitoring and request to exit, and power and wiring.
Information only. Controller, network, power, and life-safety requirements must be confirmed for the selected platform and actual openings.
Publisher’s related applied reference: commercial access-control system application.