Process Failure Modes and Effects Analysis

(PFMEA)
(PFMEA)
FMEA Name : _______________________ Process Responsibility : ___________________________________________________________________________________________________________________________

Part Name : _______________________ Prepared by: ______________________

Part Number : _______________________ FMEA Date: ______________________

Core Team : _______________________ FMEA Rev. Date: ______________________

C Current Design Actions Taken

S L R
Potential Failure Potential Cause (s) /
Process Step / Function Potential Failure Effects E A O D P Recommended Actions PIC Target Date S O D R
Mode Mechanism (s) of Failure Potential Cause (s) /
V S C Current Controls E N Actions Taken E C E P
S Mechanism (s) of Failure
C T V C T N

How Severe the impact is on

the causal path occuring

occur

Risk Priority Number

New Risk Prority Number

controls prevents or detects
How well the package of
The process step in which the X How the key input input The overall list of impacts The cause of the key input The cause of the key input

How likely the cause is to

The package of existing The planned actions for Individual responsible When Action The actual actions

New Severity rating

New Occurrence Rating

New Deection Rating

the Customer
occurs fails on downstream Customers failing failing controls along the causal path: reducing the RPN for the action will be taken
(internal or external) Cause -> FM -> Effect complete

0 0

0 0

0 0

0 0

0 0

0 0

0 0

0 0

0 0

0 0

0 0

0 0

Page 1
 Process
Process Failure
Failure Modes
Modes and
and Effects
Effects Analysis
Analysis
(PFMEA)
(PFMEA)

Process: Prepared by:

Process Owner: Revision Date:

S O D R S O D R
Actions
Process Step Input (X) Potential Failure Mode Potential Failure Effects E Potential Causes C Current Controls E P Owner Due Date Actions Taken E C E P
Recommended
V C T N V C T N

How Severe

Number
The actual actions taken

the impact is

Priority

New Severity

New

New Risk
on the

How likely the

cause is to

How well the

package of

rating

Occurrence
Rating
New Deection
Rating
Customer

occur

Prority Number
The process step The key input (X) under How the key input input The overall list of impacts on The cause of the key input The package of existing controls The planned actions Individual When Action

controls

detects the
path
occuring
prevents or
in which the X consideration fails downstream Customers failing along the causal path: Cause -> for reducing the RPN responsible will be
occurs (internal or external) FM -> Effect for the action complete

causal
Risk
Capture Data Background noise level Consistent medium level Delays in data capture, errors Old A/C equipment in area Capital equipment renewal cycle Replace A/C R.Smith 10-Sep A/C equipment replaced
noise in data capture, harm to (effectively none) equipment as planned. Noise-level
Customer from downstream 10 10 9 900 built into PMs for area 10 1 5 50
data errors, operator fatigue

Capture Data Background noise level Consistent medium level Delays in data capture, errors Other Customers in area None Facility construction of J.Jones 30-Sep Booth construction
noise in data capture, harm to operator booths completed as planned.
Customer from downstream 10 8 10 800 Queue moved to info 10 1 4 40
data errors, operator fatigue desk

Capture Data Background noise level Intermittent loud noises Delays in data capture, errors Maintenance crew work in None Move maintenance S.Brown 10-Sep Maintenance crew moved
in data capture, harm to adjacent area crew area to to facilities. Maintenance
Customer from downstream 10 7 10 700 warehouse request process updated 10 1 3 30
data errors, operator fatigue to reflect noise impacts

Capture Data Customer coherence Customer is distracted Delays in data capture, errors Customer's children are present Customer informed ahead of time
in data capture, harm to not to bring children, operator SOP
Customer from downstream 10 4 to ask children to wait outside if 5 200 0
data errors possible
Capture Data Customer coherence Customer is distracted Delays in data capture, errors Customer is taking phone calls Operator SOP to ask not to use
in data capture, harm to phone, "No Phone Calls" signage
Customer from downstream 10 2 7 140
data errors
Capture Data Customer language Different language from No data capture from
operator Customer, incomplete data
capture, errors in data 10 0
capture, harm to Customer
from downstream data errors
Capture Data Customer coherence Customer completely No data capture, delays in Customer is intoxicated
6 0
incoherent data entry
Capture Data Customer coherence Customer is distracted Delays in data capture, errors
in data capture, harm to
Customer from downstream 11 0 0
data errors
Capture Data Customer coherence Customer is distracted Delays in data capture, errors
in data capture, harm to
Customer from downstream 12 0
data errors
Capture Data Background noise level Consistent loud noise Delays in data capture, errors
in data capture, harm to
Customer from downstream 10 0
data errors, operator fatigue

Enter Data Operator eyesight Poor eyesight

0 0

Enter Data Operator time on shift Long time on shift.

Operator is tired 0 0

0 0
0 0
0 0
0 0
0 0
0 0

Page 2