-
IPD-
产品开发流程
-
开发阶段活动说明
活动
Activities
增扩
PDT
，
进
行产品开发
全员任命
Identify
Extended
Team
Members
IPMT-50
更新项目环
境
Update
Project
Environment
POP-30
召集开工会
Kick-off
meeting
LPDT-83
活动描述
Description
确定项目开
发、验证和发布阶段后续工作的外围组成员并按合同分配资源。
Identify extended team members for
continuing work on the project through the
develop, qualify and launch phases, and
allocate resources per the contract
更新项目文档及数据库，将外围组成员加入进来。同时也要更新智力资本
数据库。
add extended team
members to the project by updating the project
files, database.
Also update the
Intellectual Capital database.
LPDT
召集
PDT
核心组成员和扩展组全体成员举行开发阶段开工会，建议的会
< br>议议程如下：
1.
项目目标介
绍
(
产品经理
)
2.
版本开发合同书发布或签字仪式
(
研发管理办代表
/
产品线总监
/<
/p>
产品经理
)
任
命宣读（产品线总监
/
项目管理处经理
/
产品经理）
4.
< br>签定承诺书（产品经理和功能部门总监）
可选
成员相互介绍
(
全体<
/p>
PDT
成员
)
中角色和职责介绍
(
产品经理
)
7.
开发阶段流程以及流程求助渠道介绍<
/p>
(
引导者或项目管理处经理）
8.
计划阶段回顾和计划阶段交付件介绍（产品经理）
< br>
9.
开发阶段目标交付件介绍
(
产品经理
)
10.
开发阶段工作计划以及重要任务配合和计划风险说明
(
产品经理
)
11.
明确开发阶段工作
计划、考评和汇报关系、日常沟通方式
(
产品经理
)
12.
团队和个人测评指标及激励机制
(
产品经理
)
13.
相关领导动员讲话
LPDT bring together PDTcore
team members and extended team members
to
have a
kick-off meeting, with the
suggested agenda as follows:
project
objective(LPDT)
n development contract
issue or signature ceremony
(RD management
rep/product
line director/LPDT)
PDT appointment
(product line director/Project Management
manager/LPDT)
commitment letter (LPDT
and function department director)
optional
members
introduction to each other (all PDTmembers)
6. introduction of roles and
responsibilities of PDT(product manager)
develop phase process and process help
channel(facilitator or Project
Management manager)
plan phase and brief plan phase
deliverables ( LPDT)
develop phase
objective delivered (LPDT)
p phase work
plan , important task coordination & risk
description (LPDT)
develop phase work
plan, performance measurement ,reporting system
and
daily communication channel(LPDT)
and individual measurement and
incentive mechanism (LPDT)
13. mobilization speech by related
leader
各合作项目经理（产品合作、运营商合作、技术合作）依据对
外合作
合同
/
业务计划负责监控实施对
外合作计划，保证合作计划与产品开发的同步，
并将合作成果应用于产品开发中。
如遇需求变更或计划调整，
应按产品开发要求走变更流程，
并通过对外
合作部
/
业
务部合作分部与合作方达成一致或协调解决。
Each
cooperation project manager (product cooperation,
carrier
cooperation, tech cooperation)
responsible for monitoring external cooperation
execution, assuring cooperation plan in
pace with product development, and use
cooperation results to product
development according to external cooperation
contract/business plan.
If
requirement is
changed or plan adjusted,they should go
through
change control process,and
reach agreement with partners through external
cooperation department/functional
department cooperation branch.
< br>协调并跟踪项目任务绩效；跟踪时间进度、成本、资源和交付件；管理项目范
围和
更改；管理资源，必要的话重新分配资源；必要的话，向上反映问题；定
期性地报告项目
状态；使用
“
项目管理
”
使能流程
Coordinate and
track performance of project tasks; track
schedules, costs,
resources and deliverables; manage
scope and changes; manage and reallocate
resources if required; escalate issues
if required; report status on regular basis; use
the 'Project Management' enabling
process
执行对外合
作计划
Execute
external
cooperation
plan
LPDT-91
开始执行项
目监控
Begin
Monitoring
and Control
of Project
Execution
LPDT-90
FPDT-55
RDPDT-65
TSPDT-55
MNFPDT-55
PROPDT-55
MKTPDT-6
5
SE-125
POP-35
监控执行
信息安全
< br>计划
Monitor and
execute
Information
Security
Plan
LPDT-95
开始监控产
品质量目标
和计划
Begin
Monitoring
and
Control
Product
Quality
Objective
and Plan
/PQA-60
通过例会、阶段会议、度量分析、交付物审计
等，监控质量计划的执行情
况。
当实
际执行情况与产品质量计划发生偏差时，
PQA
应提醒
LPDT
采取相应
的补救措施，要求
LPDT
更新计划。更新后的计划必须经过再次审核和批准。
Begin monitoring and controlling
product quality plan by attending PDT
regular meeting, end of phase meeting,
delivery auditing, metrics analysis etc.
When variance is emerged between actual
result and initial product quality
plan, PQA is responsible to request
correcting activities from PDT, PDT should
update the product quality plan which
should be reviewed and approved once more.
开发代表组建
Build
小组，各开发项目组指定兼职
成员加入到
Build
小组。
Buil
d
小组负责准备
BBIT
（
Building Block Integrate and Test
）的集成方案、用例、环
境并负责执行
BBIT
活动。
RDPDT setup build
team, member in IPD-CMM project will join the team
part time.
Build team is responsible
for prepare Building Block Integrate and Test
scheme, test
cases, environment and
perform the BBIT.
组建
Build
小组
Setup Build
Team
RDPDT70
tracking
product
target cost
跟踪产品
目标成本
FPDT-56
执行标准计
划
Execute
standard plan
SE-127
According
to product BOB and procument price,FPDT calculate
the product
actual cost and the
difference from target cost,and then submit the
feedback
to R&D and procument and IPMT.
根据产品清单和采购价格，
FPDT
计
算产品的实际成本，比较实际成本与
目标成本的差距，并反馈给研发、采购和
IPMT
。
《产品标准计划》
中需要执行的标准工作活动主要有
3
类：
实施标准项目、
参加
国内外标准会议、标准研究，这些工作在计划和执行过程中都必须配合产品开
< br>发阶段的其他活动和国内外标准会议的时间表，并以促进产品开发和增强产品
市场
竞争力为目标。
There
are 3 kinds of standard activities which need to
be executed in
standard
plan
standard meetings,standard
research, which should coordinate with other
activities
of product develop phase and
domestic/international standard meeting schedule
in
order to promote product development
and enhance product market competitiveness.
优化市场计
划
Refine
market plan
MKTPDT-6
8
根据产品、客户的需求和与产品相关的潜在细分市场，在原有市场计划的基础
上
进一步分析和细化需要采取的战术性活动，
类似产品在何处销
售、
需要关注
的目标市场、如何更好地贴近和满足客户、如何提
升竞争能力等问题都需要详
细的描述
（市场策略）以及具体的措施，
包括价格和目标用户。
Based
on product and customer requirements and potential
market segmentation,
further analyze
and refine tactical activities which need to be
adopted, such as where
is the
product sold, target
market, how to better meet customer's
requirements, and
how to promote
competition ,etc. - all these questions need
detailed description
(market strategy) and specific measures
and steps ,including
price
and target users.
在
PDCP
通过之后，根据发布策略、具体的发布活动及交付件制定详细的
发布计划。
Develop detailed
launch plan after PDCP exit based on launch
strategy, launch
activities and
deliverables.
制定发布计
划
Develop
Launch plan
MKTPDT-6
9 <
/p>
开始
EC
发布
管
理，发布
初始
BOM
并
纳入
EC
控制
Begin EC
Release
Management
Release
Initial BOM
and put it
under EC
control
SE-130
对硬件设计
进行
EC
控制
Put Electrical
Design under
EC Control
EE-40
将所有技术信息放入数据库并通过正式的工程更改（
EC
）流程来管理更改；使
用
“
< br>交付件更改管理
”
使能流程来决定提议的更改，并使用<
/p>
PDM
或其它相似的系
统来自动管理工程
更改（
EC
release
）管理流程。
EC
release
管理并不是冻结数
据，
而是对更改进行控制，每个人都应该被告知有关的更改以便每个人都基于
相同的信息进行
工作。
Put all technical
information in a database and manage changes
through a formal
Engineering Change
(EC) process; use the 'Deliverable Change
Management'
enabling process to make
decisions about proposed changes and use a PDM or
equivalent system to automate the EC
release management process. EC release
management does not imply the data is
frozen, but rather the changes are controlled
and everyone is kept informed about the
changes so that everyone has the same set
of information to work from
所有共享的硬件设计信息，如规格、器件清单、原理图、网表（
netlist
）、布线
图、制造输出等都存放在一个产品数据
管理系统之中。任何更改必须通过正式
的
EC
< br>流程，该流程是交付件更改管理使能流程的一部分。在没有准备给其他团
队成员共
享之前的私人信息存放在特定的项目工作文件下。
All
shared electrical design information, such as
specifications, parts lists,
schematics, netlists, board layouts,
manufacturing outputs, etc. are stored in a
product data management system. Any
changes must go through the formal EC
process, which is part of the
Deliverable Change Management enabling process.
Private information is stored in
application-specific, project working files until
they
are ready for sharing with other
team members
对软件设计
进行
EC
控制
Put S/W
Design under
EC Control
SWE-40
所有共享的软件设计信息，如规格、原代码、目标代码、测试规格和结果、配
置、版本等都存放在软件管理系统中。
任何更改
必须通过正式的
EC
流程，它
是交付件
更改管理使能流程的一部分。在没有准备给其他团队成员共享之前的
私人信息存放在特定
的项目工作文件下。
All shared
electrical design information, such as
specifications, source code, object
code, test specs and results,
configurations, versions, etc. are stored in a
software
management system. Any changes
must go through the formal EC process, which is
part of the Deliverable Change
Management enabling process. Private information
is
stored in application-specific,
project working files until they are ready for
sharing
with other team members
对结构设计
进行
EC
控制
Put
Mechanical
Design under
EC Control
ME-40
所有的结构设计信息，比如规格、器件清单、布局图、制造输出等都存放在一
个产品数据管理系统中。
任何更改必须通过正式
的
EC
流程，它是交付件更改
管理使能
流程的一部分。在没有准备给其他团队成员共享之前的私人信息存放
在特定的项目工作文
件下。
All shared mechanical
design information, such as specifications, parts
lists, layouts,
manufacturing outputs,
etc. are stored in a product data management
system. Any
changes must go through the
formal EC process, which is part of the
Deliverable
Change Management enabling
process. Private information is stored in
application-specific, project working
files until they are ready for sharing with other
team members
对信息
开发
文档进行
EC
控制
Put
所有共享的技术产品文档，比如规格、图纸
、有关元器件的技术信息等都存放
在一个产品数据管理系统中。任何更改必须通过正式的
EC
流程，它是交付件更
改管理使能流
程的一部分。在没有准备给其他团队成员共享之前的私人信息存
放在特定的项目工作文件
下。
Documentati
on under EC
Control
TD-20
All shared technical product
documentation, such as specifications, drawings,
technical information about components
etc. are stored in a product data
management system. Any changes must go
through the formal EC process, which is
part of the Deliverable Change
Management enabling process. Private information
is
stored in application-specific,
project working files until they are ready for
sharing
with other team members
设计制造工
艺
Design
Manufacturi
ng Process
AME-40
评审现有的生产线能力
以确定设备和制造工艺的重用程度；评估自动化技术；
对工艺进行成本
< br>/
效益分析；调研开发供制造和测试用的新设备的需求；选择有
< br>效的制造工艺和设备并进行制造工艺概要设计。
Review existing manufacturing line
capabilities for reuse of equipment and
procedures; evaluate automation
technologies; perform cost / benefit analyses for
technologies; investigate need for
developing new equipment for manufacturing and
testing; select effective manufacturing
technologies and equipment and develop a
high level design of the manufacturing
process
设计生产测
试设备
Design
Manufacturi
ng testing
equipment
AME-45
参考装备总体方案和各单板概要设计内容，
< br>并考虑到各单板详细设计的规
格细化和变更情况，
制定各
单板的生产测试方案；
制定各测试仪的设计规格书。
单板生产测
试方案主要解决
FT
中各测试项目如何具体实现以及
ICT
、老化、软
件加载的方法；测试仪规格书主
要解决测试仪如何设计出来。以单板生产测试
方案和测试仪规格书共同指导后续装备的开
发。
Develop the
manufacturing testing plan taking into
consideration
equipment master plan and
single board high level design, and specs and
changes of
single board low level
design; develop design specs of all the testing
equipment.
Single board manufacturing
testing plan mainly addresses the execution of FT
testing activities and the methods of
ICT, aging and software loading; testing
equipment specs mainly addreses how the
testing equipment is designed. Single
board manufacturing testing plan and
testing equipment specs will be used together
to provide guidance to follow-up
equipment development.
供应商选
择
Select
supplier
PRO-20
制定市场资
料计划
Develop
Marketing
Information
Plan
这个活动由
CEG
根据
Sourcing plan
中设定的供应商选择标准和权重
进行。
CEG
将根据项目需要启动供应商选择流程。<
/p>
This activity is carried out
by the
CEG
using the
criteria and weightings
set out in the
sourcing plan.
CEG will
initiate the supplier selection process
（
ISC
）
if
required.
在
PDCP
通过
之后，召集营销相关人员讨论要开发的资料，并制定详细的
市场资料开发计划。
Convene Marketing members
concerned to discuss exploitative materials and
develop detailed Marketing information
plan afet PDCP exit.
<
/p>
准备发布
/
局
部
公开
/
培训
Prepare for
Announceme
nt
/Disclosure /
Training:
MKTE-26
开始修改
RFA
标准模板文档来准备
RFA
包（市场紧迫性、竞争紧迫性、机会丧
失可能性、暴露以前产品的缺陷等）；开
始收集信息来完成
RFA
文档；（
RF
A
意味着向
PDT
和
< br>IPMT
施加压力来发布产品，
PDT
< br>和
IPMT
在可获得性决策评审点
进行检查和平衡）
；
开始准备对销售员工的培训计划，
包括师资培训计划
（
T3
）
，
明确候选客户并准备秘密发布（这些客户可能是早期支
持的候选客户）；准备
局部发布的材料、信函、保密协议等
Start preparing the RFA (Request For
Announcement) package by modifying the
standard RFA template document (market
demand urgency, competitive urgency,
opportunity loss urgency, exposure to
previous product defects, etc. ); start
collecting information towards
completing the RFA document; (the RFA is intended
to put pressure on the PDT and IPMT to
announce the offering, while the PDT and
IPMT provide the check and balance via
the Availability DCP). start preparing
training programs for sales staff
including train-the-trainer programs (T3),
identify
customer candidates and
prepare for confidential disclosures (these
customers may
be candidates for early
support programs); prepare disclosure materials,
letters,
confidentiality agreements,
etc.
召开
NetStar
开工会，讨论
NetStar
的开发策略、算
法以及初步的开发计划。
Convene NetStar
kickoff meeting and discuss NetStar development
strategy,
algorithm and preliminary
plan.
根据开工会讨论的结果，制定详细的
NetSta
r
开发计划。
Develop
detailed NetStar plan based on the result of
kickoff meeting.
NetStar
启动
Kickoff
NetStar
MKTE-27
NetStar
开发
计划
Develop
NetStar Plan
MKTE-29
确定
BETA
测试和
ESP<
/p>
客户
Identify
BETA and
ESP
customer
MKTE-25
申请产品
/
模
块
/
单板命名
Apply Parts
Naming
MKTE-28
营销类资料
开发与评审
Develop and
Review
Marketing
Materials
MKTE-29A
基于制定的
BATA
客户选择标准寻找、评估、选择和确定
BATA
客户。
Looking
for, evaluating, selecting and determining BETA
customer based on BETA
customer
selection criteria.
根据产品命名规
则，在命名电子流上申请产品及部件的具体名称。
.
根据营销类资料计划，各责任部门
编写资料，并组织相关部门进行评审。
Department
concerned compose materials based on Marketing
information
plan, and organize
reviewing meeting.
监控并管理
配置及更改
Monitor and
Manage
Changes
SE-140
作为持续进行的活动的一部分，
对开
发和设计活动进行定期性的检查，
确
保产品需求、规格、配置和
其它的产品技术文档没有被随意更改；
使用
< br>PDM
的
EC
模块来使产品需求
、
规格、
配置和其它技术文档的更改受控
（在
PDM
实施
前，使用
CMM
和公司其它的相关流程）。
As part of an ongoing
activity, perform inspections regularly on design
and
development activities to make sure
that the offering requirements, specifications,
configuration(s) and other offering
technical documents are not changed in an
ad-hoc manner; maintain control over
changes to offering requirements,
specifications, configuration(s) and
other offering technical documents using the
structured 'Deliverable Change
Management' enabling process
设计检视
Perform
Design
Inspections:
SE-150
作为持
续进行的活动的一部分，通过参加由硬件、软件、结构、测试、工
业设计、采购、市场和
其他项目组成员召开的技术会议或阅读会议纪要来进行
设计检查；特别的，查实产品是否
符合特定的需求和规格，并对所有偏差或更
改进行标注；这项活动为
“
监控和管理配置及更改
”
活动提
供输入。
As part of an ongoing
activity, perform design inspections by
participating in or
reading meeting
minutes of regular project technical meetings
conducted by
electrical, software,
mechanical, testing, UCD, industrial design,
procurement,
marketing, and other
project members; specifically look for offering
compliance
with specified requirements
and specifications, and flag any deviations or
changes;
this activity feeds the
'monitor and mange changes' activity
<
/p>
企业标准、
企业内控标
准起草
Draft
Corporate
Standards
and Internal
Standards
SE-156
《企业标准》、《企业
内控标准》皆源于《产品规格书》，并在开发过程中参
照国际、国内标准，运用技术与经
济相结合原则，在不增加成本基础上，为达
到优于其他制造厂家同类产品质量而选择合适
的功能、性能指标编入到标准文
本中，两标准的各项指标定位要恰到好处，并要体现层次
和梯度：根据国家规
定，《企业标准》所列功能、性能指标可优于国际、国内同类标准中
相应的部
分，而《企业内控标准》在功能、性能指标上必须优于、严于《企业标准》的<
/p>
规定。
Corporate
Standards and Internal Standards come form
Offering Specs, considering
international and domestic standards
and based on the principle of align technology
with business. Include the proper
functional and performance indexes into the
documents with a view to reach higher
quality than the other manufacturers. The two
standards should be positioned
properly: according to national rules, Corporate
Standards can be higher than similar
international and domestic standards, and
Internal Standards must be higher and
more serious than Corporate Standards
根据项目需要检索专利文献和科技论文，
分析其可利用性和专利风险；
并
确定产品专利申请计划和商
标使用方案，以保护公司知识产权。
具体分析内容参见《知识产权分析报告模板》。
Search patent documents and technical
papers per project needs and analyze
their usability and patent risk; define
the patent plan and copywright usage plan to
protect Huawei intellectual property
rights.
Refer to IP analysis
template for details.
知识产权分
析
Intellectual
Property
analysis
SE-158
硬件详细设
计
Perform Low
Level
Electrical
Design:
EE-60
基于硬件概要设计，使用
标准的设计工具（根据情形选用
RF/
模拟
/
数字
/
芯片设计）来进行详细设
计，描绘出明确的板、卡、元器件、要完成的
功能和界面；对每一个板
< br>/
卡
/
元器件，开发电路设计，
原理图，零部件清
单，网表等；按照测试计划合并测试点来支持测试；在数据库中维护设
计信息。
Based
on
the
hardware
high
level
design,
use
standard
design
tools
(RF
/
Analog / Digital / Chip design,
depending on the situation) to perform the low
level design that lays out the specific
boards, cards, components,
functions
performed and interfaces; for
each board/card/component, develop the circuit
design,
schematic, part list, net list, etc.;
incorporate test points to support
testing per the test plan; maintain
design information in a database.
根据详细设计说明书、结构
PCB
要素图等
文档的要求进行
PCB
板的布局、
布线
和后仿真。
设计完成后投板。
具体过程见
《
PCB
设计投板流程》
（电子流）
。
Perform PCB
layout and post simulation based on low level
desogn specs and
mechanical PCB
elements diagram etc. See PCB design and making
process (notes)
硬件工程师准备好相应的物料，单
板
PCB
投板回来后，逐步加工好单板，
进行单板软硬件、逻辑调试，测试单板上模块电路特性是否符合设计要求。
Based on the low level design and the
test plans, and depending on RF / Analog /
Digital / Chip design, use appropriate
design tools to take the circuit design,
schematics, parts list, net list, test
points, etc., and design board layouts and
routings;
perform analysis and
simulation to identify and resolve problem areas
such as hot
spots, reliability, etc.;
acquire the components,
build the boards (either in-house or
using a supplier), populate the boards
and conduct unit testing; report and fix
problems and keep track of changes by
updating the documentation in the
application-specific project database;
report results of build and unit test; identify
manufacturability/serviceability/quality/
reliability issues and possible fixes
CAD
设计
CAD design
EE-65
单元测试
Develop
Electricals /
Unit Test:
EE-90
软件详细设
计
Perform Low
Level S/W
Design
SWE-50
基于分配给软件的需求和规格，使
用标准的设计工具（根据情形选用高
层次语言，
CASE
）来进行软件详细设计，描绘出详细的模块、要完成的功能、
输入、输
出和界面格式。
Based on the requirements allocated to
software and the specifications, use
standard design tools (high level
languages, CASE, depending on the situation) to
perform the low level software design
that lays out the specific modules, functions
performed, inputs, outputs and
interface formats;
编码
Develop S/W
/ Unit Test:
SWE-70
基于分配的软件需求和规格、软件详细设计，进行编码、链接
编辑并且
在编程数据库中维护代码及其历史资料。
Based on the low level
electrical design and offering specifications,
select chip
sets for offering
subsystems or boards; set up development
environments for chip
sets; acquire,
install and get trained in the use of the
programming
language/environment for
the selected chip sets; based on the allocated
embedded
software requirements and
specifications, develop code, link edit, test and
debug
code, and maintain the code and
its history in the programming database
单元测试
Unit test
SWE-72
进行测试和调试代码、并且在编程数据库中维护代码及其历史资料。
Test and debug the codes, and
maintain the codes and historical data in the
program
database
-
-
-
-
-
-
-
-
-
上一篇：法律翻译典型句型 Subject to
下一篇：食品专业英语考试重点