ECSS-Q-ST-10C Rev.

1
15 March 2016

Space product
assurance
Product assurance management

ECSS Secretariat
ESA-ESTEC
Requirements & Standards Division
Noordwijk, The Netherlands
 ECSS-Q-ST-10C Rev.1
15 March 2016

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 industry
associations for the purpose of developing and maintaining common standards. Requirements in this
Standard are defined in terms of what shall be accomplished, rather than in terms of how to organize
and perform the necessary work. This allows existing organizational structures and methods to be
applied where they are effective, and for the structures and methods to evolve as necessary without
rewriting the standards.
This Standard has been prepared by the ECSS-Q-ST-10C Rev.1 Working Group, reviewed by the ECSS
Executive Secretariat and approved by the ECSS Technical Authority.

Disclaimer
ECSS does not provide any warranty whatsoever, whether expressed, implied, or statutory, including,
but not limited to, any warranty of merchantability or fitness for a particular purpose or any warranty
that the contents of the item are error-free. In no respect shall ECSS incur any liability for any
damages, including, but not limited to, direct, indirect, special, or consequential damages arising out
of, resulting from, or in any way connected to the use of this Standard, whether or not based upon
warranty, business agreement, tort, or otherwise; whether or not injury was sustained by persons or
property or otherwise; and whether or not loss was sustained from, or arose out of, the results of, the
item, or any services that may be provided by ECSS.

Published by: ESA Requirements and Standards Division

ESTEC, P.O. Box 299,
2200 AG Noordwijk
The Netherlands
Copyright: 2016 © by the European Space Agency for the members of ECSS

2
 ECSS-Q-ST-10C Rev.1
15 March 2016

Change log

ECSS-Q-ST-10A Never issued

ECSS-Q-ST-10B Never issued
ECSS-Q-ST-10C First issue
15 November 2008 Transfer of PA related requirements from the ECSS-Q-20B standard.
ECSS-Q-ST-10C Rev.1 First issue, Revision 1
15 March 2016 Major changes of this version with regard to the previous version are:
 Update of the list of terms from ECSS-ST-00-01 in clause 3.1
 Pre-Tailoring matrix (Clause 6) added
 Addition of new DRD for "Qualification certificate for launch
segment" at Annex C, causing renumbering of former Annex C
(informative) to Annex D
 Removal of phases columns 0 to E and addition of "X*" in row
"Critical-Item List" column "LRR" of Table D-1
 Implementation of Change Requests (CR-Q-ST-10C_01 to 04)

