slide1
Download
Skip this Video
Download Presentation
GMES Space Component Sentinel Payload Ground Segment Industry Information Day

Loading in 2 Seconds...

play fullscreen
1 / 106

GMES Space Component Sentinel Payload Ground Segment Industry Information Day - PowerPoint PPT Presentation


  • 125 Views
  • Uploaded on

GMES Space Component Sentinel Payload Ground Segment Industry Information Day. Purpose of the Mtg. 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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' GMES Space Component Sentinel Payload Ground Segment Industry Information Day' - rianne


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

GMES Space Component

Sentinel Payload Ground Segment

Industry Information Day

slide2

Purpose of the Mtg

  • 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
slide3

Sentinels PDGS Industry Information Day

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

Sentinels PDGS

S-1 Payload Data Ground Segment (PDGS)

S-2 and S-3 PDGS

Procurements way forward

Best practices

Schedule and way forward

slide5

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)
slide6

GMES dedicated missions: Sentinels

Sentinel 1 – SAR imaging

All weather, day/night applications, interferometry

Sentinel 2 – Multispectral imaging

Land applications: urban, forest, agriculture, etc Continuity of Landsat, SPOT data

Sentinel 3 – Ocean and global land monitoring

Wide-swath ocean color, vegetation, sea/land surface temperature, altimetry

Sentinel 4 – Geostationary atmospheric

Atmospheric composition monitoring, trans-boundary pollution

Sentinel 5 – Low-orbit atmospheric

Atmospheric composition monitoring

2011

2012

2012

2017+

2019+

slide7

Sentinel-1

Sentinel-1:

C-band

SAR mission

slide8

Sentinel-2

Sentinel-2:

Superspectral imaging mission

slide9

Sentinel-3

Sentinel-3:

ocean & global land mission

slide11

Sentinel-4

Sentinel-4:

GEO atmospheric mission

slide12

Sentinel-5

Sentinel-5:

LEO atmospheric mission

slide13

Sentinel-1

Sentinel-3

GCM GS

GCM GS

GCM GS

GCM GS

GCM GS

GCM GS

GMES Ground Segment and Data Access

ISPs

TM/TC

GMES

Space

Component

Acquisition Stations

TT&C Stations

Sentinels PDGS

FOS

GMES Contributing Missions GS’s

(ESA, EUMETSAT, NOAA, national member-states missions, etc…)

GMES Sentinels GS

GSC Coordinated

Data Access System

USER Segment

GSC

Data Request

GSC

Data Provision

GMES Service Segment

Final end-user information products

slide14

GSC implementation schedule

Preparatory programme

Build-up phase

(Segments 1 + 2)

Operational programme

2004

2005

2006

2013

2014

2023

slide15

Content of GSC programme

  • Sentinel-1 A: Phase B2/C/D/E1. Sentinel-1B: up to flight readiness
  • Sentinel-2 A: Phase B2/C/D/E1. Sentinel-2B: up to flight readiness
  • Sentinel-3 A: Phase B2/C/D/E1. Sentinel-3B: 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)

Segment 2

slide16

GSC Data Access Status today

First Set of data requirements consolidated in May 08GMES Fast Track Pilot Services & Urban Atlas (Start Sep08-Apr09)Several Requirements Review loops and updatesGSCDA 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 MissionsEU Agency interfaces being discussedRequirements strongly evolved and evolve

gscda pre operations status
GSCDA Pre-operations Status

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

Deployed DataSets

Help Desk Statistics

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

Delivered Products

gscda system infrastructure development
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

slide19

Requirements Vs Architecture

GSC shall respond to all current and expected (*1) requirements. Accordingly the Sentinel GS will consist of a ESA Sentinel Core Ground Segment (*2)andCollaborative 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)

slide20

Main GSC GS Design / Development Drivers

High Data VolumeOperational Data Delivery from Beginning - Maximum ‘systematic’ functions - Simple, easy design - highest reliability for E2E data access for usersFlexibility (Without impact of systematic functions) - clear interfaces to complementary GS functions - Re-processing as part of system budgetsSentinel PDGS Integration into an already ‘operational’ GCM service, during commissioning

slide21

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

slide22

Funding and Procurement

ESA-only funded elements andESA-EC joint-funded elements

Open to

ESA Member States and ESA- Member States and EC FP7 participating States

Issued via

ESA Emits and ESA- Emits and EC Cordis

Managed by

ESA (and ESA procedures *)

* No georeturn targets but georeturn reporting

