ISO 10795:2019
(Main)Space systems — Programme management and quality — Vocabulary
Space systems — Programme management and quality — Vocabulary
This document provides definitions of all common terms used in the area of space systems and operations for programme management and quality. It does not contain terms specific to an individual International Standard in the area of space systems and operations, which are defined in that particular International Standard.
Systèmes spatiaux — Management de programme et qualité — Vocabulaire
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 10795
Second edition
2019-07
Space systems — Programme
management and quality —
Vocabulary
Systèmes spatiaux — Management de programme et qualité —
Vocabulaire
Reference number
©
ISO 2019
© ISO 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms .39
Bibliography .40
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles,
Subcommittee SC 14, Space systems and operations.
This second edition cancels and replaces the first edition (ISO 10795:2011), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— the following terms have been added: acceptable risk, acceptance of risk, assurance, authorization,
availability, breadboard, breakdown structure, cause, caution condition, certificate of conformity,
certification, commissioning, counterfeit part, critical , critical , flight spare,
functional specification, ground segment, implementation document, information system, interface
control document, key characteristic, milestone, orbital disposal, qualification model, re-entry,
review board, space segment, space segment element, special requirements, systems engineering,
and systems engineering management;
— the following terms have been removed: audit client, audit conclusion, audit criteria, audit evidence,
audit findings, availability of an item, certificate of compliance, certification procedure, Critical,
launch vehicle, non-conformance, normative reference, organizational structure, part, quality
manual, quality planning, space element, and spare parts.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
iv © ISO 2019 – All rights reserved
Introduction
It is intended that this document be applied for the management, engineering, and product assurance in
space projects and applications. The definitions in this document specify what is accomplished, rather
than how the necessary work is organized and carried out. This allows the application of existing
organizational structures and methods where they are effective, and for the structures and methods
to evolve as necessary without rewriting the standards. The formulation of this document takes into
account the existing International Standards prepared by ISO/TC 176, Quality management and quality
assurance.
INTERNATIONAL STANDARD ISO 10795:2019(E)
Space systems — Programme management and quality —
Vocabulary
1 Scope
This document provides definitions of all common terms used in the area of space systems and
operations for programme management and quality. It does not contain terms specific to an individual
International Standard in the area of space systems and operations, which are defined in that particular
International Standard.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.1
acceptable risk
safety (3.210) risk (3.206), the severity (3.215) and the probability of which may be reasonably accepted
by humanity, without durable or irreversible foreseeable consequence on health, Earth, and the
environment (3.92), at the present time and in the future
EXAMPLE A safety risk may be acceptable for crew members of a manned space vehicle (3.225) when it
is comparable to that of test (3.239) pilots, for the personnel participating in hazardous activities when it is
comparable to that of industrial workers, for people, public and private property, and the environment, when it is
comparable to that of other hazardous human activities (e.g. high-speed surface travel).
[SOURCE: ISO 14620-2:2011, 3.1]
3.2
acceptance
act, means of which customer (3.78) certifies that the object developed and manufactured in
accordance with his/her specification (3.227), and he/she agrees with the reveal deviations (3.86) and
failures (3.98) ("complaints") and that this object is free from defects (3.79) under its delivery by the
supplier (3.232)
3.3
acceptance
part of the verification (3.244) process (3.171), which demonstrates that the product (3.173)
meets specified acceptance margins
[SOURCE: EN 16601-00-01:2015, 2.3.2]
3.4
acceptance criteria
minimum requirements (3.201) that it is necessary for an item (3.134) to satisfy for formal acceptance
(3.2, 3.3)
3.5
acceptance of risk
decision to cope with consequences, should a risk (3.206) scenario materialize
Note 1 to entry: A risk can be accepted when its magnitude is less than a given threshold, defined in the risk
management policy (3.209).
Note 2 to entry: In the context of risk management (3.208), acceptance (3.2, 3.3) can mean that even though a risk
is not eliminated, its existence and magnitude are acknowledged and tolerated.
[SOURCE: ISO 17666:2016, 3.1.1]
3.6
accepted risk
hazard (3.120) that has not been eliminated and for which the residual risk (3.202) is deemed low enough
to continue operation and that has been accepted by project (3.178)/program management (3.146) on
the basis of documented risk (3.206) acceptance (3.2, 3.3) rationale
3.7
acceptance test
test (3.239) to determine that a system (3.234), subsystem (3.231), component (3.48) or functional part
is capable of meeting performance (3.166) requirements (3.201) prescribed in a purchase specification
(3.227) or other document (3.88) specifying what constitutes the adequate performance capability for
the item (3.134) and to demonstrate that the item is free from manufacturing defects (3.79)
3.8
accident
mishap
undesired event arising from operation of any project (3.178)-specific items (3.134) which results in:
a) human death or injury;
b) loss of, or damage to, hardware (3.119), software (3.217) or facilities which could then affect the
accomplishment of the mission (3.154);
c) loss of, or damage to, public or private property; or
d) detrimental effects on the environment (3.92)
[SOURCE: ISO 14620-1:2018, 3.1.1, modified — The term "mishap" has been added as an alternative.]
3.9
action
task negotiated between two and only two persons, one decision maker and one holder, whose result
leads to an expected result as a description of an operation in the formulation of a solution, and is
characterized by objectives in terms of cost, quality (3.188) and due date
3.10
action item
assignment to a designated organization (3.163) or individual the accomplishment of a defined objective
within a specified time frame
3.11
alert
formal notification to users, informing them of a failure (3.98) or nonconformity (3.157) of an item
(3.134), already released for use or not, that can also be present on other items already delivered (e.g.
items with identical design (3.82, 3.83) concept, material (3.148), component (3.48) or process (3.171))
Note 1 to entry: An alert can also be raised when a deficiency in a specified requirement (3.201) that can affect
the fitness for purpose in the defined application has been identified.
[SOURCE: EN 16601-00-01:2015, 2.3.6]
2 © ISO 2019 – All rights reserved
3.12
analysis
verification (3.244) method utilizing techniques and tools such as math models (3.155), compilation
similarity assessments (3.24), validation (3.243) of records (3.194), etc., to confirm that verification
requirements (3.201) have been satisfied
3.13
anomaly
gap between a current situation and an expected one
Note 1 to entry: An anomaly justifies an investigation that can lead to the discovery of a nonconformance, a defect
(3.79) or a “non-lieu” (deviation (3.86) without impact, e.g. product (3.173) peculiarity).
Note 2 to entry: A deviation may be declared, foreseen or requested.
Note 3 to entry: An anomaly is often detected in comparison with what seems to be standard or with the
expected use.
3.14
applicable document
document (3.88) that contains provisions (3.181) which, through reference in the source document,
incorporates additional provisions in the source document
Note 1 to entry: In this context, a provision is an expression that takes the form of a statement, an instruction, a
recommendation or a requirement (3.201).
3.15
approval
formal agreement by a designated management (3.146) official to use or apply an item (3.134) or
proceed with a proposed course of action (3.9)
Note 1 to entry: Approvals shall be documented.
Note 2 to entry: Approval implies that the approving authority has verified that the item conforms to its
requirements (3.201).
[SOURCE: EN 16601-00-01:2015, 2.3.11]
3.16
as-built configuration
configuration (3.50) of one product (3.173) item (3.134) identified by its gaps of conformity (3.60) with
respect to its applicable configuration
Note 1 to entry: The relevant “as-designed configuration (3.19)” corresponds to the same “part number”.
Note 2 to entry: “As-built configuration” includes any impacts from technical events, anomalies, repairs (3.199),
life potential consumption that occurred before the product delivery and any potential modifications (3.156)
applied on the product but not embodied in the relevant design (3.82, 3.83) data file.
3.17
as-built configuration list
ABCL
reporting instrument defining the “as-built status” for each serial number of a configuration item (3.55)
subject to formal acceptance (3.2, 3.3)
Note 1 to entry: The ABCL shall identify the “as-manufactured” and “as-tested” statuses applicable to a part
comprising a configuration item.
Note 2 to entry: Using the configuration item data list (3.56) as a reference, any difference between the ABCL and
the CIDL (3.56) shall be documented in the ABCL with reference to the applicable NCR and RFW (3.200).
3.18
as-delivered configuration
as-built configuration (3.16) at the time of delivery
3.19
as-designed configuration
current design (3.82, 3.83) status at any point of time providing the complete
...
INTERNATIONAL ISO
STANDARD 10795
Second edition
2019-07
Space systems — Programme
management and quality —
Vocabulary
Systèmes spatiaux — Management de programme et qualité —
Vocabulaire
Reference number
©
ISO 2019
© ISO 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2019 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms .39
Bibliography .40
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles,
Subcommittee SC 14, Space systems and operations.
This second edition cancels and replaces the first edition (ISO 10795:2011), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— the following terms have been added: acceptable risk, acceptance of risk, assurance, authorization,
availability, breadboard, breakdown structure, cause, caution condition, certificate of conformity,
certification, commissioning, counterfeit part, critical , critical , flight spare,
functional specification, ground segment, implementation document, information system, interface
control document, key characteristic, milestone, orbital disposal, qualification model, re-entry,
review board, space segment, space segment element, special requirements, systems engineering,
and systems engineering management;
— the following terms have been removed: audit client, audit conclusion, audit criteria, audit evidence,
audit findings, availability of an item, certificate of compliance, certification procedure, Critical,
launch vehicle, non-conformance, normative reference, organizational structure, part, quality
manual, quality planning, space element, and spare parts.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
iv © ISO 2019 – All rights reserved
Introduction
It is intended that this document be applied for the management, engineering, and product assurance in
space projects and applications. The definitions in this document specify what is accomplished, rather
than how the necessary work is organized and carried out. This allows the application of existing
organizational structures and methods where they are effective, and for the structures and methods
to evolve as necessary without rewriting the standards. The formulation of this document takes into
account the existing International Standards prepared by ISO/TC 176, Quality management and quality
assurance.
INTERNATIONAL STANDARD ISO 10795:2019(E)
Space systems — Programme management and quality —
Vocabulary
1 Scope
This document provides definitions of all common terms used in the area of space systems and
operations for programme management and quality. It does not contain terms specific to an individual
International Standard in the area of space systems and operations, which are defined in that particular
International Standard.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
3.1
acceptable risk
safety (3.210) risk (3.206), the severity (3.215) and the probability of which may be reasonably accepted
by humanity, without durable or irreversible foreseeable consequence on health, Earth, and the
environment (3.92), at the present time and in the future
EXAMPLE A safety risk may be acceptable for crew members of a manned space vehicle (3.225) when it
is comparable to that of test (3.239) pilots, for the personnel participating in hazardous activities when it is
comparable to that of industrial workers, for people, public and private property, and the environment, when it is
comparable to that of other hazardous human activities (e.g. high-speed surface travel).
[SOURCE: ISO 14620-2:2011, 3.1]
3.2
acceptance
act, means of which customer (3.78) certifies that the object developed and manufactured in
accordance with his/her specification (3.227), and he/she agrees with the reveal deviations (3.86) and
failures (3.98) ("complaints") and that this object is free from defects (3.79) under its delivery by the
supplier (3.232)
3.3
acceptance
part of the verification (3.244) process (3.171), which demonstrates that the product (3.173)
meets specified acceptance margins
[SOURCE: EN 16601-00-01:2015, 2.3.2]
3.4
acceptance criteria
minimum requirements (3.201) that it is necessary for an item (3.134) to satisfy for formal acceptance
(3.2, 3.3)
3.5
acceptance of risk
decision to cope with consequences, should a risk (3.206) scenario materialize
Note 1 to entry: A risk can be accepted when its magnitude is less than a given threshold, defined in the risk
management policy (3.209).
Note 2 to entry: In the context of risk management (3.208), acceptance (3.2, 3.3) can mean that even though a risk
is not eliminated, its existence and magnitude are acknowledged and tolerated.
[SOURCE: ISO 17666:2016, 3.1.1]
3.6
accepted risk
hazard (3.120) that has not been eliminated and for which the residual risk (3.202) is deemed low enough
to continue operation and that has been accepted by project (3.178)/program management (3.146) on
the basis of documented risk (3.206) acceptance (3.2, 3.3) rationale
3.7
acceptance test
test (3.239) to determine that a system (3.234), subsystem (3.231), component (3.48) or functional part
is capable of meeting performance (3.166) requirements (3.201) prescribed in a purchase specification
(3.227) or other document (3.88) specifying what constitutes the adequate performance capability for
the item (3.134) and to demonstrate that the item is free from manufacturing defects (3.79)
3.8
accident
mishap
undesired event arising from operation of any project (3.178)-specific items (3.134) which results in:
a) human death or injury;
b) loss of, or damage to, hardware (3.119), software (3.217) or facilities which could then affect the
accomplishment of the mission (3.154);
c) loss of, or damage to, public or private property; or
d) detrimental effects on the environment (3.92)
[SOURCE: ISO 14620-1:2018, 3.1.1, modified — The term "mishap" has been added as an alternative.]
3.9
action
task negotiated between two and only two persons, one decision maker and one holder, whose result
leads to an expected result as a description of an operation in the formulation of a solution, and is
characterized by objectives in terms of cost, quality (3.188) and due date
3.10
action item
assignment to a designated organization (3.163) or individual the accomplishment of a defined objective
within a specified time frame
3.11
alert
formal notification to users, informing them of a failure (3.98) or nonconformity (3.157) of an item
(3.134), already released for use or not, that can also be present on other items already delivered (e.g.
items with identical design (3.82, 3.83) concept, material (3.148), component (3.48) or process (3.171))
Note 1 to entry: An alert can also be raised when a deficiency in a specified requirement (3.201) that can affect
the fitness for purpose in the defined application has been identified.
[SOURCE: EN 16601-00-01:2015, 2.3.6]
2 © ISO 2019 – All rights reserved
3.12
analysis
verification (3.244) method utilizing techniques and tools such as math models (3.155), compilation
similarity assessments (3.24), validation (3.243) of records (3.194), etc., to confirm that verification
requirements (3.201) have been satisfied
3.13
anomaly
gap between a current situation and an expected one
Note 1 to entry: An anomaly justifies an investigation that can lead to the discovery of a nonconformance, a defect
(3.79) or a “non-lieu” (deviation (3.86) without impact, e.g. product (3.173) peculiarity).
Note 2 to entry: A deviation may be declared, foreseen or requested.
Note 3 to entry: An anomaly is often detected in comparison with what seems to be standard or with the
expected use.
3.14
applicable document
document (3.88) that contains provisions (3.181) which, through reference in the source document,
incorporates additional provisions in the source document
Note 1 to entry: In this context, a provision is an expression that takes the form of a statement, an instruction, a
recommendation or a requirement (3.201).
3.15
approval
formal agreement by a designated management (3.146) official to use or apply an item (3.134) or
proceed with a proposed course of action (3.9)
Note 1 to entry: Approvals shall be documented.
Note 2 to entry: Approval implies that the approving authority has verified that the item conforms to its
requirements (3.201).
[SOURCE: EN 16601-00-01:2015, 2.3.11]
3.16
as-built configuration
configuration (3.50) of one product (3.173) item (3.134) identified by its gaps of conformity (3.60) with
respect to its applicable configuration
Note 1 to entry: The relevant “as-designed configuration (3.19)” corresponds to the same “part number”.
Note 2 to entry: “As-built configuration” includes any impacts from technical events, anomalies, repairs (3.199),
life potential consumption that occurred before the product delivery and any potential modifications (3.156)
applied on the product but not embodied in the relevant design (3.82, 3.83) data file.
3.17
as-built configuration list
ABCL
reporting instrument defining the “as-built status” for each serial number of a configuration item (3.55)
subject to formal acceptance (3.2, 3.3)
Note 1 to entry: The ABCL shall identify the “as-manufactured” and “as-tested” statuses applicable to a part
comprising a configuration item.
Note 2 to entry: Using the configuration item data list (3.56) as a reference, any difference between the ABCL and
the CIDL (3.56) shall be documented in the ABCL with reference to the applicable NCR and RFW (3.200).
3.18
as-delivered configuration
as-built configuration (3.16) at the time of delivery
3.19
as-designed configuration
current design (3.82, 3.83) status at any point of time providing the complete
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.