SEARCH · Search NASA

Results for “knowledge capture”

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.

SourceResearch connectionFrom yearThrough year

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

At least 217 records · Page 12

All sources NASA NTRS DOE OSTI

NASA NTRS2004

The Power of Story: Dressing Up the Naked Truth

ASK Magazine is not alone when it comes to using storytelling to capture lessons learned and share knowledge. Several other practitioners have successfully introduced this approach to knowledge management within organizations. This article by Annette Simmons marks the first in a series ty authors whose work on storytelling has been widely recognized. We hope these features illuminate why ASK contributors use the story form to share their knowledge, and how you can do the same. Annette Simmons spoke at the February 2002 APPL Masters Forum.

Simmons, Annette↗

NASA NTRS2013

An Evidence Base for Human Spaceflight Risks in Wikipedia

NASA's Human Research Program (HRP) is focused on understanding and mitigating thirty two risks to crew health and performance in exploration missions beyond low Earth orbit. The HRP has developed an evidence report for each of the risks. Most evidence reports are a brief review article describing the evidence related to a specified risk, written at a level appropriate for the scientifically educated, non‐specialist reader. Each evidence report captured the current state of knowledge from both research and operations. Two limitations of the evidence reports have become apparent: 1) they are updated infrequently and 2) they do not take full advantage of the expertise available in other space agencies and in related fields of terrestrial research. Therefore, the HRP is experimenting with the use of Wikipedia articles as a repository for evidence. Wikipedia's accessibility to the international space flight community and researchers in related terrestrial fields creates the opportunity to generate a more timely and comprehensive evidence base. Initial Wikipedia articles were populated for seven risks using a subset of the information in the HRP‐approved evidence reports: Fatigue and Sleep Loss, Treating An Ill or Injured Crew Member, Radiation Carcinogenesis, Visual Impairment and Intracranial Pressure, Renal Stone Formation, Team Cohesion, and Intervertebral Disc Damage. Since the initial articles were created, there have been additions to these Wikipedia articles, including content from sources outside the HRP, and editorial changes to the pages. We will report on the nature of the contributions made after the initial articles were created, the comprehensiveness of the resulting Wikipedia articles, and the effort required to maintain quality control of the content. The Wikipedia approach will also be compared to wiki efforts that exert more traditional editorial control of content prior to posting.

Kundrot, Craig↗

NASA NTRS2021

Cryocooler Electronics Enable Thermal Imaging of Planetary Objects in Deep Space

Iris Technology Corporation received NASA SBIR awards to advance its cryocooler electronics, which control mechanical cryocoolers that enable thermal imaging systems to capture data to improve our knowledge of water and possibly life in space. Originally partnering with the Air Force SBIR program, Iris has since won several contracts to provide its cryocooler electronics on NASA missions — including a mission to examine the surface of Jupiter’s moon Europa — and on a satellite mission with the Air Force.

Mark H Davidson↗

NASA NTRS1993

System Diagnostic Builder - A rule generation tool for expert systems that do intelligent data evaluation

Consideration is given to the System Diagnostic Builder (SDB), an automated knowledge acquisition tool using state-of-the-art AI technologies. The SDB employs an inductive machine learning technique to generate rules from data sets that are classified by a subject matter expert. Thus, data are captured from the subject system, classified, and used to drive the rule generation process. These rule bases are used to represent the observable behavior of the subject system, and to represent knowledge about this system. The knowledge bases captured from the Shuttle Mission Simulator can be used as black box simulations by the Intelligent Computer Aided Training devices. The SDB can also be used to construct knowledge bases for the process control industry, such as chemical production or oil and gas production.

Nieten, Joseph↗

NASA NTRS1997

Evaluation of Flight Attendant Technical Knowledge

