Remote Traveler Support (Subsystem*)
The Remote Traveler Support Subsystem (RTSS) 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).
Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Remote Basic Information Reception (Equipment Package*)
PSpecs: - Remote Interactive Information Reception (Equipment Package*)
PSpecs:- 6.3.1-Get Traveler Request
- 6.3.2-Inform Traveler
- 6.3.3-Provide Traveler Kiosk Interface
- 6.3.4-Update Traveler Display Map Data at Kiosk
- 7.3.4-Provide Remote Terminal Traveler Card Interface
- 7.5.2-Provide Traveler Roadside Traveler Card Interface
- 7.5.4-Provide Traveler Kiosk Traveler Card Interface
- 7.6.6.2-Provide VMT Services Kiosk Interface
- Remote Transit Fare Management (Equipment Package*)
PSpecs:- 4.7.2.1-Detect Traveler at Roadside
- 4.7.2.2-Determine Traveler Needs at Roadside
- 4.7.2.3-Determine Transit Fare at Roadside
- 4.7.2.4-Manage Transit Fare Billing at Roadside
- 4.7.2.5-Provide Traveler Roadside Fare Interface
- 4.7.2.6-Update Roadside Transit Fare Data
- 4.7.2.7-Provide Transit Roadside Passenger Data
- 7.3.4-Provide Remote Terminal Traveler Card Interface
- 7.5.2-Provide Traveler Roadside Traveler Card Interface
- Remote Transit Information Services (Equipment Package*)
PSpecs: - Remote Traveler Security (Equipment Package*)
PSpecs:- 5.1.7.1.5-Report Traveler Emergencies
- Traveler Secure Area Sensor Monitoring (Equipment Package*)
PSpecs: - Traveler Secure Area Surveillance (Equipment Package*)
PSpecs:
Inputs/Outputs: Architecture Flows* and Data Flows*
Emergency Management
Remote Traveler Support
- alarm acknowledge (Architecture Flow*) - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
Data Flows*: - secure area sensor control (Architecture Flow*) - Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing.
Data Flows*: - secure area surveillance control (Architecture Flow*) - Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing.
Data Flows*:
Information Service Provider
Remote Traveler Support
- broadcast traveler information (Architecture Flow*) - General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information.
Data Flows*:- traveler_broadcast_border_data
- traveler_broadcast_event_information
- traveler_broadcast_incident_information
- traveler_broadcast_multimodal_data
- traveler_broadcast_parking_data
- traveler_broadcast_price_data
- traveler_broadcast_traffic_data
- traveler_broadcast_transit_data
- traveler_broadcast_weather_data
- emergency traveler information (Architecture Flow*) - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.
Data Flows*: - interactive traveler information (Architecture Flow*) - Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.
Data Flows*:- advanced_tolls_and_charges_roadside_confirm
- traveler_interactive_border_data
- traveler_interactive_event_information
- traveler_interactive_incident_information
- traveler_interactive_multimodal_data
- traveler_interactive_parking_data
- traveler_interactive_price_data
- traveler_interactive_traffic_data
- traveler_interactive_transit_data
- traveler_interactive_weather_data
- travel services information (Architecture Flow*) - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.
Data Flows*: - trip plan (Architecture Flow*) - A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows*:
Map Update Provider
Remote Traveler Support
- map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
Payment Administration
Remote Traveler Support
- traveler payment request (Architecture Flow*) - Request for payment for road use charges.
Data Flows*: - user VMT account reports (Architecture Flow*) - Reports on VMT charges
Data Flows*:
Remote Traveler Support
Emergency Management
- alarm notification (Architecture Flow*) - Notification of activation of an audible or silent alarm by a traveler in a public area or by a transit vehicle operator using an on-board device.
Data Flows*: - secure area sensor data (Architecture Flow*) - Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected.
Data Flows*:- field_processed_traveler_intrusion_motion_sensor_data
- field_processed_traveler_object_detection_sensor_data
- field_processed_traveler_threat_sensor_data
- traveler_intrusion_motion_sensor_data
- traveler_intrusion_motion_sensor_status
- traveler_object_detection_sensor_data
- traveler_object_detection_sensor_status
- traveler_secure_area_sensor_threat_data
- traveler_threat_sensor_data
- traveler_threat_sensor_status
- secure area surveillance data (Architecture Flow*) - Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected.
Data Flows*:
Remote Traveler Support
Information Service Provider
- emergency traveler information request (Architecture Flow*) - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
Data Flows*: - travel services request (Architecture Flow*) - Request for travel service information including tourist attractions, lodging, restaurants, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.
Data Flows*: - traveler request (Architecture Flow*) - A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.
Data Flows*: - trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*: - trip request (Architecture Flow*) - Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include a request for transit and parking reservations and ridesharing options associated with the trip.
Data Flows*:
Remote Traveler Support
Map Update Provider
- map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
Remote Traveler Support
Payment Administration
- traveler payment information (Architecture Flow*) - Payment information for road use charges.
Data Flows*: - user VMT account setup (Architecture Flow*) - Billing information, vehicle information (or registration information), and requests for reports.
Data Flows*:
Remote Traveler Support
Transit Management
- transit fare and passenger status (Architecture Flow*) - Information provided from the traveler location that supports fare payments, passenger data, and associated record-keeping.
Data Flows*: - transit information user request (Architecture Flow*) - Request for special transit routing, real-time schedule information, and availability information.
Data Flows*: - trip confirmation (Architecture Flow*) - Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
Data Flows*:
Remote Traveler Support
Traveler
- traveler interface updates (Architecture Flow*) - Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler.
Data Flows*:
Remote Traveler Support
Traveler Card
- request for payment (Architecture Flow*) - Request to deduct cost of service from user's payment account.
Data Flows*: - traveler card update (Architecture Flow*) - Information updated concerning traveler's personal data including items such as address, trip records, and profile data.
Data Flows*:
Secure Area Environment
Remote Traveler Support
- secure area characteristics (Architecture Flow*) - The range of physical and environmental characteristics (visual, audible, presence, motion, chemical, biological, radiological, other) that are monitored by surveillance and sensor systems.
Data Flows*:
Transit Management
Remote Traveler Support
- transit fare information (Architecture Flow*) - Information provided by transit management that supports fare payment transactions and passenger data collection.
Data Flows*: - transit traveler information (Architecture Flow*) - Transit information prepared to support transit users and other travelers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information.
Data Flows*: - trip plan (Architecture Flow*) - A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
Data Flows*:
Traveler
Remote Traveler Support
- traveler inputs (Architecture Flow*) - User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service.
Data Flows*:
Traveler Card
Remote Traveler Support
- payment (Architecture Flow*) - Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account.
Data Flows*: - traveler card information (Architecture Flow*) - The traveler personal information such as name, address, license number, and trip records and profile data.
Data Flows*:
