SEARCH · Search NASA

Results for “legacy documents”

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 73 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRS2005

Using CFD as a Rocket Injector Design Tool: Recent Progress at Marshall Space Flight Center

New programs are forcing American propulsion system designers into unfamiliar territory. For instance, industry s answer to the cost and reliability goals set out by the Next Generation Launch Technology Program are engine concepts based on the Oxygen- Rich Staged Combustion Cycle. Historical injector design tools are not well suited for this new task. The empirical correlations do not apply directly to the injector concepts associated with the ORSC cycle. These legacy tools focus primarily on performance with environment evaluation a secondary objective. Additionally, the environmental capability of these tools is usually one-dimensional while the actual environments are at least two- and often three-dimensional. CFD has the potential to calculate performance and multi-dimensional environments but its use in the injector design process has been retarded by long solution turnaround times and insufficient demonstrated accuracy. This paper has documented the parallel paths of program support and technology development currently employed at Marshall Space Flight Center in an effort to move CFD to the forefront of injector design. MSFC has established a long-term goal for use of CFD for combustion devices design. The work on injector design is the heart of that vision and the Combustion Devices CFD Simulation Capability Roadmap that focuses the vision. The SRL concept, combining solution fidelity, robustness and accuracy, has been established as a quantitative gauge of current and desired capability. Three examples of current injector analysis for program support have been presented and discussed. These examples are used to establish the current capability at MSFC for these problems. Shortcomings identified from this experience are being used as inputs to the Roadmap process. The SRL evaluation identified lack of demonstrated solution accuracy as a major issue. Accordingly, the MSFC view of code validation and current MSFC-funded validation efforts were discussed in some detail. The objectives of each effort were noted. Issues relative to code validation for injector design were discussed in some detail. The requirement for CFD support during the design of the experiment was noted and discussed in terms of instrumentation placement and experimental rig uncertainty. In conclusion, MSFC has made significant progress in the last two years in advancing CFD toward the goal of application to injector design. A parallel effort focused on program support and technology development via the SCIT Task have enabled the progress.

Tucker, Kevin↗

NASA NTRS2005

Exploring Diverse Data Sets and Developing New Theories and Ideas With Project Integration Architecture

The development of new ideas is the essence of scientific research. This is frequently done by developing models of physical processes and comparing model predictions with results from experiments. With models becoming ever more complex and data acquisition systems becoming more powerful, the researcher is burdened with wading through data ranging in volume up to a level of many terabytes and beyond. These data often come from multiple, heterogeneous sources and usually the methods for searching through it are at or near the manual level. In addition, current documentation methods are generally limited to researchers pen-and-paper style notebooks. Researchers may want to form constraint-based queries on a body of existing knowledge that is, itself, distributed over many different machines and environments and from the results of such queries then spawn additional queries, simulations, and data analyses in order to discover new insights into the problem being investigated. Currently, researchers are restricted to working within the boundaries of tools that are inefficient at probing current and legacy data to extend the knowledge of the problem at hand and reveal innovative and efficient solutions. A framework called the Project Integration Architecture is discussed that can address these desired functionalities.

Benyo, Theresa L.↗

NASA NTRS2015

Survey of Verification and Validation Techniques for Small Satellite Software Development

The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation.

Small Satellite Technology↗

NASA NTRSDate not supplied

Fostering Better Collaboration in Software Development Cycles Between Scientists and Programmers to Ensure the Integrity of and Promote the Development of New Scientific Data Products.

Misaligned incentives lead to reduced interaction between scientists and programmers on modern NASA science data-product development teams. Typically, situations arise where the scientist is not incentivized to learn modern coding practices and the programmer does not understand the science algorithms in the code. A programmer is responsible for the deliverable code thus setting a tradeoff between the desire for code improvement versus fear of compromising the integrity of data-product while the scientist continues to rely on their legacy codebases owing to the complexity of using the delivered code outside the processing environment and lack of validation modules. The NASA/CERES-TISA project has adopted a collaborative approach, with scientists and programmers both utilizing the same software repository with multiple branches, some optimized for delivery to a processing datacenter and others for scientific product development and validation. A team of scientists and programmers jointly review any new science code updates for integration into the codebase and strive to improve practices through promoting algorithm understanding, better institutional knowledge exchange and documentation, modularization, and developing data processing flow-dictated validation and debugging methods. This leads to a reduction in the personnel single point failures and reduced development time for creation of new science data-products.

