This document provides requirements and recommendation for space-based systems that, using satellite radionavigation services, provide high accuracy positioning of rovers. It is particularly intended for rovers whose operation requires meeting specific safety requirements, including in situations of low visibility. This document also provides methods to verify the system requirements, as well as complementary information on particular applications (Annex A), mobile mapping systems (Annex B) and augmented positioning (Annexes C and D).

  • Technical specification
    21 pages
    English language
    sale 15% off
  • Draft
    21 pages
    English language
    sale 15% off

This document addresses the design process of a collocation and the basic contents of collocation design process which include considerations, initial collocation strategy design, simulation evaluation of collocation strategy, optimal collocation strategy selection and collocation agreement. This document gives guidelines for multi-geo spacecraft collocation, and it applies in particular to multi-geo constellation.

  • Technical report
    21 pages
    English language
    sale 15% off
  • Draft
    21 pages
    English language
    sale 15% off

This document provides the baseline standard on the subject of testing at the system, subsystem and unit levels for applicable unmanned spacecraft programmes. It also provides the requirements for documentation associated with testing activities. This document contains provisions for qualification and acceptance testing, or proto-flight testing (PFT). It assumes that hardware development is complete.

  • Standard
    34 pages
    English language
    sale 15% off
  • Draft
    34 pages
    English language
    sale 15% off

The purpose of this document is to define the Space Link Extension (SLE) Return Operational Control Fields (ROCF) service in conformance with the SLE Reference Model (reference [1]). The ROCF service is an SLE transfer service that delivers to a mission user all operational control fields from one master channel or one virtual channel. This document defines, in an abstract manner, the ROCF service in terms of: the operations necessary to provide the service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to acquire telemetry frames from signals received from a spacecraft; the methods or technologies required to provide a suitable environment for communications; or the management activities required to schedule, configure, and control the ROCF service. NOTE  –   Reference [1] defines the Return Master Channel Operational Control Field (Rtn MC-OCF) service and the Return Virtual Channel Operational Control Field (Rtn VC-OCF) service as two distinct services. Subsequent study has indicated that it is preferable to define one service that provides the functionality of both. The ROCF service defined here does just that. It is anticipated that a future issue of reference [1] will take the same approach, deleting the Rtn MC-OCF and Rtn VC-OCF services and replacing them with the Rtn OCF service.

  • Standard
    144 pages
    English language
    sale 15% off

This document specifies two standard message formats for use in transferring spacecraft attitude information between space agencies: the Attitude Parameter Message (APM) and the Attitude Ephemeris Message (AEM). Such exchanges are used for: - preflight planning for tracking or attitude estimation support; - scheduling attitude and data processing support; - carrying out attitude operations; - performing attitude comparisons; - carrying out attitude propagations and/or sensor predictions; - testing to initialize sub-system simulators (communications, power, etc.). This document includes sets of requirements and criteria that the message formats have been designed to meet. For exchanges where these requirements do not capture the needs of the participating agencies, another mechanism may be selected.

  • Standard
    52 pages
    English language
    sale 15% off
  • Draft
    52 pages
    English language
    sale 15% off

The purpose of this document is to define the Space Link Extension (SLE) Return Channel Frames (RCF) service in conformance with the SLE Reference Model (reference [1]). The RCF service is an SLE transfer service that delivers to a mission user all telemetry frames from one master channel or one virtual channel. This document defines, in an abstract manner, the RCF service in terms of: the operations necessary to provide the service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to acquire telemetry frames from signals received from a spacecraft; the methods or technologies required to provide a suitable environment for communications; or the management activities required to schedule, configure, and control the RCF service. NOTE  –   Reference [1] defines the Return Master Channel Frames (Rtn MC Frames) service and the Return Virtual Channel Frames (Rtn VC Frames) service as two distinct services. Subsequent study has indicated that it is preferable to define one service that provides the functionality of both. The RCF service defined here does just that. It is anticipated that a future issue of reference [1] will take the same approach, deleting the Rtn MC Frames and Rtn VC Frames services and replacing them with the RCF service. Â

  • Standard
    141 pages
    English language
    sale 15% off

The purpose of this document is to provide a common reference and framework of standards for digital motion video and imagery, and to provide recommendations for utilization of international standards for sharing or distributing motion video and imagery between spacecraft elements and ground systems. The scope of this document includes traditional real-time streaming video and television, including human and robotic spacecraft-to-spacecraft and spacecraft-to-ground systems, as well as video recorded and distributed later, either as a real-time stream or as a file transfer. In this context, real-time streaming includes all modes where video is sent from a spacecraft in a continuous stream and is intended for immediate use when received, regardless of the latency of the transmission path. Other specialized motion imagery applications, such as high-speed scientific motion imagery and multi-spectral motion imagery, are not addressed in this document. However, if a specialized imagery camera system has a requirement to interface to spacecraft systems in a video mode, it would be required to match these interfaces. Ground-systems-to-ground-systems video distribution is obviously a key component of the entire video system. However, this is not the primary focus of this document. Currently, there are significant differences in the ways mission video products are exchanged between the various space agencies on the ground. This is the result of differences in network topologies between space agencies, and agreements for video sharing. Those differences preclude there being a standard methodology for delivering video imagery between agencies. Prior to the commencement of video transmission between space agencies, system design reviews and performance testing should be done between the ground systems in use to assure operability when video imagery comes from spacecraft.

  • Standard
    34 pages
    English language
    sale 15% off
  • Draft
    34 pages
    English language
    sale 15% off

This document defines the Communications Link Transmission Unit (CLTU) service in conformance with the transfer services specified in reference [1], Cross Support Reference Model—Part 1: SLE Services. The Forward CLTU service is a Space Link Extension (SLE) transfer service that enables a mission to send Communications Link Transmission Units (CLTUs) to a spacecraft. This document defines, in an abstract manner, the Forward CLTU service in terms of: the operations necessary to provide the transfer service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to radiate data to a spacecraft and to acquire telemetry frames from the signals received from that spacecraft for extraction of the Operational Control Field; the methods or technologies required for communications; or the management activities necessary to schedule, configure, and control the Forward CLTU service.

  • Standard
    143 pages
    English language
    sale 15% off
  • Draft
    143 pages
    English language
    sale 15% off

This document defines the Forward Space Packet (FSP) service in conformance with the transfer services specified in reference [1], Cross Support Reference Model―Part 1: SLE Services. The FSP service is a Space Link Extension (SLE) transfer service that enables a mission to send Space Packets to a spacecraft in sequence-controlled or expedited mode. This document defines, in an abstract manner, the FSP service in terms of: the operations necessary to provide the transfer service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to radiate Space Packets to a spacecraft and to acquire telemetry frames from the signals received from that spacecraft for extraction of the Operational Control Field; the methods or technologies required for communications; or the management activities necessary to schedule, configure, and control the FSP service. NOTE  –   While the FSP service as described in reference [1] is conceived to handle a variety of packet data structures, this version of the FSP Recommended Standard is restricted to the handling of Space Packets as defined in reference [6]. This version of the FSP Recommended Standard is specific to the transfer of Space Packets to be transmitted via the Telecommand protocol stack as defined in references [3], [4], and [5]. The Cross Support Reference Model (reference [1]) specifies that the FSP service may also be used in conjunction with the Advanced Orbiting System protocol stack, but that mode of operation is outside the scope of this version of the Recommended Standard. The FSP service is provided in the online delivery mode, as defined in reference [1]. The offline delivery mode is the subject of further study.

  • Standard
    190 pages
    English language
    sale 15% off
  • Draft
    190 pages
    English language
    sale 15% off

This document defines, in an abstract manner, the RAF service in terms of: the operations necessary to provide the service; the parameter data associated with each operation; the behaviors that result from the invocation of each operation; and the relationship between, and the valid sequence of, the operations and resulting behaviors. It does not specify: individual implementations or products; the implementation of entities or interfaces within real systems; the methods or technologies required to acquire telemetry frames from signals received from a spacecraft; the methods or technologies required to provide a suitable environment for communications; or the management activities required to schedule, configure, and control the RAF service.

  • Standard
    136 pages
    English language
    sale 15% off
  • Draft
    136 pages
    English language
    sale 15% off

