Issue : 01 Rev. : 01 AS250emits.sso.esa.int/emits-doc/ASTRIUMLIM/S5P_Harness/DIV...05/06/2008 First Issue 01/01 12/06/2008 All Editorials modifications AS250 Ref : DIV.SOW.00016.T.ASTR

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : ii

This document is property of EADS ASTRIUM and the contents may not be reproduced or revealed to third parties without prior authorisation

EADS Astrium.

SUMMARY

This statement of work defines the Generic programme of work for the design, development, manufacturing, verification, and delivery of equipments for Astrium AS250 product line

Document controlled by Ph Galland

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : iii


EADS Astrium.

DOCUMENT CHANGE LOG

Issue/

Revision Date Modification Nb Modified pages Observations

01/00

05/06/2008

First Issue

01/01

12/06/2008

All Editorials modifications

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : iv


EADS Astrium.

PAGE ISSUE RECORD Issue of this document comprises the following pages at the issue shown

Page Issue/ Rev.

Page Issue/ Rev.

Page Issue/ Rev.

Page Issue/ Rev.

Page Issue/ Rev.

Page Issue/Rev.

All 1/0

All 1/1

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : v


EADS Astrium.

List of Acronyms

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 , Electronicsand Electromechanical EGSE: Electrical & Ground Support Equipment EICD: Electrical Interface Control Document EIDP: End Items Datapack EM: Engineering Model EMC: Electro Magnetic Compatibility ESD: Electro Static Discharge EQM: Engineering and Qualification Model EQSR: Equipment Qualification Suitability Review FM: Flight Model

FMECA: Failure Mode Effects & Criticality Analysis FMKS: Flight Model Kit Spare GDIR: General Design and Interface Requirements ICD: Interface Control Drawing IF: Interface HW: Hardware KIP: Key Inspection Point KoM: Kick off Meeting MDVE: Model-based Development and Verification Environment MICD: Mechanical Interface Control Document MIP: Mandatory Inspection Point MD: Mechanical Dummy MRR: Manufacturing Readiness Review MPCB: Materials & Processes Control Board MPR: Monthly Progress Report NA: Not Applicable NCR: Non Conformance Report NRB: Non-Conformance Review Board OBS: PA: Product Assurance PCB: Parts Control Board PDR: Preliminary Design Review PFM: Proto Flight Model PSA: Parts Stress Analysis PT: Product Tree

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : vi


EADS Astrium.

QA: Quality Assurance QM: Qualification Model QR: Qualification Review QSR: Quality Summary Report RD: Reference Document RFD: Request for Deviation RFW: Request for Waiver RR: Requirement Review SOW: Statement of Work STM: Structural & Thermal Model SVF: Software Verification Facility 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 SW: Software UCL: User Component List ( or DCL) VCD: Verification Control Document WBS: Work Breakdown Structure WCA: Worst Case Analysis

WPD: Work Package Description

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : vii


EADS Astrium.

TABLE OF CONTENTS

1 OVERALL SCOPE OF WORK............................................................................................... 10

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

3 UNIT DEVELOPMENT APPROACH AND DELIVERABLES ..........................................11

3.1 Development Logic & Models Philosophy......................................................................11 3.1.1 Equipment Category: ....................................................................................................................11 3.1.2 Existing off-the-shelf or recurring unit (cat. A or B) ......................................................................11 3.1.3 New or modified unit (cat. C or D)...............................................................................................12

3.2 Model Description .......................................................................................................... 13 3.2.1 Prototype or Bread Board (BB) .....................................................................................................13 3.2.2 Engineering Model (EM) .............................................................................................................13 3.2.3 Engineering and Qualification Model (EQM) ..............................................................................13 3.2.4 Proto Flight Model (PFM)...........................................................................................................14 3.2.5 Flight Model (FM).......................................................................................................................14 3.2.6 FM Spare ....................................................................................................................................14

3.3 EEE parts ....................................................................................................................... 16 3.3.1 EEE Procurement under subcontractor responsibility ....................................................................16 3.3.2 Alert and problem notifications .....................................................................................................16

3.4 Specific additional Requirements ................................................................................... 17 3.4.1 Components, materials and parts...................................................................................................17 3.4.2 ITAR Policy ................................................................................................................................17

3.5 Ground support equipment ............................................................................................ 18

3.6 Hardware deliveries ........................................................................................................ 18

3.7 Reviews and Key-points.................................................................................................. 19 3.7.1 Formal reviews..............................................................................................................................19 3.7.2 Software reviews: ...........................................................................................................................24 3.7.3 Mandatory Inspection Points (MIP) and Key Inspection Points (KIP) ...........................................24 3.7.4 Parts Control Board (PCB)..........................................................................................................24 3.7.5 Material and Processes Control Board (MPCB)............................................................................25 3.7.6 Radiation Control Board (RCB) ..................................................................................................25

3.8 Deliverable documentation and mathematical models .................................................. 26 3.8.1 For unit falling in category A or B................................................................................................27 3.8.2 For unit falling in category C or D................................................................................................33

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : viii


EADS Astrium.

3.9 Mathematical Models ..................................................................................................... 39

3.10 ICD documentation and associated files........................................................................ 39

4 REQUIREMENTS ON CONTRACTOR TASKS ................................................................. 40

4.1 Management Requirements & Tasks............................................................................. 40 4.1.1 Project management.......................................................................................................................40 4.1.2 Reporting ......................................................................................................................................41 4.1.3 Meetings .......................................................................................................................................42 4.1.4 Reviews.........................................................................................................................................42 4.1.5 Risk management .........................................................................................................................43 4.1.6 Schedule control.............................................................................................................................43 4.1.7 Cost control...................................................................................................................................43 4.1.8 Change control ..............................................................................................................................43 4.1.9 Configuration control, information and documentation management................................................46 4.1.10 Process Control .............................................................................................................................46 4.1.11 Logistics and inventory ..................................................................................................................47

4.2 Product Assurance Requirements And Tasks ................................................................ 48

4.3 Engineering .................................................................................................................... 48 4.3.1 Architecture & Configuration.......................................................................................................48 4.3.2 Analyses, Design & Development ................................................................................................49 4.3.3 Hardware/software compatibility ..................................................................................................49 4.3.4 Thermal design..............................................................................................................................49 4.3.5 Mechanical engineering ..................................................................................................................49 4.3.6 Contamination..............................................................................................................................49 4.3.7 Detailed electrical design and EEE engineering .............................................................................50 4.3.8 Electromagnetic compatibility (EMC) ...........................................................................................50 4.3.9 Interfaces management...................................................................................................................50 4.3.10 Mechanical and thermal ICD, including detailed interface drawings and key mechanical and thermal parameters.......................................................................................................................................50 4.3.11 RAMS (Reliability/ Availability / Maintainability / Safety).....................................................50

4.4 Embedded software (if any)............................................................................................ 52 4.4.1 General.........................................................................................................................................52 4.4.2 Deliveries ......................................................................................................................................52 4.4.3 Verification ..................................................................................................................................52 4.4.4 Maintainability.............................................................................................................................53

4.5 Implementation & verification ....................................................................................... 54 4.5.1 Development and verification plan .................................................................................................54 4.5.2 Manufacturing, Assembly, Integration , Verification and Testing ..................................................54 4.5.3 Ground support equipment............................................................................................................57

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : ix


EADS Astrium.

4.6 Requirement on Deliveries ............................................................................................. 58 4.6.1 Deliverable Items ..........................................................................................................................58 4.6.2 Acceptance procedure.....................................................................................................................58 4.6.3 Transport, storage, insurance, customs ...........................................................................................60 4.6.4 Deliverable Mathematical Models .................................................................................................60 4.6.5 Documentation..............................................................................................................................61 4.6.6 Warranty .....................................................................................................................................61

4.7 Post Delivery Activities ................................................................................................... 62 4.7.1 Support activities during satellite tests ............................................................................................62 4.7.2 Launch campaign support .............................................................................................................62 4.7.3 Post launch support.......................................................................................................................62

4.8 Specific Activities ............................................................................................................ 62

5 ANNEX 1: DOCUMENT REQUIREMENT DESCRIPTION ............................................ 64

6 ANNEX 2: REVIEW PROCESS AND RID PROCESS ....................................................... 135

7 ANNEX 3: NON ITAR DECLARATION ........................................................................... 137

AS250

Ref : DIV.SOW.00016.T.ASTR Issue : 01 Rev. : 01 Date : 12/06/2008 Page : 10


EADS Astrium.

1 OVERALL SCOPE OF WORK

This Statement of Work (SOW) defines the Generic programme of work for AS 250 equipments , hereafter called “Unit” or “Equipment”.

The Contractor (i.e. the equipment supplier) 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 Astrium the end products and services (end items) specified in this Statement of Work (SOW).

2 APPLICABLE DOCUMENTS

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

AD Title Reference Remark

AD0 Equipment Technical Specification Given in detailed SOW

AD1 Product Assurance Requirements DIV.SP.00025.T.ASTR

AD2 General Design and Interface Requirements (GDIR)

DIV.SP.00027.T.ASTR

AD3 Equipment Specific SOW

These applicable documents include applicability of ECSS documents, which are considered as applicable standards and normal practice in space industries.

In case of conflict between AD0 and AD2, AD0 will have precedence. Equipment specific SOW shall have precedence on Generic SOW (this document)

Any conflict between this SOW and the above applicable documents shall be reported to Astrium.

AS250



EADS Astrium.

3 UNIT DEVELOPMENT APPROACH AND DELIVERABLES

3.1 Development Logic & Models Philosophy

3.1.1 Equipment Category:

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 SOW 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 ASTRIUM approval.

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

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 Astrium 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 Astrium which is then explicitly specified in the AD3.

AS250



EADS Astrium.

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

New or modified equipment shall be developed against Astrium’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 Astrium for Approval.

For category D, for risk reduction, the supplier is free to make all the design validation on a BB/EM before to go to EQM manufacturing .

UnitSuitability

Review

Category Dnew unit

Pre-qualificationon EQM

Proto-Qualification

on PFM

Category Cmodified unit

Category Brecurring unit

insufficient qualification

Majormodification

Yes

Proto-Qualification

on PFM

SpacecraftPFM

Developmentand tests

on BB or EM

deltaqualification

on EQM

Acceptancetests

on FM

No

MAT 10582 A

Category Arecurring unit

sufficient qualification

EQMAvailable

?

NoYes

AS250



EADS Astrium.

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 representativity of the FM/PFM.

All tests plans shall be submitted to Astrium 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 Astrium. 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. The Equipment Supplier 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.


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 theFlightModels shall be provided in the EQM. If redundancy is not required, the switching functions associated with redundancy functions shall be demonstrated.

AS250



EADS Astrium.

The EQM shall be used by the contractor to qualify the unit as defined in AD2 (including thermal vacuum tests mechanical vibrations, shocks, EMC/ESD, … at qualification level and duration) and delivered to Astrium 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 SOW

It shall also be possible to temporarily integrate this model in the satellite in order to conduct electrical and functional tests.


3.2.4 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 satellite protoflight model and shall successfully withstand these environmental tests in order to

achieve full qualification.


3.2.5 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.6 FM Spare

If requested in detailed SOW, FM Spares models shall be manufactured and submitted to acceptance tests as defined in AD2 requirements. Test readiness reviews and Test results reviews shall be conducted on these models as for any other models.

AS250



EADS Astrium.

If FM spare are not requested, a spare kit approach shall be proposed as a warranty service to repair or replace any unit during the unit 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.

AS250



EADS Astrium.

3.3 EEE parts

3.3.1 EEE Procurement under subcontractor responsibility

The general baseline for parts quality level is identified in AD1.

The selection, evaluation, qualification, screening, and procurement of all EEE parts shall be the responsibility of the Contractor ("Self-procured scheme" without Centralised or Co-ordinated Parts Procurement Agency under Astrium responsibility).

