ebXML Update

1
ebXML Update

• Priscilla Taylor
• Senior Director, International Corporate
  Payments
• NACHA

2
ebXML

• Creating a Single Global Electronic Market

3
ebXML Mission . . .

• To provide an open XML-based infrastructure
  enabling the global use of electronic business
  information in an interoperable, secure and
  consistent manner by all parties.

4
ebXML Value

• Provides the only globally developed open
  XML-based Standard built on a rich heritage of
  electronic business experience
• Creates a Single Global Electronic Market
• Enables all parties irrespective of size to
  engage in Internet-based electronic business
• Provides for plug and play shrink-wrapped
  solutions
• Enables parties to
• complement and extend current EC/EDI investment
• expand electronic business to new and existing
  trading partners
• Facilitates convergence of current and emerging
  XML efforts

5
ebXML delivers the value by

• Using the strengths of OASIS and UN/CEFACT to
  ensure a global open process
• Developing technical specifications for the open
  ebXML infrastructure
• Creating the technical specifications with the
  worlds best experts
• Collaborating with other initiatives and
  standards development organizations
• Building on the experience and strengths of
  existing EDI knowledge
• Enlisting industry leaders to participate and
  adopt ebXML infrastructure
• Realizing the commitment by ebXML participants to
  implement the ebXML technical specifications

6
Organization Structure

• Executive Committee -
• 2 representatives from UN/CEFACT
• Klaus-Dieter Naujok
• Ray Walker
• 2 representatives from Oasis
• Bob Sutor
• Bill Smith
• Steering Committee
• Chairs of each of the Work Groups
• Executive Committee

7
Work Groups

• ebXML Requirements
• Business Process Methodology
• Technical Architecture
• Core Components
• Transport/Routing and Packaging
• Registry and Repository
• Technical Coordination Support
• Marketing, Awareness Education

8
ebXML Requirements

• This presentation will probably involve audience
  discussion, which will create action items. Use
  PowerPoint to keep track of these action items
  during your presentation
• In Slide Show, click on the right mouse button
• Select Meeting Minder
• Select the Action Items tab
• Type in action items as they come up
• Click OK to dismiss this box
• This will automatically create an Action Item
  slide at the end of your presentation with your
  points entered.

9
ebXML Requirement Work Group

• Document and Validate Requirements
• Serve as foundation for developing deliverables
• External Communication
• Benchmark

10
ebXML Requirement Work Group

• Vision
• Deliver a set of technical specifications to
  facilitate global trade.
• Specifications
• Based on W3C specifications
• Provide for interoperability
• Transition path
• Will be submitted as a standard
• Draft specification on web now for comments

11
Business Process Methodology

• This presentation will probably involve audience
  discussion, which will create action items. Use
  PowerPoint to keep track of these action items
  during your presentation
• In Slide Show, click on the right mouse button
• Select Meeting Minder
• Select the Action Items tab
• Type in action items as they come up
• Click OK to dismiss this box
• This will automatically create an Action Item
  slide at the end of your presentation with your
  points entered.

12
Business Process Methodology

• An ebXML-based business process integration
  accomplished by means of a cross-industry global
  standard.
• The vision of ebXML with respect to business
  processes is that organizations be able to
  express their business processes according to a
  specification to insure that they are
  understandable by other organizations thereby
  enabling integration of business processes.

13
Business Process Deliverables

• The Meta-model for Business Process Definition
  -i.e. the common terminology and constructs that
  defines/describes the business semantics (e.g.
  roles, interactions, messages and data)
• Proof of Concept of the mappability between 2
  existing industry frameworks
• Define the format in which an organization
  describes its process AKA meta model.

14
Business Process Deliverables

• Naming Conventions for instances of models and
  their components (e.g. business service requests
  should consist of nouns and verbs cancelPO)
• Develop traceability between the message types
  and business processes. This may include
  recommendations to include sequence diagrams
  related to different instantiations of messages
  types in the repository.

15
Core Components
16
Core Components - Approach

• The world does not need another P.O.!
• Tried Industry Specific approach
• Tried Generic all encompassing approach
• Needed is a new approach to problem
• Context is key (models)
• Utilize rich set of existing body of related work

