F8.6.4 Provide Interface to Other Transport Modes

Header Image
Project:
F8.6.4 Provide Interface to Other Transport Modes : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 17.08.2021 20:31:29
Modified: 17.12.2021 11:05:01
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to communicate and exchange data objects with one or more Multi-Modal Systems that manage the operation of other modes of transport, e.g. railways, ferries and air freight.<br/>(2) The ability to send data objects provided by other functionality and containing the expected time of arrival (ETA) of the Freight Vehicle that is carrying the Freight Transport Load Item(s) to the system managing the appropriate other mode of transport.<br/>(3) The ability to update the data objects sent in (2) above using data objects provided to it by the Freight Vehicle position monitoring functionality.<br/>(4) The ability to send data objects to the appropriate Multi-Modal System to indicate that the Freight Vehicle is ready for the Freight Transport Load Item(s) it is carrying to be moved by the other mode of transport.<br/>(5) The ability to provide the current status of all other modes of transport with which the system has connections for use by other functionality even if they are not involved in the implementation of any active Freight Transport Execution Plans.<br/>(6) The ability to respond to requests for the provision of alternative services from other modes of transport, which may not be the same modes as those specified in the Freight Transport Execution Plan that is being implemented by sending requests to the appropriate Multi-Modal System(s) and forwarding the response(s).<br/>(7) The ability to generate data objects containing instructions about where to pick up Freight Transport Load Items that have been delivered by other modes of transport and send them to the functionality that provides the interface with the Freight Vehicle Driver.<br/>(8) The ability to provide to other functionality the current status of the movement of Freight Transport Load Items by other modes of transport when provided by the multi-modal systems.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mffo_other_mode_current_FTLI_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tmms.omfs-implement_FTLI_move
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_other_mode_service_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F8.6 Provide Freight Transport Service
FRAME_High_Level_Function «component of»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tmms.omfs-alternative_servce_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_alternative_services_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_driver_instructions_for_other_mode_transfer
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» fmms.omfs-current_service_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_eta_for_other_mode
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fmms.omfs-FTLI_move_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fmms.omfs-alternative_servce_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_request_alternative_services
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.3
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_pta_for_other_mode
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 FV eta for other mode data flow from the Implement FTEP function and the FV pta for other mode data flow from the Monitor FTEP implementation function;<br/>(b) when either of the data flows in (a) are received and their content indicates that the Freight Vehicle is about to arrive at the point where the FTLI can be transferred to an other non-road based mode of transport, send the implement FTLI move data flow to the appropriate Multi-Modal System Terminator;<br/>(c) as a result of (a) or (b), continuously monitor for receipt of the FTLI move status data flow from the Multi-Modal System Terminator;<br/>(d) when the data flow in (c) is received, check its contents and if this shows that the FTLI is about to need collecting from the other mode of transport, include the details in the driver instructions for other mode collection data flow and send it to the Provide Freight Vehicle Driver Interface function;<br/>(e) always continuously monitor for receipt of the current service status from the Multi-Modal System Terminator regardless of the number (if any) of FTEP's being implemented at any moment in time;<br/>(f) when the data flow in (e) is received, send its contents to the Implement FTEP function in the other mode service status data flow;<br/>(g) if there are any active FTEP's that need to use other non-road based modes of transport, continuously monitor for receipt of the request alternative services data flow from the Provide FTOM Interface for FTEP Monitoring function;<br/>(h) when the data flow in (g) is received, send its contents to the Multi-Modal System Terminator in the alternative service request data flow and monitor for receipt of the alternative service response data flow;<br/>(i) when the data flow in (h) is received, send its content to the Provide FTOM Interface for FTEP Monitoring function in the alternative services response data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0