ISO/TR 17400:2003

TECHNICAL ISO/TR
REPORT 17400
First edition
2003-02-15

Space systems — Space launch
complexes, integration sites and other
facilities — General testing guidelines
Systèmes spatiaux — Complexes de lancement spacial, sites
d'intégration et autres installations — Lignes directrices pour les essais




Reference number
ISO/TR 17400:2003(E)
©
ISO 2003

---------------------- Page: 1 ----------------------
ISO/TR 17400:2003(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO 2003
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO 2003 — All rights reserved

---------------------- Page: 2 ----------------------
ISO/TR 17400:2003(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Normative references. 1
3 Terms and definitions. 1
4 General characteristics. 2
5 Testing and acceptance phases and goals for launch pad and integration sites. 5
5.1 Testing phases. 5
5.2 Acceptance phases. 5
5.3 Facility testing and acceptance. 5
5.4 Main system factory testing. 5
5.5 Main system field testing . 6
5.6 Launch pad and integration site end-to-end testing . 7
6 General characteristics for testing and acceptance . 7
6.1 General considerations. 7
6.2 Test and acceptance procedure . 7
6.3 Main system factory testing. 8
6.4 Main system field testing . 10
6.5 Acceptance of the main systems and facility after field test. 13
6.6 Launch pad and integration site end-to-end testing . 15
6.7 Launch pad or integration site acceptance after end-to-end testing . 18
7 Main system and facility modifications . 20
Bibliography . 23



© ISO 2003 — All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/TR 17400:2003(E)
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In exceptional circumstances, when a technical committee has collected data of a different kind from that
which is normally published as an International Standard (“state of the art”, for example), it may decide by a
simple majority vote of its participating members to publish a Technical Report. A Technical Report is entirely
informative in nature and does not have to be reviewed until the data it provides are considered to be no
longer valid or useful.
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.
ISO/TR 17400 was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee
SC 14, Space systems and operations.
iv © ISO 2003 — All rights reserved

---------------------- Page: 4 ----------------------
ISO/TR 17400:2003(E)
Introduction
This Technical Report establishes the general characteristics related to testing at launch pad and integration
sites for launch vehicle and spacecraft.
The purpose of this Technical Report is to establish the uniform practices for organizing the tests and
promoting verification of all parameters and characteristics of various launch complexes. It is necessary to
define the functions and to coordinate the activities of all the test participants, namely, the developers of
complexes and systems, the manufacturers of systems and equipment, the organizers of tests, the customer,
and others.
This Technical Report establishes recommended test activities and lists who will be responsible for the testing
at launch pad and integration sites for launch vehicle and spacecraft.

© ISO 2003 — All rights reserved v

---------------------- Page: 5 ----------------------
TECHNICAL REPORT ISO/TR 17400:2003(E)

Space systems — Space launch complexes, integration sites
and other facilities — General testing guidelines
1 Scope
This Technical Report is applicable to new projects and programs and to redesigned and upgraded launch
pad and integration sites. This Technical Report establishes the testing phases, goals, and general aspects
for launch space complexes and complexes for assembly and tests of a vehicle and spacecraft and the
associated equipment that, after successful testing, will be ready for launch vehicle processing and launch.
This Technical Report may be applicable to the creation of international launch pad and integration sites. At
creation of new launching space complexes and complexes for assembly and tests of a vehicle and
spacecraft (or at their modernization) within the framework of one country, the rules established by that
country may be applied.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 9000:2000, Quality management systems — Fundamentals and vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 9000:2000 and the following apply.
3.1
integration site
equipment and facility designed for launch vehicle storage, assembly, testing, preparation, maintenance,
servicing and preparation for transportation to the launch pad
3.2
international launch site
land, ground/airborne/marine facilities, equipment, utilities, and infrastructure, created with the cooperation of
several countries or the entities that belong to more than one country, necessary for the launch operations of
launch vehicle and payload and for in-flight operations during the launch phase
3.3
launch pad
equipment and facility designed to provide for the pre-launch and launch operations of spacecraft
3.4
launch pad site end-to-end testing
integration site end-to-end testing
launch pad or integration site development phase including the testing and evaluation of its overall readiness
to support a launch vehicle and a spacecraft
© ISO 2003 — All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/TR 17400:2003(E)
3.5
launch pad site support system
integration site support system
component launch pad or integration site, which enables the main system to operate
3.6
main system
launch pad or integration site or components primarily responsible for providing preparation and launch of a
launch vehicle or spacecraft
3.7
main system factory testing
launch pad or integration site development phase that includes the testing of a completely assembled and
checked out main system to determine its operational readiness to be shipped to the operational launch pad
or integration site for further testing or operation
3.8
main system field testing
launch pad or integration site development phase including the testing of an assembled, fully equipped, and
checked out (or factory tested) main system; the testing is conducted at the operational launch pad or
integration site to determine the system readiness for further testing or operation
3.9
test supervision
acceptance team
group of experts formed by the customer (organization, company, etc.) with the goal of coordinating work
during specific testing or acceptance phases
4 General characteristics
4.1 Testing of launch pad and integration sites and the main systems should be conducted in accordance
with the regulatory and design documentation specifications.
4.2 The test supervision team should coordinate use of the launch pad and integration site and the system
testing process and work management.
4.3 The launch pad and integration site developer should be the technical manager during the launch pad
and integration site and system testing.
4.4 Appointments to test supervision and acceptance team should be determined according to company or
agency recommendations before the beginning of a related testing phase.
Customer representatives should participate in team activities and sign respective documents in the event the
representatives are employees of the company or agency.
4.5 Customer representatives participating in the testing may work in a Joint Control and Acceptance Group
(JCAG). JCAG functions should be determined in agreements developed by the customer.
4.6 The system testing and acceptance team should have the authority to convene representatives of
design and unit manufacturing organizations. These representatives should be involved in:
 factory testing (the system manufacturing organization);
 field testing (the test organization);
 end-to-end testing (the team chairman).
2 © ISO 2003 — All rights reserved

---------------------- Page: 7 ----------------------
ISO/TR 17400:2003(E)
4.7 Depending on the results of the analysis of malfunctions or failures found in the course of testing, the
team should have the authority to:
 continue testing without repeating the operations completed earlier;
 repeat the testing starting with a specific phase;
 repeat the testing from the beginning.
4.8 If failures occurred in the testing or the system was subjected to changes, the test supervision team
should have the authority to increase the scope of testing as necessary.
4.9 The test supervision team should have the authority to suspend or terminate testing in the event of the
following situations:
 occurrence of an emergency posing a hazard to personnel safety;
 failures;
 systems revealed to be out of conformance with the design specifications or documentation.
In these cases, the team should report to the body that appointed the team indicating the reasons for such a
termination (suspension) and provide the necessary documentation.
4.10 Testing suspended in accordance with 4.9 should be restarted only upon permission from the body that
appointed the team.
4.11 Personnel permitted to perform testing should have the skills required to operate the main systems
within the range of their operational duties and should have passed tests on the knowledge of the equipment,
its operating instructions, safety regulations, and test programs and procedures.
4.12 Personnel working in hazardous conditions or with harmful substances should undergo a medical
examination prior to commencement of duties and annually thereafter.
4.13 Launch pad and integration site safety precautions should be taken before the beginning of testing or
experimental and research tasks.
4.14 The organization should ensure safety requirements are observed and appropriate safety documents
are maintained.
4.15 During system testing and acceptance, interested organizations may conduct experimental and
research projects under special programs.
4.16 In the event experimental and research activities require the use of mock-ups of launch vehicles,
spacecraft, or testing equipment, the special programs and reports should be cleared with the space complex
development organization.
4.17 Those main system items that fail during the tests should be replaced upon the team decision.
4.18 When any test fails, the cause of the failure should be established and eliminated.
4.19 Verify that the cause of the failure has been eliminated and continue testing:
 In case of a first-time (including independent elimination) failure (test team chairman), the tests continue
from the moment of the termination.
 In case of recurrence of the same failure (test team chairman), the amount of retest is determined by the
test team chairman depending on character of failure.
© ISO 2003 — All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/TR 17400:2003(E)
 In case of occurrence of the same failure in a third time (enterprise-developer of the main system together
with the enterprise-manufacturer and representative customer), the tests are completely repeated. The
differences among the developer of the main system, manufacturer, and representative customer are
resolved by the developer of the launch pad (integration site) and customer.
4.20 Malfunctions and failures identified in the course of testing should be eliminated by the organizations
responsible for the cause of these malfunctions and failures.
4.21 During test preparation, performance, and finalization and during the acceptance of the launch pad and
integration sites, main systems, and facilities, the organization in charge of the related work should process
reports under the procedure established in accordance with its respective national aerospace industry
practices.
4.22 The final decision on the results of the main system test and acceptance for operation should be made
by the launch pad and integration site developers.
4.23 During the testing of main systems, a test log should be maintained. The following should be entered
into the log:
 list of completed operations;
 test progress report;
 defects, malfunctions, failures, deviations or functioning irregularities of the main system found during
testing;
 methods for correcting the defects, malfunctions and failures;
 information on fine tuning or adjustments that may have been made;
 information about replaced components;
 main system nonconformity’s with the design documentation specifications;
 main system operating times on a daily or per-operation basis;
 decisions regarding test programs and/or procedure updates;
 suggestions for main system design and schemes improvement.
4.24 Implementation of the main system and the changes required for the elimination of failures should be
implemented on the basis of the design documents authorizing the changes. If necessary, change the design
documentation.
4.25 The procedure and timing for the submission of claims for faulty or incomplete main systems or for poor
quality should be in accordance with the regulations accepted in the respective national space industry.
4.26 Companies should finalize (approve and adopt) test programs and procedures within 30 calendar days
of receipt (or agreed specified date between related organizations).
4.27 In performing the facility and assembly work, the test organization and the chief engineering system and
facilities development organization should, on a regular basis, ensure job quality control, building code
compliance control, technical specification conformance control, and design document requirement
conformance control. Experts from the operations or test organizations and the customer should be involved
in the control.
4 © ISO 2003 — All rights reserved

---------------------- Page: 9 ----------------------
ISO/TR 17400:2003(E)
5 Testing and acceptance phases and goals for launch pad and integration sites
5.1 Testing phases
The following main system and launch pad and integration site testing phases should be adopted:
 main system factory testing;
 main system field testing;
 launch pad and integration site end-to-end testing.
If necessary or on demand of the customer, other extra phases of tests are possible also.
5.2 Acceptance phases
The following main system and launch pad and integration site acceptance phases should be adopted:
 main system acceptance after factory testing;
 main system and facility acceptance after field testing;
 launch pad and integration site acceptance after end-to-end testing.
5.3 Facility testing and acceptance
Facility testing and acceptance should be accomplished in conformance with the established respective
national aviation and space industry practice and the facility specifications.
5.4 Main system factory testing
Main system factory testing should be conducted to verify the main system conformance to the design
specifications and documentation, the operational readiness requirements, the main system acceptance by
the customer’s representatives, and system readiness for shipping to the assembly launch pad or integration
site for further testing. The goals of the main system factory testing are:
 verification of main system completeness;
 verification of main system operational readiness and functioning interfaces and conformance to the
design specifications and documentation;
 verification of the correct interaction and functioning of the item;
 verification of system compatibility and operation with the components of the launch vehicles, spacecraft,
and main systems of the launch pad, as necessary;
 verification of the accuracy of the adopted design approaches;
 verification of the feasibility of the assembly process;
 verification of the serviceability of the protective devices and electrical interlocks in emergency modes;
 verification of the main system operational readiness and strength at the extreme parameter values
indicated in the design specifications;
 verification of the adequacy and completeness of operations documentation;
© ISO 2003 — All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/TR 17400:2003(E)
 verification of the adequacy and applicability of the tools, devices, and instruments required for the main
system operation;
 verification of the adequacy of the operational safety provisions;
 verification of maintenance and repair accessibility;
 verification of the quality of manufacturing, assembly, and checkout;
 dating the scope of the main system field testing;
 verification of transportability;
 evaluation of the main system’s reliability;
 verification of the availability of component reliability documents (for experimental items only);
 verification of test metrological support.
5.5 Main system field testing
The main system field testing should be conducted for the purpose of verifying main system operational
readiness and determining system readiness for end-to-end testing (in the event the main systems are
designated to undergo the end-to-end testing) or other subsequent tests (if necessary). The main system field
testing goals are:
 verification of main system completeness;
 verification of main system assembly and checkout quality;
 verification of main system operational readiness and functioning interfaces and conformance to the
design specifications and documentation;
 verification of the main system compatibility and operation with the launch pad and integration site’s other
main systems and facilities, as necessary;
 verification of the adequacy of the main system operation safety instructions indicated in the operations
documentation;
 verification of maintenance and repair accessibility;
 verification of the human habitability conditions (lighting, ventilation, heating, harmful gas content, etc.);
 verification of the adequacy of the operations personnel;
 verification of the efficiency of modifications made based on the factory test results;
 verification of the sufficiency and serviceability of the tools, devices, and instruments required for main
system operation;
 evaluation of the main system’s reliability;
 verification of test metrological support.
6 © ISO 2003 — All rights reserved

---------------------- Page: 11 ----------------------
ISO/TR 17400:2003(E)
5.6 Launch pad and integration site end-to-end testing
The end-to-end testing should be conducted for the purpose of verifying the launch pad and integration site
operational readiness and determining the launch pad and integration site readiness for launch or other
subsequent tests (if necessary). The end-to-end launch pad and integration site testing goals are:
 verification of the launch pad and integration site operational readiness and its conformance to the design
specifications and documentation during standard operations involving launch vehicles and spacecraft
under conditions closely approximating those conditions of actual operations but in which testing does not
require the actual launching of a launch vehicle;
 verification that the launch pad and integration site is complete;
 verification and update of the operational sequences of the main items during launch vehicle preparation,
launch, aborted launch, and preparation for a post-abort launch;
 verification and update of the time requirements for the main system operational procedures;
 verification of the accuracy of the adopted design approaches;
 verification of the compatibility of the main systems in the process sequences as well as with launch
vehicles and spacecraft;
 verification and update of the requirements and skill level of the operations personnel;
 verification and update of the completeness and adequacy of the operations documentation;
 verification of the adequacy of the safety maintenance of the launch pad and integration site and main
systems, including emergency situations;
 evaluation of the supply of spare parts and tools;
 update the procedure for launch pad and integration site maintenance and post-launch refurbishment;
 verification of the adequacy of the measures taken to eliminate failures and malfunctions based on the
results of previous and end-to-end testing;
 evaluation of launch pad and integration site reliability;
 verification of metrological support.
6 General characteristics for testing and acceptance
6.1 General considerations
Nature of the testing toward acceptance of the launch pad and integration launch pad and integration site and
the duties of each participating organizations are described generally in this section. Exact definition of the
acceptance condition, testing, and the duties of the participating organizations should be identified in the
individual contract document.
6.2 Test and acceptance procedure
The following procedure should be adopted for test and acceptance:
a) facility and support system test and acceptance should be conducted in accordance with the national
aviation and space industry practice;
b) factory main system test;
© ISO 2003 — All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/TR 17400:2003(E)
c) main system acceptance after factory test;
d) main system field testing;
e) main system and facility acceptance after field test;
f) end-to-end testing;
g) launch pad and integration site acceptance for operation as part of the space complex.
6.3 Main system factory testing
6.3.1 The factory test team should be formed by the manufacturing organization at least 30 calendar days
prior to the beginning of testing (or agreed specified date between related organizations).
6.3.2 During the factory testing involving individual items of the launch vehicle, spacecraft, and other main
systems, the factory test team should include representatives of the organizations in charge of the launch
vehicle, spacecraft, and other main system development and grant the representatives the status of team
members.
6.3.3 Ten working days before the test (or agreed specified date between the related organizations), the
manufacturing organization should submit the following documentation to the team:
a) design specifications;
b) complete set of the design documentation updated as of the date the testing begins, including:
1) test program and procedures;
2) measurement procedures, as necessary.
c) documents for the test equipment (benches, devices, instruments, etc.) that verify readiness for testing;
d) test schedule;
e) list of deviations from the design documentation that occurred during the manufacturing of the main
system at the manufacturing organization;
f) records and technical reports on the test results of specific items;
g) report on the electric equipment insulation resistance included in the main system or connected thereto
and the electric equipment of the cable network connected thereto;
h) acceptance records for the assembly of grounding and static electricity protection devices;
i) list of design identified modifications during the testing process as well as the set of documents
authorizing these modifications;
j) reports on the testing or work completed before the beginning of the factory testing;
k) submission note;
l) test log.
6.3.4 During the factory testing, supervision team, and also the organizations participating in tests (the
launch pad (integration site) developer, main system and unit developer and manufacturer, and customer)
should execute the following activities:
 submission of the documentation required for main system 2 months prior to the beginning of the testing
(or specified date agreed between related organizations);
8 © ISO 2003 — All rights reserved

---------------------- Page: 13 ----------------------
ISO/TR 17400:2003(E)
 test organization;
 assurance and control of the completeness and quality of the test in accordance with the test program
and procedures;
 technical supervision of the testing and involvement of the organization representatives in the testing;
 elimination of faults and failures identified in the course of testing and adaptation of aggregates under the
documentation authorizing this adaptation;
 development and approval of the documentation authorizing the changes resulting from the test;
 correction of design documentation as necessary;
 analysis and evaluation of test results;
 main system maintenance in accordance with the operations documentation;
 provisioning of requ
...