Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operational design domain”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Data-Centric Operational Design Domain Characterization for Machine Learning-Based Aeronautical Products

We give for Machine Learning (ML)-based aeronautical products, a first rigorous characterization of Operational Design Domains (ODDs). Unlike in other application sectors (such as self-driving road vehicles) where ODD development is scenario-based, our approach is data-centric: we propose the dimensions along which the parameters that define an ODD can be explicitly captured, using a top-down approach starting from system specifications, and a bottom-up approach starting from detailed ML Model (MLM) designs. Then we give a categorization of the data that ML-based applications can encounter in operation, identifying their system-level relevance and impact. Specifically, we discuss how those data categories are useful to determine: (1) the requirements necessary to drive the design of MLMs; (2) the potential effects on the MLM and higher levels of the system hierarchy; (3) the learning assurance processes that may be needed, and (4) system architectural considerations. We illustrate the underlying concepts with an example of an aircraft flight envelope. The approach in this paper is one of the cornerstones of a future process guidance for development and certification/approval of safety-related aeronautical products implementing Artificial Intelligence (AI), currently being developed through aviation industry-based consensus, jointly by the SAE G-34 Committee for AI in aviation, and EUROCAE WG-114 for AI.

Aeronautical products↗
NASA NTRS2023

Human Systems Integration: Managing Risk in Anesthesia

The practice of anesthesia relies on clinicians’ ability to safely manage increasingly complex equipment. Devices such as ventilators, drug infusion pumps, and physiologic monitors use sophisticated algorithms to deliver care, but most clinicians are only trained to manage automated systems during normal operation. Few if any receive training on how to manage system failures. Although manufacturers are required to consult with human factors engineers as part of the equipment design process, most pieces of equipment are ultimately brought to market without extensive input from clinicians. Systems in the operating room can be as simple as an oxygen tank, or as complex as a multi-institutional healthcare organization. Humans are also a complex system, and play a critical role in the domains of operations, design, fabrication, maintenance, repair, and ultimately, dismantling and closeout. HSI seeks to provide a means for advocating the human side of the system. Human Systems Integration (HSI) is the cross disciplinary process used as part of the Systems Engineering process to reduce risk in systems. HSI professionals consider the human, hardware, and software elements of system design to optimize system performance and improve safety. HSI professionals work in domains of study that include training, management, human factors engineering, safety, and occupational health, among others. This article discusses the role of systems in the practice of anesthesia, and how consideration of the human during all phases of the system life cycle helps manage risks and promote a better patient outcome.

Human Factors↗
NASA NTRS1998

Development and Preliminary Results of CTAS on Airline Operational Control Center Operations

Continued growth and expansion of air traffic and increased air carrier economic pressures have mandated greater flexibility and collaboration in air traffic management. The ability of airspace users to select their own routes, so called "free-flight", and to more actively manage their fleet operations for maximum economic advantage are receiving great attention. A first step toward greater airspace user and service provider collaboration is information sharing. In this work, arrival scheduling and airspace management data generated by the NASA/FAA Center/TRACON Automation System (CTAS) and used by the FAA service provider is shared with an airline with extensive operations within the CTAS operational domain. The design and development of a specialized airline CTAS "repeater" system is described, as well as some preliminary results of the impact and benefits of this information on the air carrier's operations. FAA controller per aircraft scheduling information, such as that provided by CTAS, has never before been shared in real-time with an airline. Expected airline benefits include improved fleet planning and arrival gate management, more informed "hold-go" decisions, and avoidance of costly aircraft diversions to alternate airports when faced with uncertain airborne arrival delays.

Zelenka, Richard↗
NASA NTRS2004

Development and Preliminary Results of CTAS on Airline Operational Control Center Operations

