Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Ground Support System”

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

Exploration Medical Capability System Engineering Overview

Deep Space Gateway and Transport missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element's approach to enabling the necessary autonomy. The ExMC Systems Engineering team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." The Element's work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will discuss how ExMC is using MBSE to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. How MBSE is being used to integrate across disciplines and NASA Centers will also be described. The medical system being discussed in this talk is one system within larger habitat systems. Data generated within the medical system will be inputs to other systems and vice versa. This talk will also describe the next steps in model development that include: modeling the different systems that comprise the larger system and interact with the medical system, understanding how the various systems work together, and developing tools to support trade studies.

Mindock, J.↗

Exploration Medical Cap Ability System Engineering Overview

Deep Space Gateway and Transport missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element's approach to enabling the necessary autonomy. The ExMC Systems Engineering team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." The Element's work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will discuss how ExMC is using MBSE to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. How MBSE is being used to integrate across disciplines and NASA Centers will also be described. The medical system being discussed in this talk is one system within larger habitat systems. Data generated within the medical system will be inputs to other systems and vice versa. This talk will also describe the next steps in model development that include: modeling the different systems that comprise the larger system and interact with the medical system, understanding how the various systems work together, and developing tools to support trade studies.

McGuire, K.↗

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 International Space Station (ISS) 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 variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable an increasingly autonomous crew than the current ISS paradigm. The MDA will develop capabilities that support automated data collection, and the necessary functionality and challenges in executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. To attain this goal, the first year of the MDA project focused on reducing technical risk, developing documentation and instituting iterative development processes that established the basis for the first version of MDA software (or Test Bed 1). Test Bed 1 is based on a nominal operations scenario authored by the ExMC Element Scientist. This narrative was decomposed into a Concept of Operations that formed the basis for Test Bed 1 requirements. These requirements were successfully vetted through the MDA Test Bed 1 System Requirements Review, which permitted the MDA project to begin software code development and component integration. This paper highlights the MDA objectives, development processes, and accomplishments, and identifies the fiscal year 2017 milestones and deliverables in the upcoming year.

Data management↗

Exploration Medical Capability Systems Engineering Overview and Update

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. The ExMC Systems Engineering (SE) team’s mission is to “Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds.” The Element’s work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS and what they are focusing on for the upcoming year.

Kerry McGuire↗

Advances in Orion's On-Orbit Guidance and Targeting System Architecture

NASA's manned spaceflight programs have a rich history of advancing onboard guidance and targeting technology. In order to support future missions, the guidance and targeting architecture for the Orion Multi-Purpose Crew Vehicle must be able to operate in complete autonomy, without any support from the ground. Orion's guidance and targeting system must be sufficiently flexible to easily adapt to a wide array of undecided future missions, yet also not cause an undue computational burden on the flight computer. This presents a unique design challenge from the perspective of both algorithm development and system architecture construction. The present work shows how Orion's guidance and targeting system addresses these challenges. On the algorithm side, the system advances the state-of-the-art by: (1) steering burns with a simple closed-loop guidance strategy based on Shuttle heritage, and (2) planning maneuvers with a cutting-edge two-level targeting routine. These algorithms are then placed into an architecture designed to leverage the advantages of each and ensure that they function in concert with one another. The resulting system is characterized by modularity and simplicity. As such, it is adaptable to the on-orbit phases of any future mission that Orion may attempt.

Scarritt, Sara K.↗

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic alert and Collision Avoidance System (TCAS) II. It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear.

unmanned aircraft systems↗

TES: A modular systems approach to expert system development for real-time space applications

A major goal of the Space Station era is to reduce reliance on support from ground based experts. The development of software programs using expert systems technology is one means of reaching this goal without requiring crew members to become intimately familiar with the many complex spacecraft subsystems. Development of an expert systems program requires a validation of the software with actual flight hardware. By combining accurate hardware and software modelling techniques with a modular systems approach to expert systems development, the validation of these software programs can be successfully completed with minimum risk and effort. The TIMES Expert System (TES) is an application that monitors and evaluates real time data to perform fault detection and fault isolation tasks as they would otherwise be carried out by a knowledgeable designer. The development process and primary features of TES, a modular systems approach, and the lessons learned are discussed.

Cacace, Ralph↗

Master Console System Monitoring and Control Development

The Master Console internship during the spring of 2013 involved the development of firing room displays at the John F. Kennedy Space Center (KSC). This position was with the Master Console Product Group (MCPG) on the Launch Control System (LCS) project. This project is responsible for the System Monitoring and Control (SMC) and Record and Retrieval (R&R) of launch operations data. The Master Console is responsible for: loading the correct software into each of the remaining consoles in the firing room, connecting the proper data paths to and from the launch vehicle and all ground support equipment, and initializing the entire firing room system to begin processing. During my internship, I developed a system health and status display for use by Master Console Operators (MCO) to monitor and verify the integrity of the servers, gateways, network switches, and firewalls used in the firing room.

Brooks, Russell A.↗

Thermal Modeling and Correlation of the Space Environments Complex Vacuum Chamber and Cryoshroud

A thermal model of the Space Environments Complex (SEC) vacuum chamber and cryoshroud has been developed in support of upcoming thermal vacuum/thermal balance testing for Orion EM-1. The model was developed in Thermal Desktop and includes the vacuum chamber itself, a fluid model of the gaseous nitrogen flowing through the cryoshroud and the chamber piping, the Heat Flux System (HFS) within the cryoshroud, and the mechanical ground support equipment (MGSE) that interfaces with the vehicle. It has been correlated with steady state data from three tests. Two tests ran the cryoshroud in hot mode at 170 °F, and one test ran the cryoshroud in cold mode at -263 °F. Correlation was done using an optimization algorithm to find values of unknown contact conductances that minimized the RMS error between the model predictions and the test data. Overall, model quality was very good with a total RMS error of 2.6 °F.

