F6.5.10 Provide Traveller Trip Planning Interface

Frame Repository / Frame Functional View / Functionality / Functional Area F6 - Provide Traveller Journey Assistance / F6. Provide Traveller Journey Assistance / F6.5 Prepare Trip Plan / F6.5.10 Provide Traveller Trip Planning Interface

Project:

F6.5 Prepare Trip Plan

F6.5.10 Provide Traveller Trip Planning Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:37
Modified:	08.09.2021 14:47:26

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{A73D8E6A-B8FD-4acc-AD2F-E6A619A7DEF3}
Appears In:	Functional Tree of Area F6 Provide Traveller Journey Assistance, DFD F6.5 Prepare Trip Plan

This Function shall be capable of providing the following facilities: (1) A HMI through which the Traveller can initiate and manage the trip planning process. (2) Using the HMI, the ability of the Traveller to define the parameters that are to be used to plan a trip, including origin, destination, places to be visited during the trip before the destination is reached (way points, transport modes to be used, departure time, arrival time, services to be booked, and whatever else is deemed interesting for trip satisfaction. (3) The ability for the Traveller to use the HMI to request that these parameters are entered into the store of General Trip Preferences Data or to use data in this store to supplement that being provided for a particular trip. (4) When complete, the ability to send the requirements to the Trip Planning functionality so that the trip plan can be prepared. (5) The ability to use the HMI to present the prepared trip plan to the Traveller and for the Traveller to be able to refine any of the requirements and re-plan the trip until it fulfils their needs in an iterative way. (6) The ability to store successive trip plans internally so that they can be re-called by the Traveller if later versions turn out to be unsatisfactory. (7) Once a trip plan has been accepted by the Traveller, the Function shall send the details to the Function responsible for producing the travel itinerary or to the Function responsible for making any bookings that are included in the trip plan and/or paying for the trip planning process. (8) The ability for the Traveller to use the HMI to reject a trip plan and close the trip planning activity at any time and to delete any requirements that have been provided. (9) The ability for the Traveller to be informed through the HMI about any payments that are needed, either for the trip planning process itself, or for services that the Traveller has specified for inclusion in the trip. (10) It shall be possible for the Traveller to be asked to pay for the trip planning process either before it starts, or once a successful trip plan has been produced. (11) The ability of the Traveller to use the HMI to initiate payment for the trip planning service and/or any services that are required as part of the trip, and to be informed of the success or failure of the payment process. (12) If the payment process fails, the ability to cancel the trip(s) that have been planned and to inform the Traveller of this through the HMI.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» ptja_full_trip_description_for_bookings FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Functional_Area» F6. Provide Traveller Journey Assistance FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_trip_plan_ready_for_implementation FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F6.5 Prepare Trip Plan FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_traveller_trip_requirement FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_modified_trip_plan_requirements FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-request_preferences FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-trip_alternatives FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_request_applicable_GTP_parameters FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_trip_planning_payment FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_booking_approved FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-initial_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_cancel_bookings_for_trip FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-select_trip FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-request_trip_planing_payment FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-itinerary_initial FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-advanced_payment_needed_by_trip_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.ptt-booking_mishap FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 10.2.1.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-booking_approval FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.4.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_traveller_trip_description FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.4.2.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_booking_mishap FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.3.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-trip_planning_payment FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.3.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.0.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.4.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-modified_trip_parameters FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-trip_selection FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-revised_booking_choices FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.1.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-final_approval FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_requested_applicable_GTP_parameters FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_request_trip_planning_payment FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-basic_trip_parameters FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_advanced_payment_needed FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.ptt-additional_trip_parameters FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.11 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.0.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.12 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.0.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.3.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_full_trip_description_with_bookings 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 the receipt of the basic trip parameters data flow from the Pre-Trip Traveller;<br/>(b) when the data flow in (a) is received, if required send the request applicable General Trip Preferences (GTP) parameters data flow to the GTP management function and wait for the response in the requested applicable GTP parameters data flow;<br/>(c) send the request preferences data flow requesting any changes to the GTP data to the Pre-Trip Traveller and wait for the response in the additional trip parameters data flow;<br/>(d) when the response data flow is received in (c), use its contents and all the other data provided by the Pre-Trip Traveller to prepare the trip plan requirements, put them in the traveller trip requirement data flow and send it to the Trip Planning function;<br/>(e) as a result of (d) wait for the receipt of the traveller trip description data flow from the Trip Planning function and when it is received, store the trip plan description internally for later use;<br/>(f) output the trip plan description received in (e) to the Pre-Trip Traveller in the initial trip plan data flow;<br/>(g) as a result of (f) wait for a response from the Pre-Trip Traveller in the modified trip parameters data flow;<br/>(h) use the data provided by the data flow in (g) to modify the original trip parameters, put them in the modified trip plan requirements data flow and send it to the Trip Planning function;<br/>(i) as a result of (h) await receipt of the traveller trip description data flow from the Trip Planning function and when it is received store the trip plan description internally for later use;<br/>(j) output the alternative trip plan description received in (i) to the Pre-Trip Traveller in the trip alternatives data flow and wait for a response from the Pre-Trip Traveller in the modified trip parameters data flow;<br/>(k) continue repeating (e) through (i) until no modified parameters are provided by the Pre-Trip Traveller in the modified trip parameters data flow, but giving each revised trip plan description a new identity so that it can be retrieved instead of the other trip plan descriptions;<br/>(l) output the select trip data flow to the Pre-Trip Traveller and await a response through the input of the trip selection data flow;<br/>(m) use the input in (l) to select the required trip plan description from the internal store and check to see if any bookings need to be made and paid for, or the trip plan service needs to be paid for;<br/>(n) if the answer in (m) is YES, send the selected trip plan description to the Make Trip Bookings and Payments function in the full trip description for bookings data flow;<br/>(o) as a result of (n) continuously monitor for receipt of either the request trip planning payment or advanced payment needed data flows from the Make Trip Planning Payment and Bookings function;<br/>(p) then the data flow in (o) is received, send either the request trip planning payment or advanced payment needed by trip plan data flows to the Pre-Trip Traveller and await receipt of either the trip planning payment or booking approval data flows from the pre-trip traveller;<br/>(q) the either of the data flows in (p) is received, send either the trip planning payment or the booking approval data flows to the Make Trip Booking and Payment function;<br/>(r) as a result of (q) continuously monitor for receipt of the full trip description with bookings, or booking mishap data flow from the Make Trip Booking and Payment function;<br/>(s) when the first data flow in (r) is received, inform the Pre-Trip Traveller through the select trip data flow and send the selected trip plan description to the Manage Store of Trip Plan Data function in the plan ready for implementation data flow;<br/>(t) if the answer in (m) is NO, send the selected trip description to the Manage Store of Trip Plan Data function in the plan ready for implementation data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0