Search NASA⌕ Search

SEARCH · Search NASA

Results for “engineering knowledge integration”

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 307 records · Page 17
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Center Planning and Development Student Engineer at KSC

This summer I was the Student Trainee (Engineering) Pathways Intern (co-op) at the Kennedy Space Center (KSC) in the Center Planning & Development (CPD) Directorate. CPD works with commercial companies who are interested in using KSC's unique capabilities for spaceflight, spacecraft processing, ground systems and Research & Development (R&D) projects that fall in line with NASA's Mission and Vision. CPD is divided into three (3) groups: (1) AD-A, which works on the Master Planning for the center, (2) AD-B (where I am), which works on project control, management and integration, and (3) AD-C, which works on partnership development. CPD's main goal is to make KSC the world's preeminent multi-user spaceport and maintain the center as a leader in space exploration. CPD is a very diverse group of employees having a wide knowledge of not only the Space Shuttle, but also Expendable Launch Vehicles (ELV). The director of CPD, Scott Colloredo, is on the advisory board for Commercial Space Operations (CSO) and has a degree from ERAU. I worked on a number of different tasks for AD-B, as well as CPD, that includes, but not limited to: reviewing and reissuing engineering documents, weekly notes for CPD and senior management, engineering familiarizations with facilities at KSC, leading a tour for the Embry-Riddle Aeronautical University Career Services office, and working on actual agreements/proposals that will be used in the partnership process with multiple partners, along with other projects. Most of the work I have done is sensitive information and cannot be disclosed.

Engineer↗
NASA NTRS2017

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗
NASA NTRS1990

A knowledge-based approach to configuration layout, justification, and documentation

The design, development, and implementation is described of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on Space Station Freedom. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

Craig, F. G.↗
NASA NTRS1990

Machine learning research 1989-90

Multifunctional knowledge bases offer a significant advance in artificial intelligence because they can support numerous expert tasks within a domain. As a result they amortize the costs of building a knowledge base over multiple expert systems and they reduce the brittleness of each system. Due to the inevitable size and complexity of multifunctional knowledge bases, their construction and maintenance require knowledge engineering and acquisition tools that can automatically identify interactions between new and existing knowledge. Furthermore, their use requires software for accessing those portions of the knowledge base that coherently answer questions. Considerable progress was made in developing software for building and accessing multifunctional knowledge bases. A language was developed for representing knowledge, along with software tools for editing and displaying knowledge, a machine learning program for integrating new information into existing knowledge, and a question answering system for accessing the knowledge base.

Porter, Bruce W.↗
NASA NTRSDate not supplied

Lessons Learned from NASA Goddard Space Flight Center’s Product Development Lead Training Schedule and Cost Development Workshop: Continuous Improvement

This presentation provides a status of the Goddard Space Flight Center (GSFC) effort to increase foundational knowledge of Product Development Leads (PDLs) in schedule and cost management including earned value management (EVM). In 2012, GSFC’s Engineering and Technology Directorate (ETD) implemented an in-house training program to prepare PDLs for managing the technical, cost, schedule, and risk aspects of spaceflight systems to meet their subsystem commitments. Developed in-house, the PDL training program provides an integrated approach to requirements development, risk, schedule and cost management, EVM, performance tracking, and other areas. The program has been held twice yearly since its inception with 531 participating and 451 completing the curriculum. In 2017, the program won the Robert H. Goddard award for Quality and Process Improvement. Program development and evolution were presented in the 2018 NASA Schedule and Cost Symposium. The presentation was so well received that this year we focus on one workshop within the program: Schedule and Cost Development, including EVM. We examine the on-going logic modeling process and how participant and stakeholder data influence workshop content and design, and how the disciplines of schedule and cost contribute to mission success. In this presentation we refresh you on how the approach integrates lecture, small group discussion, estimating, case study exercises, and problem solving. We update you on the data collected from participants and stakeholders, and we discuss how we use these data to measure training effectiveness. Specific topics include: • How the logic model is used as the backbone for continuous program improvement, • How feedback influences implementation and curriculum updates, • How data collection and analysis inform workshop content and development, including participant discoveries of EVM data, • How including the resource analyst and planner in the product development team supports project success.

Lessons Learned↗
NASA NTRS1991

