F4.1.13 Provide Operator Interface for Manage PT Fleet

Header Image
Project:
F4.1.13 Provide Operator Interface for Manage PT Fleet : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:31
Modified: 08.09.2021 11:24:40
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The provision of a suitable HMI through which the PT Operator can monitor and manage the operation of the PT Vehicle fleet.<br/>(2) The ability to request and display through the HMI real-time information about PT Vehicles, including the current locations and predicted arrival times, using digital map data as a background.<br/>(3) The ability to request and display through the HMI data about the performance of the PT Vehicle fleet in the delivery of its services.<br/>(4) The ability to display through the HMI details of alarms raised by PT Passengers at PT Stops.<br/>(5) The ability to display and write, using a suitable HMI, messages that are exchanged with PT Drivers in PT Vehicles.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mpto_calculate_service_performance
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F4.1 Monitor PT fleet
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-historic_information
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-alarms_raised
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-predicted_PT_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Functional_Area» F4. Manage Public Transport Operations
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-communications
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_communications_to_driver
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-performance_figures
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» to.pto-real_time_information
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 10.1.0.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_alarm_at_stop
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.4.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.pto-output_predicted_PT_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_communications_from_driver
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.pto-output_real_time_information
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_calculated_service_performance
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.pto-performance_criteria
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_predicted_PT_vehicle_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.pto-output_historic_information
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 10.2.4.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fo.pto-communications
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_historical_vehicle_information
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_real_time_vehicle_information
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 arrive of the input data flows from the PT Operator;<br/>(b) output any requests for data that has been collected and locally stored by the function using the appropriate output data flows;<br/>(c) if the communications data flow arrives in (a) send its contents to the Collect PT Vehicle Data function in the communications to driver data flow;<br/>(d) if the communications from driver data flow arrives from the Collect PT Vehicle Data function, immediately output its contents to the PT Driver in the communications data flow;<br/>(e) if any of the data flows containing historical or real time vehicle information, plus predicted PT Vehicle data is received, store the data that they contain locally to await an output request from the PT Operator in one of the data flows being continuously monitored in (a);<br/>(f) if the alarm at stop data flow is received, immediately output its contents to the PT Operator in the alarms raised data flow;<br/>(g) if the performance criteria data flow is received from the PT Operator, send the calculate service performance data flow to the Calculate PT Service Performance function and await a response;<br/>(h) when the calculated service performance data flow is received as a result of (g), output its contents to the PT Operator in the performance figures data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0