Title: Generic Statement of Work for MWI RFA...

DOCUMENT TYPE (STATEMENT OF WORK) Reference: MOS-SOW-ADST-MWI-1000002084 Issue: 1.0

Date:24/09/2014

This document is Airbus Defence & Space SAS proprietary and should not be dispatched or the content disclosed without written authorization ● /88

Title: Generic Statement of Work for MWI RFA Equipment

NAME AND FUNCTION DATE SIGNATURE

Prepared by

Franck BAYLE

MWI RFA Industrial Manager

12/11/14

Verified by

Approved by

Robert OSSWALD

MWI RFA PA Manager

12/11/14

Authorized by Christian TABART

MWI RFA Project Manager 12/11/14

Application

authorized by

DOCUMENT TYPE (STATEMENT OF WORK)

Reference: MOS-SOW-ADST-MWI-1000002084 Issue: 1.0

Date:24/09/2014


Summary

This statement of work defines the Generic programme of work for the design, development,

manufacturing, verification, and delivery of MWI RFA equipment for the Metop SG program.



Date:24/09/2014


Document change log

ISSUE/

REVISION DATE MODIFICATION NB

MODIFIED

PAGES OBSERVATIONS

01/00 24/09/2014 First Issue



Date:24/09/2014


Table of contents

1 INTRODUCTION .............................................................................................................................. 7

1.1 Scope of the document ............................................................................................................... 7

1.2 Requirements presentation ......................................................................................................... 7

2 References ...................................................................................................................................... 8

2.1 Applicable documents ................................................................................................................. 8

2.2 Reference documents ................................................................................................................. 9

2.3 Abbreviations ............................................................................................................................. 10

3 UNIT DEVELOPMENT APPROACH AND DELIVERABLES ....................................................... 13

3.1 Development Logic & Models Philosophy ................................................................................. 13

3.1.1 Equipment Category: ................................................................................................................... 13

3.1.2 Existing off-the-shelf or recurring unit (cat. A or B) ..................................................................... 13

3.1.3 New or modified unit (cat. C or D) .............................................................................................. 14

3.2 Model Description ...................................................................................................................... 15

3.2.1 Prototype or Bread Board (BB) .................................................................................................... 15

3.2.2 Engineering Model (EM)............................................................................................................. 15

3.2.3 Engineering and Qualification Model (EQM) ............................................................................. 16

3.2.4 Structural and Thermal model (STM) ......................................................................................... 16

3.2.5 Proto Flight Model (PFM) .......................................................................................................... 17

3.2.6 Flight Model (FM) ...................................................................................................................... 17

3.2.7 FM Spare .................................................................................................................................... 17

3.2.8 Spare Kit (SK)............................................................................................................................. 18

3.3 EEE parts .................................................................................................................................. 19

3.3.1 EEE Procurement under subcontractor responsibility ................................................................... 19

3.3.2 Alert and problem notifications..................................................................................................... 19

3.4 Specific Requirements .............................................................................................................. 20

3.4.1 Equipment long term storage after satellite integration ................................................................... 20

3.4.2 Components, materials and parts .................................................................................................. 22

3.4.3 Witness lots, critical materials and technology samples ................................................................... 23

3.5 Ground support equipment........................................................................................................ 24

3.6 Reviews and Key-points ............................................................................................................ 26

3.6.1 Formal reviews ............................................................................................................................. 26

3.6.2 Software reviews: .......................................................................................................................... 32

3.6.3 Mandatory Inspection Points (MIP) and Key Inspection Points (KIP) .......................................... 32



Date:24/09/2014


3.6.4 Parts Control Board (PCB) ......................................................................................................... 33

3.6.5 Material and Processes Control Board (MPCB) ........................................................................... 33

3.6.6 Radiations Control Board (ERCB) ............................................................................................. 35

4 REQUIREMENTS ON CONTRACTOR TASKS ............................................................................ 36

4.1 Management Requirements & Tasks ........................................................................................ 36

4.1.1 Project management ...................................................................................................................... 36

4.1.2 Reporting and meetings ................................................................................................................. 38

4.1.3 Reviews ........................................................................................................................................ 40

4.1.4 Risk management......................................................................................................................... 40

4.1.5 Schedule control ............................................................................................................................ 40

4.1.6 Cost control .................................................................................................................................. 41

4.1.7 Change control ............................................................................................................................. 42

4.1.8 Configuration control, information and documentation management ............................................... 44

4.1.9 Process Control............................................................................................................................. 45

4.1.10 Logistics and inventory ................................................................................................................. 46

4.2 Product Assurance Requirements and Tasks ........................................................................... 47

4.3 Engineering ............................................................................................................................... 47

4.3.1 Architecture & Configuration ...................................................................................................... 48

4.3.2 Analyses, Design & Development ................................................................................................ 48

4.3.3 Hardware/software compatibility ................................................................................................. 49

4.3.4 Thermal design ............................................................................................................................. 49

4.3.5 Mechanical engineering ................................................................................................................. 49

4.3.6 Contamination ............................................................................................................................. 50

4.3.7 Detailed electrical design and EEE engineering ............................................................................ 50

4.3.8 Electromagnetic compatibility (EMC) .......................................................................................... 50

4.3.9 Interfaces management .................................................................................................................. 51

4.3.10 RAMS (Reliability/ Availability / Maintainability / Safety) .................................................... 51

4.4 Embedded software (if any) ...................................................................................................... 52

4.4.1 General ........................................................................................................................................ 52

4.4.2 Deliveries ..................................................................................................................................... 52

4.4.3 Verification .................................................................................................................................. 53

4.4.4 Maintainability ............................................................................................................................ 54

4.5 Implementation & verification .................................................................................................... 55

4.5.1 Development and verification plan................................................................................................. 55

4.5.2 Manufacturing, Assembly, Integration , Verification and Testing ................................................. 56

4.6 Requirement on Deliveries ........................................................................................................ 58

4.6.1 Deliverable Items .......................................................................................................................... 58



Date:24/09/2014


4.6.2 Acceptance procedure .................................................................................................................... 60

4.6.3 Transport, storage, insurance, customs ........................................................................................... 61

4.6.4 Deliverable Mathematical Models ................................................................................................. 64

4.6.5 Documentation ............................................................................................................................. 65

4.6.6 Warranty ..................................................................................................................................... 65

4.7 Export Control ........................................................................................................................... 66

4.7.1 General ........................................................................................................................................ 66

4.7.2 Direct U.S. Procurements ............................................................................................................. 66

4.7.3 Lower tier U.S. Procurements ...................................................................................................... 67

4.7.4 European Union And National Export Restrictions ................................................................... 67

4.8 Health and environmental protection ........................................................................................ 68

4.9 Post Delivery Activities and Maintenance activities .................................................................. 68

5 DELIVERABLES ........................................................................................................................... 69

5.1 Deliverable documentation ........................................................................................................ 69

5.1.1 Documentation for unit falling in category A or B......................................................................... 71

5.1.2 Documentation for unit falling in category C or D ........................................................................ 78

5.2 Delivery of Mathematical Models .............................................................................................. 86

5.3 Delivery of ICD documentation and associated files ................................................................. 86

5.4 Delivery of Hardware, Software and GSE ................................................................................. 87



Date:24/09/2014


1 INTRODUCTION

1.1 Scope of the document

This Generic Statement of Work (GSOW) defines the Generic programme of work for METOP SG

MWI RFA equipment , hereafter called “Unit” or “Equipment”.

The Contractor (i.e. the equipment Contractor) shall be responsible for the provision of all materials,

manpower, facilities, supplies, tools, unit, documentation and support services as may be required to

design, manufacture, assemble, test and deliver to Airbus Defence and Space SAS the end products

and services (end items) specified in this Generic Statement of Work (GSOW).

1.2 Requirements presentation

To ease the traceability and compliance verification, all requirements in this GSOW are presented

with a specific reference code in the format below:

Requirement Code

The following requirement applies…

All formal requirements specified in this GSOW are assigned to a unique requirement code in the

following format:

MOS-GSOW-nnnn

Where

nnnn incremental number assigned to a given code

Note: nnnn is a four digit incremental number for each requirement or goal. Initial numbering of

nnnn is implemented with an increment, such to allow insertion of new / complementary

requirements during the MetOp- SG Project development phases.



Date:24/09/2014


2 REFERENCES

2.1 Applicable documents

In this section are defined the documents which are applicable associated to the present document.

The following documents will form the basis for the execution of the work by the unit Contractor:

Ref Title Document No. Issue

AD0 Equipment Requirements Specifications

AD400 Reserved AD reference for the Equipment Specific SOW Defined in specific SOW

AD13a MetOp-SG Instrument General Design & Interface Requirements MOS-SP-ASF-SYS-00816 1.1

AD13c General Design & Interface Requirements (Generic GDIR) ENS-06-00123-ASTR 8.0

AD13f General Design and Interfaces Requirements for MWI reflectors and

feed assemblies

MOS-SP-ADST-MWI-1000002085 1.0

AD14b MetOp-SG Product Assurance Requirements for Suppliers MOS-SP-ASF-SYS-0401 3.0

AD14d MetOp-SG Radiation Hardness Assurance Plan MOS-PLN-ASF-SYS-00810 2.0

AD14e MetOp-SG Cleanliness Requirements Specification MOS-SP-ASF-SYS-00770 3.0

AD15 MetOp-SG Instruments Management Requirements (INS-MARD) MOS-RS-ESA-INS-0435 1.0

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

AD19 MetOp-SG Instruments Tailoring of ECSS-E Standards MOS-RS-ESA-INS-0438 1.0

AD30 MetOp-SG Satellites Tailoring of ECSS-E Standards MOS-RS-ESA-SYS-0500 1.0

AD101 Generic Thermal Model Specification ADS.E.0206 2.0

AD102 Interface Thermal and Geometrical Model Specification (for ENS

GDIR)

ADS.E.1158 1.0

AD104 Satellite CAD Data Exchange Requirement Specification ADS.E.1054 1.1

AD105 3D and 2D ICD content specification ADS.E.1050 2.0



Date:24/09/2014


AD106 Thermal ICD (TICD) specification ADS.E.1159 1.0

AD107 Electrical double insulation - Technical requirements ADS.E.1031 1.0

AD114 Generic Mechanical FEM Specification ADS.E.0787 3.0

AD402 CAD data exchange MOS-TN-CGS-MWI-0028 1.0

These applicable documents include applicability of ECSS documents, which are considered as

applicable standards and normal practice in space industries.

The ECSS (European Co-operation for Space Standardization) documents are available at

ESA/ESTEC or on Internet at: www.ecss.nl

In case of any conflict between this GSOW and other applicable documents, the GSOW shall have

prevalence on these documents; however any conflict shall be reported to Airbus Defence and Space

SAS.

2.2 Reference documents

Ref Title Document No. Issue

RD01 List of acronyms and abbreviations MOS-LI-CGS-MWI-0001 01

RD02 MWI Instrument Design, consideration and requirements for long

term storage MOS-RS-CGS-MWI-0003 02



Date:24/09/2014


2.3 Abbreviations

ABCL: As Build Configuration List

AD: Applicable Document

AIT: Assembly Integration and Tests

BB: Bread Board model

CBS: Cost Breakdown Structure

CDR: Critical Design Review

CIDL: Configuration Item Data List

CPPA: Co-ordinated Parts Procurement Agency

CR: Conception Review

CTE: Coefficient of Thermal Expansion

DCL: Declared Components List

DDIL: Detail Deliverable Item List

DML: Declared Materials List

DPL: Declared Processes List

DR: Delivery Review

DRB: Delivery Review Board

EEE: Electrical , Electronics and Electromechanical

EGSE: Electrical & Ground Support Equipment

EICD: Electrical Interface Control Document

EIDP: End Items Datapack

EM: Engineering Model

EMC: Electro Magnetic Compatibility

EQM: Engineering and Qualification Model

EQSR: Equipment Qualification Suitability Review

ESD: Electro Static Discharge

FM: Flight Model

FMECA: Failure Mode Effects & Criticality Analysis

FMKS: Flight Model Kit Spare



Date:24/09/2014


GDIR: General Design and Interface Requirements

GSOW: Generic Statement Of Work

HW: Hardware

ICD: Interface Control Drawing

IF: Interface

KIP: Key Inspection Point

KoM: Kick off Meeting

MD: Mechanical Dummy

MDVE: Model-based Development and Verification Environment

MICD: Mechanical Interface Control Document

MIP: Mandatory Inspection Point

MOS: MetOp-SG

MPCB: Materials & Processes Control Board

MPR: Monthly Progress Report

MRR: Manufacturing Readiness Review

NA: Not Applicable

NCR: Non Conformance Report

NRB: Non-Conformance Review Board

PA: Product Assurance

PCB: Parts Control Board

PDR: Preliminary Design Review

PFM: Proto Flight Model

PSA: Parts Stress Analysis

PT: Product Tree

QA: Quality Assurance

QM: Qualification Model

QR: Qualification Review



Date:24/09/2014


QSR: Quality Summary Report

RD: Reference Document

RFD: Request for Deviation

RFW: Request for Waiver

RR: Requirement Review

SOW: Statement of Work

SSOW: Specific Statement Of Work

STM: Structural & Thermal Model

SVF: Software Verification Facility

SW: Software

