Skip to content
Camzify
Use case · Unmanned sites

Remote site monitoring

Remote site monitoring is the surveillance of facilities with no permanent security presence: substations, tower sites, pumping stations, rural depots and distributed infrastructure. A guard visiting once a day covers one hour in twenty-four. Camzify runs scheduled rounds on the site's own cameras, treats camera health as a checklist item, and puts every site on one console with its own schedule and its own person to call.

  • Rounds on schedule with nobody on site
  • Camera health checked as an item
  • Every site on one console, own schedule
A fenced substation with a mast, the perimeter outlined and a vehicle at the fence
The problem

One visit a day is twenty-three hours of nothing

Remote sites are expensive to staff and slow to reach, so they are visited on a schedule and left alone in between. Theft of cable and equipment, damage, and simple faults like an open gate go unnoticed until the next visit or the next fault report, by which time the cost has compounded.

The cameras at those sites are usually there already, recording to a box that nobody checks unless something has gone wrong. What they lack is a round that asks the right questions at the right times and a person to tell when the answer is wrong.

How Camzify handles it

The round drives out so nobody has to

An automated round visits each of the site's cameras on schedule and answers the checklist: fence intact, gate closed, no person or vehicle in the compound, equipment area clear, camera unobstructed. Each answer is recorded with the frame. A failed item messages the person designated for that camera, and a risk the AI sees that the checklist did not ask about raises a critical notification.

Between rounds, zone and line intrusion fire on a tracked person or vehicle the moment one appears, and camera tampering detection catches the site going blind, which at an unmanned site would otherwise be found on the next visit. All of it sits under one account with the rest of the estate, on the multi-site console.

The patrol round

What a remote-site round checks

A remote-site sequence is short, a handful of cameras covering the gate, the fence and the equipment, and its checklist is about the state of the site and the state of the cameras. Camera view unobstructed is on every stop, because a site that has gone blind is a site nobody is watching and nobody knows it.

Every site runs its own schedule and its own roster, so the substation on the hill and the depot in town are checked at the times that suit each and reported separately. The multi-site page covers how that is set up. Camera health monitoring is the round that matters most at a site nobody visits.

A check found Not Compliant captures a snapshot and messages the guard designated for that camera; on a manual round the operator chooses to send it, on an automated round it goes on its own. The item stays Pending until it is marked Fixed, which captures the after frame, and the report shows both.

What it will not do

It will not run without a link to the cameras; an outage is a missed round in the log, not a hidden one. It will not see a corner without a camera, and a remote site often has fewer than it needs. It will not detect an electrical fault, a leak or a temperature that the camera cannot see. And it will not attend; it tells the person designated for that camera, and the drive is theirs.

We do not publish bandwidth figures, uptime or detection rates for remote sites. The trust page sets out why.

FAQ

Frequently asked questions

Enough to carry the camera streams to Camzify. Cameras reachable from the internet connect by RTSP directly; cameras on a local network connect through the Camzify Connector on a machine at the site. We do not publish a bandwidth figure per camera, because it depends on resolution, frame rate and codec; the stream quality is detected when the camera connects.

The round cannot run against cameras it cannot reach, so the failure is logged as a missed round rather than silently skipped, and the next scheduled round runs when the link returns. Camera-side recording, where the camera has it, continues; cloud recording of that camera pauses for the outage.

Yes. Every site sits under one account with its own patrol sequences, schedule and guard roster, and the live wall groups cameras by site with a per-site online count. A site fully offline shows as such rather than as a set of frozen frames. The multi-site page covers the model.

Detections fire on a tracked object of a chosen class. An animal is not classified as a person, so a person rule stays quiet for a deer at the fence, and a vehicle rule stays quiet for both. Motion detection, which responds to any change, is a separate feature used deliberately.

Fire and smoke detection runs on the same cameras. A checklist item can ask about a visible condition, a gate closed, a cabinet door shut, a warning light off, judged from the frame at each stop. Automated rounds also raise a critical notification for a safety risk they see that the checklist did not ask about.

Whoever is designated for that camera: a mobile guard, a regional engineer, a monitoring company. Channels are set per alert category and severity per camera per detection, so a site with no one nearby can route everything critical to the people who will drive out.

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

This site is being updated

We are rebuilding pages as you read this, so an image, a link or a section may look unfinished for a while. The product itself is unaffected. If something important is broken, tell us at the contact page and we will fix it.