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 649 records · Page 36

Portable inference engine: An extended CLIPS for real-time production systems

The present C-Language Integrated Production System (CLIPS) architecture has not been optimized to deal with the constraints of real-time production systems. Matching in CLIPS is based on the Rete Net algorithm, whose assumption of working memory stability might fail to be satisfied in a system subject to real-time dataflow. Further, the CLIPS forward-chaining control mechanism with a predefined conflict resultion strategy may not effectively focus the system's attention on situation-dependent current priorties, or appropriately address different kinds of knowledge which might appear in a given application. Portable Inference Engine (PIE) is a production system architecture based on CLIPS which attempts to create a more general tool while addressing the problems of real-time expert systems. Features of the PIE design include a modular knowledge base, a modified Rete Net algorithm, a bi-directional control strategy, and multiple user-defined conflict resolution strategies. Problems associated with real-time applications are analyzed and an explanation is given for how the PIE architecture addresses these problems.

Le, Thach↗

Computer systems and software engineering

The High Technologies Laboratory (HTL) was established in the fall of 1982 at the University of Houston Clear Lake. Research conducted at the High Tech Lab is focused upon computer systems and software engineering. There is a strong emphasis on the interrelationship of these areas of technology and the United States' space program. In Jan. of 1987, NASA Headquarters announced the formation of its first research center dedicated to software engineering. Operated by the High Tech Lab, the Software Engineering Research Center (SERC) was formed at the University of Houston Clear Lake. The High Tech Lab/Software Engineering Research Center promotes cooperative research among government, industry, and academia to advance the edge-of-knowledge and the state-of-the-practice in key topics of computer systems and software engineering which are critical to NASA. The center also recommends appropriate actions, guidelines, standards, and policies to NASA in matters pertinent to the center's research. Results of the research conducted at the High Tech Lab/Software Engineering Research Center have given direction to many decisions made by NASA concerning the Space Station Program.

Mckay, Charles W.↗

Second Generation RLV Space Vehicle Concept

NASA has a long history of conducting development programs and projects in a consistent fashion. Systems Engineering within those programs and projects has also followed a given method outlined by such documents as the NASA Systems Engineering Handbook. The relatively new NASA Space Launch Initiative (SLI) is taking a new approach to developing a space vehicle, with innovative management methods as well as new Systems Engineering processes. With the program less than a year into its life cycle, the efficacy of these new processes has yet to be proven or disproven. At $776M for phase 1, SLI represents a major portion of the NASA focus; however, the new processes being incorporated are not reflected in the training provided by NASA to its engineers. The NASA Academy of Program and Project Leadership (APPL) offers core classes in program and project management and systems engineering to NASA employees with the purpose of creating a "knowledge community where ideas, skills, and experiences are exchanged to increase each other's capacity for strong leadership". The SLI program is, in one sense, a combination of a conceptual design program and a technology program. The program as a whole doesn't map into the generic systems engineering project cycle as currently, and for some time, taught. For example, the NASA APPL Systems Engineering training course teaches that the "first step in developing an architecture is to define the external boundaries of the system", which will require definition of the interfaces with other systems and the next step will be to "define all the components that make up the next lower level of the system hierarchy" where fundamental requirements are allocated to each component. Whereas, the SLI technology risk reduction approach develops architecture subsystem technologies prior to developing architectures. The higher level architecture requirements are not allowed to fully develop and undergo decomposition and allocation down to the subsystems before the subsystems must develop allocated requirements based on the highest level of requirements. In the vernacular of the project cycles prior to the mid 1990's, the architecture definition portion of the program appears to be at a generic Phase A stage, while the subsystems are operating at Phase B. Even the management structure of the SLI program is innovative in its approach to Systems Engineering and is not reflected in the APPL training modules. The SLI program has established a Systems Engineering office as an office separate from the architecture development or the subsystem technology development, while that office does have representatives within these other offices. The distributed resources of the Systems Engineering Office are co-located with the respective Project Offices. This template is intended to provide systems engineering as an integrated function at the Program Level. the program management of SLI and the MAT agree that "program/project managers and the systems engineering team must work closely together towards the single objective of delivering quality products that meet the customer needs". This paper will explore the differences between the methods being taught by NASA, which represent decades of ideas, and those currently in practice in SLI. Time will tell if the innovation employed by SLI will prove to be the model of the future. For now, it is suggested that the training of the present exercise the flexibility of recognizing the new processes employed by a major new NASA program.

Bailey, Michelle↗

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗

[NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 4:] Technical communications in aerospace: An analysis of the practices reported by US and European aerospace engineers and scientists

Two pilot studies were conducted that investigated the technical communications practices of U.S. and European aerospace engineers and scientists. Both studies had the same five objectives: (1) solicit opinions regarding the importance of technical communications; (2) determine the use and production of technical communications; (3) seek views about the appropriate content of an undergraduate course in technical communications; (4) determine use of libraries, information centers, and online database; (5) determine use and importance of computer and information technology to them. A self-administered questionnaire was mailed to randomly selected aerospace engineers and scientists, with a slightly modified version sent to European colleagues. Their responses to selected questions are presented in this paper.

Pinelli, Thomas E.↗

Interdisciplinary Interactions During R&D and Early Design of Large Engineered Systems

Designing Large-Scale Complex Engineered Systems (LaCES) such as aircraft and submarines requires the input of thousands of engineers and scientists whose work is proximate in neither time nor space. Comprehensive knowledge of the system is dispersed among specialists whose expertise is in typically one system component or discipline. This study examined the interactive work practices among such specialists seeking to improve engineering practice through a rigorous and theoretical understanding of current practice. This research explored current interdisciplinary practices and perspectives during R&D and early LaCES design and identified why these practices and perspectives prevail and persist. The research design consisted of a three-fold, integrative approach that combined an open-ended survey, semi-structured interviews, and ethnography. Significant empirical data from experienced engineers and scientists in a large engineering organization were obtained and integrated with theories from organization science and engineering. Qualitative analysis was used to obtain a holistic, contextualized understanding. The over-arching finding is that issues related to cognition, organization, and social interrelations mostly dominate interactions across disciplines. Engineering issues, such as the integration of hardware or physics-based models, are not as significant. For example, organization culture is an important underlying factor that guided researchers more toward individual sovereignty over cross-disciplinarity. The organization structure and the engineered system architecture also serve as constraints to the engineering work. Many differences in work practices were observed, including frequency and depth of interactions, definition or co-construction of requirements, clarity or creation of the system architecture, work group proximity, and cognitive challenges. Practitioners are often unaware of these differences resulting in confusion and incorrect assumptions regarding work expectations. Cognitively, the enactment and coconstruction of knowledge are the fundamental tasks of the interdisciplinary interactions. Distributed and collective cognition represent most of the efforts. Argument, ignorance, learning, and creativity are interrelated aspects of the interactions that cause discomfort but yield benefits such as problem mitigation, broader understanding, and improved system design and performance. The quality and quantity of social interrelations are central to all work across disciplines with reciprocity, respectful engagement, and heedful interrelations being significant to the effectiveness of the engineering and scientific work.

McGowan, Anna-Maria Rivas↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 9: Summary report to phase 3 faculty and student respondents including frequency distributions

This project is designed to explore the diffusion of scientific and technical information (STI) throughout the aerospace industry. The increased international competition and cooperation in the industry promises to significantly affect the STI standards of U.S. aerospace engineers and scientists. Therefore, it is important to understand the aerospace knowledge diffusion process itself and its implications at the individual, organizational, national, and international levels. Examined here is the role of STI in the academic aerospace community.

Pinelli, Thomas E.↗

NASA's Systems Engineering Approaches for Addressing Public Health Surveillance Requirements

NASA's systems engineering has its heritage in space mission analysis and design, including the end-to-end approach to managing every facet of the extreme engineering required for successful space missions. NASA sensor technology, understanding of remote sensing, and knowledge of Earth system science, can be powerful new tools for improved disease surveillance and environmental public health tracking. NASA's systems engineering framework facilitates the match between facilitates the match between partner needs and decision support requirements in the areas of 1) Science/Data; 2) Technology; 3) Integration. Partnerships between NASA and other Federal agencies are diagrammed in this viewgraph presentation. NASA's role in these partnerships is to provide systemic and sustainable solutions that contribute to the measurable enhancement of a partner agency's disease surveillance efforts.

