Grenoble Ecole de Management MEDFORIST Workshop RosettaNet

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

MEDFORIST Workshop
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
A. Dogac
Grenoble Ecole de Mana
2/33
Partner-to-Partner
Electronic Business Interface
Company B
Company A
Company Specific
processing
Internet & XML
SAP
ERP
Company Specific
processing
Oracle
ERP
Translate
from
Company A
system data
set to
RosettaNet
standards
A. Dogac
RosettaNet defines processes

and a framework for how data
gets passed over the Web and
certain handshake criteria
Translate from
RosettaNet
standards
to Company B
system data set
3/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
A. Dogac
4/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
A. Dogac
5/33
RosettaNet Framework
Partner Interface Processes (PIPs)

A Master Dictionary
Business Dictionary
Technical Dictionary
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
A. Dogac
7/33
Some Example PIPs

Cluster:
Product Information
PIP 2A1:
PIP 2A2:
PIP 2A9:
Distribute New Product Information

Query Product Information
Query EC Technical Information
Cluster:
Order Management
PIP 3A2:
PIP 3A3:
PIP 3A4:
PIP 3A6:
PIP 3A7:
PIP 3B2:
PIP 3B4:
Request Price and Availability

Transfer Shopping Cart
Manage Purchase Order
Distribute Order Status
Notify of Purchase Order Acceptance
Notify of Advance Shipment
Query Shipment Status
Cluster:
Inventory Management
PIP 4B1:
Allocate Inventory
Cluster:
Marketing Information Management
PIP 5C1:
PIP 5C2:
PIP 5C3:
Distribute Product List

Request Design Registration
Request Design Win
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
As an example of the PIPs in this segment PIP3A4: Manage

Purchase Order
A. Dogac
9/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
A. Dogac
10/33
RosettaNet Business Process Flow

Diagram for PIP3A4
A. Dogac
11/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.
A. Dogac
12/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
A. Dogac
13/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
A. Dogac
14/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
A. Dogac
15/33
Business
Customer
Processes
Supplier
Private process A
Public process
(Company -specific) (Standard)
Process
PO
Receive PO
Send PO
Customer
Figure provided by Vitria Systems
Request
P
O
Select
Supplier
Generate
RFQ
Send
Send PO
PO
Receive
Receive PO
PO
Acknowledge
Acknowledge
Public process Private process B

(Standard)
(Company
Process
-specific)
Send PO
Sales
Supplier
Order
Receive
Receive PO
PO
Receive
Receive PO
PO
Send
Send PO
PO
Acknowledge
Acknowledge
Send
RFQ
Select RFQ
Response
Send
PO
Close
A. Dogac
Check
Check
Customer
Customer
Check
Check
Credit
Credit
Check
Check
Availability
Availability
Receive
Receive PO
PO
Response
Response
Send
Send PO
PO
Response
Response
Acknowledge
Acknowledge
Send
Send PO
PO
Response
Response
Receive
Receive PO
PO
Response
Response
Acknowledge
Acknowledge
CRM
SCM
Create
Create Sales
Sales
Order
Order
Send
Send PO
PO
Response
Response
Close
Close
ERP
16/33
E-Business Exchange
Telephone
Telephone
eBusiness Process
Dialog
DIALOG
PIP
Grammar
Framework
Words
Dictionary
Alphabet
XML
Sound
Internet
human-to-human
Partner-to-Partner
business exchange
eBusiness exchange
A. Dogac
RosettaNet
Business Process
Process
Business
Ecom Application
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
An Example Public Business Process

Request Price and Availability 1
PIP 3A2
2
Request Purchase Order

PIP 3A4
3
Notify of Invoice PIP 3C3

6
Notify of Shipment Receipt

PIP 4B2
7
Notify of Billing PIP3C5

5
Transportation Request
PIP3B1
A. Dogac
Notify of Shipment Status

PIP3B3
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)
A. Dogac
20/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)
A. Dogac
21/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
A. Dogac
22/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
A. Dogac
23/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
A. Dogac
24/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
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
RosettaNet Implementation
Implementation
Partners
Results
Successes
Up and running in six
Reduced a 5-day batched delivery cycle
Arrow &
Carrier
weeks
to overnight; results in inventory

reduction, improved customer satisfaction
Bourns &
TTI
Implemented PIP 3A2 New process converted access to

in two weeks
inventory information from a weeks
delay to real-time data; improved
customer service
Compaq &
Delta
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
Implemented PIP 3A4

