Skip to main content

Handhelds Devices Settings (Handheld Commons)

Navigate

The Handhelds Devices section in OPS-COM allows administrators to manage and configure handheld devices used for enforcement and data collection. This includes registering new devices, pushing messages, and updating device settings, ensuring seamless operation for field personnel and accurate data synchronization.

Using this Feature

  1. Click Tools, Handhelds Devices.

    SelectAlternatively, you can access this on the Violations Systemmenu Configurationas →well.

    2. Violations
  2. The → Handhelds Devices.

    image.png



    The Handhelds - Common Settings screen appearsappears, where you can editmanage thevarious numberaspects of daysyour beforehandheld afleet. From here, you can edit settings such as ticket isdue due,dates, customize the ticket footer,footers, view device information, and add or manage handhelds.individual
    handheld units.

image.png

Adding Aa New Device

When adding a new handheld device, the process involves both the device startitself and the OPS-COM system configuration.

  1. Install Software: Start by installing the OPS-COM for Android software.software on the handheld device.
  2. Obtain UUID: After the first login youattempt willon getthe device, you'll receive a notice thatindicating the device isisn't notregistered. registered and theThis message will give youdisplay a UUID number(Universally toUnique beIdentifier) used.number. It'sThis is a 16 16-digit alphanumeric code thattypically appearsfound under your login screen.screen Useon thatthe UUIDdevice.
    3. to
  3. Register configureDevice yourin HandheldOPS-COM:
    • Once on the Handhelds - Common registrationSettings process.


      Oncepage in Handheldthe Commonadmin portal, click on Add New Device.

    • A new screen will openopen. up where youYou must add:

      add the following information:
      • The UUID: (Where isEnter the UUID?UUID obtained Firstfrom Timethe Installationhandheld - Android)device.
      • Set a Server to Sync with: (alwaysAlways start withby selecting the Production Server)Server. This is a critical step for initial device registration, regardless of whether the device will eventually be used for testing on a Preview server (explained further in "Important Note - Additional Information").
      • AName: Enter a descriptive name you'd like to use toeasily identify this device by.(e.g., "Patrol Unit 1," "Enforcement Officer John's Device").
    • Ensure

      Alsothe importantEnabled is to ensure Enabled is selectedcheckbox at the top of the entry form.
      Onceform youis haveselected.

      • this
    information
    4. in place click on
  4. Click Add Device

    image.png

    once

    all information is in place.

Pushing Messages 

You can also pushsend messages outdirectly to your configured handheld units.units:

Click
  1. On the 'Handhelds - Common Settings screen, click the Push Message' buttonbutton.
  2. Follow the prompts to compose and followsend your message to the prompts.selected

    devices.

    3. image.png



image.png

Updating Device Data

ClickTo modify settings for an existing handheld device:

  1. On the Handhelds - Common Settings screen, click on the device name you wish to updateupdate. toThis getwill open a drop-down list of editable settings.
  2. Make your desired changes to the settingsdevice's configuration.
  3. Once finished, ensure you can change. 

    image.png

    Make sure you selectclick Process UpdatesUpdates whento yousave areand finished.apply

    your


    changes

    to the device.

Best Practices & Considerations

  • Production Server First (Crucial):
    • Important Note: -Due Additionalto Information

      the

      Byunderlying virtuelogic of how the Handheld Common tooltool, functions.you It'smust always part of the process to start setting upregister a new handheld unit on the productionProduction sideadmin regardlessportal offirst, whethereven itif its ultimate purpose is tofor betesting used in Production or ason a testPreview unitsite.

      • on Preview.

      For initial handheld connection, the
    • The system alwaysinitially connects to the production first,server, then looks atreferences the PA Common/handheld assignment table where(which theis unitswritten arefrom production) to determine if a unit is registered to then know if they are registered onfor Production or Preview. That'sThis ensures the logiccorrect path so itrouting is importantestablished to always writein the tablesdatabase.
      • from
    • This productioninitial production-side first. 

      Additionally, thisregistration is also why weyou can refresh preview sites without loosinglosing the Handheldhandheld units that are configured tofor specificthem.

      • preview
    sites.

  • Adding a Handheld Unit to Preview for Testing

    • :

    To

    1. First, add athe handheld unit to previewHandhelds you- mustCommon first add it to handheld commonSettings on the production admin portal.portal Youas would fill everythingdescribed in as"Adding normala New Device," but select theyour previewPreview serverServer asin the entryServer into Sync Withwith.

      field. This will setsets the proper routedatabase forroute.

      2. the
    2. Next, handheld unit in the database. You will then need to gonavigate to the preview serveradmin portal and enter the exact same device information into theits previewHandhelds site.
      Then- Common Settings       section.
    3. Finally, perform a reinstallreinstallation of the software.OPS-COM for Android software on the handheld device itself. This willreinstallation allowallows the handheld to pick up the newnewly set path to the preview thatserver.
      4. you
    have set.

  • Switching Between Production and Preview:
    • Once thea handheld entry isexists in both Production (configured for Preview sync) and PreviewPreview, you can generally switch backbetween andenvironments forthby fairly easily. You repointre-pointing the syncSync withWith setting to the preferred path on both the Production and Preview.
      YouPreview haveadmin portals to doyour preferred path.
    • However, remember that you must perform a reinstallreinstallation of the software on the handheld unit each time you change the synchronization path in orderthe system for the handheld unitdevice itself to be updatedupdate with the selected path.
  • UUID Accuracy: Ensure the UUID is entered precisely, as any error will prevent the device from connecting.
  • Descriptive Naming: Use clear, identifiable names for your handheld devices to simplify management and troubleshooting.



Back to top