Skip to main content

High Resolution Copernicus-Based Information Services at Sea for Ports and Aquaculture

Deliverables

Data Management Plan

The data governance approaches should cover the following topics: - Define data management strategies. Historical maintenance, data formats, meta-data, etc. For instance the issue of the management of the historical data (what to keep, for how long, with which level of accessibility) is an issue that is a common ground of discussion between the service providers; - Data access procedures: import data, point to original data sources, caching levels, etc. It includes EO data and environmental data retrieval for the entire project. The data will be adapted and pre-processed when needed to feed the service operation with needed inputs; - Big data issue approaches: how to manage the large data sets that will be available daily; - Data integration and fusion: merge of different data sources, build best available data sets, fuse different data sources to produce derived data sets, etc.; - Data privacy policy: methods to ensure the rules established by the data owners are effectively observed); - Data quality control

Service Level Agreement

For the demonstration cases auditing actions based on the previously defined auditing procedures (Task 5.4) will be performed in order to assess the system reliability and to identify any problem that may affect the system. As a result of these audits, beyond the identification of the aspects that may need improvements; it will also be possible to get the information about the service level agreement (SLA) accomplishment. The ability of being able to commit with an agreed SLA with the clients, including quality, availability and responsibilities, are of the major importance for the services success. There will be two deliverables in total.This will be the first one.

Integration of external data Sources

The HiSea operational system makes use of these different “data sources”. These data sources primarily include Copernicus data sources and other external data that is being collected locally or remotely or external model results. In order for the platform to be able to properly “talk” with these different data sources specific plugins for each data will be set up. A relevant and innovative aspect of the HiSea is its capability to import any type of data and use the different data sources to automatically build what is commonly called the “best available information”. This aspect contributes to increase the service reliability and resilience once if for some unexpected circumstance a data source is not available, the system is capable to use an alternative source. Usually the systems have a rank of data source priority and it always tries to use the data from the highest rank. In case of unavailability, it tries the next one and so on.

Report on end-users’ needs and requirements

Partners will extensively map end-users’ activities, interests, data and information. Different users and stakeholders with interests and business in the addressed target groups will be contacted and informed on the service capacities and potential benefits for their activity. Link to WP2. There will be two deliverables in total.This will be the first one.

Updated Data Management Plan

The data governance approaches should cover the following topics: - Define data management strategies. Historical maintenance, data formats, meta-data, etc. For instance the issue of the management of the historical data (what to keep, for how long, with which level of accessibility) is an issue that is a common ground of discussion between the service providers; - Data access procedures: import data, point to original data sources, caching levels, etc. It includes EO data and environmental data retrieval for the entire project. The data will be adapted and pre-processed when needed to feed the service operation with needed inputs; - Big data issue approaches: how to manage the large data sets that will be available daily; - Data integration and fusion: merge of different data sources, build best available data sets, fuse different data sources to produce derived data sets, etc.; - Data privacy policy: methods to ensure the rules established by the data owners are effectively observed); - Data quality control (dealing with different data providers the question of the data quality control for instance is quite relevant once the users will be expecting that the data provided by the service is reliable). There will be two deliverables in total.This will be the second one.

Operational modelling procedures

In the framework of this deliverable the necessary actions to import model forecasts will be defined, existing providers (e.g. Copernicus Service, GFS, etc.) identified and, where necessary, the required operational ‘chain’ of models to run in the platform (hydrodynamics, waves, oil dispersion, biogeochemical). All these model results will be made available through the HiSea platform. These results will be later implemented in the framework of WP5.

Report on State of the art

Make an assessment of the current state of the art relating existent similar services; scan all potential data sources (including satellite/Copernicus data, in-situ systems, and online models) and identifying and assessing data gaps. Determine feasibility and availability of current archived satellite data. Also determine in-situ observations that may be required to support the validation process.

Initial report on the users feedback

