Search NASA⌕ Search

SEARCH · Search NASA

Results for “ground operational 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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Reactor Simulator Testing

As part of the Nuclear Systems Office Fission Surface Power Technology Demonstration Unit (TDU) project, a reactor simulator test loop (RxSim) was design & built to perform integrated testing of the TDU components. In particular, the objectives of RxSim testing was to verify the operation of the core simulator, the instrumentation and control system, and the ground support gas and vacuum test equipment. In addition, it was decided to include a thermal test of a cold trap purification design and a pump performance test at pump voltages up to 150 V since the targeted mass flow rate of 1.75 kg/s was not obtained in the RxSim at the originally constrained voltage of 120 V. This paper summarizes RxSim testing. The gas and vacuum ground support test equipment performed effectively in NaK fill, loop pressurization, and NaK drain operations. The instrumentation and control system effectively controlled loop temperature and flow rates or pump voltage to targeted settings. The cold trap design was able to obtain the targeted cold temperature of 480 K. An outlet temperature of 636 K was obtained which was lower than the predicted 750 K but 156 K higher than the cold temperature indicating the design provided some heat regeneration. The annular linear induction pump (ALIP) tested was able to produce a maximum flow rate of 1.53 kg/s at 800 K when operated at 150 V and 53 Hz.

Schoenfeld, Michael P.↗
NASA NTRS2013

Reactor Simulator Testing

As part of the Nuclear Systems Office Fission Surface Power Technology Demonstration Unit (TDU) project, a reactor simulator test loop (RxSim) was design & built to perform integrated testing of the TDU components. In particular, the objectives of RxSim testing was to verify the operation of the core simulator, the instrumentation and control system, and the ground support gas and vacuum test equipment. In addition, it was decided to include a thermal test of a cold trap purification design and a pump performance test at pump voltages up to 150 V since the targeted mass flow rate of 1.75 kg/s was not obtained in the RxSim at the originally constrained voltage of 120 V. This paper summarizes RxSim testing. The gas and vacuum ground support test equipment performed effectively in NaK fill, loop pressurization, and NaK drain operations. The instrumentation and control system effectively controlled loop temperature and flow rates or pump voltage to targeted settings. The cold trap design was able to obtain the targeted cold temperature of 480 K. An outlet temperature of 636 K was obtained which was lower than the predicted 750 K but 156 K higher than the cold temperature indicating the design provided some heat regeneration. The annular linear induction pump (ALIP) tested was able to produce a maximum flow rate of 1.53 kg/s at 800 K when operated at 150 V and 53 Hz.

Schoenfeld, Michael P.↗
NASA NTRS1994

GRTS operations monitor/control system

An Operations Monitor/Control System (OMCS) was developed to support remote ground station equipment. The ground station controls a Tracking Data Relay Satellite (TDRS) relocated to provide coverage in the tracking system's zone of exclusion. The relocated satellite significantly improved data recovery for the Gamma Ray Observatory mission. The OMCS implementation, performed in less than 11 months, was mission critical to TDRS drift operations. Extensive use of Commercial Off The Shelf (COTS) hardware and software products contributed to implementation success. The OMCS has been operational for over 9 months with no significant problems. This paper will share our experiences in OMCS development and integration.

Rohrer, Richard A.↗
NASA NTRS2013

Reactor Simulator Integration and Testing

As part of the Nuclear Systems Office Fission Surface Power Technology Demonstration Unit (TDU) project, a reactor simulator (RxSim) test loop was designed and built to perform integrated testing of the TDU components. In particular, the objectives of RxSim testing were to verify the operation of the core simulator, the instrumentation and control system, and the ground support gas and vacuum test equipment. In addition, it was decided to include a thermal test of a cold trap purification design and a pump performance test at pump voltages up to 150 V because the targeted mass flow rate of 1.75 kg/s was not obtained in the RxSim at the originally constrained voltage of 120 V. This Technical Memorandum summarizes RxSim testing. The gas and vacuum ground support test equipment performed effectively in NaK fill, loop pressurization, and NaK drain operations. The instrumentation and control system effectively controlled loop temperature and flow rates or pump voltage to targeted settings. The cold trap design was able to obtain the targeted cold temperature of 480 K. An outlet temperature of 636 K was obtained, which was lower than the predicted 750 K but 156 K higher than the cold temperature, indicating the design provided some heat regeneration. The annular linear induction pump tested was able to produce a maximum flow rate of 1.53 kg/s at 800 K when operated at 150 V and 53 Hz.

Schoenfield, M. P.↗
NASA NTRS1972

Skylab astronaut life support assembly

A comparative study was performed to define an optimum portable life support system for suited operations inside and outside the Skylab Program. Emphasis was placed on utilization of qualified equipment, modified versions of qualified equipment, and new systems made up to state-of-the-art components. Outlined are the mission constraints, operational modes, and evaluation ground rules by which the Skylab portable life support system was selected and the resulting design.

