Document Contents Guideline - EMITS Invitation To Tender …emits.sso.esa.int/emits-doc/EarthCARE-DCG-issue-1.pdf · · 2010-01-132 Document Contents Guideline ... Atlid Performance

Doc. No: EC-RS-ESA-SY-0006Issue: issue 1 Date: 02 February 2007 Page: 1 of 329

Prepared by EarthCARE Team Checked by D.Spence Approved by A. Lefebvre

EarthCARE Project Document Contents Guidelines for Phases B, C/D, E1

ESTEC Noordwijk

The Netherlands


DOCUMENT CHANGE RECORD

ISSUE/REV.

DATE

AFFECTED PAGES

1

02 February 2007

EarthCARE ITT Release


1 Applicable Documents .........................................................................................................................10 1.1 Documents applicable to this DCG...........................................................................................................10

2 Document Contents Guideline.............................................................................................................11 2.1 AOCS Related Documents ........................................................................................................................11

2.1.1 D-AO1 - AOCS and Propulsion Specifications....................................................................................................11 2.1.2 D-AO2 - AOCS Design Report ............................................................................................................................12 2.1.3 D-AO3 - AOCS Databank Document ..................................................................................................................13

2.2 Simulator Related Documents ..................................................................................................................14 2.2.1 D-AS1 - Requirements for ESSS and ECGP........................................................................................................14 2.2.2 D-AS2 - Architecture of ESSS and ECGP ...........................................................................................................15 2.2.3 D-AS3 - ESSS and ECGP Description.................................................................................................................16 2.2.4 D-AS4 - ESSS and ECGP User Manual...............................................................................................................17 2.2.5 D-AS5 - ESSS and ECGP Computing Resources Requirements .........................................................................18 2.2.6 D-AS6 - ESSS and ECGP ICDs ...........................................................................................................................19

2.3 ATLID Related Documents.......................................................................................................................20 2.3.1 D-AT1 - Atlid Requirements Specification ..........................................................................................................20 2.3.2 D-AT2 - Atlid ICDs..............................................................................................................................................21 2.3.3 D-AT3 - Atlid Performance Model Description and Predictions .........................................................................22 2.3.4 D-AT4 - Atlid Ground Calibration Facilities Specification .................................................................................23 2.3.5 D-AT5 - ATLID Design, Development and Verification Plan.............................................................................24 2.3.6 D-AT6 - Atlid AIV Plan.......................................................................................................................................25 2.3.7 D-AT7 - Atlid Technical Description...................................................................................................................26 2.3.8 D-AT8 - Atlid Ground Calibration Facilities Description Test and Calibration Report.......................................27 2.3.9 D-AT9 - Atlid Instrument Budgets.......................................................................................................................28 2.3.10 D-AT10 - Atlid Calibration and Characterization Data Base. ..............................................................................29 2.3.11 D-AT11 - Atlid IOV plan .....................................................................................................................................30 2.3.12 D-AT12 - Atlid Flight Operation Manual. ...........................................................................................................31 2.3.13 D-AT13 - Atlid GSE Specification. .....................................................................................................................32 2.3.14 D-AT14 - Atlid GSE Design Report ....................................................................................................................33 2.3.15 D-AT15 – ATLID ESSS and ECGP Design, Development and Verification Plans.............................................34 2.3.16 D-AT16 – ATLID ESSS and ECGP Module Specifications................................................................................35 2.3.17 D-AT17 - Atlid Level 1b Product Definition .......................................................................................................36 2.3.18 D-AT18 - Atlid Level 0 Product Definition .........................................................................................................37 2.3.19 D-AT19 – ATLID ESSS and ECGP Users Manuals ............................................................................................38 2.3.20 D-AT20 – ATLID Algorithms Theoretical Baseline Document ..........................................................................39 2.3.21 D-AT21 – ATLID ECGP Reference Test Data Set Description ..........................................................................40 2.3.22 D-AT22 – ATLID SRR Data Package .................................................................................................................41 2.3.23 D-AT23 – ATLID PDR Data Package .................................................................................................................42 2.3.24 D-AT24 – ATLID CDR Data Package.................................................................................................................43 2.3.25 D-AT25 – ATLID QR Data Package ...................................................................................................................44 2.3.26 D-AT26 – ATLID AR Data Package ...................................................................................................................45 2.3.27 D-AT27 – ATLID Master Planning .....................................................................................................................46 2.3.28 D-AT28 – ATLID Risk Analysis .........................................................................................................................47 2.3.29 D-AT29 – ATLID Long Lead Items List .............................................................................................................48

2.4 AIV Related Documents ............................................................................................................................49 2.4.1 D-AV1 - AIV/AIT Plan........................................................................................................................................49 2.4.2 D-AV2 - Facilities, Logistics and Transportation Plan ........................................................................................50 2.4.3 D-AV3 - H/W S/W Procurement Items Matrix ....................................................................................................51 2.4.4 D-AV4 - Test Specifications ................................................................................................................................52 2.4.5 D-AV5 - Verification Matrix................................................................................................................................53 2.4.6 D-AV6 - Satellite Design, Development and Verification Plan ...........................................................................54 2.4.7 D-AV7 - Test Block Plans....................................................................................................................................55 2.4.8 D-AV8 - AIT Procedures .....................................................................................................................................56


2.4.9 D-AV9 - Verification Control Document.............................................................................................................57 2.4.10 D-AV10 - Launch Operations Procedures............................................................................................................58 2.4.11 D-AV11 - Launch Operations Plan ......................................................................................................................59 2.4.12 D-AV12 - GSE Requirements Specifications.......................................................................................................60 2.4.13 D-AV13 - Launch Campaign Staffing and Logistics Plans..................................................................................61 2.4.14 D-AV14 - Waterfall Schedule for AIT.................................................................................................................62 2.4.15 D-AV15 – Characterization / Calibration Plan.....................................................................................................63 2.4.16 D-AV16 - Test Reports ........................................................................................................................................64 2.4.17 D-AV17 - Ground Operations Constraints ...........................................................................................................65 2.4.18 D-AV18 - Alignment Plan and Procedure............................................................................................................66 2.4.19 D-AV19 – Generic Front End Data Processing Specification..............................................................................67 2.4.20 D-AV20 – EGSE Internal Electrical Interface Specification................................................................................68 2.4.21 D-AV21 – Instrument and Satellite to Facilities ICDs .........................................................................................69 2.4.22 D-AV22 – EGSE Requirements Specification .....................................................................................................70

2.5 BBR Instrument Related Documents .......................................................................................................71 2.5.1 D-BB1 - BBR Requirements Specification ..........................................................................................................71 2.5.2 D-BB2 - BBR ICDs..............................................................................................................................................72 2.5.3 D-BB3 - BBR Performance Model Description and Predictions .........................................................................73 2.5.4 D-BB4 - BBR Ground Calibration Facilities Specification..................................................................................74 2.5.5 D-BB5 - BBR Design, Development and Verification Plan.................................................................................75 2.5.6 D-BB6 - BBR AIV Plan .......................................................................................................................................76 2.5.7 D-BB7 - BBR Technical Description ...................................................................................................................77 2.5.8 D-BB8 - BBR Ground Calibration Facilities Description, Test and Calibration Report ......................................78 2.5.9 D-BB9 - BBR Instrument Budgets .......................................................................................................................79 2.5.10 D-BB10 - BBR. Calibration and Characterization Data Base ..............................................................................80 2.5.11 D-BB11 - BBR IOV plan .....................................................................................................................................81 2.5.12 D-BB12 - BBR Flight Operation Manual.............................................................................................................82 2.5.13 D-BB13 - BBR GSE Specification.......................................................................................................................83 2.5.14 D-BB14 - BBR GSE Design Report.....................................................................................................................84 2.5.15 D-BB15 – BBR ESSS and ECGP Design, Development and Verification Plans.................................................85 2.5.16 D-BB16 - BBR ESSS and ECGP Module Specifications ....................................................................................86 2.5.17 D-BB17 - BBR Level 1b Product Definition .......................................................................................................87 2.5.18 D-BB18 - BBR Level 0 Product Definition .........................................................................................................88 2.5.19 D-BB19 – BBR ESSS and ECGP Users Manuals................................................................................................89 2.5.20 D-BB20 – BBR Algorithms Theoretical Baseline Document ..............................................................................90 2.5.21 D-BB21 – BBR ECGP Reference Test Data Set Description ..............................................................................91 2.5.22 D-BB22 – BBR SRR Data Package .....................................................................................................................92 2.5.23 D-BB23 – BBR PDR Data Package .....................................................................................................................93 2.5.24 D-BB24 – BBR CDR Data Package.....................................................................................................................94 2.5.25 D-BB25 – BBR QR Data Package .......................................................................................................................95 2.5.26 D-BB26 – BBR AR Data Package .......................................................................................................................96 2.5.27 D-BB27 – BBR Master Planning .........................................................................................................................97 2.5.28 D-BB28 – BBR Risk Analysis .............................................................................................................................98 2.5.29 D-BB29 – BBR Long Lead Items List .................................................................................................................99 2.5.30 D-BB30 – BBR Straylight Analysis ...................................................................................................................100

2.6 Commissioning Related Documents .......................................................................................................101 2.6.1 D-CM1 - In-Orbit Calibration and Verification Procedure ................................................................................101 2.6.2 D-CM2 - In-Orbit Verification Plan ...................................................................................................................102 2.6.3 D-CM3 – Inputs to CAL / VAL Plan .................................................................................................................103

2.7 Communications Related Documents.....................................................................................................104 2.7.1 D-CO1 – Communication & RF Subsystem Design Requirements Specification .............................................104 2.7.2 D-CO2 - RF Suitcase Design Report..................................................................................................................105 2.7.3 D-CO3 – S / X Band, Ground Station and Link Budget Analysis......................................................................106

2.8 CPR Instrument Related Documents .....................................................................................................107 2.8.1 D-CP1 - CPR ICD ..............................................................................................................................................107 2.8.2 D-CP2 – CPR specific Documentation...............................................................................................................108


2.9 Data Handling Related Documents ........................................................................................................109 2.9.1 D-DH1 – C&C and Science Data Interface Requirements Specifications .........................................................109 2.9.2 D-DH2 - Data Handling Analyses......................................................................................................................110

2.10 Data Processor Related Documents ....................................................................................................111 2.10.1 D-DP1 - Satellite In Orbit Verification Tool (SIOVT) Specification.................................................................111 2.10.2 D-DP2 – ESSS and ECGP Reference Data Set Description Documents............................................................112

2.11 Electrical Subsystem Related Documents ..........................................................................................113 2.11.1 D-EL1 - Satellite Electrical Design Requirements Specification .......................................................................113 2.11.2 D-EL2 – EMC / ESD /RFC Design and Test Requirements ..............................................................................114 2.11.3 D-EL3 – EMC / ESD Control Plan ....................................................................................................................115 2.11.4 D-EL4 - Satellite Level Grounding Diagram .....................................................................................................116 2.11.5 D-EL5 – EMC / Magnetic / ESD / RFC Analysis ..............................................................................................117 2.11.6 D-EL6 - EarthCARE Frequency Plan.................................................................................................................118 2.11.7 D-EL7 – EarthCARE Harness and Test Harness Specification..........................................................................119

2.12 Operations Support Related Documents ............................................................................................120 2.12.1 D-ES1 - Satellite Mission Analysis ....................................................................................................................120 2.12.2 D-ES2 - Satellite Operations Constraints ...........................................................................................................123 2.12.3 D-ES3 - Satellite Operations Timeline ...............................................................................................................124 2.12.4 D-ES4 - Satellite Operability Report..................................................................................................................125 2.12.5 D-ES5 - RF Suitcase Operations Manual ...........................................................................................................126 2.12.6 D-ES6 - Flight Operations Manual.....................................................................................................................127 2.12.7 D-ES7 - SRDB ICD............................................................................................................................................130 2.12.8 D-ES8 - ICD for Onboard Software Delivery ....................................................................................................131 2.12.9 D-ES9 - ICD for HK Telemetry Delivery ..........................................................................................................132 2.12.10 D-ES10 – Flight Dynamics ICD.....................................................................................................................133 2.12.11 D-ES11 - EarthCARE Space to Ground Data ICD.........................................................................................134 2.12.12 D-ES12 - EarthCARE Space to Ground RF ICD ...........................................................................................135 2.12.13 D-ES14 - Flight Procedures ICD....................................................................................................................136 2.12.14 D-ES15 – SRDB Specification.......................................................................................................................137 2.12.15 D-ES16 – SRDB-A and SRDB-B Description ...............................................................................................138 2.12.16 D-ES17 – LEOP Plan and LEOP Operation Timeline ...................................................................................139 2.12.17 D-ES18 – LEOP and IOV Report...................................................................................................................140

2.13 Launcher Interface Related Documents.............................................................................................141 2.13.1 D-LA1 - Launcher Survey Document ................................................................................................................141 2.13.2 D-LA2 - EarthCARE Spacecraft to Launcher IRD (Dnepr)...............................................................................142 2.13.3 D-LA3 - EarthCARE Spacecraft to Launcher IRD (ROCKOT) ........................................................................143 2.13.4 D-LA4 - EarthCARE Spacecraft to Launcher IRD (Soyuz)...............................................................................144 2.13.5 D-LA5 - EarthCARE Spacecraft to Launcher IRD (VEGA)..............................................................................145

2.14 Management Related Documents........................................................................................................146 2.14.1 D-MA2 - Sub-Contractor Procurement Packages ..............................................................................................146 2.14.2 D-MA3 - Industrial Procurement Plan ...............................................................................................................147 2.14.3 D-MA4 - Long Lead Items List..........................................................................................................................148

2.15 Mechanism Related Documents ..........................................................................................................149 2.15.1 D-ME1 - Mechanism Design and Performance Requirements Specification.....................................................149 2.15.2 D-ME2 - Mechanism Description Report...........................................................................................................150 2.15.3 D-ME3 - Mechanisms Analysis Report..............................................................................................................151 2.15.4 D-ME4 - Mechanisms Test Assessment Report .................................................................................................152

2.16 Mission Analysis Related Documents .................................................................................................153 2.16.1 D-MI1 - Mission and Operations Definition ......................................................................................................153

2.17 MSI Instrument Related Documents ..................................................................................................154 2.17.1 D-MS1 - MSI Requirements Specification.........................................................................................................154 2.17.2 D-MS2 - MSI ICDs ............................................................................................................................................155 2.17.3 D-MS3 - MSI Performance Model Description and Predictions........................................................................156


2.17.4 D-MS4 - MSI Ground Calibration Facilities Specification ................................................................................157 2.17.5 D-MS5 - MSI Design, Development and Verification Plan ...............................................................................158 2.17.6 D-MS6 - MSI AIV Plan .....................................................................................................................................159 2.17.7 D-MS7 - MSI Technical Description .................................................................................................................160 2.17.8 D-MS8 - MSI Ground Calibration Facilities Description, Test and Calibration Report ....................................161 2.17.9 D-MS9 - MSI Instrument Budgets .....................................................................................................................162 2.17.10 D-MS10 - MSI Calibration and Characterization Data Base..........................................................................163 2.17.11 D-MS11 - MSI IOV Plan ...............................................................................................................................164 2.17.12 D-MS12 - MSI Flight Operation Manual .......................................................................................................165 2.17.13 D-MS13 - MSI GSE Specification .................................................................................................................166 2.17.14 D-MS14 - MSI GSE Design Report ...............................................................................................................167 2.17.15 D-MS15 – MSI ESSS and ECGP Design, Development and Verification Plans ...........................................168 2.17.16 D-MS16 - MSI ESSS and ECGP Module Specifications...............................................................................169 2.17.17 D-MS17 - MSI Level 1 Product Definition ....................................................................................................170 2.17.18 D-MS18 - MSI Level 0 Product Definition ....................................................................................................171 2.17.19 D-MS19 - MSI ESSS and ECGP Users Manuals ...........................................................................................172 2.17.20 D-MS20 – MSI Algorithms Theoretical Baseline Document.........................................................................173 2.17.21 D-MS21 – MSI ECGP Reference Test Data Set Description.........................................................................174 2.17.22 D-MS22 – MSI SRR Data Package................................................................................................................175 2.17.23 D-MS23 – MSI PDR Data Package................................................................................................................176 2.17.24 D-MS24 – MSI CDR Data Package ...............................................................................................................177 2.17.25 D-MS25 – MSI QR Data Package..................................................................................................................178 2.17.26 D-MS26 – MSI AR Data Package..................................................................................................................179 2.17.27 D-MS27 – MSI Master Planning....................................................................................................................180 2.17.28 D-MS28 – MSI Risk Analysis........................................................................................................................181 2.17.29 D-MS29 – MSI Long Lead Items List............................................................................................................182 2.17.30 D-MS30 – MSI Straylight Analysis ...............................................................................................................183

2.18 Product Assurance Related Documents .............................................................................................184 2.18.1 D-PA1 - Product Assurance and Safety Plan......................................................................................................184 2.18.2 D-PA3 – Configuration Management Plan.........................................................................................................185 2.18.3 D-PA4 - Plan of External & Internal PA & Safety Audits .................................................................................186 2.18.4 D-PA5 - Audit Report ........................................................................................................................................187 2.18.5 D-PA6 - Critical Items List (CIL) ......................................................................................................................188 2.18.6 D-PA7 - Non-Conformance Report....................................................................................................................189 2.18.7 D-PA8 - Waiver/Deviation Requests..................................................................................................................190 2.18.8 D-PA9 - Cleanliness and Contamination Control Plan.......................................................................................191 2.18.9 D-PA10 - Qualification Status List.....................................................................................................................192 2.18.10 D-PA11 - Reliability Prediction Report .........................................................................................................193 2.18.11 D-PA12 - Failure Mode Effect Criticality Analysis (FMECA)......................................................................194 2.18.12 D-PA13 - Availability Analysis and Prediction .............................................................................................196 2.18.13 D-PA14 - Cleanliness Requirement Specification..........................................................................................197 2.18.14 D-PA15 - System and Operations Hazard Analysis .......................................................................................198 2.18.15 D-PA16 - Software Product Assurance File ...................................................................................................199 2.18.16 D-PA17 - Software Maintenance File ............................................................................................................200 2.18.17 D-PA18 - Request for Approval .....................................................................................................................201 2.18.18 D-PA19 - Parts Approval Document (PAD) ..................................................................................................202 2.18.19 D-PA20 - Software Criticality Analysis Report .............................................................................................203 2.18.20 D-PA21 - Destructive Physical Analysis (DPA) reports ................................................................................204 2.18.21 D-PA22 - Declared Component List (DCL)...................................................................................................205 2.18.22 D-PA23 - Radiation Analysis Report .............................................................................................................206 2.18.23 D-PA24 - Certificate of Qualification ............................................................................................................207 2.18.24 D-PA25 - Certificate of Conformity...............................................................................................................208 2.18.25 D-PA26 - Declared Mechanical Parts List (DMPL).......................................................................................209 2.18.26 D-PA27 - Declared Material List (DML).......................................................................................................210 2.18.27 D-PA28 - Declared Process List (DPL)..........................................................................................................211 2.18.28 D-PA29 – Manufacturing and Inspection Flow Chart / MIP/KIP List ...........................................................212 2.18.29 D-PA30 - End Item Data package (EIDP)......................................................................................................213 2.18.30 D-PA31 - Safety Data Package ......................................................................................................................215


2.18.31 D-PA32 - Accident / Incident Investigation Reports......................................................................................216 2.18.32 D-PA33 - Configuration Items Data List (CIDL)...........................................................................................217 2.18.33 D-PA34 - Parts Derating Analysis Report......................................................................................................218 2.18.34 D-PA35 - Maintainability Report ...................................................................................................................219 2.18.35 D-PA36 - Alert, Warning Note and Problem Notification Status List ...........................................................220 2.18.36 D-PA37 - Component Procurement Specification..........................................................................................221 2.18.37 D-PA38 - Fracture Critical Item List..............................................................................................................222 2.18.38 D-PA39 - Safety Certificates..........................................................................................................................223 2.18.39 D-PA40 - Request for Waivers/ Request for Deviations Status List ..............................................................224 2.18.40 D-PA41 - Fracture Control Plan.....................................................................................................................225 2.18.41 D-PA42 – Contingency Analysis ...................................................................................................................226 2.18.42 D-PA43 – Worst Case Analysis .....................................................................................................................227

2.19 Project Management Related Documents ..........................................................................................228 2.19.1 D-PM1 – Industrial Project Management Plan...................................................................................................228 2.19.2 D-PM2 – Dictionary of Acronyms and Abbreviations .......................................................................................229 2.19.3 D-PM3 – Project Directory ................................................................................................................................230 2.19.4 D-PM4 – Risk Management Plan.......................................................................................................................231 2.19.5 D-PM5 – Risk Register ......................................................................................................................................232 2.19.6 D-PM6 – Product Tree (PT) ...............................................................................................................................233 2.19.7 D-PM7 – Work Breakdown Structure (WBS)....................................................................................................234 2.19.8 D-PM9 – Contract Structure (CS) ......................................................................................................................235 2.19.9 D-PM10 – Project Organisation Breakdown Structure (POBS).........................................................................236 2.19.10 D-PM11 – Payment Status & Forecast Report ...............................................................................................237 2.19.11 D-PM12 - Schedule Reporting .......................................................................................................................238 2.19.12 D-PM13 - Progress Report .............................................................................................................................239 2.19.13 D-PM14 - Milestone Payment Plans and Status.............................................................................................240 2.19.14 D-PM15 - Geographical Distribution of Work (GDW)..................................................................................241 2.19.15 D-PM16 - Contract Change Notices (CCN)...................................................................................................242 2.19.16 D-PM17 - Contract Change Notices Status List .............................................................................................243 2.19.17 D-PM18 - Work Package Description............................................................................................................244 2.19.18 D-PM19 - Document Change Requests (DCR) / Notes (DCN)......................................................................245 2.19.19 D-PM20 - Documentation Management Plan ................................................................................................246 2.19.20 D-PM21 - Document Status List ....................................................................................................................247 2.19.21 D-PM22 - Contractors DRL ...........................................................................................................................248 2.19.22 D-PM23 - Inventory Record...........................................................................................................................249 2.19.23 D-PM24 - Meeting Schedule..........................................................................................................................250 2.19.24 D-PM25 - Minutes of Meeting .......................................................................................................................251 2.19.25 D-PM26 - Action Item Status List..................................................................................................................252 2.19.26 D-PM27 - End of Project Assessment and Contract Close-Out .....................................................................253 2.19.27 D-PM28 - Inventory Control Plan ..................................................................................................................254

2.20 Review Related Documents..................................................................................................................255 2.20.1 D-PR1 - Satellite Review Procedure ..................................................................................................................255 2.20.2 D-PR2 - Subsystem Review Procedure ..............................................................................................................256

2.21 Satellite Related Documents ................................................................................................................257 2.21.1 D-SA1 - Satellite Design Specification ..............................................................................................................257 2.21.2 D-SA2 - Subsystem and Unit Requirement Specifications ................................................................................258 2.21.3 D-SA3 - Design Justification File ......................................................................................................................259 2.21.4 D-SA4 - Review of “Off the Shelf” S/S and Unit Hardware..............................................................................260 2.21.5 D-SA5 – EarthCARE FDIR Definition and Implementation Report .................................................................261 2.21.6 D-SA6 - Satellite Budget Document ..................................................................................................................262 2.21.7 D-SA7 - Documentation Tree.............................................................................................................................263 2.21.8 D-SA8 - Satellite Internal Interface Control Documents....................................................................................264 2.21.9 D-SA9 - Design Definition File..........................................................................................................................265 2.21.10 D-SA9–1 - Satellite System Technical Description........................................................................................266 2.21.11 D-SA9–2 - SRR Package................................................................................................................................267 2.21.12 D-SA10 - PDR Package .................................................................................................................................268


2.21.13 D-SA11 - CDR Package.................................................................................................................................269 2.21.14 D-SA12 - QR Package....................................................................................................................................270 2.21.15 D-SA13 - AR Package....................................................................................................................................271 2.21.16 D-SA14 - IOCR Package................................................................................................................................272 2.21.17 D-SA15 - Subsystem Qualification Reports...................................................................................................273 2.21.18 D-SA16 - Subsystem Acceptance Reports .....................................................................................................274 2.21.19 D-SA17 - Overall Assembly and Geometrical Drawings...............................................................................275 2.21.20 D-SA18 - Mechanical Drawings ....................................................................................................................276 2.21.21 D-SA19 - Electrical Drawings and Synoptics ................................................................................................277 2.21.22 D-SA19-1 – Harness Routing.........................................................................................................................278 2.21.23 D-SA20 - Thermal Drawings .........................................................................................................................279 2.21.24 D-SA21 - Unit Circuit Diagrams....................................................................................................................280 2.21.25 D-SA22 - Switching Diagrams and Synoptics ...............................................................................................281 2.21.26 D-SA23 - Satellite IOV Plan and Procedures.................................................................................................282 2.21.27 D-SA24 – Satellite Calibration and Characterization Database .....................................................................283 2.21.28 D-SA25 – Elements of Manufacturing Dossier ..............................................................................................284 2.21.29 D-SA26 – Pointing, Alignment, Instrument Co-Registration and Geo-location Requirement Analysis ........285 2.21.30 D-SA27 – Pointing, Alignment and Instrument Co-Registration and Geo-location Description and Implementation...................................................................................................................................................................286 2.21.31 D-SA28 – EarthCARE EFM Specification ....................................................................................................287

