Description of content

This Data Store shall be used within the Provide In-vehicle Trip Planning High-level Function.  It shall contain data that is the result of the process to create a Vehicle Trip Plan.

The data in the Store shall be structured in the following way:
- route ID (number)
- route name (characters)
- origin (characters and/or numbers, e.g. GPS/Galileo data)
- destination (characters and/or numbers, e.g. GPS/Galileo data)
- expected arrival time (numbers defining hours, minutes and seconds)
- vehicle type for route (characters)
- type of goods carried (characters)
- route (data for a digital roadmap using a standard format, e.g. GDF, plus characters and/or numbers, e.g. GPS/Galileo data)
- rest zone:
    - ID (number)
    - name (characters)
    - location (characters and/or numbers, e.g. GPS/Galileo data)
    - booked start date (date string)
    - booked start time (numbers defining hours, minutes and seconds)
    - booked stay duration (numbers defining hours, minutes and seconds)
- un/loading zone:
    - ID (number)
    - name (characters)
    - location (characters and/or numbers, e.g. GPS/Galileo data)
    - booked start date (date string)
    - booked start time (numbers defining hours, minutes and seconds)
    - booked stay duration (numbers defining hours, minutes and seconds)
- payments made:
    - what for (characters)
    - complete (number or character indicating YES or NO)
- other relevant data (characters and/or numbers)

It shall be possible for data about more than one rest area and/or un/loading zone to be included and for payments to be recorded against some or all of these plus any pre-payment of road use charges.  The data in this Store shall be retained for the prime purpose of supporting the Diver during the implementation of the Trip Plan.  All the considerations that resulted in production of the Trip Plan are included in this Data Store.

Diagrams

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

DFD 5.14 Provide In-vehicle Trip Planning & Implementation

Input dataflows

pshvs_vehicle_trip_plan_load

Output dataflows

pshvs_vehicle_trip_plan_read