1. How to Manage Convergence ? DIGIT B2 - MIA – EA Team Dana Mateescu November 2010

2. 2 EA@EC Center of Excellence DIGITAL AGENDA  EC lead by example in ICT: DIGIT directly concerned We need CONVERGENCE We need to be SMART SMART = intelligence + accurate information: We need ASSETS VISIBILITY Process Glossary – CORPORATE INFORMATION FROM PRINCIPLES TO IMPLEMENTATION: We need accurate information on corporate assets We need corporate projects to reduce duplication WE NEED TO MAKE THE MOST OF RESOURCES ! Setup EA@EC CoE is a FLAGSHIP Project for e-Commission 2011-2015 !

3. 3 Known EC issues/problems (1/2) Many Business Processes serving similar purposes  duplication of efforts & financial expenditure! No agility to handle Organizational changes in an ever changing World! Information systems built in silos to satisfy DG-specific objectives  no interoperability and re-use

4. 4 SOA infrastructure progressively deployed and SOA projects already ongoing or to start very soon (e.g. IPCIS, eFP7, DG TAXUD, DG REGIO)  Wild West SOA! Lack of EA-SOA governance leading to Missing opportunities for interoperability, reuse and process streamlining services proliferation and duplication under use of the SOA related infrastructure and investments Not yet fully acknowledged that… …There is no SOA without strong business support and business process management… business service SOA = business service implementation ! Known EC issues/problems (2/2) BPM- SOA Strategi c Alliance Alliance

5. 5 Enterprise Architecture can help Mastering CHANGE with: Focus on BUSINESS STRATEGY  CEAF Continuous PROCESS IMPROVEMENT  BPM IT assets RATIONALIZATION  SOA Enterprise Architecture facilitates control in an ever changing environment through a holistic view linking business strategy, business processes, supporting IS and IT infrastructure

6. 6 What is Enterprise Architecture ? An enterprise architecture (EA) is a rigorous description of the structure of an enterprise, which comprise Enterprise goals Business processes Roles, organizational structures and organizational behaviors Business information Software applications Computer systems EA is also the PROCESS of managing change: From 'As Is' to incremental 'To Be' s !

7. 7 Enterprise Architecture vs. IT Architecture What? Enterprise Architecture includes: Business Strategicy Business Architecture Information Architecture Data Architecture Systems Architecture Computer Architecture Why? To bridge the gap between IT and business by providing a common framework that facilitates common understanding and communication. How? First, organize and classify existing business processes and technology investments, to identify redundancies and reduce computing complexity. Secondly, use EA to identify and communicate standards and to stir corporate convergence programs. This approach typically reduces an enterprise’s technology portfolio costs by at least 10%.

8. 8 Information Systems To-Be Architecture example: Enterprise Semantic Data Model Data spine - core enterprise data model - Grant Management Strategic planning Legislation Lifecycle Audit Human Resources Financial management IT Procurement Coordination Asset Management Document Management Program Management Policy Lifecycle Communication & Dissemination

9. 9 To-Be Architecture example: SOA by Process Category Policy Lifecycle Strategic Planning Legislation Lifecycle Program Mgt Grant Mgt Co- ordination Communication & Dissemination Audit Financial Management Human Resources Procurement Document Management Assets Management IT Management AuthenticationData access Data Transport e-InvoicingWorkflow... Staff Database Supplier Database Financial Database Legacy System Create Contract Update Employee Register Expert ……. Register Document Enterprise Data spine

10. 10 SOA - 5 Success Factors for SOA Adoption strong alignment between Business & IT strong Business and IT Governance processes skills and knowledge centralized in an SOA Centre of Excellence adequate tools, methodologies, infrastructure an appropriate funding model

11. 11 SOA@EC Governance & ROADMAP A shared vision on SOA Governance and adoption Roadmap in the Commission ! DIGIT will DRAFT an SOA@EC vision AGREE UPON within DIGIT + 1 ‘pilot’ DG… PROPOSE THIS VISION TO ALL DGs The SOA Governance preparation study in the context of SOA adoption in EC SOA Governance project

12. 12 SOA@EC Governance project To agree on a common vision on SOA@EC among all DIGIT stakeholders, we propose the following path: Phase 1 AS IS Phase 3 ROADMAP Phase 2 TO BE SOA@DIGIT Readiness Assessment SOA@EC Governance Model (Agreed by DIGIT) SOA@EC Implementation Road Map (Agreed by DIGIT) SOA Governance preparation paper (DIGIT EA team) SOA Strategy paper (Gartner)

13. 13 SOA - Phase 1 : As Is - SOA Readiness assessment Identification of stakeholders Inventory of needs for SOA (e.g. by interviews and questionnaire) Current and planned projects which are relying on SOA-related technologies Overview of current technical infrastructure related to SOA Current SOA – IT governance The As-Is state will be documented in the SOA readiness assessment.

14. 14 SOA - Phase 2 – To Be deliverables SOA@EC VISION STATEMENT SOA@EC GOVERNANCE MODEL ROLES & RESPONSIBILITIES POLICIES PROCESSES TOOLS adoption METRICS SOA@EC PILOT PROJECT

15. 15 Questions… Thank you!