TBA: To Be Agreed

TBC: To Be Confirmed

TBD: To Be Defined

TBR: To Be Reviewed

TD: Thermal Dummy

TRB: Test Review Board

TRR: Test Readiness Review

UCL: User Component List ( or DCL)

VCD: Verification Control Document

WBS: Work Breakdown Structure

WCA: Worst Case Analysis

WPD: Work Package Description

Note: The wording Contractor or Supplier refers to the same entity in charge of the work defined in this document.



Date:24/09/2014


3 UNIT DEVELOPMENT APPROACH AND DELIVERABLES

3.1 Development Logic & Models Philosophy

3.1.1 Equipment Category:

MOS-GSOW-3110 Unchanged

The Contractor shall identify the category of the proposed item and present a development logic

according to the following statement:

Depending on its design and development heritage, each unit is classified following 4 development

categories:

cat. A: existing off-the-shelf or recurring unit fully qualified

cat. B: existing off-the-shelf or recurring unit which require delta qualification

cat. C: modified unit, qualification to be made

cat. D: new unit to be developed and qualified

It is the Contractor responsibility, in view of AD's to this GSOW and Contractor own heritage to

identify, define, and establish the optimal development logic and unit category. Use of existing off-

the-shelf or recurring unit, i.e. falling under development categories A or B, will be favored as much

as possible. As a consequence, the Contractor may propose equivalent alternatives where the

design was developed with different requirements.

In case of a new or modified unit belonging to categories C or D, utilization of proven design and/or

technologies shall be considered.

This shall be properly documented within the Unit Design and Development Plan

The category and development logic proposed by the Contractor will be subject to Airbus Defence

and Space SAS approval.

3.1.2 Existing off-the-shelf or recurring unit (cat. A or B)


For items in category A or B, the Contractor shall propose an EQSR to validate the classification of

the item.

The acceptability with respect to the requirements is thoroughly verified at the Equipment

Qualification Suitability Review (EQSR) where the unit classification as category A or B is finally

settled and procurement is formally authorised.

Equipment is then directly procured by Airbus Defence and Space SAS at Flight Model (FM) or

Proto-Flight Model (PFM) standard against their own specification requirements and standard

processes/plans. In case of need for validation at higher level, an Engineering Model (EM) may be

requested by Airbus Defence and Space SAS which is then explicitly specified in the AD400.



Date:24/09/2014


Kick-Off

Equipment

Category

New Equipment Modified EquipmentRecurrent Equipment

with limited changesRecurrent Equipment

PDR

CDR

QR

Models MRR - TRR - TRB - DRB/SRB

Acceptance

EQSR, to confirm category

PDR, if required

RR

3.1.3 New or modified unit (cat. C or D)


New or modified equipment shall be developed against Airbus Defence and Space SAS’s

requirements.

New units shall be qualified on an EQM and proto-qualified on a PFM.

In case of modified units and providing that the subcontractor demonstrate that modifications are

minors, development at Prototype, Bread Board (BB) or EM standard can be proposed, followed by

Proto-qualification on PFM. The contractor shall propose a pre-qualification program at BB / EM

level for category C which must be submitted to Airbus Defence and Space SAS for Approval.

For category D, for risk reduction, the Contractor is free to make all the design validation on a

BB/EM before to go to EQM manufacturing .



Date:24/09/2014


3.2 Model Description

3.2.1 Prototype or Bread Board (BB)


A BB is functionally and electrically representative of the Flight equipment or part of it and it is used

to validate a new or critical feature of the design and secure the development of the unit. There are

no specific requirements for configuration and interface control.

Redundancy is not necessary and commercial components are allowed as far as they do not affect

the performances, nor the functional representativeness of the FM/PFM.

All tests plans shall be submitted to Airbus Defence and Space SAS approval.

3.2.2 Engineering Model (EM)


An Engineering Model shall be fully representative of Flight Models in form, fit, and functions. A

lower standard for electrical components, materials and processes may be used as long as they

provide representative performances. However, the standard shall be the highest possible

achievable within given schedule constraints. Any redundancies which are provided in the flight

standard model shall be provided in the EM unless otherwise agreed with Airbus Defence and

Space SAS. If redundancy is not required, the switching functions associated with redundant

functions shall be demonstrated.

EMs are intended to be used for the functional and electrical / EMC performance as well as ground

station compatibility verification at higher level. Participation of the EM to the higher level AIT

program in combination with flight models have to be considered. Therefore, compatibility to all FM

interfaces in AIT program is required; e.g. gold plated connectors, pins and sockets or respective

connector savers are necessary. Compatibility of the EM with thermal vacuum testing shall also be

considered allowing usage during Instrument level thermal tests.The Equipment Contractor shall

apply configuration control and as build status reporting to EMs on all ICDs as a minimum.

For particular applications in the higher level AIT, the build status and test requirements may

deviate from the above. Any such case is defined in the equipment specific Statement of Work.




Date:24/09/2014


3.2.3 Engineering and Qualification Model (EQM)


The EQM shall be fully representative of Flight Model in form, fit and functions. A lower level of

electrical components may be used. The standard of these components shall be the highest

achievable within the schedule constraints but using the same manufacturer, the same type and

the same package as for the Flight Models. Only the testing and the screening of the parts might

be different compared to the Flight Models. Any and all redundancies which will be provided in the

Flight Models shall be provided in the EQM. If redundancy is not required, the switching functions

associated with redundancy functions shall be demonstrated.

The EQM shall be used by the contractor to qualify the unit as defined in AD13f (including thermal

vacuum tests mechanical vibrations, shocks, EMC/ESD, … at qualification level and duration) and

delivered to Airbus Defence and Space SAS when requested .

Participation of the EQM to the higher level AIT program in combination with flight models have to

be considered. Therefore, compatibility to all FM interfaces in AIT program is required; E.g. gold

plated connectors, pins and sockets or respective connector savers are necessary. The EQM shall

be built to full flight standard in accordance with the PA and configuration management

requirements except for EEE parts(see above). Testing shall be done in accordance with this

GSOW

It shall also be possible to temporarily integrate this model in the satellite in order to conduct

electrical and functional tests.


3.2.4 Structural and Thermal model (STM)


A STM may be required and shall be:

structurally and thermally representative of Flight Model definition in terms of mounting interface, mass, centre of gravity, moment of inertia,allowable volume and thermal properties (dissipations, optical properties, contact conductances…). If the equipment is contributing to the main frequencies of the spacecraft (to be specified by Airbus Defence and Space SAS) the SM shall by dynamically representative of Flight Model definition.

representative with respect to micro vibration loads imposed to the mounting I/F.

The STM will be used for the mechanical and thermal qualification of the instrument.

It will be subjected to qualification levels and durations



Date:24/09/2014


3.2.5 Proto Flight Model (PFM)


The PFM shall be built to full flight standard in accordance with the PA requirements for Flight

Models. Flight Standard parts shall be used.

Protoflight models shall be subjected to proto-flight qualification and acceptance testing (including

EMC, vibrations and thermal vacuum at proto-qualification levels and duration but no ESD and

shocks).

Following successful protoflight model testing, the PFM will be used during protoflight model testing

of the RFA / instrument / satellite protoflight models and shall successfully withstand these

environmental tests in order to achieve full qualification.


3.2.6 Flight Model (FM)


FM shall be built to full flight standard in accordance with the PA requirements for Flight Models.

Flight Standard parts shall be used. Flight models shall be subject to flight acceptance testing.

FM test plans, procedures and reports shall be issued and configured.


3.2.7 FM Spare


If requested in Specific SOW, FM Spares models shall be manufactured and submitted to

acceptance tests as defined in AD13f requirements. Test readiness reviews and Test results

reviews shall be conducted on these models as for any other models.

If FM spare or spare parts are not explicitly requested in the Specific SOW, a spare kit approach

shall be proposed and agreed with the customer as a warranty service to repair or replace any unit

during the unit or RFA or instrument or satellites integration phases and during the satellites launch

campaigns. Reparation and delta acceptance tests activities shall be lower than 8 weeks, reduced

for launch campaign. Critical items shall therefore be identified and an adequate spare philosophy

shall be defined to guarantee these schedules.



Date:24/09/2014


3.2.8 Spare Kit (SK)


A spare kit shall be proposed when required by the specific SoW. SK shall allow for repair of any failure that might occur for the equipment at any time during the programme until the launch of the last satellite.

The definition of the Spare Kit shall be optimized by the contractor and may therefore comprise:

EEE parts allowing to repair any board,

each type of unpopulated PCB

structural and harness elements,

connectors,

or

Populated PCB of each type

The FM Spare Kit list shall be agreed with the Customer prior to Contract finalization.

The Contractor shall assess and propose the best approach between separate EEE parts or

assembled parts on boards to meet the long storage constraint for late repair up to the launch of

the last satellite.

In any case the contractor shall maintain the availability of a spare board in case of use of the initial

spare board on an early RFA or instrument or satellite in order to secure the repair capability of the

equipment for the last satellite before launch.

All spare elements are separately prepared, regrouped, kitted and stored under consideration of

the PA requirements.

The spare kit shall be defined, set up and kept individually. It shall not be mixed with spares of

another equipment.

All spare parts, components and assemblies procured or manufactured in support of the repair

facility shall fulfil all the applicable specifications and be fully interchangeable with the flight part,

component or assembly.

The SK shall be complete at the contract closeout. The SK shall take into account the specified

lifetime of the parts and the project schedule.



Date:24/09/2014


3.3 EEE parts

3.3.1 EEE Procurement under subcontractor responsibility

The general baseline for parts quality level and management is identified in AD14b.


The selection, evaluation, qualification, screening, and procurement of all EEE parts shall be the

responsibility of the Contractor. There will be no Centralised or Coordinated Parts Procurement

Agency under the responsibility of EADS Airbus Defence and Space SAS for the METOP SG

programme.

All tasks must be performed either internally or through a Services Agency and shall conform to the

PA requirements.

3.3.2 Alert and problem notifications


The contractor shall establish and implement procedures for handling any problem arising on EEE

parts during parts procurement, post-procurement or during all levels of equipment manufacturing

or testing as specified for alert management in PA requirements (AD14b).

Any alert notification which may be relevant to a EEE part belonging to the DCL shall be notified to

Airbus Defence and Space SAS by the contractor, within 2 working days, with the associated

recommendations.

As EM problems might be a sign of potential generic problems, the above requirement shall apply

to EM and PFM/FM components



Date:24/09/2014


3.4 Specific Requirements

3.4.1 Equipment long term storage after satellite integration

The specificity of the METOP SG programme is the production of several satellites which should be

stored after their validation until their defined launch date which might be several years after their

preliminary acceptance.

The ground operations and storage scenario for the METOP-SG equipment is planned as follows:

At delivery and shipment of the equipment from the Contractor to the Customer, the equipment will be:

- integrated onto the METOP SG RFA / instrument / satellite (PFM) for the first model

integrated on the METOP SG RFAs / instruments / satellites for the following models all these models

undertaking the nominal RFA / instrument / satellite testing campaigns.

After the testing campaign, the PFM satellite shall enter the launch campaign for the first satellite.

After the testing campaign, the FM satellites (FM2 and FM3 as option), with integrated equipment and sub-systems, will enter into a long storage, after the completion of the respective METOP SG satellite Pre-Storage Review (PSR).

After the storage period and prior to launch, the FM satellites will be de-stored and submitted to a validation scenario for final acceptance before launch.

Spare equipment and spares kits will be stored at the Contractor’s premises until the delivery date

defined in the Specific SOW and at the customer premises after delivery.

MOS-GSOW-3410 Modified

In correspondence to this scenario the Contractor shall analyse and identify the constraints regarding

the long storage on ground (several years) for flight items and long term maintenance for non-flight

items (GSE). The Contractor shall define a Long Term Storage Plan{EN-13} for the

subsystem/equipment, clearly identifying and justifying the recommendations to be undertaken in

preparation for storage and during storage (storage environment, storage conditions, periodic check-

up if necessary, parameters trend analysis..) and all necessary actions at de-storage.

After integration on the RFA / instrument / satellite, the end item shall not suffer any degradation

resulting from storage under conditions as defined in AD0 and AD13f.

.



Date:24/09/2014


MOS-GSOW-3411 New

In addition, the Contractor shall clearly identify the design requirements and constraints that shall

be applied to ensure the proposed designs of all items take full account of the storage

requirements and apply appropriate design measures.

These shall be detailed in the Equipment Design Requirements and Constraints for Long Term

Storage document {EN-14}, and shall include:

definition of all design measures that shall be taken into account in the design of the unit to ensure compatibility with long term storage, such as:

- relaxation of launch preloads in mechanisms to avoid long term creep, if relevant,

- provision of local purging / flushing (no dead end cavities / good effectiveness) for those items particularly sensitive to contaminations and / or humidity,

- provision of test interfaces (as appropriate) to allow local exercising / activation and / or troubleshooting of critical equipment without resorting to switching on the complete RFA / instrument / satellite,

- definition of simple unit health check modes;

definition of materials, material types that should be avoided in designs to ensure compliance to the long term storage requirements;

definition of samples (or test pieces) required to support the confirmation that unacceptable materials / performance degradation has not occurred during the storage period, such as adhesives integrity, thermo-optical and optical properties, lubricants;

