estec MetOp-SG Instruments Document Requirements Definition [DRD] MOS-LI-ESA-INS-0437

Transcription

1 estec European Space Research and Technology Centre Keplerlaan AZ Noordwijk The Netherlands T +31 (0) F +31 (0) MetOp-SG Instruments Document Requirements Definition [DRD] MOS-LI-ESA-INS-0437 Prepared by ESA MetOp-SG Team Reference MOS-LI-ESA-INS-0437 Issue 1 Revision 0 Date of Issue 17/07/2012 Status Approved/Applicable Document Type List Distribution

2 Title MetOp-SG Instruments Document Requirements Definition [DRD] Issue 1 Revision 0 Author MetOp-SG Team Reviewed by Signed on original Date 17/07/2012 Date Approved by Date Signed on original Reason for change Issue Revision Date Issue Revision Reason for change Date Pages Paragraph(s) Page : 2/69 Document: MOS-LI-ESA-INS-0437

3 Table Of Contents 1 INTRODUCTION Scope Applicability DOCUMENTS Applicable Documents DOCUMENTATION DESCRIPTION INSTRUMENT PROJECT MANAGEMENT INSTRUMENT LEVEL DOCUMENTS INSTRUMENT SYSTEM ENGINEERING INSTRUMENT SUPPORT SPECIFICATIONS INSTRUMENT INTERNAL AND EXTERNAL INTERFACES INSTRUMENT DRAWINGS INSTRUMENT ASSEMBLY, INTEGRATION AND VERIFICATION INSTRUMENT PRODUCT ASSURANCE Page : 3/69 Document: MOS-LI-ESA-INS-0437

4 1 INTRODUCTION 1.1 Scope The MetOp-SG Instruments Documentation Requirement Description [DRD] outlines the content requirements of the deliverable documents listed in the MetOp-SG Instruments Document Requirements List [DRL] [AD15]. Throughout this document, the following terms are used: - ESA to refer to ESA as the top level customer for MetOp-SG; - the Customer to refer to the relevant MetOp-SG satellite Prime Contractor, who represents the immediate customer with respect to the MetOp-SG instrument Prime Contractor; - the Supplier to refer to the MetOp-SG instrument Prime Contractor; - the Project to refer to the specific MetOp-SG instrument project. 1.2 Applicability Unless otherwise stated, the document requirements are applicable to all instruments developed under the ESA MetOp-SG Programme, i.e.: - MicroWave Sounder (MWS); - SCAtterometer (SCA); - Radio Occultation sounder (RO); - MicroWave Imager (MWI); - Ice Cloud Imager (ICI); - Multi-viewing, Multi-channel, Multi-polarisation Imager (3MI). Page : 4/69

5 2 DOCUMENTS 2.1 Applicable Documents The following documents are applicable to this DRD. AD Title Reference AD14 MetOp-SG Instruments Product Assurance And Safety Requirements [PARD] MOS-RS-ESA-INS-0434 AD15 MetOp-SG Instruments Management Requirements [MARD] MOS-RS-ESA-INS-0435 AD16 MetOp-SG Deliverable Items And Services List [DISL] MOS-LI-ESA-SYS-0067 AD17 MetOp-SG Instruments Document Requirements List [DRL] MOS-LI-ESA-INS-0436 Page : 5/69 Document: MOS-LI-ESA-INS-0437

6 3 DOCUMENTATION DESCRIPTION The DRD is structured according to families, with the following identification code: ins-typ-nn where ins represents the Instrument Code as defined below; typ represents the Family Type as defined below; nn represents a number. Instrument Code ICI MWS MWI RO SCA 3MI Family Type PM IN SY SS IF DR AV PA Description Ice Cloud Imager MicroWave Sounder MicroWave Imager Radio Occultation sounder SCAtterometer Multi-viewing, Multi-channel, Multi-polarisation Imager Description Instrument Project Management Instrument Level Documents Instrument System Engineering Instrument Supporting Specifications Instrument Internal and External Interfaces Instrument Drawings Instrument AIV (including GSE aspects) Instrument Product Assurance and Safety For consistency across the MetOp-SG programme, the defined DRL references are the same for all MetOp-SG instruments, with the exception a unique prefix code as defined above. In the subsequent tables the Instrument Code is identified as ins, which shall be replaced by the specific Instrument Code for a given instrument, e.g. instead of ins-pm-01, MWI-PM-01 shall be used for the MWI instrument, 3MI-PM-01 for the 3MI instrument, etc. If the specific DRD is not provided in this document, the ECSS references provided in the DRL are considered sufficient to define the document needs. Page : 6/69 Document: MOS-LI-ESA-INS-0437

