Beruflich Dokumente
Kultur Dokumente
Checked by:
Product Assurance:
Project Management:
Copying of this document, and giving it to others and the use or communication of the
contents there-of, are forbidden without express authority. Offenders are liable to the EADS Astrium GmbH
payment of damages. All rights are reserved in the event of the grant of a patent or the D-88039 Friedrichshafen
registration of a utility model or design.
Issue: 0
EGSE Specification
Date: 25.02.2006
Table of Contents
Page
1. Introduction ..................................................................................................2
1.1. Scope .......................................................................................................................... 2
1.2. Purpose ....................................................................................................................... 2
1.3. Terms and Definitions ................................................................................................ 3
1.4. References .................................................................................................................. 4
1.4.1. Applicable Documents .................................................................................... 4
1.4.2. Reference Document ....................................................................................... 4
1.4.3. Standards ......................................................................................................... 4
1.5. List of Acronyms ........................................................................................................ 5
Issue: 0
EGSE Specification
Date: 25.02.2006
5. Implementation Requirements..................................................................34
5.1. General ..................................................................................................................... 34
5.2. Lifetime .................................................................................................................... 34
5.3. Safety........................................................................................................................ 34
5.4. Cleanliness................................................................................................................ 35
5.5. Parts & Materials ...................................................................................................... 35
5.6. Maintainability & Reliability.................................................................................... 35
5.7. Interchangeability & Replaceability ......................................................................... 36
5.8. Transportation & Container...................................................................................... 36
5.9. Environment ............................................................................................................. 37
5.10. Ergonomy ................................................................................................................. 38
5.11. Mechanical & Thermal Design................................................................................. 39
5.12. Electrical & EMC ..................................................................................................... 40
5.13. Software Design & Development............................................................................. 44
5.14. Workmanship ........................................................................................................... 45
5.15. Identification & Marketing ....................................................................................... 45
6. Verification Requirements.........................................................................47
Issue: 0
EGSE Specification
Date: 25.02.2006
Page
Figure 2-1 SVF............................................................................................................................. 7
Figure 2-2 RTB ............................................................................................................................ 8
Figure 2-3 extended RTB ............................................................................................................. 9
Figure 2-4 STB........................................................................................................................... 10
Figure 2-5 Satellite EGSE .......................................................................................................... 11
Figure 2-6 Launch Site EGSE .................................................................................................... 12
Figure 2-7 RF Suitcase ............................................................................................................... 13
Figure 2-8 static SVF configurations ......................................................................................... 16
Figure 2-9 EGSE evolution ........................................................................................................ 17
Figure 3-1 CCS Schematic ......................................................................................................... 18
Figure 3-2 CCS Links ................................................................................................................ 19
Figure 3-3 TM/TC Front End Equipment Block Diagram ......................................................... 20
Figure 3-4 S-Band SCOE Blockdiagram ................................................................................... 22
Figure 3-5 Power SCOE basics .................................................................................................. 23
Figure 3-6 Solar Array Simulator (SAS) SCOE......................................................................... 24
Figure 3-7 LPS SCOE ................................................................................................................ 25
Figure 4-1 EGSE LAN Topology using unshielded Cable ........................................................ 32
Figure 4-2 EGSE LAN Topology using Fibre Optics ................................................................ 32
Figure 5-1 EGSE Grounding Schematics................................................................................... 41
Figure 5-2 Software Layers........................................................................................................ 44
Figure 5-3 Harness Identification - Example ............................................................................. 46
Issue: 0
EGSE Specification
Date: 25.02.2006
1. Introduction
1.1. Scope
This specification establishes a baseline for the Swarm Electrical Ground Support Equipment (EGSE).
1.2. Purpose
The purpose of this specification is to define the common requirements applicable to all Electrical Ground Support
Equipment (EGSE) used in the various configurations constituted during Swarm development, AIT and AIV. Thus,
this specification is conceived as a higher level applicable document to all EGSE items, the CCS, the Front Ends /
SCOEs and instrument specific EGSE.
Unless explicitly expressed by name, all requirements outlined in the dedicated requirement sections below belong
to any SCOE and Front End Equipment as well as any Instrument EGSE1. Both, SCOE and Instrument EGSE are
referred to as Front End Equipment (FEE) as they are both considered front ends from the CCS point of view.
The requirements also apply to the CCS in so far as the CCS interfaces the functions / capabilities required by the
Front End Equipment.
Requirements Identification:
Technical requirements given in this specification which are to be subjected to compliance statement and formal
verification control are identified within the text by using a formal formatting scheme. Each requirement has a
headline identifying the requirement ba a paragraph number , a keyword or short description and a proposed /
preferred verification method. Underneath this headline the requirement wording (and figures) are given. In some
cases the requirement is complemented by a comment or descriptive text. A comment is separated by horizontal
lines and has italic letters.
Issue: 0
EGSE Specification
Date: 25.02.2006
AIT/AIV Data Base Database containing all definitions for all data structures (TM/TC packets,
TM/TC parameters, monitoring definitions, calibration curves, limit sets, e.t.c)
subject to the spacecraft and all EGSE Front End / SCOE units.
Automated Procedure Test program (application) written by the user in a high level command
language to control the execution of a test. Contains statements to send
commands to the spacecraft and to other EGSE items and to process the
telemetry and other data coming from the S/C and other EGSE items.
(synonym: Test Sequence, Control File)
C&C Message ASCII data structure replacing the entire source packet "Application Data
Field" of a standard TC Source Packet. These packets are used to exchange
commands and feedback data between the CCS and SCOEs / Front End
Equipment.
Feedback Data Data from a SCOE representing either measurement data from the spacecraft
or data directly measured at a dedicated spacecraft interface.
Instrument EGSE is defined to be an instrument science data acquisition and processing unit
usually derived from the dedicated instrument unit test equipment re-used at
higher level EGSE configurations, commanded and controlled via the CCS.
MDVE constituted by development configurations in their early stages using pure S/W
simulation models for the S/C and the unit(s) under test (e.g. the SVF having
no hardware in the loop). In a next step hardware in the loop is used (e.g. the
on-board processor) whereas other units are still represented by software
simulation models (e.g. the RTB operating at least the real on-board processor
hardware connecting its real physical and electrical interfaces via the
Simulation FE and simulating the spacecraft environment by means of the
RTS). S/C EGSE not involving simulators (i.e. not making use of "models"
and not used for "Development" of on-board SW) are not considered member
of the MDVE philosophy.
SCOE Set of (electronic, magnetic, optical, etc.) equipment to stimulate and/or
simulate the S/Cs interfaces like sensors and actuators and/or other units (e.g.
sun, batteries, ...)
Script A list of procedure language commands stored in an ASCII disk file. During a
Test Session a script can be called by file name and the commands contained
are interpreted and executed sequentially (similar to DOS batch file).
Stimuli Commands Command to a SCOE to execute a stimulation of a spacecraft interface.
Structure Identifier Field within the "Application Data Field" of a TM/TC Source Packet
identifying the data structure provided with this packet.
TC Source Packet Packet according to \SD1\ "ESA Packet Telecommand Standard" for
commanding the spacecraft.
Test Environment Contains the executables of all (user-) data to conduct a test. It mainly
comprises a configuration specific sub-set of AIT/AIV Data Base data for the
spacecrafts actual as-built-configuration, the relevant automated procedures
and synoptics.
Test Session running a test at "Run-Time" using a dedicated Test Environment.
TM Source Packet Packet according to \SD2\ "ESA Packet Telemetry Standard" providing
housekeeping data either from the spacecraft or from any other SCOE / Front
End Equipment.
Issue: 0
EGSE Specification
Date: 25.02.2006
1.4. References
1.4.3. Standards
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
On-Board SW
(incl. AOCS SW)
Equipment Models
OBC HW
Model
Simulator I/F
LAN
CCS
Satellite I/F Handler
Reference CCS
Database AIT CCS MMI
(SRDB) DB Kernel
Test Result Database EGSE_Configurations.vsd/SVF
Issue: 0
EGSE Specification
Date: 25.02.2006
OBC BB -> EM
Telecommand Mass
Decoder Memory
Environment Models
Equipment Models O/B SW
Load & Dump
S/C & Environment / Real-Time Station (TE)
Simulator
EGSE LAN
CCS
Satellite I/F Handler
Reference CCS
Database AIT CCS MMI
(SRDB) DB Kernel
EGSE_Configurations.vsd/RTB Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
Test Harness
OBC BB -> EM
tbd. Telecommand Mass
STR
Decoder Memory
tbd. Electronics
GPS
Heads DC/DC Telemetry RS422, UART, SW Load
RS422 Discrete I/O A/D, D/A
Converter Encoder I/F
PL Science Data
TM Bypass
TC Bypass
Power
STR LCL/FCL
external I/F Unit &
TM/TC Baseband
S/C (Avionics)
Emulation
OGSE Processor HW Interfaces
Simulator I/F S/C / Avionics
Simulation FE
Environment Models
Equipment Models O/B SW
Load & Dump
S/C & Environment / Real-Time Station (TE)
Simulator
LAN
CCS
Satellite I/F Handler
Reference CCS
MMI
Database AIT CCS
DB Kernel
(SRDB)
EGSE_Configurations.vsd/eRTB Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
S-Band RF
TM Bypass
TC Bypass
Measurement &
Sense Lines
PL Science
Data
TC
TM
C&C
C&C
C&C
TM
C&C
TC
LAN
CCS
Satellite I/F Handler
Reference CCS
Database AIT CCS MMI
(SRDB) DB Kernel
EGSE_Configurations.vsd/STB Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
Spacecraft GPS
ACC
EFI
STR ASM
AOCS Electronics ASC
Battery PCDU S-Band OBC Sensors VFM
Heads
TM Bypass
TC Bypass
S-Band RF
Measurement &
Sense Lines
PL Science
Power
Data
TC
TM
O/B SW
Load & Dump
external OVP / OCP
RF Matching Unit Station (TE)
Solar-Array
Simulation TX RX STR
Modulator Demod. external I/F Unit &
28V
28V TM/TC Baseband OGSE
Battery Test & Measurement Processor
Main-Bus
Charge Equipment
Power Supply Instr.
Power Supply
EGSE
TC TM
Power S-Band I/F to NDIU Instrument EGSE
SCOE SCOE (provided by ESOC) Equipment
TM/TC FE details t.b.d.
C&C
C&C
C&C
TM
C&C
TC
LAN
CCS
Satellite I/F Handler
Reference CCS
Database AIT CCS MMI
(SRDB) DB Kernel
EGSE_Configurations.vsd/SAT Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
Spacecraft
TM Bypass
TC Bypass
Measurement &
Power
Sense Lines
Umbilical
Interfaces
TM
Power I/F to NDIU
(provided by ESOC)
SCOE
TM/TC FE
C&C
TM
C&C
TC
LAN
CCS
Satellite I/F Handler
Reference CCS
Database AIT CCS MMI
(SRDB) DB Kernel
EGSE_Configurations.vsd/LEG Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
2.1.6. RF-Suitcase
For ground system S-Band transmitter and receiver verification a RF Suitcase configuration will be provided as
shown in Figure 2-7 below.
Payload
TM S-Band
S-Band RF-Link Ground
HK TM
OBC (EM) Station
Transponder RX / TX
TC
TM Bypass
TC Bypass
Power
Power
external I/F Unit &
LCL/FCL
TM/TC Baseband
Emulation
Processor
Power FE TM/TC FE
C&C
C&C
TM
TC
LAN
CCS
Satellite I/F Handler
Reference CCS
CCS MMI
Database AIT
(SRDB) DB Kernel
EGSE_Configurations.vsd/RFS Test Result Database
Issue: 0
EGSE Specification
Date: 25.02.2006
Instrument EGSEs - - X X - -
STR OGSE - - X X - -
Table 2-1 EGSE Components Usage
Config # Remark
SVF 3 SVF #1 - located at O/B S/W developer / sub-contractor
SVF #2 - located at ISVV sub-contractor
SVF #3 - located with RTB
RTB & eRTB 1 generic EGSE configuration
RF Suitcase 1 no dedicated hardware; temporary use of RTB and CCS from SVF-3
STB 1 generic EGSE configuration
SAT-EGSE 3 Satellite EGSE #1 - constituted by STB
Satellite EGSE #2 - integrate at different location, operate two S/C simultaneously
Issue: 0
EGSE Specification
Date: 25.02.2006
S/C Simulation FE
Pwr SCOE - SAS
Instrument EGSE
Pwr SCOE - LPS
Components
S-Band SCOE
STR OGSE
TM/TC FE
Power FE
CCS
EGSE
Configurations
SVF-1 1 0 0 0 0 0 0 0 1 1 0 0
SVF-2 1 0 0 0 0 0 0 0 1 1 0 0
SVF-3 1 0 0 0 0 0 0 0 1 1 0 0
RTB 1 1 1 0 0 0 1 1 1 0 0 0
recruited from RTB
eRTB X X X 0 0 0 X X X 0 0 tbd. + GPS + STR + tbd.
recruited from RTB & SVF-x
RF-Suitcase X X X 0 0 0 0 0 0 0 0 0 (SVF CCS used for launch support)
STB 1 1 0 1 1 1 1 0 0 0 tbd. 1
Satellite-EGSE-1 X X 0 X X X X 0 0 0 X X recruited from STB
Satellite-EGSE-2 1 1 0 1 1 1 1 0 0 0 tbd. 1
reduced EGSE configuration:
S-Band SCOE & O/B S/W Load PC shared
Satellite EGSE 3 1 1 0 X 0 1 X 0 0 0 0 0 with Sat EGSE-1 or -2 as needed
no SAS SCOE will be provided for this
configuration
Launch Site EGSE-
X X 0 0 0 X 0 0 0 0 0 0 recruited from Sat-EGSE-1
1
Launch Site EGSE-
X X 0 0 0 X 0 0 0 0 0 0 recruited from Sat-EGSE-2
2
Launch Site EGSE-
X X 0 0 0 X 0 0 0 0 0 0 recruited from Sat-EGSE-3
3
total 7 4 1 2 2 3 3 1 4 3 0 2
Issue: 0
EGSE Specification
Date: 25.02.2006
CCS SVF-3
(SVF Config.)
OBC Sim SVF-3
(Gaisler ERC32)
Simulation PC 3
(Linux PC)
S/C Environment
/ Real-Time Sim
Issue: 0
EGSE Specification
Date: 25.02.2006
CCS Sat-0
(Satellite Config.)
CCS Sat-0 CCS Sat-0 CDMU
(Satellite Config.) CDMU (Satellite Config.) CDMU TM/TC FE EM
EM EM Set-0
TM/TC FE TM/TC FE
Set-0 Set-0 RTB &
Power FE
eRTB
Launch
RTB &
Power FE RF-Suitcase Support
eRTB
EGSE
Simulation FE RF-Suitcase
Power FE
Simulation FE
tbd Real-Time Sim
S-Band
HW in the VME / VXworks tbd
Real-Time Sim Transponder
loop HW in the S-Band
VME / VXworks
loop Transponder
OBC S/W Load
OBC S/W Load PC Set-3
PC Set-3
TM/TC FE TM/TC FE
Set-3 Set-3
Sat Launch Site
EGSE 3 EGSE 3
S-Band SCOE
Set-1 or Set-2
Usage shared between
Satellite EGSE Set-1 or Set-2 LPS SCOE LPS SCOE
and Satellite EGSE Set-3 as Set-3 Set-3
needed
OBC S/W Load
PC Set-1 or 2
Issue: 0
EGSE Specification
Date: 25.02.2006
CCS
DB
AIT/AIV C&C Pkt exchange
TM/TC
Population DB
S/C TM Pkts
Site LAN
Test Data
retrieved
TRDB S/C TM Pkts
forwarding to Instrument EGSE
Raw Data
The CCS is suited to command and monitor in real-time the test specimen (S/C- unit, subsystem or system) and all
EGSE elements for the real or simulated space segment (MDVE / SVF) during all relevant steps of the specimen
integration and testing.
The CCS generates and process TM and TC data in compliance to the following standards:
ESA Packet Telecommand Standard
ESA Packet Telemetry Standard
ESA ECSS PUS Standard tailored to Swarm
The CCS allows to perform the following main functions in parallel
Test preparation functions
Structuring and populating the satellite/mission database
Generating and editing Automated Procedures
Preparing Synoptic Pictures
Issue: 0
EGSE Specification
Date: 25.02.2006
TM/TC FE
Controller
C&C Msg
EGSE HK TM
S/C TM Pkts
S/C TC Pkts
TM/TC FE TC Echo Pkts
S-Band C&C Msg
I/F Handler
SCOE EGSE HK TM
C&C Msg
EGSE HK TM
[S/C TM Pkts]
C&C Msg
[TC Echo Pkts]
EGSE HK TM
LPS SCOE LPS SCOE CCS Instr. EGSE Instr. EGSE
Controller I/F Handler Kernel I/F Handler Controller
SAS SCOE
I/F Handler
SAS SCOE
C&C Msg
Controller EGSE HK TM CCS_logical_links.vsd
Legende: C&C Msg : Command and Control messages for remote control from CCS
EGSE HK TM : FEE / SCOE specific House-Keeping Telemetry Source Packet(s)
[] : optional these kind of packets can be provided to Instrument EGSE upon request
Issue: 0
EGSE Specification
Date: 25.02.2006
S-Band
TM Bypass A / Nominal
TC Bypass A / Nominal
Transponder
S-Band RF-Link
S-Band SCOE
TM/TC Front End
Switch Unit
TC (RF)
TC TC Echo TM
Encoder Decoder Decoder
TM (RF)
TM/TC FE GUI
EGSE LAN to Core EGSE
TC Echo Pkts
TM to NDIU
S/C TC Pkts
TM
Archiving
C&C Pkt exchange
Issue: 0
EGSE Specification
Date: 25.02.2006
TM & TC Simulation
TM Transfer Frames and / or TM Packets archiving
Remote Interface to the Core EGSE via the EGSE LAN (Ethernet using TCP/IP protocol). This
connection is used to enable the Core EGSE to command and monitor the TM/TC Front End unit.
the TM/TC Front End responsible for:
Recovering TM Transfer Frames from a serial bit stream
TC packets encoding and transmitting CLTUs in the correct serial format
Receiving serial CLTUs and decoding to retrieve TC pakets
the Switch Unit responsible for the interfacing, isolation and proper routing of TM/TC signals from
all sources/destinations. It interfaces the spacecraft, the S-Band SCOE as well as the NDIU:
The interface with the spacecraft consists of Nominal and Redundant TM NRZ-L (Clock and
Data), plus Nominal and Redundant TC NRZ-L (Enable, Clock and Data).
The interfaces with the S-Band SCOE are:
- TM NRZ-L (Clock and Data) from the S-Band SCOE,
- TC NRZ-L (Clock, Data & Enable) to the S-Band SCOE, and
- TC NRZ-L (external Clock) from the S-Band SCOE
Note: TC external clock is provided to fulfill ESA RF Modulation Standard requiring bit
change on sub-carrier frequency zero-crossing.
The interfaces with the NDIU are: TM NRZ-L (Clock and Data) and TC video.
Issue: 0
EGSE Specification
Date: 25.02.2006
Receiver
TM/TC RF
FE Matching S/C
Unit
Transmitter
Command
& Control
S-Band Measurement
EGSE LAN Devices
(to CCS) SCOE Controller
S-Band SCOE
Issue: 0
EGSE Specification
Date: 25.02.2006
STB-2
LPS SCOE Bracket PCDU
FCL
30 m LPS cable
Mainbus
Power Supply OVP sense lines FCL
to S/C consumers
BBPS
Battery Power
Supply OVP sense lines
BAPS
FCL
Mainbus Voltage HK
TM Battery Voltage HK
Acquisition Battery Current HK FCL
Battery Battery
Relay
SAS SCOE
30 m SAS cable
SAS
SAS Power
Power Sequential
SAS Power
Supply Shunt Shunt
Supply OVP sense lines
Supply
PSxx Stage x Regulation
PSxx
PSxx 11 stages
Issue: 0
EGSE Specification
Date: 25.02.2006
SAS 02
SAS Data
SAS 03
Power Supply
SCOE Acquisition SAS 04
Power Supply
Controller and Power Supply
Commanding
SAS 10
SAS 11
Power Supply
Power Supply U
external
OVP/OCP
Module I
Issue: 0
EGSE Specification
Date: 25.02.2006
external U
OVP/OCP
Module I
current
comparator 500 mA
ref.
Mainbus voltage HK
voltage
comparator
LPS Battery voltage HK
SCOE
Controller under-
voltage (UV)
Data protect analog measurement
5 channels
Acquisition
and analog Thermistor
6 measurement channels
Commanding
6
Power Supply
S/C relay
6 Relay Status channels contact
Bipolar High Power
4 Pulse Command lines
BHP / SHP
Standard High Power
Pulse Cmd
6 Pulse Command lines
Modules
10
Simulated
10 Separation Switches
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
4. Communication Requirements
This chapter establishes requirements for all FEE which shall be operated by the CCS in any EGSE configuration
(i.e. instrument EGSE, MDVE, test bed, platform EGSE, satellite EGSE, e.t.c.).
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
The FEE shall issue status and error messages to the CCS in the form of C&C messages as defined in above
reference. Keywords and message syntax shall be described in detail in the equipment ICD and users manual.
The detailed definition of command and status messages shall be defined based on the actual design implementation
of the FEE. As a minimum, messages related to the FEE elements served by the controller shall be processed in
accordance to the requirements defined above.
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
All events subject to log file entry shall be able to be visualised on-line (i.e. at time of occurence) in a display
window on the controller local console. Filters shall be able to be applied to allow the operator to only display
selected entry types (i.e. Error, Warning, Message, e.t.c.) or all entries.
Issue: 0
EGSE Specification
Date: 25.02.2006
FEE / SCOE A
Cat.5 RJ45 Patch Cable UTP
CCS
FEE / SCOE C
Multi-Mode FO Cable
TX <-> FX TX <-> FX
Media- Media-
Converter Converter
CCS
FEE / SCOE C
Issue: 0
EGSE Specification
Date: 25.02.2006
The communication between Front End Equipment (FEE) and the CCS shall be performed by means of a Local
Area Network (LAN) as follows (ref. \AD1\, 3.2):
the physical network is referenced / named "EGSE LAN"
Ethernet according to IEEE 802.3
10/100-Base-T RJ45; Category 5 shielded twisted pair (STP) or unshielded twisted pair (UTP)
TCP/IP stream socket peer-to-peer connections
Issue: 0
EGSE Specification
Date: 25.02.2006
5. Implementation Requirements
This section provides general design, implementation, manufacturing and environmental requirements. These
requirements are applicable for the implementation, as well as for selection of commercial equipment. Justification
shall be given in the case of deviation from the guidelines below.
5.1. General
5.2. Lifetime
5.3. Safety
Issue: 0
EGSE Specification
Date: 25.02.2006
No material shall be used which may constitute a risk to the health of personnel.
5.4. Cleanliness
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
Containers shall be designed to protect GSE from the worst case transportation environment as specified above. If
the GSE inside does not comply with the specified environmental conditions, the containers shall provide adequate
protective measures.
11 cm + 1cm
60 cm 1 cm
5.9. Environment
For commercial off-the-shelp equipment individual requirements below may be waived, if justified by the sub-
contractor.
Issue: 0
EGSE Specification
Date: 25.02.2006
5.10. Ergonomy
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
It needs to be decided whether all EGSE components shall provide their own "Mains Isolation Transformer Unit"
(MITU) or if there will be provided one single central "Mains Isolation Transformer" for all items in a configuration.
In case MITU requirements have to be added.
Issue: 0
EGSE Specification
Date: 25.02.2006
all signal interfaces towards the spacecraft shall be driven from earth free power supplies,
the signal ground / return lines shall have no permanent internal connection to drawer/ rack structure but
shall be available at a user defined interface for controlled grounding
LAN I/F card shall be galvanically isolated from drawer/ rack structure
In cases where this requirement cannot be completely fulfilled, all deviations (also partly deviations) shall be
brought to the attention of the customer.
SCOE - A UNIT
PCDU
Mains POWER
L
PE
N
SIGNALS
SCOE - B
SIGNALS
SIGNALS
SIGNAL(HEATER SIM.)
Mains MAINS
L
PE
N
SCOE -C
OBDH/ TT&C
Signals Signals
Coax-line
Coax-line
Mains
MAINS
L
Grounding_Concept.vsd
Issue: 0
EGSE Specification
Date: 25.02.2006
Issue: 0
EGSE Specification
Date: 25.02.2006
All data and signal interface drivers shall survive a short circuit to driver ground, receiver ground or structure
without permanent degradation.
Issue: 0
EGSE Specification
Date: 25.02.2006
Layer 3
Test S/W
Layer 2
Application S/W
Layer 1
System Software / Operating System
Issue: 0
EGSE Specification
Date: 25.02.2006
5.14. Workmanship
5.14.1.1.1 Workmanship / AS
The GSE shall be designed, fabricated and finished to a high quality of fit and finish and for adherence to the
specified requirements. Particular attention shall be given to the absence of burrs and sharp edges which might
cause injury to personnel or damage to flight or ground hardware. Paint finish shall be free of runs, voids, dirt, over-
spray and subsurface voids or contamination. Attention shall be paid to neatness and thoroughness of soldering and
wiring.
Issue: 0
EGSE Specification
Date: 25.02.2006
Item CoG
Safe Working Load
Bonding point identification
Hoisting point identification
Special safety instructions
Re-usable container marking
content identification / nomenclature with S/N
P02 *)
FPA SCOE
*) example
Issue: 0
EGSE Specification
Date: 25.02.2006
6. Verification Requirements
The verification process is that part of the subcontractor's task, which demonstrates conformance to applicable
requirements. A satisfactory completion of the verification process is the basis for a contractual acceptance of the
product by the customer.
Requirements in this specification as well as requirements in the dedicated and applicable equipment requirements
specification indicated by the identification and numbering scheme explained in section 1.2 above shall be subjected
to formal verification close out.
As far as the equipment or S/W is a rebuilt from lower level test equipment (e.g. unit tester), the formal verification
of the corresponding functions may be achieved by demonstration of successful use in lower level integration and
testing.
Issue: 0
EGSE Specification
Date: 25.02.2006
All instruments and measurement equipment used in conducting the tests shall have an accuracy of better than one
third of the tolerance for the variable to be measured unless otherwise specified.
Note: This is to be recorded in as-run-test procedure/test report
6.1.1.1.10 Objectives / nt
The objective of the functional performance test shall not only be the verification of the user requirements but also
the verification of the correct and consistent system behavior.
6.1.1.1.11 Performance / nt
The functional performance test shall include testing of the quantifiable functions and parameters of the product
(performance, accuracy, etc.) in all operational modes specified.