Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Handbook”

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 1,189 records · Page 66

Fault Management Practice: A Roadmap for Improvement

Autonomous fault management (FM) is critical for deep space and planetary missions where the limited communication opportunities may prevent timely intervention by ground control. Evidence of pervasive architecture, design, and verification/validation problems with NASA FM engineering has been revealed both during technical reviews of spaceflight missions and in flight. These problems include FM design changes required late in the life-cycle, insufficient project insight into the extent of FM testing required, unexpected test results that require resolution, spacecraft operational limitations because certain functions were not tested, and in-flight anomalies and mission failures attributable to fault management. A recent NASA initiative has characterized the FM state-of-practice throughout the spacecraft development community and identified common NASA, DoD, and commercial concerns that can be addressed in the near term through the development of a FM Practitioner's Handbook and the formation of a FM Working Group. Initial efforts will focus on standardizing FM terminology, establishing engineering processes and tools, and training.

Fesq, Lorraine M.↗

Technology Readiness Level Assessment Process as Applied to NASA Earth Science Missions

Technology assessments of fourteen science instruments were conducted within NASA using the NASA Technology Readiness Level (TRL) Metric. The instruments were part of three NASA Earth Science Decadal Survey missions in pre-formulation. The Earth Systematic Missions Program (ESMP) Systems Engineering Working Group (SEWG), composed of members of three NASA Centers, provided a newly modified electronic workbook to be completed, with instructions. Each instrument development team performed an internal assessment of its technology status, prepared an overview of its instrument, and completed the workbook with the results of its assessment. A team from the ESMP SEWG met with each instrument team and provided feedback. The instrument teams then reported through the Program Scientist for their respective missions to NASA's Earth Science Division (ESD) on technology readiness, taking the SEWG input into account. The instruments were found to have a range of TRL from 4 to 7. Lessons Learned are presented; however, due to the competition-sensitive nature of the assessments, the results for specific missions are not presented. The assessments were generally successful, and produced useful results for the agency. The SEWG team identified a number of potential improvements to the process. Particular focus was on ensuring traceability to guiding NASA documents, including the NASA Systems Engineering Handbook. The TRL Workbook has been substantially modified, and the revised workbook is described.

Systems Engineering↗

Human Systems Integration (HSI) Practitioner's Guide

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

Zumbado, Jennifer Rochlis↗

Numerical Simulation of Bolide Entry with Ground Footprint Prediction

As they decelerate through the atmosphere, meteors deposit mass, momentum and energy into the surrounding air at tremendous rates. Trauma from the entry of such bolides produces strong blast waves that can propagate hundreds of kilometers and cause substantial terrestrial damage even when no ground impact occurs. We present a new simulation technique for airburst blast prediction using a fully-conservative, Cartesian mesh, finite-volume solver and investigate the ability of this method to model far- field propagation over hundreds of kilometers. The work develops mathematical models for the deposition of mass, momentum and energy into the atmosphere and presents verification and validation through canonical problems and the comparison of surface overpressures, and blast arrival times with actual results in the literature for known bolides. The discussion also examines the effects of various approximations to the physics of bolide entry that can substantially decrease the computational expense of these simulations. We present parametric studies to quantify the influence of entry-angle, burst-height and other parameters on the ground footprint of the airburst, and these values are related to predictions from analytic and handbook-methods.

Simulation↗

Developing a Fault Management Guidebook for Nasa's Deep Space Robotic Missions

