8 Disciplines

Solo disponible en BuenasTareas
  • Páginas : 9 (2011 palabras )
  • Descarga(s) : 0
  • Publicado : 13 de marzo de 2012
Leer documento completo
Vista previa del texto
8 DISCIPLINES PROBLEM SOLVING.

Concept.
Eight Disciplines Problem Solving is a method used to approach and to resolve problems, typically employed by quality engineers or other professionals.

History.
Ford Motor Company developed a method, while the military also developed and quantified their own process during World War II. Both of these methods revolve around the Eight Disciplines.Ford's Perspective.
The development of a Team Oriented Problem Solving strategy, based on the use of statistical methods of data analysis, was developed at Ford Motor Company. 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, theassignment 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 was piloted at World Headquarters in Dearborn, Michigan. Manychanges 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. The material is extensive and the 8D titles are merely the chapter headings for each step in the process. Ford also refers to their current variant as G8D (Global 8D).

MilitaryUsage

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

The 8D Problem Solving Process is used to identify, correct and eliminate recurring problems. The methodology isuseful in product and process improvement. It establishes a permanent corrective action based on statistical analysis of the problem. It focuses on the origin of the problem by determining Root Causes.

This 'Determine a Root Cause' step is a part of the military usage of the 8D's but was not a reference in the development of the 8D problem solving methodology and is not referenced or included inthe TOPS manual or course.

Usage & Modify

Many disciplines are typically involved in the "8D" process, all of which can be found in various textbooks and reference materials used by Quality Assurance professionals. For example, an "Is/Is Not" worksheet is a common tool employed at D2, and a "Fishbone Diagram" or "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 ResponseActions (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.
Additionof Escape Point to D4 through D6. The idea here is to consider not only the Root cause of a problem, but equally importantly, what went wrong with the control system in allowing this problem to escape. Global 8D requires the team to identify and verify this Escape Point (defined as the earliest control point in the control system following the Root Cause that should have detected the problem...
tracking img