AMPA Regional ITS Architecture Update

Element Expanded Functional Requirements: Mesa Del Sol Amphitheater Parking System

Functional Area: Parking Management
  1. The parking element shall maintain parking lot information including static information such as hours of operation, rates, location, entrance locations, capacity, type, and constraints; as well as dynamic information such as current state of the lot, occupancy, arrival rates, and departure rates.
  2. The parking element shall share information with a traffic management center to identify queues at entrances, exits that should be used, and other information that supports coordinated local traffic control in and around the parking facility.
  3. The parking element shall manage local dynamic message signs that display messages to travelers such as the parking lot state, number of spaces available, location of entrances, and current charges.
  4. The parking element shall provide the capability to detect, count, and classify vehicles at entrances, exits, and designated locations within a parking facility.
Functional Area: Parking Electronic Payment
  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 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.
Functional Area: Parking Coordination
  1. The parking element shall exchange parking management data with other parking facilities including location, hours, availability, status, lot usage, operating strategies, and charging information.
  2. The parking element shall provide parking management data to traffic management centers upon request as part of the implementation of demand management programs in the region. This could include changes to hours of operation or pricing.
  3. The parking element shall distribute parking lot information to traffic management centers upon request to support integrated regional traffic control and parking management. This could include information on facility hours of operation and current parking availability.
  4. The parking element shall distribute parking lot information upon request to transit management centers for park and ride facilities, parking shuttle services, and other applications that integrate transit and parking services.
  5. The parking element shall distribute parking lot information upon request to traveler information providers to support travel planning.
  6. The parking element shall support requests for parking reservations.