The Five Key Elements of Enterprise Services Architecture

The Five Key Elements of Enterprise Services Architecture Eric Wei SAP Platinum Consultant Coworker - NJ Computer Professionals Society

Time for Change: IT is Entering its Third Market Area Enterprise Services Architecture Three-Tier Client/ Server Mainframe ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 2 n Enterprise services architecture is more than Web services n An enterprise services platform for business process innovation emerges n A huge ecosystem develops around it

Enterprise Services Architecture Business Value Drives Service Enablement Business Value Generation Level of Service Enablement 80% 75% 40% 2004 Process Efficiency (B 2 B) ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 3 2005 User Productivity 2006 Deployment Flexibility

ARCHITECTURE FOR CHANGE The 5 Key Elements of Enterprise Services Architecture ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 4

Five Key Elements of Enterprise Services Architecture PEOPLE PRODUCTIVITY ANALYTICS/REPORTING SERVICE COMPOSITION SAP Net. Weaver SERVICE ENABLEMENT Enterprise Services Repository SAP’s Enterprise Partner Services Business Objects, Components, and Engines Bus. Partner Legacy LIFE-CYCLE MGMT ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 5

First Key Element of Enterprise Services Architecture: Service Enablement SAP Net. Weaver SERVICE ENABLEMENT Enterprise Services Repository SAP’s Enterprise Partner Services Business Objects, Components, and Engines Bus. Partner ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 6 Legacy

Situation Today: Multiple Application Databases & Proprietary APIs Build composite applications ? ERP (Supplier) CRM (Supplier) SRM (internal) ? Build connectors to systems ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 7 ERP (internal) CRM (internal) SRM (Buyer) Database integration + proprietary techniques for cross-DB integration ? Change processes ? Build connectors from systems

What Is Needed: A Services-Enabled Business Process Platform User Interfaces Composite Applications Openness n Transparent unlimited access n Unified cross-system Integration Model n Extensibility of services n Standardization of services SAP Net. Weaver Common Enterprise Services Architecture Services Repository with Business Content Business Objects, Components, and Engines Common Enterprise Services Architecture Service Patterns for All Platform Objects ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 8

Second Key Element of Enterprise Services Architecture: People Productivity PEOPLE PRODUCTIVITY SAP Net. Weaver ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 9

Situation Today: People Work as Human Integrators Production Planner Purchaser ERP (Supplier) ã CRM (Supplier) SRM (internal) SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 10 ERP (internal) Accountant CRM (internal) People as “Human Integrators” SRM (Buyer) “Hard-Wired” Enterprise Applications

An Example of a Portal Workcenter ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 11

Third Key Element of Enterprise Services Architecture: Analytics/Reporting ANALYTICS/REPORTING SAP Net. Weaver ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 12

Situation Today: Inside Information Only for Specialists Information Flow Broken Sales Representatives Marketing Specialist Transactional Users ERP (Supplier) ã CRM (Supplier) SRM (internal) SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 13 Data Analysts ERP (internal) CRM (internal) SRM (Buyer) Hidden Process Integration

What Is Needed: Embedded Analytics 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 n n Information first approach Push principle Speed and flexibility On-the-fly analytical insight ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 14 People Productivity Analytics/Reporting Service Composition SAP Net. Weaver Business Objects, Components, and Engines

Enterprise Services Architecture Information Integration - Examples ã SAP AG 2004, SAP Tech. Ed Sanrefresh: Diego / Dr. 26. 05. 2004 Peter Zencke 17: 26: 24 / 16 Last’ 04 data from user: PZENCKE

Fourth Key Element of Enterprise Services Architecture: Service Composition SERVICE COMPOSITION SAP Net. Weaver ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 17

Situation Today: Coded One-to-One Process Integration Transaction CRM (Supplier) ã Transaction SRM (internal) SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 18 ERP (internal) Transaction CRM (internal) Transaction SRM (Buyer) Transactions Within Application Silos Rigid Processes, One-to-One Integrated by Coding

What Is Needed: A Common Application Life-Cycle Management User Interfaces Composite Applications SAP Net. Weaver Business Objects, Components, and Engines LIFE-CYCLE MGMT ã SAP AG 2004, SAP Tech. Ed ’ 04 San Diego / Dr. Peter Zencke / 19 Lower TCO n Deployment management n Cross-solution configuration management n Operations and support services n Cross-system application change management Solution landscape management Common change management always on – never seen