All tasks must be performed either internally or through a Services Agency and shall conform to the PA requirements. Subcontractors shall use their own internal guide list or Preferred Parts List (PPL). Selected components shall be listed and submitted to Astrium for approval through part review boards (PRB).

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.

The contractor shall investigate and resolve any component alert or problem notification received. He shall initiate and distribute any notification for all major problems arising on EEE parts during procurement, incoming inspection or during all levels of equipment manufacturing or testing, which are of general concern.

Any alert notification which may be relevant to a EEE part belonging to the DCL shall be notified to Astrium 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

AS250



EADS Astrium.

3.4 Specific additional Requirements

3.4.1 Components, materials and parts

The unit design shall be based on proven technologies with already existing components or components with a strong heritage.

All Components, materials or parts used for units or deliverable GSE shall be free with respect to obsolescence problem over the contract duration. The associated risks shall be identified in the Risk analysis.

Any information available regarding obsolescence issue arising during the contract duration shall be communicated immediately to Astrium.

3.4.2 ITAR Policy

ITAR “free” equipments and deliverable (i.e. no part or component submitted to ITAR regulations) are strictly required for the program. Any other necessary licenses will be clearly identified in proposals and declared. This shall also be properly identified in the risk management document.

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 ..)

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 . (see annexe 3)

The Contractor is fully responsible for obtaining all those export licences and shall assume the associated risks in case of non obtention .

AS250



EADS Astrium.

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 representativity (wrt flight configuration ) for unit testing as well as the reliability and safety aspects. For GSE items ,the following requirements shall apply:

▪ Testability, availability (reliability & maintainability) , safety , life duration(a minimum of 15 years is required) operability (man/machine interface, clarity & completeness of operational procedures & manuals) ,ability to interface with flight segment in a safe way.

▪ 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 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.

A European Community certification (including EMC tests results) must be provided with any deliverable EGSE .

3.6 Hardware deliveries

Refer to Equipment specific SOW,

AS250



EADS Astrium.

3.7 Reviews and Key-points

Review 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.7.1 Formal reviews

Formal review will be held at contractor premises. Representatives of Astrium and potentially institutional agencies (CNES, ESA, …) and/or final customers might participate to the reviews.

3.7.1.1 For unit falling in category A or B

All reviews listed in following table are mandatory.

Name Date Purpose

Kick-Off Review (KO)

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

- Identify major open points from Astrium requirements or supplier proposal,

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

Equipment Qualification Suitability Review (EQSR)

As per detailed SOW - 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

AS250



EADS Astrium.

- 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 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

AS250



EADS Astrium.

3.7.1.2 : For unit falling in category C or D

All reviews listed in following table are mandatory.

Name Date Main purpose

Kick-Off Meeting (KO)

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

- Identify major open points from Astrium requirements or supplier proposal,

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

Requirements Review T0+1 month The purpose of the RR is to formally review the specification requirements. The Supplier 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 Supplier shall include this analysis in its Risk Register.

Preliminary Design Review (PDR)

TBD by subcontractor - Verify design feasibility , compatibility & predicted performance with all requirements

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

- Review test results on EM or prototypes and

AS250



EADS Astrium.

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 (TR or Test Review Board ,TRB)),

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

- Review the unit status & unit & GSE documentation

- Review the final configuration and non conformances

- Verify that all actions are correctly closed

Delivery Reviews (DR, or DRB) )

- Review the final EIDP - Verify that the equipment and all deliverables

AS250



EADS Astrium.

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

AS250



EADS Astrium.

3.7.2 Software reviews:

Solutions without software shall be preferred.

If the contractor proposes a solution which requires a software development, including firmware embedded into the unit, the following reviews are required :

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

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.

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

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

MIPs and KIPs shall be held as necessary and agreed with Astrium.

The MIPs and KIPs will be held under the Contractor’s responsibility.

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 Astrium for approval.

3.7.4 Parts Control Board (PCB)

The requirements for the selection of EEE parts and their usage are given in AD1 & AD2. The approval for the Equipment are implemented through Part Control Boards (PCBs) chaired by the Supply Quality Assurance Manager and held with the Supplier.

The PCB is put under Astrium project QA control and may be composed by designer, EEE

parts engineer, PA responsible, system representative, any other experts (radiations, assembly, …)

AS250



EADS Astrium.

from both Astrium and the Supplier. The end customer 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 Supplier's EEE parts management plan and any associated document

• Parts approval including evaluation activities (by means of Supplier DCL)

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

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

3.7.5 Material and Processes Control Board (MPCB)

The requirements for the selection of Materials and Processes and their usage are given in AD1.

The Supplier shall notify the Astrium project QA as early as possible of the use of new or

unproven materials/processes, together with proposed testing and analysis, and the subsequent

update of the DML/DPL.

Astrium project QA shall chair at Suppliers’ premises a Materials & Processes Control Board meeting, with Suppliers’ representatives from design, technology, inspection, test, manufacturing, product assurance, in order to :

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

• Processes for the Supplier

• 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

3.7.6 Radiation Control Board (RCB)

The requirements for all radiations requirement are given in AD1 and AD2.

Specific radiation board shall be organised , if applicable, to review and approve all radiations outputs and justification provided by the Supplier.

AS250



EADS Astrium.

3.8 Deliverable documentation and mathematical models

Data packages delivered to the reviews shall include the documents indicated in the following tables. The content of each document is detailed in annex 1. All documentation and associated models shall be delivered to Astrium 10 working days before the reviews in 1 original copy + 2 original copies on an electronic support such as a CD-ROM (review) and Astrium ‘s FTP server.

All documentation shall be written in English.

AS250



EADS Astrium.

3.8.1 For unit falling in category A or B

3.8.1.1 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 proposal EQSR / MRR TRR DR

MA1 Management Plans (including configuration & documentation plans) X X

MA2 Risk Assessment & Mitigation Plan X X X

MA3 Development & Verification Plan (including PT, WBS, WPD, AIT plan and master schedule)

X X

MA4 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

MA5 Inventory List X

MA6 Compliance Matrix to SOW X

MA7 Configuration Item Data List (CIDL) + Detailed Deliverable Item List (DDIL) X X X

AS250



EADS Astrium.

3.8.1.2 Product Assurance Documents

DRL N° Name of the documents to be included in the data packages proposal EQSR / MRR TRR DR

PA 1 Product Assurance Plan, including RAMS management plan and parts & radiation, cleanliness and contamination control, SW quality assurance plans(if any)

X X

PA 2 Compliance Matrix to PA requirements X X

PA 3 List of qualification status at subassembly/SW/components level X X X

PA 4.1 Hazard analysis X

PA 4.2 Reliability / Availability prediction report X X

PA 4.3 Failure Modes Effects and Criticality Analysis (FMECA) X

PA 4.4 Worst Case Analysis (WCA) X X

PA 4.5 Part Stress Analysis (PSA) X X

PA 5.1 Declared component list (DCL) and documentation X X X

PA 5.2 EEE Parts justification document and procedures (including radiations reports, evaluations, PAD and reports, procurement plan, storage/relife procedure, tests)

X

PA 6.1 Materials & processes lists (including lower tiers) with critical items identification – Declared mechanical parts list (DMPL)

X

PA 6.2 MIP/KIP list X

PA 6.3 Part Material & Processes (PMP) documentation available at supplier premises On demand

PA 7 Software Product Assurance Plan (if applicable) X X

AS250



EADS Astrium.

PA 8.1 Change request status lists X X

PA 8.2 Change request and change proposal CP within 15 working days after CR receival

PA 9 Non conformance status list (NCR) and request for waivers status list (RFW) X X X

PA 10 Non conformance Report 24 hours after any major NC

PA 11 Request for derogation (RFD) and for Waiver (RFW) For any NC against applicable documents (SOW, specification, GDIR and PA

requirements).

PA 12 Cleanliness and contamination control plan X X

PA 13 Contamination justification file (analysis, tests, allocation, report,…) X

AS250



EADS Astrium.

3.8.1.3 Engineering & Verification Documents

DRL N° Name of the documents to be included in the data packages Proposal EQSR / MRR TRR DR

EN1 Product Definition File (Design Description, Lower level specs, Detailed Electrical Drawings and Budgets)

X X

EN2 Hardware Software Interaction Analysis (only if software is involved) X X

EN3 HW/SW Interface Control Document 1 X X

EN4 Justification File and Analysis Report (Electrical, EMC, Thermal, Mechanical, Radiations, Performances, PSA, WCA, SW if any, TM/TC)

X

EN5 Design Qualification Report X X X

EN6 Verification Control Document X X X

EN7 User Manual (including software if any) 1 X X X

EN8 Compliance Matrix to the Technical Specifications (AD0 + AD2) X X X

EN9 Electronic files with equipment data as specified in the TM/TC ICD X X X

EN10 ASIC and FPGA design & development documents X

Detailed mechanical and electrical drawings 2 X

1 Including for EM

2 Available at subcontractor premises

AS250



EADS Astrium.

3.8.1.4 Manufacturing & Tests Documents

DRL N° Name of the documents to be included in the data packages Proposal EQSR / MRR TRR DR

MT1 Test Technical Specification NA

MT2 Acceptance Test Plan X X X

MT3 Test Reports X

MT4 EIDP (for delivered items) 3 X

MT5 GSE Design Definition, FMECA & Safety Analysis, European Certification (including EMC), Maintenance plan, Configuration and User manual

X X X

MT6 Log book for any delivery X

3 The hardware configuration at delivery shall be indicated (i.e relays status, EEPROM status, …)

AS250



EADS Astrium.

3.8.1.5 Software Documents (if applicable)

DRL N° Name of the documents to be included in the data packages 4 Proposal EQSR / MRR TRR DR

SW1 Software System Specification (SSS) X

SW2 Software Requirements Specification (SRS) X

SW3 Software Design Document (SDD) X

SW4 Software Reuse file (SRF) X X

SW5 Software Verification Plan X

SW6 Software Validation Plan X

SW7 Software Budget Report X

SW8 Software Validation Testing Specification (SVTS) X

SW9 Software Delivery X X

SW10 Software Configuration File (SCF) X

SW11 Software Release Document X X

4 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

AS250



EADS Astrium.

3.8.2 For unit falling in category C or D

3.8.2.1 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 proposal RR PDR CDR QR TRR DR

MA1 Management Plans (including configuration & documentation plans) X X

MA2 Risk Assessment & Mitigation Plan X X X X X

MA3 Development & Verification Plan (including PT, WBS, WPD, AIT plan and master schedule)

X X X

MA4 Progress Reports (including Schedule , Action item list , financial report, PA & Configuration status, major and minor Change status, …)

Every 6 weeks (more in case of major problem)

MA5 Inventory List X

MA6 Compliance Matrix to SOW X X

MA7 Configuration Item Data List (CIDL) + Detailed Deliverable Item List (DDIL) X X X X X

AS250



EADS Astrium.

3.8.2.2 Product Assurance Documents

DRL N° Name of the documents to be included in the data packages proposal RR PDR CDR QR TRR DR

PA 1 Product Assurance Plan, including RAMS management plan and parts & radiation, cleanliness and contamination control, SW quality assurance plans(if any)

X X X

PA 2 Compliance Matrix to PA requirements X X

PA 3 List of qualification status at subassembly/SW/components level X X X X X

PA 4.1 Hazard analysis X X X

PA 4.2 Reliability / Availability prediction report X X X

PA 4.3 Failure Modes Effects and Criticality Analysis X X X

PA 4.4 Worst Case Analysis X X X

PA 4.5 Part Stress Analysis X X X

PA 5.1 Declared component list (DCL) and documentation (1) X X X X X

PA 5.2 EEE Parts justification document and procedures (including radiations reports, evaluations, PAD and reports, procurement plan, storage/relife procedure, tests)

