Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “corrective actions”

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 NTRS2011

Developing NDE Techniques for Large Cryogenic Tanks

The Shuttle Program requires very large cryogenic ground storage tanks in which to store liquid oxygen and hydrogen. The existing Pads A and B Launch Complex-39 tanks, which will be passed onto future launch programs, are 45 years old and have received minimal refurbishment and only external inspections over the years. The majority of the structure is inaccessible without a full system drain of cryogenic liquid and granular insulation in the annular region. It was previously thought that there was a limit to the number of temperature cycles that the tanks could handle due to possible insulation compaction before undergoing a costly and time consuming complete overhaul; therefore the tanks were not drained and performance issues with these tanks, specifically the Pad B liquid hydrogen tank, were accepted. There is a needind an opportunity, as the Shuttle program ends and work to upgrade the launch pads progresses, to develop innovative non-destructive evaluation (NDE) techniques to analyze the current tanks. Techniques are desired that can aid in determining the extent of refurbishment required to keep the tanks in service for another 20+ years. A nondestructive technique would also be a significant aid in acceptance testing of new and refurbished tanks, saving significant time and money, if corrective actions can be taken before cryogen is introduced to the systems.

Parker, Don↗
NASA NTRS2009

Developing NDE Techniques for Large Cryogenic Tanks

The Shuttle and Constellation Programs require very large cryogenic ground storage tanks in which to store liquid oxygen and hydrogen. The existing LC-39 pad tanks, which will be passed onto Constellation, are 40 years old and have received minimal refurbishment or even inspection, because they can only be temperature cycled a few times before being overhauled (a costly operation in both time and dollars). Numerous questions exist on the performance and reliability of these old tanks which could cause a major Program schedule disruption. Consequently, with the passing of the first two tanks to Constellation to occur this year, there is growing awareness that NDE is needed to detect problems early in these tanks so that corrective actions can be scheduled when least disruptive. Time series thermal images of two sides of the Pad B LH2 tank have been taken over multiple days to demonstrate the effects of environmental conditions to the solar heating of the tank and therefore the effectiveness of thermal imaging.

Parker, Don↗
NASA NTRS2011

Avionics Box Cold Plate Damage Prevention

Over the years there have been several occurrences of damage to Space Shuttle Orbiter cold plates during removal and replacement of avionics boxes. Thus a process improvement team was put together to determine ways to prevent these kinds of damage. From this effort there were many solutions including, protective covers, training, and improved operations instructions. The focus of this paper is to explain the cold plate damage problem and the corrective actions for preventing future damage to aerospace avionics cold plate designs.

Stambolian, Damon↗
NASA NTRS2011

Performance of the Extravehicular Mobility Unit (EMU) Airlock Coolant Loop Remediation (A/L CLR) Hardware - Final

An EMU water processing kit (Airlock Coolant Loop Recovery -- A/L CLR) was developed as a corrective action to Extravehicular Mobility Unit (EMU) coolant flow disruptions experienced on the International Space Station (ISS) in May of 2004 and thereafter. A conservative duty cycle and set of use parameters for A/L CLR use and component life were initially developed and implemented based on prior analysis results and analytical modeling. Several initiatives were undertaken to optimize the duty cycle and use parameters of the hardware. Examination of post-flight samples and EMU Coolant Loop hardware provided invaluable information on the performance of the A/L CLR and has allowed for an optimization of the process. The intent of this paper is to detail the evolution of the A/L CLR hardware, efforts to optimize the duty cycle and use parameters, and the final recommendations for implementation in the post-Shuttle retirement era.

Steele, John W.↗
NASA NTRS2011

Agent-Based Simulations for Project Management

