SEARCH · Search NASA

Results for “documentation”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRS2005

Documentation: No Substitute for Communication

SO WHAT IS AN RFI? IT WAS ONE OF THE FIRST THINGS I learned about back when I started my project management career with my first large construction firm. I learned how to use these forms as a convenient and effective means of documenting the many legitimate clarifications needed on a major project. However, like most other young engineers, I also learned to use the RFI as a weapon in the ongoing battle between owners. or their designer and the construction contractors. Recently, our project team has done a few simple things to greatly reduce the waste and frustration that comes from this type of battle. The RFI form can be a great tool if used properly, and I certainly don t recommend that they be eliminated entirely. The RFI form was created to document the many clarifications that are commonly required on projects. Typically, the contractor uses the top half of the form to clarify-or request permission to vary from-the contract documents. The bottom half of the form is used to record the answer. But this seemingly simple process is plagued by a number of problems. From the contractor s perspective, RFIs are needed to secure information that should have been in the contract documents in the first place. The missing information keeps their crews from working effectively, and it makes hitting already demanding cost and schedule targets even more difficult. Owners, or their design firms, often view the RFI as a means of harassment. Both sides of the issue have legitimate complaints, and both sides cause most of their own pain.

Strickland, John↗

NASA NTRS2008

Best Practices for Researching and Documenting Lessons Learned

Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.

Goodman, John L.↗

NASA NTRS2010

Jake Garn Mission Simulator and Training Facility, Building 5, Historical Documentation

In response to President George W. Bush's announcement in January 2004 that the Space Shuttle Program (SSP) would end in 2010, the National Aeronautics and Space Administration (NASA) completed a nation-wide historical survey and evaluation of NASA-owned facilities and properties (real property assets) at all its Centers and component facilities. The buildings and structures which supported the SSP were inventoried and assessed as per the criteria of eligibility for listing in the National Register of Historic Places (NRHP) in the context of this program. This study was performed in compliance with Section 110 of the National Historic Preservation Act (NHPA) of 1966 (Public Law 89-665), as amended; the National Environmental Policy Act (NEPA) of 1969 (Public Law 91-190); Executive Order (EO) 11593: Protection and Enhancement of the Cultural Environment; EO 13287, Preserve America, and other relevant legislation. As part of this nation-wide study, in September 2006, historical survey and evaluation of NASA-owned and managed facilities at was conducted by NASA's Lyndon B. Johnson Space Center (JSC) in Houston, Texas. The results of this study are presented in a report entitled, "Survey and Evaluation of NASA-owned Historic Facilities and Properties in the Context of the U.S. Space Shuttle Program, Lyndon B. Johnson Space Center, Houston, Texas," prepared in November 2007 by NASA JSC's contractor, Archaeological Consultants, Inc. As a result of this survey, the Jake Gam Mission Simulator and Training Facility (Building 5) was determined eligible for listing in the NRHP, with concurrence by the Texas State Historic Preservation Officer (SHPO). The survey concluded that Building 5 is eligible for the NRHP under Criteria A and C in the context of the U.S. Space Shuttle program (1969-2010). Because it has achieved significance within the past 50 years, Criteria Consideration G applies. At the time of this documentation, Building 5 was still used to support the SSP as an astronaut training facility. This documentation package precedes any undertaking as defined by Section 106 of the NHPA, as amended, and implemented in 36 CFR Part 800, as NASA JSC has decided to proactively pursue efforts to mitigate the potential adverse affects of any future modifications to the facility. It includes a historical summary of the Space Shuttle program; the history of JSC in relation to the SSP; a narrative of the history of Building 5 and how it supported the SSP; and a physical description of the structure. In addition, photographs documenting the construction and historical use of Building 5 in support of the SSP, as well as photographs of the facility documenting the existing conditions, special technological features, and engineering details, are included. A contact sheet printed on archival paper, and an electronic copy of the work product on CD, are also provided.

Slovinac, Trish↗

NASA NTRS2011

Avionics Systems Laboratory/Building 16. Historical Documentation

