F6.3.11 Monitor Trip Plan Implementation for Traveller

Header Image
Project:
F6.3.11 Monitor Trip Plan Implementation for Traveller : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:37
Modified: 08.09.2021 14:47:25
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to receive data about the current location of the Traveller so that progress with the current trip plan can be monitored until either the trip is completed, or a new trip plan is produced.<br/>(2) The ability to continuously evaluate the data that is received about travel conditions such as current and predicted traffic flows, road works, weather, incidents and PT services.<br/>(3) The ability to use the results of the evaluation of travel conditions and the current location of the Traveller to determine if there will be benefit to the Traveller from changing the trip plan and to request that a new trip plan is produced if such a benefit is found.<br/>(4) The ability to collect O-D and journey time data for the road network segments that are used in the trip plan and send them to the Inter-urban and Urban Traffic Data Collection functionality.<br/>(5) At the end of the trip, the ability to collect the data about the complete performance of the trip and send it to the Performance Evaluation functionality. <br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» ptja.mt_inter-urban_road_use_data_from_trip
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_completion_report_for_evaluation
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_revise_trip_plan_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F6.3 Support Trip
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Functional_Area» F6. Provide Traveller Journey Assistance
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja.mt_urban_road_use_data_from_trip
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja.mt_trip_plan_o-d_data
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 6.2.2.13
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_trip_plan_for_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.2.14
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.6.2.15
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.1.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_weather_information_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_de-icing_data_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.2.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.0.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_incident_information_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto.ptja_pt_services_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.0.6
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_inter-urban_network_perturbations
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.2.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_forecast_traffic_to_monitor_trip
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.6.2.7
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.1.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_urban_network_perturbations
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.2.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» ptja_traveller_location_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.4.1.5
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.6.2.14
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 6.1.2.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.ptja_roadworks_information_for_trip_monitoring
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) continuously monitor for arrival of all the input data flows;<br/>(b) when any of the data flows containing updates of travel conditions or the location of vehicles carrying hazardous goods is received in (a), store their contents locally for future use, replacing any data received previously unless it is from a different traffic control centre, or service provider;<br/>(c) when the trip plan for monitoring data flow is received in (a), store the trip plan data locally for use in monitoring the progress of the Traveller as the trip is implemented;<br/>(d) when the traveller location data flow is received in (a), compare this with the expected location according to the trip plan data to determine if the Traveller has deviated from following the trip plan;<br/>(e) use the data in (b) and (d) to calculate the predicted arrival times at the trip destination and any way points to be encountered before the destination is reached;<br/>(f) also use the data in (b) and (d) to assess whether the conditions under which the trip was planned have significantly changed;<br/>(g) if the answer to either (e) or (f) is that the trip plan needs to be changed, then send the revise implementing trip plan request data flow to the Manage Production of the Revised Trip Plan function;<br/>(h) continue with (b) plus (d) to (f) until the trip plan for monitoring data flow is again received in (a), after which (c) to (g) should be repeated;<br/>(i) as the trip progresses, collect journey times for each segment of the road network that is used in the trip;<br/>(j) use the data in (i) to produce journey times and O-D data for segments in the inter-urban and urban road network used in the trip plan;<br/>(k) as soon as it is available, i.e. before the end of the trip, put the data from (j) into the inter-urban road use data from trip and urban road use data from trip data flows, and send them to the Inter-urban Traffic Data Management and Urban Traffic Data Management functions respectively;<br/>(l) when the trip has been completed, collect data about its implementation, remove the Traveller identity and any other personal data and send it to the Evaluate Trip After Completion function in the trip completion report for evaluation data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0