Open video management and appliance/recorder options for Hanwha and supported third-party cameras.
Product and system guidance
Wisenet WAVE supports Hanwha and many ONVIF/RTSP devices, but feature depth depends on the device integration. Size servers/NVRs by streams, motion, retention, analytics and failover. Define desktop/mobile/cloud connectivity, user roles, health monitoring and export workflow.
- WAVE server/client and multi-server system design
- Hanwha NVR/appliance and PoE deployment
- Device compatibility, ONVIF and metadata support
- Storage throughput, retention, redundancy and remote access
- Scene survey, pixels on target, lens and mounting
- Bandwidth, storage, retention and evidence export
- Firmware, cybersecurity, user roles and remote access
- Current regulatory, procurement and customer compliance requirements
Engineering before procurement
Boston High Tech validates current model availability, firmware, licenses, analytics, VMS compatibility and storage calculations. We do not publish private certificate numbers or named certificate-holder records; qualifications can be confirmed through appropriate private channels.
Request a video-system design review
Serving projects from our Charlotte headquarters and local client offices in Massachusetts, New York and New Jersey. Office visits are arranged in advance.
Official manufacturer references
How to compare and specify this product family
For Hanwha WAVE VMS, NVR and Recording Storage, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following video-surveillance system decisions before equipment is ordered:
- Scene purpose and required pixels on target
- Lens, mounting height, WDR, IR and low-light needs
- Analytics supported by the selected camera and VMS
- Bandwidth, PoE and network segmentation
- Retention, storage throughput and export workflow
- User roles, cybersecurity, health monitoring and support
Installation, testing and handoff
Design starts with the evidence or operational result required at each scene—not megapixels alone. We document fields of view, identification targets, lighting, camera placement, network load, recording profiles and retention assumptions. Commissioning covers focus, exposure, time synchronization, analytics calibration, user permissions, mobile or remote access, export testing and health alerts. Final documentation records device names, locations, addressing, retention settings and administrator procedures without publishing private credentials.
Frequently asked questions
Sizing questions we field on Wisenet WAVE servers, Hanwha recorders and storage for cameras already on the network.
Will WAVE take the third-party cameras already on our network?
Wisenet WAVE supports Hanwha devices and many ONVIF/RTSP cameras, but feature depth depends on the device integration, so a camera that connects may still not expose every setting or metadata stream. Each model is checked against Hanwha’s published list of compatible devices before it goes on a reuse list.
Do we buy a WAVE server or a Hanwha recorder?
A WAVE server is software you size to the load and can extend into a multi-server system as sites or cameras are added, while the Hanwha NVR and appliance options arrive as configured recorders and are considered together with their PoE deployment. Stream count, retention, analytics and whether failover is required point toward one or the other.
How do you size the recorder for what we want to keep?
By streams, motion, retention, analytics and failover together, not by camera count. Storage throughput carries as much weight as capacity, because a disk set can hold the retention window and still not sustain the write and playback load during an export. The proposal states the stream, retention and throughput figures it was sized to, so later additions get measured against them.
What should we ask for on redundancy?
Start by naming which cameras must keep recording if a server or appliance stops, because that requirement is what failover and storage redundancy get sized against. A retention commitment that assumes every server stays up is not a commitment. Put the requirement into the design before hardware is quoted, so redundancy is priced rather than promised.
Can managers view cameras from a phone or from home?
Desktop/mobile/cloud connectivity is defined during design, along with the user roles attached to each way in. Remote access drives network and firewall work as well as who sees which cameras, so the role list is agreed before accounts are created. A manager who can view every camera from anywhere is a policy choice, not a default.
How would we find out a camera stopped recording?
A recording fault surfaces through health monitoring, and the design names who receives that alert and what the recipient does next. Device health, firmware status and user roles are reviewed on a schedule rather than only after an incident, and the export workflow is documented at the same time so an evidence request does not rest on one person’s memory.
Hanwha Vision owner, administrator and buyer resources
Discuss Hanwha installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official Hanwha Vision 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.