Note: If you would like to change the ticket prefix, (i.e. the TT- before the ticket in the default configuration) you will have to contact [OPSCOM support](mailto:support@ops-com.com).
The next setup would be to map your Lot Groups to the appropriate Offence Location: [](https://opscom.wiki/uploads/images/gallery/2024-07/dgjimage.png) With this set up, logs will be available as they come in: [](https://opscom.wiki/uploads/images/gallery/2024-07/jztimage.png) [](https://opscom.wiki/uploads/images/gallery/2024-07/dbSimage.png) Report type will contain all available filters that we support at the time. - No Permit & Over Lot Time - This option will only list vehicles where they have no permits and the duration exceeds the lot group's free parking time. The following is an explanation of each field. [](https://opscom.wiki/uploads/images/gallery/2024-07/Pl5image.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: [](https://opscom.wiki/uploads/images/gallery/2024-07/1xuimage.png) Clicking a row will display the violation entry form. The entry and exit cameras will show the chalk image associated to this entry: [](https://opscom.wiki/uploads/images/gallery/2024-07/doMimage.png) Once the details are entered, the chalk record will disappear from the list and the violation can be found by searching for it: [](https://opscom.wiki/uploads/images/gallery/2024-07/4MLimage.png) # Spoiling a Violation ## How to Spoil/Void a Violation - To spoil a violation, start by searching for the violation through the **Quick Search** or **Violation Search** tool. - Click on the **Ticket #** on the **Violation Information** page [](https://opscom.wiki/uploads/images/gallery/2024-06/uh1image.png) - Select **Edit** at the top right of the violation and change the **Spoiled** status from **Valid - not spoiled** to **Spoiled**. [](https://opscom.wiki/uploads/images/gallery/2024-06/Vi3image.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 1\. Hover over **Violations**, select **Search** 2. 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.** 3. Click on the **Ticket Number** of the violation being cancelled [](https://opscom.wiki/uploads/images/gallery/2026-05/qhiimage.png) 4\. Click on the **Edit** button [](https://opscom.wiki/uploads/images/gallery/2026-05/2Spimage.png) 5\. Click on the **Show Appeals Form** link. [](https://opscom.wiki/uploads/images/gallery/2026-05/f4Gimage.png) 6\. Select **Cancelled** in the **Fine Action** field and enter the reason for the cancellation into the **Appeal Admin Comment** field. [](https://opscom.wiki/uploads/images/gallery/2026-05/9sximage.png) 7\. Click on **Update this Violation** [](https://opscom.wiki/uploads/images/gallery/2026-05/P3Zimage.png) A pop-up with show a message in the top right of your screen that the "**Violation has been updated.**" [](https://opscom.wiki/uploads/images/gallery/2026-05/UtQimage.png) # Hiding Zero Dollar Violations 1. Hover over '**System Config**' and click '**System Settings**' [](https://opscom.wiki/uploads/images/gallery/2024-06/Yg9image.png) 2. Click '**Violations**' to open the Violations settings [](https://opscom.wiki/uploads/images/gallery/2024-06/zcjimage.png) 3. Enable the '**Hide Zero Dollar Fines**' checkbox to hide zero dollar violations. [](https://opscom.wiki/uploads/images/gallery/2024-06/B8Fimage.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: - **Violations -> Search Repeat Offenders** [](https://opscom.wiki/uploads/images/gallery/2024-07/image.png) --- ## Page Usage The page will appear as displayed. [](https://opscom.wiki/uploads/images/gallery/2024-07/MtMimage.png) Several options are available to narrow the search. - **Start Date and End Date**: specifies the range in which the violations were received. - **Ticket Category**: the category of the violation received. - **Number of Violations**: the min number of violations the user or vehicle has received. - **Processed Value**: categorizes violations based on their processing status. - - **Unprocessed**: violations that have not been processed yet. - **Processed**: violations that have been paid for and processed. - **Warning Only**: violations that were marked as a warning instead issuing a fine. - **Unknown Users Only**: only shows violations assigned to vehicles without a known user tied to them. - **Search By:** - **Vehicle/Plate**: outputs the count of violations tied to license plates. Will not include violations attached directly to a user. - **User/Driver**: outputs the count of violations tied to users. Includes violations attached directly to the user and any violations attached to their vehicles. Will not include violations attached to a vehicle with no assigned driver. ## 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. ### [](https://opscom.wiki/uploads/images/gallery/2024-07/YItimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-07/DUuimage.png)Individual 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. [](https://opscom.wiki/uploads/images/gallery/2024-07/52Limage.png) # Restricting Payment of Violations in Court Requested Conviction (CRC) Status 1. Click **System Configuration**, **System Settings** to ensure the settings that pertain to **Collections** are set to disallow payments while violations are under the CRC status. [](https://opscom.wiki/uploads/images/gallery/2024-06/Jw7image.png) 2. Ensure that the following settings are enabled and save the settings: **- Prevent Violation Payment** **- Prevent Purchases** [](https://opscom.wiki/uploads/images/gallery/2024-06/ipximage.png) 3. There are two permissions that deal with the treatment of payments for **CRC** items. To setup these permissions, click **System Configuration, Manage Roles**. [](https://opscom.wiki/uploads/images/gallery/2024-06/2Fgimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/JbHimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/nY4image.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**. [](https://opscom.wiki/uploads/images/gallery/2024-06/izsimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/8RXimage.png) In addition, if the **User** tried to pay the violation through OPSCOM Quick Pay/Guest Payments they would see the same message disallowing the payment of the violation. [](https://opscom.wiki/uploads/images/gallery/2024-06/dvPimage.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: [](https://opscom.wiki/uploads/images/gallery/2024-06/Imrimage.png) It will be found under the Messages tab. The System Location value is "form11": [](https://opscom.wiki/uploads/images/gallery/2024-06/Ontimage.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.) [](https://opscom.wiki/uploads/images/gallery/2024-06/OWSimage.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 OPSCOM 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: [](https://opscom.wiki/uploads/images/gallery/2024-06/uGqimage.png) Under the Action menu, click "Generate (title of form)": [](https://opscom.wiki/uploads/images/gallery/2024-06/JJuimage.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: [](https://opscom.wiki/uploads/images/gallery/2024-06/EdBimage.png) When this setting is enabled, a signature tab will appear when writing a violation on a handheld: [](https://opscom.wiki/uploads/images/gallery/2024-06/tM9image.png) The signature will show up on Form 11: [](https://opscom.wiki/uploads/images/gallery/2024-06/b24image.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/FPEimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/2JXimage.png) The screen will refresh with a list of items required in the **Annual MTO Report**. [](https://opscom.wiki/uploads/images/gallery/2024-06/6Cnimage.png) # Collections - Flag as Sent to CollectionsThe "Flag as Sent to Collections" feature is used to bypass the standard notification processes for a violation that is being handled externally by a collections agency. This is useful if a person wants to go directly to trial instead of waiting and going through the entire process. Once this flag is enabled, the violation will bypass the existing NIC (Notice of Impending Charge) letter and the CRC (Certificate of Request for Court) process.
## Setup & Configuration You must have the Manage Collections permission to do this. This permission can be added to your profile by your Primary Admin. To enable this permission: - Go to **System Configuration**, then **Admin Management**, and **Manage Roles**. - Locate the Role you want to edit and click the **Permissions** button. - Click the Violations tab and enable the **Manage Collections** permission. - Click **Save Settings**. --- ## Using this Feature 1. Go to Violations and click Search. 2. Search for the violation you want to flag. 3. Click the ticket # to open the Violation Information page. 4. Select the Action drop down and click **Flag as Sent to Collections**. 5. Click Ok. --- ## Best Practices & Considerations - **Admins** should use the existing **Violations Notes** feature to add detailed notes to the violation. This could include the customer's request and any necessary details explaining why the ticket was placed in the Collections state. - Admins with the appropriate permissions will still be able to **pay or cancel** the violation as necessary. - Once a violation has successfully gone through the collections process once, it is marked as such and **cannot** re-enter the Collections process again. # 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](mailto:ARIS@ontario.ca "mailto: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: - **Violations → Collections** → **Vehicle Lookup Export** [](https://opscom.wiki/uploads/images/gallery/2024-06/uhkimage.png) ## Vehicle Lookup Export Tool Several search options are present on the page: - Minimum number of violations - Vehicle province or state - To search by issue date or by due date - Date range of the lookupThe 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.
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.
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.
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.
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.
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.
The **Appeals Report** in OPSCOM provides administrators with a centralized view to review, manage, and action user appeals against violations. This feature allows for detailed examination of appeal information, recording decisions (uphold, reduce, cancel), adding comments, and notifying appellants, ensuring a fair and transparent appeal process.
### Setup & Configuration ##### System Settings Before you can process Appeals, you must have this module enabled.After enabling the appeals module, you need to decide whether or not you want to enable ***Reset Appeal on Association.*** This setting will allow users who have a **violation associated to their vehicle,** but have not made an **account**, the same amount of time to appeal a violation as a user who already had their account configured. Once they create and associate their account to the vehicle, with this setting enabled, the appeal time frame will be reset, and the user will have the amount of days specified under **Appeal days** to appeal the violation, **from the date they associated the account.**
1. Hover over **System Configuration**, and click **System Settings.** 2. On the **Violations** tab, ensure the **Enable Appeals Module** setting is enabled. If it is not, please contact**Manual Violation Entry** in OPSCOM allows administrators to record violations directly into the system via the web interface. This feature is crucial for digitally logging hand-written tickets, or citations created with a laptop instead of a handheld device, ensuring all violation data is centralized for tracking, reporting, and court purposes.
### Setup & Configuration There are a few settings that relate to Violations issued from the Admin Portal and not on handheld devices. To access these settings: 1. Hover over **System Configuration**, and click **System Settings**. 2. On the Violations tab, locate the **Prefix to go in Front of Ticket Number** setting. If you want to easily differentiate between tickets created on the Admin portal and tickets created on the Handheld devices you can set a prefix here. By default it is TT. 3. If you wish to have tickets **Auto Generated**, you can set the **Next Number for Printing** setting as well. 4. For Tickets that are issued on Car laptops through the Admin Portal, there is a setting that show **Drivers License on Tickets** if you wish that to print. 5. **Enable the Signature Required on Tickets** setting if you want there to be an area to include a signature. 6. The Print settings for tickets issued via a laptop are included in the **Printable Area for Tickets** section. ### Using this FeatureOffence types can apply to a Vehicle, a Person or both. [Refer to this wiki article](https://opscom.wiki/books/setup-configuration-for-admins/page/ticket-offence-items) for information about setting up your Offence Type items.
##### Enter a Violation for a Vehicle 1. Hover over **Violations**, and click **Violation Entry.** The **Enter Basic Violation Information** screen provides several fields and options to detail the violation. 2. Enter all known information into the provided fields: - **Ticket Writer** - Admin user who is issuing the ticket. - **Ticket Number**, if **Auto Generated** is enabled, ticket numbers will be **automatically generated** by the system. - [**Ticket Category**](https://opscom.wiki/books/setup-configuration-for-admins/page/ticket-categories) from the dropdown list. 3. Click the Toggle More Options button to show: - **Spoiled**: This is used to **cancel a manual ticket**. Enabling this allows incrementally numbered paper violations to be accounted for even if they are not issued (e.g., if a physical ticket was ruined). - **Warning**: All violations can now be issued as a **warning** by enabling this checkbox. You no longer need to pick "Warning" as a separate Ticket Type. - **Towing**: if there is a towing charge you would enter the dollar amount here. 4. **Search Vehicles**: Click the **Search Vehicles** button to find vehicle information using the license plate or VIN number. - From the search results, you can: - Click the **Plate number** to select and associate that vehicle with the violation. - Click the **Edit** button to edit the vehicle details if needed. - Click the **Permit icon** to view the permit details for the vehicle. - Click the **Red Flag icon** to view Alarms related to this individual. -(This is only available if the Alarms feature is enabled).
- Click the **Red Alerts button** to see Incident Alerts associated with this individual. -(This is only available if the Incidents feature is turned on).
- If the vehicle does not exist in the system, you will have the option to **add a new vehicle**. This is crucial for logging hard-copy or anonymous tickets. 5. Enter the [**Location**](https://opscom.wiki/books/setup-configuration-for-admins/page/locations) from the dropdown list, the **Offences** you are issuing, the **Comments** if any can also be added. 6. Add any pictures as evidence by using the **Attachments** button. 7. After selecting the correct fields and associating a vehicle/person, click the **Record this Violation** button. 8. On the next screen, confirm your violation details by clicking the Record this Violation button, or click the back button on the browser to make changes. 9. Once you have submitted the violation, the **Violation Entry Complete** screen will appear. From here, you have options to: - **Print**: Print a copy of the violation. - **View**: View the newly entered violation's details. - **Search Violations**: Navigate to the Violation Search page to find other violations. - **Search Recent Violations:** Recent tickets you have entered will show up here. - **Enter Another violation** **[](https://opscom.wiki/uploads/images/gallery/2025-06/tQlimage.png)** ##### Enter a Violation for a Person 1. Follow steps 1-3 as above. 2. **Search Person**: Enable the **Failed to Identify** checkbox if the person refuses to give you their ID and to identify themselves. If you do have User details, click the **Search Users** button to find the user by Name, Student or Employee number, or Drivers License. - From the search results, you can: - Click the **Select** button associate that user with the violation. - Click the **Pencil icon** to edit the user details if needed. - Click the **Permit icon** to view the permit details for the vehicle. - Click the **Red Flag icon** to view Alarms related to this individual. -(This is only available if the Alarms feature is enabled).
- Click the **Red Alerts button** to see Incident Alerts associated with this individual. -(This is only available if the Incidents feature is turned on).
- If the user does not exist in the system, you will have the option to **add a new user**. 3. Follow steps 5-9 to record this violationSome Offence types will require both a vehicle and a person to be added.
##### Manually Entering Hard Copy or Anonymous Tickets The manual violation entry process allows for entering tickets that do not have an associated user profile or are hard-copy tickets. - By searching for a vehicle that does not yet exist in the system, you can write an **anonymous ticket** to that plate or transcribe details from **hard-copied tickets** that have no linked user. - The system typically allows users to navigate to the login screen and pay for such tickets using [**OPSCOM Quick Pay/Guest Payments**](https://opscom.wiki/books/OPSCOM-user-portal/page/quick-easy-guest-payments) without needing to log in. --- ### Best Practices & Considerations - **Accuracy is Paramount**: When manually entering violations, ensure all information (plate, location, date, time, offence, fine) is precisely transcribed from the hard copy or incident details to maintain data integrity for tracking and court purposes. - **Utilize "Spoiled" Option**: If you are using pre-numbered paper tickets, consistently use the **Spoiled** checkbox in OPSCOM for any physical tickets that were not issued, to maintain an accurate audit trail of all ticket numbers. - **Leverage Warning Feature**: Use the **Warning** checkbox to issue non-fine warnings, which can be useful for educating parkers or for first-time offenders. - **Vehicle vs. Person Violations**: Understand when to apply a violation to a **Vehicle** versus a **Person** based on the nature of the offence and your organizational policies. - **Comprehensive Linking**: Ensure all relevant photos and documents from your PC are uploaded and linked to the digital violation record for a complete court-ready package. - **Training**: Train staff thoroughly on the manual entry process, especially regarding correct data fields, vehicle/person selection, and the use of "Spoiled" and "Warning" features. # 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. [](https://opscom.wiki/uploads/images/gallery/2024-06/Eb0image.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/ICgimage.png) Click on the box that says "**Lookup your** **Ticket**". You should now see the following screen. Enter in the ticket number and PIN. [](https://opscom.wiki/uploads/images/gallery/2024-06/W7timage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/OXHimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/Lfpimage.png) 2. Look for **Violations** in the list of components on the left: [](https://opscom.wiki/uploads/images/gallery/2024-06/KGgimage.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. [](https://opscom.wiki/uploads/images/gallery/2024-06/xYBimage.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 OPSCOM software. [](https://opscom.wiki/uploads/images/gallery/2024-06/bjXimage.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. # Notice Letter Templates # Introduction This page allows the admin to manage, create, and edit the content and appearance for notice letters used within the system. Notice letters, also known as a Notice of Impending Conviction (NIC) letter, are part of the MTO process, and are sent out to let a user know of an impending conviction for any outstanding violations on their account, to be collected through the Ontario court system. # Templates The appearance and layout of notice letters is setup within the notice letter templates page. The templates page for notice letters can be found under the system configuration menu, within the content & designs submenu. [](https://opscom.wiki/uploads/images/gallery/2024-06/jGKimage.png) On the templates page, an overview of all notice letter content within the system is shown. Different content and templates must be created for each language that is installed on the site. The notice letter templates page consists of two sections: ## **Content** **noticeLetter** - the template used when printing a notice letter containing a single violation. - **noticeLetterMultiple** - the template used when printing a notice letter that contains multiple violations. ## **Templates** **styles** - element styling to be applied to the notice letters. This is done using Cascading Style Sheets (CSS), a type of coding used to affect how parts of the notice letter looks, such as assigning a specific colour and size to a paragraph of text. - **Header** - the content that appears in the header of the notice letter.There is now the option to have a warning letter sent to those who have received a violation marked as a warning. Violations marked as a warning have had their fine amount waived.
## Setup & Configuration To enable the sending of warning notices: - Go to **System Configuration**, then **System Settings**, and scroll down to the **Violations** sub-menu. - Enable the setting named **Send Notices For Warnings**. - Click **Save Settings**. Once enabled, warning notices will be sent when the system task is run. ## Template The edit the layout of the warning letter: - Go to **System Configuration** > **Content & Designs** > **Email Templates** - Click Edit on the **New Warning Notice** template. [](https://opscom.wiki/uploads/images/gallery/2024-07/jYUimage.png) Here the content of the notice is setup for the email to be sent out to users with warning violations. [](https://opscom.wiki/uploads/images/gallery/2024-07/45mimage.png) ## System Task For the warning notices to be sent out, the system task must be run. - Go to **Tools** > **View System Task Logs**. - Ensure the **New Violation Notices** task is enabled. [](https://opscom.wiki/uploads/images/gallery/2024-07/d32image.png) --- ### Best Practices & Considerations - Like other system tasks, **New Violation Notices** is set to run at a scheduled time while it is enabled. - It can also be run immediately by pressing the run button. - While the setting **Send Notices for Warnings** is enabled, this task will include warning violations in its output. When disabled, the task will only send notices out for violations issued with a fine. - The **task frequency** can be adjusted, however it must be updated manually on our end in the database. Please contact us atWe **strongly recommend** keeping a **longer delay**, as it’s designed to prevent situations where staff may be approached or pressured immediately after issuing a violation.
# Appeal Evidence Uploads OverviewThe **Appeal Evidence Uploads** feature enhances the user experience and streamlines the violation appeals process by allowing users to directly upload supporting evidence, such as images and text documents, to their violation appeals. This eliminates the need for users to send evidence through separate channels and centralizes all appeal-related information within the OPSCOM system.
### How does this Work? This feature integrates directly into the [existing appeal submission workflow](https://opscom.wiki/books/the-opscom-admin-portal/page/managing-violationcitation-appeals). When a user submits an appeal, they will now have the option to attach supporting files. These uploaded files are then securely stored and displayed on the administrator's appeal review page, providing immediate access to all relevant evidence. This significantly reduces the time administrators spend contacting users for supporting documents and streamlines the appeal review process. ### Setup & Configuration 1. Hover over **System Configuration**, and click **System Settings.** 2. On the **Violations** tab, ensure the **Enable Appeals Module** setting is enabled. If it is not, please contact