Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Knowledge bases”

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

AiGERM: A logic programming front end for GERM

AiGerm (Artificially Intelligent Graphical Entity Relation Modeler) is a relational data base query and programming language front end for MCC (Mission Control Center)/STP's (Space Test Program) Germ (Graphical Entity Relational Modeling) system. It is intended as an add-on component of the Germ system to be used for navigating very large networks of information. It can also function as an expert system shell for prototyping knowledge-based systems. AiGerm provides an interface between the programming language and Germ.

Hashim, Safaa H.↗

Meta-tools for software development and knowledge acquisition

The effectiveness of tools that provide support for software development is highly dependent on the match between the tools and their task. Knowledge-acquisition (KA) tools constitute a class of development tools targeted at knowledge-based systems. Generally, KA tools that are custom-tailored for particular application domains are more effective than are general KA tools that cover a large class of domains. The high cost of custom-tailoring KA tools manually has encouraged researchers to develop meta-tools for KA tools. Current research issues in meta-tools for knowledge acquisition are the specification styles, or meta-views, for target KA tools used, and the relationships between the specification entered in the meta-tool and other specifications for the target program under development. We examine different types of meta-views and meta-tools. Our current project is to provide meta-tools that produce KA tools from multiple specification sources--for instance, from a task analysis of the target application.

Eriksson, Henrik↗

Recent Advances in Hydrogen Peroxide Propulsion Test Capability at NASA's Stennis Space Center E-Complex

In recent years, the rocket propulsion test capability at NASA's John C. Stennis Space Center's (SSC) E-Complex has been enhanced to include facilitization for hydrogen peroxide (H2O2) based ground testing. In particular, the E-3 test stand has conducted numerous test projects that have been reported in the open literature. These include combustion devices as simple as small-scale catalyst beds, and larger devices such as ablative thrust chambers and a flight-type engine (AR2-3). Consequently, the NASA SSC test engineering and operations knowledge base and infrastructure have grown considerably in order to conduct safe H2O2 test operations with a variety of test articles at the component and engine level. Currently, the E-Complex has a test requirement for a hydrogen peroxide based stage test. This new development, with its unique set of requirements, has motivated the facilitization for hydrogen peroxide propellant use at the E-2 Cell 2 test position in addition to E-3. Since the E-2 Cell 2 test position was not originally designed as a hydrogen peroxide test stand, a facility modernization-improvement project was planned and implemented in FY 2002-03 to enable this vertical engine test stand to accomodate H2O2. This paper discusses the ongoing enhancement of E-Complex ground test capability, specifically at the E-3 stand (Cell 1 and Cell 2) and E-2 Cell 2 stand, that enable current and future customers considerable test flexibility and operability in conducting their peroxide based rocket R&D efforts.

Jacks, Thomas E.↗

Expanding Hydrogen Peroxide Propulsion Test Capability at NASA's Stennis Space Center E-Complex

In recent years, the rocket propulsion test capability at NASA s John C. Stennis Space Center's (SSC) E-Complex has been enhanced to include facilitization for hydrogen peroxide (H2O2) based ground testing. In particular, the E-3 test stand has conducted numerous test projects that have been reported in the open literature. These include combustion devices as simple at small-scale catalyst beds, and larger devices such as ablative thrust chambers and a flight-type engine (AR2-3). Consequently, the NASA SSC test engineering and operations knowledge base and infrastructure have grown considerably in order to conduct safe H2O2 test operations with a variety of test articles at the component and engine level. Currently, the E-Complex has a test requirement for a hydrogen peroxide based stage test. This new development, with its unique set of requirements, has motivated the facilitization for hydrogen peroxide propellant use at the E-2 Cell 2 test position in addition to E-3. Since the E-2 Cell 2 test position was not originally designed as a hydrogen peroxide test stand, a facility modernization- improvement project was planned and implemented in FY 2002-03 to enable this vertical engine test stand to accommodate H2O2. This paper discusses the ongoing enhancement of E-Complex ground test capability, specifically at the E-3 stand (Cell 1 and Cell 2) and E-2 Cell 2 stand, that enable current and future customers considerable test flexibility and operability in conducting their peroxide based rocket R&D efforts.

Jacks, Thomas E.↗

IDEF5 Ontology Description Capture Method: Concept Paper

The results of research towards an ontology capture method referred to as IDEF5 are presented. Viewed simply as the study of what exists in a domain, ontology is an activity that can be understood to be at work across the full range of human inquiry prompted by the persistent effort to understand the world in which it has found itself - and which it has helped to shape. In the contest of information management, ontology is the task of extracting the structure of a given engineering, manufacturing, business, or logistical domain and storing it in an usable representational medium. A key to effective integration is a system ontology that can be accessed and modified across domains and which captures common features of the overall system relevant to the goals of the disparate domains. If the focus is on information integration, then the strongest motivation for ontology comes from the need to support data sharing and function interoperability. In the correct architecture, an enterprise ontology base would allow th e construction of an integrated environment in which legacy systems appear to be open architecture integrated resources. If the focus is on system/software development, then support for the rapid acquisition of reliable systems is perhaps the strongest motivation for ontology. Finally, ontological analysis was demonstrated to be an effective first step in the construction of robust knowledge based systems.

Menzel, Christopher P.↗

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.↗

SURE (Science User Resource Expert): A science planning and scheduling assistant for a resource based environment

SURE (Science User Resource Expert) is one of three components that compose the SURPASS (Science User Resource Planning and Scheduling System). This system is a planning and scheduling tool which supports distributed planning and scheduling, based on resource allocation and optimization. Currently SURE is being used within the SURPASS by the UARS (Upper Atmospheric Research Satellite) SOLSTICE instrument to build a daily science plan and activity schedule and in a prototyping effort with NASA GSFC to demonstrate distributed planning and scheduling for the SOLSTICE II instrument on the EOS platform. For the SOLSTICE application the SURE utilizes a rule-based system. Development of a rule-based program using Ada CLIPS as opposed to using conventional programming, allows for capture of the science planning and scheduling heuristics in rules and provides flexibility in inserting or removing rules as the scientific objectives and mission constraints change. The SURE system's role as a component in the SURPASS, the purpose of the SURE planning and scheduling tool, the SURE knowledge base, and the software architecture of the SURE component are described.

Thalman, Nancy E.↗

Human Systems Integration (HSI) Practitioner's Guide

The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).

Zumbado, Jennifer Rochlis↗

Neural network applications

A design procedure is suggested for neural networks which accommodates the inclusion of such knowledge-based systems techniques as fuzzy logic and pairwise comparisons. The use of these procedures in the design of applications combines qualitative and quantitative factors with empirical data to yield a model with justifiable design and parameter selection procedures. The procedure is especially relevant to areas of back-propagation neural network design which are highly responsive to the use of precisely recorded expert knowledge.

Padgett, Mary L.↗

The Role of Reformulation in the Automatic Design of Satisfiability Procedures

Recently there has been increasing interest in the problem of knowledge compilation (Selman & Kautz91). This is the problem of identifying tractable techniques for determining the consequences of a knowledge base. We have developed and implemented a technique, called DRAT, that given a theory, i.e., a collection of firstorder clauses, can often produce a type of decision procedure for that theory that can be used in the place of a general-purpose first-order theorem prover for determining many of the consequences of that theory. Hence, DRAT does a type of knowledge compilation. Central to the DRAT technique is a type of reformulation in which a problem's clauses are restated in terms of different nonlogical symbols. The reformulation is isomorphic in the sense that it does not change the semantics of a problem.

VanBaalen, Jeffrey↗

S&MA Internship to Support Orion and the European Service Module

