Engineering Papers⌕ Search

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.

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

At least 919 records · Page 51
All sourcesNASA NTRSDOE OSTI
NASA NTRS1975

Networks systems and operations

The application of wideband communication techniques for data links with satellites is discussed. A diagram of the demand assigned voice communications system is provided. The development of prototype integrated spacecraft paramps at S- and C-bands is described and the performance of space-qualified paramps is tabulated. The characteristics of a dual parabolic cylinder monopulse zoom antenna for use with the tracking and data relay satellite system (TDRSS) are analyzed. The development of a universally applicable transponder at S-band is reported. A block diagram of the major subassemblies of the S-band transponder is included. The technology aspects of network timing and synchronization of communication systems are to show the use of the Omega navigation system. The telemetry data compression system used during the Skylab program is evaluated.

Source record↗
NASA NTRS2012

Energy Systems Test Area (ESTA) Electrical Power Systems Test Operations: User Test Planning Guide

Test process, milestones and inputs are unknowns to first-time users of the ESTA Electrical Power Systems Test Laboratory. The User Test Planning Guide aids in establishing expectations for both NASA and non-NASA facility customers. The potential audience for this guide includes both internal and commercial spaceflight hardware/software developers. It is intended to assist their test engineering personnel in test planning and execution. Material covered includes a roadmap of the test process, roles and responsibilities of facility and user, major milestones, facility capabilities, and inputs required by the facility. Samples of deliverables, test article interfaces, and inputs necessary to define test scope, cost, and schedule are included as an appendix to the guide.

Salinas, Michael J.↗
NASA NTRS1994

Increases in Efficiency and Enhancements to the Mars Observer Non-stored Commanding Process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a Mission Operations System which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for the mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from Total Quality Management (TQM). This tool is known as a Process Action Team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's non-stored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was to, in fact, increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. The results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures. This paper will describe in detail the enhancements recommended by the PAT for the non-stored command generation process on Mars Observer. This will be contrasted with the process used by the flight team prior to implementation of these improvements. Finally, there will be a discussion of the applicability of the techniques devised by the PAT for enhancement of the non-stored command process to present and future projects.

Process↗
DOE OSTI2020

Distributed Conditions for Small-signal Stability of Power Grids and Local Control Design

Operating modern power grids with stability guarantees is markedly important. Typical methods for analyzing and certifying power grid stability are largely centralized relying on the ability of the system operator to gather network-wide information and accurately compute the system's eigenvalues. These methods are oftentimes not privacy-preserving and computationally burdensome. They are therefore, not well-suited to modern power grids where small-signal stability has to be evaluated timely, efficiently and in a privacy-preserving fashion. Herein, we introduce a distributed methodology for certifying small-signal stability of power grids and designing the local controllers. First, we analytically derive distributed conditions for network-wide stability that bus agents can inspect using local information. By leveraging these conditions, we then introduce a distributed control design algorithm (DCDA) that can guide the local control design so that stability of the interconnected system is guaranteed. The agents that adopt the proposed distributed algorithm are responsible for tuning their local controllers, producing their local control commands and ensuring that their local stability condition is met. The system operator is only responsible for verifying network-wide stability upon receiving affirmative responses from all agents and, announcing, that the overall system is stable. The proposed DCDA algorithm is numerically validated via simulations using the IEEE 39-bus system.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2024

Common Electric Power Transmission System Model JSON Schema Specification

The Common Electric Power Transmission System Model (CTM) is an intuitive, extensible, language-agnostic, and error-resistant specification of electric power network components parameter names and units, and relation between components, intended for use by the research community developing new computational methods for power systems operations and simulation. Power system datasets following the CTM specification can be read as dictionaries and manipulated in that form in most programming languages (e.g., Python, Julia, C++). This standard data structure in CTM makes it easy to work in multiple power systems domains (e.g., economic operation, reliability assessment, electricity markets, stability assessment, etc.) without requiring conversions between use-case-specific file formats with information loss in the process. This repository specifies CTM as a JSON Schema, provides documentation, derivate (code-generated) implementations of CTM, and example data and usage of the schema for important use cases.

