Document Contents Guideline for SWARM Subcontractorsemits.sso.esa.int/emits-doc/ASTRIUMLIM/SWARM_FEED... · SWARM Doc. No: SW-LI-EAD-SY-0005 Issue: 2 Document Contents Guideline for

SWARM Doc. No: SW-LI-EAD-SY-0005

Issue: 2

Document Contents Guideline for

SWARM Subcontractors Date: 10.04.2006

© EADS Astrium GmbH Page i File: SW-LI-EAD-SY-0005_2_Supplier_DCG.doc

DOCUMENT CHANGE DETAILS

ISSUE DATA SHEET DESCRIPTION

1 24.03.2006 all Initial Issue

2 10.04.206 All Update for approved ITT


Issue: 2



© EADS Astrium GmbH Page ii File: SW-LI-EAD-SY-0005_2_Supplier_DCG.doc

CONTENTS

1. INTRODUCTION ...........................................................................................................................................2

2. APPLICABLE DOCUMENTS ........................................................................................................................2

3. DOCUMENT REQUIREMENTS DESCRIPTIONS (DRD’S) .........................................................................3 3.1 Assembly, Integration & Verification ......................................................................................................3

3.1.1 Equipment Design, Development and Verification Plan, AV-1 ....................................................3 3.1.2 Equipment Verification Control Document, AV-3.........................................................................4 3.1.3 Equipment AIT Procedure and Test Report. AV-4 / AV-5............................................................5

3.2 Administration and Project Control.........................................................................................................6 3.2.1 Project Directory, MA-3 ................................................................................................................6 3.2.2 Subcontractor Project Management Plan, MA-4..........................................................................7 3.2.3 Progress Report, MA-5 ................................................................................................................8 3.2.4 Minutes of Meetings, MA-6 ..........................................................................................................9 3.2.5 Document Change Request (DCR)/Document Change Note (DCN), MA-7..............................10 3.2.6 Contract Change Notice (CCN), MA-8.......................................................................................11 3.2.7 Inventory Control List, MA-9.......................................................................................................12 3.2.8 Product Tree (PT), MA-13..........................................................................................................13 3.2.9 Work Breakdown Structure (WBS), MA-14................................................................................14 3.2.10 Work Package Description, MA-15 ..........................................................................................14 3.2.11 Master Schedule, MA-16..........................................................................................................15 3.2.12 Current Baseline Cost Plan, MA-17 .........................................................................................15 3.2.13 Action Item Report , MA-18......................................................................................................16

3.3 Engineering Documents .......................................................................................................................17 3.3.1 Calibration and Characterisation Plan, TE-1..............................................................................17 3.3.2 Design Description, TE-2 ...........................................................................................................17 3.3.3 Technical Notes (Trade-offs), TE-3............................................................................................18 3.3.4 Equipment / Instrument ICD, TE-4.............................................................................................18 3.3.5 User Manual incl. Design Description , TE-11 ...........................................................................19 3.3.6 Instrument Level 1b Algorithms Definition, TE-12 .....................................................................23 3.3.7 Instrument Performance Simulator Definition, Description and User Manual, TE-13................24 3.3.8 Equipment Budgets , TE-14.......................................................................................................25 3.3.9 Equipment Drawings incl. Geometrical Drawings, TE-15 ..........................................................26


Issue: 2



© EADS Astrium GmbH Page iii File: SW-LI-EAD-SY-0005_2_Supplier_DCG.doc

3.3.10 GSE Operations/Users Manuals, TE-16 ..................................................................................27 3.3.11 Instrument Calibration and Characterisation Data Base, TE-17..............................................28 3.3.12 S/W Development Plan, SW-3.................................................................................................29 3.3.13 Analysis, various PA-x and TE-x..............................................................................................30

3.4 Product Assurance Documents............................................................................................................31 3.4.1 Product Assurance & Safety Plan, PA-1....................................................................................31 3.4.2 Critical Item List (CIL), PA-5.......................................................................................................32 3.4.3 Parts Approval Document (PAD), PA-6 .....................................................................................33 3.4.4 Parts Evaluation Programme , PA-7 ..........................................................................................33 3.4.5 Destructive Physical Analysis (DPA) Report , PA-8 .................................................................34 3.4.6 Manufacturing and Inspection Flow Chart , PA-9 ......................................................................34 3.4.7 Declared Component List (DCL), as designed, PA-10 ..............................................................35 3.4.8 Declared Component List (DCL), as built, PA-11 ......................................................................35 3.4.9 Mechanical Parts, Material & Process List (PMP) , as-designed, PA-12 ..................................36 3.4.10 Mechanical Parts, Material & Process List (PMP) , as-built, PA-13.........................................36 3.4.11 Configured Item Data List (CIDL), PA-14.................................................................................37 3.4.12 As-Built Configuration Status List (ABCL), PA-15 ...................................................................38 3.4.13 Request for Deviation / Waiver, RFD / RFW, PA-16 / PA-17 ..................................................39 3.4.14 Non-Conformance Report (NCR), PA-18.................................................................................39 3.4.15 Failure Mode Effect Criticality Analysis , FMECA, PA-19 ........................................................40 3.4.16 Worst Case Analysis (WCA), PA-21 ........................................................................................41 3.4.17 Reliability Analysis, PA-22 .......................................................................................................41 3.4.18 Derating Analysis, PA-23 .........................................................................................................42 3.4.19 Safety Analysis, PA-24.............................................................................................................43 3.4.20 Failure Analysis Report, PA-25................................................................................................43 3.4.21 Radiation Analysis, PA-26........................................................................................................44 3.4.22 ATOX Analysis, PA-27.............................................................................................................45 3.4.23 Contamination Control Plan, PA-29 .........................................................................................46 3.4.24 Packing, Handling and Storage Procedure, PA-30..................................................................47 3.4.25 Equipment Log Book, PA-31....................................................................................................48 3.4.26 End Item Data Package (EIDP), PA-32 ...................................................................................49


