_id stringlengths 30 67 | title stringclasses 196
values | text stringlengths 31 8.3k | metadata dict | image null |
|---|---|---|---|---|
ECSS-E-ST-70C(31July2008)-page=82 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
82
Review ID
Review title
Review objective
Date
Chaired by
IOORs
In–orbit operations
reviews
To carry out a regular assessment of the performance of the
space system, i.e. both space segment and ground segment
During phase E2 on a regular
basis (e.g. yearly)
Operations customer... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 82
} | null |
ECSS-E-ST-70C(31July2008)-page=83 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex A (normative)
Customer requirements document
(CRD) - DRD
A.1
DRD identification
A.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirements 5.2.1b. and 6.2.1b.
A.1.2
Purpose and objective
The objective of the customer requirements ... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 83
} | null |
ECSS-E-ST-70C(31July2008)-page=84 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
4.
the ground segment that is foreseen for the control and operations
of the spacecraft, the instruments and the ground segment itself;
5.
the operations that are foreseen to achieve the goal of the space
project.
<4>
Project responsibilities
a.
The CRD shall describe... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 84
} | null |
ECSS-E-ST-70C(31July2008)-page=85 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
(c)
payload data processing;
(d)
payload data archiving;
(e)
user services;
(f)
data product delivery;
(g)
performance analysis.
6.
on‐board software maintenance;
7.
other mission‐specific operations functions.
c.
For the GSCRD, requirements of the following classes shall be... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 85
} | null |
ECSS-E-ST-70C(31July2008)-page=86 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex B (normative)
Mission analysis report (MAR) - DRD
B.1
DRD identification
B.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.2.2.1c.
B.1.2
Purpose and objective
The objective of the mission analysis report (MAR) is ... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 86
} | null |
ECSS-E-ST-70C(31July2008)-page=87 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<4>
Mission overview
a.
The MAR shall provide a description of the baseline mission, summarises
the basic characteristics of the spacecraft and the launch vehicle and
identifies the different mission phases, their characteristics and duration.
<5>
Launch and early orbit pha... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 87
} | null |
ECSS-E-ST-70C(31July2008)-page=88 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<8>
Routine phase (operation in final orbit)
a.
For Earth‐orbiting missions, the MAR shall describe:
1.
characteristics of the operational orbit including its evolution as a
function of time;
2.
orbit determination concept and navigation analysis (station
selection, data type... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 88
} | null |
ECSS-E-ST-70C(31July2008)-page=89 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex C (normative)
Mission operations concept document
(MOCD) - DRD
C.1
DRD identification
C.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.2.2.2b.
C.1.2
Purpose and objective
The objective of the mission operations concept d... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 89
} | null |
ECSS-E-ST-70C(31July2008)-page=90 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<3.2>
Mission description
a.
The MOCD shall describe the scope of the mission, its objectives and the
top‐level requirements on its operations.
NOTE
This information is derived from the mission
analysis report and the customer requirements
document.
<3.3>
End‐users
a.
Th... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 90
} | null |
ECSS-E-ST-70C(31July2008)-page=91 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
NOTE
The objective is to capture all the salient
operational characteristics that are needed for
the analysis of the operations processes.
<5>
Mission operations concepts
<5.1>
General
a.
The MOCD shall describe the mission operations concepts for each
distin... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 91
} | null |
ECSS-E-ST-70C(31July2008)-page=92 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
5.
resources management (space and ground);
6.
conflict resolution;
7.
space segment operations scheduling;
8.
ground segment operations scheduling.
<5.3>
Operations execution processes
a.
The MOCD shall describe the concept for the implementation of
scheduled operation... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 92
} | null |
ECSS-E-ST-70C(31July2008)-page=93 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<5.6>
Support processes
a.
The MOCD shall describe the concepts for all other activities performed
in support of operations that are not covered by any of the above
categories, including:
1.
orbit and attitude determination and maintenance;
2.
orbital and geometric even... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 93
} | null |
ECSS-E-ST-70C(31July2008)-page=94 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex D (normative)
Operations engineering plan (OEP) - DRD
D.1
DRD identification
D.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.2.2.4a.4.
D.1.2
Purpose and objective
The objective of the operations engineering plan (... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 94
} | null |
ECSS-E-ST-70C(31July2008)-page=95 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<4>
Operations engineering lifecycle and reviews
a.
The OEP shall identify the following:
1.
the major milestones driving the operations engineering processes;
2.
the operations engineering lifecycle phases;
3.
the principal operations reviews and their objectives;
4.
the operati... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 95
} | null |
ECSS-E-ST-70C(31July2008)-page=96 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<6>
Mission operations teams
a.
The OEP shall describe:
1.
the organizational structures of the mission operations teams for
both the operations preparation and operations execution phases;
2.
the allocation of responsibilities to individuals (roles);
3.
the reporting ch... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 96
} | null |
ECSS-E-ST-70C(31July2008)-page=97 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex E (normative)
Space segment user manual (SSUM) - DRD
E.1
DRD identification
E.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.3.1b.
E.1.2
Purpose and objective
The objective of the space segment user manual (SSUM) is to pr... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 97
} | null |
ECSS-E-ST-70C(31July2008)-page=98 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<3.2>
Mission analysis constraints
a.
The SSUM shall describe all space segment constraints to be included in
mission analysis.
<3.3>
Mission phases and purposes
a.
The SSUM shall provide the results of analyses for positioning and for in‐
orbit operations, taking into account satel... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 98
} | null |
ECSS-E-ST-70C(31July2008)-page=99 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
NOTE
For example, mutually exclusive modes of
operation, power or resource sharing.
<4.2>
System‐level autonomy
a.
The system‐level autonomy shall include the following:
1.
description of system‐level autonomy provisions in the areas of
mission management and fault ma... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 99
} | null |
ECSS-E-ST-70C(31July2008)-page=100 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
NOTE
For example, pointing accuracy degradation
during a manoeuvre or degraded performance
during an eclipse.
<4.5>
Satellite‐to‐ground interface specifications
a.
Provide a cross‐reference to the applicable version of the SGICD.
<4.6>
System‐level operations
<4.6.1> Mission ... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 100
} | null |
ECSS-E-ST-70C(31July2008)-page=101 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<4.6.3> System-level failure analysis
a.
The SSUM shall provide the results of the system‐level failure modes and
effects analysis (FMEA) or failure modes effects and criticality analysis
(FMECA) and the resulting list of single‐point failures.
b.
Event combinations potentiall... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 101
} | null |
ECSS-E-ST-70C(31July2008)-page=102 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
b.
For the software design, the SSUM shall describe the organization of the
subsystem software and the physical mapping of software onto
subsystem hardware;
c.
For the subsystem software, the SSUM shall describe the details of each
component of the subsystem software i.e.... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 102
} | null |
ECSS-E-ST-70C(31July2008)-page=103 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<5.6>
Subsystem failure analysis
a.
T For each satellite platform subsystem and for each payload the SSUM
shall describe:
1.
Identification of potential subsystem failures by means of a
systematic failure analysis (based on a subsystem FMEA/FMECA
and FTA).
2.
Identificat... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 103
} | null |
ECSS-E-ST-70C(31July2008)-page=104 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
(d)
telemetry data to be monitored to verify correct execution of
the step;
(e)
interrelationships between steps;
NOTE
For example, conditional branching within the
procedure, timing requirements or constraints,
hold and check points.
(f)
conditions for completion of the step.
e... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 104
} | null |
ECSS-E-ST-70C(31July2008)-page=105 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex F (normative)
Operational validation plan (OVP) - DRD
F.1
DRD identification
F.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.2.2.6c.
F.1.2
Purpose and objective
The operational validation plan (OVP) defines how th... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 105
} | null |
ECSS-E-ST-70C(31July2008)-page=106 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
3.
identification of any constraints or mission‐specific considerations;
4.
identification of the mechanisms and criteria to be used for
measuring and evaluating the success of the operational
validation.
<3.2>
Operational validation management
a.
The OVP shall desc... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 106
} | null |
ECSS-E-ST-70C(31July2008)-page=107 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<5>
Ground segment readiness tests
a.
The OVP shall describe the ground segment readiness test plan, mission
readiness tests (MRTs), data flow tests (DFTs), including:
1.
an overall test plan, and
2.
for each individual test:
(a)
the test timetable (start time, duration),
(b)
th... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 107
} | null |
ECSS-E-ST-70C(31July2008)-page=108 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex G (normative)
Mission operations plan (MOP) - DRD
G.1 DRD identification
G.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.3.2k.
G.1.2
Purpose and objective
The mission operations plan (MOP) contains all the rules, ... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 108
} | null |
ECSS-E-ST-70C(31July2008)-page=109 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<3.2>
Mission rules
a.
The MOP shall contain the rules and criteria governing the conduct of
mission operations, including:
1.
launch hold criteria;
2.
the principles and mechanisms for the routine and foreseen
contingency operations of the mission;
3.
rules an... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 109
} | null |
ECSS-E-ST-70C(31July2008)-page=110 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
2.
a description of the operations implementation strategy for the
mission phase and the consequent structure and content of the
remainder of this clause of the MOP;
3.
timelines of operations, containing:
(a)
a definition of each operational activity;
(b)
the plan... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 110
} | null |
ECSS-E-ST-70C(31July2008)-page=111 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex H (normative)
Operations anomaly report (OAR) - DRD
H.1
DRD identification
H.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.8.2.4e.
H.1.2
Purpose and objective
An operations anomaly report (OAR) is generated to do... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 111
} | null |
ECSS-E-ST-70C(31July2008)-page=112 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
3.
Descriptive title.
4.
Date and time of occurrence or, if this is unknown, the time of
anomaly detection.
5.
Severity of the anomaly in terms of operational impact on the
ground or space segment as one of the following:
(a)
No impact: The anomaly has no... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 112
} | null |
ECSS-E-ST-70C(31July2008)-page=113 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
3.
Details of the prevailing ground segment and space segment
configuration before, during and after the anomaly.
b.
Supporting material may be provided in the form of:
1.
Telemetry reports (display hardcopies, printouts, retrieval reports),
2.
Telecommand history file repor... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 113
} | null |
ECSS-E-ST-70C(31July2008)-page=114 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex I (normative)
Operations procedures - DRD
I.1
DRD identification
I.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.3.2l.
I.1.2
Purpose and objective
An operations procedure is an elementary component of the mission operati... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 114
} | null |
ECSS-E-ST-70C(31July2008)-page=115 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<2>
Preliminary elements
a.
An operations procedure shall include:
1.
Title: A short descriptive title for the procedure.
2.
Version control: The version number and date from which the
operations procedure is applicable.
3.
Author: The names of the author(s) of the operat... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 115
} | null |
ECSS-E-ST-70C(31July2008)-page=116 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<7>
Procedure body
<7.1>
General
a.
The procedure body shall contain the executable elements that achieve
the goal of the procedure.
b.
The procedure body shall be composed of building blocks called “steps”.
NOTE
Steps can either be executed in sequence or in
parallel... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 116
} | null |
ECSS-E-ST-70C(31July2008)-page=117 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
b.
In case that contingency actions are specified, the procedure shall contain
information covering how to:
1.
Restore the system configuration (space segment and ground
segment) such as to allow the procedure main body to continue its
execution (i.e. by first suspending ... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 117
} | null |
ECSS-E-ST-70C(31July2008)-page=118 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex J (normative)
Customer furnished items and services
requirements document (CFISRD) - DRD
J.1
DRD identification
J.1.1
Requirement identification and source document
This DRD is called from ECSS‐E‐ST‐70 requirement 5.2.2.3g.
J.1.2
Purpose and objective
The objective of the... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 118
} | null |
ECSS-E-ST-70C(31July2008)-page=119 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
4.
Pre‐delivery validation requirements;
5.
Delivery schedule for different issues (versions) expressed in terms
of links with the ground segment development and operations
preparation schedules;
b.
Mission information classes shall include:
1.
The space segment users manua... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 119
} | null |
ECSS-E-ST-70C(31July2008)-page=120 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
NOTE
For example, code, documentation, delivery
note,
and
software
problems
reports/lists/database.
5.
Delivery schedule for different versions.
<6>
On‐board software
a.
The CFISRD shall define the responsibilities during the different phases (
i.e. which organisation is r... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 120
} | null |
ECSS-E-ST-70C(31July2008)-page=121 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
<8>
Pre‐launch access to the space segment
a.
The CFISRD shall identify the access required to the space segment to
permit pre‐launch listen‐in tests (LITs, telemetry data reception only) and
space‐to‐ground compatibility tests (SVTs), together with associated
suppo... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 121
} | null |
ECSS-E-ST-70C(31July2008)-page=122 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
3.
Call‐out engineering support for satellite anomaly recovery
operations at the mission control centre, including response time
as a function of mission phase;
4.
Off‐site support for analysis of satellite anomalies, including inputs
to be provided to the OC (in particul... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 122
} | null |
ECSS-E-ST-70C(31July2008)-page=123 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Annex K (informative)
Commonality considerations
K.1
General
Ground segments are frequently built using existing systems including multi‐
mission infrastructure. It is important that the design considers how such
systems are re‐used including customization and extension, i... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 123
} | null |
ECSS-E-ST-70C(31July2008)-page=124 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
•
The main functional elements that can be reused include:
⎯
monitoring;
⎯
commanding;
⎯
monitoring and control database management;
⎯
operations procedures preparation, management and execution;
⎯
data archiving and distribution;
⎯
performance evaluation;
⎯
on–board softwa... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 124
} | null |
ECSS-E-ST-70C(31July2008)-page=125 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
control system, flight dynamics system, implemented by telecommunications,
software and flight dynamics engineers respectively.
Whenever possible, it should be attempted to establish common software
frameworks and a common hardware infrastructure to reduce development
a... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 125
} | null |
ECSS-E-ST-70C(31July2008)-page=126 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
126
Annex L (informative)
ECSS-E-ST-70 level 3 standards
Table L‐1 identifies the level 3 standards in the Ground Systems and Operations
domain and describes the scope of each standard. | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 126
} | null |
ECSS-E-ST-70C(31July2008)-page=127 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
127
Table L‐1 ECSS‐E‐ST‐70 level 3 standards
Number
Title
Scope
ECSS‐E‐ST‐70‐01
On‐board control
procedures
Defines the requirements to be fulfilled by on‐board services for the handling of on‐board control
procedures (OBCPs). Additionally, it identifies requirements on the life c... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 127
} | null |
ECSS-E-ST-70C(31July2008)-page=128 | ECSS-E-ST-70C(31July2008) | ECSS‐E‐ST‐70C
31 July 2008
Bibliography
ECSS‐S‐ST‐00
ECSS system – Description, implementation and
general requirements
ECSS‐E‐ST‐10‐02
Space engineering – Verification
ECSS‐E‐ST‐70‐01
Space engineering – On‐board control procedures
ECSS‐E‐ST‐70‐11
Space engineering – Space segment operability
ECSS‐E‐ST‐70‐... | {
"document_id": "ECSS-E-ST-70C(31July2008)",
"page_number": 128
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=1 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Space product
assurance
Vapour phase bioburden reduction
for flight hardware
ECSS Secretariat
ESA-ESTEC
Requirements & Standards Division
Noordwijk, The Netherlands | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 1
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=2 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Foreword
This Standard is one of the series of ECSS Standards intended to be applied together for the
management, engineering and product assurance in space projects and applications. ECSS is a
cooperative effort of the European Space Agency, national space agencies and European ind... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 2
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=3 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Change log
ECSS-Q-ST-70-56C
30 August 2013
First issue
3 | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 3
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=4 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Table of contents
Change log ................................................................................................................. 3
Introduction ................................................................................................................ 5
1 Scope ..... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 4
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=5 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Introduction
The UN Outer Space Treaty of 1967 sets up the general principles applicable to
the exploration and use of outer space. Article IX of the Outer Space Treaty
constitutes the primary statement of international law:
“States parties shall pursue studies of outer space, inc... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 5
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=6 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
1
Scope
This standard specifies procedures for the reduction of microbiological
contamination of flight hardware using hydrogen peroxide vapour.
The procedures specified in this standard cover:
•
Reduction of microbiological contamination on exposed surfaces.
•
Reduction of mic... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 6
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=7 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
2
Normative references
The following normative documents contain provisions which, through
reference in this text, constitute provisions of this ECSS Standard. For dated
references, subsequent amendments to, or revision of any of these publications
do not apply. However, parties t... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 7
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=8 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
3
Terms and abbreviated terms
3.1
Terms from other standards
For the purpose of this Standard, the terms and definitions from ECSS-S-ST-00-01
apply.
For the purpose of this Standard, the terms and definitions from ECSS-M-ST-40,
ECSS-Q-ST-70-01, ECSS-Q-ST-70-55 and ECSS-Q-ST-70-5... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 8
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=9 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
3.2.5
exposed surfaces
internal and external surfaces free for gas exchange
NOTE
Examples: Free for gas exchange are e.g.,
exterior surfaces, interior surfaces of boxes with
venting holes, surfaces of honeycomb cells,
surfaces of the outer and inner plies of multi-
layer insula... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 9
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=10 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
3.4
Nomenclature
The following nomenclature apply throughout this document:
a.
The word “shall” is used in this standard to express requirements. All the
requirements are expressed with the word “shall”.
b.
The word “should” is used in this standard to express recommendations.
... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 10
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=11 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
4
Principles
It is expected that every project specifies the high level planetary protection
requirements (as needed).
NOTE
For example: for all ESA projects, those
requirements are specified in ESSB-ST-U-001.
The following series of ECSS standards describe the processes and ... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 11
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=12 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Specifying
process
Preparing and
performing process
Quality Requirements
Recording and
reporting process
Work Proposal for the bioburden reduction
including process description (Annex B)
Bioburden reduction results
(including identified deviations, if any)
Bioburden reduction
... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 12
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=13 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
5
Requirements
5.1
General requirements
a.
The bioburden reduction agent shall be hydrogen peroxide vapour.
b.
The customer shall provide a hydrogen peroxide bioburden reduction
specification in conformance with the DRD in Annex A.
c.
The supplier shall provide a hydrogen per... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 13
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=14 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
5.2.3
Product packaging
a.
The packaging, if present at the time of bioburden reduction, shall be
compatible with the bioburden reduction process.
NOTE
Pay attention to pressure changes during the
bioburden reduction process.
b.
The packaging shall be compatible with the clea... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 14
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=15 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
5.3
Process requirements
5.3.1
Procedure requirements
5.3.1.1
Procedure for controlled ambient environment
a.
Procedure for controlled ambient environment shall be used for a 2 to 6
order of magnitude bioburden reduction.
NOTE
A 2 to 6 order of magnitude reduction is
achie... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 15
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=16 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
c.
Ct-value for surface bioburden overkill under controlled ambient
conditions shall be ≥ 14000 (mg/L)sec.
NOTE
The bioburden on the product after applying
the bioburden overkill procedure is considered
zero.
5.3.2
Bioburden reduction cycle requirements
a.
The hydrogen perox... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 16
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=17 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
4.
Humidity, if applicable
5.
Hydrogen peroxide vapour concentration
f.
Instrumentation used to monitor the process parameters shall be
calibrated.
g.
Details of calibration shall be recorded.
h.
Instrumentation used to monitor the process parameters shall be only
used with... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 17
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=18 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Annex A (normative)
Hydrogen peroxide bioburden reduction
specification - DRD
A.1
DRD identification
A.1.1
Requirement identification and source document
This DRD is called from ECSS-Q-ST-70-56, requirement 5.1b.
A.1.2
Purpose and objective
The purpose of the specification is... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 18
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=19 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
7.
Identification of any bioburden recontamination control necessary
for the product before, during and after the bioburden reduction
process is applied, including packaging.
8.
Locations to measure the hydrogen peroxide vapour concentration
on the product.
9.
Expected release ... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 19
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=20 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Annex B (normative)
Hydrogen peroxide bioburden reduction
proposal - DRD
B.1
DRD identification
B.1.1
Requirement identification and source
document
This DRD is called from ECSS-Q-ST-70-56, requirement 5.1c.
B.1.2
Purpose and objective
The purpose of the proposal is to descr... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 20
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=21 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
NOTE
To fulfil this requirement it can be necessary to
perform some tests with a geometrically and
material representative model, equipped with
hydrogen peroxide sensors and BIs, under the
same conditions as planned for the flight
hardware bioburden reduction.
8.
Locations on ... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 21
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=22 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Annex C (normative)
Hydrogen peroxide bioburden reduction
report - DRD
C.1
DRD identification
C.1.1
Requirement identification and source
document
This DRD is called from ECSS-Q-ST-70-56, requirements 5.1e.
C.1.2
Purpose and objective
The purpose of the report is to document... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 22
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=23 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
9.
The purity of the air or other gases used in the process.
10.
Environmental conditions and control of the equipment.
11.
Description of equipment for bioburden reduction.
12.
Calibration records for all the equipment.
13.
BIs certificate of performance.
14.
Particular o... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 23
} | null |
ECSS-Q-ST-70-56C(30August2013)-page=24 | ECSS-Q-ST-70-56C(30August2013) | ECSS-Q-ST-70-56C
30 August 2013
Bibliography
ECSS-S-ST-00
ECSS system - Description, implementation and general
requirements
ESSB-ST-U-001 Issue 1
ESA planetary protection requirements
ISO 11138:2006
Sterilization of health care products - Biological
indicator systems
ISO 20857:2010
Sterilization of health ... | {
"document_id": "ECSS-Q-ST-70-56C(30August2013)",
"page_number": 24
} | null |
ECSS-E-HB-20-01A(15June2020)-page=1 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
Space engineering
Multipactor handbook
ECSS Secretariat
ESA-ESTEC
Requirements & Standards Division
Noordwijk, The Netherlands | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 1
} | null |
ECSS-E-HB-20-01A(15June2020)-page=2 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
2
Foreword
This Handbook is one document of the series of ECSS Documents intended to be used as supporting
material for ECSS Standards in space projects and applications. ECSS is a cooperative effort of the
European Space Agency, national space agencies and European industry associa... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 2
} | null |
ECSS-E-HB-20-01A(15June2020)-page=3 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
3
Table of contents
Change log ...................................................................................................... 10
Introduction ..................................................................................................... 11
Scope ....................... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 3
} | null |
ECSS-E-HB-20-01A(15June2020)-page=4 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
4
5.3.2
Design analysis levels ...................................................................... 24
5.3.3
Available data for Multipactor analysis ............................................. 58
5.4
Bibliography for clause 5....................................................... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 4
} | null |
ECSS-E-HB-20-01A(15June2020)-page=5 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
5
8.4.1
Power profile .................................................................................... 93
8.5
Acceptance criteria ........................................................................................ 93
8.5.1
Definitions ........................................ | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 5
} | null |
ECSS-E-HB-20-01A(15June2020)-page=6 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
6
Figure 4-7: Power correction with respect to mismatch of the payload downstream
component assembly ................................................................................ 21
Figure 5-1: 2D schematic of a typical iris-like structure ............................................ | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 6
} | null |
ECSS-E-HB-20-01A(15June2020)-page=7 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
7
Figure 5-30: Predicted Voltage Distribution in Finalised L-band RF Device
(1525 MHz) ............................................................................................... 54
Figure 5-31: Predicted S-parameter Performance of Finalised L-band RF Device
(1405 MHz) ............ | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 7
} | null |
ECSS-E-HB-20-01A(15June2020)-page=8 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
8
Figure 6-20: Sketch of the functioning of an electron gun. ........................................... 79
Figure 6-21: Picture of an electron gun installed into a test bed. .................................. 80
Figure 7-1: Schematic of global detection systems implemented in a typi... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 8
} | null |
ECSS-E-HB-20-01A(15June2020)-page=9 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
9
Tables
Table 4-1:Multipactor simulations and multipactor measurements with and without
thermal baking for a RF component with different dielectric materials ....... 18
Table 5-1: Characteristics Ku-band transformer of ESA TRP activity [5-19] ................. 40
Table 5-2: Char... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 9
} | null |
ECSS-E-HB-20-01A(15June2020)-page=10 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
10
Change log
ECSS-E-HB-20-01A
15 June 2020
First issue | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 10
} | null |
ECSS-E-HB-20-01A(15June2020)-page=11 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
11
Introduction
Multipactor is a well-understood RF breakdown mechanism in high vacuum conditions. It has been
investigated both theoretically and experimentally over many years, as listed in references from [2-1] to
[2-7]. Essential ingredient for multipactor is initial free electr... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 11
} | null |
ECSS-E-HB-20-01A(15June2020)-page=12 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
12
Scope
This Handbook describes the guidelines and recommendations for the design and test of RF
components and equipment to achieve acceptable performance with respect to multipactor-free
operation in service in space. This document is the mirror document of the ECSS-ST-20-01 no... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 12
} | null |
ECSS-E-HB-20-01A(15June2020)-page=13 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
13
References
ECSS-S-ST-00-01
ECSS system – Glossary of terms
ECSS-E-ST-10-02
Space engineering – Verification
ECSS-E-ST-10-03
Space engineering - Testing
ECSS-E-ST-20-01
Space engineering – Multipactor design and test
ECSS-M-ST-10
Space project management – Project plannin... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 13
} | null |
ECSS-E-HB-20-01A(15June2020)-page=14 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
14
Terms, definitions and abbreviated terms
3.1
Terms from other documents
a.
For the purpose of this standard, the terms and definitions from ECSS-S-ST-00-01 apply, in
particular the following terms:
1.
acceptance
2.
bakeout
3.
component
4.
development
5.
equipment
6... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 14
} | null |
ECSS-E-HB-20-01A(15June2020)-page=15 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
15
3.2
Abbreviated terms
For the purpose of this document, the abbreviated terms from ECSS-S-ST-00-01 and the following apply:
Abbreviation
Meaning
DUT
device under test
EDC
energy distribution curve
EM
electromagnetic
ESD
electron stimulated discharge
FEM
finite elemen... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 15
} | null |
ECSS-E-HB-20-01A(15June2020)-page=16 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
16
Verification
4.1
Verification process
No supporting material needed.
4.2
Multipactor verification plan
No supporting material needed.
4.2.1
Generation and updating
No supporting material needed.
4.2.2
Description
No supporting material needed.
4.3
Power requirements ... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 16
} | null |
ECSS-E-HB-20-01A(15June2020)-page=17 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
17
Since ∆P is frequency dependent, the worst case ∆P over the operational frequency bandwidth is taken
into account.
4.3.1.3
Failure
Failure case for circulators
Circulators are used for protecting high power amplifiers in case of a failure or for improving the RF
performance of... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 17
} | null |
ECSS-E-HB-20-01A(15June2020)-page=18 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
18
(handling, triboelectrification, temperature baking…). Thus, baking can have different effects on the
charging behaviour and therefore on the multipactor effect. The initial charge of the dielectric, as well
as the induced charge during the multipactor avalanche, are highly unpred... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 18
} | null |
ECSS-E-HB-20-01A(15June2020)-page=19 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
19
The worst predicted values of Table 4-1correspond to the Multipactor analysis considering the less
conservative SEY figures for each sample.
The best predicted values of Table 4-1 correspond to the Multipactor analysis considering the more
conservative SEY figures for each sample... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 19
} | null |
ECSS-E-HB-20-01A(15June2020)-page=20 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
20
Figure 4-5: Schematic diagram of discharge at a triple point in the inverted voltage
gradient configuration with potential contours indicated by colour scale.
This phenomenon can be avoided when using rounded metal edge inside the RF component in the
“triple point” area.
4.5
... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 20
} | null |
ECSS-E-HB-20-01A(15June2020)-page=21 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
21
where Γi-1 is the reflection coefficient of the downstream component assembly (also called “component
i-1” in the Figure 4-6 below).
Figure 4-6: Component assembly with consideration of the reflection coefficient of
the downstream component assembly for test margin
The correc... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 21
} | null |
ECSS-E-HB-20-01A(15June2020)-page=22 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
22
4.7
Multicarrier
4.7.1
General
No supporting material needed.
4.7.2
Verification by analysis
No supporting material needed.
4.7.3
Verification by test
4.7.3.1
Test margins
Margins for multipactor test with multicarrier signal with free running phase (see 4.7.3.1 b of ECS... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 22
} | null |
ECSS-E-HB-20-01A(15June2020)-page=23 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
23
4.8
Bibliography for clause 4
[4-1] G. Torregrosa, A. Coves, C. P. Vicente, A. M. Perez, B. Gimeno and V. E. Boria, "Time evolution
of an electron discharge in a parallel-plate dielectric-loaded waveguide," in IEEE Electron
Device Letters, vol. 27, no. 7, pp. 619-621, July 2006.... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 23
} | null |
ECSS-E-HB-20-01A(15June2020)-page=24 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
24
Design analysis
5.1
Overview
No supporting material needed.
5.2
Field analysis
A multipactor analysis cannot be performed without a good knowledge of the electric fields within the
component. Therefore, the first step is to calculate the electrical field within the RF compo... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 24
} | null |
ECSS-E-HB-20-01A(15June2020)-page=25 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
25
5.3.2.2
Analysis level 1 (L1)
5.3.2.2.1
General requirements for analysist level 1 (L1)
No supporting material needed.
5.3.2.2.2
Criteria for geometry and material
A.
Fringing Field Effect
The basic physics involved in the multipactor phenomenon is well known for the case o... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 25
} | null |
ECSS-E-HB-20-01A(15June2020)-page=26 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
26
In fact, experimental and numerical results have shown an increase in the breakdown power in irises
with respect to the parallel-plate approach. Such works show that the ratio between height and length
of the iris (d/l) determines the increase of the breakdown voltage.
Not only i... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 26
} | null |
ECSS-E-HB-20-01A(15June2020)-page=27 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
27
A.1.3.
Application to Sombrin and/or Hatch and Williams charts
Classical Sombrin or Hatch and Williams charts can be computed with the effective SEY derived from
the models above, which renders different thresholds for different ratios. A typical chart is shown in
Figure 5-2. ... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 27
} | null |
ECSS-E-HB-20-01A(15June2020)-page=28 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
28
Figure 5-3: 2D Typical multipactor chart computed with non-stationary theory
with fringing field effect for different d/l ratios.
A.2.
Numerical computation
3D numerical RF electromagnetic software, with added capability to simulate particle trajectories
through electromagn... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 28
} | null |
ECSS-E-HB-20-01A(15June2020)-page=29 | ECSS-E-HB-20-01A(15June2020) | ECSS-E-HB-20-01A
15 June 2020
29
Figure 5-4: 2D Experimental results corresponding to EVEREST project [5-12]
Experimental results of the ESA-TESAT activity [5-10], show the voltage increase factor (breakdown
voltage compared to parallel-plates one) of the activity compared to the NASA report. It can be seen
th... | {
"document_id": "ECSS-E-HB-20-01A(15June2020)",
"page_number": 29
} | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.