Sentinels PDGS Industry Information Day, 5 May 2009, pg. 1 GMES Space Component Sentinel Payload...

Sentinels PDGS Industry Information Day, 5 May 2009, pg. 1

GMES Space Component

Sentinel Payload Ground Segment

Industry Information Day


•Inform Industry about Procurement Plans for the GSC Sentinel Payload Ground Segment

•Collect general questions to be responded to all prior to release of the ITTs

Purpose of the Mtg


Introduction

Welcome & General Introduction

Overall Scope of the activity

Sentinels PDGS Procurement rules

Sentinels PDGS Sub-Systems

Front End Processor

Precise Orbit Determination

Operational Instrument Processors

Mission Planning

Procurements way forward Best practices

Schedule and way forward

Sentinels PDGSS-1 Payload Data Ground Segment

(PDGS)

S-2 and S-3 PDGS

Sentinels PDGS Industry Information Day


GMES & GSC Introduction


GMES components

GMES is an EU led initiative

Services Component – led by EC

• Produces information services in response to European policy priorities in environment and security

• Relies on data from in-situ and space component

In-situ component – led by EEA

• Observations mostly within national responsibility, with coordination at European level

Space Component – led by ESA

• Sentinels - EO missions developed specifically for GMES:

• Contributing Missions - EO missions built for purposes other than GMES but offering part of their capacity to GMES (EU/ESA MSs, EUMETSAT, commercial, international)


GMES dedicated missions: Sentinels

Sentinel 1 – SAR imagingAll weather, day/night applications, interferometry

Sentinel 2 – Multispectral imagingLand applications: urban, forest, agriculture, etc

Continuity of Landsat, SPOT data

Sentinel 3 – Ocean and global land monitoringWide-swath ocean color, vegetation, sea/land surface

temperature, altimetry

Sentinel 4 – Geostationary atmosphericAtmospheric composition monitoring, trans-boundary

pollution

Sentinel 5 – Low-orbit atmosphericAtmospheric composition monitoring

2011

2012

2012

2017+

2019+


Sentinel-1

Applications: • monitoring sea ice zones and the arctic environment• surveillance of marine environment• monitoring land surface motion risks• mapping in support of humanitarian aid in crisis

situations

4 nominal operation modes: • strip map (80 km swath, 5X5 m res.)• interferometric wide swath (250 km swath, 20X5 m

res.)• extra wide swath (400 km swath, 25X100 m res.)• Wave (5X20 m res.)

2300 Kg spacecraft mass

Sun synchronous orbit at 693 Km mean altitude

12 days repeat cycle

7 years design life time, consumables for 12 years

Sentinel-1:

C-band

SAR mission


Sentinel-2

Applications:• Generic land cover maps• risk mapping and fast images for disaster relief• generation of leaf coverage, leaf chlorophyll

content and leaf water content

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

Spatial resolution: 10, 20 and 60 m

Field of view: 290 km

1180 kg spacecraft mass

5 days repeat cycle

Sun synchronous orbit at 786 km mean altitude


Sentinel-2:

Superspectral imaging mission


Sentinel-3

Applications:

• Sea/land colour data and surface temperature

• sea surface and land ice topography

• coastal zones, inland water and sea ice topography

• vegetation products


Sun synchronous orbit at 814.5 km mean altitude over geoid



Sentinel-3:

ocean & global land mission


Sentinel-3

Instruments:

• Ocean and Land Colour Instrument (OLCI) with 5 cameras, 8 bands (only VIS) for open ocean (low res), 15 bands (only VIS) for coastal zones (high res). Spatial sampling: 300m @ SSP

• Sea and Land Surface Temperature (SLST) with 9 spectral bands, 0.5 (VIS, SWIR) to 1 km res (MWIR, TIR). Swath: 180rpm dual view scan, nadir & backwards

• RA packageSRAL Ku-C altimeter (LRM and SAR measurement modes), MWR, POD (with Laser Retro Reflector, GNSS and DORIS)


Sentinel-4

Applications:

• monitoring changes in the atmospheric composition (e.g. ozone, NO2, SO2, BrO, formaldehyde and aerosol) at high temporal resolution

• tropospheric variability

Narrow field spectrometer covering UV (290-400 nm), visible (400-500 nm) and near-IR (750-775 nm) bands

Spatial sampling 5-50 km and spectral resolution between 0.06 nm and 1 nm (depending on band)

Geostationary orbit, at 0o longitude

Embarked on MTG-S and operated by EUMETSAT

Sentinel-4:

GEO atmospheric

mission


Sentinel-5

Applications:

• monitoring changes in the atmospheric composition (e.g. ozone, NO2, SO2, BrO, formaldehyde and aerosol) at high temporal (daily) resolution

• tropospheric variability

Wide-swath pushbroom spectrometer suite, covering UV (270-400 nm), visible (400-500 & 710-750 nm), NIR (750-775 nm) and SWIR (2305-2385 nm) bands.

Spatial sampling 5-50 km and spectral resolution between 0.05 nm and 1 nm (depending on band)

Low Earth orbit (reference altitude of about 817 km)

Sentinel-5 precursor to fill data gaps (2013-2019). Sentinel-5 embarked on post-EPS and operated by EUMETSAT

Sentinel-5:

LEO atmospheric

mission


GCM GS

GCM GS

GCM GS

GCM GS

GCM GS

GMES Service Segment

GMES Sentinels

GS

FOS

Sentinel-1

TT&C Stations

Sentinels

PDGS

Acquisition Stations

GMES C

ontributin

g Mis

sions

GS’s

(ESA, E

UMETSAT, N

OAA, nat

ional

mem

ber-s

tate

s m

issi

ons, e

tc…

)

GSC Coordinated Data Access System

GMES Space

Component

GSC Data Request

GSC Data Provision

TM/TC ISPs

GMES Ground Segment and Data Access

