F4.4.10 Provide PT Operator Fleet Control Interface

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.10 Provide PT Operator Fleet Control Interface

Project:

F4.4 Control PT Fleet

F4.4.10 Provide PT Operator Fleet Control Interface : 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:	{195D05D8-4A51-4d07-BC72-67F1A4D5DC55}
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) A HMI through which the PT Operator can manage the operation of the PT Fleet. (2) The HMI shall enable the PT Operator to set the criteria which is used to decide if and when PT Vehicle or service priority is requested and to request the introduction of additional PT Vehicles. (3) The HMI shall enable the PT Operator to confirm additional PT Vehicles requested by other modes and to request report on the PT Control actions that have been taken. (4) The HMI shall enable the PT Operator to provide data about each PT Vehicle in the fleet so that real-time and historic data can be properly associated with each Vehicle.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_actions_report_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_confirmed_PT_service_change FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_vehicle_real_time_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.pto-actions_report FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.pto-request_for_service_change FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_updated_service_delivery_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_vehicle_historical_details 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_Functional_Area» F4. Manage Public Transport Operations FRAME_Functional_Area «componentof»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» fo.pto-PT_vehicle_static_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_action_report FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-service_change_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.3.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_confirm_PT_service_change FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-change_service_delivery_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-request_actions_report 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 the receipt of the change service delivery criteria, request actions report data flows and PT vehicle static data from the PT operator;<br/>(b) when the first data flow in (a) is received send the changed criteria to the Optimise PT Fleet Control function in the updated service delivery criteria data flow;<br/>(c) when the second data flow in (a) is received send the request actions report data flow to the Optimise PT Fleet Control function;<br/>(d) as a result of (c) continuously monitor for the receipt of the requested action report data flow;<br/>(e) when the data flow in (d) is received, send its contents to the PT operator in the actions report data flow;<br/>(f) continuously monitor for the receipt of the confirm PT service change data flow and when it is received send the request for service change data flow to the PT operator;<br/>(g) when as a result of (f) the service change response data flow is received from the PT operator, out the result in the confirmed PT service change data flow to the Optimise PT Fleet Control function;<br/>(h) when the third data flow in (a) is received, send the data that it contains to the store of Real Time PT Vehicle Status and the store of Historical PT Vehicle Data in the PT vehicle static data for real time use and PT vehicle static data for historic use data flows respectively.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0