PDR CDR Entry Exit Criteria.docx

PDR/CDR Entry/Exit Criteria

Preliminary Design Review (PDR) Overview

2. To ensure the functional baseline has been fully defined and optimized, including its functional decompositions, architectural arrangements, performance requirements, and external and internal hardware and software interfaces.

3. To review the preliminary design-to baseline, as expressed by schematic drawings and layouts, and confirm that it satisfies the functional baseline, as well as the requirements for manufacturing and supportability.

4. To review the adequacy and maturity of manufacturing, verifications, validation, quality, safety plans, airworthiness plans, support equipment, and support plans.

5. To review the risks identified and progress of mitigation plans.

PDR Entry Criteria

· A001 Conference Agenda

· A003 Presentation Material

CDRL Data Items (See contract)

· All required deliverables have been delivered to the government with adequate time provided for proper review and consideration:

· A015 Software Development Plan

· A016 System/Subsystem Specification (SSS)

· A017 Software Requirements Specification (SRS)

· A018 Software Design Description (SDD)

· A019 Interface Design Description (IDD)

· A028 Systems Engineering Management Plan (SEMP)

· A037 Test Plan

· A040 Test & Evaluation Program Plan (TEPP)

· A044 System Safety Hazard Analysis Report (SSHA)

· A045 Safety Assessment Report (SAR)

· A047 System Safety Plan

· A050 Product Drawing/Models &Associated Lists

· A062 System/Subsystem Design Description (SSDD)

· A063 Database Design Description (DBDD)

· Detailed definition of all SILs being developed

· Location of all SILs

· Definition of how the SILs are being used to support CDR preparation activities

· Definition of how the SILs will be used to eliminate risks prior to modifying the test aircraft

· Definition of how the SILs will be used to obtain aircraft certification

· Definition of how the SILs will be used to provide long term support for the aircraft

· A025 Management Plan

· A033 Integrated Master Schedule (IMS)

· Issues identified and corrective action plans developed

· Opportunities identified and achievement plans developed

· Mitigation, corrective action, achievement plans captured in RIO database

PDR Exit Criteria

· Verification matrices have been updated to reflect all requirement changes.

· The PDR package included an overview of all changes, additions, and or deletions from the requirements

· The review package presented sufficiently establishes, to the government’s satisfaction, that the design-to baseline accomplishes the following:

· Satisfies the functional baseline

· Establishes the allocated baseline

· Layout drawings and schematics clearly define interfaces with external systems, interfaces between each independent system element, and interfaces within each independent element down to the subsystem level or below.

· Addresses connectors, wiring, and cabling considerations (spare pins, sealing plugs, routing, cable bend radii, etc.)

· Uses standard parts, materials and equipment to the maximum extent possible.

· Meets all environmental criteria (cooling, air flow, shock mounting, etc.).

· Incorporates built-in test (BIT) and direct fault indicators (fault light, audio signal, data terminal messaging, etc.)

· Identifies any special handling requirements.

· Meets all packaging requirements.

· Includes human integration design factors

· Minimizes the use of hazardous or limited shelf life items.

· Is producible with existing/available manufacturing processes.

· Identifies any new manufacturing processes required.

· Is sufficiently mature and complete to begin critical design efforts

· Software trade studies which address Commercial-off-the-shelf (COTS), reuse, and other software related issues have been completed.

· The computer system and software architecture design has been established.

· Software increments have been defined and capabilities allocated to specific increments

· All Computer Software Configuration Items (CSCIs), Computer Software Components (CSCs), and Computer Software Units (CSUs) have been defined.

· The Software Requirements Specification (SRS) is defined with complete interface and verification requirements for all Computer Software Configuration Items (CSCIs), Computer Software Components (CSCs), and Computer Software Units (CSUs) that satisfy all system/subsystem functional requirements.

· An overview of mission goals, key functionality and operational characteristics of the software was provided.

· The PDR software design reflects that all system requirements have been allocated, complete and flow down to verify system performance.

· The PDR software design includes a complete and comprehensive presentation of the entire design by means of block diagrams, flow diagrams, signals flow diagrams, interface circuits, software logic flow and timing diagrams.

· Fault detection, Isolation, and Recovery (FDIR) strategies were discussed.

· Resource estimates were presented for CPU usage, memory, databases, and data storage.

· Error handling and recovery strategies were discussed.

· Software development environment and test/integration labs have been established with sufficient fidelity and capacity to meet schedule requirements.

· Software development schedules reflect contractor software processes for current and future development phases, including adequate timelines for validation, verification and re-qualification of red-label software during SIL and aircraft testing phases.

· Unique software risks have been identified assessed, and mitigation plans developed and implemented.

· Software metrics have been identified and reporting processes implemented to actively track and assess success/progress.

· Various test levels (unit testing, integration testing and system testing) have been scheduled.

· Software test methodology addresses all CSCI plans, test facilities, test data, tools, and test plans, including testing required to support incremental approaches (e.g. regression tests).

· Software configuration/change control procedures are in place and documented.

· Software development estimates (i.e. size, effort (cost), and schedule) have been updated and are deemed adequate to proceed.

· Risks associated with Environmental, Safety and Occupational Health (ESOH) hazards can be mitigated to an acceptable risk level within the existing budget.

· The design-to baseline is maintainable under the current USAF maintenance concept with any additional support material or equipment defined.

· Test and support equipment required to support the design has been identified and documented.

· Product support and sustainment requirements have been defined with appropriate metrics to ensure supportability

· Critical sustainment enabler technologies are sufficiently mature to implement the support strategy and achieve needed material availability

· The test plan and procedures are fully integrated and use all available resources to reduce overlap of FAA and Government certification requirements and maximize test aircraft usage.

· Risks are known and manageable for integrated testing and developmental/operational evaluation (DT&E/OT&E)

· The technical effort and design indicate operational test and evaluation will be successful (operationally effective and suitable)

· The program is executable within the existing budget and established allocated baseline

· The updated management plan and schedule includes system and software critical path drivers

· Review artifacts demonstrate progress sufficient to support proceeding according to the project plan.

· The program schedule is executable, based on known technical and cost risk.

· Adequate processes and metrics are in place for the program to succeed.

· A002 Conference Minutes

Critical Design Review (CDR) Overview

2. To review the detailed build-to baseline, as expressed by drawings, schematics and associated lists, to confirm that it:

a. Completely defines, and is traceable to, design requirements

b. Is balanced across cost, schedule, performance, and risk for the life of the product

c. Is compatible with external interfaces, including people, processes, and other products

d. Is compatible with test and evaluation results (hardware qualification, software, etc.)

3. To review the adequacy and maturity of manufacturing, verifications, validation, quality, safety plans, airworthiness plans, supplier coordination documents, supplier orders, support equipment, and support plans.

4. To review the risks identified and progress of mitigation plans.

CDR Entry Criteria

· A001 Conference Agenda

· A003 Presentation Material

CDRL Data Items (See contract)

· All required deliverables have been delivered to the government with adequate time provided for proper review and consideration:

· A009 Contractor’s Configuration Management Plan (CCMP)

· A010 Interface Control Document (ICD)

· A012 Proposed Spare Parts List (PPSL)

· A013 Parts List

· A014 Failure Mode, Effects, Criticality Analysis (FMECA) Report

· A015 Software Development Plan

· A016 System/Subsystem Specification (SSS)

· A017 Software Requirements Specification (SRS)

· A018 Software Design Description (SDD)

· A019 Interface Design Description (IDD)

· A021 Software Test Description (STD)

· A023 Software Product Specification (SPS)

· A037 Test Plan

· A040 Test & Evaluation Program Plan (TEPP)

· A047 System Safety Plan

· A048 Performance Specification Documents

· A050 Product Drawing/Models &Associated Lists

· A055 Technical Manual Contracts Requirement (TMCR) for KC-10 CNS/ATM

· A058 Training Facility Report

· A059 Training Program Structure Document

· A060 Instructional Media Package

· A061 Mission/Task Analysis Report (MTAR)

· A062 System/Subsystem Design Description (SSDD)

· A063 Database Design Description (DBDD)

· A064 Technical Manual Contracts Requirement (TMCR) for KC-10 Aircrew Training System (ATS)

· Location of all SILs

· Definition of how the SILs have been used to support CDR preparation activities

· Definition of how the SILs will be used to eliminate risks prior to modifying the test aircraft

· Definition of how the SILs will be used to obtain aircraft certification

· Definition of how the SILs will be used to provide long term support for the aircraft

· A025 Management Plan

· A033 Integrated Master Schedule (IMS)

· Issues identified and corrective action plans developed

· Opportunities identified and achievement plans developed

· Mitigation, corrective action, achievement plans captured in RIO database

CDR Exit Criteria

· Verification matrices have been updated to reflect all requirement changes since PDR.

· The CDR package included an overview of all changes, additions, and or deletions from the requirements since PDR.

· The review package presented sufficiently establishes, to the government’s satisfaction, that the build-to baseline accomplishes the following:

· Satisfies the allocated baseline

· Establishes the product baseline

· Final drawings, schematics and wiring diagrams clearly define interfaces with external systems, interfaces between each independent system element, and interfaces within each independent element down to the subsystem level or below.

· Addresses connectors, wiring, and cabling considerations (spare pins, sealing plugs, routing, cable bend radii, etc.)

· Uses standard parts, materials and equipment to the maximum extent possible.

· Meets all environmental criteria (cooling, air flow, shock mounting, etc.).

· Incorporates built-in test (BIT) and direct fault indicators (fault light, audio signal, data terminal messaging, etc.)

· Identifies any special handling requirements.

· Meets all packaging requirements.

· Includes human integration design factors

· Minimizes the use of hazardous or limited shelf life items.

· Is producible with existing/available manufacturing processes.

· Identifies any new manufacturing processes required.

· Specifies verifications necessary to qualify product

· Is supported by analysis and prototype test and evaluation results

· Is complete with drawings and supporting documentation finalized.

· Proper configuration management processes are in place to maintain configuration control of all hardware and software configuration items

· Interface Control Documents (ICDs) trace all software interface requirements to the CSCIs and CSUs

· A final software architecture design is defined

· The CDR software design includes a complete and comprehensive presentation of the entire design by means of logic flow diagrams, signals flow diagrams, interface circuits, software logic flow and timing diagrams.

· An overview of mission goals, key functionality and operational characteristics of the software was provided.

· The computer system and software architecture design has been confirmed through analyses, demonstrations, and prototyping in a relevant environment.

· Status of all IV&V activities was provided.

· Updates to resource estimates were presented for CPU usage, memory, databases, and data storage.

· Software test scenarios are consistent with the Software Test Plan

· Unit and integration testing has been completed and the software is sufficiently complete to prepare for system testing on the aircraft.

· The design-to baseline is maintainable under the current USAF maintenance concept with any additional support material or equipment defined.

· Product support and sustainment requirements have been defined with appropriate metrics to ensure supportability

· Critical sustainment enabler technologies are sufficiently mature to implement the support strategy and achieve needed material availability

· The test plan and procedures are adequate to define critical test requirements for system validation and verification

· The test plan and procedures are fully integrated and use all available resources to reduce overlap of FAA and Government certification requirements and maximize test aircraft usage.

· Risks are known and manageable for integrated testing and developmental/operational evaluation (DT&E/OT&E)

· The technical effort and design indicate operational test and evaluation will be successful (operationally effective and suitable)

· The program is executable within the existing budget and established product baseline

· The updated management plan and schedule includes system and software critical path drivers

· Review artifacts demonstrate progress sufficient to support proceeding according to the project plan.

· The program schedule is executable, based on known technical and cost risk

· Adequate processes and metrics are in place for the program to succeed.

· A002 Conference Minutes

Note: The listing provided is representative, but not limited to the areas to be covered during the review process. The contractor should be prepared to discuss the configuration and maturity of all programmatic and technical areas of concern as they relate to the development of the program at any point in the development process.