TRL 9 meaning: proven in operational use
TRL 9 meaning: the actual system proven in operational use, what NASA, the EU and India's NTRAF require, the evidence asked for, and how it differs from TRL 8.
Part of the guide TRL levels explained: what TRL 1 to 9 really mean, and how to place your technology
TRL 9 means the actual system is proven in its operational environment. India's National Technology Readiness Assessment Framework (NTRAF) defines it as proven over the full range of expected conditions and asks for an Operational Environment Testing Report. NASA calls it flight proven through successful mission operations, with documented mission operational results as the exit criterion.
A fair question about TRL 9 is why it needs a separate level at all. If the product is finished and has passed its qualification tests at TRL 8, surely it is ready? The answer is that tests, however careful, are planned by people who already know what they are looking for. Real use finds the problems nobody planned for: the monsoon, the careless operator, the power cut, the customer who uses the product in a way the designers never imagined. TRL 9 is the level at which the technology has survived that.
This post explains what TRL 9 means under the three main definitions, the evidence India's framework asks for, how it differs from TRL 8, and the claims that fail review.
What does TRL 9 mean?
| Framework | TRL 9 wording |
|---|---|
| NASA | Actual system "flight proven" through successful mission operations |
| EU (Horizon Europe) | Actual system proven in an operational environment (competitive manufacturing in the case of key enabling technologies, or in space) |
| India (NTRAF) | Actual system proven in operational environment over full range of expected conditions |
Sources: NASA ESTO, the Horizon Europe General Annexes and the National Technology Readiness Assessment Framework.
NTRAF describes TRL 9 as the actual application of the technology in its final form and under mission conditions, giving operational test and evaluation as an example. NASA's hardware description is short: the final product is successfully operated in an actual mission. For software, NASA asks that all software be thoroughly debugged and fully integrated with all operational hardware and software systems, all documentation completed, sustaining software engineering support in place, and the system successfully operated in the operational environment.
NASA's exit criterion at TRL 9 is "documented mission operational results". At TRL 8 it was test performance verifying analytical predictions. The evidence moves from tests to records of real use.
Where does TRL 9 sit?
TRL 9 is system operations
NTRAF's stages put TRL 7 and 8 together as system commissioning and give TRL 9 a stage of its own, system operations. For the level below, see TRL 8 meaning; for the whole climb, see how to move from TRL 6 to TRL 9.
The difference from TRL 8 is the range of conditions. NTRAF's key question at TRL 8 asks whether the actual system has operated in a limited operational environment. At TRL 9 it asks whether the actual system has "successfully operated over full range of conditions in operational environment".
What evidence does NTRAF ask for?
The supporting document at TRL 9 is an Operational Environment Testing Report. NTRAF's critical items are:
| NTRAF critical item | What it means in practice |
|---|---|
| System/technology functions as defined in Operational Concept document | It does what the concept of operations said, for the users it named |
| Design stable, few or no design changes | Field use has not forced a redesign |
| System installed and deployed in intended operational environment | Real sites, real users, not a demonstration site |
| Actual system fully demonstrated | Every function, in real use |
| Operational Test and Evaluation (OT&E) completed | A planned evaluation of the system in operation |
| All documentation completed | Manuals, maintenance, training and records |
An item that often catches research teams is "design stable, few or no design changes". If each new installation needs a modification, the system is still being developed in the field, and a reviewer will place it lower.
What does TRL 9 look like in different fields?
| Field | TRL 8 example | TRL 9 example |
|---|---|---|
| Water treatment | Production units qualified and installed at limited sites | Units running at many sites through all seasons, with operating records |
| Medical device | Final device verified and validated against its specification | Device in routine clinical use, with post-market performance data |
| Software | Debugged, integrated, documented and verified | Running in production for real users, with support in place |
| Chemical process | First commercial-scale unit qualified to the process specification | Commercial plant running over normal operating ranges and feedstock variations |
Regulated products also need approvals, which sit beside the TRL scale; see TRL for medical devices. Manufacturing readiness is a separate scale too; MRL vs TRL explains how the two pair at the top.
Proving TRL 9
A worked example
Illustration with invented figures. A solar-powered cold storage unit for farmers reached TRL 8 after qualification tests and a limited trial at two sites. To claim TRL 9, the company plans a year of operation across conditions it named in its operational concept.
| Item | Detail | Cost (₹) |
|---|---|---|
| Units deployed | 12, across three climate zones | 54,00,000 |
| Monitoring | Remote temperature and power logging for 12 months | 6,00,000 |
| Operational evaluation | Independent agency visits each site twice | 8,00,000 |
| Field service | Technician support and spares | 7,00,000 |
| Documentation | Operations, maintenance and training manuals | 3,00,000 |
| Total | 78,00,000 |
The most important line is not the largest. Twelve months of logs across three climate zones, with no design change needed, is the evidence that separates TRL 9 from a good TRL 8 trial.
How does ZTRAF check TRL 9?
ZTRAF, the Zernyx Technology Readiness Assessment Framework, is Zernyx's own copyrighted framework, aligned with global standards and used in TRL Pro. It covers more than 60 technology domains and subdomains, so "full range of conditions" is judged for the kind of technology you have, whether that means seasons, loads and operators for a cold storage unit or real users at real volume for software. You answer structured questions with your evidence and get back an assessed TRL from 1 to 9, the gaps to close and the next steps, with a Zernyx certificate.
A funder or buyer may still ask for your level in NASA or NTRAF wording. Run the ZTRAF assessment first, then state the level in the wording they ask for.
Common mistakes
- Treating the first sale as proof of TRL 9.
- Deploying only at friendly or demonstration sites.
- Covering one season or one climate and calling it the full range.
- Changing the design at each installation.
- No written operational concept to judge performance against.
My view: TRL 9 is earned with time and records more than with engineering, and teams that start logging operational data from the first deployment reach it with far less argument. The hedge is that "full range of expected conditions" is a judgement, and two reviewers can disagree about how much variety is enough; state your conditions plainly and let the reviewer see the data.
If you want a structured check before you claim the level, TRL Pro assesses your technology's readiness and returns a level from TRL 1 to 9, using Zernyx's own copyrighted framework (ZTRAF) covering more than 60 technology domains and subdomains.
Common questions
What is the difference between TRL 8 and TRL 9?
At TRL 8 the actual system is complete and qualified through test and demonstration, operating in a limited operational environment. At TRL 9 it is proven in actual use, over the full range of expected conditions. The step is from passing qualification to working in the field.
What evidence does NTRAF ask for at TRL 9?
An Operational Environment Testing Report, plus critical items: the system functions as defined in its operational concept, the design is stable with few or no changes, it is installed and deployed in the intended environment, fully demonstrated, operational test and evaluation is complete, and all documentation is complete.
Is a product on sale automatically at TRL 9?
Not automatically. Sales show a market, but TRL 9 asks whether the actual system has been proven in operational use over the full range of conditions, with documented results. A product sold only in one climate or one type of site may still have gaps.
Is TRL 9 the end of development?
For that version of the technology, yes. Improvements, new markets or new operating conditions can bring parts of the system back to lower levels, and manufacturing readiness and regulatory approval are assessed separately.