D5.4 Vehicle Trip Plans Data

Header Image
Project:
D5.4 Vehicle Trip Plans Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:07
Modified: 10.09.2021 10:38:54
Project:
Advanced:
This Data Store shall be used within the Provide In-vehicle Trip Planning High-level Function.  It shall contain information objects that are the result of the process to create a Vehicle Trip Plan.<br/><br/>The information objects in the Store shall contain the following objects:<br/>(1) Route ID (number),<br/>(2) Route name (characters),<br/>(3) Origin (characters and/or numbers, e.g. GPS/Galileo data),<br/>(4) Destination (characters and/or numbers, e.g. GPS/Galileo data),<br/>(5) Expected arrival time (numbers defining hours, minutes and seconds),<br/>(6) Vehicle type for route (characters),<br/>(7) Type of goods carried, if any (characters),<br/>(8) Route (data for a digital roadmap using a standard format, e.g. GDF, plus characters and/or numbers, e.g. GPS/Galileo data),<br/>(9) Rest zone:<br/>    (9a) Rest zone ID (number),<br/>    (9b) Name (characters),<br/>    (9c) Location (characters and/or numbers, e.g. GPS/Galileo data),<br/>    (9d) Booked start date (date string),<br/>    (9e) Booked start time (numbers defining hours, minutes and seconds),<br/>    (9f) Booked stay duration numbers defining hours, minutes and seconds),<br/>(10) Un/loading zone:<br/>    (10a) Un/loading zone ID (number),<br/>    (10b) Name (characters),<br/>    (10c) Location (characters and/or numbers, e.g. GPS/Galileo data),<br/>    (10d) Booked start date (date string),<br/>    (10e) Booked start time (numbers defining hours, minutes and seconds),<br/>    (10f) Booked stay duration (numbers defining hours, minutes and seconds),<br/>(11) Payments made:<br/>    (11a) What for (characters)?<br/>    (11b) Complete (number or character indicating YES or NO),<br/>(12) Oher relevant data (characters and/or numbers).<br/><br/>It shall be possible for each information object to include data objects about more than one rest area and/or un/loading zone and for payments for use to be recorded against some or all of these, plus any pre-payment of road use charges.  The data objects in this Store shall be retained for the prime purpose of supporting the Diver during the implementation of the Trip Plan.  All the factors that were considered in production of the Trip Plan are included in the data objects described above.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
  • Other Links
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_read
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pshvs_vehicle_trip_plan_load
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Tag Value
DataStore_SecurityLevel None
Details:
Default: None
isUnlimited false
Details:
Values: true,false
Default: false
itemKind Information
Details:
Values: Physical,Information
Default: Information
Maximum acceptable request times per application and/or service 1000
Details:
Default: 1000
Number of Users supported 1
Details:
Default: 1
Physical Capacity 1 Byte
Details:
Default: 1 Byte
Planned data storage duration over time 1 Year
Details:
Default: 1 Year
Planned Service level per application and partner None
Details:
Default: None
transaction numbers over time 10
Details:
Default: 10
Property Value
isControlType: false
ordering: FIFO
Object Type Connection Direction Notes
Service Provider Main Application Object Usage From