Sie sind auf Seite 1von 11

# Global Industrialization (GI)

Problem Solving

## 40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 1

Approach and Mindset

## Define the problem

Measure the process
Analyse the process
Improve the process
Control the process

Link to Six Sigma DMAIC on agora:

## 40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 2

GI Problem Solving Method

## Determine Implement Control, Issue

Define Analyze solved Standard-
Measure Root improvement verify and
Problem Problem ization

## 40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 3

GI Problem Solving Method – Responsibility

## Determine Implement Control,

Define Analyze Root improvement verify and Standard-
Problem Measure Problem ization

Responsibilit
y
IP Engineer/ IP Engineer/ IP Engineer/ IPQM IPQM IPM & IPQM
R&D Engineer R&D Engineer R&D Engineer/ R&D
Industrialization cc: IPQM cc: IPQM Sourcing SQE
phase: cc: IPQM

Site Site Site (IPQM to confirm) IPQM IPQM IPM & IPQM
High Volume
Phase:

RCA Template

## In order to do a proper RCA, please use Global Indus Problem Solving

(RCA) Template, 4/002 01-FEA 202 8192 or similar

Define
Problem

## Tools/Support: ► Matrix (mandatory)

When? What? Where? How Often? How
much?
Does Occur
Does not
► Occur
Pictures (mandatory)
► Yield failure figures (support)
► QC, Quality Control Tools such as Pareto, Histogram etc (support)

## Reporting: ► Report problem definition into a project database

► Use standard template

Check Question: ► Does the definition reflect the gap between actual situation and
target?

Measure

## Tools/Support: ► Yield failure figures (support)

► QC, Quality Control Tools such as Pareto, Histogram etc (support)

## Reporting: ► Report production process data, test station data,

inspection data and other relevant data
► Use standard template

Check Question: ► Does the measurements reflect the situation of the process
stability (instability)

## 40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 7

Analyze Determine
Problem Rootcauses

## Key Activities: ► Collect as much data as possible and needed

► Identify possible cuases
► Prioritize and select most likely cause
► Identify Root Cause

## Tools/Support: ► Brainstorming (mandatory)

► Ishikawa diagram (mandatory)
► 5 Why (mandatory)
► Yield failure figures (support)
► QC (histogram, Pareto…) (support)
► LL DB (review)
► DMS DB (review)
► Experience – ask and investigate regarding trouble shooting

## Reporting: ► Analyzis of Directions of Rootcause (statement acc to

yield categorization)
► DMS (enclose facts)

## Check Questions: ► How does your analysis visualize the problem?

► How was the root casue found?
40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 8
Implement
improvement
actions

Key Activities: ► Set up an action plan, review it with regards to risks (FMEA) then
► Implement and make sure that improvement actions is understood
and will be followed

Tools/Support: ►

## Reporting: ► Action/Implementation Plan

- Action (activities)
- Responsible person
- Due Date
► Expectations
► Highlight risks

## Check Question: ► How will the solution be implemented?

► How is the implementation progressing?
40/155 01-FEA 202 8192 Uen Rev B 2008-10-08 9
Control,
verify and

## Key Activities: ► Review iplementation

► Review result
► Make sure the problem stays fixed
► Write final report

## Tools/Support: ► Yield figures

► QC Tools (Graphs, Pareto, Histogram…)

## Reporting: ► Final Report

► Close DMS (enclose final report)

Standard-
ization

## Reporting: ► LL with preventive action

► Report to Synchronization Forum and Platform project
► Report to other involved subproduct projects needed