Skip to main content

Automated Violation Configuration

The Automated Violation Configuration feature allows administrators to configure automated parking warnings and violations captured by fixed License Plate Recognition (LPR) cameras. Its primary purpose is to automate the identification ofidentify unpermitted vehicles that remain on campus beyond a grace period and automatically issue appropriate$0 notificationswarning notices or full-fine violations without requiring manual officer intervention. This article is intended for OPSCOM administrators.

Setup and Configuration

Before you can actively relyrelying on automated warnings and violations, there are system prerequisites that must be met and initial configurations that must be established. 

Ensure thatensure your static entry and exit cameras are correctly linked within their respective Lot Groups, as the system's exit matching and grace period verification relyrelies directly on these group definitions.

Prerequisites

  1. Pre-configured Offence Type: EnsureCreate thata an existingdedicated or dedicatedexisting Offence Type (and dollar amount) isunder establishedViolations under-> Offense Types prior to configuring this feature. The system uses this exactsingle offence type to track both the $0 initial warningwarnings and anysubsequent subsequentfull violations.

  2. Dedicated Ticket Writer Account: Create a dedicated admin user account before enabling this featureaccount.. SelectingUsing a dedicated system account ensuresprevents automated tickets dofrom not mixmixing into real patrol officers' activity reports.

Admin Configuration

  1. Hover over Violations (warning icon), hover over LPR and Chalking, and click Automated Chalking Violation Config.

  2. EnterComplete the desiredrequired graceconfiguration duration in the Unpermitted Wait Time (minutes) fieldfields.:

    • Unpermitted Wait Time (minutes): Enter the grace period duration before enforcement checks run.

    • Enter the active warning duration in the Warning Cooldown (days): fieldEnter how long an active warning suppresses a second warning before escalating to a real ticket.. 

    • Click the Offence Type & FineFine: drop-down menu and selectSelect your pre-configured offence type.

    • Click the Automated Ticket WriterWriter: drop-down menu and selectSelect your dedicated admin account.

    • ReviewTemplates: or clickClick Edit next to the Warning Email Template andor Violation Email Template  to customize templateupdate messaging if needed.

  3. Click the Save Configuration button to apply your settings.

System Task Status Banner

A status banner at the top of the configuration page providesreflects the real-time informationstate regardingof the background system task (Automated Violation Job)Job: 

  • Grey Banner (Not Installed): Indicates theThe background task has not yet been deployed on your server ("The automated violation task has not been installed on this site yet").

  • Yellow Banner (Currently Disabled): The task is installed on the server but is currently disabled in system settings.

  • Yellow Banner (Enabled but Unconfigured): The task is enabled, but required configuration settings (Offence Type or Automated Ticket Writer) are missing.

  • Green Banner (Fully Working): The task is installed, enabled, and fullyactively configured to process unpermitted vehiclesrunning.

Using this Feature

Once configured, the background job automatically evaluatesprocesses unpermitted vehiclefixed-camera reads captured by fixed cameras and applies enforcement rules acrossin two progressive stages:

  1. Fixed Camera Capture: An unpermitted vehicle enters campus and is scanned by a fixed entry camera. Handheld or officer-initiated LPRofficer scans doare not trigger this featureexcluded.

  2. Grace Period & Exit Verification: The system startswaits for the Unpermitted Wait Time timerto elapse. If a matching exit read is detected within the lot group before the timer expires, the vehicle has departed andgroup, no action is taken.

  3. Driver Lookup: If no exit read is found, the system identifies the vehicle's registered primary driver on file. Unrecognized or unregistered plates are automatically skipped.

  4. Automated Enforcement Execution:

    • First Occurrence: If no warning exists within the Warning Cooldown window, the system generatescreates a $0 warning ticket under the designated ticket writer account and emails the warning template to the driver.

    • Repeat Occurrence: If a warning was received within the Warning Cooldown window under this offence type, the system automatically issues a final, full-fine violation and emails the violation templatenotice. 

Key Information Displayed

  • Unpermitted Wait Time (minutes): Specifies how long an unpermitted vehicle can remain on campus after an entry read before enforcement checks execute (Default: 30 minutes). 

  • Warning Cooldown (days): Defines the timeframe during which an initial warning remains active against the driver's account (Default: 90 days). 

  • Offence Type & Fine: The specific violation type assigned to both $0 warnings and repeat violations. Using a single offence type allows the system to distinguish between this feature's warnings and unrelated warnings. 

  • Automated Ticket Writer: The administrative account recorded as the issuing officer on automatically created tickets.

Best Practices and Considerations

  • Use a Dedicated Ticket Writer Account: Always select a dedicated administrativesystem account for the Automated Ticket Writer field. Thisto ensures clean separation inkeep officer performance reports and audit logsclean.

  • Verify Camera Lot Groups: Ensure entry and exit cameras are accurately groupedlinked in lot configurations,configurations as exit matching relies directly on these definitions to clearso departed vehicles clear properly.

  • Driver-Based Tracking: Cooldown history is tracked per registered driver account rather than per vehicle plate, ensuring warning limits follow the personuser if they switchacross vehicles.

  • Two-Stage Escalation Limit: This feature supports exactly two levels: a $0 warning notice followed by a single full violation. Further escalations (such as automatic booting or towing flags) are not supported and must be handled manually by patrol staff.

 

Back to top