Information Service Provider

This subsystem 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 traveller information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, business directory information, ridematching information, parking information and weather information. The subsystem also provides the capability to provide specific directions to travellers by receiving origin and destination requests from travellers, generating route plans, and returning the calculated plans to the users. In addition to general route planning for travellers, 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 traveller through the Personal Information Access Subsystem, Remote Traveller 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 traveller information distribution service including systems that broadcast digital transportation data (e.g., satellite radio networks) and systems that support distribution through dedicated short range 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 dedicated short range communications networks, etc.

Security Considerations

The Information Service Provider security considerations are related to the sensitivity of the requests being made for information as well as the sensitivity of the information being provided. Some ISPs may charge their clients for information and services, in which case security measures should be in place to protect the client's personal information including their credit information as well as unauthorized access to premium services. Information such as evacuation information and emergency alerts can jeopardize public safety if the information is unauthorized, inaccurate, or not delivered in a timely fashion. Traveller information that contains financial data or other highly sensitive information should have a relatively high degree of confidentiality in order to safeguard the information. In addition, it is important that traveller information is available in times of crisis. The integrity of the information is also important to prevent deceptive practices. Most traveller information will not require this level of safeguarding.

Functionality: Equipment Packages and PSpecs

• Basic Information Broadcast
  
  • 6.5.1 - Provide Broadcast Data Interface
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  
  
• Infrastructure Provided Business Directory Service and Reservation
  
  • 6.10 - Manage Traveller Profiles
  • 6.5.3 - Register Business Directory Service Providers
  • 6.5.4 - Provide Business Directory Services
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  • 7.4.1.2 - Process Business Directory Services Provider Payments
  • 7.4.1.6 - Process Traveller Trip and Other Services Payments
  
  
• Infrastructure Provided Dynamic Ridesharing
  
  • 6.1.1 - Provide Trip Planning Information to Traveller
  • 6.1.2 - Confirm Traveller'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 Traveller Rideshare Request
  • 7.4.1.7 - Process Traveller Rideshare Payments
  
  
• Infrastructure Provided Trip Planning
  
  • 6.1.1 - Provide Trip Planning Information to Traveller
  • 6.1.2 - Confirm Traveller's Trip Plan
  • 6.1.3 - Provide ISP Operator Interface for Trip Planning Parameters
  • 6.10 - Manage Traveller 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 Traveller Map Update Payments
  • 7.4.1.6 - Process Traveller Trip and Other Services Payments
  • 7.4.3 - Route Traveller Advanced Payments
  
  
• Interactive Infrastructure Information
  
  • 6.10 - Manage Traveller Profiles
  • 6.5.2 - Provide Interactive Data Interface
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  • 7.2.6 - Distribute Advanced Tolls and Fares
  • 7.4.1.4 - Process Traveller Map Update Payments
  
  
• ISP Data Collection
  
  • 6.9 - Manage Traveller Info Archive Data
  
  
• ISP Emergency Traveller Information
  
  • 6.5.5 - Provide Emergency Traveller Information
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  
  
• ISP Operational Data Repository
  
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  • 6.5.8 - Provide Operational Data for Other Centres
  
  
• ISP Probe Information Collection
  
  • 6.2.5 - Collect Probe Data From Vehicles
  • 6.6.2.2 - Provide Vehicle Route Calculation Data
  
  
• ISP Traveller Data Collection
  
  • 6.2.1 - Collect Misc Traveller 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 Traveller 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 Traveller Information Alerts
  
  • 6.10 - Manage Traveller Profiles
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  • 6.5.9 - Provide Traveller Alert Interface
  
  
• ISP VII Traveller Information Distribution
  
  • 6.5.1 - Provide Broadcast Data Interface
  • 6.5.5 - Provide Emergency Traveller Information
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  
  
• Traveller Telephone Information
  
  • 6.5.5 - Provide Emergency Traveller Information
  • 6.5.6 - Provide Traveller Telecomm Information
  • 6.5.7 - Provide ISP Operator Traveller Information Parameters Interface
  
  

Inputs/Outputs: Architecture Flows and Data Flows

Archived Data Management Subsystem > Information Service Provider

• archive requests - 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:
  • traveller_archive_request
  
  
• archive status - 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:
  • traveller_archive_status
  
  

