Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “hardware failure”

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 883 records · Page 49

Full-Scaled Advanced Systems Testbed: Ensuring Success of Adaptive Control Research Through Project Lifecycle Risk Mitigation

The National Aeronautics and Space Administration's Dryden Flight Research Center completed flight testing of adaptive controls research on the Full-Scale Advance Systems Testbed (FAST) in January of 2011. The research addressed technical challenges involved with reducing risk in an increasingly complex and dynamic national airspace. Specific challenges lie with the development of validated, multidisciplinary, integrated aircraft control design tools and techniques to enable safe flight in the presence of adverse conditions such as structural damage, control surface failures, or aerodynamic upsets. The testbed is an F-18 aircraft serving as a full-scale vehicle to test and validate adaptive flight control research and lends a significant confidence to the development, maturation, and acceptance process of incorporating adaptive control laws into follow-on research and the operational environment. The experimental systems integrated into FAST were designed to allow for flexible yet safe flight test evaluation and validation of modern adaptive control technologies and revolve around two major hardware upgrades: the modification of Production Support Flight Control Computers (PSFCC) and integration of two, fourth-generation Airborne Research Test Systems (ARTS). Post-hardware integration verification and validation provided the foundation for safe flight test of Nonlinear Dynamic Inversion and Model Reference Aircraft Control adaptive control law experiments. To ensure success of flight in terms of cost, schedule, and test results, emphasis on risk management was incorporated into early stages of design and flight test planning and continued through the execution of each flight test mission. Specific consideration was made to incorporate safety features within the hardware and software to alleviate user demands as well as into test processes and training to reduce human factor impacts to safe and successful flight test. This paper describes the research configuration, experiment functionality, overall risk mitigation, flight test approach and results, and lessons learned of adaptive controls research of the Full-Scale Advanced Systems Testbed.

Pavlock, Kate M.↗

Flexible Peripheral Component Interconnect Input/Output Card

The Flexible Peripheral Component Interconnect (PCI) Input/Output (I/O) Card is an innovative circuit board that provides functionality to interface between a variety of devices. It supports user-defined interrupts for interface synchronization, tracks system faults and failures, and includes checksum and parity evaluation of interface data. The card supports up to 16 channels of high-speed, half-duplex, low-voltage digital signaling (LVDS) serial data, and can interface combinations of serial and parallel devices. Placement of a processor within the field programmable gate array (FPGA) controls an embedded application with links to host memory over its PCI bus. The FPGA also provides protocol stacking and quick digital signal processor (DSP) functions to improve host performance. Hardware timers, counters, state machines, and other glue logic support interface communications. The Flexible PCI I/O Card provides an interface for a variety of dissimilar computer systems, featuring direct memory access functionality. The card has the following attributes: 8/16/32-bit, 33-MHz PCI r2.2 compliance, Configurable for universal 3.3V/5V interface slots, PCI interface based on PLX Technology's PCI9056 ASIC, General-use 512K 16 SDRAM memory, General-use 1M 16 Flash memory, FPGA with 3K to 56K logical cells with embedded 27K to 198K bits RAM, I/O interface: 32-channel LVDS differential transceivers configured in eight, 4-bit banks; signaling rates to 200 MHz per channel, Common SCSI-3, 68-pin interface connector.

Bigelow, Kirk K.↗

Composite Overwrap Pressure Vessels: Mechanics and Stress Rupture Lifing Philosophy

The NASA Engineering and Safety Center (NESC) has been conducting an independent technical assessment to address safety concerns related to the known stress rupture failure mode of filament wound pressure vessels in use on Shuttle and the International Space Station. The Shuttle's Kevlar-49 fiber overwrapped tanks are of particular concern due to their long usage and the poorly understood stress rupture process in Kevlar-49 filaments. Existing long term data show that the rupture process is a function of stress, temperature and time. However due to the presence of load sharing liners and the complex manufacturing procedures, the state of actual fiber stress in flight hardware and test articles is not clearly known. Indeed non-conservative life predictions have been made where stress rupture data and lifing procedures have ignored the contribution of the liner in favor of applied pressure as the controlling load parameter. With the aid of analytical and finite element results, this paper examines the fundamental mechanical response of composite overwrapped pressure vessels including the influence of elastic-plastic liners and degraded/creeping overwrap properties. Graphical methods are presented describing the non-linear relationship of applied pressure to Kevlar-49 fiber stress/strain during manufacturing, operations and burst loadings. These are applied to experimental measurements made on a variety of vessel systems to demonstrate the correct calibration of fiber stress as a function of pressure. Applying this analysis to the actual qualification burst data for Shuttle flight hardware revealed that the nominal fiber stress at burst was in some cases 23% lower than what had previously been used to predict stress rupture life. These results motivate a detailed discussion of the appropriate stress rupture lifing philosophy for COPVs including the correct transference of stress rupture life data between dissimilar vessels and test articles.

