ENP-00094 Rev04 New Product Introduction Process 140303

Document Confidential Level: 1
New Product Introduction Process
研发流程
ENP-00094
Revision History
Version
Author Description of Change Date of Issue
No.
Parts based LCM change to Project based
L C M i n t r o d u c e ; A d d g a“t toe r e v i e w o n
01 Shirley Zhang 13-Nov.-12
Beta”; change the doc number from FIB-QI-
0601 to ENP-00094
Vicky Carl/Shirley U p d a t e q u a l i t y r e s p o n s i b i l i t y , c l a r i31-Mar-13
fy use of
02
Zhang CAPs, clarify team assignments
D e l e t e a s s e s s m e n t p h a s e ; S i m p l i f y
requirem t oe nBt e t a C A ; C l e a r l y d e f i n e d
03 Shirley Zhang 1-July-13
delivery qty limitation before CA. Change to
“RT 1000hr pass” to CA.
04 Shirley Zhang 1. Replace Projcop as EPIE. 3-Mar-14
2. A d d e“Pd R ” B d e f i n i t i o n a n d e x p a n d
“B u y i n” o f g a t e r e v i e w t o m u l t i p l e g a t e
reviews.
3. Added “Temporary deviations”.
4. Added Risk management list in kick off.
________________________________________________________________________________________________________
Source Photonics Proprietary and Confidential, Do Not Copy or Distribute Page 1 of 22
Controlled Electronic Version. 24hrs Obsolete when printed out without authorization. Last printed 3/11/2014 02:52:00 PM
Document Confidential Level: 1
5. A d d e d“D F M” d e s i g n f o r m a n u f a c t u r i n g
requirement at early design stage.
6. Correct shipment restriction qty in Beta.
7. Added MER requirement from PE at CA.
8. D e f i n e d L e s s o n L e a r n t a s r e q u i r e m e n t
in GA gate review
________________________________________________________________________________________________________
Ref. No.: ENP-00094
Revision： 04 R&D Process

Effective Date: Mar 3, 2014
TABLE OF CONTENTS
1. Objective/目的.....................................................................................................................3
2. Scope of Application/适用范围........................................................................................3
3. Definition/定义.....................................................................................................................4
4. Responsibility/职责............................................................................................................5
5. Working Procedure General/工作程序...........................................................................5
5.1 CONCEPT/Planned...........................................................................................................10
5.2 Alpha...................................................................................................................................11
5.3 Beta Stage..........................................................................................................................15
5.4 Controlled Availability-CA.............................................................................................19
5.5 General Availability-GA...................................................................................................21
5.6 Other Phases....................................................................................................................21
6. Relevant Documentation and Record/相关文件和记录............................................22
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

1. Objective/目的
This process is established to standardize research and developm
p r o c e s s o f a l l p r o j e c t s , t o c l a r i f y t h e w o r k i
departments and to provide practical methods and st
development.
为规范公司项目研发过程，明确各相关部门的工作职责，为新产品开发提供一套切
实可行的方法及步骤，特制定本流程。
2. Scope of Application/适用范围
LCM requirements apply to all FG Items including OSAs or TOs that we sell.
生命周期流程适用于包括OSA在内的所有产成品。
Any parts that do have an NPD ID that is not zero should use Project Bas
LCM.
NPD ID不为零的所以产品部件都应使用基于项目的生命周期流程。
Parts with NPD ID zero can keep the Old Part Lifecycle system. But we will not
create new part numbers for this unless it is from CAP.
NPD ID为零的产品部件可以保留原来的生命周期，但不能再为该部件创建新的
P/N,除非它是CAP流程中的部件。
A l l F G i t e m s r e l e a s e d b y C A Ps m u s t b e l i f e c yc l e “P ro to ty p e ” i f N P D I D i s n
zero, including “CAP w/ EEPROM, label change only”. First part must go through
CAP validation process. Parts are on ship-hold in WIPStatus till project linkage.
通过 C A P流程发行的所有 N P D I D
不为零的产成品，生命周期都应是
“Prototype”，包括只更改 EEPROM, 标签的CAP。首件要走CAP认证流程。零部
件在与项目建立关联前在WIPStatus中应是暂停发货状态。
CAP validation must occur before a PN can be linked to
validation the customized part number is linked to the project at the
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