As part of this nation-wide study, in September 2006, historical survey and evaluation of NASA-owned and managed facilities that was conducted by NASA s Lyndon B. Johnson Space Center (JSC) in Houston, Texas. The results of this study are presented in a report entitled, "Survey and Evaluation of NASA-owned Historic Facilities and Properties in the Context of the U.S. Space Shuttle Program, Lyndon B. Johnson Space Center, Houston, Texas," prepared in November 2007 by NASA JSC s contractor, Archaeological Consultants, Inc. As a result of this survey, the Avionics Systems Laboratory (Building 16) was determined eligible for listing in the NRHP, with concurrence by the Texas State Historic Preservation Officer (SHPO). The survey concluded that Building 5 is eligible for the NRHP under Criteria A and C in the context of the U.S. Space Shuttle program (1969-2010). Because it has achieved significance within the past 50 years, Criteria Consideration G applies. At the time of this documentation, Building 16 was still used to support the SSP as an engineering research facility, which is also sometimes used for astronaut training. This documentation package precedes any undertaking as defined by Section 106 of the NHPA, as amended, and implemented in 36 CFR Part 800, as NASA JSC has decided to proactively pursue efforts to mitigate the potential adverse affects of any future modifications to the facility. It includes a historical summary of the Space Shuttle program; the history of JSC in relation to the SSP; a narrative of the history of Building 16 and how it supported the SSP; and a physical description of the structure. In addition, photographs documenting the construction and historical use of Building 16 in support of the SSP, as well as photographs of the facility documenting the existing conditions, special technological features, and engineering details, are included. A contact sheet printed on archival paper, and an electronic copy of the work product on CD, are also provided

Slovinac, Patricia↗

NASA NTRS2011

Communications and Tracking Development Laboratory/Building 44. Historical Documentation

As part of this nation-wide study, in September 2006, historical survey and evaluation of NASA-owned and managed facilities was conducted by NASA's Lyndon B. Johnson Space Center (JSC) in Houston, Texas. The results of this study are presented in a report entitled, Survey and Evaluation of NASA-owned Historic Facilities and Properties in the Context of the U.S. Space Shuttle Program, Lyndon B. Johnson Space Center, Houston, Texas, prepared in November 2007 by NASA JSC s contractor, Archaeological Consultants, Inc. As a result of this survey, the Communications and Tracking Development Laboratory (Building 44) was determined eligible for listing in the NRHP, with concurrence by the Texas State Historic Preservation Officer (SHPO). The survey concluded that Building 44 is eligible for the NRHP under Criteria A and C in the context of the U.S. Space Shuttle Program (1969-2010). Because it has achieved significance within the past 50 years, Criteria Consideration G applies. At the time of this documentation, Building 44 was still used to support the SSP as an engineering research facility, which is also sometimes used for astronaut training. This documentation package precedes any undertaking as defined by Section 106 of the NHPA, as amended, and implemented by 36 CFR Part 800, as NASA JSC has decided to proactively pursue efforts to mitigate the potential adverse affects of any future modifications to the facility. It includes a historical summary of the Space Shuttle Program; the history of JSC in relation to the SSP; a narrative of the history of Building 44 and how it supported the SSP; and a physical description of the building. In addition, photographs documenting the construction and historical use of Building 44 in support of the SSP, as well as photographs of the facility documenting the existing conditions, special technological features, and engineering details, are included. A contact sheet printed on archival paper, and an electronic copy of the work product on CD, are also provided.

Slovinac, Patricia↗

NASA NTRS2010

Mission Control Center/Building 30. Historical Documentation