slide24
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
slide25

GSC Ground Segment infrastructure

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)

slide26

GSC Core Ground Segment Services (1/2)

Space Segment operations

Sentinels TT&C data uplink and downlink (S-band link)

Sentinels satellites commanding & control

Mission exploitation

Sentinels 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.

slide27

GSC Core Ground Segment Services (2/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

slide28

Sentinels PDGS Drivers

  • High data rates and on-ground volumes to be managed
  • 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

slide29

Sentinels PDGS infrastructure and services

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

Sentinels data acquisition

Demodulation and front end processing elements

Sentinels Mission planning

Systematic and rush generation of mission data products

Production 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 control

Instrument 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

slide30

Sentinels PDGS Development logic

  • 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
slide31

Sentinels PDGS Procurement 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 centres

Overall verification

Phase 4:

Commissioning operations

Maintenance of PDGS system during commissioning

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 centres

Overall verification

Commissioning operations

Maintenance of PDGS system during commissioning

Procurement of the centres according to PDGS interfaces specifications

Commissioning operations

Part of current ITT

Part of operations ITT in 2010

slide33

Sentinels PDGS Procurement Sizing

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

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

slide34

Sentinels PDGS Invitations to Tender:

proposal requirements & selection

O. Leonard

RES-POE

1 publication of itt
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
2. Content of ITT Package
  • Cover letter
  • Statement of Work
  • Draft Contract
  • Special Conditions of Tender
content of itt package
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)
content of itt package1
Content of ITT Package

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)
content of itt package2
Content of ITT Package

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
content of itt package3
Content of ITT Package

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
3. Evaluation process

ESA evaluation procedure applicable

  • Evaluation criteria
  • TEB (incl. EC)
  • Contract negotiation
  • Award of contract
  • Regret letter and debriefing
slide42

Sentinel-1 PDGS

Procurement Overview

slide43

1

80 Km

200 Km

2

360

3

4

100 Km

5

Sentinel-1 Mission Overview

Main Mission Objectives & Characteristics

  • 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.

Orbit: Near Polar Sun-Synchronous

Repeat cycle: 12 days. 175 orbits

Payload: C-Band Synthetic Aperture Radar (central frequency 5.405 GHz)

Constellation: Sentinel-1 system will be composed of two satellites, Sentinel-1 A & B

Duty cycle: up to 25 min in high rate mode and the rest of the orbit in WV mode

Schedule (Sentinel-1A): Launch Q4 2011

slide44

S-1 PDGS Key Design & Operations Drivers

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

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

slide45

X-Band

Acquisition Service

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

Long-term data

archiving service

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 & FEP

Centres Commissioning

Operations

Precise Orbit

Determination

User services

Auxiliary data

handling service

Sentinel-1 PDGS Implementation Contracts

Generic services

at PDGS centres

Sentinels Common Elements/Facilities

S-1 Core PDGS

S-1 PDGS specific

Future Procurements

(2010)

Service provided as part of a future “Stations & Centres” procurement activity

Future Procurements

Generic ESA

multi-mission services

Service provided as part of customisation of Multi-mission services

S-1 Specific Elements

On-going separate procurements

S-1 IPF

slide46

Info Day Scope

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

User services

Auxiliary data

handling service

Scope of this presentation

Sentinel-1 PDGS Implementation Contracts

Generic services

at PDGS centres

Sentinels Common Elements/Facilities

S-1 Core PDGS

S-1 PDGS specific

X-Band

Acquisition Service

Future Procurements

Long-term data

archiving service

Demodulator & FEP

Centres Commissioning

Operations

Generic ESA

multi-mission services

Precise Orbit

Determination

Service provided as part of customisation of Multi-mission services

S-1 Specific Elements

S-1 IPF

slide47

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

Mission Planning

Instrument

Performance Monitoring,

QC and cal/val

Procured through Best Practices within the Core PDGS

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

S-1 Core PDGS

S-1 elements/facilities

implementation

S-1 PDGS System maintenance

S-1 PDGS Reference Facility

PDGS System

end-to-end Design

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

Maintenance activities till end Commissioning Phase

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

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

Mission Planning

Instrument

Performance Monitoring,

QC and cal/val

L0 generation

Data Assembly

Processing control

Support to GS OSV

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

slide48

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

  • 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

slide49

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 Document

Provides 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 Document

Describes 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 ICD

Defines the main internal and external interfaces of the S-1 PDGS

    • S-1 PDGS System Technical Budget