Issue: 2



© EADS Astrium GmbH Page iv File: SW-LI-EAD-SY-0005_2_Supplier_DCG.doc

INTENTIONALLY BLANK


Issue: 2



© EADS Astrium GmbH Page 2 File: SW-LI-EAD-SY-0005_2_Supplier_DCG.doc

1. INTRODUCTION

The objective of the document is to define the contents of the required documentation to be established or updated during Phase B, advanced C/D, C/D, E1 (as applicable) of the SWARM programme.

The descriptions of deliverable documents as specified in this document shall be considered as being mandatory if not agreed differently with EADS Astrium. Simplifications due to re-use of available documents or equipment or reasonable combination of documents may be proposed to EADS Astrium.

2. APPLICABLE DOCUMENTS

AD Title Doc-No

AD 1 SWARM Generic Statement of Work for Equipment SW-SW-EAD-SY-0003

AD 2 Equipment Specific Statement of Work (as of contract)

Note:

The Document Requirements List (DRL) is integral part of AD 2.


Issue: 2




3. DOCUMENT REQUIREMENTS DESCRIPTIONS (DRD’S)

3.1 Assembly, Integration & Verification

3.1.1 Equipment Design, Development and Verification Plan, AV-1 PURPOSE OF DOCUMENT

To define the overall logic and planning for the design, development and verification of the equipment

CONTENTS

The Subcontractor shall establish and maintain a Design, Development and Verification Plan.

The DD&V Plan shall cover the analysis, design, manufacturing, assembly, integration, verification, operations and product assurance details.

The DD & V Plan shall include:

• system definition • equipment design and development flow, model philosophy • qualification and acceptance philosophy • description of equipment 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 equipment 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

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


Issue: 2




3.1.2 Equipment Verification Control Document, AV-3 ESA DRL: D-AV9 PURPOSE OF DOCUMENT The Verification Control Document lists the 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.

It shall enable an overview on the achieved equipment verification in front of the applicable specifications.

CONTENTS The contents of this document shall be in accordance with Annex D of the ECSS-E-10-02A The document shall include as a minimum the items listed hereafter:

• Reference to the particular Requirement to be verified

- Document/Specification (No, Title, Issue, Date)

- No of Requirement with short title

or

- No of Paragraph, identification of subject (key-word)

• Verification Method/Level/Model or target review

• trace to lower level spec where applicable

• Reference to close-out documentation

• Close-out status

• Reference to NCR/RFW as applicable

The VCD is required for all requirements made applicable, including the approved ICD´s.

Example for Equipment VCD table (pre-defined format can be provided by EADS Astrium)


Issue: 2




3.1.3 Equipment AIT Procedure and Test Report. AV-4 / AV-5 PURPOSE OF DOCUMENT To establish the procedures used in individual development, qualification and acceptance tests as foreseen in the respective Test Plan for 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.

The test report shall present the results of individual tests

CONTENTS • complete reference to the applicable test procedure • summary of test results and conclusion, • filled-in as-run-test-procedure and/or computer printout • evaluation of test results, emphasizing significant events and problems encountered • a list of all non-conformances generated during the test • a list of deviations from the applicable test procedure and the sign-off sheets


Issue: 2




3.2 Administration and Project Control

3.2.1 Project Directory, MA-3

PURPOSE OF DOCUMENT To facilitate communications among EADS Astrium and Sub-Contractors. CONTENTS The Sub-Contractor shall generate and maintain a Project Directory with the following information as a minimum:

• Company name

• Company location

• Company postal address

• Company phone, fax and telex numbers

• Key personnel with their:

- Responsibility

- Name

- Department

- Phone extension

- Electronic mail ID (user ID, network address, network name)

Note: The lower tier contractors shall prepare inputs to this directory


Issue: 2




3.2.2 Subcontractor Project Management Plan, MA-4

Purpose:

To define the management requirements for the work to be performed under the contract and to define the procedures to be applied by the Sub-Contractor to ensure that the objectives of the Swarm programme are accomplished within the prescribed time schedule at minimum risk and cost. To define the subcontractor management, subcontractor organisation, project control and planning

The document shall reflect the following items in the contents list:

• basic project management requirements

• Industrial Organisation and Company Project Structure

• Responsible Officers and Key Personnel

• project management procedures, including:

o Information Exchange and Language

o Project Breakdown Structures (WBS,..)

o Project planning, schedule control and reporting

o Cost control and reporting

o Change control

o Configuration and Documentation control incl.:

electronic means of correspondence, filing, document creation

Access to information by EADS Astrium and ESA

o Progress reporting

o Inventory control and reporting


Issue: 2




3.2.3 Progress Report, MA-5 Purpose:

The progress report shall provide information on management level, reflecting the progress during the reporting period, for analysis and discussion. The progress report shall include the schedule report.

CONTENTS

• Overall assessment, including:

o Project Manager’s assessment

o Key problem list

o Open action items requiring special attention

o Risk assessment

• Technical Status

• Product Assurance Status

• Schedule Status

• Cost, Performance and Financial Status

• Contractual Aspects

Specific annexes shall be included, or referred to, as follows:

• - Schedule Reporting

• - Action Item Status list

• - RFD / RFW list

• - NCR list

• - DCN status list

• - CCN status list


Issue: 2




3.2.4 Minutes of Meetings, MA-6 PURPOSE OF DOCUMENT To summarize all action items, decisions, recommendations and statements made during Swarm project meetings. The Minutes of Meetings shall enable the correct understanding by non-participants to the meeting, of the agreements reached. Any matter having contractual impacts shall be highlighted and reported to the Project Management, and shall be subject to formal approval, using the Contract Change Procedures. CONTENTS The minutes shall contain as a minimum:

