DTOceanPlus D2.1 Results from user-groups consultation

The DTOceanPlus project will develop and demonstrate an open-source integrated suite of 2nd generation design tools for ocean energy technologies. The tools will support the entire technology innovation and advancement process from concept, through development, to deployment, and will be applicable at a range of levels: sub-system, device, and array. This report presents findings from a consultation of potential users and other stakeholders for the DTOceanPlus tools, to identify and clarify their needs and requirements. Opinions from over 70 industry professionals from a wide range of backgrounds were collated and analysed. These will be used to inform the functional requirements for the development of the DTOceanPlus tools and software. Further work is required during the DTOceanPlus project to explain the functionality and use of the proposed tools, particularly focusing on the Structured Innovation concept as this is less well understood. Additional clarification of the tool’s scope would also be beneficial, in terms of stages of the development lifecycle covered, how this links with TRL, and to different points during a project. Of the overall software characteristics considered, usability followed by flexibility & expandability then modularity were seen as most important. Additionally, transparency of how the tools work is critical, including documentation referenced to background research, and some form of version control or parameter tracking. A high-quality software product is expected of DTOceanPlus, something not all people consider DTOcean delivered. The proposed tools will need to deal with varying degrees of complexity, both at different stages in the project lifecycle and also for different user requirements. How this will be dealt with was a concern for some. A suggestion was to have ‘high-level’ and ‘technical’ tools (or ‘simple’ and ‘expert’ modes), exposing more detail in the latter for those who have data and time available to do more analysis. Several responses stressed the importance of linkages between the tools, and with external software. One technology developer suggested having an API to allow external software and scripts two-way access to the DTOceanPlus tools and data, allowing flexibility to use either DTOceanPlus or another tool as deemed most appropriate. Nearly all respondents (>85%) indicated that they were likely or very likely to use DTOceanPlus at some stage in the project lifecycle. Similarly, most (>80%) responded that they understood or somewhat understood conceptually what all the DTOceanPlus tools would do.