• 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.2.4: Collect Multimodal Data

This process shall collect data about services, including transfer points, that are available to travelers from multimodal transportation service providers. These suppliers shall be those that provide travel services that are not part of regular transit or demand responsive transit operations, e.g., suppliers of bicycle and pedestrian facilities and services and heavy rail operators, and may not involve surface transportation, e.g., ferry and airline operations. Data quality checks shall be performed on all collected data. The process shall provide data formatted for use as part of a traveler's multimodal trip, and shall support subsequent confirmation of any portion provided by the Multimodal Transportation Service Provider. The process shall provide the data to the broadcast traveler information application and to applications that provide traveler information to other operations centers. Upon request from the interactive traveler information application the process shall provide all or some requested subset of the multimodal traveler data. Upon receipt of traveler information alert subscriptions, this process shall output relevant multimodal service (e.g., air, ferry, rail) alerts. The process shall maintain a store of data collected from the multimodal transportation service provider. The process shall maintain a store of multimodal service details that have been requested as part of the trip planning application. This process shall exchange information with Other Information Service Providers to allow one ISP to act as a wholesaler and provide information to other ISPs. The process shall select the appropriate subset of data which will be sent to each ITS application or entity that is requesting data.
The process shall provide all of the received information to the ISP Operator Interface process and receive the data collection parameters (to define exactly what data shall be retrieved as a result of each request) from the operator interface process.

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

This process is associated with the following application objects:

• TIC Connected Vehicle Traveler Info Distribution
• TIC Data Collection

This process is associated with the following data flows:

• fmtsp-air_services - In
• fmtsp-ferry_services - In
• fmtsp-non_motorized_services - In
• fmtsp-rail_services - In
• fmtsp-transit_transfer_clusters - In
• fotic-multimodal_data - In
• multimodal_data_for_alerts - Out
• multimodal_data_for_broadcast - Out
• multimodal_data_for_centers - Out
• multimodal_data_for_interactive - Out
• multimodal_data_for_route_selection - Out
• multimodal_data_for_trip_planning - Out
• multimodal_data_request_for_alerts - In
• multimodal_data_request_from_interactive - In
• multimodal_data_request_from_route_selection - In
• multimodal_data_request_from_trip_planning - In
• multimodal_service_details_data - In
• multimodal_service_details_data - Out
• multimodal_traveler_data - In
• multimodal_traveler_data - Out
• multimodal_traveler_data_collected_for_personnel - Out
• multimodal_traveler_data_collection_parameters - In
• tmtsp-air_services_request - Out
• tmtsp-ferry_services_request - Out
• tmtsp-non_motorized_services_request - Out
• tmtsp-rail_services_request - Out
• totic-multimodal_data - Out