Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “CaSe”

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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

OMC Compressor Case

This report summarizes efforts expended in the development of an all-composite compressor case. Two pre-production units have been built, one utilizing V-CAP and one utilizing AFR-700B resin systems. Both units have been rig tested at elevated temperatures well above design limit loads. This report discusses the manufacturing processes, test results, and Finite Element Analysis performed. The V-CAP unit was funded by NASA-Lewis Research Center in 1994 under contract number NAS3- 27442 for Development of an All-Composite OMC Compressor Case. This contract was followed by an Air Force study in 1996 to build and identical unit using the AFR-700B resin system in place of the V-CAP system. The second compressor case was funded under U.S. Air Force contract F33615-93-D-5326, Advanced Materials for Aerospace Structures Special Studies (AMAS3), Delivery Order 0021 entitled "Advanced Polymeric Composite Materials and Structures Technology for Advanced High Temperature Gas Turbine Engines.' Initial studies using the V-CAP resin system were undertaken in 1993 under a NASA Lewis contract (NAS3-26829). A first prototype unit was developed in a joint program between Textron-Lycoming (now Allied Signal) and Brunswick (now Lincoln Composites). This unit included composite end closures using low density, high temperature molded end closures. The units was similar in size and shape to a titanium case currently used on the PT-21 0 engine and was funded as part of the integrated High Performance Turbine Engine Technology (EHPTET) initiative of DOD and NASA.

Humphrey, W. Donald↗
NASA NTRS1994

Managing Action Duration Uncertainty with Just-In-Case Scheduling

Some applications involve automatic generation and execution of schedules that contain actions with uncertain durations. Such uncertainty can cause schedules to break during execution. This paper presents a technique, called Just-In-Case scheduling or JIC, for building robust schedules that tend not to break. The technique implements the common sense idea of being prepared for likely errors, just in case they should occur. The JIC algorithm analyzes a given schedule, determines where it is likely to break, reinvokes the scheduler to generate a contingent schedule for each highly probable break case, and produces a "multiply contingent" schedule. The technique was developed for a real telescope scheduling problem, and the paper presents empirical results showing that Just-In-Case scheduling performs extremely well for this problem.

Bresina, John↗
NASA NTRS2001

A Simple Case Study of a Grid Performance System

This document presents a simple case study of a Grid performance system based on the Grid Monitoring Architecture (GMA) being developed by the Grid Forum Performance Working Group. It describes how the various system components would interact for a very basic monitoring scenario, and is intended to introduce people to the terminology and concepts presented in greater detail in other Working Group documents. We believe that by focusing on the simple case first, working group members can familiarize themselves with terminology and concepts, and productively join in the ongoing discussions of the group. In addition, prototype implementations of this basic scenario can be built to explore the feasibility of the proposed architecture and to expose possible shortcomings. Once the simple case is understood and agreed upon, complexities can be added incrementally as warranted by cases not addressed in the most basic implementation described here. Following the basic performance monitoring scenario discussion, unresolved issues are introduced for future discussion.

Aydt, Ruth↗
NASA NTRS2003

Description of 103 Cases of Hypobaric Sickness from NASA-sponsored Research

One hundred and three cases of hypobaric decompression sickness (DCS) are documented, with 6 classified as Type II DCS. The presence and grade of venous gas emboli (VGE) are part of the case descriptions. Cases were diagnosed from 731 exposures in 5 different altitude chambers from 4 different laboratories between the years 1982 and 1999. Research was funded by NASA to develop operational prebreathe (PB) procedures that would permit safe extravehicular activity from the Space Shuttle and International Space Station using an extravehicular mobility unit (spacesuit) operated at 4.3 psia. Both vehicles operate at 14.7 psia with an "air" atmosphere, so a PB procedure is required to reduce nitrogen partial pressure in the tissues to an acceptable level prior to depressurization to 4.3 psia. Thirty-two additional descriptions of symptoms that were not diagnosed as DCS together with VGE information are also included. The information for each case resides in logbooks from 32 different tests. Additional information is stored in the NASA Decompression Sickness Database and the Prebreathe Reduction Protocol Database, both maintained by the Environmental Physiology Laboratory at the Johnson Space Center. Both sources were reviewed to provide the narratives that follow.

Conkin, Johnny↗
NASA NTRS2003

Using CASE to Adopt Organizational Learning at NASA