A Knowledge-Based Approach to Configuration Layout, Justification, and Documentation

The design, development, and implementation of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on the Space Station Freedom are described. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

Craig, F. G.↗
NASA NTRS1988

Knowledge based programming environments: A perspective

Programming environments is an area of recent origin and refers to an integrated set of tools, such as program library, text editor, compiler, and debugger, in support of program development. Understanding of programs and programming has lead to automated techniques for program development. Knowledge based programming system using program transformations offer significant impact on future program development methodologies. A review of recent developments in the area of knowledge based programming environments, from the perspective of software engineering, is presented.

Amin, Ashok T.↗
NASA NTRS1994

Galileo spacecraft modeling for orbital operations

The Galileo Jupiter orbital mission using the Low Gain Antenna (LGA) requires a higher degree of spacecraft state knowledge than was originally anticipated. Key elements of the revised design include onboard buffering of science and engineering data and extensive processing of data prior to downlink. In order to prevent loss of data resulting from overflow of the buffers and to allow efficient use of the spacecraft resources, ground based models of the spacecraft processes will be implemented. These models will be integral tools in the development of satellite encounter sequences and the cruise/playback sequences where recorded data is retrieved.

Mclaughlin, Bruce A.↗
NASA NTRS1999

Development of a 12-Thrust Chamber Kerosene /Oxygen Primary Rocket Sub-System for an Early (1964) Air-Augmented Rocket Ground-Test System

Airbreathing/Rocket combined-cycle, and specifically rocket-based combined- cycle (RBCC), propulsion systems, typically employ an internal engine flow-path installed primary rocket subsystem. To achieve acceptably short mixing lengths in effecting the "air augmentation" process, a large rocket-exhaust/air interfacial mixing surface is needed. This leads, in some engine design concepts, to a "cluster" of small rocket units, suitably arrayed in the flowpath. To support an early (1964) subscale ground-test of a specific RBCC concept, such a 12-rocket cluster was developed by NASA's Marshall Space Flight Center (MSFC). The small primary rockets used in the cluster assembly were modified versions of an existing small kerosene/oxygen water-cooled rocket engine unit routinely tested at MSFC. Following individual thrust-chamber tests and overall subsystem qualification testing, the cluster assembly was installed at the U. S. Air Force's Arnold Engineering Development Center (AEDC) for RBCC systems testing. (The results of the special air-augmented rocket testing are not covered here.) While this project was eventually successfully completed, a number of hardware integration problems were met, leading to catastrophic thrust chamber failures. The principal "lessons learned" in conducting this early primary rocket subsystem experimental effort are documented here as a basic knowledge-base contribution for the benefit of today's RBCC research and development community.

Pryor, D.↗
NASA NTRS2002

Propulsion Ground Testing with High Test Peroxide: Lessons Learned

Propulsion Ground Testing with High Test Peroxide (85 to 98% concentration) began at the NASA John C. Stennis Space Center in calendar year 1998, when the E3 Test Facility was modified to accomodate hydrogen peroxide (H2O2) in order to suport the research and development testing of the USAF Upper Stage Flight Experiment rocket engine. Since that time, efforts have continued to provide actual and planned test services to various customers, both U.S. Government and Commercial, in the ground test of many test articles, ranging from gas generators, to catalyst beds, to turbomachinery, to main injectors, to combustion chambers, to integrated rocket engines, to integrated stages. Along this path, and over the past 4 years, there has been both the rediscovery of previously learned lessons, through literature search, archive review, and personal interviews, as well as the learning of many new lessons as new areas are explored and new endeavors are tried. This paper will summarize those lessons learned in an effort to broaden the knowledge base as High Test Peroxide is considered more widely for use in rocket propulsion applications.

Bruce, Robert↗
NASA NTRS2010

Multiple Exhaust Nozzle Effects on J-2X Gas Generator Outlet Impedance

The current test setup of the J-2X gas generator system uses a multiple nozzle configuration to exhaust hot gases to drive the propellant supply turbines. Combustion stability assessment of this gas generator design requires knowledge of the impedance effects the multiple nozzle configuration creates on the combustion chamber acoustic modes. Parallel work between NASA and Sierra Engineering is presented, showing two methods used to calculate the effective end impedance resulting from multiple nozzle configurations. The NASA method is a simple estimate of the effective impedance using the long wavelength approximation. Sierra Engineering has developed a more robust numerical integration method implemented in ROCCID to accommodate for multiple nozzles. Analysis using both methods are compared to J-2X gas generator test data collected over the past year.

