(a) continuously monitor for the receipt of:<br/> - the data flow vehicle trip plan data from the Provide Driver Interface for Trip Planning function,<br/> - the revise vehicle trip plan request data flow from the Monitor Vehicle Trip Plan function,<br/> - the FTEP route request data flow from the Manage Freight and Fleet Functional Area;<br/>(b) when the first data flow in (a) is received, send the request data from stored vehicle trip store data flow to the Manage Store of Vehicle Trip Plans function to get details of the trip plans that have already been prepared;<br/>(c) as a result of (b) monitor for receipt of the requested data from stored vehicle trip plan data flow;<br/>(d) when the data flow in (c) is received extract any data that is relevant to the request received in (b);<br/>(e) assemble a request for the creation of a new vehicle trip plan and send it to the Plan Trip Plan Details function in the vehicle trip plan request data flow and then continuously monitor for receipt of the vehicle trip plan response data flow from the Plan Trip Plan Details function;<br/>(f) when the data flow in (e) is received, re-format its contents and send them to the Provide Driver Interface for Vehicle Trip Planning function in the vehicle trip plan draft data flow;<br/>(g) as a result of (h) continuously monitor for receipt of either the data flow containing vehicle trip plan data, or the vehicle trip plan acceptance data flow;<br/>(h) when the first data flow in (i) is received, repeat (b) to (h) with the new vehicle trip plan data;<br/>(i) when the second data flow in (j) is received, check to see if payment is needed for the trip planning service and/or any advanced bookings are needed, or the vehicle trip plan is for a freight vehicle and if any of these are true, send the trip plan to the Manage Trip Plan Payments function in the vehicle trip plan for bookings data flow;<br/>(j) as a result of (i) continuously monitor for receipt of the trip plan payment failed data flow from the Manage Trip Plan Payments function and when it is received, delete the vehicle trip plan and return to (a);<br/>(k) continuously monitor for receipt of the trip plan with rest area bookings data flow from the Book Suitable Rest Areas Places function;<br/>(l) if and when the data flow in (k) is received, send the complete Vehicle Trip Plan to the Manage Store of Vehicle Trip Plans function in the vehicle trip plan for store data flow;<br/>(m) continuously monitor for receipt of the revise trip plan for new rest areas data flow from the Find Suitable Rest Areas function and if and when the data flow is received, repeat (e) to (m);<br/>(n) also continuously monitor for receipt of the trip plan with un/loading bookings data flow from the Manage User of Un/Loading Zones function;<br/>(o) when the data flow in (n) is received, send the complete Vehicle Trip Plan to the Manage Store of Vehicle Trip Plans function in the vehicle trip plan for store data flow;<br/>(p) when the second data flow in (a) is received, re-format its contents into a new vehicle trip plan request and then repeat (e);<br/>(q) as a result of (p) continuously monitor for the receipt of the revised Vehicle Trip Plan for approval data flow from the Plan Trip Plan Details function;<br/>(r) when the data flow in (p) is received, re-format its contents and send them to the Provide Driver Interface for Vehicle Trip Planning function in the revised vehicle trip plan for driver data flow;<br/>(s) as a result of (r) continuously monitor for receipt of either the data flow containing Vehicle Trip Plan data, or the accept revised Vehicle Trip Plan data flow;<br/>(t) when the first data flow in (s) is received, repeat (e) and to (s) with the new Vehicle Trip Plan data;<br/>(u) when the second data flow in (s) is received, send the complete vehicle trip plan to the Manage Store of Vehicle Trip Plans function in the vehicle trip plan for store data flow;<br/>(v) when the third data flow in (a) is received, assemble a request for the creation of a new vehicle trip plan, send it to the Plan Trip Plan Details function in the vehicle trip plan request data flow and continuously monitor for receipt of the vehicle trip plan response data flow from the Plan Trip Plan Details function;<br/>(w) when the data flow in (v) is received, check to see if payment is needed for the trip planning service and/or any advanced bookings are needed, or the vehicle trip plan is for a freight vehicle and if any of these are true, send the trip plan to the Manage Trip Plan Payments function in the Vehicle Trip Plan for bookings data flow;<br/>(x) as a result of (w) continuously monitor for receipt of the trip plan payment failed data flow from the Manage Trip Plan Payments function and when it is received, delete the vehicle trip plan, send a plan preparation failed in the FTEP route request response data flow to the Manage Freight and Fleet Functional Area, and return to (a);<br/>(y) otherwise, continuously monitor for receipt of the trip plan with rest area bookings data flow from the Book Suitable Rest Areas Places function and when it is received repeat (x) with the revised routing to take account of the rest area;<br/>(z) as a result of (z) continuously monitor for receipt of the trip plan with un/loading bookings data flow and when it is received, send the Vehicle Trip Plan in the FTEP route request response data flow to the Manage Freight and Fleet Functional Area.<br/><br/><br/>
