Overview

This Function shall be capable of providing the following facilities:

(1) The ability to monitor the progress that the Driver is making with the Vehicle Trip Plan that is currently being implemented.
(2) The ability to use the current location of the Vehicle to check its progress with the Trip Plan implementation.
(3) If the Vehicle Trip Plan is for a Freight Vehicle, the ability to update the Estimated Time of Arrival (ETA) so that any rest area or un/loading zone bookings can be re-validated.
(4) When the Freight Vehicle leaves a rest area or un/loading zone, the ability to provide data showing that the parking space it has used can be booked by another Freight Vehicle.
(5) If the Vehicle departs from the route in the Trip Plan, the ability to send a warning for output to the Driver and to request that a new route is created starting from the current location of the Vehicle.
(6) The ability to continuously evaluate the data it receives about the road traffic conditions such as current and predicted traffic flows, road works, weather and incidents, plus the current Vehicle location and part of the Trip Plan that remains to be implemented, and to determine if there is any benefit in changing the current Vehicle Trip Plan.
(7) If the results of the evaluation shows that there is some benefit to the Driver in changing the current Vehicle Trip Plan, the ability to request that this is done, send a warning message with the reason for the change for output to the Driver and continue monitoring the use of the current Trip Plan until it is replaced.
(8) As implementation of the Vehicle Trip Plan progresses, the ability to collect O-D and journey time data for the road network segments that are used in the trip and send them to the Inter-urban and Urban Traffic Data Collection functionality.
(9) The ability to send data about way points in the Trip Plan to other in-vehicle functionality for inclusion in Extended Floating Car Data (XFCD).

Functional Requirements

(a) continuously monitor for receipt of the data flows containing updates to the road traffic conditions and incidents
(b) when any of the data flows are received in (a) update an internal store with the data that they contain
(c) continuously monitor for receipt of the vehicle trip plan for monitoring data flow
(d) when the data flow in (c) is received, extract the vehicle trip plan description and await the receipt of the vehicle location for trip plan monitoring data flow, but send data about way points in the trip plan to the Prepare Extended Floating Car Data function in the route information for xfcd data flow
(e) when the data flow in (d) is received use the vehicle trip plan data to determine how far the vehicle has progressed through the trip plan and calculate the Estimated Time of Arrival (ETA) at the way points and the trip destination, using the data collected in (b) above
(f) send the ETA data to the Provide Driver Trip Interface in the vehicle eta for driver data flow
(g) use the data in (e) to determine the ETA for the next booked rest area, loading or unloading zone, or holding zone and send the result from the first to the Rest Area Booking Management function in the rest area eta data flow and from either the second or third to the Manage Loading or Unloading Zone Bookings function in un/loading zone eta or holding zone eta data flows respectively
(h) when the data in (e) shows that the vehicle is leaving a rest zone, send this information to the Rest Area Booking Management function in the freight vehicle departing rest area data flow
(i) also use the data in (e) to determine if the vehicle is departing from the route in the trip plan and if so, end the revise vehicle trip plan request data flow to the Create and Revise Vehicle Trip Plan function so that a new vehicle trip plan can be created, starting from the current location of the vehicle, and send a warning message in the vehicle departed from route data flow to the Provide Driver Trip Interface function
(j) again use the data in (e) to assess the progress that is being made with implementing the trip and check to see if the ETA is remaining constant or increasing, i.e. the trip will take longer that expected
(k) if the trip will take longer than expected, send the revise vehicle trip plan request data flow to the Create and Revise Vehicle Trip Plan function so that a new vehicle trip plan can be created, starting from the current location of the vehicle
(l) periodically send details of the route from the vehicle trip plan to the inter-urban and urban functionality in the vehicle trip plan route for inter-urban and vehicle trip plan route for urban data flows
(m) as a result of (k) put the reason for the need to change the trip plan in the vehicle trip plan change reason for driver data flow and send it to the Provide Driver Trip Interface function
(n) using the data from (e) to calculate the journey time for each segment of the road network that the vehicle uses and send it to the Manage Traffic functionality in which ever is appropriate of the inter-urban road use data from trip and urban road use data from trip data flows
(o) continuously monitor for receipt of the vehicle location for trip plan monitoring data flow and when it is received, repeat (e) to (l) above, but once the data flow has been sent in (m) do not repeat until a new trip plan has been received in (c)
(p) at the end of the trip, determine the original - destination (O-D) points and total journey time for the trip, taking account of any changes to the trip plan and send it to the Process Road Traffic Data function in the data flow containing vehicle trip plan o-d data.

Diagrams

Parent Higher Level Function

• 5.14 Provide In-vehicle Trip Planning & Implementation

Input logical dataflows

• mt.pshvs_de-icing_data_for_vehicle_trip_monitoring
• mt.pshvs_forecast_traffic_to_monitor_vehicle_trip
• mt.pshvs_incident_data_for_vehicle_trip_monitoring
• mt.pshvs_inter-urban_network_perturbations
• mt.pshvs_roadworks_data_to_monitor_vehicle_trips
• mt.pshvs_urban_network_perturbations
• mt.pshvs_weather_data_for_vehicle_trip_monitoring
• pshvs_vehicle_location_for_trip_plan_monitoring
• pshvs_vehicle_trip_plan_for_monitoring

Output logical dataflows

• pshvs.mt_freight_vehicle_left_rest_areae
• pshvs.mt_inter-urban_road_use_data_from_trip
• pshvs.mt_rest_area_eta
• pshvs.mt_urban_road_use_data_from_trip
• pshvs.mt_vehicle_trip_plan_o-d_data
• pshvs.mt_vehicle_trip_plan_route_for_inter-urban
• pshvs.mt_vehicle_trip_plan_route_for_urban
• pshvs.pscs_freight_vehicle_left_un/loading_zone
• pshvs.pscs_holding_zone_eta
• pshvs.pscs_un/loading_zone_eta
• pshvs.ptja_vehicle_trip_plan_criteria_changes
• pshvs_revise_vehicle_trip_plan_request
• pshvs_route_information_for_xfcd
• pshvs_vehicle_departed_from_route
• pshvs_vehicle_eta_for_driver
• pshvs_vehicle_trip_plan_change_data_for_driver

User needs