As part of this nation-wide study, in September 2006, historical survey and evaluation of NASA-owned and managed facilities was conducted by NASA's Lyndon B. Johnson Space Center (JSC) in Houston, Texas. The results of this study are presented in a report entitled, Survey and Evaluation of NASA-owned Historic Facilities and Properties in the Context of the U.S. Space Shuttle Program, Lyndon B. Johnson Space Center, Houston, Texas, prepared in November 2007 by NASA JSC s contractor, Archaeological Consultants, Inc. As a result of this survey, the Mission Control Center (Building 30) was determined eligible for listing in the NRHP, with concurrence by the Texas State Historic Preservation Officer (SHPO). The survey concluded that Building 30 is eligible for the NRHP under Criteria A and C in the context of the U.S. Space Shuttle Program (1969-2010). Because it has achieved significance within the past 50 years, Criteria Consideration G applies. It should be noted that the Mission Control Center was designated a National Historic Landmark in 1985 for its role in the Apollo 11 Lunar Landing. At the time of this documentation, Building 30 was still used to support the SSP as an engineering research facility, which is also sometimes used for astronaut training. This documentation package precedes any undertaking as defined by Section 106 of the NHPA, as amended, and implemented in 36 CFR Part 800, as NASA JSC has decided to proactively pursue efforts to mitigate the potential adverse affects of any future modifications to the facility. It includes a historical summary of the Space Shuttle program; the history of JSC in relation to the SSP; a narrative of the history of Building 30 and how it supported the SSP; and a physical description of the structure. In addition, photographs documenting the construction and historical use of Building 30 in support of the SSP, as well as photographs of the facility documenting the existing conditions, special technological features, and engineering details, are included. A contact sheet printed on archival paper, and an electronic copy of the work product on CD, are also provided.

Source record↗

NASA NTRS2010

NASA Docking System (NDS) Interface Definitions Document (IDD)

The NASA Docking System (NDS) mating system supports low approach velocity docking and provides a modular and reconfigurable standard interface, supporting crewed and autonomous vehicles during mating and assembly operations. The NDS is NASA's implementation for the emerging International Docking System Standard (IDSS) using low impact docking technology. All NDS configurations can mate with the configuration specified in the IDSS Interface Definition Document (IDD) released September 21, 2010. The NDS evolved from the Low Impact Docking System (LIDS). The acronym international Low Impact Docking System (iLIDS) is also used to describe this system. NDS and iLIDS may be used interchangeability. Some of the heritage documentation and implementations (e.g., software command names) used on NDS will continue to use the LIDS acronym. The NDS IDD defines the interface characteristics and performance capability of the NDS, including uses ranging from crewed to autonomous space vehicles and from low earth orbit to deep space exploration. The responsibility for developing space vehicles and for making them technically and operationally compatible with the NDS rests with the vehicle providers. Host vehicle examples include crewed/uncrewed spacecraft, space station modules, elements, etc. Within this document, any docking space vehicle will be referred to as the host vehicle. This document defines the NDS-to-NDS interfaces, as well as the NDS-to-host vehicle interfaces and performance capability.

Source record↗

NASA NTRS2008

Advanced Air Transportation Technologies Project, Final Document Collection

This CD ROM contains a compilation of the final documents of the Advanced Air Transportation Technologies (AAIT) project, which was an eight-year (1996 to 2004), $400M project managed by the Airspace Systems Program office, which was part of the Aeronautics Research Mission Directorate at NASA Headquarters. AAIT focused on developing advanced automation tools and air traffic management concepts that would help improve the efficiency of the National Airspace System, while maintaining or enhancing safety. The documents contained in the CD are final reports on AAIT tasks that serve to document the project's accomplishments over its eight-year term. Documents include information on: Advanced Air Transportation Technologies, Autonomous Operations Planner, Collaborative Arrival Planner, Distributed Air/Ground Traffic Management Concept Elements 5, 6, & 11, Direct-To, Direct-To Technology Transfer, Expedite Departure Path, En Route Data Exchange, Final Approach Spacing Tool - (Active and Passive), Multi-Center Traffic Management Advisor, Multi Center Traffic Management Advisor Technology Transfer, Surface Movement Advisor, Surface Management System, Surface Management System Technology Transfer and Traffic Flow Management Research & Development.

Mogford, Richard H.↗

NASA NTRS2013

The GLAS Science Algorithm Software (GSAS) Detailed Design Document Version 6

