You are on page 1of 4

Eight Disciplines Problem Solving - Wikipedia, the free encyclopedia

1 of 4

http://en.wikipedia.org/wiki/Eight_Disciplines_Problem_Solving

Eight Disciplines Problem Solving


From Wikipedia, the free encyclopedia

Eight Disciplines Problem Solving (8D) is a method used to approach and to resolve problems, typically
employed by quality engineers or other professionals. Its purpose is to identify, correct and eliminate
recurring problems, and it is useful in product and process improvement. It establishes a permanent
corrective action based on statistical analysis of the problem (when appropriate) and focuses on the origin of
the problem by determining its root causes. Although it originally comprised eight stages, or 'disciplines', it
was later augmented by an initial planning stage. The 8D follows the logic of the PDCA cycle. The disciplines
are:
D0: Plan: Plan for solving the problem and determine the prerequisites.
D1: Use a Team: Establish a team of people with product/process knowledge.
D2: Define and describe the Problem: Specify the problem by identifying in quantifiable terms the
who, what, where, when, why, how, and how many (5W2H) for the problem.
D3: Develop Interim Containment Plan; Implement and verify Interim Actions: Define and
implement containment actions to isolate the problem from any customer.
D4: Determine, Identify, and Verify Root Causes and Escape Points: Identify all applicable causes
that could explain why the problem has occurred. Also identify why the problem has not been noticed
at the time it occurred. All causes shall be verified or proved, not determined by fuzzy brainstorming.
One can use five whys or Ishikawa diagrams to map causes against the effect or problem identified.
D5: Choose and Verify Permanent Corrections (PCs) for Problem/Non Conformity: Through
pre-production programs quantitatively confirm that the selected correction will resolve the problem
for the customer. (Verify the correction will actually solve the problem)
D6: Implement and Validate Corrective Actions: Define and Implement the best corrective actions.
D7: Take Preventive Measures: Modify the management systems, operation systems, practices, and
procedures to prevent recurrence of this and all similar problems.
D8: Congratulate Your Team: Recognize the collective efforts of the team. The team needs to be
formally thanked by the organization.
8D has become a standard in the auto, assembly and other industries that require a thorough structured
problem solving process using a team approach.[1]

Contents
1 History
1.1 Ford's perspective
1.2 Military usage
2 Usage
3 Benefits
4 Disadvantages
5 Problem Solving Tools
6 Relationship Between 8D and FMEA
7 See also
8 References
9 External links

History
8D methodology despite what is generally thought has not been created by Ford but by the U.S. Department

01-05-2014 10:33

Eight Disciplines Problem Solving - Wikipedia, the free encyclopedia

2 of 4

http://en.wikipedia.org/wiki/Eight_Disciplines_Problem_Solving

of Defense (DOD) in 1974. The standard, which described 8D, was named: MIL-STD 1520 Corrective
Action and Disposition System for Nonconforming Material Standard was officially abolished in 1995, but
the 8D methodology has been propagated by Ford in the automotive industry and is well known to many
companies in the electronics industry.

Ford's perspective
The executives of the Powertrain Organization (transmissions, chassis, engines) wanted a methodology where
teams (design engineering, manufacturing engineering, and production) could work on recurring problems. In
1986, the assignment was given to develop a manual and a subsequent course that would achieve a new
approach to solving tough engineering design and manufacturing problems. The manual for this methodology
was documented and defined in Team Oriented Problem Solving (TOPS), first published in 1987. The
manual and subsequent course material were piloted at Ford world headquarters in Dearborn, Michigan.
Many changes and revisions were made based on feedback from the pilot sessions. This has been Ford's
approach to problem solving ever since. It was never based on any military standard or other existing
problem solving methodology. Ford refers to their current variant as G8D (Global 8D).

Military usage
The US Government first standardized a process during the Second World War as Military Standard 1520,
Corrective Action and Disposition System for Nonconforming Material.[2] This military standard focused on
nonconforming material and the disposition of the material.

