Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Crew Accommodations”

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.

At least 361 records · Page 20

Plant Growth Research for Food Production: Development and Testing of Expandable Tuber Growth Module

Controlled and reliable growth of a variety of vegetable crops is an important capability for manned deep space exploration systems for providing nutritional supplementation and psychological benefits to crew members. Because current systems have been limited to leafy vegetables that require minimal root space, a major goal for these systems is to increase their ability to grow new types of crops, including tuber plants and root vegetables that require a large root space. An expandable root zone module and housing was developed to integrate this capability into the Veggie growth system. The expandable module uses a waterproof, gas-permeable bag with a structure that allows for root space to increase vertically throughout the growth cycle to accommodate for expanding tuber growth, while minimizing the required media mass. Daikon radishes were chosen as an ideal tuber crop for their subterraneous tuber size and rapid growth cycle, and investigations were done to study expanding superabsorbent hydrogels as a potential growth media. These studies showed improved water retention, but restricted oxygen availability to roots with pure gel media. It was determined that these hydrogels could be integrated in lower proportions into standard soil to achieve media expansion and water retention desired. Using the constructed module prototype and ideal gel and soil media mixture, Daikon radishes were grown in the system to test the capability and success of the system through a full growth cycle.

space↗

Plant Growth Research for Food Production: Development and Testing of Expandable Tuber Growth Module

Controlled and reliable growth of a variety of vegetable crops is an important capability for manned deep space exploration systems for providing nutritional supplementation and psychological benefits to crew members. Because current systems have been limited to leafy vegetables that require minimal root space, a major goal for these systems is to increase their ability to grow new types of crops, including tuber plants and root vegetables that require a large root space. An expandable root zone module and housing was developed to integrate this capability into the Vegetable Production System (Veggie). The expandable module uses a waterproof, gas-permeable bag with a structure that allows for root space to increase vertically throughout the growth cycle to accommodate for expanding tuber growth, while minimizing the required media mass. Daikon radishes were chosen as an ideal tuber crop for their subterraneous tuber size and rapid growth cycle, and investigations were done to study expanding superabsorbent hydrogels as a potential growth media. These studies showed improved water retention, but restricted oxygen availability to roots with pure gel media. It was determined that these hydrogels could be integrated in lower proportions into standard soil to achieve media expansion and water retention desired. Using the constructed module prototype and ideal gel and soil media mixture, daikon radishes are being grown in the system to test the capability and success of the system through a full growth cycle.

food production↗

Mars mission effects on Space Station evolution

The permanently manned Space Station scheduled to be operational in low earth by the mid 1990's, will provide accommodations for science, applications, technology, and commercial users, and will develop enabling capabilities for future missions. A major aspect of the baseline Space Station design is that provisions for evolution to greater capabilities are included in the systems and subsystems designs. User requirements are the basis for conceptual evolution modes or infrastructure to support the paths. Four such modes are discussed in support of a Human to Mars mission, along with some of the near term actions protecting the future of supporting Mars missions on the Space Station. The evolution modes include crew and payload transfer, storage, checkout, assembly, maintenance, repair, and fueling.

Askins, Barbara S.↗

NASA's Space Launch System and Deep Space Opportunities for Smallsats

Overview of the agency’s plans for deep space exploration: NASA has a phased approach to successful human exploration of deep space; We began LEO (Low Earth Orbit), where we’ve lived aboard the ISS continuously for more than 17 years; What have we learned in those years that will help us put boots on the moon with eyes toward Mars? And also help us on Earth? - Advances in materials research - 3D printing in space - Engineered life support systems for sustained stays in space - Better understanding of the effects of microgravity on the human body - We deploy CubeSats from the ISS (International Space Station) - We’ve cooperate with international partners - We’ve opened transportation to LEO to commercial vehicles; Allowing commercial companies to take over LEO frees NASA to explore deep space - next step is back to the Moon; NASA will establish a lunar Gateway near the moon (near rectilinear halo orbit);The Gateway will be crew tended (30-90 day missions); Gateway will communicate with Earth and lunar surface; Will open new opportunities for robotic exploration of the moon, especially far side of the moon and poles; Prospecting for volatiles will be high on the list of priorities; SLS (Space Launch System)/Orion will participate in gateway assembly and operation; Will serve as a testbed for new technologies and inform future Mars missions; After learning how to live and work in deep space like we did in LEO, NASA will move on Mars missions; SLS’s capability to accommodate primary, co-manifested and secondary payloads (when available) is a key component in making this vision a reality.

