Difference between revisions of "TRL1"

From beeplane
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:TRL 1 – Basic Principles Observed}}
+
{{DISPLAYTITLE:Technology Readiness Level 1 – Basic Principles Observed}}
  
__NOTOC__
+
__TOC__
  
<div style="background:linear-gradient(135deg,#0b3d5c,#1679a8); color:white; padding:28px; border-radius:16px; margin-bottom:22px; box-shadow:0 4px 12px rgba(0,0,0,0.18);">
+
<div style="border:1px solid #cfd6dd; background:#ffffff; margin-bottom:20px;">
  <div style="font-size:260%; font-weight:700; line-height:1.1;">Technology Readiness Level 1</div>
+
<div style="background:#1f3a5f; color:#ffffff; padding:12px 16px; font-weight:bold;">
  <div style="font-size:135%; margin-top:8px;">Basic Principles Observed</div>
+
Technology Readiness Level 1 Basic Principles Observed
  <div style="font-size:105%; margin-top:16px; max-width:900px;">
+
</div>
    TRL 1 is the starting point of an innovation journey: the moment when scientific principles, first observations and early ideas become structured enough to open a technology project.
+
<div style="padding:16px;">
  </div>
+
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 style="display:flex; flex-wrap:wrap; gap:14px; margin-bottom:24px;">
+
== Project access ==
  
  <div style="flex:1; min-width:220px; background:#f5fbff; border:1px solid #c8e2f3; border-radius:12px; padding:16px;">
+
{| style="width:100%; border-collapse:separate; border-spacing:12px; margin-bottom:20px;"
    <div style="font-size:140%; font-weight:bold; color:#0b5c84;">Purpose</div>
+
|-
    <div style="margin-top:8px;">
+
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff;" |
      Explain what TRL 1 means and provide a shared entry point for the first maturity stage of the Collaborative Bee projects.
+
<div style="background:#f3f5f7; border-bottom:1px solid #cfd6dd; padding:10px; font-weight:bold;">
    </div>
+
Mini-Bee
  </div>
+
</div>
 +
<div style="padding:12px;">
 +
Hybrid VTOL multicopter concept for humanitarian, emergency and light air ambulance missions.
  
  <div style="flex:1; min-width:220px; background:#fffaf0; border:1px solid #f0d39a; border-radius:12px; padding:16px;">
+
<br /><br />
    <div style="font-size:140%; font-weight:bold; color:#9a6500;">Main idea</div>
+
'''[[TRL1 Mini-Bee|Open TRL 1 – Mini-Bee]]'''
    <div style="margin-top:8px;">
+
</div>
      At TRL 1, the technology is not yet designed or validated. The goal is to identify the basic principles that may support a future concept.
 
    </div>
 
  </div>
 
  
  <div style="flex:1; min-width:220px; background:#f7fff7; border:1px solid #b9ddb9; border-radius:12px; padding:16px;">
+
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff;" |
    <div style="font-size:140%; font-weight:bold; color:#2f7a2f;">Next step</div>
+
<div style="background:#f3f5f7; border-bottom:1px solid #cfd6dd; padding:10px; font-weight:bold;">
    <div style="margin-top:8px;">
+
Bee Plane
      When the first principles are clear, the project can move toward TRL 2: technology concept formulated.
+
</div>
    </div>
+
<div style="padding:12px;">
  </div>
+
Early-stage aircraft concept developed within the Collaborative Bee framework.
  
 +
<br /><br />
 +
'''[[TRL1 Bee Plane|Open TRL 1 – Bee Plane]]'''
 
</div>
 
</div>
  
== Project TRL 1 pages ==
+
| 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 style="display:flex; flex-wrap:wrap; gap:16px; margin:18px 0 28px 0;">
+
<br /><br />
 +
'''[[TRL1 Iso-Plane|Open TRL 1 – Iso-Plane]]'''
 +
</div>
 +
|}
  
  <div style="flex:1; min-width:240px; border:1px solid #d8d8d8; border-radius:14px; padding:18px; background:#ffffff; box-shadow:0 2px 8px rgba(0,0,0,0.08);">