The Geoscience Laser Altimeter System (GLAS) is the primary instrument for the ICESat (Ice, Cloud and Land Elevation Satellite) laser altimetry mission. ICESat was the benchmark Earth Observing System (EOS) mission for measuring ice sheet mass balance, cloud and aerosol heights, as well as land topography and vegetation characteristics. From 2003 to 2009, the ICESat mission provided multi-year elevation data needed to determine ice sheet mass balance as well as cloud property information, especially for stratospheric clouds common over polar areas. It also provided topography and vegetation data around the globe, in addition to the polar-specific coverage over the Greenland and Antarctic ice sheets.This document describes the detailed design of GLAS Science Algorithm Software (GSAS). The GSAS is used to create the ICESat GLAS standard data products. The National Snow and Ice Data Center (NSDIC) distribute these products. The document contains descriptions, flow charts, data flow diagrams, and structure charts for each major component of the GSAS. The purpose of this document is to present the detailed design of the GSAS. It is intended as a reference source to assist the maintenance programmer in making changes that fix or enhance the documented software.

Lee, Jeffrey E.↗

NASA NTRS2018

Pairwise Trajectory Management (PTM): Concept Description and Documentation

Pairwise Trajectory Management (PTM) is an Interval Management (IM) concept that utilizes airborne and ground-based capabilities to enable the implementation of airborne pairwise spacing capabilities in oceanic regions. The goal of PTM is to use airborne surveillance and tools to manage an "at or greater than" inter-aircraft spacing. Due to the accuracy of Automatic Dependent Surveillance-Broadcast (ADS-B) information and the use of airborne spacing guidance, the minimum PTM spacing distance will be less than distances a controller can support with current automation systems that support oceanic operations. Ground tools assist the controller in evaluating the traffic picture and determining appropriate PTM clearances to be issued. Avionics systems provide guidance information that allows the flight crew to conform to the PTM clearance issued by the controller. The combination of a reduced minimum distance and airborne spacing management will increase the capacity and efficiency of aircraft operations at a given altitude or volume of airspace. This document provides an overview of the proposed application, a description of several key scenarios, a high level discussion of expected air and ground equipment and procedure changes, a description of a NASA human-machine interface (HMI) prototype for the flight crew that would support PTM operations, and initial benefits analysis results. Additionally, included as appendices, are the following documents: the PTM Operational Services and Environment Definition (OSED) document and a companion "Future Considerations for the Pairwise Trajectory Management (PTM) Concept: Potential Future Updates for the PTM OSED" paper, a detailed description of the PTM algorithm and PTM Limit Mach rules, initial PTM safety requirements and safety assessment documents, a detailed description of the design, development, and initial evaluations of the proposed flight crew HMI, an overview of the methodology and results of PTM pilot training requirements focus group and human-in-the-loop testing activities, and the PTM Pilot Guide.

Jones, Kenneth M.↗

NASA NTRS2020

Development of VBA Tool for Document Term Search

Employees throughout different agencies such as NASA, have identified that the search of determined terms/words through documents, consume substantial research time of such. These types of searches are substantially limited towards one word in a one document identification; forward one, these usual types of searches lack efficiency & optimization through research aspects of work. Consequently, this reflects in the decrease productivity during work hours etc. The application of VBA (Visual Basic for Applications) is the programming language of Excel, which was conducted for the development of optimized tool for document term search. The project enables the search of single & multiple word/term search through single format documents for paragraph data extraction.

Ssytems Development↗

NASA NTRS2020

KSC Integration Office Documentation and Support

This report details the process of document management within the KSC Integration Office throughout my internship in the fall term of the year 2020. During this term, I was mentored by Felix A. Soto-Toro and my main objective was to support the Audit Liaison Representatives (ALR) in their documentation processes. I worked alongside the members of the KSC Integration Office to streamline the auditing process in order to facilitate the interchangement of documents and communication between auditors and our agency. My approach to this situation was to document the events of each audit in a report, which would be updated weekly every Monday following a specific format. As support I was required to gather, organize, and release data relevant to current audits in an online server for ALRs to use across the entire NASA Agency.

Ana C Arvelo Serrano↗

