GS Overview: Responsibility & Location SMOS Ground Segment Kiruna (ESRANGE) S-band Villafranca (ESAC) X-band Toulouse (CNES) Satellite Operations Ground Segment (SOGS) Payload Operations and Programming Centre (PLPC) Processing Ground Segment (DPGS) Platform Software Payload Software Centre Aval Traitement des Donnees SMOS (CATDS) Auxiliary Providers Users 1
GS Overview: DPGS Locations User Services User Requests Auxiliary Providers X-Band Long Term Archive Long term archive User services interface Reprocessing: Level 1, 2 Quality Assessment Monitoring Fast Processing Centre Acquisition Processing: Level 0, 1, 2 Instrument planning Quality Assessment Monitoring TBD Distribution Villafranca (ESAC) 2
GS Overview: DPGS Elements 1/4 S-band X-band Auxiliary Providers DPGS Fast Processing Centre Long Term Archive SOGS XBAS Level 0 Reprocessing Centre PLPC PXMF CEC PDPC Core Level 1 Level 1 Level 2 SPQC MF SPGF Refer. Processor Level 2 SPQC MF IAT Local Archive Dissem. Multi-mission Facility Infrastructure Reports USERS Subscriptions On-request Multi-mission User Services 3
GS Overview: DPGS Elements 2/4 SPGF XBAS PXMF Operational Processors PDPC Core CEC SPQC MF IAT Reprocessing Centre MMFI MUS ADPs SMOS Plan Generation Facility: Instrument and acquisition planning information X-Band Acquisition System: 3.5 meter receiving antenna plus front end equipment (source packet stream separated by APID number). Includes a FEP-AIT for testing spacecraft to ground segment interface. Payload X-Band Monitoring Facility: Part of PLPC development. Provides a means for the operator to monitor the X-Band telemetry. Level 0, Level 1, and Level 2. Each one a separate development. Payload Processing Centre Core: provides the ground station with an operator interface, a local archive, an inventory, a catalogue, control and monitoring of subsystems. Responsible for triggering the processors, managing the data flow, and performing data distribution. Calibration Engineering Centre: product quality, calibration and validation tools, system level monitoring. SMOS Product Quality Control: simple quality checks (file format validity, flag checks, ) performed. Products not disseminated unless they pass the SPQC controls. Monitoring Facility: automated functions generating reports. Interactive Analysis Tool: functions generating reports that require input from an expert. Installation of the Level 1 operational processor, Level 2 operational processor, SPQC and MF within the LTA for use in performing a reprocessing campaign. Multi-Mission Facility Infrastructure: same function as the PDPC Core but in a multi-mission context at the LTA. Provides interface to Multi-mission User Services and performs the bulk of the data distribution. Multi-mission User Services: standard ESA service to users: data ordering, provision, help desk, mission information, Auxiliary Providers: external data to the mission (at least ECMWF but maybe others as well) 4
GS Overview: DPGS Elements 3/4 Other DPGS or DPGS related elements: SMOS Viewer: widely distributed tool for viewing SMOS products; basic field/array viewer plus some specific functions for SMOS data XML schemas: widely distributed schemas for SMOS data files; BinX language used for binary data representation XML read/write APIs: widely distributed software that will efficiently read and write SMOS data files; useful for those wanting to develop applications using SMOS data Processor prototypes: Level 1, Level 2 SM, Level 2 OS SEPS: SMOS End-to-end Performance Simulator, developed for instrument testing, source of test data MIRASIM: MIRAS Simulator, used for operations preparation (SPGF- PLPC testing) 5
GS Overview: DPGS Elements 4/4 DPGS Element FPC LTA DPGS Element FPC LTA XBAS CEC X-band acquisition, RF conversion Systematic Product Quality Control (QC) Front End Processor (FEP), Monitoring Facility (MF) Rolling buffer archive Level 0 Product Generation Interactive Analysis Tool (IAT) Payload X-Band Monitoring (PXMF) Processing Infrastructure, Inventory Local Archive Long Term Archive (LTA) External Product Dissemination Master User Services Monitoring and control Local User Services SMOS Viewer XML schema/tools Level 1 Processor Level 2 SM Processor Payload Programming Centre (PLPC) Level 2 SSS Processor SMOS Planning Generation Facility (SPGF) FPC = Fast Processing Centre (ESAC) LTA = Long Term Archive (location TBD) 6
GS Overview: DPGS Schedule Constraints DPGS must be ready for GSOV (overall verification) by end of February 2007 : DPGS version 1 All subsystems not available for DPGS version 1 shall be replaced by simulators in order to allow all subsystem interfaces to be tested Full scientific functionality (latest processing algorithms, cal/val tools) will only be available for launch : DPGS version 2 LTA must be ready for GSOV by end of June 2007 (archiving, user services, data dissemination); completed reprocessing centre is needed only for the end of commissioning ESAC site infrastructure shall be available by the end of summer 2006 ESAC network infrastructure shall be available by the end of 2006 Schedule for GSOV involving DPGS compressed relative to recent missions: precise planning and heavy coordination required to make this a success 7
GS Overview: DPGS Requirements 1/2 Given the limited time available for development the intent is to encourage re-use of existing components and interfaces (% re-use of existing system) XBAS (90%): standard turn-key system (track an existing CNES satellite using a similar X-Band transmitter) PDPC Core (50%): same basic functional requirements as PDS for Cryosat and GOCE (generic thin layer interface imposed) PLPC/PXMF (95%): use of SCOS2000 imposed SPGF (75%): same basic functional requirements as planning system used for Cryosat and GOCE SPQC (25%): same basic functional requirements as quality control system used for Cryosat MF (90%): same basic functional requirements as monitoring facility for Cryosat and GOCE Viewer (80%): same core functional requirements as EnviView, CryoView 8
Performance: GS Overview: DPGS Requirements 2/2 The DPGS at ESAC shall process 36 hours of full polarisation data to Level 2, from acquisition to ingestion, in 24 hours. The DPGS at ESAC shall process 60 hours of dual polarisation data to Level 2, from acquisition to ingestion, in 24 hours. The Reprocessing Centre shall be capable of processing and distributing one year of SMOS data in one month. Operations: Automated whenever possible. At ESAC, one shift, working days only: expectation is one person DPGS and one person SPGF/PLPC Test data: No CFI for system acceptance; prime is responsible for test data generation CFI will be provided for Level 1 and 2 processor algorithm verification Satellite data will be provided as CFI when available and shall be used to verify the interface with the ground segment 9
GS Overview: Indra Espacio Contract S-band X-band Auxiliary Providers GMV (E): PLPC/PXMF, SPGF, L0, L1, L2, SPQC, CEC specific functions SOGS PLPC SPGF XBAS PXMF CEC Refer. Processor SPQC MF IAT Fast Processing Centre Level 0 PDPC Core Level 1 Level 2 Local Archive Dissem. DPGS Long Term Archive Reprocessing Centre Level 1 Level 2 SPQC MF Multi-mission Facility Infrastructure INSA (E): system engineering support SMP (F): front end processing/demodulators Deimos (E): MF Innoware (DK): PLPC database Vega (UK): Viewer Array (CDN): SM L2 Indra Espacio responsibility Reports USERS Subscriptions On-request Multi-mission User Services ACRI (F): OS L2 Scientific Experts: L2 10
GS Overview: Other Procurements LTA system engineering ITT (open tender, March 2006); contractor identified by the end of May, work started in June LTA site selection/operations ITT (open tender, May 2006); site identified by the end of July, work started in September, LTA installation starts in late 2006, operators available for GSOV support by mid-2007. ESAC operations ITT (open tender, September 2006) ); operators needed to support GSOV starting in February 2007 ESAC scientific operations team ITT (open tender, early 2007); team needs to be in place at ESAC for launch DPGS maintenance ITT (open tender, summer 2007); covering maintenance after the commissioning phase DPGS evolution ITT (open tender, summer 2007); covering evolution after the commissioning phase 11
GS Overview: DPGS V1 System Level KO 16 Aug 05 KO Design SRR PDR CDR Design Subsystem Level ICDs, Constraints CDR Tools, Test data Implementation Implementation & Test Sept 06 FAT System Integration Delivery Jan 07 Acceptance Testing 01 Mar 07 DPGS V1 = full functionality except : preliminary L1 processor simulated L2 processor GSOV only limited specific functionality in the CEC 12
GS Overview: DPGS V2 DPGS V2 = full functionality Processors Level 1 Level 2 Level 1 &2 System Level System Integration + Maintenance + Evolution Commissioning V1 OSAT 01 Mar 07 Launch End of commissioning Deliveries Jan 06 Definition CEC Specific Functionality Implementation & Test 13
GS Overview: CEC 1/4 Calibration Engineering Centre (CEC) The CEC main objective is to monitor and improve the ultimate quality of the mission output. It is not a single system but should be considered a collection of tools. Tools requiring systematic access to data need to be located at ESAC and/or the LTA with their outputs available to users regardless of their location. Tools that are user driven will be distributed to users or remotely accessible. 14
GS Overview: CEC 2/4 Functionality Verification Mission Verification Quality Assessment Cal/Val Processing Interactive Analysis Description Systematic check of files before they are sent to users. Objective is to avoid sending unusable data. Monitor the overall performance of the ground segment. Objective is to confirm that the DPGS is performing what it is expected to do. Collection of information needed for scientific analysis of the mission outputs. Objective is to synthesise the outputs to yield a more manageable volume of data. Generate information required to systematically tune instrument and processing parameters. Objective is to automate, where possible, the calibration process. Environment that allows processing algorithms to be modified and run in order to generate local test products. Objective is to speed the algorithm/product improvement. Take input from an expert user in cases where a decision is required. Objective is to recognise that an expert s assessment will be required in certain cases. = Largely undefined (ideas welcome) 15
GS Overview: CEC 3/4 SMOS Product Quality Control (SPQC) Integrated into the operational data processing chain Performance is important Simple checks only Auxiliary Processing Products Archiving Distribution to Users Check point Products & Auxiliary from PDPC to web SPQC Detailed reports to PDPC Check result: good = send bad = do not send Typical checks: file format internal consistency internal product confidence geolocation.etc 16
GS Overview: CEC 4/4 Monitoring Facility (MF) Automatically receives inputs from PDPC but not part of operational chain Can be used for any function that can be automated Proven infrastructure allowing plug-in of specific functions (IDL Tool-box) IDL Tool-box Files Retrieval configuration, scheduling configuration, scheduling Report Distribution ftp server web site e-mail Long Term Analysis configuration Ingestion Triggering User Supplied Function Report Distribution Triggering configuration Reports & Products & Auxiliary & etc.. from PDPC MF parameter configuration File Ingestion Module parameter configuration base Report Generation Module Report Generation Triggering parameter configuration configuration, scheduling to web Detailed reports configuration, scheduling base Compression / Clean-up database table definition 17
GS Overview: Flow 00 03 06 09 12 15 18 21 00 03 06 09 12 15 18 21 00 03 06 ESAC acquisitions download time [min] 10 5 not used used data processing available from ESAC 10 to 23 hours after sensing. sensing period ~19:40 ~19:40 ~18:30 ~04:00 last product available first product available Note if both ascending and descending passes were used; availability would be reduced to 5 to 13 hours after sensing. Acquisition during descending passes at ESAC using 3.5 metre X- band antenna procured for SMOS All fast processing performed at ESAC Subset of data distribution from ESAC to users from LTA would be available 1 to 3 days later 18
GS Overview: NRT Mission? 1/4 SMOS Near Real Time Mission? Motivation: Land models in weather forecasting will be improved by including satellite soil moisture measurements. The improvements will be most significant if the delay between observation and forecast time can be minimised. Action from February PBEO and ECMWF to analyse feasibility and cost for two scenarios: Scenario 1) Availability of products < 3 hours after sensing Scenario 2) Availability of products < 8 hours after sensing Results of preliminary study presented to DOSTAG in April. 19
GS Overview: NRT Mission? 2/4 Scenario 1: Svalbard replaces ESAC for acquisitions available from ESAC 1 to 3 hours after sensing Acquisitions performed at Svalbard using an existing antenna and upgrading for the 8PSK demodulation scheme Raw data transferred from Svalbard by high-speed link to ESAC for fast processing at 4 times NRT. ESAC antenna becomes a back-up 20
GS Overview: NRT Mission? 3/4 Scenario 2: Gatineau complements ESAC available from ESAC 1 to 7 hours after sensing Note: Prince Albert is also a feasible alternative but lacks network infrastructure. Acquisitions performed at ESAC and at Gatineau using an existing antenna upgraded for the 8PSK demodulation scheme Raw data transferred from Gatineau by high-speed link to ESAC for fast processing 21
GS Overview: NRT Mission? 4/4 Either scenario can be incorporated into the ground segment design but the technical risk depends strongly on the go-ahead decision date. A late decision (shortly before launch) will take much longer to implement (ready half way through operations phase) and will be more expensive to implement (testing becomes much more difficult). Both scenarios introduce limited technical risk to the on-going development at ESAC. Both scenarios give the mission redundant acquisition; removing the ESAC antenna as a single point of failure. DOSTAG will recommend SMOS NRT to PBEO in September provided there is a clear show of support for this initiative from the SMOS user community. 22