Video Surveillance: overview

How a modern IP video system fits together and how this track is organized.

⏱ ~10 min

🎯 Learning objectives

See the end-to-end video chain from lens to operator
Know which module answers which design question

Every IP video design answers the same questions in the same order: what do we need to see (operational requirement), which camera and lens can deliver it, how many pixels are on the target, how the video is compressed, how it moves across the network, where it is stored and for how long, how operators use it (VMS, analytics, integration with access control), and how it is protected.

The video chain. Each box is a module in this track.

Module	Design question it answers
Codecs and bitrate	How big is each stream, and how do I control it?
Camera types	Which form factor fits this location and task?
Sensors, lenses, WDR and low light	Will the image be usable at night and against bright backlight?
Resolution and pixel density	Do I have enough pixels on target to identify a person?
PoE and network design	Can the switches power the cameras and carry the traffic?
Storage and retention	How many terabytes for the required retention?
VMS architecture	Which servers and roles, on-prem, edge or cloud?
Cybersecurity hardening	How do I keep cameras from becoming the weakest link?
Video analytics	What can the system detect automatically, and how reliably?
Tying video to access control	How do door events and video work together?
Design lab	Put it all together for a real site.

Vendor examples

This track uses Genetec Security Center (Omnicast for video, Synergis for access control) and Axis cameras as reference examples because they are widely deployed and well documented. Concepts apply to any open-platform VMS and ONVIF-conformant camera. Always confirm feature support for the exact model and firmware on the vendor's documentation.

Video Surveillance: overview

Modules