From camera footage to a defensible infraction

Every car park has its own rules — permitted duration, grace periods, permit holders, time-of-day restrictions. A movement in and a movement out mean nothing until they are measured against the right rule set.

Getting this wrong in either direction is expensive: miss real infractions and the operator loses revenue; flag compliant drivers and the operator inherits a queue of appeals it will lose.

The system pairs entry and exit events into parking sessions, then evaluates each session against the limits configured for the car park it occurred in.

Sessions that break the rules of stay are identified as infractions and exported to the Vehicle Management System, where they are enforced through the normal warning or charge notice process. The two systems are deliberately separate: this one decides what happened, the enforcement platform decides what to do about it.

• Session pairing Camera-captured entries and exits are resolved into complete parking sessions.
• Per-car-park rules Each session is measured against the limits configured for that specific site.
• Infraction export Confirmed breaches flow into the Vehicle Management System for enforcement.
• Clean separation Detection and enforcement stay in separate systems, each auditable on its own terms.

A processing layer ingests camera movement data, a rules layer applies per-site parking conditions, and an export interface hands verified infractions to the enforcement platform.

Operators get infractions that have already been tested against the rules of the specific car park, rather than raw camera data somebody has to interpret.

Because detection is separated from enforcement, each stage can be evidenced independently when a notice is challenged.