ExoMars 2018 Spacecraft Composite Requirements...

REFERENCE:

DATE:

EXM-M2-SYS-AI-0020

28/03/2014ISSUE: 3

ExoMars 2018 Spacecraft CompositeRequirements Specification

Written by Responsibility+ handwritten signature if no electronic workflow tool

Musetti Bruno Signed as AUTHORon 26/03/2014 16:37

Verified By

Ferro Claudio Signed as CHECKERon 31/03/2014 18:27

Palermo Annamaria Signed as DOCUMENTATION MANAGERon 02/04/2014 15:10

Approved By

Allasio Andrea Signed as PROGRAM MANAGERon 02/04/2014 15:09

Realeased By

Approval evidence is kept within the documentation management system.

THALES ALENIA SPACE INTERNAL

This document is not to be reproduced, modified, adapted, published, translated in any material form in whole or in part nor disclosed to any third party without the prior written permission ofThales Alenia Space.

© 2012, Thales Alenia Space 83230326-DOC-TAS-EN/002

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014

ISSUE : 3-Working Page : 1/184


This document is not to be reproduced, modified, adapted, published, translated in any material form in whole or in part nor disclosed to any third party without the prior written permission of Thales Alenia Space.

2014, Thales Alenia Space Template 83230326-DOC-TAS-EN/002

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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014

ISSUE : 3-Working Page: 2/184




CHANGE RECORDS

ISSUE DATE § CHANGE RECORDS AUTHOR

1 23-05-2013 1ST Issue for System Requirements Review B. Musetti

2 15-11-2013 2nd Issue Implementing the Outcomes of System Requirements Review and ESA MSRD EXM-M2-RSD-ESA-00003 Draft 1, Rev 3 with Industries comments provided with B. Musetti E_Mail dated 24-10-2013 and S. Aleksashkin e_Mail dated 23-10-2013.

Musetti

Revisited Chapter 4 for consistency with the new ExoMars Mission Analysis Guidelines (MAG) – EXM-G2-TNO-ESC-00003 Issue 1 Rev. 0 Chapter 5.3 Mass updated as per SRR directives.

Chapter 5.1.4 MoI’s requirements updated. Chapter 5.3. Communication updated in consistency with new SG-IRD EXM-G2-IRD-ESC-00001 and WG agreements. SCC- 1520 updated as per WG outcomes. Chapter 5.7.2 updated as per WG outcomes.

Chapter 6.2.5 updated as per WG outcomes.

Deletion of Requirement SCC- 1360 as per SRR MS-30_AI-001disposition. Update of Requirement SCC- 4110 as per SRR MS-32_AI-001disposition and moved to § 5.7.2.7 Update of Requirement SCC- 0840 as per SRR MS-36_AI-001disposition. Update of Requirement SCC- 0370 as per SRR RID MS-77 disposition.

Update of Requirement SCC- 0400 as per SRR MS-79_AI-001disposition.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





ISSUE DATE § CHANGE RECORDS AUTHOR

Update of Requirement SCC- 5100 as per SRR RID AP-71disposition.

3 28-03-2014 Following paragraphs have been updated reflecting the Lavochkin comments:

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-5170.

B. Musetti

SCC-460 updated based on “EXM-G2-TNO-ESC-00006 Preliminary Navigation Analysis”.

Deletion of Requirements SCC-1485 ad per MSRD Issue 02.

Table 4.1 to remove TBD’s

§5.1.3 Mass requirements

Introduction of new requirement SCC- 4645.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





TABLE OF CONTENTS

1. INTRODUCTION .............................................................................................................................. 10

1.1 Scope........................................................................................................................................................10

1.2 Structure of the Document .....................................................................................................................12

1.3 Acronyms and Terminology...................................................................................................................12

1.4 Conventions.............................................................................................................................................12

2. DOCUMENTS................................................................................................................................... 13

2.1 Normative Documents ............................................................................................................................13 2.1.1 Definition of Normative Documents ......................................................................................................13 2.1.2 ESA Normative document.....................................................................................................................13 2.1.3 A147Launcher Normative document ....................................................................................................14 2.1.4 Standards and Handbooks ...................................................................................................................15

2.1.4.1 ECSS............................................................................................................................................15 2.1.4.2 CCSDS.........................................................................................................................................17 2.1.4.3 Other Standards ...........................................................................................................................17

2.1.5 Thales Alenia Space Italia Normative Documents................................................................................18

2.2 Informative Documents ..........................................................................................................................19 2.2.1 Definition of informative documents......................................................................................................19 2.2.2 ESA/ROS/NASA Informative Documents .............................................................................................19 2.2.3 Thales Alenia Space Italia Informative Documents ..............................................................................19 2.2.4 Other Informative Documents ...............................................................................................................19

3. EXOMARS 2018 MISSION AND SYSTEM DEFINITION ................................................................ 20

3.1 Mission Objectives..................................................................................................................................20

3.2 ExoMars 2018 Mission Concept.............................................................................................................21 3.2.1 ExoMars 2018 Mission Phases.............................................................................................................22 3.2.2 Mission Timeline ...................................................................................................................................23

3.3 ExoMars 2018 System Definition...........................................................................................................23

3.4 ExoMars 2018 Mission Scientific Payloads ..........................................................................................25 3.4.1 Rover Module Science Payload............................................................................................................25 3.4.2 Landing Platform Science Payload (TBC) ............................................................................................25

3.5 ExoMars 2018 Product Tree and Responsibility sharing....................................................................25

4. EXOMARS 2018 MISSION REQUIREMENTS ................................................................................ 28

4.1 Mission Reference Frames and Time Conventions.............................................................................28

4.2 General Mission Requirements..............................................................................................................29

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





4.3 Launch and Early Orbit Phase ...............................................................................................................33

4.4 Interplanetary Cruise ..............................................................................................................................35

4.5 Mars Approach ........................................................................................................................................36

4.6 CM-DMC Separation, DM Entry, Descent and Landing .......................................................................37

4.7 General Flight Parameters......................................................................................................................41 4.7.1 Sun and Earth Angle and Distance.......................................................................................................41 4.7.2 Eclipses.................................................................................................................................................44 4.7.3 Sun-Earth-Mars / Sun-Mars-Earth Alignment (Conjunction events).....................................................44

4.8 SCC Lifetime ............................................................................................................................................46 4.8.1 SCC On-Ground Lifetime......................................................................................................................46 4.8.2 SCC (and Modules) Lifetime.................................................................................................................46 4.8.3 SCC Storage .........................................................................................................................................46

5. SCC SYSTEM REQUIREMENTS .................................................................................................... 48

5.1 Mass Properties.......................................................................................................................................48 5.1.1 Mass Budget Control.............................................................................................................................48 5.1.2 Mass Margin Policy ...............................................................................................................................49 5.1.3 Mass......................................................................................................................................................50 5.1.4 Center of Gravity & Moments of Inertia.................................................................................................51

5.2 Reference Coordinates ...........................................................................................................................52 5.2.1 SCC Reference Coordinates ................................................................................................................52 5.2.2 CM Reference Coordinates ..................................................................................................................53 5.2.3 DM Reference Coordinates ..................................................................................................................53 5.2.4 CM-DM Separation Assembly Reference Coordinates ........................................................................53 5.2.5 RM Reference Coordinates ..................................................................................................................56 5.2.6 Reference Coordinates relationship summary......................................................................................57

5.3 Communications .....................................................................................................................................57 5.3.1 General .................................................................................................................................................57 5.3.2 X-Band Communication ........................................................................................................................58 5.3.3 UHF Communication.............................................................................................................................69 5.3.4 Link Budget ...........................................................................................................................................72 5.3.5 RF Compatibility Test............................................................................................................................73

5.4 Power........................................................................................................................................................73 5.4.1 General .................................................................................................................................................73 5.4.2 Power budget ........................................................................................................................................74

5.5 Science Payload Package Accommodation .........................................................................................75

5.6 Mission Maneuvers .................................................................................................................................75 5.6.1 Delta-V Requirements...........................................................................................................................75 5.6.2 Propellant Budget..................................................................................................................................76

5.7 SCC Operations and Autonomy.............................................................................................................77 5.7.1 General .................................................................................................................................................77 5.7.2 SCC Modes...........................................................................................................................................77

5.7.2.9 EDL Phases..................................................................................................................................86 5.7.3 SCC FDIR .............................................................................................................................................86

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.7.4 SCC Operations ....................................................................................................................................89 5.7.4.1 Payloads Operations ....................................................................................................................89

5.7.5 SCC Autonomy .....................................................................................................................................89

6. DESIGN AND PERFORMANCE REQUIREMENTS ........................................................................ 92

6.1 Failure Tolerance & Redundancy Implementation Requirements .....................................................92

6.2 Electrical...................................................................................................................................................92 6.2.1 General .................................................................................................................................................92 6.2.2 Pyrotechnical devices ...........................................................................................................................93 6.2.3 EMC ......................................................................................................................................................93

6.2.3.1 EMC Design Guidelines and Requirements.................................................................................93 6.2.3.2 EMC Specification (Emission, Susceptibility, Corona, ESD) .......................................................93 6.2.3.3 EMC Test Requirements ..............................................................................................................94

6.2.4 Power System.......................................................................................................................................94 6.2.5 On Board Data Handling.......................................................................................................................98

6.2.5.1 DHS Requirements ......................................................................................................................99 6.2.5.2 Data Processing Budget.............................................................................................................117

6.2.6 TTC Performances..............................................................................................................................118 6.2.6.1 General.......................................................................................................................................118 6.2.6.2 X-Band........................................................................................................................................118 6.2.6.3 UHF Band...................................................................................................................................120

6.3 Software .................................................................................................................................................121 6.3.1 General ...............................................................................................................................................121 6.3.2 Performance........................................................................................................................................123

6.4 Harness ..................................................................................................................................................124

6.5 GNC.........................................................................................................................................................124 6.5.1 General ...............................................................................................................................................124 6.5.2 GNC Design Requirements ................................................................................................................125 6.5.3 GNC Modes ........................................................................................................................................135

6.5.3.1 Stand-by Mode ...........................................................................................................................136 6.5.3.2 Spin-Up Mode ............................................................................................................................137 6.5.3.3 Nominal Sun Pointing Mode.......................................................................................................137 6.5.3.4 Nominal Earth Pointing Mode.....................................................................................................137 6.5.3.5 Inertial Pointing Mode.................................................................................................................138 6.5.3.6 Slew Mode..................................................................................................................................138 6.5.3.7 Δ-V Mode....................................................................................................................................138 6.5.3.8 GNC Safe mode .........................................................................................................................142 6.5.3.9 GNC Survival Mode....................................................................................................................142 6.5.3.10 CM-DM Separation Mode...........................................................................................................144

6.6 Propulsion..............................................................................................................................................146 6.6.1 Propulsion design guideline and rules ................................................................................................146 6.6.2 Propulsion System Requirements.......................................................................................................146

6.7 Structure.................................................................................................................................................150

6.8 Mechanisms and Pyrotechnics............................................................................................................151

6.9 Thermal Control.....................................................................................................................................151

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





7. INTERFACE REQUIREMENTS ..................................................................................................... 157

7.1 CM to DM Interface................................................................................................................................157

7.2 DM to RM Interface................................................................................................................................158

7.3 Communications (Ground Segment and TGO) Interface Requirements.........................................158 7.3.1 Ground Segment Interface Requirements ..........................................................................................158 7.3.2 TGO Interface Requirements..............................................................................................................158

7.4 Launcher Interface Requirements .......................................................................................................158

8. ENVIRONMENTAL REQUIREMENTS .......................................................................................... 160

8.1 General ...................................................................................................................................................160

8.2 Ground....................................................................................................................................................160 8.2.1 Mechanical ..........................................................................................................................................160 8.2.2 Thermal ...............................................................................................................................................160 8.2.3 Ambient ...............................................................................................................................................160

8.3 Launch....................................................................................................................................................161 8.3.1 Mechanical ..........................................................................................................................................161 8.3.2 Thermal ...............................................................................................................................................161 8.3.3 Ambient ...............................................................................................................................................161 8.3.4 EMC ....................................................................................................................................................161

8.4 Flight (Cruise) ........................................................................................................................................162 8.4.1 Mechanical ..........................................................................................................................................162 8.4.2 Thermal ...............................................................................................................................................162 8.4.3 Space ..................................................................................................................................................162

8.4.3.1 Radiation ....................................................................................................................................162 8.4.4 EMC ....................................................................................................................................................163

8.5 Mars Proximity and Separation............................................................................................................163 8.5.1 Mechanical ..........................................................................................................................................163 8.5.2 Thermal ...............................................................................................................................................163 8.5.3 Space ..................................................................................................................................................163 8.5.4 EMC ....................................................................................................................................................164

8.6 Entry, Descent and Landing (EDL) ......................................................................................................164 8.6.1 Mechanical ..........................................................................................................................................164 8.6.2 Thermal ...............................................................................................................................................164 8.6.3 Space ..................................................................................................................................................164 8.6.4 EMC ....................................................................................................................................................165

8.7 Mars Surface..........................................................................................................................................165 8.7.1 Mechanical ..........................................................................................................................................165 8.7.2 Thermal ...............................................................................................................................................165 8.7.3 Ambient ...............................................................................................................................................165 8.7.4 EMC ....................................................................................................................................................166

9. PLANETARY PROTECTION IMPLEMENTATION REQUIREMENTS.......................................... 167

10. CLEANLINESS AND CONTAMINATION REQUIREMENTS .................................................... 168

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





11. LOGISTIC REQUIREMENTS..................................................................................................... 169

12. AIV REQUIREMENTS................................................................................................................ 170

12.1 MGSE & FGSE Requirements ..............................................................................................................172

12.2 EGSE REQUIREMENTS ........................................................................................................................177 12.2.1 EGSE Connections.........................................................................................................................178

13. PRODUCT ASSURANCE AND SAFETY REQUIREMENTS .................................................... 179

14. CARRIER MODULE DETAILED REQUIREMENTS.................................................................. 180

15. DESCENT MODULE DETAILED REQUIREMENTS ................................................................. 181

16. ROVER MODULE DETAILED REQUIREMENTS...................................................................... 182

17. MSRD REQUIREMENTS NOT TRACED IN THIS SPECIFICATION ........................................ 183

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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 .....................................................................................................................145

LIST OF TABLES

Table 3-1 - 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 .......................................................................................................45

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





1. 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 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. o 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:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





o Rover Vehicle (RV) o 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)

o 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

Figure 1-1 ExoMars 2018 Mission Top Level Specification Tree

MSRD

Carrier Module Requirements Specification

Descent Module Requirements Specification

Rover Module Requirements Specification

Spacecraft Composite Requirements Specification

TASI Support Specifications

ESA Ancillary Requirements

Documents

Standards

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





1.2 Structure of the Document

The structure of the document is shortly summarized here below. Chapter 1 is the introductory chapter reporting the object of this specification Chapter 2 is the Normative and Informative Documents chapter Chapter 3 reports the Mission top level description, its relevant objectives and the System definition

suitable for technical requirements comprehension Chapter 4 reports the Mission requirements Chapter 5 reports SCC system requirements. Chapter 6 reports the SCC Design and Performance requirements Chapter 7 defines the interface between the SCC and EDM, Communications and Launcher

interfaces. Chapter 8 specifies the environment in which the SCC will operate in all its mission phases. Chapter 9 deals with Planetary Protection requirements. Chapter 10 deals with Cleanliness and Contamination requirements. Chapter 11 defines the Logistics rules to allow SCC (and its components) packing, handling and

transportation Chapter 12 specifies the Assembly, Integration and Verification requirements Chapter 13 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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





2. 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

2.1.1 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.

2.1.2 ESA Normative document

REFERENCES DOC. TITLE DOC. NUMBER [NR 03] ExoMars Management Requirements Document EXM-MS-RS-ESA-00012 [NR 015] ExoMars Document Requirements Description EXM-MS-RS-ESA-00010 [NR 017] ExoMars Risk Management Requirements EXM-MS-RS-ESA-00011 [NR 020] ExoMars Configuration Management Requirements EXM-MS-RS-ESA-00008 [NR 02] ExoMars Rover Requirements Document EXM-RM-RS-ESA-00001

[NR 021] ExoMars 2016 and 2018 Missions Environmental Specification Requirements

EXM-MS-RS-ESA-00013

[NR 18023] ExoMars 2018 Mission and System Requirements Document

EXM-M2-RSD-ESA-00003

[NR 18025] ExoMars 2018 Assembly, Integration and Verification Requirements

EXM-M2-RSD-ESA-00004

[NR 18004] ExoMars Reference Surface Mission EXM-PL-RS-ESA-00002 [NR 18028] RM RHU Information Package EXM-RM-IPA-ESA-00001 [NR 18026] ExoMars 2018 Product Assurance Requirements EXM-M2-RSD-ESA-00001 [NR 18024] ExoMars 2018 Planetary Protection Requirements EXM-M2-RSD-ESA-00002

[NR 18021] MOC/ERCO to ROCC Interface Requirements Document

EXM-GS-IRD-ESC-00003

[NR 180xx] Consolidated Report on Mission Analysis (CReMA) To Be Written

[NR 18016] ExoMars 2018 Operation Interface Requirements Document

EXM-G2-IRD-ESC-00002

[NR 18017] ExoMars 2018 Space to Ground Interface Requirements Document, Vol 1

EXM-G2-IRD-ESC-00001

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





2.1.3 A147Launcher Normative document

REFERENCES DOC. TITLE DOC. NUMBER

[NR 18027] ExoMars 2018 to Proton Launcher Interface Requirements Document, (until issuing of the Proton Launcher to ExoMars Interface Control Document)

EXM-M2-IRD-ESA-00001

[IR Axxx] Proton Launch System Mission Planner’s Guide Applicability Matrix (Applicable to EXM 2018)

To Be Written

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





2.1.4 Standards and Handbooks

2.1.4.1 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-00019 [IR 18015] Tailoring of ECSS-E-10-02A Verification, Issue 1 Rev.0, 26 June 2007:

EXM-MS-RS-ESA-00018 [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-00028 [ES 038] ECSS E-ST-33-11C Pyrotechnics – Mechanisms

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





REFERENCES DOC. NUMBER DOC. TITLE [ES 037] ECSS E-ST-35C

E-ST-35-01C E-ST-35-10C

Mechanical- Liquid and electric propulsion

[ES 059] ECSS-E-ST-35-06C Rev1 Cleanliness requirements for spacecraft propulsion components, subsystems and systems

[IR 18011] Tailoring of ECSS E40 Software Part 1B

EXM-MS-RS-ESA-00027

[IR 18012] Tailoring of ECSS E40 Software Part 2B

EXM-MS-RS-ESA-00029

[IR 18013] Tailoring of the ECSS E50 Part 1A Communications - Part 1

Principles and requirements for ExoMars EXM-MS-RS-ESA-00026

[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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





2.1.4.2 CCSDS

REFERENCES DOC. TITLE DOC. NUMBER [CS 01] TM Synchronization and Channel Coding CCSDS 131.0-B-1 [CS 02] TM Space Data Link Protocol CCSDS 132.0-B-1 [CS 03] Space Packet Protocol CCSDS 133.0-B-1 [CS 04] TC Synchronization and Channel Coding CCSDS 231.0-B-1 [CS 05] Technical Corrigendum 1 to CCSDS 231.0-B-1 CCSDS 231.0-B-1 Cor. 1 [CS 06] TC Space Data Link Protocol CCSDS 232.0-B-1 [CS 07] Proximity-1 Space Link Protocol - Data Link Layer CCSDS 211.0-B-4. [CS 08] Proximity-1 Space Link Protocol-Physical Layer CCSDS 211.1-B-3 [CS 09] Proximity-1 Space Link Protocol-Coding and

Synchronization Sub layer CCSDS 211.2-B-1.

[CS 10] Radio Frequency and Modulation Systems CCSDS 401.0-B-20 [CS 11] Recommendation 2.5.6B (DeltaDDOR) and

recommendation 2.4.17B (Suppressed carrier modulation)

CCSDS 401.0-B

[CS 12] Communications Operation Procedure-1. Blue Book CCSDS 232.1-B-1 [CS 13] Pseudo-Noise (PN) Ranging Systems CCSDS 414.1-B-1

2.1.4.3 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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





2.1.5 Thales Alenia Space Italia Normative Documents

REFERENCES DOC. TITLE DOC. NUMBER [NR 05000] ExoMars 2018 Spacecraft Composite

Requirements Specification EXM-M2-SYS-AI-0020

[NR 06000] ExoMars 2018 - Carrier Module Requirement Specification

EXM-C2-SYS-AI-0018

[NR 07000] ExoMars 2018 - Descent Module Requirements Specification

EXM-D2-SYS-AI-0019

[NR0400] Rover Module Requirements Specification EXM-RM-SYS-AI-0004 [NR 05002] ExoMars 2018 List of NR/IR Documents, Acronyms

and Abbreviations EXM-M2-LIS-AI-0059

[NR 05004] ExoMars 2018 S/C Electrical General Design I/F Requirements

EXM-M2-SSR-AI-0023

[NR 05005] ExoMars 2018 EMC and Power Quality Reqt.s EXM-M2-SSR-AI-0024 [NR 05006] ExoMars 2018 Thermal Environment and Test

Requirements Specification EXM-M2-SSR-AI-0025

[NR 05007] ExoMars 2018 Mechanical and Thermal Design and Interface Requirements

EXM-M2-SSR-AI-0026

[NR 05008] ExoMars 2018 Product Assurance Requirements for Subcontractors

EXM-M2-RQM-AI-0067

[NR 05009] ExoMars 2018 Spacecraft Design, Development and Verification Plan

EXM-M2-PLN-AI-0136

[NR 05010] EXOMARS 2018 Mechanical Environment and Test Requirements Specification

EXM-M2-SSR-AI-0027

[NR 05011] EXOMARS 2018 Planetary Protection Implementation Requirements

EXM-M2-SSR-AI-0031

[NR 05013] EXOMARS 2018 Flight and Mars Surface Space Environment Requirements Specification

EXM-M2-SSR-AI-0029

[NR 05014] ExOMARS 2018 Cleanliness & Contamination Requirements Specification

EXM-M2-SSR-AI-0030

[NR 05025] ExOMARS 2018 SCC Autonomy and Operational Requirements Specification

EXM-M2-SSR-AI-0032

[NR 05026] ExOMARS 2018 MGSE General Design Requirements Specification

EXM-M2-SSR-AI-0033

[NR 05027] ExOMARS 2018 EGSE General Design Requirements Specification

EXM-M2-SSR-AI-0034

[NR 05028] ExOMARS 2018 CCS Communication Protocol Specification

EXM-M2-SSR-AI-0035

[NR 05029] ExoMars 2018 SW Support Requirements Specification

EXM-M2-SSR-AI-0028

[NR 05015] EXOMARS 2018 Mission FEM Requirements for Structural Analysis

EXM-M2-VRP-AI-0066

[NR 05003] ExoMars 2018 Thermal Mathematical Model Requirements Specification

EXM-M2-RQM-AI-0064

[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-0157

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Note 1: Normative and Informative Documents directly relevant to Rover Module items are reported in §

2.2.2 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

2.2.1 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].

2.2.2 ESA/ROS/NASA Informative Documents

REFERENCES DOC. TITLE DOC. NUMBER [IR 18022] ExoMars Mission Analysis Guidelines (MAG) EXM-G2-TNO-ESC-00003

Issue 1 Rev. 0 [IR ESAxx2] Rover Module Science Payloads Refer to § 3.1.6 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-71874 [NR A55] Landers and Probes Communication System EXM-MS-TN-ESA-00006

2.2.3 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

Analysis Report EXM-MS-ARP-AI-0010

2.2.4 Other Informative Documents

Refer to § 3.2 of [NR 18023], to be used for reference only. REFERENCES DOC. TITLE DOC. NUMBER

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





3. 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 2022. 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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





3.2 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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





3.2.1 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 Removal of LV umbilical from launch pad

Separation of Spacecraft Composite from LV Upper Stage

LV lift-off, and injection into Mars transfer trajectory

Early Operation Separation of Spacecraft Composite from LV Upper Stage

Completion of LV injection correction maneuver

Spacecraft Composite Check-out

Completion of LV injection correction maneuver

Completion of Spacecraft Composite checkout

Sun acquisition and power generation. Telemetry acquired by Ground Control and stable pointing attitude.

Interplanetary Cruise

Completion of Spacecraft Composite checkout

Start of intensive orbit determination activities for targeting DM deployment

Navigation correction maneuvers

Mars Approach Start of intensive orbit determination activities for targeting DM deployment

Last TCM for B-plane targeting

Several TCMs

DM Separation Preparation and Execution

Last TCM for B-plane targeting

DM separation

CM final operations

DM separation Carrier enters Mars atmosphere and disintegrates.

Carrier passively enters Mars atmosphere and disintegrate.

DM Coast DM separation DM arrival at Entry Interface Point

DM Entry, Descent and Landing

DM arrival at Entry Interface Point

Landing (EDL essential telemetry received by the TGO)

Detailed EDL sequence.

Rover egress Landing Rover outside the Landing Platform

Commissioning of Rover elements needed for egress

Landing Platform Commissioning

Landing End of Landing Platform Commissioning

Lander Science Operational Phase

End of Landing Platform Commissioning

End of SP operational life on Mars surface

Rover Science commissioning

Rover egress completed End of Rover Science commissioning

Rover Science Operational Phase

End of Rover Commissioning

End of RM operational life on Mars surface

Table 3-1 - ExoMars 2018 Mission Phases

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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.

3.2.2 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] § 4.1 ÷ 4.3 report the details of the nominal mission, while § 5.1 ÷ 5.3 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 The Carrier Module (CM) which carries the whole system close to Mars atmospheric borders. o 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)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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 3-2.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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.

