An aerospace and automotive concept defining a technical component, process, or performance measure used in vehicle design, production, or operation. It applies when relevant engineering prerequisites are satisfied and produces defined effects on safety, efficiency, reliability, or manufacturability. It does not ensure outcomes without validated design assumptions and appropriate testing and controls. It materially affects lifecycle performance and cost by influencing design tradeoffs, verification effort, and operational robustness. The concept is generally stable, though methods and standards evolve as technology advances over time.

Principle

Confirm that system requirements have been allocated to subsystems, key interfaces are identified, preliminary analyses indicate feasibility, and major risks are recognized and mitigable prior to detailed design work.

Demonstration

The systems team presents architecture diagrams, requirement allocation matrices, trade-study summaries, preliminary interface control documents, and risk registers showing mitigation plans to support progressing to the detailed design phase.

Misapplication

Using PDR to justify an immature architecture or skipping rigorous requirement allocation, which leads to rework during detailed design or missed requirements during integration.

Consequence

A correct PDR clarifies design direction, bounds system performance expectations, and identifies focus areas for detailed engineering, reducing late-stage surprises and cost growth.

Reversal

Reversal would be to proceed to detailed design without a coherent allocation of requirements or defined interfaces, turning the PDR into an administrative checkbox rather than a decision point.

Boundary

Applies to system-level design maturity and feasibility for further design; it does not verify detailed drawings, manufacturing readiness, or full verification testing.

Semantic Tension

Often contrasted with CDR: PDR assesses conceptual and architectural maturity, while CDR demands detailed, verifiable designs ready for production or construction.

Synthesis

A Preliminary Design Review establishes that the chosen architecture, requirements allocation, and identified mitigations form a credible path to detailed design, balancing feasibility, risk, and program constraints.