Bookout, Paul S.↗

Surface Map Traffic Intent Displays and Net-Centric Data-link Communications for NextGen

By 2025, U.S. air traffic is predicted to increase three fold and may strain the current air traffic management system, which may not be able to accommodate this growth. In response to this challenge, a revolutionary new concept has been proposed for U.S. aviation operations, termed the Next Generation Air Transportation System or "NextGen". Many key capabilities are being identified to enable NextGen, including the use of data-link communications. Because NextGen represents a radically different approach to air traffic management and requires a dramatic shift in the tasks, roles, and responsibilities for the flight deck, there are numerous research issues and challenges that must be overcome to ensure a safe, sustainable air transportation system. Flight deck display and crew-vehicle interaction concepts are being developed that proactively investigate and overcome potential technology and safety barriers that might otherwise constrain the full realization of NextGen. The paper describes simulation research, conducted at National Aeronautics and Space Administration (NASA) Langley Research Center, examining data-link communications and traffic intent data during envisioned four-dimensional trajectory (4DT)-based and equivalent visual (EV) surface operations. Overall, the results suggest that controller pilot data-link communications (CPDLC) with the use of mandatory pilot read-back of all clearances significantly enhanced situation awareness for 4DT and EV surface operations. The depiction of graphical traffic state and intent information on the surface map display further enhanced off-nominal detection and pilot qualitative reports of safety and awareness.

Shelton, Kevin J.↗

Evaluation of Mixed-Mode Data-Link Communications for NextGen 4DT and Equivalent Visual Surface Operations

By 2025, U.S. air traffic is predicted to increase 3-fold and may strain the current air traffic management system, which may not be able to accommodate this growth. In response to this challenge, a revolutionary new concept has been proposed for U.S. aviation operations, termed the Next Generation Air Transportation System or NextGen. Many key capabilities are being identified to enable NextGen, including the use of data-link communications. Because NextGen represents a radically different approach to air traffic management and requires a dramatic shift in the tasks, roles, and responsibilities for the flight deck, there are numerous research issues and challenges that must be overcome to ensure a safe, sustainable air transportation system. Flight deck display and crew-vehicle interaction concepts are being developed that proactively investigate and overcome potential technology and safety barriers that might otherwise constrain the full realization of NextGen. The paper describes simulation research examining data-link communications during 4DT and equivalent visual surface operations.

Prinzel, Lawrence J., III↗

Tug and payload-to-Orbiter interface requirements

This paper presents results of a study to identify, evaluate, and develop Tug plus payload-to-Orbiter accommodation requirements. Interface areas include structural, mechanical, fluids, environmental, avionics, and safety. Each interface area was investigated to determine the best physical and operational method of accomplishing the required functions with an overriding goal of establishing sample and flexible interface requirements suitable for Tug, Tug payloads, and other cargo. The recommended system for supporting the Tug and its payload from the Orbiter employs a cylindrical load-carrying structure called a deployment adapter that has a rotational capability for Tug deployment. The design and operation of the deployment adapter and other peripheral interface equipment such as crew compartment monitor and control panels and cargo bay fluid and electrical interface panels are discussed.

Bock, E. H.↗

Suit Port Aft Bulkhead Mockup Test Results and Lessons Learned

The Small Pressurized Rover (SPR) is currently being carried as an integral part of the current Lunar Surface Architectures under consideration in the Constellation program. One element of the SPR is the suit port, the means by which the crew performs Extravehicular Activities (EVAs). Two suit port deliverables were produced in fiscal year 2008: an aft bulkhead mockup for functional integrated testing with the 1-G SPR mockup and a functional and pressurizable engineering unit. This paper focuses on the test results and lessons learned on the aft bulkhead mockup. The suit port aft bulkhead mockup was integrated with the mockup of the SPR cabin and chassis. It is located on the aft bulkhead of the SPR cabin structure and includes hatches, a locking mechanism, seals, interior and exterior suit don/doff aids, and exterior platforms to accommodate different crewmember heights. A lightweight mockup of the Mark III suit was tested with the suit port aft bulkhead mockup. There are several limitations to the suit port and mockup suits, and results of the suit port evaluation are presented and interpreted within the context of the limitations.

Romig, Barbara A.↗

LunaNet Position, Navigation, and Timing Services and Signal, Enabling the Future of Lunar Exploration

The International Space Exploration Coordination Group established in 2018 the 3rd edition of the Global Exploration Roadmap (ISECG, 2018) that aims to achieve Mars human surface activities and identifies the exploration of the Moon as a critical intermediate step. A supplement covering updates on surface exploration scenarios was released in 2020 (ISECG, 2020). The Artemis Accords (NASA Artemis, 2020), first signed in October 2020, now includes over two dozen nations, in an agreement on the principles for best practices, including interoperability. September 2022 introduced the National Aeronautics and Space Administration’s (NASA) Moon to Mars Objectives highlighting recurring tenets of collaboration with international and industry partners and interoperability, along with infrastructure objectives for Position, Navigation, and Timing (PNT). The successful Artemis 1 mission paved the way to the ambitious plans to establish a sustainable human presence on the Moon. Just a few months after Artemis 1 launch (NASA, 2022), iSpace HAKUTO-R Mission1 (iSpace, 2022) launched, being the first-ever commercial mission, launched by a commercial launch service provider, aiming to land on the lunar surface. The NASA Artemis programme plans initial crewed landings and traverses in 2025, supported by the Lunar Gateway, followed by regular launches to build the lunar systems (NASA Artemis Plan, 2020), (NASA, 2022). NASA’s contracts with Commercial Lunar Payload Services (CLPS, (NASA, n.d.)) to deliver science and technology to the Moon, with launches starting in November 2023. The European Space Agency (ESA) Argonaut (ESA Argonaut, 2022) programme plans to have recurrent missions to bring payloads to the lunar surface, supporting lunar exploration. These are just a few examples of planned missions that will target the Earth’s natural satellite in the next decade, with forecasts of tens of missions per year (NSR, 2022), (Euroconsult, 2020). The large number of missions and the complexity of landing and operating are expected to demand a change of paradigm from the current Earth-based communication and navigation services. In recent years, several agencies have proposed to deploy cislunar communication and navigation services to support lunar missions (NASA LCRNS, 2022), (ESA Moonlight, 2022), (JAXA, 2022)). All these proposals seek to deploy service-providing satellites in lunar orbit to ease the user missions’ operations. The PNT services objective is to support all types of lunar users (e.g.: orbiters, landers, ascent vehicles, and surface crew and rovers). At the same time, NASA and ESA initiated an effort to define a common framework to ensure interoperability among different service providers: the LunaNet framework. The LunaNet Interoperability Specification (NASA and ESA, 2023) covers communication, PNT, and auxiliary services, by establishing a common set of requirements to ensure interoperability. This conference contribution will present the LunaNet PNT services, focusing on the Lunar Augmented Navigation Service (LANS) that resembles the Global Navigation Satellite System (GNSS) concept on Earth: constellations of satellites broadcasting a radio navigation signal synchronized to a common reference clock, with augmentations to accommodate users’ needs in an environment away from Earth. This includes a description of the high-level LANS concept and the basic principles defined to ensure interoperability. In addition, it will describe the common S-band PNT Augmented Forward Signal (AFS) and common messages to be adopted for compliance with the LunaNet framework, and the justification of the selected approach.

