Low Level Function
1.3.7 Recover Fee

Overview

This Function shall be capable of providing the following facilities:

(1) A HMI through which it shall be possible to ask the Traveller or Driver for payment for the selected service.
(2) Once the Traveller or Driver has responded to the request for payment, the ability to check with “Credit Control” for the transaction to be validated.
(3) If the transaction is not valid for some reason the ability to register it as a violation.

Functional Requirements

(a) receive payment elements from 1.3.4 or 1.3.5: amount, payment mode,
(b) ask the user for payment,
(c) check the payment. If an account number is given, and if the number is on the black list, register a violation.
if payment is correct :
(d) confirm with "Credit Control"
(e) in case of a payment made by a freight vehicle, send a receipt to the MFFO area.
(f) send an acceptance message to the user

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 1.3 Perform Electronic Payment Transaction
  • Functional Tree of Area 1

    • Parent Higher Level Function

    Input logical dataflows

    Output logical dataflows

    User needs

    Number

    Description

    4.1.0.1
    The system shall be able to use a variety of relevant payment methods either electronic or not, including central account and post payment, central account and prepayment, on-board account etc.
    4.1.0.2
    The system shall manage customer data (identification, account, rights of residents, etc.).
    4.1.0.3
    The system shall give exact details of any financial transaction to the traveller.
    4.1.0.5
    The system shall be able to use a variety of payment or receipt means, including contactless "smart cards".
    4.1.1.1
    The system shall have a minimum impact on the traffic flow, e.g. a short transaction duration.
    4.1.1.2
    The system shall have a minimum impact on the driving task.
    4.1.1.3
    The system shall not do anything to reduce the safety of either the travellers in the vehicle, or the staff close to the equipment, e.g. in toll booths.
    4.1.2.2
    The system shall enable a single payment to be paid for services offered by different related transport systems (e.g. metro, bus, train, road and parking).
    4.1.3.1
    The system shall be able to exchange financial information between roadside equipment (e.g. toll collection unit) and a moving traveller (e.g. a vehicle).
    4.1.3.2
    The system shall make atomic electronic financial transactions, I.e. that are never partially complete whatever the circumstances, even in degraded system modes.
    4.1.3.3
    The system shall have the maximum security necessary for electronic financial transactions.
    4.1.3.4
    The system shall have a low number of incorrect transactions (e.g., non-effective transactions < 1 in 10E-6; erroneous transactions < 1 in 10E-8)
    4.1.3.5
    The system shall provide information in the native language at the output location, and/or from a user selected choice of other appropriate foreign languages.
    4.1.4.1
    The system shall be able to be able to collect evidence on the non-payment of tolls, and other illegal financial transactions.