4.1.5.2: Manage Transit Vehicle Deviations
This process shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large numbers of vehicles. The process shall generate the necessary corrective actions which may involve more than the vehicles concerned and more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by the Manage Traffic function, the premature termination of some services, etc. In addition, this process will receive roadway maintenance status and work plan information from the Manage Maintenance and Construction function, and shall respond to that function with feedback regarding the work plan. Event plans from Event Promoters shall be received and confirmed. All corrective actions generated by this process shall be subject to the approval of the transit operations personnel before being implemented. The process shall generate transit signal priority business rules that are provided to the transit vehicle. Confirmation that the requested overall priority has been given by the Manage Traffic function shall be received by the process. This process shall provide the interface through which multimodal transportation service providers are informed of transit vehicle schedule deviations. The process shall provide the output in a form that enables adjustments to be made to any connecting services being provided by the multimodal supplier so that travelers are not inconvenienced by the deviations. In response to requests for deviation pertaining to a transit connection protection this process shall issue wait requests to transit vehicles that may receive a connecting traveler if that traveler is on a late arriving vehicle and the transfer falls within a predetermined threshold for waiting.
This process is associated with the Transit Management Center physical object.
This process is associated with the following functional objects:
- Transit Center Connection Protection
- Transit Center Fixed-Route Operations
- Transit Center Passenger Counting
This process is associated with the following data flows:
- approved_corrective_plan
- connection_protection_info_for_rideshare
- deviation_response_to_protect_connection
- feps-event_data_for_transit
- ftrop-approved_corrections
- incident_response_log_for_transit
- m_and_c_plan_feedback_from_transit
- m_and_c_work_plans_for_transit
- operations_input_for_deviations
- planned_events
- prediction_data
- request_for_deviation_to_protect_connection
- roadway_maint_status_for_transit
- signal_priority_rules
- tamtc-transit_arrival_deviations
- tevp-event_confirmation_from_transit
- tevp-transit_updates_for_event
- transit_highway_overall_priority
- transit_highway_priority_given
- transit_lane_use_given
- transit_ramp_overall_priority
- transit_ramp_priority_given
- transit_restricted_lane_priority
- transit_road_overall_priority
- transit_road_priority_given
- transit_services_for_scenarios
- transit_stop_requests_from_center
- transit_vehicle_connection_instructions
- transit_vehicle_connection_request_mode
- transit_vehicle_connection_response
- transit_vehicle_connection_response_constraints
- transit_vehicle_deviation_update
- transit_vehicle_deviations_from_schedule
- transit_vehicle_location_for_deviation
- transit_vehicle_passenger_connection_request
- transit_vehicle_reassignment_request
- ttrop-proposed_corrections
- vehicle_correction_actions