Added requirements
 5.2.1m to p; Annex C.2.1a (in new Annex C "Qualification
certificate for launch segment - DRD").
Modified requirement
 5.2.1h NOTE; A.2.1<3.1>a; A.2.1<3.2>a; A.2.1<10>a (Example in
requirement modified and put as NOTE 2); B.2.1a.1.
Deleted requirements
 None
Editorial corrections:
Annex A.1.1; First sentence of Annex D " PA document delivery with
respect to milestones ".

3
 ECSS-Q-ST-10C Rev.1
15 March 2016

Table of contents

Change log ................................................................................................................. 3

1 Scope ....................................................................................................................... 6

2 Normative references ............................................................................................. 7

3 Terms, definitions and abbreviated terms............................................................ 8

3.1 Terms and definitions from other standards .............................................................. 8
3.2 Abbreviated terms..................................................................................................... 9

4 Principles .............................................................................................................. 10
4.1 General principles ................................................................................................... 10
4.2 PA programme planning ......................................................................................... 10
4.3 PA programme implementation............................................................................... 11

5 Requirements........................................................................................................ 12
5.1 PA programme planning ......................................................................................... 12
5.1.1 Product Assurance organization and responsibilities................................. 12
5.1.2 PA management interfaces ....................................................................... 13
5.1.3 PA plan ..................................................................................................... 13
5.2 PA programme implementation............................................................................... 13
5.2.1 Product assurance management............................................................... 13
5.2.2 PA reporting .............................................................................................. 15
5.2.3 Project PA audits ...................................................................................... 15
5.2.4 Critical items control and PA interfaces to project risk management ......... 16
5.2.5 Documentation and data control................................................................ 16
5.2.6 Quality records .......................................................................................... 16
5.2.7 PA contribution to configuration management ........................................... 16
5.2.8 Nonconformance control ........................................................................... 17
5.2.9 Management of alerts ............................................................................... 17

6 Pre-tailoring matrix per space product types and project phases ................... 19

Annex A (normative) Product Assurance Plan (PAP) - DRD................................ 25

4
 ECSS-Q-ST-10C Rev.1
15 March 2016
Annex B (normative) Qualification Status List - DRD ........................................... 28

Annex C (normative) Qualification Certificate for Launch Segment - DRD ........ 31

Annex D (informative) PA document delivery with respect to milestones ......... 34

Bibliography............................................................................................................. 35

Figures
Figure B-1 : Example of a Qualification status list (QSL) ...................................................... 30

Tables
Table D-1 : PA document requirement list with respect to milestones................................... 34

5
 ECSS-Q-ST-10C Rev.1
15 March 2016

1
Scope

The ECSS standards of the Q branch describe a set of requirements for a

Product Assurance programme to be implemented throughout the phases of a
space project.
This document defines the Product assurance management requirements for
space projects.
This document is structured in two main parts, the first part presenting the
principles of Product Assurance management and the second providing the
detailed requirements.
In addition, the expected content of the Product Assurance plan is specified in
Annex A. Information on the expected delivery of ECSS PA management
discipline documents per review is provided in Annex D.
This Standard is applicable to all space projects.
This standard may be tailored for the specific characteristic and constrains of a
space project in conformance with ECSS-S-ST-00.

6
 ECSS-Q-ST-10C Rev.1
15 March 2016

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 to agreements based on this ECSS Standard are
encouraged to investigate the possibility of applying the more recent editions of
the normative documents indicated below. For undated references, the latest
edition of the publication referred to applies.

ECSS-S-ST-00-01 ECSS system – Glossary of terms

ECSS-Q-ST-10-04 Space product assurance – Critical-item control
ECSS-Q-ST-10-09 Space product assurance – Nonconformance control
system

7
 ECSS-Q-ST-10C Rev.1
15 March 2016

3
Terms, definitions and abbreviated terms

3.1 Terms and definitions from other standards

For the purpose of this Standard, the terms and definitions from ECSS-ST-00-01
apply, in particular for the following terms:
acceptance
alert
approval
assembly
audit
component
configuration item
conformance
critical item
customer
dependability
failure
function
nonconformance
performance
planetary protection
procedure
process
product
product assurance
project
qualification
quality assurance
review

8
 ECSS-Q-ST-10C Rev.1
15 March 2016
risk
safety
space mission
supplier
system
traceability
waiver

3.2 Abbreviated terms

For the purpose of this Standard, the abbreviated terms from ECSS-S-ST-00-01
and the following apply:

Abbreviation Meaning
EEE electrical, electronic, electromechanical

MIP mandatory inspection point

PA product assurance

QA quality assurance

QSL qualification status list

9
 ECSS-Q-ST-10C Rev.1
15 March 2016

4
Principles

4.1 General principles

The prime objective of Product Assurance is to ensure that space products
accomplish their defined mission objectives in a safe, available and reliable
way.
Commitment to quality of the entire organization is key to the Quality of the
product and success of the space mission. The management of Product
Assurance is fully embedded in the management of the project and receives the
highest priority from the organization management.
The early identification of aspects potentially detrimental for safety and mission
success, and the cost-effective prevention of any adverse consequence of such
aspects are the basic principles for the ECSS Product Assurance requirements.
Product Assurance Management ensures the integration of activities from the
Product Assurance disciplines defined in the other ECSS standards of the Q
branch, namely:
 Q-20 Quality assurance
 Q-30 Dependability
 Q-40 Safety
 Q-60 Electrical, electronic, electromechanical (EEE) components
 Q-70 Materials, mechanical parts and processes
 Q-80 Software product assurance

4.2 PA programme planning

The requirements for Product Assurance planning specified in clause 5.1
address the following aspects:
 Definition of a Product Assurance organization with the allocation of
adequate resources, personnel and facilities
 Definition of Product Assurance requirements for lower tier suppliers
 Definition of a Product Assurance Plan describing the Product Assurance
programme and how it fulfils project objectives and requirements

10
 ECSS-Q-ST-10C Rev.1
15 March 2016

4.3 PA programme implementation

The requirements for Product Assurance programme implementation specified
in clause 5.2 address the following aspects:
 Management and control of the PA tasks performed by the PA
disciplines
 Progress reporting of all Product Assurance matters
 Management of audits, critical items, nonconformances and alerts,
 Support to the risk management, in coordination with the Project
Management functions
 Support to the documentation and data control , quality records and to
configuration management.
 Lower-tier supplier control for ensuring implementation of PA
requirements by the suppliers

11
 ECSS-Q-ST-10C Rev.1
15 March 2016

5
Requirements

5.1 PA programme planning

5.1.1 Product Assurance organization and

responsibilities

5.1.1.1 Organization
a. The supplier shall identify the personnel responsible for implementing
and performing PA management and other PA disciplines.
b. The supplier shall assign a project PA manager reporting to the project
manager and having unimpeded access to higher management.
c. The appointed project PA manager, irrespective of other responsibilities,
shall have organizational authority to establish and implement a product
assurance programme in accordance with the project product assurance
requirements.
d. The project PA Manager shall act as the focal point of contact within the
project concerning Product Assurance matters.
NOTE The project PA manager is referred to as “PA
manager” in the rest of this document.

5.1.1.2 Responsibility and authority

a. The supplier shall define and document the responsibility, the authority
and the interrelation of personnel who manage, perform and verify work
affecting product assurance.
b. The supplier shall define and document the responsibilities and the
interfaces of the PA functions, either external or internal, involved in a
project.
c. When the supplier's PA organization delegates product assurance tasks
to another organization it shall be done in a documented and controlled
way monitored by the PA organization.
NOTE The supplier PA organization retains the
responsibility towards the Customer

12
 ECSS-Q-ST-10C Rev.1
15 March 2016
5.1.1.3 Resources
a. The supplier shall identify the PA resources needed to implement the PA
programme.
b. The supplier shall provide resources capable to perform the PA tasks
identified in the PA programme.
c. Reviews and audits of the product assurance programme, of processes or
of product shall be carried out by personnel not directly involved in the
work being performed.

5.1.2 PA management interfaces

a. The PA manager shall interface with project management, ensuring that
the contractual provision and schedule planning for the definition and
phasing of PA activities are met.
b. The PA manager shall interface with risk management, configuration
management, engineering, procurement and AIV for the definition and
execution of tasks in which PA activities are involved.
c. The PA manager shall interface with the customer regarding all Product
Assurance matters.
d. The PA manager shall interface with lower-tier suppliers regarding all
Product Assurance matters.

5.1.3 PA plan
a. The supplier shall prepare, maintain and implement a plan of the PA
activities in accordance with the customer PA requirements.
b. The Product Assurance plan shall be prepared in conformance with DRD
in Annex A.
c. The Product Assurance plan shall be submitted to the customer for
approval.
NOTE 1 The Product Assurance plan can refer to
Clauses of the Company Quality Manual and to
in-house procedures.
NOTE 2 Information on the schedule for delivery of PA
management documents is given in Annex D.

5.2 PA programme implementation

5.2.1 Product assurance management

a. The PA manager shall ensure that PA disciplines are organized at the
beginning of the project according to customer contractual requirements.

13
 ECSS-Q-ST-10C Rev.1
15 March 2016
b. The PA manager shall ensure that the inputs used by the PA disciplines
are consistent and complete, and available in line with the project
schedule.
c. The PA manager shall ensure that the PA disciplines perform the tasks
described in the PA Plan in line with the project schedule.
d. The PA manager shall ensure that the outputs produced by the PA
disciplines are consistent and complete, and delivered in line with the
project schedule.
e. The PA manager shall ensure the application of processes defined in
applicable project plans and documents.
f. The PA manager shall control the quality of his supplier’s products by:
1. issuing product assurance requirements applicable to the supplier
2. ensuring the implementation of the PA requirements by the
supplier.
g. The PA manager shall ensure that PA contributions to verification are
defined and provided.
h. The PA manager shall ensure that a qualification programme is defined,
approved and maintained by the relevant organization.
NOTE Requirement for the qualification programme
are addressed in ECSS-Q-ST-20, ECSS-Q-ST-60,
ECSS-Q-ST-70, ECSS-Q-ST-80, ECSS-E-ST-10-02
and ECSS-E-ST-10-03.
i. The PA manager shall ensure that the qualification programme is
implemented and the qualification results are recorded, evaluated and
documented.
j. The PA manager shall ensure that a Qualification Status List of the
programme items is maintained in conformance with Annex B.
k. The PA manager shall review and approve the achieved qualification
status.
l. The PA manager shall approve the product acceptance during the
Acceptance or Delivery Review.
NOTE The PA manager approval is based on the
outputs of the Acceptance or Delivery Review.
m. For Launch Segment perimeter, the PA manager shall ensure that
Qualification Certificates, identifying the qualified configuration, are
issued for all ground and flight programme items in accordance with
DRD in Annex C.
n. For Launch Segment perimeter, the PA manager shall sign and approve
the certificates specified in req. 5.2.1m. before final programme manager
acceptance.
o. The PA manager shall ensure that a Technology Plan is defined,
approved and maintained by the relevant organization.

14
 ECSS-Q-ST-10C Rev.1
15 March 2016
NOTE The technology plan (TP) supports evaluation
of a critical technology to meet the intended
requirements, and ensure effective preparation
of the technologies necessary for the relevant
product. Technology Plan contents are defined
in ECSS-E-ST-10 Annex E.
p. The PA manager shall ensure that a Technology Readiness Status List
(TRSL) is defined, approved and maintained by the relevant
organization.
NOTE The contents of Technology Readiness Status
List are defined in ECSS-E-ST-10 Annex
E.2.1<5>.

5.2.2 PA reporting
a. The supplier shall report on the status and progress of the product
assurance program implementation.
b. The PA report shall include at least the following items for the reporting
period:
 Progress and accomplishment of each major product assurance
task including resolved and new problems, future planning of
major activities and events
 Status of PA reviews, Audits and MIPs, Waiver requests, Non
conformances (minor and major), Critical items (including
mitigation action plan status), Qualification status, EEE component
status, Material and processes status, Alerts status.
c. The PA progress report may be part of the project progress report.
NOTE The general contents of the project progress
report are detailed in ECSS-M-ST-10 Annex E.

5.2.3 Project PA audits

a. The supplier shall perform audits on his own performance to verify the
implementation and effectiveness of the provisions defined in the PA
plan.
NOTE 1 Audits can be performed by sampling on
various projects or by periodic audits of the
supplier quality system.
NOTE 2 The general contents of project audits are
detailed in ECSS-M-ST-10 clause 5.2.3.
b. The supplier shall establish and maintain an audit plan for procurement
activities on the project, designating the lower tier suppliers to be
audited, the current status and the schedule for auditing.
c. In addition to the planned audits, extra audits shall be performed when
necessary to overcome failure, consistent poor quality, or other problems.

15
 ECSS-Q-ST-10C Rev.1
15 March 2016
d. The supplier shall plan and perform audits using established and
maintained procedures.

5.2.4 Critical items control and PA interfaces to

project risk management
a. The supplier shall establish a critical items control programme in
conformance with ECSS-Q-ST-10-04.
b. The PA manager shall identify and evaluate critical items in support of
the overall project risk management activities.
c. The PA manager shall ensure that a critical item control programme is
implemented to eliminate or mitigate associated risks.

5.2.5 Documentation and data control

a. The PA manager shall ensure that the applicable issues of all documents
and data are available at all locations where activities required for the
implementation of the PA programme are performed.
b. The PA manager shall ensure that invalid or obsolete documents and
data are removed from all points of issue or use, or assured against
unintended use.
c. The PA manager shall ensure that obsolete documents and data retained
for legal or knowledge preservation purposes are identified as such.
d. The PA manager shall identify the project documents requiring approval
including those requiring approval by PA.

5.2.6 Quality records

a. The supplier shall establish and maintain quality records to provide
objective evidence of complete and successful performance of all PA
discipline tasks and to demonstrate compliance with requirements.
NOTE Requirements for the storage, retrieval and
archiving of quality records are addressed in
ECSS-M-ST-40.

5.2.7 PA contribution to configuration

management
a. The PA manager shall verify during Configuration Control Boards the
suitability for release of drawings, plans, specifications, procedures and
changes thereto.
NOTE The operation of Configuration Control Boards
is detailed in ECSS-M-ST-40
b. The PA manager shall ensure that:

16
 ECSS-Q-ST-10C Rev.1
15 March 2016
1. the as designed status is defined and released prior to
manufacturing;
2. the as-built documentation is properly defined, identified and
maintained in order to reflect approved modifications; and
3. items delivered comply with the as-built documentation.

5.2.8 Nonconformance control

a. The supplier shall establish and maintain a nonconformance control
system in conformance with ECSS-Q-ST-10-09.

5.2.9 Management of alerts

a. The supplier shall notify its customer of preliminary information on
failures or problems that can result in an alert.
NOTE 1 The above is applicable to failure or problems
detected by the supplier or by one of his lower
tier suppliers.
NOTE 2 The above is only applicable to failures or
problems meeting all of the following criteria:
 The item with the observed failure or
problem has multiple applications, which
can have implications for more than one
project, thus requiring prompt action.
 The failure or problem has occurred in the
application of an item within the specified
design and usage limitations.
 Failures or problems due to usage within
reasonably expected limits of performance,
but where these limits were not specified
precisely.
 A preliminary investigation has provided
evidence of the root cause of the failure or
problem.
 Failure or problems are confirmed not to be
of a random nature.
b. The supplier shall investigate in cooperation with the originator of the
failure or problem to define the immediate measures to be taken, to
identify the causes, and to recommend corrective actions for similar
items.
c. The PA manager shall ensure:
1. the assessment of any failure having the potential to lead to an
alert by the customer,
2. the investigation, until disposition of the items subject of the
potential alert, and

17
 ECSS-Q-ST-10C Rev.1
15 March 2016
3. the assessment of incoming alerts for the definition,
implementation and follow-up of necessary actions.
d. The supplier shall participate in the alert system organized by the
customer or other sources, by:
1. assessment of the impact of incoming alerts to project work, and
definition, implementation and follow-up of necessary corrective
actions at any contractual level.
2. distribution of incoming alerts to the possible affected users within
the project.
NOTE The alert system is set up for the prompt
interchange of information on failures or
problems which can affect more than one user,
or can recur in other projects or circumstances,
if no preventive actions are taken.

18
 ECSS-Q-ST-10C Rev.1
15 March 2016

6
Pre-tailoring matrix per space product
types and project phases

The Matrix of Table 6-1 presents the pre-tailoring of ECSS-Q-ST-10C Rev. 1 per
space product type.
For the terminology and definitions of the nine space product types see ECSS-S-
ST-00-01. Attention of the reader is drawn to the importance of the precise
meaning of these terms for an appropriate application of the present table.

The applicability of a requirement is specified as follows:

 “A” when applicable,
 “A#” when requirement is applicable with supplementary information in
the “Comment” column
 “X#” when the applicability is to be decided on a case by case basis, with
explanation in the “Comment” column, or
 “NA” when not applicable
The number assigned for comments relating to each relevant column marked
with A# or X# starts at 1 and increases incrementally left to right across the
columns, and then starts afresh on the next row.

19
 ECSS-Q-ST-10C Rev.1
15 March 2016

Table 6-1: Pre-Tailoring matrix for ECSS-Q-ST-10C Rev.1

Space product types

element and sub-

element and sub-

element and sub-

Ground segment

Ground segment
Launch segment

Launch segment

Ground support
Space segment

Space segment
Space system

equipment

equipment

equipment

equipment

Software
ECSS req.

system

system

system
number Comments

5.1.1.1a A A A A A A A NA NA For Software, covered by clause 5.1.4 of ECSS-Q-ST-80

5.1.1.1b A A A A A A A NA NA For Software, covered by clause 5.1.4 of ECSS-Q-ST-80
5.1.1.1c A A A A A A A NA NA For Software, covered by clause 5.1.4 of ECSS-Q-ST-80
5.1.1.1d A A A A A A A NA A

5.1.1.2a A A A A A A A NA NA For Software, covered by clause 5.1.2 of ECSS-Q-ST-80

5.1.1.2b A A A A A A A NA NA For Software, covered by clause 5.1.2.1 of ECSS-Q-ST-80
5.1.1.2c A A A A A A A NA NA For Software, covered by clause 5.1.2.3 of ECSS-Q-ST-80
5.1.1.3a A A A A A A A NA NA For Software, covered by clause 5.1.3 of ECSS-Q-ST-80
5.1.1.3b A A A A A A A NA NA For Software, covered by clause 5.1.3 of ECSS-Q-ST-80
5.1.1.3c A A A A A A A NA NA For Software, covered by clause 5.1.3 of ECSS-Q-ST-80
5.1.2a A A A A A A A NA A

5.1.2b A A A A A A A NA A

5.1.2c A A A A A A A NA A

5.1.2d A A A A A A A NA A
1 Except for suppliers of catalogue OFF-THE-SHELF items such as standard
laboratory equipment, work stations, from whom a dedicated PA plan is not
5.1.3a A A A A A A1 A1 NA NA required

For Software, covered by clause 5.2.1 of ECSS-Q-ST-80

20
 ECSS-Q-ST-10C Rev.1
15 March 2016

Space product types

element and sub-

element and sub-

element and sub-

Ground segment

Ground segment
Launch segment

Launch segment

Ground support
Space segment

Space segment
Space system

equipment

equipment

equipment

equipment

Software
ECSS req.

system

system

system
number Comments

A A A A A A A NA NA For Software, replaced by ECSS-Q-ST-80 Annex B which contains the Software PA

5.1.3b
Plan DRD
5.1.3c A A A A A A A NA A

5.2.1a A A A A A A A NA A

5.2.1b A A A A A A A NA A

5.2.1c A A A A A A A NA A

5.2.1d A A A A A A A NA A

A A A A A A A NA A1
1For Software, processes are defined in clause 5.7 "Assessment and improvement
5.2.1e
process" and clause 6 "Software process assurance" of ECSS-Q-ST-80
5.2.1f A A A A A A A NA NA For Software, covered by clause 5.4.2 of ECSS-Q-ST-80
5.2.1g A A A A A A A NA A
1Except for catalogue OFF-THE-SHELF. Qualification items related to catalogue
OFF-THE-SHELF are covered at a higher level.

5.2.1h A A A A2 A2 A1 A1 NA NA 2 Except NOTE because Launchers have dedicated Qualification programmes

For Software, covered by clause 6.3.5 "Testing and validation" of ECSS-Q-ST-80

5.2.1i A A A A A A A NA NA For Software, covered by clause 6.3.5 "Testing and validation" of ECSS-Q-ST-80
1 For Launch Segment, Ground Segment and Software, the Annex B is Informative
5.2.1j A A A A1 A1 A1 A1 NA A12
2 Note: for Software, qualification is generally replaced by the word "Validation"
5.2.1k A A A A A A A NA A1 1 Note: for Software, qualification is generally replaced by the word "Validation"
5.2.1l A A A A A A A NA A

21
 ECSS-Q-ST-10C Rev.1
15 March 2016

Space product types

element and sub-

element and sub-

element and sub-

Ground segment

Ground segment
Launch segment

Launch segment

Ground support
Space segment

Space segment
Space system

equipment

equipment

equipment

equipment

Software
ECSS req.

system

system

system
number Comments

5.2.1m NA NA NA A A NA NA NA NA

5.2.1n NA NA NA A A NA NA NA NA

5.2.1o A A A A A A A NA NA

5.2.1p A A A A A A A NA NA

5.2.2a A A A A A A A NA NA For Software, covered by clause 5.2.2 of ECSS-Q-ST-80

5.2.2b A A A A A A A NA NA For Software, covered by clause 5.2.2 of ECSS-Q-ST-80
5.2.2c A A A A A A A NA A1 1 For Software, see also clause 5.2.2.1 of ECSS-Q-ST-80
5.2.3a A A A A A A A NA A1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80
5.2.3b A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80
5.2.3c A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80
5.2.3d A A A A A A A NA A 1 1 ECSS-Q-ST10 requirement declared applicable in ECSS-Q-ST-80
1 the list of criteria in ECSS-Q-ST-10-04 tailored for applicability to ground products
5.2.4a A A A A A A1 A1 NA A2
2 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 5.3.2
5.2.4b A A A A A A A NA A1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 5.3.1
5.2.4c A A A A A A A NA A1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 5.3.2
5.2.5a A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 6.2.4.7
5.2.5b A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 6.2.4.7
5.2.5c A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 6.2.4.7
5.2.5d A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in ECSS-Q-ST-80 clause 6.2.4.7

A A A A A A A NA NA For Software, covered by clauses 6.2.1, 7.2.2 and 7.2.3, Annex A and F of ECSS-Q-ST-
5.2.6a
80

22
 ECSS-Q-ST-10C Rev.1
15 March 2016

Space product types

element and sub-

element and sub-

element and sub-

Ground segment

Ground segment
Launch segment

Launch segment

Ground support
Space segment

Space segment
Space system

equipment

equipment

equipment

equipment

Software
ECSS req.

system

system

system
number Comments

5.2.7a A A A A A A A NA NA For Software, covered by clause 6.2.4 of ECSS-Q-ST-80

5.2.7b A A A A A A A NA NA For Software, covered by clause 6.2.4 of ECSS-Q-ST-80
1ECSS-Q-ST-10-09 clause 6 (Special nonconformance control requirements) has to be
tailored for Launchers
NOTE Principles developed in the ECSS-Q-ST-10-09 standard are very close to the
A A A A1 A1 A A NA A2 one used in Launchers in particular regarding rules in order to implement an
5.2.8a
exhaustive non-conformance analysis. But there are some differences between the 2
approach (difficult to assess in short term). ECSS-Q-ST-10-09 should be extensively
reviewed.
2 ECSS-Q-ST-10 requirement declared applicable in clause 5.2.6 of ECSS-Q-ST-80
5.2.9a A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in clause 5.2.4 of ECSS-Q-ST-80
5.2.9b A A A A A A A NA A1 1 ECSS-Q-ST-10 requirement declared applicable in clause 5.2.4 of ECSS-Q-ST-80
5.2.9c A A A A A A A NA A1 1 ECSS-Q-ST-10 requirement declared applicable in clause 5.2.4 of ECSS-Q-ST-80
5.2.9d A A A A A A A NA A 1 1 ECSS-Q-ST-10 requirement declared applicable in clause 5.2.4 of ECSS-Q-ST-80
A.2.1<1>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<2>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<3.1>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<3.2>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<4>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<5>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<6>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<7>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD

23
 ECSS-Q-ST-10C Rev.1
15 March 2016

Space product types

element and sub-

element and sub-

element and sub-

Ground segment

Ground segment
Launch segment

Launch segment

Ground support
Space segment

Space segment
Space system

equipment

equipment

equipment

equipment

Software
ECSS req.

system

system

system
number Comments

A.2.1<8>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD

A.2.1<9>a A1 A1 A1 A1 A1 A1 A1 NA NA 1 ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.1<10>a A A A A A A A NA NA ECSS-Q-ST-80 Annex B contains the Software PA Plan DRD
A.2.2a A A A A A A A NA A

A.2.2b A A A A A A A NA NA

B.2.1a A A A NA NA NA NA NA NA For Launch Segment, Ground Segment and Software, the Annex B is Informative
B.2.2a A A A NA NA NA NA NA NA For Launch Segment, Ground Segment and Software, the Annex B is Informative
C.2.1a NA NA NA A A NA NA NA NA

24
 ECSS-Q-ST-10C Rev.1
15 March 2016

Annex A (normative)
Product Assurance Plan (PAP) - DRD

A.1 DRD identification

A.1.1 Requirement identification and source document

This DRD is called by the ECSS-Q-ST-10, requirement 5.1.3b.

A.1.2 Purpose and objective

The objective of the PAP is to describe the activities to be performed by the
supplier to assure the quality of the space product with regard to the specified
mission objectives and to demonstrate compliance to the applicable PA
requirements.

A.2 Expected response

A.2.1 Scope and content

<1> Introduction
a. The PAP shall introduce the purpose, objective and the reason prompting
its preparation.
NOTE For example: programme or project reference
and phase.

<2> Applicable and reference documents

a. The PAP shall list the applicable and reference documents in support of
the generation of the document.

<3> Product assurance management

<3.1> PA Planning
a. The PAP shall describe the organization (including responsibilities and
authorities), the activities, processes and procedures to be applied by the

25
 ECSS-Q-ST-10C Rev.1
15 March 2016
supplier to fulfil the applicable product assurance planning requirements
defined in clause 5.1 of ECSS-Q-ST-10.

<3.2> PA implementation
a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable product assurance
implementation requirements defined in clause 5.2 of ECSS-Q-ST-10.

<4> Quality assurance

a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable quality assurance
requirements.

<5> Dependability
a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable dependability
requirements.

<6> Safety
a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable safety requirements.

<7> EEE components

a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable EEE Component
requirements.

<8> Materials and processes

a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable Material and Processes
requirements.

<9> Software product assurance

a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil the applicable Software product
assurance requirements.

<10> Other PA requirements

a. The PAP shall describe the activities, processes and procedures to be
applied by the supplier to fulfil all other applicable PA requirements not
covered in the clause A.2.1<3> to clause A.2.1<9>.
NOTE 1 The order of the sections is not mandatory.
NOTE 2 For example: Security, Planetary protection,
Off-The-Shelf, Customer furnished equipment,

26
 ECSS-Q-ST-10C Rev.1
15 March 2016
Integrated logistic support, Production
preparation, Launch system exploitation,
Involvement of relevant Surveillance Authority
Representatives, National Surveillance
Organizations for Launch Segment.

A.2.2 Special remarks

a. The response to this DRD may be combined with the response to the
project management plan, as defined in ECSS-M-ST-10.
b. The response to this DRD may be performed by reference to separate
discipline plans addressing some of the above clauses of this DRD.

27
 ECSS-Q-ST-10C Rev.1
15 March 2016

Annex B (normative)
Qualification Status List - DRD

B.1 DRD identification

B.1.1 Requirement identification and source document

This DRD called by the ECSS-Q-ST-10, requirement 5.2.1j

B.1.2 Purpose and objective

A Qualification Status List (QSL) is issued at equipment, subsystem and system
levels.
The purpose and objective if this QSL document is to summarize for each
configuration item the status achieved with respect to the planned qualification.

B.2 Expected response

B.2.1 Scope and content

a. The QSL shall include or refer to the following information:
1. Equipment, Subsystem, Element designation:
(a) Identification of hardware by name,
(b) Configuration Item number and model.
2. Next higher assembly level :
(a) Identification of next higher assembly.
3. Manufacturer's name :
(a) Identification of Item Supplier.
4. Reference of requirements documents
(a) Reference numbers of applicable requirement specifications.
5. Design heritage:
(a) Specify if the design is “New”, otherwise identification of
the project in which the design was used.
(b) Summary of current qualification status:

28
 ECSS-Q-ST-10C Rev.1
15 March 2016
 Basis for qualification (qualification test results, heritage,
and qualification on other projects) programme on which
the qualification test was conducted;
 Project on which the test was conducted.
6. Proposed category A, B, C, or D (related to Design heritage):
NOTE Qualification approach as defined in the ECSS-
E-ST-10-02.
7. Reference of Qualification plan document:
(a) Current qualification status/screening and applicability of
qualification test versus requirements.
(b) Reference numbers of Qualification Plan(s).
(c) Identification of developments models (EM, EQM, QM,
PFM) to be manufactured and tested for the project.
8. Reports:
(a) Reference to Verification Control Document and/or
reference to Analyses, Test and Inspection Reports;
(b) Qualification Authority: Organization in charge of the item
qualification (if any).
9. The qualification status:
o QUALIFIED,
o TO BE QUALIFIED,
o QUALIFICATION IN PROGRESS
10. Open Actions / Due dates/Remarks:
(a) For an open action: summary of missing qualification
actions and planned dates for the closure of such actions.
(b) List of major NCRs and associated waivers to the
qualification items

B.2.2 Special remarks

a. The form may be a table which contains the here above information of
B.2.1 or reference to separate document.
NOTE An example of such a table is shown in Figure
B-1.

29
 ECSS-Q-ST-10C Rev.1
15 March 2016

Item Next Manufacturer's Requirements Design Heritage Qualification

Designation Higher name Specifications
Assembly
Summary data Category Development Plans/ Reports Status Open actions /
Model Procedures Due dates/
Remarks
(1) (2) (3) (4) (5) (6) (7) (7) (8) (9) (10)

Figure B-1: Example of a Qualification status list (QSL)

30
 ECSS-Q-ST-10C Rev.1
15 March 2016

Annex C (normative)
Qualification Certificate for Launch
Segment - DRD

C.1 DRD identification

C.1.1 Requirement identification and source document

This DRD called by the ECSS-Q-ST-10, requirement 5.2.1m.

C.1.2 Purpose and objective

The Qualification Certificate for launch segment is the document that formalises
the qualification and identifies the qualified configuration.
NOTE A product or subsystem can only be formally
declared as qualified and thus be allocated a
Qualification Certificate, once all the residual
actions (e.g. arising from qualification reviews)
have been dealt with.
The purpose and objective of this document is to certify the qualification, and in
particular that the product or subsystem meets the agreed initial requirements.
In signing the certificate, the signing entities certify:
a. That the definition meets the requirements defined in the technical
specification including the general design rules and applicable interface
control requirements, as specified in the justification file;
b. That the definition of the first item representative of recurrent production
does not call into question the qualification of the product and its
production process.
c. That, within the framework of the qualification certificate, all the
qualification-blocking reservations, raised at the end of the Qualification
Review or during other First Article configuration reviews, have been
resolved.

31
 ECSS-Q-ST-10C Rev.1
15 March 2016

C.2 Expected response

C.2.1 Scope and content

a. The Qualification Certificate shall include or refer to at least the following
information:
1. Scope of the “Qualification Certificate” and its use in exploitation
phase:
(a) Clarification of the potential verification activities to be
performed and completed in the exploitation phase in order
to maintain the qualification status.
2. Qualification acceptance status:
(a) Statement regarding the acceptance of the Qualification
Certificate.
3. Product identification:
(a) Product identification reference;
(b) Design authority;
(c) Qualification acceptance responsible;
(d) Contractor;
(e) Development contracts reference.
4. Development key points performed:
(a) Reviews;
(b) Tests.
5. Reference documentation product:
(a) List of documentation related to the definition of the
“product”, with the indication of acceptance by customer
(issue, revision) when relevant;
(b) Other relevant documents related to the justification of the
“product”, with the indication of acceptance by customer
(issue, revision) when relevant.
6. Declaration of conformity by the supplier
7. Product Breakdown Structure
8. Status of elementary subsystem products Qualification Certificates
9. Reserves to qualification and limitation of use, including:
(a) Open critical points;
(b) Technical reserves to qualification;
(c) Deviations to Design Rules;
(d) Documentary reserves;
(e) Other reserves.

32
 ECSS-Q-ST-10C Rev.1
15 March 2016
10. Qualification perimeter:
(a) Applicable configuration status.
11. Open points:
(a) open actions (e.g. arising from development) to be carried
out in order to close the identified reservations.
NOTE 1 Examples of verification activities as per point 1:
Verification of the deviations w.r.t. the
applicable configuration, of the open critical
points.
NOTE 2 Non-exhaustive list of the Reference
documentation product includes as per point 5:
Requirements such as Applicable documents
and Technical Specifications, Dimensioning
cases file and margin policy, Definition
documentation such as Functional File,
Industrial File and User manuals, Spécifications
de Mise en Oeuvre (SMO), Configuration
Register.
Non-exhaustive list of other relevant
documents to be indicated includes: Critical
Point Log, Justification File.
NOTE 3 Example of a Declaration of Conformity by the
supplier as per point 6:
“It is hereby certified:
 That the product production definition is
fully and solely defined by the Functional
and Industrial Files referred and
configuration register to above.
 That the definition meets the requirements
(specified in the Technical Specification, etc.)
as identified in the Justification File (DJ) and
checked by the Qualification Board with the
exception of waiver and/or reservation.
 That the definition of ‘First Article’
representative of recurrent production in no
way calls into question the qualification
neither of the product nor of its production
process.
 It is certified that the above mentioned
points are verified, except for blocking
reserves identified in appendix.”

C.2.2 Special remarks

In accordance with requirement 5.2.1m., Qualification Certificates are issued for
all ground and flight subsystems within the Launch Segment perimeter, and
endorsed by the PA manager.

33
 ECSS-Q-ST-10C Rev.1
15 March 2016

Annex D (informative)
PA document delivery with respect to milestones

Table D-1 presents the reviews at which the different issues of the Product Assurance plan and the critical item list are expected.
NOTE Other PA deliverable document requirement lists are contained in the ECSS-Q-Series Level 2
documents.

Table D-1: PA document requirement list with respect to milestones

Review
Document Title DRD Ref.
MDR PRR SRR PDR CDR QR AR ORR FRR LRR CRR ELR

Product Assurance Plan (X) (X) X X (XX) ECSS-Q-ST-10, Annex A

Critical-Item List (X) X X X X X X* ECSS-Q-ST-10-04, Annex A

Qualification Status List (X) X X X X ECSS-Q-ST-10, Annex B

(X): Preliminary version

(XX) PA Plan covering Operational Phase
X* For recurring products including Launchers , Critical Items list is maintained also during Phase E (e.g. LRR)

34
 ECSS-Q-ST-10C Rev.1
15 March 2016

Bibliography

ECSS-S-ST-00 ECSS system – Description, implementation and general

requirements
ECSS-E-ST-10-02 Space engineering – Verification
ECSS-E-ST-10-03 Space engineering – Testing
ECSS-M-ST-10 Space project management – Project planning and
implementation
ECSS-M-ST-40 Space project management – Documentation and
information management
ECSS-Q-ST-20 Space product assurance – Quality assurance
ECSS-Q-ST-30 Space product assurance – Dependability
ECSS-Q-ST-40 Space product assurance – Safety
ECSS-Q-ST-60 Space product assurance – Electrical, electronic,
electromechanical (EEE) components
ECSS-Q-ST-70 Space product assurance – Materials, mechanical parts
and processes
ECSS-Q-ST-80 Space product assurance – Software product assurance

35