Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “knowledge engineering”

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRS1990

First CLIPS Conference Proceedings, volume 1

The first Conference of C Language Production Systems (CLIPS) hosted by the NASA-Lyndon B. Johnson Space Center in August 1990 is presented. Articles included engineering applications, intelligent tutors and training, intelligent software engineering, automated knowledge acquisition, network applications, verification and validation, enhancements to CLIPS, space shuttle quality control/diagnosis applications, space shuttle and real-time applications, and medical, biological, and agricultural applications.

Source record↗
NASA NTRS1996

Materials All Around Us

The purpose of this journal exercise is to determine the properties of the materials in the environment around us, and to relate these properties to the materials systems for which they are used. Students will develop a strong rationale for gaining knowledge of engineering materials. The journal entries will serve as a starting point classroom discussion. Along with the journal, students are required to bring samples to class of 'found' materials and products composed of materials systems. Students are encouraged to be materials observers.

Jacobs, James A.↗
NASA NTRS2001

Ask Pete, software planning and estimation through project characterization

Ask Pete, was developed by NASA to provide a tool for integrating the estimation and planning activities for a software development effort. It incorporates COCOMO II estimating with NASA's software development practices and IV&V criteria to characterize a project. This characterization is then used to generate estimates and tailored planning documents.

Project characterization↗
NASA NTRS1999

New frontiers in design synthesis

The Intelligent Synthesis Environment (ISE), which is one of the major strategic technologies under development at NASA centers and the University of Virginia, is described. One of the major objectives of ISE is to significantly enhance the rapid creation of innovative affordable products and missions. ISE uses a synergistic combination of leading-edge technologies, including high performance computing, high capacity communications and networking, human-centered computing, knowledge-based engineering, computational intelligence, virtual product development, and product information management. The environment will link scientists, design teams, manufacturers, suppliers, and consultants who participate in the mission synthesis as well as in the creation and operation of the aerospace system. It will radically advance the process by which complex science missions are synthesized, and high-tech engineering Systems are designed, manufactured and operated. The five major components critical to ISE are human-centered computing, infrastructure for distributed collaboration, rapid synthesis and simulation tools, life cycle integration and validation, and cultural change in both the engineering and science creative process. The five components and their subelements are described. Related U.S. government programs are outlined and the future impact of ISE on engineering research and education is discussed.

User-Computer Interface↗
NASA NTRS2008

SHINE Virtual Machine Model for In-flight Updates of Critical Mission Software

This software is a new target for the Spacecraft Health Inference Engine (SHINE) knowledge base that compiles a knowledge base to a language called Tiny C - an interpreted version of C that can be embedded on flight processors. This new target allows portions of a running SHINE knowledge base to be updated on a "live" system without needing to halt and restart the containing SHINE application. This enhancement will directly provide this capability without the risk of software validation problems and can also enable complete integration of BEAM and SHINE into a single application. This innovation enables SHINE deployment in domains where autonomy is used during flight-critical applications that require updates. This capability eliminates the need for halting the application and performing potentially serious total system uploads before resuming the application with the loss of system integrity. This software enables additional applications at JPL (microsensors, embedded mission hardware) and increases the marketability of these applications outside of JPL.

Plesea, Lucian↗
NASA NTRS2006

Automated Activation and Deactivation of a System Under Test

The MPLM Automated Activation/Deactivation application (MPLM means Multi-Purpose Logistic Module) was created with a three-fold purpose in mind: 1. To reduce the possibility of human error in issuing commands to, or interpreting telemetry from, the MPLM power, computer, and environmental control systems; 2. To reduce the amount of test time required for the repetitive activation/deactivation processes; and 3. To reduce the number of on-console personnel required for activation/ deactivation. All of these have been demonstrated with the release of the software. While some degree of automated end-item commanding had previously been performed for space-station hardware in the test environment, none approached the functionality and flexibility of this application. For MPLM activation, it provides mouse-click selection of the hardware complement to be activated, activates the desired hardware and verifies proper feedbacks, and alerts the user when telemetry indicates an error condition or manual intervention is required. For MPLM deactivation, the product senses which end items are active and deactivates them in the proper sequence. For historical purposes, an on-line log is maintained of commands issued and telemetry points monitored. The benefits of the MPLM Automated Activation/ Deactivation application were demonstrated with its first use in December 2002, when it flawlessly performed MPLM activation in 8 minutes (versus as much as 2.4 hours for previous manual activations), and performed MPLM deactivation in 3 minutes (versus 66 minutes for previous manual deactivations). The number of test team members required has dropped from eight to four, and in actuality the software can be operated by a sole (knowledgeable) system engineer.