lifecycle. CAP number is added to customization documents for

number. If requested customizations are so extensive that existing project LCM
a c t i v i t i e s d o n o t a p p l y, w e w i l l c r e a t e a n e w p r o j e c t r a t h e r t h a n
perform all LCM activities and gate reviews defined here.
CAP认证要在链接PN前发起，在认证通过后，该客定PN才可以连接到当前的项目
中。如果需要连接的客定PN因为特殊需要与当前项目的生命周期不匹配，可以新
创建一个项目对它进行管理。
3. Definition/定义
FG: Finished Goods
PRD: Product Requirement Definition
EVT: Engineering Verification Test
DVT: Design Verification Test
RT: Reliability Test
PMR: Pilot Run Report
CAP: Customization Approval Process
PD: Product Development
PLM: Product Line Management
PMG: Product Management Group
XDL: Cross Department Leader
NPD: New Product Development
NPQ: New Product Quality
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

4. Responsibility/职责
5. Working Procedure General/工作程序

R&D Process/研发流程
This R&D Process is established to show the different stages of new R&D project
developmentprocess by describing a whole and complete project lifecycle, from
p r o j e c t k i c k o f f , A s s e s s m e n t , d e t a i l e d d ebsai gt cn h,o sf m
pai l lol t r u n t o m a s s
production, in which the following stages are included:
此研发流程旨在说明新产品引入过程的不同阶段，从产品启动、策划开始到小批量
试产转入量产将经历如下产品生命周期阶段：
a) Alpha
b) Beta
c) Controlled Availability-CA
d) General Availability-GA
Thesm
e i l e s t o na er e
s the main checkpoints in executing new R
process, aiming at effectively monitoring the process and completion quality
the project. Each milestone requires for project review including evaluatio
marketing, technology, finance, etc.
里程碑作为执行新产品研发流程的主要检查点，目的在于有效监控项目的进程和完
成质量。在每一个里程碑均需进行项目评审，包括市场、技术、财务等方面的内容
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

Project based LCM:

• Simplify parts to platform based;
• Visibility key and successful design in project;
• Quality product with significant teams’ involvement, especially on Sourcing, PE
and QA.
• Delivery restriction for PN in wrong stage
产成品零部件生命周期，项目生命周期：零部件简化为项目中的基于平台的主要设
计或成功设计，一些主要的部门参与产品的流程，如Sourcing, PE和QA。限制了
PN在错误状态时的出货。
There are 5 lifecycles used in Agile/Oracle for part numbers under project LCM
 ‘Open’: this status is similar to FG Assessment. There is no BOM and
part cannot be built and shipped
 ‘Prototype’: there is a BOM but the part has not been reviewed or did not yet
meet the requirements to be linked to the project. Parts are held in WIPStatus
until review is complete and parts can be linked to project
 ‘Project’: the part has been reviewed and met all requirements to be linked to
the project. Note that key pivots and other reports will show part lifecycle that
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

matches the project lifecycle for ease of use.

 FG Not Preferred: Part is being phased out
 ‘FG Inactive’: Part is EOL.
在Agile 和Oracle系统中，项目LCM中的零部件号共有5个生命周期
 Open: 类似于FG Assessment，这种状态时零部件没有BOM,也不能进行生产或
发货
 Prototype：零部件下有BOM, 但没完成相应的审核流程，或不符合要求不能连接
到项目中。审核流程完成前，零部件保持WIP状态，完成后才可链接到项目中
 Project：零部件审核完成，并符合连接到项目中的所有要求。注意：key pivots
和其他报告会显示与项目生命周期匹配的零部件生命周期。
 Not Preferred: 零部件即将生命周期终止。
 FG Inactive：零部件生命周期终止。
All LCM documents for NPD-ID not 0 will be stored under project, not under any
specific part number, no 1493 BOM.
Parts will have a gate release process to link them to a project. Categorized by:
 Use EPIE to compare new BOM, test processes yields and cost to t
