Page 31 - Injection Molding Advanced Troubleshooting Guide
P. 31

12    1 Troubleshooting Methodology




                  ƒ Is the new condition stable and capable of producing quality parts for the long
                 term?
                  ƒ Is there anything else that should be done to ensure an adequate process win-
                 dow?
                  ƒ Could this problem be affecting other product being produced?
                  ƒ Does something in the company systems need to be changed to prevent this
                 problem from reoccurring?
               During the proceed step of STOP troubleshooting it is important to remember to
               review the results. If a process technician or engineer makes a change and does not
               examine the results they will have no way of evaluating if the change made a differ-
               ence. There have been plenty of cases where a change was made and everything
               seemed good only for it later to be found that the data showed no difference.  Always
               compare the results from after the change with the baseline data to determine if
               the change truly made a difference.
               Some problem jobs may have a proceed step that lasts for an extended period of
               time to monitor the results to ensure that the problem has been eliminated. When
               all is said and done the data will tell the story.


               1.4.5„ STOP: Troubleshooting Cycle


               It is critical to understand that the STOP methodology should be used as a cycle.
               After proceeding to make change it is time to go back to Systematic, Think, and
               Observe to work through evaluating if the change had the desired impact and if
               not, why? See Figure 1.5 for an illustration of the STOP troubleshooting cycle.





                                               Systema c





                                    Proceed                  Think






                                                Observe



               Figure 1.5  STOP Troubleshooting cycle
   26   27   28   29   30   31   32   33   34   35   36