3.4.1 Rover Module Science Payload

The description and related requirements for the RM Science Payloads are provided in [ESAxx2].

3.4.2 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).

Roscosmos RNS

ESA ESTRACK DSN

Trace Gas Orbiter (TGO)

2018 Mission

Spacecraft Composite (Carrier Module + Descent Module + Rover Module)

ROCC (incl SOC- Altec)

Proton M /

Breeze MMOCC @ ESOC, DarmstadtSpacecraft Operations

Rover and Landing Platform

Archiving (ESAC)Archiving (ROS)

NASA DSN N/AAvailable for “extreme contingencies” during Cruise

Lander Op. Center (ROS)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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:

RCS Thrusters and Tanks

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





4. 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. Parents: MoV: [SCC: RoD] ## #[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 2000. 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. Parents: MoV: [SCC: RoD] ## #[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 32.184 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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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. Parents: MoV: [SCC: RoD] ## #[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. Parents: MoV: [SCC: RoD] ##

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. Parents: MSRD MI-10, MSRD SC-SY-330 MoV: [SCC: RoD] ## #[SCC- 0060 The mission design shall be compatible with a Proton-M/Breeze M launch from Baikonur in April/May 2018. Parents: MSRD MI-10 MoV: [SCC: RoD] ## #[SCC- 0070] The SCC shall be designed to allow achieving of the Technology and Science objectives defined in § 3.1 of this Specification. Parents: MSRD MI-210 MoV: [SCC: A, RoD] ## #[SCC- 0080] The SCC shall be designed to support the implementation of the SCC mission phases reported in Table 3-1.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: A, RoD] ## #[SCC- 0090] The SCC shall be designed to comply with the Mission Timeline addressed in § 3.2.2 of this Specification. Parents: MoV: [SCC: RoD] ## #[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 Parents: MoV: [SCC: A, RoD] ## #[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 15th January 2019 as specified in [IR 18022] § 4.1. Parents: 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. Parents: 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- 0120 and with an altitude of no more than – (minus) 2 Km (TBC) above the Mars MOLA zero level.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD MI-80 MoV: [SCC: RoD] ## #[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 3.377 km/s and 3.474 km/s and arrival at an Ls of 324 degrees.

Parents: MSRD MI-50 MoV: [SCC: A, RoD] ## #[SCC- 0150] The baseline mission design shall allow landing of the DMC after the Global Dust Storm Season, at Solar Longitude 324 degrees (TBC). Parents: 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 Parents: 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 Parents: MSRD MI-110 MoV: [SCC: NTBV] ## #[SCC- 0160]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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 2.684 km/s and 3.510 km/s and arrival at an Ls of 34 degrees.

Parents: MSRD MI-40, MSRD-CM-SY-90, MSRD DM-SY-170 MoV: [SCC: A, RoD] ## #[SCC- 0170] The mission design shall enable a landing accuracy, defined as the downrange semi-major and semi-minor 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].

Parents: 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. Parents: 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

Parents: MSRD MI-150, MSRD SC-SY-50 MoV: [SCC: A] ## #[SCC- 0200]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The mission shall be compatible with a DMC Coast phase of up to 30 minutes (TBC). Parents: MSRD MI-160 MoV: [SCC: A, RoD] ## #[SCC- 0210] During all mission “not critical” phases, the Spacecraft Composite design shall allow for check-out of all its Modules and Science Payload. Parents: MSRD SC-SY-370, MSRD SC-SY-420 MoV: [SCC: RoD] ## #[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

Parents: MSRD SC-SY-390 MoV: [SCC: RoD] ##

4.3 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 7th May 2018 and closes on 27th May 2018. Parents: MSRD-MI-10, MSRD-MI-20, MSRD SC-SYS-340 MoV: [SCC: RoD] ## #[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 15th January 2019.

Parents: MSRD-30, MSRD-20 MoV: [SCC: A, RoD]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





## #[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. Parents: MSRD MI-10, MSRD MI-20 MoV: [SCC: RoD] ## #[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.

Parents: MSRD-10, MSRD-20 MoV: [SCC: RoD] ## #[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). Parents: MSRD SC-SYS-350 MoV: [SCC: RoD] ## #[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]). Parents: MSRD SC-SYS-360 MoV: [SCC: RoD] ## #[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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: This means that the launchable mass corresponds to the SCC mass after separation from

the last stage of the missile. Parents: MoV: [SCC: RoD] ## #[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 Value SCC Attitude -X-SC axis pointed to Sun ± 5 º (TBC) SCC angular Rate (right-hand about SCC axes)

6 º/s ± 1 º/s around X-SC axis (TBC) 0 º/s ± 1,1 º/s around Y-SC and Z-SC axes (TBC)

SCC- to-LV relative separation velocity > 0.35 m/s (TBC)

Table 4-1 SC Composite dynamic conditions at separation from the launcher Parents: MoV: [SCC: A] ## #[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]. Parents: MoV: [SCC: A, RoD] ## #[SCC- 0320] The SCC and its elements shall be compatible with a Launch timeline (for power up on Launch PAD, Lift-off, Ascent and Parking Orbit) relaying on its internal battery supplied power for TBD hours. Parents: 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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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. Parents: MSRD-10, MSRD-20 MoV: [SCC: RoD] ## #[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σ). Parents: MSRD MI-30 MoV: [SCC: RoD] ## #[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. Parents: MSRD SY-400 MoV: [SCC: RoD] ## #[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. Parents: MSRD SY-410 MoV: [SCC: RoD] ##

4.5 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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD MI-30 MoV: [SCC: RoD] ##

4.6 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. Parents: MSRD MI-70, MSRD DM-SY-20 MoV: [SCC: A, RoD] ## #[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. Parents: MSRD MI-160, MSRD DM-SY-50 MoV: [SCC: A, RoD] ## #[SCC- 0410] The DMC shall be designed to command the CM-DMC separation from the ESA-OBC1 Parents: DM-SYS-40 MoV: [SCC: RoD] ## #[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 = 119° ÷ 127° +Xvv-EAA = 150° ÷ 167° Parents: MoV: [SCC: A] ## #[SCC- 0430] Following separation from the CM, the DMC mission shall be decomposed into the following phases:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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. Parents: MSRD MI-70, MSRD DM-SY-20, MSRD DM-SY-30 MoV: [SCC: RoD] ## #[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. Parents: MSRD DM-SY-80, MSRD DM-SY-90 MoV: [SCC: A, RoD] ## #[SCC- 0450] The entry sequence initiation shall rely on at least on 2 independent measurement chains (i.e. IMU measurements and predefined timer) Parents: MSRD DM-SYS-100 MoV: [SCC: A, RoD] ## #[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. Parents: MoV: [SCC: A, RoD] ## #[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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD DM-SYS-110 MoV: [SCC: A] ## #[SCC- 0480] The CM-DMC separation shall induce a transversal velocity (in the YS-ZS plane) on the DMC not greater than 10-2 m/s (3-sigma) (TBC). Parents: MSRD DM-SYS-110 MoV: [SCC: A] ## #[SCC- 0490] The uncertainty of the DMC linear separation rate shall be better than 0.015 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.

Parents: MSRD DM-SYS-110 MoV: [SCC: A] ## #[SCC- 0500] The SCC shall release the DMC with a minimum spin rate around the XDM axis of 2.5 rpm. Parents: 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. Parents: MoV: [SCC: RoD] ## #[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 Parents: MSRD-DM-SY-160

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





MoV: [SCC: RoD] ## #[SCC- 0520] The landing and Landing Platform stabilization events shall be detected by the OBC 1. Parents: MoV: [SCC: RoD] ## #[SCC- 0530] Once the Landing Platform has been recognized as stable, the OBC 1 shall command the opening of the LP Landing Gears. Parents: MoV: [SCC: RoD] ## #[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. Parents: MoV: [SCC: RoD] ## #[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). Parents: MoV: [SCC: RoD] ## #[SCC- 0560] After TBD <time> from the touch down, the control of the LP shall be passed to the OBC 2 for LP check-out. 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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: RoD] ## #[SCC- 0570] After TBD <time> after the completion of RM checkout, Ground will command the RM egress from the LP. Parents: MoV: [SCC: RoD] ## #[SCC- 0580] Once on the Mars Surface, the RM shall start its mission lasting 218 sol. Parents: MoV: [SCC: RoD] ## #[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. Parents: MSRD DM-SY-140 MoV: [SCC: RoD] ##

4.7 General Flight Parameters

4.7.1 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 4-2.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Figure 4-1 Angles Evolution for ExoMars 2018 Nominal Mission, LPO

Figure 4-2 Angles Evolution for ExoMars 2018 Nominal Mission, LPC

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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.

Parents: MSRD MI-30, MSRD MI-40 MoV: [SCC: A, RoD] ## #[SCC- 0610] The SC Composite and its elements design shall be compatible with distances to the Sun ranging from 1 to 1.62 AU. Parents: MSRD MI-30, MSRD MI-40 MoV: [SCC: A, RoD] ## #[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

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD MI-30, MSRD MI-40 MoV: [SCC: A, RoD] ##

4.7.2 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. Parents: MSRD MI-30, MSRD MI-40 MoV: [SCC: A, RoD] ## #[SCC- 0640] Eclipse entry, when applicable, shall be automatically detected onboard and managed so as not to interrupt nominal operations. Parents: MoV: [SCC: RoD] ##

4.7.3 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 4-2.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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°.

SU N

EA R TH

M A RS = S pacecraft

S un -Earth -M ars ˜ 0

Su n-M ars-Earth ˜ 0

Figure 4-4 SEM and SME alignment (Conjunction)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD MI-30, MSRD MI-40 MoV: [SCC: A, RoD] ##

4.8 SCC Lifetime

4.8.1 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). Parents: MoV: [SCC: A, RoD] ##

4.8.2 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

Parents: MSRD-SC-SY-440, MSRD-CM-40, MSRD-DM-SY-140 MoV: [SCC: A, RoD] ##

4.8.3 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 un-

fueled state. This requirement does not apply to Batteries design and procurement.

Parents: MSRD-SY-430 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5. SCC SYSTEM REQUIREMENTS

5.1 Mass Properties

5.1.1 Mass Budget Control

#[SCC- 0690] The SCC Mass budget shall be maintained, documented and controlled following the rules specified in [NR 05007] § 4.11.10. Parents: MSRD SYS-60, MSRD SYS-70, MSRD SYS-90, MSRD SYS-100, MSRD SYS-110 MoV: [SCC: RoD] ## #[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

Parents: MSRD SYS-120 MoV: [SCC: RoD] ## #[SCC- 0710] The DMC propellant mass shall be calculated based on its dry mass (Mdmo of the DMC). Parents: MSRD SYS-130 MoV: [SCC: RoD] ## #[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). Parents: MSRD SYS-140 MoV: [SCC: RoD] ## #[SCC- 0730]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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. Parents: MSRD SYS-150 MoV: [SCC: RoD] ## #[SCC- 0740] The Carrier Module propellant mass shall be calculated based on the Spacecraft Composite dry mass (Mdmo of the SC Composite). Parents: MSRD SYS-160 MoV: [SCC: RoD] ## #[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. Parents: MSRD SYS-170 MoV: [SCC: RoD] ## #[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. Parents: MSRD SYS-180 MoV: [SCC: RoD] ##

5.1.2 Mass Margin Policy

#[SCC- 0770] The SCC Mass maturity and System Margins shall be established in accordance with the rules specified in [NR 0101] § 4.11.10. Comment: this applies to any of the SCC element, including CFI. Parents: MSRD SYS-70, MSRD SYS-110 MoV: [SCC: RoD] ## #[SCC- 0780] Deleted

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





##

5.1.3 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] §

4.11.10 Comment 2: The SCC Modules will include allocation for balancing masses to meet requirements

specified in § 5.1.4. Parents: 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. Parents: 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: 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- 810. DMC: 2000 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

Parents: 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.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-SY-200 MoV: [SCC: A, RoD] ## #[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. Parents: MSRD SC-SY-190, MSRD-CM-SY-25 MoV: [SCC: A, RoD] ## #[SCC- 820] A 5% (TBC) margin shall be applied to compute the DMC propellant mass for braking and attitude control maneuvers. Parents: MSRD DM-SY-130 MoV: [SCC: A, RoD] ##

5.1.4 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

Parents: MoV: [SCC: A] ## #[SCC- 840] The SCC CoG shall be nominally located on the XSC axis. The maximum displacement between the SCC CoG and the XSC 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.

Parents: MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[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*m2

Parents: MoV: [SCC: A, RoD] ## #[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. Parents: MoV: [SCC: A, RoD] ## #[SCC- 870] Deleted ##

5.2 Reference Coordinates

5.2.1 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. Parents: MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.2.2 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

Parents: MoV: [SCC: RoD] ##

5.2.3 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.


5.2.4 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:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





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 +22.5˚ (counterclockwise rotation around +XSEP axis)

Parents: MoV: [SCC: RoD] ## Figure 5-1shows the different SCC Reference Coordinates Systems

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Figure 5-1 SCC, CM, DM AND CM-DM Separation Adapter Reference Coordinates

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.2.5 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 252.5 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 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.2.6 Reference Coordinates relationship summary

The relationship between the Reference Coordinates System defined for the ExoMars 2018 Mission are summarized as follows:

X-SC // X-CM // X-DM // (-)Z-RB Y-SC // Y-CM // Y-DM // Y-RB Z-SC // Z-CM // Z-DM // X-RB

5.3 Communications

5.3.1 General

#[SCC- 0910] The SCC shall implement the following communication links: SCC- Ground up and downlink from launch until CM-DM separation (X-Band, MGA and LGA

antennae) DM-ExoMars 2016 TGO downlink during Coasting, Entry Descent and Landing (UHF-Band - LGA

Tx antenna) DM-NASA Relay Orbiter(s) that implement the same I/F of the TGO (applicable for contingency

case only) DM Landing Platform - ExoMars 2016 TGO forward and return link (UHF-Band, LGA Rx/Tx

antenna) Rovers - ExoMars 2016 TGO forward and return link from Rovers arrival on Mars until end of

Rovers mission (UHF-Band, LGA Rx/Tx antenna)

Comment 1: the SCC communication system will be used to support Data Relay functions for ESA/NASA future mission (i.e. post 2018).

Comment 2: in UHF Band, the forward link is the link between Orbiter and Mars asset (DM or Rovers) and viceversa for the return link according to the TGO Mars Relay User's Guide [IR 1154].

Comment 3: UHF communication capability with NASA Orbiters shall be verified in the frame of 2016 mission

Parents: MSRD MI-100, MSRD MI-130, MSRD MI-180, MSRD MI-190, MSRD MI-200, MSRD CO-12, MSRD CO-20, MSRD CO-30, SGIRD-FRQ-1 MoV: [SCC: T, RoD] [S/S: T] ## #[SCC- 0920] During all mission phases the Spacecraft Composite and its elements shall support at each applicable Ground Control or TGO contact the maximum data rate necessary to downlink the data generated onboard and the data recorded.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD-CO-80 MoV: [SCC: RoD] ## #[SCC- 0930 The frequency bands for the TT&C exploited for uplink and downlink shall be adequately separated from the frequencies assigned to any other RF system, which may be used, during the active lifetime of ExoMars 2018 and selected from the bands allocated to Cat B. Space Research missions. Comment: In order to additionally safeguard against potentially harmful interference:

separation of assigned frequencies should exceed the criteria applicable to the process of international frequency coordination, and/or relevant transponder performance parameters should be superior to those assumed for international frequency coordination

Parents: MSRD-CO-110, SGIRD-FRQ-2 MoV: [SCC: A, RoD] ## #[SCC- 0935] At any one time, the direct Ground to SCC TC links shall be supported by one uplink frequency only. Parents: SGIRD-RX-3 MoV: [SCC: A, RoD] ##

5.3.2 X-Band Communication

#[SCC- 0940] The SCC Telecommunication System shall comply with [NR 18017] following the mission constraints defined in § 4 of this Specification. Parents: MSRD-CO-11 MoV: [SCC: RoD] ## #[SCC- 0950] The SCC communication system shall be compatible with the ESTRACK Network, NASA DSN and Russian stations as specified in [NR 18017] in particular Chapter 2 applies for RF Link requirements while allowing for the implementation of turbo codes. Comment: The Ground Segment applicable characteristics and performance are reported in [NR 18017].

This applies to NASA DSN and Russian Stations too.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD-CO-11, SGIRD-GS-1 MoV: [SCC: A, RoD] [S/S: T] ## #[SCC- 0955] The Protocol Requirements and Packet definitions requirements are specified in[NR 18017] Chapter 3, § 3.1 ÷ 3.5. and [ES 137]. Parents: SGIRD-PRO-1, SGIRD-PRO-2, SGIRD-PRO-3, SGIRD-PKT-1, SGIRD-PKT-2, SGIRD-PKT-3, SGIRD-COM-1. MoV: [SCC: A, RoD] [S/S: T] ## #[SCC- 0960] The SCC X-Band TT&C shall be designed in compliance with [ES 048] to [ES 051], [CS 01] to [CS 10], and [NR 18017]. Parents: MSRD-SC-CO-10 MoV: [SCC: A, RoD] ## #[SCC- 0970] Individual X-band RF frequencies shall be assigned to the ExoMars 2018 SCC that may be active simultaneously. In particular, The SCC uplink and downlink frequencies shall be the ones specified in [NR 18017] § 2.2. Comment1: in this way it is ensured that the frequencies exploited for up-links and down-links shall be

adequately separated from the frequencies assigned to any other RF system, which may be used, during the active lifetime of ExoMars, in support of communications between Earth and any other element on the surface of and/or in an orbit about Mars.

Comment2: The Orbiter shall operate nominally even the frequencies assigned to the ExoMars Spacecraft are active simultaneously.

Comment3: The UHF Proximity Systems are excluded from this requirement. Parents: MSRD-CO-110, SGIRD-FRQ-3 MoV: [SCC: A, RoD] ## #[SCC- 0980] The SCC shall be compatible with the ESA DSN and Russian RNS (Bear’s Lakes) for TM, TC, Ranging and Doppler, and Delta-DOR. The compatibility requirements are in [NR 18017] § 2.1. Parents: MSRD-SC-CO-120 MoV: [SCC: RoD] [S/S: T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 0990] The SCC shall be compatible with the Russian RNS (Bear’s Lakes) and ESTRACK G/S for the use of Delta-DOR and Regenerative Ranging measurements. The compatibility requirements are in [NR 18017] § 2. Parents: MSRD-SC-CO-120, SGIRD-GS-4, SGIRD-GS-5, CHF-4.1 MoV: [SCC: RoD] [S/S: T] ## #[SCC- 1000] The SCC shall be compatible with the ESA Deep Space Antenna Station Network, and LEOP Station Network for the LEOP phase (i.e. for the first 2 days after separation from the launcher). Characteristic of these GS are [NR 18017] § 2. Parents: MSRD-SC-CO-11, SGIRD-GS-2 MoV: [SCC: RoD] ## #[SCC- 1010] Nominal and back-up Post-LEOP communications (from Commissioning up to DM release), shall be through the 35m ESTRACK Network (New Norcia, Cebreros and Malargue). Compatibility with the TNA-1500 Russian Ground Station at Bear’s Lakes for TM, TC, Ranging and Doppler support is mandatory. Comment1: ESTRACK Network performance is reported in [NR 18017]. Comment2: Russian RNS Network performance are reported in TBD but supposed fully compatible with

ESA DNS I/F. Parents: MSRD-SC-CO-11, SGIRD-GS-3, SGIRD-GS-4, SGIRD-GS-5 MoV: [SCC: RoD] ## #[SCC- 1015] Prior to RM egress, the antenna of Russian Ground station shall support SCC Safe mode(s) and agreed contingencies. After the RM egress, the antenna of Russian Ground station shall be used on a regular basis. Parents: MoV: [SCC: A, RoD] ## #[SCC- 1020] The NASA DSN 70 m shall be considered for ultimate safe mode recovery and emergency support only.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: Emergency support covers the provision of station coverage upon declaration of spacecraft emergency.

Parents: MoV: [SCC: A, RoD] ## #[SCC- 1030] The Spacecraft Composite shall be capable to communicate with Ground Control at any time apart from Earth occultation or when the Sun-Earth-Spacecraft angle is less than 3 deg. Comment: The SES < 3° corresponds to an-Earth-SC-Sun alignment known as Superior Conjunction.

