Search NASA⌕ Search

SEARCH · Search NASA

Results for “project documentation”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Human Factors Considerations for Area Navigation Departure and Arrival Procedures

Area navigation (RNAV) procedures are being implemented in the United States and around the world as part of a transition to a performance-based navigation system. These procedures are providing significant benefits and have also caused some human factors issues to emerge. Under sponsorship from the Federal Aviation Administration (FAA), the National Aeronautics and Space Administration (NASA) has undertaken a project to document RNAV-related human factors issues and propose areas for further consideration. The component focusing on RNAV Departure and Arrival Procedures involved discussions with expert users, a literature review, and a focused review of the NASA Aviation Safety Reporting System (ASRS) database. Issues were found to include aspects of air traffic control and airline procedures, aircraft systems, and procedure design. Major findings suggest the need for specific instrument procedure design guidelines that consider the effects of human performance. Ongoing industry and government activities to address air-ground communication terminology, design improvements, and chart-database commonality are strongly encouraged. A review of factors contributing to RNAV in-service errors would likely lead to improved system design and operational performance.

Barhydt, Richard↗
NASA NTRS2006

Human Factors Considerations for Performance-Based Navigation

A transition toward a performance-based navigation system is currently underway in both the United States and around the world. Performance-based navigation incorporates Area Navigation (RNAV) and Required Navigation Performance (RNP) procedures that do not rely on the location of ground-based navigation aids. These procedures offer significant benefits to both operators and air traffic managers. Under sponsorship from the Federal Aviation Administration (FAA), the National Aeronautics and Space Administration (NASA) has undertaken a project to document human factors issues that have emerged during RNAV and RNP operations and propose areas for further consideration. Issues were found to include aspects of air traffic control and airline procedures, aircraft systems, and procedure design. Major findings suggest the need for human factors-specific instrument procedure design guidelines. Ongoing industry and government activities to address air-ground communication terminology, procedure design improvements, and chart-database commonality are strongly encouraged.

Barhydt, Richard↗
NASA NTRS2009

Spreadsheets for Analyzing and Optimizing Space Missions

XCALIBR (XML Capability Analysis LIBRary) is a set of Extensible Markup Language (XML) database and spreadsheet- based analysis software tools designed to assist in technology-return-on-investment analysis and optimization of technology portfolios pertaining to outer-space missions. XCALIBR is also being examined for use in planning, tracking, and documentation of projects. An XCALIBR database contains information on mission requirements and technological capabilities, which are related by use of an XML taxonomy. XCALIBR incorporates a standardized interface for exporting data and analysis templates to an Excel spreadsheet. Unique features of XCALIBR include the following: It is inherently hierarchical by virtue of its XML basis. The XML taxonomy codifies a comprehensive data structure and data dictionary that includes performance metrics for spacecraft, sensors, and spacecraft systems other than sensors. The taxonomy contains >700 nodes representing all levels, from system through subsystem to individual parts. All entries are searchable and machine readable. There is an intuitive Web-based user interface. The software automatically matches technologies to mission requirements. The software automatically generates, and makes the required entries in, an Excel return-on-investment analysis software tool. The results of an analysis are presented in both tabular and graphical displays.

Some, Raphael R.↗
NASA NTRS2011

Lesson Learning at JPL

A lessons learned system is a hallmark of a mature engineering organization A formal lessons learned process can help assure that valuable lessons get written and published, that they are well-written, and that the essential information is "infused" into institutional practice. Requires high-level institutional commitment, and everyone's participation in gathering, disseminating, and using the lessons

project documentation↗
NASA NTRS2013

Conduit Coating Abrasion Testing

During my summer internship at NASA I have been working alongside the team members of the RESTORE project. Engineers working on the RESTORE project are creating ·a device that can go into space and service satellites that no longer work due to gas shortage or other technical difficulties. In order to complete the task of refueling the satellite a hose needs to be used and covered with a material that can withstand effects of space. The conduit coating abrasion test will help the researchers figure out what type of thermal coating to use on the hose that will be refueling the satellites. The objective of the project is to determine whether or not the conduit coating will withstand the effects of space. For the RESTORE project I will help with various aspects of the testing that needed to be done in order to determine which type of conduit should be used for refueling the satellite. During my time on the project I will be assisting with wiring a relay board that connected to the test set up by soldering, configuring wires and testing for continuity. Prior to the testing I will work on creating the testing site and help write the procedure for the test. The testing will take place over a span of two weeks and lead to an informative conclusion. Working alongside various RESTORE team members I will assist with the project's documentation and records. All in all, throughout my internship at NASA I hope to learn a number of valuable skills and be a part of a hard working team of engineers.