7 4 INSTRUMENT PROJECT MANAGEMENT DRL NO.: ins-pm-02 TITLE: Progress Report Provide the actual status of the Project to the Customer/ESA on all levels on and below the responsibility of the Supplier. The progress report shall be an extension of Annex E of ECSS-M-ST-10C, Rev 1 in order to cover the various information as required by MetOp-SG Instruments PARD [AD12] and MARD [AD13]. Progress reports shall at least cover the following subjects: Overall Assessment o Project Manager s assessment o Key problem list, high-lighting adverse trends in technical, schedule and cost performance, identification of potential problem areas and the respective proposals for corrective actions o Open Action Items requiring special attention o Risk assessment Schedule Status as per Schedule Report (DRL {ins-pm-08}) o The schedule shall also be provided as MS Project file (see MARD [AD13], Section 7) Technical Status o System Engineering o Status per discipline (Mechanical, Thermal, Electrical, AOCS/dynamics, Software, Mission/Operations, etc.) o Summary Budget Status (spec. versus current) Development/AIV/GSE o Instrument Status PA/Configuration aspects EEE parts procurement Status Lists of Waivers/deviation, Non Conformances Action Items Status List Documentation Status (DCN, documents issued in the last reporting period) Meeting list (meetings held in the last reporting period with MOM ref., meetings planned in the next reporting period) Procurement and Financial Status (as separate Annex to the Progress Report) o Procurement status (overview, achievements in the previous period, plan for the next period) o Contract Change status o Invoice status Risk Register and Risk Report Page : 7/69 Document: MOS-LI-ESA-INS-0437

8 DRL NO.: ins-pm-03 TITLE: Project Meeting Plan Schedule of planned technical and progress meetings at Supplier and lower tier supplier level. The Supplier shall prepare and update a list of Supplier and lower tier supplier meetings and visits planned during the 3 months following the date of submission of the document. The list shall clearly specify: Main subject of the meeting Name and location of the company organising the meeting Contact point of meeting Date, time and duration Participating companies DRL NO.: ins-pm-05 TITLE: Project Directory To facilitate communications among the Customer, the Supplier and lower tier suppliers. The Supplier shall generate and maintain a Project Directory with the following information as a minimum: Company name Company code Company location Company postal address Company telephone and fax numbers Key personnel with their: o Responsibility o Name o Department o Telephone extension o Full address(es) including electronic mail nickname This shall be provided in electronic format to the Customer for incorporation in the overall MetOp-SG Project Directory. Page : 8/69 Document: MOS-LI-ESA-INS-0437

9 DRL NO.: ins-pm-11 TITLE: Action Item Status List 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. The Action Items system contains datasets of agreed Project action items defined in reviews, meetings or other Project events to which the Customer and ESA have right of attendance with at least the following information: Action item number (unique coding structure) Assigned actionee, company and discipline Action item title or brief definition/description Action item issue date and action item due date Action item close-out date and close-out document ref. Information Action item status code (open, pending, closed withdrawn) Action item initiator Action item origin DRL NO.: ins-pm-18 TITLE: Contract Structure Provide a full overview of the contract structure, including all contracts within the Project and their interrelations. The content shall be in accordance to the MARD [AD13]. The Contract Structure (CS) shall represent the contractual hierarchy of the project including all suppliers, 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 Contract, the Contractor shall update the CS as appropriate. The elements of the CS shall make reference to the relevant elements of the WBS. The CS, and any updates thereon are subject to the Agency s approval. Page : 9/69 Document: MOS-LI-ESA-INS-0437

10 DRL NO.: ins-pm-21 TITLE: Document Change Notice (DCN) Provide a detailed description of all aspects related to such a document change. Should include at least the following: Document Reference Items to be changed Reason for change Requirements affected Fields for signatures (for acceptance of change) DRL NO.: ins-pm-22 TITLE: Contract Close-out Data Package Provide evidence that all aspects of the contract have been completed in accordance with all the contractual documents. The report shall include a list of all activities considered a pre-requisite for contract close-out, and the corresponding evidence of these activities having been satisfactorily completed. The document should contain as a minimum: Contract duration Warranty conditions Contract Type Contract and CCN scope including list of Class A and B CCNs Statement on close-out status of Subcontractors and Suppliers, if applicable Financial close-out including final Payment and Invoice Status List and final geographical Distribution Status Inventory Status List Statement of non-inventions Lessons-Learned (Sub)contract as reference Page : 10/69

11 DRL NO.: ins-pm-24 TITLE: Project Organisation Breakdown Structure Provide a complete description of how the Project is organised and structured for each supplier. The content shall be according to the MARD [AD13]. The Project Organisation Breakdown Structure (OBS) shall present the Supplier 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 lower tier supplier shall provide his own OBS as per the above guidelines. The Supplier and his entire lower tier supplier 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, Risk Management Engineering. The Supplier shall include at least all key personnel addressed into this document also into his Project Directory. Page : 11/69

12 DRL NO.: ins-pm-25 TITLE: Industrial Procurement Plan Defines the process and specific sequence the Supplier intends to use in selecting Subcontractors, as well as the specific potential lower tier suppliers. 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 Supplier Items to be purchased or subcontracted by the Supplier Items to be subcontracted under Customer responsibility Items to be sub-contracted under lower level supplier responsibility Identification of potential bidders Procurement, planning of activities Procurement logic for significant items (item by item) ITT Planning For each item indicate the level of maturity, and identify the necessary developments (if applicable). DRL NO.: ins-pm-27 TITLE: Document Status List Defines all the documents already delivered or to be delivered throughout the Project, and their current delivery status. The DSL shall contain as a minimum: System/sub-system/equipment to which the document belongs Company/entity responsible for the document Document reference DRL reference (if applicable) Issue number Current delivery status o Planned Delivery Date o Actual Delivery Date Next foreseen release Remarks (if any) to the current status and/or next release Page : 12/69

