Practical guide
Honeywell DVM: assess recording and operational continuity
Assess cameras, servers, storage, licences and recovery tests without assuming retention or compatibility.
A live camera view does not prove that video is recorded, can be retrieved later or may be exported by the user. Honeywell Digital Video Manager (DVM) assessment should connect every camera to its server, storage, licence and operational need.
Manufacturer reference
The public DVM 2025 brochure describes map-based oversight, DVM Status for camera and server health, and audit log investigation. It also presents integration with EBI and CCS. Usable site functions must be checked against the installed release, architecture, licences and camera compatibility matrix.
Information to gather
- DVM release, servers, workstations, operating system and database.
- Camera, model, firmware, configured stream, location and channel condition.
- Recording server, available capacity, disks, retention policies and fault records.
- Licences, system interfaces, users and viewing and export permissions.
- Network dependencies, clock synchronisation, backup power and configuration backups.
Tests supporting operations
| Function | Verify | Closing result |
|---|---|---|
| Live video | Required channel, identity, state and quality. | Record identifying the assessed channel. |
| Recording and search | Requested period, playback and timestamp alignment. | Result validated with operations. |
| Authorised export | Permission, exported file and evidence playback. | Access-controlled handover. |
Retention, security and changes
Retention depends on capacity, configuration, activity, video quality and the agreed policy; do not promise days without calculation and verification. Validate compatibility by model and firmware. A known camera protocol does not guarantee every required function.
Video evidence and personal data require permissions and protective measures. An upgrade needs backups, a work window, contingencies and recovery tests for agreed functions. A commercial brochure is not evidence of uninterrupted continuity.
Diagnosis and follow-up
Deliver camera-level and server-level records, prioritised findings, recurring faults, verified functions and outstanding actions. Storage, replacement and upgrade recommendations should connect to actual needs and operating cost. Acceptance must assess user functions as well as server health.
How BBS organises the work
- Initial assessmentInventory, fault history and criticality.
- Intervention planScope, permissions, owners, contingency and acceptance.
- Execution and testingChange control and verification of authorised interfaces.
- Handover and follow-upEvidence, validated results and outstanding actions.
Sources and scope
Public reference sources checked on 5 October 2026. This BBS guide provides planning recommendations; applicable editions and requirements must be validated for each project.
LET’S TALK