ba957f7f9774cb83ce8f36d3aa9534cc.ppt
- Количество слайдов: 78
Experiences with SOA Michaël Wittoek michael. wittoek@kbc. be
Agenda Introduction KBC Group ICT Experiences with SOA Questions & Answers
Agenda Introduction KBC Group ICT Experiences with SOA Questions & Answers
KBC Group n Ranking l l n One of the top 2 banks in Belgium One of the top 3 insurers in Belgium One of the top 20 banks in Europe Top 3 financial group in Central Europe Market share in Belgium l l Banking : 20 -25% Insurance : 9% (non-life) 22% (life) n Head office in Brussels n 56. 000 employees l l l n 11. 000 clients l l l n Belgium: 20. 000 CEE: 30. 000 Rest of the world: 6. 000 Belgium : ca. 3 300 000 CEE : ca. 6 900 000 Rest of the world : ca. 800 000 Net Profit 2007: 3 281 m euros (ROE : 18, 5%)
The participations of KBC in Central Europe Poland Kredyt Bank (80%) Warta (100%) Czech Republic ČSOB (98, 58%) ČSOB Insurance (97%) Slovakia ČSOB (97%) ČSOB Poist’ovna (98%) Hungary K&H Bank (100%) K&H Insurance (100%) Slovenia (Financial participation) NLB (34%) NLB Vita (67%) Representatived via NLB: Bosnia, Macedonia Last evolution (2007): Romania: Romstal Leasing (99, 34%), Bulgaria: DZI Insurance (85%+ public bid 15%) – EIBank (75%)* Serbia: A Banka (100%) – Senzal (100% *) – Hipobroker (100%) – Bastion (60%) Russia: Absolut Bank (95%) * Not closed Latvia-Estonia-Lituania. Ukraine: BIC (51%)
ICT in a bank: boring or not?
Group ICT n Employees l l l n Services l l n Your ICT, our business Delivering end-to-end ICT solutions (software, hardware, service) Maintenance of ICT solutions Hosting services Network & infrastructure management Clients l l l n Belgium: 1. 930 KBC & 750 external consultants Central Europe: 1. 360 KBC India: 250 Valuesource (100% daughter of KBC) KBC Group Belgium KBC Group international Other corporate clients in the Benelux (Orbay, IFB, …) Turnover: € 800 mn
ICT infrastructure (Belgium only) 2 IBM Mainframes in CCM - 1 in CCL (+/- 19. 500 Millions of Instructions Per Second) 284 beschikbare Terabyte (284. 000 Gb) 2 robots: 10. 000 tapes, 180 Gb/tape 17. 000 transactions/day 21. 000 PC’s 3. 600 portable PC’s 1. 200 softwares 17 Terabyte NAS 2050 Unix servers (HP, SUN Solaris) 1500 Intel servers 320 Terabyte hard disk 2 robots: 8. 500 tapes, tot 1 Tb/tape 10. 500 network printers & multifunctionals KBC Datacenter is one of the largest in Belgium
The ICT offices Brugge Roeselare Antwerpen Gent Aalst Mechelen Hasselt Leuven Brussel Head offices Data centers Local offices
Agenda Introduction KBC Group ICT Experiences with SOA Questions & Answers
What’s in it for you? n This is our truth and nothing but our truth on SOA n If SOA is still a mystery to you and now you expect to see “the light” and the exact road ahead… l l n If you believe in SOA and think to know the right approach l l n We’ll try to demystify But there’s no unique recipe for SOA Our story could inspire you But perhaps you can do it differently If you don’t believe in SOA l l Perhaps I’ll convince you But it’s really not the aim
Content n Why SOA makes sense for KBC? n What is SOA for KBC? n Roadmap for SOA l l l n SOA experiences: l l n The big picture Integration frameworks as enablers Method for SOA Service Oriented Organisation in ICT Fazed implementation Migration of distribution channels to a multi-channel concept Building an ASP for non-life assurances Wrap up
Why SOA makes sense for KBC? We used to see the whole picture: • All on 1 platform • Everyone using the same standard • Everything build on our own • Manageable In/ O Te AS uts o ch no P, B urci log SP ng Me ical , … rge rat rac … r e We could end up with a lot of pieces with which we have to do puzzles, but… l. We wouldn’t know the full picture we’re aiming at l. We wouldn’t know which pieces we want or have to use
Why SOA makes sense for KBC? n But then the world around her started changing… l l ASP – BSP (Insourcing & outsourcing at business or ICT level) l n Mergers of companies with similar or different activities Off the shelf packages, Internet, Web services, … …resulting in an ICT architecture l l Heterogeneous software, hardware, … l Where there are many “standards” on functional and technical level l n With a lot of interaction with external parties And a lot of flavours of banking and assurances business models But the same quality was still needed or even more! l Deliver the same of better services to our client l Regulations on EC level l Time to market and cost!
Why SOA makes sense for KBC? n So probably nothing different compared to other (financial) companies n Perhaps one extra issue…KBC Group l l Several successful acquisitions in Central Europe In parallel with the EU and € drive in Central Europe we are transforming gradually to one company with a delicate balance between - Localisation n - Local regulations Local market conditions Big bang is too dangerous Centralisation n Law looks at KBC Group as one company Economy of scale EU is becoming “one country”
Content n Why SOA makes sense for KBC? n What is SOA for KBC? n Roadmap for SOA l l l n SOA experiences: l l n The big picture Integration frameworks as enablers Method for SOA Service Oriented Organisation in ICT Fazed implementation Migration of distribution channels to a multi-channel concept Building an ASP for non-life assurances Wrap up
What is SOA for KBC?
What is SOA according to KBC? n SOA is just another example of a very general aim “staying in control…” l l n Your first lessons in programming? If you have 1000 lines of code you’d better start thinking of modular programming! How do you tackle a huge problem? Split it up in smaller problems you can handle! Divide et impera! How do you manage a big team? By making fine agreements on who’s doing what! “… and reaching the appropriate level of effectiveness and efficiency”
What is SOA according to KBC? n You have a service oriented architecture if you’re able to… l l l Create an overview of your complete external and internal application portfolio And you can cluster them in several big blocks And you can assign a list of service (= what the “thing” does for the others) to each of these big blocks And you can combine these services into processes known by the business Regardless of all technology used
What is SOA according to KBC? n SOA is not a technical concept n But: it is a way to achieve a manageable situation for all aspects of ICT: l l Architecture describes the situation Some aids, outside architecture, needed to achieve the situation: - frameworks - methods - organization - infrastructure
Content n Why SOA makes sense for KBC? n What is SOA for KBC? n Roadmap for SOA l l l n SOA experiences: l l n The big picture Integration frameworks as enablers Method for SOA Service Oriented Organisation in ICT Fazed implementation Migration of distribution channels to a multi-channel concept Building an ASP for non-life assurances Wrap up
Roadmap voor SOA
High level view on SOA-approach n We never had a big ICT change project called “KBC ICT goes SOA!” n SOA requires a multi dimensional approach. Such type of projects are very complex to manage, very difficult to absorb by your organisation n SOA is something you gradually learn and thus should be introduced step by step n Such type of projects tend to forget the real aim and start creating one on their own
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
Key succesfactoren ICT Gartner ICT strategie methodologie Solutions Strategy (Business View) Develop Target Architecture Plan Business Strategy 4 1 Summarize Strategic Business Direction Technology Trends Develop ICT Direction 2 3 Conduct ICT Assessment and Gap Analysis Develop Target Service Delivery Model 5 6 Develop Management & Governance Processes 7 Develop Migration Approach & Roadmap Develop Communication s Plan and Obtain Broad 8 Consensus Delivery Strategy (ICT View)
Business priorities in the banking world (Gartner Research) Business: ICT: n Globalization: BSP n Globalization: ASP n Time to market n Frameworks n Process standardization n Packages n Costs-control n Re-use Outsourcing
3 Roll-model as patern DISTRIBUTION Corporates Retail Front Office Markets Securities Accounting Credits Risk Management Insurances In/excasso . . . PRODUCT FACTORY Factoring COMPANY MANAGEMENT
Accounting Application infrastructure Payments Risk Management ICT Audit & compliance Reinsurances Life insurances Non-life insurances Asset management Securities Markets Savings Credits Leasing Trade Finance Niche products ERP Domain classification based on 3 roll-patern Distribution
Globalisation Local distribution Distribution P r o d u c t P r o d u c t Central product factories Distribution P r o d u c t P r o d u c t
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
Enable integration frameworks n EAI l l Synchronous Asynchronous n Network Data Model n Information layers n Internationalisation
Integration Architecture… highlevel view Central EAI Browser backbone Local WAS Browser WAS Back End Back End Browser Browser WAS Back End Browser Local EAI backbone Back End
Synchronous EAI: Web Applicatie Servers: 3 Tier architecture n 3 Tier l l l n Interaction layer Application layer Business Logic layer Principles: Thin client en Thin server: l l Only Business Logic and Data in the Business Logic layer Minimal locale footprint for interaction: sandbox of the browser Logic in the Interaction layer is minimal Optimize the flow between the different layers: take the limitations of bandwidth and the performance-requests into account. User Interaction layer Application layer Business Logic layer
Synchronous EAI: Web Application Servers: positioning of logic Presentation logic Process logic Tier 1: Browser Tier 2: Web Applicatie Server Assembly logic Business logic Data Tier 3: Back-end
Synchronous EAI: Web Applicatie Servers: Model View Controller patern Presentation: show HTML pages Presentation logic : create HTML pages Tier 1 Tier 2 Process logic: control of the UI dialogue Assembly logic: combine functionalities of 1 or more back-end applications on 1 or more back-ends to 1 service for the UI process Business logic Data Tier 3
Synchronous EAI: Web Application Servers: positioning assembly logic Tier 1: CLIENT Browser Presentation (view screen) Presentation logic (create screen) Process logic (control of the UI dialoog) Aggregation services on multiple back-ends Connection frontend - backend Aggregation functions to services function Tier 2: MIDTIER WAS Assembly logic scattered over 2 tiers Aggregation functions to services function Business logic Data Application Tier 3: BACKEND
What is asynchronous EAI? Adaptor Connection Semantic transformation Syntactic transformation Security Intelligent router Replicator & Correlator Filter Router Security Adaptor Connection Semantic transformation Syntactic transformation Security
Objectives asynchronous EAI n Asynchronous interaction between back-ends: l l l n NOT for synchronous interaction between user and backend. Complementary to the working of the Web Application Servers Back-end interactions are internally as well as externally Realize a disconnection between applications, functional as well as technical: l l “Plug and Play” Re-use of services offered by the back-ends
When synchronous? When asynchronous? n Asynchronous if … l l l n Cross-platform backend-to-backend interaction Technical disconnection Functional disconnection: no feedback within the same unit of work Attention! l l Technical SLA is “best possible time”, mostly “a few seconds” Restrict amount of asynchronous steps within an end-toend process
What is NDM ? n NDM stands for “Network Data Model” n NDM is a standard interface-model in KBC ICT - Only exists on the network between participants Never by the participants Standardized on a logical as well as a fysical level Application 1 Application 2 NDM Application 3 NDM Application 6 Application 5 NDM Application 4
Why NDM? n What happens if 6 applications are talking p 2 p? One way connecties: 15 14 13 12 11 10 0 9 8 7 6 5 4 3 2 1 Two way connecties: 30 28 26 24 22 20 18 16 14 12 10 0 8 6 4 2
Why NDM? n Managable? Number of connections (one way) 15 Number of connections (two way) 30 No !!
NDM 6 applications, communicating via a standard business document: One way connecties: 6 5 4 3 2 1 Two way connecties: 12 10 8 6 4 2
NDM n Standard business document definition for “order” Solution! Order processing department
When using NDM? n By asynchronous backend to backend integration Application 1 Application 2 Application 4 NDM Network Data Model Application 5 Adaptor Application 3 Application 6
Information layers Operational Distribution Product factory Company Management EAI + NDM Staging Staging Distributie Private Productfabriek Private Bedrijfsbeheer Public Public Informational
Internationalization Translation Cultural formats Encoding
The alternatives for Internationalization n Ignorance l n Transliteration l n Different platforms (OS, databases, applications) per codepage-instance Cloning at the boundaries l n Translate a non-standard character into the nearest form out of ASCII-7 (example: č becomes c) Full cloning l n We don’t take any code page issues into account A part of the platform is in Unicode, the boundaries themselves are cloned Full Unicode
Internationalisation: strategic vision All applications completely in Unicode on all platforms n Business long term strategy of globalisation n Unicode is the world-wide standard code page for storing and visualize all different character sets in the world without any loss. n Conversions between Unicode and locale code pages should be avoided as much as possible: l l They introduce extra cpu overhead during runtime They introduce extra complexity during design and build.
Dealing with Internationalisation System 3 System Enable applications Enable 2 application infrastructure PSN KOD OUTPUT Application substructure Connectors 1 System Enable technical infrastructure Middleware DBMS OS …
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
Basic Concepts of WPF Levels of abstraction Contextual Why … ? Conceptual What… ? Logical How… ? Physical Business/ Process By what … ? Information Systems Technical Infrastructure Service Management Security
Traceability through the layers Requirements Principle 1 Principle 2 Principle 3 Service C Service A Service B Component A Contextual Service E Service D Component B Conceptual Component C Solutions Logical Component A Component B Physical
Basic Concepts of WPF Different aspect area’s Security Architecture Service Management Architecture Information Technology Infrastructure Information System Information Architecture Business Architecture
Coordination over the aspect areas Processes Information System Components Actors Information Structures Technology Infrastructure Channels Hardware Transformation Enabling Security Service Management
WPF matrix abstraction levels x aspect area’s CONTEXTUAL Specific Aspect area’s INFORMATION SYSTEMS INFORMATION BUSINESS Information Main Aspect Area’s TECHNICAL INFRASTRUCTURE SECURITY SERVICE MANAGEMENT CONCEPTUAL LOGICAL PHYSICAL
Classification services per aspect area B services BI services IS services TI services Security services Service Management services
Classification of services: Different types of “IS services” n Workflow services l l l n Process logic services l l n Coordination of a process Work distribution to different actors (vb. front/back-office) Example: deal with a claim Coordination of an activity of a process Executed by one actor Facilitate the user interactions (screen flow) Example: Finalize a loan agreement Business logic services l l Provide in re-usable business logic Example: define rate of a contract
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
Service centres : Organisation model ice rv Se Functional Competence center Service Center Technical Competence center s Architecture Analysis & Preparation Design Development Functional & Technical Functional Maintenance Technical Maintenance Commodity Delivery Center
Life Cycle Work preparation Identification & Definition Prestudy Charter Definition Architecture Programe Definition & Proposal Production Delivering Initiating Idea Production Work Execution Initiating Close Down & Evaluation + Mobili sation & Requirements Walkthru Design Realisation & Test Imple men tation Guarantee & Completion = Operations
Globalization: Central Service Centers – Local Delivery Centers Distribution Local P Delivery P P Center P P r r o o. Central Service d d u u. Center c c t t P P Central r r Delivery o o Center d d u u c c t t P P Offshore Delivery Center Local Distribution Delivery P P Center Local Distribution P P Delivery P P Center P
High level view on SOA approach Steps & Principles Draw the big picture Challenge your ICT organisation with the real SOA target And keep reminding them of it! Trigger Introduce an adequate methodology/process Method Enable Introduce adequate technology if you don’t have it yet Reorganise Go step by step at the pace of real business cases Do it! Intensify Respect the absorption capacity Adopt your ICT organisation to of your organisation the SOA target Learn of your mistakes. Adopt your ICT organisation to this methodology and technology
Content n Why SOA makes sense for KBC? n What is SOA for KBC? n Roadmap for SOA l l l n SOA experiences: l l n The big picture Integration frameworks as enablers Method for SOA Service Oriented Organisation in ICT Fazed implementation Migration of distribution channels to a multi-channel concept Building an ASP for non-life assurances Wrap up
Synergy in insurances (SIS) An ASP case to illustrate SOA at KBC
Context en scope n Context l l n The ICT-platform ZSI with its product factory “non-life” of Warta is end of life KBC is having the ambition to setup a global product factory “nonlife” for KBC group The existing product factory “non-life” of KBC is not re-usable The infrastructure for distribution and company management of KBC is re-usable Scope l l Set-up a global product factory “non-life” for KBC group Multi-channel, for following distributors: - KBC Bank and Insurances BE, - Fidea - Warta PL - KB PL
Accounting Application infrastructure Payments Risk Management ICT Audit & compliance Reinsurances Life insurances Non-life insurances Asset management Securities Markets Savings Credits Leasing Trade Finance Niche products ERP SIS ASP in de domeinarchitectuur Distribution
AS IS architecture Fidea KBC Ins & Bank rationeel Customers Distribution concept WARTA & Customers KB ZSI Distri conc Agents OUTPUT Infra KBC Product Factory PRODUCTS CONTRACTS Polaris PRODUCTS CONTRACTS Claim handling Company Mgt INCASSO EXCASSO ACCOUNTING SAP INCASSO EXCASSO ACCOUNTING ADMINISTRATION SAP Modules ADMINISTR. ZSI
TO BE Architectuur Fidea KBC Ins & Bank rationeel WARTA & KB Persons Distribution concept AGENTS OUTPUT COMMISSIONING Distribution Persons AGENTS Persons COMMISSIONING Global Infra KBC Product Factory PRODUCTS SIS CONTRACTS SIS Global PF SIS CLAIMS SIS Company Mgt INCASSO & EXCASSO SAP FS CD ACCOUNTING SAP FI SAP ADMINISTRATION SAP Modules
SIS Overall planning 2006 1 Q 2 Q 3 Q 4 Q FO 2007 1 Q 2 Q 3 Q 4 Q 2009 2008 1 Q 2 Q 3 Q 4 Q 2010 2011 Change Pre study phase II Pre study phase I Prod/contr Claims Accounting Start workexecution Incasso Excasso Ditribution Infrastructure Go live Bus 4 Q 09 2012 2013
Content n Why SOA makes sense for KBC? n What is SOA for KBC? n Roadmap for SOA l l l n SOA experiences: l l n The big picture Integration frameworks as enablers Method for SOA Service Oriented Organisation in ICT Fazed implementation Migration of distribution channels to a multi-channel concept Building an ASP for non-life assurances Wrap up
Wrap up
Wrap up n The big picture Integration Frameworks Technology Methodology Organisation Service & Domains KBC gradually implemented its own SOA stack… n …by combining theory and practice n …by taking the time to “learn” SOA, inspired by the real aim n …and surely not by throwing away all existing tools & techniques
Wrap up n SOA isn’t just tools, platforms and applications n It’s mostly… l l l Vision and strategy An architecture to support this and A feasible plan for execution
Agenda Introduction KBC Group ICT Ervaringen met SOA Questions & Answers
Questions & Answer
KBC hires 150 new ICT employees this year You can apply by mail with your CV attached to ictjobs@kbc. be or via www. kbcworld. be What do we offer ? l A wide range of training and growth opportunities within ICT and business l Room for expert as for generic functions and careers l A professional ICT environment with a wide range of technologies, processes and business processes l Local and international opportunities l A competitive salary with extra legal benefits
ba957f7f9774cb83ce8f36d3aa9534cc.ppt