and PIP 3A7
Automated process reduced the cycle

time for order processing between the
companies
(Taiwan)
Intel & WPI

(Taiwan)
implementation
Expected to shorten lead time
Samsung & First
between Korea- and
A.
Dogac
Sony
Japan-based partners
28/33
RosettaNet Partners
Trade
Associations
Standard
Bodies
Government
Agencies
Solution
Providers
A. Dogac
Supply Chain
Companies
29/33
Information Technology (IT)

Hewlett-Packard
Supply Chain
Board
3Com
Arrow
Electronics
Avnet
Cisco Systems
Compaq
CompUSA
Dell
Federal Express
GSA
A. Dogac
IBM
Ingram
Insight
Intel
Lucent
Technologies
NEC
Netscape
Office Depot
Pioneer
Quantum
SAP
Siemens
Solectron
Tech Data
Trilogy
UPS
30/33
Electronic Components
(EC)
Agilent
Intel
Pioneer
Altera
Kemet Board Samsung
Supply Chain
Solectron
Arrow Electronics
Avnet
AVX
Bourns
Cisco Systems
FCI
Future Electronics
Hitachi
IBM
A. Dogac
Lucent Technologies
Memec
Micron Technology
Molex
Motorola
National
Nokia
NEC
Philips
Semiconductors
Sony
STMicroelectronics
Texas Instruments
Toshiba
Tyco Electronics
Xilinx
31/33
Semiconductor Manufacturing
(SM)
Sumitomo Metal
Air Supply
Products &
Micron
Technology
Chain
Board
Texas Instruments
Chemicals
Agilent Technologies
Amkor Technology
Applied Materials
ASE
Chartered
Semiconductor
Intel
JSR
LSI
Lucent Technologies
A. Dogac
Motorola
National
Semiconductor
NEC
Philips
Semiconductors
Samsung Electronics
Shin-Etsu Handoutai
Shinko Electronics
SPIL
Sumitomo Bakelite
TOK
Tokyo Electron
Toppan
Toshiba
TSMC
UMC
Winbond
Xilinx
32/33
Thank you very much for your

attention!
A. Dogac
33/33

Grenoble Ecole de Management MEDFORIST Workshop RosettaNet

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Grenoble Ecole de Management MEDFORIST Workshop RosettaNet

Uploaded by

Copyright:

Available Formats

Grenoble Ecole de

Grenoble Ecole de Management

Founded in 1998, RosettaNet is an independent,

XML-based standard electronic commerce interfaces

The RosettaNet consortium includes IT companies

Grenoble Ecole de Mana

Internet & XML

RosettaNet defines processes

Grenoble Ecole de Mana

Where the name RosettaNet

crucial breakthrough in the

Grenoble Ecole de Mana

Where the name RosettaNet

represent a single text in three different

Grenoble Ecole de Mana

Partner Interface Processes (PIPs)

Grenoble Ecole de Mana

Partner Interface Processes (PIPs)

Grenoble Ecole de Mana

Some Example PIPs

Distribute New Product Information

Request Price and Availability

Marketing Information Management

Distribute Product List

Grenoble Ecole de Mana

For example, Cluster 3 is Order Management and Segment

As an example of the PIPs in this segment PIP3A4: Manage

Grenoble Ecole de Mana

PIP 3A4: Manage Purchase

Buyer creates a Purchase Order and sends it to the Seller

Seller receives the Purchase Order and returns a Purchase

The Buyer determines success or failure based on message

Grenoble Ecole de Mana

RosettaNet Business Process Flow

Grenoble Ecole de Mana

Contains information about the trading

Business Properties (e.g. business address),

There is only one business dictionary that

Grenoble Ecole de Mana

RosettaNet Technical Dictionary

Provide properties for describing products and

Grenoble Ecole de Mana

Doing Business through

In order to do electronic business within the RosettaNet

Grenoble Ecole de Mana

Doing Business through

An electronic business process includes both

Grenoble Ecole de Mana

Figure provided by Vitria Systems

Public process Private process B

Grenoble Ecole de Mana

Public Business Processes: The process among

RosettaNet defines and fixes Public Business

Private Business Processes: The business

Grenoble Ecole de Mana

An Example Public Business Process

Request Purchase Order

Notify of Invoice PIP 3C3

Notify of Shipment Receipt

Notify of Billing PIP3C5

Notify of Shipment Status

Grenoble Ecole de Mana

Consider, for example, a scenario where a buyer