Violations/Citations and Appeals - OPSCOM ViolationAdmin OperationsCommander works hard to maintain an up to date product wiki! If you have any questions or if you feel something is missing, post about it in the community. 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 OPSCOM 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. 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 . The next setup would be to map your Lot Groups to the appropriate Offence Location: With this set up, logs will be available as they come in: 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.  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: Clicking a row will display the violation entry form. The entry and exit cameras will show the chalk image associated to this entry: Once the details are entered, the chalk record will disappear from the list and the violation can be found by searching for it: 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 Select  Edit  at the top right of the violation and change the  Spoiled  status from  Valid - not spoiled  to  Spoiled . 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 4. Click on the  Edit  button 5. Click on the  Show Appeals Form  link.  6. Select  Cancelled in the Fine Action  field and enter the reason for the cancellation into the  Appeal Admin Comment field. 7. Click on  Update this Violation A pop-up with show a message in the top right of your screen that the " Violation has been updated. " Hiding Zero Dollar Violations Hover over ' System Config ' and click ' System Settings '  Click ' Violations ' to open the Violations settings Enable the ' Hide Zero Dollar Fines ' checkbox to hide zero dollar violations. 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   Page Usage The page will appear as displayed.  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. 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. 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. Restricting Payment of Violations in Court Requested Conviction (CRC) Status  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. Ensure that the following settings are enabled and save the settings:  - Prevent Violation Payment  - Prevent Purchases There are two permissions that deal with the treatment of payments for  CRC  items. To setup these permissions, click  System Configuration, M anage Roles . 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. 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 p urchase 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. 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 . 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. 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. 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: It will be found under the Messages tab. The System Location value is "form11": 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.) 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: Under the Action menu, click "Generate (title of form)": 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: When this setting is enabled, a signature tab will appear when writing a violation on a handheld: The signature will show up on Form 11: 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. 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. The screen will refresh with a list of items required in the  Annual MTO Report . Collections - Flag as Sent to Collections The "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 Go to Violations and click Search. Search for the violation you want to flag. Click the ticket # to open the Violation Information page. Select the Action drop down and click Flag as Sent to Collections . 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 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: A violation is issued with 7 days to pay during which the fine amount may be discounted.  On the 8th day, the fine is no longer discounted. 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. 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.  Notice letters can be issued to drivers who have not paid their violations. This is done using the letter report. 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 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. 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 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 lookup 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: Aris Raw Data Account: Used with an ARIS client using raw format lookups. Aris Abstract Account: Used with an ARIS client using abstract format lookups. Send to Collections: Used to send a report to a typical collections agency outside of the MTO process. 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. 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. 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: 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 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: Violations → Collections → Vehicle Lookup Import 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. Click the Import button. A confirmation message will appear in the top right of the page. 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: Violations → Collections → Send to Court 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. An admin fee can be added to the violation on export. Some municipalities have a fee and some do not. 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: 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. 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. 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: Violations → Collections → Sent to Court Report This will open the Court Requested Conviction - Already Sent Report. 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: 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. 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: Violations → Collections → Flag as Paid by Court Enter a date range and press the search button. A list of the violations that have been sent to court will be returned by the page. 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. 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. Managing Violation/Citation Appeals 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. Hover over System Configuration , and click System Settings. On the Violations tab, ensure the Enable Appeals Module setting is enabled. If it is not, please contact support@ops-com.com . There are a number of settings you can use to help manage appeals once this module is enabled: You can choose the number of days a user has to appeal a violation in the  Appeal Days box. In the  Appeal Notification Email box, enter the email address you would like to receive notifications of new appeals to. In the  Automated Notification Email box, enter the email address you would like automated reports sent to. Enable Adjustments should be toggled on if you want Fines to be adjusted without going through the Appeals process.  If you wish to allow appeals through Fax or Email you should enable the Enable Fax for Appeal Format or Enable Email for Appeal format checkboxes. These appeals will be handled outside of OPSCOM. Remove Discount when Appeal Made should be enabled if you want to disallow the discount once an appeal has been made. Enable Appeal Evidence Uploads should be enabled if you want users to be able to submit PDFs or PNGs as evidence for their appeals. Reset Appeal on Association  should be enabled if you want your users to get the specified appeal time reset on account association, if they hadn't had the chance to make their account yet. Email Templates Hover over System Configuration, then Templates & Design, and click Email Templates . Follow the steps in this wiki article to setup the Appeal Decision email template. This is the template that will be used to communicate to the Appellant your decision. Using this Feature Accessing Appeal Details The  Appeals Report page allows you to access detailed appeal information and take action on each submitted appeal. Hover over  Violations, then Appeals, and click Appeals Report . On the  Appeals Report page, search for Appeals you wish to review. Click  View Info beside the person's name to access the full details of that appeal. The User Appeal History screen displays all information related to the appeal, including user history, and user/vehicle details. Actioning an Appeal Here, you can make a decision on the appeal: Locate the Appeal Management section. Choose one of the following options under Action Taken : Uphold : The appeal is denied, and the original fine amount remains. Reduce Violation : The appeal is partially granted. A new field will appear allowing you to enter a new, reduced fine amount. Cancel Violation : The appeal is fully granted, and the violation is voided. In the Comments to Send to Appellant box, enter your detailed comments explaining your decision regarding the appeal. Click the Submit button when finished to process the appeal. You will see a message indicating the appeal has been processed. The system will automatically email the user with your decision using the Appeal Decision email template you setup.  Alternative Method: Actioning Appeals Directly from Violation Information Administrators can also manage appeals directly from the Violation Information page. While administrators can make changes to basic violation information, remember that once a user pays for the violation, the primary comments fields become locked. For further comments, administrators must use the Violation Notes section. Access the Violation Information page for a specific ticket (e.g., by clicking the ticket number from the Appeals Report or searching for the violation). Click Edit . Click the text  Ticket has not been appealed. Show appeals form (highlighted in Blue ) to reveal the Appeals section. The Appeals Area fields are: Ticket Appealed : Displays the date the appeal was filed and how it was filed (e.g., "Online Appeal"). Fine Action : Choose from Upheld , Reduced , or Cancelled . Offense Value : This amount can be manually edited if Reduced on appeal. It will automatically be reduced to 0.00 if Cancelled . You can also edit the Offence Value directly. Appeal Reason : The reason provided by the user for launching the appeal. This field can be viewed by the user. Appeal Admin Comment : This field is for private appeal notes that are not viewable by the user . Use this for internal administrative comments. Change the Actioned per: field by selecting the Admin account making the changes from the picker. Click Update this Violation . A message will appear confirming that the violation has been updated. Best Practices & Considerations Timely Review : Process appeals promptly to ensure fairness and maintain a good relationship with users. Clear Communication : Ensure your "Comments to Send to Appellant" are clear, concise, and professional, explaining the decision effectively. Internal vs. External Comments : Differentiate between Comments to Send to Appellant (public) and Appeal Admin Comment (private) to maintain appropriate communication and internal notes. Consistency : Apply appeal decisions consistently according to your organization's policies. Reporting : The Appeals Report provides valuable data for analyzing appeal trends, common reasons for appeals, and the outcome of appeal decisions. Use this information to inform future policy adjustments. Payment Lock : Be aware that once a violation is paid, its comments section becomes locked, necessitating the use of Violation Notes for any subsequent administrative comments. Related Video 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.   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.  You will be taken to the Edit Violation Information window. 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. 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.  Paying a Violation Click  Violations  then  Search . 2.The  Violation Search  screen displays. Enter the  violation number   in the Search Text field. In this case we are looking for Ticket Numeber 10-01004 3.  In the search results. click on the  ticket number   to see the  Violation Information. 4.  From the Violation information window click ' Make Payment' . 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.' 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 . 9.  The screen will refresh with a confirmation screen. Click  'Confirm Payment Information ' to continue. 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. 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. The confirmation number of the transaction The violation information (User's Name, Amount of the fine, The date Submitted, Comments and Payment Type) The Date Processed and the name of the Admin user who processed the payment Once the payment has been made you can see in the user's history that the violation has been paid and marked processed. Search for a Violation To search for violations hover over the  Violations  icon and click  Search. The  Violation Search  screen is displayed. Type the plate number or violation you want to search for and click the  Search using only text button. Ticket numbers are composed of two parts, the first part (shown in black below) is the ticket number, and the second part (shown in blue) is the pin number. Admins can search using only the first part, but for security reasons, users must enter both parts of the ticket number to lookup their ticket. 3-001005- 11. 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. At the bottom of the ' Violation Search'  screen, the returned records will be displayed. 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.  Searching By Time Frame 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. 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). 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) By using this filtering method the search will return only violations that were issued between 4:00PM and 7:59pm on February 27th, 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.  Managing Ticket Categories Hover over  Admin Options , select  Violations , then  Manage Ticket Categories Select the Ticket Category that is being updated to allow users to receive violations, in this example Municipal is being selected OPSCOM provides the ability to issue violations directly against an individual person rather than a vehicle. These types of offenses could include violations for smoking, alcohol-related offenses, personal conduct, etc. When configuring such a category, simply select  Users only for the Violation Applies To setting. Select Users in the  Violation Applies To  section Now when entering a violation of this offence type it will be possible to apply the violation to a person.  Creating a Violation on the Admin Portal 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: Hover over System Configuration , and click System Settings . 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. If you wish to have tickets Auto Generated , you can set the Next Number for Printing setting as well.  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. Enable the Signature Required on Tickets setting if you want there to be an area to include a signature. The Print settings for tickets issued via a laptop are included in the Printable Area for Tickets section. Using this Feature Offence types can apply to a Vehicle, a Person or both. Refer to this wiki article for information about setting up your Offence Type items. Enter a Violation for a Vehicle Hover over  Violations , and click Violation Entry. The  Enter Basic Violation Information screen provides several fields and options to detail the violation. 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 from the dropdown list. 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. 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. Enter the Location from the dropdown list, the  Offences you are issuing, the Comments if any can also be added.  Add any pictures as evidence by using the Attachments button. After selecting the correct fields and associating a vehicle/person, click the  Record this Violation button. 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. 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 Enter a Violation for a Person Follow steps 1-3 as above. 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 .  Follow steps 5-9 to record this violation Some 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 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. 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. Click on the box that says " Lookup your   Ticket ". You should now see the following screen. Enter in the ticket number and PIN. 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. Removing the Pin  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.  Look for  Violations  in the list of components on the left: 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. 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.     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. 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. Content Editor This page is where the content of the notice letters can be edited. The content section is a type of WYSIWYG (What You See Is What You Get) editor. When editing the notice letter content, some basic knowledge of HTML (Hyper Text Markup Language) is beneficial. The WYSIWYG (What You See Is What You Get) editor isn't meant for templates, and when editing directly through the interface, problems can occur where the final printed page doesn’t lineup with the template correctly. Minor changes can be made with the editor, but it is recommended for most changes to be made through editing the HTML directly. You can edit the HTML in the editor by selecting Tools → Source Code . Alternatively, the layout of the template can be designed in an external HTML editor, and the source code copy and pasted into the HTML source code box. Short Codes Notice Letters use a functionality called short codes , which are pieces of text used as placeholders for user information when setting up a template. When a notice letter is generated, the short code will be automatically replaced with the relevant user information in the print out. Short codes usable on each type of notice letter template are listed at the bottom of the edit content page, below the content box. A short code placed in the template will automatically be replaced with the details of the user when the notice letter is being generated. For example, if the following short code was placed within the body of the notice letter template: Vehicle: [values show=vehicle.plate] It would be automatically replaced with the vehicle plate when the notice letter is generated, resulting in something like: Vehicle: ABC123 Using Short Codes A short code can be inserted into the content by copy and pasting the short code from the list into the content where the information is wanted to be output in the final notice letter printout. A short code can be copied to the clipboard by using these steps: Highlight the short code within the list Right click the highlighted text Click copy The short code will now be contained within the clipboard The short code can then be pasted into the content using these steps: Left click in the desired area within the content where the information is wanted to appear Press the Ctrl and V buttons on the keyboard at the same time The short code will now be pasted to the location selected within the content Using right click will open a content-specific menu within the content menu, and so can’t be used to paste into the window. Notice Letter Report Introduction The letter report page shows a list of users within the system who are eligible to be sent a notice letter, also known as a Notice of Impending Conviction ( NIC ) letter. Notice letters 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. Notice letters printed from this page are intended to be printed and physically sent to the user who incurred the violation. Page Location The letter report page can be found under the violations menu, within the reports sub menu. If the letter report tab is not present in the menu, it will need to be enabled within the system settings. The enable letter report option is located under the violations tab. Letter Reports Page The letter report page consists of two sections, listing the notice reports that can be printed, and those that cannot be printed. Printable Violation Notice Report This section contains a list of all violations within the system that are able to have a notice letter printed. Selected Template A notice at the top of the section notes which template will be used for the print-out, based on the value of the system setting “Include all unpaid violations”. Having this setting enabled will make all violations for a user be printed on a single notice letter. Otherwise, a single notice letter will be created for each violation. Not Ready to be Sent Enabling this setting will cause violations that are not ready to have their notice letter sent to appear within the list. These violations will have greyed-out text. The notice-ready column will display the amount of time left before a notice letter is able to be sent for the violation. By default, notice letters are able to be sent 7 days after the payment for a violation is past due. Printing the Notice Letter There are two locations from which a notice letter can be printed; a single notice letter can be printed using the print button to the right, or multiple notice letters can be selected and printed at once. The notice letters will be generated as a PDF file and downloaded by the web browser. Uploading a Notice Letter It is possible to upload a notice letter in place of generating one. This is used when a letter or document has already been sent to the user in place of a system-generated notice letter, enabling it to be associated to the violation as if it were system-generated. Un-Printable Violation Notice Report This section lists violations that are unable to have notice letters printed. A notice letter is considered to be unprintable when the associated vehicle is missing user details. This can happen when a user has not filled out all their details, or when a user is not present within the system. In the latter case, the unknown vehicle data must be exported and sent to the MTO for information lookup using the Vehicle Lookup Export. The MTO will return the data lookup in the form of a file, which must then be imported back into the system using the Vehicle Lookup import. After the data has been imported, the user details will be automatically entered into the system and the notice letters can be printed right away. The user data imported in this way is considered temporary and is notated as being from the MTO . For security reasons, MTO import data will be cleared from the system after all violations associated to a vehicle have been cleared. The violations on a vehicle are considered to be cleared after being paid by the driver, or by being sent to collections. Various details are listed for the affected violations, including the reason the notice letter is unable to be printed, and if the vehicle has had its data exported yet. A reminder will be listed for the vehicle if it has had its data exported to the MTO , but hasn’t had its return data imported back into the system yet. Viewing Issued Notice Letters Notice letters that have been issued previously can be viewed from the violation search page. The violation search page can be found under the violations menu. From the violations search page, additional search options can be found by clicking the toggle additional options button located in the top right. This will expand the search box with additional search options. The relevant search option here is Notice Letter Issued. By checking this option, only violations that have had notice letters issued for them will be returned. Notice letters can be viewed from within the violation info window, found by clicking on the ticket number of a violation in the results screen. The notice letters for the violation are listed near the bottom of the window. This will open the notice letter view window, from which the notice letter content can be viewed, or re-downloaded by pressing the print button. Regenerating A Notice Letter In the cases such as when the template of the notice letter is changed, there may be a need to regenerate an existing notice letter. The existing notice letter for the violation can be archived by clicking on the trash icon next to it. This will flag the notice letter as archived, allowing the violation to reappear on the letter report page so it can be printed again. Archiving a notice letter will not delete it from the system, and it will continue to appear on the violation info page, with a notice indicating it has been archived. Templates The appearance and layouts 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. System Settings There are several settings associated to notice letters. There is one setting located under the violations tab. Enable Letter Report If this setting is enabled, the letter report page will be made available for use. There are two settings located under the collections tab. Send Letter To All If this setting is enabled, notice letters will appear in the list for users who have already had the notice letter sent to them by email. Include All Unpaid Violations If this setting is enabled, all unpaid violations for the user will be included on a single notice letter. When disabled, each notice letter will be limited to a single violation. Auto Email Notifications for Warnings 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. Here the content of the notice is setup for the email to be sent out to users with warning violations. 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. 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 at support@ops-com.com  for help. We 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 Overview The 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 . 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 Hover over  System Configuration , and click  System Settings. On the  Violations  tab, ensure the  Enable Appeals Module  setting is enabled. If it is not, please contact  support@ops-com.comcom . Enable Appeal Evidence Uploads should be enabled if you want users to be able to submit files as evidence for their appeals. This setting is enabled by default. Users can upload multiple files per appeal. Supported file types include JPG, PNG, and PDF.  The maximum file size is 12MB per file.  All uploaded files are securely stored and only accessible by authorized personnel.  User Portal Experience  Users will experience a more intuitive and efficient appeal submission process. They can easily upload image and text files to provide all necessary information in one submission. For detailed instructions on how users interact with this feature, please refer this wiki article .