Sullivan, Mary K.↗
NASA NTRS2015

Check-Cases for Verification of 6-Degree-of-Freedom Flight Vehicle Simulations: Appendices - Volume 2

This NASA Engineering and Safety Center (NESC) assessment was established to develop a set of time histories for the flight behavior of increasingly complex example aerospacecraft that could be used to partially validate various simulation frameworks. The assessment was conducted by representatives from several NASA Centers and an open-source simulation project. This document contains details on models, implementation, and results.

Murri, Daniel G.↗
NASA NTRS2020

Reliability Analysis of Complex NASA Systems with Model-Based Engineering

The emergence of model-based engineering, with Model- Based Systems Engineering (MBSE) leading the way, is transforming design and analysis methodologies. The recognized benefits to systems development include moving from document-centric information systems and document-centric project communication to a model-centric environment in which control of design changes in the life cycles is facilitated. In addition, a “single source of truth” about the system, that is up-to-date in all respects of the design, becomes the authoritative source of data and information about the system. This promotes consistency and efficiency in regard to integration of the system elements as the design emerges and thereby may further optimize the design. Therefore Reliability Engineers (REs) supporting NASA missions must be integrated into model-based engineering to ensure the outputs of their analyses are relevant and value-needed to the design, development, and operational processes for failure risks assessment and communication.

FMEA/FMECA↗
NASA NTRS2020

Reliability Analysis of Complex NASA Systems with Model Based Engineering

The emergence of model-based engineering, with Model- Based Systems Engineering (MBSE) leading the way, is transforming design and analysis methodologies. The recognized benefits to systems development include moving from document-centric information systems and document-centric project communication to a model-centric environment in which control of design changes in the life cycles is facilitated. In addition, a “single source of truth” about the system, that is up-to-date in all respects of the design, becomes the authoritative source of data and information about the system. This promotes consistency and efficiency in regard to integration of the system elements as the design emerges and thereby may further optimize the design. Therefore Reliability Engineers (REs) supporting NASA missions must be integrated into model-based engineering to ensure the outputs of their analyses are relevant and value-needed to the design, development, and operational processes for failure risks assessment and communication.

Reliability prediction↗
NASA NTRS2021

Model-Based SMA Initiative Phase 1 Report: Reliability Tips Excerpt

The emergence of model-based engineering, with Model- Based Systems Engineering (MBSE) leading the way, is transforming design and analysis methodologies. [7] The recognized benefits to systems development include moving from document-centric information systems and document-centric project communication to a model-centric environment in which control of design changes in the life cycles is facilitated. In addition, a “single source of truth” about the system, that is up-to-date in all respects of the design, becomes the authoritative source of data and information about the system. This promotes consistency and efficiency in regard to integration of the system elements as the design emerges and thereby may further optimize the designs. Therefore Reliability Engineers (REs) supporting NASA missions must be integrated into model-based engineering, using these recommended modeling techniques, to ensure the outputs of their analyses are relevant and value-needed to the design, development, and operational processes for failure risk assessment and communication.

Nancy J. Lindsey↗
NASA NTRS2024

Winter Lightning to the Lee of Lake Ontario: The Lake-Effect Electrification (LEE) Field Campaign

The National Science Foundation-sponsored Lake-Effect Electrification (LEE) field campaign intensive observation periods occurred between November and early February 2022-23 across the eastern Lake Ontario region. Project LEE documented, for the first time, the total lightning and electrical charge structures of lake-effect storms and the associated storm environment using a lightning mapping array (LMA), a mobile dual-polarization X-band radar, and balloon-based soundings that measured vertical profiles of temperature, humidity, wind, electric field, and hydrometeor types. LEE also observed abundant wind turbine-initiated lightning, which is climatologically more likely during the winter. The frequent occurrence of intense lake-effect storms and the proximity of a wind farm with nearly 300 turbines each more than 100 m tall to the lee of Lake Ontario provided an ideal laboratory for this study.

Scott M Steiger↗
NASA NTRS1989

AdaNET prototype library administration manual

The functions of the AdaNET Prototype Library of Reusable Software Parts is described. Adopted from the Navy Research Laboratory's Reusability Guidebook (V.5.0), this is a working document, customized for use the the AdaNET Project. Within this document, the term part is used to denote the smallest unit controlled by a library and retrievable from it. A part may have several constituents, which may not be individually tracked. Presented are the types of parts which may be stored in the library and the relationships among those parts; a concept of trust indicators which provide measures of confidence that a user of a previously developed part may reasonably apply to a part for a new application; search and retrieval, configuration management, and communications among those who interact with the AdaNET Prototype Library; and the AdaNET Prototype, described from the perspective of its three major users: the part reuser and retriever, the part submitter, and the librarian and/or administrator.

Hanley, Lionel↗
NASA NTRS2000

SSME Advanced Health Management: Project Overview

This document is the viewgraphs from a presentation concerning the development of the Health Management system for the Space Shuttle Main Engine (SSME). It reviews the historical background of the SSME Advanced Health Management effort through the present final Health management configuration. The document includes reviews of three subsystems to the Advanced Health Management System: (1) the Real-Time Vibration Monitor System, (2) the Linear Engine Model, and (3) the Optical Plume Anomaly Detection system.

Plowden, John↗
NASA NTRS2009

Flight Mechanics Project

This report documents the generation of an outbound Earth to Moon transfer preliminary database consisting of four cases calculated twice a day for a 19 year period. The database was desired as the first step in order for NASA to rapidly generate Earth to Moon trajectories for the Constellation Program using the Mission Assessment Post Processor. The completed database was created running a flight trajectory and optimization program, called Copernicus, in batch mode with the use of newly created Matlab functions. The database is accurate and has high data resolution. The techniques and scripts developed to generate the trajectory information will also be directly used in generating a comprehensive database.

Steck, Daniel↗
NASA NTRS1988

AGT (Advanced Gas Turbine) technology project

An overall summary documentation is provided for the Advanced Gas Turbine Technology Project conducted by the Allison Gas Turbine Division of General Motors. This advanced, high risk work was initiated in October 1979 under charter from the U.S. Congress to promote an engine for transportation that would provide an alternate to reciprocating spark ignition (SI) engines for the U.S. automotive industry and simultaneously establish the feasibility of advanced ceramic materials for hot section components to be used in an automotive gas turbine. As this program evolved, dictates of available funding, Government charter, and technical developments caused program emphases to focus on the development and demonstration of the ceramic turbine hot section and away from the development of engine and powertrain technologies and subsequent vehicular demonstrations. Program technical performance concluded in June 1987. The AGT 100 program successfully achieved project objectives with significant technology advances. Specific AGT 100 program achievements are: (1) Ceramic component feasibility for use in gas turbine engines has been demonstrated; (2) A new, 100 hp engine was designed, fabricated, and tested for 572 hour at operating temperatures to 2200 F, uncooled; (3) Statistical design methodology has been applied and correlated to experimental data acquired from over 5500 hour of rig and engine testing; (4) Ceramic component processing capability has progressed from a rudimentary level able to fabricate simple parts to a sophisticated level able to provide complex geometries such as rotors and scrolls; (5) Required improvements for monolithic and composite ceramic gas turbine components to meet automotive reliability, performance, and cost goals have been identified; (6) The combustor design demonstrated lower emissions than 1986 Federal Standards on methanol, JP-5, and diesel fuel. Thus, the potential for meeting emission standards and multifuel capability has been initiated; (7) Small turbine engine aerodynamic and mechanical design capability has been initiated; and (8) An infrastructure of manpower, facilities, materials, and fabrication capabilities has been established which is available for continued development of ceramic component technology in gas turbine and other heat engines.

Source record↗
NASA NTRS2011

NASA Schedule Management Handbook

The purpose of schedule management is to provide the framework for time-phasing, resource planning, coordination, and communicating the necessary tasks within a work effort. The intent is to improve schedule management by providing recommended concepts, processes, and techniques used within the Agency and private industry. The intended function of this handbook is two-fold: first, to provide guidance for meeting the scheduling requirements contained in NPR 7120.5, NASA Space Flight Program and Project Management Requirements, NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Requirements, NPR 7120.8, NASA Research and Technology Program and Project Management Requirements, and NPD 1000.5, Policy for NASA Acquisition. The second function is to describe the schedule management approach and the recommended best practices for carrying out this project control function. With regards to the above project management requirements documents, it should be noted that those space flight projects previously established and approved under the guidance of prior versions of NPR 7120.5 will continue to comply with those requirements until project completion has been achieved. This handbook will be updated as needed, to enhance efficient and effective schedule management across the Agency. It is acknowledged that most, if not all, external organizations participating in NASA programs/projects will have their own internal schedule management documents. Issues that arise from conflicting schedule guidance will be resolved on a case by case basis as contracts and partnering relationships are established. It is also acknowledged and understood that all projects are not the same and may require different levels of schedule visibility, scrutiny and control. Project type, value, and complexity are factors that typically dictate which schedule management practices should be employed.

