DOCSLIB.ORG

Characteristics of Iiot Information Models

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Characteristics of Iiot Information Models Characteristics of IIoT Information Models An Industrial Internet Consortium White Paper Takuki Kamiya (Fujitsu), Andrei Kolesnikov (IOT Association), Brett Murphy (RTI), Kym Watson (Fraunhofer IOSB), Niklas Widell (Ericsson) Characteristics of IIoT Information Models Contents TABLE OF CONTENTS Part I: Core 1 Introduction ...................................................................................................................... 1 2 Meta-Model for Characterizing IIoT Information Models ................................................... 2 2.1 Services Needed from Connectivity Framework Layer ........................................................... 2 2.1.1 Data format ......................................................................................................................... 2 2.1.2 Interaction abstraction ........................................................................................................ 3 2.2 Levels of Abstraction in Information Models ........................................................................ 4 2.3 IIoT System Information Model Types .................................................................................. 6 2.3.1 Position in system life cycle ................................................................................................. 6 2.3.2 Position in (Architecture Layer, System Layer, Hierarchy Level):........................................ 6 2.4 Core Characteristics ............................................................................................................. 7 2.4.1 Ontology .............................................................................................................................. 7 2.4.2 Contextual data ................................................................................................................... 8 2.4.3 Metamodel .......................................................................................................................... 9 2.4.4 Observation & Measurement ............................................................................................ 11 2.4.5 Actuators and Tasking ....................................................................................................... 12 2.4.6 Security .............................................................................................................................. 13 2.4.6.1 Authorization and Access Control ........................................................................... 13 2.4.6.2 Authentication ........................................................................................................ 14 2.4.6.3 Confidentiality/Privacy ............................................................................................ 17 3 Overview of Examples of Information Models ................................................................. 18 3.1 Related work ..................................................................................................................... 20 Part II: Annexes Annex A WoT (Web of Things) Information Model ....................................................... 21 A.1 Background information .................................................................................................... 21 A.2 Services Needed from Connectivity Framework Layer ......................................................... 21 A.2.1 Data Format ....................................................................................................................... 21 A.2.2 Interaction Abstraction...................................................................................................... 21 A.2.2.1 Services.................................................................................................................... 21 A.2.2.2 Quality of service..................................................................................................... 22 A.2.2.3 Design Patterns ....................................................................................................... 22 A.2.2.4 Protocols ................................................................................................................. 22 A.3 Core Characteristics ........................................................................................................... 23 A.3.1 Ontology ............................................................................................................................ 23 A.3.2 Contextual Data ................................................................................................................. 24 A.3.3 Metamodel ........................................................................................................................ 24 A.3.4 Observation & Measurement ............................................................................................ 25 A.3.4.1 Time ......................................................................................................................... 25 A.3.4.2 Location ................................................................................................................... 25 - ii - Characteristics of IIoT Information Models A.3.4.3 Sensors .................................................................................................................... 25 A.3.4.4 Data Format ............................................................................................................ 25 A.3.5 Actuators and tasking ........................................................................................................ 26 A.3.5.1 Actuators ................................................................................................................. 26 A.3.5.2 Tasking..................................................................................................................... 26 A.3.6 Security .............................................................................................................................. 26 A.3.6.1 Authorization .......................................................................................................... 26 A.3.6.2 Authentication ........................................................................................................ 26 A.3.6.3 Confidentiality ......................................................................................................... 27 A.4 IIoT System Information Models ........................................................................................ 27 A.4.1 Position in System Life Cycle ............................................................................................. 27 A.4.2 Position in (Architecture Layer, System Layer, Hierarchy Level):...................................... 27 Annex B OPEN GEOSPATIAL CONSORTIUM SENSORTHINGS API INFORMATION MODEL 27 B.1 Background Information .................................................................................................... 27 B.2 Services Needed from Connectivity Framework Layer ......................................................... 28 B.2.1 Data Format ....................................................................................................................... 28 B.2.2 Interaction Abstraction...................................................................................................... 28 B.2.2.1 Services.................................................................................................................... 28 B.2.2.2 Quality of service..................................................................................................... 28 B.2.2.3 Design Patterns ....................................................................................................... 28 B.2.2.4 Protocols ................................................................................................................. 28 B.3 Core Characteristics ........................................................................................................... 28 B.3.1 Ontology ............................................................................................................................ 28 B.3.2 Contextual Data ................................................................................................................. 31 B.3.3 Metamodel ........................................................................................................................ 32 B.3.4 Observation & Measurement ............................................................................................ 32 B.3.4.1 Annex A Section 1, Subsection 3, Sub-SubSection 2 ............................................... 32 B.3.4.2 Time ......................................................................................................................... 32 B.3.4.3 Location ................................................................................................................... 32 B.3.4.4 Sensors .................................................................................................................... 32 B.3.4.5 Data Format ............................................................................................................ 32 B.3.5 Actuators and tasking ........................................................................................................ 32 B.3.5.1 Actuators ................................................................................................................. 32 B.3.5.2 Tasking....................................................................................................................
Load more