• a cover sheet, recording the subject of the meeting, the meeting place and date, the agenda reference and the list of participants;

• minutes itself including a brief summary of the discussion on major problem areas • summary of the overdue actions • action items initiation sheet, covering action item title and description, due date, originator and

actionee; • any annex relevant to the subject meeting.


Issue: 2




3.2.5 Document Change Request (DCR)/Document Change Note (DCN), MA-7 PURPOSE OF DOCUMENT Ensures formal mechanism for change control of documents. CONTENTS 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 DCN’s shall be subject to the EADS Astrium approval, if requirements to EADS Astrium are effected. Documents shall be updated by a new issue. Note: the DCN is the final approved version of the DCR.


Issue: 2




3.2.6 Contract Change Notice (CCN), MA-8

PURPOSE OF DOCUMENT As defined in the Swarm Management Requirements for Sub-Contractors, para 7 CONTENTS The Contract Change Notice (CCN) shall be submitted on a CCN form.

The documentation and information to be supplied with the CCN shall include, as a minimum, the following::

Justification of the change.

• A detailed technical description of the change, and its implications and consequences on equipment performances. This shall be accompanied by the proposed 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 and PSS-A8). All changes shall be submitted as Firm Fixed Price in Euros, in line with the price type of the Contract concerned.

• An update of the Geographical Distribution of Work

• Proposed payments plan(s) for the change, including those of the Subcontractors (if any).

• 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

When submitting the complete CCN to EADS Astrium, it shall be signed by the Contractor’s Project Manager and Contracts Officer.


Issue: 2




3.2.7 Inventory Control List, MA-9 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 EADS Astrium/ESA shall be subject to Inventory Control

CONTENTS The Contractor shall establish a database (called Inventory Record) of all Inventory Items for the whole project. The Inventory Record shall be presented to the EADS Astrium 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

For the listing the following rules shall be applied:

• A unique Inventory Control Number shall be assigned to each item.

• quantity;

• item description;

• manufacturer model number;

• manufacturer serial number;

• acquisition date;

• acquisition value (in national currency and Euro at year of acquisition);

• classification (1 or 2);

• physical location (sufficient detail to facilitate inspection of items);

The Inventory Record shall be updated on a continuous basis and forwarded to the customer.


Issue: 2




3.2.8 Product Tree (PT), MA-13 Purpose:

The Product Tree (CI Tree) establishes the basis for a consistent W.B.S. (see ECSS-M40B, annex L)

CONTENTS The Product Tree (PT) shall include all products down to the deliverable end items. The Product Trees of Subcontractors will be incorporated in the Contractor’s PT. The Contractor shall maintain the Product Tree under configuration control.

The Product Tree shall reference the following items:

• Level

• Product Tree ID

• Description and Abreviation

• Type of Product (H/W, S/W, …)

• Model relation


Issue: 2




3.2.9 Work Breakdown Structure (WBS), MA-14

ESA DRL: D-PM7

PURPOSE OF DOCUMENT To break down the overall work into individual Work Packages (WP) CONTENTS As defined in SW-RS-EAD-SY-0003 Para 3.3.

3.2.10 Work Package Description, MA-15

ESA DRL: D-PM34

PURPOSE OF DOCUMENT To identify the exact content, time scale, purpose and interrelationship of each task at the lowest level of the WBS. CONTENTS As defined in SW-RS-EAD-SY-0003 Para 3.3.


Issue: 2




3.2.11 Master Schedule, MA-16 ESA DRL: D-PM18 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 As defined in SW-RS-EAD-SY-0003 Para 4.

3.2.12 Current Baseline Cost Plan, MA-17

Purpose:

Generation of the payment prediction plan

Contents:

The current baseline cost plan (CBCP) shall contain:

• The payment milestones

• The price becoming due at each payment milestone

• The company requiring payment

• The national code of the company

All agreed changes of the cost plan (e.g. CCNs) shall be incorporated in the CBCP.


Issue: 2




3.2.13 Action Item Report , MA-18 ESA DRL: D-PM43 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

As defined in SW-RS-EAD-SY-0003 Para 2.3.3.

The Action Items shall be reported as part of the project report 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 of :

o new actions since last report o all open actions o all overdue actions o all actions completed since last report with closing reference and closing date.


Issue: 2




3.3 Engineering Documents

3.3.1 Calibration and Characterisation Plan, TE-1

PURPOSE OF DOCUMENT To define all Swarm equipment characterization/calibration activities, both on-ground and inorbit. CONTENTS Plan of all characterization/calibration activities, including:

• characterization/calibration approach • characterization/calibration definition/methods • on-ground characterization/calibration activities • in-orbit characterization/calibration activities • characterization/calibration activities flow and planning • definition of characterization/calibration facilities required. • Error budget definition and combination • Calibration / characterisation expected accuracies (for each parameter) • Required frequency of characterization/calibration • Operational constraints (in-orbit)

3.3.2 Design Description, TE-2

Design Description shall preferably be part of User Manual (para 3.3.1).

Note 1: User Manual and Design Description may be split / delivered in two documents ( not the preferred solution)

Note 2: Information given in the ICD shall not be repeated in the User Manual and/or Design Description, but referenced only.


Issue: 2




3.3.3 Technical Notes (Trade-offs), TE-3

Purpose:

To trade-off and provide recommendations and supporting data for the selection of alternate design solution

Summary of Contents/Preparation Information:

• They shall always indicate the design standard(s) being analysed, the relevant source requirements, the design and implementation aspects being addressed, and conclusions or consequences to be taken where applicable;

• They shall reference the analysis and/or design resolutions which have been used as supporting data;

• Preparation format is free to be chosen by the Subcontractor.

