F4.7.2 Plan On-Demand Services

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.7 Provide On-demand Services / F4.7.2 Plan On-Demand Services

Project:

F4.7 Provide On-demand Services

F4.7.2 Plan On-Demand Services : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:33
Modified:	08.09.2021 11:24:41

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{C62A6214-31B0-4554-9747-556EAFA428F0}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4.7 Provide On-Demand Services

This Function shall be capable of providing the following facilities: (1) The ability to plan the On-Demand Services following requests from Pre-Trip Travellers. (2) The ability to plan the Services using the Traveller's requirements, plus data about the road network, current traffic conditions, current scheduled PT services, the services provided by other modes of transport and where appropriate any Services already in progress. (3) The ability to plan Services using routes that shall be the most efficient within the constraints provided by the Travellers in the Service requests and may make use of existing scheduled services provided by PT operations and those of other transport modes. (4) Once the Service route, timings and cost have been determined, it shall be possible for them to be sent to the Traveller interface functionality. (5) When confirmation is received from the Traveller interface functionality, the Service details shall be sent to the implementation functionality, (6) If the Service is rejected, it shall be possible for the route and other Service parameters to be re-determined before they are again sent to the Traveller interface functionality. (7) The ability for the criteria used to produce the route for the Service to be updated by data from the functionality providing the HMI to the On-Demand Service Operator.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_current_demand_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_confirmed_demand_service FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_demand_service_confirmed FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_proposed_demand_service FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Functional_Area» F4. Manage Public Transport Operations FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_load_demand_service FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.7 Provide On-demand Services FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tmms.mms-request_data_for_demand_services FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_PT_schdeules_for_demand_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_read_demand_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_demand_service_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_update_road_network_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_demand_service_payment_successful FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_update_demand_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.1.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_predicted_road_conditions_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_demand_criteria FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_fares_for_demand_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_inter-urban_road_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-data_for_demand_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_urban_road_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously receive data about current road and traffic from the Manage Traffic functionality plus details of services from Manage Public Transport functionality and store it locally;<br/>(b) when a request for an on-demand service is received from the Traveller interface functionality, review all the planned and active on-demand services to see if there is a "fit" and if so send the proposal to use this service (including required payments) to the traveller interface functionality;<br/>(c) if there is no "fit" with an existing on-demand service. use the collected data from (a) to determine the most efficient on-demand service using the current criteria and send details of it (including required payments) to the traveller interface functionality and load it into the store of On-Demand Services Data;<br/>(d) when confirmation that any required payment has been made is received from the traveller interface functionality, finalise the proposed on-demand service and return it to the traveller interface functionality as well as to the Implement function and update it in the store of On-Demand Service Data;<br/>(e) when a request for the current demand service criteria is received from the Operator, respond to the operator interface functionality with the current data;<br/>(f) when updates to the current demand service criteria are received, change the current locally held data for the criteria;<br/>(g) when updates to the road network data are received from the Operator, update to locally held data.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0