Aravena Solis, Ignacio↗
NASA NTRS1985

Ada Run Time Support Environments and a common APSE Interface Set

The paper discusses the importance of linking Ada Run Time Support Environments to the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). A non-stop network operating systems scenario is presented to serve as a forum for identifying the important issues. The network operating system exemplifies the issues involved in the NASA Space Station data management system.

Mckay, C. W.↗
NASA NTRS1990

Evaluation of the Trajectory Operations Applications Software Task (TOAST)

The Trajectory Operations Applications Software Task (TOAST) is a software development project under the auspices of the Mission Operations Directorate. Its purpose is to provide trajectory operation pre-mission and real-time support for the Space Shuttle program. As an Application Manager, TOAST provides an isolation layer between the underlying Unix operating system and the series of user programs. It provides two main services: a common interface to operating system functions with semantics appropriate for C or FORTRAN, and a structured input and output package that can be utilized by user application programs. In order to evaluate TOAST as an Application Manager, the task was to assess current and planned capabilities, compare capabilities to functions available in commercially-available off the shelf (COTS) and Flight Analysis Design System (FADS) users for TOAST implementation. As a result of the investigation, it was found that the current version of TOAST is well implemented and meets the needs of the real-time users. The plans for migrating TOAST to the X Window System are essentially sound; the Executive will port with minor changes, while Menu Handler will require a total rewrite. A series of recommendations for future TOAST directions are included.

Perkins, Sharon↗
NASA NTRS1994

Increases in efficiency and enhancements to the Mars Observer non-stored commanding process

The Mars Observer team was, until the untimely loss of the spacecraft on August 21, 1993, performing flight operations with greater efficiency and speed than any previous JPL mission of its size. This level of through-put was made possible by a mission operations system which was composed of skilled personnel using sophisticated sequencing and commanding tools. During cruise flight operations, however, it was realized by the project that this commanding level was not going to be sufficient to support the activities planned for mapping operations. The project had committed to providing the science instrument principle investigators with a much higher level of commanding during mapping. Thus, the project began taking steps to enhance the capabilities of the flight team. One mechanism used by project management was a tool available from total quality management (TQM). This tool is known as a process action team (PAT). The Mars Observer PAT was tasked to increase the capacity of the flight team's nonstored commanding process by fifty percent with no increase in staffing and a minimal increase in risk. The outcome of this effort was, in fact, to increase the capacity by a factor of 2.5 rather than the desired fifty percent and actually reduce risk. The majority of these improvements came from the automation of the existing command process. These results required very few changes to the existing mission operations system. Rather, the PAT was able to take advantage of automation capabilities inherent in the existing system and make changes to the existing flight team procedures.

Brooks, Robert N., Jr.↗
NASA NTRS2017

Agile: From Software to Mission Systems

To maximize efficiency and flexibility in Mission Operations System (MOS) design, we are evolving principles from agile and lean methods for software, to the complete mission system. This allows for reduced operational risk at reduced cost, and achieves a more effective design through early integration of operations into mission system engineering and flight system design. The core principles are assessment of capability through demonstration, risk reduction through targeted experiments, early test and deployment, and maturation of processes and tools through use.

Trimble, Jay↗
DOE OSTI2021

Roles of Dynamic State Estimation in Power System Modeling, Monitoring and Operation

—Power system dynamic state estimation (DSE) remains an active research area. This is driven by the absence of accurate models, the increasing availability of fast-sampled, time synchronized measurements, and the advances in the capability, scalability, and affordability of computing and communications. This paper discusses the advantages of DSE as compared to static state estimation, and the implementation differences between the two, including the measurement configuration, modeling framework and support software features. The important roles of DSE are discussed from modeling, monitoring and operation aspects for today’s synchronous machine dominated systems and the future power electronics-interfaced generation systems. Several examples are presented to demonstrate the benefits of DSE on enhancing the operational robustness and resilience of 21st century power system through time critical applications. Future research directions are identified and discussed, paving the way for developing the next generation of energy management systems.