Sentinel-3

GCM GS

USER Segment

Final end-user information products


GSC implementation schedule

2004 2005 2006 2013 2014 2023

Preparatory

programme Build-up phase(Segments 1 + 2)

Operational programme


Content of GSC programme

Segment 2

Sentinel-1 A: Phase B2/C/D/E1. Sentinel-1B: up to flight readiness



Sentinel-4 (MTG-S): Phase B/C/D incl, processor & 2nd unit

Sentinel-5 (post-EPS): Phase B1 & pre-development

Sentinel 5 pre-cursor up to Launch and IOV; UV-NIR instrument provided by NL

Ground Segment Development for Sentinel-1, -2, -3

Data Access (management, operations & data procurement)

GSC Evolution Studies, incl. low-inclination altimetry (Jason follow-on)


First Set of data requirements consolidated in May 08

GMES Fast Track Pilot Services & Urban Atlas (Start Sep08-Apr09)

Several Requirements Review loops and updates

GSCDA portal open since early Dec 08; ESA- data, ESA-TPM data & Eumetsat data are provided since;

9 Contracts placed or under negotiation with GMES Contributing Missions

EU Agency interfaces being discussed

Requirements strongly evolved and evolve

GSC Data Access Status today


GSCDA Pre-operations Status

22

10

12

3

0

22

10

87

0

22

10

2

10

3

21

10

3

9

4

21

10

2

10

4

21

10

2

9

5

21

9

3

9

5

21

9

3

9

5

0

5

10

15

20

25

Nr.o

f Dat

aSet

s

10-Dec-2008 19-Dec-2008 12-Jan-2009 3-feb-2009 20-feb-09 27-feb-09 19-mar-09 23-mar-09

Defined

Potential

UnderImplementation

Partially Opened

Opened

Closed tickets by time

0

10

20

30

40

50

60

Same day Within 2days

Over 2 days Total

GEOLAND2

G-MOSAIC

MACC

MYOCEAN

SAFER

CDS internal tickets(SCI)SCIURBAN ATLAS

All GSP

ESRINNr. Products Disseminated from 16-Feb to 15-Mar

00

80

1326

54

194

186

185

185

325

387

1223

186

421

0 200 400 600 800 1000 1200 1400

DAP_MG1_08Env ASA_WSM_1P(SeaBaltic)

DAP_MG1_10Env ASA_WSM_1P(SouthGreen)

DAP_MG1_12 Env ASA_WSM_1P(Eurarctic1)

DAP_MG1_09_11_13_14_15Env ASA_WSM_1P

Env MER_RR__1P

DAP_MG3_03Env MER_RR__2P

Env ATS_NR__2P

DAP_MG3_04Env ATS_TOA_1P

DAP_MG3_05 Env RA2_FGD_2P

DAP_MG3_01 Env MER_FRS_1P

Env ATS_TOA_1P

DAP_MG3_02Ers-2 WSC_UWI_1P

DAP_MG2b_01 ALOS PSM_P-AV2_X

oo

oo

oo

oi

i§

MyO

cean

Geola

nd2

Urb

an

Atlas

Deployed DataSets Help Desk Statistics

Delivered Products

GSCDA DataSets advertised on GSC Portal http://gmesdata.esa.int

GSCDA Pre-operations started with ESA and ESA-TPMs in Dec. 2008


GSCDA System Infrastructure Development

Development of Data Access System infrastructure on-going

• System requirements Review held in June 2008

• Preliminary Design Review on-going

Development of interfaces with GSC Contributing Missions on-going


GSC shall respond to all current and expected (*1) requirements. Accordingly the Sentinel GS will consist of a

ESA Sentinel Core Ground Segment (*2)

and

Collaborative Ground Segment of- national ground segment elements - GS functions within the GMES Services Segment

(*1) from new GMES Services, EU agencies, member states, science etc(*2) incl. interfaces and mgt functions for the collaborative parts; incl EDRS interfaces in the architecture)

Requirements Vs Architecture


High Data Volume

Operational Data Delivery from Beginning- Maximum ‘systematic’ functions- Simple, easy design- highest reliability for E2E data access for users

Flexibility (Without impact of systematic functions)

- clear interfaces to complementary GS functions- Re-processing as part of system budgets

Sentinel PDGS Integration into an already ‘operational’ GCM service, during commissioning

Main GSC GS Design / Development Drivers


GMES Space Component funding

Segment 1 & 2 Co Funding Scheme

Financing – ESA GSC programme 758 M€ Segment 1 831 M€ Segment 2

Financing – EC FP7 600 M€ FP7 Space

~ 2.2 bn€ for development of first generation of Sentinels, data access to MS/EUM missions, ground segment, early operations


Funding and Procurement

ESA-only funded elements and ESA-EC joint-funded elements

Open to

ESA Member States and ESA- Member States andEC FP7 participating

StatesIssued via

ESA Emits and ESA- Emits andEC Cordis

Managed by

ESA (and ESA procedures *)

* No georeturn targets but georeturn reporting


Sentinels PDGS DevelopmentsOverall Scope


• Introduction to the GMES Space Component infrastructure and services

• Introduction to Sentinels PDGS– Drivers– Infrastructure and Services– Development Logic

• Introduction to Sentinels Procurement– Procurement Logic and phasing– Procurement Sizing

• Schedule


GSC infrastructure is decomposed into :

GSC Core Space Segment : Space infrastructure (Sentinels constellation)

GSC Contributing Missions (GCMs): National, ESA or Third Party missions partially or fully supporting the GMES Space Component, complementing the Sentinels services according to the GSC operational gap filling analysis

GSC Core Ground Segment : Sentinels Flight Operation Segment (FOS) and Payload Data Ground Segment (PDGS). The Core Ground Segment also includes capabilities for assembling data from external sources and for interfacing with the third party entities (GCM or collaborative GS)