a lre a dy li n ke d wi th p ro j ect s i n th e vi ew o f simi l a r e no u g h to b e j oi n t p ro j e
based lifecycle system.
 Meet all requirements to higher stage.
 Meet and pass CAP validation process for customized product.
今后所有的LCM文件都将保存在project中，不再单独的P/N和1493BOM中保存
产品零部件通过gate release流程与项目建立关联，如下：
 使用EPIE将新BOM和测试工艺，良率，成本与已经和项目建立关联的BOM和工
艺进行对比
 符合进入下一阶段的所有要求
 通过定制品CAP认证流程
EPIE:
 EPIE tool created for comparing new BOM and test processe
already linked with projects. All ECNS linking parts to projects must have this
attached.
 The location of the tool is on desktop of hq-termsvr
 Details of using this tool are addressed in this example: (Note there ar
tabs of interest in the excel file)
EPIE介绍
 系统中开发了一种新工具，用于新BOM，新测试工艺和与项目连接的BOM,工艺
之间的对比。为零部件和项目建立关联的所有ECN都应上传此工具。
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

 工具位置：hq-termsvr的桌面
 这个工具的详细使用步骤在如下的例子中展示：（注意:excel中有2页内容）
• New component selection & Sourcing Strategy in Product Development: 新物料选型

及Sourcing策略：
 P D s e l et sc k e y e l e c t r i c a l p a r t s w i t h i t s d ar et av si ehw
ea;ept p l yf o r n e w p a r t
samples from Sourcing if necessary.
PD识别关键电子器件，并向Sourcing申请新物料样品。
 Sourcing evaluate
s the cost roadmap, vendor
’s supply capability, LT, reliability
a n d R o H S o f t h e n e w p a r t s , a s a b u s i n e s sF oi nr pCuR
t tpor oPj,D
e c. t s
sourcing to evaluate cost-reductions w/o design changes.
Sourcing开始评估新物料的阶梯成本，交期，可靠性和RoHS情况，供应商的持续
供货能力等，给PD提供商务方面的信息支持。对于CR项目，Sourcing需评估在不
更改设计方案的前提下的成本降低。
 F A E i s d o n e a f tP
eDr completes new material sample verification with
result of EVT(if required)
. NPQ is a partner with SQE coordinating first article
approvals.
FAE在PD完成新物料样品认证及EVT测试通过后，PD开始发起FAE的制作。NPQ
与SQE一起参与物料首件的确认。
 PRB
 In the event that the team cannot reach a unanimous decision at gate
review meeting, decision is escalated to the Product Review Board (PRB)
 当项目转阶段的内部评审会不能得到一致的反馈时，就需要上报给产品评审
委员会作裁定。
 PRB consists of top management level Ops, PLM, R&D and NPQ
 产品评审委员会由运营，市场部，研发和新产品导入质量部的最高层组成。
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

 PRB will meet and decision will be recorded on ENF-00108

 产品评审委员会随后将讨论，记录在ENF-00108上的各分歧点，以作出最后
决定。
 If PRB decides to advance lifecyle, normal LCO process will be followed
with the inclusion of the completed ENF-00108
 如果产品评审委员会决定同意该项目转入下一开发阶段，需要走正常的
LCO 转生命周期流程，并附上完整的ENF-00108。
 Temporary deviations 临时变更
 In the event that there are urgent orders and we have not completed all
gate review items, a temporary deviation may be issued for specific part
numbers in a project.
 如果有紧急定单需要生产和交付，但是相应的阶段评审还没有完成，此时就
需要触发一个临时变更，这个变更可以对一个项目中的某具体产品型号。
 Any requirements specified by customer must be complete
 任何客户的特殊要求都需要满足和完成。
 PRB approval of deviation is required
 产品评审委员会需要对这个临时变更作审批。
 Deviation to shipment restrictions will be created for a specific number of
units and end on a specific date
 对于发货限制的临时解禁可以针对某一个具体产品型号，具体生效的时间周
期等。
5.1 CONCEPT/PLANNED
5.1.1 Core Tasks：核心职责
• Justify investment 项目投资可行性论证
• Review Business Case 评审市场信息
• Establish High Level Requirements 建立产品高层设计规范
• Create Team 组建项目团队
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• NPD-ID in Concept/Planned
5.1.2 Detailed Accountability 具体职责

