• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

6.1.1: Provide Trip Planning Information to Traveler

This process shall obtain all the information needed to fulfill the traveler's request for a trip. The process shall support the request for trips that require the use of one or more modes of transport, and shall use the preferences and constraints specified by the traveler in the trip request, plus data from the store of trip planning parameters, to select the most appropriate modes. It shall send details of the trip requirements to the specialized processes that provide route information for the different modes of transport. When route data is received back from these processes, this process shall ensure that the whole trip is covered by one coherent route for which all the data such as costs, arrival times, and modal (and intra-modal) transfer points are known. The information provided to the traveler by the process shall be sufficient to enable the traveler to understand the routing, modes and cost of the trip. The trip information shall be stored for possible use in subsequent trip confirmation. The process also includes parking lot data. This data is used in transactions requiring electronic payment of parking lot services, as well as for a traveler making a parking lot reservation. This process shall exchange all input and output data from and to the traveler with the appropriate traveler interface process. The traveler shall send parking lot data, traveler trip requests, and traveler current condition requests to the archival process.

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

This process is associated with the following application objects:

• TIC Corridor Decision Support System
• TIC Dynamic Ridesharing
• TIC Trip Planning

This process is associated with the following data flows:

• incident_information_for_trip_planning - In
• individual_transit_trip_plan - In
• multimodal_data_for_trip_planning - In
• multimodal_data_request_from_trip_planning - Out
• paratransit_personal_schedule - In
• paratransit_route_request - In
• paratransit_route_response - Out
• paratransit_trip_request - Out
• parking_data_for_trip_planning - In
• parking_data_request_from_trip_planning - Out
• price_data_for_trip_planning - In
• price_data_request_from_trip_planning - Out
• profiles_for_trip_planning - In
• rideshare_response - In
• supplied_route - In
• traffic_data_for_trip_planning - In
• traffic_data_request_from_trip_planning - Out
• transit_data_for_trip_planning - In
• transit_data_request_from_trip_planning - Out
• transit_trip_confirmation - Out
• transit_trip_request - Out
• traveler_personal_trip_information - Out
• traveler_personal_trip_request - In
• traveler_rideshare_request - Out
• traveler_trip_information - Out
• traveler_trip_request - In
• trip_information - Out
• trip_planning_parameters - In
• trip_planning_requests_for_archive - Out
• trip_requests_for_personnel - Out
• trip_route_request - Out
• vehicle_trip_information - Out
• vehicle_trip_request - In
• weather_data_for_trip_planning - In
• weather_data_request_from_trip_planning - Out