3.3.4 Equipment / Instrument ICD, TE-4 PURPOSE OF DOCUMENT To define the equipment external interfaces in relevant interface control documents (ICD’s) CONTENTS

The Subcontractor shall establish and maintain an Interface Control Document (ICD) for the applied equipment to be supplied to and approved by the Customer.

The ICD shall cover all external interface aspects(Electrical/Mechanical/Thermal/Optical), including physical, functional and performance, as:

• mechanical interfaces (including size, mass properties, dynamic properties, disturbance exported, deployment, field of view, physical envelope, local reference, mounting/accommodation, AIV 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)

• electrical interfaces (including power supply, avionics, timings, housekeeping interface) • Operational constraints

Connectors at interfaces shall be clearly identified in the mechanical drawing. This applies to equipment connectors as well as to interface brackets connectors.

Once approved, any change to such an ICD document shall be raised via Document Change Request procedure (DCR).


Issue: 2




3.3.5 User Manual incl. Design Description , TE-11

ESA DRL: D-ES6

PURPOSE OF DOCUMENT To provide visibility into the design and the degree of compliance with the SWARM requirements.

To give instructions how to operate the equipment in nominal and contingency cases.

CONTENTS

The document is valid for HW equipment with possibly embedded Software and stand-alone Software and shall have the following contents:

1. Short Users Manual

This section shall contain the answers to a questionnaire provided by the customer.

2. Unit Design Summary

An overview on the equipment at the level of detail such that the information presented in the sub-sequent sections can be understood in the overall context of the unit

• The overall functions of the equipment and its functional objectives

• The definition of its operational modes (nominal and contingency) during the mission

• Description of any equipment level management functions, fault management concept and redundancy provisions.

• Description of failures, how they are identified and the necessary recovery actions (including time criticality in each mode)

• A summary description of the equipment and on-board software including the functions which each supports

• Functional block diagrams and a diagram showing the source of telemetry outputs and the sink of tele-command inputs

• Interfaces (power, data, control, mechanical, thermal, optical)

External interfaces

Internal interfaces

• Budgets (power, data load, sizings, mass, error and alignment, timing); nominal/peak/worst-case values where applicable

3. Detailed equipment Design Definition

• Detailed design description including configuration block diagrams, functional diagrams, logic and circuit diagrams including references to TM/TC definitions

• Physical characteristics including location and connections to the satellite structure, axes definition and alignment where relevant, dimensions and mass properties


Issue: 2




• Principle of operation of the unit

4. Equipment Software (where applicable)

• Description of software design

Description of the organization of the unit software and the physical mapping of software into unit hardware

• Unit software

Detailed description of each component of the unit software. This shall include its functions including software task definitions (purpose, actions performed, inputs and outputs for each task, task control and scheduling information, synchronisation), component routines, I/O interfaces, timing/datation and performance characteristics, flowcharts and details of any operational constraints. Stress conditions w.r.t. data load and performance shall be outlined

• Application process service software

A short description of the services implemented making cross-reference to the SWARM Packet Utilization Standard

For each service a summary of all telemetry and tele-command structures shall be provided together with the circumstances under which they are generated, the generation frequency, content and interpretation

• Memory Map

For each memory block, a map shall be provided showing RAM and ROM address areas allocated for the program code and data, buffer space and working parameters. It shall be clearly stated which memory areas are accessible for patch an/or dump operations. For memory areas (not used by the application) shall be identified for possible usage during patch/dump testing.

5. Unit Performance

• Definition of all relevant unit performance characteristics

• Definition of expected performance degradation as a function of lifetime and identification of the resultant impact in terms of modified operational requirements

6. Unit Constraints

• Summary of all unit operational constraints

• Mode related constraints

• Constraints resulting from stress conditions (i.e. for data load and performance) 7. Unit TM/TC List

• A list of all unit housekeeping telemetry parameters. For each parameter it shall include a function description with validity conditions, telecommand relationship and all technical information necessary for using it

• A list of all unit telecommands. For each telecommand it shall include a functional description with utilization conditions and execution verification in telemetry. For each telecommand the execution run-time shall be outlined

• This data may be included in the electronic TM/TC delivery towards the satellite reference data base ( see Deliverable Item List)

8. Unit Operations


Issue: 2




• Unit Modes

Definitions of all nominal and contingency modes of the unit. This shall include for each mode a detailed description including :

a mode transition diagram

their purpose

pre-requisites

resource utilization

definition of the associated unit configurations for each mode, inclunding configurations of H/W elements (switches, relays) and configurations of software function

ground monitoring requirements

Identification of the allowable mode transitions and any operational constraints

Identification of parameters and parameter locations (e.g. internal status, limits) to be supervised by the OBC S/W in each mode.

• Nominal operation procedures

Definition of an operational procedure for each nominal mode transition identified above, for any unit configuration/parameters settings and calibration/characterization procedures. For each procedure the following shall be provided

An introduction providing the purpose of the procedure and the circumstances when it is applicable

The body of the procedure which shall be structured according to distinct operational steps. Each step may include:

pre-requisites for the start of the step, where applicable tele-commands to be sent (referencing telecommands from the provided tele-

command list) telemetry to be monitored to verify correct execution of the steps(referencing

telemetry from the provided telemetry list) recovery actions interrelationships between steps (e.g. conditional branching within the procedure,

timing requirements or constraints, hold and check points) conditions for completion of the step

• Unit failure analysis

Identification of potential unit failures by means of systematic failure analysis

Identification of the methods by which the ground segment can identify failure conditions from analysis of the telemetry data and isolate the source of the failure

Note: Reference may be made to FMECA, if up-to-date at equipment delivery and sufficiently detailed, i.e. TM parameters identifying a specific failure given with its designation.

• Contingency Procedures