NASA NTRS2023

Exploration Systems Development Mission Directorate (ESDMD) Moon-to-Mars Architecture Definition Document

There are many opportunities in executing the ambitious Moon-to-Mars efforts through an integrated architecture. NASA addresses this in its Moon-to-Mars Strategy and Objectives Development2 document (hereafter referred to as the M2M Strategy). Many of these opportunities involve establishing a system engineering framework that can support the breadth of necessary program and system contributions. By applying these needs to nearer-term lunar development, NASA will be instituting the process, procedures, and techniques needed to enable longer-term Mars goals and more. Some of the challenges being addressed in the M2M Strategy are associated with the architecture definition and include broad/changing goals, funding, and external pressures/influences. This document and the methodology outlined for architecture definition have been crafted to contend with these using an iterative and adaptable framework. The primary purpose of the Architecture Definition Document (ADD) is to capture the methodology, organization, and decomposition necessary to translate the broad objectives outlined in the M2M Strategy into functions and use cases that can be allocated to implementable programs and projects. Inherent in this process will be the need to communicate the long-term vision, maintain traceability to responsible parties, and iterate on the architectural implementation as innovations and solutions develop. This document will be updated and improved in conjunction with the Architecture Concept Review (ACR) which will be held annually to help unify the Agency and to get buy-in and input from across the Agency on the human exploration architecture. The annual nature of the process provides the opportunity to continually incorporate new developments in technologies and new partnerships, whether they be with industry, the U.S. Government, international entities, or academia.

Moon-to-Mars Strategy↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

Often when working with technical documents, it is helpful to classify them into specific categories. In this paper, we conduct a thorough review of natural language processing techniques to perform this classification task on Letters of Agreement (LOAs), technical aviation documents outlining rules for utilizing US airspace. We evaluate multiple techniques, including Transfer Learning, for representing the text in the documents as embeddings: unigram and bigram Term Frequency Inverse Document Frequency (TFIDF), Word2Vec, Doc2Vec, GloVe and RoBERTa. We investigate a wide range of classification models: K-Nearest Neighbors, Random Forest, Support Vector Machines (SVM), Logistic Regression, Naive Bayes, Feed-Forward Neural Network, Convolutional Neural Networks (CNNs) and Long-Short Term Memory (LSTM). By comparing the different methods, we found the best overall approach for our task was to use unigram TFIDF representations with SVM while also gaining insight into how the other methodologies performed on a small technical datasets.

Aayushi Batra↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

Often when working with historic air traffic management (ATM) documents, it is helpful to classify them into specific categories. In this paper, we conduct a thorough review of natural language processing techniques to perform this classification task on Letters of Agreement (LOAs), technical aviation documents outlining rules for utilizing US airspace. We evaluate multiple techniques for representing the text in the documents as embeddings: unigram and bigram Term Frequency Inverse Document Frequency (TFIDF), Word2Vec, Doc2Vec, GloVe and RoBERTa. We investigate a wide range of classification models: K-Nearest Neighbors, Random Forest, Support Vector Machines (SVM), Logistic Regression, Naive Bayes, Feed-Forward Neural Network, Convolutional Neural Networks (CNNs) and Long-Short Term Memory (LSTM). By comparing the different methods, we found the best overall approach for our task was to use unigram TFIDF representations with SVM while also gaining insight into how the other methodologies performed on a small technical datasets.

ATM↗

NASA NTRSDate not supplied

Document Classification Techniques for Aviation Letters of Agreement

ATM↗

NASA NTRSDate not supplied

Enhancing accessibility and usability of Algorithm Theoretical Basis Documents through the Algorithm Publication Tool

