A branch network is many small sites with the same handful of controlled spaces in each: the cash office, the secure room, the back entrance. The question is always the same — who went in, when, and can you show it.
A network of small estates rather than one large one, which changes both the deployment and the cost shape.
Cash office, secure room, service door. That makes configuration tight and event volume naturally low.
Audit, dispute and investigation all need the footage attached to the event rather than found later on a timeline.
Which of these apply to you, and which cameras can carry them, is what the site survey establishes before anything is proposed.
A badge opens the cash office, in or out of hours.
The camera covering the door captures the frame at the read.
Whether the person matches the credential on record.
Logged with the frame and the clip, retained for the period your policy sets.
A person detected inside a marked area when the branch is closed.
The detection frame with the area drawn on it.
Cleaner, engineer, or unexplained.
Alert to the on-call manager with the clip attached.
Movement at a back door outside permitted hours.
The doorway camera at the moment of detection.
A judgement made from the picture, in seconds.
Escalation to the nominated responders, evidence retained.
A camera is obscured, moved or stops streaming.
The last usable frame and the time it stopped.
Raised centrally rather than noticed on the next visit.
A fix scheduled before an incident finds the gap.
Each site processes locally; events reach the regional team with role-based access per branch.
Standard RTSP and ONVIF, with the recorder left doing exactly what it does now.
Door events read from your existing system during onboarding. PARVEK never controls a door.
Frame, clip, camera and time retained on the appliance for the period you set.
Capabilities are selected per site during the survey. Nothing is on by default, and several depend on camera placement and lighting — which is what the survey establishes.
Identify people, vehicles, objects and security events as they happen.
Add identity, context, movement and event intelligence to live video.
Trigger alerts, sirens, speakers, lights, guard workflows and evidence when action matters.
Camera streams, recording, playback, AI events, evidence clips, alerts, reports, users and roles and camera health — centralised in one appliance inside your premises. Faces, clips and reports stay on site.
Camera count, retention and storage are specified per appliance configuration and confirmed during the assessment.
We do not publish improvement percentages, because none have been measured across a fleet and yours would not match them anyway. What a bounded proof of concept gives you is your own numbers, on your own footage:
Each branch runs its own appliance and processes locally, with events and roles rolled up centrally. The survey works out the per-branch shape first, because a network multiplies both the cost and any configuration mistake.
No. It reads door events and pairs them with footage. Locking and unlocking stays entirely with your access-control system.
That is usually left out of configuration. The value concentrates on the controlled rooms and the out-of-hours window, where event volume is low and evidence matters most.
Retention is a site decision, bounded by storage on the appliance. It is sized during the assessment against the period your policy requires.
See how PARVEK supports this workflow.
See how PARVEK supports this workflow.
See how PARVEK supports this workflow.
Access and perimeter events across halls, cages and the site boundary, each with the footage that explains it.
Perimeter, restricted zones, yard movement and shift-change activity on a working plant.
Unmanned compounds and remote sites, analysed at the edge where the link is thin or intermittent.
AI surveillance and analytics are technology-assisted and do not guarantee prevention or detection of every security incident or 100% accuracy.