RosettaNet

Nan Ning

Helsinki University of Technology

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

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

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.

PIP (cont)

• Apply to the following core processes– 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.

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

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.

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

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)

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

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

Before

IntelIntel SHINKO(email/spreadsheet) Allocation/Forecast

(fax) Allocation/Forecast Response

(fax)Delivery Schedule

(fax)PO Request/PO Change

(fax/email)Shipping Information Inquiry

(fax/email)Shipping Information

(paper) Invoice

Web:Consignment Mgmt Report

Web:Payment Remittance

ERP Internal IS

Phase One

• Order Management and Shipment:– 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

Phase One (2)

IntelIntel SHINKO(email/spreadsheet) Allocation/Forecast

(fax) Allocation/Forecast Response

(fax)Delivery Schedule

PIP 3A4/8 PO Request/Change

(fax/email)Shipping Information Inquiry

PIP 3B2 ASN

(paper) Invoice

Web:Consignment Mgmt Report

Web:Payment Remittance

ERP Internal IS

Phase Two (2003-2005)

• Completed Forecast to Cash:– 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

Phase Two (2)

IntelIntel SHINKOPIP 4A2/3 Notify of Forecast 2003

PIP 4A5 Reply of Forecast 2003

PIP 4A2/3 Notify of Forecast 2003

PIP 3A4/8 PO Request/Change

(fax/email)Shipping Information Inquiry

PIP 3B2 ASN

PIP 3C3/4 Invoice

PIP 4C1 Inventory Report 2003-4

PIP 3C6 Remittance Advice 2003-4

ERP Internal IS

Further Information

• RosettaNet web site:

http://www.rosettanet.org