NASA designs and builds systems that achieve incredibly ambitious goals, as evidenced by the Curiosity rover traversing on Mars, the highly complex International Space Station orbiting our Earth, and the compelling plans for capturing, retrieving and redirecting an asteroid into a lunar orbit to create a nearby a target to be investigated by astronauts. In order to accomplish these feats, the missions must be imbued with sufficient knowledge and capability not only to realize the goals, but also to identify and respond to off-nominal conditions. Fault Management (FM) is the discipline of establishing how a system will respond to preserve its ability to function even in the presence of faults. In 2012, NASA released a draft FM Handbook in an attempt to coalesce the field by establishing a unified terminology and a common process for designing FM mechanisms. However, FM approaches are very diverse across NASA, especially between the different mission types such as Earth orbiters, launch vehicles, deep space robotic vehicles and human spaceflight missions, and the authors were challenged to capture and represent all of these views. The authors recognized that a necessary precursor step is for each sub-community to codify its FM policies, practices and approaches in individual, focused guidebooks. Then, the sub-communities can look across NASA to better understand the different ways off-nominal conditions are addressed, and to seek commonality or at least an understanding of the multitude of FM approaches. This paper describes the development of the "Deep Space Robotic Fault Management Guidebook," which is intended to be the first of NASA's FM guidebooks. Its purpose is to be a field-guide for FM practitioners working on deep space robotic missions, as well as a planning tool for project managers. Publication of this Deep Space Robotic FM Guidebook is expected in early 2015. The guidebook will be posted on NASA's Engineering Network on the FM Community of Practice website so that it will be available to all NASA projects. Future plans for subsequent guidebooks for the other NASA sub-communities are proposed.

Fesq, Lorraine M.↗

Space Launch System Vibration Analysis Support

The ultimate goal for my efforts during this internship was to help prepare for the Space Launch System (SLS) integrated modal test (IMT) with Rodney Rocha. In 2018, the Structural Engineering Loads and Dynamics Team will have 10 days to perform the IMT on the SLS Integrated Launch Vehicle. After that 10 day period, we will have about two months to analyze the test data and determine whether the integrated vehicle modes/frequencies are adequate for launching the vehicle. Because of the time constraints, NASA must have newly developed post-test analysis methods proven well and with technical confidence before testing. NASA civil servants along with help from rotational interns are working with novel techniques developed and applied external to Johnson Space Center (JSC) to uncover issues in applying this technique to much larger scales than ever before. We intend to use modal decoupling methods to separate the entangled vibrations coming from the SLS and its support structure during the IMT. This new approach is still under development. The primary goal of my internship was to learn the basics of structural dynamics and physical vibrations. I was able to accomplish this by working on two experimental test set ups, the Simple Beam and TAURUS-T, and by doing some light analytical and post-processing work. Within the Simple Beam project, my role involves changing the data acquisition system, reconfiguration of the test set up, transducer calibration, data collection, data file recovery, and post-processing analysis. Within the TAURUS-T project, my duties included cataloging and removing the 30+ triaxial accelerometers, coordinating the removal of the structure from the current rolling cart to a sturdy billet for further testing, preparing the accelerometers for remounting, accurately calibrating, mounting, and mapping of all accelerometer channels, and some testing. Hammer and shaker tests will be performed to easily visualize mode shapes at low frequencies. Short analytical projects using MATLAB were also assigned to aid in research efforts. These included integration of acceleration data for comparison to measured displacement data. Laplace and Fourier transforms were also investigated to determine viability as a method of modal decoupling. In addition to these projects, I was also able contribute work that would benefit future interns and the division as a whole. I gave a short presentation and answered questions to aid in the recruitment of subsequent interns and co-ops for the division. I also assisted in revisions and additions to Intern/Co-Op Handbook to provide incoming employees with background information on the organization they are about to work for. I further developed tutorial on Pulse software, which was used for data acquisition for both experiments and will be helpful to interns and engineers that may be unfamiliar to the software. I gained a diverse range of experience throughout my internship. I was introduced to advanced dynamics and analytical techniques. This was through new experience with both hands on experimentation and analytical post processing methods. I was exposed to the benefits of interdepartmental collaboration and developed stronger skills in time management by coordinating two different tests at once. This internship provided an excellent opportunity to see how engineering theories applied to real life scenarios, and an introduction to how NASA/JSC solves technical problems.

Johnson, Katie↗

20th Century NASA History: Mercury Manned Orbital Capsule Detail Specification and Project Mercury Capsule Flight Operations Manual

The detailed preparation required in attempting a mission of the magnitude and scope of PROJECT MERCURY obviously cannot and need not be covered in a document of the handbook type. Prior to any actual attempt to launch a manned capsule, many weeks will be spent in an extensive training and familiarization program. The information contained in this manual, therefore, will pre-suppose a detailed knowledge of the capsule systems and will be confined, for the most part, to procedural data.

