Protect & respond · Feature guide

Abandoned object detection CCTV

Two opposite problems share one technique: something left behind that should not be there, and something removed that should be. Both are detected by learning what a monitored area normally looks like and flagging a change that persists. A bag in a lobby corner and a missing trolley from a marked bay are the same kind of event to the software.

How it works

Flag an object left in a monitored area beyond a set time, or one removed from a place it should occupy.

Where it could help your business

Review a bag left in a lobby, or equipment missing from a marked bay.

Pick areas where "normal" is genuinely stable. A corner that is empty all day works; a corridor where stock moves constantly will alert all day until the thresholds are loosened so far that they catch nothing. Set the dwell time deliberately, and expect a tuning period on your own site before the alerts are worth acting on.

What your camera setup needs

Needs a stable camera view and a defined normal state. Busy scenes, moved furniture and changing light all raise false alerts until tuned.

Will it alert every time someone puts a box down?

It will until it is tuned. The threshold is how long an object must stay before it counts, and that number has to be set per area against your own activity. Expect to adjust it during the first fortnight rather than accepting a default.

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 · C22

Abandoned and removed objects: 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 = events × (old − assisted) ÷ 60 − exception hours

Worked example (illustrative inputs)

80 events; 5 old; 2 new; 1 exception hour.

staff time released: 3 hours a month.

Formula version 1.0.0.

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.