GSC Collaborative Ground Segments: Third party entities that contribute to the GSC infrastructure, providing complementary services or improving overall performances (e.g. local stations)

GSC Ground Segment infrastructure


Space Segment operationsSentinels TT&C data uplink and downlink (S-band link)Sentinels satellites commanding & control

Mission exploitationSentinels data acquisition: (X-Band/Ka-Band data downlink and ingestion), through a Sentinels Core Ground Stations network

Sentinels Mission planning: for Sentinels data downlink and instrument sensing.

Systematic and rush generation of mission data products: (at least to a calibrated product level) and access through satellite broadcast link over Europe or ground network to a pick up point

Mission data preservation and access: long-term preservation (25 years) of all Sentinels and relevant GCM products (Including Mission reprocessing function). These data are accessed on-line through automated request mechanism.

GSC Core Ground Segment Services (1/2)


Mission exploitation

Sentinels mission performances monitoring and control: characterisation of the space and ground infrastructure performances (e.g. sensors ageing, network availability), adjustment of on-ground services to guaranty services performance continuity, regular reporting on measured operations performances

GSC data-sets assembly: The assembly service offers the possibility to generate, consolidate and retrieve some of the large data sets required by GMES Services Projects, (e.g. coverage or stack data sets), including the integration of non-Sentinels mission data whenever necessary.

GSC Users Coordinated Interface: Interface to the GSC users for:Coordination of multi-mission rush satellite tasking requests in support to emergencies and crises management Service support for GSC users, including user registration and service desk

GSC Core Ground Segment Services (2/2)


•High data rates and on-ground volumes to be managed

Sentinels PDGS Drivers

S1-A

S2-A

S3-A

S1-B

S2-B

S3-B

ENVISAT HRENVISAT LR

0

500

1000

1500

2000

2500

3000

3500

4000

GB

sentinels L0 GB/day ENVISAT L0 GB/day

Sentinels & ENVISAT L0 Volume per day

S1-A

ENVISAT ASAR

0

100

200

300

400

500

600

GB

Systematic NRT(Average S-1 Scenario) [GB/day]

Systematic NRT

•Initial development is organised to support the B-series as a natural upgrade

•Missions are considered operational and commissioning phase shall be completed within 3 to 4 months

•25 years of mission exploitation

All developments are defined as operational software development


The Payload Data Ground Segment (PDGS) covers the infrastructure necessary for :

Sentinels data acquisitionDemodulation and front end processing elements

Sentinels Mission planning

Systematic and rush generation of mission data productsProduction data flow control including: processors, auxiliary data management, precise orbit determination, dissemination, rolling and on-line repositories

Mission data preservation and access

Long term archive, catalogue, dissemination

Sentinels mission performances monitoring and controlInstrument performance monitoring, quality control, cal/val tools, end-to-end system performances monitoring and reporting

GSC data-sets assembly

Product consolidation and data assembly elements

Sentinels PDGS infrastructure and services


•Common elements regrouped into separate ITTs• Demodulator and Front End Processor• Precise orbit determination services

•Maximise reuse of existing European infrastructure and ESA supported operational interfaces:

• X-Band Antenna Acquisition System • Long term data archiving infrastructure • User Services•Auxiliary data handling services

Elements will be procured as services within a separate ITT (for stations & centres) based on customisation of standard interfaces

•Three Satellite missions leading to specific procurements (ITTs or Best practices)

• “PDGS core contract” for end-to-end design and integration (including development of required specific elements)• Mission Planning• Operational Instrument Processor and Performance monitoring and QC

Sentinels PDGS Development logic


Phase 1: Definition of the PDGS operational interfaces Development of the PDGS infrastructure elements Reference platform integration

Phase 2 : Procurement of the centres according to PDGS interfaces specifications

Phase 3:

Deployment of PDGS elements into the procured centresOverall verification

Phase 4: Commissioning operations Maintenance of PDGS system during commissioning

Sentinels PDGS Procurement Logic

Part of current ITT

Definition of the PDGS operational interfaces Development of the PDGS infrastructure elements Reference platform integration

Procurement of the centres according to PDGS interfaces specifications

Deployment of PDGS elements into the procured centresOverall verification

Commissioning operations Maintenance of PDGS system during commissioning

Procurement of the centres according to PDGS interfaces specifications

Commissioning operations

Part of operations ITT in 2010


Project timeline overview

S-3 PDGS

S-2 PDGS

S-1 PDGS

2013

Feb 12IOCR

Nov 11Launch

2010 2012

Nov 08GS RR

Jan 10PDGS-PDR

2009 Apr 09PDGS-SRR

20122011

Oct 12Launch

Jan 13IOCR

2009 Sep 10PDGS-PDR

20132010Nov 09PDGS-SRR

Nov 12Launch

201320102009 2012Apr 10PDGSPDR

Feb 13IOCR

Jul 09PDGS-SRR

2011

April 09GS RR

June 09GS RR


S1 PDGS Core ~18 M€ Including Best Practices



Values may be refined while preparing the SOW, targets will be indicated with the issue of the ITT

S1 Mission Planning ~600 k€ S1 is considered the most complex (~400 k€ for S2)

S1 Mission Performances tools

~1,5 M€

S2 and S3 figures will be consolidated (IPF best practices between 1.5M € and 2.0M€, and Performances tools between 1M€ and 2M€)

Sentinels PDGS Procurement Sizing


Sentinels PDGS Invitations to Tender: proposal requirements & selection

O. Leonard

RES-POE


1. Publication of ITT

Emits:

http://emits.esa.int -> Open Invitations to Tender

Cordis:

http://cordis.europa.eu/fp7/cooperation/space_en.html

English only Closing Date Requests for clarifications/extensions


2. Content of ITT Package

1. Cover letter

2. Statement of Work

3. Draft Contract

4. Special Conditions of Tender


Content of ITT Package

