This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
OPERATIONAL DATA REQUIREMENTS FOR EXPERIENCE RETENTION
Annotation ability available
Sector:
Language:
English
Abstract
This paper explains the need for and use of operational field failure data to eliminate modes of equipment failure from existing designs and to prevent their recurrence in future designs. At The Boeing Company these processes are called “corrective action” and “experience retention.” Experience retention goes farther than the “field fix” or hardware corrective action because the process is considered complete only when needed changes have been made to basic resources such as methods and data manuals. The paper explains how field failure reporting principles are applied by specialists whose only job is to report factual qualitative data. It shows how specialists use this information to assure that modes of failure are eliminated from like follow-on hardware as well as retained in basic company resources.
Authors
Topic
Citation
Herrold,, G., "OPERATIONAL DATA REQUIREMENTS FOR EXPERIENCE RETENTION," SAE Technical Paper 630572, 1963, https://doi.org/10.4271/630572.Also In
References
- Friddell, H. G. and Jacks, H. G., “System Operational Effectiveness (Reliability Performance Maintainability Cost)” Fifth National Symposium on Reliability and Quality Control 179 196 January 1959
- Meister, D., “The Problem of Human Initiated Failures,” Proceedings Eighth National Symposium on Reliability and Quality Control Washington, D. C. 234 239 January 1962
- Cooper, J., “Human Initiated Failures and Malfunction Reporting,” Proceedings IRE Transactions on Human Factors in Electronics September 1961
- Shapero, A., Cooper, J. I., Rappaport, M., Schaeffer, K., Bates, C. Jr., WADD Technical Report 60–36 “Human Engineering, Testing and Malfunction Data Collection in Weapon System Test Programs,” February 1960
- Vorhees, H. A., Chairman Tommaney, R. F., Vice President, Maintenance Reporting Panel of the Maintenance Advisory Committee “National Security Industry Association Final Report to the Department of Defense on In-Service Data Collection and Analysis,” May 1962
- Gould E. B. III, Rainwaters, R. J., “Product Improvement Through Failure Reporting,” Hughes Aircraft Company October 1962
- “Data Systems Processing Requests from Manufacturers and Air Force Contractors for Logistics Information from Automated Data Processing Systems Under the Control of AFLC,” May 28 1962
- Elliott, D. R., “Integrated Record System for Manufacturing, Inspection and Test of Complex Weapon Systems,” Proceedings Eighth National Symposium on Reliability and Quality Control Washington, D. C. January 1962
- Overbey, C. A., “The Role of a Reliability Field Engineering Program in Weapon Systems Reliability,” presented at the SAE National Aeronautic Meeting Los Angeles, California October 10–14 1960
- Ball, L. W., “Reliability Management by Objectives and Results,” Eighth National Symposium 156 162 Washington, D. C. January 1962
- Stoler, D. S. and Van Horn, R. L., “Design of a Management Information System,” November 1958
- Anderson, G. P. and Raymond, G. A., “Failures are Important,” Missiles and Space Magazine 33 35 June 1961
- Kimball, E. W., “Failure Analysis,” Proceedings Eighth National Symposium on Reliability and Quality Control Washington, D. C. 117 128 January 1962
- Ferraro, Dr. Eugene T., Vice President, Customer Services, “Aspects of the Cost Reduction Program - The Concept of Data Provisioning,” presented at the l8th Annual Meeting of the National Security Industrial Association September 196l
- Ball, L. W., “The Impact of Reliability Requirements on U. S. Engineering Management,” presented at the Sixth International Conference of European Organization for Quality Control Aix-En-Providence, France 5 September 1962
- Ball, L. W., “Prediction, Improvement and Measurement of Reliability of One Shot Devices,” National IAS-ARS Joint Meeting Los Angeles, California June 196l
- Marsh, F. E., “A Comprehensive Education and Training Program for Design Reliability,” Proceedings Eighth National Symposium on Reliability and Quality Control Washington, D. C. 227 233 January 1962