ExoMars 2018 Spacecraft Composite Requirements Specification

Transcription

1 REFERENCE: EXM-M2-SYS-AI-0020 DATE: 28/03/2014 ISSUE: 3 ExoMars 2018 Spacecraft Composite Requirements Specification Written by Responsibility + handwritten signature if no electronic workflow tool Musetti Bruno Signed as AUTHOR on 26/03/ :37 Verified By Ferro Claudio Signed as CHECKER on 31/03/ :27 Palermo Annamaria Signed as DOCUMENTATION MANAGER on 02/04/ :10 Approved By Allasio Andrea Signed as PROGRAM MANAGER on 02/04/ :09 Realeased By Approval evidence is kept within the documentation management system. 2012, Thales Alenia Space DOC-TAS-EN/002

2 REFERENCE : EXM-M2-SYS-AI-0020 ISSUE : 3-Working Page : 1/184 EXOMARS ExoMars 2018 Spacecraft Composite Requirements Specification DRL/DRD: ENG-4 W.P. No: EB20-1ADA Written by Responsibility + handwritten signature if no electronic workflow tool B. MUSETTI Author Verified by C. FERRO Checker L. ZACCAGNINI Product Assurance Manager C. STURIANO Configuration Control Manager B. MUSETTI 2018 Mission System Engineering Manager Approved by A. ALLASIO ExoMars Deputy and 2018 Mission Program Manager W. CUGNO ExoMars Program Director A. LUKYANCHIKOV Lavochkin ExoMars Project Manager Documentation Manager A. PALERMO Approval evidence is kept within the documentation management system. 2014, Thales Alenia Space

3 ISSUE : 3-Working Page: 2/184 CHANGE RECORDS ISSUE DATE CHANGE RECORDS AUTHOR ST Issue for System Requirements Review B. Musetti nd Issue Implementing the Outcomes of System Requirements Review and ESA MSRD EXM-M2-RSD- ESA Draft 1, Rev 3 with Industries comments provided with B. Musetti E_Mail dated and S. Aleksashkin e_mail dated Musetti Revisited Chapter 4 for consistency with the new ExoMars Mission Analysis Guidelines (MAG) EXM-G2-TNO-ESC Issue 1 Rev. 0 Chapter 5.3 Mass updated as per SRR directives. Chapter MoI s requirements updated. Chapter 5.3. Communication updated in consistency with new SG-IRD EXM-G2-IRD-ESC and WG agreements. SCC updated as per WG outcomes. Chapter updated as per WG outcomes. Chapter updated as per WG outcomes. Deletion of Requirement SCC as per SRR MS- 30_AI-001disposition. Update of Requirement SCC as per SRR MS- 32_AI-001disposition and moved to Update of Requirement SCC as per SRR MS- 36_AI-001disposition. Update of Requirement SCC as per SRR RID MS- 77 disposition. Update of Requirement SCC as per SRR MS- 79_AI-001disposition. 2014, Thales Alenia Space

4 ISSUE : 3-Working Page: 3/184 ISSUE DATE CHANGE RECORDS AUTHOR Update of Requirement SCC as per SRR RID AP- 71disposition. 3 Following paragraphs have been updated reflecting the Lavochkin comments: B. Musetti 1.1, 1.3, 2.1.1, 2.1.5, 3.1, 3.2.1, 3.5., 5.2 Following requirements have been updated reflecting the Lavochkin comments: SCC-0120, SCC-0130, SCC-0340, SCC-0470, SCC-500, SCC-0560, SCC-0890, SCC-1015, SCC-1040, SCC- 5621, SCC-1930, SCC-2100, SCC-2420, SCC-3280, SCC-4490, SCC-4500, SCC-4550, SCC-4600, SCC- 4660, SCC-4900, SCC-4910, SCC-4920, SCC-4930, SCC-4940, SCC-4950, SCC-4960, SCC-4970, SCC- 5010, SCC-5020, SCC-5030, SCC-5060, SCC-5080, SCC-5130, SCC SCC-460 updated based on EXM-G2-TNO-ESC Preliminary Navigation Analysis. Deletion of Requirements SCC-1485 ad per MSRD Issue 02. Table 4.1 to remove TBD s Mass requirements Introduction of new requirement SCC , Thales Alenia Space

5 ISSUE : 3-Working Page: 4/184 TABLE OF CONTENTS 1. INTRODUCTION Scope Structure of the Document Acronyms and Terminology Conventions DOCUMENTS Normative Documents Definition of Normative Documents ESA Normative document A147Launcher Normative document Standards and Handbooks ECSS CCSDS Other Standards Thales Alenia Space Italia Normative Documents Informative Documents Definition of informative documents ESA/ROS/NASA Informative Documents Thales Alenia Space Italia Informative Documents Other Informative Documents EXOMARS 2018 MISSION AND SYSTEM DEFINITION Mission Objectives ExoMars 2018 Mission Concept ExoMars 2018 Mission Phases Mission Timeline ExoMars 2018 System Definition ExoMars 2018 Mission Scientific Payloads Rover Module Science Payload Landing Platform Science Payload (TBC) ExoMars 2018 Product Tree and Responsibility sharing EXOMARS 2018 MISSION REQUIREMENTS Mission Reference Frames and Time Conventions General Mission Requirements , Thales Alenia Space

6 ISSUE : 3-Working Page: 5/ Launch and Early Orbit Phase Interplanetary Cruise Mars Approach CM-DMC Separation, DM Entry, Descent and Landing General Flight Parameters Sun and Earth Angle and Distance Eclipses Sun-Earth-Mars / Sun-Mars-Earth Alignment (Conjunction events) SCC Lifetime SCC On-Ground Lifetime SCC (and Modules) Lifetime SCC Storage SCC SYSTEM REQUIREMENTS Mass Properties Mass Budget Control Mass Margin Policy Mass Center of Gravity & Moments of Inertia Reference Coordinates SCC Reference Coordinates CM Reference Coordinates DM Reference Coordinates CM-DM Separation Assembly Reference Coordinates RM Reference Coordinates Reference Coordinates relationship summary Communications General X-Band Communication UHF Communication Link Budget RF Compatibility Test Power General Power budget Science Payload Package Accommodation Mission Maneuvers Delta-V Requirements Propellant Budget SCC Operations and Autonomy General SCC Modes EDL Phases SCC FDIR , Thales Alenia Space

7 ISSUE : 3-Working Page: 6/ SCC Operations Payloads Operations SCC Autonomy DESIGN AND PERFORMANCE REQUIREMENTS Failure Tolerance & Redundancy Implementation Requirements Electrical General Pyrotechnical devices EMC EMC Design Guidelines and Requirements EMC Specification (Emission, Susceptibility, Corona, ESD) EMC Test Requirements Power System On Board Data Handling DHS Requirements Data Processing Budget TTC Performances General X-Band UHF Band Software General Performance Harness GNC General GNC Design Requirements GNC Modes Stand-by Mode Spin-Up Mode Nominal Sun Pointing Mode Nominal Earth Pointing Mode Inertial Pointing Mode Slew Mode Δ-V Mode GNC Safe mode GNC Survival Mode CM-DM Separation Mode Propulsion Propulsion design guideline and rules Propulsion System Requirements Structure Mechanisms and Pyrotechnics Thermal Control , Thales Alenia Space

8 ISSUE : 3-Working Page: 7/ INTERFACE REQUIREMENTS CM to DM Interface DM to RM Interface Communications (Ground Segment and TGO) Interface Requirements Ground Segment Interface Requirements TGO Interface Requirements Launcher Interface Requirements ENVIRONMENTAL REQUIREMENTS General Ground Mechanical Thermal Ambient Launch Mechanical Thermal Ambient EMC Flight (Cruise) Mechanical Thermal Space Radiation EMC Mars Proximity and Separation Mechanical Thermal Space EMC Entry, Descent and Landing (EDL) Mechanical Thermal Space EMC Mars Surface Mechanical Thermal Ambient EMC PLANETARY PROTECTION IMPLEMENTATION REQUIREMENTS CLEANLINESS AND CONTAMINATION REQUIREMENTS , Thales Alenia Space

9 ISSUE : 3-Working Page: 8/ LOGISTIC REQUIREMENTS AIV REQUIREMENTS MGSE & FGSE Requirements EGSE REQUIREMENTS EGSE Connections PRODUCT ASSURANCE AND SAFETY REQUIREMENTS CARRIER MODULE DETAILED REQUIREMENTS DESCENT MODULE DETAILED REQUIREMENTS ROVER MODULE DETAILED REQUIREMENTS MSRD REQUIREMENTS NOT TRACED IN THIS SPECIFICATION , Thales Alenia Space

10 ISSUE : 3-Working Page: 9/184 LIST OF FIGURES Figure 1-1 ExoMars 2018 Mission Top Level Specification Tree...11 Figure 3-1 Spacecraft Composite (for reference only)...24 Figure 3-2 ExoMars 2018 Mission System Elements...25 Figure 3-3 ExoMars 2018 Product Tree and responsibility sharing...26 Figure 4-1 Angles Evolution for ExoMars 2018 Nominal Mission, LPO...42 Figure 4-2 Angles Evolution for ExoMars 2018 Nominal Mission, LPC...42 Figure 4-3 Earth-Mars and Sun-Mars distances...43 Figure 4-4 SEM and SME alignment (Conjunction)...45 Figure 5-1 SCC, DM & CM Reference Coordinates...55 Figure 5-2 RM Reference Coordinates...56 Figure 6-1 SCC Attitude at Separation LIST OF TABLES Table ExoMars 2018 Mission Phases...22 Table 4-1 SC Composite dynamic conditions at separation from the launcher...35 Table 4-2 SEM Angle for 2019 and 2021 Events , Thales Alenia Space

