Cloud-managed IP access control designed around reader-controller devices and centralized web administration.
Products and selection guidance
ISONAS systems place access intelligence at the reader-controller and use Pure Access for users, schedules, events and multi-site management. Current ownership/product naming under acre security and software lifecycle should be confirmed. Define cloud account, network segmentation, power, offline decisions and credential policy.
- Pure Access cloud organization and site administration
- Users, schedules, events and remote door commands
- Network/cybersecurity and outage behavior
- Existing ISONAS hardware/firmware migration
- Door, lock, free-egress, accessibility and fire-alarm requirements
- Network, power, standby battery and outage behavior
- Current licenses, subscriptions, firmware and integrations
- Administrator training, backup, documentation and maintenance
Site-specific design
Boston High Tech inventories existing equipment and validates current manufacturer compatibility before specifying reuse, migration or replacement. Qualifications may be confirmed privately when needed; license numbers, certificate copies and named certificate-holder details are not published.
Request a manufacturer-specific consultation
Projects are supported from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For ISONAS Pure Access Cloud and Software Management, 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 reader-controller architecture, Pure Access administration and what changes when access intelligence sits at the door.
What is a reader-controller, and how does it differ from a panel in a closet?
A reader-controller is one device at the opening carrying the access intelligence, instead of a reader at the door wired back to a controller in an electrical room. ISONAS is designed around that arrangement, so equipment at the door goes up while panel count in the closet goes down. Pure Access then administers those devices centrally.
Where does the network cable have to reach with reader-controllers?
To each opening, because these are IP access-control devices at the door rather than panels in a closet, so every controlled door needs a cable path, a switch port and a power arrangement. Plan network segmentation for those ports in the same exercise, and flag openings whose cable route is long enough to drive the construction schedule.
Does existing ISONAS hardware move onto Pure Access?
Inventory answers that, opening by opening. Existing ISONAS hardware/firmware migration sits on the list of items defined for the design, alongside controller, reader, lock and credential compatibility. Record the model and firmware at each door during the walk, then check them against current manufacturer compatibility, so reuse, migration or replacement is specified per device instead of as one blanket call.
Can a manager unlock a door from Pure Access without walking to it?
Yes. Remote door commands are listed among the Pure Access functions, alongside users, schedules and events. The question to settle in the same conversation is which operator roles may issue those commands, since cloud administration and ownership are an open decision on this page, and a remote unlock is only as controlled as the account able to issue it.
Does Pure Access handle several buildings from one account?
Yes. Pure Access is described with multi-site management, using a cloud organization with site administration underneath it. Decide early how sites are divided, because that structure is what a local manager sees and what a regional administrator inherits. Users, schedules and events are then administered inside that structure rather than in one undivided list.
Is ISONAS still a current product line under acre security?
This page is explicit that current ownership and product naming under acre security, along with the software lifecycle, should be confirmed for the project at hand. Ask for that in writing when the quote is issued and carry it into the as-built documentation, so device labels, the account name and the support contact still line up years later.
ISONAS owner, administrator and buyer resources
Discuss ISONAS installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official ISONAS 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.