Presenters Name Presenters Title Affliation December 2002 Email@address

1. ebXML News, Implementations, Developments and more Presenters Name Presenters Title Affliation December 2002 Email@address.com

2. Contents • Deployment Landscape • ebXML Today • Latest Specification Developments • ebXML in the marketplace - vendor products • ebXML projects - deployments, funding, and pathfinder work • Summary

3. Deployment Landscape Chasing the technology ‘bouncing ball’; delivering real ROI for eBusiness

4. The CIO nightmare • What standards do I choose? • How do I build significant ROI for my organization? • Can I leverage my existing systems? • What resources are available to deploy my solution? • What are my partners doing? • How much of this is real? • What if I just build it my way and ignore everyone else?

5. Identifying the Needs • What are you trying to build anyway? • Better EDI system? • Reach SME partners more effectively? • eMarketplace solution? • Next generation XML system and network? • Open eGovernment systems? • Integration of major corporations applications? • Common industry collaboration and vocabularies?

6. Electronic Business Technologies

7. Business Architecture Reference Framework e-Business Roadmap Reference Models Data Applications Reference Views Technology Architecture Technology Business Why is the engagement being undertaken? What are your organization's primary motivations and business drivers? Functional What will your system do? What information will it provide? Technical How will your system be realized with IT components? Implementation With what specific products and other components will your system be implemented? In what organization? According to what plan? For each reference view OBJECTIVES REQUIREMENTS MODELS PRINCIPLES & RULES STANDARDS ONTOLOGY RATIONALE AUTHORATATIVE SOURCE PRIORITY RISK MANAGEMENT AS IS MIGRATION TO BE

8. Solving the right problem • Web services: • interactive point-to-point unrestricted transactions • internal backend system sockets • ebXML: • secure, reliable business-to-business exchanges • metadata alignment, consistent vocabularies, registries • open eBusiness architecture, business process engineering • W3C XML: • wire formats, syntax parsing, security, storage and retrieval • middleware plumbing, web service plumbing

9. Standards Focus • OASIS • ebXML technology specifications • Web service technology specifications • Industry XML vocabularies • Registry technology specifications • CEFACT • ebXML architecture specifications – UMM / UML • Migration of UN/EDIFACT to UMM world • Business Process alignment • Industry Standards Groups • Local vocabularies for vertical industry use

10. Standards Focus (more) • ISO • International standard tables and measures • Registry technology specifications • OMG • Programming language technology • EAN/ UCC / CEN / DISA and others • Cross-industry integration • Is there overlap and confusion of mission? YES!

11. Standards Chemistry Traction XML W3C web services SOAP v1.1 SOAP v1.2 W3C BPSS CEFACT eb MS v2 OASIS ebXML spec’s Market Adoption WSDL v1.2 W3C WSDL v1.1 CCSD CEFACT OAG BODs eb Reg v2 OASIS UMM/ UML UDDI v3x OASIS UDDI v3 UDDI.org Content Assembly UBL XML SGML ISO UN/EDIFACT Proprietary JCV Consortia SDO Standing Open Standardization

12. Reap the Benefits of Standards • Lower costs and reduced errors. • Greater efficiency of processes. • Drive consistent business conduct. • Increase speed of deployment. • Improve inventory controls. • Reduce risk for businesses. • Provide investment protection. Key: Champion awareness and recognition of the value of standards. The first step is knowledge.

13. ebXML Today Mission, focus and components

14. ebXML Adoption Q4 - 2002

15. ebXML History • Begun as 18-month initiative in November 1999 • V1.0 Specifications delivered on schedule in May 2001 • Developed in an open process by more than 2000 participants representing 100 organizations in 150 countries • Facilitation meetings held in N.America, Europe and Japan • Development and deployment of the specifications is continuing within OASIS and CEFACT with support from NIST, UCC/EAN, EU and more.

16. ebXML - Why? • Computers are quicker and more reliable than people (in processing data), and offer significant potential ROI • Mature organisations process their information electronically and reap very significant competitive and production benefits • Information exchange & accounting between organisations is: • largely still paper / fax based • dictated by regulation or large customers • great once you get it working and stable electronically • lots of potential in internet as delivery medium • international need to enable global trade and opportunities • eCommerce / Web revolution well underway (e.g. eBay+)

17. Challenges of e-business today • XML initiatives underway for specific industries • attempts at verbatim translation of EDI to XML • Consensus required on common requirements • No core infrastructure means incompatibility, reinvention and segregated pockets of communication

18. Manufacturers Shippers Distributers Traditional EDI Each arrow is a project

19. SMDG Togaf HR-XML EHD xCat UBL Rosettanet OTA IATA cXML E-construct Ford AIAG Bolero Boeing Opentrans xCBL HL7 Acord CIDX xBRL Wal-mart agXML VICS SWIFT GCI OBI Odette XML More than 400 initiatives