Border Inspection Administration > Information Service Provider

• border traveller information - Traveller information relevant to border crossings such as queue times, transit times, wait times, and weather. This flow may include forecasts of border delays as well as current conditions.
  Data Flows:
  • border_data_for_alerts
  • border_data_for_interactive
  • border_data_for_broadcast
  
  

Border Inspection Systems > Information Service Provider

• border crossing status information - Port of entry status including current wait-times.
  Data Flows:
  • traveller_border_status
  
  

Business Directory Service Providers > Information Service Provider

• travel service information - 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:
  • fbdsp-business_directory_service_data
  • fbdsp-emergency_travel_service_update
  • fbdsp-provider_profile_update
  • fbdsp-request_provider_registration
  
  
• travel service reservations - Traveller service (e.g., for a hotel or restaurant) reservation information and status, including information on associated billing transactions, when applicable.
  Data Flows:
  • fbdsp-transaction_confirmation
  
  

Care Facility > Information Service Provider

• care facility status - Information regarding facility type and capabilities, facility status, and its ability to admit new patients.
  Data Flows:
  • fcf-care_facility_status_for_isp
  
  

Commercial Vehicle Administration > Information Service Provider

• route restrictions - 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:
  • route_restrictions_for_isp
  
  

Emergency Management > Information Service Provider

• alert notification - 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:
  • traveller_information_restrictions_for_travellers
  • wide_area_alert_notification_for_travellers
  • deactivate_traveller_information_restrictions_for_travellers
  
  
• evacuation information - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • evacuation_data_for_isp
  
  
• incident information - 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:
  • incident_information
  
  
• shelter information - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
  Data Flows:
  • shelter_information_for_isp
  
  
• transportation system status - 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:
  • disaster_transportation_system_status_for_isp
  • evacuation_transportation_system_status_for_isp
  
  

Emissions Management > Information Service Provider

• air quality information - Aggregated region-wide measured air quality data and possible pollution incident information.
  Data Flows:
  • current_traffic_pollution_data
  
  

Event Promoters > Information Service Provider

• event information - Special event information for travellers. 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:
  • fevp-event_information_for_travellers
  
  

Financial Institution > Information Service Provider

• transaction status - Response to transaction request. Normally dealing with a request for payment.
  Data Flows:
  • ffi-driver_display_payment_confirm
  • ffi-traveller_rideshare_payment_confirm
  • ffi-traveller_other_services_payments_confirm
  • ffi-traveller_map_payment_confirm
  • ffi-traveller_display_payment_confirm
  • ffi-registration_payment_confirm
  • ffi-driver_map_payment_confirm
  
  

Fleet and Freight Management > Information Service Provider

• route request - Request for a tailored route based on given constraints.
  Data Flows:
  • cf_route_request
  • cv_route_request
  
  
• toll data request - 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:
  • cvo_advanced_payments_request
  
  

Information Service Provider > Archived Data Management Subsystem

• traveller archive data - Data associated with traveller information services including service requests, facility usage, rideshare, routing, and traveller 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:
  • traveller_archive_data
  
  

Information Service Provider > Business Directory Service Providers

• travel service information request - Requests for travel service information. This flow supports initial registration of service providers and requests for additional traveller service information from registered providers.
  Data Flows:
  • tbdsp-provider_update_confirm
  • tbdsp-business_directory_service_info_request
  
  
• travel service reservation request - Reservation request for traveller services (e.g. for a hotel or restaurant) including billing information when applicable.
  Data Flows:
  • tbdsp-transaction_request
  
  

Information Service Provider > Emergency Management

• alert status - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
  Data Flows:
  • alert_notification_status_from_travellers
  
  
• transportation information for operations - 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:
  • transportation_information_for_disaster_operations
  • transportation_information_for_evac_operations
  • transportation_information_for_emerg_routing
  • transportation_information_for_emerg_operations
  
  

Information Service Provider > Event Promoters

• event information request - Request for special event information.
  Data Flows:
  • tevp-event_information_request
  
  

Information Service Provider > Financial Institution

• payment request - Request for payment from financial institution.
  Data Flows:
  • tfi-traveller_map_payment_request
  • tfi-driver_display_payment_request
  • tfi-driver_map_payment_request
  • tfi-registration_payment_request
  • tfi-traveller_display_payment_request
  • tfi-traveller_other_services_payments_request
  • tfi-traveller_rideshare_payment_request
  
  

