Low Level Function
6.5.3.9 Plan Trip Details

Overview

This Function shall be capable of providing the following facilities:

(1) The ability to manage the production of trip plans based on data provided by the Traveller through functionality in other parts of the system.
(2) The ability to prepare trip plans for journeys that are either one way,  or for a return trip (including weeks/months ahead), and that take advantage of late opening hours, special facilities etc.
(3) The ability to check the criteria provided by the Traveller and obtain information for the specified modes to be used in the requested trip, but taking account of the trip planning criteria that have been set up by the Travel Information Operator.
(4) The ability to use data from the store of Road Trip Planning Data and/or the store of PT Trip Planning Data, plus also to collect information about Points of Interest (POI) and Personal Services (PS) from External Service Providers.
(5) Where specified by the Traveller the ability to request information about the services provided by other transport modes, tolls plus other charges if they will need to be paid in order to complete the proposed trip, and to pass all of this information on to the Provide Traveller Information functionality.
(6) The ability to create trip plans for cyclists and pedestrians using the road network data and related perturbations, but disregarding traffic incident information.
(7) The ability to revise a part completed trip plan when a Traveller departs in any way from its contents, or travel conditions change, starting from the current Traveller location and mode of travel.
(8) The ability to exchange journey time data for each segment of the road network with its implementation in other devices and to plan trips when the only traffic related data that is available this journey time data.

Functional Requirements

