Last quarter we cut motion-camera false alerts by 41% on C-Block nights by tightening zones and adding a 10-second human verification step; response times held at a 2:35 average. For teams running Genetec or Milestone, what alert thresholds or SOP language have reduced noise without degrading threat detection during 2200–0600?
On Milestone, we cut nightside noise by tying motion to a ‘3s dwell + line-cross in’ rule and adding a 45s per-camera cooldown during 2200–0600; we kept the 10-second human verify and saw no hit to real intrusions. Small caveat: sprinters can bypass the dwell if your line is too tight, so place the line 1–2m inside the zone. If you’re on Genetec, are you using Event-to-Action ‘Aggregated events’ for the cooldown?
Genetec: 2200–0600 set ‘min object size 0.5 m2’ plus direction-in at ports; kept 10s verify — any misses on slim profiles?
It’s great to see everyone focusing on cutting down those false alerts! I’ve found that tweaking the alert zones based on traffic patterns can help, though I’ve had some issues with smaller objects slipping through occasionally. @jmoore45, have you looked into adjusting alert intensity based on the time of night?