The TBC will be removed after that a detailed up-link budget has demonstrated the performance reduction as function of the Earth/Spacecraft/ Sun angle.

Parents: MSRD-SY-380 MoV: [SCC: A, RoD] ## #[SCC- 1040]

In nominal conditions during all mission phases, the Spacecraft Composite shall support simultaneous telemetry, ranging and telecommands up to the maximum distance from the Earth (1.9 AU) and in nominal attitude, as per [NR 18017]. Comment 1: Exceptions over transient periods (e.g. during a delta-V maneuvers, CM-DMC separation

sequence) shall be justified individually and agreed with the Prime. Comment 2: Exceptions for simultaneous ranging during nominal suppress carrier operations shall be

justified individually and agreed between TASI and ESA . Parents: MSRD SC-CO-170, MSRD SC-CO-50 MoV: [SCC: RoD] ## #[SCC- 1050] Deleted Parents: MoV: ## #[SCC- 1060] The ranging signal shall be compatible with [ES 050]. Comment: The ranging, Doppler and Delta DOR performance shall ensure the accuracy requirements

for Orbit Determination. It can be assumed that 1/3 of the error budget is allocated to the GS, 1/3 to the SCC and 1/3 to the propagation elements (apportionment TBC).

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





1-σ Range random error for 2-way range 2m 1-σ Range considered bias for 2-way range 10 m 1-σ 2-way Doppler random error (over 60 seconds) 0.1 mm/s 1-σ Doppler considered bias none 1-σ Delta-DOR random error 5 cm

Parents: MSRD SC-CO-120, SGIRD-CHF-4.1 MoV: [SCC: RoD] ## #[SCC- 1070] The spacecraft shall be able to implement Delta-DOR capability using dedicated DOR tones and shall support Delta-DOR measurements according to [CS 10] and [CS 11]. Parents: MSRD SC-CO-120, SGIRD-GS-6, SGIRD-CHF-4.2, SGIRD-DOR-1 MoV: [SCC: RoD] ## #[SCC- 1080] The SCC shall be able to provide ranging and/or Delta DOR signals for up to:

TBD Comment: The above duration figures are indicative for TM/TC link computations Parents: MoV: [SCC: A, T] ## #[SCC- 1090] During LEOP the SCC shall be able to operate assuming a daily contact of 24 hrs/day with Ground Control. Parents: , SGIRD-GS-9 MoV: [SCC: A, RoD] ## #[SCC- 1100] During Near Earth commissioning the SCC shall be able to operate assuming a daily contact of 8 hrs/day with Ground. Comment: Estimated Phase duration around 4 weeks.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: SGIRD-GS-10 MoV: [SCC: A, RoD] ## #[SCC- 1110] For nominal operations during Cruise (from end of LEOP until DM release preparation), the SCC shall be able to operate assuming daily Ground Control contact of 4 hours each for non-critical operations. Parents: SGIRD-GS-11 MoV: [SCC: A, RoD] ## #[SCC- 1120] The SCC shall be able to continue nominal operations without ground intervention for at least the period between TBD Ground contacts, also in case of recoverable single failure. Comment 1: The requirement means that TBD consecutive ground contacts may be lost with no impacts

on nominal SCC operations. Comment 2: ‘Ground contact’ is intended as the Mars view-period booked on a single ground station.

Split passes on one ground station due to e.g. Mars occultations do not count as individual contact periods.

Comment 3: Loss of the ground contacts for critical operations is not allowed: daily contacts must be guaranteed.

Parents: MoV: [SCC: A, RoD] ## #[SCC- 1130] The SCC shall perform all nominal operations in all phases of the mission under the Ground stations visibility constraints specified in [NR 180xx] and [NR18017]. Parents: MoV: [SCC: A, RoD] ## #[SCC- 1140] The SCC shall ensure data transmission during all phases of the mission for the range-rate and range-rate profiles specified in [NR18017]. Parents: MSRD SC-CO-40 MoV: [SCC: A, RoD] ## #[SCC- 1150] During all mission phases and all spacecraft attitudes, the SCC shall ensure:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





transmission of essential spacecraft telemetry from/to Ground Control. reduced commandability, when in Fail Safe conditions and pending availability of Russian RNS

Comment1 : The content and data volume of the essential telemetry is to be defined by the Prime

Contractor and agreed with the Agency. Comment2: Solar effects shall be taken into account for this requirement. Parents: MSRD SC-CO-70 MoV: [SCC: A, RoD] ## #[SCC- 1160] During Mars Arrival and its preparation (including DM separation), the SCC shall be able to operate assuming daily contact of 8 hrs/day with Ground. For the last week the contact duration is 20 hours/day to allow transmission specific spacecraft statuses, coarse telemetry of critical performance parameters, as well as information regarding clear completion of major events (e.g. “separation ready”) . Comment 1: DM separation preparation and execution phase starts TBD days before actual DM

release and covers the period between the start of the slew maneuver to get the SCC into separation attitude, DM Release and the completion of the subsequent collision avoidance maneuver (TBC if necessary).

Comment 2: The preparation period is estimated to be about TBD weeks during which also DDOR measurement will be performed.

Parents: SGIRD-GS-13 MoV: [SCC: A, RoD] ## #[SCC- 1170] From initiation of CM-DMC separation sequence until actual separation, a coherent downlink signal (or 2-way Doppler tracking) of the Spacecraft Composite shall be ensured. Parents: MSRD SC-CO-75 MoV: [SCC: A, RoD] ## #[SCC- 1171] TMO-2 It shall be possible to set the Carrier Module transponder to coherent or non-coherent mode. This shall be done by telecommand. Parents: SGIRD-TMO-2 MoV: [SCC: T, RoD] ## #[SCC- 1172]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





When set to coherent mode, the Carrier Module transmitter shall operate coherent to the receiver as soon as the receiver is locked. If the receiver loses lock, the transmitter shall go to non-coherent state and return to coherent state as soon as the receiver is in lock again. Parents: SGIRD-TMO-3 MoV: [SCC: T, RoD] ## #[SCC- 1173] When set to non-coherent mode, the Carrier Module transmitter shall stay non-coherent, irrespective of the receiver’s lock status. Parents: SGIRD-TMO-4 MoV: [SCC: T, RoD] ## #[SCC- 1175] From initiation of CM-DM separation sequence until actual separation, observability of the Spacecraft Composite shall be ensured, e.g. specific spacecraft statuses, coarse telemetry of critical performance parameters, as well as information regarding clear completion of major events (e.g. separation) shall be transmitted back to TGO (pending TGO availability). Parents: MSRD SC-CO-71 MoV: [SCC: A, RoD] ## #[SCC- 1180] In the cases when all data generated on board cannot be transmitted (e.g. during a delta-V maneuvers, CM-DM separation sequence, Conjunctions), the Spacecraft Composite shall be able to transmit recorded data based on priority defined by Ground Control. Comment: These cases shall be defined, justified individually and agreed with the Agency. Parents: MSRD SC-CO-81 MoV: [SCC: A, RoD] ## #[SCC- 1190] The TT&C communication links shall be capable of operating within specifications during all expected Doppler shift and Doppler rate conditions experienced during the different mission phases as specified in [NR 18017]. Parents: MSRD SC-CO-90 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1200] Quasi omni-directional coverage shall be ensured by the Spacecraft Composite Low Gain Antennas at minimum bit rates, for all nominal phases (including safe mode) except during maneuvers. During maneuvers the coverage shall be optimized in order to minimize the duration of any communications black-out Parents: MSRD SC-CO-130 MoV: [SCC: A, RoD] ## #[SCC- 1210] During SCC maneuver, (ΔV, attitude slews…) SCC data shall be recorded On Board and downlinked to Ground when the pointing to Ground is restored. Parents: MSRD SC-CO-81 MoV: [SCC: A, RoD] ## #[SCC- 1220] For the Earth uplink, the maximum telecommand bit error rate (BER) shall be less than 10-5 at the input to the telecommand decoder. Parents: MSRD SC-CO-140, SGIRD-DR-5 MoV: [SCC: A, RoD] ## #[SCC- 1230] The probability of frame loss for Spacecraft composite telemetry (FER) shall be less than 10-5. Parents: MSRD SC-CO-150, SGIRD-DR-5 MoV: [SCC: A, RoD] ## #[SCC- 1240] The TT&C subsystem shall be compliant with the requirement of RF emissions imposed by the launcher, as specified in [18027]. Parents: MSRD SC-CO-160, SC-EL-40 MoV: [SCC: A, RoD] ## #[SCC- 1250] In nominal conditions during all mission phases, the Spacecraft Composite shall support the following modes for the uplink:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Carrier only Ranging only (up to CM-DMC separation Telecommand Ranging and telecommand simultaneously.

Comment 1: Exceptions over transient periods (e.g. during a delta-V maneuvers, CM-DMC separation

sequence) shall be justified individually and agreed with the Agency. Comment 2: For GMSK modulation, ranging is not required. Parents: MSRD SC-CO-180, SGIRD-CHF-4 MoV: [SCC: A, RoD] ## #[SCC- 1260] In nominal conditions during all the mission phases, the SCC shall support the following downlink modes, selectable by telecommand:

Carrier only Ranging only (up to DMC Separation only) Telemetry Ranging and telemetry simultaneously

Comment: Exceptions over transient periods (e.g. during a delta-V maneuvers, CM-DMC separation

sequence) shall be justified individually and agreed with the Agency. Parents: MSRD SC-CO-190 MoV: [SCC: T] ## #[SCC- 1270] The mission shall be designed to guarantee a Spacecraft Composite housekeeping data return of 50 Mb/day (TBC) during all mission phases, worst case. Parents: MSRD SC-MI-200 MoV: [SCC: A, RoD] ## #[SCC- 1280] During all mission phases, the Spacecraft Composite shall support reception of commands from Ground Control at a minimum data rate of 2000 bps (TBC) using an Estrack Deep Space Station. Comment: Exceptions over transient periods (e.g. during a delta-V maneuvers, CM-DMC separation

sequence) shall be justified individually and agreed with the Prime Parents: MSRD SC-CO-60 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1290] The Telecommand format shall be compliant with the Packet Telecommand Standards [ES 133], [ES 134] and [CS 03]. Parents: SGIRD-CHF-1 MoV: [SCC: A, RoD, T] ## #[SCC- 1300] The Uplink and Downlink modulation, including modulation modes, shall be compliant with the [ES 050], [ES 051], [CS 10] and [CS 11] standard. Parents: SGIRD-MOD-1, SGIRD-MOD-4, SGIRD-TMM-1 Parents: MoV: [SCC: A, RoD, T] ## #[SCC- 1310] The Managed Parameters, as listed in the standards, shall be defined in the [NR 18017] in consultation with ESOC. These relate but are not limited to the following: Authentication use Randomization of the transfer frame Error detecting and/or correcting mode PLOP used CLTU maximum length Segmentation or non-segmentation COP protocol used

Parents: SGIRD-CHF-1.1 MoV: [SCC: A, RoD, T] ## #[SCC- 1320] The Telemetry format shall be compliant with the CCSDS Packet Telemetry standards, [ES 135], [CS 02] and [CS 03]. Parents: SGIRD-CHF-2 MoV: [SCC: A, RoD, T] ## #[SCC- 1321] It shall be possible on the Carrier Module to radiate the signal generated via any one antenna at a time.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: SGIRD-DL-2 MoV: [SCC: A, RoD, T] ##

5.3.3 UHF Communication

#[SCC- 1325] During the EDL event, the DMC shall be able to transmit “alive signal” to Ground (TBC). Comment 1: Requirement not committed yet and pending the verification of the requirement #[SCC- 0156. Comment 2: Only the UHF Carrier Signal should be received by Ground (no Data). Parents: MSRD MI-110 MoV: [SCC: A] ## #[SCC- 1330] The DMC shall provide adequate communication capability such that when in visibility with the TGO or with the NRO(s) (TBC) a broadcast communication link can be established in UHF band in order to transmit telemetry. Comment 1: The capability to receive on Earth the above required UHF band telemetry shall be

computed by th Ground Station. Comment 2: The possible communications black-out phenomena, due to both Mars natural and induced

plasma during the EDL phase, shall be assessed but the impact induced by their occurrence does not need to be mitigated by design.

Parents: MSRD DM-CO-10 MoV: [SCC: A] ## #[SCC- 1340] The DMC communication interface design with the ExoMars TGO shall conform to the “ExoMars TGO Data Relay User Manual [IR 1154]. Parents: MSRD SC-CO-30 MoV: [SCC: A, RoD] ## #[SCC- 1350] The DMC shall be capable to receive and implement updated operational timeline during the Cruise Phase. Parents: MSRD DM-CO-40 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1360] Deleted MoV: Parents: ## #[SCC- 1370] The DMC shall be capable to transmit to the TGO essential telemetry immediately after its separation from the Carrier Module (pending TGO visibility during EDL) Parents: MSRD DM-CO-50 MoV: [SCC: A, RoD] ## #[SCC- 1380] The DMC shall be capable to transmit to the TGO essential telemetry of the Coast phase before the initiation of the Entry Phase (pending TGO visibility during EDL). Parents: MSRD DM-CO-60 MoV: [SCC: A, RoD] ## #[SCC- 1390] The DMC shall be capable to transmit to the TGO essential telemetry of the Entry phase before the initiation of the Descent Phase (pending TGO visibility during EDL). Parents: MSRD DM-CO-70 MoV: [SCC: A, RoD] ## #[SCC- 1400] The DMC shall be capable to transmit to the TGO essential telemetry of the Descent phase before the initiation of the Landing Phase (pending TGO visibility during EDL). Parents: MSRD DM-CO-80 MoV: [SCC: A, RoD] ## #[SCC- 1410] The DMC shall be capable to transmit to the TGO essential telemetry of the Landing phase before the initiation of the Surface Phase (pending TGO visibility after landing). Parents: MSRD DM-CO-90 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1420] For SCC 1110 to -1150, “essential telemetry” shall include at least basic system status and health, and shall allow for post-flight analysis/diagnosis at any point in the Coast abd EDL phases.. Comment: The content and data volume of the essential telemetry is to be defined by the Prime

Contractor and agreed with the Agency. Parents: MSRD DM-CO-100, MSRD MI-100 MoV: [SCC: A, RoD] ## #[SCC- 1430] The mission shall be designed to allow real time transmission to, and reception by, the TGO of the essential telemetry transmitted at 8 kbps by the DMC during the Coast and EDL phases (TBC). Comment 1: The sequence of transmission of the DMC essential telemetry from separation until

landing is specified in SCC 1370 through SCC 1410. Comment 2: During the EDL phase the data transmission from the EDL to the TGO, if confirmed as

applicable requirement, will be in "open loop recording mode". Parents: MSRD MI-100 MoV: [SCC: A, RoD] ## #[SCC- 1440] The DMC shall be capable to receive in UHF band an updated operational timeline during the Surface Phase. Parents: MSRD DM-CO-110 MoV: [SCC: A, RoD] ## #[SCC- 1450] After landing on the Martian surface, the DMC shall transmit to the TGO the EDL data set defined in SCC- 2480 (3rd bullet) with priority versus the surface science data. Parents: MSRD DM-CO-120 MoV: [SCC: A, RoD] ## #[SCC- 1455] Ground Command shall be able to select any data for transmission based on the operational needs. Parents: MSRD DM-CO-121 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1460] During the Surface phase operations, the DMC shall be capable to guarantee to the TGO an average data relay return of 0.150 Gb/sol (TBC) for EDL data, SP HK and Surface Science Data. Parents: MSRD DM-CO-130, MSRD DM-CO-140, MSRD DM-SY-70, MSRD MI-180, MSRD DM-DH-60 MoV: [SCC: A, RoD] ## #[SCC- 1470] During the Mars Surface operations, the RM shall be capable to guarantee to the TGO an average data relay return of 0.150 Gb/sol for both RM HK and Science Data. Parents: MSRD MI-180 MoV: [SCC: A, RoD] ## #[SCC- 1480] The communication passes sharing strategy shall be designed compatibly with the limitations imposed by the TGO design and the Electra UHF package. Comment: The communication passes of the TGO have to be shared between the two surface assets of

the 2018 Mission, i.e. the Rover Module and the Landing Platform Parents: MSRD MI-190 MoV: [SCC: A, RoD] ## #[SCC- 1485] Deleted. Parents: MoV: ##

5.3.4 Link Budget

#[SCC- 1490] Link Budget shall be maintained, documented and controlled following the requirements and rules specified in [NR 18017] and [NR 05004] § 4.2.2 for Link Margins. In particular: Link budgets shall be computed, including nominal, adverse, favorable, mean -3σ and worst case RSS (root sum square). The link budget calculations and associated margins shall be according to [ES 048]

Nominal margin > 3dB; RSS worst-case margin > 0dB;

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Mean -3 margin > 0dB Parents: MSRD SC-SY-260 MoV: [SCC: A] ## #[SCC- 1500] Link Budget shall be maintained, documented and controlled following the requirements and rules Deep space link budgets for communications with Earth shall be calculated for a weather availability of 95%. Parents: MSRD SC-SY-270 MoV: [SCC: A] ##

5.3.5 RF Compatibility Test

#[SCC- 1510] The SCC shall provide a RF suitcase as specified in [NR 18016] § 4.11. Parents: OIRD-RFS-1, OIRD-RFS-5, OIRD-RFS-6 MoV: [SCC: RoD] ##

5.4 Power

5.4.1 General

#[SCC- 1520] The SCC shall provide power to the whole SCC. In particular: All the power needed by the SCC to implement the requirements of this specification 400 W (TBC) to DM during Cruise, NTE figure, all margins included, for DMC thermal control,

commissioning and check-out, RM commissioning and checkout TBD W to DMC during thermal boost (if necessary) before separation

Parents: MSRD CM-SY-30 MoV: [SCC: T, RoD] ## #[SCC- 1530] The SCC provided power shall follow the requirement specified in [NR 05005] and [NR 05004].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-PO-10, MSRD SC-PO-20 MoV: [SCC: T, RoD] [S/S: A] ##

5.4.2 Power budget

#[SCC- 1540] Power budgets and margins shall be documented and controlled following the requirements and rules specified in [NR 05004] § 4.2.1 Parents: MSRD SC-SY-210, MSRD SC-SY-220, MSRD SC-SY-230, MSRD SC-SY-240, MSRD SC-SY-250 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.5 Science Payload Package Accommodation

#[SCC- 1550] The SCC shall include Science Payloads inside the DMC, as part of SP and RM for science to be performed on the Mars surface only. Details on science instruments can be found in [IR ESAxx2] and [IR ROSxx1]. Parents: MSRD DM-SY-150 MoV: [SCC: RoD] ##

5.6 Mission Maneuvers

5.6.1 Delta-V Requirements

#[SCC- 1560] The SCC shall provide the -V maneuvers, with margins, specified in SCC- 0340 Comment: All delta-V maneuvers shall be performed with a confidence level of at least 99.7% (3). Parents: MoV: [SCC: A, RoD] ## #[SCC- 1570 For propellant budgets computation, a 100% of margin to the Attitude control actuations shall be added. Comment: The SCC propellant mass will be calculated using the -V values reported in SCC- 340 and

considering the SCC Dry Mass. Parents: MSRD SC-SY-190 MoV: [SCC: A] ## #[SCC- 1580] The resulting error (in any direction) of any Delta-V maneuver vector bigger than 1 m/s shall not exceed 0.1% (3) bigger than 0.15 m/s but smaller than 1 m/s shall not exceed 2% (3) smaller than 0.15 m/s shall not exceed 0.003 m/s (3)

of the nominal commanded value.

Comment: proper calibration means shall be implemented to meet the specified requirement, especially for the transverse component of the Delta-V vector.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: A] ## #[SCC- 1590] The error in the direction of any Spacecraft Composite delta-V vector shall be less than 0.3 deg (3) (TBC), with respect to the nominal commanded value, including all misalignments and attitude reconstruction errors at the time of the maneuver. Parents: MoV: ## #[SCC- 1600] The SCC design shall be such that the parameters needed to allow post-facto reconstruction of the actually performed -V are stored on-board for subsequent transmission to Ground Control. Parents: MoV: [SCC: A, RoD] ## #[SCC- 1610] The Spacecraft Composite design shall be such that the actually performed delta-V’s can be measured, compared onboard with the programmed ones and corrected on-board in case of discrepancy. Parents: MSRD SC-AO-70 MoV: [SCC: RoD] ## #[SCC- 1620] Neither Delta V maneuvers nor critical operations shall be planned when the Sun-Earth-Spacecraft (SES) angle is less than 5 deg. Comment 1: Science and data relay operations are not considered to be critical operations. Comment 2: Recovery from ultimate safe mode is considered to be a critical operation. Parents: MSRD SC-AO100 MoV: [SCC: RoD] ##

5.6.2 Propellant Budget

#[SCC- 1630]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





For calculation of the propellant mass the following margins on the effective mission delta-V’s shall apply: - 100% for attitude control maneuvers Comment: No additional margin on delta-V value specified for Navigation maneuvers is requested. Parents: MSRD SC-SY-190 MoV: [SCC: A] ## #[SCC- 1640] A minimum of 2 % (TBC) provision on the total propellant mass shall be applied to estimate the propellant residuals mass for calculating the total propellant needs. MoV: [SCC: A] Parents: MSRD SC-SY-200 ##

5.7 SCC Operations and Autonomy

5.7.1 General

#[SCC- 1650] The SCC shall implement the Operational and Autonomy requirement defined in [NR 05025]. Comment: the [NR 05025] will trace the [NR 18016]. Parents: MoV: [SCC: RoD] ##

5.7.2 SCC Modes

SCC Modes are defined for each SCC configuration corresponding to specific phases of the mission.

Each SCC Mode terminology includes one or more subsystem modes for GNC, TM/TC, EPS, TCS, OBC.

Subsystem modes requirements will be defined in relevant S/S Specifications.

#[SCC- 1660] The SCC shall implement following modes to cope with the SCC operations throughout all mission phases: Ground Modes

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Test Mode Pre-Launch Mode

Cruise Flight Modes

Launch Mode Sun Pointing Mode - Nominal Earth Pointing Mode - Nominal CM/DM Separation Preparation Mode - Critical Safe Mode - Critical Survival Mode – Critical

Comment: details on EDL Modes, LP Modes and RM Modes will be defined in the relevant

requirements specifications Parents: MoV: [SCC: RoD] ## #[SCC- 1670]

The SCC Modes design shall be compatible with the requirements stated in [NR 05025] § 4. Parents: MoV: [SCC: T, RoD] ## #[SCC- 5310]

The SCC on-board system shall be in fail-safe during all Nominal Modes and in Fail-Operational during Critical Modes. Parents: MSRD SC-AO-40 MoV: [SCC: T, RoD] ##

5.7.2.1 Test Mode

#[SCC- 5320]

Test Mode shall be active on Ground during testing session. The default settings shall be loaded by test sequence. The following actions shall be inhibited:

Thrust activation Pyro activation Separation activation RF transmission

Parents: MoV: [SCC: T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 5330]

