Technology readiness levels
From DGC Wiki
| Contents Description Usage |
Team Caltech technology readiness levels (TRLs) are used to keep track of the stage of technology that we are considering for incorporation into our race system. These readiness levels are loosely based on the NASA Technology Readiness Levels that are used in the space systems community. TRLs are used to help manage the different between research, development and implementation.
TRL Description
| TRL | Description | Entry criteria |
|
[edit] 1 | Technology concept - A review of existing literature indicates that a technology concept is available and potentially useful for autonomous driving. | Concept documented on wiki or bugzilla |
|
[edit] 2 | GOTChA chart - A GOTChA chart has been developed for the project indicating how a given technology might be applied. The goals and objectives should provide a clear indication of the utility of the technology to autonomous driving. | GOTChA chart posted on the wiki |
|
[edit] 3 | Desktop demo - A basic demonstration of the key ideas is available either via a hardware mockup (eg, cardboard model) or a simple software demonstration (eg, MATLAB code). | Preliminary design and demonstration posted on the wiki |
|
[edit] 4 | Prototype implementation - A documented initial demonstration of the technology is available that verifies the key objectives for the system are achievable. | Documented design with external review. |
|
[edit] 5 | Alice demonstration - A demonstration of the technology on Alice (or using logged data, if appropriate) is available. The demonstration need not be integrated into the standard code/hardware base. | Demonstration on Alice |
|
[edit] 6 | Reviewed design - The technology has been demonstrated and successfully passed a design review, including implementation compatible with the standard code/hardware base on Alice. The final design must be documented on the wiki. | Pass formal design review |
|
[edit] 7 | Integrated module - The technology has been integrated into the standard code/hardware base and is being tracked through the configuration management process. | Build manager signoff |
|
[edit] 8 | Flight tested - The technology has been demonstrated in an Independent Test Team (ITT) sponsored test. | Documented performance in ITT test |
|
[edit] 9 | Race ready - The technology has been tested for 100+ hours of operations in a race-like environment. | Documented operation for 100+ hours |
Notes:
- TRL 1-3 is considered basic research
- TRL 4-6 is considered applied research and development
- TRL 7-9 is considered implementation
Usage
This section describes how TRL levels are used for inserted technology onto the race platform.
2006 SURF Projects
Most successful SURF projects will be at TRL 4-5 at the end of the summer (once the final report is turned in). Turning the academic year, they can be advanced to TRL 6 and higher through independent research classes or volunteer time. In some instances a separate individual may take a SURF project from TRL 5 to 6 by working with the student that did the original project.
CS/EE/ME 75
Students in CS/EE/ME 75 will generally have relatively little knowledge of Alice. There are two paths toward implementing technology through 75:
- Linked courses - several courses have projects that are directly applicable to autonomous driving. Students taking these courses can make use of Alice during the term in which the course is taken to bring their technology up to TRL 5 (typically). Moving to TRL 6 and higher generally requires a level of integration that is beyond what can be fit into most course projects.
- Small projects - a number of small projects are also available for improving the operation of Alice and its algorithms. These projects can generally be completed by a small group of students in 40-80 hours of total effort. Most projects of this sort will start at TRL 1 and can be advanced to TRL 6 in the course of one to two terms. Integration beyond level 6 becomes part of the configuration management process.
For students taking CS/EE/ME 75 with no prior experience on Alice, it will generally be possible to advanced a project to TRL 3 in one term and TRL 5-6 in the next term. Full integration should occur in spring term (when CS/EE/ME 75 is 18 units of credit) or during the summer.
Graduate Research
Graduate students actively pursuing research relevant to autonomous driving will generally have their research at TRL 4 at the inception of work. A GOTChA chart should be generated that lays out the work through TRL 6. Maintaining the technology at TRL 7-9 is part of the build process.
TRL 7-9
Technology at readiness levels 7 to 9 is managed by the configuration management process. The basic idea in this process is to use lightweight "branching" to quickly integrate new features into the baseline code. New features can either come from technology at TRL 6 that is ready to insert into the baseline configuration or improvements to code that is at TRL 7, 8 or 9.
New software features are greated by creating a development branch of the code (using YaM). This branch is considered to be at TRL 6 or lower. To reinstall the code into the baseline, it must first be verified by an appropriate build manager (TRL 7), tested in an ITT demonstration (TRL 8) and then used for 100+ hours of operation (TRL 9).
![[Main Page]](../../../../upload/alice.jpg)