Security / Existing CCTV

Give activity a boundary. Give alerts a reason.

Add a computer vision monitoring layer to suitable existing cameras. Detect presence, measure time in a zone and flag a configured change in activity without identifying the people in view.

Monitor a visible zone, not a whole building
Monitor a visible zone, not a whole buildingAn overhead plan has a solid building across its top and an open forecourt beneath it. A monitored zone is wholly within the forecourt. A conceptual presence marker is inside the zone; the building interior is explicitly outside the monitored area.EXTERIOR / OVERHEADBuilding interiorNot monitored hereOpen forecourtDefined zonePresenceZone + dwell time + rule

The shaded zone is an analysis region in a suitable camera view, not a camera cone. Presence or dwell time can trigger a configured rule for a person to review. Illustrative, not live data.

Build the monitoring brief

Start with a zone, not a suspicion.

Define what is visible, what is expected and when a change should reach your team.

01 / Observe

People & flow

Detect and count people, understand entry and exit flow, occupancy levels and presence patterns within the monitored area.

02 / Define

Independent zones

Set virtual zones inside each camera view, with their own activity thresholds and rules. Loiter-time analysis measures how long a presence remains in a zone.

03 / Review

Useful evidence

Use historical dashboards, trends and CSV exports for incident review and operational planning. An alert signals a condition; it does not identify intent.

The alert playbook

Choose the condition that matters.

Rules can monitor an absence of expected activity as well as increased activity or dwell time.

No activity

No people or vehicles are detected in a zone for a configurable period. Choose the relevant zone and period for the operation.

No vehicles

Expected vehicle activity has stopped. This can prompt a review of access, operations or the monitored view.

No pedestrians

Expected foot traffic has dropped to zero in a monitored area.

Volume threshold

The people or vehicle count exceeds a configured limit within a defined time window.

Loitering detected

A detected person remains in a zone beyond the configured dwell time. This flags duration for review, not identity or intent.

Alerts are evaluated on a configured cadence and delivered near real-time. They are signals for review, not a guarantee of immediate detection. Models and rules can be configured per tenant, device and location; custom alert types can be scoped for your workflow.

Where it fits

An analytics layer for the cameras you have.

Assess existing infrastructure and the operational question before adding or changing equipment.

Retail & commercial CCTV

Understand customer flow, peak periods and zone utilisation using suitable existing views.

Building perimeters

Monitor visible restricted areas or after-hours presence with object-based analytics rather than relying only on simple motion detection.

Car parks

Review occupancy, activity, prolonged dwell and unexpected drops in traffic.

Campuses & estates

Compare zone activity across multiple cameras and understand recurring foot-traffic patterns.

Construction sites

Monitor visible access points during and outside working hours, with aggregate reports for site management.

Public spaces

Use activity patterns to inform staffing, lighting decisions, resource allocation and safety reviews.

An important distinction

An object track is not an identity.

Computer vision connects detections across frames so it can measure movement and dwell time. It does not need a name or a face.

Keep the scope visible

Standard analytics use aggregate statistics and zone-level activity. No facial recognition, personal identification or identity tracking between sites is needed.

Blind spots remain blind spots. Zones must be within the usable camera view; analytics do not replace site procedures or human review.

Configure, then test

Models and rules are configurable for each tenant, device and location. New alert types or detection models can be scoped with the engineering team.

The public demonstration focuses on traffic. Use a site pilot to test whether security analytics answer your particular question.

Start with a conversation

What should your team be told about?

Describe the site, existing cameras and the activity that needs attention. We can assess feasibility and scope a pilot.

Discuss your project
Direct to Percepta

Tell us about your site

Describe your site, your cameras and the question you need answered. We can discuss the right approach for your project.

EDINBURGH, SCOTLAND
UK & INTERNATIONAL ENQUIRIES

Send a secure enquiry

All fields marked * are required.

Please do not include passwords, payment-card details or sensitive personal information.

We use the details you provide to review and respond to your enquiry and protect the form from abuse. See our privacy notice.

Your choice

Optional video settings

These demonstration videos are hosted by Google/YouTube, separately from Percepta's on-device camera analytics. Loading a player sends your IP address to Google/YouTube and may let it use cookies or similar storage for measurement and advertising.

No YouTube player connects until you allow YouTube and explicitly load a video. Allowing here does not load any videos. Each player needs its own Load action, then Play; nothing starts automatically.

Your choice stays in memory while you browse these public pages and resets on a full page reload. We do not save a preference cookie or use browser storage.

Turning videos off immediately removes all loaded players. It cannot erase information YouTube has already received or cookies it has already set.

YouTube videos: off.