13 5 INSTRUMENT LEVEL DOCUMENTS DRL NO.: ins-in-01 TITLE: Instrument Design and Technical Description To describe the instrument design and its operational, functional and performance characteristics from instrument level down to unit/module level. The Instrument Design shall be defined consistent with Annex G of ECSS-E-ST-10C (DDF). Instrument description in terms of: Instrument design principle Instrument architecture Instrument calibration Instrument Operations concept Operational modes Functional modes Instrument performance Block diagram down to equipment level with description of each equipment block and performance Electrical interfaces Thermo/mechanical interfaces Optical/RF design (with more details in {ins-in-07}) Antenna / Reflector / Quasi-optics / Receiver / Optics / Focal Plane Assembly / Detector Ground processing algorithm assumptions Mechanical design Electrical design Thermal design Power distribution Command / control concept (including datation) Timing diagram On-board processing Software architecture (including lower level specification tree and parameters) Overall configuration Harness Mechanisms Page : 13/69

14 DRL NO.: ins-in-02 TITLE: Instrument Requirements Specification To specify requirements at instrument level in terms of measurement performance, interface specifications and verification requirements. Draft version from the Supplier for the Phase B2/C/D/E1 offer; thereafter, to be provided and maintained by the Customer. Instrument requirements specifications in terms of: Applicable documents Functional requirements Units breakdown Operational requirements Performance requirements Calibration and characterisation requirements Electrical requirements (signal, power, telemetry, data processing, control) Mechanical requirements Thermal requirements Interface requirements Environmental requirements EMC/ESD/RFC design requirements Page : 14/69

15 DRL NO.: ins-in-05 TITLE: Instrument Technical Budgets Report To provide all the budgets of the instrument. The document shall comply with ECSS-ST-10C, Annex I. All instrument current budgets down to subsystem/equipment level, including (as applicable for each instrument): Engineering Budgets: Mass and mass properties Power and thermal budgets (including power dissipation and heater power, with detailed power consumption profiles with temporal resolution consistent with the thermal control regulation frequency) TM/TC and data bus exchange budgets Software and memory budgets Performance, data quality budget, reliability and availability budgets Synchronisation and datation budget EMC/EMI budget DC/AC magnetic budget Alignment and tolerance budgets Pointing budget Geolocation budget Calibration budget and error budget Performance Budgets: RF performances Spatial and spectral performances Radiometric performance budget Calibration budget and error budget Characterisation error budget Pointing / alignment performances Instrument calibration budgets End-to-end calibration budgets As annex to the document, the following shall also be delivered: Engineering budgets tools and mathematical models Performance budgets tools and mathematical Models Note: The source of the numbers contained in the budgets shall be referenced with their source (Supplier estimation, measured, etc.) stating the original document. The budgets shall contain, as a minimum, the indication of the current best estimate, applied margins and specified values. In addition, the budget trends should be included by including a table with the recording of all budgets variations since start of the contract. Page : 15/69

16 DRL NO.: ins-in-06 TITLE: Instrument Budgets and Margins Definition Document Presentation of the budget with margin philosophy. The document shall comply with ECSS-ST-10C, Annex I and with the specific MetOp-SG budgeting rules. The document shall contain as a minimum the margin philosophy adopted for Engineering and Performance Budgets (in line with {ins-in-05}). The final budget is to be recalled in details, with its justification. All instrument current budgets specified within {ins-in-05} shall follow a detailed methodology for managing aspects related to margin philosophy, margin evolutions from AIT before launch, for BOL and for EOL inorbit. Note: Probabilistic approach for each methodology shall be preferred considering tools able to process simultaneously and globally all statistical phenomena represented by their physical characteristics. DRL NO.: ins-in-07 TITLE: Instrument Design Justification File Presentation of the design including CADs and justification. For the design justification, the document shall include: Analysis as a minimum as listed in the applicable documentation Trade-off approach General trade-off criteria Summary of system trade-offs Results and conclusions Link to detailed technical notes on specific subjects (e.g. {ins-in-10}, {ins-in-10a}, {ins-in-10b}) For the Design Justification Files, the document shall include: Optical design model (Code V or Zemax) and CAD model For stray light analysis, the ASAP (or equivalent) model RF design model Sun ray intrusion model and multi-path analysis model For Thermal analysis the ESARAD and/or ESATAN For mechanical analysis the NASTRAN or equivalent This DRD applies to Design Justification Files through all Instrument levels of design and development, down to sub-equipment level. Page : 16/69