GSE design constraints.


The Contractor shall define the baseline activities required for subsystem/equipment de-storage,

identifying those specific tests, including environmental and/or functional / performance that will be

required when revalidating the subsystem/equipment prior to its scheduled launch.


Any specific storage requirement of the equipment, integrated on the RFA or instrument or satellite,

or in the adequate container, shall be detailed in the User Manual regarding Storage and Delivery

Instruction.



Date:24/09/2014


MOS-GSOW-3414 ECSS-Q-ST-70_MOS-010 8.2 New

Particular attention shall be given to the need for unit recalibration (if any) after long term storage

periods. Possibilities to minimise / eliminate the needs for extensive recalibration shall be

thoroughly investigated.

3.4.2 Components, materials and parts


The unit design shall be based on proven technologies with already existing components or

components with a strong heritage. The Contractor shall identify the components (EEE parts,

materials, ….) manufacturing processes which can be sensitive to evolution, critical to long term

storage of the equipment integrated or not on satellite or to potential ageing effects.

The design and materials selection for the subsystem/equipment shall minimize constraints during

the long-term storage period. Any needs for special environments (local purging) and/or periodic

subsystem/equipment activation, shall be coordinated with Customer. The contractor shall identify

materials / parts needed to cover sensitive items (life limited items, mechanisms,…) versus long

term storage.


The life limited items shall be avoided as much as possible; in case such items are needed, the

Contractor shall define:

The validity period,

Any constraint regarding use of the item in the RFA or instrument or satellite AIT sequence (environmental testing, operations before launch…) or storage,

The need for exchange and revalidation testing. In case the limited life item can be exchanged at RFA or instrument or satellite level, any specific GSE for this operation shall be identified and provided.

The need of recalibration after long term storage periods; avoidance or minimization of such recalibration shall be investigated.



Date:24/09/2014


3.4.3 Witness lots, critical materials and technology samples

The need of witness lots and technology samples, especially of any critical or new technologies and

manufacturing processes, are defined in the following requirements.

MOS-GSOW-3430 New

The Long Term Storage Plan {EN-14} shall address material performance during the storage

period and identify mechanisms to predict and/or verify material or process or mechanical part

performance throughout the storage period until de-storage and launch campaign activities.


For critical items sensitive to long term storage, the Contractor shall analyse and define an

approach of witness samples to be stored in the same conditions as flight hardware and used for

verification at the required time. This approach will be performed by the Contractor in the early

phase of his activities and presented to Airbus Defence and Space SAS for analysis and

agreement for implementation of the necessary witness lots and adequate samples, which will be

part of contractual change to the baseline activities.


The Contractor will have to issue and maintain a list of these samples with recommendations to be

applied during storage. The samples might be stored in an environment close to the one applied for

the RFA or instrument or satellite during storage (GN2 environment, RH < 10%). For each sample,

the Contractor shall define which kind of verification has to be done, including the frequency of the

verifications (recommended periods / dates and warnings for de-storage operations).

MOS-GSOW-3433 New

The Contractor shall ensure that materials / parts life testing is initiated when the cumulative life-

time all along the different sequences of use (AIT, storage and in orbit operations) is assessed

critical or out of specification and alternative materials / items are not available.



Date:24/09/2014


3.5 Ground support equipment


The Contractor shall carry out the design and development of all the HW & SW Ground Support

equipment which are necessary to support the Unit development, qualification and acceptance.

The contractor shall take care of the interfaces representativeness (wrt flight configuration ) for unit

testing as well as the reliability and safety aspects.

MOS-GSOW-3511 New

The design of all GSE and associated test equipment shall be undertaken with due regard to the

duration of the overall MetOp-SG programme, together with associated storage plans and

constraints.

For deliverable GSE items ,the following requirements shall apply:


The Contractor shall address the testability, availability (reliability & maintainability) , safety , life duration (use of some GSE to be considered in case of need for last launch) operability (man/machine interface, clarity & completeness of operational procedures & manuals) ,ability to interface with flight segment in a safe way in the design of the GSE items.


The contractor shall provide FMECA to guarantee the safety of the tested unit in case of failure (no failure propagation from GSE to tested unit).


The contractor shall provide Hazard analysis (or Safety Assessment Report), including any GSE SW as necessary, to guarantee the safety of the personal and tested unit during operations (unit integration, unit testing).


The Contractor shall ensure that these GSE and related procedures are properly controlled. As a minimum he shall identify the baseline documentation & product definition and trace



Date:24/09/2014


subsequent modifications.


The Contractor shall ensure that the deliverable GSE is able to fulfil its requirements and is correctly and sufficiently documented. The Contractor shall ensure that maintainability requirements are fulfilled and define a maintenance plan.


The contractor shall provide a European Community certification (including EMC tests results) with any deliverable GSE. The contractor shall provide a CE (Conformité Européenne) Declaration of Conformity for any deliverable GSE (with regard to the applicable Product Liability CE directives).


GSE which is not a deliverable item to AIRBUS DEFENCE AND SPACE SAS, either constituted

from the Contractor's or his lower level contractor's inventory of laboratory and test equipment,

shall remain available for MetOp SG for dedicated need with regard to equipment operations

(investigation, repair, retrofit, testing…) and able to be back operational in a reasonable time until

launch of the last MetOp SG Satellite. The Contractor shall define the approach for GSE availability

in the last de-storage phase of the satellite before launch with respect to the need of possible repair

of the equipment if needed.

The Contractor shall ensure that these GSE and related documentation, manuals and software

(including SW tools and Data Base) are subject to configuration management and control.

MOS-GSOW-3519 New

The responsibility for storing and maintaining all associated unit level GSE and associated special

test equipment required at unit level, either for nominal activities or unit anomaly investigations

and/or repair remains with the Contractor for the duration of the programme, and until the

successful SIOVR of the last MetOp-SG satellite on which the unit is embarked.



Date:24/09/2014


3.6 Reviews and Key-points


Reviews at unit level, formal reviews and key-points, shall be identified during the development

phase depending on the unit development category. The Contractor shall document within its

Development Plan, in coherence with its own heritage, the unit reviews he intends to implement in

order to secure the development during Phase B-C/D.

3.6.1 Formal reviews

Formal review will be held at contractor premises. Representatives of Airbus Defence and Space

SAS, Speng, CGS, Airbus Defence and Space GmbH and ESA and possibly EUMETSAT might

participate to the reviews.

3.6.1.1 For unit falling in category A or B


For units/items identified in category A or B, the reviews listed in the following table shall be

implemented and meet the presented purpose.

Name Date Purpose

Kick-Off Review (KO)

T0 - Confirm the contract baseline (design, development, performance , verification, deliveries)

- Identify major open points from Airbus Defence and Space SAS requirements or Contractor proposal,

- If successful, shall give the go ahead for the activities defined in the meeting,

Requirements Review (RR) T0 + 1 month The purpose of the RR is to formally review the specification requirements. The Contractor shall identify:

- What are the critical technical issues contained within the requirements

- How each of the requirements will be fulfilled

- What back-up is foreseen for critical technical issues

- Which milestones are on the critical planning path

- What is the preliminary design approach

The impact of TBD or TBC in the specification shall be assessed.



Date:24/09/2014


Name Date Purpose

The compatibility of the equipment with its interfaces and its ability to satisfy the performance requirements shall be formally acknowledged.

- The RR is a major milestone in the equipment supply process as it establishes a technical risk analysis for the equipment development. The Contractor shall include this analysis it its risk register.

Equipment Qualification Suitability Review (EQSR)

Typically 1 month after KO when EQSR is applicable (equipment Cat A,B,C)

- Review the design standard, built standard , configuration and qualification status against requirements,

- Verify the acceptability of the unit design, specifications and plans with respect to requirements

- Freeze the unit interfaces (electrical, TM/TC, mechanical, & software ICD)

- Review qualification status of all parts, materials and processes used and qualification status of the unit

- Need for PCB and MPCB in the case of changes on parts, materials or processes

- Identify the need of delta-qualification and evolution in material and processes

- Verify the acceptability of the GSE design, specifications and plans with respect to requirements

- Confirm equipment category

- Authorise unit and GSE development activities

Manufacturing Readiness Review (MRR)

TBD by subcontractor at least 2 weeks before EQM, PFM & FM manufacturing

- Review “as-design” documents

- Verify that all activities necessary prior to start of MAIT are complete,

- Review material, EEE and processes

- Authorise unit & GSE manufacturing

Test Readiness Review (TRR) TBD by subcontractor, at least 2 weeks before acceptance tests of any model (including EM)

- Review delta-qualification plan if any

- Review test procedures, test plan and test sequences

- Review “as-built” configuration

- Review test configuration (HW and SW), facilities and personnel

Test Review (TR or Test Review Board ,TRB)), and Qualification Review (QR) for category B

TBD by subcontractor

- Review the satisfactory qualification and acceptance test results and analysis by subcontractor

- Review the unit status & unit & GSE



Date:24/09/2014


Name Date Purpose

documentation

- Review the final configuration and non conformances

- Verify that all actions are correctly closed

Delivery Review (DR, or DRB) TBD by subcontractor

Review the final EIDP

Verify that the equipment and all deliverables satisfy all contractual requirements

- Acceptance of unit, inspection and authorisation of shipment

- Review of all logistics requirements (container, shipment …)

Note: TRB and DRB may be combined



Date:24/09/2014


3.6.1.2 For unit falling in category C or D


For units/items identified in category C or D, the reviews listed in the following table shall be

implemented and meet the presented purpose.

Name Date Main purpose

Kick-Off Meeting (KO)

T0 - Confirm the contract baseline (design, development, performance , verification, deliveries)

- Identify major open points from Airbus Defence and Space SAS requirements or Contractor proposal,

If successful, shall give the go ahead for the activities defined in the meeting,

Equipment Qualification Suitability Review (EQSR)

(for category C only)

Typically 1 month after T0

See description above

Requirements Review T0+1 month The purpose of the RR is to formally review the specification requirements. The Contractor shall identify:

- what are the critical technical issues contained within the requirements

- how each of the requirements will be fulfilled

- what back-up is foreseen for critical technical issues

- which milestones are on the critical planning path

- what are the preliminary design, including software or VHDL approach

The impact of TBD/TBC in the specification shall be assessed.

The compatibility of the equipment with its interfaces and its ability to satisfy the performance requirements placed on it shall be formally acknowledged.

The RR is a major milestone in the equipment supply process as it establishes a technical risk analysis for the equipment development. The Contractor shall include this analysis in its Risk Register.

Preliminary Design Review (PDR)

TBD by subcontractor

- Verify design feasibility , compatibility & predicted performance with all



Date:24/09/2014



For category C, PDR may be adjusted according to outcome of EQSR (1)

requirements

- Verify the consistency of the lower level constituents specifications with the unit specification

- Review test results on EM or prototypes and identify design modifications required to meet the specification

- Review development plan and associated risks

- Review detailed plans and procedures

- Review parts list, materials list & processes list

- Formally agree preliminary Design,

- Authorise detail design activities, unit EQM manufacturing and procurement of FM long lead items (LLI) when duly justified

Manufacturing Readiness Review (MRR)

TBD by subcontractor at least 2 weeks before EQM, PFM & FM manufacturing

- Review “as-design” documents

- Review material, EEE and processes

- Authorise unit & GSE manufacturing

Test Readiness Review (TRR) TBD by subcontractor, at least 2 weeks before tests of any model (including EM)

- Review delta-qualification plan if any

- Review test procedures, test plan and test sequences

- Review “as-built” configuration

- Review test configuration (HW and SW), facilities and personnel

Critical Design Review (CDR)

- Verify compatibility of the detailed design and complete set of analyses with requirements

- Review EQM or EM test results

- Review unit GSEs acceptability /documentation (if any)

- Review PFM manufacturing file and CIDL

- Review the qualification / acceptance plan

- Formally agree detailed design,

- Authorise the unit PFM manufacturing

Qualification Review (QR) - Review results of EQM and/or proto-qualification tests on the PFM

Test Review Board( Test Review Board ,TRB)) (2)

- Review the satisfactory qualification and acceptance test results and analysis by subcontractor

- Review the unit status & unit & GSE



Date:24/09/2014



documentation

- Review the final configuration and non-conformances

- Verify that all actions are correctly closed

Delivery Reviews Board (DRB) Review the final EIDP

Verify that the equipment and all deliverables satisfy all contractual requirements

- Acceptance of unit, inspection and authorisation of shipment

Review of all logistics requirements (container, shipment …)

Note: TRB and DRB may be combined

(1) For unit category C, review of design changes documented by the delta-design/delta-analysis

documentation and review of the delta-qualification or qualification test results.

(2) Specific tasks :


a) The Contractor shall provide at the TRR any lower level test data


b) Identification of out of family test results will be done as far as possible, depending on the

availability of relevant past data at the equipment level or at sub-assembly level. In this case:

a. at the TRB any equipment level test data which may assist in the review of performance

trends, out-of-family behaviour, situations of excessive variability, risky weak margins to

specification limits, etc, relating to the equipment which is about to undergo formal tests.

A subset of the above-mentioned test data shall be represented in the form of Trend

Analysis Curves including the same test data resulting from similar tests performed on all

equipment of the same product line.

The Contractor shall provide an analysis (root cause) of any abnormal behaviour and

