Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “draft”

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 523 records · Page 29

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM). This methodology and corresponding model, known as a Goal-Function Tree (GFT), provides a means to represent, decompose, and elaborate system goals and functions in a rigorous manner that connects directly to design through use of state variables that translate natural language requirements and goals into logical-physical state language. The state variable-based approach also provides the means to directly connect FM to the design, by specifying the range in which state variables must be controlled to achieve goals, and conversely, the failures that exist if system behavior go out-of-range. This in turn allows for the systems engineers and SHM/FM engineers to determine which state variables to monitor, and what action(s) to take should the system fail to achieve that goal. In sum, the GFT representation provides a unified approach to early-phase SE and FM development. This representation and methodology has been successfully developed and implemented using Systems Modeling Language (SysML) on the NASA Space Launch System (SLS) Program. It enabled early design trade studies of failure detection coverage to ensure complete detection coverage of all crew-threatening failures. The representation maps directly both to FM algorithm designs, and to failure scenario definitions needed for design analysis and testing. The GFT representation provided the basis for mapping of abort triggers into scenarios, both needed for initial, and successful quantitative analyses of abort effectiveness (detection and response to crew-threatening events).

Patterson, Jonathan D.↗

Goal-Function Tree Modeling for Systems Engineering and Fault Management

The draft NASA Fault Management (FM) Handbook (2012) states that Fault Management (FM) is a "part of systems engineering", and that it "demands a system-level perspective" (NASAHDBK- 1002, 7). What, exactly, is the relationship between systems engineering and FM? To NASA, systems engineering (SE) is "the art and science of developing an operable system capable of meeting requirements within often opposed constraints" (NASA/SP-2007-6105, 3). Systems engineering starts with the elucidation and development of requirements, which set the goals that the system is to achieve. To achieve these goals, the systems engineer typically defines functions, and the functions in turn are the basis for design trades to determine the best means to perform the functions. System Health Management (SHM), by contrast, defines "the capabilities of a system that preserve the system's ability to function as intended" (Johnson et al., 2011, 3). Fault Management, in turn, is the operational subset of SHM, which detects current or future failures, and takes operational measures to prevent or respond to these failures. Failure, in turn, is the "unacceptable performance of intended function." (Johnson 2011, 605) Thus the relationship of SE to FM is that SE defines the functions and the design to perform those functions to meet system goals and requirements, while FM detects the inability to perform those functions and takes action. SHM and FM are in essence "the dark side" of SE. For every function to be performed (SE), there is the possibility that it is not successfully performed (SHM); FM defines the means to operationally detect and respond to this lack of success. We can also describe this in terms of goals: for every goal to be achieved, there is the possibility that it is not achieved; FM defines the means to operationally detect and respond to this inability to achieve the goal. This brief description of relationships between SE, SHM, and FM provide hints to a modeling approach to provide formal connectivity between the nominal (SE), and off-nominal (SHM and FM) aspects of functions and designs. This paper describes a formal modeling approach to the initial phases of the development process that integrates the nominal and off-nominal perspectives in a model that unites SE goals and functions of with the failure to achieve goals and functions (SHM/FM).

Johnson, Stephen B.↗

Center-TRACON Automation System (CTAS) En Route Trajectory Predictor Requirements and Capabilities

This requirements framework document is designed to support the capture of requirements and capabilities for state-of-the-art trajectory predictors (TPs). This framework has been developed to assist TP experts in capturing a clear, consistent, and cross-comparable set of requirements and capabilities. The goal is to capture capabilities (types of trajectories that can be built), functional requirements (including inputs and outputs), non-functional requirements (including prediction accuracy and computational performance), approaches for constraint relaxation, and input uncertainties. The sections of this framework are based on the Common Trajectory Predictor structure developed by the FAA/Eurocontrol Cooperative R&D Action Plan 16 Committee on Common Trajectory Prediction. It is assumed that the reader is familiar with the Common TP Structure.1 This initial draft is intended as a first cut capture of the En Route TS Capabilities and Requirements. As such, it contains many annotations indicating possible logic errors in the CTAS code or in the description provided. It is intended to work out the details of the annotations with NASA and to update this document at a later time.