Continued growth and expansion of air traffic and increased air carrier economic pressures have mandated greater flexibility and collaboration in air traffic management. The ability of airspace users to select their own routes, so called "free-flight", and to more actively manage their fleet operations for maximum economic advantage are receiving great attention. A first step toward greater airspace user and service provider collaboration is information sharing. In this work, arrival scheduling and airspace management data generated by the NASA/FAA Center/TRACON Automation System (CTAS) and used by the FAA service provider is shared with an airline with extensive operations within the CTAS operational domain. The design and development of a specialized airline CTAS "repeater" system is described, as well as some preliminary results of the impact and benefits of this information on the air carrier's operations. FAA controller per aircraft scheduling information, such as that provided by CTAS, has never before been shared in real-time with an airline. Expected airline benefits include improved fleet planning and arrival gate management, more informed "hold-go decisions, and avoidance of costly aircraft diversions to alternate airports when faced with uncertain airborne arrival delays.

Zelenka, Richard↗
NASA NTRS2018

System-of-Systems Tools for the Analysis of Technological Choices in Space Propulsion

Difficulties in space mission architecture design arise from many factors. Performance, cost, and risk constraints become less obvious due to complex interactions between the systems involved in the mission; decisions regarding long-term goals can heavily impact technological choices for short-term parts of the mission, while conversely decisions in the near future will impact the whole flexibility of long-term plans. Furthermore, the space community is broadening its borders, and space agencies from different countries are collaborating with industry and commercial partners towards large-scale endeavors. This paradigm shift is prompting the development of non-traditional approaches to the design of space missions. This paper reports the results of the first year of a continuing collaboration of the authors to develop and demonstrate System-of-System engineering methodologies for the deep analysis of dependencies and synthesis of robust architectures in exploration mission contexts. We present the procedure that we followed to develop and apply our methodology, obstacles found, steps taken to improve the methods based on the needs of experts and decision makers, required data for the analysis, and results produced by our holistic analysis. In particular, we focus on the analysis of technological choices for space propulsion for a generic cislunar mission, including both complex interactions between subsystems in different type of propulsion and availability of different providers. We identify critical systems and sets of systems based on cascading effects of performance degradation, assessment of the robustness of different designs in the operational domain, and simultaneous analysis of schedule dependencies between the constituent systems.

Guariniello, Cesare↗
NASA NTRS1987

Theoretical considerations in designing operator interfaces for automated systems

The domains most amenable to techniques based on artificial intelligence (AI) are those that are systematic or for which a systematic domain can be generated. In aerospace systems, many operational tasks are systematic owing to the highly procedural nature of the applications. However, aerospace applications can also be nonprocedural, particularly in the event of a failure or an unexpected event. Several techniques are discussed for designing automated systems for real-time, dynamic environments, particularly when a 'breakdown' occurs. A breakdown is defined as operation of an automated system outside its predetermined, conceptual domain.

Norman, Susan D.↗
NASA NTRS2014

Overview of the Contributing Factor Map and How it can Support your Research

The Contributing Factor Map (CFM) is a visual representation of a taxonomy of factors influencing human health and performance in space. This presentation will give an overview of its development and its structure. It will describe various uses of the CFM that can support researchers working within the Human Research Program (HRP) Architecture of Evidence-Risk-Gap-Task-Deliverable. For example, during the Risk phase, the CFM can be used as a "menu" to help formulate a qualitative model of the factors contributing to specific consequences of concern. It provides a reference set of factors from across the operational, vehicle design, and human domains that otherwise might not be considered if approaching a risk from a specific domain perspective. Using the CFM as a reference can increase awareness of potential cross-disciplinary collaborations for overall risk mitigation. The CFM can also be used as a framework for identifying gaps in knowledge about a risk. This identification can support the subsequent development of gaps and tasks comprising the research plan aimed at risk mitigation. Examples of these types of applications of the CFM will be discussed and information on the support available to researchers in using it will be provided.

Mindock, Jennifer A.↗
NASA NTRS1988

OFMspert - Inference of operator intentions in supervisory control using a blackboard architecture

The authors proposes an architecture for an expert system that can function as an operator's associate in the supervisory control of a complex dynamic system. Called OFMspert (operator function model (OFM) expert system), the architecture uses the operator function modeling methodology as the basis for the design. The authors put emphasis on the understanding capabilities, i.e., the intent referencing property, of an operator's associate. The authors define the generic structure of OFMspert, particularly those features that support intent inferencing. They also describe the implementation and validation of OFMspert in GT-MSOCC (Georgia Tech-Multisatellite Operations Control Center), a laboratory domain designed to support research in human-computer interaction and decision aiding in complex, dynamic systems.