Kenny, R. Jeremy↗
NASA NTRS2015

Operator Informational Needs for Multiple Autonomous Small Vehicles

With the anticipated explosion of small unmanned aerial vehicles, it is highly likely that operators will be controlling fleets of autonomous vehicles. To fulfill the promise of autonomy, vehicle operators will not be concerned with manual control of the vehicle; instead, they will deal with the overall mission. Furthermore, the one operator to many vehicles is becoming a constant meme with various industries including package delivery, search and rescue, and utility companies. In order for an operator to concurrently control several vehicles, his station must look and behave very differently than the current ground control station instantiations. Furthermore, the vehicle will have to be much more autonomous, especially during non-normal operations, in order to accommodate the knowledge deficit or the information overload of the operator in charge of several vehicles. The expected usage increase of small drones requires presenting the operational information generated by a fleet of heterogeneous autonomous agents to an operator. NASA Langley Research Center's Autonomy Incubator has brought together researchers in various disciplines including controls, trajectory planning, systems engineering, and human factors to develop an integrated system to study autonomy issues. The initial human factors effort is focusing on mission displays that would give an operator the overall status of all autonomous agents involved in the current mission. This paper will discuss the specifics of the mission displays for operators controlling several vehicles.

Trujillo, Anna C.↗
NASA NTRS1994

Galileo Spacecraft Modeling for Orbital Operations

The Galileo Jupiter orbital mission using the Low Gain Antenna (LGA) requires a higher degree of spacecraft state knowledge than was originally anticipated. Key elements of the revised design include onboard buffering of science and engineering data and extensive processing of data prior to downlink. In order to prevent loss of data resulting from overflow of the buffers and to allow efficient use of the spacecraft resources, ground based models of the spacecraft processes will be implemented. These models will be integral tools in the development of satellite encounter sequences and the cruise/playback sequences where recorded data is retrieved.

aerospace↗
NASA NTRSDate not supplied

Selection Factors for Space Crops

NASA is actively researching space crop production to determine its potential to contribute to food system security on long duration missions beyond Low Earth Orbit. Our near-term focus is on nutrient and variety supplementation of prepackaged food with fresh produce that requires little or no processing. The longer-term goal is caloric replacement to become less dependent on Earth, and this will require cultivation of staple crops, processing and cooking equipment, integration with spacecraft air, water, and power systems, and automation. There are numerous technology and knowledge gaps remaining for sustainable space crop production systems, but one high-impact area is in the development of crops specifically customized to meet the needs of controlled environment crop production, astronaut health and well-being, and space-unique environments. Modern crop breeding and genome engineering tools are allowing for rapid development of new genotypes with incredible specificity. Targeted aspects to optimize crops for space have been identified and characterized into five categories: plant growth and development, plant physiology, produce nutrition, produce organoleptic acceptability, and postharvest characteristics. Within each category there are several targets that further the development of crop production systems for spaceflight, such as crop size and harvest index, tolerance to specific environmental stresses, optimizing target nutrients that are low or degrade in the packaged diet, maintenance time requirements, and less indigestible structural material. NASA-funded PIs are already beginning to develop candidate crops, and spaceflight testing and validation of novel space crops is on the horizon. Crops developed for space also have the potential to benefit terrestrial controlled environment agriculture crop production systems. This research was supported by NASA’s Space Biology and Human Research Programs.

Space Crop Production↗
NASA NTRSDate not supplied

Selection Factors for Space Crops

