SEARCH · Search NASA
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.
A study of rocket dynamics done by K. E. Tsiolkovsky in 1896 is reported. Problems in rectilinear movement of rockets were studied. Calculations were done on velocity efficiency, motion in free space, motion in a homogeneous gravitational field and motion with constant acceleration.
The final integration of Spacelab payloads with the Shuttle is described. Attention is given to launch processing planning, schedules, quality control, and problem reports and configuration maintenance. Also covered are the integration and checkout of individual and combined experiments, mounting the end cones, attachment of the transfer tunnel, and inclusion of an extra experiments pallet. The entire Spacelab module was subjected to a full systems simulation before deliverance to the Orbiter bay. Modular parts that were transferred from building-to-building were placed in sealed containers filled with a purged atmosphere during transport.
The range of managerial, technical, and procedural initiatives implemented by NASA's post-Challenger safety program is reviewed. The recommendations made by the Rogers Commission, the NASA post-Challenger review of Shuttle design, the Congressional investigation of the accident, the National Research Council, the Aerospace Safety Advisory Panel, and NASA internal advisory panels and studies are summarized. NASA safety initiatives regarding improved organizational accountability for safety, upgraded analytical techniques and methodologies for risk assessment and management, procedural initiatives in problem reporting and corrective-action tracking, ground processing, maintenance documentation, and improved technologies are discussed. Safety issues relevant to the planned Space Station are examined.
Statistics are emphasized as an important role in quality control and reliability. Consequently, Trend Analysis Techniques recommended a variety of statistical methodologies that could be applied to time series data. The major goal of the working handbook, using data from the MSFC Problem Assessment System, is to illustrate some of the techniques in the NASA standard, some different techniques, and to notice patterns of data. Techniques for trend estimation used are: regression (exponential, power, reciprocal, straight line) and Kendall's rank correlation coefficient. The important details of a statistical strategy for estimating a trend component are covered in the examples. However, careful analysis and interpretation is necessary because of small samples and frequent zero problem reports in a given time period. Further investigations to deal with these issues are being conducted.
A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.
The development of a culture of safety and NASA since the Challenger accident is reviewed. The technical elements of the strengthened NASA safety program are described, including problem reporting, risk/assessment/risk management, operational safety, and safety assurance are addressed. Future directions in the development of safety are considered.
The authors discuss a trend analysis program that is being conducted on the problem reports written during the processing of Space Shuttle payloads at Kennedy Space Center. The program is aimed at developing lessons learned that can both improve the effectiveness of the current payload processing cycles as well as help to guide the processing strategies for Space Station Freedom. The payload processing reports from STS 26R and STS 41 are used. A two-tier evaluation activity is described, and some typical results from the tier one analyses are presented.
The problem of the transformation of numerical values expressed in one system of units into another set or system of units frequently arises in connection with aerodynamic problems. Report contains aerodynamic coefficients and conversion tables needed to facilitate such transformation. (author)
This paper presents the complex social life of a large data base. The topics include: 1) Social Construction of Mechanisms of Memory; 2) Data Bases: The Invisible Memory Mechanism; 3) The Human in the Machine; 4) Data of the Study: A Large-Scale Problem Reporting Data Base; 5) The PRACA Study; 6) Description of PRACA; 7) PRACA and Paper; 8) Multiple Uses of PRACA; 9) The Work of PRACA; 10) Multiple Forms of Invisibility; 11) Such Systems are Everywhere; and 12) Two Morals to the Story. This paper is in viewgraph form.
The Aerospace Mechanisms Symposium (AMS) provides a unique forum for those active in the design, production and use of aerospace mechanisms. A major focus is reporting problems and solutions associated with the development and flight certification of new mechanisms. Organized by the Mechanisms Education Association, NASA and Lockheed Martin Space Systems Company (LMSSC) share the responsibility for hosting the AMS. Now in its 37th symposium, the AMS continues to be well attended, attracting participants from both the U.S. and abroad. The 37th AMS, hosted by the Johnson Space Center (JSC) in Galveston, Texas, was held May 19, 20 and 21, 2004. During these three days, 34 papers were presented. Topics included deployment mechanisms, tribology, actuators, pointing and optical mechanisms, Space Station and Mars Rover mechanisms, release mechanisms, and test equipment. Hardware displays during the supplier exhibit gave attendees an opportunity to meet with developers of current and future mechanism components.
In performance of this task order, bd Systems personnel provided support to the Flight Software Branch and the Software Working Group through multiple tasks related to software engineering improvement and to activities of the independent Technical Authority (iTA) Discipline Technical Warrant Holder (DTWH) for software engineering. To ensure that the products, comments, and recommendations complied with customer requirements and the statement of work, bd Systems personnel maintained close coordination with the customer. These personnel performed work in areas such as update of agency requirements and directives database, software effort estimation, software problem reports, a web-based process asset library, miscellaneous documentation review, software system requirements, issue tracking software survey, systems engineering NPR, and project-related reviews. This report contains a summary of the work performed and the accomplishments in each of these areas.
This study investigated the Shuttle Program s belief that Space Transportation System (STS) wiring damage occurrences are random, that is, a constant occurrence rate. Using Problem Reporting and Corrective Action (PRACA)-derived data for STS Space Shuttle OV-103, wiring damage was observed to increase over the vehicle s life. Causal factors could include wiring physical deterioration, maintenance and inspection induced damage, and inspection process changes resulting in more damage events being reported. Induced damage effects cannot be resolved with existent data. Growth analysis (using Crow-AMSAA, or CA) resolved maintenance/inspection effects (e.g., heightened awareness) on all wire damages and indicated an overall increase since Challenger Return-to-Flight (RTF). An increasing failure or occurrence rate per flight cycle was seen for each wire damage mode; these (individual) rates were not affected by inspection process effects, within statistical error.
Mission Assurance independent assessments started during the development cycle and continued through post launch operations. In operations, Health and Safety of the Observatory is of utmost importance. Therefore, Mission Assurance must ensure requirements compliance and focus on process improvements required across the operational systems including new/modified products, tools, and procedures. The deployment of the interactive model involves three objectives: Team member Interaction, Good Root Cause Analysis Practices, and Risk Assessment to avoid reoccurrences. In applying this model, we use a metric based measurement process and was found to have the most significant effect, which points to the importance of focuses on a combination of root cause analysis and risk approaches allowing the engineers the ability to prioritize and quantify their corrective actions based on a well-defined set of root cause definitions (i.e. closure criteria for problem reports), success criteria and risk rating definitions.
This viewgraph presentation reviews the implementation of Accident Precursor Analysis (APA), as well as the evaluation of In-Flight Investigations (IFI) and Problem Reporting and Corrective Action (PRACA) data for the identification of unrecognized accident potentials on the International Space Station.
A method has been formulated to enable prediction of the amount of work that remains to be performed in developing flight software for a spacecraft. The basic concept embodied in the method is that of using an idealized curve (specifically, the Weibull function) to interpolate from (1) the numbers of problems discovered thus far to (2) a goal of discovering no new problems after launch (or six months into the future for software already in use in orbit). The steps of the method can be summarized as follows: 1. Take raw data in the form of problem reports (PRs), including the dates on which they are generated. 2. Remove, from the data collection, PRs that are subsequently withdrawn or to which no response is required. 3. Count the numbers of PRs created in 1-week periods and the running total number of PRs each week. 4. Perform the interpolation by making a least-squares fit of the Weibull function to (a) the cumulative distribution of PRs gathered thus far and (b) the goal of no more PRs after the currently anticipated launch date. The interpolation and the anticipated launch date are subject to iterative re-estimation.
Fault Induced Document Retrieval Officer (FIDO) is a computer program that reduces the need for a large and costly team of engineers and/or technicians to monitor the state of a spacecraft and associated ground systems and respond to anomalies. FIDO includes artificial-intelligence components that imitate the reasoning of human experts with reference to a knowledge base of rules that represent failure modes and to a database of engineering documentation. These components act together to give an unskilled operator instantaneous expert assistance and access to information that can enable resolution of most anomalies, without the need for highly paid experts. FIDO provides a system state summary (a configurable engineering summary) and documentation for diagnosis of a potentially failing component that might have caused a given error message or anomaly. FIDO also enables high-level browsing of documentation by use of an interface indexed to the particular error message. The collection of available documents includes information on operations and associated procedures, engineering problem reports, documentation of components, and engineering drawings. FIDO also affords a capability for combining information on the state of ground systems with detailed, hierarchically-organized, hypertext- enabled documentation.
During Space Shuttle processing, discrepancies between vehicle dimensions and per print dimensions determine if a part should be refurbished, replaced or accepted "as-is." The engineer's job is to address each discrepancy by choosing the most accurate procedure and tool available, sometimes with up to ten thousands of an inch tolerance. Four methods of measurement are commonly used at the Kennedy Space Center: 1) caliper, 2) mold impressions, 3) optical comparator, 4) dial bore gage. During a problem report evaluation, uncertainty arose between methods after measuring diameters with variations of up to 0.0004" inches. The results showed that computer based measuring devices are extremely accurate, but when human factor is involved in determining points of reference, the results may vary widely compared to more traditional methods. iv
The Data Mining project seeks to bring the capability of data visualization to NASA anomaly and problem reporting systems for the purpose of improving data trending, evaluations, and analyses. Currently NASA systems are tailored to meet the specific needs of its organizations. This tailoring has led to a variety of nomenclatures and levels of annotation for procedures, parts, and anomalies making difficult the realization of the common causes for anomalies. Making significant observations and realizing the connection between these causes without a common way to view large data sets is difficult to impossible. In the first phase of the Data Mining project a portal was created to present a common visualization of normalized sensitive data to customers with the appropriate security access. The tool of the visualization itself was also developed and fine-tuned. In the second phase of the project we took on the difficult task of searching and analyzing the target data set for common causes between anomalies. In the final part of the second phase we have learned more about how much of the analysis work will be the job of the Data Mining team, how to perform that work, and how that work may be used by different customers in different ways. In this paper I detail how our perspective has changed after gaining more insight into how the customers wish to interact with the output and how that has changed the product.