propose improvement measures accordingly.

b. Test Results and Test Result Summary sheets shall be available and delivered at the TRB

in the form of data populating spread sheets, with associated X-Y Trend Analysis Curves

as required in above paragraph and showing clearly the Upper Specification Limits (USL)

and/or the Lower Specification Limits (LSL) together with the Out-of-specification results if

any.

The Contractor shall provide an analysis (root cause) of any abnormal behaviour and propose



Date:24/09/2014


improvement measures accordingly.

3.6.2 Software reviews:

Solutions without software are preferred.


If the contractor proposes a solution which requires a software development, including firmware

embedded into the unit, the following reviews shall be implemented :

SW-SRR : Software Requirements Review,

SW-PDR : Software Preliminary Design Review,

SW-CDR : Software Critical Design Review,

SW-QR : Software Qualification Review,

SW-AR : Software Acceptance Review.

This is in accordance with the ECSS-E-40 1B, document applicable to the software.

Development, methodology and validation aspects shall be addressed during the reviews.


The software review cycle shall run in parallel with the equipment review cycle defined in chapter

3.6.1.2. The links between the 2 review cycles is the following :

The (equipment) SRR is prior to the SW-SRR.

The SW-QR is prior to the (equipment) QR.


If the contractor proposes a solution using recurring software, the Equipment Qualification

Suitability Review (EQSR) at unit level shall include the SW-SRR, the SW-PDR and the SW-CDR,

the two other software reviews being held within the unit TRR and DR.

3.6.3 Mandatory Inspection Points (MIP) and Key Inspection Points (KIP)

The purpose of the unit inspection points is to verify the acceptability of the as built configuration of

the hardware at pre-defined points in the flow chart of the manufacture activities.


MIPs and KIPs shall be held as necessary and agreed with Airbus Defence and Space SAS.

The MIPs and KIPs shall be held under the Contractor’s responsibility. EADS Airbus Defence and



Date:24/09/2014


Space SASshall be invited to the MIP with sufficient notice in advance. The CGS, Airbus Defence

and Space GmbH and ESA representative(s) may also attend The results of the MIP / KIP shall be

reported to Airbus Defence and Space SAS without delay.


The unit Manufacturing And Integration and Test (MAIT) flow diagram shall indicate all MIPs and

KIPs and the scheduled dates and location. The results shall be submitted to Airbus Defence and

Space SAS for approval.

3.6.4 Parts Control Board (PCB)


The Contractor shall organize a Part Control Board whose objectives and organization is as

follows:

The requirements for the selection of EEE parts and their usage are given in AD14b & AD13f. The

approval for the Equipment are implemented through Part Control Boards (PCBs) chaired by the

Supply Quality Assurance Manager and held with the Contractor.

The PCB is put under Airbus Defence and Space SAS project QA control and may be composed

by designer, EEE parts engineer, PA responsible, system representative, any other experts

(radiations, assembly, …) from both Airbus Defence and Space SAS and the Contractor. The end

customer (CGS, Airbus Defence and Space GmbH, ESA) representative may also use the right to

participate as a PCB member.

Depending on the progress of the Equipment Purchase, the main PCB activities are :

Review and approval of the Contractor's EEE parts management plan and any associated document

Parts approval including evaluation activities (by means of Contractor DCL)

Purchase status (including schedule, dispatching, delivery schedule) ,

Problem resolution (non-conformances, RFD, RFW, ...).

3.6.5 Material and Processes Control Board (MPCB)

The requirements for the

selection of Materials and

Processes and their usage are

given in AD14b.MOS-GSOW-

3650

Unchanged

The Contractor shall notify the Airbus Defence and Space SAS project QA as early as possible of

the use of new or unproven materials/processes, together with proposed testing and analysis, and



Date:24/09/2014


the subsequent update of the DML/DPL and shall organize a Material and Processes Control

Board. The CGS, Airbus Defence and Space GmbH and ESA representative(s) may also attend.

Airbus Defence and Space SAS project QA will chair at Contractors’ premises the Materials &

Processes Control Board meeting with Contractors’ representatives from design, technology,

inspection, test, manufacturing, product assurance.


The MPCB shall be organized as such to meet the following objectives:

Co-ordinate all actions related to the selection and control of all Materials, Parts and

Processes for the Contractor

Verify that Materials and Processes lists are representative of the hardware design

Review and approve DML and DPL

Specify the necessary actions for Materials and Processes approval

Establish validation / qualification plans and review qualification reports



Date:24/09/2014


3.6.6 Radiations Control Board (ERCB)

MOS-GSOW-3652 New

An Equipment radiation Control Board (ERCB) shall be organised, as required by AD14b as

follows:

“as designed” ERCB : At time of PDR in the case of new or modified equipment design and not later than CDR in case of change of EEE parts between PDR and CDR ; at EQSR time frame in the case of category A/B recurring equipment,

“as built” ERCB : At time of MRR and not later than TRR, as soon as “as built” DCL is available

The « as designed » ERCB will examine:

EEE parts list as design

Available test data for these EEE parts

Needed and planned radiation verification tests (RVTs)

Radiation analysis (PDR issue)

Radiation effects on design (FMEA, WCA) and counter measures

The “as built” ERCB will examine:

As Built DCL, and verification that all actual parts of the as built DCL have been considered in radiations analysis,

Final radiation analysis/report,

Radiation test data/report (including RVTs),

Validation of radiation data results (by sampling of TID, DD and SEE data) used for radiation analysis,

The ERCB is chaired by an Airbus DS SAS radiation engineer. The contractor shall make sure of

the availability of (as a minimum) a radiation engineer and an electronic designer (mandatory for

“as designed” ERCB), other participants may need to attend on chairman request. An end

customer (CGS, Airbus Defence and Space GmbH, ESA) representative may also be invited by

Airbus DS SAS and participate as an ERCB member.

The contractor shall provide on-site all necessary justificatives to support the review:

Drawings and schematics,

EEE parts list (as design/as built)

Radiations modelling and analysis results,

Test data, and reports showing radiation capability of the components (and materials when applicable),

Worst case analysis, FMEA, showing radiations effects accounted for,

Radiation Verification Test Reports for actual lots assembled to MetOp SG H/W.



Date:24/09/2014


4 REQUIREMENTS ON CONTRACTOR TASKS

4.1 Management Requirements & Tasks

4.1.1 Project management


The contractor shall implement and maintain a project management organisation in order to

manage and control adequately all activities of the contract (with particular emphasis on quality,

risks and schedule control), to provide the proper control and directives to the lower tier

subcontractors or Contractors if any, and the required reporting and interface to Airbus Defence

and Space SAS.

This organization shall be presented in the proposal management plan. A project Management

Plan shall be issued by the Contractor reflecting the management principles implemented in

answer to the management requirements.


When the Contractor has lower tier subcontractors or Contractors, he shall, as a minimum, :

issue procurement specifications and other relevant documentation

ensure that all project requirements are properly reflected to his lower tier subcontractors or Contractors and effectively implemented

monitor lower tier subcontractors or Contractors performances with respect to all project issues, schedule, quality, documentation and deliveries.

Lower Tier Subcontractors obligations are defined in the Contract and in the PA Requirements.


The Contractor shall submit the list of Lower Tier Subcontractors as defined in the Contract, with

the description of the work to be performed, for approval by Airbus Defence and Space SAS.

Further changes to this proposed list of Lower Tier Subcontractors shall be submitted to Airbus Defence and Space SAS approval. Access to data (even proprietary data) and access to plants are requested at any level of subcontracting.



Date:24/09/2014



Airbus Defence and Space SAS shall have access to the Contractor’s and his subcontractors

‘facilities, to all unit related documentation and to all areas where the project work is performed.

The access shall also be granted for Airbus Defence and Space SAS customers (CGS, Astrium

Defence and space GmbH, ESA) or his representatives, in the presence of Airbus Defence and

Space SAS.


The Contractor's project manager shall be responsible for the execution of the contract. Every

formal communication shall be addressed to him and the formal communications signed by him

shall be binding for the Contractor.

All information delivered under this contract by the Contractor to Airbus Defence and Space SAS

may be copied to Airbus Defence and Space SAS customers (CGS, Astrium Defence and space

GmbH, ESA).


Electronic information exchange shall be implemented according to any of the following

production standards (Word (TM), Power point (TM), Excel (TM) for Windows, Portable Data

Format (pdf) document generated using Adobe Acrobat software)


The Contractor shall nominate the key persons who perform the essential functions for the

execution of the contract. Any change of key personnel shall be reported to and agreed by Airbus

Defence and Space SAS beforehand.

The Contractor shall provide a project directory enabling efficient communications and keep it up to

date.


Airbus Defence and Space SAS will exercise its control and monitoring of the contractor through

the progress reports, progress meetings or other meetings, and reviews as defined in this GSOW.

Conference calls can be organised whenever necessary or for efficiency reasons. The contractor

shall accept a collocation of Airbus Defence and Space SAS representative at his premises if

considered necessary at a point of development.



Date:24/09/2014



Based on inputs given by the customer, the contractor shall develop and maintain the project

management structure (product tree ,WBS, OBS, CBS, contract structure). The contract structure

and product tree shall be approved by Airbus Defence and Space SAS.

4.1.2 Reporting and meetings


The Contractor shall provide to Airbus Defence and Space SAS, every 6 weeks, a progress report

providing concise description of :

major achievements of the period (including formal milestones and deliveries)

major achievements planned for next period

area of concerns description (including PA issues) and recovery/risk mitigation actions

major engineering data and technical status

configuration status : status list of changes (CR, CP) and status list of non-conformances RFD, RFW

Written statement of any change (Lower Tier Subcontractors organisation, design, part, material, process or procedure) in the period at subcontractor or lower tier level.

schedule showing current progress and appreciation of the critical path. (including Source electronic files , eg MPP S/W)

contractual milestones

action item list including also risk mitigation plan action item status

The contractor shall send the progress report one week prior to the relevant progress meeting to

allow an effective meeting.


The Contractor shall establish an action item system and make the action item status available at

any time and as a minimum in the progress report.



Date:24/09/2014



The Contractor shall propose a progress meeting calendar enabling efficient communication

according to the various project phases. This will be subject to Airbus Defence and Space SAS

approval . One progress meeting every 6 weeks at least is requested. Other meetings may be

requested to address any managerial, contractual, or technical matter (including audits, anomalies,

etc..).


The Contractor shall inform Airbus Defence and Space SAS of the progress meetings calendar

with his own lower-tier subcontractors. Airbus Defence and Space SAS may decide to attend such

meetings.


The contractor shall provide in all cases minutes of meeting for reviews at unit level or SW level

with low tier subcontractors.


Airbus Defence and Space SAS shall be allowed to audit the Contractor to ensure its compliance

with the management, technical and PA requirements. The Contractor shall audit his Lower Tier

Subcontractors to ensure their compliance with the requirements. Airbus Defence and Space SAS

shall be notified of the Contractor’s intention to audit a Lower Tier Subcontractor by Fax or E-mail.

The Contractor shall produce an audit report one month after audit.


The Contractor shall authorize the attendance of Airbus Defence and Space SAS final customers

(CGS, Astrium Defence and space GmbH, ESA) to any meeting where Airbus Defence and Space

SAS participates,



Date:24/09/2014


4.1.3 Reviews


The Contractor shall hold the reviews defined in chapter 3.7 and reminded in the following table:

EQUIPMENT

CATEGORY RR EQSR PDR CDR QR

A x x

B x x x(1)

C x x x x

D x x x x

(1) Review of minor design changes (if any) documented by the delta-design/delta-analysis

documentation and review of the delta-qualification test results

4.1.4 Risk management


A risk assessment and mitigation plan shall be issued by the Contractor and updated on a regular

basis as stipulated in ECSS-M-ST-80. The subcontractor must identify all risks on technical,

management, quality, development manufacturing and testing aspects. The impact of each risk

must be assessed and mitigation actions must be proposed for all risks categorised as “medium” or

“high” (low probability x high impact - medium probability x medium impact - high probability x low

impact). Risk monitoring & control shall be implemented with a list of actions and reference

schedule. This shall be done in a continuous manner until the end of the project.

4.1.5 Schedule control


A reference schedule shall be established to represent all the tasks to be carried out by the

Contractor and the associated inputs/outputs. The Contractor shall also identify the key milestones

of the development and production phases. The project contractual milestones must be clearly

identified in the schedule: (i) kick off, (ii) reviews, (iii) models delivery. The critical path of the

schedule must be highlighted and explained.



Date:24/09/2014



Any change of the Contractor reference schedule affecting the milestones must be submitted to

Airbus Defence and Space SAS for approval.

The Contractor shall notify Airbus Defence and Space SAS within 2 working days of any change in

the schedule affecting a contractual milestone.


The Contractor shall maintain a current schedule and include this schedule in its progress report.

The Contractor project manager, on behalf of his company, shall formally endorse the content of

the progress report.

4.1.6 Cost control


The Contractor shall propose and agree with Airbus Defence and Space SAS a Milestones and

Payment Plan for him and his Subcontractors (if any) for the work under the Contract.


The Contractor shall certify achievement of milestones before patment.


The Contractor shall follow the formal change procedures for any change of the cost baseline and

update when relevant the Milestones and Payment Plan.


