COMP4DRONES - User contributions [en]

RODENT network

2023-03-15T13:47:54Z

Grolleaue: /* 12. Intellectual Property */

=Draft of Memorandum of Understanding Founding and Operation of European Drone Technology Network (RODENT )=

==1. MoU Preamble ==

The European Commission and ECSEL JU have funded the COMP4DRONES project (Grant-Agreement ID 826610) on drone technologies to ensure European strategic autonomy in such technologies. Drones underpin most of our future business and private activities, with a potentially significant socio-economic impact. Europe's potential in the field of UAVs, including its world-class research community, must be strengthened and exploited to be at the forefront of UAV development.

The entire network will be a common resource and will become a shared facility, like a virtual laboratory providing access to knowledge and expertise and attracting talent. It should become a reference, creating an easy entry point to drone technology in Europe and should contribute to its visibility.

The ECSEL JU COMP4DRONES project has made several connections with other European projects active in this field (ADACORSA, Drones4Safety, AW-Drones, RIMA, OPTICS2, GOF2.0, etc.) whose participating parties will be approached to sign also this MoU.

==2. MoU Scope ==

The Organization and Operation of the European Drone Technology Network (RODENT) aims to provide access to knowledge and expertise, functioning as an umbrella for the European drone industry's value network.

The purpose of this MoU is to establish certain principles that the Parties agree that it shall govern both the process of forming the RODENT and the operations of the future RODENT.

If the Parties choose to enter into any binding obligations other than those listed in this MoU below, any such binding obligations shall be set forth in a teaming agreement or other agreement (defined as the Definitive Agreement), if any, to be negotiated and executed by authorized representatives of each Party, in the sole, absolute discretion of each Party.

The Parties understand and agree that this MoU may, or may not, lead to a Definitive Agreement. Failure to consummate a Definitive Agreement based on the Parties’ intentions shall not entitle either Party to any remedies or damages under contract law, tort law, or any other legal or equitable theory. For the avoidance of doubt, neither Party is obliged to conclude Definitive Agreements.

This MoU is not intended to constitute, create, or give effect to or otherwise recognize a joint venture, partnership, teaming agreement or similar enforceable arrangement. Neither Party hereto has any right or authority to make or undertake any promise or to make any representation for the other Parties, or to execute any document or to otherwise assume any obligations or responsibility in the name of or on behalf of the other Party hereto.

==3. RODENT Objectives ==

The main objective of the RODEN networks is to promote, encourage and assist the coordinated development and deployment of UAV-based technologies and services in Europe. The following specific objectives are identified:
# Set up a virtual drone design platform promoting drone services based on European technologies.
# Mapping of European “supply” skills
# Increase cooperation between European Drone Industry
# Enable more R&D activities
# Build a competitive offer
# Expand accessibility to European drone technologies
# Increase the availability of drone technologies
# Improve the interoperability of components and tools
# Increase the qualification of engineers through training to acquire new practices

==4. RODENT Definitions ==
# Founding Members: Partners of the COMP4DRONES project signing this MoU at the first round.
# Full Members (acronym RODENT Members): organisations from European Union (EU) or Associated Countries that will be invited to and will sign this MoU. RODENT founding Members are RODENT full members.
# Associate Members: Organizations from countries other than EU member states or associated countries that will be invited to sign this MoU.
# Research & Industry Members: Research Institutions or Companies within EU countries or Associated with drone technologies activities that will be invited to and will sign this MoU.
# Representatives. Employees of any member type within EU countries or Associated having received a signed mandate to represent their organizations at RODENT level. A Representative may assign a Deputy Representative.

==5. RODENT Governance ==

# General Assembly (GA): It is the highest RODENT governing body consisting of one Representative of each Full Member.
# Management Board (MB): It consists of five Full Member Representatives and manages RODENT operations. The GA elects it for a four-year term. The number of MB members may be changed by GA decision, but cannot be less than three.
# Coordinator: It is a Full Member hosting RODENT Management operations. The GA elect it for a four-year term. MB member, which is the Representative of the Coordinator and chairs RODENT GA, MB and Research and Innovation Board.
# Research and Innovation Board: It consists of research and industry experts that advises RODENT on research and industrial innovation. All RODENT Member Representatives of any type elect expert for a four years term, or less.
RODENT GA or MB can decide to create (or dissolve) special committees to work on any RODENT Operation.

==6. RODENT Operations ==

===6.1 RODENT Management ===

It concerns the management, dissemination, accounting and reporting of RODENT activities and resources. The management rules and procedures will be decided by the RODENT GA or the RODENT BoD and should be compatible with the internal legislation, rules and procedures of the coordinator's country. The Coordinator, in accordance with the legislation, rules and internal procedures of his country, will mainly manage the project as a funded project.

===6.2 RODENT Activities ===

All RODENT members, regardless of type, are welcome to participate in RODENT activities on a win-win basis. Below is a non-exhaustive list, to be updated during RODENT operations, of activities to achieve RODENT's goals:
# Set up working groups to study the multiple issues (interoperability, business model, industrial intellectual property, etc.) that need to be resolved in order to create a virtual platform for drone design
# Offer of short courses, lecture series, web lectures etc. to promote technologies that can be used by the drone industry
# Industry, research or academic secondments.
# Offering Drone vision: Drones system engineering workshop and drone grand challenges.
# SoA overviews on drone topics.
# Drone event calendar.

== 7. RODENT Dissemination/communication ==

They will be done mainly through the RODENT web portal, various lists and email channels that will be managed by the coordinator and various drone events.

== 8. RODENT Resources ==

RODENT resources come from its members of any kind, from its activities, from funded R&D projetcs or educational projects, but also from any other source, e.g., donations or sponsorships.

The activities mentioned in this MoU shall not, in principle, impose any financial obligations on the members of RODENT of any type. Each member, regardless of its type, shall bear the costs and expenses related to its participation in RODENT, unless otherwise specified and agreed/accepted by the member concerned.

Nothing contained in this MoU shall be construed as providing for the sharing of profits, losses, expenses, debts or liabilities arising out of the efforts of any of the Parties. All Parties agree to proceed at their own risk and expense and agree that each Party will be solely responsible for its own costs incurred in connection with its efforts under or related to this MoU, unless and until, if ever, other cost related responsibilities are set forth in a Definitive Agreement.

==9. RODENT International Cooperation ==

