Enterprise
Services
Standards
Claus von Riegen
Director Web Services Standards, SAP AG
7th UN/CEFACT Forum
Lyon, France
UN/CEFACT
Enterprise Services Architecture
Enterprise Services
Architecture (ESA)
- is SAP’s blueprint
Composite Applications
SAP
SAP
3rd Party
- for a business process-driven
approach
- to more productivity, flexibility and
competitive advantage
Enterprise
Services
Repository
- using a service oriented infrastructure.
SAP NetWeaver
SAP NetWeaver
- is the technology platform
Legacy
System
3rd
Party
SAP
- that enables ESA
- to drive innovation and enable
business change.
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
Enterprise Services (Platform View)
Enterprise Standards
 Reliability, scalability, performance,
security
Composite Applications
SAP
SAP
3rd Party
 Driven by business and legal
requirements
 Mostly user-specific
 Examples: throughput of 100.000
invoices per hour, Section 508
accessibility
Web Services Standards
Enterprise
Services
Repository
SAP NetWeaver
Legacy
System
3rd
Party
SAP
 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, WSSecurity, WS-ReliableMessaging
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
Take The Business Perspective
SOA IS REQUIRED BUT NOT ENOUGH
Common Business Semantics are required
+
SOA
ES
ESA
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
Enterprise Services (Business Application View)
Business Standards
Composite Applications
SAP
SAP
3rd Party
 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.)
Enterprise
Services
Repository
SAP NetWeaver
Legacy
System
3rd
Party
SAP
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
The Business Standards Dilemma
Higher Education
& Research
Healthcare
Financial
Service Provider
High
Tech
Telco
Chemicals
Automotive
Mill Products
Engineering &
Construction
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
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
Mining
Pharma
Oil & Gas
Insurance
Media
Aerospace
& Defense
Banking
Retail
Consumer
Products
Introducing Standards for Standards
Development Methodology
Standards
 Modeling and design rules
Composite Applications
SAP
SAP
3rd Party
 Driven by development and
integration efficiency and quality needs
 Covered by OMG, UN/CEFACT
 Examples: UML, XMI, CCTS, XML
NDR
Enterprise
Services
Repository
SAP NetWeaver
Legacy
System
3rd
Party
SAP
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
 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
Platform Ecosystem
Collective Innovation
- Customers, Partners, ISVs & SAP
- Develop and prioritize Enterprise
Service Definitions
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
Based on Open Standards
- Interoperability: Web Services
- Methodology: CCTS, etc.
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 needed
 Common
methodology needs to be applied
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›
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 choice
 Enhance
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 / ‹#›
Questions?
claus.von.riegen@sap.com
 SAP AG 2005, Enterprise Services Standards / C. v. Riegen / ‹#›