F6.5.3.9 Plan Trip Details

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.3 Trip Planning / F6.5.3.9 Plan Trip Details

Project:

F6.5.3 Trip Planning

F6.5.3.9 Plan Trip Details : 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:	{2AB906E1-0864-4458-9917-F8388133E990}
Appears In:	SSTP Function Allocation, High Level Function Information Service, DFD F6.5.3 Trip Planning, Functional Tree of Area F6 Provide Traveller Journey Assistance

This Function shall be capable of providing the following facilities: (1) The ability to manage the production of trip plans based on data provided by the Traveller through functionality in other parts of the system. (2) The ability to prepare trip plans for journeys that are either one way, or for a return trip (including weeks/months ahead), and that take advantage of late opening hours, special facilities etc. (3) The ability to check the criteria provided by the Traveller and obtain information for the specified modes to be used in the requested trip, but taking account of the trip planning criteria that have been set up by the Travel Information Operator. (4) The ability to use data from the store of Road Trip Planning Data and/or the store of PT Trip Planning Data, plus also to collect information about Points of Interest (POI) and Personal Services (PS) from External Service Providers. (5) Where specified by the Traveller the ability to request information about the services provided by other transport modes, tolls plus other charges if they will need to be paid in order to complete the proposed trip, and to pass all of this information on to the Provide Traveller Information functionality. (6) The ability to create trip plans for cyclists and pedestrians using the road network data and related perturbations, but disregarding traffic incident information. (7) The ability to revise a part completed trip plan when a Traveller departs in any way from its contents, or travel conditions change, starting from the current Traveller location and mode of travel. (8) The ability to exchange journey time data for each segment of the road network with its implementation in other devices and to plan trips when the only traffic related data that is available this journey time data.

Associations To
Associations From
Requirements
Advanced
Other Links

Element	Source Role	Target Role
«FRAME_High_Level_Function» F6.5.3 Trip Planning FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_traveller_trip_description FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_revised_trip_plan_for_approval FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_road_trip_planning_data_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_requested_trip_planning_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja.pepf_service_contract_info FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.bsp-request_bookable_service_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja.pshvs_vehicle_trip_plan_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_other_mode_data_for_travel_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.gip-request_poi_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.gip-request_ps_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_request_PT_trip_planning_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tesp.mmtip-request_travel_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja.pshvs_revised_vehicle_trip_plan_for_approval FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_poi/ps_data_for_travel_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja.pepf_service_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_toll_data_for_travel_information FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» ptja_retrieved_PT_trip_planning_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.26 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.2 FRAME_User_Need «Servedby»	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_User_Need» 6.1.2.5 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.3.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» 6.4.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_modified_trip_plan_requirements FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_retrieved_road_trip_planning_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.17 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.2.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.ptja_inter-urban_recommended_routes FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.ptja_vehicle_trip_plan_criteria_changes FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_request_trip_planning_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.2.5 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.2.12 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.gip-poi_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.mmtip-requested_travel_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.6.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.ptja_vehicle_trip_plan_request 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» 6.1.2.14 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.ptja_urban_recommended_routes FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.4.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_traveller_trip_requirement FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.13 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.1.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.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.2.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_update_trip_planning_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ptja_revised_trip_plan_requirements FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pshvs.ptja_revised_vehicle_trip_plan_requirements FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.15 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.21 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.25 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.bsp-bookable_service_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 6.4.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.gip-ps_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 6.1.2.11 FRAME_User_Need «Servedby»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for the receipt of the traveller trip requirements and vehicle trip plan request data flows;<br/>(b) when the traveller trip requirements data flow is received in (a), request data objects about the road network and PT services from the appropriate Data Stores and use them to create a trip plan that fulfils the Traveller's trip request;<br/>(c) in addition to (b) include in the trip plan a choice from different routes for the road part of the trip that use the motorway networks, secondary road networks, scenic routes and so forth depending on the criteria provided by the Traveller and the travel information Operator, plus recommendations received from TCC's in the inter-urban recommended routes and urban recommended routes data flows;<br/>(d) in addition to (b) and (c) include in the trip plan a choice of travel modes, where they provide sensible alternatives, or have been requested by the Traveller;<br/>(e) in addition to (b) and (c) include in the trip plan information about bookable services (e.g. accommodation, plus leisure and sporting events) that will be available at the time of the proposed trip and have been obtained from data objects provided by the relevant Terminators;<br/>(f) if required by the Traveller details of both single and return trips, including those where the date of the return part of the trip may be some time ahead of that for the outward part shall be included in the trip plan;<br/>(g) when the preparation of a new/revised trip plan is completed, it shall be sent back to the Traveller interface in the traveller trip description data flow;<br/>(h) as a result of (g) continuously monitor for receipt of the modified trip plan requirements data flow and if received within a short time, repeat (b) to (g) using the revised requirements;<br/>(i) when the vehicle trip plan request data flow is received in (a), use the data it contains to produce a vehicle based trip plan, fulfilling the requirements of (c) and (e) but include other information such as the need to book parking places for freight vehicles so that goods can be loaded or unloaded;<br/>(j) when the preparation of a new/revised trip plan is completed, it shall be sent back to the vehicle interface in the vehicle trip plan response data flow;<br/>(k) all trip plans shall include any appropriate warnings about the existing conditions, safety recommendations and the expected conditions at the planned time of travelling on the route(s) that they include;<br/>(l) when revising a part completed trip plan, propose alternative modes and/or times of travel to those in the remainder of the plan;<br/>(m) all trip plans shall be produced according to criteria that are set up and modified by the travel information operator so that trips conform to the current travel and/or traffic management policies;<br/>(n) it shall be possible to prepare trip plans with a minimum set of road traffic data that only includes travel times for each segment of the road network;<br/>(o) continuously monitor for receipt of any of the data flows from the Provide Trip Planning Operator Interface function;<br/>(p) when the request trip planning criteria data flow is received in (o), collect the criteria from the internal store of criteria used in (c) and send it back the toe Provide Trip Planning Operator Interface function in the requested trip planning criteria data flow;<br/>(q) when the update trip planning criteria data flow is received in (o) use its contents to update the internal store of criteria used in (c);<br/>(r) continuously monitor for receipt of the vehicle trip plan criteria changes data flow;<br/>(s) when the data flow in (r) is received, update the part of the internal store of criteria used in (c) that is used to prepare vehicle trip plans.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
Service Provider Main Application	Object	Usage	From