Definition of the recovery procedure for each failure case identified above. This may utilize a nominal operational procedure already identified above, but more likely it requires the definition of a new procedure. The same information shall be provided for recovery as for the nominal operational procedures above. For some failures, or groups of failures, the recovery method can be mode, mission phase dependent, in which case separate procedures shall be defined


Issue: 2




8. Unit Science Data Definition

• Definition of the unit science output data, circumstance of generation, format, content and data rate, for each operational mode of the unit

• Definition of the processing performed on the sensor data, the algorithms used, selection or rejection criteria

Definition of the required ground processing of the payload data


Issue: 2




3.3.6 Instrument Level 1b Algorithms Definition, TE-12 PURPOSE OF DOCUMENT To provide a description of the Instrument Level 1B Processing algorithms to be used for the on ground Instrument science data processing. CONTENTS

• Algorithm overview. • Use of Calibration data base data • ISP / Raw data interface. • Instrument performance / measurements Results • Instrument Level 1b data definition


Issue: 2




3.3.7 Instrument Performance Simulator Definition, Description and User Manual, TE-13 PURPOSE OF DOCUMENT To describe the Instrument Performance Simulator Design and its operational, functional and performance characteristics incl. associated User Manual of the SW involved. CONTENTS

Part A) Simulator Definition

- Design & Simulator Principles - Simulation of the instrument and mathematical basis - Environmental model - Treatment of errors - Calculation of output quantities / Algorithm

Part B) Simulator Description

- Implementation approach - Presentation of the Instrument model incl.

- Input parameters - Functionality, performance, - Output parameters

- Description of the software supporting the application.

Part C) User Manual

- Overview of the software - Overview of the simulator performance - Description for installation and operation of the Software incl. special operational constraints to be

considered

Part D) Test Data

- Test data as provided in support of the SW


Issue: 2




3.3.8 Equipment Budgets , TE-14 ESA DRL: D-SA6 PURPOSE OF DOCUMENT To provide a comprehensive source of reference for all Swarm “current” satellite system budgets. CONTENTS

To describe resource management controls, to document resource requirements, allocations, traceability


The Subcontractor shall provide a two monthly Budget Report to EADS Astrium which may be linked to the Progress Report.

This resource budget report shall be organised traceable to the Product Tree and shall include the status of the following resources:

• Mass Budget

• Mass Properties

• Power Budget (if applicable)

• Processor Budget (if applicable)

• Memory Budget (if applicable)

• Interface Budgets (if applicable)

The report shall show the current margins/deficits with respect to the requirements and in the case of subsystem report the originating requirement and its apportionment down through the system.


Issue: 2




3.3.9 Equipment Drawings incl. Geometrical Drawings, TE-15 ESA DRL: (D-SA17 / D-SA18 / D-SA19 / D-SA20 / D-SA21) PURPOSE OF DOCUMENT To provide overall drawings of the Swarm equipments and assemblies. CONTENTS The drawings shall cover as a minimum: Mechanical:

• internal and external top assembly drawings, in stowed and deployed configurations • overall mechanical drawings (indicating e.g. internal structural interfaces, equipment attachment

points, lifting points etc.) • main structural characteristics : size, attachment, material and thickness, etc • panel lay-outs (indicating unit/equipment footprints, keep-out zones, through-holes etc.) • harness routing and connector bracket allocation drawings. • thermal and AOCS piping routing drawings.

Electrical: • overall block diagram • system functional diagram • TM/TC diagram • power diagrams • system wiring diagrams • grounding and isolation diagrams

Thermal • 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.

Unit Circuit Diagrams • The drawings shall be provided of the equipment down to PCB level. ASIC/Hybrid design and lay-

out drawings are not required, however shall be available for consultation the at manufacturer’s premises.


Issue: 2




3.3.10 GSE Operations/Users Manuals, TE-16

Purpose:

The document covers the use of the ground support equipment in connection with satellite AIT operations. Aspects of implementation are be covered only on the extent necessary for EADS Astrium understanding and can be cross referenced to other documents


The manual shall provide all information needed, to understand the operation of the equipment. All information needed to make efficient use of the whole spectrum of services/functions shall be provided. Drawings, diagrams and schematics shall be used to enhance understanding.

The content shall cover at least:

• Background information • equipment configuration • design description as relevant for equipment operation • maintenance • operations constraints, e.g.

- environment, - safety, - etc.

Operating instructions / procedures

• equipment initialisation • nominal tasks • cautions, pre-cautions, safe operation • task limitations • exceptional tasks and anomaly recovery • maintenance tasks

This part of the document shall be structured according to - and cover the full scope of – the applicable requirements specification.

Operations Support Information:

• List of malfunctions, errors, error messages with recovery instructions • Manuals, Instructions of included lower level equipment (e.g. for COTE) • Commands, control code, instructions libraries (as applicable)


Issue: 2




3.3.11 Instrument Calibration and Characterisation Data Base, TE-17

PURPOSE OF DOCUMENT

To provide all information pertinent to the use of the calibration / characterisation parameters to be injected within the ground processing algorithms.

CONTENTS

A set of files providing for each calibration and characterisation parameter

• instrument configuration identifier • environmental conditions • reference to the test set-up configuration • accuracy • parameter value(s)

This shall include a document describing file content and format (how to read it)


Issue: 2




3.3.12 S/W Development Plan, SW-3 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 To provide a list of all S/W documents to be delivered, together with a brief description of the purpose and contents of each document, including:

• 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 Plan • S/W Integration Procedures • S/W Configuration Status List • S/W Users Manual • H/W-S/W Integration Docs • source code listing • Selection of one high-level programming language. • specification of all S/W reviews and major S/W milestones.


Issue: 2




3.3.13 Analysis, various PA-x and TE-x The description below covers a generic set-up of an analysis to be performed on Swarm. Scope and contents of some analyses may be individually defined within this DCG or in other applicable documents (e.g. PA specification). PURPOSE OF DOCUMENT