2.22 Structure Related Documents..............................................................................................................288 2.22.1 D-ST1 - Satellite Mechanical Design Requirements Specification ....................................................................288 2.22.2 D-ST2 - Satellite Environmental Design and Test Requirements Specification ................................................289 2.22.3 D-ST3 - Structural Description Report...............................................................................................................290 2.22.4 D-ST4 - Preliminary FEM Description Reports .................................................................................................291 2.22.5 D-ST5 - Structural Analysis Report ...................................................................................................................292 2.22.6 D-ST6 - Alignment and Stability Analysis.........................................................................................................293 2.22.7 D-ST7 - Fracture Analysis Report......................................................................................................................294 2.22.8 D-ST8 - Correlated FEM Description Report.....................................................................................................295 2.22.9 D-ST9 - Sine Test Predictions and Preliminary Notching Analysis ...................................................................296 2.22.10 D-ST10 - FEM Correlation Report.................................................................................................................297 2.22.11 D-ST11 - LCDA FEM Description Report.....................................................................................................298 2.22.12 D-ST12 - LCDA Results Assessment Report.................................................................................................299 2.22.13 D-ST13 - Acoustic, Sine & Shock Test Design Assessment Report ..............................................................300 2.22.14 D-ST14 – FEM Requirements Specification ..................................................................................................301 2.22.15 D-ST15 – EarthCARE STM Specification.....................................................................................................302 2.22.16 D-ST16 – EarthCARE STM Description .......................................................................................................303

2.23 Software Related Documents...............................................................................................................304 2.23.1 D-SW1 - On Board Software Overview.............................................................................................................304 2.23.2 D-SW2 - On Ground Software Overview ..........................................................................................................305 2.23.3 D-SW3 - Requirements Baseline and Interface Requirements (RB)..................................................................306 2.23.4 D-SW4 - Technical Specification including Interface Control Document (TS).................................................307 2.23.5 D-SW5 - Design Justification File for Re-Used Software..................................................................................308 2.23.6 D-SW6 - Software Development Plan................................................................................................................309 2.23.7 D-SW7 - Plan for Independent Onboard S/W Verification and Validation........................................................310 2.23.8 D-SW8 - IV&V Report ......................................................................................................................................311 2.23.9 D-SW9 - Software Design Definition File .........................................................................................................312 2.23.10 D-SW10 - Software Design Justification File ................................................................................................313 2.23.11 D-SW11 - User Manual and Maintenance Manual for SDVE........................................................................314 2.23.12 D-SW12 - SDVE Specification ......................................................................................................................315 2.23.13 D-SW13 - Software Release Note ..................................................................................................................316 2.23.14 D-SW14 – Set of Software Documents for Units Containing Software.........................................................317

2.24 Thermal Related Documents ...............................................................................................................318 2.24.1 D-TH1 - Satellite Thermal Design Requirements Specification ........................................................................318 2.24.2 D-TH2 - Trade- Off Studies ...............................................................................................................................319 2.24.3 D-TH3 - Thermal Design Report........................................................................................................................320


2.24.4 D-TH4 - Thermal Analysis Report of Satellite and Instruments ........................................................................321 2.24.5 D-TH5 - Report of Satellite/Launcher Coupled Thermal Analysis ....................................................................322 2.24.6 D-TH6 - Temperature Predictions for TB/TV tests............................................................................................323 2.24.7 D-TH7 - TB Tests Correlation with TMM’s ......................................................................................................324 2.24.8 D-TH8 - Post Test Flight Predictions .................................................................................................................325 2.24.9 D-TH9 – Measurement Point Plan .....................................................................................................................326 2.24.10 D-TH10 – Test Heater Plan ............................................................................................................................327 2.24.11 D-TH11 – In-Orbit Thermal Report ...............................................................................................................328 2.24.12 D-TH12 – TMM Requirements Specifications ..............................................................................................329


Introduction Purpose of this document is to provide a guideline for the contents and structure of each document listed in the EarthCARE Document Requirements List (Ref. EC-RS-ESA-SY-005). The documents should include as a minimum the information required in the section “Content”.

1 Applicable Documents

1.1 Documents applicable to this DCG The following documents are applicable AD1 EC-RS-ESA-SY-0011 EarthCARE Contractual Baseline Documentation List (CBDL) AD2 EC-SW-ESA-SY-0003 EarthCARE Statement of Work AD3 EC-RS-ESA-SY-0004 EarthCARE Management Requirements and Tasks AD4 EC-RS-ESA-SY-0005 EarthCARE Document Requirements List Note: to avoid duplication of Applicable Document Numbers, the DGG calls for the various AD, ND, ID as listed in the CBDL [AD1],


2 Document Contents Guideline

2.1 AOCS Related Documents

