4.2.3: Manage Transit Archive Data

This process shall obtain transit passenger and deployment data, traveler payment transaction data, transit emergency data, transit security data, maintenance and personnel data, and distribute it to the Manage Archive Data function. This process shall receive and respond to requests from the Manage Archived Data process for either a catalog of the data contained within the transit data stores or for the data itself. Additionally, this process shall be able to produce sample products of the data available. As data is received into this process, quality control metrics shall be assigned. The appropriate meta-data shall be generated and stored along with the data. The process shall run when a request for data is received from an external source, or when fresh data is received.

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

This process is associated with the following functional objects:

• Transit Center Data Collection

This process is associated with the following data flows:

• bad_transit_collected_fare_payment
• bad_transit_roadside_fare_payment
• bad_transit_vehicle_fare_payment
• ftrop-archive_commands
• paratransit_service_data_for_archive
• transit_archive_data
• transit_archive_request
• transit_archive_status
• transit_emergency_data_for_archive
• transit_fare_transactions
• transit_incident_info_for_archive
• transit_operational_data_for_archive
• transit_route_assign_for_archive
• transit_services_for_deployment
• transit_technician_info
• transit_vehicle_data_for_archive
• transit_vehicle_maintenance_info
• transit_vehicle_operator_data_for_archive
• traveler_payments_transactions
• ttrop-archive_status