Source record↗

Natural Environments Definition for Design

Planning for future National Aeronautics and Space Administration (NASA) missions will encompass a variety of operational and engineering activities that involve a multitude of issues, constraints, and influences derived from the natural environment. This Technical Memorandum (TM) presents a definition of the natural environment, i.e., a description in engineering handbook format of models and data specifically selected to support the architecture development, engineering design, and technology development for NASA's Exploration Systems Development (ESD) initiatives.

Justh, H. L.↗

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

This document 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 expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

Steven R Hirshorn↗

Kepler Fine Guidance Sensor Data

The Kepler and K2 missions collected Fine Guidance Sensor (FGS) data in addition to the science data, as discussed in the Kepler Instrument Handbook (KIH, Van Cleve and Caldwell 2016). The FGS CCDs are frame transfer devices (KIH Table 7) located in the corners of the Kepler focal plane (KIH Figure 24), which are read out 10 times every second. The FGS data are being made available to the user community for scientific analysis as flux and centroid time series, along with a limited number of FGS full frame images which may be useful for constructing a World Coordinate System (WCS) or otherwise putting the time series data in context. This document will describe the data content and file format, and give example MATLAB scripts to read the time series. There are three file types delivered as the FGS data.1. Flux and Centroid (FLC) data: time series of star signal and centroid data. 2. Ancillary FGS Reference (AFR) data: catalog of information about the observed stars in the FLC data. 3. FGS Full-Frame Image (FGI) data: full-frame image snapshots of the FGS CCDs.

Kepler↗

Closed Loop Control Compact Exercise Device for Use on MPCV

Long duration space travel to Mars or to an asteroid will expose astronauts to extended periods of reduced gravity. To combat spaceflight physiological deconditioning, astronauts will use resistive and aerobic exercise regimens for the duration of the space flight to minimize the loss of bone density, muscle mass and aerobic capacity that occurs during exposure to a reduced gravity environment. Unlike the International Space Station (ISS), the mass and volume available for an exercise device in the next generation of spacecraft is limited. Therefore, compact exercise device prototypes are being developed for human in the loop evaluations. The NASA Human Research Program (HRP) is managing Advanced Exercise Concepts (AEC) requirements development and candidate technology maturation for all exploration mission profiles from Multi-Purpose Crew Vehicle (MPCV) exploration missions (e.g., EM-2, up to 21 day) to Mars Transit (up to 1000 day) missions. Numerous technologies have been considered and evaluated against HRP-approved functional requirements and include flywheel, pneumatic and closed-loop microprocessor-controlled motor driven power plants. Motor driven technologies offer excellent torque density and load accuracy characteristics as well as the ability to create custom mechanical impedance (the dynamic relationship between force and velocity) and custom load versus position exercise algorithms. Further, closed-loop motor-driven technologies offer the ability to monitor exercise dose parameters and adapt to the needs of the crewmember for real time optimization of exercise prescriptions. A simple proportional-integral-derivative (PID) controller is demonstrated in a prototype motor driven exercise device with comparison to resistive static and dynamic load set points and aerobic work rate targets. The resistive load term in the algorithm includes a constant force component (Fcmg) as well as inertial component (Fima) and a discussion of system tuning is presented in terms of addressing key functional requirements and human interfaces. The device aerobic modality is modelled as a rowing exercise using ground data sets obtained from Concept 2 rowers as well as competitive rowing1. A discussion of software and electronic implementations are presented which demonstrate unique approaches to meeting the constrained mass, volume and power requirements of the MPCV. . In addition to utilizing traditional PID control, controllers utilizing state feedback with gains solved using a Linear Quadratic Regulator will be developed. Controllability and observability will be utilized to investigate the need for state measurement in the design. As the control system directly interacts with human test subjects, robust methods such as H-infinity are also being investigated.1. Kleshnev V. Biomechanics. In: Rowing, Handbook of Sports Medicine and Science. ed. by Secher N., Voliantis S. IOC Medical Commission, Blackwell Pub. pp. 22-34, 2007

microgravity↗

Technology and Tool Development to Support Safety and Mission Assurance

