Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “technical support”

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 883 records · Page 49
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Research and Technology, 1994

This report selectively summarizes the NASA Lewis Research Center's research and technology accomplishments for the fiscal year 1994. It comprises approximately 200 short articles submitted by the staff members of the technical directorates. The report is organized into six major sections: Aeronautics, Aerospace Technology, Space Flight Systems, Engineering and Computational Support, Lewis Research Academy, and Technology Transfer. A table of contents and author index have been developed to assist the reader in finding articles of special interest. This report is not intended to be a comprehensive summary of all research and technology work done over the past fiscal year. Most of the work is reported in Lewis-published technical reports, journal articles, and presentations prepared by Lewis staff members and contractors. In addition, university grants have enabled faculty members and graduate students to engage in sponsored research that is reported at technical meetings or in journal articles. For each article in this report a Lewis contact person has been identified, and where possible, reference documents are listed so that additional information can be easily obtained. The diversity of topics attests to the breadth of research and technology being pursued and to the skill mix of the staff that makes it possible.

Source record↗
NASA NTRS1983

Tracking and data acquisition system for the 1990's. Volume 8: TDAS frequency planning

Current planning calls for the TDAS to support new user and crosslink services, in addition to TDRSS-compatible services. TDRSS-compatible services would operate in current S-band and K-band channels used by TDRSS. New services, however, can take advantage of technology advances at microwave and optical frequencies. For augmented space-to-space services, 60 GHz and GaAs laser systems offer technical advantages, relative freedom from RFI, and a benign regulatory environment (i.e., minimal congestion and, in the case of 60 GHz, maximum regulatory support for TDAS-type services). For TDAS Earth-to-space and space-to-Earth services, the 30/20 GHz band offers the best mix of technical and regulatory advantages. But use of these bands would have to be coordinated with the U.S. military.

Heppe, S. B.↗
NASA NTRS2023

U.S. Spacesuit Knowledge Capture – Expanding Our Future

NASA is going to the Moon. And it will don a new spacesuit when it reaches its destination. NASA is partnering with industry to build the spacesuit and supporting systems (i.e., surface mobility tools) that astronauts will use on the Moon, starting with Artemis III. The Johnson Space Center’s (JSC) Extravehicular Activity and Human Surface Mobility Program (EHP) is managing this effort, and the U.S. Spacesuit Knowledge Capture (SKC) Program is expanding its scope to help. For 15 years, the SKC Program has collected, archived, and disseminated decades of spacesuit-related knowledge, as appropriate, to help NASA scientists, technicians, and engineers support space exploration. The SKC Program captures its knowledge by hosting and recording subject-matter expert (SME) lectures, interviews, and workshops. It also collects retired SMEs’ reports, drawings, and schematics containing legacy spacesuit knowledge. To build a technically capable spacesuit essential for future lunar exploration, spacesuit professionals borrowed much of their knowledge from legacy Extravehicular Activity (EVA) spacesuits. Most of the SKC Program’s captured knowledge has focused on legacy and current spacesuits. To support EHP, the SKC Program is expanding its knowledge capture focus beyond the spacesuit and will seek to collect knowledge from other pertinent topics (e.g., Lunar Terrain Vehicle and EVA tools). In 2007, the SKC Program began as an independent source, without funding. As demand for capturing essential spacesuit knowledge increased, consequently, the SKC Program’s funding increased. Expansion of the SKC Program was evident in 2019, when it seized the opportunity to capture the Exploration Extravehicular Mobility Unit (xEMU) buildup at JSC. In 2021, its collaboration with the xEMU Technical Community of Practice facilitated training and knowledge sharing with the xEMU team. In 2022, the SKC Program began supporting EHP. This paper describes the SKC Program’s expansive evolution, plans to support EHP, and more.

Cinda Chullen↗
NASA NTRS2018

Medical Data Architecture Project Status

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. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. 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 supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗
NASA NTRS2018

Medical Data Architecture (MDA) Project Status

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. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. 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 supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗
NASA NTRS2019

Medical Data Architecture (MDA) Project Status

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. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. 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 supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗
NASA NTRS2020

