Questions? Call 800-624-6242 About | Ordering | New Menu | Items in cart [0] SEARCH

PAPERBACK price:$29.75 add to cart Rights & Permissions Free PDF Access Sign in to download PDF book and chapters Free Resources Display this book on your site! Related Titles NASA Space Technology Roadmaps and Priorities: Restoring NASA's Technological Edge and Paving the Way for a New Era in Space Review of the Space Communications Program of NASA's Space Operations Mission Directorate Other Related Titles Capabilities for the Future: An Assessment of NASA Laboratories for Basic Research (2010) Space Studies Board (SSB) Laboratory Assessments Board (LAB) Aeronautics and Space Engineering Board (ASEB) Citation Manager Export the bibliographic data for this book in your chosen format Web Search Builder Use this book's key terms to search within this book, across our collection, or across the Web. Skim This Chapter Skim this chapter and use this chapter's key terms to search within this book. Reference Finder Paste in your own text to find books that relate to your topic. Citation Manager . "Appendix B: Technology Readiness Level Descriptions." Capabilities for the Future: An Assessment of NASA Laboratories for Basic Research. Washington, DC: The National Academies Press, 2010. Please select a format: Page 81   E-mail Share on facebook Facebook Share on delicious Delicious Share on stumbleupon Stumble Share on twitter Twitter More Sharing ServicesMore The following HTML text is provided to enhance online readability. Many aspects of typography translate only awkwardly to HTML. Please use the page image as the authoritative form to ensure accuracy. B Technology Readiness Level Descriptions Technology Readiness Level (TRL) Definition Hardware Description Software Description Exit 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 publication of research underlying the proposed concept/application 2 Technology concept or application formulated Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture. Underlying algorithms are clarified and documented Documented description of the application/concept that addresses feasibility and benefit 3 Analytical and/or experimental critical function or characteristic proof-of-concept Analytical studies place the technology in an appropriate context and laboratory demonstrations, modeling and simulation validate analytical prediction Development of limited functionality to validate critical properties and predictions using non-integrated software components Documented analytical/experimental results validating predictions of key parameters 4 Component or breadboard validation in laboratory A low fidelity system/component breadboard is built and operated to demonstrate basic functionality and critical test environments and associated performance predictions are defined relative to the final operating environment Key, functionally critical, software components are integrated, and functionally validated, to establish interoperability and begin architecture development. Relevant environments defined and performance in this environment predicted Documented test performance demonstrating agreement with analytical predictions. Documented definition of relevant environment 5 Component or breadboard validation in a relevant environment A mid-level fidelity system/component brassboard is built and operated to demonstrate overall performance in a simulated operational environment with realistic support elements that demonstrates overall performance in critical areas. Performance predictions are made for subsequent development phases 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. Prototype implementations developed. Documented test performance demonstrating agreement with analytical predictions. Documented definition of scaling requirements 6 System/subsystem model or prototype demonstration in a relevant environment A high-fidelity system/component prototype that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate operations under critical environmental conditions Prototype software partially integrated with existing hardware/software systems and demonstrated on full scale realistic problems Documented test performance demonstrating agreement with analytical predictions 7 System prototype demonstration in space A high fidelity engineering unit that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate performance in the actual operational environment and platform (ground, airborne or space) Prototype software is fully integrated with operational hardware/software systems demonstrating operational feasibility Documented test performance demonstrating agreement with analytical predictions 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) 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) Documented test performance verifying analytical predictions 9 Actual system flight proven through successful mission operations The final product is successfully operated in an actual mission The final product is successfully operated in an actual mission Documented mission operational results SOURCE: “NASA Research and Technology Program and Project Management Requirements,” NPR 7120.8, Appendix J, February 5, 2008. Page 81 Front Matter (R1-R12) Summary (1-4) 1 Introduction (5-5) 2 Assessment Methodology (6-9) 3 Support for Fundamental Research at NASA (10-19) 4 Aeronautics Research (20-38) 5 Space and Earth Science Research (39-66) 6 Findings and Recommendations (67-76) Appendixes (77-78) Appendix A: Statement of Task (79-80) Appendix B: Technology Readiness Level Descriptions (81-81) Appendix C: Subcommittee Members (82-82) Appendix D: Laboratories and Facilities Visited by the Committee (83-89) Appendix E: Biographies of the Committee Members (90-96) Appendix F: Acronyms (97-99) Appendix G: List of Questions Sent to NASA Centers (100-100)

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 81
Capabilities for the Future: An Assessment of NASA Laboratories for Basic Research B Technology Readiness Level Descriptions Technology Readiness Level (TRL) Definition Hardware Description Software Description Exit 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 publication of research underlying the proposed concept/application 2 Technology concept or application formulated Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture. Underlying algorithms are clarified and documented Documented description of the application/concept that addresses feasibility and benefit 3 Analytical and/or experimental critical function or characteristic proof-of-concept Analytical studies place the technology in an appropriate context and laboratory demonstrations, modeling and simulation validate analytical prediction Development of limited functionality to validate critical properties and predictions using non-integrated software components Documented analytical/experimental results validating predictions of key parameters 4 Component or breadboard validation in laboratory A low fidelity system/component breadboard is built and operated to demonstrate basic functionality and critical test environments and associated performance predictions are defined relative to the final operating environment Key, functionally critical, software components are integrated, and functionally validated, to establish interoperability and begin architecture development. Relevant environments defined and performance in this environment predicted Documented test performance demonstrating agreement with analytical predictions. Documented definition of relevant environment 5 Component or breadboard validation in a relevant environment A mid-level fidelity system/component brassboard is built and operated to demonstrate overall performance in a simulated operational environment with realistic support elements that demonstrates overall performance in critical areas. Performance predictions are made for subsequent development phases 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. Prototype implementations developed. Documented test performance demonstrating agreement with analytical predictions. Documented definition of scaling requirements 6 System/subsystem model or prototype demonstration in a relevant environment A high-fidelity system/component prototype that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate operations under critical environmental conditions Prototype software partially integrated with existing hardware/software systems and demonstrated on full scale realistic problems Documented test performance demonstrating agreement with analytical predictions 7 System prototype demonstration in space A high fidelity engineering unit that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate performance in the actual operational environment and platform (ground, airborne or space) Prototype software is fully integrated with operational hardware/software systems demonstrating operational feasibility Documented test performance demonstrating agreement with analytical predictions 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) 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) Documented test performance verifying analytical predictions 9 Actual system flight proven through successful mission operations The final product is successfully operated in an actual mission The final product is successfully operated in an actual mission Documented mission operational results SOURCE: “NASA Research and Technology Program and Project Management Requirements,” NPR 7120.8, Appendix J, February 5, 2008.