SEARCH · Engineering Papers

Results for “System Operations”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,153 records · Page 64

All sources NASA NTRS DOE OSTI

NASA NTRS2017

The Use of a Satellite Communications System for Command and Control of the National Aeronautics and Space Administration Surrogate Unmanned Aerial System Research Aircraft

The NASA Langley Research Center has transformed a Cirrus Design SR22 general aviation (GA) aircraft into an Unmanned Aerial Systems (UAS) Surrogate research aircraft which has served for several years as a platform for unmanned systems research and development. The aircraft is manned with a Safety Pilot and a Research Systems Operator (RSO) that allows for flight operations almost any-where in the national airspace system (NAS) without the need for a Federal Aviation Administration (FAA) Certificate of Authorization (COA). The UAS Surrogate can be remotely controlled from a modular, transportable ground control station (GCS) like a true UAS. Ground control of the aircraft is accomplished by the use of data links that allow the two-way passage of the required data to control the aircraft and provide the GCS with situational awareness. The original UAS Surrogate data-link system was composed of redundant very high frequency (VHF) data radio modems with a maximum range of approximately 40 nautical miles. A new requirement was developed to extend this range beyond visual range (BVR). This new requirement led to the development of a satellite communications system that provided the means to command and control the UAS Surrogate at ranges beyond the limits of the VHF data links. The system makes use of the Globalstar low earth orbit (LEO) satellite communications system. This paper will provide details of the development, implementation, and flight testing of the satellite data communications system on the UAS Surrogate research aircraft.

Howell, Charles T.↗

NASA NTRS1974

Medical results of the Skylab program

The Skylab food system, waste management system, operational bioinstrumentation, personal hygiene provisions, in-flight medical support system, and the cardiovascular counterpressure garment worn during reentry are described. The medical experiments program provided scientific data and also served as the basis for real-time decisions on flight duration. Premission support, in-flight operational support, and postflight medical activities are surveyed. Measures devised to deal with possible food spoilage, medical instrument damage, and toxic atmosphere caused by the initial failures on the Orbital Workshop (OWS) are discussed. The major medical experiments performed in flight allowed the study of physiological changes as a function of exposure to weightless flight. The experiments included studies of the cardiovascular system, musculoskeletal and fluid/electrolyte balance, sleep, blood, vestibular system, and time and motion studies.

Johnston, R. S.↗

NASA NTRS1983

Parallel, Asynchronous Executive (PAX): System concepts, facilities, and architecture

The Parallel, Asynchronous Executive (PAX) is a software operating system simulation that allows many computers to work on a single problem at the same time. PAX is currently implemented on a UNIVAC 1100/42 computer system. Independent UNIVAC runstreams are used to simulate independent computers. Data are shared among independent UNIVAC runstreams through shared mass-storage files. PAX has achieved the following: (1) applied several computing processes simultaneously to a single, logically unified problem; (2) resolved most parallel processor conflicts by careful work assignment; (3) resolved by means of worker requests to PAX all conflicts not resolved by work assignment; (4) provided fault isolation and recovery mechanisms to meet the problems of an actual parallel, asynchronous processing machine. Additionally, one real-life problem has been constructed for the PAX environment. This is CASPER, a collection of aerodynamic and structural dynamic problem simulation routines. CASPER is not discussed in this report except to provide examples of parallel-processing techniques.

Jones, W. H.↗

NASA NTRS1985

The SIFT hardware/software systems. Volume 2: Software listings

This document contains software listings of the SIFT operating system and application software. The software is coded for the most part in a variant of the Pascal language, Pascal*. Pascal* is a cross-compiler running on the VAX and Eclipse computers. The output of Pascal* is BDX-390 assembler code. When necessary, modules are written directly in BDX-390 assembler code. The listings in this document supplement the description of the SIFT system found in Volume 1 of this report, A Detailed Description.

Palumbo, Daniel L.↗

NASA NTRS2018

Astrobee Robot Software: A Modern Software System for Space

Astrobee is a new free-flyer robot designed to operate inside the International Space Station (ISS). Astrobee capabilities include markerless navigation, autonomous docking for recharge, perching on handrails to minimize power and modular payloads. Astrobee will operate without crew support, controlled by teleoperation, plan execution, or on-board third parties software. This paper presents the Astrobee Robot Software, a NASA Open-Source project, powering the Astrobee robot. The Astrobee Robot Software relies on a distributed architecture based on the Robot Operating System (ROS). The software runs on three interconnected smart phone class processors. We present the software approach, infrastructure required, and main software components. The Astrobee Robot Software embrace modern software practices while respecting flight constraints. The paper concludes with the lessons learned, including examples usage of the software. Several research teams are already using the Astrobee Robot Software to develop novel projects that will fly on Astrobee.

