Distinguish detections from events
Video can produce many observations of one continuous situation. If every frame or track update generates a new notification, operators receive repeated messages instead of a useful incident history.
Define an episode
Specify when the event begins, which observations belong to it and what ends it. Object identity, zone membership, elapsed time and external equipment state may be relevant. The available blocks and parameters depend on the deployed version.
Choose an appropriate repeat policy
A suppression period can reduce noise but can also hide a new incident. Test short interruptions, two different people entering the same zone, camera reconnects and cases where the original risk remains unresolved.
Keep enough context for review
Retain the evidence and version information needed to explain why events were grouped or repeated. Compare notification volume with labelled episodes, not only with the number of model detections.
Validate against missed events
Every change to grouping or suppression should be checked against missed and delayed events. The target is a usable operational signal, with a repeat policy appropriate to the task.
Read the scenario methodology.