Faurecia 8D - QRCI Training Module

8D- QRCI Training module
>> Be a master of active claim management
JR
20th April • 2012
Objectives
Welcome to the training session

“QRCI” !
In this module:
You will discover the QRCI / 8D methodology (steps and

description ) and Lesson Learned Sheet (when and how to do
them).
At the end of this training, you should be able to:

 Initiate 8D’s report
Property of Faurecia - Duplication prohibited
 apply the QRCI methodology.

 Assess 8D’s
 Initiate Lessons Learned
2
Problem Solving Tools
3
Problem solving tools
Different tools :
 QRCI, 8D …
 But always a scientific method based on PDCA :

 Understand the problem
 Look for possible causes
 Test possible causes to confirm them or eliminate them
 Confirm corrective actions (counter-measures)

 Monitor and confirm results
 Re-iterate if it does not work
4
PDCA (or Deming wheel)
A P
Plan
C D
A P
Do
C D
A P
Check C D
A P
C D
Act / Adjust
5
What is a QRCI?
6
What is a QRCI?
A MINDSET and MANAGEMENT approach to
immediately respond to
non-performance, solve any kind of
problems and learn lessons for the future
1st priority: secure the customer (user)
2nd priority: avoid re-occurrence
Quick Response Continuous

Improvement
7
QRCI ….. QUICK ?
Why ?
do we need to be
quick
1. To be efficient
2. To be closer to the problem
8
The 6 Key Points of QRCI
 Real workplace Where and when it happens

 Real parts What is really the defect? Compare OK (good) and
NOK (bad) parts (causes, situation,..)
 Real Data No guessing, no bla-bla
Speak with data compared to standards
 Quick Response Respond immediately
Protect customer (user) first
 Logical Thinking What is the problem?
What is/are the root cause(s)?
What are the countermeasures?

How do I prevent re-occurrence?
 On Job Coaching Monitor, Train, Support, Recognize
9
D7
D2
QRCI Board for an 8D Analysis
BE LOGICAL ! D1
D1 What is the problem? D3

D2 Do I have same problem elsewhere?
Plan D3 How to contain, quickly?
D4
D4 What is the root cause?
D5 (non detection and occurrence)
Do D6 What are corrective actions plan?
Check D7 How to check effectiveness? D5

Act D8 What did we learn?
(How to capitalize and

transversalize ?)
D6
D8 10
8D Methodology
11
8D – The background
- An 8D-like process used by US military during WW II (STD 1520)
- 1987 FORD motor company – Team oriented problem solving –
- FAURECIA FCP FAU-S-LSG 0230 + FAU-F-LSG 0230
D1: Problem description 5W / 2H + IS / IS NOT QP by
D2: Risks on similar products and processes (plants) SQA
Supplier
reaction after
D3: Containment action
max 24h
D4: Root cause of non- detection WHY shipped/ WHY not seen ?
.. max.
D5: Root cause of occurrence WHY happened/ Why made ? 10days
D6: Countermeasures
D7: Effectiveness .. max.
D8: Lesson learned / Preventing reoccurrence 60days
12
8D methodology steps
D1 – Problem description
D2 – Risks on similar products and processes
D3 – Containment actions
D4 – Root causes for non detection
D5 – Root causes for occurrence
D6 – Corrective action plan
D7 – Effectiveness (Tracking chart)
D8 – Lessons Learned and Closure
13
8D – The format
FAU-F–LSG 0230
14
Guideline n°1
Plant must provide precise defect description to their supplier,
including picture or photo and part manufacturing date.
(See guideline n°3)
Attach file with

picture!
Be precise!
Provide details on supplier

manufacturing date!
15
Capitalization & Transversalization of 8D
8D – problem solving report for Quality
D1. Description & Sketch _
D2. Risk on similar products and _

processes
D3. Containment In 1 day

D4. Root cause of non detection _
D5. Root cause of non _

conformance
D6. Countermeasure to non In 10 working days

detection and non conformance
D7. Effectiveness of action plan _
D8. Lessons learned In 60 working days
16
D1 : be precise !
5W / 2H
Be precise towards the supplier and

