ESA INDUSTRY INFORMATION DAY Ground Segment...

ESA Unclassified – Releasable to the Public

Sentinels Facilities Info Day, ESRIN, 12 April 2011

ESA INDUSTRY INFORMATION DAY

Ground Segment Facilities and Network

for the GMES Sentinel Satellites

ESRIN

12 April 2011



Introduction & Status of the GMES Programme

G. Kohlhammer



Introduction

• The objective of this Industry Information Day is to provide information to industry about the forthcoming procurements for the ground segment facilities for the GMES Sentinel satellites:

– X-band acquisition stations;

– Processing and Archiving Centres;

– Mission Performance Centres;

– data circulation and dissemination network.

• In addition to some detailed information regarding each of the four procurements, this will also include some general information about the overall ground segment concept for GMES and the status of the GMES Programme.



Introduction

This procurement is part of:

• the overall GMES Space Component Programme (GSC);

• the GSC ground segment;

• the grouped procurement proposal approved by IPC in November 2010.



Introduction – Agenda

1. Introduction & Status Of GMES Programme G. Kohlhammer

2. Overview Of GMES Ground Segment E. Monjoux

3. Scope Of Procurements G. Mason

– Acquisition And NRT Stations E. Doyle

Coffee Break

– Processing And Archiving Centres (PACs) N. Houghton

– Mission Performance Centres (MPCs) Ph. Goryl

– Data Circulation And Dissemination Network G. Buscemi

– Security Requirements G. Buscemi

4. Procurement Rules L. Govaert

5. Concluding Remarks G. Mason



Introduction

• Logistics:

– Coffee break at about 11:00 for 30 mins;

– Presentation until about 13:00.

• Questions at the end of each presentation block.

• Presentation will be published via EMITS News.

• Usual clarification process once the ITT is open.



GSC Progressive Programme Build-up

2008 2009 20102007 2023

ESA Build-up phase(Segments 1 + 2)

EU Operational programme

GMES Init-Ops

2011 20152012 2013 2014

EU-only funding.Approval expected in 2013.Funding request based upon ESA Long Term scenario.ESA-EC agreement to be settled.

ESA-EC agreement approved by PBEO in March 2011.Joint and EC-only funding.

On-going.PDGS relies on joint ESA and EC funding.PDGS developments on-going.



GMES Sentinel Satellite Schedule

2013

Sentinel 1 –

SAR imagingAll weather, day/night applications, interferometry

2013

Sentinel 2 –

Multi-spectral imagingLand applications: urban, forest, agriculture,..Continuity of Landsat, SPOT

2013

Sentinel 3 –

Ocean and global land monitoringWide-swath ocean color, vegetation, sea/land surface temperature, altimetry

2019

Sentinel 4 –

Geostationary atmosphericAtmospheric composition monitoring, trans-boundary pollution

2020+

Sentinel 5 –

Low-orbit atmosphericAtmospheric composition monitoring(S5 Precursor launch in 2014)



Satellite Status: Sentinel-1


Sentinel-1 Four nominal imaging operation modes (SM, IW, EW, WV)

Duty Cycle: Max 25 min in HR mode per orbit in HBR mode & rest of the orbit in LBR

Downlink time: Max of 30 min per orbit (with 20 consecutive min)

Sun synchronous orbit at 693 Km mean altitude

12 days repeat cycle

7 years design life time, consumables for 12 years

• Satellite Preliminary Design Review• Q2 2008

• Satellite Critical Design Review• Q2 2010





• Satellite Preliminary Design Review • Q4 2008

• Satellite Critical Design Review• Q4 2010

Sentinel-2 Pushbroom filter based multi spectral imager with 13 spectral bands (VNIR & SWIR)

Spatial resolution: 10, 20 and 60 m

Field of view: 290 km

Average data supply (compressed) of ~17minutes per orbit at 490Mbps

Downlink time: Average of 16 min per orbit

Sun synchronous orbit at 786 km mean altitude

10 days repeat cycle






• Satellite Preliminary Design Review: • Q4 2008

• Satellite Critical Design Review• Q2 2011 => On-going

Sentinel-33 main instruments: Ocean and Land Colour Instrument (OLCI), a spectrometer imaging in pushbroom mode with an across-track scan, strongly inherited from MERIS Sea and Land Surface Temperature Radiometer (SLSTR), a conical imaging radiometer with a dual view (near-nadir and oblique) capability, presenting design heritage from the AATSR SAR Radar ALtimeter

(SRAL) instrument, a dual-frequency altimeter, derived from the Alcatel Alenia Space line of products such as SIRAL of Cryosat

Downlink time: Average 6 min / Orbit

Sun synchronous orbit

at 814.5 km (with local time at desc. node at 10:00 a.m)

Polar orbit

to achieve near-complete Earth coverage with 27 days repeat cycle




GMES Sentinel Satellite Schedule

• Nominal launch schedules for “A” units:

– Sentinel-1A May 2013

– Sentinel-2A November 2013

– Sentinel-3A August 2013

• Launch schedules for “B” units:

– “B” units to be ready for launch 18 months after launch of “A” units.



GMES Ground Segment Status

• Current initial operations based on data from GMES Contributing Missions provided to GMES Core Services.

• Coordinated Data-access System (CDS) v2 installation and deployment expected soon.

• Three PDGS development contracts (S-1, S-2, S-3) and other GS development contracts starting/on-going.

• Sentinel Data Policy approved by ESA PBEO – EC governance process on-going.

Baseline is “free and open” for sentinel data.



GMES Ground Segment Requirements

• Sentinel Ground Segment and Operational Requirements have been derived from:

– The mission requirements documents (EC).

– The data warehouse process (EC).

– The space segment design and constraints.

– The programmatic agreements (e.g. with EUMETSAT for S-3, S-4, S-5).

– The Programme declaration (e.g. giving sentinel data access to GMES and for national use of Member States).



GMES Space Component Operations Concept



GMES Ground Segment And Data Access

FOS

Sentinel-1

TT&C Stations

Sentinels

PDGS

Acquisition Stations

GSC Coordinated Data Access System

TM/TCISPsSentinel-3

GMES Collaborative Ground Segment

Collaborative Centre A

GSCCore Ground Segment

GCM GS

GCM GS

GCM GS

GCM GS

GCM GS

GCM GS

GMES Con

tribu

ting M

ission

s (ESA,

EUMETSAT,

Nation

al mem

ber-s

tates

mission

s, etc

.)

GCM GSCollaborative Centre A





GMES Space Component

EO Data UsersEO Data Users

GMES Services Users

EDRS

GSC data

Request

GSC data

Provision

GMES Service Entities



Overview Of GMES Ground Segment

E. Monjoux



Presentation Objectives

• Provide an introduction on the Sentinel -1, -2, -3 Ground segment implementation Logic

• Provide an overview of the Sentinel -1, -2, -3 Ground segment Implementation Status and next phases schedule




GSC Ground Segment

• The Coordinated Data access System (CDS) for the coordination of the data flows for the GMES Services

• The Sentinel missions core ground segments :

– Satellite control (Flight Operation Segment: FOS)

• ESOC for S-1 and S-2, EUMETSAT for S-3