11 ISSUE : 3-Working Page: 10/ INTRODUCTION The ExoMars Programme shall be pursued as part of a broad cooperation between ESA and Roscosmos. This cooperation shall build towards a cooperative Mars sample return mission. Two missions are foreseen within the ExoMars programme for the 2016 and 2018 launch opportunities to Mars. The 2016 mission is an ESA led mission that will be launched by a Roscosmos supplied Proton- M/Breeze-M rocket. ESA will supply a Mars Orbiter that will carry an Entry, Descent and Landing Demonstrator also supplied by ESA. Russian and European scientific instruments will be accommodated on the ExoMars Orbiter to investigate atmospheric trace gases, their temporal and spatial variation and, possibly, to identify sources on Mars. The 2018 mission is an extended ESA and Roscosmos cooperation devoting to develop a complex Spacecraft, to be launched with a Proton M/Breeze-M rocket, consisting of a Descent Module and a Carrier Module. Inside the Descent Module are a static Landing Platform and Rover which will be deployed on the Mars surface. Both the Landing Platform and the Rover will carry scientific instruments mainly devoted to exobiology and geology research. The CM carries the DM to Mars, performs fine targeting and attitude operations and jettisons the DM, shortly before atmospheric entry, for its ballistic landing on the Mars surface. The CM is not foreseen to operate after separation. 1.1 Scope This Spacecraft System Requirements Specification (SCRS) define the requirements for the design, development and verification of the whole Space Segment of the ExoMars 2018 Mission. The Space Segment of the ExoMars 2018 consists of three main modules: o o The Carrier Module (CM) which carries the whole system close to Mars atmospheric borders and releases the Descent Module into its entry, descent and landing trajectory. The Descent Module (DM) which performs the entry, descent and landing on the Martian surface of a Landing (or Surface) Platform and its payloads for static science research. The DM main elements consist of: CM/DM Separation System (CM/DM SS) Landing Platform (LP) Front Shield (FS) Rear Jacket (RJ) Parachute system (PAS). Note: The Landing Platform (LP) ensures the landing on Mars Surface and consists of Propulsion system, Landing devices, systems ensuring LP operation on Martian surface and scientific instruments o The Rover Module (RM) which, egressing from inside the DM, allows a Rover Vehicle (RV) and its boarded experiments to perform science exploration onto the Mars Planet. It is composed of: 2014, Thales Alenia Space

12 ISSUE : 3-Working Page: 11/184 o o o Rover Vehicle (RV) Pasteur Payload (PPL) composed of 6 Survey Payloads Panoramic Cameras (WAcs + HRC) - PanCam Ground Penetrating Radar - WISDOM Close-Up Imager - CLUPI Mars Multispectral Imager for Subsurface Studies - Ma_Miss Neutron Detector Package - ADRON (Roscomos - IKI) Infrared Pointing Spectrometer - ISEm (Roscomos - IKI) 3 Analytical Payload Infrared Microscope (MicrOmega) Raman/LIBS Spectrometer (RLS) Gas Chromatographer / Mass Spectrometer (MOMA) Payload Support Function (PSF) composed of Sample acquisition System (SAS), including the DRILL Sample Preparation and Distribution System (SPDS) Payload Support Electronics (PSE) Note1: the compound made of Descent Module and Rover Module is called Descent Module Composite (DMC). Note2: In Russian documentation, the term DMC is not used. DM is used to indicate the DMC compound. The Carrier Module together with the Descent Module and the Rover Module constitutes the ExoMars Spacecraft Composite (SCC). This SCRS responds to the ESA ExoMars 2018 Mission and System Requirements Document (EXM- MS-RSD-ESA-00029). Detailed Requirements Specifications, responding to this SCRS, will be developed for the three main modules composing the SCC. The ExoMars 2018 Mission Top Level Specification Tree is shown in Figure 1-1 Standards MSRD ESA Ancillary Requirements Documents TASI Support Specifications Spacecraft Composite Requirements Specification Carrier Module Requirements Specification Descent Module Requirements Specification Rover Module Requirements Specification Figure 1-1 ExoMars 2018 Mission Top Level Specification Tree 2014, Thales Alenia Space

13 ISSUE : 3-Working Page: 12/ Structure of the Document The structure of the document is shortly summarized here below. Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Chapter 11 Chapter 12 Chapter 13 is the introductory chapter reporting the object of this specification is the Normative and Informative Documents chapter reports the Mission top level description, its relevant objectives and the System definition suitable for technical requirements comprehension reports the Mission requirements reports SCC system requirements. reports the SCC Design and Performance requirements defines the interface between the SCC and EDM, Communications and Launcher interfaces. specifies the environment in which the SCC will operate in all its mission phases. deals with Planetary Protection requirements. deals with Cleanliness and Contamination requirements. defines the Logistics rules to allow SCC (and its components) packing, handling and transportation specifies the Assembly, Integration and Verification requirements specifies the PA requirements. 1.3 Acronyms and Terminology Acronyms and Terminology to be used in the ExoMars program are defined in the document named ExoMars 2018 List of NR/IR Documents, Acronyms and Abbreviations EXM-M2-LIS-AI-0059 [NR 05002]. Note: The [NR05002] is applicable to all SCC items under ESA responsibility or interfacing with ESA provided HW and or Software. DM elements under Russian ROS responsibility, not interfacing with ESA-provided Hw/Sw can be developed following Russian regulations and standards. 1.4 Conventions The convention for the requirements numbering in this specification is M2-SY-xxxx, where the xxxx indicates the requirements progressive number. A requirement or group of requirements may be followed or preceded by comments, i.e. an explanatory text. This is intended only to assist the understanding of the requirement or its origin. The text proceeded by the wording Comment: is in italic characters and it describes the context in which a requirement has to be understood, explains the rationale for the requirement or refer to its source. The following verification levels are identified in this specification: EQ = Equipment S/S = Sub-System MOD = Module (i.e. CM, DM, RM) SCC = SpaceCraft Composite 2014, Thales Alenia Space

14 ISSUE : 3-Working Page: 13/ DOCUMENTS The documents reported in this chapter have to be used, when explicitly addressed, to complete the content of this specification. 2.1 Normative Documents Definition of Normative Documents Normative References (NR) are directly applicable in their entirety to this document and are listed below as dated or undated references. These normative references may be cited at appropriate places in the text as [NR XXXXX]. For dated references, subsequent amendments to or revisions of any of these document apply to this list only when incorporated in it by amendment or revision. For undated references, the latest signed version is applicable when incorporated by TASI as ExoMars 2018 mission Prime Contractor in the project baseline after evaluation in a relevant Change Control Board.. In case of conflict between this document and normative documents listed herein TASI together with its Russian partner Lavochkin shall inform the ESA/Roskosmos Program Offices for resolution ESA Normative document REFERENCES DOC. TITLE DOC. NUMBER [NR 03] ExoMars Management Requirements Document EXM-MS-RS-ESA [NR 015] ExoMars Document Requirements Description EXM-MS-RS-ESA [NR 017] ExoMars Risk Management Requirements EXM-MS-RS-ESA [NR 020] ExoMars Configuration Management Requirements EXM-MS-RS-ESA [NR 02] ExoMars Rover Requirements Document EXM-RM-RS-ESA [NR 021] ExoMars 2016 and 2018 Missions Environmental Specification Requirements EXM-MS-RS-ESA [NR 18023] ExoMars 2018 Mission and System Requirements EXM-M2-RSD-ESA Document [NR 18025] ExoMars 2018 Assembly, Integration and Verification Requirements EXM-M2-RSD-ESA [NR 18004] ExoMars Reference Surface Mission EXM-PL-RS-ESA [NR 18028] RM RHU Information Package EXM-RM-IPA-ESA [NR 18026] ExoMars 2018 Product Assurance Requirements EXM-M2-RSD-ESA [NR 18024] ExoMars 2018 Planetary Protection Requirements EXM-M2-RSD-ESA [NR 18021] MOC/ERCO to ROCC Interface Requirements Document EXM-GS-IRD-ESC [NR 180xx] Consolidated Report on Mission Analysis (CReMA) To Be Written [NR 18016] ExoMars 2018 Operation Interface Requirements Document EXM-G2-IRD-ESC [NR 18017] ExoMars 2018 Space to Ground Interface Requirements EXM-G2-IRD-ESC Document, Vol , Thales Alenia Space

15 ISSUE : 3-Working Page: 14/ A147Launcher Normative document REFERENCES DOC. TITLE DOC. NUMBER [NR 18027] [IR Axxx] ExoMars 2018 to Proton Launcher Interface Requirements Document, (until issuing of the Proton Launcher to ExoMars Interface Control Document) Proton Launch System Mission Planner s Guide Applicability Matrix (Applicable to EXM 2018) EXM-M2-IRD-ESA To Be Written 2014, Thales Alenia Space