Jones, Patricia S.↗
NASA NTRS1990

StarPlan: A model-based diagnostic system for spacecraft

The Sunnyvale Division of Ford Aerospace created a model-based reasoning capability for diagnosing faults in space systems. The approach employs reasoning about a model of the domain (as it is designed to operate) to explain differences between expected and actual telemetry; i.e., to identify the root cause of the discrepancy (at an appropriate level of detail) and determine necessary corrective action. A development environment, named Paragon, was implemented to support both model-building and reasoning. The major benefit of the model-based approach is the capability for the intelligent system to handle faults that were not anticipated by a human expert. The feasibility of this approach for diagnosing problems in a spacecraft was demonstrated in a prototype system, named StarPlan. Reasoning modules within StarPlan detect anomalous telemetry, establish goals for returning the telemetry to nominal values, and create a command plan for attaining the goals. Before commands are implemented, their effects are simulated to assure convergence toward the goal. After the commands are issued, the telemetry is monitored to assure that the plan is successful. These features of StarPlan, along with associated concerns, issues and future directions, are discussed.

Heher, Dennis↗
NASA NTRS1973

Digital processing of radiographic images

Some techniques are presented and the software documentation for the digital enhancement of radiographs. Both image handling and image processing operations are considered. The image handling operations dealt with are: (1) conversion of format of data from packed to unpacked and vice versa; (2) automatic extraction of image data arrays; (3) transposition and 90 deg rotations of large data arrays; (4) translation of data arrays for registration; and (5) reduction of the dimensions of data arrays by integral factors. Both the frequency and the spatial domain approaches are presented for the design and implementation of the image processing operation. It is shown that spatial domain recursive implementation of filters is much faster than nonrecursive implementations using fast fourier transforms (FFT) for the cases of interest in this work. The recursive implementation of a class of matched filters for enhancing image signal to noise ratio is described. Test patterns are used to illustrate the filtering operations. The application of the techniques to radiographic images of metallic structures is demonstrated through several examples.

Bond, A. D.↗
NASA NTRS1993

ATOS-1: Designing the infrastructure for an advanced spacecraft operations system

The space industry has identified the need to use artificial intelligence and knowledge based system techniques as integrated, central, symbolic processing components of future mission design, support and operations systems. Various practical and commercial constraints require that off-the-shelf applications, and their knowledge bases, are reused where appropriate and that different mission contractors, potentially using different KBS technologies, can provide application and knowledge sub-modules of an overall integrated system. In order to achieve this integration, which we call knowledge sharing and distributed reasoning, there needs to be agreement on knowledge representations, knowledge interchange-formats, knowledge level communications protocols, and ontology. Research indicates that the latter is most important, providing the applications with a common conceptualization of the domain, in our case spacecraft operations, mission design, and planning. Agreement on ontology permits applications that employ different knowledge representations to interwork through mediators which we refer to as knowledge agents. This creates the illusion of a shared model without the constraints, both technical and commercial, that occur in centralized or uniform architectures. This paper explains how these matters are being addressed within the ATOS program at ESOC, using techniques which draw upon ideas and standards emerging from the DARPA Knowledge Sharing Effort. In particular, we explain how the project is developing an electronic Ontology of Spacecraft Operations and how this can be used as an enabling component within space support systems that employ advanced software engineering. We indicate our hope and expectation that the core ontology developed in ATOS, will permit the full development of standards for such systems throughout the space industry.

Poulter, K. J.↗
NASA NTRS2014

Comprehension of Spacecraft Telemetry Using Hierarchical Specifications of Behavior

