🚓Violations/Citations and Appeals - ViolationAdmin


Violations From Static Cameras / Mailout Violations

Violations/Infractions can be created from a report that looks at chalk records. Before this can work, ensure that OPS-COM has set your static cameras up with the necessary settings to report on the lot group and gps location of the camera. Some cameras report on more vehicle information than others. This can be helpful in the report later.

The next setup would be to map your Lot Groups to the appropriate Offence Location:

image.png

With this set up, logs will be available as they come in:

image.png

image.png

Report type will contain all available filters that we support at the time. 

The following is an explanation of each field. 

image.png

Vehicles can appear in one of three formats. No existing vehicle record, a single vehicle record, or multiple vehicle records. They will change the violation creation screen as follows:

image.png

Clicking a row will display the violation entry form.

The entry and exit cameras will show the chalk image associated to this entry:

image.png

Once the details are entered, the chalk record will disappear from the list and the violation can be found by searching for it:

image.png

Spoiling a Violation

How to Spoil a Violation

To spoil a violation start by searching for the violation through the Quick Search or Violation Search tool. 

image.png



Drill into the payment details on the Violation Information page


image.png



Select Edit at the top right of the violation and change the Spoiled status from Valid - not spoiled to Spoiled. 


image.png


Submit the changed violation details and your ticket will now be marked as Spoiled the next time you go to search for it. 

Cancelling a Violation

How to cancel a violation

Hover over Violations, select Search

image.png



Enter the violation being cancelled into the Search Text field, then select Search using only text. In this case the violation being cancelled is TT-10063.

image.png



Click on the Ticket Number of the violation being cancelled

image.png

Click on the Edit button

image.png

Select Cancelled in Fine Action field and enter the reason for the cancellation into the Appeal Admin Comment field

image.png



Click on Update this Violation

image.png



The Violation Information Updated page displays, showing the violation has been updated

image.png

Hiding Zero Dollar Violations

  1. Hover over 'System Config' and click 'System Settings'

    image.png


  2.  Click 'Violations' to open the Violations settings

    image.png


  3. Enable the 'Hide Zero Dollar Fines' checkbox to hide zero dollar violations.

    image.png


Violations by Pay Type by Month Report

Running the Report

To begin go to the Violations menu and hover over Reports. Select List By Type By Month Report.

image.png

The Violations by Pay Type by Month screen opens.

image.png

Select the month you wish to report on. In our example we will look at November of 2020. Click on Retrieve to continue.

image.png

The resulting report will display onscreen. 

image.png

The report may also be exported as an excel file.

image.png

List Overdue Report

Accessing the Report

From the Violations menu hover over Reports and click the List Overdue menu item to access the Overdue Violation Payments report. 

image.png

The Overdue Violation Payments screen is displayed.
Enter your search criteria and click List Overdue Records. In this case we are looking at violations between May1st 2020 and February 8th 2021
The report will appear at the bottom of the screen with the violation number, details, amount, and offender details. 

image.png

Emailing Users

You can click on the user email address to email users directly related to their overdue violations.
You can also select Email Listed Users at the bottom of the report to send an email to all users on the report. 

Generating an Excel Report

Click Generate Excel Report to create an excel document for your records or further manipulation.

Summary Report by Officer

1. Hover over the Violations icon and hover over Reports. Click on Summary Report by Officers in the drop down menu.

image.png

2. The Violation Summary by Officer screen is displayed. Select your Ticket Writer and date parameters for the search.
You can search individual officers or select either one of the full list options: Summary Only or Group led By Officer

Click Display Summary and the report will appear at the bottom of the screen.
The report can also be exported to Excel. To do so click on the Export button.

image.png

The report will display based on your search criteria.

image.png

Violations by Officer Report

Using the Report

Hover over Violations and click Reports, Report by Officers.

image.png

The Violations by Officer screen is displayed. Select your parameters for the search. 

Search Criteria include:

Ticket Writer: You can select a specific officer or List all violations grouped by officer
Spoiled: Select a spoiled state 
Ticket Category: Select a specific ticket category such as Private Property 
Include Archived Categories: Toggle the item on to apply the search filter
Warnings: Select to hide, include, or show warnings only
Show Only Due: Toggle the item on to apply the search filter
Date Search By: Select either the Due Date or the Issued Date
Start Date and Up To and Including: Set the date range you wish to report on

You can then click Search to view the report onscreen or click Export to download the report as an excel document.

image.png

The report will appear at the bottom of the screen.

image.png

If you wish to view more information about each violation, click on the violation number. If you wish to view the pictures associated with a violation click on the Camera icon.

Exporting the Report

You can export the information to a .csv file and manipulate the data in Excel. Click Export to download the file.

image.png

Paid Violations Summary by Type Report

Accessing the Report

Hover over the Violations icon and click Paid Summary by Type.

image.png

The Paid Violations Summary by Type screen is displayed. Select your date parameters for the search.

Click Display Summary and the report will appear at the bottom of the screen.

image.png

Violations by Location/Officer Report

Using the Report

Hover over the Violations icon and click Report by Location/Officers.

image.png

The Violation Summary by Location/Officer screen is displayed. Select your date parameters for the search. 

image.png

Click Display Summary and the report will appear at the bottom of the screen.

image.png

Search Repeat Offenders Report

Introduction

The search repeat offenders page allows site admins to find vehicles and users on the site that have received multiple parking violations on their account.

 

Navigation

To navigate to the page, look under the menu tree:

image.png

 

Page Usage

The page will appear as displayed. 

image.png

Several options are available to narrow the search.

 

Output

The grouping of the output will vary depending on whether it is selected to be output by vehicle or by user.

 

By Vehicle/Plate

Grouping on the vehicle will show the number of violations on each plate, and any associated drivers of the vehicle.

image.png

Individual violations can be viewed by clicking on the violation count.

The warning icon next to the username will show a list of the violations associated to that user.

 

By User/Driver

Grouping on the user will show the number of violations given to the user, including any violations given to vehicles the user is the driver of.

image.pngIndividual violations can be viewed by clicking on the violation count.

The icon next to the total violation count shows the breakdown of the total, showing the number of violations assigned to the user and the number of violations assigned to that user's vehicles.

 

Exporting Results

After searching, the results can be exported in a chosen format by clicking one of the green buttons at the top right of the search results.

image.png

