Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “RECOMMENDATIONS”

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 721 records · Page 40

Medical Data Architecture Platform and Recommended Requirements for a Medical Data System for Exploration Missions

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically- relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions. In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Medical Data Architecture Platform and Recommended Requirements for A Medical Data System for Exploration Missions

Minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically relevant information to support medical operations during exploration missions. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm of medical data management on the International Space Station. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products derived from the third MDA prototype development will directly inform exploration medical system requirements for Level of Care IV in Gateway missions.In fiscal year 2019, the MDA project developed Test Bed 3, the third iteration in a series of prototypes, that featured integrations with cognition tool data, ultrasound image analytics and core Flight Software (cFS). Maintaining a layered architecture design, the framework implemented a plug-in, modular approach in the integration of these external data sources. An early version of MDA Test Bed 3 software was deployed and operated in a simulated analog environment that was part of the Next Space Technologies for Exploration Partnerships (NextSTEP) Gateway tests of multiple habitat prototypes. In addition, the MDA team participated in the Gateway Test and Verification Demonstration, where the MDA cFS applications was integrated with Gateway-in-a-Box software to send and receive medically relevant data over a simulated vehicle network. This software demonstration was given to ExMC and Gateway Program stakeholders at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Also, the integrated prototypes served as a vehicle to provide Level 5 requirements for the Crew Health and Performance Habitat Data System for Gateway Missions (Medical Level of Care IV). In the upcoming fiscal year, the MDA project will continue to provide systems engineering and vertical prototypes to refine requirements for medical Level of Care IV and inform requirements for Level of Care V.

Krihak, M.↗

Enabled International Collaborations in EDL: Lessons Learned and Recommendations

The modern day National Airspace System (NAS) is powered by System Wide Information Management (SWIM) which is a real-time digital data sharing infrastructure that provides a high fidelity view of the lifecycle of a flight. The newly available data within the SWIM feeds can be leveraged to help drive efficiencies in the NAS. In this talk, we investigate the gate conflict prediction problem as a concrete use case which could help drive efficiencies. We begin with a high level description of NASA's Airspace Technology Demonstration 2 which is built upon the real-time SWIM feeds and produces the data used in our investigation. We model gate conflicts as a regression problem and describe the iterative process of model building, model validation, and evaluation used to assess the efficacy of our approach.

William J. Coupe↗

Recommendation for a Medical System Concept of Operations for Gateway Missions

NASA’s exploration missions to cis-lunar space will establish a permanent gateway to future transport missions to Mars. These missions mandate a significant paradigm change for mission planning, spacecraft design, human systems integration, and in-flight medical care due to constraints on mass, volume, power, resupply, and medical evacuation capability. These constraints require medical system development to be tightly integrated with mission and habitat design to provide a sufficient medical infrastructure and enable mission success. This concept of operations provides a vision of medical care needs that will be used to guide the development of a medical system for the cis-lunar Gateway Habitat. This medical system will serve as the precursor to what is implemented in future exploration missions to Mars. This concept of operations documents an overview of the stakeholder needs and system goals of a medical system and provides examples of the types of activities for which the system will be used during the mission. This concept of operations informs the ExMC systems engineering effort to define the Gateway Habitat Medical System by documenting the medical activities and capabilities relevant to Gateway missions, as identified by the ExMC clinician community. In addition, this concept of operations will inform the subsequent systems engineering process of developing technical requirements, system architectures, interfaces, and verification and validation approaches for the medical system. This document supports the closure of ExMC Gap Med01: We do not have a concept of operations for medical care during exploration missions, corresponding to the ExMC-managed human system risk: Risk of Adverse Health Outcomes & Decrements in Performance due to Inflight Medical Conditions.

Rubin, David↗

Recommendations for Future Efforts in RANS Modeling and Simulation

