1 RosettaNet Applications in Semiconductor Industry

2 Outline  RosettaNet Organization  RosettaNet Standard  PIPs Examples  General RosettaNet Applications  Case Sharing  Semiconductor Industry  Infrastructure  Dancing scenario  Open Issues

3 RosettaNet Organization  Established on 1998   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

4 RosettaNet Standard  RNIF (RosettaNet Implementation Framework) 2.0  PIP (Partner Interface Process)  Business flow  Specified message contents  RNTD (Technical Dictionary)

5 PIPs Examples PIP CodeBusiness FlowMessage ContentReal Case

6 PIPs Examples PIP CodeBusiness FlowMessage ContentReal Case

7 PIPs Examples 3A1 3: Cluster; A: Segment; Number: A sequence number Each process has a unique PIP code PIP CodeBusiness FlowMessage ContentReal Case

8 PIPs Examples Acknowledgement 7B1 is a one way PIP along with one acknowledgement PIP CodeBusiness FlowMessage ContentReal Case

9 PIPs Examples 3A4 is a two way PIP along with one ack Business flow can be decomposed by multiple PIPs PIP CodeBusiness FlowMessage ContentReal Case

10 PIPs Examples 1Required. Only once 0..1Optional. If having value, only once 0..nOptional, If having value, allow multiple times 1..nRequired, allow multiple times SPEC DTD PIP, data structure Dictionary Usage XML based sample PIP CodeBusiness FlowMessage ContentReal Case

11 PIPs Examples PIP CodeBusiness FlowMessage ContentReal Case Project Kick off Mapping SPEC Events Mapping

12 General RN Applications 3A4/8 Purchase Order Related (Vendor / Customer) Purchase Order Receive / Confirm Purchase Order Receive / Confirm 3B2 Notify Of Advance Shipment (Customer/ Vendor ) Shipping Notification Wafer/Goods Receive In Process WIP Update 7B1/3D8 Distribute Work In Process (Customer) 4C1 Distribute Inventory Report (Not Available) Inventory Status 7B5 Production Work Order (Customer) Work Order Create Production Order Release Production Order Release 3B2 Notify Of Advance Shipment (Customer) Shipping Notification Shipping Confirmation. Testing/Inkless file Data Application Testing/Inkless file Data Application 7C7 Testing Result Data (Not Available) Purchase Order Issue/ Confirm Purchase Order Issue/ Confirm WIP Management Testing Data Sharing / Analysis Testing Data Sharing / Analysis 3B2 Notify Of Advance Shipment (Customer) Shipment Allocation 3C3/4/6/7 Invoicing and Payment (Not Available) Account Receivables/ Cash Account Receivables/ Cash Account Payable/ Remittance Account Payable/ Remittance Consigned Inventory Management Consigned Inventory Management Shipping Planning

13 Case Sharing Semiconductor IndustryInfrastructureScenario Cases Foundry1 Foundry2 Foundry3 Probing1 Probing2 Assembly 1 Assembly 2 Assembly 3 Testing1 Testing2 BumpingFoundry AssemblyTesting Stock Point ProbingTestingSMT Virtual Factory Facing different partners

14 Case Sharing Semiconductor IndustryInfrastructureScenario Cases Design Foundry Probing Assembly Testing Intel MediaTek TSMC/UMC KYEC ASE/SPIL Integration in one Company Disintegration by Multiple Companies Traditional Process

15 Case Sharing Semiconductor IndustryInfrastructureScenario Cases Data Warehouse Warehouse ERP (Oracle R11i) MES(Promis) CustomerWeb FTPEDIB2Bi(webMethod) B2Bi BackendSystem CIM (By Site) Business Flow Customer Online Query Auto Send Purchase Order Work Order Wafer Shipping WIP and Inventory Shipment Internet PC Assembly *1 Bumping *1 Testing *1 XXX

16 Open Issues (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. Business flow and system integration

17 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