Accident and incident reports have indicated that flight attendants have numerous opportunities to provide the flight-deck crew with operational information that may prevent or lessen the severity of a potential problem. Additionally, as carrier fleets transition from three person to two person flight-deck crews, the reliance upon the cabin crew for the transfer of this information may increase further. Recent research indicates that flight attendants do not feel confident in their ability to describe mechanical parts or malfunctions of the aircraft, and the lack of flight attendant technical training has been referenced in a number of recent reports. Chute and Wiener describe five factors which may produce communication barriers between cockpit and cabin crews: the historical background of aviation, the physical separation of the two crews, psychosocial issues, regulatory factors, and organizational factors. By examining these areas of division we can identify possible bridges and address the implications of deficient cockpit/cabin communication on flight safety. Flight attendant operational knowledge may provide some mitigation of these barriers. The present study explored both flight attendant technical knowledge and flight attendant and pilot expectations of flight attendant technical knowledge. To assess the technical knowledge of cabin crewmembers, 177 current flight attendants from two U.S. carriers voluntarily completed a 13-item technical quiz. To investigate expectations of flight attendant technical knowledge, 181 pilots and a second sample of 96 flight attendants, from the same two airlines, completed surveys designed to capture each group's expectations of operational knowledge required of flight attendants. Analyses revealed several discrepancies between the present level of flight attendant operational knowledge and pilots' and flight attendants' expected and desired levels of technical knowledge. Implications for training will be discussed.

Dunbar, Melisa G.↗

NASA NTRS1998

Evaluation of Cabin Crew Technical Knowledge

Accident and incident reports have indicated that flight attendants have numerous opportunities to provide the flight-deck crew with operational information that may prevent or essen the severity of a potential problem. Additionally, as carrier fleets transition from three person to two person flight-deck crews, the reliance upon the cabin crew for the transfer of this information may increase further. Recent research (Chute & Wiener, 1996) indicates that light attendants do not feel confident in their ability to describe mechanical parts or malfunctions of the aircraft, and the lack of flight attendant technical training has been referenced in a number of recent reports (National Transportation Safety Board, 1992; Transportation Safety Board of Canada, 1995; Chute & Wiener, 1996). The present study explored both flight attendant technical knowledge and flight attendant and dot expectations of flight attendant technical knowledge. To assess the technical knowledge if cabin crewmembers, 177 current flight attendants from two U.S. carriers voluntarily :ompleted a 13-item technical quiz. To investigate expectations of flight attendant technical knowledge, 181 pilots and a second sample of 96 flight attendants, from the same two airlines, completed surveys designed to capture each group's expectations of operational knowledge required of flight attendants. Analyses revealed several discrepancies between the present level of flight attendants.

Dunbar, Melisa G.↗

NASA NTRS2011

The Planning Execution Monitoring Architecture

The Planning Execution Monitoring (PEM) architecture is a design concept for developing autonomous cockpit command and control software. The PEM architecture is designed to reduce the operations costs in the space transportation system through the use of automation while improving safety and operability of the system. Specifically, the PEM autonomous framework enables automatic performance of many vehicle operations that would typically be performed by a human. Also, this framework supports varying levels of autonomous control, ranging from fully automatic to fully manual control. The PEM autonomous framework interfaces with the core flight software to perform flight procedures. It can either assist human operators in performing procedures or autonomously execute routine cockpit procedures based on the operational context. Most importantly, the PEM autonomous framework promotes and simplifies the capture, verification, and validation of the flight operations knowledge. Through a hierarchical decomposition of the domain knowledge, the vehicle command and control capabilities are divided into manageable functional "chunks" that can be captured and verified separately. These functional units, each of which has the responsibility to manage part of the vehicle command and control, are modular, re-usable, and extensible. Also, the functional units are self-contained and have the ability to plan and execute the necessary steps for accomplishing a task based upon the current mission state and available resources. The PEM architecture has potential for application outside the realm of spaceflight, including management of complex industrial processes, nuclear control, and control of complex vehicles such as submarines or unmanned air vehicles.

Wang, Lui↗

NASA NTRS1991

Capturing flight system test engineering expertise: Lessons learned

Within a few years, JPL will be challenged by the most active mission set in history. Concurrently, flight systems are increasingly more complex. Presently, the knowledge to conduct integration and test of spacecraft and large instruments is held by a few key people, each with many years of experience. JPL is in danger of losing a significant amount of this critical expertise, through retirement, during a period when demand for this expertise is rapidly increasing. The most critical issue at hand is to collect and retain this expertise and develop tools that would ensure the ability to successfully perform the integration and test of future spacecraft and large instruments. The proposed solution was to capture and codity a subset of existing knowledge, and to utilize this captured expertise in knowledge-based systems. First year results and activities planned for the second year of this on-going effort are described. Topics discussed include lessons learned in knowledge acquisition and elicitation techniques, life-cycle paradigms, and rapid prototyping of a knowledge-based advisor (Spacecraft Test Assistant) and a hypermedia browser (Test Engineering Browser). The prototype Spacecraft Test Assistant supports a subset of integration and test activities for flight systems. Browser is a hypermedia tool that allows users easy perusal of spacecraft test topics. A knowledge acquisition tool called ConceptFinder which was developed to search through large volumes of data for related concepts is also described and is modified to semi-automate the process of creating hypertext links.