– Sentinel core Payload Data Ground Segment (PDGS)

• 3 distinct PDGS, with EUMETSAT responsible for the S-3 Marine operations

• External operational interfaces:

– Sentinel Satellites

– EDRS satellite and ground segment

– GMES contributing mission (GCMs) ground segment

– Potential collaborative elements

– GMES Services & Non-GMES Services usersSentinels Facilities Info Day, ESRIN, 12 April 2011



Coordinated Data Access System

• CDS services:

– GSCDA Advertisement

– GMES Services Support Desk

– GMES Emergency Satellite Tasking

– Coverage Area Monitoring

– Service Performance Reporting

– Coordinated Quality Control

– Product archiving when necessary

•

with features like:

– On-line client for data access

– Single Sign On

– Standardized (HMA) interfaces for catalogue and ordering



Coordinated Data Access System – Operations

• In operation since 2009

– Operations are based on collection of products (data sets) from contributing missions (GCMs) defined according to user needs and mission/sensors possibilities

– Access managed according to licence terms and registration

– New systems for operational streamlining and integration of heterogeneous ground segments being put in place (Q2 2011)

• The Sentinels PDGS products will be integrated into the relevant data sets

Evolution of total number of products archived in catalogue

~150 operational GMES Services users

~60 orders / month

131 datasets

~10 data providers

>30 missions



Sentinels PDGS Implementation: Building Blocks

• The PDGS is made of :

– Antenna and front end processing

– Near real time or off-line processing and archiving

– Dissemination and circulation

– Quality control & mission performances

– Mission planning & Ground Segment control

• Relying on supporting layers or interfaces for:

– Security, Network, User front desk, auxiliary data providers operations Sentinels Facilities Info Day, ESRIN, 12 April 2011



Sentinels PDGS Implementation Drivers

• Ground Segment technology challenges

– Sentinels mission represents a HUGE amount of data

• Missions and Program requirements challenges

– Systematic processing of all received data

– Open data policy

– Operational continuity for GMES Services (e.g. ENVISAT continuity)

• Technical constraints drivers

– Decentralised

network of centres

• Project organisation drivers

– asynchronous schedules between satellite projects




Sentinels PDGS Implementation Drivers: A Huge Amount Of Data


ENVISAT reference



Sentinels PDGS Implementation Plan: Some Logic Drivers

• Consolidation of requirements

– Operation concepts, Product lists

• Identification of sub-systems commonalities

– Multi-Sentinel Front End Processor

– Multi-Missions data access front-end

• Reuse of existing & suitable operational capabilities

– X band acquisition

• Identification of critical elements and dependencies

– Satellite schedule

– Satellite interferences management




one 100km x 100km tile

Sentinels PDGS Implementation Plan: Production Baseline Highlight


Stripmap

Mode (SM)400 Km

400 Km

250 Km

200

Km100

Km

80 Km

2 3o 3

6o

S1

S6

Interferometric

Wide Swath

Mode (IW)

Extra Wide

Swath Mode

(EW)

Wave Mode (WV)

1 9o

4 6o

3 0o

4 5o

1 9o

4 6o

• Major achievement in 2010 to confirm the production baseline through the GSC operation concept

– Product definition baseline consolidated in terms of algorithms, format and timeliness

• Next step:

– User documentation, test data one to two years before launch



Sentinels PDGS Implementation Plan: Procurement Highlights

• Early start critical elements

– S-1 Operational processor, Multi-

Sentinel Front End Processor, algorithms spec.

• Reinforce mission end-to-end view through strategic grouping of the Ground Segment integration tasks

– Sentinels -1, -2 -3 PDGS core contracts

– Implementation of the reference platform

• Combined procurement of potentially synergetic operational capabilities

– Centres

procurements

• Optimise procurements schedule according to inter-dependencies

– WAN procurement Sentinels Facilities Info Day, ESRIN, 12 April 2011



Sentinels PDGS Schedule Status: Procurement Highlights

• PDGS Core

– S-1 KO: Q2 2010

– S-1 PDGS Preliminary Design Review: Q4 2010

– S-3 KO: Q3 2010

– S-3 PDGS Preliminary Design Review: Q1 2011

– S-2 KO: Q2 2011 (TBC)

• S-1 Operational Processors : CDR Q2 2011, S-1 Mission Planning : KO Q1 2011, S-1 Mission Performance Tools: KO Q2 2011

• S-2 Algorithms : DDR Q1 2011, S-2 Mission Planning : ITT Q1 2011

• S-3 Mission planning (EUMETSAT): ITT Q2 2011

• Multi-Sentinel Front End Processor: CDR: Q1 2011

• Next Generation Earth Observation data access front end (ngEO): KO Q1 2011




Sentinels PDGS Integration Plan


Sub-systems implementation Mission specific:

•S-1 IPF•S-3 Mission planning •Production controller…

Multi-Sentinel specific

•DFEPMulti-Missions

•ngEO

Sub-systems implementationMission specific:

•S-1 IPF•S-3 Mission planning•Production controller…

Multi-Sentinel specific

•DFEPMulti-Missions

•ngEO

Reference platform

integration

Reference platform

integration

Centres selection and preparation

Centres selection and preparation

Commissioning configuration

Deployment End to end testing

Commissioning configuration

DeploymentEnd to end testing

Operational Configuration

Incremental deployment & integration

Operational Configuration

Incremental deployment & integration

Reference platform Sentinel-1 : First elements being integrated this month



Presentation Highlights

• A HUGE data volume to be considered: EVERYWHERE, ALL THE TIME

• 3 payload data ground segments supporting 3 different missions.

• A single industrial integration approach per PDGS fostering all implementation tasks through the setup of a representative reference platform.

• Incremental deployment and integration into operational network of centres according to exploitation needs.

• Complex implementation plan with critical paths due to procurements inter-dependencies.

The good coordination with the satellite, FOS teams and with the PDGS industrial partners allow us to be in-time to start the next

procurement phase.Sentinels Facilities Info Day, ESRIN, 12 April 2011



Scope Of Procurements

G. Mason



Scope Of The Procurements – Overview

• The core ground segment for the acquisition, processing, dissemination and archiving of data from the Sentinel series of satellites will consist of:

– X-band Acquisition Stations including Near Real-Time (NRT) processing;

– distributed off-line Processing and Archiving Centres (PACs);

– Mission Performance Centres (MPCs) to check data products quality and mission performances;

– data circulation and dissemination network;

in addition, mission planning, overall monitoring, and maintenance of the various reference platforms will be performed at ESRIN.

• The Sentinel-specific Payload Data Ground Segments (PDGSs) will be deployed at both the acquisition stations for NRT processing and the offline PACs.



Scope Of The Procurements – Overview

Deployment, Integration &

Validation

Deployment, Integration &

Validation

ImplementationImplementation

SpecificationsSpecificationsSentinels & Data Access - Requirement & Operation concepts & procurement plans

(2008-2009)

Systems & Sub-System procurements(PDGS Core, CDS, Multi-sentinels or

specific elements) (2010-2011)

Facilities site preparation

(2012)

Deployment & testing

(2012-2013)

Facilities & Network procurements(2011-2012)

Routine operations(2014-)

Commissioning operations

(2013-2014)

