Send Your Comments

Parking Electronic Payment Equipment Package

Description:

Parking payment collection using in-vehicle equipment (tags) or contact or proximity traveler cards used for electronic payment. Includes field elements and back-office functionality.

Included in:

Lufkin Intermodal Terminal

Functional Requirements:

1	The parking element shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable features, etc.).
2	The parking element shall read data from the traveler card / payment instrument carried on-board the vehicle (tag) or by the traveler.
3	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.
4	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.
5	The parking element shall manage the parking lot charges, considering such factors as location, vehicle types, and times of day.
6	The parking element shall process the financial requests and manage an interface to a Financial Institution.
7	The parking element shall support the payment of parking lot transactions using data provided by the traveler cards / payment instruments.
8	The parking element shall process requests for parking lot charges to be paid in advance.
9	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, or bad tag lists.

User Service Requirements (fully or partially addressed):

1.8	TRAVEL DEMAND MANAGEMENT
1.8.1	TDM shall include a communications function.
1.8.1.6	The communications function shall include the capability for two-way communications with other ITS user services including, but not limited to, the following:
1.8.1.6(e)	Electronic Payment.
1.8.2	TDM shall include a processing function.
1.8.2.12	The processing function's dynamically generated management and control strategies shall include the capability to respond to the need for control of pollution by generating messages for variable signs that include, but are not limited to, the following:
1.8.2.12(b)	Informing of higher parking fees.
1.8.2.13	The processing function's dynamically generated management and control strategies for air pollution control shall be based on factors that include, but are not limited to, the following:
1.8.2.13(c)	Individual vehicle database files.
3.0	ELECTRONIC PAYMENT
3.1	ELECTRONIC PAYMENT SERVICES
3.1.1	Electronic Payment shall provide an Electronic Toll Collection (ETC) capability.
3.1.1.4	ETC shall include the capability to identify those vehicles and/or operators that violate its toll collection process.
3.1.3	Electronic Payment shall include an Electronic Parking Payment (EPP) capability.
3.1.3.1	EPP shall provide the capability to pay for parking without the use of cash.
3.1.3.2	EPP shall include the capability for transit operators to utilize a single medium to charge for both transit related charges and parking charges.
3.1.3.3	EPP shall provide the capability to provide flexible pricing parking fee structures based upon factors including, but not limited to, vehicle classification.
3.1.4	ITS shall include an Electronic Payment Services Integration (EPSI) feature.
3.1.4.1	EPSI shall provide the capability to combine electronic payments made for use of various transportation modes into a single integrated system.

The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.