# Ionic - Search Vehicles

# Search Vehicles - OPSCOM Enforce App

<p class="callout info">The **Search Vehicles** function on the OPSCOM enforcement application is the primary tool for field personnel to look up vehicle information by license plate or VIN, verify parking permit status, and initiate enforcement actions. Its primary purpose is to allow enforcement officers to quickly retrieve actionable vehicle data in the field. This guide is intended for operators of OPSCOM handheld units.</p>

## Setup and Configuration

The Vehicle Search function is a core, native component of the handheld application and does not require any special administrative configuration or backend setup to function.

**Admin Side:** No setup is required. Simply ensure your device is actively connected to a network to receive real-time data, though offline cached searches are supported.

<p class="callout info">**Visual Cues and Status Indicators** A colored dot at the top of the search panel indicates the device's current connection status: **Green Dot:** The unit is actively connected to Wi-Fi or a cellular network (3G/LTE). **Yellow Dot:** The unit is not connected. Searches can still be performed using cached data, but the information may not be real-time.</p>

## Using this Feature

Enforcement personnel can use this feature to query vehicles using manual text entry, voice commands, or the device's camera for optical character recognition.

### Performing a Vehicle Search

Tap **Vehicle Search** from the main menu and use one of the three methods below to enter vehicle information.

1. Select a **Parking Lot Group** in the drop-down menu
2. Select a **Parking Zone** in the drop-down menu

**Text Search**

1. Tap the text field on the Vehicle Search screen to activate the on-screen keypad.
2. Enter the full license plate number or Vehicle Identification Number (VIN).
3. Tap the **Search** button.

**Voice Search**

1. Tap the **microphone** icon to activate the voice recognition feature.
2. Clearly speak the license plate number when the prompt appears. The system will transcribe the speech directly into the search field.
3. Tap the **Search** button.

**LPR and OCR Camera Search**

1. Tap the **camera** icon to enter License Plate Recognition (LPR) search mode.
2. Position the device's camera so the vehicle's license plate is aligned within the on-screen rectangle.
3. Tap and Hold the screen to capture an image of the plate.
4. Tap the correct plate number from the resulting list of possibilities to initiate the search.

### Reviewing Search Results

After a successful search, the vehicle and permit details will appear below the search area. Tapping on the vehicle record expands a yellow ribbon, revealing available actions for that specific vehicle. You can also tap directly on the permit information displayed under the license plate for a quick view of its expiry details.

### Available Actions and Buttons

- **Virtual Chalk:** Tap this button to apply a virtual chalk to the vehicle, logging its current location and time for time-limit enforcement.
- **Issue Violation:** Tap this button to proceed directly to the violation issuance screen for this specific vehicle.
- **Details:** Tap this button to view a comprehensive sc<span class="citation-851 citation-end-851">reen displaying all permit and vehicle details.</span>

---

## <span class="citation-850 citation-end-850" style="color: rgb(22, 145, 121);">Best Practices and Considerations<sup class="superscript embedded" data-turn-source-index="2"></sup></span>

## <span style="color: rgb(22, 145, 121);"></span>

- <span style="color: rgb(22, 145, 121);">**<span class="citation-849">Connect to a network when possible:</span>** **<span class="citation-849 citation-end-849">While offline searches are possible thanks to the device's data cache, always connect to <sup class="superscript embedded" data-turn-source-index="3"></sup></span>a network when possible.** This ensures you are working with the most current, real-time permit and violation data.</span>
- <span style="color: rgb(22, 145, 121);">**Optimize your camera scans:** **For best results with the LPR <span class="citation-847 citation-848">and OCR camera search, ensure the license plate is well-lit, clean, and fills as much of the alignment rectangle as possible.</span>**<span class="citation-847 citation-848 citation-end-848"><sup class="superscript embedded" data-turn-source-index="4"></sup></span><span class="citation-847 citation-end-847"><sup class="superscript embedded" data-turn-source-index="5"></sup></span></span>
- <span style="color: rgb(22, 145, 121);">**<span class="citation-845 citation-846">Reduce audio interference:</span>** **<span class="citation-845 citation-846 citation-end-846">For the most accurate voice search results, speak clearly in an environment with minimal ba<sup class="superscript embedded" data-turn-source-index="6"></sup></span><span class="citation-845 citation-end-845"><sup class="superscript embedded" data-turn-source-index="7"></sup></span>ckground noise.**</span>

