SAP Enterprise Architecture:

42  Download (0)

Full text

(1)

SAP Enterprise Architecture:

A governance model to ensure the successful

adoption of Enterprise SOA

Franck Lopez, Global Director, Enterprise Architecture

Field Services, Solution Management

(2)

SAP Enterprise Architecture:

A governance model to ensure the successful adoption of Enterprise SOA

Franck Lopez, Global Director, Enterprise Architecture

Field Services, Solution Management

(3)

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

(4)

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

(5)

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

(6)

What is Enterprise Architecture Governance?

Enterprise Architecture Governance does not and cannot operate in isolation.

Enterprise Architecture

Business Strategy and Planning

Research

and

Innovation

Programs and Projects

(PMO)

Service

Delivery

Landscape

Provide

Evidence of

Architecture

Compliance

Support and

Align Projects

to Strategic

Roadmap

Set Strategy

and Vision

Support

Effective

Governance

Monitor

Obsolescence

Learn from

Operations

Support and

Model

IT Landscape

Align

innovation to

strategy,

using “proof

of concepts”

Monitor

Technology

Innovations

and Align to

Vision

(7)

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

(8)

Why is Governance important in Enterprise

SOA?

“However, through 2010,

the biggest barriers to SOA adoption will be

non-technical 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

“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

“…. to enable an SOA governance strategy,

companies must re-evaluate their

higher-level 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”

(9)

Why Enterprise Architecture Governance?

“…. to enable an SOA governance strategy,

companies must re-evaluate their

higher-level 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

(10)

Systems of Architecture Governance

breakdown

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.

We have defined our TO-BE Information Architecture and a set of Design Standard,

but no-one takes any notice of them …

(11)

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

„

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.

(12)

Enterprise SOA Governance is wider than that

Realizing Enterprise SOA Benefits

Safeguarding Enterprise SOA Projects

Accelerated Learning Curve

Re-usable Services for the Enterprise

Enterprise Architecture

Governance

Business

Strategy

Solution Planning

& Operations

IT

Strategy

ESOA

Governance

(13)

Enterprise SOA Governance

ES Design & Modeling Methodology

Service Design

PIC 0 PIC 1 GDT-PIC PIC 3 In ES Repos.

Raw

design

Decision on

service cut

GDT PIC

review

Final

design

Imple-mentation

ES Toolset & Lifecycle Mgmt.

ES Community

Product

CDG

Outward

CDG

CAG

EA Governance

Resource Base

Extensions SAP Technology Reference Models SAP Business Reference Models TOGAF Architecture Development Method TOGAF Resource Base SAP Content Tools SAP Implementation

Tools EA Modelling Tools

SAP Tooling Extensions SAP Mapping Extensions SAP Enterprise Architecture

Framework extensions Architecture Development Method Content Metamodel

Templates, Examples and Case Studies Usage Guidelines Resource Base Extensions SAP Technology Reference Models SAP Business Reference Models TOGAF Architecture Development Method TOGAF Resource Base TOGAF Architecture Development Method TOGAF Resource Base SAP Content Tools SAP Implementation

Tools EA Modelling Tools

SAP Tooling Extensions

SAP Content Tools

SAP Implementation

Tools EA Modelling Tools

SAP Tooling Extensions SAP Mapping Extensions SAP Enterprise Architecture

Framework extensions Architecture Development Method Content Metamodel

Templates, Examples and Case Studies Usage Guidelines

Processes

Standards and Templates

People and Organization

KPIs and Monitoring

Resource

Base

SAP Enterprise

Architecture

Framework

ESOA

Governance

(14)

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

(15)

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

(16)

How the SAP EA Framework accelerates good

Governance

R

e

leased

t

o

t

h

e

O

p

e

n

Gro

u

p

SAP Enterprise Architecture Framework

for Enterprise SOA

TOGAF Architecture

Development Method

TOGAF

Resource Base

Resource Base

Extensions

SAP Technology

Reference Models

SAP Business

Reference Models

SAP Enterprise Architecture

Framework extensions

Architecture

Development

Method

Content

Metamodel

Templates, Examples and Case

Studies

Usage Guidelines

R

e

leased

t

o

t

h

e

O

p

e

n

Gro

u

p

SAP Content

Tools

SAP Implementation

Tools

EA Modelling Tools

SAP Tooling Extensions

SAP Mapping Extensions

Maps SAP terminology,

content, reference models

and products into the

metamodel and the EA

Toolset

FEWER REJECTIONS &

FASTER

TIME-TO-MARKET

Provides an EA Tool Reference

Implementation, and other SAP Tools

REUSABILITY &

Identifies the key inputs,

steps and outputs for

implementing Governance

GUIDANCE &

BEST PRACTICES

Enables standard terms and

concepts , and tailored

stakeholder views of the

architecture

MORE EFFECTIVE

PROCESSES & COMMON

Provides standard

patterns and reference

models to improve

architecture quality

LOWER COSTS &

LESS RISK

(17)

Examples of SAP EAF Governance Extentions

SAP EAF to SAP

Roadmap Mapping

Motivation Functional Requirements Organizational Impacts Solution Infrastructure Solution Scope Solution Security Business Strategy Business Process Models Organizational Structure Work Package IT Infrastructure Gaps

Roles and Authorization Technology Strategy

Discover

Evaluate

Implement

Operate ESA and SAP NewWeaver Vision Value

Session ESA Opportunity Workshop

TCO Discovery Session Enterprise SOA Pulse Check

Plan Services

Build Services Run Services Continuous Operations and

Governance ESA / NetWeaver Community ESA Leader in Your Industry

As-Is Analysis and Opportunity Assessment

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 Business and IT Strategy Business Processes Organization Charts Project Portfolio IT Landscape Strategy to ESOA Mapping

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 Role Design Requirements Constraints Project Vision and

Strategy

Business Services

Applications

Application Landscape

Solution Data Aspects

Entity Model Business Function Models

Implementation

Governance

Narrative

Outputs Steps Impact Analysis Architecture Contracts for Architecturally

Governed Change Activity Architecturally Compliant Systems

Im plement EA Governance Framework

Review Project Approach and Output Guide Project Implementation

Implementation Governance

Phase

Inputs

SAP EAF Implementation Governance Phase Worksheet SAP EAF Im plem entation Governance

Narrative Document

Detailed Implementation and Migration Plan

Solutions Building Blocks Architecture Repository TOGAF ADM Implementation

Governance Narrative TOGAF Re fe re nc e Ma te ri a l P h a s e S p e c if ic I n p u ts P re -E x is ti n g o r P re v io u s P h ase I n p u ts

Architecture Change

Management Narrative

IS IT A C OM P LE X CH AN G E? C HE C K Y E S/N O

„ Are there significant new Busin ess Drivers, Goals and O bjectives that m ean the Bu siness Strategy is changing?

„ H as a significant event like a M erg er/Acquisition or D ivestiture occu rred that w ill imp act the architecture of all d om ains?

„ Are there n ew technology develop ments that have significan t b usiness user imp act?

„E.g. availab ility of affordable m obile computing in a w ireless m ode

„ Are there n ew technology compo nents and guidelines for use in deplo ym ent of the architecture?

„E.g. w eb service standards

„ D oes the change impact tw o stakeholder classes o r m ore?

„ D oes it im pact two dom ains or mo re?

„ D oes it involve adding or rem oving large nu mb ers of m etam od el ob ject instances in m ore th an tw o do mains?

„E.g. adding one o r tw o new Data Entities in Data Architecture dom ain, plus new business p rocesses in th e Business Architecture do main , plus new T echnology classes in the T echnical R eference Model th at impacts the T echnology Architecture?

„

AC T IO N:

„ Progress via new arch itecture eng agement

„ F ollow the SAP EAF process again

„ T he En terprise Architect needs to agree and scope a new Request for Arch itecture W o rk as detailed in Unit 3 – Architectu re Vision and Unit 12 – Using SAP EAF in Architecture Engagem ents

SAP Specific

Technical Reference

Business Applications Infrastructure Applications

Application Programming Interface

Communication InfrastructurInterface

CommunicationIntfrastructure

