SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The capabilities of the European Space Agency's SPAS and EURECA platforms for reference payload accommodation are considered. The instrument pointing subsystem, the position and hold mount, and the antenna pointing mechanism developed by Dornier are described. Relevant payloads for the space station are summarized and space station accommodation aspects are discussed.
This document is the NASA AATT Task Order 24 Final Report. NASA Research Task Order 24 calls for the development of eleven distinct task reports. Each task was a necessary exercise in the development of comprehensive communications systems architecture (CSA) for air traffic management and aviation weather information dissemination for 2015, the definition of the interim architecture for 2007, and the transition plan to achieve the desired End State. The eleven tasks are summarized along with the associated Task Order reference. The output of each task was an individual task report. The task reports that make up the main body of this document include Task 5, Task 6, Task 7, Task 8, Task 10, and Task 11. The other tasks provide the supporting detail used in the development of the architecture. These reports are included in the appendices. The detailed user needs, functional communications requirements and engineering requirements associated with Tasks 1, 2, and 3 have been put into a relational database and are provided electronically.
The material contained in this report was compiled to capture the work performed by the National Aeronautics and Space Administration's (NASA's) Exploration study team in the late 2002 timeframe. The "Exploration Blueprint Data Book" documents the analyses and findings of the 90-day Agency-wide study conducted from September - November 2002. During the summer of 2002, the NASA Deputy Administrator requested that a study be performed with the following objectives: - Develop the rationale for exploration beyond low-Earth orbit - Develop roadmaps for how to accomplish the first steps through humans to Mars - Develop design reference missions as a basis for the roadmaps - Make recommendations on what can be done now to effect this future This planning team, termed the Exploration Blueprint, performed architecture analyses to develop roadmaps for how to accomplish the first steps beyond LEO through the human exploration of Mars. The previous NASA Exploration Team activities laid the foundation and framework for development of NASA's Integrated Space Plan. The reference missions resulting from the analysis performed by the Exploration Blueprint team formed the basis for requirement definition, systems development, technology roadmapping, and risk assessments for future human exploration beyond low-Earth orbit. Emphasis was placed on developing recommendations on what could be done now to effect future exploration activities. The Exploration Blueprint team embraced the "Stepping Stone" approach to exploration where human and robotic activities are conducted through progressive expansion outward beyond low-Earth orbit. Results from this study produced a long-term strategy for exploration with near-term implementation plans, program recommendations, and technology investments. Specific results included the development of a common exploration crew vehicle concept, a unified space nuclear strategy, focused bioastronautics research objectives, and an integrated human and robotic exploration strategy. Recommendations from the Exploration Blueprint included the endorsement of the Nuclear Systems Initiative, augmentation of the bioastronautics research, a focused space transportation program including heavy-lift launch and a common exploration vehicle design for ISS and exploration missions, as well as an integrated human and robotic exploration strategy for Mars.
The Lunar Landing Research Vehicles (LLRVs) and the Lunar Landing Training Vehicles (LLTVs) provided astronaut candidates for the Apollo program with essential experience and confidence required to complete the missions, and contributed to six successful manned landings on the moon. The primary challenge in terrestrial training was being able to replicate the ratio of bank angle to linear acceleration that a pilot would experience in lunar gravity. Presently, as the Artemis program seeks to return humans to the Moon by 2025, engineers are evaluating suitable platforms to serve as an In-Flight Trainer (IFT) or Artemis Lunar Training Vehicle (ALTV) for astronauts training in the task of manual landing. The program is investigating the viability of current technology in the field of electric vertical takeoff and landing (eVTOL) vehicles and is evaluating using a multi tilt-rotor aircraft platform as a candidate platform for a preliminary ALTV. The tilt-rotor capability enables the vehicle attitude to be decoupled from its flight path, which is a crucial requirement in realistically simulating lunar gravity on Earth. Other key considerations include compensating for a lack of aerodynamic forces while flying through the atmosphere of Earth, as well as the ability to simulate the dynamics of multiple different lander designs for the Human Landing System (HLS) program. This paper details the feasibility study and presents a preliminary flight control architecture for an IFT based on a notional multi tilt-rotor platform. The modeling-following control law, based on nonlinear dynamic inversion (NDI), removes the need for gain scheduling because the vehicle operates across a wide range of flight conditions. The inner-loop dynamic control allocation strategy consists of a static portion that is optimized offline for trim while compensating for the difference in gravity and a dynamic portion that is computed in real time. The reference model consists of the full closed-loop dynamics of a generic HLS design. The modularity of the flight control architecture enables evaluation of multiple HLS concepts with minimal modifications to the control law. Simulation results of the multi tilt-rotor configuration following the final portion of the Apollo 11 descent trajectory are shown.
This paper presents a Port Controlled Hamiltonian based direct power control architecture for a back-to-back modular multilevel converter system connecting two ac sources at different frequencies. The system features advanced grid support functionalities based on IEEE 1547-2018, implemented on the inverter side. The rectifier side controller ensures reference following for active and/or reactive powers and maintains the commanded dc bus voltage. The inverter side controller ensures power command following for active and reactive powers.The proposed control architecture is designed to suppress second harmonic oscillations in powers during unbalanced grid voltage sags by dynamically adjusting the currents on each ac side. This also ensures effective elimination of any second harmonic oscillations in the equivalent dc bus voltage. Validation is performed on an OPAL-RT real-time platform with case studies on unbalanced and balanced sags, demonstrating the controller's effectiveness during real time implementation. A reduced-scale laboratory prototype further verifies these case studies, with experimental results for balanced sags due to grid simulator limitations. The results confirm the robustness and efficiency of the proposed control strategy in ensuring stable and reliable operation under various grid conditions.
There is a growing demand for advanced conductors with enhanced electrical properties to increase the energy efficiency in various applications. A promising strategy to achieve this involves the use of ultraconductive copper (UCC) composites that incorporate highly conductive carbon materials, such as carbon nanotubes (CNTs), into the copper matrix. In this study, we present a scalable brush coating technique to incorporate CNTs onto Cu substrates to produce Cu–CNT–Cu composites. The process involves brush coating the CNT solution on Cu tape substrates, followed by vacuum-assisted thermal removal of organic moieties (e.g., surfactant/polymer). This step ensures the creation of a uniformly distributed CNT network within the Cu matrix. By addition of a thin film Cu overlayer, the fabricated Cu–CNT–Cu composite architecture demonstrates similar electrical conductivity, increased current carrying capacity, and enhanced mechanical properties compared to pure Cu reference tapes. Finally, the performance characteristics of these UCC tapes along with the scalability of the brush coating approach hold great promise for the fabrication of advanced conductors for wide-ranging energy applications.
Large aperture phased array antennas operating at millimeter wave frequencies are designed for space-based communications and imaging platforms. Array elements are comprised of active T/R modules which are linked to the central processing unit through high-speed fiber-optic networks. The system architecture satisfying system requirements at millimeter wave frequency is T/R level data mixing where data and frequency reference signals are distributed independently before mixing at the T/R modules. This paper demonstrates design procedures of a low loss high-speed fiber-optic link used for transmission of data signals over 600-900 MHz bandwidth inside satellite. The fiber-optic link is characterized for transmission of analog and digital data. A dynamic range of 79 dB/MHz was measured for analog data over the bandwidth. On the other hand, for bursted SMSK satellite traffic at 220 Mbps rates, BER of 2 x 10 to the -7th was measured for E(b)/N(o) of 14.3 dB.
This paper describes the design, development, and initial use of a generalized and configurable lunar lander simulation to support NASA’s Artemis Program. This simulation is being developed for the Crew Compartment Office (CrewCo) in the Human Landing Systems (HLS) program and is called the HLS CrewCo Lander Simulation (HCLS). The HCLS provides insight into the challenges associated with returning humans to the Moon and the particular difficulties of operating at the Lunar South Pole. The simulation models a generalized integrated lunar landing spacecraft based on a government reference design but can and has been adapted to model vendor specific designs as well. The simulation architecture and tool sets provide a flexible framework that allows for quickly prototyping and evaluating various aspects of a piloted lunar landing system. This includes the modeling of all principal human controlled flight phases: rendezvous and docking with crew transfer systems; docked orbital outpost operations; undocking and lunar transfer; lunar orbital operations; lunar deorbit, descent, and landing (DDL); lunar surface operations; lunar ascent; and return to the orbital outpost. The flexibility of the simulation allows for the integrated evaluation of potential vehicle subsystems, crew displays, guidance and control modes, and trajectory designs. The purpose of the HCLS is not to design the ideal lunar lander, but rather to understand and the strengths and weaknesses of vehicle design choices. This paper describes the basic simulation architecture and discusses the tool sets used to develop the HCLS. This includes a number of open source tool sets and publicly available data sets. This paper also describes some of the early use cases and findings. The primary focus of early HCLS use has been on the manual piloting task to safely get the crew to the desired landing site in case of a failure in the automated guidance system. Several guidance modes and cues have been implemented which allow a pilot to manually fly the vehicle to the targeted landing site starting anywhere from powered descent initiation. It has been a valuable tool for understanding what is required to manually fly a lunar lander as well as giving a sense of the vehicle dynamics, which are much different than anything that is flown on Earth. A number of experienced test pilots have participated in manual piloting evaluations using the HCLS and provided valuable feedback on the piloting task which has been very beneficial to NASA and the HLS program.
To the extent it makes sense, leverage JWST (James Webb Space Telescope) knowledge, designs, architectures. GSE (Ground Support Equipment) good starting point. Develop a full end-to-end architecture that closes. Try to avoid recreating the wheel except where needed. Optimize from there (mainly for stability and coronagraphy). Develop a scalable design reference mission (9.2 meters). Do just enough work to understand launch break points in aperture size Demonstrate 10 pm (phase modulation) stability is achievable on a design reference mission. A really key design driver is the most robust stability possible!!! Make design compatible with starshades. While segmented coronagraphs with high throughput and large bandpasses are important, make the system serviceable so you can evolve the instruments. Keep it room temperature to minimize the costs associated with cryo. Focus resources on the contrast problem. Start with the architecture and connect it to the technology needs.
The U.S. Vision for Space Exploration (January 2004) serves as the foundation for the National Aeronautics and Space Administration's (NASA) strategic goals and objectives. As the NASA Administrator outlined during his confirmation hearing in April 2005, these include: 1) Flying the Space Shuttle as safely as possible until its retirement, not later than 2010. 2) Bringing a new Crew Exploration Vehicle (CEV) into service as soon as possible after Shuttle retirement. 3) Developing a balanced overall program of science, exploration, and aeronautics at NASA, consistent with the redirection of the human space flight program to focus on exploration. 4) Completing the International Space Station (ISS) in a manner consistent with international partner commitments and the needs of human exploration. 5) Encouraging the pursuit of appropriate partnerships with the emerging commercial space sector. 6) Establishing a lunar return program having the maximum possible utility for later missions to Mars and other destinations. In spring 2005, the Agency commissioned a team of aerospace subject matter experts to perform the Exploration Systems Architecture Study (ESAS). The ESAS team performed in-depth evaluations of a number of space transportation architectures and provided recommendations based on their findings? The ESAS analysis focused on a human-rated Crew Launch Vehicle (CLV) for astronaut transport and a heavy lift Cargo Launch Vehicle (CaLV) to carry equipment, materials, and supplies for lunar missions and, later, the first human journeys to Mars. After several months of intense study utilizing safety and reliability, technical performance, budget, and schedule figures of merit in relation to design reference missions, the ESAS design options were unveiled in summer 2005. As part of NASA's systems engineering approach, these point of departure architectures have been refined through trade studies during the ongoing design phase leading to the development phase that begins in 2008. Comprehensive reviews of engineering data and business assessments by both internal and independent reviewers serve as decision gates to ensure that systems can fully meet customer and stakeholder requirements. This paper provides the current CLV and CaLV configuration designs and gives examples of the progress being made during the first year of this significant effort. Safe, reliable, cost-effective space transportation systems are a foundational piece of America s future in space and the next step in realizing the plan for revitalizing lunar capabilities on the passageway to the human exploration of Mars. While building on legacy knowledge and heritage hardware for risk reduction, NASA will apply lessons learned from developing these new launch vehicles to the growth path for future missions. The elements for mission success and continued U.S. leadership in space have been assembled over the past year. As NASA designs and develops these two new systems over the next dozen years, visible progress, such as that reported in this paper, may sustain the national will to stay the course across political administrations and weather the inevitable trials that will be experienced during this challenging endeavor.
As part of NASA s Constellation Program to resume exploration beyond low Earth orbit (LEO), the Ares V heavy-lift cargo launch vehicle as currently conceived will be able to send more crew and cargo to more places on the Moon than the Apollo Program Saturn V. (Figure 1) It also has unprecedented cargo mass and volume capabilities that will be a national asset for science, commerce, and national defense applications. Compared to current systems, it will offer approximately five times the mass and volume to most orbits and locations. The Columbia space shuttle accident, the resulting investigation, the Vision for Space Exploration, and the Exploration Systems Architecture Study (ESAS) broadly shaped the Constellation architecture. Out of those events and initiatives emerged an architecture intended to replace the space shuttle, complete the International Space Station (ISS), resume a much more ambitious plan to explore the moon as a stepping stone to other destinations in the solar system. The Ares I was NASA s main priority because of the goal to retire the Shuttle. Ares V remains in a concept development phase, evolving through hundreds of configurations. The current reference design was approved during the Lunar Capabilities Concept Review/Ares V Mission Concept Review (LCCR/MCR) in June 2008. This reference concept serves as a starting point for a renewed set of design trades and detailed analysis into its interaction with the other components of the Constellation architecture and existing launch infrastructure. In 2009, the Ares V team was heavily involved in supporting the Review of U.S. Human Space Flight Plans Committee. Several alternative designs for Ares V have been supplied to the committee. This paper will discuss the origins of the Ares V design, the evolution to the current reference configuration, and the options provided to the review committee.
This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.
The Johnson Space Center Management Information System (JSCMIS) is an interface to computer data bases at the NASA Johnson Space Center which allows an authorized user to browse and retrieve information from a variety of sources with minimum effort. The User's Guide to JSCMIS is the supplement to the JSCMIS Research Report which details the objectives, the architecture, and implementation of the interface. It is a tutorial on how to use the interface and a reference for details about it. The guide is structured like an extended JSCMIS session, describing all of the interface features and how to use them. It also contains an appendix with each of the standard FORMATs currently included in the interface. Users may review them to decide which FORMAT most suits their needs.
Surprisingly little is known about Venus, our neighboring sister planet in the solar system, due to the challenges of operating in its extremely hot, corrosive, and dense environment. For example, after over two dozen missions to the planet, the longest-lived lander was the Soviet Venera 13, and it only survived two hours on the surface. Several conceptual Venus mission studies have been formulated in the past two decades proposing lander architectures that potentially extend lander lifetime. Most recently, the Venus Science and Technology Definition Team (STDT) was commissioned by NASA to study a Venus Flagship Mission potentially launching in the 2020- 2025 time-frame; the reference lander of this study is designed to survive for only a few hours more than Venera 13 launched back in 1981! Since Cytherean mission planners lack a viable approach to a long-lived surface architecture, specific scientific objectives outlined in the National Science Foundation Decadal Survey and Venus Exploration Advisory Group final report cannot be completed. These include: mapping the mineralogy and composition of the surface on a planetary scale determining the age of various rock samples on Venus, searching for evidence of changes in interior dynamics (seismometry) and its impact on climate and many other key observations that benefit with time scales of at least a full Venus day (Le. daylight/night cycle). This report reviews those studies and recommends a hybrid lander architecture that can survive for at least one Venus day (243 Earth days) by incorporating selective Stirling multi-stage active cooling and hybrid thermoacoustic power.
For any given surface mission duration, there exists a set of surface capabilities necessary to sustain a four-person crew for the length of time the crew is on the surface. Identifying these capabilities is important to mission planners and spacecraft design engineers responsible for lunar surface habitation elements, who need to know which systems and capabilities must be prioritized for the vehicles they are designing. However, simply identifying the surface capabilities does not necessarily equal a viable surface configuration. These capabilities may or may not satisfy stakeholder expectations or even permit completion of mission objectives. Lunar lander cargo mass constraints are a powerful forcing function that requires significant efforts to reduce the mass of all surface elements, including those supporting crew habitation. The required capabilities do increase as a function of mission duration, but it is a nonlinear growth. There are key points in mission duration, beyond which certain additional capabilities are needed. This forms bands of capability between each point. Within a given band, the same functional capabilities are needed, and the only scaling is that associated with daily consumables. The next higher band requires additional capabilities. This paper will focus on those capabilities needed for missions of 30-90 days. It should be noted that there are some uncertainties interpreting NASA requirements that require capabilities after a certain number of days, as typically this refers to number of days in space, not number of days on the lunar surface. Depending on transportation architecture, the number of days between Earth launch and lunar surface landing may vary, therefore impacting when certain required capabilities are implemented. However, activities to prepare humans for missions to Mars and commercial interest in lunar development may drive progressive increases in surface duration. Missions up to 30 days are expected to follow the initial 6.5-day surface missions and there may be commercial interest in extending to even greater durations. This paper will examine the potential case of a 30-90-day surface mission duration with respect to the systems necessary to support crew living and working on the lunar surface.
The Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) is a computational model that provides human health and medical risk predictions for crewed spaceflight missions. MEDPRAT utilizes discrete event modeling and dynamic probabilistic simulation to predict critical mission outcomes (total medical events, crew health index, quality time lost, loss of crew life, removal to definitive care), condition occurrences, and resource consumption. Input parameters for MEDPRAT include crew attributes (e.g., sex), types of mission activities (e.g., whether and where crew members perform an extravehicular activity (EVA)), available resources, treatment information, and probability distributions for medical conditions. As an evolution of the Integrated Medical Model (IMM), MEDPRAT provides enhanced capabilities and higher fidelity, and incorporates more appropriate assumptions for long-duration spaceflight. IMM is the currently accepted standard for quantifying spaceflight mission medical risk in NASA operations that uses a probabilistic risk assessment (PRA) approach. MEDPRAT builds on the same logical foundation as IMM but implements the model architecture through highly optimized Monte Carlo sampling methods. An analysis is performed comparing the outputs from IMM with those from MEDPRAT V1.0 and V2.0 for the same reference missions in order to quantify similarities and differences in the model outcomes. The juxtaposition between IMM and MEDPRAT V1.0 and 2.0 shown in this report demonstrates that these two models generate very similar results; where differences in outcomes are shown, these are in accordance with the underlying assumptions and differences in the model architectures. This validation effort further establishes the credibility and reliability of the MEDPRAT software.
NASA's Unmanned Aerial System (UAS) Traffic Management (UTM) project aims at enabling near-term, safe operations of small UAS vehicles in uncontrolled airspace, i.e., Class G airspace. A far-term goal of UTM research and development is to accommodate the expected rise in small UAS traffic density throughout the National Airspace System (NAS) at low altitudes for beyond visual line-of-sight operations. This video describes a new capability referred to as ICAROUS (Integrated Configurable Algorithms for Reliable Operations of Unmanned Systems), which is being developed under the auspices of the UTM project. ICAROUS is a software architecture comprised of highly assured algorithms for building safety-centric, autonomous, unmanned aircraft applications. Central to the development of the ICAROUS algorithms is the use of well-established formal methods to guarantee higher levels of safety assurance by monitoring and bounding the behavior of autonomous systems. The core autonomy-enabling capabilities in ICAROUS include constraint conformance monitoring and autonomous detect and avoid functions. ICAROUS also provides a highly configurable user interface that enables the modular integration of mission-specific software components.
The Simulation Interoperability Standards Organization (SISO) Space Reference Federation Object Model (SpaceFOM) version 1.0 is nearing completion. Earlier papers have described the use of the High Level Architecture (HLA) in Space simulation as well as technical aspects of the SpaceFOM. This paper takes a look at different SpaceFOM tools and how they were used during the development and testing of the standard.The first organizations to develop SpaceFOM-compliant federates for SpaceFOM development and testing were NASA's Johnson Space Center (JSC), the University of Calabria (UNICAL), and Pitch Technologies.JSC is one of NASA's lead centers for human space flight. Much of the core distributed simulation technology development, specifically associated with the SpaceFOM, is done by the NASA Exploration Systems Simulations (NExSyS) team. One of NASA's principal simulation development tools is the Trick Simulation Environment. NASA's NExSyS team has been modifying and using Trick and TrickHLA to help develop and test the SpaceFOM.The System Modeling And Simulation Hub Laboratory (SMASH-Lab) at UNICAL has developed the Simulation Exploration Experience (SEE) HLA Starter kit, that has been used by most SEE teams involved in the distributed simulation of a Moon base. It is particularly useful for the development of federates that are compatible with the SpaceFOM. The HLA Starter Kit is a Java based tool that provides a well-structured framework to simplify the formulation, generation, and execution of SpaceFOM-compliant federates.Pitch Technologies, a company specializing in distributed simulation, is utilizing a number of their existing HLA tools to support development and testing of the SpaceFOM. In addition to the existing tools, Pitch has developed a few SpaceFOM specific federates: Space Master for managing the initialization, execution and pacing of any SpaceFOM federation; EarthEnvironment, a simple Root Reference Publisher; and Space Monitor, a graphical tool for monitoring reference frames and physical entities.Early testing of the SpaceFOM was carried out in the SEE university outreach program, initiated in SISO. Students were given a subset of the FOM, that was later extended. Sample federates were developed and frameworks were developed or adapted to the early FOM versions.As drafts of the standard matured, testing was performed using federates from government, industry, and academia. By mixing federates developed by different teams the standard could be tested with respect to functional correctness, robustness and clarity.These frameworks and federates have been useful when testing and verifying the design of the standard. In addition to this, they have since formed a starting point for developing SpaceFOM-compliant federations in several projects, for example for NASA, ESA as well as SEE.