17 DRL NO.: ins-in-08 TITLE: Instrument Performance Model Description To describe the instrument performance model(s) and study the expected performance of the instrument based on available data and thereby demonstrate the ability of the instrument, and of the associated instrument calibration, to comply with specified performances. The document shall include: Instrument calibration and performance requirements summary List of parameters influencing the performance Mathematical formulation of the problem Transfer functions Sensitivity to parameters Results budgets: synthesis only (extensive budgets in {ins-in-05}) Performance Mathematical Model DRL NO.: ins-in-10a TITLE: Instrument Straylight Analysis Reporting of Straylight Analyses and results. Applicable only for 3MI. The document shall include as a minimum: Scope of analysis Analysis performed including sub-equipment test results used to perform the analysis at instrument level Analysis performed including instrument test results to validate the straylight model The analysis shall take into account all the optical elements, the housings and any involved surfaces, the various scan angles, the baffles and any other contributors Summary and conclusions This DRD applies to technical notes through all Instrument levels of design and development, down to subequipment level. Page : 17/69

18 DRL NO.: ins-in-10b TITLE: Instrument Tolerance Analysis Reporting of the tolerance analysis and results. Applicable only for ICI, MWI, MWS and 3MI. The document shall include as a minimum: Scope of analysis Tolerance analysis method description Tolerance analysis computation results: tolerance analysis taking into account all potential contributors (e.g. manufacturing errors, alignment errors, thermal variations, etc.) affecting the system performance (integrated energy, co-registration, etc.) for the end-to-end optical/rf system. This analysis will include all optical/rf components, reflecting the way the optical/rf system will be integrated and aligned (including potential compensators). For optical instruments, this analysis shall be based on a Monte Carlo simulation in an optical design software used in tolerancing mode Summary and conclusions This DRD applies to technical notes through all Instrument levels of design and development, down to subequipment level. DRL NO.: ins-in-10c TITLE: Impact Analysis of In-Orbit Radiation Environment on Detector To assess the impact of the in-orbit radiation environment on the instrument performance. Applicable only for 3MI. The impact of the in-orbit radiation environment on the instrument performance shall be assessed and quantified. The impact on instrument calibration, 0-1b data processing and instrument operations shall be assessed. In particular, the following effects need to be considered: 1. Pixel-dependent detector dark current increase. 2. Potential pixel-dependent, time-correlated dark current variations (e.g. RTS effects, 1/f). 3. Accuracy of background correction. 4. Detector temperature dependance on the RTS effect. 5. How to cope with the above points in-orbit to maintain accuracy of level 1b data products: timedependent calibration key data, impact on instrument operations scenario to enable in-orbit measurements with sufficient time resolution. The results shall be used to provide inputs to the system calibration plan in general, and to the in-orbit calibration plan in particular. Page : 18/69

19 DRL NO.: ins-in-10d TITLE: Instrument Sun Intrusion Analysis Reporting of the sun intrusion analysis and results. Applicable only for ICI, MWI and MWS. The document shall include as a minimum: Scope of analysis Model representation used for the instrument/satellite Analysis performed The analysis shall take into account all the contributing elements from the satellite and other instruments, as well as variations around the orbit and around the year Impacts on instrument performances and any mitigation measures (e.g. sun shields) to be implemented Summary and conclusions DRL NO.: ins-in-10e TITLE: Instrument Multi-Path Analysis Reporting of the multi-path analysis and results. Applicable only for RO and SCA. The document shall include as a minimum: Scope of analysis Model representation used for the satellite Analysis performed The analysis shall take into account all the contributing elements from the satellite and other instruments, as well as variations around the orbit Impacts on instrument performances and any mitigation measures to be implemented Summary and conclusions Page : 19/69

20 DRL NO.: ins-in-10f TITLE: Instrument RF Interference Analysis Reporting of the RF interference analysis and results. Applicable only for ICI, MWI, MWS, RO and SCA. The document shall include as a minimum: Scope of analysis Model representation used for the satellite and all RF sources (including frequencies, power levels and couplings from source to the instrument) Analysis performed The analysis shall take into account all the RF transmitters from the satellite and other instruments, including any scan dependent effects from other instruments or the receiving instrument Impacts on instrument performances and any mitigation measures to be implemented Summary and conclusions DRL NO.: ins-in-10g TITLE: GNSS Acquisition, Tracking and Processing Algorithms Analysis Reporting of the analysis of algorithms for acquiring, tracking and processing GNSS signals from GPS, Galileo, GLONASS and Compass-BeiDou. Applicable only for RO. The document shall include as a minimum: Scope of analysis Details of GNSS signals to be processed Analysis performed Impacts on algorithms to be implemented in the instrument Instrument processor loading and margins Summary and conclusions Page : 20/69

21 DRL NO.: ins-in-11 TITLE: Instrument Design, Development and Verification Plan To define the overall Instrument design, development and verification activities. The design, development and verification plan shall be based on ECSS-E-ST-10C and Annex A of ECSS-E-ST C and shall include as a minimum: Instrument overview including major functional elements and subsystems General design and engineering considerations; including performance, optical design, mechanical/thermal design, electrical design, EMC/ESD/RFC aspects, software development and validation (see {ins-sa-23}), EGSE/MGSE (see {ins-av-03}) Technology plan and technology matrix (as per ECSS-ST-10C Annexes E and F) Model philosophy Overview of design & verification limitations and constraints Verification strategy, programme, tools, methodology, documentation and organisation (as per ECSS- ST-10-02C) Verification Plan (as per Annex A of ECSS-ST-10-02C) Qualification and acceptance approach Instrument design and development flow Instrument integration flow Major Test sequences for Instrument development models, protoflight and recurrent models Definition of special test equipments and facilities (at instrument and satellite level) Description of satellite level activities Hardware and software breakdown, where applicable Page : 21/69

22 DRL NO.: ins-in-11a TITLE: Subsystem and Equipment Design, Development and Verification Plan(s) To define the overall design, development and verification activities for the associated instrument subsystems and equipment(s). The design, development and verification plan shall be based on ECSS-E-ST-10C and Annex A of ECSS-E-ST C and shall include as a minimum: Subsystems and equipment(s) overview including its major functional elements General design and engineering considerations; including performance, optical design, mechanical/thermal design, electrical design, EMC/ESD/RFC aspects, software development and validation (see {ins-sa-23}), EGSE/MGSE (see {ins-av-03}) Technology plan and technology matrix (as per ECSS-ST-10C Annexes E and F) Verification strategy, programme, tools, methodology, documentation and organisation (as per ECSS- ST-10-02C) Verification Plan (as per Annex A of ECSS-ST-10-02C) Model philosophy Overview of design & verification limitations and constraints Qualification and acceptance approach Design and development flow Integration flow, if adequate Major test sequences for development models, protoflight and recurrent models Definition of special test equipments and facilities, if adequate Hardware and software breakdown, where applicable Page : 22/69

23 DRL NO.: ins-in-12 TITLE: Instrument AIT Plan To define and control the instrument assembly, integration and test plan. To define the full qualification and acceptance test programmes from instrument level down to subsystem/equipment level. The document shall comply with ECSS-ST C and ECSS-10-03A. The document shall include: Integration Plan in terms of integration approach, methods and responsibilities. Qualification and acceptance test programme definition in terms of: o Test philosophy o Model philosophy o Test conditions o Hardware/software matrices o Qualification test programme o Acceptance level programme o Test plan and methods PA and safety provisions AIT planning, flow chart and test sequences Test matrices Page : 23/69

24 DRL NO.: ins-in-14 TITLE: Instrument Verification Matrix Provide a clear traceability and record of the verification approach and status of all instrument technical requirements. The document shall comply with ECSS-ST C. The instrument verification matrix shall support the verification control document {ins-in-13} and provide a clear traceability and status of the verification of the instrument requirements for each model developed. As a minimum they shall contain: A complete list of the Customer s requirements defined in the instrument requirements specification, the GDIR and the ICD Compliance status per requirement Verification stage, method (means) and levels Direct reference to the Analysis/Inspection/Review of Design/Test Plan/Procedures, under which the requirements will be validated Direct reference to Test (or Analysis/Inspection/Review of Design) Report demonstrating requirement has been achieved Any RFD/RFWs (and their status) resulting from NCs or test anomalies A list of all RFDs/RFWs occurring at the lower levels (subsystem and/or equipments) which impact overall instrument level compliance/verification Clear indication where final instrument verification is reliant on satellite level testing and clear link to the appropriate satellite test plan Any necessary comments and clarification, as applicable These verification matrices shall constitute standalone documents issued at the time of the major instrument or satellite reviews and will provide a snap shot of the verification status at that time. Whilst it is recognised that this process will be actively traced through a living verification database, for which ESA has requested regular visibility, provision of the latest database WILL NOT constitute this delivery. The contractor shall extract all relevant data into a self standing document. Page : 24/69

25 DRL NO.: ins-in-14a TITLE: Subsystem and Equipment Verification Matrix Provide a clear traceability and record of the verification approach and status of all Subsystem and Equipment technical requirements. The document shall comply with ECSS-ST-10-02C. The verification matrices shall support the verification control document {ins-in-14} and provide a clear traceability and status of the verification of the respective requirements for each model developed. As a minimum they shall contain A complete list of the subsystem/equipment (derived) requirements Compliance status per requirement Verification means Direct reference to the Test Plan/Procedures, under which the requirements will be validated Direct reference to Test Report demonstrating requirement has been achieved Any RFD/RFWs (and their status) resulting from NCs or test anomalies A list of all RFDs/RFWs occurring at the lower levels (subsystem and/or equipments) which impact overall instrument level compliance/verification Clear indication where final verification is reliant on satellite and/or instrument level testing and clear link to the appropriate satellite test plan Any necessary comments and clarification, as applicable These verification matrices shall constitute standalone documents issued at the time of the respective Project reviews and will provide a snap shot of the verification status at that time. Page : 25/69