17
Core Components - Deliverables

• Scope
• Project Plan
• Attributes which specify context
• Methodology for Describing Core Components
• Core Component Content
• Reuse and extension methodology
• Sample recommended for XML EDI instantiation

18
Transportation/Routing Packaging
19
Project overview and scope

• provide an envelope and header for routing of
  message content
• define template sequences for the exchange of
  messages
• provide support for payloads of any type of
  digital data
• adopt security protocols that enable
• non repudiation of sending of messages and
  acknowledgements
• privacy and integrity of communications between
  parties

20
Project overview and scope (cont.)

• authentication of senders of messages
• control over access to services
• support verifiable audit trails
• provide mechanisms for reporting on errors or
  other problems
• develop a messaging protocol for reliable message
  delivery
• define the information required that describes
  how to interact with a service
• develop a default method of usage that enables
  bootstrapping of services

21
Objectives

• enable any party to carry out integrated
  eCommerce transactions with any other party
  anywhere in the world using their hardware and
  software vendor of choice
• persuade a wide variety of vendors to implement
  the approach
• don't reinvent the wheel - re-use where possible
• enable existing "messaging" solutions to "bridge"
  to the ebXML solution
• scalable from SMEs to large companies
• scalable from low power to high end solutions

22
Relationship of Components
TPR
API
Behavior
IntegrationSystem
EnterpriseSystems
MessagingSystem
?
Message Formats
BusinessDocuments
Repository
Internet
Policy Repository
Core Component Library
CoreComponents
BusinessRules
BusinessProcessModelling
MessagingSystem
DocumentChoreography
Registry Repository
23
ebXML Message Structure
Message Structure Information (MIME or XML?)
Message Headers (XML?) - transport routing,
application routing, d-receipts requests,
intermediate status requests, e-messages,
workflow, security, request for special
services, TBD
Business
Message Body (MIME or XML?)
Body Part
Technical
Body Part n
Signature block
Encryption description block
24
Registry and Repository
25
Project Objective

• To define the business and functional
  requirements for an ebXML registry and repository
• XML-based interfaces to interact with the
  registry and repository

26
ebXML Registry and Repository Mission Statement

• The ebXML registry and repository project team
  will deliver requirements and specifications for
  the creation and use of a registry and
  repository. The registry and repository will be
  comprehensive, distributed, business analysis
  driven, and support the runtime and development
  viewpoints of the ebXML architecture.

27
Repository Business Requirements

• Storage of items in their original form
• Support Services
• Query search / retrieval
• Workflow e.g., development of process models
• Quality Assurance ensure consist process models
• Transformation to / from different forms, e.g.,
  XMI
• Repository Interface Discovery capabilities of
  distributed Repositories
• Logging transactional events

28
Repository Business Requirements

• Specific Workflow business requirements
• Best Practices

29
ebXML Architecture Goals

• Providing a view for integration of business
  processes among ad-hoc or established independent
  business partners by electronic means.
• Reducing the need for collaborative business
  partners to have individual and expensive prior
  agreement on how to integrate business processes.
• Providing a high-level business-centric view of
  distributed e-business processes.
• Supporting and representing business processes
  independent of the technical solution.
• Providing and supporting a library of common,
  standard intra-business processes
• Allowing for both business processes and enabling
  technologies to evolve independently while
  retaining long-term investments in both.
• Integrating with new and legacy systems
  throughout the enterprise
• Leveraging existing technologies and standards

30
Enables
Business Process (Meta) Model
Defines
Network Economy
Sends Receives
Market
Structures
Component Library
Business Party
Common Component Library
Common Components
Provides metadata for
Process
Services
Technology Mapping
Provides content for
Schemata
Supports
Codes, Elements
Holds
Provides Access To
Uses
Populates
Common Technical Architecture
Holds
Distributed Repository
Registry
Security
Syntax schema
Transport
31
ebXML Business Architecture

• The business architecture defines how EBXML
  represents business requirements

32
Additional Information

• Anyone can participate in ebXML project and
  participate in any of the work groups.
  Participation can be virtual or in person at the
  meetings.
• web address is ebXML.org
• Next meeting
• May 8-12 in Brussels Belgium

33
Questions??