Vann, Timi↗

Overview of High-Fidelity Modeling Activities in the Numerical Propulsion System Simulations (NPSS) Project

A high-fidelity simulation of a commercial turbofan engine has been created as part of the Numerical Propulsion System Simulation Project. The high-fidelity computer simulation utilizes computer models that were developed at NASA Glenn Research Center in cooperation with turbofan engine manufacturers. The average-passage (APNASA) Navier-Stokes based viscous flow computer code is used to simulate the 3D flow in the compressors and turbines of the advanced commercial turbofan engine. The 3D National Combustion Code (NCC) is used to simulate the flow and chemistry in the advanced aircraft combustor. The APNASA turbomachinery code and the NCC combustor code exchange boundary conditions at the interface planes at the combustor inlet and exit. This computer simulation technique can evaluate engine performance at steady operating conditions. The 3D flow models provide detailed knowledge of the airflow within the fan and compressor, the high and low pressure turbines, and the flow and chemistry within the combustor. The models simulate the performance of the engine at operating conditions that include sea level takeoff and the altitude cruise condition.

Veres, Joseph P.↗

Students Solving Problems for ISS and Beyond: Inspiring the Next-Generation

Students Solving Problems for ISS and Beyond: Inspiring the Next-Generation Session Title: Students Solving Problems for ISS and Beyond: Inspiring the Next-Generation Session Description: NASA High school students United with NASA to Create Hardware (HUNCH) mission is to empower and inspire students through a Project-Based Learning program where 7-12 grade students learn 21st century skills and can launch their careers through participation in the design and fabrication of real-world valued products for NASA. With six different tracks consisting of Design & Prototype, Culinary Challenge, Softgoods, Precision Machining, Software, and Video Challenge, students are given the opportunity to create solutions for the International Space Station (ISS), the Moon, and beyond. Many projects are requested by the Crew to help ease living conditions, giving students the opportunity to make an impact on the lives of Astronauts. Other projects come directly from NASA and its partners. Join our session to learn how NASA is working with teachers across the country to mentor the next generation of scientists and engineers to solve some of NASA’s greatest challenges. Learning Outcomes: 1. Describe the NASA HUNCH Program, including the program objectives, goals, and strategic partnerships for middle school and high school outreach and advocacy efforts. 2. Identify the innovative strategies NASA is using to work with middle and high school students to solve real-world problems 3. Use the knowledge gained to inspire the next generation of scientists and engineers Session Track: Advocacy & Outreach Specialized Focus Area: Women in Government and Military Learning Level: Foundational Session Format: Listen & Learn Speaker Qualifications: 1. Deboshri Sadhukhan • Current Job Title: Deputy Project Manager • Topic Experience (years of experience related to proposed topic): 1-5 years • Biography: Deboshri Sadhukhan is an engineer for NASA Glenn Research Center (GRC). She has worked on numerous projects — from International Space Station (ISS) fluid technologies, to Orion European Service Module propulsion, to planetary science missions and other game-changing technologies. Her roles have ranged from Project Manager to System Safety Lead. She currently serves as a GRC Regional Mentor for the High school students United with NASA to Create Hardware (HUNCH) program. She also serves as Deputy Project Manager for an ISS payload and Safety & Mission Assurance Lead for a Radioisotope Power Systems project. In these roles, she oversees each phase of a project from beginning to end and provides leadership to increase the reliability, maintainability and system safety of hardware and personnel throughout the system life cycle. She holds a Bachelor of Science in Electrical Engineering from The University of Akron. 2. Nancy Hall • Current Job Title: Project Manager • Topic Experience: 20+ years • Biography: Nancy Rabel Hall earned a B.S. degree in Space Sciences from Florida Institute of Technology and a M.S. degree in Mechanical Engineering from the University of Toledo. She has been at NASA Glenn for over 30 years. She has led several International Space Station experiments that studied how the behavior of fluids and fluid systems behave differently in microgravity as compared to here on Earth. She is also the High school students United with NASA to Create Hardware (HUNCH) project manager, a program that allows students to design and fabricate hardware and softgoods for NASA as well as participate in a culinary and video challenge. She enjoys talking to the public and students about the work being done at NASA as well as showing students how math and science can be fun. She is an amateur radio operator, enjoys playing golf, and reading science fiction and fantasy books.