CERES↗

NASA NTRSDate not supplied

Training Artemis Astronauts to Explore the Moon

To prepare for human exploration of the Moon in the mid-2020s, NASA is developing a program to provide geoscience and planetary science classroom training and geologic eld training to astronauts and other mission personnel. The Artemis geoscience training plan builds on a long legacy: NASA has trained astronauts in geology, planetary science, and geological eld work for more than 50 years. From ~1965-1972, the geology focus for astronauts included orbital Earth observations during the early NASA missions, but the endgame was preparation for the Apollo missions to the Lunar surface [see Phinney (2015), NASA-SP-2015-626; Lofgren et al.(2011);Schmitt, et al. (2011); and El Baz (2011), all from GSA SP483]. From the mid 1970s through2017, the primary purpose for geoscience training was to prepare astronauts to observe theEarth and document a wide variety of Earth processes from orbital platforms (Skylab, SpaceShuttle and International Space Station). Astronaut observations of Earth from the InternationalSpace Station remain an important activity today, but the prospect of exploration of the lunar surface through the Artemis Program lends additional purpose to the geoscience content and eld experiences that we provide the astronauts. We recently completed the geology and eld training with Astronaut Class 22 and are now planning both focused eld exercises and simulations for future Artemis crews, as well as the accompanying classroom lessons on lunar and planetary sciences. The training we offer extends beyond the astronaut office – we partner across operational and engineering organizations at NASA and provide eld work exercises and opportunities to personnel in the Flight Operations Directorate (responsible for the overall training and certification), as well as the exploration Extravehicular Activity Oce (developing spacewalk suits and tools). These partnerships contribute to building a common language and sense of purpose, and also help to ensure that NASA’s geoscience training and science operations are fully integrated with the teams and systems responsible for getting the next generation of astronauts to the surface of the Moon.

Artemis↗

NASA NTRS2002

Range Information Systems Management (RISM) Phase 1 Report

RISM investigated alternative approaches, technologies, and communication network architectures to facilitate building the Spaceports and Ranges of the future. RISM started by document most existing US ranges and their capabilities. In parallel, RISM obtained inputs from the following: 1) NASA and NASA-contractor engineers and managers, and; 2) Aerospace leaders from Government, Academia, and Industry, participating through the Space Based Range Distributed System Working Group (SBRDSWG), many of whom are also; 3) Members of the Advanced Range Technology Working Group (ARTWG) subgroups, and; 4) Members of the Advanced Spaceport Technology Working Group (ASTWG). These diverse inputs helped to envision advanced technologies for implementing future Ranges and Range systems that builds on today s cabled and wireless legacy infrastructures while seamlessly integrating both today s emerging and tomorrow s building-block communication techniques. The fundamental key is to envision a transition to a Space Based Range Distributed Subsystem. The enabling concept is to identify the specific needs of Range users that can be solved through applying emerging communication tech

Bastin, Gary L.↗

NASA NTRSDate not supplied

An assessment of the impact of system spectral response parameters on spectral shape and algal bloom detection for the GeoXO ocean color instrument (OCX)

NOAA’s Geostationary Extended Observations (GeoXO) program is planning to include a hyperspectral ocean color instrument (OCX) in geostationary orbit slated for operations by the early 2030s. Shared international focus has led to a diverse legacy of space-based remote sensing ocean color missions that have and will continue to provide ocean color products into the future at a variety of spatial, temporal, and spectral resolutions. This work reports on an investigation of the impacts of system spectral response parameters on spectral shape and algal bloom detection for the planned OCX instrument. A large dataset in-situ spectra, from a variety of locations and water cases collected with an above water spectrometer, was used to simulate OCX observations of varying system spectral response parameters. The OCX Performance Operational Requirements Document (PORD) level spectral resolution and sampling are varied concurrently and the location of band centers is varied independently. The impacts to the spectral shape using hyperspectral signature analysis, as well as the impacts to two heritage multispectral algal bloom detection algorithms – red band difference (RBD) and Karenia brevis bloom index (KBBI) – are assessed considering both changes in resolution/sampling and band center location. This work provides a quantitative assessment of the impacts of system spectral response requirements on both the spectral shape of observations as well as the algal bloom detection to provide insight on how various instrument performance parameters influence science and operational utility of OCX.

Monica Cook↗

NASA NTRSDate not supplied

Genesis Solar Wind – Capture, Return, Curate and Analyze: Looking Backward and Creating a Timeline

Introduction: In 1997 NASA’S Discovery Program selected the Genesis mission proposal to return solar wind samples to Earth for laboratory analyses. Principal Investigator Donald S. Burnett and the science team defined the purity of collector materials and ability to analyze solar wind composition to the precision required for planetary science. As a small mission, focused on a well-defined science goal, yet needing careful attention to engineering details, the communication among scientists and engineers, nurtured by Don Burnett, was exceptional. Genesis Mission and Curation Legacy: Genesis, as the first U. S. spacecraft to return astromaterial samples since Apollo, not only integrated the mission planning and flight teams, but also the science and sample curation teams during the mission development period. Since Genesis is a sample return mission, the Science Team was essential in certifying the collectors (sample containers for solar atoms). From inception, Genesis established mission funding for returned sample curation. JSC was lead in contamination control during mission preparation, including establishment of an ISO 4 cleanroom facility and use of ultrapure water (UPW) for cleaning flight hardware (and, as it turned out, for cleaning collectors after the mishap). Reliable, fast communication among scientists, engineers and curators at the hands-on level established deep respect among team members and efficient decision-making. JSC’s 50-years of astromaterial sample curation provided experienced sample processors onsite during recovery in Utah (a deep bench for emergency response). Post-recovery curation included iterative collaboration with science sample users to clean or verify cleanliness of samples. The science legacy from Genesis is addressed by Burnett and Jurewicz, this volume. In The Beginning: After Apollo sample return, Burnett and Marcia Neugebauer at JPL began discussing a solar wind sample return, with Neugebauer arguing that separate collection of solar wind regimes was essential science. By 1992 a solar wind sample return mission was presented at a workshop, and by 1994 a mission was proposed named Suess-Urey. The mission was re-proposed under a new name GENESIS and selected in 1997. Susan Niebur captured the Genesis mission history and stories, from high level management documents and from many interviews with participants [2]. Her account lets readers glimpse personality of participants in quotations from interviews. Need and Scope for Detailed Technical Timeline: A timeline constructed from lower level task documents has been initiated to document the resources and skills actually used, as well as task sequence or concurrency. Timelines for high level mission events are captured in two documents [1] [2] and for detailed re-entry events in [3]. A detailed technical timeline for Genesis mission and curation activities will provide data points for lower level tasks, such as ISO 4 curation facility construction time, preparation for nominal sample field recovery, mishap recovery, and UPW expansion. Changes in technology context 1990-2024: Semiconductor technologies were easily accessible in the U.S.A. (1990-1999), and the Genesis team used those resources for cleanroom design and UPW system expansion. Image documentation was changing from film to digital during cleanroom construction and payload cleaning (1997-2001). Engineering design was done using computer aided design proprietary software, making more difficult the archiving of payload configuration and materials. Email of documents, tracked delivery service and virtual meeting capability greatly improved communication efficiency. Information sources – Pre-launch mission preparation: Examples of mission science, engineering and contamination control are collector purity testing, payload design/fabrication and ISO 4 cleanroom construction. Information on timing of these activities comes from facility readiness reviews, management reviews, shipping documents, procurement documents, test reports, travel documents, laboratory logs, Quality Assurance documents, dates on images, participant notebooks and emails. Information sources – Sample return re-entry and field recovery activities: Information comes from event timelines produced by Mid-Air Recovery team, Lockheed team lead notes and from chase video, JPL Quality Assurance. Information also comes from images and logbooks from UTTR cleanroom operations and from curatorial documents. Information sources – Resulting science and sample cleaning processes: Agendas from the annual gatherings of the science team initially trace testing for collector purity/cleanliness, and after sample recovery, include collector cleaning and cleanliness assessment. Post-recovery documents include curatorial orders and procedures, sample allocation documents and LPSC abstracts. Timeline Objectives: A simple spreadsheet timeline with headers DATE, EVENT, PEOPLE, COMMENT, INFORMATION SOURCE has been initiated and currently has over 90 entries. While this is not definitive historical research, it is a quick look at the evolution of Genesis curation with pointers to documents or people with information. Engineers for future missions may find useful points of comparison for development of facilities. References:[1] Genesis Mission Reference Document, (2011) JPL D-62382.[2] Niebur S. M., edited by Brown D. W. (2023) NASA’s Discovery Program: The First 20 Years of Competitive Planetary Exploration, NASA-SP-2023-4238.[3] Genesis Mishap Investigation Board Report, Vol. 1 (July 2005).

solar wind↗

NASA NTRS2019

Airspace Technology Demonstration 3 (ATD-3): Dynamic Routes for Arrivals in Weather (DRAW) Technology Transfer Document Summary Version 2.0

Airspace Technology Demonstration – 3 (ATD-3) is part of NASA’s Airspace Operations and Safety Program (AOSP) – specifically, its Airspace Technology Demonstrations (ATD) Project. ATD-3 is a multi-year research and development effort which proposes to develop and demonstrate automation technologies and operating concepts that enable air navigation service providers and airspace users to continuously assess weather, winds, traffic, and other information to identify, evaluate, and implement workable opportunities for flight plan route corrections that can result in significant flight time and fuel savings in en route airspace. In order to ensure that the products of this tech-transfer are relevant and useful, NASA has created strong partnerships with the FAA and key industry stakeholders. This summary document and accompanying technology artifacts satisfy the third Research Transition Product (RTP) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan, which is Dynamic Routes for Arrivals in Weather (DRAW). This technology transfer consists of artifacts for DRAW Arrival Metering (AM) Operations delivered in June 2018, DRAW AM updates, and DRAW Extended Metering (XM) Operations. Blue highlighting indicates the new or modified deliverables. Some of the artifacts in this technology transfer have distribution restrictions that need to be followed. Distribution information is noted in each section. DRAW is a trajectory-based system that combines the legacy Dynamic Weather Routes (DWR) weather avoidance technology with an arrival-specific rerouting algorithm and arrival scheduler to improve traffic flows on weather-impacted arrival routes into major airports. First, DRAW identifies flights that could be rerouted to more efficient Standard Terminal Arrival Routes (STARs) that may have previously been impacted by weather. Second, when weather is impacting the arrival routing, DRAW proposes simple arrival route corrections that enable aircraft to stay on their flight plan while avoiding weather. The DRAW system proposes reroutes early enough to allow Time Based Flow Management (TBFM) to make the necessary schedule adjustments. As a result, metering operations can be sustained longer and more consistently in the presence of weather because the arrival schedule accounts for the dynamic routing intent of arrival flights to deviate around weather. The first DRAW tech transfer in June 2018 focused on arrival metering operations with the DRAW algorithm implemented in the NASA Center TRACON Automation System (CTAS) automation software. This tech transfer delivery includes updates for DRAW implemented in FAA’s TBFM 4.7 automation software and preliminary research into DRAW for XM operations.

Isaacson, Douglas R.↗

NASA NTRSDate not supplied

An Initial Assessment of the Impact of System Spectral Response Parameters on Driving Ocean Color Applications for the GeoXO Ocean Color Instrument (OCX)

NOAA’s Geostationary Extended Observations (GeoXO) program is planning to include a hyperspectral ocean color instrument (OCX) in geostationary orbit slated for operations by the early 2030s. Shared international focus has led to a diverse legacy of space-based remote sensing ocean color missions that have and will continue to provide ocean color products into the future at a variety of spatial, temporal, and spectral resolutions. This work reports on an investigation of the impacts of system spectral response parameters on spectral shape and algal bloom detection for the planned OCX instrument. A dataset of high resolution (1 nm spectral sampling) in-situ spectra of red tide collected with an above water spectrometer, and associated K. brevis cell concentrations, were used to simulate OCX observations of varying system spectral response parameters. The OCX Performance Operational Requirements Document (PORD) level spectral resolution and sampling are varied concurrently and the location of band centers is varied independently. The impacts to the spectral shape using hyperspectral signature analysis, as well as the impacts to two heritage multispectral algal bloom detection algorithms – red band difference (RBD) and Karenia brevis bloom index (KBBI) – are assessed considering both changes in resolution/sampling and band center location. This work provides a quantitative assessment of the impacts of system spectral response requirements on both the spectral shape of observations as well as the algal bloom detection to provide insight on how various instrument performance parameters influence science and operational utility of OCX. Future work will seek to expand this analysis to include a larger dataset that considers additional water cases.

Monica Cook↗

NASA NTRSDate not supplied

An Initial Assessment of the Impact of System Spectral Response Parameters on Driving Ocean Color Applications for the GeoXO Ocean Color Instrument (OCX)

NOAA’s Geostationary Extended Observations (GeoXO) program is planning to include a hyperspectral ocean color instrument (OCX) in geostationary orbit slated for operations by the early 2030s. Shared international focus has led to a diverse legacy of space-based remote sensing ocean color missions that have and will continue to provide ocean color products into the future at a variety of spatial, temporal, and spectral resolutions. This work reports on an investigation of the impacts of system spectral response parameters on spectral shape and algal bloom detection for the planned OCX instrument. A dataset of high resolution (1 nm spectral sampling) in-situ spectra of red tide collected with an above water spectrometer, and associated K. brevis cell concentrations, were used to simulate OCX observations of varying system spectral response parameters. The OCX Performance Operational Requirements Document (PORD) level spectral resolution and sampling are varied concurrently and the location of band centers is varied independently. The impacts to the spectral shape using hyperspectral signature analysis, as well as the impacts to two heritage multispectral algal bloom detection algorithms – red band difference (RBD) and Karenia brevis bloom index (KBBI) – are assessed considering both changes in resolution/sampling and band center location. This work provides a quantitative assessment of the impacts of system spectral response requirements on both the spectral shape of observations as well as the algal bloom detection to provide insight on how various instrument performance parameters influence science and operational utility of OCX. Future work will seek to expand this analysis to include a larger dataset that considers additional water cases.

M. Cook↗

NASA NTRS2016

Preserving, Enhancing, and Continuing the Scientific Legacy of the Apollo Sample Suite

From 1969 to 1972, Apollo astronauts collected 382 kg of rocks, soils, and core samples from six geologically diverse locations on the Moon. In the nearly 50 years since the samples were collected, over 3000 different studies have been conducted using the nearly 2200 different Apollo samples. Despite the maturity of the sample collection, many new studies of lunar samples are undertaken each year, with an average of more than 55 requests and more than 600 distinct subsamples allocated annually over the past five years. The Apollo samples are a finite resource, however. Although new studies are encouraged, it is important that new studies do not duplicate previous studies, and where possible, leverage previous results to inform and enhance the current studies. This helps to preserve the samples and scientific funding, both of which are precious resources. We have initiated several new efforts to rescue some of the early analyses from these samples, including unpublished analytical data. We are actively scanning NASA documentation in paper form that is related to the Apollo missions and sample processing, and we are collaborating with IEDA to establish a geochemical data base called MoonDB. To populate this database, we are actively working with about a dozen prominent lunar PIs to organize and transcribe years of both published and unpublished data, making it available to all researchers. This effort will also take advantage of new online analytical tools like PetDB. There have already been tangible results from the MoonDB data rescue effort. A pilot project involving the rescue of geochemical data of John Delano on Apollo pyroclastic glasses has already been referenced in multiple Apollo sample requests, and in fact, the compiled data was used as part of one of the new studies. Similarly, scanned sample handling reports have been utilized to find previously analyzed samples that were appropriate to fulfill new sample requests. We have also begun to image the Apollo samples using (1) micro‐CT scanning to document the interior structure of samples, and (2) comprehensive high resolution photography of samples, enabling high resolution 3D reconstructions of the samples. Both efforts will provide comprehensive access to these samples and allow for more targeted requests, and thus better curation of the samples for decades to come.

Zeigler, Ryan↗

NASA NTRS2009

The Urban Environmental Monitoring/100 Cities Project: Legacy of the First Phase and Next Steps

