Deliverables

The deliverable provides a first version of the RAWFIE user and system requirements that will form the basis for the definition of the Platform and Testbeds architecture and detailed design. In keeping with the overall project workflow, the requirements captured and synthesized here will be given to WP4 – Platform Design as input for the first development cycle. Within the deliverable, a number of use cases are presented. A use case is in most cases a real world scenario that aims to serve as source for identifying user specific requirements, capabilities and corresponding experiments that need to be supported by the RAWFIE Platform.

The requirements identified in this first iteration are divided in 2 broad categories (a) Platform and (b) Testbed (including UxV resource specific) requirements and are also prioritized base on their significance.

The document also includes a section related to constraints and limitations pertaining to UxV systems and the testbed areas based on facility providers’ feedback.

This deliverable comprises the 2nd version of the RAWFIE Components requirements. Based on the grounds of the 1st version and by utilizing information regarding the architecture and detailed design elaborated during the 1st iteration of the project it attempts to refine the list of requirements defined in the previous version of the Requirements document.

The initial version of the Requirements Analysis provided a coarse-grained outline of the overall system, the envisaged components and the expected user and system high-level requirements by defining two broad categories. In the present version, a more elaborated requirement analysis look is attempted. Requirements are classified following the RAWFIE component breakdown structure prescribed by the RAWFIE Architecture related documents compiled during the 1st iteration cycle. The methodology used is still based on the VOLERE like card template agreed in the 1st version.

In keeping with the overall project workflow, the requirements captured and synthesized here will be provided as input to WP4 – Platform Design for the 2nd development cycle.

The use cases defined in the 1st version of the Requirements document remain valid while some additional ones have been added.

A traceability matrix is also provided between the requirements defined during the 1st and the 2nd version of the Requirement analysis

This deliverable comprises the 3nd version of the RAWFIE Components requirements. Based on the grounds of the 2nd version and by utilizing information regarding the architecture and detailed design elaborated during the 2nd iteration of the project it attempts to refine the list of requirements defined in the previous version of the Requirements document and identify any missing ones.

Version 2 of the Requirements Analysis elaborated and classified requirements following the RAWFIE component breakdown structure prescribed by the RAWFIE Architecture. Therefore, requirements were defined on a more detailed level (system & detailed level) compared to version 1. The methodology used was based on the VOLERE like card template agreed in the 1st version. A similar approach is used and in the present document starting from the point that D3.2 concluded.

In keeping with the overall project workflow, the requirements captured and synthesized here will be provided as input to WP4 – Platform Design for the 3nd development cycle.

While the use cases/scenarios defined in the previous versions of the Requirements document remain valid the present version attempts to go one step further and identify a list of features that could be available to platform oncoming experimenters.

A traceability matrix is also provided allowing the user to track and navigate between the requirements defined in each iteration.

 

This deliverable describes the first version of the RAWFIE high lever architecture. An overview of all components and there interaction is given. Also a state of the art summary of technologies that may be used to implement the architecture is given.

This deliverable presents the design documentation of RAWFIE subsystem and belonging components. It contains the architectural definition and specification of the components as well as the different interactions and responsibilities among them, highlighting their interfaces and communication flow.

This deliverable is based on the results of T4.1 for what concerns the definition of the testing and validation scenarios of the RAWFIE platform. It contains the definition of a set of test and validation scenarios that will be performed in WP6 as well as the definition of the metrics and the success criteria.

This deliverable describes the second version of the RAWFIE high-level architecture. An overview of all components and their interaction is given. Several changes were made on the architecture to reflect the latest developments and also improvements as a result of several internal discussions.

As a result of the progresses on tasks T4.2, T4.3 and T4.4, a new version of the Design and Specification of RAWFIE Components deliverable, for the 2nd technical iteration cycle, is released.

Built on the updated list of architectural components and technological decisions presented in the D4.4, on the first components’ prototype, and especially on the updated requirements’ definition of D3.2, this report presents the updated design documentation of RAWFIE Architectural tiers, and belonging components. It moves from the conceptual perspective of the system design in the 1st iteration, to development and operational perspectives, by providing more details regarding the way the components are, or will be, implemented and deployed.

This deliverable is based on the results of T4.1 for what concerns the definition of the testing and validation scenarios of the RAWFIE platform. It contains the definition of a set of test and validation scenarios that will be performed in WP6 as well as the definition of the metrics and the success criteria.

This deliverable describes the third version of the RAWFIE high-level architecture. An overview of all components and their interaction is given.
Several changes were made on the architecture to reflect the latest design choices and improvements brought during the third design round .
This is the last deliverable of the RAWFIE High Level architecture documents’ series. Further changes on high level architectural elements, if any, will be reported in the last deliverable of the RAWFIE components’ design and specification documents’ series, D4.8.

As a result of the progresses on tasks T4.2, T4.3 and T4.4, the final version of the Design and Specification of RAWFIE Components deliverable, for the 3rd technical iteration cycle, is released. Built on the final updated list of architectural components and technological decisions presented in the D4.7, on the 2nd iteration of components’ implementation and on the updated requirements’ definition of D3.3, this report presents the final modifications to the design, and the interfaces specifications of RAWFIE platform and components.

This deliverable describes the definition of the testing and validation scenarios of the RAWFIE platform. It defines the test and validation plan as a set of scenarios that are performed in WP6 as well as the definition of the metrics and the success criteria.

