Physical Object: Traveler Support Equipment
Traveler Interactive Information
Overview
'Traveler Interactive Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by a public traveler interface, such as a kiosk.
This functional object is included in the "Traveler Support Equipment" physical object.
This functional object is included in the following service packages:
- PS14: Disaster Traveler Information
- SU04: Map Management
- TI02: Personalized Traveler Information
- TI09: Travel Services Information and Reservation
- TM11: Road Use Charging
This functional object is mapped to the following Functional View PSpecs:
- 6.3.1: Get Traveler Request
- 6.3.2: Inform Traveler
- 6.3.3: Provide Public Traveler Interface
- 6.3.4: Update Traveler Display Map Data at Kiosk
- 7.3.4: Provide Remote Terminal Payment Device Interface
- 7.5.2: Provide Traveler Roadside Payment Device Interface
- 7.5.4: Provide Traveler Kiosk Payment Device Interface
- 7.6.6.2: Provide Road Use Charging Services Kiosk Interface
Requirements
# | Requirement |
---|---|
01 | The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request. |
02 | The public interface for travelers shall receive transit information from a center and present it to the traveler upon request. |
03 | 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. |
04 | The public interface for travelers shall receive event information from a center and present it to the traveler upon request. |
05 | The public interface for travelers shall receive evacuation information from a center and present it to the traveler. |
06 | The public interface for travelers shall accept reservations for confirmed trip plans. |
07 | 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. |
08 | 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. |
09 | 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. |
10 | The public interface for travelers shall support interactive traveler input in audio or manual form. |
11 | The public interface for travelers shall present interactive 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. |
12 | The public interface for travelers shall store frequently requested data. |
13 | The public interface for travelers shall provide an interface to establish and manage user road pricing accounts, process road pricing payments, and access road pricing reports under user control. |
14 | The public interface for travelers shall receive information on the shelter from a center and present it to the traveler. |
15 | The public interface for travelers shall provide an interface to select information on resources and options along an evacuation route based on inputs from other evacuees. |
16 | The public interface for travelers shall receive information on estimated reentry date/times from a center and present it to the traveler. |
Information Flows
Standards
Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.