When the SCC is in Test Mode, all other subsystem modes are allowed and they shall be configurable by test sequence. Parents: MoV: [SCC: T, RoD] ##

5.7.2.2 Pre-Launch Mode

#[SCC- 5340] The Pre-Launch Mode shall be active from the positioning of the SCC on the launch pad up to the Check-Out test equipment disconnection. Comment: S/S elements inhibit philosophy during Pre-Launch Mode will be defined with the Launcher

Authority in agreements with applicable Safety rules. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5350] The Pre-Launch Mode shall allow the check out and verification of all SCC subsystem modes. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5360] The Pre-Launch Mode shall allow the SCC batteries charging. Parents: MoV: [SCC: T] [S/S: RoD] ##

5.7.2.3 Launch Mode

#[SCC- 5370] Launch Mode shall be enabled from launch pad Test Equipment disconnection up to detection of separation from the Launcher, aiming to set the spacecraft in flight operational configuration. Parents: MoV: [SCC: T] [S/S: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 5380] During Launch Mode, as a minimum:

GNC shall be set to Stand-By Mode TCS active (survival) TC reception and processing shall be active, TM collection and storage (but not transmission)

shall be performed Power shall be provided by CM batteries, i.e. the on-board configuration shall minimize power

demand Comment: During Launch Mode, after fairing separation, orientation of the upper stage will be such that

the SCC is oriented with the Sun vector orthogonal to the SCC X axis (i.e. the SCC lateral stowed Solar Array will be exposed to Sun increasing available on-board power)

Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5390] During Launch Mode the SCC shall be configured such that the GNC system can be immediately operational after separation. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5400] During launch mode, HK data shall be stored in Mass Memory. Parents: MoV: [SCC: T] [S/S: RoD] ##

5.7.2.4 Sun Pointing Mode - Nominal

#[SCC- 5410] Sun Pointing Mode shall be the entered at detection of separation from the Launcher or by Ground Command and shall be terminated upon Ground Command or on-board pre-loaded MTL command, or following autonomous transition to Safe Mode as a consequence of major failure. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5420] When SCC is in Sun Pointing Mode, the following GNC tasks shall be performed:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Sun Acquisition attitude maneuver (including attitude correction maneuvers foreseen to align the Sun vector with the S/A normal vector)

Sun Pointing allowing full Solar Array illumination Orbit Control performing Delta-V maneuver as per on-board MTL or commanded by Ground

Control (i.e. Launch Injection Correction). Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5430] MoV: [SCC: T] [S/S: RoD] Parents: When SCC is in Sun Pointing Mode, it shall be possible to use the following TM/TC Subsystem configuration(s):

TC shall be always active through LGA1 or LGA2/3 TM shall be active on LGA1 or LGA2/3, during communication windows

The selection of the antenna shall be either autonomous, based on MTL command, or commanded by Ground. ## #[SCC- 5440] When SCC is in Sun Pointing Mode, the SCC EPS shall distribute power generated by power Solar Arrays. Comment: CM Battery recharging capability is always active. Parents: MoV: [SCC: T] [S/S: RoD] ##

5.7.2.5 Earth Pointing Mode - Nominal

#[SCC- 5450] Earth Pointing Mode shall be the entered and terminated by on-board MTL command or by Ground Command or following autonomous transition to Safe Mode as a consequence of major failure. Comment: In case of loss of Ground communication the Earth Pointing Mode shall be autonomously

entered by default when the distance from Earth (estimated on-board based on pre-loaded ephemerides) requires the use of MGA for full data volume generation and the Sun Aspect Angle ensures that generated power is sufficient to cover power demand at any time.

Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5460]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





When SCC is in Earth Pointing Mode, the following GNC tasks shall be performed: Earth Acquisition attitude maneuver (including attitude correction maneuvers foreseen to align the

Earth vector with the MGA boresight vector) Earth tracking allowing full communication capability Orbit Control performing Delta-V maneuver as per on-board MTL or commanded by Ground

Control (i.e. Trajectory Correction Maneuver). Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5470] : When SCC is in Earth Pointing Mode it shall be possible to use the following TM/TC Subsystem configurations:

TC shall be always active through MGA TM shall be active through MGA during communication windows

Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5480] When in Earth Pointing Mode, the SCC EPS design shall guarantee a positive balance between power availability (from both Solar arrays and batteries) and power demand. Comment: CM Battery recharging capability is always active. In case of negative balance, SCC Safe

Mode will be activated. Parents: MoV: [SCC: T] [S/S: RoD] ##

5.7.2.6 CM/DM Separation Preparation Mode - Critical

#[SCC- 5490] CM/DM Separation Preparation Mode shall be the entered by on-board MTL command or by Ground Command. The Mode shall terminate when the CM/DM separation event is detected by DM ESA-OBC1. Comment: The Pre-Separation mode is critical phase during which the SCC is preparing for DM/CM

separation event by performing final on-board health check and acquisition of separation attitude. Being critical phase the system is in fail-operational, therefore no transition into Safe Mode shall be allowed.

Parents: MoV: [SCC: T] [S/S: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 5500] When the SCC is in CM/DM Separation Preparation Mode, the following GNC tasks shall be performed:

Earth Acquisition and tracking (including attitude correction maneuvers foreseen to align the Earth vector with the MGA boresight vector)

Separation attitude acquisition maneuver Separation attitude keeping Enabling of CM/DM Separation command

Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5510] When the SCC is in CM/DM Separation Preparation Mode, it shall be possible to use the following TM/TC Subsystem configuration(s):

TC shall be always active through MGA when SCC is Earth pointed TM shall be active through MGA when SCC is Earth pointed TM shall be active through LGA1 or LGA2/3 depending on Earth Aspect Angle when SCC is in

Separation attitude TM shall be also active through DM UHF Rear Jacket antenna Management of the hand-over between X-Band and UHF communication systems (implemented

TBD s before the separation event) Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5520] When the SCC is in CM/DM Separation Preparation Mode, the SCC EPS shall distribute power generate by Solar Arrays. In case the power demand will overcome generation capability, the CM on-board batteries shall provide necessary power. Comment: CM Battery recharging capability is always active. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5530] When the SCC is in CM/DM Separation Preparation Mode, TBD s before the CM/DM separation event, the DM shall switch to its internal batteries. Parents: MoV: [SCC: T] [S/S: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





5.7.2.7 Safe Mode - Critical

#[SCC- 5540] Safe Mode shall be the entered following major unrecoverable on-board failure or by Ground Command. The Mode shall be terminated by Ground Command or autonomously (TBC) in case of mission critical phase. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5550] The Safe Mode shall be autonomously abandoned in favor of Survival Mode in case of detected battery Depth of Discharge (DoD) overcome the safety threshold. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5560] When the SCC is in Safe Mode, the GNC shall keep the current pointing avoiding re-orientation maneuvers. The following GNC tasks shall be performed (in alternative):

Earth pointing attitude keeping (including attitude correction maneuvers foreseen to align the Earth vector with the MGA boresight vector)

Sun pointing attitude keeping (including attitude correction maneuvers foreseen to align the Sun vector with the S/A normal vector)

Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5570] When the SCC is in Safe Mode, it shall be possible to use the following TM/TC Subsystem configuration(s):

TC shall be always active through LGA1 when SCC is Earth pointed or LGA2/3 when SCC is Sun pointed

TM shall be active through LGA1 when SCC is Earth pointed or LGA2/3 when SCC is Sun pointed

TM/TC through MGA shall be activated following Ground Command. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5580]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





When SCC is in Safe Mode the SCC EPS shall distribute power generated by Solar Arrays and CM batteries up to the reaching of a pre-defined DoD threshold. The on-board configuration shall reduce power consumption disabling all non-essential loads. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 4110] The entering of safe mode throughout the entire SCC Cruise Phase shall not jeopardize the allocated fuel budget (as specified in § 5.1.3 of this specification to complete the mission objective). Comment: Fuel budget computation will consider the possibility to enter in Safe Mode once per year which means to trigger 1 Safe Mode only (TBC) during the In-flight lifetime specified in #[SCC- 0670. Parents: MSRD SC-SY-180 MoV: [SCC: A, RoD] ##

5.7.2.8 Survival Mode - Critical

#[SCC- 5590] Survival Mode shall be the entered following detection of battery DoD when the SCC is in Safe Mode. Survival Mode exit shall be possible only through Ground Command or autonomously (TBC) in case of mission critical phase. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5600] When the SCC is in Survival Mode, the following GNC tasks shall be performed:

Sun Acquisition from any attitude Sun pointing attitude keeping (including attitude correction maneuvers foreseen to align the Sun

vector with the S/A normal vector) Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 5610] When the SCC is in Survival Mode, it shall be possible to use the following TM/TC Subsystem configuration(s):

TC shall be always active through LGA1 or LGA2/3 depending on estimated Earth Aspect Angle TM shall be active through LGA1 or LGA2/3 depending on estimated Earth Aspect Angle

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T] [S/S: RoD] ##

#[SCC- 5620] When the SCC is in Survival Mode, the SCC EPS shall distribute power generated by Solar Arrays. Battery charging shall be also ensured. The on-board configuration shall reduce power consumption disabling all non-essential loads. Parents: MoV: [SCC: T] [S/S: RoD] ##

5.7.2.9 EDL Phases

#[SCC- 5621] Deleted: Covered by SCC-0430 Parents: MoV: ##

5.7.3 SCC FDIR

#[SCC- 1680] The SCC design shall include an autonomous Failure Detection, Isolation and Recovery (FDIR) function with an ability of being disabled by Ground Control. Comment: For the Rover Module it’s requested to implement Failure Detection Isolation and Safe

(FDIS) function Parents: MSRD SC-AO-10 MoV: [SCC: A, T, RoD] ## #[SCC- 1690] The FDIR function shall be implemented at the lowest possible functional level. Parents: MSRD SC-AO-20 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 1700] During all time-critical mission phases, the SCC design shall be “fail operational”, i.e. autonomously perform failure detection, isolation and recovery from a time-critical anomaly to continue the nominal operation at the time of the occurrence of the anomalous event. Comment: applicable to SCC only (i.e. not applicable to DMC during EDL) Parents: MSRD SC-AO-30 MoV: [SCC: T, RoD] ## #[SCC- 1710] During all non time-critical mission phases, the SCC design shall be “fail safe”, i.e. autonomously perform the transition to safe mode without Ground Control support. Parents: MSRD SC-AO-40 MoV: [SCC: T, RoD] ## #[SCC- 1720] The SCC shall be designed to exclude repetitive malfunctions which lead to safe mode on a regular basis. Parents: MSRD SC-AO-50 MoV: [SCC: RoD] ## #[SCC- 1730] In case of failure, the SCC shall provide to the Ground Control sufficient data to understand the type of failure and the actions performed to isolate and recover it on-board. Parents: MSRD SC-SY-390 MoV: [SCC: RoD] ## #[SCC- 1740] Hot redundancy shall be provided for functions which are essential for a continuous, uninterrupted time critical mission operation. Parents: MSRD CM-SY-60 MoV: [SCC: RoD] ## #[SCC- 1750] The total amount of time in Safe Mode shall not reduce the nominal operational mission time.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-AO-60 MoV: [SCC: A] ## #[SCC- 1760] The SCC shall support: Switch-over to the redundant resources Shut-down and isolation of malfunctioning parts Override of On-Board actions

Parents: MSRD-SC-SY-390 MoV: [SCC: A, T, RoD] ## #[SCC- 1770] The SCC shall implement FDIR functions according to the levels, from lowest to highest criticality, specified in [NR 05029] § 5. Parents: MoV: [SCC: T, RoD] ## #[SCC- 1780] The SCC shall perform FDIR functions implementing the requirements specified in [NR 05029] § 5. Parents: MoV: [SCC: A, T, RoD] ## #[SCC- 1790] When in Fail Safe (including ultimate safe mode), the Spacecraft Composite shall be able to survive up to TBC days without the need for Ground contact Operations Parents: MSRD SC-AO-80 MoV: [SCC: A, T, RoD] ## #[SCC- 1800] At power up, restart and upon recovery from any power loss, the Spacecraft Composite shall configure into a known deterministic and reproducible state. This state shall be safe (full battery charging capability and minimum power loading) and shall allow for a predefined recovery of the Spacecraft and of its subsystems.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-AO-110 MoV: [SCC: A, T, RoD] ##

5.7.4 SCC Operations

#[SCC- 1810] The SCC shall be designed and verify to comply with the detailed Operation requirements specified in [NR 05029] § 4. Parents: MoV: [SCC: A, T, RoD] ##

5.7.4.1 Payloads Operations

#[SCC- 1820] The SCC Payloads Operations are not object of this specification. Parents: MoV: [SCC: A, RoD] ##

5.7.5 SCC Autonomy

#[SCC- 1830] Single failure The SCC shall survive to failures as per requirements specified in § 6.1. Parents: MoV: [SCC: A, RoD] ## #[SCC- 1840] During all mission phases, the SCC shall be nominally controllable by Ground contact as specified in § 5.3. Parents: MoV: [SCC: RoD] ## #[SCC- 1850]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





During Conjunction, when the Sun-Earth-Spacecraft angle is less than 3 deg, the Spacecraft Composite shall be able to operate without Ground Control contact. Parents: MoV: [SCC: RoD] ## #[SCC- 1860] In case of Fail Safe, the SCC shall be able to survive for at least the period between 5 Ground contacts. Pass frequency outside of critical phases is defined in SC-1110. Comment1: The SCC design will allow permanence in Safe Mode for an unlimited time, provided that at

least 1 Ground contact per month is guaranteed. Comment2: Ground contacts means here the Mars view-period booked on a single ground station. Split

passes on one ground station do not count as individual contact periods. Parents: OIRD-CTRL-2 MoV: [SCC: A, RoD] ## #[SCC- 1870] During all non time critical mission phases, the SCC design shall allow for transition to safe mode. Parents: MoV: [SCC: T, RoD] ## #[SCC- 1880] The SCC shall perform autonomous recovery from an anomalous onboard situation (Fail Op) to continue the nominal operation at the time of the occurrence of the anomalous event during the following time-critical mission phases: SCC Initialization after separation from LV SCC Slew (TBC) CM/EDM Separation

Parents: MoV: [SCC: T, RoD] ## #[SCC- 1890] Immediately after Injection into Mars transfer trajectory by the Launch Vehicle, the SCC shall Autonomously detect separation from the Upper Stage Damp residual angular rates from the Launcher

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Acquire a safe sun pointing mode Establish communication link without Ground Control command

Parents: MSRD SC-AO-90 MoV: [SCC: A, T] ## #[SCC- 1900] Hazard Situation The SCC shall detect any reasonably determinable threat or hazard that may affect mission objectives or SCC safety and provide relevant data to the Data Handling. Comment: e.g. device failure, low battery energy level. Parents: MoV: [SCC: A, RoD] [S/S: T] ## #[SCC- 1910] The SCC shall implement the detailed Autonomy requirements specified in [NR 0198] § 4. Parents: MoV: [SCC: T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





6. DESIGN AND PERFORMANCE REQUIREMENTS

6.1 Failure Tolerance & Redundancy Implementation Requirements

#[SCC- 1920] Failure tolerance requirements related to the applicable safety regulations are specified in [NR 18026]. Parents: MSRD SY-450 MoV: [SCC: A, RoD] ## #[SCC- 1930] No single point failure shall lead to loss of mission unless differently agreed on a case-by-case basis. Comment: e.g. looking for commonality with ExoMars 2016 Mission or during critical phases like EDL. Parents: MSRD SY-460, MSRD CM-SY-70 MoV: [SCC: A, RoD] ## #[SCC- 1940] No HW or SW failure shall propagate across the interface to a redundant item or functional path. Parents: MSRD SY-470 MoV: [SCC: A, RoD] ##

6.2 Electrical

6.2.1 General

#[SCC- 1950] The SCC electrical design shall comply with the requirements of [NR 05004] (Electrical Design and Interface Requirement) and [NR 05005] (EMC and Power quality requirements) which includes [ES 032] Parents: MSRD SC-PO-10, MSRD SC-PO-20, MSRD SC-EL-10, MSRD SC-EL-20 MoV: [SCC: T, RoD] [S/S: T] ## #[SCC- 1960]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Deleted Parents: MoV: [SCC: T, RoD] ##

6.2.2 Pyrotechnical devices

#[SCC- 1970] The requirements of [NR 05007] Mechanical and Thermal Design & Interface Requirements § 4.7.12 and [NR 05004], Electrical Design and Interface Requirements § 4.5.5 shall be used. Parents: MSRD SC-MP-20, MSRD SC-MP-30 MoV: [SCC: RoD] [S/S: T] [EQP: T] ##

6.2.3 EMC

6.2.3.1 EMC Design Guidelines and Requirements

#[SCC- 1980] The requirements of [NR 05005] (EMC and Power Quality Requirements) shall be used for the EMC design of the SCC and its elements. In particular:

§ 5.1 specifies the general Design rules applicable to MOD level § 5.2 specifies the Design requirements applicable to EQ level § 5.3 specifies the Design requirements applicable to MOD-S/S level § 5.4 specifies the Design requirements applicable to Harness § 5.5 specifies the Design requirements applicable to CM-DM Interface

Parents: MSRD SC-EL-30 MoV: [SCC: T, RoD] ##

6.2.3.2 EMC Specification (Emission, Susceptibility, Corona, ESD)

#[SCC- 1990] The requirements of [NR 05005] (EMC and Power Quality Requirements) shall be used for the EMC design and verification of the SCC and its elements. In particular:

§ 6.1 specifies the EMC Requirements applicable to EQ–S/S level (Including Payloads) § 6.3 specifies the EMC Requirements applicable to MOD level § 6.4 specifies the EMC Requirements applicable to SCC level § 6.5 specifies the EMC Requirements applicable to GSE

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014






6.2.3.3 EMC Test Requirements

#[SCC- 2000] The requirements of [NR 05005] (EMC and Power Quality Requirements) shall be used for the EMC tests of the SCC and its elements. In particular:

§ 7.1 ÷ 7.3 specifies the general rules and guidelines applicable to Test logic and Facilities § 7.4 specify the requirements applicable to Test equipment’s § 7.5 ÷ 7.6 specify the Test set-up requirements for emission tests (radiated and conducted)

applicable to SSC-MOD-S/S-EQ level § 7.7 specifies the Test set-up requirements for susceptibility tests (radiated and conducted)


6.2.4 Power System

#[SCC- 2010] The Spacecraft Composite Power subsystem shall provide power generation, storage, conditioning and distribution capability to the extent necessary to fulfill the mission requirements to all its units during all phases and modes of operation including ground testing and pre-launch. Parents: MSRD SC-PO-30 MoV: [SCC: T, RoD] ## #[SCC- 2020] The SCC Power subsystem shall be designed to provide the following functions: Generation of electrical power by means of a solar array Control, conditioning and distribution of electrical power to/via a main bus Storage of the power in a SCC battery and its charge/discharge management (including the case

in which the charge starts with the CM on and the battery fully discharged) I/O functions (Status monitoring and Command interfaces) for subsystem operations and

performance evaluation Adequate redundancy and protection circuitry to avoid failure propagation and to ensure recovery

from any malfunction within the subsystem and/or electrical load failure Survival Heating power to the CM Redundant Regulated power lines to the DMC (31.5 Vdc ± 1Vdc)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Survival Heating power to the DM (as part of provided regulated power to DMC) Parents: MSRD SC-PO-40 MoV: [SCC: T, RoD] ## #[SCC- 2030] The SCC Electrical Power Subsystem (EPS) shall be in charge of electrical power provision, during ground testing, pre-launch and throughout all the mission phases, to: DM (which will be in charge to distribute power to RM during Cruise and, after landing, until

umbilical release). In particular: Rover battery charging - preplanned and periodic operations Rover thermal control system startup - sporadic, as needed Rover check-outs - preplanned and periodic operations Rover SW uploading/upgrading -preplanned and periodic operations

CM via a redundant power bus in accordance to [NR 05005] § 4. Parents: MSRD-DM-PO-20, MSRD-DM-PO-30 MoV: [SCC: RoD] ## #[SCC- 2040] MoV: [SCC: RoD] Parents: MSRD SC-PO-70 The SCC Power subsystem shall accept power supply from an umbilical external source during ground and launch operations up to satellite release from launch. ## #[SCC- 2050] The DMC secondary batteries shall be charged only at anytime prior to DMC separation, and the Spacecraft Composite Power subsystem shall enable to recharge them via protected lines. Parents: MSRD SC-PO-50 MoV: [SCC: RoD] ## #[SCC- 2060] The SCC Power subsystem shall be equipped with suitable protection devices preventing failure propagation from any user to the power bus or to any other power outlet during both on-ground activities and in-orbit operations. The operation of a protection device, shall not result in a inhibition or performance degradations of the protection features on the other power outlets.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-PO-90 MoV: [SCC: RoD] ## #[SCC- 2070] The SCC Power subsystem shall be equipped with suitable protection devices preventing failure propagation from the power bus to any user during both on-ground activities and in-orbit operations. Comment: Required protections shall not only be designed for coping with in-orbit configurations (and

possible failure modes) but as well with non-flight configuration (and failure modes) which can happen on ground (e.g. inadvertent disconnection of battery and/or solar simulators).

Parents: MSRD SC-PO-100 MoV: [SCC: RoD] ## #[SCC- 2080] The SCC Power Budget and subsystem shall be sized assuming a solar cell string and a battery string loss. Parents: MoV: [SCC: A, RoD] ## #[SCC- 2090] The SCC power subsystem shall accept modification of operational parameters by ground command. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 2100] Deleted Parents: MoV: ## #[SCC- 2110] The power outlets shall be switchable by Ground Control command, with the exception of the power outlets supplying the TC reception chain and other essential units. Parents: MSRD SC-PO-80 MoV: [SCC: T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2120] Adequate means and telemetry shall be provided to the ground to be able to determine the state of charge of the SCC battery throughout all mission phases with accuracy better than 5%. Parents: MoV: [SCC: T, RoD] # #[SCC- 2130] The SA design shall be based on actual cell performance measurements made under representative conditions. Parents: MoV: [S/S: RoD] ## #[SCC- 2140] The SCC SA Thermo-mechanical design shall comply with the requirement stated in [NR 05007] Parents: MoV: [S/S: RoD] ## #[SCC- 2150] The SA design shall be based on documented cell degradation figures. Parents: MoV: [S/S: A, RoD] ## #[SCC- 2160] The SA Loss Factors shall be assessed and taken into account for BOL/EOL power calculation with the environment specified in [NR 05013] and [NR 05007]. Comment: They shall include at least: radiations, mismatch, random failure, calibration, UV+

micrometeorites, solar attitude, temperature, contamination, sun intensity, solar aspect angle, micro debris. MPPT tracking error, if applicable, will be taken into account in the PCDU model