The deliverable will gather feedback from users and analysis and identify points and ways forward in the process and possible adjustment. The task will be carried out throughout the whole project in iterative way to ensure that the user’s community requirements are met at all stages of the project and to facilitate the uptake of their needs and requirements in the process, to confirm their uptake in the on-going improvement of the services and its usefulness and value to the users themselves. The users’ opinion is of prime importance to adjust the way the services are being provided and getting wider acceptance. This deliverable will be the first report of four deliverables in total.

Guideline for communication flow

The communication flow will be bottom-up and top-down through the typical communication methods such as: meetings, e-mail, phone, etc. In particular a cooperative working method using a website will be established. The system will be organized with a structure in which all participants can leave and download information to and from the different WPs and tasks according to their role and responsibilities. Passwords will be generated to all partners as well as to the EC. Minutes and guidelines will be made available through the internal communication system.

Establishing governance structure

The Governance structure will be implemented in line with the management structure (see 3.2.1), which defines the roles, responsibilities and activities of the different committees and other decision rules. The Coordinator will be responsible for the coordination of the different WPs and scientific and technical aspects of the project. For this purpose, the Coordinator will be supported by a RTD Manager, Innovation Manager and an Administrative Manager. Together they form the Project Executive. The Coordinator will also be responsible for the day to day com¬munications with the European Commission (EC), all technical, administrative, financial, ethical and legal issues as well as for the management of the knowledge. WPs leaders will be in charge of the coordination of their WPs and task leaders will be responsible for the coordination of their respective tasks. The Coordinator will be the chairman of the General Assembly and the Project Executive.

HiSea backend architecture guidelines

Currently the existent backend platforms (including the ones being proposed here FEWS and AQUASAFE) work in more “traditional” workstation environments. By moving to a cloud based system will need some adjustments in the overall architecture, but will allow moving to the next level of micro services concept based on docker containers. This approach will make the platforms independent of the infrastructure supporting an easy deployment in a cloud environment such as DIAS but also enabling the services to run in any type of operating system (Linux or Windows). This task will be focused on defining the backend design and assessing the required work to achieve this goal.

Report on the ethics requirements related to collection, storage and processing of personal data

This deliverable will address the requirements related to collection, storage and processing of personal data. The document will include the main issues (e.g. obtaining ethical approvals for the collection of personal data by the competent National Data Protection authority) that need to be taken into account by the partners when dealing with the data protection and privacy aspects. This document will also provide guidance for the identification of the privacy and data protection aspects and how such issues need to be dealt with in the project along with a description of the measures that need to be taken in order to comply with the relevant EU rules.

Report on technical requirements for the service platform

The use case scenarios are analysed and translated into platform requirements as soon as they are described. Functional, robustness and stress requirements will provide top level services description in line with use cases description and data governance. These requirements are described without any consideration of the HiSea platform architecture to ensure an end-to-end services definition.

HiSea frontend drafts

The service frontend (e.g. desktop, web, mobile) is a key component of any service. Through the frontend users have access to the service. So its level of acceptance is closely related with the service capability to properly answer to the user’s questions but also with its design and effectiveness. In this context this is a critical service component that must be developed in close cooperation with potential users to ensure that the required functionalities are integrated and that the information is delivered in the most comprehensive way (e.g. content, formats, design, etc.). This task will be focused on preparing some service mock-ups (e.g. web and mobile clients) to enable an informed exchange of ideas with different potential users that lead to a first draft of how the services looks like.

Minutes of General Assembly

