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 451 records · Page 25

Orbital Debris Ontology, Terminology, and Knowledge Modeling

The looming threat orbital debris poses to assets in orbit demands solutions. As the orbital population grows, so does this hazard, but so does the sea of data. The problem is also an opportunity for interdisciplinary innovation and cooperation. This paper focuses on the data and information management aspect of developing solutions for a sustainable and safe orbital space environment. The corresponding author’s in-progress work to develop an orbital debris domain ontology is summarized in order to discuss knowledge modeling for this domain. Methodological approaches of this effort can also contribute to standards efforts and address terminological and policy questions. Leveraging the growing volumes of orbital debris and space situational awareness (SSA) data will create a more complete picture of the orbital space environment. Part of the solution will be: consistent and correct data interpretation, sharing orbital debris and SSA data in one form or another, terminology development & harmonization, and knowledge or domain modeling. To facilitate this, [Rovetto, 2015/16] discussed ontology development for the orbital debris domain. This paper lists concepts from that paper, and subsequently developed concepts [2-9]. Ontology engineering is an interdisciplinary field related to knowledge representation and reasoning in artificial intelligence, semantic technologies and the so-called semantic web. An ontology is effectively a computable and semantically rich terminology that presents a knowledge or domain model for a topic area. Expressions of knowledge or assertions are stored using formally defined term. This knowledge base is reasoned over to yield answers to queries, among other things. Ontologies have been developed in knowledge-based projects across various disciplines, and used for such things as search engines, chatbots, enterprise knowledge graphs, etc. Ontologies support: interoperability, automated reasoning, data sharing and integration, data search and retrieval, and communicating the meaning of data. The Orbital Debris Ontology (ODO), and related ontologies [Rovetto & Kelso 2016] [Rovetto 2016, 2017], were proposed to help achieve this. ODO, for instance, is intended as a domain ontology that can be used across federated databases, offering an explicitly specified set of concepts describing the orbital debris domain. Its meaning-rich taxonomy will provide a sharable semantics for orbital debris data to, in part, consistently communicate the meaning of data to both humans and machines, and tag data elements in space object catalogs to help afford inference tasks, decision support, knowledge discovery, and information integration. ODO and the SSA ontology (SSAO) is part of the overall Orbital Space Domain Ontology concept, which is conceived as a broader domain reference ontology. It aims to provide a knowledge representation structure of the orbital space environment, a common semantic model, and develop a sharable terminology. Collectively this will provide common meaning for datasets, a high-level taxonomy or classification for orbital space objects, and thus means to characterize space objects. Ongoing efforts have included using visualizations, R, JSON-LD, and contemporary semantic technologies. Potential applications and interdisciplinary partnerships include web-based platforms, web apps, visualizations, and academia projects. Community input and participation may yield a more widely understood domain model as well as facilitate terminological standards. For example, the proposed conceptual, terminological and ontological analysis may contribute to such efforts as the Space Debris Mitigation Requirements in the International Standards Organization by developing more precise, consistent and coherent terms and definitions. Projects that seek to develop in-house ontologies can use ODO and related ontologies as domain reference ontologies. This paper was developed independent of author affiliations. Readers are encouraged to contact corresponding author(1) with general interest and potential opportunities to support or realize the described project.

Robert J. Rovetto↗

An international perspective on nuclear criticality safety

Full text of publication follows: As one of the standing technical committees within the OECD Nuclear Energy Agency (NEA) the Nuclear Science Committee overseas a programme of work aimed at delivering the following key objectives: - the advancement of scientific knowledge needed to enhance the performance and safety of current nuclear systems; - building a solid scientific and technical basis for the development of future-generation nuclear systems; - the preservation of essential knowledge in the field of nuclear science. Criticality safety is an important aspect of all three of these objectives, and the NEA Nuclear Science Working Party on Nuclear Criticality (WPNCS) coordinates many international activities under its programme of work. An overview of the WPNCS is given in the following presentation, and many of the papers presented during the ICNC 2015 technical sessions will be giving details of the outputs from the various projects and activities which make up the WPNCS programme of work. This presentation focuses on issues associated with knowledge management, particularly on how an international framework for nuclear science and criticality safety activities can provide a very effective means of transferring knowledge across technical disciplines, and between different generations of engineers and scientists. To ensure that it is the essential knowledge that is preserved and transferred, we need to understand current trends and future requirements in criticality safety. In this respect, an international framework provides both the broad scope as well as the long-term perspective needed to make an informed judgement on which information/knowledge will be of most relevance to future practitioners of criticality safety. (author)

42 ENGINEERING↗

