RosettaNet Applications in
Semiconductor Industry
1
Outline





RosettaNet Organization
RosettaNet Standard
PIPs Examples
General RosettaNet Applications
Case Sharing




Semiconductor Industry
Infrastructure
Dancing scenario
Open Issues
2
RosettaNet Organization
 Established on 1998
 www.rosettanet.org
 Key sponsors, that’s why applied in global
 Intel, Motorola, HP, Nokia, Cisco, Seagate, Sonly, Samsung,
Toshiba, Fujitsu, IBM, Infineon, Philips
 It’s a virtual organization
 Few formal staffs, about 20
 On loan resource from sponsors
 Board
 Information Technology (IT)
 Electronic Component (EC)
 Semiconductor (SM) since 2000, SPIL is the initiate member along
with TSMC, UMC, and ASE
 Solution
 Score Card System
3
RosettaNet Standard
 RNIF (RosettaNet Implementation Framework) 2.0
 PIP (Partner Interface Process)
 Business flow
 Specified message contents
 RNTD (Technical Dictionary)
4
PIPs Examples
PIP Code
Business Flow
Message Content
5
Real Case
PIPs Examples
PIP Code
Business Flow
Message Content
6
Real Case
PIPs Examples
PIP Code
Business Flow
Message Content
3A1 3: Cluster; A: Segment; Number: A sequence number
Each process has a unique PIP code
7
Real Case
PIPs Examples
PIP Code
Business Flow
Message Content
Real Case
7B1 is a one way PIP along with one acknowledgement
Acknowledgement
8
PIPs Examples
PIP Code
Business Flow
Message Content
•3A4 is a two way PIP along with one ack
•Business flow can be decomposed by multiple PIPs
9
Real Case
PIPs Examples
PIP Code
Business Flow
Message Content
Real Case
SPEC
DTD
PIP, data structure
1
0..1
0..n
1..n
Required. Only once
Optional. If having value, only once
Optional, If having value, allow multiple times
Required, allow multiple times
Dictionary Usage
XML based sample
10
PIPs Examples
PIP Code
Business Flow
Message Content
Project Kick off
Mapping SPEC
Events Mapping
11
Real Case
General RN Applications
Purchase Order
Receive / Confirm
Wafer/Goods Receive
Work Order Create
In Process WIP Update
3A4/8 Purchase Order Related (Vendor / Customer)
3B2 Notify Of Advance Shipment (Customer/ Vendor )
7B5 Production Work Order (Customer)
7B1/3D8 Distribute Work In Process (Customer)
Purchase Order
Issue/ Confirm
Shipping Notification
Production Order
Release
WIP Management
Testing/Inkless file
Data Application
7C7 Testing Result Data (Not Available)
Testing Data
Sharing / Analysis
Inventory Status
4C1 Distribute Inventory Report (Not Available)
Consigned Inventory
Management
Shipment Allocation
3B2 Notify Of Advance Shipment (Customer)
Shipping Notification
3B2 Notify Of Advance Shipment (Customer)
Account Receivables/
Cash
3C3/4/6/7 Invoicing and Payment (Not Available)
12
Shipping Planning
Shipping Confirmation.
Account Payable/
Remittance
Case Sharing
Semiconductor Industry
Foundry1
Foundry2
Probing1
Probing2
Foundry3
Foundry
Bumping
Infrastructure
Assembly
1
Assembly
2
Assembly
3
Probing
Scenario Cases
Testing1
Testing2
Virtual Factory
Facing different partners
Assembly
Stock Point
13
Testing
SMT
Testing
Case Sharing
Semiconductor Industry
Traditional Process
Infrastructure
Scenario Cases
Integration in one
Company
Disintegration by
Multiple Companies
•Design
MediaTek
•Foundry
TSMC/UMC
•Probing
Intel
KYEC
•Assembly
ASE/SPIL
•Testing
ASE/SPIL
14
Case Sharing
Semiconductor Industry
Infrastructure
Business Flow
XXX
Data
Warehouse
Scenario Cases
Customer
Web
Customer
Online Query
Auto Send
ERP
E-Mail
PC
Purchase Order
(Oracle R11i)
Work Order
MES
FTP
Wafer Shipping
(Promis)
Assembly *1
Bumping *1
Testing *1
Backend
System
B2Bi
EDI
WIP and Inventory
B2Bi
(webMethod)
CIM
Shipment
(By Site)
Internet
Internet
15
Open Issues
•Business flow and system integration
(1) Even RosettaNet is a standard, but each customer
has its own definition, especially in transaction base
data integration.
(2) There is still lack of mechanism for data revision
(3) Some changes will impact business process
(4) It needs a well-constructed infrastructure, or it is
difficult to meet customer’s requirement
(5) Even after go live, we can still found some scenario is
out of design. User’s involvement is very important, or
it will bring more problems.
(6) EEI is a trend, most customer has this kind of
requirement, especially IDM.
16
Open Issues
•Project Management
1. High level supports
2. Project members are complex, and they should join
project in different stage. For example, Project
manager, business analyst, end user, backend
system analyst, programmer, B2Bi expert, Network
engineer et al  No body can understand all things
3. Global collaboration Only voice, not FTF meeting.
If considering the language capability, it brings more
challenge during implementation. It is easy to
confuse requirement.
4. Time zone difference Need to well arrange or will
delay over 3 days
17