Commission Implementing Decision (EU) 2018/620 of 20 April 2018 on the technical specifications for the Copernicus service component pursuant to Regulation (EU) No 377/2014 of the European Parliament and of the Council (Text with EEA relevance)
EU Decision 2018/620 · Adopted 20 April 2018 · Extends to United Kingdom
Commission Implementing Decision (EU) 2018/620
of 20 April 2018
on the technical specifications for the Copernicus service component pursuant to Regulation (EU) No 377/2014 of the European Parliament and of the Council
(Text with EEA relevance)
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Regulation (EU) No 377/2014 of the European Parliament and of the Council of 3 April 2014 establishing the Copernicus Programme and repealing Regulation (EU) No 911/2010f1, and in particular Article 9(8)(a) thereof,
Whereas:
(1)
The Copernicus Programme, which was established by Regulation (EU) No 377/2014, is a civil, user driven programme, building on the existing national and European capacities, with the overarching operational objective to provide accurate and reliable information in the field of the environment and security, tailored to the needs of users and supporting other Union policies, more specifically relating to the internal market, transport, environment, energy, civil protection and civil security, cooperation with third countries and humanitarian aid.
(2)
Pursuant to Regulation (EU) No 377/2014, Copernicus consists of three components, including a service component the purpose of which is to ensure delivery of information in the following areas: atmosphere monitoring, marine environment monitoring, land monitoring, climate change, emergency management and security. The Commission has the overall responsibility for Copernicus and coordinates its different components.
(3)
The technical specifications for the Copernicus service component are necessary to establish a baseline for the implementation of the service component as part of the governance of Copernicus.
(4)
The technical specifications for the Copernicus service component should address aspects such as scope, architecture, technical service portfolios, monitoring and evaluation, space and in situ data service needs, evolution, archiving and dissemination of data and are required to guarantee the correct operation of the Copernicus service component.
(5)
The technical specifications for the Copernicus service component should cover the entire service component, with a specific focus on the activities funded under Regulation (EU) No 377/2014.
(6)
The measures provided for in this Decision are in accordance with the opinion of the Copernicus Committee,
HAS ADOPTED THIS DECISION:
Annotations to the whole text
Footnotes
Contents
- 1Technical specifications for the Copernicus service component
- 2Entry into force
- Signature
- Annex I: GENERAL CHARACTERISTICS OF THE COPERNICUS SERVICE COMPONENT
- 1SCOPE
- GENERAL SERVICE SPECIFICATION
- 2.1Architecture
- 2.2Integrated operations
- 2.3Product and service quality management
- 2.4Continuous service improvements
- 2.5User uptake and communication
- 2.6Products dissemination and archiving
- TECHNICAL SERVICE PORTFOLIO
- 3.1Service products general standards – INSPIRE compliance
- 4MONITORING AND EVALUATION OF THE SERVICES
- Services providing routine products (land, climate change, maritime monitoring, atmosphere monitoring)
- Services providing on-demand products (e.g. security, emergency)
- 5DATA NEEDS FOR COPERNICUS
- 5.1Satellite based observation
- 5.2In situ observations
- 6EVOLUTION OF THE COPERNICUS SERVICE COMPONENT UNTIL 2020
- Annex II: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS ATMOSPHERE MONITORING SERVICE
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- (1)Regional products
- (2)Global products
- (3)Supplementary products
- (4)Emission products
- 5DATA NEEDS
- 5.1Satellites-Based Observation
- 5.2In-situ Observation
- Annex III: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS MARINE ENVIRONMENT MONITORING SERVICE
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- (1)Marine Safety
- (2)Marine Resources
- (3)Marine and coastal environment
- (4)Weather, climate and seasonal forecasting
- 3SERVICE ARCHITECTURE
- (1)Processing
- (2)Product Management
- (3)Outreach and training
- 4TECHNICAL SERVICE PORTFOLIO
- 5DATA NEEDS
- 5.1Satellites-Based Observation
- 5.2In-Situ Observation
- Annex IV: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS LAND MONITORING SERVICE
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- DATA NEEDS
- 5.1Satellites-Based Observation
- 5.2In-Situ Observations
- Annex V: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS CLIMATE CHANGE SERVICE
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATIONS
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- (1)Climate observations
- (2)Climate reanalyses
- (3)Climate projections
- (4)Seasonal forecasts
- 5DATA NEEDS
- 5.1Satellites-Based Observations
- 5.2In-situ Observations
- Annex VI: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS EMERGENCY MANAGEMENT SERVICE
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- (1)The Mapping Component
- (2)Division (2)
- 3.1Product Dissemination
- TECHNICAL SERVICE PORTFOLIO
- (1)CEMS — Rapid Mapping products
- (2)CEMS – Risk and Recovering Mapping Products
- (3)CEMS – EFAS
- (4)CEMS – EFFIS
- (5)CEMS — European Drought Observatory (EDO)
- DATA NEEDS
- 5.1Satellite –Based and In-Situ Observation
- Annex VII: THE TECHNICAL SPECIFICATIONS FOR THE COPERNICUS SECURITY SERVICE
- OBJECTIVES AND SCOPE OF THE COPERNICUS SECURITY SERVICE
- Part I: Border surveillance component of the Copernicus Security Service
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- 5DATA NEEDS
- Part II: Maritime surveillance component of the Copernicus Security Service
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- (1)Fishery control services
- (2)Maritime safety and security services
- (3)Customs services
- (4)Law enforcement services
- (5)Marine environment services
- 5DATA NEEDS
- Part III: Support for the Union's External Action component of the Copernicus Security Service
- 1SCOPE
- 2USER REQUIREMENTS AND MAIN DOMAINS OF APPLICATION
- 3SERVICE ARCHITECTURE
- 4TECHNICAL SERVICE PORTFOLIO
- (1)Reference Maps:
- (2)Road Network Status Assessment:
- (3)Conflict Damage Assessment:
- (4)Critical Infrastructure Analysis:
- (5)Support to Evacuation Plan:
- (6)Non-EU Border Map:
- (7)Camp Analysis:
- (8)Crisis Situation Picture:
- (9)Activity Report:
- 5DATA NEEDS