NASA is actively researching space crop production to determine its potential to contribute to food system security on long duration missions beyond Low Earth Orbit. Our near-term focus is on nutrient and variety supplementation of prepackaged food with fresh produce that requires little or no processing. The longer-term goal is caloric replacement to become less dependent on Earth, and this will require cultivation of staple crops, processing and cooking equipment, integration with spacecraft air, water, and power systems, and automation. There are numerous technology and knowledge gaps remaining for sustainable space crop production systems, but one high-impact area is in the development of crops specifically customized to meet the needs of controlled environment crop production, astronaut health and well-being, and space-unique environments. Modern crop breeding and genome engineering tools are allowing for rapid development of new genotypes with incredible specificity. Targeted aspects to optimize crops for space have been identified and characterized into five categories: plant growth and development, plant physiology, produce nutrition, produce organoleptic acceptability, and postharvest characteristics. Within each category there are several targets that further the development of crop production systems for spaceflight, such as crop size and harvest index, tolerance to specific environmental stresses, optimizing target nutrients that are low or degrade in the packaged diet, maintenance time requirements, and less indigestible structural material. NASA-funded PIs are already beginning to develop candidate crops, and spaceflight testing and validation of novel space crops is on the horizon. Crops developed for space also have the potential to benefit terrestrial controlled environment agriculture crop production systems. This research was supported by NASA’s Space Biology and Human Research Programs.

Space Crop Production↗
NASA NTRS1992

Reuse: A knowledge-based approach

This paper describes our research in automating the reuse process through the use of application domain models. Application domain models are explicit formal representations of the application knowledge necessary to understand, specify, and generate application programs. Furthermore, they provide a unified repository for the operational structure, rules, policies, and constraints of a specific application area. In our approach, domain models are expressed in terms of a transaction-based meta-modeling language. This paper has described in detail the creation and maintenance of hierarchical structures. These structures are created through a process that includes reverse engineering of data models with supplementary enhancement from application experts. Source code is also reverse engineered but is not a major source of domain model instantiation at this time. In the second phase of the software synthesis process, program specifications are interactively synthesized from an instantiated domain model. These specifications are currently integrated into a manual programming process but will eventually be used to derive executable code with mechanically assisted transformations. This research is performed within the context of programming-in-the-large types of systems. Although our goals are ambitious, we are implementing the synthesis system in an incremental manner through which we can realize tangible results. The client/server architecture is capable of supporting 16 simultaneous X/Motif users and tens of thousands of attributes and classes. Domain models have been partially synthesized from five different application areas. As additional domain models are synthesized and additional knowledge is gathered, we will inevitably add to and modify our representation. However, our current experience indicates that it will scale and expand to meet our modeling needs.

Iscoe, Neil↗
NASA NTRS2005

On Automating Failure Mode Analysis and Enforcing its Integrity

This paper reports our experience on the development of a design-for-safety (DFS) workbench called Risk Assessment and Management Environment (RAME) for microelectronic avionics systems. Our objective is to transform DFS practice from an ad-hoc, inefficient, error-prone approach to a stringent engineering process such that DFS can keep up with the rapidly growing complexity of avionics systems. In particular, RAME is built upon an information infrastructure that comprises a fault model, a knowledge base, and a failure reporting/tracking system. This infrastructure permits systematic learning from prior projects and enables the automation of failure modes, effects and criticality analysis (FMECA). Among other unique features, the most important advantage of RAME is its capability of directly accepting design source code in hardware description languages (HDLs) for automated failure mode analysis, which enables RAME to be compatible and to evolve with most electronic-computer-aided-design systems. Through an initial experimental evaluation of the RAME prototype, we show that our approach to FMECA automation improves failure mode analysis turn-around-time, completeness, and accuracy.

design for safety↗
NASA NTRS1993

The methodology of multi-viewpoint clustering analysis

One of the greatest challenges facing the software engineering community is the ability to produce large and complex computer systems, such as ground support systems for unmanned scientific missions, that are reliable and cost effective. In order to build and maintain these systems, it is important that the knowledge in the system be suitably abstracted, structured, and otherwise clustered in a manner which facilitates its understanding, manipulation, testing, and utilization. Development of complex mission-critical systems will require the ability to abstract overall concepts in the system at various levels of detail and to consider the system from different points of view. Multi-ViewPoint - Clustering Analysis MVP-CA methodology has been developed to provide multiple views of large, complicated systems. MVP-CA provides an ability to discover significant structures by providing an automated mechanism to structure both hierarchically (from detail to abstract) and orthogonally (from different perspectives). We propose to integrate MVP/CA into an overall software engineering life cycle to support the development and evolution of complex mission critical systems.

Mehrotra, Mala↗