Search NASASearch

SEARCH · Search NASA

Results for “Project Closeout”

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 19 records

X-43A Final Flight Observations

The presentation will provide an overview of the final flight of the NASA X-43A project. The project consisted of three flights, two planned for Mach 7 and one for Mach 10. The first flight, conducted on June 2, 2001, was unsuccessful and resulted in a nine-month mishap investigation. A two-year return to flight effort ensued and concluded when the second Mach 7 flight was successfully conducted on March 27, 2004. The third and final flight, which occurred on November 16, 2004, was the first Mach 10 flight demonstration of an airframe-integrated, scramjet-powered, hypersonic vehicle. As such, the final flight presented first time technical challenges in addition to final flight project closeout concerns. The goals and objectives for the third flight as well as those for the project will be presented. The configuration of the Hyper-X stack including the X-43A, Hyper-X launch vehicle, and Hyper-X research vehicle adapter wil also be presented. Mission differences, vehicle modifications and lessons learned from the first and second flights as they applied to the third flight will also be discussed. Although X-43A flight 3 was always planned to be the final flight of the X-43A project, the X-43 program had two other vehicles and corresponding flight phases in X-43C and X-43B. Those other projects never manifested under the X-43 banner and X-43A flight 3 also became the final flight of X-43 program.

Grindle, Laurie

TC3 Overview

This presentation gives an overview of the technology, methods and processes developed during the TC3 Technical Challenge of the System-Wide Safety (SWS) project. The presentation goes over the motivation for doing this research, gives an overview of the tool, methods and process developed under this program, and describes case studies and impact in industry.

Software assurance

Development of Gas Analysis Capabilities

Project Description: The project objective was to develop gas analysis methodology and processes to identify and quantify contaminants specific to KSC, primarily volatile organic compounds (VOCs), utilizing the recently purchased gas chromatograph-mass spectrometer (GCMS) coupled with a sample pre-concentrator. This work established a standing, quick-turnaround quantitative GCMS methodology for KSC-specific VOCs associated with launching and landing spacecraft at trace-levels far below previous detection limits. Closeout Summary: This project established a standing methodology for rapid turnaround identification and quantification of 119 targeted VOCs considered most likely to be encountered at KSC. Of these, 111 of the calibration files are based on manufacturer-certified gas standard mixes. The other eight were generated using standards generated in-house from neat, certified reference materials using procedures for standard generation that were developed under this project. Additionally, the spectral signatures of two hydrofluorocarbon precision cleaning solvents, that are widely used in flight hardware processing, have been added to the mass spectral library for rapid qualitative identification.

Cristina Oropeza

University of Tennessee Center for Space Transportation and Applied Research (CSTAR)

The Center for Space Transportation and Applied Research had projects with space applications in six major areas: laser materials processing, artificial intelligence/expert systems, space transportation, computational methods, chemical propulsion, and electric propulsion. The closeout status of all these projects is addressed.

Source record

Characterization of Low-Temperature, Co-Fired Ceramic-Manufactured Electrostatic Thruster-Closeout Report

The goal of the project was to evaluate prototypes of an experimental thruster developed by the University of Arkansas (UA), Fayetteville, AR. The design under evaluation is a radio frequency (RF) electrostatic thruster that was fabricated using the low-temperature, co-fired ceramic (LTCC) materials and fabrication process. This materials system is analogous to printed circuit board (PCB) technology with the most significant difference being that the laminate is replaced by a ceramic material and the copper layer is replaced by printed sinterable silver paste. LTCC designs are baked after fabrication and assembled to realize an entirely monolithic structure with internal conductors, vias, and cavities. In this process, the LTCC electrostatic thruster (LTCC-ET) that is the subject of the present work becomes a monolithic ceramic thruster capable of withstanding temperatures in excess of 500 ºC. The UA and NASA Marshall Space Flight Center (MSFC) jointly performed prototype testing on the LTCC-ET under a NASA Cooperative Agreement Notice (CAN) award. The LTCC-ET was tested at MSFC in May 2018 over a 1-week period. There were two goals for the test program: (1) Testing to determine the operating parameters required to create plasma ignition in the test articles. This was explored by setting a propellant flowrate and increasing RF power until plasma ignition was observed. Testing was conducted with both argon and krypton. (2) Investigate the thrust and specific impulse (Isp) performance of the thruster as a function of propellant flowrate and grid voltage. This goal was not met during the project as technical challenges in maintaining stable plasma ignition arose due to stress and heating of the RF power feed. In summary, a prototype thruster design (consisting of three packaged units) was fabricated by UA and tested for the first time under vacuum conditions at MSFC to experimentally determine basic performance metrics and functionality. It was found that the design was not sufficiently optimized or robust enough in its initial iteration to support a significant test campaign or characterization program. It was concluded that the propellant outlet channels must be reduced in size with the flowpaths adjusted to increase propellant residence time in the thruster, and that the RF connector must be replaced with a version capable of handling higher power throughput and heating. However, even in its unoptimized form, a plasma could be produced in the LTCCET, demonstrating the efficacy of the design approach. The design is especially compelling due to its low cost to manufacture and, more importantly, its scalability of size and power throughput. Low cost and scalability are also important in that additional functionalities, such as thrust vectoring and plume charge neutralization, can be integrated into future designs with minimal additional cost. This project has matured the LTCC-ET development Technology Readiness Level (TRL) from 1 to 2. The low-cost RF plasma source portion of the LTCC device was matured from TRL 2 to 4 through the demonstration of RF plasma ignition under vacuum conditions.