16 ISSUE : 3-Working Page: 15/ Standards and Handbooks ECSS ECSS standards documents are, in general, applicable as design guidelines. They define applicable requirements when they are explicitly addressed by Program specifications. Hereafter, the Engineering ECCS standards to be used in the frame of the ExoMars 2018 mission are listed. These normative references may be cited at appropriate places in the text as [*S XXX]. For all the others ECSS standards, i.e. Managements and Quality, refer to 2.3 of the document named ExoMars 2018 List of NR/IR Documents, Acronyms and Abbreviations EXM-M2-LIS-AI-0059 [NR 05002]. REFERENCES DOC. NUMBER DOC. TITLE [ES 004] ECSS E-10 Part 1B Requirements and Process [ES 029] ECSS E-10 Part 6A Functional and Technical Specifications [ES 030] ECSS E-10 Part 7A Product Data Exchange [IR 18014] Tailoring of ECSS-E-10-03A Testing, Issue 1 Rev.0, 25 June 2007: EXM-MS-RS-ESA [IR 18015] Tailoring of ECSS-E-10-02A Verification, Issue 1 Rev.0, 26 June 2007: EXM-MS-RS-ESA [ES 026] ECSS E-ST-10-04C Space Environment [ES 031] ECSS E-10-05A Functional Analysis [ES 032] ECSS E-ST-20C Electrical and Electronic [ES 033] ECSS-E-20-1A Multipaction design and test [ES 034] ECSS E-ST-20-06C Spacecraft Charging [ES 035] ECSS E-ST-20-07C Electromagnetic Compatibility [ES 036] ECSS E-ST-20-08C Photovoltaic Assemblies and Components [ES 039] ECSS E30 Part 7A Mechanical Parts [ES 007] ECSS E-ST-31C Thermal Control [ES 040] ECSS E-ST-32-08C Materials [ES 041] ECSS E-ST-32-01C Rev1 Fracture control [ES 042] ECSS E-ST-32-11C Modal Survey Assessment [ES 043] ECSS E-ST-32C Rev1 Structural General Requirements [ES 044] ECSS E-ST-32-02C Rev1 Structural Design and Verification of Pressurized Hardware [ES 045] ECSS E-ST-32-03C Finite Element Model Requirements [ES 046] ECSS E-ST-32-10C Rev1 Structural FoS for Spacecraft and Launch Vehicles [IR A132] Tailoring of ECSS E-ST-33-01C Mechanical Mechanisms for EXM-MS-RSD- ESA [ES 038] ECSS E-ST-33-11C Pyrotechnics Mechanisms 2014, Thales Alenia Space

17 ISSUE : 3-Working Page: 16/184 REFERENCES DOC. NUMBER DOC. TITLE [ES 037] ECSS E-ST-35C Mechanical- Liquid and electric propulsion E-ST-35-01C E-ST-35-10C [ES 059] ECSS-E-ST-35-06C Rev1 Cleanliness requirements for spacecraft propulsion components, subsystems and systems [IR 18011] Tailoring of ECSS E40 EXM-MS-RS-ESA Software Part 1B [IR 18012] Tailoring of ECSS E40 EXM-MS-RS-ESA Software Part 2B [IR 18013] Tailoring of the ECSS E50 Part 1A Communications - Part 1 Principles and requirements for ExoMars EXM- MS-RS-ESA [ES 049] ECSS E50 Part 2A Document requirements definitions (DRDs) [ES 050] ECSS E-ST-50-02C Ranging and Doppler tracking [ES 051] ECSS E-ST-50-05C Rev1 Radio Frequency and Modulation [ES 052] ECSS E-ST-50-12C SpaceWire - Links, nodes, routers and networks [ES 053] ECSS E-ST-50-13C Interface and communication protocol for MIL- STD-1553B data bus On-board spacecraft [ES 057] ECSS-E-ST-50-14C Discrete Signal Interfaces [ES 135] ECSS-E-ST-50-01C Space Data Links - Telemetry Synchronization and Channel Coding [ES 133] ECSS-E-ST-50-03C Space data links - Telemetry transfer frame protocol [ES 134] ECSS-E-ST-50-04C Space data links - Telecommand protocols synchronization and channel coding [ES 137] ECSS E-ST-50-11C SpaceWire Protocol [ES 057] ECSS E-ST-50-14C Discrete Signals Interfaces [ES 054] ECSS E60A Control Engineering [ES 055] ECSS E-ST-60-20C Rev1 Star Sensor Terminology and Performance Specification [ES 058] ECSS-E-ST-60-10C Control Performances [ES 027] ECSS-E-70C Ground System and Operations General Requirements [ES 136] ECSS-E-70-41A Telemetry and Telecommand Packet Utilisation [ES 074] ECSS-M-ST-80C Risk Management [ES 056] ECSS-U-AS-10C Space sustainability. Adoption Notice of ISO 24113: Space systems - Space debris mitigation requirements 2014, Thales Alenia Space

18 ISSUE : 3-Working Page: 17/ CCSDS REFERENCES DOC. TITLE DOC. NUMBER [CS 01] TM Synchronization and Channel Coding CCSDS B-1 [CS 02] TM Space Data Link Protocol CCSDS B-1 [CS 03] Space Packet Protocol CCSDS B-1 [CS 04] TC Synchronization and Channel Coding CCSDS B-1 [CS 05] Technical Corrigendum 1 to CCSDS B-1 CCSDS B-1 Cor. 1 [CS 06] TC Space Data Link Protocol CCSDS B-1 [CS 07] Proximity-1 Space Link Protocol - Data Link Layer CCSDS B-4. [CS 08] Proximity-1 Space Link Protocol-Physical Layer CCSDS B-3 [CS 09] Proximity-1 Space Link Protocol-Coding and CCSDS B-1. Synchronization Sub layer [CS 10] Radio Frequency and Modulation Systems CCSDS B-20 [CS 11] Recommendation 2.5.6B (DeltaDDOR) and CCSDS B recommendation B (Suppressed carrier modulation) [CS 12] Communications Operation Procedure-1. Blue Book CCSDS B-1 [CS 13] Pseudo-Noise (PN) Ranging Systems CCSDS B Other Standards REFERENCES DOC. TITLE DOC. NUMBER [MS 01] MIL-STD-1553B: Interface Standard for Digital Time Division Command/Response Multiples Data Bus TM Synchronization and Channel Coding 2014, Thales Alenia Space

19 ISSUE : 3-Working Page: 18/ Thales Alenia Space Italia Normative Documents REFERENCES DOC. TITLE DOC. NUMBER [NR 05000] ExoMars 2018 Spacecraft Composite EXM-M2-SYS-AI-0020 Requirements Specification [NR 06000] ExoMars Carrier Module Requirement EXM-C2-SYS-AI-0018 Specification [NR 07000] ExoMars Descent Module Requirements EXM-D2-SYS-AI-0019 Specification [NR0400] Rover Module Requirements Specification EXM-RM-SYS-AI-0004 [NR 05002] ExoMars 2018 List of NR/IR Documents, Acronyms EXM-M2-LIS-AI-0059 and Abbreviations [NR 05004] ExoMars 2018 S/C Electrical General Design I/F EXM-M2-SSR-AI-0023 Requirements [NR 05005] ExoMars 2018 EMC and Power Quality Reqt.s EXM-M2-SSR-AI-0024 [NR 05006] ExoMars 2018 Thermal Environment and Test EXM-M2-SSR-AI-0025 Requirements Specification [NR 05007] ExoMars 2018 Mechanical and Thermal Design EXM-M2-SSR-AI-0026 and Interface Requirements [NR 05008] ExoMars 2018 Product Assurance Requirements EXM-M2-RQM-AI-0067 for Subcontractors [NR 05009] ExoMars 2018 Spacecraft Design, Development EXM-M2-PLN-AI-0136 and Verification Plan [NR 05010] EXOMARS 2018 Mechanical Environment and EXM-M2-SSR-AI-0027 Test Requirements Specification [NR 05011] EXOMARS 2018 Planetary Protection EXM-M2-SSR-AI-0031 Implementation Requirements [NR 05013] EXOMARS 2018 Flight and Mars Surface Space EXM-M2-SSR-AI-0029 Environment Requirements Specification [NR 05014] ExOMARS 2018 Cleanliness & Contamination EXM-M2-SSR-AI-0030 Requirements Specification [NR 05025] ExOMARS 2018 SCC Autonomy and Operational EXM-M2-SSR-AI-0032 Requirements Specification [NR 05026] ExOMARS 2018 MGSE General Design EXM-M2-SSR-AI-0033 Requirements Specification [NR 05027] ExOMARS 2018 EGSE General Design EXM-M2-SSR-AI-0034 Requirements Specification [NR 05028] ExOMARS 2018 CCS Communication Protocol EXM-M2-SSR-AI-0035 Specification [NR 05029] ExoMars 2018 SW Support Requirements EXM-M2-SSR-AI-0028 Specification [NR 05015] EXOMARS 2018 Mission FEM Requirements for EXM-M2-VRP-AI-0066 Structural Analysis [NR 05003] ExoMars 2018 Thermal Mathematical Model EXM-M2-RQM-AI-0064 Requirements Specification [NR 05016] EXOMARS 2018 Product Tree EXM-M2-SLI-AI-0029 [NR 05001] CM/DM Interface Requirements Document EXM-M2-IRD-AI-0029 [NR 05017] DM/RM Interface Requirements Document EXM-M2-IRD-AI-0030 [NR 05030] ExoMars 2018 SW PA Requirements for Subco s EXM-M2-RQM-AI-0075 [NR 05039] ExoMars 2018 Joint Verification Plan EXM-M2-PLN-AI , Thales Alenia Space

