2. XML EUROPE 2002 ebXML and the e-Business Protocol Stack John Yunker Chief Architect Collaborative Domain

3. XML EUROPE 2002 Business Vision Align, implement, optimize, and evolve value chain partnerships

4. XML EUROPE 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

5. XML EUROPE 2002 The alignment domain Business Domain Model Organization A Business Operations Model Organization B Business Operations Model Supply Chain Operations Model e-Business Collaboration Model Process Alignment Information Alignment Goal Alignment Security Infrastructure Message Infrastructure Business Processes Alignment Interface Collaboration Alignment Stack

6. XML EUROPE 2002 StakeholderBusiness Focus Model ActivityElaborated Into Management Goal alignment Business agreements and metrics Business commitment and collaboration specification Operations Process alignment Business operation and interaction processes Business collaboration protocol specification Analysts, Developers Information alignment Business object stateeBusiness message Systems Integrator, Network Admin Security infrastructure Partner authentication and authorization Collaboration role and digital signature Application Integrator Messaging infrastructure Component interaction sequence diagrams eBusiness implementation framework B2B A2A The elaboration methodology

7. XML EUROPE 2002 PerspectiveUMM View Business Operations RequirementsBusiness Domain View (BDV) Business Collaboration Requirements Business Requirements View (BRV) Commercial Transaction Protocol and Business Collaboration Protocol Business Transaction View (BTV) Functional Service ProtocolBusiness Service View (BSV) Network Implementation ProtocolImplementation 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

8. XML EUROPE 2002 Alignment with OSI Stack Network Layer Logical Link Layer Physical Layer Application Layer Session Layer Transport Layer OSI Layered Ubiquitous Communications Reference Model Action Layer Transfer Layer Agent Layer Transaction Layer Security Layer Messaging Layer Service Layer Presentation Layer Transport Application Internet Communications Reference Model Collaboration Layer

9. XML EUROPE 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

10. XML EUROPE 2002 Domain of Alignment > Public Information Definition Public Process Definition Information And Process Exchange Data InformationApplicationEnterprise Business Model Value Chain Business Model InformationApplicationEnterprise Business Model Value Chain Business Model Messaging Interface Specification Interface Dependency Interface Key Public in this context means known to all parties, not the at large public Source: eBTWG

11. XML EUROPE 2002 Principles Business requirements drive technology solutions Embody best practices in collaborative ebusiness standards Focus on expected business results Source: eBTWG

12. XML EUROPE 2002 How to make computers understand business conversations? Put your business objectives into the system Source: eBTWG

13. XML EUROPE 2002 Elaboration of Business Objectives Target States of Business Objects Expected Business Results Business Collaboration Protocol Collaborative Business Process Partner Metrics evaluated asexpressed as Object-in-state expressions aligned usingmodeled as Message Exchanges eBusiness Transactions Semantic Information Structures applied toresulting in feedback

14. XML EUROPE 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

15. XML EUROPE 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.

16. XML EUROPE 2002 Elaboration Methodology Reference Instantiation Requirements Specification

17. XML EUROPE 2002 Participants and Standards

18. XML EUROPE 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) BDV  BRV  BTV  BSV  IFV  PM  TPA Boundary between reference and implementation

19. XML EUROPE 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

20. XML EUROPE 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

21. XML EUROPE 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 The Company

22. XML EUROPE 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

23. XML EUROPE 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 The Company

24. XML EUROPE 2002 BDV – identify collaboration Create Supplier Agreements Query Supplier Agreements Archive Supplier Agreements Update Supplier Agreementts Manage Supplier Agreements +Product Buyer The Company From: Enable SourceFrom: Enable Deliver

25. XML EUROPE 2002 BDV->BRV – map collaboration to processes Create Supplier Agreements +Product Buyer The Company Create Customer Contract Information 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.

26. XML EUROPE 2002 BRV – establish new partnership collaboration +Product Buyer Partner A Partner B +Product Provider 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 “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.

27. XML EUROPE 2002 BTV – 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.

28. XML EUROPE 2002 BTV – commercial transaction Well defined business transaction semantics Business-oriented view

29. XML EUROPE 2002 BTV – library Core component / object model Facilitates semantic consistency across multiple business documents

30. XML EUROPE 2002 BTV – business document Contextually constrained business document composition Include attributes of an entity only where appropriate Content validation based on usage context

31. XML EUROPE 2002 BSV – service-to-service Well defined business service semantics Transaction state transitions are pattern based Technically oriented view

32. XML EUROPE 2002 BSV – message guideline Business document structure Data definition e.g. min,max, lexical representation, data type Validation constraints Consistent entity structure

33. XML EUROPE 2002 Partner model ReferenceInstantiation BDVPartner Process Model BRVPartner Collaboration model Select processes Select collaborations  Constrain implementation Mapping Elaboration

34. XML EUROPE 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

35. XML EUROPE 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.

36. XML EUROPE 2002 Thank you! john.yunker@collaborativedomain.com Reference Material at: www.collaborativedomain.com/standards

37. XML EUROPE 2002 Slides for browsing… At your leisure

38. XML EUROPE 2002 Commitments and Collaborations BusinessEntityTypes Specifies the computation of named business states BusinessProcesses Specifies the interactions between business partners BusinessCommitmentPattern Specifies the reciprocal business commitments BusinessCollaborationPattern Specifies 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

39. XML EUROPE 2002 Commitment Pattern EconomicEvent Records the occurrence of an event specified by the commitment EconomicCommitment Specifies the reciprocal business commitments of each party The event uses the commitment to validate execution conditions EconomicContract Represents the agreement between the parties EconomicResource Represents 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

40. XML EUROPE 2002 Specification / Observation Specification EconomicEventType Specifies compliance conditions for the event representing the exchange EconomicCommitment Specifies conditions governing the exchange of economic value EconomicResourceType Specifies compliance for the economic value exchanged between the parties Observation EconomicEvent Records the occurrence of an event specified by the commitment EconomicResource Represents the actual economic value exchanged by the event occurrence Source: eBTWG

41. XML EUROPE 2002 Collaboration Pattern BusinessEntityState Specifies the conditions under which a business entity is considered to be in a named state BusinessTransaction Specifies the execution of exchanges between business partners The transaction is defined by transitions between its action states BusinessEntityType Represents the business artifacts created or referenced by the collaboration BusinessActionState Specifies 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 BusinessCollaborationPattern Specifies the business transactions and business objects which together define the business elements governed by the collaboration Source: eBTWG

42. XML EUROPE 2002 Business Entity Type Source: eBTWG BusinessEntityLifecycle Represents the sequence of states of a business entity during its existence BusinessEntityType Represents a logical business entity created or referenced during a collaboration The business entity type has a set of lifecycles BusinessEntityContent Represents the agreement between the parties BusinessEntityState Represents 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

43. XML EUROPE 2002 Business Process Source: eBTWG

44. XML EUROPE 2002 Collaboration Functional Decomposition Source: eBTWG

45. XML EUROPE 2002 Business Process Activity Model Start State BusinessCollaborationTask BusinessEntityType [State] BusinessEntityType [State] BusinessEntityType [State] BusinessEntityType [State] End State Join Fork Each activity is a use of one business collaboration usecase Business entity in state Collaboration Activity Model Source: eBTWG