Many businesses can connect existing CCTV to remote monitoring without starting again, but nobody can confirm it from a camera count or a brand name alone. It depends on whether the cameras show what a monitoring operator needs to see, whether the recorder can send events and images reliably, and whether the system is secure and supported. Some systems connect with configuration changes, some need targeted upgrades, and some are better replaced. A site-specific assessment decides which, and gathering the right information first makes it quicker.
Recording and monitoring are different jobs
Recording stores footage so you can review it after an incident. Remote monitoring adds an agreed process: specified events are received, an operator assesses the images, and the agreed contacts or response provider are notified.
Many monitoring services are event-triggered. A detector or a video analytics rule raises an alert, and the operator then looks at live and recorded images from the relevant cameras. Event-triggered monitoring and continuous live observation are different arrangements, so a proposal should say which applies. If the system will also need to qualify for police response, that brings further requirements. Our guide to monitored CCTV and police response explains them.
What to list before you ask for a proposal
Put together a short inventory of the system as it is today:
Cameras: makes, models and approximate ages, where each one is and what it is meant to show.
Recorder: the make and model of the DVR or NVR (or any cloud or video management platform), its software or firmware version if you know it, and how long footage is currently kept.
Camera type: whether the cameras are analogue (coaxial cable to a DVR) or IP (network cable to an NVR or switch). This often decides what is possible.
Power: where the recorder and any network switches are powered from, and whether anything is on a battery backup.
Network path: how the system reaches the internet today, if it does, and who manages that connection and the router.
Detection: any existing detectors, analytics or intruder alarm that could trigger events.
Ownership: who owns and maintains the equipment, and who holds the administrator accounts.
Do not include passwords, access codes or remote-access details in a website enquiry. Share credentials later, through a secure route agreed once the work is scoped.
What the assessment looks at
Views that work for monitoring
Cameras placed to record a yard for later review may not help an operator quickly decide whether an alert is genuine. Agree what each view needs to show and assess image detail at the distances that matter. Check for gaps at entrances, perimeters, loading areas and storage.
Night-time images and lighting
Out-of-hours monitoring depends on usable images in the dark. Review recorded night footage, not just the daytime picture. Check illumination, reflections, glare and the reach of infrared lighting against the actual scene; a camera specification alone cannot establish whether the images support verification.
Events and false alerts
Without a reliable trigger, there is nothing to respond to. The assessment should check whether existing detectors or analytics can generate events, and whether those events are likely to be set off by normal site activity, vehicles, wildlife or weather. Frequent unwanted alerts make monitoring less effective.
Connectivity and resilience
Monitoring relies on the link between the site and the monitoring centre. Check the upload capacity, whether the connection is shared with business systems, and what happens if it or the mains power fails, including who is told.
Security and support
The Information Commissioner’s Office (ICO) recommends encryption and access controls for CCTV images transmitted over the internet. Ask who maintains firmware, replaces default credentials and checks manufacturer support. An unsupported recorder may need replacing before it is connected.
What might need upgrading
Typical findings include:
Replacing an unsupported recorder, or adding equipment so analogue cameras can be integrated.
Repositioning or adding cameras where views do not support verification.
Adding detection or analytics to create reliable events.
Improving lighting or infrared coverage.
Providing a suitable connection and power backup for the recorder and network equipment.
If a proposal relies on ONVIF compatibility between manufacturers, ask which ONVIF profile is meant. ONVIF says conformance applies to a specific firmware version and can be checked in its conformant products database.
Data protection when a third party views footage
Bringing in a monitoring provider means another organisation will handle your footage. Review your data protection impact assessment and whether it needs updating. Where the provider acts as a processor, put the required written contract in place. Set retention around the purpose of the system, maintain a process for footage-access requests, and review signage and privacy information. Refer to current ICO guidance when agreeing the arrangement.
Questions to ask in a proposal
Which existing cameras and equipment will be kept, which will change, and why?
Which events will trigger an alert, and during which hours?
Who will monitor the system, and what will happen after an alert is verified?
Who is responsible for the connection, maintenance, firmware updates and fault reporting?
How will installation or upgrade work be priced separately from recurring monitoring charges?
Ask about your existing system
If you already have cameras on a commercial or industrial site, tell MCN Fire & Security what is installed, what you need to protect and when the site is unoccupied. You can request a CCTV monitoring assessment or send us your site details. Please leave passwords out of your enquiry.
Further guidance: ICO: Encryption scenarios (CCTV and video surveillance) · ICO: CCTV for your organisation, things you need to do · ONVIF: Conformant Products