Skip to main content

Managing Lot Zones

The Managing Lot Zones feature allows administrators to define specific geographical or logical areas within a single parking lot. Its primary purpose is to provide granular control over pricing variations, access rules, and enforcement strategies tailored to different sections of a larger lot. This article is intended for OPS-COM administrators responsible for configuring parking environments and lot infrastructure.

Setup and Configuration

This feature is a core administrative tool used to structure parking locations within the system.

Admin Side: Administrators must have the appropriate system role permissions enabled to access the parking configuration menus and manage lot zones.

User Side: End-users do not directly interact with lot zone backend configurations. However, the pricing and access rules applied to these zones dictate where users are permitted to park and how much they are charged.

Using this Feature

Administrators can use the following instructions to navigate the management interface to seamlessly add, edit, or delete lot zones.

Accessing the Management Interface

  1. Hover over System Configuration, click Parking, then Manage Lot Zones.

Adding Lot Zones

  1. Click the Add Lot Zone button.

  2. Enter the full, descriptive name of the zone into the Name field (e.g., Day Care Center).

  3. Enter a shortened identifier into the Short Name field. This is typically used for optimized display on handheld enforcement devices (e.g., DAY).

  4. Click the Save Changes button to add the new zone to the list.

Editing Lot Zones

  1. Locate the specific lot zone you wish to modify in the list.

  2. Click the Edit button next to the entry.

  3. Enter the desired changes into the name fields.

  4. Click the Save Changes button to apply your updates.

Deleting Lot Zones

  1. Locate the specific lot zone you wish to remove from the list.

  2. Click the Delete button next to the entry.

  3. Click the Delete button in the confirmation window to permanently remove it from the system.

A lot zone can only be deleted if no records are currently associated with it. Administrators must first ensure that the zone is not actively in use or linked to any specific parking spaces, permits, or lot configurations before it can be removed.

Best Practices and Considerations

  • Implement granular control: Use lot zones to apply different rules, prices, or restrictions to sub-sections within a single large parking lot. This prevents the need to create entirely separate lots in the system when they physically share the same location.

  • Use clear naming conventions: Use descriptive names for your lot zones that clearly indicate their specific purpose or physical location. Utilizing clear names like "North End Hourly" or "Permit Holder Zone A" drastically reduces confusion for enforcement staff.

  • Ensure data integrity before deletion: Always ensure that a lot zone is not actively referenced by any other part of the system before attempting to delete it. Attempting to force the deletion of linked zones can cause data conflicts with existing spaces or user permits.

  • Integrate with mapping features: If your system includes mapping features, ensure your defined lot zones can be visually represented. Clearly drawn and labeled zones on a digital map improve clarity for both administrators managing the system and users navigating the physical lot.

Back to top