Professional Documents
Culture Documents
Risk/Failure Models
At the project level.
At the system or device level.
Common methods include Fishbone analysis or FMEA FMEA Failure Modes and Effects Analysis
Fishbone Chart
Cause and Effect Analysis Create an Ishikawa or Fishbone Chart Head is Problem Skeleton are the Causes Typical categories, 5Ms + E
Man Machine Material Method Measurement Environment
FMEA Example
How many ways can a floppy disk be inserted ??
FMEA Steps
1. 2. 3. 4. 5. 6.
Team activity Select component, system, process step, etc. Identify possible failure modes. Identify causes of failure modes. Identify effects of failures. Estimate (1-10 ranking):
1. Occurrence how often (1=not, 10=often) 2. Severity how bad (1=not, 10=severe) 3. Detection how easy (1=easy, 10=difficult)
Rules for OSD Values Threshold for Action Varies Thresholds 55-100 (?)
10
11
12
Process FMEA
Page Prepared by Original FMEA Date FMEA Number Telephone # FMEA Revision Date
Subsystem
Component
Design or Process Responsibility
Core Team
S e v
C l a s s
O c c
D e t
R P N
Recommended Actions
Actions Taken
S e v
O c c
D e t
R P N
13
14
From Dieter
15
16
FMEA Summary
Combines ideas of Cause and Effect chart, mistake proofing, and risk.
Useful to identify and prioritize possible failure modes and fixes. Possible Fixes :
High reliability components, De-rate components, Redundancy, Change the design.
17
FMEA
- A Requirements Approach
Consider
Requirements are what the system is supposed to do. Counter-requirements (not being met) are failure modes. Use counter-requirements to populate the FMEA table.
18
19
Design
FMEA
Coyote Hoist
20
*Process FMEA
21