Recommended publications
  • Iot4cps Deliverable
    IoT4CPS – Trustworthy IoT for CPS FFG - ICT of the Future Project No. 863129 Deliverable D5.1 Lifecycle Data Models for Smart Automotive and Smart Manufacturing Deliverable number: D5.1 Dissemination level: Public Delivery data: 13. June 2018 Editor: Violeta Damjanovic-Behrendt Author(s): Violeta Damjanovic-Behrendt (SRFG) Michaela Mühlberger (SRFG) Cristina de Luca (IFAT) Thomos Christos (IFAT) Reviewers: Heinz Weiskirchner (NOKIA) Edin Arnautovic (TTTech) The IoT4CPS project is partially funded by the “ICT of the Future” Program of the FFG and the BMVIT. The IoT4CPS Consortium: IoT4CPS – 863129 Lifecycle Data Models for Smart Automotive and Smart Manufacturing AIT – Austrian Institute of Technology GmbH AVL – AVL List GmbH DUK – Donau-Universität Krems IFAT – Infineon Technologies Austria AG JKU – JK Universität Linz / Institute for Pervasive Computing JR – Joanneum Research Forschungsgesellschaft mbH NOKIA – Nokia Solutions and Networks Österreich GmbH NXP – NXP Semiconductors Austria GmbH SBA – SBA Research GmbH SRFG – Salzburg Research Forschungsgesellschaft SCCH – Software Competence Center Hagenberg GmbH SAGÖ – Siemens AG Österreich TTTech – TTTech Computertechnik AG IAIK – TU Graz / Institute for Applied Information Processing and Communications ITI – TU Graz / Institute for Technical Informatics TUW – TU Wien / Institute of Computer Engineering XNET – X-Net Services GmbH Document Control Title: Lifecycle Data Models for Smart Automotive and Smart Manufacturing Type: Public Editor(s): Violeta Damjanovic-Behrendt Author(s): Violeta
    [Show full text]
  • Openo&M Oil & Gas Industry Use Cases with Scenarios and Enabling
    OpenO&M Oil & Gas Industry Use Cases with Scenarios and Enabling Technology Ken Bever MIMOSA CTO [email protected] +1 (513) 276-4105 1 Use Cases 1 Handover Information from EPC to O/O 2 Engineering Upgrades to O&M 3 Field Changes to Plant/Facility Engineering 4 Up-to-Date Product Data Library (from On-line RDL) 5 O&M Asset Configuration Updates 6 Preventive Maintenance Triggering 7 (Semi-) Automatic Triggering of Condition Based Maintenance (CBM) 8 Early Warning Notifications 9 Incident Management/Accountability 10 Information Provisioning of O&M Systems 2 Systems Requiring Interoperability AHMS Asset Health Management System MES Manufacturing Execution System CIR Common Interoperability Registry MMS Maintenance Management System CMS Condition Monitoring System OPM Operational Performance Modelling & Optimization System DCS Distributed Control System ORM Operational Risk Management System DMS Document Management System PDM Product Data Management System EAM Enterprise Asset Management System PLC Programmable Logic Controller ENG Engineering Schematic Topology and PORT Enterprise KPI/Event Portal Instrumentation Tag Configuration Management System ERM Enterprise Risk Management System PSMS Process Safety Management System ERP Enterprise Resource Planning System QMS Quality Management System HMI Human-Machine Interface (Operator Console) REG O&M Product, Structure, Asset Registry with System Standardised Data Dictionary and Taxonomy ISBM Information Service Bus Model SCADA Supervisory Control and Data Acquisition LIMS Lab Information Management
    [Show full text]
  • Multi-Domain Semantic Information and Physical Behavior Modeling of Power Systems and Gas Turbines Expanding the Common Information Model
    SPECIAL SECTION ON CYBER-PHYSICAL SYSTEMS Received October 20, 2018, accepted November 7, 2018, date of publication November 20, 2018, date of current version December 19, 2018. Digital Object Identifier 10.1109/ACCESS.2018.2882311 Multi-Domain Semantic Information and Physical Behavior Modeling of Power Systems and Gas Turbines Expanding the Common Information Model FRANCISCO J. GÓMEZ 1, (Member, IEEE), MIGUEL AGUILERA CHAVES2, LUIGI VANFRETTI 3, (Member, IEEE), AND SVEIN HARALD OLSEN4 1Royal Institute of Technology, SE-100 44 Stockholm, Sweden 2Instituto Costarricense de Electricidad, San José 10032-1000, Costa Rica 3Renssealer Polytechnic Institute, Troy, NY 12180-3590, USA 4Statnett SF, 0423 Oslo, Norway Corresponding authors: Francisco J. Gómez ([email protected]) and Luigi Vanfretti ([email protected]) The work of F. J. Gómez was supported by the ITEA3 Project 14018, Open Cyber-Physical System Model-Driven Certified Development (openCPS). The work of L. Vanfretti was supported in part by the Engineering Research Center Program of the National Science Foundation and the Department of Energy under Award EEC-1041877 and in part by the CURENT Industry Partnership Program. ABSTRACT Due to the rapid increase of intermittent energy resources (IERs), there is a need to have dispatchable production available to ensure secure operation and increase opportunity for energy system flexibility. Gas turbine-based power plants offer flexible operation that is being improved with new technology advancements. Those plants provide, in general, quick start together with significant ramping capability, which can be exploited to balance IERs. Consequently, to understand the potential source of flexibility, better models for gas turbines are required for power system studies and analysis.
    [Show full text]
  • Accessing PI System Using OPC Unified Architecture
    Accessing PI System using OPC Unified Architecture Alisher Maksumov OPC Development Group Lead OSIsoft, Inc. Agenda • What is OPC Unified Architecture? • OPC UA Web Services • Information Modeling • Client and Sever Communication • Exposing PI System • Server and Client Demo • OPC UA Roadmap • Summary What is OPC Unified Architecture? • Next generation of OPC technology – Platform independent • Designed with SOA principles – Extensible, discoverable – Well defined message syntax • Mapped into Web Services – WSDL, XML schema, SOAP – Message exchange over HTTP/HTTPS • Supports enhanced security – Certificates, Encryption, Signature • Adopts Information Modeling concepts – Browsable and discoverable Address Space model – Objects, Nodes, Types, Data Variables, Properties OPC UA Specification • Part 1 – Concepts • Part 2 – Security • Part 3 – Address Space Generic Parts • Part 4 – Services • Part 5 – Information Model • Part 6 – Mappings Mapping to Web Services • Part 7 – Profiles Supported features • Part 8 – Data Access • Part 9 – Alarms and Conditions Parts specific to classic • Part 10 – Programs OPC mapping • Part 11 – Historical Access • Part 12 – Discovery OPC Server discovery • Part 13 – Aggregates OPC UA Web Services • Defined in OPC UA Spec (Parts 4, 6) and OPC UA WSDL • Can be group into service sets: – Discovery Service Set • FindServers, GetEndpoints, RegisterServer – Secure Channel Service Set • OpenSecureChannel, CloseSecureChannel – Session Service Set • Create, Activate, Close Session – Node Management Service Set • Add and
    [Show full text]
  • OPC UA Server App OPC UA Server for Ctrlx CORE
    Application Manual OPC UA Server App OPC UA Server for ctrlX CORE R911403778, Edition 03 Copyright © Bosch Rexroth AG 2021 All rights reserved, also regarding any disposal, exploitation, reproduction, editing, distribution, as well as in the event of applications for industrial property rights. Liability The specified data is intended for product description purposes only and shall not be deemed to be a guaranteed characteristic unless expressly stipulated in the contract. All rights are reserved with respect to the content of this documentation and the availability of the product. DOK-XCORE*-OPCUA*SERV*-AP03-EN-P DC-IA/EPI5 (TaDo/MePe) f5f200cddfc773880a347e883d356b4f, 3, en_US OPC UA Server App 3 / 31 Table of contents 1 About this documentation 4 2 Important directions on use 5 2.1 Intended use. 5 2.1.1 Introduction. 5 2.1.2 Areas of use and application . 5 2.2 Unintended use. 6 3 Safety instructions 7 4 Introduction into the OPC Unified Architecture 9 4.1 General information. 9 4.2 Overview on specifications . 9 4.3 Information model . 10 4.4 Service-oriented architecture . 10 5 Rexroth ctrlX OPC UA Server 17 5.1 The ctrlX OPC UA Server in the ctrlX AUTOMATION . 17 5.2 Installation on ctrlX CORE. 17 5.3 Properties. 19 5.4 Configuration . 19 5.4.1 Certificate configuration . 20 6 Related documentation 23 6.1 Overview. 23 6.2 ctrlX AUTOMATION. 23 6.3 ctrlX WORKS. 23 6.4 ctrlX CORE. 24 6.5 ctrlX CORE Apps. 24 7 Service and support 27 8 Index 29 R911403778, Edition 03 Bosch Rexroth AG 4 / 31 OPC UA Server App 1 About this documentation Editions of this documentation Edition Release Notes date 01 2020-06 First edition 02 2021-01 Revision ctrlX CORE version UAS-V-0106 03 2021-04 Revision ctrlX CORE version UAS-V-0108 Bosch Rexroth AG R911403778, Edition 03 OPC UA Server App 5 / 31 Intended use 2 Important directions on use 2.1 Intended use 2.1.1 Introduction Rexroth products are developed and manufactured to the state-of-the-art.
    [Show full text]
  • A Conceptual Framework for Constructing Distributed Object Libraries Using Gellish
    A Conceptual Framework for Constructing Distributed Object Libraries using Gellish Master's Thesis in Computer Science Michael Rudi Henrichs [email protected] Parallel and Distributed Systems group Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology June 1, 2009 Student Michael Rudi Henrichs Studentnumber: 9327103 Oranjelaan 8 2264 CW Leidschendam [email protected] MSc Presentation June 2, 2009 at 14:00 Lipkenszaal (LB 01.150), Faculty EWI, Mekelweg 4, Delft Committee Chair: Prof. Dr. Ir. H.J. Sips [email protected] Member: Dr. Ir. D.H.J. Epema [email protected] Member: Ir. N.W. Roest [email protected] Supervisor: Dr. K. van der Meer [email protected] Idoro B.V. Zonnebloem 52 2317 LM Leiden The Netherlands Parallel and Distributed Systems group Department of Software Technology Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology Mekelweg 4 2826 CD Delft The Netherlands www.ewi.tudelft.nl Sponsors: This master's thesis was typeset with MiKTEX 2.7, edited on TEXnicCenter 1 beta 7.50. Illustrations and diagrams were created using Microsoft Visio 2003 and Corel Paint Shop Pro 12.0. All running on an Acer Aspire 6930. Copyright c 2009 by Michael Henrichs, Idoro B.V. Cover photo and design by Michael Henrichs c 2009 http:nnphoto.lemantle.com All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the author.
    [Show full text]
  • National Standardization Plan 2019-2022
    FINAL APRIL 2020 NATIONAL STANDARDIZATION PLAN 2019-2022 Table of Contents 1 Introduction ............................................................................................................................................................. 2 2 Background ............................................................................................................................................................. 4 3 Methodology ............................................................................................................................................................ 4 3.1 Economic Priorities (Economic Impact Strategy) ................................................................................ 5 3.2 Government Policy Priorities ............................................................................................................ 12 3.3 Non-Economic Priorities (Social Impact Strategy) ............................................................................ 14 3.4 Stakeholders requests (Stakeholder Engagement Strategy) ............................................................. 15 3.5 Selected Sectors of Standardization and Expected Benefits ............................................................. 16 3.5.2 Benefits of Selected Sectors and Sub-Sectors of Standardization ................................................ 17 4 Needed Human and Financial Resources and Work Items Implementation Plan............................................ 19 4.1 Human Resources by Type of Work Item and Category ...................................................................
    [Show full text]
  • Comtrol IO-Link to OPC UA
    FOR IMMEDIATE RELEASE CONTACT: Jordan DeGidio Marketing Specialist +1 763.957.6000 [email protected] Comtrol Implements OPC-UA connectivity with MultiLink™ on IO-Link Master family MINNEAPOLIS, Minnesota – April 21, 2017 — Comtrol Corporation, a manufacturer of industrial device connectivity products and the official North American IO-Link Competency Center, today announced the availability of OPC-UA support with its MultiLink™ technology on its IO-Link Master family of products. OPC Unified Architecture (OPC-UA) is a machine to machine communication protocol developed for industrial automation. OPC-UA allows customers to communicate with industrial equipment and systems for data connection and control, freely use an open standard, cross-platform, implement service-oriented architecture (SOA) software and utilize robust security. Comtrol’s MultiLink™ technology allows IO-Link Masters to simultaneously provide sensors Process data to PLC platforms, while also sending the sensors ISDU Service and Process data via Modbus TCP or OPC-UA upstream to IIoT/Industry 4.0 Cloud solutions or factory SCADA systems. Comtrol’s IO-Link Masters are available in three industrial Ethernet protocols: EtherNet/IP, Modbus TCP and PROFINET IO, which are all capable of running OPC UA with MultiLink™. “The OPC Foundation is very excited about the great work that Comtrol Corporation has been doing with the OPC UA technology. Their company specializes in quality networking and industrial data communication products, with the addition OPC UA to their portfolio of IO-Link Masters, factory automation users will have a seamless connection from IO-Link sensors and actuators to SCADA/HMI and cloud systems. This will add significant capability allowing seamless interoperability across the multitude of industrial networks and industrial devices says Thomas J Burke, OPC Foundation President & Executive Director.
    [Show full text]
  • GATEKEEPER Platform Overview
    GATEKEEPER – Platform overview Table of contents ABSTRACT .........................................................................................................................................................4 1 ARCHITECTURE DEFINITION PRINCIPLES ................................................................................... 5 1.1 WEB OF THINGS ................................................................................................................................................................. 5 1.1.1 Principles for Gatekeeper data ....................................................................................................................... 6 1.1.2 Gatekeeper Web of Thing based architecture .................................................................................... 7 1.1.3 Role of WoT Thing Description ....................................................................................................................... 9 1.1.4 Role of FHIR and relation with Thing Description ............................................................................ 15 1.2 GATEKEEPER PLATFORM STAKEHOLDERS ........................................................................................................ 16 1.3 SECURITY AND PRIVACY CONSIDERATIONS ....................................................................................................... 17 1.3.1 Infrastructure security ..........................................................................................................................................18
    [Show full text]
  • Data Exchange in Distributed Mining Systems by OPC Unified Architec- Ture, WLAN and TTE VLF Technology
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Technische Universität Bergakademie Freiberg: Qucosa REAL TIME MINING - Conference on Innovation on Raw Material Extraction Amsterdam 2017 Data exchange in distributed mining systems by OPC Unified Architec- ture, WLAN and TTE VLF technology. David Horner1, Friedemann Grafe2, Tobias Krichler1, Helmut Mischo1, Thomas Wilsnack2) 1 TU Bergakademie Freiberg 2 IBeWa Consulting ABSTRACT Mining operations rely on effective extraction policies, which base on concerted manage- ment and technical arrangements. In addition to commodities, mining of data is the in- creasingly matter of subject in mining engineering. The Horizon 2020 project – Real-Time- Mining supports the ongoing paradigm shift of pushing mining activities from discontinuous to continuous operation. In this respect, the partners TU Bergakademie Freiberg (TU BAF) and IBeWa Consulting tackle the issue of physical and logical data acquisition in under- ground mining. The first aspect of the project addresses the ‘logical’ provision of data. Mining technology is increasingly interacting among each other and integrated into globally distributed sys- tems. At the same time, the integration of current mining devices and machineries into su- perordinated systems is still complex and costly. This means only a few number of mining operators is capable to integrate their operation technology into a Supervisory Control and Data Acquisition (SCADA) system. TU BAF presents the middleware OPC Unified Archi- tecture, which is a platform independent middleware for data exchange and technology interconnection among distributed systems. By installing a SCADA demonstrator at the research and education mine Reiche Zeche, TU BAF intends to present the technical fea- sibility of a SCADA system basing on OPC UA even for SME mining operations.
    [Show full text]
  • CBOR (RFC 7049) Concise Binary Object Representation
    CBOR (RFC 7049) Concise Binary Object Representation Carsten Bormann, 2015-11-01 1 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 2 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 3 Slide stolen from Douglas Crockford History of Data Formats • Ad Hoc • Database Model • Document Model • Programming Language Model Box notation TLV 5 XML XSD 6 Slide stolen from Douglas Crockford JSON • JavaScript Object Notation • Minimal • Textual • Subset of JavaScript Values • Strings • Numbers • Booleans • Objects • Arrays • null Array ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"] [ [0, -1, 0], [1, 0, 0], [0, 0, 1] ] Object { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } Object Map { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } JSON limitations • No binary data (byte strings) • Numbers are in decimal, some parsing required • Format requires copying: • Escaping for strings • Base64 for binary • No extensibility (e.g., date format?) • Interoperability issues • I-JSON further reduces functionality (RFC 7493) 12 BSON and friends • Lots of “binary JSON” proposals • Often optimized for data at rest, not protocol use (BSON ➔ MongoDB) • Most are more complex than JSON 13 Why a new binary object format? • Different design goals from current formats – stated up front in the document • Extremely small code size – for work on constrained node networks • Reasonably compact data size – but no compression or even bit-fiddling • Useful to any protocol or application that likes the design goals 14 Concise Binary Object Representation (CBOR) 15 “Sea Boar” “Sea Boar” 16 Design goals (1 of 2) 1.
    [Show full text]
  • Data Management Plan (First Version)
    Open Sea Operating Experience to Reduce Wave Energy Costs Deliverable D8.5 Data Management Plan (first version) Lead Beneficiary TECNALIA Delivery date 2016-07-27 Dissemination level Public Status Approved Version 1.0 Keywords Open access, datasets, metadata, ZENODO This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 654444 D8.5 Data Management Plan (first version) Disclaimer This Deliverable reflects only the author’s views and the Agency is not responsible for any use that may be made of the information contained therein Document Information Grant Agreement Number 654444 Project Acronym OPERA Work Package WP 8 Task(s) T8.2 Deliverable D8.5 Title Data Management Plan (first version) Author(s) Pablo Ruiz-Minguela (TECNALIA), Endika Aldaiturriaga (OCEANTEC) File Name OPERA_D8.5_Data management plan_TECNALIA_20160727_v1.0.docx Change Record Revision Date Description Reviewer 0.0 14-04-2016 Initial outline Pablo Ruiz-Minguela 0.5 21-06-2016 Full draft contents WP8 partners 0.9 15-07-2016 Version for peer review Sara Armstrong (UCC) 1.0 27-07-2016 Final deliverable to EC EC OPERA Deliverable, Grant Agreement No 654444 Page 2 | 30 D8.5 Data Management Plan (first version) EXECUTIVE SUMMARY This document, D8.5 Data Management Plan (DMP) is a deliverable of the OPERA project, which is funded by the European Union’s H2020 Programme under Grant Agreement #654444. OPERA’s main goal is to collect, analyse and share open sea operating data and experience to validate and de-risk four industrial innovations for wave energy opening the way to long term cost reduction of over 50%.
    [Show full text]