IPD-產(chǎn)品開發(fā)流程-開發(fā)階段精彩活動說明書

1、實用標準文檔IPD- 產(chǎn)品開發(fā)流程 - 開發(fā)階段活動說明活動Activities活動描述Description增擴PDT ， 進行產(chǎn)品開 發(fā)全員任命 Identify Extended Team Members IPMT-50確定項目開發(fā)、驗證和發(fā)布階段后續(xù)工作的外圍組成員并按合同分配資源。 Identify extended team members for continuing work on the project through the develop, qualify and launch phases, and allocate resources per the contract

2、更新項目環(huán) 境 Update Project Environme nt POP-30更新項目文檔及數(shù)據(jù)庫，將外圍組成員加入進來。同時也要更新智力資本 數(shù)據(jù)庫。add extended team members to the project by updating the project files, database. Also update the Intellectual Capital database.召集開工會Kick-off meetingLPDT-83LPDT 召集 PDT核心組成員和擴展組全體成員舉行開發(fā)階段開工會，建議的會 議議程如下：1. 項目目標介紹 （產(chǎn)品經(jīng)理 ）2.版

3、本開發(fā)合同書發(fā)布或簽字儀式 （研發(fā)管理辦代表 / 產(chǎn)品線總監(jiān) /產(chǎn)品經(jīng)理 ）3.PDT 任命宣讀（產(chǎn)品線總監(jiān) /項目管理處經(jīng)理 /產(chǎn)品經(jīng)理）4. 簽定承諾書（產(chǎn)品經(jīng)理和功能部門總監(jiān)） 可選5.PDT成員相互介紹 （全體PDT成員 ）6.PDT 中角色和職責介紹 （產(chǎn)品經(jīng)理 ）7. 開發(fā)階段流程以及流程求助渠道介紹 （引導者或項目管理處經(jīng)理）文案大全實用標準文檔8.計劃階段回顧和計劃階段交付件介紹(產(chǎn)品經(jīng)理)9. 開發(fā)階段目標交付件介紹 (產(chǎn)品經(jīng)理 )10. 開發(fā)階段工作計劃以及重要任務配合和計劃風險說明(產(chǎn)品經(jīng)理 )11. 明確開發(fā)階段工作計劃、考評和匯報關系、日常溝通方式(產(chǎn)品經(jīng)理 )12.

4、 團隊和個人測評指標及激勵機制(產(chǎn)品經(jīng)理 )13.相關領導動員講話LPDT bring together PDTcore team members and extended team members to have a kick-off meeting, with the suggested agenda as follows:1.brief project objective(LPDT)2.version development contract issue or signature ceremony(RDmanagement rep/product line director/LPDT)3

5、.read PDT appointment (product line director/Project Management manager/LPDT)4.sign commitment letter (LPDT and function department director) optional5.PDT members introduction to each other (all PDTmembers)6. introduction of roles and responsibilities of PDT(product manager)7.brief develop phase pr

6、ocess and process help channel(facilitator or Project Management manager)8.review plan phase and brief plan phase deliverables ( LPDT)9.brief develop phase objective delivered (LPDT) 10.develop phase work plan , important task coordination & risk description (LPDT)11.define develop phase work plan,

7、performance measurement ,reporting system and daily communication channel(LPDT)12.team and individual measurement andincentive mechanism(LPDT)13. mobilization speech by related leader文案大全實用標準文檔執(zhí)行對外合 作計劃 Execute external cooperatio n plan LPDT-91各合作項目經(jīng)理(產(chǎn)品合作、運營商合作、技術合作)依據(jù)對外合作 合同 / 業(yè)務計劃負責監(jiān)控實施對外合作計劃，保證

8、合作計劃與產(chǎn)品開發(fā)的同步， 并將合作成果應用于產(chǎn)品開發(fā)中。如遇需求變更或計劃調整， 應按產(chǎn)品開發(fā)要求走變更流程， 并通過對外 合作部 / 業(yè)務部合作分部與合作方達成一致或協(xié)調解決。Each cooperation project manager (product cooperation, carrier cooperation, tech cooperation) responsible for monitoring external cooperation execution, assuring cooperation plan in pace with product developmen

