Vietnam Banking 2006

Callatay & Wouters Presentation 18th May 2006 Vietnam Banking 2006 Ariff Sultan, Commercial Director (Asia Pacific) 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. Callatay & Wouters Background – www.c-w.com.sg Presence Company Profile Partner in Vietnam - HPT Vietnam Corporation 2006 Dubai 2005 : 39 million EUR Consistent, strong profitability Revenue Company Profile Some references Company Profile The Enterprise of the Year 2005 award C&W wins the Enterprise of the Year 2005 award organized by Callatay & Wouters Thaler, Kyudo and Teran Banking solutions Products 20th Century Banks Banking solutions Use of ATM Email Call Centre Branch Web Mobile Intelligent service, efficient, end to end ? Bank’s IT Problem Definition (Source: Celent, 2003) “ Applications responsible for processing and posting transactions, performing deposit accounting, maintaining loan accounts, keeping securities and treasury positions and clearing payments.” 21st Century Core Banking Retail Bank Model Shifts (Source: Mercer Oliver Wyman, 2005) Bureaucracy Manage P&L, Balance-sheet Compete for market share Manage sales Product-value Compete for customer value Manage local market Mixture of Products Products-Based Seller Retailer Customer = Irritant Customer = Sales Opportunities Customer = Customer Banking Business Models 21st Century Environment (Source: BearingPoint, 2005) More intense regulatory demands Emergence of new competitors in Asia. Expansion of Chinese and Indian Banks in Asia. IT outsourcing trend in the banking industry – possible re-thinking and a new business model Accelerated expansion regionally and globally. Further consolidation of Banks. Mass affluent and High-nett worth customers. Private Banking in the Retail space. Financial Spa due to customer sophistication “I want an Innovative Bank” 21st Century Banking solutions 21st Century Banking Software Technology & Operations 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 21st Century Banking solutions Our Proposition to Vietnamese Banks: 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 21st Century Banking solutions Your Bank’s Business Requirements for Core Banking? Thaler : Latest Version dated 2005 Source: KPMG Financial Services – Banking System Survey 2005 Callatay & Wouters Presentation 18th May 2006 Vietnam Banking 2006 Erik Bogaerts, Director Asia Agenda SOA: the right choice for you? Revolution or evolution? Service Oriented Architecture (SOA) Business Process Management (BPM) Are SOA and BPM for you? First wave: MRP Payroll General Ledger 1970s-1982 Host-based Architecture Middle wave: ERP Human res. Financial Mgt 1983-1993 Client/Server Architecture Last wave: CRM Early Web applications 1994-2002 Early N-Tier Architecture Source : Delphi Group New wave: Process Orchestration Composite application 2003+ Service Oriented Architecture Revolution or evolution? Service Oriented Architecture 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 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 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 jThaler Global scheme Technical architecture service bus JSP & JSF views Servlet controller Backing Beans Web Server INTERFACES Application Server RDBMS Any platform BusinessServices BusinessServices BusinessServices BusinessServices … Process-centric Services Any platform Other F-E Service Repository WSDL jThaler Front-End architecture Technical architecture service bus JSP & JSF views Servlet controller Backing Beans Web server INTERFACES Application Server RDBMS Any platform BusinessServices BusinessServices BusinessServices BusinessServices … Business Process Manag’t Any platform 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 jThaler Service Architecture Technical architecture service bus Thaler Front-end Application Server RDBMS Any platform Business Service Interface Other Front-end JCA connector Java Business Methods Data Access Layer Service Repository WSDL Web Services Local Interface Remote Interface WS Proxy Thaler v2 Any EIS 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 Main characteristics 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 Service architecture Implementations 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 Service architecture Process-centric services : definitions What’s 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 Service architecture c Application Server J2EE Generic InterfaceexecuteOperation Method JCA connector Java Business Methods Web Services Local Interface Remote Interface WS Proxy Data Access Layer jThaler Service Architecture : Orchestration with BPMS service bus Thaler Front-end Any other Front-end BPMS Process Interface Service Repository WSDL Interface Implementation Web Services WS Proxy Application Server Service architecture Process-centric services : Package CLA1 Add new client CLAM Add client portfolio DVA4 Add securities account CCA1 Add client account Service architecture CGC3 Check Balance CNA3 Grant condition jThaler Business Objects Architecture Technical architecture service bus Front-end INTERFACES Application Server RDBMS Business Services JDBC Generic DAO Implementation Specific DAO Implementation Extendable DAO interface 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 "Things should be made as simple as possible, but no simpler." - Albert Einstein -