Search NASA⌕ Search

SEARCH · Search NASA

Results for “system thinking”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Recovery of the Space Shuttle Columbia Avionics

Lessons Learned: a) Avionics data can playa critical role in the investigation of a "close call" or accident. b) Avionics designers should think about the role their systems might play in an investigation. c) Know your data, down to the bit level. d) Know your spacecraft - follow the data. e) Internal placement of circuit cards can affect their survivability. f) Think about how to reconstruct nonvolatile memory (e.g. serialize IC's, etc.) g) Use of external assets can aid in extracting data from avionics.

Hames, Kevin L.↗
NASA NTRSDate not supplied

Thinking outside the box: The human role in increasingly automated aviation systems

Rapid advances in artificial intelligence are enabling automated systems to operate in an increasingly autonomous manner in domains that previously required the involvement of human operators. Examples are rail transport systems, self-driving cars, and warehouse delivery systems. From time to time, such automation encounters operational conditions that fall outside a “competency box” within which the system has been designed to operate. Human operators add resilience because they can see and act outside the competency box of scenarios and environments for which the system was designed. The system’s competencies can be expanded over time with modifications to software, sensors, etc.; however, it is unclear at what point the competency box becomes large enough to safely eliminate the role of the human operator. One area where advanced automation may be applied is Urban Air Mobility (UAM). Current UAM concepts envision fleets of highly automated air vehicles providing on-demand transport for people and goods. A phased development of UAM has been proposed, beginning with on-board pilots and transitioning to a future state where automated vehicles operate with minimal human involvement. Proponents of UAM note that this final state reduces cost as well as eliminating pilot error, identified as a contributing factor in many aircraft accidents. However, eliminating human involvement also risks eliminating their positive contributions to system resilience. Here we examine Concepts of Operation proposed for future UAM systems and explore how humans can best be incorporated to maintain resilience while minimizing cost and risk. A human-autonomy teaming approach is suggested.

Advanced Air Mobility↗
NASA NTRS2014

Neither Pollyanna nor Chicken Little: Thoughts on the Ethics of Automation

This paper has raised issues concerning the ethics of automation in aviation systems, and outlined ways of thinking about the issues that may help in ethical decision making. It is very easy to be carried along by technology and the Pollyanna view, but just because we can do something, doesn't mean we should - which is perhaps a little milder than the Chicken Little view. Both views have merits, and we would view ethical decisions as ones that more appropriately balance or reconcile these conflicting viewpoints. We have set out some of the background to the problems of automation in aviation systems, but are aware that there is much more that could be said (considering military UAS, for example). We hope, however, that the brief introduction provides a foundation for the ethical questions that we have set out. The underlying aim in proposing ESCs is to make understanding ethical issues easier so that ethically-informed decisions can be made. Whilst we have not linked the discussion directly back to specific ethical decisions, we believe that making explicit those issues on which such judgments are based is a contribution to ethically informed decision making. We also believe that the four principles set out by the RAEng are reflected in this approach. We acknowledge that what we have set out, especially the ideas of ESC, goes some way beyond current practice and principles and there are significant technical issues to resolve before such an approach could be implemented. It is hoped, however, that the ideas will help improve the production and presentation of safety cases in a range of industries not just aviation - a Pollyanna view, of course!

Holloway, C. Michael↗
NASA NTRS2020

Airspace Operations: Vision for 2045 and Beyond

We are seeing interesting changes in airspace operations. We are experiencing growth in global aviation for passenger and cargo travel. At the same time, drones of all sizes, urban air mobility, electric aircraft, commercial space transportation, supersonics, hypersonics, and increasingly autonomous vehicles will continue to mature. These operations along with current aviation will require access to airspace operations. Such access and scalability needs will only continue to increase in the future. Given that systems and procedures that will enable and support the future density and diversity takes a considerable amount of time to build and harmonize across the globe, it is appropriate that research efforts to enable 2045 operations begin now. A perfect storm is brewing as a number of factors are coming together, including: anticipated growth in diversity and density; limitations of our current system to support the growth and diversity; lack of utilization of latest technologies in an increasingly digitized world to support air traffic management; and a long lead time to conduct research, develop requirements, and built and deploy air traffic management systems. All these factors indicate that now is the time to start thinking about the needs of 2045 and beyond. In a limited manner, Unmanned Aircraft System Traffic Management (UTM) has shown that new thinking and implementation paths for airspace operations is possible. The current system as it exists is based on many assumptions and limitations of technologies (e.g., radar, human-centered voice communications) which may not be true moving forward given the technologies around us are changing. The panel will discuss the following and related topics: 1. Expected growth in density, diversity, and needed scalability, 2. Likely requirements of air traffic management system to enable and support 2045 and beyond operations, 3. Assumptions related to air traffic management and operations that need to reevaluated based on technology trends, 4. Identification of research priorities and harmonization of research across the globe, and 5. Transition approaches from current air traffic operations to new vision 2045. The panel discussion will be useful for global air traffic management researchers, managers, strategists, airspace users, air traffic management system developers and integrators, and academic researchers.

Kopardekar, Parimal H.↗
NASA NTRS2020

A ROS-based Simulator for Testing the Enhanced Autonomous Navigation of the Mars 2020 Rover

In order to achieve the ambitious objectives of the Mars 2020 (M2020) mission, in particular the ability to autonomously traverse more challenging terrains more efficiently, new surface mobility software was developed for Enhanced Navigation (ENav). That decision was made early in the project, before most of the new surface flight software (FSW) existed, which created a need for a separate framework where the new navigation algorithms could be quickly prototyped and tested, before more realistic FSW-based testbeds became available. The JPL robotics team chose the Robot Operating System [1] (ROS) as the environment in which to test the new ENav algorithms. This made it possible to write the algorithms in the C language required by the FSW, so they could be directly ported over to the flight module later on, while leveraging all the C++ libraries and tools provided by ROS for simulation and testing. The ENav algorithms were developed as a separate C library, and stubs were used to replace any FSW-specific code, such as Event Reporting (EVRs) and data products (DPs). A ROS simulator was developed to generate a rich set of varied 3D terrains representative of the candidate Mars landing sites and simulate the physics of the rover motion, the point cloud perceived by the rover’s stereo vision system, and the new thinking-while-driving (TWD) navigation logic which directs the rover to drive autonomously to user-specified waypoints. To simulate the rover motion and perception, a ROS node was developed that uses a software library called HyperDrive Sim (HDSim), which is a wrapper for the Rover Sequencing and Visualization Program [2] (RSVP). That library provides roverterrain settling, realistic slip modelling, and camera rendering capability based on the rover’s NavCam machine vision models. To simulate the navigation logic, a ROS node was created that initializes and runs the ENav algorithms in a way that mimics the FSW execution, while also providing the capability to load and replay data products, including re-running the recorded inputs through the ENav algorithms for testing. An engineering Graphical User Interface (GUI) was also developed to visualize various elements, such as the rover pose during the drive, the simulated and perceived terrain, the selected local and global paths to the goal, the evaluated candidate paths and the reasons why they were rejected, the keep-in and keep-out zones (KIOZs), etc. Finally, an advanced Monte Carlo (MC) framework that can run many simulations in parallel on the Cloud and automatically generate reports that capture the key ENav performance metrics was developed to evaluate the system in a statisticallymeaningful way. This paper provides an overview of the ROSbased simulator used for testing the M2020 ENav algorithms.

Toupet, Olivier↗
NASA NTRS2004

To Boldly Go: America's Next Era in Space. Machine Consciousness and the Exploration of Space

Dr. France Cordova, NASA's Chief Scientist, chaired this meeting, another part of the NASA Administrator's Seminar Series. She introduced Administrator Daniel S. Goldin, who welcomed the attendees, and noted that the two speakers have a running feud regarding the possibility of creating robots that can 'think'. Dr. Cordova then introduced the first speaker, Dr. Roger Penrose of the Mathematical Institute at Oxford in the U.K. His primary interests are in mathematics, physics, information systems technology, and artificial intelligence. He thinks that robots cannot be made to 'think' and that consciousness is not computable. Dr. Hans Moravec, who spoke next, has opinions and activities that are related to, but substantially different from those of Dr. Penrose. Dr. Moravec believes that he can build a robot that can act based on the deductions that it will make. To mimic human thinking capabilities, he figures that a robot ultimately will need to be able to handle ten trillion computations per second. He predicts that his goal of building a 'thinking' robot will be met in the 2030-2040 time period. He pointed out that he already has built a car that successfully drove itself from Washington, DC to San Diego, CA. He commented that a human being, was ready to take over driving the car, if necessary, but there was no need. The robots envisioned by Dr. Moravec would not only be able to 'think', but also would have human-like emotions, and ultimately would be able to reproduce. The discussion that followed raised questions about the morality of sending human-like robots into outer space. Also a concern was expressed that human-like robots might perceive humans as a threat and become dangerous to people.

Source record↗
NASA NTRS2005

Systems Engineering and Integration for Advanced Life Support System and HST

Systems engineering (SE) discipline has revolutionized the way engineers and managers think about solving issues related to design of complex systems: With continued development of state-of-the-art technologies, systems are becoming more complex and therefore, a systematic approach is essential to control and manage their integrated design and development. This complexity is driven from integration issues. In this case, subsystems must interact with one another in order to achieve integration objectives, and also achieve the overall system's required performance. Systems engineering process addresses these issues at multiple levels. It is a technology and management process dedicated to controlling all aspects of system life cycle to assure integration at all levels. The Advanced Integration Matrix (AIM) project serves as the systems engineering and integration function for the Human Support Technology (HST) program. AIM provides means for integrated test facilities and personnel for performance trade studies, analyses, integrated models, test results, and validated requirements of the integration of HST. The goal of AIM is to address systems-level integration issues for exploration missions. It will use an incremental systems integration approach to yield technologies, baselines for further development, and possible breakthrough concepts in the areas of technological and organizational interfaces, total information flow, system wide controls, technical synergism, mission operations protocols and procedures, and human-machine interfaces.

Kamarani, Ali K.↗
NASA NTRS1967

Design of Liquid Propellant Rocket Engines Second Edition

This book intends to build a bridge for the student and the young engineer: to link the rocket propulsion fundamentals and elements (which are well covered in the literature) with the actual rocket engine design and development work as it is carried out in industry (which is very little, if at all covered in literature). The book attempts to further the understanding of the realistic application of liquid rocket propulsion theories, and to help avoid or at least reduce time and money consuming errors and disappointments. In so doing, it also attempts to digest and consolidate numerous closely related subjects, hitherto often treated as separate, bringing them up to date at the same time. The book was written "on the job" for use by those active in all phases of engine systems design, development, and application, in industry as well as government agencies. Since it addresses itself to human beings set out to create new machines, rather than describing machines about to dominate man, the language chosen may not always be "functional" in the strict sense of the word. The book presents sufficient detail to familiarize and educate thoroughly those responsible for various aspects of liquid propellant rocketry, including engine systems design, engine development, and flight vehicle application. It should enable the rocket engineer to conduct, independently, complete or partial engine systems preliminary detail designs and to understand and judge the activities in, and the problems, limitations, and "facts of life~ of the various subsystems making up a complete engine system. It also attempts to educate those ultimately interested in specialized subsystems and component design (thrust chamber, turbopump, control valves, etc.) about their own as well as neighboring subsystems and about the complete engine system. This should enable the student to prepare realistic analytical calculations and design layouts with a long headstart toward the final specialized designs for subsystem production release. Special emphasis has been placed on engine flight application to stimulate engine systems and subsystem designers to think in these terms from the outset. The book is intended as a textbook, with specific consideration of the teacher without industry experience. We hope it will stimulate those desiring to specialize in the area of a rocket engine subsystem by supplying adequate information to enable them to benefit fully from the specialized literature. Thus, it provides a realistic expert introduction for those joining the liquid propellant rocket engine field.

Dieter K Huzel↗
NASA NTRS1984

Evaluation of Fuzzy Rulemaking for Expert Systems for Failure Detection

Computer aids in expert systems were proposed to diagnose failures in complex systems. It is shown that the fuzzy set theory of Zadeh offers a new perspective for modeling for humans thinking and language use. It is assumed that real expert human operators of aircraft, power plants and other systems do not think of their control tasks or failure diagnosis tasks in terms of control laws in differential equation form, but rather keep in mind a set of rules of thumb in fuzzy form. Fuzzy set experiments are described.

Laritz, F.↗
NASA NTRSDate not supplied

Designing for Advanced Aerial Mobility: Human-Autonomy Teaming and In-Time System-Wide Safety Assurance

The continued growth of aviation shall require new innovative technologies and operational concepts to meet the ever-increasing demands on air transportation. The NASA Advanced Air Mobility (AAM) project focuses on emerging aviation markets, such as Urban Air Mobility (UAM). UAM is defined as “...a safe and efficient system for air passenger and cargo transportation within an urban area. It is inclusive of small package delivery and other urban unmanned aerial system services and supports a mix of onboard/ground-piloted and increasingly autonomous operations” ([1]). The AAM project emphasizes technology development and validating system-level concepts and solutions in coordination with other NASA Aeronautics Research Mission Directorate (ARMD) projects to enable UAM metro- and micro-plex vertiport and airspace concepts of operations. The NASA AAM research portfolio includes the concepts of Remote Supervisor-in-Command (RSC) and Fleet and Airspace Manager (FAM) as possible human roles for consumer fleet providers. NASA research in RSC is focused on development of guidelines and standards for remote pilots/operators passively and actively controlling a large fleet of autonomous aircraft. For FAM, flight and ground system concepts and technologies to enable high density homogeneous operations at increased scale from vertiport(s), and coordination with other humans in the systems (e.g., UAM urban airspace manager, Air Traffic Control) are key research areas. The envisioned UAM operations are posited to require autonomous systems to enable functions ranging from fleet and resource management to vehicle control. Although automation has become increasingly sophisticated and ubiquitous in civil aviation, autonomy represents a significant evolution in automation, which has generally been limited in functional scope and capability. As autonomy takes on increasing responsibilities, humans and machines will be required to work together in new and different ways [2], rather than traditional design approaches focused on how machines (i.e., autonomy) can do the work of people. The emerging field of human-autonomy teaming (HAT) represents a comprehensive and prioritized research-driven approach to enable the success of future emerging aviation market applications through capabilities and principles that facilitate humans and machine working and thinking better together. The NASA Transformational Tools and Technologies (TTT) Autonomous System (AS) Sub-project was created to assist with the transition into higher levels of autonomy to enable new modes of air transportation, such as UAM. TTT-AS has identified HAT as a key research need to enable UAM while maintaining today’s ultra-safe aviation system safety levels. The latter challenge has been taken up by the NASA System-Wide Safety (SWS) Project, which recognizes that aviation safety, as it evolves, shall require new ways of thinking about safety to include integration of a wide-range of existing and new safety systems and practices, enhanced tools and technologies, increased access to data and data fusion, improved data analysis capabilities, enhanced in-time risk monitoring and detection, hazard prioritization and mitigation, safety assurance decision-support, and in-time integrated system analytics [3].The operational concept of UAM represents a variety of work that has been termed, “work-as-imagined” to characterize the idea that how people think that work is done and how work is actually done are often not the same [4]. To ensure design success and system safety, looking at “work-as-done” provides a comparative approach toward UAM concept and technology design through examination of corresponding analogs found today in aviation (e.g., on-demand operations) and other transportation domains (e.g., port operations). The paper shall discuss various alternative applications with specific focus on airline operation center (AOC) operations, and unmanned aerial system (UAS) command-and-control to inform scaled-versions of FAM and RSC, respectively, and with consideration of the national airspace system contextual environment. The tenets and principles of the HAT field and current NASA research efforts under the TTT-AS sub-project shall also be described. Finally, the SWS sub-project efforts to develop In-Time System-Wide Safety Assurance (ISSA) and In-Time Safety Management Systems (IASMS) are discussed in terms of how “in-time” safety assurance may be conceptualized for the on-demand mobility air taxi “work-as-imagined” operational concept [5]. As part of this effort, concepts from the emerging field of resilience engineering, are being studied. Traditional approaches to aviation safety have focused on what can go wrong and how to prevent it. Another approach to thinking about system safety should reflect not only “avoiding things that go wrong” (protective safety) but also “ensuring that things go right” (productive safety), that enables a system to exhibit the resilient performance [6] necessary for the success of the future aviation system emerging concepts of operations. The paper shall describe efforts focused on how productive safety and resilience may enable a more complete approach to system safety thinking and design of ISSA and IASMS for UAM. Future directions and research needs shall also be discussed.

resilience↗
NASA NTRS1991

Beyond formalism

The ongoing debate over the role of formalism and formal specifications in software features many speakers with diverse positions. Yet, in the end, they share the conviction that the requirements of a software system can be unambiguously specified, that acceptable software is a product demonstrably meeting the specifications, and that the design process can be carried out with little interaction between designers and users once the specification has been agreed to. This conviction is part of a larger paradigm prevalent in American management thinking, which holds that organizations are systems that can be precisely specified and optimized. This paradigm, which traces historically to the works of Frederick Taylor in the early 1900s, is no longer sufficient for organizations and software systems today. In the domain of software, a new paradigm, called user-centered design, overcomes the limitations of pure formalism. Pioneered in Scandinavia, user-centered design is spreading through Europe and is beginning to make its way into the U.S.

Denning, Peter J.↗
NASA NTRS2000

Implementing Journaling in a Linux Shared Disk File System

In computer systems today, speed and responsiveness is often determined by network and storage subsystem performance. Faster, more scalable networking interfaces like Fibre Channel and Gigabit Ethernet provide the scaffolding from which higher performance computer systems implementations may be constructed, but new thinking is required about how machines interact with network-enabled storage devices. In this paper we describe how we implemented journaling in the Global File System (GFS), a shared-disk, cluster file system for Linux. Our previous three papers on GFS at the Mass Storage Symposium discussed our first three GFS implementations, their performance, and the lessons learned. Our fourth paper describes, appropriately enough, the evolution of GFS version 3 to version 4, which supports journaling and recovery from client failures. In addition, GFS scalability tests extending to 8 machines accessing 8 4-disk enclosures were conducted: these tests showed good scaling. We describe the GFS cluster infrastructure, which is necessary for proper recovery from machine and disk failures in a collection of machines sharing disks using GFS. Finally, we discuss the suitability of Linux for handling the big data requirements of supercomputing centers.

Preslan, Kenneth W.↗
NASA NTRSDate not supplied

Advancing Open Science Through Innovative Data System Solutions: The Joint ESA-NASA Multi-Mission Algorithm and Analysis Platform (MAAP)'s Data Ecosystem

Collaborative open science practices are changing the way research is conducted. These changes affect how scientists work together on data, code and information. Data systems enhance open science by offering forward thinking technological solutions, such as providing data and computation on the cloud, to enable collaboration, sharing and analysis. In this paper, we present our vision for a conceptual data system on the cloud that enables open science. We also present our work on the Multi-Mission Algorithm and Analysis Platform (MAAP)which has served as a pathfinder data system for this conceptual approach.

Kaylin Bugbee↗
NASA NTRSDate not supplied

Oversimplification of Systems Engineering Goals, Processes, and Criteria in NASA Space Life Support

This paper investigates the oversimplification of the inherently complex systems engineering process in space life support. The standard systems engineering process steps are described. The International Space Station (ISS) life support system is explained with its goals and performance criteria. Although it is not usually emphasized, the essential function of developing a hierarchy of systems and subsystems is to simplify the design process. The System Complexity Metric (SCM) shows how this di-vide-and-conquer approach also reduces the system complexity. The complete systems engineering process has many detailed steps. It is often simplified because of the effort required and the human limitations on working memory and decision span. Systems analysis demands slow, logical, and fo-cused thinking but is often bypassed in favor of quick, intuitive, subconscious “gut feel.” A study of 100 system designs found examples of 12 specific mental mistakes, such as ignoring stakeholder needs, and these mistakes are essentially oversimplifications of the systems engineering process. An analysis of space life support goals, options, criteria, and processes found 11 examples of oversimplifications in systems engineering, such as neglecting safety and cost. All these 11 oversimplifications could be traced to one or more of the 12 previously identified mental mistakes or other well-known ones, such as ig-noring sunk costs. Oversimplification of the systems engineering process is rarely noticed but is a common and harmful problem. A study of failures in 50 different space systems found that problems in systems engineering caused failures and often led to errors in design, development, and test that further contributed to failure. It seems that more diligent systems engineering could prevent many project problems and failures, but projects seem to be more guided by “gut feel” based on tradition, authority, and consensus than on the logical, rational systems engineering approach.

Simplified systems engineering↗
NASA NTRS2003

Architecture and System Engineering Development Study of Space-Based Satellite Networks for NASA Missions

Traditional NASA missions, both near Earth and deep space, have been stovepipe in nature and point-to-point in architecture. Recently, NASA and others have conceptualized missions that required space-based networking. The notion of networks in space is a drastic shift in thinking and requires entirely new architectures, radio systems (antennas, modems, and media access), and possibly even new protocols. A full system engineering approach for some key mission architectures will occur that considers issues such as the science being performed, stationkeeping, antenna size, contact time, data rates, radio-link power requirements, media access techniques, and appropriate networking and transport protocols. This report highlights preliminary architecture concepts and key technologies that will be investigated.

Ivancic, William D.↗
NASA NTRS1991

Lunar crane system

In many lunar construction scenarios, mechanical cranes in some form will be indispensible in moving large masses around with various degrees of fine positioning. While thorough experience exists in the use of terrestrial cranes new thinking is required about the design of cranes to be used in extraterrestrial construction. The primary driving force for this new thinking is the need to automate the crane system so that space cranes can be operated as telerobotic machines with a large number of automatic capabilities. This is true because in extraterrestrial construction human resources will need to be critically rationed. The design problems of mechanisms and control systems for a lunar crane must deal with at least two areas of performance. First, the automated crane must be capable of maneuvering a large mass, so that when the mass arrives at the target position there are only small vibrations. Secondly, any residue vibrations must be automatically damped out and a fine positioning must be achieved. For extraterrestrial use there are additional challenges to a crane design - for example, to design a crane system so that it can be transformed for other construction uses. This initial project in crane design does not address such additional issues, although they may be the subject of future CSC research. To date the Center has designed and analyzed many mechanisms. The fundamental problem of trade-offs between passively stabilizing the load and actively controlling the load by actuators was extensively studied. The capability of 3D dynamics modeling now exists for such studies. A scaled model of a lunar crane was set up and it has been most fruitful in providing basic understanding of lunar cranes. Due to an interesting scaling match-up, this scaled model exhibits the load vibration frequencies one would expect in the real lunar case. Using the analytical results achieved to date, a laboratory crane system is now being developed as a test bed for verifying a wide variety of mechanisms and control designs. Future development will be aimed at making the crane system a telerobotic test bed into which external sensors such as computer vision systems, and other small robotic devices such as CSC lunar rovers, will be integrated.

Mikulas, Martin M., Jr.↗
NASA NTRS2004

Training Informal Educators Provides Leverage for Space Science Education and Public Outreach

How do we reach the public with the exciting story of Solar System Exploration? How do we encourage girls to think about careers in science, math, engineering and technology? Why should NASA scientists make an effort to reach the public and informal education settings to tell the Solar System Exploration story? These are questions that the Solar System Exploration Forum, a part of the NASA Office of Space Science Education (SSE) and Public Outreach network, has tackled over the past few years. The SSE Forum is a group of education teams and scientists who work to share the excitement of solar system exploration with colleagues, formal educators, and informal educators like museums and youth groups. One major area of the SSE Forum outreach supports the training of Girl Scouts of the USA (GS) leaders and trainers in a suite of activities that reflect NASA missions and science research. Youth groups like Girl Scouts structure their activities as informal education.

Allen, J. S.↗
NASA NTRS2001

Think Tanks

A new inspection robot from Solex Robotics Systems was designed to eliminate hazardous inspections of petroleum and chemical storage tanks. The submersible robot, named Maverick, is used to inspect the bottoms of tanks, keeping the tanks operational during inspection. Maverick is able to provide services that will make manual tank inspections obsolete. While the inspection is conducted, Maverick's remote human operators remain safe outside of the tank. The risk to human health and life is now virtually eliminated. The risk to the environment is also minimal because there is a reduced chance of spillage from emptying and cleaning the tanks, where previously, tons of pollutants were released through the process of draining and refilling.

Source record↗