NASA Procedural Requirements |
NPR 7123.1D Effective Date: July 05, 2023 Expiration Date: July 05, 2028 |
| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL | |
TRL | Definition | Hardware Description | Software Description | Success criteria | |
---|---|---|---|---|---|
1 | Basic principles observed and reported. | Scientific knowledge generated underpinning hardware technology concepts/applications. | Scientific knowledge generated underpinning basic properties of software architecture and mathematical formulation. | Peer reviewed documentation of research underlying the proposed concept/application. | |
Examples:
|
|||||
2 | Technology concept and/or application formulated. | Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture. | Practical application is identified but is speculative; no experimental proof or detailed analysis is available to support the conjecture. Basic properties of algorithms, representations, and concepts defined. Basic principles coded. Experiments performed with synthetic data. | Documented description of the application/concept that addresses feasibility and benefit. | |
Example: Carbon nanotube composites were created for lightweight, high-strength structural materials for space structures. |
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
3 | Analytical and experimental proof-of-concept of critical function and/or characteristics. | Research and development are initiated, including analytical and laboratory studies to validate predictions regarding the technology. | Development of limited functionality to validate critical properties and predictions using non-integrated software components. | Documented analytical/experimental results validating predictions of key parameters. | |
Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
4 | Component and/or breadboard validation in a laboratory environment. | A low fidelity system/component breadboard is built and operated to demonstrate basic functionality in a laboratory environment. | Key, functionality critical software components are integrated and functionally validated to establish interoperability and begin architecture development. Relevant environments defined and performance in the environment predicted. | Documented test performance demonstrating agreement with analytical predictions. Documented definition of potentially relevant environment. | |
Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
5 | Component and/or brassboard validated in a relevant environment. | A medium-fidelity component and/or brassboard, with realistic support elements, is built and operated for validation in a relevant environment so as to demonstrate overall performance in critical areas. | End-to-end software elements implemented and interfaced with existing systems/simulations conforming to target environment. End-to-end software system tested in relevant environment, meeting predicted performance. Operational environment performance predicted. Implementations. | Documented test performance demonstrating agreement with analytical predictions. Documented definition of scaling requirements. Performance predictions are made for subsequent development phases. | |
Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
6 | System/sub-system model or prototype demonstration in a relevant environment. | A high-fidelity prototype of the system/subsystems that adequately addresses all critical scaling issues is built and tested in a relevant environment to demonstrate performance under critical environmental conditions. | Prototype implementations of the software demonstrated on full-scale, realistic problems. Partially integrated with existing hardware/software systems. Limited documentation available. Engineering feasibility fully demonstrated. | Documented test performance demonstrating agreement with analytical predictions. | |
Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
7 | System prototype demonstration in an operational environment. | A high-fidelity prototype or engineering unit that adequately addresses all critical scaling issues is built and functions in the actual operational environment and platform (ground, airborne, or space). | Prototype software exists having all key functionality available for demonstration and test. Well integrated with operational hardware/software systems demonstrating operational feasibility. Most software bugs removed. Limited documentation available. | Documented test performance demonstrating agreement with analytical predictions. | |
Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
8 | Actual system completed and "flight qualified" through test and demonstration. | The final product in its final configuration is successfully demonstrated through test and analysis for its intended operational environment and platform (ground, airborne, or space). If necessary*, life testing has been completed. | All software has been thoroughly debugged and fully integrated with all operational hardware and software systems. All user documentation, training documentation, and maintenance documentation completed. All functionality successfully demonstrated in simulated operational scenarios. Verification and Validation completed. | Documented test performance verifying analytical predictions. | |
Note: *"If necessary" refers to the need to life test either for worn out mechanisms, for temperature stability over time, and for performance over time in extreme environments. An evaluation on a case-by-case basis should be made to determine the system/systems that warrant life testing and the tests begun early in the technology development process to enable completion by TRL 8. It is preferable to have the technology life test initiated and completed at the earliest possible stage in development. Some components may require life testing on or after TRL 5. Examples:
|
|||||
TRL | Definition | Hardware Description | Software Description | Success criteria | |
9 | Actual system flight proven through successful mission operations. | The final product is successfully operated in an actual mission. | All software has been thoroughly debugged and fully integrated with all operational hardware and software systems. All documentation has been completed. Sustaining software support is in place. System has been successfully operated in the operational environment. | Documented mission operational results. | |
Examples:
|
Note: In cases of conflict between NASA directives concerning TRL definitions, NPR 7123.1 will take precedence.
| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | ALL | |
| NODIS Library | Program Formulation(7000s) | Search | |
This document does not bind the public, except as authorized by law or as incorporated into a contract. This document is uncontrolled when printed. Check the NASA Online Directives Information System (NODIS) Library to verify that this is the correct version before use: https://nodis3.gsfc.nasa.gov.