Poff, Mark A.↗
NASA NTRS2010

Integrated System Health Management: Pilot Operational Implementation in a Rocket Engine Test Stand

This paper describes a credible implementation of integrated system health management (ISHM) capability, as a pilot operational system. Important core elements that make possible fielding and evolution of ISHM capability have been validated in a rocket engine test stand, encompassing all phases of operation: stand-by, pre-test, test, and post-test. The core elements include an architecture (hardware/software) for ISHM, gateways for streaming real-time data from the data acquisition system into the ISHM system, automated configuration management employing transducer electronic data sheets (TEDS?s) adhering to the IEEE 1451.4 Standard for Smart Sensors and Actuators, broadcasting and capture of sensor measurements and health information adhering to the IEEE 1451.1 Standard for Smart Sensors and Actuators, user interfaces for management of redlines/bluelines, and establishment of a health assessment database system (HADS) and browser for extensive post-test analysis. The ISHM system was installed in the Test Control Room, where test operators were exposed to the capability. All functionalities of the pilot implementation were validated during testing and in post-test data streaming through the ISHM system. The implementation enabled significant improvements in awareness about the status of the test stand, and events and their causes/consequences. The architecture and software elements embody a systems engineering, knowledge-based approach; in conjunction with object-oriented environments. These qualities are permitting systematic augmentation of the capability and scaling to encompass other subsystems.

Figueroa, Fernando↗
NASA NTRS2006

Adaptive Modeling Language and Its Derivatives

Adaptive Modeling Language (AML) is the underlying language of an object-oriented, multidisciplinary, knowledge-based engineering framework. AML offers an advanced modeling paradigm with an open architecture, enabling the automation of the entire product development cycle, integrating product configuration, design, analysis, visualization, production planning, inspection, and cost estimation.

Chemaly, Adel↗
NASA NTRS2010

Establishing Consensus Turbulence Statistics for Hot Subsonic Jets

Many tasks in fluids engineering require knowledge of the turbulence in jets. There is a strong, although fragmented, literature base for low order statistics, such as jet spread and other meanvelocity field characteristics. Some sources, particularly for low speed cold jets, also provide turbulence intensities that are required for validating Reynolds-averaged Navier-Stokes (RANS) Computational Fluid Dynamics (CFD) codes. There are far fewer sources for jet spectra and for space-time correlations of turbulent velocity required for aeroacoustics applications, although there have been many singular publications with various unique statistics, such as Proper Orthogonal Decomposition, designed to uncover an underlying low-order dynamical description of turbulent jet flow. As the complexity of the statistic increases, the number of flows for which the data has been categorized and assembled decreases, making it difficult to systematically validate prediction codes that require high-level statistics over a broad range of jet flow conditions. For several years, researchers at NASA have worked on developing and validating jet noise prediction codes. One such class of codes, loosely called CFD-based or statistical methods, uses RANS CFD to predict jet mean and turbulent intensities in velocity and temperature. These flow quantities serve as the input to the acoustic source models and flow-sound interaction calculations that yield predictions of far-field jet noise. To develop this capability, a catalog of turbulent jet flows has been created with statistics ranging from mean velocity to space-time correlations of Reynolds stresses. The present document aims to document this catalog and to assess the accuracies of the data, e.g. establish uncertainties for the data. This paper covers the following five tasks: Document acquisition and processing procedures used to create the particle image velocimetry (PIV) datasets. Compare PIV data with hotwire and laser Doppler velocimetry (LDV) data published in the open literature. Compare different datasets acquired at roughly the same flow conditions to establish uncertainties. Create a consensus dataset for a range of hot jet flows, including uncertainty bands. Analyze this consensus dataset for self-consistency and compare jet characteristics to those of the open literature. One final objective fulfilled by this work was the demonstration of a universal scaling for the jet flow fields, at least within the region of interest to aeroacoustics. The potential core length and the spread rate of the half-velocity radius were used to collapse of the mean and turbulent velocity fields over the first 20 jet diameters in a highly satisfying manner.

Bridges, James↗
NASA NTRS1970

Skylab Operations Handbook: Orbital Workshop (OWS), Airlock Module (AM), Multiple Docking Adapter (MDA): Systems Descriptions - Volume 1

The Skylab Program consists of three low-earth-orbit missions of the Orbital Assembly (OA) (figure 1.0-1), extending over.an a-month period. The OA consists of the CSM docked to the Saturn Workshop.(SWS). This handbook describes the systems for three of the four major components of the SWS (OWS, AM, and MDA), and also discusses significant interfaces with the Instrument Unit (IU), ATM, and CSM. The other major component of the SWS, the ATM, is treated separately in its own handbook. The OWS, AM, MDA, ATM Deployment Assembly (ATM-DA), Fixed Airlock Shroud (FAS), Payload Shroud (PS), and IU are addressed throughout this document as individual modules from a structural standpoint only. Although normally considered a part of the launch vehicle, the IU is treated in this document as part of the SWS because of its function in preparing the SWS for orbital operation. Section 1.0 describes vehicle and mission configurations of the Skylab program and provides general descriptions of the various systems. Section 2.0 provides detailed systems data covering system interfaces, functional description, subsystems and major components description, component operation, failure modes, performance and design data, operational limitations and restrictions, and instrumentation, and briefly outlines the experiments. Section 3.0 contains illustrations of all panels and identifies the controls and displays, panels, reference designators, nomenclature, functions, circuit breakers, and power sources. The Table of Contents lists in order of appearance all sections, subsections, major paragraphs, illustrations, and tables and provides their respective page locations. Appendix A defines the abbreviations and acronyms employed throughout this handbook, and Appendix B explains the symbols used. Appendix C is a locator index that references component controls contained in Section 3.0. Appendix D is an alphabetical index of paragraph headings, illustrations, and tables, according to the key word, with applicable page numbers. Additional items of significance to the user have been included in the index. The technical level to which this document is written assumes the reader to have general knowledge of engineering terms and principles.

West, W. D.↗
NASA NTRSDate not supplied

A Lunar Water ISRU System Study for Human-Scale Propellant Production

NASA’s plans to return to the moon in the Artemis campaign include intentions for sustainable surface operations. In-Situ Resource Utilization (ISRU) is key to enabling sustainability. The use of water, which has been identified in the lunar polar regions [1-4], could be pivotal to a sustainable architecture. While water has been identified, there is limited information regarding its form and distribution. The Lunar Water ISRU Measurement Study (LWIMS) [5] outlined the current state of knowledge regarding water resources on the moon, what information is lacking, and how to approach a measurement campaign to close those knowledge gaps. However the NASA timeline necessitates that lunar surface water prospecting, or reconnaissance, efforts and ISRU system design to occur in parallel. ISRU hardware and systems development must proceed without key resource knowledge. Yet, engineering design requires come constraints and targets to work to. The goal of this study was to define a set of lunar water reference cases, based on the cur-rent lunar water information, to help focus ISRU de-sign and planning. This approach is similar to an study focused on Mars resources called Mars Water ISRU Planning (MWIP) [6].

Lunar Water↗
NASA NTRSDate not supplied

Additive Manufacturing for Propulsion Applications

This event will improve MSFC team members’ understanding and awareness of Agency strategy related to advanced manufacturing subjects. With a focus toward growing Engineering Directorate knowledge of the selected topics, Subject Matter Experts will provide lectures on the technologies that MSFC will need to leverage in order successfully achieve new objectives related to our role in On-Orbit-Servicing, Assembly, and Manufacturing (OSAM) and provide updates on Center Initiatives. The workshop will conclude with a panel discussion including MSFC leaders from discipline and project formulation offices with conversations related to innovative technologies.

Additive Manufacturing↗
NASA NTRSDate not supplied

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗
NASA NTRSDate not supplied

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗
DOE OSTI2021

SMART-COM – Scalable Multi-Agent Adaptive Resolution Tools for Collaborative Outage Management

