TEMENOS T24 – Overview

TEMENOS EDUCATION CENTRE

Copyright © 2004 TEMENOS HOLDINGS NV

1
 Open Standards

• TEMENOS T24 runs on

– Open hardware

– Open database

– Open J2EE application server

– Open user interface through browser, HTML and

XSLT

– Open connectivity through XML and Web services

07 December 2004

Clients can select the best vendor or environment to suit their own needs –
whether this is low cost, high performance, local support or any other factor.
If this changes in the future, they can switch vendor without altering their
investment in TEMENOS T24.
This will provide true longevity in their chosen system.

2
 Scalability

• TEMENOS T24 can support

– 1,000 transactions per second

– 10,000 signed on users

– 100,000 signed on internet users

– 50,000,000 accounts

• Achievable through scalable architecture that permits

to add further servers as volumes expand

07 December 2004

High volumes are achieved through an efficient and scalable architecture that
permits clients to add further low cost servers as volumes expand.
They do not need to constantly push the boundaries of their hardware with all
the risk and expense that this entails.

3
 Non stop operation

• The ability to run Non Stop is an additional product that must be

purchased and installed
• The initial version of Temenos T24 provides non-stop
processing for the following applications:
– CUSTOMER
– ACCOUNT
– FUNDS.TRANSFER
– STANDING.ORDER
– TELLER
– TELLER.ID
– SEC.OPEN.ORDER

07 December 2004

A normal End of day procedure involves:

Stop online work
Take Back up
Execution of EOD jobs defined in BATCH application
Take Post EOD back-up
Ready to start Online

Now, non-stop processing is possible as an additional product – NS.

Transactions can be input while COB (close of business) is running. This is available from
from G14 release.

4
 Temenos T24 Technical Architecture

Zero footprint

Presentation
MQ
APIs Multi-channel
Scale

Excel etc.
SOAP

Browser GIB Internet Web Services Enterprise Console Other connectivity Open, e.g. Tivoli
API – Java and COM

Network Dispatcher Web Server,

e.g. Apache Tomcat
NO
Connectivity

HTTP Server TCP/IP

SINGLE MQ Series
Scale

POINT J2EE J2EE Server,

OF Websphere, Oracle,

XML
Weblogic
FAILURE EJB Container

Linux, IBM I/Z Series,

Presentation Presentation Presentation
Application

HP,Unix, Windows
Scale

C object code
Server level API
Common presentation
NON-STOP
No batch Non Stop!
Database

Oracle, DB2, J4
Scale

Cluster etc.

07 December 2004

5
Temenos T24 Functional features

• Temenos T24 is a product for the international

financial services market
• It has comprehensive functions
Integration
Timely (both in batch and real time)
Multi-currency
• It has core functionality
• It has optional Applications

07 December 2004

6
 TEMENOS T24 Functional Architecture

Web Call Centre Mobile Channel Services Browser Web Svcs IVR

Version Presentation Enquiry

Security Management System

Static Contact History Overview Customer Profitability Preferences and Groups

Retail Trust /Private Treasury Corporate General

Wealth Management

Asset Management FX Trade Finance Nostro Recs

Accounts Performance
DDA, checks, cards, Modeling… Money Market Commercial Loans Confo matching
statements, charges, Funds Transfer
sweeps, direct debits Fiduciaries Swaps Guarantees Euro
Mortgages / loans Fixed deposits FRA Cash Management Past Due
Brokerage Intermediary comp
Teller Order processing Repos Syndicated Loans
Corporate Actions… Tax
Mutual Funds* Capital Markets Leasing Image
Planning
Futures/Options Bills Document mgt

Accounting Multi Dev Toolkit Workflow Risk Delivery

CORE Exception STP Limits / Collateral Swift / FIX
General Ledger Company, ccy Programming
Support Modules Dispo Market Risk Print / Telex / Other
MIS / Profitabilty Language, GAC Database

Security Management System

07 December 2004

We have an overview of the TEMENOS T24 banking system here.

The Core part of Temenos T24, is the most essential part, around which the
optional modules are built. Security Management System over encompasses
the core and optional modules.

7
Temenos T24 Customisation

 Security Management System

Retail
Temenos T24 Core Treasury
Teller FX
Funds Transfer & Risk Management
Customer Money Market
Standing Orders
 Integrated CIF  Credit Risk Repos
