1 / 18

Enhancing Dataflows with Reportnet 3.0 - A Progress Overview

Learn about the transition from Reportnet 1.0 to 3.0, goals, achievements, and upcoming plans. Explore the key principles, milestones, and project team involved. Follow the journey towards improved performance, stability, and security.

richardsk
Download Presentation

Enhancing Dataflows with Reportnet 3.0 - A Progress Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reportnet 2.0 & 3.0 An overview Ilkka Melleri | EEA | NRC EIS Meeting 24.11.2017

  2. Contents Reportnet 1, 2 & 3 – what are we talking about? Reportnet 2.0 – overview and status update Reportnet 3.0 – plans

  3. Short summary of terminology Reportnet 1.0 The existing Reportnet platform Operational since year 2000 Reportnet 2.0 Improve performance, stabilityand security of Reportnet 1.0 Planned for three years 2017-2019 Reportnet 3.0 Modernise e-Reporting

  4. Reportnet 1 - ”our first house” Source: https://commons.wikimedia.org/ • Custom-built first home for our small family of dataflows • Fixes were done quickly and on-demand

  5. Reportnet 2 – ”a renovation of the house” Source: https://commons.wikimedia.org/ Polishing up the visual appearance Additional space Increased security Modernising the infrastructure

  6. Reportnet 3 – ”a skyscraper” Source: https://www.freevector.com

  7. Comparing Reportnet 1&2 with 3

  8. Reportnet 2.0 Overview and Status Update

  9. Motivation – why Reportnet 2.0 is needed? Massive increase in Data sizes QA rule complexity Evolution of security threats Handling of more sensitive data 15 year old software Reportnet 2.0 is an effort to address these challenges Planned for 3 years (2017-2019) Annual number of Reportnet deliveries (until 21.02.2017)

  10. Planned for 2017 Enhance performance and stability of Reportnet (MPS: EEA/ITSYS/2017/021) Enhance security on Reportnet (MPS: EEA/ITSYS/2017/016) Operational management of Reportnet (MPS: EEA/PROD/2017/017) Budget: 200.000 €

  11. What did we accomplish in 2017?

  12. Status for 2017 (as of November 2017) Enhance performance and stability of Reportnet (MPS: EEA/ITSYS/2017/021) ~50% of planned work will be delivered However, overall performance and stability has improved (fewer reported major incidents) Enhance security on Reportnet (MPS: EEA/ITSYS/2017/016) ~60% of planned work will be delivered Operational management of Reportnet (MPS: EEA/PROD/2017/017) ~70% of planned work will be delivered Budget spent: 100.000 €(~50% of the planned)

  13. Reportnet 3.0 Plans

  14. Reportnet 3 - Key principles • Using state of the art ICT technology for next decade e-reporting • Supporting the key functions of the whole data flow management lifecycle • Building upon interoperable generic modules and standards • Limiting investment costs at national level by making use of existing IT infrastructure • Incorporating Reportnet 2.0 functionalities • Customisable where specific thematic user requirements exist • Reducing cost per individual data flow

  15. Reportnet 3.0 Timeline Tendering process to find IT contractor 1 Jan 2020 1 Jan 2019 1 Jan 2021 1 Jan 2018 Now Q1 Q2 Q4 Q3 Prelim. Scoping –IDM only Development of Reportnet 3.0 Stakeholder involvementExt. contractor organising a professional scoping study

  16. Reportnet 3.0 project management and governance EEA Senior Management Team Business governing layer DRAFT Steering Committee: Reps EEA, EIONET, EC (ENV, CLIMA) Steering layer Solution provider: Søren Roug Project Owner: Chris Steenmans Directing layer Business managers: Hermann Peifer, Jan Bliki, Stefan Jensen Project manager: Ilkka Melleri Managing layer Project core team: EEA IDM, Consultants Business implementation group: EEA ACC, NSS, IEA, Eionet Performing layer Provider side Requester side

  17. Role of Eionet in Reportnet 3.0 project - proposal Potential involvement Eionet partners: Reportnet 3.0 Steering Committee Eionet NFP ICT User (sub-)Group? Business implementation group Eionet NRC Environmental Information Systems (EIS)? other NRCs? ETC? Other?

  18. The End! Ilkka MelleriIT Project Manager & Architect ilkka.melleri@eea.europa.eu +45 33367100/33367276 Skype for business: ilkka.melleri@eea.europa.eu Skype: ilkkamellerieea

More Related