Currently, the most common approach used in project planning tools is the Critical Path Method (CPM). While this method was a great improvement over the basic Gantt chart technique being used at the time, it now suffers from three primary flaws: (1) task duration is an input, (2) productivity impacts are not considered , and (3) management corrective actions are not included. Today, computers have exceptional computational power to handle complex simulations of task e)(eculion and project management activities (e.g ., dynamically changing the number of resources assigned to a task when it is behind schedule). Through research under a Department of Defense contract, the author and the ViaSim team have developed a project simulation tool that enables more realistic cost and schedule estimates by using a resource-based model that literally turns the current duration-based CPM approach "on its head." The approach represents a fundamental paradigm shift in estimating projects, managing schedules, and reducing risk through innovative predictive techniques.

White, J. Chris↗
NASA NTRS2011

Putting the Power of Configuration in the Hands of the Users

Goal was to reduce the overall cost of human space flight while maintaining the most demanding standards for safety and mission success. In support of this goal, a project team was chartered to replace 18 legacy Space Shuttle nonconformance processes and systems with one fully integrated system Problem Reporting and Corrective Action (PRACA) processes provide a closed-loop system for the identification, disposition, resolution, closure, and reporting of all Space Shuttle hardware/software problems PRACA processes are integrated throughout the Space Shuttle organizational processes and are critical to assuring a safe and successful program Primary Project Objectives Develop a fully integrated system that provides an automated workflow with electronic signatures Support multiple NASA programs and contracts with a single "system" architecture Define standard processes, implement best practices, and minimize process variations

Al-Shihabi, Mary-Jo↗
NASA NTRS2005

Wipes, Coatings, and Patches for Detecting Hydrazines

Three color-indicating devices have been conceived as simple, rapid, inexpensive means of detecting hazardous liquid and gaseous substances in settings in which safety is of paramount concern and it would be too time-consuming or otherwise impractical to perform detection by use of such instruments as mass spectrometers. More specifically, these devices are designed for detecting hypergolic fuels (in particular, hydrazines) and hypergolic oxidizers in spacecraft settings, where occasional leakage of these substances in liquid or vapor form occurs and it is imperative to take early corrective action to minimize adverse health effects. With suitable redesign, including reformulation of their color indicator chemicals, these devices could be adapted to detection of other hazardous substances in terrestrial settings (e.g., industrial and military ones). One of the devices is a pad of a commercially available absorbent material doped with a color indicator. The absorbent material is made from 70 percent polyester and 30 percent nylon and can absorb about eight times its own weight of liquid. The color indicator is a mixture of conventional pH color indicator chemicals. Hydrazine and monomethyl hydrazine, which are basic, cause the color indicator to turn green. In the original intended application, the pad is wiped on a space suit that is suspected of having been exposed to leaking monomethyl hydrazine during a space walk, before the wearer returns to the interior of the spacecraft. If the wiped surface is contaminated with hydrazine, the pad turns green. In addition, the pad absorbs hydrazine from the wiped surface, thereby reducing or eliminating the hazard. Used pads, including ones that show contamination by hydrazine, can be stored in a sealed plastic bag for subsequent disposal. The second device, which has been proposed but not yet developed, would comprise a color indicator material in the form of either a coating on a space suit (or other protective garment) or a coating on a sheet that could be easily attached to and detached from the protective garment. The coating material would be a hydrogel doped with a suitable pH indicator. The hydrogel would also serve to maintain a level of moisture needed to support the chemical reaction mentioned in the next sentence. In addition to changing color to indicate the presence of any hypergolic fuel (which is basic) or hypergolic oxidizer (which is acidic) that might splash on the space suit, the pH indicator would also react with the hypergolic fuel or oxidizer and thereby bind it. The third device is a color dosimeter for detecting hydrazine liquid or vapor coming from microscopic leaks. This device is designed to satisfy several requirements specific to its original intended use in the auxiliary power unit of the space shuttle. These requirements include stability under vacuum, stability at moderate temperature, fast and irreversible change in color upon exposure to hydrazine, and visibility of the color change through polyimide tape.

Young, Rebecca↗
NASA NTRS2004

Simple Systems for Detecting Spacecraft Meteoroid Punctures

A report describes proposed systems to be installed in spacecraft to detect punctures by impinging meteoroids or debris. Relative to other systems that have been used for this purpose, the proposed systems would be simpler and more adaptable, and would demand less of astronauts attention and of spacecraft power and computing resources. The proposed systems would include a thin, hollow, hermetically sealed panel containing an inert fluid at a pressure above the spacecraft cabin pressure. A transducer would monitor the pressure in the panel. It is assumed that an impinging object that punctures the cabin at the location of the panel would also puncture the panel. Because the volume of the panel would be much smaller than that of the cabin, the panel would lose its elevated pressure much faster than the cabin would lose its lower pressure. The transducer would convert the rapid pressure drop to an electrical signal that could trigger an alarm. Hence, the system would provide an immediate indication of the approximate location of a small impact leak, possibly in time to take corrective action before a large loss of cabin pressure could occur.

Hall, Stephen B.↗
NASA NTRS2003

Prognostics Methodology for Complex Systems

An automatic method to schedule maintenance and repair of complex systems is produced based on a computational structure called the Informed Maintenance Grid (IMG). This method provides solutions to the two fundamental problems in autonomic logistics: (1) unambiguous detection of deterioration or impending loss of function and (2) determination of the time remaining to perform maintenance or other corrective action based upon information from the system. The IMG provides a health determination over the medium-to-longterm operation of the system, from one or more days to years of study. The IMG is especially applicable to spacecraft and both piloted and autonomous aircraft, or industrial control processes.

Gulati, Sandeep↗
NASA NTRS2003

Oxygen-Partial-Pressure Sensor for Aircraft Oxygen Mask

A device that generates an alarm when the partial pressure of oxygen decreases to less than a preset level has been developed to help prevent hypoxia in a pilot or other crewmember of a military or other high-performance aircraft. Loss of oxygen partial pressure can be caused by poor fit of the mask or failure of a hose or other component of an oxygen distribution system. The deleterious physical and mental effects of hypoxia cause the loss of a military aircraft and crew every few years. The device is installed in the crewmember s oxygen mask and is powered via communication wiring already present in all such oxygen masks. The device (see figure) includes an electrochemical sensor, the output potential of which is proportional to the partial pressure of oxygen. The output of the sensor is amplified and fed to the input of a comparator circuit. A reference potential that corresponds to the amplified sensor output at the alarm oxygen-partial-pressure level is fed to the second input of the comparator. When the sensed partial pressure of oxygen falls below the minimum acceptable level, the output of the comparator goes from the low state (a few millivolts) to the high state (near the supply potential, which is typically 6.8 V for microphone power). The switching of the comparator output to the high state triggers a tactile alarm in the form of a vibration in the mask, generated by a small 1.3-Vdc pager motor spinning an eccentric mass at a rate between 8,000 and 10,000 rpm. The sensation of the mask vibrating against the crewmember s nose is very effective at alerting the crewmember, who may already be groggy from hypoxia and is immersed in an environment that is saturated with visual cues and sounds. Indeed, the sensation is one of rudeness, but such rudeness could be what is needed to stimulate the crewmember to take corrective action in a life-threatening situation.

Kelly, Mark↗
NASA NTRS2003

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗
NASA NTRS2011

Detecting Abnormal Machine Characteristics in Cloud Infrastructures

In the cloud computing environment resources are accessed as services rather than as a product. Monitoring this system for performance is crucial because of typical pay-peruse packages bought by the users for their jobs. With the huge number of machines currently in the cloud system, it is often extremely difficult for system administrators to keep track of all machines using distributed monitoring programs such as Ganglia1 which lacks system health assessment and summarization capabilities. To overcome this problem, we propose a technique for automated anomaly detection using machine performance data in the cloud. Our algorithm is entirely distributed and runs locally on each computing machine on the cloud in order to rank the machines in order of their anomalous behavior for given jobs. There is no need to centralize any of the performance data for the analysis and at the end of the analysis, our algorithm generates error reports, thereby allowing the system administrators to take corrective actions. Experiments performed on real data sets collected for different jobs validate the fact that our algorithm has a low overhead for tracking anomalous machines in a cloud infrastructure.

Bhaduri, Kanishka↗
NASA NTRS2011

Solid Rocket Booster (SRB) - Evolution and Lessons Learned During the Shuttle Program

The Solid Rocket Booster (SRB) element integrates all the subsystems needed for ascent flight, entry, and recovery of the combined Booster and Motor system. These include the structures, avionics, thrust vector control, pyrotechnic, range safety, deceleration, thermal protection, and retrieval systems. This represents the only human-rated, recoverable and refurbishable solid rocket ever developed and flown. Challenges included subsystem integration, thermal environments and severe loads (including water impact), sometimes resulting in hardware attrition. Several of the subsystems evolved during the program through design changes. These included the thermal protection system, range safety system, parachute/recovery system, and others. Obsolescence issues occasionally required component recertification. Because the system was recovered, the SRB was ideal for data and imagery acquisition, which proved essential for understanding loads and system response. The three main parachutes that lower the SRBs to the ocean are the largest parachutes ever designed, and the SRBs are the largest structures ever to be lowered by parachutes. SRB recovery from the ocean was a unique process and represented a significant operational challenge; requiring personnel, facilities, transportation, and ground support equipment. The SRB element achieved reliability via extensive system testing and checkout, redundancy management, and a thorough postflight assessment process. Assembly and integration of the booster subsystems was a unique process and acceptance testing of reused hardware components was required for each build. Extensive testing was done to assure hardware functionality at each level of stage integration. Because the booster element is recoverable, subsystems were available for inspection and testing postflight, unique to the Shuttle launch vehicle. Problems were noted and corrective actions were implemented as needed. The postflight assessment process was quite detailed and a significant portion of flight operations. The SRBs provided fully redundant critical systems including thrust vector control, mission critical pyrotechnics, avionics, and parachute recovery system. The design intent was to lift off with full redundancy. On occasion, the redundancy management scheme was needed during flight operations. This paper describes some of the design challenges, how the design evolved with time, and key areas where hardware reusability contributed to improved system level understanding.

Kanner, Howard S.↗
NASA NTRS2011

Solid Rocket Booster (SRB) Flight System Integration at Its Best

The Solid Rocket Booster (SRB) element integrates all the subsystems needed for ascent flight, entry, and recovery of the combined Booster and Motor system. These include the structures, avionics, thrust vector control, pyrotechnic, range safety, deceleration, thermal protection, and retrieval systems. This represents the only human-rated, recoverable and refurbishable solid rocket ever developed and flown. Challenges included subsystem integration, thermal environments and severe loads (including water impact), sometimes resulting in hardware attrition. Several of the subsystems evolved during the program through design changes. These included the thermal protection system, range safety system, parachute/recovery system, and others. Because the system was recovered, the SRB was ideal for data and imagery acquisition, which proved essential for understanding loads, environments and system response. The three main parachutes that lower the SRBs to the ocean are the largest parachutes ever designed, and the SRBs are the largest structures ever to be lowered by parachutes. SRB recovery from the ocean was a unique process and represented a significant operational challenge; requiring personnel, facilities, transportation, and ground support equipment. The SRB element achieved reliability via extensive system testing and checkout, redundancy management, and a thorough postflight assessment process. However, the in-flight data and postflight assessment process revealed the hardware was affected much more strongly than originally anticipated. Assembly and integration of the booster subsystems required acceptance testing of reused hardware components for each build. Extensive testing was done to assure hardware functionality at each level of stage integration. Because the booster element is recoverable, subsystems were available for inspection and testing postflight, unique to the Shuttle launch vehicle. Problems were noted and corrective actions were implemented as needed. The postflight assessment process was quite detailed and a significant portion of flight operations. The SRBs provided fully redundant critical systems including thrust vector control, mission critical pyrotechnics, avionics, and parachute recovery system. The design intent was to lift off with full redundancy. On occasion, the redundancy management scheme was needed during flight operations. This paper describes some of the design challenges and technical issues, how the design evolved with time, and key areas where hardware reusability contributed to improved system level understanding.

Wood, T. David↗
NASA NTRS2011

NASA Accident Precursor Analysis Handbook, Version 1.0

Catastrophic accidents are usually preceded by precursory events that, although observable, are not recognized as harbingers of a tragedy until after the fact. In the nuclear industry, the Three Mile Island accident was preceded by at least two events portending the potential for severe consequences from an underappreciated causal mechanism. Anomalies whose failure mechanisms were integral to the losses of Space Transportation Systems (STS) Challenger and Columbia had been occurring within the STS fleet prior to those accidents. Both the Rogers Commission Report and the Columbia Accident Investigation Board report found that processes in place at the time did not respond to the prior anomalies in a way that shed light on their true risk implications. This includes the concern that, in the words of the NASA Aerospace Safety Advisory Panel (ASAP), "no process addresses the need to update a hazard analysis when anomalies occur" At a broader level, the ASAP noted in 2007 that NASA "could better gauge the likelihood of losses by developing leading indicators, rather than continue to depend on lagging indicators". These observations suggest a need to revalidate prior assumptions and conclusions of existing safety (and reliability) analyses, as well as to consider the potential for previously unrecognized accident scenarios, when unexpected or otherwise undesired behaviors of the system are observed. This need is also discussed in NASA's system safety handbook, which advocates a view of safety assurance as driving a program to take steps that are necessary to establish and maintain a valid and credible argument for the safety of its missions. It is the premise of this handbook that making cases for safety more experience-based allows NASA to be better informed about the safety performance of its systems, and will ultimately help it to manage safety in a more effective manner. The APA process described in this handbook provides a systematic means of analyzing candidate accident precursors by evaluating anomaly occurrences for their system safety implications and, through both analytical and deliberative methods used to project to other circumstances, identifying those that portend more serious consequences to come if effective corrective action is not taken. APA builds upon existing safety analysis processes currently in practice within NASA, leveraging their results to provide an improved understanding of overall system risk. As such, APA represents an important dimension of safety evaluation; as operational experience is acquired, precursor information is generated such that it can be fed back into system safety analyses to risk-inform safety improvements. Importantly, APA utilizes anomaly data to predict risk whereas standard reliability and PRA approaches utilize failure data which often is limited and rare.

Groen, Frank↗
NASA NTRS2011

EMU Lessons Learned Database

As manned space exploration takes on the task of traveling beyond low Earth orbit, many problems arise that must be solved in order to make the journey possible. One major task is protecting humans from the harsh space environment. The current method of protecting astronauts during Extravehicular Activity (EVA) is through use of the specially designed Extravehicular Mobility Unit (EMU). As more rigorous EVA conditions need to be endured at new destinations, the suit will need to be tailored and improved in order to accommodate the astronaut. The Objective behind the EMU Lessons Learned Database(LLD) is to be able to create a tool which will assist in the development of next-generation EMUs, along with maintenance and improvement of the current EMU, by compiling data from Failure Investigation and Analysis Reports (FIARs) which have information on past suit failures. FIARs use a system of codes that give more information on the aspects of the failure, but if one is unfamiliar with the EMU they will be unable to decipher the information. A goal of the EMU LLD is to not only compile the information, but to present it in a user-friendly, organized, searchable database accessible to all familiarity levels with the EMU; both newcomers and veterans alike. The EMU LLD originally started as an Excel database, which allowed easy navigation and analysis of the data through pivot charts. Creating an entry requires access to the Problem Reporting And Corrective Action database (PRACA), which contains the original FIAR data for all hardware. FIAR data are then transferred to, defined, and formatted in the LLD. Work is being done to create a web-based version of the LLD in order to increase accessibility to all of Johnson Space Center (JSC), which includes converting entries from Excel to the HTML format. FIARs related to the EMU have been completed in the Excel version, and now focus has shifted to expanding FIAR data in the LLD to include EVA tools and support hardware such as the Pistol Grip Tool (PGT) and the Battery Charger Module (BCM), while adding any recently closed EMU-related FIARs.

Matthews, Kevin M., Jr.↗
NASA NTRS2012

STS-133/ET-137 Tanking Test Photogrammetry Assessment

Following the launch scrub of Space Shuttle mission STS-133 on November 5, 2010, an anomalous condition of cracked and raised thermal protection system (TPS) foam was observed on the External Tank (ET). Subsequent dissection of the affected TPS region revealed cracks in the feet of two Intertank (IT) metallic stringers. An extensive investigation into the cause(s) and corrective action(s) for the cracked stringers was initiated, involving a wide array of material and structural tests and nondestructive evaluations, with the intent to culminate into the development of flight rational. One such structural test was the instrumented tanking test performed on December 17, 2010. The tanking test incorporated two three-dimensional optical displacement measurement systems to measure full-field outer surface displacements of the TPS surrounding the affected region that contained the stringer cracks. The results showed that the radial displacement and rotation of the liquid oxygen (LO2) tank flange changed significantly as the fluid level of the LO2 approached and passed the LO2 tank flange.

Oliver, Stanley T.↗
NASA NTRS2012

Onboard Sensor Data Qualification in Human-Rated Launch Vehicles

The avionics system software for human-rated launch vehicles requires an implementation approach that is robust to failures, especially the failure of sensors used to monitor vehicle conditions that might result in an abort determination. Sensor measurements provide the basis for operational decisions on human-rated launch vehicles. This data is often used to assess the health of system or subsystem components, to identify failures, and to take corrective action. An incorrect conclusion and/or response may result if the sensor itself provides faulty data, or if the data provided by the sensor has been corrupted. Operational decisions based on faulty sensor data have the potential to be catastrophic, resulting in loss of mission or loss of crew. To prevent these later situations from occurring, a Modular Architecture and Generalized Methodology for Sensor Data Qualification in Human-rated Launch Vehicles has been developed. Sensor Data Qualification (SDQ) is a set of algorithms that can be implemented in onboard flight software, and can be used to qualify data obtained from flight-critical sensors prior to the data being used by other flight software algorithms. Qualified data has been analyzed by SDQ and is determined to be a true representation of the sensed system state; that is, the sensor data is determined not to be corrupted by sensor faults or signal transmission faults. Sensor data can become corrupted by faults at any point in the signal path between the sensor and the flight computer. Qualifying the sensor data has the benefit of ensuring that erroneous data is identified and flagged before otherwise being used for operational decisions, thus increasing confidence in the response of the other flight software processes using the qualified data, and decreasing the probability of false alarms or missed detections.

Wong, Edmond↗