field note
Camera uptime reporting for integrators and their customers
Camera uptime reporting gives an integrator and its customer one accurate record per site and per camera. What the report should include and how to use it.
2026-10-25
Camera uptime reporting is a regular record, by site and by camera, of how much of the period each camera was reachable, shared between the integrator and the customer. A good report also lists the conditions that are open right now and the work that closed during the period, so the number comes with its explanation.
Most customers do not ask for uptime until they need footage that is not there. Then the question is how long that camera had been down, whether anyone knew, and how many others are in the same state. An integrator that already sends a monthly uptime report can answer in one sentence. One that does not is reconstructing it from VMS logs while the customer waits.
Why integrators should send it before they are asked
Camera uptime reporting does three jobs for an integrator.
It replaces opinion with a shared number. “The cameras seem fine” and “the cameras are always down” are both opinions. A per-site uptime figure, measured continuously and sent on a schedule, ends that argument before it starts.
It shows the service working. Most of what a service team does on a monitored fleet is invisible: a certificate renewed before it expired, a firmware wave pushed overnight, a card replaced on a visit that was already planned. The report is where the customer sees that work.
It sets up the next conversation. The same few cameras at the bottom of the list every month are a replacement quote. A site with falling uptime is a network conversation with the customer’s IT team. The renewal meeting starts from the report instead of from a blank page.
What the report should include
Keep it to one or two pages. A customer facilities lead should be able to read it in five minutes.
| Section | What it shows | Why it is there |
|---|---|---|
| Fleet uptime for the period | One figure for the whole fleet, plus a line over time | The headline the customer will repeat to their boss |
| Uptime by site | Each site’s figure, lowest first | Shows where problems concentrate |
| Lowest cameras | The cameras with the most downtime, named, with location | The list a technician and the customer can act on |
| Open conditions | SD cards failing or worn, certificates expiring, firmware behind, tamper events | What is going to cause downtime next |
| Work closed | Tickets resolved, firmware waves completed, visits made | The service the customer paid for |
| Planned maintenance | Windows when cameras were down on purpose | Keeps planned work from reading as failure |
Sort by the worst first. A fleet average looks fine when one site has been dark for a week, because the healthy sites outvote it. The report should make the bad camera hard to miss.
Get the definitions agreed first
An uptime number is only useful if both sides agree what it measures. Settle these before the first report goes out.
- What counts as up. The plainest definition is reachable: the camera answered when checked. A camera can be reachable and still have a black image or a failed SD card, so list those under open conditions rather than folding them into the uptime figure.
- How often it is measured. A camera checked once a day can be dark for most of a day and still read as up. Continuous measurement, rolled up to daily figures, is the honest version.
- Planned maintenance. A camera rebooting during an approved firmware window was down on purpose. Mark those windows so they do not count against the service, and show them in the report so the customer can see they were planned.
- Cameras added or removed mid-period. Count only the time each camera was under management. A camera installed on day 20 should not show 19 days of downtime.
- Site-wide outages. When a site’s connection drops, every camera there goes unreachable at once. Report it as a site event with its own cause, so it is not read as forty camera failures.
How the report changes customer service
Three things change once the customer gets the report every month.
The customer stops being the integrator’s monitoring system. Without a report, the integrator learns about failures when the customer calls, which means the customer was the first to notice. With one, the integrator can say: this camera dropped on the 4th, we replaced the card on the 6th, and here is the line on the chart where it came back.
Disputes get shorter. When a customer says a camera has “been down for months,” the integrator can show the camera’s daily uptime for the period. Either it was down and here is why, or it was up and the problem is somewhere else, such as recording settings in the VMS.
The replacement conversation gets easier. A camera past vendor support that drops every few weeks shows up at the bottom of the list every month. After a few reports, the customer usually brings it up before the integrator does.
Uptime is one view of the fleet. The fuller inventory, including firmware status, shared passwords, and published CVEs per camera, is covered in camera fleet visibility.
Doing this across 500 cameras
On a small install, uptime reporting is a spreadsheet someone updates before the quarterly meeting. Across hundreds of cameras and dozens of sites, a spreadsheet is out of date by the time it is sent, and nobody can say how a camera was doing on a specific Tuesday.
MentatNOC is a white-label managed services toolkit for security integrators. It measures every camera under management continuously and keeps the history, and each end customer gets a view-only uptime view under the integrator’s brand: fleet availability over a chosen period, 30-day uptime for each camera, and 90-day daily availability in the compliance report. Integrator and customer read the same numbers, from the same record. It monitors device health, not video.
The integrator adds it to the service contract and bundles it with the monitoring they already sell, as alarm monitoring for the cameras they already installed. When a camera drops, the alert opens a classified ticket in the integrator’s own ticketing system under their own SLA, so they can call the customer before the customer notices the gap in the report. The compliance report is described on compliance and evidence, and the live demo shows the availability views on a 500-camera fleet.