Difference between revisions of "TRL1"
Wiki.admin (talk | contribs) |
Wiki.admin (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{DISPLAYTITLE: | + | {{DISPLAYTITLE:Technology Readiness Level 1 – Basic Principles Observed}} |
| − | + | __TOC__ | |
| − | <div style=" | + | <div style="border:1px solid #cfd6dd; background:#ffffff; margin-bottom:20px;"> |
| − | + | <div style="background:#1f3a5f; color:#ffffff; padding:12px 16px; font-weight:bold;"> | |
| − | + | Technology Readiness Level 1 – Basic Principles Observed | |
| − | + | </div> | |
| − | + | <div style="padding:16px;"> | |
| − | + | This page introduces the first maturity 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> | ||
| − | + | == Project access == | |
| − | + | {| style="width:100%; border-collapse:separate; border-spacing:12px; margin-bottom:20px;" | |
| − | + | |- | |
| − | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff;" | | |
| − | + | <div style="background:#f3f5f7; border-bottom:1px solid #cfd6dd; padding:10px; font-weight:bold;"> | |
| − | + | Mini-Bee | |
| − | + | </div> | |
| + | <div style="padding:12px;"> | ||
| + | Hybrid VTOL multicopter concept for humanitarian, emergency and light air ambulance missions. | ||
| − | + | <br /><br /> | |
| − | + | '''[[TRL1 Mini-Bee|Open TRL 1 – Mini-Bee]]''' | |
| − | + | </div> | |
| − | |||
| − | |||
| − | |||
| − | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff;" | | |
| − | + | <div style="background:#f3f5f7; border-bottom:1px solid #cfd6dd; padding:10px; font-weight:bold;"> | |
| − | + | Bee Plane | |
| − | + | </div> | |
| − | + | <div style="padding:12px;"> | |
| − | + | Early-stage aircraft concept developed within the Collaborative Bee framework. | |
| + | <br /><br /> | ||
| + | '''[[TRL1 Bee Plane|Open TRL 1 – Bee Plane]]''' | ||
</div> | </div> | ||
| − | == | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff;" | |
| + | <div style="background:#f3f5f7; border-bottom:1px solid #cfd6dd; padding:10px; font-weight:bold;"> | ||
| + | Iso-Plane | ||
| + | </div> | ||
| + | <div style="padding:12px;"> | ||
| + | Early-stage aircraft concept based on specific technical and operational assumptions. | ||
| − | <div | + | <br /><br /> |
| + | '''[[TRL1 Iso-Plane|Open TRL 1 – Iso-Plane]]''' | ||
| + | </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 designed to provide a shared reference before accessing the project-specific TRL 1 pages. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | <div style="border-left:4px solid #1f3a5f; background:#f6f8fa; padding:12px; margin:16px 0;"> | ||
| + | '''Objective:''' provide a clear and professional maturity framework for early-stage project documentation. | ||
</div> | </div> | ||
== What are Technology Readiness Levels? == | == What are Technology Readiness Levels? == | ||
| − | '''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 maturity pathway == | |
| − | + | ||
| − | + | {| style="width:100%; border-collapse:collapse; text-align:center; margin:16px 0 20px 0;" | |
| + | |- | ||
| + | | style="background:#1f3a5f; color:#ffffff; border:1px solid #cfd6dd; padding:8px; font-weight:bold;" | TRL 1 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 2 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 3 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 4 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 5 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 6 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 7 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 8 | ||
| + | | style="background:#f3f5f7; border:1px solid #cfd6dd; padding:8px;" | TRL 9 | ||
| + | |- | ||
| + | | style="background:#eef1f4; border:1px solid #cfd6dd; padding:8px;" | Basic principles | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Concept | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Proof of concept | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Laboratory validation | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Relevant environment | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Demonstration | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Operational prototype | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Qualified system | ||
| + | | style="border:1px solid #cfd6dd; padding:8px;" | Operational use | ||
| + | |} | ||
== 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. |
| − | |||
| − | + | {| style="width:100%; border-collapse:separate; border-spacing:12px; margin:16px 0;" | |
| − | |||
| − | {| style="width:100%; border-spacing:12px; | ||
|- | |- | ||
| − | | style="width:33%; vertical-align:top | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" | |
| − | ''' | + | '''Observe''' |
| − | Identify scientific | + | Identify basic scientific, technical or operational principles. |
| − | | style="width:33%; vertical-align:top | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" | |
| − | ''' | + | '''Question''' |
| − | List | + | List assumptions, opportunities, unknowns and early risks. |
| − | | style="width:33%; vertical-align:top | + | | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" | |
| − | ''' | + | '''Prepare''' |
| − | Create the | + | Create the documentation base before moving toward a formulated concept. |
|} | |} | ||
| − | == | + | == 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 supports 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 == |
| − | + | {| style="width:100%; border-collapse:separate; border-spacing:12px; margin:16px 0;" | |
| + | |- | ||
| + | | style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" | | ||
| + | '''No final design''' | ||
| − | + | The architecture is not frozen at this stage. | |
| − | |||
| − | |||
| − | + | | style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" | | |
| − | + | '''No prototype''' | |
| − | |||
| − | + | Physical demonstration is not required at TRL 1. | |
| − | |||
| − | |||
| − | + | | style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" | | |
| − | + | '''No certification evidence''' | |
| − | |||
| − | + | Compliance demonstration belongs to later stages. | |
| + | |||
| + | | style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" | | ||
| + | '''No industrial plan''' | ||
| + | |||
| + | Industrialization is not expected at this level. | ||
| + | |} | ||
== 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 257: | ||
|- | |- | ||
| 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 269: | ||
|} | |} | ||
| − | == | + | == 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. | |
| − | + | {| class="wikitable" style="width:100%;" | |
| − | + | |- | |
| − | # Mission or need | + | ! style="width:8%; background:#eef1f4;" | # |
| − | + | ! style="width:28%; background:#eef1f4;" | Section | |
| − | + | ! style="background:#eef1f4;" | Purpose | |
| − | + | |- | |
| − | + | | 1 | |
| − | + | | Project overview | |
| − | + | | Present the project and its general objective. | |
| − | + | |- | |
| − | + | | 2 | |
| − | + | | Mission or need | |
| − | + | | Explain the operational need addressed by the project. | |
| + | |- | ||
| + | | 3 | ||
| + | | Basic principles observed | ||
| + | | Identify the scientific, technical or operational principles behind the idea. | ||
| + | |- | ||
| + | | 4 | ||
| + | | Initial technical assumptions | ||
| + | | List the first working assumptions. | ||
| + | |- | ||
| + | | 5 | ||
| + | | Comparable technologies or references | ||
| + | | Identify relevant existing systems or references. | ||
| + | |- | ||
| + | | 6 | ||
| + | | Main opportunities | ||
| + | | Explain the potential value of the project. | ||
| + | |- | ||
| + | | 7 | ||
| + | | Main uncertainties | ||
| + | | Identify what is still unknown. | ||
| + | |- | ||
| + | | 8 | ||
| + | | Initial risks | ||
| + | | List early technical, operational, safety or regulatory risks. | ||
| + | |- | ||
| + | | 9 | ||
| + | | Questions to solve before TRL 2 | ||
| + | | Define the key questions to answer before concept formulation. | ||
| + | |- | ||
| + | | 10 | ||
| + | | Contributors and references | ||
| + | | List contributors and useful documentation. | ||
| + | |} | ||
== 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 #cfd6dd; background:#f6f8fa; padding:14px; margin-top:18px;"> |
| − | + | '''Next step:''' once TRL 1 is sufficiently documented, the project may progress toward '''TRL 2 – Technology Concept Formulated'''. | |
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
Latest revision as of 12:32, 6 May 2026
Technology Readiness Level 1 – Basic Principles Observed
This page introduces the first maturity level of the Technology Readiness Level scale and provides a common entry point for the TRL 1 documentation of the Collaborative Bee projects.
Project access
|
Mini-Bee Hybrid VTOL multicopter concept for humanitarian, emergency and light air ambulance missions. |
Bee Plane Early-stage aircraft concept developed within the Collaborative Bee framework. |
Iso-Plane Early-stage aircraft concept based on specific technical and operational assumptions. |
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 designed to provide a shared reference before accessing the project-specific TRL 1 pages.
Objective: provide a clear and professional maturity framework for early-stage project documentation.
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 maturity pathway
| TRL 1 | TRL 2 | TRL 3 | TRL 4 | TRL 5 | TRL 6 | TRL 7 | TRL 8 | TRL 9 |
| Basic principles | Concept | Proof of concept | Laboratory validation | Relevant environment | Demonstration | Operational prototype | Qualified system | Operational use |
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.
|
Observe Identify basic scientific, technical or operational principles. |
Question List assumptions, opportunities, unknowns and early risks. |
Prepare Create the documentation base before moving toward a formulated concept. |
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 supports 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
|
No final design The architecture is not frozen at this stage. |
No prototype Physical demonstration is not required at TRL 1. |
No certification evidence Compliance demonstration belongs to later stages. |
No industrial plan Industrialization is not expected at this level. |
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.
| # | Section | Purpose |
|---|---|---|
| 1 | Project overview | Present the project and its general objective. |
| 2 | Mission or need | Explain the operational need addressed by the project. |
| 3 | Basic principles observed | Identify the scientific, technical or operational principles behind the idea. |
| 4 | Initial technical assumptions | List the first working assumptions. |
| 5 | Comparable technologies or references | Identify relevant existing systems or references. |
| 6 | Main opportunities | Explain the potential value of the project. |
| 7 | Main uncertainties | Identify what is still unknown. |
| 8 | Initial risks | List early technical, operational, safety or regulatory risks. |
| 9 | Questions to solve before TRL 2 | Define the key questions to answer before concept formulation. |
| 10 | Contributors and references | List contributors and useful documentation. |
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.