9、t, and use cooperation results to product development according to external cooperation contract/business plan.If requirement ischanged or plan adjusted,they should gothrough change control process,and reach agreement with partners through external cooperation department/functional department cooper

10、ation branch.文案大全實用標準文檔開始執(zhí)行項 目監(jiān)控 Begin Monitoring and Control of Project Execution LPDT-90 FPDT-55 RDPDT-65 TSPDT-55 MNFPDT-5 5PROPDT-5 5MKTPDT-6 5SE-125 POP-35協(xié)調并跟蹤項目任務績效；跟蹤時間進度、成本、資源和交付件；管理項目范 圍和更改；管理資源，必要的話重新分配資源；必要的話，向上反映問題；定 期性地報告項目狀態(tài)；使用“項目管理”使能流程Coordinate and track performance of project task

11、s; trackschedules,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監(jiān)控執(zhí)行 信息安全 計劃 Monitor and execute Informati on Security Plan LPDT-95文案大全實

12、用標準文檔開始監(jiān)控產(chǎn)通過例會、階段會議、度量分析、交付物審計等，監(jiān)控質量計劃的執(zhí)行情品質量目標況。和計劃當實際執(zhí)行情況與產(chǎn)品質量計劃發(fā)生偏差時， PQA 應提醒LPDT采取相應Begin的補救措施，要求 LPDT 更新計劃。更新后的計劃必須經(jīng)過再次審核和批準。MonitoringBegin monitoring and controlling product quality plan byandattending PDT regular meeting, end of phase meeting, deliveryControlauditing, metrics analysis etc.Pr

13、oductWhen variance is emerged between actual result and initialQualityproduct quality plan, PQA is responsible to request correcting activitiesObjectivefrom PDT, PDT should update the product quality plan which shouldand Plan /PQA-60be reviewed and approved once more.組建Build開發(fā)代表組建 Build 小組，各開發(fā)項目組指定兼

14、職成員加入到 Build 小組。 Build小組小組負責準備 BBIT( Building Block Integrate and Test)的集成方案、 用例、Setup環(huán)境并負責執(zhí)行 BBIT 活動。BuildRDPDT setup build team, member in IPD-CMM project will join theTeamRDPDT70team part time. Build team is responsible for prepare Building Block Integrate and Test scheme, test cases, environment

15、 and perform the BBIT.trackingAccording to product BOB and procument price,FPDT calculateproductthe product actual cost and the difference from target cost,andtargetthen submit the feedback to R&D and procument and IPMT.cost根據(jù)產(chǎn)品清單和采購價格， FPDT計算產(chǎn)品的實際成本，比較實際成本與跟蹤產(chǎn)品目標成本FPDT-56目標成本的差距，并反饋給研發(fā)、采購和 IPMT 。執(zhí)行

16、標準計產(chǎn)品標準計劃中需要執(zhí)行的標準工作活動主要有 3 類：實施標準項目、參劃加國內(nèi)外標準會議、標準研究，這些工作在計劃和執(zhí)行過程中都必須配合產(chǎn)品Execute開發(fā)階段的其他活動和國內(nèi)外標準會議的時間表，并以促進產(chǎn)品開發(fā)和增強產(chǎn)standard品市場競爭力為目標。planThere are 3 kinds of standard activities which need to be executed inSE-127product standard plan,that is execute standard project,attend文案大全實用標準文檔domestic and intern

17、ational 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.優(yōu)化市場計 劃 Refine market planMKTPDT-68根據(jù)產(chǎn)品、客戶的需求和與產(chǎn)

18、品相關的潛在細分市場，在原有市場計劃的基礎 上進一步分析和細化需要采取的戰(zhàn)術性活動， 類似產(chǎn)品在何處銷售、 需要關注 的目標市場、如何更好地貼近和滿足客戶、如何提升競爭能力等問題都需要詳 細的描述 (市場策略)以及具體的措施， 包括價格和目標用戶。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 theprodu