• Create Teams and set assigned personnel in DWM. 项目组创建，并完成在DWM
系统中的设置。
• When a DWM project goes from a concept state to a full kickoff, PMG will create
this project in Agile with a numbering scheme: NPD-xxx, where xxx is the NPD
ID.
DWM项目从概念阶段变成全面启动时，PMG在Agile中创建项目，项目的编号规则
是NPD-xxx，其中的数字就是NPD ID。
5.1.3 Deliverables 输出
– Kick off Meeting Minutes. (Attach in DWM). 项目启动会议记录需要挂在DWM中.
– Product Spec Definition from customer
or standards or market assessment
. (From
PLM)
客户定义或行业标准的初始版本的产品性能指标定义(PLM提供).
– NPD ID in DWM and agile. 项目ID号的建立.
5.1.4 Kick-off Meeting (no kick-off without preliminary product spec definition)
启动会议。项目启动的前提必须有初始状态客户对产品性能指标的定义(PLM提供)。
• Kick off meeting covers discussion of project background; business segment review
i e c o s t t a r g e t , k e y c u s t o m e r a n d c r i t i c a ldseal im
v eprl ye
date; preliminary design
platform, check patent status and ways to evade our new design conflict with th
c o m p e , t i r t eo sr os u r c ea pp pl a
r ,on v&
q au l a l i t y t a r g e t ( i e , y i e l
items to be
w a i v e r e dm u s t b eh i g h l i g h t eadn d m a k e a r e c o r d i n k i c k o ff m e e t i n g
minutes.
启动会议上会讨论新项目的背景，市场方面的信息，如目标成本，关键客户，重要样
品发货时间，RD讨论新设计平台，确认专利及可能的新设计是否与竞争对手的已有专
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

利相冲突，人力资源计划和审批，质量目标，以及可能的豁免项，都需要在启动会议
上讨论，并作好相关记录。
• X D L , P M G , a n d P L M o r g a n i z e k i c k
Team.
XDL, PMG 和PLM组织项目成员参加项目启动会。
• Kick off meeting presentation, please use “kick off meeting minute’s template” ENF-
00095 in Agile.
项目启动会议记录，请参考 A g i l系
e统中的“kick off meeting minut
template”。
• Design Center NPD set to state Kicked Off
Design Center将NPD设置为启动状态.
• LCO for project “to Alpha” submitted in Agile as soon as first BOM is created
5.2 ALPHA
The core task of this stage is to have teams work together to get required items ready
a n d a p p r o vfeodr “t o B e t a r e v”.i eKwe y t a s k s a r e t o m a k e a n o v e r a l l p l a n f o r
product development project, bring forward product solution
(s), verify core technology,
key circuit and key components, complete prototype development and EVT test.
本阶段的核心工作是部门间合作，以保证产品满足转移到Beta阶段的要求。主要任务项
为对该产品开发项目进行总体规划，提出产品解决方案并对核心技术和关键电路、关键元
器件进行验证，完成原型产品开发及EVT测试.
• Technical design and Prototype builds.
• PD committed Schedule
• Sourcing Strategy
• Mfg Strategy
• DFM rules/Source Wiki
• Identify critical specs and qual windows
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• Multiple designs allowed

• Shipment: None allowed
Note: Prototypes for customer testing of Alpha units will be allowed as long as the
products are clearly marked: product not for qualification purposes.

• PD shall complete PRD according to the inform
d ai nt ikoi cn k P
o: L
f fM p r o
c u s t o m e r r e q u i r e m e n t o r r e l e v a n t i n
requirement to product design validation, which shall cover:
a. requirements of function, performance and related parameters;
b. EVT,DVT test plan in module level;
c. Non-standard test requirements (e.g. ATIS, tin-whisker, CE cert)
PD根据PLM提供的相关客户需要及相关行业标准完成产品需求定义，包括对产品设计
验证的相关要求。其内容须涵盖：
a) 功能和性能及其参数指标等要求
b) 模块的EVT,DVT测试计划。
c) 非常规测试需求（如：ATIS, tin-whisker, CE cert）
• PD shallprepare the rpeliminary BOM

