SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
DOCUMENT CHANGE DETAILS
ISSUE
DATA
SHEET
DESCRIPTION
1
24.03.2006
all
First Formal Issue
2
10.04.2006
all
Approved issue for ITT
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
II
SWARM
SWARM Generic Statement of Work
for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
CONTENTS
1. INTRODUCTION .................................................................................................................................... 2
1.1 Scope .............................................................................................................................................. 2
1.2 Applicability ..................................................................................................................................... 2
2. REFERENCES ....................................................................................................................................... 3
2.1 Requirements Tree.......................................................................................................................... 3
2.2 Documents ...................................................................................................................................... 3
2.2.1 Applicable Documents .......................................................................................................... 3
2.2.2 Reference Documents .......................................................................................................... 4
2.3 Abbreviation List.............................................................................................................................. 5
3. EQUIPMENT MODEL & CATEGORY DEFINITION .............................................................................. 8
3.1 Equipment Model Definitions .......................................................................................................... 8
3.1.1 Lot Samples of EEE Components ........................................................................................ 8
3.1.2 Technology Samples............................................................................................................. 8
3.1.3 Breadboard Model (BB) ........................................................................................................ 8
3.1.4 Engineering Model (EM) ....................................................................................................... 8
3.1.5 Engineering Qualification Model (EQM)................................................................................ 9
3.1.6 Qualification Model (QM) ...................................................................................................... 9
3.1.7 Protoflight Model (PFM) ...................................................................................................... 10
3.1.8 Flight Model (FM) ................................................................................................................ 10
3.1.9 Flight Spare model (FS) ...................................................................................................... 10
3.1.10 Spare Kit (SK) ................................................................................................................... 10
3.2 Equipment Category Definitions.................................................................................................... 11
3.2.1 Fully Recurring Equipment - Category A ............................................................................ 11
3.2.2 Recurring Equipment with Limited Changes - Category B ................................................. 11
3.2.3 Modified Equipment - Category C....................................................................................... 12
3.2.4 New Equipment - Category D ............................................................................................. 12
4. WORKFLOW ........................................................................................................................................ 13
4.1 Fully Recurring Equipment - Category A....................................................................................... 13
4.2 Recurring Equipment with Limited Changes - Category B............................................................ 14
4.3 Modified Equipment - Category C ................................................................................................. 15
4.4 New Equipment - Category D........................................................................................................ 16
5. REVIEWS AND BOARDS DEFINITION............................................................................................... 17
5.1 Reviews ......................................................................................................................................... 17
5.1.1 Kick-Off Review................................................................................................................... 17
5.1.2 Equipment Qualification Status Review (EQSR) ................................................................ 17
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
III
SWARM
SWARM Generic Statement of Work
for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5.1.3 Design Reviews .................................................................................................................. 18
5.1.4 Manufacturing Readiness Review (MRR)........................................................................... 19
5.1.5 Qualification Review (QR)................................................................................................... 19
5.1.6 Test Readiness Review (TRR)............................................................................................ 19
5.1.7 Test Review (TR, or Test Review Board, TRB) .................................................................. 19
5.1.8 Delivery Review (DR, or Delivery Review Board, DRB) ..................................................... 20
5.2 Boards ........................................................................................................................................... 21
5.2.1 Parts Control Board (PCB).................................................................................................. 21
5.2.2 Materials & Processes Control Board (MPCB) ................................................................... 21
5.2.3 Non-Conformance Review Board (NRB) ............................................................................ 22
6. MANAGEMENT REQUIREMENTS...................................................................................................... 23
7. PRODUCT ASSURANCE REQUIREMENTS ...................................................................................... 24
8. ENGINEERING REQUIREMENTS ...................................................................................................... 25
8.1 General.......................................................................................................................................... 25
8.2 Equipment Design ......................................................................................................................... 25
8.3 Interfaces....................................................................................................................................... 25
8.4 Operations ..................................................................................................................................... 26
8.5 Analyses ........................................................................................................................................ 26
8.6 Verification Task............................................................................................................................ 27
9. EXPORT CONTROL REQUIREMENTS .............................................................................................. 28
9.1 General.......................................................................................................................................... 28
9.2 EU Export Control Requirements.................................................................................................. 28
9.3 Direct “US Supplier” ...................................................................................................................... 28
9.3.1 Inputs from EADS Astrium to Support Subcontractor's Application.................................... 28
9.3.2 Description of Subcontractor's Responsibilities .................................................................. 29
9.3.3 Outputs from Subcontractor ................................................................................................ 29
9.4 Requirements for Lower Tiers ‘’US Suppliers’’.............................................................................. 29
10. MANUFACTURING & TEST REQUIREMENTS ................................................................................ 31
10.1 Introduction.................................................................................................................................. 31
10.2 Manufacturing and Production .................................................................................................... 31
10.3 Assembly Integration and Verification......................................................................................... 31
10.3.1 MAIV Planning .................................................................................................................. 31
10.3.2 General Test Requirements .............................................................................................. 31
10.3.3 Life Tests........................................................................................................................... 32
10.3.4 Test Failure ....................................................................................................................... 32
10.3.5 Verification Control............................................................................................................ 33
10.4 Ground Support Equipment ........................................................................................................ 34
11. SUPPORT TASKS ............................................................................................................................. 36
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
IV
SWARM
SWARM Generic Statement of Work
for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
11.1 Introduction.................................................................................................................................. 36
11.2 Support to Higher Level Reviews................................................................................................ 36
11.3 Support to AIV at Higher Level.................................................................................................... 36
11.3.1 EGSE Operation Support.................................................................................................. 36
11.3.2 Integration and Test Support ............................................................................................ 37
12. APPENDIX A DOCUMENTATION REQUIREMENTS LIST .............................................................. 38
13. APPENDIX B INTERFACE DATA REQUIREMENTS........................................................................ 39
13.1 Computer Aided Drawing and Design (CAD) data...................................................................... 39
13.1.1 EADS Astrium CAD system .............................................................................................. 39
13.1.2 CAD Data Exchanges ....................................................................................................... 39
13.1.3 General Preparation of CAD Data .................................................................................... 41
13.1.4 CAD Data Deliveries ......................................................................................................... 41
13.2 Engineering Data......................................................................................................................... 42
13.2.1 EADS Astrium Engineering Data Repository .................................................................... 42
13.2.2 Engineering Data Exchange ............................................................................................. 43
TABLES
Table 13.2-1: Definition of Site names related to file naming convention for data exchange .................. 44
Table 13.2-2: Definition of Type names related to file naming convention for data exchange ................ 44
Table 13.2-3: Definition of Version, Release and Update Number related to file naming convention for
data exchange .................................................................................................................................. 44
Table 13.2-4: Definition of information in electronic format for data exchange between EADS Astrium
and subcontractors ........................................................................................................................... 46
FIGURES
Figure 13.1-1: Flowchart for CAD data exchange .................................................................................... 40
Figure 13.2-1: Overview on Users of Swarm Engineering Database Repository .................................... 42
Figure 13.2-2: Data Exchange Process for Swarm.................................................................................. 43
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
V
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
INTENTIONALLY BLANK
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
1
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
1. INTRODUCTION
1.1 Scope
Together with the equipment specific SOW, this Generic SOW describes the tasks necessary to be
performed by the Equipment Subcontractor in the frame of a SWARM equipment supply contract or
work order with EADS Astrium GmbH or EADS Astrium Ltd.. In the context of this document, EADS
Astrium refers to either EADS Astrium GmbH, or EADS ASTRIUM Ltd. as defined in the contract.
In the context of this document, the term "equipment" shall be interpreted as the product in subject
either being
•
hardware or
•
software or
•
a hardware with embedded software or
•
services.
The SOW defines the activities from beginning of the contract until equipment contract closure, i.e.:
•
The design, development, qualification, production, test and delivery of the equipment
hardware and software
•
The provision for documentation, data and numerical models, test equipment, tooling and
support equipment and transportation as required to support the higher level assembly,
integration, and verification
•
The provision of equipment related support activities and services as required by EADS
Astrium for conduction of the higher level tasks
This generic SOW is amended by an Equipment Specific SOW which considers the essentials of the
particular equipment and the special project requirements.
The subcontractor shall be responsible for the provision of all materials, manpower, facilities, supplies,
tools, equipment, documentation and support services as may be required to design, manufacture,
assemble, test and deliver to EADS Astrium the end products and services as specified in the
Statement of Work (SoW) and referred to as the “equipment”.
1.2 Applicability
This Generic SOW is applicable for all flight or ground equipment procured in the SWARM project.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
2
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
2. REFERENCES
2.1 Requirements Tree
This Generic Statement of Work, amended by the Equipment specific Statement of Work defines the
tasks to be performed in frame of the Equipment Supply Contract, on basis of the technical and quality
requirements.
For illustration, the requirements tree and the order of precedence is shown in the figure below.
Contract
(level1)
Equipment Specific SOW
- Specific
For SWARM
Equipment
- Equipment PA
Requirements
Requirements
-
(level 4b)
- General Design
Generic
Equipment SOW
& I/F Req’s
(level3)
Figure: Requirements Tree with Level of Precedence
For SWARM, the General Design and Interface Requirements are included in the Equipment
Specification.
2.2 Documents
2.2.1 Applicable Documents
The work defined in this SOW shall be performed in accordance with the requirements contained in
the following applicable documents, in their latest issue and revision as agreed with EADS Astrium.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
3
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
The following documents are applicable:
Title
Doc. No.
AD 1
Not used
AD 2
Equipment Specification
Note 1)
AD 3
SWARM PA Requirements for Subcontractors
SW-RS-EAD-PA-0001
AD 4
Software PA Requirements for Subcontractors
SW-RS-EAD-PA-0014
AD 5
Management Requirements Document for Subcontractors
SW-RS-EAD-SY-0003
AD 6
Document Contents Guidelines for Subcontractors
SW-LI-EAD-SY-0005
AD 7
Swarm Engineering Data Repository Development Plan
SW-PL-EAD-SY-0019
Notes:
1) as defined in the equipment specific SOW
ECSS standards shall be considered in their latest issues as defined in the Equipment Specification
[AD 2], the SWARM Product Assurance Requirements [AD 3], and in the Management Requirements
[AD 5] to be Applicable Documents.
2.2.2 Reference Documents
The following documents are referred in the SOW:
Title
RD 1
Swarm General Supporting Information
Doc. No.
SW-LI-EAD-SY-0004
RD 2
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
4
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
2.3 Abbreviation List
Abbreviation
Description
ABCL
As Build Configuration List
AIT
Assemly Integration and Test
AR
Acceptance Review
BB
Bread Board model
CDR
Critical Design Review
CIDL
Configuration Item Data List
COTS
Commercial Off-the Shelf
DCL
Declared Components List
DML
Declared Materials List
DOS
[US] Department of State
DPA
Destructive Parts Analysis
DPL
Declared Processes List
DR(B)
Delivery Review (Board)
DTC
[US] Department of Trade Control
EICD
Electrical Interface Control Document
EIDP
End Item Data Package
EM
Engineering Model
EMC
Electro Magnetic Analysis
ESD
Electro Static Discharge
EQM
Engineering Qualification Model
EQSR
Equipment Qualification Status Review
FGSE
Fluidic Ground Support Equipment
FM
Flight Model
FMECA
Failure Mode Effects & Criticality Analysis
FS
Flight Spare
GDIR
General Design and Interface Requirements
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
5
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Abbreviation
Description
GSE
Ground Support Equipment
ICD
Interface Control Document
ITAR
International Traffic in Arms Regulations
KIP
Key Inspection Point
MAIV
Mechanical Assembly Integration and Verification
MDVE
Model-based Development and Verification Environment
MGSE
Mechanical Ground Support Equipment
MICD
Mechanical Interface Control Document
MIP
Mandatory Inspection Point
MD
Mechanical Dummy
MPCB
Materials & Processes Control Board
MRR
Manufacturing Release Review
NCR
Non Conformance Report
NRB
Non-Conformance Review Board
OGSE
Optical Ground Support Equipment
PA
Product Assurance
PCB
Parts Control Board
PDR
Preliminary Design Review
PFM
Proto Flight Model
PMP
Parts, Materials, and Processes
PSA
Parts Stress Analysis
QM
Qualification Model
QR
Qualification Review
QSR
Quality Summary Report
RFD
Request for Deviation
RFW
Request for Waiver
RID
Review Item Discrepancy
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
6
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Abbreviation
Description
RoHS
Restriction of the use of certain Hazardous Substances
SDB
Satellite Data Base
SK
Spare Kit
SOW
Statement of Work
SVF
Software Verification Facility
TAA
Technical Assistance Agreement
TC
Telecommand
TD
Thermal Dummy
TM
Telemetry
TR
Test Results review
TRB
Test Review Board
TRR
Test Readiness Review
VCD
Verification Control Document
WCA
Worst Case Analysis
WEEE
Waste of Electrical and Electronic Equipment
For further abbreviations and terms used refer to the Swarm General Supporting Information [RD 1].
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
7
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
3. EQUIPMENT MODEL & CATEGORY DEFINITION
3.1 Equipment Model Definitions
The ECSS Standard ECSS-E-10-02A, Annex B, defines equipment models in general. For SWARM,
specific model definitions shall apply as following.
3.1.1 Lot Samples of EEE Components
Samples are required for DPA on each procured part lot as defined in the PA requirements [AD 3].
3.1.2 Technology Samples
Technology samples are not normally deliverable, however EADS Astrium may request
manufacturing, test and delivery of the following:
•
unused materials and parts,
•
witness or coupon samples of painting, adhesive and bonding processes of any critical or new
technologies,
•
witness of coupon samples for in-process manufacturing control.
Any Technology Sample shall be kept with full traceability during the warranty period, as a minimum.
3.1.3 Breadboard Model (BB)
A BB is functionally and electrically representative of the full equipment or part of it and it is used to
validate a new or critical feature of the design. There are no specific requirements for configuration
and interface control. BB shall normally not be used to validate software. For deviations approval of
EADS Astrium is necessary.
3.1.4 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. However, the standard
shall be the highest possible achievable within given schedule and cost constraints but using the same
manufacturer, the same type and the same package as for the Flight Models. Any redundancies which
may be provided in the flight standard model shall be provided in the EM unless otherwise agreed with
EADS 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 has to be considered. Therefore, compatibility to all FM interfaces in
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
8
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
AIT program is required; e.g. gold plated connectors, pins and sockets are necessary. The use of
connector savers might conflict with test on higher level and require agreement of EADS Astrium. The
Equipment Subcontractor shall apply configuration control and as-build status reporting to EMs.
Testing shall be done in accordance with Equipment Subcontractor issued plans approved by EADS
Astrium. Test reports shall be prepared and issued.
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.1.5 Engineering Qualification Model (EQM)
An EQM shall be fully representative of Flight Model in form, fit and functions, i.e. including electrical,
thermal, mechanical, optical etc. fidelity. A lower level of electrical components may be used. The
standard of these components shall be the highest achievable within the schedule and cost
constraints but using the same manufacturer, the same type and the same package as for the Flight
Models. However, the selected components shall withstand the environmental loads applied during
qualification testing. Only the testing and the screening of the parts might be different compared to the
Flight Models. Any and all redundancies which may be provided in a Flight Model shall be provided in
the EQM.
The EQM shall be subject to the full equipment level qualification test sequence. Participation of the
EQM to the higher level AIT program in combination with flight models has to be considered.
Therefore, compatibility to all FM interfaces in AIT program is required; E.g. gold plated connectors,
pins and sockets are necessary. The use of connector savers might conflict with test on higher level
and require agreement of EADS Astrium. The EQM shall be build 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 Equipment Subcontractors issued plans approved by EADS Astrium.
Test reports shall be prepared and issued.
3.1.6 Qualification Model (QM)
A QM shall be built to full flight standard in accordance with the PA requirements for Flight Models.
Flight Standard parts shall be used with the same manufacturers, the same types, the same packages
and the same level of testing and screening as for the Flight Models.
When it is necessary to demonstrate and qualify the life capability of an equipment subject to wearout, qualification must be achieved by the life test of a QM.
A QM shall be subject to the full equipment level qualification testing. EADS Astrium shall approve the
relevant test plans and reports to establish qualification.
As for the QM hardware (and software, if applicable), the QM test plans, procedures and reports shall
be issued and configured.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
9
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
3.1.7 Protoflight Model (PFM)
A 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 protoflight qualification and acceptance testing. EADS Astrium
shall approve the relevant test plans and test reports to establish protoqualification and acceptance for
flight.
PFM test plans, procedures and reports shall be issued and configured.
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.
If more than one of the same standard equipment is required for use on the satellite, only one of these
needs to be a PFM unless otherwise specified.
3.1.8 Flight Model (FM)
A 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. EADS Astrium shall approve the relevant
test plans and test reports to establish acceptance for flight.
FM test plans, procedures and reports shall be issued and configured.
3.1.9 Flight Spare model (FS)
A FS shall be of the same built standard as the PFM or FM.
An EQM or QM could be used as FS if convenient (e.g. acceptable parts level) after proper
refurbishment. The detailed requirements on the FS if applicable, shall be on top of those of EQM and
QM respectively and are to be defined in the Equipment Specific SOW.
3.1.10 Spare Kit (SK)
The need for Spare Kits is defined in the Equipment Specific SOW. In general, Spare Kits shall allow
for repair of any "random" failure that might occur to the equipment and within a maximum allowable
repair time of typically 3 weeks. It shall therefore comprise each of the EEE parts in the maximum
number in which it is used on any one board, all boards (unassembled, including Mother Board),, , one
connector per type, etc. Any other Long Lead Item or element requiring a procurement period or preintegration steps being not compliant with the repair time, as well as sub-assemblies or modules which
cannot be dis-assembled for repair shall form part of the Spare Kit, too. All these elements are to be
separately prepared, regrouped, kitted and stored under consideration of the PA requirements or
delivered, in accordance to the Equipment Specific SOW, under consideration of any export licenses if
applicable.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
10
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
The spare kit shall be defined individually for the equipment and shall not be mixed with similar parts
which are spares of another unit.
All spare parts, components and assemblies procured or manufactured in support of the repair facility
shall fulfil all the applicable specifications and be fully interchangeable with the flight part, component
or assembly.
Spare parts may not be required for casing, structural, and harness elements.
3.2 Equipment Category Definitions
The use of recurring items (available design from other programmes) and of common items (currently
under development in the frame of other programmes) shall be considered wherever possible. The
Subcontractor shall demonstrate that all items comply with Swarm requirements. In case the Swarm
requirements are more stringent than the original design requirements the Subcontractor shall take the
necessary steps to provide compliance (analysis, delta qualification or qualifications as appropriate).
The Subcontractor shall monitor any changes, part obsolescence deviations or waivers raised on
these items, which could affect the Swarm programme.
With respect to recurrent mechanisms the Subcontractor shall demonstrate that the intended use for
Swarm is within the scope of the original application for which these mechanisms have been qualified.
It is the responsibility of the subcontractor to fully justify and demonstrate the qualification of his items
and the resulting categorisation.
With this background, the equipment shall be categorised as A, B, C, or D according to the rules
defined below.
The Subcontractor shall describe in detail his approach in the Design, Development and Verification
Plan. The appropriate workflow per category as outlined in section 4 below shall be used as guideline.
3.2.1 Fully Recurring Equipment - Category A
Equipment which is fully identical to one already qualified for comparable mission environmental
requirements, with no changes in design, manufacturing, materials, parts, processes. The qualification
test programme in heritage shall be at least as severe as that imposed by that of SWARM.
The demonstration of the validity of the equipment definition has to be provided by a detailed
qualification status list/report.
3.2.2 Recurring Equipment with Limited Changes - Category B
Recurring equipment with no modifications that was already tested and qualified but subjected to less
severe qualification programme or to a different environment.
Minor modifications to the existing design or applied processes, either in design, manufacturing,
materials, parts which do not significantly invalidate the existing qualification are allowable.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
11
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Delta design and/or delta qualification are needed and shall be agreed on a case-by-case basis.
Re-classification to Category C shall be possible on the basis of the EQSR.
3.2.3 Modified Equipment - Category C
Equipment similar to one already qualified or flown, with major or significant changes in design,
manufacturing, materials, parts, processes. Formal design reviews and a delta or full qualification
programme are needed. They shall be decided on a case-by-case basis.
3.2.4 New Equipment - Category D
Newly designed and developed equipment. A full qualification test programme shall be imposed.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
12
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
4. WORKFLOW
This chapter defines the logical flow of work to be performed on equipment along the required reviews,
dependant on its category as defined in Section 3 above.
The subcontractor is encouraged
•
to optimize the review sequence in order to consider the schedule necessities of SWARM and
to improve the production flow of his deliverable models, but without increasing the risk nor
invalidating the need of full qualification,
•
to propose combined reviews as far as reasonable and efficient, pending agreement of EADS
Astrium (e.g. EQSR combined with Kick-off or MRR).
4.1 Fully Recurring Equipment - Category A
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
13
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
4.2 Recurring Equipment with Limited Changes - Category B
Note: PFM TRB, DRB, and QR may be combined
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
14
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
4.3 Modified Equipment - Category C
MODIFIED
EQUIPMENT
START SUPPLY
CONTRACT
Equipment Requirements
KICK-OFF
REVIEW
Vendor Proposal
Equipment Requirements
& available Data Package
Equipment Requirements
Preliminary Design Data Package
Equipment Requirements
Detailed Design Data Package
Equipment Functional Baseline
approved
EQSR
Equipment Development
Baseline provisionally approved
(PDR needed, or approved (no
PDR)
PDR
Equipment Development Baseline
approved
CDR
Equipment Design/Qualification
Baseline approved for
EQM, QM & PFM Production
PFM
MRR
(E)QM
MRR
PFM
TRR
(E)QM
TRR
PFM
TRB
(E)QM
TRB
PFM
DRB
Equipment Requirements
Full Product documentation
QR
Equipment Production Baseline
approved for Flight Model
Production
FM MRR
FM TRR
FM TRB
FM DRB
Note: the qualification can be done on an EQM, QM, or PFM, whatever is appropriate for the
equipment / instrument.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
15
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
4.4 New Equipment - Category D
Note: the qualification can be done on an EQM, QM, or PFM, whatever is appropriate for the
equipment / instrument.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
16
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5. REVIEWS AND BOARDS DEFINITION
Reviews and boards will be held for control and guidance of all project activities at Equipment
Subcontractor. The reviews/boards will be chaired by EADS Astrium. The relevant documentation
shall be reviewed before the review meeting. Comments shall be given to the Subcontractor in
advance to the meeting as far as possible. The review meeting can either be held at Subcontractor's
premises or via tele/videoconference. Due to the evidence of project transparency, ESA will be invited
by EADS Astrium to share the review.
Due to its significance in terms of risk, the Design Review organisation is of more formal type and
described in the corresponding chapter below.
5.1 Reviews
5.1.1 Kick-Off Review
The purpose of the Kick-Off Review is to address all questions left open regarding EADS Astrium
requirements or the Subcontractor proposal. The contractual baseline, including design and
development, performance, verification and delivery shall be confirmed. The declaration of the review
success by EADS Astrium gives the go-ahead for the activities to be defined during the Kick-off
Review.
5.1.2 Equipment Qualification Status Review (EQSR)
The EQSR generally do not apply to equipment falling into the category D, “New Equipment”. The
purpose of the EQSR is to formally review the design standard, build standard, configuration, and
qualification status of the equipment against the programme requirements. The maturity of the
equipment design, compatibility with equipment interfaces and its ability to satisfy the performance
requirements placed on it shall be formally acknowledged.
The qualification status of all parts, materials and processes used in the manufacturing of the
equipment shall be presented and reviewed as part of the EQSR. Evidence of equipment qualification
tests from other programmes, this being at equipment, sub-assembly, components/parts, and software
level, shall be given as appropriate. The review shall also establish the adequacy of the test plan and
test procedures of flight equipment.
The main outputs of the EQSR are the confirmation or change of the equipment category as proposed
by the subcontractor and the decision upon the development and qualification plan and models in the
case of modified equipment design or build standard.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
17
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5.1.3 Design Reviews
5.1.3.1 Preliminary Design Review (PDR)
A PDR is generally not needed for recurring equipment (Category A) and usually not needed for
equipment with limited modifications in design, build or environment (Category B).
The purpose of the PDR is to formally agree the preliminary design of the equipment. The selected
design concept and its feasibility shall be presented, together with the trade-off analyses performed in
the design selection process. External interfaces of the equipment shall be reviewed for compatibility
with the system design and frozen at that stage. A successful PDR means that the equipment
development baseline is agreed and satisfies the functional baseline requirements, and that detailed
design is authorised. If any aspect of this review is considered unacceptable a close-out process shall
be followed to concur on an agreed development baseline.
5.1.3.2 Critical Design Review (CDR)
A CDR is generally not needed for recurring equipment (Category A) and for equipment with limited
modifications in design, build or environment (Category B).
The purpose of the CDR is to formally agree the detailed design of the equipment. It verifies the
compatibility of equipment interfaces and compliance of the detailed design with the performance
requirements, and establishes the adequacy of plans and preparations for manufacture and test of
flight equipment. The supporting analyses which form part of the Design Review Data Package are
reviewed at the CDR. A successful CDR means that the equipment design baseline is agreed on the
basis of the detailed design documentation reviewed and approved at the CDR.
5.1.3.3 Design Review Organisation
Design Review meetings shall be held at the subcontractor's premises where the work is normally
performed, unless agreement is obtained from EADS Astrium for an alternative location.
•
15 working days prior this meeting, a complete Data Package shall be received by EADS
Astrium. This time period could be extended based on the complexity of the equipment, and in
the case of a review of this Data Package by ESA. Thus, the 15 days lead time need to be
confirmed by EADS Astrium case-by-case.
•
EADS Astrium review the Data Package and provide comments written on Review Item
Discrepancies (RID). As a goal, the RIDs from EADS Astrium and its customer ESA (if any)
will be sent to the subcontractor as far as possible 10 working days after reception of the Data
Package. The subcontractor shall be prepared to accept further RIDs during the subject
review meeting.
•
The subcontractor shall answer to each RID . Responses to the RIDs received before the
review meeting shall be provided to EADS Astrium 5 working days after RIDs reception, but
not later than during the review meeting.
•
A Design Review meeting shall be held under the control of the EADS Astrium chairman.
Minutes shall be written by EADS Astrium, identifying all the conclusions and
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
18
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
recommendations. EADS Astrium shall identify which of the action items must be completed
before the review can be considered successfully completed.
•
The review shall be considered successful after EADS Astrium agreement on the closure of
the here-above major action items. In this case, the Astrium chairman formally closes the
review.
5.1.4 Manufacturing Readiness Review (MRR)
The purpose of the MRR is to verify that all activities necessary prior to the start of manufacture of
qualification, protoflight or flight models are complete and all the necessary documentation and
resources are in place to enable manufacture to commence. If some activities are not completed at
the time of the MRR, it is part of the review to assess the open issues and to decide if manufacturing
may commence concurrently to the closure of the open issue action items.
5.1.5 Qualification Review (QR)
The purpose of the QR is to formally review the qualification and/or delta-qualification test results and
to demonstrate the qualification of the equipment. Life tests shall be completed before the QR,
whenever practicable. When it is not practicable, provisional qualification may be granted subject to
life test results. In addition, all qualification activities of parts, processes and materials as required by
PCB or MPCB shall be completed satisfactorily at the QR to grant full qualification status.
5.1.6 Test Readiness Review (TRR)
The purpose of the TRR is to review the readiness of the equipment to be tested, and the readiness of
test documentation, test procedures, test programmes, test software, test facilities and test personnel.
TRR shall be held before performing acceptance, qualification, protoflight and environmental tests on
the equipment or batch of equipment as agreed with EADS Astrium.
The Subcontractor shall have an established process whereby designated personnel certify that the
test item, equipment, protective devices, cabling, procedures and supporting documentation have
been reviewed and found to be complete and adequate prior to the application of power and initiation
of environmental testing.
5.1.7 Test Review (TR, or Test Review Board, TRB)
The purpose of the TR, or frequently called TRB, is to summarise the Subcontractors analysis on the
test results, and in the case of NCRs to decide which actions have to be taken.
EADS Astrium shall be provided with a complete set of the test data to be reviewed in sufficient time in
advance to the TR.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
19
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5.1.8 Delivery Review (DR, or Delivery Review Board, DRB)
The purpose of the DR, or frequently called DRB, after satisfactory completion of all tests and
inspections is to verify:
•
That the equipment and all deliverables satisfy all contractual requirements
•
That the EIDP is a complete and accurate history of the equipment
•
That all non-conformances and concessions have been satisfactorily closed and there are no
outstanding actions
•
The hardware status through a visual inspection of the equipment, its container and the
associated tooling whenever applicable
•
The packing, packaging, adequate configuration and protection of the equipment for shipment
•
The release of shipment after successful DR.
All actions still open at the time of delivery shall be closed through formal close-out agreed by EADS
Astrium in order to close the DR.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
20
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5.2 Boards
5.2.1 Parts Control Board (PCB)
The selection of EEE parts and their usage approval for the Equipment are implemented through Part
Control Boards (PCBs) chaired by the EEE Parts Manager representing the SWARM Product
Assurance of EADS Astrium and held with the Subcontractor.
The PCB is put under EADS Astrium Product Assurance control and may be composed by designer,
system representative, any other experts (radiations, assembly, …) from both EADS Astrium and the
Subcontractor. ESA representative may also use the right to participate as a PCB member.
Depending on the progress of the Equipment Purchase, the main PCB activities are :
•
Review and approval of the Subcontractor's EEE parts management plan and any associated
document
•
Parts approval including evaluation activities (by means of Subcontractor DCL)
•
Purchase status (including schedule, dispatching, delivery schedule) ,
•
Problem resolution (non conformances, RFD, RFW, ...).
5.2.2 Materials & Processes Control Board (MPCB)
Materials and Processes shall preferably be selected from a valid Materials/Processes List of a
recognised authority (CNES, ESA, NASA, MIL, etc…) or from previously flown space hardware. For
each equipment a declared materials list, including mechanical parts (DML) and a declared processes
list (DPL) is kept up to date during development and manufacturing until delivery.
The Subcontractor shall notify to EADS Astrium as early as possible intended the use of new or
unproven materials/processes, together with proposed testing and analysis, and the subsequent
update of the DML/DPL.
A Materials & Processes Control Board (MPCB) shall be established between EADS Astrium and with
support from Subcontractors’ representatives from design, technology, inspection, test, manufacturing,
and product assurance. ESA has the right to participate in the MPCB process. The MPCB shall:
•
Evaluate and approve the DML and DPL
•
Ensure that PMP management is conducted in accordance with the project requirements.
•
Ensure that PMP implementation is performed in accordance with design and manufacturing
documents (mandatory inspection points and key inspection points) and to request audits and/or
technical reviews where considered necessary.
•
Support investigations to resolve PMP non-conformances.
Non qualified materials/processes or open MPCB actions might have major schedule impacts on
equipment manufacturing.
Where deemed necessary a MPCB meeting may be convened.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
21
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
5.2.3 Non-Conformance Review Board (NRB)
During the NRB meeting, the following points are presented and reviewed :
•
the detailed circumstances of the non conformance
•
the different analyses, tests or simulations performed to understand the cause of the non
conformance
•
the consequences of the non conformance the Subcontractors’ investigations results
For Major NCR's, the EADS Astrium Product Assurance shall ensure with the active support of the
Subcontractor the determination of corrective actions to eliminate the cause(s) of the non
conformance and prevent any recurrence. Typical corrective actions consist of changes to tools,
equipment, facilities, processes, materials, drawings, specifications, procedures, etc.
For Minor NCR's the above responsibility remains with the Subcontractor's PA. EADS Astrium is to be
informed about the existence of such NCR, the progress, and the close-out with a right to re-classify to
Major NCR or to veto the corrective action or the close-out.
The NRB determines also preventive actions to avoid the occurrence of the non conformance on
similar items, as appropriate.
The NCR is closed-out only after :
•
All related actions have been performed and their results successfully verified.
•
All necessary inspections and tests have been performed, and their results verified and
reported on or traceable from the NCR.
•
Related RFWs are approved.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
22
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
6. MANAGEMENT REQUIREMENTS
The Subcontractor shall perform the work in line with management requirements specified in the
Management Requirements Specification [AD 5].
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
23
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
7. PRODUCT ASSURANCE REQUIREMENTS
The Subcontractor shall perform the work in line with PA Requirements specified in the PA
Requirements Specification [AD 3].
Any software developed or re-used for the deliverable items shall respect the Software PA
Requirements [AD 4].
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
24
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
8. ENGINEERING REQUIREMENTS
8.1 General
The Equipment Subcontractor shall co-ordinate all technical activities and the interfaces between the
different disciplines involved and shall manage the technical and commercial interfaces to EADS
Astrium and to the lower tier subcontractors and suppliers.
He shall analyse all requirements imposed by the applicable documents and shall derive/analyse
respective means to maintain compliance to the specification or propose a well founded other
alternative with minor impact on the compliance status to EADS Astrium.
If necessary the Equipment Subcontractor shall establish and maintain requirement specifications for
the lower level configuration items.
8.2 Equipment Design
The Equipment Subcontractor shall perform all design activities necessary to define the equipment
under his responsibility such that it meets all applicable requirements.
In case the equipment includes a controller with software, the software development shall ensure that
the development process is performed in accordance with the SW PA Requirements [AD 4] and the
relevant ECSS referred to therein.
Company internal software development standards shall be compared to the above mentioned
documents via compliance matrix. The acceptance of company internal standards is subject to
approval by EADS Astrium.
8.3 Interfaces
The Equipment Subcontractor shall perform interface engineering, design and manufacturing to
assure the compatibility and coherence of all physical and operational interfaces of the
Subcontractor's equipment.
The interface engineering between spacecraft system and Subcontractor equipment will be performed
by EADS Astrium. The Subcontractor shall review, complement and comment on the spacecraft ICDs
and finally confirm the interfaces related to his equipment by signature. For this purpose, the
Subcontractor shall issue an Interface Control Document for his equipment.
After approval of the ICD by EADS Astrium this issue is binding for the Subcontractor. Any change
needs the approval of EADS Astrium.
EADS Astrium reserves the right to define and provide machine readable formats like EXCEL tables of
XML (e.g. for harness data). Then the subcontractor shall migrate, maintain and deliver interface data
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
25
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
in this format. For the task of interface data exchange, the Subcontractor shall obey conventions and
rules given by EADS Astrium.
Appendix B provides an overview on the interface data and required formats. More specific
requirements are specified in the equipment specific SoW.
8.4 Operations
The Equipment Subcontractor shall investigate the operation and control of the equipment in relation
to the satellite operations and control.
He shall generate and maintain a User Manual for his equipment (derived from ECSS-E-70, Part 2,
equipment user manual content). As part of the User Manual, he shall develop flight operations
procedures for his equipment. The flight operation procedure steps shall use correct references to the
TM/TC definitions.
In case the Subcontractor delivers equipment which is either a PUS packet terminal for the on-board
data handling or non-PUS terminal equipments which can submit telemetry and receive
telecommands (provide a data interface), EADS Astrium will provide an empty TM/TC Database (in
MS Access 2003 format tbc.). The definition of the database and its user manual will be provided in a
set of documents (e.g. Satellite Database ICD, SDB). The applicability for which equipment type which
tables in the TM/TC database are to be populated is defined in [AD 7] SW-PL-EAD-SY-0019, Swarm
Engineering Data Repository Development Plan. The subcontractor shall migrate, maintain and deliver
the database with the telemetry and telecommand data for his equipment in accordance with the
Packet Utilization Standard and the Satellite Database ICD.
8.5 Analyses
The Equipment Subcontractor shall perform all analyses (e.g. thermal, structural, radiation, RAMS,
electrical) necessary to properly design, manufacture and verify the items under his responsibility wrt
the requirements made applicable in this SOW. The analyses shall at least encompass but not be
limited to the analyses explicitly required in the SOW.
The mathematical models and the necessary software tools shall be established by the Equipment
Subcontractor unless commercially available. The analyses results, the tools and the math models
shall be described.
Tools and models developed under the contract shall be delivered to EADS Astrium. In case the
model is used during operations and/or check-out on spacecraft level an adequate manual shall be
provided.
The analyses shall be performed / updated in accordance with the design progress of the equipment
and its lower level items. The analyses shall be described in a self standing way to allow an effective
review and understanding.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
26
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
8.6 Verification Task
The Equipment Subcontractor shall demonstrate that:
•
the design conforms to the requirements (qualification)
•
the flight hardware and software complies to the qualified design, is free of workmanship
errors and is fully functional (acceptance)
•
The requirements to be verified are identified in the applicable specifications by a unique
requirements numbers.
The verification of the requirements shall be performed on equipment level, wherever possible.
Verification on lower level is permitted. Higher level verification needs approval by EADS Astrium.
The Subcontractor shall maintain a Verification Control Document (VCD) which lists all applicable
requirements and the correlated verification activities.
More specific verification tasks, e.g. for software, are covered by the Specific SoW.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
27
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
9. EXPORT CONTROL REQUIREMENTS
9.1 General
The Equipment Subcontractor shall be responsible for ensuring compliance with all Export Control
Requirements of the European Union and the United States of America regarding exportation or reexportation of the goods and/or materials which are the subject of the present contract from EADS
Astrium. In order to achieve this, the Subcontractor shall be responsible for obtaining the following
tasks:
•
Identify whether your product is listed in the EU Export Control List and/or whether a national
export license from your government is necessary and available or not and inform EADS
Astrium accordingly.
•
Identify US-ITAR and US-EAR parts in your equipment and prove compliance with the existing
US re-export law.
•
Identify TAA's (Technical Assistance Agreements)
•
Provide copies of all licenses and TAA's identified above.
•
Certify your right to export your equipment to EADS Astrium GmbH (and to EADS Astrium Ltd
if applicable), which (in case of US-licenses) also allows EADS Astrium to re-export the
equipment to other intermediate consignees and to the end user ESA as destination and the
launch site.
9.2 EU Export Control Requirements
Concerning the export /re-export regulations of the subcontractor's country, the subcontractor has to
follow the rules of its government and/or the regulations of the EU.
9.3 Direct “US Supplier”
When the Subcontractor to EADS Astrium is a “Direct US Supplier”, the following provisions shall
apply between EADS Astrium and the Subcontractor:
9.3.1 Inputs from EADS Astrium to Support Subcontractor's Application
•
EADS Astrium cover letter
•
DSP-83 (for agreements or an export licence for classified 'defence articles')
•
EADS Astrium control plan, if available
•
EADS Astrium accountability plan (for DSP-5 export licence only)
•
Minutes of meetings, if any to the subject
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
28
SWARM
SWARM Generic Statement of
Work for Equipment
•
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
EADS Astrium information and requirements related to the agreement
9.3.2 Description of Subcontractor's Responsibilities
To draft the documentation that has to be prepared to make the application to the DOS;
To take into account in the documentation the information that EADS Astrium has transmitted via the
cover letter, the DSP-83 (for agreements or an export of classified 'defence articles) and associated
documents;
To inform EADS Astrium about any omission in the submitted cover letter and / or missing document
and not to venture any input as a replacement for a missing information;
To send the drafted relevant documentation to EADS Astrium for internal review before submission to
the DOS;
To inform EADS Astrium about the status of the application (preparation, submission, staffing,
authorisation, provisos…);
To pass on to EADS Astrium the DOS authorisation (i.e. the DTC original case number (for
agreements) or the licence number (for DSP-5 licence) , the text of the authorisation and provisos);
According to the ITAR regulation, to do the identification of the hardware, software, technical data and
information which are exported in the frame of the authorised agreement or export licence.
9.3.3 Outputs from Subcontractor
Drafted documentation including final issue that is submitted to the DOS;
TAA or Distribution Agreement as agreed with EADS Astrium, submitted to the DOS authorisation and
countersigned by both parties after DOS approval when applicable;
DSP-5 submitted to the DOS authorisation when applicable;
DTC original case number and licence number;
Copy of the DOS authorisation, including provisos;
Technical data and information identified as 'defence articles' as required by the ITAR rules;
H/W, S/W and relevant documentation (EIDP, etc) identified as 'ITAR controlled' as required by DOS.
9.4 Requirements for Lower Tiers ‘’US Suppliers’’
When the Subcontractor to EADS Astrium is not a “Direct US Supplier” but cooperates with US
Suppliers as Lower Tiers Suppliers, the requirements of paragraph 9.3 shall be applied between the
Subcontractor and its “Direct US Suppliers” and at any level between a Lower Tiers Supplier and its
“Direct US Supplier”, with all references to “EADS Astrium” changed to refer to the Subcontractor or
EADS Astrium.
In addition, the subcontractor to EADS Astrium shall:
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
29
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
•
Advise the DTC original case number(s) and licence number(s) to EADS Astrium;
•
Provide copy(ies) of the DOS authorisation(s), including provisos, to EADS Astrium;
•
Provide a copy of his own control plan, to EADS Astrium;
•
Ensure that all 'technical data and information' passed on to EADS Astrium or that all data and
information supplied to EADS Astrium which incorporates such 'technical data and information'
are identified as 'defence articles' as required by the ITAR rules;
•
Ensure that all 'H/W, S/W and relevant documentation (EIDP, etc)' passed on to EADS
Astrium or that all hardware, software and documentation incorporating any items subject to
such ITAR control, are identified as 'ITAR controlled' as required by DOS.
•
Flow down all the provisions of Paragraph 9.3 and above mutatis mutandis to each of his
lower tier Suppliers, down to the lowest tier of supply contract, unless otherwise agreed with
EADS Astrium. Hence, the Subcontractor shall ensure that the relevant data is provided to him
by these lower tier Suppliers, and passed up to EADS Astrium..
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
30
SWARM
SWARM Generic Statement of
Work for Equipment
10.
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
MANUFACTURING & TEST REQUIREMENTS
10.1 Introduction
The applicability of this section depends on design and development heritage and the according
categorisation of the equipment. Compliance to the tasks and documentation required in this section
may be established by reference to precursor projects. In any such case the subcontractor shall
provide the evidence of his compliance to the SOW.
10.2 Manufacturing and Production
The subcontractor shall maintain adequate facilities and personnel resources to sustain
manufacturing, assembly, testing, handling and transportation of hardware at all levels during the
programme in compliance with programme schedules. He shall ensure that the standards of in-house
and subcontracted manufacture are compatible with the requirements set forth in the PA
Requirements.
The subcontractor shall ensure that adequate documentation is available prior to start of any hardware
manufacture to describe all manufacturing processes, flow diagrams, planning, process control,
material application data, personnel, and facility certification.
The above shall be applied to production of software items mutatis mutandis.
In line with the PA Requirements [AD 3], all relevant process steps shall be recorded in the Equipment
Log Book.
10.3 Assembly Integration and Verification
10.3.1 MAIV Planning
The subcontractor shall generate, maintain and implement the MAIV Planning, defining all the
activities necessary to achieve the complete equipment manufacturing, integration, and verification of
his product. For simplification, this planning can be presented as part of the Design, Development,
and Verification Plan.
10.3.2 General Test Requirements
The subcontractor shall carry out all development, qualification and acceptance testing in accordance
with the approved Verification Plan, and any additional testing necessary to demonstrate the
performance requirements are met.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
31
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Equipment level testing intended for formal close-out of requirements shall be performed in a flight
representative configuration (i.e. flight hardware and software, flight interfaces) to the maximum
extend possible. This request shall also be applied to any removable extensions (e.g. PROMs).
In general and as far as feasible the subcontractor shall test on the highest integration level under his
control.
10.3.3 Life Tests
Equipments which are susceptible to wear, degradation, fatigue, or creep during their projected
lifetime (including time for fabrication, storage, ground testing and flight) shall be subjected to life tests,
under conditions representative of their intended usage.
Life tests shall be conducted on an accelerated basis to the maximum extent possible, considering the
dominant degradation factor (e.g. actuation for mechanical actuators).
Each equipment submitted to an accelerated life test shall demonstrate an adequate margin to be
agreed on a case by case basis according to the applicable standards. It is desirable that the life test
proceeds beyond that limit to the maximum extent practical in order to provide additional assurance of
the design margins.
Accelerated or real tests are considered as part of the qualification programme and as such shall be
conducted on after environmental qualification tests.
Following life testing, all equipment tested shall be disassembled and examined for any abnormality or
trends in degradation, and EADS Astrium informed of the results.
Life test reporting may be provided to cover equipment which have been life tested on previous flight
programmes.
No life test sample (e.g. EEE parts, boards, units) shall be used for flight applications.
10.3.4 Test Failure
Any failure during tests shall be reported verbally or by e-mail without delay (in advance to the formal
issue of the related NCR).
Any failure during qualification and acceptance tests as well as any failure of qualification models,
prototype models and flight models (as applicable) during the warranty period, shall be analyzed by
the subcontractor and a copy of this failure analysis report including corrective actions shall be
provided by the subcontractor.
Retro-fit of deliverable Breadboard or Engineering Models:
In case of failures or weaknesses causing a modification of the flight models (PFM and FM),
deliverable Breadboard Models or Engineering Models shall be reworked by the subcontractor on his
own cost to avoid differences between the flight equipment and their equivalents for ground tests.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
32
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
10.3.5 Verification Control
The equipment specification is available in the EADS Astrium DOORS database, thus giving to each
requirement a unique identifier. These identifiers shall be used for tracking of the verification planning,
execution and reporting on the level of individual requirements.
The subcontractor shall define the verification method as well as an appropriate assignment of the
verification level per requirement (with a preliminary definition included in his proposal).
For verification against a requirement the following methods are allowed:
•
Test
T
•
Analysis
A
•
Review of Design
R
•
Inspection
I
Generally, the verification of equipment requirements shall be performed on equipment level. This may
be delegated to lower level pending approval of EADS Astrium.
The subcontractor shall maintain a Verification Control Document (VCD) which lists all applicable
requirements and the correlated verification activities in particular the methods and integration level on
which verification will be performed.
The VCD shall cover the qualification and the acceptance program.
The verification control document shall preferably be maintained using DOORS in accordance to the
instructions and conventions for DOORS usage in the project, which will be provided by EADS
Astrium. If verification close out is intended on lower level, the corresponding lower level specifications
shall also be prepared, and the verification planning and tracking made using DOORS, preferably.
In case that the Subcontractor cannot work with DOORS, he is requested to propose an alternative,
electronic format. However, any alternative format requires agreement of EADS Astrium.
This is required to enable a tracing of requirements and their verification close out down to lower then
the equipment level. The VCD shall be provided to each major review and be part of the End Item
Data Packages.
The Verification Matrix shall be frozen and mutually agreed by the Subcontractor and the EADS
Astrium by CDR.
The Subcontractor shall demonstrate by AR that the verification of each requirement has been
successfully completed. He shall do this by means of the Verification Control Document.
The Verification Programme shall comply with the Swarm PA Requirements [AD 3] and Software PA
Requirements [AD 4].
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
33
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
10.4 Ground Support Equipment
The subcontractor shall be responsible for the provision, maintenance, calibration and validation of all
the necessary test equipment (e.g. electrical, mechanical, optical, thermal, fluidic, software) for
manufacture and test of the deliverable equipments.
All test fixtures and facilities shall be calibrated and validated. Validation routines shall be configured
and the results shall be stored at the Subcontractor plant against any test related investigations.
The equipment GSE may be subdivided into two categories: deliverable GSE for use in the higher
level AIT programme and launch campaign, and non deliverable GSE needed for the sole purpose of
the equipment AIT. The number of models of each type of GSE shall be in accordance with the
deliverable items list and the utilisation for equipment AIT.
Besides the safety and liability requirements defined by applicable laws, the deliverable GSE shall
comply with the requirements presented in the equipment specification, with the PA and Safety
requirements being part of the PA Requirements Specification [AD 3], as well as with the design
implementation requirements for EGSE, OGSE, MGSE, TGSE, and FGSE. Formal verification control
as defined in previous section shall be applied also to GSE requirements, as a minimum to those
requirements affecting safety and flight interfaces. In order to limit the effort for GSE verification in a
“stand alone” configuration, the verification “by use” may be an acceptable method for all deliverable
GSE that is used also for equipment level AIT.
In case of deliverable GSE, the equipment shall be delivered with all the necessary documentation
required for the operation and for the maintenance of the GSE.
The design of equipment GSE to be delivered to higher level AIT shall be validated by use in the
frame of equipment AIT. According warranty agreements shall be closed with vendors of COTS
equipment included in the GSE.
The subcontractor shall ensure that the deliverable GSE is able to fulfil its requirements and is
correctly and sufficiently documented. The subcontractor shall ensure that maintainability
requirements are fulfilled and define a maintenance plan.
GSE which is not a deliverable item to EADS Astrium may be constituted from the subcontractor's or
his lower level supplier's inventory of laboratory and test equipment. In any such case, the GSE shall
be kept available to SWARM and operational throughout the warranty period or latest until lift-off of all
SWARM spacecraft.
The subcontractor shall ensure that these GSE and related documentation, manuals and software are
subject to configuration management and control.
WEEE - Waste Electrical and Electronic Equipment /
RoHS - Restriction on the use of certain Hazardous Substances:
The subcontractor guarantees the compliance with EC WEEE directive 2002/96/EC and RoHS
directive 2002/95/EC and their respective implementations into national laws. Therefore, inter alia, the
subcontractor will take back the supplied electric- and electronic equipment after end of their livetime
according to these rules without charge to EADS Astrium.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
34
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
CE (Declaration of Conformity):
The subcontractor shall ensure that the delivered GSE is "CE marked" to indicate the compliance with
the applicable EU New Approach Directive (98/34/EC and 98/48/EC), irrespective of the GSE sites of
usage.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
35
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
SUPPORT TASKS
11.
11.1 Introduction
In order to be able to provide technical support after delivery of the equipment the subcontractor shall
ensure that technically qualified and project experienced personnel can be made available to support
the activities at higher level. This shall cover the period between equipment delivery up to lift-off of all
SWARM spacecraft.
Furthermore if the project should foresee a storage period before launch, then the constraints of this
storage shall be considered and the equipment needed for retest and possible repair kept in working
order by the subcontractor until notice has been made that this is no longer required.
11.2 Support to Higher Level Reviews
The subcontractor shall support reviews at higher level by preparation of presentation material for the
perimeter of his equipment and by personnel attendance if required to treat equipment related topics
at higher level reviews.
11.3 Support to AIV at Higher Level
11.3.1 EGSE Operation Support
For each of the equipment EGSE to be used at higher level, the subcontractor shall provide support as
follows:
On site support to equipment integration with other EGSE elements and the flight equipment to be
provided for the first EGSE model of each type to be delivered (estimate duration several days)
•
user teaching and training sessions based on the subcontractors estimated effort
•
fast maintenance / repair service on a time and material basis (when not covered by
warranty), including:
•
o
24 hour response time for fast trouble shooting and first aid advice to the check-out
team (weekends to be included during critical test periods)
o
Replacement/repair service for commercial equipment to guarantee a minimum
equipment outage of not more than 48 hours
regular maintenance / calibration up to launch (or longer if required for mission support) for
both commercial equipment and own production
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
36
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
11.3.2 Integration and Test Support
The subcontractor shall support the integration and test of the equipment at higher level by the
following activities:
•
Assistance to the integration and operation commissioning on the satellite/ subsystem.
•
Assistance to satellite/ subsystem related special function and performance tests
The subcontractor shall commit to providing further support on time and material cost basis (when not
covered by warranty), including in particular 24 hour response time for fast trouble shooting and first
aid advice to the satellite AIV team for all models (weekends to be included during critical test periods)
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
37
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
12. APPENDIX A DOCUMENTATION REQUIREMENTS LIST
The set of documents required to be delivered is defined in the Specific SoW.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
38
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
13. APPENDIX B INTERFACE DATA REQUIREMENTS
13.1 Computer Aided Drawing and Design (CAD) data
13.1.1 EADS Astrium CAD system
Note: As the Swarm configuration is under control of EADS Astrium Ltd. The CAD data have to be
compliant with their system.
The EADS Astrium standard CAD system is: CATIA© version CATIA V5.14.4 (English) Any change
will be notified by EADS Astrium and impacts reviewed with the Supplier.
13.1.2 CAD Data Exchanges
For accommodation or analysis purpose, CAD models shall be provided for every equipment to be
delivered to EADS Astrium. The standard format, for CATIA© data exchanges between the Supplier
and EADS Astrium is the CATIA© version format, native or catexport.
Should the Supplier use another CAD tool system, the Supplier shall be responsible for performing
and guaranteeing the conversion into the EADS Astrium CATIA© version data format.
The level of detail / degree of complexity of the deliverable CAD models shall be discussed and
agreed with EADS Astrium so that the file size is not unnecessarily big.
The rules shall be defined and be confirmed by both sides in a written form. The data exchange
agreement (DEA) shall at least contain/define:
◊
Kind of data exchanged
◊
rules for the structure, naming and numbering of the files
◊
A reference to this document to define the general requirements for data transfer
◊
The data quality (volumes or solids with history / structure of models / max. filesize)
◊
Procedure for the control / acceptance of the data
◊
The type of transfer (CD / FTP)
Figure 13.1-1 shows a typical flowchart for the data transfer process.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
39
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Figure 13.1-1: Flowchart for CAD data exchange
A general test of the data exchange process shall take place BEFORE the main project work starts!
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
40
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
13.1.3 General Preparation of CAD Data
To minimize the effort of dealing with the exchanged data, the following topics shall be regarded
before the transfer:
◊
delete all unnecessary geometry (e. g. hidden parts, standard parts, parts inside a box, when
the
◊
box is needed for clash detection only)
◊
delete all supporting elements where possible (e. g. wireframes for 3D geometry)
◊
all geometry / drawings must be updated
◊
all links to local libraries / catalogs must be eliminated
◊
Country specific characters like ß, Ä or â are not allowed for any text or description (2D and
3D)
◊
Special characters in the file names are not allowed. In order to stay compatible with Unix
and Windows OSs, only the following have to be used:
Characters A…Z, a…z
Numbers: 0…9
Symbols: _ (underscore), - (minus sign)
For more details on the CAD models and associated level of refining required per type of equipment,
the Supplier shall refer to the equipment specific SOW.
13.1.4 CAD Data Deliveries
The CAD models to be delivered to EADS Astrium are overall configuration information only, i.e.
similar to the I/F information to be given in the ICD.
Finite Element Models and/or Thermal Mathematical Models may be required in addition.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
41
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
13.2 Engineering Data
13.2.1 EADS Astrium Engineering Data Repository
The EADS Astrium Swarm Engineering Data Repository comprises the needs for information of
various engineering disciplines in order to develop and test the Swarm satellites.
Figure 13.2-1 depicts the users which are linked to the Swarm Engineering Data Repository. This
repository consists of various dedicated database or information in electronic format. The required
data or information is indicated at the links between the user and the repository.
The following section will provide a definition on how these data shall be provided from equipment /
unit suppliers to EADS Astrium Swarm prime team but excluding CAD Model which is described in
section 13.1 .
Telemetry & Telecommands
User Manual (Functions & Modes)
Flight Operations
CAD Model
Interface Description & Drawings
Assembly Drawings
Telemetry & Telecommands
User Manual (Functions, Modes)
Flight Operations
Operations Engineering
Telemetry & Telecommands
User Manual (Functions, Modes)
Flight Operations (incl. Safe Mode)
Simulation Models
AIT Engineering
AOCS Engineering
Thermal Engineering
Contact Surface
Heat flux
Power dissipation vs. equipment modes
Thermal Mathematical Models or
Finite Element Models
Swarm
Engineering Data
Repository
Mechanical Engineering
Electrical Engineering
Electrical Architecture
Electrical Interfaces
Grounding Diagram
Harness to Pin Allocations
Assembly Constraints (w.r.t EMC & Harness)
EMC Properties
Magnetic Properties
Mass & Mass Properties (CoG, MoI)
Volume
Assembly Drawings
Assembly Constraints
CAD Model
Finite Element Models
Figure 13.2-1: Overview on Users of Swarm Engineering Database Repository
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
42
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
13.2.2 Engineering Data Exchange
This section describes the required data and data format and the process in order to exchange the
data between supplier to the Swarm Prime at EADS Astrium.
Locally at each site where parts of the data of the Swarm Engineering Data Repository are generated,
the relevant but identical part of the Swarm Engineering Data Repository shall be established. For
instance the Swarm Satellite Database (S-SDB) shall be established at On-Board Software
subcontractor and at EADS Astrium level to support a proper definition, verification and exchange of
the relevant data.
Therefore the delivery of any data shall be according the following process depicted in Figure 13.2-2.
Prepare Data
Sender
Verify Data
Notice of transfer of Data
Precondition !
Exchange Standards
in Data Format
Selected Transfer Media
Agree on
Data format & transfer
N
Notice of receipt of Data
Receiver
Verify Data
Notice of Acceptance
Figure 13.2-2: Data Exchange Process for Swarm
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
43
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
This means the subcontractor prepares & verifies the data in
a defined format for the data
for a defined data transfer media.
according Swarm project naming conventions (e.g. for S-SDB telecommand and telemetry
descriptions)
in a defined format for filenames to indicate where the data has been populated
nnnn_XXXX_V_x_y_z
nnnn
Name
C
OPS
OBSW
ACC
ASM
EFI
GPS
STR
VFM
ESOC
AIV
TBD
the Central (=Master) SDB
generated by Operations Team at Prime
deliveries from OBC S/W contractor
deliveries from ACC contractor
deliveries from ASM contractor
deliveries from EFI contractor
deliveries from GPS contractor
deliveries from STR contractor
deliveries from VFM contractor
deliveries to ESOC
deliveries to Prime AIV / EGSE
to be defined by delivery from other contractors
Table 13.2-1: Definition of Site names related to file naming convention for data exchange
XXXX
Type
SDB
SMOD
TMM
FEMT
FEMS
TMD
MPD
HCPA
FOP
TBD
Satellite Database
Simulation Model
Thermal Mathematical Model
Finite Elemet Model Thermal
Finite Elemet Model Mechanical/Structural
Thermal Data
Mass Property Data (CoG, MoI)
Harness Connector to Pin Allocation List
Flight Operations Procedure
to be defined, for delivery of any other data
Table 13.2-2: Definition of Type names related to file naming convention for data exchange
V_x_y_z
x
version /
y
release
z
x = Version Number
y = Release Number (is reset when Version is
incremented)
z = Update Number (is reset when Version is
incremented)
Table 13.2-3: Definition of Version, Release and Update Number related to file naming
convention for data exchange
New Versions are generated in case of a significant change (e.g. a new subsystem / instrument or
new onboard software is included).
New Releases are documented by a ’Release Note’ and will be generated for each ’Delivery’ (from
subcontractor to Prime and / or from EADS Astrium to ESA).
A new Update is generated whenever needed (e.g. when change requests have been incorporated
and are to be tested).
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
44
SWARM
SWARM Generic Statement of
Work for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
The following table provides the list of data to be exchanged (please note this list may not be
complete, therefore please refer also to the equipment specific SoW for details) and the Software type
(e.g. drawing, MS Excel, MS Access).
Item
Mass, Power
Consumption
& Dissipation
and data rate
properties
Volume
Thermal data
Connector
location
Fixing location
Grounding
stud
Unit TM/TC
Parameter &
Packet
Definitions
Description
Maximum equipment mass including connectors and other
parts
Power Consumption vs. Equipment Modes
Power Dissipation vs. Equipment Modes
Data Rate vs. Equipment Modes
Applicability of which tables are to be populated for
equipments & materials(tbc) are defined in [AD 7] SW-PLEAD-SY-0019
Lay out of the equipment in 3 dimensions with each
dimension given as maximum including equipment
connectors and other parts
Contact surface (with shaping) with each size at a precision
of 10%
Heat flux (with repartition if non-homogeneous) at a
precision of 10 %
Dissipation for each operational mode(including start up,
heating, different functioning modes if any) with a precision
of 10 %
Connectors identification, position and orientation
(electrical, waveguide, coax) on each side of the
equipment.
Position of all fixings.
Location and number of grounding stud
Definition of telecommands with associated type.
Definition of of telemetry with associated type.
For Pus packet and non-PUS packet terminals which are
data terminals.
Applicability of which tables in the S-SDB are to be
populated for PUS and non-PUS terminals are defined in
[AD 7] SW-PL-EAD-SY-0019
Format
MS Access,
MS Excel
CAD Model
MS Excel or
MS Word
CAD Model
CAD Model
CAD Model
MS Access
An S-SDB tool will be provided by EADS Astrium
Harness
Connector Pin
Allocation
Table
Allocation of harness signals to unit connector pins
Applicability of which tables in Harness to Pin Allocation DB
are to be populated for equipments having electrical
interfaces are defined in [AD 7] SW-PL-EAD-SY-0019
Either
MS Access or MS
Excel
Example will be provided by EADS Astrium
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
45
SWARM
SWARM Generic Statement of
Work for Equipment
Item
Unit User
Manual
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
Description
According DRD, but including Functional Block Diagram
and Correlation to Modes and related Telemetry /
Telecommands
Format
Word format
Example will be provided by EADS Astrium in the DRD
Unit Flight
Operations
Procedures
Flight Operations Procedures; to be delivered as part of the
User Manual
Word format
Example will be provided by EADS Astrium
Electrical
Interface
schematics
Grounding
diagram
Assembly
Constraints
Magnetic
Properties
EMC
Properties
Complete equivalent interface schematics with EEE
properties
Drawing
Unit internal grounding diagram including designation of
grounding and isolation, interface types, grounding lines
both for signal and power lines.
Maximum Distance affordable between units within the
assembly
Specific requirements if any (twisting, shielding,
intermediate harness length, etc.)
Drawing
Magnetic Vector Position and Orientation
MS Excel
Definition of Notches, Frequency Plan, a.s.f.
MS Excel
CAD Model and
overall
configuration
drawing or ICD
Table 13.2-4: Definition of information in electronic format for data exchange between EADS
Astrium and subcontractors
Deliveries for information defined in Table 13.2-4 shall be provided in the format as defined above
when delivering the ICD document except for User Manual, S-SDB and Flight Operations Procedures.
The delivery of ICD is defined in the Documents Requirements List of the specific SoW.
The delivery of the User Manual is defined according the Document Requiremenst List in the specific
SoW.
The delivery of the unit S-SDB and of Unit Flight Operations Procedures shall be triggered by event.
Events are for instance Software Updates or major updates to ICD.
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
46
SWARM
SWARM Generic Statement of Work
for Equipment
Doc. No:
SW-SW-EAD-SY-0003
Issue:
2
Date:
10.04.2006
INTENTIONALLY BLANK
© EADS Astrium GmbH
File: SW-SW-EAD-SY-0003_2_SWARM_generic_SoW.doc
Page
47