Cause and Effect
Analysis:
The team carried out a cause and effect
analysis on all of the issues that were
identified during the measure phase.
We performed this at a scheduled workshop that was an extension of the
weekly team meeting. We used the standard
categories of this tool to try and understand the root cause of each issue:
The team found this tool to be really useful as it helped us to identify a root cause for each issue and propose a recommendation.
Following the cause and effect analysis we gathered all of the information and broke each issue into three categories - Observation, Risk & Recommendation. The team put these into a powerpoint presentation to visually outline each issue. We found this to work well as it helped us to visually display the risks identified and recommendations to improve them. We used the following template to show this information.
Process Map Review and Analysis:
The team mapped the process during the Define/Measure phase. It was now time to carry out a robust review and analysis on the map. The team also identified where there are risks to the process during each step using a basic risk analysis tool. This worked well for the group and created a lot of discussion about what the risks during each step of the process are.
Ideal State process sequence re-mapped and documented:
The ideal state process sequences were re-mapped and documented following the review and analysis. As the team identified where there are risks to the process during each step, we decided to highlight these using warning symbols. This will allow the team to develop the best practice method for each step involved whilst taking these risks into consideration. You can see a screenshot below for each of the symbols that we used and an example of the process map.
Key findings of Analyse phase:
As
a group we conducted an exercise to summarize our findings during the analyze
phase of the project, so we would remain focused as we prepared for the improve
phase. We identified 8 key improvements that we will focus on during the improve phase.
|
Sunday, 24 March 2013
Analyse
Friday, 8 March 2013
Measure
Data Collection Plan
A data collection plan was developed to outline the data the team needed to collect and how it should be captured and recorded. The following headings were used for this;
- What is being measured
- Measure/Data type
- How measured
- How and where recorded
Team Brainstorming (Current state - Ideal state)
At one of our team meetings we held a brainstorming session to determine the current state issues and what the ideal state should be.
This session proved to be really worthwhile as it opened up a very honest and frank discussion with the team as to what some of the issues are. The production staff are working closest to the process so are in the best position to outline what the critical issues are. In some cases it was a surprise to the department manager and engineering that there are such problems with the equipment and the process. At times production and engineering can blame each other when issues occur during the production process. As a team we felt that this exercise helped to break down some of those barriers.
Detailed Process Mapping
We mapped the process from a high level as part of the define phase so we needed to drill down on the process a bit further to understand what the actual flow is. There was a lot of discussion when the team were doing this. It became apparent that each shift carries out the process in a different sequence and there is no clear standard in place. Again this tool was highly successful as it created excellent discussion and understanding of the process among the group.
As a team we documented the process to the best of our ability. We would then have to verify it with the other production staff at the second round of workshops.
GEMBA - Process Observation sheet
The team carried out a number of observations on the process. The purpose of these observations was to observe issues with the assembly/disassembly process and to time the sequence. During the define phase a number of problems were identified in relation to the quality of the process and the variation around standard operating times. These observations were carried out to verify that data. We used a basic process observation sheet for this and took numerous pictures of the equipment and the process. You can see the template we used to observe the process below.
In my opinion, this was one of the most useful parts of the measure phase as we began to really understand the process and current issues, as we were observing the process live.
GEMBA -Spaghetti diagrams
During the observations we also used spaghetti diagrams to map out the movement within the process room so we could identify waste in motion. This tool has identified a huge amount of waste due to movement within the room and outside the room looking for tools and parts. This has helped the team to understand why there is such variance around standard operating times for comprehensive cleans.
VOC Workshops - Part 2
Following the above data collection the team led another set of workshops with each of the production crews. We used these workshops to verify the process flow and to present the data that was gathered during the observations. The second set of workshops were a much more positive experience for the team, as the production crews seemed more engaged due to the fact they have taken part in a lot of the observations that have been carried out.
The project is now well into the analyse phase. The team are beginning to prepare for the improve phase which will be completed as a week long Kaizen event. The team will work together for the full week to identify solutions to problems that have been recorded and prepare any necessary documentation that is required. This will be the most challenging part of the project to date.
Subscribe to:
Posts (Atom)