Difference between revisions of "TRL1"
Wiki.admin (talk | contribs) |
Wiki.admin (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | {{DISPLAYTITLE: | + | {{DISPLAYTITLE:Technology Readiness Level 1 – Basic Principles Observed}} |
| − | + | __TOC__ | |
| − | <div style=" | + | <div style="border:1px solid #d0d7de; background:#f6f8fa; padding:18px; margin-bottom:20px;"> |
| − | + | <div style="font-size:180%; font-weight:bold; color:#1f2933;">Technology Readiness Level 1</div> | |
| − | + | <div style="font-size:120%; color:#3b4a5a; margin-top:4px;">Basic Principles Observed</div> | |
| − | + | <div style="margin-top:12px;"> | |
| − | + | This page introduces the first level of the Technology Readiness Level scale and provides a common entry point for the TRL 1 documentation of the Collaborative Bee projects. | |
| − | |||
</div> | </div> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
| − | == | + | == Purpose of this page == |
| − | + | This page defines the meaning of '''Technology Readiness Level 1 (TRL 1)''' and explains how it is used within the Collaborative Bee project framework. | |
| − | + | It is intended to provide a shared reference before accessing the project-specific TRL 1 pages: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | {| class="wikitable" style="width:100%;" | |
| − | + | |- | |
| − | + | ! style="width:25%; background:#eef1f4;" | Project | |
| − | + | ! style="width:30%; background:#eef1f4;" | TRL 1 page | |
| − | + | ! style="background:#eef1f4;" | Scope | |
| − | + | |- | |
| − | + | | '''Mini-Bee''' | |
| − | + | | [[TRL1 Mini-Bee|TRL 1 – Mini-Bee]] | |
| − | + | | Hybrid VTOL multicopter concept for humanitarian and emergency missions. | |
| + | |- | ||
| + | | '''Bee Plane''' | ||
| + | | [[TRL1 Bee Plane|TRL 1 – Bee Plane]] | ||
| + | | Early-stage aircraft concept developed within the Collaborative Bee framework. | ||
| + | |- | ||
| + | | '''Iso-Plane''' | ||
| + | | [[TRL1 Iso-Plane|TRL 1 – Iso-Plane]] | ||
| + | | Early-stage aircraft concept based on specific technical and operational assumptions. | ||
| + | |} | ||
| − | + | == What are Technology Readiness Levels? == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''Technology Readiness Levels''' are a structured scale used to assess the maturity of a technology. | |
| − | + | They help project teams, contributors, partners and stakeholders understand whether a technology is still at the stage of scientific observation, concept formulation, prototype development, validation, qualification or operational use. | |
| − | + | TRLs are useful for: | |
| − | + | * structuring research and development activities; | |
| − | + | * clarifying the maturity of each project; | |
| − | + | * supporting technical reviews; | |
| − | + | * preparing industrial development roadmaps; | |
| − | + | * improving communication with academic, industrial and institutional partners; | |
| + | * anticipating certification and validation work. | ||
== TRL scale overview == | == TRL scale overview == | ||
| − | {| class="wikitable" style="width:100% | + | {| class="wikitable" style="width:100%;" |
|- | |- | ||
| − | ! style="width:10%; background:# | + | ! style="width:10%; background:#eef1f4;" | Level |
| − | ! style="width: | + | ! style="width:30%; background:#eef1f4;" | Name |
| − | ! style="background:# | + | ! style="background:#eef1f4;" | General meaning |
|- | |- | ||
| − | | | + | | '''TRL 1''' |
| − | + | | Basic principles observed | |
| − | | Scientific principles are identified | + | | Scientific or technical principles are identified. |
|- | |- | ||
| − | | | + | | '''TRL 2''' |
| Technology concept formulated | | Technology concept formulated | ||
| A possible application is described. | | A possible application is described. | ||
|- | |- | ||
| − | | | + | | '''TRL 3''' |
| Experimental proof of concept | | Experimental proof of concept | ||
| First analytical or experimental evidence supports the concept. | | First analytical or experimental evidence supports the concept. | ||
|- | |- | ||
| − | | | + | | '''TRL 4''' |
| Technology validated in laboratory | | Technology validated in laboratory | ||
| − | | Key functions are | + | | Key functions are validated in a controlled environment. |
|- | |- | ||
| − | | | + | | '''TRL 5''' |
| Technology validated in relevant environment | | Technology validated in relevant environment | ||
| The technology is tested in conditions closer to real use. | | The technology is tested in conditions closer to real use. | ||
|- | |- | ||
| − | | | + | | '''TRL 6''' |
| Technology demonstrated in relevant environment | | Technology demonstrated in relevant environment | ||
| A representative prototype demonstrates the main functions. | | A representative prototype demonstrates the main functions. | ||
|- | |- | ||
| − | | | + | | '''TRL 7''' |
| − | | | + | | System prototype demonstrated in operational environment |
| − | | A prototype is | + | | A prototype is demonstrated in realistic operational conditions. |
|- | |- | ||
| − | | | + | | '''TRL 8''' |
| System complete and qualified | | System complete and qualified | ||
| The system is completed, tested and qualified. | | The system is completed, tested and qualified. | ||
|- | |- | ||
| − | | | + | | '''TRL 9''' |
| − | | | + | | Actual system proven in operational use |
| − | | The technology is | + | | The technology is proven through real operational use. |
|} | |} | ||
| − | == | + | == Definition of TRL 1 == |
| − | + | '''TRL 1 – Basic Principles Observed''' is the first maturity level of a technology project. | |
| − | |||
| − | At this stage, the | + | At this stage, the objective is to identify the scientific, physical, technical or operational principles that may support a future concept. |
| − | TRL 1 | + | TRL 1 does not mean that a product, prototype or complete architecture already exists. |
| − | + | It means that the first technical foundations have been identified and can be documented. | |
| − | == | + | == TRL 1 within Collaborative Bee projects == |
| − | + | Within the Collaborative Bee framework, TRL 1 is used to document the starting point of each project in a consistent and reusable way. | |
| − | |||
| − | |||
| − | |||
| − | + | For each project, TRL 1 should clarify: | |
| − | + | * the mission or need addressed by the project; | |
| − | + | * the basic principles that justify the concept; | |
| + | * the initial assumptions; | ||
| + | * comparable technologies or references; | ||
| + | * the main uncertainties; | ||
| + | * the first technical and operational risks; | ||
| + | * the questions that must be answered before moving to TRL 2. | ||
| − | + | This approach helps create continuity between academic, industrial and individual contributors. | |
| − | + | == Expected outputs at TRL 1 == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | ||
{| class="wikitable" style="width:100%;" | {| class="wikitable" style="width:100%;" | ||
|- | |- | ||
| − | ! style="width: | + | ! style="width:30%; background:#eef1f4;" | Output |
| − | ! style="background:# | + | ! style="background:#eef1f4;" | Description |
|- | |- | ||
| − | | '''Mission | + | | '''Mission statement''' |
| − | | First | + | | First description of the operational need or opportunity addressed by the project. |
|- | |- | ||
| '''Basic principles note''' | | '''Basic principles note''' | ||
| − | | | + | | Identification of the main scientific or technical principles supporting the idea. |
|- | |- | ||
| '''Initial assumptions''' | | '''Initial assumptions''' | ||
| − | | Early assumptions about | + | | Early assumptions about the system, mission, environment, energy, structure or operation. |
|- | |- | ||
| − | | ''' | + | | '''Reference technologies''' |
| − | | First list of | + | | First list of comparable systems, technologies, publications or existing projects. |
|- | |- | ||
| '''Open questions''' | | '''Open questions''' | ||
| − | | | + | | Main questions that must be studied before formulating a complete concept. |
|- | |- | ||
| − | | ''' | + | | '''Initial risk list''' |
| − | | | + | | First identification of technical, safety, operational, regulatory or industrial risks. |
|} | |} | ||
| − | == What is not expected at TRL 1 | + | == What is not expected at TRL 1 == |
| − | + | At TRL 1, the following items are normally not yet required: | |
| − | + | * a final design; | |
| − | + | * a detailed system architecture; | |
| − | + | * a prototype; | |
| + | * validated performance data; | ||
| + | * laboratory test results; | ||
| + | * certification compliance evidence; | ||
| + | * industrialization planning; | ||
| + | * operational procedures. | ||
| − | + | These elements are progressively developed at higher TRL levels. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== TRL 1 exit criteria == | == TRL 1 exit criteria == | ||
| − | A project | + | A project may move from TRL 1 to TRL 2 when the following criteria are sufficiently documented: |
{| class="wikitable" style="width:100%;" | {| class="wikitable" style="width:100%;" | ||
|- | |- | ||
| − | ! style="width:8%; background:# | + | ! style="width:8%; background:#eef1f4;" | # |
| − | ! style="background:# | + | ! style="background:#eef1f4;" | Criterion |
| − | ! style="width: | + | ! style="width:20%; background:#eef1f4;" | Status |
|- | |- | ||
| 1 | | 1 | ||
| Line 224: | Line 181: | ||
|- | |- | ||
| 3 | | 3 | ||
| − | | The | + | | The initial assumptions are documented. |
| To be assessed | | To be assessed | ||
|- | |- | ||
| 4 | | 4 | ||
| − | | The main | + | | The main uncertainties and risks are listed. |
| To be assessed | | To be assessed | ||
|- | |- | ||
| Line 236: | Line 193: | ||
|} | |} | ||
| − | == | + | == Recommended structure for project-specific TRL 1 pages == |
| − | + | Each project-specific TRL 1 page should follow a common structure to ensure clarity and comparability across projects. | |
| − | + | Recommended structure: | |
| + | # Project overview | ||
# Mission or need | # Mission or need | ||
# Basic principles observed | # Basic principles observed | ||
| − | # | + | # Initial technical assumptions |
# Comparable technologies or references | # Comparable technologies or references | ||
# Main opportunities | # Main opportunities | ||
# Main uncertainties | # Main uncertainties | ||
| − | # | + | # Initial risks |
# Questions to solve before TRL 2 | # Questions to solve before TRL 2 | ||
# Contributors and references | # Contributors and references | ||
| − | + | == Project access == | |
| + | |||
| + | {| class="wikitable" style="width:100%;" | ||
| + | |- | ||
| + | ! style="width:25%; background:#eef1f4;" | Project | ||
| + | ! style="width:25%; background:#eef1f4;" | Access | ||
| + | ! style="background:#eef1f4;" | Objective of the TRL 1 page | ||
| + | |- | ||
| + | | '''Mini-Bee''' | ||
| + | | [[TRL1 Mini-Bee|Open page]] | ||
| + | | Document the basic principles behind the hybrid VTOL multicopter concept. | ||
| + | |- | ||
| + | | '''Bee Plane''' | ||
| + | | [[TRL1 Bee Plane|Open page]] | ||
| + | | Document the first principles and assumptions behind the Bee Plane concept. | ||
| + | |- | ||
| + | | '''Iso-Plane''' | ||
| + | | [[TRL1 Iso-Plane|Open page]] | ||
| + | | Document the first principles and assumptions behind the Iso-Plane concept. | ||
| + | |} | ||
== Summary == | == Summary == | ||
| − | + | TRL 1 is the foundation level of a technology project. | |
| − | It | + | It provides a structured starting point before the project moves toward a formulated concept. |
| − | + | Its role is to document the first principles, the initial assumptions and the key questions that will guide the next stages of development. | |
| − | |||
| − | <div style=" | + | <div style="border:1px solid #d0d7de; background:#f6f8fa; padding:14px; margin-top:20px;"> |
| − | + | '''Next step:''' once TRL 1 is sufficiently documented, the project may progress toward '''TRL 2 – Technology Concept Formulated'''. | |
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
Revision as of 12:16, 6 May 2026
This page introduces the first level of the Technology Readiness Level scale and provides a common entry point for the TRL 1 documentation of the Collaborative Bee projects.
Purpose of this page
This page defines the meaning of Technology Readiness Level 1 (TRL 1) and explains how it is used within the Collaborative Bee project framework.
It is intended to provide a shared reference before accessing the project-specific TRL 1 pages:
| Project | TRL 1 page | Scope |
|---|---|---|
| Mini-Bee | TRL 1 – Mini-Bee | Hybrid VTOL multicopter concept for humanitarian and emergency missions. |
| Bee Plane | TRL 1 – Bee Plane | Early-stage aircraft concept developed within the Collaborative Bee framework. |
| Iso-Plane | TRL 1 – Iso-Plane | Early-stage aircraft concept based on specific technical and operational assumptions. |
What are Technology Readiness Levels?
Technology Readiness Levels are a structured scale used to assess the maturity of a technology.
They help project teams, contributors, partners and stakeholders understand whether a technology is still at the stage of scientific observation, concept formulation, prototype development, validation, qualification or operational use.
TRLs are useful for:
- structuring research and development activities;
- clarifying the maturity of each project;
- supporting technical reviews;
- preparing industrial development roadmaps;
- improving communication with academic, industrial and institutional partners;
- anticipating certification and validation work.
TRL scale overview
| Level | Name | General meaning |
|---|---|---|
| TRL 1 | Basic principles observed | Scientific or technical principles are identified. |
| TRL 2 | Technology concept formulated | A possible application is described. |
| TRL 3 | Experimental proof of concept | First analytical or experimental evidence supports the concept. |
| TRL 4 | Technology validated in laboratory | Key functions are validated in a controlled environment. |
| TRL 5 | Technology validated in relevant environment | The technology is tested in conditions closer to real use. |
| TRL 6 | Technology demonstrated in relevant environment | A representative prototype demonstrates the main functions. |
| TRL 7 | System prototype demonstrated in operational environment | A prototype is demonstrated in realistic operational conditions. |
| TRL 8 | System complete and qualified | The system is completed, tested and qualified. |
| TRL 9 | Actual system proven in operational use | The technology is proven through real operational use. |
Definition of TRL 1
TRL 1 – Basic Principles Observed is the first maturity level of a technology project.
At this stage, the objective is to identify the scientific, physical, technical or operational principles that may support a future concept.
TRL 1 does not mean that a product, prototype or complete architecture already exists. It means that the first technical foundations have been identified and can be documented.
TRL 1 within Collaborative Bee projects
Within the Collaborative Bee framework, TRL 1 is used to document the starting point of each project in a consistent and reusable way.
For each project, TRL 1 should clarify:
- the mission or need addressed by the project;
- the basic principles that justify the concept;
- the initial assumptions;
- comparable technologies or references;
- the main uncertainties;
- the first technical and operational risks;
- the questions that must be answered before moving to TRL 2.
This approach helps create continuity between academic, industrial and individual contributors.
Expected outputs at TRL 1
| Output | Description |
|---|---|
| Mission statement | First description of the operational need or opportunity addressed by the project. |
| Basic principles note | Identification of the main scientific or technical principles supporting the idea. |
| Initial assumptions | Early assumptions about the system, mission, environment, energy, structure or operation. |
| Reference technologies | First list of comparable systems, technologies, publications or existing projects. |
| Open questions | Main questions that must be studied before formulating a complete concept. |
| Initial risk list | First identification of technical, safety, operational, regulatory or industrial risks. |
What is not expected at TRL 1
At TRL 1, the following items are normally not yet required:
- a final design;
- a detailed system architecture;
- a prototype;
- validated performance data;
- laboratory test results;
- certification compliance evidence;
- industrialization planning;
- operational procedures.
These elements are progressively developed at higher TRL levels.
TRL 1 exit criteria
A project may move from TRL 1 to TRL 2 when the following criteria are sufficiently documented:
| # | Criterion | Status |
|---|---|---|
| 1 | The basic principles have been identified. | To be assessed |
| 2 | A possible application has been described. | To be assessed |
| 3 | The initial assumptions are documented. | To be assessed |
| 4 | The main uncertainties and risks are listed. | To be assessed |
| 5 | A first concept direction can be formulated. | To be assessed |
Recommended structure for project-specific TRL 1 pages
Each project-specific TRL 1 page should follow a common structure to ensure clarity and comparability across projects.
Recommended structure:
- Project overview
- Mission or need
- Basic principles observed
- Initial technical assumptions
- Comparable technologies or references
- Main opportunities
- Main uncertainties
- Initial risks
- Questions to solve before TRL 2
- Contributors and references
Project access
| Project | Access | Objective of the TRL 1 page |
|---|---|---|
| Mini-Bee | Open page | Document the basic principles behind the hybrid VTOL multicopter concept. |
| Bee Plane | Open page | Document the first principles and assumptions behind the Bee Plane concept. |
| Iso-Plane | Open page | Document the first principles and assumptions behind the Iso-Plane concept. |
Summary
TRL 1 is the foundation level of a technology project.
It provides a structured starting point before the project moves toward a formulated concept. Its role is to document the first principles, the initial assumptions and the key questions that will guide the next stages of development.
Next step: once TRL 1 is sufficiently documented, the project may progress toward TRL 2 – Technology Concept Formulated.