X X X

PA 6.1 Materials & processes list (including lower tiers) with critical items identification– Declared mechanical parts list (DMPL)

(1) X X X X

PA 6.2 MIP/KIP list X X X

PA 6.3 Part Material & Processes (PMP) documentation available at supplier premises On demand

AS250



EADS Astrium.

PA 7 Software Product Assurance Plan (if applicable) X

SW-SRR

X

SW-PDR

X

SW-CDR

X

SW-QR

PA 8.1 Change requests status list X X X X

PA 8.2 Change request and change proposal CP within 15 working days after CR receival

PA 9 Non conformance status list (NCR) and request for waivers status list (RFW) X X X X X

PA 10 Non conformance Report 24 hours after any major NC

PA 11 Request for deviation (RFD) and for Waiver (RFW) For any NC against applicable documents (SOW, specification, GDIR and PA requirements).

PA 12 Cleanliness and contamination control plan X X X X

PA 13 Contamination justification file (analysis, tests, allocation, report,…) X X X

(1) Any non qualified parts and Materials and Processes shall be identified in Risk assessment and mitigation plan

AS250



EADS Astrium.

3.8.2.3 Engineering & Verification Documents

DRL N° Name of the documents to be included in the data packages Proposal RR PDR CDR QR TRR DR

EN1 Product Definition File (Design Description, Lower level specs, Detailed Electrical Drawings and Budgets)

X X X X X

EN2 Hardware Software Interaction Analysis (only if software is involved) X X X

EN3 HW/SW Interface Control Document 5 X X X X

EN4 Justification File and Analysis Report (Electrical, EMC, Thermal, Mechanical, Performances, SW if any, TM/TC)

X X X

EN5 Design Qualification Report X X X

EN6 Verification Control Document X X X X X X

EN7 User Manual (including software if any) 1 X X X X X

EN8 Compliance Matrix to the Technical Specifications (AD0 + AD2) X X X X X X

EN9 Electronic files with equipment data as specified in the TM/TC ICD X X X X X

EN10 ASIC and FPGA design & development documents X X X

Detailed mechanical and electrical drawings 6 X X X

1 for all models

5 Including for EM

6 Available at subcontractor premises

AS250



EADS Astrium.

3.8.2.4 Manufacturing & Tests Documents

DRL N° Name of the documents to be included in the data packages Proposal RR PDR CDR QR TRR DR

MT1 Test Technical Specification X X

MT2 Qualification & Acceptance Test Plan X X X X X

MT3 Test Reports X X X

MT4 EIDP (for delivered items) 7 X

MT5 GSE Design Definition, FMECA & Safety Analysis, European Certification (including EMC), Maintenance plan, Configuration and User manual

If deliverable X X X X X

MT6 Log book for any delivery X X X X

7 The hardware configuration at delivery shall be indicated in(i.e relays status, EEPROM status, …)

AS250



EADS Astrium.

3.8.2.5 Software Documents (if applicable)

DRL N° Name of the documents to be included in the data packages 8 Proposal SW-SRR SW-PDR SW-CDR SW-QR SW-AR

SW1 Software System Specification (SSS) X

SW2 Software Requirements Specification (SRS) X

SW3 Software Design Document (SDD) X X

SW4 Software Reuse file (SRF) X X X

SW5 Software Verification Plan X

SW6 Software Validation Plan X

SW7 Software Budget Report X X X X

SW8 Software Validation Testing Specification (SVTS) X X

SW9 Software Delivery X X

SW10 Software Configuration File (SCF) X X X X

SW11 Software Release Document X X

8 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

AS250



EADS Astrium.

3.9 Mathematical Models

The models to be delivered are indicated in the following table.

PDR for cat C or D CDR for cat C or D

EQSR for cat A or B

Mechanical model (FEM) Preliminary Final

Thermal model Preliminary Final

3.10 ICD documentation and associated files

Format of all interface documents and associated files are defined in AD2 (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

AS250



EADS Astrium.

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 the 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 suppliers if any, and the required reporting and interface to Astrium.

When the Contractor has lower tier subcontractors or suppliers, he shall undertake as a minimum to:

- issue procurement specifications and other relevant documentation

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

- monitor lower tier subcontractors or suppliers 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 Astrium.

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

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.

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 Astrium beforehand.

All information delivered under this contract by the Contractor to Astrium may be copied to Astrium final customer.

Astrium 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 Astrium final customer or his representatives, in the presence of Astrium.

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)

AS250



EADS Astrium.

Astrium will exercise its control and monitoring of the contractor through the progress reports, progress meetings or other meetings, and reviews as defined in this SOW. Conference calls can be organised whenever necessary or for efficiency reasons. The contractor shall accept a collocation of Astrium representative at his premises if considered necessary at a point of development.

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

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 Astrium.

A project Management Plan shall be issued by the Contractor reflecting the management principles implemented in answer to the management requirements.

4.1.2 Reporting

The Contractor shall provide to Astrium, 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 establish an action item system and make the action item status available at any time and as a minimum in the progress report.

The contractor shall send the progress report one week prior to the relevant progress meeting to allow an effective meeting.

AS250



EADS Astrium.

4.1.3 Meetings

The Contractor shall propose a progress meeting calendar enabling efficient communication according to the various project phases. This will be subject to Astrium 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..).

Astrium 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. Astrium 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 inform Astrium of the progress meetings calendar with his own lower-tier subcontractors. Astrium may decide to attend such meetings. The contractor shall provide in all cases minutes of meeting for TRB, DR at unit or SW level at low tier subcontractors.

For all meetings where Astrium participates, Astrium may invite final customer’s representatives.

4.1.4 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

B 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

The overall Review and RID process is common to the PDR and CDR and is described in annexe 2.

AS250



EADS Astrium.

4.1.5 Risk management

A risk assessment and mitigation plan shall be issued by the Contractor and updated on a regular basis. 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.6 Schedule control

A reference schedule must 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. Any change of the Contractor reference schedule affecting milestones must be submitted to Astrium for approval.

The Contractor shall notify Astrium 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.7 Cost control

The Contractor shall propose and agree with Astrium 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. 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.

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.8 Change control

AS250



EADS Astrium.

The contractor shall implement an effective change control management. The change control procedure shall be agreed by Astrium 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.8.1 Introduction of change:

- The Contractor shall acknowledge receipt of any Change Request (CR) from Astrium and submit a contract Change Proposal (CP) to Astrium within 15 working days of the issue of the request by Astrium. Except specific request the minimum validity for CP shall be 4 months.

- The Contractor shall also submit a Change Proposal (CP) to Astrium immediately when a change is anticipated that may have an influence on the contract itself or any contractually agreed item.

- The form which will support the CP shall be approved by Astrium (in house forms can be accepted if complete information is provided).

AS250



EADS Astrium.

4.1.8.2 Review and approval of change:

- Change review boards (CRB) may be requested by the Contractor and/or Astrium 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 Astrium and its own Subcontractors or suppliers (if any). Astrium may invite final customer representatives to CRB concerning major changes.

- All submitted CP shall be reviewed by Astrium 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 Astrium may instruct the contractor to introduce a change before the change has not been formally processed, through delivery by Astrium 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 suppliers of the agreed change definitions

The Contractor shall propose to and agree with Astrium 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, SOW, User manual, Contract) shall be processed according to Contractor internal procedures for changes. Information and full visibility shall be provided to Astrium so that "the no impact status at spacecraft level" is reassessed. Astrium 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 Astrium 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 reported to Astrium with a justification for the change and an assessment of the impacts on the qualification status

4.1.8.3 Non Conformances

Two categories of non-conformances are defined according to ECSS-Q-20-09:

- major non-conformances (refer to ECSS definition)

- minor non-conformances: those which by definition cannot be classified as major

In case of doubt, non conformances shall be classified as major.

The Contractor shall manage derogations and derogations status list following the configuration control process (see PA requirement in AD1):

AS250



EADS Astrium.

- derogations to any applicable documents, called deviations (RFD), must be submitted to Astrium for approval before manufacturing and testing any item. When approved , deviations are entered into the “as design” configuration with identification of models impacted by the change.

- production derogations, called waivers (RFW), concern Non –conformance discovered during or after manufacture or test of an item. Following the conclusion of the NCR review board, the unit concerned by the NC shall be either corrected or RFWs shall be issued for approval by Astrium.

4.1.9 Configuration control, information and documentation management

4.1.9.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 Astrium agreement.

Configured items (HW and SW) must be marked according to Astrium requirements.

EMs, EQM must be configured at FM standard.

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

For “off the shelf” unit, maximum reuse of existing documentation is recommended. The subcontractor must demonstrate that its documentation cover the content of deliverable documentation specified in this SOW. Any discrepancy shall be approved by Astrium.

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 Astrium agreement.

The Contractor shall provide the documentation in original electronic form.

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

The documentation should be marked “CONFIDENTIAL” if necessary to protect Astrium and its customer proprietary information.

4.1.10 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.

AS250



EADS Astrium.

4.1.11 Logistics and inventory

The Contractor shall develop and agree with Astrium the logistics and transportation methods to use. The agreed method shall be kept up to date, any change being subject to Astrium agreement .

The Contractor shall regularly report to Astrium on a yearly basis an inventory list of all property according to an inventory control procedure to be agreed with Astrium.

AS250



EADS Astrium.

4.2 Product Assurance Requirements And Tasks

The Contractor shall perform all tasks in response to the product assurance requirements detailed in AD1. 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, AD1 & AD2) 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,.

The Engineering and Verification tasks requested within this Section shall be understood as the minimum tasks the Contractor shall fulfil but the are not exclusive to the other tasks the Contractor shall do in order to fulfil its obligations.

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.

AS250



EADS Astrium.

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.

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 is responsible for the following thermal activities :

- Thermal design

- Detailed thermal mathematical model

- Thermal analyses

- Definition of thermal interface

- Definition of thermal budgets

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

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 SOW.

4.3.6 Contamination

AS250



EADS Astrium.

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 /offgassing.

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.

4.3.8 Electromagnetic compatibility (EMC)

The Contractor shall be responsible for Unit EMC compatibility with respect to the requirement defined in AD2.

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.

4.3.9 Interfaces management

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

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

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

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

and thermal parameters

4.3.11 RAMS (Reliability/ Availability / Maintainability / Safety)

AS250



EADS Astrium.

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 (AD1) and according to RAMS technical requirements expressed in documents (AD0) and (AD2).

AS250



EADS Astrium.

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 AD1 based on the application of the ECSS standards.

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

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 Astrium.

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.

On request, all software shall be delivered at any time, including documentation.

If the software developed under the contract is embedded in or relies upon another software product, the Contractor shall offer to Astrium and final customet the option for a license to use the supporting product if it is not commonly available.

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.

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.

4.4.3 Verification

AS250



EADS Astrium.

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 Astrium.

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 supplier.

A software is herein classified as :

• safety critical, if a misbehaviour of it would cause the loss of the spacecraft, • 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 Astrium, 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 Spacecraft commissioning.

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.

AS250



EADS Astrium.

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 the 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 SOW.

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.

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 AD2)

AS250



EADS Astrium.

- E(Q)M model shall be submitted to qualification tests, according to this SOW and AD0 & AD2 requirements

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

- FM models shall be submitted to acceptance tests as defined in this SOW and AD0 & AD2 requirements.


AS250



EADS Astrium.

The Verification and Qual and Acceptance tests to be performed shall include the tests as listed in the table below. This list and development models (EM, EQM, PFM, FM) may be tailored with the approval of Astrium depending on the category and maturity of each unit.

Test Deliverable BB model

Deliverable EM model

Deliverable EQM model

Deliverable PFM

Deliverable FM notes

Mechanical Mass / Dimensions / Interfaces T T T T CoG / MOI T/A T/A T/A T/A Equipment data mode, except for specific