+
== Purpose of this page ==
    <div style="font-size:160%; font-weight:bold; color:#0b5c84;">Mini-Bee</div>
 
    <div style="margin-top:8px; min-height:70px;">
 
      Hybrid VTOL multicopter concept for humanitarian, emergency and light air ambulance missions.
 
    </div>
 
    <div style="margin-top:14px;">
 
      <span style="background:#e8f3ff; padding:6px 10px; border-radius:20px;">[[TRL1 Mini-Bee|Open TRL 1 page]]</span>
 
    </div>
 
  </div>
 
  
  <div style="flex:1; min-width:240px; border:1px solid #d8d8d8; border-radius:14px; padding:18px; background:#ffffff; box-shadow:0 2px 8px rgba(0,0,0,0.08);">
+
This page defines the meaning of '''Technology Readiness Level 1 (TRL 1)''' and explains how it is used within the Collaborative Bee project framework.
    <div style="font-size:160%; font-weight:bold; color:#8a5a00;">Bee Plane</div>
 
    <div style="margin-top:8px; min-height:70px;">
 
      Aircraft concept exploring new principles for transport, efficiency and collaborative aviation development.
 
    </div>
 
    <div style="margin-top:14px;">
 
      <span style="background:#fff1d6; padding:6px 10px; border-radius:20px;">[[TRL1 Bee Plane|Open TRL 1 page]]</span>
 
    </div>
 
  </div>
 
  
  <div style="flex:1; min-width:240px; border:1px solid #d8d8d8; border-radius:14px; padding:18px; background:#ffffff; box-shadow:0 2px 8px rgba(0,0,0,0.08);">
+
It is designed to provide a shared reference before accessing the project-specific TRL 1 pages.
    <div style="font-size:160%; font-weight:bold; color:#2f7a2f;">Iso-Plane</div>
 
    <div style="margin-top:8px; min-height:70px;">
 
      Early aircraft concept focused on first physical principles, possible use cases and technical assumptions.
 
    </div>
 
    <div style="margin-top:14px;">
 
      <span style="background:#e9f8e9; padding:6px 10px; border-radius:20px;">[[TRL1 Iso-Plane|Open TRL 1 page]]</span>
 
    </div>
 
  </div>
 
  
 +
<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''' — or '''TRLs''' — are a maturity scale used to describe how far a technology has progressed.
+
'''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:
  
They help a project team understand whether an idea is still a scientific observation, a concept, a prototype, a validated system, or an operational product.
+
* 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.
  
<div style="border-left:6px solid #1679a8; background:#f5fbff; padding:14px 18px; margin:18px 0; border-radius:8px;">
+
== TRL maturity pathway ==
'''Simple question behind TRLs:''' how mature is the technology, and what evidence do we have to prove it?
+
 