Astrobee↗

NASA NTRS1994

Use of Multimission System for Cost Effective Support of Planetary Science Data Processing

JPL's Multimission Operations System Office (MOSO) provides a multimission facility at JPL for processing science instrument data from NASA's planetary missions.

system↗

NASA NTRS2017

Creative Analytics of Mission Ops Event Messages

Historically, tremendous effort has been put into processing and displaying mission health and safety telemetry data; and relatively little attention has been paid to extracting information from missions time-tagged event log messages. Todays missions may log tens of thousands of messages per day and the numbers are expected to dramatically increase as satellite fleets and constellations are launched, as security monitoring continues to evolve, and as the overall complexity of ground system operations increases. The logs may contain information about orbital events, scheduled and actual observations, device status and anomalies, when operators were logged on, when commands were resent, when there were data drop outs or system failures, and much much more. When dealing with distributed space missions or operational fleets, it becomes even more important to systematically analyze this data. Several advanced information systems technologies make it appropriate to now develop analytic capabilities which can increase mission situational awareness, reduce mission risk, enable better event-driven automation and cross-mission collaborations, and lead to improved operations strategies: Industry Standard for Log Messages. The Object Management Group (OMG) Space Domain Task Force (SDTF) standards organization is in the process of creating a formal standard for industry for event log messages. The format is based on work at NASA GSFC. Open System Architectures. The DoD, NASA, and others are moving towards common open system architectures for mission ground data systems based on work at NASA GSFC with the full support of the commercial product industry and major integration contractors. Text Analytics. A specific area of data analytics which applies statistical, linguistic, and structural techniques to extract and classify information from textual sources. This presentation describes work now underway at NASA to increase situational awareness through the collection of non-telemetry mission operations information into a common log format and then providing display and analytics tools to provide in-depth assessment of the log contents. The work includes: Common interface formats for acquiring time-tagged text messages Conversion of common files for schedules, orbital events, and stored commands to the common log format Innovative displays to depict thousands of messages on a single display Structured English text queries against the log message data store, extensible to a more mature natural language query capability Goal of speech-to-text and text-to-speech additions to create a personal mission operations assistant to aid on-console operations. A wide variety of planned uses identified by the mission operations teams will be discussed.

events↗

NASA NTRS1989

Advanced Manned Launch Systems

Advanced Manned Launch Systems (AMLS) studies underway at the NASA Langley Research Center are part of a broader effort examining options for the next U.S. manned space transportation system. AMLS study phases have focused on investigating mission needs and identifying technologies and technology levels, concepts, systems, operational requirements, and life-cycle costs. For near-term technologies and an operations-oriented approach, two-stage vertical-takeoff rocket vehicles with significant levels of reusability are shown to be cost-effective for moderate to high flight rates. All-hydrogen fuel vehicles are also preferred over methane boosted systems from both operational and cost considerations.

Talay, Theodore A.↗

NASA NTRS2018

UTM and D-NET: NASA and JAXA's Collaborative Research on Integrating Small UAS with Disaster Response Efforts

Natural disasters, such as flooding, wildfire, hurricane, tornadoes, earthquakes and tsunamis, pose challenges in preserving human life and minimizing the damages to a region. During catastrophic events, timely response of disaster relief personnel, an efficient deployment of resources in the recovery effort, and coordinated information sharing amongst different relief agencies can make a substantial difference in responding to those impacted by the disaster. Many relief activities currently utilize both ground personnel and manned airborne assets during different phases of the disaster response. Typically, multiple organizations support relief activities and this often creates logistics coordination challenges between agencies which can result in wasted time or resources. The Japan Aerospace Exploration Agency (JAXA) has been developing an "Integrated aircraft operation system for disaster relief (D-NET)", which assists collection and sharing of disaster information through the integrated operation of aircraft such as helicopters, aircraft, and satellites, for efficient and safe rescue operations by disaster relief aircraft. Due to the advancement in unmanned aircraft systems (UAS) technologies, public safety organizations have started incorporating small UAS (sUAS) as an asset in their disasters response activities. To address the airspace integration challenges of the influx of sUAS in the United States the National Aeronautics and Space Administration (NASA), under the UAS Traffic Management (UTM) project, has been engaged in research to enable large-scale commercial applications of sUAS operating in low altitude airspace. This paper presents the integration of D-NET, which incorporate sUAS in the planning, information sharing, and operation support of disasters response activities, and UTM, which provides airspace management to enable large scale high density operations. The integration of the DNET and UTM systems enables coordination, data sharing, and airspace management to improve the timeliness of the disaster response, enable relief organization to reduce cost and overhead by using UAS assets and still maintain airspace safety during the relief activities.

