Description of content

This Data Store shall be used within the Provide Traveller Journey Assistance Area.  It shall contain data that is the result of the trip planning process.  This data is retained for the prime purpose of supporting the Traveller during the trip. The most notable requirement is to react to the consequences of perturbations in the situation(s) existing during trip planning.  All the considerations that resulted in production of the trip itinerary are included in this Data Store.

The data in the Store shall be structured in the following way:
- Traveller’s ID (number)
- Traveller's preferred language (characters)
- Traveller's disabilities (characters)
- route (data for a digital roadmap using a standard format, e.g. GDF, plus characters and/or numbers, e.g. GPS/Galileo data)
- trip origin characters and/or numbers, e.g. GPS/Galileo data()
- departure date (date string)
- departure time (numbers defining hours, minutes and seconds)
- way point:
    - location (characters and/or numbers, e.g. GPS/Galileo data)
    - expected arrival date (date string)
    - expected arrival time (numbers defining hours, minutes and seconds)
    - car park information (characters)
- trip destination (characters and/or numbers, e.g. GPS/Galileo data)
- expected arrival date (date string)
- expected arrival time (numbers defining hours, minutes and seconds)
- car park information (characters)
- description of cargo to be carried on trip (characters)
- number of passengers expected in Vehicle (number)
- hotel bookings completed (characters)
- hotel bookings still to be made (characters)
- car rental bookings completed (characters)
- car rental bookings still to be made (characters)
- other travel mode bookings completed (characters)
- other travel mode bookings still to be made (characters)
- vehicle breakdown assistance information (characters)
- way of communication with Traveller while on-trip (characters + numbers)
- route guidance facilitation parameters (characters)
- trip skeletons (see below).

It shall be possible for there to be none, or more that one way point, plus hotel. car rental and other travel mode bookings.

A special feature of the data in the Store to support the Traveller shall be the "trip skeleton", which shall be available for use in two ways:
(1) as the start of the search for alternatives during trip planning;
(2) as the fixed part of the trip if the trip has to be retained for future reuse.
The core part of the "skeleton" shall be the origin-destination combination and a date and/or time for the start or the arrival and possibly a number of intermediate locations - see data to be stored above.  In both cases, trip preferences are part of the trip skeleton for trip planning purposes and it shall be possible to obtain these from the store of GTP data.

The data for each Traveller must be kept separate with no possibility of inadvertent access to the data for one Traveller by either another Traveller, or some form of un-authorised access.

Diagrams

The Diagram(s) below is (are) the Diagram(s) where you can find the Datastore

DFD 6.8 Manage Trip Plan Store

Input dataflows

ptja_load_trip_plan_data

Output dataflows

ptja_read_trip_plan_data