"Houston, we [the Germans] have a problem." | Bodo Wiegand | Wiegand's Watch

Bodo WiegandBodo Wiegand heads the Lean Management Institute, which is the German affiliate of the Lean Enterprise Institute. In his latest newsletter, on Wiegand’s Watch, he discusses the significance of recent problems in well-known German corporations, specifically VW, Siemens, and Deutsche Bank. The VW emissions test scandal has been covered in the media worldwide. Siemens executive were indicted for bribery last year in Greece, for acts related to the Athens Olympics in 2004, and the top management of Deutsche Bank was replaced in 2015 after scandals that included manipulating the London inter-bank lending rate (Libor), and mis-stating financial reports.

Continue reading

Is Vendor Selection Really The First Step in ERP Implementation?

A free guide that you can download from ERP Focus makes vendor selection the first of an 11-step implementation process, while defining success is the last.  In other words, they have you choose who you buy from before having a clear idea of what you are trying to accomplish.

It reminds me of a meeting at a client site where ERP implementation was about to begin. "This train has left the station," I was told. The purpose of the meeting was to draw a "Value Stream Map" for the whole plant, in preparation for ERP, and the participants included managers from Manufacturing, Quality, Production Control, Maintenance, Purchasing, Sales, and Engineering.

Continue reading

What Went Wrong? (With Lean) | Bob Emiliani

Can Lean do a do-over? Nearly 30 years after the start of the Lean movement, there is widespread agreement that things have not gone according to plan.

Sourced through Scoop.it from: www.bobemiliani.com

 

 

Michel Baudin's comments:

Bob's title for the article is just "What Went Wrong?" which I feel needs to be set in context.

I agree with him that the most popular "Lean tools" are peripheral at best. None of the ones he mentions -- 5S, visual controls, value stream maps A3 reports, or gemba walks -- would make my list of what should be taught and applied first in a Lean manufacturing implementation. I would, on the other hand, include SMED, cell design, assembly line design based on takt time, etc.

Continue reading

Lean’s Midlife Crisis | Bob Emiliani

"It seems to be common knowledge that the Lean movement is now suffering from a midlife crisis. Lean movement leaders are perplexed at the widespread continuing emphasis on Lean tools, narrow focus on cost cutting, and the slow uptake of the “Respect for People” principle over the last 15 years. This is the outcome, despite determined efforts to inform people otherwise. I’m not surprised."

Sourced through Scoop.it from: www.bobemiliani.com

 

Michel Baudin's comments:

While I agree with Bob's overall diagnosis of a midlife crisis for Lean, I object to a few details, the main one being his assertion that Lean descends directly from "Scientific Management," the brand under which Frederick Taylor sold his consulting services.

Continue reading

A critical look on Industry 4.0 | Christoph Roser

One of the hottest buzzwords right now (at least in Germany) is Industry 4.0. However, it’s a bit fuzzy what Industry 4.0 is, exactly. In this post I would like to talk about Industry 4.0. This includes very little about all the promises of a wonderful future – you can read that elsewhere. Instead, I will try to give you the big picture. I will talk about how Industry 4.0 came into existence, why it is so popular, what the true current benefit of Industry 4.0 is, and why you should pay attention to clothes.

Sourced through Scoop.it from: www.allaboutlean.com

Continue reading

How Can I Speed Up My Team’s Lean Learning?

"How can I speed up my team’s lean learning?" is a question found on the web, with no context given: we don't know whether it is team of managers, engineers, or operators, or whether it works in manufacturing, finance, or health care... We can infer from the tone of the question that its author is a leader frustrated with the pace of a team's progress. I will further make the assumption that the concern is not just about skills but also about principles. It's not just about know-how but also know-why, as it is essential to address new challenges.