20 ISSUE : 3-Working Page: 19/184 Note 1: Normative and Informative Documents directly relevant to Rover Module items are reported in of [NR 05002]. Their applicability will be detailed in the [NR0400]. Note 2: Normative and Informative Documents directly relevant to Descent Module items are defined by the Russian Partner Lavochkin and reported in the document EXM-SF-0-X-0002-LAV 2.2 Informative Documents Definition of informative documents Informative References are applicable to this document only when specifically called up in the text with specific indications of the parts of the document that are to be applicable. Otherwise the documents are listed below for information only as an aid for the purpose of understanding. These normative references may be cited at appropriate places in the text as [IR XXXXX] ESA/ROS/NASA Informative Documents REFERENCES DOC. TITLE DOC. NUMBER [IR 18022] ExoMars Mission Analysis Guidelines (MAG) EXM-G2-TNO-ESC Issue 1 Rev. 0 [IR ESAxx2] Rover Module Science Payloads Refer to of [NR 18023]. Note: RM P/L ICD s are for information only. [IR ROSxx1] Landing Platform Science Payloads To be written Note: LP P/L ICD s are for information only. [IR ESAxx3] UHF Telecommunication Package To be written [IR A136] Mars Relay Network Handbook JPL D [NR A55] Landers and Probes Communication System EXM-MS-TN-ESA Thales Alenia Space Italia Informative Documents REFERENCES DOC. TITLE DOC. NUMBER [IR 1154] ExoMars TGO Data Relay User Guide EXM-MS-MAN-AI-0007 [IR 0157] ExoMars Flight and Mars Surface Environment EXM-MS-ARP-AI-0010 Analysis Report Other Informative Documents Refer to 3.2 of [NR 18023], to be used for reference only. REFERENCES DOC. TITLE DOC. NUMBER 2014, Thales Alenia Space

21 ISSUE : 3-Working Page: 20/ EXOMARS 2018 MISSION AND SYSTEM DEFINITION 3.1 Mission Objectives The ExoMars Programme will demonstrate key flight and in situ enabling technologies in support of the European ambitions for future exploration missions, as outlined in the Aurora Declaration and will pursue fundamental scientific investigations. In support of the objectives of the Aurora Program, the development, in flight and in situ demonstration of the following technologies shall be achieved: Entry, Descent and Landing (EDL) of a payload on the surface of Mars Surface mobility with a Rover Access to the sub-surface to acquire samples Sample preparation and distribution for analyses by scientific instruments The ExoMars scientific objectives are: To search for signs of past and present life on Mars To investigate the water/geochemical environment as a function of depth in the shallow subsurface To investigate Martian atmospheric trace gases and their sources To investigate and solve scientific problems within the composition of Mars Surface long-living stationary platform A further objective of the ExoMars Programme is to provide data relay services for landed assets on the surface of Mars until the end of Note: this objective will be achieved as part of the ExoMars 2016 Mission. The objectives of the ExoMars Programme will be pursued as part of a broad cooperation with Roscosmos that will build towards a cooperative Mars sample return mission in the following decades. Two missions are foreseen within the ExoMars programme for the 2016 and 2018 launch opportunities to Mars: The 2016 mission is an ESA led mission that will be launched by a Roscosmos supplied Proton- M/Breeze-M rocket. ESA will supply a Mars Orbiter that will carry an Entry, Descent and Landing Demonstrator also supplied by ESA. Scientific instruments will be accommodated on the ExoMars Orbiter to investigate atmospheric trace gases, their temporal and spatial variation and, possibly, to identify sources on Mars. The 2018 mission is also an ESA led mission consisting of a Rover, a Descent Module and a Carrier Module or Cruise stage. Scientific Instruments are boarded on both Surface [Platform and Rover Module to study Mars environment and its geological structure exploring surface and subsurface in the vicinity of the landing site. 2014, Thales Alenia Space

22 ISSUE : 3-Working Page: 21/ ExoMars 2018 Mission Concept The 2018 ExoMars mission includes a Carrier Module and a Mars Rover developed by ESA, and a Descent Module including a Landing Platform developed by Roscosmos. The goal of the 300kg-class Rover is to explore the surface and subsurface in the vicinity of the landing site to conduct geological investigations and to search for Parents of past and present life for a nominal period of 218 sols. The ExoMars Rover shall include a two-meter drill, the Pasteur payload provided by ESA, and Russian scientific instruments. The Landing Platform shall include a set of instruments for studying the environment and investigating the planet s internal structure during one Martian year. Once the Rover has egressed, the Landing Platform shall conduct its science mission. Roscosmos will provide a Proton launcher, upper stage Breeze-M and associated launch services, be responsible for the development of the Descent Module with Landing Platform and Rover egress system with ESA contributions, taking advantage of some of the key technology developments and the demonstration performed with the 2016 ExoMars EDM, and provide ESA with heating units (RHUs) for the Rover. ESA shall be responsible for the Carrier Module and the Rover implementation, with contributions from Roscosmos. The ESA MOC shall, in coordination with Roscosmos, in accordance with an ExoMars Joint Management Plan agreed at Agencies level, exercise operation functions over the Spacecraft Composite until separation and entry of the Descent Module using ESTRACK with support from RNS (Russian Deep Space Network). After landing and Rover egress, the ESA MOC shall receive telemetry from and pass commands to the Rover and the Landing Platform through the TGO spacecraft in orbit using ESTRACK with support from RNS. The ESA Rover Operations Control Centre (ROCC) and the Russian Landing Platform Control Centre shall coordinate their efforts to plan science activities and submit the command loads to the ESA MOC for transmission to the Rover and Landing Platform respectively through the ExoMars TGO. 2014, Thales Alenia Space

23 ISSUE : 3-Working Page: 22/ ExoMars 2018 Mission Phases The ExoMars 2018 Mission phases are summarized together with the associated events in the Table 3-1 Phase Starting event Ending event Main intermediate events Pre-Launch LV on launch pad Removal of LV umbilical from launch pad Launch Early Operation Spacecraft Composite Checkout Interplanetary Cruise Mars Approach DM Separation Preparation and Execution CM final operations Removal of LV umbilical from launch pad Separation of Spacecraft Composite from LV Upper Stage Completion of LV injection correction maneuver Completion of Spacecraft Composite checkout Start of intensive orbit determination activities for targeting DM deployment Last TCM for B-plane targeting Separation of Spacecraft Composite from LV Upper Stage Completion of LV injection correction maneuver Completion of Spacecraft Composite checkout Start of intensive orbit determination activities for targeting DM deployment Last TCM for B-plane targeting DM separation DM separation Carrier enters Mars atmosphere and disintegrates. DM Coast DM separation DM arrival at Entry Interface Point DM Entry, Descent DM arrival at Entry and Landing Interface Point Landing (EDL essential telemetry received by the TGO) Rover egress Landing Rover outside the Landing Platform Landing Platform Landing End of Landing Platform Commissioning Commissioning Lander Science End of Landing End of SP operational life on Operational Phase Platform Mars surface Commissioning Rover Science Rover egress completed End of Rover Science commissioning Rover Science Operational Phase End of Rover Commissioning commissioning End of RM operational life on Mars surface Table ExoMars 2018 Mission Phases LV lift-off, and injection into Mars transfer trajectory Sun acquisition and power generation. Telemetry acquired by Ground Control and stable pointing attitude. Navigation correction maneuvers Several TCMs Carrier passively enters Mars atmosphere and disintegrate. Detailed EDL sequence. Commissioning of Rover elements needed for egress 2014, Thales Alenia Space

24 ISSUE : 3-Working Page: 23/184 Note: Due to the nature of the mission, the Spacecraft Composite configuration changes throughout the mission phases, in particular: From Launch phase to Carrier - DM separation the Spacecraft is a unique composite. At DM separation, the Spacecraft Composite splits in two modules: the Carrier Module and the Descent Module Composite (DMC) which is the Descent Module incorporating in its inside the Rover Module. During DM Entry Descent and Landing phase the sub-modules of the DMC are separated and jettisoned to allow the safe touch down on Mars of the Landing Platform. After landing, the Rover Module will deploy its solar panels and egress from the Landing Platform. Both Rover Module and Landing Platform are ready to start their science operations on the Mars surface Mission Timeline The description of the ExoMars 2018 reference mission (considering a Russian Proton M with the Breeze M upper stage, launched from Baikonur, which uses an extended escape sequence to achieve insertion into the hyperbolic Earth escape orbit) is reported in [IR 18022]. In particular, [IR 18022] report the details of the nominal mission, while report the details of the applicable back-up mission. 3.3 ExoMars 2018 System Definition The ExoMars 2018 Mission System consists of: A) The Space Segment, as a single Spacecraft Composite (SCC), reported in Figure 3-1, which consists of: o o The Carrier Module (CM) which carries the whole system close to Mars atmospheric borders. The Descent Module (DM) which separates from the CM, heading the Descent Module into its entry, descent and landing trajectory. It performs the entry, descent and landing on the Martian surface of a Surface (or Landing) Platform (SP) and its payloads for static science research. The DM consists of Landing Platform, Front shield and Backshell and a Parachute system. Note 1: The Landing Platform (LP) ensures the landing on Mars Surface and consists of Propulsion system, Landing devices, systems ensuring SP operation on Martian surface and scientific instruments Note 2: The CM-DM separation is implemented through a CM-DM Separation Assembly, which is composed by the Separation mechanism and the Adapter. o The Rover Module (RM) which, egressing from inside the DM, allows a Rover Vehicle (RV) and its boarded experiments to perform science exploration onto the Mars Planet Note: the compound made of Descent Module and Rover Module is called Descent Module Composite (DMC) 2014, Thales Alenia Space