Branch System  Addresses  Market Risk
Collateral FRAs
 Current & Savings

Accounting Utilities IRSwaps

Loans
 General Ledger  Reports
Commercial Loans Private
 Accounts  Inquiries
Trade Finance  Interest Rates  Screens & Menus Fiduciaries
 Sector  Word-Link
Guarantees  Charges  Excel-Link Securities
 Commissions
Past Due  Currency Image Portfolio mgmt

Mortgages MIS / Profitability

Messages/Clearing Legend:
Regulatory Reporting
 Print
Other  Core
SWIFT SID Interface
EURO
Module
Multi-Company Custom Interfaces
OFS Customization
GIS
Nostro Recon.

RDBMS
07 December 2004

8
 Temenos T24 Customisation scope

Parameters &
Conditions Local Reference Fields

Screen Design
Temenos T24
(Version) Implementation Enquiries & Reports
Tape

User defined Routines Default field data

Customised
Temenos T24

07 December 2004

Every bank has its own unique needs. Though `Model banks’ have been built,
still banks would like to have their own choices of conditions, and hold
additional information, would like to have user friendly screens with default
conditions and above all get their own reports other than the standard enquiries
and reports.
This calls for a project type of implelementation out of a product. Temenos
T24 is flexible enough to allow all these.

9
 Initial System build

• Temenos T24 Core Tables

– Banking / Financial
– Customers / Account
– Limits etc
• Application Parameters
– Treasury : FX, MM, FRA, IRS
– Lending : LD, MG, SL, etc
– Securities
– Operations: FT, TT etc

07 December 2004

Mandatory core tables include Country, Currency.Market, Currency.Param,

Currency, Holiday, Language etc. Financial control tables include Category,
Consolidate.cond, Interco.Parameter etc.

10
Custom System build

• Local references

• Screen versions

• Menus

• Enquiries

• Reports

07 December 2004

11
 Temenos T24 Functionality

or

Transaction Input Authorizer Queries

 Security Management System

RDBMS
APPLICATION LOGIC

Temenos T24 Core

End-
End-Of-
Of-Day
 Accruals
 Validation  Maturity Control
 Reporting
AUTHORIZED  Revaluation
UNAUTHORIZED

Static Data
Risk Management Messages/Clearing Accounting
 Product
 Interest Rates  General Ledger
 Credit Risk  Print
 Commissions  Debits/Credits
 Market Risk
 Currency SWIFT SID Interface
MIS / Profitability
 etc... Collateral
Custom Interfaces Regulatory Reporting

07 December 2004

Any Temenos T24 operation passes through SMS and reaches Core.

Relevant Static Data are used and limits are affected before authorisation in
case of debits (and after authorisation in case of credits). The deal is then
authorised by a user other than the original initiator (Maker and Checker are
different). Then the respective delivery messages are generated, required
accounting entries generated. The requisite End of the Day (EOD) operations
are performed by batch process for generation of reports, effect accruals, carry
on necessary revaluations etc.

12
 File stages

• Unauthorised

• Live

• History

07 December 2004

When a record is input and committed, the data is stored in an Unauthorised

stage.

When this record is authorised, it moves to Live stage.

When an authorised record is modified to create a new record or reversed, the

data moves to History stage.

It is possible to restore a History file and bring it back to live stage.

13
 Vocabulary

• Modules (Business products)

• FX, Funds Transfer

• Applications (Programs to run Temenos T24)

• CUSTOMER, ACCOUNT

• Tables / Files (Data storing objects)

• CURRENCY, RATES

• Records (Individual transactions)

• Fields
• Standard and Local Reference

07 December 2004

Modules – the business products that are within the Temenos T24 banking
system such as FX and Trade Finance
Applications – These are the programs required to run Temenos T24 – eg
CUSTOMER, ACCOUNT. Applications cannot store data. They are front end.
Tables/Files - The data input in the Applications are stored in Tables. While
Applications are like Front ends, Tables are the actual objects that store data
entered via applications. Data input in Account application is stored in tables
like Account and Customer.Account.
Records - Individual transactions within Temenos T24. For example, each
payment transaction is known as a payment record and each Customer will have
a customer record.
Fields – These are either Standard fields or LOCAL REFERENCE fields . Many
fields are mandatory as they require input for Temenos T24 to perform another
operation from this data.

14