The Urban Environmental Monitoring (UEM) project, now known as the 100 Cities Project, at Arizona State University (ASU) is a baseline effort to collect and analyze remotely sensed data for 100 urban centers worldwide. Our overarching goal is to use remote sensing technology to better understand the consequences of rapid urbanization through advanced biophysical measurements, classification methods, and modeling, which can then be used to inform public policy and planning. Urbanization represents one of the most significant alterations that humankind has made to the surface of the earth. In the early 20th century, there were less than 20 cities in the world with populations exceeding 1 million; today, there are more than 400. The consequences of urbanization include the transformation of land surfaces from undisturbed natural environments to land that supports different forms of human activity, including agriculture, residential, commercial, industrial, and infrastructure such as roads and other types of transportation. Each of these land transformations has impacted, to varying degrees, the local climatology, hydrology, geology, and biota that predate human settlement. It is essential that we document, to the best of our ability, the nature of land transformations and the consequences to the existing environment. The focus in the UEM project since its inception has been on rapid urbanization. Rapid urbanization is occurring in hundreds of cities worldwide as population increases and people migrate from rural communities to urban centers in search of employment and a better quality of life. The unintended consequences of rapid urbanization have the potential to cause serious harm to the environment, to human life, and to the resulting built environment because rapid development constrains and rushes decision making. Such rapid decision making can result in poor planning, ineffective policies, and decisions that harm the environment and the quality of human life. Slower, more thought-out, decision making could result in more favorable outcomes. The harm to the environment includes poor air quality, soil erosion, polluted rivers and aquifers, and loss of wildlife habitat. Human life is then threatened because of increased potential for disease spreading, human conflict, environmental hazards, and diminished quality of life. The built environment is potentially threatened when cities are built in areas that can be impacted by events such as hurricanes, tsunamis, earthquakes, fires, and landslides. Our goals include assessing the threat of such events on cities and the people living there.

Stefanov, William L.↗

NASA NTRSDate not supplied

Natural Language Processing Analysis of Notices to Airmen for Air Traffic Management Optimization

With new emerging technologies in the field of NLP, we explore their applications to digitize and analyze heritage Air Traffic Management (ATM) documents for planning and optimizing airspace operations. Specifically, this research focuses on harvesting semi-structured or un-structured information contained in Notices to Airmen (NOTAMs). Using NLP and other advanced data analytics, we will construct a data-driven framework which facilitates finding language patterns and the use of pretrained language models for classification and extraction of useful airspace constraints and restrictions. These may lead to tools that assist airspace users in understanding the constraints more efficiently, contributing to better route planning and safer execution. This paper explores three workflows entailing different NLP tasks. First, unsupervised techniques like word embedding and topic modeling are used for pattern finding and document classification. Second, a dataset is created by extracting information from the semi-structured NOTAM format as metadata for categorizing, visualizing, and extracting key entities driving NOTAM content. Third, modern pre-built deep learning based transformer models such as BERT, RoBERTa, and XLNet are evaluated on the question answering task, an even more robust approach to information extraction, as well as their respective fine-tuning tasks. In this work we include various performance metrics for the trained models to evaluate both accuracy and precision and we show that the models can be generalized for their respective tasks. The research work developed shows promise in uncovering trends in digital NOTAMs in the NAS and also offers a new framework for digitizing and inferring insights from free-form legacy NOTAMs, that are yet to be digitized.

Natural Language Processing↗

NASA NTRSDate not supplied

Natural Language Processing (NLP) Analysis of NOTAMs for Air Traffic Management Optimization

Natural Language Processing↗

NASA NTRS2008

Modifying the Heliophysics Data Policy to Better Enable Heliophysics Research

The Heliophysics (HP) Science Data Management Policy, adopted by HP in June 2007, has helped to provide a structure for the HP data lifecycle. It provides guidelines for Project Data Management Plans and related documents, initiates Resident Archives to maintain data services after a mission ends, and outlines a route to the unification of data finding, access, and distribution through Virtual observatories. Recently we have filled in missing pieces that assure more coherence and a home for the VxOs (through the 'Heliophsyics Data and Model Consortium'), and provide greater clarity with respect to long term archiving. In particular, the new policy which has been vetted with many community members, details the 'Final Archives' that are to provide long-term data access. These are distinguished from RAs in that they provide little additional service beyond servicing data, but critical to their success is that the final archival materials include calibrated data in useful formats such as one finds in CDAWeb and various ASCII or FITS archives. Having a clear goal for legacy products, to be detailed as part of the Mission Archives Plans presented at Senior Reviews, will help to avoid the situation so common in the past of having archival products that preserve bits well but not readily usable information. We hope to avoid the need for the large numbers of 'data upgrade' projects that have been necessary in recent years.

Hayes, Jeffrey↗

NASA NTRS2017

Smashing the Stovepipe: Leveraging the GMSEC Open Architecture and Advanced IT Automation to Rapidly Prototype, Develop and Deploy Next-Generation Multi-Mission Ground Systems

Satellite/Payload Ground Systems - Typically highly-customized to a specific mission's use cases - Utilize hundreds (or thousands!) of specialized point-to-point interfaces for data flows / file transfers Documentation and tracking of these complex interfaces requires extensive time to develop and extremely high staffing costs Implementation and testing of these interfaces are even more cost-prohibitive, and documentation often lags behind implementation resulting in inconsistencies down the road With expanding threat vectors, IT Security, Information Assurance and Operational Security have become key Ground System architecture drivers New Federal security-related directives are generated on a daily basis, imposing new requirements on current / existing ground systems - These mandated activities and data calls typically carry little or no additional funding for implementation As a result, Ground System Sustaining Engineering groups and Information Technology staff continually struggle to keep up with the rolling tide of security Advancing security concerns and shrinking budgets are pushing these large stove-piped ground systems to begin sharing resources - I.e. Operational / SysAdmin staff, IT security baselines, architecture decisions or even networks / hosting infrastructure Refactoring these existing ground systems into multi-mission assets proves extremely challenging due to what is typically very tight coupling between legacy components As a result, many "Multi-Mission" ops. environments end up simply sharing compute resources and networks due to the difficulty of refactoring into true multi-mission systems Utilizing continuous integration / rapid system deployment technologies in conjunction with an open architecture messaging approach allows System Engineers and Architects to worry less about the low-level details of interfaces between components and configuration of systems GMSEC messaging is inherently designed to support multi-mission requirements, and allows components to aggregate data across multiple homogeneous or heterogeneous satellites or payloads - The highly-successful Goddard Science and Planetary Operations Control Center (SPOCC) utilizes GMSEC as the hub for it's automation and situational awareness capability Shifts focus towards getting GS to a final configuration-managed baseline, as well as multi-mission / big-picture capabilities that help increase situational awareness, promote cross-mission sharing and establish enhanced fleet management capabilities across all levels of the enterprise.

GMSEC↗

NASA NTRS2026

Moon Base Transportation - Deliveries to the Lunar Surface

Development of the Moon Base will enable a home away from home for astronauts who will live and work at humanity’s first lunar outpost. In this effort, NASA’s Moon Transportation Office is responsible for enabling the transformational missions required to deliver habitats, supplies, science payloads, and all other elements needed to cultivate a permanent presence on the Lunar Surface. The Mission Concept (MC) is characterized through evaluation of an end-to-end architecture that can successfully deliver a generalized heavy large-volume payload, in excess of 4000 kg, to a precision landing and touchdown on the lunar surface. The mission architecture utilizes a single launch configuration of a Lunar Lander (LL) with a unique propellant system. The LL has an integral orbital transfer capability and features jettisonable elements. The design circumvents the need for prop transfer on orbit and multiple launch configurations. The launch vehicle (LV) for this work will assume the capability to deliver a payload in excess of 40,000 kg to orbit, affording multiple LV solutions. Considerations for the LL and payload deployment from the fairing are assumed to be handled through compliance with a launch providers’ Interface Requirements Document (IRD). The MC will span from launch at Kennedy Space Center (KSC) to terminal descent and touchdown on the lunar surface, requiring a total ΔV on the order of 6 km/s beyond what is required to get the vehicle stack to a 200 km circular Low Earth Orbit (LEO). Major mission phases include: launch and launch vehicle separation, transfer operations, pre-landing navigation, and lunar descent and touchdown. A Concept of Operations (ConOps) is used as the primary design driver for defining architecture of the vehicles necessary to achieve final payload delivery. Numerous ground rules and assumptions will be provided for each phase of the mission. Concept designs for the LL is presented. An emphasis of the design maximizes a feasible path for maturation, manufacturing, and operation. A self-imposed practical consideration for this effort is the incorporation of legacy designed hardware to minimize expensive, time-intensive, and high-risk hardware development cycles. The propulsion system of the LL adopts a conventional storable bipropellant configuration of monomethyl hydrazine (MMH) and mixed oxides of nitrogen (MON3). This effort will showcase a unique propellant delivery system to minimize the reliance on propellant management devices (PMDs) during descent. Numerous key constraints have been considered, across the multiple segments of the mission. These include the unique aspects of center of gravity (CG) management, thruster plume effects including self-impingement, propulsion system hardware limitations, navigation during multiple mission phases, and landing gear geometry for uneven terrain. These constraints shape the trades necessary for precision landing of heavy cargo and ensure compatibility with broader Moon Base Transportation concepts. The resulting insights inform future transportation strategies for the Moon and beyond; directly contributing to the development of cargo‑delivery standards that will support the long‑term buildup of a sustainable, continuously inhabited Moon Base.

Lunar Habitat↗