LunaNet↗

Space transfer concepts and analysis for exploration missions. Implementation plan and element description document (draft final). Volume 6: Lunar systems

NASA's two Office of Space Flight (Code M) Space Transfer Vehicle (STV) contractors supported development of Space Exploration Initiative (SEI) lunar transportation concepts. This work treated lunar SEI missions as the far end of a more near-term STV program, most of whose missions were satellite delivery and servicing requirements derived from Civil Needs Data Base (CNDB) projections. Space Transfer Concepts and Analysis for Exploration Missions (STCAEM) began to address the complete design of a lunar transportation system. The following challenges were addressed: (1) the geometry of aerobraking; (2) accommodation of mixed payloads; (3) cryogenic propellant transfer in Low Lunar Orbit (LLO); (4) fully re-usable design; and (5) growth capability. The leveled requirements, derived requirements, and assumptions applied to the lunar transportation system design are discussed. The mission operations section includes data on mission analysis studies and performance parametrics as well as the operating modes and performance evaluations which include the STCAEM recommendations. Element descriptions for the lunar transportation family included are a listing of the lunar transfer vehicle/lunar excursion vehicle (LTV/LEV) components; trade studies and mass analyses of the transfer and excursion modules; advanced crew recovery vehicle (ACRV) (modified crew recovery vehicle (MCRV)) modifications required to fulfill lunar operations; the aerobrake shape and L/D to be used; and some costing methods and results. Commonality and evolution issues are also discussed.

Source record↗

A Case for Hypogravity Studies Aboard ISS

Future human space exploration missions being contemplated by NASA and other spacefaring nations include some that would require long stays upon bodies having gravity levels much lower than that of Earth. While we have been able to quantify the physiological effects of sustained exposure to microgravity during various spaceflight programs over the past half-century, there has been no opportunity to study the physiological adaptations to gravity levels between zero-g and one-g. We know now that the microgravity environment of spaceflight drives adaptive responses of the bone, muscle, cardiovascular, and sensorimotor systems, causing bone demineralization, muscle atrophy, reduced aerobic capacity, motion sickness, and malcoordination. All of these outcomes can affect crew health and performance, particularly after return to a one-g environment. An important question for physicians, scientists, and mission designers planning human exploration missions to Mars (3/8 g), the Moon (1/6 g), or asteroids (likely negligible g) is: What protection can be expected from gravitational levels between zero-g and one-g? Will crewmembers deconditioned by six months of microgravity exposure on their way to Mars experience continued deconditioning on the Martian surface? Or, will the 3/8 g be sufficient to arrest or even reverse these adaptive changes? The implications for countermeasure deployment, habitat accommodations, and mission design warrant further investigation into the physiological responses to hypogravity. It is not possible to fully simulate hypogravity exposure on Earth for other than transient episodes (e.g., parabolic flight). However, it would be possible to do so in low Earth orbit (LEO) using the centrifugal forces produced in a live-aboard centrifuge. As we're not likely to launch a rotating human spacecraft into LEO anytime in the near future, we could take advantage of rodent subjects aboard the ISS if we had a centrifuge that could accommodate the rodent subjects for extended periods (weeks to months) at various hypogravity levels. Experiments aboard such a centrifuge could provide important insight into human exploration questions and simultaneously answer fundamental questions in gravitational physiology.

Paloski, William H.↗

Integration and use of Microgravity Research Facility: Lessons learned by the crystals by vapor transport experiment and Space Experiments Facility programs

