6.5.2: Provide Interactive Data Interface

This process shall receive data from the ISP data collector function for traffic, transit, incident, weather, event, parking, multimodal travel services, and pricing information. This process shall receive requests for information from kiosks (traveler), personal devices (traveler_personal), in-vehicle units (vehicle), and telecommunications-based traveler information systems (traveler_telecomm, commonly called "511"). The requested information will be pulled from the data being sent from the data collectors, processed for traveler consumption, filtered and sorted based on the traveler's request, and sent back out to the requesting processes. The data may be filtered depending on the type of request, location of the requesting process, or specifics provided by the requesting process. The content and format of these messages shall be based upon parameters which are managed by the ISP operator.

This process is associated with the Transportation Information Center physical object.

This process is associated with the following application objects:

This process is associated with the following data flows:

border_data_for_interactive - In
event_information_for_interactive - In
event_information_request_from_interactive - Out
incident_information_for_interactive - In
incident_information_request_from_interactive - Out
interactive_traveler_information_parameters - In
multimodal_data_for_interactive - In
multimodal_data_request_from_interactive - Out
parking_data_for_interactive - In
parking_data_request_from_interactive - Out
price_data_for_interactive - In
price_data_request_from_interactive - Out
profiles_for_interactive - In
traffic_data_for_interactive - In
traffic_data_request_from_interactive - Out
transit_data_for_interactive - In
transit_data_request_from_interactive - Out
transportation_data_for_interactive_output - In
traveler_info_requests_for_archive - Out
traveler_information_request - In
traveler_interactive_border_data - Out
traveler_interactive_event_information - Out
traveler_interactive_incident_information - Out
traveler_interactive_multimodal_data - Out
traveler_interactive_parking_data - Out
traveler_interactive_price_data - Out
traveler_interactive_traffic_data - Out
traveler_interactive_transit_data - Out
traveler_interactive_weather_data - Out
traveler_personal_information_request - In
traveler_personal_interactive_border_data - Out
traveler_personal_interactive_event_information - Out
traveler_personal_interactive_incident_information - Out
traveler_personal_interactive_multimodal_data - Out
traveler_personal_interactive_parking_data - Out
traveler_personal_interactive_price_data - Out
traveler_personal_interactive_traffic_data - Out
traveler_personal_interactive_transit_data - Out
traveler_personal_interactive_traveler_information - Out
traveler_personal_interactive_weather_data - Out
traveler_telecomm_information_request - In
traveler_telecomm_interactive_border_data - Out
traveler_telecomm_interactive_event_information - Out
traveler_telecomm_interactive_incident_information - Out
traveler_telecomm_interactive_multimodal_data - Out
traveler_telecomm_interactive_parking_data - Out
traveler_telecomm_interactive_price_data - Out
traveler_telecomm_interactive_traffic_data - Out
traveler_telecomm_interactive_transit_data - Out
traveler_telecomm_interactive_weather_data - Out
vehicle_information_request - In
vehicle_interactive_border_data - Out
vehicle_interactive_event_information - Out
vehicle_interactive_incident_information - Out
vehicle_interactive_multimodal_data - Out
vehicle_interactive_parking_data - Out
vehicle_interactive_price_data - Out
vehicle_interactive_traffic_data - Out
vehicle_interactive_transit_data - Out
vehicle_interactive_traveler_information - Out
vehicle_interactive_weather_data - Out
weather_data_for_interactive - In
weather_data_request_from_interactive - Out