Woerner, Irene Wong↗

NASA NTRS1984

Measuring planetary hydrogen by remote gamma-ray sensing

The detection and measurement of hydrogen concentration and neutron leakage flux in planetary bodies by means of a proximate gamma-ray spectrometer (GRS) are discussed. The H concentration and the neutron flux are intimately linked in the planetary surface, and the measurement of hydrogen is dependent on knowledge of the neutron flux. The capture of thermal neutrons is responsible for the production of the 2.223 MeV line which characterizes hydrogen. The 2.223 MeV H signal is observed in the gamma-ray spectrum against an interference spectrum consisting of cosmic gamma rays, planetary background emission, and gamma rays arising from the interaction of cosmic rays with the GRS and the spacecraft (SC). An interfering line background results from the interaction of slow neutrons with H in the GRS and SC. The sources and magnitudes of the signal and background components in the H band are identified in terms of two missions, a lunar orbiter and a comet nucleus rendezvous. For the lunar mission, a 100 h observation at a 100 km altitude permits the detection of H at a level of 0.06 percent with an uncertainty of about 0.02 percent, while at an altitude equal to the radius of the comet's nucleus, in 100 h a GRS detects H at a level of 0.07 percent with an uncertainty of 0.06 percent.

Haines, E. L.↗

NASA NTRS1997

Application of Domain Knowledge to Software Quality Assurance

This work focused on capturing, using, and evolving a qualitative decision support structure across the life cycle of a project. The particular application of this study was towards business process reengineering and the representation of the business process in a set of Business Rules (BR). In this work, we defined a decision model which captured the qualitative decision deliberation process. It represented arguments both for and against proposed alternatives to a problem. It was felt that the subjective nature of many critical business policy decisions required a qualitative modeling approach similar to that of Lee and Mylopoulos. While previous work was limited almost exclusively to the decision capture phase, which occurs early in the project life cycle, we investigated the use of such a model during the later stages as well. One of our significant developments was the use of the decision model during the operational phase of a project. By operational phase, we mean the phase in which the system or set of policies which were earlier decided are deployed and put into practice. By making the decision model available to operational decision makers, they would have access to the arguments pro and con for a variety of actions and can thus make a more informed decision which balances the often conflicting criteria by which the value of action is measured. We also developed the concept of a 'monitored decision' in which metrics of performance were identified during the decision making process and used to evaluate the quality of that decision. It is important to monitor those decision which seem at highest risk of not meeting their stated objectives. Operational decisions are also potentially high risk decisions. Finally, we investigated the use of performance metrics for monitored decisions and audit logs of operational decisions in order to feed an evolutionary phase of the the life cycle. During evolution, decisions are revisisted, assumptions verified or refuted, and possible reassessments resulting in new policy are made. In this regard we implemented a machine learning algorithm which automatically defined business rules based on expert assessment of the quality of operational decisions as recorded during deployment.

Wild, Christian W.↗

NASA NTRS2006

Knowledge management in the engineering design environment

The Aerospace and Defense industry is experiencing an increasing loss of knowledge through workforce reductions associated with business consolidation and retirement of senior personnel. Significant effort is being placed on process definition as part of ISO certification and, more recently, CMMI certification. The process knowledge in these efforts represents the simplest of engineering knowledge and many organizations are trying to get senior engineers to write more significant guidelines, best practices and design manuals. A new generation of design software, known as Product Lifecycle Management systems, has many mechanisms for capturing and deploying a wider variety of engineering knowledge than simple process definitions. These hold the promise of significant improvements through reuse of prior designs, codification of practices in workflows, and placement of detailed how-tos at the point of application.

designs↗

NASA NTRS2010

