OPSCOM Parking Enforcement Admin System Settings

Administrator

The 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

ThereThese arefoundational settings that will need tomust be populatedconfigured inwithin orderthe tocore haveadministrative portal before the handheld units workcan withbe commonproperly core settings.

There settings include:

• Organization Name
• Country
• Ticket footer

Setting the Organization Name and Country

To access the settings godeployed to the field.

Admin Side: Hover over System Configuration and click on System Settings.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

OnceAdministrators incan systemuse settingsthis clickinterface onto 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 infrom the list of components.components on the left side of the screen.

   

2. EditType your organization's official title into the  Organization Name andfield.

3. Type your location into the Country Countryfield.

4. Click Save Settings to reflectapply yourthe specific location.

   Click Save Settingschanges to proceed.the database.

   

Editing the Handheld Footer

(Footer

printed on the actual ticket.)

1. Click on Violations infrom the list of Components.components on the left side of the screen.

   

2. InLocate the Handheld Footer field in the top portion of the formconfiguration form.

3. Type the exact legal or instructional text you willwant seeprinted aat fieldthe labeledbottom of all physical parking tickets.

4. Toggle the appearance of the Handheldpin Footernumbers. Editon the violation in this fieldsame area, depending on your organization's payment portal requirements.

5. Click to displaysave whatyour youconfiguration wouldchanges.

   like
printed

in

Example theFooter Message A standard and effective ticket footer area.

The 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.

You can also toggle the appearance of the pin numbers on the violation in this area as well.

---

HandheldBest SettingsPractices and Considerations

• TheConfigure settingsacross proper environments: Administrators must be aware that you setup for your device aresettings pushed to thea specific site environment (preview or productionproduction) sitedo not automatically sync to the other. If you usedconfigure a handheld device while connected to setup.the Thisproduction means that if you setup your device on production,site, it will not be configured for the preview site, and ifvice youversa.

• Follow the recommended device setup yoursequence: Always add and configure the handheld device onthrough the preview environment first, and then set it willup noton bethe configuredproduction forenvironment. production.This Thespecific properdeployment methodsequence forensures adding devices would be to first addthat the device throughsettings preview.are Andproperly thenwritten setup your device on production which will addto the settingsPA_Common totables for both theenvironments productionsimultaneously, andpreventing previewfuture PA_Commonsynchronization tables.conflicts.