framework↗

Evaluation of Arctic Sea Ice Thickness Simulated by Arctic Ocean Model Intercomparison Project Models

Six Arctic Ocean Model Intercomparison Project model simulations are compared with estimates of sea ice thickness derived from pan-Arctic satellite freeboard measurements (2004-2008); airborne electromagnetic measurements (2001-2009); ice draft data from moored instruments in Fram Strait, the Greenland Sea, and the Beaufort Sea (1992-2008) and from submarines (1975-2000); and drill hole data from the Arctic basin, Laptev, and East Siberian marginal seas (1982-1986) and coastal stations (1998-2009). Despite an assessment of six models that differ in numerical methods, resolution, domain, forcing, and boundary conditions, the models generally overestimate the thickness of measured ice thinner than approximately 2 mand underestimate the thickness of ice measured thicker than about approximately 2m. In the regions of flat immobile landfast ice (shallow Siberian Seas with depths less than 25-30 m), the models generally overestimate both the total observed sea ice thickness and rates of September and October ice growth from observations by more than 4 times and more than one standard deviation, respectively. The models do not reproduce conditions of fast ice formation and growth. Instead, the modeled fast ice is replaced with pack ice which drifts, generating ridges of increasing ice thickness, in addition to thermodynamic ice growth. Considering all observational data sets, the better correlations and smaller differences from observations are from the Estimating the Circulation and Climate of the Ocean, Phase II and Pan-Arctic Ice Ocean Modeling and Assimilation System models.

sea ice↗

Planning Considerations Related to Collecting and Analyzing Samples of the Martian Soils

The Mars Sample Return (MSR) End-to-End International Science Analysis Group (E2E-iSAG [1]) established scientific objectives associ-ated with Mars returned-sample science that require the return and investigation of one or more soil samples. Soil is defined here as loose, unconsolidated materials with no implication for the presence or absence of or-ganic components. The proposed Mars 2020 (M-2020) rover is likely to collect and cache soil in addition to rock samples [2], which could be followed by future sample retrieval and return missions. Here we discuss key scientific consid-erations for sampling and caching soil samples on the proposed M-2020 rover, as well as the state in which samples would need to be preserved when received by analysts on Earth. We are seeking feedback on these draft plans as input to mission requirement formulation. A related planning exercise on rocks is reported in an accompanying abstract [3].

Liu, Yang↗

Sabots, Obturator and Gas-In-Launch Tube Techniques for Heat Flux Models in Ballistic Ranges

For thermal protection system (heat shield) design for space vehicle entry into earth and other planetary atmospheres, it is essential to know the augmentation of the heat flux due to vehicle surface roughness. At the NASA Ames Hypervelocity Free Flight Aerodynamic Facility (HFFAF) ballistic range, a campaign of heat flux studies on rough models, using infrared camera techniques, has been initiated. Several phenomena can interfere with obtaining good heat flux data when using this measuring technique. These include leakage of the hot drive gas in the gun barrel through joints in the sabot (model carrier) to create spurious thermal imprints on the model forebody, deposition of sabot material on the model forebody, thereby changing the thermal properties of the model surface and unknown in-barrel heating of the model. This report presents developments in launch techniques to greatly reduce or eliminate these problems. The techniques include the use of obturator cups behind the launch package, enclosed versus open front sabot designs and the use of hydrogen gas in the launch tube. Attention also had to be paid to the problem of the obturator drafting behind the model and impacting the model. Of the techniques presented, the obturator cups and hydrogen in the launch tube were successful when properly implemented

obturators↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs)

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This report contains the outcome of the assessment and the findings, observations, and NESC recommendations to the Agency and individual NASA Centers.

Prosser, William H.↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs) : Appendices - Volume 2

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This document contains the appendices to the main report.

Prosser, William H.↗