# Search Vehicle Results - OPSCOM Enforce App

<p class="callout info">The Search Vehicle Results screen allows field personnel to interpret the information returned after looking up a specific vehicle. Its primary purpose is to help officers verify parking rights, review a vehicle's history, and make informed enforcement decisions directly in the field. This guide is intended for personnel using OPS-COM Android handheld units.</p>

## Setup and Configuration

While the handheld results screen requires no configuration for the end-user, administrators control how much historical violation data is sent to the devices.

**Admin Side:**

1. Hover over **System Configuration** and click **System Settings**.
2. Click the **Violations** tab.
3. Locate the **Violation History on Handhelds** setting.
4. Set the desired date range (e.g., 6 months or 12 months) to limit how far back the visible violation list goes on the handheld devices.

## Using this Feature

After performing a vehicle search, the application presents detailed information in a multi-layered interface, starting with a high-level summary and allowing you to drill down into specific details.

### Results Summary

Immediately after a successful search, a list of potential plate matches is shown while a summary for the vehicles is displayed.

- **Key Information Displayed:** The license plate, Province/State, and the type of vehicle (e.g., passenger, commercial).

### Quick Actions (More Details)

Tap the vehicle record in the results list to expand the **More Details** section. This reveals further information on the make, model, color of the car (if available), details on the violation history, and a set of quick action buttons.

- **Chalk:** Tap this button to instantly initiate the Virtual Chalking workflow for time-limit enforcement.
- **Violation:** Tap this button to proceed directly to the Issuing a Violation screen for the selected vehicle.
- **Details:** Tap this button to open a comprehensive screen containing the vehicle's complete history.

### The Details Screen

Tap the **Details** button for a complete overview of a vehicle's record. This screen is the central hub for all historical data related to a vehicle in the system and is organized into three distinct tabs.

**Current Permits Tab**

- **Key Information Displayed:** A complete list of all current permits associated with the license plate. Each entry provides key information such as the permit type, its validity period (start and end dates), and the specific lots where it is valid.

**Violations Tab**

- **Key Information Displayed:** A historical log of all violations previously issued to the vehicle. For each entry, you can review the violation date, type of infraction, and its current status (e.g., paid, outstanding).
- **All-Time Violations:** This count includes every non-spoiled violation the vehic<span class="citation-884 citation-end-884">le has ever received (Total Paid, Unpaid, and Warnings). This all-time total may be higher than the actual list of violations visible on the page because the list is filtered by the administrative history setting, while this s<sup class="superscript embedded" data-turn-source-index="1"></sup></span>ummary counts absolutely everything.
- **History Period Violations:** This count only includes violations that occurred within the date range set by your administrator. This ensures officers apply escalation policies correctly (e.g., booting after 3 violations in the last 12 months) without accidentally counting ancient history.

<p class="callout info">The **All-Time Violations** count on the Violations tab will always exactly match the total violation count displayed in the **More Details** section of the main search results screen.</p>

**Recent Chalk Records Tab**

- **Key Information Displayed:** A history of all Virtual Chalking events for the vehicle. It serves as a log to track time-limit enforcement, displaying the date, time, and location of each chalking instance.

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Review all tabs:** **Always review all three tabs in the Details screen to get a complete vehicle history before issuing a violation.** A pattern of previous violations or chalks can provide important context for enforcement and escalation.</span>
- <span style="color: rgb(22, 145, 121);">**Check permit validity closely:** **When checking the Current Permits tab, pay close attention to the valid dates and lot assignments for each permit** to ensure the vehicle is compliant at the exact current time and location.</span>
- <span style="color: rgb(22, 145, 121);">**Monitor your connection status:** **Always check the connection dot at the top of the search panel, as the accuracy of the data depends on the device's last synchronization.** A green connection dot indicates you are viewing real-time information, while a yellow dot means you are viewing potentially outdated data from the device's local cache.</span>

# LPR Scanning

<p class="callout info">The LPR Scanning interface provides real-time data and visual cues when using the handheld's License Plate Recognition (LPR) capabilities. Its primary purpose is to help field officers quickly identify vehicles in violation, track chalked vehicles, and effectively monitor their active scanning status during patrols. This article is intended for OPS-COM administrators and field enforcement personnel using the application.</p>

## Setup and Configuration

