1、 Reference number ISO/TR 17400:2003(E) ISO 2003TECHNICAL REPORT ISO/TR 17400 First edition 2003-02-15 Space systems Space launch complexes, integration sites and other facilities General testing guidelines Systmes spatiaux Complexes de lancement spacial, sites dintgration et autres installations Lig
2、nes directrices pour les essaisISO/TR 17400:2003(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes 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 compute
3、r performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes 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
4、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 Ce
5、ntral 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
6、 at the address below or ISOs 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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2003 All rights reservedISO/TR 17400:2003(E) ISO 2003
7、 All rights reserved iiiContents 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 test
8、ing 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 test
9、ing. 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
10、 . 23 ISO/TR 17400:2003(E) iv ISO 2003 All rights reservedForeword 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 committe
11、es. 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 Inte
12、rnational 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 S
13、tandards 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 kin
14、d 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
15、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 Technic
16、al Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee SC 14, Space systems and operations. ISO/TR 17400:2003(E) ISO 2003 All rights reserved vIntroduction This Technical Report establishes the general characteristics related to testing at launch pad and integration sites for launch vehic
17、le 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 tes
18、t 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 integratio
19、n sites for launch vehicle and spacecraft. TECHNICAL REPORT ISO/TR 17400:2003(E) ISO 2003 All rights reserved 1Space 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 redes
20、igned 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
21、 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 f
22、ramework 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 ref
23、erenced 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
24、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 co
25、untries 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 la
26、unch 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/TR 17400:2003(E) 2 ISO 2003 All rights reserved3.5 launch pad site supp
27、ort 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 fact
28、ory 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 t
29、esting 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 operatio
30、n 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 conduc
31、ted 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 mana
32、ger 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 activit
33、ies 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
34、.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 testi
35、ng (the team chairman). ISO/TR 17400:2003(E) ISO 2003 All rights reserved 34.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 t
36、esting 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 t
37、he 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 bo
38、dy 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 sho
39、uld 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 wi
40、th 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 r
41、equirements 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 l
42、aunch 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
43、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
44、 failure (test team chairman), the amount of retest is determined by the test team chairman depending on character of failure. ISO/TR 17400:2003(E) 4 ISO 2003 All rights reserved In case of occurrence of the same failure in a third time (enterprise-developer of the main system together with the ente
45、rprise-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 ident
46、ified 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 orga
47、nization 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 inte
48、gration 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 duri
49、ng 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 nonconformitys 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 requir
