Callatay

1
Callatay Wouters Presentation
18th May 2006
Vietnam Banking 2006 Ariff Sultan, Commercial
Director (Asia Pacific)
2
Callatay Wouters
Background www.c-w.com.sg

• Started business in 1983, at Brussels
• Mission is to deliver innovative financial
  software solutions
• Principle Business activities are
• Licence Thaler, Kyudo and Teran solutions
• Consulting Project Management
• Delivered several successful European Banking
  solutions since 1983
• Developed Thaler Version 1 in 1996 and Version 2
  in 2001.
• Global Staff strength of 360 with Banking and
  Technical Experts.

3
Presence
Company Profile
2006
Dubai
Partner in Vietnam - HPT Vietnam Corporation
4
Revenue
Company Profile

• 2005 39 million EUR
• Consistent, strong profitability

5
Some references
Company Profile
6
The Enterprise of the Year 2005 award
Callatay Wouters

• CW wins the Enterprise of the Year 2005 award
• organized by

7
Thaler, Kyudo and Teran Banking solutions
Products
8
20th Century Banks
Banking solutions
Use of ATM
9
Banks IT Problem
Email
Call Centre
Branch
Web
Mobile
Intelligent service, efficient, end to end ?
10
Definition (Source Celent, 2003)
21st Century Core Banking
Applications responsible for processing and
posting transactions, performing deposit
accounting, maintaining loan accounts, keeping
securities and treasury positions and clearing
payments.

11
Retail Bank Model Shifts (Source Mercer Oliver
Wyman, 2005)
Banking Business Models
Products-Based
Seller
Retailer

• Compete for market share
• Manage sales
• Product-value

• Compete for customer value
• Manage local market
• Mixture of Products

• Bureaucracy
• Manage PL, Balance-sheet

Customer Irritant
Customer Customer
Customer Sales Opportunities
12
21st Century Environment (Source BearingPoint,
2005)
21st Century Banking solutions

• IT outsourcing trend in the banking industry
  possible re-thinking and a new business model

• Accelerated expansion regionally and globally.
  Further consolidation of Banks.

• Emergence of new competitors in Asia. Expansion
  of Chinese and Indian Banks in Asia.

• More intense regulatory demands

• Mass affluent and High-nett worth customers.
  Private Banking in the Retail space.
• Financial Spa due to customer sophistication I
  want an Innovative Bank

13
21st Century Banking Software Technology
Operations
21st Century Banking solutions

• Service-Oriented Architecture solution
• Open solutions
• Decision Support
• Innovative products customised offering
• Quick to Market quick to implement
• Parameterisation
• Workflow-based, STP
• Best practices Re-engineering
• 24X7 operations and support

14
Our Proposition to Vietnamese Banks
21st Century Banking solutions

• Thaler, Kyudo and Teran are Service-Oriented
  Architectured Core Banking solutions
• Single, core solution for Retail, Wholesale,
  Treasury, Corporate, Securities and Wealth
  Management Banking (Universal Banking)
• Low risk, Stable, proven software with 35
  installations world-wide
• High customer satisfaction KPMG Banking System
  Survey 2006
• High value to the enterprise KPMG Banking
  System Survey 2006
• Quick Payback to the investment

15
Your Banks Business Requirements for Core
Banking?
16
Thaler Latest Version dated 2005
Source KPMG Financial Services Banking System
Survey 2005
17
Callatay Wouters Presentation
18th May 2006
Vietnam Banking 2006 Erik Bogaerts, Director Asia
18
Agenda
SOA the right choice for you?

• Revolution or evolution?
• Service Oriented Architecture (SOA)
• Business Process Management (BPM)
• Are SOA and BPM for you?

19
Service Oriented Architecture
Revolution or evolution?

• Middle wave
• ERP
• Human res.
• Financial Mgt
• 1983-1993
• Client/Server
• Architecture

• First wave
• MRP
• Payroll
• General Ledger
• 1970s-1982
• Host-based
• Architecture

• Last wave
• CRM
• Early Web applications
• 1994-2002
• Early N-Tier
• Architecture

• New wave
• Process Orchestration
• Composite application
• 2003
• Service Oriented
• Architecture

Source Delphi Group
20
Why SOA?
Service Oriented Architecture

• SOA an architectural style whose goal is to
  achieve loose coupling among interacting software
  agents.
• SOA architecture based on
• Application front-end (service consumer)
• Service and service provider
• Service repository
• Service bus
• Service defined by a contract, interface(s) and
  an implementation

21
Why SOA?
Service Oriented Architecture