inside the FAURECIA QSS system …
17
D1 - Problem description by 5W2H´s
CATEGORY :
- The SQA- task
Don't forget the drawing release number PF1 Disturbance of the
supply flow
PF2 Disturbance of the
production flow
What happened ? PF3 Stoppage of
FAURECIA production line
PF4 Claim from FAURECIA
Why is it a problem ? customer
PF4/SR Claim from
FAURECIA customer
related to a S/R
Where was it detected ? characteristic
( If known, where was it created ? )
When was it detected ?

( If known, when was it created ? )
Who detected it ?
( If known, who created it ? )
How was it detected ?

( If known, how was it created ? )
How many defective parts ?

( How many suspect parts ? )
… , also a risk for other FAURECIA plants ?

18
D1 - Problem description by Is / Is Not
- The SQA- task
Retained
IS IS NOT
Factors
Scratches / dents inclusions or other Type and dimension of wetting

Wettings on the class "A" surface
cosmetic imperfections (investigate)
Reaction between paint components Paint composition

Fibers / finger marks
Reaction between paint and substrate Raw materails
Stress on the injected part(?) Delamination of the injected plastic

Paint aplication System(?) material Analysis of differents machines
Paint aplication process Analysis of cleaning before or in-

After painting aplication
Part surface cleaning method line
Painting inspection team

At the laser process Sequential injection point
Reaction between paint and substrate
Type of material used

Part surface cleaning - materials
At the assy laser Evaluate the stress of the injected
Stress on the injected part(?)
part and on the paint
Visual inspection
19
Open QRCI
Described with customer view, the problem as
stated
Put the date when you open the QRCI and the
meeting dates for the review and follow up of the
QRCI
Define a team with a driver and

support functions. (put names)
20
D1 – Problem Description
Example of customer view
Customer view
21
D1 – D3
Description of the problem,

as detailed as possible, to
be focused only on that
problem
Installation of containment
actions
Measurement of the
problem
22
D1 Problem Description (5W’s + 2H’s)
3 progressive steps to describe the problem:
1st problem
definition
Customer
view
2d problem
(re) definition once the
retained factors have
been identified
23
D1 – Problem Description (5W’s + 2H’s)
Define the problem by asking the following questions (5W+2H):
•What is the problem ?
• Why is it a problem?
• Where was it detected ?
• When was it detected?
• Who detected the problem?
• How was it detected ? (describe what has enabled people to say
there is a problem)
• How many defects ?
By answering these questions, with facts and data, you will

describe the situation that you want to improve
24
D1 Identify the problem
Purpose :
 Describe the situation, understand the problem
Method :
 Questions, NO pre-conceived idea
 5W2H :
 What, Who, When, Where, Why ?
 How and How much ?
NO GENERAL STATEMENT, use DETAILS from the

GEMBA,
REDUCE THE SCOPE !!
25
What is GEMBA?
26
Remember:
> This part aims to
describe and clearly
identify the problem as the
Faurecia view (“supplier”).
> Collect information's as
much as possible
> Let the data “talk to you”
27
D1 Is / Is not analysis and Differences
IS: What did happen
IS NOT: What did not happen whereas it could have happened
What ? => between parts why this part and not that one ?
Who ? => between operators why Mr X and not Mrs X ?
Where ? => between plants here and not there?

=> between customers (users)
=> between defect location
=> between processes
When ? => between days/shifts why today and not yesterday?

How ? => between detection modes why did he see it and not me ?
How much ?=> between shifts why not (or less) on shift B ?
28
Good / Bad « Parts »
In a Production
context:
29
D1 IS and IS NOT / Retained factor
> Cut a big problem into small pieces
5W/ 2H´ s IS IS NOT Retained Remember:

1st Problem Definition (is the problem) (Is not the problem) Factors The retained factors
What is the problem ? blue pigment (migrating under
db dl, da X
Skin TITAN SCHWARZ becoming blue db-0.3

certain conditions)
considered must be
in Spain skin has to match the air bag lid
Why is it a problem?
Specification db + - 0.25
(see VW report)
in South Africa ?
color from TRW
?
elements from our
VW Spain nok
match wih air bag lid becomes cr itical
On Visteon
“processes” that explain
Time :
DETECTED on skin Uitenhage ; on IP
? On other Titan Schwarz
Palmela
customer does not see if IP the criteria placed in the
after mount by SAS cockpit immediately mounted ? x
FOUNTAIN INN ? IS and the IS NOT.
PUEBLA ?
RHD (processed Uitenhage) LHD (processed by Visteon Medina)

in bound transportation
(temperature in container on ?
The Formulation
When the problem happened? When was the
problem created? ship) between the columns IS
> dec 2011
? By VW Spain
db measure taken just after slush as
1ok part ; (2h to max 8h)
and IS NOT has to be
Who found the problem? Who created the
problem ?
different from the
VW Spain
some points in skin more stable Processing of the Powder X
column “Retained
Where was the problem found? Where was the
problem created? seen on recent as well as > 10 dependant of shelf life of the
Factors"
Found VW months old powders powder
cr eated FAU Uit
How the problem was found ?
Measur e db
visual ?
Why under some circumstances the problem occurs, but also why, under other circumstances, the
problem does not occur. Identify differences.
REDUCE THE SCOPE , Differences are potential FACTORS of occurrence and non- detection
30
D2 Risks on similar products and processes
> All risky part numbers/ Objective: identify risks on
process- steps are known ! similar products and
> Concrete actions taken to processes
protect the customer (user)! TO BE DONE BEFORE D3
> D2 Results are known and taken
into consideration Purpose:
> Re-define the problem after IS/ • Warn other support or
IS NOT check, get focused operation teams that the
> Reduce the scope problem could occur on their
sites
• Learn from them if they have
had similar issues and how
they tackled them
If similar risks on similar products, Method: Identify which other

processes, plants has been detected then it sites, teams, products,

will be also need containment actions there. processes could be impacted if
critical, warn other teams
31
D3 Containment [Customer protection first]
Objective: Define the immediate
actions to be carried out to
protect the customer.
Typically these actions include
sorting of all parts identified as
potentially at risk, then a
temporary containment action
Purpose :Take immediate action

to protect user from issue + Key
step when disruption is significant
(critical system unavailable, data
loss …)
Method :Define degraded

solutions, workarounds to protect
The action is considered effective if the
user from major disruption; Check
customer (external or internal) has not that the containment measures
received a non-conforming “parts” after the are in place and that they work
implementation of the action
> Tasks assignment to involved staff
The effectiveness is demonstrated by
monitoring the tracking chart. > Blocking of suspect batches/ sorting /
collected data taken into consideration for
In this column, we have new risks identified D4/D5!
only if defects were found in different sort
> Close communication with customer
(user) 32
D3 – Containment actions within 24h - The SUPPLIER task
“FAURECIA, we
are confident
that you are fully
protected,
we will start to
analyze the
root causes,
we will update
you about
D4/D5/D6
on time!”
33
DEVIATION/ DEROGATION !!!
Just in case we have to

use the parts, with
additional workload for
FAURECIA, to avoid
delivery problems
> Deviation
A time- limited or quantity limited

acceptance giving to the supplier
to deliver out of specification !!
Signed by the SQA and the

QUALITY MANAGER
To be shared with logistic/ UAP /
controlling ….
34
D3 & D7 Tracking Chart
• Follow all relevant indicator's, day by day, shift by shift
• Evaluate the impact of corrective actions on indicators
This bar represents the day of the incident. The In order to visualize the effectiveness of the actions
previous section is used to the recording of mentioned in the D6, we must entered on the tracking
historical data (3 months) chart the date of implementation of corrective actions
of the Action Plan
35
D4 – D6
Investigation to the cause
of the problem
Action Plan
36
D4 / D5 Preliminary Checks
1st question to be answered: Did we follow our standards?
Before starting the analysis ask the following questions:

 Control Plan and FMEA checked?
 Procedure checked?
 “Operators” trained and Standardized Work followed?

 ...
Always check existing standards before starting

