KTH-DSV meeting, 2002.11.14 Copyright WebGiro AB, 2002. All rights reserved. ECIMF Business Context...
-
Upload
madison-watkins -
Category
Documents
-
view
217 -
download
0
description
Transcript of KTH-DSV meeting, 2002.11.14 Copyright WebGiro AB, 2002. All rights reserved. ECIMF Business Context...
KTH-DSV meeting, 2002.11.14
Copyright WebGiro AB, 2002. All rights reserved.
ECIMF Business ContextInteroperability
Andrzej BialeckiAndrzej BialeckiECIMF Project ChairECIMF Project Chair
Copyright WebGiro AB, 2002. All rights reserved. 2
Interoperability challenge
Different business culturesDifferent business cultures Different industry sectors, geographical regions, laws, user Different industry sectors, geographical regions, laws, user
communities, corporate cultures, etc…communities, corporate cultures, etc… Different technical frameworksDifferent technical frameworks
Different business processes, e-commerce standards, Different business processes, e-commerce standards, implementations, integration to back-office systems, etc…implementations, integration to back-office systems, etc…
Standards help, sure – there are just too many of them… Standards help, sure – there are just too many of them… Fragmented standards help only small user groups, creating large Fragmented standards help only small user groups, creating large
integration costs for the rest of the worldintegration costs for the rest of the world ECIMF meta-framework addresses these concernsECIMF meta-framework addresses these concerns
جظغئؤةض
5000€/pcs.
ECIMF Interoperability Framework
Syntax
Semantics
Business processes
Business context
Copyright WebGiro AB, 2002. All rights reserved. 3
ECIMF Business Context ECIMF Interoperability ModelECIMF Interoperability Model
Interop. of technical infrastructuresInterop. of technical infrastructures Interop. of business infrastructuresInterop. of business infrastructures
ECIMF Business Context ModelingECIMF Business Context Modeling Captures economic aspects, based on REACaptures economic aspects, based on REA
Resources: what is traded: what is traded Events: when and how it happens: when and how it happens Agents: who is involved: who is involved Agreements & Commitments: legal aspects, Agreements & Commitments: legal aspects,
transactional naturetransactional nature Value-chain view of commerceValue-chain view of commerce
Chain of business processesChain of business processes Flow of resources between processesFlow of resources between processes
Syntax
Semantics
Business processes
Business context
Business Infrastructures
Technical Infrastructures Important for interoperabilityImportant for interoperability
Economic goals, business rules and legal Economic goals, business rules and legal obligations ultimately define the meaning and obligations ultimately define the meaning and consequences of information exchangeconsequences of information exchange
Copyright WebGiro AB, 2002. All rights reserved. 4
ECIMF – eBTWG coordination
Informal process (email discussions)Informal process (email discussions) Started from the common use of REA frameworkStarted from the common use of REA framework
Initial ECIMF adoption of REA and UMMInitial ECIMF adoption of REA and UMM ebXML use of UMM Economic Elements (based on ebXML use of UMM Economic Elements (based on
simplified REA)simplified REA)
Copyright WebGiro AB, 2002. All rights reserved. 5
REA Enterprise Modeling
Economic exchange as a central conceptEconomic exchange as a central concept Recently extended to provide a comprehensive meta-modelRecently extended to provide a comprehensive meta-model Originally used non-standard modeling notation (now uses UML)Originally used non-standard modeling notation (now uses UML)
EconomicEvent
EconomicResource
EconomicCommitment/Event
Type
reservesstock-flow participationEconomic
ResourceType
EconomicAgentType
EconomicEvent
EconomicAgent
EconomicCommitment/Event
Typedualexecutesreciprocal
Commitment Commitment
custodyassociation
typificationKnowledge
Infrastructure
OperationalInfrastructurereciprocal
dual
executes executes
participationreserves
stock-flow
linkage
participation
associationlinkagecustody
description“the type of resources
an agent can provide…”
Copyright WebGiro AB, 2002. All rights reserved. 6
Rental Recipe
Rental Exchange
REA Enterprise Script
Enterprise script is a series of processes, consisting of Enterprise script is a series of processes, consisting of exchanges realized with recipes (ordered tasks)exchanges realized with recipes (ordered tasks)
RevenueProcess
other processes
stock-flows
Customer
Rental
RentalAgent
CarGIVE
TAKE
CashRcpt
Customer
Cash
Cashier
labor cars
used carscash Asse
ss
Cust
omer
Chec
k ca
r File
&
Choo
se Asse
ss In
sura
nce
& Cr
edit
Fill i
n Co
ntra
ct
Processes Exchanges Recipes(tasks, ordering)
Find
Car
&
Keys
Chec
k-ou
t Ca
rRe
turn
Ca
rUp
date
Fi
les
Copyright WebGiro AB, 2002. All rights reserved. 7
UMM Business Requirements View*
Slightly different, but compatible with REASlightly different, but compatible with REA More focused on technical than human aspectsMore focused on technical than human aspects Provides clear connection with the dynamic aspectsProvides clear connection with the dynamic aspects Uses standard UML diagramsUses standard UML diagrams * simplified, v. N090.R8.x
EconomicEvent
EconomicResource
EconomicResourceType
reserves
PartnerType
EconomicAgent
EconomicCommitment/Event
Type
Commitment
reciprocity
duality
fulfills
resource-flow
classifiesAgreement
classifies
participation
establish
resultsIn
Collaboration
governsrole
resultsIn
Copyright WebGiro AB, 2002. All rights reserved. 8
ebXML Economic Modeling Elements Closely followed a subset of UMM-BRVClosely followed a subset of UMM-BRV Non-normative and disconnectedNon-normative and disconnected
Status of “Technical report”Status of “Technical report” No explicit influence on the BPSS or CPP/CPA No explicit influence on the BPSS or CPP/CPA
formationformation BUT: Very useful worksheets in bpWSBUT: Very useful worksheets in bpWS
Useful for better understanding of the influence of Useful for better understanding of the influence of economic aspectseconomic aspects
Copyright WebGiro AB, 2002. All rights reserved. 9
eBTWG: BOTL and BCP/MC work
e-Business Transitionary Working Groupe-Business Transitionary Working Group Continuation of ebXML (excluding TRP)Continuation of ebXML (excluding TRP)
Business Information Object Types teamBusiness Information Object Types team Business Collaboration Patterns and Monitored Business Collaboration Patterns and Monitored
Commitments teamCommitments team
Copyright WebGiro AB, 2002. All rights reserved. 10
CC, BIE, ABIE, BOT…
BOTs consist of:BOTs consist of: context-modified CCscontext-modified CCs business semanticsbusiness semantics state model (and current state)state model (and current state)
Business Object Types Core Components
BasicBIE
AggregateBIE
BasicCC
AggregateCC
BOT
BOTState
BOTLifecycle
BOTIdentity
expression
expression
expression
Context andRequirements
BOTBusinessSemantic
expression
BOTContent
contextdependent
contextindependent
Copyright WebGiro AB, 2002. All rights reserved. 11
BOTS, Commitments & Collaborations
Commitments, collaborations and processes use BOTs:Commitments, collaborations and processes use BOTs: BOTs help to represent the state of all BIEs processed by each BOTs help to represent the state of all BIEs processed by each
partner, in the appropriate business contextpartner, in the appropriate business context
BusinessObjectTypesSpecifies 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
Copyright WebGiro AB, 2002. All rights reserved. 12
ECIMF Business Context with BOTs Definition of Business Context:Definition of Business Context:
Business Context is a collection of: Agreements / Contracts defining the Commitments Collaboration Patterns (using Business Processes) to execute
commitments Business Objects with their semantics, lifecycle and state,
which encapsulate business data and business rules
Main concepts:Main concepts: Based on REABased on REA Incorporates BOTsIncorporates BOTs Defines the relationship of Defines the relationship of Business ContextBusiness Context to to ProcessesProcesses and and
SemanticsSemantics layers in the ECIMF model layers in the ECIMF model
Copyright WebGiro AB, 2002. All rights reserved. 13
Interoperability: different Business Contexts What is required in traditional business?What is required in traditional business?
Both partners need to agree on:Both partners need to agree on: The type of resources exchangedThe type of resources exchanged The timing (event sequences/dependencies)The timing (event sequences/dependencies) The persons/organizations/roles involvedThe persons/organizations/roles involved
Each of the partners needs to follow the commitments under legal Each of the partners needs to follow the commitments under legal consequencesconsequences
Business Context models need to be equivalentBusiness Context models need to be equivalent Partners need to play complementary Partners need to play complementary rolesroles Expected Expected resourcesresources need to be equivalent need to be equivalent TimingTiming constraints need to be mutually satisfiable constraints need to be mutually satisfiable
• The sequence and dependencies between events need to be the same, The sequence and dependencies between events need to be the same, even though the individual interactions may differeven though the individual interactions may differ
TransactionTransaction boundaries need to be preserved boundaries need to be preserved• Especially those, which cause Especially those, which cause legallegal consequences consequences
Both parties need to receive Both parties need to receive business databusiness data that is mandatory and that is mandatory and sufficient to satisfy their internal processessufficient to satisfy their internal processes
Copyright WebGiro AB, 2002. All rights reserved. 14
Applying Business Context models Business Context Models help to understand Business Context Models help to understand
business-related constraints in integration business-related constraints in integration scenarios:scenarios: Economic exchange viewEconomic exchange view
Events sequence constraintsEvents sequence constraints Stock management constraintsStock management constraints Legal constraintsLegal constraints
Business process viewBusiness process view High-level transaction boundariesHigh-level transaction boundaries Relationship to business activitiesRelationship to business activities Relationship to business documentsRelationship to business documents
All above aspects will limit the degrees of freedom in All above aspects will limit the degrees of freedom in other integration layersother integration layers
Copyright WebGiro AB, 2002. All rights reserved. 15
Shipping Agent’s viewCustomer’s viewExample Business Context models
Example taken from ECIMF-POC documentExample taken from ECIMF-POC document see complete detailed analysis theresee complete detailed analysis there
These two models match - “let’s have a deal!”These two models match - “let’s have a deal!”
«Event» Shipment
«Resource» Truck
2 - TAK E«Agent»
ShippingAgent
custody
stock-flow{use}
role
«Agent»Customer
1 - GIVE
«Event»CashRcpt
«Resource» Cash $1000
«Agent» ShippingAgent
collaboration
collaboration
role
Uses {when, how long, etc …}Gives {when, where to, etc …}
«Commitment»Shipment
«Commitment»Payment
«Agreement»ShippingContract
cash
executes
payload
shipped payload
«Event» Shipment
«Resource» Car
2 - GIVE«Agent»
ShippingAgent
custody
stock-flow{use}
role
«Agent»Customer
1 - TAK E
«Event»CashRcpt
«Resource» Cash
«Agent» Cashier
collaboration
collaboration
role
«Commitment»Shipment
«Commitment»Payment
«Agreement»ShippingContract
labor cars
used carscash
collaborationexecutes
Uses {when, how long, etc …}Gives {when, where to, etc …}
Copyright WebGiro AB, 2002. All rights reserved. 16
«Event» Rental
«Resource» Car
GIVE«Agent»
RentalAgent
custody
stock-flow
role1
Tx 1
Example: a Business Context model
Customer and RentalAgent follow the same collaboration protocolCustomer and RentalAgent follow the same collaboration protocol Customer, RentalAgent and Cashier execute commitments according to the Customer, RentalAgent and Cashier execute commitments according to the
ContractContract Rental occurs first, and then CashReceipt (within time constraints)Rental occurs first, and then CashReceipt (within time constraints) The transaction boundaries are related to Events (and legal constraints)The transaction boundaries are related to Events (and legal constraints)
«Agent»Customer
TAKE
«Event» CashRcpt
«Resource» Cash
«Agent» Cashier
Assess Customer Needs
Check Car file & Choose
Assess Insurance & Credit
Fill in Contract
Find Car & Provide Keys
Check Out Car
Tx 2
Return Car
Update Filescollaboration
collaboration
Rental Agent
Cus
tom
er
Col
labo
ratio
n (B
usin
ess
inte
rfac
e ta
sks)
role
takesgives
2
Copyright WebGiro AB, 2002. All rights reserved. 17
Example: Application of the models Business Context Equivalence:Business Context Equivalence:
Both partners play complementary rolesBoth partners play complementary roles Both partners expect first Rental, then CashRcptBoth partners expect first Rental, then CashRcpt
They still need to agree on the exact timing!They still need to agree on the exact timing! The collaboration tasks have to be grouped into 2 transactions, which The collaboration tasks have to be grouped into 2 transactions, which
correspond to Eventscorrespond to Events Both agreed to the type of Car and amount of CashBoth agreed to the type of Car and amount of Cash
Conclusions from the Business Context model example:Conclusions from the Business Context model example: The assessment of needs doesn’t cause any EventsThe assessment of needs doesn’t cause any Events
I.e. the Customer can repeat this step as many times as he wants I.e. the Customer can repeat this step as many times as he wants without any legal obligations on either sidewithout any legal obligations on either side
The success of Return Car should depend on success of tasks The success of Return Car should depend on success of tasks related to CashRcptrelated to CashRcpt
This collaboration (Customer - Cashier) should be recorded in another This collaboration (Customer - Cashier) should be recorded in another activity diagramactivity diagram
Copyright WebGiro AB, 2002. All rights reserved. 18
Customer(RNIF)
Process Mediator ShippingAgency (EDI)
SecureFlowRemAdv
SecureFlowQuoteReqSecureFlow
QuoteConfirm
SecureFlowPOReqSecureFlow
POConfirm
SecureFlowInvoice
REQUOTE
QUOTES
ORDERS
ORDRSP
INVOIC
APERAK
?
Payment
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
REMADV?
CONTRL
?
Business Context & Business Processes Business Context determines the Business Context determines the
business-related constraints, e.g.:business-related constraints, e.g.: timeoutstimeouts compensation needed for failed compensation needed for failed
transactionstransactions relationships between several relationships between several
business processesbusiness processes etc.etc.
«Event» Shipment
«Resource» Truck
2 - TAK E«Agent»
ShippingAgent
custody
stock-flow{use}
role
«Agent»Customer
1 - GIVE
«Event»CashRcpt
«Resource» Cash $1000
«Agent» ShippingAgent
collaboration
collaboration
role
Uses {when, how long, etc …}Gives {when, where to, etc …}
«Commitment»Shipment
«Commitment»Payment
«Agreement»ShippingContract
cash
executes
payload
shipped payload
These constraints These constraints cannot (easily/at all) cannot (easily/at all) be explained at the be explained at the technical leveltechnical level
Copyright WebGiro AB, 2002. All rights reserved. 19
BOTs and Process Mediation
BOTs explain requirements for specific business dataBOTs explain requirements for specific business data BOTs allow to follow the state of collaborationBOTs allow to follow the state of collaboration BOTs explain how to adjust missing/superfluous data BOTs explain how to adjust missing/superfluous data
between partners, to cause desired state changesbetween partners, to cause desired state changes Business Context + BOTs provides good indications how to Business Context + BOTs provides good indications how to
implement process mediators / brokersimplement process mediators / brokers
Customer(RNIF)
Process Mediator ShippingAgency (EDI)
SecureFlowRemAdv
SecureFlowQuoteReqSecureFlow
QuoteConfirm
SecureFlowPOReqSecureFlow
POConfirm
SecureFlowInvoice
REQUOTE
QUOTES
ORDERS
ORDRSP
INVOIC
APERAK
?
Payment
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
Transaction boundaries (also legal)
REMADV?
CONTRL
?
BOT
BOTBOT
BOT
BOTBOT
Copyright WebGiro AB, 2002. All rights reserved. 20
Summary
ECIMF Business Context concept ties together ECIMF Business Context concept ties together eBTWG CCs, BOTs, Collaborations and eBTWG CCs, BOTs, Collaborations and CommitmentsCommitments
eBTWG work on business modeling fits well with eBTWG work on business modeling fits well with the 4-layer model of ECIMF, and provides a the 4-layer model of ECIMF, and provides a detailed view of each layerdetailed view of each layer
Copyright WebGiro AB, 2002. All rights reserved. 21
Further information
ECIMF Project Information CenterECIMF Project Information Center http://www.ecimf.orghttp://www.ecimf.org
UN/CEFACT eBTWGUN/CEFACT eBTWG http://www.ebtwg.orghttp://www.ebtwg.org