D9.4 Loading or Unloading Zone Use Data

Header Image
Project:
D9.4 Loading or Unloading Zone Use Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:07
Modified: 10.09.2021 10:38:55
Project:
Advanced:
This Data Store shall be used within the Provide Support for Cooperative Systems Functional Area.  It shall contain information objects that provide details about the use and characteristics of loading and unloading zones plus holding zones that are used by Freight Vehicles to pick-up and deliver goods.  The information objects for each zone shall be in two forms: static data and dynamic data<br/><br/>The information object in the Store containing static data about each zone shall contain the following data objects:<br/>(1) Zone location (characters and/or numbers, e.g. GPS/Galileo data),<br/>(2) Zone size (number),<br/>(3) Type of goods that the zone can accommodate (characters),<br/>(4) Restrictions on use of the zone (characters),<br/>(5) Type(s) of Vehicle that the zone will accommodate (characters),<br/>(6) Number(s) of Vehicles of different types that can be accommodated (number),<br/>(7) Road network in and around zone (data for a digital roadmap using a standard format, e.g. GDF),<br/>(8) Zone entry point (characters and/or numbers, e.g. GPS/Galileo data),<br/>(9) Zone exit point (characters and/or numbers, e.g. GPS/Galileo data).<br/><br/>This information object shall be repeated for each zone of each type.<br/><br/>The information object in the Store containing dynamic data about each zone shall contain the following data objects:<br/>(10) Date when zone is booked (date string),<br/>(11) Time when zone is booked (numbers defining hours, minutes and seconds),<br/>(12) Number of Vehicles that have booked a place for date/time (number),<br/>(13) The ID of each Vehicle for each booking (number),<br/>(14) Expected duration of stay for each booked Vehicle (numbers defining hours, minutes and seconds),<br/>(15) The ID of the Vehicle currently occupying the zone (number).<br/><br/>It shall be possible for the information objects containing dynamic data to be repeated for each booking of each type of zone and to be updated as soon as the data changes.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pscs_read_zone_use_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pscs_load_zone_use_data
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