Parents: MoV: [S/S: A] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2170] At power up the SCC configuration shall be deterministic and reproducible with the all essential lines automatically in ON mode. Parents : MoV: [SCC: T, RoD] ## #[SCC- 2180] In case of failure of one EPS line, if cold redundancy is implemented, the switching time shall be less than TBD ms. Parents: MoV: [SCC: T] ## #[SCC- 2190] The EPS shall provide status monitoring and telecommand interfaces for subsystem operation and performance evaluation. Parents : MoV: [SCC: T, RoD] ## #[SCC- 2200] The SCC EPS shall inhibit any pyro’s activation until detection of occurred Launcher/SCC separation. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2210] MoV: [SCC: T, RoD] Parents: MSRD SC-PO-60 The Spacecraft Composite EPS operation shall be fully autonomous including operation of protections, energy management and bus regulation under all operational conditions of the mission including contingency situations without support from other spacecraft subsystems. No damage or degradation shall result from intermittent or cycled operation. ##

6.2.5 On Board Data Handling

The Avionics is the HW/SW system which implements the functions of monitoring, command and control of the complete SCC.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The Guidance Navigation and Control (GNC) functions of both attitude and trajectory are part of its tasks. Comment 1: Object of this specification is the functions to be implemented in ESA-OBC1 up to CM-DM

separation as per applicable [NR18023]. Comment 2: Functions of ESA-OBC1 relevant to EDL and Surface Mission, up to the RM egress from

the LP will be addressed but detailed requirements will be will be specified in DM Specification [NR 07000] or in relevant Roscosmos documentation (TBD).

Comment 3: Functions of ROS-OBC2 will be specified in DM Specification [NR 07000] or in relevant Roscosmos documentation (TBD) applicable to DM SP for the mission onto the Mars surface.

6.2.5.1 DHS Requirements

#[SCC- 2220] The SCC Data handling shall comprise HW and SW modules to implement the following main tasks:

Mission control (Timeline and FDIR) SCC S/S management (GNC, Propulsion, Power, Thermal, TTC and pointing mechanisms) Receiving and Dispatching telecommands Collecting, Storing, Transmitting to Ground all telemetry data (i.e. events and housekeeping

data (HK) originated both from the different Modules when active) Time Distribution I/F management with ROS-OBC2

o Execution of the ROS-OBC2 checkout o Execution of the DM P/L’s checkout (through ROS-OBC2) o SW patches

DM Battery recharging management I/F management with RM

o Execution of the RM checkouts o SW patches o RM Battery recharging o direct analog and discrete lines

Communication on internal buses and serial lines X-Band/UHF transceivers management Applications On-Board SW processing (including GNC functions) SW Patching External I/F management (with DMC) CM/DM Separation Mechanisms activation management EDL management RM egress preparation (including touch down detection, DM Solar Arrays and LP ramps

deployment, LP attitude detection, DM/RM separation inhibits removal, DM/RM separation detection)

Parents: MSRD-DH-10, DM-SY-180 MoV: [SCC: T, RoD]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





## #[SCC- 2230] The SCC On-Board Data Handling functions and relevant performance shall comply with the operations defined in § 5.7 of this Specification. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2240] The SCC On-Board Data Handling shall implement the following functions: Commandability

o Telecommand packets reception and checks o Telecommand dispatching to receivers o Telecommand forwarding to remote units o Mission timeline management o On Board Control Procedure management o Patch management and storage o Applications management

Spacecraft Modes management

o Start-up sequences o Spacecraft modes o Sub-systems modes o Equipment status o Equipment redundancy management o Communication with the equipment’s o Configuration of the equipment’s

Observability

o Telemetry parameter acquisition o Telemetry routing o Packet stores management o Telemetry forwarding from remote units o File/large data transfers management o Mass memory management o Dump management

FDIR

o SCC monitoring o Failure detection o Failure isolation o Failure recovery o Spacecraft safe mode triggering o Safe Guard Memory Management

On Board Communication

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





o 1553 buses management o CAN bus management o Serial I/F (RS422) management o Discrete& Analogue links management with internal and external units o Internal ESA-OBC1 management o External I/F management with ROS-OBC2 and RM Data Handling o Internal (GNC, TCS, RCS, …) and External (DMC & RM) I/F management

On Board Time

o On-board time computation o On-board time distribution

Application Software processing

o Cruise GNC o TCS o EDL GNC o RM egress preparation o …

Parents: MSRD DM-DH-20, MSRD DM-DH-30, MSRD DM-DH-40, MoV: [SCC: T, RoD] ## #[SCC- 2250] The SCC On-Board Data Handling design shall implement the overall SCC monitoring and control functions as specified in [NR 05029] and [NR 05025]. Parents: MSRD SC-DH-10 MoV: [SCC: T, RoD] ## #[SCC- 2260] The SCC On-Board Data Handling design shall comply with [NR 05004] which reflects the content of [ES 032]. Parents: MSRD SC-DH-20 MoV: [SCC: RoD] ## #[SCC- 2270] The SCC On-Board Data Handling architecture shall comply and [NR 05004] which reflect the content of [ES 048]. Parents: MSRD SC-DH-30 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2280] The SC Data Handling Telecommand decoder shall be compatible with [NR 05029] which reflect the content of [CS 04] ÷ [CS 07] and [NR 18017]. Parents: MSRD SC-DH-40 MoV: [SCC: T, RoD] ## #[SCC- 2290] The SC Data Handling telemetry formatter shall be compatible with [NR 05029] which reflect the content of [CS 01], [CS 02], [CS 07] and [NR 18017]. Parents: MSRD SC-DH-50 MoV: [SCC: T, RoD] ## #[SCC- 2300] If SpaceWire interface is used, the SC Data Handling System shall be compliant with [NR 05004] § 4.8.5 which reflect the content of [ES 137]. Parents: MSRD SC-DH-60 MoV: [SCC: T, RoD] ## #[SCC- 2310] For CAN Bus management, the SC Data Handling System shall be compliant with [NR 05004] § 4.8.2. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2320] The SCC On-Board Data Handling shall be considered an essential unit fully operational at power-up. Parents: MSRD SC-DH-70, MSRD SC-DH-80 MoV: [SCC: T, RoD] ## #[SCC- 2330] The SCC On-Board Data Handling (ESA-OBC1) shall allow data exchange with the DMC ROS-OBC2 through a full redundant MIL 1553B bus during all mission phases until CM/DM Separation.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: the ROS-OBC2 will be remote terminal during CRUISE, EDL and Mars Surface missions up top RM egress. After RM egress, the ROS-OBC2 will take the control of the ESA-OBC1 which will act as repeater for LP commands and telemetries.

Parents: MoV: [SCC: T, RoD] ## #[SCC- 2340] The SCC On-Board Data Handling shall acquire all the discrete and analogue signals necessary to effectively monitor the SCC elements health and status during all relevant mission phases. Comment: final monitor architecture will be reflected in the approved SCC Electrical ICD. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2350] The SCC Data Handling (ESA-OBC1) shall interface the X-Band transceiver for TM and TC management during Cruise. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2360] The SCC Data Handling (ESA-OBC1) shall interface the UHF transceiver for TM and TC management during EDL and Mars Surface Operation for communication with the UHF ELECTRA transceiver for Command/Data exchange as per I/F data specified in [ESAxx3] and [IR1154]. Parents: MSRD DMC-DH-50 MoV: [SCC: T, RoD] ## #[SCC- 2370] Deleted. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2380] The SCC Data Handling shall implement the overall SCC, up to the DMC Separation, and DMC EDL functions (including the generation of the guidance reference state in the form of a terrain relative state,

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





as well as a possible slew guidance profile from the present to the target pointing (completeness and continuity of the guidance attitude shall be ensured autonomously), up to landing on Mars surface. Parents: MSRD DM-GN-10 MoV: [SCC: A, T] ## #[SCC- 2390] The SCC Data Handling shall maintain the Mission Elapsed Time (MET) during all the mission phases. Parents: MSRD SC-DH-140 MoV: [SCC: T] ## #[SCC- 2400] The SCC Data Handling shall implement the capability to allow the MET setting by Ground command. Parents: MSRD SC-DH-150 MoV: [SCC: T] ## #[SCC- 2410] The SCC shall use the Mission Elapsed Time as reference time for all on-board, telemetry and telecommand services and timeline-related operations. Parents: MSRD SC-DH-160 MoV: [SCC: T] ## #[SCC- 2420] The SCC Data Handling shall maintain its On Board Time (OBT) with the following stability (TBC):

A) Short Term Drift Stability (daily) 2,85 ms/day/day (end of life figure to be met at any time between daily ground station passes). Note: max oscillator temperature variation compatible with the above specified daily stability figure has to be guaranteed by the spacecraft design.

B) Long Term Drift Stability (weekly)

Deleted

C) Absolute OBT Drift (Absolute Clock Stability) 8,65 (TBC) ms/day (1.00E-07 s/s) (figure valid for the entire lifetime and for the overall temperature range of the oscillator)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: OBC-2 OBT stability requirements are not object of this specification. They have to be defined based on the LP mission objectives in the relevant requirement specifications.

Parents: MoV: [SCC: A, T, RoD] ## #[SCC- 2430] The SCC Data Handling shall provide an interface for ground testing with the Ground Support Equipment (GSE), via redundant serial links, during ground testing and pre-launch phase. This interface shall accept telecommand and telemetry directly from the GSE. Parents: MSRD SC-DH-170 MoV: [SCC: T, RoD] ## #[SCC- 2440] : The SCC Data Handling shall command the CM-DM Separation mechanism. Parents: MoV: [SCC: T] ## #[SCC- 2450] The SCC Data Handling shall detect separation from the Launcher. Parents: MoV: [SCC: T] ## #[SCC- 2460] The SCC Data Handling shall detect separation from the CM. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2470] The SCC Data Handling shall allow data exchange among all SCC units during all mission phases. Parents: MoV: [SCC: T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2480] The SCC Data Handling shall implement a single point failure tolerant mass memory sized to store at End of Life

the SCC estimated essential telemetry during the Solar Conjunction the SCC generated telemetry data to be transmitted during the Ground contacts defined in § 5.3

of this specification considering two times the longest period without ground contact the DMC generated telemetry during EDL necessary for post flight reconstruction of the EDL

flight trajectory, induced thermal-mechanical loads and performance of all relevant subsystems contributing to the EDL function

During the Surface Phase, the EDL data set shall be ready for re-transmission to the TGO until confirmation from Ground of proper data reception and decoding

Parents: MSRD SC-DH-90, MSRD DM-SY-60, MSRD DM-DH-50 MoV: [SCC: A, RoD] ## #[SCC- 2485] The data volume generated during EDL, to be transmitted to Ground for Post-Flight reconstruction, shall not exceed 100 Mb (TBC). Parents: MSRD DM-SY-70 MoV: [SCC: A, RoD] ## #[SCC- 2490] The SCC Data Handling shall implement a dedicated storage area sized to store at End of Life two times the maximum planned daily return (Cruise Housekeeping). The data storage capability shall be not less than TBD Gbit end of life, assuming any one failure of the DHS. Comment: the data storage capability shall include the need to store all the necessary EDL data. Parents: MSRD SC-DH-90 MoV: [SCC: A, RoD] ## #[SCC- 2500] The SCC mass memory shall implement the management requirements specified in [NR 05029]. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2510]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Any SCC Data Handling memory and storage unit shall be designed for simultaneous and independent read and write capability. Parents: MSRD SC-DH-110 MoV: [SCC: T] ## #[SCC- 2520] Any SCC Data Handling memory and storage area shall be protected against Radiation Inducted Effects by detection and correction mechanism. Memory error detection shall be traced and reported in telemetry. Parents: MSRD SC-DH-120 MoV: [SCC: RoD] [EQP: T] ## #[SCC- 2530] A memory scrubbing mechanism shall be foreseen to prevent accumulation of errors in memories. Relevant memory scrubbing rate shall be Programmable and Commandable from Ground. Parents: MSRD SC-DH-130 MoV: [SCC: T] ## #[SCC- 2540] The SCC Data Handling shall allow specifying if the generated telemetry has to be stored in mass memory, transmitted to the RF units or any combination of these. Parents: MoV: [SCC: T] ## #[SCC- 2550] With the exception of boot PROM, all on-board memories shall be re-programmable. Parents: MoV: [SCC: T] ## #[SCC- 2560] The SCC Data Handling shall allow resetting the SCC elements into a default configuration by Ground command without the need that the command processed by software. Parents: MoV: [SCC: T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2570] In the event of major problems with Onboard Software, the SCC shall attempt re-boot in sequence from all alternative images. In case all possible reconfigurations are unsuccessful, as last resource the OBSW shall boot from a "safe software image" stored in a dedicated and independent non-volatile memory. As a minimum, the Orbiter "safe software image" shall support at least SW maintenance capabilities and safe mode. Parents: MoV: [SCC: T] ## #[SCC- 2580] It shall be possible to patch and dump all the non-volatile memory of all the onboard computers, including one installed on units. I.e. it shall be possible to patch/dump the nominal/redundant non-volatile memory, containing the base boot-up images and overlay patches, even if the associated computer is not active. Comment 1: The "base boot-up images" are to be intended as the OBSW images loaded in RAM at

system boot. Comment 2: Memory patching is required to be possible also when the associated computer is not

actively involved in the SCC control chain (hot redundant chain). Parents: MoV: [SCC: T] ## #[SCC- 2590] The SCC "safe software image" shall be patchable and it shall support at least SW maintenance capabilities and safe mode. Parents: MoV: [SCC: T] ## #[SCC- 2600] The OBSW system and application software shall reside on a non-volatile on-board memory and loaded from that memory into working memory (RAM) at time of boot-up. Two identical copies (prime and redundant) of the OBSW shall be stored on redundant non-volatile memories. The one to be used shall be defined by a flag (HW or SW), and commandable by telecommand. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2610]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





An overlay patch area shall be provided to host at least two sets of patches in non-volatile area. This shall allow to select one set of patches and to apply it to the loaded software image in RAM. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2620] The SCC Data Handling shall protect all telemetry data from overwriting. Parents: MoV: [SCC: T] ## #[SCC- 2630] The SCC Data Handling shall provide sufficient commanding to power-On every CM units. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2640] The SCC Data Handling shall be able to re-configure all the subsystems that implement redundancy at unit level accordingly to the different mission phase requirements either as autonomous FDIR action or by telecommand. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2650] The SCC Data Handling shall implement the capability to command, without software intervention, SCC critical switches, up to the DMC Separation, by on-ground telecommand, via HPC. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2660] In case of an internal failure, the SCC Data Handling shall generate sufficient data to allow Ground to understand the type of failure and the actions performed on-board to isolate and recovery it. Parents: MoV: [SCC: RoD] [S/S: T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 2670] The Orbiter Data Handling shall allow testing of the uploaded software patches before their execution, within the constraints of safety and feasibility driven by the relevant mission phase. Parents : MoV: [SCC: A, T] ## #[SCC- 2680] The Orbiter Data Handling shall provide a built-in test allowing verification of correct functions. The results of the built-in test shall be available on Ground Control request. Parents: MSRD SC-DH-180 MoV: [SCC: T] ## #[SCC- 2690] The Orbiter Data Handling shall allow performing built-in test and Software maintenance while performing nominal operations. Such maintenance operations shall have no impact on the nominal operations of the SCC. Parents: MSRD SC-DH-190 MoV: [SCC: T] ## #[SCC- 2700] The SCC in all mission phases and in all operational modes, when transmitting telemetry, shall generate a set of data named “essential telemetry” able to allow Ground to understand Spacecraft attitude and status. Parents: MoV: [SCC: A, RoD] ## #[SCC- 2710] The SCC shall be responsible to quantify the resources needed (CPU performances, Memory, etc…) to accomplish all applicable tasks reported in this specification. Parents: MoV: [SCC: A, RoD] ## #[SCC- 2720]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Any SCC intelligent unit shall be capable to accept and execute an “are you alive” command for testing the end-to-end connection commanded by: Ground The Data Handling

Parents: MoV: [SCC: T] ## #[SCC- 2730] The SCC units shall provide the capability, on Data Handling request, to enable/disable the generation of each defined periodic TM (e.g. HK or diagnostic TM packet). Parents: MoV: [SCC: T, RoD] ## #[SCC- 2740] The SCC units shall be capable to execute an internal checkout and health check without interfering with the on-going activity. Comment: this requirement applies to all non-critical mission phases Parents: MoV: [SCC: T] ## #[SCC- 2750] The SCC shall perform the checks either with a direct TC or through direct End-Items commanding. Parents: MoV: [SCC: T] ## #[SCC- 2760] The SCC Data Handling shall provide Power Management functions (e.g. Battery management) using unit telemetry readout and unit telecommand capability. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 2770] The SCC Data Handling shall provide Thermal Control functions to monitor CM units temperature and commanding heater accordingly.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T, RoD] ## #[SCC- 2780] The SCC Data Handling shall provide Thermal Control functions to monitor DMC temperatures and commanding heater accordingly during Cruise with the power provision allocated to DCM as per § 5.4 of this Specification. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2790] The SCC shall provide Data Handling with sufficient information to allow CM resource consumption and left availability evaluation, including RCS parameters for propellant consumption evaluation like individual thruster pulse durations, inlet pressures and temperatures of operation. Comment: same information shall be made available to Ground for separate computation. Parents: MoV: [SCC: A, RoD] ## #[SCC- 2800] The SCC shall provide to the Data Handling with sufficient data to evaluate the actual health status of the HW units and of the available resources and, consequently, can trigger autonomous reaction in case sufficient resources exist. Parents: MoV: [SCC: RoD] ## #[SCC- 2810] The SCC shall be able to perform mode transitions (including the safe mode) upon Data Handling Request. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2820] In case of a Safe mode the SCC shall be capable to generate TBD minimum data allowing unambiguous and rapid identification of the Safe mode.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: The reason for the triggering of the Safe mode and the history of the defined events occurred before and after the detection of the failure condition shall always be accessible in direct telemetry and stored in memory areas that can be later dumped and reset by the ground.

Parents: MoV: [SCC: T, RoD] ## #[SCC- 2830] The SCC shall provide information relevant to the health status of all on-board units and their usability for autonomous process by Data Handling. Parents: MoV: [SCC: T] [S/S: T] ## #[SCC- 2840] The SCC shall be designed to be controlled by SW running on the Data Handling, which is based on cyclic scheduling processes. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2850] The SCC shall be designed to withstand a Data Handling processor reboot lasting TBD seconds whichever is the operative mode. Comment: The duration of the reboot phase will be defined for each mode and agreed with the Prime

Contractor. Particular attention is drawn to the reboot duration to cope with during the thrusted phases.

Parents: MoV: [SCC: T, RoD] ## #[SCC- 2860] The SCC Data Handling shall provide timing synchronization to all SCC units requiring it. Parents: MoV: [SCC: T, RoD] ## #[SCC- 2870] The SCC Data Handling TMTC Functions shall implement the requirements stated in [NR 18017], [NR A134] and [NR 05029].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T, RoD] ## #[SCC- 2880] Fixed sets of data rates shall be assigned to uplink and downlink operations. Parents: SGIRD-DRC-1 MoV: [SCC: RoD] ## #[SCC- 2890] Data rates shall be selectable from these sets by transmitting a single telecommand. Parents: SGIRD-DRC-2 MoV: [SCC: T] ## #[SCC- 2900] Data rate changes on the up- and down-link shall be independent of each other and shall not lead to a loss of data. Parents: SGIRD-DRC-3 MoV: [SCC: T, RoD] ## #[SCC- 2910] It shall be possible to command the telemetry modulation index. Parents: SGIRD-DRC-4 MoV: [SCC: T] ## #[SCC- 2920] It shall be possible to command the value of the ranging modulation index without loss of data. Parents: SGIRD-DRC-5 MoV: [SCC: T] ## #[SCC- 2930] It shall be possible to command the value of the X-Band Delta DOR tones modulation index.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: SGIRD-DRC-6 MoV: [SCC: T] ## #[SCC- 2940] Switching the transponder to antenna assignments shall be executable by a single telecommand. Parents: SGIRD-CHA-1 MoV: [SCC: T, RoD] ## #[SCC- 2950] Switches in the antenna switching matrix shall also be commandable individually by direct command. Parents: SGIRD-CHA-2 MoV: [SCC: T, RoD] ## #[SCC- 2960] The TM packet down-transmission for each TM link shall be carefully managed such that:

1. No data coming from the mass memory is lost (i.e. it is flow controlled). 2. Real-time packets are down-linked in a timely manner.

Parents: SGIRD-FLC-1 MoV: [SCC: T, RoD] ## #[SCC- 2970] The SCC Data Handling shall be considered as an essential unit. Parents: MoV: [SCC: RoD] ## #[SCC- 2980] The SCC Data Handling shall be fully operational at power-up. Parents: MoV: [SCC: T] ## #[SCC- 2981]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





During the Cruise and Surface Phases, the ESA-OBC1 shall enable software uploading as an integral part of the software functionality. Parents: MSRD DM-DH-10 MoV: [SCC: T, RoD] ## #[SCC- 2982] During the Cruise Phase, the ESA-OBC1 shall enable maximum checkout testing, within the constraints of safety and feasibility of the Cruise Phase. Parents: MSRD DM-DH-20 MoV: [SCC: T, RoD] ## #[SCC- 2983] During EDL the ESA-OBC1 shall record housekeeping and telemetry for later transmission to Ground Control. Parents: MSRD DM-DH-30 MoV: [SCC: T] ## #[SCC- 2982] The ESA-OBC1 shall support the protocol defined in [CS 07], [CS 08] and [CS 09] for communication with the TGO (nominal mission) or NASA Relay Orbiter(s) that implement the same I/F of the TGO (contingency case only). Parents: MSRD DM-DH-40 MoV: [SCC: T, RoD] ## #[SCC- 2982]

During the Surface Phase, the EDL data set defined in #[SCC- 2480 shall be ready for re-transmission to the TGO until confirmation from Ground of proper data reception and decoding. Parents: MSRD DM-DH-50 MoV: [SCC: T, RoD] ##

#[SCC- 2982]

The DM LP shall be capable to acquire and store, on ROS-OBC-2, a data volume generated by the Surface Payload of up to 4 Gb/sol (TBC). Parents: MSRD DM-DH-60 MoV: [SCC: NTBV] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





6.2.5.2 Data Processing Budget

#[SCC- 2990]

The Spacecraft Composite processing load margin shall be applied as follows:

50% at System PDR 40% at System CDR 25% at System FAR

Parents: MSRD SC-SY-280 MoV: [SCC: A, RoD] ## #[SCC- 3000]

The Spacecraft Composite memory (RAM, EEPROM and PROM) size margin shall be applied as follows:

50% at System PDR 40% at System CDR 25% at System FAR

Parents: MSRD SC-SY-290 MoV: [SCC: A, RoD] ## #[SCC- 3010]

The Spacecraft Composite data busses load margin shall be applied as follows :

50% until System CDR 30% at System FAR

Parents: MSRD SC-SY-300 MoV: [SCC: A, RoD] ##

#[SCC- 3020] The Spacecraft Composite Telecommand and Telemetry channels data rate margin shall be greater than 25% under data flow required during nominal operation conditions. Parents: MSRD SC-SY-310 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





6.2.6 TTC Performances

6.2.6.1 General

