Looking for Productivity Improvement ?
Check out our Productivity site with 100s of FREE downloads.

DFMEA Common Mistakes (Plantech, 1 page)

10 Ways to Get More Value From Your FMEA (Plantech, 1 page)

Typical ground rules for an FMEA are given along with an overview of the technique, principal, step-by-step instructions, sample work sheets, and work sheet data entries. Specific projects must, of course, add to, delete and otherwise tailor the procedures to conform with their needs, objectives, and contractual requirements. That is particularly true of safety issues or workaround operational methods. Although software analysis is outside the scope of an FMEA, the effects of failure modes at both software and hardware-software interfaces are included. (12 pages)

This packet is intended for use in the fourth year mechanical engineering design sequence. The material in this packet should help design teams perform a Failure Mode and Effect Analysis (FMEA) or a Failure Mode, Effect, and Criticality Analysis (FMECA) on their design projects. This experience should increase the students’ awareness of safety and reliability issues. The FMEA or FMECA should also help the design teams to improve the safety and reliability of their products while at the same time reducing design time and expenses. An example FMECA is included in the lecture. A homework assignment is included which involves completing an FMECA. (44 pages)

Sverdrup FMEA Manual.
Topics covered: Background, Definitions, Uses & Practical Applications, Procedure - Process, System Breakdown Concept, Don’t Forget These & Items Typically Ignored, FMEA Worksheets, Pressure Cooker Problem & Example, Coyote Hoist Problem & Example, SPF Countermeasures, When is an FMEA performed?, Benefits of FMEA, Limitations & Abuses of FMEA, Further Reading (38 pages)

Cayman Business System Potential Failure Mode and Effects Analysis (113 sheets)

Discount: 100s of books, vhs, dvd at our FMEA shop

Large presentation about FMEA (161 sheets)

QPAC Handbook: How to implement integrated quality systems in a factory.

This document describes how you can implement quality systems in a factory to improve both the quality of product produced now, and the quality of future product designs. In factories where these systems have been installed, the experience has been that wasted production has been reduced, and quality and customer satisfaction have been improved. The handbook provides results and details of the experience of implementing integrated quality systems at a number of aluminum foundries. However, the benefits are not limited to foundries. They should be applicable whether your company makes cakes or circuit boards (26 pages)

The Basics of Healthcare Failure Mode and Effect Analysis.
The purpose of this course is to help VA Patient Safety Managers understand and carry out analysis using Healthcare Failure Mode and Effect Analysis (FMEA) techniques in accordance with the revised standards issued by the Joint Commission on the Accreditation of Healthcare Organizations (L.D.5.2. Select high risk process for proactive risk assessment). Participants will learn through instruction and practice the steps involved in carrying out a successful proactive risk assessment using Healthcare FMEA. In addition, we will discuss how to choose an appropriate topic for evaluation (10 pages)

This guide was developed by the DoD Patient Safety Center to assist Patient Safety Managers in their role as FMEA team advisors and does not serve as the DoD manual on FMEAs. Review the entire guide before starting an FMEA. It is a guide to be used as a check sheet during the FMEA, to help ensure that each step of the FMEA has been fully completed and documented. Areas of the FMEA projects that have proven to be obstacles or stumbling points for other FMEA teams are underlined for your reference. If you have questions or concerns the Patient Safety Center can serve as a resource to assist in the completion of your FMEA (29 pages)

MFMEA Common Mistakes (1 page)

MILITARY STANDARD PROCEDURES FOR PERFORMING A FAILURE MODE, EFFECTS AND Critically ANALYSIS.
Procedures for performing a Failure Mode, Effects, and Criticality Analysis: MIL-STD-1629A
This standard establishes requirements and procedures for performing a failure mode, effects, and criticality analysis (FMECA) to systematically evaluate and document, by item failure mode analysis, the potential impact of each functional or hardware failure on mission success, personnel and system safety, system performance, maintainability, and maintenance requirements. Each potential failure is ranked by the severity of its effect in order that appropriate corrective actions may be taken to eliminate or control the high risk items (80 pages)

FMEA Example of an Investment Cast Rifle Bolt (7 pages)

The focus of this document is on analysis and development of safety critical software, including firmware (e.g. software residing in non-volatile memory, such as ROM, EPROM, or EEPROM) and programmable logic.
This Guidebook provides information on development activities and analyses used in the creation and assurance of safety critical software. Resource data required for each task, methodologies and tools for performing the task, and the output products are detailed. It also describes how to address software safety in the overall software development, management, and risk management activities.
This Guidebook goes on to describe techniques and procedures. Some techniques are well established and are illustrated in detail (or good reference sources are provided). Other techniques or analyses are new, and not much information is available. The Guidebook attempts to give a flavor of the technique or procedure as well as pointing to sources of more information.
To make the guidebook more practical, it contains analysis examples and possible pitfalls and problems that may be encountered during the analysis process. It is a synergistic collection of techniques either already in use throughout NASA and industry, or which have potential for use. Opinions differ widely concerning the validity of the various techniques, and this Guidebook attempts to present these opinions, without prejudging their validity. In most cases there are few or no “metrics” to quantitatively evaluate or compare the techniques. Moreover, this Guidebook is meant not only to provide possible techniques and analyses, but to open the reader to how to think about software from a safety perspective. It is important to observe software development with a “safety eye”. This Guidebook points out things to look for (and look out for) in the development of safety critical software. Development approaches, safety analyses, and testing methodologies that lead to improved safety in the software product are included. (317 pages !)

PFMEA Common Mistakes (1 page)