26 DRL NO.: ins-in-15 TITLE: Instrument Test Plans To define the test objectives, configuration and constraints for all instrument level test activities relating to development and flight models and encompassing qualification, acceptance and functional/performance validation. The document shall comply with ECSS-10-03A, Annex C. Test plans shall be generated for all major testing blocks throughout the instrument test campaigns. From these plans the detailed test procedures will be defined. The test plans shall include: The scope, objectives and requirements associated with the test Test success/failure criteria A detailed description of the test, including instrument configuration, test set up, test phasing and durations, special test equipments/conditions, test limitations and constraints Test implementation and responsibilities Test environment(s) and facilities including definition of test tolerances, instrumentation types and accuracy, test data processing tools Test Safety and contingency considerations Prior to the implementation of the major testing, the test plans will be approved by the Customer. All major instrument tests shall be preceded by a Test Readiness Review (TRR) and concluded with a Test Review Board (TRB). Page : 26/69

27 DRL NO.: ins-in-15a TITLE: Subsystem and Equipment Test Plans To define the test objectives, configuration and constraints for all instrument subsystem and equipment/unit level test activities relating to development and flight models and encompassing qualification, acceptance and functional/performance validation. The document shall comply with ECSS-10-03A, Annex C. Test plans shall be generated for all major testing blocks throughout the respective test campaigns. From these plans the detailed test procedures will be defined. The test plans shall include: The scope, objectives and requirements associated with the test Test success/failure criteria A detailed description of the test, including configuration, test set up, test phasing and durations, special test equipments/conditions, test limitations and constraints Test implementation and responsibilities Test environment(s) and facilities including definition of test tolerances, subsystem/equipment/unit type(s) and accuracy, test data processing tools Test safety and contingency considerations Page : 27/69

28 DRL NO.: ins-in-16 TITLE: Instrument Test Procedures To establish the procedures used in individual development, qualification and acceptance tests as foreseen in the Test Plans/Specifications of Instrument hardware and software at all instrument levels (i.e. instrument, subsystem and equipment). The test procedures shall include as a minimum: Pre-requisites for the test Starting conditions for the test 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 organisation Test conditions Test equipment and set-up, with configuration control status of all H/W S/W involved in the test (including Media control) Step by step procedure with pass/fail criteria Recording of data Pass/fail criteria for the complete test and test data evaluation requirements Criteria for test deviations and for retest The final test procedure shall be approved at the Test Readiness Review (TRR) held to authorise the start of the test. The As-Run Test procedure, with the recording of all measurements, NCR s and deviations occurred during the test, shall be presented at the Test Review Boards (TRB) organised according to the MARD [AD13] after the completion of the test. Page : 28/69

29 DRL NO.: ins-in-16a TITLE: Subsystem and Equipment Test Procedures To establish the procedures used in individual development, qualification and acceptance tests as foreseen in the Test Plans/Specifications of Subsystem and Equipment hardware and software. The test procedures shall include as a minimum: Pre-requisites for the test Starting conditions for the test 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 organisation Test conditions Test equipment and set-up, with configuration control status of all H/W S/W involved in the test (including Media control) Step by step procedure with pass/fail criteria Recording of data Pass/fail criteria for the complete test and test data evaluation requirements Criteria for test deviations and for retest DRL NO.: ins-in-18 TITLE: Instrument Test Correlation Reports To describe mathematical models modifications implemented to correlate analytical predictions with actual tested/measured data. The document shall highlight the modification introduced in the modelling to correlate the analytical predictions and the test/measurements results to satisfy the imposed correlation criteria. Re-validation of the correlated model shall also be included. As a minimum correlation reports will be required with respect to the mechanical, thermal designs of the instruments and performance modelling. Note: Each correlation report shall make precise reference to the unique name and version of the models before and after the correlation, as identified by the Configuration Control system and as delivered to the Customer. Page : 29/69

30 DRL NO.: ins-in-19 TITLE: Instrument Characterisation and Performance Verification Plan To define the full instrument characterisation / performance verification approach and programme, covering both the on-ground characterisation / performance verification and the in-flight characterisation / performance verification. The document shall define and address the full on-ground characterisation and performance verification approach and programme in terms of: Characterisation and performance verification approach, covering all relevant on-ground activities. Characterisation and performance verification definition / methods. Characterisation and performance verification tools and models (e.g. antenna model, etc.). Expected on-ground accuracies (for each characterisation / performance parameter), accuracy propagation and overall accuracy budget for characterisation / performance parameters. On-ground characterisation / performance verification measurement plan, flow and planning. Description and requirements for required on-ground support equipment: optical, mechanical, electrical and facilities, plus flow and planning thereof. Definition of relevant characterisation curves. The document shall define and address the full in-orbit characterisation and performance verification approach in terms of: Characterisation and performance verification approach, covering all relevant in-flight activities (commissioning phase as well as long-term performance monitoring approach beyond the commissioning phase), as well as the transition from on-ground to in-orbit. Characterisation and performance verification definition / methods. Characterisation and performance verification tools and models (e.g. antenna model, etc.). In-flight accuracies and performance (for each characterisation / performance parameter), accuracy propagation and overall accuracy budget for characterisation / performance parameters. Role and purpose of on-board hardware for short-term and long-term performance monitoring. Providing inputs to the instrument operations approach for commissioning and nominal operations for performance assessment and monitoring. In-orbit activities preparation, including algorithms readiness verification. In-orbit operational constraints. In-orbit operational characterisation constraints during commissioning. Image / FOV geolocation characterisation in line with {ins-in-22} and {ins-in-23} Radiometric and spectral characterisation in line with {ins-in-22} and {ins-in-23} The document shall also define and address the links between the characterisation / performance verification on the ground and in flight. Page : 30/69

