Company Name:

Project Leader DARIO ARRIAGA

WEXSOL

Date Initiated: 3-Sep-20

Built In Quality - 1 Pager
Establish the Team Go to where the problem has occurred & document 'point of cause.' Can you see the problem occur again? Did the team member see the problem occur again? 5 WHY's Problem Solving to Root Cause R
P 1. Why #1 The 1st Why - what directly cause the problem? Most cases, direct cause is NOT the root cause but is basis for implementing temporary counter measure. O
O Direct Cause O
I T
S 2. Why #2 Each of the 5-Why's should have quantified statements that connect the next level 'why' in terms of being a 'deeper' cause of the problem.
O C
N A
3. Why #3 U
M S
U Problem Description E
Attach photos, if possible. Document direct observation, data, and/or mini-experiments conducted to capture the facts (not opinions) of what is "really occurring?"Before rushing into 5 why's, utilize observation,
S testing and critical review of data to capture "facts." May require testing, verification, etc to rule out potential direct causes. 4. Why #4
H A
R N
O 5. Why #5 A
O L
M Y
Root Cause: The first abnormal event that sets off a chain of cause-and-effects that ultimately results in the problem. Does the root cause identify a gap that can be addressed through a systematic solution or countermeasure to prevent recurrence?S
I I
D S
E Interim Corrective Actions How can we be sure that this problem will not surface again before the PCA is implemented? List SN breaks, if applicable.
N Responsible Party By When Break Point (SN) Status
T C
I #1 O
F _______________ ___________ ___________ ___________ R
I Go, See, Act Go to where the problem has occurred & document 'point of cause.' Can you see the problem occur again? Did the team member see the problem occur again? R
E p Was Standard Work followed? p Were correct parts used? p Were correct tools used? p Are parts to blue print? p Are part per Spec?
#2 E
D Additional comments Permanent Corrective Actions Has the PCA been validated? Can we create the failure again? If yes, will we catch it? List SN breaks, if applicable. C
p myCPI updated Responsible Party By When Break Point (SN) Status T
I
V
#1 E
Containment Actions Verify that this problem was not built into any other product already, or that the next pieces we build will have this problem. _______________ ___________ ___________ ___________
Responsible Party By When Break Point (SN) Status A
C
T
#1 #2 I
_______________ ___________ ___________ ___________ _______________ ___________ ___________ ___________ O
C N
O S
N
#2
T _______________ ___________ ___________ ___________ #3
A _______________ ___________ ___________ ___________
I
N
#3 Prevent Recurrence Indentify and Implement steps that need to be taken to prevent the same or a similar problem from ocurring in the future:
M _______________ ___________ ___________ ___________ V
E #1 Trends and graphs are improving? A
N Quality Gate Implementation #2 Is a PPAP needed to support the corrective action and validate the process changes? L
T Responsible Party By When Status #3 Define an Audit Plan for your process and validate that standard work is been followed I
D
#1 Implement a Quality Gate - Depict in a Process Map where the QG will be located ___________ ___________ A
T
#2 Create a Checklist with Detailed and Visual Inspection Criteria ___________ ___________ I
O
#3 Define a Stop process for all parts that are found in the QG ___________ ___________ N

#4 Implement a Quality Gate Board at the QG ___________ ___________ A

Communication Plan How is everyone going to know to do this corrective action? Updated Std Work # p Quality Standard is updated N
#5 Design Metrics that depict Misses, Founds and New Finds and Post metric in the QG Board ___________ ___________ p Control Plan is updated and attached p Send 1 Pager Update to your customer and validate D

#6 Implement a Daily Internal Communication Process ___________ ___________ junta M

I
#7 Assign an Inspector for the QG and Train him on the Inspection Checklist ___________ ___________ T
Verification Metric to monitor to confirm that the corrective action is working I
Metric to Monitor Verification Date Status G

Fishbone Diagram
#1 Think in establish or Develop a Metric that contains Misses, Founds and New Finds: A
R T
O I
O O
T N

C
A
U
S
E

A
N
A

L
Y Lessons Learned Where else could this problem occur or might this solution apply?

S Replication Opportunities
I
S

Recognize the team as appropiate

 When Fishbone is complete
click this button to copy
the fishbone diagram to the
Fishbone Diagram one pager

Environment People Method

asdasdasd
fdfdfdf no existe metodo
dsadasd

sdsdsd
fdfdfdf
sadasd

PROBLEMAS

dsfdsf
dfdfdf dfdfdf

Material Measurement Equipment

LINEA = NO SE CONSIDERA CAUSA

? = PUDIERA NO SER UNA CAUSA DIRECTA
P = SE CONSIDERA UNA CAUSA DIRECTA

Some add 'Measurement' and/or 'Management'

 CONTAINMENT ACTIONS / IMMEDIATE CA / PERM
Containment /
Immediate /
Item Action Description Permanent or To
Prevent Recurrence
D5
D3
D6
ONS / IMMEDIATE CA / PERMANENT CA

Commitment Closed Is Audited

Responsible Date Date Status Effective? by
Comments
 5Ws + 2Hs
1. What / QUE?
¿Qué es la falla? Se trata de escribir una breve
descripción del problema que se está presentando,
máximo 2 líneas.

2. When / CUANDO?

¿Cuándo estamos viendo el problema? ¿En qué

momento del día y/o del proceso en cuestión?

3. Where / DONDE?
¿Dónde estamos viendo los problemas? (Línea /
Máquina / Lugar); ¿En qué parte/lugar del
producto/proceso estamos viendo el problema?.

4. Who / QUIEN?

¿A quién le sucede? ¿Quién lo esta haciendo?

5. Why / POR QUE?

¿Por qué sucede el problema? ¿Por qué fallo?

6. How / COMO?
¿Cómo se diferencia el problema del estado normal
(óptimo)? ¿La tendencia en la que aparece el
problema es aleatoria o sigue un patrón?

7. How Much / CUANTO?

¿Cuántos problemas se dan en un dia? ¿En una

semana? ¿En un mes? ¿Cuánto dinero están
implicando? ¿Qué tan grande es la afectacion?
DEFINICION DEL PROBLEMA

TOTAL
% CUMPLIMIENTO

100 80%