F5.14.14 Manage Driver Trip Plan Payments

Header Image
Project:
F5.14.14 Manage Driver Trip Plan Payments : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:34
Modified: 21.12.2021 9:43:46
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to take responsibility for enabling the Freight Vehicle Driver or the Freight Transport Operations Manager to make any required payments for the trip planning service and/or make any required advanced payments for services included in the accepted Vehicle Trip Plan.<br/>(2) The ability to communicate directly with the Freight Vehicle Driver to obtain details of the payment mechanism that is to be used and to report on the success of failure of all of the payment transactions.<br/>(3) The ability to repeat all failed transactions for a defined number of times before abandoning the payment process and providing a payment failure response to the Prepare and Revise Trip Plans function.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» tft.ftom-vehicle_trip_planning_booking_mishap
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» td.tpd-request_vehicle_trip_planning_payment
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tft-ftom-request_vehicle_trip_planning_payment
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F5.14 Provide In-vehicle Trip Planning & Implementation
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tfc-request_payment_for_vehicle_trip_planning
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» tfc-vehicle_trip_planning_service_payment_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» td.tpd-vehicle_trip_planning_booking_mishap
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_trip_plan_with_parking_needs
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_trip_plan_payment_failed
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» td.tpd-advanced_payment_for_vehicle_trip_plan
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» fd.tpd-revised_vehicle_trip_plan_booking_choices
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_for_bookings
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fd.tpd-vehicle_trip_plan_booking_approval
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fft.ftom-vehicle_trip_planning_payment
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fd.tpd-vehicle_trip_planning_payment
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ffc-vehicle_trip_planning_service_payment_response
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ffc-payment_for_vehicle_trip_planning_response
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 vehicle trip plan for bookings data flow;<br/>(b) when the data flow in (a) is received, check its contents to see if any payment for the actual trip planning service is needed;<br/>(c) if the answer to the question is (b) is yes, request payment from the Trip Planning Driver or the Freight Transport Operations Manager Terminators in the request vehicle trip planning payment data flow;<br/>(d) as a result of (c) continuously monitor for the receipt of the vehicle trip planning payment data flow from either the Trip Planning Driver or the Freight Transport Operations Manager Terminators;<br/>(e) when the data flow in (d) is received, check for payment information and if found, send this to the Financial Clearinghouse Terminator in the request payment for vehicle trip planning data flow;<br/>(f) as a result of (e), continuously monitor for receipt of the payment for vehicle trip planning response data flow from the Financial Clearinghouse Terminator;<br/>(g) when the data flow in (f) is received, check to see if it was successful and if not, send the vehicle trip planning booking mishap data flow to the Trip Planning Driver or the Freight Transport Operations Manager Terminators and repeat (c) to (f), or if failure has occurred a defined number of times, send a message to the Trip Planning Driver or the Freight Transport Operations Manager Terminators that the trip plan will be deleted in the request vehicle trip planning payment data flow and send a failure response to the Prepare and Revise Trip Plans function in the trip plan with trip plan payment failed data flow;<br/>(h) if in (b) no payment for the trip planning service is needed or the payment for the actual trip planning service in (c) to (g) has been successful, then check to see if any advanced payments are needed and if not send details of the vehicle trip plan to the Manage Freight Vehicle Rest Area Use function in the trip plan with zone of parking booking needed data flow;<br/>(i) if the check in (h) shows that advanced payment for some part of the vehicle trip plan is needed, send details to the Trip Planning Driver in the advanced payment for vehicle trip plan data flow;<br/>(j) as a result of (i) continuously monitor for receipt of the vehicle trip plan booking approval data flow from the Trip Planning Driver;<br/>(k) when the data flow in (j) is received, check for payment information and if found, send this to the Financial Clearinghouse in the vehicle trip planning service payment request data flow;<br/>(l) as a result of (k), continuously monitor for receipt of the vehicle trip planning service payment response data flow from the Financial Clearinghouse;<br/>(m) when the data flow in (l) is received, check to see if it was successful and if not, send the vehicle trip planning booking mishap data flow to the Trip Planning Driver, wait for the revised vehicle trip plan booking choices data flow and repeat (i) to (l);<br/>(n) if in (i) a negative or no response is received, or (i) to (l) have been repeated a defined number of times, send a message to the Trip Planning Driver that the trip plan will be deleted in the request vehicle trip planning payment data flow and send a failure response to the Prepare and Revise Trip Plans function in the trip plan with trip plan payment failed data flow;<br/>(o) if the response found in (m) showed that payment has been successfully made, send details of the vehicle trip plan to the Manage Use of Rest Areas function in the trip plan with zone of parking needs data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0