SIST EN 16601-00-01:2015

SLOVENSKI STANDARD
01-april-2015
1DGRPHãþD
SIST EN 13701:2002
Vesoljski sistemi - Slovar
Space systems - Glossary of terms
Raumfahrttechnik - Glossar
Système spatiale - Glossaire
Ta slovenski standard je istoveten z: EN 16601-00-01:2015
ICS:
01.040.49 Letalska in vesoljska tehnika Aircraft and space vehicle
(Slovarji) engineering (Vocabularies)
49.140 Vesoljski sistemi in operacije Space systems and
operations
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 16601-00-01
NORME EUROPÉENNE
EUROPÄISCHE NORM
January 2015
ICS 49.140; 01.040.49 Supersedes EN 13701:2001
English version
Space systems - Glossary of terms
Syst?e spatiale - Glossaire Raumfahrttechnik - Glossar
This European Standard was approved by CEN on 1 March 2014.

CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving
this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning
such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre
has the same status as the official versions.

CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece,
Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia,
Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.

CEN-CENELEC Management Centre:
Avenue Marnix 17, B-1000 Brussels
© 2015 CEN/CENELEC All rights of exploitation in any form and by any means reserved Ref. No. EN 16601-00-01:2015 E
worldwide for CEN national Members and for CENELEC
Members.
Table of contents
Foreword . 3
1 Scope . 4
2 Terms, definitions and abbreviated terms . 5
2.1 Terms and definitions . 5
2.2 Space system breakdown . 6
2.2.1 Introduction . 6
2.2.2 Definitions for generic terms . 8
2.2.3 Definitions for space system . 9
2.2.4 Definitions for space segment . 9
2.2.5 Definitions for ground segment . 10
2.2.6 Definitions for launch segment . 10
2.2.7 Definitions for support segment . 11
2.3 Terms and definitions . 12
2.4 Abbreviated terms. 42
Annex A Traceability with respect to ECSS-P-001B . 46
Annex B Segment trees . 54
B.1 Space segment . 55
B.2 Ground segment . 56
B.3 Launch segment . 57
B.4 Support segment . 58
Annex C Launch segment-specific terms . 59
Bibliography . 62

Figures
Figure 2-1: Space system breakdown . 7

