  | 
                                    Element Expanded Functional Requirements: HDOT-AIR-K Traveler Information Kiosk | 
                                   
                                | 
                             
    
                            
                               
    
| Functional Area: Remote Basic Information Reception |  
- The public interface for travelers shall receive traffic information from a center and present it to the traveler.
 
- The public interface for travelers shall receive transit information from a center and present it to the traveler.
 
- The public interface for travelers shall receive event information from a center and present it to the traveler.
 
- This public interface for travelers shall receive evacuation information from a center and present it to the traveler.
 
- The public interface for travelers shall receive wide-area alerts and present it to the traveler.
 
- 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.
 
- The public interface for travelers shall support traveler input in audio or manual form.
 
- 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.
 
- The public interface for travelers shall be able to store frequently requested data.
 
  |  
| Functional Area: Remote Interactive Information Reception |  
- The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request.
 
- The public interface for travelers shall receive transit information from a center and present it to the traveler upon request.
 
- 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.
 
- The public interface for travelers shall receive event information from a center and present it to the traveler upon request.
 
- The public interface for travelers shall receive evacuation information from a center and present it to the traveler.
 
- The public interface for travelers shall receive wide-area alerts and present it to the traveler.
 
- The public interface for travelers shall accept reservations for confirmed trip plans.
 
- 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.
 
- 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.
 
- 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.
 
- The public interface for travelers shall provide digitized map data to act as the background to the  information presented to the traveler.
 
- The public interface for travelers shall support traveler input in audio or manual form.
 
- 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.
 
- The public interface for travelers shall be able to store frequently requested data.
 
- 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.
 
  |  
 
                           | 
                           
                       
                   | 
                   
               
           | 
           
              |