F4.4.5 Optimise PT Fleet Control

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.4 Control PT Fleet / F4.4.5 Optimise PT Fleet Control

Project:

F4.4 Control PT Fleet

F4.4.5 Optimise PT Fleet Control : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:32
Modified:	08.09.2021 11:24:41

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{F9D068DE-95DB-49d5-88F0-975A9FEA97C5}
Appears In:	DFD F4.4 Control PT Fleet, Functional Tree of Area F4 Manage Public Transport Operations

This Function shall be capable of providing the following facilities: (1) The ability to optimise actions to improve the reliability and schedule adherence of PT services, due to such events as changes in Passenger numbers (e.g. high demand), PT Vehicle breakdown and incidents that have occurred that affect the flow of traffic through the road network. (2) The ability to change the current way that PT Services are being operated, including sending revised instructions to PT Vehicle Drivers, and introducing extra PT Vehicles to support those already delivering the current services. (3) The ability to send to other functionality requests PT Vehicle priority for late running services or individual PT Vehicles and additional Vehicles added to services when Traveller demand is high. (4) The ability to exchange data with the functionality providing the HMI that enables the PT Operator to monitor and manage PT service delivery. (5) The ability to exchange data about PT Service operation with other instances of PT management functionality, (6) The ability to interact through an interface function with other transport modes to enable co-operation on the maintenance and variation in PT Services (7) The ability to use both real-time and historic PT Vehicle data in its actions and to record service information in the Store of historic PT Vehicle data.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Functional_Area» F4. Manage Public Transport Operations FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_other_mode_service_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_PT_service_variations FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_confirm_PT_service_change FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_control_actions FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_other_mode_service_change_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tors.ptms-control_parameters FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_priority_PT_vehicle_identity FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_change_data_for_vehicles FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_change_response_to_other_mode FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.4 Control PT Fleet FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_additional_PT_vehicle_required FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_control_strategy FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_number_for_priority FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_change_data_for_stops FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_action_report FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_additional_PT_vehicle_available FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_incident_details FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fors.ptms-control_parameters FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_vehicle_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_services_in_operation FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.6.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_other_mode_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_current_PT_vehicle_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_updated_service_delivery_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.3.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_recorded_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 2.1.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_confirmed_PT_service_change FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_actions_report_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_passenger_numbers_at_stop FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_change_request_from_other_mode FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_observed_performance_figures FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_other_mode_service_change_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for receipt of the updated service delivery criteria data flow;<br/>(b) when the data flow in (a) is received, store the data that it contains for internal use within the function and send it to any other instances of this function in the control parameters data flow;<br/>(c) continuously monitor for receipt of the actions report request data flow;<br/>(d) when the data flow in (c) is received collect the data needed from the report from internal data stores that have accumulated the inputs from the data flows containing current PT Vehicle data and recorded data. plus PT Service Plan Data and send it to the Provide PT Operator Interface for Fleet Control function in the requested action report data flow;<br/>(e) when either of the observed performance figures or the passenger numbers at stop data flows is received, store the data for internal use within the function;<br/>(f) when the incident details data flow is received, carryout an assessment of the need for changes in the PT services currently being provided;<br/>(g) if any changes are needed send these to the Provide PT Operator Interface for Fleet Control function in the confirm PT service change data flow;<br/>(h) as a result of (g) monitor for the receipt of the confirmed PT service change data flow and if when it arrives it contains a positive indication, implement the change to the services and use the control actions data flow to get it loaded in the store of Historical PT Vehicle Data;<br/>(i) as part of (h) send details of the revised services to PT vehicles, PT stops and to functionality in the Manage Traffic Functional Area;<br/>(j) if the response in (h) is negative, repeat (f);<br/>(k) analyse the current service performance and if priority is needed for selected PT vehicles, send the service number for priority and priority PT vehicle identity data flows to the Request Vehicle Priority function;<br/>(l) if as part of any of the above, changes are needed to the services provided by other transport modes then send the other mode service change request data flow to the Provide Interface to Other Modes function;<br/>(m) as a result of (l) continuously monitor for the receipt of the other mode service change response data flow;<br/>(n) when the data flow in (m) is received, implement (i) with the details of any service changes;<br/>(o) continuously monitor for the receipt of the service change request from other mode data flow;<br/>(p) when the data flow in (o) is received, determine whether or not the changes can be accommodated and if so repeat (g) to (i), except that if the response is negative repeat the first part of this instruction;<br/>(q) if the response received in (p) was positive sent the service change response to other modes data flow to the Provide Interface to Other Modes function;<br/>(r) if necessary for any of the above, send the request other mode service details data flow to the Provide Interface to Other Modes function and wait for receipt of a response in the other mode services data flow;<br/>(s) if the control parameters data flow is received from another instance of the function, store its contents for local use in those of the above instructions that are appropriate.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0