ISO 26870:2022 Space Systems — Launch Pad and Integration Site Operational Documents

Standardized Documentation Framework for Multi-Nation Space Launch Complex Operations

1. Introduction and Scope

ISO 26870:2022 (second edition, replacing ISO 26870:2009) establishes requirements for the nomenclature, structure, and contents of operational documents used at a launch pad or integration site. Developed by ISO/TC 20/SC 14, this standard is specifically designed for scenarios where multiple nations cooperate in the design, development, installation, testing, activation, or operation of space launch facilities.

When equipment manufactured in one country is installed in another country’s launch facility, language barriers, differing operational cultures, and incompatible documentation practices create significant safety and efficiency risks. ISO 26870 provides a neutral, internationally agreed framework for operational documentation that bridges these gaps.

The standard applies to five categories of operations: preparation of integration site equipment to receive space vehicles, preparation of launch pad equipment for launch, the launch itself, post-launch maintenance, and periodic maintenance of both the integration site and launch pad.

2. Operational Document Types and Structure

2.1 Document Taxonomy

ISO 26870 defines twelve types of operational documents, each with a specific code, name, and application scope. These range from mandatory documents required for every system to optional documents developed only when needed.

Code Document Name Mandatory? Application
SDL System Documentation List Yes Complex + Main System
O&M Operation and Maintenance Manual Yes Complex + Main System
OM Operational Manual Yes Complex + Main System
MM Maintenance Manual Optional Main System
AM Assembly, Repair and Regulation Manual Optional Main System
DLB Data Log Book Yes Complex + Main System
TAIR Test, Assembly and Inspection Record Yes Complex + Main System
HA Hazard Analysis Optional Main System
SPL Spare-Parts List No Complex (not required)
SPUI Spare-Part Use Manual Optional Main System
DWG Drawings Yes Complex + Main System

2.2 Data Log Book Structure

The DLB is the most comprehensive document defined in the standard, containing 20 mandatory sections that track the entire lifecycle of the facility or system: general directions, technical characteristics, hazards, delivered component lists, customer and developer opinions, technical resource and guarantee information, conservation records, certification of acceptance, transfer records, operation duration, maintenance history, modifications, storage, problem reports, inspections, repairs, salvage, and approval — covering every phase from manufacture to decommissioning.

The TAIR (Test, Assembly and Inspection Record) file serves as an extension of the DLB for systems with large volumes of documentation, providing a mechanism to manage test operations, maintenance, modifications, problem reports, and inspections without overloading the primary log book.

3. Specific Content Requirements

3.1 Operational Manual (OM)

The OM is the most operationally critical document, prepared jointly by the system developers and the operating organization. It must include detailed step-by-step procedures for: operation preparation (safety rules, power system connection, workstation configuration, measurement means), normal operation (initial condition, operation modes, procedures, monitoring, mode sequence, work stoppage), and emergency operations (fire, explosion, breakdown, failure, emergency evacuation). The standard includes a critical rule: within the OM, references to other documents are prohibited — every required procedure must be fully self-contained.

3.2 Material Review Board Requirements

New in the 2022 edition, Clause 5.2 requires the creation of a Material Review Board (MRB) or equivalent construct as a standard anomaly handling mechanism. The MRB addresses off-nominal situations that could introduce unacceptable risk, negotiating a path forward between involved programs and contractors. This clause reflects lessons learned from decades of space launch operations where unplanned anomalies require rapid, documented decision-making.

4. Engineering Design Insights

For launch facility engineers and operators, ISO 26870 provides a proven framework for documentation that directly impacts operational safety and efficiency. Unlike generic technical documentation standards, ISO 26870 is tailored specifically for the high-consequence, multi-organization environment of space launch operations where miscommunication can result in catastrophic loss of vehicle and life. Key practical considerations include:

International cooperation provisions: The standard was written explicitly for scenarios involving multiple countries — equipment manufactured in one country, installed in another, and operated by personnel from yet another nation. The document structure assumes that developers, operators, and customers may be from different organizations with different documentation traditions. This international perspective is reflected in the emphasis on clear, unambiguous illustrations, standardized terminology, and the prohibition on references within operational manuals to ensure self-contained usability across language barriers.

Change management discipline: The standard mandates that changes to operational documents can only be made through an approved authorizing document, signed by the initiator, the system developer, and (if required) the customer. All changes must be recorded in a list with copy numbers, authorizing document designations, effective dates, and the identity of the official executing the change.

Paper vs. electronic: The standard pragmatically supports both paper and electronic publishing formats, with specific format requirements for paper documents (210×297 mm maximum, long-service-life paper and stitching). This dual approach recognizes that launch site operations often require rugged, portable documents that may not be practical on electronic devices. The standard also permits electronic distribution with digital signatures for the original operational document, accommodating modern workflows while maintaining document integrity and traceability.

A critical safety requirement: the words “ATTENTION” or “FORBIDDEN” must precede the description of security measures in all operational documents. These standardized warning markers ensure that personnel operating in high-stress, time-critical launch environments can immediately identify critical safety instructions regardless of their native language.

5. FAQs

Q1: What is the difference between an O&M manual and an OM?
The O&M Manual combines operational and maintenance information for familiarization purposes, while the OM is a focused step-by-step procedure document for actual launch preparation and launch operations, containing only directly actionable instructions.
Q2: Can operational documents be combined?
Yes — the standard explicitly allows combining OM, AM, and MM into a single manual, or dividing a document into separate parts, depending on operational needs.
Q3: Who prepares the operational documents?
The system developer is primarily responsible, but the OM, MM, AM, and HA must be developed jointly with the operating organization to ensure practical usability.
Q4: What changed between the 2009 and 2022 editions?
The 2022 edition updated terms and definitions, added Clause 5.2 on Material Review Board requirements, specified Bibliography information in Table 1, and removed the term “preventive maintenance” from the definitions section.

Leave a Reply

Your email address will not be published. Required fields are marked *