Costs shall be structured and justified according to standard Cost Breakdown Structure (hours

number/hour rate/expenses /profit…) . This will be applied according to WBS tasks and also for

modifications.



Date:24/09/2014



A financial report shall be provided on a 6 weeks frequency basis associated with the progress

report it will cover as a minimum invoices status, update of payment milestones as necessary,

status of Change Request (CR) and Change Notification (CN).

4.1.7 Change control


The contractor shall implement an effective change control management. The change control

procedure shall be agreed by Airbus Defence and Space SAS project contract and configuration

manager (use of in-house standard procedure and forms are preferred as long as complete topics

and information are included).


Change classification: the Contractor shall implement the classification to be used for changes as

specified in the Contract. The classification defines the responsibility of the participants to bear the

impacts in cost, schedule and technical performance.

4.1.7.1 Introduction of change


The Contractor shall acknowledge receipt of any Change Request (CR) from Airbus Defence and

Space SAS and submit a contract Change Proposal (CP) to Airbus Defence and Space SAS within

15 working days of the issue of the request by Airbus Defence and Space SAS. Except specific

request the minimum validity for CP shall be 4 months.


The Contractor shall also submit a Change Proposal (CP) to Airbus Defence and Space SAS

immediately when a change is anticipated that may have an influence on the contract itself or any

contractually agreed item.



Date:24/09/2014



The form which will support the CP shall be approved by Airbus Defence and Space SAS(in house

forms can be accepted if complete information is provided).

4.1.7.2 Review and approval of change:


Change review boards (CRB) may be requested by the Contractor and/or Airbus Defence and Space SAS on a case by case basis to review and make fast decision on the on-going changes. The Contractor shall maintain up to date the log of all its changes and make it available to Airbus Defence and Space SAS and its own Subcontractors or Contractors (if any). Airbus Defence and Space SAS may invite final customer (CGS, Airbus Defence and Space GmbH, ESA) representatives to CRB concerning major changes.

All submitted CP shall be reviewed by Airbus Defence and Space SAS and processed during CRB meeting

Signature by both parties of Change Proposal (CP) formalises the contact change and authorises the change implementation, and the term and conditions of contract shall be modified accordingly

In special cases Airbus Defence and Space SAS may instruct the contractor to introduce a change before the change has not been formally processed, through delivery by Airbus Defence and Space SAS of an Authorisation To Proceed (ATP).

After change approval the Contractor (and his subcontractors) shall implement the change without delay, the Contractor shall formally notify all its potential Subcontractors or Contractors of the agreed change definitions.


The Contractor shall propose to and agree with Airbus Defence and Space SAS the procedures to

be used for processing each class of change. As a general rule :

All changes without impact on the contractual documentation (Specifications and interfaces, GSOW, User manual, Contract) shall be processed according to Contractor internal procedures for changes. Information and full visibility shall be provided to Airbus Defence and Space SAS so that "the no impact status at spacecraft level" is reassessed. Airbus Defence and Space SAS shall have the right (within 2 weeks) to request formal agreement of the change at its level.

All changes affecting contractual documentation and milestones shall be agreed with Airbus Defence and Space SAS and processed accordingly

Any changes in the approved baseline of the boards (PCB, MPCB) , e.g any addition, deletion/replacement or modification in DCL, DPL shall be submitted for approval.

Any change to the qualified unit baseline shall be thoroughly analysed by the Contractor and



Date:24/09/2014


reported to Airbus Defence and Space SAS with a justification for the change and an assessment of the impacts on the qualification status

4.1.7.3 Non Conformances


The Non Conformances are defined and shall be managed according to ECSS-Q-20-09 and the

applicable PA requirements (AD14b).

4.1.8 Configuration control, information and documentation management

4.1.8.1 Configuration management (ECSS M-40A)


The Contractor shall perform configuration management and control tasks in coherence with ECSS

M-40A

Reuse in house configuration management plan and procedure is recommended as long as ECCS

M-40A is respected. The configuration management plan, list of Configured Items (CI), the list and

content of configuration baselines, the CIDL content, the ABCL content, the EIDP content, the DIL

content shall be described in management documents and are subject to Airbus Defence and

Space SAS agreement.

Configured items (HW and SW) must be marked according to Airbus Defence and Space SAS

requirements.

EMs, EQM must be configured at FM standard.

4.1.8.2 Information & Documentation/data management ECSS-M-50 A


For “off the shelf” unit, maximum reuse of existing documentation is recommended. The

subcontractor shall demonstrate that its documentation cover the content of deliverable

documentation specified in this GSOW. Any discrepancy shall be approved by Airbus Defence and

Space SAS.



Date:24/09/2014



The Contractor shall describe the process and responsibilities to manage the information,

documentation and data, supporting tools. The project information and documentation plan shall be

subject to Airbus Defence and Space SAS agreement.

The documentation should be marked “CONFIDENTIAL” if necessary to protect Airbus Defence

and Space SAS and its customer proprietary information.

An index of all deliverable documents (Document Delivery List - DDL, see section 5.1) shall be

established by the Contractor and agreed by Airbus DS SAS.

The DDL shall be kept up to date under configuration control. Any change of the agreed DDL and

document deliveries shall be approved by Airbus DS SAS and shall follow the change procedure.

Controlled documents, i.e. deliverable documents identified in the CIDL for a Configuration Item,

shall be included in the DDL.

The Contractor shall agree with Airbus DS SAS the procedures and standards for classification of

documents, numbering and identification, distribution, format and contents, class of documents.

The document reference shall be : MOS-TYP-ORG-EEE-NNNNN where TYP is the document type,

ORG is the company code, EEE is the product code as provided by Airbus DS SAS, and NNNNN

is a sequential number.

All documents listed in the DDL shall be made available to Airbus DS SAS in electronic format.


The Contractor shall provide the documentation in original electronic form.

The Contractor shall store all documentation related to the unit during 20 years.

4.1.9 Process Control


The subcontractor shall submit for approval a Declared Process List as required in the Product

Assurance Requirements, indicating all processes used in the equipment, including processes of

Lower Tier Subcontractors.


Changes to the processes listed in the Declared Process List by addition, deletion, replacement or

modification of the Process Identification Document shall be submitted to the Change Notice and

Change Control process.



Date:24/09/2014


4.1.10 Logistics and inventory


The Contractor shall develop and agree with Airbus Defence and Space SAS the logistics and

transportation methods to use. The agreed method shall be kept up to date, any change being

subject to Airbus Defence and Space SAS agreement.


The Contractor shall regularly report to Airbus Defence and Space SAS on a yearly basis an

inventory list of all property according to an inventory control procedure to be agreed with Airbus

Defence and Space SAS.



Date:24/09/2014


4.2 Product Assurance Requirements and Tasks


The Contractor shall perform all tasks in response to the product assurance requirements detailed

in AD14b. The contractor shall provide a PA plan to answer requirements

4.3 Engineering


The Contractor shall perform all studies, analyses, simulations and testing necessary to

demonstrate the unit conformance with the specified requirements (AD0, AD14b & AD13f) over the

mission lifetime and environments.

The Contractor shall demonstrate that

The unit design conforms to the requirements (design qualification verification),

The flight items conform to the qualified design, are free of materials and/or workmanship deficiencies, and will function within the specified operational conditions.

The verification program shall verify that any individual specified requirement is fulfilled, either by

test, or by analysis, or by similarity, or by a combination of any of these methods,

MOS-GSOW-4305 New

In addition, all the associated design provisions and constraints, including required test pieces and

reference coupons which are necessary to support the long term storage implementation, and

subsequent destorage validation activities for the recurrent models shall be fully established in

conjunction with the detailed storage and destorage requirements.

MOS-GSOW-4306 New

The Contractor shall perform the definition of the concept for the maintenance of the unit over the

programme duration (including storage phases). The unit shall be designed in order to allow its

maintenance once integrated onto the RFA or instrument or satellitewithout having to switch ON

the complete RFA or instrument or satellite.

The Engineering and Verification tasks requested within this Section shall be understood as the

minimum tasks the Contractor shall fulfil but these are not exclusive to the other tasks the Contractor

shall do in order to fulfil its obligations.



Date:24/09/2014


4.3.1 Architecture & Configuration


The Contractor shall complete the design of the Unit and associated Ground Support equipment,

inclusive of all means necessary for developing and verifying it and ensuring the capability of the

end product to fulfil the specified requirements over the mission lifetime and environments.

The description of the unit design and associated justification shall be documented in the Unit

Definition and Justification file which shall contain as a minimum :

A concise description of the unit technical baseline, recalling major functions and characteristics and budgets,

A detailed description in terms of functions, assemblies interfaces, characteristics, performances, drawing, ... including the unit itself and associated GSE (if any),

Design justification as necessary.

This document shall be maintained in order to reflect the actual status of the unit. In addition to the

planned updates required for the design reviews, this file shall be updated following each major

design change and when a number of minor changes have been accumulated.

4.3.2 Analyses, Design & Development


The Contractor shall perform or re-use all analyses and trade studies necessary to ensure that the

chosen design concept will meet the requirements contained in the applicable specifications in the

most cost effective manner and at an acceptable development risk.

The Contractor shall use its analyses as formal inputs for the unit qualification verification. All

analyses data shall be documented properly and shall be part of the verification documentation.

Mathematical models and software tools necessary to complete these tasks shall be developed,

unless commercially available.

MOS-GSOW-4325 New

The Contractor shall clearly identify and assess critical aspects of subsystems and equipments that

are considered potential driving aspects of the unit performance requirements. The Contractor shall

identify and define the need of any special design features required by the unit to ensure

compatibility with the RFA or instrument or satellite AIT, the launch preparation and long term

storage requirements, maintain stringent cleanliness requirements and facilitate dedicated purging,

where applicable.



Date:24/09/2014


4.3.3 Hardware/software compatibility


The Contractor shall perform all necessary activities at unit level to ensure compatibility of HW and

SW (if any)

4.3.4 Thermal design


The Contractor shall be responsible for qualifying the unit wrt environmental requirements given in

AD0 and AD13f in carrying the following thermal activities :

Thermal design

Detailed thermal mathematical model

Thermal analyses

Definition of thermal interface

Definition of thermal budgets

4.3.5 Mechanical engineering


The Contractor shall define the overall physical configuration of his unit.

The design solution shall cover the structural/mechanical integrity, manufacturing, operations

accessibility and maintenance in compliance with relevant requirements (AD0)

The Contractor shall perform all necessary analyses and test to verify the mechanical/structural

conformity with requirements.

Mounting shall be verified by fail safe analysis.

The Contractor shall perform dynamic analyses.

The Contractor shall perform qualification and acceptance testing according to unit specification

and relevant applicable documents of this GSOW.



Date:24/09/2014


4.3.6 Contamination


The Contractor shall ensure that the unit design avoid any potential contamination (material

selection, design and cleanliness procedures) in accordance with applicable documents. The

Contractor shall identify all sources of contamination including outgassing /off gassing.

The Contractor shall identify all parts of the unit which may be sensitive to contamination together

with associated impacts.

4.3.7 Detailed electrical design and EEE engineering


Technical meetings shall be organised to review the detailed design as soon as available ,if

necessary. They might be combined with progress meeting.

Unit detailed drawings and their associated parts list must also be available, with a description of

the unit internal design. This will include the hybrids electrical drawings and associated parts list.

The Contractor shall provide the customer with ASIC or PFGA specifications.

MOS-GSOW-4371 New

The Contractor shall perform all analyses and trade-off studies necessary to ensure that the

chosen electrical design will meet the requirements and provide necessary margins and adjustment

capability considering ageing of components (lower power levels, etc.).

4.3.8 Electromagnetic compatibility (EMC)


The Contractor shall be responsible for Unit EMC compatibility with respect to the requirement

defined in AD13f.

The EMC control approach at Unit level shall include the following steps :

Analyse/maintain the applicability and compliance EMC and power quality requirements,

Investigate specific EMC aspects, identify critical areas and determine EMC environment by analysis

Detail grounding & bonding solutions,

Perform EMC testing on the unit.

The Contractor shall be responsible for qualifying the unit wrt EMC environment requirements.



Date:24/09/2014


4.3.9 Interfaces management


The Contractor shall provide the following data in documents (ICD) and electronic format (refer to

AD13f).

Measurement & command list including information on source, destination, conditioning, accuracy, calibration, etc ...,

EICD, including pin allocation & connector list as well as TM/TC description

Mechanical and thermal ICD, including detailed interface drawings and key mechanical and thermal parameters

4.3.10 RAMS (Reliability/ Availability / Maintainability / Safety)


The Contractor shall implement and maintain a RAMS programme depending on the category of its

product, according to the RAMS management requirements expressed in documents (AD14b) and

according to RAMS technical requirements expressed in documents (AD0) and (AD13f).



Date:24/09/2014


4.4 Embedded software (if any)

4.4.1 General

This chapter is applicable for all software embedded in the equipment. It includes on-board software

running in any sub-systems, including firmware.


All software production and test shall follow the requirements of AD14b based on the application of

the ECSS standards.

Reuse of existing software shall be made in accordance with the requirements of AD14b.

All on-board software running in the Spacecraft subsystems shall be developed using the same

development environment, except where explicitly exempted.

The on-board software shall be developed using a high-level language, except where explicitly