Restricting Payment of Violations in Court Requested Conviction (CRC) Status

  1.  Click System Config, System Settings to ensure the settings that pertain to Collections are set to disallow payments while violations are under the CRC status.

    image.png


  2. Ensure that the following settings are enabled and save the settings:
     - Prevent Violation Payment
     - Prevent Purchases

    image.png



  3. There are two permissions that deal with the treatment of payments for CRC items. To setup these permissions, click System Config, Manage Roles.  

    image.png


  4. Select the role you wish to add these abilities to. In this example we will add them to Primary Admin. Click on Permissions to access the settings.

    image.png


  5. Under the violations Tab ensure that these two settings are enabled:
    (A) Pay Violations In Collections. (Allows the Admin to process payments on violations that are in collections.)
    (B) Purchase While Outstanding (Allows the Admin to purchase items for the user while the user has a violation that has been sent to collections. This is only necessary while Prevent Purchases is turned on in the settings.

    image.png


  6. The following two screens show how this functionality appears to the End User and the Admin:

    This is what the User will see if they have violations with the 'Sent to CRC' status. Note the notices indicating the violation has been Sent to Collections.

    image.png



    Here is what the Admin sees if they have the permission to pay these violations while in collection status. Note the notices indicating the violation has been Sent to Collections.



    Here's the Admin view with the permission to pay these violations while in collection status enabled. Note the fact that the violation is still shown as Sent to Collections yet is still payable by the Admin.

    image.png



    In addition, if the User tried to pay the violation through OPS-COM Quick Pay/Guest Payments they would see the same message disallowing the payment of the violation.

    image.png


Printing the Certificate of Parking Infraction

Create Form 11 Template

If it already exists, the Form 11 template will be found under the Content & Designs menu, in Pages and Content Blocks:

image.png

It will be found under the Messages tab. The System Location value is "form11":

image.png

If the template doesn't already exist, it can be created by clicking "Create Page/Message". Set Page Type to "Message", and for Identifier enter "form11". (Be sure to click "Save Messaging" once done.)

image.png

Edit Form 11

The content of the form can be edited in Pages and Content Blocks. Locate "form11" under the Messages tab and click "Edit". On this page is a text editor where the content of the form can be set. (Be sure to click "Save Messaging" once done.)

Although it's possible for admins to set Form 11 content themselves, it's strongly recommended to request the form content from OPS-COM support. This is because the content of Form 11 is very specific, and requires the use of shortcodes to auto-fill information such as date, plate number, fine amount, etc.

Print Form 11

To download and print Form 11 for a violation, first find the violation on the Violation Search page and click on the violation number:

image.png

Under the Action menu, click "Generate (title of form)":

image.png

The form will be downloaded as a PDF, which can then be printed.

Adding a Digital Signature

There is an option to add a digital signature when writing a violation on an enforcement handheld. When that option is enabled, the patrol is required to sign the violation on the handheld screen. When uploaded to the server, the timestamped signature is sent with the other images. When using this option, the signature will also appear on Form 11 when printed. The option to use signatures on tickets can be enabled in System Settings under Violations:

image.png

When this setting is enabled, a signature tab will appear when writing a violation on a handheld:

image.png

The signature will show up on Form 11:

image.png

MTO Annual Report

Running the Report

To begin go to the Violations menu and hover over Reports.
Select MTO Report from the drop down menu.

image.png

Enter the date range you wish to report on. In this case we are looking at the full 2020 year end report (January 1st 2020 - December 31st 2020).
Click Search to continue.

image.png

The screen will refresh with a list of items required in the Annual MTO Report.

image.png

Collections - Flag as Sent to Collections

  1. To set the flag, open the violation search page.

    image.png



  2. Enter the violation that is being flagged. In this case it is TT-10001. Select the ticket # to open the Violation Information page.

    image.png



  3. Select the Action box and enable 'Flag as Sent to Collections'. Click Ok.

    image.png


Municipal Violations and Collections

Introduction

Municipal clients located within Ontario have specific processes for violation offences to be sent through. The two relevant processes are the POA (Provincial Offenses Act) and the AMPS (Administrative Monetary Penalty System). Municipalities will prescribe to one process or the other.

OPS-COM supports most aspects of the POA process and is considered as a Permitted Recipient under ARIS rules. The POA process is used when a violation is given to a vehicle that has no user information present within the system.

This process involves sending out vehicle data to the transportation authority (MTO) to receive additional user information, so any outstanding violations on the vehicle can be sent to court for collections.

This article will explain the process involved in the life-cycle of a violation for one municipality in Ontario, including interactions with the Ministry of Transportation (MTO) and the Ontario court system.

It is important to note these violations would be issued to a vehicle by license plate number. Unless the driver is a registered user in the OPS-COM system, the actual owner of the vehicle would not be known.

A client must be setup beforehand to use the MTO Lookup and the Court Requested Conviction status and workflow. This could require custom development fees to handle the client’s setup. Currently, this process is only available for use within the Ontario court system.

In addition to the OPS-COM setup, the client must work with the MTO to become an Authorized Requester of the MTO information. The process can be started by contacting ARIS@ontario.ca and requesting a RAW data account.

Please contact your sales representative for more information.

An Example

Consider a municipal client that has the following violation life-cycle:

  1. A violation is issued with 7 days to pay during which the fine amount may be discounted. 

  2. On the 8th day, the fine is no longer discounted.

  3. Weekly, all tickets that have reached their 15th day of non-payment are sent to the MTO to do a lookup of relevant driver info.

  4. The MTO will send a return file containing the driver information for the vehicle involved in the violation, including address and driver's license number, to be stored temporarily in the database. 

    1. Notice letters can be issued to drivers who have not paid their violations. This is done using the letter report.

  5. If the violation is still outstanding on day 65 it will be sent to court and an additional court fee can be applied to the violation. 

    1. A file can be generated that is compatible with the Ontario court system if upload is available. In addition, a summary file can be generated to include all cases submitted to court in a particular timeframe.

  6. When the ticket has been paid, the court will send a report back to the parking manager to let them know what the outcome was. Admins can then use the information in the report process the payment on the violation within the OPS-COM system.

Important Note about MTO Information

ARIS rules dictate the use of MTO information, requiring the information from the MTO is only temporarily stored within the OPS-COM system.

Once a violation has been cancelled, paid, or sent to collections, all information from the MTO related to the violation will be purged from the system.

Starting the Process

The interaction with the MTO begins after a violation is past due.

The admin will run a weekly report to determine if there are outstanding violations in the system that have gone unpaid for 7 days after they were marked as due. This is done using the Vehicle Lookup Export page.

This page can be found by following this menu tree:

image.png


Vehicle Lookup Export Tool

Several search options are present on the page:


image.png

Clicking on export will generate a file to be sent to the MTO containing the vehicle information that is additional information is being requested for.

Notice there are various formats for this export:

image.png

A text file will be generated with the filename as SendToMTO-XX-XX-XX.txt, with the Xs acting as placeholders for the timestamp at the time of file creation.


image.png

 

MTO Export File

Here is a sample of what the exported text file will look like.

The file is formatted in a custom format required for the MTO to lookup driver information.

image.png

 

MTO Response File

The file that is returned from MTO Lookup will include driver information such as the registered vehicle owner's name and home address.

This information is temporarily stored in the OPS-COM system. As governed by ARIS rules, the information will be purged from the system after it is no longer needed. 

The document return from the MTO will look like the following:

image.png

Simulated Response File

There is an option to generate a mock version of an MTO response file using the file previously exported.

This can be done using the Third Party Simulator page, located under the menu tree:

  • Tomahawk Options → Third Party Simulators

image-20240417-211012.png

Importing the MTO Response File

To import the information received back from the MTO into the OPS-COM system, navigate to the vehicle lookup import found under the menu tree:


image.png

The Vehicle Lookup Import file selector tool opens.

Choose the file that came back from MTO and navigate to the file you wish to select for import.

image.png

Click the Import button.

A confirmation message will appear in the top right of the page.

image.png

 

Generating Notice Letters

Once the information has been imported, the data will be used to populate any missing notice letter information.

Violations that have had MTO information associated to them can be viewed from the Letter Report page.

After the notice letters have been printed, they must be sent to the drivers of the vehicles by mail.

Sending to Collections

If the ticket still remains unpaid after the notice letter has been sent, it is eligible to be sent to the Ontario court system for collections.

The page can be found under the menu tree:

image.png

The number of days since the violation was issued can be specified, and violations that have not been issued a notice letter can also be included.

image.png

An admin fee can be added to the violation on export.

Some municipalities have a fee and some do not.

image.png

The page will then generate a file to be sent to the Ontario court system, named in the format of SendToCRC-XX-XX-XX.txt, with the Xs acting as placeholders for the timestamp at the time of file creation.

The report generated by the system is in a format specified by the Ontario court system for processing, and must be customized for each municipality.

It will look something like this:

image.png

 

Client MTO Codes

For each client sending information to the MTO, there are 4 codes required by the Ontario court system that must be set up on the client’s site.

NOTE - The client must request a RAW Data account from the MTO to use this process. This system will not work otherwise.

Here's a reference for all the provincial forms: https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/

The provincial forms are:

  • Case Court: starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186.

  • Case Jurisdiction: starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190.

  • The Agency Code: 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658).

  • Disbursement Code: 1 alphanumeric character followed by 3 numbers (Parry Sound is M525, Perth's is M658).

To set these codes up within the site, go to System Settings and select the Collections Component.

Enter the values in the designated fields, and then click on save settings.

image-20240417-204520.png

For municipalities using the extra-detailed version of the notice letter where one notice is sent out for each violation rather than in bulk, the "Include All Unpaid Violations" setting must be disabled.

image-20240417-204725.png

Generating the Ontario Court Report

A file can be generated and exported to Excel, containing a summary of all violations being sent to court in a particular time frame. 

The page can be found under the menu tree:


image.png

This will open the Court Requested Conviction - Already Sent Report.

image.png

Clicking on export will download an Excel file to the browser.

A copy can be printed to bring to court on the day of the hearings.

It is exported in the format recommended by the courts:

image.png

 

Court Requested Conviction Fee

If a conviction fee was added on to the violations sent to court, it can be viewed when looking at the violation’s info page.

A record for the Court Requested Conviction (CRC) fee will have been added.

image.png

Flagging Paid Records

When a report is received back from the court indicating a violation was paid, it must be flagged in the system as being paid.

The report to flag as paid is located under the collections menu, within the menu tree:


Enter a date range and press the search button.

image.png

A list of the violations that have been sent to court will be returned by the page.

image.png

Click Flag as paid to process all selected violations to be marked as paid.

Violations flagged as paid will also appear on the Daily Processed Report with a payment type of paid by court.

image.png

Additionally, when looking at the vehicle information for this violation, the MTO information will have been purged from the system.

Note the vehicle shows there are no associated drivers.

image.png

Handhelds Devices Settings

Navigate to Handhelds Devices

Select System Configuration → Violations → Handhelds Devices.

image.png



The Handhelds - Common Settings screen appears where you can edit the number of days before a ticket is due, customize the ticket footer, view device information, and manage handhelds.  

image.png

Adding A New Device

When adding a new handheld device start by installing the OPS-COM for Android software. After first login you will get a notice that the device is not registered and the message will give you a UUID number to be used. It's a 16 digit alphanumeric code that appears under your login screen. Use that UUID to configure your Handheld Common registration process.


Once in Handheld Common click on Add New Device.

A screen will open up where you must add:

Also important is to ensure Enabled is selected at the top of the entry form.
Once you have this information in place click on Add Device

image.png

Pushing Messages 

You can also push messages out to handheld units. Click the 'Push Message' button and follow the prompts. 

image.png



image.png

Updating Device Data

Click the device you wish to update to get a drop-down list of the settings you can change. 

image.png

Make sure you select Process Updates when you are finished. 


Important Note - Additional Information

By virtue of how the Handheld Common tool functions. It's always part of the process to start setting up a unit on the production side regardless of whether it is to be used in Production or as a test unit on Preview.

For initial handheld connection, the system always connects to production first, then looks at the PA Common/handheld assignment table where the units are registered to then know if they are registered on Production or Preview. That's the logic path so it is important to always write the tables from production side first. 

Additionally, this is why we can refresh preview sites without loosing the Handheld units that are configured to specific preview sites.

Adding a Handheld Unit to Preview for Testing

To add a handheld unit to preview you must first add it to handheld common on the production admin portal. You would fill everything in as normal but select the preview server as the entry in Sync With.

This will set the proper route for the handheld unit in the database. You will then need to go to the preview server and enter the same information into the preview site.
Then perform a reinstall of the software. This will allow the handheld to pick up the new path to preview that you have set.

Once the entry is in both Production and Preview you can switch back and forth fairly easily. You repoint the sync with setting to the preferred path on both Production and Preview.
You have to do a reinstall each time you change the path in order for the handheld unit itself to be updated with the selected path.

Appeals Report

To review appeals as an admin hover over the Violations icon and click Appeals and then select Appeals Report.

image.png

The Appeals Report page is displayed with information related to the violation and appeal date. 

image.png

Click View Info beside a person's name to get details on that appeal. The User Appeal History screen displays.

Additional Options

If you click the person's username, you will be taken to the Edit User Profile page. If you click the ticket number, you will be able to view the Violation Information page.


image.png

All information on the appeal is displayed. The user history is displayed as well as user and vehicle information.  

Click the Action Taken picker and choose to Uphold, Reduce or Cancel this violation. In this example, Reduce Violation has been selected and a new fine amount is entered. In the box for Comments to Send to Appellant, enter your comments regarding your appeal decision.

Click the Submit button when finished to process the appeal and to email the user.

This is an example of the email that will go to the user, your email might look different from ours depending on your set up. 

image.png

Alternatively, you can follow steps taken from the 'Edit a Violation as an Administrator' page excerpted below:

Edit a Violation
Administrators can make changes to basic information and deal with appeals for this Violation however once a user pays for the violation the comments are locked and admins must use the Violation Notes for further comments. Simply click the Ticket has not been appealed. Show appeals form text to get the appeal information. 

Highlighted in yellow is the Appeals section. The different fields in the 'Appeals Area' are explained below:

Ticket Appealed - This is the date in the first picker and how the appeal was filed in the second picker.

Fine Action - Choose from Upheld, Reduced or Cancelled

Offense Value - The amount can be manually edited if Reduced on appeal but will automatically be reduced to 0.00 if Cancelled. You can also edit the Offence Value directly.

Appeal Reason - The reason for launching the appeal can be recorded here. This field can be viewed by the user.

Appeal Admin Comment - This is for private appeal notes. These notes are not viewable by the user.

image.png


Change the Actioned per: field by selecting the Admin account making the changes from the picker.

Click  Update this Violation and a message will appear letting you know that the violation has been updated. 

image.png



Edit a Violation

Searching for the Violation

Follow the steps to search for a violation - Search for a Violation as an Administrator

At the bottom of the Violation Search screen, the returned records will be displayed. 

Getting to the Violation Information

Click the TICKET# to open the Violation Information window.  

image.png


A new window will appear with the Violation Information. You can edit the violation from the Edit button at the top right, or by using the Action dropdown menu. 

image.png

You will be taken to the Edit Violation Information window.

image.png

Editing the Violation and Important Information


IMPORTANT

APPEALS GRANTED, REDUCED OR CANCELLED TICKETS CANNOT BE EDITED AGAIN AND ARE NO LONGER ELIGIBLE FOR DISCOUNTS.

Violation Notes can be used for further comments. If the ticket has been appealed and the user goes to a higher power to have the ticket overturned, then you can edit the ticket and change it to a warning this will keep the information and change it to a zero value and complete the processing. This will also keep the history so that the Admin will still know that they had a ticket in the past. A comment can be added to the warning to further explain

Administrators can make changes to basic information and deal with appeals for this Violation however once a user pays for the violation the comments are locked and admins must use the Violation Notes for further comments. Simply click the Ticket has not been appealed. Show appeals form text to get the appeal information. 

Highlighted in yellow is the Appeals section. The different fields in the 'Appeals Area' are explained below:

Ticket Appealed - This is the date in the first picker and how the appeal was filed in the second picker.

Fine Action - Choose from Upheld, Reduced or Cancelled

Offense Value - The amount can be manually edited if Reduced on appeal but will automatically be reduced to 0.00 if Cancelled. You can also edit the Offence Value directly.

Appeal Reason - The reason for launching the appeal can be recorded here. This field can be viewed by the user.

Appeal Admin Comment - This is for private appeal notes. These notes are not viewable by the user.

image.png


Change the Actioned per: field by selecting the Admin account making the changes from the picker.

Click  Update this Violation and a message will appear letting you know that the violation has been updated. 

image.png



Paying a Violation

  1. Click Violations then Search.

image.png

2.The Violation Search screen displays. Enter the violation number in the Search Text field.

image.png

In this case we are looking for Ticket Numeber 10-01004

image.png

3.  In the search results. click on the ticket number to see the Violation Information.

image.png

4.  From the Violation information window click 'Make Payment'.

image.png

5.  The Payment Due screen for the user's profile will display. Note: If there are more than one item to be paid the Admin can select by checkbox the items the user wishes to pay. 

6.  Click 'Proceed to Payment.'

image.png

7.  The screen will refresh with the specific purchase information you requested. Select the payment type you wish to process the item with. In our case we are processing a cash transaction.

8.  Click Submit Payment Information.

image.png

9.  The screen will refresh with a confirmation screen. Click 'Confirm Payment Information' to continue.

image.png

10.  The Transaction Details window opens. This will list the item/s being paid for. Click 'Process Manually' to complete the transaction.  You may also choose 'Cancel Transaction' to back out of this action.

image.png

11.  The system will process the payment and return to the Transaction Details page. There are several pieces of information that can be seen here.

image.png

Once the payment has been made you can see in the user's history that the violation has been paid and marked processed.

image.png

Search for a Violation

To search for violations hover over the Violations icon and click Search.

image.png


You can also Search with text and date range if you want to narrow down the search parameters to a specific date range.  As you can see below, there are a number of search parameters you can choose from to further enhance your search results.

image.png

At the bottom of the 'Violation Search' screen, the returned records will be displayed.

image.png

4. Click the Ticket Number to open the 'Violation Information' window. Click 'Edit/Update' to display the 'Edit Violation Information' screen to make changes if required.  From this window, you can also link the Violation to an incident if you have the Incident Module available. Alternatively, you can make a payment or add Notes to the Violation. 

image.png

Searching By Time Frame

  1. It is also possible to search for violations using a time frame filter. In our example here we are searching for any violation written between the hours of 4:00pm and 8:00pm on February 27th.
    To access the time setting click on "with time" beside the date field.

    image.png


    This will bring up a an interface where you can chose both date and time:
    In this example for the start time we are selecting Feb. 27th at 4:00pm (1600 hours). 

    image.png


  2. Set the up to and including date and time in a similar fashion. Note that the time blocks are in one hour segments so to choose 8:00pm you would need to select hour 19 which would include 7:00 to 7:59 and appear in the date and time field as 19:59 (see above)

  3. image.png

    By using this filtering method the search will return only violations that were issued between 4:00PM and 7:59pm on February 27th,

    image.png


Configure Violations to a Person

Setting up Violation Entries 

Before you can issue violations you must enable Link violations to users in System Settings, Violations before issuing violations by person or vehicle. 

image.png

Managing Ticket Categories

Hover over Admin Options, select Violations, then Manage Ticket Categories

image.png



Select the Ticket Category that is being updated to allow users to receive violations, in this example Municipal is being selected

image.png



Select Users in the Violation Applies To section

image.png



Now when entering a violation of this offence type it will be possible to apply the violation to a person. 

image.png

Manual Violation Entry

Entering a Violation

Hover over the Violations icon and click Violation Entry.

image.png



The Enter Basic Violation Information screen is displayed. The numbered fields are explained below:

#1 - Spoiled - This is used to cancel a manual ticket. This allows incrementally numbered paper violations to be accounted for.

#2 - Auto Generated - Ticket numbers can now be Auto Generated if this checkbox is enabled.

#3 - Warning -  All violations can now be issued as a warning by enabling the 'Warning' checkbox. You will no longer pick 'Warning' as a Ticket Type.

#4 and #5 - Vehicle or Person - If you have the features enabled you can issue a violation to a Vehicle or a Person.


image.png



Enter all known information in the fields provided. Click the Search Vehicles button to find vehicle information by the license plate or VIN number. You can choose a vehicle or add a new one from the Search area. There are a number of actions you can take from this screen.

image.png



After you have selected the correct fields click the Enter Violation button to proceed.

Entering and Confirming Violation Information

The Enter Violation Information screen is displayed. Allowing the Administrator to enter more details about the Violation. 


image.png



Click the Record this Violation button. The Confirm Violation Information screen is displayed. Verify the details are correct and click the Information Correct button to save the violation.

image.png


Violation Entry Completed

Once you have submitted the violation the Violation Entry Complete screen will appear where you can choose to print, view, search violations. 

image.png

Manually Entering Hard Copy or Anonymous Ticket 

Searching a vehicle that does not exist in the system will allow you to write an anonymous ticket to that plate or to transcribe hard copied tickets with no users. The user can then navigate to the login screen and pay for the ticket using OPS-COM Quick Pay/Guest Payments without logging in. 

image.png

Security PIN on Violations - How is it used

The Ticket PIN


The additional dash and 2 digits at the end of the violations are known as a "Ticket Security PIN".
It may look like it's part of the ticket number, but it's not. It's only used as a password for the ticket when appealing it.

image.png

As an example when creating a violation, it appeared as TT-10016-8T The actual internal ticket number is TT-10016-8T, same format as it has always been. If you search violation TT-10016 in violation search it will appear as TT-10016.
Additionally, if someone did type in the ticket number and PIN (TT-10016-8T) it would return the same ticket.

This means the reports in the FTP file, for example, will only reference TT-10016 as the ticket number, not the additional -8T.

Additionally, the code that generates the FTP files isn't going to change/add the pin.

FTP reports will remain unchanged by the addition of the violation PIN. No PIN will be shown in the mailed out the violation.

The PIN is only used when appealing tickets if the user isn't logged in. As an example, you can see the "Lookup your Ticket" box on the login screen here. 
The PIN is used in that box to give some protection from public users just looking up sequential ticket numbers.

image.png


Click on the box that says "Lookup your Ticket". You should now see the following screen. Enter in the ticket number and PIN.

image.png


Once you click check you will be presented with a screen that allows you to appeal or pay the ticket.
Notice when the record of the ticket is found it does not include the PIN.

image.png


Removing the Pin


  1.  If you wish to remove the PIN from the printed ticket, this can be done from the System Settings located under the System Config tab. 

    image.png



  2. Look for Violations in the list of components on the left:

    image.png



  3. Click on Violations to view and edit the settings. By default the setting for including a random PIN number to the ticket number when printed is enabled. 
    To remove the PIN, ensure that the Include Random PIN on Handheld Tickets box is toggled off.

    image.png


Ticket Warnings Explained

Below is, a sample of a warning ticket, a sample of an actual violation ticket and a sample of the back of a ticket/warning provided by the OPS-COM software.

      

image.png

Explanation of the Front of the Ticket/Warning

Ticket Number - This is a system assigned number that identifies each individual violation/warning.

Date - This is the date that the violation/warning was issued on.

Ticket Type - This identifies the type of violation that occurred (broad range category).

License Plate - This is the license plate number for the vehicle that incurred the violation.

Province - This is the province that the license plate is issued in.

Offense Type - This identifies the specific violation that occurred.

Location - This identifies the location where the violation occurred.

Writer - This is a system assigned number that identifies the enforcement officer that issued the violation. Each enforcement officer has their own unique number and can be verified by administrators. The writer is identified by a unique identifier to provide security to the enforcement officer. If you require more information about the ticket writer you can search the violation on the admin side and get an actual name for the person who wrote the ticket. 

Fine - This is the amount owed for the particular violation. Note, on the warning ticket the amount is followed by "*Warning". This indicates that the amount on the ticket is not owing, but this is the amount that would be due if a ticket for the same violation was issued.

Towing - This is the amount due if the vehicle that incurred the violation had to be towed.

Comments - This section includes any additional notes that the enforcement officer wants to include.

Explanation of the Back of the Ticket/Warning

The back of the ticket provides details about the organization that issued the ticket and the policies and procedures regarding the ticket. The back clearly identifies how the violator can pay or appeal the ticket with a section for the violator to identify themselves and sign off on the ticket. The back also identifies where to find additional information on the organization and the office hours. 

Warnings and Spoiled Tickets

Warning is a warning that the user has broken the rules.  The warning is tracked as a zero dollar violation that is processed immediately upon syncing to the server.  The idea here is that a user will still get a ticket, but won't have to pay for it.  A slap on the wrist as they say..


Spoiled refers to the old concept of spoiling a ticket.  Back in the day (of paper!) a patrol might be writing up a ticket and the user shows up and moves their car.  The ticket is then said to be spoiled, or another example might be a patrol entering the wrong plate/vehicle details.  This is also a void type ticket and in this case like it never happened.