Scribd
Upload
144 views3 pages

ADC.F.7 Preliminary Design Review

The document outlines the requirements and participants for a Preliminary Design Review (PDR) meeting. The objective of the PDR is to check that the preliminary aircraft design complies with requirements and identifies any design risks. The review requires documentation of the design, interfaces, and risk assessment to be provided in advance. Participants must include heads of design organizations, compliance engineers, and customer representatives. The output is an evaluation of the design maturity and risks, and a determination of whether the project can proceed to detailed development.

Uploaded by

mycopteraviation
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
144 views3 pages

ADC.F.7 Preliminary Design Review

The document outlines the requirements and participants for a Preliminary Design Review (PDR) meeting. The objective of the PDR is to check that the preliminary aircraft design complies with requirements and identifies any design risks. The review requires documentation of the design, interfaces, and risk assessment to be provided in advance. Participants must include heads of design organizations, compliance engineers, and customer representatives. The output is an evaluation of the design maturity and risks, and a determination of whether the project can proceed to detailed development.

Uploaded by

mycopteraviation
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Code:

PRELIMINARY DESIGN REVIEW


Revision:

Project Title:
Date:

Project Ref No:

Objective :
The objective of the Preliminary Design Review (PDR) is to check the preliminary design compliance with customer
& airworthiness requirements, and the acceptability of the residual level of risk.

Review Pre-requisite:
To be performed during the development phase when the preliminary design is adequately mature (including interfaces)
and approval to proceed with modification has been granted by ADC .The following inputs must be provided to the
essential participants 3 working days before the review:
 Master Document List (MDL)
 Modification Classification Record (MCR)
 Type Investigation Plan
 Preliminary design – interface definition
o Structures – general arrangement, preliminary design, interfaces with physical characteristics defined
o Avionics – power requirements, equipment requirements, interfaces with equipment architecture defined
o BOM - list of main components
 Project Status (Budget, Project Plan)
 Risk Assessment (review all supplier data)
** Where more than one engineering discipline is involved in a design stage, the review is done properly by authorised
persons from each discipline represented during the discussion.

Participants
Mandatory Nice to have Present
Head of Design Organisation X
Compliance Verification Engineer X
Show Compliance Engineer X
Airworthiness Engineer X
Independent Monitoring Officer X
Finance X
Customer X
Authority (i.e DCAM, DGTA) X

Page 1 of 3
ADC.F.7/Oct 2011
REQUIRED OUTPUTS Applicable? Considered? Risk evaluation: Action
(Y or NA) (Y or N) A , B or C* number
Are the actions raised during the previous discussions closed?

Is the documentation list (MDL) available & agreed?

Are the Design files (preliminary drawings, physical


characteristics (weight, size), pre-dimensioning (computation
files), functional and physical interfaces available?
Are the preliminary design data compliant with customer
requirements & technical specification?
Are the performance and limitations defined and accepted?
Are all possible tests needed for certification defined?
Are the preliminary weight and gravity center breakdowns
defined, reviewed and accepted?
Are all maintainability impacts defined & accepted?

Is the preliminary design taking into account Production


constraints?
Are equivalent projects known and solutions on this project
implemented? Are all existing substantiation & supplier
data critically reviewed?
Is the Type Investigation Plan available and agreed?
Are all development & design risks defined in accordance with
ADC standard?
Is the project schedule & budget reviewed and updated
(consistent with resource availability)?
Are lessons learned from this step identified?

Conclusion of the review:


Is the preliminary design mature enough to launch the
detailed development phase?
* A = risks not acceptable so need to stop, B = significant risks so need to have an action defined to mitigate this risk with a short term
target, C = low risk so an action can been defined with a mid term target

Page 2 of 3
ADC.F.7/Oct 2011
Quality Gate status:
This section is assessed (circle decision) and approved by HODO.
APPROVED BY:

Gate is passed without any reserve.

Gate is passed with reserves and the following phase can


be launched only after a more detailed analysis of the
incurred risks and validation of the acceptability of these
risks

Gate is not passed and cannot be passed as long as the


reserves are not treated.

NOTE :

Page 3 of 3
ADC.F.7/Oct 2011

You might also like