4 Final Report - Emits - ESA

4 Final
Report
• one or several deployable Payload Data Reception and Processing facilities.
The Figure below depicts the Ground Segment Architecture. It also identifies the main internal and
external interfaces. The external interfaces comprise the interfaces to the users and additional data
sources, which provide auxiliary data for processing and meteorological forecast data supporting the
scheduling of observations.
EGSE
Instrument Raw Data
LEOP
Network X-Band
TMTC
TMTC
station
S-Band
S-Band
Flight Operations
Control Centre
FOS PDGS
Receiving
Station(s)
Backup
Payload Data
Reception
Decryption, Processing,
Archiving &
Dissemination
Users Services
Coordination & Control
Payload Mission
Planning
User
Requests
External
Auxiliary Data
Sensor
Performance,
Products and
Algorithms
Meteo Forecast Data
+ MTG real time data
Users
Figure 4.6-2: Preliminary Architecture of the Geo-Oculus Ground Segment
External
External
Data
Data
Sources
Sources
Basic Products
User Reception
and Processing
Terminal
Service
Segment
Customised
Services
Payload Data
Reception
Decryption,
Processing,
Archiving &
Dissemination
Basic Products
The concept for the GEO-Oculus Ground Segment takes into account the particular principles of
operations and technical constraints resulting from a spacecraft on a geostationary orbit. Moreover,
the ground segment architecture is adapted to the needs of its customers for the different targeted
applications, in terms of revisit time, flexibility in satellite observations programming and latency from
observation to end of product delivery. In addition, the Ground Segment concept for the Sentinel
missions, which will be operated by ESA in the GMES era, has been considered as a "loose" design
guideline.
The mission for an optical high spatial resolution satellite operating from a GEO orbit must be
regarded as the conjunction of routine monitoring missions (sometimes termed “background” mission)
and of one or several emergency monitoring missions, which are by nature less schedulable than the
routine ones. An example of routine monitoring mission is the monitoring of coastal areas for which the
revisit times and the response times are comparatively long. Emergency monitoring missions are e.g.
fire or disaster monitoring. In this case, the revisit time as well as the response time need to be much
Doc. No: GOC-ASG-RP-002 Page 4-79
Issue: 2
Date: 13.05.2009 Astrium GmbH