The LPR scanning interface relies on core system settings established in the <span class="citation-1079 citation-1080 citation-end-1080">backend, but the interface itself is ready to use natively within the app.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-1079 citation-end-1079"><sup class="superscript embedded" data-turn-source-index="2"></sup></span>

**<span class="citation-1077 citation-1078 citation-end-1078">Admin Side: <sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-1077 citation-end-1077"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>**<span class="citation-1075 citation-1076 citation-end-1076">Administrators should ensure that lot grace periods, permit rules, and any vehicles of interest (hotlists) are accurately configured within the core OPS-COM administrative portal, as the handheld relies on this dat<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-1075 citation-end-1075">a to display the correct flags.<sup class="superscript embedded" data-turn-source-index="6"></sup></span>

**<span class="citation-1074 citation-end-1074">User Side (Enforcement Staff): <sup class="superscript embedded" data-turn-source-index="7"></sup></span>**<span class="citation-1073 citation-end-1073">No specific device setup is required. Enforcement officers s<sup class="superscript embedded" data-turn-source-index="8"></sup></span>imply need to log in to the OPS-COM Enforce app and navigate to the LPR scanning section with their device's camera or external LPR hardware active.

## Using this Feature

The LPR screen is designed to present crucia<span class="citation-1071 citation-1072 citation-end-1072">l enforcement data rapidly as the officer moves through a lot.<sup class="superscript embedded" data-turn-source-index="9"></sup></span><span class="citation-1071 citation-end-1071"><sup class="superscript embedded" data-turn-source-index="10"></sup></span>

### <span class="citation-1069 citation-1070 citation-end-1070">Key Information Displayed<sup class="superscript embedded" data-turn-source-index="11"></sup></span><span class="citation-1069 citation-end-1069"><sup class="superscript embedded" data-turn-source-index="12"></sup></span>

- **<span class="citation-1067 citation-1068">Running Scan Total:</span>**<span class="citation-1067 citation-1068 citation-end-1068"> Located on the right side of the screen, just above the recent read list. This number indicates the to<sup class="superscript embedded" data-turn-source-index="13"></sup></span><span class="citation-1067 citation-end-1067">tal amount of plate reads success<sup class="superscript embedded" data-turn-source-index="14"></sup></span>fully captured during your current patrol session.
- **Camera Directional Arrow:** An orange arrow displayed beside the plate image indicates exactly which camera (e.g., the right-side camera) captured the recent plate read.

### Visual Cues and Status Indicators

The system uses colored flags to instantly communicate the status of a scanned license plate:

- **Red Flag:** Indicates the scanned p<span class="citation-1066 citation-end-1066">late is currently in violation.<sup class="superscript embedded" data-turn-source-index="15"></sup></span>
- **<span class="citation-1065">Green Flag:</span>**<span class="citation-1065 citation-end-1065"> Indicates the scanned plate holds a valid permit or authorization.<sup class="superscript embedded" data-turn-source-index="16"></sup></span>
- **<span class="citation-1064">Orange Flag:</span>**<span class="citation-1064 citation-end-1064"> Indicates the vehicle has been chalked and is currently still with<sup class="superscript embedded" data-turn-source-index="17"></sup></span>in its allowed grace period.

<p class="callout warning">**If no cameras are configured** to the account and area the **Key Info**, **Visual Cues** and **Status Indicators** like mentioned above will not show up when you open the **LPR Scanning** tab. In the **top right corner** there will be a small message letting you know there are no connected cameras and head to settings to add them. </p>

### Available Actions and Buttons

- **Parking Lot Group/Zone drop-down menu:** Tap these menus to select the group and the parking zone to scan through.
- **<span class="citation-1063">Plates-of-Interest Toggle:</span>**<span class="citation-1063"> Tap this toggle located at the top of the</span><span class="citation-1063 citation-end-1063"> panel to initiate alert-only scanning. Once selected, no standard permit validation will be performed, vehicles will continue to be chalked normally, and loud aler<sup class="superscript embedded" data-turn-source-index="18"></sup></span>t notifications will be presented on the dev<span class="citation-1062 citation-end-1062">ice only if a specific vehicle of interest is seen.<sup class="superscript embedded" data-turn-source-index="19"></sup></span>
- **<span class="citation-1062 citation-end-1062">Plate</span>**<span class="citation-1062 citation-end-1062"> **Entry:** You have two options - Manual Entry and Voice Entry. Either type in the plate or read the plate out loud to be transcribed in order to find all details linked to it in the system.</span>

