Enterprise SOA Erfahrungen und Herausforderungen bei Credit Suisse

Transcription

1 Enterprise SOA Erfahrungen und Herausforderungen bei Credit Suisse 25. Januar 2011 Dr. Georg Hüttenegger, Credit Suisse AG Enterprise Integration Architecture

2 The Challenge of Enterprise IT Systems Complexity September 14th, 2010 / Slide 2

3 Simple IT View: Business Credit Suisse Number 1: Agility and Integration As-is Target Number 2: Control/Reduce Running Costs Unmitigated Run the Bank Costs Steady Run the Bank Costs September 14th, 2010 / Slide 3

4 Agenda Credit Suisse: Short Introduction Credit Suisse Learnings & Challenges Conclusion September 14th, 2010 / Slide 4

5 Credit Suisse Group today key facts Global bank headquartered in Zurich, serving clients in private banking, investment banking and asset management. Registered shares of Credit Suisse Group AG (CSGN) are listed in Switzerland (SIX) and as American Depositary Shares (CS) in New York (NYSE). Total number of employees: 50,500. The Group s long-term ratings are: Moody s Aa2, Standard & Poor s A, Fitch Ratings AA-. September 14th, 2010 / Slide 5

6 Numbers: CS IT in Switzerland as of 10/2009 ~250 million payments/year ~190 million pages A4 output/year 40 million lines of source code in 800 applications 26 million IMS transactions/peak day > 150 project running in parallel September 14th, 2010 / Slide 6

7 Application Domains as logical components 6: Accounting, Controlling and Reporting Regulatory, Risk and Liquidity (RRL) Financial Accounting (FAC) Accounting Control (AOC) 2: Finance, Investm ent & Sales 3: Trading and Markets 4: Cash and Asset Operations 1: Partners & Persons Customer & Partner (CUS) Customer Relationship Management (CRM) CS Clients, Prospects & Public CS Employees Partner Applications Regulators Financial Service Providers Market Data Providers Market Access Communication and Access (CHA) 5: Com m unications & Collaboration Street Side Interfaces (SSI) Business Partner Applications (BPA) Enterprise Content Management (ECM) Financial Market Information (FIN) Payments (PAY) Wealth Management & Advisory (WMA) Trading (TRA) Single Accounts (SAC) Order and Trade Management (OTM) Settlement and Clearing (SCL) Credits and Syndication (CRS) Product Control (PRC) Custody (CDY) Asset Servicing (COA) 7: Enterprise Com m on Services Logistics (LOG) Enterprise Base Solutions (BAS) September 14th, 2010 / Slide 7 V /11/19

8 Public Interfaces Couple Domains as Components Domain Domain Domain Data Data Data App App App App App App Interfaces Interfaces Interfaces CS exchange Bus CS Information Bus Interfaces Domain App App Data Data Data September 14th, 2010 / Slide 8

9 Designing for/managing Service Reuse Services have to be designed for reuse They allow access to an area beyond the direct responsibility of the service consumer Services couple applications together Consumers depend on the services you provide When you change a service many applications can be influenced Modification of reused code is particularly error-prone Services need governance & versioning Re-usable services and their reuse result from strong governance Services & their data types need to be versioned Designing for reuse is difficult. We have to get it right the first time. September 14th, 2010 / Slide 9

10 Technical Perspective of CS X Bus CS X Bus IFMS Provider Integration type Service Integration (synchronous) Message Integration (asynchronous) Bulk Integration (asynchronous) Portal Integration Infrastructure class Service Infrastructure Messaging Infrastructure File Transfer Infrastructure Portal Int. Infrastructure Integration technology SOAP/https CORBA MQ EMS FTPS C:D WSRP JSR 168,286 September 14th, 2010 / Slide 10

11 Credit Suisse does SOA since 1998 Credit Suisse Inform ation Bus since 1998 >1000 services Industry benchm ark PB Global SOA since countries > 50 services 4 back-ends Manage diversity! Disentangling the Mainfram e Apps since 2005 SOA within the mainframe Bringing agility to the m ainfram e BIAN: SOA standards for the financial industry 36 banks/vendors involved Create a m arket for standardized banking com ponents "Credit Suisse succeeded in building a highly business-critical integration infrastructure. The company is fully experiencing the benefits of SOA and the componentization of core business applications. However, to reach that desired state, Credit Suisse went through a lengthy and expensive endeavor that only leading-edge, technically sophisticated enterprises will be able to tackle." Gartner Group September 14th, 2010 / Slide 11

