1、活動/活動號Activity /Activity ID活動描述Description增擴PDTAugment PDTIPMT-30選擇和落實為完成該產品計劃階段任務所需的PDT擴展組成員。Identify and obtain PDT extended team members for continuing work on the project for Plan Phase.團隊培訓Conduct teamtrainingLPDT-46在PDT開始工作前對PDT團隊的系統培訓，包括以下內容：Provide systematic training to PDT before kickoff,

2、including:1、團隊建設培訓1;2、產品開發流程培訓，重點是計劃階段的流程；3、系統工程培訓1; 4、項目管理培訓。1. Team building; 2. Product development process with focus on Plan Phase process;3. System engineering; 4. Project management增加擴展組 成員并更新 項目文檔Add Extended TeamMembers and UpdateProject FilesPOP-20更新項目文檔（如根據評宙意見更新業務計劃書）及數據庫，將外圍組成員加入進來。同時也要

3、更新智力資本數據庫。Add extended team members to the project by updating the project files, database. Also updatethe Intellectual Capital database.開工會Lead Kickoff PlanPhase ActivitiesLPDT-50通知和分配附加的團隊成員給項目；團隊，將新成員引導進入項目，解釋他們的角色和對他們的期望。參考議程如下：1、項目目標介紹(PDT經理)；2、宣讀PDT展組任命(產品線總監或項目管理處經理)；3、PD成員相互介紹(核心組和擴展組成員)；4、計

4、劃階段流程簡單介紹(引導者或項目管理處經理)；5、 概念階段回顧和交付件介紹(PDT理)；6、 計劃階段團隊成員的角色和職責(LPDT);7、 計劃階段目標交付件介紹(PDT理)；8、 明確計劃階段項目計劃、考評和匯報關系、日常溝通方式(PDT經理)；9、 團隊和個人測評指標及激勵機制(LPDT);10、簽訂資源承諾書(可選)；11、領導動員。Inform and assign the additional team members to the project; perform team-building; bring newmembers up to date on project; ex

5、plain their roles and expectations from them. The following agendais for reference:1. Introduce project target (LPDT);2.Announce appointment of PDTextended team members ( Product Line director or ProjectManagement Office manager)3.PDT members introduce themselves to each other (core team and extende

6、d team members)4.Brief introduction of Plan Phase process ( facilitator or Project Management Office manager)5. Recap of Concept Phase and introduction of deliverables ( LPDT);6. PDT members roles and responsibilities in Plan Phase (LPDT);7. Introduction of target deliverables in Plan Phase ( LPDT);

7、8.Identify Plan Phase project plan, measurement and report relationship, day to daycommunication approach ( LPDT)9. Team and individual measurement metrics and incentive mechanism(LPDT);10. Sign resource commitment letter (optional);11. Lead deliver mobilization speech制定計劃階 段項目計劃(WBS3/4級)Develop Pla

8、n PhaseProject Plan (WBSL3/L4) LPDT-55/FPDT-45/RDPDT-55/TSPDT-45/MNFPDT-45/PROPDT-45/MKTPDT- 45組織PDT成員共同討論制定項目計劃階段項目計劃，為計劃階段工作提供指 導。Organize PDT members to discuss and develop Plan Phase project plan to provide guidance for PlanPhase activities.decomposeproduct targetcost分解產品目 標成本FPDT-47According to

9、 product structure,FPDT decomposes product target cost into medel orkey material,in orer to R&D and procument could control cost.根據產品結構，FPDT將產品目標成本分解成模塊或關鍵物料的成本，以便 研發和米購控制成本。優化產品質 量目標和計 劃Refine productquality objectiveand plan /PQA-30進一步優化產品質量目標和計劃，產品質量計劃由LPD秘各功能領域代表審 核，并作為業務計劃的一部分納入業務計劃進行管理和監控。

10、Refine product quality objective and plan, the product plan shall be reviewed by LPDT and othermembers of PDT core team, monitored and controlled by PDT as a part of business plan.制JE發布策 略Develop LaunchStrategyMKTPDT-47在CDCP通過之后，參考營銷策略、市場策略、目標市場等編寫產品發布策略（網上發布 新聞發布會 廣告，什么時間將提供具備什么功能的產品。Compose the la

11、unch strategy after CDCP exit with input from marketing strategy, market strategyand target market.需求分解和分配Partition andAllocateRequirementsSE-50與硬件工作師、軟件工程師及結構工程師一起協作，分析產品包需求， 將需求分解成硬件、軟件或結構子系統；然后每一塊（硬件、軟件、結構）進一 步將需求分配到小一層子系統、部件或模塊之中；需求分解要確定某些特殊需求如何由硬件、軟件或金構或任何組甘形式頭現；需求分配要清晰地決需求的 哪些部門由硬件實現，哪些部分由軟件實現

