Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Guideline 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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Constellation Operations: Lessons Learned For Future Exploration

The Earth science community has long advocated placing numerous instruments in space to study the Earth and its environment. Space agencies from many countries have responded to this call with a wide range of orbiting satellites. Scientists also envisioned placing some satellites in constellations, to enable diverse remote sensing instruments to observe the same part of the Earth (or its atmosphere) at about the same time, thereby increasing the opportunities for coincident science observations. The Earth Science Afternoon Constellation is answering this call, but there have been unique challenges on the way to its deployment. Currently, the Afternoon Constellation is to comprise six satellites. Three are currently on orbit: NASA's Earth Observing System (EOS)-Aqua (2002) and EOS-Aura (2004), and CNES's Polarization & Anisotropy of Reflectances for Atmospheric Sciences coupled with Observations from a Lidar (PARASOL) (2004). Two more satellites, the Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observation (CALIPSO) and Cloudsat, are to be jointly launched in late 2005, followed by the Orbiting Carbon Observatory (OCO) in 2008. The Afternoon Constellation is unlike most satellite constellations in that: 1) It is not a homogenous mix of identical satellites; rather it comprises several satellites with complementary observational capabilities; 2) The satellites are not spaced around the Earth to provide instantaneous, global coverage (as for a communications satellite constellation); rather they orbit in close proximity so observations occur at about the same time over approximately the same region; and 3) Lastly, the satellites are not managed and controlled by one organization; rather the list of organizations is diverse: CNES in France, NASA Centers at Goddard, Langley, and the Jet Propulsion Laboratory, and the US Air Force facility in New Mexico. The PARASOL launch and early orbit (L&EO) phase proved to be a learning experience for constellation members (including Constellation management). Prior to launch, all members signed an operations coordination document that spelled out basic requirements for keeping the constellation safe and resolving non-nominal events. Once PARASOL reached orbit and the mission teams gained experience using the newly-developed constellation monitoring tools, it became clear that some of the guidelines in the signed agreements had to be adjusted. This paper presents the L&EO lessons learned and how they were used to prepare for the next phase - the period following the CloudSat/CALIPSO launch.

Kelly, Angelita C.↗
NASA NTRS2014

Turbulence Modeling Verification and Validation

Computational fluid dynamics (CFD) software that solves the Reynolds-averaged Navier-Stokes (RANS) equations has been in routine use for more than a quarter of a century. It is currently employed not only for basic research in fluid dynamics, but also for the analysis and design processes in many industries worldwide, including aerospace, automotive, power generation, chemical manufacturing, polymer processing, and petroleum exploration. A key feature of RANS CFD is the turbulence model. Because the RANS equations are unclosed, a model is necessary to describe the effects of the turbulence on the mean flow, through the Reynolds stress terms. The turbulence model is one of the largest sources of uncertainty in RANS CFD, and most models are known to be flawed in one way or another. Alternative methods such as direct numerical simulations (DNS) and large eddy simulations (LES) rely less on modeling and hence include more physics than RANS. In DNS all turbulent scales are resolved, and in LES the large scales are resolved and the effects of the smallest turbulence scales are modeled. However, both DNS and LES are too expensive for most routine industrial usage on today's computers. Hybrid RANS-LES, which blends RANS near walls with LES away from walls, helps to moderate the cost while still retaining some of the scale-resolving capability of LES, but for some applications it can still be too expensive. Even considering its associated uncertainties, RANS turbulence modeling has proved to be very useful for a wide variety of applications. For example, in the aerospace field, many RANS models are considered to be reliable for computing attached flows. However, existing turbulence models are known to be inaccurate for many flows involving separation. Research has been ongoing for decades in an attempt to improve turbulence models for separated and other nonequilibrium flows. When developing or improving turbulence models, both verification and validation are important steps in the process. Verification insures that the CFD code is solving the equations as intended (no errors in the implementation). This is typically done either through the method of manufactured solutions (MMS) or through careful step-by-step comparisons with other verified codes. After the verification step is concluded, validation is performed to document the ability of the turbulence model to represent different types of flow physics. Validation can involve a large number of test case comparisons with experiments, theory, or DNS. Organized workshops have proved to be valuable resources for the turbulence modeling community in its pursuit of turbulence modeling verification and validation. Workshop contributors using different CFD codes run the same cases, often according to strict guidelines, and compare results. Through these comparisons, it is often possible to (1) identify codes that have likely implementation errors, and (2) gain insight into the capabilities and shortcomings of different turbulence models to predict the flow physics associated with particular types of flows. These are valuable lessons because they help bring consistency to CFD codes by encouraging the correction of faulty programming and facilitating the adoption of better models. They also sometimes point to specific areas needed for improvement in the models. In this paper, several recent workshops are summarized primarily from the point of view of turbulence modeling verification and validation. Furthermore, the NASA Langley Turbulence Modeling Resource website is described. The purpose of this site is to provide a central location where RANS turbulence models are documented, and test cases, grids, and data are provided. The goal of this paper is to provide an abbreviated survey of turbulence modeling verification and validation efforts, summarize some of the outcomes, and give some ideas for future endeavors in this area.