25 ISSUE : 3-Working Page: 24/184 Figure 3-1 Spacecraft Composite (for reference only) B) The Ground Segment which consists of: The Mission Ground Control which is subdivided into: o The Mission Operations Centre (MOC) located at ESOC, Germany o The ExoMars Rover Operations Control Centre (ROCC) located at ALTEC, Italy o The Pasteur payload Science Data Archiving and Dissemination located at ESAC, Spain o The Landing Platform Payload Operations Control Centre (TBD) The ESA Ground Station & Communications Subnet (ESTRACK) The NASA Ground Stations & Communication Subnet (DSN) Note: to be considered for critical phases like Safe Mode(s) or Flight Software upload or for extreme contingencies like the loss of SCC attitude The Russian Ground Stations & Communication Subnet (RNS) The Science Data Archiving centers (NASA PDS and ESA PSA) C) The Launcher and Launch Services: Proton M with the Breeze M upper stage D) ExoMars 2016 Trace Gas (Data Relay) Orbiter (TGO) The ExoMars 2018 Mission System elements are depicted in Figure , Thales Alenia Space

26 ISSUE : 3-Working Page: 25/ Mission Trace Gas Orbiter (TGO) NASA DSN N/A Available for extreme contingencies during Cruise Spacecraft Composite (Carrier Module + Descent Module + Rover Module) Roscosmos RNS ESA ESTRACK DSN ROCC (incl SOC- Altec) ESOC, Darmstadt Spacecraft Operations Archiving (ESAC) Archiving (ROS) Lander Op. Center (ROS) Rover and Landing Platform Proton M / Breeze M Figure 3-2 ExoMars 2018 Mission System Elements 3.4 ExoMars 2018 Mission Scientific Payloads The mission includes the Rover Payload (Pasteur Payload Package) and the Landing Platform Payload asset Rover Module Science Payload The description and related requirements for the RM Science Payloads are provided in [ESAxx2] Landing Platform Science Payload (TBC) The description and related requirements for the Landing Platform Science Payload are provided in [ROSxx1]. 3.5 ExoMars 2018 Product Tree and Responsibility sharing To understand better the content of this specification, it is worthwhile to know the ExoMars 2018 high level Product Tree and relevant responsibility sharing among the different modules (refer to Figure 3-3). 2014, Thales Alenia Space

27 ISSUE : 3-Working Page: 26/184 RCS Thrusters and Tanks Figure 3-3 ExoMars 2018 Product Tree and responsibility sharing (As per last available ESA-ROS Joint Management Plan) It has to be known that the SCC will include two (redundant) On Board computers both located into the DM. The first computer (referred as OBC 1 in this Specification) will be in charge of all the SCC functions during Cruise, CM/DM separation and Entry, Descent and Landing, up to the egress of the RM from the SP. The second computer (referred as OBC 2 in this Specification) will be in charge of managing all the operations of the SP once the RM has left the SP. The content of this SCRS is relevant to the Mission and System requirements of the SCC, including top level requirements for the SCC elements which will be developed in details in the relevant Module Specification. In particular: CM Requirements as per [NR 06000] DM Requirements as per [NR 07000] RM Requirements as per [NR 0400] In particular, the Mission System main functions like: 2014, Thales Alenia Space

28 ISSUE : 3-Working Page: 27/184 Mission Management Data Handling Environmental Control GNC FDIR Telecommand reception and Telemetry generation, including telemetry formatting and telecommand decoding Maneuver execution Power generation and storage will be defined following the requirements of this SCRS from Launch up to the landing on the Mars surface. Detailed design requirements for all the elements operating on the Mars Surface, will implement the requirement specified in the relevant Module/Elements Specifications. 2014, Thales Alenia Space

29 ISSUE : 3-Working Page: 28/ EXOMARS 2018 MISSION REQUIREMENTS 4.1 Mission Reference Frames and Time Conventions #[SCC- 0010] All analysis involving a Mars gravity model shall make use of the MGSF2 Mars gravity model [NR 180xx]. Deviation from the use of this model, if any, shall be agreed with the agency on a case by case basis. #[SCC- 0020] The following reference frames shall be used for ExoMars 2018 Mission (details can be found in [NR 180xx]): Mean Earth Equator of 2000 (MEE2000) It corresponds to the mean Earth equator fixed frame at epoch 2000/1/1 12h ET. Coordinate systems with their axis directions parallel to those of the MEE2000 reference frame and their origin in the barycenter of the solar system or the center of the Sun, the Earth or Mars are used for ephemeris definitions and in the calculations leading to the mission analysis results presented in [NR 180xx]. Mars-equator fixed frame of date This equatorial inertial frame is used for the definition of the orbits around Mars. The associated coordinate system is centered in the current Mars position of epoch. Its z-axis points in the direction of the current Mars axis of rotation; its x-y-plane is contained in the current equator plane of date, with x laying at the intersection between the equator plane and the Mean Earth Equator of Mars-equator rotating frame of date This non-inertial, rotating frame is used for the definition of the inhomogeneity terms of the Mars gravity model and the entry conditions relative to the Mars rotating atmosphere. The associated coordinate system is centered in the current Mars position of epoch. Its z-axis points in the direction of the current Mars axis of rotation; its x-y-plane is contained in the current equator plane of date, with x pointing at the reference meridian and rotating with the planet. #[SCC- 0030] The time convention used for epochs shall be Modified Julian Date of 2000, which is 0 at epoch 2000/1/1, 0:0:0. The time scale used in mission analysis work is the Ephemeris Time (ET). ET differs from TAI in a given quantity equal to s and TAI differs from UTC an integer number of seconds introduced so that UTC follows the Earth rotation (leap seconds). The last leap second was introduced at 2008/12/31 and 2014, Thales Alenia Space

30 ISSUE : 3-Working Page: 29/184 currently TAI-UTC=34 s. Predictions for TAI-UTC account for another leap second so that in the period 2013 to 2017 TAI-UTC=35 s. As a consequence, UTC can be obtained from the ET provided in this document by subtracting roughly 67 s. #[SCC- 0040] If other reference frames or time conventions are introduced, they shall be defined with respect to one of the reference frames or time conventions defined above. 4.2 General Mission Requirements #[SCC- 0050] The SCC shall be designed to comply with the Launcher and Launch Site requirements, rules and constraints specified in [NR 18027], implementing the specific requirements stated in this specification. MSRD MI-10, MSRD SC-SY-330 #[SCC The mission design shall be compatible with a Proton-M/Breeze M launch from Baikonur in April/May MSRD MI-10 #[SCC- 0070] The SCC shall be designed to allow achieving of the Technology and Science objectives defined in 3.1 of this Specification. MSRD MI-210 #[SCC- 0080] The SCC shall be designed to support the implementation of the SCC mission phases reported in Table , Thales Alenia Space

31 ISSUE : 3-Working Page: 30/184 #[SCC- 0090] The SCC shall be designed to comply with the Mission Timeline addressed in of this Specification. #[SCC- 0100] The SCC shall be designed to support the DMC mission phases reported in Table 3-1. In particular: DMC Separation Preparation and Execution by implementing the SCC attitude required for the separation and commanding the actuation of the Separation Mechanisms #[SCC- 0110] The nominal mission design shall be based on direct entry of the DMC into the Martian atmosphere from the incoming hyperbolic approach. In particular, the mission design shall be compatible with a baseline transfer based on a direct injection to a Mars T2 transfer trajectory with no DSM and a fixed Mars arrival date on 15 th January 2019 as specified in [IR 18022] 4.1. MSRD MI-30, MSRD MI-60 MoV: [SCC: A] #[SCC- 0120] The mission design shall enable the landing of the ExoMars LP at any latitude in the range 5 degrees South to 25 degrees North of the Martian surface. Comment: compatibility with requirement SCC-0130 has to be considered too. MSRD MI-70 MoV: [SCC: A] #[SCC- 0130] The mission design shall enable access to landing sites located in the latitude band specified in [SCC and with an altitude of no more than (minus) 2 Km (TBC) above the Mars MOLA zero level. 2014, Thales Alenia Space