Effective communication of scientific theories is crucial for transforming raw instrument data into valuable Earth observation products. The NASA Earth science data community disseminates this knowledge through Algorithm Theoretical Basis Documents (ATBDs). Historically, these documents lacked a standardized format, were designed for human readability rather than machine interpretation, and were challenging to locate due to the absence of a centralized repository. The Algorithm Publication Tool (APT) transforms how ATBD content is presented, simplifying the processes of creating, updating, and locating these documents. APT offers authors the option to use its user-friendly cloud-based interface or standardized templates for ATBD development. The primary advantage of the interface is its capability to manage the entire ATBD creation process within a single environment, ensuring comprehensive tracking of all activities and facilitating user tasks. Conversely, the use of standardized ATBD templates allows users to create documents using familiar tools like Google Docs, Microsoft Word, or Overleaf for LaTeX. APT also provides a centralized repository, enabling easy search and discovery of published ATBDs. This presentation showcases APT's functionalities, illustrates its contributions to advancing open science, and highlights potential benefits for broader community adoption.

Bradley Baker↗

NASA NTRS2024

Exploration Systems Development Mission Directorate: Moon to Mars Architecture Definition Document

The National Aeronautics and Space Administration (NASA) explores the unknown in air and space, innovates for the benefit of humanity, and inspires the world through discovery. Extending the reach of humanity through the human exploration of the Moon, Mars, and beyond is key to that mission. NASA’s Moon to Mars Strategy and Objectives document establishes long-term goals and objectives for crewed deep space exploration; however, satisfying NASA’s Moon to Mars Objectives requires an innovative approach to the definition, management, and execution of NASA’s Moon to Mars Architecture. An architecture offers a high-level unifying structure and defines a system. It provides rules, guidelines, and constraints that define a cohesive and coherent framework that identifies constituent parts, relationships, and connections and establishes how those parts fit and work together. This Architecture Definition Document (ADD) establishes the process for the decomposition of objectives empowers the agency’s success in achieving human exploration of the cosmos. NASA updates this document annually to reflect the maturation of the architecture and the progress NASA and partners make toward achieving exploration objectives. The ADD is not a manifest or requirements document. Instead, it serves as a tool for the programs, projects, and engineers who will implement and execute NASA’s bold ambitions for crewed exploration of deep space. As established in the Moon to Mars Strategy and Objectives, “Why” we explore encompasses three pillars: Science, Inspiration, and National Posture. Ensuring success in all three areas requires an architectural approach that incorporates innovation, collaboration, and partnerships that can be sustained across a multi-decadal effort. This second revision (Rev-B) of the ADD, developed to support NASA’s 2024 Architecture Concept Review (ACR), incorporates several key updates to support the continued evolution of the architecture. Since the last revision of the ADD, NASA has significantly improved the clarity of the objective decomposition, which distills exploration objectives into the characteristics and needs and use cases and functions needed to achieve them. The updated decomposition incorporates findings from internal studies and diverse stakeholder feedback. A model-based systems engineering approach ensures coherence and consistency, removing inconsistency and repetition. Revision B also incorporates advancements to NASA’s Mars architecture, including insight into initial capabilities, systems, and operations necessary to support the Humans to Mars segment. Updates to objective decomposition for Mars add significant detail to the ADD and hint at areas of forward work and future study. An appendix adds greater depth in the future decisions needed for Mars that will drive lunar needs. They are not the only decisions to be made, but they will have huge effects on subsequent decisions. NASA continues to introduce new exploration systems into the architecture. Two new elements — initial surface habitat and lunar surface cargo lander—successfully passed mission concept review in 2024 as a result of extensive analysis, concept refinement, and studies. These elements and their respective reference missions appear in this revision. NASA also continues to apply architecture processes to cross-agency efforts and coordination with external stakeholders by including definitions of architecture technology gaps — essential areas for engagement across and beyond the agency. The technology gaps appendix identifies areas that need attention and innovation to enable future exploration. In publishing this information, NASA communicates the technologies and capabilities that may benefit from partnership with industry, academia, other U.S. government agencies, and international space agencies. Ultimately, NASA established the Moon to Mars Architecture approach to communicate and facilitate humanity’s journey into the universe according to the principles and recurring tenets of NASA’s Moon to Mars Strategy and Objectives. The NASA architecture team thanks their many stakeholders, participants, and partners for their efforts to review and provide feedback. Their support has been critical to the success of this approach.

Elements↗