Introducing an ebXML Implementation Methodology

1
Introducing an ebXML Implementation Methodology
From Chapter11, ebXML Concepts and Application,
by Brian Gibb and Suresh Damodaran, Wiley, 2003

• ? ? ?
• ???? ?????
• Email chingyeh_at_cse.ttu.edu.tw
• URL http//www.cse.ttu.edu.tw/chingyeh

2
Introduction

• We present a sample purchase order scenario to
  demonstrate the use of ebXML BPSS, CPPA, and
  Registry specifications.

3
The Purchase Use Case

• International purchase use case, adapted from a
  CEFACT model of international supply chain
• Identify a partner
• Negotiate a contract
• Order goods
• Ship the goods
• Make payment
• The goal of ebXML framework is to create
  e-business solutions that automate the above
  steps.

4
Observations on the use case

• The following observations help to identify
• what you can automate and
• How to do so.
• Observation 1 Common business processes exist
• Identify a partner (Step 1 of use case)
• Negotiate and create a contract (Step 2 of use
  case)
• Place order based on contract (Step 3 of use
  case)
• Ship merchandise (Step 4 of use case)
• Pay for merchandise (Step 5 of use case)
• Archive trade records for auditing by authorities
  and to settle nonrepudiation of claims by
  collaboration partners.

5
Observations on the use case

• Observation 2
• Standardized yet customizable business documents
  in multiple formats are required
• Request for Invoice (RFI), RFQ, Order
• ASC X12, EDIFACT, OAGIS Business Object Document
  (BOD)
• Observation 3
• Standardized description of collaboration steps
  is required

6
Public and private processes
BSIBusiness Service Interface
7
Observations on the use case

• Observation 4
• Standardized description of each partnerss
  profile and the contract between partners are
  required
• Observation 5
• Support for intermediaries is required
• Observation 6
• Support for verification of authority constraints
  is required
• Observation 7
• Standardized protocols for discovery are
  essential
• Observation 8
• Security is paramount

8
The Move Toward Automation

• Each of the steps can benefit from automation.
• Step 3 is of higher priority to business than
  others steps
• Assumption is therefore made to the automation of
  Step 3.

Business contracts that set the business terms of
the trade between the customer and supplier, as
well as with any intermediaries already exist
9
Performing the automation
10
The ebXML Framework at Work

• A hypothetical scenario
• One customer, a retail chain store in the United
  States, does business transaction with one
  supplier, who is selling orchids in India
• Assumptions
• The supplier has been already identified by the
  customer, and a business contract is already in
  place between the partner regarding the economic
  and legal aspect of the deal.
• The supplier and customer are already aware of
  the ebXML Registry where the business-process for
  ordering, shipping, and payment are store.
• The supplier and customer are notified of
  references to the relevant business-process
  specifications and profiles in the registry
  through the exchanged RFQ, RFI, or other means

11
The ebXML Framework at Work

• The transaction process is outlined in the
  following steps
• The supplier queries the ebXML registry for the
  orchid purchase, orchid ship, and orchid payment
  process specifications that exist in the
  registry. The process specification contains
  business collaboration specified using the ebXML
  BPSS.
• The supplier implements services and actions
  required to support the business collaborations.
  The supplier may implement new BSIs to facilitate
  invocation of the services and actions. The
  services for the role of supplier may be Purchase
  Service, and actions of this service may be
  Receive new purchase order, Send Confirmation or
  Query Status.

12
The ebXML Framework at Work

• The supplier creates a profile of the services
  implemented. To define the profile, the supplier
  uses the ebXML CPP schema. The suppliers schema
  is then registered and stored in the registry.The
  registry implements the model and interfaces
  specified in ebXML Registry.
• The customer looks into ebXML Registry and finds
  the CPPs of the supplier and any intermediary.

13
The ebXML Framework at Work

• The customer starts a negotiation with the
  supplier for finalizing the technical contract
  for flowers.
• This step matches the supplier and customer CPPs,
  as published in the ebXML Registry. The contract
  covers only technical details required to send
  and receive interoperable, secure, and reliable
  message between the customer and supplier to
  allow invocation of services and actions the
  supplier and customer implement. These details
  are embodied in a CPA.
• If intermediaries are involved, the negotiation
  is also carried out with each intermediary, by
  customer and supplier, and appropriate CPAs are
  created.

14
The ebXML Framework at Work

• Both customer and supplier modify existing BSIs
  or create new BSIs to satisfy the newly created
  CPA, if necessary.
• The Purchase service is executed using the BSI at
  each partner.
• For shipping and payment of the money, similar
  BSIs are created at each partner involved, and
  appropriate business processes are carried
  between the customer and supplier through
  intermediaries.
• The supplier uses a shipping intermediary to ship
  the orchids to the customer, and the customer
  makes the payment for the orchids through an
  intermediary, such as an international trade
  bank.

15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)