Skip to main content

First Time Installation - Enforce

The First Time Installation 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 OPS-COM 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 your device.

Admin Side: 

  1. Tap the Google Play Store app on the device's main screen to open it.

  2. Tap the search bar and type OPSCOM Enforce or OPSCOM.

  3. Tap the OPSCOM Enforce 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 OPS-COM 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.

Back to top