#[SCC- 3030] The SCC TT&C shall be designed in compliance with the following standards: [ES 048], [ECSS 050], [ES 051], [ES 135], [ES 133], [ES 134] & [CS 01] to [CS 13]. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3040] The SCC TT&C shall be designed in compliance with [NR 18xxx]. Parents: MoV: [SCC: T, RoD] ##

6.2.6.2 X-Band

#[SCC- 3050] The SCC shall accommodate X-Band telecommunications package implementing the interface requirements specified in [NR 1154]. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3060] The TT&C shall receive and process the uplink telecommand signal in X-Band from Ground for subsequent transmission to the Data Handling subsystem. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3070] The TT&C shall be designed based on the exploitation of RF links in X-band as specified in § 5.3.2 Parents: MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 3080] The SCC TT&C subsystem shall be operational to allow Ground control during all mission phases, including pre-launch. Parents: MoV: [SCC: RoD] ## #[SCC- 3090] During pre-launch and launch only the Rx function shall be available. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3100] The SCC shall implement Hw inhibit capability to prevent Tx switch on before Launcher-SCC separation. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3110] The TT&C RFDN shall allow any path between the two receivers and any of the SCC antennae. Parents: MoV: [SCC: T] ## #[SCC- 3120] : The TT&C RFDN shall allow any path between the two transmitters and any of the SCC antennae Parents : MoV: [SCC: T] ## #[SCC- 3130] The RF architecture shall be Single Point Failure Modes tolerant. Parents: MoV: [SCC: RoD] [S/S: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 3140] Hot redundancy shall be provided for the receive function and cold redundancy for the transmit function Parents: MSRD SC-CO-100 MoV: [SCC: RoD] [S/S: RoD] ## #[SCC- 3150] During all nominal mission phases the SCC shall support Uplink data rates shall be selectable in the range 7.8125 bps to 4 kbps. Parents: SGIRD-DR-6 MoV: [SCC: RoD] ## #[SCC- 3160] During all nominal mission phases the SCC shall support a TM Data Rate selectable in the range 8 bps to 2.18 Mbpps (TBC), defined at SCC Data Handling telemetry formatter input and assuming the encoding scheme as defined in [NR 05004]. Comment 1: Exceptions over transient periods (e.g. during a delta-V maneuvers, CM-DM separation

sequence and Safe Mode) shall be justified individually and agreed with the Prime. Comment 2: Any encoding methods applied will be compliant with the ECSS standards and shall

be defined in the SG-ICD Volume 1. Comment 3: Except for standard coding the selected method will be justified by performance results

achieved with pseudo random bit strings as well as simulated science and HKTM. Parents: SGIRD-DR-7, SGIRD-ENC-2, SGIRD-ENC-3 MoV: [SCC: A, T] ## #[SCC- 3165] It shall be possible to change the encoding scheme by telecommand without loss of data. Parents: SGIRD-ENC-5 MoV: [SCC: A, T] ##

6.2.6.3 UHF Band

#[SCC- 3170] The SCC (within the DMC and RM) shall accommodate an UHF telecommunications package implementing the interface requirements specified in [ESAxx3].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T, RoD] ## #[SCC- 3180] The SCC TT&C’s (as part of the DMC and RM) DMC shall receive and process the uplink telecommand signal in UHF-Band from Ground for subsequent transmission to the Data Handling subsystem (DMC ROS-OBC2 and RM OBC). Parents: MoV: [SCC: T, RoD] ## #[SCC- 3190] The DMC TT&C shall be designed based on the exploitation of RF links in UHF-band as specified in § 5.3.3 Parents: MoV: [SCC: RoD] ## #[SCC- 3200] During EDM Coasting, EDM surface operations, Rovers Operations, the SCC UHF shall be operated implementing the Proximity 1 protocol, as per [CS 07] to [CS 09]. Parents: MoV: [SCC: RoD] [S/S: T] ##

6.3 Software

The Software requirements of this specification apply to the On Board Software to be implemented in OBC-1 and in all units under ESA procurement responsibility.

6.3.1 General

#[SCC- 3210] All the SCC software shall be developed and tested in accordance with the requirements specified in [NR 05029], [NR 05030] applies for SW PA Requirements. Parents: MSRD SC-SW-10 MoV: [SCC: A, T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 3220] All the SCC units boarding software shall comply with the requirements specified in [NR 05029]. Parents: MoV: [SCC: A, T, RoD] ## #[SCC- 3230] All software shall be developed using a Software Development Environment (SDE). Parents: MSRD SC-SW-20 MoV: [SCC: A, T, RoD] ## #[SCC- 3240] All onboard software running on the same onboard computer shall be developed using the same SDE. However, exception shall be assessed for agreement. Comment: The SW Development Environment for the ESA-OBC1 OBSW (applicable to ESA-OBC1 Data

Handling, CM ASW and DM ASW) is specified in [NR 05029] (req. M2-SW-0214). Parents: MSRD SC-SW-30 MoV: [SCC: A, T, RoD] ## #[SCC- 3250] The onboard software shall be developed using a high-level language except where explicitly exempted in agreement with Prime. Parents: MSRD SC-SW-40 MoV: [SCC: A, T, RoD] ## #[SCC- 3260] The Spacecraft Composite shall support post-launch modifications of all onboard software as specified in [NR 18016] Comment: Preliminary evaluation of maximum data volume required for OBC-1 reprogramming (reading

and recording) is 4Mb (as well as per RM OBC). Parents: MSRD SC-SW-50 MoV: [SCC: A, T, RoD] ## #[SCC- 3270]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The onboard software shall be structured such that modifications to individual code modules have minimum impact on other modules. Parents: MSRD SC-SW-60 MoV: [SCC: A, T, RoD] ## #[SCC- 3280] The onboard software, including all the needed automated procedures for all mission phases, shall be ready and qualified before launch according to [NR 05029]. Parents: MSRD SC-SW-65 MoV: [SCC: A, T, RoD] ## #[SCC- 3290] All the SCC software shall be developed in accordance with the Interface requirements specified in [NR 05029] Comment: ExoMars 2018 Sw Interface Control Document will apply when available Parents: MoV: [SCC: RoD] ##

6.3.2 Performance

#[SCC- 3300] Software and the system shall protect itself against infinite loops, computational errors and possible lock-ups resulting from undetected hardware failure on an “as much as practical” basis. Comment: requirement to be taken into account based on an “as much as practical” approach Parents: MSRD SC-SW-70 MoV: [SCC: RoD] ## #[SCC- 3310] Starting or stopping processes shall not affect the execution or performance of other running processes. Parents: MSRD SC-SW-80 MoV: [SCC: RoD] ## #[SCC- 3320]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Onboard and control monitoring shall be the activity continuously ensuring that the onboard units under supervision are in an acceptable safe state. This shall be achieved by regularly checking the state of individual parameters in the housekeeping information. Parents: MSRD SC-SW-90 MoV: [SCC: RoD] ## #[SCC- 3330] Under all load conditions permitted by the nominal operation the software shall complete its functions within the required time. This means that there shall be no schedule overruns leading to uncompleted tasks Comment: It should be pointed out that this requirement implies that only the MAXIMUM execution

times for a task shall be controlled and thus SW can tolerate execution time jitters that are below that maximum.

Parents: MSRD SC-SW-100 MoV: [SCC: RoD] ##

6.4 Harness

#[SCC- 3340] The SCC shall design spacecraft harness following the design stated in [NR 05004] § 4.6 and [NR 05005] § 5.4. Parents: MoV: [SCC: T, RoD] [S/S: T, RoD] ##

6.5 GNC

6.5.1 General

#[SCC- 3350] The SCC GNC shall provide hardware and associated on-board software to acquire, control and measure the required spacecraft attitude during all phases of the mission, and to control and monitor all the necessary Velocity Increments for the complete mission according to the specified system requirements. Comment1: The GNC architecture shall rely on the ESA-OBC1 located inside the DMC that will

implement all the GNC functions for both Cruise and EDL.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment2: Object of this specification is to provide main requirements for the Cruise GNC and main guideline for EDL GNC, which will be specified, in detail, in a dedicated Requirement Specification.

Parents: MSRD-SC-GN-10 MoV: [SCC: A, RoD] ##

6.5.2 GNC Design Requirements

#[SCC- 3360] The SCC Guidance Navigation and Control (GNC) shall provide with the following main functions throughout all the mission phases from launcher separation until the end of the Relay mission:

Attitude determination Attitude Control Trajectory determination -V control

Parents: MoV: [SCC: T, RoD] ## #[SCC- 3370] For all mission phases, the SCC shall have the autonomous capability to maintain the required attitude and to perform attitude maneuvers; including when contact with Ground Control is not available or Ground Control response time is inadequate. Parents: MSRD-GN-20 MoV: [SCC: A, RoD] ## #[SCC- 3380] Based on procedures and timelines predefined by Ground Control, the SCC shall have the capability to autonomously perform delta-V maneuvers during periods when contact with Ground Control is not available or Ground Control response time is inadequate. Parents: MSRD-GN-30 MoV: [SCC: A, RoD] ## #[SCC- 3390] The SCC shall rely on Ground Control performed navigation, using radiometric measurements, to be used for interplanetary trajectory.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD-GN-40 MoV: [SCC: A, RoD] ## #[SCC- 3400] Deleted (covered by SCC- 4000) Parents: MoV: ## #[SCC- 3410] The GNC shall provide Ground with all necessary data to allow trajectory guidance and navigation timelining by Ground sequence. Parents: MoV: [SCC: A, RoD] ## #[SCC- 3420] Throughout all mission phases the GNC design shall enable orbit determination from Ground Control. Parents: MoV: [SCC: RoD] ## #[SCC- 3430] During all mission phases, the GNC shall guarantee a stable Spacecraft Composite attitude even in the presence of perturbing torques, spacecraft flexible modes, or liquid slosh during all mission phases and in all operational modes. Parents: MSRD-GN-70 MoV: [SCC: A, RoD] ## #[SCC- 3440] During safe mode, the GNC subsystem shall be able to maintain the Spacecraft Composite in an attitude requiring a minimum of the on-board resources while ensuring power generation and communication with Ground Control. Parents: MSRD-GN-80 MoV: [SCC: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 3450] Throughout all mission phases, the SCC design shall support determination of its interplanetary trajectory and Mars orbit, with the requirement as per [NR 18017] by Ground Control. Comment: for orbit determination the DDOR technique will be used Parents: MoV: [SCC: A, RoD] ## #[SCC- 3460] The SCC shall identify all the In-Flight/On-Ground calibration requirements (including control parameters tuning) and relevant operational constraints necessary to meet the applicable requirements of this specification. Parents: MoV: [SCC: RoD] ## #[SCC- 3470] The GNC shall implement Delta-V modes according to the predefined Earth to Mars trajectory. The Delta-V manoeuvres (direction, amplitude, date), associated to this trajectory, shall be computed by Ground Control taking into account the available fuel, available time and propulsion subsystem design. Parents: MSRD-GN-90 MoV: [SCC: A, RoD] ## #[SCC- 3480] During all mission phases it shall be possible for Ground Control to update the main parameters of the GNC subsystem. Comment 1: With the exception of autonomous operations, i.e. DMC separation sequence Comment 2: Generic patch commands shall not be used for this function. Parents: MSRD-GN-100 MoV: [SCC: A, RoD] ## #[SCC- 3490] The GNC subsystem shall provide the capability to define, based on Ground Control telecommand, a new nominal/redundant configuration. Such a reconfiguration shall only be possible outside Delta-V manoeuvres (or fail-operational phases).

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD-GN-110 MoV: [SCC: A, RoD] ## #[SCC- 3500] During all mission phases, the GNC subsystem shall provide the capability of thruster reconfiguration after thruster failure. Parents: MSRD-GN-120 MoV: [SCC: A, RoD] ## #[SCC- 3510] The GNC subsystem shall allow for modification of the thruster selection and modulation algorithms parameters to take into account variations of the Centre of Mass and Inertias. Parents: MSRD-GN-130 MoV: [SCC: A, RoD] ## #[SCC- 3520] The GNC subsystem shall be able to autonomously detect blinding of STRs by Sun or planets or other bodies. In such event the GNC subsystem shall make attitude estimation based on IMU integration. Comment: a unique IMU, located in the DMC shall support both Cruise and EDL GNC. MoV: [SCC: A, RoD] Parents: MSRD-GN-160, DM-GN-20 ## #[SCC- 3530] The Spacecraft Composite shall be able to perform an end to end orbit control manoeuvre (including e.g. slew to the manoeuvre attitude, based on predefined and pre-loaded sequences but with the capability to trigger the full execution by a single command). Parents: MSRD-GN-180] MoV: [SCC: A, RoD] ## #[SCC- 3540] After the orbit control manoeuvre, the Spacecraft Composite shall autonomously go back to a default attitude (predefined by Ground Control) and acquire communications with Earth to be able to continue normal operations.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: Communication with Earth shall be established as far as battery will be in the condition to provide sufficient power to support the communication with Ground

Parents: MSRD-GN-190 MoV: [SCC: A, RoD] ## #[SCC- 3550] The GNC shall automatically regain power generation condition by Solar Array after completion of any delta V maneuver. Parents: MoV: ## #[SCC- 3560] The GNC design shall implement spin stabilized control mode for the entire cruise mission, from separation from the launcher to CM/DMC separation (this allows the implementation of a CM/DM linear separation system). The spin rate shall be nominally at 2.75rpm (16.5deg/s) (TBC) with an accuracy of +/-0.25rpm (1.5deg/s) (TBC). Comment: The SCC will be released form launcher (Proton-M/Breeze-M) in spin mode with spin rate

TBD deg/s +/-TBD deg/s. The SCC target spin rate is driven by the DMC requirement for entry phase. The DMC shall be separated in spin mode though linear separation system.

Parents: MSRD SC-SY-40, CM-SY-100 MoV: [SCC: A, RoD] ## #[SCC- 3570] The SCC shall rely on autonomous attitude determination and control using Star Trackers (STR) and Inertial Measurement Units (IMU) as sensors (same IMU for both Cruise and EDL GNC) and RCS thrusters as actuators. A Coarse Sun Sensor (CSS) shall be used to support Sun acquisition. Parents: MoV: [SCC: RoD] ## #[SCC- 3580] STR design The STR design shall rely on [ES 055] Parents:

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





MoV: [S/S: RoD] ## #[SCC- 3590] The SCC GNC shall enable the initialization of the DMC IMU before CM-DM separation providing the following data relevant at the Separation event:

SCC Quaternion (inertial Mars centered) with an accuracy 0.2 deg (3 ) (TBC) SCC Position Vector (inertial Mars centered) with an accuracy of 2 Km (TBC) SCC Velocity Vector (inertial Mars centered)with an accuracy of 1 cm/s (TBC)

Parents: MoV: [SCC: A, T] ## #[SCC- 3600] IMU periodic calibration shall be implemented during Cruise phase. Last IMU Calibration shall occur not later that tbd Hr before separation sequence start. Comment: during the IMU calibration period, the RCS actuation should be avoided. Parents: MoV: [SCC: A, T] ## #[SCC- 3610] Following calibration and prior to the separation the SCC shall allow adjustment of parameters of the DMC sequence by dedicated Ground Control command. Parents: MoV: [SCC: T] ## #[SCC- 3620] The GNC design shall take into account the presence of:

Environmental disturbing torques Composite flexible modes (e.g. due to solar arrays) Liquid slosh (e.g. fuel inside the tanks) Actuators misalignment Sensors misalignment MCI Uncertainties and variation during the mission

o SCC inertias products less that 1Kg*m2 (TBC) o Inertia ratio between spin axis and transversal axes Ixx/Iyy(Izz) > 1.2

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: A] [S/S: A, RoD] ## #[SCC- 3630] The GNC shall achieve the performance specified in § 6.5 of this specification considering the external disturbance torque (i.e. solar pressure, gravity gradients and atmospheric torques) derived from consolidated simulation data bases tailored against the SCC specific geometrical configuration and used materials. Parents: MoV: [SCC: A] ## #[SCC- 3640] Eclipse (if applicable) entry shall be automatically detected onboard and managed such as not to interrupt nominal operations. Parents: MoV: ## #[SCC- 3650] The GNC control loops for the cases which can be treated as a SISO system shall have at least the following stability margins

GM > 6db PM > 30 deg

after having taken into account all known uncertainties in the models of the plant in the control feedback loops. Where 6 DOF control loops are used or where couplings exist in the plant a MIMO control approach shall be taken and the stability margins shall be evaluated by SCC control analysis using the structured singular value to be smaller than 1. Comment: Extensive worst case simulations, like Monte Carlo analysis, utilizing representative nonlinear

system model, can be used to support stability requirement verification. Parents: MSRD SC-SY-320 MoV: [SCC: A] ## #[SCC- 3660] During all mission phases it shall be possible for Ground Control to upload the main parameters of the GNC subsystem. As a minimum:

Open-loop compensation torque initial value for the Settling Phase (for the first TCM activation or significant evolution)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Velocity measurement method used to stop the maneuver Timeline for maneuvers Mode time-out (limit for the Burn Firing Phase ending) Commanded inertial attitude quaternion for the trajectory corrections maneuvers Commanded inertial attitude quaternion for slew maneuvers Commanded -V values

Parents: MoV: [SCC: T] ## #[SCC- 3670] The SCC GNC shall identify and minimize as possible all pointing constraints to the Sun and Earth. These are generally due to Thermal or Blinding constraints. Parents: MoV: [SCC: A] ## #[SCC- 3680] Before starting a maneuver (-V or slew) the GNC subsystem shall check on-board consistency of the guidance data received from Ground. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 3690] In case an inconsistency is found between the on-board guidance data and the ones uploaded by ground, the maneuver shall not be activated. Parents: MoV: [SCC: T] [S/S: RoD] ##. #[SCC- 3700] The updating from Ground of the ephemeris tables (e.g. Earth, Mars, and Sun) used by the SCC shall be required:

not more frequently than once per week during all critical phases not more frequently than once per month during nominal phases and safe mode

Parents: MoV: [SCC: A, T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 3710] On-board the Orbiter, rough ephemeris tables shall be always available for back-up modes or Safe modes, sufficient to maintain RF link to the Earth. Parents: MoV: [SCC: A, RoD] ## #[SCC- 3720] The SCC GNC units shall be managed by the SCC Data Handling computer (ESA-OBC1). Parents: MoV: [SCC: T, RoD] ## #[SCC- 3730] The CM GNC shall provide in Telemetry unambiguous status information of all commands and programme controlled variables and modes and of all parameters required for sub-system monitoring and performance evaluation. Parents: MoV: [SCC: RoD, T] ## #[SCC- 3740] During all time-critical mission phases, the GNC design shall be “fail operational”, i.e. autonomously perform failure detection, isolation and recovery from a time-critical anomaly to continue the nominal operation at the time of the occurrence of the anomalous event. Parents: MoV: [SCC: A, T] ## #[SCC-3750] During all non time-critical mission phases, the CM GNC design shall be “fail safe”, i.e. autonomously perform the transition to safe mode without Ground Control support. Parents: MoV: [SCC: A, T] ## #[SCC- 3760]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





During the entire cruise phase, from separation from launcher to CM/DMC separation, the CM GNC shall avoid any unsafe attitudes which might endanger the mission (i.e. DMC Front Shield illuminated by Sun), even in presence of a failure. Parents: MoV: [CM: RoD, A, T, SCC: T] ## #[SCC- 3770] During the Cruise phase up to the DMC separation, the GNC design shall provide all the data needed to allow post-facto reconstruction of the SCC attitude and actually performed delta-V’s implementing all the necessary onboard storage capability for subsequent transmission to Ground. Parents: MSRD SC-SY-410 MoV: [CM: RoD, A, T, SCC: T] ## #[SCC- 3780] During the entire mission, the GNC shall provide the Propulsion S/S with monitoring and control capability. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 3790] During the entire mission, the GNC shall have the capability to command a thruster reconfiguration even after thruster failure (both continuous open or continuous closed). Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 3800] It shall be possible for the ground to command, via dedicated telecommands, every individual actuator. Parents: MoV: [SCC: T] ## #[SCC- 3810] A counter for the accumulated commanded “thruster-on” time shall be available in telemetry for each thruster independently. This shall not be reset except upon ground command.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T] ## #[SCC- 3820] The GNC shall allow modification of the thruster selection and modulation algorithms parameters to take into account variations of the spacecraft Center of Mass and inertias. Parents: MoV: [SCC: T] [S/S: A, RoD] ## #[SCC- 3830] The GNC subsystem shall provide the capability to define, by ground telecommand, a new nominal/redundant configuration. Such a reconfiguration shall only be possible outside Delta-V maneuvers. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 3840] The GNC shall not use more than TBD Kg for GNC during all ExoMars mission phases. In any case the total amount of fuel has to cope with requirement #[SCC- 810. Parents: MoV: [SCC: A] ##

6.5.3 GNC Modes

The GNC modes reported hereafter have to be considered as design guidelines for the Cruise GNC. Variations, based on GNC design constraints/optimization Vs Mission SCC Modes specified in § 5.7.2 can be considered. #[SCC- 3850] The SCC shall provide HW and SW to implement the following attitude measurement and control functional modes: Stand-by mode Spin-Up mode Nominal Sun Pointing mode Nominal Earth Pointing mode Inertial pointing mode Slew mode Delta-V mode

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





GNC Safe mode Survival mode Pre-separation mode

Comment: The Modes actual implementation in the GNC will depends on chosen design implementation. Parents: MoV: [SCC: T] [S/S: RoD] ## #[SCC- 3860] The GNC modes shall be designed to require minimum commanding during the mission lifetime. Parents: MoV: [SCC: A] ## #[SCC- 3870] The GNC modes shall provide sensor information on request and in HK telemetry to allow the ground to determine the attitude independently of the on-board system estimation process. Parents: MoV: [SCC: T, RoD] ## #[SCC- 3880] The GNC modes shall provide information from all actuators and units involved in control on request and in HK telemetry to allow the ground to verify the correct performance of the attitude and orbit control algorithms Parents: MoV: [SCC: T, RoD] ##

6.5.3.1 Stand-by Mode

#[SCC- 3890] In the Stand-by mode the GNC shall: Initiate SC S/S at power up Monitor separation straps to detect separation from launcher

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014






6.5.3.2 Spin-Up Mode

#[SCC- 3895] In the Spin up mode the GNC shall: Spin up to nominal spin rate

Comment: this will occur nominally only at launcher separation. Parents: MoV: [SCC: T, RoD] ##

6.5.3.3 Nominal Sun Pointing Mode

#[SCC- 3900] In the Nominal Sun Pointing mode the GNC shall: Acquire a stable Sun pointing, with illuminated S/A Dump residual nutation Absolute Pointing Error (APE) shall be kept less than 0.5 deg (3σ) (TBC)

Comment: The Sun Acquisition & Pointing Mode shall rely on on-board ephemeris uploaded by

Ground to autonomously derive the target attitude quaternion Parents: MoV: [SCC: T, RoD] ##

6.5.3.4 Nominal Earth Pointing Mode

