F8.4.3 Provide Freight Transport Operations Manager Interface

Frame Repository / Frame Functional View / Functionality / Functional Area F8 - Manage Freight and Fleet Operations / F8. Manage Freight and Fleet Operations / F8.4 Manage FTEP Preparation / F8.4.3 Provide Freight Transport Operations Manager Interface

Project:

F8.4 Manage FTEP Preparation

F8.4.3 Provide Freight Transport Operations Manager Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	16.08.2021 16:57:45
Modified:	10.12.2021 11:06:40

Project:
Author:	Richard
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{8FBDF54B-6B59-4624-BAA2-0843DE946DB2}
Appears In:	Functional Tree of Functional Area F8 Manage Freight and Fleet Operations, DFD F8.4 Manage FTEP Preparation

This Function shall be capable of providing the following facilities: (1) Provide an interface through which the Freight Transport Operations Manager shall be able to perform the following activities: (a) Manage the creation of new Freight Transport Execution Plans at the request of the Freight Transport User using data objects provide by the User, plus other data objects about relevant statutory regulations and the capabilities of available Freight Vehicles; (b) Initiate the implementation of a previously created Freight Transport Execution Plan when requested by the Freight Transport User; (c) Check the content of a prepared Freight Transport Execution Plan; (d) Review the facilities available at Freight Terminal Areas and include any that are relevant with the data objects that are to be used to prepare a Freight Transport Execution Plan; (e) Provide and review information about the capabilities of available Freight Transport Vehicles and include any that are relevant with the data objects that are to be used to prepare a Freight Transport Execution Plan. (2) Manage the store of Freight Transport Execution Plan details provided by the Freight Transport User to prevent the un-necessary repeat input of common data, e.g. the location from which the Freight Transport User regularly moves Freight Transport Load Items. (3) Manage the store of the capabilities of available Freight Transport Vehicles updating the content as Vehicles are required for use in the requested implementation of Freight Transport Execution Plans.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mffo_load_Freight_Vehicle_capabilities FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.1.3 FRAME_User_Need «belongsto»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_request_FTA_facilities_for_FTOM FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_existing_FTEP FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ttp-FTOM_request_traffic_management_policies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_load_FTEP_preparation_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.2.6 FRAME_User_Need «belongsto»	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» tft.ftom-requested_traffic_management_policies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_prepare_new_FTEP FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_for_FTU_approval FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_save_new_FTEP_to_implement FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_FTOM_FTEP_data_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.1.2 FRAME_User_Need «belongsto»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_request_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_Freight_Vechicle_capabilities FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tft.ftom-prepared_new_FTEP FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_FTA_facilities FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_User_Need» 9.11.1.1 FRAME_User_Need «belongsto»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_read_Freight_Vehicle_capabilities FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.fton-updated_Freight_Vehicle_capabilities FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-request_Freight_Vehicle_capabilities FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_FTOM_FTEP_data_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-prepare_new_FTEP FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom_new_FTEP_checking_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-request_traffic_management_policies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 9.10.1.1 FRAME_User_Need «served by»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-request_existing_FTEP FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_read_FTEP_preparation_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_new_FTEP_FTU_approval_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-route_constraint_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 9.10.1.4 FRAME_User_Need «served by»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fft.ftom-request_FTA_facilities 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» mffo_prepared_new_FTEP FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ftp-FTOM_traffic_management_policies_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mffo_requested_FTA_facilities_for_FTOM 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 new FTEP request data flow from the Provide FTU Interface function;<br/>(b) when the data flow in (a) is received, check its contents and make sure that all the data objects needed to prepare a FTEP are present;<br/>(c) as a result of (b) send the new FTEP request response data flow back to the Provide FTU Interface function, with either an acceptance or a request for the missing data to be provided;<br/>(d) if the response in (c) was "acceptance" then add to the FTEP data that has been provided by the data flow in (b):<br/> - data about available Freight Vehicles extracted from the Freight Vehicle Capabilities Data Store,<br/> - data about route constraints and relevant FTA facilities from the FTEP Preparation Data store,<br/> - data about traffic management policies that have been provided by the Transport Planner;<br/>(e) when (d) is complete, assign a FTEP number to the data and send it to the FTEP Preparation Data store and also to the Prepare FTEP for Implementation function in the prepare new FTEP data flow;<br/>(f) as a result of (e) continuously monitor for receipt of the prepared new FTEP data flow from the Prepare FTEP for Implementation function;<br/>(g) when the data flow in (f) is received, output its contents to the FTOM in the prepared new FTEP data flow and continuously monitor for receipt of the new FTEP checking response data flow;<br/>(h) when the data flow in (g) is received, if it contains "acceptance", send the content to the Provide FTU Interface function in the new FTEP for FTU approval data flow and continuously monitor for receipt of the new FTEP FTU approval response data flow;<br/>(i) if the content of the data flow received in (h) is not "acceptance" then use it to modify the FTEP data and repeat (h) to (g);<br/>(j) if the data flow received from the Provide FTU Interface in (h) is "acceptance" send the FTEP back to the Prepare FTEP for Implementation function in the save new FTEP to implement data flow;<br/>(k) continuously monitor for receipt of the request FTA facilities data flow from the FTOM and when it is received, send its content to the Manage FTA Facilities Data Store function in the request FTA facilities for FTOM data flow;<br/>(l) as a result of (k) continuously monitor for receipt of the requested FTA facilities for FTOM data flow and when it is received add its content to the FTEP Preparation Data Store and output it to the FTOM;<br/>(m) continuously monitor for receipt of the route constraint data flow from the FTOM and when it is received, add its content to the FTEP Preparation Data Store;<br/>(n) continuously monitor for receipt of the updated Freight Vehicle capabilities data flow and when it is received, add its content to the Freight Vehicle Capabilities Data Store;<br/>(o) continuously monitor for receipt of data flows requesting existing FTEP data, or Freight Vehicle capabilities data and when received, extract the requested data from the appropriate Data Store and output it to the FTOM;<br/>(p) continuously monitor for receipt of the request traffic management policies data flow from the FTOM and when received send the request to the Transport Planner in the FTOM request traffic management policies data flow;<br/>(q) as a result of (p) continuously monitor for receipt of the FTOM traffic management policies response data flow and when received send its content to the FTEP Preparation Data Store and output it to the FTOM;<br/>(r) continuously monitor for receipt of the prepare new FTEP data flow and when received extract the specified FTEP data from the FTEP Preparation Data Store and repeat (d) to (h).<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0