Information Service Provider > Fleet and Freight Management

• incident information - 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:
  • incident_data_for_cvo
  
  
• road network conditions - 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_data_for_cvo
  
  
• route plan - Tailored route provided by ISP in response to a specific request.
  Data Flows:
  • cv_route
  • cf_route
  
  
• toll data - Current toll schedules for different types of vehicles as well as advanced toll payment information.
  Data Flows:
  • cvo_advanced_toll_payment_information
  • toll_price_for_cvo
  
  

Information Service Provider > ISP Operator

• ISP operations information presentation - 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-trip_planning_data
  • tispo-route_selection_parameters
  • tispo-data_collection_parameters
  • tispo-business_directory_service_operator_information
  • tispo-archive_status
  • tispo-trip_planning_parameters
  • tispo-traveller_data_collected
  • tispo-traveller_information_parameters
  • tispo-traveller_services_data
  • tispo-trav_info_equip_status
  
  

Information Service Provider > Maintenance and Construction Management

• field equipment status - Identification of field equipment requiring repair and known information about the associated faults.
  Data Flows:
  • field_equipment_status_from_isp
  
  
• road network environmental probe data - 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:
  • env_probe_info_from_isp_for_maint
  
  
• transportation information for operations - 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:
  • transportation_information_for_maint_operations
  
  

Information Service Provider > Map Update Provider

• map update request - Request for a map update which could include a new underlying map or map layer updates.
  Data Flows:
  • tmup-request_info_provider_map_update
  
  

Information Service Provider > Media

• traveller information for media - General traveller information regarding incidents, unusual traffic conditions, transit issues, or other advisory information that has been desensitized and provided to the media.
  Data Flows:
  • tm-traffic_information
  • tm-transit_vehicle_deviations
  • tm-traveller_information_request
  • tm-incident_information
  
  

Information Service Provider > Meteorological Service Provider

• road network environmental probe data - 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:
  • tmsp-env_probe_info_from_isp
  
  
• transportation weather information request - 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:
  • tmsp-trans_weather_info_request
  
  

Information Service Provider > Multimodal Transportation Service Provider

• multimodal information request - Information request for alternate mode transportation providers such as train, ferry, air and bus.
  Data Flows:
  • tmtsp-confirm_multimodal_service
  • tmtsp-ferry_services_request
  • tmtsp-non_motorized_services_request
  • tmtsp-rail_services_request
  • tmtsp-air_services_request
  
  

Information Service Provider > National Meteorological Service

• road network environmental probe data - 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:
  • tnms-env_probe_info_from_isp
  
  

Information Service Provider > Other ISP

• ISP coordination - Coordination and exchange of transportation information between centres. This flow allows a broad range of transportation information collected by one ISP to be redistributed to many other ISPs and their clients.
  Data Flows:
  • toisp-data_supply
  • toisp-emergency_data
  • toisp-misc_traveller_information
  • toisp-multimodal_data
  • toisp-price_data
  • toisp-request_data
  • toisp-traffic_data
  • toisp-transit_data
  
  

Information Service Provider > Parking Management

• parking lot data request - 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_lot_price_data_request
  • parking_lot_static_information_request_by_isp
  • advanced_other_charges_request
  • parking_lot_dynamic_information_request_by_isp
  • parking_lot_data_request
  • advanced_traveller_charges_request
  
  
• parking reservations request - Reservation request for parking lot.
  Data Flows:
  • parking_lot_reservation_request
  
  

Information Service Provider > Personal Information Access

• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • traveller_personal_broadcast_weather_data
  • traveller_personal_broadcast_traffic_data
  • traveller_personal_broadcast_parking_data
  • traveller_personal_broadcast_incident_information
  • traveller_personal_broadcast_transit_data
  • traveller_personal_broadcast_event_information
  • traveller_personal_broadcast_border_data
  • traveller_personal_broadcast_multimodal_data
  • traveller_personal_broadcast_price_data
  
  
• business directory information - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveller.
  Data Flows:
  • traveller_personal_transaction_confirmation
  • traveller_personal_business_directory_service_data
  
  
• emergency traveller information - 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, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • traveller_personal_emergency_traveller_information
  • traveller_personal_transportation_system_status
  • traveller_personal_evacuation_traveller_information
  • traveller_personal_wide_area_alert_information
  
  
• interactive traveller information - Traveller information provided in response to a traveller 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:
  • traveller_personal_interactive_incident_information
  • traveller_personal_interactive_traffic_data
  • traveller_personal_interactive_transit_data
  • traveller_personal_interactive_parking_data
  • traveller_map_update_payment_response
  • traveller_personal_interactive_multimodal_data
  • traveller_personal_interactive_weather_data
  • traveller_personal_interactive_event_information
  • traveller_personal_interactive_border_data
  • traveller_personal_interactive_price_data
  • traveller_personal_display_update_payment_response
  
  
• traveller alerts - Traveller information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveller. Relevant alerts are provided based on traveller-supplied profile information including trip characteristics and preferences.
  Data Flows:
  • traveller_personal_parking_alert
  • traveller_personal_multimodal_alert
  • traveller_personal_transit_alert
  • traveller_personal_weather_alert
  • traveller_personal_border_alert
  • traveller_personal_traffic_alert
  • traveller_personal_event_alert
  • traveller_personal_incident_alert
  
  
• trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
  Data Flows:
  • traveller_personal_trip_information
  • traveller_personal_payment_confirmation
  • traveller_guidance_route
  
  

Information Service Provider > Remote Traveller Support

• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • traveller_broadcast_multimodal_data
  • traveller_broadcast_event_information
  • traveller_broadcast_border_data
  • traveller_broadcast_weather_data
  • traveller_broadcast_traffic_data
  • traveller_broadcast_incident_information
  • traveller_broadcast_parking_data
  • traveller_broadcast_price_data
  • traveller_broadcast_transit_data
  
  
• business directory information - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveller.
  Data Flows:
  • traveller_transaction_confirmation
  • traveller_business_directory_service_data
  
  
• emergency traveller information - 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, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • traveller_wide_area_alert_information
  • traveller_transportation_system_status
  • traveller_evacuation_traveller_information
  • traveller_emergency_traveller_information
  
  
• interactive traveller information - Traveller information provided in response to a traveller 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:
  • traveller_interactive_incident_information
  • traveller_interactive_transit_data
  • traveller_interactive_traffic_data
  • traveller_interactive_price_data
  • traveller_interactive_weather_data
  • advanced_tolls_and_charges_roadside_confirm
  • traveller_interactive_event_information
  • traveller_interactive_multimodal_data
  • traveller_interactive_parking_data
  • traveller_interactive_border_data
  
  
• trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
  Data Flows:
  • traveller_payment_confirmation
  • traveller_trip_information
  
  

Information Service Provider > Roadway Subsystem

• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • field_broadcast_traffic_data
  • field_broadcast_incident_information
  • field_broadcast_multimodal_data
  • field_broadcast_event_information
  • field_broadcast_border_data
  • field_broadcast_weather_data
  • field_broadcast_transit_data
  • field_broadcast_price_data
  • field_broadcast_parking_data
  
  
• emergency traveller information - 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, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • field_transportation_system_status
  • field_evacuation_traveller_information
  • field_wide_area_alert_information
  • field_emergency_traveller_information
  
  

Information Service Provider > Shelter Providers

• emergency traveller information - 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, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • tsp-evacuation_traveller_information
  
  

Information Service Provider > Telecommunications System for Traveller Information

• voice-based alert notification - 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 traveller information.
  Data Flows:
  • ttsti-telecomm_alert_notification
  • traveller_telecomm_wide_area_alert_information
  
  
• voice-based traveller information - Traveller information sent to the telecommunications systems for traveller information terminator. This flow may represent the bulk transfer of traveller information, including traffic conditions, incident information, transit information and weather and road condition information. It may be specially formatted for voice-based traveller information.
  Data Flows:
  • ttsti-telecomm_caller_traveller_information
  • ttsti-telecomm_batch_regional_traveller_information
  
  

Information Service Provider > Toll Administration

• toll data request - 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:
  • toll_price_data_request
  • advanced_traveller_tolls_request
  • advanced_other_tolls_request
  
  

Information Service Provider > Traffic Management