investigation
37
D4+ D5 > FICS Training
QSE Operations
Interior Systems
FICS analysis
FICS vs. Fishbone Diagram
 Starting from the same hypothesis (6 M)

 But: FICS=observation of the shop floor
 But: FICS=use my eyes and my legs
 But: FICS=translation of my observation in data

good - bad
is - is not
actual situation
39
FICS analysis
FICS
 Possible causes derived from Fishbone diagram
Factor = potential cause

 Through observation on genba
 Through comparison good/ bad parts
 Through using the 3 REAL’s
FICS is more concrete than Fishbone

 Defining root cause is more factual, based on real

data
40
FICS analysis
On job coaching
 Not looking for the perfect solution

 100% solution not always obvious
 Using the Kaizen principle

 Step by step improvements
 Keeping up the momentum
 Better a quick 60% solution than a 100% longterm

solution
41
FICS analysis
Factors
Investigation
Comparison
Standard
Factors Investigation in Comparison

to the Standard
Non Detection Creation/ Occurrence
Factors Factors
D4 and D5 stages of QRQC UAP.

42
FICS analysis
O = OK, X = NOK, ∆ = Doubt , V = VerifyNON

DETECTION FACTOR: potential cause
As short why the defective part was not detected in the

and process (ex. during self-inspection)
detailed Or why occurrence factor was not detected
as  Fishbone!
possible
43
FICS analysis
CREATION / OCCURENCE FACTOR:

reasons why the part is NOK
(ex. pressure, geometry of assembly
stand, temperature, design,
standard)
Or why occurrence factor was not
detected
 Fishbone!
Short and
detailed
O = OK, X = NOK, ∆ = Doubt , V = Verify
44
FICS analysis
STANDARD: what is the rule, the specification (as
indicated in drawing, in standardized work instruction);
the standard can be explicit or implicit
(ex. inspect visually that pillar B is free of scars)
CONTROL POINT: how to evaluate /

O = OK, X = NOK, ∆ = Doubt , V = Verify measure / characterize the factor
condition
(ex. visual acc. to self-inspection instructions)
45
FICS analysis
STANDARD: what is the rule, the specification (as

indicated in drawing, in standardized work instruction);
the standard can be explicit or implicit
(ex. temperature of the mould, the number of parts in box)
CONTROL POINT: how to

evaluate / measure / characterize

the factor condition
(ex. visual or with measuring device)
46
FICS analysis
Observation results with data Judgement of observations findings
Comparison good / bad parts Prove what is real cause
REAL vs. STANDARD:

X when NOK parts do
not meet the standard
STANDARD OK?:
the standard is clear.
the respect of the standard
will contribute to prevent
the problem to occur.
REAL SITUATION: describe the real

situation of the factor with the real
values or the observation result on
OK parts/process and on NOK
parts/process
(ex. inspection result during self inspection)
47
FICS analysis
Observation results with data Judgement of observations findings
Comparison good / bad parts Prove what is real cause
REAL SITUATION: describe the real situation of the

factor with the real values or the observation result
on OK parts/process and on NOK parts/process
(ex. measuring result during self inspection)
REAL vs.
STANDARD:
STANDARD OK?:
X when NOK parts
the standard is clear.

do not meet the
the respect of the
standard
standard will
contribute to prevent
the problem to occur
48
FICS analysis
INVESTIGATION ACTION: Action to prove that

the suspected factor is the real cause.
Attention: standard may be NOK, parts may be
NOK without relationship to the problem

The factor is validated, that means the potential factor is
a cause of the problem. An analysis with the 5 WHY´s will
investigate the root cause of this factor / cause.
A corrective action D6 must be associated
(ex. set up more powerful lamps)
49
FICS analysis
INVESTIGATION ACTION: Action to prove that

the suspected factor is the real cause.
Attention: standard may be NOK, parts may be
NOK without relationship to the problem
The factor is validated, it means the potential factor

is a cause of the problem. An analysis with the 5
WHY´s will investigate the root cause of this factor /
cause.
A corrective action D6 must be associated
(ex. accurate temperature control) 50
FICS analysis
Potential causes Real causes

O = OK, X = NOK, ∆ = Doubts , V = Verify

Root cause
Analysis using
5 Why’s needed
51
FICS analysis
Potential causes Real causes

O = OK, X = NOK, ∆ = Doubts , V = Verify Root cause

Analysis using
5 Why’s needed 52
FICS analysis
possible non detection factors ….
Standardized work
Operators training
People availability
Rework flow
Work station ergonomics
Cycle time
Process audits
1st part OK
Polyvalence
53
FICS analysis
possible creation factors ….
Product and process parameters

 volume / longitude / weight
 % humidity
 quantity
 cost
 identification / traceability
 packaging
 pressure
Standardized work
Operators training
54
D4 & D5 5 Why's
Purpose :
 Identify a problem's root cause
Method :
 Ask at least 5 times, consecutively, the question
"why" regarding the problem and its probable cause
(s)
 When should it be used ?
 For each factor if it was validated
55
D4 & D5 5 Why's
5 WHY’s: finding the root cause
Focus on technical WHY’s, “V”: There is evidence / action that this
not on systems ’s statement is true
For each validated factor, we do the analysis

with the 5 WHY´s to find the root cause of the
If check in detail and / or factor (= the real cause of the problem) and a
validation of statement is corrective action D6 must be associated for
needed, go back to FICS and each root cause.
add it as new factor 56
FICS analysis
5 WHY’s: finding the root cause

“V”: There is evidence
Focus on technical WHY’s, / action that this
not on systems why’s statement is true
TEMPERATURE V INSUFFICIENT V FILTER V NOT V CHECK FILTER V MAINTENANCE

UPPER TOOL COOLING DIRTY CLEANED of COOLING SYSTEM
STANDARD
at 250°C NOT Required by
NOT According to
MAINTENANCE SPEC
TOOLING SPEC.
REQUIRING
FILTER
If check in detail and / CLEANLINESS
or validation of
statement is needed,
go back to FICS and
add it as new factor

For each validated factor, we do the analysis
with the 5 WHY´s to find the root cause of the
factor (= the real cause of the problem) and a
corrective action D6 must be associated for
each root cause.
57
FICS analysis
Lessons Learned Sheet
Detailed description
of only 1 problem.
Self explainable picture of the

change. It describes the
action done on the factor /
cause which created the issue
Action to maintain the

changed situation and
to avoid reoccurrence.
58
FICS analysis
Lessons Learned Sheet

This is the REACTION RULE
if the factor is out of control
This is the new FACTOR

to be kept under control.
This is the CONTROL POINT

to monitor / check that the
factor is in the right
condition
59
FICS analysis
Sum up
60
FICS analysis: SUM UP
 Non Detection Factor: potential causes why the defective

part was not detected and/ or why the occurrence factor was
not detected
 Creation/ Occurrence Factor: reasons why the defect was
created
 Control Point: how to evaluate/ measure/ characterize the
factor condition, and afterwards how to control it in the
control plan
 Investigation Action: concrete action to prove that the
suspected factor, is or is not, the real cause

 5 Why’s: investigation actions to find the root cause of every
validated factor (real cause).
61
FICS analysis
Exercise
62
Complete ...
REAL Parts Real vs. Standard

Factor Control Point Standard NOK Parts OK Parts Std ? OK ?
Train
Stopwatch 20' +/- 2' 30' 19'
frequency
Diameter a Caliper 15 +/- 2 14 16
Diameter b Caliper 13 +/- 2 15 14


a
b 63
Solution
REAL Parts Real vs. Standard

Factor Control Point Standard NOK Parts OK Parts Std ? OK ?
Train
frequency
Stopwatch 20' +/- 2' 30' 19' X O
Diameter a Caliper 15 +/- 2 14 16 O X
Diameter b Caliper 13 +/- 2 15 14 O X

a
b 64
D6 Corrective Actions
Objective: Define and implement actions to eradicate the problem.
Do not start D6 before having completed D4 and D5
Check that implemented actions do not create a new problem
Create the Lessons Learned Sheet after implementing the corrective

actions. This will right away:
 Challenge the logic of the action
 Highlight the changes before/after
 Highlight the factors to be controlled to prevent reoccurrence
In Production: check actual implementation of actions,