The Crystals by Vapor Transport Experiment (CVTE) and Space Experiments Facility (SEF) are materials processing facilities designed and built for use on the Space Shuttle mid deck. The CVTE was built as a commercial facility owned by the Boeing Company. The SEF was built under contract to the UAH Center for Commercial Development of Space (CCDS). Both facilities include up to three furnaces capable of reaching 850 C minimum, stand-alone electronics and software, and independent cooling control. In addition, the CVTE includes a dedicated stowage locker for cameras, a laptop computer, and other ancillary equipment. Both systems are designed to fly in a Middeck Accommodations Rack (MAR), though the SEF is currently being integrated into a Spacehab rack. The CVTE hardware includes two transparent furnaces capable of achieving temperatures in the 850 to 870 C range. The transparent feature allows scientists/astronauts to directly observe and affect crystal growth both on the ground and in space. Cameras mounted to the rack provide photodocumentation of the crystal growth. The basic design of the furnace allows for modification to accommodate techniques other than vapor crystal growth. Early in the CVTE program, the decision was made to assign a principal scientist to develop the experiment plan, affect the hardware/software design, run the ground and flight research effort, and interface with the scientific community. The principal scientist is responsible to the program manager and is a critical member of the engineering development team. As a result of this decision, the hardware/experiment requirements were established in such a way as to balance the engineering and science demands on the equipment. Program schedules for hardware development, experiment definition and material selection, flight operations development and crew training, both ground support and astronauts, were all planned and carried out with the understanding that the success of the program science was as important as the hardware functionality. How the CVTE payload was designed and what it is capable of, the philosophy of including the scientists in design and operations decisions, and the lessons learned during the integration process are descussed.

Heizer, Barbara L.↗

Servicing capability for the evolutionary Space Station

Since the beginning of the Space Station Freedom (SSF) program the concept of on-orbit servicing of user hardware has been an integral part of the program implementation. The user servicing system architecture has been divided into a baseline and a growth phase. The baseline system consists of the following hardware elements that will support user servicing - flight telerobotic servicer, crew and equipment translation aid, crew intravehicular and extravehicular servicing support, logistics supply system, mobile servicing center, and the special purpose dextrous manipulator. The growth phase incorporates a customer servicing facility (CSF), a station-based orbital maneuvering vehicle and an orbital spacecraft consumables resupply system. The requirements for user servicing were derived from the necessity to service attached payloads, free flyers and coorbiting platforms. These requirements include: orbital replacement units (ORU) and instrument changeout, National Space Transportation System cargo bay loading and unloading, contamination control and monitoring, thermal protection, payload berthing, storage, access to SSF distributed systems, functional checkout, and fluid replenishment. The baseline user servicing capabilities accommodate ORU and instrument changeout. However, this service is limited to attached payloads, either in situ or at a locally adjacent site. The growth phase satisfies all identified user servicing requirements by expanding servicing capabilities to include complex servicing tasks for attached payloads, free-flyers and coorbiting platforms at a dedicated, protected Servicing site. To provide a smooth evolution of user servicing the SSF interfaces that are necessary to accommodate the growth phase have been identified. The interface requirements on SSF have been greatly simplified by accommodating the growth servicing support elements within the CSF. This results in a single SSF interface: SSF to the CSF.

Thomas, Edward F.↗

Facilitating Science--The International Space Station Fluids and Combustion Facility

