Networked access-control software, controllers, readers and credentials for commercial and institutional facilities.
What this product family does
Keyscan designs combine access-management software with door/elevator controllers and dormakaba reader/credential choices. Current compatibility, controller capacity, integrations and migration from legacy Keyscan products must be checked against the exact software and hardware generation.
Products and decisions
| Product area | What it includes | Selection guidance |
|---|---|---|
| Management | Keyscan access-management software and operator workstations | Define server/cloud path, sites, operators, reporting and backup |
| Controllers | Door and elevator-floor controller families | Size doors, readers, inputs/outputs, elevators, enclosures and power |
| Readers/credentials | Standard, high-frequency, UHF and mobile credential choices | Plan credential security and migration instead of defaulting to legacy proximity |
| Integrations | Supported lodging, multifamily and third-party workflows | Verify current versions and responsibilities before contracting |
Questions to answer before quoting
- Inventory existing panels and software version
- Door/elevator count and expansion
- Reader protocol and credential security
- Server, network, backup and support ownership
- Who owns administration, backups, updates and recurring services?
- What must continue working during network, internet or power failure?
- Which opening, egress, accessibility and life-safety requirements apply?
- What training, documentation and preventive maintenance are required?
Request a product-specific site survey
Boston High Tech serves projects from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
Capabilities and product families were checked against the manufacturer links below.
How to compare and specify this product family
For dormakaba Keyscan Access Control, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions about extending, migrating or replacing an installed Keyscan system without guessing at controller, reader and software compatibility.
Our Keyscan panels are years old. Do they all have to go?
Not necessarily, and the deciding factor is the panel generation and the software version those panels run. Migration from legacy Keyscan products is checked against the exact software and hardware generation, so the first task is an inventory of the installed panels and their firmware. That inventory is what turns a reuse question into a priced answer.
Do elevator floors need different hardware than doors?
Yes. Door and elevator-floor controller families are counted separately when the system is sized, because floor control and opening control consume different inputs and outputs. Size doors, readers, inputs and outputs, elevators, enclosures and power in one exercise so the enclosure and power supply match the final count. Allow for the doors and floors you expect to add later.
Does replacing the controllers mean pulling new cable to every door?
Not automatically. The site survey records each opening, door hardware, cable path, power and network before anyone commits to reuse, and the reader protocol you move to is what decides whether an existing home run still serves. Where the survey finds shared, damaged or undersized cable, that opening gets a new run and the others keep what they have.
Does the access-management software run on our server or in the cloud?
Either path is on the table, and the choice is made during design rather than after cutover. The Keyscan access-management software is set up with the sites, operators, reporting and backup plan it will serve, so the server or cloud decision is made alongside those. Server, network, backup and support ownership are recorded in the proposal with a named owner for each.
Will Keyscan tie into our property-management or lodging platform?
Only where that workflow is among the supported lodging, multifamily and third-party workflows for the exact software generation you are buying. Verify current versions and responsibilities before contracting, because an integration that exists in principle still needs an owner for the interface, for the data it passes and for the support call when it stops.
Can we move to mobile credentials without changing every reader?
The reader protocol on the doors today decides that, so read it before planning a rollout. Standard, high-frequency, UHF and mobile credential choices are specified as a group, and the guidance is to plan credential security and migration rather than defaulting to legacy proximity. A transition period in which two credential types stay valid is worth writing into the plan.
dormakaba owner, administrator and buyer resources
Discuss dormakaba installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official dormakaba software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.