D4.9 On-Demand Service Performance Data

Header Image
Project:
D4.9 On-Demand Service Performance Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:07
Modified: 10.09.2021 10:38:53
Project:
Advanced:
This Data Store shall be used within the Manage Public Transport Operations Functional Area.  It shall contain information objects that provide a record of the delivery of On-Demand Services.  As a minimum the information objects can be divided into two parts: about the Vehicles used to provide the On-Demand Services and a record of previous services.<br/><br/>Each information object about the Vehicles used to provide the On-Demand Services in the Store shall contain the following data objects:<br/>(1) Time (numbers defining hours, minutes and seconds),<br/>(2) Date (date string),<br/>(3) Vehicle ID (number),<br/>(4) Vehicle type (characters),<br/>(5) Current status (characters),<br/>(6) Current location (characters and/or numbers, e.g. GPS/Galileo data),<br/>(7) ID of Service currently being delivered (number).<br/><br/>The information objects in the Store that provide a record of previous services shall contain the following data objects:<br/>(8) Service ID (number),<br/>(9) Origin (characters and/or numbers, e.g. GPS/Galileo data),<br/>(10) Destination (characters and/or numbers, e.g. GPS/Galileo data),<br/>(11) Route (data for a digital roadmap using a standard format, e.g. GDF, plus characters and/or numbers, e.g. GPS/Galileo data),<br/>(12) Date of delivery (date string),<br/>(13) Time of delivery (numbers defining hours and minutes),<br/>(14) Performance, e.g. stops at which on-time, early or late (text/numbers).<br/><br/>It shall be possible for the Vehicle data to be accumulated for each Vehicle to provide a historic record of its use.  Also it shall be possible for the record of previous Services data to be maintained in perpetuity to provide a source of information for the On-demand Service Operator.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mpto_read_demand_service_performance
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mpto_load_demand_service_performance
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