DW Spectrum IPVMS and DW Cloud Planning
DW Spectrum separates recording services from client viewing and can connect sites through DW Cloud. A successful deployment depends on server sizing, supported devices, user roles, network design, retention and a controlled update process.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the design.
Server, client and site architecture
Map cameras, sites, concurrent users, viewing stations, analytics, integrations and retention before sizing servers. Decide whether one site uses a single server or a multi-server layout. Separate client workstations from recording servers when workload, security or operator ergonomics require it.
Write the sizing inputs as numbers a server build can be checked against: stream count and bit rate per site, days of retention, peak concurrent viewing sessions, and which analytics run on cameras versus on the recording servers. Record who holds the administrator role, since that shapes how sites are grouped and who can change configuration later.
- Camera and stream inventory
- Server and client roles
- Retention and storage target
- Multi-site and failover goals
Licensing, cameras and integrations
Verify each camera model and required stream, codec, resolution, frame rate and analytics path. Document licenses, failover expectations, video-wall needs, mobile access and integrations such as access control or analytics plugins. Compatibility must be checked against the intended software release.
Order against the verified list, not the marketing sheet. A camera family can share a name across models whose codec support, analytics options or license type differ, and a plugin may need a specific software release. Record which release each integration was checked on, so a later upgrade is reviewed against those integrations before it is applied.
- Supported cameras and plugins
- License ownership and counts
- Video wall and mobile needs
- Integration version matrix
| Layer | Purpose | Confirm |
|---|---|---|
| Media Server | Recording and system database | Capacity, storage and support |
| Client | Viewing and administration | Workstation and monitor workload |
| DW Cloud | Remote site association | Ownership, users and connectivity |
| Integrations | Access, analytics and APIs | License and version compatibility |
Users, remote access and cybersecurity
Create named roles for operators, investigators and administrators. Protect Cloud and local accounts with appropriate authentication, restrict exported-video permissions and review internet, firewall, DNS and time dependencies. Remote access must preserve auditability without exposing unnecessary services.
Use multifactor authentication wherever the Cloud and local account types support it, and keep export rights with a short list of named investigators. Assign owners for configuration backup, server health alerts and after-hours escalation. Before any server or client update, read the release notes and keep a way back to the version currently running.
- Named users and least privilege
- Cloud ownership and recovery
- Firewall, DNS and time services
- Export and audit controls
Updates, backup and acceptance
Back up the database before upgrades, read release notes and confirm supported operating systems, server models and plugins. Stage changes where practical, then test cameras, recording, search, export, mobile, Cloud and integrations. Keep older appliances on their supported release when hardware limits prevent a safe upgrade.
Sign off the upgrade the same way the original system was accepted: pull a server power cord and a network link, confirm recording resumes and the event log shows the gap, then check notification and an administrator recovery path. Hand over the database backup, license keys, server serials and the exception list for appliances held back.
- Database backup and release notes
- Supported OS and hardware
- Post-update functional tests
- Official download and rollback record
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Size servers
Match recording server hardware and disk to the camera load, stream count and retention each building expects.
License cameras
Record the channel licenses required per server and confirm which cameras and integrations are supported before anything is ordered.
Build the system
Install servers, merge sites into one system, set user roles, and connect remote access through the cloud service.
Control updates
Establish a version baseline, back up the database and configuration, and schedule updates rather than applying them on release.
Information to gather before design
Server sizing, licensing and user access are decided together in a video management deployment, so gather the camera and network facts before hardware is ordered.
- Camera models and stream configuration
- Recording server locations per building
- Viewing clients and video wall needs
- User roles and remote access requirements
- Existing network segments and firewall rules
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is the DW Spectrum Client the recording server?
No. The Media Server records and maintains the database; the Client is the user interface.
Does DW Cloud replace local recording?
No. It provides remote connectivity and site association while recording remains on the media servers.
Should every server be updated immediately?
Review release notes, hardware, operating-system and plugin compatibility and back up first.
Where should software be downloaded?
Use Digital Watchdog’s official support, Cloud or product download portals.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Plan a DW Spectrum deployment across your sites
Tell us how many cameras each building records, where viewing stations sit, who needs remote access, and what retention the site requires. We will size servers, licensing and the cloud connection around that.