Organise the physical context
The product description groups sources by enterprise, facility, workshop and area. Record the camera, its owner, location and applicable permissions. Use consistent identifiers when connecting reference data and events.
Define zone types
Zones represent areas relevant to a scenario, such as hazardous areas, exclusion areas or counting boundaries. The type and attributes determine how the scenario interprets the geometry. A visible polygon alone does not define event behaviour.
Bind a scenario
Assign a published scenario version to the camera. Set local zone geometry, schedule and permitted parameter overrides. Check that the scenario expects the selected zone types and that categories match the model output.
Test the local configuration
- A target event inside the relevant zone.
- A similar activity outside the zone.
- Boundary crossings and partial occlusion.
- Changes in view, lighting or source resolution.
- Correct site and source identifiers on the event.
Maintain the assignment
Record the scenario version and the camera’s local parameters. Re-test when the camera moves or when zones, thresholds and schedules change. Keep a known working configuration for rollback.
VMS mapping and zone-type reuse
Automatic camera-list import requires a compatible VMS adapter, approved access and matching reference data. Retain the external system’s source identifier, and recheck assignments, permissions and events after a VMS or camera-parameter change.
One camera may contain several polygons of the same zone type. A reusable scenario refers to that type rather than hard-coded coordinates in the shared graph. After assignment, confirm that the scenario actually receives the expected zone types; a missing or wrongly typed zone can make running analytics ineffective.