dias overview jrc ispra, 17-mar-20171 esa unclassified -for official use dias overview jrc ispra,...
TRANSCRIPT
1
ESA UNCLASSIFIED - For Official Use
DIAS OverviewJRC Ispra, 17-Mar-2017
Simon Jutz, Head Copernicus Space Office,
Earth Observation Programmes Directorate
| Slide 2ESA UNCLASSIFIED - For Official Use
2
| Slide 3ESA UNCLASSIFIED - For Official Use
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 4ESA UNCLASSIFIED - For Official Use
Sentinel-2B First ImageBrindisi, 15 March 2017
3
| Slide 5ESA UNCLASSIFIED - For Official Use
Further Launches 2017
Sentinel-5P on Rockot
launch date
Summer 2017
Sentinel-3B on Rockot
launch end of 2017
| Slide 6ESA UNCLASSIFIED - For Official Use
Sentinels Data Access – User Registration
ESA missions data
users
Number of
registered users Sen nels missions data
users
61,920 self-registered
unique users (status 7 February 2017)
4
| Slide 7ESA UNCLASSIFIED - For Official Use
Sentinels Data Dissemination Volumes
Approx. 4,6 MILLION products were downloaded during Q4-
2016 corresponding to 4.6 PB of data
| Slide 8ESA UNCLASSIFIED - For Official Use
Copernicus Data and Information Access Services
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
Copernicus DIAS procurement is one element of the Partnership and aligned
programming between DG-GROW and ESA
5
| Slide 9ESA UNCLASSIFIED - For Official Use
Copernicus Data and Information Access Services
ESA detailed implementation approach endorsed by
European Commission and Copernicus Committee
| Slide 10ESA UNCLASSIFIED - For Official Use
Copernicus Data and Information Access Services
Ops. extension
• 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 undersame operational conditions (subject to the review process with the EuropeanCommission)
Jan.17KO(s)Jul.17 Jan.18 Jan.19 Jan.20 Jan.21
DIAS OperationsDIAS Phase-In
6
| Slide 11ESA UNCLASSIFIED - For Official Use
DIAS Context andObjectives
| Slide 12ESA UNCLASSIFIED - For Official Use
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
- 2014 / 2015 : archive exploitation ratio of 10
- Currently more than 50,000 registered unique users (different emails)
*Note: Archive exploitation ratio is defined as the Number of downloads / Number of products in the archive
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
7
| Slide 13ESA UNCLASSIFIED - For Official Use
Copernicus Campus Technical overview: Front-office
End user: User of the third-parties services
Third-Party resources
Third-Party user interface
Third-Party
DIASFront-office
DIAS Provider
DIAS Context and Objectives
| Slide 14ESA UNCLASSIFIED - For Official Use
Procurement Objectives and Requirements
Pg. 14
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.
8
| Slide 15ESA UNCLASSIFIED - For Official Use
Conclusion
Scenario overview: remote DIAS services access
End user accessing the support services to browse through the different DIAS
offers
| Slide 16ESA UNCLASSIFIED - For Official Use
Conclusion
The Third-party autonomously operates its own front-office services and user
community
3 – OPERATE
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).
1 – AGREE & GET ACCESS TO THE REQUIRED RESOURCES
2 – CONFIGURE
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.
Scenario overview: Provision of Third-party services on Copernicus DIAS
9
| Slide 17ESA UNCLASSIFIED - For Official Use
The Third-parties take direct contact with the DIAS Provider to get access to the
needed resources according to the DIAS Commercial Services Offer.
1 – AGREE & GET ACCESS TO THE REQUIRED RESOURCES
Third-party(2) negotiates data and interfaces with another Third-party(1) service provider.
Direct link between the Third-parties.
3 – GET ACCESS TO THIRD PARTY DATA
2 – CONFIGURE
The Third-parties autonomously configures their own front-office environment.
Third-parties operate their own services for their own users community
4 – OPERATE
Scenario overview: Chaining of Third-party services on Copernicus DIAS
Conclusion