• Procurement of the ground segment facilities and network is part of the overall GMES ground segment development:



Scope Of The Procurements – Approach

• Each of the four procurements will be performed via open ITT.

• Each of the procurements will cover (under existing ESA / EU and EU GIO funding):

– initial site preparation and deployment activities;

– support to pre-launch ground segment integration, testing and rehearsals;

– operations during the commissioning phase for each A unit satellite;

– build-up of full network of facilities in a staggered approach.

• In addition, options will be requested (under future EU GMES Operations budget) for:

– annual routine operations (up to 5 years of routine operations).




• The Stations, PACs and associated network connectivity will be deployed in a staggered approach to meet the actual satellite launch schedules and needs of Commissioning Phases.

• Operations during the Satellites Commissioning Phases will involve a sub-set of the Stations and PACs to avoid possibility of multiplying problems and diluting resources.

• For the Operations Phases, the procurements will be based on service contracts with service level agreements and key performance indicators.

• Options for Routine Operations to be exercised as the EU funding is confirmed and dependent on the contractor service performance.




• ESA’s overall approach is to outsource the GMES operations activities as much as possible, with ESA providing the overall coordination and management.

• This requires experienced contractors who are responsible and motivated to provide the required operational services autonomously.

• GMES funding is not unlimited and the level of operations funding from the EU still needs to be confirmed – both development and operations costs need to be affordable.



Scope Of The Procurements – Contracts

• Stations:

– Network of 6-7 acquisition stations required.

– Several separate contracts will be placed.

• PACs:

– 2 PACs for Sentinel-1, 2 PACs for Sentinel-2, 3 PACs for Sentinel-3.

– Some PACs may be collocated.

– Several separate contracts will be placed.

• MPCs:

– 1 MPC for each Sentinel.

– Three separate contracts (one for each MPC) will be placed.

• Network:

– Single contract will be placed.



Scope Of The Procurements – Contracts

• Any station in the selected network will have to be capable of acquiring data from any Sentinel satellite (multi-Sentinel Demodulator and Front End Processor, DFEP, to be provided by ESA).

• Bidders will be requested to provide separately costed options for each of the Sentinel specific activities, and to identify the cost savings to ESA in the event that more than one Sentinel specific option is selected (e.g. S-1 NRT and S-2 NRT to be costed separately and also identify cost savings if both selected).

• ESA reserves the right to select individual Sentinel specific options from any given bid (e.g. S-1 PAC and S-2 PAC proposed, but only S-1 PAC selected by ESA).



Scope Of The Procurements – EDRS

• The European Data Relay Satellite (EDRS) project has been approved by ESA’s Joint Board on Communication Satellite Programmes (JCB).

• The EDRS programme will consist of 1 in-orbit, geo-stationary satellite (EDRS-C) and a piggyback payload (EDRS-A) providing:

– LEO satellite to EDRS satellite to ground data transmission;

– ground to EDRS satellite to ground data dissemination (option).

• The Sentinel-1 and 2 satellites will be equipped with Laser Communication Terminals to allow data transfer to the EDRS satellites.



Scope Of The Procurements – EDRS

• The services from the EDRS satellites will be provided by Astrium Services as a commercial service.

• Discussions are currently on-going between ESA and Astrium Services regarding the use of EDRS for the Sentinels.

• EDRS is not included in these current Facilities procurements.

• The network of selected X-band ground stations needs to provide the capability to acquire all data from each of the Sentinel satellites.

• EDRS capability will be added at a later stage to include EDRS Ka-band acquisition stations.



Scope Of The Procurements – Schedule

• Schedule for Stations:

– ITT release: end April, early May 2011.

– Contract Kick-Offs: Q4 2011.

• Schedule for PACs:

– ITT release: early May 2011.


• Schedule for Network:

– ITT release: Q4 2011 / Q1 2012.

– Contract Kick-Off: Q2 / Q3 2012.

• Schedule for MPCs:

– ITT release: Q4 2011 / Q1 2012.




Common Issues – Phasing & Review Logic

• The phasing / logic for the Stations and PACs will be as follows (even if a given Station or PAC is deployed at a later stage):

Site Preparations

Deployment / Test

Commissioning Ops.

Routine Ops.

Kick-Off

SRR

ORR

RORR

SPR

Initial Contract Options for Routine Operations

SRR = Site Readiness ReviewORR = Operations Readiness ReviewRORR = Routine Operations Readiness ReviewSPR = Service Performance Review (annual)



Common Issues – WAN Connectivity

• ESA will provide the Wide Area Network (WAN) services as a CFI to the Stations, PACs and a single location for each MPC.

• Facilities located in mainland Europe / UK shall interconnect to the WAN service provider at the Facility or its proposed point of presence (PoP).

• Facilities not located in mainland Europe / UK shall interconnect to the WAN service provider at a major commercial hub and include in the proposal:

– one time costs and monthly recurring costs for the WAN service from the Facility location to the PoP,

– contract terms and conditions,

– possibility to transfer, as an option, the contract to the WAN service provider.



Common Issues – LAN Infrastructure

• The Contractor shall be provide a Multi-Sentinel Local Area Network (LAN) to host the Sentinel systems and to provide access to the ESA Wide Area Network (WAN) (CFI).

• The Multi-Sentinel LAN shall provide DMZ and internal LAN access functions via multiple 10 Gbit interfaces.

• ESA will provide a reference architecture and detailed technical requirements document.

• The Contractor shall provide an architectural design document, implementation plan and after deployment demonstrate compliance through acceptance tests.

• The Contractor shall operate the LAN as a managed service with a target availability of 99.9%.



Common Issues – LAN Infrastructure

• Multi-Sentinel high level logical topology:



Acquisition And NRT Stations

E. Doyle



Acquisition And NRT Stations

• Sentinel Downlinks

– Contacts

– Link budget

• Core Ground Stations Scenario

• Scope of Ground Station Contracts

• Contractor Deliverables

• ESA CFI’s

• Site Requirements

• Acquisition Requirements

• NRT Production Requirements

• Support Requirements



Acquisition And NRT Stations Sentinel Downlinks

• Sentinel 1 and 2 satellites require more than one contact per orbit to downlink the global on-board data, whereas Sentinel 3 requires one contact per orbit.

• To provide full coverage for all the Sentinels therefore, a network of 6 or 7 core ground stations (depending on locations) is required to receive all the global data and to provide some near real time coverage over Europe.

• To ensure adequate flexibility any station must be available to support downlinks from any of the Sentinel satellites.

• Same X-band downlink frequencies / different repeat cycles:

– (S1 / S2 / S3 – 12 / 10 / 27 day).

• Acquisition conflicts (1 – 1.5 degrees) managed by ESA using predefined slots.

• Approx 560 Mbit bit rate / 8PSK / 290 MHz of bandwidth required.



Acquisition And NRT Stations Sentinel Downlinks –

Contacts

Satellite Contacts / Orbit Contacts / Day Contacts / Month

Satellite-1A 2 -4 ≈42 ≈

1,275

Satellite-2A 2-4 ≈

42 ≈

1,275

Satellite-3A 1 14 ≈

426

Total ≈

7 ≈

98 ≈

2,980

