Oracle, OAGIS and Open Standards October 21-22, 2008. Walldorf, Germany

1. Oracle, OAGIS and Open StandardsOctober 21-22, 2008. Walldorf, Germany Garret Minakawa, Director

2. Agenda • Standards, UN/CEFACT Overview • Strategic Value of CCTS • Oracle Standards Strategy • Oracle Implementation of Standards • Future of Open Standards

3. Interoperability Standards Industry SWIFT, RosettaNet etc Functional HR-XML, GS1-GDSN etc Legacy EDI Core Infrastructure WS-* stack Data UNSPSC, ISO Codes etc Horizontal OAGIS Content Infrastructure CCTS Core Foundation XML, XML Schema • Core Standards • Core Foundation • Mature, owned by W3C • Core InfrastructureStandardsConsolidated over the last few years, driven by middleware and Web Services adoption. Majority owned by OASIS. Core Standards Content Standards • Content Standards • Fragmented with different technology baselines: EDI, DTDs, XML Schema, CCTS 3

4. Content Standards Industry SWIFT, RosettaNet etc Functional HR-XML, GS1-GDSN etc Core Infrastructure WS-* stack Legacy EDI Data UNSPSC, ISO Codes etc Horizontal OAGIS Content Infrastructure CCTS • Content Data Standards • Code lists that are shared, generally • Content Infrastructure Standards • CCTS from UN/CEFACT • Content Horizontal Standards • Common across Industries and Domains. Implements Infrastructure Standards. • Content Domain Standards • Domain specific common across Industries. • OAGIS the only horizontal standard • Extremely fragmented with different technology baselines: EDI, XML DTDs, XML Schema, CCTS • Some consolidation in the recent past mainly around OAGIS specifications • No driver for consolidation until CCTS • Content Vertical Standards • Industry specific standards • Content Legacy Standards • EDI 4

5. Syntax-Specific Business Message XML Naming & Design Rules (NDR) Core Components Message Assembly (CCMA) Standard Business Document Header (SBDH) Business Process Models (BRS/RSM) Unified Modeling Methodology (UMM) UN/CEFACT Standards/Projects Generate Syntax Representation Assemble Business Message Core Component Library (CCL) Core Data Type Catalog (CDT) Model Business Objects, Components Unified Context Methodology (UCM) UML Profile for CCTS (UPCC) Core Components Technical Specification (CCTS) Model Business Process, Information Exchange TMG (Techniques and Methodologies Group) ATG (Applied Technologies Group) TBG (Trade Business Group)

6. Related UN/CEFACT Standards/Projects • Unified Modeling Methodology (UMM) • Modeling language for inter-organizational business processes and the resulting information exchanges. • Business Requirements Specification (BRS) • Template to document business requirements • Requirements Specification Mapping (RSM) • Template to describe data model • UML Profile for Core Components (UPCC) • Mapping of CCTS to UML as a formal UML Profile • Unified Context Methodology (UCM) • Methodology and technical specification for developing, registering, and using context drivers

7. Related UN/CEFACT Standards/Projects • Core Data Type Catalog (CDT) • Catalog and procedures for maintaining UN/CEFACT Core Data Types • Core Components Library (CCL) • Library of harmonized core components • Standard Business Document Header (SBDH) • Defines logical routing and processing requirements • Core Components Message Assembly (CCMA) • Technical specification for syntax-neutral, semantic assembly of business messages based on UMM and CCTS • XML Naming & Design Rules (NDR) • Specification to map CCMA and CCTS-based business information to XML Schema

8. Strategic Value of CCTS

9. Strategic Value of CCTSUN/CEFACT Standard • United Nations “Brand” • Recognized by many governments • “De Jure” Standard • Member of MoU/MG • Politically Neutral • Less conflict across SDOs • Open IPR

10. Strategic Value of CCTSSDO / Solution Provider Adoption UN/CEFACT UNIFI (ISO 20022)

11. Strategic Value of CCTSConvergence Opportunities • Open Applications Group, Inc. (OAGi) • HR-XML 3.0 based on OAGIS • AIAG/JADM based on OAGIS • STAR based on OAGIS • High Tech Council • UN/CEFACT NDR 3.0 Harmonization • OAGi participation • ACORD participation • UBL participation

12. Strategic Value of CCTSInteroperability (Levels Of) Core Component Library (CCL) Common Content XML Naming & Design Rules (NDR) Common XML Naming and Design Rules Common Message Architecture Core Components Message Assembly (CCMA) Standard Business Document Header (SBDH) Common Data Types Common Data Modeling Methodology Core Data Type Catalog (CDT) Core Components Technical Specification (CCTS)

13. Oracle Standards Strategy