UTM↗

NASA NTRS1980

Initial guidelines and estimates for a power system with inertial (flywheel) energy storage

The starting point for the assessment of a spacecraft power system utilizing inertial (flywheel) energy storage. Both general and specific guidelines are defined for the assessment of a modular flywheel system, operationally similar to but with significantly greater capability than the multimission modular spacecraft (MMS) power system. Goals for the flywheel system are defined in terms of efficiently train estimates and mass estimates for the system components. The inertial storage power system uses a 5 kw-hr flywheel storage component at 50 percent depth of discharge (DOD). It is capable of supporting an average load of 3 kw, including a peak load of 7.5 kw for 10 percent of the duty cycle, in low earth orbit operation. The specific power goal for the system is 10 w/kg, consisting of a 56w/kg (end of life) solar array, a 21.7 w-hr/kg (at 50 percent DOD) flywheel, and 43 w/kg power processing (conditioning, control and distribution).

Slifer, L. W., Jr.↗

NASA NTRSDate not supplied

Design of Space Systems to Enable In-space Assembly and Servicing

For several decades, NASA has employed in-space systems to enhance the performance and extend the useful life of operational orbital assets. In at least one case, an operational mission was not only enhanced, but enabled – the International Space Station was made possible by crewed and robotic in-space assembly, and continues to support installation and operation of new science and technology payloads. In several cases (Hubble Space Telescope, Intelsat 401, Westar and Palapa), major operational assets were rescued or repaired soon after launch when otherwise mission-ending anomalies occurred or were detected. In addition to the original rescue, Hubble was upgraded four times, enabling high-demand, world class science over four decades. More recently, two Northrop Grumman Mission Extension Vehicles have captured two Intelsat spacecraft near the end of their life and fuel capacity, to take over maneuvering duties. In spite of these recent operational achievements, and with the exception of large human exploration vehicles and large space telescopes, space architects rarely consider in-orbit servicing and assembly capabilities in their future planning. Technologies such as multi-launch mission architectures (and rendezvous and proximity operations systems), docking systems, external robotics, advanced tools, modular systems and structures, and fluid transfer systems are available today to support these missions. In-space manufacturing will soon be operational to enable resilient missions that recover from on-orbit failures, and expand the utilization of space. We envision a future that includes these capabilities, and discuss the cultural, engineering, and technological challenges to achieving this vision. We discuss the vision, the proverbial chicken and the egg (which came first, the serviceable spacecraft or the servicer?), the cost, risk, and perceptions thereof of in-space operations, a “spectrum” of cooperative servicing design considerations, and the current status of the space industry’s slow but steady march to widespread operational use of on-orbit servicing, assembly, and manufacturing.

Bo Naasz↗

NASA NTRS1982

Field operations with cesium clocks in HF navigation systems

Networks of HF phase comparison marine navigation stations employing cesium clocks are discussed. The largest permanent network is in the Gulf of Mexico where some fourteen base stations are continuously active and others are activated as needed. These HF phase comparison systems, which operate on a single transmission path, require a clock on the mobile unit as well. Inventory consists of upwards of 70 clocks from two different manufacturers. The maintenance of this network as an operating system requires a coordinated effort involving clock preparation, clock environment control, station performance monitoring and field service.

Christy, E. H.↗

NASA NTRS1992

Advanced information processing system: The Army fault tolerant architecture conceptual study. Volume 2: Army fault tolerant architecture design and analysis

Described here is the Army Fault Tolerant Architecture (AFTA) hardware architecture and components and the operating system. The architectural and operational theory of the AFTA Fault Tolerant Data Bus is discussed. The test and maintenance strategy developed for use in fielded AFTA installations is presented. An approach to be used in reducing the probability of AFTA failure due to common mode faults is described. Analytical models for AFTA performance, reliability, availability, life cycle cost, weight, power, and volume are developed. An approach is presented for using VHSIC Hardware Description Language (VHDL) to describe and design AFTA's developmental hardware. A plan is described for verifying and validating key AFTA concepts during the Dem/Val phase. Analytical models and partial mission requirements are used to generate AFTA configurations for the TF/TA/NOE and Ground Vehicle missions.

