Overview

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.

Functional Requirements

(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
(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
(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
(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
(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
(f) when updates to the current demand service criteria are received, change the current locally held data for the criteria
(g) when updates to the road network data are received from the operator, update to locally held data.

Diagrams

Parent Higher Level Function

• 4.7 Provide On-demand Services

Input logical dataflows

• fmms.mms-data_for_demand_services
• mpto_demand_service_payment_successful
• mpto_demand_service_request
• mpto_PT_fares_for_demand_services
• mpto_PT_schdeules_for_demand_services
• mpto_read_demand_services
• mpto_request_demand_criteria
• mpto_update_demand_criteria
• mpto_update_road_network_data
• mt.mpto_inter-urban_road_data_for_demand
• mt.mpto_predicted_road_conditions_for_demand
• mt.mpto_urban_road_data_for_demand

Output logical dataflows

• mpto_confirmed_demand_service
• mpto_current_demand_criteria
• mpto_demand_service_confirmed
• mpto_load_demand_service
• mpto_proposed_demand_service
• tmms.mms-request_data_for_demand_services

User needs