Applies to: HealthPro Bridge

Summary

HealthPro Bridge is designed to connect compatible on-premises devices to HealthPro for cloud-based health monitoring and firmware management. When planning a deployment, the goal is not only to connect as many devices as possible, but to build an environment that remains stable, responsive, and easy to manage over time.

HealthPro Bridge is recommended for up to 200 managed devices per Bridge under the published recommended system requirements. This guidance is intended to help users build reliable real-world deployments across single sites, large campuses, and multi-site environments.

The right deployment model depends on several factors, including site size, subnet structure, device density, available PC resources, and whether the Bridge is installed on a dedicated machine. Network segmentation is also an important design consideration: placing devices in appropriate Class C or custom-sized subnets can limit broadcast and discovery scope, support firewall and access control policies, isolate faults, and make traffic and device ownership easier to monitor. The exact subnet size should be determined by the customer’s network and cybersecurity policies.

Reasons for Deployment Planning

HealthPro Bridge communicates continuously with managed devices and the HealthPro cloud. As the number of managed devices increases, so does the volume of device communication, health data collection, background processing, and hardware resource usage on the Bridge host. A larger device count may require a more capable PC or additional Bridge hosts.

Deployment quality depends on more than a raw device count. A well-planned design helps maintain predictable performance for device discovery, health data collection, status updates, and ongoing management tasks.

Published capacity guidance should be considered with the recommended PC specifications, network conditions, and installation method. Results can vary depending on the user's environment.

Deployment Guidance

For most environments, Hanwha Vision recommends sizing one HealthPro Bridge for up to 200 devices and installing it on a dedicated PC that meets the published system requirements.

This distributed model is often the most practical design for real deployments, especially when devices are already separated by site, subnet, or local infrastructure.

200 Devices Recommendation

The 200-device recommendation should be viewed as a practical deployment guideline based on the published system requirements, rather than a fixed product limitation. It represents a deployment size at which Hanwha Vision can confidently recommend stable operation under the published system requirements. As device counts increase, HealthPro Bridge must handle more simultaneous device communications, health data collection, status synchronization, firmware management activities, and background processing tasks. The recommended sizing helps ensure predictable performance, simpler troubleshooting, and reliable long-term operation in typical customer environments.

The recommended sizing reflects real deployment conditions rather than a theoretical maximum. CCTV networks are commonly organized as Class C subnets or custom-sized subnets based on site design, device density, and security policy. Keeping a manageable number of devices within each network segment can improve traffic control, fault isolation, and day-to-day administration.

• Many surveillance networks are organized by subnet, building, floor, or operational zone.
• Class C or custom-sized subnets can keep device discovery and monitoring traffic within an appropriate scope, reducing unnecessary network-wide traffic.
• Segmentation can support firewall rules, least-privilege access, and clearer separation between camera networks and other business systems.
• Smaller network segments help isolate faults, simplify troubleshooting, and make device ownership and operational responsibility easier to manage.
• Even large facilities often divide cameras across multiple smaller network segments, while multi-site organizations typically benefit from local or distributed Bridge placement instead of centralizing all devices behind one host.

This means a distributed deployment is often a better fit operationally than aiming to place every device behind one Bridge.

A good rule of thumb is to align HealthPro Bridge placement with how the customer's network is already organized. If devices are naturally separated by site or subnet, Bridge deployment should usually follow the same structure.

IMPORTANT: Deployments exceeding the recommended sizing may still operate 
successfully, but performance should be validated based on the actual 
hardware specifications, network conditions, and operational requirements.

Dedicated PC

It is strongly recommended to install HealthPro Bridge on a dedicated PC. Running it on the same machine as other resource-intensive applications, such as VMS or NVR software, can reduce predictability because those applications compete for CPU, memory, storage, and network resources. As the number of managed devices grows, the Bridge may require additional PC resources to process more device requests, health data, and background tasks. For this reason, installing HealthPro Bridge on an existing VMS host becomes increasingly difficult to recommend as the deployment grows.

Using a dedicated host helps provide:

• More consistent device communication
• More predictable health monitoring behavior
• Simpler maintenance and troubleshooting
• Cleaner capacity planning as deployments grow

Scaling Large Environments

Large environments should be scaled horizontally, not just vertically. Adding more Bridge instances is often more effective than concentrating more devices onto a single host. Although some competing edge-management products publish higher single-host device counts, those figures are not directly comparable because monitoring scope, polling intervals, supported device types, health metrics, and PC specifications may differ. A higher advertised device count should not be treated as a substitute for environment-specific capacity planning.

Examples of practical grouping

• One Bridge per site
• One Bridge per building
• One Bridge per subnet
• One Bridge per recorder or server group

Common benefits

• Lower load per host
• Better isolation of issues
• Easier expansion over time
• Closer alignment with field operations

From an availability perspective, distributing devices across multiple Bridge instances can also reduce operational risk. Concentrating a large number of devices behind a single Bridge may create a larger single point of failure, where an outage, maintenance event, or host-level issue affects a significant portion of the deployment. Distributing devices across multiple Bridges can help contain the impact of individual host failures and improve overall operational resilience.

This approach is especially useful for enterprise customers, campus deployments, retail chains, and distributed business operations.

Planning for Future Growth

HealthPro Bridge is expected to continue evolving over time, including improvements that support larger-scale management scenarios. However, deployment decisions should be based on the currently published guidance and the customer’s actual environment.

The best long-term strategy is to design for reliability first. A deployment that is distributed, right-sized, and easy to maintain usually delivers better operational results than one optimized only for the highest possible device count on a single host.