RODENT will seek active cooperation with any European, national and international entity engaged in Drones activities of any type, notably with any national Drones network within EU and with:
* KDT JU (https://www.kdt-ju.europa.eu/ )
* INSIDE Industry Association (https://www.inside-association.eu/ )
* SESAR 3 JU (https://www.sesarju.eu/ )
* EUROCONTROL (https://www.eurocontrol.int )
* EASA (https://www.easa.europa.eu )
* ENAC Laboratory (https://www.enac.fr/en )
* Drones Paris Region (https://systematic-paris-region.org/hubs-enjeux/hub-drones/ )
* Rozas (https://www.inta.es/CIAR/en/ )
* ADRA Association (https://adr-association.eu/ )
* Dronecode Foundation (https://www.dronecode.org/ )
* HiPEAC Network (https://www.hipeac.net/ )
* Aerial Connectivity Joint Activity – ACJA (https://www.gsma.com/iot/aerial-connectivity-joint-activity/ )

==10. RODENT Duration and Other Provisions ==

RODENT will start its activities as soon as at least five founding members from three European countries and participants in the ECSEL JU COMP4DRONES project (Grant-Agreement ID 826610) have signed this MoU. Potential members/associate members/research and industry members can adhere to this MoU by signing its copy, together with the coordinator. This MoU is valid for five years (2023-2027) and can be extended by decision of the RODENT General Assembly.

This MoU can only be changed by a written amendment agreed upon by the Parties and signed by persons authorised to bind the Parties.

Either Party may withdraw from this MoU at any time by providing written notification to the other Parties 30 days in advance.

Decisions of the RODENT General Assembly must be taken by a relative majority of the votes of all full members present. Decisions of the board of directors or any other board or committee of RODENT must be taken by unanimity, if possible, or by a relative majority in the second round, if the unanimous vote fails in the first round.

Any member of RODENT can refuse to execute a decision if it is contrary to the law of his country or to the internal rules governing its functioning.

RODENT may be dissolved by a decision of the GA of RODENT to take effect after a period of six months, so that any ongoing activity has been duly completed, in order to avoid any disadvantage to the members of RODENT.

RODENT members of any type are free to leave RODENT, after six months' notice and provided that any ongoing activity has been duly completed, in order to avoid any disadvantage to RODENT members.

In very exceptional cases of violation of the provisions of the RODENT Memorandum of Understanding, the GA of RODENT may decide to terminate the membership of a member of RODENT, regardless of its type, which will take effect after giving six months' notice to the member concerned.

==11. PERSONAL DATA PROTECTION AND CONFIDENTIALITY==

Personal data, as defined in Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data, will always be treated as Confidential Information, and will be protected with an adequate level of security and confidentiality, subject to any applicable legal, regulatory or contractual requirements.

All RODENT Members agree to comply with the EU Regulation 2016/679 (GDPR), as well as applicable national laws.

As the processing of personal data of individuals is necessary for the performance of this Agreement, all Members agree to enter into data processing agreements, which shall be attached to this MoU to constitute the entire Agreement and reflect the rights and obligations of each Party in this regard.

Unless otherwise agreed to in writing, the Parties hereto agree to keep all confidential information in this MoU and all related activities and documents strictly confidential unless the disclosure of such information by either Party is required under the law or order by any court of law, in which such Party (the Receiving Party) shall first inform the other Party (the Disclosing Party) before making such disclosure of the same. In respect of certain information that either Party may reveal to another Party, another Party hereby agrees to keep such information confidential. The confidential obligation under this clause shall remain in force 3 years after the termination of this MoU.

==12. INTELLECTUAL PROPERTY==

All trademarks, service marks, logos or other words or symbols identifying each Party`s respective products and services and all goodwill arising therefrom (hereinafter referred to as “Marks”) and all other proprietary and intellectual property rights, including but not limited to patents, know-how, inventions, copyrights are and will remain, unless otherwise stipulated in a specific contract, the exclusive property of the owner thereof. Neither Party acquires under this MoU any license or other right or interest in the patents, copyrights, trade secrets, service marks, trademarks or other proprietary and/ or intellectual property rights of the other Party nor will it take any action that jeopardizes such rights. Any use by a Party of the other Party`s Marks will require the prior written approval of such other Party and must be in compliance with any instruction and guidelines respecting the Marks made available by such other Party.

==13. APPLICABLE LAW AND SETTLEMENT OF DISPUTES==

This MoU is governed by the laws of Belgium, excluding its conflict of law provisions.

All disputes arising out of or in connection with this MoU, which cannot be solved amicably, shall be finally settled under the Rules of Arbitration of the International Chamber of Commerce by three arbitrators appointed in accordance with the said Rules. The place of arbitration shall be Brussels if not otherwise agreed by the conflicting Parties and the language of the arbitration proceeding shall be English. The award of the arbitration will be final and binding upon the Parties.

RODENT network

2023-03-15T13:47:06Z

Grolleaue: /* RODENT Dissemination/communication */

=Draft of Memorandum of Understanding Founding and Operation of European Drone Technology Network (RODENT )=

==1. MoU Preamble ==

The European Commission and ECSEL JU have funded the COMP4DRONES project (Grant-Agreement ID 826610) on drone technologies to ensure European strategic autonomy in such technologies. Drones underpin most of our future business and private activities, with a potentially significant socio-economic impact. Europe's potential in the field of UAVs, including its world-class research community, must be strengthened and exploited to be at the forefront of UAV development.

The entire network will be a common resource and will become a shared facility, like a virtual laboratory providing access to knowledge and expertise and attracting talent. It should become a reference, creating an easy entry point to drone technology in Europe and should contribute to its visibility.

The ECSEL JU COMP4DRONES project has made several connections with other European projects active in this field (ADACORSA, Drones4Safety, AW-Drones, RIMA, OPTICS2, GOF2.0, etc.) whose participating parties will be approached to sign also this MoU.

==2. MoU Scope ==

The Organization and Operation of the European Drone Technology Network (RODENT) aims to provide access to knowledge and expertise, functioning as an umbrella for the European drone industry's value network.

The purpose of this MoU is to establish certain principles that the Parties agree that it shall govern both the process of forming the RODENT and the operations of the future RODENT.

If the Parties choose to enter into any binding obligations other than those listed in this MoU below, any such binding obligations shall be set forth in a teaming agreement or other agreement (defined as the Definitive Agreement), if any, to be negotiated and executed by authorized representatives of each Party, in the sole, absolute discretion of each Party.

The Parties understand and agree that this MoU may, or may not, lead to a Definitive Agreement. Failure to consummate a Definitive Agreement based on the Parties’ intentions shall not entitle either Party to any remedies or damages under contract law, tort law, or any other legal or equitable theory. For the avoidance of doubt, neither Party is obliged to conclude Definitive Agreements.

This MoU is not intended to constitute, create, or give effect to or otherwise recognize a joint venture, partnership, teaming agreement or similar enforceable arrangement. Neither Party hereto has any right or authority to make or undertake any promise or to make any representation for the other Parties, or to execute any document or to otherwise assume any obligations or responsibility in the name of or on behalf of the other Party hereto.

==3. RODENT Objectives ==

The main objective of the RODEN networks is to promote, encourage and assist the coordinated development and deployment of UAV-based technologies and services in Europe. The following specific objectives are identified:
# Set up a virtual drone design platform promoting drone services based on European technologies.
# Mapping of European “supply” skills
# Increase cooperation between European Drone Industry
# Enable more R&D activities
# Build a competitive offer
# Expand accessibility to European drone technologies
# Increase the availability of drone technologies
# Improve the interoperability of components and tools
# Increase the qualification of engineers through training to acquire new practices

==4. RODENT Definitions ==
# Founding Members: Partners of the COMP4DRONES project signing this MoU at the first round.
# Full Members (acronym RODENT Members): organisations from European Union (EU) or Associated Countries that will be invited to and will sign this MoU. RODENT founding Members are RODENT full members.
# Associate Members: Organizations from countries other than EU member states or associated countries that will be invited to sign this MoU.
# Research & Industry Members: Research Institutions or Companies within EU countries or Associated with drone technologies activities that will be invited to and will sign this MoU.
# Representatives. Employees of any member type within EU countries or Associated having received a signed mandate to represent their organizations at RODENT level. A Representative may assign a Deputy Representative.

==5. RODENT Governance ==

# General Assembly (GA): It is the highest RODENT governing body consisting of one Representative of each Full Member.
# Management Board (MB): It consists of five Full Member Representatives and manages RODENT operations. The GA elects it for a four-year term. The number of MB members may be changed by GA decision, but cannot be less than three.
# Coordinator: It is a Full Member hosting RODENT Management operations. The GA elect it for a four-year term. MB member, which is the Representative of the Coordinator and chairs RODENT GA, MB and Research and Innovation Board.
# Research and Innovation Board: It consists of research and industry experts that advises RODENT on research and industrial innovation. All RODENT Member Representatives of any type elect expert for a four years term, or less.
RODENT GA or MB can decide to create (or dissolve) special committees to work on any RODENT Operation.

==6. RODENT Operations ==

===6.1 RODENT Management ===

It concerns the management, dissemination, accounting and reporting of RODENT activities and resources. The management rules and procedures will be decided by the RODENT GA or the RODENT BoD and should be compatible with the internal legislation, rules and procedures of the coordinator's country. The Coordinator, in accordance with the legislation, rules and internal procedures of his country, will mainly manage the project as a funded project.

===6.2 RODENT Activities ===

All RODENT members, regardless of type, are welcome to participate in RODENT activities on a win-win basis. Below is a non-exhaustive list, to be updated during RODENT operations, of activities to achieve RODENT's goals:
# Set up working groups to study the multiple issues (interoperability, business model, industrial intellectual property, etc.) that need to be resolved in order to create a virtual platform for drone design
# Offer of short courses, lecture series, web lectures etc. to promote technologies that can be used by the drone industry
# Industry, research or academic secondments.
# Offering Drone vision: Drones system engineering workshop and drone grand challenges.
# SoA overviews on drone topics.
# Drone event calendar.

== 7. RODENT Dissemination/communication ==

They will be done mainly through the RODENT web portal, various lists and email channels that will be managed by the coordinator and various drone events.

== 8. RODENT Resources ==

RODENT resources come from its members of any kind, from its activities, from funded R&D projetcs or educational projects, but also from any other source, e.g., donations or sponsorships.

The activities mentioned in this MoU shall not, in principle, impose any financial obligations on the members of RODENT of any type. Each member, regardless of its type, shall bear the costs and expenses related to its participation in RODENT, unless otherwise specified and agreed/accepted by the member concerned.

Nothing contained in this MoU shall be construed as providing for the sharing of profits, losses, expenses, debts or liabilities arising out of the efforts of any of the Parties. All Parties agree to proceed at their own risk and expense and agree that each Party will be solely responsible for its own costs incurred in connection with its efforts under or related to this MoU, unless and until, if ever, other cost related responsibilities are set forth in a Definitive Agreement.

==9. RODENT International Cooperation ==

RODENT will seek active cooperation with any European, national and international entity engaged in Drones activities of any type, notably with any national Drones network within EU and with:
* KDT JU (https://www.kdt-ju.europa.eu/ )
* INSIDE Industry Association (https://www.inside-association.eu/ )
* SESAR 3 JU (https://www.sesarju.eu/ )
* EUROCONTROL (https://www.eurocontrol.int )
* EASA (https://www.easa.europa.eu )
* ENAC Laboratory (https://www.enac.fr/en )
* Drones Paris Region (https://systematic-paris-region.org/hubs-enjeux/hub-drones/ )
* Rozas (https://www.inta.es/CIAR/en/ )
* ADRA Association (https://adr-association.eu/ )
* Dronecode Foundation (https://www.dronecode.org/ )
* HiPEAC Network (https://www.hipeac.net/ )
* Aerial Connectivity Joint Activity – ACJA (https://www.gsma.com/iot/aerial-connectivity-joint-activity/ )

==10. RODENT Duration and Other Provisions ==

RODENT will start its activities as soon as at least five founding members from three European countries and participants in the ECSEL JU COMP4DRONES project (Grant-Agreement ID 826610) have signed this MoU. Potential members/associate members/research and industry members can adhere to this MoU by signing its copy, together with the coordinator. This MoU is valid for five years (2023-2027) and can be extended by decision of the RODENT General Assembly.

This MoU can only be changed by a written amendment agreed upon by the Parties and signed by persons authorised to bind the Parties.

Either Party may withdraw from this MoU at any time by providing written notification to the other Parties 30 days in advance.

Decisions of the RODENT General Assembly must be taken by a relative majority of the votes of all full members present. Decisions of the board of directors or any other board or committee of RODENT must be taken by unanimity, if possible, or by a relative majority in the second round, if the unanimous vote fails in the first round.

Any member of RODENT can refuse to execute a decision if it is contrary to the law of his country or to the internal rules governing its functioning.

RODENT may be dissolved by a decision of the GA of RODENT to take effect after a period of six months, so that any ongoing activity has been duly completed, in order to avoid any disadvantage to the members of RODENT.

RODENT members of any type are free to leave RODENT, after six months' notice and provided that any ongoing activity has been duly completed, in order to avoid any disadvantage to RODENT members.

In very exceptional cases of violation of the provisions of the RODENT Memorandum of Understanding, the GA of RODENT may decide to terminate the membership of a member of RODENT, regardless of its type, which will take effect after giving six months' notice to the member concerned.

==11. PERSONAL DATA PROTECTION AND CONFIDENTIALITY==

Personal data, as defined in Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data, will always be treated as Confidential Information, and will be protected with an adequate level of security and confidentiality, subject to any applicable legal, regulatory or contractual requirements.

All RODENT Members agree to comply with the EU Regulation 2016/679 (GDPR), as well as applicable national laws.

As the processing of personal data of individuals is necessary for the performance of this Agreement, all Members agree to enter into data processing agreements, which shall be attached to this MoU to constitute the entire Agreement and reflect the rights and obligations of each Party in this regard.

Unless otherwise agreed to in writing, the Parties hereto agree to keep all confidential information in this MoU and all related activities and documents strictly confidential unless the disclosure of such information by either Party is required under the law or order by any court of law, in which such Party (the Receiving Party) shall first inform the other Party (the Disclosing Party) before making such disclosure of the same. In respect of certain information that either Party may reveal to another Party, another Party hereby agrees to keep such information confidential. The confidential obligation under this clause shall remain in force 3 years after the termination of this MoU.

==12. Intellectual Property==

All trademarks, service marks, logos or other words or symbols identifying each Party`s respective products and services and all goodwill arising therefrom (hereinafter referred to as “Marks”) and all other proprietary and intellectual property rights, including but not limited to patents, know-how, inventions, copyrights are and will remain, unless otherwise stipulated in a specific contract, the exclusive property of the owner thereof. Neither Party acquires under this MoU any license or other right or interest in the patents, copyrights, trade secrets, service marks, trademarks or other proprietary and/ or intellectual property rights of the other Party nor will it take any action that jeopardizes such rights. Any use by a Party of the other Party`s Marks will require the prior written approval of such other Party and must be in compliance with any instruction and guidelines respecting the Marks made available by such other Party.

==13. APPLICABLE LAW AND SETTLEMENT OF DISPUTES==

This MoU is governed by the laws of Belgium, excluding its conflict of law provisions.

All disputes arising out of or in connection with this MoU, which cannot be solved amicably, shall be finally settled under the Rules of Arbitration of the International Chamber of Commerce by three arbitrators appointed in accordance with the said Rules. The place of arbitration shall be Brussels if not otherwise agreed by the conflicting Parties and the language of the arbitration proceeding shall be English. The award of the arbitration will be final and binding upon the Parties.

RODENT network

2023-03-15T13:46:40Z

Grolleaue:

=Draft of Memorandum of Understanding Founding and Operation of European Drone Technology Network (RODENT )=

==1. MoU Preamble ==

The European Commission and ECSEL JU have funded the COMP4DRONES project (Grant-Agreement ID 826610) on drone technologies to ensure European strategic autonomy in such technologies. Drones underpin most of our future business and private activities, with a potentially significant socio-economic impact. Europe's potential in the field of UAVs, including its world-class research community, must be strengthened and exploited to be at the forefront of UAV development.

The entire network will be a common resource and will become a shared facility, like a virtual laboratory providing access to knowledge and expertise and attracting talent. It should become a reference, creating an easy entry point to drone technology in Europe and should contribute to its visibility.

The ECSEL JU COMP4DRONES project has made several connections with other European projects active in this field (ADACORSA, Drones4Safety, AW-Drones, RIMA, OPTICS2, GOF2.0, etc.) whose participating parties will be approached to sign also this MoU.

==2. MoU Scope ==

The Organization and Operation of the European Drone Technology Network (RODENT) aims to provide access to knowledge and expertise, functioning as an umbrella for the European drone industry's value network.

The purpose of this MoU is to establish certain principles that the Parties agree that it shall govern both the process of forming the RODENT and the operations of the future RODENT.

If the Parties choose to enter into any binding obligations other than those listed in this MoU below, any such binding obligations shall be set forth in a teaming agreement or other agreement (defined as the Definitive Agreement), if any, to be negotiated and executed by authorized representatives of each Party, in the sole, absolute discretion of each Party.

The Parties understand and agree that this MoU may, or may not, lead to a Definitive Agreement. Failure to consummate a Definitive Agreement based on the Parties’ intentions shall not entitle either Party to any remedies or damages under contract law, tort law, or any other legal or equitable theory. For the avoidance of doubt, neither Party is obliged to conclude Definitive Agreements.

This MoU is not intended to constitute, create, or give effect to or otherwise recognize a joint venture, partnership, teaming agreement or similar enforceable arrangement. Neither Party hereto has any right or authority to make or undertake any promise or to make any representation for the other Parties, or to execute any document or to otherwise assume any obligations or responsibility in the name of or on behalf of the other Party hereto.

==3. RODENT Objectives ==

The main objective of the RODEN networks is to promote, encourage and assist the coordinated development and deployment of UAV-based technologies and services in Europe. The following specific objectives are identified:
# Set up a virtual drone design platform promoting drone services based on European technologies.
# Mapping of European “supply” skills
# Increase cooperation between European Drone Industry
# Enable more R&D activities
# Build a competitive offer
# Expand accessibility to European drone technologies
# Increase the availability of drone technologies
# Improve the interoperability of components and tools
# Increase the qualification of engineers through training to acquire new practices

==4. RODENT Definitions ==
# Founding Members: Partners of the COMP4DRONES project signing this MoU at the first round.
# Full Members (acronym RODENT Members): organisations from European Union (EU) or Associated Countries that will be invited to and will sign this MoU. RODENT founding Members are RODENT full members.
# Associate Members: Organizations from countries other than EU member states or associated countries that will be invited to sign this MoU.
# Research & Industry Members: Research Institutions or Companies within EU countries or Associated with drone technologies activities that will be invited to and will sign this MoU.
# Representatives. Employees of any member type within EU countries or Associated having received a signed mandate to represent their organizations at RODENT level. A Representative may assign a Deputy Representative.

==5. RODENT Governance ==

# General Assembly (GA): It is the highest RODENT governing body consisting of one Representative of each Full Member.
# Management Board (MB): It consists of five Full Member Representatives and manages RODENT operations. The GA elects it for a four-year term. The number of MB members may be changed by GA decision, but cannot be less than three.
# Coordinator: It is a Full Member hosting RODENT Management operations. The GA elect it for a four-year term. MB member, which is the Representative of the Coordinator and chairs RODENT GA, MB and Research and Innovation Board.
# Research and Innovation Board: It consists of research and industry experts that advises RODENT on research and industrial innovation. All RODENT Member Representatives of any type elect expert for a four years term, or less.
RODENT GA or MB can decide to create (or dissolve) special committees to work on any RODENT Operation.

==6. RODENT Operations ==

===6.1 RODENT Management ===

It concerns the management, dissemination, accounting and reporting of RODENT activities and resources. The management rules and procedures will be decided by the RODENT GA or the RODENT BoD and should be compatible with the internal legislation, rules and procedures of the coordinator's country. The Coordinator, in accordance with the legislation, rules and internal procedures of his country, will mainly manage the project as a funded project.

===6.2 RODENT Activities ===

All RODENT members, regardless of type, are welcome to participate in RODENT activities on a win-win basis. Below is a non-exhaustive list, to be updated during RODENT operations, of activities to achieve RODENT's goals:
# Set up working groups to study the multiple issues (interoperability, business model, industrial intellectual property, etc.) that need to be resolved in order to create a virtual platform for drone design
# Offer of short courses, lecture series, web lectures etc. to promote technologies that can be used by the drone industry
# Industry, research or academic secondments.
# Offering Drone vision: Drones system engineering workshop and drone grand challenges.
# SoA overviews on drone topics.
# Drone event calendar.

== RODENT Dissemination/communication ==

They will be done mainly through the RODENT web portal, various lists and email channels that will be managed by the coordinator and various drone events.

== 8. RODENT Resources ==

RODENT resources come from its members of any kind, from its activities, from funded R&D projetcs or educational projects, but also from any other source, e.g., donations or sponsorships.

The activities mentioned in this MoU shall not, in principle, impose any financial obligations on the members of RODENT of any type. Each member, regardless of its type, shall bear the costs and expenses related to its participation in RODENT, unless otherwise specified and agreed/accepted by the member concerned.

Nothing contained in this MoU shall be construed as providing for the sharing of profits, losses, expenses, debts or liabilities arising out of the efforts of any of the Parties. All Parties agree to proceed at their own risk and expense and agree that each Party will be solely responsible for its own costs incurred in connection with its efforts under or related to this MoU, unless and until, if ever, other cost related responsibilities are set forth in a Definitive Agreement.

==9. RODENT International Cooperation ==

RODENT will seek active cooperation with any European, national and international entity engaged in Drones activities of any type, notably with any national Drones network within EU and with:
* KDT JU (https://www.kdt-ju.europa.eu/ )
* INSIDE Industry Association (https://www.inside-association.eu/ )
* SESAR 3 JU (https://www.sesarju.eu/ )
* EUROCONTROL (https://www.eurocontrol.int )
* EASA (https://www.easa.europa.eu )
* ENAC Laboratory (https://www.enac.fr/en )
* Drones Paris Region (https://systematic-paris-region.org/hubs-enjeux/hub-drones/ )
* Rozas (https://www.inta.es/CIAR/en/ )
* ADRA Association (https://adr-association.eu/ )
* Dronecode Foundation (https://www.dronecode.org/ )
* HiPEAC Network (https://www.hipeac.net/ )
* Aerial Connectivity Joint Activity – ACJA (https://www.gsma.com/iot/aerial-connectivity-joint-activity/ )

==10. RODENT Duration and Other Provisions ==

RODENT will start its activities as soon as at least five founding members from three European countries and participants in the ECSEL JU COMP4DRONES project (Grant-Agreement ID 826610) have signed this MoU. Potential members/associate members/research and industry members can adhere to this MoU by signing its copy, together with the coordinator. This MoU is valid for five years (2023-2027) and can be extended by decision of the RODENT General Assembly.

This MoU can only be changed by a written amendment agreed upon by the Parties and signed by persons authorised to bind the Parties.

Either Party may withdraw from this MoU at any time by providing written notification to the other Parties 30 days in advance.

Decisions of the RODENT General Assembly must be taken by a relative majority of the votes of all full members present. Decisions of the board of directors or any other board or committee of RODENT must be taken by unanimity, if possible, or by a relative majority in the second round, if the unanimous vote fails in the first round.

Any member of RODENT can refuse to execute a decision if it is contrary to the law of his country or to the internal rules governing its functioning.

RODENT may be dissolved by a decision of the GA of RODENT to take effect after a period of six months, so that any ongoing activity has been duly completed, in order to avoid any disadvantage to the members of RODENT.

RODENT members of any type are free to leave RODENT, after six months' notice and provided that any ongoing activity has been duly completed, in order to avoid any disadvantage to RODENT members.

In very exceptional cases of violation of the provisions of the RODENT Memorandum of Understanding, the GA of RODENT may decide to terminate the membership of a member of RODENT, regardless of its type, which will take effect after giving six months' notice to the member concerned.

==11. PERSONAL DATA PROTECTION AND CONFIDENTIALITY==

Personal data, as defined in Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data, will always be treated as Confidential Information, and will be protected with an adequate level of security and confidentiality, subject to any applicable legal, regulatory or contractual requirements.

All RODENT Members agree to comply with the EU Regulation 2016/679 (GDPR), as well as applicable national laws.

As the processing of personal data of individuals is necessary for the performance of this Agreement, all Members agree to enter into data processing agreements, which shall be attached to this MoU to constitute the entire Agreement and reflect the rights and obligations of each Party in this regard.

Unless otherwise agreed to in writing, the Parties hereto agree to keep all confidential information in this MoU and all related activities and documents strictly confidential unless the disclosure of such information by either Party is required under the law or order by any court of law, in which such Party (the Receiving Party) shall first inform the other Party (the Disclosing Party) before making such disclosure of the same. In respect of certain information that either Party may reveal to another Party, another Party hereby agrees to keep such information confidential. The confidential obligation under this clause shall remain in force 3 years after the termination of this MoU.

==12. Intellectual Property==

All trademarks, service marks, logos or other words or symbols identifying each Party`s respective products and services and all goodwill arising therefrom (hereinafter referred to as “Marks”) and all other proprietary and intellectual property rights, including but not limited to patents, know-how, inventions, copyrights are and will remain, unless otherwise stipulated in a specific contract, the exclusive property of the owner thereof. Neither Party acquires under this MoU any license or other right or interest in the patents, copyrights, trade secrets, service marks, trademarks or other proprietary and/ or intellectual property rights of the other Party nor will it take any action that jeopardizes such rights. Any use by a Party of the other Party`s Marks will require the prior written approval of such other Party and must be in compliance with any instruction and guidelines respecting the Marks made available by such other Party.

==13. APPLICABLE LAW AND SETTLEMENT OF DISPUTES==

This MoU is governed by the laws of Belgium, excluding its conflict of law provisions.

All disputes arising out of or in connection with this MoU, which cannot be solved amicably, shall be finally settled under the Rules of Arbitration of the International Chamber of Commerce by three arbitrators appointed in accordance with the said Rules. The place of arbitration shall be Brussels if not otherwise agreed by the conflicting Parties and the language of the arbitration proceeding shall be English. The award of the arbitration will be final and binding upon the Parties.

Main Page

2023-03-15T10:49:51Z

Grolleaue: /* Entry points */

==Welcome to the COMP4DRONES Wiki. ==

See [[About]] for a quick description, and to know more about COMP4DRONES please visit [https://www.comp4drones.eu/ comp4drones.eu].

== Entry points ==
* [[Component repository|Comp4Drones component repository]]
* [[WP6 Tools Table|Tools repository as a table]]
* [[RODENT network|RODENT Network agreement]]

RODENT network

2023-03-15T10:46:15Z

Grolleaue:

RODENT network

2023-03-15T10:44:30Z

Grolleaue:

Component repository

2023-03-12T21:07:37Z

Grolleaue:

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication establishment
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing

|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing

|-
|[[WP4-07]]
|ROT
|Run-Time Safety Checker

|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18]]
|TEKNE
|Transponder for drone-rover cooperation

|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components

|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain

|-
|[[WP5-08]]
|ROT
|Lightweight Cryptography
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05|WP5-05-TEK]]
|TEKNE
|LPWAN for identification, tracking, and emergency messages
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-01]]
|AIT
|Workflow
|-
|[[WP6-02]]
|AIT
|ThreatGet – Post- / Precondition
|-
|[[WP6-03]]
|AIT
|MoMuT Protocol Testing
|-
|[[WP6-09]]
|UWB
|DronePort Simulation Extensions for Gazebo
|-
|[[WP6-11]]
|Siemens
|Simcenter Amesim
|-
|[[WP6-12]]
|ENSMA
|MOSART, retro-engineering and analysis framework
|-
|[[WP6-13]]
|UNIMORE
|OODK
|-
|[[WP6-15]]
|UNISS
|MDC
|-
|[[WP6-16]]
|UNISS
|SAGE
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated SYstems (HEPSYCODE)
|-
|[[WP6-20]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-21]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-22]]
|IKERLAN
|SelfTestTool
|-
|[[WP6-23]]
|IKERLAN
|AsyncCommsTool
|-
|[[WP6-P4R|WP6-24]]
|CEA
|Model driven engineering
|-
|[[WP6-25]]
|UNICAN
|S3D - Model-Driven Analysis and Design Framework
|-
|[[WP6-26]]
|UNICAN
|SoSIM - System-of-Systems Simulation & Performance Analysis
|-
|[[WP3-26|WP6-27]]
|SM
|DronePort design tool
|-
|[[WP6-30]]
|ALTRAN
|e-Handbook
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

WP5-05

2023-03-12T21:06:29Z

2023-03-12T20:58:20Z

Grolleaue: Created page with "=Transponder for drone-rover cooperation= {|class="wikitable" | ID|| WP4-18 |- | Contributor || TEKNE |- | Levels || System functions — Coordination — Drone and Rover |- | Require || UWB transceivers |- | Provide || Guidance for the drone positioning with respect to the landing pad. |- | Input | * Autopilot GPS and intertial navigation data * Distances measured using the UWB system |- | Output || Guidance commands |- | Input Interface || PX4, s..."

=Transponder for drone-rover cooperation=
{|class="wikitable"
| ID|| WP4-18
|-
| Contributor || TEKNE
|-
| Levels || System functions — Coordination — Drone and Rover
|-
| Require || UWB transceivers
|-
| Provide || Guidance for the drone positioning with respect to the landing pad.
|-
| Input
|
* Autopilot GPS and intertial navigation data
* Distances measured using the UWB system
|-
| Output || Guidance commands
|-
| Input Interface || PX4, serial link
|-
| Output Interface || PX4, serial link
|-
| TRL || 5
|-
| Tasks || T4.1, T4.2
|-
| Use Case || UC5 - Agriculture
|-
| Demonstrator || D1 - Crop monitoring
|-
| Contact || c.tiere@tekne.it
|}

=Description=

The WP4-18 component estimates the still UGV (Unmanned Ground Vehicle) position with respect to the UAV on the basis of the autopilot navigation data and of the distance between the two vehicles. The distance is computed from the measurements of Time of Flight (ToF — time of electromagnetic propagation) measured by the UWB transceivers which both vehicles are equipped with. The WP4-18 component drives the UAV towards a certain target position that is given relatively to the UGV (on the vertical, at a certain height). To land on the UGV, the UAV moves by navigating on the basis of GPS data. At the end of this approaching manoeuvre, due to the limited GPS accuracy, it may happen that the UGV (the landing pad) is not in the field of view of the UAV dedicated video camera that controls the landing. The WP4-18 component, which doesn’t require optical visibility, executes the positioning manoeuvre to bring the UAV to a position such that the autonomous landing manoeuvre can start.

=Usage Example=
The WP4-18 component can be used for autonomous UAV landing on the UGV during missions that the vehicles carry out cooperatively. When the two vehicles are far from each other and from the Ground Control Station WP5-05-TEK “LPWAN for identification, tracking, and emergency messages” component (work package WP5) can provide long-range communication for monitoring the positions
and for commanding the UAV to execute the manoeuvre (approaching + positioning + landing).

[[File:wp4-18-01.jpg|frame|center]]

=Improvements=

While the autonomous landing of a UAV on a UGV is a mature technique, the approaching manoeuvre, which brings the UGV in the field of view of the UAV landing camera, depends on the availability and the quality of GPS signals. The WP4-18 component solves this issue by using UWB distance measurement sensors for positioning the UAV with respect to the UGV.

Component repository

2023-03-12T20:51:48Z

Grolleaue:

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication establishment
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing

|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing

|-
|[[WP4-07]]
|ROT
|Run-Time Safety Checker

|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18]]
|TEKNE
|Transponder for drone-rover cooperation

|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components

|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain

|-
|[[WP5-08]]
|ROT
|Lightweight Cryptography
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05]]
|TEKNE
|LPWAN for identification, tracking, and emergency messages
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-01]]
|AIT
|Workflow
|-
|[[WP6-02]]
|AIT
|ThreatGet – Post- / Precondition
|-
|[[WP6-03]]
|AIT
|MoMuT Protocol Testing
|-
|[[WP6-09]]
|UWB
|DronePort Simulation Extensions for Gazebo
|-
|[[WP6-11]]
|Siemens
|Simcenter Amesim
|-
|[[WP6-12]]
|ENSMA
|MOSART, retro-engineering and analysis framework
|-
|[[WP6-13]]
|UNIMORE
|OODK
|-
|[[WP6-15]]
|UNISS
|MDC
|-
|[[WP6-16]]
|UNISS
|SAGE
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated SYstems (HEPSYCODE)
|-
|[[WP6-20]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-21]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-22]]
|IKERLAN
|SelfTestTool
|-
|[[WP6-23]]
|IKERLAN
|AsyncCommsTool
|-
|[[WP6-P4R|WP6-24]]
|CEA
|Model driven engineering
|-
|[[WP6-25]]
|UNICAN
|S3D - Model-Driven Analysis and Design Framework
|-
|[[WP6-26]]
|UNICAN
|SoSIM - System-of-Systems Simulation & Performance Analysis
|-
|[[WP3-26|WP6-27]]
|SM
|DronePort design tool
|-
|[[WP6-30]]
|ALTRAN
|e-Handbook
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

Component repository

2023-03-12T20:50:16Z

Grolleaue:

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication establishment
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing

|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing

|-
|[[WP4-07]]
|ROT
|Run-Time Safety Checker

|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder

|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components

|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain

|-
|[[WP5-08]]
|ROT
|Lightweight Cryptography
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-01]]
|AIT
|Workflow
|-
|[[WP6-02]]
|AIT
|ThreatGet – Post- / Precondition
|-
|[[WP6-03]]
|AIT
|MoMuT Protocol Testing
|-
|[[WP6-09]]
|UWB
|DronePort Simulation Extensions for Gazebo
|-
|[[WP6-11]]
|Siemens
|Simcenter Amesim
|-
|[[WP6-12]]
|ENSMA
|MOSART, retro-engineering and analysis framework
|-
|[[WP6-13]]
|UNIMORE
|OODK
|-
|[[WP6-15]]
|UNISS
|MDC
|-
|[[WP6-16]]
|UNISS
|SAGE
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated SYstems (HEPSYCODE)
|-
|[[WP6-20]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-21]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-22]]
|IKERLAN
|SelfTestTool
|-
|[[WP6-23]]
|IKERLAN
|AsyncCommsTool
|-
|[[WP6-P4R|WP6-24]]
|CEA
|Model driven engineering
|-
|[[WP6-25]]
|UNICAN
|S3D - Model-Driven Analysis and Design Framework
|-
|[[WP6-26]]
|UNICAN
|SoSIM - System-of-Systems Simulation & Performance Analysis
|-
|[[WP3-26|WP6-27]]
|SM
|DronePort design tool
|-
|[[WP6-30]]
|ALTRAN
|e-Handbook
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

File:Wp3-37-2.jpg

2023-03-10T17:13:39Z

Grolleaue:

2023-03-10T14:16:07Z

Grolleaue:

== Introduction ==
{|class="wikitable"
| ID|| WP6-12
|-
| Contributor || ENSMA
|-
| Levels || Tool
|-
| Require || Capella with AADL-like point of view plugin
|-
| Provide || Retro-engineering of Paparazzi C/C++ code into a Capella point of view, offset adjustment to avoid interferences in telemetry messages or in the kernel
|-
| Input || C/C++ code and Makefile of Paparazzi UAV
|-
| Output || Model for Capella AADL-like point of view, offsets computed by GCD+ offset choosing method
|-
| C4D tooling || System-Level modelling and analysis
|-
| TRL || 3
|-
| Contact || grolleau at ensma.fr
|}

==Retro engineering from autopilot source code to model==

Our toolchain allows the retro-engineering of an autopilot programmed in C/C++, to obtain a AADL-like model, an extension of AADL semantics following COMP4DRONES implementation. The AADL-like model is expressed in a Capella Point of View, allowing the end-user to obtain a graphical representation of threads, functions seen as a dataflow graph, software buses and shared global variable access. The flow is represented in the following figure.

[[File:wp6-12_01.jpg|frame|center|Autopilot retro-engineering workflow]]

Our framework is based on ''ANTLR'' and it is composed of a parsing engine, which is the program that is responsible for the traversal and the transformation of the parse tree.
The processing consists of three layers. From top to bottom, the program that performs the tree traversal and its text-to-text transformation layer. This program is built on top of the two other layers, which are provided by ''ANTLR'', namely the built parse tree as well as the generated bricks (lexer, parser, tokens, and the listeners).

Building the parse tree consists in parsing the GIMPLE code (e.g., Paparazzi GIMPLE files) that is conforming to the GIMPLE grammar and requires the three given components of the first layer, namely the Parser, the Lexer, and the Tokens. Once the parse tree is built, it is then transformed into XML code. This process requires the generated listeners of the first layer.

This toolchain has been tested on instances of Paparazzi UAV autopilots, and still requires some rare (compared to the hundreds of source code files) manual addition.

==AADL-like point of view in Capella==

We developed this point of view in order to visualize tasks and their interactions with an AADL graphical syntax. Note that there are additional semantics related to COMP4DRONES D3.3 definitions, in order to be able to represent the core elements of an autopilot. Its tool palette is represented on the right hand side.

[[file:wp6-12-3.png|thumb|Tool palette of the AADL-like Capella point of view]]

The following figure shows an excerpt of an AADL-like representation of an autopilot.

[[File:wp6-12-02.svg|frameless|upright=4.0|Excerpt of an AADL-like representation of an autopilot]]

The figure represents two parts of the viewpoint: on the left-hand side, we can see all the threads of a ChibiOS based Paparazzi autopilot: the ones marked (1) are four threads in charge of UART, (2) is a shell thread, (3) is a log thread, and (4) is the main autopilot thread. On the right-hand side, (5) is an excerpt of the functions present in the main autopilot thread. These are functions called to check if the UAV lost communication with the ground station or is too high compared to the allowed altitude, and in both cases, will change the actual mode of the autopilot. This representation is giving a global view of Paparazzi implementation on the Ulysse rotorcraft platform, which is requiring the compilation of 161 C and C++ files. At the very bottom of the left-hand side, we can see green bent up and down arrows for every access (read or write) to a software bus (global variables or middleware). Several properties are accessible from the environment for each represented element, but in this mode we directly displayed the LOC (Lines of Code) field to quickly indicate to the developer which functions may be computationally intensive, and require some WCET computation.

==Experimentation==
It was successfully used on Paparazzi UAV where our offset assignment heuristic, called GCD+, was used to avoid critical instants within custom modules added to the core of Paparazzi UAV.

== References ==
[1] Kamni, S., Ouhammou, Y., Grolleau, E., Bertout, A., & Hattenberger, G. (2022, November). A Reverse Design Framework for Modifiable-off-the-Shelf Embedded Systems: Application to Open-Source Autopilots. In Model and Data Engineering: 11th International Conference, MEDI 2022, Cairo, Egypt, November 21–24, 2022, Proceedings (pp. 133-146). Cham: Springer Nature Switzerland.

[2] Ladeira, M., Grolleau, E., Bonneval, F., Hattenberger, G., Ouhammou, Y., & Hérouard, Y. (2022, July). Scheduling offset-free systems under fifo priority protocol. In 34th Euromicro Conference on Real-Time Systems (ECRTS 2022) (Vol. 231).

[3] Hattenberger, G., Bonneval, F., Ladeira, M., Grolleau, E., & Ouhammou, Y. (2022, September). Micro-drone autopilot architecture for efficient static scheduling. In 13th International Micro Air Vehicle Conference (pp. 175-182).

WP6-12

2023-03-10T14:14:08Z

Grolleaue: /* Experimentation */

WP6-12

2023-03-10T14:12:02Z

Grolleaue:

2023-03-10T14:01:09Z

Grolleaue:

== Introduction ==
{|class="wikitable"
| ID|| WP6-12
|-
| Contributor || ENSMA
|-
| Levels || Tool
|-
| Require || Capella with AADL-like point of view plugin
|-
| Provide || Retro-engineering of Paparazzi C/C++ code into a Capella point of view, offset adjustment to avoid interferences in telemetry messages or in the kernel
|-
| Input || C/C++ code and Makefile of Paparazzi UAV
|-
| Output || Model for Capella AADL-like point of view, offsets computed by GCD+ offset choosing method
|-
| C4D tooling || System-Level modelling and analysis
|-
| TRL || 3
|-
| Contact || grolleau at ensma.fr
|}

==Retro engineering from autopilot source code to model==

Our toolchain allows the retro-engineering of an autopilot programmed in C/C++, to obtain a AADL-like model, an extension of AADL semantics following COMP4DRONES implementation. The AADL-like model is expressed in a Capella Point of View, allowing the end-user to obtain a graphical representation of threads, functions seen as a dataflow graph, software buses and shared global variable access. The flow is represented in the following figure.

[[File:wp6-12_01.jpg|frame|center|Autopilot retro-engineering workflow]]

Our framework is based on ''ANTLR'' and it is composed of a parsing engine, which is the program that is responsible for the traversal and the transformation of the parse tree.
The processing consists of three layers. From top to bottom, the program that performs the tree traversal and its text-to-text transformation layer. This program is built on top of the two other layers, which are provided by ''ANTLR'', namely the built parse tree as well as the generated bricks (lexer, parser, tokens, and the listeners).

Building the parse tree consists in parsing the GIMPLE code (e.g., Paparazzi GIMPLE files) that is conforming to the GIMPLE grammar and requires the three given components of the first layer, namely the Parser, the Lexer, and the Tokens. Once the parse tree is built, it is then transformed into XML code. This process requires the generated listeners of the first layer.

This toolchain has been tested on instances of Paparazzi UAV autopilots, and still requires some rare (compared to the hundreds of source code files) manual addition.

==AADL-like point of view in Capella==

We developed this point of view in order to visualize tasks and their interactions with an AADL graphical syntax. Note that there are additional semantics related to COMP4DRONES D3.3 definitions, in order to be able to represent the core elements of an autopiot.

The following figure shows an excerpt of an AADL-like representation of an autopilot.

[[File:wp6-12_02.svg|frame|center|Excerpt of an AADL-like representation of an autopilot]]

The figure represents two parts of the viewpoint: on the left-hand side, we can see all the threads of a ChibiOS based Paparazzi autopilot: the ones marked (1) are four threads in charge of UART, (2) is a shell thread, (3) is a log thread, and (4) is the main autopilot thread. On the right-hand side, (5) is an excerpt of the functions present in the main autopilot thread. These are functions called to check if the UAV lost communication with the ground station or is too high compared to the allowed altitude, and in both cases, will change the actual mode of the autopilot. This representation is giving a global view of Paparazzi implementation on the Ulysse rotorcraft platform, which is requiring the compilation of 161 C and C++ files. At the very bottom of the left-hand side, we can see green bent up and down arrows for every access (read or write) to a software bus (global variables or middleware). Several properties are accessible from the environment for each represented element, but in this mode we directly displayed the LOC (Lines of Code) field to quickly indicate to the developer which functions may be computationally intensive, and require some WCET computation.