• Number of X-band contacts required for Sentinel A units (B units separated by 180 degrees).



Acquisition And NRT Stations Sentinel Downlinks –

Contacts

SatelliteLocation in Latitude (degrees)

GS_30 GS_40 GS_50 GS_60 GS_70 GS_80

Sentinel 1A 4.08 4.66 5.83 8.75 10.83 14.58

Sentinel 2A 4.30 5.00 6.20 9.80 11.00 14.30

Sentinel 3A 4.30 5.04 6.22 9.82 11.00 14.26

• Average number of theoretical Sentinel A unit contacts per day (5 degree elevation mask).



Acquisition And NRT Stations Downlink Information

• Detailed link budgets are provided in the Space-to-Ground ICDs for each mission (to be included in ITT package).

• Downlink information:

• The required minimum G/T in Free Space = 30.2 dB/K.

• The required minimum effective G/T for a given station requires addition of atmospheric and polarisation losses (location dependent) and pointing losses for the antenna system, with a minimum availability of 99.4%.

Sentinel-1 / 2 / 3

Downlink frequency f1 8095 MHz

Downlink frequency f2 8260 MHz

Maximum Bandwidth 145 MHz

Link Availability Requirement ≥

99.4%



Acquisition And NRT Stations CGS Operational Scenario

• Sentinel acquisition requests provided from Mission planning.

• Core Ground Station acquires Sentinel (Real Time or Memory dump) data downlinks.

• Demultiplexes and stores the ISP data.

• Instrument Source Packets (ISPs) provided to L0 processor (on / off site) and to other parties (ESOC, Eumetsat (S-3)).

• L0 data circulated to PACs.

• NRT L1 / L2 production performed (Real Time, Memory dump) and made available to users and PACs.



Acquisition And NRT Stations Scope of Ground Station Contracts

• To provide the site infrastructure (including Antenna, computer rooms, etc.) needed for the selected core ground systems.

• To provide and operate the Multi-Sentinel LAN at each facility.

• To support ESA and its industry during the deployment and integration phases.

• To provide Acquisition / Production services in commissioning and (optional) routine operations phase.

• To provide the necessary System and Database management services.

• To perform monitoring and control requirements.

• To support the local logistics (maintenance, configuration management, inventory management, etc.).



Acquisition And NRT Stations Contractor Deliverables

• Site infrastructure (including Antenna, computer rooms, etc) needed for the selected core ground systems.

• Local Area Network infrastructure.

• Network point of presence.

• Support to integration / Ground Segment Operational Validation (GSOV).

• Support to Commissioning Operations.

• Acquisition / Production service in Commissioning Operations and (optional) Routine Operations phases.

• Local system management / logistics.

• Monitoring and control.



Acquisition And NRT Stations ESA CFI’s

ESA provided Customer Furnished Items (CFIs):

• Multi-Sentinel Demodulator and Front End Processor (DFEP).

• Separate S1 / S2 / S3 Core NRT production / distribution systems.

• Wide Area Network (via separate ITT), up to agreed PoP.

• Anomaly tool.



Acquisition And NRT Stations Site Requirements

• Preparation of the site Sentinel Core systems (power, computer room / ops environment, security, etc).

• Preparation and testing of Multi-Sentinel LAN (10 Gb) to host the DFEP and Core PDGS systems.

• Support the site readiness reviews performed by ESA industrial teams.

• Prepare and test interface points (intermediate frequency, network).

• Generate and maintain ICDs for accommodation of systems for selected Sentinel missions.



Acquisition And NRT Stations Acquisition Requirements

• Objective is to set up a set of facilities to provide Acquisition Service.

• Support acquisition of any of the Sentinel satellites inside assigned horizontal mask (station slots).

• A Multi-Sentinel Demodulator and Front End Processor (DFEP) shall be provided as ESA CFI.

• DFEP provides Instrument Source Packets (ISPs) to PDGS L0 ingestion node.



Acquisition And NRT Stations CGS NRT Processing Requirements

• Ensure ISPs streamed to relevant Sentinel L0 ingestion nodes.

• Perform higher level production in required time frame and circulate to users (L1, L2) and PACs (L0, L1, L2).

• Sentinel-1:

– L1: NRT 10m / NRT 1h for direct downlink, NRT 3h from memory;

– L2: NRT 10m / NRT 1h for direct downlink, NRT 3h from memory.

• Sentinel-2

– L1: NRT 1h (Majority) / Remainder 100m;

• Sentinel-3:

– L1: NRT 3h from sensing;

– L2: NRT 3h from sensing (Land).



Acquisition And NRT Stations Support Requirements

Support needed shall vary depending on the phase: deployment, pre- operations, routine operations.

• Logistics (Normal Working Days, NWD; Normal Working Hours, NWH):– Packing/Unpacking shipment of goods / customs;

– Configuration items handling.

• System / Database Management and hardware Maintenance (NWH, NWD):

– Preventative maintenance;

– Level 1 and Level 2 support;

– Backups / restores.

• General operations (NWD, NWH):– Software upgrades, procedure updates.

• Call out.



Processing And Archiving Centres (PACs)

N. Houghton



Processing And Archiving Centres

• Overview of PACs/LTAs

• Site Requirements (PDGS)

• Scope of Contract

• Deliverables

• Operational Scenario

• LTA Requirements

• Data Volumes

• Support Requirements

• Reprocessing Scenario



Processing And Archiving Centres Overview of PACs/LTAs

• Two PACs for Sentinel-1 in separate locations.

• Full and redundant Long Term Archives (LTAs) collocated with Sentinel-1 PACs.

• Same as the above for Sentinel-2.

• Sentinel-3: three PACs:

– OLCI (L0, L1 and Land L2 products);

– SLSTR (L0,L1 and Land L2 products);

– SRAL (L0, L1 and Land L2 products).

• For S-3, backup of L1 products in EUMETSAT.

• Sentinel-3 synergy products to be generated at additional centre and archived in OLCI and/or (tbc) SLSTR LTAs.



Processing And Archiving Centres Site Requirements

• Preparation of the site Sentinel Core systems (power, computer room / ops environment, security, etc).

• Preparation and testing of Multi-Sentinel LAN (10 Gb) to host the Core PDGS systems.

• Support the site readiness reviews performed by ESA industrial teams.

• Prepare and test interface points (network).

• Generate and maintain ICDs for selected Sentinel missions.

• Establishment of LTA.



Processing And Archiving Centres Scope of PACs

Contracts

• To provide the site infrastructure needed for the selected core ground systems.

• To provide and operate the multi-Sentinel LAN at each facility.

• To support the deployment and integration phases.

• To support the commissioning ops and routine ops phases.

• To provide Production services in commissioning and (optional) routine operations phase.

• To provide LTA Service (to be proven in Deployment phase).

• To provide the necessary System and Database management services.

• To perform monitoring and control requirements.

• To support the logistics (maintenance, configuration management, inventory management, etc).



Processing And Archiving Centres Contractor Deliverables

• Site infrastructure.

• Local Area Network infrastructure.

• Network point of presence.

• Support to integration / GSOV.

• Support to Commissioning OPS.

• Production service in Commissioning and (optional) Routine operations phase.

• System management / logistics.

