IPD Learning Notes: Key Elements of Technical Reviews in Product Development

IPD Background

The IPD methodology originates from PACE theory by PRTM in the United States and was refined through IBM practice; it now represents a systematic engineering approach covering product development ideas, models, and tools.

The IPD process is divided into six stages—Concept, Planning, Development, Verification, Release, and Lifecycle—with clearly defined decision review points that focus on business aspects such as market positioning and profitability rather than pure technical reviews.

TR1 Review Elements

Coverage Across Departments

IPD Concept‑stage TP1 product‑package requirement review mandates cross‑functional verification covering finance, quality, market, the entire R&D chain (SE/hardware/software/structure/hardware testing), and procurement, enabling early risk control before development.

Core Control Objectives per Module

Finance: lock cost baseline to avoid budget overruns.

Quality: pre‑plan industry certification to prevent rework.

Market: align product positioning with commercial goals.

SE (System Engineering): ensure overall solution feasibility and top‑level requirement validation.

Hardware/Software/Structure: assess technical, process, and implementation feasibility per domain.

Hardware Testing: evaluate test resources, reliability, and testability risks early.

Procurement: identify material, supplier, and supply‑risk upfront to guarantee volume production.

TR2 Review Checklist (Planning Stage)

Checklist Purpose

This checklist standardizes cross‑department verification of the overall solution in the planning stage, building on TP1 outputs. It validates product design specifications, technical方案, cost, testing, and supply‑chain feasibility before moving to domain‑level preliminary design (TR3).

Key Control Points per Function

Finance: provide decomposed cost indicators to constrain subsequent hardware/structure/software design costs.

Quality: lock customer quality, agreement, and certification baselines to avoid later compliance rework.

Market: verify commercial match of product specs and monitor market‑driven competitive risk.

SE System Engineering: bind requirement‑to‑design specifications, establishing a traceability baseline.

Hardware/Software/Structure/ID: finalize overall方案, hardware‑software split, and preliminary appearance/process design.

Hardware/Software Testing: draft test plan early to identify resource and standard risks.

TR3 Review Checklist (Preliminary Design)

Checklist Purpose

This checklist standardizes the domain‑level preliminary design review, inheriting TR2 outputs. It verifies that hardware, software, and structure designs meet product specifications, performance, DFX, cost, and certification requirements, serving as the final gate before detailed development.

Key Control Points per Function

Finance: lock cost aggregation rules, ensuring material and functional module costs align with system方案.

Quality: confirm quality targets and certification plan approval, establishing a quality baseline for development.

Market: validate commercial fit of design, synchronize promotion material and prototype delivery schedule to control launch timing.

SE System Engineering: coordinate full‑module design implementation, focusing on DFX (EMC, safety, thermal) and defect closure.

Hardware R&D: complete key material and electrical performance reviews to ensure hardware feasibility.

Software R&D: cover selection, certification, schedule, collaboration model, schematic alignment, and IP across six dimensions, pre‑empting software risks.

TR4 Review Checklist (Detailed Development)

Checklist Purpose

This checklist standardizes detailed module development verification, building on TR3 outputs. It validates detailed implementation, self‑testing, structural prototype verification, cost variance control, and pre‑mass‑production readiness, acting as a critical gate before full‑machine trial.

Key Control Points per Function

Finance: analyze cost variance between design phase actuals and initial targets, locking cost‑reduction actions.

Quality: pre‑control PCBA sealing, material traceability, and certification sample preparation.

Market: align prototype delivery and launch pacing, assess schedule risk from requirement changes.

SE System Engineering: verify all modules meet previously defined design specs, maintaining overall方案 baseline.

Hardware/Software R&D: complete unit development, hardware‑software integration, self‑test verification, and meet production‑readiness criteria; close all defects.

Structure R&D: finalize detailed mold design, CNC prototype assembly verification, and overall tolerance checks to avoid assembly defects.

TR5 Review Checklist (Integration Trial)

Checklist Purpose

This checklist standardizes full‑machine integration trial verification, inheriting TR4 outputs. It focuses on cross‑dimensional validation after integration, pre‑production material/tooling/certification preparation, and change control, serving as the core gate before small‑batch trial production.

Key Control Points per Function

Finance: solidify cost‑variance conclusions, lock cost‑control baseline for mass production.

Quality: complete full‑process material traceability, testing fixtures, certification sampling, and sealing plan to pre‑empt material and compliance risks.

Market: verify prototype delivery rhythm, ensure no major requirement changes, and stabilize launch plan.

SE System Engineering: enforce cross‑department change review to avoid large‑scale rework after integration.

Hardware R&D: complete antenna integration, full‑machine safety/EMC/reliability testing, and eliminate high‑level hardware defects.

Software R&D: freeze requirement baseline, achieve functional implementation targets, and drive defect remediation per milestone.

Structure R&D: resolve trial assembly and appearance tolerance issues, continuously close critical structural defects, and meet environmental test criteria.

TR6 Review Checklist (Mass‑Production Admission)

Checklist Purpose

This checklist is the final gate before formal mass production, inheriting TR5 outputs. It covers five dimensions—customer contract fulfillment, compliance certification closure, complete technical documentation archiving, full requirement realization, and material standardization verification.

Key Control Points per Function

Finance: lock mass‑production cost baseline and confirm controllable cost variance.

Quality: complete certification and sealing processes, close quality targets, and eliminate compliance risks.

Market: secure first‑batch customer contracts, validate market promotion effectiveness, and control new requirement change risk.

SE System Engineering: verify full requirement implementation and pre‑identify defects affecting shipment.

Hardware: archive full set of drawings and service manuals; ensure hardware specifications meet standards.

Software: achieve full requirement coverage, defect convergence, and meet delivery acceptance standards.

Structure: archive BOM, certify material samples, validate multi‑supplier part compatibility, and continuously eliminate major structural defects.

Implementation Recommendations

Before review meetings, each function should provide archived checklists, certification reports, defect‑convergence logs, and customer contract documents as evidence.

Focus on four high‑risk “no‑go” items: unsealed materials, missing drawings, unresolved software defects, and unsigned core customers.

Define remediation milestones and owners for any residual issues, establishing pre‑release conditions.

Differences Between TR5 and TR6

Market: TR5 assesses prototype promotion; TR6 requires signed first‑batch customers and commercial launch readiness.

Quality: TR5 prepares certification samples; TR6 demands completed certification and issue remediation.

Documentation: TR5 has no archiving requirement; TR6 mandates full BOM, drawings, and service manual archiving.

Requirement Verification: TR5 controls development schedule; TR6 requires 100 % requirement realization and impact assessment of defects on shipment.

Structure Materials: TR6 adds multi‑mold, multi‑supplier part compatibility, FAI dimension acceptance, and material‑sign‑off checks.

LDCP Review (Product Release Decision)

LDCP (Life Decision Check Point) is the company‑level commercial release gate covering finance, quality, market, full R&D, and procurement. It ensures cost control, complete certification, guaranteed customer delivery, full requirement validation, and supply‑chain readiness for batch production.

Key Control Points per Function

Finance: lock final cost variance and confirm controllable mass‑production cost.

Quality: achieve all quality targets, archive certification certificates, and eliminate compliance risks.

Market: guarantee first‑batch customer delivery, meet promotion effectiveness, and avoid major requirement changes.

SE System Engineering: validate full requirement implementation and ensure complete product functionality.

Hardware/Structure R&D: realize all specifications and close requirement verification loops.

Software R&D: clear high‑level defects and meet delivery quality standards.

Hardware/Software Testing: complete SVT and Beta testing, archive full test reports.

Procurement: ensure full BOM material certification, quality, orders, and ERP readiness for batch delivery.

Implementation Recommendations

Before the review, each function should supply complete evidence: cost reports, certification certificates, test reports, BOM, orders, and customer contracts.

Four “one‑vote‑no” items must be checked: unresolved high‑level defects, missing certification archives, unready BOM, and unguaranteed first‑batch delivery.

Specify remediation nodes and responsible owners for any leftover issues, setting pre‑release conditions.

Differences Between LDCP and TR6

Decision Level: TR6 is a technical mass‑production admission; LDCP is a company‑wide commercial release decision.

Scope: LDCP adds full‑chain procurement, first‑batch delivery, and complete test‑report archiving.

Defect Requirement: TR6 permits some serious issues to remain tracked; LDCP requires closure of all fatal and serious issues.

Supply‑Chain Requirement: LDCP demands official BOM release, ERP go‑live, and batch order readiness for mass delivery.

Market Requirement: LDCP mandates executable first‑batch delivery plans and validated promotion effectiveness for commercial operation.