1. Measuring Technology Maturity Actual system “flight proven” through successful mission operations Actual system completed and “flight qualified” through test and demonstration System prototype demonstration in a operational environment System/subsystem model or prototype demonstration in a relevant environment 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

2. Technology Readiness LevelsDescription #1 Basic principles observed and reported Scientific research begins translation to applied R & D (paper studies) #2 Technology concept and/or application formulated Basic principles documented and practical applications formulated (analytic studies) #3 Analytical and experimental critical function and/or characteristic proof of concept Active R & D initiated (physical validation in laboratory) #4 Component and/or breadboard validation in laboratory environment Component integration in “low-fidelity” laboratory environment (HIL/SIL simulation) #5 Component and/or breadboard validation in relevant environment Component/subsystem integration in “high- fidelity” laboratory environment (more realistic simulation) #6 System/Subsystem model or prototype demonstration in a relevant environment System/subsystem prototype evaluation in a simulated laboratory operational environment #7 System prototype demonstration in an operational environment Whole system prototype evaluation in actual operational environment (“open-air” or “at- sea”) #8 Actual system completed and qualified through test and demonstration Final phase of system development... validation of technical performance and compliance with design specifications #9 Actual system proven through successful mission operations Fuel mission evaluation in realistic operational conditions (combat environment, all-wx, typical operators, countermeasures, tactics, etc.) TRLs

3. Breadboard- Integrated components that provide a representation of a system/subsystem and which can be used to determine concept feasibility and to develop a technical data. Typically configured for laboratory use to determine the technical principles of immediate interest. May resemble final system/subsystem in function only. “High Fidelity”- Addresses form, fit and function. High-fidelity laboratory environment would involve testing with equipment that can simulate and validate all system specifications within a laboratory setting. “Low-Fidelity”- A representative of the component or system that has limited ability to provide anything but first order information about the end product. Low-fidelity assessments are used to provide trend analysis. Model- A functional form of a system, generally reduced in scale, near or at operational specification. Models will be sufficiently hardened to allow demonstration of the technical and operational capabilities required of the final system to include platform/packaging. Prototype: A physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility of a particular technology or process, concept, end item or system. Relevant Environment- Testing environment that simulates the key aspects of the operational environment. Simulated Operational Environmental- Either 1) a real environment that can simulate all of the operational requirements and specifications required of the final system, or 2) a simulated environment that allows for testing of a virtual prototype; used in either case to determine whether a developmental system meets the operational requirements and specifications of the final systems TRLs

4. Findings from multiple studies attribute some program troubles to lack of technology maturity (TM) Findings from multiple studies attribute some program troubles to lack of technology maturity (TM) GAO GAO QDR QDR DAPA DAPA SSE/AS Program Support Reviews SSE/AS Program Support Reviews “Programs that started development with immature technologies experienced an average acquisition unit cost increase of nearly 21 percent” (GAO Report) “Programs that started development with immature technologies experienced an average acquisition unit cost increase of nearly 21 percent” (GAO Report) FY06, PL 109-163, Section 801 requires USD(AT&L) certification, before Milestone B, that “the technology in the program has been demonstrated in a relevant environment” FY06, PL 109-163, Section 801 requires USD(AT&L) certification, before Milestone B, that “the technology in the program has been demonstrated in a relevant environment” Above wording equates to Technology Readiness Level (TRL) 6 Above wording equates to Technology Readiness Level (TRL) 6 Mr. Chris DiPetto, Deputy Director Developmental Test & Evaluation November 7, 2006 Measuring Technology Maturity

5. Technology Readiness Levels (TRLs) Actual system “flight proven” through successful mission operations Actual system completed and “flight qualified” through test and demonstration System prototype demonstration in a operational environment System/subsystem model or prototype demonstration in a relevant environment 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 Demonstrated at least TRL 6 by Milestone B

6. Reaching TRL 6 TRL 6 definition – System/subsystem model or prototype demonstrated in a relevant environment TRL 6 definition – System/subsystem model or prototype demonstrated in a relevant environment TRL 6 can be reached at the subsystem level. The model or prototype, whether hardware or software, should show that the essential functionality is achievable. TRL 6 can be reached at the subsystem level. The model or prototype, whether hardware or software, should show that the essential functionality is achievable. For hardware, demonstrate the technology under relevant conditions of the physical environment.For hardware, demonstrate the technology under relevant conditions of the physical environment. For software, demonstrate the algorithms and processes under relevant conditions of input data quality and rate.For software, demonstrate the algorithms and processes under relevant conditions of input data quality and rate. Relevant conditions are not ideal conditions. They are stressing conditions but not necessarily the worst conditions imaginable. Relevant conditions are not ideal conditions. They are stressing conditions but not necessarily the worst conditions imaginable.

7. TRA Lessons Learned Start early Start early Early identification and agreement on critical technologies Early identification and agreement on critical technologies Flexibility required – No two TRAs will be the same Flexibility required – No two TRAs will be the same Technology Readiness Assessment must be performed independently from Risk Assessment Technology Readiness Assessment must be performed independently from Risk Assessment Regular IPRs Regular IPRs Test data the most difficult to verify Test data the most difficult to verify Working Group should include representatives from PM, Component S&T Executive, Component Acquisition Executive, and DUSD(S&T) Working Group should include representatives from PM, Component S&T Executive, Component Acquisition Executive, and DUSD(S&T)

8. System Integration System Demo System Dev & Demonstration IOC Defense Acquisition Management Framework DoDI Defense Acquisition Management Framework DoDI 5000.2 Design Readiness Review LRIP Operations & Support Process entry points at Milestone A, B, or C Entrance criteria met before entering phase Evolutionary Acquisition or Single Step to Full Capability Integrate subsystems, complete detailed design, and reduce system-level risk Integrate subsystems, complete detailed design, and reduce system-level risk System Integration Conduct AoA, refine initial concept & develop Technology Development Strategy Conduct AoA, refine initial concept & develop Technology Development Strategy Concept Refinement FRP Decision Review Full-Rate Prod & Deployment Full rate production Full rate production Deployment of system Deployment of system ConceptRefinement TechnologyDevelopment Concept Decision FRP & Deployment Production & Deployment Low-Rate Initial Production Create efficient manufacturin g cap,LRIP Create efficient manufacturin g cap,LRIP IOT&E, LFT&E of prod-rep articles IOT&E, LFT&E of prod-rep articles C Pre-Systems Acquisition Systems Acquisition Sustainment User Needs & Technology Opportunities FOC Complete development Complete development Demonstrate ability of system to operate in useful way consistent with KPPs Demonstrate ability of system to operate in useful way consistent with KPPs Combined DT/OT Combined DT/OT System Demonstration Reduce technology risk & determine the appropriate set of technologies to be integrated into a full system Reduce technology risk & determine the appropriate set of technologies to be integrated into a full system Demo the technologies in a relevant environment Demo the technologies in a relevant environment Technology Development Funding: Rqmnts: BA 3/4 BA 5 BA 5/ProcurementProc/Operations & Maintenance BA 5 CDD CPD Validated & approved by operational validation authority ICD Increment II Increment III B DRR C FRP BA 1&2 3&4 6 7 8 9 5

9. Pacing Technologies: Cannon - Recoil Mitigation Munitions - Electro-Thermal-Chemical Propulsion Seeker/Guidance & Control Multi-Mode Warhead Armament & Ammunition ATD An Army Example Objective: Demonstrate compact, direct/indirect fire armament system module capable of rapid lethality against the full spectrum of threats at 0-50km range. “One Shot.. ….At Least One Kill” “Precision Point Target Defeat” NLOS 4-50KM BLOS 2-12km LOS 0-4Km Warfighter Payoffs: Heavy Force Lethality with a 105mm > Multi-range - LOS, BLOS, & NLOS > Multi-Threat Capable Reduced logistic footprint > High number of stowed rounds A Lightweight Armament System For Dominating the Red Zone and Beyond

10. TRL=6 Seeker/ G&C METRIC: 50-150m CEP to 50km Ambient Temp functionality TRL=4 Seeker/G&C Acq Demo METRICS: P acq/Enc to 8km via CFT Demo TRL=4 ETC Propellant Demo METRICS: Sub Scale firings of Gen II. Model to validate launch velocity. Full Scale Firing With Adv JA2. Validate integration TRL=4 Recoil Mitigation Demo METRICS: 50% reduced recoil force w/Fire-out-of- battery modified M35 cannon w/ETC ignition TRL=5 Seeker/G&C High-g Demo METRIC: MP-ERM: 18k g’s air gun test Cargo: 20k g’s air gun test FY01 FY02 FY03 FY04 FY05 FY06 FY07 Cannon TRL=5 Propulsion Demo METRICS: Fire Full Scale Case Telescoped Ammo, Demo M829A2 + 20% performance TRL=5 Recoil Mitigation Demo METRICS: <80K lbs hardstand firing of KE slugs TRL=5 Multi-Mode WHD METRIC: Shaped Charge L/D=1 (vs 1.7) EFP 25% increase in armor penetration TRL=6 Multi-Mode WHD METRIC: Integrated WHD demo of 3 lethality modes TRL=6 Seeker/ G&C METRIC: P acq/Enc via Integ Projectile Guide to Hit gun launch to 10km TRL=7 Systems Level Live fire demo of Ammo Suite METRICS: Turret integrated on candidate vehicle Armament & Ammunition ATD An Army Example