Rumsey, Christopher L.↗
NASA NTRS1996

Contamination control engineering design guidelines for the aerospace community

Thermal control surfaces, solar arrays, and optical devices may be adversely affected by a small quantity of molecular and/or particulate contamination. What is rarely discussed is how one: (1) quantifies the level of contamination that must be maintained in order for the system to function properly, and (2) enforces contamination control to ensure compliance with requirements. This document is designed to address these specific issues and is intended to serve as a handbook on contamination control for the reader, illustrating process and methodology while providing direction to more detailed references when needed. The effects of molecular contamination on reflecting and transmitting surfaces are examined and quantified in accordance with MIL STD 1246C. The generation, transportation, and deposition of molecular contamination is reviewed and specific examples are worked to illustrate the process a design engineer can use to estimate end of life cleanliness levels required by solar arrays, thermal control surfaces, and optical surfaces. A similar process is used to describe the effect of particulate contamination as related to percent area coverage (PAC) and bi-directional reflectance distribution function (BRDF). Relationships between PAC and surface cleanliness, which include the effects of submicron sized particles, are developed and BRDF is related to specific sensor design parameters such as Point Source Transmittance (PST). The pros and cons of various methods of preventing, monitoring, and cleaning surfaces are examined and discussed.

Tribble, A. C.↗
NASA NTRS1978

Manufacturing process applications team (MATeam)

Activities of the manufacturing applications team (MATeam) in effecting widespread transfer of NASA technology to aid in the solution of manufacturing problems in the industrial sector are described. During the program's first year of operation, 450 companies, industry associations, and government agencies were contacted, 150 manufacturing problems were documented, and 20 potential technology transfers were identified. Although none of the technology transfers has been commercialized and put in use, several are in the applications engineering phase, and others are in the early stages of implementation. The technology transfer process is described and guidelines used for the preparation of problems statements are included.

Bangs, E. R.↗
NASA NTRS1979

Implementation Procedure for STS Payloads, System Safety Requirements

Guidelines and instructions for the implementation of the SP&R system safety requirements applicable to STS payloads are provided. The initial contact meeting with the payload organization and the subsequent safety reviews necessary to comply with the system safety requirements of the SP&R document are described. Waiver instructions are included for the cases in which a safety requirement cannot be met.

Source record↗
NASA NTRS2014

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗
NASA NTRS1997

HARV ANSER Flight Test Data Retrieval and Processing Procedures

Under the NASA High-Alpha Technology Program the High Alpha Research Vehicle (HARV) was used to conduct flight tests of advanced control effectors, advanced control laws, and high-alpha design guidelines for future super-maneuverable fighters. The High-Alpha Research Vehicle is a pre-production F/A-18 airplane modified with a multi-axis thrust-vectoring system for augmented pitch and yaw control power and Actuated Nose Strakes for Enhanced Rolling (ANSER) to augment body-axis yaw control power. Flight testing at the Dryden Flight Research Center (DFRC) began in July 1995 and continued until May 1996. Flight data will be utilized to evaluate control law performance and aircraft dynamics, determine aircraft control and stability derivatives using parameter identification techniques, and validate design guidelines. To accomplish these purposes, essential flight data parameters were retrieved from the DFRC data system and stored on the Dynamics and Control Branch (DCB) computer complex at Langley. This report describes the multi-step task used to retrieve and process this data and documents the results of these tasks. Documentation includes software listings, flight information, maneuver information, time intervals for which data were retrieved, lists of data parameters and definitions, and example data plots.

Yeager, Jessie C.↗
NASA NTRS2013

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.

computer information security↗
NASA NTRS1965

NASA agenda D mission capabilities and restraints catalog, volume 1

The purpose of this document is to provide a single source of information regarding Agena D mission capabilities and restraints which affect spacecraft design. Utilized as a handbook during conceptual design and program planning, this catalog is intended to supplement the designer's knowledge of the Agena D and specify guidelines that enable him to design a spacecraft configuration which is: - Compatible with the booster system - Designed to realize maximum capabilities of the existing launch vehicle and associated equipment

Lockheed Missiles and Space Company↗
NASA NTRS1987

Numerical solutions of the compressible 3-D boundary-layer equations for aerospace configurations with emphasis on LFC

The application of stability theory in Laminar Flow Control (LFC) research requires that density and velocity profiles be specified throughout the viscous flow field of interest. These profile values must be as numerically accurate as possible and free of any numerically induced oscillations. Guidelines for the present research project are presented: develop an efficient and accurate procedure for solving the 3-D boundary layer equation for aerospace configurations; develop an interface program to couple selected 3-D inviscid programs that span the subsonic to hypersonic Mach number range; and document and release software to the LFC community. The interface program was found to be a dependable approach for developing a user friendly procedure for generating the boundary-layer grid and transforming an inviscid solution from a relatively coarse grid to a sufficiently fine boundary-layer grid. The boundary-layer program was shown to be fourth-order accurate in the direction normal to the wall boundary and second-order accurate in planes parallel to the boundary. The fourth-order accuracy allows accurate calculations with as few as one-fifth the number of grid points required for conventional second-order schemes.

Harris, Julius E.↗
NASA NTRS1993

Architectural design of the science complex at Elizabeth City State University

This paper gives an overall view of the architectural design process and elements in taking an idea from conception to execution. The project presented is an example for this process. Once the need for a new structure is established, an architect studies the requirements, opinions and limits in creating a structure that people will exist in, move through, and use. Elements in designing a building include factors such as volume and surface, light and form changes of scale and view, movement and stasis. Some of the other factors are functions and physical conditions of construction. Based on experience, intuition, and boundaries, an architect will utilize all elements in creating a new building. In general, the design process begins with studying the spatial needs which develop into an architectural program. A comprehensive and accurate architectural program is essential for having a successful building. The most attractive building which does not meet the functional needs of its users has failed at the primary reason for its existence. To have a good program an architect must have a full understanding of the daily functions that will take place in the building. The architectural program along with site characteristics are among a few of the important guidelines in studying the form, adjacencies, and circulation for the structure itself and also in relation to the adjacent structures. Conceptual studies are part of the schematic design, which is the first milestone in the design process. The other reference points are design development and construction documents. At each milestone, review and coordination with all the consultants is established, and the user is essential in refining the project. In design development phase, conceptual diagrams take shape, and architectural, structural, mechanical, and electrical systems are developed. The final phase construction documents convey all the information required to construct the building. The design process and elements described were applied in the following project.

Jahromi, Soheila↗
NASA NTRS2015

Second Annual Transformative Vertical Flight Concepts Workshop: Enabling New Flight Concepts Through Novel Propulsion and Energy Architectures

