F8.7.2 Calculate FTEP Implementation Status

Header Image
Project:
F8.7.2 Calculate FTEP Implementation Status : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 17.08.2021 20:45:29
Modified: 20.12.2021 15:34:01
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to receive from other functionality data objects that show the current status of the Freight Vehicle and equipment on-board that is used to carry and/or load/unload Freight Transport Load Items onto/off the Vehicle.<br/>(2) The ability to process the data objects received in (1) above to create data objects that show the status of the Freight Vehicle and its location, and to send these data objects to other functionality for output to the Freight Transport User and/or Freight Transport Operations Manager, or for, storage and/or analysis.<br/>(3) As part of (2), if the data objects that have been received indicate that an incident has occurred that involved the Freight Vehicle and/or the Freight Transport Load Item(s) it is carrying, create data objects to show this and send them to the appropriate functionality.<br/>(4) As a result of the data objects received in (1) above calculate the expected arrival time (eta) at the next Freight Terminal Area identified in the Freight Transport Execution Plan and if not the same as in the Plan send data objects containing the amended eta to the Freight Terminal Area Facilities Terminator.<br/>(5) As a result of (4) receive data objects from the Freight Terminal Area Facilities Terminator containing its response and inform the appropriate functionality of the need to change the way that the Freight Transport Execution Plan is currently being implemented.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_User_Need» 9.11.2.6
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_for_FTU
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.9
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FTEP_implementation_status_for_record
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FTEP_progress_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.3.4
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.2.8
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.fta-revise_FTEP_eta_reqiuest
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_revised_FTEP_needed
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.8
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_for_FTOM
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.1.15
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.2.9
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_vehicle_incident_found
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.3.3
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.3.2
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.1.5
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.1.11
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F8.7 Monitor Freight Vehicle during FTEP Implementation
FRAME_High_Level_Function «component of»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mffo_FV_status_request_from_FTU
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.fta-revise_FTEP_eta_request_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_vehicle_speed
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_vehicle_location
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_expected_FTEP_implement_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_road_network_location
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_request_from_FTOM
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_vehicle_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_other_mode_current_FTLI_status
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 any of the following data flows from the Collect Data from Freight Vehicle function:<br/>- vehicle speed,<br/>- vehicle location,<br/>- vehicle status,<br/>plus,<br/>- the FV road network location data flow from the Monitor FTEP implementation function,<br/>- the other mode current FTLI status data flow from the Provide Interface to Other Transport Modes function, and<br/>- the expected FTEP implement status from the Implement FTEP function;<br/>(b) whenever any of the first three data flows in (a) are received, load their content (using the content of the road network location data flow each time) into the FTEP implementation status for record data flow and send it to the Evaluate FTEP Implementation function;<br/>(c) in addition to the action in (b), store the content of each data flow locally until updated by the next receipt of the same data flow;<br/>(d) whenever the other mode current FTLI status data flow is received in (a) also load its content into the FTEP implementation status for record data flow and send it to the Evaluate FTEP Implementation function;<br/>(e) whenever the expected FTEP implement status data flow is received in (a) store its content locally until updated by the next receipt of the same data flow and calculate how far the FTEP implementation has deviated from what was expected;<br/>(f) if the deviation in (e) will cause significant delay to arrival of the Freight Transport Load Items at the destination, request the preparation of a revised Freight Transport Execution Plan by sending the revised FTEP needed data flow to the Prepare Freight Transport Execution Plan for Implementation function;<br/>(g) if the deviation in (e) will significantly delay the transfer of the Freight Transport Load Item(s) to another mode of transport, send the revise FTEP eta request data flow to the Freight Terminal Area Terminator;<br/>(h) as a result of (g) monitor for receipt of the revise FTEP eta request response data flow from the Freight Terminal Area Terminator and, if necessary, request the preparation of a revised Freight Transport Execution Plan by sending the revised FTEP needed data flow to the Prepare Freight Transport Execution Plan for Implementation function;<br/>(i) continuously monitor for receipt of the FV status request from FTU data flow from the Provide Freight Transport User Interface function;<br/>(j) when the data flow in (i) is received, obtain the FV status last reported by the vehicle status data flow in (a) and send it in the FV status for FTU data flow to the Provide Freight Transport User Interface function;<br/>(k) continuously monitor for receipt of the FV status request from FTOM data flow from the Provide FTOM Interface for FTEP Monitoring function;<br/>(l) when the data flow in (j) is received, obtain the FV status last reported by the vehicle status data flow in (a) and send it in the FV status for FTOM data flow to the Provide FTOM Interface for FTEP Monitoring function.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0