A key challenge in operating remote spacecraft is that ground operators must rely on the limited visibility available through spacecraft telemetry in order to assess spacecraft health and operational status. We describe a tool for processing spacecraft telemetry that allows ground operators to impose structure on received telemetry in order to achieve a better comprehension of system state. A key element of our approach is the design of a domain-specific language that allows operators to express models of expected system behavior using partial specifications. The language allows behavior specifications with data fields, similar to other recent runtime verification systems. What is notable about our approach is the ability to develop hierarchical specifications of behavior. The language is implemented as an internal DSL in the Scala programming language that synthesizes rules from patterns of specification behavior. The rules are automatically applied to received telemetry and the inferred behaviors are available to ground operators using a visualization interface that makes it easier to understand and track spacecraft state. We describe initial results from applying our tool to telemetry received from the Curiosity rover currently roving the surface of Mars, where the visualizations are being used to trend subsystem behaviors, in order to identify potential problems before they happen. However, the technology is completely general and can be applied to any system that generates telemetry such as event logs.

Runtime monitoring↗
NASA NTRS1994

ELISA, a demonstrator environment for information systems architecture design

This paper describes an approach of reusability of software engineering technology in the area of ground space system design. System engineers have lots of needs similar to software developers: sharing of a common data base, capitalization of knowledge, definition of a common design process, communication between different technical domains. Moreover system designers need to simulate dynamically their system as early as possible. Software development environments, methods and tools now become operational and widely used. Their architecture is based on a unique object base, a set of common management services and they host a family of tools for each life cycle activity. In late '92, CNES decided to develop a demonstrative software environment supporting some system activities. The design of ground space data processing systems was chosen as the application domain. ELISA (Integrated Software Environment for Architectures Specification) was specified as a 'demonstrator', i.e. a sufficient basis for demonstrations, evaluation and future operational enhancements. A process with three phases was implemented: system requirements definition, design of system architectures models, and selection of physical architectures. Each phase is composed of several activities that can be performed in parallel, with the provision of Commercial Off the Shelves Tools. ELISA has been delivered to CNES in January 94, currently used for demonstrations and evaluations on real projects (e.g. SPOT4 Satellite Control Center). It is on the way of new evolutions.

Panem, Chantal↗
NASA NTRS1994

A DNA enzyme that cleaves RNA

BACKGROUND: Several types of RNA enzymes (ribozymes) have been identified in biological systems and generated in the laboratory. Considering the variety of known RNA enzymes and the similarity of DNA and RNA, it is reasonable to imagine that DNA might be able to function as an enzyme as well. No such DNA enzyme has been found in nature, however. We set out to identify a metal-dependent DNA enzyme using in vitro selection methodology. RESULTS: Beginning with a population of 10(14) DNAs containing 50 random nucleotides, we carried out five successive rounds of selective amplification, enriching for individuals that best promote the Pb(2+)-dependent cleavage of a target ribonucleoside 3'-O-P bond embedded within an otherwise all-DNA sequence. By the fifth round, the population as a whole carried out this reaction at a rate of 0.2 min-1. Based on the sequence of 20 individuals isolated from this population, we designed a simplified version of the catalytic domain that operates in an intermolecular context with a turnover rate of 1 min-1. This rate is about 10(5)-fold increased compared to the uncatalyzed reaction. CONCLUSIONS: Using in vitro selection techniques, we obtained a DNA enzyme that catalyzes the Pb(2+)-dependent cleavage of an RNA phosphoester in a reaction that proceeds with rapid turnover. The catalytic rate compares favorably to that of known RNA enzymes. We expect that other examples of DNA enzymes will soon be forthcoming.

Non-NASA Center↗
NASA NTRS2010

Constraint and Flight Rule Management for Space Mission Operations

