E. Tilmans 34 April 2003 Page 1

1
Operations Plan

• Mission Entities.
• User Data Request/Deliver Scheme.
• CHRIS and HRC Operations Description and
  Constraints.
• Technology experiments.
• Kiruna ESRANGE downlink capability.

2

• Mission Entities
• ESTEC TOS-E - Overall PROBA Mission
  responsibility.
• PROBA Steering Group chaired by ESTEC TOS-ES -
  Overall Mission management.
• ESTEC TOS-EL - Project management support.
• ESA-Redu PROBA Control Centre - Satellite
  operations and daily Mission management.
• ESRIN EOP-AD - PROBA downlink data acquisition
  at Kiruna Esrange and Earthnet CHRIS HRC
  products archiving.
• ESTEC EOP-FSS - Project customer, coordinating
  CHRIS PIs activity.
• ESTEC TOS-EMA - Project customer for DEBIE.
• ESTEC TOS-QCA - Project customer for SREM and
  MRM.
• ESTEC TOS-ES - Project customer for technology
  experiments.
• ESA Education Office (ADM-AE) - Project customer
  for HRC and CHRIS pictures.
• EDUPROBA (through Belspo)
• - Project customer for HRC and CHRIS pictures and
  DEBIE and SREM data.

3

• Mission Entities
•  Verhaert - Industry Prime Contractor.
• SA - Ground segment remote maintenance.
• Sira Electro-Optics Ltd
• - CHRIS instrument manufacturer in charge of
  instrument configuration and calibration, data
  processing up to Level 1 and products delivery to
  PIs.
• Remote Sensing Applications Consultants Ltd
• - In charge of daily CHRIS planning taking into
  account target visibility and clouds prediction.
• University of Reading - In charge of generating
  Overpass tables for RSAC.
• UK Meteorological Office - In charge of
  generating clouds prediction for RSAC.
•  

4
Note iv)
Univ. ReadingOverpass Tables
UK Met.Office Cloud Predictor
ESRIN EarthnetCHRIS HRCProduct Archiving
Requests from EO scientistsCHRIS HRC
PROBA-1
CHRIS raw data
Note i)
CHRIS requests
RSACRequest Processing
SIRA (specify config. files)
HRC requests Daily clouds prediction
CHRIS requests
Requests from technology, industry, public
interestCHRIS, HRC, WAC, SIP, PASS, Platform
SIRACHRIS DataProcessing
KIRUNACHRIS Data Extraction and Q-L Processing
EOscience users
CHRIS requests
REDU Request Consolidation
CHRIS products
HRCWACSIPPASSPlatform requests
TOS-ES Request Processing
CHRIS Q-L
HRC products
Non-HRCrequests
REDUFull Data Extractionand CHRIS
Q-LProcessing
Technology,space envir.,education, industry,
public interest users
Requests from ESA Edu. Office users
ADM-AERequestProcessing
HRC requests
CHRIS Q-L and non-CHRIS products
Note iii)
CHRISrequests
Requests fromEDUPROBAusers
EDUPROBARequest Processing
HRC requests

• Notes
• No longer required when standard set of config.
  files is finalised and stored at REDU.
• SREM, DEBIE, MRM normally left on. Requests are
  only for special needs.
• REDU processed data products distributed via web
  server.
• Possibly (later) also CHRIS product distribution.
• Diagram does not include s/c housekeeping and
  maintenance operations (which may take priority).

Requests from space envir. SREM, DEBIE,
MRMNote ii)
TOS-EMA Request Processing
SREMDEBIEMRM requests
5

• User Data Request/Deliver Scheme.
• All the CHRIS requests are sent to RSAC which
  elaborates then a consolidated planning for the
  use of the instrument taking into account the
  target visibility and the clouds prediction.
• The HRC requests are collected by Redu which is
  in charge to interleave them in the CHRIS
  planning. The HRC requests can benefit from the
  RSAC clouds prediction data.
• The technology experiments requests are issued
  from TOS-ES to Redu which is in charge of the
  implementation.
• The Kiruna Esrange downlink data acquisition and
  the ESRIN Earthnet Product Archiving are under
  implementation. In order to increase the data
  return, it is foreseen to add 5 Kiruna downlink
  passes, 2 morning passes before the Redu passes
  and 3 evening passes before the Redu passes.
• All the raw data products are made available
  automatically on the Redu server. The processing
  of the HRC pictures is done at Redu and the
  pictures are available on the server. A quick
  look tool is installed at Redu to process the
  CHRIS pictures and made them available on the
  server.
• Sira mirrors via Internet the CHRIS raw data from
  Redu, processes them up to the Level 1 and make
  them available to the scientists on a ftp server.

6

