The parking rules that define how and when a vehicle can be parked can vary greatly from one parking zone to another. The parking rules that you configure can be assigned to one or more parking zones.
If you want to incorporate third-party license plate enabled parking (LEP) payment systems, you must install the Pay-by-Plate Sync plugin on all servers and client workstations that must use the plugin. For more information, see the Pay-by-Plate Sync Plugin Guide.
Before you begin
The following parking scenarios are supported:
What you should know
- Overtime parking (for example, free parking for a maximum of 2 hours).
- Transient parking using Pay-by-Plate Sync enabled payment providers.
- Contract parking using Pay-by-Plate Sync permits.
- From the Config Tool home page, open the ALPR task and click Parking rules.
- Click Parking rule ().
- In the Identity tab, rename your parking rule and add a Description and Logical ID (optional).
- You can define Relationships to link parking zones and actions to your parking rule.
In the Properties tab, configure the following:
- Convenience time
- The convenience time is a configurable leeway time before a vehicle starts to be charged after entering the parking zone. For example, if you need to set up a 2-hour free parking period before paid time or parking enforcement takes effect, you would set the convenience time for 2 hours. For parking lots where parking enforcement begins immediately, you would still need to set a short convenience time to allow vehicle owners time to find a parking spot and purchase parking time before parking enforcement begins.NOTE:
- If you are setting up a parking lot that uses permits, you can set the convenience time for 10 minutes. This allows clients enough time to park and purchase a permit before they are in violation. You can also give the client leniency when exiting by configuring a grace period.
- If you are setting up a parking lot that is free, but with a 1-hour time limit, you must configure a 1-hour convenience time. Note that this scenario does not use third-party parking permits and does not require the Pay-by-Plate Sync plugin.
- Grace period
- A grace period can be added to a parking session for purposes of lenient enforcement. Following the expiration of the vehicle’s parking time, extra time is given before a vehicle's parking session is flagged as a violation.
If your system uses the Pay-by-Plate
Sync plugin to
incorporate third-party payment systems, turn on the feature and configure the
- Permit / permit restriction
- Select the Pay-by-Plate
Sync permit or permit
restriction you want to apply.NOTE: Permit restrictions require Pay-by-Plate Sync 5.0 or later.
- Default expiration delay
- It is recommended that you configure an EffectiveDate and ExpiryDate for Pay-by-Plate Sync permits (if supported by the payment providers). This reduces the volume of queries to the third-party providers. The Default expiration delay is used for permits that do not include an expiration. In this case, AutoVu™ Free-Flow checks with the parking permit provider to see if the permit is still valid. Increasing this value reduces the frequency of the permit checks. For example, if the parking lot charges for parking in increments of 15 minutes, you could set the Default expiration delay to 15 minutes.
- Convenience time and grace period
- When using Pay-by-Plate Sync for transient parking, you can also configure convenience time and a grace period for purposes of lenient enforcement.