Brown, J. T.↗
NASA NTRS2006

AERCam Autonomy: Intelligent Software Architecture for Robotic Free Flying Nanosatellite Inspection Vehicles

The NASA Johnson Space Center has developed a nanosatellite-class Free Flyer intended for future external inspection and remote viewing of human spacecraft. The Miniature Autonomous Extravehicular Robotic Camera (Mini AERCam) technology demonstration unit has been integrated into the approximate form and function of a flight system. The spherical Mini AERCam Free Flyer is 7.5 inches in diameter and weighs approximately 10 pounds, yet it incorporates significant additional capabilities compared to the 35-pound, 14-inch diameter AERCam Sprint that flew as a Shuttle flight experiment in 1997. Mini AERCam hosts a full suite of miniaturized avionics, instrumentation, communications, navigation, power, propulsion, and imaging subsystems, including digital video cameras and a high resolution still image camera. The vehicle is designed for either remotely piloted operations or supervised autonomous operations, including automatic stationkeeping, point-to-point maneuvering, and waypoint tracking. The Mini AERCam Free Flyer is accompanied by a sophisticated control station for command and control, as well as a docking system for automated deployment, docking, and recharge at a parent spacecraft. Free Flyer functional testing has been conducted successfully on both an airbearing table and in a six-degree-of-freedom closed-loop orbital simulation with avionics hardware in the loop. Mini AERCam aims to provide beneficial on-orbit views that cannot be obtained from fixed cameras, cameras on robotic manipulators, or cameras carried by crewmembers during extravehicular activities (EVA s). On Shuttle or International Space Station (ISS), for example, Mini AERCam could support external robotic operations by supplying orthogonal views to the intravehicular activity (IVA) robotic operator, supply views of EVA operations to IVA and/or ground crews monitoring the EVA, and carry out independent visual inspections of areas of interest around the spacecraft. To enable these future benefits with minimal impact on IVA operators and ground controllers, the Mini AERCam system architecture incorporates intelligent systems attributes that support various autonomous capabilities. 1) A robust command sequencer enables task-level command scripting. Command scripting is employed for operations such as automatic inspection scans over a region of interest, and operator-hands-off automated docking. 2) A system manager built on the same expert-system software as the command sequencer provides detection and smart-response capability for potential system-level anomalies, like loss of communications between the Free Flyer and control station. 3) An AERCam dynamics manager provides nominal and off-nominal management of guidance, navigation, and control (GN&C) functions. It is employed for safe trajectory monitoring, contingency maneuvering, and related roles. This paper will describe these architectural components of Mini AERCam autonomy, as well as the interaction of these elements with a human operator during supervised autonomous control.

Fredrickson, Steven E.↗
NASA NTRS1993

NASDA satellite mission operation system and operations

NASDA has recently developed a new tracking and control system as a basis for future satellite mission operation. It is named type-I Space Operations and Data Systems (type-I SODS). The software of this system is separated into three parts: operation and control system, network system, and support and information system. The operation control system treats telemetry and command operations. The network system controls the communication line and ground station equipments to connect the satellite and the operation control system. The support and information system provides to other systems necessary information. JERS-1 which was launched in February of this year is the first satellite operated by type-l SODS. We explain the architecture and operation methods of this system using JERS-1 mission operations.

Yamaya, Kousaku↗
NASA NTRSDate not supplied

Earth Independent Medical Operations (EIMO)

Inherent in interplanetary space travel are unprecedented challenges that could threaten mission success and negatively impact crew health and performance. Return to definitive care is essentially untenable and resources will be constrained with practically no re-supply capability. Access to ground-based medical expertise will be significantly delayed under nominal conditions with exacerbation during conjunction or prolonged dust storms. Taken together, these challenges necessitate the development of a progressively autonomous medical operational support system to assist the crew medical officer (CMO). While support from ground based medical experts will remain indispensable for pre-mission planning, the approach to management of acute/emergent medical contingencies will require a gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. To progressively enable EIMO, a series of meetings were convened with subject matter experts from within NASA, academia and industry to facilitate mapping of the path to support autonomous medical operations. Topics explored in these meetings included the scope of data (storage capacity, usage, transmission rate and bandwidth, computing capacity), CMO training, supply and resource management and task load balance. Recommendations from these meetings will inform the EIMO Concept of Operations and definition of the associated requirements culminating in updates to the NASA 3001 standards. The EIMO project team will work with stakeholders to conceptualize a clinical decision support system (CDSS) to assist the CMO in response to medical contingencies when terrestrial support is delayed or otherwise unavailable. The CDSS will be a system of systems that will utilize data from numerous input vectors. Successful deployment of the CDSS will facilitate medical decision making while decreasing the cognitive load leading to an improvement in task load balancing. Additional benefits of the envisioned CDSS include assistance with inventory management, locating resources, storage/retrieval of medical records, highlighting trends in recorded data, in addition to providing a consult for diagnosis and treatment. More advanced features might include passive monitoring to identify early warning signs of behavioral or medical anomalies to possibly pre-empt onset of conditions that would compromise crew health and performance.

