Jun 30 2012
See on Scoop.it – lean manufacturing
This is what jidoka/autonomation is about! Contrary to what you read in the reductionist literature, jidoka is not just about stopping machines when they start to malfunction. It is instead a complete and intelligent approach to automation.
See on www.dcvelocity.com
Jun 30 2012
There have been several posts on this issue in The Lean Edge:
My own answer to the same question is as follows:
The first question to ask is the extent to which converting silos to process organizations should be done, and whether pursuing it at a given moment is opportune.
It is easy to overestimate the importance of organization structure. In discussions of these issues, American managers often use the following quote: “We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganized. Presumably the plans for our employment were being changed. I was to learn later in life that, perhaps because we are so good at organizing, we tend as a nation to meet any new situation by reorganizing; and a wonderful method it can be for creating the illusion of progress while producing confusion, inefficiency and demoralization” (C. Ogburn, Merrill’s Marauders, Harper’s Magazine, 1957). To emphasize how long this has been going on, many even falsely attribute this quote to Satyricon author Petronius, or even Cato the Elder.
It doesn’t mean, however, that organization structure is unimportant, only that changing it is not the right first step to solve a problem or implement change. What actually works is to start by changing the work that is being done, and then adjusting the organization to remove the friction caused by the changes. For example, in a machining job-shop, you would first implement some cells — moving the equipment and redesigning operator jobs — and then you would worry about changing the job categories in Human Resource policies to reflect how the work of cell operators differs from that of specialized mill or lathe operators.
The relative merits of functional versus process organizations have been widely discussed in both American and Japanese business literature, with various solutions proposed. In “Another Look at How Toyota Integrates Product Development,” (Harvard Business Review, July, 1998) Durward Sobek and Jeffrey Liker describe a functional organization with several twists added to ensure information flow between silos. One car company that did use an integrated team to develop a car is Ford, for the 1996 Taurus. All the product planning and engineering resources, including some representatives from Manufacturing, were collocated at one facility in Michigan. The approach did reduce the product development time but the resulting product, while great as a work of art and engineering, was not the market success that its designers had hoped, and the previous versions had been. For details, see Mary Walton’s Car.
In Electronics, a common approach has been to use “matrix organizations,” in which professionals report to both a process manager, for the work they do, and a functional manager for training, skills maintenance, and career planning.
When organizing around a process, we should always remember that Lean is about making it easiest to do what we do the most often. Putting together baskets of products around feature or process similarity is just classical group technology.The Lean approach starts with a Runner/Repeater/Stranger analysis to determine what it is we do often and what not. Without this analysis, we commingle in the same lines products made every day with other products made sporadically. In Japan, this is called P-Q, or Product-Quantity analysis, with the categories called A, B and C. The more vivid Runner/Repeater/Stranger terminology comes from Lucas Industries in the UK. You then use dedicated, integrated production lines for Runners, flexible lines for Repeaters, but a job-shop with functional groupings of equipment for Strangers.
Jun 30 2012
See on Scoop.it – lean manufacturing
Interview published in March, 2012.
It was prepared with your help, in the following posts:
Thanks for the many comments.
See on www.apd.es
Jun 28 2012
Mingled last night with 209 internet operations “ninjas” at the meetup of the Large Scale Production Engineering (#lspe) group, on Actionable Metrics, hosted by Yahoo! in Sunnyvale, CA, and heard speakers from collectibles marketplace site etsy, web performance testing service SOASTA, and video streaming service Netflix describe how they used metrics in their activities.
Both in style and content, the presentations were radically different from what I have heard in manufacturing on that subject. The speakers went fast, as if they were in a great hurry to give us as much information as possible prior to returning to work. They were also extraordinarily open about the tools they used and how they used them.
The first feature of their work that struck me was the simplicity of their dashboards. Almost all the charts they monitor are simple line plots of time series, free of the jumble of 3D pie charts, stacked bar charts, and other complicated displays commonly found on manufacturing dashboards. The most elaborate display showed a time series of, for example, login response times, with a dynamically adjusted confidence band based on a statistical model to help operations engineers tell significant changes from fluctuations. Yet, even with these features, the meaning of the chart was obvious, even to an outsider to their business. It is not difficult, for example, to understand a plot of the evolution of login times as the number of users grows or additional security is added.
As engineers tweak and enhance the functions provided on their servers everyday, they monitor metrics to see if it does any good, and take immediate action if it doesn’t. The time within which they can and must react is measured in seconds, not hours or days. Their metrics fall into the following categories:
Customer experience translates as is to a manufacturing context but Infrastructure, on the other hand, corresponds to Logistics, and Application to Production all with different time scales. While one of the speakers described response time as “one metric to rule them all,” none of the organizations presenting imposed any standard set of metrics on their engineers. Instead, they provide them with tools to capture the data, compute the metrics, display them on charts, and generate alerts, but it is their choice and their responsibility to define the metrics.
Response time is to their world what order fulfillment lead time is in manufacturing, but its importance is much greater. There are sectors in manufacturing where short order fulfillment lead times are a competitive advantage with customers, but also many, particularly with big ticket items, where other factors trump short lead times. If you are a farmer buying a tractor, for example, you will take one with the features you want over one you can have sooner that doesn’t have them. The pursuit of short production lead times has to do with other considerations, such as reducing inventory, detecting quality problems faster, or reducing the obsolescence cost of engineering changes. When providing services on the web, on the other hand, any slowdown in response causes customers to balk, and, internally, any increase in transaction processing time can cause servers to saturate and customer response times to explode.
For these engineers, capturing one metric is a matter of adding one line of code in their software, and they use open-source tools to generate plots and dashboards. It is not difficult to do. The hard part is identifying the right metrics. The Netflix speaker was quite aware of this. After someone had him “No matter what you measure, it’s useful,” he charted the evolution over one year of the proportion of user IP addresses ending with an even number.
Jun 27 2012
See on Scoop.it – lean manufacturing
Author encourages kaizen methods to improve healthcare (San Antonio Express) The book, published Wednesday, highlights lean management practices, which focus on methods of daily continuous improvement, or “kaizen,” for healthcare …and more »…
See on www.mysanantonio.com
Jul 3 2012
A Video Showing Office 5S Gone Wrong
See on Scoop.it – lean manufacturing
Not fresh news, but my colleague Maria Samsonova just pointed it out to me.
See on www.leanblog.org
Share this:
Like this:
By Michel Baudin • Blog clippings • 2 • Tags: 5S, Office Lean