KIPDA Regional ITS Architecture

Element Expanded Functional Requirements: Louisville Traveler Information Kiosks

Functional Area: Remote Basic Information Reception
  1. The public interface for travelers shall receive traffic information from a center and present it to the traveler.
  2. The public interface for travelers shall receive transit information from a center and present it to the traveler.
  3. The public interface for travelers shall receive event information from a center and present it to the traveler.
  4. This public interface for travelers shall receive evacuation information from a center and present it to the traveler.
  5. The public interface for travelers shall receive wide-area alerts and present it to the traveler.
  6. The public interface for travelers shall provide the capability for digitized map data to act as the background to the information presented to the traveler.
  7. The public interface for travelers shall support traveler input in audio or manual form.
  8. The public interface for travelers shall present information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities.
  9. The public interface for travelers shall be able to store frequently requested data.
Functional Area: Remote Interactive Information Reception
  1. The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request.
  2. The public interface for travelers shall receive transit information from a center and present it to the traveler upon request.
  3. The public interface for travelers shall receive yellow pages information (such as lodging, restaurants, theaters, bicycle facilities, and other tourist activities) from a center and present it to the traveler upon request.
  4. The public interface for travelers shall receive event information from a center and present it to the traveler upon request.
  5. The public interface for travelers shall receive evacuation information from a center and present it to the traveler.
  6. The public interface for travelers shall receive wide-area alerts and present it to the traveler.
  7. The public interface for travelers shall accept reservations for confirmed trip plans.
  8. The public interface for travelers shall support payment for services, such as confirmed trip plans, confirmed traveler services, tolls, transit fares, parking lot charges, and advanced payment for tolls.
  9. The public interface for travelers shall provide an interface through which credit identities and stored credit values may be collected from tags, traveler cards, or payment instruments used by travelers.
  10. The public interface for travelers shall base requests from the traveler on the traveler's current location or a specific location identified by the traveler, and filter the provided information accordingly.
  11. The public interface for travelers shall provide digitized map data to act as the background to the information presented to the traveler.
  12. The public interface for travelers shall support traveler input in audio or manual form.
  13. The public interface for travelers shall present information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities.
  14. The public interface for travelers shall be able to store frequently requested data.
  15. The public interface for travelers shall provide an interface to establish and manage user VMT accounts, process VMT payments, and access VMT reports under user control.