Benjamin Easter↗
NASA NTRS2020

Conducting Efficient Remote Science and Planning Operations for Ocean Exploration Using Exploration Ground Data Systems (xGDS)

NASA Ames’ Exploration Ground Data Systems (xGDS) supports rapid scientific decision making by synchronizing information in time and space, including video and still images, scientific instrument data, and science and operations notes in geographic and temporal context. We have deployed xGDS at multiple NASA field analog missions over the past decade. In the last two years, we have participated in SUBSEA, a multi-institution collaborative project*. SUBSEA used the research ship E/V Nautilus along with its two remotely operated vehicles (ROVs), Hercules and Argus, to explore deep ocean volcanic vents as an analog for ocean worlds (e.g. Enceladus). This work allowed us to compare the existing oceanographic operations methods and technologies used for ocean exploration with corresponding tools and approaches developed and used at NASA. In the first year of SUBSEA we observed existing remote science operations from the Inner Space Center (ISC)**. In the second year, we deployed xGDS at ISC to complement existing capabilities with xGDS tools designed to support remote Nautilus science operations from the ISC. During operations, video, ROV position and instrument telemetry were streamed from the ship to the ISC. As the science team watched dive operations, they could annotate the data with observations that were relevant to their work domain. Later, the team members could review the data at their own pace to collaboratively develop a dive plan for the next day, which had to be delivered on a fixed daily schedule. The opportunity to compare operations under different conditions enabled us to make several key observations about conducting remote science and planning operations efficiently: (i) Reviewing data collaboratively and interactively with temporal and spatial context was critical for the remote science team’s ability to plan dive operations on the Nautilus. (ii) Science team members were actively engaged with the remote dive operations because they could interact with the collected data and visualize it as they desired. (iii) Being able to replay past events at accelerated speeds, and jump to points in time and spaced based on search results, provided efficient access to critical points of interest in a massive volume of data, so the remote science team could deliver plans on time. * SUBSEA (Systematic Underwater Biogeochemical Science and Exploration Analog) is a multi-institution collaboration supported by NASA, NOAA’s Office of Exploration Research (OER), the Ocean Exploration Trust (OET) and the University of Rhode Island’s Graduate School of Oceanography (GSO).

Cohen, Tamar E.↗
NASA NTRSDate not supplied

2021 NE-XF Pathways Internship Student Showcase Presentation

Branch of Fluid Mechanics concern with the mechanics and properties of gases and its application to engineering systems. Applications of Pneumatics in the Aerospace systems: (1) Flight Hardware - Reaction Control, Systems, Rocket Pressure Fed Systems (2) Ground Operations – Valve Actuation, Inert Environment (Purge), Tube Drying/Cleaning NE-XFPneumatics Engineering provides design & operation expertise to support EGS. Commodities used at KSC systems: Gaseous Helium (GHe) Gaseous Oxygen (GO2) Gaseous Nitrogen (GN2) Breathing Air (BAIR) Support other subsystems: LH2, LO2, Ground Main Propulsion System (GMPS), etc.

Environmental and Life Support Systems↗
NASA NTRS2002

Lessons Learned In Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The "pieces" are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗
NASA NTRS2002

Lessons Learned in Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The pieces are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗
NASA NTRS2001

The Standard Autonomous File Server, a Customized, Off-the-Shelf Success Story

The Standard Autonomous File Server (SAFS), which includes both off-the-shelf hardware and software, uses an improved automated file transfer process to provide a quicker, more reliable, prioritized file distribution for customers of near real-time data without interfering with the assets involved in the acquisition and processing of the data. It operates as a stand-alone solution, monitoring itself, and providing an automated fail-over process to enhance reliability. This paper will describe the unique problems and lessons learned both during the COTS selection and integration into SAFS, and the system's first year of operation in support of NASA's satellite ground network. COTS was the key factor in allowing the two-person development team to deploy systems in less than a year, meeting the required launch schedule. The SAFS system his been so successful, it is becoming a NASA standard resource, leading to its nomination for NASA's Software or the Year Award in 1999.

Semancik, Susan K.↗
NASA NTRS2001

A Fully Redundant On-Line Mass Spectrometer System Used to Monitor Cryogenic Fuel Leaks on the Space Shuttle