32 ISSUE : 3-Working Page: 31/184 MSRD MI-80 #[SCC- 0140] The Spacecraft Composite designs shall comply with the nominal mission specified in Chapter 4. of [IR 18022]. Comment: The nominal interplanetary transfer is a delayed T1, identified as 2018 Short Transfer Early Arrival, with unconstrained arrival velocity ranging between km/s and km/s and arrival at an Ls of 324 degrees. MSRD MI-50 #[SCC- 0150] The baseline mission design shall allow landing of the DMC after the Global Dust Storm Season, at Solar Longitude 324 degrees (TBC). MSRD MI-90 MoV: [SCC: A] #[SCC- 0155] The back-up mission shall be designed to minimize exposure to the Global Dust Storm Season during the surface mission. Comment: Requirement not applicable to the SCC MSRD MI-91 MoV: [SCC: NTBV] #[SCC- 0156] The mission shall be designed to allow visibility from Earth of the EDL event. Comment: Requirement not applicable to the SCC and its Modules MSRD MI-110 MoV: [SCC: NTBV] #[SCC- 0160] 2014, Thales Alenia Space

33 ISSUE : 3-Working Page: 32/184 The Spacecraft Composite and its elements design shall comply with the back-up transfer scenario specified in Chapter 5 of [IR 18022]. Comment: The back-up interplanetary transfer is a delayed T1, identified as 2020 Short Transfer Late Arrival, with unconstrained arrival velocity ranging between km/s and km/s and arrival at an Ls of 34 degrees. MSRD MI-40, MSRD-CM-SY-90, MSRD DM-SY-170 #[SCC- 0170] The mission design shall enable a landing accuracy, defined as the downrange semi-major and semiminor axes of the landing ellipse, smaller than 50 km (TBC) and 7.5 km (TBC) respectively, at 99% (90% confidence level). Comment: This requirement has to be translated into navigation -V and attitude accuracy for the S/C Composite. The demonstration of this requirement will be obtained by means of covariance analysis and/or Monte Carlo analysis with the error assumptions to be listed in [NR 18022]. MSRD MI-120, MSRD DM-SY-120 MoV: [SCC: A] #[SCC- 0180] The mission shall be designed such that the Carrier Module breaks up and burns up in the Martian atmosphere after release of the DMC. MSRD MI-140 MoV: [SCC: A] #[SCC- 0190] The Spacecraft Composite design shall ensure separation between the Carrier Module and the DMC without risk of re-contact after separation, in nominal and worst case conditions for the system, the separation mechanism and the mechanical and electrical components of the activation chain. Comment: in case a Collision Avoidance Maneuver cannot be avoided, it will be implemented by an automatic and hardcoded thrust command, considering that the HW located on DMC (i.e. ESA-OBC1 & 2, IMU) will not be available anymore, such that the thrusters force pushes in the direction opposite to separation, until the propellant tanks are empty MSRD MI-150, MSRD SC-SY-50 MoV: [SCC: A] #[SCC- 0200] 2014, Thales Alenia Space

34 ISSUE : 3-Working Page: 33/184 The mission shall be compatible with a DMC Coast phase of up to 30 minutes (TBC). MSRD MI-160 #[SCC- 0210] During all mission not critical phases, the Spacecraft Composite design shall allow for check-out of all its Modules and Science Payload. MSRD SC-SY-370, MSRD SC-SY-420 #[SCC- 0220] Spacecraft Composite shall provide to the Ground Control sufficient data to perform: Failure detection and isolation Switch-over to the redundant resources Shut-down and isolation of malfunctioning parts MSRD SC-SY Launch and Early Orbit Phase #[SCC- 0230] The SC Composite design shall be compatible with a launch window of 21-day: the present LW opens on 7 th May 2018 and closes on 27 th May MSRD-MI-10, MSRD-MI-20, MSRD SC-SYS-340 #[SCC- 0240] The SC Composite shall be compatible with direct insertion into an Earth escape hyperbolic trajectory (known as delayed Type 1 Earth-to-Mars Transfer Trajectory), and the time from lift off until separation from the launcher upper stage is approximately 11.5 hours (TBC) in the worst case for the back-up mission (i.e. about 50% longer than the duration for the baseline scenario). Comment 1: The Earth escape hyperbolic trajectory parameters are different for each of the 21 days of the launch window and are provided in [IR 18022]. Comment 2: The nominal mission design foresees a fixed Mars arrival date on 15 th January MSRD-30, MSRD , Thales Alenia Space

35 ISSUE : 3-Working Page: 34/184 #[SCC- 0250] The SC Composite shall be ready for launcher dispersion correction maneuver within (TBD) days from launch. Comment: This requirement provides a maximum limit within which the SCC must have performed all necessary set up and calibrations to perform its first ΔV maneuver. MSRD MI-10, MSRD MI-20 #[SCC- 0260] The SC Composite shall be compatible with launching at a specified time of the day expressed in hours, minutes and seconds. Comment: An accurate launch time is standard procedure for many missions and is typical for interplanetary missions. The actual launch time for every day of the launch window has to be calculated by the launcher authority. MSRD-10, MSRD-20 #[SCC- 0270] The SCC and its elements shall be designed for a launch abort case in case the umbilical remains disconnected up to two hours (TBC). MSRD SC-SYS-350 #[SCC- 0280] The SCC shall start to transmit telemetry after separation from the launch vehicle as soon as allowed by the launch vehicle EMC requirements, as per [NR 18027] and the ITU flux density requirements on Earth (see [NR 021]). MSRD SC-SYS-360 #[SCC- 0290] All launch related mass calculations shall not account for the Launcher I/F adapter which is provided by the Launcher authority and already included in the performance. 2014, Thales Alenia Space

36 ISSUE : 3-Working Page: 35/184 Comment: This means that the launchable mass corresponds to the SCC mass after separation from the last stage of the missile. #[SCC- 0300] The SC Composite and its elements shall be compatible with the conditions at separation from the launcher shown in Table 4-1. Parameter SCC Attitude SCC angular Rate (right-hand about SCC axes) SCC- to-lv relative separation velocity Value -X-SC axis pointed to Sun ± 5 º (TBC) 6 º/s ± 1 º/s around X-SC axis (TBC) 0 º/s ± 1,1 º/s around Y-SC and Z-SC axes (TBC) > 0.35 m/s (TBC) MoV: [SCC: A] Table 4-1 SC Composite dynamic conditions at separation from the launcher #[SCC- 0310] During escape sequence, The SC Composite and its elements design shall be compatible with the eclipses defined in 4.2 Table 3 (Nominal Mission) and 5.2 Table 27 (Back Up mission) of [IR 18022]. #[SCC- 0320] The SCC and its elements shall be compatible with a Launch timeline (for power up on Launch PAD, Liftoff, Ascent and Parking Orbit) relaying on its internal battery supplied power for TBD hours. MSRD MI-10 MoV: [SCC: A] 4.4 Interplanetary Cruise #[SCC- 330] The SC design shall be compatible with maximum interplanetary cruise duration of 10 months. 2014, Thales Alenia Space

37 ISSUE : 3-Working Page: 36/184 Comment: As the arrival date is fixed the duration of the cruise depends on the day of launch; the launch window is presently 21 days, rounded off to 1 month for the purpose of this requirement. MSRD-10, MSRD-20 #[SCC- 0340] The Composite SC shall do not consider the capability to implement Deep Space Maneuvers during the Interplanetary Cruise. Only corrections of about 25 m/s for the Launcher Injection Correction (LIC) and 25 m/s for the transfer navigation have to be considered. Comment: All delta-v maneuvers shall be performed with a confidence level of at least 99.7% (3σ). MSRD MI-30 #[SCC- 0350] During the Cruise phase and prior to the DMC separation, the Spacecraft Composite design shall allow for adjustment of parameters of the EDL sequence by dedicated Ground Control command. MSRD SY-400 #[SCC- 0360] During the Cruise phase and prior to the DMC separation, the Spacecraft Composite design shall be such that the telemetry parameters needed to allow post-facto reconstruction of the actually performed delta-vs are stored onboard for subsequent transmission to Ground Control. MSRD SY Mars Approach #[SCC- 0370] The Composite and its elements shall be compatible with an arrival at Mars on a fixed date, according to an hyperbolic trajectory having the characteristics defined in Table 2 4 and Table 26 5 of [IR 18022] for nominal and back-up transfer scenario respectively 2014, Thales Alenia Space

38 ISSUE : 3-Working Page: 37/184 MSRD MI CM-DMC Separation, DM Entry, Descent and Landing #[SCC- 0390] The Spacecraft and its elements shall be designed to allow a safe landing of the DMC onto the Mars surface. MSRD MI-70, MSRD DM-SY-20 #[SCC- 0400] The SC Composite design shall take into account that the CM-DMC separation shall take place up to 0.5 hr (TBC) before the DMC reaches the Entry Interface Point. MSRD MI-160, MSRD DM-SY-50 #[SCC- 0410] The DMC shall be designed to command the CM-DMC separation from the ESA-OBC1 DM-SYS-40 #[SCC- 0420] During CM-DM separation the SC Composite and its elements shall consider that the alignment between the Spacecraft velocity vector at EIP (Xvv) with respect to the Sun Aspect Angle (SAA) and the Earth Aspect Angle (EAA) ranges will be in the following ranges +Xvv-SAA = Xvv-EAA = MoV: [SCC: A] #[SCC- 0430] Following separation from the CM, the DMC mission shall be decomposed into the following phases: 2014, Thales Alenia Space

