by Rabhya Sharma
How the Nexus connectivity layer is bridging new and existing entrance control to ensure integration, interoperability and remote diagnostics are plug and play.
It’s becoming essential for entrance control to be connected to wider building and security infrastructure. Gates and lanes exchange information with access control, building management, local control and service systems, often using different protocols, communication methods and generations of equipment.
On sites where equipment is upgraded over time this is significant challenge. Different generations of gates need to communicate without requiring system architecture to be redesigned every time a change is made.
A connectivity layer can manage these differences, allowing new and existing gates to operate within the same system. For phased upgrades, this means individual gates or systems can be replaced at different times while remaining integrated into the wider installation.
Interoperability across generations
Entrance control equipment can remain in service for many years, while network infrastructure, access control platforms, building systems and service applications may be replaced several times during the same period.
A connectivity architecture needs to accommodate equipment that will not all be the same age. Different gate generations and communication methods may need to operate within the same installation, particularly where upgrades are phased rather than carried out as a single replacement programme.
We’ve developed NexusBridge as a connectivity hub to communicate with different gate brands, generations and models. Its development includes the ability to communicate with different generations in parallel, including combinations of serial and TCP/IP communication. The wider architecture is intended to provide a local integration hub, with API and BMS protocol support.
This puts the differences between gate models, generations and protocols directly within the connectivity layer. Other systems can then interact through a more consistent interface, reducing the need to develop separate connections for each type of entrance equipment or having multiple applications and software to look after.
For sites being upgraded progressively, this allows existing and new equipment to remain within the same architecture while individual components change. The result is a better experience and an upgrade that becomes hassle-free.
Turning data into operational information
With NexusBridge entrance control systems are connected to our cloud-based technology solutions, EntraLinq and EntraServe Connect. These solutions are designed to make operating and maintaining gates simpler.
NexusBridge speaks directly to our EntraLinq software, providing information including status, technical and fraud alarms, event histories and usage. Making this information available in the EntraLinq app gives real-time visibility of what’s happening across an entire installation. Whether you’re on-site or on the move, EntraLinq keeps you connected to the performance of your system. And with two packages available – Essentials and Plus – you can choose the level of system reporting you need.
For service teams, NexusBridge also connects with EntraServe Connect. EntraServe Connect securely links systems to our engineers giving continuous remote access to status information, alarms and event history. Providing greater insight into a fault before an engineer attends site, EntraServe Connect and our EntraServe maintenance packages lead to faster troubleshooting, improved first-time fix rates, reduced repair times and no unnecessary call outs.
New installations and retrofit
How NexusBridge connectivity is physically implemented depends on whether equipment is being installed for the first time or added to an existing installation.
For new gates, NexusBridge is now integrated as standard through NexusConnect Native™. This hardware is factory mounted and designed to support interconnection between lanes, rather than requiring a separate external bridge to be installed as an upgrade.
Existing installations have different requirements because the equipment, control architecture, cabling and physical infrastructure are already defined. Our NexusConnect Ready ™ enabled gates make connectivity possible for existing equipment through the Bridge Lite module, with a wireless version planned for installations where reducing additional cabling and civil works is necessary.
The result is a connected system that our EntraLinq and EntraServe Connect cloud technologies are delivered ‘plug and play’ through a secure ecosystem.
A secure ecosystem
Connecting entrance equipment to wider networks also brings cybersecurity requirements at device level, as well as within the surrounding network.
Device identity needs to be established securely, communications need to be protected, stored information needs to be secured, and software updates need to be controlled. These requirements apply from initial provisioning through to the ongoing operation and maintenance of the device.
NexusBridge handles it all. It uses factory provisioning with unique credentials for each bridge and secure transfer of secrets. Authentication between the bridge and cloud uses X.509 certificates, while MQTT communications are encrypted using TLS 1.2. Firmware updates use signed images.
The hardware incorporates a TPM 2.0 chip for encryption and secure storage of keys and certificates, alongside an encrypted file system and Secure Boot. The operating system is hardened by removing or disabling unused packages, services, ports and protocols.
These controls cover different parts of the connected device. Provisioning establishes device identity, encryption protects information while it is communicated or stored and controlled firmware and operating system environments help maintain the integrity of the device after installation.
Connectivity beyond commissioning
Nexus connectivity also simplifies keeping your entrance control installation at pace with software and performance improvements. Nexus over-the-air (OTA) updates keep systems secure and up to date without needing a site visit. This same connectivity can also be an interface for upgraded functions and integrations introduced later in the installation’s lifecycle.
Our Nexus roadmap includes robust OTA updates alongside planned support for local control panels, integration APIs and BMS protocols, local intelligence and additional communication capabilities. In short, a Nexus connected installation is your gateway to entrance control that’s always up to date and secure.
Yet the architecture is not just limited to cloud-based deployments and provides a common technical point for system-wide local communication across the installation. A simpler and quicker way to deploy on-site software updates and upgrades.
What to consider when specifying connectivity
Connectivity needs to be considered as part of the overall entrance control architecture rather than as a standalone connection.
The specification needs to establish which systems need to communicate, what information needs to be exchanged, which functions need to remain local and how different equipment generations and communication protocols will be accommodated.
Cybersecurity requirements need to cover the connected device itself, while the maintenance model should account for how remote equipment information will be used by service teams.
The physical implementation also needs to be considered. For new equipment, factory-integrated connectivity can affect installation and commissioning. Existing sites may require retrofit hardware, additional cabling or alternative communication methods. Compatibility with the equipment already installed needs to be established before selecting the integration approach.
The development of NexusBridge and the wider Nexus architecture addresses these requirements through multi-generation equipment compatibility, local communication and intelligence, cloud connectivity, defined integration interfaces, cybersecurity controls and OTA update capability.
This allows existing and new entrance equipment to be connected within the same architecture, while providing the interfaces needed to communicate with other systems and support ongoing maintenance.