Archives for category: RCO

I went to the dentist today. This is the first time in over 6 years. I know, I know. Every 6 months. I felt bad for the dental hygienist but it was a great forrm work out. Anyway, they wanted to do x-rays and they put the film holder in my mouth with a circle on the end. The picture is below. When I asked what it was for they said it helped line up the camera with the film. I thought it was a cool idea. I think it is called a Rinn. It seemed faster than I remember though I wasn’t timing it in the past. I wonder how many images had to be redone because the film didn’t line up with the camera.  I was also wondering how else this concept be used. Could this help with packaging materials that need to be centerlined but the operator can’t see or reach the material due to guarding or confined space issues. What other applications can you think of for a device that lines up a tool you can control and a mating piece that you can’t?



Most continuous improvement projects need a payback or at least a justification to do the project. Does it cut inventory? If so, by how much? Does it improve speed to market of a new product or existing product? If so, how much more will the customer be willing to pay for it? How much will be realized this fiscal year versus next? These are valid questions and have their place but how often have you found that a company or production site or office and there aren’t any work instructions or standard work?

Can you do a “black belt project” based on just writing down what everyone does, train to that procedure, and then audit the process instead of the people? Is it the threshold of $250K annual savings? I don’t know how you would state it financially but I will say that it is either priceless or at least a requirement before any CI activities take place at the site. And I would say that the CI leader should state as much before getting involved or capturing any savings.

If you do start CI activities in this environment, it is usually unsustainable or one has to become very creative to justify the project and / or the savings. A simple checklist is not a rapid changeover. But is it necessary? Yes. Can there be a successful improvement without it? No. Can anyone really quantify the savings of eliminating chaos or at least limiting the outliers?

When focused on the basics, there may not have been a P&L impact but the work day seems to be “easier.” Not as many fires to put out, not as many discussions with the phrase,” you have got to be kidding, me?” or “It happened again?” started.

If there are not checklists, work instructions, standard work and training, you will not know what an outlier is, what the direction or action should be and what effect, if any, it will have on the customer’s experience, but you will sure be busy cleaning up the crisis du jour that management wants you to clean up by the end of the day.

I was working in a site that wanted and needed a better changeover process on some of their production lines. This site was set up so that there was only 1 maintenance person per line per shift but there was also a 3 hour overlap on some days. We went through the traditional 4 step approach but there was an added complexity to the changeover. The employees who did the changeover were rarely the ones that were there during start-up.

Though the leadership knew this was the right thing to do, it was hard to free up the resources and the time required to do the project effectively. So I came up with a small team, 1 or 2 maintenance techs and 1 operator, to work this process. Also, I did not have any traditional sitdown meetings. We met on the line, during production or changeover and pulled the process together. Even though it was a small group, we were getting a lot accomplished.

Because of this, we developed a feedback loop. We would do the changeover and document the steps, move from internal to external, stream line internal events and the I would come back during production, when the lines was running in steady state, and document the changes, if any, were made. I worked with the operators as well as maintenance staff on the process. Checklists were developed for each type of package. Good stuff.

So we were going into a package change on a Monday to Tuesday and I had sent out the checklists and told the maintenance person to call me when the changeover started so I could document the changes. I also stated in the email that I may not be able to get there due to other commitments but give me a call anyway. I did not receive a call and got up when I normally do. I figured he either got tied up or the changeover was quick and he didn’t need to call. That had happened on occasion.

I get to the site and the first thing I notice is that there is no primary packaging staged for the run. This was around an hour before production so it wasn’t a huge concern but still odd. Then I ran into the maintenance tech.

“Hey, where’s Dave?”, I asked.
“He called off.” he stated

That was not a good sign since he was the one I had been working with and he had the checklists. I reviewed the checklist on the equipment while the maintenance tech worked on another issue. There were packages that had run through the equipment that seemed to be used as “test subjects” to tweak the set-up. Were the settings correct. Nope. In his defence or mine, he had run some product through and it seemed to be working. What did I do? I thought that since this product was slightly different from the one documented, may be it would be okay. Guess what? It wasn’t.

After 2 hours of adjustments and several tongue lashing, we finally got the line running where it should have been. How close was the checklist. Very close but, even at that, there were still some adjustments that we had not captured earlier. This made every one very disappointed in the results for that day.

After discussing the issue with the production manager and site manager, I admitted that it was my fault and that even though the small team had done some great work and that it was still a work in progress, the communication of current state and next steps hurt everyone. What did I do differently?

Made sure the team as well as anyone the team was in contact with related to the project was aware of what was going on and why.

Made sure that there were regular, and timely updates and training where needed. This meant a weekly stand up meeting or posting on the bulletin board of where we were and what’s next.

Didn’t just ask but solicited thoughts on the project and how we could make it better both from stakeholders and those outside the impact zone so that we could incorporate them into the project.

In end, it came out okay and the team was recognized for their good work and the efficiency of the line improved dramatically. The lesson learned – Even if you have a small team working under the radar, you need to broadcast periodically where you are using the radar.