The Value of Identifying and Recovering Lost GN&C Lessons Learned: Aeronautical, Spacecraft, and Launch Vehicle Examples

Within the broad aerospace community the importance of identifying, documenting and widely sharing lessons learned during system development, flight test, operational or research programs/projects is broadly acknowledged. Documenting and sharing lessons learned helps managers and engineers to minimize project risk and improve performance of their systems. Often significant lessons learned on a project fail to get captured even though they are well known 'tribal knowledge' amongst the project team members. The physical act of actually writing down and documenting these lessons learned for the next generation of NASA GN&C engineers fails to happen on some projects for various reasons. In this paper we will first review the importance of capturing lessons learned and then will discuss reasons why some lessons are not documented. A simple proven approach called 'Pause and Learn' will be highlighted as a proven low-impact method of organizational learning that could foster the timely capture of critical lessons learned. Lastly some examples of 'lost' GN&C lessons learned from the aeronautics, spacecraft and launch vehicle domains are briefly highlighted. In the context of this paper 'lost' refers to lessons that have not achieved broad visibility within the NASA-wide GN&C CoP because they are either undocumented, masked or poorly documented in the NASA Lessons Learned Information System (LLIS).

Dennehy, Cornelius J.↗

NASA NTRS1995

Fuzzy logic techniques for rendezvous and docking of two geostationary satellites

Large assemblings in space require the ability to manage rendezvous and docking operations. In future these techniques will be required for the gradual build up of big telecommunication platforms in the geostationary orbit. The paper discusses the use of fuzzy logic to model and implement a control system for the docking/berthing of two satellites in geostationary orbit. The system mounted in a chaser vehicle determines the actual state of both satellites and generates torques to execute maneuvers to establish the structural latching. The paper describes the proximity operations to collocate the two satellites in the same orbital window, the fuzzy guidance and navigation of the chaser approaching the target and the final Fuzzy berthing. The fuzzy logic system represents a knowledge based controller that realizes the close loop operations autonomously replacing the conventional control algorithms. The goal is to produce smooth control actions in the proximity of the target and during the docking to avoid disturbance torques in the final assembly orbit. The knowledge of the fuzzy controller consists of a data base of rules and the definitions of the fuzzy sets. The knowledge of an experienced spacecraft controller is captured into a set of rules forming the Rules Data Base.

Ortega, Guillermo↗

NASA NTRS2001

D3: A Collaborative Infrastructure for Aerospace Design

Walton, Joan↗

NASA NTRS2004

Specification, Design, and Analysis of Advanced HUMS Architectures

During the two-year project period, we have worked on several aspects of domain-specific architectures for HUMS. In particular, we looked at using scenario-based approach for the design and designed a language for describing such architectures. The language is now being used in all aspects of our HUMS design. In particular, we have made contributions in the following areas. 1) We have employed scenarios in the development of HUMS in three main areas. They are: (a) To improve reusability by using scenarios as a library indexing tool and as a domain analysis tool; (b) To improve maintainability by recording design rationales from two perspectives - problem domain and solution domain; (c) To evaluate the software architecture. 2) We have defined a new architectural language called HADL or HUMS Architectural Definition Language. It is a customized version of xArch/xADL. It is based on XML and, hence, is easily portable from domain to domain, application to application, and machine to machine. Specifications written in HADL can be easily read and parsed using the currently available XML parsers. Thus, there is no need to develop a plethora of software to support HADL. 3) We have developed an automated design process that involves two main techniques: (a) Selection of solutions from a large space of designs; (b) Synthesis of designs. However, the automation process is not an absolute Artificial Intelligence (AI) approach though it uses a knowledge-based system that epitomizes a specific HUMS domain. The process uses a database of solutions as an aid to solve the problems rather than creating a new design in the literal sense. Since searching is adopted as the main technique, the challenges involved are: (a) To minimize the effort in searching the database where a very large number of possibilities exist; (b) To develop representations that could conveniently allow us to depict design knowledge evolved over many years; (c) To capture the required information that aid the automation process.

Mukkamala, Ravi↗

NASA NTRS2002

The D3 Middleware Architecture

