Difference between revisions of "TRL1"

From beeplane
Jump to navigation Jump to search
Line 3: Line 3:
 
__TOC__
 
__TOC__
  
<div style="border:1px solid #d0d7de; background:#f6f8fa; padding:18px; margin-bottom:20px;">
+
<div style="border:1px solid #cfd6dd; background:#ffffff; margin-bottom:22px;">
<div style="font-size:180%; font-weight:bold; color:#1f2933;">Technology Readiness Level 1</div>
+
  <div style="background:#1f3a5f; height:8px;"></div>
<div style="font-size:120%; color:#3b4a5a; margin-top:4px;">Basic Principles Observed</div>
+
  <div style="padding:22px;">
<div style="margin-top:12px;">
+
    <div style="font-size:190%; font-weight:bold; color:#1f2933;">Technology Readiness Level 1</div>
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 style="font-size:125%; color:#4b5563; margin-top:4px;">Basic Principles Observed</div>
 +
    <div style="margin-top:14px; max-width:950px;">
 +
      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>
 
</div>
 +
 +
== Project access ==
 +
 +
<div style="display:flex; flex-wrap:wrap; gap:14px; margin:16px 0 24px 0;">
 +
 +
  <div style="flex:1; min-width:250px; border:1px solid #d0d7de; background:#ffffff;">
 +
    <div style="background:#f3f5f7; padding:10px 14px; font-weight:bold; color:#1f3a5f; border-bottom:1px solid #d0d7de;">
 +
      Mini-Bee
 +
    </div>
 +
    <div style="padding:14px;">
 +
      <div style="min-height:62px;">
 +
        Hybrid VTOL multicopter concept for humanitarian, emergency and light air ambulance missions.
 +
      </div>
 +
      <div style="margin-top:14px;">
 +
        '''[[TRL1 Mini-Bee|Open TRL 1 – Mini-Bee]]'''
 +
      </div>
 +
    </div>
 +
  </div>
 +
 +
  <div style="flex:1; min-width:250px; border:1px solid #d0d7de; background:#ffffff;">
 +
    <div style="background:#f3f5f7; padding:10px 14px; font-weight:bold; color:#1f3a5f; border-bottom:1px solid #d0d7de;">
 +
      Bee Plane
 +
    </div>
 +
    <div style="padding:14px;">
 +
      <div style="min-height:62px;">
 +
        Early-stage aircraft concept developed within the Collaborative Bee framework.
 +
      </div>
 +
      <div style="margin-top:14px;">
 +
        '''[[TRL1 Bee Plane|Open TRL 1 – Bee Plane]]'''
 +
      </div>
 +
    </div>
 +
  </div>
 +
 +
  <div style="flex:1; min-width:250px; border:1px solid #d0d7de; background:#ffffff;">
 +
    <div style="background:#f3f5f7; padding:10px 14px; font-weight:bold; color:#1f3a5f; border-bottom:1px solid #d0d7de;">
 +
      Iso-Plane
 +
    </div>
 +
    <div style="padding:14px;">
 +
      <div style="min-height:62px;">
 +
        Early-stage aircraft concept based on specific technical and operational assumptions.
 +
      </div>
 +
      <div style="margin-top:14px;">
 +
        '''[[TRL1 Iso-Plane|Open TRL 1 – Iso-Plane]]'''
 +
      </div>
 +
    </div>
 +
  </div>
 +
 
</div>
 
</div>
  
Line 15: Line 66:
 
This page defines the meaning of '''Technology Readiness Level 1 (TRL 1)''' and explains how it is used within the Collaborative Bee project framework.
 
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:
+
It is designed to provide a common reference before accessing the project-specific TRL 1 pages.
  