Stalcup, Erik J.↗

Integrated ECLSS Ground Testbed Development and Status for 2025

The reliability of Spacecraft Life Support systems and the associated mass needed to support human spaceflight is one of the largest risks for missions beyond Low Earth Orbit. The reliability of these systems directly corresponds to the number of spares needed to support the mission. Performance improvements for these systems can reduce the consumables needed for long-duration missions. The only integrated spacecraft regenerative Life Support System exists in Low Earth Orbit. It is not practical to use the ISS system to fully understand the reliability of the technology as these systems are currently maintaining a livable environment and crew’s lives are dependent on the availability of these systems. To achieve advancement on reliability and mass, NASA has initiated the development of an Integrated ECLSS ground Testbed. This paper will provide a status on the testbed development, hardware development and areas for investigation. This paper will also cover planned testbed integration and support for Earth Independent Operations (EIO). This paper will be relevant to sessions: 205, 300, 301, 404, 406, 500, 50, 506, and 511.

Christopher Brown↗

DIGITAL COMMAND SYSTEM FOR SATELLITES

New coding system capable of transmitting almost 8,000 commands for a single tone and compatible with both tone- and digital-controlled satellites

SATELLITE CONTROL↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components.

guidelines↗

Design and evaluation of an advanced air-ground data-link system for air traffic control

The design and evaluation of the ground-based portion of an air-ground data-link system for air traffic control (ATC) are described. The system was developed to support the 4D Aircraft/ATC Integration Study, a joint simulation experiment conducted at NASA's Ames and Langley Research Centers. The experiment focused on airborne and ground-based procedures for handling aircraft equipped with a 4D-Flight Management System (FMS) and the system requirements needed to ensure conflict-free traffic flow. The Center/TRACON Automation System (CTAS) at Ames was used for the ATC part of the experiment, and the 4D-FMS-equipped aircraft was simulated by the Transport Systems Research Vehicle (TSRV) simulator at Langley. The data-link system supported not only conventional ATC communications, but also the communications needed to accommodate the 4D-FMS capabilities of advanced aircraft. Of great significance was the synergism gained from integrating the data link with CTAS. Information transmitted via the data link was used to improve the monitoring and analysis capability of CTAS without increasing controller input workload. Conversely, CTAS was used to anticipate and create prototype messages, thus reducing the workload associated with the manual creation of data-link messages.

Denbraven, Wim↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. The Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create an integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components...

ground data system (GDS)↗

Integrated Ground Operations Demonstration Units Testing Plans and Status

Cryogenic propellant loading operations with their associated flight and ground systems are some of the most complex, critical activities in launch operations. Consequently, these systems and operations account for a sizeable portion of the life cycle costs of any launch program. NASA operations for handling cryogens in ground support equipment have not changed substantially in 50 years, despite advances in cryogenics, system health management and command and control technologies. This project was developed to mature, integrate and demonstrate advancement in the current state of the art in these areas using two distinct integrated ground operations demonstration units (GODU): GODU Integrated Refrigeration and Storage (IRAS) and GODU Autonomous Control

Johnson, Robert G.↗

Brentwood Lessons Learned Project Report

The purpose of this report is to document lessons learned in the installation of the hydrogen fueling station at the National Park Service Brentwood site in Washington, D.C., to help further the deployment of hydrogen infrastructure required to support hydrogen and other fuel cell technologies. Hydrogen fueling is the most difficult infrastructure component to build and permit. Hydrogen fueling can include augmenting hydrogen fueling capability to existing conventional fuel fueling stations as well as building brand new hydrogen fueling stations. This report was produced as part of the Brentwood Lessons Learned project. The project consisted of transplanting an existing modular hydrogen fueling station from Connecticut to the National Park Service Brentwood site. This relocation required design and construction at the Brentwood site to accommodate the existing station design as well as installation and validation of the updated station. One of the most important lessons learned was that simply moving an existing modular station to an operating site was not necessarily straight-forward - performing the relocation required significant effort and cost. The station has to function at the selected operating site and this functionality requires a power supply, building supports connecting to an existing alarm system, electrical grounding and lighting, providing nitrogen for purging, and providing deionized water if an electrolyzer is part of the station package. Most importantly, the station has to fit into the existing site both spatially and operationally and not disrupt existing operations at the site. All of this coordination and integration requires logistical planning and project management. The idea that a hydrogen fueling station can be simply dropped onto a site and made immediately operational is generally not realistic. Other important lessons learned include that delineating the boundaries of the multiple jurisdictions that have authority over a project for all parties involved in the project are key to an efficient approval process; and site investigation is necessary when integrating a new station design onto an existing site, particularly an older existing site that may have limited documentation on the site history and operations. The lessons learned for permitting and subcontracting construction work can be applied to other similar sites and to commercial sites.

30 DIRECT ENERGY CONVERSION↗

Programmed schedule holds for improving launch vehicle holds

Baseline definition and system optimization are used for the analysis of programmed holds developed through prelaunch system analysis. Identification of design specifications for ground support equipment and maintenance concepts, and design specifications are used to describe the functional utilization of the overall flow process.

Gralow, F. H.↗