• 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

4.2.3.5: Manage Transit Operational Data Store

This process shall collect transit operational data and load it into a data store for use by the routes and schedules generation processes. The data shall be provided to this process by other processes in the Manage Transit function and shall enable an accurate picture of how routes and schedules are currently operating in terms of the numbers of vehicles that are available, the numbers of passengers that they are carrying, and the numbers of passengers passing through each roadside facility (transit stop).

This process is associated with the Transit Management Center physical object.

This process is associated with the following application objects:

• Transit Center Fare Management
• Transit Center Passenger Counting

This process is associated with the following data flows:

• ftrop-passenger_loading_updates - In
• transit_operational_data - In
• transit_operational_data - Out
• transit_operational_data_for_archive - Out
• transit_operational_data_for_routes - Out
• transit_operational_data_for_schedules - Out
• transit_roadside_passenger_data - In
• transit_roadside_passenger_data_request - Out
• transit_vehicle_assignment_data - In
• transit_vehicle_availability - In
• transit_vehicle_data - In
• transit_vehicle_passenger_data - In
• ttrop-passenger_loading_error - Out