understanding and training of operators, in all shifts.
65
D6 Countermeasures implemented
Modify standardized work, auto-control absence of cracks Second detector to guarantee the
and correct settlement of rubber in tool. right position in both sides.
Train up-date, polyvalence level. Shift A, B , C.
66
D6 – Corrective actions within 10 days - The SUPPLIER task
Challenge the Supplier 8D against following criteria :

( Root cause analysis properly done -> DIG DEEP ! )
D4 : No inspection instruction or weak

Inspection process unclear, flow and content
Missing information
Poor gauges
Don't accept the easy
Missing POKA- YOKE, no OK first piece process
answer :
Workstation lightning, ergonomics
„It was a human error
or a new employee, we Takt- time faster than inspection time, or nothing reserved
will train him”
D5 : Process- Setting ( no parameter sheets or no respect )

No Poka Yoke ( High mental workload of employees )

Does D6 reflect the Poor work instructions
control of different No respect of standardize work
root causes ???
People training status etc. etc …….
67
D7 – D8
Tracking chart
Lesson learned
68
D7 Check effectiveness
> Follow up of defects per day/ shift … Highlight relation between actions introduced and the indicators
Objective: Check effectiveness of D6 actions, using the

tracking chart
On the tracking chart, highlight the implementation of the
corrective actions and check if there are no reoccurrences
Are corrective actions effective?

Do corrective actions prevent non-detection

and defect occurrence?
69
D8 Closure
Objective: Identify definitive changes to make sure the

problem will not occur again
 Did we understand why we did not predict the defect?

 Objectives met?
 People informed?
 Lesson Learned sheet completed, displayed and
disseminated?
 Are all standards directly related to the problem
(PFMEA, Control Plan, SW’s, Maintenance Plan,
Boundary Samples…) updated?
70
D8 – Lessons learned within 60 days - The SUPPLIER task
Challenge the Supplier 8D against following criteria :

- Any risk for reoccurrence or risk for FAURECIA ??
Workstation documents updated ?

Workstation modified ?
Inspection modifications ?
Boundary samples and Gauge R&R ?
Lesson learned sheets ?
71


Agenda
8D report upload process in GPS

Overall process of the 8D report /
introduction to Suppliers
2. Fill in your 8D 3. Attach the completed report for each

report 8D relevant step in GPS
Supplier
Side D3 step D6 step D8 step GPS
Notification
Notification
1. QP document 4. SQA validates
Faurecia sent from Faurecia the 8D report QSS
Side
73
QRCI Management
QRCI MANAGEMENT Check -list
Reaction Rules set? QRCI Schedule set?
q GAP readily informed q Schedule / attendance for
of any incident? reviews?
q Line: Response rules
to stop the line and do
QRCI?
Plant Review
By Div, BG
During visits
READY TO START?
QRCI Layout OK?

q Dedicated zone (Gap, UAP,
Plant Plant) with flip chart?
QRCI Priority rules set? q Line QRCI close to operators?
Daily, q NOK parts for open problems
q Safety -> S/R -> customer claims ->
kept?
Customer
Quality wall -> scraps -> reworks -> pph …
Complaints
Plant Mgr, Quality Mgr Stop at defect UAP QRCI

UAP Mgr, Supervisors, q Today's top 3 internal problems
q ALL defects analyzed at the time
Support Functions selected?
they arise, by operators, according
UAP Review to reaction rules? q Activities assigned?
Weekly q Tracking chart updated every shift?
q Customer protected? Why sent?
Plant Mgr q Impact of activities reviewed?
UAP QRCI Why made?
Daily, q Immediate actions to improve? q Weekly on job coaching by Plant
Top 3 problems Mgr + Quantity Mgr?
q Flip chart updated?
not solved by lines q Did the UAP improve something
today?
q Problem handover at shift change?
UAP Mgr
Supervisors, Support Functions Line Review Line QRCI PLANT QRCI
Daily q Review separated from problem q All customers claims tackled?
UAP Mgr solving?
q Activities Assigned?
/ Supervisors q Respect of QRCI 6 key points?
q Response time monitored?
Line QRCI / Stop at defect q Commitments met?