Thesken, John C.↗

NASA's In-Space Manufacturing Project: Development of a Multimaterial, Multiprocess Fabrication Laboratory for the International Space Station

NASA's long term goal is to send humans to Mars. Over the next two decades, NASA will work with private industry to develop and demonstrate the technologies and capabilities needed to support exploration of the red planet by humans and ensure their safe return to earth. To accomplish this goal, NASA is employing a capability driven approach to its human spaceflight strategy. This approach will develop a suite of evolving capabilities which provide specific functions to solve exploration challenges. One challenge that is critical to sustainable and safer exploration is the ability to manufacture and recycle materials in space. This paper provides an overview of NASA's in-space manufacturing project, its past and current activities, and how technologies under development will ultimately culminate in a multimaterial, multiprocess fabrication laboratory ('FabLab') to be deployed on the International Space Station in the early 2020s. ISM is a critical capability for the long endurance missions NASA seeks to undertake in the coming decades. An unanticipated failure that can be adapted for in low earth orbit may result in a loss of mission in transit to Mars. In order to have a suite of functional ISM capabilities that are compatible with NASA's exploration timeline, ISM must be equipped with the resources necessary to develop these technologies and deploy them for testing prior to the scheduled de-orbit of ISS in 2024. The paper will discuss the phased approach to FabLab development, desired capabilities, and requirements for the hardware. The FabLab will move NASA and private industry significantly closer to changing historical paradigms for human spaceflight where all materials used in space are launched from earth. While the FabLab will be tested on ISS, the system is ultimately intended for use in a deep space habitat or transit vehicle.

Prater, T.↗

Software Reliability 2002

In FY01 we learned that hardware reliability models need substantial changes to account for differences in software, thus making software reliability measurements more effective, accurate, and easier to apply. These reliability models are generally based on familiar distributions or parametric methods. An obvious question is 'What new statistical and probability models can be developed using non-parametric and distribution-free methods instead of the traditional parametric method?" Two approaches to software reliability engineering appear somewhat promising. The first study, begin in FY01, is based in hardware reliability, a very well established science that has many aspects that can be applied to software. This research effort has investigated mathematical aspects of hardware reliability and has identified those applicable to software. Currently the research effort is applying and testing these approaches to software reliability measurement, These parametric models require much project data that may be difficult to apply and interpret. Projects at GSFC are often complex in both technology and schedules. Assessing and estimating reliability of the final system is extremely difficult when various subsystems are tested and completed long before others. Parametric and distribution free techniques may offer a new and accurate way of modeling failure time and other project data to provide earlier and more accurate estimates of system reliability.

Wallace, Dolores R.↗

Structural Requirements for the Space Propulsion Engine Systems

In January 2004, the National Aeronautics and Space Administration (NASA) was given a vision for Space Exploration by President Bush, setting our sight on a bold new path to go back to the Moon, then to Mars and beyond. As NASA gets ready to meet the vision set by President Bush, failures are not an option. Reliability of the propulsion engine systems will play an important role in establishing an overall safe and reliable operation of these new space systems. A new standard, NASA-STD-5012, Strength and Life Assessment for Space Propulsion System Engines, has been developed to provide structural requirements for assessment of the propulsion systems engine. This standard is a complement to the current NASA-wide standard NASA-STD-5001, Structural Design and Test Factors of Safety for Spaceflight Hardware, which excluded the requirement for the engine systems (rotatory structures) along with pressure vessels. As developed, this document builds on the heritage of the multiple industrial standards related to strength and life assessment of the structures. For assuring a safe and reliable operation of a product and/or mission, establishing a set of structural assessment requirements is a key ingredient. Hence, a concentrated effort was made to improve the requirements where there are known lessons learned during the design, test, and operation phases of the Space Shuttle Main Engine (SSME) and other engine development programs. Requirements delineated in this standard are also applicable for the reusable and/or human missions. It shall be noted that "reliability of a system cannot be tested and inspected but can only be achieved if it is first designed into a system." Hence, these strength and life assessment requirements for the space propulsion system engines shall be used along with other good engineering practices, requirements, and policies.