Foreword
This document (EN 16601-00-01:2015) has been prepared by Technical
Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN.
This standard (EN 16601-00-01:2015) originates from ECSS-S-ST-00-01C.
This European Standard shall be given the status of a national standard, either
by publication of an identical text or by endorsement, at the latest by July 2015,
and conflicting national standards shall be withdrawn at the latest by July 2015.
Attention is drawn to the possibility that some of the elements of this document
may be the subject of patent rights. CEN [and/or CENELEC] shall not be held
responsible for identifying any or all such patent rights.
This document has been prepared under a mandate given to CEN by the
European Commission and the European Free Trade Association.
This document supersedes EN 13701-2001.
This document has been developed to cover specifically space systems and has
therefore precedence over any EN covering the same scope but with a wider
domain of applicability (e.g. : aerospace).
According to the CEN-CENELEC Internal Regulations, the national standards
organizations of the following countries are bound to implement this European
Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United
Kingdom.
Scope
This document controls the definition of all common terms used in the
European Cooperation for Space Standardization (ECSS) Standards System.
Terms specific to a particular ECSS Standard are defined in that standard.
This document does not include the definition of terms used with their common
meaning. In this case, the definition from the Oxford English Dictionary
applies.
Terms, definitions and abbreviated terms
2.1 Terms and definitions
When using the ECSS standards, the following is the order of precedence of
documents as the source of definition of terms:
1. the standard in question
2. the present Glossary of terms
3. the Oxford English dictionary.
A term used within a definition, which is defined elsewhere in this document is
shown in boldface. A boldface term may be replaced within the definition by its
own definition.
A concept that has a special meaning in a particular context is indicated by
designating the context in angle brackets, < >, before the definition.
A document reference shown after a definition in square brackets, [ ], indicates
that this definition is reproduced from the referenced document.
NOTE For example:
2.3.17 auditee
organization being audited
[ISO 9000:2005]
All terms and their definitions appear in alphabetic order in clause 2.3 of this
Glossary. However, wherever it is considered important to present together a
set of terms that are interrelated (i.e. constitute a particular “view”), these terms
and their definitions are repeated in standalone sections of this Glossary or in
Annexes. For example, clause 2.2 collects together all terms that relate to the
breakdown of the overall Space System.
2.2 Space system breakdown
2.2.1 Introduction
ECSS-S-ST-00C defines the highest-level system within a space project – i.e. the
one at the mission-level - as the “Space System”. The purpose of the present
clause is to identify the breakdown of a typical space system and to define a set of
standard terms for the constituent levels within the breakdown (see Figure 2-1).
In so doing, it is acknowledged that each distinct domain (i.e. space, ground
and launcher) already has its own domain-specific terminology for its internal
entities e.g. elements and systems. In the case of the launcher domain, this
terminology has been formally defined and agreed at programme-level. It is not
the intention to define new terms in this Glossary to supersede those already in
universal use. Rather, the intention is to define a standard set of terms for the
levels of the space system breakdown and then to show where the domain-
specific entities fit into these levels. To this end, Annex B contains examples of
entities from the three principal space system segments, mapped to the space
system breakdown levels defined below.
The terms are defined in clause 2.2.2 to 2.2.7 and are listed not in alphabetic
order but according to the hierarchy defined in Figure 2-1: Space system
breakdown below.
• 2.2.2 defines generic terms
• 2.2.3 defines the space system
• 2.2.4 defines terms relating to the space segment
• 2.2.5 defines terms relating to the ground segment
• 2.2.6 defines terms relating to the launch segment
• 2.2.7 defines terms relating to the support segment