exempted.


The on-board software shall be deliverable to Airbus Defence and Space SAS.

4.4.2 Deliveries


Any software procured or developed under the contract shall be delivered.

All deliverable software shall be fully tested and documented.

The Contractor shall deliver software data packages during the development in accordance with

ECSS.


All on-board software shall be delivered in source form, including all building scripts necessary to

regenerate the on-board image. This shall also apply to reused software.



Date:24/09/2014



The delivered software and support information shall include :

complete source code and listings,

target processor executable image,

link cross-reference listings,

software maintenance environnement,

all relevant documentation.


If the software developed under the contract is embedded in or relies upon another software

product, the Contractor shall offer to Airbus Defence and Space SAS and final customers (CGS,

Airbus Defence and Space GmbH, ESA) the option for a license to use the supporting product if it

is not commonly available.

4.4.3 Verification


The Contractor shall validate and qualify the equipment software on a flight representative model.

The intermediate models shall be equipped with the flight version of the software, unless versioning

is preliminarily agreed with Airbus Defence and Space SAS.


Any software upgrade shall be possible on the delivered models without the need to ship back the

unit to the Contractor.


All software which are critical for Spacecraft safety and/or mission shall be verified by an

Independent Software Verification (ISV) team different from the software Contractor.

A software is herein classified as :

safety critical, if a misbehaviour of it would cause the loss of the spacecraft,



Date:24/09/2014


mission critical, if a misbehaviour of it would cause an unacceptable impact on the mission (loss of the scientific mission or unavailability drastically affecting the science return).

The software and its support information shall be made available to the Independent Software

Verification (ISV) Contractor in order to allow him to perform the independent verification activity.

When applicable, the Contractor shall take into account the ISV activity in order to properly phase it

with its own software development.

The outcomes of the ISV, as approved by Airbus Defence and Space SAS, shall be made

applicable as part of the contract.

4.4.4 Maintainability


The Contractor shall be responsible for the on-board software maintenance until the end of the last

Spacecraft commissioning. The Contractor shall take into account the Long Term Storage

requirements (refer to §3.4.1 and § 3.5).


The software maintenance environment shall provide the means to generate and prepare software

patches or full images and associated checksums for uplink to the Spacecraft.

Post-launch modifications of all the on-board software shall be possible.

The on-board software shall be fully patchable and dump-able without any restriction.


The on-board software shall be re-programmable on ground and in orbit without any restriction with

the exception of PROMs.



Date:24/09/2014


4.5 Implementation & verification


The Contractor shall undertake all manufacturing and testing activities necessary to deliver the end

items according to applicable documents.

The Contractor shall define, manufacture, make available or procure all specific jigs, tools and test

unit or facilities necessary for the manufacturing, assembly, handling, testing, storage, and

transport of the end items.

The Contractor shall develop and validate all software necessary for the development and testing

of the unit.

The Implementation Tasks requested within this section shall be understood as the minimum tasks

the Contractor shall fulfil but these are not exclusive to the other tasks the Contractor shall do in order

to fulfil its obligations.

4.5.1 Development and verification plan


The Contractor shall generate, maintain and implement a development and verification plan

defining all activities necessary to achieve the complete unit development as specified in this

GSOW.

The Development and verification plan shall include :

Development and verification logic and description of activities (engineering, procurement, MAIT and verification) of the product / a MAIT plan shall be included

Bar charts, milestones & review activities

Long lead items procurements and parts procurement

Model and test philosophy

Interfaces management

Delivery schedule

Customer undertakings

The unit development and verification plan shall be sufficiently complete and self-contained to

demonstrate the programme feasibility within specified schedule.

Adequate margins shall be integrated in the development plan.



Date:24/09/2014


4.5.2 Manufacturing, Assembly, Integration , Verification and Testing


The Contractor shall define and implement the manufacturing assembly, integration and verification

programme for the unit in compliance with the list of deliverable items defined in chapter 4 and

associated schedule requirements.


Before delivery, the models shall be submitted to the following tests:

EM shall be submitted to functional, electrical and performances tests to demonstrate the unit behaviour (see AD0 and AD13f). Compatibility of the EM with thermal vacuum testing shall also be considered allowing usage during Instrument level thermal tests.

E(Q)M model shall be submitted to qualification tests, according to this GSOW and AD0 & AD13f requirements

PFM models shall be submitted to proto-qualification tests, according to this GSOW and AD0 & AD13f requirements.

FM models shall be submitted to acceptance tests as defined in this GSOW and AD0 & AD13f requirements.


The Verification and Qualification and Acceptance tests to be performed shall include the tests as

listed in AD0. This list and development models (EM, EQM, PFM, FM) may be tailored with the

approval of Airbus Defence and Space SAS depending on the category and maturity of each unit.



Date:24/09/2014


4.6

4.6

4.6

4.6

4.6

4.6

4.6

4.6

4.6

4.6



Date:24/09/2014


4.6 Requirement on Deliveries

4.6.1 Deliverable Items

Hardware and software


The Contractor shall deliver the end items in the quantity, at the required need dates, and at the

place of delivery specified in the Specific Statement of Work.

The hardware and software shall be delivered with their associated documentation and Ground

Support Unit as specified hereafter.

Ground Support Equipment


Ground Support Equipment (GSE) necessary to transport, protect, store, handle and integrate the

unit within the spacecraft must be delivered. In particular, the Contractor shall deliver the hardware

items in appropriate reusable containers, with a full set of connector savers.


When the unit includes a processor or a programmable unit, all necessary software which are

required for its set-up, check-out and operation shall be delivered with the hardware.


The Contractor shall establish and describe the list of delivered GSE he proposes with each of the

delivered unit model.

All deliverable GSE (if any) shall be delivered with their supporting documentation, in particular the

user manual and ICD.


The deliverable GSE shall be subject to the same guarantee clauses as the flight hardware in

accordance with the contract terms and conditions.



Date:24/09/2014


Items procured or manufactured under the contract


GSE (hardware and software) which were procured under the contract but not delivered with the

flight hardware and software shall be treated in accordance with the following terms.

All items procured or manufactured which have been paid for under the contract shall be the

property of Airbus Defence and Space SAS or its customer at the closure of the contract. Such

items include EEE parts, tools, test unit, spare items, or any other items, which have been

produced and paid for under the contract, but which may not delivered at the time of the contract

closure. These items shall be recorded in the inventory list of the Contractor. For such items,

Airbus Defence and Space SAS, will specify later the disposal conditions.



Date:24/09/2014


4.6.2 Acceptance procedure

Pre delivery Acceptance tests


Pre-delivery acceptance tests shall take place at Contractor’s premises. Airbus Defence and Space

SAS, potentially accompanied by its customers (CGS, Airbus Defence and Space GmbH, ESA)

representatives, shall be invited to attend to the pre-delivery acceptance tests. The pre-delivery

acceptance tests schedule shall be communicated to Airbus Defence and Space SAS 15 calendar

days and confirmed 5 working days prior to the beginning. Airbus Defence and Space SAS shall

inform the Contractor about Airbus Defence and Space SAS or its customer (CGS, Airbus Defence

and Space GmbH, ESA) participation.

Delivery Review Board (DRB) and Consent to ship.


A DRB shall be organised at the Contractor’s premises after completion of the Pre-Delivery

Acceptance tests. The DRB schedule shall be communicated 15 calendar days ant confirmed 5

working days prior to the beginning of the review. During this meeting, the results of the pre-

delivery acceptance tests shall be submitted to review to Airbus Defence and Space SAS and the

EIDP shall be examined. At the DRB the delivery status of the unit shall be checked: list of

deliverables, Non Conformances, visual inspection. The DRB shall be judged successful and the

consent to ship the unit shall be given by Airbus Defence and Space SAS, based on the conformity

of the unit to the applicable documentation, on completeness of the deliverable documentation, and

after unit visual inspection. In case of unsuccessful DRB, actions shall be taken by the Contractor

to correct the situation and the consent to ship shall be delayed until action completion.

Consent to ship


The Shipping of the unit shall be done only and after the consent to ship of the unit is given to the

Contractor by Airbus Defence and Space SAS.

The completion of the following shall be considered for the formal consent to ship:

Pre-delivery acceptance test results are checked and approved during the formal DRB.

All major actions issued during the DRB are closed

Airbus Defence and Space SAS has checked and approved the unit EIDP.



Date:24/09/2014


Incoming inspection and final acceptance.


All delivered hardware shall be subjected upon their receipt to a short incoming inspection, at the

delivery point, to check the transport conditions. The conclusions of the incoming inspection shall

be notified by Airbus Defence and Space SAS to the Contractor within 15 days following receipt of

the hardware by Airbus Defence and Space SAS.

Acceptance of the deliverable hardware shall be deemed to have occurred when:

All deliverable and associated documentation are received at the specified point of delivery.

The unit incoming inspection including potential functional tests is successfully performed at the formal point of delivery.

Rejection and re-delivery


In case of unsuccessful incoming inspection, the rejected unit shall be considered as a non delivery

and shall be returned to the Contractor’s address at Contractor risks and expenses after due

notification by Airbus Defence and Space SAS. Any unit which is returned to the seller for repair or

modification shall be subject to the above acceptance procedure upon redelivery.

This unit shall be returned by the Contractor to Airbus Defence and Space SAS at the specified

delivery location. If Airbus Defence and Space SAS requests an alternate delivery location, the

delivery costs shall be under the responsibility of the Contractor.

4.6.3 Transport, storage, insurance, customs


The Contractor shall be responsible for the transport and insurance of the deliverable items

together with their associated documentation and the necessary shipping documents up to the

Airbus Defence and Space SAS or any other TBD premises in Europe or to the launch site in case

of a specific need or request regarding the equipment prior to launch (late retrofit, model

replacement..).

The Contractor shall develop and agree with Airbus Defence and Space SAS the logistics and

transportation methods to use in accordance with the rules presented below. The agreed method

shall be kept up to date, any change being subject to Airbus Defence and Space SAS agreement.



Date:24/09/2014


Detailed rules to follow are the following:

a) General transport

Definition

Dedicated Transport: Dedicated transport means door to door pick-up, dedicated vehicle for road

transportation (no grouping, except possibly with other Airbus Defence and Space SAS or Airbus

Group items), and delivery of the equipment by the accountable person from the transportation

company. In case handling operations during transport and/or change of transportation mode

(road, air, sea and/or river) are necessary, the accountable person from the transportation

company shall be requested to monitor all intermediate hand-over and handling stages.

Flight Equipment

All flight equipment shall be transported by dedicated transport.

Ground Equipment

Only equipment combining the following characteristics can be transported by integrators (DHL,

UPS, Fedex, others):

• Dimensions smaller than 1 m x 0.5 m x 0.5 m

• Weight lighter than 50 kg

• Value less than 50 kEUR

All other equipment have to be transported by dedicated transports

b) Critical transport


For critical transport of flight or ground equipment meeting one of the criteria listed hereafter, a

transport risk analysis/FMEA shall be performed by the Contractor if contractually responsible for

the transport of the Equipment to the delivery location.

Expensive equipment (the value exceeds the insurance of the haulier)

Specific transport requirement (e.g. customer, military programmes)

Oversized container (exceeding the transport envelope with respect to applicable local transport regulations)

Sensitiveness of the transported equipment to environmental conditions (e.g. temperature, humidity, shocks, contamination)

Equipment requiring special maintenance or monitoring activities during transportation

Schedule critical equipment

This transport FMEA shall conclude on the need or not for specific transport requirements

(including escort) and shall be delivered to Airbus Defence and Space SAS, for review.

As a minimum, for ground equipment meeting one of the above criteria, a dedicated transport shall

be selected. Whenever possible, the use of several means of transportation shall also be avoided

so as to minimize the number of hand-over and handling operations during transport.



Date:24/09/2014


c) Escort


All oversized containers (exceeding the transport envelope with respect to applicable local

transport regulations) shall be escorted by the Contractor if contractually responsible for the

transport of the Equipment to the delivery location.

On a case by case basis, escort requirements may also be specified in the Supply Contract for

specific types of equipment, even when not leading to the transport of oversized containers.

Typical list of Hardware to be escorted (regardless of size):

Satellite structures,

Solar Generators,

Large antennae,,

Propulsion modules.

It is the Contractor’s responsibility to derive the appropriate requirements for transport and storage

and have them implemented up to the place of delivery to Airbus Defence and Space SAS.


The Contractor shall provide the shipping containers with the appropriate packing to protect the unit

from the environment conditions experienced during transit or storage. The transport container

shall allow transport of the equipment by road, rail, airplane and ship. Environmental indicators

(shock detectors mandatory, temperature/humidity/shock recorders or others if required from the

FMEA) shall be provided, set and fitted to the product/container prior to shipment..


The Contractor shall be responsible for compliance with the applicable export regulations, and he

shall fulfil the customs formalities.



Date:24/09/2014



Identification label shall be marked before delivery in a permanent way on each deliverable.

Packaging shall be done according to the applicable regulations. All packages labelling shall be in

English language. Packaging ships and containers shall be marked with the following information:

Unit name / Configuration item number with serial number

Content and quantity

Gross and net mass in Kg

Contract number

Contractor name and address

FRAGILE label, in red.

Presence of chemical or dangerous products (if any)