The research direction was articulated in a statement of work created in collaboration between two program colleagues, an outside researcher and an internal user. The researcher was to deliver an implemented CASE tool (CasewiseTM) that was to be used to serve non-traditional (i.e., not software development related) organizational purposes. The explicitly stated functions of the tool were the support of 1) ISO-9000 compliance in the documentation of processes and 2) the management of process improvement. The collaborative team consisted of the researcher (GT), a full-time accompanying student (CRO), and the user (JD). The team originally focused on populating the CASE repository for the purpose of solving the two primary objectives. Consistent with the action research approach, several additional user requirements emerged as the project evolved, needs became apparent in discussions about how the tool would be used to solve organizational problems. These deliverables were contained within the CASE repository: 1) the creation of a paradigm diagram 2) the creation of a context diagram 3) the creation of child diagrams 4) the generation of 73 issues relating to organizational change 5) a compendium of stakeholder interview transcripts All record keeping was done manually and then keyed into the CASE interface. An issue is the difference between an organization s current situation (action) and its collective ideals.

Templeton, Gary F.↗
NASA NTRS2005

Raman Lidar Measurements During the International H2O Project: Instrument Comparisons and Case Studies - 2

The NASA/GSFC Scanning Raman Lidar (SRL) participated in the International H2O Project (IHOP) that occurred in May and June, 2002 in the midwestern part of the U. S. The SRL system configuration and methods of data analysis were described in part I of this paper. In this second part, comparisons of SRL water vapor measurements and those of chilled mirror radiosonde and LASE airborne water vapor lidar are performed. Two case studies are presented; one for daytime and one for nighttime. The daytime case study is of a convectively driven boundary layer event and is used to characterize the SRL water vapor random error characteristics. The nighttime case study is of a thunderstorm-generated cirrus cloud case that is studied in it s meteorological context. Upper tropospheric humidification due to precipitation from the cirrus cloud is quantified as is the cirrus cloud ice water content and particle depolarization ratio. These detailed cirrus cloud measurements are being used in a cirrus cloud modeling study.

Whiteman, D. N.↗
NASA NTRS2007

The Continuous Intercomparison of Radiation Codes (CIRC): Phase I Cases

CIRC aspires to be the successor to ICRCCM (Intercomparison of Radiation Codes in Climate Models). It is envisioned as an evolving and regularly updated reference source for GCM-type radiative transfer (RT) code evaluation with the principle goal to contribute in the improvement of RT parameterizations. CIRC is jointly endorsed by DOE's Atmospheric Radiation Measurement (ARM) program and the GEWEX Radiation Panel (GRP). CIRC's goal is to provide test cases for which GCM RT algorithms should be performing at their best, i.e, well characterized clear-sky and homogeneous, overcast cloudy cases. What distinguishes CIRC from previous intercomparisons is that its pool of cases is based on observed datasets. The bulk of atmospheric and surface input as well as radiative fluxes come from ARM observations as documented in the Broadband Heating Rate Profile (BBHRP) product. BBHRP also provides reference calculations from AER's RRTM RT algorithms that can be used to select the most optimal set of cases and to provide a first-order estimate of our ability to achieve radiative flux closure given the limitations in our knowledge of the atmospheric state.

Oreopoulos, Lazaros↗
NASA NTRS2005

Method of producing an integral resonator sensor and case

The present invention discloses an inertial sensor having an integral resonator. A typical sensor comprises a planar mechanical resonator for sensing motion of the inertial sensor and a case for housing the resonator. The resonator and a wall of the case are defined through an etching process. A typical method of producing the resonator includes etching a baseplate, bonding a wafer to the etched baseplate, through etching the wafer to form a planar mechanical resonator and the wall of the case and bonding an end cap wafer to the wall to complete the case.

Shcheglov, Kirill V.↗
NASA NTRS2009

Installing a Test Tap on a Metal Battery Case

A mechanical fitting and relatively simple and safe method of installing it on the metal case of a battery have been devised to provide access to the interior of the battery to perform inspection and/or to measure such internal conditions as temperature and pressure. A metal boss or stud having an exterior thread is attached to the case by capacitor-discharge stud welding (CDSW), which takes only 3 to 6 milliseconds and in which the metallurgical bond (weld) and the heat-affected zone are limited to a depth of a few thousandths of an inch (a few hundredths of a millimeter). These characteristics of CDSW prevent distortion of the case and localized internal heating that could damage the chemical components inside of the battery. An access hole is then drilled through the stud and case, into the interior of the battery. A mechanical fitting having a matching thread is installed on the stud and the interior end of the fitting is sealed with a pressure-sealing washer/gasket. The exterior end of the fitting is configured for attachment of whatever instrumentation is required for the selected inspection or measurement.