Solar Electric Propulsion (SEP) Systems for SMD Mission Needs. Technology Infusion Study.

Two presentations for SBAG and OPAG meetings: 1) Solar Electric Propulsion Systems for SMD Missions, and 2) Technology Infusion Study - Draft Findings Recommendation Small Bodies Assessment Group (SBAG) meeting is January 9th in Washington D.C., and the Outer Planets Assessment Group (OPAG) meeting is January 23-14 in Tucson, AZ. NASA sponsors these assessment groups, through the NRC, for the science community to assess and provide advice. These talks are to provide a status of 2 NASA activities, and to seek feedback from the respective science communities.

aerospace technology transfer↗

High Fidelity CFD Analysis and Validation of Rotorcraft Gearbox Aerodynamics Under Operational and Oil-Out Conditions

This document represents the evolving formal documentation of the NPHASE-PSU computer code. Version 3.15 is being delivered along with the software to NASA in 2013.Significant upgrades to the NPHASE-PSU have been made since the first delivery of draft documentation to DARPA and USNRC in 2006. These include a much lighter, faster and memory efficient face based front end, support for arbitrary polyhedra in front end, flow-solver and back-end, a generalized homogeneous multiphase capability, and several two-fluid modelling and algorithmic elements. Specific capability installed for the NASA Gearbox Windage Aerodynamics NRA are included in this version: Hybrid Immersed Overset Boundary Method (HOIBM) [Noack et. al (2009)] Periodic boundary conditions for multiple frames of reference, Fully generalized immersed boundary method, Fully generalized conjugate heat transfer, Droplet deposition, bouncing, splashing models, and, Film transport and breakup.

Gears↗

Evaluation of Agency Non-Code Layered Pressure Vessels (LPVs)

In coordination with the Office of Safety and Mission Assurance and the respective Center Pressure System Managers (PSMs), the NASA Engineering and Safety Center (NESC) was requested to formulate a consensus draft proposal for the development of additional testing and analysis methods to establish the technical validity, and any limitation thereof, for the continued safe operation of facility non-code layered pressure vessels. The PSMs from each NASA Center were asked to participate as part of the assessment team by providing, collecting, and reviewing data regarding current operations of these vessels. This report contains the outcome of the assessment and the findings, observations, and NESC recommendations to the Agency and individual NASA Centers.

Prosser, William H.↗

Waste Water Treatment Apparatus and Methods

An improved draft tube spout fluid bed (DTSFB) mixing, handling, conveying, and treating apparatus and systems, and methods for operating are provided. The apparatus and systems can accept particulate material and pneumatically or hydraulically conveying the material to mix and/or treat the material. In addition to conveying apparatus, a collection and separation apparatus adapted to receive the conveyed particulate material is also provided. The collection apparatus may include an impaction plate against which the conveyed material is directed to improve mixing and/or treatment. The improved apparatus are characterized by means of controlling the operation of the pneumatic or hydraulic transfer to enhance the mixing and/or reacting by controlling the flow of fluids, for example, air, into and out of the apparatus. The disclosed apparatus may be used to mix particulate material, for example, mortar; react fluids with particulate material; coat particulate material, or simply convey particulate material.

Littman, Howard↗

Sparse Superpixel Unmixing for Exploratory Analysis of CRISM Hyperspectral Images

Fast automated analysis of hyperspectral imagery can inform observation planning and tactical decisions during planetary exploration. Products such as mineralogical maps can focus analysts' attention on areas of interest and assist data mining in large hyperspectral catalogs. In this work, sparse spectral unmixing drafts mineral abundance maps with Compact Reconnaissance Imaging Spectrometer (CRISM) images from the Mars Reconnaissance Orbiter. We demonstrate a novel "superpixel" segmentation strategy enabling efficient unmixing in an interactive session. Tests correlate automatic unmixing results based on redundant spectral libraries against hand-tuned summary products currently in use by CRISM researchers.

Image Segmentation↗

Domain-Specific Languages and Diagram Customization for a Concurrent Engineering Environment