The Project Executive (PE) will be responsible for continuous risk management (i.e. technical, financial and administrative risk) and for an effective implementation of the contingency plan, which will be periodically reviewed. After each major stage of the project, the PE will conduct a risk assessment of the achieved results and determine in advance if a correction action should be carried out for the next stages. This includes (i) reporting any minor deviations from the project plan to the General Assembly (GA); (ii) implementing the GA recommendations in the contingency plan associated with the specific WP in question; (iii) drafting additional or alternative contingency plans, if needed, together with other relevant persons (e.g. the WP Leader in question; (iv) communicating the conclusions from the GA, regarding the revised strategies, to all project members, and include them in the project plan; and (v) in the event of more serious problems, convene with the GA the best route forward; the Coordinator w

Report on sustainable supply chain

The deliverable focuses on establishing the most operational supply chain in terms of data information flow through the platform. This deliverable will analyse the potential to improve the operational performance of algorithms and workflows to provide HiSea services as well as process and display data. It will generate operational components, which are required for the service provision, such as metadata sheets, quick looks and quality descriptions. In order to make the service ready to be integrated into client’s workflows and day to day work activities, customized solutions to the platforms are provided. Further making sure that tools developed integrate with client operation procedures, workflows and security requirements. Provide user administrative functions and organizations administrative functions.

Service Tools Prototype I

This deliverable consists of the development of different tools that may provide are meant to be used by the service users in order to tailor customized derived products adapted to their needs. At the most basic level, a toolset of statistical methods will be provided to extract means, limits, trends, patterns, etc. in order to deliver uniform, easy to use forecast information both to generic users and premium services alike. On top of this layer, a customizable engine will allow the combination of these outcomes under the form of more complex events, facilitating the composition of triggering rules for notifications and reports on meaningful events for the users. There will be two deliverables in total.This will be the first one.

A project identity and specific project website

A corporate identity for HiSea will be created to ensure a common graphic line (project leaflet, website, mobile app, presentation templates etc.) for all communications material produced by the consortium. A specific website for the project will be set-up and maintained by Agora for the duration of the project and for a further 3 years after the project completion. After three years it will be owned and eventually maintained by the Consortium. Its structure will be: i) An external website (accessible to everyone) that will be the main information resource of the project (describing project objectives, partners, work areas and results), coordinated by Agora and updated with the help of all partners. An external website (accessible to everyone) that will be the main information resource of the project (describing project objectives, work areas, results and partners), coordinated by Agora and updated with the help of the participating partners. ii) An additional internal platform or extranet (restricted area),

Service Routing and Deployment Prototype I

Services of HiSea will be realized on top of Docker as described in T5.1. As such, they will be available as independent services (“micro services”), which can be used by the clients of T5.2. Task 5.4 will interconnect those micro services using a service routing approach, which will most likely be handled via a reverse proxy such as Traefik (https://traefik.io/). The component will ensure that requests from clients are reaching the correct services. The task will also shield all services via an HTTPS layer and it will allow the detection of attacks. Additionally, services will be monitored for their availability. As soon as a service becomes unavailable, new services instances will be deployed via T5.5 and team members will be notified. There will be two deliverables in total.This will be the first one.

Outline of ORDP

The data governance approaches should cover the following topics: Define data management strategies. Historical maintenance, data formats, meta-data, etc. For instance the issue of the management of the historical data (what to keep, for how long, with which level of accessibility) is an issue that is a common ground of discussion between the service providers; Data access procedures: import data, point to original data sources, caching levels, etc. It includes EO data and environmental data retrieval for the entire project. The data will be adapted and pre-processed when needed to feed the service operation with needed inputs; Big data issue approaches: how to manage the large data sets that will be available daily; Data integration and fusion: merge of different data sources, build best available data sets, fuse different data sources to produce derived data sets, etc.; Data privacy policy: methods to ensure the rules established by the data owners are effectively observed); Data quality control (deal

Publications

Improvement of an Operational Forecasting System for Extreme Tidal Events in Santos Estuary (Brazil)

Author(s): Joana Mendes, Paulo Leitão, José Chambel Leitão, Sofia Bartolomeu, João Rodrigues, João Dias
Published in: Geosciences, Issue 9/12, 2019, Page(s) 511, ISSN 2076-3263
DOI: 10.3390/geosciences9120511