Zhao, Junbo↗
NASA NTRS2009

Development of a Portable Oxygen Monitoring System for Operations in the International Space Station Airlock

NASA is currently engaged in an activity to facilitate effective operations on the International Space Station (ISS) after the Space Shuttle retires. Currently, the Space Shuttle delivers crew and cargo to and from ISS. The Space Shuttle provides the only large scale method of hardware return from ISS to the ground. Hardware that needs to be periodically repaired, refurbished, or recalibrated must come back from ISS on the Shuttle. One example of NASA flight hardware that is used on ISS and refurbished on the ground is the Compound Specific Analyzer for Oxygen (CSA-O2). The CSA-O2 is an electrochemical sensor that is used on orbit for about 12 months (depending on Shuttle launch schedules), then returned to the ground for sensor replacement. The shuttle is scheduled to retire in 2010, and the ISS is scheduled to operate until 2016. NASA needs a hand held sensor that measures oxygen in the ISS environment and has a 5-10 year service life. After conducting a survey of oxygen sensor systems, NASA selected a Tunable Diode Laser Absorption Spectrometer (TDLAS) as the method of measurement that best addresses the needs for ISS. These systems are compact, meet ISS accuracy requirements, and because they use spectroscopic techniques, the sensors are not consumed or altered after making a measurement. TDLAS systems have service life ratings of 5-10 years, based on the lifetime of the laser. NASA is engaged in modifying a commercially available sensor, the Vaisala OMT 355, for the ISS application. The Vaisala OMT 355 requires three significant modifications to meet ISS needs. The commercial sensor uses a wall mount power supply, and the ISS sensor needs to use a rechargeable battery as its source of power. The commercial sensor has a pressure correction setpoint: the sensor can be adjusted to operate at reduced pressure conditions, but the sensor does not self correct dynamically and automatically. The ISS sensor needs to operate in the airlock, and make accurate measurements in an environment that can change from 14.7 psia to 10.2 psia in 15 minutes. The commercial sensor needs to be repackaged into a configuration that is more compact, and better suited for ISS airlock operations. NASA has recently completed a prototype of the reconfigured system. The unit has been repackaged in a way that the optical path of the spectrometer is unchanged, but the electronics has been integrated into a case measuring 10.7 X 7.2 X 3.0 inches. Two flight qualified rechargeable batteries have been integrated into system. The batteries can power the sensor for 10 hours on a single charge. A pressure sensor has been added to the system. The modified unit automatically compensates for changes in pressure, and meets 0.2% accuracy requirements for oxygen measurements in an environment with 18 to 32% oxygen across a pressure range of 10.0 to 15.0 psia.

Graf, John↗
NASA NTRS2004

Updated System-Availability and Resource-Allocation Program

A second version of the Availability, Cost and Resource Allocation (ACARA) computer program has become available. The first version was reported in an earlier tech brief. To recapitulate: ACARA analyzes the availability, mean-time-between-failures of components, life-cycle costs, and scheduling of resources of a complex system of equipment. ACARA uses a statistical Monte Carlo method to simulate the failure and repair of components while complying with user-specified constraints on spare parts and resources. ACARA evaluates the performance of the system on the basis of a mathematical model developed from a block-diagram representation. The previous version utilized the MS-DOS operating system and could not be run by use of the most recent versions of the Windows operating system. The current version incorporates the algorithms of the previous version but is compatible with Windows and utilizes menus and a file-management approach typical of Windows-based software.

Viterna, Larry↗
NASA NTRS2024

FRAAME Version 1.0 User Manual

