Arrow Asset Management

Banking Software Package Questionnaire

27/06/01

1.

GUIDANCE FOR
QUESTIONNAIRE

REPLYING

TO

THE

Please make sure in replying to the questionnaire that:

1.

You answer all the questions included.

2.

Give in all applicable cases a Yes/No/Partially answer. Then expand with

clarifications if needed.

3.

Be as specific as possible.

4.

Regarding the functionality questions please answer with a short paragraph

of free text.

In the appendix you will find the commercial specification of a specific product.
Please provide a detailed description (providing samples of screens and reports)
of:
1.

How this product would be set-up in the package

2.

What automation for administering the product would be available.

2.

QUESTIONNAIRE

2.1.

Functionality

Phase 1
1.

What are the main features of Statutory Returns and reports in your
system?

2.

What are the main features for supporting customer profiles in your system?

3.

What are the main features of Cash (teller transactions) services in your
system?

4.

deposits (time, savings, checking)

4.1.

what are the main features of Current accounts in your system?

4.2.

what are the main features of Savings accounts in your system?

4.3.

what are the main features of Deposits in your system?

4.4.

what are the main features of Terms accounts in your system?

4.5.

what are the main features of Credit accounts in your system?

5.

Payments (ATM, transfers, checks)

6.

What are the main features for Fund transfering in your system?

7.

What type of credit/debit cards does the package support?

8.

Brokerage (MFs, Asset management, Insurance)

9.

What are the main features of Standing orders in your system?

10.

What are the main features of GL in your system?

Phase 2
11.

What are the main features of Mortgage Loans in your system?

12.

What are the main features of Capital markets in your system (Securities)?

13.

What are the main features of Private banking in your system?

14.

What are the main features for Cheque & Draft Management / Clearing
(truncation) in your system?

15.

Does the system provide CREDIT / RISK Management functionality?

16.

What are the main features of FX & MM in your system?

17.

What are the main features of Collaterals in your system?

18.

What kind of real time market information system does the package connect
with (please provide reference implementations)?

19.

Does the package provide activity monitoring for sales representatives

(commission based agents)?

20.

Does the package provide for fee calculation of sales representatives?

Generic functionality
21.

Is the package multi-entity?

22.

Is the package multi-branch?

23.

Is the package Euro-compliant (please expand)?

24.

Can the base currency be parametrically specified?

25.

Does the package provide flexible product factory (please expand and also
see appendix).

26.
27.

Is the package based on the customer centric concept?

To what extent can the 4 eyes principle be applied in transactions,
(secondary verification)?

28.

Does the system provide on line signature verification?

29.

On what bases can banking day calendars be defined?

30.

What are the main features of Audit trail in your system?

31.

Does the system provide data warehousing functionality?

32.

Does the system provide MIS functionality?

33.

Does the system provide CRM functionality?

34.

Does the system provide Call Centre functionality (If yes please describe it.
What CTI and IVR packages are used, what is the architecture of the call
centre solution)?

35.

Does the system provide EIS functionality?

36.

Does the system provide Campaign Management functionality (Please

expand)?

2.2.

Technology

Architecture
37.

What type of architecture is the package based upon (monolithic, client

server, n-tier)?

38.

Is the package web based?

39.

Is the system modular (Please list the modules)?

40.

Are modules independent

dependencies).

41.

Describe (preferably using a diagram) the physical architecture of the

package.

of

each

other?

