Search NASA⌕ Search

SEARCH · Search NASA

Results for “Prototype tool”

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

Supplying the Giant

It was critical for our team to find a radically different way of doing business. Deciding to build the airframe out of composites was the first step, refining processes from the boat building industry was second, and the final step was choosing a supplier. Lockheed Martin built the first prototypes at our Skunk Works facility in Palmdale, California. These units were hand-built and used early prototypical tooling. They looked great but were not affordable. We had to focus on minimizing touch labor and cycle time and reducing material costs. We needed a company to produce the composite quilts we would use to avoid hand lay-ups. The company we found surprised a lot of people. We partnered with a small company outside of Boston whose primary business was making baseball bats and golf club shafts.

Lawson, Larry↗
NASA NTRS2005

Black Box Testing: Experiments with Runway Incursion Advisory Alerting System

This report summarizes our research findings on the Black box testing of Runway Incursion Advisory Alerting System (RIAAS) and Runway Safety Monitor (RSM) system. Developing automated testing software for such systems has been a problem because of the extensive information that has to be processed. Customized software solutions have been proposed. However, they are time consuming to develop. Here, we present a less expensive, and a more general test platform that is capable of performing complete black box testing. The technique is based on the classification of the anomalies that arise during Monte Carlo simulations. In addition, we also discuss a generalized testing tool (prototype) that we have developed.

Mukkamala, Ravi↗
NASA NTRS2012

Linguistic Preprocessing and Tagging for Problem Report Trend Analysis

Mr. Robert Beil, Systems Engineer at Kennedy Space Center (KSC), requested the NASA Engineering and Safety Center (NESC) develop a prototype tool suite that combines complementary software technology used at Johnson Space Center (JSC) and KSC for problem report preprocessing and semantic tag extraction, to improve input to data mining and trend analysis. This document contains the outcome of the assessment and the Findings, Observations and NESC Recommendations.

Beil, Robert J.↗
NASA NTRS2014

An Overview of Current Capabilities and Research Activities in the Airspace Operations Laboratory at NASA Ames Research Center

The Airspace Operations Laboratory at NASA Ames conducts research to provide a better understanding of roles, responsibilities, and requirements for human operators and automation in future air traffic management (ATM) systems. The research encompasses developing, evaluating, and integrating operational concepts and technologies for near-, mid-, and far-term air traffic operations. Current research threads include efficient arrival operations, function allocation in separation assurance and efficient airspace and trajectory management. The AOL has developed powerful air traffic simulation capabilities, most notably the Multi Aircraft Control System (MACS) that is used for many air traffic control simulations at NASA and its partners in government, academia and industry. Several additional NASA technologies have been integrated with the AOL's primary simulation capabilities where appropriate. Using this environment, large and small-scale system-level evaluations can be conducted to help make near-term improvements and transition NASA technologies to the FAA, such as the technologies developed under NASA's Air Traffic Management Demonstration-1 (ATD-1). The AOL's rapid prototyping and flexible simulation capabilities have proven a highly effective environment to progress the initiation of trajectory-based operations and support the mid-term implementation of NextGen. Fundamental questions about accuracy requirements have been investigated as well as realworld problems on how to improve operations in some of the most complex airspaces in the US. This includes using advanced trajectory-based operations and prototype tools for coordinating arrivals to converging runways at Newark airport and coordinating departures and arrivals in the San Francisco and the New York metro areas. Looking beyond NextGen, the AOL has started exploring hybrid human/automation control strategies as well as highly autonomous operations in the air traffic control domain. Initial results indicate improved capacity, low operator workload, good situation awareness and acceptability for controllers teaming with autonomous air traffic systems. While much research and development needs to be conducted to make such concepts a reality, these approaches have the potential to truly transform the airspace system towards increased mobility, safe and efficient growth in global operations and enabling many of the new vehicles and operations that are expected over the next decades. This paper describes how the AOL currently contributes to the ongoing air transportation transformation.

simulation↗
NASA NTRS2014

State Event Models for the Formal Analysis of Human-Machine Interactions

The work described in this paper was motivated by our experience with applying a framework for formal analysis of human-machine interactions (HMI) to a realistic model of an autopilot. The framework is built around a formally defined conformance relation called "fullcontrol" between an actual system and the mental model according to which the system is operated. Systems are well-designed if they can be described by relatively simple, full-control, mental models for their human operators. For this reason, our framework supports automated generation of minimal full-control mental models for HMI systems, where both the system and the mental models are described as labelled transition systems (LTS). The autopilot that we analysed has been developed in the NASA Ames HMI prototyping tool ADEPT. In this paper, we describe how we extended the models that our HMI analysis framework handles to allow adequate representation of ADEPT models. We then provide a property-preserving reduction from these extended models to LTSs, to enable application of our LTS-based formal analysis algorithms. Finally, we briefly discuss the analyses we were able to perform on the autopilot model with our extended framework.