39 ISSUE : 3-Working Page: 38/184 Coast Phase, defined as the period between separation and EIP Entry Phase, defined as the period between EIP and Parachute opening command Descent Phase, defined as the period between Parachute opening command and Parachute release Landing Phase, defined as the period between Parachute release and stabilisation on Mars surface Surface Phase, defined as the period between the stabilisation on Mars surface and transmission and the end of the surface science mission. MSRD MI-70, MSRD DM-SY-20, MSRD DM-SY-30 #[SCC- 0440] The SC Composite and its elements shall be designed to implement a DMC ballistic entry, i.e. to allow a dynamic and gyroscopic stabilization by spin at Separation. MSRD DM-SY-80, MSRD DM-SY-90 #[SCC- 0450] The entry sequence initiation shall rely on at least on 2 independent measurement chains (i.e. IMU measurements and predefined timer) MSRD DM-SYS-100 #[SCC- 0460] The DMC Flight Path Angle (FPA) error at EIP shall not exceed ± 0.3 deg (3-sigma). Comment: The nominal FPA is -TBD deg throughout all launch period. #[SCC- 0470] The CM-DMC separation shall be such that the relative velocity between the modules is at least 0.6 m/s (in case of separation commanded 30min before EIP) or at least 0.8 m/s (in case of separation commanded 20min before EIP) Comment: This relative velocity is to avoid re-contact between the CM and the DMC and guaranteeing an average distance of 1 Km between the CM and DMC. 2014, Thales Alenia Space

40 ISSUE : 3-Working Page: 39/184 MSRD DM-SYS-110 MoV: [SCC: A] #[SCC- 0480] The CM-DMC separation shall induce a transversal velocity (in the Y S -Z S plane) on the DMC not greater than 10-2 m/s (3-sigma) (TBC). MSRD DM-SYS-110 MoV: [SCC: A] #[SCC- 0490] The uncertainty of the DMC linear separation rate shall be better than m/s (TBC). Comment 1: This uncertainty is calculated on the DM separation rate (not on the relative one specified above). Comment 2: This uncertainty must be demonstrated using a single mass properties configuration. This configuration will be calculated on the basis of the propellant usage until the time of separation. MSRD DM-SYS-110 MoV: [SCC: A] #[SCC- 0500] The SCC shall release the DMC with a minimum spin rate around the X DM axis of 2.5 rpm. MoV: [SCC: A] #[SCC- 0510] All the DMC EDL phase, up to the touch-down of Mars surface, shall be performed under the control of the OBC 1. #[SCC- 0515] The Landing Module shall be designed to protect itself, the RM and the scientific instruments from interaction of the plume and the Martian terrain MSRD-DM-SY , Thales Alenia Space

41 ISSUE : 3-Working Page: 40/184 #[SCC- 0520] The landing and Landing Platform stabilization events shall be detected by the OBC 1. #[SCC- 0530] Once the Landing Platform has been recognized as stable, the OBC 1 shall command the opening of the LP Landing Gears. #[SCC- 0540] After the completion of the LP Landing Gears deployment event, the OBC 1 shall command the RM power On which will autonomously provide for the release (or partial release) of the its Solar Panels to start its check-out when still on the LP. #[SCC- 0550] RM check-out, which includes also the egress preparation activities, egress and start of RM commissioning, shall be performed with control by Ground and will be completed within 10 sols (TBC). #[SCC- 0560] After TBD <time> from the touch down, the control of the LP shall be passed to the OBC 2 for LP checkout. Comment 1: the switch between the two computers will be commanded by the OBC 1 or by Ground (TBD). Comment 2: LP and RM check-out are supposed to occur in parallel 2014, Thales Alenia Space

42 ISSUE : 3-Working Page: 41/184 #[SCC- 0570] After TBD <time> after the completion of RM checkout, Ground will command the RM egress from the LP. #[SCC- 0580] Once on the Mars Surface, the RM shall start its mission lasting 218 sol. #[SCC- 0590] After the completion of the RM egress, the LP shall start its mission lasting TBD sols. Comment: the LP operations on Mars lasting 1 Martian year have to be verified against the lifetime of the DM ESA provided equipment s. MSRD DM-SY General Flight Parameters Sun and Earth Angle and Distance #[SCC- 0600] The SC Composite and its elements design shall comply with Sun-Earth-SCC (blue line) and Sun-SCC- Earth (red line) angles shown in Figure 4-1and Figure , Thales Alenia Space

43 ISSUE : 3-Working Page: 42/184 Figure 4-1 Angles Evolution for ExoMars 2018 Nominal Mission, LPO Figure 4-2 Angles Evolution for ExoMars 2018 Nominal Mission, LPC 2014, Thales Alenia Space

44 ISSUE : 3-Working Page: 43/184 Comment: Figure 4-1and Figure 4-2 show the Sun-Earth-Spacecraft and Sun-Spacecraft-Earth angles. There will be an opposition event in late July / early August 2018 when the Earth passes between the Sun and the Spacecraft. There is no conjunction event. MSRD MI-30, MSRD MI-40 #[SCC- 0610] The SC Composite and its elements design shall be compatible with distances to the Sun ranging from 1 to 1.62 AU. MSRD MI-30, MSRD MI-40 #[SCC- 0620] The SC Composite and its elements design shall be compatible with distances to the Earth up to 1.9 AU. Comment: The Earth-Mars (green line), Sun-Mars (blue line) distances along the ExoMars mission timeline are as shown in Figure 4-3. Figure 4-3 Earth-Mars and Sun-Mars distances 2014, Thales Alenia Space

45 ISSUE : 3-Working Page: 44/184 MSRD MI-30, MSRD MI Eclipses #[SCC- 0630] The ExoMars SC can undergo in-flight sun-eclipses due to: Earth in the LEOP (SC Composite mission) Eclipse history during escape First eclipse entry/exit [hh:mm from liftoff] 01:00 / 01:36 00:55 / 01:32 Second eclipse entry/exit [hh:mm from liftoff] 02:30 / 02:57 02:25 / 03:01 Third eclipse entry/exit [hh:mm from liftoff] 06:28 / 06:52 05:29 / 06:09 Fourth eclipse entry/exit [hh:mm from liftoff] 14:38 / 14:57 15:01 / 15:46 The specified eclipse duration does not include any margin and therefore the margin shall be taken on the power subsystem as per relevant chapters. MSRD MI-30, MSRD MI-40 #[SCC- 0640] Eclipse entry, when applicable, shall be automatically detected onboard and managed so as not to interrupt nominal operations Sun-Earth-Mars / Sun-Mars-Earth Alignment (Conjunction events) #[SCC- 0650] Then SCC design shall be compatible with the occurrence of solar conjunctions as defined in Table , Thales Alenia Space

46 ISSUE : 3-Working Page: 45/184 Table 4-2 SEM Angle for 2019 and 2021 Events Comment : The Earth-Sun-Mars alignments (also known as Conjunctions) occur when the Sun is between Earth and Mars as shown in Figure 4-4: both Sun-Mars-Earth angle (SME) and Sun-Earth-Mars angle (SEM) are near 0. EARTH Sun-Earth-Mars 0 SUN Sun-M ars-earth 0 MARS = Spacecraft Figure 4-4 SEM and SME alignment (Conjunction) 2014, Thales Alenia Space

47 ISSUE : 3-Working Page: 46/184 MSRD MI-30, MSRD MI SCC Lifetime SCC On-Ground Lifetime #[SCC- 0660] The SCC design shall be compatible with Ground activities lasting up to 48 months. Comment: The requirement applies to AIT/AIV activities implemented on both SCC and integrated SCC levels (including Launch Campaign) SCC (and Modules) Lifetime #[SCC- 0670] The SCC Modules shall have an in-flight/operative lifetime from Launch of at least: CM : 1 year DM-SP : 2 years (*) (TBC based on resolution of SCC-0590) RM : 1.5 year (*) (*) Operative only for periodical check-out during Cruise MSRD-SC-SY-440, MSRD-CM-40, MSRD-DM-SY SCC Storage #[SCC- 0680] The SCC Modules lifetime shall be compatible with a controlled storage up to 2.5 years (either in standalone configuration or once integrated into the SCC). Comment: the specified storage period corresponds to the next launch opportunity and considers an unfueled state. This requirement does not apply to Batteries design and procurement. MSRD-SY , Thales Alenia Space

48 ISSUE : 3-Working Page: 47/ , Thales Alenia Space

49 ISSUE : 3-Working Page: 48/ SCC SYSTEM REQUIREMENTS 5.1 Mass Properties Mass Budget Control #[SCC- 0690] The SCC Mass budget shall be maintained, documented and controlled following the rules specified in [NR 05007] MSRD SYS-60, MSRD SYS-70, MSRD SYS-90, MSRD SYS-100, MSRD SYS-110 #[SCC- 0700] The mass budget of each of the Modules shall show the allocation for balancing mass and the corresponding provision for mounting shall be implemented in the design. Comment 1: The system mass margin and the ESA dry mass reserve shall not be used for any balancing mass Comment 2: An analysis at system level shall be performed to assess the balancing of the Spacecraft Composite stack with all Modules integrated MSRD SYS-120 #[SCC- 0710] The DMC propellant mass shall be calculated based on its dry mass (Mdmo of the DMC). MSRD SYS-130 #[SCC- 0720] The DMC total (wet, in case of liquid propulsion) mass shall be calculated as the sum of the DMC dry mass and the DMC propellant mass (including the pressurant). MSRD SYS-140 #[SCC- 0730] 2014, Thales Alenia Space

