1、 Reference number ISO 26870:2009(E) ISO 2009INTERNATIONAL STANDARD ISO 26870 First edition 2009-12-01 Space systems Launch pad and integration site operational documents Systmes spatiaux Documents oprationnels pour aire de lancement et site dintgration ISO 26870:2009(E) PDF disclaimer This PDF file
2、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 computer performing the editing. In downloading this file, parties accept therein the re
3、sponsibility 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 this PDF file can be found in the General Info relative to the file; the PDF-crea
4、tion 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. COPYRIGHT PROTECTED DOCUMENT ISO 20
5、09 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 ISOs member body in the cou
6、ntry 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 2009 All rights reservedISO 26870:2009(E) ISO 2009 All rights reserved iiiContents Page Foreword iv Intro
7、duction.v 1 Scope1 2 Normative references1 3 Terms and definitions .2 4 General requirements .4 4.1 Operational-document applicability 4 4.2 Overall content requirements.5 4.3 Publishing medium .5 4.4 Approval and delivery.5 4.5 Illustrations 6 4.6 Attachments.6 4.7 References .6 5 Specific content
8、requirements.6 5.1 System documentation list (SDL) 6 5.2 Operation and maintenance (O to provide a procedure for applying these documents; and to provide organizations and corporations that develop the operational documents with the common rules of their development. INTERNATIONAL STANDARD ISO 26870
9、:2009(E) ISO 2009 All rights reserved 1Space systems Launch pad and integration site operational documents 1 Scope This International Standard establishes requirements for the nomenclature, structure and contents of operational documents used at a launch pad or integration site. When there is intern
10、ational participation, partnership or cooperation in the design, development, installation, test, activation or operation of a launch pad or integration site, this International Standard applies to the development of the operational documents required for the following circumstances: installation, t
11、esting, activation or operation within the territory of one country of a launch pad or integration site manufactured in another country; joint installation, testing, activation or operation when the equipment designed and manufactured in one country is part of the launch pad or integration site desi
12、gned by another country; training of the launch pad or integration site personnel of one country by the experts from another country. The development and use of the operational documents described in this International Standard are applicable to the following international launch pad or integration
13、site operations: a) preparation of integration site equipment to receive space vehicles and spacecraft; b) preparation of launch pad equipment and the space complex for the launch of space vehicles; c) space vehicle launch; d) post-launch maintenance of the integration site and launch pad; e) period
14、ic maintenance of the integration site and launch pad. 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 (includ
15、ing any amendments) applies. ISO 23041, Space systems Unmanned spacecraft operational procedures Documentation ISO/TR 17400:2003, Space systems Space launch complexes, integration sites and other facilities General testing guidelines ISO 26870:2009(E) 2 ISO 2009 All rights reserved3 Terms and defini
16、tions For the purposes of this document, the following terms and definitions apply. 3.1 assembly, repair and regulation instruction assembly, repair and regulation procedure AI document containing detailed descriptions of the complex, system operations or tests required for assembly, repair and regu
17、lation 3.2 complex launch pad or integration site 3.3 customer firm that awards the design specification or work task and finances the work 3.4 data log book DLB collection of documents that define the initial and current technical condition of a facility, system or item of equipment 3.5 hazard anal
18、ysis HA document that identifies the hazards associated with the operation of a system or component, the likelihood and consequences of their occurrence, and the procedures for preventing their occurrence and mitigating their consequences 3.6 integration site equipment and facility designed for laun
19、ch vehicle storage, assembly, testing, preparation, maintenance, servicing and preparation for transportation to the launch pad ISO/TR 17400:2003, definition 3.1 3.7 launch pad equipment and facility designed to provide for the pre-launch and launch operations of spacecraft ISO/TR 17400:2003, defini
20、tion 3.3 3.8 main system launch pad or integration site or components primarily responsible for providing preparation and launch of a launch vehicle or spacecraft ISO/TR 17400:2003, definition 3.6 3.9 main system field testing launch pad or integration site development phase including the testing of
21、 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 ISO/TR 17400:2003, definition 3.8 ISO 26870:2009(E) ISO 2009 All rights reserv
22、ed 33.10 maintenance instruction maintenance procedure MI document containing detailed descriptions of the maintenance procedures that are required for a complex or main system 3.11 operation and maintenance manual O b) launch pad and integration site operation; c) recording the results of launch pa
23、d and integration site operation; d) launch pad and integration site maintenance; e) logistics. Operational documents that are generally developed are included in Table 1, along with their applications. Table 1 Types of operational documents Application Code Name Complex Main system SDL System docum
24、entation list aaO&M Operation and maintenance manual aaOI Operational instruction or procedure aaMI Maintenance instruction or procedure baAI Assembly, repair and regulation instruction or procedure bbDLB Data log book aaTAIR Test, assembly and inspection record file aaHA Hazard analysis bbSPL Spare
25、-parts list caSPUI Spare-part use instruction or procedure bbDWG Drawing daaaThe document is mandatory. bThe document is optional and is developed, when required, by the customer. cThe document is not required. dDrawings can be included in O&M, OI, MI or AI. ISO 26870:2009(E) ISO 2009 All rights res
26、erved 5Depending on the type of facility, system or item of equipment, the amount of information, operational conditions or national practice, the operational documents and applications listed in Table 1 may be changed as follows: to add other operational documents, to waive operational documents de
27、emed unnecessary, to combine several operational documents into one document (e.g. OI, AI and MI may be combined as a single type of instruction or procedure), to divide an operational document into several separate documents, NOTE The titles of the resulting separate documents can reflect their con
28、tents. to waive individual sections from an operational document, or to add indispensable sections. The SDL and the contents of operational documents for all complexes and main systems shall be determined by the corresponding developers. 4.2 Overall content requirements Operational documents shall i
29、nclude the exact parameters, characteristics and other properties included in the corresponding design documents. Parameters, characteristics or properties missing from design documents shall not be included in corresponding operational documents. Operational documents shall be clear and comprehensi
30、ve, with no dependence on other documents, except as noted in 4.7. The words “ATTENTION” or “FORBIDDEN” shall precede the description of security measures. Spelling and appearance in operational documents shall comply with ISO 23041, except in relation to illustrations. The operational document orig
31、inal shall be stored by the developer of the subject complex or main system. Each operational document shall include a list of changes or revisions in accordance with Clause 6. 4.3 Publishing medium Operational documents shall be published and distributed either on paper or electronically, depending
32、 on the intended use of the documents, their means of control, the skill of the personnel involved and the requirements of the customer. The paper on which operational documents are published shall not exceed (210 297) mm, except as noted in 4.5. The paper and stitching chosen shall have a long term
33、 of service. The customer shall determine the means of electronic publishing and distribution. 4.4 Approval and delivery Operational documents shall be approved in accordance with national practice and shall be delivered to the operational site before field testing has begun. If the subject operatio
34、nal document contains references to other operational documents (see 4.7), those referenced operational documents shall also be delivered to the operational site. ISO 26870:2009(E) 6 ISO 2009 All rights reserved4.5 Illustrations Operational documents shall include illustrations of all components men
35、tioned in the technical description. Each component shall be identified by a number and called out in a legend in the illustration. The illustrations may be placed in the text of a document or in attachments. A sheet dimension of (297 210) mm, of (297 420) mm or of (297 630) mm shall be used. On she
36、ets of width 420 mm or 630 mm, illustrations shall be placed toward the outside margin. 4.6 Attachments Information required for launch or launch preparations shall be included in the main text of the operational document, not in an attachment. Supplemental or minor information may be included in at
37、tachments and may be bound together with or separately from the main text of the printed operational document. Attachments may be included in the electronic files of operational documents or may comprise separate files. EXAMPLE Suitable material for attachments include illustrations, information sec
38、urity requirements, requirements for spare parts and instructions for specialists. 4.7 References If it is necessary to refer to an operational document of another main system, the reference shall identify the main system, the code of the operational document (see Table 1), the document title, the d
39、ocument number, and any other specific information that helps identify the other document. If the operation process does not accommodate a pause or stopping point in the process, then references to operational documents of other main systems are prohibited. If it is necessary to refer to a structura
40、l element of the main system, the reference shall identify the design document for the main-system structural element. If the components and materials used in the main system are required to conform to an established standard, the reference shall fully identify that standard. 5 Specific content requ
41、irements 5.1 System documentation list (SDL) The operational documents developed for the facility and system shall be indicated in a facility SDL. All operational documents developed for the main system and SDLs for the components are indicated in a main system SDL. The SDL shall reflect the number
42、and title of each operational document exactly as they appear in the original operational document. The location of the operational document shall be indicated explicitly. The location may change depending on the activity being performed (e.g. one site at transportation and the other location is where the main system is operated).