State-event Models↗
NASA NTRS2016

Assurance of Fault Management: Risk-Significant Adverse Condition Awareness

Fault Management (FM) systems are ranked high in risk-based assessment of criticality within flight software, emphasizing the importance of establishing highly competent domain expertise to provide assurance for NASA projects, especially as spaceflight systems continue to increase in complexity. Insight into specific characteristics of FM architectures seen embedded within safety- and mission-critical software systems analyzed by the NASA Independent Verification Validation (IVV) Program has been enhanced with an FM Technical Reference (TR) suite. Benefits are aimed beyond the IVV community to those that seek ways to efficiently and effectively provide software assurance to reduce the FM risk posture of NASA and other space missions. The identification of particular FM architectures, visibility, and associated IVV techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. The role FM has with regard to overall asset protection of flight software systems is being addressed with the development of an adverse condition (AC) database encompassing flight software vulnerabilities.Identification of potential off-nominal conditions and analysis to determine how a system responds to these conditions are important aspects of hazard analysis and fault management. Understanding what ACs the mission may face, and ensuring they are prevented or addressed is the responsibility of the assurance team, which necessarily should have insight into ACs beyond those defined by the project itself. Research efforts sponsored by NASAs Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs, and allowing queries based on project, mission type, domain component, causal fault, and other key characteristics. The repository has a firm structure, initial collection of data, and an interface established for informational queries, with plans for integration within the Enterprise Architecture at NASA IVV, enabling support and accessibility across the Agency. The development of an improved workflow process for adaptive, risk-informed FM assurance is currently underway.

Software Verification & Validation↗
NASA NTRS2017

Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification & Validation (IV&V) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASAs Office of Safety and Mission Assurance (OSMA) defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domain/component, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IV&V enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this database for adaptive, risk-informed FM assurance that critical software systems will safely and securely protect against faults and respond to ACs in order to achieve successful missions.

IV&V↗
NASA NTRS2017

Risk-Significant Adverse Condition Awareness Strengthens Assurance of Fault Management Systems

As spaceflight systems increase in complexity, Fault Management (FM) systems are ranked high in risk-based assessment of software criticality, emphasizing the importance of establishing highly competent domain expertise to provide assurance. Adverse conditions (ACs) and specific vulnerabilities encountered by safety- and mission-critical software systems have been identified through efforts to reduce the risk posture of software-intensive NASA missions. Acknowledgement of potential off-nominal conditions and analysis to determine software system resiliency are important aspects of hazard analysis and FM. A key component of assuring FM is an assessment of how well software addresses susceptibility to failure through consideration of ACs. Focus on significant risk predicted through experienced analysis conducted at the NASA Independent Verification Validation (IVV) Program enables the scoping of effective assurance strategies with regard to overall asset protection of complex spaceflight as well as ground systems. Research efforts sponsored by NASA's Office of Safety and Mission Assurance defined terminology, categorized data fields, and designed a baseline repository that centralizes and compiles a comprehensive listing of ACs and correlated data relevant across many NASA missions. This prototype tool helps projects improve analysis by tracking ACs and allowing queries based on project, mission type, domaincomponent, causal fault, and other key characteristics. Vulnerability in off-nominal situations, architectural design weaknesses, and unexpected or undesirable system behaviors in reaction to faults are curtailed with the awareness of ACs and risk-significant scenarios modeled for analysts through this database. Integration within the Enterprise Architecture at NASA IVV enables interfacing with other tools and datasets, technical support, and accessibility across the Agency. This paper discusses the development of an improved workflow process utilizing this database for adaptive, risk-informed FM assurance that critical software systems will safely and securely protect against faults and respond to ACs in order to achieve successful missions.

Fault management↗
NASA NTRS2018

An Abstract Interpretation Framework for the Round-Off Error Analysis of Floating-Point Programs

This paper presents an abstract interpretation framework for the round-off error analysis of floating-point programs. This framework defines a parametric abstract analysis that computes, for each combination of ideal and floating-point execution path of the program, a sound over-approximation of the accumulated floating-point round-off error that may occur. In addition, a Boolean expression that characterizes the input values leading to the computed error approximation is also computed. An abstraction on the control flow of the program is proposed to mitigate the explosion of the number of elements generated by the analysis. Additionally, a widening operator is defined to ensure the convergence of recursive functions and loops. An instantiation of this framework is implemented in the prototype tool PRECiSA that generates formal proof certificates stating the correctness of the computed round-off errors.

Titolo, Laura↗
NASA NTRS2023

Exploration Habitat (X-Hab) 2013-2014 Academic Innovation Challenge