Huang, P.-H. A.

Physical Studies of Brown Dwarfs and Extrasolar Planets

The main purpose of this grant proposal was to fund the ongoing work on brown dwarfs by Denise Stephens during her tenure at STScI as a postdoctoral researcher. We have completed approximately half of the three-year grant period. Dr. Stephens has now assumed to role of senior research associate at Johns Hopkins University and in this position is eligible to be PI of grants. Because the bulk of the work and funds under this grant have been and will continue to be for the purposes of supporting Dr. Stephens, we are transferring control of the grant to her at JHU. This closeout is a formality to allow that transfer. The largest project was the completion of a major work on the infrared photometry of L and T dwarfs. The paper was published in January 2004.

Noll, Keith

NASA Systems Engineering Handbook

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

Source record

The ICARE Method

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

Henke, Luke

Prometheus Project final report

This Final Report serves as an executive summary of the Prometheus Project's activities and deliverables from November 2002 through September 2005. It focuses on the challenges from a technical and management perspective, what was different and innovative about this project, and identifies the major options, decisions, and accomplishments of the Project team as a whole. However, the details of the activities performed by DOE NR and its contractors will be documented separately in accordance with closeout requirements of the DOE NR and consistent with agreements between NASA and NR.

Prometheus Project

External Tank (ET) Foam Thermal/Structural Analysis Project

An independent study was performed to assess the pre-launch thermally induced stresses in the Space Shuttle External Tank Bipod closeout and Ice/Frost ramps (IFRs). Finite element models with various levels of detail were built that included the three types of foam (BX-265, NCFI 24-124, and PDL 1034) and the underlying structure and bracketry. Temperature profiles generated by the thermal analyses were input to the structural models to calculate the stress levels. An area of high stress in the Bipod closeout was found along the aluminum tank wall near the phenolic insulator and along the phenolic insulator itself. This area of high stress might be prone to cracking and possible delamination. There is a small region of slightly increased stress in the NCFI 24-124 foam near its joint with the Bipod closeout BX-265 foam. The calculated stresses in the NCFI 24-124 acreage foam are highest at the NCFI 24-124/PDL 1034/tank wall interface under the LO2 and LH2 IFRs. The highest calculated stresses in the LH2 NCFI 24-124 foam are higher than in similar locations in the LO2 IFR. This finding is consistent with the dissection results of IFRs on ET-120.

Moore, David F.

The Intelligent Flight Control Program (IFCS)

Institute for Scientific Research, Inc. (ISR) is pleased to submit this closeout report for the Research Cooperative Agreement NCC4-00128 of accomplishments for the Intelligent Flight Control System (IFCS) Project. It has been a pleasure working with NASA and NASA partners as we strive to meet the goals of this research initiative. ISR was engaged in this Research Cooperative Agreement beginning March 3, 2001 and ending March 31, 2003. During this time, a great deal has been accomplished and plans have been solidified for the continued success of this program. Our primary areas of involvement include the following: 1) ARTS II Master Test Plan; 2) ARTS II Hardware Design and Development; 3) ARTS II Software Design and Development; 4) IFCS PID/BLNN/OLNN Development; 5) Performed Preliminary and Formal Testing; 6) Documentation and Reporting.

Source record

The Intelligent Flight Control Program (IFCS)

This is the closeout report for the Research Cooperative Agreement NCC4-00130 of accomplishments for the Intelligent Flight Control System (IFCS) Project. It has been a pleasure working with NASA and NASA partners as we strive to meet the goals of this research initiative. ISR was engaged in this Research Cooperative Agreement beginning 01 January 2003 and ending 31 January 2004. During this time ISR conducted efforts towards development of the ARTS II Computer Software Configuration Item (CSCI) version 4.0 by performing or developing the following: 1) Requirements Definition; 2) Software Design and Development; 3) Hardware In the Loop Simulation; 4) Unit Level testing; 5) Documentation.

Source record

Enabling the Capture and Sharing of NASA Technical Expertise Through Communities of Practice

Historically, engineers at the National Aeronautics and Space Administration (NASA) had few opportunities or incentives to share their technical expertise across the Agency. Its center- and project- focused culture often meant that knowledge never left organizational and geographic boundaries. With increasingly complex missions, the closeout of the Shuttle Program, and a new generation entering the workforce, developing a knowledge sharing culture became critical. To address this need, the Office of the Chief Engineer established communities of practice on the NASA Engineering Network. These communities were strategically aligned with NASA's core competencies in such disciplines as avionics, flight mechanics, life support, propulsion, structures, loads and dynamics, human factors, and guidance, navigation, and control. This paper describes the process used to identify and develop communities, from establishing simple websites that compiled discipline-specific resources to fostering a knowledge-sharing environment through collaborative and interactive technologies. It includes qualitative evidence of improved availability and transfer of knowledge. It focuses on pivotal capabilities that increased knowledge exchange such as a custom-made Ask An Expert system, community contact lists, publication of key resources, and submission forms that allowed any user to propose content for the sites. It discusses the peer relationships that developed through the communities and the leadership and infrastructure that made them possible.

Topousis, Daria E.