This document defines the Application Program Interface in terms of: the components that provide the services of the API; the functionality provided by each of the components; the interfaces provided by each of the components; and the externally visible behavior associated with the interfaces exported by the components. It does not specify: individual implementations or products; the internal design of the components; and the technology used for communications. This document defines those aspects of the Application Program Interface, which are common for all SLE service types or for a subset of the SLE service types, e.g., all return link services or all forward link services. It also defines a framework for specification of service type-specific elements of the API. Service-specific aspects of the API are defined by supplemental Recommended Practice documents for SLE return link services (references [10], [11], and [12]) and SLE forward link services (references [13] and [14]). This document for the Application Program Interface responds to the requirements imposed on such an API by the CCSDS SLE transfer service Recommended Standards that were available when this document was released.

  • Standard
    365 pages
    English language
    sale 15% off
  • Draft
    365 pages
    English language
    sale 15% off

This document specifies a common process for selecting and implementing meteoroid and space debris environment models used in the impact flux assessment for design and operation of spacecraft and other purposes. This document provides guidelines and requirements for the process.

  • Standard
    14 pages
    English language
    sale 15% off
  • Draft
    14 pages
    English language
    sale 15% off

The document considers peculiarities of the space environment impact on a special kind of materials: nanostructured materials (i.e. materials with structured objects which size in at least one dimension lies within 1Â nm to 100Â nm) and specifies the methods of mathematical simulation of such processes. It emphasizes the necessity of applying multiscale simulation approach and does not include any special details concerning concrete materials, elements of spacecraft construction and equipment, etc. This document provides the general description of the methodology of applying computer simulation methods which relate to different space and time scales to modelling processes occurring in nanostructured materials under the space environment impact. The document can be applied as a reference document in spacecraft designing, forecasting the spacecraft lifetime, conducting ground-based tests, and analysing changes of material properties during operation.

  • Technical specification
    29 pages
    English language
    sale 15% off
  • Draft
    29 pages
    English language
    sale 15% off

This document establishes the baseline requirements for the design, fabrication and testing of space flight pressure components. It also establishes the requirements for the assembly, installation, test, inspection, operation and maintenance of the pressure systems in spacecraft and launch vehicles. These requirements, when implemented on a particular space system, ensure a high level of confidence in achieving safe and reliable operation. This document applies to all pressure components other than pressure vessels and pressurized structures in a pressure system. It covers lines, fittings, valves, bellows, hoses and other appropriate components that are integrated to form a pressure system. The requirements for pressure vessels and pressurized structures are set forth in ISOÂ 14623. This document does not apply to engine components.

  • Standard
    27 pages
    English language
    sale 15% off
  • Draft
    27 pages
    English language
    sale 15% off

This document contains information on the design and operational practices for launch vehicle orbital stages for mitigating space debris. This document provides information to engineers on the requirements and recommendations in the space debris mitigation standards to reduce the growth of space debris by ensuring that launch vehicle orbital stages are designed, operated, and disposed of in a manner that prevents them from generating debris throughout their orbital lifetime.

  • Technical report
    31 pages
    English language
    sale 15% off
  • Draft
    31 pages
    English language
    sale 15% off

This document establishes the requirements for simulation of the space control system, including the objective, architecture and procedure, etc. This document is applicable to four phases of control system development, including conceptual design, detailed design, prototype and integrated system. The control system referred to in this document is the flight control system for guidance, navigation and control (GNC) of space systems which include launch vehicle, satellite and spaceship, etc. This document establishes a minimum set of requirements for simulation of the flight control system, and provides guidance to engineers on what to simulate in each phase of control system development. The requirements are generic in nature because of their broad applicability to all types of simulations. Implementation details of the requirements are addressed in project-specific standards, requirements, and handbooks, etc.

  • Standard
    22 pages
    English language
    sale 15% off
  • Draft
    22 pages
    English language
    sale 15% off

This document defines detailed space debris mitigation requirements and recommendations for the design and operation of launch vehicle orbital stages in Earth orbit. The requirements defined in this document are applicable for: — avoiding the release of space debris; — disposing of a launch vehicle orbital stage after the end of its mission so as to avoid a break-up in orbit; — disposing of a launch vehicle orbital stage after the end of its mission so as to minimize interference with the protected regions; — safely re-entering a launch vehicle orbital stage.

  • Standard
    8 pages
    English language
    sale 15% off
  • Draft
    8 pages
    English language
    sale 15% off
  • Standard
    3 pages
    English language
    sale 15% off
  • Draft
    3 pages
    English language
    sale 15% off

