1. Helsinki University of Technology
RosettaNet
Nan Ning
Helsinki University of Technology

2. RosettaNet History and organization
Named after the Rosetta Stone, which, carved with the same message in three languages, led to the understanding of hieroglyphics
Founded in June 1998 by 40 leading IT organizations
Non-profit consortium
Members of more than 400 of the world's leading Information Technology (IT), Electronic Components (EC), Semiconductor Manufacturing (SM) and Solution Provider (SP) companies

3. RosettaNet Goals
working to implement standards for supply-chain (manager-supplier) transactions on the Internet
to standardize labels for elements like product descriptions, part numbers, pricing data, and inventory status
to implement many of its goals through XML

4. PIPs Short for RosettaNet Partner Interface Processes
Specialized system-to-system XML-based dialogs
Define business processes between trading partners
Each PIP specification includes
a business document with the vocabulary
a business process with the choreography of the message dialog
structure and content format of the business documents exchanged (XML DTDs and guidelines)
the time, security, authentication and performance constraints on the document interactions.

5. PIP (cont) Apply to the following core processes Examples
Administration
Partner, Product and Service Review
Product Introduction
Order Management
Inventory Management
Marketing Information Management
Service and Support
Manufacturing
Examples
purchase order management
distribution of new product information.

6. RNIF Short for RosettaNet Implementation Framework
Problem: format of PIP varies on per PIP and the specific business document type basis
Provides the packaging, routing, and transport of RosettaNet PIP message and business signals using XML
Provides implementation guidelines for creating interoperable software applications components that facilitate the execution of Partner Interface Processes (PIPs)
Core Specification provides exchange protocols for quick and efficient implementation of RosettaNet standards

7. RNIF 2.0 Core specification is the RosettaNet Business Message
Includes the authentication, authorization, encryption and non-repudiation requirements
Essential for conducting secure electronic business over the Internet
Specifies the use of MIME multipart/related type for the basic enveloping construct to pack
Supports HTTP(S) and SMTP protocols with provision for future addition of other transfer protocols like FTP.

8. RosettaNet Dictionaries
Common vocabulary for conducting e-business
Reduce confusion in the procurement process due to each company's uniquely defined terminology
Are classified as Business and Technical Dictionaries.
RosettaNet Business Dictionary
Designates the properties for defining business transactions between trading partners
RosettaNet Technical Dictionary
provides properties for defining products and services

9. RosettaNet Business Dictionary
Defines the Business Properties, Business Data Entities, and Fundamental Business Data Entities in PIP Message Guidelines, which are used in basic business activities between trading partners
Those properties are:
Business Properties (e.g. business address)
Business Data Entities (e.g. ActionIdentity)
Fundamental Business Data Entities (e.g. BusinessTaxIdentifier, AccountNumber)
Etc.
Only one business dictionary that encompasses all supply chains (EC, IT etc)

10. RosettaNet Technical Dictionary (RNTD)
Defines properties for products, components/devices and services that span the EC, IT and other supply chains
Formerly distinct EC Technical Dictionary and the IT Technical Dictionary are now integrated into the RosettaNet Technical Dictionary
Latest version RNTD 3.0 released in March 2003

11. Example
Project: Intel and Shinko use RosettaNet standards to build forecast-to-cash procurement process
Featured Partners
Intel, semiconductor manufacturer
Shinko, components supplier/assembly subcontractor
Business Challenges
Replacement of manual procurement system; establishment of 100% electronic forecast-tocash procurement process; support of Intel'sB2Bi strategy

12. Before Intel SHINKO Intel Internal IS ERP
( /spreadsheet) Allocation/Forecast
SHINKO
Intel
(fax) Allocation/Forecast Response
(fax)Delivery Schedule
(fax)PO Request/PO Change
Internal IS
ERP
(fax/ )Shipping Information Inquiry
(fax/ )Shipping Information
(paper) Invoice
Web:Consignment Mgmt Report
Web:Payment Remittance

13. Phase One Order Management and Shipment: Business Benefits
PIP 3A4: Request Purchase Order
PIP 3A8: Request Purchase Order Change
PIP 3B2: Notify of Advance Shipment
Business Benefits
50% reduction in manual workload at Shinko; total elimination of substantial yearly autofax costs; order management throughput time reduced from 24 hours to less than 1 hour; 100% errorfree purchase order processing

14. Phase One (2) Intel SHINKO Intel Internal IS ERP
( /spreadsheet) Allocation/Forecast
SHINKO
Intel
(fax) Allocation/Forecast Response
(fax)Delivery Schedule
PIP 3A4/8 PO Request/Change
Internal IS
ERP
(fax/ )Shipping Information Inquiry
PIP 3B2 ASN
(paper) Invoice
Web:Consignment Mgmt Report
Web:Payment Remittance

15. Phase Two (2003-2005) Completed Forecast to Cash: Business Benefits
PIP 3C3: Notify of Invoice
PIP 3C4: Notify of Invoice Reject
PIP 3C6: Notify of Remittance Advice
PIP 4A2: Notify of Embedded Release Forecast
PIP 4A3: Notify of Threshold Release Forecast
PIP 4A5: Notify of Forecast Reply
PIP 4C1: Distribute Inventory Report
Business Benefits
81% annual efficiency gain at Shinko from Phase Two PIPs alone, representing 1,352 saved hours; 100% errorfree forecast-to-cash procurement process; 47% forecast-related lead time reduction from real-time forecasting; improved supply chain visibility; support of Intel’s B2Bi strategy

16. Phase Two (2) Intel SHINKO Intel Internal IS ERP
PIP 4A2/3 Notify of Forecast 2003
SHINKO
Intel
PIP 4A5 Reply of Forecast 2003
PIP 4A2/3 Notify of Forecast 2003
PIP 3A4/8 PO Request/Change
Internal IS
ERP
(fax/ )Shipping Information Inquiry
PIP 3B2 ASN
PIP 3C3/4 Invoice
PIP 4C1 Inventory Report
PIP 3C6 Remittance Advice

17. Further Information
RosettaNet web site: