Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “deployment strategy”

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 307 records · Page 17

Space-to-Space Communications System

The Space-to-Space Communications System (SSCS) is an Ultra High Frequency (UHF) Time-Division-Multiple Access (TDMA) system that is designed, developed, and deployed by the NASA Johnson Space Center (JSC) to provide voice, commands, telemetry and data services in close proximity among three space elements: International Space Station (ISS), Space Shuttle Orbiter, and Extravehicular Mobility Units (EMU). The SSCS consists of a family of three radios which are, Space-to-Space Station Radio (SSSR), Space-to-Space Orbiter Radio (SSOR), and Space-to-Space Extravehicular Mobility Radio (SSER). The SSCS can support up to five such radios at a time. Each user has its own time slot within which to transmit voice and data. Continuous Phase Frequency Shift Keying (CPFSK) carrier modulation with a burst data rate of 695 kbps and a frequency deviation of 486.5 kHz is employed by the system. Reed-Solomon (R-S) coding is also adopted to ensure data quality. In this paper, the SSCS system requirements, operational scenario, detailed system architecture and parameters, link acquisition strategy, and link performance analysis will be presented and discussed

Kwei tU↗

Methodology to Define Delivery Accuracy Under Current Day ATC Operations

In order to enable arrival management concepts and solutions in a NextGen environment, ground- based sequencing and scheduling functions have been developed to support metering operations in the National Airspace System. These sequencing and scheduling algorithms as well as tools are designed to aid air traffic controllers in developing an overall arrival strategy. The ground systems being developed will support the management of aircraft to their Scheduled Times of Arrival (STAs) at flow-constrained meter points. This paper presents a methodology for determining the undelayed delivery accuracy for current day air traffic control operations. This new method analyzes the undelayed delivery accuracy at meter points in order to understand changes of desired flow rates as well as enabling definition of metrics that will allow near-future ground automation tools to successfully achieve desired separation at the meter points. This enables aircraft to meet their STAs while performing high precision arrivals. The research presents a possible implementation that would allow delivery performance of current tools to be estimated and delivery accuracy requirements for future tools to be defined, which allows analysis of Estimated Time of Arrival (ETA) accuracy for Time-Based Flow Management (TBFM) and the FAA's Traffic Management Advisor (TMA). TMA is a deployed system that generates scheduled time-of-arrival constraints for en- route air traffic controllers in the US. This new method of automated analysis provides a repeatable evaluation of the delay metrics for current day traffic, new releases of TMA, implementation of different tools, and across different airspace environments. This method utilizes a wide set of data from the Operational TMA-TBFM Repository (OTTR) system, which processes raw data collected by the FAA from operational TMA systems at all ARTCCs in the nation. The OTTR system generates daily reports concerning ATC status, intent and actions. Due to its availability, ease of use, and vast collection of data across several airspaces it was determined that the OTTR data set would be the best method to utilize moving forward with this analysis. The particular variables needed for further analysis were determined along with the necessary OTTR reports, by working closely with the repository team additional analysis reports were developed that provided key ETA and STA information at the freeze horizon. One major benefit of the OTTR data is that using the correct reports the data across several airports could be analyzed over large periods of time. The OTTR data processes the TBFM data daily and is stored in various formats across several airspaces. This allowed us to develop our own parsing methods and raw data processing that would not rely on other computationally expensive tools that perform more in depth analysis of similar sets of data. The majority of this work consisted of the development of the ability to filter flights to create a subset of flights that could be considered undelayed, which is defined as a flight at the freeze horizon with an ETA and STA difference that was minimal or close to zero. This was a broad method that allowed the consideration of a large data set which consisted of all the traffic across a two month period in 2013, the hottest and coldest months, arriving into four airports: George Bush Intercontinental, Denver International, Los Angeles International, and Phoenix Sky Harbor.

delivery accuracy↗

Gateway Program Progress and Overview

This paper provides an overview and status of the Gateway, which will be a small, human-tended space station in orbit around the Moon. The National Aeronautics and Space Administration (NASA) leads the Program and serves as the integrator of the spaceflight capabilities and contributions of U.S. commercial partners and international partners to develop the Gateway. Gateway is the cornerstone of sustainable deep space human exploration and is an essential element of the infrastructure necessary for the execution of the Artemis missions to the Moon. This paper will outline the current planned configuration and deployment of the station, describing the concept of operations and how Gateway supports both lunar surface missions and also serves as the springboard for exploration deeper in space. Calendar year 2022 will see the accomplishments of major milestones such as over twenty systems preliminary design reviews (PDRs), a Program-wide PDR-informed synchronization review, and NASA Key Decision Point marking the evolution of the program as a whole from the formulation phase and into implementation. This paper will provide a progress update for each major component of the Gateway: The Power and Propulsion Element; the Habitation and Logistics Outpost (HALO); Deep Space Logistics; the International Habitation module; the European System Providing Refueling, Infrastructure, and Telecommunications (ESPRIT), which includes a Refueler Module and the HALO Lunar Communications System; External Robotics System; and an Airlock with both science and crew capabilities. For each component, the paper will describe the current maturity of the modules, acquisition strategy, contracts, and if applicable, international partnership status. This paper will also outline the integration function the Gateway Program Office performs at the NASA Johnson Space Center, including the multilateral governance structure and cross-program interfaces across Artemis.

Gateway↗

Performance results of cooperating expert systems in a distributed real-time monitoring system

There are numerous definitions for real-time systems, the most stringent of which involve guaranteeing correct system response within a domain-dependent or situationally defined period of time. For applications such as diagnosis, in which the time required to produce a solution can be non-deterministic, this requirement poses a unique set of challenges in dynamic modification of solution strategy that conforms with maximum possible latencies. However, another definition of real time is relevant in the case of monitoring systems where failure to supply a response in the proper (and often infinitesimal) amount of time allowed does not make the solution less useful (or, in the extreme example of a monitoring system responsible for detecting and deflecting enemy missiles, completely irrelevant). This more casual definition involves responding to data at the same rate at which it is produced, and is more appropriate for monitoring applications with softer real-time constraints, such as interplanetary exploration, which results in massive quantities of data transmitted at the speed of light for a number of hours before it even reaches the monitoring system. The latter definition of real time has been applied to the MARVEL system for automated monitoring and diagnosis of spacecraft telemetry. An early version of this system has been in continuous operational use since it was first deployed in 1989 for the Voyager encounter with Neptune. This system remained under incremental development until 1991 and has been under routine maintenance in operations since then, while continuing to serve as an artificial intelligence (AI) testbed in the laboratory. The system architecture has been designed to facilitate concurrent and cooperative processing by multiple diagnostic expert systems in a hierarchical organization. The diagnostic modules adhere to concepts of data-driven reasoning, constrained but complete nonoverlapping domains, metaknowledge of global consequences of anomalous data, hierarchical reporting of problems that extend beyond a single domain, and shared responsibility for problems that overlap domains. The system enables efficient diagnosis of complex system failures in real-time environments with high data volumes and moderate failure rates, as indicated by extensive performance measurements.

Schwuttke, U. M.↗

Three Years of Airborne Observations During NASA Activate: A Statistical Summary of Chemical, Optical, and Microphysical Aerosol Properties Over the Western North Atlantic Ocean

Airborne observations are critical to understanding Earth’s climate system and surface-level air quality by providing both spatial and vertical information that is not possible through ground measurement networks or satellite observations. Airborne platforms allow assessments of long-range transport, vertical redistribution, boundary-layer dynamics, and cloud-aerosol-interactions that are critical to model evaluation and satellite validation. Still, the high cost and effort of aircraft operations can limit measurement campaigns to short, focused time periods. Multiple deployments are often necessary for seasonal comparisons, and results can be limited if target phenomenon are infrequent. Subsequent analyses typically focus on case studies, especially if deployment conditions are climatologically anomalous. The NASA ACTIVATE (Aerosol Cloud meTeorology Interactions oVer the western ATlantic Experiment) mission was designed to overcome these limitations by operating semi-continuously over multiple months during multiple seasons. Flight plans were intentionally simple, repetitive, and systematic to provide a statistically robust dataset that could be utilized similarly to a ground-network. Here, we present an overview of three years (2020-2022) of aerosol measurements from the NASA HU-25 Falcon aircraft supporting the ACTIVATE mission. Data from 179 flights were considered, the majority of which were based at NASA Langley Research Center and flown locally over the Wester North Atlantic Ocean just east of Hampton, VA, USA. Airmass characteristics tended to transition from continental outflow near the coast to mostly marine over the open ocean. Seasonal, diurnal, spatial, and vertical trends in aerosol microphysical, optical, and chemical properties are discussed in the context of synoptic scale meteorology. Statistical benefits of the ACTIVATE sampling strategy are discussed with regard to future model evaluation.

Luke D Ziemba↗

Assessment of NASA Airborne Laser Altimetry Data Using Ground-Based GPS Data near Summit Station, Greenland

A series of NASA airborne lidars have been used in support of satellite laser altimetry missions. These airbornelaser altimeters have been deployed for satellite instrument development, for spaceborne data validation, and to bridge the data gap between satellite missions. We used data from ground-based Global Positioning System (GPS) surveys of an 11 km long track near Summit Station, Greenland, to assess the surface elevation bias and measurement precision of three airborne laser altimeters including the Airborne Topographic Mapper (ATM), the Land, Vegetation, and Ice Sensor (LVIS), and the Multiple Altimeter Beam Experimental Lidar (MABEL). Ground-based GPS data from the monthly ground-based traverses, which commenced in 2006, allowed for the assessment of nine airborne lidar surveys associated with ATM and LVIS between 2007 and 2016. Surface elevation biases for these altimeters over the flat, ice-sheet interior are less than 0.12 m, while assessments of measurement precision are 0.09 m or better. Ground-based GPS positions determined both with and without differential post-processing techniques provided internally consistent solutions. Results from the analyses of ground-based and airborne data provide validation strategy guidance for the Ice, Cloud, and land Elevation Satellite 2 (ICESat-2) elevation and elevation-change data products.

Summit Station↗

Overview of NASA's Earth Science Data Systems

For over the last 15 years, NASA's Earth Science Enterprise (ESE) has devoted a tremendous effort to design and build the Earth Observing System (EOS) Data and Information System (EOSDIS) to acquire, process, archive and distribute the data of the EOS series of satellites and other ESE missions and field programs. The development of EOSDIS began with an early prototype to support NASA data from heritage missions and progressed through a formal development process to today's system that supports the data from multiple missions including Landsat 7, Terra, Aqua, SORCE and ICESat. The system is deployed at multiple Distributed Active Archive Centers (DAACs) and its current holdings are approximately 4.5 petabytes. The current set of unique users requesting EOS data and information products exceeds 2 million. While EOSDIS has been the centerpiece of NASA's Earth Science Data Systems, other initiatives have augmented the services of EOSDIS and have impacted its evolution and the future directions of data systems within the ESE. ESDIS had an active prototyping effort and has continued to be involved in the activities of the Earth Science Technology Office (ESTO). In response to concerns from the science community that EOSDIS was too large and monolithic, the ESE initiated the Earth Science Information Partners (ESP) Federation Experiment that funded a series of projects to develop specialized products and services to support Earth science research and applications. Last year, the enterprise made 41 awards to successful proposals to the Research, Education and Applications Solutions Network (REASON) Cooperative Agreement Notice to continue and extend the ESP activity. The ESE has also sponsored a formulation activity called the Strategy for the Evolution of ESE Data Systems (SEEDS) to develop approaches and decision support processes for the management of the collection of data system and service providers of the enterprise. Throughout the development of its earth science data systems, NASA has had an active collaboration with a number of interagency and international partners. One of the mechanisms that has been extremely helpful in initiating and promoting this collaboration has been NASA's participation in the Committee on Earth Observation Satellites (CEOS) and its Working Group on Information Systems and Services (WGISS). The CEOS members, working together, have implemented an International Directory Network that enables users to locate collections of earth science data held by the international community and an International Catalog System to search and order specific data products. CEOS WGISS has also promoted the international interest in the Open GIS Consortium s specifications that further advance the access and use of geospatial data and the interoperation of GTS components. These are just a few highlights of the benefits that member agencies gain from CEOS participation.

McDonald, Kenneth↗

Mars 2020 Entry, Descent, and Landing as Observed by Radio Science Techniques at UHF and X-band Frequencies

On February 18, 2021, NASA’s Mars 2020 Rover “Perseverance” conducted the Entry, Descent, and Landing (EDL) sequence to land safely on the surface of Mars at Jezero Crater. Due to the criticality of the EDL sequence, redundant telecommunications strategies were utilized to observe the event. The rover transmitted an X-band (8.4 GHz) signal encoded with Multiple Frequency Shift Keying tones direct-to-Earth and a UHF (401.5 MHz) signal with 8 kbps encoded telemetry to orbiters, which relayed the signal back to Earth at X-band. NASA’s Deep Space Network complexes at Goldstone, California and Madrid, Spain received the direct-to-Earth X-band signal. Two of the largest steerable radio telescopes in the world, the 100-meter Green Bank Telescope in West Virginia and the Effelsberg 100-meter Radio Telescope in Germany also received the UHF carrier signal on Earth. During the EDL event, full spectrum recordings of the UHF and X-band signals were captured at these observatories using open-loop receivers. Real-time and post-processing signal analysis to determine power level, received frequency, and Doppler shift allowed determination of the spacecraft’s health and safety state during critical sequences, including event detection such as atmospheric entry, plasma blackouts, and parachute deployment. Simultaneous observations of the UHF and X-band radio links allow for redundancy in the event of a fault and greatly improve confidence in Doppler event detection.

Gladden, Roy↗

Physical, Ecological, and Societal Indicators for the National Climate Assessment

The National Climate Assessment (NCA) is being conducted under the auspices of the U.S. Global Change Research Program (USGCRP), pursuant to the Global Change Research Act of 1990, Section 106, which requires a report to Congress every 4 years. The current NCA (http://globalchange.gov/what-we-do/assessment/) differs in multiple ways from previous U.S. climate assessment efforts, being: (1) more focused on supporting the Nation s activities in adaptation and mitigation and on evaluating the current state of scientific knowledge relative to climate impacts and trends; (2) a long-term, consistent process for evaluation of climate risks and opportunities and providing information to support decision-making processes within regions and sectors; and (3) establishing a permanent assessment capacity both inside and outside of the federal government. As a part of ongoing, long-term assessment activities, the NCA intends to develop an integrated strategic framework and deploy climate-relevant physical, ecological, and societal indicators. The NCA indicators framework is underdevelopment by the NCA Development and Advisory Committee Indicators Working Group and are envisioned as a relatively small number of policy-relevant integrated indicators designed to provide a consistent, objective, and transparent overview of major variations in climate impacts, vulnerabilities, adaptation, and mitigation activities across sectors, regions, and timeframes. The potential questions that could be addressed by these indicators include: How do we know that there is a changing climate and how is it expected to change in the future? Are important climate impacts and opportunities occurring or predicted to occur in the future? Are we adapting successfully? What are the vulnerabilities and resiliencies given a changing climate? Are we preparing adequately for extreme events? It is not expected that the NCA societal indicators would be linked directly to a single decision or portfolio of decisions, but subsets of indicators, or the data supporting the indicator, might be used to inform decision-making processes such as the development and implementation of climate adaptation strategies in a particular sector or region.

Kenney, Melissa A.↗

Pre-Mission Input Requirements to Enable Successful Sample Collection by a Remote Field/EVA Team

This paper is intended to evaluate the sample collection process with respect to sample characterization and decision making. In some cases, it may be sufficient to know whether a given outcrop or hand sample is the same as or different from previous sampling localities or samples. In other cases, it may be important to have more in-depth characterization of the sample, such as basic composition, mineralogy, and petrology, in order to effectively identify the best sample. Contextual field observations, in situ/handheld analysis, and backroom evaluation may all play a role in understanding field lithologies and their importance for return. For example, whether a rock is a breccia or a clast-laden impact melt may be difficult based on a single sample, but becomes clear as exploration of a field site puts it into context. The FINESSE (Field Investigations to Enable Solar System Science and Exploration) team is a new activity focused on a science and exploration field based research program aimed at generating strategic knowledge in preparation for the human and robotic exploration of the Moon, near-Earth asteroids (NEAs) and Phobos and Deimos. We used the FINESSE field excursion to the West Clearwater Lake Impact structure (WCIS) as an opportunity to test factors related to sampling decisions. In contract to other technology-driven NASA analog studies, The FINESSE WCIS activity is science-focused, and moreover, is sampling-focused, with the explicit intent to return the best samples for geochronology studies in the laboratory. This specific objective effectively reduces the number of variables in the goals of the field test and enables a more controlled investigation of the role of the crewmember in selecting samples. We formulated one hypothesis to test: that providing details regarding the analytical fate of the samples (e.g. geochronology, XRF/XRD, etc.) to the crew prior to their traverse will result in samples that are more likely to meet specific analytical objectives than samples collected in the absence of this premission information. We conducted three tests of this hypothesis. Our investigation was designed to document processes, tools and procedures for crew sampling of planetary targets. This is not meant to be a blind, controlled test of crew efficacy, but rather an effort to recognize the relevant variables that enter into sampling protocol and to develop recommendations for crew and backroom training in future endeavors. Methods: One of the primary FINESSE field deployment objectives was to collect impact melt rocks and impact melt-bearing breccias from a number of locations around the WCIS structure to enable high precision geochronology of the crater to be performed [1]. We conducted three tests at WCIS after two full days of team participation in field site activities, including using remote sensing data and geologic maps, hiking overland to become familiar with the terrain, and examining previously-collected samples from other islands. In addition, the team members shared their projects and techniques with the entire team. We chose our "crew members" as volunteers from the team, all of whom had had moderate training in geologic fieldwork and became familiar with the general field setting. The first two tests were short, focused tests of our hypothesis. Test A was to obtain hydrothermal vugs; Test B was to obtain impact melt and intrusive rock as well as the contact between the two to check for contact metamorphism and age differences. In both cases, the test director had prior knowledge of the site geology and had developed a study-specific objective for sampling prior to deployment. Prior to the field deployment, the crewmember was briefed on the sampling objective and the laboratory techniques that would be used on the samples. At the field sites (Fig. 2), the crewmember was given 30 minutes to survey a small section of outcrop (10-15 m) and acquire a suite of three samples. The crewmember talked through his process and the test director kept track of the timeline in verbal cues to the crewmember. At the conclusion, the team member conducting the scientific study appraised the samples and train of thought. Test C was a 90-minute EVA simulation using two crewmembers working out of line-of-sight in communication with a science backroom. The science objectives were determined by the science backroom team in advance using a Gigapan image of the outcrop (Fig. 1). The science team formulated hypotheses for the outcrop units and created sampling objectives for impact-melt lithologies; the science team turned these into a science plan, which they communicated to the crew in camp prior to crew deployment. As part of the science plan, the science team also discussed their sample needs in depth with the crewmembers, including laboratory methods, objectives, and samples sizes needed. During the deployment, the two crewmembers relayed real-time information to the science backroom by radio with no time delay. Both the crew and science team re-evaluated their hypotheses and science plans in real-time. Discussion: Upon evaluation, we found that the focused tests (Tests A and B) were successful in meeting their scientific objectives. The crewmember used their knowledge of how the samples were to be used in further study (technique, sample size, and scientific need) to focus on the sampling task. The crewmember was comfortable spending minimal time describing and mapping the outcrop. The crewmember used all available time to get a good sample. The larger test was unsuccessful in meeting the sampling objectives. When the crewmembers began describing the lithologies, it was quickly apparent that the lithologies were not as the backroom expected and had communicated to the crew. When the outcrop wasn't as expected, the crew members instinctively switched to field characterization mode, taking significant time to characterize and map the outcrop. One crew member admitted that he "kind of lost track" of the sampling strategy as he focused on the basic outcrop characterization. This is the logical first step in a field geology campaign, that a significant amount of time must be spent by the crew and backroom to understand the outcrop and its significance. Basic field characterization of an outcrop is a focused activity that takes significant time and training [2, 3]. Sampling of representational lithologies can be added to this activity for little cost [4]. However, we have shown that identification of unusual or specific samples for laboratory study also takes significant time and knowledge. We suggest that sampling of this type be considered a separate activity from field characterization, and that crewmembers be trained in sampling needs for different kinds of studies (representative lithologies vs. specialized samples) to acquire a mindset for sampling similar to field mapping. Sampling activities should be given a significant amount of specifically allocated time in scheduling EVA activities; and in the better case, that sampling be done as a second activity to a previously studied outcrop where both crew and backroom are comfortable with its context and characteristics. Our hypothesis posited that crewmember knowledge of how the samples would be used upon return would aid them in choosing relevant samples. Our testing bore this hypothesis out to some extent. We therefore recommend that crewmember training should include exposure to the laboratory techniques and analyses that will be used on the samples to foster this knowledge. There is also the potential for increasing crewmember contextual knowledge real-time in the field through the introduction of in situ geochemical technologies such as field portable XRF. The presence of field portable geochemical technology could enable the astronauts to interrogate the samples for K abundance real-time, ensuring they could collect valuable and dateable samples [5]. Though simulations such as these can teach us a fair bit about decision making processes and timeline building, one EVA participant noted that when he wasn't collecting "real" samples, he wasn't at his best. This effect suggests that higher-fidelity studies involving truly remote participants conducting actual scientific studies merit further attention to capture lessons for application to future crew situations.

sample collection↗

Integration Process for the Habitat Demonstration Unit

The Habitat Demonstration Unit (HDU) is an experimental exploration habitat technology and architecture test platform designed for analog demonstration activities The HDU project has required a team to integrate a variety of contributions from NASA centers and outside collaborators and poses a challenge in integrating these disparate efforts into a cohesive architecture To complete the development of the HDU from conception in June 2009 to rollout for operations in July 2010, a cohesive integration strategy has been developed to integrate the various systems of HDU and the payloads, such as the Geology Lab, that those systems will support The utilization of interface design standards and uniquely tailored reviews have allowed for an accelerated design process Scheduled activities include early fit-checks and the utilization of a Habitat avionics test bed prior to equipment installation into HDU A coordinated effort to utilize modeling and simulation systems has aided in design and integration concept development Modeling tools have been effective in hardware systems layout, cable routing and length estimation, and human factors analysis Decision processes on the shell development including the assembly sequence and the transportation have been fleshed out early on HDU to maximize the efficiency of both integration and field operations Incremental test operations leading up to an integrated systems test allows for an orderly systems test program The HDU will begin its journey as an emulation of a Pressurized Excursion Module (PEM) for 2010 field testing and then may evolve to a Pressurized Core Module (PCM) for 2011 and later field tests, depending on agency architecture decisions The HDU deployment will vary slightly from current lunar architecture plans to include developmental hardware and software items and additional systems called opportunities for technology demonstration One of the HDU challenges has been designing to be prepared for the integration of presently unanticipated systems Results of the HDU field tests will influence future designs of habitat systems.

Gill, Tracy↗

NASA In-Situ Resource Utilization (ISRU) Technology and Development Project Overview

Since the Vision for Space Exploration (VSE) was released in 2004, NASA, in conjunction with international space agencies, industry, and academia, has continued to define and refine plans for sustained and affordable robotic and human exploration of the Moon and beyond. With the goal of establishing a lunar Outpost on the Moon to extend human presence, pursue scientific activities, use the Moon to prepare for future human missions to Mars, and expand Earth s economic sphere, a change in how space exploration is performed is required. One area that opens up the possibility for the first time of breaking our reliance on Earth supplied consumables and learn to live off the land is In-Situ Resource Utilization (ISRU). ISRU, which involves the extraction and processing of space resources into useful products, can have a substantial impact on mission and architecture concepts. In particular, the ability to make propellants, life support consumables, and fuel cell reagents can significantly reduce the cost, mass, and risk of sustained human activities beyond Earth. However, ISRU is an unproven capability for human lunar exploration and can not be put in the critical path of lunar Outpost success until it has been proven. Therefore, ISRU development and deployment needs to take incremental steps toward the desired end state. To ensure ISRU capabilities are available for pre-Outpost and Outpost deployment by 2020, and mission and architecture planners are confident that ISRU can meet initial and long term mission requirements, the ISRU Project is developing technologies and systems in three critical areas: (1) Regolith Excavation, Handling and Material Transportation; (2) Oxygen Extraction from Regolith; and (3) Volatile Extraction and Resource Prospecting, and in four development stages: (I) Demonstrate feasibility; (II) Evolve system w/ improved technologies; (III) Develop one or more systems to TRL 6 before start of flight development; and (IV) Flight development for Outpost. To minimize cost and ensure that ISRU technologies, systems, and functions are integrated properly into the Outpost, technology development efforts are being coordinated with other development areas such as Surface Mobility, Surface Power, Life Support, EVA, and Propulsion. Lastly, laboratory and field system-level tests and demonstrations will be performed as often as possible to demonstrate improvements in: Capabilities (ex. digging deeper); Performance (ex. lower power); and Duration (ex. more autonomy or more robustness). This presentation will provide the status of work performed to date within the NASA ISRU project with respect to technology and system development and field demonstration activities, as well as the current strategy to implement ISRU in future robotic and human lunar exploration missions.

Sanders, Gerald B.↗

Entry, Descent, and Landing Communications for the 2011 Mars Science Laboratory

The Mars Science Laboratory (MSL), established as the most advanced rover to land on the surface of Mars to date, launched on November 26th, 2011 and arrived to the Martian Gale Crater during the night of August 5th, 2012 (PDT). MSL will investigate whether the landing region was ever suitable to support carbon-based life, and examine rocks, soil, and the atmosphere with a sophisticated suite of tools. This paper addresses the flight system requirement by which the vehicle transmitted indications of the following events using both X-band tones and UHF telemetry to allow identification of probable root causes should a mission anomaly have occurred: Heat-Rejection System (HRS) venting, completion of the cruise stage separation, turn to entry attitude, atmospheric deceleration, bank angle reversal commanded, parachute deployment, heatshield separation, radar ground acquisition, powered descent initiation, rover separation from the descent stage, and rover release. During Entry, Descent, and Landing (EDL), the flight system transmitted a UHF telemetry stream adequate to determine the state of the spacecraft (including the presence of faults) at 8 kbps initiating from cruise stage separation through at least one minute after positive indication of rover release on the surface of Mars. The flight system also transmitted X-band semaphore tones from Entry to Landing plus one minute although since MSL was occulted, as predicted, by Mars as seen from the Earth, Direct-To-Earth (DTE) communications were interrupted at approximately is approx. 5 min after Entry ( approximately 130 prior to Landing). The primary data return paths were through the Deep Space Network (DSN) for DTE and the existing Mars network of orbiting assets for UHF, which included the Mars Reconnaissance Orbiter (MRO), Mars Odyssey (ODY), and Mars Express (MEX) elements. These orbiters recorded the telemetry data stream and returned it back to Earth via the DSN. The paper also discusses the total power received during EDL and the robustness of the telecom design strategy used to ensure EDL communications coverage.

relay operations↗

“Are We There Yet?” Can We Biomap the Solar System with Low-Cost Solar Sail Missions?

Abstract: So much of our effort in space exploration has been devoted to one-off missions with major investments in each. This is a great strategy for early investigations of clearly significant planetary and small body destinations, but we have an entire Solar System to interrogate and the pace has definitely been slow to date. We are in the dawning era of much smaller spacecraft, and the potential to gather data from multiple destinations over longer time spans with a heightened cadence of missions to allow us to conduct survey-style investigations of the vast number of objects that attend our particular star. If we think of solar systems as belonging to one of two classes, i.e. life-bearing or not life-bearing, then the presence of some sort of biological or prebiological phenomenon on any individual body in a system places that system in the first category. The emergence of life can then be considered as a solar system-wide property and the entire suite of ingredients and processes that go into kindling of life anywhere within that system is of interest. This ranges from bodies with prebiotic chemistry through to full-blown biospheres. Thus, all bodies in a solar system are part of the milieu within which life occurs. Can the idea of low-cost solar sail-propelled spacecraft deployed en masse be useful for something as hard to investigate as life-like phenomena and their precursors? Perhaps, the answer is yes, and we must give serious attention to the possibilities.

Penelope J Boston↗

Low-Earth Orbit Trajectory Optimization in the Presence of Atmospheric Uncertainty

The previous 20 to 25 years have seen a tremendous increase in space exploration, and with that an increase in the level of logistics planning needed to ensure mission success. For spacecraft that are designed to be periodically re-supplied, a key logistics consumable is propellant, as it constitutes the greatest up-mass on re-supply vehicles. A trajectory design strategy is therefore desired that minimizes propellant usage in order to ease the demand for propellant re-supply missions. This thesis develops such a strategy in three stages, and uses the International Space Station (ISS) as its testbed, as no other LEO spacecraft is more challenging from a space logistics standpoint. First, the ISS trajectory planning problem is formulated as a constrained burn optimization problem assuming a deterministic atmosphere. The cost function is total ∆v, with constraints imposed on longitude of ascending viii node (LAN) and semi-major axis (SMA) altitude. Analytic derivatives are constructed for both the cost and constraints, which are necessary given the 6-week to 2-year time frames being considered. A gradient-based optimizer is then utilized to find locally-optimal solutions to real-world ISS trajectory planning problems. Second, atmospheric uncertainty is addressed by constructing a probabilistic model of space weather data using Gaussian Processes (GPs). Bayesian inference is performed using the GP model to generate mean and covariance estimates for space weather predictions, whose pedigree is assessed against test data. The predictions are then mapped into atmospheric density via the analytic Jacchia-Roberts density model, and the effect of space weather uncertainty on orbital lifetime is examined. Third, an ISS burn execution uncertainty model is developed. This model, along with the space weather uncertainty model, are deployed in a linear covariance analysis to ascertain their combined effect on LAN and SMA altitude dispersions. The deterministic constraints from the original problem are re-formulated as stochastic constraints, where now the constraint uncertainty interval is required to fall within specified bounds. An updated optimization framework is constructed using the original ∆v cost function along with the stochastic constraints to solve the trajectory optimization problem under atmospheric uncertainty. Finally, the complete architecture is summarized for deployment in an operational setting.

Trajectory Optimization↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

NASA Delay Tolerant Networks: Operational, Evolving, an Ready for Expansion

The future of humanity’s presence beyond Earth depends on the successful commercialization of space. For commercialization to succeed, companies need cost-efficient architectures to support their business models and minimize risks for human capital, design, development, and operations. An ongoing challenge to any space enterprise is the reality that terrestrial network technologies are insufficient to provide reliable communications between assets in space. Whether you need to ensure your valuable data is safely transmitted to the ground or reliably delivered between platforms in orbit, ensuring data integrity over intermittent communication links is a necessity. Current solutions to space communications rely heavily on manual recording, storing, and retrieval of data from spacecraft. The current standard in space communication protocols, Consultative Committee for Space Data Systems (CCSDS) Space Packet standard, is reliant on inflexible network architectures based around mission-critical infrastructure to ensure data delivery. However, by automating the recording, storing, retrieval, and verification of data with Delay Tolerant Networks (DTN), the operator is freed from the dependence on manual data management and expensive mission critical infrastructure. NASA has been developing delay tolerant systems since the late 1990’s. Multiple DTN implementations have been established during that time, each suited to different use cases. Most notably, the DTN deployment for the International Space Station (ISS) includes demonstration of two DTN technologies: Interplanetary Overlay Network (ION) and Delay Tolerant Network Marshall Enterprise (DTNME). Beyond ISS, there are even more NASA DTN deployments being considered. Now that DTN implementations are maturing, it is appropriate to reflect upon these decades of work, review the integration and performance of the existing ISS deployment, and explore the future possibilities for DTN deployment industry-wide. The ISS DTN deployment is a complex architecture consisting of different DTN implementations for the onboard and ground network environments. The ION DTN implementation is being used in the on-board network. The Huntsville Operations Support Center (HOSC) DTN implementation, DTNME, is used by the ground network supporting ISS and will soon be a second onboard gateway too. The two implementations work cooperatively to provide high fidelity data services to flight operations users and payload developers across the globe. Though the two implementations yield a quality service, limitations are evident. Data rate, data storage, and device management are constrained by the services themselves and the complex nature of the deployment. Evolution of operations concepts will improve system capabilities and stability, but significant improvement will require additional development to the implementations themselves and to the overall deployment architecture. Taking advantage of the ongoing development and operation of the ISS DTN service will be central to the success of the future evolutions of NASA DTN deployments while demonstrating the benefits of DTN’s low-cost reliable data communication protocols for the growing commercial space industry. A broad effort on DTN integration and support is necessary to promote expansion beyond existing applications. NASA is developing several useful DTN implementations across a number of different systems: ION, DTNME, High-Rate DTN (HDTN), Bundle Protocol Library (BPLib), and others. To prevent fragmentation, DTN implementation teams need to communicate, collaborate, and integrate with one another to build a solid operational foundation for new DTN deployments. The establishment of a group that can assist new DTN users with understanding the purpose of each DTN implementation, provide best practices, and serve as a general knowledge base is paramount. Potential use of DTN on Gateway and other future NASA missions further drives the need for streamlined communication between DTN implementation teams. A well-integrated and highly engaged NASA DTN working group should help provide system architects the best DTN solutions for future commercial space efforts. This paper will first review the history of DTN implementations, explore the shortcoming of current space networking solutions given available limits in technology, and therefore establish the need for Delay Tolerant Networking in space communications. Secondly, the authors will explore NASA’s array of DTN implementations and highlight their usefulness to space applications. Thirdly, this paper will establish general DTN implementation distinguishing factors. Fourthly, the authors will discuss attempts to create a generic DTN comparison matrix, and the authors will review potential future topics in DTN innovation and collaboration, highlighting several key future efforts. Finally, this paper will describe how the institution of a NASA DTN Working Group will benefit DTN adoption across the governmental and commercial space sector. The goal of this paper is to encourage enthusiasm for DTN, share strategies for improving DTN on both current and future applications, promote the collaboration of DTN implementation groups within the international space operations community, and open the conversations about DTN, priorities, complexities, and innovation to the wider spaceflight industry.

DTN↗