This document contains information on the design and operational practices for launch vehicle orbital stages for mitigating space debris. This document provides information to engineers on what are required or recommended in the family of space debris mitigation standards to reduce the growth of space debris by ensuring that spacecraft is designed, operated, and disposed of in a manner that prevents them from generating debris throughout their orbital lifetime.

  • Technical report
    56 pages
    English language
    sale 15% off
  • Draft
    56 pages
    English language
    sale 15% off

This document provides detailed information on the various methods of assessing the health status of lithium-ion space batteries in flight and makes recommendations to battery suppliers, spacecraft manufacturers and operators to ease this assessment.

  • Technical report
    54 pages
    English language
    sale 15% off
  • Draft
    54 pages
    English language
    sale 15% off

This document specifies criteria and requirements for the use of explosive systems and explosive devices commonly used on spacecraft and other space products, including launch vehicles and space vehicle systems. It addresses the aspects of design, analysis, verification, manufacturing, operations and safety. To the greatest extent possible, requirements from past and existing standards have been analyzed, selected and tailored to be incorporated herein. In addition, the requirements herein include those generated as a result of lessons learned from launch and space vehicle programs. NOTE Specific requirements for man-rating are not addressed.

  • Standard
    77 pages
    English language
    sale 15% off
  • Draft
    77 pages
    English language
    sale 15% off

This standard defines the requirements and recommendations for the design and test of RF components and equipment to achieve acceptable performance with respect to multipaction-free operation in service in space. The standard includes:
•   verification planning requirements,
•   definition of a route to conform to the requirements,
•   design and test margin requirements,
•   design and test requirements, and
•   informative annexes that provide guidelines on the design and test processes.
This standard is intended to result in the effective design and verification of the multipaction performance of the equipment and consequently in a high confidence in achieving successful product operation.
This standard covers multipaction events occurring in all classes of RF satellite components and equipment at all frequency bands of interest. Operation in single carrier CW and pulse modulated mode are included, as well as multi-carrier operations. This standard does not include breakdown processes caused by collisional processes, such as plasma formation.
This standard is applicable to all space missions.
NOTE    Multipactor in multi-carrier operation is currently being investigated. Hence, please be aware that this document provides only recommendations to multi-carrier operation. These recommendations are provisional and will be reviewed in future versions.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    74 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    92 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The scope of the SpaceFibre standard is the detailed specification a very high-speed serial link protocol stack reaching from link level Quality layer  down to the Physical layer. The higher layers like packet, network and higher level protocols are the same as for SpaceWire and specified in the respective standards ECSS-E-ST-50-12C and ECSS-E-ST-50-51C to 53C.

  • Standard
    232 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This activity will be the update of EN16603-20-06 (published 2014).
This activity was started in ECSS to implement as urgent classified Change Requests.

  • Standard
    124 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This standard specifies the requirements, also known as "relifing requirements", for the planned, intentional storage, control, and removal from storage of electronic, electrical and electromechanical parts which are intended to be used for space applications.
This standard covers the relifing of all components as defined by ECSS-Q-ST-60 and ECSS-Q-ST-60-13.
The relifing process is a lot quality control activity.  The inspections and tests defined do not constitute an up-screening or up-grading of components to a higher level of quality than procured to.
In line with ECSS-Q-ST-60, this standard differentiates between classes of components through different sets of standardization requirements.
The classes provide levels of trade-off between assurance and risk. The highest assurance and lowest risk is provided by Class 1 and the lowest assurance and highest risk by Class 3. Procurement costs are typically highest for Class 1 and lowest for Class 3. Mitigation and other engineering measures can decrease the total cost of ownership differences between the three classes. The project objectives, definition and constraints determine which class or classes of components are appropriate to be utilised within the system and subsystems.
-   Class 1 components are described in Clause 4, 5 and 6
-   Class 2 components are described in Clause 4, 5 and 6
-   Class 3 components are described in Clause 4, 5 and 7
The requirements of this document apply to all parties involved at all levels in the integration of EEE components into space segment hardware and launchers.
This standard is applicable to all EEE parts covered by ECSS-Q-ST-60 and used in space programmes.
This standard is not applicable to dice.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard establishes the basic rules and general principles applicable to the electrical, electronic, electromagnetic, microwave and engineering processes. It specifies the tasks of these engineering processes and the basic performance and design requirements in each discipline.
It defines the terminology for the activities within these areas.
It defines the specific requirements for electrical subsystems and payloads, deriving from the system engineering requirements laid out in ECSS-E-ST-10 “Space engineering – System engineering general requirements”.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    128 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard specifies star sensor performances as part of a space project. The Standard covers all aspects of performances, including nomenclature, definitions, and performance requirements for the performance specification of star sensors.
The Standard focuses on:
- performance specifications (including the impact of temperature, radiation and straylight environments);
- robustness (ability to maintain functionalities under non nominal environmental conditions).
Other specification types, for example mass and power, housekeeping data and data structures, are outside the scope of this Standard.
This Standard also proposes a standard core of functional interfaces defined by unit suppliers and avionics primes in the context of Space AVionics Open Interface aRchitecture (SAVOIR) initiative.
When viewed from the perspective of a specific project context, the requirements defined in this Standard should be tailored to match the genuine requirements of a particular profile and circumstances of a project.
This standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.

  • Standard
    88 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1   Purpose:
The "Scheduling and Commanding Messages" (SCM) specifies a standard format for observing system commanding and scheduling. This document aims to ease the planning and operation processes and to reduce the effors from researchers that use several different observing systems and/or simulation software products.
The SCM establishes a common language for exchanging information on planning, scheduling, and executing observations of celestial objects. In the end this will:
a)   Facilitate interoperability and enable consistent warning between data originators who supply celestial observations and the entities or researchers who use it; and
b)   Facilitate the automation of observation processes.
1.2   Applicability:
The SCM is applicable to ground-based activities related to the planning, scheduling, and execution of the observations of celestial objects. It is used by planning software, scheduling software, telescope commanding software. It is applicable for optical telescopes.

  • Standard
    64 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1   Purpose:
The Observing System Data Message (OSDM) is a standard message format to be used in the exchange of optical telescope, laser ranging station, and radar (observing systems) information between Space situational Awareness (SSA) data providers, owners/operators of observing systems, and other parties. These messages can inform SSA data providers, which are the consumers of observing system output data, on the parameters of the observing systems.
The OSDM standard will:
a)   enable consistent data exchange between observation data providers and SSA systems;
b)   facilitate data exchange automation and ingestion of observation data from different providers;
c)   facilitate SSA system architecture performance simulations; and
d)   provide a quick way to estimate the expected performance from one observing system.
1.2   Applicability:
The Observing System Data Message standard is applicable to all SSA activities, especially Space Surveillance and Tracking (SST) and near-Earth objects (NEO), and other fields where the acquisition of astrometric and photometric data plays a role (e.g. space debris, observational astronomy). The standard contains a message designed to contain observing system parameters exchanged between producers and consumers of astrometric and/or photometric data. These data include observing system name, location, type (optical/radar), operator and tracking/survey performance.
The OSDM is suitable for both manual and automated interaction, but will not contain a large amount of data. The message is self contained and can be paired with several Tracking Data Messages (TDM – specified reference [1]), FITS images (specified in reference [2]), or other formats containing the observation data.
The OSDM standard only applies to the message format, structure and content. The exchange method is beyond the scope of the standard, and it is due to be specified in an ICD, though an ICD is not always required. The methods used to produce the data in the message are also beyond the scope of the standard.
1.3   Document structure:
Clause 5 provides an overview of the OSDM.
Clause 6 described the structure and content of the 'keyword = value' (KVN) version of the OSDM.
Clause 7 described the strucuture and content of the XML version of the OSDM.
Clause 8 describes the data and syntax of OSDM messages, in both KVN and XML.
Annex A lists agreed values for some of the OSDM keywords.
Annex B presents some examples of OSDMs.

  • Standard
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document establishes general test requirements for launch vehicles equipped with liquid-propellant engines, launched from stationary ground-, sea- and air-based launchers, in all phases of their development.

  • Standard
    37 pages
    English language
    sale 15% off
  • Draft
    37 pages
    English language
    sale 15% off

This document provides requirements for launch system designers or interface designers regarding interfaces between LV and EGSE, which is used to support on-line processing. It defines electrical interface types, design requirements, environment requirements, verification methods (analyses and tests), and interface check operation requirements. This document is intended to minimize design costs and reduce risks from errors resulting from miscommunication. It does not limit LV or EGSE organizational requirements to specify a unique interface.

  • Standard
    10 pages
    English language
    sale 15% off
  • Draft
    10 pages
    English language
    sale 15% off