ITAR, if the equipment is not ITAR free

ESD sensitive, if applicable

Following label: “Open only in-clean room area by qualified operators”


The Contractor shall notify Airbus Defence and Space SAS of the pending shipment 3 working

days prior to the actual shipment date, and the advice of dispatch shall contain all the necessary

information ( contract reference, quantity and description of goods, package number, air flight

number, air way bill number, customs proforma invoice, etc…). The Contractor shall be able to

give, at any time, information concerning the location of the deliverable and expected delivery time.

4.6.4 Deliverable Mathematical Models


Mathematical models representative of the unit performance to be provided by the Contractor (see

chapter 5) shall be as representative as possible of the performances and finally correlated with

test results. The mathematical models shall be delivered according to software requirements,

modelling requirements, numbering requirements and integrity checks requirements specified in

the technical documentation. All mathematical models shall be delivered with the associated

documentation allowing their use and integration by Airbus Defence and Space SAS for analyses

and simulations. Depending on the unit complexity, the mathematical models may be limited to a

set of technical and performance data as agreed with Airbus Defence and Space SAS.



Date:24/09/2014


4.6.5 Documentation

The deliverable documentation is listed in section 5. In particular, the contractually controlled

documents are specified therein. The Contractor shall derive the list of documents he intends to

deliver from this generic list of deliverable documents.

Maximum re-use of existing documentation shall be proposed by the Contractor if the unit is derived

from an existing unit. In that respect the list given section 5 may be superseded by Contractor existing

documents. It is Contractor’s responsibility to propose and justify that the contents of its proposed

documents are compatible with Airbus Defence and Space SAS request in section 5.

In order to minimise the documentation management effort, the Contractor may propose to Airbus

Defence and Space SAS not to deliver all the documents specified in section 5 but to provide a

summary for some of them and make the complete corresponding document and details accessible at

Contractor’s premises. Gathering several documents into a single one is also acceptable provided

that the required information is given.

It shall be understood that other documents not mentioned in section 5, either of minor importance, or

for justification purposes, or in case of problems, may have to be produced by the Contractor and

delivered (or being accessible) to Airbus Defence and Space SAS.

Notwithstanding the dates indicated for delivery, all documents shall be updated as necessary and

according to the changes introduced to reflect the up to date status of the unit.

4.6.6 Warranty

The warranty for all deliverable Items shall be as defined in the contract.



Date:24/09/2014


4.7 Export Control

Use of ITAR components shall be minimized or avoided as far as possible. In case ITAR components

are necessary the Contractor shall follow the following directives:

4.7.1 General


The Contractor shall be responsible for ensuring compliance with the applicable export control

requirements, in particular those of the Government of the United States of America regarding

exportation or re-exportation of goods and / or materials in case of U.S. procurements.

The Contractor shall be responsible for obtaining any necessary export licence or approval from

the governmental authorities and shall ensure that he has covered all potential countries of

subsequent onward export. The Contractor shall bear the associated risks in case of non-

attribution.

The export control document shall collect the required information (list, status about ITAR/EAR,

governmental licence, non-ITAR certificates, copy of licences, …).

For the US imported items which are not requiring an export licence , a formal written certificate

approved at management level , shall be supplied by the contractor and joined to the unit EIDP :

this certificate shall warranty that the different US items present in the delivered unit and duly listed

in the certificate are export licence free .

An exhaustive status on the export licences shall be given by the contactor at each main review of

the unit ( PDR, CDR, EQSR, TRR , DRB ..)

4.7.2 Direct U.S. Procurements


When the Contractor is a direct U.S. Contractor to Airbus Defence and Space SAS , the Contractor

shall undertake :

To draft the documentation which has to be prepared to make the application to the Department Of State (DOS),

To send it to Airbus Defence and Space SAS for review before submission,

To prepare the final issue and submit it in due time to the DOS,

To inform Airbus Defence and Space SAS about the status of the application (preparation, submission, staffing, authorisation, provisos)

To provide Airbus Defence and Space SAS with the DOS authorisation, the complete text of authorisation and the provisos,

To identify the technical data, information, documentation, and hardware which are exported in the frame of the authorised agreement or export licence, as required by the ITAR regulations.



Date:24/09/2014


4.7.3 Lower tier U.S. Procurements


When the Contractor has subcontract(s) with U.S. Contractors, the Contractor shall apply the same

rules towards his own subcontractors. The Contractor shall :

Provide a copy of his own control plan to Airbus Defence and Space SAS,

Flow down the export control requirements to his subcontractors,

Ensure the proper execution of the export control requirements throughout the subcontracting chain,

Ensure that the authorisations will include the higher level customers and destination,

Inform and report to Airbus Defence and Space SAS on the applicability and progress status,

Provide copies of all relevant documentation and authorisations to Airbus Defence and Space SAS

4.7.4 European Union And National Export Restrictions


The Contractor shall take all steps that are necessary to ensure compliance with European export

requirements. This includes the rating of all hardware and documentation to identify its presence

(or not) on the Dual Use List of controlled hardware and technologies. If the technology or

hardware is positively rated, the Contractor is responsible for ensuring that the correct export

licences (or waivers, as appropriate) are in place to ensure the lawful shipment to Airbus Defence

and Space SAS by the Contractor and to permit Airbus Defence and Space SAS to lawfully re-ship

the products according to the needs of the project.



Date:24/09/2014


4.8 Health and environmental protection


The contractor activity shall comply with the REACH regulation.

REACH (Registration, Evaluation, Authorisation and Restriction of Chemical substances) is the

applicable European Community Regulation on chemicals and their safe use (see regulation EC

1907/2006).

4.9 Post Delivery Activities and Maintenance activities


The Contractor shall undertake all the post-delivery activities as required in the specific SoW (AD0)

to support Airbus Defence and Space SAS in the performance of system and AIT tasks. This shall

cover AIT support during RFAs and instruments and satellites tests, launch campaign support

tasks when required and post launch support in case expertise (on call) is required.


The maintenance approach shall provide ability to manufacture, investigate and repair any

equipment until launch of the last satellite and any GSE (including SW). Launch date of the last

satellite is scheduled in 2036.



Date:24/09/2014


5 DELIVERABLES

5.1 Deliverable documentation

The Deliverable Requirements List (DRL) defines in table 5.1.1 and table 5.1.2 the list of documents

to be delivered in phase C/D.

If the unit is existing or is derived from an existing unit, the Contractor may propose its Contractor

existing documentation, justifying that the contents of its proposed documents are compatible with the

required deliverable documents. Gathering several documents into a single one is also acceptable

provided that the required information is given.

It shall be understood that other documents not mentioned in this SOW, either of minor importance, or

for justification purposes, or in case of problems, may have to be produced by the Contractor and

delivered (or being accessible) to Airbus Defence and Space SAS.

Notwithstanding the dates indicated for delivery, all documents shall be updated as necessary and

according to the changes introduced or the comments received, to reflect the up to date status of the

unit.


Documents shall be delivered in electronically generated and native searchable PDF format, with

active file index table, generated using Adobe Acrobat or similar software.

On request (e.g. when portion of the document needs to be imported in Customer's

documentation), the Contractor shall also deliver the native version (Word, PowerPoint or Excel for

Windows) of the documents, e.g. for user manual.

Documentation shall be written in English.


Document shall be delivered by FTP server (or any collaborative means to be agreed by the

parties) to Airbus Defence and Space SAS. For each document delivery, a dispatch note shall be

sent to Airbus Defence and Space SAS project documentation office and Airbus Defence and

Space SAS contractor project interface. Mail can be used for informal and non sensitive information

only.

Further deliverable documentation may also be defined in the applicable PA and software

requirements documents.



Date:24/09/2014


Documents for reviews :


Review data packages shall be delivered to Airbus Defence and Space SAS by FTP server (or any

collaborative means to be agreed by the parties) and on 4 CD-ROMs. The number of electronic

copies on CD-ROMs may be increased in specific cases.

Data packages delivered for the reviews shall include the documents indicated for each review in the

tables hereafter and with the following codes :

KO = to be available at the KO

PDR = to be included in the Preliminary Design Review data package

CDR = to be included in the Critical Design Review data package

EQSR = to be included in the EQuipment Suitability Review data package

MRR = to be included in the Manufacturing Release Review data package

QR = to be included in the Qualification Review data package

TRR = to be included in the Test Readiness Review data package

DR = to be included in the Acceptance Data Package at delivery review

As NR = as necessary or as required


The review documentation and associated models shall be delivered to Airbus Defence and Space

SAS 10 working days before the review meeting.

APP = approval level :

A : to be approved ( the contractor cannot continue in its process without customer approval but

the customer approval in no way frees the contractor from his technical and contractual

obligations)

R : to be reviewed/agreed

I : for information

Ref numbering:

The management and PA deliverable documents are following the ESA reference numbering

applicable to other items at RFA / instrument / satellite level.

The numbering for other documents is dedicated to equipment management


Reference: MOS-SOW-ADST-MWI-1000002084 Issue: 1.0 Date:01/09/2014


5.1.1 Documentation for unit falling in category A or B

Management & Implementation Documents

The following table gives the list of management documents to be included in the data packages of the different reviews.

DRL N° Name of the documents to be included in the data packages RR EQSR / MRR

TRR DR Approval level

PM-01 Management Plans (including configuration & documentation plans) X A

PM-02 Progress Reports (including Schedule , Action item list , financial report, PA & Configuration status, major and minor Change status, …)

Every 6 weeks when situation is nominal. Frequency may be increased in case of

major problem

I

PM-03 Not Applicable

PM-04 Minutes of Meetings with meeting presentations X X X X A with Customer

PM-05 & 06 Not Applicable

PM-07 Inventory List X R

PM-08 Project Schedule X X X A

PM-09 Change Proposal CP within 15 working days after CR receipt

A

PM-10 Change Proposals Status List X X X X R

PM-11 Action Item Status List Database to be maintained by the Contractor consultable by the Customer

I


PM-13 Work Breakdown Structure A

PM-14 Work Package Description A

PM-15 Invoices Status List List maintained by the Supplier communicable to the Customer

I






PM-16 Milestone Payment Plan (MPP)

Update as required

A

PM-17,18 & 19 Not Applicable

PM-20 Configuration and Documentation Management Plan A

PM-21 Change Request As required A

PM-22 Contract Close-out At relevant last satellite in orbit A

PM-23 Request for derogation (RFD) and for Waiver (RFW) For any NC against applicable documents

(SOW, specification, GDIR and PA requirements).

A


PM-26 Configuration Item Data List (CIDL) + Detailed Deliverable Item List (DDIL) X X X X R

PM-27 Document Status List X X X X R

PM-28 Risk Assessment & Mitigation Plan X X R

PM-29 Risk Register X X X X R

PM-30 List of Acronyms and Abbreviations Updated as required I

PM-31 Export Control Document X X X R

PM-32 Development & Verification Plan X X A

PM-33 Compliance Matrix to GSOW X X A

PM-34 RFD and RFW Status List X X X I




Product Assurance Documents



PA-01 Product Assurance Plan, including component control plan X R

PA-01b Compliance Matrix to MetOp SG PA requirements X A

PA-02,03,04 Not Applicable

PA-05 Critical item list (with long lead item list) X X X R

PA-06 Non-conformance Report , including NCRs relative to qualification status from previous programmes

Shall be available on line on NCTS

R

PA-07 NCR Status List, including NCRs relative to qualification status from previous programmes X X X R

PA-08 Qualification Status List including subassembly/SW/components level X X X R

PA-09 MIP/KIP list X X X R

PA-10 Alerts Status List X X X R

PA-11 End Item Data Package, including lower tiers EIDPs 1 X R

PA-12 Not Applicable

PA-13 Cleanliness and contamination control plan X R

PA 13b Contamination justification file (analysis, tests, allocation, report,…) X X R


PA-15 Reliability / Availability prediction report X X R

PA-16 Failure Modes Effects Analysis X X R

PA-16b Process FMEA X X I

PA-17 Hazard analysis/safety data package, incl. GSE as necessary X X R


PA-19 Worst Case Analysis X X R




PA-20 Parts Approval Documents (PAD sheets), including all EEE justificative files (ITAR components justification, evaluation reports, storage/relife procedure)

X A

PA-21 Declared component list (DCL) X X X A

PA-22 Radiation analysis and test reports X X R

PA-23 Parts Stress Analysis X X R

PA-24 Request For Approval (materials and process) X A

PA-25 Declared Mechanical Parts List (DMPL) including lower tiers DMPL X X A

PA-26 Declared Material List (DML) including lower tiers DML X X A

PA-27 Declared Process List (DPL) including lower tiers DPL X X A

PA-28 & 29 Not Applicable

PA-30 SW PA Milestone report X R

PA-31 Software Product Assurance Plan (if applicable) X X R

PA-32 MPI/KIP reports X X I

PA-33 Certificate of conformance and declaration of conformity X I


PA-35 LogBook X I

PA-36 to 45 Not Applicable

PA-46 ASIC/FPGA Verification and Validation reports X X R


PA-50 ASIC/FPGA Burn In procedure and report X X R

The hardware configuration at delivery shall be indicated (i.e relays status, EEPROM status, …)




Engineering & Verification Documents

DRL N° Name of the documents to be included in the data packages RR EQSR / MRR TRR DR Approval level