The exploration of space is one of the most fascinating domains to study from a human factors perspective. Like other complex work domains such as aviation (Pritchett and Kim, 2008), air traffic management (Durso and Manning, 2008), health care (Morrow, North, and Wickens, 2006), homeland security (Cooke and Winner, 2008), and vehicle control (Lee, 2006), space exploration is a large-scale sociotechnical work domain characterized by complexity, dynamism, uncertainty, and risk in real-time operational contexts (Perrow, 1999; Woods et al, 1994). Nearly the entire gamut of human factors issues - for example, human-automation interaction (Sheridan and Parasuraman, 2006), telerobotics, display and control design (Smith, Bennett, and Stone, 2006), usability, anthropometry (Chaffin, 2008), biomechanics (Marras and Radwin, 2006), safety engineering, emergency operations, maintenance human factors, situation awareness (Tenney and Pew, 2006), crew resource management (Salas et al., 2006), methods for cognitive work analysis (Bisantz and Roth, 2008) and the like -- are applicable to astronauts, mission control, operational medicine, Space Shuttle manufacturing and assembly operations, and space suit designers as they are in other work domains (e.g., Bloomberg, 2003; Bos et al, 2006; Brooks and Ince, 1992; Casler and Cook, 1999; Jones, 1994; McCurdy et al, 2006; Neerincx et aI., 2006; Olofinboba and Dorneich, 2005; Patterson, Watts-Perotti and Woods, 1999; Patterson and Woods, 2001; Seagull et ai, 2007; Sierhuis, Clancey and Sims, 2002). The human exploration of space also has unique challenges of particular interest to human factors research and practice. This chapter provides an overview of those issues and reports on some of the latest research results as well as the latest challenges still facing the field.

Barreiro, J.↗
NASA NTRS2010

Human Factors in Space Exploration

The exploration of space is one of the most fascinating domains to study from a human factors perspective. Like other complex work domains such as aviation (Pritchett and Kim, 2008), air traffic management (Durso and Manning, 2008), health care (Morrow, North, and Wickens, 2006), homeland security (Cooke and Winner, 2008), and vehicle control (Lee, 2006), space exploration is a large-scale sociotechnical work domain characterized by complexity, dynamism, uncertainty, and risk in real-time operational contexts (Perrow, 1999; Woods et ai, 1994). Nearly the entire gamut of human factors issues - for example, human-automation interaction (Sheridan and Parasuraman, 2006), telerobotics, display and control design (Smith, Bennett, and Stone, 2006), usability, anthropometry (Chaffin, 2008), biomechanics (Marras and Radwin, 2006), safety engineering, emergency operations, maintenance human factors, situation awareness (Tenney and Pew, 2006), crew resource management (Salas et aI., 2006), methods for cognitive work analysis (Bisantz and Roth, 2008) and the like -- are applicable to astronauts, mission control, operational medicine, Space Shuttle manufacturing and assembly operations, and space suit designers as they are in other work domains (e.g., Bloomberg, 2003; Bos et al, 2006; Brooks and Ince, 1992; Casler and Cook, 1999; Jones, 1994; McCurdy et ai, 2006; Neerincx et aI., 2006; Olofinboba and Dorneich, 2005; Patterson, Watts-Perotti and Woods, 1999; Patterson and Woods, 2001; Seagull et ai, 2007; Sierhuis, Clancey and Sims, 2002). The human exploration of space also has unique challenges of particular interest to human factors research and practice. This chapter provides an overview of those issues and reports on sorne of the latest research results as well as the latest challenges still facing the field.

FROM↗
NASA NTRS1992

Domain specific software design for decision aiding

McDonnell Aircraft Company (MCAIR) is involved in many large multi-discipline design and development efforts of tactical aircraft. These involve a number of design disciplines that must be coordinated to produce an integrated design and a successful product. Our interpretation of a domain specific software design (DSSD) is that of a representation or framework that is specialized to support a limited problem domain. A DSSD is an abstract software design that is shaped by the problem characteristics. This parallels the theme of object-oriented analysis and design of letting the problem model directly drive the design. The DSSD concept extends the notion of software reusability to include representations or frameworks. It supports the entire software life cycle and specifically leads to improved prototyping capability, supports system integration, and promotes reuse of software designs and supporting frameworks. The example presented in this paper is the task network architecture or design which was developed for the MCAIR Pilot's Associate program. The task network concept supported both module development and system integration within the domain of operator decision aiding. It is presented as an instance where a software design exhibited many of the attributes associated with DSSD concept.

Keller, Kirby↗