4 Final Report - Emits - ESA

More documents

Recommendations

Info

4 Final Report 4.6.1.1 High Level Functional Architecture At the first level of breakdown, the functional architecture identifies two main components: • The Flight Operations Segment (FOS), • The Payload Data Ground Segment (PDGS). This breakdown is illustrated and further refined in Figure 4.6-1. Mission Control System • Spacecraft Operational Database • Housekeeping Telemetry Processing • Time Management • Telecommand • Mission Planning • On-Board Software Maintenance • Ground Station Network Interface • Off-line analysis • Authentication and Encryption Facilities Ground Segment • Acquisition • Ingestion • Processing / reprocessing • Archiving and Inventory • Production Requests Handling • Dissemination • Circulation • Monitoring and Control FOS Flight Dynamics • Orbit Determination, Prediction and Control • AOCS Monitoring • AOCS Command Generation • Test and Validation Spacecraft Simulator • Platform Model • Payload Model • Ground Segment Model Ground Stations and Networks • TMTC Ground Stations • NDIU • PSS • Ground Communication Network User Services & Mission Planning • General Web • Catalogue • On-line Ordering and Order Handling • User Management • Mission Planning • Help and Documentation Desk • Statistics & Reporting PDGS Figure 4.6-1: Geo-Oculus -Ground Segment breakdown into Domains and Functions Sensor Performance, Products & Algorithms • Routine Quality Control • Product Quality Control • Product Calibration • Product Validation • Instrument Calibration • Processing and Instrument Data Files Generation • Instrument Performance Monitoring • Algorithms and Instrument Processing Facility Development • Instrument Processing Facility Maintenance & Evolution • User Support • Precise Orbit Determination 4.6.1.2 Proposed Architecture In the following, the proposed overall architecture of the Geo-Oculus Ground Segment is presented. The single elements of the architecture will be considered in the subsequent subsections. The Geo-Oculus Ground Segment Architecture features: For Mission Monitoring and Control: • A Flight Operations Control Centre, • a nominal TM/TC station, • a back-up TM/TC station and • a network of additional TM/TC stations used only for LEOP. For Payload Data Reception, Exploitation and Processing: • A “core” Payload Data Ground Segment and Page 4-78 Doc. No: GOC-ASG-RP-002 Issue: 2 Astrium GmbH Date: 13.05.2009
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
Page 1:
Geo-Oculus: A Mission for Real-Time
Page 7:
DL Final Distribution List Report Q
Page 11 and 12:
TOC Final Table of Content Report D
Page 13 and 14:
1 Final Report 1 Introduction 1.1 S
Page 15:
1 Final Report [RD 7] Candidate Mis
Page 18 and 19:
2 Final Report capability of existi
Page 20 and 21:
2 Final Report Figure 2.3-1: Flood
Page 22 and 23:
2 Final Report Figure 2.3-3: Algal
Page 24 and 25:
2 Final Report Figure 2.3-6: Chloro
Page 26 and 27:
2 Final Report Erosion / Sediment T
Page 28 and 29:
3 Final Report 3 System Requirement
Page 30 and 31:
3 Final Report Furthermore, the mis
Page 32 and 33:
3 Final Report better than 0.5 SSD
Page 34 and 35:
3 Final Report • Image post integ
Page 36 and 37:
3 Final Report Table 3.3-1: Baselin
Page 38 and 39:
3 Final Report Manoeuvre Times and
Page 40 and 41:
3 Final Report Cloud Amount [%] Num
Page 42 and 43:
3 Final Report cloud scenes where t
Page 44 and 45: 4 Final Report Alternative solution
Page 46 and 47: 4 Final Report The achieved ground
Page 48 and 49: 4 Final Report board image processi
Page 50 and 51: 4 Final Report 4.3.3.2 UV-VNIR foca
Page 52 and 53: 4 Final Report Column decoder 4 out
Page 54 and 55: 4 Final Report 4.3.3.5 Mechanical a
Page 56 and 57: 4 Final Report 4.3.3.7 Electrical a
Page 58 and 59: 4 Final Report 4.3.4 PLM budgets Th
Page 60 and 61: 4 Final Report 4.4.2 Microvibration
Page 62 and 63: 4 Final Report Figure 4.4-2: Struct
Page 64 and 65: 4 Final 4.5 Satellite Report 4.5.1
Page 66 and 67: 4 Final Report Star Tracker Figure
Page 68 and 69: 4 Final Report (Spacecraft Computer
Page 70 and 71: 4 Final Report This is based on a w
Page 72 and 73: 4 Final Report Reception of the ins
Page 74 and 75: 4 Final Report Table 4.5-2: Charact
Page 76 and 77: 4 Final Report Table 4.5-4: Compari
Page 78 and 79: 4 Final Report Table 4.5-5: EPS fue
Page 80 and 81: 4 Final Report manoeuvre. It also h
Page 82 and 83: 4 Final Report Figure 4.5-10: Basel
Page 84 and 85: 4 Final Report The CPS considered f
Page 86 and 87: 4 Final Report PPU B* FU XST Page 4
Page 88 and 89: 4 Final Report Table 4.5-17. EP mas
Page 90 and 91: 4 Final Report The primary structur
Page 92 and 93: 4 Final Report Direction MTG Scaled
Page 96 and 97: 4 Final Report shorter. As a conseq
Page 98 and 99: 4 Final Report 4.6.2.4 Cloud Cover
Page 100 and 101: 4 Final Report management functions
Page 102 and 103: 4 Final Report 4.6.2.8 Ground Stati
Page 104 and 105: 5 Final Report based on EUMETSAT im
Page 107 and 108: A Final Report Annex A Abbreviation
Page 109 and 110: A Final Report ICU Instrument Contr
Page 111: A Final Report Doc. No: GOC-ASG-RP-
show all

4 Final Report - Emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?