31 DRL NO.: ins-in-20 TITLE: Instrument Calibration Plan To define the instrument calibration approach, covering both the on-ground calibration and the in-flight calibration. The document shall define and address the overall on-ground calibration in terms of: Calibration concept, theory and approach, covering all relevant on-ground activities. Calibration definition / methods. Calibration tools and models in line with {ins-in-29}. Expected on-ground calibration accuracies (for each calibration parameter), accuracy propagation and overall accuracy budget for calibration parameters and level-1b data products. On-ground calibration accuracy budget, in conjunction with 0-1b data processing and expected inflight accuracy for the level-1b data products. On-ground calibration measurement plan, flow and planning. Description and requirements for required on-ground support equipment: optical, mechanical, electrical and facilities, plus flow and planning thereof. The document shall define and address the overall in-orbit calibration in terms of: Calibration concept, theory and approach, covering all relevant in-flight activities (commissioning phase as well as long-term calibration monitoring approach beyond the commissioning phase), as well as the transition from on-ground to in-orbit. Calibration definition / methods. Calibration tools and models in line with {ins-in-29}. In-flight calibration accuracy budget, in conjunction with 0-1b data processing, accuracy propagation and overall accuracy budget for the level-1b data products. Role and purpose of on-board hardware within the overall calibration approach. Providing inputs to the instrument operations approach for commissioning and nominal operations for assessment and monitoring of the calibration parameters. In-orbit operational calibration constraints during commissioning. Definition of relevant calibration curves. The document shall also define and address the links between the calibration on the ground and in flight. Page : 31/69

32 DRL NO.: ins-in-21 TITLE: Instrument Data Simulator Requirements Specification To establish the requirements related to the instrument data simulator for performance verification and ground testing. The instrument data simulator specification shall cover as a minimum: Functional requirements Operational requirements Performance requirements Maintenance and Calibration requirements Transportability requirements The instrument data simulator shall be described in terms of: Architecture including focal plane or feed-horn cartography and scanning law/pattern (to be used at S/C level) Interfaces Functionality Operational requirements Thermo-elastic deformation (to be used at S/C level) Performance Users manual Page : 32/69

33 DRL NO.: ins-in-22 TITLE: Instrument Data Evaluation Algorithms Detailed Design Description To define the data evaluation algorithms to be used for analysing the instrument performance during onground and in-orbit characterisation and calibration tests. The document shall describe in detail the algorithms to be used to evaluate the overall instrument performance and to confirm compliance to the specifications during on-ground and in-orbit characterisation and calibration tests. This shall include, in particular, radiometric calibration / correction algorithms, algorithms for all calibration tests, averaging and sampling algorithms, evaluation or pass/fail thresholds. For each algorithm the document shall include: An overview of the algorithm including the objective or purpose of the algorithm; The rationale for the algorithm and the specifications it supports; A description of any external data used by the algorithm (if applicable); A description of the algorithm outputs (including intermediate products); A mathematical description of the algorithm; The algorithm executable code and source code and identification of the Operating System that the source code was built on; An error analysis showing the expected accuracy of the algorithm results; List of parameters influencing the performance and associated sensitivity analysis; A description of the methods used to validate the algorithm and the validation results; A list of references; A user manual. DRL NO.: ins-in-24 TITLE: Instrument Characterisation and Calibration Data Base Specification To specify and provide all calibration / characterisation data and information pertinent to their use for instrument and end-to-end system calibration and performance, calibration tools, ground processing, etc. The document shall include: calibration and characterisation parameter files, content and format description subsystem and equipment calibration and characterisation data instrument calibration and characterisation data error budgets For each calibration and characterisation parameter, the following data shall be included: File content and format (how to read it) File name of the calibration/characterisation Instrument configuration identifier Parameter file (look-up tables) Environmental conditions Reference to the tests, test set-up configuration, validation, etc. Page : 33/69

34 DRL NO.: ins-in-25 TITLE: Instrument Flight Operations Manual To provide all instrument design and operational information and data that is used as an input to ground segment and operations implementation and preparation and for the execution of all phases of instrument operations. The information required for the data processing and calibration is out of the scope of this document. The document shall include: Description of the instrument design, including top level description of ICU SW architecture, Description of operational modes including: o Purpose (i.e. conditions under which each mode shall be used) o Operational constraints o Resource utilisation o Definition of mode o Identification of allowed mode transitions and associated operational contraints. TM & TC data descriptions (details are included in inputs to SRDB {ins-sy-09}) Operations concept and scenarios Operational constraints Instrument failure analysis Instrument operations procedures complemented by electronic files as defined by the Customer. The information included with the procedures (nominal and contingency) shall include: o Purpose, and mission phases and/or conditions when applicable, o Description of the operation covered by the procedure, o o o Preconditions for the initiation of the procedure Description of the step-by-step operational sequence; preconditions for execution of each step, verification conditions, step interrelations, conditional and timing information. Instrument telecommand and telemetry shall be unambiguously identified by ID Description of parameters to be uploaded, including validity and references to algorithms as necessary. Identification of specific instrument parameters to be monitored for in-orbit, long-term trend analysis of instrument health and performance. Page : 34/69