</div>
+
{| 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%; text-align:left; border-collapse:collapse;"
+
{| class="wikitable" style="width:100%;"
 
|-
 
|-
! style="width:10%; background:#0b5c84; color:white;" | Level
+
! style="width:10%; background:#eef1f4;" | Level
! style="width:28%; background:#0b5c84; color:white;" | Name
+
! style="width:30%; background:#eef1f4;" | Name
! style="background:#0b5c84; color:white;" | Meaning
+
! style="background:#eef1f4;" | General meaning
 
|-
 
|-
| style="font-weight:bold; background:#e8f3ff;" | TRL 1
+
| '''TRL 1'''
| '''Basic principles observed'''
+
| Basic principles observed
| Scientific principles are identified. The idea is at the earliest stage.
+
| Scientific or technical principles are identified.
 
|-
 
|-
| style="font-weight:bold;" | TRL 2
+
| '''TRL 2'''
 
| Technology concept formulated
 
| Technology concept formulated
 
| A possible application is described.
 
| A possible application is described.
 
|-
 
|-
| style="font-weight:bold;" | TRL 3
+
| '''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.
 
|-
 
|-
| style="font-weight:bold;" | TRL 4
+
| '''TRL 4'''
 
| Technology validated in laboratory
 
| Technology validated in laboratory
| Key functions are tested in a controlled environment.
+
| Key functions are validated in a controlled environment.
 
|-
 
|-
| style="font-weight:bold;" | TRL 5
+
| '''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.
 
|-
 
|-
| style="font-weight:bold;" | TRL 6
+
| '''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.
 
|-
 
|-
| style="font-weight:bold;" | TRL 7
+
| '''TRL 7'''
| Prototype demonstrated in operational environment
+
| System prototype demonstrated in operational environment
| A prototype is tested in realistic operational conditions.
+
| A prototype is demonstrated in realistic operational conditions.
 
|-
 
|-
| style="font-weight:bold;" | TRL 8
+
| '''TRL 8'''
 
| System complete and qualified
 
| System complete and qualified
 
| The system is completed, tested and qualified.
 
| The system is completed, tested and qualified.
 
|-
 
|-
| style="font-weight:bold;" | TRL 9
+
| '''TRL 9'''
| System proven in operational use
+
| Actual system proven in operational use
| The technology is fully operational and used in real missions.
+
| The technology is proven through real operational use.
 
|}
 
|}
  
== Focus on TRL 1 ==
+
== Definition of TRL 1 ==
  
<div style="background:#fafafa; border:1px solid #ddd; border-radius:14px; padding:18px; margin:18px 0;">
+
'''TRL 1 – Basic Principles Observed''' is the first maturity level of a technology project.
<div style="font-size:150%; font-weight:bold; color:#0b5c84;">TRL 1 means: the journey begins.</div>
 
  
At this stage, the project team observes a principle, identifies a possible opportunity and starts collecting the first technical questions.
+
At this stage, the objective is to identify the scientific, physical, technical or operational principles that may support a future concept.
  
TRL 1 is not a prototype stage. It is not a validation stage. It is the moment where the first foundations are written clearly enough to open a structured project.
+
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.
</div>
 
  
== What happens at TRL 1? ==
+
{| style="width:100%; border-collapse:separate; border-spacing:12px; margin:16px 0;"
 
 
{| style="width:100%; border-spacing:12px; border-collapse:separate;"
 
 
|-
 
|-
| style="width:33%; vertical-align:top; background:#f5fbff; border:1px solid #c8e2f3; border-radius:12px; padding:14px;" |
+
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''1. Observe'''
+
'''Observe'''
  
Identify scientific, physical, technical or operational principles that may support a future technology.
+
Identify basic scientific, technical or operational principles.
  
| style="width:33%; vertical-align:top; background:#fffaf0; border:1px solid #f0d39a; border-radius:12px; padding:14px;" |
+
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''2. Question'''
+
'''Question'''
  
List the first unknowns, assumptions, risks and possible limitations.
+
List assumptions, opportunities, unknowns and early risks.
  
| style="width:33%; vertical-align:top; background:#f7fff7; border:1px solid #b9ddb9; border-radius:12px; padding:14px;" |
+
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''3. Structure'''
+
'''Prepare'''
  
Create the first project page, organize the reasoning and prepare the transition toward TRL 2.
+
Create the documentation base before moving toward a formulated concept.
 
|}
 
|}
  
== Typical TRL 1 deliverables ==
+
== 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:28%; background:#eef6ff;" | Deliverable
+
! style="width:30%; background:#eef1f4;" | Output
! style="background:#eef6ff;" | Description
+
! style="background:#eef1f4;" | Description
 
|-
 
|-
| '''Mission or need statement'''
+
| '''Mission statement'''
| First explanation of the problem, mission or opportunity.
+
| First description of the operational need or opportunity addressed by the project.
 
|-
 
|-
 
| '''Basic principles note'''
 
| '''Basic principles note'''
| Short description of the scientific or technical principles observed.
+
| Identification of the main scientific or technical principles supporting the idea.
 
|-
 
|-
 
| '''Initial assumptions'''
 
| '''Initial assumptions'''
| Early assumptions about mass, energy, structure, operation, mission or environment.
+
| Early assumptions about the system, mission, environment, energy, structure or operation.
 
|-
 
|-
| '''Comparable references'''
+
| '''Reference technologies'''
| First list of existing technologies, projects, papers or systems that may inspire the concept.
+
| First list of comparable systems, technologies, publications or existing projects.
 
|-
 
|-
 
| '''Open questions'''
 
| '''Open questions'''
| Questions that must be answered before moving to TRL 2.
+
| Main questions that must be studied before formulating a complete concept.
 
|-
 
|-
| '''First risk list'''
+
| '''Initial risk list'''
| Early technical, operational, safety or regulatory risks.
+
| First identification of technical, safety, operational, regulatory or industrial risks.
 
|}
 
|}
  
