Shared technical guidance
Design the view before choosing the camera: cctv surveillance decisions
The required view comes first. CCTV surveillance design treats overview as a concrete operating case, where follow activity across a space. Each job needs different scene width, pixel density, angle and light. Resolution on the box tells only part of that story. The project timeline places the overview survey before equipment selection, followed by installation and a witnessed wide scene, low identification detail check. The written decision is wide scene, low identification detail; the related keep camera traffic predictable review then checks that choice against the site's actual users, opening or camera view, and failure response.
Retention needs rules. CCTV surveillance design treats recognition as a concrete operating case, where recognise a known person. Lens choice and mounting height follow from that. The written decision is tighter view and controlled angle; the related prove retention with playback review then checks that choice against the site's actual users, opening or camera view, and failure response.
Recording is a storage and access policy: cctv surveillance decisions
The required view comes first. CCTV surveillance design treats identification as a concrete operating case, where support a clear identity judgement. We calculate it with headroom, then test playback and export. The written decision is high subject detail and suitable light; the related keep camera traffic predictable review then checks that choice against the site's actual users, opening or camera view, and failure response.
Plate capture has limits. CCTV surveillance design treats plate capture as a concrete operating case, where read vehicle plates. The written decision is dedicated lane geometry and shutter settings; the related prove retention with playback review then checks that choice against the site's actual users, opening or camera view, and failure response.
Analytics narrow attention; they do not establish truth: cctv surveillance decisions
The required view comes first. CCTV surveillance design treats overview as a concrete operating case, where follow activity across a space. They also miss events and create nuisance alerts when the scene, light or threshold changes. Maintenance revisits wide scene, low identification detail, user access and the physical condition that could change this result after handover. The written decision is wide scene, low identification detail; the related keep camera traffic predictable review then checks that choice against the site's actual users, opening or camera view, and failure response.
Retention needs rules. CCTV surveillance design treats recognition as a concrete operating case, where recognise a known person. Sensitive uses such as face matching need a separate legal, privacy and operational review. A simpler alternative is retained whenever the site can meet the same need with a staffed, mechanical or non-analytic process. The written decision is tighter view and controlled angle; the related prove retention with playback review then checks that choice against the site's actual users, opening or camera view, and failure response.