Search & investigate · Feature guide

Cross camera person and vehicle search

An incident rarely stays in one camera view. Cross-camera search helps you find appearances of a selected person or vehicle across a connected site. It can give your team a starting point for reviewing the entrance, corridor and loading bay without manually searching each recording from scratch.

Illustration matching the same delivery worker across gate, corridor and loading-bay cameras
AI-generated illustration of cross-camera target search. The scene and overlays explain the concept; they are not a PGAK screenshot or measured result.

How it works

Use a reference image to find similar appearances across connected camera views.

Where it could help your business

Review a target’s appearances between a factory entrance and production area.

Test with similar-looking uniforms and vehicles, not just an easy demonstration. Gaps in coverage, changing light and obstructed views can break the trail. Treat the suggested matches as leads for review rather than a confirmed identity or a complete journey.

What your camera setup needs

Compatible cameras, metadata and search software are needed. Similarity is not proof of identity.

Is cross-camera search the same as face recognition?

No. A system may match appearance, clothing or vehicle characteristics without recognising a face. Confirm what the chosen product actually compares and what evidence an operator can inspect.

Check it on your own site

Bring a camera model list and explain the event you want to find or detect. We can use that to scope a compatibility assessment. Ask for a written proposal naming the supported functions, processing hardware, licences and pilot checks before agreeing to an installation.

Check my camera setup →

Calculator · C02

Cross-camera search: estimate it for your site

Use your own measurements. The result is the staff time released, shown separately from any cash, using the formula below. It runs in your browser and nothing is sent anywhere.

Fields start empty. A blank is “not entered”, not zero; type 0 where 0 is true.

Money (optional)

Salary plus benefits and overheads, per working hour. Needed only if you enter a realisation above 0%.

0% unless you can name the mechanism — overtime that stops, a post not refilled, a contract reduced.

Only from your own records. May be negative.

Licences, support, connectivity. Enter 0 if there is none.

Hardware, installation, commissioning. Enter 0 if there is none.

Enter every amount on the same basis — all including GST or all excluding it. Nothing here adds or removes tax. Values are nominal rupees, not discounted.

Result

Enter your own figures, or load the worked example, to see the result.

How it is calculated

hours = cases × (cameras × old minutes per camera − new total − verification) ÷ 60

Worked example (illustrative inputs)

10 cases; 4 cameras; 15 old; 12 new; 3 review.

staff time released: 7.5 hours a month.

Formula version 1.0.0. The full standalone tool: investigation time.

What this does not tell you

  • Hours released are capacity, not cash. They become cash only through a mechanism you state — overtime that stops, a post that is not refilled — entered as the realisation fraction.
  • The 'after' values are your assumptions or pilot measurements. PGAK publishes no effectiveness figure for this feature.

Evidence status: Supplier/integration or marketed capability; PGAK availability and site performance require verification.

Request a site-specific assessment with these assumptions

Your result stays on this page either way. If you want it checked against your cameras and quotation, leave a number; mention the figures on the call. Nothing you typed into the calculator is sent with this form.

Request a camera assessment. Timing and scope agreed on the call. By submitting, you ask PGAK to contact you about this enquiry. Privacy notice.