To report the results of an equipment analysis and to support the verification of compliance with related requirements.

CONTENTS

The document shall report the results of a specific analysis of the equipment. The level of detail shall be sufficient to demonstrate that all requirements are fulfilled. Full performance of the equipment shall be demonstrated for the specified lifetime. The report shall also include prediction uncertainties, considering modelling errors and realistic variations of all parameters, sensibly affecting the performance.

The analysis shall at least cover the following subjects:

• Listing of the requirements of concern

• Relevant assumptions

• Boundary conditions

• Design data on which the analysis is based

• Description of analysis tools used

• Descriptions of model(s) developed

• Results synthesis and assessment, including assessment on limitations to the data validity


Issue: 2




3.4 Product Assurance Documents

3.4.1 Product Assurance & Safety Plan, PA-1

PURPOSE OF DOCUMENT

Provides the policies and objectives for organisation, implementation and control of the Swarm product assurance programme.

CONTENTS

The Plan shall describe as a minimum the following items:

• Product Assurance & Safety organisation and management - The organisational structure established for the project’s product assurance programme shall be described, include the interfaces with supporting groups, services and facilities. The product assurance and safety manager and senior personnel of the product assurance group shall be named and their authority and position within the project technical management structure stated. Organisational charts and exhibits describing organisation elements and system flow shall be included. A statement of the manpower complement needed for the performance of the product assurance programme shall be included, showing the manpower required per period / project phase.

• Tasks and schedule – The PA&S tasks to be undertaken shall be described together with the relationship to these tasks to the overall programme milestones. The relationship of activities in each PA&S discipline to those of all other PA&S disciplines shall also be defined.

• Deliverables – The documents to be delivered by the contractor in the PA/S area shall be identified.

• Documentation – In accordance with the requirements of the PA & Safety Requirements Document, the contractor shall define or make reference to the product assurance design rules, standards, practices, methods (including analyses), procedures, and data formats that shall be used in the implementation and execution of each PA&S discipline. Details shall be provided of any lists, specifications reports and records, which are to be prepared and maintained.

• Policy and objectives for the PA tasks including: Quality Assurance Personnel Training and certification Dependability (Reliability, Availability & Maintainability) Assurance Safety Assurance EEE Components Control Parts, Materials and Processes Assurance Cleanliness Assurance Software PA Assurance

• Statement of the applicability and compliance to each paragraph of the Swarm PA requirements


Issue: 2




3.4.2 Critical Item List (CIL), PA-5

PURPOSE OF DOCUMENT To identify parts suitability for the applicable radiation environment and identify component radiation testing.

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 • Items requiring precautions to avoid contamination • Long Lead Items • Radiation sensitive elements not meeting the radiation requirements • New industrial processes, technologies (not qualified or not standard)

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.


Issue: 2




3.4.3 Parts Approval Document (PAD), PA-6

ESA DRL: D-PA19

PURPOSE OF DOCUMENT Collect information about parts and prepare approval. CONTENTS As per ECSS-Q-60A clause 3.3.2 & Annex A

3.4.4 Parts Evaluation Programme , PA-7

ESA DRL: D-PA25

PURPOSE OF DOCUMENT

To document the evaluation and validation of Parts, Materials and Processes that requires further data in order todemonstrate meeting mission requirements.

CONTENTS

As defined in ECSS-Q-70A clause 3.1, 4.1, 5.1


Issue: 2




3.4.5 Destructive Physical Analysis (DPA) Report , PA-8

ESA DRL: D-PA22

PURPOSE OF DOCUMENT

DPA is one element to evaluate EEE parts quality and techniques, and to investigate EEE parts failure mechanism.

The requirements for when and how to perform DPA are given in the Swarm PA requirements for subcontractors SW-RS-EAD-PA-0001

CONTENTS

The report shall include the results of inspections, tests and analysis performed on a sample of components.

3.4.6 Manufacturing and Inspection Flow Chart , PA-9

ESA DRL: D-PA27

PURPOSE OF DOCUMENT

To plan and control MIP/KIP events and their implementation

CONTENTS

• MIP/KIP dates shall be defined in relation with the manufacturing, assembly and test flow charts.

• The MIP/KIP dates shall be updated with the regular schedule control reporting. • A confirmation latest 5 days before the event has to be given via electronic mail.


Issue: 2




3.4.7 Declared Component List (DCL), as designed, PA-10

PURPOSE OF DOCUMENT To identify all components types needed for the current design. CONTENTS As defined in SW-RS-EAD-PA-0001 annex 2.

3.4.8 Declared Component List (DCL), as built, PA-11

PURPOSE OF DOCUMENT To identify all components types reflecting the as-built design.. CONTENTS As defined in SW-RS-EAD-PA-0001 annex 2.


Issue: 2




3.4.9 Mechanical Parts, Material & Process List (PMP) , as-designed, PA-12

ESA DRL: D-PA25

PURPOSE OF DOCUMENT Mechanical Parts:

To provide a complete list of all mechanical parts used for manufacturing of qualification or flight hardware with all relevant information and approval status reflecting as-designed status.

Materials:

To provide a complete list of all materials used for manufacturing of qualification or flight hardware with all relevant information and approval status reflecting as-designed status.

Processes:

To provide a complete list of all processes used for manufacturing of qualification or flight hardware with all relevant information and approval status reflecting as-designed status.

CONTENTS As defined in SW-RS-EAD-PA-0001 annex 3.

3.4.10 Mechanical Parts, Material & Process List (PMP) , as-built, PA-13

ESA DRL: D-PA25

PURPOSE OF DOCUMENT See PA-12, but reflecting as-built status.

CONTENTS See PA-12, but reflecting as-built status.


Issue: 2




