<Insert Picture Here>
Standards and Competitive AdvantageGlobal StandardizationOctober 23, 2008. Houston, TX
Michael Rowell, Oracle, Applications Standards Strategy Manager
Open Applications Group, Chief Architect
3rd Annual Energistics Standards Summit and Reception
Theme: Strategic Standardization Management
Agenda
• Standards, UN/CEFACT Overview
• Strategic Value of CCTS
• Oracle Standards Strategy
• Oracle Implementation of Standards
• Future of Open Standards
Interoperability Standards
Core StandardsCore Standards Content StandardsContent Standards
• Core Standards• Core Foundation
Mature, owned by W3C
• Core Infrastructure StandardsConsolidated over the last few years, driven by middleware and Web Services adoption. Majority owned by OASIS.
3
Core FoundationXML, XML Schema
Core Infrastructure
WS-* stack
Content InfrastructureCCTS
HorizontalOAGIS
DataUNSPSC, ISO Codes etc
FunctionalHR-XML, GS1-
GDSN etc
IndustrySWIFT,
RosettaNet etc
LegacyEDI
• Content StandardsFragmented with different technology baselines: EDI, DTDs, XML Schema, CCTS
Content Standards
4
• Content Data StandardsCode lists that are shared, generally
• Content Infrastructure StandardsCCTS from UN/CEFACT
• Content Horizontal StandardsCommon across Industries and Domains.
Implements Infrastructure Standards.
• Content Domain StandardsDomain specific common across Industries.
• Content Vertical StandardsIndustry specific standards
• Content Legacy StandardsEDI
Core Infrastructure
WS-* stack
Content InfrastructureCCTS
HorizontalOAGIS
DataUNSPSC, ISO Codes etc
FunctionalHR-XML, GS1-
GDSN etc
IndustrySWIFT,
RosettaNet etc
LegacyEDI
• 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
Core Component Library (CCL)
UN/CEFACT Standards/Projects
Core Components Technical Specification (CCTS)
TMG (Techniques and Methodologies Group)TBG (Trade Business Group)ATG (Applied Technologies Group)
Business Process Models (BRS/RSM)
Unified Modeling Methodology (UMM)
UML Profile for CCTS (UPCC)
Unified Context Methodology (UCM)
Syntax-Specific Business Message
Core Components Message Assembly (CCMA)
Standard Business Document Header (SBDH)
XML Naming & Design Rules (NDR)
Model Business Process, Information Exchange
Model Business Objects, Components
Generate Syntax Representation
Assemble Business Message
Core Data Type Catalog (CDT)
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
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
Strategic Value of CCTS
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
Strategic Value of CCTSSDO / Solution Provider Adoption
UN/CEFACT
UNIFI (ISO 20022)
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
Strategic Value of CCTSInteroperability (Levels Of)
Core Component Library (CCL)
Core Components Technical Specification (CCTS)
Core Components Message Assembly (CCMA)
Standard Business Document Header (SBDH)
XML Naming & Design Rules (NDR)
Core Data Type Catalog (CDT) Common Data Types
Common Data Modeling Methodology
Common XML Naming and Design Rules
Common Message Architecture
Common Content
Oracle Standards Strategy
Guiding Principles
Core and Infrastructure Standards are stable Content Standards like the Wild West
o Numerous StandardsApproximately 400 different content standards generally
overlapping content defined differentlyOracle involved in more than a hundred different content
standards
A “Standard for standards” is needed
Guiding Principles
Define a platform for a “Standard for standards”:o Content Infrastructure Standard (CCTS) as a basis for a common
understanding of type, naming, and rules.o 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
Content Standards LeadershipStandardize the platform
Innovation and Adoption of Content Infrastructure Standards o 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.o Unified Context Methodology (UCM)
Project leadero Core Components Management Assembly (CCMA)
Active member
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 OAGio Chair of OAGi Board Members
Set the convergence direction of OAGi and OAGISo Chief Architect
Leader of the Architecture CouncilVisibility to all work groupsLead development of OAGISReview and approve all content for each release
Content Standards LeadershipDrive the adoption of “Standard for standards”
Horizontal content workgroups participations Vertical standards participations using the “Standard for
standards” platformo OAGI High Tech Council – Active Member – Provide requirementso Automotive
AIAG STAR Joint Automotive including AIAG, STAR, JAMA, JAPIA, Odette
o HR-XMLo CIDXo ARTSo Steel Industry
Oracle Implementation of Standards
BPEL Process Manager
Enterprise Service Bus
Data Integration
Application Integration ArchitectureAbstraction Layer Concept
AIA Enterprise Business Objects & Services Layer
Customer Sales Order Invoice…
Optimize Offer
Forecast Demand
Capture Order
Pick, Pack, Ship
Billing Deduction &
Settlement
Siebel CRM
E-Business Suite
SAP Custom App
Composite UI
Application Business Connector Service
API or Web Service
JMS or WSIF
API or Web Service
Common Objects, Standardized Business ServicesRe-Usable , Loosely Coupled Services to support one to manyLeverage AIA UI Service SDK to build Composite Tasks
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 blocks and methodology to build your Enterprise Business Services
Prebuilt Reusable Services
Create Order Update Order Get Balance Query Products Utility Services…
Benefits
• Faster time to value
• Overcome SOA adoption challenges
• Lower cost of ownership
• 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
• Precise definition of each business component and attribute by adoption of standards for both content as well as naming and design
• Designed for extensibility Physical Data Model
Logical Data Model
EDIEBS / WebServices
XMLA2A/B2B
Other DataIntegration
EBO
Enterprise Business ObjectWhat is an EBO…
• 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
Why EBO …Standardized Service definitions 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)
Why EBO …Standardized Service payloads across applications
Future of Open Standards
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
Future of Open StandardsEmerging Trends
• SOA Implementation / SOA Governance
• Business Process integration
• Standards Development Organization consolidation
• Semantics / Ontologies
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
Top Related