_id
stringlengths
30
67
title
stringclasses
196 values
text
stringlengths
31
8.3k
metadata
dict
image
null
ECSS-E-ST-10-09C(31July2008)-page=20
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  5.4.5 Mechanical frames a. The  frame  for  a  mechanical  system  shall  be  related  to  its  material  structure definition.  b. For alignment, integration and test purposes, the origin and axes of the  coordinate systems shall be defined using physical and accessible points,  inc...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 20 }
null
ECSS-E-ST-10-09C(31July2008)-page=21
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  d. Positive angles about an axis should be defined in a right handed sense.  e. Any left handed rotation convention shall be highlighted in the CSD.  f. An elementary rotation shall be defined by a rotation axis and an angle.  g. If the rotation is represented by a quaternion, the or...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 21 }
null
ECSS-E-ST-10-09C(31July2008)-page=22
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  NOTE 3  The  uncertainty  of  transformed  quantities  is  not  the transformation of the uncertainties. See [3] for  pointing errors and [4] for measurement errors.  h. The  time  dependency  of  a  transformation  between  coordinate  systems  shall be defined.  NOTE  The transformat...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 22 }
null
ECSS-E-ST-10-09C(31July2008)-page=23
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Annex A (normative) Coordinate Systems Document (CSD) - DRD A.1 DRD identification A.1.1 Requirement identification and source document This DRD is called from ECSS‐E‐ST‐10‐09, requirement 5.2.2a.  A.1.2 Purpose and objective Proper documentation and maintenance of coordinate s...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 23 }
null
ECSS-E-ST-10-09C(31July2008)-page=24
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  c. The CSD shall define notation conventions for the transfer of coordinates  and transformation data.  <4> Units  a. The CSD shall specify the units pertaining to the coordinate systems and  parameterisations used within the project.  <5> Time standards  a. The  CSD  shall  specify...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 24 }
null
ECSS-E-ST-10-09C(31July2008)-page=25
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  c. The  CSD  shall  describe  in  a  graphical  representation  the  lower  level  chains of transformations.   d. Each  individual  coordinate  system,  identified  in  <9>  below,  shall  be   graphically represented.   e. These  diagrams  shall  contain  any  additional  constraint...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 25 }
null
ECSS-E-ST-10-09C(31July2008)-page=26
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Annex B (informative) Transformation tree analysis B.1 General Issues involved in the definition of coordinate systems and the transformations  between them are illustrated via examples below.  B.2 Transformation examples A coordinate system can be defined using a “Franck” template...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 26 }
null
ECSS-E-ST-10-09C(31July2008)-page=27
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  are docked together. Additional arrows (broken lines) can be added to indicate  measurement or estimation.   Figure B‐3 shows a Franck diagram for a spacecraft, whilst Figure B‐4 shows a  preliminary Franck diagram for star tracker alignment.  Table B‐1: Example of mechanical body frame ...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 27 }
null
ECSS-E-ST-10-09C(31July2008)-page=28
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Table B‐2: Example of orbital coordinate system   TYPE :   Pseudo‐inertial   Title/Name :   Equatorial coordinate frame  Mnemonic :  E  ID :   IN‐E‐01  Definition :  Origin is at the centre of the Earth.  The X axis lies in the equatorial plane and passes through the intersection of the ...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 28 }
null
ECSS-E-ST-10-09C(31July2008)-page=29
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Diagram : Kouro   XE O YE ZE θE2TOD Vernal   direction  Level‐0  reference  coordinate system  kinetic  trans‐  Level‐1  coordinate  system kinetic  trans‐  kinetic  trans‐  kinetic  trans‐  kinetic  trans‐  Level‐2  coordinate  system  kinetic  trans‐  Level‐2  coordinate  system Lev...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 29 }
null
ECSS-E-ST-10-09C(31July2008)-page=30
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  reference coordinate system kinetic trans- formation planetary coordinate system vehicle coordinate system kinetic trans- formation mobile equipment or fixed instrument intermediate coordinate system moving system coordinate system Basic etc. etc. etc. e...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 30 }
null
ECSS-E-ST-10-09C(31July2008)-page=31
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  ToD frame attitude control frame mechanical reference frame Sun sensor measurement frame attitude guidance frame local orbital frame trajectory attitude T, R T, R T, R Static transformations T = translational transformation R = rotational transformation D...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 31 }
null
ECSS-E-ST-10-09C(31July2008)-page=32
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Level-0 Level-1 Level-2 s/c mechanical reference frame STR boresight reference frame STR mechanical reference frame s/c alignment frame STR alignment frame Quaternion of boresight reference frame w.r.t. star catalogue frame determine measure T,R T,R T,R T,R Figure B‐4: ...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 32 }
null
ECSS-E-ST-10-09C(31July2008)-page=33
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Annex C (informative) International standards authorities C.1 Standards The  international  authorities  listed  below  define  and  maintain  reference  information.  C.2 Time C.2.1 United States Naval Observatory (USNO) The Official Source of Time for the Department of Defense...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 33 }
null
ECSS-E-ST-10-09C(31July2008)-page=34
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Information on direct link to solar system ephemeris data is available at: <ftp://ftp.imcce.fr/pub/ephem> and <http://www.imcce.fr/inpop>. C.3.2 Jet Propulsion Laboratory (JPL) ephemerides Jet  Propulsion  Laboratory  (JPL)  provides  ephemerides  for  planets,  planetary satellit...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 34 }
null
ECSS-E-ST-10-09C(31July2008)-page=35
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  At  <http://maia.usno.navy.mil/index.html>,  it  is  possible  to  get  a  snapshot  definition of time and access the Earth rotation parameters, which are essential  for  the  transformation  between  Earth‐centred  inertial  coordinates  and  Earth‐ centred Earth‐fixed coordinates. It ...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 35 }
null
ECSS-E-ST-10-09C(31July2008)-page=36
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  This document specifies two types of standard attitude data message formats  for use in transferring spacecraft attitude information between space agencies:  the attitude parameter message and the attitude ephemeris message.  C.6 IAU/IAG Working Group on Cartographic Coordinates and Ro...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 36 }
null
ECSS-E-ST-10-09C(31July2008)-page=37
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  References [1] “The past, present and future of reference systems for astronomy and  geodesy”, G.A. Wilkins, Proceedings of the 141st symposium on the  International Astronomical Union, Leningrad, October 17‐21, 1989,  (Kluwer academic publishers), pp 39‐46.  [2] IERS Technical Note 3...
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 37 }
null
ECSS-E-ST-10-09C(31July2008)-page=38
ECSS-E-ST-10-09C(31July2008)
ECSS‐E‐ST‐10‐09C  31 July 2008  Bibliography ECSS‐S‐ST‐00  ECSS system – Description and implementation  ECSS‐E‐ST‐10  Space engineering – System engineering general  requirements    38
{ "document_id": "ECSS-E-ST-10-09C(31July2008)", "page_number": 38 }
null
ECSS-E-ST-70C(31July2008)-page=1
ECSS-E-ST-70C(31July2008)
ECSS-E-ST-70C 31 July 2008 Space engineering Ground systems and operations   ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 1 }
null
ECSS-E-ST-70C(31July2008)-page=2
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Foreword This  Standard  is  one  of  the  series  of  ECSS  Standards  intended  to  be  applied  together  for  the  management,  engineering  and  product  assurance  in  space  projects  and  applications.  ECSS  is  a  cooperative  effort  of  the  European  Space  Agency,  national  ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 2 }
null
ECSS-E-ST-70C(31July2008)-page=3
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Change log ECSS‐E‐70 Part 1A  25 April 2000  and  ECSS‐E‐70 Part 2A  2 April 2001  First issues  ECSS‐E‐70B  Never issued   ECSS‐E‐ST‐70C  31 July 2008  The present version (ECSS‐E‐ST‐70C) is the evolution of ECSS‐E‐70 Part  1A “Ground systems and operations ‐ Principles and requirement” a...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 3 }
null
ECSS-E-ST-70C(31July2008)-page=4
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  • Harmonization with ECSS‐E‐ST‐10C System engineering  ECSS‐E‐ST‐70C  is  now  consistent  with  the  E‐ST‐10  series  of  standards:  it  makes  cross‐reference  to  E‐ST‐10  processes,  where  applicable  to  the  GS  development.    It  in  general  uses  the  same  terminology for proc...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 4 }
null
ECSS-E-ST-70C(31July2008)-page=5
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table of contents Change log.................................................................................................................3 Introduction..............................................................................................................10 1 Scope................
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 5 }
null
ECSS-E-ST-70C(31July2008)-page=6
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.3.3 Outputs.......................................................................................................35 5.4 Mission operations data validation ...........................................................................35 5.4.1 Inputs.........................................
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 6 }
null
ECSS-E-ST-70C(31July2008)-page=7
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.4.2 Process description ....................................................................................57 6.4.3 Outputs.......................................................................................................60 6.5 Ground segment maintenance ..........................
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 7 }
null
ECSS-E-ST-70C(31July2008)-page=8
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.7.2 Processes during phase F..........................................................................77 7.7.3 Milestones and reviews of phase F ............................................................78 7.8 Summary of key documents and reviews.......................................
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 8 }
null
ECSS-E-ST-70C(31July2008)-page=9
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Tables Table 5-1 Inputs to the requirements analysis and concept development process...............27 Table 5-2: Outputs of the requirements analysis and concept development process............32 Table 5-3: Inputs to the mission operations data production process...........................
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 9 }
null
ECSS-E-ST-70C(31July2008)-page=10
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Introduction Ground systems and operations are key elements of a space system and play an  essential role in achieving mission success. Mission success is defined here as  the  achievement  of  the  target  mission objectives  as expressed in terms  of  the  quantity,  quality  and  availa...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 10 }
null
ECSS-E-ST-70C(31July2008)-page=11
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  1 Scope Within the framework of the overall engineering standards for space missions,  this Standard contains the basic rules, principles and requirements applied to  the engineering of the ground segment and mission operations, which form an  integral part of the overall system implement...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 11 }
null
ECSS-E-ST-70C(31July2008)-page=12
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  2 Normative references The  following  normative  documents  contain  provisions  which,  through  reference  in  this  text,  constitute  provisions  of  this  ECSS  Standard.  For  dated  references, subsequent amendments to, or revision of any of these publications  do not apply, Howev...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 12 }
null
ECSS-E-ST-70C(31July2008)-page=13
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  3 Terms, definitions and abbreviated terms 3.1 Terms defined in other standards For  the  purpose  of  this  Standard,  the  terms  and  definitions  from  ECSS‐S‐ST‐00‐01 apply.  For  the  purpose  of  this  Standard,  the  following  terms  and  definitions  from  ECSS‐E‐ST‐10 apply: ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 13 }
null
ECSS-E-ST-70C(31July2008)-page=14
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  3.2.6 ground system integrated  set  of  ground  functions  used  to  support  the  preparation  activities  leading up to mission operations or the conduct of mission operations itself  3.2.7 incident in  provision  of  a  service,  an  enquiry,  an  observation  or  an  anomaly,  whi...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 14 }
null
ECSS-E-ST-70C(31July2008)-page=15
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  3.2.14 operational validation test  activities  whose  objective  is  to  establish  the  readiness  of  the  complete  ground segment, including mission operations data, and operations personnel  to support the space mission in–orbit by means of simulations and rehearsals  NOTE  The  co...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 15 }
null
ECSS-E-ST-70C(31July2008)-page=16
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  EEPROM  electrically erasable programmable read‐only memory  EGSE  electrical ground support equipment  ELR  end‐of‐life review  EM  engineering model  FAT  factory acceptance testing  FDIR  failure detection, isolation and recovery  FM  flight model  FMEA  failure modes and effects analysi...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 16 }
null
ECSS-E-ST-70C(31July2008)-page=17
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  LIT  listen‐in test  LS  logistic support  LSP  logistics support plan  MAR  mission analysis report  MCR  mission close–out review  MDD  mission description document  MOCD  mission operations concept document  MOP  mission operations plan  MRT  mission readiness tests  OAR  operations anom...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 17 }
null
ECSS-E-ST-70C(31July2008)-page=18
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  SSS  space segment supplier  SSM  space system model  SSUM  space segment user manual  SVT  system validation test  TS  technical specification  TT&C  telemetry, tracking and command  18
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 18 }
null
ECSS-E-ST-70C(31July2008)-page=19
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  4 Ground segment and operations domain 4.1 Overview The domain of ECSS‐E‐ST‐70 is shown in Figure 4‐1 and is composed of two  main components:  • The  ground  segment  comprising  all  ground  systems  that  are  used  to  support the preparation activities leading up to mission operat...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 19 }
null
ECSS-E-ST-70C(31July2008)-page=20
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  • Mission exploitation personnel (e.g. scientific/algorithm experts, end‐user  community liaison staff, product generation support staff);  • Ground systems maintenance engineers.  Team Team System System System System System System Team Team System System System Team OPER...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 20 }
null
ECSS-E-ST-70C(31July2008)-page=21
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  • Simulation;  • Mission planning and scheduling;  • Monitoring and control;  • Flight dynamics;  • On‐board software maintenance and management;  • Data archiving;  • User services;  • Data product delivery;  • Performance analysis and reporting;  • Configuration  management  (sp...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 21 }
null
ECSS-E-ST-70C(31July2008)-page=22
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  • Performance analysis and reporting;  • Algorithm tuning and development, verification and validation;  • System maintenance.  4.3.4 Ground station system The ground station system provides the physical link with the space segment  while in–orbit. The following are supported, where a...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 22 }
null
ECSS-E-ST-70C(31July2008)-page=23
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  4.5 Critical areas In  order  to  cost–effectively  ensure  mission  success,  this  Standard  covers  the  coordination established during the phases of the space system project, between  space and ground segment, and between ground segment entities, as these are  often under different r...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 23 }
null
ECSS-E-ST-70C(31July2008)-page=24
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5 Operations engineering 5.1 Overview Figure 5‐1 shows the main operations engineering processes, which are:  • Requirements analysis and concept development;  • Mission operations data production;  • Mission operations data validation;  • Operations teams build‐up and training;  • ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 24 }
null
ECSS-E-ST-70C(31July2008)-page=25
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Mission Description Document (MDD) Operations Customer Operations Supplier Requirements Analysis and Concept Development Operations Customer Requirements Document (OCRD) Trade-off Report Mission Operations Concept Document (MOCD) Mission Analysis Report (MAR) Launcher User Manual ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 25 }
null
ECSS-E-ST-70C(31July2008)-page=26
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Space Segment Disposal Operations Operations Execution Disposed Space Segment Operational Space Segment Operations Reports Anomaly Reports Operations Customer Disposal Report Mission Operations Experience Reports Mission Products Mission User Community Mission Archives Validated Gro...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 26 }
null
ECSS-E-ST-70C(31July2008)-page=27
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  NOTE 3  The trade‐off report provides a summary of the  different  mission  concepts  considered at  space  system  level,  the  criteria  used  to  assess  them  and the justification for the selected solution.  NOTE 4  The  mission  description  document  and  trade‐ off report are define...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 27 }
null
ECSS-E-ST-70C(31July2008)-page=28
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  NOTE 2  Mission  analysis  also  provides  input  to  the  spacecraft and mission design.  NOTE 3  The  mission  analysis  process  is  carried  out  in  cooperation  with  the  space  segment  supplierʹs  operations team.  b. The mission analysis shall supply the following information:  1...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 28 }
null
ECSS-E-ST-70C(31July2008)-page=29
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.2.2.3 Operational interfaces definition a. Space segment operability requirements shall be identified to ensure that  the  space  segment  can  be  operated  during  nominal  situations  and  foreseeable  contingency  situations,  in  accordance  with  the  mission  requirements  and ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 29 }
null
ECSS-E-ST-70C(31July2008)-page=30
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  3. Provision  of  representative  space  segment  telemetry  and  telecommand data samples (including payload data).  4. Provision  of  suitcase  for  testing  compatibility  between  space  segment TT&C and ground stations.  5. Access to the space segment when on ground, for the validat...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 30 }
null
ECSS-E-ST-70C(31July2008)-page=31
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  2. The mission operations team organisation for both the operations  preparation and operations execution phases.  3. The recruitment profile for the mission operations team, showing  how  staff  are  phased‐in  (and  out)  and  identifying  any  potential  time‐sharing or role‐sharing wi...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 31 }
null
ECSS-E-ST-70C(31July2008)-page=32
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.2.2.6 Operational validation plan production a. An  operational  validation  plan  (OVP)  shall  be  produced  for  the  operational  validation  of  the  ground  segment  systems  and  the  mission  operations data.  b. The OVP shall cover:  1. Test preparation activities.  2. Tec...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 32 }
null
ECSS-E-ST-70C(31July2008)-page=33
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.3 Mission operations data production 5.3.1 Inputs a. The inputs to the mission operations data production process shall be the  ones specified in Table 5‐3.  b. The space segment user manual (SSUM) contents shall conform to Annex  E.  NOTE  The  SSUM  includes  information  used  f...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 33 }
null
ECSS-E-ST-70C(31July2008)-page=34
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  2. The sequence of main mission events for all critical mission phases,  including  ground  stations  visibility  and  major  space  segment  operations;  3. Operations  schedules  for  all  mission  critical  operations  defining  the timed sequence of:  (a) operational  activities  exe...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 34 }
null
ECSS-E-ST-70C(31July2008)-page=35
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  1. the space segment monitoring and control database, and  2. the space segment procedures contained in the SSUM.  k. The contents of the MOP shall be in conformance with Annex G.  l. The  contents  of  operations  procedures  shall  be  in  conformance  with  Annex I.  5.3.3 Outputs ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 35 }
null
ECSS-E-ST-70C(31July2008)-page=36
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.4.2 Process description a. Mission operations data shall be validated.  NOTE 1  The  validation  of  the  mission  operations  data  demonstrates the correctness of the data and its  compatibility with the space segment.  NOTE 2  For  some  data,  verification  by  inspection  is  suff...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 36 }
null
ECSS-E-ST-70C(31July2008)-page=37
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 5‐7: Inputs to the operations teams build‐up and training  process  ID  Title  Mnemonic Provider  1  Mission analysis report   MAR  Operations supplier  2  SSUM  SSUM  Operations customer  3  Mission operations concept  document  MOCD  Operations supplier  4  Mission operations plan  ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 37 }
null
ECSS-E-ST-70C(31July2008)-page=38
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  b. Roles  and  responsibilities  shall  be  defined,  for  each  team  member,  for  each mission phase.  c. The  operations  teams  shall  be  assigned  and  trained  such  that  they  are  familiar with the mission and the supporting facilities before the start of  operational validatio...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 38 }
null
ECSS-E-ST-70C(31July2008)-page=39
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.6.2 Process description a. Operational validation shall take place in a realistic operational context  i.e. through representative operations scenarios supported by operational  simulators, thereby demonstrating:  1. Proper  functioning  and  set–up  of  the  entire  ground  segment  ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 39 }
null
ECSS-E-ST-70C(31July2008)-page=40
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  2. the  results  of  the  tests  and  implementation  of  any  necessary  actions.  NOTE  For  example,  corrections  to  the  space  segment  design or impacts on subsequent activities such  as the repetition of tests.  h. Following  successful  completion  of  the  operational  validat...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 40 }
null
ECSS-E-ST-70C(31July2008)-page=41
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.7.2 Process description a. In  accordance  with  the  requirements  for  “Configuration  management  approach  for  operational  phase”  of  ECSS‐M‐ST‐40,  the  mission  operations  data  shall  be  maintained  in  a  functional  state  and  remain  under  configuration  control  for  ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 41 }
null
ECSS-E-ST-70C(31July2008)-page=42
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.8 Operations execution 5.8.1 Inputs a. The  inputs  to  the  operations  execution  process  shall  be  the  ones  as  specified in Table 5‐13.  Table 5‐13  Inputs to the operations execution process  ID  Description  Provider  1  Fully validated ground segment, including  personnel ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 42 }
null
ECSS-E-ST-70C(31July2008)-page=43
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.8.2.3 Routine mission operations a. Mission  planning  shall  be  performed  in  response  to  end‐user  requests  and the operational and maintenance constraints of the space and ground  segments.  b. Detailed  operations  schedules  shall  be  produced  from  the  mission  planning....
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 43 }
null
ECSS-E-ST-70C(31July2008)-page=44
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  c. A  commissioning  report  shall  be  produced  at  the  end  of  the  in‐orbit  commissioning.  d. Performance reports on the space and ground segments (including trend  analysis) shall be produced at suitable intervals to determine success in  meeting the mission objectives.  NOTE 1  ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 44 }
null
ECSS-E-ST-70C(31July2008)-page=45
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 5‐14: Outputs of the operations execution process  ID  Title  Mnemonic  Producer  1  Space segment elements in their final orbits,  configured for mission exploitation    Operations  supplier  2  LEOP reports    Operations  supplier  3  Commissioning report    Operations  supplier  4 ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 45 }
null
ECSS-E-ST-70C(31July2008)-page=46
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5.9.2 Process description a. The space segment disposal operations process shall include:  1. Disposal operations analyses.  2. Development of products and processes for disposal.  3. Processes validation.  4. Final de–orbiting, ,re–entry or retrieval operations, and  5. Disposal or...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 46 }
null
ECSS-E-ST-70C(31July2008)-page=47
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6 Ground segment engineering 6.1 Overview This clause covers, in particular, the system engineering of the ground segment  and its lower levels.  Figure 6‐1 shows the main ground segment engineering processes which are:  • Ground segment definition, covering:  ⎯ ground segment require...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 47 }
null
ECSS-E-ST-70C(31July2008)-page=48
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Ground Segment Definition Ground Segment Production System Z System Y System Z System Y Ground Segment Customer Requirements Document (GSCRD) Ground Segment Supplier Ground Segment Customer Operations Supplier Ground Segment Engineering Plan (GSEP) System X Rqts Document & ICDs Ground ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 48 }
null
ECSS-E-ST-70C(31July2008)-page=49
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.2 Ground segment definition 6.2.1 Inputs a. The  inputs  to  the  ground  segment  definition  process  shall  be  the  ones  identified in Table 6‐1.  b. The  contents  of  the  ground  segment  customer  requirements  document  (GSCRD) shall conform to Annex A.  NOTE 1  The  GSCR...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 49 }
null
ECSS-E-ST-70C(31July2008)-page=50
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  NOTE 2  This also includes user requirements produced  by the operations supplier (see clause 5.2.2.5).  b. Requirements addressing the following topics shall be included:  1. functionality;  2. performance of the ground segment derived from the overall space  system requirements;  3. d...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 50 }
null
ECSS-E-ST-70C(31July2008)-page=51
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  c. The  architecture  shall  cover  integrated  logistics  support  systems  in  accordance  with  the  “Requirements  for  control  of  logistic  activities”  of  ECSS‐M‐ST‐70.   d. The verification and validation approach and associated tools and data  shall be defined.  e. Ground segm...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 51 }
null
ECSS-E-ST-70C(31July2008)-page=52
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  NOTE 3  This also includes user requirements produced  by the operations supplier (see clause 5.2.2.5).  b. Requirements of at least the following categories shall be covered :  1. Functional;  2. Performance;  3. Interface;  4. Design;  5. Operational;  6. Environment;  7. Resource...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 52 }
null
ECSS-E-ST-70C(31July2008)-page=53
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  d. The logistics support plan shall identify the available or shared resources  that  can  be  deployed  in  support  of  the  mission  and  those  that  are  procured for the mission.  6.2.3 Outputs a. The outputs of the ground segment definition process shall be the ones  specified in...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 53 }
null
ECSS-E-ST-70C(31July2008)-page=54
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.3 Ground segment production 6.3.1 Inputs a. The inputs to the ground segment production process shall be the ones  specified in Table 6‐3.  Table 6‐3  Inputs to the ground segment production process  ID  Title  Mnemonic Provider  1  Ground segment engineering plan  GSEP  Ground segme...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 54 }
null
ECSS-E-ST-70C(31July2008)-page=55
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  NOTE 3  In the context of the complete ground segment  (i.e.  all  ground  systems  fully  integrated),  the  ground segment  supplier is  responsible  for all  constituent  ground  systems  vis‐à‐vis  both  the  ground  segment  customer  and  the  operations  supplier.  NOTE 4  Appropriat...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 55 }
null
ECSS-E-ST-70C(31July2008)-page=56
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 6‐4: Outputs of the ground segment production process  ID  Description  Producer  1  Qualified ground systems  Ground system suppliers  2  Acceptance reports for each ground system  Ground system customer  3  User manuals for each ground system  Ground system suppliers  4  Maintenance...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 56 }
null
ECSS-E-ST-70C(31July2008)-page=57
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.4.2 Process description 6.4.2.1 General a. The ground segment AIT activity shall:  1. Be performed using a preliminary set of mission operations data.  2. Be carried out in an incremental manner, starting from low‐level  subsystems up to ground segment level, including at each stag...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 57 }
null
ECSS-E-ST-70C(31July2008)-page=58
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  shown  in  Figure  6‐2,  ground  segment  operational  validation,  is  part  of  operations  engineering (see clause 5.6) but is included here  to give an overall view of the entire approach.  Figure 6‐2: Ground segment AIT and verification  6.4.2.2 Ground segment AIT a. Ground segmen...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 58 }
null
ECSS-E-ST-70C(31July2008)-page=59
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  (b) the sequence in which the individual systems are integrated,  taking account of expected readiness;  (c) the use of test systems or simulators;  (d) the integration with individual external elements;  (e) the  relationship  between  these  tests  and  planned  pre– releases of the s...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 59 }
null
ECSS-E-ST-70C(31July2008)-page=60
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  d. For the space‐to‐ground compatibility tests, at least two periods shall be  provided of a duration that is commensurate with the complexity of the  space segment and with an interval between them allowing correction of  potential ground segment problems found during the first period of ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 60 }
null
ECSS-E-ST-70C(31July2008)-page=61
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.5 Ground segment maintenance 6.5.1 Inputs a. The inputs to the ground segment maintenance process shall be the ones  specified in Table 6‐7  Table 6‐7: Inputs to the ground segment maintenance process  ID  Title  Mnemonic  Provider  1  Ground segment requirements  document  GSRD  Gr...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 61 }
null
ECSS-E-ST-70C(31July2008)-page=62
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.5.2.2 Process description a. Regular performance monitoring shall be undertaken in order to identify  trends or degradations indicating the need for preventive maintenance  b. Performance monitoring results shall be recorded in performance reports.  c. Routine  maintenance  shall  be...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 62 }
null
ECSS-E-ST-70C(31July2008)-page=63
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  6.5.3 Outputs a. The  outputs  of  the  maintenance  process  shall  be  the  ones  specified  in  Table 6‐8.  Table 6‐8  Outputs of the maintenance process  ID  Description  Producer  1  Performance reports  Ground segment supplier   2  Maintenance logs  Ground segment supplier  3  Inci...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 63 }
null
ECSS-E-ST-70C(31July2008)-page=64
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  ensure  mission  termination  without  degradation to the environment.  b. Disposal analysis shall cover methods for storage, dismantling, reusing,  recycling and destruction of the ground segment.   c. The disposal analysis shall cover cost and organization of the disposal.  d. Mission ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 64 }
null
ECSS-E-ST-70C(31July2008)-page=65
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  65  7 Ground segment and operations lifecycle 7.1 General 7.1.1 The lifecycle In  accordance  with  the  ECSS  life  cycle  defined  in  ECSS‐M‐ST‐10,  the  ground  segment  engineering  processes  are  allocated  to  phases,  which  proceed  in  sequence and each of which ends in a f...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 65 }
null
ECSS-E-ST-70C(31July2008)-page=66
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  66  Figure 7‐1: Ground segment and operations phases
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 66 }
null
ECSS-E-ST-70C(31July2008)-page=67
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.1.2 General requirements a. The GSC, the OC, the GSS and the OS shall be represented in the ground  segment and operations reviews.  b. Ground  segment  reviews  and  operations  reviews  should  be  combined  wherever practical.   NOTE  In particular where the GSS and OS are part of...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 67 }
null
ECSS-E-ST-70C(31July2008)-page=68
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 7‐1: Processes and outputs of phase A  ID  Ground Segment  Engineering  Operations  Engineering  Outputs  Reviews  1    Mission analysis  (clause 5.2.2.1)  Draft issue of mission analysis  report (MAR) covering the  various proposed solutions, see  Annex C  CRR  2    Operational  anal...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 68 }
null
ECSS-E-ST-70C(31July2008)-page=69
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.3.2 Processes during phase B a. The main processes specified Table 7‐2 shall be carried out during phase B.  Table 7‐2: Processes and outputs of phase B  ID  Ground Segment  Engineering  Operations  Engineering  Outputs  Reviews  1  Ground segment  requirements engineering  (clause 6.2...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 69 }
null
ECSS-E-ST-70C(31July2008)-page=70
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.3.3 Milestones and reviews of phase B a. A  ground  segment  system  requirements  review  (GSSRR)  shall  be  held  during phase B.  b. The  purpose  of  the  GSSRR  shall  be  to  approve  the  ground  segment  requirements  such  that  preliminary  design  and  the  definition  of ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 70 }
null
ECSS-E-ST-70C(31July2008)-page=71
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 7‐3: Processes and outputs of phase C  Ground Segment  Engineering  Operations  Engineering  ID  Outputs  Reviews  1  Ground segment  requirements  engineering (clause    Inputs to space–to–ground interface  control document (SGICD) in final  version  GSCDR  6.2.2.2)  2  Ground segmen...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 71 }
null
ECSS-E-ST-70C(31July2008)-page=72
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.5 Phase D: Production, AIT and verification 7.5.1 Purpose of phase D The purpose of the phase is to procure all ground systems and to integrate them  into an operational ground segment ready to support the in–orbit operations and  exploitation of the space segment.  7.5.2 Processes d...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 72 }
null
ECSS-E-ST-70C(31July2008)-page=73
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 7‐4: Processes and outputs of phase D  Ground  Segment  Engineering  Operations  Engineering  ID  Outputs  Reviews  1    Mission analysis  (clause  Mission analysis report (MAR) in final  version  GSQR  5.2.2.1)  Qualified ground systems     Test and training tools    2  Qualification...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 73 }
null
ECSS-E-ST-70C(31July2008)-page=74
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.5.3 Milestones and reviews of phase D a. Phase D shall be subdivided into four main sub‐phases (see Figure 7‐1) as  follows:  1. Ground segment production.  NOTE  This  activity  concentrates  on  the  production  and  procurement of the ground systems.  2. Ground segment AIT and ve...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 74 }
null
ECSS-E-ST-70C(31July2008)-page=75
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  5. Authorize  use  of  the  ground  segment  for  space  segment  in–orbit  operations.  NOTE  The  ORR  normally  also  constitutes  the  final  acceptance of the ground segment.  i. The results of the ORR shall be presented at the flight readiness review (FRR).  NOTE  For project phas...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 75 }
null
ECSS-E-ST-70C(31July2008)-page=76
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 7‐5: Processes and outputs of sub‐phase E1  Ground Segment  Engineering  ID  Operations Engineering  Outputs  Reviews  1    LEOP operations (clause  5.8.2.2)  Space segment elements in their  final orbits and configured for  commissioning operations;  FQR  LEOP report  2    Commission...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 76 }
null
ECSS-E-ST-70C(31July2008)-page=77
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  7.6.3 Milestones and reviews of phase E a. Phase E1 shall be concluded by the flight qualification review (FQR). This  review  shall  be  held  after  completion  of  the  space  segment  in–orbit  commissioning,  in  order  to  assess  performance  of  the  space  and  ground  segments ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 77 }
null
ECSS-E-ST-70C(31July2008)-page=78
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  78  7.7.3 Milestones and reviews of phase F a. Phase F shall be concluded by the mission close–out review (MCR).  b. The purpose of the MCR shall be to assess the performance of the services  provided and to confirm proper disposal of space and ground segments.  7.8 Summary of key docu...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 78 }
null
ECSS-E-ST-70C(31July2008)-page=79
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  79  Table 7‐8: Key ground segment and operations documents and reviews at which they are deliverable  Domain Type Title Mnemonic Reference CRR GSSRR GSPDR GSCDR GSQR COR ORR FRR FQR IOOR ELR MCR SSYS MISC Mission description document MDD ECSS-E-ST-10 A ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 79 }
null
ECSS-E-ST-70C(31July2008)-page=80
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Domain Type Title Mnemonic Reference GSCDR GSPDR GSSRR GSQR IOOR MCR COR ORR CRR FQR ELR FRR OPS MISC Mission operations concept document MOCD Annex D P F F OPS SPEC Operations engineering plan OEP Annex E P F OPS PLAN ...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 80 }
null
ECSS-E-ST-70C(31July2008)-page=81
ECSS-E-ST-70C(31July2008)
ECSS‐E‐ST‐70C  31 July 2008  Table 7‐9: Ground segment and operations reviews  Review ID Review title  Review objective  Date  Chaired by  Customer requirements  review  To assess the completeness of the customer requirements  and review the draft operations concept and ground  segment baseline  End of phase A  Operati...
{ "document_id": "ECSS-E-ST-70C(31July2008)", "page_number": 81 }
null