• CHRIS operations description.
• The CHRIS acquisition plan is published on the
  CHRIS website. The site selected by RSAC,
  according to visibility, priority and clouds
  prediction, is communicated to Sira by email
  (and/or telephone). The information is also
  available on the CHRIS website.
•  Sira elaborates the CHRIS request accordingly
  via an UPLOAD form. The form and the instrument
  configuration files are automatically processed
  at Redu leading to the generation of the request
  telecommand procedure including the scheduling of
  the pictures downlink over the ground station.
• CHRIS mission operations constraints.
• PPU imaging cannot be performed simultaneously
  with pictures dump.
• The HRC operations need the knowledge of the PPU
  switch-on time, which is dependant on the last
  CHRIS session.
• A dump of 80 MB (5 x 240 sec. Dump) of CHRIS data
  requires a mean number of 2.5 passes therefore
  two targets must be separated by 3 passes.
• The PROBA mission control system is attended only
  during normal working hours. The planning and
  scheduling activities with the preparation of the
  pass template are then done in the morning while
  the telecommands uplink can be spread over
  several passes like the data download.

7

• CHRIS requests and planning
• RSAC is in charge of the planning of all the
  CHRIS requests including PI requests, EduPROBA,
  ESA Education Office and ESTEC TOS-ES. Priority
  is given according to the request type and the
  clouds prediction.
• The number of CHRIS calibration is limited to 1
  dark and 1 Sun per month.
• Before 09h30 local Redu time and for each Redu
  normal working day, Sira communicates to Redu via
  telephone and email the CHRIS planning (target
  and time are enough) of the next working day
  (morning and evening passes) including the
  weekend and the Redu bank holidays.
• As soon as a CHRIS request is made operational,
  an email is automatically sent to Sira
  (optional).

8

• CHRIS data processing
• Sira generates quicklook data within one working
  day from acquisition and make them available on
  the server.
• For operations purpose, Redu generates quicklook
  data using a ESTEC provided tool within one
  working day from acquisition and make them
  available on the server.
• Sira generates L1 products in HDF format within
  14 working days from acquisition and make them
  available on the ftp server.
• The CHRIS temperature data and other telemetry
  data are made available on the Redu server within
  one working day from acquisition.
• All the CHRIS requests uploaded to the satellite
  are logged in a catalog.

9

• HRC operations description
• HRC operations are performed at Redu. According
  to the User Data Request/Delivery Scheme (see
  above), it has been identified that the HRC
  requests should come from EduPROBA, ESA Education
  Office, TOS-ES and RSAC. The request forms
  completed are processed by the target visibility
  planning software based on ESOC Flight Dynamics
  tool. The selection of potential sites can then
  be checked with the clouds prediction file
  provided by RSAC and the telecommand procedure
  including the schedule of the pictures dump
  inserted in the pass template.
• After the processing which requires human
  intervention, the good pictures are made
  available on the Redu server

10

• HRC operations constraints
• PPU imaging cannot be performed simultaneously
  with pictures dump.
• The HRC operations need the knowledge of the PPU
  switch-on time. This one is dependant on the last
  CHRIS session. The HRC operations are interleaved
  with the CHRIS target and pictures dump times.
• Only one target can be taken on the sunlit part
  of the orbit.
• The MMU can hold a maximum of 5 HRC before
  overwriting.
• CHRIS target takes priority over HRC target when
  both times coincide.
• HRC requests and planning
• The approach which has been chosen is to
  establish a list of potential targets and to try
  to take them at the best opportunities
• HRC data processing
• After the processing which requires human
  intervention, the good pictures are made
  available on the Redu server
• All the HRC requests uploaded to the satellite
  are logged in a catalog.
•  

11

• Technology experiments request
• ESTEC PROBA Project Team initiates the Technology
  experiments requests and coordinates them with
  Redu.
• Technology experiments list
• The Technology experiments include the following
• Off earth observations and non baseline
  manoeuvres
• SREM specific measurements (rotations)
• GPS attitude
• AST tests
• MRM/SIPS testing
• PASS test
• Solar arrays efficiencies and albedo
  determination
• Battery pseudo-cycling
• Autonomous orbit determination without GPS

12

• Kiruna ESRANGE downlink capability
• Under implementation.
• Combined Kiruna/Redu pass planning for the next
  10 days sent by Redu to Kiruna.
• Kiruna cannot modify the first five days (TBC) of
  the planning. The remaining days can be updated
  with pass cancellation or re-scheduling.
• The updated planning is sent then also to RSAC
  and made available on the Redu PROBA server.
• Kiruna will be able to extract the PPU data
  (VC1)from the baseband equipement and make them
  vailable on a internet server for Sira download.
• Quiclook pictures will also be generated at
  ESRANGE and downloaded to Redu.