(a) continuously monitor for the receipt of the traveller trip requirements and vehicle trip plan request data flows
(b) when the traveller trip requirements data flow is received in (a), use the trip planning information to fulfil the traveller's trip request from the stores of Road Trip Planning Data and/or PT Trip Planning Data and produce a trip plan
(c) in addition to (b) include in the trip plan a choice from different routes for the road part of the trip that use the motorway networks, secondary road networks, scenic routes and so forth depending on the criteria provided by the traveller and the travel information operator, plus recommendations received from TCC's in the inter-urban recommended routes and urban recommended routes data flows
(d) in addition to (b) and (c) include in the trip plan a choice of travel modes, where they provide sensible alternatives, or have been requested by the traveller
(e) if required by the traveller details of both single and return trips, including those where the date of the return part of the trip may be some time ahead of that for the outward part shall be included in the trip plan
(f) when the preparation of a new/revised trip plan is completed, it shall be sent back to the traveller interface in the traveller trip description data flow
(g) as a result of (f) continuously monitor for receipt of the modified trip plan requirements data flow and if received within a short time, repeat (b) to (g) using the revised requirements
(h) when the vehicle trip plan request data flow is received in (a), use the data it contains to produce a vehicle based trip plan, fulfilling the requirements of (c) and (e) but include other information such as the need to book parking places for freight vehicles so that goods can be loaded or unloaded
(i) when the preparation of a new/revised trip plan is completed, it shall be sent back to the vehicle interface in the vehicle trip plan response data flow
(j) all trip plans shall include any appropriate warnings about the existing conditions, safety recommendations and the expected conditions at the planned time of travelling on the route(s) that they include
(k) when revising a part completed trip plan, propose alternative modes and/or times of travel to those in the remainder of the plan
(l) all trip plans shall be produced according to criteria that are set up and modified by the travel information operator so that trips conform to the current travel and/or traffic management policies
(m) it shall be possible to prepare trip plans with a minimum set of road traffic data that only includes travel times for each segment of the road network
(n) continuously monitor for receipt of any of the data flows from the Provide Trip Planning Operator Interface function
(o) when the request trip planning criteria data flow is received in (n), collect the criteria from the internal store of criteria used in (c) and send it back the toe Provide Trip Planning Operator Interface function in the requested trip planning criteria data flow
(p) when the update trip planning criteria data flow is received in (n), use its contents to update the internal store of criteria used in (c)
(q) continuously monitor for receipt of the vehicle trip plan criteria changes data flow
(r) when the data flow in (q) is received, update the part of the internal store of criteria used in (c) that is used to prepare vehicle trip plans.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 6.5.3 Trip Planning
  • Functional Tree of Area 6

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    10.2.0.2
    The system shall be able to satisfy a variety of booking types, e.g. last minute, return trip (including weeks/months ahead), being able to take advantage of late opening hours, special facilities etc.
    10.2.1.3
    The system shall be able to predict the time that will be taken to make a particular trip.
    6.1.0.7
    The system shall be able to provide information so that travellers may share a vehicle with others for all or part of a (multi-modal) journey.
    6.1.1.2
    The system shall be able to provide trip information on other modes of transport, e.g. for demand-spreading when major events occur, or when weather conditions, strikes, cultural or sports events etc cause problems for one mode.
    6.1.2.11
    The system shall be able to provide information about "Points of Interest", e.g. location, opening times, price of service, nearest transport service points.
    6.1.2.12
    The system shall be able to receive information about a point of interest from the providers/owners/managers of that "Point of Interest".
    6.1.2.13
    The system shall be able to provide information to travellers so as to influence their choice of destination and/or mode of travel, e.g. to protect the environment of a "Point of Interest", or geographic area.
    6.1.2.14
    The system shall be able to provide information to travellers about the personal support services, e.g. doctor, in a specific locality.
    6.1.2.15
    The system shall be able to receive information about a personal support service, e.g. doctor, from the providers/owners/managers of that service.
    6.1.2.5
    The system shall be able to analyse, process and retrieve data from different combinations of sources (including floating car).
    6.2.0.4
    The system shall provide traffic information to the traveller during his/her trip in a timely manner, and include travel conditions, accidents, special events, car park status, etc.
    6.2.1.3
    The system shall be able to provide information about other transport modes: e.g. location of P+R areas, PT timetable, etc.
    6.2.2.10
    The system shall be able to collect data from a variety of different sources, e.g. road/traffic management, police, weather services, floating car etc.
    6.2.2.3
    The system shall be able to provide cyclists and pedestrians with information about suitable routes.
    6.2.2.5
    The system shall be able to provide information to all drivers including route restrictions, travel times, etc.
    6.2.2.9
    The system shall be able to adapt the information to different classes of users, e.g. travellers, radio broadcasters, service operators.
    6.2.3.1
    The system within the vehicle, or in the centre, shall support various types of presentation to the user.
    6.2.3.2
    The system shall normally provide messages from a finite set of well defined messages.
    6.2.3.3
    The system shall provide information in the native language at the output location, and/or from a user selected choice of other appropriate foreign languages, when applicable.
    6.2.3.4
    The system shall provide information using "open" standard communication protocols.
    6.2.3.5
    The system shall be able to provide customised on-trip information to hand-held and in-vehicle devices.
    6.4.0.1
    The system shall provide travellers with recommended routes to specified destinations.
    6.4.0.2
    The system shall not base its decisions on a restricted sub-set of the road network, e.g. motorways only.
    6.4.1.1
    The system shall be able to provide guidance to Car Parks (with parking spaces).
    6.4.1.3
    The system shall be able to compute the total predicted journey time over the route selected.
    6.4.1.4
    The system shall be able provide customised navigation information to the destination using a variety of selection criteria.
    6.4.1.5
    The system shall be able to provide guidance to "Points of Interest".
    6.4.1.6
    The system shall provide information which is consistent with any other information being presented about the road.
    7.3.0.1
    The system shall provide information that will influence travellers' decisions regarding their destinations, time, mode of travel, route etc.
    7.3.4.1
    The system shall be able to provide information to promote the use of cycles and walking.
    7.5.1.17
    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.
    7.5.1.21
    The system shall be able to “follow” those vehicles that have been provide with individual routes and to prove the effectiveness of those suggested routes, making changes to the algorithms that will be used in the future if necessary.
    7.5.1.25
    The system shall enable the TCC to recommend the use of alternative routes for different types of vehicle.
    7.5.1.26
    The system shall enable the TCC to command the use of alternative routes for different types of vehicle.
    7.6.2.3
    The system shall enable a traveller to request and receive personalised journey plans in advance, assess different plans according to certain criteria (e.g. vehicle type, travel time, cost, expected traffic density, planned events, facilities en route, parking), and to save one for future use.