An on-premises access-control system places management software and data under a locally managed infrastructure model. The application may run on a physical or virtual server; controllers at the openings may retain their own rules and event records. The exact architecture must be documented rather than inferred from the term “on-premises.”
When to evaluate local management
Local management may fit an organization with established server operations, defined data-location requirements or an existing enterprise platform. It is not automatically more secure or more suitable for every hospital, school or industrial property. The quality of administration, network design, patching, recovery and physical hardware matters.
Compare local management with cloud, hosted and embedded options using the same operating requirements. Include administrator availability, remote-site connectivity, integration needs, support lifecycle and recovery capability.
Separate server operation from door operation
A management-server failure does not necessarily stop every controller, and an internet outage does not necessarily affect a local door decision. Define which credentials and schedules are held at controllers, how events are buffered, and what changes require the management service. Genetec’s Synergis architecture documentation is one example of a distributed design; verify the corresponding behavior for the selected platform.
Assign infrastructure responsibilities
- Supported operating system, application and database versions.
- Server capacity, storage, time synchronization and certificates.
- Network segmentation, authorized connectivity and remote-support controls.
- Named administrator accounts, appropriate authentication and least privilege.
- Backups, restoration procedures, recovery access and retention.
- Updates, license records, end-of-support review and replacement planning.
Plan recovery before deployment
Record the required recovery time and acceptable data loss for management functions. Identify what a backup contains and what it omits, including certificates, integration settings or device configuration. Test restoration using an approved method. Keep recovery information available to authorized personnel when the normal management server is unavailable.
Evaluate integrations and upgrades
Document the exact supported versions for identity, video, intrusion and visitor interfaces. Coordinate upgrades across dependencies and retain a rollback plan. A supported controller board does not guarantee that every firmware or software combination is valid.
Acceptance questions
- Do doors perform the specified local functions when the server is unavailable?
- Are events and administrative changes reconciled after restoration?
- Can authorized staff restore the system from the retained records?
- Are remote support and administrator permissions limited and auditable?
- Who owns ongoing server, software, network and door maintenance?
Continue with the software and management guide and manufacturer comparison.
Publisher’s related applied reference: commercial access-control applications.