equipment (large, heavy) Sine Vibration T T T Random vibration T Acoustic noise T

T T Random or acoustic, depending on the type of unit

Shock T Vs Vs Thermal Thermal Cycling T T Thermal Vacuum T T T/A

Thermal cycling is deemed acceptable for a recurring unit being qualified in thermal vacuum

EMC Bonding, Isolation T T T T Power consumption / Inrush T T T T Conducted Emission T/A Vs T T FM if necessary Conducted Susceptibility T/A Vs T T/A Radiated Emission T T T/A Radiated Susceptibility T T/A T/A ESD T Vs Vs Confirm applicability of qual. test Electrical interfaces T T T T T Functional / performance Functional tests T T T T T HW / SW tests T T T T T For equipment with embedded SW, tests

representing the HW/SW qualification of the equipment

RF tests T T T T Specific RF testing for TT&C units Pyro / release tests T/A T/A T T As relevant Deployment tests T T For deployable items Propulsion tests T T For propulsion items (functional checks,

cleanliness, pressure proof test, leak test)Optical tests T T T For optical items, optical properties Life tests T Vs Vs For mechanisms

Legend : T verified by Test T/A Test or Analysis

A verified by Analysis Vs Verified by Similarity

AS250



EADS Astrium.

4.5.3 Ground support equipment

The Contractor shall carry out the design and development off all hardware and software Ground Support Equipment (GSE) necessary to support the Unit development, qualification and acceptance.

The contractor shall take care of the interfaces representativity (wrt flight configuration ) for unit testing as well as the reliability and safety aspects.

For GSE items, the following requirements shall apply:

- Testability,

- Availability (reliability & maintainability),

- Safety,

- Life duration,

- Operability (man/machine interface, clarity & completeness of operational procedures & manuals, ability to interface with flight segment in a safe way).

- FMECA to guarantee the safety of personal and tested unit in case of failure

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 subsequent modifications.

The Contractor shall ensure that the deliverable GSE (if any) 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 for his GSEs .

AS250



EADS Astrium.

4.6 Requirement on Deliveries

4.6.1 Deliverable Items

4.6.1.1 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 chapter 3.

The hardware and software shall be delivered with their associated documentation and Ground Support Unit as specified hereafter.

4.6.1.2 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.

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.

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

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 terms of the next paragraph.

4.6.1.3 Items procured or manufactured under the contract

All items procured or manufactured which have been paid for under the contract shall be the property of Astrium 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, Astrium, will specify the disposal conditions.

4.6.2 Acceptance procedure

4.6.2.1 Pre delivery Acceptance tests

Pre-delivery acceptance tests will take place at Contractor’s premises. Astrium, potentially accompanied by its customer representatives, shall be invited to attend to the pre-delivery acceptance tests. The pre-delivery

AS250



EADS Astrium.

acceptance tests schedule shall be communicated to Astrium 15 calendar days and confirmed 5 working days prior to the beginning. Astrium shall inform the Contractor about Astrium or its customer participation.

4.6.2.2 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 Astrium 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 Astrium, 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.

4.6.2.3 Consent to ship

The consent to ship of the unit gives to the Contractor the obligation to deliver the unit.

4.6.2.4 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 Astrium to the Contractor within 15 days following receipt of the hardware by Astrium.

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

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

All major actions issued during the DRB are closed

Astrium has checked and approved the unit EIDP.

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.

4.6.2.5 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 Astrium. 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 Astrium at the specified delivery location. If Astrium requests an alternate delivery location, the delivery costs shall be under the responsibility of the Contractor.

AS250



EADS Astrium.

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 Astrium or any other TBD premises in Europe.

The Contractor shall provide the shipping containers with the appropriate packing to protect the unit from the environment conditions experienced during transit or storage. It is the Contractor’s responsibility to define the appropriate requirements for transport and storage and have them implemented up to the place of delivery to Astrium.

The Contractor shall be responsible for compliance with the applicable export regulations, and he shall fulfil the customs formalities.

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

Supplier name and address

FRAGILE label, in red.

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

The Contractor shall notify Astrium 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 3.8) 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 Astrium 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 Astrium.

AS250



EADS Astrium.

4.6.5 Documentation

The deliverable documentation is listed in section 3.8. 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 3.8 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 Astrium request in section 3.8.

In order to minimise the documentation management effort, the Contractor may propose to Astrium not to deliver all the documents specified in section 3.8 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 3.8, 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 Astrium.

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 for a period of five (5) years from the date of acceptance of the unit by the Buyer.

AS250



EADS Astrium.

4.7 Post Delivery Activities

4.7.1 Support activities during satellite tests

Expertise on call.

4.7.2 Launch campaign support

Expertise on call.

4.7.3 Post launch support

Expertise on call.

4.8 Specific Activities

None

AS250



EADS Astrium.

PAGE INTENTIONALLY LEFT BLANK

AS250



EADS Astrium.

5 ANNEX 1: DOCUMENT REQUIREMENT DESCRIPTION

This annex defines the minimum data that must be included in the major deliverable documents.

AS250



EADS Astrium.

TITLE : MANAGEMENT PLAN DLR n° : MA1

PURPOSE OF DOCUMENT :

This plan describes the proposed management approach and activities in response to the S.O.W. requirements

CONTENTS :

The Management Plan shall give a precise description of the project management and control procedures that the Contractor will operate in response to the Astrium management requirements of the S.O.W., covering the following aspects :

- Project Management

- Company organisational structure

- Relevant company experience

- Responsibilities, interface to Astrium and subcontractors (if any)

- Key personnel with CV’s

- Information systems and management tools

- Project Breakdown Structures

- Product Tree

- Work Breakdown Structure

- Organisation Breakdown Structure

- Company/Country Structure

- List of suppliers with associated responsibilities

- Reporting/Meetings/Reviews

- Project Control

- Risk management

- Schedule control

- Cost control

- Change control

- Configuration control (HW and SW)

- Documentation control

- Logistics and inventory

AS250



EADS Astrium.

AS250



EADS Astrium.

TITLE : RISK ASSESSMENT AND MITIGATION PLAN DLR n° : MA2


This plan describes the risk analysis for the design, development, qualification and production of the unit as well as for the project organisation.

CONTENTS :

- Classification of risks categories: probabilities (low, medium, high) and planning or performances

impacts (low, medium, high)

- Identification of all risks, with associated probability and impact

- Risk owner

- Definition of mitigation actions for all risks within the following gravities

o Low probability x high impact

o Medium probability x medium impact

o Medium probability x high impact

o High probability x low impact

o High probability x medium impact

o High probability x high impact

- Definition of due dates for all mitigation actions and recovery action if risks are raised

- Definition of due date for recovery actions

- The risks shall cover as a minimum following topics:

o Management, organisation

o Development,

o Qualification (new technology , etc)

o Design ,

o Radiation

o Design, feasibility,

o MAIT,

o Procurement ,

o ITAR

o Obsolescence.

o Lower tiers …

AS250



EADS Astrium.

AS250



EADS Astrium.

TITLE : DEVELOPMENT & VERIFICATION PLAN DRL N° : MA3


This plan describes the development verification & testing approach and activities (for the unit HW, SW and GSE) in response to the SOW requirements

CONTENTS :

- Development

- Design, development and qualification status (heritage status)

- Development category and model philosophy with rationale

- Overall design and engineering, development, manufacturing and AIT process and activities (including software if applicable)

- Description of project reviews (including MRR, TRR and MIP/KIPs)

- Hardware/software matrix at equipment unit and GSE level, w.r.t. Product Tree

- Spare approach description

- Schedule bar charts showing design, development, manufacturing and AIT activities at all levels

- Manufacturing, Assembly, Integration And Test

- MAIT flow charts including key points & reviews

- Test activities description & justification

- Verification

- Verification approach method and control

- Verification activities

- Test matrices and analyses

AS250



EADS Astrium.

TITLE : PROGRESS REPORT DRL N° : MA4


Provide a regular status of the development and manufacturing status, including at lower tier level

CONTENTS :

- List the current major applicable documents (reference and issue)

- Progress of technical & development activities

- Progress of production activities

- Status on procurement activities (EEE, PCBs, …)

- Current planning including milestones, critical path and due date for deliveries (with SW source file)

- Meeting plan

- Status of deliverable items (documentation, HW, SW, EGSE)

- Action item status list, including progress of risk mitigation actions

- Contractual and invoice status

- Status of major NCs, RFD, RFWs, CR, CP

- List of major issues especially new ones w.r.t. previous progress report.

AS250



EADS Astrium.

TITLE : INVENTORY LIST DRL N° : MA5


Provide the list of all items developed or procured in the frame of the contract, excluding deliverable items which are described through EIDPs

CONTENTS :

For each item developed or procured under the contract, description of the item, provide the item serial number, date code or identification :

- non deliverable development models

- spare material

- Spare EEE and parts

- Non deliverable EGSE

- Tools, jigs and other laboratory means

AS250



EADS Astrium.

TITLE : COMPLIANCE MATRIX TO SOW DRL N° : MA6


Provide a status of conformity to every requirements of the SOW

CONTENTS :

For each requirement where a discrepancy exist, provide

- The status of the non compliance: Partial Compliance (PC) or Non Compliance (NC)

- A description of the nature of the non or partial compliance

- A justification of the non or partial compliance

- A proposition to re-formulate the requirement

AS250



EADS Astrium.

TITLE : CIDL & DDIL DRL N° : MA7


The document gives the Configuration Item Data List (CIDL) and the Detailed Deliverable Item List (DDIL) detailed content. The CIDL and DDIL are controlled by CADM .

The CIDL is a document generated from central database giving the current design status of a configuration item during the development, manufacture, qualification and delivery providing its complete definition. The list shall indicate the issues of all documents which are applicable for the build of each model.

The DDIL shall provide the “planned, as delivered” constitution of each delivery

CONTENTS :

- Configuration Item Data List:

- IDL identification header (supplier, product name, product tree code, model, issue date)

- Applicable controlled document list:

- customer control documentation: customer specifications, ICDs, support specifications

- engineering /design documentation: verification plans, special procedures (e.g. transportation& handling), declared PMP lists,lower level specifications, lower level interface documents, drawings and associated lists, test specifications and procedures, user manual,….)

- list of applicable change and applicable deviation RFDs (including status, directly related to the document)

- Detailed Deliverable Item List content:

- The DDIL shall be managed at Product Tree + model level and for each delivery (including spare parts or model).

- The DDIL shall be in EXCEL format or compatible with EXCEL format including following header and fields.

- Header: supplier, subcontracted product name, product tree code and model.

- Fields: item name, item supplier internal product code (marking reference), applicable drawing reference, serial number (same identification as defined in requirement specification), type (complete or partial with sequential number), quantity of delivered item product code

AS250



EADS Astrium.

TITLE : PRODUCT ASSURANCE PLAN DRL N° PA1


This plan shall describe the proposed PA / RAMS approach and activities for the equipment in response to the PA requirements to assure the quality of the product..

CONTENTS :

The PA plan shall describe the overall PA programme including reliability, quality, safety, parts,

materials and software.

It shall include:

- Policy and objectives for the PA tasks including quality assurance, safety, reliability, maintainability, EEE parts, materials and processes, software, ground support equipments, cleanliness.

- Product Assurance Organization (with detail of product assurance disciplines organisation: RAMS, EEE, M1P… at company level and at project level with the involved personnel)

- Schedule

- Applicable and reference documentation

- Reporting

- Non conformance management and control

- A KIP/MIP (Key Inspection Point/Mandatory Inspection Point) programme where criteria for KIP’s (to be attended by Subcontractor QA) and MIP’s (to be attended by Subcontractor QA and Astrium) shall be defined (if not a self standing document – see PA6.3)

- Cleanliness and Contamination Control (if not a self standing document – see PA13)

- Sizing of PA effort based on ranking list of critical items and characteristics