1. Cover letter Eligible bidders:

-ESA + EU FP7 (http://cordis.europa.eu/fp7/who_en.html#countries) -no industrial policy requirements / Geo-return clause -requested expertise of bidding consortium -exclusions in case of conflict of interest (if any)

Overall max. budget Responsible Contracts Officer Closing date and place of submission.

-at least 6 weeks left for submission of bids -Possibility of request for extension (request must be made at

least 2 weeks before closing date) Number and type of copies required and where to address (ESA)



2. Technical Documentation (Appendix 1 to ITT)

Statement of Work Formal statement of the work required by ESA

(evaluation techn. Crit) Tasks descriptions, outputs Annexes: Applicable and reference documents

Technical requirements Technical specifications to be observed for

performance of work (mandatory)



3. Draft Contract (Appendix 2 to ITT)

Content ESA GCC applicable, specific conditions in the contract Applicable documents Price type and payment scheme Place and date of delivery, Agency furnished Items, penalties,

acceptance and rejection IPR: all Operational Software – IPR assigned to ESA (see Part II.

(Option A)ESA GCC, esp. Clauses 39 to 44) Best practices (Annex)

Specific provisions stemming from ESA/EC Delegation Agreement

Publicity related to Contract (specific EU mentions and logo) Availability of deliverables to EC or EC-designated entities IPR waiver liability towards EC



4. Special Conditions of Tender (Appendix 3 to ITT)

Purpose Conditions specific to the procurement and related to submission of offers

(not a contractual doc) Ensure the offers contain enough information as to its quality, that offers are

structured in a similar way, to identify easily non-compliances and allow fair assessment

Content Structure of the tender (cover letter,

technical-management-financial/administrative/contractual proposal) Technical requirements Management requirements (incl. best practices organisation) Financial proposal Contractual proposal: acceptance (incl. best practices)/reservation, IPR

conditions Annexes: checklist, evaluation criteria


3. Evaluation process

ESA evaluation procedure applicable

1. Evaluation criteria2. TEB (incl. EC)

3. Contract negotiation

4. Award of contract

5. Regret letter and debriefing


Sentinel-1 PDGS

Procurement Overview


• Sentinel-1 is a polar-orbiting SAR satellite constellation for operational SAR applications, primarily focussed on those offered by the GMES Fast Track Services (Land Monitoring Core Service, Ocean Monitoring Core Service, and Emergency Respond Core Service).

• The Sentinel-1 mission will ensure the C-band data continuity to satisfy requirements defined in the Sentinel-1 Mission Requirements Document, current requirements from GMES Core Services and Downstream services, the projection of these requirements for the GSC operations phase from 2012 onwards and the expected National and scientific requirements.

Main Mission Objectives & Characteristics

Sentinel-1 Mission Overview

Orbit: Near Polar Sun-SynchronousRepeat cycle: 12 days. 175 orbitsPayload: C-Band Synthetic Aperture Radar (central frequency 5.405 GHz)Constellation: Sentinel-1 system will be composed of two satellites, Sentinel-1 A & BDuty cycle: up to 25 min in high rate mode and the rest of the orbit in WV modeSchedule (Sentinel-1A): Launch Q4 2011

360

100 Km

200 Km

12

34

5

80 Km


S-1 PDGS Key Design & Operations Drivers

• Large down-linked data volume (~ 60 GB/orbit, ~ 900 GB/day from 1 satellite)

• Priority downlink from memory to support NRT, direct downlink at Core Ground Stations and downlink support to local stations

• Highly pre-defined systematic observation plan

• Systematic data driven processing, dissemination and archiving of all acquired data. NRT data provided in less than 1 h from station acquisition, the rest within 24-48 h

• Rush on-request planning, processing and dissemination supported for emergency and security.

• Access to systematic data flow on subscription basis (no ordering required)

• On-line access to past mission data

• Stable and traceable product quality meeting the quality requirements and accurate product calibration

• Capability to support Sentinel-1A & Sentinel-1B

Key drivers for S-1 PDGS design and operations from GMES Services needs


Sentinels Common Elements/Facilities

Future Procurements (2010)

Service provided as part of a future

“Stations & Centres” procurement activity

Sentinel-1 PDGS Implementation Contracts

S-1 Core PDGS

Future ProcurementsS-1 PDGS specific

Generic servicesat PDGS centres

Service provided as part of customisation

of Multi-mission services

Generic ESA multi-mission

services

S-1 Specific Elements

On-going separate procurements

X-Band Acquisition Service


Long-term dataarchiving serviceLong-term data

archiving service

Centres Commissioning Operations


User servicesUser services

Auxiliary data handling serviceAuxiliary data

handling service

S-1 IPFS-1 IPF

Definition and integration of the S-1 end-to-end PDGS

Including:

• Development of new elements• Update/configuration of suitable existing elements• Integration of elements or services provided by ESA• Best Practices specification and organization

• Overall PDGS AIV activities

• Support to GS OSV

• Sentinel-1 PDGS System maintenance till the end of the Commissioning Phase

Demodulator & FEPDemodulator & FEP

Precise Orbit DeterminationPrecise Orbit Determination


Info Day ScopeSentinels Common Elements/Facilities


S-1 Core PDGS

Future Procurements




Long-term dataarchiving serviceLong-term data

archiving service



Scope of this presentation



S-1 Specific Elements

S-1 IPFS-1 IPF




services



handling service

Definition and integration of the S-1 end-to-end PDGS

Including:





S-1 PDGS specific


S-1 Core PDGSS-1 elements/facilities

implementation

Instrument Performance Monitoring,

QC and cal/val


QC and cal/val

L0 generation L0 generation

Data AssemblyData Assembly

Mission PlanningMission Planning

Includes specific S-1 development as well as elements operationally proven with other missions and reusable with update/configuration for S-1

S-1 PDGS AIV

Integration and Testing activities leading to PDGS Acceptance.

Includes integration of S-1 elements procured separately & configuration of any provided CFI element

S-1 PDGS Reference Facility

Set-up of a reference PDGS facility for testing and maintenance

Support to GS OSV

Support to the integration of the PDGS in the GS and OSV tests leading to GS Acceptance

S-1 PDGS System maintenance

Maintenance activities till end Commissioning Phase

Sentinel-1 Core PDGS Contract Scope (1/2)

PDGS System end-to-end Design

The required task covers the full PDGS end-to-end design, including interfaces with external elements to the PDGS core contract, e.g.:Interfaces with collaborative entities

… …

Processing controlProcessing control

Procured through Best Practices within the Core PDGSProcured through Best Practices within the Core PDGS


QC and cal/val


QC and cal/val

Mission PlanningMission Planning


• S-1 PDGS AIV activities within the Core PDGS contract will include:

Set-up of a reference PDGS facility to support end-to-end PDGS tests before deployment and maintenance activities

Integration of elements procured inside the S-1 Core PDGS Contract

Integration with ESA non-specific services (e.g. user services)

Integration of S-1 specific elements procured separately and provided as ESA CFI (e.g. S-1 L1/2 processor)

Integration of Sentinel common elements provided separately and provided as ESA CFI (e.g. FEP)

Organisation and deployment of the PDGS system (including ESA provided CFIs) in the ESA-procured centres and Integration with generic services at these centres (Acquisition, Long-term data archiving) -> PDGS sites (X-Band Ground Receiving Stations and Assembly, Processing and Archiving Centres) will be procured as part of a separate ITT

Sentinel-1 Core PDGS Contract Scope (2/2)


Sentinel-1 Core PDGS Procurement Approach (1/2)

• S-1 Core PDGS Procurement will be based on the following system technical baseline documentation:

S-1 PDGS System Requirements DocumentProvides the system level requirements to be fulfilled by the S-1 PDGS as a whole and the parent requirements for the PDGS elements. Does not pre-define a system architecture.

S-1 PDGS Operations Concept DocumentDescribes the PDGS end-to-end system operations concept to be satisfied.

• In addition, the following complementary system technical information will be provided:

S-1 PDGS Master ICDDefines the main internal and external interfaces of the S-1 PDGS

S-1 PDGS System Technical BudgetDescribes a set of observation scenarios for system sizing purposes

S-1 PDGS System Test ConceptProvides the guidelines PDGS testing


• For the ESA CFI elements (e.g. S-1 IPF or common PDGS elements), the integration will be based on ESA provided interface specifications

• For some specific S-1 PDGS elements to be implemented as part of the Core PDGS, ESA will provide preliminary version of technical requirements to be refined as part of this contract

e.g. for mission planning, Instrument performance monitoring, S-1 products Quality verification and calibration

• For the generic services at PDGS centres - procured independently by ESA-, the integration will be based on the interfaces specified within the present contract

Sentinel-1 Core PDGS Procurement Approach (2/2)


Sentinel-2 and Sentinel-3 PDGS

Procurement Overview


Applications:• Generic land cover maps• risk mapping and fast images for disaster relief• Damage evaluation• Burned areas mapping

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

Spatial resolution: 10, 20 and 60 m

Field of view: 290 km


10-day repeat cycle (5 day revisit with two satellites)

Sun synchronous orbit at 786 km mean altitude


Sentinel-2:

Superspectral imaging mission

Sentinel-2 Mission Overview


Sentinel-2 PDGS Drivers

• Large down-linked data volume (~55 GB/orbit, 800 GB /day from 1 satellite)

• Priority downlink from memory for supporting Near-Real Time, downlink at Core Ground Stations and possibility of live image downlink to local stations

• Uninterrupted land imaging following seasonal sun elevation between 83 and -56

• Systematic data driven processing, dissemination and archiving of all acquired data. NRT data provided in less than 1 h from station acquisition, the rest within 24-48 h


• Systematic production of continental-scale cloud-free coverages (i.e. image collections) available online and via subscriptions

• On-line access to past mission data


• Capability to support Sentinel-2 A and Sentinel-2 B



Applications:

• Sea/land colour data and surface temperature

• sea surface and land ice topography

• coastal zones, inland water and sea ice topography

• vegetation products


Sun synchronous orbit at 814.5 km mean altitude over geoid



Sentinel-3:

ocean & global land mission

Sentinel-3 Mission Overview (1/2)


Instruments:

• Ocean and Land Colour Instrument (OLCI) with 5 cameras, 8 bands (only VIS) for open ocean (low res), 15 bands (only VIS) for coastal zones (high res). Spatial sampling: 300m @ SSP

• Sea and Land Surface Temperature (SLST) with 9 spectral bands, 0.5 (VIS, SWIR) to 1 km res (MWIR, TIR). Swath: 180rpm dual view scan, nadir & backwards

• RA packageSRAL Ku-C altimeter (LRM and SAR measurement modes), MWR, POD (with Laser Retro Reflector, GNSS and DORIS)

Sentinel-3 Mission Overview (2/2)


Sentinel-3 PDGS Drivers

• Large down-linked data volume (~20 GB/orbit, 300 GB /day from 1 satellite)

• Systematic Near-Real Time L-1/2 processing and on-line availability of 100% of the data

• Archiving and precision reprocessing of 100% of the data to level 1/2

• Possibility of direct image downlink to local stations (from imagers)

• Continuous payload operations (except OLCI operating only in daylight)


• Direct access to past mission data


• Capability to support Sentinel-3 A and Sentinel-3 B



Sentinels Common Elements/Facilities

Future Procurements (2010)

Service provided as part of a future

“Stations & Centres” procurement activity

Sentinel-2 PDGS Implementation Contracts (1/2)

S-2 Core PDGS

Future ProcurementsS-2 PDGS specific





services

S-2 specific elements procurement



Sentinel-2 PDGS Implementation Contracts (2/2)

S-2 Core PDGS

Future Procurements Definition and integration of the S-2 end-to-end PDGS



services




Long-term dataArchiving

Long-term dataArchiving



Including:








handling service

S-2 Mission PlanningS-2 Mission Planning

S-2 specific elements procurement





S-3 Core PDGS

Future Procurements Definition and integration of the S-3 end-to-end PDGS



services




Long-term dataArchiving (land)Long-term dataArchiving (land)



Including:








handling service

S-3 Mission Planning (EUMETSAT)S-3 Mission Planning (EUMETSAT)

S-3 specific elements procurementPDGS EUMETSAT

Elements

Marine User AccessMarine User Access

Marine processing and long term

Archive centre

Marine processing and long term

Archive centre



S-2 Core PDGSSpecific S-2

elements/facilitiesDevelopment



S-2 PDGS AIV




Set-up of a reference PDGS facility for testing and maintenance

Support to GS OSV




Sentinel-2 Core PDGS Contract Scope



… …




QC and cal/val


QC and cal/val

Instrument Processing Facility

Instrument Processing Facility



S-3 Core PDGSSpecific S-3

elements/facilitiesDevelopment



S-3 PDGS AIV




Set-up of a reference PDGS facility for testing and maintenance. Including deployment of reference facilities at EUMETSAT

Support to GS OSV




Sentinel-3 Core PDGS Contract Scope



… …




QC and cal/val


QC and cal/val

Instrument Processing Facility(Land & Marine)

Instrument Processing Facility(Land & Marine)



Sentinel-2 / Sentinel-3 Core PDGS Scope

• S-2/3 Core PDGS Procurement will be based on the following system technical baseline documentation (jointly prepared with EUMETSAT for S-3):

S-2/3 PDGS System Requirements DocumentProvides the system level requirements to be fulfilled by the S-2/3 PDGS as a whole and the parent requirements for the PDGS elements. Does not pre-define a system architecture.

S-2/3 PDGS Operations Concept DocumentDescribes the S-2/3 PDGS end-to-end system operations concept to be satisfied.

• In addition, the following complementary system technical information will be provided:

S-2/3 PDGS Master ICDDefines the main internal and external interfaces of the S-2/3 PDGS

S-2/3 PDGS System Technical BudgetDescribes a set of observation scenarios for system sizing purposes

S-2/3 PDGS System Test ConceptProvides the guidelines PDGS testing


• Satellite and FOS Interfaces Documents

• Detailed processing model and reference test data

• Sample satellite Test Data

• S2 Decompression Software & all related documentation

Sentinel-2 / Sentinel-3 ESA CFIs


Sentinels PDGS

Demodulator andFront End Processor


The technical feasibility assessment has shown that a common procurement is feasible across Sentinels:

RF level – commonality confirmed.

Data level (commonality based on standards, e.g., CCSDS)

Downlink Channel Management – Commonality issue found. Sentinel 3 only: inter-channel downstream dependency (implies extra development and more stringent ground performances) – Function allocation still TBC.

Other differences are mainly at configuration level.

The market survey indicates the presence of some equipment closed to Sentinel needs (not extensive development phase expected).

Technical Assessment and Market Survey


The Scope of the Procurement

FEPFEPX-band AntennaX-band Antenna

L0L0MODEMMODEM

DFEP

SchedulePower

SchedulePower

IFIF FEPFEPX-band AntennaX-band Antenna

L0L0MODEMMODEM

DFEP

SchedulePower

SchedulePower

IFIF

Main Sub-elementsMODEM Demodulator and Modulator

FEP Front End Processor


Activities and Driving Principles

One Procurement Action

The bidder(s) need to provide a proposal compatible with the two sub-elements subject to delivery.

The bidder(s) need to cover the following activities:Design and Development activities

AIV (Factory and on-Site) activities

Management activities involving the sub-element(s) subject to its bidding.

Driving Principles:The new development should be kept at minimum in favour of evolving existing units already available on the market

Multi-mission programmable demodulators (based on standards) and front end processing systems.


Quotation and Delivery

Core Stations Approach

The bidder(s) need to deliver and support the integration for:Initial number of units necessary for reference and validation platforms.

Units for the Sentinel 1, 2 and 3 Core Stations (locations and number TBD).

The bidder(s) need to provide a quotation showing the benefits of scale:Purchase up to 4 recurrent units; purchase from 4 to 8 recurrent units; purchase from 8 to 12 recurrent units, etc.

The bidder(s) need to provide the quotation also for maintenance

Local Stations Approach

The bidder(s) need to provide a quotation showing the benefits of recurrent units (including maintenance):

Available to Local Stations at recurrent price

As an option, ESA could procure the units and provide them to the Local Stations


Sentinel PDGS

Precise Orbit Determination


The GMES Precise Orbit Determination (POD) Service shall provide orbit products to the

Sentinels 1, 2 and 3 missions for supporting the PDGS operations

GMES POD Service Objective


The GMES POD Service shall ensure the following functions for each of the Sentinel missions:

- NRT and OFL Orbit Products Computation

- GNSS In-orbit Sensor Performance Monitoring

- Long Term Monitoring & Validation of PDGS Orbits

- Orbit Reprocessing

GMES POD Service Functions


GMES POD System - Context

Two entities:- NRT POD- OFL POD

S-3 Specific


GMES POD Interfaces

Satellite & Receiver Info [mass, manoeuvres quaternions,

phase centres and clocks, attitude data (NAVATT),

receiver status, ...]

Environmental Data [leap seconds, gravity fields, ocean tides, solar flux,

geomagnetic indices, GIM, ...]

Measurements

LRR

DORIS Network

IGS Network

DORIS data

GPS data

Rapid (NRT) + Prelim./Precise (OFL)

Orbit Ephemerides

Reports[ops, QC]

ILRSNetwork

SLR data

S3 specific

On-board Receivers

PODService


The GMES POD Service shall :

- Be compliant and tailored to the mission specific objectives, error budgets, expected performance and availability requirements

- Rely on common and shared infrastructure and expertise

- Rely on specific expertise for OFL orbit processing (e.g. Altimetry)

- Be scalable for the integration of additional EO Sentinel Satellites

- Support to Integration and Verification Phases

GMES POD Project Objectives


- One single contract based for:

- Service Level Agreement based on an available POD Service Capability

- Delivery of NRT POD for integration in Sentinel PDGS

=> No DPM provided as ESA CFI

=> Only Sat to ground ICD

- Incremental Delivery and Service Provision approach for each Sentinel mission

GMES POD - Procurement Approach


Sentinels PDGS S-2, S-3

Operational Instrument Processorsand Cal/Val and Quality tools


Procurement will cover :Processors for Sentinel-2 and Sentinel-3 products

IPF – Instrument Processing FacilityQuality Tools for Sentinel-2 and Sentinel-3 Cal/Val tools, QC tools

Sentinel-1 processor covered by previous contract (already initiated)

Procurement objectives


Sentinel-3: Optical Sensors Processing

L1 IPFOLCI

L1 IPF SLSTR

L1B

L1CCombined

OLCI/SLSTR

L1B

L1C IPF SLSTR/OLCI

L2 IPFOLCI

L2 IPF SLSTR

L2 IPF SLSTR/OLCI

Waterproducts

Land products

SSTLand surface product

Surface Directional Reflectances

Level 1IPFs

Level 2IPFs


Sentinel-3 : Altimetry Processing

SRAL Level 1B Processor

MWR Measurements (20 Hz)

MWR Level 1B Processor

SRAL & MWR Level 2

Processor

Auxiliary Data Files

L1 B MWR Product

Ku/C bands LRM mode SRAL Measurement

(20 Hz)

C band SAR modeSRAL Measurement

(20 Hz)

L1 B SRAL Product

Ku band SAR modeSRAL Measurement

(20 Hz)

L2 SRAL / MWR Product

Ku band SAR modeSRAL Measurement

(20 Hz, 1 Hz)

Ku/C bands LRM modeSRAL Measurement

(20 Hz, 1 Hz)

C band SAR modeSRAL Measurement

(20 Hz, 1 Hz)


Sentinel-2: Instrument Processor Facility

IPF L1

IPF L2

L1C orthorectified product

Atmospheric correction.

L1B

DEM

CFI


Operational developmentESLs

Input from ESA Baseline for IPF development

Detailed Processing Model L1 / L2 Input Output Data DescriptionTest data set Generic Interface Specification ECSS standard

NB: DPM / IODD / TDS provided by “Prototype contracts”

Deliveries Software – code, exe Documentation (Product specification, Test reports, user manual, Software release note, Product Specification, ICD…etc)Support, maintenance, expertise, commissioning phase support

IPF: Engineering approach

Algorithms Specification

Algorithms Engineering

S2 / S3 prototypes

S2 / S3 IPF

ESA

Algorithm Specifications and prototyping

•Software•Processors ICDs

Algorithm definition and prototyping contracts

Operational implementation contracts


IPF main inputLevel 0Aux files (including orbit files)Orders files

IPF main outputLevel 1 productsLevel 2 products Basic Level 3 productsBrowse / catalogue

Cal/Val and quality tools Calibration and validations functions Initial analysis and monitoring functions Reporting functions

Procurement Scope


Procurement will be done through “Best Practices”

2 ITTs / within each core PDGS contract- IPF software development- Quality Tools software development,

algorithm development and earth observation products expertise

Incremental procurement according to mission schedule Maintenance until end of commissioning phase Support to commissioning phase, maintenance of reference chain

Procurement Organization


Sentinels PDGS

Mission Planning


• Instrument Planning• On-board recording resource management

(packet store management)• Downlink Planning• Handling of multi-satellite constellation as single

resource• Support to local Stations• Support to EDRS• X-Band conflict handling to be solved outside

mission planning by operational agreements

Procurement Scope


• FOS interface: customized from Earth Explorer missions interface

• Mission Management Interface for ingestion of systematic observation requirements from GMES Service Providers

• User Service interfaces to be based on current multi-mission ICDs with possible customizations

• Station Interface to be based on multi-mission station interface with possible customizations

Mission Planning Interfaces


• variable on-board compression make location of actual downlink difficult to predict ==> mission planning probabilistic packet store management algorithm requires capability of stations and assembly centres to handle non-nominal scenarios

• MP was incorporated into the PDGS contract => "best practise" approach

• Output: fully operational system integrated in PDGS and support to commissioning phase

Mission Planning: S-1


Variable Compression Algorithm

• Mission Planning System will need to rely on an external library that evaluates the expected compressed size of each data take

• size evaluation has to be provided with a probabilistic approach (i.e. with 95% of probability the size will be smaller than ...)

• library to be provided as part of PDGS development ==> expert knowledge required


• separate MP system will be procured as separate competitive tender

• Output: – fully operational system– support to integrate the system into the PDGS– support to commissioning phase



• systematic planning, no conflict management due to user requests

• procurement as separate tender by Eumetsat



• ESA will provide mission CFIs for orbit propagation and for the ingestion of FOS orbit files

• S-1 On-board data compression algorithm description provided as CFI

Procurement CFI


Sentinels PDGS: Best Practices for the Selection of Subcontractors

Luc Govaert

RES-POE


Code of Best Practices, Definition and Governing Principles/Purpose of Best

Practices

ESA has a Code of Best Practices, approved by the Industrial Policy Committee as industrial policy ruling.

Definition of Best Practices: Basically, a mechanism through which a Prime selects subcontractors for a given element within an ESA programme prior or subsequent to his own selection by ESA.

The principle and purpose of Best Practices is to achieve fairness of competition at all levels (Prime and subcontractors) and to guarantee fair, impartial and equal treatment of non-primes.

1. Best Practices


PDGS Best Practices: Origin and Extent

Statement in the ESA Procurement Plan approved by IPC: “The ESA Best Practices may be followed for some elements within the PDGS Core Procurement.”

The bulk of the Sentinels PDGS procurement will be placed further to ESA ITTs, only a limited part through Best Practices (up to 40%).

ESA will decide which elements of a given procurement will be awarded through Best Practices.

2. Best Practices


3. Best Practices

ESA shall have full visibility on the ITT preparation by the Prime (ITT package to be approved by the Agency), on the evaluation and on the selection (Prime’s recommendation will be submitted to ESA; ESA will either endorse the recommendation or request to submit the recommendation for decision to a Joint ESA/Industry Procurement Board), with the right to audit the full process.

The Prime shall have to state his acceptance of the Best Practices principles and of his obligation to organize Best Practices.

Implementation and Guarantees to ensure Fairness of Competition (I)


3. Best Practices

To guarantee impartiality, the Prime shall be required to accept and cooperate with the Agency’s Industrial Ombudsman.

The Prime shall have to implement a SIMPLIFIED Best Practices selection procedure drafted by ESA and based on the principles of fair and open competition (procedure will be included in the ESA ITT package).

IITT and ITT to be approved by the Agency and issued on EMITS (EXTERNAL ENTITIES) and CORDIS.

Implementation and Guarantees to ensure Fairness of Competition (II)


3. Best Practices

Conflict of interest: If the Prime and/or any subcontractor wish to bid for any element, the Prime/subcontractor shall be excluded from the evaluation of the proposals, this in the interest of impartiality and the Agency shall run the TEB.

Same applies in case of companies belonging to the same industrial and/or legal organisation, or affiliated companies, meaning any form of association giving a company a vested interest in the outcome of the evaluation. However, the Prime’s responsibility vis-à-vis selected subcontractor is left untouched.

Implementation and Guarantees to ensure Fairness of Competition (III)


3. Best Practices

ESA Staff may be involved in the Tender Evaluation Board set up by the Prime (one Technical Representative, ESA CO at his discretion). Notwithstanding this, the Agency at any moment reserves the right to initiate a parallel evaluation performed by its Staff in accordance with the ESA tender evaluation process.

Confidentiality of proposals submitted will have to be guaranteed by the Prime.

The SoW/technical requirements, to be written by the Prime and to be reviewed and approved by the Agency, shall not be ambiguous or company tailored.

The selection criteria shall be defined and made available to all potential bidders.

Implementation and Guarantees to ensure Fairness of Competition (IV)


Sentinels PDGS

Schedule and way forward


The Payload Data Ground Segment undergoes a complete ESA system engineering lifecycle

The following reviews are defined:

• PDGS System requirements : Definition of the PDGS core procurement technical baseline

• PDGS Preliminary Design (supported by the core PDGS team): the review is performed at facility specification, architecture and interface level

• PDGS Critical design review and Qualification reviews (supported by the core PDGS team): These reviews characterise the reference system integration and centres deployment statuses

• PDGS Acceptance review (supported by the core PDGS team): The review characterise the integration with the GMES Service Projects shall be verified

Sentinels PDGS Engineering life-cycle


The Core PDGS prime supports the Ground Segment milestones (PDR, CDR, AR) where coherencies between Satellite, FOS and PDGS systems, interfaces

and operations are reviewed

Highlight on PDGS System Requirements review -> Technical Documentation package based on:

System requirement documentsOperation concept documentSystem technical budget

• Updated technical documentation will be publicly released following the review recommendation updates:

S-1: Released on EMITS end of May (board is 20 May…)S-2, S-3: Released together with intended ITT announcement

• Technical Baseline may be consolidated for the ITT without pre-announcement

Sentinels PDGS Engineering life-cycle 2/2


S-1 PDGS SRR: On-going: Panel Collocation foreseen for 7th May 2009

S-1 PDGS core ITT: end July 2009

S-2 PDGS SRR: Nov. 2009

S-2 PDGS core ITT: Feb. 2010

S-3 PDGS SRR: July 2009

S-3 PDGS core ITT: Oct. 2009

PDGS Core Indicative Schedule


Demodulator & FEP: Sept. 2009Precise Orbit Determination: ITT Dec. 2009

S-1 Mission Planning : PDGS core KO + 3 monthsS-1 Instrument Performance Monitoring, QC and cal/val elements:

PDGS core KO + 3 months

S-2 Mission Planning : ITT March 2010S-2 Processors and performances elements : PDGS core KO + 3 months

S-3 Mission Planning : March 2010S-3 Processors and performances elements : PDGS core KO + 3 months

PDGS Facilities Indicative Schedule


Questions and Answers

Questions can be e-mailed to [email protected]

…until May 18st 2009

Answers to questions will be published on EMITS News, towards end of May


Summary


Information Day Highlights 3 independent ITTs for 3 sentinel PDGS development contracts

Including best practices for few sub-systems (mission planning, processors and mission performances elements)

… ITTs for common elements (FEP, POD)

Drivers for ‘operational’ systems delivery

Re-use of proven technology & interfaces

Sentinels are part of the GSC overall and share the data flows and interface

Systematic generation of all data into lvl1b and retrieval on-line is a challenging technical driver to cope with the high data volume

ITT organisation

ITTs Issued and open both via ESA and EC contract systems

Response to, Selection and Mgt according to normal ESA procedures

Process is ready to start

Sentinels PDGS Industry Information Day, 5 May 2009, pg. 1 GMES Space Component Sentinel Payload...

Documents

Transcript of Sentinels PDGS Industry Information Day, 5 May 2009, pg. 1 GMES Space Component Sentinel Payload...