The Assurance Case approach is being adopted in a number of safety-mission-critical application domains in the U.S., e.g., medical devices, defense aviation, automotive systems, and, lately, civil aviation. This paradigm refocuses traditional, process-based approaches to assurance on demonstrating explicitly stated assurance goals, emphasizing the use of structured rationale, and concrete product-based evidence as the means for providing justified confidence that systems and software are fit for purpose in safely achieving mission objectives. NASA has also been embracing assurance cases through the concepts of Risk Informed Safety Cases (RISCs), as documented in the NASA System Safety Handbook, and Objective Hierarchies (OHs) as put forth by the Agency's Office of Safety and Mission Assurance (OSMA). This talk will give an overview of the work being performed by the SGT team located at NASA Ames Research Center, in developing technologies and tools to engineer and apply assurance cases in customer projects pertaining to aviation safety. We elaborate how our Assurance Case Automation Toolset (AdvoCATE) has not only extended the state-of-the-art in assurance case research, but also demonstrated its practical utility. We have successfully developed safety assurance cases for a number of Unmanned Aircraft Systems (UAS) operations, which underwent, and passed, scrutiny both by the aviation regulator, i.e., the FAA, as well as the applicable NASA boards for airworthiness and flight safety, flight readiness, and mission readiness. We discuss our efforts in expanding AdvoCATE capabilities to support RISCs and OHs under a project recently funded by OSMA under its Software Assurance Research Program. Finally, we speculate on the applicability of our innovations beyond aviation safety to such endeavors as robotic, and human spaceflight.

Mission Assuranc↗

MIL-HDBK-338-Environmental Conversion Table Correction

In reliability analysis for space launch vehicles, limited data is frequently a challenge due to the pure number of launches. A common solution is to use surrogate historical data of similar components from other industries (military data). The operating environment of the common data may be different from that of the necessary target analysis. The military electronic design handbook (MIL-HDBK-338) has a table for converting Mean Time Between Failure (MTBF) data from one environment to another. However, the table has some discrepancies and rounding of complementary conversions; namely going from environment A to B does not given the same result as going from B to A. This presentation will show the discrepancies in the original conversation table, the greater than expected magnitude, the problem with the updated published table and a suggested corrected table to reference when doing MTBF data environment conversion.

Hark, Frank↗

An Investigation of Risk Management Approaches for NASA Piloted X-Plane Projects

NASA is resuming X-plane research. It plans to build a low-boom supersonic flight demonstrator (LBFD), an all-electric general aviation aircraft (X-57), and possibly an ultra-efficient subsonic transport (UEST) demonstrator. In an attempt to define what levels of risk are appropriate in piloted X-plane research, the NASA Office of the Chief Engineer (OCE) evaluated numerous NASA, Department of Defense (DoD), and industry project management and risk assessment tools. Provided are the results of the evaluations of NASA Procedural Requirements (NPR) 7120.5, 7120.8, and 8705.4; Langley Research Center (LaRC) Procedural Requirement (LPR) 7120.5; Dryden (Armstrong) Center Procedures S-002 and X-009; and Military Handbook 516C. Some of these were applied to the LBFD and X-57 aircraft. The impacts on risk of budgeting decisions and specialized flight conditions were also considered. None of the evaluated processes were found to be fully appropriate for governing experimental aircraft projects, but many useful elements were found in some of them.

X-59↗

CARA Devolution ESMO Pilot Program

Information regarding the current effort ongoing with CARA to determine the steps needed to have a mission move away from being supported by CARA, otherwise referred to as Devolving/Devolution. Information regarding the working group established to undertake this effort, documents agreed that needed to be written and plans for a parallel operations period. The communication between ESMO and CARA during the Parallel Operations period will be as the following: – A daily email will be sent from ESMO to CARA describing each HIE that is being actively planned and worked, and the action that ESMO is planning on taking – A weekly email will be sent from ESMO to CARA listing the progress toward achieving the parallel operations success criteria – The CARA team will remain on distribution for ESMO HIE communications and CAM invitations associated with DAMs/RMMs during the parallel operations period – At a minimum, 2 members of the CARA team will be in attendance at all ESMO planning and review discussions – A monthly email will be sent from ESMO to CARA with the HIE metrics • During parallel operations, ESMO will contact NASA Headquarters to report any redDevolution Working Group laid out and completed all steps needed to begin parallel operations • Parallel Ops for ESMO began on 11/26 (CARA in shadow mode only) • Any lessons learned from parallel ops will be folded back into documents/templates • Hope to achieve all success criteria < 6 months • Decision for permanent devolution will be based on completion of parallel ops and other future documentation creation (CARA Standard and Handbook, etc) and reviews (ORR) event which is less than 2 days from TCA, including the proposed remediation, on an as-needed daily basis flow using SpaceTrack to send and receive data