Harper, R. E.↗

NASA NTRSDate not supplied

Developing a Medical System Concept of Operations for Level of Care IV: Long-Duration Lunar Orbital and Surface Operations

A goal of the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element Systems Engineering (SE) team is to define the technical system needed to support crew medical system capabilities for future exploration missions, including a mission with lunar orbital and long duration surface operations. The medical system concept of operations (ConOps) is the starting point of creating a foundation for a medical system that meets Level of Care IV requirements, as defined by NASA’s space flight human-system standards. This ConOps illustrates how NASA can provide a Level of Care IV medical system for crews within the various cis-lunar orbit and lunar surface habitat environments. The use case scenarios included in this ConOps illustrate required medical system capabilities for Level of Care IV and enable the ExMC SE team to develop integrated medical system requirements and identify capabilities required to meet those requirements. This discussion will focus on how this concept of operations was constructed – by utilizing the lessons learned from ExMC’s existing Short-Duration Lunar Orbit Medical System Concept of Operations, by employing Model-Based Systems Engineering, and by collaborating with stakeholders in order to ensure the necessary assumptions were made.

M. Kaetzer↗

NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy M. Mclaughlin↗

NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

Kassidy McLaughlin↗

NASA NTRS2010

Space Operations for a New Era of Exploration Launch Vehicles

NASA's Constellation Program is depending on the Ares Projects to deliver the crew and cargo launch capabilities needed to send human explorers to the Moon and beyond. Ares I and V will provide the core space launch capabilities needed to continue providing crew and cargo access to the International Space Station (ISS), and to build upon the U.S. history of human space exploration. Since 2005, Ares has made substantial progress on designing, developing, and testing the Ares I crew launch vehicle and has continued its in-depth studies of the Ares V cargo launch vehicles. The combined Ares I/Ares V architecture has been designed to reduce the complexity and labor intensity of ground operations for America's next journeys beyond low-Earth orbit (LEO). A deliberate effort is being made to ensure a high level of system operability to significantly increase safety and system availability as well as reduce recurring costs for this new launch vehicle. The Ares Projects goal is to instill operability as part of the vehicles requirements development, design, and operations. This simplicity will come from using simpler, proven engine designs, as in the case of the J-2X upper stage engine and RS-68 engine; improving existing hardware, as in the case of the Shuttle-heritage 5-segment solid rocket motor; and using common propulsion and instrument unit elements between Ares I and Ares V. Furthermore, lessons learned while developing Ares I will be applied directly to Ares V operations. In 2009, the Ares Projects plan to conduct the first flight test of Ares I, designated Ares I-X. Ares I-X preparations have already prompted changes to the vehicle stacking and launch infrastructure at Kennedy Space Center (KSC), including removing Shuttle-specific fixtures from the Vehicle Assembly Building (VAB) to accommodate Ares I-style stacking operations, new firing room computers and infrastructure in the VAB Launch Control Center, and new lightning protection system towers at Launch Complex 39B to accommodate the greater height of Ares I-X. In addition to lessons learned from the stacking of Ares I-X, the flight test itself promises to yield important data and operations lessons for assembling, launching, and flying Ares I.

Cook, Stephen A.↗

NASA NTRS2000

Applying Contamination Modelling to Spacecraft Propulsion Systems Designs and Operations

Molecular and particulate contaminants generated from the operations of a propulsion system may impinge on spacecraft critical surfaces. Plume depositions or clouds may hinder the spacecraft and instruments from performing normal operations. Firing thrusters will generate both molecular and particulate contaminants. How to minimize the contamination impact from the plume becomes very critical for a successful mission. The resulting effect from either molecular or particulate contamination of the thruster firing is very distinct. This paper will discuss the interconnection between the functions of spacecraft contamination modeling and propulsion system implementation. The paper will address an innovative contamination engineering approach implemented from the spacecraft concept design, manufacturing, integration and test (I&T), launch, to on- orbit operations. This paper will also summarize the implementation on several successful missions. Despite other contamination sources, only molecular contamination will be considered here.

Chen, Philip T.↗