Low Level Function
5.14.2 Create and Revise Vehicle Trip Plan
Overview
This Function shall be capable of providing the following facilities:
(1) The ability to take responsibility for the management of the creation of Vehicle Trip Plans.
(2) The ability to create Vehicle Trip Plans either as a result of a request from a Driver, or because the implementation of a previously created Vehicle Trip Plan shows that changes are needed to provide an improved road trip experience for the Driver.
(3) The ability to send its requests for Trip Plans to be created to the Trip Planning functionality within the Provide Traveller Journey Assistance Functional Area and to seek acceptance from the Driver of the resulting Trip Plans.
(4) Once a Trip Plan has been accepted by the Driver, the ability to send it to the Manage Store of Vehicle Trip Plans function so that it can be available for implementation.
Functional Requirements
(a) continuously monitor for the receipt of the vehicle trip plan data and revise vehicle trip plan request data flows
(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
(c) as a result of (b) monitor for receipt of the requested data from stored vehicle trip plan data flow
(d) when the data flow in (c) is received extract any data that is relevant to the request received in (b)
(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
(f) as a result of (e), continuously monitor for receipt of the vehicle trip plan response data flow from the Plan Trip Plan Details function
(g) when the data flow in (f) 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
(h) as a result of (g) continuously monitor for receipt of either the data flow containing vehicle trip plan data, or the vehicle trip plan acceptance data flow
(i) when the first data flow in (h) is received, repeat (b) to (h) with the new vehicle trip plan data
(j) when the second data flow in (h) 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 Enable Driver to Make Payments function in the vehicle trip plan for bookings data flow
(k) as a result of (j) continuously monitor for receipt of either the trip plan with no zone or parking bookings data flow from the Enable Driver to Make Payments function or the vehicle trip plan with rest zone bookings data flow from the Manage Freight Vehicle Rest Zone Use function, or the vehicle trip plan with parking bookings data flow from the Manage Freight Vehicle Parking Reservations function
(l) when any of the data flows in (k) is received check their contents and if it is not a success then delete the vehicle trip plan and return to (a)
(m) when any of the data flows in (k) is received with a positive response, send the complete vehicle trip plan to the Manage Store of Vehicle Trip Plans function in the vehicle trip plan for store data flow
(n) when the second data flow in (a) is received, re-format its contents into a new vehicle trip plan request and then repeat (e)
(o) as a result of (n) continuously monitor for the receipt of the revised vehicle trip plan for approval data flow
(p) when the data flow in (o) 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
(q) as a result of (p) continuously monitor for receipt of either the data flow containing vehicle trip plan data, or the accept revised vehicle trip plan data flow
(r) when the first data flow in (q) is received, repeat (e) and (j) to (m) with the new vehicle trip plan data
(s) when the second data flow in (q) 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.
Diagrams
Parent Higher Level Function
Input logical dataflows
Output logical dataflows
User needs
Number | Description |
| The system shall be able to provide guidance to Car Parks (with parking spaces).
|
| (X)FCD - The system shall be able to determine the intended route of the host vehicle. |
| The system shall enable the driver to store data relating to the characteristics of the host vehicle for that trip (e.g. loaded weight, hazardous goods, (trailer) dimensions). |
| The system shall be able to provide the driver via an in-vehicle device with a route to a selected destination that takes account of the vehicle type, the state of the traffic on the road network and any incidents/congestion (route options may be offered and one selected by the driver). |
| The system shall be able to compute an alternative local route for vehicles approaching a location to be avoided (e.g. one where there is a traffic incident or congestion above a given severity), and does not create congestion downstream. The alternative route computed may depend upon the vehicle type, and may need to be changed as the incident or congestion to be avoided evolves over time. |
| The system shall be able to present an alternative route that avoids an incident or congestion to the driver via an in-vehicle device, and to update that route if necessary. |
| The system shall enable the driver to store data relating to the characteristics of the host vehicle for that trip (e.g. loaded weight, hazardous goods, (trailer) dimensions). |