HUNCH↗

STRUTEX: A prototype knowledge-based system for initially configuring a structure to support point loads in two dimensions

Only recently have engineers begun making use of Artificial Intelligence (AI) tools in the area of conceptual design. To continue filling this void in the design process, a prototype knowledge-based system, called STRUTEX has been developed to initially configure a structure to support point loads in two dimensions. This prototype was developed for testing the application of AI tools to conceptual design as opposed to being a testbed for new methods for improving structural analysis and optimization. This system combines numerical and symbolic processing by the computer with interactive problem solving aided by the vision of the user. How the system is constructed to interact with the user is described. Of special interest is the information flow between the knowledge base and the data base under control of the algorithmic main program. Examples of computed and refined structures are presented during the explanation of the system.

Robers, James L.↗

Lessons Learned for Improving Spacecraft Ground Operations

NASA policy requires each Program or Project to develop a plan for how they will address Lessons Learned. Projects have the flexibility to determine how best to promote and implement lessons learned. A large project might budget for a lessons learned position to coordinate elicitation, documentation and archival of the project lessons. The lessons learned process crosses all NASA Centers and includes the contactor community. o The Office of The Chief Engineer at NASA Headquarters in Washington D.C., is the overall process owner, and field locations manage the local implementation. One tool used to transfer knowledge between program and projects is the Lessons Learned Information System (LLIS). Most lessons come from NASA in partnership with support contractors. A search for lessons that might impact a new design is often performed by a contractor team member. Knowledge is not found with only one person, one project team, or one organization. Sometimes, another project team, or person, knows something that can help your project or your task. Knowledge sharing is an everyday activity at the Kennedy Space Center through storytelling, Kennedy Engineering Academy presentations and through searching the Lessons Learned Information system. o Project teams search the lessons repository to ensure the best possible results are delivered. o The ideas from the past are not always directly applicable but usually spark new ideas and innovations. Teams have a great responsibility to collect and disseminate these lessons so that they are shared with future generations of space systems designers. o Leaders should set a goal for themselves to host a set numbers of lesson learned events each year and do more to promote multiple methods of lessons learned activities. o High performing employees are expected to share their lessons, however formal knowledge sharing presentation are not the norm for many employees.

Bell, Michael↗

Resource Management and Contingencies in Aerospace Concurrent Engineering

significant concern in designing complex systems implementing new technologies is that while knowledge about the system is acquired incrementally, substantial financial commitments, even make-or-break decisions, must be made upfront, essentially in the unknown. One practice that helps in dealing with this dichotomy is the smart embedding of contingencies and margins in the design to serve as buffers against surprises. This issue presents itself in full force in the aerospace industry, where unprecedented systems are formulated and committed to as a matter of routine. As more and more aerospace mission concepts are generated by concurrent design laboratories, it is imperative that such laboratories apply well thought-out contingency and margin structures to their designs. The first part of this publication provides an overview of resource management techniques and standards used in the aerospace industry. That is followed by a thought provoking treatise on margin policies. The expose presents the actual flight telemetry data recorded by the thermal discipline during several recent NASA Goddard Space Flight Center missions. The margins actually achieved in flight are compared against pre-flight predictions, and the appropriateness and the ramifications of having designed with rigid margins to bounding stacked worst case conditions are assessed. The second half of the paper examines the particular issues associated with the application of contingencies and margins in the concurrent engineering environment. In closure, a discipline-by-discipline disclosure of the contingency and margin policies in use at the Integrated Design Center at NASA s Goddard Space Flight Center is made.

Karpati, Gabe↗