Outreach activities were coordinated with OSU’s NASA Education Office and focused around the Space Habitat Innovation Challenge. Two challenges were developed for this year: the Rapidly Prototyped Tool Challenge (RaPTC) and the Space Habitat Airlock Challenge (SHAC). RaPTC was open to eligible high school student teams while SHAC was open to eligible community college student teams. Teams involved 3-6 students from 12 states across the country and submitted videos or virtual presentations.1 Entries were judged by the OSU XHab students and were provided with feedback on feasibility and design. Three groups in each challenge were selected as finalists for a final virtual presentation and interview with students and professors in the engineering program at Oklahoma State University. Three groups total were selected to present their design to engineers and astronauts at a NASA JSC. Judges included astronauts Joe Acaba, Nicole Stott, and Dottie Metcalf-Lindenburger.

Jamey D Jacob↗
NASA NTRS2024

A Computational Framework for Making Early Design Decisions in Deep Space Habitats

The dynamics of systems of systems often involve complex interactions among the individual systems, making the implications of design choices challenging to predict. Design features in such systems may trigger unexpected behaviors or result in large variations in safety, performance or resilience. To provide a means of simulating such systems for aiding in these decisions, we have developed a prototype tool, the control-oriented dynamic computational modeling tool (CDCM). The CDCM provides rapid simulation capabilities to perform trade studies in systems of systems. The general class of systems of systems that we aim to examine involve multiple hazards, damage, cascading consequences, repair and recovery. We especially focus on systems-of-systems that incorporate a health management system (HMS) that can monitor the state of the habitat and make decisions about actions to take. In this paper we describe the features of the CDCM, the architecture we devised for simulation of systems-of-systems, the unique functionalities of this tool, and we provide a demonstration of the capabilities by performing two illustrative examples. We articulate the use of this tool for making early design decisions and demonstrate its use for trade studies that consider a model of a deep space habitat. We also share some experiences and lessons that may be useful for others seeking to address similar problems.

Amir Behjat↗
NASA NTRS1988

Development of a prototype commonality analysis tool for use in space programs

A software tool to aid in performing commonality analyses, called Commonality Analysis Problem Solver (CAPS), was designed, and a prototype version (CAPS 1.0) was implemented and tested. The CAPS 1.0 runs in an MS-DOS or IBM PC-DOS environment. The CAPS is designed around a simple input language which provides a natural syntax for the description of feasibility constraints. It provides its users with the ability to load a database representing a set of design items, describe the feasibility constraints on items in that database, and do a comprehensive cost analysis to find the most economical substitution pattern.

Yeager, Dorian P.↗
NASA NTRS2008

Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.

Leucht, Kurt W.↗
NASA NTRS1994

Robotic Tool Changer For Automated Welding

Prototype robotic tool changer for automated welding system eliminates need for most manual tool setups and attendant problems: operates rapidly, always chooses designated tool, maneuvers tip of welding torch or other tool in correct position, and reliably connects water, gas, welding wire, high-voltage electrical signals, and ground. Also loads tools other than those for welding. Intended for use in robotic work cell producing all good parts, no rejects. In production, robot welds part, tests for flaws, and reworks as necessary before releasing it.

Gilbert, Jeffrey L.↗
NASA NTRS1998

Virtual Environment Design for Low/Zero Visibility Tower Tools

This paper describes prototype software for three-dimensional display of aircraft movement based on realtime radar and other Air Traffic Control (ATC) information. This prototype can be used to develop operational tools for controllers in ATC Towers who cannot view aircraft in low or zero visibility (LZV) weather conditions. The controller could also use the software to arbitrarily reposition his virtual eyepoint to overcome physical obstructions or increase situation awareness. The LZV Tower tool prototype consists of server and client components. The server interfaces to operational ATC radar and communications systems, sending processed data to a client process written in java. This client process runs under Netscape Communicator to provide an interactive perspective display of aircraft in the airport environment. Prototype VRML airport models were derived from 3-D databases used in FAA-certified high fidelity flight-simulators. The web-based design offers potential efficiency increases and decreased costs in the development and deployment of operational LZV Tower tools.

Reisman, Ron↗
NASA NTRS1992

The MERMAID project

The tendency for software development projects to be completed over schedule and over budget was documented extensively. Additionally many projects are completed within budgetary and schedule target only as a result of the customer agreeing to accept reduced functionality. In his classic book, The Mythical Man Month, Fred Brooks exposes the fallacy that effort and schedule are freely interchangeable. All current cost models are produced on the assumption that there is very limited scope for schedule compression unless there is a corresponding reduction in delivered functionality. The Metrication and Resources Modeling Aid (MERMAID) project, partially financed by the Commission of the European Communities (CEC) as Project 2046 began in Oct. 1988 and its goal were as follows: (1) improvement of understanding of the relationships between software development productivity and product and process metrics; (2) to facilitate the widespread technology transfer from the Consortium to the European Software Industry; and (3) to facilitate the widespread uptake of cost estimation techniques by the provision of prototype cost estimation tools. MERMAID developed a family of methods for cost estimation, many of which have had tools implemented in prototypes. These prototypes are best considered as toolkits or workbenches.

Cowderoy, A. J. C.↗