1 / 18

RosettaNET v. ebXML

RosettaNET v. ebXML. The Race for Standards. Nila LaVanaway Claudia Yoshi Dipti Katewa April 25, 2011. Company introduction. #33 in Fortune 500 2010 Revenues $61.6 Billion Employees: >120,000 3 Sectors Consumer Goods Medical Devices Pharmaceuticals 250 Business Units

bunny
Download Presentation

RosettaNET v. ebXML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RosettaNET v. ebXML The Race for Standards Nila LaVanaway Claudia Yoshi Dipti Katewa April 25, 2011

  2. Company introduction • #33 in Fortune 500 • 2010 Revenues $61.6 Billion • Employees: >120,000 • 3 Sectors • Consumer Goods • Medical Devices • Pharmaceuticals • 250 Business Units • HIGHLY Decentralized

  3. Company introduction

  4. J&J Organizational Need Consumer MD&D Non-Op Pharma Pharma Sales HR IT SCM Mftr

  5. J&J Value chain External Manufacturing Prof. Services HR IT Sales Wal-Mart Hospitals Doctors Consumers Packaging Raw Materials Marketing Operations CVS Hotels Target Patients Internal & External Stakeholders Require Reliable Integration

  6. Enterprise software needs

  7. Example: Baby Powder As-IS

  8. Example: Baby Powder Desired-State

  9. Recommendation • Developcom should focus on ebXML

  10. WHAT IS ebXML • The 'eb' in ebXML stands for "electronic business," and you can pronounce the phrase as "electronic business XML," "e-biz XML," "e-business XML," or simply "ee-bee-ex-em-el.“ • ebXML is a set of specifications that together enable a modular electronic business FRAMEWORK through the exchange of XML-based messages.

  11. ebXML Specification • Modular suite of specifications • Core Infrastructure: • messaging service, registry and repository, and collaborative partner agreement • Relies on the Internet's existing standards • HTTP, TCP/IP, MIME, SMTP, FTP, UML, and XML • Supports SM to MID sized enterprises • design and technical architecture promote use of shrink-wrapped, plug-and-play software • puts standard in the reach of smaller businesses

  12. Ebxml Terminology • Registry: A central server that stores a variety of data necessary to make ebXML work. • Business Processes: Activities that a business can engage in • Collaboration Protocol Profile (CPP): A profile filed with a Registry by a business wishing to engage in ebXML transactions. • Business Messages: The actual information communicated as part of a business transaction. • Collaboration Protocol Agreement (CPA): a contract between businesses that can be derived automatically from the CPPs. If a CPP says "I can do X," a CPA says "We will do X together."

  13. Use of ebXML Source: http://www.ibm.com/developerworks/xml/library/x-ebxml/

  14. Sample Ebxml ProcessSpecification DTD declaration <!ELEMENT ProcessSpecification (Documentation*, (Include* | DocumentSpecification* | ProcessSpecification* | Package | BinaryCollaboration | BusinessTransaction | MultiPartyCollaboration)*)> <!ATTLIST ProcessSpecification name ID #REQUIRED version CDATA #REQUIRED uuid CDATA #REQUIRED > A package of collaborations <Package name="Ordering"> <!-- First the overall MultiParty Collaboration --> <MultiPartyCollaboration name="DropShip"> <BusinessPartnerRole name="Customer"> <Performs authorizedRole="requestor"/> <Performs authorizedRole="buyer"/> <Transition fromBusinessState="Catalog Request" toBusinessState="Create Order"/> </BusinessPartnerRole> <BusinessPartnerRole name="Retailer"> <Performs authorizedRole="provider"/> <Performs authorizedRole="seller"/> <Performs authorizedRole="Creditor"/> <Performs authorizedRole="buyer"/> <Performs authorizedRole="Payee"/> [...] <BinaryCollaboration name="Request Catalog"> <AuthorizedRole name="requestor"/> <AuthorizedRole name="provider"/> <BusinessTransactionActivity name="Catalog Request" businessTransaction="Catalog Request" fromAuthorizedRole="requestor" toAuthorizedRole="provider"/> </BinaryCollaboration> [...] Source: http://www.ibm.com/developerworks/xml/ library/x-ebxml/

  15. Benefits of ebXML √ √ √ √ √ √ √ √ √ √ √ √

  16. 7 reasons J&J loves ebXML • Horizontal Standard • No Structure Specified • Independence of Specifications • Reliable Communication • Modularity • Complete Automation • Standard of the Future

  17. Growth Opportunities RosettaNET ebXML • Vertical Standard • Mature • Industry Specific • Horizontal Standard • Emerging • International M Time Time E Growth Growth

  18. COnclusion • ebXML helps J&J grow • ebXML helps J&J help Developcom grow Thank you

More Related