sentinels pdgs demodulator and front end...
Post on 09-Feb-2021
2 Views
Preview:
TRANSCRIPT
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 1
Sentinels PDGS
Demodulator andFront End Processor
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 2
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 3
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 ModulatorFEP Front End Processor
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 4
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 activitiesAIV (Factory and on-Site) activitiesManagement 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 marketMulti-mission programmable demodulators (based on standards) and front end processing systems.
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 5
Quotation and Delivery
Core Stations ApproachThe 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 ApproachThe bidder(s) need to provide a quotation showing the benefits of recurrent units (including maintenance):
Available to Local Stations at recurrent priceAs an option, ESA could procure the units and provide them to the Local Stations
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 6
Sentinel PDGS
Precise Orbit Determination
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 7
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 8
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 9
GMES POD System - Context
Two entities:- NRT POD- OFL POD
S-3 Specific
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 10
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 11
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 12
- 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 Industry Information Day, 5 May 2009, pg. 13
Sentinels PDGSS-2, S-3
Operational Instrument Processorsand Cal/Val and Quality tools
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 14
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 15
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
SST Land surface productSurface Directional Reflectances
Level 1IPFs
Level 2IPFs
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 16
Sentinel-3 : Altimetry Processing
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 17
Sentinel-2: Instrument Processor Facility
IPF L1
IPF L2
L1C orthorectified product
Atmospheric correction.
L1B
DEMCFI
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 18
Operational developmentESLs
Input from ESABaseline for IPF development
Detailed Processing Model L1 / L2 Input Output Data DescriptionTest data setGeneric Interface SpecificationECSS standard
NB: DPM / IODD / TDS provided by “Prototype contracts”
DeliveriesSoftware – code, exeDocumentation (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 Specificationsand prototyping
•Software•Processors ICDs
Algorithm definition and prototyping contracts Operational implementation contracts
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 19
IPF main inputLevel 0Aux files (including orbit files)Orders files
IPF main outputLevel 1 productsLevel 2 productsBasic Level 3 products
Browse / catalogue
Cal/Val and quality tools Calibration and validations functionsInitial analysis and monitoring functions Reporting functions
Procurement Scope
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 20
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 observationproducts expertise
Incremental procurement according to mission schedule Maintenance until end of commissioning phaseSupport to commissioning phase, maintenance of reference chain
Procurement Organization
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 21
Sentinels PDGS
Mission Planning
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 22
• 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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 23
• 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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 24
• 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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 25
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
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 26
• 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
Mission Planning: S-2
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 27
• systematic planning, no conflict management due to user requests
• procurement as separate tender by Eumetsat
Mission Planning: S-3
-
Sentinels PDGS Industry Information Day, 5 May 2009, pg. 28
• 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
top related