== What is not expected at TRL 1? ==
+
== What is not expected at TRL 1 ==
  
<div style="display:flex; flex-wrap:wrap; gap:12px; margin:16px 0;">
+
{| 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'''
  
  <div style="flex:1; min-width:200px; background:#fff5f5; border:1px solid #e5b7b7; border-radius:12px; padding:12px;">
+
The architecture is not frozen at this stage.
    No prototype required
 
  </div>
 
  
  <div style="flex:1; min-width:200px; background:#fff5f5; border:1px solid #e5b7b7; border-radius:12px; padding:12px;">
+
| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
    No final architecture required
+
'''No prototype'''
  </div>
 
  
  <div style="flex:1; min-width:200px; background:#fff5f5; border:1px solid #e5b7b7; border-radius:12px; padding:12px;">
+
Physical demonstration is not required at TRL 1.
    No certification evidence required
 
  </div>
 
  
  <div style="flex:1; min-width:200px; background:#fff5f5; border:1px solid #e5b7b7; border-radius:12px; padding:12px;">
+
| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
    No detailed industrial plan required
+
'''No certification evidence'''
  </div>
 
  
</div>
+
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 can normally move from '''TRL 1''' to '''TRL 2''' when the following points are clear enough:
+
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:#0b5c84; color:white;" | #
+
! style="width:8%; background:#eef1f4;" | #
! style="background:#0b5c84; color:white;" | Criterion
+
! style="background:#eef1f4;" | Criterion
! style="width:18%; background:#0b5c84; color:white;" | Status
+
! style="width:20%; background:#eef1f4;" | Status
 
|-
 
|-
 
| 1
 
| 1
Line 224: Line 257:
 
|-
 
|-
 
| 3
 
| 3
| The main assumptions are listed.
+
| The initial assumptions are documented.
 
| To be assessed
 
| To be assessed
 
|-
 
|-
 
| 4
 
| 4
| The main unknowns and risks are documented.
+
| The main uncertainties and risks are listed.
 
| To be assessed
 
| To be assessed
 
|-
 
|-
Line 236: Line 269:
 
|}
 
|}
  
== Suggested structure for each project TRL 1 page ==
+
== Recommended structure for project-specific TRL 1 pages ==
  
<div style="background:#f5fbff; border:1px solid #c8e2f3; border-radius:12px; padding:16px; margin:18px 0;">
+
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 preferably follow this structure:
+
{| class="wikitable" style="width:100%;"
 
+
|-
# Mission or need
+
! style="width:8%; background:#eef1f4;" | #
# Basic principles observed
+
! style="width:28%; background:#eef1f4;" | Section
# Early technical assumptions
+
! style="background:#eef1f4;" | Purpose
# Comparable technologies or references
+
|-
# Main opportunities
+
| 1
# Main uncertainties
+
| Project overview
# First risks
+
| Present the project and its general objective.
# Questions to solve before TRL 2
+
|-
# Contributors and references
+
| 2
 
+
| Mission or need
</div>
+
| 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 stage.'''
+
TRL 1 is the foundation level of a technology project.
  
It transforms an intuition into a documented starting point
+
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.
It does not prove that the technology works yet.
 
It simply gives the project a clear first base for future concept work, technical studies and collaboration.
 
  
<div style="background:linear-gradient(135deg,#f5fbff,#ffffff); border:1px solid #c8e2f3; border-radius:14px; padding:18px; margin-top:24px;">
+
<div style="border:1px solid #cfd6dd; background:#f6f8fa; padding:14px; margin-top:18px;">
<div style="font-size:140%; font-weight:bold; color:#0b5c84;">Next maturity step</div>
+
'''Next step:''' once TRL 1 is sufficiently documented, the project may progress toward '''TRL 2 – Technology Concept Formulated'''.
<div style="margin-top:8px;">
 
After TRL 1, the project may move toward '''TRL 2 – Technology Concept Formulated''', where the first concept is described and linked to a potential application.
 
</div>
 
 
</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.



Open TRL 1 – Mini-Bee

Bee Plane

Early-stage aircraft concept developed within the Collaborative Bee framework.



Open TRL 1 – Bee Plane

Iso-Plane

Early-stage aircraft concept based on specific technical and operational assumptions.



Open TRL 1 – Iso-Plane

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.

See also