The Five Key Elements of Enterprise Services Architecture

Eric WeiSAP Platinum ConsultantCoworker - NJ Computer Professionals Society

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 2

Time for Change: IT is Entering its Third Market Area

Enterprise services architecture is more than Web services

An enterprise services platform for business process innovation emerges

A huge ecosystem develops around it

Main-frame

Enterprise Services

Architecture

Three-Tier Client/Server

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 3

Enterprise Services ArchitectureBusiness Value Drives Service Enablement

BusinessValue

Generation

Level ofService

Enablement

40%

20%

2004 2005 2006

40%

80%

ProcessEfficiency (B2B)

UserProductivity

DeploymentFlexibility

75%

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 4

ARCHITECTUREFOR CHANGE

The 5 Key Elements of Enterprise Services Architecture

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 5

Five Key Elements of Enterprise Services Architecture

ANALYTICS/REPORTING

Bus.Partner

Legacy

PEOPLE PRODUCTIVITY

SAP NetWeaver

SERVICE COMPOSITION

Business Objects, Components, and Engines

PartnerServices

EnterpriseServices

RepositorySERVICE

ENABLEMENT

LIFE-CYCLELIFE-CYCLE MGMT

SAP’s Enterprise Services

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 6

First Key Element of Enterprise Services Architecture:Service Enablement

Bus.Partner

Legacy

SAP NetWeaver

Business Objects, Components, and Engines

PartnerServices

EnterpriseServices

RepositorySERVICE

ENABLEMENT

SAP’s Enterprise Services

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 7

Situation Today:Multiple Application Databases & Proprietary APIs

Build composite

applica-tions

Buildconnectors

tosystems

Buildconnectors

fromsystems

Changeprocesses

? ? ?

?

ERP(Supplier)

CRM(Supplier)

SRM(internal)

ERP(internal)

CRM(internal)

SRM(Buyer)

Databaseintegration +proprietary

techniques for cross-DB

integration

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 8

What Is Needed:A Services-Enabled Business Process Platform

User Interfaces

SAP NetWeaver

Composite Applications

Business Objects, Components, and Engines

Openness Transparent unlimited access Unified cross-system Integration

Model Extensibility of services Standardization of services

Common Enterprise ServicesArchitecture Service Patterns for All Platform Objects

Common Enterprise ServicesArchitecture Services Repository with Business Content

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 9

Second Key Element of Enterprise Services Architecture:People Productivity

PEOPLE PRODUCTIVITY

SAP NetWeaver

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 10

Situation Today:People Work as Human Integrators

Purchaser Production Planner Accountant

ERP(Supplier)

CRM(Supplier)

SRM(internal)

ERP(internal)

CRM(internal)

SRM(Buyer)

People as “Human

Integrators”

“Hard-Wired”Enterprise

Applications

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 11

An Example of a Portal Workcenter

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 12

Third Key Element of Enterprise Services Architecture:Analytics/Reporting

ANALYTICS/REPORTING

SAP NetWeaver

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 13

Sales Representatives

ERP(Supplier)

CRM(Supplier)

SRM(internal)

ERP(internal)

CRM(internal)

SRM(Buyer)

Situation Today:Inside Information Only for Specialists

Transactional Users

Hidden Process

Integration

Marketing Specialist

DataAnalysts

Information Flow

Broken

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 14

Analytics/Reporting

What Is Needed:Embedded Analytics

SAP NetWeaver

Business Objects, Components, and Engines

Seamless integration of transactional and analytical content

Unified modeling environment for business users and developers

High performance use of BI

Business Intelligence for People Empowerment

Information first approach Push principle Speed and flexibility On-the-fly analytical insight

People Productivity

Service Composition

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 16

Enterprise Services ArchitectureInformation Integration - Examples

Last data refresh: 26.05.2004 17:26:24 from user: PZENCKE

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 17

Fourth Key Element of Enterprise Services Architecture:Service Composition

SERVICE COMPOSITION

SAP NetWeaver

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 18

Situation Today:Coded One-to-One Process Integration

Transaction

CRM(Supplier)

ERP(internal)

CRM(internal)

SRM(Buyer)

Transactions Within

Application Silos

Rigid Processes,One-to-One

Integrated by Coding

Transaction Transaction Transaction Transaction

SRM(internal)

SAP AG 2004, SAP TechEd ’04 San Diego / Dr. Peter Zencke / 19

What Is Needed:A Common Application Life-Cycle Management

User Interfaces

SAP NetWeaver

Composite Applications

Business Objects, Components, and Engines

Lower TCO Deployment management Cross-solution configuration

management Operations and support

services Cross-system application

change management

LIFE-CYCLE MGMT

Common change managementalways on – never seen

Solution landscapemanagement