Source record↗
NASA NTRS2010

Airspace Systems Program: Next Generation Air Transportation System Concepts and Technology Development FY2010 Project Plan Version 3.0

This document describes the FY2010 plan for the management and execution of the Next Generation Air Transportation System (NextGen) Concepts and Technology Development (CTD) Project. The document was developed in response to guidance from the Airspace Systems Program (ASP), as approved by the Associate Administrator of the Aeronautics Research Mission Directorate (ARMD), and from guidelines in the Airspace Systems Program Plan. Congress established the multi-agency Joint Planning and Development Office (JPDO) in 2003 to develop a vision for the 2025 Next Generation Air Transportation System (NextGen) and to define the research required to enable it. NASA is one of seven agency partners contributing to the effort. Accordingly, NASA's ARMD realigned the Airspace Systems Program in 2007 to "directly address the fundamental research needs of the Next Generation Air Transportation System...in partnership with the member agencies of the JPDO." The Program subsequently established two new projects to meet this objective: the NextGen-Airspace Project and the NextGen-Airportal Project. Together, the projects will also focus NASA s technical expertise and world-class facilities to address the question of where, when, how and the extent to which automation can be applied to moving aircraft safely and efficiently through the NAS and technologies that address optimal allocation of ground and air technologies necessary for NextGen. Additionally, the roles and responsibilities of humans and automation influence in the NAS will be addressed by both projects. Foundational concept and technology research and development begun under the NextGen-Airspace and NextGen-Airportal projects will continue. There will be no change in NASA Research Announcement (NRA) strategy, nor will there be any change to NASA interfaces with the JPDO, Federal Aviation Administration (FAA), Research Transition Teams (RTTs), or other stakeholders

Kopardekar, Parimal H.↗
NASA NTRS2009

An Analysis of Rocket Propulsion Testing Costs

The primary mission at NASA Stennis Space Center (SSC) is rocket propulsion testing. Such testing is generally performed within two arenas: (1) Production testing for certification and acceptance, and (2) Developmental testing for prototype or experimental purposes. The customer base consists of NASA programs, DOD programs, and commercial programs. Resources in place to perform on-site testing include both civil servants and contractor personnel, hardware and software including data acquisition and control, and 6 test stands with a total of 14 test positions/cells. For several business reasons there is the need to augment understanding of the test costs for all the various types of test campaigns. Historical propulsion test data was evaluated and analyzed in many different ways with the intent to find any correlation or statistics that could help produce more reliable and accurate cost estimates and projections. The analytical efforts included timeline trends, statistical curve fitting, average cost per test, cost per test second, test cost timeline, and test cost envelopes. Further, the analytical effort includes examining the test cost from the perspective of thrust level and test article characteristics. Some of the analytical approaches did not produce evidence strong enough for further analysis. Some other analytical approaches yield promising results and are candidates for further development and focused study. Information was organized for into its elements: a Project Profile, Test Cost Timeline, and Cost Envelope. The Project Profile is a snap shot of the project life cycle on a timeline fashion, which includes various statistical analyses. The Test Cost Timeline shows the cumulative average test cost, for each project, at each month where there was test activity. The Test Cost Envelope shows a range of cost for a given number of test(s). The supporting information upon which this study was performed came from diverse sources and thus it was necessary to build several intermediate databases in order to understand, validate, and manipulate data. These intermediate databases (validated historical account of schedule, test activity, and cost) by themselves are of great value and utility. For example, for the Project Profile, we were able to merged schedule, cost, and test activity. This kind of historical account conveys important information about sequence of events, lead time, and opportunities for improvement in future propulsion test projects. The Product Requirement Document (PRD) file is a collection of data extracted from each project PRD (technical characteristics, test requirements, and projection of cost, schedule, and test activity). This information could help expedite the development of future PRD (or equivalent document) on similar projects, and could also, when compared to the actual results, help improve projections around cost and schedule. Also, this file can be sorted by the parameter of interest to perform a visual review of potential common themes or trends. The process of searching, collecting, and validating propulsion test data encountered a lot of difficulties which then led to a set of recommendations for improvement in order to facilitate future data gathering and analysis.

Ramirez-Pagan, Carmen P.↗