: As BOMs are added to theses PNs by PD
they have a LCM state = “Prototype”.
PD需要准备初始BOM, BOM完成后，该产品生命周期为prototype.
• U s e “ De s i g nF o r M a n u f a c t u r e C h e”,c E
k NL Fi s- t0 0 1 w
00h i c hf o c u s o n p r o d u c t
m a n u as
f a g c u t i u d r e a l bi in l e i t f y o r
Mechanical/OSA/FPC/PCB,etc
. when PD works on the first design. Then the DFM
list should be filed under its corresponding material code as one of the attachments
in agile.
ENF-00100是可制造性设计指导清单，该文件作为研发工程师第一版设计该物料（结
构件/光器件/柔板/硬板等）时的指导文件，使新设计的物料能够满足可制造性的要求
随后，该文件以附件形式归档在Agile其对应的物料号下。
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• FVT (firmware verification test) is prepared whit ATE test team’s support to compete
EVT test by PD.
EVT测试的过程中，ATE测试部门并行完成FW的验证测试。
• PMG: EPIE review, project schedule.
项目进度和EPIE的制作和维护。
• Engineering: MFG strategy, new equipment requirements (as applicable)
PE：MFG方案，适用的新设备要求
• DVT/RT: DVT and Reliability Test plan ; DVT和可靠性测试计划
• QA: In Process and final inspection criteria
& Supplier and key component quality
status.
5.2.3 Into Beta meeting Deliverables 输出

• General Deliverables: 5 items
– PRD (upgraded version)
– Datasheet
– Prototype BOM release
– EVT(Engineering verification test report) pass and release
– FVT(Firmware verification test report) if product has FW.
• Other deliverables per customer request:
– DSN (Design Files)
– DFMEA (preliminary)
– MTB_FITS
– RTP
5.2.4 Transfer to Beta: 转换到Beta阶段

• Formal meeting for the PROJECT to Beta is REQUIRED项目转到Beta阶段需要正
式会议
• The core objective of this stage is to meet 7 requirements
defined in the checklist
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

该阶段的核心目标是完成下面7项，
Rules：
• Call Beta review and sign off into Beta before sample delivery. Otherwise only
Alpha samples with clear marking of “Not for Qualification” may be provided to
customer
• Beta review is "Buy-In”
Requirements:
 To Beta gate review checklist”, Template is found in Agile as ENF-00093
请参见Agile系统中归档的“To Beta gate review checklist”。
 Meeting notes (To Beta & EPIE) attached to LCO changing project status to
Beta. Meeting notes must include any action items and responsible people.
会议记录（Beta & EPIE）要上传到将零部件链接到Beta项目的ECN中.会议记
录必须包含任务项和其责任人。
 PN cleanup: PNS not allowed to stay linked to the project shall have their
status changed to one of the following
“Open”- Recycle PN for other use
“FG Inactive”- Dead PN that will not be used
“Prototype” – not ready for qual
 Additional customer-specific requirements such as DVT or pre-pi
result
5.3 BETA STAGE

• Design frozen, ready for qualification builds.
• Consolidate and link designs.
• Verification of DFM, pre-pilot.
• All teams agree with the design and approach.
• S h i p m el n
imt i t a: t 2
i o5n0 q t y pe ea rc hP N o r m a x i m u m 2 K q t y p e r N P
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

counted.

