The Locate Application Version Legacy guide details how to easily find the current software version and unique handheld identifier for the older OPSCOM Parking Validation Enforcement App. Its primary purpose is to help administrators and enforcement staff verify that their mobile devices are running the most up-to-date software, which is critical for troubleshooting and maintaining system compatibility. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy application.
## Setup and Configuration To ensure your enforcement device is running correctly, staff must download and maintain the application via official app stores. No backend administrative configuration is required. **Admin Side (Enforcement Staff):** 1. Open the Apple App Store or Google Play Store on your handheld device. 2. Search for the **OPSCOM Parking Validation** application. 3. Tap the application to view its specific store details. 4. Tap the **Update** button if it is visible. If the button displays as **Install** or **Open**, you are either installing it for the first time or already running the latest available store version. ## Using this Feature Enforcement personnel can locate the version details in two different locations within the legacy application, making it accessible whether you are actively logged in or not. ### Locating on the Login Screen 1. Open the **OPSCOM Parking Validation** app on your handheld device. 2. Remain on the initial Login Screen. 3. Look directly below the main login box and input fields to find the version details and the unique handheld identifier clearly listed. ### Locating via the About Screen 1. Log into the application and navigate to the main menu. 2. Tap **About** to open a pop-up message. This message will display a brief description of the OPSCOM application alongside the exact version number. 3. Tap **OK** on the pop-up to close the message and return to the main menu. --- ## Best Practices and Considerations - **Keep devices updated:** **Regularly check the app store to ensure enforcement handhelds are running the latest version of the application.** Running outdated versions can lead to unexpected synchronization errors or connectivity drops in the field. - **Provide details for support:** **Always provide the precise Application Version and Handheld Identifier when submitting support tickets.** Supplying this specific hardware and software information allows the OPSCOM support team to diagnose device-specific issues much more efficiently.**Transitioning to Modern Apps** Please note that this article pertains to the legacy version of the OPSCOM enforcement application. If your organization has upgraded to the newer mobile application, the interface and steps to locate version information may differ.
# Replication Status (Legacy)The Replication Status Legacy screen within the older OPSCOM Android application displays the synchronization state of all local database tables against the central server. Its primary purpose is to help identify connectivity issues and allow users to manually manage data synchronization when standard automated syncing fails. This article is intended for OPSCOM administrators and field enforcement staff using the legacy application.
## Setup and Configuration The Replication Status feature is built natively into the legacy application and does not require backend configuration. **Admin Side:** Staff must have the legacy OPSCOM parking enforcement app installed on their handheld device and be logged in to view the local database tables. ## Using this Feature Enforcement personnel can use this feature to check the health of their connection and manually force data pushes if records are failing to upload automatically. ### Viewing System Status 1. **Tap** the **Replication Status** option from the main application menu. 2. Review the list of database tables on the Record Counts and Data Table Tools screen. ### Visual Cues and Status Indicators The following icons are used to clearly indicate the synchronization status of each individual table: - **Green Checkmark:** Table data is successfully synchronized with the server. - **Red X:** Table data is NOT synchronized with the server. - **Blue Exclamation Point:** There is currently no table data that needs to be synchronized between the handheld and the server.**During normal field use (i.e., when actively issuing violations), it is completely expected that tables like VehicleTransfer and ViolationsTransfer may temporarily display a Red X.** This simply indicates that new data has been captured on your local device and is waiting in the queue to be pushed to the server.
### Replication Actions (Table-Specific) You can perform targeted actions on individual tables if they are stuck or experiencing issues. 1. **Tap and Hold** an individual table to open a pop-up message with additional options. 2. **Tap** one of the following actions: - **Push table data to the server:** This will attempt to manually upload the local device's table data to the server. This is generally safe to do, as nothing is overwritten or removed. - **Rebuild and retrieve table data:** This option will permanently delete the local table data and retrieve the newest available data from the server. - **Delete local table data:** This will permanently delete the local table data but has no effect on the server. - **Email debug details to Tomahawk:** This will send an email log file to [OPSCOM Support](https://support.ops-com.com/) containing helpful information for troubleshooting issues. ### Replication Options (System-Wide) There are additional system-wide options available to manage the entire database at once. 1. **Tap** the **Menu** icon located in the top right-hand corner of the screen. 2. **Tap** one of the following actions: - **Rebuild database:** This will delete ALL local table data across the entire device. - **Synchronize all:** The device will attempt to safely synchronize ALL table data with the server. - **Send config to Tomahawk:** This will send a comprehensive email log file to support for debugging. - **Download new config:** The device will re-download all relevant system settings (e.g., organization details, device name, ticket footer) on the next startup. --- ## Best Practices and Considerations - **Rely on standard login for synchronization:** **If your unit is working correctly, none of these manual options should be necessary.** We highly recommend simply logging out and logging back into the application as needed, which acts as a safe, natural trigger for proper synchronization. - **Avoid unauthorized rebuilds or deletions:** **Never select the rebuild or delete functions unless explicitly instructed by OPSCOM Support.** Doing so without manually pushing your data first can result in the permanent loss of violations or vehicle data that has not yet been synchronized to the server. - **Communicate before sending logs:** **If you need to use the Email debug details option, please notify the OPSCOM support team first if possible**, or only select it when actively requested by a support technician. # Setup Installation and Maintenance # First Time Installation - AndroidThe First Time Installation - Android guide outlines how to download and set up the legacy parking enforcement application on a new mobile device. Its primary purpose is to ensure field officers successfully download the application from the Google Play Store and understand the initial registration and permission requirements. This article is intended for OPSCOM administrators and field enforcement personnel provisioning new handheld devices.
## Setup and Configuration The installation requires both administrative setup in the web portal and physical configuration on the Android device. **Admin Side:** Administrators must ensure that field users have the correct access rights before they can log in. Specifically, the user profile must have the **Add New Violation** permission enabled under the **Violations Permissions** settings in the core portal. **User Side (Enforcement Staff):** 1. Tap the **Google Play Store** app on the device's main screen to open it. 2. Tap the search bar and type **OperationsCommander** or **OPSCOM**. 3. Tap the **OPSCOM** application icon from the search results to access the store page. 4. Tap the **Install** button to begin the download process. 5. Tap **Accept** on the settings pop-up window to grant the application access to required device integrations. 6. Tap the **Open** button directly within the store once the installation completes, or return to the device's home screen and tap the newly created **OPSCOM** app shortcut. ## Using this Feature Because this is a one-time installation process, interacting with the software primarily involves completing the initial launch and capturing the device's unique identifier. ### Initial Application Launch Upon opening the application for the very first time, the system will prevent immediate login and display a registration warning. - **Application UUID Prompt:** A message will pop up stating that the device is not registered. This message displays a unique UUID number. This string is critical, as your administrator needs this exact UUID to manually register and authorize the physical tablet within the main OPSCOM system. --- ## Best Practices and Considerations - **Document the UUID immediately:** **Officers should take note of the UUID displayed upon first launch and provide it to their supervisor.** The application cannot proceed past the login screen until an administrator registers this specific hardware ID. - **Verify user permissions:** **If an officer's account login fails after the UUID has been registered, contact your organization's high-level administrator.** The login failure is likely due to the user account missing the mandatory **Add New Violation** permission on the backend. # Manual Update or InstallationThe Manual Update or Installation process allows users to install or update the legacy Android enforcement application directly from the Google Play Store. Its primary purpose is to ensure field officers have the latest software version on their handheld devices for optimal performance and access to new features. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup & Configuration To use the software, the officer's user profile must have the proper permissions granted in the core OPSCOM system before they attempt to log into the mobile application. **Admin Side:** Administrators must ensure that field users have the "Wireless handheld" permission enabled. 1. Hover over **System Config** and click **Manage Roles**. 2. Click **Permissions** beside the specific Administrator Role you wish to edit (e.g., Patrol Officer). 3. Click the **Violations** tab. 4. Enable the **Display as Ticket Writer** checkbox. **User Side (Enforcement Staff):** Ensure the Android handheld device is connected to a stable Wi-Fi or cellular network before attempting to download or update the application. ## Using this Feature Field personnel can manually check for and install updates using the native Android app store. ### Installing or Updating the Application 1. Tap the **Google Play Store** app on the device's Apps screen. 2. Tap the search bar and enter **OperationsCommander** or **OPSCOM**. 3. Tap the **OperationsCommander** app icon to open the installation page. 4. Tap the **Install** button to perform a fresh installation, or tap the **Update** button to perform an in-place update of the existing software. 5. Tap **Accept** when the settings window pops up requesting access to integrated device features. *(Note: On newer tablets, these permission requests may appear during the initial startup of the application instead).* 6. Tap the **Open** button directly within the Play Store, or return to the device's home screen and tap the newly created shortcut to launch the application.**Install vs. Update** Tapping the **Install** button performs a fresh installation where a new shortcut and a fresh local database are created. Tapping the **Update** button performs an in-place update, meaning a new database is not created and your existing local data will not be disrupted.
--- ## Best Practices & Considerations - **Always synchronize before updating:** **It is highly recommended to perform a full manual data sync before proceeding with any kind of update.** While an update typically will not disrupt existing data, syncing first guarantees that no offline tickets or chalk records are lost during the software transition. - **Grant all requested permissions:** **It is critical to grant access to all requested permissions during installation or initial startup.** The OPSCOM application requires these integrations (such as camera, location, and storage) to function correctly in the field. # Testing Your WIFI ConnectionThe Testing Your WIFI Connection process guides users in diagnosing wireless network stability on Android handheld devices using a third-party application. Its primary purpose is to help identify signal drops and channel congestion that may disrupt real-time communication with the server. This article is intended for OPSCOM administrators and field enforcement staff.
## Setup and Configuration To accurately test your network connection, you must install a specific third-party diagnostic application on your Android handheld device. **Admin Side:** 1. Open the Google Play Store on your Android handheld device. 2. Search for and download **WifiAnalyzer (open-source)** by VREM Software Group. This is a free utility application. ## Using this Feature Administrators and staff can use this application to take a precise measurement of their Wi-Fi strength and identify the source channel to aid in troubleshooting. ### Monitoring Wi-Fi Strength 1. Open the **WifiAnalyzer** application on your device. 2. **Tap** the hamburger icon (three parallel lines) located at the top left of the screen to open the main menu. 3. **Tap** **Access Points** to view a graphic representation of your available networks and their current signal strengths. 4. **Tap** the hamburger icon again and select **Channel Graph** to view a visual representation of channel congestion and overlapping network signals. ### Visual Cues & Status Indicators - **Signal Strength Graph:** The signal strength is visually represented as a column of color rising from the bottom of the graph, typically ranging from -100 dBm to -20 dBm. - **Reading dBm Values:** Signal strength is measured in negative numbers. The smaller the negative number, the higher (stronger) the signal. Keep in mind that a value closer to zero (e.g., -20 dBm) indicates a much better signal than a lower number (e.g., -100 dBm). --- ## Best Practices & Considerations - **Monitor signal fluctuations throughout the day.** It is highly recommended to check the app periodically, especially when drops in signal occur. Observing how much the signal goes up and down can help pinpoint exactly when connectivity drops. - **Check channel congestion.** Pay close attention to how many devices or networks are broadcasting on the exact same channel. Too many devices trying to access the same channel simultaneously will create interference and have a severe adverse effect on your connectivity strength. - **Capture data for support.** **Please provide screen captures of both the Access Points and Channel Graph screens when contacting OPSCOM support.** Having a visual record of the exact dBm reading for your Wi-Fi source and the channel congestion allows the support team to assist you much more effectively. # Uninstalling the ApplicationThe Uninstalling the Application process outlines how to safely remove the legacy OPSCOM Parking Enforcement app and its associated data folders from an Android handheld device. Its primary purpose is to guide users through a standard removal or a full clean data purge to prepare the device for troubleshooting or a fresh installation. This article is intended for OPSCOM administrators and IT support personnel.
## Setup and Configuration Before removing the application, it is critical to ensure that all local data has been safely transferred to the core database. **Admin Side:** Administrators should ensure the device has an active network connection and verify that all recent patrol data has successfully synchronized to the backend. **User Side (Enforcement Staff):** Field staff must log in to the application one final time and check the **Replication Status** page to ensure all records have been pushed to the server. ## Using this Feature The uninstallation process can be completed natively on the Android device. In the event of a full clean install, residual files must also be deleted using the device's file manager or a connected PC. ### Standard Application Uninstall 1. Tap **Settings** from the main Android applications menu. 2. Tap the **General** tab. 3. Tap **Applications** under the Device Manager section to view the installed apps list. 4. Tap the **OperationsCommander** application in the list. 5. Tap **Uninstall** to remove the application from the unit. ### Full Clean Install with Data Purge In some cases, [OPSCOM Support](https://support.ops-com.com/) may ask you to perform a full clean install. This requires removing the app (following the steps above) and manually deleting all associated local files to prevent artifacts from affecting the new installation.**Data Loss Prevention** If you are uninstalling the software to reinstall it, do not uninstall the software if the **ViolationTransfer** and/or **VehicleTransfer** tables contain data (viewable under **Replication Status**). These tables must be replicated to the server first to avoid permanent data loss and integrity issues.
#### Delete Files with Handheld Tools 1. Tap the **App Tray** at the bottom right of the home screen display. 2. Tap the **My Files** application. 3. Locate and Tap and Hold the **OPSCOM** folder from the directory list. 4. Tap **Delete** from the pop-up options window. 5. Tap **OK** on the confirmation screen to remove the folder and all its contents. #### Delete Files using a PC (USB Connection) 1. Connect the handheld device to your computer via USB. 2. Open **Windows Explorer** and locate the device under **This PC**. 3. Click **Tablet** (or internal storage) to view the file content of the device. 4. Locate the folder named **OPSCOM**. 5. Right-click the folder and click **Delete** from the drop-down menu to remove the folder and all its contents. --- ## Best Practices and Considerations - **Always verify replication status before uninstalling:** **Ensure the ViolationTransfer and VehicleTransfer tables are completely empty.** Uninstalling with unsynced data will result in permanent data loss for the organization. - **Purge files for persistent issues:** **If the application is crashing frequently, perform the full clean install with a data purge** before reinstalling the OPSCOM Legacy app. This ensures corrupted cache files do not carry over to the fresh installation. # Reinstalling the OPSCOM AppThe Reinstalling the OPSCOM App process guides users through completely removing the legacy Android application and preparing the device for a fresh installation. Its primary purpose is to help resolve persistent application issues or update the software when automated updates are unavailable. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration Before removing the application, it is critical to ensure that the device is prepared and that no local data is left unsynchronized. **Admin Side:** Administrators should ensure the device has a stable Wi-Fi or cellular connection to successfully download the new application package once the old version is removed. **User Side (Enforcement Staff):** Enforcement officers must verify that all recent patrol data (such as offline violations or chalk records) has successfully synchronized to the backend database before beginning the uninstallation process. ## Using this Feature The uninstallation process is performed natively through the Android operating system's application manager. ### Uninstalling the Application 1. Tap **Settings** from your device's home screen or app drawer. 2. Tap the **General** tab at the top of the settings menu. 3. Tap **Applications** under the **Device Manager** section on the left side of the screen to bring up a list of installed apps on the right. 4. Scroll through the list and tap the **OPSCOM** application. 5. Tap **Uninstall** to remove the application and its base data from the unit.**Data Loss Prevention** Never uninstall the application while you have active, unsynced data on your device. Removing the application will permanently delete all local cache files, and any violations that have not been pushed to the main server will be lost.
### Reinstalling the Application Once the application has been successfully removed from the Android device, you must download and install a fresh copy. 1. Please refer to the *[Manual Update or Installation](https://opscom.wiki/books/legacy-android-enforcement-app-OPSCOM-parking-enforcement/page/manual-update-or-installation)* article for complete, step-by-step instructions on downloading the APK file and setting up the new application. --- ## Best Practices and Considerations - **Perform a full clean install for persistent issues:** **If a simple uninstallation does not resolve application crashes or performance issues, you may need to perform a full clean install.** This involves manually deleting residual OPSCOM folders from the device's internal storage before reinstalling. - **Keep the operating system updated:** **Ensure the Android OS is up-to-date before reinstalling the OPSCOM application.** Installing a fresh version of the app on an outdated operating system can lead to unexpected compatibility issues. # Retrieve Local Tablet BackupsThe Retrieve Local Tablet Backups process allows organizations to access and extract offline violation data directly from an Android handheld device's internal storage. Its primary purpose is to recover locally stored violations in the event of a synchronization failure, accidental application uninstallation, or database error before the records are successfully uploaded to the server. This article is intended for OPS-COM administrators and IT support personnel.
## Setup and Configuration Extracting these files requires physical access to the device and a wired connection to a workstation. **Admin Side:** Administrators must have a physical USB connection cable and a PC to access the device's internal file system. **User Side (Enforcement Staff):** Ensure the Android tablet is powered on and actively unlocked before connecting it to the computer.**Locating a USB Cable** If you do not have a dedicated USB data cable, check the tablet's charging unit. Most charging cables feature a detachable USB plug that can be removed from the wall adapter and plugged directly into your PC.
## Using this Feature Administrators must connect the device to a PC, locate the specific application data folder, and transfer the files to OPSCOM support for recovery. ### Connecting the Tablet to a PC 1. Connect the tablet to your computer using a compatible USB cable. 2. Unlock the tablet screen so the PC can authorize the connection and read the internal storage. 3. Click the USB connection notification on your PC, or navigate manually through **File Explorer** to **This PC** and open the tablet's internal storage drive. ### Locating and Copying Backup Files 1. Navigate through the tablet's internal storage to the following folder path: **Android\\data\\com.operationscommander.handheld\\files\\Backups**. 2. Select all backup files located within this folder (or the specific files requested by support). 3. Copy the selected files. 4. Paste the files into a new, temporary folder on your local computer's desktop (e.g., "Tablet Backups"). ### Sharing Backups with Support Once the files are secured on your local computer, they must be shared with the support team to complete the recovery. 1. Open a web browser and navigate to Google Drive. 2. Click **New** and select **Folder Upload**. 3. Select the temporary backup folder you created on your desktop to begin the upload. 4. Wait for the upload status window in the bottom right corner of the screen to confirm all files have successfully uploaded. 5. Share the uploaded folder withYou may also email the backup files directly to support if the overall file size is small enough to attach.
--- ## Best Practices and Considerations - **Unlock the device before connecting:** **Always ensure the tablet screen is unlocked before plugging it into the USB port.** PCs cannot read the internal file system of a locked Android device due to native security protocols. - **Clean up temporary files:** **Delete the temporary backup folder from your local desktop once the support team confirms successful receipt.** This keeps your PC free of unnecessary files and protects sensitive organizational violation data. # Connecting as USB Hard DriveThe Connecting as USB Hard Drive process allows users to physically link their Android handheld device to a desktop computer to access its internal file system. Its primary purpose is to enable the direct transfer, copying, or backup of application data and files (such as local OPSCOM folders) without relying on a network connection. This article is intended for OPS-COM administrators and IT support personnel managing the legacy Android application.
## Setup and Configuration This procedure relies on the native Android operating system and a physical connection to a desktop computer. **User Side (Enforcement Staff):** The handheld device requires a physical USB data cable and must have Developer Options enabled within the Android operating system to allow debugging and mass storage access. ## Using this Feature To access the device's file system, you must first enable the correct connection mode on the handheld, then navigate the file structure on your desktop computer. ### Enabling Developer Options If you do not already see a Development option in your settings menu, follow these steps to unhide it: 1. Tap **Settings** from the device's main menu. 2. Scroll down and tap **About phone**. 3. Scroll down to locate **Build number**. 4. Tap **Build number** seven times in rapid succession. A notification will appear confirming that the Developer setting is now unlocked. ### Connecting the Device 1. Tap **Settings**, select **Applications**, tap **Development**, and enable the **USB debugging** checkbox. 2. Plug the USB cable into your desktop computer and connect the other end to your Android device. A USB icon will appear in the device's top status bar. 3. Swipe down from the top edge of the Android device screen to reveal the notification shade. 4. Tap **USB Connected** and select the option to mount the device (e.g., **Connect USB storage** or **Mount**). 5. Tap **Ok** to confirm. The Android icon will change color (typically to orange), indicating the phone is now in USB Mass Storage mode. ### Accessing Files on the Desktop Computer 1. Open the file explorer on your desktop computer and navigate to the connected devices or removable storage section. 2. Click the newly mounted hard drive letter associated with the Android device. 3. Locate and click the **OPSCOM** folder (sometimes labeled **ParkAdmin**) to browse, copy, or transfer the required files.**Disable Mass Storage Mode** Turn off USB hard drive mode on the handheld device immediately when you are finished copying files. Leaving this connection active can cause read/write conflicts and operational issues with the OPSCOM software.
--- ## Best Practices and Considerations - **Use a data-capable cable:** **Ensure the USB cable you are using supports data transfer.** Some standard charging cables only provide power and will fail to trigger the USB connection prompt on your computer or device. - **Safely eject the device:** **Always safely eject the USB drive from your desktop computer's operating system before physically unplugging the cable.** This prevents data corruption within the OPSCOM folders during active file transfers. --- ### Related Video # Google AccountThe Google Account configuration process guides users on how to add a Google profile to their Android handheld device. Its primary purpose is to grant access to the Google Play Store for downloading, updating, and troubleshooting the legacy OPS-COM Parking Enforcement app, as well as managing beta releases. This article is intended for OPS-COM administrators and field enforcement personnel configuring their devices.
## Setup and Configuration You will require a valid Gmail email account and password to access the Google Play Store on your handheld device. **Admin Side:** Administrators configuring field devices prior to deployment should ensure the device is connected to a stable network and a standardized organizational Google account is available for use. **User Side:** Depending on your Android version, the exact naming conventions may vary slightly, but the core steps remain the same. 1. Tap **Settings** from the main menu of your Android device. 2. Tap **Accounts** (or **Users & Accounts**). 3. Tap **Add account** from the settings list. 4. Tap **Google** from the list of available account types. 5. Enter your assigned Gmail email address and password, then follow the on-screen prompts to finalize the login.**Removing an Account** If you already see Google in the accounts area and need to switch profiles, you can remove existing Google accounts from the device by tapping **Google** and selecting the remove option before adding the new account.
## Using this Feature Enforcement personnel and administrators use the active Google account to manage app updates, clear system caches, and opt into beta testing directly through the Google Play Store. ### Clearing Google Play Cache Google Play will cache application details for hours to even a day or more. Clearing the cache ensures that the most recent version of the application that is available is accessible to your device. 1. Access your device's native app settings. 2. Tap the **Google Play Store** application. 3. Tap **Storage** or **Storage & cache**. 4. Tap **Clear cache** to remove the temporary data. ### Joining or Leaving the Beta Program At times, new beta (non-production) releases may be offered that address client-reported issues or new functionality. Clients may test the beta versions to ensure issues are resolved and that normal functionality is not disrupted. 1. Navigate to the [Beta Program on Android](https://play.google.com/store/apps/details?id=com.operationscommander.handheld) on your handheld device, or the [Beta Program on the Web](https://play.google.com/apps/testing/com.operationscommander.handheld) on a desktop browser. 2. Scroll down the page to determine your current status under the beta header. 3. Tap **Join** to enter the program, and tap **Join** (or **Confirm**) a second time when prompted. 4. Tap **Leave** if you wish to remove yourself from the beta program and no longer receive pre-release updates. --- ## Best Practices and Considerations ## - **Limit beta testing to specific devices:** **We recommend that only one device be used for the Beta program as these releases may be unstable.** Testing on a single, dedicated unit ensures normal operations are not disrupted for the rest of your enforcement fleet. - **Verify your active profile:** **Ensure the handheld operates under the specific Google profile intended for beta access.** If you are not sure what account you are using, review the linked accounts under settings within Android. Alternatively, simply follow the beta links above to use whatever profile you are currently logged into. - **Clear cache for missing apps:** **If you cannot see the OPS-COM app or the latest update on the Play Store, clear the Google Play cache immediately.** If issues persist, there are additional troubleshooting steps available for [Google Play Store app visibility issues](https://www.maketecheasier.com/fixes-for-google-play-store-my-apps-not-showing/). --- ### Related Video # Application LogoutThe Application Logout process safely secures the legacy OPSCOM Android application and triggers an automatic synchronization of field data with the main database. Its primary purpose is to protect user accounts and ensure all citations, chalks, and vehicle updates captured during a patrol shift are uploaded to the central server. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The logout process is a core functionality built into the application and requires minimal backend setup. **Admin Side:** Administrators must ensure user credentials and permissions are properly maintained in the central portal so field officers can log back in for subsequent shifts. **User Side (Enforcement Staff):** Enforcement officers must ensure the handheld unit has an active Wi-Fi or cellular network connection prior to initiating the logoff process to guarantee complete data synchronization. ## Using this Feature Enforcement personnel must complete the logout procedure at the end of every shift or whenever handing off a device to another officer. ### Executing the Shutdown Process 1. Tap **Application Logout** from the main menu of the OPSCOM application. 2. Tap **OK** on the confirmation pop-up message to confirm logoff. 3. Allow the application to perform the automatic data synchronization before returning to the main login screen.**Logout Without Connectivity** If you log off in an area without internet access, the software will still lock securely (requiring a password to sign back in), and all shift data will save locally on the tablet. However, the data will not upload to the server until a manual or startup synchronization occurs when connectivity is restored.
### Confirming Data Synchronization 1. Tap **Synchronize Data** prior to logging off if you receive an error or suspect recent shift data did not sync automatically. 2. Tap **Replication Status** to verify that all pending records have successfully replicated to the main database. --- ## Best Practices and Considerations - **Ensure active connectivity before logging off:** **Always verify your device has an active internet connection before initiating the logoff process.** This ensures all newly created violations and vehicle records immediately sync to the central server. - **Complete proper logoff at shift end:** **Always use the formal Application Logout button rather than simply closing or minimizing the app.** Logging off properly secures the application with password protection and prevents unauthorized access to sensitive enforcement records. - **Verify replication status:** **Check the Replication Status screen if you experience network drops during logoff.** Confirming that zero unsynced records remain ensures no data is left stored exclusively on the handheld unit. # Using the OPSCOM App in DEMO ModeThe Using the OPSCOM App in DEMO Mode feature allows users to explore and test the legacy OPSCOM Parking Enforcement application without needing to officially register a handheld device. Its primary purpose is to provide a safe, pre-populated sandbox environment for training and familiarizing staff with the software's core functions. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration No formal registration or backend configuration is required to access the demonstration environment. **Admin Side:** Administrators do not need to configure specific user permissions or device profiles within the core OPSCOM portal for devices operating strictly in demo mode. **User Side (Enforcement Staff):** Enforcement officers simply need to ensure the legacy Android application is successfully installed on their handheld device. ## Using this Feature Enforcement personnel can bypass the standard device registration screen to access a fully functional, pre-populated version of the application for testing purposes. ### Accessing Demo Mode 1. Boot up the application after the initial installation on your Android device. 2. Tap **DEMO MODE** on the initial *Device Not Recognized* pop-up screen. 3. Review the sign-in screen. The demonstration username and password credentials will automatically populate. 4. Tap **LOGIN** to access the main index screen and begin testing. ### Available Actions and Testing Scope Once logged into DEMO mode, users can practice various core enforcement actions without affecting live database records. Recommended testing actions include: - **Searching Vehicles:** Querying by plate or VIN. - **Searching Permits:** Verifying active and unpaid permits. - **Searching People:** Looking up user profiles and associated vehicles. - **Virtual Chalking:** Practicing the digital tire chalking workflow. - **Issuing Violations:** Generating both person and plate-based citations. ### Key Information Displayed: Test Data Profiles The demonstration environment is pre-loaded with sample data. Use the following profiles to test different search queries, permit statuses, and violation scenarios:| **Username** | **First Name** | **Last Name** | **User Type** | **Plate** | **VIN Number** | **Violations** | **Permits** |
| spencer | Spencer | Carr | Full Time Staff | SPENCE | |||
| jparsons | Julie | Parsons | Complimentary | JULPAR ASDA347 | 1q21242143124213 | COM100 - Unpaid | |
| jrockwood | James | Rockwood | F/T Student | JROCK | 5SXHANDC38RZ55506 | R102 - Red Student Lot W | |
| sjamieson | Steph | Jamieson | P/T Student | SJAM SJAM2 | 2T1BU4EE5DC972469 1N4AL3AP5DN517821 | TT-10001 | 100 - Red Student W 102 Red Student W |
| johndoe | John | Doe | F/T Staff | ABC316 | 1FMCU0EG1CKB65454 | 501 - Unpaid | |
| skjones | Jones | Sarah | Daily Reserved | AKRJ259 | |||
| vcosta | Voula | Costa | Daily Reserved | VCOST | 2GCEC19V531113601 | L103 - Unpaid | |
| bcameron | Brady | Cameron | Complimentary | BCAM | COM100 - Unpaid | ||
| sbyers | Sheldon | Byers | Daily Reserved | SHELBY | 1G8ZN12871Z117051 | L100 - Unpaid | |
| pbirch | Patricia | Birch | F/T Staff | BIRCH No Plate | 1N6AD0ER5FN709323 1GKS1AKC7FR518845 | TT-10003 | None |
| mashbury | Micheal | Ashbury | P/T Staff | MASH ASDA437 BDHE385 | JNAMA43H9XGE50339 | 15-170420 TT-10010 | Monthly 0005 - Red Staff Lot West 0002 - Red Staff Lot West 50 -After 4PM 500 - Green Staff Lot East - UNPAID |
The Handheld Training module provides comprehensive multimedia resources, including a slide presentation and a video training playlist, to educate enforcement staff on using the OPSCOM handheld application. Its primary purpose is to help administrators and new field personnel quickly onboard, understand core functionalities, and standardize enforcement operations. This article is intended for OPSCOM administrators and field enforcement staff.
## Setup and Configuration There is no technical backend setup required to utilize these training materials. **Admin Side:** Administrators should simply ensure that new enforcement staff have access to a reliable internet connection to stream the presentation and video content, and provide them with a physical handheld device configured for a test environment if possible. **User Side:** No setup is required. Trainees can simply navigate to this page to view the embedded resources. ## Using this Feature Administrators and trainees interact directly with the embedded media players on this page to complete their initial onboarding or to refresh their knowledge of the handheld application. ### Viewing the Slides Presentation 1. Locate the embedded **Slides Presentation** player on the page. 2. Click the **Next** (right arrow) and **Previous** (left arrow) buttons on the player control bar to navigate through the slides. 3. Review the core concepts, visual diagrams, and workflow instructions detailed in each slide. ### Watching the Training Videos 1. Locate the **Videos Linked in the Presentation** section on the page. 2. Click the **Play** button on the embedded YouTube player to begin the Handheld Training playlist (which includes foundational videos such as the **OPSCOM Handheld Menu Options** guide). 3. Click the **Playlist** icon (typically located in the top right corner of the video player) to view and skip between different videos in the training series. --- ## Best Practices and Considerations - **Follow along with a test device:** **We highly recommend having a handheld device logged into a staging or test environment while reviewing this training.** This allows new users to safely practice navigating menus, capturing plates, and issuing mock violations alongside the videos without affecting live production data. - **Review all materials comprehensively:** **Ensure staff review both the slides and the entire video playlist.** The slides provide excellent theoretical and policy-based grounding, while the videos demonstrate the practical, real-time application of the software in the field.**Legacy Application Note:** These specific training materials are geared toward the legacy Android enforcement app. If your organization has upgraded to the newer mobile application, the interface and exact button placements shown in these videos may differ slightly from your current software.
--- ### Related Videos [Handheld Training playlist](https://www.youtube.com/playlist?list=PLh-g-lutOq9pDRYFrDPa86iwoSTPbUpBT) # Handheld Operation LogThe Handheld Operation Log feature allows the mobile device to record and store data regarding the operations and functions performed on the enforcement unit. Its primary purpose is to help identify and troubleshoot technical issues by providing detailed diagnostic information directly to the support team. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The operation logging feature runs automatically in the background of the handheld application and requires no specialized backend configuration. **Admin Side:** No manual setup is required on the device to begin logging. Officers simply need to ensure the handheld device is connected to a network and synchronizing regularly to allow for automatic log uploads. ## Using this Feature When technical issues arise, [OPS-COM Support](https://support.ops-com.com/) personnel may request that you manually send a log file to them. Administrators and field staff can send, view, or extract these logs using the following methods. ### Sending the Log Manually 1. Log in to the legacy Android application. 2. Tap **Replication Status** from the main menu. 3. Tap the **Menu** icon (three vertical dots) located at the top right of the replication status screen. - *Note: If you do not see the three dots on the screen, your specific tablet may utilize a physical hardware "overflow" button (typically located near the physical home and back buttons). Tap this hardware button to open the context settings.* 4. Tap **Send Log to Tomahawk** to transmit the diagnostic data to the support team. ### Viewing Logs via the About Panel If you need to quickly review the recent log entries without sending them: 1. Navigate to the main menu. 2. Tap **About** to view the application details and review the log file directly on the device screen. ### Extracting Logs via USB If the device is completely offline and cannot transmit the log via the application, it can be extracted manually. 1. Connect the handheld device to a computer using a USB cable or a wireless file transfer application. 2. Navigate the internal storage to locate the OPSCOM application folder. 3. Copy the specific log file to your computer. 4. Attach the copied file to an email and send it directly to your support representative. --- ## Best Practices and Considerations - **Coordinate with support:** **Only manually push logs or extract them via USB when explicitly requested by OPSCOM support personnel.** Unsolicited log files without an associated support ticket may not be reviewed. - **Maintain device connectivity:** **Ensure field devices are brought online and synchronized regularly.** Regular synchronization prevents the local storage from filling up and ensures support has access to recent data if an issue occurs.**Automatic Log Uploads** Log files are natively designed to automatically upload to the OPSCOM server for review once they are more than one day old. For example, logs created on Monday will automatically upload to the server on Tuesday around midnight, assuming the handheld is online and performs a successful synchronization at some point after the 24-hour mark.
# Plate Capture Using HandheldThe Plate Capture Using Handheld functionality utilizes the device camera and License Plate Recognition (LPR) software to quickly identify vehicles in the field. Its primary purpose is to ensure highly accurate plate reads by educating users on proper camera framing, distance, and the use of on-screen guide boxes. This article is intended for OPSCOM administrators and field enforcement personnel using the Android application.
## Setup and Configuration The optical character recognition functionality is built directly into the mobile application and relies primarily on proper physical technique rather than software configuration. **Admin Side:** 1. Open the OPSCOM parking enforcement app on your handheld device. 2. Grant any requested operating system permissions to allow the application to access your device's camera. 3. Tap **Search Vehicles** from the main menu to access the capture screen. ## Using this Feature Enforcement personnel use the on-screen viewfinder to align the license plate, allowing the image processor to extract the alphanumeric characters. ### Framing and Capturing a Plate 1. Tap the **camera** icon to open the viewfinder. 2. Position the device so the license plate is visible within the on-screen bounding boxes. 3. Keep the device steady until the system successfully captures the plate and returns to the Plate Read screen. 4. Tap the captured thumbnail image of the plate to open the full context image. ### Visual Cues & Status Indicators The viewfinder provides two outlined boxes to help determine if minor physical adjustments are needed to properly line up a plate: - **Red Box:** Indicates the maximum scanning area. If the physical plate extends outside of this red area, it will not be read by the system. - **Blue Box:** Indicates the optimal target area. It is highly advisable to keep the entire plate inside this blue box to ensure the LPR engine processes it correctly. --- ## Best Practices and Considerations - **Include the plate edges and background:** **Do not capture the plate too tightly.** It is better to include the entire plate plus some of the vehicle's background. If the physical edges of the plate are excluded from the picture, the LPR engine struggles to distinguish the actual plate number from secondary text (such as province or state names) and may return an incorrect read. - **Exclude complex vanity logos:** **Focus the view specifically on the plate numbers.** If scanning a vanity plate with heavy graphics, position the camera to exclude the logo from the blue bounding box if it consistently confuses the image processor. - **Review context images to correct hardware offsets:** **Tap the thumbnail to view the full context image if your reads are consistently failing.** With some device hardware, the plate may look perfectly centered in the live viewfinder, but the actual processed shot comes out off-center. The context image displays a date-stamped, red bounding box representing exactly where the system processed the image, allowing you to manually adjust your physical centering technique.**Step back and try again:** Do not be afraid to back away from the vehicle if the scanner is struggling. We often exaggerate the distance and pull back quite a bit to yield better results. The image processor can accurately read plates even when they appear surprisingly small within the viewfinder.
# Search Vehicles & Tabs # Search VehiclesThe Search Vehicles feature in the OPSCOM Android application allows enforcement officers to instantly look up vehicle information using text, voice, or License Plate Recognition (LPR). Its primary purpose is to quickly retrieve live permit status and violation history to assist officers in making accurate enforcement decisions in the field. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration The vehicle search functionality is a core component of the handheld application and requires no specialized backend setup. **Admin Side:** Enforcement officers simply need to ensure they have an active session in the application and have granted the device necessary microphone and camera permissions to utilize voice and LPR search methods.**Connection Status Indicator** A colored dot on the search panel indicates your real-time connectivity: **Green Dot:** The unit is actively connected to a Wi-Fi or cellular (3G/LTE) network, providing real-time data. **Yellow Dot:** The unit does not have an active connection. Searches can still be performed using the device's local cache, but data may not be fully up to date.
## Using this Feature Enforcement personnel can query the database using three distinct methods: manual text entry, voice dictation, or the device's LPR camera. Tap **Search Vehicles** from the main application menu to begin. *(Note: If you are connecting to a preview system, an additional menu item at the top of the list will indicate that the device is in Preview Mode).* ### Performing a Text Search 1. Tap the search field and enter the full license plate number or Vehicle Identification Number (VIN) using the on-screen keypad. 2. Tap the **Search** button. ### Performing a Voice Search 1. Tap the **microphone** icon. 2. Wait for the Google Voice Recognition prompt to appear. 3. Speak the license plate number clearly out loud to populate the search field. ### Performing an LPR/OCR Camera Search 1. Tap the **camera** icon to enter LPR Search mode. 2. Line up the physical license plate within the on-screen rectangle. 3. **Tap and Hold** the screen to capture a shot. The screen will refresh with a list of possible plate numbers. 4. Tap the specific plate number that matches the image (e.g., BDHE385) to execute the search. ### Reviewing Results and Available Actions Selecting the vehicle from the search results expands a yellow ribbon detailing the available enforcement options. - **Virtual Chalk:** Tap this button to initiate a time-stamped digital chalk record for time-limit enforcement. - **Issue Violation:** Tap this button to proceed directly to the ticket issuance screen for the selected vehicle. - **Details:** Tap this button to open the comprehensive [Search Vehicle Results](https://opscom.wiki/books/legacy-android-enforcement-app-OPSCOM-parking-enforcement/page/search-vehicle-results) screen, detailing the full permit and violation history. - **Permit Pill:** Tap the specific permit name appearing directly underneath the license plate number to quickly review its expiration details without opening the full history. --- ## Best Practices and Considerations - **Maintain an active connection:** **Always try to maintain a Wi-Fi or 3G/LTE connection (Green Dot) when actively patrolling.** While the yellow dot indicates cached searches are possible, real-time connectivity guarantees you are seeing the most recent permit purchases and user updates. - **Optimize LPR conditions:** **Hold the device steady and ensure the license plate is well-lit and centered within the rectangle** when using the LPR/OCR camera to guarantee the highest accuracy and avoid manual corrections. - **Minimize environmental noise:** **Speak clearly and shield the device's microphone from wind or heavy traffic noise** when using the voice search feature to prevent incorrect plate transcriptions. # Search Vehicle ResultsThe Search Vehicle Results screen in the legacy OPSCOM Parking Enforcement application displays comprehensive vehicle information after a plate search is performed. Its primary purpose is to give patrol officers immediate access to permit, violation, and chalking history so they can make informed enforcement decisions directly in the field. This guide is intended for OPSCOM administrators and field personnel using the legacy Android application.
## Setup and Configuration Viewing vehicle results is a core, native function of the legacy enforcement app and requires no backend administrative configuration. **Admin Side:** No setup is required. You simply need to be logged into the enforcement app and successfully perform a standard vehicle search. ## Using this Feature During a typical plate search, a wealth of actionable information is placed right at the patrol officer's fingertips. ### Viewing Extended Details Tap the specific plate read from the initial search results list to expand the record and view more detailed information. Expanding this record reveals the core enforcement action buttons. ### Available Actions and Buttons - **Chalk:** Tap this button to instantly initiate a virtual chalk record for time-limit enforcement. - **Issue Violation:** Tap this button to begin writing a new violation for the vehicle. - **Details:** Tap this button to drill deeper into the vehicle's complete parking history within your system. ### Reviewing History Tabs After tapping the **Details** button, the application presents three distinct tabs containing the vehicle's historical records. You can tap each tab header or swipe left and right across the screen to navigate seamlessly between them. - **Permits:** Displays any active or past permits associated with the license plate. - **Violations:** Displays the historical log of violations previously issued to the vehicle. - **Chalks:** Displays a history of virtual chalking events for the vehicle to assist with time-limit enforcement tracking. --- ## Best Practices and Considerations - **Review all tabs before ticketing:** **Always check the Permits, Violations, and Chalks tabs before issuing a new violation.** Taking a moment to understand the full vehicle history and current permit status prevents issuing invalid tickets and greatly reduces user appeals. - **Use swipe navigation:** **Take advantage of the swipe gesture to quickly move between the three detail screens.** Swiping back and forth saves time in the field compared to manually reaching up to tap the top tab headers.**Legacy Application Notice** This article pertains specifically to the legacy OPSCOM Parking Enforcement app. If your organization has recently updated to the modern OPSCOM Enforce application, the interface, button placement, and expanded details views will differ from what is described here.
# Permits TabThe Permits 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 legacy OPSCOM Parking Enforcement app. Its primary purpose is to provide field officers with detailed information regarding a vehicle's active and historical permit validity, including specific zone assignments, days, and time restrictions. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The Permits Tab automatically pulls its data directly from the user and permit profiles configured in the backend database. **Admin Side:** No specific configuration is required on the handheld device. Administrators manage all permit rules (such as valid days, hours, and zones) within the core OPSCOM administrative portal. **User Side (Enforcement Staff):** No setup is required. Enforcement officers simply need to be logged into the legacy enforcement app and successfully perform a standard vehicle search. ## Using this Feature Enforcement personnel use this tab to verify if a vehicle is parked legally based on its specific permit rules, rather than just checking if it generally has a permit. ### Accessing the Permits 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** button to open the extended vehicle record. 4. Tap the **Permits** tab (or swipe left/right across the screen to navigate to it). ### Key Information Displayed - **Permit Expiry Date:** Displays the exact expiration date of the permit. The system supports custom expiration dates (e.g., Sep-01-2018) that will accurately reflect here. - **Zone Association:** Displays which specific zones the vehicle is authorized to park in (e.g., the "Day Care" zone or "Centrum and Test Zone"). - **Valid Days and Times:** Outlines the specific days of the week the permit is valid, as well as the exact times the vehicle is allowed to park on those particular days (e.g., from 4:00 PM to midnight). ### Visual Cues and Status Indicators - **Green and Red Bars:** These color-coded bars visually represent whether the vehicle is currently valid to park in specific zones at the time of the search. A green bar indicates active validity for the zone, while a red bar indicates the vehicle is either in the wrong zone or outside of its permitted timeframe. --- ## Best Practices and Considerations - **Check time and zone restrictions carefully:** **Always review the specific days, times, and zone associations listed on the Permits tab before issuing a violation.** A vehicle may have a valid permit, but if they are parked in the wrong zone or outside of their designated hours, they are still subject to a citation. - **Ensure data synchronization:** **Always check your connection status indicator on the main search screen.** The permit details rely on recent data syncs; if you are operating entirely offline for extended periods, recently updated custom expiry dates or newly purchased permits may not immediately display on this tab.**Legacy Application Notice** This article pertains specifically to the legacy OPSCOM Parking Enforcement app. If your organization has recently updated to the modern OPSCOM Enforce application, the interface, tab layout, and visual indicators will differ from what is described here.
# Permit Misuse NotificationThe 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 Android handheld application.
## Setup and Configuration This feature is configured directly on the handheld enforcement device. Setting a timer dictates exactly how long the system "remembers" the first vehicle's capture before resetting the misuse window. **Admin Side:** 1. Tap **System Settings** from the main menu of the handheld application. 2. Scroll to the **Advanced Settings** section and tap **Permit Sharing and Misuse**. 3. Tap the **Permit Sharing and Misuse Timer** 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. ### 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.**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 the monitoring process starts over.
--- ## Best Practices and Considerations - **Establish a clear enforcement policy:** **Organizations should develop a strict business rule for how officers handle a misuse alert.** Officers need clear directives on whether to issue a standard parking violation, write a specific "Permit Misuse/Fraud" citation, or attempt to verify the presence of both vehicles before ticketing. - **Tailor the timer to your environment:** **Carefully consider the length of your misuse timer based on your lot turnover and specific permit policies.** A timer that is too short may miss abusers who stagger their arrival times, while a timer that is excessively long may capture legitimate instances where family members swap parking spots halfway through the day. # LPR Scanning InformationThe LPR Scanning Information 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 OPSCOM administrators and field enforcement personnel using the Android application.
## Setup & Configuration The LPR scanning interface relies on core system settings established in the backend, but the interface itself is ready to use natively within the app. **Admin Side:** Administrators should ensure that lot grace periods, permit rules, and any "vehicles of interest" (hotlists) are accurately configured within the core OPSCOM administrative portal, as the handheld relies on this data to display the correct flags. **User Side (Enforcement Staff):** No specific device setup is required. Enforcement officers simply need to be logged into the OPSCOM Android 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 crucial enforcement data rapidly as the officer moves through a lot. ### Key Information Displayed - **Running Scan Total:** Located on the right side of the screen, just above the recent read list. This number indicates the total amount of plate reads successfully 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 & Status Indicators The system uses colored flags to instantly communicate the status of a scanned license plate: - **Red Flag:** Indicates the scanned plate is currently in violation. - **Green Flag:** Indicates the scanned plate holds a valid permit or authorization. - **Orange Flag:** Indicates the vehicle has been chalked and is currently still within its allowed grace period.**Valid Plate Logging** While Valid Plates (Green Flags) will temporarily list on the handheld unit's screen for the officer's situational awareness, they will **not** be chalked or permanently passed into the backend system as part of the formal LPR events report.
### Available Actions & Buttons - **Scanner Toggle:** When an officer stops to manually edit a plate read, the system automatically enters offline mode, and the scanning status button will change from green to red. Tap the **ON** button to return it to green and resume active scanning. - **Plates-of-Interest Toggle:** Tap this toggle located at the top of the PL8-RDR LPR Scanning panel to initiate alert-only scanning. Once selected, the system behaves differently: - No standard permit validation will be performed. - Vehicles will continue to be chalked normally. - Loud alert notifications will be presented on the device only if a specific "vehicle of interest" is seen. --- ## Best Practices & Considerations - **Always resume scanning after edits:** **Remember to tap the ON button after manually editing a plate read.** Failing to toggle the scanner back to green means the system remains in offline mode, and subsequent plates will not be scanned as you continue your patrol. - **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 distracted by standard permit validation alerts. # Updating Incorrect LPR ReadsThe Updating Incorrect LPR Reads 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 using the legacy Android application.
## Setup and Configuration This correction feature is native to the LPR scanning module and does not require any specialized backend setup. **Admin Side:** No manual setup is required. Enforcement officers simply need to be logged into the legacy Android application and actively conducting patrols using the LPR scanning tool. ## Using this Feature Enforcement personnel can seamlessly correct misread plates without having to exit their active patrol session. ### Correcting a Plate Read 1. Tap the **LPR Scanning** menu item to open the **PL8-RDR LPR Scanning** window. 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 the **Search & Update** button. The record will refresh to 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 the **Search & Update** button, the correction is not just local to your screen. The record is immediately updated within the core database to reference the newly corrected plate data.
--- ## Best Practices and Considerations - **Remember to resume scanning:** **Always remember to toggle the scanner back to ON after updating a plate.** If you leave the button in the red OFF state, the system will not capture any subsequent plates as you continue to move through the lot. - **Verify against context images:** **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 correcting the initial OCR error. # Message AlertsThe 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 OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The messaging system is native to the application and requires no specialized configuration on the mobile device itself. **Admin Side:** Administrators create and push alert messages to all active units or individual specific handhelds via the core OPSCOM administrative portal. **User Side (Enforcement Staff):** No setup is required. Enforcement officers simply need to be logged into the legacy Android 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 OPSCOM 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 Android OS 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 OPSCOM application and navigate directly to the Message Alert list.**App Icon Badges** If you are on the device's home screen, the OPSCOM application shortcut icon will display a notification badge (a small numbered dot) indicating that you have unread messages waiting.
### 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: - **Blue Alerts:** These alerts are for general informational purposes (e.g., a reminder about an upcoming shift change). - **Yellow Alerts:** These alerts are used to inform users of events or situations that should be actively monitored (e.g., a large event causing lot congestion). - **Red Alerts:** These alerts are reserved for high-priority situations that require immediate action or response from the officer. --- ## Best Practices and Considerations - **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. - **Prevent alert fatigue:** **Administrators should reserve Red Alerts strictly for genuine emergencies or time-sensitive directives.** Overusing the highest priority alert for standard informational updates can cause officers to become desensitized to actual urgent situations. # Dispatch LogThe Dispatch Log feature allows administrators and dispatchers to record and track all inquiries or communications that come into the office directly from the handheld device. Its primary purpose is to maintain a formal, time-stamped record of field inquiries, which can later be linked to specific incidents for further tracking and resolution. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The dispatch logging functionality is native to the handheld application and requires minimal backend configuration to use in the field. **Admin Side:** Administrators must ensure that appropriate Log Categories are established within the core OPSCOM administrative portal so that field staff can accurately categorize their entries. ## Using this Feature Enforcement personnel can use this tool to quickly document interactions, dispatch calls, or field inquiries, complete with supporting photographic evidence. ### Adding a Dispatch Log Entry 1. Tap **Dispatch Log** from the main application menu. 2. Tap the **Log Category** drop-down menu and choose the appropriate classification for the inquiry. 3. Tap the text field and enter detailed notes related to the dispatch or inquiry. 4. Tap one of the **camera** icons (represented by a vehicle with a camera) towards the bottom of the screen to attach a supporting image. 5. Tap the **shutter button** (the circle with a camera in it) to take the picture. 6. Tap the **check mark** to accept the image, or tap the **arrow** to go back and retake the picture. *Note: You can attach up to two supporting images per log entry.* 7. Tap the **Save** button at the bottom of the screen once all information and images are entered. 8. Tap **OK** on the confirmation pop-up message to complete the process and return to the main menu. --- ## Best Practices and Considerations - **Provide detailed context:** **Always enter clear, descriptive notes in the text field.** Comprehensive notes make it significantly easier for administrators to understand the context of the inquiry when reviewing logs or linking them to complex incidents on the backend. - **Utilize image attachments:** **Attach relevant photos whenever applicable.** Visual evidence (such as a photo of a hazard, a damaged sign, or a specific vehicle) is highly valuable when a standard dispatch inquiry escalates into a formal incident or dispute.**Linking to Incidents** While the handheld device creates the initial Dispatch Log entry, the process of formally linking these logs to larger, ongoing "Incidents" is managed by administrators or dispatchers within the main OPSCOM web portal.
# Violations TabThe 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 legacy OPSCOM Parking Enforcement 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 OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration The Violations Tab automatically retrieves its historical ticket data directly from the central database. **Admin Side:** No specific configuration is required on the handheld device. Administrators manage all violation histories, payment statuses, and escalation policies within the core OPSCOM administrative portal. ## Using this Feature Enforcement personnel 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** button to open the extended vehicle record. 4. Tap the **Violations** tab (or swipe left/right across the screen to navigate to it). ### Key Information Displayed - **Violation Date:** The exact date the previous ticket was issued. - **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 - **Payment Status Text:** Each individual violation record features a clear, color-coded status indicator on the right side of the screen. - **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. --- ## Best Practices and Considerations - **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. - **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 this tab.**Legacy Application Notice** This article pertains specifically to the legacy OPSCOM Parking Enforcement app. If your organization has recently updated to the modern OPSCOM Enforce application, the interface, tab layout, and specific visual indicators will differ from what is described here.
# Chalks TabThe Chalks Tab is a dedicated 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 legacy OPSCOM 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 OPSCOM administrators and field enforcement personnel using the legacy Android application.
## 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 required on the handheld device to view this tab. Administrators manage global chalking grace periods and settings within the core OPSCOM administrative portal. ## Using this Feature Enforcement 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 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** button to open the extended vehicle record. 4. Tap the **Chalks** 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. --- ## Best Practices and Considerations - **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. - **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.**Legacy Application Notice** This article pertains specifically to the legacy OPSCOM Parking Enforcement app. If your organization has recently updated to the modern OPSCOM Enforce application, the interface, tab layout, and specific visual indicators will differ from what is described here.
# Violations and Chalking # Issuing a Person ViolationThe Issuing a Person Violation feature allows parking enforcement officers to write citations directly to individuals, rather than just to vehicles, using the legacy Android application. Its primary purpose is to enable enforcement actions for non-vehicular infractions or situations where a driver is explicitly known and present. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration In order to successfully issue violations to people, the system requires both backend categorization and local hardware preparation. **Admin Side:** Administrators must ensure that a specific ticket category is configured in the backend system that explicitly applies to users (person violations). **User Side (Enforcement Staff):** Before a physical ticket can be printed in the field, enforcement officers must ensure their Bluetooth printer is actively paired to their handheld device and correctly selected within the **System Settings** menu. ## Using this Feature Enforcement personnel can query the database for existing users, create new user profiles on the fly, and issue direct violations. ### Searching for a Person 1. Tap **Person Search** from the main menu of the OPSCOM Parking Enforcement app. 2. Enter the user's details into the **Name Search** field and tap **Search**. 3. Perform a wildcard search instead if you only have partial information, allowing you to search based on a phone number, student/staff ID, or driver's license. ### Creating a New User If a person is not already known in your system, you can quickly create a profile so the violation can be properly associated with an account. 1. Tap the **Create** button from the search interface. 2. Enter the individual's personal details manually into the provided fields. 3. Tap the **Failed to Identify** checkbox above the user details if the user refuses to supply their personal information, allowing you to continue issuing the violation anonymously. ### Issuing the Violation 1. Tap the person's name from the search results to open the Add Violation Record window. 2. Select the appropriate **Ticket Type** and **Offense Type**. 3. Tap the person tab to review the profile and correct any outdated information. 4. Tap **Save** to log the violation, or tap **Save & Print** to log the violation and immediately print the physical ticket. ### Visual Cues and Status Indicators - **People Alarms:** When searching for an existing user, any people alarms associated with that specific profile will prominently display on the screen, and a sound notification will trigger on your tablet. This allows officers to gather crucial details or warnings about a user before approaching them. ### Printed Ticket Details When you issue a person-only violation, the license plate field will automatically be excluded from the printed ticket. **Explanation of the Front of the Ticket/Warning:**| **Field** | **Description** |
| **Ticket Number** | A system-assigned number that identifies each individual violation or warning. |
| **Date** | The exact date the violation was issued. |
| **Ticket Type** | Identifies the broad category of the violation. |
| **License Plate** | The license plate number of the vehicle involved (if applicable). |
| **Province** | The issuing province or state for the license plate. |
| **Offense Type** | The specific infraction that occurred. |
| **Location** | The physical location where the violation took place. |
| **Writer** | A unique system-assigned identifier for the enforcement officer. This provides security for the officer in the field, while administrators can use it backend to verify the ticket writer's actual name. |
| **Fine** | The amount owed for the violation. \*(Note: On a warning ticket, the amount is followed by "*Warning", indicating it is not owed but shows what would be due if a real ticket was issued).* |
| **Towing** | The amount due if the vehicle that incurred the violation had to be towed. |
| **Comments** | Any additional notes the enforcement officer chose to include. |
The Issuing a Plate Violation feature allows parking enforcement officers to look up vehicle license plates and record parking infractions using the legacy Android application. Its primary purpose is to streamline the ticketing process by utilizing existing database records or easily capturing details for new, unknown vehicles. This guide is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration In order to issue violations effectively in the field, administrators must ensure the backend environment is fully configured, and users must prep their hardware. **Admin Side:** Administrators must ensure that all ticket types, offense locations, default fee amounts, and zone rules are properly configured within the main OPSCOM administrative portal. **User Side (Enforcement Staff):** Before starting a patrol, ensure your mobile device is fully charged, logged into the enforcement app, and actively paired with your Bluetooth printer (if issuing physical citations). ## Using this Feature Enforcement personnel can use this feature to issue citations to both known vehicles and vehicles that have never been entered into the system. ### Issuing Violations to Known Vehicles 1. Tap **Search Vehicles** from the main application menu. 2. Enter the plate number using OCR, voice command, or by typing on the keypad. 3. Review the search results list. A red **X** icon indicates the vehicle is currently in violation. 4. Tap the plate record that is in violation to open the **Add Violation Record** screen. 5. Tap **Select Offence Location** and choose the appropriate location from the drop-down menu. 6. Tap **Offence Type** and choose the specific infraction. You can tap the fee amount to manually override the default fee if necessary. 7. Tap **Towing Fee** and enter an amount if the vehicle requires towing. 8. Capture pictures of the vehicle and infraction for proof in case of a dispute. 9. Tap **Save & Print** to print the ticket and return to the search screen, or tap **Save** to log the violation without printing. ### Issuing Violations to New Vehicles If a scanned plate is unknown to the system, it will be indicated by a **+** icon in the search results. You must manually add the vehicle description to issue a citation. 1. Tap the plate record with the **+** icon. 2. Tap the vehicle description field and enter the vehicle's make, model, and color. 3. Complete the violation details (Offence Location, Offence Type, Towing Fee, and photos) as outlined in the steps above. 4. Tap **Save** or **Save & Print**. The new vehicle will automatically be added to the database the next time your handheld synchronizes.**VIN-Only Vehicles** If a violation is entered on a vehicle using only a VIN, the VIN will automatically appear on the printed ticket in the License Plate field.
### Filtering by Groups and Zones You can focus your plate searching and vetting by applying specific group and zone filters, which is particularly useful for virtual lots or reserved parking areas. 1. Tap **Any Parking Group** on the search screen and select a specific group (e.g., BLDG1). 2. Tap **Any Zone** and select the specific zone you are patrolling (e.g., Day Care). 3. Scan plates using the LPR/OCR functionality. A green check mark will explicitly indicate if a vehicle is permitted to park in that specified group and zone combination. ### Understanding the Printed Ticket **Explanation of the Front of the Ticket/Warning:**| **Field** | **Description** |
| **Ticket Number** | A system-assigned number that uniquely identifies each individual violation or warning. |
| **Date** | The date the violation or warning was issued. |
| **Ticket Type** | Identifies the broad category of the violation. |
| **License Plate** | The license plate number for the vehicle that incurred the violation. |
| **Province** | The province or state where the license plate was issued. |
| **Offense Type** | Identifies the specific parking violation that occurred. |
| **Location** | The physical location where the violation occurred. |
| **Writer** | A unique system-assigned identifier for the enforcement officer, providing security to the officer while allowing administrators to verify their identity in the backend. |
| **Fine** | The amount owed. \*(Note: On a warning ticket, the amount is followed by "*Warning", indicating the amount is not owed, but shows what would be due if a real ticket was issued).* |
| **Towing** | The amount due if the vehicle had to be towed. |
| **Comments** | Any additional notes included by the enforcement officer. |
The Displaying Towing Charges on a Violation feature allows organizations to print a default $0.00 towing fee on all physical parking tickets. Its primary purpose is to serve as a visible deterrent, reminding parkers that their vehicle could potentially be towed for infractions, even if a tow is not ordered for the current offense. This article is intended for OPS-COM administrators and field enforcement personnel configuring the legacy Android application.
## Setup and Configuration This setting is configured directly within the system settings of the individual handheld enforcement device. **Admin Side:** Administrators or supervisors must configure this setting on the physical devices used by the enforcement officers. 1. Tap **System Settings** from the main menu of the handheld application. 2. Scroll to locate the specific towing charge options. 3. Enable the **Show $0.00 Towing Charge** checkbox.**Default State** By default, this setting is disabled. If the checkbox remains disabled, the towing charge line item will be completely hidden on standard printed tickets unless a real fee is applied.
## Using this Feature Enforcement personnel do not need to perform any special actions to use this feature; it operates automatically when a physical violation is printed. ### Printing Tickets with the Notice 1. Issue a standard plate or person violation on the handheld device. 2. Tap **Save & Print** on the violation entry screen. 3. Review the printed ticket. The physical citation will now automatically include a "Towing" line item explicitly displaying a "$0.00" value. --- ## Best Practices and Considerations - **Understand actual towing charges:** **If a real towing charge is manually applied to the violation by the officer, the towing charge will always appear on the printed ticket regardless of whether this setting is enabled or disabled.** This toggle strictly controls the display of the $0.00 placeholder value. - **Align with institutional policy:** **Organizations should ensure that displaying a towing reminder aligns with their official parking and enforcement policies.** Displaying this warning is an effective deterrent, but it should be supported by actual lot signage and organizational towing rules to avoid confusing your parkers. # Virtual ChalkingThe Virtual Chalking (or e-chalking) feature in the legacy OPSCOM Android application is an electronic process that mirrors manually chalking a vehicle's tire to track parking durations. Its primary purpose is to provide enforcement officers with a time-efficient way to manage time-limited parking areas and grace periods, automatically generating time-stamped photographic evidence for potential violations. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration Virtual chalking is a native feature of the enforcement application. **Admin Side:** Administrators must ensure that parking lots with timed parking or permit grace periods are properly configured within the core OPSCOM administrative portal. **User Side (Enforcement Staff):** Enforcement officers must have the legacy OPSCOM Android app installed, be logged into an active account, and have granted the application permission to use the device's camera. ## Using this Feature Enforcement personnel can use the handheld application to record a vehicle's presence at a specific time. Note that vehicle plates are automatically chalked when initially searched via LPR, but officers can perform a manual chalk to add contextual information and specific images. ### Performing a Manual Virtual Chalk 1. Tap **Search Vehicle** to open the vehicle search window. 2. Enter a plate number and tap the **search** icon. 3. Tap and Hold the listed vehicle in the search results to access the advanced information screen. 4. Tap the **Virtual Chalk** button to access the chalking function. 5. Tap the **image** icon to open the camera and snap a picture of the vehicle. 6. Tap **Save** on the thumbnail view to record the chalking timestamp. ### Visual Cues and Status Indicators - **Elapsed Time Indicator:** If you search for the same vehicle again later, the screen will refresh and display red text indicating exactly how many minutes ago the vehicle was last chalked. - **Time and Date Stamp:** Tapping the information box on the advanced listing screen will display a full-frame view of the captured image, complete with a visible time and date stamp located at the bottom right corner of the image.**Court-Admissible Evidence** Virtual chalking provides photographic proof that is seamlessly attached to a violation. This evidence is generally acceptable in a court of law or formal appeal, provided the date and time stamp is clearly visible on the image. The chalked image remains a permanent part of the violation unless the patrol officer manually deletes it.
--- ## Best Practices and Considerations - **Capture contextual images for manual entries:** **If you enter a plate via text or voice when chalking, you must manually take a contextual image to record the time stamp.** The system only captures these automatically when using LPR/OCR camera mode (which automatically grabs both a close-up of the plate and a contextual full-back image). - **Take multiple images when issuing violations:** **When capturing the plate a second time to issue the actual violation, take multiple images.** Using both the timestamped chalk image and the time printed on the ticket allows you to definitively prove the time the vehicle was parked. There is no limit to the number of images you can attach. - **Leverage chalking for grace periods:** **Use virtual chalking to manage grace periods fairly.** For example, if a vehicle is parked and the owner is walking to a pay station to purchase a permit, chalking the vehicle allows a fair grace period for them to obtain it before a violation is issued on a subsequent patrol pass. # Printers & Printing # Choosing and Configuring PrintersThe Choosing and Configuring Printers configuration process allows enforcement officers to connect and properly format their mobile Bluetooth printers within the legacy OPSCOM Android application. Its primary purpose is to ensure the application communicates with the correct hardware drivers, allowing for clear and accurate physical ticket printing in the field. This article is intended for OPSCOM administrators and field enforcement personnel configuring their handheld devices.
## Setup and Configuration Before configuring the printer within the OPSCOM application, the physical printer must be powered on and actively paired to the Android device via the device's native OS Bluetooth settings. **Admin Side:** Administrators should ensure the organization's chosen Bluetooth printers (such as Star Micronics or Zebra models) are fully charged, loaded with paper, and paired to the assigned handheld device. **User Side (Enforcement Staff):** Enforcement officers must configure the application settings to recognize the paired printer and driver before issuing their first physical citation. ## Using this Feature Officers must explicitly select both the appropriate software driver and the specific hardware device within the application's system settings. ### Accessing System Settings 1. Tap **System Settings** from the main menu of the OPSCOM application. 2. Scroll through the menu to locate the specific printer settings options. ### Selecting the Driver and Printer 1. Tap **Bluetooth print driver** to select the proper driver for the hardware you are using. By default, the printer driver is set to Star Micronics. If you are using a Zebra printer, tap to select Zebra. Selecting the driver will automatically close the pop-up and return you to the main settings menu. 2. Tap **Bluetooth Printer** to open a list of paired Bluetooth devices. 3. Tap the name of the specific printer you are actively using to finalize the connection. --- ## Best Practices and Considerations - **Match your drivers to your hardware:** **It is critical that the selected driver matches your physical printer type.** If these two settings do not match, the printer will either fail to work entirely or it will begin to print out unreadable code and odd characters instead of a properly formatted violation. - **Verify functionality before patrolling:** **Always issue a test violation after configuration.** Printing a test ticket ensures the printer is connected, formatting correctly, and working exactly as expected before you step out into the field to begin enforcement. # Install Bluetooth PrinterThe Install Bluetooth Printer process ensures that your Android handheld device can communicate with your mobile printing hardware. Its primary purpose is to establish a successful Bluetooth connection at the operating system level, which is required before the OPSCOM application can print physical violation tickets. This article is intended for OPSCOM administrators and field enforcement personnel preparing their devices for field use.
## Setup and Configuration Connecting the hardware is the first step in the printing workflow. This process takes place entirely within the Android operating system settings and must be completed before configuring the printer within the OPSCOM software. **Admin Side:** Administrators should ensure the physical printer is fully charged, powered on, and set to discoverable mode. **User Side:** Before attempting to pair the device, users must verify two things: 1. Ensure the printer is properly set up and able to connect to the tablet. 2. Ensure the tablet has its internal Bluetooth receiver enabled.**Star Micronics Printers** If your organization is using a Star Micronics printer, please refer to the specific *[Changing Bluetooth Mode](https://opscom.wiki/books/legacy-android-enforcement-app-OPSCOM-parking-enforcement/page/changing-bluetooth-mode "Changing Bluetooth Mode")* documentation to ensure the hardware is transmitting the correct signal type before pairing.
## Using this Feature Enforcement personnel must pair the tablet and the printer directly through the Android device's native settings. ### Pairing the Printer 1. Tap **Bluetooth** within your Android device's main system settings to open the connection options. 2. Tap **Search for Devices** (or a similarly named scan button, depending on your Android version). 3. Wait for the scan to complete. Your printer will appear in the listing of available devices. 4. Tap the specific printer name in the list to initiate the pairing process between your printer and tablet. 5. Enter the printer PIN using the on-screen keyboard if the device prompts you for a security code. --- ## Best Practices and Considerations - **Remember the default PIN:** **If the system asks for a Printer PIN during the pairing process, the default Bluetooth PIN is usually 1234.** If this code is rejected, please consult your printer's official hardware manual for the correct code. - **Complete the setup in OPSCOM:** **Pairing the printer to the tablet is only the first step.** Once the operating system successfully sees and connects to the printer, you must log into the enforcement app and complete the *[Choosing and Configuring Printers](https://opscom.wiki/books/legacy-android-enforcement-app-OPSCOM-parking-enforcement/page/choosing-and-configuring-printers "Choosing and Configuring Printers")* setup so the software knows which driver to use. # SM-T300 PrinterThe SM-T300 is a mobile Bluetooth hardware printer used to issue physical citations from the legacy OPSCOM Android enforcement application. Its primary purpose is to print physical tickets in the field, and this guide outlines how to configure its core hardware connection and power-saving settings. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration Before the SM-T300 printer can successfully pair with your Android handheld and print tickets, you must ensure its internal hardware settings are configured to broadcast a standard Bluetooth signal and manage power efficiently. All setup is performed directly on the physical printer using its hardware buttons. ### Configure Bluetooth Mode To pair the printer with an Android device, the printer must be set to the standard Bluetooth mode, rather than UART or Bluetooth (iAP). 1. Hold down the **Feed** button and **Power** button simultaneously for approximately 6 seconds until the printer enters setup mode. 2. Press the **Power** button to cycle through the available connection modes. 3. Stop cycling when the screen displays **Bluetooth**. 4. Hold down the **Feed** button and **Power** button simultaneously for approximately 6 seconds to confirm and save your connection setting. ### Configure Power Down Settings To preserve battery life during patrols, you can configure the printer's timeout setting. It can be set to "no power down" or configured to power down automatically after 1 to 5 minutes of inactivity. 1. Turn the physical printer on. 2. Press and hold the **Power** button, then immediately press and hold the **Feed** button at the same time for approximately 5 seconds until the screen becomes backlit and enters Settings mode. 3. Press the **Feed** button to step through the settings menu until the screen displays **PWDN X min off** (where X represents the current timeout duration). 4. Press the **Power** button to cycle through the available timeout options. 5. Press the **Power** button and **Feed** button simultaneously once you have selected your desired wait time.**Configuration Confirmation** Once you save your power down settings by pressing both buttons, the SM-T300 will automatically print out a short paper summary of your current settings and return to standard standby mode.
--- ## Best Practices and Considerations - **Optimize your battery life:** **Always configure a power down timeout of 3 to 5 minutes to ensure the printer battery lasts through an entire enforcement shift.** Leaving the printer constantly powered on when not actively ticketing will drain the battery prematurely. - **Verify connection modes:** **If your Android tablet cannot discover the printer during the initial pairing process, verify that the printer is in standard Bluetooth mode.** If it is accidentally set to Bluetooth (iAP), which is generally reserved for iOS devices, standard Android tablets will struggle to connect. --- ### Supporting References For more advanced configuration or troubleshooting, administrators can refer to the official Star Micronics resources and SDK documentation below: - [https://play.google.com/store/apps/details?id=com.StarMicronics.StarIOSDK](https://play.google.com/store/apps/details?id=com.StarMicronics.StarIOSDK) # Reprint ViolationThe Reprint Violation feature allows enforcement officers to print a duplicate copy of a previously issued parking ticket directly from their handheld device. Its primary purpose is to quickly replace lost, damaged, or misprinted citations while officers remain active in the field. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration This feature is a native function of the enforcement application and does not require specialized backend configuration. However, it relies on properly configured external printer hardware. **Admin Side:** Administrators must ensure that field personnel are equipped with functioning mobile Bluetooth printers and that these devices are authorized within the OPSCOM system. **User Side (Enforcement Staff):** Enforcement officers must ensure their handheld device is actively paired and connected to their designated mobile printer before attempting to reprint a ticket. ## Using this Feature Field personnel can rapidly retrieve and reprint recent violation notices directly from the application's main menu. ### Reprinting Tickets 1. Tap **Reprint Violation** from the main menu of the legacy Android enforcement app. 2. Review the list of recently issued tickets displayed on the Reprint Violation Notice screen. 3. Tap the specific violation record that you want to reprint. 4. Follow the subsequent on-screen printer instructions to complete the physical printing process.**Check printer readiness** Before navigating to the reprint screen, always verify that your mobile printer is powered on, has sufficient battery life, and is loaded with ticket paper. This prevents application timeouts or connection errors during the print command.
--- ## Best Practices and Considerations - **Verify the correct ticket:** **Always double-check the ticket details on the screen before tapping to reprint.** Confirming the license plate and time of issue ensures you are leaving the correct duplicate citation on the offending vehicle. - **Address the root cause of misprints:** **If you find yourself frequently reprinting tickets due to faded ink, connection drops, or paper jams, report the hardware issue to your administrator.** Continuous reprinting wastes time and thermal paper resources in the field. # Zebra PrinterThe Zebra Printer configuration process allows enforcement officers to properly pair and format Zebra mobile Bluetooth printers for use with the legacy Android enforcement application. Its primary purpose is to ensure the Android device communicates correctly with the printer hardware and formats tickets accurately for a standard 3x7 receipt roll. This article is intended for OPSCOM administrators and field enforcement personnel configuring their handheld devices.
## Setup and Configuration Before configuring the printer within the OPSCOM application, the physical printer must be paired to the Android device, and its media settings must be configured using a specialized Zebra utility application. **Admin Side:** Administrators must ensure that field tablets are updated to at least Android Version 12 to successfully pair with Zebra printer models (e.g., ZQ520BT). **User Side (Enforcement Staff):** Enforcement officers must download the official [Zebra Printer Setup Utility](https://www.zebra.com/us/en/support-downloads/software/printer-software/printer-setup-utilities.html?downloadId=2c1cd23f-c1e5-4d08-92b0-1941416084ca) from the Google Play Store to configure the printer's specific media settings. ## Using this Feature Enforcement personnel must first pair the hardware via the Android operating system, then configure the print dimensions using the downloaded utility app. ### Pairing the Printer Tap **Connections** within the Android device settings, then tap **Bluetooth**. Tap the specific **printer name** (e.g., ZQ520BT) from the list of available devices to begin pairing. Verify the pairing code that appears on both the printer screen and the Android device. Tap the **check mark** button on the physical printer to confirm the code. Tap the confirmation message on the Android device to finalize the pairing. ### Setting up the Printer for Use - Open the installed Zebra Printer Setup Utility on your Android device. - Tap the **Media Settings** menu. Tap **Media Settings** again on the subsequent screen. - Enter **Receipt** for the format to begin setting up the 3x7 printer roll. Enter **3.1** for the width and **7.85** for the length. - Select **Inverted** for the orientation. - Tap **Next** to proceed to the next configuration screen. - Select **Continuous** for the Media Type. - Select **Direct Thermal** for the Type of Transfer. - Select **Rewind** for the Mobile Handling setting. Tap **Next**. - Tap **Apply** on the final screen to save your configuration to the printer. - Tap **Print Test Label** from the main Media Settings screen to verify that the print is centered and oriented properly. --- ## Best Practices and Considerations - **Verify your Android OS version:** **Ensure your tablet is running at least Android Version 12 before attempting to pair.** Older versions of the Android operating system may struggle to maintain a stable Bluetooth connection with modern Zebra hardware. - **Always print a test label:** **Do not skip the Print Test Label step within the utility app.** Confirming the physical alignment of the 3x7 formatting saves time in the field and prevents wasted receipt paper from misaligned citations. - **Complete the software setup:** **Remember to select the newly configured Zebra printer within the OPSCOM app.** Once this hardware configuration is complete, you must still log into the legacy enforcement app and select the Zebra driver under the internal system settings. --- ### Supporting References - [Zebra Tech Docs](http://techdocs.zebra.com/) - [Zebra Setup Utility Downloads](https://www.zebra.com/us/en/support-downloads/software/printer-software/printer-setup-utilities.html?downloadId=2c1cd23f-c1e5-4d08-92b0-1941416084ca) - [Zebra RW Series Manual](https://opscom.atlassian.net/wiki/download/attachments/755937/Zebra_RW_Series.pdf?version=1&modificationDate=1440410993000&cacheVersion=1&api=v2) - [ZSDK Demos Android](https://opscom.atlassian.net/wiki/download/attachments/755937/ZSDK_DemosAndroid.zip?version=1&modificationDate=1537362104000&cacheVersion=1&api=v2) # Ticket Printing (Legacy) - Zebra Printer Configuration (Android Only)The Legacy Zebra Printer Configuration Android process allows administrators and field officers to connect Zebra mobile printers to Android devices for use with the legacy OPSCOM Parking Enforcement application. Its primary purpose is to establish proper communication and printing settings, enabling the issuance of physical parking tickets directly from a mobile device. This article is intended for OPSCOM administrators and enforcement personnel setting up their handheld devices.
## Setup and Configuration This involves a one-time setup process to pair the mobile device with the printer hardware and configure the software to utilize the correct drivers. **Admin Side:** Administrators must install the application, pair the printer via Bluetooth, and configure the internal application settings.**Application Permissions** Every time a pop-up window appears asking for permissions (e.g., Microphone, Camera, Location access), you must choose **Always** or **While Using App**. If these permissions are denied, the application will not work properly.
### Application Installation 1. Power on your Zebra printer. 2. Navigate to the Google Play store on your Android device and install the OPSCOM Parking Enforcement app. *(Note: If you already have the application installed, uninstall and reinstall it to ensure a clean setup and prevent potential connection issues.)* ### Connect to Bluetooth 1. Open **System Settings** on your device and enable Bluetooth if it is not already active. 2. Tap **Scan** on the device, then tap and hold the **feed** button on the physical printer until the Bluetooth symbol appears. Release the button once it appears to put the printer into discoverable mode. 3. Tap your printer name (or printer serial number) from the list of available devices and tap **Pair**. 4. Compare the pairing code on the Android screen to the one printed by the printer, then tap **Pair** on the popup to confirm. ### Connect to the Enforcement App 1. Open the OPSCOM Parking Enforcement app and log in. 2. Tap the **Menu** icon (☰) in the top-left corner and tap **System Settings**. 3. Scroll down to the *Printer Settings* section. 4. Tap the **Printer Driver** drop-down menu and choose **Zebra**. 5. Tap **Saved Bluetooth Printer** to prompt the app to scan for nearby Bluetooth devices. 6. Tap your specific printer from the list of discovered devices. 7. Tap the **Save** button when prompted to save the printer. 8. Tap the **Menu** button, then tap **Home** to return to the main screen and start using the app. ## Using this Feature Once the setup is complete, the printer is fully integrated into the violation workflow and handles ticket generation automatically. ### Printing a Ticket 1. Issue a standard parking violation through the application. 2. Tap the on-screen prompt to print the ticket when the violation entry is complete. 3. Retrieve the successfully printed physical ticket from the Zebra printer.**Advanced Media Settings** Configuring specific printer hardware settings, such as media size, rewind handling, and orientation, can be done through the separate **Zebra Printer Setup Utility** found on the Google Play Store.
--- ## Best Practices and Considerations - **Perform a one-time setup per device pair:** **Remember that this configuration must be performed for each unique combination of a mobile device and a Zebra printer.** - **Maintain Bluetooth range:** **Ensure the mobile device remains within the effective Bluetooth range of the printer.** For a stable connection in the field, keep the devices within approximately 30 feet (10 meters) of each other. - **Troubleshoot connections efficiently:** **If you experience printing issues, always verify that the printer is powered on first.** If it is on and charged, re-selecting the printer from the **Saved Bluetooth Printer** menu within the application settings can often quickly re-establish a dropped connection. # Changing Bluetooth ModeThe Changing Bluetooth Mode process outlines how to correctly configure Star Micronics mobile printers to communicate with Android handheld devices. Its primary purpose is to resolve pairing issues caused by the printer being set to the iOS-specific Bluetooth (iAP) mode, ensuring seamless physical ticket printing in the field. This article is intended for OPS-COM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration This hardware configuration is performed directly on the physical Star Micronics printer using its hardware buttons. It does not require any backend adjustments within the OPS-COM administrative portal. **Admin Side:** Administrators deploying new printers should ensure they are configured to standard Bluetooth mode before issuing them to the field. **User Side (Enforcement Staff):** Enforcement officers experiencing pairing failures must manually adjust the internal printer settings using the physical buttons before attempting to connect the hardware to their Android device. ## Using this Feature Enforcement personnel must interact with the physical buttons on the printer's front panel to navigate its internal menus and adjust the operational connection mode. ### Adjusting the Printer Settings 1. Hold the **Power** button down for 3 seconds until the printer beeps to power it on. 2. Hold down both the **Power** button and **Feed** button simultaneously for approximately 5 seconds until the printer enters settings mode (indicated by a flashing LED), then release the buttons. 3. Press the **Power** button to change the currently displayed setting from Bluetooth (iAP) to Bluetooth Mode or Bluetooth (the exact naming varies by model, but ensure the *iAP* suffix is removed). 4. Hold down the **Power** button and **Feed** button simultaneously for another 5 seconds to exit and save your changes. ### Visual Cues and Status Indicators - **LED Indicator:** The correct, updated Bluetooth mode will be displayed directly on the LED indicator screen. - **Settings Receipt:** Once you save your changes and exit the configuration area, the device will automatically print a detailed paper list showing your new internal settings.**Button Functions in Settings Mode** While navigating the internal printer settings, pressing the **Power** button changes the currently displayed setting, while pressing the **Feed** button skips to the next available setting in the menu.
--- ## Best Practices and Considerations - **Avoid the iAP mode for Android devices:** **Never leave the printer in Bluetooth (iAP) mode if you are using an Android handheld.** Even if the Android OS appears to successfully pair with the printer in the device's native Bluetooth settings, the OPS-COM application will not be able to communicate with it or print tickets successfully. - **Confirm your configuration with a test print:** **Always follow the instructions in the Install Bluetooth Printer guide to pair your device and perform a test print after changing the mode.** This ensures the hardware is communicating correctly with the OperationsCommander Android application before you begin an active patrol. # System Settings # System SettingsThe System Settings area in the legacy OPSCOM Android application provides centralized control over the handheld's hardware integrations and local behaviors. Its primary purpose is to allow administrators and officers to configure mobile printers, adjust License Plate Recognition (LPR) camera inputs, and customize ticket formatting directly on the device. This article is intended for OPSCOM administrators and field enforcement personnel configuring their handheld units.
## Setup and Configuration While the handheld device offers extensive local customization, several foundational settings must be established in the core administrative portal first. **Admin Side:** Administrators must manage the core organization details, unique device identifiers, and the **Next Offence Number** through the OPSCOM web portal.**LPR Authorization** To successfully use the LPR features on a handheld unit, an administrator must first toggle the LPR functionality on within the System Settings of the main Admin Portal.
**User Side (Enforcement Staff):** Tap the main application menu icon, then tap **System Settings** to open the configuration interface on the mobile device. ## Using this Feature The system settings are divided into four main categories. Enforcement personnel can interact with these menus to tailor the application's performance. ### Local Device Settings This section displays read-only device information pulled directly from the admin portal, including the organization name, country of operation, and the device's unique identifier. ### Printer Settings Tap any item in this list to modify how the device communicates with mobile printers and formats physical tickets. - **Bluetooth print driver:** Tap to select the specific printer driver (e.g., Star Micronics). - **Bluetooth Printer:** Tap to select the physical paired printer hardware. - **Characters per line:** Tap to set the width limit of text on the ticket. - **Lines Before Ticket:** Tap to adjust the blank buffer space below the printed company logo. - **Lines per Ticket:** Tap to set a maximum length for the printed citation. - **Ticket Footer:** Displays the footer message (this is not editable locally and must be changed via the admin web tool in the *Handheld Common* area). - **Include Client Name:** Enable to print the client name if the organization's logo does not already include it. - **Include Dotted Header:** Enable to print a dotted line separator beneath the company logo. - **Include Warning Value:** Enable to display what the fine would be if a warning ticket were an actual violation. - **Include Discount Value:** Enable to show the early-payment discount amount. - **Include $0.00 Towing Charge:** Enable to display a placeholder towing cost on the ticket. - **Include Barcode:** Enable to print the specific violation number as a scannable barcode. ### LPR Settings Tap these options to configure camera connections and virtual chalking rules. - **LPR Proxy IP Address:** Tap to enter the IP address. The default IP is 192.18.8.1, which is used to connect to a PL8RDR. - **LPR Proxy Port:** Tap to enter the proxy port number. The default is 32000. - **Include NOREAD Results:** Tap to set the acceptable read score percentage. Setting the level to greater than 50% ensures the system only includes reads with a 50% or greater confidence score. - **Auto Chalk Vehicles:** Enable to automatically chalk vehicles in the background while reading plates. - **Trigger on Inactive Vehicle:** Enable to trigger an alarm when scanning a vehicle marked as inactive in the system. - **Time until chalked vehicle in violation:** Tap to set the grace period duration before a chalked vehicle is officially flagged for a violation. - **Chalk Units:** Enable to display virtual chalking distances in meters. ### Advanced Settings Tap these options to adjust backend synchronization and interface behaviors. - **Next Offence Number:** A read-only display of the next sequential ticket number assigned to this device by the admin portal. - **Show Hyphen in Ticket:** Enable to insert a hyphen between the device ID and the ticket number. - **Auto Synchronization Frequency:** Tap to select how often the handheld automatically pushes and pulls data from the main database. - **Temp Permit Barcodes:** Enable the temporary parking barcode scanning function. - **System Debugging:** Enable to put the device into debug mode for testing and support diagnostics. - **Reset Settings:** Tap to re-sync all settings with the core OPSCOM server, returning the handheld to its default state. - **Preference settings:** Enable to hide multi-menus for chalking and evidence photos, streamlining the user interface. --- ## Best Practices and Considerations - **Match printer drivers to hardware:** **Always ensure the Bluetooth print driver matches the exact Bluetooth Printer selected.** If these two settings do not align, the printer will fail to connect or will print unreadable code instead of a formatted ticket. - **Leverage Auto Synchronization cautiously:** **Carefully consider your Auto Synchronization Frequency based on your field network reliability.** Setting the sync frequency too high in areas with poor cellular reception can drain the device battery as it repeatedly attempts to connect to the database. # Setting Device to Auto-UpdateThe Setting Device to Auto-Update process allows organizations to configure their Android handheld devices to automatically download and install application updates. Its primary purpose is to ensure that the legacy OPSCOM Parking Enforcement app, along with other critical device software, remains on the latest version without requiring manual intervention from field staff. This article is intended for OPSCOM administrators and IT personnel responsible for provisioning enforcement devices.
## Setup and Configuration This configuration is performed directly within the native Google Play Store on the Android operating system. It does not require any backend adjustments within the OPSCOM administrative portal. **Admin Side:** Administrators configuring the field devices prior to deployment should ensure the device is connected to a stable network and logged into an active Google account to access the Play Store settings. **User Side (Enforcement Staff):** Generally, field officers do not need to configure this setting if the device was pre-provisioned by administration. If manual configuration is required in the field, follow the steps below. ## Using this Feature Administrators interact with the native Google Play Store settings to dictate how the device handles application updates. ### Configuring Auto-Update Settings 1. Open the **Google Play Store** application on the handheld device. 2. Tap the **Menu** icon (represented by three horizontal lines) located in the top-left corner of the screen. 3. Tap **Settings** from the slide-out menu. 4. Tap **Auto-update apps** to open the configuration prompt. 5. Select **Auto-update apps at any time** to enable automatic updates, or select **Do not auto-update apps** to strictly disable the automatic updating process.**Data Charges and Connectivity** When selecting the option to update apps at any time, be aware that the device will utilize whatever network connection is currently active. If the device is not on Wi-Fi, cellular data charges may apply based on your organization's mobile carrier plan.
--- ## Best Practices and Considerations - **Maintain up-to-date software:** **Organizations should establish a business rule to keep auto-updates enabled whenever possible.** Allowing the device to update automatically ensures field officers always benefit from the latest bug fixes, security patches, and feature enhancements for the OPSCOM application. - **Monitor cellular data usage:** **If your organization uses strict or limited cellular data plans, consider using the Wi-Fi only update option if available on your device's Android version.** This prevents large app updates from exhausting your monthly cellular data allowance while officers are actively patrolling. # Reset Settings for OPSCOM Parking EnforcementThe Reset Settings feature within the legacy Android application allows users to clear local device configurations and force the handheld to pull fresh data from the server. Its primary purpose is to troubleshoot and resolve synchronization or configuration issues on the mobile device. This article is intended for OPSCOM administrators and field enforcement personnel acting under the guidance of support staff.
## Setup and Configuration This troubleshooting feature is natively built into the application and does not require any backend configuration to activate. **Admin Side:** Before initiating a reset, ensure the handheld device is connected to a stable Wi-Fi or cellular network, as the application will need to download a fresh batch of data upon the next login. ## Using this Feature Enforcement personnel should only use this feature when experiencing specific device issues and only under direction from the support team. ### Resetting the Application Settings 1. Log in to the OPSCOM Parking Enforcement app. 2. Tap **System Settings** from the main menu. 3. Scroll down to the bottom of the settings list and tap the **Reset Settings** checkbox to select it. 4. Tap the device's back button and log out of the application completely. 5. Fully close the application from the Android recent apps menu. 6. Restart the tablet or handheld device. 7. Log in to the OPSCOM Parking Enforcement app. The system will automatically re-download all system settings and related data during this initial login. --- ## Best Practices and Considerations - **Ensure a stable network connection:** **Always verify your device has a strong cellular or Wi-Fi signal before logging back in.** Because the reset clears local data, a stable connection is required to successfully pull the fresh settings from the database and resume normal operations.**Authorized Use Only** **Do not perform a settings reset as a standard troubleshooting step.** The reset settings function should only be performed if you have been explicitly told to do so by an [OPS-COM Support](https://support.ops-com.com/) representative.
# OPSCOM Parking Enforcement Admin System SettingsThe OPSCOM Parking Enforcement Admin System Settings feature allows administrators to configure core global variables that synchronize directly to the mobile enforcement handhelds. Its primary purpose is to ensure all printed tickets and app interfaces consistently display the correct organizational details, locations, and legal footers. This article is intended for OPS-COM administrators.
## Setup and Configuration These foundational settings must be configured within the core administrative portal before the handheld units can be properly deployed to the field. **Admin Side:** Hover over **System Configuration** and click **System Settings** to access the main configuration portal. **User Side (Enforcement Staff):** No configuration is required on the handheld device to receive these settings. The mobile enforcement units will automatically download these core variables during their next routine synchronization with the server. ## Using this Feature Administrators can use this interface to update the organization's core identity details and customize the legal text that prints at the bottom of physical citations. ### Setting the Organization Name and Country 1. Click **General System Settings** from the list of components on the left side of the screen. 2. Type your organization's official title into the **Organization Name** field. 3. Type your location into the **Country** field. 4. Click **Save Settings** to apply the changes to the database. ### Editing the Handheld Footer 1. Click **Violations** from the list of components on the left side of the screen. 2. Locate the **Handheld Footer** field in the top portion of the configuration form. 3. Type the exact legal or instructional text you want printed at the bottom of all physical parking tickets. 4. Toggle the appearance of the **pin numbers** on the violation in this same area, depending on your organization's payment portal requirements. 5. Click to save your configuration changes.**Example Footer Message** A standard and effective ticket footer message should look something like this: *This parking ticket is due within 14 days. Failure to settle this parking ticket will result in the account becoming delinquent and subject your vehicle to collections and/or towing.*
--- ## Best Practices and Considerations - **Configure across proper environments:** **Administrators must be aware that settings pushed to a specific site environment (preview or production) do not automatically sync to the other.** If you configure a handheld device while connected to the production site, it will not be configured for the preview site, and vice versa. - **Follow the recommended device setup sequence:** **Always add and configure the handheld device through the preview environment first, and then set it up on the production environment.** This specific deployment sequence ensures that the device settings are properly written to the *PA\_Common* tables for both environments simultaneously, preventing future synchronization conflicts. # CategoriesThe Incident Categories feature allows organizations to classify and organize different types of incidents, such as security events, parking violations, or maintenance requests. Its primary purpose is to help administrators standardize reporting and dispatching by defining a structured hierarchy of categories and sub-categories. This article is intended for OPSCOM administrators.
## Setup and Configuration This feature is managed entirely within the core OPSCOM administrative portal. No configuration is required on the mobile handheld devices, as they will automatically inherit the category lists during their regular synchronization. **Admin Side:** Hover over **Admin Options**, click **Incidents**, and then click **Categories**. This will open the **Edit Categories and Sub Categories** main page. ## Using this Feature Administrators can use this interface to build a custom list of incident types, create granular sub-categories, and define operational rules such as checklist requirements. ### Adding a New Category 1. Scroll to the bottom of the **Edit Categories and Sub Categories** main page. 2. Click **Add New Category**. 3. Enter a descriptive name in the **Category Name** text field. 4. Enable the **In-House** checkbox if this incident type is handled strictly internally. 5. Enter a **GIS** number if applicable for spatial tracking and mapping integration. 6. Enable the option to include this category in system reports, if desired. 7. Click **Save Incident Category** to finalize and add the new category to the system. ### Editing an Existing Category 1. Locate the specific category in the listed items on the main page. 2. Click the **pencil** icon next to the category to open the edit screen. 3. Update the category name or specific configuration details as needed. 4. Click **Save Incident Category** to apply your changes to the database. ### Managing Sub-Categories Sub-categories allow you to break down broad incidents into highly specific events. 1. Click **Sub** next to an existing category on the main list to view its associated sub-categories. 2. Enter a new name in the provided text field to add a new sub-category. 3. Click **Required** under the checklist column if a formal checklist must be completed by the officer when this specific sub-category is selected in the field. 4. Click **Include** if you want this specific sub-category to be visible in statistical reports. 5. Click **Save SubCategory** to add the new sub-category to the parent group. --- ## Best Practices and Considerations - **Standardize your naming conventions:** **Organizations should establish a clear and consistent naming convention for all categories and sub-categories.** This prevents duplicate entries and ensures dispatchers and field officers can quickly select the correct option during an active, high-stress incident. - **Utilize checklists for complex incidents:** **Enable the checklist requirement for sub-categories that involve multi-step procedures or critical safety protocols.** This ensures field officers follow standard operating procedures when responding to specific incident types, reducing organizational liability. # Best Practices # Best PracticesThe Best Practices guide outlines the recommended daily maintenance routines for field enforcement handhelds. Its primary purpose is to ensure devices remain connected, up-to-date, and synchronized with the core database for optimal performance in the field. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration Maintaining the handheld devices requires minimal backend configuration, but relies on consistent network availability. **Admin Side:** Administrators should ensure devices are properly provisioned with Google Play Store access so they can receive regular application updates. **User Side (Enforcement Staff):** Enforcement officers must ensure their device has an active internet connection (Wi-Fi or cellular data) to successfully download updates and synchronize enforcement data. ## Using this Feature Enforcement personnel should regularly interact with the device's update and synchronization features to maintain system health. ### Updating the Application 1. Open the Google Play store on your handheld device and search for "OPSCOM". 2. Tap the red and black OPSCOM application icon. 3. Tap the **Update** button if there is a new version available. *(Note: Prior to updating, be sure to fully close the running OPSCOM application first).* ### Synchronizing Data 1. Ensure the tablet is in an area with a stable internet connection. 2. Tap the **Synchronize Data** option from the main menu to force the tablet to sync all local data with the main database immediately. ### Visual Cues and Status Indicators When patrolling, monitor the top left panel of the Search pages to verify your **Database Connection State**: - **Green Dot:** Indicates a healthy, active connection to the live database systems. - **Orange Dot:** Indicates that the system has lost its live connection but is currently operating on cached data. The system is still fully usable, but if the orange dot remains for an extended period, it is best to restart the application to reset the network connections. --- ## Best Practices and Considerations - **Reset handheld units daily:** **It is good practice to reset all handheld units before each shift.** Resetting the unit refreshes network connections and allows any pending auto-updates to be installed. If the app is left running indefinitely, the system cannot auto-update and you will miss out on recent changes. - **Kill background applications entirely:** **Make sure to completely shut down the app, rather than simply minimizing or switching away from it at the end of your shift.** To swipe the app out of memory, access the Recent Apps screen. - **Clear the application cache for persistent issues:** **If connection or performance issues persist even after resetting the app, try refreshing the app's cache.****Check your version frequently** It is important to always be running the latest version of OPSCOM Parking Enforcement. Regularly checking the Play Store for updates prevents unexpected bugs and ensures you have access to the latest field features.
# How weak Wi-Fi can affect OPSCOMThe How weak Wi-Fi can affect OPSCOM guide outlines how network connectivity impacts the legacy Android enforcement application. Its primary purpose is to help administrators and field officers troubleshoot Wi-Fi issues, understand how data synchronizes, and ensure offline records are properly uploaded to the main server. This article is intended for OPSCOM administrators and field enforcement personnel.
## Setup and Configuration Data synchronization occurs natively within the application, but administrators can customize how frequently the device attempts to auto-sync when idle. **Admin Side:** Administrators or supervisors can adjust the idle Auto-Sync time interval (or disable it entirely) by accessing the **System Settings** menu on the handheld device. **User Side (Enforcement Staff):** Officers must ensure the device's Wi-Fi receiver is turned on and connected to a reliable network when starting a shift, or when returning to a dispatch area to upload offline data. ## Using this Feature Enforcement personnel do not need a constant connection to issue violations, but they must interact with the application's synchronization tools to push that data to the main database. ### Testing Connectivity in the Field If you suspect you have lost your Wi-Fi connection while on patrol: 1. Open the native web browser on your tablet device. 2. Attempt to load any standard public web page. If the browser cannot connect to the website, the device does not have sufficient signal strength to connect with the OPSCOM server. ### Manually Synchronizing Data When you return to an area with known Wi-Fi coverage (like the main office or a connected vehicle), you can manually push your offline data. 1. Tap **Synchronize Data** from the main menu of the OPSCOM application. The synchronization process will begin immediately. ### Understanding Auto-Sync The application is designed to automatically sync in three specific instances to protect your data: - **Startup:** A sync is performed automatically when the app is launched, provided you have connectivity. *(Note: If you have poor connectivity upon startup, the app will display an error and will not allow you to log in).* - **Logout:** The unit will run a final auto-sync when you use the formal logout button. - **Idle:** The unit will auto-sync when the device has been completely idle for the duration specified in the system settings.**Idle Timer Behavior** The idle Auto-Sync is a precaution to ensure syncing happens when an officer has not manually synced in a while. If your idle setting is 15 minutes, the unit must remain completely untouched for 15 minutes. If the tablet is used for any task during that time, the 15-minute timer restarts.
### Visual Cues and Status Indicators - **Data Available Warning:** When offline data is waiting to be uploaded, a red flashing message will appear at the top of the screen indicating *"Data available to sync:"* followed by the number of violations and vehicles stored locally. - **Sync Successful:** Once a proper sync has occurred and all data is transferred to the main server, the red data available warning will disappear from the screen. --- ## Best Practices and Considerations - **Understand environmental signal interference:** **Be aware that structural objects, concrete, brick, and load-bearing walls severely affect signal strength.** Keep this in mind if patrolling interiors such as parking garages or underground levels, as you will likely lose connection and need to sync later. - **Perform an end-of-shift sync:** **Always return to the main menu and allow a sync, or force a manual sync, before logging out for the day at the end of your shift.** This guarantees all field data is securely uploaded. - **Log out properly:** **Do not simply put the app in the background, close it from the recent apps menu, or power off the unit while it is running.** You must log out of the application properly using the interface to trigger the final logout auto-sync. - **Consider electrical interference:** **Be aware that devices operating on the 2.4GHz frequency (such as certain appliances and older electronics) can interfere with Wi-Fi signals.** While not the most common cause of complete signal loss, it is worth considering if you repeatedly fail to sync in a specific indoor location.**Don't Panic!** If you cannot sync immediately due to a dead zone, it is not a critical issue. The OPSCOM app is designed to store your work locally. As long as you perform a manual sync when you return to an area with better connectivity, your data is safe.
# Working in Low and Bright LightThe Working in Low and Bright Light guide outlines how to manage device screen brightness and optimize camera settings for nighttime patrols. Its primary purpose is to ensure field officers can operate their handheld units comfortably without eye strain and capture clear violation photos regardless of ambient lighting conditions. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration Managing light settings is performed directly on the mobile device operating system and native camera application. It does not require any backend adjustments within the OPSCOM administrative portal. **Admin Side:** Enforcement officers must familiarize themselves with their specific Android device's quick settings shade and native camera application preferences to make on-the-fly adjustments during their shift. ## Using this Feature Field personnel can quickly adjust their screen brightness for viewing comfort and modify camera settings to ensure optimal photo evidence collection in low-light environments. ### Adjusting Screen Brightness 1. Swipe down from the top edge of the Android device screen to reveal the quick settings menu. 2. Drag the brightness slider left to manually dim the screen for low-light conditions, or right to increase brightness for daylight visibility. 3. Tap the **Auto** checkbox (or equivalent auto-brightness toggle) to allow the device to dynamically adjust the screen brightness based on available ambient light. ### Taking Photos at Night To capture the highest quality photo evidence when working with the camera flash in low-light situations, adjust the native Android camera settings: 1. Open your device's native camera settings menu. 2. Select **Matrix** for the metering option (rather than a centered reading). 3. Set the flash option to **Always On**. 4. Enable the **Low Light Detection** option if your device supports it.**Brightness Overrides** Depending on the manufacturer, some Android handheld units feature a specialized brightness override within the camera settings. Enabling this can significantly improve image processing, yielding much better evidentiary photos during night patrols.
--- ## Best Practices and Considerations - **Utilize auto-brightness:** **Enable auto-brightness to preserve battery life.** Manually leaving the screen at maximum brightness during a full shift will rapidly drain the device battery. Allowing the system to manage brightness automatically ensures optimal visibility while conserving power. - **Test your camera configurations:** **Always take a few test photos in your patrol environment after modifying camera settings.** Because native camera applications vary heavily between different Android tablet manufacturers, taking test shots ensures your matrix metering and flash settings are producing clear, legible license plate captures before you begin issuing active violations. # OPSCOM on the WebThe OPSCOM on the Web feature provides a convenient shortcut from the mobile application directly to the main administrative web portal. Its primary purpose is to allow administrators and field staff to seamlessly transition from the mobile app to a full web browser to access backend tools and manage tasks. This article is intended for OPSCOM administrators and field enforcement personnel using the legacy Android application.
## Setup and Configuration This feature utilizes the device's default web browser and requires no specialized backend configuration within the OPSCOM portal. **User Side (Enforcement Staff):** No manual setup is required within the application. However, the handheld device must have an active internet connection and at least one standard web browser app (such as Google Chrome) installed to load the page properly. ## Using this Feature Enforcement personnel can use this shortcut to quickly jump from their active mobile session to the full OPSCOM login page. ### Accessing the Web Portal 1. Tap **OPSCOM on the Web** from the main menu of the mobile application. 2. Tap your preferred web browser (e.g., **Chrome**) from the pop-up list when prompted by the Android operating system to choose an application. 3. Tap **Just Once** or **Always** to confirm your browser selection and execute the launch. 4. Log in to the standard OPSCOM web portal using your credentials once the browser redirects you to the login page. --- ## Best Practices and Considerations - **Select a default browser:** **Tap Always when selecting your preferred web browser to streamline future access.** Setting a default browser skips the OS prompt, allowing the login page to launch immediately during subsequent uses. - **Maintain active connectivity:** **Ensure your device is connected to a reliable network before attempting to use this shortcut.** Because this feature redirects you to a live, external web page, it will not function if the device is currently in a dead zone or operating offline.**Network Requirements** In order for this feature to work properly, the tablet must be in an area in which it is connected to the internet via Wi-Fi or cellular data. If the device is offline, the browser will open but display a connection error.