The code for Forced Response Aeromechanics Analysis in a MATLAB-based (The MathWorks, Inc.) Environment (FRAAME Version 1.0) was developed for internal use in aeromechanics efforts undertaken at the NASA Glenn Research Center for computing turbomachine component forced response and Goodman diagrams via modal summation method. The main working script (FRAAMEv1.m) allows users to input case-specific manual inputs while the triple-nested loop invokes functions to compute forced response per blade, per nodal diameter, and per mode. Secondly, forced response values are applied to modal stresses to compute complex Von Mises stress values and generate Goodman diagrams per blade, per nodal diameter, and per mode using a linear modal summation method. Currently, this code functions in the Windows (Microsoft Corporation) operating system using MATLAB Version R2023a, but it can be adapted for use in the Linux (Linus Torvalds) operating system by changing the appropriate file path structure in the main script, as well as functions that call external results files.

Aeromechanics↗
NASA NTRS1991

Organizing and Typing Persistent Objects Within an Object-Oriented Framework

Conventional operating systems provide little or no direct support for the services required for an efficient persistent object system implementation. We have built a persistent object scheme using a customization and extension of an object-oriented operating system called Choices. Choices includes a framework for the storage of persistent data that is suited to the construction of both conventional file system and persistent object system. In this paper we describe three areas in which persistent object support differs from file system support: storage organization, storage management, and typing. Persistent object systems must support various sizes of objects efficiently. Customizable containers, which are themselves persistent objects and can be nested, support a wide range of object sizes in Choices. Collections of persistent objects that are accessed as an aggregate and collections of light-weight persistent objects can be clustered in containers that are nested within containers for larger objects. Automated garbage collection schemes are added to storage management and have a major impact on persistent object applications. The Choices persistent object store provides extensible sets of persistent object types. The store contains not only the data for persistent objects but also the names of the classes to which they belong and the code for the operation of the classes. Besides presenting persistent object storage organization, storage management, and typing, this paper discusses how persistent objects are named and used within the Choices persistent data/file system framework.

Madany, Peter W.↗
DOE OSTI2024

Hydropower Flexibility and Environmental Tradeoffs Analysis

The importance of hydropower increases as the power grid evolves with the higher variable renewable contribution. As conventional thermal power plants are retired, the importance of hydropower contribution increases to balance the variability of solar and wind generation. However, reservoir water resources are constrained by multiple constraints, and variability of water inflow to the reservoirs creates limitations to dam water releases for power grid needs. Coordinating multiple tools, including water resources, ecological, and technical and economic power grid modeling, informs dam water releases. The case study, the Columbia River Basin multipurpose reservoir project, is operated for hydropower production and many other purposes considering the aquatic habitat of the river basin. Specifically, the river basin fish population is a vital element for the tribal community of the river basin. We integrated a production cost model, a water resource model, and decades of tribal knowledge to analyze the fish-friendly way of operating Columbia hydropower scheduling and grid impacts. We measure power grid impacts for various water resources planning scenarios in terms of total system operating cost, system reliability indicators, changes in wind and solar generation and curtailments, local marginal prices, and revenue for hydropower producers. The study results inform reservoir operating rules decisions from hydropower power producers, system operators, other water users, tribes, environmentalists, and other stakeholders.

Columbia River↗
NASA NTRS1992

Survivable algorithms and redundancy management in NASA's distributed computing systems

The design of survivable algorithms requires a solid foundation for executing them. While hardware techniques for fault-tolerant computing are relatively well understood, fault-tolerant operating systems, as well as fault-tolerant applications (survivable algorithms), are, by contrast, little understood, and much more work in this field is required. We outline some of our work that contributes to the foundation of ultrareliable operating systems and fault-tolerant algorithm design. We introduce our consensus-based framework for fault-tolerant system design. This is followed by a description of a hierarchical partitioning method for efficient consensus. A scheduler for redundancy management is introduced, and application-specific fault tolerance is described. We give an overview of our hybrid algorithm technique, which is an alternative to the formal approach given.

Malek, Miroslaw↗