- Audit planning

- RAMS management :

- description of tasks to demonstrate how the contractor will implement the requirements

- risk reduction actions follow-up,

- management of RAMS critical items

- RAMS deliverables & deliveries planning for all phase C/D,

- Component Control Plan (if not a self standing document)

- Software PA plan (if not a self standing document)

- Compliance matrix against this set of requirements (if not a self standing document – cf PA2)

AS250



EADS Astrium.

TITLE : COMPLIANCE MATRIX TO PA REQUIREMENTS DRL N° PA2


Provide a detailed status of compliance to each technical requirement included in AD1.

This document may be a part of PA1.

CONTENTS :

The compliance matrix to PA requirements shall contain a statement of applicability and compliance (Compliant/Partly Compliant /Non Compliant) to each requirement in the PA requirements with a clear reference to in-house documents. If no inhouse documents exist the contractor has to establish or describe the activities planned in the PA-Plan.

Contractor in-house PA-Manuals or other PA documents must be available and capable to demonstrate compliance with the PA requirements

For each requirement where a discrepancy exist, provide

- The status of the non compliance: Partial Compliance (PC) or Non Compliance (NC)


- A justification of the non or partial compliance

- A proposition to re-formulate the requirement

The requirements of PA requirements for Subco document must be contractually accepted. Each non compliance (even partial) must be accepted through contract or request for deviation.

AS250



EADS Astrium.

TITLE : List of qualification status at subassembly/SW/components level DRL N° PA3


This document provides the Qualification Status of all Configured Items at unit, SW and lower tier level.

Qualification at Parts, Materials and Processes (PMP) level is not treated in this document but is declared in all PMP lists (DCL, DML, DPL): see DRL N°5.1, 5.2 & 6.1.

This document will be filled up all along the project life, following CI Qualification (At Equipment Level).

The objective of this list is to provide as much information as possible on the Qualification status of all CIs : - Qualification Test,

- Qualification related Actions

CONTENTS :

For each configured items, the list shall provide as a minimum:

- Name of configured item,

- Subcontractor,

- Qualification parameters (e.g. mechanical performances, mechanical I/F, EMC/ESD, …)

- Associated qualification document reference (test report…);

- Status of the qualification (for each parameters ) and remarks (if any).

- Non conformances raised during the qualification test with their status

AS250



EADS Astrium.

TITLE : HAZARD ANALYSIS DRL N° : PA4.1


The hazard analysis shall identify the potential hazards arising from the products and their causes.

CONTENTS :

The hazard analysis shall contain:

• Analyse of all hazardous events inherent to the products during nominal operations or in case of failures.

• Fault Tree analysis for all safety critical feared events specified in the Technical Specification in order to verify the required failure tolerance of the product.

For detailed content of the hazard analysis, it will be referred to document AD1.

AS250



EADS Astrium.

TITLE : RELIABILITY / AVAILABILITY PREDICTION REPORT DRL N° : PA4.2


This document shall provide a demonstration of the reliability and the availability of the product.

CONTENTS :

The content of the Reliability / Availability prediction report shall be :

1) Reliability prediction part:

• a scheme of the unit representing all lower level functional blocks, detailing each interfaces,

• a Reliability Blocks Diagram with clear references to the above functional blocks,

• the reliability prediction assumptions, procedure and results. Particularly all formulae and numerical techniques shall be identified and justified,

• the list of the most important parts which contribute to low reliability,

• conclusion and recommendations.

The reliability shall be evaluated according to some basic rules :

• all parts are assumed to have constant failure rates and to fail independently,

• the method of ‘Parts count’ or ‘Part Stress’ shall be carried out using the procedure of the document Mil hdbk 217 F + notice 2.

• failure rate adjustment factors : the following factors shall be applied to the base failure rate :

duty cycle factor :

when applicable, duty cycle multiplying factors shall be determined using the following formula

factor = (on time) * (operational k factor) + (fraction ‘off’ time) * (non operational k factor)

2) Availability prediction part:

The Subcontractor shall provide the occurrence rates associated to events (Single Event Upset, Single Event Transient, …) leading to unavailability of the product.

All the constraints associated to the recovery of product nominal performances shall be identified and quantified:

- delay between product switch OFF and ON,

- warm up duration,

- …

AS250



EADS Astrium.

TITLE : Failure Modes Effects and Criticality Analysis DRL N° : PA4.3


The FMECA identifies all failure modes, their effects on equipment performances and on external interfaces and their criticality.

CONTENTS :

A FMECA shall be performed on the functional and physical design at equipment level

The FMECA report shall contain the results of the FMECA analyses and data sources and techniques.

The FMECA report shall include all information necessary for understanding and review of the analysis:

- Identification of equipment configuration being analysed,

- Identification of applicable functional description and reliability block diagram,

- Identification of operational mode under consideration,

- Identification of level of analysis (refer to AD1),

The FMECA shall address for each hardware failures, for Single Event Phenomena as well as for software functional failure modes:

- The effects on the unit functions, on the unit performances, on the interfaces signals and the impacts on the unit power dissipation

- How each failure mode is detected and the associated unit telemetries affected

- Description of the failure isolation and recovery concept within the equipment

- For equipment containing software, a Hardware/Software Interaction Analysis shall be performed to ensure that the software is designed to react in an acceptable way to hardware failures.

- The need for specific monitoring and actions at to be implemented at system level

- The gravity (or severity), as defined hereafter:

1 = failure propagation outside the unit

= internal failure propagation between unit redundant functions

2 = loss of all the functions of the unit

3 = loss of some functions within the unit

4 = without functional effect - FMECA items identified as a safety hazard shall include a cross reference to the corresponding

paragraph in the Hazard Analysis, where those particular items are treated.

- Discussion of reliability critical areas: Single Point Failures, areas of possible failure propagation. and safety hazards

AS250



EADS Astrium.

- Discussion of changes since last issue.

Parts failures to be considered are defined in annex 3 of AD1.

Common mode and common cause failure shall be considered.

The FMECA form sheet used are defined in document ECSS-Q-30-02.

AS250



EADS Astrium.

TITLE : WORST CASE ANALYSIS DRL N° : PA4.4


This document shall demonstrate that compliance with interface and performances requirements is met in the worst nominal case of use.

CONTENTS : The Worst Case Analysis will contain:

• The assumptions, the method and the data base used,

• The list of the functions (circuits analysed),

• The list of the parameters analysed,

• The results and eventual non compliance.

The Worst Case Analysis will take into account the effects of:

• Initial part tolerance i.e electrical and/or mechanical tolerances as given in the appropriate Part Procurement Specification,

• Temperature,

• Ageing,

• Radiation

• Variation of interface parameters,

The referenced document to be used is ECSS-Q-30-01.

AS250



EADS Astrium.

TITLE : PART STRESS ANALYSIS DRL N° : 4.5


This document shall determine the level of stress applied to EEE parts et demonstrate compliance to derating requirements specified in ECSS-Q-60-11 'Derating EEE components'

CONTENTS :

Each Parts Stress Analysis Report shall identify:

• Applicable design documentation,

• Applicable technical specifications,

For each component used in the design list:

• Component identification,

• Performance requirements,

• Environment.

• Applied stress including:

• Voltage,

• Current

• Thermal,

• Mechanical

• Stress cycles

• Transient stress

• Derating factors applied to each parameter

• Conformance to derating requirements of ECSS-Q-30-11

• Identification of critical parameters for each component and integration in Critical Items List,

• Discussion of results and recommendation.

AS250



EADS Astrium.

TITLE : DECLARED COMPONENT LIST (DCL) AND DOCUMENTATION

DRL N° : PA5.1


This document shall provide above information and support the Part Review Board defined in the SOW and in PA Requirements AD1.

CONTENTS :

The Declared Component List & documentation shall contain as minimum (Applicable requirements can be found in the PA requirements document AD1) :

- DCL:

• Component number (commercial equivalent designation) • Family (ESCC group code) • Package • Value or range of values with tolerance for non qualified parts • Component manufacturer (name, country) • Generic procurement specification • Detail procurement specification (with issue & revision for non qualified parts) • Specification amendment (including issue and revision) • Name of the procurement agent (CPPA, Subcontractor, distributor) • Quality level and lot test (ESCC LAT/LVT, MIL TCI/QCI/CI) • Space qualified status (yes or no) • RVT (yes or no) • Reference of the PAD or Justification Document • Approval status of the part • Change identification between each DCL issue • Date-code (only for “as built” DCL)

- Evaluation plans & Evaluation reports: See §7.4.3 of [AD1].

- Procurement specification: see §752 of [AD1]:

any new specification shall include as a minimum:

• Absolute maximum ratings • Electrical and mechanical parameters and limits • Screening, burn–in, and acceptance requirements • Package material and lead finish • Documentation/data requirements • Delta limits when applicable • Criteria for percent defective allowable

AS250



EADS Astrium.

• Lot Validation Testing / Quality Conformance Inspections • Marking • Storage requirements • Requirements for lot homogeneity • Serialization (when applicable) • Protective packaging and handling requirements • Radiation Verification Testing requirements, when applicable - Complementary tests

- User’s derating rules

- User’s relife procedure: see req 7.5.10 of [AD1]. The procedure shall include as a minimum:

• Maximum storage period, • Testing and control sequence applied • Acceptance and rejection criteria - User’s requirements for ASICs & MMICs See §7.8 of [AD1]

- User’s screening procedure for programmable devices See §7.8 of [AD1]

The following documents shall be sent to Astrium for review:

- user’s incoming procedure: this document shall include as a minimum (as per req. 757b of [AD1]:

• Marking control • Quantity verification • Packing checking • Review of the manufacturer delivered documentation • Additional tests when the buy-off has not been performed (external visual by AQL 0,65% or

sampling [20 parts min] and electrical measurements at room temperature on 20 parts) • Additional tests based on the type of component, criticality and heritage with the manufacturer (e.g.

solderability tests, electrical tests)

- procedure for handling & storage of EEE parts or to handle EEE parts during mounting: as a minimum, the following areas shall be covered (as per req.76c of [AD1]):

• Control of the environment in accordance with ESCC Basic Specification No. 24900 • Measures and facilities to segregate and protect components during receiving inspection, storage,

and delivery to manufacturing. • Control measures to ensure that electrostatic discharge susceptible components are identified and

handled only by trained personnel using anti static packaging and tools.

AS250



EADS Astrium.

TITLE : EEE Parts justification document and procedures DRL N° : PA5.2


Justification of commercial /industrial part or any other parts not qualified and not listed in ESA or MIL QPL/QML lists.

CONTENTS : Applicable requirements can be found in the PA requirements document (AD1) and its referenced document: Guidelines for selection, procurement, control and use of commercial EEE parts: ADS.E.0705. This document shall contain as a minimum: - Description of the parts, their manufacturers, the use of the parts on commercial market, and

services proposed by the manufacturers

- Supporting data: qualification status of product & manufacturer, internal quality & reliability data, radiation data, evaluation programme

- Procurement & Post-procurement Data: final production tests, production conditions, additional tests, procurement conditions

- Risk analysis in using those parts for the unit

AS250



EADS Astrium.

TITLE : Materials and Processes list (including lower tiers) WITH CRITICAL ITEMS IDENTIFICATION – Declared mechanical parts list (DMPL)

DRL N° : PA6.1


The purpose of the DML / DPL / DMPL is to have a detailed record of all the materials / processes / mechanical parts used to produce the equipment (including lower tiers).

The data in the DML / DPL / DMPL shall make it possible to assess whether the materials / processes are suitable for our specific application.

CONTENTS :

The Declared Materials List (DML), Declared Process List (DPL) and Declared mechanical part list (DMPL) shall comply with ECSS-Q-70 (latest issue).

The DML shall contain as minimum the following items:

- Identification item number - Commercial identification or standardized designation - Chemical nature/type of product - Manufacturer/ procurement specification - Summary of process parameters - Use and location on equipment/subsystem - Environmental code (radiation, ambiance, temperature) - Size code (surface, volume or mass) - Stress corrosion cracking code - Out gassing values - Material criticality - Justification of approval, comments - Approval status The DPL shall contain as minimum the following items:

- Identification item number - Process identification - User name and Process specification - Process description - Use and location on equipment/subsystem - Associated DML or DMPL items - Criticality with reason of criticality - Justification of approval, comments - Approval status The DMPL shall contain as a minimum the following items: - Identification item number

AS250



EADS Astrium.

- Commercial identification, - Type of part - Procurement information - Elementary function,main characteristics - Use and location on equipment/subsystem - Environmental code (radiation environment, ambiance, temperature) - Criticality with reason of criticality - Justification of approval, comments - Approval status Following documents are also requested:

- Critical items list (CIL) giving details of items, reason for criticality and details of control programme (risk reduction, approach / comments).

- Requests for Approval (when necessary): to request permission to use a critical materials or processes.

AS250



EADS Astrium.

TITLE : MIP / KIP List DRL N° : PA6.2


To identify the KIP/MIP's planned on the equipment unit(s)

CONTENTS :

- All KIP/MIP's have to be listed in this document. Difference shall be done between KIP (Key inspection point) for which Astrium is informed and MIPs (Mandatory inspection point) for which Astrium has to be invited. Please refer to PA requirements for subcontractors § 4.5.9 inspection.

- KIPs/MIPs description shall contain as a minimum:

- identification number of KIP / MIP; - item affected - date of inspection - step of the manufacturing, assembly and integration flow where KIPs or MIPs take place - inspection procedure ( if already available) - nature of inspection point, e.g. test surveillance, dimensional check, visual check, etc This document needs to be agreed by Astrium for MRR as required in PA requirements for subcontractors req. 459c.

AS250



EADS Astrium.

TITLE : PMP DOCUMENTATION AVAILABLE ON REQUEST AT SUPPLIER PREMISES

DRL N° : PA6.3


Documentation to be available during meetings to justify qualification status,…

CONTENTS :

The following documentation shall be available at supplier premises :

- Key points Minutes of Meeting and reviews reports

- Lowers tiers certification plan and certification Minutes of Meeting

- Qualification plan and qualification reports of lowers tiers

- PMP Purchasing specification

- PMP Incoming inspection report

- Internal and lower tiers PMP procedures

- All data relevant to justify use of materials and processes w.r.t our application (qualification aspects).

AS250



EADS Astrium.

TITLE : Software Product Assurance Plan (SPAP) DRL N° : PA7


The purpose of the Software Product Assurance Plan is to provide information on the organisational aspects and the technical approach to the execution of the software assurance programme.

CONTENTS :

The scope and content of this document is fully detailed in ECSS-E-40 Part 2B, Annex K.

AS250



EADS Astrium.

TITLE : Change Requests Status List DRL N° : PA8.1


This document shall list all changes w.r.t the contract.

CONTENTS :

This list shall provide for each change proposal:

- CP document number; - Issue & revision; - Date; - Title of the change; - Change request originating the change; - Configuration item affected; - Status of approval.

AS250



EADS Astrium.

TITLE : Change Request and Change Proposal DRL N° : PA8.2


The objective of a change request is to collect the information that formally defines a proposed programme or project change versus the existing requirements.

A change proposal the vehicle for proposing a major change to an approved baseline data or the business agreement. A change proposal may be raised in answer to a change request or not.

CONTENTS :

These documents shall comply with ECSS-M-40 (latest issue).

Change request shall include:

- Organization / company originator of the document; - Identification of the CR: ref/issue; - Date; - Project; - Title of change request; - Affected item(s); - Affected document(s): documents to which the CR applies; - Reason for change; - Description of change; - Approval. & authorisation to proceed

Change proposal shall include:

- Organization / company originator of the document; - Identification of the CR: ref/issue; - Date; Project; - Change request reference (if any); - Title of change proposal; - Change description; - Classification; - Effectivity: recommended introduction point. - Affected item(s); Affected document(s): documents affected by the change; - Reason for change; - Description of change; - Related factors of the change (interface, safety, qualification…) - Effect, price, schedule impact; - Limitation of use. - Approval..

AS250



EADS Astrium.

TITLE : Non conformance status list (NCR) and request for waivers status list (RFW)

DRL N° : PA9


These documents shall list all discrepancies between the as designed configuration (documented in the CIDL) and the as built configuration.

Non conformance status list and waivers status list provide complete representation of the status of all non conformances/RFWs occuring in the frame of the project at any time. They include minor and major NCRs/RFWs.

CONTENTS : - Non conformance status list: for each NCR, at least the following information shall be included:

- NCR unique identification; - non conforming item identification; - classification; - short description of the non conformance (title); - date of last NRB meeting; - disposition; - implementation status of disposition; - reference to RFW, if applicable; - open and closed status.

Request for waiver status list: for each RFW, at least the following information shall be included:

- RFW unique identification; - non conforming item identification; - classification; - related NCRs; - short description of the RFW (title); - open and closed status.

AS250



EADS Astrium.

TITLE : Non conformance reports DRL N° : PA10


The purpose of non conformance report is to provide the recording of non conformances: reporting, review, disposition, analysis of non conformances, the definition of implementation of corrective and preventive actions.

Each non conformance shall be fully documented and self explanatory

CONTENTS :

Non conformance report shall contain as a minimum: - identification of the supplier of the NC item; - project; - Unique identification including id. of updated issues; - related internal NCR - critical item: ‘yes’ or ‘no’ as identified in the project CIL; - pages and attachments: individual page number and total number of pages of the report; - NCR title: short description (same as the one used in NC status list); - NC item: identification of the NC item by name and number according to the CIDL and its serial number. - next higher assembly, subsystem model - NC observation: date and location of the non conformance observation - NC detecting during: activity being performed when the NC was detected - Description: description of the non conformance, location on the product, means of detection, condition for observation, to be supported by attachments as appropriate, environmental conditions pertaining to the product at that time - classification as major or minor - initiator: date, signature - internal or external NRBs: MOMs reference, date and agreed dispositions - corrective or preventive actions agreed by NRB - verification: individual close-out statement by PA personnel for all actions raised by the NRB - request for waiver: if applicable, related RFW - cause of NC: basic fact or circumstance which causes the non conformance - NC close out: date, signature of supplier PA or Qa responsible for closure

AS250



EADS Astrium.

TITLE : request for Deviation (RFD) and for Waiver (RFW) DRL N° : PA11


A deviation is the vehicle for requiring and agreeing the departure from a customer’s requirement that is part of an approved configuration baseline.

A waiver is a written authorization to use or release a product which does not conform to the specified requirements. For follow-on production model of the unit a ‘request for deviation’ or a ‘contract change notice’ may be requested.

These documents shall comply with ECSS-M-40 (latest issue)

CONTENTS : Request for deviation shall include:

- Organization / company originator of the document; - Identification of the RFD: ref/issue; - Date; - Classification; - Project, business agreement, order; - Originator site; - Item designation (identification of the non conforming item); - Affected items; - Effectivity of the deviation by model or serial number; - Affected documents (documents to which the item does not conform, document reference and

issue, § or requirement) - Description; - Reason for request; - Adverse effects; - Approval.

Request for waiver shall include:

- Organization / company originator of the document; - Identification of the RFW: ref/issue; - Date; - Classification; - Project, business agreement, order; - Originator site; - Item designation (identification of the non conforming item); - Affected items; - Effectivity: model or serial number of the NC item (s); - Affected documents (documents to which the item does not conform, document reference and

AS250



EADS Astrium.

issue, § or requirement) - Description; - Reason for request: reason why the proposed NC can be accepted; - NCR; - NRB minutes of meeting (NRB which decided to raise the RFW) - Adverse effects; - Limitation of use; - Approval

AS250



EADS Astrium.

TITLE : Cleanliness and Contamination control plan DRL N° : PA12


The purpose of this document is to set out the ways in which the required cleanliness levels are achieved and maintained during the life of the programme, from design to launch, and which also defines cleanliness levels throughout the mission up to the end-of-life.

CONTENTS :

This document shall comply with ECSS-Q-70-01A. It shall include as a minimum:

- cleanliness requirements: higher level requirements, prediction of contamination levels, selection of materials and processes, corrective actions (in case the prediction are out of specification);

- environment and facilities;

- MAIT activities: allocation, control definition, cleaning and decontamination methods and tools, packaging, storage & transportation, control flow…

- Responsibilities for inspections, clean rooms and facilities and contamination monitoring.

AS250



EADS Astrium.

TITLE : Contamination justification file (analysis, tests, allocation, report …)

DRL N° : PA13


This document is the answer to cleanliness and contamination control plan.

It gives all elements to justify that the equipment is within the allocation.

CONTENTS :

This document shall include the following points as a minimum: - Contamination requirements: spec, allocation for each phase of the MAIT…

- measurements done on witnesses, other tests…

- analyses and justification of contamination level estimated on the equipment w.r.t allocation;

- assessment, corrective actions done in case of anomaly related to equipment contamination.

AS250



EADS Astrium.

TITLE : PRODUCT DEFINITION FILE DRL N° : EN1


The equipment design description details the equipment design as proposed to meet the specification requirements.

CONTENTS :

As a minimum, this document shall give :

- The different function of the units (HW & SW)

- The detailed description of the unit and of each module contained in the unit (including module block diagram) for HW & SW

- The performances of the unit (including mass, power, lifetime, reliability figures, cleanliness, radiation tolerances, ...)

- The operational requirements i.e. the operational modes description, the allowed mode transitions, the operational constraints on ground and in orbit, the maintenance needs (on ground and in orbit), the transportation and storage constraints

- A detailed description of the unit interfaces (mechanical, thermal, electrical ...) and of the technical characteristics of these interfaces (for example, for an electrical interface : input and output impedance, protection, voltage ...)

- General and detailed electrical drawings and associated list of components with their values

- Budgets

- Lower level specifications

AS250



EADS Astrium.

TITLE : Hardware Software Interaction Analysis (HSIA) document DRL N° : EN 2


The Hardware Software Interaction Analysis document is to verify that the Software Requirement Specification (SRS) covers all hardware failures.

(the HSIA document is necessary only when there is software in the equipment)

CONTENTS : The HSIA activity is fully detailed in ECSS-Q-30-02A, Chapter 4.10. The HSIA document is a set of form sheets, one per hardware failure.

The content of each form sheet shall be inspired from Chapter 4.10.2, item h, and can be tailored if necessary.

The HSIA may be part of the FMECA: PA §4.3

AS250



EADS Astrium.

TITLE : HW/SW Interface Control Document DRL N° : EN 3


The HW/SW Interface Control Document provides the exhaustive and detailed list of all hardware/software interfaces of the equipment.

CONTENTS :

The content shall be the following :

- Overview of the hardware architecture (hardware layout, buses, external interfaces, etc),

- Memory address map,

- Processor module interfaces,

- Interrupts management (if any),

- Detailed definition of all registers (including timings, constraints),

- Detailed description of all external interfaces,

- Operational constraints (initialisation, modes, error codes, FDIR, monitoring, etc).

AS250



EADS Astrium.

TITLE : JUSTIFICATION FILE & ANALYSIS REPORTS (POWER ,EMC, THERMAL ,MECHANICAL, TM/TC & SOFTWARE PERFORMANCES)

DRL N° : EN4


It shall gives a design justification synthesis (how the justification documents are organised, current status, critical points,…) and gather all supporting information (plan, design report, design analysis, tests report, …)

CONTENTS :

- Description

- Product

- Justification Documentation overview

- Current baseline

- Justification synthesis

- Main requirements

- Overview of justification approach

- Hypothesis

- Current status

- Discussion

- Open points and action plan

- Critical items

- Support documentation (technical notes, test reports, analysis report,….)

AS250



EADS Astrium.

TITLE : DESIGN QUALIFICATION REPORT DRL N° : EN5


This document defines for each deliverable a synthesis of the qualification test result.

CONTENTS :

It shall contain the data in the format given in the following pages.

AS250



EADS Astrium.

SPACECRAFT:UNIT:CONTRACTOR:SUBSYSTEM:

1 : EQSR

Reference:Category:Conclusions:

Mechanical qualification: CommentsRandom: Analysis / Test on … (Model)/Heritage (Spacecraft/model), Not applicableQuasi-static:Sine:Shock:Micro vib.:

Life test CommentsLife cycles:

Thermal qualification CommentsThermal vac.

EMC qualification: CommentsCE:Inrush:CS:RE:RS:ESD:

Open points status:

PLEIADES

AS250



EADS Astrium.


2 : MECHANICAL QUALIFICATION STATUS

Random :Perpendicular

to I/F plane Test report ref:as requested as tested

Freq. range Spectral density Duration Spectral density Duration RFW/RFD ref. Subject / Justification StatusdB/Oct s dB/Oct s g2/Hz g2/Hz

dB/Oct g(RMS) dB/Oct g(RMS)

Lateral axisas requested as tested

Freq. range Spectral density Duration Spectral density Duration dB/Oct s dB/Oct sg2/Hz g2/Hz

dB/Oct g(RMS) dB/Oct g(RMS)

Comments: STATUS: Proto qualified at unit levelwaiting for tests at satellitelevel for finalqualification

PLEIADES

AS250



EADS Astrium.


2 : MECHANICAL QUALIFICATION STATUS (CONT'D)Quasi-static

Test report ref:

RFW/RFD ref. Subject / Justification Status

as requested as tested Acceleration factor Acceleration factor

g / s g / s

Comments: STATUS:

PLEIADES

AS250



EADS Astrium.

SPACECRAFT:

UNIT:CONTRACTOR:SUBSYSTEM:

2 : MECHANICAL QUALIFICATION STATUS (CONT'D)Sine

Perpendicularto I/F plane Test report ref:

as requested as tested Freq. range Acceleration Sw. rate Acceleration Sw. rate RFW/RFD ref. Subject / Justification Status

mm mm g oct/s g oct/s

Lateral axis as requested as tested

Freq. range Acceleration Sw. rate Acceleration Sw. ratemm mm

g oct/s g oct/s

Comments: STATUS: Proto qualified at unit levelWaiting for test at satellitelevel for final qualification

PLEIADES

AS250



EADS Astrium.


2 : MECHANICAL QUALIFICATION STATUS (CONT'D)Shock

Perpendicularto I/F plane Test report ref: -

as requested as tested Acceleration: g Acceleration: RFW/RFD ref. Subject / Justification Status (0 - peak) (0 - peak)

Pulse shape: Pulse shape: Duration: Duration:

Lateral axis

as requested as tested Acceleration: g Acceleration:

(0 - peak) (0 - peak)Pulse shape: Pulse shape: Duration: Duration:

Comments: STATUS:

PLEIADES

AS250



EADS Astrium.

SPACECRAFT:UNIT:

CONTRACTOR:SUBSYSTEM:

2 : MECHANICAL QUALIFICATION STATUS (CONT'D)Microvibration

Test report ref: -


as requested as tested

Comments: STATUS:

PLEAIDES

AS250



EADS Astrium.

SPAC EC R A FT:U N IT:C O N TR A CT O R :SU BSY ST EM :

3: LIFE TE ST ST ATU S

T est report ref: -

RFW /RFD ref. Subject / Justification Status


Com m ents: STA TU S:

PLE IA DE S

AS250



EADS Astrium.


4: THERMAL QUALIFICATION STATUSThermal vacuum cycling:

as requested as tested Corona test Y/N N Test report ref:

as requested as tested RFW/RFD ref. Subject / Justification StatusDepressurization Delta P: Delta P:

Max. time: Max. time:

as requested as tested Cycles number OFF: OFF:

ON: ON:TOTAL: TOTAL:


Temperatures T non-op max. °C T non-op max. °CT qual. max. °C T qual. max. °C T qual. min. °C T qual. min. °C

T start up °C T start up °CT non op min. °C T non op min. °C

Comments STATUS: Proto qualified at unit levelWaiting for tests at satellitelevel for final qualification

PLEIADES

AS250



EADS Astrium.


5: EMC QUALIFICATION STATUSConducted Emissions

Test report ref: -


as requested as tested Frequency Levels Frequency Levels

DM dBuA dBuAdB/Oct dB/Oct

CM

Comments STATUS:

PLEAIDES

AS250



EADS Astrium.


5: EMC QUALIFICATION STATUSInrush current

Test report ref:


as requested as tested Initial slope A/us Levels A/us

Peak current A ASlope after peak A/us A/usPlateau current A A

Plateau duration ms ms

Total capacitance uC Total capacitance uC

Comments STATUS:

PLEIADES

AS250



EADS Astrium.


5: EMC QUALIFICATION STATUSConducted susceptibility

Test report ref:


SINEWAVE as requested as tested Frequency Level Frequency Level

Vrms Vrms

TRANSIENT as requested as tested Duration kHz Levels kHz

Peak V V Period of repeat s s

Comments STATUS:

PLEIADES

AS250



EADS Astrium.


5: EMC QUALIFICATION STATUSRadiated emissions

as requested as tested Test report ref:General mask Frequency Level Frequency Level

dBuVrms MHz dBuVrms RFW/RFD ref. Subject / Justification Status

dB/oct dB/oct


Specific bands Frequency Level Frequency LevelMHz dBuVrms MHz dBuVrms

Comments STATUS:

PLEIADES

AS250



EADS Astrium.

SP A C E C R A F T :U N IT :C O N T R A C T O R :SU B SY ST E M :

5: E M C Q U A L IF IC A T IO N ST A T U S

R adiated susceptibility

as requested as tested T est report ref:G eneral m ask F requency L evel F requency L evel

dB u V rm s dB u V rm s R F W /R F D ref. Subject / Justification Status

dB /oct dB /oct


Specific bands F requency L evel F requency L evelM H z dB u V rm s M H z dB u V rm s

- -

C om m ents ST A T U S:

P L E IA D E S

AS250



EADS Astrium.


5: EMC QUALIFICATION STATUS

ESD

Test report ref: -


as requested as tested Shape

Pulses number

Comments STATUS:

PLEIADES

AS250



EADS Astrium.

TITLE : VERIFICATION CONTROL DOCUMENT (VCD) DRL N° : EN6


For each requirement, it must explain how the compliance is demonstrated (test, analysis, similarity) with a reference of the document and of the chapter of this document (test specification, engineering analyses report, test reports, etc..) where the compliance can be found. The VCD shall be extended to include the close-out documentation and its status.

CONTENTS :

The verification control document shall give in a table :

- the requirement reference document

- the requirement reference paragraph

- the verification requirement identification (ID number)

- the verification requirement title (Key word)

- the verification method

- the verification level with reference to test plan, analysis, documentation

- the unit model (i.e. PFM, FM)

- the close-out document reference (including the relevant chapter) explaining the method

- the verification status, relevant RFWs, RFDs and NCRs

For each requirement whose compliance is not supported by a test, the VCD shall refer to the adequate engineering analyses report(s) which shall contain all the justification of the compliance with the specification which can be either a technical note reference, analysis report reference, manufacturing control or directly the justification itself with the indication of the calculation methods and data base which have been used.

AS250



EADS Astrium.

TITLE : USER MANUAL (1/3) DRL N° : EN 7


The equipment user manual is used both by the ground segment for preparation and execution of the flight operations and also for Assembly, Integration and Tests activities

CONTENT :

It is constituted of 2 parts : part A : IN-ORBIT user manual and part B :AIT LEVEL user manual - Part A : In Orbit User Manual

Part A shall clearly distinguish between the functional description of the unit and the operational procedures

1. General Description - Overview of the unit such that the detailed design information presented in the subsequent

sections can be understood in the overall context.

2. Configuration - Functional breakdown - Hierarchical configuration - Physical configuration

3. Detailed description - Detailed description of the unit functions, using functional block diagrams, switching diagram

showing the location of the telemetry outputs and telecomand inputs, and logic and circuit diagrams

4. Interfaces - Description of the external interface of the unit relative to the in-flight configuration

5. Performance and budgets

6. Modes - Summary of all nominal and back-up modes, their purpose and conditions for use. - Modes transition diagram. - Detailed description of each mode (with identification of the related electrical configuration and

of the active SW functions if any). - Detailed description of each mode transition (including H/W and S/W actions, timing)

7. In flight operational constraints - Dangerous commands - Command and sequencing constraints - Environmental limits - Cumulative operations (number of maximum activations)

AS250



EADS Astrium.

TITLE : USER MANUAL (2/3) DRL N° : EN7

8. Failures - Description of the external interface of the unit relative to the in-orbit conditions - Fault management at unit level and redundancy concept - Unit failures to be treated at upper level (FMECA) - Expected degradation of performance and resultant impact in terms of modified operational

constraints may be defined. 9. Nominal operations procedures (a template on hard media (diskette) will be provided for procedure generation) Each procedure for each phase of the mission, including modes transitions shall be described :

- purpose and applicability - constraints on use and upper levels pre-requisites (if any), equipment status and resources,

configuration at each step (initial and final), time criticality - For each distinct operational step, the following information is required :

- Preliminary verification and Telemetry parameters to be monitored, special processing needed to interpret them, and values expected

- commands to be executed, command parameters needed and definition of calculations needed to prepare command parameters

- timing between steps of the procedure, verification action at each step. 10. Contingency operations procedures - Procedures to isolate the source of the failure and the recovery procedures to return to nominal

mode . - The same format as for nominal procedures will be provided. 11. Internal Software (when existing within the unit) - Software Functional description (bus communication management, memory management, time

management, interrupt handling, application functions, management of automatic functions supporting equipments modes transitions, FDIR etc)

- Memory mapping - Software modes (e.g. initialization and timing aspects) - Description of synchronization/datation processing - Telecommand and telemetry description (may be provided as inputs to the SDB) - Error handling and reporting - Maintenance (documentation, tools and equipments) - Patches (method for patches development (from analysis to binary files generation), procedures

for patches uploading) 12. Description of functions handled by main on board software and related constraints 13. Summary of Telemetry and telecommand data (detailed information will be provided as inputs to the SDB) - List of telemetry parameters - List of telecommands parameters

AS250



EADS Astrium.

TITLE : USER MANUAL (3/3) DRL N° : EN7

14. Ground support software requirement specification - Definition of needs - Detailed description of the method including the necessary algorithms - Inputs data - Output data 15. Model applicability - As various issues of the user’s manual are identified all along the design and development of the

equipment, it will be necessary to identify to which model (EM, FM..) they apply, and to identify peculiarities if any.

- PART B : AIT LEVEL USER MANUAL

This part describes the specific constraints to use the unit correctly and safely during the integration and test at the upper level.

16. Electrical constraints and tasks - tests connectors definition - constraints at power ON/OFF for on-ground use - ESD precautions instructions

17. Mechanical constraints - handling, storage, packaging, transportation, constraints - protective operations instructions - cleaning process

18. Environmental constraints - temperature, pressure, humidity, gravity

19. Safety - safety precaution (personnel and equipment)

20. Operations - reference to specific tests equipment User’s Handbook and specific tools - specific AIT level test procedures - specific test points identification and description of the usage if authorized at AIT level - specific processing for telemetry derived parameters calculation - specific AIT level modes transitions definition - cumulative operations limitations, e.g. limited number of mechanism activation or other - preventive and corrective maintenance operations, - calibration operations, calibration constraints - identification of launch preparation constraints - specific test points using identification and description of their usage if authorized at AIT level

AS250



EADS Astrium.

TITLE : Compliance matrix to the technical Specifications DRL N° : EN 8


Provide a detailed status of compliance to each technical requirement included in AD0 and AD2

CONTENTS :

For every requirement, provide

- The status of the compliance: Compliant (C), Partial Compliance (PC) or Non Compliance (NC)

- A justification of the compliance status


- A proposition to re-formulate the requirement where a non or partial compliance is stated

TITLE : Electronic files with equipment data as specified in the TM/TC ICD DRL N° : EN 9


The Electronic files collects all the data characteristics of each model delivered : its behaviour and all external interfaces as described in the TM/TC ICD.

CONTENTS :

The Electronic files requested here, will be used as input to the System database (SDB).

The System database is the collection of all characteristics that identify all components and models of the satellite (EM, PFM, FM). Indeed, the behaviour, the electrical and software interfaces usually differ slightly from EM to PFM equipments.

The purpose of the System Database is to provide accurate and exhaustive data to be used during the lifetime of the satellite. The various “users” of the SDB are simulators developers, flight software developers, AIT teams and flight control operators.

Electronic files will be based on pre-defined tables to be provided by the SDB manager, together with the definition of the structure and explanations on how to fill in the tables.

AS250



EADS Astrium.

TITLE : ASIC or FPGA design & development documents DRL N° : EN 10


The ASIC or FPGA design & development documents are produced all along the successive phases of the development, starting from the Definition Phase up to the Validation.

CONTENTS : The list and content of these documents shall be inspired from the ECSS-Q-60-02A, Annex A, and can be tailored if necessary.

TITLE : TEST SPECIFICATION DRL N° : MT1


The test specification provides detailed information on how a test is made to verify a requirement

CONTENTS :

The test specification shall provide the following information concerning each test :

− the purpose of the test : it shall reflect the requirement in the unit requirement specification or other applicable document

− the description of the test : it shall provide detailed information of how a requirement is verified and which function of the test equipment is used

− the test sequence : give a synthesis of the commands sent to the test equipment

− the configuration : it states in which configuration of the unit the test shall be performed

It shall also describe the test environment and the test instrumentation

AS250



EADS Astrium.

TITLE : QUALIFICATION AND ACCEPTANCE TEST PLAN DRL N° : MT2


The qualification and acceptance test plan contains information about the overall test sequence

CONTENTS :

The qualification and acceptance test plan shall detail the verification sequence for each model allowing :

− to achieve the mechanical qualification of the unit

− to achieve the thermal qualification of the unit

− to achieve the electromagnetic qualification of the unit

− to achieve the electrical and performance qualification of the design of the unit

− to achieve the on-board software qualification, as well as the functional qualification of the overall hardware and software system

− to achieve the full acceptance of each flight unit

It shall also describe the test environment and the test instrumentation

Nota: the nominal chronology of the sequence shall be identified

AS250



EADS Astrium.

TITLE : Tests Reports DRL N° : MT 3


For each equipment (prototype, Breadboard, EM, EQM, PFM and FM), Test reports shall be provided with the results of the tests performed on the model (see SOW and AD1 for tests to be performed on the different models)

CONTENTS :

The test reports contain all test results:

− Physical measurement

− functional tests

− mechanical tests

− thermal tests

− EMC tests

− electrical

− performance tests

− Software tests (if any)

Detailed measurement must be provided, together with a synthesis of each test results showing the conformance with expected values, status of compliance w.r.t specifications including end of life worst case extrapolation.

Trend analysis of test results of all models must be provided.

The test report shall also describe the test environment and the test instrumentation

Nota: the actual chronology of the sequence shall be recalled

AS250



EADS Astrium.

TITLE : END ITEM DATA PACKAGE (EIDP) DRL N° : MT4


The EIDP is a collection of the data related to the manufacturing, assembly, integration and test of a deliverable configuration item., shall constitute the basis to support the acceptance of the product.

CONTENTS : It shall contain the following: The following subjects in the form of documents shall constitute the EIDP: (refer to PA requirements for subcontractors document § 11.2.2): 1. Content of EIDP 2. Certificate of conformity with reference and statement 3. CE certificate of compliance 4. Open item register (Open works, differed works, loose items, temporary items) 5. Operational constraints, Operating and Maintenance operations/procedures, User manual 6. Specific instructions (Packaging, handling, storage, safety, cleanliness and shipping

operations/procedures) 7. Test Readiness Review and Delivery Review Board minutes 8. Deliverable items List 9. Configuration status (as built, as design, reconciliation, list and status of Request for Deviations) 10. Change Requests status list 11. Non-conformances (major + minor) status list 12. Copies of NCR/NRB reports and Minutes for major non-conformances 13. Request for Waivers status list 14. Copies of RFDs and RFWs 15. Test results and status (summary report and as run procedures) 16. Calibration curves and data 17. Contamination status 18. Limited life items (subject to wear out) 19. Top Assembly and Interface drawings 20. Limited Life items 21. Log Book , including operating time 22. List of lower tiers EIDP’s and log book (if applicable) 23. Hardware and Software maintenance manual (for GSE) 24. Maintenance plan (for Software) 25. Shipping documents

26. Declaration of non ITAR products

27. User Manual, including handling, storage, transportation , safety

28. KIP, MIPs reports

29. Test equipment list

AS250



EADS Astrium.

TITLE : GSE Design definition, FMECA & Safety Analysis, European Certification (including EMC), Maintenance plan, Configuration and User manual.

DRL N° : MT 5


This document describes the GSE used for unit tests and/or deliverable GSE

CONTENTS :

For all GSE, the document must describe:

- the GSE description

- The GSE design

- The Failure Mode and Propagation (FMECA) inside the GSE and potential propagation to the tested unit

For all deliverable GSE, the contractor must also deliver

- Safety analysis

- CE certificate, including EMC

- Maintenance plan

- Configured item list

- User Manual

AS250



EADS Astrium.

TITLE : Log book for any delivery DRL N° : MT 6


The logbook is the document in which the data related to the integration and testing of a configuration item are recorded in chronogical order to provide the necessary events traceability at any time during the programme life cycle, beginning with the first qualification or acceptance test. It shall contain all historical, quality data and information which is significant for operation of the item.

This document is part of EIDP.

CONTENTS :

The logbook shall include as a minimum:

- precise identification of the product;

- hardware change and status table giving all changes (integration, removal or replacement) of each single element;

- summary list of integration and test instructions;

- connectors mate and demate if relevant;

- operating hours log if relevant (for limited life items).

AS250



EADS Astrium.

TITLE : Software System Specification (SSS) DRL N° : SW 1


The Software System Specification is the highest level description of the software and contains the requirements expressed by the “customer” of the software, i.e. the system responsible for the equipment.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex A, and can be tailored if necessary.

TITLE : Software Requirements Specification (SRS) DRL N° : SW 2


The Software Requirements Specification describes the functional and non functional requirements applicable to the software item.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex B, and can be tailored if necessary.

AS250



EADS Astrium.

TITLE : Software Design Document (SDD) DRL N° : SW 3


The Software Design Document describes the software architectural design and the software detailed design. Internal interfaces design is also included in this document.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex C, and can be tailored if necessary.

TITLE : Software Reuse File (SRF) DRL N° : SW 4


The purpose of this document is to describe the software reuse file in the frame of ECSS based project. The software reuse file is a constituent of the design justification file (DJF) to be developed in the course of a software development project. It documents the output of analysis to be performed on existing software intended to be reused. The global aim of the software reuse file is to document all the information used to decide about the reuse (or not) of existing software and specific action plan related to identified risks.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex I, and can be tailored if necessary.

AS250



EADS Astrium.

TITLE : Software Verification Plan DRL N° : SW 5


The Software Verification Plan document is produced in order to describe the software verification approach and the organizational aspects of the verification activities to be executed.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex G, and can be tailored if necessary.

TITLE : Software Validation Plan - DRL N° : SW 6


The Software Validation Plan provides the definition of organizational aspects and management approach to the implementation of the validation tasks.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex H, and can be tailored if necessary.

AS250



EADS Astrium.

TITLE : Software Budget Report DRL N° : SW 7


The Software Budget Reports provides the CPU and Memory budgets of the software.

CONTENTS : The content of this document shall include as a minimum : - Occupation and margins for PROM, RAM and EEPROM memories,

- Occupation and margins for CPU budget in nominal and worst case scenarios.

TITLE : Software Validation Testing Specification (SVTS) DRL N° : SW 8


The Software Validation Testing Specification describes the testing activities to be performed w.r.t. each requirement of the Software Requirements Specification (SRS).

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex F, and can be tailored if necessary.

AS250



EADS Astrium.

TITLE : Software Delivery DRL N° : SW 9


This is the complete collection of source code that is running in the equipment, together with the compilation command files used to generate and load the executable software

CONTENTS : It is not necessary to produce a formal document. The complete collection of source files and command files can be delivered on a CD-ROM media.

TITLE : Software Configuration File (SCF) DRL N° : SW 10


The objective of the Software Configuration File is to provide the configuration status of the software configuration item. It controls its evolution during the programme or project life cycle.

CONTENTS : The content of this document shall be inspired from the ECSS-M-40-B, Annex F, and can be tailored if necessary.

AS250



EADS Astrium.

TITLE : Software Release Document DRL N° : SW 11


The purpose of this document is to describe a given software version in terms of known problems, limitations or restrictions with respect to its approved baseline.

CONTENTS : The content of this document shall be inspired from the ECSS-E-40 Part 2B, Annex D, and can be tailored if necessary.

AS250



EADS Astrium.

6 ANNEX 2: REVIEW PROCESS AND RID PROCESS

The overall Review process is common to the PDR and CDR and is described on the following figure

AS250



EADS Astrium.

The RID process is detailed in the following figure:

AS250



EADS Astrium.

7 ANNEX 3: NON ITAR DECLARATION

no export/import licenses certificate

Should the performance of the Contract not necessitate any governmental authorisation attached to any procurement of equipment/part/material/process and/or attached to the delivery of the Equipment to ASTRIUM , the Contractor shall print this form on head paper showing the name of its Company and shall sign it. Once signed, this Certificate shall be joined to the ADP.

“

AS250 PROGRAMME

NO EXPORT/IMPORT LICENSES CERTIFICATE

Pursuant to the Contract N°………………………. (hereinafter referred to as the “ Contract ”) between ASTRIUM and ................................................................................. (hereinafter referred to as “ the Contractor”), the undersigned, a duly authorised representative of the Contractor, hereby certifies that, for the performance of the Work (including any procurement of equipment/component/part/material/process and the delivery of the Equipment to ASTRIUM ) neither import nor export governmental authorisations (or licenses) have been necessary.

This Certificate is provided in accordance with the requirements of the Contract specified in the Article 6 (delivery and acceptance) and Article14 (Governmental Authorisations)

The Contractor’s Managing Director

By

Typed Name :

Title :

Date :

AS250



EADS Astrium.

INTERNAL DISTRIBUTION

Document complet Resume Action Information Astrium

Laurent BARABOTTI x

Valérie COSCULLUELA x

Ange DEFENDINI x

Philippe FERRIERE x

Isabelle FOURNIER x

Brigitte FOURNE x

Bernard GILLOT x

Olivier HAMEURY x

Yann HENRY x

Jérome LEBREDONCHEL x

Emanuelle POQUET GOURDON x

Hervé MARCILLE x

Sylvain PREVOT x

Christian SIBILLA x

Pierre BARADAT x

Charles KOECK x

Philippe GALLAND x

Jean Pierre COUSTY x

Laurent DUROU x

Pierre THIBAUD x

Patrick VIDAL x

Jacques AUGIER x

Christian ETIENNE x

Bruno VIGNON x