Beruflich Dokumente
Kultur Dokumente
RosettaNet
Asuman Dogac Middle East Technical University Ankara Turkey asuman@srdc.metu.edu.tr
Grenoble Ecole de Management MEDFORIST Workshop
A. Dogac
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
Grenoble Ecole de Management MEDFORIST Workshop 2/33
A. Dogac
Company B
Internet & XML
Company Specific processing Oracle ERP
RosettaNet defines processes and a framework for how data gets passed over the Web and certain handshake criteria
3/33
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 Grenoble Ecole de Management
MEDFORIST Workshop
4/33
A. Dogac
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
Grenoble Ecole de Management MEDFORIST Workshop
A. Dogac
5/33
RosettaNet Framework
A messaging system
A. Dogac
6/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
Grenoble Ecole de Management MEDFORIST Workshop 7/33
A. Dogac
A. Dogac
8/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
A. Dogac
9/33
Buyer creates a Purchase Order and sends it to the Seller Seller receives the Purchase Order and returns a Purchase Order Acceptance
A. Dogac
10/33
A. Dogac
11/33
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.
Grenoble Ecole de Management MEDFORIST Workshop 12/33
A. Dogac
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
Grenoble Ecole de Management MEDFORIST Workshop 13/33
A. Dogac
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
A. Dogac
14/33
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
A. Dogac
15/33
Business Processes
Customer
Private process A (Company -specific) Process PO Receive PO
Request
Supplier
Public process (Standard) Send PO Supplier
P O
Figure provided by Vitria Systems
Select Supplier Generate RFQ Send RFQ Select RFQ Response Send PO
Send PO
Receive PO
Check Customer
CRM
Receive PO Acknowledge Send PO Acknowledge Check Credit Check Availability Receive PO Response Send PO Response Create Sales Order Send PO Response
SCM
Close A. Dogac
Close
ERP
16/33
E-Business Exchange
Telephone Telephone Business Process Business Process Dialog DIALOG Grammar Words Alphabet Sound
human-to-human business exchange
A. Dogac
RosettaNet
PIP
Framework Dictionary XML Internet
Partner-to-Partner eBusiness exchange
17/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
A. Dogac
18/33
A. Dogac
19/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)
Grenoble Ecole de Management MEDFORIST Workshop 20/33
A. Dogac
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)
A. Dogac
21/33
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
A. Dogac
22/33
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
Grenoble Ecole de Management MEDFORIST Workshop 23/33
A. Dogac
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
Grenoble Ecole de Management MEDFORIST Workshop
A. Dogac
24/33
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
A. Dogac
25/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"
A. Dogac
26/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
A. Dogac
27/33
Implementation
Up and running in six weeks Implemented PIP 3A2 in two weeks
Results
Reduced a 5-day batched delivery cycle to overnight; results in inventory reduction, improved customer satisfaction New process converted access to inventory information from a weeks delay to real-time data; improved customer service 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 Automated process reduced the cycle time for order processing between the companies
First implementation Expected to shorten lead time Grenoble Ecole between Korea- and de Management MEDFORIST Workshop Japan-based partners
28/33
RosettaNet Partners
Trade Associations Standard Bodies Government Agencies
Solution Providers
A. Dogac
29/33
Hewlett-Packard IBM Ingram Insight Intel Lucent Technologies NEC Netscape Office Depot
Grenoble Ecole de Management MEDFORIST Workshop
30/33
Pioneer Samsung Solectron Sony STMicroelectronics Texas Instruments Toshiba Tyco Electronics Xilinx
A. Dogac
31/33
Micron Technology Motorola National Semiconductor NEC Philips Semiconductors Samsung Electronics Shin-Etsu Handoutai Shinko Electronics SPIL Sumitomo Bakelite
Grenoble Ecole de Management MEDFORIST Workshop
Sumitomo Metal Texas Instruments TOK Tokyo Electron Toppan Toshiba TSMC UMC Winbond Xilinx
32/33
A. Dogac
33/33