Medical Data Architecture Prototype Development - Summary of Recent Work and Proposed Ideas for Upcoming Work

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, and in ExMC Gap Med 10: We do not have the capability to provide computed medical decision support during exploration missions. These gaps recognize the need for a comprehensive medical data management system and the accompanying computational support to provide autonomous medical care during long duration exploration missions. As the MDA matures—including the capability to comprehensively process and discover medically-relevant information to support medical operations during exploration missions—project focus will shift to maturing and extending the MDA platform to enable clinical decision support and real-time guidance. To date, the MDA foundational architecture has recommended exploration medical system Level of Care IV requirements through a series of test bed prototype developments and analog demonstrations. The next stage in the development will focus on more autonomous clinical decision making necessary to address challenges in executing a self-contained medical system that enables health care both with and without assistance from ground support. A thorough understanding of current state of medical decision support systems, advanced machine learning algorithms and vast and varied data sources is required. The development of a clinical decision support for exploration missions (Level of Care V) roadmap is needed: one that assesses of current state of the art of clinical decision support systems (CDSS), interoperability issues, identification of challenges in health and performance monitoring, obtaining and processing information from biosensors, knowledge and data management, data integration and fusion, and advanced algorithm development. This roadmap must also include rapid prototype development in the areas of data processing, advanced analysis and prediction of medical events, and treatment based on medically relevant information processing and evidence-based best practices. In this presentation, an overview of the relevant issues and the beginning framework of a Level of Care V CDSS development roadmap will be provided.

Krihak, M.↗
NASA NTRS1989

Telescience workstation

As part of the Telescience Testbed Pilot Program, the Universities Space Research Association/ Research Institute for Advanced Computer Science (USRA/RIACS) proposed to support remote communication by providing a network of human/machine interfaces, computer resources, and experimental equipment which allows: remote science, collaboration, technical exchange, and multimedia communication. The telescience workstation is intended to provide a local computing environment for telescience. The purpose of the program are as follows: (1) to provide a suitable environment to integrate existing and new software for a telescience workstation; (2) to provide a suitable environment to develop new software in support of telescience activities; (3) to provide an interoperable environment so that a wide variety of workstations may be used in the telescience program; (4) to provide a supportive infrastructure and a common software base; and (5) to advance, apply, and evaluate the telescience technolgy base. A prototype telescience computing environment designed to bring practicing scientists in domains other than their computer science into a modern style of doing their computing was created and deployed. This environment, the Telescience Windowing Environment, Phase 1 (TeleWEn-1), met some, but not all of the goals stated above. The TeleWEn-1 provided a window-based workstation environment and a set of tools for text editing, document preparation, electronic mail, multimedia mail, raster manipulation, and system management.

Brown, Robert L.↗
NASA NTRSDate not supplied

A New Vision and A More Rational Process Will Advance Space Life Support Through Better Projects

Many space life support assumptions are obviously mistaken but they are generally accepted because they mutually support each other and because they advance a mistaken futuristic vision of closed human ecosystems in space. Many projects have been mistakenly selected to increase life support system closure or reduce launch mass in order to implement this impractical vision. Project members rarely challenge their project’s assumptions and guiding vision. Systems engineering including cost, reliability, risk, and system trade-offs has been very strongly discouraged to prevent rational criticism of these dubious assumptions, the projects, and the ecosystem vision. A more realistic vision can define better near term life support goals and future aspirations that will improve mission support and increase public interest. Given more realistic goals, it will be possible to develop effective technical alternatives, use open rational project selection methods, conduct professional project management, and make swifter progress in the inevitable human advance into space. The current unworkable human space settlement scenario involves moon visits and permanent bases, zero gravity trips to Mars, Mars visits and bases, all leading to extensive human settlements on the moon and Mars. This is unrealistic because the moon and Mars have less than Earth normal gravity and high radiation that can seriously damage human health. A better alternative would use rotating space colonies that produce Earth gravity and are radiation shielded. The attractive fantasy of reproducing terrestrial ecology in space should be replaced by the idea of building a closed system based on advancing technology such as artificial photosynthesis. Past mistaken projects include growing plants for food to replicate terrestrial food sources, recovering small amounts of water from difficult to process waste to achieve high system closure, and using newly designed, lighter, but unreliable hardware to reduce launch mass. The political process supporting the false assumptions, projects, and vision has deliberately prevented the usual systems engineering and cost-benefit analysis. We are going to do much better.

Harry W. Jones↗
NASA NTRS1991

ECLSS medical support activities

During the period from April 10, 1990 to April 9, 1991, the Consortium for the Space Life Sciences provided technical assistance to the NASA/MSFC water recovery efforts. This assistance was in the form of literature reviews, technical recommendations, and presentations. This final report summarizes the activities completed during this period and identifies those areas requiring additional efforts. The tasks which the University of Alabama in Huntsville (UAH) water recovery team addressed were either identified by MSFC technical representatives or chosen from those outlined in the subject statement of work.

