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 identify unpermitted vehicles that remain on campus beyond a grace period and automatically issue $0 warning notices or full-fine violations without requiring manual officer intervention. This article is intended for OPSCOM administrators.

Setup and Configuration

Before actively relying on automated warnings and violations, ensure your static entry and exit cameras are correctly linked within their respective Lot Groups, as exit matching relies directly on these definitions.

Prerequisites

  1. Pre-configured Offence Type: Create a dedicated or existing Offence Type (and dollar amount) under Violations -> Offense Types. The system uses this single offence type to track both $0 initial warnings and subsequent full violations.

  2. Dedicated Ticket Writer Account: Create a dedicated admin user account. Using a system account prevents automated tickets from mixing 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. Complete the required configuration fields:

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

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

    • Offence Type & Fine: Select your pre-configured offence type.

    • Automated Ticket Writer: Select your dedicated admin account.

    • Templates: Click Edit next to Warning Email Template or Violation Email Template to update messaging if needed.

  3. Click Save Configuration.

System Task Status Banner

A status banner at the top of the configuration page reflects the real-time state of the background task Automated Violation Job:

  • Grey Banner (Not Installed): The background task has not been deployed on your server.

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

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

  • Green Banner (Fully Working): The task is installed, enabled, and actively running.

Using this Feature

Once configured, the background job processes unpermitted fixed-camera reads in two progressive stages:

  1. Fixed Camera Capture: An unpermitted vehicle is scanned by a fixed entry camera. Handheld officer scans are excluded.

  2. Grace Period & Exit Verification: The system waits for the Unpermitted Wait Time to elapse. If a matching exit read is detected within the lot group, no action is taken.

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

  4. Automated Enforcement Execution:

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

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

Best Practices and Considerations

  • Use a Dedicated Ticket Writer Account: Always select a dedicated system account for the Automated Ticket Writer field to keep officer performance reports clean.

  • Verify Camera Lot Groups: Ensure entry and exit cameras are accurately linked in lot configurations so departed vehicles clear properly.

  • Driver-Based Tracking: Cooldown history is tracked per registered driver account rather than per plate, ensuring warning limits follow the user across 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 booting or towing flags) must be handled manually.

Back to top