Navy magazine is distributed on Capitol Hill,the Pentagon and naval bases around the world. It provides information that impacts Sailors, their families and the Navy. Navy is published quarterly by the Association of the United States Navy (AUSN).

Issue link:

Contents of this Issue


Page 29 of 43

28 Navy | Spring 2018 Department of Defense Technology Readiness Levels Technology Readi- ness Level (TRL) Description Supporting Information 1. Basic principles observed and reported Lowest level of technology readiness. Scientific research begins to be translated into applied research and development (R&D). Examples might include paper studies of a technology's basic properties. Published research that identifies the principles that underlie this technology. References to who, where and when. 2. Technology concept and/or application formulated Invention begins. Once basic principles are observed, practical applications can be invented. Applications are speculative, and there may be no proof or detailed analysis to support the assumptions. Examples are limited to analytic studies. Publications or other references that outline the appli- cation being considered and that provide analysis to support the concept. 3. Analytical and exper- imental critical function and/or characteristic proof of concept Active R&D is initiated. This includes analytical studies and laboratory studies to physically validate the analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative. Results of laboratory tests performed to measure parameters of interest and comparison to analytical predictions for critical subsystems. References to who, where and when these tests and comparisons were performed. 4. Component and/or breadboard validation in laboratory environment. (Breadboard: A construc- tion base for the proto- typing of electronics) Basic technological components are integrated to establish that they will work together. This is relatively "low fidelity" compared with the even- tual system. Examples include integration of "ad hoc" hardware in the laboratory. System concepts that have been considered and results from testing laboratory-scale breadboard(s). References to who did this work and when. Provide an estimate of how breadboard hardware and test results differ from the expected system goals. 5. Component and/or breadboard validation in relevant environment Fidelity of breadboard technology increases significantly. The basic technological compo- nents are integrated with reasonably realistic supporting elements so they can be tested in a simulated environment. Examples include "high-fidelity" laboratory integration of components. Results from testing laboratory breadboard system are integrated with other supporting elements in a simu- lated operational environment. How does the "relevant environment" differ from the expected operational environment? How do the test results compare with expectations? What problems, if any, were encoun- tered? Was the breadboard system refined to more nearly match the expected system goals? 6. System/subsystem model or prototype demonstration in a rele- vant environment Representative model or prototype system, which is well beyond that of TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness. Examples include testing a prototype in a high-fidelity laboratory environment or in a simulated operational environment. Results from laboratory testing of a prototype system that is near the desired configuration in terms of performance, weight and volume. How did the test environment differ from the operational environment? Who performed the tests? How did the test compare with expectations? What problems, if any, were encountered? What are/were the plans, options or actions to resolve problems before moving to the next level? 7. System prototype demonstration in an operational environment Prototype near or at planned operational system. Represents a major step up from TRL 6 by requiring demonstration of an actual system prototype in an operational environment (e.g., in an aircraft, in a vehicle or in space). Results from testing a prototype system in an opera- tional environment. Who performed the tests? How did the test compare with expectations? What problems, if any, were encountered? What are/were the plans, options or actions to resolve problems before moving to the next level? 8. Actual system completed and qualified through test and demon- stration Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications. Results of testing the system in its final configuration under the expected range of environmental conditions in which it will be expected to operate. Assessment of whether it will meet its operational requirements. What problems, if any, were encountered? What are/were the plans, options or actions to resolve problems before finalizing the design? 9. Actual system proven through successful mission operations Actual application of the technology in its final form and under mission conditions, such as those encountered in operational test and evalu- ation (OT&E). Examples include using the system under operational mission conditions. OT&E reports. Source: Department of Defense

Articles in this issue

Archives of this issue

view archives of AUSN - SPRING 2018