#[SCC- 3910] In the Earth Pointing mode the GNC shall: Acquire a stable Earth pointing (with the Antenna boresight axis pointed toward Earth for

communication) Dump residual nutation Absolute Pointing Error shall be kept less than 0.5 deg (3σ) (TBC)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: The Earth Pointing mode shall rely on on-board ephemeris uploaded by Ground to autonomously derive the target attitude quaternion.


6.5.3.5 Inertial Pointing Mode

#[SCC- 3920] In the Inertial Pointing mode the GNC shall:

Acquire commanded target attitude Dump residual nutation Absolute Pointing Error (APE) shall be kept less than 1 deg (3σ) (TBC)

Comment: The Inertial Pointing Mode shall be entered only after dedicated Ground command indicating

the target attitude to be reached and it shall rely on STR and IMU measurements. Parents: MoV: [SCC: T, RoD] ##

6.5.3.6 Slew Mode

#[SCC- 3930] In the Slew mode the GNC shall: Autonomously generate the guidance profile from the present to target attitude Perform the slew (thruster command) Point target attitude


6.5.3.7 Δ-V Mode

#[SCC- 3940] In the Delta-V mode the CM GNC shall: Acquire the desired attitude Perform the thrust using selected thrusters

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Dump residual nutation Acquire default attitude

Comment: The Delta-V maneuvers (direction, amplitude, date), associated to this trajectory, shall be

computed by Ground Control taking into account the available fuel, available time and propulsion subsystem design

Parents: MoV: [SCC: T, RoD] ## #[SCC- 3950] In TCM (if applicable) the SCC thrust vector shall follow a pre-defined thrust program to optimize the maneuver efficiency. Parents: MoV: [SCC: A, T] ## #[SCC- 3960] The GNC subsystem shall implement Delta-V modes according to the predefined Earth to Mars trajectory. The Delta-V maneuvers (direction, amplitude, date), associated to this trajectory, shall be computed by Ground Control taking into account the available fuel, available time and propulsion subsystem design. Parents: MoV: [SCC: A, RoD] ## #[SCC- 3970] The SCC shall be able to operate in -V Mode to perform -V maneuvers at any time after 7 days from launch. Parents: MoV: [SCC: RoD] ## #[SCC- 3980] In -V Mode the GNC subsystem shall point and keep the SC thrust vector along a pre-defined trajectory direction within 0.2° half cone (3) (TBC). Thrust vector alignment during transient induced at the beginning of the maneuver shall not exceed TBD deg for TBD s Comment: The pre-selected trajectory direction is normally the instantaneous velocity (tangential to the

trajectory) which is not inertial fixed and is provided by Ground taking into account the available fuel, time and propulsion characteristics like thrust level, specific impulse etc. The GNC needs to consider the relevant attitude as time-dependant.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The requirement is given in terms of ± half-cone angle of the thrust axis, i.e. V vector (actually the XS axis).

Parents: MoV: [SCC: A, T] ## #[SCC- 3990] The GNC shall guarantee the required Delta-V maneuver accuracy considering worst case MCI uncertainties, MCI evolution, CoG offset, CoG evolution, actuators misalignment as specified in [NR 05029] SCC ICD. Parents: MoV: [SCC: A] ## #[SCC- 4000] During trajectory correction maneuver (if applicable), the GNC shall be able to autonomously generate the guidance reference attitude, in the form of a constant inertial quaternion, as well as a possible slew guidance profile from the present to the target pointing. Completeness and continuity of the guidance attitude shall be ensured at Ground segment level. Comment 1: The quaternion representation is recommended due to its suitability for SW

implementation. Comment 2: Ground has the possibility to upload the guidance in the form of: a constant inertial

quaternion or an attitude profile wrt inertial frame (polynomial coefficients for instance). Before each TCM, the GNC will be able to rally autonomously the constant inertial quaternion corresponding to the DV direction. If the ground uploads an attitude profile, the GNC checks the continuity of the profile and the completeness of the profile that are in principle both ensured at ground segment level. Completeness is understood as the reception of all the required parameters for the attitude profile generation. Note that it is not required to check the compatibility of the attitude profile with the actuators capabilities. Note also that the check of continuity depends on the parameters that are uploaded and that the continuity is automatically ensured if polynomial coefficients are uploaded. Completeness and continuity of the guidance attitude shall be ensured at ground segment level and be consistency checked on-board by the GNC.

Parents: MSRD SC-GN-50 MoV: [SCC: A, RoD T] ## #[SCC- 4010] In TCM (if applicable) the GNC shall implement the Delta-V maneuver parameters (e.g. amplitude and date) computed by ground and tele-commanded to the Composite.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: The delta-V characteristics are computed by Ground taking into account the radiometric measurements, available fuel, available time and propulsion subsystem design. Thus the GNC does not perform a proper autonomous navigation.

Parents: MoV: [SCC: RoD, T] ## #[SCC- 4020] The magnitude error of any -V maneuver bigger than 1 m/s (TBC) shall not exceed 0.1% (3) of the nominal commanded value. Parents: MoV: [SCC: A, RoD] ## #[SCC- 4030] During all -V maneuvers, the GNC shall implement the measurement, comparison and correction of the actual -V such that the requirement on Delta-V accuracy is met without Ground intervention (up to expiration of. time-out limiting the Burn Firing). Parents: MoV: [SCC: RoD, T] [S/S: A, RoD] ## #[SCC- 4040] The SCC design shall be such that the actually performed delta-Vs can be measured, compared onboard with the programmed ones and corrected on-board in case of discrepancy. Parents: MoV: [SCC: T] ## #[SCC- 4050] During delta-V maneuvers, the attitude around the thrust direction shall be optimized for power generation and communication with Ground. Comment: The exact attitude is a trade-off between the two needs and can only be done once the SCC

configuration with SA and antennas location is defined. Parents: MoV: [SCC: A, RoD] ## #[SCC- 4060]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The GNC shall automatically go to Sun/Earth Mode at the completion of any delta-V maneuvers, automatically re-pointing the solar array to the Sun. Parents: MoV: [SCC: T, RoD] ##

6.5.3.8 GNC Safe mode

#[SCC- 4064] In this mode the CM GNC shall: Keep the current attitude avoiding actuator commanding Comment: This Mode shall make use of minimal configuration reducing as much as possible the power

demand. All the unused units shall be switched off, e.g. the Star Tracker. Exiting from this mode shall be possible either via Ground TC to recover Nominal mode or autonomously to Survival mode in case of DoD alarm.

Parents: MoV: [SCC: T, RoD] ## #[SCC- 4065] The GNC shall implement sensors suite independent from the one used when the GNC Safe Modes (i.e. both Sun and Earth Pointing) activation occurs (TBC). Comment: after identification of the failure, the reconfiguration of the GNC Hw shall be in any case possible by Ground. Parents: MoV: [SCC: T, RoD] ##

6.5.3.9 GNC Survival Mode

#[SCC- 4070] In this mode the CM GNC shall: Acquire default attitude ensuring enough power generation by solar array to cover power demand

and ensuring minimum communication with Ground for diagnostic purposes and proper command receiving to exit the Safe Mode as necessary

Comment: The Safe Mode shall make use of minimal configuration reducing as much as possible the

power demand. All the unused units shall be switched off, e.g. the Star Tracker.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: T, RoD] ## #[SCC- 4080] In this Mode the GNC subsystem shall be able to maintain the Solar Array pointed to the Sun, ensuring at least an accuracy of ± 5° (1). Comment: The specified accuracy corresponds to a pointing cone angle of 5° around the Sun vector. Parents: MoV: [SCC: T] [S/S: A] ## #[SCC- 4090] During this Mode, the GNC shall be able to maintain a Sun-pointing attitude using reduced on-board resources while ensuring power generation and communication with Ground. Parents: MoV: [SCC: T, RoD] ## #[SCC- 4091] Deleted Parents: MoV: ## #[SCC- 4092] Deleted Parents: MoV: ## #[SCC- 4093] Deleted Parents: MoV: ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4100] Deleted Parents: MoV: ##

6.5.3.10 CM-DM Separation Mode

#[SCC- 4120] : In the CM-DM Separation mode the GNC shall: Perform slew to point the SCC to target inertial attitude to be kept during separation Dump residual nutation Point the SCC XSCC axis as required The 3-axis attitude determination accuracy at DMC release shall be within 0.5 deg (3σ) (TBC)

Comment: The CM-DM separation mode shall be entered either by Ground command or, in case of

communication problems, autonomously following the on-board timeline. Nominally the pre-separation shall be entered less than 24h before the separation event.

Parents MoV: [SCC: A] ## #[SCC- 4130] The SCC XSCC Absolute Pointing Error (APE) before separation shall be kept less than 0.5 deg (3σ) (TBC) Comment: The attitude error is defined as the angle between the nominal attitude (that leads to 0° to the

requested AoA at EIP along the nominal trajectory - see Figure 6-1) and the actual DMC attitude before separation.

The Angle of Attack (AoA see figure below) is the angle between a defined SC axis (the X axis in figure) and its instantaneous velocity vector; for the EDM at the instant of EIP it should be nominally 0°. Therefore the commanded XSC axis direction at separation is calculated in such a way to guarantee a 0° AoA at the EIP.

The total error at separation have to take into account the contribution induced by the separation mechanism that must be added linearly (worst case assumption) to obtain the total error.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: A] ## #[SCC- 4140] The CM-DM separation mechanism (unbalances, non-synchronous release etc.) shall produce a DMC attitude error such that its lateral angular velocity, Omegalat, is limited by:

arctan (Omegalat/Omegaspin) < TBD°

X

V t

Fligh Path Angle

SC CoM

Angle of Attack

V = velocity vector X = DM Axis of symmetry = OM thrust vector t = tangent to local horizon If X // V then “angle of attack” = 0 If V // t then “flight path angle” = 0

Figure 6-1 SCC Attitude at Separation

Parents: MoV: [SCC: A] [S/S: A, T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4150] The DM GNC, implemented as part of the ESA-OBC1 ASW, shall allow a DM safe EDL. Detailed EDL GNC requirements shall be reported in the specific document EXM-D2-RQM-AI-0074. Parents: MoV: [SCC: NTBVT] ##

6.6 Propulsion

For sake of simplification, the whole propulsion subsystem is herein identified with the standard term of Reaction Control System (RCS).

6.6.1 Propulsion design guideline and rules

#[SCC- 4160] The reaction control system (RCS) or propulsion design shall include:

Reaction Control Thrusters (RCT) to be used for attitude control and small thrusting capability

Comment: The SCC design will not implement any DSM. As a consequence it will not foresee the usage

of a Main Engine (ME) for main maneuvers Parents: MoV: [SCC: RoD] ##

6.6.2 Propulsion System Requirements

#[SCC- 4170] The S/C Composite RCS shall be designed in accordance to the propulsion system design requirements defined in § 4.8 of [NR 05007], which incorporate the [ES 037]. Parents: MSRD SC-PR-20 MoV: [SCC: A, T, RoD] [S/S: A, T, RoD] ## #[SCC- 4180] The SCC RCS shall deliver the total required delta-V and shall support all the maneuvers as defined by the mission analysis and described in § 5.6.1 of this Specification Parents: MSRD SC-PR-10 MoV: [SCC: A] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4190] The propellant tanks shall be sized to ensure propellant filling ratio of 95% without loss of performance, considering worst case conditions. Comment: Verification by Test at SSS level shall be limited to volume determination only. Parents: MSRD SC-PR-30 MoV: [SCC: A, RoD] [S/S: A, T, RoD] ## #[SCC- 4200] The propellant mass and tank capability shall be sized taking into account the propellant residual. Parents: MSRD SC-PR-40 MoV: [SCC: RoD] [S/S: A, RoD] ## #[SCC- 4210] The Propulsion subsystem shall be designed to remain configured for launch, i.e.: fully propellant and pressurant loaded, for a period of up to two (2) months without any subsequent performance degradation. Parents: MSRD SC-PR-50 MoV: [SCC: RoD] [S/S: A, RoD] ## #[SCC- 4220] No propellant leakage is allowed from the SCC RCS during any mission phase. Parents: MSRD SC-PR-70] MoV: [SCC: A, RoD] [S/S: A, RoD ## #[SCC- 4230] The maximum allowable gas leakage from the fully SCC RCS shall be of a level so as not to impact or degrading the performance of any subsystems or the Spacecraft Composite or Orbiter Module as a whole. Parents: MSRD SC-PR-80 MoV: [SCC: A, T] [S/S: A, T] ## #[SCC- 4240] The Propulsion subsystem shall be designed such that during the on ground handling, launch preparation, launch and separation phase, the propellant tanks are isolated from the combustion

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





chambers of all engines (RCTs and Main Engine) by a minimum of three in-series independent mechanical inhibits throughout the duration of this phase. Parents: MSRD SC-PR-60 MoV: [SCC: RoD] [S/S: RoD] ## #[SCC- 4250] In order to minimize disturbances generated by total thrust misalignments, the thruster layout shall be balanced to avoid orbit disturbances in case of thrusters based attitude re-acquisition. In case of single thruster failure, the balancing shall be guaranteed through dedicated maneuver (TBC). Comment: the requirements can be read also as the RCS shall provide torque around three orthogonal

axes for attitude control purposes, i.e. provide control torques in any direction without a parasitic delta-V.

Parents: MSRD SC-PR-100 MoV: [SCC: A, RoD] ## #[SCC- 4260] The RCS shall provide pure force in the XSCC axis direction (TBC). Comment: Torque residuals have to be managed by the SCC GNC. Parents: MoV: [SCC: A, T, RoD] ## #[SCC- 4270] The Propulsion System shall be designed to be used in any attitude and with a spin rate around the XSC axis as specified in #[SCC- 3560. The Reaction Control Thruster and Tanks shall be qualified for such environmental conditions. Parents: MoV: [S/S: A, RoD] ## #[SCC- 4280] A continuous monitoring capability of the following items shall be provided to Ground through telemetry for health monitoring, propellant gauging and failure detection. This shall include, as a minimum:

Tanks Operating pressure Temperature of the main engine, thrusters, thrusters propellant lines and tanks Valves Status (On/Off mode)

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Comment: The requirement defines the minimum telemetry data to be provided by the Propulsion sub-system to allow Ground, as part of Ground Operations, the proper monitoring of the S/S itself.

Parents: MSRD SC-PR-90 MoV: [SCC: T, RoD] [S/S: RoD] ## #[SCC- 4290] The propellant tank design shall be such that the required propellant flow at the correct pressures and temperatures without gas bubbles is guaranteed for all applicable mission conditions. Parents: MSRD SC-PR-110 MoV: [SCC: RoD] [S/S: T, RoD] ## #[SCC- 4300] The propellant tank design shall be such that the tank expulsion should be efficient. Parents: MSRD SC-PR-120 MoV: [SCC: A] [S/S: A, RoD] ## #[SCC- 4310] The propulsion subsystem design shall be such that propellant or gas trapped in the lines has no adverse effect on ground operations or flight operations. Parents: MSRD SC-PR-130 MoV: [SCC: A] [S/S: A, RoD] ## #[SCC- 4320] The propulsion subsystems shall be designed such that during ground operations both horizontal and vertical handling and transport in both dry and wet conditions are allowed with no adverse effects on the systems status and efficiency. Parents: MSRD SC-PR-140 MoV: [SCC: RoD] [S/S: RoD] ## #[SCC- 4330] RCS Vs GNC The propulsion subsystem shall be designed in accordance with the GNC needs

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014






6.7 Structure

#[SCC- 4340] The SCC Structure shall be designed to meet the applicable requirements specified in [NR 05007] & [NR 05010] that cover the [ES 043] Parents: MSRD SC-ST-10 MoV: [SCC: A] [S/S: T] ## #[SCC- 4350] The SCC Structure shall be designed and verified to withstand, without failure or degradation of its function, the mechanical loads as defined in [NR 05010]. Comment 1: Thermoelastic loads will be defined based on thermal maps derived from SCC Thermal

analysis. Parents: MSRD SC-ST-10 MoV: [SCC: A] ## #[SCC- 4360] The SCC structural design shall comply with the Design Margins, Uncertainty Factors and Factors of Safety specified in [NR 05007] § 4.3. Parents: MSRD SC-ST-20 MoV: [SCC: A] ## #[SCC- 4370] Structure resonant frequencies shall meet the launcher requirements specified in [NR 18027]. The structural design shall provide a minimum margin of 15% over the specified frequencies before verification of the Spacecraft Composite dynamic properties by test. Parents: MSRD SC-ST-30 MoV: [SCC: A] ## #[SCC- 4380]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The SCC structure shall comply with the dynamic envelope requirements as defined in [NR 18027]. when subject to worst case combination of limit loads and root-mean-square manufacturing tolerance. Parents: MSRD SC-ST-40 MoV: [SCC: A] ## #[SCC- 4390] The SCC structure shall comply with the Fracture Control requirements specified in [NR 05007] § 4.4 & 4.5. Parents: MoV: [SCC: A, RoD] [S/S: RoD] [EQP: T] ## #[SCC- 4400] The SCC Finite Element Model (FEM) shall be built following the directive reported in [NR 05015]. Parents: MoV: [SCC: RoD] ##

6.8 Mechanisms and Pyrotechnics

#[SCC- 4410] All the SCC mechanisms and Pyrotechnics (RCS pyros…) shall comply with the requirements specified in [NR 05007] § 4.7, [IR A132] and [ES 038] and [NR 05004]. Parents: MSRD SC-MP-10, MSRD SC-MP-20 MoV: [SCC: RoD] ## #[SCC- 4420] Pyrotechnic devices shall have barriers to ensure prevention of unintentional function in accordance with [NR 05008]. Parents: MSRD SC-MP-30 MoV: [SCC: RoD] ##

6.9 Thermal Control

#[SCC- 4430]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The SCC TCS shall be designed to meet the applicable requirements specified in [NR 05007] that covers [ES 007] and [NR 18027]. Parents: MSRD SC-TH-100 MoV: [SCC: A] ## #[SCC- 4440] The SCC TCS shall be designed and verified to withstand, without failure or degradation of its function, when exposed to the Thermal Environment as defined in [NR 05006], defined for all mission phases. Parents: MSRD SC-TH-10 MoV: [SCC: A] ## #[SCC- 4450] The TCS shall provide the thermal environment (temperatures, temperature gradients and temperature stability) required to ensure the integrity and the required performance of the SCC and its components during all the mission phases. Parents: MSRD SC-TH-10 MoV: [SCC: A, RoD] ## #[SCC- 4460] The TCS shall be dimensioned to cover the worst case scenarios derived from every mission phases in all modes of operation. Parents: MSRD SC-TH-20, MSRD-SC-TH-50 MoV: [SCC: A, RoD] ## #[SCC- 4470] The TCS shall be designed considering that the design temperature range is equal to the worst case predicted temperature range. Parents: MSRD SC-TH-71 MoV: [SCC: A] ## #[SCC- 4480] Time and temperature dependant thermally related parameters shall be taken into account in the thermal analysis. Parents: MSRD SC-TH-40 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4490] The SCC TCS shall ensure that all SCC equipment’s temperatures remain within the thermal design limits defined for each unit, during all phases of the mission and during testing activities on ground. Parents: MSRD SC-TH-71 MoV: [SCC: A] ## #[SCC- 4500] The SCC thermal control subsystem (TCS) shall maintain the structural parts which support items needing precise mounting and alignment within the temperatures and temperature stabilities ranges that allow maintaining the alignment requirements applicable to those items for all the applicable mission phases. Comment: this requirement applies also to RCS elements needing alignment. Parents: MSRD SC-TH-71 MoV: [SCC: A] ## #[SCC- 4510] The TCS shall be designed considering that the worst case predicted temperature range is equal to the worst case calculated temperatures with an uncertainty of 10°C extended at both range ends. Comment: Any other uncertainty figure must be justified and agreed with the Prime. Parents: MSRD SC-TH-70 MoV: [SCC: A] ## #[SCC- 4520] The TCS shall be designed considering that the acceptance temperature range is equal to the TCS design temperature range with a 5°C margin extended at both range ends. Parents: MSRD SC-TH-72 MoV: [SCC: A] ## #[SCC- 4530] The TCS shall be designed considering that the qualification temperature range is equal to the acceptance temperature range with a 5°C margin extended at both range ends. Parents: MSRD SC-TH-73 MoV: [SCC: A] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4540] The TCS shall provide sufficient temperature sensors to enable adequate monitoring and control during all mission phases in all modes of operation. Parents: MSRD SC-TH-30 MoV: [SCC: RoD] ## #[SCC- 4550] The SCC Power budget and associated SA and Battery sizing shall account at least for additional 20% margin on the heater power, as resulting from the analysis, during Nominal Mission operations. Parents: MoV: [SCC: A, RoD] ## #[SCC- 4560] Units declared failed by the onboard software shall be kept within the thermal control survival range, until they are confirmed unrecoverably failed by Ground control. Parents: MoV: [SCC: A, RoD] ## #[SCC- 4570] The SCC Thermal Control S/S shall be designed to cope with thermal conditions variation due to applicable eclipses. Parents: MoV: [SCC: A] ## #[SCC- 4580] The SCC TCS shall assure that the minimum predicted temperatures of any propulsion wetted component or surface contacting the propellant shall remain at least 10°C above the maximum freezing point of the on-board propellant. Parents: MoV: [SCC: A] ## #[SCC- 4590] The SCC modules reduced Thermal and Geometrical Mathematical Models (respectively TMM & GMM) shall be built following the directive reported in [NR 05003] and provided to TASI.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD SC-TH-90 MoV: [SCC: RoD] ## #[SCC- 4600] The qualification temperature range for units, where the Temperature Reference Point (TRP) is guaranteed by the TCS, shall be equal to the TCS qualification range, i.e. considering ±20°C on top of the worst case computed TRP minimum and maximum temperatures. Parents: MSRD SC-TH-74 MoV: [SCC: A, RoD, T] ## #[SCC- 4610] For external units, the worst case predicted temperature range is equal to the worst case calculated temperatures with an uncertainty of 15°C extended at both ends for flight phases and 10°C for Mars surface phase. Comment: Any other uncertainty figure must be justified and agreed with TASI. Parents: MSRD SC-TH-75 MoV: [SCC: A, RoD, T] ## #[SCC- 4620] A Thermal Reference Point (TRP) shall be defined and instrumented for all units during Ground testing and shall be used for all analyses as “interface temperature”. This reference point shall be selected such that its temperature reflects the general thermal status of the equipment. Parents: MSRD SC-TH-60, MSRD SC-TH-80 MoV: [SCC: RoD] ## #[SCC- 4630] Deleted. Parents: MoV: ## #[SCC- 4640] The SCC shall provide the DMC within the resources specified in § 5.4 of this Specification, survival thermal control capability by means of TBD M + TBD R heater lines and TBD thermistors.

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [SCC: RoD] ## #[SCC- 4645] The Thermal interface betrwwen SCC Modules, including admittable heat exchange, will be regulated by relevant thermal sections of [NR 05001] and [NR 07017]. Parents: MSRD-CM-SY-110, MSRD-DM-TH-10, MSRD-DM-TH-20 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





7. INTERFACE REQUIREMENTS