12 Measure Progress: Use of Services Follows Availability services available 600 services available 800 services available 900 services available Wide use of services follows a critical mass of available services Today ~20 Mio. service calls a day Fully decoupled platform some years ahead Channels domain almost completely decoupled from remainder of platform September 14th, 2010 / Slide 12

13 Does IT Architecture Generate Value? Revenue relative to IT costs 2001 (Revenues 2008: CHF 12.9 bn) Revenue relative to IT costs 2005 Technology replacement (Smalltalk, SNA) Application platforms (Java, DWH) SOA, Interface management Formal architecture management Cost reductions >33% Maintenance vs. project costs stable A lot of new functionality (CRM, Internet Banking) Much more business volume Substantially improved stability Since 2007 growth strategy September 14th, 2010 / Slide 13

14 B2B Integration Partner's IT Systems Partner's IT Systems Bus. Process Automation Integration Does Not Stop at Individual Services Desktop Integration Presentation, Portals etc CS Applications CS exchange Bus Workflow Engine Service Oriented Architecture (SOA) Integrate applications with the CS exchange Bus Managed Interfaces Desktop Integration Integrate the user interfaces of applications Create a coherent user experience Business process automation Automate business processes through workflow technology B2B Integration Integrate with IT systems of partners Service oriented Architecture (SOA) September 14th, 2010 / Slide 14

15 Enterprise BPM Requires SOA Users Business processes can be automated on different levels: within one application within one domain across the enterprise Portals Business Processes (BPMS/WFMS*) BPM across the enterprise requires SOA to decompose the application landscape into components that offer their functionality through services Services Components Larger scale of reuse can be achieved by exposing reusable parts of business processes as services Legacy CRM ERP DBs * BPMS: Business Process Management System WFMS: Workflow Management System September 14th, 2010 / Slide 15

16 Key Success Factors A strong central architecture function With a good reputation and senior IT management support Own budget for infrastructure and cleanup CIO basket budget is available and the chief architects administrate it Processes are enforced; no ivory tower architecture Architecture processes are embedded in project work Based on the managed evolution principle Stepwise improvements to reach the long term goal Most importantly: Hanging on to it! September 14th, 2010 / Slide 16

17 Key Learnings Always focus on the business value of architecture Make it THE Enterprise Architecture value proposition Establish unavoidable check points in infrastructure Example: A new CORBA service needs architecture approval within CS otherwise it is not registered with the naming service Ensures that architecture is not just an ivory tower exercise Drawback : This means architecture needs to deliver on its promises! Select a few major principles and drive them through Leave breathing space for the individual projects! A federated approach was ideal for Credit Suisse A strong center supported by decentralized architects September 14th, 2010 / Slide 17

18 Governance Model of Service Review/Quality Checks (QC) Rework Major Modification Rework Rework Rework QC1 Accept QC2 Accept QC3 Accept Accept Simple Case Core questions to pass QC Is this new interface really needed? What is its correct position in the respective Interface Group Hierarchy? Is the interface well specified? Does it use the correct data types? Are the new data types well designed? Was the interface testing and documentation successful and complete? Are all obligations from previous QCs fulfilled? September 14th, 2010 / Slide 18

19 Selected ( ) Challenges Leverage Switzerland success/experiences world-wide Clash of cultures Migrating CORBA service operations to web services The biggest central middleware Credit Suisse Defining & managing global & cross-divisional service definitions Despite different approaches, cultures, legacy systems, To name the most important ones September 14th, 2010 / Slide 19

20 Conclusion Credit Suisse's business needs an agile and cost effective IT Tightly coupled legacy systems are no longer sufficient SOA is key to achieve agility Credit Suisse enjoys most of the promised SOA benefits Re-use is a reality and reduces project costs It is a long road to a successful SOA There are a lot of challenges ahead There is still a lot to do! September 14th, 2010 / Slide 20

21 Thank you. QUESTIONS? September 14th, 2010 / Slide 21