Mayes, Daniel R.↗
NASA NTRS2009

Deriving Safety Cases from Automatically Constructed Proofs

Formal proofs provide detailed justification for the validity of claims and are widely used in formal software development methods. However, they are often complex and difficult to understand, because the formalism in which they are constructed and encoded is usually machine-oriented, and they may also be based on assumptions that are not justified. This causes concerns about the trustworthiness of using formal proofs as arguments in safety-critical applications. Here, we present an approach to develop safety cases that correspond to formal proofs found by automated theorem provers and reveal the underlying argumentation structure and top-level assumptions. We concentrate on natural deduction style proofs, which are closer to human reasoning than resolution proofs, and show how to construct the safety cases by covering the natural deduction proof tree with corresponding safety case fragments. We also abstract away logical book-keeping steps, which reduces the size of the constructed safety cases. We show how the approach can be applied to the proofs found by the Muscadet prover.

Basir, Nurlida↗
NASA NTRS2010

Human Spaceflight Trajectory Operations: A Case Study from STS-132/ULF4

Prior to the launch of the STS-132/ULF4 mission, the International Space Station (ISS) Flight Control Team was alerted to the approach of a space debris with a predicted time of closest approach approximately 1 hr after Space Shuttle docking. As a result, the ISS team considered performing a collision avoidance maneuver prior to the Space Shuttle s approach. The purpose of this presentation will be to use this case study to illustrate best practices of the human spaceflight trajectory operations team. The presentation will begin with an overview of the roles of the real-time ISS and Space Shuttle trajectory flight control teams. Then, the STS-132/ULF4 case study will be used to illustrate the issues and lessons learned involved in performing Space Shuttle rendezvous maneuver planning and execution. Specific elements of the STS-132 Space Shuttle rendezvous maneuver profile that can be used to provide mission assurance in cases of trajectory uncertainty will be described and discussed. Additionally, this case study will be used to provide context for identifying lessons learned in an operational environment that requires technical and decision-making coordination between two control center teams with two potentially maneuvering space vehicles.

Cutri-Kohart, Rebecca↗
NASA NTRS2011

From Science to e-Science to Semantic e-Science: A Heliosphysics Case Study

The past few years have witnessed unparalleled efforts to make scientific data web accessible. The Semantic Web has proven invaluable in this effort; however, much of the literature is devoted to system design, ontology creation, and trials and tribulations of current technologies. In order to fully develop the nascent field of Semantic e-Science we must also evaluate systems in real-world settings. We describe a case study within the field of Heliophysics and provide a comparison of the evolutionary stages of data discovery, from manual to semantically enable. We describe the socio-technical implications of moving toward automated and intelligent data discovery. In doing so, we highlight how this process enhances what is currently being done manually in various scientific disciplines. Our case study illustrates that Semantic e-Science is more than just semantic search. The integration of search with web services, relational databases, and other cyberinfrastructure is a central tenet of our case study and one that we believe has applicability as a generalized research area within Semantic e-Science. This case study illustrates a specific example of the benefits, and limitations, of semantically replicating data discovery. We show examples of significant reductions in time and effort enable by Semantic e-Science; yet, we argue that a "complete" solution requires integrating semantic search with other research areas such as data provenance and web services.

Narock, Thomas↗
NASA NTRS2011

JPL Thermal Design Modeling Philosophy and NASA-STD-7009 Standard for Models and Simulations - A Case Study

The Standard JPL thermal engineering practice prescribes worst-case methodologies for design. In this process, environmental and key uncertain thermal parameters (e.g., thermal blanket performance, interface conductance, optical properties) are stacked in a worst case fashion to yield the most hot- or cold-biased temperature. Thus, these simulations would represent the upper and lower bounds. This, effectively, represents JPL thermal design margin philosophy. Uncertainty in the margins and the absolute temperatures is usually estimated by sensitivity analyses and/or by comparing the worst-case results with "expected" results. Applicability of the analytical model for specific design purposes along with any temperature requirement violations are documented in peer and project design review material. In 2008, NASA released NASA-STD-7009, Standard for Models and Simulations. The scope of this standard covers the development and maintenance of models, the operation of simulations, the analysis of the results, training, recommended practices, the assessment of the Modeling and Simulation (M&S) credibility, and the reporting of the M&S results. The Mars Exploration Rover (MER) project thermal control system M&S activity was chosen as a case study determining whether JPL practice is in line with the standard and to identify areas of non-compliance. This paper summarizes the results and makes recommendations regarding the application of this standard to JPL thermal M&S practices.

