F8.4.1 Provide Freight Transport User Interface

Header Image
Project:
F8.4.1 Provide Freight Transport User Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 13.08.2021 16:57:29
Modified: 20.12.2021 15:00:48
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) An interface through which the Freight Transport User shall be able to do the following activities:<br/>      (a) Provide data objects for use in the preparation of a Freight Transport Execution Plan that will enable the Freight Transport User to have specified Freight Transport Load Items moved from one location to another;<br/>      (b) Approve the content of a prepared Freight Transport Execution Plan, or request changes using new data objects;<br/>      (c) Request the implementation of a previously prepared Freight Transport Execution Plan;<br/>      (d) Request the status of Freight Transport Load Items being moved by active Freight Transport Execution Plans.<br/>(2) Interface with other functionality in the Manage Freight and Fleet Operations Functional Area to:<br/>      (a) Provide the data objects created from the inputs specified in (1) above; <br/>      (b) Collect data objects needed for the outputs specified in (1) above.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» tft.ftu-requested_FV_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftu-existing_FTEP_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_FTU_approval_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftu-new_FTEP_for_approval
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_request_from_FTU
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.1.8
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F8.4 Manage FTEP Preparation
FRAME_High_Level_Function «component of»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_implement_FTEP
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Function» F8.4.1 Provide Freight Transport User Interface
FRAME_Low_Level_Function «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftu-new_FTEP_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_request_existing_FTEP
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» fft.ftu-implement_FTEP
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftu-new_FTEP_approval_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.9
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.10
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_existing_FTEP_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.8
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_request_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.5
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftu-request_FTLI_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.6
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_for_FTU
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftu-request_FTEP_data
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftu-new_FTEP_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Function» F8.4.1 Provide Freight Transport User Interface
FRAME_Low_Level_Function «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.10.1.1
FRAME_User_Need «served by»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_for_FTU_approval
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 any of the input data flows from the FTU;<br/>(b) when any of the data flows are received in (a), depending on their content, sent it to either the Provide FTOM Interface or FTEP Store Management functions;<br/>(c) as a result of (b) continuously monitor for receipt of either the new FTEP for FTU approval or new FTEP request response data flows from the Provide FTOM Interface function;<br/>(d) when either of the data flows in (c) is received, output its content to the Freight Transport User terminator in either the new FTEP response or new FTEP for approval data flows;<br/>(e) also as a result of (b) continuously monitor for receipt of the data flow existing FTEP data from the FTEP Store Management function;<br/>(f) when the data flow in (e) is received output its content to the Freight Transport User Terminator in the data flow existing FTEP data;<br/>(g) if the data flow from the Provide FTOM Interface function received in (c) shows that, more or corrected, data is needed before a new FTEP can be prepared, enter into a dialogue with the Freight Transport User to obtain that data;<br/>(h) also continuously monitor for receipt of the FV status data flow;<br/>(i) when the data flow in (h) is received, output its content to the Freight Transport User Terminator in the requested FV status data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0