• Monitoring and control.



Processing And Archiving Centres ESA CFIs

ESA provided Customer Furnished Items (CFIs):

• Hardware and Software for the PACs.

• IPFs.

• ICDs.

• Operational Procedures.

• Documentation.

• Anomaly Tool.



Processing And Archiving Centres PACs/LTAs

Operational Scenario

• L0 received from CGS.

• Concatenation of L0 segments if necessary.

• IPF generates L1/L2.

• All product generation systematic (except S1 to support CHARTER).

• Short Term/Medium Term Archives (STA/MTA) store products for fixed time period (typically a few months).

• Rolling Archive stores products to be made available to users (typically a couple of weeks).

• Products (L0/L1/L2) stored in Long Term Archive (LTA).

• LTA functions are storage and retrieval.

• User interface through ngEO.



Processing And Archiving Centres PAC Operational Activities

• Operations required Normal Working Hours.

• Weekend/Public Holiday call out (optional package)

• Checking of logs.

• Recovery of failed production.

• Opening anomalies (tool to be provided).

• Bulk Dissemination/Transcriptions.

• Media Dissemination (hard disk).

• Ensure data is archived.

• LTA Service.



Processing And Archiving Centres LTA Requirements

• LTA Provided as a service (limited CFIs provided).

• LTA Storage and retrieval only (no processing).

• ESA will supply limited level of CFIs including ICDs.

• Bidder will build interface to their chosen solution.



Processing And Archiving Centres Data Volumes for LTA

• S1:

– LTA L0: 321 TBytes/Year L0/1/2: 1076 TBytes/Year

• S2:

– LTA L0: 405 TBytes/Year L0/1/2: 991 TBytes/Year

• S3:

– OLCI LTA: L0: 48 TBytes/Year L0/1/2: 238 TBytes/Year

– SLSTR: L0: 24 TBytes/Year L0/1/2: 270 TBytes/Year

– SRAL: L0: 26 TBytes/Year L0/1/2: 31 TBytes/Year

– Synergy Products for OLCI/SLSTR: L1/2: 442 TBytes/Year



Processing And Archiving Centres Support Requirements

Support needed shall vary depending on the phase: deployment, pre-

operations, routine operations.

• Logistics (NWD, NWH):

– Packing/Unpacking shipment of goods / customs (NWD, NWH),

– Configuration items handling.

• System / Database Management and Hardware Maintenance:

– Preventative maintenance,

– Level 1 and Level 2 support

– Backups / restores.

• General operations (NWD, NWH):

– Software upgrades, procedure updates.

• On Call support as an option.



Processing And Archiving Centres Reprocessing Scenario

• Bidder to demonstrate ability

to be able to set up and operate reprocessing chain on PAC infrastructure.

• ESA will provide IPFs and ICDs as CFI.

• Actual reprocessing to be addressed as a delta service.



Mission Performance Centres (MPCs)

Ph. Goryl



The Mission Performance Centre cover the following functions:

Calibration

– the objective of which is to update on-board and on-ground configuration data in order to meet product quality requirements. Calibration is performed by analysing the calibration data acquired by the instruments or the calibration data processed in the vicarious calibration program.

Validation

– the objective of which is to assess, by independent means, the quality of the data products derived from the system outputs. Validation functions provide input for algorithm evolution and processor upgrades.

Quality Control – the objective of which is to monitor the status of the spacecraft (payload and platform) and to check if the derived products meet the quality requirements along mission life-time.

Data processors (prototypes) and QC tools corrective and evolutive

maintenance – whose objective is to manage the updates of the processors and auxiliary files in order to ensure the overall quality targets.

End-to-end system performance assessment – whose objective is to detect anomalies at system-level and provide high-level performance figures on the overall mission performance.

Procurement Scope



Quality Controland

Coordination

Quality Controland

Coordination

Calibration, Validation and

Algorithms Evolution

Calibration, Validation and

Algorithms Evolution

Cal/Val Data Provision

Cal/Val Data Provision

Core Ground Stations

PACsPACs

Payload Data Management

Center

Payload Data Management

Center

NetworkInterfaces: plans, reports, software packages & configuration…

Network or m

edia

Interfaces: Products

Networ

k

Inte

rface

s:

Prod

ucts

& repo

rts

Mission Performance Functional Breakdown

Reports

Reports

& data

PDGS

products &

data & reports

Reports & data

Mission Performance Functions and Interfaces

Mission Performance

Manager



Data from other

Missions for Cal/Val

Data from other

Missions for Cal/Val

In-SituCal/Val

Campaigns

In-SituCal/Val

Campaigns

Expert Support Laboratories

(ESL) for Cal/Val and

characterisation activities

Expert Support Laboratories

(ESL) forCal/Val and

characterisation activities

Core Infrastructure

Core Infrastructure

PermanentC al/Val Infra-

structure

PermanentC al/Val Infra-

structure

Expert Support

Laboratories(ESL) for

algorithm evolution activities

• The Mission Performance activity is coordinated through a data access point concentrating PDGS data flows interface: The MPC Core Infrastructure.

• Mission Performance Centre (MPC) is used to refer to the whole set of activities and infrastructure.

* For Sentinel 3: MPC breakdown might be adapted in line with the Sentinel-3 Mission management Concept to be agreed between ESA & EUMETSAT.

Mission Performance Centre (MPC)

Routine Quality Control

(collocated with core

infrastructure)

Routine Quality Control

(collocated with core

infrastructure)



Each MPC will be composed of a core infrastructure and distributed

entities that will provide expertise and data for Cal/Val activities and

algorithms evolutions.

Single procurement process for the selection of the 3 Sentinel Mission

Performance consortiums.

The MPC procurements is aligned with the program phases

Phase 1: MPC setup.

Phase 2: Operation for the commissioning of the A unit.

Phase 3: Transition into a service provider configuration for the

exploitation phase.

MPC Procurement Approach



The MPC procurements is aligned with the program phases

Phase 1: MPC setup

Core centre integration with (PDGS interfaces, Cal/Val data

providers, ESLs,…)

Integration of CFI or reused tools

Phase 2: Operation for the commissioning of the A unit

Infrastructure operations

CAL/VAL operations

Definition of complete MPC operations based on Service Level

Agreement approach

Phase 3: transition into a service provider configuration for the

exploitation phase.

MPC Phasing Approach



PDGSPDGSEngineering

Framework (Task 2)

Calibration and Validation Data

Provision(Task 5)

• Provide cal/val data from permanent infrastructures or field/airborne campaigns to the ESL teams.

Expert Support Laboratories (ESL)

(Task 4)•Maintain the processing algorithms documentation & the prototype processors. •Propose and implement algorithm changes.•Perform calibration, validation (using cal/val data) and instrument characterisation activities.

Core Infrastructure

(Task 1)

Routine QC and Coordination (Task 3)

•Check routinely the production reports. •Check the completeness & quality of the data (sampling approach).•Maintain the configuration of the operational processors and QC tools.•Respond to user issues channelled through the ESA EO multi-mission or the GSC DA helpdesk (incl. EUMETSAT help desk)•Support to MPC set up.

Tasks are refined in the SOW according to the deliverables expected in the different phases of the MPC project (e.g. operations of infrastructure versus service provision).

