TRL 7 meaning: system prototype demonstrated in an operational environment
TRL 7 meaning: a full-scale system prototype demonstrated in the operational environment, what NASA, the EU and India's NTRAF require, and the evidence needed.
Part of the guide TRL levels explained: what TRL 1 to 9 really mean, and how to place your technology
TRL 7 means a full-scale system prototype, near or at the planned operational system, has been demonstrated in an operational environment. India's National Technology Readiness Assessment Framework (NTRAF) places it in the system commissioning stage and asks for a Full-Scale System Prototype Demonstration Report. NASA's exit criterion is documented test performance agreeing with analytical predictions.
A pilot unit that worked well in a simulated test rig is now bolted into a real plant, running on real feed, operated by the plant's own staff. Within a week the problems are different: dust, vibration, a power supply that dips at shift change, an operator who skips a step. TRL 7 is the level at which a technology has met those conditions and still performed.
It is also the level at which academic projects often hand over to industry, because the operational environment usually belongs to someone else. This post explains what TRL 7 means under the three main definitions, the evidence India's framework asks for, how it differs from TRL 6 and TRL 8, and how to plan the demonstration.
What does TRL 7 mean?
| Framework | TRL 7 wording |
|---|---|
| NASA | System prototype demonstration in an operational environment |
| EU (Horizon Europe) | System prototype demonstration in operational environment |
| India (NTRAF) | Full scale system prototype demonstration in operational environment |
Sources: NASA ESTO, the Horizon Europe General Annexes and the National Technology Readiness Assessment Framework.
The three wordings are close. NTRAF adds "full scale", and describes the prototype as "near, or at, planned operational system". NASA's hardware description asks for a high-fidelity engineering unit that adequately addresses all critical scaling issues, built and operated to demonstrate performance in the actual operational environment and platform. Its software description asks for prototype software with all key functionality, well integrated with operational hardware and software systems, with most bugs removed and limited documentation.
NASA's exit criterion is the same as at TRL 6: "documented test performance demonstrating agreement with analytical predictions". The difference is where the test happens.
Where does TRL 7 sit?
TRL 7 opens system commissioning
NTRAF's stages make the shift clear. TRL 4 to 6 is technology demonstration. TRL 7 and 8 are system commissioning. TRL 9 is system operations. At TRL 7 you are no longer showing that a technology can work; you are showing that a system built around it works where it will be used.
For the level below, see TRL 6 meaning. For the whole path to deployment, see moving from TRL 6 to TRL 9.
What does "operational environment" mean?
NTRAF defines the operational environment as the environment that addresses all the operational requirements and specifications required of the final system, including platform and packaging. A relevant environment, used at TRL 5 and 6, only simulates the key aspects.
| Relevant environment (TRL 6) | Operational environment (TRL 7) | |
|---|---|---|
| What it covers | Key physical and chemical conditions | All operational requirements of the final system |
| Platform and packaging | May differ | Included |
| Who operates | Usually the research team | Often the end user or partner |
| Typical place | Test rig, simulator, pilot hall | Customer site, field, hospital, plant |
NTRAF also notes that at TRL 7 the prototype may be tested in a relevant operational environment that is not the eventual platform, giving a test-bed aircraft as an example. So a field trial on a representative site can count, as long as it addresses the operational requirements.
What evidence does NTRAF ask for?
NTRAF's key question at this level is: "Has the full scale system prototype successfully been demonstrated in relevant operational environment?" The supporting document is a Full-Scale System Prototype Demonstration Report. The critical items are:
| NTRAF critical item | What it means in practice |
|---|---|
| Tested in relevant operational environment, but not the eventual platform | A representative site or test-bed is acceptable |
| Components representative of production components | Parts are close to what will be manufactured |
| Materials, processes, methods and design techniques moderately developed and verified | The way it is built is largely settled |
| Materials and manufacturing processes initially demonstrated | Some units have been made the production way |
| Fully integrated prototype demonstrated in actual or simulated operational environment | The whole system, not a subsystem |
| Safety and adverse-effect issues identified and mitigated | Risks to users and the environment are handled |
The manufacturing and safety items are where academic submissions are likely to fall short. A prototype assembled by hand in the lab, however well it performs on site, does not show components representative of production.
What does TRL 7 look like in different fields?
| Field | TRL 6 example | TRL 7 example |
|---|---|---|
| Water treatment | Pilot unit at 1,000 litres a day on a borewell | Full-scale unit supplying a village or plant for a season, run by local operators |
| Medical device | Engineering prototype in a simulated clinical setting | Near-final device used in a hospital under an approved study |
| Software | Prototype on full-scale realistic problems, partly integrated | All key functions running with the user's live systems |
| Chemical process | Pilot reactor with plant feedstock | Demonstration unit inside the plant, on plant utilities |
Medical and drug technologies add regulatory steps at this level; see TRL for medical devices.
How should you plan a TRL 7 demonstration?
Planning a TRL 7 demonstration
Finding the site is the hardest step and the one to start first. Most operational environments belong to a company, a utility, a hospital or a government user. Agree access, duration, data ownership and liability in writing before any hardware moves.
Illustration with invented figures. A team taking a water treatment system from TRL 6 to TRL 7 budgets ₹45 lakh: ₹22 lakh for a full-scale unit made with production-grade components, ₹8 lakh for site preparation and installation, ₹9 lakh for six months of operation and monitoring, ₹4 lakh for safety and water quality testing by an accredited lab, and ₹2 lakh for the demonstration report. That is far more than the ₹18 lakh sensor budget in our TRL 6 example, mainly because of full-scale hardware and months of field operation.
How does ZTRAF check TRL 7?
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 "operational environment" is judged for the kind of technology you have, whether that is a village water plant, a hospital ward or a factory line. 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 partner 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
- Calling a long test in a simulator an operational demonstration.
- Demonstrating a subsystem and claiming TRL 7 for the whole system.
- Hand-built prototypes with no link to production components or processes.
- No written predictions, so results cannot be shown to agree with anything.
- Ignoring safety and adverse effects, which NTRAF lists as a critical item.
My view: TRL 7 is where a research team should expect to share control with a partner, and planning that partnership early matters more than the technology itself at this stage. The hedge is that NTRAF's acceptance of a representative site leaves room for judgement, and I am not sure every reviewer draws the line in the same place; describe your site's limits plainly.
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 6 and TRL 7?
TRL 6 is an engineering or pilot-scale prototype demonstrated in a relevant environment, which simulates the key conditions of use. TRL 7 is a full-scale system prototype, near or at the planned system, demonstrated in an operational environment that addresses all the requirements of the final system.
What is the difference between TRL 7 and TRL 8?
At TRL 7 a prototype is demonstrated in the operational environment. At TRL 8 the actual system is completed and qualified through test and demonstration. NASA describes TRL 8 as the actual system completed and 'flight qualified'. The step is from prototype to the finished, qualified product.
What evidence does NTRAF ask for at TRL 7?
A Full-Scale System Prototype Demonstration Report, plus critical items such as components representative of production components, materials and manufacturing processes initially demonstrated, a fully integrated prototype demonstrated in an actual or simulated operational environment, and safety and adverse-effect issues identified and mitigated.
Can a research lab reach TRL 7 on its own?
Rarely. TRL 7 needs a full-scale prototype in the real operating environment, which usually means an industry partner, an end-user site or a field trial. Academic projects commonly reach TRL 7 through a licensee, a sponsored project or a government user agency.