Figure 1: Depicts the high-level decomposition of the CSC Ground Segment targeted architecture, highlighting the components operated on cloud-based infrastructures
Overview of Copernicus Operations
The Copernicus Space Component has been established as one of the largest and most proficient Earth Observation infrastructure in the world. With six high-performance satellites put in orbit the system has evolved at a breath-taking pace. It covers Sentinel-1A; Setninel-2A and 2B ;Setninel-3(land) and Setninel-5P.
The Copernicus operations generated more than 6 PBytes of data per year. Central to the programme, the current CSC fuels the operational Copernicus Services but also provides a reliable and growing data stream for numerous new applications and services.
Since 2019, the Copernicus ground segment operations have been transferred to cloud based environments (in anticipation of the enlargement of the Copernicus Sentinel missions and in response to the ever-increasing demand for Copernicus data) and the service-orientedapproach for each component of the CSC ground segment operations has been strengthened to enhance competitiveness, prevent industrial and technical lock-in and introduce the necessary operational flexibility and transparency to allow the adaptation of the Copernicus Ground Segment to future challenges.
The new service-based architecture, with operational industrial services (such as acquisition, processing or archiving services) interconnected through standard interfaces via the Internet, relying to the maximum extent on scalable cloud services, has strengthened the operations resilience and flexibility and driven the operations management towards a “plug-and-play” service operations approach.
The transformation of the Copernicus Ground Segment, implemented between 2019 and 2022, demonstrated its resilience to efficiently deal with major contingencies such as fire on Cloud Facilities and at Inuvik Acquisition station.
All future Copernicus missions operated by ESA will be integrated in the Copernicus Ground Segment, so to benefit from the existing Ground Segment and Data Access framework, while introducing any necessary mission specificities.
The Copernicus Ground Segment high level architecture is illustrated in Fig. 1.
From a functional perspective, the Copernicus Ground Segment encompasses in particular all activities necessary to:
define and implement the mission observation scenario, including instrument and satellite downlink planning,
acquire the satellite data on ground,
gather and manage the necessary auxiliary data files for the processing of user-level-data and generate the Precise Orbit Determination for the flying Copernicus Satellites.
monitor the instrument performance, the data quality and perform all necessary calibration and validation activities,
maintain the satellite data processing algorithms and the generate the mission user-level data for the acquired instrument observations.
archive the essential mission data allowing the future re-generation of any mission user-level data,
provide open and free user access to the mission user-level data in line with the Copernicus Data Policy.
Some of these functions are common to all Sentinel missions while others are specifically implemented and operated for each Sentinel mission. The functions composing the Ground Segment architecture are implemented in the form of operational services, complying to a set of applicable input and output interfaces and to the corresponding operational performance requirements. A dedicated component, namely the End to End Operations Performance Monitoring, ensures that the offered service meets the high-level standards of the agency.
The provision of open and free access to the Copernicus user-level data is operated in the frame of the Copernicus Data Space Ecosystem service available at: https://dataspace.copernicus.eu/ . The https://www.copernicus.eu/en Data Space Ecosystem offers open and free access to Copernicus data, including easy discovery, visualisation, download, and analysis of vast amounts of data.
The challenges our society and economy are facing require higher volumes of quality data to be easily accessible for immediate analysis and the volumes expected from the Copernicus missions are further reinforcing the need for such an ecosystem.
The mission planning function is fulfilled by the Mission Planning Service(s) in the form of operational service provision making use of mission-specific systems maintained by ESA and provided as CFI to the service operator. Pre-defined observation plans are implemented for all Sentinel missions in order to guarantee continuous data flow to the operational services. The up-to-date Acquisition Plans are available at the following links, for Sentinel-1 and Sentinel-2 respectively. The mission planning function implements the observation scenario of each Sentinel mission, in line with the observation strategy implementation and with the available satellite and ground resources and constraints. The mission planning function includes a transversal planning system for the managing and de-conflicting of downlink conflicts between the various Sentinel satellite units, the Sentinels Resource Allocation system (SRA).
The ESA CSC Ground Segment includes the following Mission Planning elements:
One Sentinel-1 mission planning system, in charge of implementing the Sentinel-1 observation scenario, in line with the spacecraft operational constraints and available downlink resources.
One Sentinel-2 mission planning system, in charge of implementing the Sentinel-2 observation scenario, in line with the spacecraft operational constraints and available downlink resources.
One Sentinel-5P acquisition planning system, interfacing the Spacecraft Operations and Control for implementing the Sentinel-5P observation scenario, in line with the spacecraft operational constraints and available downlink resources
One Sentinels resource allocation system (SRA), resolving conflicts between Sentinels to prevent downlink interferences and ensure coordinated usage of downlink resources, interfacing with each Sentinel Mission planning system accordingly.
One Mission planning interface point (MPIP), also referred as Exchange Data Server, acting as a temporal repository of scheduling information generated by the various mission planning systems accessible to the CGSs for retrieving the associated acquisition schedule.
Flight Operations Service
The Flight Operation Segment (FOS) is responsible for command and control of the satellite and is operated from ESA’s European Space Operations Centre (ESOC) in Darmstadt, Germany, and in Darmstadt (EUMETSAT) for Sentinel-3 routine activities.
The FOS consists of the Ground Station and Communications Network, Flight Operations Control Centre and a General-Purpose Communication Network.
The FOS provides the capability to monitor and control the satellite during all mission phases including the Flight Dynamics System facility responsible for orbit determination and prediction, and for the generation of attitude and orbit control telecommands.
The main functions of the FOS include:
Spacecraft status monitoring. Processing housekeeping telemetry, providing information about the status of all spacecraft subsystems and attitude.
Spacecraft control. Taking control actions by means of telecommands, based on the spacecraft monitoring and following the mission plan.
Orbit determination and control. Using tracking data and implementing orbit manoeuvres, ensuring required orbital conditions are achieved.
Attitude determination and control. Using processed attitude sensor data from spacecraft monitoring and by commanded updates of control parameters through the on-board attitude control system.
On-board software maintenance. Integrating software images received from the spacecraft manufacturer (pre-launch and post-launch) into the telecommand process.
Communications. Communicating (TM/TC) with one satellite at a time.
The data acquisition function is fulfilled by Acquisition Service in the form of operational service provision.
The CSC Acquisition service is tailored to the technical baseline of each CSC satellite family and includes in particular:
X-Band Acquisition service, in line with the Sentinels satellite downlink operations technical baseline
EDRS Acquisition service, in line with the Sentinel-1 and Sentinel-2 satellites downlink operations technical baseline
Ka-Band Acquisition service, foreseen to fulfil the needs of some Expansion missions
Multiple Ground Stations may be necessary to jointly fulfil the acquisition needs of a given satellite unit and in any case, multiple Ground Stations are necessary to fulfil the overall acquisition needs. The same Ground Station may serve one single or several Sentinel missions, depending on its acquisition capacity and the various mission needs. Each Acquisition Ground Station contributing to the CSC acquisition operates autonomously with respect to the others, the allocation of downlink operations for each Ground Station being performed by the Mission Planning system of each Sentinel after being de-conflicted by the Sentinels Resource Allocation (SRA) system.
The scope of the X-Band Acquisition function is defined with the aim of minimising the need for Copernicus specificities (e.g. hosting, e.g. processing to Level-0 data). Accordingly, the functional scope is focussed on the Copernicus missions data acquisition, data downconversion, demodulation, satellite CADU data stream generation and delivery. Multiple Acquisition Ground Stations are necessary in the GS architecture to jointly satisfy the downlink needs of all flying missions. Each Acquisition Ground Station operates autonomously with respect to the others, the allocation of downlink operations for each Ground Station being performed by the Mission Planning system of each Sentinel after being de-conflicted by the Sentinels Resource Allocation (SRA) system. The same Ground Station may serve one single or several Sentinel missions, depending on its acquisition capacity and the various mission needs.
The EDRS service covers the following functions:
Regular definition of the EDRS Links available for the data downlink planning.
Optical Sentinel-EDRSGEO Link operations and Ka-Band Sentinel payload and HKTM
data acquisition based on associated link schedule, including down-converter and
Generation of Sentinel CADU data stream for the scheduled passes
Transfer of generated Sentinel CADU stream to the EDRS Interface Point
Maintenance of the EIP, ensuring its availability for consumers and handling of the CADU rolling policy
The EDRS Acquisition is a Sentinel-1 and Sentinel-2 element.
EDRS downlink visibilities are settled by the SRA in interface with the EDRS Mission Control Operations (MOC) and used by each Sentinel mission planning as part of the available downlink resources, together with the X-Band available passes.
The observation requirements of the Copernicus missions currently in operations (i.e. Copernicus Sentinel-1,2,3,5P,6) are compatible with a downlink of payload data in X-Band. In contrast, the increased volume of data generated by some of the Copernicus Expansion (COP EX) missions requires Ka-Band to fulfil the demanding downlink capacity.
The COP EX missions will also implement the CFDP protocol for the transmission of the payload data between the satellite and the ground.
The scope of the Ka-Band Acquisition function is identical to the X-Band Acquisition function and it covers the following functions:
Regular retrieval of station scheduling information from the Mission Planning Interface
Point (MPIP), as made available by the mission planning element.
Ka-Band acquisition of Sentinel satellites payload and HKTM data based on associated.
acquisition schedule, including down-converter and demodulation (HKTM is
downloaded in every orbit in Ka-Band).
Generation of Sentinel CADU data stream for the scheduled passes.
Transfer of generated Sentinel CADU stream to the Ka-Band Interface Point (CADIP)
within required timeliness
Maintenance of the CADIP, ensuring its availability for consumers and handling of the
CADU rolling policy.
The Ka-Band Acquisition is a common element for the Copernicus missions: The functional scope of the Ka-Band Acquisition is defined in order to be generic and fulfil the acquisition needs for all flying Copernicus missions requiring the Ka-Band downlink operations.
Production and routine quality control
The CSC Production operations encompass all activities necessary to process any acquired Sentinel satellite data, generating user level data, engineering data or HKTM, meeting the quality specifications and making it available for archiving and for further user access.
The production operations cover the following operational functions, addressed in more detail in the following sections:
Systematic Production, gathering the data stream acquired by the Sentinel satellites and made available at pick-up points by the Acquisition services; processing it into a set of pre-defined set of data meeting the expected specifications; and deliver them systematically and fully to the production delivery point within a given timeliness.
Reprocessing, aiming at the bulk (re-)generation of past User Level Data (typically Level-1/2) from archived lower level data (typically Level-0).
Production operations rely on the use of data processors developed and maintained by ESA, and made available to the services involved in production operations (the precise list and scope of the data processors is mission dependent):
Data processors, allowing transforming input satellite data into output User Level Data according to validated algorithms (typically Level-0, Level-1 and Level-2 data processors).
Routine Quality Control elements, allowing the automated routine quality control of all generated User Level Data as part of the systematic production data flow.
The Routine Quality Control performed as part of the production operations allows screening all generated User Level Data for detecting production related issues or data quality related issues that are identifiable in a fully automated manner. The Routine Quality Control complements the expert quality control performed as part of the calibration and validation activities and allows the fast identification of production and/or quality issues whenever their nature allows an automated detection.
In line with the Copernicus missions’ operations concept, all data acquired by the Copernicus Sentinel missions satellites is systematically processed to a set of pre-defined User Level Data types and made available to users within a given timeliness.
The systematic production is the element in charge of generating a pre-established set of User
Level Data for each Sentinel satellite according to the associated User Level Data and timeliness baseline, starting from the satellite CADU stream acquired at the Acquisition Ground Stations contributing to the satellite operations, and performing an automated routine quality control of the resulting User Level Data.
The Systematic Production operations are fulfilled by the Production Service in the form of operational service provision. Multiple Production Service contribute jointly to the overall CSC systematic production needs.
The systematic production and routine quality control operations cover the following main functions:
Retrieval of CADU data stream from the XBIP, as delivered by each Acquisition service and of CADU data steam from the EDRS Service (whenever relevant)
Retrieval of auxiliary data from AUX data gathering
Systematic production from the CADU stream of the Level-0/1/2 User Level Data in line with the Sentinel mission specificities (including CADU assembly as necessary, generation of Level-0 data, generation of the Level-1 data, generation of Level-2 data whenever relevant)
Operations and management of the Production Interface Point, including a short rolling storage (few days) to support retrieval from the various consumers
Provision of the systematically generated data to the PRIP within the required timeliness and performance
Automated routine quality control of the generated User Level Data
In order to ensure redundancy and avoid single points of failure, at least 2 services for each Sentinel mission production are foreseen as part of the Ground Segment architecture, jointly contributing to the overall mission data production without duplication (e.g. sharing implemented based on Sentinel satellite unit). The production services for each Sentinel mission comply to the same interfaces, performance and expected service outputs in order to ensure full transparency from user perspective and to be fully interchangeable.
The Reprocessing operations allow the bulk (re-)generation of past higher level data (typically Level-1/2) from archived lower level data (typically Level-0). The reprocessing function may be operated in a public cloud environment or on a private infrastructure according to the reprocessing needs, performance, capacity and effort. The Reprocessing operations are fulfilled by the Production Services according to the specific reprocessing needs.
The reprocessing covers the following main functions:
Retrieval from the LTA AIP of Level-0, auxiliary data or other data required for the processing
Generation of the requested higher level User Level Data (typically Level-1 or Level-2) according to the required processing baseline.
Provision of the data to within the required schedule and performance
Automated routine quality control of the generated User Level Data
The reprocessing is considered a specific case of Production service. Reprocessing operations are performed on a case by case basis, according to the needs for massive re-generation of a specific mission User Level Data types over a specific mission time frame with a given processing baseline.
Auxiliary Data Gathering
The processing of the acquired satellite data requires a number of auxiliary information, not included in the satellite telemetry. This encompasses different types of auxiliary information from different sources:
Regularly updated auxiliary files related to the instrument and processing configuration information, updated regularly on a need basis. These files are typically generated as part of the Cal/Val operations and used for the Level-1 production and Level-2 production.
Dynamic auxiliary information generated by external entities (e.g. ECMWF, Ifremer, etc.), systematically renewed with a known frequency. This information is often available in a heterogeneous format and requires reformatting before it can be used for the Copernicus production operations.
Dynamic auxiliary data from FOS (e.g. orbital info), systematically renewed with a known frequency.
Dynamic auxiliary orbit and attitude information generated by the POD service, systematically renewed with a known frequency.
Static and semi-statis auxiliary files, required by the data processor an updated rarely through the mission.
Production operations require access to these various types and sources of auxiliary data. In order to optimise the effort related to the auxiliary data management and ensuring coherence among all services requiring the use of auxiliary information, a single auxiliary data collector and reformatting is considered within the CSC GS Architecture. The Auxiliary Data Gathering (ADG) Service acts as a concentrator and single point of access for auxiliary data for all systematic production operations within the CSC GS. In case timeliness to specific auxiliary data is of essence for some specific production operations (e.g. access to POD for Sentinel-1 production operations), the relevant auxiliary files may overpass the ADG. Static and semi-static auxiliary data are instead managed in configuration control with the processing software (through a dedicated environment within the Reference System).
The Auxiliary Data Gathering Service covers the following key functions:
Collection of auxiliary data from the different sources (e.g. Cal&Val component, FOS, ECMWF, Ifremer, etc.) in line with the operational needs of the various Copernicus missions
Reformatting of the external auxiliary data in line with the CSC GS interfaces
Gathering of auxiliary data generated by the Cal&Val service for production operations
Repository of auxiliary data interface point
Operations and management of the Auxiliary Interface Point, including a rolling repository to support retrieval of auxiliary data from the various consumers (e.g. systematic production service, on-demand production service, Data Access and LTA service). By configuration, for some auxiliary data types, the full historic set will be maintained within the AUXIP without a rolling policy.
Mission Performance Cluster
The aim of the Mission Performance Cluster (MPC) function is to monitor the instrument performance and perform all expert activities necessary to ensure that User Level Data meet the calibration and validation specifications. The Calibration and Validation operations are fulfilled by the Mission Performance Cluster services in the form of operational services provision.
The Cal&Val function encompasses all expert activities to monitor the instrument performance, to characterise the User Level Data quality, to assess the achievement of the expected quality levels according to the product specifications, to perform all necessary activities to derive and maintain the calibration information, to perform all necessary activities to derive and maintain the validation information and to characterise the User Level Data quality and its calibration and validation levels. The function includes the scientific algorithm definition and maintenance, in particular the definition and maintenance of the Level-2 algorithms and the implementation and maintenance of the Level-2 data processors.
The Precise Orbit Determination (POD) function is in charge of the generation, provision and validation of precise orbital data and auxiliary data files for the flying Copernicus Sentinel Satellites.
The POD encompasses the following functionalities:
generation, provision and validation of precise orbital data and auxiliary data files for the relevant flying Copernicus missions (at present for Sentinel-1, Sentinel-2 and Sentinel-3)
the assessment of the GPS (Global Positioning System) receiver sensor performance on-board the Copernicus satellites, the quality of the generated data
interface and liaising with Copernicus POD Quality Working Group
interface and liaising with the International Laser Range Satellite (ILRS) community
interface and liaising with the GPS POD data providers
interface and liaising with partner agencies (CNES, EUMETSAT)
The POD function is a common to all flying Copernicus mission, used where a high precision orbit determination is required for the geolocation accuracy of the Copernicus User Level Data. This is the case for the Sentinel-1, Sentinel-2, Sentinel-3 and Sentinel-6 operations. The POD operations are based on the data from the GNSS receiver on board of the Sentinel satellites, downlinked to ground as part of the regular operations and extracted by each Systematic Production function from the overall satellite data stream. The extracted GNSS data is made available in the PRIP as input to the POD function, together with any other satellite data necessary to generate the POD auxiliary files.
The Data Preservation and Long Term Archiving function ensures the storage of the essential mission data. It is fulfilled by the Long Term Archive element in the form of operational service provision.
The Long Term Archive (LTA) service is defined to cover the following main functions:
Data Ingestion and safe storage
Data Query, Retrieval and delivery on an Archive Interface delivery Point (AIP)
Data curation and archive Integrity
Performance Monitoring and Reporting
Implementation and operations of the AIP, ensuring its availability for consumers and handling of cache policy
The LTA interface includes all the features necessary to support the above LTA functionalities. In particular, all the features to query the stored data, query performance information for monitoring purposes and to retrieve the selected data. The LTA interface allows precise query capabilities for standard EO oriented metadata, with a detailed definition of the indexed fields for each data type.
The LTA service scope is common to all missions: The functional scope of the LTA and the associated interfaces are defined in order to be Sentinel-generic and fulfil the archiving needs for any Copernicus mission. Multiple LTAs service instances are however necessary in the GS architecture to ensure geographical redundancy with separated safe storage for all Sentinel missions. The same LTA may serve one single Copernicus mission or several Copernicus missions, depending on its capacity and cost efficiencies. The content of each LTA (in terms of Sentinel mission and data types) and the overall data flow configuration (data flows between the various Sentinel production services and the various LTA services) is defined and maintained by ESA as part of the E2E operations management. Each LTA operates autonomously with respect to the other LTAs. However, the LTAs monitor their own completeness, and any missing products are downloaded from one of the other LTAs in case it is no longer available on the PRIP. An E2E view is also gathered through the E2E operations monitoring and the traceability service.
The Data Access element provides end user access to the Copernicus missions User Level Data. The Data Access element is embedded in a cloud computing ecosystem (herein called the Copernicus Data Space) that allows the provision of computing environments (IaaS, PaaS, etc.) to customers to process hosted data with high efficiency.
The GS architecture foresees a that the Data Access services serves all Copernicus missions and provides access to the Copernicus Contributing Missions Core datasets. The characteristics of the service and its criticality of the Data Access service are such that the redundancy principle followed for the CSC GS Architecture is implemented here by ensuring that the service is deployable on two separated and independent cloud infrastructure, with a rapid reconfiguration from the primary to secondary cloud in response to any disaster situation. The Data Access element relies on a unified user management user management service, providing user access to services through a common identity management. As an example, the provision of an account for the Copernicus Data Access Services shall open access to complementary Copernicus Data Space services like IaaS, PaaS or SaaS based on the same digital identity.
The Data Access element addresses the following key functions:
Data Distribution (a.k.a. Data Retrieval) function allowing download of user Copernicus mission User level data for any user. The Data Distribution function is based on immediate synchronous access to a certain configurable data set, including most recent data and past data with a configurable time span, and asynchronous access to other data e.g. via data archive or a triggering of on-demand processing.
Streamlined Access function allowing direct / interactive processing of selected datasets. The role of the Streamlined Access function is to provide an open and free streamlined and harmonised access to dedicated Sentinel User Level Data collections, allowing local processing through a Platform as a Service paradigm (e.g. Notebook server).
On-demand Production, allowing the generation of higher level of data (typically Level-1/2) from archived lower level of data (typically Level-0) available in the Long Term Archive (LTA). On-demand product is nominally triggered as a result of a user request through the Data Access function for a user level data not available for user access at the time of the request.
The Data Access Service covers the following elements:
User Registration, Terms and Conditions acceptance
Data Retrieval, Ingestion and Publication
Quicklook Generation (if needed) / Publication
Data Download functions
Data Transformation functions
Data Deletion functions
Catalogue Summary functions
Streamlined data access interfaces
Data visualisation interfaces
The Data Access is common to all flying Copernicus missions, providing at present data access for all Sentinel missions operated by ESA in the form of an operational service provision. The Data Access service provides configurable access performances to specific use typologies (Open Access, Copernicus service, Collaborative GS, International partners, etc.).
User registration is managed according to the user typologies, self-registration (web-based) for the Open Access, operator managed registration for the other services. Access policies are also configured accordingly (parallel download quota, etc.). User information are managed according to the relevant personal data policy regulations, and in principle aim to request and retain the minimum set of user information necessary to fulfil the data access operations and reporting requirements.
The Data Access function ensures the immediate availability of a configurable amount of data (from one year to the whole mission_. Data not anymore available for immediate access remain available to users through the same data access interfaces by triggering either the retrieval e.g. from a data archive or an on-demand processing. Data thus retrieved are maintained in a cache for configurable period of time.
The https://www.copernicus.eu/en Data Space Ecosystem offers open and free access to Copernicus user-level data, including easy discovery, visualisation, download, and analysis of vast amounts of data.
Users benefit from a set of data processing tools made available to extract the information they need to conduct their public, private or commercial activities. Users may provide new downstream services using the resources and interfaces made available within the Ecosystem, hence enriching the Copernicus data space with a broader service offering.
The challenges our society and economy are facing require higher volumes of quality data to be easily accessible for immediate analysis and the volumes expected from the Copernicus Expansion missions are further reinforcing the need for such an ecosystem.
The Reference System is a key element of the Ground Segment architecture, responding to multiple needs and aiming mainly at:
preventing the industrial lock-in for the production and data download operations by implementing and maintaining an open-source solution for these functions
operating an “under-scaled” production service, cloud-based, able to be scaled up to support an operational load should it be necessary, and offering a reference production and quality control environment (with well-defined access and sizing conditions)
providing a ready-to-use representative environment for the integration of new User Level Data and their pilot production phase
serving as potential representative CSC ground segment operational environment for the pre-launch activities related to the new satellite units/new Copernicus missions.
As a secondary service, The Reference System ensures the publication of the historical, new and updated versions of the Sentinel Data processors packages which are used in various components of the CSC (e.g. Production Services, Data Access).
The Reference System covers the following main functionalities and scope:
Implementation and maintenance of an operational open-source cloud-based solution for the (scaled-back) production, routine quality control and data download
Offering the interfaces for triggering the production of any Sentinel User Level Data, from fresh or archived data, and from any processing baseline
Operating an “under-scaled” production service, cloud-based, able to be scaled up to support an operational load should it be necessary, and offering a reference production and quality control environment (with well-defined access and sizing conditions)
Offering the tools and functionalities allowing a streamlined pilot integration of new data processors and the associated pilot production activities
Implementing and maintaining the tools and functionalities allowing the streamlined integration of new data flows for new Sentinel units, including associated data processing and routine quality control
Providing a suitable environment to support the pre-launch CSC ground segment preparation activities for new Sentinel units/new Copernicus missions.
Providing the possibility to trigger the processing of any historical User Level Data with any former processor version no longer part of the operational baseline.
Managing the publicly accessible repositories for all RS software related documentation, open-source code, and executables / containerised deployment images available to the various Copernicus Ground Segment operational services and to the Collaborative Ground Segment partners community in general.
Operating a dedicated Web portal and API for the publication of the Sentinel Data Processors packages, in native form and as RS addons, accessible towards duly authorized entities (e.g. Production Service operators).
Service Web Information Service
The Sentinel Web Information Service (SWIS) is the service providing up-to-date information about the Copernicus Sentinels missions to end users. It consists of the following main portals:
Sentinel Online: the main entry point for people interested in actual facts of the Sentinels missions. It collects the latest news, maintenance news, the upcoming congresses and events, an overview of the Copernicus Ground Segment and Expansion Missions, as well as a dedicated section presenting the key persons of the programme.
Success Stories: the portal collecting the most important applications of Sentinel data, presented in the form of short stories, and accompanied by high-quality images.
SentiWiki: the official technical guides for both beginners and advanced users. The SentiWiki pages collect in an organized way all the technical information about each Copernicus Sentinels missions, including (but not limited to): the purpose of the mission, the history behind, the orbital and satellite characteristics, the description of the satellite sensors, the acquired products and the relevant applications and the processing algorithms permitting to create those products. In a dedicated section, named “Document Library”, the full collection of the technical documentation of each mission is available for download. This section includes also the full set of Data Quality Reports, Acquisition Plans, the Mission Status Reports, and any other document of potential interest for end users.
Since November 2023, all the SWIS portals underwent a deep renewal and re-organization, meant to present the complex technical information about the Copernicus Sentinels missions in a clear, accessible and appealing way, chasing the maximum benefits for the users’ community.
Coordination Desk Service
End-to-End Operations Performance Monitoring
The E2E Operations performance monitoring aims at gathering the operations performance of the various services contributing to the CSC GS operations in order to build a comprehensive overall end-to-end view of the operations performance at satellite unit level, mission level and CSC GS level. The E2E Operations performance function is fulfilled by the E2E Performance Monitoring Service in the form of operational service provision.
The E2E Operations Performance Monitoring covers the following main functionalities and scope:
Implementation, maintenance and operations of an open-source cloud-based system for the E2E CSC Ground Segment Operations Performance Monitoring
Monitoring of the E2E operations of each operational service, each Sentinel satellite unit, each Sentinel mission and the overall CSC GS
Provision of a comprehensive monitoring and reporting interactive dashboard for CSC operations management, allowing access to the full operations performance information (at service level, at satellite unit level, at mission level, etc.)
Provision of a comprehensive monitoring and reporting interactive https://operations.dashboard.copernicus.eu/index.html for Copernicus users and stakeholders, providing up to date information on any operational issues at mission level, satellite level and User Level Data (including plans, unavailabilities, data quality information, operations performance information, etc.)
By its nature, the E2E Operations Performance Monitoring is common to all Copernicus missions and covers the complete operational chain, from planning to acquisition and data access, including notably the data production, quality control and archiving. Each CSC GS operational service provides an operations dashboard and/or an interface to query operations performance monitoring information. The E2E Operations Monitoring element interfaces with all the services and functions contributing to the CSC operations in order to build a comprehensive performance monitoring view.
The E2E Operation Monitoring output is the SentiBoard . Learn more here: SentiBoard
Services Operations Coordination
Service Operations Coordination consists of the engineering processes necessary to analyse the performances of the E2E CSC Ground Segment Operations, coordinate the various issues that may impact on the multiple Ground Segments Services, coordinate the response to the user’s inquiry or complaint, ensuring the correct level of information is easily available to the users with reference to the CSC operations and outputs.
The Services Operations Coordination function encompasses the following main functions:
PA/QA elements for
coordinated anomaly management,
coordinated maintenance management,
coordinated configuration control.
Coordination helpdesk operations to trigger 2nd line investigations within the various service elements.
Operations and maintenance of the Coordinated Anomaly Management System, providing an open environment shared among all entities contributing to the CSC operations, for the coordinated management of service anomalies affecting the E2E operations, management of service maintenance activities and configuration control.
Users and web information support
Integration and Validation activities
Benchmarking and Conformance testing
By its nature, the Services Operations Coordination is common to all Copernicus missions and covers the complete operational chain.