SAP Enterprise Architecture:

SAP Enterprise Architecture: A governance model to ensure the successful adoption of Enterprise SOA Franck Lopez, Global Director, Enterprise Architecture Field Services, Solution Management

SAP Enterprise Architecture: A governance model to ensure the successful adoption of Enterprise SOA Franck Lopez, Global Director, Enterprise Architecture Field Services, Solution Management

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 3

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 4

What is Enterprise Architecture Governance? Enterprise Architecture Governance ensures Business-IT alignment. The practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level As defined by The Open Group SAP 2007 / Page 5

What is Enterprise Architecture Governance? Enterprise Architecture Governance does not and cannot operate in isolation. Business Strategy and Planning Monitor Technology Innovations and Align to Vision Set Strategy and Vision Support Effective Governance Support and Model IT Landscape Research and Innovation Enterprise Architecture Service Delivery Landscape Align innovation to strategy, using proof of concepts Support and Align Projects to Strategic Roadmap Provide Evidence of Architecture Compliance Programs and Projects (PMO) Monitor Obsolescence Learn from Operations SAP 2007 / Page 6

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 7

Why is Governance important in Enterprise SOA? However, through 2010, the biggest barriers to SOA adoption will be nontechnical issues related to inadequate governance, lack of clear value metrics, poorly defined requirements and scope, and insufficient business involvement in project prioritization and service identification. SOA governance isn't an option it's an imperative. Paolo Malinverno, et al, Gartner, 2006. to enable an SOA governance strategy, companies must re-evaluate their higherlevel IT governance strategies and align their SOA governance initiatives with them. Any vendor providing a holistic SOA governance solution should have a set of technologies or services that can help you organize for SOA and SOA governance Frank Kenney, et al. Gartner 2007 Before innovative SAP customers decide to adopt service-oriented architecture (SOA) across the entire enterprise, they will need a holistic view of how all the pieces of their IT puzzle fits together. They will need an enterprise-wide enterprise architecture (EA) blueprint Derek Prior, et al, AMR Research, 2006 SAP 2007 / Page 8

Why Enterprise Architecture Governance?. to enable an SOA governance strategy, companies must re-evaluate their higherlevel IT governance strategies and align their SOA governance initiatives with them. Any vendor providing a holistic SOA governance solution should have a set of technologies or services that can help you organize for SOA and SOA governance Frank Kenney, et al. Gartner 2007 Before innovative SAP customers decide to adopt service-oriented architecture (SOA) across the entire enterprise, they will need a holistic view of how all the pieces of their IT puzzle fits together. They will need an enterprise-wide enterprise architecture (EA) blueprint Derek Prior, et al, AMR Research, 2006 Enterprise Architecture Governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled at an enterprise-wide level The Open Group, 2006 SAP 2007 / Page 9

Systems of Architecture Governance breakdown Projects end without delivering their promised benefits an dleaving duplicated processes and systems... everything gets more compley We have defined our TO-BE Information Architecture and a set of Design Standard, but no-one takes any notice of them Projects are initiated before we realise it... the solution has been chosen by a senior manager before the users requirements have been confirmed Our budget round for next year is made up of a series of good ideas that aren t aligned to our corporate business strategy We have 3 ERP systems, and 10 flavors of UNIX to support and our three main Operational systems will soon be out of extended maintenance Our solutions are tactical rather than aligning to strategic objectives. This is leading to a loss of economies due to duplication and little if any reuse. SAP 2007 / Page 10

So what do we mean when we say SOA Governance? Managing the portfolio of services planning development of new services and updating current services Managing the service lifecycle ensuring that updates of services do not disturb current service consumers Using policies to restrict behavior ensure consistency of services using rules that all services need to conform to Establish performance monitoring of services Service Repository loosely-coupled nature of service composition, means the consequences of service downtime or underperformance can be severe. by monitoring service performance and availability, action can be taken instantly when a problem occurs. SAP 2007 / Page 11

Enterprise SOA Governance is wider than that Realizing Enterprise SOA Benefits Safeguarding Enterprise SOA Projects Business Strategy Solution Planning & Operations ESOA Governance IT Strategy Enterprise Architecture Governance Accelerated Learning Curve Re-usable Services for the Enterprise SAP 2007 / Page 12

Enterprise SOA Governance EA Governance SAP Enterprise Architecture Framework SAP Enterprise Architecture Framework extensions Usage Guidelines Architecture Development Method ES Community Resource Base Extensions SAP Business Reference Models Content Metamodel SAP Technology Reference Models Templates, Examples and Case Studies SAP Mapping Extensions SAP Tooling Extensions People and Organization SAP Content Tools Processes SAP Implementation Tools Standards and Templates TOGAF Architecture Development Method EA Modelling Tools Resource TOGAF Base Resource Base Product CDG CAG KPIs and Monitoring Outward CDG ESOA Governance Service Design PIC 0 Decision on service cut ES Toolset & Lifecycle Mgmt. SAP 2007 / Page 13 PIC 1 Raw design GDTPIC GDT PIC review PIC 3 Final design In ES Repos. Implementation ES Design & Modeling Methodology

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 14

How the Governance fits into the SAP Enterprise Architecture Framework The SAP Enterprise Architecture Framework extends the Open Group Architecture Framework (TOGAF) with further tools. Define how the framework will be governed Define a vision to implement EA governance Establish a Design Authority Ensure Project Compliance Define and Use Architecture Contracts Example Review Checklists SAP 2007 / Page 15

How the SAP EA Framework accelerates good Governance Identifies the key inputs, steps and outputs for implementing Governance Released to the Open Group GUIDANCE & BEST PRACTICES SAP Enterprise Architecture Framework for Enterprise SOA SAP Enterprise Architecture Resource Base Framework extensions Extensions Architecture Development Method Usage Guidelines Content Metamodel Templates, Examples and Case Studies SAP Mapping Extensions Provides standard patterns and reference models to improve architecture quality LOWER COSTS & LESS RISK Released to the Open Group SAP Business Reference Models Maps SAP terminology, content, reference models and products into the SAP Technology metamodel and the EA Reference Models Toolset FEWER REJECTIONS & FASTER TIME-TO- MARKET SAP 2007 / Page 16 Enables standard SAP Content terms and concepts, and tailored Tools stakeholder views of the architecture TOGAF Architecture Development Method MORE EFFECTIVE PROCESSES & COMMON TAXONOMY SAP Tooling Extensions SAP Implementation Tools EA Modelling Tools TOGAF Resource Base Provides an EA Tool Reference Implementation, and other SAP Tools REUSABILITY & REDUCTION OF SILO WORK

Analytics Financials Human Resources Corporate Services Operations Examples of SAP EAF Governance Extentions Discover ESA and SAP NewWeaver Vision Value Session ESA Opportunity Workshop As-Is Analysis and Opportunity Assessment TCO Discovery Session Evaluate Enterprise SOA Pulse Check Business and IT Strategy Business Processes Organization Charts Project Portfolio IT Landscape Strategy to ESOA Mapping Define Enterprise SOA relevant scenarios Enterprise SOA potential process identification Enterprise SOA service candidate identification Produce assessed scenarios Build Enterprise SOA based architecture Map Business Functions/Services to IT Architecture Fill Gaps Create TO-BE Architecture Create Enterprise SOA based Roadmap Map SAP Upgrade Strategy Customer Specific Upgrade Plan Enterprise SOA Roadmap Recommendations Risk Assessment Management Summary Motivation Project Vision and Strategy Business Strategy Technology Strategy Organizational Impacts Organizational Structure Functional Requirements Business Process Models Business Services Business Function Models Applications Application Landscape Solution Scope Requirements Work Package Constraints Gaps Solution Infrastructure IT Infrastructure Implement Plan Services Scope Business Model (Entity Model, Process Structure, Role Model, Process Flow Model) Service Model (Functional Business Components, Business Component Interaction Analysis, Derivation of Enterprise Service Operations) Implementation Design (Mapping Functional Business Components to Functional Components, Implementation Design for Functional Components, Implementation Design for Process Components, Implementation Design for Process Component Interaction) Gap Analysis Landscape Design Solution Design Build Services Role Design Run Services Operate Continuous Operations and Governance ESA / NetWeaver Community ESA Leader in Your Industry SAP EAF to SAP Roadmap Mapping IS IT A COMPLEX CHANGE? CHECK Are there significant new Business Drivers, Goals and Objectives that mean the Business Strategy is changing? Has a significant event like a Merger/Acquisition or Divestiture occurred that will impact the architecture of all domains? YES/NO Solution Data Aspects Entity Model Solution Security Roles and Authorization General Reference Name Description Source Owner Type Version Business RACI Service name caller Service name called Business Objects (CRUD) Functional Requirements Importance to the process. Quality of information required Contract control requirements Result control requirements Quality of Service Service Level Agreement Technical Service Contract Invocation Invocation Preconditions Master Data Impacted Behaviour Characteristics Post Condition Reference Material Phase Specific Inputs Pre-Existing or Previous Phase Inputs Non-Functional Requirements Throughput Throughput period Growth Growth period Service times Peak profile short term Peak profile long term Security requirements Response requirements Inputs TOGAF TOGAF ADM Implementation Governance Narrative SAP EAF Implementation Governance Phase Worksheet SAP EAF Implementation Governance Narrative Document Detailed Implementation and Migration Plan Architecture Repository Solutions Building Blocks Qualities Infrastructure Business Applications Applications Application Programming Interface Implementation Governance Phase Implementation Governance Narrative SAP for <Industry> SAP for Aerospace & Defense SAP for Automotive SAP Packaged Solutions Outputs Impact Analysis Architecture Contracts for Architecturally Governed Change Activity Architecturally Compliant Systems Service Management for < Industry> Financial Insights for <Industry> Steps Implement EA Governance Framework Guide Project Implementation Review Project Approach and Output...... Are there new technology developments that have significant business user impact? E.g. availability of affordable mobile computing in a wireless mode Are there new technology components and guidelines for use in deployment of the architecture? E.g. web service standards Does the change impact two stakeholder classes or more? Does it impact two domains or more? Does it involve adding or removing large numbers of metamodel object instances in more than two domains? E.g. adding one or two new Data Entities in Data Architecture domain, plus new business processes in the Business Architecture domain, plus new Technology classes in the Technical Reference Model that impacts the Technology Architecture? Qualities Software Engineering Security System & Network Management Transaction Processing Qualities Graphics & Image Data Management Data Interchange International Operations User Interface Location & Directory Operating System Services Network Services Communication Infrastructur Interface Communication Infrastructure Intfrastructure Qualities SAP xapps SAP xapp Resource & Program Mgmt SAP xapp Product Definition SAP xapp Mergers & Acquisition... SAP NetWeaver SAP Enterprise Portal SAP Master Data Mgmt SAP Business Suite SAP PLM SAP SRM SAP ERP SAP CRM SAP SCM SAP Business Intelligence --- SAP Exchange Infrastructure... SAP Smart Business Solutions SAP SAP All -in-one Business One SAP Business One Server ACTION : Architecture Change Management Narrative SAP 2007 / Page 17 Progress via new architecture engagement Follow the SAP EAF process again The Enterprise Architect needs to agree and scope a new Request for Architecture Work as detailed in Unit 3 Architecture Vision and Unit 12 Using SAP EAF in Architecture Engagements SAP Specific Technical Reference Model

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 18

The Enterprise Architecture Governance Service Analyze Design Transform Improve Conduct Enterprise Architecture Maturity and Best Practice workshop Design Enterprise Architecture Organization and Roles Deploy Organizational Structures / Processes based on roadmap Design and implement continuous improvement process Analyze Strategies and Derive Imperatives Design Enterprise Architecture Governance Processes / Standards Implement Design Authority / Governance processes / Standards Monitor KPIs Perform Assessment and Analyze Gaps Design Personnel/Role Development Conduct Personnel/Role Development activities Initiate Stakeholder Management Design Organizational Change Management activities and KPIs Conduct Change Management Activities Define To-Be Enterprise Architecture Governance Vision Create Transformation Roadmap Implement EA Tools and KPIs Concept Decision Transition is a structured project approach based on SAP Consulting best-practices. SAP 2007 / Page 19

The SAP Enterprise Architecture Governance Service: the Five Key Dimensions Research and Innovation Enterprise Architecture Projects and Programs Service Design PIC 0 PIC 1 Decision on service cut Business Strategy and Planning Governance Framework 1. People and organization 2. Processes 3. Standards and Templates Raw design GDT PIC review Is my Design process integrated to my Service Design process? PIC 3 Final design In ES Repos. GDT- PIC Implementation Do I have service description, interface standards? 5. KPIs and Monitoring Solution Implementation Lifecycle Do I have business service specialist promoting and identifying re-use opportunity? 4. Resource Base Am I building 100s of services that no-one is reusing? Are they too coarse-grained? Service Delivery Landscape Does my ES Repository align to my Resource Base? How are projects that build services being governed? SAP 2007 / Page 20

The Enterprise Architecture Governance Service Step 1: Analyze Work Package Overview Analyze Conduct Enterprise Architecture Maturity and Best Practice workshop Analyze Strategies and Derive Imperatives Structure Processes People Present SAP s best-practices model Influence and Impact Business IT-Alignment 5 4 3 2 1 Governance Derive strategic imperatives Perform Assessment and Analyze Gaps Communication 0 People Stakeholder Involvement Architecture Process Initiate Stakeholder Management Readiness Expectation Architecture Development Perform GAP analysis Identify stakeholders Define To-Be Enterprise Architecture Governance Vision Scoping for To-Be design SAP 2007 / Page 21

Enterprise Architecture Governance is based on standard architecture frameworks and provides the complete set of best practices ready to use from SAP Consulting. People and Organization Processes Standards and Templates Resource Base KPIs Organization Competencies Strategic Alignment Business Process Management Standards Templates EA Tools Enterprise Architecture Controlling Architecture Board/ Design Authority Identification and allocation of HR Alignment of business and IT objectives Processes Standards for design and modeling Business Opportunity Maintenance Processes KPIs New tasks and roles Skill profiles (To-Be, As-Is) Requirements analysis management Task Descriptions Standards for enterprise services Outline Design Metamodel and View Mapping Benefit tracking Organizational structure Training Project portfolio management RACI Standards for applications Detailed Design Tools Strategy and Selection Budget and cost allocation Budget ownership Knowledge management Service Landscape Operations Standards for IT infrastruct. Support Model Tool Implementation Risk management Compliance Use the SAP Consulting framework to accelerate the design of your Enterprise Architecture governance. SAP 2007 / Page 22

1. People and Organization IT Strategy Board IT Strategy Board sets the overall governing IT strategy Design Authority Program Management Office Service Delivery Management The Design Authority responsible for governing and maintaining the architecture that delivers the strategy co-ordinates, shapes and reviews all programs Program Design Authority Project A SAP 2007 / Page 23 Project B Program Design Authority Project C Project D Program Design Authorities delegated responsibility for shaping and review an individual program Projects use their own staff to ensure their own developments are controlled

1. People and Organization Terms of Reference for a Design Authority Provide early design direction to programs / projects prior to feasibility stage Support the development of designs throughout the project lifecycle Ensure that dependencies and interfaces across projects and between individual programs are proactively managed and resolved Be the next escalation point to resolve issues that could not be dealt with at the Program Design Authority level Early Design Direction Outline and Detailed Solution Design Governance Update Enterprise Architecture to deployed systems, gather best practice SAP 2007 / Page 24

1. People and Organization IT Strategy Board CIO chairs the IT Strategy Board CIO Service Manager Business Champions Principal Architect Principal Architect chairs the Design Authority Enterprise Architect 1 Enterprise Architect 2 Design Authority Principal Architect Infrastructure Architect Service Manager Enterprise Architects aligned to programs and assurance the program architecture specialize in Business, Application, Data or Technology Program Design Authority Project A Enterprise Architect 1 Project B Program Design Authority Enterprise Architect 2 Project C Project D Other roles play their part : Business Analysts or Domain Experts Service Manager Infrastructure Architects Business Analyst 1 Solution Architect 1 Business Analyst 2 Solution Architect 2 Business Analyst 3 Solution Architect 3 Business Analyst 4 Solution Architect 4 Solution Architects aligned to projects and assure the solution architecture SAP 2007 / Page 25

2. Processes Governance in context PLAN AND ORGANIZE ACQUIRE AND IMPLEMENT IT Governance DELIVER AND SUPPORT MONITOR AND EVALUATE Strategic Technology Radar Maintain IT Vision Select Strategic Technology Produce Outline Designs Solution Acceptance Maintain Solution Resource Base Monitor EA KPIs Demonstrate Innovation Strategic Supplier Radar Produce Detailed Designs Enterprise Architecture Governance Monitor Operations + Obsolescence Assure Designs Maintain Enterprise Architecture Define Organization Vision and Capability Define Enterprise Services Taxonomy Decide Service Cut Assure Integration Define Service Levels & Interfaces Produce Service Design SOA Governance Service Acceptance Into Operation Cost Allocation of Shared Services Monitor Service Reuse And Performance Monitor Service Obsolescence SAP 2007 / Page 26

2. Processes Governance in context PLAN AND ORGANIZE ACQUIRE AND IMPLEMENT DELIVER AND SUPPORT MONITOR AND EVALUATE Enterprise Architecture Governance SAP 2007 / Page 27

2. Example TO-BE Level 0 Processes Map Business Vision Business Roadmap Business Engagement Project Lifecycle Supplier Selection Align Vision Align Roadmap New Opportunities Approved Designs Approved Designs Maintain IT Vision Demonstrate Innovation Select Strategic Technology Strategic Supplier Watch Maintain Enterprise Architecture Assure Designs Produce Outline Designs Produce Detailed Designs Maintain Solution Resource Base Strategic Technology Watch Solution Handback Monitor Operations + Obsolescence Requirements Agreed High Level Test Strategy Service Acceptance Requirements Management Testing Service Delivery SAP 2007 / Page 28 Develop a set of integrated EA Governance processes

2. Processes SAP EAF Governance aligned to COBIT (IT governance framework from the IT Governance Institute ) Strategic Technology Watch Maintain IT Vision Monitor Operations + Obsolescence Monitor EA KPIs MONITOR AND EVALUATE PLAN AND ORGANIZE Demonstrate Innovation Strategic Supplier Watch Assure Designs Maintain Enterprise Architecture Produce Outline Designs Solution Handback Maintain Solution Resource Base DELIVER AND SUPPORT ACQUIRE AND IMPLEMENT Select Strategic Technology Produce Detailed Designs SAP 2007 / Page 29

Processes Governance in context PLAN AND ORGANIZE ACQUIRE AND IMPLEMENT DELIVER AND SUPPORT MONITOR AND EVALUATE Strategic Technology Radar Maintain IT Vision Select Strategic Technology Produce Outline Designs Solution Acceptance Maintain Solution Resource Base Monitor EA KPIs Demonstrate Innovation Strategic Supplier Radar Produce Detailed Designs Monitor Operations + Obsolescence Assure Designs Maintain Enterprise Architecture Define Organization Vision and Capability Define Enterprise Services Taxonomy Decide Service Cut Assure Integration Define Service Levels & Interfaces Produce Service Design SOA Governance Service Acceptance Into Operation Cost Allocation of Shared Services Monitor Service Reuse And Performance Monitor Service Obsolescence Early Service Design Direction Outline and Detailed Service Design Governance Check what was designed was delivered Update Enterprise Architecture, gather best practice, monitor success SAP 2007 / Page 30

2. Processes In order for EA Governance to function efficiently, we need: A clear set of business processes linked to existing programs and projects Which roles perform what tasks and when A clear set of task descriptions What happens at each process step A clear set of RACI matrices Who is Responsible, Accountable, Consulted, Informed A set of review checklists for key design artifacts SAP 2007 / Page 31

3. Standards & Templates Standards ensure: Enterprise complexity is reduced Solutions can be maintained efficiently Business and IT are aligned Typical standards needed include: Business Process Standards How are processes to be modeled and documented? Design Standards How will we use UML? Infrastructure Standards What infrastructure technology will we standardize on Templates ensure: the right information is available the right quality is produced consistency between projects Typical templates needed include: Statement of Opportunity What s the problem? Outline Design How do I intend to build it? Detailed Design How am I actually building it? Support Model How will what is built be supported? SAP 2007 / Page 32

4. Resource Base A Resource Base is needed to : Enable easy maintenance of architecture as the business and IT landscape changes Efficient share architecture knowledge sharing across the whole organization Provides stakeholders with models most relevant to their role Promotes re-use of models Promotes more consistent quality as the models are integrated Everyone uses the same language Provides one source of the truth properly managed ARCHITECTURE VISION, CONTEXT AND ROADMAP Associated With All Principle Constraint Requirement Gap Work Package Objects BUSINESS ARCHITECTURE Operates in Participates Organisation Unit in Owns and governs Is motivated by Contains Owns Produces Operates in Interacts with, Supports, Is Is Produced Motivates Belongs to Performs performed by Is owned by by Supplies or Consumes Product Driver Actor Function Can be Process Extension Generates, accessed by Creates Resolves Performs Supports, Is Is bounded by Is Produced task in realised by by Participates Addresses in Goal Is Performed Orchestrates, by decomposes Is realised Produces through Involves Role Process Realises Accesses Involves Generates, Resolves Objective Is tracked Control against Ensures correct Process Extension operation of Sets performance Is Resolved by, criteria for Is Generated by Applies to Meets Is Resolved by, Is Generated by Service Quality Contract Measure Event Governance Governance Governance Extension Process Extension Extension Extension Sets performance Is Resolved by Applies to Governs, Measures criteria for Supports, Is Is governed and Location Is tracked against Is Provided to Resolves realised by Meets measured by Infrastructure Consolidation Is owned and (Business, Information System) Service Extension governed by Services are Contained in Core, Business / IS split supports the Business / IT Alignment Extension Provides governed interface to access Provides, consumes Is realised Is implemented on through Is Supplied or Consumed by Is accessed and Is processed Operates Provides updated through by on Implements platform for Supplies Is Hosted Is Supplied By Contains Physical Information in Component Logical Application Logical Technology Data Entity Data Extension Component Component Platform Service Infrastructure Consolidation Resides within Resides within Extension Encapsulates Is Realised by Realises Logical Information Physical Application Component Component Physical Technology Data Extension Infrastructure Component Consolidation Extension Encapsulates Is Hosted in Is Hosted in Contains Contains Contains Contains Consumes Isguided by Orchest rates, decomposes APPLICATION DATA ARCHITECTURE ARCHITECTURE TECHNOLOGY ARCHITECTURE Infrastructure Process Modelling Business / IT Alignment Consolidation Extension Extension Extension Governance Extension Data Modelling Extension Core Content A Resource Base helps prevent: Proliferation of non-standard artifacts Unmaintainable Visio and Excel files Knowledge locked away in only one person SAP 2007 / Page 33

4. Common objects promote common standards Metamodel An Enterprise Architecture Resource Base models the enterprise and promotes common models based on a single source of truth Metamodel Reference Models Architecture Resource Base Application Platform Real - World Enterprise Standard Catalogs Matrices and Views Preliminary Catalogs Principles Catalog Value Chain View Core Views Architecture Vision Solution Concept View Matrices Stakeholder Map Matrix Business Architecture Application Architecture Data Architecture Technology Architecture Core Views Core Views Core Views Core Views Business Footprint View Application Communication View Conceptual/ Logical ER View Environments and Locations View Service / Information View Application and User Location View Data Dissemination View Platform Decomposition View Functional Decomposition View Extension Views Extension Views Extension Views Extension Views Goal Objective / / Service View Enterprise Manageability View Data Security View Processing View Use Case View Process System / Realization View Entity Hierarchy View Networked Computing / Hardware View Organization Chart View Process Flow View Software Engineering View Application Migration View Data Migration View Data Lifecycle View Communications Engineering View Event View Matrices Business Interaction Matrix Actor/ Role Matrix Catalogs Organisation / Actor Catalog Driver / Goal / Objective Catalog Role Catalog Service / Function Catalog Software Distribution View Matrices System / Organisation Matrix Role/ System Matrix System / Function Matrix Application Interaction Matrix Catalogs Application Portfolio Catalog Interface Catalog Matrices Data Entity/ Business Function Matrix System / Data Matrix Catalogs Data Entity/ Information Component Catalog Matrices System / Technology Matrix Catalogs Technology Standards Catalog Technology Portfolio Catalog Queries / Analysis Catalogs, Matrices and Views Location Catalog Process / Event / Control / Product Catalog Contract/ Measure Catalog Requirements Catalogs Requirements Catalog Opportunities and Solutions Core Views Project Context View Portfolio View Infrastructure Consolidation Extension Governance Extension Process Modelling Extension Data Modelling Extension Business / IT Alignment Extension Core Content SAP 2007 / Page 34 Stakeholder

5. KPIs and Monitoring Key Benefits of Enterprise Architecture Helps achieve business strategy Faster time-to-market of new innovations and capabilities More-consistent business processes and information across business units More reliability and security, and less risk Better traceability of IT costs Lower IT costs - Design, buy, operate, support, change Faster design and development Less complexity Less IT risk How do we know its working or not? How do we measure the benefits we are creating? How do we convince the sceptics that it s not a pointless exercise? SAP 2007 / Page 35

KPIs and Monitoring Business Benefits # Projects compliant with strategy # Project overruns >x months Ease of Access to Information Time to implement new capabilities # of security incidents IT Benefits # Projects compliant with IT strategy # Projects into support w/o issue Rate of reactive infrastructure projects # Applications rationalized # Avoided purchases EA Coverage % AS-IS architecture complete % TO-BE architecture complete % Migration Plans in-place % Projects engaging design assurance % Projects with solution architects EA Processes # Projects reviewed/rejected # Projects rejected 1st time Frequency of reviews % Projects engaging design assurance % Projects with solution architects EA Presence # of architects in post # of architects trained # of architects certified # of approved standards in place SAP 2007 / Page 36

Agenda 1. What is Enterprise Architecture Governance? 2. Why is it Important? 3. How to execute EA Governance using SAP EAF 4. The Enterprise Architecture Governance Summary 5. Benefits & Summary SAP 2007 / Page 37

What happens if you follow the 5 Dimensions? There are no surprises IT Projects and programs are aligned to the Business Strategy The organizations requirements and technical constraints are met When solutions are assembled Everything is in place at the right time The right people are involved, as early as possible When projects are initiated Architecture & design risks spotted early in the project Issues trapped quickly We develop and maintain a successful Enterprise Architecture which means The problem is understood The solution solves the problem How the solution will work is understood Elements of the solution can be reused to build other solutions SAP 2007 / Page 38

Key for Realization of Enterprise SOA Benefits Business Potentials Strategic Potential Normative Potential Operative Potential Enterprise SOA Benefits Common Platform Linking Applications Reusability 1 2 3 Process Automation 4 5 6 Process Composition Flexible Deployment Reduction of Development Costs Reduction of System Costs Reduction of Operating Cost TCO Reduction Potentials People are focused on the strategic goal of building of an enterprise SOA Processes and organizational structures are aligned to enterprise SOA Governance ensures the realization of enterprise SOA potential benefits SAP 2007 / Page 39

Conclusion & Recommendations Enterprise Architecture Governance managing and controlling architectures at an enterprise-wide level SOA Governance managing the portfolio of services, planning development of new services and updating current services Failure to consider Governance will mean architecture work will be in vain Solutions will become tactical, unaligned to strategic objectives. Loss of efficiency as re-use wains and duplication increases The SAP EA Framework, based on TOGAF, provides useful methods, tools, and content to help organizations execute Enterprise Architecture Governance An EA Governance Framework contains 5 key dimensions : Organization, Process, Standards, Tools and KPIs SAP 2007 / Page 40

Thank you! Q & A Contact: franck.lopez@sap.com SAP 2007 / Page 41

Copyright 2007 SAP AG All rights reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP -Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten. SAP 2007 / Page 42