14. Guiding Principles • Core and Infrastructure Standards are stable • Content Standards like the Wild West • Numerous Standards • Approximately 400 different content standards generally overlapping content defined differently • Oracle involved in more than a hundred different content standards • A “Standard for standards” is needed

15. Guiding Principles • Define a platform for a “Standard for standards”: • Content Infrastructure Standard (CCTS) as a basis for a common understanding of type, naming, and rules. • Horizontal Standard (OAGIS) as a common platform for implementing the Content Infrastructure Standard and driving convergence • Implement the “Standard for standards” platform for EBO architecture • Standardize the platform through a global standard organization • Drive the adoption of “Standard for standards” platform across content standard organizations

16. Content Standards LeadershipStandardize the platform • Innovation and Adoption of Content Infrastructure Standards • Core Components from UNCEFACT • Core Component Technical Specification (CCTS) • Active member • Naming and Design Rules (NDR) • Lead editor • Harmonize Oracle’s, OAGi’s, UBL, GS1, ACORD, AIAG, and STAR NDR. • Unified Context Methodology (UCM) • Project leader • Core Components Management Assembly (CCMA) • Active member

17. Content Standards LeadershipStandardize the platform • Open Applications Group Integration Specification (OAGIS) is a platform for using Core Components that vertical standards can leverage from OAGi • Participation in OAGi • Chair of OAGi Board Members • Set the convergence direction of OAGi and OAGIS • Chief Architect • Leader of the Architecture Council • Visibility to all work groups • Lead development of OAGIS • Review and approve all content for each release

18. Content Standards LeadershipDrive the adoption of “Standard for standards” • Horizontal content workgroups participations • Vertical standards participations using the “Standard for standards” platform • OAGI High Tech Council – Active Member – Provide requirements • Automotive • AIAG • STAR • Joint Automotive including AIAG, STAR, JAMA, JAPIA, Odette • HR-XML • CIDX • ARTS • Steel Industry

19. Oracle Implementation of Standards

20. Application Integration ArchitectureAbstraction Layer Concept Optimize Offer Forecast Demand Capture Order Pick, Pack, Ship Deduction & Settlement Billing Siebel CRM E-Business Suite Enterprise Service Bus Customer Sales Order Invoice… BPEL Process Manager AIA Enterprise Business Objects & Services Layer Data Integration SAP Custom App Composite UI Application Business Connector Service JMS or WSIF API or Web Service API or Web Service • Common Objects, Standardized Business Services • Re-Usable , Loosely Coupled Services to support one to many • Leverage AIA UI Service SDK to build Composite Tasks

21. Predefined, Reusable ServicesBuild Any-to-Any Applications Integrations Out of the box, library of reusable business services for cross application process automation Common semantics foundation to easily build, change and optimize business processes Building blocksand methodology to build your Enterprise Business Services Create Order Update Order Get Balance Query Products Utility Services… Benefits • Faster time to value • Overcome SOA adoption challenges • Lower cost of ownership Prebuilt Reusable Services

22. Common Object definition of business concepts such as a customer, a sales order, a payment etc Defined using inputs from multiple applications and content standards Enterprise Business ObjectWhat is an EBO… Other Data Integration XML A2A/B2B EBS / Web Services EDI • Precise definition of each business component and attribute by adoption of standards for both content as well as naming and design • Designed for extensibility EBO Logical Data Model Physical Data Model

23. Why EBO …Standardized Service definitions across applications • Create standard service definitions that are implemented by all Oracle applications • A single service supporting multiple operations – e.g. SalesOrder Service may support Create, Cancel, Update Operations • Each operation will use EBOs as standard input and/or output • Multiple applications may provide the same service e.g. e-Business Suite (EBS), Siebel, Enterprise and E1 can support Create Sales Order • Objective is to be able to switch the service provider without affecting the service e.g. switch from EBS or E1 to Fusion (or any other partner applications that provide the same service

24. Why EBO …Standardized Service payloads across applications • Standard Services require standard payloads to be truly application independent • EBOs are standardized representations of business objects that will serve as the payload (input or output) for standard services • EBOs are based on standards published by international standards organizations • UN/CEFACT Core Components Technical Specification (CCTS) • Open Applications Group Integration Specification (OAGIS)

25. Future of Open Standards

26. Future of Open StandardsCurrent State UN/CEFACT CCTS Adoption Canonical Data Model Merging of A2A and B2B Increasing cross-industry collaboration requirements Increasing pressure on standards development organizations

27. Future of Open StandardsEmerging Trends SOA Implementation / SOA Governance Business Process integration Standards Development Organization consolidation Semantics / Ontologies

28. Future of Open StandardsKey Initiatives UN/CEFACT framework completion/maturity Universal Context Methodology Core Components Message Assembly OAGi Industry Council model for convergence and collaboration

30. 30