Overview

This Function shall be capable of providing the following facilities:

(1) A HMI through which Pre-Trip Travellers can request an On-Demand Service for some or their entire proposed journey.
(2) The HMI shall enable the Traveller to provide information about the proposed journey, such as origin, destination, required times of departure and arrival, plus any other relevant information, e.g. disabled, elderly, luggage and young children.
(3) Once the Traveller has accepted the proposed service, the HMI shall also enable payment to be requested and only confirm acceptance once payment has been completed.
(4) A separate interface through which payments can be transacted in a safe and secure way.

Functional Requirements

(a) when the request demand service data flow is received from the traveller, check that all the required input data is present and sent to the Plan Demand Service function
(b) following (a) when the proposed demand service data flow is received, output the proposed service data flow to the traveller, including details of any payments that are required
(c) following (b), when details of how any payment is to be made are provided by the traveller, send this information via secure link to the financial clearinghouse
(d) following (d), when confirmation of successful payment is received from the financial clearinghouse, send the payment made message to the Plan Demand Service function
(e) when the demand service confirmed message is received, send details of the service to the traveller.

Diagrams

Parent Higher Level Function

• 4.7 Provide On-demand Services

Input logical dataflows

• ffc-demand_service_payment_confirmed
• ft.ppt-confirm_demand_service
• ft.ppt-request_demand_service
• ft.ptt-make_demand_service_payment
• mpto_demand_service_confirmed
• mpto_proposed_demand_service

Output logical dataflows

• mpto_demand_service_payment_successful
• mpto_demand_service_request
• tfc-demand_service_payment
• tt.ppt-demand_service
• tt.ppt-proposed_demand_service

User needs