The roadmap laid out in the CFD Vision 2030 document suggests that a decision to move away from RANS research needs to be made in the current timeframe (around 2020). This paper outlines industry requirements for improved predictions of turbulent flows and the cost-barrier that is often associated with reliance on scale resolving methods. Capabilities of RANS model accuracy for simple and complex flow flow fields are assessed, and modeling practices that degrade predictive accuracy are identified. Suggested research topics are identified that have the potential to improve the applicability and accuracy of RANS models. We conclude that it is important that some part of a balanced turbulence modeling research portfolio should include RANS efforts.

Bush, Robert H.↗

Recommended Crew Systems Capabilities for a 30 to 90 Day Four-Crew Lunar Surface Mission

For any given surface mission duration, there exists a set of surface capabilities necessary to sustain a four-person crew for the length of time the crew is on the surface. Identifying these capabilities is important to mission planners and spacecraft design engineers responsible for lunar surface habitation elements, who need to know which systems and capabilities must be prioritized for the vehicles they are designing. However, simply identifying the surface capabilities does not necessarily equal a viable surface configuration. These capabilities may or may not satisfy stakeholder expectations or even permit completion of mission objectives. Lunar lander cargo mass constraints are a powerful forcing function that requires significant efforts to reduce the mass of all surface elements, including those supporting crew habitation. The required capabilities do increase as a function of mission duration, but it is a nonlinear growth. There are key points in mission duration, beyond which certain additional capabilities are needed. This forms bands of capability between each point. Within a given band, the same functional capabilities are needed, and the only scaling is that associated with daily consumables. The next higher band requires additional capabilities. This paper will focus on those capabilities needed for missions of 30-90 days. It should be noted that there are some uncertainties interpreting NASA requirements that require capabilities after a certain number of days, as typically this refers to number of days in space, not number of days on the lunar surface. Depending on transportation architecture, the number of days between Earth launch and lunar surface landing may vary, therefore impacting when certain required capabilities are implemented. However, activities to prepare humans for missions to Mars and commercial interest in lunar development may drive progressive increases in surface duration. Missions up to 30 days are expected to follow the initial 6.5-day surface missions and there may be commercial interest in extending to even greater durations. This paper will examine the potential case of a 30-90-day surface mission duration with respect to the systems necessary to support crew living and working on the lunar surface.

Habitat↗

Urban Air Mobility Noise: Current Practice, Gaps, and Recommendations

AN Air Mobility (UAM) is an opportunity for aviation to improve transportation systems across the world. Representative UAM vehicle attributes include electrical vertical takeoff and landing (eVTOL) vehicles that can accommodate up to 6 passengers (or equivalent cargo), are possibly autonomous, perform missions of up to 100 nautical miles at altitudes up to 3000 ft. above ground level, have flight speeds up to 200 knots, and weigh between 800 and 8000 pounds. Along with the many anticipated benefits, there will be noise issues that need to be addressed. In 2018, NASA formed an Urban Air Mobility Noise Working Group (UNWG) to assemble noise experts from industry, universities and government agencies to identify, discuss, and address UAM noise issues. This oral presentation summarizes technology gaps and goals associated with four areas of interest: Tools & Technologies, Ground & Flight Testing, Human Response & Metrics, and Regulation & Policy, and is drawn from a draft white paper [1] by the same title. Tools & Technologies include noise prediction tools and noise reduction technologies that have been developed for conventional rotorcraft and fixed-wing vehicles that may be applicable or need to be modified for UAM. Prediction tools need to be able to account for variable speed rotors and other temporal variation effects that impact community noise. A reprioritization of noise sources needs to be done since UAM vehicles include multiple rotors/propellers, often in proximity to one another and/or the airframe, with dynamic transition, and new noise sources such as electric motors or hybrid-electric propulsion. Scattering and propagation methods need to be developed that include the vehicle components and surfaces near a receiver such as buildings and vertiports. Validation databases are needed to quantify prediction uncertainties. Prediction tools used to evaluate community noise will need source models appropriate for a wide range of UAM vehicles. Existing noise reduction technologies need to be evaluated and new noise reduction technologies should be developed in anticipation of future noise requirements. Although the prediction and treatment of interior cabin noise is a secondary goal, it is recognized that new tools and methods may be needed due to the uniqueness of the vehicle design and the presence of both acoustic and structure-borne loads. Ground & Flight Testing has been a critical part of validating noise reduction technologies and verifying that an air vehicle is ready for certification. UAM vehicles introduce new challenges for test procedures such as different source noise directivity, unsteady sources due to maneuvers, and a variety of takeoff and approach trajectories. The operating environment will be more complex than current aircraft with the introduction of vertiports in populated areas with “urban canyons” making reflections an important part of noise prediction and annoyance. It is expected that new test procedures and measurement methods will be necessary. Consideration will need to be given for both piloted and autonomous operations. Human Response & Metrics may be very different for UAM noise compared to current experience with airport noise. Current metrics used to certify rotorcraft and fixed-wing aircraft may not be as useful for evaluating UAM noise. Operations at lower altitudes may influence annoyance. Psychoacoustic and community testing will be needed to quantify annoyance and assess appropriate metrics. In addition to conventional noise level metrics, considerations such as audibility and temporal variation of the sound may be required. Differences between indoor or outdoor exposure will have an impact with dependence on urban and residential flight paths. Aircraft noise is currently regulated at a national level and typically involves partnerships with the industry to establish regulations. Regulators realize that current policies and procedures may not be appropriate for some of the emerging air vehicles and new procedures may be needed to address UAM noise. Development of new policies and procedures are needed so that local communities do not hastily attempt to establish their own restrictions that will both limit growth of the market and create an inconsistent and confusing regulatory environment. To expedite this development, it is crucial early measurement data are shared through partnership arrangements to support both noise certification and noise modeling/noise assessment. At the same time, an effective engagement strategy should be developed to address local community noise issues associated with UAM vehicles and flight operations as they arise.

urban air mobility↗

Recommended Laboratory and Field Studies ahead of Future Mercury Exploration

Data from Mariner 10, MESSENGER, and ground-based telescopic observations have facilitated great advancements towards understanding the geochemistry, geology, internal structure, and space environment (exosphere/magnetosphere) of Mercury. Future exploration efforts by BepiColombo, landed science, and sample return will revolutionize our understanding of this planet. However, to enhance the scientific return of past, present, and future data collection at Mercury, it is imperative that laboratory and field-based studies be conducted over the next decade. This white paper gives examples of laboratory and field studies, including instrument testing, which should take place over the next decade to facilitate the interpretation of data and preparation of future missions to the inner-most planet. By no means are the topics in this paper exhaustive, but rather are meant to demonstrate the immense amount of work that needs to be completed ahead of, or in conjunction with, current and future exploration efforts of Mercury. This work would amplify the benefits from additional data obtained from the planet’s surface to the fullest extent possible, and to aid in decision making of future instrument payloads. We have chosen to focus our inputs here on geochemistry, geology, and space environment related efforts, but we emphasize that extensive research in the areas of geophysics and other geosciences-related disciplines will benefit from additional studies.

Kathleen E. Vander Kaaden↗

Challenges and Advances in Modeling of the Solar Atmosphere: A White Paper of Findings and Recommendations

The next decade will be an exciting period for solar astrophysics, as new ground- and space-based instrumentation will provide unprecedented observations of the solar atmosphere and heliosphere. The synergy between modeling effort and comprehensive analysis of observations is crucial for the understanding of the physical processes behind the observed phenomena. However, the unprecedented wealth of data on one hand, and the complexity of the physical phenomena on the other, require the development of new approaches in both data analysis and numerical modeling. In this white paper, we summarize recent numerical achievements to reproduce structure, dynamics, and observed phenomena from the photosphere to the low corona and outline challenges we expect to face for the interpretation of future observations.

Heliophysics↗

Mitigation selection and qualification recommendations for Xilinx Virtex, Virtex-II, and Virtex-4 field programmable gate arrays

This work discusses mitigation selection and qualification techniques for Xilinx reconfigurable field programmable gate arrays (FPGAs). The aim of the paper is to provide readers with a better understanding of the engineering/reliability/project cost relationship that occurs when developing a mitigation strategy for static random access memory (SRAM)-based FPGAs.

Allen, Gregory↗