Development of the Spacecraft Materials Selector Expert System

A specific knowledge base to evaluate the on-orbit performance of selected materials on spacecraft is being developed under contract to the NASA SEE program. An artificial intelligence software package, the Boeing Expert System Tool (BEST), contains an inference engine used to operate knowledge bases constructed to selectively recall and distribute information about materials performance in space applications. This same system is used to make estimates of the environmental exposures expected for a given space flight. The performance capabilities of the Spacecraft Materials Selector (SMS) knowledge base are described in this paper. A case history for a planned flight experiment on ISS is shown as an example of the use of the SMS, and capabilities and limitations of the knowledge base are discussed.

Pippin, H. G.↗

Rocket University at KSC

"Rocket University" is an exciting new initiative at Kennedy Space Center led by NASA's Engineering and Technology Directorate. This hands‐on experience has been established to develop, refine & maintain targeted flight engineering skills to enable the Agency and KSC strategic goals. Through "RocketU", KSC is developing a nimble, rapid flight engineering life cycle systems knowledge base. Ongoing activities in RocketU develop and test new technologies and potential customer systems through small scale vehicles, build and maintain flight experience through balloon and small‐scale rocket missions, and enable a revolving fresh perspective of engineers with hands on expertise back into the large scale NASA programs, providing a more experienced multi‐disciplined set of systems engineers. This overview will define the Program, highlight aspects of the training curriculum, and identify recent accomplishments and activities.

Training↗

NASA/DoD Aerospace Knowledge Diffusion Research Project. XXXIII - Technical communications practices and the use of information technologies as reported by Dutch and U.S. aerospace engineers

As part of Phase 4 of the NASA/DOD Aerospace Knowledge Diffusion Research Project, two studies were conducted that investigated the technical communications practices of Dutch and U.S. aerospace engineers and scientists. A self-administered questionnaire was distributed to aerospace engineers and scientists at the National Aerospace Laboratory (The Netherlands), and NASA Ames Research Center (U.S.), and the NASA Langley Research Center (U.S.). This paper presents responses of the Dutch and U.S. participants to selected questions about four of the seven project objectives: determining the importance of technical communications to aerospace engineering professionals, investigating the production of technical communications, examining the use and importance of computer and information technology, and exploring the use of electronic networks.

Barclay, Rebecca O.↗

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

Modular design: Implementing proven engineering principles in biotechnology

Modular design resides at the foundation of contemporary engineering, enabling rapid, efficient, and reproducible construction and maintenance of complex systems across applications. Remarkably, modularity has recently been discovered as a governing principle in natural biological systems from genes to proteins to complex networks within a cell and organism communities. The convergent knowledge of natural and engineered modular systems provides a key to drive modern biotechnology to address emergent challenges associated with health, food, energy, and the environment. Here, we first present the theory and application of modular design in traditional engineering fields. We further discuss the significance and impact of modular architectures on systems biology and biotechnology. Next, we focus on the very recent theoretical and experimental advances in modular cell engineering that seeks to enable rapid and systematic development of microbial catalysts capable of efficiently synthesizing a large space of useful chemicals. We conclude with an outlook towards theoretical and practical opportunities for a more systematic and effective application of modular engineering in biotechnology.

59 BASIC BIOLOGICAL SCIENCES↗

Executive control systems in the engineering design environment

An executive control system (ECS) is a software structure for unifying various applications codes into a comprehensive system. It provides a library of applications, a uniform access method through a cental user interface, and a data management facility. A survey of twenty-four executive control systems designed to unify various CAD/CAE applications for use in diverse engineering design environments within government and industry was conducted. The goals of this research were to establish system requirements to survey state-of-the-art architectural design approaches, and to provide an overview of the historical evolution of these systems. Foundations for design are presented and include environmental settings, system requirements, major architectural components, and a system classification scheme based on knowledge of the supported engineering domain(s). An overview of the design approaches used in developing the major architectural components of an ECS is presented with examples taken from the surveyed systems. Attention is drawn to four major areas of ECS development: interdisciplinary usage; standardization; knowledge utilization; and computer science technology transfer.

Hurst, P. W.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 16: A comparison of the technical communications practices of Russian and US aerospace engineers and scientists

