 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
 |
|
|
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
What is PS2? |
|
|
|
|
|
Summary: |
|
|
|
|
|
PS2 is an acronym for Problem, Solution, Periphery, Standardize. This tool was developed to systematically solve problems and prevent their repetition. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Problem |
|
|
|
|
|
The team should set a goal to measure the success of the PS2 activity at this phase. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Each PS2 activity must begin with a clear understanding of the problem. Begin by describing what occured, and the expected result vs. the observed result. |
|
|
|
|
|
|
|
|
|
|
|
|
|
The PS2 team shall invest sufficient time to understand the cause(s) of the problem, using any and all analytical tools available to uncover the root cause. Wherever possible, provide pictures, sketches, and analytical data to support the team's findings. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Solution |
|
|
|
|
|
A cross functional team shall brainstorm several solutions to the problem, addressing the root cause - recording all ideas. |
|
|
|
|
|
|
|
|
|
|
|
|
|
The list of solutions is to be analyzed for feasibility, cost, and effectiveness so that the alternatives may be ranked accordingly. |
|
|
|
|
|
|
|
|
|
|
|
|
|
At this point, an action plan is to be initiated for the favored solution |
|
|
|
|
|
|
|
|
|
|
|
|
|
Periphery |
|
|
|
|
|
Once the original problem has been addressed and results verified, the PS2 team shall seek other potential embodiments of the problem. Groups of products that share common components, designs, or processes are subject to the peripheral investigation. |
|
|
|
|
|
|
|
|
|
|
|
|
|
With other products susceptible to experience the same, or similar, problem identified, the team shall establish an action plan to prevent problem recurrance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Standardize |
|
|
|
|
|
The standardization phase of the PS2 plan is deceptively easy to mismanage or overlook. The corrective actions taken to resolve the problem shall be applied as a standard to prevent recurrance of the issue. Sketches, pictures, and data may also be required to make the new standard clearly understood. |
|
|
|
|
|
|
|
|
|
|
|
|
|
With the root cause and corrective actions known, the team must appropriately document the lessons learned. Appropriate locations to document the standard include, but are not limited to: intraweb documents, supplier quality manuals, design checklists, DFMEA, and PFMEA documents |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|