New Acquisition Policy Changes for Systems Engineering November 12, 2008 Don Gelosh, Ph.D., CSEP-Acq Senior Systems Engineer Systems Engineering Support Office Enterprise Development/Systems and Software Engineering Office of the Deputy Under Secretary of Defense (A&T) PRE-DECISIONAL: DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working paper. Do not release under FOIA. This briefing includes draft policy language that has not been formally reviewed or approved. NOT FOR GENERAL DISTRIBUTION
Bottom-line Upfront National Research Council Pre-Milestone A and Early-Phase Systems Engineering Jan 2008 DoD 5000.02 changes emphasize early stages of pre-systems acquisition - prior to Milestone B Reduce risk before making business commitment Improve likelihood of being able to meet commitments Changes mean new challenges for the program during this early period Early systems engineering is a key enabler Recent studies acknowledge early SE benefits Provides technical foundation for Milestone B decision DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 2
Draft 5000.02 Elevates Recognition of Systems Engineering and Risk Reduction PDR or PDR** CDR Materiel Development Decision (MDD) Competing prototypes before MS B PDR & PDR report to the MDA or PDR and Post- PDR- Assessment Decision Point Systemlevel CDR with an initial product baseline & a Post-CDR Report to the MDA Post-CDR Assessment by the MDA between EMD subphases Renewed emphasis on manufacturing across the life-cycle Re-titles SDD phase to EMD with two sub phases: - Integrated System Design and - System Capability and Manufacturing Process Demonstration Establishes consideration of manufacturing maturity at key decision points ** If no PDR is held prior to MS B, mandatory PDR and decision point occur after MS B DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 3
Draft 5000.02 and Guidance Address Reliability, Availability, and Maintainability (RAM) Life-cycle sustainment planning The LCSP shall be updated and May 2007: CJCSI RAM strategy: shall 3170.01F be considered and CJCSM during An executed LCSP shall during be 3170.01C require: Includes a Materiel reliability Solution growth Analysis, program and Production prepared and for Deployment as an integral part Sustainment of design and (Materiel shall development mature Availability) throughout KPP and Operations Milestone and B. Support. Prior to beginning EMD, users shall Two Integrated supporting within Technology Key the Systems Development. Attributes Engineering processes identify and the requirements (KSA): Documented in the program s Systems Engineering authority shall approve a minimum Plan (SEP) and Life-Cycle Sustainment Plan (LCSP) Materiel Reliability set of Key Performance Parameters Assessed during technical reviews, test and evaluation (KPPs), included in the CDD, that (T&E), Ownership and Program Cost Support Reviews (PSRs). Mandatory for JROC Interest Programs shall guide the efforts of this phase. Effective sustainment of systems results from the design and development of reliable and maintainable systems through the continuous application of a robust systems engineering methodology. DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 4
Defense Acquisition Guidebook Provides 20 Design Considerations Diminishing Manufacturing Sources and Material Shortages Accessibility Unique Identification of Items Reliability, Availability, and Maintainability Corrosion Prevention and Control Insensitive Munitions Disposal and Demilitarization Supportability Software Commercial Off-the-Shelf Parts Management Critical Safety Items Balanced Best Value Solution Interoperability Standardization Quality and Producibility Open Systems Design Survivability and Susceptibility Human Systems Integration Program Protection & System Assurance Environment, Safety, and Occupational Health (ESOH) Achieving the best value solution is an iterative task performed within the framework of Systems Engineering. DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 5
USD(AT&L) Imperatives Provide a context within which I can make decisions about individual programs. Achieve credibility and effectiveness in the acquisition and logistics support processes. Help drive good systems engineering practices back into the way we do business. DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 6
Questions? Don Gelosh, Ph.D., CSEP Senior Systems Engineer OSD (AT&L) SSE/ED 1851 SOUTH BELL STREET CRYSTAL MALL 3 SUITE 102 ARLINGTON, VA 22202 OFFICE: 703-602-0851 EXT 194 FAX: 703-602-3560 DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 7
Backup DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 8
Reliability Improvement Working Group February 2008: DUSD(A&T) Memo requested Component Acquisition Executives to establish a Reliability Improvement Working Group (RIWG) to: Ensure programs are formulated to execute a viable systems engineering strategy from the beginning, including a RAM growth program, as an integral part of design and development. Ensure government organizations reconstitute a cadre of experienced T&E and RAM personnel. Implement mandated integrated DT and OT, including the sharing and access to all appropriate contractor and government data and the use of operationally representative environments in early testing. DELIBERATIVE DOCUMENT: For discussion purposes only. Draft working papers. Do not release under FOIA. 9