Aggarwal, Pravin K.↗

Composite Overwrap Pressure Vessels: Mechanics and Stress Rupture Lifting Philosophy

The NASA Engineering and Safety Center (NESC) has been conducting an independent technical assessment to address safety concerns related to the known stress rupture failure mode of filament wound pressure vessels in use on Shuttle and the International Space Station. The Shuttle s Kevlar-49 (DuPont) fiber overwrapped tanks are of particular concern due to their long usage and the poorly understood stress rupture process in Kevlar-49 filaments. Existing long term data show that the rupture process is a function of stress, temperature and time. However due to the presence of load sharing liners and the complex manufacturing procedures, the state of actual fiber stress in flight hardware and test articles is not clearly known. Indeed nonconservative life predictions have been made where stress rupture data and lifing procedures have ignored the contribution of the liner in favor of applied pressure as the controlling load parameter. With the aid of analytical and finite element results, this paper examines the fundamental mechanical response of composite overwrapped pressure vessels including the influence of elastic plastic liners and degraded/creeping overwrap properties. Graphical methods are presented describing the non-linear relationship of applied pressure to Kevlar-49 fiber stress/strain during manufacturing, operations and burst loadings. These are applied to experimental measurements made on a variety of vessel systems to demonstrate the correct calibration of fiber stress as a function of pressure. Applying this analysis to the actual qualification burst data for Shuttle flight hardware revealed that the nominal fiber stress at burst was in some cases 23 percent lower than what had previously been used to predict stress rupture life. These results motivate a detailed discussion of the appropriate stress rupture lifing philosophy for COPVs including the correct transference of stress rupture life data between dissimilar vessels and test articles.

Thesken, John C.↗

Rocket Cratering in Simulated Lunar and Martian Environments

With NASA's planned return to the moon and possibly with lunar outposts being formed, repeated landings at the same site will be necessary. Understanding rocket plume interaction with lunar and Martian surfaces is of paramount importance in order to safely land and protect hardware surrounding the landing site. This work will report on results of three small experiments intended to explore plume impingement onto lunar and Martian surfaces: Handheld Observation of Scour Holes (HOOSH), Handheld Angle of Repose Measurements of Lunar Simulants (HARMLuS), and Mars Architecture Team study (MATS). The first two experiments were performed during two sorties of reduced gravity flights. HOOSH was designed to investigate crater formation as a function of gravitational level (lunar and Martian gravity). HARMLuS was designed to measure the Angle of Failure (related to the angle of repose) at lunar and Martian gravity. Both experiments have complex findings indicative of the hysteretic behavior of granular materials, especially resulting from reduced gravity. The MATS experiment was designed to investigate the effects of regolith compaction on the granular mechanics of crater formation . In general, the granular mechanics is a much stronger function of compaction than gravitation acceleration. Crater formation is greatly enhanced at reduced gravity (resulting in much larger craters). The angle of failure of the lunar simulants increases with decreasing gravitational acceleration, and occasionally becomes infinite for some compactions at lunar gravity. The angle of failure also increases with increasing compaction. While compaction does play a role in the time development of crater formation, the asymptotic behavior is largely unaffected.

Immer, Christopher↗

A Historical Analysis of Crane Mishaps at Kennedy Space Center

Cranes and hoists are widely used in many areas. Crane accidents and handling mishaps are responsible for injuries, costly equipment damage, and program delays. Most crane accidents are caused by preventable factors. Understanding these factors is critical when designing cranes and preparing lift plans. Analysis of previous accidents provides insight into current recommendations for crane safety. Cranes and hoists are used throughout Kennedy Space Center to lift everything from machine components to critical flight hardware. Unless they are trained crane operators, most NASA employees and contractors do not need to undergo specialized crane training and may not understand the safety issues surrounding the use of cranes and hoists. A single accident with a crane or hoist can injure or kill people, cause severe equipment damage, and delay or terminate a program. Handling mishaps can also have a significant impact on the program. Simple mistakes like bouncing or jarring a load, or moving the crane down when it should go up, can damage fragile flight hardware and cause major delays in processing. Hazardous commodities (high pressure gas, hypergolic propellants, and solid rocket motors) can cause life safety concerns for the workers performing the lifting operations. Most crane accidents are preventable with the correct training and understanding of potential hazards. Designing the crane with human factors taken into account can prevent many accidents. Engineers are also responsible for preparing lift plans where understanding the safety issues can prevent or mitigate potential accidents. Cranes are widely used across many areas of KSC. Failure of these cranes often leads to injury, high damage costs, and significant delays in program objectives. Following a basic set of principles and procedures during design, fabrication, testing, regular use, and maintenance can significantly minimize many of these failures. As the accident analysis shows, load drops are often caused or influenced by human factors. Therefore, proper training and understanding of crane safety throughout the workforce is critical. It is important that the engineers designing the cranes, lift planners preparing the lift plans, operators performing the lifts, and training officers conducting the operator training all understand the problems that can happen with cranes and how to ensure the safety of the workforce and equipment being lifted.