q On job coaching by Div / BG when
At Defect (Reaction rules) q Focus on priorities?
present?
• Analyze and quick response q On job coaching by UAP Mgr?
q Effectiveness checked for all shifts? q Did the plant improve
Operators, Gap Leader
something today?
(Supervisor) q Old problems closed first?
q Check understanding with operators?
q Standards updated at closing?
q Feedback to operators on quality
improvements at each top 5?
-1- QRCI Pocket Guide FAU -S-PSG -0230 EN V2 q Did the line improve something
today?
-2- QRCI Pocket Guide FAU -S -PSG -0230 EN V2
74
The key messages
Manage by walking around
Observe
Spend time on close

examinations
Focus on measurable
results
Pass only Good parts to the next stage
75
The basic tools….
What are the

Most important
Quality Tools?
My eyes and my legs (& my camera !) to….

see/ measure/ observe/ analyze/
record… 76
Conclusion
What have you learned during this session ?
What are the possible pitfalls ?

77
Thank You,
But you ?
What did you improve

today ?
Glossary
 Failure Mode and Effect Analysis (FMEA)
 Mass Production Trial (MPT)
 Design Validation Plan (DVP)
 Production Validation Plan (PVP)
 Initial Sample (IS)

 8D report (8 Discipline report)
 FCP (Faurecia Core Procedure)

79
Glossary
 5W 2H
 What happened ?  How detected
 Who detected ?  How many
 Where is it detected ?
 When it happened ?
 Why is it a problem?
 5Whys
 Why? / Why? / Why? / Why? / Why? / … to find root causes
 PDCA (= Deming ‘s wheel) : Plan / Do / Check / Act
 FICS (Factor Investigation with comparison to standard)

80
81

Faurecia 8D - QRCI Training Module

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Faurecia 8D - QRCI Training Module

Uploaded by

Copyright:

Available Formats

8D- QRCI Training module

>> Be a master of active claim management

Welcome to the training session

You will discover the QRCI / 8D methodology (steps and

At the end of this training, you should be able to:

 apply the QRCI methodology.

Problem Solving Tools

 But always a scientific method based on PDCA :

 Confirm corrective actions (counter-measures)

Quick Response Continuous

2. To be closer to the problem

 Real workplace Where and when it happens

What are the countermeasures?

D1 What is the problem? D3

Do D6 What are corrective actions plan?

Check D7 How to check effectiveness? D5

Act D8 What did we learn?

(How to capitalize and

D7: Effectiveness .. max.

D8: Lesson learned / Preventing reoccurrence 60days

(See guideline n°3)

Attach file with

Provide details on supplier

D1. Description & Sketch _

D2. Risk on similar products and _

D3. Containment In 1 day

D5. Root cause of non _

D6. Countermeasure to non In 10 working days

D7. Effectiveness of action plan _

D8. Lessons learned In 60 working days

Be precise towards the supplier and

( If known, where was it created ? )

When was it detected ?

How was it detected ?

How many defective parts ?

… , also a risk for other FAURECIA plants ?

Scratches / dents inclusions or other Type and dimension of wetting

Reaction between paint components Paint composition

Stress on the injected part(?) Delamination of the injected plastic

Paint aplication process Analysis of cleaning before or in-

Painting inspection team

Type of material used

Define a team with a driver and

Description of the problem,

By answering these questions, with facts and data, you will

NO GENERAL STATEMENT, use DETAILS from the

Who ? => between operators why Mr X and not Mrs X ?

Where ? => between plants here and not there?

When ? => between days/shifts why today and not yesterday?

5W/ 2H´ s IS IS NOT Retained Remember:

Skin TITAN SCHWARZ becoming blue db-0.3

RHD (processed Uitenhage) LHD (processed by Visteon Medina)

If similar risks on similar products, Method: Identify which other

processes, plants has been detected then it sites, teams, products,

Purpose :Take immediate action

Method :Define degraded

Just in case we have to

A time- limited or quantity limited

Signed by the SQA and the

Before starting the analysis ask the following questions:

Always check existing standards before starting

FICS vs. Fishbone Diagram

 Starting from the same hypothesis (6 M)