Usage
Many disciplines are typically involved in the "8D" process, all of which can be found in textbooks and
reference materials used by quality assurance professionals. For example, an "Is/Is Not" worksheet is a
common tool employed at D2, and Ishikawa, or "fishbone," diagrams and "5-why analysis" are common tools
employed at step D4.
In the late 1990s, Ford developed a revised version of the 8D process that they call "Global 8D" (G8D)
which is the current global standard for Ford and many other companies in the automotive supply chain. The
major revisions to the process are as follows:
Addition of a D0 (D-Zero) step as a gateway to the process. At D0, the team documents the symptoms
that initiated the effort along with any emergency response actions (ERAs) that were taken before
formal initiation of the G8D. D0 also incorporates standard assessing questions meant to determine
whether a full G8D is required. The assessing questions are meant to ensure that in a world of limited
problem-solving resources, the efforts required for a full team-based problem-solving effort are limited
to those problems that warrant these resources.
Addition of the notion of escape points to D4 through D6. An 'escape point' is the earliest control point
in the control system following the root cause of a problem that should have detected that problem but
failed to do so. The idea here is to consider not only the root cause, but also what went wrong with the
control system in allowing this problem to escape. Global 8D requires the team to identify and verify
an escape point at D4. Then, through D5 and D6, the process requires the team to choose, verify,
implement, and validate permanent corrective actions to address the escape point.
Recently, the 8D process has been employed significantly outside the auto industry. As part of lean initiatives
and continuous-improvement processes it is employed extensively in the food manufacturing, health care,
and high-tech industries.

Benefits
01-05-2014 10:33

Eight Disciplines Problem Solving - Wikipedia, the free encyclopedia

3 of 4

http://en.wikipedia.org/wiki/Eight_Disciplines_Problem_Solving

Effective approach at finding a root cause, developing proper actions to eliminate root causes, and
implementing the permanent corrective action. Also helps to explore the control system that allowed the
problem to escape. The Escape Point is studied for the purpose of improving the ability of the Control System
to detect the failure or cause when and if it should occur again. Finally the Prevention Loop explores the
systems that permitted the condition that allowed the Failure and Cause Mechanism to exist in the first place.

Disadvantages
Requires training in the 8D problem-solving process as well as appropriate data collection and analysis tools
such as Pareto diagrams, Fishbone Diagrams, and flowcharts.

Problem Solving Tools


The following tools can be used within 8D:
Brainstorming
Trend Charts
Five Whys
Story Boards
Scatter Diagrams
Surveys
Check Sheets
Histograms
Fail-Safing
Pareto diagrams
Fishbone Diagrams
Flowcharts

Relationship Between 8D and FMEA


FMEA (Failure Mode and Effect Analsysis) is a tool generally used in the planning of product or process
design. The Failure Modes in a FMEA are equivalent to the problem statement or description in an 8D.
Causes in a FMEA are equivalent to potential causes in an 8D. Effects of failure in a FMEA are problem
symptoms in an 8D. The relationships between 8D and FMEA are outlined below:
1. The problem statements and descriptions are sometimes linked between both documents. An 8D can
utilize pre-brainstormed information from a FMEA to solve problems.
2. Possible causes in a FMEA can immediately be used to jump start 8D Fishbone or Ishikawa diagrams.
Brainstorming information that is already known is not a good use of time or resources.
3. Data and brainstorming collected during an 8D can be placed into a FMEA for future planning of new
product or process quality. This allows a FMEA to consider actual failures, occurring as failure modes
and causes, becoming more effective and complete.
4. The design or process controls in a FMEA can be used in verifying the root cause and Permanent
Corrective Action in an 8D.
The FMEA and 8D should reconcile each failure and cause by cross documenting failure modes, problem
statements and possible causes. Each FMEA can be used as a database of possible causes of failure as an 8D
is developed.[3]

See also
Corrective and Preventive Action

01-05-2014 10:33

Eight Disciplines Problem Solving - Wikipedia, the free encyclopedia

4 of 4

http://en.wikipedia.org/wiki/Eight_Disciplines_Problem_Solving

Failure mode and effects analysis


Fault Tree Analysis
Quality management system (QMS)
Problem solving
RPR Problem Diagnosis

References
1. ^ * Laurie Rambaud (2011), 8D Structured Problem Solving: A Guide to Creating High Quality 8D Reports,
PHRED Solutions (http://www.phredsolutions.com), 978-0979055317
2. ^ http://www.everyspec.com/MIL-STD/MIL-STD-1500-1599/MIL_STD_1520C_1489/
3. ^ http://www.quality-one.com/eight-disciplines/

External links
Society of Manufacturing Engineers: SME, [1] (http://www.sme.org/cgi-bin
/get-newsletter.pl?LEAN&20030116&1&)
Retrieved from "http://en.wikipedia.org/w/index.php?title=Eight_Disciplines_Problem_Solving&
oldid=605795179"
Categories: Quality Problem solving
This page was last modified on 25 April 2014 at 19:51.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may
apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia is a registered
trademark of the Wikimedia Foundation, Inc., a non-profit organization.

01-05-2014 10:33

You might also like