As a University Space Research Association (USRA) intern for NASA Johnson Space Center (JSC) during the summer 2016 work term, I worked on three main projects for the Space Exploration Division (NC) of the Safety and Mission Assurance (S&MA) Directorate. I worked on all three projects concurrently. One of the projects involved facilitating the status and closure of technical actions that were created during European Service Module (ESM) safety reviews by the MPCV Safety & Engineering Review Panel (MSERP). The two main duties included accurately collecting and summarizing qualitative data, and communicating that information to the European Space Agency (ESA) and Airbus (ESA's prime contractor) in a clear, succinct and precise manner. This project also required that I create a report on the challenges and opportunities of international S&MA. With its heavy emphasis on soft skills, this project taught me how to communicate better, by showing me how to present and share information in an easy-to-read and understandable format, and by showing me how to cooperate with and culturally respect international partners on a technical project. The second project involved working with the Orion Thermal Protection System (TPS) Process Failure Modes and Effects Analysis (PFMEA) Working Group to create the first full version of the Orion TPS PFMEA. The Orion TPS PFMEA Working Group met twice a week to analyze the Avcoat block installation process for failure modes, the failure modes effects, and how such failure modes could be controlled. I was in charge of implementing changes that were discussed in meeting, but were not implemented real time. Another major task included creating a significant portion of the content alongside another team member outside the two weekly meetings. This project caused me to become knowledgeable about TPS, heatshields, space-rated manufacturing, and non-destructive evaluation (NDE). The project also helped me to become better at working with a small team and helped improved my technical communication skills. My main duty for the third project was creating a Safety Verification Tracking Log (SVTL) for the Orbital Maneuvering System Engine (OMS-E), and contacting subject matter experts to close Hazard Report (HR) control verifications. This project also required me to support other OMS-E safety process tasks, like monitoring OMS-E vibration testing for Quality Assurance (QA) purposes. This project helped me become even more proficient in Excel. Throughout the project, I gained knowledge about the OMS-E system and improved my understanding of pressure systems and propellant systems. In terms of education goals, this work term has affirmed my desire to take a few more space-related courses, like orbital mechanics, so that I can have a better understanding of human spaceflight and the industry surrounding it. However, the work term did not persuade me to pursue a master's degree. In terms of career goals, this work term has helped me clarify the direction I would like to head in the future. The perspective of three summer terms working for NASA in S&MA has allowed me to observe that most S&MA employees joined S&MA after working in other NASA directorates, such as Engineering or Flight Operations. It is my belief that it would be advantageous for both NASA and I for me to broaden my knowledge base and technical skill set by completing hands-on technical work on human spaceflight projects, and for me to integrate my safety experience directly into technical work in other directorates. The other significant advantage to this proposed situation is that if I were to eventually return to S&MA, I would be returning with a substantial set of hands-on technical experience and knowledge, which would be a significant resource for S&MA tasks and projects.

Hutcheson, Connor↗

An expert system for planning and scheduling in a telerobotic environment

A knowledge based approach to assigning tasks to multi-agents working cooperatively in jobs that require a telerobot in the loop was developed. The generality of the approach allows for such a concept to be applied in a nonteleoperational domain. The planning architecture known as the task oriented planner (TOP) uses the principle of flow mechanism and the concept of planning by deliberation to preserve and use knowledge about a particular task. The TOP is an open ended architecture developed with a NEXPERT expert system shell and its knowledge organization allows for indirect consultation at various levels of task abstraction. Considering that a telerobot operates in a hostile and nonstructured environment, task scheduling should respond to environmental changes. A general heuristic was developed for scheduling jobs with the TOP system. The technique is not to optimize a given scheduling criterion as in classical job and/or flow shop problems. For a teleoperation job schedule, criteria are situation dependent. A criterion selection is fuzzily embedded in the task-skill matrix computation. However, goal achievement with minimum expected risk to the human operator is emphasized.

Ntuen, Celestine A.↗

An expert system for a distributed real-time trainer

The problem addressed by this expert system concerns the expansion of capability of a Real Time Trainer for the Spacelab flight crew. As requirements for more models or fidelity are placed upon the system, expansion is necessary. The simulator can be expanded using a larger processor or by going to a distributed system and expand by adding additional processors. The distributed system is preferable because it is more economical and can be expanded in a more incremental manner. An expert system was developed to evaluate modeling and timing capability within a real time training simulator. The expert system is based upon a distributed configuration. Components of the modeled system are control tasks, network tasks, emulator tasks, processors, displays, and a network. The distributed module expert system (DMES) allows the configuring of processors, tasks, display use, keyboard use, and selection of alternate methods to update the data buffer. Modules can be defined with execution occurring in a specific processor on a network. The system consists of a knowledge front end editor to interactively generate or update the knowledge base, an inference engine, a display module, and a recording module.

Purinton, Steven C.↗

Function Allocation between Automation and Human Pilot for Airborne Separation Assurance

Maintaining safe separation between aircraft is a key determinant of the airspace capacity to handle air transportation. With the advent of satellite-based surveillance, aircraft equipped with the needed technologies are now capable of maintaining awareness of their location in the airspace and sharing it with their surrounding traffic. As a result, concepts and cockpit automation are emerging to enable delegating the responsibility of maintaining safe separation from traffic to the pilot; thus increasing the airspace capacity by alleviating the limitation of the current non-scalable centralized ground-based system. In this paper, an analysis of allocating separation assurance functions to the human pilot and cockpit automation is presented to support the design of these concepts and technologies. A task analysis was conducted with the help of Petri nets to identify the main separation assurance functions and their interactions. Each function was characterized by three behavior levels that may be needed to perform the task: skill, rule and knowledge based levels. Then recommendations are made for allocating each function to an automation scale based on their behavior level characterization and with the help of Subject matter experts.

Idris, Husni↗

FY22 X-Hab: Rochester Institute of Technology: Gamification and Performance-Based Monitoring of Sensorimotor Training Activities

Proprioception is the body’s ability to sense movement, action, and location. Proprioceptive training is crucial for astronauts because humans balance system, cognitive functions, and muscle tone heavily rely on Earth’s gravity. The goal of this project is to create a training system that strengthens those characteristics to ensure astronauts not only maintain their coordination and cognitive skills, but improve upon them as well. Furthermore, the system’s live biofeedback provides astronauts with sensorimotor feedback to correct any balance dysfunction. The completed system prototype and data collected from it will support NASA’s knowledge base about the use of gamification for sensorimotor training activities.

Griffin Brown↗

Specification, Design, and Analysis of Advanced HUMS Architectures

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

Mukkamala, Ravi↗

The Life Cycle Application of Intelligent Software Modeling for the First Materials Science Research Rack

Marshall Space Flight Center (MSFC) has been funding development of intelligent software models to benefit payload ground operations for nearly a decade. Experience gained from simulator development and real-time monitoring and control is being applied to engineering design, testing, and operation of the First Material Science Research Rack (MSRR-1). MSRR-1 is the first rack in a suite of three racks comprising the Materials Science Research Facility (MSRF) which will operate on the International Space Station (ISS). The MSRF will accommodate advanced microgravity investigations in areas such as the fields of solidification of metals and alloys, thermo-physical properties of polymers, crystal growth studies of semiconductor materials, and research in ceramics and glasses. The MSRR-1 is a joint venture between NASA and the European Space Agency (ESA) to study the behavior of different materials during high temperature processing in a low gravity environment. The planned MSRR-1 mission duration is five (5) years on-orbit and the total design life is ten (IO) years. The MSRR-1 launch is scheduled on the third Utilization Flight (UF-3) to ISS, currently in February of 2003). The objective of MSRR-1 is to provide an early capability on the ISS to conduct material science, materials technology, and space product research investigations in microgravity. It will provide a modular, multi-user facility for microgravity research in materials crystal growth and solidification. An intelligent software model of MSRR-1 is under development and will serve multiple purposes to support the engineering analysis, testing, training, and operational phases of the MSRR-1 life cycle development. The G2 real-time expert system software environment developed by Gensym Corporation was selected as the intelligent system shell for this development work based on past experience gained and the effectiveness of the programming environment. Our approach of multi- uses of the simulation model and its intuitive graphics capabilities is providing a concurrent engineering environment for rapid prototyping and development. Operational schematics of the MSRR-1 electrical, thermal control, vacuum access, and gas supply systems, and furnace inserts are represented graphically in the environment. Logic to represent first order engineering calculations is coded into the knowledge base to simulate the operational behavior of the MSRR-1 systems. An example of engineering data provided includes electrical currents, voltages, operational power, temperatures, thermal fluid flow rates. pressures, and component status indications. These type of data are calculated and displayed at appropriate instrumentation points, and the schematics are animated to reflect the simulated operational status of the MSRR-1. The software control functions are also simulated to represent appropriate operational behavior based on automated control and response to commands received by the crew or ground controllers. The first benefit of this simulation environment is being realized in the high fidelity engineering analysis results from the electrical power system G2 model. Secondly, the MSRR-1 simulation model will be embedded with a hardware mock-up of the MSRR-1 to provide crew training on MSRR-1 integrated payload operations. G2 gateway code will output the simulated instrumentation values, termed as telemetry, in a flight-like data stream so that the crew has realistic and accurate simulated MSRR-1 data on the flight displays which will be designed for crew use. The simulation will also respond appropriately to crew or ground initiated commands, which will be part of normal facility operations. A third use of the G2 model is being planned; the MSRR-1 simulation will be integrated with additional software code as part of the test configuration of the primary onboard computer, or Master Controller, for MSRR-1. We will take advantage of the G2 capability to simulate the flight like data stream to test flight software responses and behavior. A fourth use of the G2 model will be to train the Ground Support Personnel that will monitor the MSRR-1 systems and payloads while they are operating aboard the ISS. The intuitive, schematic based environment will provide an excellent foundation for personnel to understand the integrated configuration and operation of the MSRR-1, and the anticipated telemetry feedback based on operational modes of the equipment. Expert monitoring features will be enhanced to provide a smart monitoring environment for the operators. These features include: (1) Animated, intuitive schematic-based displays which reflect telemetry values, (1) Real-time plotting of simulated or incoming sensor values, (3) High/Low exception monitoring for analog data, (4) Expected state monitoring for discrete data, (5) Data trending, (6) Automated malfunction procedure execution to diagnose problems, (7) Look ahead capability to planned MSRR-1 activities in the onboard timeline. And finally, the logic to calculate telemetry values will be deactivated, and the same environment will interface to the incoming data for the real-time telemetry stream to schematically represent the onboard hardware configuration. G2 will be the foundation for the real-time monitoring and control environment. In summary, our MSRR-1 simulation model spans many elements of the life cycle development of this project: Engineering Analysis, Test and Checkout, Training of Crew and Ground Personnel, and Real-time monitoring and control. By utilizing the unique features afforded by an expert system development environment, we have been able to synergize a powerful tool capable of addressing our project needs at every phase of project development.

