FMEA Form v3.

FMEA
Process/Product Name: Encoding credit accounts,
giving notifications and grading
System.
Prepared By: GAZELY SANTUYO
Responsible: DSF, PSD, SAO & ICTS FMEA Date (Orig.): 22-Mar (Rev.):

Process Potential Potential Potential Current Action

OCCURRENCE (1 - 10)
Resp. Actions Taken

DETECTION (1 - 10)
Step/Input Failure Mode Failure Effects Causes Controls Recommended

SEVERITY (1 - 10)
What are the

RPN
What is the impact What causes What controls recommended Who is What are the
What is the In what ways
on the customer if the step or exist that either actions for reducing responsible for completed action
process step or could the step or
this failure is not feature to go prevent or the occurrence of making sure taken with the
feature under feature go
prevented or wrong? (how detect the the cause or the actions are recalculated
investigation? wrong?
corrected? could it occur?) failure? improving completed? RPN?
detection?

Encoding When the The student/s 7 When the 8 Substition of 2 112 To limit the The The
and adjusting persons-in- would not be person-in- workers, access of the Director of establishment
the labor charge have able to get charge of the supervision system to the the Student of having
(credit not encoded their subsidies feature has and ones who only Finance. limited
amounts) of the credit and at the been very monitoring of has the personnel
the working balances on same time pre-occupied the authority to do who would
students on time and or would not be with toxicity performance so to avoid have access
their personal encoded a allowed to get (task loaded) of jobs done. confusion and and do the
accounts. wrong their foods in the office. errors. encoding in
amount. from the the system.
cafeteria
without their
labor being
encoded in the
system.

Copyright 2019 GoLeanSixSigma.com. All Rights Reserved.

 FMEA Form v3.6

Public Safety When the The student 9 When the 7 Rechecking 2 126 To request the The Conduction of
Department's guard on will create a one who and re- confronter to Director of seminars and
giving of duty have social and confronted examination ask for second the Public or forums
notifications given a emotional and gave the of the opinion from Safety about the
and wrong panic on notification violation. the higher Department importance of
violations to notifications, his/her part to the person in knowing what
the students. violations or when the student/s position about notifications
imfractions consequences lacks the violation. or violation
to the of the knowledge penalties to
student/s. notification of his give to the
given is post/job. student/s.
beyond his/her
control.

Encoding of When the The student's 8 When both 7 The 1 56 To have a The The
the encoder convocation the encoder monitoring of detector that Director of development
attendance wasn't able grade will be or the the ID will create a the of a system
during the to see if affected. student is numbers sound Student's with a
student's he/she not attentive being whenever an Affairs and detector that
convocation. correctly of what is entered in ID number has the ICTS willcreate
inputs the ID happening or the system. been correctly Dept. sound
numbers of what they or incorrectly whenever an
the students are doing. encoded in the ID number
(during system. has been
manual encoded
encoding) or correctly/incor
if both the rectly.
encoder and
the student
didn't check
whether the
ID card has
been
entered in
the system
during scan.

Copyright 2019 GoLeanSixSigma.com. All Rights Reserved.

 FMEA Form v3.6

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

Copyright 2019 GoLeanSixSigma.com. All Rights Reserved.

 Severity Scale
Adapt as appropriate

Effect Criteria: Severity of Effect Ranking

Hazardous - May expose client to loss, harm or major disruption -

10
Without Warning failure will occur without warning

Hazardous - May expose client to loss, harm or major disruption -

9
With Warning failure will occur with warning

Major disruption of service involving client interaction, resulting in either

Very High 8
associate re-work or inconvenience to client

Minor disruption of service involving client interaction and resulting in either

High 7
associate re-work or inconvenience to clients

Major disruption of service not involving client interaction and resulting in either
Moderate 6
associate re-work or inconvenience to clients

Minor disruption of service not involving client interaction and resulting in either
Low 5
associate re-work or inconvenience to clients

Minor disruption of service involving client interaction that does not result in
Very Low 4
either associate re-work or inconvenience to clients

Minor disruption of service not involving client interaction and does not result in
Minor 3
either associate re-work or inconvenience to clients

No disruption of service noticed by the client in any capacity and does not result
Very Minor 2
in either associate re-work or inconvenience to clients

None No Effect 1
 Occurrence Scale

Per Item Failure

Probability of Failure Time Period Ranking
Rates

More than once per day >= 1 in 2 10

Very High: Failure is almost inevitable
Once every 3-4 days 1 in 3 9

Once every week 1 in 8 8

High: Generally associated with processes similar to
previous processes that have often failed
Once every month 1in 20 7

Once every 3 months 1 in 80 6

Moderate: Generally associated with processes
similar to previous processes which have
Once every 6 months 1 in 400 5
experienced occasional failures, but not in major
proportions
Once a year 1 in 800 4

Low: Isolated failures associated with similar

Once every 1 - 3 years 1 in 1,500 3
processes

Very Low: Only isolated failures associated with

Once every 3 - 6 years 1 in 3,000 2
almost identical processes

Remote: Failure is unlikely. No failures associated

Once Every 7+ Years 1 in 6000 1
with almost identical processes
 Detection Scale

Criteria: Likelihood the existence of a defect will be detected

Detection by process controls before next or subsequent process, -OR- Ranking
before exposure to a client

Almost Impossible No known controls available to detect failure mode 10

Very remote likelihood current controls will

Very Remote 9
detect failure mode

Remote likelihood current controls will

Remote 8
detect failure mode

Very low likelihood current controls will

Very Low 7
detect failure mode

Low Low likelihood current controls will detect failure mode 6

Moderate likelihood current controls will

Moderate 5
detect failure mode

Moderately high likelihood current controls will

Moderately High 4
detect failure mode

High High likelihood current controls will detect failure mode 3

Very high likelihood current controls will

Very High 2
detect failure mode

Current controls almost certain to detect the failure mode.

Almost Certain Reliable detection controls are known 1
with similar processes.