The document defines the requirements for the interfaces of simulation models between simulation
environments.

  • Standard
    143 pages
    English language
    sale 10% off
    e-Library read for
    1 day

In general terms, the scope of the consolidation of the electrical interface
requirements for electrical (hold down and release or deployment) actuators in
the present ECSS-E-ST-20-21 and the relevant explanation in the handbook
ECSS-E-HB-20-21 is to allow a more recurrent approach both for actuator
electronics (power source) and electrical actuators (power load) offered by the
relevant manufacturers, at the benefit of the system integrators and of the
Agency, thus ensuring:
• better quality,
• stability of performances, and
• independence of the products from specific mission targets.
A recurrent approach enables manufacturing companies to concentrate on
products and a small step improvement approach that is the basis of a high
quality industrial output.

  • Standard
    37 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The purpose of this Standard is to define the Factors Of Safety (FOS), Design Factor and additional factors to be used for the dimensioning and design verification of spaceflight hardware including qualification and acceptance tests.
This standard is not self standing and is used in conjunction with the ECSS-E-ST-32, ECSS-E-ST-32-02 and ECSS-E-ST-33-01 documents.
Following assumptions are made in the document:
-   that recognized methodologies are used for the determination of the limit loads, including their scatter, that are applied to the hardware and for the stress analyses;
-   that the structural and mechanical system design is amenable to engineering analyses by current state-of-the-art methods and is conforming to standard aerospace industry practices.
Factors of safety are defined to cover chosen load level probability, assumed uncertainty in mechanical properties and manufacturing but not a lack of engineering effort.
The choice of a factor of safety for a program is directly linked to the rationale retained for designing, dimensioning and testing within the program. Therefore, as the development logic and the associated reliability objectives are different for:
-   unmanned scientific or commercial satellite,
-   expendable launch vehicles,
-   man-rated spacecraft, and
-   any other unmanned space vehicle (e.g. transfer vehicle, planetary probe)
specific values are presented for each of them.
Factors of safety for re-usable launch vehicles and man-rated commercial spacecraft are not addressed in this document.
For all of these space products, factors of safety are defined hereafter in the document whatever the adopted qualification logic: proto-flight or prototype model.
For pressurized hardware, factors of safety for all loads except internal pressure loads are defined in this standard. Concerning the internal pressure, the factors of safety for pressurised hardware can be found in ECSS-E-ST-32-02. For loads combination refer to ECSS-E-ST-32-02.
For mechanisms, specific factors of safety associated with yield and ultimate of metallic materials, cable rupture factors of safety, stops/shaft shoulders/recess yield factors of safety and limits for peak Hertzian contact stress are specified in ECSS-E-ST-33-01.
Alternate approach
The factors of safety specified hereafter are applied using a deterministic approach i.e. as generally applied in the Space Industry to achieve the structures standard reliability objectives. Structural safety based on a probabilistic analysis could be an alternate approach but it has to be demonstrated this process achieves the reliability objective specified to the structure. The procedure is approved by the customer.
This standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.

  • Standard
    24 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document regards the test procedures for assessment of robustness to security attacks.
Starting from the definition of security attacks taxonomy and security metrics, this TR aims to:
1. Specify test facilities to be used in the tests of GPBT. This comprises both hardware and software equipment.
2. Define relevant test scenarios applicable to security performances. Also the field test needed for validation of scenarios will be properly described.
3. Define end-to-end test procedures comprising experimental validation of the whole test chain.
The results will benefit to the operational basis of EN16803-3 "Assessment of security performances of GNSS based
positioning terminals".

  • Technical report
    135 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    135 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document presents the requirements for requirements management (RM) for space projects. This document addresses the space programme/project management requirements, applicable through a top-down approach in a contractual relationship between customers and suppliers. The objective of this document is to state and establish a common reference framework for all the customers and suppliers in the space sector to deploy requirements management for all space products and projects. This document on requirements management includes — a definition of the requirements management scope for the space sector, — the standard processes for requirements management within the product lifecycle management, and — a set of rules for requirements management activities to be implemented by the actors (customers and suppliers), including rules derived from best practices. The primary target audience for this document includes — the requirements management/systems engineering process owners of the customers and suppliers, — the programme/project managers managing the space programmes, and — the chief engineers and the quality managers. The term "programme" is understood as a group of several projects. Both "programme" and "project" can be used in the same context throughout this document. In addition, this document allows customer/supplier flexibility in its implementation and tailoring.

  • Standard
    15 pages
    English language
    sale 15% off

