In the ECSS system, Technology Readiness Levels (TRLs) are not defined directly in the testing standard ECSS-E-ST-10-03C Rev.1 – Testing (31 May 2022). Instead, ECSS adopts ISO 16290 through ECSS-E-AS-11C1October2014, which is the ECSS reference for TRL definitions and assessment criteria. [
ECSS Definition of TRL
ECSS treats a TRL as a measure of the maturity of a technology, based on demonstrated evidence and achievement of specific milestones. A technology cannot be claimed to be at a given TRL unless the criteria for that level have been met and documented.
| TRL | ECSS Description |
| TRL 1 | Basic principles observed and reported. Potential applications identified. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 2 | Technology concept and/or application formulated. Preliminary concept exists but no proof of concept. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 3 | Analytical and experimental proof of concept demonstrated. Models and laboratory data support expected performance. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 4 | Functional verification of a component or breadboard in a laboratory environment. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 5 | Critical functions verified in a relevant environment using representative breadboards. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 6 | Representative model demonstrates critical functions in a relevant environment. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 7 | Representative model demonstrates performance in the operational environment (ground or space). ECSS additionally requires a successful Qualification Review (QR). [ECSS-E-AS-…ctober2014 | Word] |
| TRL 8 | Actual flight hardware qualified and integrated into the final system (“flight qualified”). ECSS additionally requires a successful Acceptance Review (AR) at system level. [ECSS-E-AS-…ctober2014 | Word] |
| TRL 9 | Technology proven through successful mission operations (“flight proven”). ECSS additionally requires a successful Commissioning Review (CRR). [ECSS-E-AS-…ctober2014 | Word] |
An Important ECSS Distinction
One of the key differences between ECSS and some simplified TRL interpretations is that TRL progression is tied to formal project evidence and reviews, not only technical tests. For example:
Within system engineering, ECSS requires technologies to be assessed and tracked by TRL throughout project phases. The technology status is recorded in a Technology Readiness Status List (TRSL) and managed through the technology plan. ECSS-E-ST-10C-Rev.1(15February2017) explicitly requires technologies to be assessed using the TRL definitions of ECSS-E-AS-11.
Practical Engineering Interpretation
A useful engineering shorthand is:
For spacecraft programmes, customers commonly expect critical technologies to reach at least TRL 6 before Phase B/C commitment, with TRL 8–9 expected for flight hardware in operational programmes. This latter point is common ESA/industry practice, but the formal ECSS requirement is that the TRL level claimed must satisfy the criteria defined in ECSS-E-AS-11C1October2014.
Technology Readiness Levels (TRLs) and spacecraft testing are closely linked because testing provides the objective evidence needed to justify progression from one TRL to the next.
Although the testing standard itself does not define TRLs, it explains how testing is used to demonstrate that a technology, equipment item, or spacecraft can survive and operate in its intended environment. The standard states that testing is part of the overall system engineering and verification process, providing evidence for qualification and acceptance of space products.
A practical mapping is:
| TRL | Typical Testing Evidence |
| TRL 1–3 | Analytical studies, laboratory experiments, proof-of-concept demonstrations. |
| TRL 4 | Functional verification of components or breadboards in a laboratory environment. |
| TRL 5 | Environmental testing in a relevant environment (thermal, vibration, EMC, etc.) on representative hardware. |
| TRL 6 | Qualification-style testing of a representative model demonstrating critical functions in a relevant environment. |
| TRL 7 | Qualification testing demonstrating operation in an operationally representative spacecraft environment. |
| TRL 8 | Acceptance and protoflight testing of actual flight hardware. |
| TRL 9 | Successful operation in space after launch and commissioning. |
The testing standard focuses primarily on the activities that support TRL 5 through TRL 8:
Qualification Testing → TRL 6–7
ECSS requires qualification testing to demonstrate that equipment or spacecraft elements perform according to specification in their intended environments with qualification margins.
Examples include:
These tests provide evidence that the design is robust enough for flight conditions.
Acceptance Testing → TRL 8
Acceptance testing demonstrates that each flight unit conforms to specification and is free from workmanship defects and material flaws.
This is the stage at which the actual flight hardware is shown to be ready for delivery and launch.
Protoflight Testing → TRL 7–8
Protoflight testing combines qualification and acceptance objectives on the first flight model. ECSS describes this as demonstrating both environmental capability and flight readiness.
Key Environmental Tests Supporting TRL Growth
The standard defines comprehensive test programmes including:
Each successful test reduces technical risk and increases confidence that the technology will survive launch and operate in orbit.
From an ECSS systems engineering viewpoint:
Consider a new spacecraft star tracker:
In summary, TRLs describe technology maturity, while ECSS testing provides the verification evidence that allows a technology to claim that maturity level. Qualification testing is the key bridge to TRL 6–7, acceptance testing supports TRL 8, and flight operation is required for TRL 9.
Whether you’re looking to contact us for the first time or have another testing requirement, we’d love to hear from you.
