Low Level Function
1.4.1 Distribute Fees Revenue

Overview

This Function shall be capable of providing the following facilities:

(1) The ability to apportion the payments received amongst the operators according to rules defined in the store of Service Information Data.
(2) The ability to send the apportioned payment details to the functionality for crediting Service Operators' accounts.

Functional Requirements

(a) read the information about the transaction, and extract the operators ID and service concerned
(b) extract from the store of "service information" Data the rules to be followed concerning the allocation of revenue for this service
(c) compute the corresponding revenue for each operator
(d) send the result to the Credit Operator's Account function

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 1.4 Manage Operators' Revenue
  • 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.2.1
    The system shall be able to share revenues between road network operators.
    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.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)