TECHNICAL BUYER GUIDE
Deployment requirements and responsibilities
Plan processing, connectivity and the operating response together. A written scope should identify what PGAK supplies, what the site supplies and what remains unverified.
YOUR EXISTING SYSTEM01 → 04
- 01Compatible camera feedStream, view & lighting checked
- 02Processing & configurationHardware and use case scoped
- 03Event evidenceDetection and delivery tested
- 04Your team’s reviewA named person owns the response
Before the pilot
- Inventory camera feeds and recorders. Verify permitted stream access and test decoding.
- Size processing hardware against the tested analytics, simultaneous feeds and stream settings. Do not assume no additional hardware.
- Review local network capacity, internet requirements, power and recovery after an interruption.
- Agree permitted data use, authorised accounts, retention and deletion responsibilities.
Agree who owns each step
| Responsibility | Confirm in the scope |
|---|---|
| Camera and network maintenance | Named site or integration owner; access and maintenance windows. |
| Analytics configuration | Supplier role, approved zones, schedules, version and change process. |
| Alert delivery and response | Verified channel, escalation owner and actions during an outage. |
| Recording and retention | Existing VMS/recorder role, storage, permissions, exports and deletion. |
| Support | Hours, response targets, exclusions and contact path agreed in writing. |
Test interruption as well as detection
A pilot should include stream loss, reconnection, processing restart and an unavailable notification destination. Record what recovers automatically and what needs an operator.
Open the acceptance-test worksheet →