An on-line gas monitoring system was developed to replace the older systems used to monitor for cryogenic leaks on the Space Shuttles before launch. The system uses a mass spectrometer to monitor multiple locations in the process, which allows the system to monitor all gas constituents of interest in a nearly simultaneous manner. The system is fully redundant and meets all requirements for ground support equipment (GSE). This includes ruggedness to withstand launch on the Mobile Launcher Platform (MLP), ease of operation, and minimal operator intervention. The system can be fully automated so that an operator is notified when an unusual situation or fault is detected. User inputs are through personal computer using mouse and keyboard commands. The graphical user interface is very intuitive and easy to operate. The system has successfully supported four launches to date. It is currently being permanently installed as the primary system monitoring the Space Shuttles during ground processing and launch operations. Time and cost savings will be substantial over the current systems when it is fully implemented in the field. Tests were performed to demonstrate the performance of the system. Low limits-of-detection coupled with small drift make the system a major enhancement over the current systems. Though this system is currently optimized for detecting cryogenic leaks, many other gas constituents could be monitored using the Hazardous Gas Detection System (HGDS) 2000.

Griffin, Timothy P.↗
NASA NTRS2010

The Next Generation of Ground Operations Command and Control; Scripting in C no. and Visual Basic

Scripting languages have become a common method for implementing command and control solutions in space ground operations. The Systems Test and Operations Language (STOL), the Huntsville Operations Support Center (HOSC) Scripting Language Processor (SLP), and the Spacecraft Control Language (SCL) offer script-commands that wrap tedious operations tasks into single calls. Since script-commands are interpreted, they also offer a certain amount of hands-on control that is highly valued in space ground operations. Although compiled programs seem to be unsuited for interactive user control and are more complex to develop, Marshall Space flight Center (MSFC) has developed a product called the Enhanced and Redesign Scripting (ERS) that makes use of the graphical and logical richness of a programming language while offering the hands-on and ease of control of a scripting language. ERS is currently used by the International Space Station (ISS) Payload Operations Integration Center (POIC) Cadre team members. ERS integrates spacecraft command mnemonics, telemetry measurements, and command and telemetry control procedures into a standard programming language, while making use of Microsoft's Visual Studio for developing Visual Basic (VB) or C# ground operations procedures. ERS also allows for script-style user control during procedure execution using a robust graphical user input and output feature. The availability of VB and C# programmers, and the richness of the languages and their development environment, has allowed ERS to lower our "script" development time and maintenance costs at the Marshall POIC.

Ritter, George↗
NASA NTRS1985

Mathematical models for space shuttle ground systems

Math models are a series of algorithms, comprised of algebraic equations and Boolean Logic. At Kennedy Space Center, math models for the Space Shuttle Systems are performed utilizing the Honeywell 66/80 digital computers, Modcomp II/45 Minicomputers and special purpose hardware simulators (MicroComputers). The Shuttle Ground Operations Simulator operating system provides the language formats, subroutines, queueing schemes, execution modes and support software to write, maintain and execute the models. The ground systems presented consist primarily of the Liquid Oxygen and Liquid Hydrogen Cryogenic Propellant Systems, as well as liquid oxygen External Tank Gaseous Oxygen Vent Hood/Arm and the Vehicle Assembly Building (VAB) High Bay Cells. The purpose of math modeling is to simulate the ground hardware systems and to provide an environment for testing in a benign mode. This capability allows the engineers to check out application software for loading and launching the vehicle, and to verify the Checkout, Control, & Monitor Subsystem within the Launch Processing System. It is also used to train operators and to predict system response and status in various configurations (normal operations, emergency and contingent operations), including untried configurations or those too dangerous to try under real conditions, i.e., failure modes.

Tory, E. G.↗
NASA NTRS2015

Demonstrating Autonomous Mission Operations Onboard the International Space Station

The NASA Autonomous Mission Operations (AMO) project conducted an experiment to turn over operation and management of selected International Space Station (ISS) sys- tems to the on-board crew. ISS crews managed two different spacecraft systems: the Total Organic Carbon Analyzer (TOCA), a water quality analyzer, and Station Support Com- puters (SSC) laptops, which are non-critical crew computer systems. These systems were selected because they are representative of systems a future crew may need to operate au- tonomously during a deep space mission. The crew autonomously operated these systems, taking on mission operations functions traditionally performed by support teams on the ground, using new software tools that provide decision support algorithms for planning, monitoring and fault management, hardware schematics, system briefs, and data displays that are normally unavailable to the crew. The experiment lasted seven months, during which ISS crews managed TOCA and SSCs on 22 occasions. The AMO software processed data from TOCA and SSCs continuously during this seven month period. The combined performance of the software and crew achieved a 88 success rate on managing TOCA activity, the system for which ground-truth was available.

Autonomous Mission Operations↗