Deliverable D5.2 “Site Characterisation – alpha version” of the DTOceanPlus project include the details of the Deployment Tool module: “Site Characterisation” (SC), and it represents the result of the work developed during the task 5.3 of the project. This document summarises both the functionalities as well as the more technical aspects of the code implemented for this module.

This report is the outcome of a task dedicated to specific sector standards for business management models for the ocean energy sector. The aim of this task was to define alternative business models for the sector by developing a greater understanding of these models and recommending development routes to industrial roll-out to improving the market opportunity.

This document is the third annual report on dissemination and communication activities regarding DTOceanPlus project.

A coherent set of functional and technical requirements have been developed for the DTOceanPlus suite of design tools based on analysis of gaps between the current state-of-the-art tools, learning from the original DTOcean project, and the stakeholder expectations identified in the user consultation survey. The technical requirements in this document are translated from the general requirements for the overall suite of tools, and specific requirements (functional, operational, user, interfacing, and data) for the Deployment design tool that will be developed as part of this project.

Deliverable D4.2 “Stage Gate Tools – alpha version” of the DTOceanPlus project includes the details of the Stage Gate Design Tool, and it represents the result of the work developed during task T4.2 of the project. This tool is an application of a stage gate process which is used in research and industry to provide structure to the technology development process. This approach supports the R&D pathway towards producing reliable and cost-effective ocean energy sub-systems, devices and arrays.

This document is the second annual report on dissemination and communication activities regarding DTOceanPlus project.

A coherent set of functional and technical requirements have been developed for the DTOceanPlus suite of design tools based on analysis of gaps between the current state-of-the-art tools, learning from the original DTOcean project, and the stakeholder expectations identified in the user consultation survey. The technical requirements in this document are translated from the general requirements for the overall suite of tools, and specific requirements (functional, operational, user, interfacing, and data) for the Structured Innovation design tool that has been developed as part of this project. These requirements relate to detailed technical requirements of the technology and environment, for the development, maintenance, support and execution of the software specifications to best meet the needs of the ocean energy industry.

This document presents the first step in achieving DTOceanPlus project website’s launching.

This document aimed at developing a comprehensive communication plan developed at the beginning of the project in accordance with the overall project management. This plan was an evolving document built on a targeted communication of the DTOceanPluq project results and capitalization on the community. It is the reference framework for evaluating the impact of communication and dissemination activities.

This report describes the methodology used to define the “validation scenarios”, accounting for the different potential use cases. Given the large number of permutations of tools, use cases, and the set of minimum validation requirements, the number of validation scenarios has been reduced to a number that can be run during the life of the DTOceanPlus project but that are sufficient to fully demonstrate the functionality of the DTOceanPlus suite of tools. The selection process, based on a successive approximation approach, has led to the cases that the potential users in the DTOceanPlus consortium have considered as the most relevant for the sector. In Section 4 of the document, the selected validation scenarios is described; the definition of these scenarios has been completed during the project to ensure that the most updated information is used.