XMLEUROPE 2002

ebXML and the e-Business Protocol Stack

John Yunker

Chief Architect

Collaborative Domain

XMLEUROPE 2002

Business Vision

• Align, implement, optimize, and evolve value chain partnerships

XMLEUROPE 2002

Keys to the Vision

Requirements

• Alignment of business goals and objectives

• Alignment of business processes and procedures

• Alignment of business objects and information

• Alignment of technology

• Partner, model, and service discovery

Standards SolutionsOperations reference models

and commitment / collaboration patterns

Partner process protocols ebXML, RosettaNet, OAG

XML and EDI messaging standards

Internet Implementation frameworks

Registries with partner, process and service descriptions

XMLEUROPE 2002

The alignment domainBusiness Domain Model

Organization ABusiness Operations

Model

Organization BBusiness Operations

Model

Supply Chain Operations Model

e-Business Collaboration Model

Process Alignment

Information Alignment

Goal Alignment

Security Infrastructure

Message Infrastructure

Business Processes

Business Processes

Alig

nm

ent In

terface

Alig

nm

ent In

terface

Collaboration Alignment Stack

XMLEUROPE 2002

Stakeholder Business Focus Model Activity Elaborated Into

ManagementGoal alignment

Business agreements and metrics

Business commitment and collaboration specification

OperationsProcess alignment

Business operation and interaction processes

Business collaborationprotocol specification

Analysts, Developers

Information alignment

Business object state eBusiness message

Systems Integrator,

Network AdminSecurity infrastructure

Partner authentication and authorization

Collaboration role and digital signature

Application IntegratorMessaging infrastructure

Component interaction sequence diagrams

eBusiness implementation framework

B2B

A2A

The elaboration methodology

XMLEUROPE 2002

Perspective UMM View

Business Operations Requirements Business Domain View (BDV)

Business Collaboration Requirements

Business Requirements View (BRV)

Commercial Transaction Protocol and Business Collaboration Protocol

Business Transaction View (BTV)

Functional Service Protocol Business Service View (BSV)

Network Implementation Protocol Implementation Framework View (IFV)

Requirements

Specification

• United Nations Center for Electronic Facilitation of Administration of Commerce and Trade (UN/CEFACT) has developed the UMM which is both:

• a business modeling methodology• a meta-framework for organizing business/technology dependencies • an extension of UML

• ebXML uses the UMM as it’s modeling foundation • UMM structures modeling into layers of “views”.

ebXML

UN/CEFACT

ebXML OASIS

The UMM and ebXML

XMLEUROPE 2002

Alignment with OSI Stack

Network Layer

Logical Link Layer

Physical Layer

Application Layer

Session Layer

Transport Layer

OSI LayeredUbiquitous Communications Reference Model

Action Layer

Transfer Layer

Agent Layer

Transaction Layer

Security Layer

Messaging Layer

Service Layer

Presentation Layer

Tra

ns

po

rtA

pp

lic

ati

on

Inte

rne

t C

om

mu

nic

ati

on

s R

efe

ren

ce

Mo

de

lCollaboration Layer

XMLEUROPE 2002

The Role of Specifications

• Alignment of expectations

• Communication of semantic

• Communication of syntax

• Basis for iterative evolution

• Basis for conflict resolution

• Requirements for adjacent stack layers

XMLEUROPE 2002

Domain of Alignment

<<Private>><<Collaborative>><<Private>>

PublicInformationDefinition

PublicProcess

Definition

InformationAnd Process

Exchange DataInformation

Application

EnterpriseBusiness

Model

Value ChainBusiness

Model

Information

Application

EnterpriseBusiness

Model

Value ChainBusiness

Model

Messaging Interface

Messaging Interface

Specification Interface

Specification Interface

DependencyInterface

Key

Public in this context means known to all parties, not the at large public

Public in this context means known to all parties, not the at large public

Source: eBTWG

XMLEUROPE 2002

Principles

• Business requirements drive technology solutions

• Embody best practices in collaborative ebusiness standards

• Focus on expected business results

Source: eBTWG

XMLEUROPE 2002

How to makecomputers understand

business conversations?

