Low Level Function
6.3.11 Monitor Trip Plan Implementation for Traveller

Overview

This Function shall be capable of providing the following facilities:

(1) The ability to receive data about the current location of the Traveller so that progress with the current trip plan can be monitored until either the trip is completed, or a new trip plan is produced.
(2) The ability to continuously evaluate the data that is received about travel conditions such as current and predicted traffic flows, road works, weather, incidents and PT services.
(3) The ability to use the results of the evaluation of travel conditions and the current location of the Traveller to determine if there will be benefit to the Traveller from changing the trip plan and to request that a new trip plan is produced if such a benefit is found.
(4) The ability to collect O-D and journey time data for the road network segments that are used in the trip plan and send them to the Inter-urban and Urban Traffic Data Collection functionality.
(5) At the end of the trip, the ability to collect the data about the complete performance of the trip and send it to the Performance Evaluation functionality.

Functional Requirements

(a) continuously monitor for arrival of all the input data flows
(b) when any of the data flows containing updates of travel conditions or the location of vehicles carrying hazardous goods is received in (a), store their contents locally for future use, replacing any data received previously unless it is from a different traffic control centre, or service provider
(c) when the trip plan for monitoring data flow is received in (a), store the trip plan data locally for use in monitoring the progress of the traveller as the trip is implemented
(d) when the traveller location data flow is received in (a), compare this with the expected location according to the trip plan data to determine if the traveller has deviated from following the trip plan
(e) use the data in (b) and (d) to calculate the predicted arrival times at the trip destination and any way points to be encountered before the destination is reached
(f) also use the data in (b) and (d) to assess whether the conditions under which the trip was planned have significantly changed
(g) if the answer to either (e) or (f) is that the trip plan needs to be changed, then send the revise implementing trip plan request data flow to the Manage Production of the Revised Trip Plan function
(h) continue with (b) plus (d) to (f) until the trip plan for monitoring data flow is again received in (a), after which (c) to (g) should be repeated
(i) as the trip progresses, collect journey times for each segment of the road network that is used in the trip
(j) use the data in (i) to produce journey times and O-D data for segments in the inter-urban and urban road network used in the trip plan
(k) as soon as it is available, i.e. before the end of the trip, put the data from (j) into the inter-urban road use data from trip and urban road use data from trip data flows, and send them to the Inter-urban Traffic Data Management and Urban Traffic Data Management functions respectively
(l) when the trip has been completed, collect data about its implementation, remove the Traveller identity and any other personal data and send it to the Evaluate Trip After Completion function in the trip completion report for evaluation data flow.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 6.3 Support Trip
  • Functional Tree of Area 6
  • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    6.1.1.4
    The system shall be able to provide extensive multi-modal trip information, e.g. prices, fares, routes, forecast & current traffic situations, traffic control, demand mgt measures, local warnings, special events, weather conditions, hotels etc.
    6.1.2.1
    The system shall inform the User when changes occur to the criteria upon which the pre trip information had been given.
    6.1.2.2
    The system shall be able to provide information on the cancellation of departures from an inter-modal interchange (e.g. railway station, an airport , a port or a coach station) due to the weather; strikes or other reasons.
    6.2.0.6
    The system shall inform the User when changes occur to the criteria upon which the pre trip information had been given.
    6.2.1.1
    The system shall be able to provide alternative routes or mode-switch recommendations when it detects, or is informed, that problems have occurred on a mode.
    6.2.2.13
    The system shall be able to provide information to vehicle drivers in case of medical emergency, e.g. location of rest areas, medical assistance, etc.
    6.2.2.14
    The system shall be able to modify a travel plan if the traveller does not follow it.
    6.4.0.4
    The system shall be able to modify its navigation instructions if an incorrect turn is made.
    6.4.1.1
    The system shall be able to provide guidance to Car Parks (with parking spaces).
    6.4.1.5
    The system shall be able to provide guidance to "Points of Interest".
    6.4.2.3
    The system shall enable bi-directional voice and data communication with the vehicle.
    7.6.2.14
    The system shall be able to send O-D data, from the navigation system, and current location data from the host vehicle to the TCC to enable geo-referenced travel times to be produced.
    7.6.2.15
    The system shall enable the service provided to the traveller to be passed from one Service Provide to another as the traveller changes areas of coverage.
    7.6.2.7
    The system shall be able to calculate the expected time of arrival at a destination or way point based on the driver’s profile and the anticipated traffic conditions.