19、ct sold, target market, howto better meet customers requirements, and how to promote competition ,etc. - all these questions needdetailed description(market strategy) and specific measures and steps ,includingpriceand target users.制定發(fā)布計 劃 Develop Launch planMKTPDT-69在PDCP 通過之后，根據(jù)發(fā)布策略、具體的發(fā)布活動及交付件制定詳細

20、的 發(fā)布計劃。Develop detailed launch plan after PDCP exit based on launch strategy, launch activities and deliverables.文案大全實用標準文檔開始EC發(fā)布 管理，發(fā)布 初始 BOM 并 納入 EC控制 Begin EC Release Manageme nt Release Initial BOM and put it under EC control SE-130將所有技術信息放入數(shù)據(jù)庫并通過正式的工程更改(EC)流程來管理更改；使用“交付件更改管理”使能流程來決定提議的更改，并使用PDM

21、 或其它相似的系統(tǒng)來自動管理工程更改 ( EC release )管理流程。 EC release 管理并不是凍 結數(shù)據(jù)，而是對更改進行控制，每個人都應該被告知有關的更改以便每個人都 基于相同的信息進行工作。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 prop

22、osed 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對

23、硬件設計 進行EC控制 Put Electrical Design under EC Control EE-40所有共享的硬件設計信息，如規(guī)格、器件清單、原理圖、網(wǎng)表( netlist )、布 線圖、制造輸出等都存放在一個產(chǎn)品數(shù)據(jù)管理系統(tǒng)之中。任何更改必須通過正 式的 EC流程，該流程是交付件更改管理使能流程的一部分。在沒有準備給其他 團隊成員共享之前的私人信息存放在特定的項目工作文件下。All shared electrical design information, such as specifications, parts lists, schematics, netlists, boa

24、rd 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

25、ready for sharing with other team members對軟件設計 進行EC控制 Put S/W Design under EC Control SWE-40所有共享的軟件設計信息，如規(guī)格、原代碼、目標代碼、測試規(guī)格和結果、配 置、版本等都存放在軟件管理系統(tǒng)中。 任何更改必須通過正式的 EC流程，它 是交付件更改管理使能流程的一部分。在沒有準備給其他團隊成員共享之前的 私人信息存放在特定的項目工作文件下。All shared electrical design information, such as specifications, source code, obje

26、ct 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 f

27、iles until they are ready for文案大全實用標準文檔sharing with other team members對結構設計 進行EC控制 Put Mechanical Design under EC Control ME-40所有的結構設計信息，比如規(guī)格、器件清單、布局圖、制造輸出等都存放在一 個產(chǎn)品數(shù)據(jù)管理系統(tǒng)中。 任何更改必須通過正式的 EC流程，它是交付件更改 管理使能流程的一部分。在沒有準備給其他團隊成員共享之前的私人信息存放 在特定的項目工作文件下。All shared mechanical design information, such as spec

28、ifications, 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

29、 files until they are ready for sharing with other team members對信息開發(fā) 文檔進行 EC 控制PutDocument ation under EC ControlTD-20所有共享的技術產(chǎn)品文檔，比如規(guī)格、圖紙、有關元器件的技術信息等都存放 在一個產(chǎn)品數(shù)據(jù)管理系統(tǒng)中。任何更改必須通過正式的EC流程，它是交付件更改管理使能流程的一部分。在沒有準備給其他團隊成員共享之前的私人信息存 放在特定的項目工作文件下。All shared technical product documentation, such as specificatio

30、ns, 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 fil

31、es until they are ready for sharing with other team members設計制造工 藝 Design Manufactu ring Process AME-40評審現(xiàn)有的生產(chǎn)線能力以確定設備和制造工藝的重用程度；評估自動化技術； 對工藝進行成本 /效益分析； 調研開發(fā)供制造和測試用的新設備的需求； 選擇有 效的制造工藝和設備并進行制造工藝概要設計。Review existing manufacturing line capabilities for reuse of equipment and procedures; evaluate automa

32、tion 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文案大全實用標準文檔設計生產(chǎn)測 試設備 Design Manufactu

33、 ring testing equipment AME-45參考裝備總體方案和各單板概要設計內(nèi)容， 并考慮到各單板詳細設計的規(guī) 格細化和變更情況， 制定各單板的生產(chǎn)測試方案； 制定各測試儀的設計規(guī)格書。 單板生產(chǎn)測試方案主要解決 FT中各測試項目如何具體實現(xiàn)以及 ICT、老化、軟 件加載的方法；測試儀規(guī)格書主要解決測試儀如何設計出來。以單板生產(chǎn)測試 方案和測試儀規(guī)格書共同指導后續(xù)裝備的開發(fā)。Develop the manufacturing testing plan taking into consideration equipment master plan and single board

34、 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 m

35、ainly 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這個活動由 CEG根據(jù) Sourcing plan 中設定的供應商選擇標準和權 重進行。 CEG將根據(jù)項目需要啟動供應商選擇流程。This ac

36、tivity is carried out by theCEG using the criteria andweightings set out in the sourcing plan.CEG will initiate thesupplier selection process（ ISC）if required.制定市場資 料計劃 Develop Marketing Informatio n Plan在PDCP 通過之后，召集營銷相關人員討論要開發(fā)的資料，并制定詳細的 市場資料開發(fā)計劃。Convene Marketing members concerned to discuss explo

37、itative materials and develop detailed Marketing information plan afet PDCP exit.文案大全實用標準文檔準備發(fā)布 / 局 部公開 / 培訓 Prepare for Announce ment /Disclosure / Training: MKTE-26開始修改 RFA 標準模板文檔來準備 RFA 包(市場緊迫性、競爭緊迫性、機會喪 失可能性、暴露以前產(chǎn)品的缺陷等)；開始收集信息來完成RFA文檔；( RFA意味著向 PDT和IPMT 施加壓力來發(fā)布產(chǎn)品， PDT和IPMT在可獲得性決策評審 點進行檢查和平衡)；開始準

38、備對銷售員工的培訓計劃，包括師資培訓計劃 ( T3)，明確候選客戶并準備秘密發(fā)布 (這些客戶可能是早期支持的候選客戶) ； 準備局部發(fā)布的材料、信函、保密協(xié)議等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.

39、 ); 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-t

40、he-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 啟 動KickoffNetStarMKTE-27召開 NetStar 開工會，討論 NetStar 的開發(fā)策略、算法以及初

41、步的開發(fā)計劃。 Convene NetStar kickoff meeting and discuss NetStar development strategy, algorithm and preliminary plan.NetStar 開 發(fā)計劃 Develop NetStar Plan MKTE-29根據(jù)開工會討論的結果，制定詳細的 NetStar 開發(fā)計劃。Develop detailed NetStar plan based on the result of kickoff meeting.確定 BETA 測試和 ESP 客戶 Identify BETA and ESP custo

42、mer基于制定的 BATA 客戶選擇標準尋找、評估、選擇和確定 BATA 客戶。 Looking for, evaluating, selecting and determining BETA customer based on BETA customer selection criteria.文案大全實用標準文檔MKTE-25申請產(chǎn)品 / 模 塊 / 單板命名 Apply Parts Naming MKTE-28根據(jù)產(chǎn)品命名規(guī)則，在命名電子流上申請產(chǎn)品及部件的具體名稱。營銷類資料 開發(fā)與評審 Develop and Review Marketing Materials MKTE-29A根據(jù)營

43、銷類資料計劃，各責任部門編寫資料，并組織相關部門進行評審。Department concerned compose materials based on Marketing information plan, and organize reviewing meeting.監(jiān)控并管理 配置及更改 Monitor and Manage Changes SE-140作為持續(xù)進行的活動的一部分， 對開發(fā)和設計活動進行定期性的檢查， 確 保產(chǎn)品需求、規(guī)格、配置和其它的產(chǎn)品技術文檔沒有被隨意更改； 使用 PDM 的EC模塊來使產(chǎn)品需求、 規(guī)格、配置和其它技術文檔的更改受控 (在 PDM 實施 前，使用 C

44、MM 和公司其它的相關流程)。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

45、 offering requirements, specifications, configuration(s) and other offering technical documents using the structured Deliverable Change Management enabling process設計檢視 Perform Design Inspection s: SE-150作為持續(xù)進行的活動的一部分，通過參加由硬件、軟件、結構、測試、工 業(yè)設計、采購、市場和其他項目組成員召開的技術會議或閱讀會議紀要來進行 設計檢查；特別的，查實產(chǎn)品是否符合特定的需求和規(guī)格，并對所

46、有偏差或更 改進行標注；這項活動為“監(jiān)控和管理配置及更改”活動提供輸入。 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文案大全實用

47、標準文檔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企業(yè)標準、 企業(yè)內(nèi)控標 準起草 Draft Corporate Standards and Internal Standards SE-156企業(yè)標準、企業(yè)內(nèi)控標準皆源于產(chǎn)品規(guī)格書，并在開發(fā)

48、過程中參 照國際、國內(nèi)標準，運用技術與經(jīng)濟相結合原則，在不增加成本基礎上，為達 到優(yōu)于其他制造廠家同類產(chǎn)品質量而選擇合適的功能、性能指標編入到標準文 本中，兩標準的各項指標定位要恰到好處，并要體現(xiàn)層次和梯度：根據(jù)國家規(guī) 定，企業(yè)標準所列功能、性能指標可優(yōu)于國際、國內(nèi)同類標準中相應的部 分，而企業(yè)內(nèi)控標準在功能、性能指標上必須優(yōu)于、嚴于企業(yè)標準的 規(guī)定。Corporate Standards and Internal Standards come form Offering Specs, considering international and domestic standards and b

49、ased 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

50、 higher than similar international and domestic standards, and Internal Standards must be higher and more serious than Corporate Standards知識產(chǎn)權分 析 Intellectual Property analysis SE-158根據(jù)項目需要檢索專利文獻和科技論文， 分析其可利用性和專利風險； 并 確定產(chǎn)品專利申請計劃和商標使用方案，以保護公司知識產(chǎn)權。具體分析內(nèi)容參見知識產(chǎn)權分析報告模板。Search patent documents and technic

51、al 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.文案大全實用標準文檔硬件詳細設 計 Perform Low Level Electrical Design: EE-60基于硬件概要設計，使用標準的設計工具(根據(jù)情形選用 RF/

52、模擬 /數(shù)字 / 芯片設計)來進行詳細設計，描繪出明確的板、卡、元器件、要完成的 功能和界面；對每一個板 / 卡/ 元器件，開發(fā)電路設計，原理圖，零部件 清單，網(wǎng)表等；按照測試計劃合并測試點來支持測試；在數(shù)據(jù)庫中維護 設計信息。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 spe

53、cific 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.CAD 設計CAD designEE-65根據(jù)詳細設計說明書

54、、結構 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）單元測試 Develop Electricals / Unit Test: EE-90硬件工程師準備好相應的物料，單板 PCB投板回來后，逐步加工好單板， 進行

55、單板軟硬件、邏輯調試，測試單板上模塊電路特性是否符合設計要求。 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 analysi

56、s 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 asupplier), populate the boards and conduct unit testing; report and fix problems and keep track of changes by updating the documentation in

57、the application-specific project database; report results of build and unit test; identify manufacturability/serviceability/quality/reliability issues and possible fixes軟件詳細設 計基于分配給軟件的需求和規(guī)格，使用標準的設計工具（根據(jù)情形選用高層次語言， CASE）來進行軟件詳細設計，描繪出詳細的模塊、要完成的功能、文案大全實用標準文檔Perform Low Level S/W Design SWE-50輸入、輸出和界面格式。

58、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基于分配的軟件需求和規(guī)格、軟件詳細設計，