Then we also need to make a distinction between learning as a team and learning by team members. You hear leaders say "as a team, we have learned to change over a lathe in 7 minutes," or "as a team, we have learned to introduce a new product on this line in 3 weeks." If such a team replaces one of its members, it can bring the newcomer up to speed and retain the skills and the knowledge; if, on the other hand, it replaces half its members, it has to relearn. A team  is more than the collection of its members, but it builds on the expertise of its members, which means that their individual expertise also needs to be nurtured. This means that individual learning by team members also is a topic that must be addressed.

Continue reading

Lean Coffee

Lean Coffee in Palo Alto

The first Palo Alto Lean Coffee happened this morning, as planned, at the Palo Alto Cafe, with Paul Zhao and me. We didn't know each other, and connected through Meetup. Paul is involved with a startup company aiming to be "Uber for 3D printing," connecting users who have designs with shop that have 3D printers. Our discussion was centered on manufacturing strategies for startups with hardware products, a topic I expect to come up again in Palo Alto.

Palo Alto Cafe Front at Night

Inaugural Lean Coffee on 12/17 7:30 AM at Palo Alto Cafe

David Veech last week suggested I start a Lean Coffee in Palo Alto. It seems like an attractive format, and I hope you find it useful.

It is scheduled early in the day to minimize interference with work. You don't have to prepare anything. You come as you are, and I will provide Post-It notes for us to set an agenda when we start. Then we will discuss all the items agreed on, each participant contributing on the fly from his or her experience. It's at the Palo Alto Cafe, and we can each enjoy coffee, bagels, muffins, or croissant-egg scrambles while letting others talk.

RSVP if interested.

 

 

Industry 4.0: Without Stable Processes, Nothing Works | Wiegand's Watch

This is a translation of Bodo Wiegand's latest newsletter, about Lean in Germany, followed by my comments:

This week I was with a company that is on its way to implement industry 4.0. All machines were networked. The manager could see from his desk which machines were running and which were not. All data were collected centrally and also shown locally to the machine operator. The trend was easy to see. One third of the machines had a malfunction. With an average OEE of 62%, the machines do not always run.

"As long as we buy new machines, we have to live with this," was his answer to my question.

But, it was not only the newest, but also the older machines that don't need to be smeared with oil and dirty, even even while generating chips. Provided on request, the Fire-Fighting-factor reported to us by the maintenance technicians was above 75%. The chief knew exactly: 76.6%. An OEE of 62% and 76.6% Firefighting means in plain language: In this business, there is no stable processes.

But what drives intelligent managers then to link his whole company, only to find that the processes are unstable? With some thought they could have discovered this without networking and invested first in stabilizing the processes. Introducing Industry 4.0 For industry on unstable processes will fail. The crucial question: how I manage to stabilize the processes and avoid unplanned shutdowns?

Continue reading

What Poka-Yoke Are And Are Not, And How To Sustain Them

Chet Marchwinski recently exhumed a 2011 discussion about Poka-Yoke that had been started by the following question:

I’m a manufacturing engineer and since I have started participating in kaizen workshops, I have noticed that production supervisors tend to disconnect some of the poka-yokes we’ve put in place in the machines. When I challenge them about this they argue that operators can’t run production and cope with the complexity of our machines. I am perplexed by this and wondered whether you’d have a comment.

In short, I can think of two reasons for production supervisors to disconnect Poka-Yoke:

  1. No production supervisor in his right mind would disconnect devices that make the work easier for operators. If they do disconnect them, the most likely explanation is that the devices described as "Poka-Yoke" actually add work for the operator. If you have to pick a part from one of ten open bins in front of you, you will spend precious seconds finding the right one; if all bins are covered with lids except the right one, not only are you physically prevented from picking the wrong one but you don't have to look for it. It makes your job easier. On the other hand, if you have to scan a bar code on the part to validate the pick, it adds to your work load and your supervisor will pull the plug on the next production rush.
  2. The manufacturing process is not ready for Poka-Yoke. A production supervisor is quoted in the question as saying "operators can’t run production and cope with the complexity of our machines." This suggests that the line has process capability issues that must be addressed before implementing Poka-Yoke.

The following paragraphs elaborate on these points.

Continue reading