{| class="wikitable" style="width:100%;"
+
<div style="border-left:5px solid #1f3a5f; background:#f6f8fa; padding:14px 16px; margin:18px 0;">
|-
+
'''Objective:''' create a clear and professional maturity framework for early-stage project documentation.
! style="width:25%; background:#eef1f4;" | Project
+
</div>
! 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? ==
 
== What are Technology Readiness Levels? ==
Line 52: Line 88:
  
 
== TRL scale overview ==
 
== TRL scale overview ==
 +
 +
<div style="margin:16px 0 22px 0;">
 +
{| style="width:100%; border-collapse:collapse; text-align:center;"
 +
|-
 +
| style="background:#1f3a5f; color:white; padding:10px; border:1px solid #cfd6dd; font-weight:bold;" | TRL 1
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 2
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 3
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 4
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 5
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 6
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 7
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 8
 +
| style="background:#f3f5f7; padding:10px; border:1px solid #cfd6dd;" | TRL 9
 +
|-
 +
| style="background:#eef2f6; padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Basic principles
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Concept
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Proof of concept
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Lab validation
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Relevant environment
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Demonstration
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Operational prototype
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Qualified system
 +
| style="padding:8px; border:1px solid #cfd6dd; font-size:90%;" | Operational use
 +
|}
 +
</div>
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
Line 102: Line 163:
 
At this stage, the objective is to identify the scientific, physical, technical or operational principles that may support a future concept.
 
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.
+
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.
It means that the first technical foundations have been identified and can be documented.
+
 
 +
<div style="background:#f6f8fa; border:1px solid #d0d7de; padding:16px; margin:18px 0;">
 +
{| style="width:100%;"
 +
|-
 +
| style="width:33%; vertical-align:top; padding-right:14px;" |
 +
'''At TRL 1, the project observes'''
 +
 
 +
Basic scientific, technical or operational principles are identified.
 +
 
 +
| style="width:33%; vertical-align:top; padding-right:14px;" |
 +
'''At TRL 1, the project questions'''
 +
 
 +
Initial assumptions, opportunities, unknowns and risks are listed.
 +
 
 +
| style="width:33%; vertical-align:top;" |
 +
'''At TRL 1, the project prepares'''
 +
 
 +
The documentation base is created before moving toward a formulated concept.
 +
|}
 +
</div>
  
 
== TRL 1 within Collaborative Bee projects ==
 
== TRL 1 within Collaborative Bee projects ==
Line 119: Line 199:
 
* the questions that must be answered before moving to TRL 2.
 
* the questions that must be answered before moving to TRL 2.
  
This approach helps create continuity between academic, industrial and individual contributors.
+
This approach supports continuity between academic, industrial and individual contributors.
  
 
== Expected outputs at TRL 1 ==
 
== Expected outputs at TRL 1 ==
Line 149: Line 229:
 
== 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:
+
<div style="display:flex; flex-wrap:wrap; gap:12px; margin:16px 0 20px 0;">
  
* a final design;
+
  <div style="flex:1; min-width:210px; border:1px solid #d0d7de; background:#ffffff; padding:12px;">
* a detailed system architecture;
+
    '''No final design'''<br />
* a prototype;
+
    The architecture is not frozen at this stage.
* validated performance data;
+
  </div>
* laboratory test results;
 
* certification compliance evidence;
 
* industrialization planning;
 
* operational procedures.
 
  
These elements are progressively developed at higher TRL levels.
+
  <div style="flex:1; min-width:210px; border:1px solid #d0d7de; background:#ffffff; padding:12px;">
 +
    '''No prototype'''<br />
 +
    Physical demonstration is not required at TRL 1.
 +
  </div>
 +
 
 +
  <div style="flex:1; min-width:210px; border:1px solid #d0d7de; background:#ffffff; padding:12px;">
 +
    '''No certification evidence'''<br />
 +
    Compliance demonstration belongs to later stages.
 +
  </div>
 +
 
 +
  <div style="flex:1; min-width:210px; border:1px solid #d0d7de; background:#ffffff; padding:12px;">
 +
    '''No industrial plan'''<br />
 +
    Industrialization is not expected at this level.
 +
  </div>
 +
 
 +
</div>
  
 
== TRL 1 exit criteria ==
 
== TRL 1 exit criteria ==
Line 196: Line 287:
  
 
Each project-specific TRL 1 page should follow a common structure to ensure clarity and comparability across projects.
 
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 ==
 
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
 
|-
 
|-
! style="width:25%; background:#eef1f4;" | Project
+
! style="width:8%; background:#eef1f4;" | #
! style="width:25%; background:#eef1f4;" | Access
+
! style="background:#eef1f4;" | Section
! style="background:#eef1f4;" | Objective of the TRL 1 page
+
! 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.
 
|-
 
|-
| '''Mini-Bee'''
+
| 8
| [[TRL1 Mini-Bee|Open page]]
+
| Initial risks
| Document the basic principles behind the hybrid VTOL multicopter concept.
+
| List early technical, operational, safety or regulatory risks.
 
|-
 
|-
| '''Bee Plane'''
+
| 9
| [[TRL1 Bee Plane|Open page]]
+
| Questions to solve before TRL 2
| Document the first principles and assumptions behind the Bee Plane concept.
+
| Define the key questions to answer before concept formulation.
 
|-
 
|-
| '''Iso-Plane'''
+
| 10
| [[TRL1 Iso-Plane|Open page]]
+
| Contributors and references
| Document the first principles and assumptions behind the Iso-Plane concept.
+
| List contributors and useful documentation.
 
|}
 
|}
  
Line 235: Line 339:
 
TRL 1 is the foundation level of a technology project.
 
TRL 1 is the foundation level of a technology project.
  
It provides a structured starting point before the project moves toward a formulated concept.
+
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.
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="border:1px solid #d0d7de; background:#f6f8fa; padding:14px; margin-top:20px;">
+
<div style="border:1px solid #cfd6dd; background:#f6f8fa; padding:16px; margin-top:20px;">
 
'''Next step:''' once TRL 1 is sufficiently documented, the project may progress toward '''TRL 2 – Technology Concept Formulated'''.
 
'''Next step:''' once TRL 1 is sufficiently documented, the project may progress toward '''TRL 2 – Technology Concept Formulated'''.
 
</div>
 
</div>

Revision as of 12:26, 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 common reference before accessing the project-specific TRL 1 pages.

Objective: create 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 scale overview

TRL 1 TRL 2 TRL 3 TRL 4 TRL 5 TRL 6 TRL 7 TRL 8 TRL 9
Basic principles Concept Proof of concept Lab validation Relevant environment Demonstration Operational prototype Qualified system Operational use
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.

At TRL 1, the project observes

Basic scientific, technical or operational principles are identified.

At TRL 1, the project questions

Initial assumptions, opportunities, unknowns and risks are listed.

At TRL 1, the project prepares

The documentation base is created 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.

See also