For Sentinel 3, MPC SOW Tasks Decomposition might be adapted once the Sentinel-3 Mission management Concept has been agreed between ESA & EUMETSAT.

Generic MPC SOW Tasks Decomposition



SOW based on a generic tasks decomposition that allows, whenever

possible, proposals to maximise synergy and participation to

consortium in different roles according to mission expertise.

Each task is refined capturing mission and instruments specificities.

Phase 1 and Phase 2 are in scope of the procurement while options will

be required for Phase 3.

Estimated split of effort for S-1 : S-2 : S-3 is approximately

23% : 23% : 54%.

Options shall be provided for a yearly based service

covering MPC

operations at the end of the commissioning.

Best practices will be identified on case by case basis in the ITT.

MPC ITT Highlights (1/2)



Proposals shall be mission-based and shall cover all tasks for a given

mission.

No participation exclusion principles between two Sentinel MPC.

In case the same task is proposed for different missions or in different

consortium the task proposal shall be part of every relevant proposals.

Synergies between proposals shall be identified as an option.

Task 2 shall be optional, the agency will evaluate the possibility to reuse

one proposal as a CFI for other MPCs.

MPC ITT Highlights (2/2)



Sentinel specific Mission Performance tools provided as ESA CFI:

o Developed (as Best Practices) within the Sentinels PDGS Core contracts. o Deployed and integrated at the MPC as part of the Sentinels PDGS AIV activities.o WAN.

In addition, other elements will be provided by ESA as CFI to the MPC:

o Prototype and/or stand-alone IPF.

Additional tools might be needed in order to complement ESA CFIs.

Details will be provided as part of the ITT.

MPC Tools



The prime contractor will be required to have experience and capacity to foster ESL teams.

For Sentinel-3, the MPC is a procurement/development managed by a ESA/EUMETSAT joint team. EUMETSAT expertise and in-house facility will also be used for the Sentinel-3 mission and should complement the MPC Sentinel-3. The location of the Sentinel-3 MPC coordination center will be decided by the joint team.

MPC Procurement TasksSpecific Requirements



Reference platform (Core PDGS Contract)Reference platform (Core PDGS Contract)

Other Facilities ContractsOther Facilities Contracts

Inter-Centres Network ContractInter-Centres Network Contract

Mission Performances Centres

CFI: MP Tools & Processors

Operational interfacesintegration Operational

network integration

Generic MPC Procurement TasksMPC Dependencies

Operational Processors Development

Mission Performance Tools

Acquisition Stations Network

Processing and Archiving Centres



Sx-A Launch Sx-B LaunchMPC

selection

Sat.Sx-A CP review

Support to ESA CFI tools/HW deployment & integration for Sx-A

Support to ESA CFI tools/HW deployment & integration for Sx-A

Support to AIV for Sx-ASupport to AIV for Sx-A

Support to Sx-A Satellite CP ops.

Support to Sx-A Satellite CP ops.

Sx-A MP service operationsSx-A MP service operations

Support to Sx-B Satellite CP ops.

Support to Sx-B Satellite CP ops.

Support to Sx-A/B GS CP ops. Support to Sx-A/B GS CP ops.

Demonstration of site readiness for deployment

Sx-A/B MP service operations

Sx-A/B MP service operations

Sat.Sx-A CP review

Support to Sx-A GS CP ops. Support to Sx-A GS CP ops.

Baseline contract activitiesBaseline contract activities

Optional contract activitiesOptional contract activities

Progressive PDGS system build-up with several releases up to end Sat. CP

Preparation of CP calibration/validation activities starts before launch, with Sentinel mission dependent schedule.

Support to Satellite CP activities as per Satellite CP Plan

Sx-A Phase 1Sx-A Phase 1 Sx-A Phase 2 Sx-A Phase 3Sx-A Phase 3

MPC Activities High-Level Schedule



ITT end 2011 / beginning 2012.

KO estimated Q2/Q3 2012.

PGDS Tools Integration / Tools Development / System Testing / Interface testing: Rehearsal: Q1 2013.

Commissioning phase review: S1: Launch + 3 months S2: Launch + 3 months S3: Launch + 5 months

Gradual effort is planned: Low level for the 6 first months – document review / preparation/procedure. Medium Level during the integration/testing phase. High Level during the commissioning phase.

MPC Procurement Schedule



Phase 1:• Reports: Integration phase: AIV, OSV report, MPC commissioning phase plan, procedure.• Mission Phase-E2 preparation documents (Phase E2 Cal/Val plan).

Phase 2:• Reports: Commissioning phase and phase E2: technical note, daily report, cyclic report, validation

report, calibration report, anomaly report, (integration report, acceptance and testing report, daily reports, cyclic reports, validation reports, calibration report, anomaly report, Technical Notes, user service request, etc.)

Phase 3:•Product handbook maintenance.•Algorithm (ATBD/DPM/IODD/TDS) maintenance, prototype maintenance and evolution (phase E), product specification maintenance.•QC tools configuration.•Calibration database.•Validation database.•ADF/CTI operational provision.•Deliveries quality and deadline will be monitored by KPIs.

MPC Procurement Deliverables



Stations & PACs selection will be completed and location will be identified.

PDGS S1 Mission performance tools V1.

PDGS S3 & S2 Mission Performance tools and operational processors best practices.

Commissioning and CAL/VAL plans will be under preparation.

For Sentinel-3, split of ESA / EUMETSAT roles clarified.

Between now and MPC Invitation-To-Tender



Data Circulation And Dissemination Network

G. Buscemi



Data Circulation And Dissemination Network: ITT Services (1/2)

• The Network will provide telecommunications connection to the GMES Ground Segment Facilities and Centres.

• IP Network based on the state-of-art technology and architecture meeting established security needs.

• The following services will be part of the Data Circulation and Dissemination Network:

– Internet and Intranet interconnection.

– Centralized/distributed Security Services (e.g. Firewall).

– Auxiliary services (DNS, mail relay, NTP).

– Secure Remote Access (e.g. for remote maintenance).

– Possible Hosting/Housing PDGS front-end systems (data distribution servers) and mirroring DMZ in the Internet access points.



• Point of Service (PoP) delivered at the facility.

• WAN Capacity profile aligned to the Sentinels needs (100 Mbps/ 500Mbps/1Gbps).

• Procurement based on Service oriented and Managed elements.

• The services will be regulated by SLAs and measured by KPIs; SLA aligned to the end-to-end Sentinels level of service.

• KPIs will be measured on a monthly basis and associated with a penalty scheme based on service credits.

• Sentinels Integration and Validation activity supported via capacity of the existing Network or via IP/VPN over Internet (IP-SEC).

Data Circulation And Dissemination Network: ITT Services (2/2)



Sentinel Centre: High Level Network Reference Architecture

• Part of the WAN ITT

• Sentinels WAN Access

Internet/WANInternet/WAN



Schedule

• Relevant parts of network to be ready 1 month prior to launch of each Sentinel.

• Planned ITT publication: Q4 2011 / 1Q 2012



Security Requirements for Sentinels Facilities ITTs

G. Buscemi



Security Requirements