A major open question for advocates of Model-Based Systems Engineering (MBSE) is the question of how system and subsystem engineers will work together. The Systems Modeling Language (SysML), like any language intended for a large audience, is in tension between the desires for simplicity and for expressiveness. In order to be more expressive, many specialized language elements may be introduced, which will unfortunately make a complete understanding of the language a more daunting task. While this may be acceptable for systems modelers, it will increase the challenge of including subsystem engineers in the modeling effort. One possible answer to this situation is the use of Domain-Specific Languages (DSL), which are fully supported by the Unified Modeling Language (UML). SysML is in fact a DSL for systems engineering. The expressive power of a DSL can be enhanced through the use of diagram customization. Various domains have already developed their own schematic vocabularies. Within the space engineering community, two excellent examples are the propulsion and telecommunication subsystems. A return to simple box-and-line diagrams (e.g., the SysML Internal Block Diagram) are in many ways a step backward. In order allow subsystem engineers to contribute directly to the model, it is necessary to make a system modeling tool at least approximate in accessibility to drawing tools like Microsoft PowerPoint and Visio. The challenge is made more extreme in a concurrent engineering environment, where designs must often be drafted in an hour or two. In the case of the Jet Propulsion Laboratory's Team X concurrent design team, a subsystem is specified using a combination of PowerPoint for drawing and Excel for calculation. A pilot has been undertaken in order to meld the drawing portion and the production of master equipment lists (MELs) via a SysML authoring tool, MagicDraw. Team X currently interacts with its customers in a process of sharing presentations. There are several inefficiencies that arise from this situation. The first is that a customer team must wait two weeks to a month (which is 2-4 times the duration of most Team X studies themselves) for a finalized, detailed design description. Another is that this information must be re-entered by hand into the set of engineering artifacts and design tools that the mission concept team uses after a study is complete. Further, there is no persistent connection to Team X or institutionally shared formulation design tools and data after a given study, again reducing the direct reuse of designs created in a Team X study. This paper presents the underpinnings of subsystem DSLs as they were developed for this pilot. This includes specialized semantics for different domains as well as the process by which major categories of objects were derived in support of defining the DSLs. The feedback given to us by the domain experts on usability, along with a pilot study with the partial inclusion of these tools is also discussed.

Cole, Bjorn↗

Assessing Impacts of Climate Change on Food Security Worldwide

The combination of a warming Earth and an increasing population will likely strain the world's food systems in the coming decades. Experts involved with the Agricultural Model Intercomparison and Improvement Project (AgMIP) focus on quantifying the changes through time. AgMIP, a program begun in 2010, involves about 800 climate scientists, economists, nutritionists, information technology specialists, and crop and livestock experts. In mid-September 2015, the Aspen Global Change Institute convened an AgMIP workshop to draft plans and protocols for assessing global- and regional-scale modeling of crops, livestock, economics, and nutrition across major agricultural regions worldwide. The goal of this Coordinated Global and Regional Integrated Assessments (CGRA) project is to characterize climate effects on large- and small-scale farming systems.

farm crops↗

A Space Data System Standard for Telerobotic Operations

The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.

Mittman, David S.↗

Cold Helium Pressurization for Liquid Oxygen / Liquid Methane Propulsion Systems: Fully-Integrated Initial Hot-Fire Test Results

A prototype cold helium active pressurization system was incorporated into an existing liquid oxygen (LOX) / liquid methane (LCH4) prototype planetary lander and hot-fire tested to collect vehicle-level performance data. Results from this hot-fire test series were used to validate integrated models of the vehicle helium and propulsion systems and demonstrate system effectiveness for a throttling lander. Pressurization systems vary greatly in complexity and efficiency between vehicles, so a pressurization performance metric was also developed as a means to compare different active pressurization schemes. This implementation of an active repress system is an initial sizing draft. Refined implementations will be tested in the future, improving the general knowledge base for a cryogenic lander-based cold helium system.

Morehead, R. L.↗

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.↗