Crump, William J.↗
NASA NTRSDate not supplied

A Decision Support System for Extravehicular Operations Under Significant Communication Latency

Within the next few decades, humanity hopes to perform extravehicular activities (EVAs) on the surface of Mars; however, several technical and operational challenges must first be overcome. Foremost among these challenges is managing a significant two-way communication latency between Earth and Mars. Current and historical paradigms of EVA operations have required near-real-time communication between the crewmember(s) performing an EVA and an Earth-based mission control. Next-generation operational paradigms for supporting deep space exploration will necessitate a distributed decision authority system, including delayed Earth-based mission control, the on-planet extravehicular crewmember(s), and intermediate mission support from intravehicular crewmember(s) within real-time communication range. This latter group is of particular interest: they must provide operations support without the plentiful resources available to mission control on Earth. For this purpose, NASA is developing the Personalized EVA Informatics and Decision Support (PersEIDS) software platform. PersEIDS is designed to bolster operator situational awareness and offload operator workload by automating the tracking and projection of consumables usage over an EVA timeline, providing real-time probabilistic safety assessments of an EVA timeline given consumables constraints, and recommending alternative EVA timeline(s) when the active timeline is not expected to be completed under consumables limits. The PersEIDS concept of operations, use cases, and models will be presented. A limited version of PersEIDS was demonstrated during a three-day-long study where each day a roughly four-hour-long simulated Martian EVA was performed in virtual reality at the NASA Johnson Space Center. The first day was a control trial without PersEIDS support; the second and third days represented different levels of decision support provided by PersEIDS to the intravehicular crewmember acting as mission control. With PersEIDS support, the IV crewmember was able to manage the mission to completion faster and with more remaining consumables; however, additional testing is required to understand confounding factors, e.g. training bias.

Mars↗
NASA NTRS1988

Successful expert systems for space shuttle payload integration

Expert systems are successfully applied to solve recurring NASA Space Shuttle orbiter payload integration problems. Recurrence of these problems is the result of each Space Shuttle mission being unique. The NASA Space Shuttle orbiter was designed to be extremely flexible in its ability to handle many types and combinations of satellites and experiments. This flexibility results in different and unique engineering resource requirements for each of the payload satellites and experiments. The first successful expert system to be applied to these problems was the Orbiter Payload Bay Cabling Expert System (EXCABL), developed at Rockwell International Space Transportation Systems Division. The operational version of EXCABL was delivered in 1986 and successfully solved the payload electrical support services cabling layout problem. As a result of this success, a second expert system, Expert Drawing Matching System (EXMATCH), was developed to generate a list of the reusable installation drawings available for each EXCABL solution. EXMATCH went operational in 1987. As a result of these initial successes, the need for a third expert system was defined and is awaiting development. This new Expert System, called Technical Order Listing Expert System (EXTOL), will generate a list of all the applicable reusable installation drawings available to support the total payload bay mission provisioning and installation effort. This paper describes these expert systems, the individual problems that they were designed to solve, their individual solutions, and the degree of success achieved. These expert systems' instantiate the applicability of this technology to the solution of real-world Space Shuttle payload integration problems.

Morris, Keith↗
NASA NTRS2017

Unexpected Control Structure Interaction on International Space Station

On June 23, 2011, the International Space Station (ISS) was performing a routine 180 degree yaw maneuver in support of a Russian vehicle docking when the on board Russian Segment (RS) software unexpectedly declared two attitude thrusters failed and switched thruster configurations in response to unanticipated ISS dynamic motion. Flight data analysis after the maneuver indicated that higher than predicted structural loads had been induced at various locations on the United States (U.S.) segment of the ISS. Further analysis revealed that the attitude control system was firing thrusters in response to both structural flex and rigid body rates, which resonated the structure and caused high loads and fatigue cycles. It was later determined that the thruster themselves were healthy. The RS software logic, which was intended to react to thruster failures, had instead been heavily influenced by interaction between the control system and structural flex. This paper will discuss the technical aspects of the control structure interaction problem that led to the RS control system firing thrusters in response to structural flex, the factors that led to insufficient preflight analysis of the thruster firings, and the ramifications the event had on the ISS. An immediate consequence included limiting which thrusters could be used for attitude control. This complicated the planning of on-orbit thruster events and necessitated the use of suboptimal thruster configurations that increased propellant usage and caused thruster lifetime usage concerns. In addition to the technical aspects of the problem, the team dynamics and communication shortcomings that led to such an event happening in an environment where extensive analysis is performed in support of human space flight will also be examined. Finally, the technical solution will be presented, which required a multidisciplinary effort between the U.S. and Russian control system engineers and loads and dynamics structural engineers to develop and implement an extensive modification in the RS software logic for ISS attitude control thruster firings.

Gomez, Susan F.↗
NASA NTRS2009

The Deep Impact Network Experiment Operations Center Monitor and Control System

The Interplanetary Overlay Network (ION) software at JPL is an implementation of Delay/Disruption Tolerant Networking (DTN) which has been proposed as an interplanetary protocol to support space communication. The JPL Deep Impact Network (DINET) is a technology development experiment intended to increase the technical readiness of the JPL implemented ION suite. The DINET Experiment Operations Center (EOC) developed by JPL's Protocol Technology Lab (PTL) was critical in accomplishing the experiment. EOC, containing all end nodes of simulated spaces and one administrative node, exercised publish and subscribe functions for payload data among all end nodes to verify the effectiveness of data exchange over ION protocol stacks. A Monitor and Control System was created and installed on the administrative node as a multi-tiered internet-based Web application to support the Deep Impact Network Experiment by allowing monitoring and analysis of the data delivery and statistics from ION. This Monitor and Control System includes the capability of receiving protocol status messages, classifying and storing status messages into a database from the ION simulation network, and providing web interfaces for viewing the live results in addition to interactive database queries.

Delay/Disruption Tolerant Network (DTN)↗
NASA NTRS2012

AES Water Architecture Study Interim Results

The mission of the Advanced Exploration System (AES) Water Recovery Project (WRP) is to develop advanced water recovery systems in order to enable NASA human exploration missions beyond low earth orbit (LEO). The primary objective of the AES WRP is to develop water recovery technologies critical to near term missions beyond LEO. The secondary objective is to continue to advance mid-readiness level technologies to support future NASA missions. An effort is being undertaken to establish the architecture for the AES Water Recovery System (WRS) that meets both near and long term objectives. The resultant architecture will be used to guide future technical planning, establish a baseline development roadmap for technology infusion, and establish baseline assumptions for integrated ground and on-orbit environmental control and life support systems (ECLSS) definition. This study is being performed in three phases. Phase I of this study established the scope of the study through definition of the mission requirements and constraints, as well as indentifying all possible WRS configurations that meet the mission requirements. Phase II of this study focused on the near term space exploration objectives by establishing an ISS-derived reference schematic for long-duration (>180 day) in-space habitation. Phase III will focus on the long term space exploration objectives, trading the viable WRS configurations identified in Phase I to identify the ideal exploration WRS. The results of Phases I and II are discussed in this paper.

Sarguisingh, Miriam J.↗
NASA NTRS1992

A feasibility assessment of magnetic bearings for free-piston Stirling space power converters

This report describes a design and analysis study performed by Mechanical Technology Incorporated (MTI) under NASA Contract NAS3-26061. The objective of the study was to assess the feasibility and efficacy of applying magnetic bearings to free-piston Stirling-cycle power conversion machinery of the type currently being evaluated for possible use in long-term space missions. The study was performed for a 50-kWe Reference Stirling Space Power Converter (RSSPC) system consisting of two 25-kWe free-piston Stirling engine modules. Two different versions of the RSSPC engine modules have been defined under NASA Contract NAS3-25463. These modules currently use hydrostatic gas bearings to support the reciprocating displacer and power piston assemblies. Results of this study show that active magnetic bearings of the attractive electromagnetic type are technically feasible for RSSPC application provided that wire insulation with 60,000-hr life capability at 300 C can be developed for the bearing coils. From a design integration standpoint, both versions of the RSSPC were found to be conceptually amenable to magnetic support of the power piston assembly. However, only one version of the RSSPC was found to be amendable to magnetic support of the displacer assembly. Unacceptable changes to the basic engine design would be required to incorporate magnetic displacer bearings into the second version. Complete magnetic suspension of the RSSPC can potentially increase overall efficiency of the Stirling cycle power converter by 0.53 to 1.4 percent (0.15 to 0.4 efficiency points). Magnetic bearings will also overcome several operational concerns associated with hydrostatic gas bearing systems. However, these advantages are accompanied by a 5 to 8 percent increase in specific mass of the RSSPC, depending on the RSSPC version employed. Additionally, magnetic bearings are much more complex, both mechanically and particularly electronically, than hydrostatic bearings. Accordingly, long-term stability and reliability represent areas of uncertainty for magnetic bearings. Considerable development effort will be required to establish the long-term suitability of these bearings for Stirling space power applications.

Curwen, Peter W.↗