• Implementation Multi-tier architecture
• Isolate system responsibilities in different
  tiers
• Reduce coupling between tiers
• Standards strongly recommended
• Framework set of tools, rules, standards to
  efficiently develop new programs
• SOA must
• Facilitate integration of different applications,
  whatever their technologies
• Allow easy business process building by
  assembling of basic services

22
Why a Business Process layer?
Service Oriented Architecture

• Isolating business process from
• Banking business logic
• Technological platforms
• One solution for multiple companies, cross-border
• Convergence with other added-value projects
• Basel II
• ABC
• Quality (TQM, 6s,)
• SOX
• AML

23
jThaler Global scheme
Technical architecture

Other F-E

• JSP JSF views
• Servlet controller
• Backing Beans

Any platform
Web Server
Service Repository WSDL
service bus
INTERFACES

BusinessServices
BusinessServices
BusinessServices
BusinessServices

Process-centric Services
Any platform
Application Server
RDBMS
24
jThaler Front-End architecture
Technical architecture

• JSP JSF views
• Servlet controller
• Backing Beans

Any platform
Web server
service bus
INTERFACES

BusinessServices
BusinessServices
BusinessServices
BusinessServices

Business Process Managt
Any platform
Application Server
RDBMS
25
Front-end Architecture Responsibilities
Front-end Architecture

• Presentation  send XML/HTML document over HTTP
  (static and dynamic content)
• Page navigation, including user help
• Syntaxic validation
• Format (account, amount, number, VAT number, )
• Shortcuts (J for today, 3M for 3 months, )
• Required fields
• State management
• Error Exception handling
• Access to business services - No business logic
  in the front-end

26
jThaler Service Architecture
Technical architecture
Thaler Front-end
Other Front-end
Business Service Interface
Service Repository WSDL
service bus
Local Interface
Remote Interface
WS Proxy

JCA connector
Java Business Methods
Web Services
Thaler v2 Any EIS
Data Access Layer
Any platform
Application Server
RDBMS
27
Service Architecture Responsibilities
Service Architecture

• Reduce the coupling between the web tier and the
  business tier
• Provide a framework for basic as process-centric
  services (reduced remote method calls)
• Distribute services through a standard service
  based interface
• Manage generically cross-cutting functions
  (security, audit trail, logging)
• Transaction management

28
Main characteristics
Service architecture

• Stateless service
• Integration
• Local Interface
• Remote Interface
• Web Service proxy
• Interfaces
• Specified Business Methods
• J2EE generic interface with unique method and
  unique signature executeOperation
  (operationName, List of Fields)
• Metadata
• Service Operations - Messages I/O Fields (?
  WSDL)
• Implementation type

29
Implementations
Service architecture

• Full Java
• POJOs no intrusion of technical functions
  (delegated to technical layer EJB, AOP, )
• Methods operations
• Mapping between message string fields and BO
  typed fields defined in data dictionary
• JCA
• one TP per operation
• mapping via data dictionary
• Web Services e.g. process-centric services

30
Process-centric services definitions
Service architecture

• Whats a business process ?
• A flow of coordinated tasks triggered by a
  specific event in order to achieve a specific
  goal.
• Modeling processes
• Graphical tools
• UML standard Business Process Modeling Notation
• Executing processes
• Designed processes can be instanciated and
  executed
• OASIS standard Business Process Execution
  Language

31
jThaler Service Architecture Orchestration with
BPMS
Service architecture
Thaler Front-end
Any other Front-end
J2EE Generic InterfaceexecuteOperation Method
Service Repository WSDL
service bus
Local Interface
Remote Interface
WS Proxy
WS Proxy
BPMS Process Interface
c
Interface


Implementation Web Services
JCA connector
Java Business Methods
Web Services
Data Access Layer
Application Server
Application Server
32
Process-centric services Package
Service architecture
CLA1 Add new client
CLAM Add client portfolio
CCA1 Add client account
DVA4 Add securities account
CGC3 Check Balance
CNA3 Grant condition
33
jThaler Business Objects Architecture
Technical architecture
Business Services
Front-end
Extendable DAO interface
service bus
INTERFACES
JDBC

Generic DAO Implementation
Specific DAO Implementation
Application Server
RDBMS
34
BO Architecture Responsibilities
Business Objects Architecture

• Reduce the coupling between the business tier and
  the data tier
• Business objects definition and access methods
• Relationships with other Business objects
• Handle concurrency
• Provide a framework for O/R mapping
• Business objects persistence

35
"Things should be made as simple as possible, but
no simpler." - Albert Einstein -
36
(No Transcript)