F8.6.5 Provide FTOM Interface for FTEP Monitoring

Header Image
Project:
F8.6.5 Provide FTOM Interface for FTEP Monitoring : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 18.08.2021 12:58:54
Modified: 20.12.2021 15:26:07
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to provide an interface through which audio and/or visual information can be exchanged with the Freight Transport Operations Manager.<br/>(2) The ability to convert data objects received from other functionality into audio and/or visual outputs that can be easily understood by the Freight Transport Operations Manager.<br/>(3) The ability to receive audio and/or visual inputs from the Freight Transport Operations Manager and convert them into digital objects that can be sent to other functionality for their interpretation and use.<br/>(4) The ability to alert the Freight Transport Operations Manager to the output of audio and/or visual messages.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_User_Need» 9.11.2.9
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.2.4
FRAME_User_Need «belongsto»
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» mffo_new_incident_response_details
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-other_mode_service_issue
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-other_mode_negotiation_response
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_request_from_FTOM
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_request_alternative_services
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_message_for_Driver
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_incident_responses
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.2.3
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-incident_response_needed
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.2.7
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_FV_status
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-FTEP_progress_report
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_request_incident_response_details
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-requested_FTEP_implementation_record
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft.ftom-message_from_Driver
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_prepare_revised_FTEP
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_request_FTEP_implementation_record
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mffo_FTEP_progress_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-message_for_Driver
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_no_incident_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-request_FTEP_implementation_record
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_vehicle_location_status
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_message_from_Driver
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-request_incident_responses
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 9.11.1.15
FRAME_User_Need «belongsto»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-prepare_revised_FTEP
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_alternative_services_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-incident_responses
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_requested_FTEP_implementation_record
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_FV_status_for_FTOM
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_incident_response_details
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mffo_other_mode_service_issues
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-other_mode_negotation_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-request_FV_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 the message from Driver data flow from the Provide Freight Vehicle Driver Interface function;<br/>(b) when the data flow in (a) is received, output its content in the message from Driver data flow to the Freight Transport Operations Manager Terminator in audio and/or visual form;<br/>(c) continuously monitor for receipt of the request incident responses data flow from the Freight Transport Operations Manager Terminator and, when it is received, send the request to the Manage Incident Response Data Store function in the request incident response details data flow;<br/>(d) as a result of (c), continuously monitor for receipt of the incident response details data flow from the Manage Incident Response Data Store function and, when it is received, output its contents to the Freight Transport Operations Manager Terminator in the requested incident responses data flow;<br/>(e) continuously monitor for receipt of the no incident response data flow from the Manage Incident Response Data Store function and, when it is received , output its contents to the Freight Transport Operations Manager Terminator in the incident response needed data flow;<br/>(f) as a result of (e), continuously monitor for receipt of the incident responses data flow from the Freight Transport Operations Manager Terminator and, when it is received, send its contents to the Manage Incident Response Data Store function in the new incident response details data flow;<br/>(g) continuously monitor for receipt of the message for Driver data flow from the Freight Transport Operations Manager Terminator and, when received, send its contents to the Provide Freight Vehicle Driver Interface function in the message for Driver data flow;<br/>(h) continuously monitor for receipt of the other mode service issues data flow from the Implement FTEP function and, when it is received, output its content in the other mode service issue data flow to the Freight Transport Operations Manager Terminator;<br/>(i) as a result of (h), continuously monitor for receipt of the other mode negotiation request data flow from the Freight Transport Operations Manager Terminator and, when it is received, send its content to the Provide Interface for Other Transport Modes function in the request alternative services data flow;<br/>(j) as a result of (i) continuously monitor for receipt of the alternative services response data flow from the Provide Interface for Other Transport Modes function and, when it is received, output its content to the Freight Transport Operations Manager Terminator in the other mode negotiation response data flow;<br/>(k) continuously monitor for receipt of the prepare revised FTEP data flow from the Freight Transport Operations Manager Terminator and, when it is received, send the request to the Prepare Freight Transport Execution Plan for Implementation Function in the prepare revised FTEP data flow;<br/>(l) continuously monitor for receipt of the request FTEP implementation record data flow from the Freight Transport Operations Manager Terminator and, when it is received, send its contents to the Evaluate FTEP Implementation function in the request FTEP implementation record data flow;<br/>(m) as a result of (l) continuously monitor for receipt of the requested FTEP implementation record data flow from the Evaluate FTEP Implementation function and, when it is received, output its contents to the Freight Transport Operations Manager Terminator in the requested FTEP implementation record data flow;<br/>(n) continuously monitor for receipt of the request FV status data flow from the Freight Transport Operations Manager Terminator and, when it is received, send the FV status request for FTOM data flow to the Calculate FTEP Implementation Status function;<br/>(o) as a result of (p)  continuously monitor for receipt of the FV status for FTOM data flow from the Calculate FTEP Implementation Status function and, when it is received, output its content to the Freight Transport Operations Manager Terminator in the requested FV status data flow;<br/>(p) continuously monitor for receipt of the FTEP progress status from the Calculate FTEP Implementation Status function and, when it is received, output its content to the Freight Transport Operations Manager Terminator in the FTEP progress report data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0