This standard specifies requirements for the durability testing of coatings most commonly used for space applications, i.e.:
-   Thin film optical coatings
-   Thermo-optical and thermal control coatings (the majority are paints, metallic deposits and coatings for stray light reduction)
-   Metallic coatings for other applications (RF, electrical, corrosion protection)
This standard covers testing for both ground and in-orbit phases of a space mission, mainly for satellite applications.
This standard applies to coatings within off the shelf items
This standard specifies the types of test to be performed for each class of coating, covering the different phases of a space project (evaluation, qualification and acceptance)
This standard does not cover:
-   The particular qualification requirements for a specific mission
-   Specific applications of coatings for launchers (e.g. high temperature coatings)
-   Specific functional testing requirements for the different coating classes
-   Test requirements for long term storage
-   Solar cell cover glass coatings
-   Surface treatments and conformal coatings applied on EEE parts

  • Standard
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard defines the requirements for the control of nonconformances.
This Standard applies to all deliverable products and supplies, at all levels, which fail to conform to project requirements.
This Standard is applicable throughout the whole project lifecycle as defined in ECSS-M-ST-10.
This standard may be tailored for the specific characteristics and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard specifies the physical interconnection media and data communication protocols to enable the reliable sending of data at high­speed (between 2 Mb/s and 400 Mb/s) from one unit to another. SpaceWire links are full­duplex, point­to­point, serial data communication links.
The scope of this Standard is the physical connectors and cables, electrical properties, and logical protocols that comprise the SpaceWire data link. SpaceWire provides a means of sending packets of information from a source node to a specified destination node. SpaceWire does not specify the contents of the packets of information.
This Standard covers the following protocol levels:
•   Physical level: Defines connectors, cables, cable assemblies and printed circuit board tracks.
•   Signal level: Defines signal encoding, voltage levels, noise margins, and data signalling rates.
•   Character level: Defines the data and control characters used to manage the flow of data across a link.
•   Exchange level: Defines the protocol for link initialization, flow control, link error detection and link error recovery.
•   Packet level: Defines how data for transmission over a SpaceWire link is split up into packets.
•   Network level: Defines the structure of a SpaceWire network and the way in which packets are transferred from a source node to a destination node across a network. It also defines how link errors and network level errors are handled.
This Standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.

  • Standard
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard defines the quality assurance (QA) requirements for the establishment and implementation of a Quality Assurance
programme for products of space projects. Discipline related qualification activities are complemented in standards specific to those
disciplines (e.g. ECSS-E-ST-32-01 for fracture control).
For software quality assurance, the software product assurance standard, ECSS-Q-ST-80 is applicable.
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.
For the tailoring of this standard the following information is provided:
- A table providing the pre-tailoring per "Product types" in clause 6
- A table providing the pre-tailoring per "Project phase" in Annex J

  • Standard
    70 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This standard specifies requirements for the durability testing of coatings most commonly used for space applications, i.e.:
-   Thin film optical coatings
-   Thermo-optical and thermal control coatings (the majority are paints, metallic deposits and coatings for stray light reduction)
-   Metallic coatings for other applications (RF, electrical, corrosion protection)
This standard covers testing for both ground and in-orbit phases of a space mission, mainly for satellite applications.
This standard applies to coatings within off the shelf items
This standard specifies the types of test to be performed for each class of coating, covering the different phases of a space project (evaluation, qualification and acceptance)
This standard does not cover:
-   The particular qualification requirements for a specific mission
-   Specific applications of coatings for launchers (e.g. high temperature coatings)
-   Specific functional testing requirements for the different coating classes
-   Test requirements for long term storage
-   Solar cell cover glass coatings
-   Surface treatments and conformal coatings applied on EEE parts

  • Standard
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard defines the quality assurance (QA) requirements for the establishment and implementation of a Quality Assurance
programme for products of space projects. Discipline related qualification activities are complemented in standards specific to those
disciplines (e.g. ECSS-E-ST-32-01 for fracture control).
For software quality assurance, the software product assurance standard, ECSS-Q-ST-80 is applicable.
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.
For the tailoring of this standard the following information is provided:
- A table providing the pre-tailoring per "Product types" in clause 6
- A table providing the pre-tailoring per "Project phase" in Annex J

  • Standard
    70 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard specifies the physical interconnection media and data communication protocols to enable the reliable sending of data at high­speed (between 2 Mb/s and 400 Mb/s) from one unit to another. SpaceWire links are full­duplex, point­to­point, serial data communication links.