20. ebXML ebXML automates business partner connectionacross industry boundaries Profile Profile Profile Profile Profile Profile Profile Profile Each arrow is a product

21. ebXML Approach – Business Centric Each participant needs to specify their own: ‘Who, What, Why and How?’ ebXML parlance Business Terms Organisation(s) Industry / Service Business process Context factors Transaction interchanges Information details Messaging details CPPA BPSS Content Assembly XML content structure(s) Core components + Registry CPP + ebMS

22. ebXML Business Profile Organisation Business process Information Technology Own Capabilities and Requirements to trading partners ebXML Registry ebXML Profile

23. App.2 App.1 Runtime communication ebXML Profile matching ebXML Profile 1 ebXML Profile 2 Requirements Alignment ebXML Agreement

24. ebXML Profile Components Collaboration Partner Agreements Collaboration Partner Profiles 5 Contract Business Integration Registry Taxonomy BP Specification 4 Workflow Process XForms 3 Specifications Schema Messages Assemblies Artifact relationships Web Services 2 Motivation Time People Presentation Roles Rules Events Directory Services Technology Integration Data/Codes Services/Functions Network 1 ebMS/SOAP Nouns Verbs Secure content delivery

25. Deployment Flows / Components Collaboration Partner Profiles 4 5 Collaboration Partner Agreements To/From Partner Registry 2 Events Adaptors 2 3 Rules Messages Transform BP engine Verbs Nouns 4 Content Payload 1 Process Secure Content Delivery Messages Messaging Verbs Nouns 2 Roles Templates ebXML / WS 1

26. Bulk Buying Example – GM Bulk Used Cars <<BinaryCollaboration>> General Motors Bulk UsedCar Buyers Trading PartnerAgreement (CPA) Business Process Specifications (BPSS) Bulk Buying Business Process Specifies Contains Check Vehicle Availability Dealer Location Vehicle History Submit PO Business Transactions Contains XML Message Structures DTDs

27. Example –Bulk Used Cars - Dealers Conceptual DealerLocator DealerLocator Map To AvailableVehicle Activity Map To DealerLocation Activity DealerLocator e.g., Map DealerLocation Activity to the DealerLocator Web service Map To Business Analysts map B2B Transactions to the services available in Back-end systems VehicleHistory Activity PurchaseRequest Activity Map To PurchaseApproval Activity Map To [Business Error] DealerLocator

28. VehicleHistory Activity <<BusinessTransactionActivity>> VehicleHistory Activity PurchaseRequest Activity <<BusinessTransactionActivity>> Vehicle Purchase Request Activity PurchaseApproval Activity <<BusinessTransactionActivity>> VehiclePurchase Approval Activity Script into BPSS definitions Conceptual AvailableVehicle Activity The B2B Collaboration may be composed of several business transactions The resulting sequence is captured in a BPSS <<BusinessTransactionActivity>> DealerLocation Activity <<BusinessTransactionActivity>> [Business Error] Business Transactions Physical

29. Example Deployment - GM DMZ Legacy Apps B2B—Trading Partner EJBBusinessServices Internal Firewall Internet EJBBusinessServices DB ebXMLProcessServer ebXML ebXMLBSI ebXMLMSH SOAP Orchestration Services Systems Interface J2EE Application Server Container Business ProcessCollaboration COTSApps J2EE Web Container Legacy Apps Apps CPA BPSS

30. Deployment Issues - Information Quality • For eBusiness - vital to ensure low-cost interoperability • Accounting – mandatory for accuracy and verification • US Gov – critical for homeland security integration • Globally – meeting the challenges of a secure reliable electronic marketplace

31. XML Information Exchange Quality (and long-term consistency) ebXML Secure Authenticated Delivery and Tracking: ebXML Messaging system, envelope format and payload with exchange source profile (CPP) controls Delivery Assembly XML Content Assembly: Business logic for content structure decisions and explicit rules to enforce content, and interdependencies, with business exchange context, and content definition UID references Schema: Content structure definition and simple content typing Schema Registry/ Dictionary business information UID content referencing system ensures consistent definition usage UID

32. ebXML in the marketplace Vendor products

33. UCC ebXML Interoperability Certification • Eleven vendors:

34. Vendor Challenge – Implementing Business-Centric Approach • Semantics • Define Business Context • Use Case and Sequence Diagrams • Identify Authoritative Sources • Register/Link Source Concepts • Register Internal Concepts • Assign Classification (Dublin Core) • Place into organization’s ontology - concept - linking - construct Business Goals Frameworks & Stds Conceptual Layer Business Drivers: Model / Process / Patterns / Constraints Alias Concepts • Requirements • Identify business rules / patterns • Scope; atomics & constructs • Structure: Resolution / Indenture • Workflow / process identification • Mandatory vs Optional • Sub-setting Codelists Strategic Context Business Layer Community of Interest Reuse - Compound Constructs Target Constructs Legacy • Outreach • Role-Process Identification • Standards & Framework Adoption • Qualifier to Object Breakout • Thesaurus Assignment • Interchange Mapping Extension Layer Reuse Publish Technology Model / Constraints Mappings Implementation Guide Partner Profile • Transaction / Presentation • Collaboration Partner Specifics • Elements vs Attributes • Length, Datatyping and Masking • Routing & Packaging • Service Parameters • Framework Envelope - eg. X12 slots Tactical ‘Service’ Agreement Implementation Layer Physical

35. ebXML projects Deployments, funding, and pathfinders today

36. US Government • CDC – lightweight ebXML client developed and being UCC certified • Homeland Security • NIST – OAG test-bed • DARPA – Advanced Supply Chain • CIO Council – Registry • DFAS – Information Agility • Addresses • Invoices • FDIC – MDR with intelligent mapping project

37. Canadian Government • PWGSC – Registry – base implementation path finder • PWGSC - EDI transformation using ebXML approach - evaluation • Integrated Justice System – reviewing funding Registry pilot for data dictionary alignment – IJI content, SSDUE content

38. European ebXML • CEN/ISSS • EAN • CEN / eBIS Vendor forum - project beginning in September – to demonstrate implementations in Europe using ebXML • SEEM initiative for eCommerce

39. Automotive • GM demonstrated their ebXML system with web service integration at AIAG, Detroit - 25th Sept’02 • Covisint – endorsed ebXML • STAR – ebXML messaging pathfinder implemented and delivered • AIAG – working from X12 base • OAG - Vendor challenges using automotive payloads and business processes • Straw poll in Detroit – 50% of new projects now using OAG V8 XML

40. Industry • Australia • State of Victoria (Sydney) • Utility Supply – Gas and Electric Distribution • In production – 100,000 ebXML messaging transactions daily. • USA - State of Texas • Electric distribution – with power suppliers • Using ebXML messaging for daily transactions

41. Industry Groups • DISA X12 – DRIVE Registry using GoXML • OTA and IFX • OAG – implementing Registry • OAGIS V8.0 schemas • Vendor challenges • UCCNet ebMS certification • OAG - RosettaNet – ebXML migration

42. Latest Specification Developments Upcoming capabilities and extensions

43. Upcoming Registry Developments ebXML V3.0 enhancements - partner discovery / direct content access and UDDI Delivering on eBusiness web services -with critical federated model Allows open industry and government deployments worldwide Allows building collaborating communities

44. Registry v 3.0 • Cooperating Registry Model • Allows linking multiple ebXML registries together • Loosely-coupled federation approach • Local operators have autonomy over their own registry • Can make several small registries appear as one single large registry • Supports direct accessing via URI (REST approach) • Built using the existing V2.0 Registry components • Event notification mechanism

45. Example Deployment One View to User Organizations Request Federation Make Associations Synch User Groups Local content control Federation Server OAG Registry Content Classification STAR Registry OAG BOD's STAR Assemblies STAR BPS OAG staff Approve Data Dictionary Data Dictionary Element Definitions STAR staff Transaction Assembly Element Definitions Transaction Assembly

46. Extending ebXML Registry Collaboration Protocol Profile (CPP) Supported Business Process (BPS) <<references>> 1.. WSDL <<References>> 1.. Binding Info INPUT/OUTPUT DTDs & Schemas DTD’s Schemas? DTD’s Schemas? + Web Services

47. Leveraging UDDI work within OASIS Start here Collaboration Protocol Profile (CPP) tModel UDDI Registry WSDL + UDDI ebXMLRegistry Binding Info INPUT/OUTPUT DTDs & Schemas + Web Services Core Comp. Core Comp. Core Comp. Core Comp.

48. ebXML Vision “A semantic registry is the key foundation block upon which global electronic business exchanges will be built”.

49. Summary Adopting ebXML - roadmap for implementers

50. Some ebXML selection metrics • B2B or large A2A Environments— extending or integrating enterprise systems, or when loosely coupled messaging is desirable • Need Reliable Messaging— when enterprise services perform updates, insert, or deletes to the underlying data model, reliable messaging becomes critical • Security is a Concern—when different security profiles and requirements exist between trading partners • High scalability requirements—ebXML’s loosely coupled messaging architecture allows for horizontal scalability, queuing, and clustering • Want to Leverage Industry Standards—XML grammars, business process modelling and trading partner agreements