Physical Object: Parking Area Equipment

Parking Area Electronic Payment

Overview

'Parking Area Electronic Payment' supports electronic payment of parking fees using in-vehicle equipment (e.g., tags) or contact or proximity cards. It includes the field elements that provide the interface to the in-vehicle or card payment device and the back-office functionality that performs the transaction.

This functional object is included in the "Parking Area Equipment" physical object.

This functional object is included in the following service packages:

This functional object is mapped to the following Functional View PSpecs:

Requirements

# Requirement
01 The parking element shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable features, etc.).
02 The parking element shall read data from the payment device on-board the vehicle or by the traveler.
03 The parking element shall provide an interface to the driver informing them of the success or failure of the financial transaction. This may involve a request for the driver to pull aside so the operator can resolve an issue.
04 The parking element shall collect data on payment violations and send the data, including images of the violator and the vehicle registration data obtained from the Department of Motor Vehicles (DMV) office, to the appropriate enforcement agency.
05 The parking element shall manage the parking lot charges, considering such factors as location, vehicle types, and times of day.
06 The parking element shall process the financial requests and manage an interface to a Financial Institution.
07 The parking element shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments.
08 The parking element shall process requests for parking lot charges to be paid in advance.
09 The parking element shall process requests for the advanced payment of tolls and transit fares as well as other non-transportation services, e.g. yellow-pages services.
10 The parking element shall maintain a list of invalid traveler credit identities.
11 The field element shall provide drivers the current parking lot charges, considering such factors as location, vehicle types, and times of day.
12 The field element shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments.
13 The field element shall read data from the traveler card / payment instrument carried on-board the vehicle or by the traveler.
14 The field element shall provide an interface to the driver informing them of the success or failure of the financial transaction. This may involve a request for the driver to pull aside so the operator can resolve an issue.

Standards

Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.