When do we use this?

Our municipal clients have a specific process that all violations go through. This process includes sending out to the Transportation authority for more information and ultimately sending unpaid violations to court for collections. This article will explain the process involved in the lifecycle of a violation for one municipality in Ontario, including interactions with the MTO and the Ontario Court system.

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

Note: You must be setup to use the MTO Lookup and the Court Requested Conviction status and workflow. This could require custom development fees to handle your setup. Currently this is only available for the Ontario Court. Contact your sales representative for more information.

For this example, our Municipal client has the following violation lifecycle:

  1. Ticket 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 MTO to do a lookup of relevant driver info.
  4. Once the MTO information comes back, we will have driver info including address and driver's license number to store temporarily in our database.  Letters of impending conviction can be issued to drivers that have not paid their tickets.  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.  A file can be generated that is compatible with the Ontario Courts 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. OPS-COM Admins can use the report for information to process the payment on the violation.

Important Note about MTO Information

ARIS rules dictate the use of MTO information. This information is only temporarily stored to OPS-COM. Once the ticket is cancelled or paid all information received from MTO will be purged from the system.

 

Let's take a closer look at the process. Up to the 15th day the violation is following the typical rules of OPS-COM. We will start the process at day 15 when the interaction with MTO begins.

  1. The admin will run a weekly report to determine if there are outstanding violations in the system that have passed the 15 day mark. This would be done using the 'Vehicle Lookup Export' in OPS-COM. To get there click on the Violations Menu and hover over Collections. Click Vehicle Lookup Export.
  2. The Vehicle Lookup Export Tool opens. In our example the search parameters are:
     - Minimum Number of violations
     - Vehicle Province or State
     - Issue date or by due date
     - Date range of the lookup

  3. This search returns 3 results. To generate the required report click on Send For Lookup (MTO).



  4. A text file will be generated with the filename as SentToMTO-XX-XX-XX.txt where the X's are the date stamp (ie: SendToMTO-18-01-30.txt)
  5. Here is a small sample of what the text file will look like. Do not worry if it looks unformated or foreign. The file is set up in a custom format for MTO.

  6. The file that is returned from MTO Lookup will include Driver information such as the registered vehicle owner's name and address. This information is stored temporarily in OPS-COM and is governed by ARIS rules.  The returned document will look like the following:

  7. |To import this information into OPS-COM, click on the Violations Menu, hover over Collections and click on Vehicle Lookup Import.

  8. 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.

  9. Click Import. The following confirmation screen will appear.

  10. Once the information is imported, this information will be used to automatically populate the Notices of Impending Conviction. Go to the Letter Report to see all your violations have information from MTO.  Print the appropriate letters and mail them to the drivers.

  11. If the ticket still remains unpaid for 65 days. It could be sent to the Ontario Court for collection. To do so, Click Violations tab, hover over Collections and click on Send to Court.

  12. Select Court Requested Conviction Fee to add the court fee to the violation. Some municipalities will have a fee and some may not. For information about setting up your Admin Fees, click here.

  13. The system will generate a report in text format that would be sent to the Ontario Court.  This file is in a specific court approved format and must be customized for each municipality.
     
  14. A summary file can be generated and exported to Excel. This will contain a summary of all cases being sent to court in a particular time frame.  Click Violations, Collections, Export Sent to Court.
     
  15. The Court Requested Conviction - Already Sent Report screen displays.


  16. Click export. In excel the summary report will be displayed. You can print a copy to bring to court the day of hearings. This is in a format that the court recommends.


  17. When you look one of these violations that was sent to court you will see that the CRC fee has been added.


  18. Now we will assume we have gotten back a report for the Ontario Court that this ticket is paid. We need to flag them in the system as paid. You run this report under the Collections menu as well. Choose "Flag as Paid by Court". 

  19. Pick your date range and click Search. My ticket 7/1906 is shown. See example below:



  20.  Click Flag as paid and the violation record will show the item as processed in the user's profile.



  21. Additionally, when you look at the vehicle information for this violation, the MTO information will have been purged from the system. Note the vehicle shows No Associated Drivers.

Labels (0)

  • No labels

Comments  (0)

Attachments  (21)

Add Attachment
  File Modified
PNG File image2017-10-10 14_43_50.png Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_11-16-09.jpg Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_11-26-31.jpg Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_11-31-40.jpg Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_11-33-28.jpg Jan 30, 2018 by John Griffiths
PNG File image2018-1-18 10_37_46.png Jan 30, 2018 by John Griffiths
PNG File image2018-1-19 10_12_16.png Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_12-01-38.jpg Jan 30, 2018 by John Griffiths
JPEG File 2018-01-30_12-11-06.jpg Jan 30, 2018 by John Griffiths
JPEG File image2018-1-18 10_55_46.jpg Jan 30, 2018 by John Griffiths
PNG File image2018-1-19 10_8_47.png Feb 01, 2018 by John Griffiths
PNG File image2018-1-19 10_9_48.png Feb 01, 2018 by John Griffiths
PNG File image2018-1-19 10_16_49.png Feb 01, 2018 by John Griffiths
PNG File 2018-02-01_16-28-17.png Feb 01, 2018 by John Griffiths
PNG File image2018-1-19 10_27_34.png Feb 01, 2018 by John Griffiths
PNG File image2018-1-19 10_29_13.png Feb 01, 2018 by John Griffiths
PNG File REPORT.png Feb 12, 2018 by John Griffiths
PNG File image2018-1-19 10_25_51.png Feb 12, 2018 by John Griffiths
PNG File image2018-5-10_11-21-5.png May 10, 2018 by Shannon Jones
PNG File image2018-5-10_11-23-6.png May 10, 2018 by Shannon Jones
PNG File image2018-5-10_11-28-8.png May 10, 2018 by Shannon Jones