NYSDOT Rest Areas/Truck Stops/Service Plaza Kiosks - Remote Traveler Support Functionality
Subsystem Description
This subsystem provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops, simple displays providing schedule information and imminent arrival signals can be provided. This basic information may be extended to include multi-modal information including traffic conditions and transit schedules along with yellow pages information to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. The subsystem also supports electronic payment of transit fares.
In addition to the traveler information provisions, this subsystem also supports security and safety monitoring of public areas. This monitoring includes traveler activated silent alarms, as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras) and/or audio systems. The sensor equipment includes threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors (e.g. metal detectors).
Functional Area: Remote Interactive Information Reception
Public traveler interface, such as a kiosk, that provides traffic, transit, yellow pages, special event, and other personalized traveler information services upon request.
ID | Requirement | Status |
---|---|---|
1 | The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request. | Planned |
2 | The public interface for travelers shall receive transit information from a center and present it to the traveler upon request. | Planned |
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. | Planned |
4 | The public interface for travelers shall receive event information from a center and present it to the traveler upon request. | Planned |
5 | The public interface for travelers shall receive evacuation information from a center and present it to the traveler. | Planned |
6 | The public interface for travelers shall receive wide-area alerts and present it to the traveler. | Planned |
7 | The public interface for travelers shall accept reservations for confirmed trip plans. | Planned |
8 | The public interface for travelers shall support payment for services, such as confirmed trip plans, confirmed yellow pages services, tolls, transit fares, parking lot charges, and advanced payment for tolls. | Planned |
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. | Planned |
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. | Planned |
11 | The public interface for travelers shall provide digitized map data to act as the background to the information presented to the traveler. | Planned |
12 | The public interface for travelers shall support traveler input in audio or manual form. | Planned |
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. | Planned |
14 | The public interface for travelers shall be able to store frequently requested data. | Planned |