As part of Phase 4 of the NASA/DOD Aerospace Knowledge Diffusion Project, two studies were conducted that investigated the technical communications practices of Russian and U.S. aerospace engineers and scientists. Both studies have the same five objectives: first, to solicit the opinions of aerospace engineers and scientists regarding the importance of technical communications to their profession; second, to determine the use and production of technical communications by aerospace engineers and scientists; third, to seek their views about the appropriate content of an undergraduate course in technical communications; fourth, to determine aerospace engineers' and scientists' use of libraries, technical information centers, and on-line data bases; and fifth, to determine the use and importance of computer and information technology to them. A self-administered questionnaire was distributed to aerospace engineers and scientists at the Central Aero-Hydrodynamic Institute (TsAGI), NASA ARC, and NASA LaRC. The completion rates for the Russian and U.S. surveys were 64 and 61 percent, respectively. The responses of the Russian and U.S. participants, to selected questions, are presented in this report.

Thomas E Pinelli↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 17: A comparison of the technical communication practices of Dutch and US aerospace engineers and scientists

As part of Phase 4 of the NASA/DoD Aerospace Knowledge Diffusion Research Project, two studies were conducted that investigated the technical communications practices of Dutch and U.S. aerospace engineers and scientists. Both studies have the same seven objectives: first, to solicit the opinions of aerospace engineers and scientists regarding the importance of technical communications to their profession; second, to determine the use and production of technical communications by aerospace engineers and scientists; third, to seek their views about the appropriate content of an undergraduate course in technical communications; fourth, to determine aerospace engineers' and scientists' use of libraries, technical information centers, and on-line data bases; fifth, to determine the use and importance of computer and information technology to them; sixth, to determine their use of electronic networks; and seventh, to determine their use of foreign and domestically produced technical reports. A self-administered questionnaire was distributed to aerospace engineers and scientists at the National Aerospace Laboratory (NLR), and NASA Ames Research Center, and the NASA Langley Research Center. The completion rates for the Dutch and U.S. surveys were 55 and 61 percent, respectively. Responses of the Dutch and U.S. participants to selected questions are presented.

Barclay, Rebecca O.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Report 29: A comparison of the technical communications practices of Japanese and US aerospace engineers and scientists

As part of Phase 4 of the NASA/DoD Aerospace Knowledge Diffusion Research Project, two studies were conducted that investigated the technical communications practices of Japanese and U.S. aerospace engineers and scientists. Both studies have the same seven objectives: first, to solicit the opinions of aerospace engineers and scientists regarding the importance of technical communications to their profession; second, to determine the use and production of technical communications by aerospace engineers and scientists; third; to seek their views about the appropriate content of an undergraduate course in technical communications; fourth, to determine aerospace engineers' and scientists' use of libraries, technical information centers, and on-line data bases; fifth, to determine the use and importance of computer and information technology to them; sixth, to determine their use of electronic networks; and seventh, to determine their use of foreign and domestically produced technical reports. A self-administered questionnaire was distributed to aerospace engineers and scientists in Japan and at the NASA Ames Research Center and the NASA Langley Research Center. The completion rates for the Japanese and U.S. surveys were 85 and 61 percent, respectively. Responses of the Japanese and U.S. participants to selected questions are presented in this report.

Pinelli, Thomas E.↗

Utilizing the Shift Technical Engineer Pipeline to Develop the Next Generation of Engineers - 17354

As the liquid waste contractor for the U.S. Department of Energy's (DOE) Savannah River Site (SRS), Savannah River Remediation (SRR) is responsible for safely treating and dispositioning approximately 35 million gallons of liquid waste stored at SRS. To achieve this mission, SRR manages and operates several complex nuclear facilities. These nuclear facilities include the H and F Tank Farms, the Defense Waste Processing Facility (DWPF), and the Saltstone Processing and Disposal Facility. To support the operations of these complex nuclear facilities, a Shift Technical Engineer (STE) is stationed for every shift. The STE is the sole Engineering Organization representative on-shift and serves as a direct technical resource for operations, including safety basis interpretation, process monitoring and prompt troubleshooting support. The training and qualification for an STE is more intensive than for typical technical staff personnel at SRR, involving additional classes, under-instruction watches, demonstration of practical factors, and culminating in an intense oral board examination. Like many other contractors in the DOE complex, SRR faces the challenge of preparing a significant number of new generation engineers to take the place of an aging workforce. Beyond the traditional training to establish minimum technical qualifications, SRR has established a number of initiatives aimed at accelerating the process of preparing early career engineers to replace experienced senior engineers. These initiatives include an internal rotational program, technical exchange activities with companies at other DOE sites, and an STE pipeline. The STE role provides a unique mechanism for select, early career engineers to gain in-depth knowledge and significant responsibility normally not achieved until much later in their careers. Once qualification is complete, the engineers perform the STE duties, providing technical support for nuclear facility operations. In addition, creating an STE pipeline, where promising young engineers are continually being qualified to replace the on-shift STEs, provides the company with a source of experienced engineers with in-depth technical knowledge as well as valuable experience interfacing with operations and other facility support groups. This paper will discuss the STE position, the qualification process, and how SRR is using the STE qualification pipeline to benefit both the company and the individual engineer. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Stirling laboratory research engine survey report