Describes a set of observation scenarios for system sizing purposes

    • S-1 PDGS System Test Concept

Provides the guidelines PDGS testing

slide50

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

  • 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
slide52

Sentinel-2 Mission Overview

Sentinel-2:

Superspectral imaging mission

slide53

Sentinel-2 PDGS Drivers

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

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

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

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

On-line access to past mission data

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

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

slide54

Sentinel-3 Mission Overview (1/2)

Sentinel-3:

ocean & global land mission

slide56

Sentinel-3 PDGS Drivers

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

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)

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

Direct access to past mission data

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

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

slide57

Sentinel-2 PDGS Implementation Contracts (1/2)

Generic services

at PDGS centres

Sentinels Common Elements/Facilities

S-2 Core PDGS

S-2 PDGS specific

Future Procurements

(2010)

Service provided as part of a future “Stations & Centres” procurement activity

Future Procurements

Generic ESA

multi-mission services

Service provided as part of customisation of Multi-mission services

S-2 specific elements procurement

slide58

Info Day Scope

Scope of this presentation

Sentinel-2 PDGS Implementation Contracts (2/2)

Generic services

at PDGS centres

Sentinels Common Elements/Facilities

S-2 Core PDGS

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

X-Band

Acquisition Service

Future Procurements

Long-term data

Archiving

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-2 PDGS System maintenance till the end of the Commissioning Phase

Demodulator & FEP

Centres Commissioning

Operations

Generic ESA

multi-mission services

Precise Orbit

Determination

User services

Auxiliary data

handling service

S-2 specific elements procurement

S-2 Mission Planning

slide59

Info Day Scope

Scope of this presentation

Sentinel-3 PDGS Implementation Contracts

Generic services

at PDGS centres

Sentinels Common Elements/Facilities

S-3 Core PDGS

X-Band

Acquisition Service

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

Future Procurements

Long-term data

Archiving (land)

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-3 PDGS System maintenance till the end of the Commissioning Phase

Centres Commissioning

Operations

Demodulator & FEP

Generic ESA

multi-mission services

Precise Orbit

Determination

User services

Auxiliary data

handling service

PDGS EUMETSAT

Elements

S-3 specific elements procurement

S-3 Mission Planning (EUMETSAT)

Marine User Access

Marine processing and

long term

Archive centre

slide60

S-2 PDGS AIV

Integration and Testing activities leading to PDGS Acceptance.

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

Sentinel-2 Core PDGS Contract Scope

S-2 Core PDGS

Specific S-2 elements/facilities

Development

S-2 PDGS System maintenance

S-2 PDGS Reference Facility

PDGS System

end-to-end Design

Maintenance activities till end Commissioning Phase

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

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

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

Instrument

Processing Facility

Instrument

Performance Monitoring,

QC and cal/val

L0 generation

Data Assembly

Support to GS OSV

Processing control

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

Procured through Best Practices within the Core PDGS

slide61

Sentinel-3 Core PDGS Contract Scope

S-3 Core PDGS

Specific S-3 elements/facilities

Development

S-3 PDGS System maintenance

S-3 PDGS Reference Facility

PDGS System

end-to-end Design

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

Maintenance activities till end Commissioning Phase

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

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

S-3 PDGS AIV

Instrument

Processing Facility

(Land & Marine)

Integration and Testing activities leading to PDGS Acceptance.

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

Instrument

Performance Monitoring,

QC and cal/val

L0 generation

Data Assembly

Support to GS OSV

Processing control

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

Procured through Best Practices within the Core PDGS

slide62

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 Document

Provides 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 Document

Describes 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 ICD

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

    • S-2/3 PDGS System Technical Budget

Describes a set of observation scenarios for system sizing purposes

    • S-2/3 PDGS System Test Concept

Provides the guidelines PDGS testing

slide63

Sentinel-2 / Sentinel-3 ESA CFIs

  • Satellite and FOS Interfaces Documents
  • Detailed processing model and reference test data
  • Sample satellite Test Data
  • S2 Decompression Software & all related documentation
slide64

Sentinels PDGS

Demodulator and

Front End Processor

technical assessment and market survey
Technical Assessment and Market Survey
  • 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).
slide66

The Scope of the Procurement

Main Sub-elements

  • MODEM  Demodulator and Modulator
  • FEP  Front End Processor
slide67

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.
slide68

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
slide69

Sentinel PDGS

Precise Orbit Determination

slide70

GMES POD Service Objective