• The EOP-G Security requirements are applicable to the Sentinels Facilities, Mission Performance Centres, and Network procurements.



Network and ICT Security Requirements 1/2

• Network and ICT security requirements for the EO PDGS v.1.1

(GMGT-SENE- EOPG-RS-09-0002)

It details the Network and ICT security requirements expected to be followed by the full EO PDGS systems.



• Physical Security:– SEC-580: Non- ESA sites shall install EO systems in a zone compliant to the following requirements:

Locking, ..

• System Security:– SEC-30: A system Security Plan ([RD5]) shall be provided for every machine inside any EO DMZs and

before the TTO.

• Application Security:– SEC-170: The application shall not have any hard-coded root and/or administrative passwords,

and/or url. This applies also to configuration files.

• Applicable Network Architecture:– Compliance with ESA EO PDGS Implementation of the EO network security policy

• Data categorization:– Compliance to a specific Annex (e.g. Internal users account information are considered ESA

Unclassified - For Internal use)

• User classification:– Compliance to a specific Annex (e.g. Operators Definition and right)

• Access control:– SEC-300: Proper Internal Users password policy shall be implemented based on the following

requirements:…

• Secure operations and management:– SEC-370: Operators, Administrators and Maintainers staff will be allowed access to the system,

application, service, data on a need-to-know basis, according to [AD10] (Need-to-know principle).

Network and ICT Security Requirements 2/2



ESA EO PDGS Implementation Of The EO Network Security Policy

• ESA EO PDGS Implementation of the EO network security policy

(v1.2, GMGT-SENE-EOPG- PD-10-0004)

It describes the EO implementation at network level of Ground segment security policy. It defines the security zones, the traffic baseline allowed between the different zones and the policy for the EO ICT services (proxy, NTP, DNS, mail relay, SSO, IDS/IPS)

Each zone has the same level of Network security across facility



Procurement Rules

L. Govaert



Procurement Rules

• The 4 ITTs:

– Acquisition and NRT Stations,

– Processing and Archiving Centres,

– Mission Performance Centres,

– Data circulation and dissemination network,

to be issued implement the Grouped Procurement Proposals approved by ESA’s Industrial Policy Committee in November 2010.



Procurement Rules

• All procurements are jointly funded by ESA and the EC.

• Procurements currently regulated by the First Amendment to the ESA/EC ‘Agreement on the Implementation of the Space Component of GMES’ (“Delegation Agreement”).

• The Second Amendment to this Delegation Agreement includes the GIO funding and is currently in the approval process, which is expected to be completed in the summer.

• Funding available under the First Amendment covers the minimum set-up necessary to support commissioning of the first units of each of the Sentinels.

• The Second Amendment includes provision for completing the build-up of the facilities to achieve full operational capability.

• EU GMES Operations budget (expected to be finalised in 2013) to fund full Routine Operations Phase.

• Breakpoints to be included in the Contracts to reflect availability of funds.



Procurement Rules

• The ITTs will be subject to the same set of Procurement Rules and Procedures:

1. Procurement conducted by ESA or, for some MPC Tasks, by the Prime Contractor (“Best Practices)”.

2. ESA procurement rules and procedures – as amended by the Delegation Agreement – e.g., NO geo-return limitations/targets.

3. New General Clauses and Conditions for ESA Contracts, 2010 (revision 7).

4. The new Tender Evaluation Manual as published on EMITS.

5. But, the old ESA Contracts Regulations will apply, ESA/C (82)111.



Procurement Rules

• The ITTs will be open to ‘economic operators’ from the ESA GSC Participating Member States and States participating in FP7:

– Albania, Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Israel, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, the Former Yugoslav Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey, the United Kingdom, and Canada.

• Both primes and subs must register with ESA as an ESA tenderer - applies also to primes/subs from FP7 countries:

– Industry Portal: http://www.esa.int/esaMI/Industry/index.html

http://www.esa.int/esaMI/Industry/index.html



Procurement Rules

• Intended ITTs for the Stations and PACs already published on EMITS (11.187.02):

– http://emits.esa.int/emits/owa/emits.main

• Will also be published on CORDIS:

– http://cordis.europa.eu/

• ITTs will be published on both EMITS and CORDIS:

– in English

only, in accordance with the Delegation Agreement.

http://emits.esa.int/emits/owa/emits.main

http://cordis.europa.eu/



Procurement Rules

• Submission deadline: minimum 6 weeks

after publication.

• Evaluated by ESA Tender Evaluation Board with EC Observer.

– Evaluation criteria.

– Weighting factors.

– The TEB will make a final recommendation for awarding the contract to the tenderer(s) who offer the most economic and effective employment of the Agency’s resources. This shall be the best combination of the total weighted mark and price.



Concluding Remarks

G. Mason



Concluding Remarks – Schedule

• Schedule for Stations:

– ITT release: end April, early May 2011.


• Schedule for PACs:

– ITT release: early May 2011.


• Schedule for Network:

– ITT release: Q4 2011 / Q1 2012.


• Schedule for MPCs:

– ITT release: Q4 2011 / Q1 2012.




Concluding Remarks

• ESA intends to out-source the GMES ground segment operations as much as possible to industry through these various procurements as service contracts.

• Requires experienced, responsible contractors.

• Procurements in accordance with ESA rules as amended by the Delegation Agreement with EC (no geo-return, FP7 Countries).

• Competitive ITTs.

• Initial contracts to support up to Commissioning Operations, with Routine Operations to be exercised as options.

• EU GMES operations budget and funding level not yet approved.

• GMES funding is not unlimited – costs must be affordable.



Reserve Slides: Products

Products



The data volume of Sentinel-1,-2,-3 A-series production is equivalent to ˜25 * ENVISAT missions with:

Systematic processing of all Sentinels data.System Requirement: 'All observation data acquired by Sentinels shall be systematically processed to a pre-determined product level for each sensor type, archived and made available for on-line access to end-users'.

Highly configurable data driven production, products are available as soon as produced.

No backlog accumulation under nominal conditions

3 main categories of operational latency customized according to mission production and consolidation requirements, acquisition areas and Payload Data Ground Segment resources.

- Real Time: 1h, - Near Real Time: 3h, - Non Time Critical.

Sentinels Production Highlights



(*) Based on GSC Operation concept (**) Validated Level 2 products are progressively available through commissioning and GIO Phase(***) Toolbox for atmospheric corrections provided to support users in L2 production

Sentinel-1** Sentinel-2 Sentinel-3**PDGS Core production* for users dissemination & retrieval

SAR L0 - -SAR L1 SLC MSI L1B OLCI L1SAR L1 GRD MSI L1C SLSTR L1

SAR L2 OCN (waves, wind, radial

velocity)

(***) OLCI Water Color L2

OLCI Land L2SLSTR Water L2SLSTR Land L2

SRAL L2

Synergy/Vegetation L2

Sentinel 1-2-3 Core Ground Segment User Products List



A unique packaging concept adapted to the different missions user communities.

Google EarthMap overlay

XML Schema files for

measurement data and

annotations

XML

ManifestMeasurement

Data

XSD

XML

Schema

SUPPORT

PRODUCT*

PREVIEW

Data(e.g. img.,param.)

Quicklook

Map

HTMLPreview

KML

