Low Level Function
1.1.1 Create EP Contract

Overview

This Function shall be capable of providing the following facilities:

(1) A HMI through which the Traveller can establish a contract with an Electronic Fee Collection Operator, or a Service Provider.
(2) The HMI shall present the Traveller with information about the different types of services available, and record the choices that they make for use by other functionality.

Functional Requirements

(a) read user's request : type of service on which information is required,
(b) receive corresponding elements from the "Provide Traveller Journey Assistance" Function.
(c) display corresponding information to the user
(d) read user's choice
(e) write contract
(f) display the contract to the user, record it in the store of "EP contract" Data.

Diagrams

The Diagram(s) is (are) the diagram(s) where you can find the function :
  • DFD 1.1 Set up Contract
  • 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.4
    The system shall be able to manage tariff policies (define fares/fees according to selected criteria, e.g. type of Traveller or traffic conditions, 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.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.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.