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

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

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

Reportnet 1 - ”our first house” Custom-built first home for our small family of dataflows Fixes were done quickly and on-demand However, over the years our family grew and the house started to be crowded and run-down Source: https://commons.wikimedia.org/

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

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

Comparing Reportnet 1&2 with 3 Topic Reportnet 1&2 Reportnet 3 Overall goal Designed for 2000 Designed for 2020 Main philosophy Automation of process steps Automated processes Scope Delivery Collaboration User Experience ”Application-centric” (Navigating between separate applications) ”Task-centric” (Integrated portal with customisable dashboards) Security ”Friendly environment” ”Hostile environment” Scalability Assumes constant usage load Scales dynamically based on need Software architecture Uncoordinated evolution Standardised Adding/changing a dataflow ”Developer-driven” (Most changes require software developers) ”Thematic expert driven” (Most changes can be done by thematic experts) Data management approach File-based Data-driven Data acquisition Manual file upload Machine-to-machine reporting options

Reportnet 2.0 Overview and Status Update

Motivation – why Reportnet 2.0 is needed? Annual number of Reportnet deliveries (until 21.02.2017) 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)

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 €

What did we accomplish in 2017?

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)

Reportnet 3.0 Plans

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

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

DRAFT 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 Project Owner: Chris Steenmans Solution provider: Søren Roug Directing layer Business managers: Hermann Peifer, Jan Bliki, Stefan Jensen Project manager: Ilkka Melleri Managing layer Business implementation group: EEA ACC, NSS, IEA, Eionet Project core team: EEA IDM, Consultants Performing layer Requester side Provider side

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?

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