PLATFORM GUIDE
AI video analytics software for existing CCTV
Video analytics evaluates selected events in camera feeds. Check the intended task, technical fit and evidence before choosing software for your business.
What video analytics software does
Straight answer: video analytics software reads a feed from cameras that are already installed and flags one defined event — a person crossing a boundary, a vehicle stopping where it should not, a camera that has gone dark — so a person reviews the exception instead of watching every screen. The decision worth making is which single event it must detect, and what evidence shows it does so on your own cameras.
What the analytics layer does
A scoped analytics deployment evaluates a defined event rather than asking someone to watch every feed continuously. The exact PGAK function and output must be demonstrated on the proposed configuration; the capability register distinguishes missing proof from available features.
Read capability and evidence status →Four decisions before a pilot
- Choose one observable problem: perimeter events, attendance exceptions or unavailable camera feeds.
- Check stream compatibility, placement, lighting, network and processing requirements.
- Agree authorised data use, evidence format, recipient and human response.
- Define acceptance criteria including false alerts, missed events, delays and outages.
Analytics is not the same as a VMS
Recording, playback, storage retention and user permissions need their own specification. A full PGAK replacement VMS is unverified; describe the role of the existing recorder explicitly.
Explore VMS integration requirements →Compare requirements, not blanket promises
A claim to work with every camera, need no hardware or eliminate false alarms is not a useful acceptance criterion. Use dated configuration records and representative tests. A successful scene demonstration is not a measured accuracy study.
Use the evaluation method →What a project here involves
Compatible cameras and recorders you already own are reused wherever they are suitable. Detection runs on an on-site processing unit, and camera suitability, stream access, processing hardware and network are all confirmed at the assessment — with anything extra itemised in the quote before you commit.
What the quote is made of
| Component | What decides it | Price |
|---|---|---|
| Cameras reused | Which existing cameras give a usable view for each use case — confirmed on a still image of each view. | Quoted per site |
| Cameras moved or added | Only where a use case needs a view no camera has (plates and faces usually do). Each one named in the quote. | Quoted per site |
| On-site processing unit | Detection runs here, next to the recorder. Model, quantity and warranty depend on camera count and analytics. | Quoted per site |
| Software / licences | Which analytics on which cameras, the term, and the basis for renewal. | Quoted per site |
| Installation and configuration | Stream setup, zones, schedules, alert routing and commissioning. | Quoted per site |
| Pilot | Agreed scenes, acceptance criteria and duration before rollout. | Quoted per site |
| Support | Hours, response versus fix time, and who replaces failed hardware. | Quoted per site |
| Taxes | Stated separately on the quote. | Quoted per site |
How it is evaluated
- 1. Self-check — Two minutes, nothing sent — find likely blockers.
- 2. Scope on paper — Cameras, use cases and acceptance tests, written down.
- 3. Site assessment — PGAK checks streams, views and network on your cameras.
- 4. Pilot against criteria — Precision, recall, false alerts and delay, agreed in advance.
- 5. Written proposal — Itemised as above; you decide whether to roll out.
Evidence for this page
No PGAK recording is published for this page yet. The capability register shows what has been demonstrated and under what conditions.