Claus von Riegen Director Web Services Standards, SAP AG Enterprise Services Standards UN/CEFACT 7 th UN/CEFACT Forum Lyon, France.

Claus von RiegenDirector Web Services Standards, SAP AG

Enterprise Services Standards

UN/CEFACT

7th UN/CEFACT ForumLyon, France

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 2

Enterprise Services Architecture

Enterprise Services Architecture (ESA)

- is SAP’s blueprint

- for a business process-driven approach

- to more productivity, flexibility and competitive advantage

- using a service oriented infrastructure.

SAP NetWeaver

- is the technology platform

- that enables ESA

- to drive innovation and enable business change.

LegacySystemLegacySystem

3rdParty3rd

PartySAPSAP

SAP NetWeaver SAP NetWeaver

Enterprise Services

Repository

Enterprise Services

Repository

SAP SAP 3rd Party 3rd Party SAP SAP

Composite Applications

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 3

Enterprise Services (Platform View)

Enterprise Standards Reliability, scalability, performance, security Driven by business and legal requirements Mostly user-specific Examples: throughput of 100.000 invoices per hour, Section 508 accessibility

Web Services Standards SOA using Internet standards (XML, HTTP, etc.) Driven by interoperability needs with partner platforms (e.g. IBM WebSphere, Microsoft .NET) Covered by W3C, OASIS, WS-I Examples: WSDL, SOAP, WS-Security, WS-ReliableMessaging

LegacySystemLegacySystem

3rdParty3rd

PartySAPSAP

SAP NetWeaver SAP NetWeaver

Enterprise Services

Repository

Enterprise Services

Repository

SAP SAP 3rd Party 3rd Party SAP SAP

Composite Applications

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 4

Take The Business Perspective

SOA IS REQUIRED BUT NOT ENOUGHSOA IS REQUIRED BUT NOT ENOUGH

Common Business Semantics are required

SOASOA

ESES

ESAESA

++

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 5

Enterprise Services (Business Application View)

Business Standards Common business language (processes, document and data structures, codelists)

Driven by user requirements, often context-specific

Covered by UN/CEFACT and various industry consortia (e.g. CIDX, GS1, RosettaNet, S.W.I.F.T.)

LegacySystemLegacySystem

3rdParty3rd

PartySAPSAP

SAP NetWeaver SAP NetWeaver

Enterprise Services

Repository

Enterprise Services

Repository

SAP SAP 3rd Party 3rd Party SAP SAP

Composite Applications

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 6

The Business Standards Dilemma

Users Need to integrate with

businesses from other industries

Do not want to learn, deploy and maintain different integration approaches

Industry Communities Need to provide a complete

integration specification Do not want to define

everything from scratch

SAP Needs to support almost any

industry Does not want to provide and

maintain numerous mapping approaches

Mill Products

FinancialService Provider

Healthcare

HighTech

Banking

ConsumerProducts

Higher Education& Research

Aerospace& Defense

Telco

Retail

Media

Oil & Gas

Mining

Pharma

Insurance

Automotive

Engineering &Construction

Chemicals

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 7

Introducing Standards for Standards

Development Methodology Standards

Modeling and design rules

Driven by development and integration efficiency and quality needs

Covered by OMG, UN/CEFACT

Examples: UML, XMI, CCTS, XML NDR

Effectively enhance reuse and address the Business Standards Dilemma

SAP takes the lead in leveraging UN/CEFACT CCTS and XML NDR for the semantical definition of Enterprise Services

LegacySystemLegacySystem

3rdParty3rd

PartySAPSAP

SAP NetWeaver SAP NetWeaver

Enterprise Services

Repository

Enterprise Services

Repository

SAP SAP 3rd Party 3rd Party SAP SAP

Composite Applications

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 8

Platform Ecosystem

Collective Innovation- Customers, Partners, ISVs & SAP- Develop and prioritize Enterprise Service Definitions

Based on Open Standards- Interoperability: Web Services- Methodology: CCTS, etc.

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 9

Next Steps

SAP will launch an Ecosystem for Enterprise Services (early 2006) Customers and Partners shape the future scope and design of

Enterprise Services

Better planning for all involved parties

Enhanced application interoperability

Individual business standards are leveraged whenever deemed appropriate

Efficient and reliable exchange of business standards neededCommon methodology needs to be applied

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 10

Recommendations

UN/CEFACT Continuously improve efficiency and quality of standards development

process

Adopt IPR policy that allows contributions of software vendors

Actively promote UN/CEFACT standards for adoption in industry consortia and user groups

Allow Web services standards as an infrastructure choiceEnhance cooperation with industry consortia such as WS-I

Industry Consortia Adopt development methodology standards (UN/CEFACT CCTS & XML

NDR)

Develop network to share business standards libraries for enhanced reuse

SAP AG 2005, Enterprise Services Standards / C. v. Riegen / 11

Questions?

claus.von.riegen@sap.com