Hensarling, Paula L. | Search NASA

NASA NTRS2007

Test Facilities Capability Handbook: Volume 1 - Stennis Space Center (SSC); Volume 2 - Marshall Space Flight Center (MSFC)

The John C. Stennis Space Center (SSC) is located in Southern Mississippi near the Mississippi-Louisiana state line. SSC is chartered as the National Aeronautics and Space Administration (NASA) Center of Excellence for large space transportation propulsion system testing. This charter has led to many unique test facilities, capabilities and advanced technologies provided through the supporting infrastructure. SSC has conducted projects in support of such diverse activities as liquid, and hybrid rocket testing and development; material development; non-intrusive plume diagnostics; plume tracking; commercial remote sensing; test technology and more. On May 30, 1996 NASA designated SSC the lead center for rocket propulsion testing, giving the center total responsibility for conducting and/or managing all NASA rocket engine testing. Test services are now available not only for NASA but also for the Department of Defense, other government agencies, academia, and industry. This handbook was developed to provide a summary of the capabilities that exist within SSC. It is intended as a primary resource document, which will provide the reader with the top-level capabilities and characteristics of the numerous test facilities, test support facilities, laboratories, and services. Due to the nature of continually evolving programs and test technologies, descriptions of the Center's current capabilities are provided. Periodic updates and revisions of this document will be made to maintain its completeness and accuracy.

Hensarling, Paula L.↗

NASA NTRS2007

ISHM Anomaly Lexicon for Rocket Test

Integrated Systems Health Management (ISHM) is a comprehensive capability. An ISHM system must detect anomalies, identify causes of such anomalies, predict future anomalies, help identify consequences of anomalies for example, suggested mitigation steps. The system should also provide users with appropriate navigation tools to facilitate the flow of information into and out of the ISHM system. Central to the ability of the ISHM to detect anomalies is a clearly defined catalog of anomalies. Further, this lexicon of anomalies must be organized in ways that make it accessible to a suite of tools used to manage the data, information and knowledge (DIaK) associated with a system. In particular, it is critical to ensure that there is optimal mapping between target anomalies and the algorithms associated with their detection. During the early development of our ISHM architecture and approach, it became clear that a lexicon of anomalies would be important to the development of critical anomaly detection algorithms. In our work in the rocket engine test environment at John C. Stennis Space Center, we have access to a repository of discrepancy reports (DRs) that are generated in response to squawks identified during post-test data analysis. The DR is the tool used to document anomalies and the methods used to resolve the issue. These DRs have been generated for many different tests and for all test stands. The result is that they represent a comprehensive summary of the anomalies associated with rocket engine testing. Fig. 1 illustrates some of the data that can be extracted from a DR. Such information includes affected transducer channels, narrative description of the observed anomaly, and the steps used to correct the problem. The primary goal of the anomaly lexicon development efforts we have undertaken is to create a lexicon that could be used in support of an associated health assessment database system (HADS) co-development effort. There are a number of significant byproducts of the anomaly lexicon compilation effort. For example, (1) Allows determination of the frequency distribution of anomalies to help identify those with the potential for high return on investment if included in automated detection as part of an ISHM system, (2) Availability of a regular lexicon could provide the base anomaly name choices to help maintain consistency in the DR collection process, and (3) Although developed for the rocket engine test environment, most of the anomalies are not specific to rocket testing, and thus can be reused in other applications.

Schmalzel, John L.↗