How IPD Structures Technical Review: A Step‑by‑Step Process Guide

IPD Foundations

The Integrated Product Development (IPD) methodology originates from the PACE theory of PRTM (USA) and was refined through IBM practice. IPD defines six phases—concept, planning, development, verification, release, and lifecycle—and inserts clear decision‑gate points that evaluate market positioning and profitability rather than pure technical criteria. Advancement to the next gate requires completion of the prescribed work.

Standardized Technical Review Workflow

A unified technical review process spans four stages: preparation, pre‑meeting communication, on‑site review, and post‑review archiving. System Engineers (SE) and Process Quality Assurance (PQA) jointly manage the workflow, which applies to all technical gates TR1 through TR6 and the commercial gate LDCP.

Stage‑Control Value

Pre‑meeting control (‑3 days ~ ‑0.5 day) : complete material preparation, distribution, expert pre‑reading, and issue pre‑sorting to avoid prolonged meetings and information asymmetry, thereby boosting efficiency.

On‑site three‑phase meeting (Report – Discussion – Summary) : a standardized structure guarantees full material presentation, thorough discussion, and actionable conclusions; all issues are recorded with remediation plans.

Post‑meeting closure (+1 day) : hierarchical approval and unified archiving create review assets that serve as the release basis; without archived assets the next development activity cannot start, achieving a closed‑loop control.

Core Control Rules

Dual‑role governance: SE ensures technical completeness; PQA ensures process compliance and supervises documentation throughout the cycle.

Pre‑review requirement: every stage must distribute materials and allow expert pre‑reading; meetings without pre‑reading are prohibited.

Stage release threshold: the next development stage cannot commence until the Technical Review Report is approved and archived.

Applicable scope: all IPD technical gates (TR1‑TR6) and the commercial decision gate (LDCP) use this unified process.

TR6 Production Admission Review (Technical Gate)

TR6 focuses on product technical specifications, material readiness, certification status, and prototype commercialization prerequisites. Completion of the TR6 technical review permits trial production but does not guarantee full‑scale market delivery.

LDCP Product Release Decision Review (Commercial Gate)

LDCP is the company‑level launch approval node. Building on TR6 closure, it adds full‑scale testing closure, complete supply‑chain procurement verification, and batch‑customer delivery guarantees. All critical or severe issues must be eliminated (100 % clearance) before approval.

Gate Differences

The diagram below contrasts TR6 and LDCP criteria, highlighting that TR6 validates technical trial readiness while LDCP requires full testing, supply‑chain clearance, and zero critical defects.

Overall Control Logic

TR6 Production Admission : technical trial‑run release gate; the standardized review checks financial, quality, market, and technical baselines to ensure readiness for limited batch production.

LDCP Product Release Decision : company‑level launch gate; on top of TR6 closure it adds full‑test closure, complete supply‑chain verification, and batch delivery assurance. Only after all critical defects are cleared can the product be mass‑delivered.

Both gates share the same pre‑meeting, on‑site, and post‑archiving workflow, coordinated by SE and PQA across all functional departments. Review artifacts are archived as the sole evidence for stage release, internal audit, and retrospective tracing.

Execution Requirements

All TR6 and LDCP reviews must follow the sequential process; skipping pre‑reading or pre‑communication is prohibited.

TR6 grants only technical trial release; full market supply requires subsequent LDCP approval.

LDCP veto items: any unresolved critical/severe defect, supply‑chain BOM not approved by ERP, missing first‑batch delivery plan, or unarchived certification.

Each review produces a Technical Review Report; only after hierarchical approval and archiving can the next stage begin.

Technical Review Best Practices

Identify both strengths and weaknesses, discuss problems and risks thoroughly, and avoid omitting reviews due to schedule pressure.

Standardize the review process; allocate sufficient pre‑reading time to improve efficiency.

Post‑review measurement and execution of conclusions are essential; findings must be acted upon.