Definition General Info Policies Guides Communities Training Related
DEFINITION
The CDR is a multi-disciplined technical review to ensure that the system under review can proceed into system fabrication, demonstration, and test; and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints.
GENERAL INFORMATION/NARRATIVE
Generally this review assesses the system final design as captured in product specifications for each configuration item in the system (product baseline), and ensures that each product in the product baseline has been captured in the detailed design documentation. Product specifications for hardware enable the fabrication of configuration items, and may include production drawings. Product specifications for software (e.g., Software Design Documents) enable coding of a Computer Software Configuration Item. Configuration items may consist of hardware and software elements, and include items such as airframe, avionics, weapons, crew systems, engines, trainers/training, etc. Completion of the CDR should provide:
(1) An established system product baseline;
(2) An updated risk assessment for System Development and Demonstration;
(3) An updated Cost Analysis Requirements Description (CARD) (or CARD-like document) based on the system product baseline;
(4) An updated program development schedule including fabrication, test, and software coding critical path drivers; and
(5) An approved Product Support Plan with updates applicable to this phase.
For complex systems, the program manager may conduct a CDR for each subsystem or configuration item. These individual reviews would lead to an overall system CDR. When individual reviews have been conducted, the emphasis of the overall system CDR should focus on configuration item functional and physical interface design, as well as overall system detail design requirements. The CDR determines whether the hardware, human, and software final detail designs are complete, and whether the Integrated Product Team is prepared to start system fabrication, demonstration, and test.
The subsystem detailed designs are evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem, and whether the traceability of final subsystem requirements to final system detail design is maintained. At this review, the Integrated Product Team also reviews the results of peer reviews on requirements and final detail design documentation, and ensures that the latest estimates of cost (development, production, and support) are consistent with the detail design. A successful review is predicated on the Integrated Product Team's determination that the subsystem requirements, subsystem detail design, results of peer reviews, and plans for testing form a satisfactory basis for proceeding into system fabrication, demonstration and test.
The program manager should tailor the review to the technical scope and risk of the system, and address the CDR in the Systems Engineering Plan.
Typical CDR success criteria include affirmative answers to the following exit questions:
(1) Does the status of the technical effort and design indicate operational test success (operationally suitable and effective)?
(2) Does the detailed design, as disclosed, satisfy the Capability Development Document or any available draft Capability Production Document?
(3) Has the system product baseline been established and documented to enable hardware fabrication and software coding to proceed with proper configuration management?
(4) Has the detailed design satisfied Human Systems Integration (HSI) requirements?
(5) Are adequate processes and metrics in place for the program to succeed?
(6) Are the risks known and manageable for developmental testing and operational testing?
(7) Is the program schedule executable (technical/cost risks)?
(8) Is the program properly staffed?
(9) Is the program executable with the existing budget and the approved product baseline?
(10) Is the detailed design producible within the production budget?
(11) Is the updated CARD consistent with the approved product baseline?
(12) Are all Critical Safety Items and Critical Application Items identified?
(13) Does the updated cost estimate fit within the existing budget?
(14) Is the software functionality in the approved product baseline consistent with the updated software metrics and resource-loaded schedule?
(15) Have key product characteristics having the most impact on system performance, assembly, cost, reliability, or safety been identified?
(16) Have the critical manufacturing processes that impact the key characteristics been identified and their capability to meet design tolerances determined?
(17) Have process control plans been developed for critical manufacturing processes?
The program manager should conduct the CDR when the "build-to" baseline has been achieved, allowing production and coding of software deliverables to proceed. A rule of thumb is that 75% to 90% of (manufacturing quality) product drawings and associated instructions should be complete, and that 100% of all airworthiness critical component (Critical Safety Items and Critical Application Items) drawings are complete.
POLICIES, DIRECTIVES, REGULATIONS, LAWS
BEST PRACTICES, LESSONS LEARNED, STORIES, GUIDES, HANDBOOKS, TEMPLATES, EXAMPLES, TOOLS
COMMUNITIES OF PRACTICE
TRAINING RESOURCES
RELATED ARTICLES
Definition General Info Policies Guides Communities Training Related