35 DRL NO.: ins-in-29 TITLE: Instrument Performance and Calibration Analysis To study the expected performance of the instrument based on available data and thereby demonstrate the ability of the instrument, and of the associated instrument calibration, to comply with specified performances. The document shall include: Instrument calibration and performance requirements summary List of parameters influencing the performance Mathematical formulation of the problem Transfer functions Sensitivity to parameters Results budgets: o RF performances o Spatial and spectral performances o Radiometric performance budget o Calibration budget and error budget o Characterisation error budget o Pointing / alignment performances o Instrument calibration budgets o End-to-end calibration budgets DRL NO.: ins-in-30 TITLE: Instrument Contamination Analysis To describe the contamination analyses and provide results. The document shall contain a contamination analyses in line with the contamination plan and shall address as a minimum: Molecular and particulate contamination All (instrument) materials used in flight at their operating temperature All materials (instrument and GSE coming in close contact with the instrument) used on-ground within their operative ranges (temperature, pressure, humidity) A model shall be performed to assess the contamination (to be updated in line with the instrument milestones as needed) and its impact on the overall radiometric and spectral performances shall be analysed and documented. Page : 35/69

36 DRL NO.: ins-in-32 TITLE: Instrument Alignment Requirements and Control Plan To describe the instrument alignment requirements, the control of the alignment and the associated verification. The document shall contain the internal and external instrument alignment requirements; the implementation of the internal/external alignment requirements and its control; the associated verification approach; instrument alignment requirements at satellite level; methodology / procedure for instrument alignment at satellite level. Page : 36/69

37 DRL NO.: ins-in-35 TITLE: GPP Algorithm Theoretical Baseline Document (ATBD) To specify the Algorithm Theoretical Baseline for the instrument level 0-1b GPP software. The ATBD 0-1b data processing software description shall include as a minimum: Introduction, scope and role of level-1b data in overall instrument data processing. Brief description of relevant instrument characteristics, including in-orbit calibration and monitoring possibilities and relation to instrument operations concept. Measurement class description (for example earth radiance, sun irradiance, dark view, cold space view, on-board target/source, etc.). High-level description of relation between instrument operations and 0-1b GPP software. High-level descriptions of the physical principles of all correction, calibration and flagging algorithms required to transfer level-0 data into level-1b data to a level that the description would suffice to write the GPP Detailed Processing Model. High-level description of all variables involved in the above correction and flagging functions. High-level description of all calibration key parameters involved in the above correction and flagging functions. Algorithms include, but are not limited to: radiometric radiance correction, radiometric irradiance correction, radiometric irradiance goniometry correction, stray light correction, detector/receiver and electronics corrections (for example, PRNU, non-linearity, detector exposure smear, background correction, dark current calculation, bad/dead/rts pixel identification, RF interference), pixel quality flagging functions, pointing and geolocation determination, spectral calibration and assignment. High-level description of all algorithms involved in the uncertainty calculation for the level-1b data products. Uncertainty estimates for the level-1b data products and the scene radiance or irradiance (including numerical values). Product flow for the various algorithms applied to each measurement class. High-level description of quality control and statistics. High-level description of exception handling. High-level description of input files (for example, level-0 data, attitude and ephemeris data, calibration data, process control file, ancillary data). High-level description of output files (radiance, irradiance, calibration). High-level description of level-1b data product metadata. The GPP ATBD document shall include a forward model (instrument simulation software) of the measurement principles, physical processes and the instrumental processes that shows how the input radiance and irradiance spectra in physical units are transferred into measured level-0 data (digital counts per pixel). Subsequently, this knowledge shall be used to develop and describe the inverse process, i.e. transferring the level-0 data back into level-1b data in what is called the level 0-1b GPP software. The forward model shall be described such that the model allows for a direct comparison between predicted and actually measured instrument performance in order to understand critical performance parameters. The forward model shall have a possibility to modify instrument parameters in order to assess the impact on the performance. Such parameters can include for example antenna/reflector reflectances, mirror transmissions, grating efficiency, but also for example exposure time, gain factor, gain parameters, gain switch wavelengths, coaddition time, skip rows, etc. The most convenient way is to set up the forward model and level 0-1b GPP software (inverse model) such that they mutually can ingest each others input and output files. The ATBD shall be written such that parties which are external to the MetOp-SG / EPS-SG Project can understand the tasks the level 0-1b data processing is performing. The ATBD shall be written such that it can be distributed without restriction, also outside the Project. Page : 37/69