1. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop1 Grenoble Ecole de Management MEDFORIST Workshop RosettaNet Asuman Dogac Middle East Technical University Ankara Turkey asuman@srdc.metu.edu.tr

2. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 2/33 RosettaNet Founded in 1998, RosettaNet is an independent, self-funded, non-profit consortium dedicated to the development of  XML-based standard electronic commerce interfaces  to align the processes between supply chain partners on a global basis The RosettaNet consortium includes IT companies like IBM, Microsoft, EDS, Netscape, Oracle, SAP, Cisco systems, Compaq and Intel http://www.rosettanet.org

3. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 3/33 Internet & XML RosettaNet defines processes and a framework for how data gets passed over the Web and certain handshake criteria Company A SAP ERP Company Specific processing Oracle ERP Company B Company Specific processing Translate from Company A system data set to RosettaNet standards Translate from RosettaNet standards to Company B system data set Partner-to-Partner Electronic Business Interface

4. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 4/33 Where the name RosettaNet comes from? The name Rosetta refers to the crucial breakthrough in the research regarding Egyptian hieroglyphs The name Rosetta is attached to the stone of Rosette This is a compact basalt slab that was found in July 1799 in the Egyptian village Rosette (Raschid), which is located in the western delta of the Nile The Rosetta Stone is a text written by a group of priests in Egypt to honour the Egyptian pharaoh It lists all of the things that the pharaoh has done that are good for the priests and the people of Egypt

5. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 5/33 Where the name RosettaNet comes from? It contains three inscriptions that represent a single text in three different variants of script written in 196 B.C. The text appears in form of  hieroglyphs (script of the official and religious texts),  of Demotic (everyday Egyptian script),  and in Greek Many people worked on deciphering hieroglyphs over several hundred years However, the structure of the script was very difficult to work out The representation of a single text of the three mentioned script variants enabled the French scholar Jean Francois Champollion (1790-1832) in 1822 to basically decipher the hieroglyphs

6. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 6/33 RosettaNet Framework  Partner Interface Processes (PIPs)  A Master Dictionary Business Dictionary Technical Dictionary  A messaging system

7. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 7/33 RosettaNet Framework Partner Interface Processes (PIPs)  The sequence of steps required to execute an atomic business process between two supply chain partners  The activities involved  The roles of the partners  The business documents exchanged  The security, authentication, time-outs of messages exchanged

8. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 8/33 Some Example PIPs Cluster:Order Management PIP 3A2:Request Price and Availability PIP 3A3:Transfer Shopping Cart PIP 3A4:Manage Purchase Order PIP 3A6:Distribute Order Status PIP 3A7:Notify of Purchase Order Acceptance PIP 3B2:Notify of Advance Shipment PIP 3B4:Query Shipment Status Cluster:Inventory Management PIP 4B1:Allocate Inventory Cluster:Product Information PIP 2A1:Distribute New Product Information PIP 2A2:Query Product Information PIP 2A9:Query EC Technical Information Cluster:Marketing Information Management PIP 5C1:Distribute Product List PIP 5C2:Request Design Registration PIP 5C3:Request Design Win

9. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 9/33 RosettaNet PIPs More than 100 PIPs grouped into clusters and then to segments For example, Cluster 3 is Order Management and Segment 3A in this cluster is about Quote and Order Entry As an example of the PIPs in this segment PIP3A4: Manage Purchase Order

10. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 10/33 PIP 3A4: Manage Purchase Order Buyer creates a Purchase Order and sends it to the Seller Seller receives the Purchase Order and returns a Purchase Order Acceptance The Buyer determines success or failure based on message content

11. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 11/33 RosettaNet Business Process Flow Diagram for PIP3A4

12. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 12/33 RosettaNet Business Dictionary Contains information about the trading partners like  Business Properties (e.g. business address),  Business Data Entities (like ActionIdentity), and  Fundemental Business Data Entities (e.g. BusinessTaxIdentifier, AccountNumber) There is only one business dictionary that encompasses all supply chains like Electronic Components (EC), Information Technology (IT), etc.

13. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 13/33 RosettaNet Technical Dictionary and PIPs Provide properties for describing products and services The RosettaNet framework enables supply chain business partners to execute interoperable electronic business (e-business) processes by developing and maintaining PIP implementation guidelines RosettaNet distributes PIPs to the trading partners, who use these guidelines as a road map to develop their own software applications PIPs include all business logic, message flow, and message contents to enable alignment of two processes

14. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 14/33 Doing Business through RosettaNet In order to do electronic business within the RosettaNet framework, there are a number of steps the partners have to go through First, the supply chain partners come together and analyze their common inter-company business scenarios (i.e., public processes), that is, how they interact to do business with each other, which documents they exchange and in what sequence These inter-company processes are in fact, the “as-is” scenarios of their way of doing business with each other Then they re-engineer these processes to define the electronic processes to be implemented within the scope of the RosettaNet Framework

15. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 15/33 Doing Business through RosettaNet An electronic business process includes both the interactions between partner companies, and the private processes within the company RosettaNet provides guidelines only for PIPs which are the public part of the inter-company processes

16. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 16/33 Business Processes Process PO Send PO Customer Send PO Supplier Process Sales Order Customer Supplier Receive PO Acknowledge Send PO Acknowledge Send PO Response Close Send PO Receive PO Response Send PO Response Acknowledge Receive PO Send PO Response Receive PO Response Acknowledge Receive PO Check Customer Check Credit Check Availability Create Sales Order Receive PO Acknowledge Send PO Acknowledge Send PO Response Close Receive PO Request Select Supplier Generate RFQ Send RFQ Select RFQ Response Send PO Close Send PO Receive PO Response Send PO Response Acknowledge Receive PO Send PO Response Receive PO Response Acknowledge Receive PO Check Customer Check Credit Check Availability Create Sales Order Private process A (Company -specific) Public process (Standard) Private process B (Company -specific) POPO CRM SCM ERP Figure provided by Vitria Systems

17. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 17/33 Dialog human-to-human business exchange Partner-to-Partner eBusiness exchange Alphabet Grammar Words Sound Business Process Telephone Business Process Telephone DIALOG PIP™ RosettaNet Framework Dictionary eBusiness Process XML Internet Ecom Application E-Business Exchange

18. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 18/33 Necessary to differentiate: Public Business Processes: The process among the trading partners RosettaNet defines and fixes Public Business Processes in terms of PIPs Private Business Processes: The business processes internal to the company

19. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 19/33 An Example Public Business Process Notify of Billing PIP3C5 Notify of Shipment Receipt PIP 4B2 Notify of Shipment Status PIP3B3 Transportation Request PIP3B1 Notify of Invoice PIP 3C3 Request Purchase Order PIP 3A4 Request Price and Availability PIP 3A2 2 1 3 5 6 4 7

20. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 20/33 An Example Consider, for example, a scenario where a buyer requests the price and availability of some products from a seller (PIP3A2) After receiving the response, the buyer initiates a Purchase Order Request (PIP3A4) The seller, on the other hand, after acknowledging the Purchase Order Request, sends an invoice notification (PIP3C3) to the buyer The seller sends a transportation request (PIP3B1) to the shipper (There is a third party in this scenario, which is a shipper)

21. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 21/33 An Example The shipper, after shipment of the goods, sends the status of the shipment (PIP3B3) When buyer receives the shipment, it sends a shipment receipt notification (PIP4B2) to the seller. Finally, the seller prepares a billing statement and notifies the buyer (PIP3C5)

22. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 22/33 Product Categorization and Classification in RosettaNet Product categorization and classification in RosettaNet is achieved through RosettaNet Technical Dictionary (RTD) The RTD specifies classes of products with their properties in XML DTD That is, associated with a product type, there is a collection of predefined XML tags Each product class also has a corresponding Universal Standard Products and Services Classification (UNSPSC) code, basically used to differentiate the products in the catalogs that do not fall into IT domain

23. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 23/33 Global Trade Item Number (GTIN) In RosettaNet, PIPs use Global Trade Item Number (GTIN) to identify products In contrast to the product numbering that has been traditionally used within the Electronic Components supply chain, GTINs do not contain embedded information to describe products Traditional product numbers are split into “segments‘”, each representing specific product characteristics RosettaNet, on the other hand, in order to streamline the information exchange throughout the supply chain, defines GTINs to be used by PIPs to identify products In this way proprietary manufacturer and customer product numbers are avoided

24. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 24/33 Global Trade Item Number (GTIN) In RosettaNet product information details can be obtained by querying a supply chain partner's catalog by using the standard tags through “PIP2A5/EC Query Technical Information” to return one or more GTINs along with product data Hence RTD is used in associating the product data with GTINs To implement the Technical Dictionary, an organization must categorize all saleable products according to the product classes and class properties specified in the Technical Dictionary

25. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 25/33 RosettaNet Messaging Structure Execution of PIPs involves exchanging messages between the parties, and RosettaNet provides a Business Message structure for this purpose RosettaNet business messages (also termed as action or service messages) consist of a message header and a message body Both the header and the body are complete, valid XML documents The header and the body are encoded within a multipart/Related MIME message

26. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 26/33 RosettaNet Messaging The message content is specified in individual PIPs Each PIP has one or more "actions" that are described by means of an individual DTD or schema RosettaNet Implementation Framework (RNIF) specifies and provides for a consistent mechanism to digitally sign and/or encrypt all RosettaNet messages (as needed), independent of the transfer protocol, PIP and the specific business document being exchanged It also specifies a reliable messaging mechanism based on "Acknowledgements"

27. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 27/33 RosettaNet Transport The PIP business message is encapsulated into a RosettaNet protocol message termed as "RosettaNet Object” The RosettaNet Object is composed of  a version and content length header,  content comprising a business action message, and  a digital signature length followed by a digital signature trailer "RosettaNet Object” is encapsulated into a message of HTTP protocol and send as a as a direct HTTP message

28. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 28/33 RosettaNet Implementation Successes Partners Implementation Results Arrow & Carrier Up and running in six weeks Reduced a 5-day batched delivery cycle to overnight; results in inventory reduction, improved customer satisfaction Bourns & TTI Implemented PIP™ 3A2 in two weeks New process converted access to inventory information from a week’s delay to real-time data; improved customer service Compaq & Delta (Taiwan) Implemented PIP 3A4 and PIP 3A7 Reduced the order processing lead time to several minutes; enabled Compaq to receive the P.O. acknowledgement immediately and allowed departments involved in the process to receive related information in real time Intel & WPI (Taiwan) Implemented PIP 3A4 and PIP 3A7 Automated process reduced the cycle time for order processing between the companies Samsung & Sony First implementation between Korea- and Japan-based partners Expected to shorten lead time

29. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 29/33 RosettaNet Partners Solution Providers Supply Chain Companies Government Agencies Trade Associations Standard Bodies

30. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 30/33 Information Technology (IT) Supply Chain Board 3Com Arrow Electronics Avnet Cisco Systems Compaq CompUSA Dell Federal Express GSA Hewlett-Packard IBM Ingram Insight Intel Lucent Technologies NEC Netscape Office Depot Pioneer Quantum SAP Siemens Solectron Tech Data Trilogy UPS

31. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 31/33 Electronic Components (EC) Supply Chain Board Agilent Altera Arrow Electronics Avnet AVX Bourns Cisco Systems FCI Future Electronics Hitachi IBM Intel Kemet Lucent Technologies Memec Micron Technology Molex Motorola National Nokia NEC Philips Semiconductors Pioneer Samsung Solectron Sony STMicroelectronics Texas Instruments Toshiba Tyco Electronics Xilinx

32. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 32/33 Semiconductor Manufacturing (SM) Supply Chain Board Air Products & Chemicals Agilent Technologies Amkor Technology Applied Materials ASE Chartered Semiconductor Intel JSR LSI Lucent Technologies Micron Technology Motorola National Semiconductor NEC Philips Semiconductors Samsung Electronics Shin-Etsu Handoutai Shinko Electronics SPIL Sumitomo Bakelite Sumitomo Metal Texas Instruments TOK Tokyo Electron Toppan Toshiba TSMC UMC Winbond Xilinx

33. A. Dogac Grenoble Ecole de Management MEDFORIST Workshop 33/33 Thank you very much for your attention!