Every tour has a gap. Know where yours is.

Two kinds of tours on a monitoring wall.

Operators use the word “tour” for two different things, and both create coverage gaps.

PTZ guard tours move one physical camera. A pan-tilt-zoom camera steps through stored presets — the gate, then the loading dock, then the fence corner — pausing at each for a set time. One camera covers several areas, but only one at a time. While it looks at the dock, the gate is not being recorded by that camera at all.

Cycling views (sequences, salvos, layout tours) move the screen. The VMS or camera dashboard rotates which cameras fill the tiles on the video wall, because there are more cameras than tiles. Every camera keeps recording, but whoever is watching live only sees a camera when its turn comes up.

Most sites run both: fixed cameras cycling through a grid, with a PTZ or two touring on top. The result is a wall that looks busy and complete, while a large share of the site is off-screen at any given moment.

Where the coverage gaps come from.

• Dwell too short. A preset or tile shown for a few seconds is a glance, not monitoring. Operators cannot read a scene that fast across a full grid.
• Cycle too long. If a camera comes back every few minutes, a fence climb or a converter theft can start and finish between visits.
• Predictable tours. A PTZ that sweeps on a fixed rhythm can be timed by someone watching it from the street.
• Analytics blind spots. Rules drawn on one PTZ preset only work while the camera is parked there. Move the camera and the tripwire is looking at the wrong place.
• Operators taking control. A guard who grabs a PTZ to follow a person often forgets to return it to the tour. The camera stays zoomed on an empty lot for the rest of the shift.
• No record of what was on screen. After an incident, nobody can say for sure whether that camera was displayed when it happened.

Designing better tours.

Then write it down. Post orders should say which cameras are pinned, which cycle, and which areas are only covered part of the time, so the client knows what they are buying. Our guide on how many cameras one guard can monitor covers the attention side of the same problem.

Know what nobody is watching.

The single most important fix for tour gaps is honesty about them. When a camera is cycled off the wall, the system — and the report — should say “not observed”, not “quiet”. A timeline that shows a blank where the camera was off-screen is far more useful than one that implies the area was clear. That matters for the guard deciding where to look next, for the supervisor reviewing the shift, and for any report written after an incident.

Where Semaphor fits.

Semaphor works from the rendered monitoring screen, so it sees exactly what the wall shows — tours, sequences and all. There is no camera replacement and no VMS integration; see what Semaphor is. Camera view tracking separates the panes, gives each camera view a visual identity from its scene and follows it as layouts cycle, resize or rearrange, so an alert stays tied to the right camera when it comes back in a different tile. A camera that cycles off-screen is marked unobserved, never assumed quiet.

Fixed tour presets are the strongest fit: each preset reads as a stable view. A PTZ under live manual control changes the scene continuously, and that remains an area of active development. Every visible pane gets person and vehicle detection the moment it is on screen, so the few seconds a camera gets on the wall are not wasted. See it on your own layout: start a pilot or book a live demo on your own camera screens.

PTZ tour FAQ