DIAS Overview JRC Ispra, 17-Mar-2017

Size: px

Start display at page:

Download "DIAS Overview JRC Ispra, 17-Mar-2017"

Shannon Hood
6 years ago
Views:

1 DIAS Overview JRC Ispra, 17-Mar-2017 Simon Jutz, Head Copernicus Space Office, Earth Observation Programmes Directorate Slide 2 1

2 Sentinel-2B launched on 6 March 2017 from Kourou Very precise orbit insertion (<100 m) Spacecraft health in excellent state For the first time ESA had a dedicated. group on social media at the launch event in ESOC Slide 3 Sentinel-2B First Image Brindisi, 15 March 2017 Slide 4 2

3 Further Launches 2017 Sentinel-5P on Rockot launch date Summer 2017 Sentinel-3B on Rockot launch end of 2017 Slide 5 Sentinels Data Access User Registration Number of registered users 61,920 self-registered unique users (status 7 February 2017) Sen nels missions data users ESA missions data users Slide 6 3

Sentinels Data Dissemination Volumes Approx. 4,6 MILLION products were downloaded during Q4-2016 corresponding to 4.

4 Sentinels Data Dissemination Volumes Approx. 4,6 MILLION products were downloaded during Q corresponding to 4.6 PB of data Slide 7 Copernicus Data and Information Access Services Copernicus DIAS procurement is one element of the Partnership and aligned programming between DG-GROW and ESA Creating and enabling a European EO Data ecosystem for research and business A common European approach to EO data exploitation with Copernicus data at its core Implementing the EO-Innovation Europe concept in full complementarity with the COM initiatives notably the Copernicus Data and Information Access Services Slide 8 4

Copernicus Data and Information Access Services ESA detailed implementation approach endorsed by European Commission and Copernicus Committee Slide 9 Copernicus Data and Information Access Services

5 Copernicus Data and Information Access Services ESA detailed implementation approach endorsed by European Commission and Copernicus Committee Slide 9 Copernicus Data and Information Access Services DIAS ITT released in January 2017, closing date 14 April 2017 DIAS Contract(s) K.O.: July 2017 DIAS initial services start: January 2018 The procurement foresees a 4 years duration with possible yearly extension under same operational conditions (subject to the review process with the European Commission) DIAS Phase-In DIAS Operations Ops. extension Jan.17 Jul.17 Jan.18 Jan.19 Jan.20 Jan.21 KO(s) Slide 10 5

6 DIAS Context and Objectives Slide 11 DIAS Context and Objectives Bringing together data & user processing One year of Sentinels operations represents several PBs of new data (rate ~ 10 PB/year in 2018) - User products: More than 1 Million of new records generated every three months / 2015 : archive exploitation ratio of 10 - Currently more than 50,000 registered unique users (different s) Sizing figures for the Copernicus Services data and information and the Sentinels products are provided in the IGS Functional Requirements Document included as reference document as part of the ITT documentation *Note: Archive exploitation ratio is defined as the Number of downloads / Number of products in the archive Slide 12 6

Copernicus Campus DIAS Context and Objectives Technical overview: Front-office DIAS Frontoffice End user: User of the third-parties services Third-Party user interface Third-Party resources

through direct agreement between the DIAS provider and the Third-party.

7 Copernicus Campus DIAS Context and Objectives Technical overview: Front-office DIAS Frontoffice End user: User of the third-parties services Third-Party user interface Third-Party resources Third-Party DIAS Provider Slide 13 Procurement Objectives and Requirements Support for Third-party services integration The DIAS Provider may provide technical integration support to Third-parties through direct agreement between the DIAS provider and the Third-party. In addition, the DIAS provider may be requested by ESA as part of the contract to provide technical support to a Third-party for the integration of its service(s) on the DIAS. The associated effort will be covered through the activation of this Optional activity. The task may be activated as many times as necessary during the contract duration. The DIAS provider shall describe the proposed approach to provide such support. Applicable hourly rates shall be provided as part of the financial proposal. Slide 14 Pg. 14 7

Conclusion Scenario overview: remote DIAS services access End user accessing the support services to browse through the different DIAS offers Slide 15 Conclusion Scenario overview: Provision of

Third-party autonomously configures its own front-office environment (e.g. install own application, select needed data collections).

8 Conclusion Scenario overview: remote DIAS services access End user accessing the support services to browse through the different DIAS offers Slide 15 Conclusion Scenario overview: Provision of Third-party services on Copernicus DIAS 3 OPERATE The Third-party autonomously operates its own front-office services and user community 2 CONFIGURE 1 AGREE& GET ACCESS TO THE REQUIRED RESOURCES The Third-party autonomously configures its own front-office environment (e.g. install own application, select needed data collections). In doing this, it is able to browse through all (virtually) available DIAS collections through DIAS interfaces. It has also the possibility to reuse any DIAS available tool. It is able to contact the DIAS Help Desk in case support is needed. The Third-party takes direct contact with the DIAS Provider to get access to the needed resources according to the DIAS Commercial Services Offer (incl. processing, storage and network capacity as well as data collections access). Slide 16 8

Conclusion Scenario overview: Chaining of Third-party services on Copernicus DIAS 4 OPERATE 3 GET ACCESS TO THIRD PARTY DATA 2 CONFIGURE Third-parties operate their own services for their own users

9 Conclusion Scenario overview: Chaining of Third-party services on Copernicus DIAS 4 OPERATE 3 GET ACCESS TO THIRD PARTY DATA 2 CONFIGURE Third-parties operate their own services for their own users community Third-party(2) negotiates data and interfaces with another Third-party(1) service provider. Direct link between the Third-parties. The Third-parties autonomously configures their own front-office environment. 1 AGREE & GET ACCESS TO THE REQUIRED RESOURCES The Third-parties take direct contact with the DIAS Provider to get access to the needed resources according to the DIAS Commercial Services Offer. Slide 17 9

The Sentinels Mission Control Systems a versatile approach to deployment and operations

The Sentinels Mission Control Systems a versatile approach to deployment and operations Michael Koller 01/03/2016 Issue/Revision: 1.2 Reference: Status: Approved 2016 by the European Space Agency. Published