On August 3rd and 4th, 2015, a workshop was held at the NASA Ames Research Center, located at the Moffett Federal Airfield in California to explore the aviation communities interest in Transformative Vertical Flight (TVF) Concepts. The Workshop was sponsored by the AHS International (AHS), the American Institute of Aeronautics and Astronautics (AIAA), the National Aeronautics and Space Administration (NASA), and hosted by the NASA Aeronautics Research Institute (NARI). This second annual workshop built on the success and enthusiasm generated by the first TVF Workshop held in Washington, DC in August of 2014. The previous Workshop identified the existence of a multi-disciplinary community interested in this topic and established a consensus among the participants that opportunities to establish further collaborations in this area are warranted. The desire to conduct a series of annual workshops augmented by online virtual technical seminars to strengthen the TVF community and continue planning for advocacy and collaboration was a direct outcome of the first Workshop. The second Workshop organizers focused on four desired action-oriented outcomes. The first was to establish and document common stakeholder needs and areas of potential collaborations. This includes advocacy strategies to encourage the future success of unconventional vertiport capable flight concept solutions that are enabled by emerging technologies. The second was to assemble a community that can collaborate on new conceptual design and analysis tools to permit novel configuration paths with far greater multi-disciplinary coupling (i.e., aero-propulsive-control) to be investigated. The third was to establish a community to develop and deploy regulatory guidelines. This community would have the potential to initiate formation of an American Society for Testing and Materials (ASTM) F44 Committee Subgroup for the development of consensus-based certification standards for General Aviation scale vertiport capable flight systems. These standards need to accommodate novel fixed wing concepts that do not fit within the existing Federal Aviation Administration (FAA) rotorcraft certification framework (Code of Federal Regulations, Title 14, Chapter I, Subchapter C, Part 27). The fourth desired outcome was to launch an information campaign to ensure key U.S. Government agencies understand the potential benefits and industry interest in establishing new vertiport capable flight markets. This record of the Workshop proceedings documents Workshop activities and products including summaries of the video recorded technical presentations, overviews of three breakout sessions (Missions Operational Concepts, Prioritized Technical Challenges, Regulatory Roadmap), and a preliminary draft roadmap framework for TVF.

V/STOL↗
NASA NTRS1972

Manned space flight nuclear system safety. Volume 3: Reactor system preliminary nuclear safety analysis. Part 3: Nuclear Safety Analysis Document (NSAD)

Nuclear safety analysis as applied to a space base mission is presented. The nuclear safety analysis document summarizes the mission and the credible accidents/events which may lead to nuclear hazards to the general public. The radiological effects and associated consequences of the hazards are discussed in detail. The probability of occurrence is combined with the potential number of individuals exposed to or above guideline values to provide a measure of accident and total mission risk. The overall mission risk has been determined to be low with the potential exposure to or above 25 rem limited to less than 4 individuals per every 1000 missions performed. No radiological risk to the general public occurs during the prelaunch phase at KSC. The most significant risks occur from prolonged exposure to reactor debris following land impact generally associated with the disposal phase of the mission where fission product inventories can be high.

Source record↗
NASA NTRS1987

Guidelines for applying the Composite Specification Model (CSM)

The Composite Specification Model (CSM) is an approach to representing software requirements. Guidelines are provided for applying CSM and developing each of the three descriptive views of the software: the contextual view, using entities and relationships; the dynamic view, using states and transitions; and the function view, using data flows and processes. Using CSM results in a software specification document, which is outlined.

Agresti, William↗
NASA NTRS1998

Mission to the Solar System: Exploration and Discovery. A Mission and Technology Roadmap

Solar System exploration addresses some of humanity's most fundamental questions: How and when did life form on Earth? Does life exist elsewhere in the Solar System or in the Universe? - How did the Solar System form and evolve in time? - What can the other planets teach us about the Earth? This document describes a Mission and Technology Roadmap for addressing these and other fundamental Solar System Questions. A Roadmap Development Team of scientists, engineers, educators, and technologists worked to define the next evolutionary steps in in situ exploration, sample return, and completion of the overall Solar System survey. Guidelines were to "develop aa visionary, but affordable, mission and technology development Roadmap for the exploration of the Solar System in the 2000 to 2012 timeframe." The Roadmap provides a catalog of potential flight missions. (Supporting research and technology, ground-based observations, and laboratory research, which are no less important than flight missions, are not included in this Roadmap.)

Gulkis, S.↗
NASA NTRS2014

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to the communication among the military branches legionnaires. With advanced persistent threats (APT's) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning, and configuration of network devices i.e. routers and IDS's/IPS's. In addition, I will be completing security assessments on software and hardware, vulnerability assessments and reporting, and conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.

security↗
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 NTRS1995

Computational Modeling of Tires

This document contains presentations and discussions from the joint UVA/NASA Workshop on Computational Modeling of Tires. The workshop attendees represented NASA, the Army and Air force, tire companies, commercial software developers, and academia. The workshop objectives were to assess the state of technology in the computational modeling of tires and to provide guidelines for future research.

Noor, Ahmed K.↗