• fare and price information - Current transit, parking, and toll fee schedule information.
  Data Flows:
  • parking_lot_charge_details
  • transit_fare_details
  • toll_price_details
  
  
• logged vehicle routes - 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:
  • current_transit_routes_use
  • logged_special_vehicle_route
  • special_vehicle_priority_routing
  • route_segment_use_prediction
  • current_other_routes_use
  
  
• road network traffic probe data - Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions.
  Data Flows:
  • current_road_network_use
  • traffic_probe_info_from_isp_for_traffic
  
  
• transportation information for operations - 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:
  • transportation_information_for_traffic_operations
  
  

Information Service Provider > Transit Management

• demand responsive transit request - Request for paratransit support.
  Data Flows:
  • paratransit_trip_request
  
  
• selected routes - Routes selected based on route request criteria.
  Data Flows:
  • transit_trip_confirmation
  • paratransit_service_confirmation
  • advanced_tolls_and_charges_vehicle_confirm
  
  
• transit information request - 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:
  • advanced_traveller_fares_request
  • transit_fare_data_request
  • transit_services_guidance_request
  • advanced_other_fares_request
  
  
• transit trip request - Request for a transit trip plan that is responsive to traveller requirements such as schedule, cost, or duration.
  Data Flows:
  • transit_trip_request
  
  
• transportation information for operations - 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:
  • transportation_information_for_transit_operations
  
  

Information Service Provider > Vehicle

• broadcast traveller information - General traveller information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveller information.
  Data Flows:
  • vehicle_broadcast_event_information
  • vehicle_broadcast_incident_information
  • vehicle_broadcast_multimodal_data
  • vehicle_broadcast_parking_data
  • vehicle_broadcast_price_data
  • vehicle_broadcast_weather_data
  • link_and_queue_data
  • vehicle_broadcast_transit_data
  • vehicle_broadcast_traffic_data
  • vehicle_broadcast_border_data
  
  
• business directory information - Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveller.
  Data Flows:
  • vehicle_transaction_confirmation
  • vehicle_business_directory_service_data
  
  
• emergency traveller information - 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, traveller services and shelter information, and reentry times and instructions.
  Data Flows:
  • vehicle_wide_area_alert_information
  • vehicle_emergency_traveller_information
  • vehicle_transportation_system_status
  • vehicle_evacuation_traveller_information
  
  
• interactive traveller information - Traveller information provided in response to a traveller 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_fares_response
  • vehicle_interactive_border_data
  • vehicle_interactive_event_information
  • vehicle_interactive_incident_information
  • advanced_fares_and_charges_response
  • vehicle_interactive_parking_data
  • vehicle_interactive_price_data
  • driver_map_update_payment_response
  • driver_display_update_payment_response
  • vehicle_interactive_transit_data
  • vehicle_interactive_traffic_data
  • vehicle_interactive_weather_data
  • vehicle_interactive_multimodal_data
  
  
• traveller alerts - Traveller information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveller. Relevant alerts are provided based on traveller-supplied profile information including trip characteristics and preferences.
  Data Flows:
  • vehicle_parking_alert
  • vehicle_traffic_alert
  • vehicle_incident_alert
  • vehicle_transit_alert
  • vehicle_multimodal_alert
  • vehicle_border_alert
  • vehicle_event_alert
  • vehicle_weather_alert
  
  
• trip plan - A travel itinerary identifying a route and associated traveller information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.
  Data Flows:
  • vehicle_trip_information
  • vehicle_guidance_route
  • vehicle_payment_confirmation
  
  

ISP Operator > Information Service Provider

• ISP operator inputs - 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-request_traveller_service_map_update
  • fispo-trip_planning_parameters_update
  • fispo-data_collection_parameters_update
  • fispo-data_collection_parameters_request
  • fispo-request_trip_planning_map_update
  • fispo-request_other_routes_selection_map_data_update
  • fispo-traveller_information_parameters_request
  • fispo-trip_planning_parameters_request
  • fispo-request_route_selection_map_data_update
  • fispo-traveller_information_parameters_update
  • fispo-route_selection_parameters_request
  • fispo-route_selection_parameters_update
  • fispo-trav_info_equip_status_request
  • fispo-traveller_data_collection_request
  • fispo-business_directory_service_operator_inputs
  • fispo-request_data_collection_map_update
  
  