ANNOTATIONS

XML

Annotations Products metadata

HTML product preview

GeoTIFF

• Format for user delivery or retrieval can be tuned according to user community (e.g. DIMAP).

Sentinels Core Ground SegmentProduct Format



SAR modes and production

The Sentinel-1 SAR features four exclusive imaging modes of operations, with different resolutions and coverage (as illustrated in Figure …):

•Interferometric Wide Swath (IW),•Extra Wide Swath (EW),•Strip Map (SM) with 6 possible incidence angles,•Wave (WV).

400 Km

400 Km

250 Km

200

Km

100

Km

80 Km

23o

36o

S1

S6 Stripmap Mode (SM)

Interferometric Wide

Swath Mode (IW)

Extra Wide

Swath Mode (EW)

Wave Mode (WV)

19o

46o

30o

45o

19o

46o

Sentinel-1 SAR operational modes

For all of these operating modes, the same family of Sentinel- 1 products is available to users from the Sentinel-1 Core PDGS.

The systematic processing into specific product type is done according to pre-defined areas defined (in the HLOP) while other product types will be available on request in offline (see Table 2).

Sentinel 1 Core PDGSOperational Products Types



Operational product types of the Sentinel-1 Core PDGS.

Level 0 products: contain the compressed, unprocessed instrument source packets, with additional annotations and auxiliary information to support the processing. SAR Level-0 products for IW, EW and SM modes are made available to the Sentinel-1 users.

Level 1 products: Level-1 Slant-Range Single-Look Complex Products (SLC):SLC products: provide focused data in slant-range geometry, single look, containing phase and amplitudeinformationLevel-1 Ground Range Detected Geo-referenced Products (GRD): focused data is projected to ground range, detected (phase information is lost) and multi-looked. Data is projected to ground range using an Earth ellipsoid model, maintaining the original satellite path direction and including complete geo-reference information

Level 2 products (waves, wind, radial velocity products): ocean wind field, swell wave spectra and surface radial velocity information as derived from SAR data. L2 ocean products are available for all modes (although information content may slightly vary per mode).

Sentinel-1 Core PDGS Processing Concept“Systematic global”

applies to all acquired data.“Systematic regional”

applies to data acquired over well defined geographical areas, including areas required in NRT, defined in the HLOP.“Systematic Local”

applies to well-defined geographical areas fulfilling specific constraints (e.g. within the stations coverage area), defined in the HLOP.

Sentinel-1 Core PDGSOperational Products Types



Processing Concept

Product Type

Timeliness (availability after sensing)

Comment

Systematic Global

SAR L0SAR L1 GRD

<24h All acquired data

SAR L2 OCN <3h All acquired WV mode data (oceans areas)

Systematic Regional

SAR L2 OCN <3h For regional maritime surveillance areas in HBR mode defined through HLOP

SAR L0SAR L1 GRDSAR L1 SLC

<3hData available in 3h from sensing from the core PDGS for regional areas defined through HLOP

SAR L1 SLC <24h Data available in 24h from sensing from the core PDGS for regional areas defined through HLOP

Systematic Local

SAR L0SAR L1 GRD <10 min Only for data acquired in direct downlink over the S-1 Core Ground

Stations when not addressed by collaborative stations

Archive

SAR L0SAR L1 GRDSAR L1 SLCSAR L2 OCN

Offline

All systematically generated data is available on-line on a Non Time Critical basis (e.g. nominally ˜24h)Products non systematically generated (e.g. SLC outside the systematic regional areas) can be requested from L0

Sentinel-1 Core PDGS Processing Concept and Timeliness




Sentinel-2 Core Products

Name Description Production Type of user Preservation strategy

Level-0 Raw payload and platform annotated telemetry. Image data is compressed. Granularity per detector and on-board scene25km across-track x 23km along-track.

Systematic* Internal use Long-term

Level-1A Uncompressed raw image data in sensor geometry with spectral bands coarsely co-registered. Granularity per detector and on-board scene 25km across-track x 23km along-track.

Systematic* Expert users (e.g. cal/val)

Short-term (1 month)

Level-1B Radiometrically-corrected image data in sensor geometry with spectral bands coarsely co-registered and refined geometric model appended but not applied. Granularity per detector and on-board scene 25km across-track x 23km along-track.

Systematic* Expert users (e.g. cal/val)

Long-term

Level-1C Orthorectified top-of-atmosphere reflectance images (with all parameters to convert in radiances). Product provided in tiles of 100x100km in UTM WGS84 projection.

Systematic* General users Long-term

Level-2A Orthorectified bottom-of-atmosphere reflectance images (i.e. atmospherically corrected product) + Pixel Classification (including cloud information). Product generated in tiles of 100x100km in UTM WGS84 projection.

Client side (Toolbox)

General users N/A

TCI True colour image (TCI) in JPEG format for qualitiative data exploitation and communication purposes.

Systematic* General users Medium-term (1year)

*: Systematic production includes the following regions: (1) All land surfaces between 56deg South latitude and 84deg North latitude; (2) Major islands (greater than 100 km2 size), EU islands and all the other small islands located at less than 20km from the coastline; (3) Mediterranean Sea, all inland water bodies and all closed seas; (4) Specific acquisition campaigns as required.




ESA Sentinel-3 Product Type

Instrument Name Product Type and Content

OLCI

L0 satellite data stream (ISP) - Internal product not considered for distribution

L1B Top of atmosphere Radiances ortho-geo-referenced

L2 Water Colour Product Water Leaving ReflectancesAerosol Optical ThicknessAerosol Angstrom CoefficientInstantaneous Photosynthetically Available Radiation (PAR)Chlorophyll concentration open ocean watersChlorophyll concentration coastal water watersTotal suspended MatterColoured Dissolved Organic matterDiffuse Attenuation Coefficient

L2 Land Colour Product fAPAR or OLCI Global Vegetation indexChlorophyll Terrestrial IndexRectified Reflectance in channels O9 & O17Water Vapour (over land)

SLSTR


L1B Nadir & Backward view brightness temperaturesNadir view & backward top of atmosphere radiances - Ortho-geo-referenced

L2 Geophysical Land product Land surface temperature nadir view

L2 Geophysical Water product Sea Surface Temperature




Synergy Products

L1C All OLCI and SLSTR – Internal product not considered for distribution

L2C Bidirectional Reflectance Factor Aerosol optical Depth and Angstrom over land

L2 Vegetation NDVI (1 day synthesis, 10 days synthesis)Ground reflectance

SRAL


L1B Expert users (e.g. cal/val)

L2 Land SAR mode GDR

L2 Marine SAR and LRM modes GDR

MWRL0 satellite data stream (ISP) - Internal product not considered for distribution

L1B - Expert users (e.g. cal/val)

Sentinel-3 Core PDGS Processing ConceptThe Sentinel-3 production is global and systematic, performed in NRT (<3h from sensing) or NTC, i.e. the production starts not later than 24h from the reception of the last necessary data.ESA and EUMETSAT ensure the same Sentinel-3 Level-1B Core systematic production.


ESA INDUSTRY INFORMATION DAY Ground Segment...

Documents

Transcript of ESA INDUSTRY INFORMATION DAY Ground Segment...