The scope of this Standard is the physical connectors and cables, electrical properties, and logical protocols that comprise the SpaceWire data link. SpaceWire provides a means of sending packets of information from a source node to a specified destination node. SpaceWire does not specify the contents of the packets of information.
This Standard covers the following protocol levels:
•   Physical level: Defines connectors, cables, cable assemblies and printed circuit board tracks.
•   Signal level: Defines signal encoding, voltage levels, noise margins, and data signalling rates.
•   Character level: Defines the data and control characters used to manage the flow of data across a link.
•   Exchange level: Defines the protocol for link initialization, flow control, link error detection and link error recovery.
•   Packet level: Defines how data for transmission over a SpaceWire link is split up into packets.
•   Network level: Defines the structure of a SpaceWire network and the way in which packets are transferred from a source node to a destination node across a network. It also defines how link errors and network level errors are handled.
This Standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.

  • Standard
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    123 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Standard defines the requirements for the control of nonconformances.
This Standard applies to all deliverable products and supplies, at all levels, which fail to conform to project requirements.
This Standard is applicable throughout the whole project lifecycle as defined in ECSS-M-ST-10.
This standard may be tailored for the specific characteristics and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines procedures, contents and requirements for test reviews which are composed of the Test Readiness Review (TRR), Post Test Review (PTR) and Test Review Board (TRB). This document is applicable to tests of space systems and space products, including environment tests and functional and performance tests, especially for system level tests and complicated tests.

  • Standard
    20 pages
    English language
    sale 15% off

This standard contains planetary protection requirements, including:
-   Planetary protection management requirements;
-   Technical planetary protection requirements for robotic and human missions (forward and backward contamination);
-   Planetary protection requirements related to procedures;
-   Document Requirements Descriptions (DRD) and their relation to the respective reviews.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.

  • Standard
    46 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Recommended Standard defines the Monitored Data service in terms of: a) the CSTS procedures that constitute the service; b) the extensions and refinements of the behavior of those CSTS procedures necessary to provide the transfer service; c) the extensions and refinements of standard CSTS operations associated with each of the procedures; d) the relationships among the procedures that constitute the service. It does not specify: a) individual implementations or products; b) the implementation of entities or interfaces within real systems; c) the methods or technologies required to measure the values of monitored parameters and to detect the occurrence of events of interest; d) the methods or technologies required for communication; e) the management activities necessary to schedule, configure, and control the MD-CSTS; f) the specific parameters that are to be reported and events that are to be notified by the MD-CSTS.

  • Standard
    108 pages
    English language
    sale 15% off

1.1.1 This Recommended Standard defines, in an abstract manner, a CSTS in terms of: a) the procedures necessary to provide the service; b) the states of the service; c) the behavior of each procedure; d) the states of the procedures; e) the operations necessary to constitute the procedures; and f) the parameters associated with each operation. 1.1.2 It does not specify: a) individual application services, implementations, or products; b) the implementation of entities or interfaces within real systems; c) the methods or technologies required to acquire data; d) the methods or technologies required to provide a suitable environment for communications; or e) the management activities required to schedule and configure services.

  • Standard
    329 pages
    English language
    sale 15% off

This standard contains planetary protection requirements, including:
-   Planetary protection management requirements;
-   Technical planetary protection requirements for robotic and human missions (forward and backward contamination);
-   Planetary protection requirements related to procedures;
-   Document Requirements Descriptions (DRD) and their relation to the respective reviews.
This standard may be tailored for the specific characteristic and constraints of a space project in conformance with ECSS-S-ST-00.

  • Standard
    46 pages
    English language
    sale 10% off
    e-Library read for
    1 day