Maintenance and Construction Management > Information Service Provider

• current asset restrictions - 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:
  • asset_restrictions_for_info_provider
  
  
• equipment maintenance status - Current status of field equipment maintenance actions.
  Data Flows:
  • field_equip_maint_status_for_isp
  
  
• maint and constr work plans - 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:
  • m_and_c_work_plans_for_info_provider
  
  
• road weather information - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
  Data Flows:
  • road_weather_info_for_isp
  
  
• roadway maintenance status - Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
  Data Flows:
  • roadway_maint_status_for_info_provider
  
  
• work zone information - 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:
  • work_zone_info_for_isp
  • work_zone_images_for_isp
  
  

Map Update Provider > Information Service Provider

• map updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
  Data Flows:
  • fmup-info_provider_map_data
  
  

Media > Information Service Provider

• external reports - 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:
  • fm-incident_details
  • fm-traveller_information
  
  

Meteorological Service Provider > Information Service Provider

• transportation weather information - 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:
  • fmsp-surface_trans_weather_forecasts
  • fmsp-surface_trans_weather_observations
  
  

Multimodal Transportation Service Provider > Information Service Provider

• multimodal information - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
  Data Flows:
  • fmtsp-transit_transfer_clusters
  • fmtsp-rail_services
  • fmtsp-non_motorized_services
  • fmtsp-multimodal_service_confirmation
  • fmtsp-ferry_services
  • fmtsp-air_services
  
  

National Meteorological Service > Information Service Provider

• qualified environmental conditions data - 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:
  • fnms-env_sensor_data_for_isp
  
  
• volume weather information - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
  Data Flows:
  • fnms-weather_forecasts
  • fnms-current_weather_observations
  
  

Other ISP > Information Service Provider

• ISP coordination - Coordination and exchange of transportation information between centres. This flow allows a broad range of transportation information collected by one ISP to be redistributed to many other ISPs and their clients.
  Data Flows:
  • foisp-traffic_data
  • foisp-emergency_data
  • foisp-misc_traveller_information
  • foisp-transit_data
  • foisp-multimodal_data
  • foisp-data_supply
  • foisp-price_data
  • foisp-request_data
  
  

Parking Management > Information Service Provider

• parking information - General parking information and status, including current parking availability.
  Data Flows:
  • static_parking_information_for_isp
  • parking_lot_availability
  • parking_lot_price_data
  • dynamic_parking_information_for_isp
  
  
• parking lot reservation confirmation - Confirmation for parking lot reservation.
  Data Flows:
  • parking_lot_reservation_confirm
  • advanced_traveller_charges_confirm
  • advanced_other_charges_confirm
  
  

Personal Information Access > Information Service Provider

• business directory request - 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:
  • traveller_personal_transaction_request
  • traveller_personal_payment_information_for_bd
  • traveller_personal_business_directory_service_data_request
  
  
• emergency traveller information request - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
  Data Flows:
  • traveller_personal_emergency_information_request
  
  
• traveller profile - Information about a traveller including equipment capabilities, personal preferences, and traveller alert subscriptions.
  Data Flows:
  • traveller_personal_profile
  • traveller_personal_alert_subscriptions
  
  
• traveller request - A request for traveller 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:
  • traveller_personal_information_request
  • traveller_map_update_payment_request
  • traveller_personal_display_update_payment_request
  
  
• trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
  Data Flows:
  • traveller_personal_payment_information
  • traveller_personal_trip_confirmation
  • traveller_route_accepted
  
  
• trip request - 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:
  • traveller_personal_trip_request
  • traveller_route_request
  
  

Remote Traveller Support > Information Service Provider

• business directory request - 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:
  • traveller_transaction_request
  • traveller_business_directory_service_data_request
  • traveller_payment_information_for_bd
  
  
• emergency traveller information request - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
  Data Flows:
  • traveller_emergency_information_request
  
  
• traveller request - A request for traveller 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:
  • advanced_tolls_and_charges_roadside_request
  • traveller_information_request
  
  
• trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
  Data Flows:
  • traveller_payment_information
  • traveller_trip_confirmation
  
  
• trip request - 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:
  • traveller_trip_request
  
  

Roadway Subsystem > Information Service Provider