The objective of this deliverable is to report about the interface tests, the verification tests and to present the integration results and all the technicalities required for the consolidation of the several components (software and hardware) of the RAWFIE architecture in a unified platform. Enhancements of the RAWFIE operational platform based on the outcomes of the testing procedures are also listed in this deliverable. The document is released as a live document in three phases/cycles according to the roadmap.

This deliverable is based on the results of the following tasks: T6.1 and T6.2 on the basis of the work done in WP5, and on the verification tests planning presented in D4.3.

The objective of this deliverable is a report on the validation of the RAWFIE platform. It describes the validation and evaluation procedures and their outcomes.

The document will be released as a live document in three phases/cycles according to the roadmap.

This deliverable is based on the validation plan setup in D4.3 and on the results of tasks T6.1 and T6.2.

The objective of this deliverable is to report about the integration and testing of the RAWFIE system. It presents the status of the interface tests and the verification tests as well as of the integration results. It mentions the technicalities required for the consolidation of the RAWFIE components in a unified platform. The results obtained during the experimentations and the specific tests are analysed to identify and characterise the improvements and fixes to be brought to the prototype implementation during the third development iteration. The integration roadmap lists the enhancements of the RAWFIE operational platform based on the outcomes of the testing procedures and the deployments on the operational sites. The document is the second release over the three phases/cycles defined in the RAWFIE project.
This deliverable is based on the results of the tasks T6.1 and T6.2, on the work done in WP5, and on the verification tests planning presented in D4.6.

The objective of this deliverable is to report the results of the second validation run of the RAWFIE platform. It describes the validation and evaluation procedures and their outcomes of the second implementation phase.
The document is released as a live document in three phases/cycles according to the roadmap (2 of 3).
This deliverable is based on the validation plan setup in D4.6, the requirements found in D3.2 and on the results of tasks T6.1 and T6.2.

The objective of this deliverable is to report about the integration and testing of the RAWFIE system at the end of the third and last development cycle. It presents the status of the interface tests and the verification tests as well as of the integration results.  The document is the third release over the three phases/cycles defined in the RAWFIE project. The tests reported in this document were executed during the current iteration if they were not successful at the previous one or if they were newly defined in D4.9.   This deliverable is based on the results of the tasks T6.1 and T6.2, on the work done in WP5, and on the verification tests planning presented in D4.9.

The objective of this deliverable is to report the results of the third validation run of the RAWFIE platform. It describes the validation and evaluation procedures and their outcomes of the third implementation phase.The document is released as a live document in three phases/cycles according to the roadmap (3 of 3).
This deliverable is based on the validation plan setup in D4.9, the requirements found in D3.3 and on the results of tasks T6.1 and T6.2.

This report contains the initial results on establishing the RAWFIE community and the strategy to further expand it to the target members, including experimenters, testbed operators, UxV manufacturers and suppliers, research institutes, universities, and other interested parties. In the elapsed 15 months from the beginning of the project, the RAWFIE Consortium has actively pursued various means to raise awareness, inform the target audience to follow the development of the platform, create interest in joining the RAWFIE community, and to inform the broader audience of the first Open Call.

In this deliverable, it appears that interested parties (testbed operators and experimenters) are aware on the various details of the functionalities of the existing systems that have been delivered from the the 1st Open Call. Furthermore, users involved are familiar to Unmanned Vehicles (UxV, where ‘x’ represents “A” for aerial or “S” for sea-surface or “G” for grounds ), as well as the platform’s functionalities, the relevant configuration options and the experiment lifecycle in general.

The present document describes the training events and the efforts undertaken by operators and experimenters on the RAWFIE platform into the testbed, so that the requested experiments can be successfully defined, executed and validated.

The deliverable provides a first version of the data management plan that will be adopted by the RAWFIE project. The plan which follow the Horizon 2020 Work Program 2014-15 directives for Data Management Plan (DMP). The purpose of this deliverable is to support the data management life cycle for all data that will be collected, processed or generated by the project. It will provide an outline of the data types the project will generate, whether and how it will be exploited or made accessible for verification and re-use, and how it will be curated and preserved.

The deliverable provides the second version of the data management plan that RAWFIE project adopts. The plan follows the Horizon 2020 Work Program 2014-15 directives for Data Management Plan (DMP). The purpose of this deliverable is to provide updates to the data management life cycle of the project. The deliverable provides an outline of the data types the project generates, whether and how it exploits or makes them accessible for verification and re-use, and how it will curate and preserve them.

This deliverable is a report of the 1st Open Call of RAWFIE. It presents the open call launch, as well as the submission and selection process of the open call proposals. It also provides a summary of the accepted proposals with respect to this open call.

This deliverable is the final report of the 1st Open Call of RAWFIE. It presents the launch of the projects corresponding to the open call successful proposals, the project management process and the current status. It also presents the workshop that took place for the 1st open call projects.

This deliverable is a report of the 2nd Open Call of RAWFIE. It presents the open call launch, as well as the submission and selection process of the open call proposals. It also provides a summary of the accepted proposals with respect to this open call.

This deliverable is the final report of the 2nd Open Call of RAWFIE. It presents the launch of the projects corresponding to the open call successful proposals, the project management process and the current status. It also presents the meeting that took place for the 2nd Open Call projects

This deliverable is a report of the 3rd Open Call of RAWFIE. It presents the open call launch, as well as the submission and selection process of the open call proposals. It also provides a summary of the accepted proposals with respect to this open call.