50 ISSUE : 3-Working Page: 49/184 The Spacecraft Composite dry mass (Mdmo of the SC Composite) shall be calculated as the sum of the Carrier Module dry mass (Mdmo of the CM) and the DMC total (wet, in case of liquid propulsion) mass. MSRD SYS-150 #[SCC- 0740] The Carrier Module propellant mass shall be calculated based on the Spacecraft Composite dry mass (Mdmo of the SC Composite). MSRD SYS-160 #[SCC- 0750] Spacecraft Composite total (wet) mass shall be calculated as the sum of the SC Composite total dry mass and the Carrier Module propellant mass. MSRD SYS-170 #[SCC- 0760] The Carrier Module GNC propellant mass shall be calculated considering an average of one Safe Mode (SM) occurrence per year (365 days) TBC. MSRD SYS Mass Margin Policy #[SCC- 0770] The SCC Mass maturity and System Margins shall be established in accordance with the rules specified in [NR 0101] Comment: this applies to any of the SCC element, including CFI. MSRD SYS-70, MSRD SYS-110 #[SCC- 0780] Deleted 2014, Thales Alenia Space

51 ISSUE : 3-Working Page: 50/ Mass #[SCC- 0790] The SCC wet mass (without Launcher Adapter) to be used for Launcher analyses shall not exceed 2900 Kg + TBD Kg as ESA mass reserve including maturity and system margins. Comment 1: System margin policy shall be applied following the requirements stated in [NR 05007] Comment 2: The SCC Modules will include allocation for balancing masses to meet requirements specified in MSRD CM-SY-20, MSRD SC-SY-185, MSRD DM-SY-150, MSRD DM-SY-10, CM-SY-10 MoV: [SCC: A, T] [S/S: T] #[SCC- 0795] The CM shall be designed to be compatible with a SCC wet mass of 2900 Kg + TBD Kg as ESA mass reserve, without considering the Launcher Adapter, including maturity and system margins. MSRD CM-SY-20 MoV: [SCC: A, T] [S/S: T] #[SCC- 0796] The Mass allocation to be specified to Modules shall be as follows: CM: DMC: 780 Kg (dry mass, including the part of the CM-DM Separation mechanism that will stay on the CM after Separation) + Propellant mass as specified in SCC Kg (total wet mass, including the mass allocated to the RM (350 Kg), the Surface Science Payload (50 Kg), the part of the CM-DM Separation mechanism that will stay on the DMC after Separation) and tbd Kg as ROS mass reserve, to be reported in the DM mass budget MSRD CM-SY-20, MSRD DM-SY-10, MSRD DM-SY-150, MSRD-DM-SY-15, MSRD-SC-SY- 112 MoV: [SCC: A, T] [S/S: T] #[SCC- 800] The mass specified for the DMC, which includes the propellant necessary to perform a safe EDL on Mars surface, shall consider a minimum of 2 % (TBC) provision on the total propellant mass to be applied to estimate the propellant residuals mass for calculating the total propellant needs. 2014, Thales Alenia Space

52 ISSUE : 3-Working Page: 51/184 MSRD SC-SY-200 #[SCC- 810] The CM propellant mass, necessary to implement the required ΔV maneuvers specified in SCC- 340 and the Cruise GNC shall not exceed 120 Kg, including the 100% margin for GNC estimated consumption. MSRD SC-SY-190, MSRD-CM-SY-25 #[SCC- 820] A 5% (TBC) margin shall be applied to compute the DMC propellant mass for braking and attitude control maneuvers. MSRD DM-SY Center of Gravity & Moments of Inertia #[SCC- 0830] The SCC shall be balanced such to allow SCC Stable Spin (SCC maximum Momentum of Inertia around the longitudinal axis X- SC ) Stable GNC Operations Stable V maneuvers as specified in 4.4, requirement SCC- 340 Stable CM-DM separation MoV: [SCC: A] #[SCC- 840] The SCC CoG shall be nominally located on the X SC axis. The maximum displacement between the SCC CoG and the X SC axis shall not exceed 20 mm in any lateral direction (TBC). Comment: the current requirement value is in line with what specified by the Launcher supposing that the SCC Xsc is coincident with the LV longitudinal axis. Currently, the presence of the TBC is due to the more stringent constraints potentially coming from Cruise GNC. 2014, Thales Alenia Space

53 ISSUE : 3-Working Page: 52/184 #[SCC- 850] The SCC MoI s (calculated with respect the SCC CoG) shall respect the following rules: Ixx/Iyy(IZZ) > 1.15 SCC inertia cross products Ixy/ Ixz/ Iyz < 1kg*m 2 #[SCC- 860] The SCC Mass Properties measurement accuracy shall be consistent with the tolerance for the variable to be measured, as specified in [IR 18014] and should be at least one third of the tolerance itself. #[SCC- 870] Deleted 5.2 Reference Coordinates SCC Reference Coordinates #[SCC- 0880] The SCC Reference Coordinates (*-SC) shall be a right-handed, orthogonal coordinate system to be used for geometrical configuration, design drawings and dimensions defined as follows: O- SC origin located on the (SCC Spacecraft Composite / Launcher separation plane at the center of the Spacecraft interface ring X-SC axis orthogonal to the Spacecraft Composite/Launcher separation plane, pointing positively from the separation plane towards the DMC Y-SC axis orthogonal to the X-SC axis and nominally oriented toward the side CM radiator (side where PCDU is located) (TBC). This direction will be further marked with a keyway on the SC to Launcher interface flange Z-SC axis completing the right handed coordinate system such that: Z = X ^ Y Note: The SCC Reference Coordinates shall coincide with the CM reference Coordinates. 2014, Thales Alenia Space

54 ISSUE : 3-Working Page: 53/ CM Reference Coordinates #[SCC- 0885] The CM Coordinates (*-CM) shall be a right-handed, orthogonal coordinate system used for geometrical configuration, design drawings and dimensions, and defined as follows: O-CM O-SC +X-CM +X-SC +Y-CM +Y-SC +Z-C +Z- SC DM Reference Coordinates #[SCC- 0890] The DM Coordinates (*-DM) shall be a right-handed, orthogonal coordinate system used for geometrical configuration, design drawings and dimensions, and defined as follows: O-DM origin is located on the DM/CM Adapter mounting plane (DM side) at the intersection with the revolution axis of the DM conical shape (i.e. located on the DM mounting plane coinciding with the geometrical center of circumference which goes through centers of fastening elements for the separation system). Note: currently, the CM-DM Separation Plane coincides with the DM mounting Plane +X-DM axis is orthogonal to the Descent Module/Adapter mounting plane, pointing positively toward the Front Shield nose. Same orientation and direction of +X-SC +Y-DM axis perpendicular to X-DM and to the RM direction of egress, pointing positively towards the center of the fastening element for installation of the DM on the Adapter, located on the Landing Platform Experiment Boom side. +Z-DM axis completes the right handed coordinate system. The +Y direction shall be marked with a keyway on the lower flange of the Separation System interfacing with the CM CM-DM Separation Assembly Reference Coordinates #[SCC- 0895] The CM-DM Separation Assembly Coordinates (*_SEP) shall be a right-handed, orthogonal coordinate system used for geometrical configuration, design drawings and dimensions, and defined as follows: 2014, Thales Alenia Space

55 ISSUE : 3-Working Page: 54/184 O-SEP origin is located on the DM/CM Adapter (CM side) mounting plane at the intersection with the revolution axis of the DM conical shape (i.e. located on the DM/CM Adapter-CM mounting plane coinciding with geometrical center of circumference which goes through centers of fastening elements of the Adapter, CM side). +X-SEP axis is orthogonal to the Adapter/CM mounting plane, pointing positively toward the Front Shield nose. It coincides with axes +X-CM, +X-DM and +X-SC +Y-SEP axis perpendicular to X-SEP, directed to the center of a fastening element (TBD) for installation on CM. i is rotated wrt Y-CM and Y-DM axes by (counterclockwise rotation around +XSEP axis) Figure 5-1shows the different SCC Reference Coordinates Systems 2014, Thales Alenia Space

56 ISSUE : 3-Working Page: 55/184 Figure 5-1 SCC, CM, DM AND CM-DM Separation Adapter Reference Coordinates 2014, Thales Alenia Space

57 ISSUE : 3-Working Page: 56/ RM Reference Coordinates #[SCC- 0900] The Rover Module Coordinate Frame shall be a right-handed, orthogonal coordinate system used for geometrical configuration, design drawings and dimensions. It is defined as follows (details can be found in [NR 0400]: The origin ORB is at the intersection of the following planes (see Figure 5-2): A plane mm aft and parallel to Plane 1 - the plane formed by the nominal bolt axes of the front body HDRMs Plane 2 - the plane of symmetry between the front body HDRM nominal bolt axes (= rover body midplane) A plane 30 mm below and parallel to Plane 3 - the plane of the rover body base inner skin mould surface XRM = roll axis, in direction of movement, forward is positive (+XRB) ZRB = yaw axis, coinciding with the gravity direction on flat, horizontal terrain, zenith is positive (+ZRB) +YRB is the left side of the Rover and the Vehicle, -YRB is the right side Figure 5-2 RM Reference Coordinates Parents 2014, Thales Alenia Space