Put your business objectives into the system

Source: eBTWG

XMLEUROPE 2002

Elaboration of Business Objectives

Target States of Business Objects

Expected Business Results

Business Collaboration

Protocol

Collaborative Business Process

Partner Metrics

evaluated as expressed as

Object-in-state expressions

aligned usingmodeled as

Message Exchanges

eBusiness Transactions

Semantic Information Structures

applied toresulting in

feedback

feedback

feedback

feedback

XMLEUROPE 2002

Business Collaboration Model

A prescription of the business and network protocols between independent business processes that permit the legally enforceable formation of commercial contracts between independent entities

Business Process Model

XMLEUROPE 2002

Not a Business Process Model

It describes a particular set of interactions between two or more business process models provided by independent business entities that collaborate to reach common or complementary goals.

XMLEUROPE 2002

Elaboration Methodology

Supply Chain Model Partnership Model

Supply ChainSpecifications

PartnershipSpecification

Reference Instantiation

Requirements

Implementation

Use cases Realized as

Specs Realized as

Col

labo

ratio

ns re

ified

as

Use

Cas

es re

ified

as

Reference InstantiationR

equir

em

ents

Speci

fica

tion

XMLEUROPE 2002

Participants and Standards

PartnershipModel

Supply ChainSpecifications

PartnershipSpecification

Supply ChainModel

Elaborate Supply Chain Reference Modelby: Business Architectsfor: Industry Groups / Enterprises

Construct Collaboration Specificationsby: Business Analystsfor: Industry Groups / Enterprises

Elaborate Value Net Modelsby: Supply Chain Expertsfor: Supply Chain Partners

Instantiate Trading Partner Agreementsby: Business System Architectsfor: Supply Chain Partners

XMLEUROPE 2002

Elaboration Example

• Reference– Supply-Chain.Org reference model (SCOR)

http://www.supply-chain.org

– RosettaNet EConcert Scenariohttp://www.rosettanet.org

• Establish New Partnership

• Instantiation– Partner Model

– Trading Partner Agreement (TPA)

BDVBRVBTVBSVIFVPMTPA

Boundary between reference and implementation

XMLEUROPE 2002 BDV using SCOR

Business Areas:•Plan•Source•Make•Deliver

View Point == The Company

Models Recursive Interaction•Customer, Customer’s

Customer ….•Supplier, Supplier’s

Supplier ….

Supply Chain Operations

DeliverMake

Plan Source

Customer

Customer's Customer

Supplier

The Company

Supplier's Supplier

•Source

•Deliver

XMLEUROPE 2002

BDV - source drill down

Process Areas:•Enable Source•Source Purchased

Product•Source Make to

Order Product•Source Engineer to

Order Product

Source

Enable Source

Source Engineer to Order Product

Source Make to Order Product

Source Purchased Product

•Enable Source

XMLEUROPE 2002

Manage Supplier Agreements

Manage Sourcing Business Rules

Assess Supplier Performance

Maintain Source Data

Manage Product Inventory

Manage Capital Assets

Manage Incoming Product

Manage Supplier Network

Manage Import Export Requirements

Manage Supplier Agreements

?

?

BDV - enable source drill down

?

?

?

?

?

?

Supplier's Supplier

SupplierThe

Company

XMLEUROPE 2002

BDV - deliver drill down

Process Areas:•Enable Deliver•Deliver Stocked

Product•Deliver Make to

Order Product•Deliver Engineer to

Order Product

Deliver

Enable Deliver Deliver Stocked Product

Deliver Make to Order Product

Deliver Engineer to Order Product

•Enable Deliver

XMLEUROPE 2002

Manage Deliver Information

BDV – enable deliver drill down

?

?

Manage Deliver Business Rules

Assess Delivery Performance

Manage Deliver Information

Manage Finished Goods Inventories

Manage Deliver Capital Assets

Manage Transportation

Manage Product Life Cycle

Manage Import Export Requirements

Manage Customer Returns

??

?

?

?

?

Customer's Customer

CustomerThe

Company

XMLEUROPE 2002BDV – identify collaboration

Create Supplier Agreements

Query Supplier Agreements

Archive Supplier Agreements

Update Supplier Agreementts

Manage Supplier Agreements

+Product Buyer

The Company The CompanyCreate Customer Contract

Information

Update Customer ContractInformation

Query Customer ContractInformation

Manage Deliver Information

Archive Customer ContractInformation

+Product Provider

From: Enable Source From: Enable Deliver

XMLEUROPE 2002

BDV->BRV – map collaboration to processes

Create Supplier Agreements

+Product Buyer

The Company

Create Customer ContractInformation

The Company

+Product Provider

Establish New Partnership

The Collaboration maps to leaf node processes and forms an interaction between two separate supply chain operations models.

XMLEUROPE 2002

BRV – establish new partnership collaboration

+Product Buyer

Partner A Partner B

+Product Provider

Establish New Partnership

Credit Agency+Service Provider

Account Set-up InformationCredit Reference RequestCredit RatingAccount Set-up ResponseAvailable Product Information

The BRV Diagram shown here sets the scope for a “fully-elaborated” use case description. The use case definition (a.k.a. steps or events) are then detailed in an activity diagram as the top level of the BTV.

XMLEUROPE 2002BTV – business collaboration protocol

The Diagram shown here connects the set of transactions which together define a Business Collaboration Protocol at the Business Transaction View (BTV) level. This diagram represents the top level of the BTV. Each transaction is then decomposed according to its appropriate pattern.

START

Request Account Setup

Request Credit Reference

Note: Sequence based on EConcert Scenario for "New Partnership"

Distribute Product Information

[ CREDIT APPROVED ]

FAIL

[ CREDIT DISAPPROVED ]

END

XMLEUROPE 2002

Tabl e 2-3: Business Ac t ivit y Per f or manc e C ont r ol s Acknowledgment

of Receipt

Role Name

Activity Name N

on-R

epud

iatio

n Req

uire

d?

Tim

e to

Ack

now

ledg

e

Tim

e to

Ack

now

ledg

e Acc

epta

nce

Tim

e to

Per

form

Ret

ry C

ount

Is A

utho

riza

tion

Req

uire

d?

Non

-Rep

udiatio

n of

O

rigin

and

Con

tent

?

Account User

Request New Account

Y 2hr 24hr 24hr 3 Y Y

BTV – commercial transaction

: Account SetupAcknowledgement

START

Request New Account<<BusinessTransactionActivity>>

END FAILED

: AccountRequest

Process NewAccount Request

[ SUCCESS ] [ FAIL ]

: Account Supplier : Account User

•Well defined business transaction semantics•Business-oriented view

XMLEUROPE 2002

BTV – library

•Core component / object model•Facilitates semantic consistency across multiple business documents

XMLEUROPE 2002BTV – business document

Contextually constrained business document composition •Include attributes of an entity only where appropriate•Content validation based on usage context

XMLEUROPE 2002

BSV – service-to-service

: Account User Service

: Account Supplier Service

1. request(:AccountRequestAction)

1.1. signal(:ReceiptAcknowledgment)

2. response(:AccountSetupAcknowledgmentAction)

2.1. signal(:ReceiptAcknowledgment)

•Well defined business service semantics•Transaction state transitions are pattern based•Technically oriented view

XMLEUROPE 2002BSV – message guideline

•Business document structure•Data definition e.g. min,max, lexical representation, data type•Validation constraints•Consistent entity structure

XMLEUROPE 2002

Partner model

Reference Instantiation

BDV Partner Process Model

BRV Partner Collaboration model

Select processes

Select collaborations Constrain implementation

Mapping

Elaboration

XMLEUROPE 2002

Summary

• Elaboration of business expectations into eBusiness Technical Specifications

• Map business success onto eBusiness partnership implementations

• Keep your partnership implementations in lockstep with your logical business model as you evolve and extend your business goals

XMLEUROPE 2002

Legal Stuff

Elements of this presentation are copyrighted materials of UN/CEFACT, eBTWG, OASIS, and ebXML. These materials should not be used without acknowledgement of their source and permission of the copyright holder.

XMLEUROPE 2002

Thank you!

john.yunker@collaborativedomain.com

Reference Material at:

www.collaborativedomain.com/standards

XMLEUROPE 2002

Slides for browsing…

At your leisure

XMLEUROPE 2002

Commitments and Collaborations

BusinessEntityTypesSpecifies the computation of named

business states

BusinessProcessesSpecifies the interactions between

business partners

BusinessCommitmentPatternSpecifies the reciprocal business

commitments

BusinessCollaborationPatternSpecifies the orchestration of

business partner actions

Uses states to define success and failure

Uses process to define interactions

Uses states to define transition conditions

Uses states to define transaction success and

failure

Uses collaboration to describe commitment

execution

Source: eBTWG

XMLEUROPE 2002

Commitment Pattern

EconomicEventRecords the occurrence of an event specified by the

commitment

EconomicCommitmentSpecifies the reciprocal

business commitments of each party

The event uses the commitment to validate

execution conditions

EconomicContractRepresents the agreement

between the parties

EconomicResourceRepresents the actual

economic value transferred by the event occurrence

The economic contract is defined by its contained

commitments

The event references the resource exchanged between

the parties

Source: eBTWG

XMLEUROPE 2002

Specification / Observation

Specification

EconomicEventTypeSpecifies compliance

conditions for the event representing the exchange

EconomicCommitmentSpecifies conditions

governing the exchange of economic value

EconomicResourceTypeSpecifies compliance for the economic value exchanged

between the parties

ObservationEconomicEvent

Records the occurrence of an event specified by the

commitment

EconomicResourceRepresents the actual

economic value exchanged by the event occurrence

Source: eBTWG

XMLEUROPE 2002

Collaboration Pattern

BusinessEntityStateSpecifies the conditions under

which a business entity is considered to be in a named

state

BusinessTransactionSpecifies the execution of

exchanges between business partners

The transaction is defined by transitions between its

action states

BusinessEntityTypeRepresents the business

artifacts created or referenced by the

collaboration

BusinessActionStateSpecifies the conditions under which a business transaction

is considered to be in a named state

The action state references the entity state to compute its

current state

The entity lifecycle is defined by transitions

between its object states

BusinessCollaborationPatternSpecifies the business transactions and business objects which together define the business elements governed by the

collaboration

Source: eBTWG

XMLEUROPE 2002

Business Entity Type

Source: eBTWG

BusinessEntityLifecycleRepresents the sequence of states of a business entity

during its existence

BusinessEntityTypeRepresents a logical business entity created or referenced

during a collaboration

The business entity type has a set of lifecycles

BusinessEntityContentRepresents the agreement

between the parties

BusinessEntityStateRepresents the actual

economic value transferred by the event occurrence

The business entity type is mapped onto its content

The business entity lifecycle is a sequence of states

The business entity state identifies content

required to compute that state

XMLEUROPE 2002

Business Process

BusinessCollaboration UseCase

Specifies functional decomposition of process

BusinessProcess Specifies the actions of, and

interactions between partners

The business collaboration usecase identifies

functionality requirements

BusinessProcessActivityModel

Specifies the sequencing and dependencies of transactions

BusinessTransaction Specifies the execution of

exchanges between business partners

The process execution is specified by the business process activity model

A business transaction executes a business

collaboration usecase

The business object state identifies content required

to compute that state

Source: eBTWG

XMLEUROPE 2002

Collaboration Functional Decomposition Business Collaboration Functional Decomposition

BusinessCollaborationUseCase

BusinessTransactionUseCase BusinessCollaborationUseCase

BusinessTransactionUseCase BusinessTransactionUseCase

<<includes>> <<includes>>

<<includes>> <<includes>>

Model of business collaboration pattern

Model of high-level business process

Model of low-level business process

Source: eBTWG

XMLEUROPE 2002

Business Process Activity ModelStart State

BusinessCollaborationTaskBusinessCollaborationTask

BusinessCollaborationTask

BusinessEntityType

[State]

BusinessEntityType

[State]

BusinessEntityType

[State]

BusinessEntityType

[State]

End State

Join

ForkEach activity is a use of one business collaboration usecase

Business entity in state

Collaboration Activity Model

Source: eBTWG