There is No Free Lunch: Tradeoffs in the Utility of Learned Knowledge

With the recent introduction of learning in integrated systems, there is a need to measure the utility of learned knowledge for these more complex systems. A difficulty arrises when there are multiple, possibly conflicting, utility metrics to be measured. In this paper, we present schemes which trade off conflicting utility metrics in order to achieve some global performance objectives. In particular, we present a case study of a multi-strategy machine learning system, mutual theory refinement, which refines world models for an integrated reactive system, the Entropy Reduction Engine. We provide experimental results on the utility of learned knowledge in two conflicting metrics - improved accuracy and degraded efficiency. We then demonstrate two ways to trade off these metrics. In each, some learned knowledge is either approximated or dynamically 'forgotten' so as to improve efficiency while degrading accuracy only slightly.

Kedar, Smadar T.↗

Probabilistic failure assessment with application to solid rocket motors

A quantitative methodology is being developed for assessment of risk of failure of solid rocket motors. This probabilistic methodology employs best available engineering models and available information in a stochastic framework. The framework accounts for incomplete knowledge of governing parameters, intrinsic variability, and failure model specification error. Earlier case studies have been conducted on several failure modes of the Space Shuttle Main Engine. Work in progress on application of this probabilistic approach to large solid rocket boosters such as the Advanced Solid Rocket Motor for the Space Shuttle is described. Failure due to debonding has been selected as the first case study for large solid rocket motors (SRMs) since it accounts for a significant number of historical SRM failures. Impact of incomplete knowledge of governing parameters and failure model specification errors is expected to be important.

Jan, Darrell L.↗

U.S. Spacesuit Knowledge Capture Status and Initiatives in Fiscal Year 2014

Since its 2008 inception, the NASA U.S. Spacesuit Knowledge Capture (KC) program has shared historical spacesuit information with engineers and other technical team members to expand their understanding of the spacesuit's evolution, known capability and limitations, and future desires and needs for its use. As part of the U.S. Spacesuit KC program, subject-matter experts have delivered presentations, held workshops, and participated in interviews to share valuable spacesuit lessons learned to ensure this vital information will survive for existing and future generations to use. These events have included spacesuit knowledge from the inception of NASA's first spacesuit to current spacesuit design. To ensure that this information is shared with the entire NASA community and other interested or invested entities, these KC events were digitally recorded and transcribed to be uploaded onto several applicable NASA Web sites. This paper discusses the various Web sites that the KC events are uploaded to and possible future sites that will channel this information.

Chullen, Cinda↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 17: The relationship between seven variables and the use of US government technical reports by US aerospace engineers and scientists

A study was undertaken to investigate the relationship between the use of U.S. government technical reports by U.S. aerospace engineers and scientists and seven selected sociometric variables. Data were collected by means of a self-administered mail survey which was distributed to a randomly drawn sample of American Institute of Aeronautics and Astronautics (AIAA) members. Two research questions concerning the use of conference meeting papers, journal articles, in-house technical reports, and U.S. government technical reports were investigated. Relevance, technical quality, and accessibility were found to be more important determinants of the overall extent to which U.S. government technical reports and three other information products were used by U.S. aerospace engineers and scientists.

Pinelli, Thomas E.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 37: The impact of political control on technical communications: A comparative study of Russian and US aerospace engineers and scientists

Until the recent dissolution of the Soviet Union, the Communist Party exerted a strict control of access to and dissemination of scientific and technical information (STI). This article presents models of the Soviet-style information society and the Western-style information society and discusses the effects of centralized governmental control of information on Russian technical communication practices. The effects of political control on technical communication are then used to interpret the results of a survey of Russian and U.S. aerospace engineers and scientists concerning the time devoted to technical communication, their collaborative writing practices and their attitudes toward collaboration, the kinds of technical documents they produce and use, and their use of computer technology, and their use of and the importance to them of libraries and technical information centers. The data are discussed in terms of tentative conclusions drawn from the literature. Finally, we conclude with four questions concerning government policy, collaboration, and the flow of STI between Russian and U.S. aerospace engineers and scientists.

Barclay, Rebecca O.↗