Milestone A to Milestone B Requirements Management Activities Tom Fritz thomas.fritz@dau.mil 703 805 4583

Lesson Objectives Determine the major requirements management activities during the acquisition process from Milestone A to Milestone B Analyze the purpose and major activities of the Technology Development phase and the links between those activities Describe the decisions the Milestone Decision Authority (MDA) makes and the items the MDA approves at Milestone B

Milestone A to Milestone B Technology Development Full Rate Prod Decision Review Joint Concepts Capabilities - Based Assessment MS C MS B FCB Strategic Guidance Incremental Development MS A Technology Development Engineering & Manufacturing Development Production & Deployment AoA Materiel Solution Analysis Technology Opportunities & Resources ICD O&S User Needs MDD CDD CPD Pre-EMD Decision Review Post CDR Assessment ICD CDD CPD

Milestone A to Milestone B Requirements Management Activities Purpose: Reduce technology risk Major activity: Competitive prototyping A B Technology Development Draft CDD CDD CDD Pre-EMD Review PDR SRR SFR or TRA Requirements Management Activities Develop Final CDD Participate in IPTs and Technical Reviews (DAG 4.2.4.1 Fig 1) Program , Pre-EMD, and Milestone Reviews Monitor/provide input Acquisition Strategy Acquisition Program Baseline (APB) Test & Evaluation Master Plan (TEMP) Affordability Requirements & Cost Estimate PPBE Process Technology Readiness Assessment (TRA) Life Cycle Sustainment Plan (LCSP) AoA Update

Preliminary Design Review (PDR) PDR is a technical review to ensure that the system is ready to proceed into detailed design – assesses the design as captured in performance specification (system allocated baseline) and each function in functional baseline is allocated to one or more system configuration items. PDRs before Milestone B are mandatory for MDAPs. “A successful PDR will inform requirements trades; improve cost estimation; and identify remaining design, integration, and manufacturing risks. The PDR shall be conducted at the system level and include user representatives and associated certification authorities. The PDR Report shall be provided to the MDA at Milestone B and include recommended requirements trades based upon an assessment of cost, schedule, and performance risk.” (DoDI 5000.02)

Pre-EMD Review Pre-EMD Review is directed by AT&L Memo, June 23, 2011. Purpose is to authorize release of final RFP and source selection for EMD contract. Contract award ASAP after MS B approval Timing implications for CDD validation Discussion: What experience in this class with Pre-EMD review? USAF Expeditionary Combat Support System, MS B, 9/7/2011 Army Joint Air-to-Ground Missile, MS B cnx, 11/12/2011 Navy Consolidated Afloat Enterprise Network, MS B paper, 12/9/2011

Technology Readiness Assessment (TRA) TRA is a systematic, metrics based process that assesses maturity of, and risk associated with Critical technologies to be used in an MDAP TRA plan prepared by PM; approved by PEO, CAE and ASD(R&E). Conducted by Subject Matter Experts independent of PMO, but assigned by PM. Required for MDAPs for Sec. 2366b cert at Milestones B TRA results are included in CDD/CPD ASD(R&E) provides MDA an independent assessment and review of the TRA final report as to whether technology was demonstrated in relevant environment Technology Readiness Levels (TRLs) are knowledge-based standard but not a substitute for professional judgment A TRA focuses on the program’s “critical” technologies (i.e., those that may pose major technological risk during development, particularly during the Engineering and Manufacturing Development (EMD) phase of acquisition). Page 1-1 , TRA Guidance, April 2011, ASD(R&E)

Technology Maturity Technology Readiness Levels (TRL) Actual system proven through successful mission operations Actual system completed and qualified through test and demonstration (Full-Rate Production Decision) System prototype demonstration in a operational environment (Milestone C) System/subsystem model or prototype demonstration in a “relevant environment” (2366b certification item - Milestone B) Component and/or breadboard validation in relevant environment Component and/or breadboard validation in laboratory environment Analytical and experimental critical function and/or characteristic proof-of-concept Technology concept and/or application formulated Basic principles observed and reported System Test, Launch & Operations System/Subsystem Development Technology Demonstration Technology Development Research to Prove Feasibility Basic Technology Research TRL 9 TRL 8 TRL 7 TRL 6 TRL 5 TRL 4 TRL 3 TRL 2 TRL 1 Here are a few official resources to help out: U.S.C. Title 10, Section 2364 U.S.C. Title 10, Section 2366a (MDA Certification) Defense Acquisition Resource Center http://akss.dau.mil/darc/darc.html DoD Directive 5000.1 (DoDD 5000.1), The Defense Acquisition System, dated May 12, 2003 DoD Instruction 5000.2 (DoDI 5000.2), Operation of the Defense Acquisition System, dated May 12, 2003 Defense Acquisition Guidebook http://akss.dau.mil/DAG/ DAU Continuous Learning Module CLE021 https://learn.dau.mil/html/clc/Clc.jsp (to browse it) TRA Deskbook http://www.acq.osd.mil/ddre/publications/docs/TRA2011.pdf http://www.dod.mil/ddre/doc/DoD_TRA_July_2009_Read_Version.pdf   TRL Definitions on wikipedia: http://en.wikipedia.org/wiki/Technology_Readiness_Level Current update: TRA 2011 Link Public law requires MDAPs be at TRL 6 for Milestone B

Milestone B MDA approves: (DAG Encl 2—6, EMD Phase) Program Initiation (for most programs) Entry into Engineering and Manufacturing Development (EMD) Acquisition Strategy APB (includes affordability requirement – functional equivalent of KPPs) LRIP quantities Exit criteria for next phase Type of Contract Milestone B Certification ADM Requires Approved CDD*, and Full Funding in the Future Years Defense Program (FYDP) (affordability determination) *If first entering the acquisition process at MS B, JCIDS also requires an ICD

MDA Program Certification for MS B (Required by 10 USC 2366b for MDAPs) MEMORANDUM FOR THE RECORD SUBJECT: Milestone B Program Certification As required by Section 2366b of Title 10, United States Code, (1) I have received a business case analysis for the (name of program) and certify on the basis of the analysis that: (A) the program is affordable when considering the ability of the Department of Defense to accomplish the program's mission using alternative systems; (B) appropriate trade-offs among cost, schedule, and performance objectives have been made to ensure that the program is affordable when considering the per unit cost and the total acquisition cost in the context of the total resources available during the period covered by the future-years defense program submitted during the fiscal year in which the certification is made; (C) reasonable cost and schedule estimates have been developed to execute, with the concurrence of the Director of Cost Assessment and Program Evaluation, the product development and production plan under the program; (D) funding is available to execute the product development and production plan under the program, through the period covered by the future-years defense program submitted during the fiscal year in which the certification is made, consistent with the estimates described in paragraph (C) for the program; and Continued on next chart

MDA Program Certification for MS B, continued (2) I have received the results of the preliminary design review and conducted a formal post-preliminary design review assessment, and certify on the basis of such assessment that the program demonstrates a high likelihood of accomplishing its intended mission; and (3) I further certify that: (A) appropriate market research has been conducted prior to technology development to reduce duplication of existing technology and products; (B) the Department of Defense has completed an analysis of alternatives with respect to the program; (C) the Joint Requirements Oversight Council has accomplished its duties with respect to the program pursuant to section 181(b) of Title 10, including an analysis of the operational requirements for the program; (D) the technology in the program has been demonstrated in a relevant environment, as determined by the Milestone Decision Authority on the basis of an independent review and assessment by the Director of Defense Research and Engineering; and (E) the program complies with all relevant policies, regulations, and directives of the Department of Defense.

The Information Technology (IT) Box Purpose: Describe overall bounds of an IT program to facilitate program initiation and reduce subsequent return trips to the JROC for approval of improved capabilities as the program is executed. (JCIDS Manual Enclosure C) Applies to systems where there is no need to develop hardware systems (i.e., commercial-off-the-shelf hardware is used) Note: With JCIDS revision – the IT Box is an ICD format (JCIDS Manual Draft, 14 Oct 2011, page B-14)

The IT Box – Four Major Areas Presents the complete program for JCB and JROC members on one chart Flag-level oversight Chair & Members Total program cost Plan & cost for hardware & system integration Plan & cost for tech refresh per FY KPPs that represent initial level of performance for entire IT program FY funding for software development Total program costs for application and system software development/integration How often new releases will be delivered

Technology Development Phase Linkage: CDD, APB, TEMP & Contract for Engineering and Manufacturing Development (EMD) Milestone A Milestone B Pre-EMD Review Cost Estimate & $$ Competitive Designs & Prototypes DT TEMP COIs, MOEs, MOPs, CTPs Contract KPPs KSAs CDD AoA Update SPECs “design-to” PDR MOEs MOPs APB KPPs KSAs EMD Technology Development Phase 13

BACK UP SLIDES and INFORMATION

Oversight & Review DAE CAE PEO IPT’s assist in oversight & review DAB USD(AT&L) Defense Acquisition Executive Acquisition Category DAE Makes Decisions Signs ADM ACAT ID DAB-Defense Acquisition Board ITAB-Information Technology Acquisition Board $365M RDT&E or $2.19B Procurement (FY2000 Constant $) DAB ITAB ACAT IAM $378M Life Cycle Cost or $126M Total Prog. Cost or $32M Prog. Cost in any single year (FY2000 Constant $) OIPTs Overarching IPT’s (OIPT’s) Issue resolution Component Acquisition Executive (Asst Secretary) ACAT IC/IAC Configuration Steering Boards Makes ACAT IC, IAC & II Decisions Signs ADM CAE ACAT II Working-Level IPT’s (WIPT’s) $140M RDT&E or $660M Procurement (FY2000 Constant $) Teaching points: - Relationship of ACAT to the level of milestone review: clearly, more oversight at the ACAT ID/IAM level. -Important point is that ACAT ID/IAM programs are reviewed by the CAE before they go to OSD for review. -Note IPTs: requirements manager need to be involved at each level: PM level; WIPT and OIPT at Pentagon. Component HQ Review Issue resolution Program Level IPT’s Program Executive Officer (General Officer/SES Civilian) ACAT III PEO Makes ACAT III/IV Decisions Signs ADM No Fiscal Criteria IPT’s assist in oversight & review Program Manager (Col/LtCol/Civilian Equivalent) ACAT IV PM Navy USMC Note: Some PMs report directly to CAE.

Defense Acquisition Guidebook , 4.2.4.1 Figure 1