2.1.1 D-AO1 - AOCS and Propulsion Specifications PURPOSE OF DOCUMENT The - AOCS specification - propulsion specification - establishes the requirements for the design, the development, the performance, the testing & validation, and the delivery of the AOCS subsystem and propulsion subsystem. They also specify the interface with the satellite system. The AOCS subsystem specification and propulsion subsystem specification shall serve as a basis: - To derive the AOCS sensors/actuators and propulsion components procurement specifications. - To establish the AOCS and propulsion subsystem test plan and specification CONTENTS AOCS design specification and propulsion design specifications in terms of: - General function - Subsystem definition (functional and mode description, architecture, components, …) - Subsystem design requirements (performance, SW, timing, construction, storage, …) - Subsystem budget requirements (pointing accuracy, alignment, mass, power, propellant budget, …) - Subsystem operational requirement (operational constraints, TM/TC, fault protection requirements, …) - Subsystem lifetime and reliability requirements - Satellite and payload interface requirements (mass and inertia properties, flexure modes of appendages, magnetic dipole, internal disturbances, …) - Subsystem physical interfaces requirements (electrical, mechanical, thermal) - Environmental testing requirements (mechanical , thermal, EMC,…) - Subsystem verification requirements (verification approach at subsystem level, summary test sequence and detailed test matrices) - Ground support equipment requirements (EGSE/MGSE/FGSE/STE) - PA (including model philosophy


2.1.2 D-AO2 - AOCS Design Report PURPOSE OF DOCUMENT The - AOCS design report – propulsion design report - purpose are to report the main design features, the design drivers, the design analyses and the justification for the AOCS subsystem design and for the propulsion subsystem design. CONTENTS The AOCS design report shall provide a description in terms of: - Overview of the AOCS subsystem (function, key performances, …) - AOCS HW architecture description(block diagram down to unit/equipment level with description of each unit/equipment block, sensor and actuator configuration, …) - AOCS unit by unit description (functional description, performance, mounting, operation, alignment, mass and power, interfaces, constraints, …) - AOCS operational modes description (mode logic and sequence of events, mode performance requirements, AOCS mode by mode functional description, nominal equipment configuration in each mode, operational requirements,…) - AOCS Mode transition (mode entry and exit conditions, mode initialisation description, …) - AOCS control loop design (design requirements and design drivers, description of the control law algorithm and justification for the control loop design choices, selection of the control parameters with justification of their tuning, performance results versus requirements, theoretical analysis of the control loop robustness, …) - AOCS FDIR (redundancy, reliability and failure management, …) - AOCS subsystem budget (pointing and stability for each mode, timing and delays, mass, power, propellant consumption, …) - AOCS SW description (required onboard software support functions, …) - AOCS TM/TC description (Data Handling interfaces, …) - AOCS subsystem electrical architecture and interfaces The Propulsion design report shall provide a description in terms of: - Description of the propulsion subsystem (subsystem function, block diagram, subsystem layout, key performances, …) - Subsystem sizing (tank, …) - Propulsion unit by unit description (functional description, performance, mounting, operation, alignment, mass and power, interfaces, constraints, …) - Propulsion subsystem budget (mass, power, …) - Functional analyses (pressure drop, thermodynamic, leak, thruster mismatch, plume impingement, propellant filtering, propellant tank PMD adequacy to launcher and satellite accelerations, mass, reliability, structural design adequacy, end of life propellant residuals, propellant gauging accuracy, subsystem safety, …) - Propulsion unit by unit description (functional description, performance, mounting, operation, alignment, mass and power, interfaces, constraints, …) - Propulsion FDIR (redundancy, reliability and failure management,…) - Propulsion TM/TC description (Data Handling interfaces, …) - Propulsion subsystem electrical architecture and interfaces - Description of integration and test activities - Description of the propellant loading strategy


2.1.3 D-AO3 - AOCS Databank Document PURPOSE OF DOCUMENT The purpose of the AOCS databank document is to provide a full description and traceability of the simulation environment that will be used to demonstrate the compliance of the AOCS control loop performance to the subsystem and system requirements. It shall become an applicable document for the AOCS simulation test report. CONTENTS The AOCS data bank document shall contain the detailed definition of the mathematical models used for: - The reference frames - The AOCS equipments (sensors and actuators) with their parameters, inputs and outputs - The equipment layout including mounting frames and alignment accuracy - The potential shadowing effects on optical sensors. - The satellite external environment (external forces and torques due to air drag, earth magnetic field, gravity gradient, sun radiation pressure ...) - The internal disturbances (satellite magnetic dipole, fuel sloshing, wheel imbalances, thruster disturbance torques, plume impingement, ...) - The satellite and appendages dynamics (including flexible modes)


2.2 Simulator Related Documents

2.2.1 D-AS1 - Requirements for ESSS and ECGP PURPOSE OF DOCUMENT To establish the requirements related to the ESSS and ECGP portions of the ECEESIM for the EarthCARE ground control Center. CONTENTS The specification shall cover as a minimum the requirements for: - the simulation of the spacecraft - the simulation of the instruments - the simulated data streams - the simulation of the ground segment - the software/hardware implementation - the man-machine interface - representativity and accuracy of simulation of parameters - presentation of analogue parameters and control loops - management and presentation of the simulation context and parameters - generation of images from downloaded software as well as management of reference images for uploading of

memory


2.2.2 D-AS2 - Architecture of ESSS and ECGP PURPOSE OF DOCUMENT The document shall define the architecture of the ESSS and ECGP, and is part of the Design Definition File. CONTENTS To be proposed by the contractor and to be agreed by the Agency


2.2.3 D-AS3 - ESSS and ECGP Description PURPOSE OF DOCUMENT To describe the ESSS and ECGP design and its operational, functional and performance characteristics. CONTENTS The document should contain as a minimum: - design principle - definition and architecture (block diagram, computation load, computation speed) - description and characteristics of each module - operational description - functional description - performances description - interface descriptions - mathematical formulation - input / output data description - validation / characterisation methods - logic flow of data processing - description of the hardware supporting the application - description of the software supporting the application.


2.2.4 D-AS4 - ESSS and ECGP User Manual PURPOSE OF DOCUMENT To describe the ESSS and ECGP hardware, software functions and interfaces to the user CONTENTS The document should contain as a minimum: - Overview of the hardware and software to module level - Overview of the performance characteristics - Description of the man-machine interfaces - Description of the data inputs and outputs, format and interpretations - Description of special operational constraints - Step-by-step example for a typical use case - Installation instructions


2.2.5 D-AS5 - ESSS and ECGP Computing Resources Requirements PURPOSE OF DOCUMENT To describe the computing resources required for operation of the ESSS and ECGP. CONTENTS To be proposed by the contractor and to be agreed by the Agency


2.2.6 D-AS6 - ESSS and ECGP ICDs PURPOSE OF DOCUMENT To describe the interfaces to the ESSS and ECGP, including hardware, software and user interfaces. CONTENTS To be proposed by the contractor and to be agreed by the Agency


2.3 ATLID Related Documents

2.3.1 D-AT1 - Atlid Requirements Specification PURPOSE OF DOCUMENT To specify design at instrument level in terms of performance, interface specifications and verification requirements. CONTENTS Instrument design specifications in terms of: - functional requirement - units breakdown - performance requirements - electrical requirements (signals, power, telemetry, telecommand, data handling,...) - mechanical requirements - thermal requirements - interface requirements - environmental requirements - operational requirements (e.g. reliability and lifetime) - EMC, DC/AC magnetic design and test requirements - EGSE/MGSE/OGSE requirements - PA (including model philosophy) - summary test sequence and detailed test matrices


2.3.2 D-AT2 - Atlid ICDs PURPOSE OF DOCUMENT To define all the requirements on Atlid instrument specific interfaces, mechanical, thermal, electrical, environmental and operational, between the instrument and the EarthCARE satellite. CONTENTS Interface specifications in terms of: - general requirements - electrical interfaces (including power supply interfaces, command and control I/F, timings, datation, pyros

interfaces) - mechanical interfaces (including physical properties, local reference, design loads, structural interfaces,

dynamic interfaces, alignment/pointing, field of view, mounting, AIV interfaces) - thermal interfaces (including thermal environmental conditions, thermal limits and dissipations, heat capacities,

surface treatment and thermal insulation, thermal conductances) - science data interfaces, housekeeping TM - connector description, pin allocation - deliverable mathematical models (e.g. reduced thermal mathematical model and reduced finite element model)


2.3.3 D-AT3 - Atlid Performance Model Description and Predictions PURPOSE OF DOCUMENT To study the expected performance of the Atlid instrument based on reference input scenes and thereby demonstrate the ability of the instrument to comply with specified performances. CONTENTS The document should contain as a minimum: - Instrument performances requirements summary - list of parameters influencing the performance - mathematical formulation of the problem - exhaustive description - sensitivity to parameters - results budgets - user manual.


2.3.4 D-AT4 - Atlid Ground Calibration Facilities Specification PURPOSE OF DOCUMENT To specify the external calibration facilities for establishing the absolute calibration of the Atlid instrument. CONTENTS - general function - operational requirements - functional requirements - performance requirements - interfaces requirements - mechanical and environmental requirements - validation / calibration and test requirements - maintenance requirements - reliability requirements - software requirements - communication requirements - safety requirements - installation requirements - transportation requirements


2.3.5 D-AT5 - ATLID Design, Development and Verification Plan PURPOSE OF DOCUMENT To define the overall instrument design/development philosophy from engineering design through integration, verification and calibration while taking into account schedule and programme constraints. CONTENTS - instrument requirements and constraints - hardware and software breakdown - margin philosophy - instrument verification concept - description of development activities (covering manufacturing, integration, test calibration/characterization and

GSE plans) - instrument design and development flow model philosophy - summary schedule and milestones (including reviews) - description of software activities (specification to validation)


2.3.6 D-AT6 - Atlid AIV Plan PURPOSE OF DOCUMENT To define and control the Atlid instrument assembly, integration, test and verification plan. To define the full qualification and acceptance test programs from instrument level down to equipment level. CONTENTS Integration Plan in terms of integration approach, methods and responsibilities. Qualification and acceptance test program definition in terms of: - test philosophy - test conditions - hardware/software matrices - qualification test program - acceptance test program - test plan and methods - PA provisions - GSE needs - AIV/AIT planning, flow chart and test sequences - verification and test matrices


2.3.7 D-AT7 - Atlid Technical Description. PURPOSE OF DOCUMENT To describe the Atlid instrument design and its operational, functional and performance characteristics. CONTENTS Instrument description in terms of: - instrument design principle - operational modes - functional modes - performances - block diagram down to equipment level with description of each equipment block and performances - electrical interfaces - ground processing algorithm assumptions - mechanical design - thermal design - power distribution - command/control concept (including datation) - timing diagram - on-board processing - software architecture (including lower level spec. tree and parameters) - software simulation/validation - overall configuration - harness


2.3.8 D-AT8 - Atlid Ground Calibration Facilities Description Test and Calibration Report

PURPOSE OF DOCUMENT To describe the Atlid instrument on-ground calibration facilities design and their operational, functional and performance characteristics and to summarize the results of the test and calibration performed on these facilities. CONTENTS - ground calibration facilities description and characteristics - operational modes - functional modes - performances - block diagram and description of each module - interface description - mechanical, electrical, environmental design - calibration description - test description - calibration report - test report


2.3.9 D-AT9 - Atlid Instrument Budgets PURPOSE OF DOCUMENT To provide the budgets of the Atlid instrument (mass, power, telemetry, performance, etc.). CONTENTS All instrument budgets in support to the contents of [D-SA6], and furthermore all the instrument specific performance parameters.


2.3.10 D-AT10 - Atlid Calibration and Characterization Data Base. PURPOSE OF DOCUMENT To provide all the information pertinent to the use of the calibration/characterization parameters to be injected within the ground processing algorithms. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the database. This shall include a complete description of the physical and electronic data exchange and the format and layout of all database files, so that their contents can be read and installed. For each calibration and characterization parameter, a form sheet indicating: - file name of the calibration/characterization - instrument configuration identifier - parameter file (look-up tables) - environmental conditions - reference to the test set-up configuration and test date/time


2.3.11 D-AT11 - Atlid IOV plan PURPOSE OF DOCUMENT To provide all the information needed to verify the in-orbit instrument functionality, verification and characterization of the instrument in-orbit performance, verification of the consistency of Ground processor processing and level 1a and level 1 b products. CONTENTS IOV Plan in terms of approach, methods and responsibilities. Schedule and phasing approach. Data flows during IOV phase Instrument verification program definition in terms of: - in-orbit verification philosophy - instrument constraints during IOV phases - hardware/software matrices - thermal aspects verification program - power aspects verification program - functional aspects verification program - performance aspects verification program - verification plan and methods - PA provisions - Verification sheets - Verification report - Verification matrices


2.3.12 D-AT12 - Atlid Flight Operation Manual. PURPOSE OF DOCUMENT To define in full detail the in-orbit operation and control procedures of the instrument. CONTENTS - detailed design description down to the level of functional and block diagrams - operational modes, redundancy and cross-strapping concepts - full description of command and control functions - physical configuration and accommodation including external and major internal electrical/mechanical

interfaces/interconnections as well as alignment data, mass and dimensional properties - MCMD description as applicable - Source packet description and formatting - Telemetry and telecommand sheets - On-ground operational procedures and constraints, also describing failure recognition and recovery

procedures. This document will be included in [D-ES6]


2.3.13 D-AT13 - Atlid GSE Specification. PURPOSE OF DOCUMENT To establish the requirements for the instrument GSE. CONTENTS - GSE definition (general and specific requirements, test levels and objectives) - Operational requirements - Interface requirements - Software requirements - List of test and performance requirements - List of Special Test Equipment - Hardware design and construction requirements - EMC requirements - Environmental requirements - PA - Preparation for delivery


2.3.14 D-AT14 - Atlid GSE Design Report PURPOSE OF DOCUMENT To present the design of the instrument GSE and to give an assessment of the expected performance against the specification. CONTENTS - GSE design overview

- Operational description - Functional architecture - Physical configuration - Electrical design and configuration - Mechanical design and configuration

- GSE hardware design - EGSE software - Performances - Instrument/GSE thermal interfaces - Instrument/GSE mechanical interfaces - Instrument/GSE electrical/software interfaces - Instrument/GSE optical interfaces - EGSE test set-up description and performances - Compliance matrix - PA aspects - Maintenance aspects - Transportability aspects.


2.3.15 D-AT15 – ATLID ESSS and ECGP Design, Development and Verification Plans

PURPOSE OF DOCUMENT To define the overall design/development philosophy for the ATLID ESSS / ECGP from engineering design through integration and verification and calibration while taking into account schedule and program constraints. CONTENTS The document should address as a minimum: - Instrument simulator module - processor module - hardware and software breakdown - verification concept - description of development activities (covering manufacturing, integration, test, characterisation plans) - summary schedule and milestones (including reviews) - description of software activities (specification to validation)


2.3.16 D-AT16 – ATLID ESSS and ECGP Module Specifications PURPOSE OF DOCUMENT Top-level specification for the ATLID ESSS and ECGP modules development. These modules will be part of the system ESSS and ECGP. CONTENTS List of requirements on the ATLID ESSS and ECGP, including in particular: - Simulation of the instrument - Raw Data Interface (high-level) - Level 1b Product Definition (high-level) [Draft D-AT 17] - Level 0 Product Definitions (high-level) [Draft D-AT 18] - Product Delivery interface Definition - Man/Machine interface for Processor - Automatic command and control interface for Processor - Integration with System ESSS / ECGP. Note: All low-level data definitions should go into their own docs (Science packet specifications, product format specifications)


2.3.17 D-AT17 - Atlid Level 1b Product Definition D-AT17 PURPOSE OF DOCUMENT Defines the Atlid Level 1a and 1b product. CONTENTS To be specified by contractor and to be agreed with agency.


2.3.18 D-AT18 - Atlid Level 0 Product Definition PURPOSE OF DOCUMENT Defines the Atlid Level 0 product CONTENTS Defines the Level 0 product, which consists essentially of instrument raw data, time ordered and quality marked.


2.3.19 D-AT19 – ATLID ESSS and ECGP Users Manuals PURPOSE OF DOCUMENT To describe the Atlid ESSS and ECGP hardware, software functions and interfaces to the user CONTENTS The document should contain as a minimum: - Overview of the hardware and the software to module level - Overview of performance - Description of the man-machine and command-line interfaces - Description of the data inputs and outputs, format and interpretations - Description of special operational constraints - Step-by-step example for a typical use case - Interface description / ICD - Installation instructions


2.3.20 D-AT20 – ATLID Algorithms Theoretical Baseline Document D-AT20 PURPOSE OF DOCUMENT To describe the algorithm to derive the Atlid level 1 b product CONTENTS To be specified by contractor and to be agreed with agency.


2.3.21 D-AT21 – ATLID ECGP Reference Test Data Set Description PURPOSE OF DOCUMENT This document contains a description of the test data and file structure used to validate the processor. CONTENTS To be specified by contractor and to be agreed with agency.


2.3.22 D-AT22 – ATLID SRR Data Package PURPOSE OF DOCUMENT To provide the information necessary to perform the ATLID Specific Requirements Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline

(electrical, mechanical, thermal, command and control, data handling, AOCS, EMC/RFC, software and product assurance) an overview of:

- the major design aspects - major achievements in the development and test programme - major problem areas and their proposed solutions - major waivers/deviations from the baseline requirements as evolved

The summary is part of the data package proper and is required in the same number of copies. 2. The baseline documents as identified for each major review in the EarthCARE Document Requirements List

(DRL). The baseline documents to be provided as part of the data package proper and the number of copies will be agreed and specified in dedicated review procedures provided by the Customer. Baseline documents not included in the data package proper, however listed in the DRL as deliverable at the review milestone, shall be provided in the number of copies specified in the DRL.

The Contractor shall propose a detailed contents list of the Review Package for Customer approval 2 months prior to the submission of the data package.


2.3.23 D-AT23 – ATLID PDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the ATLID Preliminary Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline


- the major design changes - major achievements in the development and test programme - major problem areas and their proposed solutions - major waivers/deviations from the baseline requirements as evolved



3. The Contractor shall propose a detailed contents list of the Review Package for Customer approval 2 months

prior to the submission of the data package.


2.3.24 D-AT24 – ATLID CDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the ATLID Critical Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline








2.3.25 D-AT25 – ATLID QR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the ATLID Qualification Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline


- the major design changes - major achievements in the development and test programme, including qualification status - major problem areas and their proposed solutions - major waivers/deviations from the baseline requirements as evolved






2.3.26 D-AT26 – ATLID AR Data Package D-AT26 PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the ATLID Acceptance Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline








2.3.27 D-AT27 – ATLID Master Planning PURPOSE OF DOCUMENTS To report the schedule as a result of an objective and realistic analysis of the progress made, showing an active control of the execution of the work CONTENTS ‘Similar’ to D-PM18 for the instrument. During instrument AIT, separately, a schedule shall be re-issued every week to identify the day to day activities for the next two weeks.


2.3.28 D-AT28 – ATLID Risk Analysis D-AT28 PURPOSE OF DOCUMENT To assess and control all risks associated to the Instrument and to the overall project. CONTENTS See D-PM4 for the content of the Risk Management Plan. See D-PM5 for the content of the Risk Register.


2.3.29 D-AT29 – ATLID Long Lead Items List PURPOSE OF DOCUMENT Identification of Long Lead Items. CONTENTS The Long Lead Items list shall fully identify all parts and materials that have excessive procurement cycles which may lead to schedule drivers for the EarthCARE project. The list shall also identify intended delivery dates of the identified items and provide a reference to detailed procurement information.


2.4 AIV Related Documents

2.4.1 D-AV1 - AIV/AIT Plan PURPOSE OF DOCUMENT To define and control the EarthCARE satellite system assembly, integration verification and test plan from instrument/sub-system level up to satellite level. CONTENTS The contents of this document shall be in accordance with Annex D of the ND41. They will at least include the following topics: Verification philosophy, to include as a minimum: - Verification approach - Verification planning - Verification control - Responsibilities - Verification summary matrix AIT philosophy, to include: - AIT approach - AIT planning - AIT control - AIT responsibilities It specifically includes the satellite integration plan, covering the qualification and acceptance test program definition in terms of: - test philosophy - test conditions - hardware/software matrices - qualification test program (involving functional testing at ambient, qualification level, vibration and TV test limits,

TV profile and EMC/RFC) - acceptance level program (involving functional testing at ambient, acceptance level, vibration and TV test

limits, TV profile and EMC/RFC) - test plan and methods - PA provisions


2.4.2 D-AV2 - Facilities, Logistics and Transportation Plan PURPOSE OF DOCUMENT To define and plan the provision of suitable test facilities, indicating the location of all hardware at all times during the programme (Instrument and Spacecraft level), all the major shipments foreseen in the course of the programme and means of transportation for the EarthCARE satellite system. CONTENTS Facilities, logistics and transportation planning, to include as a minimum: - list of proposed test activities - proposed test facility - schedule for test facility availability - location of all hardware at all times - indication of all major shipments - means of transportation, including: - items to be transported - requirements on transportation - transport responsibility - transportation planning.


2.4.3 D-AV3 - H/W S/W Procurement Items Matrix PURPOSE OF DOCUMENT To establish the list of all deliverable items of satellite, hardware and software as well as GSE down to unit level. CONTENTS As a minimum the document shall contain deliverables covered by the following areas: - satellite hardware breakdown to unit level covering all models, spares, attrition and repair kit - all satellite on-board software - GSE hardware and test software - software validation facilities - software development tools (hardware & software) - simulation tools (hardware & software) - mathematical models.


2.4.4 D-AV4 - Test Specifications D-AV4 PURPOSE OF DOCUMENT This document details the test requirements for specific test activity(ies) described in the AIV plan. This applies at all levels of integration. CONTENTS As defined in ND41 (ECSS-E-10-02) Annex F


2.4.5 D-AV5 - Verification Matrix PURPOSE OF DOCUMENT The verification Matrix defines the verification strategy for each Satellite Contractual Baseline requirement in terms of methods / levels / stages. The Verification Matrix is the starting point for the Verification Control Document and will be eventually incorporated in the VCD as soon as it is frozen. CONTENTS The contents of this document shall be in accordance with Annex C of the ND41.


2.4.6 D-AV6 - Satellite Design, Development and Verification Plan PURPOSE OF DOCUMENT To define the overall EarthCARE satellite system design and development activities. CONTENTS The DDV Plans of the major entities (e.g. instruments and GSE) are considered to be part of the Satellite DDV Plan. Design and development plan, to include as a minimum: - system definition - system design and development flow, model philosophy - margin philosophy - qualification and acceptance philosophy - description of system level activities - schedule, including major milestones and reviews - hardware and software breakdown, where applicable - development plan (covering manufacturing, integration and test plans and model philosophy) - general design and engineering aspects (including performance, mechanical/thermal, electrical design,

EMC/RFC aspects, software development and validation, EGSE/MGSE) - summary schedule and milestones - compliance to system/satellite-level requirements In addition, a specific chapter should contain a system level Test Requirements Specification. These specifications should describe the system level tests to be performed in order to verify that the satellite requirements are met. Traceability to the relevant documents shall be provided. The test specifications shall be detailed enough to allow: - to derive system level test block plans and test procedures - to derive functional requirements on the GSE such that the foreseen tests can be performed, - to derive testability requirements on unit, equipment and subsystem level (e.g. requirements for test-

connectors, specific test-modes, test-interface characteristics, etc.), - to derive requirements on specific test-equipment and external test-facilities needed.


2.4.7 D-AV7 - Test Block Plans PURPOSE OF DOCUMENT To establish the objectives, organization and constraints of major development, qualification and acceptance tests as foreseen in the design and development and verification of EarthCARE hardware and software (system and major entities). CONTENTS A test block plan shall be prepared covering: - scope and objectives (specifying test success criteria) - description (specifying phases of test and items under test as well as the logical test flow diagram including

their interrelation) - implementation (configuration control, personnel logistics and responsibilities, test durations, test

documentation) - environment (required facilities, data processing and operational requirements) Major Test Readiness Review Boards (TRRB) and post test Test Review Boards (TRB) shall be organized for each test block plan.


2.4.8 D-AV8 - AIT Procedures PURPOSE OF DOCUMENT To establish the procedures used in individual development, qualification and acceptance tests as foreseen in the Test Block Plans of EarthCARE hardware and software. CONTENTS The test procedures shall include as a minimum: - scope of the test, including the identification of the requirements(s) being verified - identification of the test object - applicable documents, with their revision status - test flow - test organization - test conditions - test equipment and set-up - step by step procedure - recording of data - pass/fail criteria and test data evaluation requirements - guidelines/criteria for test deviations and for retest Test Readiness Review Boards (TRRB) and post test Test Review Boards (TRB) shall be organized.


2.4.9 D-AV9 - Verification Control Document PURPOSE OF DOCUMENT The Verification Control Document lists the Satellite Contractual Baseline requirements to be verified and the associated verification matrix. It also provides traceability on the verification process events and documentation and gives evidence of the verification status and close-out. The VCD is used to monitor and control the verification process and to demonstrate to the Customer, at the end of the relevant stages (e.g. qualification, acceptance) that verification has been completed. CONTENTS The contents of this document shall be in accordance with Annex E of the ND41.


2.4.10 D-AV10 - Launch Operations Procedures PURPOSE OF DOCUMENT To establish the detailed procedures related to the satellite integration, test and launch preparation at the launch site. CONTENTS The document shall provide detailed procedures for the satellite integration, test and launch preparation activities, and satellite launch countdown activities as described in the Launch Operation Plan [D-AV11]. The relevant test procedures shall include as a minimum: - scope of the test, including the identification of the requirements(s) being verified - identification of the test object - applicable documents, with their revision status - test flow - test organization - test conditions - test equipment and set-up - step by step procedure - recording of data - pass/fail criteria and test data evaluation requirements - guidelines/criteria for test deviations and for retest Test Readiness Review Boards (TRRB) and post test Test Review Boards (TRB) shall be organised according to the EarthCARE Management Requirements. Safety critical operation procedures are furthermore subject to the Launch Authority safety submission requirements.


2.4.11 D-AV11 - Launch Operations Plan PURPOSE OF DOCUMENT To establish the requirements related to the satellite integration, test and launch preparation at the launch site. CONTENTS The plan shall cover as a minimum the detailed tasks planned at the launch site including logistics, manpower, duration, required facilities (external and internal) in support of: - the satellite transport to the launch site - the activities covered by the Customer provided Satellite Operations Plan and the Launch Operations Manual - the activities covered by the Customer together with the Launch Authority in the Interleaved Operations Plan - the activities covered by the Customer together with the Launch Authority in the Combined Operations Plan

including the Countdown Manual and Rehearsals - the activities covered by the return transport of GSE, flight/integration spares.


2.4.12 D-AV12 - GSE Requirements Specifications PURPOSE OF DOCUMENT To define the design requirements for EGSE, MGSE, FGSE and OGSE. CONTENTS GSE Design Specifications, to include at least: - GSE definition - performance requirements - operational requirements - interface requirements - software requirements - hardware requirements - structural (load) and test requirements - PA aspects


2.4.13 D-AV13 - Launch Campaign Staffing and Logistics Plans PURPOSE OF DOCUMENT To define and plan the provision of the necessary manpower, suitable test facilities and means of transportation for EarthCARE satellite system. CONTENTS Manpower, facilities and transportation planning, to include: - list of required manpower and breakdown/schedule of launch site attendance - additional support needed (e.g. CPR related) - list of proposed test activities - proposed test facility - schedule for test facility availability - means of transportation, including: - items to be transported - requirements on transportation - transport responsibility - transportation planning.


2.4.14 D-AV14 - Waterfall Schedule for AIT PURPOSE OF DOCUMENT Scheduling information for AIT activities. CONTENTS All activities identified in the AIT plan shall be provided in the waterfall schedule. A schedule shall be re-issued every month showing the waterfall schedule of activities identified in the AIT Plan for the next six weeks. Separately, a schedule shall be re-issued every week to identify the day to day activities for the next two weeks.


2.4.15 D-AV15 – Characterization / Calibration Plan PURPOSE OF DOCUMENT To define all EarthCARE satellite system and instruments characterization / calibration activities, both on-ground and in-orbit. CONTENTS Plan of all characterization / calibration activities, including: - system and instrument characterisation/calibration definition - on-ground characterization / calibration activities - in-orbit characterization/calibration activities - characterization/calibration activities flow - definition of characterization / calibration facilities required. - Required frequency of characterization/calibration


2.4.16 D-AV16 - Test Reports PURPOSE OF DOCUMENT To present the results of individual development, qualification and acceptance tests as foreseen in the Test Block Plans of EarthCARE. CONTENTS The document shall include the contents required in ND41. The test report shall include as a minimum: - complete reference to the applicable test procedure and test specification, as well as the relevant test block. - scope and objectives - configuration of test article and test conditions, including software and function operability configuration - summary of test results - synthesis of verifications performed (e.g. tables / plots of automated verifications) - evaluation of test results, emphasizing significant events and problems encountered; it shall also cover

interpretation and correlation of test results to relevant analytical predictions - a list of all non-conformances generated during the test - the as-run test procedure including a list of deviations from the applicable test procedure and the sign-off

sheets In the case where automated test procedures are used, the report shall not be limited to provision only of “pass” / “fail” responses and log files.


2.4.17 D-AV17 - Ground Operations Constraints D-AV17 PURPOSE OF DOCUMENT To identify any operational limitation of the satellite (platform plus instruments) applicable only to the System Validation Tests test environment. CONTENTS This shall identify all limitations and constraints of the satellite, including instruments, for the planning and conduct of the System Validation Tests.


2.4.18 D-AV18 - Alignment Plan and Procedure PURPOSE OF DOCUMENT To identify and organise all alignment activities needed to fulfil the performance requirements CONTENTS The document shall:

- recall all requirements for all units. - list all optical cube locations - list all alignment activities to be done during the course of the program (STM and FM) at all levels of

integration - define the format in which the results will be recorded


2.4.19 D-AV19 – Generic Front End Data Processing Specification PURPOSE OF DOCUMENT To specify the requirements for the front end data processing element of the GSE used in the instruments and satellite AIV activities. CONTENTS To be proposed by the contractor and approved by the Agency


2.4.20 D-AV20 – EGSE Internal Electrical Interface Specification PURPOSE OF DOCUMENT To specify the internal electrical interfaces of the EGSE equipment for satellite and instruments. CONTENTS To be proposed by the contractor and approved by the Agency


2.4.21 D-AV21 – Instrument and Satellite to Facilities ICDs PURPOSE OF DOCUMENT To specify the interfaces of the satellite and the instruments (including their GSE) to the facilities used for development, integration and verification. CONTENTS To be proposed by the contractor and approved by the Agency


2.4.22 D-AV22 – EGSE Requirements Specification PURPOSE OF DOCUMENT To specify the requirements EGSE used in the satellite and instrument AIV activities. CONTENTS See D-AV12.


2.5 BBR Instrument Related Documents

2.5.1 D-BB1 - BBR Requirements Specification PURPOSE OF DOCUMENT To specify design at instrument level in terms of performance, interface specifications and verification requirements. CONTENTS Instrument design specifications in terms of: - functional requirement - units breakdown - performance requirements - electrical requirements (signals, power, telemetry, telecommand, data handling,...) - mechanical requirements - thermal requirements - interface requirements - environmental requirements - operational requirements (e.g. reliability and lifetime) - EMC, DC/AC magnetic design and test requirements - EGSE/MGSE/OGSE requirements - PA (including model philosophy) - summary test sequence and detailed test matrices


2.5.2 D-BB2 - BBR ICDs PURPOSE OF DOCUMENT To define all the requirements on BBR instrument specific interfaces, mechanical, thermal, electrical, environmental and operational, between the instrument and the EarthCARE satellite. CONTENTS Interface specifications in terms of: - general requirements - electrical interfaces (including power supply interfaces, command and control I/F, timings, datation, pyros





2.5.3 D-BB3 - BBR Performance Model Description and Predictions PURPOSE OF DOCUMENT To study the expected performance of the BBR instrument based on reference input scenes and thereby demonstrate the ability of the instrument to comply with specified performances. CONTENTS The document should contain as a minimum: - Instrument performances requirements summary - list of parameters influencing the performance - mathematical formulation of the problem - exhaustive description - sensitivity to parameters - results budgets - user manual.


2.5.4 D-BB4 - BBR Ground Calibration Facilities Specification PURPOSE OF DOCUMENT To specify the external calibration facilities for establishing the absolute calibration of the BBR instrument. CONTENTS - general function - operational requirements - functional requirements - performance requirements - interfaces requirements - mechanical and environmental requirements - validation / calibration and test requirements - maintenance requirements - reliability requirements - software requirements - communication requirements - safety requirements - installation requirements - transportation requirements


2.5.5 D-BB5 - BBR Design, Development and Verification Plan PURPOSE OF DOCUMENT To define the overall instrument design/development philosophy from engineering design through integration, verification and calibration while taking into account schedule and programme constraints. CONTENTS - instrument requirements and constraints - hardware and software breakdown - margin philosophy - instrument verification concept - description of development activities (covering manufacturing, integration, test calibration/characterization and



2.5.6 D-BB6 - BBR AIV Plan PURPOSE OF DOCUMENT To define and control the BBR instrument assembly, integration, test and verification plan. To define the full qualification and acceptance test programs from instrument level down to equipment level. CONTENTS Integration Plan in terms of integration approach, methods and responsibilities. Qualification and acceptance test program definition in terms of: - test philosophy - test conditions - hardware/software matrices - qualification test program - acceptance test program - test plan and methods - PA provisions - GSE needs - AIV/AIT planning, flow chart and test sequences - verification and test matrices


2.5.7 D-BB7 - BBR Technical Description PURPOSE OF DOCUMENT To describe the BBR instrument design and its operational, functional and performance characteristics. CONTENTS Instrument description in terms of: - instrument design principle - operational modes - functional modes - performances - block diagram down to equipment level with description of each equipment block and performances - electrical interfaces - ground processing algorithm assumptions - mechanical design - thermal design - power distribution - command/control concept (including datation) - timing diagram - on-board processing - software architecture (including lower level spec. tree and parameters) - software simulation/validation - overall configuration - harness


2.5.8 D-BB8 - BBR Ground Calibration Facilities Description, Test and Calibration Report

PURPOSE OF DOCUMENT To describe the BBR instrument on-ground calibration facilities design and their operational, functional and performance characteristics and to summarize the results of the test and calibration performed on these facilities. CONTENTS - ground calibration facilities description and characteristics - operational modes - functional modes - performances - block diagram and description of each module - interface description - mechanical, electrical, environmental design - calibration description - test description - calibration report - test report


2.5.9 D-BB9 - BBR Instrument Budgets PURPOSE OF DOCUMENT To provide the budgets of the BBR instrument (mass, power, telemetry, performance, etc.). CONTENTS All instrument budgets in support to the contents of [D-SA6], and furthermore all the instrument specific performance parameters.


2.5.10 D-BB10 - BBR. Calibration and Characterization Data Base PURPOSE OF DOCUMENT To provide all the information pertinent to the use of the calibration/characterization parameters to be injected within the ground processing algorithms. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the database. This shall include a complete description of the physical and electronic data exchange and the format and layout of all database files, so that their contents can be read and installed. For each calibration and characterization parameter, a form sheet indicating: - file name of the calibration/characterization - instrument configuration identifier - parameter file (look-up tables) - environmental conditions - reference to the test set-up configuration and test date/time


2.5.11 D-BB11 - BBR IOV plan PURPOSE OF DOCUMENT To provide all the information needed to verify the in-orbit instrument functionality, verification and characterization of the instrument in-orbit performance, verification of the consistency of Ground processor processing and level 1a and level 1 b products. CONTENTS IOV Plan in terms of approach, methods and responsibilities. Schedule and phasing approach. Data flows during IOV phase Instrument verification program definition in terms of: - in-orbit verification philosophy - instrument constraints during IOV phases - hardware/software matrices - thermal aspects verification program - power aspects verification program - functional aspects verification program - performance aspects verification program - verification plan and methods - PA provisions - Verification sheets - Verification report - Verification matrices


2.5.12 D-BB12 - BBR Flight Operation Manual PURPOSE OF DOCUMENT To define in full detail the in-orbit operation and control procedures of the instrument. CONTENTS - detailed design description down to the level of functional and block diagrams - operational modes, redundancy and cross-strapping concepts - full description of command and control functions - physical configuration and accommodation including external and major internal electrical/mechanical




2.5.13 D-BB13 - BBR GSE Specification PURPOSE OF DOCUMENT To establish the requirements for the instrument GSE. CONTENTS - GSE definition (general and specific requirements, test levels and objectives) - Operational requirements - Interface requirements - Software requirements - List of test and performance requirements - List of STE - Hardware design and construction requirements - EMC requirements - Environmental requirements - PA - Preparation for delivery


2.5.14 D-BB14 - BBR GSE Design Report PURPOSE OF DOCUMENT To present the design of the instrument GSE and to give an assessment of the expected performance against the specification. CONTENTS - GSE design overview




2.5.15 D-BB15 – BBR ESSS and ECGP Design, Development and Verification Plans

PURPOSE OF DOCUMENT To define the overall ESSS and ECGP modules design/development philosophy for the BBR from engineering design through integration and verification and calibration while taking into account schedule and program constraints. CONTENTS The document should contain as a minimum: - Instrument simulator module - processor module - hardware and software breakdown - verification concept - description of development activities (covering manufacturing, integration, test, characterisation plans) - summary schedule and milestones (including reviews) - description of software activities (specification to validation)


2.5.16 D-BB16 - BBR ESSS and ECGP Module Specifications PURPOSE OF DOCUMENT Top-level specification for the BBR ESSS and ECGP modules development. These modules will be part of the system ESSS and ECGP. CONTENTS List of requirements on the BBR ESSS and ECGP, including in particular: - Simulation of the instrument - Raw Data Interface (high-level) - Level 1b Product Definition (high-level) [Draft D-AT 17] - Level 0 Product Definitions (high-level) [Draft D-AT 18] - Product Delivery interface Definition - Man/Machine interface for Processor - Automatic command and control interface for Processor - Integration with System ESSS / ECGP. Note: All low-level data definitions should go into their own docs (Science packet specifications, product format specifications)


2.5.17 D-BB17 - BBR Level 1b Product Definition PURPOSE OF DOCUMENT Defines the BBR Level 1 product. CONTENTS To be specified by contractor and to be agreed with agency.


2.5.18 D-BB18 - BBR Level 0 Product Definition PURPOSE OF DOCUMENT Defines the BBR Level 0 product CONTENTS Defines the Level 0 product, which consists essentially of instrument raw data, time ordered and quality marked.


2.5.19 D-BB19 – BBR ESSS and ECGP Users Manuals PURPOSE OF DOCUMENT To describe the BBR ESSS and ECGP hardware, software functions and interfaces to the user CONTENTS The document should contain as a minimum: - Overview of the hardware and the software to module level - Overview of the performance - Description of the man-machine and command-line interfaces - Description of the data inputs and outputs, format and interpretations - Description of special operational constraints - Step-by-step example for a typical use case - Installation instructions


2.5.20 D-BB20 – BBR Algorithms Theoretical Baseline Document PURPOSE OF DOCUMENT To describe the algorithm to derive the BBR level 1 product CONTENTS To be specified by contractor and to be agreed with agency.


2.5.21 D-BB21 – BBR ECGP Reference Test Data Set Description PURPOSE OF DOCUMENT This document contains a description of the test data and file structure used to validate the processor. CONTENTS To proposed by the contractor and agreed by the Agency


2.5.22 D-BB22 – BBR SRR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the BBR Specific Requirements Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.5.23 D-BB23 – BBR PDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the BBR Preliminary Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.5.24 D-BB24 – BBR CDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the BBR Critical Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.5.25 D-BB25 – BBR QR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the BBR Qualification Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline


- the major design changes - major achievements in the development and test programme - qualification status - major problem areas and their proposed solutions - major waivers/deviations from the baseline requirements as evolved





2.5.26 D-BB26 – BBR AR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the BBR Acceptance Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.5.27 D-BB27 – BBR Master Planning PURPOSE OF DOCUMENT To report the schedule as a result of an objective and realistic analysis of the progress made, showing an active control of the execution of the work CONTENTS ‘Similar’ to D-PM18 for the instrument. During instrument AIT, separately, a schedule shall be re-issued every week to identify the day to day activities for the next two weeks.


2.5.28 D-BB28 – BBR Risk Analysis PURPOSE OF DOCUMENT To assess and control all risks associated to the instrument and to the overall project. CONTENTS See D-PM4 for the content of the Risk Management Plan. See D-PM5 for the content of the Risk Register.


2.5.29 D-BB29 – BBR Long Lead Items List PURPOSE OF DOCUMENT Identification of Long Lead Items. CONTENTS The Long Lead Items list shall fully identify all parts and materials that have excessive procurement cycles which may lead to schedule drivers for the EarthCARE project. The list shall also identify intended delivery dates of the identified items and provide a reference to detailed procurement information.


2.5.30 D-BB30 – BBR Straylight Analysis PURPOSE OF DOCUMENT To document the analysis of the straylight and effects on the BBR instrument. CONTENTS To be proposed by the contractor and agreed by the Agency


2.6 Commissioning Related Documents

2.6.1 D-CM1 - In-Orbit Calibration and Verification Procedure PURPOSE OF DOCUMENT To define the procedures related to the full calibration and functional and performance verification of the in-orbit EarthCARE satellite system. CONTENTS In-flight calibration and functional and performance verification procedures, including: - satellite activation and stabilisation - satellite testing, including functional checks of all modes and measurement performance - instrument calibration activities - verification of overall system performance


2.6.2 D-CM2 - In-Orbit Verification Plan PURPOSE OF DOCUMENT To define all the activities concerning the EarthCARE satellite system in-orbit verification. CONTENTS Plan of all commissioning activities, including: - in-orbit activities and sequence of operations - spacecraft operational modes summary - commissioning activities flow - definition of ground facilities required In particular, the document shall: - Identify each requirement contained in the System Requirements Document, in the Satellite Design

Specification and in the Level 1b Processors Specifications that is appropriate for in-orbit verification and pass fail criteria.

- Propose a means to verify the requirement. If these means introduce specific requirements for satellite operations, he shall identify these requirements in the plan.

- Define all parameters/ telemetries to be monitored during the in orbit verification. - Define satellite/instruments parameters for routine monitoring during the commissioning phase. The plan shall specifically include the following activities: - Satellite and instrument switch on activities - Satellite in orbit health status and performances - Instrument in orbit health status and characterisation - Instruments in orbit calibration and update if needed of the calibration tables of the level 1b processors - Instruments and level 1b (level 1c for MSI) in orbit performances.


2.6.3 D-CM3 – Inputs to CAL / VAL Plan PURPOSE OF DOCUMENT To document the contractor inputs to the Agency’s Satellite Calibration / Validation Plan. CONTENTS To be proposed by the contractor and agreed by the Agency


2.7 Communications Related Documents

2.7.1 D-CO1 – Communication & RF Subsystem Design Requirements Specification

PURPOSE OF DOCUMENT To specify the RF subsystem design at sub-system and equipment level in terms of performance, interface specifications and verification requirements. CONTENTS RF subsystem (S band and X band) design specifications in terms of: - general function - performance requirements - electrical interfaces (i.e. signals, power, telemetry) - mechanical interfaces - thermal interfaces - mechanical and thermal environmental requirements - EMC/RFC design and test requirements - EGSE/MGSE/STE requirements - operational requirements (e.g. reliability and lifetime) - PA (including model philosophy) - summary test sequence and detailed test matrices - RF Suitcase


2.7.2 D-CO2 - RF Suitcase Design Report PURPOSE OF DOCUMENT To describe the RF Suitcase operational, functional and performance characteristics. CONTENTS RF suitcase description in terms of: - main characteristics - operational modes - functional modes - performance summary - block diagram down to unit/equipment level with description of each unit/equipment block - main electrical interfaces - special requirements on transport and storage - mechanical design, rack layout


2.7.3 D-CO3 – S / X Band, Ground Station and Link Budget Analysis PURPOSE OF DOCUMENT To identify the set of required ground stations and to provide a detailed analysis of the link performance for all scenarios. CONTENTS This document shall include: - Identification of ground stations - Definition of ground station and satellite communication characteristics - Detailed link budget - Ground station visibility - Mass memory sizing - Down link operation


2.8 CPR Instrument Related Documents

2.8.1 D-CP1 - CPR ICD PURPOSE OF DOCUMENT To define all the requirements on instrument specific interfaces, mechanical, thermal, electrical, environmental and operational, between the instrument and the EarthCARE satellite. CONTENTS Interface specifications in terms of: - general requirements - electrical interfaces (including power supply interfaces, command and control I/F, timings, datation, pyros





2.8.2 D-CP2 – CPR specific Documentation PURPOSE OF DOCUMENT To document satellite contractor activities and results related to CPR: - For support during the development of the CPR - For satellite activities after taking possession of the CPR. CONTENTS This includes multiple documents including:

• Technical Notes • Procedures • RFW • NCR • DCR • DCN • Presentations • Logbooks • Data exchange files


2.9 Data Handling Related Documents

2.9.1 D-DH1 – C&C and Science Data Interface Requirements Specifications PURPOSE OF DOCUMENT To specify the Command & Control and Science Data Interface requirements at sub-system and equipment level in terms of performance, interface specifications and verification requirements. CONTENTS Data Handling subsystem C&C and Science data interface specifications in terms of: - general function - performance requirements - communication protocols - operational requirements (e.g. reliability and bit error rate)


2.9.2 D-DH2 - Data Handling Analyses PURPOSE OF DOCUMENT Reports analyses performed on the DHS design (part of [D-SA3]). CONTENTS The document shall report the analysis, budgets and technical justifications which demonstrate that, in conjunction with the RFS, the DHS provides levels of observability and commandability consistent with the required performance. It shall also demonstrate that adequate margins exist for e.g. microprocessor loading, bus utilisation, processor memory size, SW-schedulability (for each unit containing software), timing and synchronisation signals, capacity of onboard storage, and other interfaces with external subsystems. Management, storage and transmission of science data should be analysed and results reported.


2.10 Data Processor Related Documents

2.10.1 D-DP1 - Satellite In Orbit Verification Tool (SIOVT) Specification PURPOSE OF DOCUMENT To specify all the requirements to design, develop and test a Satellite In Orbit Verification Tool (SIOVT) based on the level 1b (1c for MSI) ECGP, the satellite and instrument EGSE and complementary tools for archiving, visualisation, computing trends and performances analysis to be used for in orbit verification. CONTENTS The requirements included in the document shall cover as a minimum the following topics:

- Definition of all the parameters/ telemetries to be monitored during the in orbit verification, and the corresponding tool requirements.

- Definition of the satellite/instruments parameters for routine monitoring during the commissioning phase.

- Satellite and instrument switch on activities. - Satellite in orbit health status and performances. - Instrument in orbit health status and characterisation. - Instrument in orbit calibration and update if needed of the calibration tables of the level 1b (1c for

MSI) processors. - Instruments and level 1b (1c for MSI) in orbit performances.


2.10.2 D-DP2 – ESSS and ECGP Reference Data Set Description Documents

PURPOSE OF DOCUMENT These documents contain descriptions of the test data and file structure used to validate the ESSS and ECGP. CONTENTS To be proposed by the contractor and agreed by the Agency


2.11 Electrical Subsystem Related Documents

2.11.1 D-EL1 - Satellite Electrical Design Requirements Specification PURPOSE OF DOCUMENT To define a common set of electrical design requirements and guidelines for EarthCARE to be applied at satellite, payload and platform, instrument/sub-system and equipment level. CONTENTS Satellite electrical design requirements in terms of: - general design approach (covering design specifications and performance verification) - basic electrical design requirements - specification of electrical interfaces (e.g. signals, power, telecommand, telemetry) - design guidelines for optical and RF equipment - design rules for data management electrical systems - power generation, distribution and quality - cable harness and connectors - electrical systems structural and electrical integrity - grounding and protection - general requirements on verification


2.11.2 D-EL2 – EMC / ESD /RFC Design and Test Requirements PURPOSE OF DOCUMENT To establish the overall satellite EMC, ESD and RFC requirements in order to ensure electromagnetic compatibility of the spacecraft and its associated GSE in all modes of operation (on-ground and in-orbit). Furthermore, the EMC / RFC requirements shall be broken down to sub-system / unit level as appropriate. A verification concept shall be defined to demonstrate the implementation / verification of the requirements from satellite level down to unit level and for the GSE. CONTENTS This specification shall cover at least the following items: - EMC design requirements (bonding, isolation, grounding, cabling, frequency selection etc.) - magnetic requirements - RFC design requirements (blocking, filtering, frequency selection, etc.) - RF compatibility requirements - conducted emission / susceptibility requirements - radiated emission / susceptibility requirements - GSE EMC requirements - ESD requirements - EMC / ESD / RFC test requirements (test specification) - EMC / ESD / RFC verification requirements (test plan)


2.11.3 D-EL3 – EMC / ESD Control Plan PURPOSE OF DOCUMENT To define the Electromagnetic Compatibility, Electrostatic Discharge and Radio-Frequency Compatibility control program to be initiated by the contractor on the EarthCARE project. Specifically the plan shall describe the overall approach, planning, technical criteria and management controls to meet the satellite compatibility requirements. CONTENTS The EMC / ESD control plan shall comprise at least the following subjects: - EMC / ESD program management - EMC / ESD documentation (to be generated by the Prime Contractor and subcontractors) - EMC / ESD control activities - EMC / ESD design criteria/techniques - test and verification concept See also ND3 Annex A.


2.11.4 D-EL4 - Satellite Level Grounding Diagram PURPOSE OF DOCUMENT Depicts the satellite level grounding concept. CONTENTS The document shall report the satellite grounding concept to sufficient detail at unit, assembly, harness and structure level.


2.11.5 D-EL5 – EMC / Magnetic / ESD / RFC Analysis PURPOSE OF DOCUMENT To analyse in depth the proposed EarthCARE design concept concerning EMC and RFC critical areas. Furthermore, all necessary analyses/trade-off’s shall be performed to establish the basic EMC/RFC design and test requirements. These analyses shall form the baseline for deriving the satellite level EMC/RFC requirements. CONTENTS Satellite EMC / Magnetic / ESD / RFC analysis to cover at least the following issues: - grounding concept - magnetic compatibility - conducted compatibility - radiated compatibility - radio frequency compatibility - test/verification approach (unit to satellite)


2.11.6 D-EL6 - EarthCARE Frequency Plan PURPOSE OF DOCUMENT To provide the complete list of all the frequency generated on-board EarthCARE satellite, i.e. including all the frequencies generated both by platform and payload. Such list will be used to verify some EarthCARE EMC specifications requirements and during various level EMC test. As such the EarthCARE Frequency Plan is a key document/tool for identifying sources of potential interferences. CONTENTS The list shall include all frequencies intentionally generated on-board EarthCARE, i.e. covering both platform and instrument equipment. Through tables, each frequency input shall identify and list per increasing order, with at least the following information:

• Frequency (incl. min/max deviation) value and unit (e.g. 2200-2290 MHz) • Description of Frequency Source (e.g. S-band Down-link) • Signal level and unit (e.g. 30 dBm • Equipment (e.g. Transponder)

The document shall also refer to any reserved/not allowed frequencies as e.g. the launcher ones. Each document issue shall provide a conclusion reflecting the actual situation and in particular any potential interference and way forward to solve them, if applicable.


2.11.7 D-EL7 – EarthCARE Harness and Test Harness Specification PURPOSE OF DOCUMENT To specify the requirements for the satellite harness and the test harness. CONTENTS To be proposed by the contractor and agreed by the Agency


2.12 Operations Support Related Documents

2.12.1 D-ES1 - Satellite Mission Analysis PURPOSE OF DOCUMENT Mission analyses for all the launcher options. CONTENTS For all the pre-selected launchers (in [D-LA1]), the document shall provide mission analysis data to the Agency together with the necessary support to ESA for its implementation in the ground segment. The mission analyses shall cover mission profiles from lift-off to end of mission. Outputs from mission analyses will include the mathematical Delta-V requirements, tracking requirements in terms of accuracy, eclipses, solar/earth aspect angles, star coverage, ground station visibility and launch window. This shall follow the structure below: 1. OVERVIEW 1.1 Purpose of the Document This document compiles the mission analysis tasks, which are usually required for the implementation of the Ground Segment Design and the formulation of the Operations Concept of the EarthCARE Mission. 1.2 Mission Description A short mission description should be included here containing mission objectives, mission instruments, mission phases. 1.2.1 Mission Purpose 1.2.2 Platform Summary Description 1.2.3 Payload Summary Description 1.2.4 Ground Segment Summary Description. Ground Stations Network 1.2.5 Mission Phases Description (LEOP, Commissioning, Routine, Extended, End of Life) 1.3 Overall Mission Requirements The following subsections should summarise the main requirements applicable to the mission analysis tasks collected from the SRD and the MRD. 1.3.1 Scientific or Application Requirements 1.3.2 Spacecraft Requirements 1.4 Overall Mission Constraints This Section should summarise the main constraints collected from the SRD and the MRD 1.5 Applicable and Reference Documents 1.5.1 Applicable Documents 1.5.2 Reference Documents 1.5.3 Applicable Standards 1.6 Acronyms 2. GENERAL ASSUMPTIONS AND MODELS 2.1 Basic Spacecraft Data Dry mass, wet mass, payload mass, dimensions, stabilisation, description of platform subsystems (thermal, power, AOCS, propulsion, data handling, …) 2.1.1 Spacecraft Reference Frames Definitions Reference axis description and drawings 2.2 Orbit Perturbations 2.2.1 Gravity Field Model used, number of terms in the description of the gravitational potential 2.2.2 Air Drag 2.2.2.1 Modelisation Model used for the drag force, reference cross-section surface, space weather assumptions (solar activity, geomagnetic activity). 2.2.2.2 Ballistic Coefficient


Explanation on computations made in order to derive the ballistic coefficient 2.2.3 Solar Radiation Pressure Solar radiation pressure model, reference surface, reflectivity coefficient, … 2.2.4 Third Body Perturbations Third massive bodies and models considered (Sun, Moon, point mass, …) 2.2.5 Other Mission Relevant Perturbations 2.3 Selection of Operational Orbit Trade-off performed for the selection of the operational orbit. 2.3.1 Ascent Trajectory, Injection Sequence and Injection Orbit Ascent trajectory description according to Launcher authorities data, if available. If not available, then ascent trajectory reconstruction if relevant for early operations phase. Description of Injection sequence (start/end of thrust of rocket upper stage, attitude change, impulses for s/c release, s/c attitude after injection, injection orbit attained). 2.3.1.1 Injection Errors (orbit and attitude) Values and tolerances 2.3.1.2 Spacecraft Illumination (Solar Aspect Angle, Beta Angle) 2.3.1.3 Eclipse Profile 2.3.2 Reference Orbit Definition Selection of the reference orbit, keplerian orbital elements defining the reference orbit, perturbations included in the propagation. 3. LAUNCH AND EARLY ORBIT PHASE 3.1 Launcher Selection Process Trade-off performed for the launcher selection based on launcher performances, fairing volume, cost, availability, reliability. 3.1.1 Launcher Description and Constraints Country of origin, company offering the launch services, number of stages, type of propellant, launcher performances for the desired target orbit, launcher dimensions, launch window constraints if any, other constraints if any (i.e. ascent trajectory to be covered by ground stations belonging to the service provider, launch azimuth limitations, illumination/coverage of burns) 3.2 LEOP Constraints Maximum duration of eclipses, battery power limitations, constrained values for the Solar Aspect Angle, communications angle constraints, minimum altitude, safety angles of line of sight of instruments w.r.t. the Sun, the Moon, the Earth. 3.3 Initial Ground Track and Ground Station Coverage Ground stations network selected for the LEOP coverage. Plot of initial ground track with visibility circles for the ground station coverage. 3.4 LEOP Sequence (Timeline including manoeuvring and transfer phase) Attitude acquisition, list of orbit and attitude manoeuvres planned, deployment of appendages like solar array, instruments, antennae, or booms. Ground stations AOS/LOS list. 3.5 Eclipse Analysis during LEOP Eclipse pattern and duration if occurring during LEOP 3.6 LEOP Delta-V Budget Delta-V budget estimate for LEOP. Assumptions made (i.e. impulsive manoeuvres, gravity losses, specific impulse of propellant, fixed thrust direction or orientable) 4. OPERATIONAL ORBIT 4.1 Reference Orbit Reference Orbit description, change in reference orbit along the mission if any. Provide Orbital elements and foreseen epoch. Baseline scenario description. 4.1.1 Reference Orbit Constraints Semi major axis, eccentricity, inclination, right ascension of ascending node, or argument of perigee constraints. 4.2 Orbit Control Requirements Dead bands for the different orbital elements. 4.3 Orbit Control/Maintenance Strategy Orbital parameters to be controlled. 4.3.1 Orbit Evolution Analysis of orbital elements evolution with time. (Lifetime propagation, propagation in arcs between manoeuvres, …) 4.3.2 Permitted Orbital Parameter Drift 4.3.3 Orbit Correction Manoeuvres Type of manoeuvres, thrusters/engine performing the manoeuvres, criticality of the manoeuvres.


4.4 Operational Orbit Control/Maintenance Implementation Preferred scheme for Orbit control/maintenance should be explained here. Trade-off between scientific requirements, spacecraft needs and operational constraints should be stated here. 4.5 Ground Station Coverage Analysis of ground station coverage from routine stations during the nominal (routine) phase. Number of blind orbits. Average duration of visibility passes per day. Minimum elevation considered. Conflict with other mission if data is available. 4.6 Eclipse Analysis Eclipse of the Sun by the Earth or the Moon analysed along the lifetime. Maximum eclipse time in umbra and penumbra. Repetition of eclipses. Time available for recharging the batteries. 4.7 Constellations In case of satellites forming a constellation, the specific constellation analysis should be done depending on the requirements (e.g. figures of merit, simultaneous coverage from ground station, data downlink strategy, collision risk analysis, Earth’s surface coverage issues). 4.8 End of Life Operations. De-orbit Strategy De-orbit strategy. Compliance with Space Debris avoidance regulations. 4.9 Lifetime Delta-V Budget A delta-V budget shall be generated for the nominal and extended mission. Delta-V for orbit corrections, for manoeuvring into the different mission phases, attitude manoeuvres, navigation manoeuvres, attitude reacquisition manoeuvres, collision avoidance manoeuvres, extended mission and de- or re-orbit manoeuvres shall be considered. 5. MEASUREMENT RETURN 5.1 Instrument Description Number and purpose of the instruments on board. Description focused on operational implications (e.g. pointing accuracy) 5.2 Instrument Constraints Angles of bright objects to line of sight, contamination, other constraints. 5.3 Instruments Data Production Data volume produced by the instruments. Timeline for data download. 5.4 Orbit and/or Attitude Constraints on the Instruments 5.5 Measurements strategy Any planning or strategy for the measurement scheme should appear here. 5.6 On-board Data Management This section should deal with science data compression mechanisms, on-board memory capacity, avoidance of science data losses, on-board science data storage policy, protocol for recovery of lost science data during downlink. This section should also describe the management of real time and playback HKTM and the downlink procedure. 5.7 Download Strategy The downlink strategy for recorded housekeeping TM should be described in this section The science data downlink strategy should be described in this section. 5.7.1 Ground Station Network Selected Routine ground station network selected. Short station description. 5.7.2 Ground Station Availability Analysis on ground station availability and conflict with other missions should appear here. 5.7.3 Data Products Timeliness Requirements on the housekeeping/scientific data distribution. 5.7.4 Frequency Band and Frequency Allocation Frequency band to be used and any concern on frequency allocation problems should be stated here. 5.7.5 Required Data Rate 6. CONCLUSIONS Evaluation of the compliance of the mission orbital design with the mission top requirements, the intended spacecraft design, and the intended ground segment design.


2.12.2 D-ES2 - Satellite Operations Constraints PURPOSE OF DOCUMENT Identifies operational constraints stemming from the chosen satellite design. CONTENTS The document shall identify operations constraints stemming from the satellite conceptual design taking into account the payload operational limitations and requirements. It shall also identify any operational conflicts between different elements of the satellite and/or instrument. It shall identify potential impacts on the satellite design and propose to the Agency an appropriate course of action to resolve those conflicts.


2.12.3 D-ES3 - Satellite Operations Timeline PURPOSE OF DOCUMENT The document shall define an up-to-date timeline of satellite (including the payload), system/sub-system-operations from launch through to the end of the mission. CONTENTS To be proposed by the contractor and agreed by the Agency


2.12.4 D-ES4 - Satellite Operability Report PURPOSE OF DOCUMENT Justifies the satellite operations concept. CONTENTS The document shall demonstrate that the Satellite is safely operable at low cost. It shall demonstrate that the on-board mission timeline requires no nominal updates, and that the satellite can survive autonomously without ground intervention. It shall show that requirements for ground intervention are reliably, simply and unambiguously identified in telemetry


2.12.5 D-ES5 - RF Suitcase Operations Manual PURPOSE OF DOCUMENT Contains the necessary information for the use of the RF suitcase. CONTENTS The RF suitcase operations manual shall be delivered together with the RF suitcase model. It shall describe the design of the RF suitcase, its external interfaces and all necessary information for the operation and the maintenance of the RF suitcase.


2.12.6 D-ES6 - Flight Operations Manual PURPOSE OF DOCUMENT To define in full detail, the on-orbit operation and control procedures of the satellite, its modules, sub-systems and instrument. CONTENTS The Flight Operations Manual contents shall be in accordance with Annex D (Space Segment User Manual) of ND32. The Flight Operations Manual shall be structured as a top level overall satellite part and a set of lower level flight operations manuals covering SVM/PLM module and/or sub-systems and EarthCARE instruments. The satellite FOM shall cover as a minimum: - the mission objectives and a complete description of the different mission phases, including LEOP, and

required operations - a description of the overall satellite and the ground segment as far as the satellite to ground operations and

control interfaces are concerned - a full description of the on-board system and control functions incorporating a summary of details provided in

lower level FOM’s. - a description of the satellite to ground interface for telemetry and telecommand purpose, operational

procedures and constraints, failure situations, failure recognition and failure recovery procedures (Incl. FMECA).

- a set of annexes covering satellite dynamic and mass properties, detailed resource details, power consumption and thermal predictions, telemetry and telecommand sheets, drawings.

Lower level FOM’s shall cover as a minimum: - the detailed design description down to the level of functional and block diagrams of equipments/units - operational modes, redundancy and cross-strapping concepts, a full description of command and control

functions down to equipment/unit level and ground monitoring needs. - physical configuration and accommodation including external and major internal electrical/mechanical

interfaces/interconnections as well as alignment data, mass and dimensional properties down to unit level - source packet description and formatting - detailed telemetry and telecommand sheets (in agreed structure) - on-ground operational procedures and constraints, FMECA also describing failure recognition and recovery

procedures. Expected minimal content for deliveries:

Issue 1: This issue shall be representative, at least of design description and draft nominal operations. Issue 2: This issue shall contain the mission description, the system and subsystem sections and all the design

information, all nominal operating procedures and draft important contingency procedures. Issue 3: This issue shall contain all nominal and contingency procedures. The Annexes shall be supplied in draft

form. Issue 4: Final version of the Manual; all sections and annexes shall reflect the latest state of knowledge of the

Flight spacecraft. Structure of the document shall be: 1. Introduction This includes the list of reference documents used to produce the FOM Volume. 2. Functional Characteristics


2.1 Functional Objectives which gives a brief overview of the purpose or mission of the subsystem covered by the FOM volume. 2.2 Principle of Operation which describes how the above purpose or mission is achieved and includes a summary of the relevant performances. 3. Configuration 3.1 Hierarchical Configuration which explains how the FOM Volume fits into the overall FOM hierarchy and how the concerned subsystem relates to the overall spacecraft. For example: Volume 1 Satellite Volume 2 Command & Data Management Volume 3 Power Volume 4 AOCS and Propulsion Volume 5 RF Comms Volume 6 Thermal Volume 7 Payload X 3.2 Physical Configuration which describes all physical units and assemblies including their location on the spacecraft, structural and physical layout, associated thermal control hardware and location, fields of view and zones of impingement and deployment / release mechanisms. 3.3 Functional Configuration which gives a functional block diagram of the subsystem together with a detailed description of the subsystem function and the individual units and assemblies functions. 3.4 Redundancy which describes the subsystem redundancy and cross strapping. 4. Modes 4.1 Mode Descriptions which identifies and describes all the subsystem modes and mode characteristics including the used units and functions. 4.2 Mode Transitions which describes all the allowed mode transitions. 5. Operational Interfaces 5.1 Control Signals which describes all control signals, including actions and timings. This also includes time synchronisation. 5.2 Command Mechanisms which describes the command and control interfaces logically and physically including description of command transfer protocols. 5.3 Telemetry Mechanisms which describes the telemetry interfaces logically and physically including description of telemetry transfer protocols. 6. Operations and Constraints 6.1 Routine Operations which outlines the nominal operation (routine commanding, maintenance and calibration) including operational timelines. 6.2 Launch, Initial Switch-On and In-Orbit Check Out which lists all the operational constraints and limitations regarding launch, initial switch on and in orbit checkout (e.g. deployments, releases, switch-on, in-orbit calibration and verification). This includes description of deployment / switch-on sequences where relevant. 6.3Safe Mode which lists all the operational constraints and limitations regarding safe mode operations. 6.4 Operations and Constraints For Ground Initiated Reconfigurations which describes all operations and related operational constraints and limitations for ground initiated reconfigurations (i.e. main to redundant, redundant to main, cross-strapping). 6.5 General Constraints and Limitations which identifies and quantifies all operational constraints and limitations not already covered in the previous sections. In particular this will include: -satellite attitude and altitude; -shocks; -in-orbit acceleration; -thermal; -Sun illumination; -out-gassing; -contamination; -life limited items. 7. Command and Control which identifies all relevant command information not included in the SDB such as; -command function description (including sequence of actions performed); -command mode dependency; -command execution duration; -command parameter meaning and how to compute / set it;


-any command specific constraints. 8. Observability which describes all TM packets, their generation trigger and rate and the relative age of the TM data in the packet with respect to the packet header time. The meaning and behaviour of the each TM parameter is also described. 9. Software which for each processor gives -an overview of the memory map -the method and constraints for dumping memory to the ground; -the method for obtaining the checksum of specified areas of the memory; -the method and constraints for patching memory from the ground; -a task description mapping SW tasks to software modules; -an overview of the SW scheduling and use of interrupts; -detailed description of any patches to be uplinked. 10. Routine Monitoring and Error Handling 10.1 Routine Monitoring which lists and describes the monitorings performed, including frequency, trigger thresholds and filter values, justification for the monitoring and identifier of the corrective action. This covers monitoring internal to the subsystem, on-board but external to the subsystem and ground monitorings. Ground monitorings are described in the form of procedures. 10.2 Corrective Action which describes all the corrective actions performed either internally, onboard externally or by ground. Ground corrective actions are described in the form of procedures. 11. Failure Analysis which defines the logical flow of activities to isolate an onboard failure starting from the anomaly message in the TM. 12. Nominal Procedures 13. Contingency Recovery Procedures 14. On-Ground Operation which describes all aspects of on-ground operation at satellite level. This is primarily intended for AIT use but may also be of interest to ESOC for SVT preparation. 15. Budgets which contains all operationally relevant budgets. Annex 1. Detailed Configuration Drawings Annex 2. Internal Event Tables Annex 3. Command and Control Diagrams Annex 4. Logic Diagrams and Truth Tables Annex 5. Source Code


2.12.7 D-ES7 - SRDB ICD PURPOSE OF DOCUMENT Defines the exchange formats of the SRDB files. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the SRDB files e.g. at ESOC. This shall include a complete description of the physical and electronic data exchange and the format and layout of all database files, so that their contents can be read and installed.


2.12.8 D-ES8 - ICD for Onboard Software Delivery PURPOSE OF DOCUMENT Defines the exchange formats of the Onboard Software files. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the Onboard Software files e.g. at ESOC. This shall include a complete description of the physical and electronic data exchange and the format and layout of all product files, including the structure of the source code files, linker map files, etc.


2.12.9 D-ES9 - ICD for HK Telemetry Delivery PURPOSE OF DOCUMENT To define the format and the exchanging mechanism for the spacecraft housekeeping telemetry, recorded during the AIT activities. CONTENTS The document shall contain the complete set of information necessary for the successful utilisation of the HK telemetry data during the development of the Operation Control Centre software. This shall include a complete description of the physical and electronic data exchange and the format and layout of the provided data files.


2.12.10 D-ES10 – Flight Dynamics ICD PURPOSE OF DOCUMENT To define the format and the transfer mechanism for the AOCS subsystem data bank to ESOC. CONTENTS The document shall contain the complete set of information necessary for the successful utilisation of the AOCS subsystem data bank at ESOC. This data bank will be used to prepare operations related to EarthCARE flight dynamics. This shall include a complete description of the physical and electronic data exchange and the format and layout of the provided data files.


2.12.11 D-ES11 - EarthCARE Space to Ground Data ICD PURPOSE OF DOCUMENT To define the data interfaces between the EarthCARE satellite (including the instruments) and all S band and X band ground stations. Note: To minimise duplication and inconsistencies, D-ES11 document may be combined with the on-board data communication ICD as long as it is clearly instantiated between data interface definitions which apply to space-ground and on-board communications and provides an exhaustive list. CONTENTS Satellite to Ground Segment data I/F definition, including instruments and S band and X band ground stations. This document shall contain: - EarthCARE system overview - Ground segment overview - On-board data communication architecture and interfaces - On-board SW capabilities overview - Monitoring and control concept (incl. FDIR) - Space to Ground RF ICD reference and summary - CCSDS source packet and generalities - Communication Protocol

- HW & SW interfaces - TM (incl. Science)/TC Packet format & content - Event detection & action execution & monitoring functions - APID allocation, …

- Time synchronization & datation requirements - Verification of the time synchronization & datation - Specific operational requirements - Reference profile assumptions - Auxiliary information - Data base interface - Compatibility Satellite to Ground Segment test requirements


2.12.12 D-ES12 - EarthCARE Space to Ground RF ICD PURPOSE OF DOCUMENT To define the RF interfaces between the EarthCARE satellite and all S band and X band ground stations. CONTENTS Satellite to Ground Segment RF (S band and X band) I/F definition, including: - EarthCARE system overview - satellite and orbit definition - On-board RF communication sub-system architecture and interfaces - Ground station network (LEOP, routine GS) and front-end interfaces - Operational Utilisation and Modulation modes - Performance requirements - Telecommunication (incl. TTC & Science)

- Uplink/downlink parameters: frequency, turn-around ratio, bandwith, modulation, EIRP, G/T, polarization, sub-carrier, BER, data rate, … - Slant - Link budget (summary showing margins and PFD)

- Ranging and interface - Telemetry (incl. Science) and Telecommand structures: - TM Transfer Frame format (length, header & trailer definition, S/C ID, VC list and bandwith allocation table, RS & error protection features, … ) - TM Packet structure (incl. HPTM packet format & rate) - TC Transfer Frame format (length, header & Frame Error Control definition, S/C ID, VC list, MAP, …) - TC Packet structure (incl. HPC-1 Packet format and utilisation) - Time synchronization requirements - Verification of the time synchronization - Specific operational requirements - Reference profile assumptions - Ranging - auxiliary information - Compatibility Satellite to Ground Segment test requirements (including suitcases).


2.12.13 D-ES14 - Flight Procedures ICD PURPOSE OF DOCUMENT This document shall provide guidelines how to understand and use the procedures – Structure, Information Contents, Interface, Validity, etc. to allow their usage during operations. CONTENTS To be proposed by the contractor and agreed by the Agency


2.12.14 D-ES15 – SRDB Specification PURPOSE OF DOCUMENT To specify the requirements for the satellite reference database. CONTENTS To be proposed by the contractor following the tasks identified in the SOW and agreed by the Agency.


2.12.15 D-ES16 – SRDB-A and SRDB-B Description PURPOSE OF DOCUMENT To describe the structure and contents of the database and data contents elements of the satellite reference database. CONTENTS To be proposed by the contractor following the tasks identified in the SOW and agreed by the Agency.


2.12.16 D-ES17 – LEOP Plan and LEOP Operation Timeline PURPOSE OF DOCUMENT To specify the Launch and Early Operations Phase plan and its associated timeline of activities and milestones. CONTENTS To be proposed by the contractor and agreed by the Agency


2.12.17 D-ES18 – LEOP and IOV Report PURPOSE OF DOCUMENT To report the results of the LEOP and In-Orbit Verification activities. CONTENTS To be proposed by the contractor and agreed by the Agency


2.13 Launcher Interface Related Documents

2.13.1 D-LA1 - Launcher Survey Document PURPOSE OF DOCUMENT Identifies and evaluates viable launcher options for the EarthCARE mission. CONTENTS The document shall identify and evaluate all viable launchers compatible with the launch mass and orbit parameters of the EarthCARE satellite. More detailed study results for the selected launchers (in consultation with the Agency) shall be presented.


2.13.2 D-LA2 - EarthCARE Spacecraft to Launcher IRD (Dnepr) PURPOSE OF DOCUMENT To define the EarthCARE requirements with regard to orbit injection requirements, dynamic and thermal environment, accessibility, RF transparency and umbilical cables of the Dnepr launcher, which shall serve as the customer's input to the launch system. CONTENTS To define the satellite requirements on the launcher system in terms of: - mission characteristics and constraints - spacecraft launch and flight configuration - spacecraft mechanical properties and interfaces - thermal interfaces - operational interfaces and safety - umbilical link electrical interfaces and grounding - RF transparency - environmental requirements during on-ground handling and storage and launch preparation and launch phase - contamination requirements - launch facilities interfaces


2.13.3 D-LA3 - EarthCARE Spacecraft to Launcher IRD (ROCKOT) PURPOSE OF DOCUMENT To define the EarthCARE requirements with regard to orbit injection requirements, dynamic and thermal environment, accessibility, RF transparency and umbilical cables of the Rockot launcher, which shall serve as the customer's input to the launch system. CONTENTS To define the satellite requirements on the launcher system in terms of: - mission characteristics and constraints - spacecraft launch and flight configuration - spacecraft mechanical properties and interfaces - thermal interfaces - operational interfaces and safety - umbilical link electrical interfaces and grounding - RF transparency - environmental requirements during on-ground handling and storage and launch preparation and launch phase - contamination requirements - launch facilities interfaces


2.13.4 D-LA4 - EarthCARE Spacecraft to Launcher IRD (Soyuz) PURPOSE OF DOCUMENT To define the EarthCARE requirements with regard to orbit injection requirements, dynamic and thermal environment, accessibility, RF transparency and umbilical cables of the Soyuz launcher, which shall serve as the customer's input to the launch system. CONTENTS To define the satellite requirements on the launcher system in terms of: - mission characteristics and constraints - spacecraft launch and flight configuration - spacecraft mechanical properties and interfaces - thermal interfaces - operational interfaces and safety - umbilical link electrical interfaces and grounding - RF transparency - environmental requirements during on-ground handling and storage and launch preparation and launch phase - contamination requirements - launch facilities interfaces


2.13.5 D-LA5 - EarthCARE Spacecraft to Launcher IRD (VEGA) PURPOSE OF DOCUMENT To define the EarthCARE requirements with regard to orbit injection requirements, dynamic and thermal environment, accessibility, RF transparency and umbilical cables of the launcher VEGA, which shall serve as the customer's input to the launch system. CONTENTS To define the satellite requirements on the launcher system in terms of: - mission characteristics and constraints - spacecraft launch and flight configuration - spacecraft mechanical properties and interfaces - thermal interfaces - operational interfaces and safety - umbilical link electrical interfaces and grounding - RF transparency - environmental requirements during on-ground handling and storage and launch preparation and launch phase - contamination requirements - launch facilities interfaces


2.14 Management Related Documents

2.14.1 D-MA2 - Sub-Contractor Procurement Packages PURPOSE OF DOCUMENT To specify all work to be performed in Phase C/D by selected subcontractors. CONTENTS ITT to include as a minimum: - Statement of Work - contract - all requirement specifications (unless otherwise provided) - all supporting documentation necessary for the fulfillment of the task


2.14.2 D-MA3 - Industrial Procurement Plan PURPOSE OF DOCUMENT Defines the process and specific sequence the Prime Contractor intends to use in selecting subcontractors, as well as the specific potential subcontractors CONTENTS The following content is the minimum requirement for this plan (that will constitute for the version to be submitted at the time of the offer the preliminary make or buy plan): - Introduction - Items directly made or carried out by the prime contractor - Items to be purchased or subcontracted Items to be subcontracted under Prime responsibility Items to be sub-contracted under other subcontractors responsibility - Identification of potential bidders - Procurement, planning of activities General ITT activities and relationship to trade off and engineering activities Procurement logic for significant items (item by item) ITT Planning For each item indicate the level of maturity (Class A to D) and identify the necessary developments (if applicable) For off the shelf subsystem or unit fill the document [D-SA4]


2.14.3 D-MA4 - Long Lead Items List PURPOSE OF DOCUMENT Identification of Long Lead Items. CONTENTS The Long Lead Items list shall fully identify all parts and materials that have excessive procurement cycles which may lead to schedule drivers for the EarthCARE project. The list shall also identify intended delivery dates of the identified items and provide a reference to detailed procurement information.


2.15 Mechanism Related Documents

2.15.1 D-ME1 - Mechanism Design and Performance Requirements Specification

PURPOSE OF DOCUMENT To define a common set of mechanisms design definitions, requirements and rules for use in design activities at satellite, payload and platform instrument/sub-system and equipment level. CONTENTS Mechanisms design requirements in terms of: - mechanisms configuration and architecture - dimensioning rules (including the definition of all safety factors and design / qualification / acceptance

mechanical loads, environment accelerations and temperature ranges and relevant margins) - mechanisms performance requirements - common design and construction requirements (e.g. materials, lubrication, etc...) - mechanisms analysis requirements (including torque margin, functional analysis, static, dynamic, stress and

thermal distortion and structure interfaces) - mechanisms analysis campaigns identification and implementation logic - maintenance and verification requirements.(including reference configuration and coordinate system) - mechanism heritage description


2.15.2 D-ME2 - Mechanism Description Report PURPOSE OF DOCUMENT Describes the design of the mechanisms as part of [D-SA9] CONTENTS Describes the design of the mechanisms. Describes the lubrication system used. Gives top assembly drawings and cross-section drawings. Describes the way the mechanism works. The description shall include an assessment of : functions, failure tolerance, manufacturing, integration (including alignment), storage, testing configuration and maintenance Describes mechanism heritage.


2.15.3 D-ME3 - Mechanisms Analysis Report PURPOSE OF DOCUMENT Describes analyses performed as part of [D-SA3]. CONTENTS Describes the mechanical and electrical analyses performed on the mechanisms. They shall demonstrate that all requirements are fulfilled for all mission phases and in the natural environment encountered. This shall include: - functional, - performance, - accuracy, - torque margin and disturbance analyses, - stress analyses (including contact stresses). Thermal distortion and pointing analyses to support the pointing budgets shall also be performed.


2.15.4 D-ME4 - Mechanisms Test Assessment Report PURPOSE OF DOCUMENT Describes and assesses the performed mechanisms tests as part of [D-SA3]. CONTENTS Reports assessment results of the mechanism tests performed. This shall include: - life, - torque margin, - performance and - accuracy.


2.16 Mission Analysis Related Documents

2.16.1 D-MI1 - Mission and Operations Definition PURPOSE OF DOCUMENT Defines the operational concepts for all mission phases and modes. CONTENTS The document shall define a satellite mode sequence for initial deployment in orbit during the Launch and Early Orbit Operations phase. The document shall define a concept for nominal operations of the spacecraft. In defining this requirements for on-board scheduling of recording and recorder dumps, of nominal instrument measurements and of regular, cyclic instrument calibration shall be considered. It shall be considered whether orbital or seasonal variations of illumination conditions need to be taken into account. The document shall specify which controlling parameters of the on-board task sequence shall be changeable on ground command. It shall also define an orbit maintenance strategy such that the orbit can be maintained without interrupting nominal operations. The document shall define a concept for spacecraft operation in the event of on-board anomalies, describing how the satellite can automatically detect and react to an on-board anomaly in order either to recover and continue nominal operations or to enter contingency modes. Any associated sequence of ground intervention necessary to fulfil this task will be defined as well.


2.17 MSI Instrument Related Documents

2.17.1 D-MS1 - MSI Requirements Specification PURPOSE OF DOCUMENT To specify design at instrument level in terms of performance, interface specifications and verification requirements. CONTENTS Instrument design specifications in terms of: - functional requirement - units breakdown - performance requirements - electrical requirements (signals, power, telemetry, telecommand, data handling,...) - mechanical requirements - thermal requirements - interface requirements - environmental requirements - operational requirements (e.g. reliability and lifetime) - EMC, DC/AC magnetic design and test requirements - EGSE/MGSE/OGSE requirements - PA (including model philosophy) - summary test sequence and detailed test matrices


2.17.2 D-MS2 - MSI ICDs PURPOSE OF DOCUMENT To define all the requirements on MSI instrument specific interfaces, mechanical, thermal, electrical, environmental and operational, between the instrument and the EarthCARE satellite. CONTENTS Interface specifications in terms of: - general requirements - electrical interfaces (including power supply interfaces, command and control I/F, timings, datation, pyros





2.17.3 D-MS3 - MSI Performance Model Description and Predictions PURPOSE OF DOCUMENT To study the expected performance of the MSI instrument based on reference input scenes and thereby demonstrate the ability of the instrument to comply with specified performances. CONTENTS The document should contain as a minimum: - Instrument performances requirements summary - list of parameters influencing the performance - mathematical formulation of the problem - exhaustive description - sensitivity to parameters - results budgets - user manual.


2.17.4 D-MS4 - MSI Ground Calibration Facilities Specification PURPOSE OF DOCUMENT To specify the external calibration for establishing the absolute calibration of the MSI instrument. CONTENTS - general function - operational requirements - functional requirements - performance requirements - interfaces requirements - mechanical and environmental requirements - validation/calibration and test requirements - maintenance requirements - reliability requirements - software requirements - communication requirements - safety requirements - installation requirements - transportation requirements


2.17.5 D-MS5 - MSI Design, Development and Verification Plan PURPOSE OF DOCUMENT To define the overall instrument design/development philosophy from engineering design through integration, verification and calibration while taking into account schedule and programme constraints. CONTENTS - instrument requirements and constraints - hardware and software breakdown - margin philosophy - instrument verification concept - description of development activities (covering manufacturing, integration, test calibration/characterization and



2.17.6 D-MS6 - MSI AIV Plan PURPOSE OF DOCUMENT To define and control the MSI instrument assembly, integration, test and verification plan. To define the full qualification and acceptance test programs from instrument level down to equipment level. CONTENTS Integration Plan in terms of integration approach, methods and responsibilities. Qualification and acceptance test program definition in terms of: - test philosophy - test conditions - hardware/software matrices - qualification test program - acceptance test program - test plan and methods - PA provisions - GSE needs - AIV/AIT planning, flow chart and test sequences - verification and test matrices


2.17.7 D-MS7 - MSI Technical Description PURPOSE OF DOCUMENT To describe the MSI instrument design and its operational, functional and performance characteristics. CONTENTS Instrument description in terms of: - instrument design principle - operational modes - functional modes - performances - block diagram down to equipment level with description of each equipment block and performances - electrical interfaces - ground processing algorithm assumptions - mechanical design - thermal design - power distribution - command/control concept (including datation) - timing diagram - on-board processing - software architecture (including lower level spec. tree and parameters) - software simulation/validation - overall configuration - harness


2.17.8 D-MS8 - MSI Ground Calibration Facilities Description, Test and Calibration Report

PURPOSE OF DOCUMENT To describe the MSI instrument on-ground calibration facilities design and their operational, functional and performance characteristics and to summarize the results of the test and calibration performed on these facilities. CONTENTS - ground calibration facilities description and characteristics - operational modes - functional modes - performances - block diagram and description of each module - interface description - mechanical, electrical, environmental design - calibration description - test description - calibration report - test report


2.17.9 D-MS9 - MSI Instrument Budgets PURPOSE OF DOCUMENT To provide the budgets of the Atlid instrument (mass, power, telemetry, performance, etc.). CONTENTS All instrument budgets in support to the contents of [D-SA6], and furthermore all the instrument specific performance parameters.


2.17.10 D-MS10 - MSI Calibration and Characterization Data Base PURPOSE OF DOCUMENT To provide all the information pertinent to the use of the calibration/characterization parameters to be injected within the ground processing algorithms. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the database. This shall include a complete description of the physical and electronic data exchange and the format and layout of all database files, so that their contents can be read and installed. For each calibration and characterization parameter, a form sheet indicating: - file name of the calibration/characterization - instrument configuration identifier - parameter file (look-up tables) - environmental conditions - reference to the test set-up configuration and test date/time


2.17.11 D-MS11 - MSI IOV Plan PURPOSE OF DOCUMENT To provide all the information needed to verify the in-orbit instrument functionality, verification and characterization of the instrument in-orbit performance, verification of the consistency of Ground processor processing and level 1a and level 1 b products. CONTENTS IOV Plan in terms of approach, methods and responsibilities. Schedule and phasing approach. Data flows during IOV phase Instrument verification program definition in terms of: - in-orbit verification philosophy - instrument constraints during IOV phases - hardware/software matrices - thermal aspects verification program - power aspects verification program - functional aspects verification program - performance aspects verification program - verification plan and methods - PA provisions - Verification sheets - Verification report - Verification matrices


2.17.12 D-MS12 - MSI Flight Operation Manual PURPOSE OF DOCUMENT To define in full detail the in-orbit operation and control procedures of the instrument. CONTENTS - detailed design description down to the level of functional and block diagrams - operational modes, redundancy and cross-strapping concepts - full description of command and control functions - physical configuration and accommodation including external and major internal electrical/mechanical




2.17.13 D-MS13 - MSI GSE Specification PURPOSE OF DOCUMENT To establish the requirements for the instrument GSE. CONTENTS - GSE definition (general and specific requirements, test levels and objectives) - Operational requirements - Interface requirements - Software requirements - List of test and performance requirements - List of STE - Hardware design and construction requirements - EMC requirements - Environmental requirements - PA - Preparation for delivery


2.17.14 D-MS14 - MSI GSE Design Report PURPOSE OF DOCUMENT To present the design of the instrument GSE and to give an assessment of the expected performance against the specification. CONTENTS - GSE design overview




2.17.15 D-MS15 – MSI ESSS and ECGP Design, Development and Verification Plans

PURPOSE OF DOCUMENT To define the overall design/development philosophy from engineering design through integration and verification and calibration for the MSI ESSS and ECGP while taking into account schedule and program constraints. CONTENTS The document should contain as a minimum: - Instrument simulator module - processor module - hardware and software breakdown - verification concept - description of development activities (covering manufacturing, integration, test, characterisation plans) - summary schedule and milestones (including reviews) - description of software activities (specification to validation)


2.17.16 D-MS16 - MSI ESSS and ECGP Module Specifications PURPOSE OF DOCUMENT Top-level specification for the MSI ESSS and ECGP modules development. These modules will be part of the system ESSS and ECGP. CONTENTS List of requirements on the MSI ESSS and ECGP, including in particular: - Simulation of the instrument - Raw Data Interface (high-level) - Level 1b Product Definition (high-level) [Draft D-AT 17] - Level 0 Product Definitions (high-level) [Draft D-AT 18] - Product Delivery interface Definition - Man/Machine interface for Processor - Automatic command and control interface for Processor - Integration with System ESSS / ECGP. Note: All low-level data definitions should go into their own docs (Science packet specifications, product format specifications)


2.17.17 D-MS17 - MSI Level 1 Product Definition PURPOSE OF DOCUMENT Defines the MSI Level 1 product. CONTENTS To be specified by contractor and to be agreed with agency.


2.17.18 D-MS18 - MSI Level 0 Product Definition PURPOSE OF DOCUMENT Defines the MSI Level 0 product CONTENTS Defines the Level 0 product, which consists essentially of instrument raw data, time ordered and quality marked.


2.17.19 D-MS19 - MSI ESSS and ECGP Users Manuals PURPOSE OF DOCUMENT To describe the MSI ESSS and ECGP hardware, software functions and interfaces to the user CONTENTS The document should contain as a minimum: - Overview of the hardware and the software to module level - Overview of the performance - Description of the man-machine and command line interfaces - Description of the data inputs and outputs, format and interpretations - Description of special operational constraints - Step-by-step example for a typical use case - Installation instructions


2.17.20 D-MS20 – MSI Algorithms Theoretical Baseline Document PURPOSE OF DOCUMENT To describe the algorithm to derive the MSI level 1 products CONTENTS To be specified by contractor and to be agreed with agency.


2.17.21 D-MS21 – MSI ECGP Reference Test Data Set Description PURPOSE OF DOCUMENT This document contains a description of the test data and file structure used to validate the processor. CONTENTS To be specified by the contractor and agreed with the Agency


2.17.22 D-MS22 – MSI SRR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the MSI Specific Requirements Review. CONTENTS The review documentation shall consist of the following two elements:

1. The review package summary providing a description of the instruments covering for each technical discipline (electrical, mechanical, thermal, command and control, data handling, AOCS, EMC/RFC, software and product assurance) an overview of:


The summary is part of the data package proper and is required in the same number of copies.

2. The baseline documents as identified for each major review in the EarthCARE Document Requirements List (DRL). The baseline documents to be provided as part of the data package proper and the number of copies will be agreed and specified in dedicated review procedures provided by the Customer. Baseline documents not included in the data package proper, however listed in the DRL as deliverable at the review milestone, shall be provided in the number of copies specified in the DRL.



2.17.23 D-MS23 – MSI PDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the MSI Preliminary Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline








2.17.24 D-MS24 – MSI CDR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the MSI Critical Design Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline








2.17.25 D-MS25 – MSI QR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the MSI Qualification Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.17.26 D-MS26 – MSI AR Data Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the MSI Acceptance Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the instruments covering for each technical discipline







2.17.27 D-MS27 – MSI Master Planning PURPOSE OF DOCUMENT To report the schedule as a result of an objective and realistic analysis of the progress made, showing an active control of the execution of the work CONTENTS ‘Similar’ to D-PM18 for the instrument. During instrument AIT, separately, a schedule shall be re-issued every week to identify the day to day activities for the next two weeks.


2.17.28 D-MS28 – MSI Risk Analysis PURPOSE OF DOCUMENT To assess and control all risks associated to the instrument and to the overall project. CONTENTS See D-PM4 for the content of the Risk Management Plan. See D-PM5 for the content of the Risk Register.


2.17.29 D-MS29 – MSI Long Lead Items List PURPOSE OF DOCUMENT Identification of Long Lead Items. CONTENTS The Long Lead Items list shall fully identify all parts and materials that have excessive procurement cycles which may lead to schedule drivers for the EarthCARE project. The list shall also identify intended delivery dates of the identified items and provide a reference to detailed procurement information.


2.17.30 D-MS30 – MSI Straylight Analysis PURPOSE OF DOCUMENT To document the analysis of the straylight and effects on the MSI instrument. CONTENTS To be proposed by the contractor and agreed by the Agency


2.18 Product Assurance Related Documents

2.18.1 D-PA1 - Product Assurance and Safety Plan PURPOSE OF DOCUMENT To document the organisation, requirements, methods, tools, resources and responsibilities for the product assurance and safety disciplines prior to development and implemented at each project level CONTENTS a) The PA plan shall describe the resources, tasks, responsibilities, methods and procedures adopted by the Contractor for the implementation of the ESA PA&S requirements and for the achievement of the PA objectives. b) The PA plan shall include the following major elements of contents: 1. Introduction:

Scope, Applicability, 2. PA management:

Objectives, Policies, Implementation Approach, Responsibilities, Organization, Reporting, Compliance with each ESA PA requirement Management of Subcontractor PA programme and activities

3. Documents: ESA requirement documents, Applicable documents, Reference documents

4. Quality Assurance: Audits, Personnel certification, Quality records, Traceability, Metrology and calibration, Nonconformance Control system, Alerts, Critical items control, Design control, Verification, Procurement control, cleanliness and contamination control, Handling, Storage, preservation, Marking, Labelling, Packaging, Shipping, Surveillance of procurement sources, Receiving inspection, In-process inspection, Process control, Workmanship standards, Temporary installation and removals, Logbook, Acceptance and delivery, Acceptance data package

5. Dependability: Dependability approach, Dependability-critical items, Dependability requirements in technical specifications, Failure consequence severity categories, Failure tolerance, failure propagation, Monitoring, Maintainability, Dependability analyses (FMECA, reliability assessment, Departing analysis), Single failure Points

6. Safety Safety approach, Safety representative, Safety analyses, Safety design principles, Safety inhibits, Design for minimum risk, Fracture control, Safety-critical items, Safety factors, Material safety, Safety documentation

7. Electrical, Electronic and Electromechanical components The contractor shall address the requirements applicable within the Contract between ESA for the procurement of EEE parts within the CPPA contract: Component control programme (component control board and plan), Component engineering, Component selection, Component approval, Component listing, Component procurement, Component quality assurance (manufacturer and component evaluation, incoming inspection, handling and storage, non-conformances and failures), Documentation

8. Materials, mechanical parts and processes Selection, Approval, Evaluation and validation, Listing, technical requirements

9. Software Product Assurance Content as defined in ND111, Annex K


2.18.2 D-PA3 – Configuration Management Plan PURPOSE OF DOCUMENT Provide information about the organisation, conduct and documentation of Configuration Management of the system. CONTENTS The CM Plan shall meet the requirements of ND52 Annex A.


2.18.3 D-PA4 - Plan of External & Internal PA & Safety Audits PURPOSE OF DOCUMENT Provide information about planned PA & safety Audits of procurement sources. CONTENTS List the audits planned by the contractor. The list shall identify subcontractors and suppliers to be audited, audit baseline, current status and schedule, periodicity. The Audit Programme Plan shall contain the following minimum information for all internal and external audits: - subcontractor / supplier to be audited - reason and criticality of the audit - baseline of the audit - planned date - status - periodicity - audit plan, checklist and report references


2.18.4 D-PA5 - Audit Report PURPOSE OF DOCUMENT To record the proceedings and outcome of an audit. CONTENTS The Audit Report shall contain the following minimum information for all internal and external audits:

• Objectives • Scope • Audit Client • Audit team members • Auditee representative(s) • Audit activities, dates & times • Audit baseline • Findings • Recommendations for improvement • Follow-up action plans • Statement of confidentiality of report • Conclusions


2.18.5 D-PA6 - Critical Items List (CIL) PURPOSE OF DOCUMENT To identify critical items from the different PA & safety disciplines, to ensure that they receive proper management actions and follow-up. CONTENTS The Critical Items List (CIL) shall contain summary information on critical areas from the following sources: - Single Point Failures; - Life Limited Items (subject to wear out, drift or degradation below minimum required performance in less than

the storage + mission time); - Hazardous Items of categories catastrophic and critical; - EEE components which are unique and for their specific function are essential for the design of a system /

subsystem, and consequently would have sever impacts on the program (delays, re-design ..) in case of unavailability or unsuitability. Critical Technologies (only those items/technologies with exceptional qualification circumstances and/or process sensitivity, not all unqualified PMP and EEE-parts);

- Items or procedures that do not comply with the applicable safety / dependability requirements, or which cannot be verified as complying with those requirements.

As defined in ND 59 Annex A, for each critical item the following information shall be provided: - Descriptive name and function/item number. - Related hazard and failure conditions (including operational phase / mode) with reference to the dependability

or safety Analysis. - Required failure tolerance or lifetime requirements. - Design failure tolerance (with rationale for retention if different from required failure tolerance) or design life

limitation. - Fracture critical items. - Critical performance characteristics. - Safety critical function supported by the item. - Recommendations for a surveillance programme. - Trace ability to requests for waiver. - Potential for elimination or reduction of criticality. - Recommendation for special manufacturing and test requirements. - Identification of operational constraints. - Results of the critical items control activities. - Rationale for retention of critical item (as applicable). - Summary of results, statement of recommendations for design changes / improvements.


2.18.6 D-PA7 - Non-Conformance Report PURPOSE OF DOCUMENT Documents the identification, investigation and disposition of project non-conformances. To provide a summary report of the current status of the NCRs raised, to aid the overall tracking of control of NCR closeout. This report shall be generated from the overall NCR database. CONTENTS Individual NCR reports shall be raised, documented and processed in accordance with the NCR control system established as defined in ND61. Periodic reporting of the overall NCR status shall be provided via NCTS. The report shall identify for each NCR, the relevant identification, opening / closure dates, classification, description & summary of investigations / closeout activities etc. The report shall also be provided in electronic data base form, which is kept regularly up to date. ESA shall have read access to this data base.


2.18.7 D-PA8 - Waiver/Deviation Requests PURPOSE OF DOCUMENT To process waivers/deviations against EarthCARE requirements. To provide a summary report of the current status of the waivers raised against EarthCARErequirements. This report shall be generated from the overall waiver database. CONTENTS Individual waivers/deviations shall be documented and raised as defined in ND 52 Annexes J and K. The waiver/deviation shall have a unique RFWRFD reference number, define the applicable requirements to be waived, present a technical explanation and justification of the waiver/deviation. Waivers/deviations will be approved at the level at which the requirements are specified. For system level requirements violating ESA requirements, the waiver shall be subject to ESA approval. Periodic reporting of the overall waiver/deviation status shall be provided. The report shall identify for each waiver/deviation, the relevant identification, opening /submittal dates, description of waiver/deviation, submittal / approval status. The report shall also be provided in electronic data base form, which is kept regularly up to date. ESA shall have read access to the database.


2.18.8 D-PA9 - Cleanliness and Contamination Control Plan PURPOSE OF DOCUMENT To define the methods, procedures and responsibilities in achieving and maintaining the cleanliness levels applicable to EarthCARE. CONTENTS As defined in ND 45 Annex H. The Contamination Control Plan shall cover at least: - Contamination allowance for performance degradation and rationale for its selection. - Cleanliness control management: tasks and responsibilities, schedule wrt. Project milestone, reporting, facilities

audits, etc. - Contamination analyses and contamination budget definition. - Contamination control requirements during fabrication, integration test, launch. - Measurements methods and cleanliness monitoring and verification activities. - Procedures for removal of contamination. - Protection methods and provisions. - Contamination controls to be exercised during testing. - Contamination controls for packaging, transportation and storage. - Requirements for subcontractors


2.18.9 D-PA10 - Qualification Status List PURPOSE OF DOCUMENT To document the qualification status and the procurement constraints for EarthCARE down to equipment level. CONTENTS For each proposed or identified satellite subsystems and equipment, the document shall:

Identify the requirements applicable for qualification Identify the current and intended qualification status with reference to existing qualification documentation

(particularly test documents), and including any relevant use history of the item (project reference, dates, qualification level, qualification standard, relevant documentation, etc.).

Provide the justification and identify the documentation for the qualification status of each item Reference any NCR, Waivers or Deviations related to the qualification article(s) or test equipment Identify activities needed to achieve qualification, including all qualification tests, status reviews, associated

schedule and status. Document and analyse the procurement conditions (schedule, component procurement, procurement

agency, purchasing licenses, country of origin, possible alternative European suppliers, etc.)


2.18.10 D-PA11 - Reliability Prediction Report PURPOSE OF DOCUMENT To document the results of reliability prediction analysis. CONTENTS The following shall be documented as a minimum:

Design baseline and description Analysis assumptions, input data and results Supporting information and analyses Statement of compliance with applicable requirements Critical Items identified from the analysis Recommendations for design (including redundancy and FDIR concepts), verification, test and operations

(as relevant) Conclusions.


2.18.11 D-PA12 - Failure Mode Effect Criticality Analysis (FMECA) PURPOSE OF DOCUMENT To identify all failure modes of the system and rank them in accordance with the severity of the effects of their occurrence. CONTENTS The FMECA shall be prepared in accordance with the procedure described in ND65 clause 4.7. A functional analysis shall be performed as part of the FMECA activity, which shall classify the system functions and products into functional categories. This analysis shall be used to establish applicable failure tolerance requirements. The FMECA shall contain general and supporting information and FMECA worksheets. General and supporting information: - Unique Reference Number, issue and date of the analysis, sign-off date and signature, and the analyst's name. - Design Baseline - the definitive reference to the design under analysis, with release information, dates, etc. of

all documents used to establish the FMECA, in particular, where available, the reference to the applicable Configuration Item Data List (CIDL).

- Assumptions - a statement of all assumptions regarding mission phases and times, operational modes, environmental conditions, failure criteria, etc.

- Reliability Block Diagram of the equipment. - Functional Description - a narrative description of the total function, and of each lower level function considered

in the analysis, to a depth sufficient to provide an understanding of the system and of the analysis. Schematic diagrams shall be included of all functional assemblies to a level consistent with the depth of the analysis, and design maturity.

- A Summary and discussion on the major findings of the analysis, and a list of recommendations. - A Status on recommendations from previous issues of the analysis, stating whether implemented or not, and

referencing the appropriate action item tracking list, supporting technical notes and reports, etc. The operational aspects shall be taken into account when performing the FMECA, as a consequence: - The failure detection field shall detail the observable symptoms in flight and during ground tests (i.e. how is the

failure observed by mission operations, with reference to the telemetry channel and the limits exceeded, and, how the failure can be detected during a scheduled test sequence)

- The compensating provisions field shall include reference to manual, telecommand or automatic corrective action that could be taken in response to a failure indication, including an explanation as to how a successful response is verified.

The FMECA shall contain S/W failure modes, effects, and criticalities and shall use for their establishment the HW/SW Interaction analysis (HSIA). The HSIA shall identify: - The effect of each H/W failure mode on the S/W operation

- All disruptions to S/W functions for each failure mode - Fault which originate in H/W and are propagated by the S/W whether or not the fault affects the S/W operation - Method of detection of faults by S/W - Methods of correction/containment of faults by S/W - The effects of S/W on H/W elements including:

o Potential damage resulting to H/W from incorrect methods of prevention of these harmful effects o Prior fault detection methods applied to the S/W functions. o Methods of controlling/containing the harmful effects of faults. o Recovery/rollback method applied

The FMECA shall consider common-mode and common cause failures.



2.18.12 D-PA13 - Availability Analysis and Prediction PURPOSE OF DOCUMENT To document the results of availability prediction analysis. CONTENTS The following shall be documented as a minimum:

Design baseline and description Analysis assumptions, input data and results Supporting information and analyses System outage sources

o Causes o Probability of occurrence o Duration o Detection & recovery method(s)

Detailed calculation of system availability Statement of compliance with applicable requirements Recommendations for design (including redundancy and FDIR concepts), verification, test and operations



2.18.13 D-PA14 - Cleanliness Requirement Specification PURPOSE OF DOCUMENT To define the cleanliness requirements of the EarthCARE system. CONTENTS As defined in ND 45 Annex G


2.18.14 D-PA15 - System and Operations Hazard Analysis PURPOSE OF DOCUMENT - To identify inherent hazards; - To highlight means to eliminate or reduce the hazard potential; - To trace all hazard control activities and to demonstrate an acceptable status prior to completion of the design

for customer approval. CONTENTSND 62 Annex B shall be used. The safety file shall contain the following: - Hazard Identification Check List; - Residual Hazard Sheets (Hazard Reports). - Additional information as required by the launcher authorities

The Hazard Identification Check List shall be completed for each equipment. If by this check list evidence is provided that equipment does not contain any hazard potential, it is not necessary to perform a detailed hazard report. It is, however, required to keep this checklist alive in order to identify hazards, which may evolve during design progress. The Residual Hazard Sheets shall document the potential hazards arising from materials, sources of energy, facilities or operations. It shall detail the nature of the hazard with its classification; it shall describe the safety considerations and/or requirements to be used for eliminating or reducing the hazard potential. The cases where a hazard is identified, but only inadequate means are available to eliminate or reduce this hazard to an acceptable level, shall be noted and a rationale for the retention shall be given for customer approval. The Safety analysis shall include all hazards, which are associated with testing, transportation, integration, handling, storage, pre-launch operations and launch up to separation.


2.18.15 D-PA16 - Software Product Assurance File PURPOSE OF DOCUMENT See ND15, Annex A.9. CONTENTS Prepare as defined in ND15 Annex A.9: Software Product Assurance Plan, Software Product Assurance reports, procedures and standards. See also ND44.


2.18.16 D-PA17 - Software Maintenance File PURPOSE OF DOCUMENT See ND15, Annex A.7 CONTENTS Prepare as defined in ND15, Annex A.7: Maintenance Plan, Mitigation Plan. See also ND44.


2.18.17 D-PA18 - Request for Approval PURPOSE OF DOCUMENT To request approval of a specific material and its application. CONTENTS As defined in ND 71 Annex E


2.18.18 D-PA19 - Parts Approval Document (PAD) PURPOSE OF DOCUMENT Collect information about parts and prepare approval CONTENTS As per ND67, clause 3.3.2 & Annex A.


2.18.19 D-PA20 - Software Criticality Analysis Report PURPOSE OF DOCUMENT To identify the criticality class of each software component in order to tailor software engineering and PA requirements. CONTENTS The Software Criticality Analysis Report shall include:

• Software Criticality Analysis approach and assumptions • System description • Mapping of software components to (sub)system functions and associated criticality • Analysis of results: classification of software components and associated justification • Design Recommendations • Conclusions


2.18.20 D-PA21 - Destructive Physical Analysis (DPA) reports PURPOSE OF DOCUMENT To report on the series of inspections, tests and analysis performed on a sample of components. The requirements for when and how to perform DPA are given ND67, clause 3.4.5 & 4.4.2. CONTENTS The report shall include the results of the series of inspections, tests and analysis performed on a sample of components as stated in ND67, clause 4.4.2.


2.18.21 D-PA22 - Declared Component List (DCL) PURPOSE OF DOCUMENT To identify all components types needed for the current design. CONTENTS As defined in ND67, clause 2.4.3.


2.18.22 D-PA23 - Radiation Analysis Report PURPOSE OF DOCUMENT To assess sensitive components regarding Total Dose (TD), Single Event Effects (SEE) and Displacement Damage (DD) in the frame of the mission and individual units’ boundary conditions (environment, duration of the mission, shielding). CONTENTS

• Mission radiation environment and constraints • Local radiation environment of each individual unit • Conditions (design margins, biasing, shielding) of all individual units • Assessment of performance impact of radiation on each unit (margins for timing, sensitivity & voltage /

current, etc; and effect on system availability) • Identification of all parts classified as sensitive to TD, SEE and DD • Recommendations for corrective action

The conclusions shall be transferred to the Worst Case Analysis / Failure Modes Effects Analysis for consideration in those analyses. The Analysis shall be consistent with the agreed classification of parts sensitivities in the EarthCARE project and shall be coherent with the Declared Components List contents.


2.18.23 D-PA24 - Certificate of Qualification PURPOSE OF DOCUMENT To identify the design baseline and justify the qualification status of a delivered item. CONTENTS As defined in ND50 Annex D, relating specifically to the design verification & qualification history, activities and results of the item.


2.18.24 D-PA25 - Certificate of Conformity PURPOSE OF DOCUMENT To identify the build baseline and justify the verification / validation / acceptance status of a delivered item. CONTENTS As defined in ND50 Annex D, relating specifically to the verification, validation and acceptance history, activities and results of the item.


2.18.25 D-PA26 - Declared Mechanical Parts List (DMPL) PURPOSE OF DOCUMENT To provide a complete list of all mechanical parts used for manufacturing of qualification or flight hardware with all relevant information and approval status. CONTENTS As defined in ND71 Annex C. In case of re-use of 'fully qualified' subsystems, boxes or items, the corresponding mechanical-parts should not appear in the system DMPL. The term 'fully qualified' means that the status of the element is traceable to a valid and complete qualification report containing a DMPL officially approved by the relevant Customer authority. This list is to be attached to the system DMPL for reference. In addition to the required paper copies, the DMP List shall be provided in a form that is exchangeable, searchable, sortable and suitable for storage and retrieval. The ESA DMPL tool, given at the following address, can be used. http://www.estec.esa.nl/tosqm/What%27sNew/what_s_new.html


2.18.26 D-PA27 - Declared Material List (DML) PURPOSE OF DOCUMENT To provide a complete list of all materials used for manufacturing of qualification or flight hardware with all relevant information and approval status. CONTENTS As defined in ND71 Annex B. In case of reuse of ' fully qualified ' subsystems, boxes or items, the corresponding materials should not appear in the system DML. The term ' fully qualified ' means that the status of the element is traceable to a valid and complete qualification report containing a DML officially approved by the relevant Customer authority. This list is to be attached to the system DML for reference. In addition to the required paper copies, the DM List shall be provided in a form that is exchangeable, searchable, sortable and suitable for storage and retrieval. The ESA DMPL tool, given at the following address, can be used. http://www.estec.esa.nl/tosqm/What%27sNew/what_s_new.html

http://www.estec.esa.nl/tosqm/What%27sNew/what_s_new.html


2.18.27 D-PA28 - Declared Process List (DPL) PURPOSE OF DOCUMENT To provide a complete list of all processes used for manufacturing of qualification or flight hardware with all relevant information and approval status. CONTENTS As defined in ND71 Annex D. In case of re-use of 'fully qualified' subsystems, boxes or items, the corresponding processes should not appear in the DPL. The term 'fully qualified' means that the status of the element is traceable to a valid and complete qualification report containing a DPL officially approved by the relevant Customer authority. This list is to be attached to the system DPL for reference. In addition to the required paper copies, the DP List shall be provided in a form that is exchangeable, searchable, sortable and suitable for storage and retrieval. The ESA DMPL tool, given at the following address, can be used. http://www.estec.esa.nl/tosqm/What%27sNew/what_s_new.html


2.18.28 D-PA29 – Manufacturing and Inspection Flow Chart / MIP/KIP List PURPOSE OF DOCUMENT To plan, control and reflect the implementation of MIPs and KIPs events during the EarthCARE manufacturing, assembly, integration and test flow. CONTENTS The Contractor shall identify inspection points based on detailed knowledge of the manufacturing, assembly and test flow, in accordance with the requirements of the PARD and ND58. The S/W MIP programme shall be conducted as defined in the S/W development standard. The following events are candidates for MIPs in addition to ND58 clause 8.9.6

Final inspection during qualification of flight standard H/W and S/W Configuration item inspection consisting of at least CIDL/ABCL comparison Qualification or Acceptance testing Safety significant operations Release of S/W products for integration Test Readiness Reviews, and Post Test Reviews Simulation/Interface verification

ESA may elect to add MIPs and KIPs to the Contractor proposed MIPs list as necessary. The MIP/KIP status list shall contain as a minimum the information:

• Company name, • Document identifier and issue, • Project Name, • Item to be inspected, including CI identifier, CI name and serial number, • Specification references, • Item Type (flight / spare / EM / QM, etc), • Inspection identifier & type (MIP or KIP), • Inspection level (ESA / PRIME / Subco, etc), • Inspection location, • Schedule (expected date & actual date), • Status, • Report reference, • Closure date.


2.18.29 D-PA30 - End Item Data package (EIDP) PURPOSE OF DOCUMENT Set of Data needed for the Acceptance of Deliverable items. EIDP TABLE OF CONTENTS

1. Title page identifying the item and the issue status of the EIDP 2. Certificate of Conformance 3. Historical Record ("Logbook") 4. As-built Configuration Status List including Manufacturing and Inspection flowchart + MIP report 5. Configuration Item Data List 6. Reference List for Lower ADP's (if not included in the CIDL) 7. Top Level Drawings (including installation drawings) 8. Functional Diagrams 9. Electrical Circuit Diagrams and PCB assembly schemes 10. List of Non-conformance Reports 11. Copies of Non-conformance Reports (Major) 12. List of Waiver and Deviation Requests 13. Copies of Waiver and Deviation Requests 14. Qualification (for EQM)/Acceptance (for PFM/FM) Test Procedure and Reports 15. Verification Control Documents 16. Safety Data Package 17. Operating Time/Cycle Record 18. Limited Life Items 19. Connectors Mating/Demating Records 20. Proof Load Certificate of Handling Equipment 21. Mass and Balance Record 22. Open Work/Deferred Work/Open Tests 23. Temporary Installation and Removal 24. Loose Delivered Items 25. Operation and Maintenance Manuals/Handbooks 26. Packing/Unpacking, Handling, Transportation and Storage Instructions (including any relevant Safety

Procedure) 27. Minutes of the TRB/DRB authorising the shipment of the item with evidence of the closure of DRB actions.

Evidence of the closure of those DRB actions that were not identified as having to be completed before shipment are to be added as updates to the EIDP after delivery

28. ICD CONTENTS For Hardware (any deviation to be agreed with ESA): ND58, Annex C shall apply with the following supplement:

-Shipping documents -Qualification status -Test specifications -Test procedures (including as-run procedures) -Top level drawing Family tree -Functional diagrams -Top level electrical and interface circuit diagrams -Serialised component list -Copies of waivers and deviations + status lists -Copies of NCRs reports (complete record for each NCR) + status list


-Alert status list -MIP/KIP reports -Operating item Cycle record (where applicable) -Connector mating /demating log book (where applicable) -Age sensitive items (when applicable) -Pressure vessel history log -Calibration data record -Open work/deferred work/open tests/temporary installation -lower level ADPs

For Software:

• Software configuration file (SCF) • Software release document (SRelD) • Software user manual • Software delivery, (source code, make files, libraries etc) • Acceptance test plans • Installation plans • Software validation test reports • Acceptance testing documentation • Acceptance test reports • Installation report • Software traceability matrices (this is not necessarily a standalone document but can be part of other

documents) • Independent software verification & validation reports • Software budget report • Validation report evaluation • Copies of Software Problem Reports and status list • Copies of non-conformance reports (complete record for each NCR) and status list • Milestones and technical review reports • Customer approvals of documents (this is not a separate document but a proof of approval of documents) • Maintenance records • Software criticality analyses report • List of critical software components • Software product assurance report • As-designed and as-built configuration statuses

For GSE: ND58, Annex C is applicable with the following supplement -Software and Hardware configuration status list -Proof load certificates -Open work/deferred work/open tests/temporary installation -AIT-DB packet, parameter and Command definition -Control files -EGSE interface tests


2.18.30 D-PA31 - Safety Data Package PURPOSE OF DOCUMENT To support safety reviews and safety certification with launcher safety authority. CONTENTS As defined by the Launcher Authority. The following elements are indicative. Safety Data packages for flight systems The safety documentation file shall include as applicable: - Hazard analysis input data (e.g. design and operational data, either by document reference and issue or the

document copy) - Hazard analysis - Supporting analysis and safety studies that are performed in support of hazard identification and evaluation. - Technical safety requirements file - Hazard and risk acceptance support documents (e.g. analyses, qualification test procedures or drawings), either

by document reference and issue, or the document copy) - Safety data packages - Risk assessment data - Risk assessment reports - Safety reviews and safety audit reports - Safety related non-compliances (including waivers) and failure documentation - Documents review tracking data - Accidents and incident data - Safety requirements conformance data - Verification tracking log - Safety problem data - Lessons learnt Safety Data packages for Ground Support Equipment - Hazard analysis input data (e.g. design and operational data, either by document reference and issue or the

document copy). - Hazard analysis - Supporting analysis and safety studies that are performed in support of hazard identification and evaluation. - Technical safety requirements file - Hazard and risk acceptance support documents (e.g. analyses, qualification test procedures or drawings), either

by document reference and issue, or the document copy) - Safety reviews and safety audit reports - Safety related non-compliances (including waivers) and failure documentation - Documents review tracking data - Accidents and incident data - Safety requirements conformance data - Safety problem data See also ND 62 Annex D.


2.18.31 D-PA32 - Accident / Incident Investigation Reports PURPOSE OF DOCUMENT To report on Accident / Incident investigations. CONTENTS Accidents/ incidents shall be processed according to the non-conformance control system, and treated as a major non-conformance. In addition, the contractor shall notify ESA of such accident / incidents by fax within 24 hrs of the occurrence. The following information shall be transmitted: - Contractor/ subcontractor involved. - Equipment / system involved - Description of accident / incident - Tentative cause - Personnel injured / personnel involved - Estimates of damage to EarthCARE equipment and other property - Predicted consequences including schedule impact - Recommended corrective actions and present activity Following investigation, a report shall be provided which shall contain all necessary information and assessments needed to identify the cause, and prevent recurrence. The report shall include, but not be limited to: - The situation prior to the event - The sequence of events leading to the accident / incident - The accident / incident itself - Immediate consequences of the accident / incident - Other consequences of the accident / incident - Recovery plan for the accident / incident Corrective action required to equipment, activities, or procedure. See also ND 62 Annex E.


2.18.32 D-PA33 - Configuration Items Data List (CIDL) PURPOSE OF DOCUMENT Provide listing of all documents and their applicable status defining the configuration of the instrument CONTENTS As defined in ND52 Annex D The CIDL shall contain for each configuration item the following as a minimum: - The reference of the configuration items including: - CI number - CI name. - CI level. - Company's code (supplier and buyer) - The list of configuration baseline documents defining the configuration in terms of requirements, design and

verification, with their evolution status including NCRs and RFWs and their approval status. These shall as a minimum include:

o Drawings (Including assembly and interface drawings). o Circuit functional diagrams. o Specifications. o Test procedures and plans. o Design verification matrix. o EEE list. o Material, mechanical part and process list.

- The current configuration status (such as "as designed", "as built"), - The status reports on changes, deviations and waivers, - The status reports on change implementation and verification. In addition to the required paper copies, one electronic copy shall be delivered.


2.18.33 D-PA34 - Parts Derating Analysis Report PURPOSE OF DOCUMENT To document the stress levels applied to EEE components and assess the end of life drift and the compliance to the derating requirements. CONTENTS As defined in ND 66, the Parts Derating Analysis Report shall contain the following information: Analysis of all EEE parts to verify conformance to project’s requirements regarding margins by design, considering the highest stress levels resulting from the specified operational and environmental requirements of the spacecraft. The Analysis shall be consistent with the DCL contents


2.18.34 D-PA35 - Maintainability Report PURPOSE OF DOCUMENT To document the results of maintainability analyses performed on the EarthCARE design. CONTENTS The following shall be documented as a minimum:

Design baseline and description Analysis assumptions, input data and results Supporting information and analyses Statement of compliance with applicable requirements Critical Items identified from the analysis Recommendations for design (including redundancy and FDIR concepts), verification, test and operations



2.18.35 D-PA36 - Alert, Warning Note and Problem Notification Status List PURPOSE OF DOCUMENT Identify all Alerts, Warning Notes and Notifications applicable to the project and summarise related corrective actions CONTENTS The list shall

• Identify all known Alerts, Warning Notes and Problem Notifications • Assess the relevance of each problem to items used in the project. • Identify any warning issued to contractors in the project • Identify the impact to the project • Identify Corrective Actions to be taken and implementation status

The document shall contain:

• Summary table: o Reference ID o part type & manufacturer, o nature of the problem, o origin and reference (ESA/CNES/…), o status,

• a warning summary table: o FC number, o Part type, o manufacturer, o nature of the problem, o date of issue

The list shall list in annex for each alert synthesis reference

• Title of the Alert, Warning Notice or Problem Notification • Summary problem description • Recommendations • impacted/users and Corrective actions

Alert status list shall be under configuration control


2.18.36 D-PA37 - Component Procurement Specification PURPOSE OF DOCUMENT CONTENTS As defined in ND 67 clause 3.4


2.18.37 D-PA38 - Fracture Critical Item List PURPOSE OF DOCUMENT CONTENTS As defined in ND13 clause 6.4


2.18.38 D-PA39 - Safety Certificates PURPOSE OF DOCUMENT CONTENTS The Safety Certificate shall contain the following information as a minimum:

• Certificate Number • Certifying Organisation • Accreditation status of Certifying Organisation • Definition of certified item • Applicable Safety Requirements / Standards • Authorising signature / stamp • Date


2.18.39 D-PA40 - Request for Waivers/ Request for Deviations Status List PURPOSE OF DOCUMENT CONTENTS As defined in ND 52 Annex G


2.18.40 D-PA41 - Fracture Control Plan PURPOSE OF DOCUMENT To describe the foreseen implementation of the applicable Fracture Control requirements CONTENTS As defined in ND13 clause 5.3. This includes: - Identify the criteria for the classification of structural items for Fracture Control verification - Design and verification approaches (safe-life, fail-safe, etc and their associated verification process) - Description of special approaches (pressure vessels, glass, fasteners, etc) - Define criteria for material selection, non-destructive inspections and their traceability - Identify whether required material data are available from reliable sources or how will the y be generated - Define the analyses to be performed - Describe any fracture and/or fatigue related tests that are foreseen - Provide a schedule for the main milestones in the Fracture Control verification including deliverable documents


2.18.41 D-PA42 – Contingency Analysis Document Description and Purpose To identify the contingencies arising from system failures and the corresponding recovery operations. Note: Contingencies are defined as “departures from predicted behaviour”. They require compensation methods in order to recover an operational mode either nominal or characterized by an acceptable degradation level. Note: The CA is a dependability analysis that complements the FMECA. Its results are used for the generation of recovery operation procedures Document Content The CA shall contain the following minimum information: - introduction - design baseline - documents - contingency approach - assumptions


2.18.42 D-PA43 – Worst Case Analysis Document Description and Purpose The worst case analysis is used to demonstrate sufficient operating margins for all operating conditions in electronic circuits. Document Content - As defined in ND64 Annex A.


2.19 Project Management Related Documents

2.19.1 D-PM1 – Industrial Project Management Plan PURPOSE OF DOCUMENT To define the management requirements for the work to be performed under the contract and to define the procedures to be applied by the Contractor to ensure that the objectives of theEarthCARE programme are accomplished within the prescribed time schedule at minimum risk and cost. CONTENTS Project Management Plan, covering at least: - basic project management requirements - responsible officers and interfaces - project management procedures, including - technical monitoring and control - Project Breakdown Structures - schedule control and reporting - cost control and reporting - change control and reporting - property control and reporting - progress reporting Documentation and configuration control including electronic means of correspondence, filing, document creation etc.


2.19.2 D-PM2 – Dictionary of Acronyms and Abbreviations PURPOSE OF DOCUMENT Provide a list of acronyms and abbreviations used in the project with an explanation of their meaning CONTENTS Updated and consolidated list of acronyms and abbreviations used throughout the whole project structure and all project phases.


2.19.3 D-PM3 – Project Directory PURPOSE OF DOCUMENT To facilitate communications among the Customer, the Prime Contractor and lower level contractors. CONTENTS The Prime Contractor shall generate and maintain a Project Directory with the following information as a minimum: - Company name - EarthCARE company code - Company location - Company postal address - Company telephone and telefax numbers - Key personnel with their:

responsibility name department telephone extension full electronic mail ID (user ID, network address, network name) electronic mail nickname


2.19.4 D-PM4 – Risk Management Plan PURPOSE OF DOCUMENT To assess and control all risks associated to the project. CONTENTS The content of the Risk Management Plan shall be derived from the Contractor’s proposal after discussion and agreement with the Agency during phase B. Reference is made to the Product Assurance Requirement Document regarding interfaces with Critical Item Control. The Risk Management approach and documents shall be in line with ND48, clause 7. The content of the Risk Management Plan shall be maintained through the EarthCARE project lifetime.


2.19.5 D-PM5 – Risk Register PURPOSE OF DOCUMENT To record the data emanating from risk management activities. CONTENTS The data emanating from risk management activities shall be recorded in a risk management database containing all data necessary to manage risks and document the evolution of risks over the project duration (refer to section 7.2.10 of ND48). Information recorded for each risk shall include: - The name of the custodian for control of the risk - The related Work Package code - An explanatory description - Reasons for the assigned criticality - Importance of their consequences (classification and severity) - Magnitudes of consequences (e.g. schedule and/or cost impacts) - Probability of their occurrence - The preferred solution, with reasons - Alternative solutions and contingencies - Assigned actions - Current status The database is a living document, and shall be maintained current. Extracts from the database are presented at project meetings, reviews and milestones as required by the risk management plan. Items to be candidates for “lessons learned” are identified. Example forms for the registration and ranking/logging of risk items are presented in Annex A of ND48.


2.19.6 D-PM6 – Product Tree (PT) PURPOSE OF DOCUMENT CONTENTS The Product Tree (PT) shall include all products down to the deliverable end items. The Product Trees of Sub-contractors shall be incorporated in the Contractor’s PT. The Contractor shall maintain the Product Tree under configuration control.


2.19.7 D-PM7 – Work Breakdown Structure (WBS) PURPOSE OF DOCUMENT To break down the overall work into individual Work Packages (WP) CONTENTS A WBS covering all activities required to fulfil the contract and based on the Product Tree shall be provided as a part of the proposal. Work related to manufacturing, assembly, integration and test shall be shown in the WBS, in relation to the models. Engineering work shall be identifiable in connection with its related product tree elements such as system, subsystem or unit level. Work related to management, product assurance and any other support activities (e.g. procurement) shall be shown in the WBS. The initial WBS presented in the proposal shall be subject to customer approval. Each supplier shall maintain the WBS for his work share in the project up-to-date.


2.19.8 D-PM9 – Contract Structure (CS) PURPOSE OF DOCUMENT Describes the contractual relationship within the project. CONTENTS The Contract Structure (CS) shall represent the contractual hierarchy of the project including all sub-contractors, showing the relationship between countries, companies and Contracts, such that the Contractual responsibilities can be easily traced. The countries and companies shall be identified by their commonly agreed codes. Based on any input provided by the Agency and/or resulting from the Contract negotiation, and/or resulting from the activities performed during the execution of the Phase B/C/D/E1 Contract, the Contractor shall update the CS as appropriate. The CS, and any updates thereon are subject to the Agency’s approval.


2.19.9 D-PM10 – Project Organisation Breakdown Structure (POBS) PURPOSE OF DOCUMENT Gives the project organisation for each contractor. CONTENTS The Project Organisation Breakdown Structure (OBS) shall present the contractor’s Project Team organisation which depicts the functional aspects of the project organisation, and shows in a few lines the place of the Project Team within the overall company structure. The responsible supervisor for each Work Package shall be identified within the OBS. The OBS shall be part of the offer and shall be maintained and regularly updated during the project life cycle. Each Sub-contractor shall provide his own OBS as per the above guidelines. The Contractor and all his Sub-contractors shall identify the key personnel as defined in the Contract to be deployed on the work and include them in the OBS. The following functions are to be considered:

- project management, - contracts, - project control, - documentation management, - information systems, - procurement, - assembly, integration and verification, - product assurance and safety, - engineering. The same key person may perform certain functions, but no artificial intermediate levels shall be introduced. The Contractor shall include all key personnel into his Project Directory.


2.19.10 D-PM11 – Payment Status & Forecast Report PURPOSE OF DOCUMENT This document identifies the status of all payments made by the contractor in the EarthCARE project and the forecast of future payments to be made, including relationship to key contract milestones. CONTENTS To be specified by contractor and to be agreed with agency.


2.19.11 D-PM12 - Schedule Reporting PURPOSE OF DOCUMENT To report the schedule as the result of an objective and realistic analysis of the progress made, showing an active control of the execution of the work CONTENTS The Schedule Reporting shall include the following elements:

• a narrative part explaining the overall status of the Project

• the updated milestone list

• the updated bar-charts

• the updated trend analysis

• an analysis of any critical items affecting the schedule

• a report on the planned usage of the test facilities, identifying any potential conflict in availability and identifying backups in case of problems. The use of CETeF’s and/or other test facilities shall be clearly indicated;

• an indication of any further changes in duration, added or deleted activities or logic changes which may have occurred and the reason for such changes

The reporting shall show the approved Original or Current Baseline Schedule against the Current Working Schedule. In addition, more frequent specific reporting shall be done in critical situations.


2.19.12 D-PM13 - Progress Report PURPOSE OF DOCUMENT At agreed intervals, the Progress Report shall provide information to the Agency’s project management, reflecting the progress of the project during the reporting period for analysis and discussion. See Management Requirements and Tasks chapters 2.3, 4 and 9. CONTENTS Non exhaustive list - Overall assessment, including:

Project Manager’s assessment Key problem list Open action items requiring special attention Risk assessment

- Technical Status (actual versus planned) - Schedule Status (actual versus planned) - Cost, Performance and Financial Status - Contractual Aspects Specific annexes shall be included, or referred to, as follows: - schedule reporting - action item status list - RFW list - NCR list - DCN status list - CCN status list


2.19.13 D-PM14 - Milestone Payment Plans and Status PURPOSE OF DOCUMENT To report the current contractual milestone payment plan status. CONTENTS The report shall be prepared in EFIS and shall contain all payment milestones with identification of: - titles - MPP reference - company code - no. of Milestone List - baseline date (contractual) - estimated date - achieved date - contractual price (baseline plus approved changes) in Euros The document shall provide the Original Baseline Cost Plan (OBCP), as agreed after the finalisation of contract negotiation. The document shall also include the Current baseline Cost Plan (CBCP), showing the updated situation as defined by the introduction of each approved change to the baseline. A section of the document shall be dedicated to the Payment Status and Forecast Report, including all milestones and known or estimated escalation amounts.


2.19.14 D-PM15 - Geographical Distribution of Work (GDW) PURPOSE OF DOCUMENT Updated overview of the geographical distribution of contracts. CONTENTS The Geographical Distribution of work (GDW) shall be updated on a quarterly basis. The following requirements apply: - The first issue of the GDW shall be based on the offer provided by the Contractor, amended as a result of the

contract negotiation, and shall be issued immediately thereafter. - Any further updates shall take due account of the results of selection of sub-contractors, including approved

class A and class B changes. - The GDW shall clearly show the baseline and the impacts resulting from new subcontracts, class A and class B

changes separately, supported by a clarification note.


2.19.15 D-PM16 - Contract Change Notices (CCN) PURPOSE OF DOCUMENT As defined in the EarthCARE Management Requirements and Tasks, para 7 CONTENTS The substantiating documentation and information to be supplied with the CCN shall include, as a minimum, the following:

• Justification of change

• A detailed technical description of the change, and its implications and consequences on system or subsystem performances. This shall be accompanied by the propos–d - amendments to the relevant documents.

• A description of the envisaged tasks in the form of a brief Statement of Work, subdivided into the affected Work Packages, and/or list of the tasks to be eliminated.

• Work Package Descriptions.

• A statement of the schedule impact, if any, supported by revisions to the affected schedule documents.

• Company Price Breakdown Forms (PSS-A1, PSS-A2,PSS-A8 and PSS A10). All changes shall be submitted as (Firm) Fixed Price in Euros, in line with the price type of the (sub)Contract concerned. Proposed payments plan(s) for the change, including those of the Subcontractors.

• The Contractor shall list on each CCN the reference numbers of any CCN’s from his Subcontractors. These shall be annexed to the Contractors CCN. The Contractor shall include, as part of his CCN, his assessment, conclusions and recommendations on any CCN submitted by his Subcontractors.

The Contractor shall ensure that his Subcontractors’ CCN’s are submitted by means of fully completed CCN forms, with additional information as required, in a fully co-ordinated manner, including all impacts of even lower level Subcontractors


2.19.16 D-PM17 - Contract Change Notices Status List PURPOSE OF DOCUMENT For information and analysis. CONTENTS The Contractor shall create and continuously maintain an up to date log (the Contract Change Notices Status List) of all his own and his lower level Contractors contract changes. The Contract Change Notices Status List shall as a minimum contain the following information:

• list of changes still under preparation,

• list of approved CCN’s, breakdown per Contractor, classification, price, type of price,

• list of rejected or withdrawn CCN’s,

• list of changes submitted to the Agency, but not yet approved,

• list of Change Requests issued by the Agency, with reference to the related CCN,

• list of all approved Class B changes.


2.19.17 D-PM18 - Work Package Description PURPOSE OF DOCUMENT To identify the exact content, time scale, purpose and interrelationship of each task at the lowest level of the WBS. CONTENTS Each WP shall be formatted in accordance with ESA PSS-A-20 and shall contain as a minimum the following information:

• project name and project phase,

• WP title,

• unique identification of each WP,

• supplier or entity in charge of the WP performance;

• WP manager’s name and organization;

• product to which the tasks of the WP are allocated (link to the product tree),

• description of the objectives of the WP,

• description of the tasks,

• list of the inputs necessary to achieve the tasks,

• interfaces or links with other tasks or WPs,

• list of constraints, requirements, standards, and regulations,

• list of the expected outputs,

• start event identification including date

• end event identification including date

• excluded tasks. WPD’s shall be developed for each work package of each WBS. Their detail must be sufficient to relate an individual work element to: - The lowest contractor. - the schedule and networks - a contractual delivery - the lowest detail required in the proposal


2.19.18 D-PM19 - Document Change Requests (DCR) / Notes (DCN) PURPOSE OF DOCUMENT Ensures formal mechanism for change control of documents. CONTENTS Document Change Requests (DCR) and Document Change Notice (DCN) shall be the formal means to record updates to level 1 and level 2 documents and shall be issued to all recipients. All DCR and DCN’s shall be subject to the Agency’s approval. Documents shall be updated either by a revision or by a new issue. Revisions will be made for minor additions, deletions or changes of information. New issues or re-issues will be made when major changes in the scope or the text have evolved.


2.19.19 D-PM20 - Documentation Management Plan PURPOSE OF DOCUMENT To define the plannin�elecommand�ion and procedures used to manage the documentation of the EarthCARE project, including external and internal interfaces. CONTENTS Content as defined in ND 53 clauses 6.2.2 and 6.5


2.19.20 D-PM21 - Document Status List PURPOSE OF DOCUMENT To provide information about the status of EarthCARE project documents CONTENTS The documents list shall present the current status of all documents prepared under this contract and sorted by types. The list shall include a sub-list of all the controlled documents with: - Identification - Title - Issue/Revision and its date - DRD No. (For Customer deliverable documents) - Issuing company and distribution - Approval category - Contractual delivery dates.


2.19.21 D-PM22 - Contractors DRL PURPOSE OF DOCUMENT Derived contractor’s DRL. CONTENTS The Contractor DRL shall be based on the DRL included in the ITT. All changes to the Contractor’s DRL shall be communicated to the Agency for approval. The DRL shall show full traceability to the original DRL, and issued as part of the Progress Report.


2.19.22 D-PM23 - Inventory Record PURPOSE OF DOCUMENT Items which are produced or purchased specifically and used exclusively for the purpose of the Contract, as well as items made available by the Agency to the Contractor shall be subject to Inventory Control and listed into the Inventory Record document. CONTENTS The Contractor shall establish an electronic central database (called Inventory Record) of all Inventory Items for the whole project. The Inventory Record shall be presented to the Agency in the following way:

• one for each class • one per physical location (company level) and • record of deleted items, one for each class including reason for deletion

All Inventory Items shall be entered into a registration system with the following information:

• unique item registration number (inventory number), • quantity, • item description, • manufacturer model and serial number, • acquisition date and value in Euro and National currency at the time of purchase, • classification (1 or 2) and • physical location (sufficient detail to accommodate inspection).


2.19.23 D-PM24 - Meeting Schedule PURPOSE OF DOCUMENT Schedule of planned technical and progress meetings at Prime Contractor and lower contractor level. CONTENTS The Prime contractor shall prepare and update a list of meetings within the industrial consortium and visits, updated on a bi-weekly basis. The list shall clearly specify: - main subject of the meeting - name and location of the compa�elecommaning the meeting - contact point of meeting - date, time and duration - attendees / participating companies


2.19.24 D-PM25 - Minutes of Meeting PURPOSE OF DOCUMENT To summarize all action items, decisions, recommendations and statements made during the EarthCARE project meetings. CONTENTS The minutes shall contain as a minimum: - A standard front sheet, indicating date, place and subject of the meeting, together with the agenda and the list

of participants; - The conclusions of the meeting, with reasons for disagreement, if any; - A brief point of the overdue actions; - A list of new actions, precisely formulated, coded in accordance with an overall coding system and indicating

actionees and due dates assigned; - A brief summary of the discussion on major problem areas; - Copies of technical notes, view-graphs, drawings, etc as presented at the meeting.


2.19.25 D-PM26 - Action Item Status List PURPOSE OF DOCUMENT Report of project Action Items with their actual status information related to a review, meeting, etc., to ensure that agreed items are properly recorded, monitoring, performed and closed-out at the required time. CONTENTS The Action Items system contains datasets of agreed project action items defined in reviews, meetings or other project events to which ESA have right of attendance, with at least the following information:

• action item identifier,

• a brief description,

• initiation date,

• reference to the minutes of meeting at which the action item was initiated;

• due date

• the actionee (company + person’s name,)

• the initiator (company + person’s name,)

• status (“O” = Op”n”"P””= Proposed for closure “C” = Closed),

• closing reference • closing date.


2.19.26 D-PM27 - End of Project Assessment and Contract Close-Out PURPOSE OF DOCUMENT Certification and agreement between Customer and Contractor on the termination of their contracts. Subject to Customer approval/concurrence. Assessment of “Lessons-Learnt” during the project. CONTENTS The document should contain as a minimum: - Contract duration - Warranty conditions - Contract conditions - Contract and CCN scope - Subcontracts close-out - Financial matters - Final escalation calculation - Penalty Application - Document Status List - End item data pack - CFI - Third Parties Intellectual property rights - Status of inventions - Inventory Status - Contract fulfillment - Contract termination - Lessons-Learnt


2.19.27 D-PM28 - Inventory Control Plan PURPOSE OF DOCUMENT Plan for monitoring the identification, control and disposition of Customer property. CONTENTS The Inventory Control Plan shall address all items to be controlled and shall include a: - Classification of property - Treatment of property - Recording of property - Marking of property - Disposal of property - Audit and physical inspection


2.20 Review Related Documents

2.20.1 D-PR1 - Satellite Review Procedure PURPOSE OF DOCUMENT U S E D B Y E S A CONTENTS


2.20.2 D-PR2 - Subsystem Review Procedure PURPOSE OF DOCUMENT Describes the organisation of each subsystem review CONTENTS The document should contain the necessary information for planning the review, including: - Review objectives - List of documents contained in the review Data Package - deadlines for the submission of Data Package - deadlines for RID-submission / RID close-out - dates and location of meetings - list of participants - deadlines for the contractor’s answers to reviewers


2.21 Satellite Related Documents

2.21.1 D-SA1 - Satellite Design Specification PURPOSE OF DOCUMENT To define all specifications for the system from satellite level down to subsystem and instrument level. CONTENTS Specifications shall address the satellite system, all sub-systems and instruments. The design specifications shall contain: - applicable documents (including support specifications) - functional requirements including FDIR - performance requirements including reliability - operational requirements - electrical requirements (RF, signal, power, grounding, data handling, command and control) - software requirements - mechanical requirements - thermal requirements - interface requirements - environmental requirements - EMC/RFC requirements - GSE requirements - Verification requirements - PA �elecommand�ion�


2.21.2 D-SA2 - Subsystem and Unit Requirement Specifications PURPOSE OF DOCUMENT The documents define Requirements Specifications for Subsystems and Units (including instrument subsystems and units). CONTENTS Each of these specifications shall contain: - applicable documents (including support specifications) - functional requirements including FDIR - performance requirements including reliability - operational requirements - electrical requirements (RF, signal, power, grounding, data handling, command and control) - software requirements - mechanical requirements - thermal requirements - interface requirements - environmental requirements - EMC/RFC requirements - GSE requirements - Verification requirements - PA


2.21.3 D-SA3 - Design Justification File PURPOSE OF DOCUMENT The DJF is generated and reviewed at all stages of the development and review processes. It contains the documents that describe the trade-offs, design choice justifications, test procedures, test results, evaluations and any other documentation called for to justify the design of the suppl’er's product. CONTENTS The DJF shall contain: - Analysis as a minimum as listed in the EarthCARE applicable documentation - trade-off approach - general trade-off criteria - summary of system trade-offs - results and conclusions. Further details regarding the contents to be specified by the contractor and agreed by the Agency


2.21.4 D-SA4 - Review of “Off the Shelf” S/S and Unit Hardware PURPOSE OF DOCUMENT Reviews and identifies possible “off the shelf” subsystem and unit level hardware from existing platforms and assesses their suitability for the EarthCARE satellites CONTENTS The document shall contain a list of available equipment and the assessment of the suitability for the purposes of EarthCARE. Where more than one candidate is identified the rationale for selection of a specific one (if any) should be given. The document shall identify the qualification status of the item with respect to the EarthCARE requirements and specifically identify any additional assessments or evaluations required to achieve qualification for EarthCARE.


2.21.5 D-SA5 – EarthCARE FDIR Definition and Implementation Report PURPOSE OF DOCUMENT To document the definition and implementation of the FDIR in EarthCARE. CONTENTS To be specified by the contractor and agreed by the Agency


2.21.6 D-SA6 - Satellite Budget Document PURPOSE OF DOCUMENT To provide a comprehensive source of reference for all EarthCARE “current” satellite system budgets, compared to the required performance and margin. CONTENTS The document includes the Margins and Budgets Management Approach and should indicate clearly the margin applied to every item in each of the system budgets. All satellite current system & performance budgets down to unit level, including: - mass and mass properties - power and thermal budgets (including power dissipation and heater power) - energy - RF link budgets - TM/TC and data bus exchange budgets - software and memory budgets - on-board propellant - system performance, data quality budget, reliability and availability budge�elecommand�ionion and datation

budget - EMC/EMI budget - DC/AC magnetic budget - attitude budget - alignment budget - pointing budget - calibration budget and error budget - pyrotechnics budget - instrument end to end performance budgets The budgets shall contain, as a minimum, the indication of the “current” best estimate values compared with the “specified” values. This document may be built-up or refer to lower/equal level documents. An electronic spreadsheet shall be delivered in parallel.


2.21.7 D-SA7 - Documentation Tree PURPOSE OF DOCUMENT To define the documentation (e.g. plans, specifications, drawings, ICD, reports) applicable to EarthCARE from system to unit level. CONTENTS A drawing, chart or indented listing showing the drawings, description, analysis, specifications and all relevant documentation that defines the design, tasks and project organization.


2.21.8 D-SA8 - Satellite Internal Interface Control Documents PURPOSE OF DOCUMENT To define the satellite internal interfaces in relevant interface control documents (ICD’s) CONTENTS

ICD’s covering as a minimum:

- mechanical interfaces (including size, mass properties, dynamic properties, disturbance exported, deployment,

field of view, physical envelope, local reference, mounting/accommodation, AIT interfaces including GSE interfaces, ground operations and constraints on ground operations)

- thermal interfaces (including temperature limits, surface treatment, thermal insulation, thermal conductances, power dissipation, heater budget, heater values and thermostat switching values)

- electrical interfaces (including power supply, avionics, timings, housekeeping interface, skin connectors) - On-board communication


2.21.9 D-SA9 - Design Definition File PURPOSE OF DOCUMENT The DDF is a supplier-generated document that documents the result of the design engineering processes. CONTENTS Includes as a minimum: - Overall assembly and geometrical drawing [D-SA17] - Mechanical Drawings [D-SA18] - Electrical Drawings including grounding diagrams [D-SA19] - Thermal Drawings [D-SA20] - Unit circuit diagrams, particularly of interfaces [D-SA22] - Switching diagrams and synoptics [D-SA22]

These drawings shall be updated as appropriate in all mission phases up to E1. Further details regarding the contents to be specified by the contractor and agreed by the Agency


2.21.10 D-SA9–1 - Satellite System Technical Description PURPOSE OF DOCUMENT To provide a comprehensive technical description of the overall baseline EarthCARE satellite system, including external interfaces and system budgets. CONTENTS Technical description, to include: - Introduction - Mission, instrument performances and operations overview - Instrument accommodation - Launch, LEOP and in-orbit configurations - Satellite design concepts, including avionics, thermal and mechanical architecture - Data processing hierarchy / software architecture - Baseline satellite description - For each subsystem, for GSE and for Simulators:

- Functional block diagram/schematic - Description of key features and interfaces

- Satellite system budgets summary - External interfaces (Launcher, GSE, Ground Segment)


2.21.11 D-SA9–2 - SRR Package

PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the System Requirements Review. CONTENTS The review documentation shall consist of the following two elements:

1. The review package summary providing a description of the satellite/module/instruments covering for each technical discipline (electrical, mechanical, thermal, command and control, data handling, AOCS, EMC/RFC, software and product assurance) an overview of:



2. The baseline documents as identified for each major review in the EarthCARE Document Requirements List (DRL), including the support specifications. The baseline documents to be provided as part of the data package proper and the number of copies will be agreed and specified in dedicated review procedures provided by the Customer. Baseline documents not included in the data package proper, however listed in the DRL as deliverable at the review milestone, shall be provided in the number of copies specified in the DRL.



2.21.12 D-SA10 - PDR Package

PURPOSE OF DOCUMENT

To establish the requirements related to the documentation package required for the System Preliminary Design Review.

CONTENTS The review documentation shall consist of the following two elements:

1. The review package summary providing a description of the satellite/module/instruments covering for each technical discipline (electrical, mechanical, thermal, command and control, data handling, AOCS, EMC/RFC, software and product assurance) an overview of:



2. The baseline documents as identified for each major review in the EarthCARE Document Requirements List (DRL). The baseline documents to be provided as part of the data package proper and the number of copies will be agreed and specified in dedicated review procedures provided by the Customer. Baseline documents not included in the data package proper, however listed in the DRL as deliverable at the review milestone, shall be provided in the number of copies specified in the DRL.



2.21.13 D-SA11 - CDR Package PURPOSE OF DOCUMENT

To establish the requirements related to the documentation package required for the System Critical Design Review.

CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the satellite/module/instruments covering for each

technical discipline (electrical, mechanical, thermal, command and control, data handling, AOCS, EMC/RFC, software and product assurance) an overview of:






2.21.14 D-SA12 - QR Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the System Qualification Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the satellite/module/instruments covering for each







2.21.15 D-SA13 - AR Package

PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the System Acceptance Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the satellite/module/instruments covering for each


- the major design changes - major achievements in the development and test programme - acceptance status - major problem areas and their proposed solutions - major waivers/deviations from the baseline requirements as evolved


(DRL), including the launch campaign related documents. The baseline documents to be provided as part of the data package proper and the number of copies will be agreed and specified in dedicated review procedures provided by the Customer. Baseline documents not included in the data package proper, however listed in the DRL as deliverable at the review milestone, shall be provided in the number of copies specified in the DRL.



2.21.16 D-SA14 - IOCR Package PURPOSE OF DOCUMENT To establish the requirements related to the documentation package required for the System In-Orbit Commissioning Review. CONTENTS The review documentation shall consist of the following two elements: 1. The review package summary providing a description of the outcome of the satellite/instruments calibration,

commissioning, verification and validation: - Commissioning status - Data processing results and status

- major achievements in the commissioning and in-orbit verification programme

- major IOVR results

- Software and software maintenance status

- major problem areas and their proposed solutions

The summary is part of the data package proper and is required in the same number of copies. The Contractor shall propose a detailed contents list of the Review Package for Customer approval 2 months prior to the submission of the data package.


2.21.17 D-SA15 - Subsystem Qualification Reports

PURPOSE OF DOCUMENT Demonstrates that supplied subsystems are qualification tested in a systematic and traceable manner. CONTENTS The test report shall include as a minimum: - scope and objectives - summary of test results - conclusion about qualification - test results and evaluation of test results, emphasizing significant events and problems encountered; it shall

also cover interpretation and correlation of test results to relevant analytical predictions - a list of all non-conformances generated during the test - the as-run test procedure including a list of deviations from the applicable test procedure and the sign-off

sheets


2.21.18 D-SA16 - Subsystem Acceptance Reports

PURPOSE OF DOCUMENT Ensures that supplied subsystems are acceptance tested in a systematic and traceable manner. CONTENTS The test report shall include as a minimum: - scope and objectives - summary of test results - a conclusion about the acceptance - test results and evaluation of test results, emphasizing significant events and problems encountered; it shall

also cover interpretation and correlation of test results to relevant analytical predictions - a list of all non-conformances generated during the test - the as-run test procedure including a list of deviations from the applicable test procedure and the sign-off

sheets


2.21.19 D-SA17 - Overall Assembly and Geometrical Drawings

PURPOSE OF DOCUMENT

To provide overall drawings of the EarthCARE assembly and accommodation.

CONTENTS The drawings shall cover as a minimum: - internal and external top assembly drawings, in stowed and deployed configurations - major sub-system top assembly drawings in stowed and deployed configurations - general internal and external assembly drawings - major sub-system assembly drawings - instrument accommodation drawings - satellite launcher accommodation drawings - satellite test facilities accommodation drawings - satellite sensors, antennae and instrument unobstructed field of view drawings


2.21.20 D-SA18 - Mechanical Drawings

PURPOSE OF DOCUMENT To provide the EarthCARE satellite mechanical interface drawings. CONTENTS The drawings shall cover as a minimum: - overall mechanical drawings (indicating e.g. internal structural interfaces, equipment attachment points, lifting

points etc.)

- panel lay-outs (indicating unit/equipment footprints, keep-out zones, through-holes etc.)

- piping routing drawings.

- main structural characteristics : size, attachment, material and thickness, etc

- harness routing and connector bracket allocation drawings.


2.21.21 D-SA19 - Electrical Drawings and Synoptics

PURPOSE OF DOCUMENT To provide overall EarthCARE satellite electrical drawings. CONTENTS The drawings shall cover as a minimum: - overall block diagram (system and equipments) - system functional diagram - TM/TC diagram - power diagrams

- grounding and isolation diagrams

- system wiring diagrams


2.21.22 D-SA19-1 – Harness Routing PURPOSE OF DOCUMENT

To document the routing of the spacecraft harness within the satellite.

CONTENTS To be specified by the contractor and agreed by the Agency


PURPOSE OF DOCUMENT

2.21.23 D-SA20 - Thermal Drawings

To provide the EarthCARE satellite thermal interface drawings.

CONTENTS The drawings shall cover as a minimum: - overall thermal drawings (indicating, thermo-optical properties, blankets, heater characteristics and location

etc.) - locations and type of temperature sensors - harness routing and connector bracket allocation drawings.


2.21.24 D-SA21 - Unit Circuit Diagrams

PURPOSE OF DOCUMENT To provide circuit diagrams of all EarthCARE procured unit/equipment types. CONTENTS The drawings shall be provided of the unit down to PCB level.

ASIC/Hybrid design and lay-out drawings are not required. However, they shall be available for consultation..


2.21.25 D-SA22 - Switching Diagrams and Synoptics

PURPOSE OF DOCUMENT

To provide a comprehensive overview over switchable functions and redundancies

CONTENTS Drawings from unit to system level with an overview of all switchable blocks. All switches shall be identified by the�elecommandand-identifier and the pertinent telemetry-identifier which allows monitoring of the switching-action by ground. Tc-IDs and Tm-IDs shall be the same as used in the SRDB-D.


2.21.26 D-SA23 - Satellite IOV Plan and Procedures

PURPOSE OF DOCUMENT This document defines the plans and procedures for the In-Orbit Verification activities. CONTENTS To be specified by contractor and to be agreed with agency.


2.21.27 D-SA24 – Satellite Calibration and Characterization Database

PURPOSE OF DOCUMENT To provide all the information pertinent to the use of the calibration/characterization parameters for the satellite. CONTENTS The document shall contain the complete set of information necessary for the successful installation of the database. This shall include a complete description of the physical and electronic data exchange and the format and layout of all database files, so that their contents can be read and installed. For each calibration and characterization parameter, a form sheet indicating: - file name of the calibration/characterization - item (equipment) configuration identifier - parameter file (look-up tables) - environmental conditions - reference to the test set-up configuration and test date/time


2.21.28 D-SA25 – Elements of Manufacturing Dossier

PURPOSE OF DOCUMENT To provide elements of the manufacturing dossiers needed for the Agency to monitor and control the spacecraft development. CONTENTS These documents are a subset of the EIDP contents for each deliverable item. The following documents are included as a minimum:

• Schematics • Harness diagrams • Interconnection drawings • Photographs of PCB and subsystems • Layout drawings • SOT values • Jumper settings & values


2.21.29 D-SA26 – Pointing, Alignment, Instrument Co-Registration and Geo-location Requirement Analysis

PURPOSE OF DOCUMENT

To identify and justify detailed requirements for pointing, alignment, co-registration and geo-location of all instruments and the satellite platform.

CONTENTS The following analysis shall be included as a minimum: - End to end summary requirements - Instrument requirements - Spacecraft structure requirements - AOCS requirements - Datation - Allocation of budgets between CPR and spacecraft - AIV alignment requirements - Alignment trimming provisions - Stability (ground handling, 1g to 0g, temperature, water release) - Derivation / justification of above requirements into subsystem specifications


2.21.30 D-SA27 – Pointing, Alignment and Instrument Co-Registration and Geo-location Description and Implementation

PURPOSE OF DOCUMENT To describe the implementation of the detailed requirements for pointing, alignment, co-registration and geo-location of all instruments and the satellite platform, with reference to D-SA25. CONTENTS Description of the implementation of the pointing, alignment, instrument co-registration and data geo-location requirements shall be addressed, including the measured results: - End to end summary budget - Instrument budget - Spacecraft structure budget - AOCS budget - Datation - AIV alignment results - Alignment trimming - Stability (ground handling, 1g to 0g, temperature, water release)


2.21.31 D-SA28 – EarthCARE EFM Specification

PURPOSE OF DOCUMENT To define the requirements for Electrical Functional Model of the EarthCARE spacecraft. CONTENTS The document shall contain as applicable: - applicable documents (including support specifications) - functional requirements including FDIR - performance requirements including reliability - operational requirements - electrical requirements (RF, signal, power, grounding, data handling, command and control) - software requirements - mechanical requirements

- interface requirements

- thermal requirements

- environmental requirements - EMC/RFC requirements - GSE requirements - Verification requirements - PA


2.22 Structure Related Documents

2.22.1 D-ST1 - Satellite Mechanical Design Requirements Specification

PURPOSE OF DOCUMENT To define a common set of mechanical design definitions, requirements and rules for use in mechanical design activities at satellite, payload and platform instrument/sub-system and equipment level. CONTENTS Mechanical design requirements in terms of: - satellite configuration and mechanical architecture dimensioning rules (including the definition of all safety factors and design/qualification/acceptance mechanical loads, relevant margins) and definitions of margins of safety and rules for loads combination) - structural design requirements - structure performance requirements (including alignment requirements) - common design and construction requirements (e.g. materials, mechanical properties, etc...) - structure analysis requirements (including static, dynamic, stress and thermal distortion, structure interfaces)

- maintenance and verification requirements (including reference configuration and coordinate system)

Furthermore, the document shall provide an exhaustive list of all definitions and terms used in the mechanical design fields for the EarthCARE project.

- mechanical analysis campaigns identification and implementation logic

-

The document should also describe the selected verification approach (analysis, test or combination of both) to be used for the different structural elements at satellite, payload and platform instrument/sub-system and equipment level The contents of this document can be combined with those ones of [D-TH1] in a single “Satellite Mechanical and Thermal Design Requirement Specification”.


2.22.2 D-ST2 - Satellite Environmental Design and Test Requirements Specification

PURPOSE OF DOCUMENT To define the natural and induced environment that the EarthCARE satellites and their constituent parts shall be able to withstand in all phases of transportation, handling, storage, pre-launch, launch, ascent and in-orbit. To specify the levels and profiles of mechanical environmental tests to qualify and accept the EarthCARE hardware at equipment, sub-system/instrument payload, platform and satellite levels. CONTENTS Environmental Design and Test Requirements in terms of: - general environmental requirements (description of applicable environments) - general test requirements (test categories, conditions, tolerances and applicability matrix) - specification of natural and induced environments encountered by EarthCARE at equipment, sub-

system/instrument, payload/platform and satellite levels. - specification of qualification and acceptance environmental test levels and test methods at equipment, sub-

system/instrument, payload/platform and satellite level.


2.22.3 D-ST3 - Structural Description Report

PURPOSE OF DOCUMENT To report the selection and definition of the satellite mechanical design. CONTENTS

The document shall contain as a minimum:

- description of the structure and structural components, - description of the interfaces, - description of the build standard - performance : alignment, mass, static loads - a comprehensive subset of structural drawings in A3-format


2.22.4 D-ST4 - Preliminary FEM Description Reports

PURPOSE OF DOCUMENT Description of the preliminary static and dynamic FEMs. CONTENTS

- Description of the preliminary static and dynamic FEMs (Finite Element Models) to support overall stress, dimensional stability, dynamic behaviour and preliminary spacecraft / launcher coupled load analyses.

- Description of the System of units - Description of coordinate systems - Rules for numbering - Assumptions, idealizations and limitations - General description of the model including figures - Global mass and inertia properties - Description of interfaces, listing the interface nodes and boundary conditions - Results of the mathematical correctness checks, including as a minimum:

• 1g gravity check • Rigid body strain energy check • Normal models analyses in free and fixed boundary conditions • Thermo-elastic analysis check for those models that will be used for thermo-elastic analysis

- Description of the procedure to run the models (including analysis parameters to be used)

- Reporting the validation of these models.


2.22.5 D-ST5 - Structural Analysis Report PURPOSE OF DOCUMENT To report the structural analysis as part of the Design Justification File [D-SA3]. CONTENTS To describe the detailed structural analyses of the satellite and its equipment., considering all mission and contingency phases. This shall, at least, include prediction of dynamic behaviour, launch flight limit loads, quasi static loads, sine, acoustic, random and shock responses and stresses, in-orbit thermal distortions, thermal stress and micro-vibrations. Margins shall be reported. Analyses shall demonstrate that all requirements are fulfilled. The static test response shall be predicted The report shall include: - Clear description of the applied loads in each analysis - Damping considered in the analysis where applicable - Material properties considered for the analysis - Reference to the corresponding FEM description report/s - Applicable design allowables - Applicable Factors of Safety - Considered failure modes - Analysis results - Resulting Margins of safety


2.22.6 D-ST6 - Alignment and Stability Analysis

PURPOSE OF DOCUMENT To report the results of the alignment and stability analysis based on all effects, including (but not limited to) thermal, outgassing, etc. CONTENTS The alignment and stability analysis shall be performed for all orbit phases, taking into account all mechanical (and thermal) misalignment sources. Analyses shall demonstrate that all requirements are fulfilled. The report should identify clearly: - The structural parameters (displacements, rotations, deformations, etc) that are used to derive the alignment and stability

performance and the method to do so - The environmental conditions considered for the analysis - Assumptions and idealizations used in the analysis and their justification - Analysis results - Alignment and stability performance and comparison with the corresponding requirements


2.22.7 D-ST7 - Fracture Analysis Report

PURPOSE OF DOCUMENT To report the verification of the fracture control requirements and the corresponding results for all the potential fracture critical items CONTENTS As defined in ND 13, includ ing: - Classification of structural items for the Fracture Control verification (Potential Fracture Critical Items List, Fracture Critical

Items List and Fracture Limited Life Items List) - Overview of the hardware to be analysed - Definition pf applicable service life Spectrum - Input data for Fracture and Fatigue analyses (Material data to be used, geometries of parts and initial crack sizes) - Summary of performed Non destructive inspections - Fatigue analyses results - Fail Safe analyses results - Safe-life analyses results - Containment analyses (if any) - Damage tolerance test results (if any) - Leak before bursting analyses results (if any) - Summary of results defining what is the actual life of the hardware


2.22.8 D-ST8 - Correlated FEM Description Report

PURPOSE OF DOCUMENT To describe the FEMs correlated with the static and modal survey test results. CONTENTS - Description of the correlated FEMs. - Description of the System of units - Description of coordinate systems - Rules for numbering - Assumptions, idealizations and limitations - General description of the model including figures - Global mass and inertia properties - Description of interfaces, listing the interface nodes and boundary conditions - Results of the mathematical correctness checks, including as a minimum:

- 1g gravity check - Rigid body strain energy check - Normal models analyses in free and fixed boundary conditions - Thermo-elastic analysis check for those models that will be used for thermo-elastic analysis

- Description of the procedure to run the models (including analysis parameters to be used). - Reporting the validation of these models. - Reporting the correlation of the models.


2.22.9 D-ST9 - Sine Test Predictions and Preliminary Notching Analysis

PURPOSE OF DOCUMENT To predict the sine test responses and provides preliminary notching analysis. CONTENTS The document shall contain as a minimum: - the internal sine responses, including instruments - the CoG sine response - the launcher / satellite interface loads - the philosophy used for notching - the proposed sine notched profiles, the equipment which drive the notches, and the minimum margins


2.22.10 D-ST10 - FEM Correlation Report PURPOSE OF DOCUMENT To report the correlation of the FEMs with the static and modal survey test results. CONTENTS

- Report of the correlation of the static FEM with static test results if any.

- Report of the correlation of the dynamic FEM with modal survey test results if any.

- Correlation of dynamic FEM with sine test results.

- Summary of test results For each of these 3 tests the correlation report should include:

- Comparison of test results before correlation - Modifications introduced in the model to correlate with the test results - Comparison of test results with FEM results after correlation - Assessment of the compliance with the applicable correlation requirements


2.22.11 D-ST11 - LCDA FEM Description Report

PURPOSE OF DOCUMENT Description of the FEMs to be used for the LCDA CONTENTS - Description of the LCDA FEMs - Description of the System of units - Description of coordinate systems - Rules for numbering - Assumptions, idealizations and limitations - General description of the model including figures - Global mass and inertia properties - Description of interfaces, listing the interface nodes and boundary conditions - Results of the mathematical correctness checks, including as a minimum:

- 1g gravity check - Rigid body strain energy check - Normal models analyses in free and fixed boundary conditions - Thermo-elastic analysis check for those models that will be used for thermo-elastic analysis

- Description of the procedure to run the models (including analysis parameters to be used) - Reporting of the validation of these models.


2.22.12 D-ST12 - LCDA Results Assessment Report

PURPOSE OF DOCUMENT To report and analyse the results of the LCDA. CONTENTS

Provide reporting of the results of the coupled dynamic analysis of the spacecraft and the launcher:

- internal accelerations,

- CoG acceleration,

- interface loads,

- bending moment.

For each internal equipment, including the primary structure, report the assessment of the qualification of the equipment and give the margins.


2.22.13 D-ST13 - Acoustic, Sine & Shock Test Design Assessment Report PURPOSE OF DOCUMENT

To assess the mechanical design and its suitability for the expected mechanical loads.

CONTENTS Report the assessment of the suitability of equipment qualification loads as a result of the satellite acoustic, sine and shock tests.


2.22.14 D-ST14 – FEM Requirements Specification

PURPOSE OF DOCUMENT To specify the requirements for the Finite Element Model (spacecraft or element). CONTENTS To be specified by the contractor and agreed by the Agency


2.22.15 D-ST15 – EarthCARE STM Specification

PURPOSE OF DOCUMENT To define the requirements for Structural and Thermal Model of the EarthCARE spacecraft. CONTENTS

The document shall contain as applicable:

- applicable documents (including support specifications)

- performance requirements including reliability

- functional requirements including FDIR

- operational requirements - electrical requirements (RF, signal, power, grounding, data handling, command and control) - software requirements - mechanical requirements - thermal requirements - interface requirements - environmental requirements - EMC/RFC requirements - GSE requirements - Verification requirements - PA Where appropriate, the document may simply identify the differences from the requirements of the Flight Model.


PURPOSE OF DOCUMENT

2.22.16 D-ST16 – EarthCARE STM Description

To provide a comprehensive technical description of the EarthCARE Structural and Thermal Model, including external interfaces and instrumentation. CONTENTS

Technical description, to include:

- Introduction - Model objectives - Instrumentation accommodation - Model configuration - Baseline STM description - Description of key features and interfaces - STM budgets summary - External interfaces


2.23 Software Related Documents

2.23.1 D-SW1 - On Board Software Overview

PURPOSE OF DOCUMENT To identify each piece of SW used on the satellite. CONTENTS The document shall identify each piece of software on the spacecraft and identify the documented means of controlling each of the on board interfaces concerned.


2.23.2 D-SW2 - On Ground Software Overview PURPOSE OF DOCUMENT

To identify each piece of SW used on ground.

CONTENTS The document shall identify each piece of ground software and identify the documented means of controlling each of the ground interfaces concerned. This specifically includes EGSE application software used for checkout.


2.23.3 D-SW3 - Requirements Baseline and Interface Requirements (RB)

PURPOSE OF DOCUMENT

The RB expresses the custo’er's requirements. It is generated by the requirements engineering processes.

CONTENTS As per ND15 and ND111. This Requirements Baseline (including Interface Requirements Document) shall be produced separately for each piece of ground or flight software.


2.23.4 D-SW4 - Technical Specification including Interface Control Document (TS)

PURPOSE OF DOCUMENT

The TS contains the suppl’er's response to the requirements baseline, and is the primary input to the PDR review process.

CONTENTS As per ND15 and ND111 This Technical Specification (including Interface Requirements Document) shall be produced separately for each piece of ground or flight software.


2.23.5 D-SW5 - Design Justification File for Re-Used Software

PURPOSE OF DOCUMENT Provides sufficient evidence that existing software (if any) can be re-used safely. CONTENTS As defined in ND15, ND111 and ND44 The document shall identify any software intended for re-use from other programs. It shall provide evidence, in the form of a Design Justification File, that this software is properly specified, tested and accepted in accordance with the applicable documents and standards. References to historical tests for flight software must include proof that each branch of code in each module has been tested at least once.


2.23.6 D-SW6 - Software Development Plan

PURPOSE OF DOCUMENT To establish for all on-board S/W, a plan for all the software activities to be performed during the entire software life cycle, starting with the specification of the S/W requirements and ending with the delivery of the fully tested S/W. The tools required for the different S/W activities shall also be defined. CONTENTS This Document shall be applicable to all on-board S/W including instruments and sub-systems. It shall contain as a minimum: - list of all S/W documents to be delivered, together with a brief description of the purpose and contents of each

document, such as: - S/W Requirements Documents (SRD) - S/W Design Document (SDD) - S/W Test Plan - S/W Test Procedures - S/W Test Report

- S/W Integration Procedures

- S/W Users Manual

- source code listing

- identification of all S/W reviews and major S/W milestones.

- Selection of the high-level programming language.

- S/W Integration Plan

- S/W Configuration Status List

- H/W-S/W Integration Docs

- development schedule


2.23.7 D-SW7 - Plan for Independent Onboard S/W Verification and Validation

PURPOSE OF DOCUMENT Plan for the performance of an Independent Software Verification and Validation (ISVV) campaign. CONTENTS The document shall specify the planning, selection and briefing of an independent software verification and validation contractor for the on board software, who shall be involved in the review process for the requirements baseline. In this document the satellite prime contractor shall provide full visibility regarding the organisation and activities of this independent team.

The document shall be prepared in accordance with the ND15, ND111 and ND44 requirements.


2.23.8 D-SW8 - IV&V Report PURPOSE OF DOCUMENT Provides the outputs of the ISVV (Independent Software Verification and Validation) campaign (part of the Design Justification File [D-SA3]). CONTENTS The document shall provide the outputs of the validation of the on board software by the IV&V team, who have independently performed a set of verification and validation tests. The document shall be prepared in accordance with the ND15, ND111 and ND44 requirements.


2.23.9 D-SW9 - Software Design Definition File

PURPOSE OF DOCUMENT

The DDF is a supplier-generated document that documents the result of the design engineering processes.

CONTENTS As per ND 15 and ND111.


2.23.10 D-SW10 - Software Design Justification File

PURPOSE OF DOCUMENT The DJF is generated and reviewed at all stages of the development and review processes. It contains the documents that describe the trade-offs, design choice justifications, test procedures, test results, evaluations and any other documentation called for to justify the design of the suppl’er's product. CONTENTS As per ND15 and ND111.


2.23.11 D-SW11 - User Manual and Maintenance Manual for SDVE

PURPOSE OF DOCUMENT Contains all information necessary for the installation, use and maintenance of the SDVE (Software Development and Validation Environment), both by the contractor and external parties (e.g. the ISVV contractor). CONTENTS The SVDE User and Maintenance Manual shall include all necessary information about the SDVE hardware and software for unit testing, verification, validation and metrication. This specifically includes compilers, linkers, emulators, simulators and test tools, as well as the flight software itself. This SDVE User and Maintenance Manual is also intended to be used by the independent software verification contractor.


2.23.12 D-SW12 - SDVE Specification

PURPOSE OF DOCUMENT To specify the requirements for the Software Development and Validation Environment (SDVE) CONTENTS Specification of the SDVE for production, testing, verification and validation of the flight software in terms of: - definition and architecture - SW-design and test tools - simulation requirements (environment, protocols) - hardware requirements - interfaces - design and development Limitations of the SDVE (subject to agreement by the Agency) shall be clearly identified.


2.23.13 D-SW13 - Software Release Note PURPOSE OF DOCUMENT

This document identifies the configuration, configuration changes and software / media identifiers for a specific software release.

CONTENTS As per ND111 Annex D.


2.23.14 D-SW14 – Set of Software Documents for Units Containing Software

PURPOSE OF DOCUMENT This set of documents provides the complete description of software contained in a unit. CONTENTS As defined in AD2 (SOW) Annex A. (tailoring of ND15)


2.24 Thermal Related Documents

2.24.1 D-TH1 - Satellite Thermal Design Requirements Specification

PURPOSE OF DOCUMENT To define a common set of thermal design definitions, requirements and rules for use in thermal design activities at satellite, payload and platform instrument/sub-system and equipment level. CONTENTS Thermal design requirements in terms of: - satellite configuration and thermal architecture - dimensioning rules (including design/qualification/acceptance temperature ranges and relevant margins) - thermal design requirements - thermal performance requirements

- thermal analysis requirements - common design and construction requirements (e.g. materials, thermo-optical properties, etc...)

- thermal analysis campaigns identification and implementation logic - maintenance and verification requirements. Further, the document shall provide an exhaustive list of all definitions and terms used in the thermal design fields for the EarthCARE project. The contents of this document can be combined with those ones of [D-ST1] in a single “Satellite Mechanical and Thermal Design Requirement Specification”.


2.24.2 D-TH2 - Trade- Off Studies

PURPOSE OF DOCUMENT To describe the results of trade-off studies performed on the thermal design (part of [D-SA 3]). CONTENTS This document shall describe the trade-off studies and their results, which lead to the chosen thermal design solutions. It should report how the thermal design has been optimised with respect to margins, mass, power consumption, reliability and cost. This includes the derivation of energy balances, sensitivities and flexibility of the design. Special attention shall be given to the (atomic oxygen) environment and its impact on the degradation of the thermal system elements.


2.24.3 D-TH3 - Thermal Design Report

PURPOSE OF DOCUMENT Describes the thermal design (part of [D-SA9]). CONTENTS The document shall identify the boundary conditions applied to the system and instruments. It shall describe the thermal design solutions chosen for the satellite and its instruments, such that they ease individual and combined thermal analyses and tests and also enhance flexibility, trimmability and ease of repair. This shall include the results of a critical assessment of the suitability of all thermal H/W considering the particular constraints of the mission and the natural and induced environment encountered.


2.24.4 D-TH4 - Thermal Analysis Report of Satellite and Instruments

PURPOSE OF DOCUMENT To report the results of the satellite thermal analysis. CONTENTS

The document shall report the results of thermal analyses of the satellite using a thermal mathematical model [M-TH1] for all nominal and contingency mission phases (including launch and LEOP).

The level of detail shall be sufficient to demonstrate that all requirements are fulfilled. Full performance of the thermal control subsystem shall be demonstrated for the specified lifetime. The report shall also include: - temperature prediction uncertainties, considering modelling errors and realistic variations of all parameters,

sensibly affecting the thermal performance - temperatures of the instrument models for comparison with the system model - temperature fields of the Spacecraft and the Instruments, which fulfil the requirements of the structure thermo-

elastic analyses.


2.24.5 D-TH5 - Report of Satellite/Launcher Coupled Thermal Analysis

PURPOSE OF DOCUMENT To report the results of the satellite/launcher coupled thermal analyses. This applies to the ground environment (inside the fairing) and during the flight ascent. CONTENTS The document shall report the coupled thermal analyses performed using mathematical models [M-TH2] of the Spacecraft in line with the requirements of the Launcher Authority (if not performed by the Launcher Authority).


PURPOSE OF DOCUMENT

2.24.6 D-TH6 - Temperature Predictions for TB/TV tests

To provide temperature predictions for the TB/TV tests.

CONTENTS The document shall provide the temperature predictions for TB and TV tests carried out at instrument and satellite level. Thermal mathematical models suitably adapted to the test environment shall be used.


2.24.7 D-TH7 - TB Tests Correlation with TMM’s

PURPOSE OF DOCUMENT To correlate thermal test data with TMMs. CONTENTS This document shall correlate the temperature measurements taken during the Thermal Balance tests with the temperature predictions done before the TB tests by adapting the TMMs [M-TH1] following pre-defined correlation criteria, which are agreed with the Agency. In particular, correlation of the instrument models shall be reported.


2.24.8 D-TH8 - Post Test Flight Predictions

PURPOSE OF DOCUMENT To predict in-flight temperatures CONTENTS This document shall provide post-test flight predictions using correlated TMMs suitably adapted to the flight environment. These predictions shall consider both the design cases (with margins) and the most likely in-flight temperatures. In addition to the extreme design cases, predictions shall be made for nominal cases.


2.24.9 D-TH9 – Measurement Point Plan

PURPOSE OF DOCUMENT This document identifies the type and location of all thermocouples applied to the test item during environmental testing. This enables an accurate mapping to be made of the temperatures in all parts of the spacecraft during the test campaign. CONTENTS This shall contain as a minimum:

• Thermocouple identifier • Location (reference to layout drawing) • Thermocouple type • (if necessary) Thermocouple characteristics


2.24.10 D-TH10 – Test Heater Plan

PURPOSE OF DOCUMENT To document the needs analysis and intentions for placement / use of heaters, including aids used to represent more closely the eventual flight environment (e.g. Earth reflectance) during TV testing. CONTENTS

To be specified by the contractor and agreed by the Agency


2.24.11 D-TH11 – In-Orbit Thermal Report PURPOSE OF DOCUMENT

To report the actual in-orbit thermal performance of the EarthCARE satellite and elements. CONTENTS

To be specified by the contractor and agreed by the Agency


2.24.12 D-TH12 – TMM Requirements Specifications

PURPOSE OF DOCUMENT To specify the requirements for the Thermal-Mathematical Model. CONTENTS To be specified by the contractor and agreed by the Agency

-- End of the document--