Therefore, the part not properly installed would be listed in the Ishikawa diagram. In this example, lighting could cause an employee to make a mistake resulting in a part not properly installed. Instead, the result of bad lighting should be listed and then empirically investigated. For example, “lighting” is a typical example under “environment” however, it is seldom clear how lighting could lead to the failure. Figure 1: Ishikawa Diagram How Did the Failure Happen?Įlements in the Ishikawa diagram should be able to explain how the failure happened. Hypotheses that have been investigated can also be marked on the Ishikawa diagram to quickly show that they are not the cause of the failure (Figure 1). It serves to quickly communicate these hypotheses to team members, customers and management. An Ishikawa diagram should be viewed as a graphical depiction of hypotheses that could explain the failure under investigation. A good problem statement would be: “Customer X reports 2 shafts with part numbers 54635v4 found in customer’s assembly department with length 14.5 +/-2 mm measuring 14.12 mm and 14.11 mm.” Create an Ishikawa DiagramĪn Ishikawa (or fishbone) diagram should be created once the problem statement is written and data has been collected. For example, a problem statement may start as, “Customer X reports Product A does not work.” The rest of the problem statement would then clarify what “does not work” means in technical terms based upon the available data or evidence. The customer’s description does not need to be correct it should reflect the customer’s words and be clear that it is a quote and not an observation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |