Technology readiness level
|Technology assessment and forecasting|
Technology readiness levels (TRLs) are a method for estimating the maturity of technologies during the acquisition phase of a program. TRLs enable consistent and uniform discussions of technical maturity across different types of technology. TRL is determined during a technology readiness assessment (TRA) that examines program concepts, technology requirements, and demonstrated technology capabilities. TRLs are based on a scale from 1 to 9 with 9 being the most mature technology.
TRL was developed at NASA during the 1970s. The US Department of Defense has used the scale for procurement since the early 2000s. By 2008 the scale was also in use at the European Space Agency (ESA). The European Commission advised EU-funded research and innovation projects to adopt the scale in 2010. TRLs were consequently used in 2014 in the EU Horizon 2020 program. In 2013, the TRL scale was further canonized by the International Organization for Standardization (ISO) with the publication of the ISO 16290:2013 standard.
A comprehensive approach and discussion of TRLs has been published by the European Association of Research and Technology Organisations (EARTO). Extensive criticism of the adoption of TRL scale by the European Union was published in The Innovation Journal, stating that the "concreteness and sophistication of the TRL scale gradually diminished as its usage spread outside its original context (space programs)".
Current TRL definitions
|TRL||Current NASA usage||European Union|
|1||Basic principles observed and reported||Basic principles observed|
|2||Technology concept and/or application formulated||Technology concept formulated|
|3||Analytical and experimental critical function and/or characteristic proof-of concept||Experimental proof of concept|
|4||Component and/or breadboard validation in laboratory environment||Technology validated in lab|
|5||Component and/or breadboard validation in relevant environment||Technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)|
|6||System/subsystem model or prototype demonstration in a relevant environment (ground or space)||Technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)|
|7||System prototype demonstration in a space environment||System prototype demonstration in operational environment|
|8||Actual system completed and "flight qualified" through test and demonstration (ground or space)||System complete and qualified|
|9||Actual system "flight proven" through successful mission operations||Actual system proven in operational environment (competitive manufacturing in the case of key enabling technologies; or in space)|
A Technology Readiness Level Calculator was developed by the United States Air Force. This tool is a standard set of questions implemented in Microsoft Excel that produces a graphical display of the TRLs achieved. This tool is intended to provide a snapshot of technology maturity at a given point in time.
The Defense Acquisition University (DAU) Decision Point (DP) Tool originally named the Technology Program Management Model was developed by the United States Army. and later adopted by the DAU. The DP/TPMM is a TRL-gated high-fidelity activity model that provides a flexible management tool to assist Technology Managers in planning, managing, and assessing their technologies for successful technology transition. The model provides a core set of activities including systems engineering and program management tasks that are tailored to the technology development and management goals. This approach is comprehensive, yet it consolidates the complex activities that are relevant to the development and transition of a specific technology program into one integrated model.
The primary purpose of using technology readiness levels is to help management in making decisions concerning the development and transitioning of technology. It should be viewed as one of several tools that are needed to manage the progress of research and development activity within an organization.
Among the advantages of TRLs:
- Provides a common understanding of technology status
- Risk management
- Used to make decisions concerning technology funding
- Used to make decisions concerning transition of technology
Some of the characteristics of TRLs that limit their utility:
- Readiness does not necessarily fit with appropriateness or technology maturity
- A mature product may possess a greater or lesser degree of readiness for use in a particular system context than one of lower maturity
- Numerous factors must be considered, including the relevance of the products' operational environment to the system at hand, as well as the product-system architectural mismatch
Current TRL models tend to disregard negative and obsolescence factors. There have been suggestions made for incorporating such factors into assessments.
For complex technologies that incorporate various development stages, a more detailed scheme called the Technology Readiness Pathway Matrix has been developed going from basic units to applications in society. This tool aims to show that a readiness level of a technology is based on a less linear process but on a more complex pathway through its application in society.
Technology readiness levels were originally conceived at NASA in 1974 and formally defined in 1989. The original definition included seven levels, but in the 1990s NASA adopted the current nine-level scale that subsequently gained widespread acceptance.
Original NASA TRL Definitions (1989)
- Level 1 – Basic Principles Observed and Reported
- Level 2 – Potential Application Validated
- Level 3 – Proof-of-Concept Demonstrated, Analytically and/or Experimentally
- Level 4 – Component and/or Breadboard Laboratory Validated
- Level 5 – Component and/or Breadboard Validated in Simulated or Realspace Environment
- Level 6 – System Adequacy Validated in Simulated Environment
- Level 7 – System Adequacy Validated in Space
The TRL methodology was originated by Stan Sadin at NASA Headquarters in 1974. At that time, Ray Chase was the JPL Propulsion Division representative on the Jupiter Orbiter design team. At the suggestion of Stan Sadin, Chase used this methodology to assess the technology readiness of the proposed JPL Jupiter Orbiter spacecraft design. Later Chase spent a year at NASA Headquarters helping Sadin institutionalize the TRL methodology. Chase joined ANSER in 1978, where he used the TRL methodology to evaluate the technology readiness of proposed Air Force development programs. He published several articles during the 1980s and 90s on reusable launch vehicles utilizing the TRL methodology. These documented an expanded version of the methodology that included design tools, test facilities, and manufacturing readiness on the Air Force Have Not program. The Have Not program manager, Greg Jenkins, and Ray Chase published the expanded version of the TRL methodology, which included design and manufacturing. Leon McKinney and Chase used the expanded version to assess the technology readiness of the ANSER team's Highly Reusable Space Transportation (HRST) concept. ANSER also created an adapted version of the TRL methodology for proposed Homeland Security Agency programs.
The United States Air Force adopted the use of technology readiness levels in the 1990s.
In 1995, John C. Mankins, NASA, wrote a paper that discussed NASA's use of TRL, extended the scale, and proposed expanded descriptions for each TRL. In 1999, the United States General Accounting Office produced an influential report that examined the differences in technology transition between the DOD and private industry. It concluded that the DOD takes greater risks and attempts to transition emerging technologies at lesser degrees of maturity than does private industry. The GAO concluded that use of immature technology increased overall program risk. The GAO recommended that the DOD make wider use of technology readiness levels as a means of assessing technology maturity prior to transition. In 2001, the Deputy Under Secretary of Defense for Science and Technology issued a memorandum that endorsed use of TRLs in new major programs. Guidance for assessing technology maturity was incorporated into the Defense Acquisition Guidebook. Subsequently, the DOD developed detailed guidance for using TRLs in the 2003 DOD Technology Readiness Assessment Deskbook.
Because of their relevance to Habitation, 'Habitation Readiness Levels (HRL)' were formed by a group of NASA engineers (Jan Connolly, Kathy Daues, Robert Howard, and Larry Toups). They have been created to address habitability requirements and design aspects in correlation with already established and widely used standards by different agencies, including NASA TRLs.
In the European Union
The European Space Agency adopted the TRL scale in the mid-2000s. Its handbook closely follows the NASA definition of TRLs. The universal usage of TRL in EU policy was proposed in the final report of the first High Level Expert Group on Key Enabling Technologies, and it was indeed implemented in the subsequent EU framework program, called H2020, running from 2013 to 2020. This means not only space and weapons programs, but everything from nanotechnology to informatics and communication technology.
- List of emerging technologies
- Technology transfer
- Technology assessment
- Technology life cycle
- Manufacturing Readiness Level
- Capability Maturity Model Integration
- Open Innovation
- ^ a b c d e f g h Mihaly, Heder (September 2017). "From NASA to EU: the evolution of the TRL scale in Public Sector Innovation" (PDF). The Innovation Journal. 22: 1–23. Archived from the original (PDF) on October 11, 2017.
- ^ a b "Technology Readiness Levels Handbook for Space Applications" (PDF) (1 revision 6 ed.). ESA. September 2008. TEC-SHS/5551/MG/ap.
- ^ "The TRL Scale as a Research & Innovation Policy Tool, EARTO Recommendations" (PDF). European Association of Research & Technology Organisations. 30 April 2014.
- ^ "Technology Readiness Level Definitions" (PDF). nasa.gov. Retrieved 6 September 2019. This article incorporates text from this source, which is in the public domain.
- ^ "Technology readiness levels (TRL); Extract from Part 19 - Commission Decision C(2014)4995" (PDF). ec.europa.eu. 2014. Retrieved 11 November 2019. Material was copied from this source, which is available under a Creative Commons Attribution 4.0 International License.
- ^ Nolte, William L.; et al. (20 October 2003). "Technology Readiness Level Calculator, Air Force Research Laboratory, presented at the NDIA Systems Engineering Conference". Archived from the original on 13 May 2015.
- ^ "Technology Assessment Calculator".
- ^ Craver, Jeffrey T. (28 Dec 2020). "Decision Point / Technology Program Management Model, DAU". Defense Acquisition University.
- ^ Jeff, Craver. "Decision Point / TPMM - Technology Program Management Model (only available to DOD components)".
- ^ Christophe Deutsch; Chiara Meneghini; Ozzy Mermut; Martin Lefort. "Measuring Technology Readiness to improve Innovation Management" (PDF). INO. Archived from the original (PDF) on 2012-06-02. Retrieved 2011-11-27.
- ^ a b Ben Dawson (31 October 2007). "The Impact of Technology Insertion on Organisations" (PDF). Human Factors Integration Design Technology Centre. Archived from the original (PDF) on 26 April 2012.
- ^ Ricardo Valerdi; Ron J. Kohl (March 2004). An Approach to Technology Risk Management (PDF). Engineering Systems Division Symposium MIT, Cambridge, MA, March 29-31, 2004. CiteSeerX 10.1.1.402.359.[dead link]
- ^ Vincent Jamier; Christophe Aucher (April 2018). "Demystifying Technology Readiness Levels for Complex Technologies". Leitat Projects Blog.
- ^ a b Banke, Jim (20 August 2010). "Technology Readiness Levels Demystified". NASA.
- ^ Sadin, Stanley R.; Povinelli, Frederick P.; Rosen, Robert (October 1, 1988). The NASA technology push towards future space mission systems. International Astronautical Congress, 39th, Bangalore, India, Oct. 8-15, 1988.
- ^ Chase, R.L. (26 June 1991). Methodology for Assessing Technological and Manufacturing Readiness of NASP-Technology Enabled Vehicles. 27th Joint Propulsion Conference, June 24-26, 1991, Sacramento CA. doi:10.2514/6.1991-2389. AIAA 91-2389.
- ^ R. L. Chase; L. E. McKinney; H. D. Froning, Jr.; P. Czysz; et al. (January 1999). "A comparison of selected air-breathing propulsion choices for an aerospace plane". AIP Conference Proceedings. Vol. 458. American Institute of Physics. pp. 1133–8. doi:10.1063/1.57719.
- ^ "Department of Homeland Security Science and Technology Readiness Level Calculator (Ver. 1.1) - Final Report and User"s Manual" (PDF). Homeland Security Institute. September 30, 2009. Archived from the original (PDF) on August 26, 2010.
- ^ "Best Practices: Better Management of Technology Can Improve Weapon System Outcomes" (PDF). General Accounting Office. July 1999. GAO/NSIAD-99-162.
- ^ Defense Acquisition Guidebook Archived 2012-04-25 at the Wayback Machine
- ^ Häuplik-Meusburger and Bannova (2016). Space Architecture Education for Engineers and Architects. Springer. ISBN 978-3-319-19278-9.
- ^ Cohen, Marc (2012). Mockups 101: Code and Standard Research for Space Habitat Analogues. AIAA Space 2012 Conference Pasadena, California.
- ^ "High-Level Expert Group on Key Enabling Technologies – Final Report". June 2011. p. 31. Retrieved March 16, 2020.
- "Best Practices: Better Management of Technology Development Can Improve Weapon System Outcomes". U.S. Government Accountability Office. July 1999. NSIAD-99-162.
- "Joint Strike Fighter Acquisition: Mature Critical Technologies Needed to Reduce Risks". U.S. Government Accountability Office. October 2001. GAO-02-39.