---

## <span style="color: rgb(22, 145, 121);"><span class="citation-1061 citation-end-1061">Best Practices and Considerations<sup class="superscript embedded" data-turn-source-index="20"></sup></span></span>

- <span style="color: rgb(22, 145, 121);">**<span class="citation-1060">Always resume scanning after edits:</span>** **<span class="citation-1060">Remember to tap the ON button after manually editing a plate read.</span>**<span class="citation-1060 citation-end-1060"> Failing to toggle the scanner back to green me<sup class="superscript embedded" data-turn-source-index="21"></sup></span>ans the system remains in offline mode, and subsequent plates will not be scanned as you continue your patrol.</span>
- <span style="color: rgb(22, 145, 121);">**Utilize alert-only mode for targeted patrols:** **Use the Plates-of-Interest toggle when specifically hunting for scofflaws, stolen vehicles, or banned users**, rather than performing general parking enforcement. This streamlines the patrol process and prevents the officer from being dis</span><span class="citation-1059 citation-end-1059"><span style="color: rgb(22, 145, 121);">tracted by standard permit validation alerts.</span><sup class="superscript embedded" data-turn-source-index="22"></sup></span>

# Incorrect LPR Reads Updating

<p class="callout info">The Incorrect LPR Reads Update process allows officers to manually correct license plate numbers that were misread by the device's camera. Its primary purpose is to ensure accurate enforcement and maintain reliable database records by fixing optical character recognition (OCR) errors directly in the field. This article is intended for OPS-COM administrators and field enforcement personnel usin<span class="citation-1483 citation-1484 citation-end-1484">g the handheld application.</span></p>

## <span class="citation-1481 citation-1482 citation-end-1482">Setup and Configuration<sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-1481 citation-end-1481"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>

<span class="citation-1479 citation-1480 citation-end-1480">This correction feature is native to the LPR scanning module and does not require any specialized backend setup.<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-1479 citation-end-1479"><sup class="superscript embedded" data-turn-source-index="6"></sup></span>

**<span class="citation-1477 citation-1478 citation-end-1478">Admin Side: <sup class="superscript embedded" data-turn-source-index="7"></sup></span><span class="citation-1477 citation-end-1477"><sup class="superscript embedded" data-turn-source-index="8"></sup></span><span class="citation-1473 citation-1474 citation-end-1474"><sup class="superscript embedded" data-turn-source-index="11"></sup></span><span class="citation-1473 citation-end-1473"><sup class="superscript embedded" data-turn-source-index="12"></sup></span>**<span class="citation-1471 citation-1472 citation-end-1472">Ensure you are logged into the application and actively conducting <sup class="superscript embedded" data-turn-source-index="13"></sup></span><span class="citation-1471 citation-end-1471">patrols using the LPR scanning tool.<sup class="superscript embedded" data-turn-source-index="14"></sup></span>

## <span class="citation-1470 citation-end-1470">Using this Feature<sup class="superscript embedded" data-turn-source-index="15"></sup></span>

<span class="citation-1469 citation-end-1469">Enfo<sup class="superscript embedded" data-turn-source-index="16"></sup></span>rcement personnel can seamlessly correct misread plates without having to exit their active patrol session.

### Correcting a Plate Read

1. Tap **LPR Scanning** from the main menu to open the LPR Scanning page.
2. Locate the incorrectly read plate from the active list of plate reads generated during your patrol.
3. Tap the text field of the incorrect plate and manually type the correct alphanumeric characters (e.g., if the camera read VZ7281, but the actual plate is BVZT282, type the missing letters).
4. Tap **Search &amp; Update** to refresh the record and display the updated, correct plate number.
5. Tap the red **OFF** button to toggle it back to the green **ON** state to resume your patrol.

### Visual Cues and Status Indicators

- **Offline Mode Indicator:** The moment you tap into a field to adjust a plate read, the LPR system automatically enters an offline state to prevent the camera from overwriting your work. This is indicated by the main scanning button changing from a green **ON** state to a red **OFF** state.
- **Database Synchronization:** Once you tap **Search &amp; Update**, the correction is not just local to your<span class="citation-1467 citation-1468 citation-end-1468"> screen. The record is immediately updated within the core database to reference the newly corrected plate data.<sup class="superscript embedded" data-turn-source-index="17"></sup></span><span class="citation-1467 citation-end-1467"><sup class="superscript embedded" data-turn-source-index="18"></sup></span>

---

## <span style="color: rgb(22, 145, 121);"><span class="citation-1465 citation-1466 citation-end-1466">Best Practices and Considerations<sup class="superscript embedded" data-turn-source-index="19"></sup></span><span class="citation-1465 citation-end-1465"><sup class="superscript embedded" data-turn-source-index="20"></sup></span></span>

- <span style="color: rgb(22, 145, 121);">**<span class="citation-1463 citation-1464">Always remember to toggle the scanner back to ON after updating a plate.</span>**<span class="citation-1463 citation-1464 citation-end-1464"> If you leave<sup class="superscript embedded" data-turn-source-index="21"></sup></span><span class="citation-1463"> the button in the red </span>**<span class="citation-1463">OFF</span>**<span class="citation-1463 citation-end-1463"> state,<sup class="superscript embedded" data-turn-source-index="22"></sup></span> the system will not capture any subsequent plates as you continue to move through the lot.</span>
- <span style="color: rgb(22, 145, 121);">**Take a moment to verify the physical plate or the captured context image before submitting a fix.** This ensures that you do not accidentally introduce a secondary typo while c</span><span class="citation-1462 citation-end-1462"><span style="color: rgb(22, 145, 121);">orrecting the initial OCR error.</span><sup class="superscript embedded" data-turn-source-index="23"></sup></span>

# Message Alerts Tab

<p class="callout info">The Message Alerts feature provides a centralized communication channel for pushing important news, updates, and urgent notifications directly to patrol officers' handheld devices. Its primary purpose is to help administrators ensure field staff are immediately aware of changing situations, safety notices, or operational directives. This article is intended for OPS-COM administrators and field enforcement personnel using t<span class="citation-1778 citation-1779 citation-end-1779">he application.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-1778 citation-end-1778"><sup class="superscript embedded" data-turn-source-index="2"></sup></span></p>

## <span class="citation-1776 citation-1777 citation-end-1777">Setup and Configuration<sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-1776 citation-end-1776"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>

<span class="citation-1774 citation-1775 citation-end-1775">The messaging system is native to the application and requires no specialized configuration on the mobile device itself.<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-1774 citation-end-1774"><sup class="superscript embedded" data-turn-source-index="6"></sup></span>

**<span class="citation-1772 citation-1773 citation-end-1773">Admin Side: <sup class="superscript embedded" data-turn-source-index="7"></sup></span><span class="citation-1772 citation-end-1772"><sup class="superscript embedded" data-turn-source-index="8"></sup></span>**<span class="citation-1770 citation-1771 citation-end-1771">Administrators create and push alert messages to all active un<sup class="superscript embedded" data-turn-source-index="9"></sup></span><span class="citation-1770 citation-end-1770">its or individual specific handhelds via the core OPS-COM administrative portal.<sup class="superscript embedded" data-turn-source-index="10"></sup></span>

**<span class="citation-1769 citation-end-1769">User Side (Enforcement Staff): <sup class="superscript embedded" data-turn-source-index="11"></sup></span>**<span class="citation-1768 citation-end-1768">No setup is required. Enforcement officers simply need to be logged into the handheld </span>application and maintain an active network connection (Wi-Fi or cellular) to receive incoming messages.

## Using this Feature

Enforcement personnel can receive alerts in real-time or review previously sent messages at their convenience through the application interface.

### Reviewing Message Alerts

1. Tap **Message Alerts** from the main menu of the OPS-COM Enforce application to open the message center.
2. Review the list of recent alerts sent to your device.

### Message Notifications

When a new message is pushed to the device, officers are notified through several standard methods even if the app is running in the background:

1. Look at the device's top header bar to see new message icons as they arrive.
2. Swipe down on the header bar to open the notification shade for a quick preview of the alert text.
3. Tap the specific alert notification to automatically open the OPS-COM application and navigate directly to the Message Alert list.

<p class="callout info">**App Icon Badges** If you are on the device's home screen, the OPS-COM application shortcut icon will display a notification badge (a small numbered dot) indicating that you have unread messages waiting.</p>

### Visual Cues and Status Indicators

Alerts are categorized into three distinct types, indicated by color, to help officers instantly gauge the priority of the message:

- **<span style="color: rgb(53, 152, 219);">Blue Alerts</span>:** These alerts are for general informational purposes (e.g., a reminder about an upcoming shift change).
- **<span style="color: rgb(241, 196, 15);">Yellow Alerts</span>:** These alerts are used to inform users of events or situations that should be actively monitored (e.g., a large event causing lot congestion).
- **<span style="color: rgb(224, 62, 45);">Red Alerts</span>:** These alerts are reserved for high-priority situations that require immediate action or response from the officer.

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Acknowledge notifications promptly:** **Officers should routinely check their notification shade and the Message Alerts menu while on patrol.** Ensuring timely review of incoming messages is critical, especially when Red Alerts are dispatched for immediate action.</span>
- <span style="color: rgb(22, 145, 121);">**Prevent alert fatigue:** **Administrators should reserve Red Alerts strictly for genuine emergencies or time-sensitive directives.** Overusing the highe<span class="citation-1767 citation-end-1767">st priority alert for standard informational updates can cause officers to become desensitized to actual urgent situations.</span></span>

# Violations View

<p class="callout info">The Violations Tab is a specific section within the *[Search Vehicle Results](https://opscom.wiki/books/opscom-enforce-ios-android/page/search-vehicle-results-opscom-enforce-app "Search Vehicle Results - OPSCOM Enforce App")* screen on the OPS-COM Enforce application. Its primary purpose is to provide field officers with a detailed historical log of all past violations issued to a specific vehicle, assisting them in making informed and escalated enforcement decisions. This article is intended for OPS-COM administrators and field enforcement personnel using the handheld application.</p>

## Setup and Configuration

The Violations Tab automatically retrieves its historical ticket data directly from the central database.

**Admin Side:** No specific configuration i<span class="citation-1971 citation-1972 citation-end-1972">s required on the handheld device. Administrators manage all violation histories, payment statuses, and escalation policies within the core OPS-COM administrative portal.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-1971 citation-end-1971"><sup class="superscript embedded" data-turn-source-index="2"></sup></span>

**<span class="citation-1969 citation-1970 citation-end-1970">User Side (Enforcement Staff): <sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-1969 citation-end-1969"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>**<span class="citation-1967 citation-1968 citation-end-1968">No specific device setup is required. The historical<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-1967 citation-end-1967"> data populates automatically during vehicle searches, provided the device has a network connection.<sup class="superscript embedded" data-turn-source-index="6"></sup></span>

## <span class="citation-1966 citation-end-1966">Using this Feature<sup class="superscript embedded" data-turn-source-index="7"></sup></span>

<span class="citation-1965 citation-end-1965">Enforcement perso<sup class="superscript embedded" data-turn-source-index="8"></sup></span>nnel use this tab to review a vehicle's citation history and current payment compliance before issuing new tickets.

### Accessing the Violations Tab

1. Perform a plate or VIN query using the **Search Vehicles** function.
2. Tap the specific plate read from the initial search results list .
3. Tap the **Details** tab in the extended plate read menu.
4. Open up the **Violations** section of the **vehicle details** page.

### Key Information Displayed

- **Violation Date/Time:** The exact date and time that the ticket was issued.
- **Violation Number:** The Violation # that was assigned when the ticket was added to the system.
- **Offense Location:** The specific lot or zone where the infraction occurred.
- **Violation Type:** The nature of the offense (e.g., Parked in No Parking Area).
- **History Summary:** A high-level count of the vehicle's past violations (e.g., within the last 18 months), including a breakdown of paid, unpaid, and warning counts.

### Visual Cues and Status Indicators

Each individual violation record features a clear, color-coded status indicator on the right side of the screen denoting the **Payment Status Text**:

- **PAID** (typically displayed in green) indicates the citation has been resolved.
- **UNPAID** (typically displayed in red or orange) indicates there is still an outstanding balance for that specific infraction.
- **CANCELLED** (typically displayed in grey) indicates that the citation is no longer open.

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Review unpaid violations before ticketing:** **Always check the Violations tab for a history of unpaid tickets or repeated offenses.** Identifying a pattern of unpaid or frequent violations is critical for enforcing escalation policies, such as initiating a tow or applying a boot.</span>
- <span style="color: rgb(22, 145, 121);">**Ensure data synchronization:** **Always verify your device has an active connection when reviewing violation history.** If your device is operating strictly from its offline cache, recent ticket payments or newly issued citations from other officers may not be immediately reflected on</span><span class="citation-1964 citation-end-1964"><span style="color: rgb(22, 145, 121);"> this tab.</span><sup class="superscript embedded" data-turn-source-index="9"></sup></span>

# Chalking View

<p class="callout info">The Chalks Tab is a dedicated section within the Search Vehicle Results screen on the legacy OPS-COM Parking Enforcement application. Its primary purpose is to display a historical log of virtual chalking events for a specific vehicle, assisting officers in accurately enforcing time-limited parking zones. This article is intended for OPS-COM administrators and field enforcement personnel using the legacy Android application.</p>

## Setup and Configuration

The Chalks Tab automatically compiles its data directly from previous virtual chalking events performed by enforcement officers in the field.

**Admin Side:** No specific configuration is req<span class="citation-2221 citation-2222 citation-end-2222">uired on the handheld device to view this tab. Administrators manage global chalking grace periods and settings within the core OPS-COM administrative portal.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-2221 citation-end-2221"><sup class="superscript embedded" data-turn-source-index="2"></sup></span>

## <span class="citation-2216 citation-end-2216">Using this Feature<sup class="superscript embedded" data-turn-source-index="7"></sup></span>

<span class="citation-2215 citation-end-2215">Enforcement <sup class="superscript embedded" data-turn-source-index="8"></sup></span>personnel use this tab to review past chalking records to determine if a vehicle has overstayed its allowed time in a specific location.

### Accessing the Chalks Tab

1. Perform a <span class="citation-2214">plate or VIN query using the </span>**<span class="citation-2214">Search Vehicles</span>**<span class="citation-2214 citation-end-2214"> function.<sup class="superscript embedded" data-turn-source-index="9"></sup></span>
2. <span class="citation-2213 citation-end-2213">Tap the specific plate read from the initial search results list.<sup class="superscript embedded" data-turn-source-index="10"></sup></span>
3. <span class="citation-2212">Tap the </span>**<span class="citation-2212">Details</span>**<span class="citation-2212 citation-end-2212"> button to open the extended vehicle record.<sup class="superscript embedded" data-turn-source-index="11"></sup></span>
4. <span class="citation-2211">Tap the </span>**<span class="citation-2211 citation-end-2211">C<sup class="superscript embedded" data-turn-source-index="12"></sup></span>halks** tab (or swipe left/right across the screen to navigate to it).

### Key Information Displayed

- **Chalk History:** Chalk records are listed chronologically, displaying from the most recent event at the top to the oldest at the bottom.
- **Time Stamp:** The specific date and exact time the chalk event occurred.
- **Map Location:** A visual map snippet illustrates exactly where the vehicle was parked when it was chalked.
- **Chalk Comments:** Any notes or comments entered by the patrol officer at the time of the initial chalking.
- **Distance Calculation:** A distance reading (in meters) indicating exactly how far your present physical position is from the location of the first chalk record.

### Available Actions and Buttons

- **Camera:** Tap the camera icon on a specific chalk record to display the full-size image captured during that initial chalking event.

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

- <span style="color: rgb(22, 145, 121);">**Review chalk images before ticketing:** **Always tap the camera icon to verify the chalk image is clear and the vehicle has not moved.** Ensuring the evidence is solid and time-stamped correctly is crucial for defending against potential parking appeals.</span>
- <span style="color: rgb(22, 145, 121);">**Leverage chalk comments:** **Encourage officers to add descriptive comments when initially chalking a vehicle.** Notes providing valuable context (e.g., valve stem positions, specific parking bays, or vehicle damage) are highly visible on this tab and can assist the same or other officers upon their return patrol.</span>

# Notifications from Permit Misuse

<p class="callout info">The Permit Misuse Notification feature alerts parking enforcement officers when multiple vehicles sharing the exact same permit are scanned within a specified timeframe. Its primary purpose is to help identify and deter fraudulent permit sharing on-site, ensuring users are not abusing multi-vehicle permit privileges. This article is intended for OPS-COM administrators and field enforcement personnel using the Enforce handheld application.</p>

## Setup and Configuration

This feature is configured directly on the handheld enforcement device. Setting a timer dictates exactly<span class="citation-627 citation-628 citation-end-628"> how long the system remembers the first vehicle's capture before resetting the misuse window.<sup class="superscript embedded" data-turn-source-index="1"></sup></span><span class="citation-627 citation-end-627"><sup class="superscript embedded" data-turn-source-index="2"></sup></span>

**<span class="citation-625 citation-626 citation-end-626">Admin Side: <sup class="superscript embedded" data-turn-source-index="3"></sup></span><span class="citation-625 citation-end-625"><sup class="superscript embedded" data-turn-source-index="4"></sup></span>**<span class="citation-623 citation-624 citation-end-624">Administrators or supervisors must configure the specific duration of the misuse timer on the device itself.<sup class="superscript embedded" data-turn-source-index="5"></sup></span><span class="citation-623 citation-end-623"><sup class="superscript embedded" data-turn-source-index="6"></sup></span>

1. <span class="citation-621 citation-622">Tap </span>**<span class="citation-621 citation-622">System Settings</span>**<span class="citation-621 citation-622 citation-end-622"> from the main menu o<sup class="superscript embedded" data-turn-source-index="7"></sup></span><span class="citation-621 citation-end-621">f the handheld application.<sup class="superscript embedded" data-turn-source-index="8"></sup></span>
2. <span class="citation-620">Scroll to the **Violations and Chalking**</span><span class="citation-620"> section and tap </span>**<span class="citation-620">Permit Misuse Window</span>**<span class="citation-620 citation-end-620">.<sup class="superscript embedded" data-turn-source-index="9"></sup></span>
3. <span class="citation-619">Tap the </span>**<span class="citation-619 citation-end-619">Permit Sharing an<sup class="superscript embedded" data-turn-source-index="10"></sup></span>d Misuse drop-down** menu to open the duration options.
4. Choose the desired length of time (e.g., 1 Hour). Setting this time immediately activates the function.

## Using this Feature

Enforcement personnel do not need to perform any special actions to use this feature; it operates seamlessly alongside standard vehicle searches during an active patrol.

### Triggering a Misuse Alert

1. Perform a standard plate or VIN query using the **Search Vehicles** function while on patrol.
2. Acknowledge any on-screen pop-ups before proceeding with standard enforcement actions.

### Visual Cues and Status Indicators

- **Permit Misuse Alert Popup:** If you search for a vehicle that shares a permit with another vehicle that was recently scanned within the active timer window, a prominent alert will appear directly on the device screen. This immediately notifies the officer of possible permit misuse.

<p class="callout info">**Understanding the Timer Cycle** If your timer is set to one hour, the system will present a warning if the second vehicle is scanned within 60 minutes of the first vehicle's scan. After that hour has passed, the first read is effectively forgotten by the handheld's local cache, and th<span class="citation-618 citation-end-618">e monitoring process starts over.</span></p>

---

## <span style="color: rgb(22, 145, 121);"><span class="citation-617 citation-end-617">Best Practices and Considerations<sup class="superscript embedded" data-turn-source-index="12"></sup></span></span>

- <span style="color: rgb(22, 145, 121);">**<span class="citation-616">Establish a clear enforcement policy:</span>** **<span class="citation-616">Organizations should develop a strict business rule for how officers handle a misuse alert.</span>**<span class="citation-616 citation-end-616"> Officers need clear directives on whether to issue a standar<sup class="superscript embedded" data-turn-source-index="13"></sup></span>d parking violatio<span class="citation-614 citation-615 citation-end-615">n, write a specific permit fraud citation, or attempt to verify the physical presence of both vehicles on-site before ticketing.<sup class="superscript embedded" data-turn-source-index="14"></sup></span><span class="citation-614 citation-end-614"><sup class="superscript embedded" data-turn-source-index="15"></sup></span></span>
- <span style="color: rgb(22, 145, 121);">**<span class="citation-612 citation-613">Tailor the timer to your environment:</span>** **<span class="citation-612 citation-613">Carefully consider the length of your misuse timer based on your lot turnover and specific permit policies.</span>**<span class="citation-612 citation-613 citation-end-613"> A timer that is too short ma<sup class="superscript embedded" data-turn-source-index="16"></sup></span><span class="citation-612 citation-end-612">y miss abusers <sup class="superscript embedded" data-turn-source-index="17"></sup></span>who stagger their arrival times, while a </span><span class="citation-611 citation-end-611"><span style="color: rgb(22, 145, 121);">timer that is excessively long may capture legitimate instances where family members legally swap parking spots halfway through the day.</span><sup class="superscript embedded" data-turn-source-index="18"></sup></span>