Presenters Name Presenters Title Affliation December 2002 Email@address.com

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

2. Contents Speaker Hint • Deployment Landscape • ebXML Today • Latest Specification Developments • ebXML in the marketplace - vendor products • ebXML projects - deployments, funding, and pathfinder work • Summary This presentation contains extensive materials, you should tailor this to your audience and the amount of time available

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? • How do I avoid being in a vendor revolving doors strategy? • What if I just build it my way and ignore everyone else?

5. Identifying the Needs Speaker Hint • 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? You can tailor this list to suit your audience and their industry

6. The Challenge of Change • People accept that a digital world is coming and are adjusting their work habits accordingly: • Virtual presentations and meetings • All digital documents and transactions • Digital photographs, voices, sound, and signatures (UPS, Radio Shack, Home Depot, Best Buy and more). • Shared factor – naturally multi-lingual. • Vast gulf between First World and Third World.

7. Business Challenges • In determining operational needs there are three levels and areas to include: • The first level is the overall operational approach to solving large enterprise level interactions, • then enterprise to small business interactions, • and small business to small business interactions.

8. Affordable Infrastructure • For a large enterprise this translates into: • Reducing the headcount of staff needed • Decreasing the effort to migrate to implementation versions • Lowering the necessary specialty skills to instead enabling general business staff (costs, productivity, customers). • For small business it means: • Being able to support multiple large partners diverse requests for information interchanges • Supporting a single technology base • Linking the interchange to your applications.

9. Electronic Business Technologies

10. Business Architecture Reference Framework e-Business Roadmap Process 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

11. XML itself is not enough • XML, by itself, does not solve interoperability problems yet it is an important tool for doing so. • XML does not provide semantics. • XML by itself is not the magic bullet. • What we really need is a consistent set of methods for building interoperable eBusiness systems using XML – “railroads and telephony”.

12. 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

13. 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

14. 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!

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

16. 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.

17. ebXML Today Mission, focus and components

18. ebXML Adoption Q4 - 2002

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

20. ebXML – Why and How? • Computers are quicker and more reliable than people (in processing data), and offer potential business 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 • cost savings and availability via internet as delivery medium • international need to enable global trade and opportunities • eCommerce / Web revolution well underway (e.g. eBay+) Productivity + ROI

21. 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 the norm • Segregated pockets of communication

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

23. 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

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

25. 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

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

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

28. 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

29. 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 Assembly 4 Content Payload 1 Process Secure Content Delivery Messages Messaging Verbs Nouns 2 Roles Templates ebXML / WS 1

30. 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 Speaker Hint Business Transactions Contains XML Message Structures DTDs You can change the context here to your own project

31. Example – Bulk Used Cars - Dealers Conceptual Speaker Hint DealerLocator DealerLocator Map To AvailableVehicle Activity Map To DealerLocation Activity You can change the context here to your own project 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

32. VehicleHistory Activity <<BusinessTransactionActivity>> VehicleHistory Activity PurchaseRequest Activity <<BusinessTransactionActivity>> Vehicle Purchase Request Activity PurchaseApproval Activity <<BusinessTransactionActivity>> VehiclePurchase Approval Activity Script into BPSS definitions Speaker Hint You can change the context here to your own project 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

33. 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 Speaker Hint This deployment model shows the ebXML components, you can adapt this to your own implementation context.

34. 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 Speaker Hint You can add context here to your own project, and change the priority to those from your user commuity

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

36. Web Services+ ebXML Type Request/response Collaboration Communication RPC-style synchronous communication between tightly coupled services, Document-style asynchronous communication between loosely coupled services Synchronous, asynchronous communication Business ServiceInterface description WSDL CPP, CPA(WSDL within CPP, with CPA also) Protocol and Formats SOAP, XML ebXML Message Service (over SOAP), XML, BPSS (as "business" protocol) Content Standards None Recommended Standards (e.g. OAGI BODs, EDIFACT, UBL) How to find business partners UDDI Registry ebXML Registry(UDDI Registry may point to an ebXML Registry or Registry objects (e.g. CPA)) Comprehensive Messaging Delivery With thanks to Alan Kotok from his recent article : http://www.webservices.org/index.php/article/articleview/451/1/22/

37. ebXML in the marketplace Vendor products

38. UCC ebXML Interoperability Certification • Eleven vendors: • Full list of other ebXML vendors available from:- • http://www.ebxml.org/implementations/

39. 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 • 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 Speaker Hint Target Constructs Legacy • Outreach • Role-Process Identification • Standards & Framework Adoption • Qualifier to Object Breakout • Thesaurus Assignment • Interchange Mapping See presentation slide notes. 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

40. ebXML projects Deployments, funding, and pathfinders today Speaker Hint This section can be customized to your audience. Additional project details can be found from the JMT website: http://www.ebxml.org/ebxml_jmt/index.htm/#documents

41. 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

42. Canadian Government • PWGSC – Registry – base implementation path finder • PWGSC - EDI transformation using ebXML approach - evaluation • XML in Ontario (XiO) – In Phase 2 through March 2003, evaluating tools to use ebXML Reg/Rep for prototype implementation – committed to ebXML. • EDAT – e-Forms Domain Architecture - In 2002, integrated MS BizTalk environment with a Registry and ebXML adapter.

43. European ebXML • CEN/ISSS • EAN • CEN / eBIS Vendor forum - project began in September – to demonstrate implementations in Europe using ebXML • SEEM initiative for eCommerce • Industry - Steel 24x7 Open eXchange

44. 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

45. 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

46. 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

47. Latest Specification Developments Upcoming capabilities and extensions

48. Content Assembly Mechanism (CAM) • Legacy payloads can be used “as is” • Supports vocabulary alignment and multi-lingual element tags • Minimizes overhead in payload itself – can be just simple structure • Provides ability to do automated mapping • OASIS TC – scheduled to deliver complete specifications in July, 2003

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

50. 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