3.4.11 Configured Item Data List (CIDL), PA-14 PURPOSE OF DOCUMENT Provide listing of all documents and their applicable status defining the configuration of an Equipement, according to ECSS-M-40B, Annex D CONTENTS The CIDL shall contain for each configuration item the following as a minimum:

• Cover sheets and scope. indicating current configuration status (such as "as designed", "as built"), • Customer controlled documentation, including

• customer specifications and ICDs, and • support specifications.

• Engineering or design documentation, including configuration baseline documents defining the configuration in terms of requirements, design and verification, with their evolution status .

• verification plans demonstrating compatibility with specified requirements, (verification matrix)

• special instructions or procedures (e.g. transportation. integration, and handling), • declared PMP lists, • lower level specifications, • lower level ICDs, • drawings and associated lists, • Circuit functional diagrams. • test specifications, • test procedures and plans • users manual or handbook.

• List of applicable changes not yet incorporated into the baselined documentation, and deviations (including approval status, directly related to the document (e.g. specification) to which the change belongs to) including deviations and waivers (NCRs and RFWs).

• CI breakdown including: • The reference of the configuration items:

- CI number - CI name. - CI level. - Company's code (supplier and buyer)

• indentured breakdown by part numbers starting from the part number associated with the CI down to the lowest level of composition;

• quantity of each part number used on the next higher assembly; • issue status of the drawings and associated lists applicable to each part number.

Each entry in the CIDL shall relate to the applicable model(s) of the CI and be defined by its document number, title, issue and release date.


Issue: 2




3.4.12 As-Built Configuration Status List (ABCL), PA-15 PURPOSE OF DOCUMENT Provide listing of all documents and their applicable status defining the Configuration Item or Product, according to ECSS-M-40B, Annex E

The “As-designed / As-built” reconciliation provides the means for verifying that the achieved built status of a CI, complies with the approved design documentation.

CONTENTS

The as-built configuration list shall list all discrepancies between the as-designed configuration documented in the configuration item data list and the as-built configurationdocumented bynonconformance reports or waivers.

The ABCL configuration item breakdown section, obtained from the equivalent configuration item data list section, shall be completed by adding the following information:

• serial number identification; • lot or batch number identification; • reference(s) of applicable nonconformance report(s) or request for waiver(s).


Issue: 2




3.4.13 Request for Deviation / Waiver, RFD / RFW, PA-16 / PA-17 ESA DRL: D-PA7 PURPOSE OF DOCUMENT To process waivers/deviations against Swarm requirements. To provide a summary report of the current status of the waivers raised against Swarm requirements. This report shall be generated from the overall waiver/deviation database, according to ECSS-M-40B, Annex J / Annex K respectively. CONTENTS Individual waivers/deviations shall be raised. 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.

3.4.14 Non-Conformance Report (NCR), PA-18 PURPOSE OF DOCUMENT To provide a summary report of the current status of the NCRs raised, to aid the overall tracking of the control for NCR closeout.

CONTENTS

Individual NCR reports shall be raised and processed in accordance with the NCR control system established as defined in ECSS-Q-20-09B.

Periodic reporting of the overall NCR status shall be provided. The report shall identify for each NCR (minor and major), the relevant identification (number, issue, title, etc), opening / closure dates, classification, description & action item tracking/ closeout activities etc.


Issue: 2




3.4.15 Failure Mode Effect Criticality Analysis , FMECA, PA-19 ESA DRL. D-PA11 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 ECSS-Q-30-02A . 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:

- Potential damage resulting to H/W from incorrect methods of prevention of these harmful effects

- Prior fault detection methods applied to the S/W functions. - Methods of controlling/containing the harmful effects of faults. - Recovery/rollback method applied

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


Issue: 2




3.4.16 Worst Case Analysis (WCA), PA-21

PURPOSE OF DOCUMENT

Worst case circuit performance analysis (WCCPA) (see ECSS-Q-30-01) shall be performed on electronic/electrical equipment to demonstrate that it performs within specification despite particular variations in its constituent part parameters and the imposed environment. WCA shall be accomplished at equipment level.

CONTENTS

See ECSS-Q-30-01A

Worst case Analysis will be performed as required on a case-by-case basis for critical design applications (e.g. at temperature extremes, voltage, current, frequency limits,etc.)

3.4.17 Reliability Analysis, PA-22

ESA DRL: D-PA10

PURPOSE OF DOCUMENT

To provide an overall Swarm Satellite system Reliability estimate based on reliability estimates for all satellite sub-systems and instruments.

CONTENTS

The overall Swarm reliability requirement shall be apportioned to the satellite lower level specifications.

Satellite sub-system/instrument reliability figures leading to an overall satellite system reliability estimate with compliance to overall satellite system requirements

The report shall include:

• A description of the hypothesis used to build the reliability models • A description of the reliability model (e.g. block diagrams) • The list of quantitative data (together with their source) which are used in the predictions • The reliability results • The identification of the main contributors to the unreliability and recommendations on how to

reduce their impact. • The results of sensitivity analysis on the main parameters influencing the reliability results. • Conclusions


Issue: 2




3.4.18 Derating Analysis, PA-23

ESA DRL: D-PA35

PURPOSE OF DOCUMENT

To determine the level of stress applied to EEE parts in conformance to derating requirements of ECSS-Q-30-11A

CONTENTS

Each Parts Stress Analysis Report shall identify:

• Applicable design documentation • Applicable technical specifications. • Configuration status of all documentation

For each component used in the design list:

• Component identification • Performance requirements • Environment • Application stress including:

o Voltage o Current o Thermal o Mechanical o Stress cycles o Transient o Stresses o Safety factors applied to each parameter o Conformance to derating requirements of ECSS-Q-30-11A o Discussion of results o Recommendations


Issue: 2




3.4.19 Safety Analysis, PA-24

PURPOSE OF DOCUMENT

To ensure, that:

• Hazardous characteristics and functions with potentially hazardous failure effects are identified and progressively evaluated by iteratively performing systematic safety analyses

• The potential hazardous consequences associated with the equipment characteristics and functional failures are subjected to a hazard reduction sequence

• The risks that remain after the application of a hazard elimination and reduction process are progressively assessed and subjected to risk assessment

• The adequacy of the hazard and risk control measures applied are formally verified in order to support safety validation and risk acceptance

• Safety compliance is assessed by the project and safety approval obtained from the relevant authorities

CONTENTS

As required by SW-RS-EAD-PA-0001 § 6

3.4.20 Failure Analysis Report, PA-25

ESA DRL: D-PA32

PURPOSE OF DOCUMENT

Results of failure investigations to be performed as applicable, usually as part of NCR investigations

CONTENTS

As relevant to the analysis.


Issue: 2




3.4.21 Radiation Analysis, PA-26

PURPOSE OF DOCUMENT

To identify parts which are critical for the applicable radiation environment and to identify component radiation testing.

CONTENTS

The sub-contractors shall add this shielding (provided by SW-TN-EAD-SY-0017) to their equipment radiation model in order to demonstrate the compatibility of the parts with the radiation level induced by the Swarm mission.

For components identified as inadequate for the radiation environment, define the RVT to be performed. Identify the components, type of radiation testing, test facilities, methods and applicable radiation test levels to be tested.

The analysis report shall contain as minimum:

• Identification of TID & SEE sensitive components • Assessment of TID & SEE effects (including error rates) • Identification of protection measures for SEE sensitive parts (e.g. latch-up protections,

majority voting, error detection and correction circuitries, etc.) • Identification of protection measures for TID sensitive parts (e.g. spot shielding) • Summary of analysis results


Issue: 2




3.4.22 ATOX Analysis, PA-27

ESA DRL: D-PA24

PURPOSE OF DOCUMENT

To assess the effects of Atomic Oxygen (Atox) on the outer surfaces of the spacecraft, on the basis of the orbit parameters, mission duration and launch date and to demonstrate that the selected materials on the outer surfaces of the spacecraft (including appendages, solar panels, etc.) are adequate with respect to the Atox environment to fulfil the mission requested performance.

The Swarm Atox environment is provided in SW-TN-EAD-SY-0021

CONTENTS

• Identification of ATOX critical items • Analyse equipment performance degradation due to ATOX • Identify measures to protect surfaces against ATOX where necessary


Issue: 2




3.4.23 Contamination Control Plan, PA-29

ESA DRL: D-PA8

PURPOSE OF DOCUMENT

To define the methods, procedures and responsibilities in achieving and maintaining the cleanliness levels applicable to Swarm

CONTENTS

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

Equipment level Contamination Control Plan is only required for equipment containing contamination sensitive items.


Issue: 2




3.4.24 Packing, Handling and Storage Procedure, PA-30

PURPOSE OF DOCUMENT

To specify protection measures for flight, flight spare and GSE items against contamination, damage or degradation during transport, handling and storage.

CONTENTS

The procedure shall contain as minimum:

- Packing and unpacking guidelines - Identification of hazards - Thermal, humidity and mechanical (shock) constraints - Handling and Integration procedures - Description of required precautions - Identification of life limited items (if any) - Identification temporary installed items - Specific cleanliness requirements (e.g. for optics) - Conditions for storage

Requirements of ESA PSS-01-202 shall be considered.


Issue: 2




3.4.25 Equipment Log Book, PA-31

ESA DRL: D-PA13

PURPOSE OF DOCUMENT

To document major handlings and occurrences related to flight equipment during manufacturing and tests until delivery.

CONTENTS

Equipment logbooks shall be prepared and maintained according to the principles of ECSS-Q-20B § 8.10.2 for all equipment operations and tests performed.

Adequate instructions, such as shop travellers, shall direct the actual performance of manufacturing, assembly and integration operations and inspections, to ensure that the activities proceed in an orderly manner and according to the planned sequence, according to the principles of ECSS-Q-20B § 8.2.3

The logbooks shall contain historical, quality data and information which is significant for operation of the item, including non-conformances, deviations and open tasks.


Issue: 2




3.4.26 End Item Data Package (EIDP), PA-32 ESA DRL: D-PA28 PURPOSE OF DOCUMENT Document the as build baseline for acceptance CONTENTS The EIDP’s shall be prepared for the acceptance review of the deliverable items. One copy shall always accompany the HW / SW. The EIDP's are to be maintained and to be integrated into higher-level EIDP's during subsystem/system integration and testing. The contents shall include the following: A) References

• Cover page • Shipping documents

B) Generic Data

• ADP Number • Nomenclature • CI Number • Drawing Number or Identification Number • Serial Number • Contract Number

C) Detailed Contents: • Certificate of Conformance • As-built Configuration List, Reconciliation As-designed vs. As-built and variants between each

deliverable of the same type • RFD/RFW List (plus copies of the major ones) • Temporary Installation Record (e.g. remove-before-flight items) • Open/Deferred Works, Open Tests, Missing Items • Proof Load Certificate • Cleanliness Certificate • Integration, Operation and Maintenance Manual (including engineering drawings and

electrical/functional schematics) • Special Packaging, Handling and Shipping Procedures • Packing List (including loose items and spares) • Design and Verification Compliance Matrix • Acceptance Test Reports • Interface Control Documents • Logbook • DRB Minutes of Meeting • Critical Item List • CIDL • Qualification Status List • Non-conformance List (plus copies of the major ones) • Verification Control Document • Copies of Key Inspection (KIP) and MIP Reports • Photographs of all flight hardware down to board level.

Format:

Signed Document (Original) with flight H/W, PDF File on CD-ROM, paper copies to ESA and EADS Astrium each