As one step in expanding the knowledge relative to and accelerating the development of Stirling engines, NASA, through the Jet Propulsion Laboratory (JPL), is sponsoring a program which will lead to a versatile Stirling Laboratory Research Engine (SLRE). An objective of this program is to lay the groundwork for a commercial version of this engine. It is important to consider, at an early stage in the engine's development, the needs of the potential users so that the SLRE can support the requirements of educators and researchers in academic, industrial, and government laboratories. For this reason, a survey was performed, the results of which are described.

Anderson, J. W.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 33: Technical communications practices and the use of information technologies as reported by Dutch and US aerospace engineers

As part of Phase 4 of the NASA/DOD Aerospace Knowledge Diffusion Research Project, two studies were conducted that investigated the technical communications practices of Dutch and U.S. aerospace engineers and scientists. A self-administered questionnaire was distributed to aerospace engineers and scientists at the National Aerospace Laboratory (The Netherlands), and NASA ARC (U.S.), and NASA LaRC (U.S.). This paper presents responses of the Dutch and U.S. participants to selected questions concerning four of the seven project objectives: determining the importance of technical communications to aerospace engineering professionals, investigating the production of technical communications, examining the use and importance of computer and information technology, and exploring the use of electronic networks.

Barclay, Rebecca O.↗

NASA Engineering and Safety Center Technical Bulletins 2007-2023

An NESC Technical Bulletin captures critical knowledge in the form of new engineering information or best practices in a one-page format that have resulted from NESC independent testing, analysis, and assessments. This document contains all NESC Technical Bulletins from 2007 through 2023.

additive manufacturing, battery, braycote, capacit↗

Applying Cyber-Informed Engineering to Power System Operations

This presentation covers the interaction of the discipline of system operations with the growing body of knowledge around Cyber-Informed Engineering (CIE). First is discussion of a number of fundamental concepts for system operators - organizational division of responsibilities, human and machine cooperation, goals, and priorities. The next section covers the reasons why CIE was developed, what it is, and the key design and operational, and organizational principles of CIE. Finally, some thoughts on how CIE can be applied to power system operations are offered, along with some examples of how an organization can approach applying CIE principles in their particular circumstances.

24 POWER TRANSMISSION AND DISTRIBUTION↗

An overview of expert systems

An expert system is defined and its basic structure is discussed. The knowledge base, the inference engine, and uses of expert systems are discussed. Architecture is considered, including choice of solution direction, reasoning in the presence of uncertainty, searching small and large search spaces, handling large search spaces by transforming them and by developing alternative or additional spaces, and dealing with time. Existing expert systems are reviewed. Tools for building such systems, construction, and knowledge acquisition and learning are discussed. Centers of research and funding sources are listed. The state-of-the-art, current problems, required research, and future trends are summarized.

Gevarter, W. B.↗

Heavy Duty Natural Gas Single Cylinder Research Engine Installation, Commissioning, and Baseline Testing

Natural Gas (NG) Internal Combustion Engines (ICE) are a promising alternative to diesel engines for on-road heavy-duty applications to reduce greenhouse gas and harmful pollutant emissions. NG engines have not been widely adopted due to the lower thermal efficiency compared with diesel engine counterparts. To develop the base knowledge required to reach the desired efficiency, a Single Cylinder Engine (SCE) is the most effective platform to acquire reliable and repeatable data. A SCE test cell was developed using a Cummins 15-liter six-cylinder heavy-duty engine block modified to fire one cylinder (2.5-liter displacement). A Woodward Large Engine Control Module (LECM) is integrated to permit implementation of real-time advanced combustion control. Intake and exhaust characteristics, fuel composition, and exhaust gas recirculated substitution rate (EGR) are fully adjustable. A high-speed data acquisition system acquires in-cylinder, intake, and exhaust pressure for combustion analysis. The baseline testing shows reliable and consistent results for engine thermal efficiency, indicated mean effective pressure (IMEP), and coefficient of variance of the IMEP over a wide range of operating conditions while achieving effective control of all engine control and operation variables. This test cell will be used to conduct a research program to develop new and innovative control algorithms and CFD optimized combustion chamber designs, allowing ultra-high efficiency and low emissions for NG ICE heavy-duty on-road applications.

03 NATURAL GAS↗