EN-01 Product Definition File (Design Description, Lower level specs, Detailed Electrical Drawings and Budgets) and corresponding ICDs (Mechanical, Thermal and Electrical)

X X X R

EN-02 Hardware Software Interaction Analysis (only if software is involved) X X R

EN-03 HW/SW Interface Control Document 1 X X R

EN-04 Justification File and Analysis Report (Electrical, EMC, Thermal, Mechanical, Radiations, Performances, PSA, WCA, SW if any, TM/TC)

X R

EN-05 Equipment Qualification Report X X R

EN-06 Equipment Qualification test plan X X X A

EN-07 Verification Control Document X X R

EN-08 User Manual (software operations if any) 1 X X X R

EN-09 Compliance Matrix to the Technical Specifications (AD0 + AD13f) X X X A

EN-10 Electronic files with equipment data as specified in the TM/TC ICD X X X R

EN-11 ASIC and FPGA design & development documents X R

EN-12 Detailed mechanical and electrical drawings 2 X R

EN-13 Long Term Storage Plan X X A

EN-14 Equipment Design Considerations and Requirements for Long Term Storage X X A

1 Including for EM

2 Available at subcontractor premises




Manufacturing & Tests Documents

DRL N° Name of the documents to be included in the data packages EQSR / MRR TRR DR Approval

level

MT-01 Acceptance/qualification Test Plan X X R

MT-02 Test procedure X I

MT-03 Test Reports X R

MT-04 Detailed Deliverable Item List X X X R

MT-05 GSE Design Definition, FMECA & Safety Analysis, European Certification (including

EMC), Maintenance plan, Configuration, User manual and Long term storage approach.

X X X R




Software Documents (if applicable)

DRL N° Name of the documents to be included in the data packages 3 EQSR / MRR TRR DR Approval level

SW-01 Software System Specification (SSS) X R

SW-02 Software Requirements Specification (SRS) X X R

SW-03 Software development plan NA NA NA

SW-03 Software Design Document (SDD) X R

SW-04 Software Reuse file (SRF) X R

SW-05 Software Verification Plan X A

SW-06 Software Validation Plan X R

SW-07 Software Budget Report X R

SW-08 Software Validation Testing Specification (SVTS) X R

SW-09 Software Delivery X X R

SW-10 Software Configuration File (SCF) X R

SW-11 Software Release Document X X R

SW-12 Software User Manual X X R

3 This table identifies the major deliveries for the software documentation; the complete software documentation requirements of ECSS-E-40B and ECSS-Q-80B are applicable




5.1.2 Documentation for unit falling in category C or D

Management & Implementation Documents

The following table gives the list of management documents to be included in the data packages of the different reviews.

DRL N° Name of the documents to be included in the data packages RR PDR CDR QR MRR TRR DR Approval

level

PM-01 Management Plans (including configuration & documentation plans) X A

PM-02 Progress Reports (including Schedule , Action item list , financial report, PA & Configuration status, major and minor Change status, …)

Every 6 weeks when situation is nominal. Frequency may be increased in case of major problem

I


PM-04 Minutes of Meetings with meeting presentations X X X X X X X A with Customer


PM-07 Inventory List X R

PM-08 Project Schedule X X X X X X A

PM-09 Change Proposal CP within 15 working days after CR receipt A

PM-10 Change Proposals Status List X X X X X X X R

PM-11 Action Item Status List Database to be maintained by the Contractor consultable by the Customer

I


PM-13 Work Breakdown Structure A

PM-14 Work Package Description A

PM-15 Invoices Status List List maintained by the Supplier communicable to the Customer I

PM-16 Milestone Payment Plan (MPP) Update as required A





level

PM-17,18 & 19

Not Applicable

PM-20 Configuration and Documentation Management Plan A

PM-21 Change Request As required A

PM-22 Contract Close-out At relevant last satellite in orbit A

PM-23 Request for derogation (RFD) and for Waiver (RFW) For any NC against applicable documents (SOW, specification, GDIR and PA requirements).

A


PM-26 Configuration Item Data List (CIDL) + Detailed Deliverable Item List (DDIL) X X X X X X X R

PM-27 Document Status List X X X X X X X R

PM-28 Risk Assessment & Mitigation Plan X X X R

PM-29 Risk Register X X X X X X X R

PM-30 List of Acronyms and Abbreviations Updated as required I

PM-31 Export Control Document X X X X X X X R

PM-32 Development & Verification Plan X X X A

PM-33 Compliance Matrix to GSOW X A

PM-34 RFD/RFW Status List X X X X X I




Product Assurance Documents


level

PA-01 Product Assurance Plan, including component control plan X X R

PA-01b Compliance Matrix to PA requirements X X A


PA-03 Audit Plan X X I

PA-04 Audits check lists and reports X I

PA-05 Critical item list X X X X X X R

PA-06 Non-conformance Reports 24 hours after any major NC. To be available on line in

NCTS

R

PA-07 NCR Status List, including NCRs relative to qualification status from previous programmes if any

X X X X X X I

PA-08 Qualification Status List including subassembly/SW/components level X X X X X X R

PA-09 MIP/KIP list X X X R

PA-10 Alerts Status List X X X X R

PA-11 End Item Data Package, including lower tiers EIDPs 1 X A

PA-12 Long Lead Item List X X R

PA-13 Cleanliness and contamination control plan X X R

PA 13b Contamination justification file (analysis, tests, allocation, report,…) X X X X I


PA-15 Reliability / Availability prediction report X X X X R

PA-16 Failure Modes Effects Analysis X X X R





level

PA-16b Process FMEA X X R

PA-17 Hazard analysis/safety data package, incl. GSE as necessary X X X R


PA-19 Worst Case Analysis X X X X R

PA-20 Parts Approval Documents (PAD sheets), including all EEE justificative files (ITAR components justification, evaluation reports, storage/relife procedure)

X X X X X R

PA-21 Declared component list (DCL) X X X X X A

PA-22 Radiation analysis and test reports X X X X R

PA-23 Part Stress Analysis X X X X R

PA-24 Request For Approval (materials and process) X X X A

PA-25 Declared Mechanical Parts List (DMPL) including lower tiers DMPL X X X X R

PA-26 Declared Material List (DML) including lower tiers DML X X X X R

PA-27 Declared Process List (DPL) including lower tiers DPL X X X X R


PA-29 SW criticality Analysis Report X X X R

PA-30 SW PA Milestone Report X X X X R

PA-31 Software Product Assurance Plan (if applicable) X X X X A

PA-32 MPI/KIP reports X X X R

PA-33 Certificate of conformance and declaration of conformity X A


PA-35 LogBook X I






level

PA-40 ASIC/FPGA Control Plan X X R


PA-42 ASIC/FPGA Requirements Specification X X R

PA-43 ASIC/FPGA Verification Plan X X R

PA-44 ASIC/FPGA Verification report X R

PA-45 ASIC/FPGA validation Plan X X R

PA-46 ASIC/FPGA Validation report X R

PA-47 & 48 Not Applicable

PA-49 ASIC/FPGA burn-in procedure (also with PAD sheet) X X X R

PA-50 ASIC/FPGA Burn In procedure and report X X X X R

PA-51 Experience Summary Report X I

PA-52 Qualification plan and qualification reports for new materiel & processes X X X X R




Engineering & Verification Documents

DRL N° Name of the documents to be included in the data packages RR PDR CDR QR MMR TRR DR Approval level

EN-01 Product Definition File (Design Description, Lower level specs, Detailed Electrical Drawings and Budgets) and corresponding ICDs (Mechanical, Thermal and Electrical)

X X X X X R

EN-02 Hardware Software Interaction Analysis (only if software is involved)

X X X X R

EN-03 HW/SW Interface Control Document 4 X X X X R

EN-04 Justification File and Analysis Report (Electrical, EMC, Thermal, Mechanical, Performances, SW if any, TM/TC)

X X X R

EN-05 Design Qualification Report X X X R

EN-06 Equipment Qualification test plan X X X X X X A

EN-07 Verification Control Document X X X X X R

EN-08 User Manual (software operations if any) 1 X X X X X R

EN-09 Compliance Matrix to the Technical Specifications (AD0 + AD13f) X X X X X A

EN-10 Electronic files with equipment data as specified in the TM/TC ICD X X X X X R

EN-11 ASIC and FPGA design & development documents X X X R

EN-12 Detailed mechanical and electrical drawings 5 X X X R

EN-13 Long Term Storage Plan X X X X A

EN-14 Equipment Design Requirements and constraints for Long Term Storage

X X X X A

1 for all models

4 Including for EM

5 Available at subcontractor premises




Manufacturing & Tests Documents

DRL N° Name of the documents to be included in the data

packages

RR PDR CDR QR MMR TRR DR Approval

level

MT-01 Test Technical Specification X X X X X R

MT-02 Acceptance Test Plan X X X X X R

MT-03 Test procedures X X I

MT-04 Test Reports X X X R

MT-05 GSE Design Definition, FMECA & Safety Analysis,

European Certification (including EMC), Maintenance plan,

Configuration, User manual and Long term storage

approach.

X X X X R




Software Documents (if applicable)

DRL N° Name of the documents to be included in the data packages 6 SW-SRR SW-PDR SW-CDR SW-QR SW-AR Approval level

SW-01 Software System Specification (SSS) X R

SW-02 Software Requirements Specification (SRS) X R

SW-03 Software Development Plan X X X R

SW-04 Software Design Document (SDD) X X R

SW-05 Software Reuse file (SRF) X X X R

SW-06 Software Verification Plan X A

SW-07 Software Validation Plan X R

SW-08 Software Budget Report X X X X R

SW-09 Software Validation Testing Specification (SVTS) X X R

SW-10 Software Delivery X X R

SW-11 Software Configuration File (SCF) X X X X R

SW-12 Software Release Document X X R

6 This table identifies the major deliveries for the software documentation; the complete software documentation requirements of ECSS-E-40B and ECSS-Q-80B are applicable



Date:01/09/2014


5.2 Delivery of Mathematical Models

The models to be delivered are indicated in the following table.

Mathematical Model Versions

Delivery Date

Equip. Cat A or B Equip. Cat C or D

- CATIA 3D model

- Mechanical models or performance data (*)

preliminary

complete

correlated

Kick-off

EQSR

DRB

PDR

CDR

DRB

- Thermal models or performance

data (*)

preliminary

complete

correlated

Kick-off

EQSR

DRB

PDR

CDR

DRB

- Other specific models (**) preliminary

complete

correlated

Kick-off

EQSR

DRB

PDR

CDR

DRB

(*) depending on equipment characteristics or complexity: mechanical and thermal models if

required (see

AD13f), otherwise performance data

(**) other specific models: refer to the specific SOW

5.3 Delivery of ICD documentation and associated files

Format of all interface documents and associated files are defined in AD13f (URD). Details will be provided at unit Kick Off Meeting

Proposal PDR 3 months

after PDR

CDR DR

TM/TC interface (input to Satellite data base) V0 V1 V2 Vfinal

Electrical interfaces (EICD, including TM/TC) V0 V1 V2 Vfinal

Mechanical & Thermal interfaces (MICD/TICD) V0 V1 V2 Vfinal

DOCUMENT TYPE (EX : SPECIFICATION)


Date:01/09/2014


5.4 Delivery of Hardware, Software and GSE

Refer to the specific SOW (AD400).

In addition the witness lots defined in section 3.4.3 will also be delivered.



Date:01/09/2014


AIRBUS DS

AIRBUS DS

ESA

Instruments

Agullo J.M. Braun F. ftp site 3MI

Bayle F. Engelke S. Adams G.

Boué J. Fayard R. Barre H.

Brugnera E. Gessler L. Barsanti I.

Chinal E. Gotsmann M. Betto M. ICI

Clochet A. Hashagen V. Bordes Y.

Corradin P. Holzner M. Capova M.

Coste P. Hug J. Corpaccioli E.

Damilano P. Koenig W. D'Addio S. RO

Duquesne J.L. Kraft B. Erdmann M.

Durand C. Lau B. Garcia Rodriguez A.

Etienne C. Lebherz D. Goodey K.

Gajewski J.F. Leissle T. Kangas V. MWI

Gandrieau M.A. Moore C. Klein U.

Giacometto A. Müller J. Krenzer K.

Gillot B. Paul E. Loiselet M.

Goueffon Y. Riede M. Martin D. MWS

Herbin D. Schmidt H. Mason G. Masterson D.

Larue N. Schull U. Mourra O.

Le Henaff V. Schulte H. Oremus R.

Mangeret R. Stephan A. Ostergaard A. SCA

Mansour A.S. Streppel J. Perez Albinana A.

Mechin X. Timmermann J. Porciani M.

Mulet Y. Wiedermann G. Prol Padin E.

Orlhac J.C. Zaglauer A. Scolamiero L. IASI

Pawlak D.

Peltier S. DOC OFFICE

Pendaries M. CONF MGMT OFFICE

Peres P. EUMETSAT

Perreau P. ftp site

Richard X. Cohen M.

Rieu J.P.

Robert F.

Roques R.

Rousière M.

Seronie-Vivien J.

Tabart C.

Vlimant P.

Title: Generic Statement of Work for MWI RFA...

Documents

Transcript of Title: Generic Statement of Work for MWI RFA...