The GMES Precise Orbit Determination (POD) Service shall provide orbit products to the Sentinels 1, 2 and 3 missions for supporting the PDGS operations

slide71

GMES POD Service Functions

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
slide72

GMES POD System - Context

Two entities:

  • NRT POD
  • OFL POD

S-3 Specific

slide74

GMES POD Project Objectives

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
slide75

GMES POD - Procurement Approach

  • 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
slide76

Sentinels PDGS

S-2, S-3

Operational Instrument Processors

and Cal/Val and Quality tools

slide77

Procurement objectives

  • Procurement will cover :
    • Processors for Sentinel-2 and Sentinel-3 productsIPF – Instrument Processing Facility
    • Quality Tools for Sentinel-2 and Sentinel-3

Cal/Val tools, QC tools

  • Sentinel-1 processor covered by previous contract

(already initiated)

slide78

Sentinel-3: Optical Sensors Processing

L1 IPF SLSTR

L1 IPF

OLCI

Level 1

IPFs

L1C IPF SLSTR/OLCI

L1B

L1B

L1C

Combined

OLCI/SLSTR

L2 IPF

OLCI

L2 IPF SLSTR

Level 2

IPFs

L2 IPF SLSTR/OLCI

SST

Land surface

product

Water

products

Land

products

Surface Directional

Reflectances

slide80

Sentinel-2: Instrument Processor Facility

IPF L1

L1B

DEM

CFI

L1C orthorectified product

IPF L2

Atmospheric correction.

slide81

IPF: Engineering approach

  • Input from ESA

Baseline for IPF development

    • Detailed Processing Model L1 / L2
    • Input Output Data Description
    • Test 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

Operational

development

ESLs

Algorithms Engineering

Algorithms Specification

S2 / S3

IPF

S2 / S3 prototypes

ESA

Algorithm definition and prototyping contracts

Operational implementation contracts

Algorithm Specifications

and prototyping

Software

Processors ICDs

slide82

Procurement Scope

  • IPF main input
    • Level 0
    • Aux files (including orbit files)
    • Orders files
  • IPF main output
    • Level 1 products
    • Level 2 products
    • Basic Level 3 products
    • Browse / catalogue
  • Cal/Val and quality tools
    • Calibration and validations functions
    • Initial analysis and monitoring functions
    • Reporting functions
slide83

Procurement Organization

  • 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
slide84

Sentinels PDGS

Mission Planning

slide85

Procurement Scope

  • 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
slide86

Mission Planning Interfaces

  • 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
slide87

Mission Planning: S-1

  • 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
variable compression algorithm
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
slide89

Mission Planning: S-2

  • 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
slide90

Mission Planning: S-3

  • systematic planning, no conflict management due to user requests
  • procurement as separate tender by Eumetsat
slide91

Procurement CFI

  • 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
code of best practices definition and governing principles purpose of best practices
Code of Best Practices, Definition and Governing Principles/Purpose of Best Practices

1. 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.
pdgs best practices origin and extent
PDGS Best Practices: Origin and Extent

2. Best Practices

  • 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.
3 best practices
3. Best Practices

Implementation and Guarantees to ensure Fairness of Competition (I)

  • 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.
3 best practices1
3. Best Practices

Implementation and Guarantees to ensure Fairness of Competition (II)

  • 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.
3 best practices2
3. Best Practices

Implementation and Guarantees to ensure Fairness of Competition (III)

  • 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.
3 best practices3
3. Best Practices

Implementation and Guarantees to ensure Fairness of Competition (IV)

  • 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.
slide99

Sentinels PDGS

Schedule and way forward

slide100

Sentinels PDGS Engineering life-cycle

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 andinterface 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
slide101

Sentinels PDGS Engineering life-cycle 2/2

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 documents

Operation concept document

System technical budget

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

S-1: Released on EMITSend 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
slide102

PDGS Core Indicative Schedule

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

slide103

PDGS Facilities Indicative Schedule

Demodulator & FEP: Sept. 2009

Precise Orbit Determination: ITT Dec. 2009

S-1 Mission Planning : PDGS core KO + 3 months

S-1 Instrument Performance Monitoring, QC and cal/val elements: PDGS coreKO + 3 months

S-2 Mission Planning : ITT March 2010

S-2 Processors and performances elements : PDGS core KO + 3 months

S-3 Mission Planning : March 2010

S-3 Processors and performances elements : PDGS core KO + 3 months

slide104

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

slide106

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

ad