• environmental probe data - 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:
  • vehicle_env_probe_data_for_isp
  • vehicle_env_probe_status_for_isp
  
  
• short range communications status - Status of the short range communications equipment including the current state or mode of operation and the current equipment status.
  Data Flows:
  • trav_info_equip_status_for_isp_operator
  
  
• traffic probe data - 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:
  • vehicle_traffic_probe_status_for_isp
  • vehicle_traffic_probe_data_for_isp
  
  

Shelter Providers > Information Service Provider

• shelter information - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
  Data Flows:
  • fsp-shelter_information_to_travellers
  
  

Telecommunications System for Traveller Information > Information Service Provider

• voice-based traveller request - The electronic traveller information request from the telecommunications systems for traveller information terminator. It may be specifically formatted for voice-based traveller 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:
  • ftsti-telecomm_caller_request
  • ftsti-telecomm_batch_regional_info_request
  
  

Toll Administration > Information Service Provider

• toll data - Current toll schedules for different types of vehicles as well as advanced toll payment information.
  Data Flows:
  • advanced_traveller_tolls_confirm
  • advanced_other_tolls_confirm
  • toll_price_data
  
  
• toll probe data - 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:
  • toll_probe_data_for_isp
  
  

Traffic Management > Information Service Provider

• incident information - 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:
  • traffic_incident_data_for_isp
  • planned_events
  
  
• road network conditions - 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:
  • current_road_network_state
  • traffic_data_for_isp
  • reversible_lane_signal_state_for_freeways
  • reversible_lane_signal_state_for_roads
  • roadway_detours_and_closures_for_isp
  • link_data_for_guidance
  • traffic_road_weather_data_for_isp
  • prediction_data
  • current_highway_network_state
  
  

Transit Management > Information Service Provider

• demand responsive transit plan - Plan regarding overall demand responsive transit schedules and deployment.
  Data Flows:
  • paratransit_personal_schedule
  
  
• emergency transit schedule information - 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_evacuation_data_for_isp
  
  
• transit and fare schedules - Transit service information including routes, schedules, and fare information.
  Data Flows:
  • transit_fare_data_for_isp
  • transit_fare_data
  • transit_services_for_isp
  • transit_services_for_guidance
  • transit_transfer_point_list
  
  
• transit incident information - Information on transit incidents that impact transit services for public dissemination.
  Data Flows:
  • transit_incident_data
  
  
• transit probe data - 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_probe_data_for_isp
  
  
• transit request confirmation - Confirmation of a request for transit information or service.
  Data Flows:
  • advanced_traveller_fares_confirm
  • advanced_other_fares_confirm
  • advanced_tolls_and_charges_vehicle_request
  
  
• transit schedule adherence information - Dynamic transit schedule adherence and transit vehicle location information.
  Data Flows:
  • transit_vehicle_deviations_details
  
  
• transit trip plan - An origin-destination transit trip that may involve multiple modes and connections.
  Data Flows:
  • individual_transit_trip_plan
  
  

Vehicle > Information Service Provider

• business directory request - 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:
  • vehicle_transaction_request
  • vehicle_payment_information_for_bd
  • vehicle_business_directory_service_data_request
  
  
• emergency traveller information request - Request for alerts, evacuation information, and other emergency information provided to the traveling public.
  Data Flows:
  • vehicle_emergency_information_request
  
  
• environmental probe data - 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:
  • env_probe_data_from_vehicle
  
  
• traffic probe data - 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:
  • traffic_probe_data_from_vehicle
  • guidance_probe_data_from_vehicle
  
  
• traveller profile - Information about a traveller including equipment capabilities, personal preferences, and traveller alert subscriptions.
  Data Flows:
  • vehicle_alert_subscriptions
  • vehicle_profile
  
  
• traveller request - A request for traveller 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:
  • vehicle_information_request
  • advanced_tolls_and_fares_request
  • driver_display_update_payment_request
  • advanced_fares_and_charges_request
  • driver_map_update_payment_request
  
  
• trip confirmation - Acknowledgement by the driver/traveller of acceptance of a trip plan with associated personal and payment information required to confirm reservations.
  Data Flows:
  • vehicle_guidance_route_accepted
  • vehicle_trip_confirmation
  • vehicle_payment_information
  
  
• trip request - 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:
  • vehicle_trip_request
  • vehicle_route_request