Pre-pilot (typically > 100 units; less may be acceptable depending on project
requirements) to build DVT and R
in T p sr a
omd up cl e
t iso: n Bl ui ni let b
operators; NPIE/PD responsibility
完成小批量试生产（通常>100件；也可根据项目要求减量）并得到DVT，RT样品
注意该样品是由生产线操作员在产线制作完成；NPIE/PD负责跟线作技术指导。
- For brand new project, PD/NPIE should get typically 100pcs (less acceptable
for high speed line) pre-pilot date as an input to ask PE to take over the volume
production though lifecycle is still in Beta.
- 对于全新的产品，PD/NPIE需要提供100片的试产数据（高速产品可减少数量）
作为PE接手批量定单生产的依据，虽然这时产品的生命周期仍然在Beta.
- For derived or #-version product with component change or minor changes on
mfg process, it is PD/NPIE’s charge to run 20-50pcs pre-pilot first, if the result is
p o s i t i v e , N P I E i s t o w o r k o u t P M R 1 a s a n i n p u t ot ot aakseok vP
eEr the
s u b s e q u e n t v o l u m e p r o d u l ci tf ieoc ny ictslheos u
t igl lh i n B e t a . A f t e r t h
it’s PE’s charge to collect production date. When mfg qty reaches 100pcs, PE
needs to send these data to NPIE team so that NPIE will finish PMR2 as pilot
run report to transfer project to CA.
- 对于衍生或更换器件等改动的产品，PD/NPIE需要先跑20-50片的试生产，如果
生产情况良好，NPIE需要完成试产报告PMR1作为PE接手批量定单生产的依据；
此后，PE负责产线生产和收集生产数据，当数量超过100pcs且生产情况良好，由
PE发生产数据给NPIE部门，NPIE部门将负责完成PMR2，以作为转产CA的试产
报告。
• Initial customer qualification samples 客户
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

– RD is responsible for qualification sample build. After the building is done,

NPQ team starts to inspect sample quality per sample checklist and finish
sample checklist report accordingly. Sample could be shipped out after
approved by PLM.
RD负责完成认证样品的制作，当样品完成后，NPQ部门负责根据样品
checklist来检查样品质量并完成样品检验报告。样品报告需要得到PLM市场部
门的审批后，样品才能出货。
– NPQ is to coordinate with cross functional departments to finish waiver

process if there's any deviation detected during sample
inspection.
NPQ会跨部门协调豁免流程的完成，如果在样品检验过程中有发现作临时变更
的情况。
• Design Verification Process/设计验证过程

– All samples must come from Production line with no Engineering tuning or
pre-screening
所有样品均为无工程师调试或预挑选的产线生产出的产品。
– DVT is NOT a design tool, and a clean PASS is the expectation: PD must
v a l i d a t e a n d o p t i m i z e t h e d e s i g n P R I O R t
DVT failures are a serious problem for which PD and XDL must take full
accountability
DVT测试结果必须完全通过：PD必须保证DVT样品是使用被提前优化过的方案。对
于DVT测试失效，PD和XDL必须负全部责任，分析失效的原因和解决方案。
• P D s h a lpl r e p a r e s a m p l e f o r r e l i a b i l i t y tt he eset n. dP roi fo rt ht ios s t a g e ,

1000hours conditional test shall be completed and pass. Par
related with product design and key production process c
Please refer to “LCM-000001” for details.
PD准备样品进行可靠性测试，在本阶段结束之前必须完成并通过1k小时阶段性测试，
可以接受部分不涉及产品设计和关键生产工艺的失效。参见《LCM-000001》。
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• If PRD requires certification ofCDRH/TUV/CE/UL/FCC,prior to the end of this

stage, PD shall provide samples to Testing for product certification work.
根据产品需求定义要求，若涉及CDRH/TUV/CE/UL/FCC等产品认证，本阶段结束前
须由PD提供样品，交测试部安排产品认证工作.
• OSA PD/OE PD: Pilot complete,
conditionalRT (OSA a‘ ctive’), OE chip - LCM
“active”.
• E n g i n e e r i n g / N P I E t o p r e s e n t Te s t d e s i g n i m p l e m e n t a t i
Checklist, fixture design, PFC, PMR1.
• E n g i n e e r i n g / I E t o p r e s e n t W I , r o u t e r ; c a p a c i t y
instructions
• PD/PMG revisit which PNs will stay linked to Project and which will be dropped.
• OPS to validate Oracle resources and yields are scrubbed and process is ready
• QA to present in-process and final inspection criteria
• NPQ to drive the closure of the open issues found in PMR(pilot run report), NPQ
n e e d s t o f o l l o w u p t h i s cl o su r e b e f o r e p r o j e c t mo v e s t o n e xt s ta g e , a n d w o
with PE for PFMEA preparation.
• PLM to present DS if it has changed ;
– PD to present final DFMEA and PRD if it has changed
– BOM, Pre-pilot (<100 units), RT+DVT passing
– PFC must be released and under 1492 mfg BOM but not presented in meeting
• P r e - p i l o t : (i Pfy M
i eRl )d d no oe tm
s e e t t a rP gDe/ tN, P I E c o u l d p r o v
improvement plan and actions to PE as an instruction.
• DVT team to present DVT Report using template DVT-00001
• R e l i a b i l itteya mt o p r e s e nc to n d i t i o nRa T
l report using template RTR-00002;
CDRH/UL/TUV/CE/FCC
• Subassembly levels all Active lifecycle status.
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

5.3.4 Transfer to CA: 转换到CA阶段

• A f t e r a b o v e w o r k , P M G s h a l l k i c k o ff G a t e F
Roervm
i eaw.
l m e e t i nf o
gr t h e
PROJECT is REQUIRED to change the project lifecycle stage into CA stage.
EPIE review is required:
• M e e t i n g m i n u t e s a t t a c h e d t o
change. Meeting minutes must include review and closure of action items from
Beta Gate Review.
会议记录要上传到将零部件链接到CA项目的ECN中.会议记录必须包含任务项和
其责任人。
• “To CA gate review checklist” using template ENF-00094 found in Agile
请参见Agile系统中归档的“To CA gate review checklist”.
• PN cleanup: PNS not allowed to stay linked to the project shall have
• Production test plan is one of the key deliverables in“to CA” checklist, this is
to review yield of key spec in pilot run, whether all required DVT test items are
t e s t e d p wo i st i htr iev seu l t , s p e c t e s t p l a n w h e n p
PE’s responsibility, and the possible OQC and ORT test plan.
• 量产测试计划是“To CA”评审中的一个重要环节。在这里会评审关键指标在试
产中的良率，是否需要测试的DVT测试项都作了测试并结果是通过，产品转给
PE接手后的ATE测试计划，及可能的OQC， ORT测试计划。
Rules:
• Not meeting yield target, RDL and cost target are acceptable "into CA".
• RT 1000hrspass required to move to CA
. RT failure may be present if root
c a u s e a n d c o r r e c t i v e a c t i o nO iSs A k, nToOw na.n d o t h e r s u b a s s e m b
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

should be “Active” before “into CA”.

• CA review is "Buy-In”
5.4 CONTROLLED AVAILABILITY-CA

• Run Pilot Builds,
• Start ORT
• Manufacturing mature
• Ownership to Engineering/Ops. PD remains support on technical issues
• Volume Shipment
5.4.2 Detailed Accountability具体职责
• PE: MER, manufacturing report release

(typically >200 units) to see the yield
a n d c a p a c i t y i m p r o v Pe F
mMeE
n tA. s h o u l d b e c o m p l e t e d a n d a p p r o v e
agile.
PE：发行量产报告：PMR2（通常>200件），验证生产良率及产能提高，并完成
和归档PFMEA报告。
• Must meet required Yield, RDL and cost targets to GA
必须达成GA要求的一次性通过率和最终良率目标。
• RT: Full RT test finished and report released.
RT：完成RT测试，发行测试报告
• If a new PN needs to be linked to the Project, a separate ECN is needed and
rules for BOM and test process commonality apply
• ORT
• QA to release OQC WI according to checklist ofin-process and final inspection
criteria.
• NPQ to coordinate cross team to review all key criteria listed in Quality Plan and
close all open issues found in previous pilot run before projects moves to GA.
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• Final Module MER, full module Reliability Report.

• Final OSA PMR, full OSA Reliability Report.
• PFMEA
5.4.4 Transfer to FG-GA: 转移至GA阶段

• Formal review meeting is required to transfer to FG-GA.
转移到FG-GA阶段要求有正式的评审会议.
• Meeting notes attached to LCO for the Project LCM change
• “To GA gate review checklist”, template found in in Agile as ENF-00099
• . 请参见Agile系统中归档的“To GA gate review checklist”。
• PN cleanup: PNS not allowed to stay linked to the project shall have their
Rules:
• Must meet yield target and RDL target to "into GA",
in both module and optics
level.
• Must meet cost target and reflect in Oracle to "into GA".
• Lessons learned are reviewed and recorded during meeting
• GA review is "Buy-In”
5.5 GENERAL AVAILABILITY-GA

Core Tasks：核心职责
• Full production.
• ORT implemented.
• Quality Safety Nets running
_______________________________________________________________________________________________________
Ref. No.: ENP-00094

• Test reduction plans finished

• Shipment: No limitation.
5.6 OTHER PHASES

“Not preferred, Inactive and obsolete”, there are 3 additional phases after GA which
product lifecycles are maintained by PLM team.
– N o t p r e f e r r:eN
d o longer the best choice for new customer applications. Will
replaced by better design.
– I n a c t i vC
e :a n n o t t a k e n e w o r d e r s , b u t p a r t i s i n O r a c l e s o w e c a n s t
RMAs.
– Obsolete: Cannot do anything in Oracle including receiving RMAs, use only for part
numbers that were never shipped.
6. Relevant Documentation and Record/相关文件和记录

6.1 LCM-00001
6.2 CAP Management Regulation ENI-00061
《客户定制产品管理规范》
6.3 Reliability Test Management Regulation ENI-00074
《可靠性实验规范》
6.4 DVT Management Regulation ENP-00070
《DVT测试管理规范》
6.5 FAE Operation Regulation QAI-00543
《FAE操作管理规范》
6.6 Managing Lifecycle Status for Optics Subassemblies ENP-00036
《光器件组件生命周期管理规范》
_______________________________________________________________________________________________________

ENP-00094 Rev04 New Product Introduction Process 140303

Uploaded by

Document Information

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

ENP-00094 Rev04 New Product Introduction Process 140303

Uploaded by

Copyright:

Available Formats

Document Confidential Level: 1

New Product Introduction Process

Revision： 04 R&D Process

Revision： 04 R&D Process

Revision： 04 R&D Process

lifecycle. CAP number is added to customization documents for

Revision： 04 R&D Process

5. Working Procedure General/工作程序

Revision： 04 R&D Process

Project based LCM:

Revision： 04 R&D Process

matches the project lifecycle for ease of use.

Revision： 04 R&D Process

• New component selection & Sourcing Strategy in Product Development: 新物料选型

Revision： 04 R&D Process

 PRB will meet and decision will be recorded on ENF-00108

Revision： 04 R&D Process

5.1.2 Detailed Accountability 具体职责

Revision： 04 R&D Process

Revision： 04 R&D Process

• Multiple designs allowed

5.2.2 Detailed Accountability 具体职责

• PD shallprepare the rpeliminary BOM

Revision： 04 R&D Process

5.2.3 Into Beta meeting Deliverables 输出

5.2.4 Transfer to Beta: 转换到Beta阶段

Revision： 04 R&D Process

5.3 BETA STAGE

Revision： 04 R&D Process

5.3.2 Detailed Accountability 具体职责

Revision： 04 R&D Process

– RD is responsible for qualification sample build. After the building is done,

– NPQ is to coordinate with cross functional departments to finish waiver

• Design Verification Process/设计验证过程

• P D s h a lpl r e p a r e s a m p l e f o r r e l i a b i l i t y tt he eset n. dP roi fo rt ht ios s t a g e ,

Revision： 04 R&D Process

• If PRD requires certification ofCDRH/TUV/CE/UL/FCC,prior to the end of this

Revision： 04 R&D Process

5.3.4 Transfer to CA: 转换到CA阶段

Revision： 04 R&D Process

should be “Active” before “into CA”.

5.4 CONTROLLED AVAILABILITY-CA

• PE: MER, manufacturing report release

Revision： 04 R&D Process

• Final Module MER, full module Reliability Report.

5.4.4 Transfer to FG-GA: 转移至GA阶段

5.5 GENERAL AVAILABILITY-GA

Revision： 04 R&D Process

• Test reduction plans finished

5.6 OTHER PHASES

6. Relevant Documentation and Record/相关文件和记录

You might also like