SEARCH · Engineering Papers
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.
Long-term and short-term objectives for the development of a network operating system for the Space Station are stated. The short-term objective is to develop a prototype network operating system for a 100 megabit/second fiber optic data bus. The long-term objective is to establish guidelines for writing a detailed specification for a Space Station network operating system. Major milestones are noted. Information is given in outline form.
The ADAMS Executive and Operating System, a multitasking environment under which a variety of data reduction, display and utility programs are executed, a system which provides a high level of isolation between programs allowing them to be developed and modified independently, is described. The Airborne Data Analysis/Monitor System (ADAMS) was developed to provide a real time data monitoring and analysis capability onboard Boeing commercial airplanes during flight testing. It inputs sensor data from an airplane performance data by applying transforms to the collected sensor data, and presents this data to test personnel via various display media. Current utilization and future development are addressed.
Space Robot Operating System (Space ROS) is an open-source software framework for flight-quality robotic and autonomous space systems. It combines the benefits of open-source software and flight software best-practices into a single framework. Space ROS is predicated on ROS2 and is therefore reusable, modular and adoptable. As an open-source framework, it is accessible to the global space community. Space ROS is intended to be compliant with NASA flight software engineering practices in order to facilitate meeting mission and safety standards. Space ROS has fault management and real-time capabilities at its core.
This paper demonstrates a methodology to model and evaluate the fault tolerance characteristics of operational software. The methodology is illustrated through case studies on three different operating systems: the Tandem GUARDIAN fault-tolerant system, the VAX/VMS distributed system, and the IBM/MVS system. Measurements are made on these systems for substantial periods to collect software error and recovery data. In addition to investigating basic dependability characteristics such as major software problems and error distributions, we develop two levels of models to describe error and recovery processes inside an operating system and on multiple instances of an operating system running in a distributed environment. Based on the models, reward analysis is conducted to evaluate the loss of service due to software errors and the effect of the fault-tolerance techniques implemented in the systems. Software error correlation in multicomputer systems is also investigated.
The design requirements and implementation standards for an NSSC-2 operating system are defined. An operating system diagram is presented along with system concepts and terminology.
To ensure the reliability and performance of a new system, it must be verified or validated in some manner. Currently, testing is the only resonable technique available for doing this. Part of this testing process is the high level system test. System testing is considered with respect to operating systems and in particular UNIX. This consideration results in the development and presentation of a good method for performing the system test. The method includes derivations from the system specifications and ideas for management of the system testing project. Results of applying the method to the IBM System/9000 XENIX operating system test and the development of a UNIX test suite are presented.
Economic benefits studies regarding the application of remote sensing to resource management and the Total Earth Resources for the Shuttle Era (TERSSE) study to outline the structure and development of future systems are used, along with experience from LANDSAT and LACIE, to define the system performance and economics of an operational Earth Resources system. The system is to be based on current (LANDSAT follow-on) technology and its application to high priority resource management missions, such as global crop inventory. The TERSSE Operational System Study (TOSS) investigated system-level design alternatives using economic performance as the evaluation criterion. As such, the TOSS effort represented a significant step forward in the systems engineering and economic analysis of Earth Resources programs. By parametrically relating engineering design parameters, such as sensor performance details, to the economic benefit mechanisms a new level of confidence in the conclusions concerning the implementation of such systems can be reached.
The Department of Defense (DoD) defined System Operational Effectiveness (SOE) model provides an exceptional framework for an affordable approach to the development and operation of space launch vehicles and their supporting infrastructure. The SOE model provides a focal point from which to direct and measure technical effectiveness and process efficiencies of space launch vehicles. The application of the SOE model to a space launch vehicle's development and operation effort leads to very specific approaches and measures that require consideration during the design phase. This paper provides a mapping of the SOE model to the development of space launch vehicles for human exploration by addressing the SOE model key points of measurement including System Performance, System Availability, Technical Effectiveness, Process Efficiency, System Effectiveness, Life Cycle Cost, and Affordable Operational Effectiveness. In addition, the application of the SOE model to the launch vehicle development process is defined providing the unique aspects of space launch vehicle production and operations in lieu of the traditional broader SOE context that examines large quantities of fielded systems. The tailoring and application of the SOE model to space launch vehicles provides some key insights into the operational design drivers, capability phasing, and operational support systems.
Probabilistic scenarios of renewable energy production, such as wind, have been gaining popularity for use in stochastic variants of power systems operations scheduling problems, allowing for optimal decision-making under uncertainty. The quality of the scenarios has a direct impact on the value of the resulting decisions, but until now, methods for creating scenarios have not been compared under realistic operational conditions. Here, we compare the quality of scenario sets created using three different methods, based on a simulated re-enactment of stochastic day-ahead unit commitment and subsequent dispatch for a realistic test system. We create scenarios using a dataset of forecasted and actual wind power values, scaled to evaluate the effects of increasing wind penetration levels. We show that the choice of scenario set can significantly impact system operating cost, renewable energy use, and the ability of the system to meet demand. This result has implications for the ability of system operators to efficiently integrate renewable production into their day-ahead planning, highlighting the need for the use of performance-based assessments for scenario evaluation.
The National Aeronautics and Space Administration (NASA) Dryden Flight Research Center (DFRC) Ikhana (ee-kah-nah) project executed the 2007 Western States Fire Missions over several of the western United States using an MQ-9 unmanned aircraft system (UAS) in partnership with the NASA Ames Research Center, the United States Forest Service, and the National Interagency Fire Center. The missions were intended to supply infrared imagery of wildfires to firefighters on the ground within 10 minutes of data acquisition. For each of the eight missions, the NASA DFRC notified the Federal Aviation Administration (FAA) of specific flight plans within three or fewer days of the flight. The FAA Certificate of Waiver or Authorization (commonly referred to as a COA ) process was used to obtain access to the United States National Airspace System. Significant time and resources were necessary to develop the COA application, perform mission planning, and define and approve emergency landing sites. Unique aspects of flying unmanned aircraft created challenges to mission operations. Close coordination with FAA headquarters and air traffic control resulted in safe and successful missions that assisted firefighters by providing near-real-time imagery of selected wildfires.
The EOS project is investigating the design and construction of a family of real-time distributed embedded operating systems for reliable, distributed aerospace applications. Using the real-time programming techniques developed in co-operation with NASA in earlier research, the project staff is building a kernel for a multiple processor networked system. The first six months of the grant included a study of scheduling in an object-oriented system, the design philosophy of the kernel, and the architectural overview of the operating system. In this report, the operating system and kernel concepts are described. An environment for the experiments has been built and several of the key concepts of the system have been prototyped. The kernel and operating system is intended to support future experimental studies in multiprocessing, load-balancing, routing, software fault-tolerance, distributed data base design, and real-time processing.
The Resource Prospector Mission seeks to rove the lunar surface with an in-situ resource utilization payload in search of volatiles at a polar region. The mission operations system (MOS) will need to perform the short-duration mission while taking advantage of the near real time control that the short one-way light time to the Moon provides. To maximize our use of limited resources for the design and development of the MOS we are utilizing agile and lean methods derived from our previous experience with applying these methods to software. By using methods such as "say it then sim it" we will spend less time in meetings and more time focused on the one outcome that counts - the effective utilization of our assets on the Moon to meet mission objectives.
A new technology for producing finite capacity schedules has been developed in response to complex requirements for operating space systems such as the Space Shuttle, the Space Station, and the Deep Space Network for telecommunications. This technology has proven its effectiveness in manufacturing environments where popular scheduling techniques associated with Materials Resources Planning (MRPII) and with factory simulation are not adequate for shop-floor work planning and control. The technology has three components. The first is a set of data structures that accommodate an extremely general description of a factory's resources, its manufacturing activities, and the constraints imposed by the environment. The second component is a language and set of software utilities that enable a rapid synthesis of functional capabilities. The third component is an algorithmic architecture called the Five Ruleset Model which accommodates the unique needs of each factory. Using the new technology, systems can model activities that generate, consume, and/or obligate resources. This allows work-in-process (WIP) to be generated and used; it permits constraints to be imposed or intermediate as well as finished goods inventories. It is also possible to match as closely as possible both the current factory state and future conditions such as promise dates. Schedule revisions can be accommodated without impacting the entire production schedule. Applications have been successful in both discrete and process manufacturing environments. The availability of a high-quality finite capacity production planning capability enhances the data management capabilities of MRP II systems. These schedules can be integrated with shop-floor data collection systems and accounting systems. Using the new technology, semi-custom systems can be developed at costs that are comparable to products that do not have equivalent functional capabilities and/or extensibility.
The application of commonality in a system represents an attempt to reduce costs by reducing the number of unique components. Research in this area has primarily addressed a significant benefit of commonality, the reduction of parts inventories in assemble-to-order manufacturing systems. Likewise, in an operational system subject to component failures, spares inventories are reduced through the increased commonality of components. However, commonality tends to degrade system performance parameters, a degradation that can preclude commonality in resource-constrained systems such as spacecraft. The functional impacts of component commonality on a system is addressed in a manner that allows inclusion in a commonality analysis.
The Distribution System Operator with Transactive (DSO+T) study investigates the engineering and economic performance of a transactive energy retail market coordinating a high penetration of customer-side flexible energy assets. The study seeks to answer whether such an implementation is cost effective for customers, recovers sufficient revenue for DSOs, and is equally applicable and beneficial to a range of flexible asset types, renewable generation scenarios, and market assumptions. Using a highly interdisciplinary co-simulation and valuation framework, this assessment encompasses the entire electrical delivery system from bulk system generation and transmission, through the distribution system, to the modeling of individual customer buildings and flexible assets (including heating, ventilation, and air conditioning [HVAC] units, water heaters, batteries, and electric vehicles). The study exercises a transactive energy retail market coordination scheme designed to integrate with an existing day-ahead and real-time competitive wholesale electricity market. Software decision-making agents are designed for the retail market operator as well as various price-responsive flexible assets. The engineering and economic performance of the transactive energy scheme is studied for two separate flexible asset deployments: flexible loads (HVAC units and residential water heaters) and behind-the-meter batteries. The results of each transactive case are compared to a business-as-usual case. These cases are subject to two different renewable generation scenarios, a moderate renewable generation scenario, representative of current levels of renewable generation deployment, and a future high renewables scenario, including the increased deployment of rooftop solar photovoltaic and electric vehicles. The transactive coordination scheme is shown to produce effective and stable control and decrease peak loads 9–15%. The resulting annual demand flexibility provides net economic savings of $3.3–5.0B per year for a region the size of Texas. Detailed analysis shows that net benefits were seen for a range of distribution system operator, customer, and flexible asset types. Both participating customer (with transactive flexible assets) and nonparticipating customers (with nonflexible assets) see reductions in annual utility bills and net annual energy expenses in the range of 10–16%.
This project develops an innovative, integrated, and transformative approach to mitigate the impact of wind ramping by providing flexible ramping products from wind power. The project will significantly contribute to the reduction of wind integration costs by making wind power dispatchable and allowing the efficient management of wind ramping characteristics. In addition, we collaborated with industry to test and validate the methodology, considering economic and reliability goals, by integrating the proposed methodology into the simulated market frameworks of two independent system operators: California Independent System Operator and the Electric Reliability Council of Texas.
The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost-effective set of multimission MOS products and services.
Nasa reliability evaluation program for operational systems set forth in npc 250-1