The purpose of this grant was to conduct scientific research and prototype applications to support NPP outage staff in their adaptive decision-making in efficient scheduling and resource allocation while preventing violation of safety technical specifications. The project contributed to scientific knowledge and engineering methods in (1) user interface design, (2) scheduling optimization and risk estimation, and (2) natural language processing that would benefit the nuclear power plants in minimizing schedule overruns and even unexpected shutdowns. The research team conducted site visits at a test reactor facility and an operating nuclear power plant to gather necessary information and inputs for research and development of a software application to support NPP staff in executing their outages. The final software application consisted of three modules. First, the natural language processing module supports interactive processing of technical documentation to build a database for outage staff to query non-permissible actions on system components. This module can alleviate outage staff from reviewing extensive documentation and minimize violation of technical specifications, especially in time-sensitive situations. Second, the schedule optimization module schedules outage activities and compute risk indices that outperform existing software and current practice. This module can reduce completion time of an outage that typically have too many activities for human to optimize based on current practice that does not apply the latest operations research. Finally, the visualization module presents progress and risk information of the overall outage and individual activities, as well as enabling access to the natural language processing and schedule optimization modules. This module can provide outage staff with situation awareness that are necessary to make risk-informed decisions in response to unexpected events during the execution of an outage.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS1997

Rocket Engine Numerical Simulator (RENS)

Work is being done at three universities to help today's NASA engineers use the knowledge and experience of their Apolloera predecessors in designing liquid rocket engines. Ground-breaking work is being done in important subject areas to create a prototype of the most important functions for the Rocket Engine Numerical Simulator (RENS). The goal of RENS is to develop an interactive, realtime application that engineers can utilize for comprehensive preliminary propulsion system design functions. RENS will employ computer science and artificial intelligence research in knowledge acquisition, computer code parallelization and objectification, expert system architecture design, and object-oriented programming. In 1995, a 3year grant from the NASA Lewis Research Center was awarded to Dr. Douglas Moreman and Dr. John Dyer of Southern University at Baton Rouge, Louisiana, to begin acquiring knowledge in liquid rocket propulsion systems. Resources of the University of West Florida in Pensacola were enlisted to begin the process of enlisting knowledge from senior NASA engineers who are recognized experts in liquid rocket engine propulsion systems. Dr. John Coffey of the University of West Florida is utilizing his expertise in interviewing and concept mapping techniques to encode, classify, and integrate information obtained through personal interviews. The expertise extracted from the NASA engineers has been put into concept maps with supporting textual, audio, graphic, and video material. A fundamental concept map was delivered by the end of the first year of work and the development of maps containing increasing amounts of information is continuing. Find out more information about this work at the Southern University/University of West Florida. In 1996, the Southern University/University of West Florida team conducted a 4day group interview with a panel of five experts to discuss failures of the RL10 rocket engine in conjunction with the Centaur launch vehicle. The discussion was recorded on video and audio tape. Transcriptions of the entire proceedings and an abbreviated video presentation of the discussion highlights are under development. Also in 1996, two additional 3year grants were awarded to conduct parallel efforts that would complement the work being done by Southern University and the University of West Florida. Dr. Prem Bhalla of Jackson State University in Jackson, Mississippi, is developing the architectural framework for RENS. By employing the Rose Rational language and Booch Object Oriented Programming (OOP) technology, Dr. Bhalla is developing the basic structure of RENS by identifying and encoding propulsion system components, their individual characteristics, and cross-functionality and dependencies. Dr. Ruknet Cezzar of Hampton University, located in Hampton, Virginia, began working on the parallelization and objectification of rocket engine analysis and design codes. Dr. Cezzar will use the Turbo C++ OOP language to translate important liquid rocket engine computer codes from FORTRAN and permit their inclusion into the RENS framework being developed at Jackson State University. The Southern University/University of West Florida grant was extended by 1 year to coordinate the conclusion of all three efforts in 1999.

Davidian, Kenneth O.↗
NASA NTRS1992

The KASE approach to domain-specific software systems

Designing software systems, like all design activities, is a knowledge-intensive task. Several studies have found that the predominant cause of failures among system designers is lack of knowledge: knowledge about the application domain, knowledge about design schemes, knowledge about design processes, etc. The goal of domain-specific software design systems is to explicitly represent knowledge relevant to a class of applications and use it to partially or completely automate various aspects of the designing systems within that domain. The hope is that this would reduce the intellectual burden on the human designers and lead to more efficient software development. In this paper, we present a domain-specific system built on top of KASE, a knowledge-assisted software engineering environment being developed at the Stanford Knowledge Systems Laboratory. We introduce the main ideas underlying the construction of domain specific systems within KASE, illustrate the application of the idea in the synthesis of a system for tracking aircraft from radar signals, and discuss some of the issues in constructing domain-specific systems.

Bhansali, Sanjay↗