The program will standardize and automate the business processes for work order management across the supply chain in order to reduce the human error in handling work orders and enable efficient planning for outsource manufacturing.

Program Objectives

• To develop work order management standards that meet the requirements for order release control and exchange of technical data.
• Improve the accuracy of manufacturing work order
• Speed up the delivery of manufacturing work orders.
• Enable efficient planning processes for outsourced manufacturing.
• Build to order

Definition of Work Order

• Release Signal: When PO is in place, manufacturing instructions are ready, the main purpose of the work order is to control the release of manufacturing orders to the manufacturers.
• Technical Data: In situations where engineering instructions and/or technical data are required, the work order also helps the manufacturer to exchange technical data with its customers.

Target Supply Chain

2 main areas:

• IDM/Fabless ® Foundry (weekly demand in specific device names and/or mask version sets)
• IDM/Fabless/Foundry ® Test/Assembly (by lot assembly instruction or testing spec.)

Value Proposition

Initial deployment of work order PIPs by SM Board companies as early adopters. These implementations will enable the milestone participants to increase their connections with subsequent trading partners.

Manufacturing Work Order Management Potential Benefits

• Supply Chain Velocity: (assembly instruction arrives before wafer/die, and EQ setup/material is ready when wafer/die arrives at the shop floor)
• Standard work order attributes across the supply chain: (Information sharing across the supply chain)
• Enable more efficient planning processes for outsourced manufacturing.

Issues or Risks

• The team needs to move fast to reduce the schedule impact by the holiday season (Thanksgiving, Christmas, New Year, and Chinese New Year).

Roadmap

• 11/2001 Form the team
• 11/2001 Kick-off
• 11/2001 ~ 2/2002 Requirement analysis & PIP development
• • 4/2002 New PIPs released for vote
• • 5/2002 ~ 8/2002 Validation
• • 9/9/2002 PIPs on production
• • Q1/2003 Roll out to more than 2 partners by each company