Materials Handling↗

Safer Bridges

Safer bridges are among a number of spinoff benefits from NASA procedures for testing 'cfracture toughness" of a structural part, meaning its ability to -~sis~cracktsh at might cause failure. The New River Bridge in West Virginia, shown under construction, is the world's largest single span bridge. U.S. Steel fracture toughness requirements for such bridges include NASA-developed test procedures. Bridge materials and other metal structures may develop flaws during their service lifetimes. Such flaws can affect the structural integrity of the part. Thus, it is important to know the "fracture toughness" of a structural part, or its ability to resist cracks. NASA has long experience in developing fracture toughness tests for aerospace hardware. Since 1960, NASA-Lewis has worked closely with the American Society for Testing & Materials. Lewis and NASA-funded industrial contractors have made many important contributions to test procedures, now recommended by ASTM, for measuring fracture toughness.

Source record↗

Proof Testing Aluminum and Titanium Thin-Walled Tubes for Aerospace Applications

Proof testing aerospace components aids in verifying the structural integrity of flight hardware. This process is often an important step in the certification process for critical parts. Though proof testing is a common practice at NASA and in industry, there is often a need to understand better the effectiveness of proof testing pressure systems discovering cracklike flaws or defects. Often proof tests are used in requirements and in practice as technical rationale for screening critical defects in a part in lieu of performing a non-destructive inspection. The intent of this work is to define proof test failure envelopes for thin-walled tubes composed of two materials: aluminum and titanium. Both materials are common in aerospace thin-walled tubing applications which is why these were the materials chosen for this study. The fracture mechanics software NASGRO was used to perform a parametric study on the effect of defects in thin-walled tubes subjected to proof testing. For both materials, the parameters varied in the NASGRO analyses were aspect ratio, proof test pressure, thickness, diameter, and flaw multiplier. With each case defined as a through crack or failure, the results were then pulled into MATLAB in order to parse through the data and produce failure envelope plots. Failure envelopes were created by meshing a surface in between the minimum proof pressure failing data points. As expected, based on material properties, the plots indicated the aluminum material would fail at much lower proof tests than the titanium. The parametric data and failure envelopes may be used as general qualitative insight on the effectiveness of proof testing thin-walled tubes of similar alloys.

Leah B Davis↗

Development of an Expert System for Representing Procedural Knowledge

A high level of automation is of paramount importance in most space operations. It is critical for unmanned missions and greatly increases the effectiveness of manned missions. However, although many functions can be automated by using advanced engineering techniques, others require complex reasoning, sensing, and manipulatory capabilities that go beyond this technology. Automation of fault diagnosis and malfunction handling is a case in point. The military have long been interested in this problem, and have developed automatic test equipment to aid in the maintenance of complex military hardware. These systems are all based on conventional software and engineering techniques. However, the effectiveness of such test equipment is severely limited. The equipment is inflexible and unresponsive to the skill level of the technicians using it. The diagnostic procedures cannot be matched to the exigencies of the current situation nor can they cope with reconfiguration or modification of the items under test. The diagnosis cannot be guided by useful advice from technicians and, when a fault cannot be isolated, no explanation is given as to the cause of failure. Because these systems perform a prescribed sequence of tests, they cannot utilize knowledge of a particular situation to focus attention on more likely trouble spots. Consequently, real-time performance is highly unsatisfactory. Furthermore, the cost of developing test software is substantial and time to maturation is excessive. Significant advances in artificial intelligence (AI) have recently led to the development of powerful and flexible reasoning systems, known as expert or knowledge-based systems. We have devised a powerful and theoretically sound scheme for representing and reasoning about procedural knowledge.

Georgeff, Michael P.↗

AEA Cell-Bypass-Switch Activation: An Update