Scientists in many fields would like to perform experiments on the International Space Station (ISS) to take advantage of the unique environment of microgravity (which is the near-absence of gravity). The ISS will provide the opportunity for scientists to perform microgravity tests over much longer time periods than previously available on the space shuttle--months rather than hours or days--providing more data that could lead to new discoveries. Many of the experiments on ISS will be conducted through the use of new microgravity science facilities. A microgravity science facility is a complete system of on-orbit and ground (on-Earth) hardware, software, operations, and plans that have been optimized to perform sustained microgravity research in one or two scientific disciplines. The facility concept includes hardware that remains on-orbit (because of its general usefulness) and a small amount of unique hardware that is developed for each principal investigator. Such unique hardware customizes the facility to perform a given principal investigator's experiment effectively. Many facilities are planned for the ISS to accommodate scientists' needs. While the quality and quantity of scientific data are being improved, per-experiment costs will be lowered relative to other ways of performing such experiments. The NASA Lewis Research Center is developing a Fluids and Combustion Facility (FCF) to perform microgravity fluids and combustion experiments on the ISS. The FCF will be the lowest cost, most resource efficient approach to performing fluid physics and combustion science experiments on the ISS. Experiments performed in the FCF will be 3 to 9 times less expensive than similar Spacelab experiments. Moreover, use of key ISS resources, such as upmass, power, cooling, and astronaut crew time, will be cut by the same factor.

Winsa, Edward A.↗

Lunanet Position, Navigation, and Timing Services and Signals, Enabling the Future of Lunar Exploration

The International Space Exploration Coordination Group established in 2018 the 3rd edition of the Global Exploration Roadmap (ISECG, 2018) that aims to achieve Mars human surface activities and identifies the exploration of the Moon as a critical intermediate step. A supplement covering updates on surface exploration scenarios was released in 2020 (ISECG, 2020). The Artemis Accords (NASA Artemis, 2020), first signed in October 2020, now includes over two dozen nations, in an agreement on the principles for best practices, including interoperability. In September 2022 the National Aeronautics and Space Administration (NASA) introduced the Moon to Mars Objectives highlighting recurring tenets of collaboration with international and industry partners and interoperability, along with infrastructure objectives for Position, Navigation, and Timing (PNT). The successful Artemis 1 mission paved the way to the ambitious plans to establish a sustainable human presence on the Moon. Just a few months after Artemis 1 launch (NASA, 2022), iSpace HAKUTO-R Mission1 (iSpace, 2022) launched, being the first-ever mission launched by a commercial launch service provider aiming to land on the lunar surface. The NASA Artemis program plans initial crewed landings and surface traverses in 2025, supported by the Lunar Gateway. Regular launches will follow to build the lunar systems for a sustained presence as presented in the Artemis Plan (NASA Artemis Plan, 2020), (NASA, 2022). NASA’s contracts with commercial providers through the Commercial Lunar Payload Services program (CLPS, (NASA, n.d.)) will deliver science and technology demonstration missions to the Moon starting in November 2023. The European Space Agency (ESA) Argonaut (ESA Argonaut, 2022) program plans to have recurrent missions to bring payloads to the lunar surface, supporting lunar exploration. These are just a few examples of planned missions that will target Earth’s natural satellite in the next decade, with forecasts of tens of missions per year (NSR, 2022), (Euroconsult, 2020). The large number of missions and the complexity of landing and operating are expected to demand a change of paradigm from the current Earth-based communication and navigation services, that may be combined with onboard sensors. In recent years, several agencies have proposed to deploy cislunar communication and navigation services to support lunar missions (NASA LCRNS, 2022), (ESA Moonlight, 2022), (JAXA, 2022)). All these proposals seek to deploy service-providing satellites in lunar orbit to ease the user missions’ operations. The PNT services objective is to support all types of lunar users (e.g.: orbiters, landers, ascent vehicles, surface crew, rovers, and deployed science payloads). At the same time, NASA and ESA initiated an effort to define a common framework to ensure interoperability among different service providers: the LunaNet framework. The LunaNet Interoperability Specification (NASA and ESA, 2023) covers communication, PNT, and auxiliary services, by establishing a common set of requirements to ensure interoperability. This conference contribution will present the LunaNet PNT services, focusing on the Lunar Augmented Navigation Service (LANS) that would be provided by a system that resembles the Global Navigation Satellite System (GNSS) concept on Earth: constellations of satellites broadcasting a radio navigation signal synchronized to a common reference clock, with augmentations to accommodate users’ needs in an environment away from Earth. This paper includes a description of the high-level LANS concept, and the basic principles defined to ensure interoperability. In addition, it will describe the common S-band PNT Augmented Forward Signal (AFS) and common messages to be adopted for compliance with the LunaNet framework, and the justification of the selected approach.