ESMO pilot devolution program↗

A Structured, Model-Based Systems Engineering Methodology for Operations System Design

Two widely accepted techniques for lowering the cost and risk of developing systems are (1) the use of a defined systems engineering (SE) process or methodology and (2) the reuse of existing (previously built) system components. The first technique is represented, for example, in materials published by NASA (e.g., NASA Systems Engineering Handbook) or by professional societies such as INCOSE (International Council on Systems Engineering). Well-formed SE techniques provide value by establishing the proper scope of the system (e.g., requirements), and by identifying and resolving problems relatively early in project lifecycles, when fixes are less expensive. The second technique (reuse) is applied most commonly to hardware and software; it seeks to avoid replicating design and implementation costs while also reducing risk by placing proven capabilities into operational use. In this paper, we outline a methodology combining these two techniques and extending reuse beyond hardware and software to foundational aspects of a Mission Operation System’s (MOS) design. We describe the system design artifacts that result (e.g., requirements, design documentation), as well as the reusable patterns and elements of the design, and their interrelationships. This approach is enabled by model-based systems engineering (MBSE) techniques and tools and is currently available in SysML form as a plug-in to MagicDraw. Additionally, usage of a rigorous MBSE approach allows for training materials and tutorials to be packaged within the overall model itself. The results of such an approach include decreased cost and risk during the design phase, improved ability of the MOS development team to investigate trade spaces and identify impacts to important flight-ground trade studies. Such results extend into decreased costs and risk in later phases due to improved design, decreased need for late fixes or development of "glue-ware" or scripts to fill unanticipated gaps in functionality, and improved ability to identify and plan testing and other validation activities. Finally, lower operational costs can be expected, both due to improved quality of the MOS, increased ease of maintaining updated knowledge of system configuration, and the fact that training and procedural materials are also updated at the same time as accepted system changes.

Bindschadler, Duane L.↗

Fine Guidance Sensor Data

The Kepler and K2 missions collected Fine Guidance Sensor (FGS) data in addition to the science data, as discussed in the Kepler Instrument Handbook (KIH, Van Cleve and Caldwell 2016). The FGS CCDs areframe transfer devices located in the corners of the Kepler focal plane, which are read out 10 times every second. The FGS data are being made available to the user community for scientific analysis as flux and centroid time series, along with a limited number of FGS full frame images which may be useful for constructing a World Coordinate System (WCS) or otherwise putting the time series data in context. This document will describe the data content and file format, and give example MATLAB scripts to read the time series.

FGS↗

Aircraft Conceptual Structural Design Using the AMMIT Structural Analysis Tool

Aircraft conceptual structural design is the process of developing and refining an idea for an aircraft into a feasible structural design. The process typically involves multiple evaluations of a single configuration and can require designers to examine thousands of concepts. Standard approaches to conducting structural analyses in this phase are either based on the use of historical or empirical data or often require significant expertise in structural analysis to perform these rapid assessments. The AMMIT structural analysis tool includes structural line models and handbook methods wrapped in a simple to use interface that can enable rapid, physics-based structural designs without requiring extensive structural expertise. The objectives of the present paper are to introduce AMMIT, describe the methods used in AMMIT, and present the results of the validation effort. Validation of the AMMIT methodology was performed on nine aircraft to determine the accuracy of the methods, highlight features of AMMIT, and guide future development of the methodology. Results of the validation effort indicated that AMMIT provides a prediction of primary structural weight for each aircraft with an acceptable level of error during the preliminary design phase with a minimal expenditure of computational resources.

Horvath, Bryce L.↗