(Please

specify

any

Scalability
42.

Specify the maximum number of users/transactions/accounts that the

system is designed to support.

43.

Specify the maximum number of users in an existing implementation

(specify the implementation as well and the hardware being used).

44.

Specify the maximum number of branches in an existing implementation

(specify the implementation as well and the hardware being used).

45.

Specify the maximum number of accounts in an existing implementation

(specify the implementation as well and the hardware being used).

Development / Customization / Reporting tools

46.

Which tools has the package been developed with?

47.

Is the package customizable? With what tools (including reporting ones)?

Are they a proprietary, standard, third party tool?

48.

Is the package component based? If yes which is the technology?

Integration & Connectivity

49.

Is there a standard interfacing mechanism that does not require knowledge

of the DB schema?

50.

Is there a standard mechanism for automating transaction entry?

51.

Is there a standard mechanism for uploading static data?

52.

Does the package support an Application Programming Interface (API)? If

yes, is it guaranteed backward compatible across different versions?

53.

Does the package provide its own middleware platform? If yes, please
expand.

54.

If not please explain how you integrate your platform in a multi-channel

environment.

55.

Does the package provide integration with office automation tools (Please
expand briefly)?

56.

Has the package ever been integrated with Kana middleware product? If
yes, please specify the implementation and the technology used.

57.

Has the package ever been integrated with CRM applications? If yes,
please provide some specifics.

58.

How are the back end transactions of the package exposed (i.e. 3271 CICS
transaction, string CICS transaction, RPC transaction, CORBA/DCOMCOM+ objects etc)?

Platforms
59.

Which operating systems can the package operate under (separately for
Server & Client if applicable)?

60.

Which database/s is/are used by the package?

61.

Is it/are they relational? If not, is an SQL standard interface provided?

Realtime processing (24x7)

62.

Does the package use an overnight batch processing? If yes, can it run
unattended?

63.

Does the package provide non-stop processing (real-time processing 24

hour x 7 days) (Please expand on mechanism used)?

64.

Does the package possess branch offline operation capability?

Security
65.

Explain all the levels that access rights are provided at?

66.

Does the system support user group profiles? If yes, can a user belong to
more than one groups?

67.

In which cases does the user need to provide a password?

Multi channel
68.

Does the package provide on multi-channel capabilities?

69.

Does the package provide ATM and POS connectivity?

70.

Does the package provide capabilities for phone-banking and web-banking?

Languages
71.

List the languages that the package supports.

72.

Are all screens and reports provided in the supported language?

73.

What is the mechanism for adding a currently non-supported language?

2.3.

Vendor capacity to execute and vision

Company size
74.

Please, provide company revenue for the last three years.

75.

Please provide revenue from the package in the last three years.

76.

Please, provide company staff numbers for the last three years.

Capacity to Execute
Geographic coverage
77.

Where are the headquarters of the company?

78.

Please, provide information about company presence in European

Countries (Offices, Subsidiaries, Distributors, Partner system integrators)
(indicate the type of presence as per above list).

79. Please, provide information about EMEA general partnership and alliances
Installed base
80.

Please, provide reference sites in Greece, Spain, Belgium, France, Italy.

Reference sites should be the closest possible to:
1. Retail Bank with small number of branches (10-30).
2. Functionality supported as per section 4.1.
3. Implementation time (Phase I functionality) 3-6 calendar months.
4. Multi-channel operation, preferably supported by the package.
5. Integration / connection with CRM.

6. Integration / connection with Date warehousing / Data Mart / Data

Mining.
Outsourcing
81.

Do you or some of your partners provide outsourcing services in Europe? If

Yes:
81.1.

In which countries?

81.2.

How many banks customers do they manage? (Please site

references).

Maintenance

82.

Maintenance services are provided by yourselves or by a third party

regarding the following items:
82.1.

Package.

82.2.

Operating System.

82.3.

Database Management System.

82.4.

Development / Customisation / Reporting Tools.

Package Future Direction

Please describe very briefly (in one short paragraph per question):
83.

The main functionality upgrades planned for the next major release.

84.

The main technology evolution planned for the next two years.

85.

What is the typical time between major releases of the product (please
provide dates for 3 previous major releases)?

2.4.

General Information

Implementation Time
86.

Assuming minimum customisation please provide rough estimates as per

following table:
Calendar
Time

Person-month
time

Team-size

Implementation
Cost (in Euros)
(Services only)

Phase I
Functionality
Phase II
Functionality
87.

Do you provide a pre-configured release of the package? If yes, please

provide details of reference sites where it has been used.

3.

COSTS

Services
88.

Please explain the cost drivers (i.e. Authorised users, concurrent users,
number of accounts, number of transactions, number of installations,
modules, etc.) for the following types of cost:
88.1. Licenses
88.2. Maintenance
88.3. Customisation
88.4. Implementation
88.5. Training
88.6. Upgrades

89.

Please analyse an estimate for the full 3 year cost of the package, excluding
implementation services:

10 Branches

100 Users

10000 Customers

20000 Accounts

1 Installation

Phase I functionality for the 1st year.

Phase II functionality for the 2nd and 3rd years.