Optimizing U.S. Air Force and Department of Defense Review of Air Force Acquisition Programs (2009) / Chapter Skim
Currently Skimming:
Appendix E: Types of Reviews
Appendix E: Types of Reviews
Pages 88-106
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 88... ...
The Acquisition Strategy Panel supports the SAE and other MDAs. ASPs are forums that evaluate proposed acquisition strategies to ensure all key viable alternatives have been considered and that the best recommendation is provided to the SAE and/or the program's MDA for approval.
|
From page 89... ...
The AFROCC ensures Air Force capabilities-based requirements documentation is prepared in accordance with Air Force and Joint Staff guidance, complies with established standards, and accurately articulates valid Air Force capabilities-based requirements. The AFROCC reviews Air Force FSA study plans directed by JCDs, AFCDs and for initiatives forecast to become ACAT I programs.
|
From page 90... ...
3.7.1.4. For ACAT ID and ACAT IAMs, AFRBs are used to develop the AF cor porate consensus prior to an OSD Defense Acquisition Board (DAB)
|
From page 91... ...
The Defense Acquisition Guidebook describes the ASR as follows: The ASR is a multi-disciplined technical review to ensure that the resulting set of requirements agrees with the customers' needs and expectations and that the system under review can proceed into the Technology Development phase. The ASR should be complete prior to Milestone A
|
From page 92... ...
The Defense Acquisition Guidebook describes the CDR as follows: 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)
|
From page 93... ...
Defense Acquisition Executive Summary (DAES) The Defense Acquisition Guidebook describes the DAES as follows:10 The DAES is a multi-part document, reporting program information and assess ments; program manager, Program Executive Officer, CAE comments; and cost and funding data.
|
From page 94... ...
Department of Defense Instruction 5000.2 described the DRR as follows: 11 The Design Readiness Review during SDD provides an opportunity for mid phase assessment of design maturity as evidenced by measures such as the number of subsystem and system design reviews successfully completed; the percentage of drawings completed; planned corrective actions to hardware/ software deficiencies; adequate development testing; an assessment of environ ment, safety and occupational health risks; a completed failure modes and effects analysis; the identification of key system characteristics and critical manufactur ing processes; an estimate of system reliability based on demonstrated reliability rates; etc. Successful completion of the Design Readiness Review ends System Integration and continues the SDD phase into the System Demonstration effort.
|
From page 95... ...
Functional Configuration Audit (FCA) Military Handbook 61A describes the FCA as follows:13 The Functional Configuration Audit (FCA)
|
From page 96... ...
15 ational Security Space Acquisition Policy 03-01, Guidance for DoD Space System Acquisition N Process, December 27, 2004. 16 efense Acquisition Guidebook, Section 11.3.3.3, Integrated Baseline Reviews (IBRs)
|
From page 97... ...
17 Defense Acquisition Guidebook, Section 10.3, Role of Integrated Product Teams (IPTs)
|
From page 98... ...
The Defense Acquisition Guidebook describes the OIPT as follows:21 All Acquisition Category ID and IAM programs will have an OIPT to provide assistance, oversight, and review as the program proceeds through its acquisition 19 anufacturing Readiness Assessment (MRA) Deskbook [draft]
|
From page 99... ...
The OIPT charters the Integrating Integrated Product Team and Working level Integrated Product Teams. The OIPT should consider the recommendations of the Integrating Integrated Product Team regarding the appropriate milestone for program initiation and the minimum information needed for the program initiation milestone review.
|
From page 100... ...
Post Critical Design Review Assessment (PCDRA) Department of Defense Instruction 5000.02 describes the PCDRA as follows:23 22 efense Acquisition Guidebook, Section 4.3.4.4.3, Physical Configuration Audit (PCA)
|
From page 101... ...
Preliminary Design Review (PDR) The Defense Acquisition Guidebook describes the PDR as follows:24 24 Defense Acquisition Guidebook, Section 4.3.3.4.4, Preliminary Design Review (PDR)
|
From page 102... ...
Production Readiness Review (PRR) The Defense Acquisition Guidebook describes the PRR as follows:25 The PRR examines a program to determine if the design is ready for production and if the producer has accomplished adequate production planning.
|
From page 103... ...
The Defense Acquisition Guidebook describes the SFR as follows:29 The SFR is a multi-disciplined technical review to ensure that the system under review can proceed into preliminary design, and that all system requirements and functional performance requirements derived from the Capability Development Document are defined and are consistent with cost (program budget) , schedule (program schedule)
|
From page 104... ...
The Defense Acquisition Guidebook describes the SVR as follows:31 The SVR is a multi-disciplined product and process assessment to ensure that the system under review can proceed into Low-Rate Initial Production and Full Rate Production within cost (program budget) , schedule (program schedule)
|
From page 105... ...
Technology Readiness Assessment (TRA) The Defense Acquisition Guidebook describes the TRA as follows:32 The TRA is a systematic, metrics-based process that assesses the maturity of Critical Technology Elements.
|
From page 106... ...
106 OPTIMIZING USAF AND DOD REVIEW OF AIR FORCE ACQUISITION PROGRAMS to support planned tests. The TRR verifies the traceability of planned tests to program requirements and user needs.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.