Go to Post Nothing worse than an intolerant field :D - JB987 [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #1   Spotlight this post!  
Unread 15-07-2012, 08:13
IKE's Avatar
IKE IKE is offline
Not so Custom User Title
AKA: Isaac Rife
no team (N/A)
Team Role: Mechanical
 
Join Date: Jan 2008
Rookie Year: 2003
Location: Michigan
Posts: 2,149
IKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond reputeIKE has a reputation beyond repute
[ER] Fishbone or Ishikawa diagram

Within the Einstein Report, it mentions the use of a Fishbone Diagram:

"As part of the investigation, Ted McKain, formerly the Technical and Quality Director for Rolls Royce North America, currently retired, and a consultant to Rolls Royce, came to FRC headquarters to work with the FIRST staff. With his support, a complete list of possible causes for command response failures was compiled into a fishbone diagram."

I created this thread because many in FIRST probably do not have exposure to using such a tool. Many problems are easy to diagnose, and you can just do some poking and prodding. For the tough ones, or the ones that you are going to have to answer to an audience that won't accept your "first guess", a Fishbone diagram is a good way to start. A Fishibone diagram is alos known as an Ishikawa diagram. While the diagrams by themselves do not solve problems, they are a great tool for organizing thoughts and possible causes in order to prioritize testing and analysis to find the actual root cause. These documentation tools are really helpful to ensure that all possible causes are thought of and evaluated, and to make sure you are not just treating the symptom, but looking for the root cause as well. They still require the knowledge and expertise to list all the possible causes, as well as the expert judgement to prioritize possible causes and get rid of the most likely non-contributors. I have found that these are especially useful when you have a group of experts of particular fields all working on the same problem which is likely why the quality expert of a jet engine company was called in to organize the thoughts of a group of 18 experts with the variety of expertise this group had.

Note this style of problem solving is good for both manufacturing, product development, as well as the service industry.

I have often thought that while watching "House", that it would be worth-while for someone to teach him how to make an Ishikawa diagram to focus there efforts, and possibly make a less mistakes. Of course, that would mean the programs would be 30 minutes of Ishikawa development, 20 minutes of testing, and a lot fewer near death moments which is probably not good for television.

Last edited by IKE : 15-07-2012 at 08:23. Reason: Added a reason for the thread.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 03:26.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi