25
Enterprise Architecture & SAP Enterprise Architecture Framework Driving and Governing Your Business Transformation Laurent Rieu Office of the CTO EMEA June 11, 2008

Zlot Technologiczny SAP 2008 - Enterprise Architecture

  • Upload
    aamir97

  • View
    1.576

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Enterprise Architecture & SAP Enterprise ArchitectureFrameworkDriving and Governing Your Business Transformation

Laurent RieuOffice of the CTO EMEAJune 11, 2008

Page 2: Zlot Technologiczny SAP 2008 - Enterprise Architecture

1. Why Enterprise Architecture: Drivers, Benefits, Values2. Enterprise Architecture and Enterprise SOA3. SAP Delivering Enterprise Architecture

Agenda

© SAP 2008 / Page 2

Page 3: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Business Networks: How Do You Get There?How Do You Govern The Transformation?

You lack criticalmass to enter amarket alone

Complement anincumbent’soffer

Competition ispressuring margins

Divest non-core processes

Market rewardsrapid introduction ofnew products

Drive changesthrough brandpower

Customer problemrequires diversedisciplines to solve

Orchestrate astrusted advisor

© SAP 2007 / Page 3

Page 4: Zlot Technologiczny SAP 2008 - Enterprise Architecture

What is Enterprise Architecture?

Enterprise ArchitectureDefinition

The description of the current and future stateof an organization's business processes,

technology platforms and information systemsrequired to support the business strategy

How to get from the current architecture tofuture desired state

Enterprise ArchitectureGoal

Bring together Business and IT people in acommon understanding of how people,

process, data and technology must convergeto take the business strategy from vision to

reality

Why Enterprise Architecture?

The successful businesstransformation supported by IT

requires Enterprise Architecture:

How do I get there? What are thebest practices?

How do I control and govern thetransformation?

How can I ensure that IT is aligned tothe business?

How do I integrate solutions acrossthe organisation?

© SAP 2008 / Page 4

Page 5: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Enterprise Architecture Discipline

Key discipline facilitating a holistic view of anenterprise

Treats the entire enterprise as a System

Mechanism for enabling design, development,communication and understanding of the enterprise

Overarching goal is to manage the complexity of theenterprise

Align business strategies and implementations

Facilitate rapid change in order to maintain businessand technological advantages

Applicationand DataArchitecture

EAGovernance

TechnologyArchitecture

OrgStructure

EnterpriseData

ModelBusinessStrategy

ArchContext

BusinessArchitecture

ChangeMgmt

© SAP 2008 / Page 5

Page 6: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Benefits of Enterprise Architecture to theBusiness

Achievement of a company’s business strategy or of externaldrivers

Without a full understanding of business, application and technicalarchitectures, a business doesn’t know what it has or doesn’t have

Business processes and information consistencyEA unlocks the power of information whilst unifying information silos thatinhibit business processesIdentify processes, applications and data that need to be consistent

More reliability and security, less riskEA provides clear traceability between business processes, data, userroles, applications and infrastructure

Faster time-to-marketIf IT can introduce new technologies and functionalities faster, theorganization can respond to competitive pressures fasterThese areas are most likely to be spotted when business and IT staffcollaborate closely in the EA process

Innovations

© SAP 2008 / Page 6

Page 7: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Benefits of Enterprise Architecture to IT

Lower IT costsFaster design and development due to standard designs andcomponentsIT procurement efficiencies due to economies of scale

Better traceability of IT costsGreater understanding of the interrelated nature of business,application and infrastructure assets

More manageable complexityClear vision of As-Is and To-Be architecture and migration planComprehensive view of apps, software, infrastructure and theirinterrelatedness diminishes duplication and overlap

Less IT riskDeveloping a managed transformation plan means IT is prepared todeliver new capabilities in a timely mannerIT effort is aligned with the strategy and expectations set at the rightlevel

© SAP 2008 / Page 7

Page 8: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Components of Enterprise Architecture

BusinessStrategy

Requirements

Programs

Projects

PortfolioAnalysis

BusinessArchitectureBusinessArchitecture

Business Processes,Workflows, Transactions

and Collaboration

DataArchitectureDataArchitecture

Technology ArchitectureTechnology Architecture Software, Hardware, Server, OS, Network

ApplicationArchitectureApplicationArchitecture

Systems, Services,Functional Use Cases

Data, Business Objects,Exchange Formats,

Security and Privacy

© SAP 2008 / Page 8

Page 9: Zlot Technologiczny SAP 2008 - Enterprise Architecture

1. Why Enterprise Architecture: Drivers, Benefits, Values2. Enterprise Architecture and Enterprise SOA3. SAP Delivering Enterprise Architecture

Agenda

© SAP 2008 / Page 9

Page 10: Zlot Technologiczny SAP 2008 - Enterprise Architecture

What’s the difference between EA andEnterprise SOA?

Enterprise ArchitectureThe description of the current and futurestate of an organization's businessprocesses, technology platforms andinformation systems required to supportthe business strategy

Enterprise SOAAn application pattern that provides newtechnology and business capabilitywithin the boundaries set out byEnterprise Architecture Build

HomeGrown

HomeGrown

Build

HomeGrown

HomeGrown

Buy

CRM ERP ...

Buy

CRM ERP ...

ComposeCompose

When a customer is considering Enterprise SOA, either there is already an EAin place or there is a need to develop one…

© SAP 2008 / Page 10

Page 11: Zlot Technologiczny SAP 2008 - Enterprise Architecture

The need for Enterprise Architecture in EnterpriseSOA

Effective management of SOA requires a more formalized understandingof the IT landscape with explicit links to the business it supports

Alignment between business and IT is the challenge facing SOA adoptersSignificant differences between an SOA landscape and a traditional IT landscapeNew points of stress and focus

Technology can address many of these stress points ; but not allKey Risks

Proliferation of misaligned services at inappropriate levels of granularityservice sprawl

Inability to do impact assessment and overspend on infrastructurepoor service quality

Multiple technology stacks that are costly to support and do not interoperatecostly services

“Islands of services” tied to implementation specificsServices are brittle and have high operational costs

Inability for potential service consumers to identify services for re-useDuplicate services

© SAP 2008 / Page 11

Page 12: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Putting It Together - How EA can helpEnterprise SOA

Provides a set of tools and techniques to link Business-Led SOA to Developer-Led SOA

a robust and maintainable frameworkaddresses the non-technical challenges associated with SOA adoption

Defines structured traceable representations of business and technologylinks IT assets to the business they supportClear, maintainable and measurable

Supports impactassessment and portfoliomanagement

Provides a much richercontextImproves the ability tomanage change

Defines principles,constraints, frameworks,patterns and standards

Forms the basis of ongoinggovernance,Ensures aligned services,interoperability and re-use

BusinessStrategy

Requirements

Programs

Projects

PortfolioAnalysis

BusinessArchitectureBusinessArchitecture

Business Processes,Workflows, Transactions

and Collaboration

DataArchitectureDataArchitecture

Technology ArchitectureTechnology Architecture Software, Hardware, Server, OS, Network

ApplicationArchitectureApplicationArchitecture

Systems, Services,Functional Use Cases

Data, Business Objects,Exchange Formats,

Security and Privacy

BusinessStrategy

Requirements

Programs

Projects

PortfolioAnalysis

BusinessArchitectureBusinessArchitecture

Business Processes,Workflows, Transactions

and Collaboration

DataArchitectureDataArchitecture

Technology ArchitectureTechnology Architecture Software, Hardware, Server, OS, Network

ApplicationArchitectureApplicationArchitecture

Systems, Services,Functional Use Cases

Data, Business Objects,Exchange Formats,

Security and Privacy

© SAP 2008 / Page 12

Page 13: Zlot Technologiczny SAP 2008 - Enterprise Architecture

1. Why Enterprise Architecture: Drivers, Benefits, Values2. Enterprise Architecture and Enterprise SOA3. SAP Delivering Enterprise Architecture

Agenda

© SAP 2008 / Page 13

Page 14: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Why Enterprise Architecture is becomingprominent?

New External Pressures on customersCorporate Governance

Data Protection and Privacy

Increased Security Profile

The same old internal pressuresBusiness wants more from IT for less

IT wants to reduce complexity and cost

Increasing adoption of Enterprise SOANew issues for customers to handle

Specifically for SAPProduct Suite is richer: more components, moreoptions

SAP is developing its footprint in Industry Sectorswhere SAP is a secondary part of the Architecture

© SAP 2008 / Page 14

Page 15: Zlot Technologiczny SAP 2008 - Enterprise Architecture

© SAP 2007 / Page 15

Enterprise Architecture: Now a strategicinitiative for SAP

© SAP 2008 / Page 15

Page 16: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP Enterprise ArchitectureFramework for Enterprise SOA

EAF available under RoadmapComposer and integrated withSAP other assets

Global Hubof Enterprise Architects

Dedicated training and certificationfor Enterprise Architects

Enterprise Architecture Service Portfolioand Enterprise SOA Services

SAP Enterprise Architecture initiative

TRAINING

SERVICES

METHODOLOGY

TOOLS

SKILLS & RESOURCES

Global EA Community, with user groupsnotably ASUG, customers and partners

COMMUNITY

EAF

© SAP 2008 / Page 16

Page 17: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP Enterprise Architecture Framework:Leverage and Extends TOGAF…

Generic andapplicable to many types

of architectures Vendor-agnosticopen standard

ComprehensiveArchitecture

development method

Can be usedacross a wide variety

of industry typesand geographies

Technology- andSolution-independent

Tailorable to meetdifferent organizations

and industry needs

Business-ITAlignment

Traditional EA Frameworks generate a wealth of benefits for the Enterprise

Avoids re-inventingthe wheel

Large adoptionin the market

Available under a freeperpetual license

Possibility to participatein the evolution

of the Framework

BlackHole

There is still a blackhole…

© SAP 2008 / Page 17

Page 18: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP Enterprise Architecture Framework:Filling The Gaps With Extensive Content

Two critical features are missing intraditional Enterprise Architecture Frameworks

PackagedApplications

EnterpriseServiceOriented

Architecture

Accelerated timelines

A clear transitionbetween Enterprise

Architectureand Solution delivery

Practical guidance

Robust and maturereference models

ComprehensiveEnterprisedescription

Fully packaged toolsetincl. methodology

Templates, concreteexamples and an applied

case study

Best Practices

An explicitMetamodel

A clear definition of process

A completedelivery tool

A clear definition of terms

© SAP 2008 / Page 18

Page 19: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP Enterprise Architecture Framework:Mission Statement

© SAP 2007 / Page 19

SAP EAF is an extension of theTOGAF Enterprise ArchitectureFramework specificallydesigned to support theeffective adoption of packagedsolutions in the Service-Oriented Enterprise.

© SAP 2008 / Page 19

Page 20: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP EAF Overview

© SAP 2008 / Page 20

Rel

ease

d to

the

Ope

n G

roup

SAP Enterprise Architecture Framework for Enterprise SOA

TOGAF ArchitectureDevelopment Method

TOGAFResource Base

Resource BaseExtensions

SAP TechnologyReference Models

SAP BusinessReference Models

SAP Enterprise ArchitectureFramework extensions

ArchitectureDevelopment

Method

ContentMetamodel

Templates, Examples and CaseStudies

Usage Guidelines

Rel

ease

d to

the

Ope

n G

roup

SAP ContentTools

SAP ImplementationTools EA Modeling Tools

SAP Tooling Extensions

SAP Mapping Extensions

Page 21: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP EAF – Architecture Development Method

ArchitectureContext Iterations

ArchitectureDevelopmentIterations

ArchitectureDeploymentIterations

TransitionPlanningIterations

SAP EAF Processfollows TOGAFADM….but with

iterations

© SAP 2008 / Page 22

Page 22: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Master7+ years of experience in Enterprise ArchitectureIn- and externally recognized as an expert in his/her EnterpriseArchitecture fieldDeep practical EA experience, integration, optimization andarchitectural knowledgeAbility to provide strategic vision and realizationAbility to articulate EA at CxO levelLeading teams and projects

Associate1-3 years of experience in Enterprise ArchitectureHands-on skills to successfully implement ERP solutionsFoundation knowledge of at least one domain in EnterpriseArchitectureWorks in a mentored position within an experienced team

Professional3-7 years of experience in Enterprise ArchitectureProfessional ERP experience, advanced solution and processknowledge, industry expertiseDeep knowledge of at least 1-2 domains in EnterpriseArchitectureT-shaped: broad view across several dimensions, plus deepcapability to understand a specific areaWorks independently within teams to realize EA projects,capability of mentoring others

SAP Tiered Certification: New ProgramFramework

Master Level:Expert knowledgein EnterpriseArchitecture

ProfessionalLevel:Advancedknowledge inEnterpriseArchitecture

AssociateLevel:Foundation levelknowledge inEnterpriseArchitecture. Skillsto contribute to EAprojects.

© SAP 2008 / Page 23

Page 23: Zlot Technologiczny SAP 2008 - Enterprise Architecture

SAP Enterprise Architect Curriculum andCertification: Associate and Professional

SOA200

SAP Enterprise ArchitectFramework Level I

5 DaysSOA100

Enterprise SOAFundamentals

2 Days SOA110

Enterprise SOARoadmap

2 Days

SOA250

SAP Enterprise ArchitectFramework Level II

5 DaysSO220

TOGAF Training& Certification

4 DaysCertified ProfessionalSAP Enterprise Architect

Q4/08

Certified Associate SAPEnterprise Architect

SAP Certified AssociateEnterprise Architect

SAP Certified ProfessionalEnterprise Architect

SOA230

Aris Toolset for SAPEnterprise ArchitectFramework

2 Days

Certified Associate SAPEnterprise Architect

Q2/07

© SAP 2008 / Page 24

Page 24: Zlot Technologiczny SAP 2008 - Enterprise Architecture

Enterprise Architecture and SAP EAF:The Methodology for Enterprise SOA Adoption

Business Network Transformation requires guidance and rigor in orderto ensure Business and IT alignment and to deliver on its full promises

Enterprise Architecture as a corporate discipline helps govern thesuccessful transformation of a company’s business and IT landscapes

The New SAP Enterprise Architecture Framework is based on openstandards and may be used free of charge by our customers andpartners

It is specifically designed to support the effective adoption ofpackaged solutions in an Enterprise SOA environment

The New SAP Enterprise Architecture Framework is holistic, practicaland agile

Education materials, certification and service offerings are available

A global Enterprise Architecture Community is already created – withuser groups, customers and partners

© SAP 2008 / Page 25

Page 25: Zlot Technologiczny SAP 2008 - Enterprise Architecture

© SAP 2007 / Page 26

Thank you!