thermal blanket performance↗
NASA NTRS2012

Hierarchical Safety Cases

We introduce hierarchical safety cases (or hicases) as a technique to overcome some of the difficulties that arise creating and maintaining industrial-size safety cases. Our approach extends the existing Goal Structuring Notation with abstraction structures, which allow the safety case to be viewed at different levels of detail. We motivate hicases and give a mathematical account of them as well as an intuition, relating them to other related concepts. We give a second definition which corresponds closely to our implementation of hicases in the AdvoCATE Assurance Case Editor and prove the correspondence between the two. Finally, we suggest areas of future enhancement, both theoretically and practically.

Denney, Ewen W.↗
NASA NTRS2009

Deriving Safety Cases for the Formal Safety Certification of Automatically Generated Code

We present an approach to systematically derive safety cases for automatically generated code from information collected during a formal, Hoare-style safety certification of the code. This safety case makes explicit the formal and informal reasoning principles, and reveals the top-level assumptions and external dependencies that must be taken into account; however, the evidence still comes from the formal safety proofs. It uses a generic goal-based argument that is instantiated with respect to the certified safety property (i.e., safety claims) and the program. This will be combined with a complementary safety case that argues the safety of the framework itself, in particular the correctness of the Hoare rules with respect to the safety property and the trustworthiness of the certification system and its individual components. Keywords: Automated code generation, Hoare logic, formal code certification, safety case, Goal Structuring Notation.

Basir, Nurlida↗
NASA NTRS2014

An Extended Case Study Methoology for Investigating Influence of Cultural, Organizational, and Automation Factors on Human-Automation Trust

This paper discusses a case study that examined the influence of cultural, organizational and automation capability upon human trust in, and reliance on, automation. In particular, this paper focuses on the design and application of an extended case study methodology, and on the foundational lessons revealed by it. Experimental test pilots involved in the research and development of the US Air Forces newly developed Automatic Ground Collision Avoidance System served as the context for this examination. An eclectic, multi-pronged approach was designed to conduct this case study, and proved effective in addressing the challenges associated with the cases politically sensitive and military environment. Key results indicate that the system design was in alignment with pilot culture and organizational mission, indicating the potential for appropriate trust development in operational pilots. These include the low-vulnerabilityhigh risk nature of the pilot profession, automation transparency and suspicion, system reputation, and the setup of and communications among organizations involved in the system development.

automation suspicion↗
NASA NTRS2014

Selection of Thermal Worst-Case Orbits via Modified Efficient Global Optimization

Efficient Global Optimization (EGO) was used to select orbits with worst-case hot and cold thermal environments for the Stratospheric Aerosol and Gas Experiment (SAGE) III. The SAGE III system thermal model changed substantially since the previous selection of worst-case orbits (which did not use the EGO method), so the selections were revised to ensure the worst cases are being captured. The EGO method consists of first conducting an initial set of parametric runs, generated with a space-filling Design of Experiments (DoE) method, then fitting a surrogate model to the data and searching for points of maximum Expected Improvement (EI) to conduct additional runs. The general EGO method was modified by using a multi-start optimizer to identify multiple new test points at each iteration. This modification facilitates parallel computing and decreases the burden of user interaction when the optimizer code is not integrated with the model. Thermal worst-case orbits for SAGE III were successfully identified and shown by direct comparison to be more severe than those identified in the previous selection. The EGO method is a useful tool for this application and can result in computational savings if the initial Design of Experiments (DoE) is selected appropriately.

Moeller, Timothy M.↗
NASA NTRS2014

Influence of Cultural, Organizational, and Automation Capability on Human Automation Trust: A Case Study of Auto-GCAS Experimental Test Pilots

This paper discusses a case study that examined the influence of cultural, organizational and automation capability upon human trust in, and reliance on, automation. In particular, this paper focuses on the design and application of an extended case study methodology, and on the foundational lessons revealed by it. Experimental test pilots involved in the research and development of the US Air Force's newly developed Automatic Ground Collision Avoidance System served as the context for this examination. An eclectic, multi-pronged approach was designed to conduct this case study, and proved effective in addressing the challenges associated with the case's politically sensitive and military environment. Key results indicate that the system design was in alignment with pilot culture and organizational mission, indicating the potential for appropriate trust development in operational pilots. These include the low-vulnerability/ high risk nature of the pilot profession, automation transparency and suspicion, system reputation, and the setup of and communications among organizations involved in the system development.

trust↗