The objectives of this project included the following: (1) verify the performance of AEA cell bypass protection device (CBPD) under simulated EOS-Aqua/Aura flight hardware configuration; (2) assess the safety of the hardware under an inadvertent firing of CBPD switch, as well as the closing of CBPD; and (3) confirm that the mode of operation of CBPD switch is the formation of a continuous low impedance path (a homogeneous low melting point alloy). The nominal performance of AEA CBPD under flight operating conditions (vacuum except zero-G, and high impedance cell) has been demonstrated. There is no evidence of cell rupture or excessive heat production during or after CBPD switch activation under simulated high cell impedance (open-circuit cell failure mode). The formation of a continuous low impedance path (a homogeneous low melting point alloy) has been confirmed.

Keys, Denney↗

Copilot 3

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enables monitoring these systems in runtime, to detect property violations early and limit their potential consequences. The introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. This paper presents Copilot 3, a runtime verification framework for real-time embedded systems. Copilot monitors are written in a compositional, stream-based language with support for a variety of Temporal Logics (TL), which results in robust, high-level specifications that are easier to understand than their traditional counterparts. The framework translates monitor specifications into C code with static memory requirements, which can be compiled to run on embedded hardware. This paper presents version 3 of the Copilot language, demonstrates its suitability with a number of examples, and discusses its use in larger applications. Additionally, it describes the framework?s architecture, its implementation as a Domain Specific Language (DSL) embedded in Haskell, and the progress of the project over the years.

Ivan Perez↗

Interpretation of Space Shuttle telemetry

This paper describes the Payload Deployment and Retrieval System (PDRS) Failure Analysis and Diagnosis problem, our planned use of an expert system employing the C Language Integrated Production System (CLIPS) language to solve it, and our progress to date. In addition, it will address the importance of the overall design within the context of automation in the RTDS architecture, the methodology used, and the validation approach taken. The Decision Support System will evolve as a modularized rule-based system programmed in the CLIPS expert system language. Each of five modules represents a subsystem of the RMS and includes the positioning and retention hardware (MPM/MRL), the Display & Control panel (D8C), the Arm Based Electronics (ABE), the End Effector (EE), and the Orbiter to RMS data interface unit (MCIU). The MPM/MRL subsystem was chosen as the target of a prototype development and its knowledge base is completed. Testing and validation of the software is conducted by experienced mission controllers. The initial design stages for the D&C panel module are beginning.

Culp, Donald R.↗

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy M. Mclaughlin↗

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy McLaughlin↗

Evaluation of Anomaly Detection Capability for Ground-Based Pre-Launch Shuttle Operations

This chapter will provide a thorough end-to-end description of the process for evaluation of three different data-driven algorithms for anomaly detection to select the best candidate for deployment as part of a suite of IVHM (Integrated Vehicle Health Management) technologies. These algorithms were deemed to be sufficiently mature enough to be considered viable candidates for deployment in support of the maiden launch of Ares I-X, the successor to the Space Shuttle for NASA's Constellation program. Data-driven algorithms are just one of three different types being deployed. The other two types of algorithms being deployed include a "nile-based" expert system, and a "model-based" system. Within these two categories, the deployable candidates have already been selected based upon qualitative factors such as flight heritage. For the rule-based system, SHINE (Spacecraft High-speed Inference Engine) has been selected for deployment, which is a component of BEAM (Beacon-based Exception Analysis for Multimissions), a patented technology developed at NASA's JPL (Jet Propulsion Laboratory) and serves to aid in the management and identification of operational modes. For the "model-based" system, a commercially available package developed by QSI (Qualtech Systems, Inc.), TEAMS (Testability Engineering and Maintenance System) has been selected for deployment to aid in diagnosis. In the context of this particular deployment, distinctions among the use of the terms "data-driven," "rule-based," and "model-based," can be found in. Although there are three different categories of algorithms that have been selected for deployment, our main focus in this chapter will be on the evaluation of three candidates for data-driven anomaly detection. These algorithms will be evaluated upon their capability for robustly detecting incipient faults or failures in the ground-based phase of pre-launch space shuttle operations, rather than based oil heritage as performed in previous studies. Robust detection will allow for the achievement of pre-specified minimum false alarm and/or missed detection rates in the selection of alert thresholds. All algorithms will also be optimized with respect to an aggregation of these same criteria. Our study relies upon the use of Shuttle data to act as was a proxy for and in preparation for application to Ares I-X data, which uses a very similar hardware platform for the subsystems that are being targeted (TVC - Thrust Vector Control subsystem for the SRB (Solid Rocket Booster)).

Martin, Rodney Alexander↗