INDUSTRY WORKFLOW
AI CCTV evaluation for factory operations
Start with a factory workflow: gates, restricted production areas, shift change or after-hours access. Define the event and operating response before selecting analytics.
Start with the operating workflow
Security controls the gate while supervisors manage shifts and authorised contractor movement. A production-line view is a different task from a perimeter view; agree separate requirements and owners.
Define an observable event
Entry into a restricted maintenance zone outside a permitted window, or an attendance exception at the selected staff gate.
Limitations to test
Busy shifts, PPE, dust, glare and machine movement affect performance. Analytics is supplementary monitoring; it is not certified machine guarding, protective equipment or a replacement for safety procedures.
Technical requirements
- Views suited to the chosen task, accounting for machinery, dust and occlusion.
- Shift schedules, contractor exceptions and authorised enrolment where relevant.
- Processing, network and an operating response agreed with security and production.
A scoped deployment example
Illustration: select a gate and a restricted stores area for different tests. Keep the guard's operating process and existing recorder in place while reviewing the pilot findings.
Acceptance-test approach
Sample normal shifts, changeovers, authorised maintenance and closed hours. Log useful and missed events and nuisance alerts. Stop or revise the pilot if it disrupts operations or fails agreed acceptance criteria.
Use the evaluation worksheet →Available evidence
PGAK has published recorded demonstrations of its own (listed on the evidence page), each with its conditions and limits. No customer result or measured accuracy report is published yet, and the deployment scenarios are illustrations, not verified deployments.
No PGAK recording is published for this use case yet, so it is not listed as an available capability. Ask for evidence of the exact workflow you need.
Inspect evidence status →Cost drivers and responsibilities
Camera count is only one input. Include processing, site preparation, configuration, integration, support, taxes and contract terms. Agree who maintains the feeds, reviews events and responds during an outage.
Understand project pricing →Privacy and safety boundaries
Separate security and attendance purposes. Limit identification access and ensure workers can raise corrections before any employment decision.
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.
Discuss this use case
Send a callback request with this page’s context. Camera count is optional; do not include credentials or footage.