Rice, Amanda↗

Behavior of Spinning Space Vehicles with Onboard Liquids, 2nd Edition, Technical Report B8030

Although the fundamental principles of spin stabilization are well established, uncertainty regarding the potential for rapid nutation growth caused by onboard liquids is a continuing concern. NASA and other organizations regularly encounter the issue of rapid nutation growth due to energy dissipation by liquids on spinning vehicles. Of concern is the stability of spinning upper stages and of spacecraft that spin for part or all of their missions. Several missions have required last-minute hardware or operational changes to deal with rapid nutation divergences that were identified late in the program. In some instances, major schedule slips were barely averted. In at least two cases, it was determined that a spinning upper stage was not a viable option. Historically, the "slosh" issue has been addressed by each space vehicle project individually, if it has been addressed at all. Due to budgetary and programmatic constraints, individual projects are unable to address the problem globally. Hence, there has been little effort to collect available test and flight data and use that data to make a coherent, unified picture of the "slosh" effect and how to deal with it. To some extent, each project has had to "reinvent the wheel", which can be both costly and risky. This study is a step toward correcting the situation. Specifically, the goal was to identify and collect available flight and test data for spinning vehicles with onboard liquid propellants. A total of 149 flight data points and 1,692 test points were collected as part of this study. This data was analyzed, correlated, and is presented here in a normalized form. In most cases, the normalization involves a dimensionless nutation time constant that can be used to predict performance of other vehicles with the same type of tank. For some configurations, it was also possible to identify conditions that can lead to resonance between nutational motion and liquid modes. Gaps in the knowledge base are identified and approaches to filling those gaps are outlined. The data presented here has two different but related uses. First, it can be applied directly to current and future spacecraft programs. Second, it can provide truth models for testing analytical techniques. Experience has shown that purely analytical models of the liquid "slosh" effect on spinning vehicles are unreliable unless they are validated against flight or test data. To the author's knowledge, this report contains the most extensive and varied data set available. As such, it should be a good resource for anyone seeking to develop and validate improved analytical techniques. All of the original digital data sets have been archived on disk, with copies provided to NASA/KSC. With some restrictions, many of these data sets can be made available to researchers within the United States. Whenever possible, spacecraft are identified by name in this report. However, several organizations provided access to data with the explicit proviso that their programs not be identified and that parameters be presented only in normalized form. These constraints have been respected.

Hubert, Carl↗