LunaNet↗

Mars Entry, Descent, Landing, and Ascent Systems Sensitivities to Landing Site and Atmospheric Dust

Plans for human missions to Mars continue to go through several architectural changes, dating all the way back to the 1950s [1]. The continuous study, reformulation, and refinement of Mars architectures and system concepts is necessary in order to incorporate evolving mission objectives, technology advancements, and growth in the body of knowledge regarding human factors and the various environments of human space travel. This evolution has continued into the 21st century, with architectures concepts such as NASA’s Design Reference Architecture 5.0 in 2009 [2], The Evolvable Mars Campaign in 2016 [3], and as recently as 2020, an architecture focused on a crewed mission as early as the 2030s that aims to minimizing crewed duration and infrastructure investment for the first mission [4]. Within these architectures, numerous studies around the current concept designs for Mars entry, descent, landing, and ascent (EDLA) systems have been performed over the last half a decade [[5], [6], [7], [8], [9], [10]]. Despite the breadth and depth of these studies, landing site, a key design parameter relevant to the design of EDLA systems, has remained nebulous over the years, largely due to the ever evolving mission objectives and architecture concept over the decades. However, the specific landing site has direct impact on the altitude and atmospheric conditions, which subsequently impact the design of EDLA systems. To accommodate the lack of a specific landing site, a baseline reference altitude of 0 km relative to the Mars Orbiter Laser Altimeter (MOLA), which is similar to an Earth sea level reference, has typically been selected and fixed for these past studies. Similarly, a baseline reference atmosphere has typically been utilized in these studies, either the Mars Global Reference Atmospheric Model [11], or a general 1982 standard warm, high pressure atmosphere model derived from Viking lander data [12]. Fig. 1 shows the range of elevations across the surface of Mars. Current architectures are focused on latitudes greater than 30 degrees north in an effort to ensure access to frozen water ice. From the figure, it is quickly evident that elevations over the range of longitudes at or above this latitude are significantly varied between roughly -4 to +4 km MOLA. Based on these observations, initial qualitative assessments of the impacts of landing site elevation on EDLA systems were performed. Fig. 2 depicts the expected trends in EDLA system mass for variations in both land site latitude and elevation. The background coloring is a qualitative evaluation of the current knowledge on ice water availability at the latitudes. Further modeling and simulation was performed to obtain numerical predictions of sensitivities to these parameters. Results indicate up to +2% to -4% mass variation from the current baseline Mars Ascent Vehicle concept, with the potential for greater than 6% mass variation at latitudes greater than 70 degrees north. However, variations in the descent system due to landing site were much more significant with mass variations in the range of -15% to +30% around the current baseline Mars Descent System concept. Additionally, Fig. 3 provides a depiction of potential Mars atmospheric density variations with both dust and Martian season. Though the Martian atmosphere is relatively thin compared to Earth’s atmosphere, it still poses significant impact on the design of EDLA systems. Variations in atmospheric density indicated by this slice of data would have significant impact on the design of EDLA systems. However, due to the highly complex nature of atmospheric flight, a qualitative assessment could not be performed. Rather, sensitivity results relied on modeling and simulation to provide numerical results for sensitivities on the current EDLA design concepts under consideration. Understanding these sensitivities is vital to the overall systems design of a Mars architecture. The resulting mass impacts on EDLA systems, driven by landing site elevation and dust level variations, has rippling impacts throughout the architecture that, ultimately, impact the viability of the architecture. Results showed fairly minor mass impacts to the current Mars Ascent Vehicle baseline configuration, roughly -0.6% to + 0.4% mass variations, while the Mars Descent System say greater variations due to dust, roughly -4% to +6% around the baseline concept.

EDLA↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