#[SCC- 4650] General SCC external and internal interface shall comply with the requirements reported in: [NR 05007] for Mechanical and Thermal interface [NR 05004] & [NR 05005] for Electrical interface [NR 05029] ExoMars 2018 SW Support Requirements Specification (EXM-M2-SSR-AI-

0028) for Software interface Comment 1: Documents applicability to Orbiter s is traced in the Applicability Matrix annexed to each

document. Comment 2: Consolidated I/F details are reported in [NR 05029] ExoMars 2018 SCC Mechanical ICD,

NR 05029] ExoMars 2018 SCC Electrical ICD & [NR 05029] ExoMars 2018 SCC Thermal ICD for Mechanical, Electrical and Thermal Interfaces respectively.


7.1 CM to DM Interface

#[SCC- 4660] The interface between the CM and the DM shall comply with the requirements stated in [NR 05001]. In particular:

§ 4 applies for I/F requirements § 5 specifies the formats that will be used for establishing the CM-DMC ICD

Comment 1: mechanical and thermal interface between CM and DMC are implemented via the coupling with the CM-DM Separation mechanism while electrical interface are implemented via feed-through connectors

Comment 2: All CM-DM Interface shall be documented in the SCC ICD’s Parents: MoV: [SCC: T, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





7.2 DM to RM Interface

#[SCC- 4670] The interface between the RM and the DM shall comply with the requirements stated in [NR 05017]. Parents: MoV: [SCC: RoD] ##

7.3 Communications (Ground Segment and TGO) Interface Requirements

7.3.1 Ground Segment Interface Requirements

#[SCC- 4680] The interface between the SCC and the Ground Segment shall be according to the requirements specified in: [NR 05029] ExoMars 2018 Autonomy and Operational Requirement Specification (EXM-M2-SSR-AI-

0032) [NR 05029] ExoMars 2018 SW Support Requirements Specification (EXM-M2-SSR-AI-0028) [NR 18017] ExoMars 2018 Space to Ground IRD (to be replaced by SGICD Vol 1&2 when available) [NR 18016] ExoMars 2018 OIRD (EXM-G2IRD-ESC-0002) Parents: MSRD GS-MO-10 MoV: [SCC: T, RoD] ##

7.3.2 TGO Interface Requirements

#[SCC- 4690] The SCC shall be designed to provide the TGO with service compatible to [IR 1154[. Comment: documents like ExoMars Input to Mars Data Relay Link ICD (EXM-MS-TNO-AI-0217) and [IR

A136] – Mars Relay Network Handbook, should be used for information Parents: MoV: [SCC: RoD, T] ##

7.4 Launcher Interface Requirements

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 4700] The SCC design shall comply with the requirements stated in [NR 18027] for both Launcher I/F and Launcher Coupled Load Analysis. Parents: MSRD SC-LA-10, MSRD SC-LA-20 MoV: [SCC: T, RoD] ## #[SCC- 4710] Attitude requirements during the coast phase of the launcher upper stage before separation of the Spacecraft Composite must be agreed with ESA and the Launcher Authority. Parents: MSRD SC-LA-40 MoV: [SCC: T, RoD] ## #[SCC- 4720] Deleted Parents: MoV: ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





8. ENVIRONMENTAL REQUIREMENTS

8.1 General

#[SCC- 4730] The Spacecraft Composite and its constituent modules shall be designed to operate under the predicted environment defined in [NR 021] during all mission phases. Induced environment shall be computed and applied according to [NR 18026]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [SCC: NTBV] ##

8.2 Ground

8.2.1 Mechanical

#[SCC- 4740] The SCC Vehicle shall be compatible with the Ground mechanical environment defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.1. Parents: MSRD EN-20, MSRD EN-30 MoV: [SCC: RoD, A, T] ##

8.2.2 Thermal

#[SCC- 4750]

The SCC Vehicle shall be compatible with the Ground thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.1. Parents: MSRD EN-80 MoV: [SCC: A, RoD] [EQP: T] ##

8.2.3 Ambient

#[SCC- 4760] During integration and testing the SCC Vehicle shall be compatible with the Ground ambient environment (e.g. humidity) defined in the [NR 18025].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD EN-10, MSRD EN-70 MoV: [SCC: A, RoD] ##

8.3 Launch

8.3.1 Mechanical

#[SCC- 4770] During launch the SCC shall withstand the mechanical loads defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.2, which incorporates the directives stated in [NR18027]. Parents: MSRD EN-20, MSRD EN-40, MSRD EN-50 MoV: [SCC: A, RoD, T] ##

8.3.2 Thermal

#[SCC- 4780] During launch the SCC shall withstand the thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.2. Parents: MSRD EN-100 MoV: [SCC: A, RoD] [S/S: T] ##

8.3.3 Ambient

#[SCC- 4790] During launch the SCC shall withstand the ambient (e.g. depressurization, air flux…) defined in the Space Environment and Test Requirements Specification [NR 05010] § 4.2.2.6 and [NR 05006] § 5.1. Parents: MoV: [SCC: A, RoD] ##

8.3.4 EMC

#[SCC- 4800]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





During launch the SCC shall withstand the electromagnetic environment defined in the EMC and Power Quality Requirements Specification [NR 05005], which incorporates the Launcher imposed requirements stated in [NR 18027]. Parents: MoV: [SCC: RoD] [S/S: T] ##

8.4 Flight (Cruise)

8.4.1 Mechanical

#[SCC- 4810] During the Cruise to Mars, the SCC shall withstand the mechanical loads defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.3. Parents: MSRD EN-60 MoV: [SCC: A, RoD] ##

8.4.2 Thermal

#[SCC- 4820] During the Cruise to Mars, the SCC vehicle shall withstand the thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.3. Parents: MSRD EN-90, MSRD EN-110 MoV: [SCC: A, RoD] [EQP: T] ##

8.4.3 Space

#[SCC- 4830] During its In-Flight mission, the SCC shall withstand the ambient defined in the [NR 05013]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [SCC: A, RoD, T] ##

8.4.3.1 Radiation

#[SCC- 4840]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The SCC and its elements shall be designed to operate during all phases of the mission under the predicted ionizing radiation environment as described in the NR 05013]. Margin on the radiation dose shall be applied according to [NR 18026]. Parents: MSRD EN-120 MoV: [SCC: A, RoD] [EQP: T] ##

8.4.4 EMC

#[SCC- 4850] The SCC vehicle shall withstand the electromagnetic environment defined in the EMC and Power Quality Requirements Specification [NR 05005]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [SCC: RoD] [S/S: T] [EQP: T] ##

8.5 Mars Proximity and Separation

8.5.1 Mechanical

#[SCC- 4860] During Mars Proximity and Separation, the SCC shall withstand the mechanical loads defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.4. Parents: MSRD EN-60 MoV: [SCC: A, RoD] ##

8.5.2 Thermal

#[SCC- 4870] During Mars Proximity and Separation, the SCC vehicle shall withstand the thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.4. Parents: MSRD EN-110 MoV: [SCC: A, RoD] [EQP: T] ##

8.5.3 Space

#[SCC- 4880]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





During Mars Proximity and Separation, the SCC shall withstand the ambient defined in the [NR 05013]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [SCC: A, RoD, T] ##

8.5.4 EMC

#[SCC- 4890] Mars Proximity and Separation, the SCC vehicle shall withstand the electromagnetic environment defined in the EMC and Power Quality Requirements Specification [NR 05005]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [SCC: RoD, T] ##

8.6 Entry, Descent and Landing (EDL)

8.6.1 Mechanical

#[SCC- 4900] During the EDL phases the DM shall withstand the mechanical loads defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.5. Parents: MSRD EN-60 MoV: [DM: A, RoD] ##

8.6.2 Thermal

#[SCC- 4910] During the EDL phases the DM shall withstand the thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.5. MoV: [DM: A, RoD] Parents: MSRD EN-110, MSRD EN-90 ##

8.6.3 Space

#[SCC- 4920] During the EDL phases, the DM shall withstand the ambient defined in the Specification [NR 05013].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [DM: A, RoD, T] ##

8.6.4 EMC

#[SCC- 4930] During the EDL phases, the DM vehicle shall withstand the electromagnetic environment defined in the EMC and Power Quality Requirements Specification [NR 05005]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [DM: RoD] [S/S: T] [EQP: T] ##

8.7 Mars Surface

8.7.1 Mechanical

#[SCC- 4940] During the Mars Surface operations, the LP shall withstand the mechanical loads defined in the Mechanical Environment and Test Requirements Specification [NR 05010] § 4.6. Parents: MSRD EN-60 MoV: [DM: A, RoD] ##

8.7.2 Thermal

#[SCC- 4950] During the Mars Surface operations, the LP vehicle shall withstand the thermal environment defined in the Thermal Environment and Test Requirements Specification [NR 05006] § 5.6 and § 5.7. Parents: MSRD EN-110, MSRD EN-90 MoV: [DM: A, RoD, T] ##

8.7.3 Ambient

#[SCC- 4960] During the Mars Surface operations, the LP shall withstand the ambient defined in the Specification [NR 05013].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Parents: MoV: [DM: A, RoD, T] ##

8.7.4 EMC

#[SCC- 4970] During the Mars Surface operations, the LP vehicle shall withstand the electromagnetic environment defined in the EMC and Power Quality Requirements Specification [NR 05005]. Parents: MSRD EN-10, MSRD SC-SY-20 MoV: [DM: RoD] [S/S: T] [EQP: T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





9. PLANETARY PROTECTION IMPLEMENTATION REQUIREMENTS

#[SCC- 4980] The SCC (and related GSE where applicable) shall comply with the requirements described [NR 05011]. Parents: MSRD MI-170 MoV: [SCC: A, RoD] [S/S: T] [EQP: T] ## #[SCC- 4990] The bioburden reduction of the CM during atmospheric entry on Mars shall be demonstrated by a break-up/burn-out analysis Parents: MSRD CM-SY-50 MoV: [CM: A, RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





10. CLEANLINESS AND CONTAMINATION REQUIREMENTS

#[SCC- 5000] General C&C The SCC (and related GSE) shall comply with cleanliness and contamination requirements as defined in [NR 05014]. Parents: MoV: [SCC: A, RoD, I] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





11. LOGISTIC REQUIREMENTS

#[SCC- 5010] The SCC design shall allow its packing, handling and transportation following the guidelines reported in PSS-01-202 Issue 1 Preservation, Storage, Handling and Transportation of ESA spacecraft hardware, see [NR 18026] § 4.1, ExoMars Facilities Plan (Facilities Utilization and Transportation) and ExoMars Transportation Plan both to be written. Comment: The Spacecraft Composite will be designed taking into account transportation to the launch

site by rail (current baseline) or air. Parents: MSRD SC SYS-30 MoV: [SCC: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





12. AIV REQUIREMENTS

#[SCC- 5020] The SCC shall be integrated and verified according to AIV requirements as defined in [NR 18025] and following the plan [NR 05039]. Parents: MoV: [SCC: RoD] ## #[SCC- 5030] The SCC shall be based on a Flight/Proto-flight model development approach, supported by at least the following models:

Structural Model (SM) Avionics Test Bench(es)/Avionics Validation Model (ATB’s/AVM(*)) Flight/Proto-Flight Model (FM/PFM (**))

(*) ATB is the test bench used at module level. The AVM integrates the Modules ATB to

perform the end-to-end functional verification at SCC level. (**) Proto-Flight Approach applies for CM Thermal Qualification only

Comment: SOW is applicable for deliverables details. Parents: MoV: [SCC: NTBV] ## #[SCC- 5040] The models to be delivered shall be the following:

1 Structural Model (SM) 1 Proto-Flight Model (PFM) EM or FUMO units for the ATB’s/AVM

Comment: SOW is applicable for deliverables details. Parents: MoV: [SCC: NTBV] ## #[SCC- 5050]

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





The SCC shall provide the following hardware and software simulators (TBC):

CM I/F simulator (OB-EDM) DM I/F simulator RM I/F Simulator CRUISE GNC simulator (part of GNC SCOE) EDL GMC simulator 6-DoF spacecraft E2E Simulator (for all the mission phases) Power, TT&C, DH units simulators, as needed, as part of relevant SCOE’s

Parents: MoV: [SCC: NTBV] ## #[SCC- 5060] The purpose of the SCC SM is the structural qualification. The minimum required SM tests shall be:

Mass properties (CoG determination, Weighting, MoI) (TBC) Alignment measurement Sinusoidal vibration tests (including the Test for the determination of vibrational modes) Acoustic tests Proof Pressure & Leakage (TBC) Shock during the separation of clampband from LV adapter; Shock during the separation of DM from CM .

Parents: MoV: [SCC: NTBV] ## #[SCC- 5070] The SCC AVM shall be used to validate the avionics design and electrical interfaces, including FDIR management. It shall be made of at least Data Handling FUMO (implementing processor redundancy), inclusive of SCC Software, GNC sensors, EPS and TT&C units. Parents: MoV: [SCC: NTBV] ## #[SCC- 5080] On the AVM, a complete functional, electrical, software and GNC validation of the SCC is required and the following tests (as a minimum) shall be performed (TBC):

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Electrical interfaces (internal and external) On Board Data Handling Integrated Subsystem tests EPS Integrated Subsystem tests TT&C Integrated Subsystem tests GNC functional & performances through GNC open and closed-loop On Board Software Validation FDIR and general module functions verification

Parents: MoV: [SCC: NTBV] ## #[SCC- 5090] The PFM shall perform at least the following tests (TBC):

Mass properties (CoG determination, Weight, MoI) Mechanical Interfaces check Alignment adjustment and measurement Mechanism deployment/actuation RCS subsystem validation Proof Pressure & Leakage Conducted EMC Electrical interfaces (internal and external) On Board Data Handling Integrated Subsystem tests EPS Integrated Subsystem tests TT&C Integrated Subsystem tests GNC functional & performances through GNC open and closed-loop On Board Software Final Acceptance FDIR and general module functions verification

Parents: MoV: [SCC: NTBV] ##

12.1 MGSE & FGSE Requirements

#[SCC- 5100] MGSE General Requirements All MGSE to be used for the AIT activities of the SCC shall be designed according to general requirements defined in [NR 05029]. Parents: MoV: [RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 5110] MGSE Used at Orbiter and SCC Level The following MGSE shall be used during SCC AIT activities (TBC):

Transport & Storage (*) Container (CTSC) Equipment/Panel Integration Trolley & Handling Set (CIHT) Vertical Integration Stand (CVIS) Vertical Hoisting Device (CVHD) Handling Transport Adapter (CHTA) Handling & Test Clamp-Band (CTCB) Solar Array Transport Container (CSATC) (**) Solar Array Deployment Device (SADD) SCC Tilting & Rotating Dolly (CTRD) (SCC inside the container in horizontal position) SCC Horizontal Handling Device (CHHD) (SCC inside the container in horizontal

position) SCC Protection Covers (CPC) Alignment Tools MGA Transport Container (TBC if necessary)

(*) purging with dry nitrogen will be considered on an “as necessary” basis. (**) In case the CM solar Arrays will need to be transported separately from the CM Parents: MoV: [S/S: RoD] ## #[SCC- 5120] CTSC, CHHD, CPC shall support the CM AIV CTRD, CIHT, CHTA, CVIS, CVHD, CTCB shall support the SCC AIV Parents: MoV: [S/S: RoD] ## #[SCC- 5130] FGSE Used at S/C (Composite) Level The following FGSE shall be made available for AIT system activities at S/C Composite level (TBC):

Thruster Leak Test Adapter, with std I/F (e.g. KT flange) to leak detectors Dedicated Fluid I/F adapters kit (Ground Half Couplings) with standard interface to FGSE

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Pressurization Device Unit Tester (UPS SCOE) Simulant Loading Device Propellant Loading Device

Parents: MoV: [S/S: RoD] ## #[SCC- 5140] Specific requirements are defined hereafter for some MGSE items used by TAS-I/Lavochkin at S/C Composite level. Parents: MoV: [S/S: RoD] ## #[SCC- 5150] The CTRD, CIHT, CHTA, CVIS, CVHD, the SADD and the SCC Protective Covers dimensions shall be compatible with the overall envelope of the SCC. Parents: MoV: [S/S: RoD] ## #[SCC- 5160] The CTRD, CIHT, CHTA, CVIS, CVHD, CTCB shall be designed on the account of the physical properties (Mass and CoG) of the SCC. Parents: MoV: [S/S: RoD] ## #[SCC- 5170] The CRTD, CIHT, CHTA, CVIS, CVHD, CTCB and the SCC Protective Covers dimensions shall be agreed with TASI in order to ensure their compatibility with the overall envelope of the SCC MGSE Access Working Platforms (AWP). Parents: MoV: [S/S: RoD] ## #[SCC- 5180] The CTCB shall interface with the following System MGSE Composite Test Adapters (at separation ring I/F, Φ1666 mm):

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





Composite Mass Properties Adapter (CMPA) TBC Composite Thermal Test Adapter (CTTA) Composite Vibration Test Adapter (CVTA) Composite Acoustic Test Adapter (CATA),

Parents: MoV: [S/S: RoD] ## #[SCC- 5190] The SCC transport container shall be a leak tight container, i.e. is shall be designed to guarantee leakage values compatible with the ones specified to be detected during CM propulsion sub-system leak test, implemented on SCC system. Parents: MoV: [S/S: T, RoD] ## #[SCC- 5200] The CVIS shall support the maximum limit loads due to SCC Integration and handling activities carried out on different assemblies (different mass and CoG) Integration operation, static worst case (CVIS on screw-jacks), on following assembly: DMIRS tilting cradle (System MGSE) + DCHTB (System-I MGSE) + S/C Composite( wet) + CHTA MGSE (or CTTA System MGSE or LVA F/H) + CTCB MGSE. Clean Room indoor displacements (CVIS on wheels): S/C Composite (dry) + DCHTB + CHTA MGSE (or CTTA TAS-I MGSE or LVA F/H) + CTCB MGSE Parents: MoV: [S/S: A, T] ## #[SCC- 5210] The CHTA shall support the maximum limit loads due to S/C Composite integration and handling activities carried out on different assemblies (different mass and CoG), both in vertical and horizontal configurations.

Integration operation, static case, on following assembly installed on CVIS: DMIRS tilting cradle (TAS-I MGSE) + DCHTB (TAS-I MGSE) + SCC (wet) + CTCB MGSE

Clean Room indoor displacements, via CVIS on wheels: S/C Composite (dry) + DCHTB (TAS-I MGSE) + CTCB MGSE

Handling (hoisting) operation, with dry S/C Composite in horizontal configuration: S/C Composite (dry) + DCHTB (TAS-I MGSE) + CTCB MGSE

Parents: MoV: [S/S: A, T] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





#[SCC- 5220] : The CTCB shall support the maximum limit loads due to S/C Composite integration and handling activities carried out on different assemblies (different mass and CoG), both in vertical and horizontal configurations.

Integration operation, static case, on following assembly installed on CVIS: DMIRS tilting cradle (System MGSE) + DCHTB (System MGSE) + S/C Composite (wet)

Clean Room indoor displacements, via CVIS on wheels: S/C Composite (dry) + DCHTB (System MGSE)

Handling (hoisting) operation, with dry S/C Composite in horizontal configuration: S/C Composite (dry) + DCHTB (System MGSE)

Parents MoV: [S/S: A, T] ## #[SCC- 5230] The CTCB shall support the thermal loads induced by the SCC system thermal tests (combined with the limit static loads due to the SCC supported mass). Parents: MoV: [S/S: A] ## #[SCC- 5240] The CTCB shall support the dynamic loads induced by vibration test (axial and lateral) on the maximum supported mass due to the SCC wet configuration. Parents: MoV: [S/S: A, T] ## #[SCC- 5250] All MGSE's, in terms of design, verification, manufacturing materials, electromechanical components, surface protection treatments etc...) shall comply with the requirements reported in [NR 0112] § 11. Parents: MoV: [S/S: RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





12.2 EGSE REQUIREMENTS

#[SCC- 5260] All EGSE to be used for the AIT activities of the SCC shall be designed according to general requirements defined in [NR 05029]. Parents: MoV: [RoD] ## #[SCC- 5270] EGSE Used at SCC Level The following EGSE shall be used during SCC AIT activities:

Full CCS SCC Power SCOE including:

o Solar array simulator o Battery simulator o Pyro Simulator

TMTC Front End Equipment TT&C SCOE (X-band) Data Handling SCOE including:

o 1553 milbus Emulation/Simulation o CAN Bus o Others (e.g. to I/F UHF Package)

GNC SCOE Including: o Spacecraft dynamics simulator o Sensors and Actuators simulators (as needed) o Units Simulators/SCOE

QSL (Quick SW loading) SCOE UHF Transceiver SCOE RF Suitcase

Parents: MoV: [SCC: NTBV] ## #[SCC- 5280] EGSE PA Requirements All EGSE's, in terms of design, verification, manufacturing materials, components, surface protection treatments etc...) shall comply with the requirements reported in [NR 18026]. Parents: MoV: [SCC: NTBV] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





12.2.1 EGSE Connections

#[SCC- 5290] EGSE Lines The SCC shall provide dedicated Test connectors to be used during SCC AIT phase. Parents: MoV: [RoD] ## #[SCC- 5300] Test connector(s) shall be located in an easily accessible part allowing the connection even with the CM in stowed configuration. Parents: MoV: [RoD] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





13. PRODUCT ASSURANCE AND SAFETY REQUIREMENTS

#[SCC- 5310] The SCC, including its equipment and GSE shall be designed, manufactured and tested according to PA requirements as defined in [NR 05008]. Parents: MSRD MoV: [SCC: A, T, RoD, I] ##

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





14. CARRIER MODULE DETAILED REQUIREMENTS

Detailed requirements applicable to CM are deferred to the [NR06000].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





15. DESCENT MODULE DETAILED REQUIREMENTS

Detailed requirements applicable to DM are deferred to the [NR07000].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





16. ROVER MODULE DETAILED REQUIREMENTS

Detailed requirements applicable to RM are deferred to the [NR0400].

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





17. MSRD REQUIREMENTS NOT TRACED IN THIS SPECIFICATION

MSRD-MI-220 The mission shall be designed to fulfil the Space Debris mitigation guidelines established in ECSS-U-AS-10C, Space sustainability. Adoption Notice of ISO 24113: Space systems - Space debris mitigation requirements. The verification of this requirement has to be managed by ROS/LAV as per SRR RID AP-34 disposition. MSRD SC-SY-10 The Spacecraft Composite shall be designed according to the tailored or integral ECSS and CCSDS standards (as per 3.1.2 and 3.1.3) unless otherwise specified in this document applicability of Standards is spread all over this specification. MSRD-CM-SY-80 Requirement not applicable neither to the SCC nor to the CM. MSRD-DM-PO-10 Requirement not pertinent to System Specification

REFERENCE : DATE :

EXM-M2-SYS-AI-0020 28-03-2014





END OF DOCUMENT

ExoMars 2018 Spacecraft Composite Requirements...

Documents

Transcript of ExoMars 2018 Spacecraft Composite Requirements...