Information Service Provider (Subsystem*)
The Information Service Provider Subsystem (ISPS) collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The subsystem can play several different roles in an integrated ITS. In one role, the ISP provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other ISPs. In this information redistribution role, the ISP provides a bridge between the various transportation systems that produce the information and the other ISPs and their subscribers that use the information. The second role of an ISP is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ridematching information, and parking information. The subsystem also provides the capability to provide specific directions to travelers by receiving origin and destination requests from travelers, generating route plans, and returning the calculated plans to the users. In addition to general route planning for travelers, the ISP also supports specialized route planning for vehicle fleets. In this third role, the ISP function may be dedicated to, or even embedded within, the dispatch system. Reservation services are also provided in advanced implementations. The information is provided to the traveler through the Personal Information Access Subsystem, Remote Traveler Support Subsystem, and the Vehicle Subsystem through available communications links. Both basic one-way (broadcast) and personalized two-way information provision are supported. The ISP is most commonly implemented as an Internet web site, but it represents any traveler information distribution service including systems that broadcast digital transportation data (e.g., satellite radio networks) and systems that support distribution through Field-Vehicle Communications networks. The ISP accomplishes these roles using constantly evolving technologies like the Internet (World Wide Web pages), direct broadcast communications (email alerts, pagers, satellite radio network data broadcasts), communications through Field-Vehicle Communications networks, etc.Subsystem Interfaces Diagram
Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.
Functionality: Equipment Packages* and PSpecs*
- Basic Information Broadcast (Equipment Package*)
PSpecs: - Infrastructure Provided Dynamic Ridesharing (Equipment Package*)
PSpecs:- 6.1.1-Provide Trip Planning Information to Traveler
- 6.1.2-Confirm Traveler's Trip Plan
- 6.1.3-Provide ISP Operator Interface for Trip Planning Parameters
- 6.4.1-Screen Rider Requests
- 6.4.2-Match Rider and Provider
- 6.4.3-Report Ride Match Results to Requestor
- 6.4.4-Confirm Traveler Rideshare Request
- 7.4.1.7-Process Traveler Rideshare Payments
- Infrastructure Provided Trip Planning (Equipment Package*)
PSpecs:- 6.1.1-Provide Trip Planning Information to Traveler
- 6.1.2-Confirm Traveler's Trip Plan
- 6.1.3-Provide ISP Operator Interface for Trip Planning Parameters
- 6.10-Manage Traveler Profiles
- 6.6.1-Provide Multimodal Route Selection
- 6.6.2.1-Calculate Vehicle Route
- 6.6.2.2-Provide Vehicle Route Calculation Data
- 6.6.3-Provide ISP Operator Route Parameters Interface
- 6.6.4-Select Transit Route
- 6.6.5-Select Other Routes
- 7.1.6-Distribute Advanced Charges and Fares
- 7.3.2-Distribute Advanced Tolls and Parking Lot Charges
- 7.4.1.3-Process Driver Map Update Payments
- 7.4.1.4-Process Traveler Map Update Payments
- 7.4.1.6-Process Traveler Trip and Other Services Payments
- 7.4.3-Route Traveler Advanced Payments
- Interactive Infrastructure Information (Equipment Package*)
PSpecs: - ISP Data Collection (Equipment Package*)
PSpecs:- 6.9-Manage Traveler Info Archive Data
- ISP Emergency Traveler Information (Equipment Package*)
PSpecs: - ISP Operational Data Repository (Equipment Package*)
PSpecs: - ISP Probe Information Collection (Equipment Package*)
PSpecs: - ISP Short Range Communications Traveler Information Distribution (Equipment Package*)
PSpecs: - ISP Travel Services Information and Reservation (Equipment Package*)
PSpecs: - ISP Traveler Data Collection (Equipment Package*)
PSpecs:- 6.2.1-Collect Misc Traveler Information
- 6.2.2-Collect Traffic Data
- 6.2.3-Collect Transit Operations Data
- 6.2.4-Collect Multimodal Data
- 6.2.6-Collect Emergency Traveler Data
- 6.2.7-Provide ISP Operator Data Collection Interface
- 6.2.8-Provide ISP Map Update Interface
- 6.6.2.3-Provide Route Segment Data for Other Areas
- 7.4.2-Collect Price Data for ITS Use
- ISP Traveler Information Alerts (Equipment Package*)
PSpecs: - Traveler Telephone Information (Equipment Package*)
PSpecs:
Inputs/Outputs: Architecture Flows* and Data Flows*
Archived Data Management
Information Service Provider
- archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*: - archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
Border Inspection Systems
Information Service Provider
- border crossing status information (Architecture Flow*) - Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border
Data Flows*:
Care Facility
Information Service Provider
- care facility status (Architecture Flow*) - Information regarding facility type and capabilities, facility status, and its ability to admit new patients.
Data Flows*:
Commercial Vehicle Administration
Information Service Provider
- route restrictions (Architecture Flow*) - Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits).
Data Flows*:
Emergency Management
Information Service Provider
- alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This flow may also identify specific information that should not be released to the public.
Data Flows*: - evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
Emissions Management
Information Service Provider
- air quality information (Architecture Flow*) - Aggregated region-wide measured air quality data and possible pollution incident information.
Data Flows*:
Event Promoters
Information Service Provider
- event information (Architecture Flow*) - Special event information for travelers. This would include a broader array of information than the similar "event plans" that conveys only information necessary to support traffic management for the event.
Data Flows*:
Financial Institution
Information Service Provider
- transaction status (Architecture Flow*) - Response to transaction request. Normally dealing with a request for payment.
Data Flows*:
Fleet and Freight Management
Information Service Provider
- route request (Architecture Flow*) - Request for a tailored route based on given constraints.
Data Flows*: - toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
Information Service Provider
Archived Data Management
- traveler archive data (Architecture Flow*) - Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
Information Service Provider
Emergency Management
- alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*: - transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:
Information Service Provider
Event Promoters
- event information request (Architecture Flow*) - Request for special event information.
Data Flows*:
Information Service Provider
Financial Institution
- payment request (Architecture Flow*) - Request for payment from financial institution.
Data Flows*:
Information Service Provider
Fleet and Freight Management
- incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - route plan (Architecture Flow*) - Tailored route provided by ISP in response to a specific request.
Data Flows*: - toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*:
Information Service Provider
ISP Operator
- ISP operations information presentation (Architecture Flow*) - Presentation of information to the ISP Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms.
Data Flows*:- tispo-archive_status
- tispo-data_collection_parameters
- tispo-route_selection_parameters
- tispo-trav_info_equip_status
- tispo-travel_services_operator_information
- tispo-traveler_data_collected
- tispo-traveler_information_parameters
- tispo-traveler_services_data
- tispo-trip_planning_data
- tispo-trip_planning_parameters
Information Service Provider
Maintenance and Construction Management
- field equipment status (Architecture Flow*) - Identification of field equipment requiring repair and known information about the associated faults.
Data Flows*: - road network environmental probe data (Architecture Flow*) - Aggregated vehicle probe information that can be used to estimate current environmental conditions. Collected information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information.
Data Flows*: - transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:
Information Service Provider
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*:
Information Service Provider
Media
- traveler information for media (Architecture Flow*) - General traveler information regarding incidents, unusual traffic conditions, transit issues, or other advisory information that has been desensitized and provided to the media.
Data Flows*:
Information Service Provider
Multimodal Transportation Service Provider
- multimodal information request (Architecture Flow*) - Information request for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*:
Information Service Provider
Other ISP
- 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*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - multimodal information (Architecture Flow*) - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*: - parking information (Architecture Flow*) - General parking information and status, including current parking availability.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*: - transit service information (Architecture Flow*) - Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.
Data Flows*:
Information Service Provider
Parking Management
- parking lot data request (Architecture Flow*) - Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*: - parking reservations request (Architecture Flow*) - Reservation request for parking lot.
Data Flows*:
Information Service Provider
Payment Administration
- toll data request (Architecture Flow*) - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*:
Information Service Provider
Personal Information Access
- 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_personal_broadcast_border_data
- traveler_personal_broadcast_event_information
- traveler_personal_broadcast_incident_information
- traveler_personal_broadcast_multimodal_data
- traveler_personal_broadcast_parking_data
- traveler_personal_broadcast_price_data
- traveler_personal_broadcast_traffic_data
- traveler_personal_broadcast_transit_data
- traveler_personal_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*:- traveler_map_update_payment_response
- traveler_personal_display_update_payment_response
- traveler_personal_interactive_border_data
- traveler_personal_interactive_event_information
- traveler_personal_interactive_incident_information
- traveler_personal_interactive_multimodal_data
- traveler_personal_interactive_parking_data
- traveler_personal_interactive_price_data
- traveler_personal_interactive_traffic_data
- traveler_personal_interactive_transit_data
- traveler_personal_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*: - traveler alerts (Architecture Flow*) - Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler-supplied profile information including trip characteristics and preferences.
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*:
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*:
Information Service Provider
Roadway
- 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*: - 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*:
Information Service Provider
Shelter Providers
- 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*:
Information Service Provider
Surface Transportation Weather Service
- road network environmental probe data (Architecture Flow*) - Aggregated vehicle probe information that can be used to estimate current environmental conditions. Collected information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information.
Data Flows*: - transportation weather information request (Architecture Flow*) - A request for transportation weather information that may specify the area of interest (a geographic region, particular routes within a region, specific road segments), the type of information that is required, the desired spatial resolution of the information, and time horizon.
Data Flows*:
Information Service Provider
Telecommunications System for Traveler Information
- voice-based alert notification (Architecture Flow*) - Information to be distributed to the traveling public via voice regarding a major emergency such as a natural or man-made disaster, civil emergency, severe weather or child abduction. The flow may identify the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. The content of this architecture flow may be specially formatted for voice-based traveler information.
Data Flows*: - voice-based traveler information (Architecture Flow*) - Traveler information sent to the telecommunications systems for traveler information terminator. This flow may represent the bulk transfer of traveler information, including traffic conditions, incident information, transit information and weather and road condition information. It may be specially formatted for voice-based traveler information.
Data Flows*:
Information Service Provider
Traffic Management
- fare and price information (Architecture Flow*) - Current transit, parking, and toll fee schedule information.
Data Flows*: - logged vehicle routes (Architecture Flow*) - Anticipated route information for guided vehicles, special vehicles (e.g., oversize vehicles) or groups of vehicles (e.g., governor's motorcade) that may require changes in traffic control strategy.
Data Flows*: - road network traffic probe data (Architecture Flow*) - Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions.
Data Flows*: - transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:
Information Service Provider
Transit Management
- demand responsive transit request (Architecture Flow*) - Request for paratransit support.
Data Flows*: - selected routes (Architecture Flow*) - Routes selected based on route request criteria.
Data Flows*: - transit information request (Architecture Flow*) - Request for transit operations information including schedule and fare information. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows*: - transit trip request (Architecture Flow*) - Request for a transit trip plan that is responsive to traveler requirements such as schedule, cost, or duration.
Data Flows*: - transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:
Information Service Provider
Travel Services Provider
- travel service information request (Architecture Flow*) - Requests for travel service information. This flow supports initial registration of service providers and requests for additional traveler service information from registered providers.
Data Flows*: - travel service reservation request (Architecture Flow*) - Reservation request for traveler services (e.g. for a hotel or restaurant) including billing information when applicable.
Data Flows*:
Information Service Provider
Vehicle
- 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*:- link_and_queue_data
- vehicle_broadcast_border_data
- vehicle_broadcast_event_information
- vehicle_broadcast_incident_information
- vehicle_broadcast_multimodal_data
- vehicle_broadcast_parking_data
- vehicle_broadcast_price_data
- vehicle_broadcast_traffic_data
- vehicle_broadcast_transit_data
- vehicle_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_fares_and_charges_response
- advanced_tolls_and_fares_response
- driver_display_update_payment_response
- driver_map_update_payment_response
- vehicle_interactive_border_data
- vehicle_interactive_event_information
- vehicle_interactive_incident_information
- vehicle_interactive_multimodal_data
- vehicle_interactive_parking_data
- vehicle_interactive_price_data
- vehicle_interactive_traffic_data
- vehicle_interactive_transit_data
- vehicle_interactive_weather_data
- traffic probe reporting management (Architecture Flow*) - Data used to manage probe data reporting by vehicles. This flow indicates to the vehicle when to report probe data, the type of probe data to send, and thresholds for nominal conditions when sending data can be skipped.
Data Flows*: - 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*: - traveler alerts (Architecture Flow*) - Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler-supplied profile information including trip characteristics and preferences.
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*:
Information Service Provider
Weather Service
- road network environmental probe data (Architecture Flow*) - Aggregated vehicle probe information that can be used to estimate current environmental conditions. Collected information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information.
Data Flows*:
ISP Operator
Information Service Provider
- ISP operator inputs (Architecture Flow*) - User input from the ISP system operator including requests to monitor current system operation and inputs to affect system operation including tuning and performance enhancement parameters to ISP algorithms.
Data Flows*:- fispo-archive_commands
- fispo-data_collection_parameters_request
- fispo-data_collection_parameters_update
- fispo-request_data_collection_map_update
- fispo-request_other_routes_selection_map_data_update
- fispo-request_route_selection_map_data_update
- fispo-request_traveler_service_map_update
- fispo-request_trip_planning_map_update
- fispo-route_selection_parameters_request
- fispo-route_selection_parameters_update
- fispo-trav_info_equip_status_request
- fispo-travel_services_operator_inputs
- fispo-traveler_data_collection_request
- fispo-traveler_information_parameters_request
- fispo-traveler_information_parameters_update
- fispo-trip_planning_parameters_request
- fispo-trip_planning_parameters_update
Maintenance and Construction Management
Information Service Provider
- current asset restrictions (Architecture Flow*) - Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
Data Flows*: - equipment maintenance status (Architecture Flow*) - Current status of field equipment maintenance actions.
Data Flows*: - maint and constr work plans (Architecture Flow*) - Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
Data Flows*: - road weather information (Architecture Flow*) - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
Data Flows*: - roadway maintenance status (Architecture Flow*) - Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
Data Flows*: - work zone information (Architecture Flow*) - Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
Data Flows*:
Map Update Provider
Information Service Provider
- map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
Media
Information Service Provider
- external reports (Architecture Flow*) - Traffic and incident information that is collected by the media through a variety of mechanisms (e.g., radio station call-in programs, air surveillance).
Data Flows*:
Multimodal Transportation Service Provider
Information Service Provider
- multimodal information (Architecture Flow*) - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*:
Other ISP
Information Service Provider
- 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*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - multimodal information (Architecture Flow*) - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*: - parking information (Architecture Flow*) - General parking information and status, including current parking availability.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*: - transit service information (Architecture Flow*) - Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.
Data Flows*:
Parking Management
Information Service Provider
- parking information (Architecture Flow*) - General parking information and status, including current parking availability.
Data Flows*: - parking lot reservation confirmation (Architecture Flow*) - Confirmation for parking lot reservation.
Data Flows*:
Payment Administration
Information Service Provider
- toll data (Architecture Flow*) - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows*: - toll probe data (Architecture Flow*) - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
Data Flows*: - VMT data for ISP (Architecture Flow*) - Road use charge rate policies for distribution to travelers.
Data Flows*:
Personal Information Access
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 profile (Architecture Flow*) - Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions.
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
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*:
Roadway
Information Service Provider
- environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
Data Flows*: - short range communications status (Architecture Flow*) - Status of the short range communications equipment including the current state or mode of operation and the current equipment status.
Data Flows*: - traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
Data Flows*:
Shelter Providers
Information Service Provider
- shelter information (Architecture Flow*) - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
Data Flows*:
Surface Transportation Weather Service
Information Service Provider
- transportation weather information (Architecture Flow*) - Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making.
Data Flows*:
Telecommunications System for Traveler Information
Information Service Provider
- voice-based traveler request (Architecture Flow*) - The electronic traveler information request from the telecommunications systems for traveler information terminator. It may be specifically formatted for voice-based traveler requests. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*:
Traffic Management
Information Service Provider
- incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*:
Transit Management
Information Service Provider
- demand responsive transit plan (Architecture Flow*) - Plan regarding overall demand responsive transit schedules and deployment.
Data Flows*: - emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
Data Flows*: - transit and fare schedules (Architecture Flow*) - Transit service information including routes, schedules, and fare information.
Data Flows*: - transit incident information (Architecture Flow*) - Information on transit incidents that impact transit services for public dissemination.
Data Flows*: - transit probe data (Architecture Flow*) - Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
Data Flows*: - transit request confirmation (Architecture Flow*) - Confirmation of a request for transit information or service.
Data Flows*: - transit schedule adherence information (Architecture Flow*) - Dynamic transit schedule adherence and transit vehicle location information.
Data Flows*: - transit trip plan (Architecture Flow*) - An origin-destination transit trip that may involve multiple modes and connections. (could use current trip plan that is PIAS to ISP, but since this is center to center a separate AF might be called for).
Data Flows*:
Travel Services Provider
Information Service Provider
- travel service information (Architecture Flow*) - Information supplied by a service provider (e.g., a hotel or restaurant) that identifies the service provider and provides details of the service offering. This flow covers initial registration of a service provider and subsequent submittal of new information and status updates so that data currency is maintained.
Data Flows*: - travel service reservations (Architecture Flow*) - Traveler service (e.g., for a hotel or restaurant) reservation information and status, including information on associated billing transactions, when applicable.
Data Flows*:
Vehicle
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*: - environmental probe data (Architecture Flow*) - Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
Data Flows*: - traffic probe data (Architecture Flow*) - Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions.
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 profile (Architecture Flow*) - Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions.
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*:
Weather Service
Information Service Provider
- qualified environmental conditions data (Architecture Flow*) - Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included.
Data Flows*: - weather information (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
Data Flows*:

