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 Solutions
 Operations 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 domain
Business Domain Model
Supply Chain Operations Model
Organization A
Process Alignment
Information Alignment
Security Infrastructure
Message Infrastructure
Alignment Interface
Business
Processes
Alignment Interface
Business Operations
Model
e-Business
Organization B
Collaboration Model Business Operations
Model
Goal Alignment
Collaboration Alignment Stack
Business
Processes
XMLEUROPE 2002
The elaboration methodology
Stakeholder
Model Activity
Elaborated Into
Management
Goal
alignment
Business commitment
Business agreements and
and collaboration
metrics
specification
Operations
Process
alignment
Business operation and
interaction processes
Business
collaboration
Analysts,
Developers
Information
alignment
Business object state
eBusiness message
Systems Integrator,
Network Admin
Security
infrastructure
Partner authentication
and authorization
Collaboration role
and digital signature
Component interaction
sequence diagrams
eBusiness
implementation
framework
B2B
A2A
Business Focus
Messaging
Application Integrator
infrastructure
protocol specification
XMLEUROPE 2002
The UMM and ebXML
• 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”.
Perspective
ebXML
UN/CEFACT
ebXML
OASIS
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
XMLEUROPE 2002
Alignment with OSI Stack
Application
Transport
Internet Communications Reference Model
Collaboration Layer
Application Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Logical Link Layer
Physical Layer
OSI Layered
Ubiquitous
Communications
Reference Model
Action Layer
Transaction Layer
Service Layer
Agent Layer
Messaging Layer
Transfer Layer
Security 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
Public in this
context means
known to all
parties, not the
at large public
Domain of Alignment
<<Private>>
Enterprise
Business
Model
<<Collaborative>>
Specification
Interface
Value Chain
Business
Model
Public
Process
Definition
Public
Information
Definition
Key
Dependency
Interface
<<Private>>
Enterprise
Business
Model
Specification
Interface
Value Chain
Business
Model
Application
Information
Application
Messaging
Interface
Information
And Process
Exchange Data
Messaging
Interface
Information
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 make
computers understand
business conversations?
Put your business objectives
into the system
Source: eBTWG
XMLEUROPE 2002
Elaboration of Business Objectives
feedback
Expected
Business Results
feedback
Target States of
Business Objects
Partner Metrics
evaluated as
expressed as
feedback
Collaborative
Business Process
Business
Collaboration
Protocol
modeled as
Object-in-state
expressions
aligned using
feedback
eBusiness
Transactions
Semantic
Information
Structures
Message
Exchanges
resulting in
applied to
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
Reference
Instantiation
Reference
Supply Chain Model
Use Cases reified as
Specification
Supply Chain
Specifications
Partnership Model
Partnership
Specification
Specs Realized as
Collaborations reified as
Requirements
Use cases Realized as
Requirements
Implementation
Instantiation
XMLEUROPE 2002
Participants and Standards
Elaborate Supply Chain Reference Model
by: Business Architects
for: Industry Groups / Enterprises
Supply Chain
Model
Partnership
Model
Supply Chain
Specifications
Partnership
Specification
Elaborate Value Net Models
by: Supply Chain Experts
for: Supply Chain Partners
Construct Collaboration Specifications
by: Business Analysts
for: Industry Groups / Enterprises
Instantiate Trading Partner Agreements
by: Business System Architects
for: Supply Chain Partners
XMLEUROPE 2002
Elaboration Example
• Reference
– Supply-Chain.Org reference model (SCOR)
http://www.supply-chain.org
– RosettaNet EConcert Scenario
http://www.rosettanet.org
• Establish New Partnership
• Instantiation
– Partner Model
– Trading Partner Agreement (TPA)
Boundary between reference
and implementation
BDVBRVBTVBSVIFVPMTPA
XMLEUROPE 2002
BDV using SCOR
Business Areas:
•Plan
•Source
•Make
•Deliver
Supply Chain Operations
Plan
Source
Make
Deliver
View Point == The Company
Models Recursive Interaction
•Customer, Customer’s
Customer ….
•Supplier, Supplier’s
Supplier ….
The Company
Customer
Customer's
Customer
Supplier
Supplier's Supplier
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 Make to
Order Product
Source Purchased
Product
Source Engineer to
Order Product
XMLEUROPE 2002
BDV - enable source drill down
Manage Sourcing Business Rules
Assess Supplier Performance
?
The
Company
Maintain Source Data
?
?
Supplier
?
Manage Product Inventory
?
Manage Capital Assets
?
?
?
Manage Incoming Product
Manage Supplier Network
Manage Import Export Requirements
Manage Supplier
Agreements
Manage Supplier Agreements
Supplier's
Supplier
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 Make to
Order Product
Deliver Stocked
Product
Deliver Engineer to
Order Product
XMLEUROPE 2002
BDV – enable deliver drill down
Manage Deliver Business Rules
Manage Deliver
Information
The
Company
Assess Delivery Performance
?
Manage Deliver Information
?
?
Customer
?
Manage Finished Goods Inventories
?
Manage Deliver Capital Assets
?
?
Manage Transportation
Manage Product Life Cycle
Manage Import Export Requirements
Manage Customer Returns
?
Customer's
Customer
XMLEUROPE 2002
BDV – identify collaboration
From: Enable Source
The Company
Create Supplier Agreements
From: Enable Deliver
Create Customer Contract
Information
+Product Provider
+Product Buyer
Manage Supplier
Agreements
The Company
Query Supplier Agreements
Update Supplier Agreementts
Archive Supplier Agreements
Update Customer Contract
Information
Query Customer Contract
Information
Archive Customer Contract
Information
Manage Deliver Information
XMLEUROPE 2002
BDV->BRV – map collaboration to processes
The Company
The Company
+Product Provider
+Product Buyer
Create Supplier Agreements
The Collaboration maps
to leaf node processes
and forms an interaction
between two separate
supply chain operations
models.
Create Customer Contract
Information
Establish New Partnership
XMLEUROPE 2002
BRV – establish new partnership collaboration
Partner A
Partner B
+Product Provider
+Product Buyer
Establish New Partnership
Credit Agency
+Service Provider
Account Set-up Information
Credit Reference Request
Credit Rating
Account Set-up Response
Available Product Information
The BRV Diagram shown here sets the scope for a “fullyelaborated” 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 2002
BTV – business collaboration protocol
START
Note: Sequence based on
EConcert Scenario for
"New Partnership"
Request
Account Setup
[ CREDIT APPROVED ]
Request Credit
Reference
Distribute Product
Information
[ CREDIT DISAPPROVED ]
END
FAIL
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.
XMLEUROPE 2002
BTV – commercial transaction
: Account User
: Account Supplier
START
<<BusinessTransactionActivity>>
Request New Account
[ SUCCESS ]
•Well defined business transaction
semantics
•Business-oriented view
: Account Setup
Acknowledgement
[ FAIL ]
FAILED
Process New
Account Request
Time to Perform
Retry Count
Is Authorization
Required?
Non-Repudiation of
Origin and Content?
Role
Activity
Name
Name
Accoun Request
t User New
Account
Time to Acknowledge
Acceptance
T a b l e 2 -3 : B u s in e s s A c t iv it y P e r f o r ma n c e C o n t r o l s
Acknowledgment
of Receipt
Time to
Acknowledge
: Account
Request
Non-Repudiation
Required?
END
Y
2hr
24hr
24hr
3
Y
Y
XMLEUROPE 2002
BTV – library
•Core component / object
model
•Facilitates semantic
consistency across multiple
business documents
XMLEUROPE 2002
BTV – 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 2002
BSV – 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
BDV
Select processes
Instantiation
Partner Process Model
Mapping
BRV
Elaboration
Partner Collaboration
model
Select collaborations  Constrain implementation
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
BusinessCommitmentPattern
Specifies the reciprocal business
commitments
Uses states to define
success and failure
Uses collaboration to
describe commitment
execution
Uses states to define
transition conditions
BusinessCollaborationPattern
Specifies the orchestration of
business partner actions
Uses process to define
interactions
BusinessEntityTypes
BusinessProcesses
Specifies the computation of named
business states
Specifies the interactions between
business partners
Uses states to define
transaction success and
failure
Source: eBTWG
XMLEUROPE 2002
Commitment Pattern
EconomicCommitment
Specifies the reciprocal
business commitments of
each party
The economic contract is
defined by its contained
commitments
EconomicContract
Represents the agreement
between the parties
The event uses the
commitment to validate
execution conditions
EconomicEvent
EconomicResource
Records the occurrence of
Represents the actual
The
event
references
the
an event specified by the
economic value transferred
resource
exchanged
between
commitment
by the event occurrence
the parties
Source: eBTWG
XMLEUROPE 2002
Specification / Observation
Specification
EconomicEventType
EconomicCommitment
EconomicResourceType
Specifies compliance
conditions for the event
representing the exchange
Specifies conditions
governing the exchange of
economic value
Specifies compliance for the
economic value exchanged
between the parties
Observation
EconomicEvent
EconomicResource
Records the occurrence of
an event specified by the
commitment
Represents the actual
economic value exchanged
by the event occurrence
Source: eBTWG
XMLEUROPE 2002
Collaboration Pattern
BusinessCollaborationPattern
Specifies the business transactions and
business objects which together define
the business elements governed by the
collaboration
BusinessTransaction
Specifies the execution of
exchanges between business
partners
The transaction is defined
by transitions between its
action states
BusinessActionState
BusinessEntityType
Represents the business
artifacts created or
referenced by the
collaboration
The entity lifecycle is
defined by transitions
between its object states
BusinessEntityState
Specifies the conditions under
Specifies the conditions under
which a business entity is
which a business transaction The action state references
the entity state to compute its considered to be in a named
is considered to be in a
current state
state
named state
Source: eBTWG
XMLEUROPE 2002
Business Entity Type
BusinessEntityType
The business entity type is
mapped onto its content
Represents a logical business
entity created or referenced
during a collaboration
Represents the agreement
between the parties
The business entity type
has a set of lifecycles
BusinessEntityLifecycle
Represents the sequence of
states of a business entity
during its existence
BusinessEntityContent
The business entity state
identifies content required
to compute that state
BusinessEntityState
Represents the actual
The business entity lifecycle economic value transferred
by the event occurrence
is a sequence of states
Source: eBTWG
XMLEUROPE 2002
Business Process
Source: eBTWG
XMLEUROPE 2002
Collaboration Functional Decomposition
Business Collaboration Functional Decomposition
Model of business
collaboration pattern
BusinessCollaborationUseCase
Model of high-level
business process
<<includes>>
<<includes>>
BusinessCollaborationUseCase
<<includes>>
BusinessTransactionUseCase
BusinessTransactionUseCase
<<includes>>
BusinessTransactionUseCase
Model of low-level
business process
Source: eBTWG
2002
XMLEUROPE
Collaboration Activity Model
Business Process Activity Model
Start State
BusinessCollaborationTask
Each activity is a use of one
business collaboration usecase
Fork
BusinessEntityType
BusinessEntityType
[State]
[State]
BusinessCollaborationTask
BusinessCollaborationTask
BusinessEntityType
BusinessEntityType
[State]
[State]
Business entity
in state
Join
End State
Source: eBTWG