Data item description



Download 29.09 Kb.
Date conversion25.05.2016
Size29.09 Kb.

DATA ITEM DESCRIPTION







Form Approved

OMB No. 0704-0188



Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503.










1. TITLE
PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

2. IDENTIFICATION NUMBER
FAA-SE-013


3. DESCRIPTION/PURPOSE
3.1 The Preliminary Design Review Data Package is required by the Government to permit adequate preparation for the Preliminary Design Review (PDR) prior to the review meeting.


4. APPROVAL DATE

(YYMMDD)


960501

5. OFFICE OF PRIMARY RESPONSIBILITY (OPR)
NOAA/NWS/OSO3

6a. DTIC APPLICABLE
N/A

6b. GIDEP APPLICABLE

N/A


7. APPLICATION/INTERRELATIONSHIP
7.1 This Data Item Description contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.
7.2 This DID is for one-time use for the ____ Production Contract.


8. APPROVAL LIMITATION

52-DGNW-6-90044



9a. APPLICABLE FORMS
N/A

9b. AMSC NUMBER
N/A

10. PREPARATION INSTRUCTIONS
10.1 Format. Contractor format is acceptable.
10.2 Content Requirements. The PDR data package shall provide sufficient documentation to confirm that the engineering analysis, design concepts, and design approach will:
a. Establish the basic design and preliminary engineering approach for the overall system.

b. Identify and describe the critical system, subsystem, and HWCI design , manufacturing, and performance problems

and risks.

c. Satisfy the Functional Baseline (FBL).

d. Ensure the total system is ready for detailed design.
The PDR data package will include:
10.2.1 Issues Data. Provide preliminary engineering and design data sufficient to identify resolution of critical issues.
10.2.2 System Design Data. Provide preliminary system, subsystem, and HWCI design requirements data for the following:
10.2.2.1 Design Balance. Provide information on considerations given to cost, schedule, performance, and risk for the life cycle. Include preliminary life cycle cost (LCC) analysis results of selected and alternative design approaches and equipment. Include discussion of effort to mitigate known risks and to make remaining risks acceptable. Provide documentation of risk

and problem resolution.






Block 10. Preparation Instructions (Continued)

10.2.2.2 Preliminary Design Data. Provide preliminary design data to validate the Functional Baseline

(Government specification and drawing requirements) and projected Allocated Baseline (ABL) including:
a. Description of basic design approach for the overall system.
b. System integration sketches, preliminary drawings, and schematic diagrams.
c. Shelter structural, electrical, and mechanical design concepts, preliminary sketches and drawings, and

schematic diagrams.


d. Commercial equipment drawings, product descriptions, and characteristics.
10.2.2.3 Audit Trail. Provide a complete set of proposed and approved configuration changes from the Functional Baseline (FBL), including backup and supporting material.
10.2.2.4 Baselines. Define and describe the Allocated Baseline (ABL). Identify changes to the Functional Baseline

as a basis for establishment of the Allocated Baseline.


10.2.2.5 Interface Design Data. Provide preliminary interface documents, interface drawings, and supporting

engineering data to define and verify external and internal interfaces.


10.2.3 Engineering Analysis Data. Provide systems engineering requirements analysis data to verify engineering decisions. Include sufficient engineering data to demonstrate achievement of specification requirements, and provide documentation describing preliminary engineering analysis of:
a. Basic engineering approach for the system.

b. Engineering specification and requirements review.

c. Preliminary engineering design reviews, studies, and computer program results.

d. Preliminary Reliability, Maintainability, and Availability ( RMA) review.

e. Preliminary Integrated Logistic Support (ILS) review, including spares, and test and support equipment.
10.2.4 Test and Evaluation (T&E) Support for Design Approach. Provide existing COTS historical test and evaluation results and supporting documentation (including available COTS test plans, methods, standards, and procedures).

Provide results of analysis and evaluation of T & E data, including documentation of performance, failures, reliability, maintainability, and cost.


DD Form 1664, APR 89 Previous editions are obsolete. Page 1 of 2 Pages




The database is protected by copyright ©essaydocs.org 2016
send message

    Main page