DARWIN is a NASA developed, Internet-based system for enabling aerospace researchers to securely and remotely access and collaborate on the analysis of aerospace vehicle design data, primarily the results of wind-tunnel testing and numeric (e.g., computational fluid-dynamics) model executions. DARWIN captures, stores and indexes data; manages derived knowledge (such as visualizations across multiple datasets); and provides an environment for designers to collaborate in the analysis of test results. DARWIN is an interesting application because it supports high-volumes of data. integrates multiple modalities of data display (e.g., images and data visualizations), and provides non-trivial access control mechanisms. DARWIN enables collaboration by allowing not only sharing visualizations of data, but also commentary about and views of data. Here we provide an overview of the architecture of D3, the third generation of DARWIN. Earlier versions of DARWIN were characterized by browser-based interfaces and a hodge-podge of server technologies: CGI scripts, applets, PERL, and so forth. But browsers proved difficult to control, and a proliferation of computational mechanisms proved inefficient and difficult to maintain. D3 substitutes a pure-Java approach for that medley: A Java client communicates (though RMI over HTTPS) with a Java-based application server. Code on the server accesses information from JDBC databases, distributed LDAP security services, and a collaborative information system. D3 is a three tier-architecture, but unlike 'E-commerce' applications, the data usage pattern suggests different strategies than traditional Enterprise Java Beans - we need to move volumes of related data together, considerable processing happens on the client, and the 'business logic' on the server-side is primarily data integration and collaboration. With D3, we are extending DARWIN to handle other data domains and to be a distributed system, where a single login allows a user transparent access to test results from multiple servers and authority domains.

Walton, Joan↗

NASA NTRS2012

Detached Eddy Simulation of the UH-60 Rotor Wake Using Adaptive Mesh Refinement

Time-dependent Navier-Stokes flow simulations have been carried out for a UH-60 rotor with simplified hub in forward flight and hover flight conditions. Flexible rotor blades and flight trim conditions are modeled and established by loosely coupling the OVERFLOW Computational Fluid Dynamics (CFD) code with the CAMRAD II helicopter comprehensive code. High order spatial differences, Adaptive Mesh Refinement (AMR), and Detached Eddy Simulation (DES) are used to obtain highly resolved vortex wakes, where the largest turbulent structures are captured. Special attention is directed towards ensuring the dual time accuracy is within the asymptotic range, and verifying the loose coupling convergence process using AMR. The AMR/DES simulation produced vortical worms for forward flight and hover conditions, similar to previous results obtained for the TRAM rotor in hover. AMR proved to be an efficient means to capture a rotor wake without a priori knowledge of the wake shape.

Chaderjian, Neal M.↗

NASA NTRS2017

JANNAF "Test and Evaluation Guidelines for Liquid Rocket Engines": Status and Application

For many decades, the U.S. rocket propulsion industrial base has performed remarkably in developing complex liquid rocket engines that can propel critical payloads into service for the nation, as well as transport people and hardware for missions that open the frontiers of space exploration for humanity. This has been possible only at considerable expense given the lack of detailed guidance that captures the essence of successful practices and knowledge accumulated over five decades of liquid rocket engine development. In an effort to provide benchmarks and guidance for the next generation of rocket engineers, the Joint Army Navy NASA Air Force (JANNAF) Interagency Propulsion Committee published a liquid rocket engine (LRE) test and evaluation (T&E) guideline document in 2012 focusing on the development challenges and test verification considerations for liquid rocket engine systems. This document has been well received and applied by many current LRE developers as a benchmark and guidance tool, both for government-driven applications as well as for fully commercial ventures. The USAF Space and Missile Systems Center (SMC) has taken an additional near-term step and is directing activity to adapt and augment the content from the JANNAF LRE T&E guideline into a standard for potential application to future USAF requests for proposals for LRE development initiatives and launch vehicles for national security missions. A draft of this standard was already sent out for review and comment, and is intended to be formally approved and released towards the end of 2017. The acceptance and use of the LRE T&E guideline is possible through broad government and industry participation in the JANNAF liquid propulsion committee and associated panels. The sponsoring JANNAF community is expanding upon this initial baseline version and delving into further critical development aspects of liquid rocket propulsion testing at the integrated stage level as well as engine component level, in order to advance the state of the practice. The full participation of the entire U.S. rocket propulsion industrial base is invited and expected at this opportune moment in the continuing advancement of spaceflight technology.

Parkinson, Douglas↗