12、，哪些部分由結構實現，它們之間的 接口也要定義清楚。In collaboration with the electrical engineer, software engineer and mechanical engineer,analyze the offering requirements, partition them into electrical, software or mechanical subsystems;each discipline (electrical, software, mechanical) then further allocates the requir

13、ements intosubsystems and components or modules; the partitioning determines whether a particular requirement willbe met using electrical, software or mechanical or any combination; the allocation clearly decides whichpart of the requirement is to be met by electrical, which part by software, which

14、part by mechanical,and the interfaces between them.硬件需求分 解與分配Partitionand AllocateElectricalRequirementsEE-20分析硬件需求，將需求分割成子系統、部件或模塊；“硬件需求”的分解和 分配將確定某些特殊需求如何采用子系統、部件或模塊的組合來實現，它們之間 的接口關系也要定義清楚Analyze the electrical requirements, partition them into subsystems and components or modules;the partitioning

15、 and allocation of the electrical requirements determines how a particular requirementwill be met using a combination of subsystems, components, or modules, and the interfaces between them.軟件需求分解與分配Partition andAllocate SWRequirementsSWE-20分析軟件需求，將它們分割成子系統或模塊；“軟件”需求的分割和分配要 確定某些特殊需求如何采用子系統或模塊的組合來實現，它

16、們之間的接口關系也 要定義清楚。Analyze the software requirements, partition them into subsystems or modules; the partitioning andallocation of the software requirements determines how a particular requirement will be met usinga combination of subsystems or modules, and the interfaces between them.結構需求分 解與分配Partiti

17、onand AllocateMechanicalRequirementsME-20分析結構需求，將它們分割成子系統、部件或模塊；“結構”需求的分割和 分配要確定某些特殊需求如何由子系統、部件或模塊的組合實現，以及它們之間 的接口關系。Analyze the mechanical requirements, partition them into subsystems and components or modules;the partitioning and allocation of the mechanical requirements determines how a particula

18、r requirementwill be met using a combination of subsystems, components, or modules, and the interfaces between them系統設u和 設計規格定 義Develop SystemDesign and SpecsSE-60基于需求分解和分配方面的協作活動，生成系統、子系統、部件、模塊及 接口的技術規格，要求表達清晰以減少誤解及重復；生成一個概要的BOM結構樹以及系統設計概念塊圖。Based on the partitioning and allocation collaborative ac

19、tivities, generate technicalspecification for the system, subsystems, modules, components and interfaces in clear language to reducemisunderstanding and duplication; develop a high level BOM tree structure and a block diagram of thesystem design concept.技術評審2Perform TechnicalReview 2SE-70PQA-40在計劃階段

20、對產品設計規格的評審。TR2重點關注產品設計需求到產品設計規格的完備性。Review the product design specifications in Plan phase. TR2 is focused on assessing the completenessof the translation of design requirements into design specifications.TR2的準備活動包括各功能領域完成專項評審，在TR2的評審會上將由PDT核心團隊在綜合層面進行討論，確保設計規格包括并適應每單兀和構建模塊(譬如單板、軟件模 塊)的設計。TR2 prepar

21、ation and review activities include affirmation of functionalspecification reviews at the sub-process level as well as summary level discussion at the PDT core team levelto ensure that design specifications include specifications suitable for unit and building block design; forexample hardware singl

22、e board assemblies and software modules.TR2的評審過程包括對關鍵設計規格和要點的綜合討論，也對產品架構(配置)進行細致審閱(走讀)，以確保后續的概要設計(HLD )能進行。The TR2 session includesa summary level review of key design points and specifications. It also includes a walkthrough of the productarchitecture (configuration) as a foundation for performing

23、subsequent High Level Design activities.TR2誦過后 L 品設計規格應被置干更改控制之下。After TR2 passes, the product designspecifications shall be put under the change control.TR2的目的是確保：The objective of TR2 is to ensure that:a.設計規格充分映射了設計需求，并足以指導后續的IPD流程及功能領域子流程的產品開發活動；The Design Specification adequately addresses Design

24、 Requirementsand is appropriate for subsequent IPD and Functional sub-process level product development activities.b.定位產品規格和配置中的缺陷和限制，評估風險，形成規避策略和應急計劃；Gaps and limitations in product specification and configuration have been identified; risks evaluated, andmitigation strategies and action plans have

25、 been put in placec.形成有效的廣品酉己置。A viable product configuration has been identified系統規格基 線化Set System SpecsBaseline SE-801、將評審通過的產品規格書作為基線；2、對后續產品開發過程中產生的規格更改進行控制。1. Set approved product specifications as the baseline;2. Put follow up specs changes under change control.開始監控設計規格Begin toMonitor &Man

26、age SpecsSE-90定期地對設計和開發活動進行檢查以確保開發人員正確地按產品包技術規格 進行開發；使用PDM的EC模塊來使規格的更改受控(在PDM實施前，使用CMM和公司其它的相關流程)。Perform inspections regularly on design and development activities to make sure that the technicaloffering specifications are properly addressed by the developers; maintain control over changes tospecif

27、ications using the structured Deliverable Change Management enabling process ( use CMM andother appropriate Huawei existing processes before implementation of PDM)Build劃分BuildPartition SE-65SEffl織開發人員依據設計需求和設計規格進行Build劃分，生成Build計劃和BBIT的策略。Build計劃是后續制訂開發計劃和測試與驗證計劃的依據。Build劃分的關鍵步驟如下：1、根據設計需求和設計規格建立功能-

28、模塊矩陣2、初步分析、整理功能跟蹤矩陣，建立unique-combination3、劃分Build4、畫Build拓撲圖并整理模塊進度計劃SE organize developer to perform build partition based on design requirement anddesign specification. Complete build plan and building block integrate and teststrategy. Follow up develop plan and certification and test plan will ba

29、sed on BuildPlan.Key step for build partition is:1. Define function-module matrix based on design requirement and designspecification.2. Analysis function-module matrix and create unique-combination.3.Partition build.4.Draw build plan diagram and develop build schedule.開發產品包 需求跟蹤矩 陣DevelopOffering R

30、eq.Track MatrixSE-85系統工程師根據基線化的產品包需求、設計需求和設計規格建立需求跟蹤矩陣， 明確產品包需求如何一級級分解到構建模塊上。SE develop offering requirement track matrix based on offering requirement, designrequirement and design specification. Identify how offering requirement is allocatedto building block through steps.開發BBIT策略DevelopBBITStrate

31、gyEE-35,SWE-35開發人員根據Build計劃確定BBIT策略，確保Build構建的質量。Developer develop Building Block Integrate and Test Strategy based on Build Plan。Ensure the quality of Integrate and test of building block.概要設計High Level DesignSE-95系統工程師，和各專業工程師(硬件、軟件、結構、EMC等)合作，按照概要設計文檔模板要求，開發和精練概要設計，包括系統概要設計、硬 件概要設計、軟件概要設計、結構概要設計等

32、。System engineer collaborate with expertise in different areas ( electronic, software,mechanical and EMC,etc) to develop and refine high level design following High Level Design template,including system high level design, electronic high level design, software high level design andmechanical high l

33、evel design, etc.知識產權分 析PerformIntellectualProperty AnalysisSE-98根據項目需要檢索專利文獻和科技論文，分析其可利用性和專利風險； 并確定產品專利申請計劃和商標使用方案，特別是專利申請計劃，以保護公司知 識產權；具體分析內容參見知識產權分析報告模板。Retrieve patents and technical documents based on requirements of the project and analyzeits usability and patent risk; identify product patent

34、filing plan and trade mark plan, (esp. Patentfiling plan) to protect corporate intellectual property; pls refer to Intellectual Property AnalysisReport Template for detail.硬件概要設 計PerformElectrical HighLevel Design EE-30基丁概要的BOM結構樹及系統的設計規格書，開發一個到板級的硬件概要 設計；與系統工程師 F 來解決 F 它功能開發小組之間的沖突和問題。 必要的話，提出需求和/或

35、規格更改方面的建議。Based on the high level BOM tree structure and system specification, develop a highlevel electrical system design at the board level, work with the Systems Engineer inresolving conflicts and issues with the other disciplines. Recommend changes to therequirements and/or specifications if ne

36、cessary.軟件概要設 計Perform SW HighLevel DesignSWE-30基于概要BOM結構樹及系統設計概念塊圖，進行模塊級即需要多少個模塊以 及每個模塊的環境及功能等的軟件系統概要設計；準備這一層次的軟件系統配置，與系統工程師一起來解決與其它功能開發小組之間的沖突和問題。必要的話，提 出需求和/或規格更改方面的建議。Based on the high level BOM tree structure and a block diagram of the system design concept,develop a high level software system

37、design at the module level, i.e., how many modules, environmentsand functions of each module, etc.; prepare the software system configuration at this level and workwith the Systems Engineer in resolving conflicts and issues with the other disciplines. Recommend changesto the requirements and/or spec

38、ifications if necessary結構概要設 計PerformMechanical HighLevel Design EE-30時概要的BOM結構樹及系統設計概念塊圖，進行結構系統概要設計，闡述 硬件系統所需要的放置、供電、線路安裝/連接及板件冷卻，以及提供軟件載入的方法；準備這一層次的結構系統配置，與系統工程師一起來解決與其它功能開發 小組之間的沖突和問題。必要的話，提出需求和/或規格更改方面的建議。Based on the high level BOM tree structure and a block diagram of the system design concept

39、,develop a high level mechanical system design to house, power, wire/connect and cool the boards requiredby the electrical system, as well as to provide means for loading software; prepare the mechanical systemconfiguration at this level and work with the Systems Engineer in resolving conflicts and

40、issues withthe other disciplines. Recommend changes to the requirements and/or specifications if necessary.工業設計概 要設計Perform High LevelIndustrialDesign IDE-30基于結構系統概要設計，提供工藝(外觀)設計給結構工程師以維持品牌形 象；基十概要的BOM結構樹和系統設計概念塊圖，以及來自于硬件、軟件、結構、工藝/以用戶為中心的設計、測試和認證、信息開發和翻譯等方面的工程師/專家的輸入，修改標準的WBS模板，形成包括了資源、成本、和時間進度估計的詳細

41、計 戈(J,闡述了以用戶為中心的設計的各個方面，包括所有顧客接觸點；包括工藝設 計以及可用性和人機工程設計等各方面。Based on the high level mechanical system design, provide industrial (appearance) design inputto the mechanical engineer in order to maintain the brand image; based on the high level BOM treestructure and a block diagram of the system design

42、concept, as well as inputs from the electrical,software,mechanical,industrial/user-centereddesign,testing&certification,informationdevelopment and translation engineer/specialist, modify the standard WBS templates to develop adetailed plan with resource, cost and schedule estimates, to address t

43、he user-centered design aspectsof the offering including all the customer touch points; include industrial design as well as usabilityand ergonomic design aspects.制定系統測 試及驗證計 劃Develop SystemTest andCertificationPlan TE-20時概要的BOM結構樹和系統設計概念框圖，以及來自于硬件、軟件、結構、工藝/以用戶為中心的設計、測試和認證、信息開發和翻譯等方面的工程師/專家的輸入，修改標準的

44、WBS模板，形成包括了資源、成本、和時間進度估計的詳細計 戈闡述了系統測試(內部和外部的)、品質保證，以及各國準入法規。Based on the high level BOM tree structure and a block diagram of the system design concept,as well as inputs from the electrical, software, mechanical, industrial/user-centered design, modifythe standard WBS templates and develop a detaile

45、d plan with resource, cost and schedule estimates,to address systems testing (internal and external), quality assurance, as well as industry (orgovernment) certification (including homologation).制定信息計 劃DevelopInformation PlanTD-10制定翻譯計劃DevelopTranslation PlanTD-15時概要的BOM結構樹和系統設計概念框圖，以及來自于硬件、軟件、結構、工藝

46、/以用戶為中心的設計、測試和認證、信息開發和翻譯等方面的工程師/專家的輸入，修改標準的WBS模板，形成包括了資源、成本、和時間進度估計的詳細計 戈闡述了技術文檔的開發和在線信息(信息計劃)的開發。W行銷計劃(考慮不同的地區和渠道)以及詳細的信息計劃，修改標準的WBS模板，形成包括了資源、成本、和時間進度估計的詳細計劃，闡述技術 文檔和在線信息的翻譯(翻譯計劃)Based on the high level BOM tree structure and a block diagram of the system design concept,as well as inputs from the

47、electrical, software, mechanical, industrial/user-centered design, modifythe standard WBS templates and develop a detailed plan with resource, cost and schedule estimates,to address the development of technical documentation and online information (information plan)Based on marketing plan (consider

48、different geographies and channels) and detailed informationplan, modify standard WBS template and develop detailed plan with estimates of resource, cost and timeschedule, to address translation of technical document and on-line information. (translation plan)產品數據結構設計Design ofProduct DataStructureSE

49、-99產品數據總體方案設計；產品結構樹設計；組織對產品結構樹評審。Design of overall product data plan; design of product tree structure; organize review of product treestructure.開發初始BOMDevelopInitialBOMSE-99APD潮動.使機器結構開發規范化并且在EC空制之下。開發這種清單以支持設計和模塊（build ）流程。找到在其它產品已經發布的已有部件編碼，如果已有部件不 能滿足產品規格的話，則申請新的編碼。PDM activity. Formalize develo

50、pment of the machine structure and placePROPDT-47Aunder ECcontrol. Develop the BOMsto support the design and build process. Identify existing part numbersthat have already been released on other products, and assign new part numbers if existing parts cannotbe found to satisfy product specifications.

51、如果提前采 購定單批準，向Oracle發 布初始BOM. Ifanticipatio norder is approved,then releaseinitial BOM toOracle.PROPDT-49PDM動PDM activity.技術評審3PerformTechnicalReview 3SE-100PQA-50TR3是在計劃階段對概要設計（HLD）的評審，確保設計規格已經完全、正確地在概 要設計中得到體現。TR3的結果將作為開發階段的后續詳細設計活動是否繼續投入資 源的根據。TR3 is the Plan Phase review of the High Level Design

52、（HLD） to ensure that design specification has beencompletely addressed, and that the design has been interpreted correctly and completely by sub-process designteams in functional areas as appropriate. TR3 forms the basis for the decision to commit resources for subsequentdetailed design activities d

53、uring Development PhaseTR3的準備活動包括各功能領域完成專項評審，在TR3的評審會上將由PDT核心團隊在綜合層面進行討論，確保概要設計足以指導產品項目計劃制訂、產品業務計劃制訂、 以及后續的詳細設計（LLD）活動。TR3 preparation and review activities include affirmation of functional specification reviews at thesub-process level as well as summary level discussion at the core team level to e

54、nsure that HLD is completeenough for subsequent IPD activities - establish Product Project Plan, establish Product Business Plan, andLLD.TR3的評審過程包括對概要設計各主要沖突點的討論，也需要跟蹤設計規格、共用模 塊重用計劃、產品策略、產品配置的落實情況。The TR3 session includes a summary level review of key conflicts of HLD. It also assesses the completen

55、essof the translation of the Design Specifications, Common Module Use Plan, Product Standards Strategies, and ProductConfiguration into HLD.TR3通過后產品所設計應被置于更改控制之下。After TR3 passes, the HLD shall beput under the change control.TR3的目的是確保： The objective of TR3 is to ensure that:a.概要設計（HL D）完備，足以指導后續的詳細設

56、計（LLD ）活動；The HLD iscomplete enough for subsequent LLD activities.b.保產品設計規格到概要設計 （HLD）之間的完備性；Ensure the completeness of the translationof design specifications into HLD.c.定位呻設計中的缺陷和限制，評估風險，形成規避策略和應急計劃。Gaps and limitations in HLD have been identified; risks evaluated, and mitigation strategies and ac

57、tion planshave been put in place.概要設計基 線化Set a Baseline forHigh Level DesignSE-1101、將評審通過的產品概要設計作為基線；2、對后續產品開發過程中產生的配置更改進行控制。1. Set the approved high level design as the baseline;2.Put configuration changes in follow up product development under change control.制定命名規則ConstituteNaming RulesMKTE-15在PDC

58、P通過之后，參考業界、競爭對手及公司已有的商標、命名規范制定產 品的命名規則。.優化信息安 全計劃Updateinformationsecurity planLPDT-59A優化概念階段制定的信息安全計劃Update the information security plan developed in concept phase.制定客戶服 務/支持計劃DevelopCustomerService andSupport PlanTSS-20時概要的BOM結構樹和系統設計概念框圖，以及來自硬件、軟件、結構、 工藝/以用戶為中心的設計產生的輸入，修改標準的WBS模板，形成包括資源、成本、和時間進度

59、估計的詳細計劃，闡述技術支持。（注，是和上支持，何時培訓辦事處和客戶，備件準備情況，是否在海外設 E、事處進行售后服務）Based on the high level BOM tree structure and a block diagram of the system design concept,as well as inputs from the electrical, software, mechanical, industrial/user-centered design, modifythe standard WBS templates and develop a detaile

60、d plan with resource, cost and schedule estimates,to address technical support制JE制造計 劃DevelopManufacturin gPlan AME-30偵略，更新標準的WBS模板，形成包括資源、成本、和時間進度估 計的詳細計劃，闡述如何制造產品；與采購一道決定哪些元器件或零件需要制造， 哪些應米購，部件在哪里制造(哪個地點，哪條生產線等等)。Based on the manufacturing strategy, update the standard WBS template and develop a detailedplan