Q4: Standard Development Approaches

1. Q4: Standard Development Approaches UN/CEFACT Standard Development Advisory Team Conference Call, 20th January 2010 Christian Huemer & Philipp Liegl

2. ebXML is gone … but which ideas are still valid? … where enterprises of any size, anywhere can: • find each other electronically • conduct business through the exchange of XML based messages • according to standard business processes • using standard message structures • with clear business semantics • according to agreed trading partner agreements • using off the shelf purchased business applicationscommercial off-the-shelf software (COTS)

3. Data Centric Approaches Top-down business document standards A Generic standard Subset A BusinessDomain B Business Domain A union Subset B Subset C B Bottom-up business document standards Exten-sion A Exten-sion B A inter- section Business Domain A Business Domain B Core standard Core standard B

4. Hybrid Approaches Top-Down: but hooks for (arbitrary) extensions A Generic Standard BusinessDomain B Business Domain A Union + Extension B Exten-sion X Exten-sion Y Generic Generic Generic Standard A inter- section Business Domain A Business Domain B Generic Standard Core Standard Core standard B

5. Hybrid Approaches ? Subset A ? Generic(Requ A) Generic(Requ A) Generic(Requ B) Core standard Core standard

6. Registry CC BIE? UN/CEFACT BIE CIDX Automotive SWIFT BIE of BIE Or Rules on BIE Swiss Bank Assocation Austrian Bank Assocation Bayer BASF AIAG ODETTE

7. Process oriented approach • Which process are we talking about? • A process to be followed in the standardization • No, this is referred to as a method(ology) • The processes triggered in a company when a document arrives • No, orchestrations are not subject to standardization • The interactions between business partners • Yes, we do care about choreographies

8. B2B Application Computing B2B Application Server B2B Application Server SOAP request over HTTP, SMTP, ... Messaging Layer Messaging Layer Document Layer Common Document Logic Document Layer Business Layer Business Layer Common Process Logic • Is itCEFACT´sjob? • A Methodology? • Building Blocks forprocesses? • Standard Processes? • Customizationof StandardProcesses • Reference Processes? … … Databases ERP Systems Databases ERP Systems Persistence Layer Persistence Layer

9. The original UMM idea – realistic? • Subject of standardization is an inter-organizational business process, it is defined by a business collaboration protocol • A business collaboration protocol consists of many business transactions. A business transaction exchanges one or two business documents. • A business transaction and its document exchanges are not developed in isolation, but always in the context of the business collaboration protocol • It follows, that there may be different documents of the same type when used in different business collaboration protocols

10. The CEFACT delivers only a process methodology approach • CEFACT defines business documents only • However, CEFACT suggests the UMM to specify a choreography of document exchanges • The definition of these choreographies is up to • Industry consortia (?) • Supply chain leaders (?) • Software vendors (?) • Individual companies – market leaders (?) • … or whoever wants to do the job ;-) • Question: Should the choreographies be contained in the registry at the 2nd and 3rd level?

11. Conservative: The CEFACT delivers business transactions • CEFACT still concentrates on business documents • Each business document results in a one way business transaction • Alternative: some business documents are grouped into two way business transactions (e.g. request for quote and quote) • CEFACT suggests UMM to specify a choreography amongst business transactions • The definition of these choreographies is still up to • Industry consortia (?) • Supply chain leaders (?) • Software vendors (?) • Individual companies – market leaders (?) • … or whoever wants to do the job ;-) • Question remains : Should the choreographies be contained in the registry at the 2nd and 3rd level?

12. Advanced: The CEFACT delivers reference models • CEFACT still concentrates on business documents • Each business document results in a one way business transaction • Alternative: some business documents are grouped into two way business transactions (e.g. request for quote and quote) • Additionally, CEFACT delivers reference models proposing a business collaboration protocol - i.e. a choreography amongst the business transactions • The customization of these choreographies is still up to • Industry consortia (?) • Supply chain leaders (?) • Software vendors (?) • Individual companies – market leaders (?) • … or whoever wants to do the job ;-) • Question remains : Should the choreographies be contained in the registry at the 2nd and 3rd level?

13. Visionary: The Business Entity State Centric Approach • A business collaboration is about changing states of one or more business entities • An exchange is about synchronizing the states of one (or more) business entities • The exchange is limited to the information required to change the state of a business entity (or all business entities that are changed) • A business entity is a data model comprising several classes (CCs / BIEs) • A data model for a business collaboration is the union of the data models of the considered business entities • An exchange specifies a view into the data model of the business collaboration. This view comprises all the data necessary to perform a state change.