Figure 2-1: Space system breakdown
2.2.2 Definitions for generic terms
system
set of interrelated or interacting functions constituted to achieve a specified
objective
segment
set of elements or combination of systems that fulfils a major, self-contained,
subset of the space mission objectives
Examples are space segment, ground segment, launch segment and support
segment.
element
combination of integrated equipment, components and parts
NOTE An element fulfils a major, self-contained, subset of
a segment's objectives.
subsystem
part of a system fulfilling one or more of its functions
equipment
integrated set of parts and components
NOTE 1 An equipment accomplishes a specific function.
NOTE 2 An equipment is self-contained and classified as
such for the purposes of separate manufacture,
procurement, drawings, specification, storage,
issue, maintenance or use.
NOTE 3 The term "unit" is synonymous with the term
"equipment"
component
set of materials, assembled according to defined and controlled processes,
which cannot be disassembled without destroying its capability and which
performs a simple function that can be evaluated against expected
performance requirements
NOTE 1 The term "part" is synonymous.
NOTE 2 The term "part" is preferred when referring to
purely mechanical devices.
NOTE 3 The term "component" is preferred for EEE
devices.
part
see "component"
material
raw, semi–finished or finished substance (gaseous, liquid, solid) of given
characteristics from which processing into a component or part is undertaken
2.2.3 Definitions for space system
space system
system that contains at least a space, a ground or a launch segment
NOTE Generally a space system is composed of all three
segments and is supported by a support segment.
2.2.4 Definitions for space segment
space segment
part of a space system, placed in space, to fulfil the space mission objectives
space segment system
system within a space segment
NOTE Examples are given in Annex B.1.
space segment element
element within a space segment
NOTE 1 A space segment element can be composed of
several space segment elements, e.g. a spacecraft is
composed of instruments, a payload module and a
service module.
NOTE 2 Examples are given in Annex B.1.
stand-alone space segment element
space segment element that performs its mission autonomously
NOTE For example: satellite, rover, lander.
embedded space segment element
space segment element that performs its mission as part of another space
segment element
NOTE For example: platform, module, instrument,
payload.
space segment subsystem
subsystem within a space segment
NOTE Examples are given in Annex B.1.
space segment equipment
equipment within a space segment
NOTE Examples are given in Annex B.1.
2.2.5 Definitions for ground segment
ground segment
part of a space system, located on ground, which monitors and controls space
segment element(s)
NOTE A ground segment is composed of one or more
ground segment elements.
ground segment system
system within a ground segment
NOTE Examples are given in Annex B.2.
ground segment element
element within a ground segment
NOTE 1 A ground segment element can be composed of
several ground segment elements, e.g. a ground
station network is a ground segment element that
can be composed of a set of ground stations and a
communication network.
NOTE 2 Examples are given in Annex B.2.
ground segment subsystem
subsystem within a ground segment
NOTE Examples are given in Annex B.2.
ground segment equipment
equipment within a ground segment
NOTE Examples are given in Annex B.2.
2.2.6 Definitions for launch segment
launch segment
part of a space system which is used to transport space segment element(s)
into space
NOTE 1 A launch segment is composed of one or more
launch segment elements.
NOTE 2 A launch segment is composed of the integrated
launcher and the facilities needed for
manufacturing, testing and delivering launcher
elements.
launch segment system
system within a launch segment
NOTE Examples are given in Annex B.3
launch segment element
element within a launch segment
NOTE 1 A launch segment element can be composed of
several launch segment elements, e.g. a launcher is
a launch segment element that is composed of
several launch segment elements, such as stage,
engine and upper part.
NOTE 2 Examples are given in Annex B.3.
launch segment subsystem
subsystem within a launch segment
NOTE Examples are given in Annex B.3.
launch segment equipment
equipment within a launch segment
NOTE Examples are given in Annex B.3.
2.2.7 Definitions for support segment
support segment
generic infrastructure and services used to support the development and
operation of space system elements
NOTE 1 Examples are ground stations and associated
networks, orbit computing facilities, test centres,
astronaut centre, launch facilities (e.g. Plestek,
Baikonour, Guiana Space Centre).
NOTE 2 Items can be part of other segments during their
development and later become part of the support
segment when used (e.g. a tracking network).
2.3 Terms and definitions
2.3.1 acceptance
act by which the customer agrees that the product is designed and
produced according to its specifications and the agreed deviations and
waivers, and it is free of defects when delivered by the supplier
2.3.2 acceptance
that part of the verification process which demonstrates that the
product meets specified acceptance margins
2.3.3 accident
undesired event arising from operation of any project-specific item that results in
a. human death or injury,
b. loss of, or damage to, project hardware, software or facilities that can
then affect the accomplishment of the mission,
c. loss of, or damage to, public or private property, or
d. detrimental effects on the environment.
NOTE Accident and mishap are synonymous.
2.3.4 active redundancy
redundancy where all entities are operating and the system can continue to
operate without downtime or defects despite the loss of one or more entities
2.3.5 actuator
device that transforms an input signal into motion
2.3.6 alert
formal notification to users, informing them of failures or nonconformance of
items, already released for use or not, which could also be present on other
items already delivered [e.g. items with identical design concept, materials,
components or processes]
NOTE An alert can also be raised when a deficiency in the
specified requirements, which can affect the fitness
for purpose in the defined application, has been
identified.
2.3.7 allowable load
maximum load that can be permitted in a structural part for a given operating
environment to prevent rupture, collapse, detrimental deformation or
unacceptable crack growth
NOTE Adapted from ISO 14623:2003.
2.3.8 analysis
verification method utilizing techniques and tools to confirm that
verification requirements have been satisfied
NOTE 1 Examples of techniques and tools are mathematical
models, compilation similarity assessments and
validation of records.
NOTE 2 Adapted from ISO 10795:2011.
2.3.9 anomaly
any deviation from the expected situation
NOTE An anomaly justifies an investigation that might
lead to the discovery of a nonconformance or a
defect.
2.3.10 applicable document
document that contains provisions which, through reference in the source
document, constitute additional provisions of the source document
NOTE Adapted from ISO 10795:2011.
2.3.11 approval
formal agreement by a designated management official to use or apply an item
or proceed with a proposed course of action
NOTE 1 Approvals must be documented.
NOTE 2 Approval implies that the approving authority has
verified that the item conforms to its requirements.
2.3.12 assembly
physically combining parts, components, equipment or segment
elements to form a larger entity
2.3.13 assurance
planned and systematic activities implemented, and demonstrated as needed,
to provide adequate confidence that an entity fulfils its requirements
2.3.14 audit
systematic, independent and documented process for obtaining audit evidence
and evaluating it objectively to determine the extent to which audit criteria are
fulfilled
NOTE 1 Internal audits, sometimes called first-party audits,
are conducted by, or on behalf of, the organization
itself for management review and other internal
purposes, and may form the basis for an
organization’s declaration of conformity. In many
cases, particularly in smaller organizations,
independence can be demonstrated by the freedom
from responsibility for the activity being audited.
NOTE 2 External audits include those generally termed
second- and third-party audits. Second-party
audits are conducted by parties having an interest
in the organization, such as customers, or by other
persons on their behalf. Third-party audits are
conducted by external, independent auditing
organizations, such as those providing
certification/registration of conformity to ISO 9001
or ISO 14001.
NOTE 3 When quality and environmental management
systems are audited together, this is termed
“combined audit”.
NOTE 4 When two or more auditing organizations
cooperate to audit a single auditee jointly, this is
termed “joint audit”.
[ISO 9000:2005]
2.3.15 audit criteria
set of policies, procedures or requirements
NOTE Audit criteria are used as a reference against which
audit evidence is compared.
[ISO 9000:2005]
2.3.16 audit evidence
records, statements of fact or other information which are relevant to the audit
criteria and verifiable
NOTE Audit evidence can be qualitative or quantitative.
[ISO 9000:2005]
2.3.17 auditee
organization being audited
[ISO 9000:2005]
2.3.18 auditor
person with the demonstrated personal attributes and competence to conduct
an audit
NOTE Adapted from ISO 9000:2005.
2.3.19 availability
ability of an item to be in a state to perform a required function under given
conditions at a given instant of time or over a given time interval, assuming that
the required external resources are provided
NOTE 1 This ability depends on the combined aspects of
the reliability performance, the maintainability
performance and the maintenance support
performance.
NOTE 2 Required external resources, other than
maintenance resources do not affect the
availability performance of the item.
NOTE 3 When referring to the measure for availability, the
preferred term is “instantaneous availability”.
NOTE 4 Adapted from IEC Multilingual Dictionary: 2001
edition.
2.3.20 backward contamination
contamination of the terrestrial biosphere by extra-terrestrial life forms in the
course of spaceflight missions
2.3.21 bakeout
activity of increasing the temperature of hardware to accelerate its outgassing
rates with the intent of reducing the content of molecular contaminants within
the hardware
NOTE Bakeout is usually performed in a vacuum
environment, but may be done in a controlled
atmosphere.
2.3.22 baseline
set of information which describes exhaustively a situation at a given instant of
time or over a given time interval
NOTE A baseline is generally used as a reference for
comparison with and analysis of subsequent
evolutions of the information.
2.3.23 batch
quantity produced at one operation
2.3.24 black box
representation of an item whereby knowledge of its internal composition is not
available to the user, only its function and interface characteristics are known
2.3.25 business agreement
legally binding agreement, for the supply of goods or services, between two or
more actors in the customer–supplier chain
NOTE Business agreements are recorded in a variety of
forms, such as:
• Contracts,
• Memoranda of understanding,
• Inter-governmental agreements,
• Inter-agency agreements,
• Partnerships,
• Bartering agreements, and
• Purchase orders.
2.3.26 calibration
all the operations for the purpose of determining the values of the errors and, if
necessary, other metrological properties of a measuring instrument
NOTE The metrological use of the term “calibration” is
often extended to include operations such as
adjustments, scale graduation, etc. This use is
deprecated.
[IEC Multilingual Dictionary: 2001 edition]
2.3.27 capability
ability of an organization, system or process to realize a product that will fulfil
the requirements for that product
NOTE Process capability terms in the field of statistics are
defined in ISO 3534-2.
[ISO 9000:2005]
2.3.28 catastrophic
resulting in loss of life, life-threatening, permanently disabling injury
or occupational illness, loss of system, loss of an interfacing manned flight
system, loss of launch site facilities or severe detrimental environmental effects
2.3.29 certification
procedure by which a party gives formal assurance that a person or an
organization acts, or a product is, in compliance with specified requirements
NOTE Certification can be carried out by a first, second or
third party.
2.3.30 clean area
area under contamination control
NOTE Examples of clean areas are cleanrooms,
integration tent, gloves box.
2.3.31 cleanliness
level of particulate or molecular contamination
2.3.32 cleanroom
clean area controlled according to specified levels
NOTE Specified levels are humidity, temperature,
particulates number versus size and volume and
chemical contamination.
2.3.33 cold redundancy
redundancy where one entity is operating and the others are powered off
2.3.34 commissioning
verification and validation activities conducted after the launch and before the
entry into operational service either on the space segment elements only or on
the overall system (including the ground segment elements)
2.3.35 common cause failure
failure of multiple items occurring from a single cause that is common to all of
them
2.3.36 common mode failure
failure of multiple identical items that fail in the same mode
NOTE Common mode failures are a particular case of
common cause failures.
2.3.37 component
set of materials, assembled according to defined and controlled processes,
which cannot be disassembled without destroying its capability and which
performs a simple function that can be evaluated against expected
performance requirements
NOTE 1 The term "part" is synonymous.
NOTE 2 The term "part" is preferred when referring to
purely mechanical devices.
NOTE 3 The term "component" is preferred for EEE
devices.
2.3.38 composite
building block of a launcher composed of one or several pre-integrated stages
and structural parts (fairing, payload adaptor, dual launch structure, etc.)
NOTE 1 Example-1: A5 Upper Composite includes the
cryogenic upper stage (ESC), the vehicle
equipment bay (VEB), fairing and payload
adaptor.
NOTE 2 Example-2: A5 Lower Composite includes two
solid booster stages (EAP) and the main cryogenic
stage (EPC).
2.3.39 configuration
interrelated functional and/or physical characteristics of a product defined in
configuration documents subject to configuration management
NOTE Adapted from ISO 10007:2003.
2.3.40 configuration baseline
approved status of requirements and design of a product at a project key
milestone that serves as a reference for activities throughout the life cycle of the
product
NOTE Adapted from ISO 10007:2003.
2.3.41 configuration control
coordinated activities for controlling modifications to a configuration baseline
NOTE Requests for deviation are also considered
modifications to a baseline.
2.3.42 configuration document
document that defines the requirements for function, design, build,
production, and verification for a configuration item
NOTE For space standards, configuration documents can
include documents relating to operation and
disposal of the configuration item.
2.3.43 configuration identification
coordinated activities to establish rules for configuration item selection,
configuration baseline content definition, and product and document
identifiers definition
2.3.44 configuration item
aggregation of hardware, software, processed materials, services or any of its
discrete portions, that is designated for configuration management and treated
as a single entity in the configuration management process
NOTE A configuration item can contain other
configuration item(s).
2.3.45 configuration management
activity for establishing and maintaining consistent records of the performance
parameters of a product and its functional and physical attributes compared to
product design and operational requirements
NOTE 1 Configuration management is applied throughout
the entire life cycle of the product (i.e.
development, production, deployment, operation
and disposal).
NOTE 2 Adapted from ISO 10007:2003.
2.3.46 configuration status accounting
formalized recording and reporting of product characteristics and
configuration information, the status of applicable changes and the status of
their implementation
NOTE Adapted from ISO 10007:2003.
2.3.47 configuration verification
coordinated activities to determine the conformance of the configuration item
to its configuration document(s)
2.3.48 conformance
fulfilment of a requirement
NOTE The term “conformity” is synonymous.
2.3.49 conformity
see “conformance”
NOTE The term “conformance” is strongly recommended
for use in the ECSS system.
2.3.50 contaminant
undesirable molecular or particulate matter
NOTE This includes microbiological matter.
2.3.51 contamination
introduction of contaminant to an item or to the environment of interest
2.3.52 contract
legally enforceable business agreement in which payment is part of the
conditions
2.3.53 corrective action
action to eliminate the cause of a detected nonconformance, or other
undesirable situation
NOTE 1 There can be more than one cause for a non-
conformance.
NOTE 2 Corrective action is taken to prevent recurrence
whereas preventive action is taken to prevent
occurrence.
2.3.54 COTS
commercial electronic component readily available and not manufactured,
inspected or tested in accordance with military or space standards
2.3.55 critical
characteristic of a process, process condition, parameter,
requirement or item that deserves control and special attention in order to meet
the objectives (e.g. of a mission) within given constraints
2.3.56 critical
resulting in temporarily disabling but not life threatening injury,
temporary occupational illness, major detrimental environmental effects, major
damage to public or private properties, major damage to interfacing flight
systems or major damage to ground facilities
2.3.57 critical item
potential threat to the schedule, cost, performance and quality of a project or
programme that is controlled by a specific action plan in order to mitigate
emanating risks and to prevent undesirable consequences
NOTE Examples of critical items are:
• item not qualified or validated for the
application in question (or has caused problems
previously which remained unresolved).
• item for which it is difficult to demonstrate
design performance.
• item highly sensitive to the conditions under
which it is produced or used (e.g.
contamination, radiation).
• item having the potential to degrade the quality
of the product significantly, and hence the
ability of the end-product to accomplish
defined mission objectives.
• item for which major difficulties or
uncertainties are expected in the procurement,
manufacturing, assembly, inspection, test,
handling, storage and transportation, that have
the potential to lead to a major degradation in
the quality of the product.
2.3.58 critical path
chain of activities that determines the earliest completion of the project
NOTE As a consequence, any delay of one task belonging
to the critical path extends the project duration.
2.3.59 customer
organization or person that receives a product as part of a business agreement
NOTE A customer can be internal or external to the
supplier organization.
2.3.60 defect
non-fulfilment of a requirement related to an intended or specified use
NOTE 1 The distinction between the concepts defect and
nonconformance is important as it has legal
connotations, particularly those associated with
product liability issues. Consequently the term
“defect” should be used with extreme caution.
NOTE 2 The intended use as intended by the customer can
be affected by the nature of the information, such
as operating or maintenance instructions, provided
by the supplier.
2.3.61 dependability
the extent to which the fulfilment of a required function can be justifiably
trusted
NOTE 1 Its main components are reliability, availability
and maintainability.
NOTE 2 Dependability shall be considered in conjunction
with safety.
2.3.62 derating
action when designing a product to limit the component stresses to specified
levels that are below their ratings in order to increase its reliability
2.3.63 design
set of information that defines the characteristics of a product
2.3.64 design
process used to generate the set of information defining the
characteristics of a product
NOTE The design is completed at CDR closure.
2.3.65 development
complete process of elaborating a product from concept to manufacturing
including its qualification and final acceptance
NOTE Technology development and design production
are part of the process (i.e. from phase 0 to phase D).
2.3.66 deviation
formal authorization to depart from the originally specified requirements for a
product, prior to its production
NOTE Waiver is an a posteriori decision whereas
deviation is an a priori decision with respect to the
production phase.
2.3.67 discipline
specific area of expertise within a general subject
NOTE The name of the discipline normally indicates the
type of expertise (e.g. in the ECSS system, system
engineering, mechanical engineering, software and
communications are disciplines within the
engineering domain).
2.3.68 discrepancy
departure from expected performance
NOTE 1 A discrepancy can be the result of nonconforming
hardware or software, or conditions occurring in
test set-up.
NOTE 2 A discrepancy can be momentary, non-repeatable,
or permanent.
NOTE 3 Adapted from ISO 10795:2011.
2.3.69 disposal
actions performed by a spacecraft or launch vehicle orbital stage to
permanently reduce its chance of accidental break-up and to achieve its
required long-term clearance of the protected regions
[ISO 24113:2011]
2.3.70 effectiveness
extent to which planned activities are realized and planned results achieved
[ISO 9000:2005]
2.3.71 efficiency
relationship between the result achieved and the resources used
[ISO 9000:2005]
2.3.72 element
combination of integrated equipment, components and parts
NOTE An element fulfils a major, self-contained, subset of
a segment's objectives.
2.3.73 emergency
situation where hazardous events have occurred with potentially catastrophic
or critical consequences requiring an immediate action
2.3.74 embedded space segment element
space segment element that performs its mission as part of another space
segment element
NOTE For example: platform, module, instrument,
payload.
2.3.75 end item
product that is deliverable under a business agreement
2.3.76 engineering model
flight representative model in terms of form, fit and function used for
functional and failure effect verification
NOTE 1 The engineering model is usually not equipped with
high reliability parts or full redundancy.
NOTE 2 The engineering model is also used for final
validation of test facilities, GSE and associated
procedures.
NOTE 3 More detailed information on the build standard and
the use of this model is given in ECSS-E-HB-10-02.
2.3.77 engineering qualification model
model, which fully reflects the design of the flight model except for the parts
standard, used for functional performance and EMC verification and possibly
for qualification
NOTE 1 Military grade or lower-level parts can be used
instead of high reliability parts, provided they are
procured from the same manufacturer with the same
packaging.
NOTE 2 Functional performance qualification includes
verification of procedures for failure detection,
isolation and recovery and for redundancy
management.
NOTE 3 The engineering qualification model may also be
used for environmental testing if the customer
accepts the risk, in which case the qualification model
rules apply.
NOTE 4 More detailed information on the build standard and
the use of this model is given in ECSS-E-HB-10-02.
2.3.78 environment
natural conditions and induced conditions that constrain the design definitions
or operations of a product
NOTE 1 Examples of natural conditions are weather,
climate, ocean conditions, terrain, vegetation, dust,
light and radiation.
NOTE 2 Examples of induced conditions are
electromagnetic interference, heat, vibration,
pollution and contamination.
2.3.79 equipment
integrated set of parts and components
NOTE 1 An equipment accomplishes a specific function.
NOTE 2 An equipment is self-contained and classified as
such for the purposes of separate manufacture,
procurement, drawings, specification, storage,
issue, maintenance or use.
NOTE 3 The term "unit" is synonymous with the term
"equipment".
2.3.80 fail-safe
preventing the failure of an item from resulting in catastrophic or critical
consequences
2.3.81 failure
the event resulting in an item being no longer able to perform its required
function
NOTE "Failure" is an event, as distinguished from "fault"
which is a state.
2.3.82 failure mode
mechanism through which a failure occurs
NOTE 1 For example,. short-circuit, open-circuit, fracture,
or excessive wear.
NOTE 2 This term is equivalent to the term “fault mode” in
IEC Multilingual Dictionary: 2001 edition.
2.3.83 failure tolerance
attribute of an item that makes it able to perform a required function in the
presence of certain given sub-item failures
2.3.84 fault
state of an item characterized by inability to perform as required
NOTE 1 A fault can be the result of a failure of the item
itself or can exist without prior failure.
NOTE 2 A fault can generate a failure.
2.3.85 fault tolerance
attribute of an item that makes it able to perform a required function in the
presence of certain given sub-item faults
2.3.86 firmware
hardware that contains a computer program or data that cannot be changed in
its user environment
NOTE The computer program and data contained in
firmware are classified as software; the circuitry
containing the computer program and data is
classified as hardware.
2.3.87 flammability
measure of the ease with which a material is set on fire
2.3.88 flight model
end product that is intended for flight
NOTE 1 The flight model is subjected to formal functional and
environmental acceptance testing.
NOTE 2 More detailed information on the build standard and
the use of this model is given in ECSS-E-HB-10-02.
2.3.89 flight operations
all activities related to the planning, execution and evaluation of the control of
the space segment when in orbit
2.3.90 flight spare
spare flight model that could be used in place of the flight model
NOTE 1 Exceptionally, a refurbished qualification model can
be used as a flight spare.
NOTE 2 More detailed information on the build standard and
the use of this model is given in ECSS-E-HB-10-02.
2.3.91 forward contamination
contamination of celestial bodies other than the Earth by terrestrial life forms in
the course of spaceflight missions
2.3.92 function
intended effect of a product
2.3.93 function tree
hierarchical breakdown of a function into successive levels of function
2.3.94 functional analysis
process that describes completely the functions and their relationships, which
are systematically characterised, classified and evaluated
2.3.95 ground segment
part of a space system, located on ground, which monitors and controls space
segment element(s)
NOTE A ground segment is composed of one or more
ground segment elements.
2.3.96 ground segment element
element within a ground segment
NOTE 1 A ground segment element can be composed of
several ground segment elements, e.g. a ground
station network is a ground segment element that
can be composed of a set of ground stations and a
communication network.
NOTE 2 Examples are given in Annex B.2.
2.3.97 ground segment equipment
equipment within a ground segment
NOTE Examples are given in Annex B.2.
2.3.98 ground segment subsystem
subsystem within a ground segment
NOTE Examples are given in Annex B.2.
2.3.99 ground segment system
system within a ground segment
NOTE Examples are given in Annex B.2.
2.3.100 ground support equipment
non flight product (hardware/software) used on ground to assemble, integrate,
test, transport, access, handle, maintain, measure, calibrate, verify, protect or
service a flight product (hardware/software)
2.3.101 handbook
non-normative document providing background information,
orientation, advice or recommendations related to one specific discipline or to a
specific technique, technology, process or activity
2.3.102 hazard
existing or potential condition that can result in a mishap
NOTE 1 This condition can be associated with the design,
manufacturing, operation or environment.
NOTE 2 Hazards are not events but potential threats to
safety.
2.3.103 hazardous event
mishap resulting from a hazard
2.3.104 hot redundancy
redundancy where all entities are powered on with only one operating
2.3.105 human factors
model of observed human physical and psycho-physiological behaviour in
relation to environment and product
2.3.106 implementation document
formal response from the supplier to the customer’s Project Requirements
Document describing how all requirements will be met
2.3.107 incident
unexpected event that might be, or could lead to, an operational interruption,
disruption, loss, emergency, crisis or accident
NOTE Incidents are recorded for further assessment.
2.3.108 informative
providing non-normative information intended to assist the understanding or
use of requirements
2.3.109 inhibit
design feature that prevents a function from undesirable execution
NOTE An inhibit can be software or hardware.
2.3.110 inspection
conformance evaluation by observation and judgement accompanied as
appropriate by measurement, testing or gauging
[ISO 9000:2005]
2.3.111 integration
functionally combining lower-level functional entities (hardware or software)
so they operate together to constitute a higher-level functional entity
NOTE Assembly is a pre-requisite for integration.
2.3.112 interchangeability
ability of a product to be used in place of another to fulfil the same
requirements
2.3.113 interface
boundary where two or more products meet and interact
2.3.114 launch base
composed of launch range and launch complexes
2.3.115 launch campaign
launch activities which include:
• Launcher preparation and final integration
• Payload processing and integration on the launcher
• Launch Operations including Flight Data Gathering
2.3.116 launch complex
integration and facilities necessary to carry out the final integration of the
launcher elements as well as the launch operations
NOTE A Launch System is associated with its specific
Launch Complex, which may include facilities
shared with other Launch Systems (e.g.: Lox plant
at CSG).
2.3.117 launch operations
all launch related activities taking place after completion of the acti
...