Operating System Services Network Services G raphi c s & Im age Da ta M anagem ent Da ta Int e rc h ange In te rnat ional O perat ions U s er I nte rfac e Locat io n & D ire ct ory T ra nsa ctio n P ro c ess in g S yste m & N e tw o rk M a n agem ent Sec u rity So ftw are E ngi neeri n g Qualities Q u alit ie s Qua lit ie s Qualities Business Applications Infrastructure Applications

Application Programming Interface

Communication InfrastructurInterface

CommunicationInfrastructure

Operating System Services Network Services G raphi c s & Im age Da ta M anagem ent Da ta Int e rc h ange In te rnat ional O perat ions U s er I nte rfac e Locat io n & D ire ct ory T ra nsa ctio n P ro c ess in g S yste m & N e tw o rk M a n agem ent Sec u rity So ftw are E ngi neeri n g Qualities Q u alit ie s Qua lit ie s Qualities Business Applications Infrastructure Applications

Application Programming Interface

Communication InfrastructurInterface

CommunicationIntfrastructure

Operating System Services Network Services G raphi c s & Im age Da ta M anagem ent Da ta Int e rc h ange In te rnat ional O perat ions U s er I nte rfac e Locat io n & D ire ct ory T ra nsa ctio n P ro c ess in g S yste m & N e tw o rk M a n agem ent Sec u rity So ftw are E ngi neeri n g Qualities Q u alit ie s Qua lit ie s Qualities Business Applications Infrastructure Applications

Application Programming Interface

Communication InfrastructurInterface

CommunicationInfrastructure

Operating System Services Network Services G raphi c s & Im age Da ta M anagem ent Da ta Int e rc h ange In te rnat ional O perat ions U s er I nte rfac e Locat io n & D ire ct ory T ra nsa ctio n P ro c ess in g S yste m & N e tw o rk M a n agem ent Sec u rity So ftw are E ngi neeri n g Qualities Q u alit ie s Qua lit ie s Qualities SAP NetWeaver SAP for <Industry>

„SAP Enterprise Portal

„SAP Master Data Mgmt

„SAP Business Intelligence

„SAP Exchange Infrastructure

SAP xApps

„SAP xApp Resource

& Program Mgmt

„SAP xApp Product

Definition „SAP xApp Mergers &

Acquisition „...

SAP Packaged

Solutions „Service Management for < Industry> „Financial Insightsfor <Industry>

„...

„ ---„... „SAP for Aerospace & Defense

„SAP for Automotive

„...

SAP Business Suite

„SAP All -in-One SAP Smart Business Solutions „SAP Business One „SAP Business One Server SAP ERP Analytics Financials Human Resources Corporate Services Operations SAP PLM SAP SCM SAP SRM SAP CRM

Service Contract

„ General ‹ Reference ‹ Name ‹ Description ‹ Source ‹ Owner ‹ Type ‹ Version „ Technical ‹ Invocation ‹ Invocation Preconditions

‹ Master Data Impacted

‹ Behaviour Characteristics ‹ Post Condition „ Non-Functional Requirements ‹ Throughput ‹ Throughput period ‹ Growth ‹ Growth period ‹ Service times

‹ Peak profile short term

‹ Peak profile long term

‹ Security requirements

‹ Response requirements

„ 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

(18)

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

(19)

The Enterprise Architecture Governance

Service

… is a structured project approach based on SAP Consulting best-practices.

Analyze

Conduct Enterprise

Architecture Maturity and Best

Practice workshop

Analyze Strategies and Derive

Imperatives

Perform Assessment and

Analyze Gaps

Initiate Stakeholder

Management

Define To-Be Enterprise

Architecture Governance

Vision

Design

Transform

Improve

Design Personnel/Role

Development

Design Organizational Change

Management activities and

KPIs

Create Transformation

Roadmap

Design Enterprise Architecture

Organization and Roles

Design Enterprise Architecture

Governance Processes /

Standards

Concept

Transition

Deploy Organizational

Structures / Processes based

on roadmap

Conduct Personnel/Role

Development activities

Implement Design Authority /

Governance processes /

Standards

Conduct Change Management

Activities

Implement EA Tools and KPIs

Decision

Design and implement

continuous improvement

process

(20)

The SAP Enterprise Architecture Governance

Service: the Five Key Dimensions

Enterpr

ise A

rchit

ect

ure

Pr

oject

s and

Programs

Solution Implementation Lifecycle

Governance Framework

2. Processes

3. Standards and Templates

1. People and organization

Business Strategy and Planning

5. KPIs and Monitoring

4. Resource Base

Research and

Innovation

Service Deliver

y

Landsc

a

pe

Do I have business service

specialist promoting and

identifying re-use

opportunity ?

Service Design

PIC 0 PIC 1 GDT-PIC PIC 3 Repos.In ES

Raw design Decision on service cut GDT PIC review Final design Imple-mentation Service Design

PIC 0 PIC 1 GDT-PIC PIC 3 Repos.In ES

Raw design Decision on service cut GDT PIC review Final design Imple-mentation

Is my Design process

integrated to my Service

Design process ?

Am I building 100s of services

that no-one is reusing? Are

they too coarse-grained ?

How are projects that build

services being governed?

Do I have service

description, interface

standards ?

Does my ES Repository

align to my

Resource Base ?

(21)

The Enterprise Architecture Governance

Service

Step 1: Analyze

Work Package

Overview

Scoping for To-Be

design

Analyze

… … …

… …

… … …

Present SAP’s best-practices model

Str

uc

tur

e

Pr

oc

es

se

s

Pe

op

le

Identify stakeholders

Derive strategic imperatives

Conduct Enterprise

Architecture Maturity and Best

Practice workshop

Analyze Strategies and Derive

Imperatives

Perform Assessment and

Analyze Gaps

Initiate Stakeholder

Management

Define To-Be Enterprise

Architecture Governance

Vision

Perform GAP analysis

0 1 2 3 4 5 Business IT-Alignment Governance People Architecture Process Architecture Development Stakeholder Involvement Communication Influence and Impact

Readiness Expectation

(22)

Enterprise Architecture Governance

… is based on standard architecture frameworks and provides the complete set of best practices

ready to use from SAP Consulting.

Use the SAP Consulting framework to accelerate the design of your

Processes

People and Organization

Resource

KPIs

Base

Organization

Budget ownership

New tasks and

roles

Organizational

structure

Architecture Board/

Design Authority

Competencies

Identification and

allocation of HR

Skill profiles

(To-Be, As-Is)

Training

Knowledge

management

Enterprise

Architecture

Controlling

KPIs

Benefit tracking

Budget and

cost allocation

Compliance

Risk

management

Business

Process

Management

Task

Descriptions

Processes

RACI

Strategic

Alignment

Alignment of

business and IT

objectives

Requirements

analysis

management

Project portfolio

management

Service

Landscape

Operations

EA Tools

Maintenance

Processes

Metamodel and

View Mapping

Tools Strategy

and Selection

Tool

Implementation

Standards and

Templates

Standards

Standards for

applications

Standards for

IT infrastruct.

Standards for

enterprise

services

Standards for

design and

modeling

Templates

Detailed Design

Support Model

Outline Design

Business

Opportunity

(23)

1. People and Organization

Project

A

Project

B

Project

C

Project

D

Program

Design

Authority

Program

Design

Authority

Design Authority

Service

Delivery

Management

Program

Management

Office

IT Strategy Board

IT Strategy Board

sets the overall governing IT

strategy

The Design Authority

responsible for governing and

maintaining the architecture

that delivers the strategy

co-ordinates, shapes and

reviews all programs

Program Design Authorities

delegated responsibility for

shaping and review an

individual program

Projects

use their own staff to ensure

their own developments are

(24)

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

(25)

1. People and Organization

Design Authority

IT Strategy Board

Program Design Authority

Project A

Program Design Authority

Principal

Architect

CIO

Service

Manager

Business

Champions

Enterprise

Architect 2

Infrastructure

Architect

Principal

Architect

Enterprise

Architect 1

Service

Manager

Project B

Enterprise

Architect 1

Enterprise

Architect 2

Project C

Project D

Solution

Architect 1

Business

Analyst 1

Solution

Architect 2

Business

Analyst 2

Solution

Architect 3

Business

Analyst 3

Solution

Architect 4

Business

Analyst 4

CIO

chairs the IT Strategy Board

Principal Architect

chairs the Design Authority

Enterprise Architects

aligned to programs and

assurance the program

architecture

specialize in Business,

Application, Data or

Technology

Solution Architects

aligned to projects and assure

the solution architecture

Other roles play their part :

Business Analysts or Domain Experts

Service Manager

(26)

2. Processes – Governance in context

Define

Service

Levels &

Interfaces

Produce

Service

Design

Cost

Allocation

of Shared

Services

Monitor

Service Reuse

And

Performance

Define

Organization

Vision

and

Capability

Monitor

Service

Obsolescence

Service

Acceptance

Into

Operation

Decide

Service

Cut

Assure

Integration

Define

Enterprise

Services

Taxonomy

Select

Strategic

Technology

Produce

Outline

Designs

Produce

Detailed

Designs

Strategic

Supplier

Radar

Strategic

Technology

Radar

Maintain

IT

Vision

Maintain

Enterprise

Architecture

Assure

Designs

Demonstrate

Innovation

Monitor

EA

KPIs

Maintain

Solution

Resource

Base

Solution

Acceptance

Monitor

Operations +

Obsolescence

ACQUIRE

AND IMPLEMENT

PLAN AND

ORGANIZE

MONITOR

AND EVALUATE

DELIVER

AND SUPPORT

IT Governance

Enterprise Architecture Governance

(27)

2. Processes – Governance in context

ACQUIRE

AND IMPLEMENT

PLAN AND

ORGANIZE

MONITOR

AND EVALUATE

DELIVER

AND SUPPORT

(28)

2. Example TO-BE Level 0 Processes Map

Select

Strategic

Technology

Strategic

Supplier

Watch

Supplier

Selection

Strategic

Technology

Watch

Approved Designs

Maintain

IT

Vision

Maintain

Enterprise

Architecture

Business

Roadmap

Business

Vision

Align Vision

Align Roadmap

Produce

Outline

Designs

Requirements

Management

Assure

Designs

Project

Lifecycle

Produce

Detailed

Designs

Testing

High Level Test

Strategy

Requirements

Agreed

Approved Designs

Business

Engagement

Demonstrate

Innovation

New Opportunities

Service

Delivery

Maintain

Solution

Resource

Base

Solution

Handback

Service Acceptance

Monitor

Operations +

Obsolescence

(29)

2. Processes – SAP EAF Governance aligned to COBIT (IT

governance framework from the IT Governance

Institute®)

ACQUIRE

AND IMPLEMENT

Select

Strategic

Technology

Produce

Outline

Designs

Produce

Detailed

Designs

PLAN AND

ORGANIZE

Strategic

Supplier

Watch

Strategic

Technology

Watch

Maintain

IT

Vision

Maintain

Enterprise

Architecture

Assure

Designs

Demonstrate

Innovation

DELIVER

AND SUPPORT

Maintain

Solution

Resource

Base

Solution

Handback

MONITOR

AND EVALUATE

Monitor

EA

KPIs

Monitor

Operations +

Obsolescence

(30)

Processes – Governance in context

Define

Service

Levels &

Interfaces

Produce

Service

Design

Cost

Allocation

of Shared

Services

Monitor

Service Reuse

And

Performance

Define

Organization

Vision

and

Capability

Monitor

Service

Obsolescence

Service

Acceptance

Into

Operation

Decide

Service

Cut

Assure

Integration

Define

Enterprise

Services

Taxonomy

Select

Strategic

Technology

Produce

Outline

Designs

Produce

Detailed

Designs

Strategic

Supplier

Radar

Strategic

Technology

Radar

Maintain

IT

Vision

Maintain

Enterprise

Architecture

Assure

Designs

Demonstrate

Innovation

Monitor

EA

KPIs

Maintain

Solution

Resource

Base

Solution

Acceptance

Monitor

Operations +

Obsolescence

ACQUIRE

AND IMPLEMENT

PLAN AND

ORGANIZE

MONITOR

AND EVALUATE

DELIVER

AND SUPPORT

SOA Governance

Early Service

Design

Direction

Outline and Detailed Service

Design Governance

Update Enterprise

Architecture, gather best

Check what was designed

(31)

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

(32)

3. Standards & Templates

Standards ensure:

„

Enterprise complexity is reduced

„

Solutions can be maintained efficiently

„

Business and IT are aligned

Templates ensure:

„

the right information is available

„

the right quality is produced

„

consistency between projects

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

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

(33)

4. Resource Base

Infrastructure

Consolidation Extension Process ModellingExtension Business / IT AlignmentExtension Governance Extension Data Modelling Extension Core Content

ARCHITECTURE VISION, CONTEXT AND ROADMAP

BUSINESS ARCHITECTURE TECHNOLOGY ARCHITECTURE APPLICATION ARCHITECTURE DATA ARCHITECTURE Associated With All Objects Organisation Unit Goal Objective Measure Governance Extension

(Business, Information System) Service

Services are Contained in Core , Business / IS split supports the Business / IT Alignment Extension

Function Process Actor Role Control Process Extension Event Process Extension Product Process Extension Data Entity Logical Information Component Data Extension Location Infrastructure Consolidation Extension Physical Information Component Data Extension Logical Application Component Physical Application Component Infrastructure Consolidation Extension Logical Technology Component Infrastructure Consolidation Extension Physical Technology Component Principle Constraint Requirement

Contract Governance

Extension

Gap Work Package

Driver Platform Service Owns and governs Operates in Operates in Is Hosted in Is Hosted in Is Hosted in Encapsulates Encapsulates Resides within Supplies Is Supplied By Is Realised by Realises Operates on Is processed by Provides, consumes Is accessed and updated through Resides within Is implemented on Provides platform for Implements Is realised through Contains C o nt a in s Co nt a in s Co n ta in s Co n ta in s Contains Belongs to C on su m e s Participates in Interacts with, Performs Performs task in Generates, Resolves Produces Is Produced by Is owned by Owns Supports, Is performed by Accesses Can be accessed by Orchestrates, decomposes Supports, Is realised by Is bounded by Provides governed interface to access Produces Is Produced by Involves Participates in Involves Is Resolved by, Is Generated by Generates, Resolves Is Resolved by Is Resolved by, Is Generated by Resolves Supports, Is realised by O rch es tra tes , de co m po ses Ensures correct operation of Is gu id ed by Governs, Measures Is governed and measured by Is Provided to Is owned and governed by Is tracked against Sets performance criteria for Sets performance criteria for Is tracked against Is motivated by Motivates Creates Addresses Is realised through Realises Service Quality Governance Extension Applies to Meets Applies to Meets Is Performed by Is Supplied or Consumed by Supplies or Consumes Infrastructure

Consolidation Extension Process ModellingExtension Business / IT AlignmentExtension Governance Extension Data Modelling Extension Core Content

ARCHITECTURE VISION, CONTEXT AND ROADMAP

BUSINESS ARCHITECTURE TECHNOLOGY ARCHITECTURE APPLICATION ARCHITECTURE DATA ARCHITECTURE Associated With All Objects Organisation Unit Goal Objective Measure Governance Extension

(Business, Information System) Service

Services are Contained in Core , Business / IS split supports the Business / IT Alignment Extension

Function Process Actor Role Control Process Extension Event Process Extension Product Process Extension Data Entity Logical Information Component Data Extension Location Infrastructure Consolidation Extension Physical Information Component Data Extension Logical Application Component Physical Application Component Infrastructure Consolidation Extension Logical Technology Component Infrastructure Consolidation Extension Physical Technology Component Principle Constraint Requirement

Contract Governance

Extension

Gap Work Package

Driver Platform Service Owns and governs Operates in Operates in Is Hosted in Is Hosted in Is Hosted in Encapsulates Encapsulates Resides within Supplies Is Supplied By Is Realised by Realises Operates on Is processed by Provides, consumes Is accessed and updated through Resides within Is implemented on Provides platform for Implements Is realised through Contains C o nt a in s Co nt a in s Co n ta in s Co n ta in s Contains Belongs to C on su m e s Participates in Interacts with, Performs Performs task in Generates, Resolves Produces Is Produced by Is owned by Owns Supports, Is performed by Accesses Can be accessed by Orchestrates, decomposes Supports, Is realised by Is bounded by Provides governed interface to access Produces Is Produced by Involves Participates in Involves Is Resolved by, Is Generated by Generates, Resolves Is Resolved by Is Resolved by, Is Generated by Resolves Supports, Is realised by O rch es tra tes , de co m po ses Ensures correct operation of Is gu id ed by Governs, Measures Is governed and measured by Is Provided to Is owned and governed by Is tracked against Sets performance criteria for Sets performance criteria for Is tracked against Is motivated by Motivates Creates Addresses Is realised through Realises Service Quality Governance Extension Applies to Meets Applies to Meets Is Performed by Is Supplied or Consumed by Supplies or Consumes

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

A Resource Base helps prevent:

„

Proliferation of non-standard artifacts

„

Unmaintainable Visio and Excel files

(34)

4. Common objects promote common

standards

“Real - World” Enterprise

Reference

Models

Application

Platform

Queries / Analysis

Catalogs, Matrices

and Views

Standard Catalogs

Matrices and Views

Metamodel

Metamodel

Application Architecture Core Views Catalogs Matrices Extension Views Data Architecture Core Views Catalogs Matrices Extension Views Technology Architecture Core Views Catalogs Matrices Extension Views Business Architecture Core Views Catalogs Matrices Extension Views

Functional Decomposition View

Application Communication View Application and User Location View

Conceptual / Logical ER View Data Dissemination View

Data Entity/ Business Function Matrix

Environments and Locations View

Organisation / Actor Catalog Role Catalog Actor/ Role Matrix

Application Portfolio Catalog

Technology Portfolio Catalog Technology Standards Catalog Service / Function Catalog

Role/ System Matrix

Data Entity/ Information Component Catalog

Location Catalog

Platform Decomposition View

System / Data Matrix

Process Flow View Use Case View Organization Chart View

Event View

Process / System Realization View Enterprise Manageability View

Data Lifecycle View Data Security View

Networked Computing / Hardware View Communications Engineering

View

Process / Event / Control / Product Catalog

Driver / Goal / Objective Catalog

System / Organisation Matrix System / Function Matrix

System / Technology Matrix Application Interaction Matrix

Business Interaction Matrix Business Footprint View Service / Information View

Goal /Objective / Service View

Software Engineering View Software Distribution View Application Migration View

Data Migration View Entity Hierarchy View

Processing View

Contract/ Measure Catalog

Interface Catalog

Core Content Business / IT Alignment Extension Data Modelling Extension Process Modelling Extension Governance Extension Infrastructure Consolidation Extension Architecture Vision Core Views

Value Chain View Solution Concept View

Matrices

Stakeholder Map Matrix

Opportunities and Solutions Core Views

Project Context View Portfolio View

Requirements Catalogs Requirements Catalog Preliminary Catalogs Principles Catalog

Architecture

Resource Base

An Enterprise Architecture Resource Base models the enterprise and promotes common models

based on a single source of truth

(35)

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 ?

(36)

KPIs and Monitoring

% AS-IS architecture complete

% TO-BE architecture complete

% Migration Plans in-place

% Projects engaging design assurance

% Projects with solution architects

EA Coverage

# Projects reviewed/rejected

# Projects rejected 1st time

Frequency of reviews

% Projects engaging design assurance

% Projects with solution architects

EA Processes

# of architects in post

# of architects trained

# of architects certified

# of approved standards in place

EA Presence

# Projects compliant with strategy

# Project overruns >x months

Ease of Access to Information

Time to implement new capabilities

# of security incidents

Business Benefits

# Projects compliant with IT strategy

# Projects into support w/o issue

Rate of reactive infrastructure projects

# Applications rationalized

# Avoided purchases

IT Benefits

(37)

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

Agenda

(38)

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

(39)

Key for Realization of Enterprise SOA Benefits

Business Potentials

Strategic Potential

Normative Potential

Operative Potential

TCO Reduction Potentials

Reduction of Development Costs

Reduction of System Costs

Reduction of Operating Cost

4

Linking Applications

5

Process Automation

6

Flexible Deployment

Process Composition

Reusability

Common Platform

1

2

3

Enterprise SOA Benefits

„

People are focused on the strategic goal of building of an enterprise SOA

„

Processes and organizational structures are aligned to enterprise SOA

(40)

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

(41)

Thank you!

Q & A

(42)

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.

Figure

Updating...

References