Nov 1 2011
Design First, Lean Second: A Case Study
Via Scoop.it – lean manufacturing
For when you are not stuck with a 10-year old design…
Show original
Nov 1 2011
Via Scoop.it – lean manufacturing
For when you are not stuck with a 10-year old design…
Show original
By Michel Baudin • Press clippings, Technology • 0 • Tags: Lean manufacturing, Manufacturing engineering, Manufactuting
Nov 1 2011
To be useful, a metaphor must help understanding. For the promoters of Six Sigma to call their certification Black Belt was marketing genius. A more descriptive label might have been Staff Statistician, but what self-respecting manufacturing professional would want to be that? Borrowing a term from Japanese martial arts not only appealed to their fighting spirit, but also gave the impression that an approach developed at Motorola in the US had a connection with Japan, ground-zero of manufacturing excellence. Even in Japan, Black Belt (“Kuroto”) and White Belt (“Shiroto”) have migrated from martial arts to everyday language, to designate respectively a real pro and an amateur.
As a metaphor, Black Belt also made sense because there is a parallel between the Six Sigma and martial arts training programs. Traditional masters in the martial arts of China trained one or two disciples at the Bruce Lee level in a lifetime, just as universities trained only a handful of experts in statistical design of experiments that could be effective in electronics manufacturing. One Karate instructor, on the other hand, can train hundreds of Black Belts, just as a Six Sigma program can teach a focused subset of statistical design of experiments to hundreds of engineers.
Scrum, in software development, is also a sports metaphor, a term borrowed from rugby, which few Americans know. The connection between a rugby scrum and what software people call by the same name, however, is not obvious. A rugby scrum involves the forward players of two teams locked in the pattern of Figure 1.
Figure 1. A rugby scrum
The ball is released in the middle of the scrum and both team try to take possession by kicking it backwards while pushing the other team forwards. It is exciting and bruising to participate in, as well as a great spectacle. For software developers, scrum is an approach to project management illustrated by the status panel in Figure 2.
Figure 2. A software development scrum
It leaves you wondering what plays the role of the opposing team, the ball, or the player positions. In other words, in what way is a rugby scrum a metaphor for this approach at all?
By Michel Baudin • Management • 11 • Tags: Management, Product development
Oct 28 2011
A speaker I once heard on manufacturing metrics started with a quote from football coach Vince Lombardi: “If you’re not keeping score, you’re only practicing.” In a sport, your score or your rank is, by definition, the correct measure of success, and we assume too easily that this kind of thinking crosses over to every human endeavor, from national economies to plant performance or education. In this process, we begin using highly aggregated metrics as if they were physical measurements like mass or speed, and avert our eyes from how these sausages are made.
Following are a few of the egregious examples:
Fiber calories are included in nutrition information, but only in come countries. In the US, it is legal to not put in fiber calories because they are not digestible. Therefore, they do not “count” as such. however, if you, like most people, tend to underestimate cals sightly, there is nothing wrong with including them to create a “buffer zone.”
In other words, it makes no sense but you should pretend it does.
Do we behave the same way in the manufacturing world? Yes. For example, many companies measure productivity in terms of Sales/Employee. There is an easy way to boost this metric: outsource all production, close all plants and become a trading company. It is not easy to find metrics for quality, cost, delivery, safety, and morale that are meaningful and cannot be gamed, but it can be done. For overall company productivity, for example, you can use Value added/Employee, where
Value-added = Sales – (Materials + Energy + Outsourced Services)
This is what Peter Drucker called Contributed Value. Value added/Employee is not a perfect metric, but at least it does not provide a perverse incentive to outsource, and the US census bureau publishes statistics on value-added and employment by industry, that are helpful for benchmarking.
Following are a few conditions that a good metric must meet:
Peter Drucker sold corporate America on the idea that you can’t manage what you can’t measure, and this has led many managers to believe that employees would do whatever it takes to maximize their scores. Given flawed metrics, it if fortunate for the companies that these managers were wrong. If they had been right, all the companies that measure productivity in terms of Sales/Employee would actually have outsourced all production. They didn’t, because metrics are only one of many factors influencing behavior. Most employees, at all level, will not maximize their metrics through actions they feel violate common sense or are inconsistent with their personal ethics.
By Michel Baudin • Metrics • 12 • Tags: industrial engineering, Management
Oct 27 2011
We have all seen the absurd situation in the featured picture above of a line of customers waiting for taxis while a line of taxis next to them is waiting for customers, with a barrier separating them. This particular instance is from The Hopeful Traveler blog. The cabs are from London, but the same scene could have been shot in many other major world cities.
I am sure we have all encountered similar situations in other circumstances, which may or may not be easy to resolve. One particular case where it should be easy is the restaurant buffet. Figure 1 shows a typical scene in buffet restaurants, with a line of people waiting to get food all on the one side of the table, while food is waiting and accessible on the opposite side.
Figure 1. A typical buffet
I think the fundamental mistake is the assumption that a buffet is like an assembly line, providing sequential access to dishes. This means that you cannot get to the Alo Gobi until the person in front of you is done with the Tandoori. The ideal buffet would instead provide random access, meaning that each customer would have immediate access to all dishes at all times. While it may not be feasible, you can get much closer to it than with the linear buffet. The following picture shows an alternative organization of a buffet in circular islands that is non-sequential.
Figure 2. A buffet island at the Holiday Inn in Visalia, CA
The limitation of this concept is that replenishment by waiters can interfere with customers. To avoid this, you would want dishes to be replenished from inside the circle while customers help themselves on the outside, as in the following sketch:
Figure 3. A buffet island with replenishment from inside
One problem with the circular buffet island, however, is its lack of modularity. You can add or remove whole islands but you cannot expand or shrink an island, which you can if you use straight tables arranged in a U-shape, as in Figure 4.
Figure 4. Buffet island with straight tables
This buffet island may superficially look like a manufacturing cell, but it is radically different. Its purpose is random access to food as opposed to sequential processing of work pieces, and the materials do not flow around the cell but from the inside out.
Such are the thoughts going through my mind while munching on the Naan at Darbar.
By Michel Baudin • Technology • 3 • Tags: Buffet, industrial engineering, Lean manufacturing, Restaurant
Oct 26 2011
Data mining, in general, is the retrieval of information from data collected for a different purpose, such as using sales transaction histories to infer what products tend to be bought together. By contrast, design of experiments involves the collection of observations for the purpose of confirming or refuting hypotheses.
This perspective on data mining is consistent with the literature in expressing purpose, but most authors go further. They include in their definitions that data mining is done with computers, using large databases and specific analytical tools, which I think is too restrictive. The tools they list are the ones they have found useful in analyzing the behavior of millions of users of search engines or commerce websites, and they are not obviously applicable in other areas, such as manufacturing.
During World War II, British analysts used the serial numbers of captured or destroyed German tanks to estimate the numbers produced. Because serial numbers were not attached for this purpose, it was data mining. It used clever statistical models but, obviously, no computers.
Today, PhD-level data miners at Google, eBay, or Amazon sift through the page views and click-throughs of millions of users for clues to patterns they can use. The data, automatically collected, is accurate and collected by the terabytes every day. This “big data” requires parallel processing on clusters of computers and lends itself to the most advanced analytical tools ever developed.
Compared to this fire hose of data, what manufacturing produces is a trickle. In a factory, the master data/technical specs, plans and schedules, status of operations and work in process, and the history of production over, say, 12 months, usually adds up to a few gigabytes. It doesn’t fit on one spreadsheet, but it often does on a memory stick. On the other hand, much of it is still manually generated and therefore contains errors, and it is often structured in ways that make it difficult to work with.
Even if manufacturing companies could hire the data miners away from their current jobs, their experience with e-commerce or web search would not have prepared them well for the different challenges of manufacturing data mining.
There is an opportunity for data mining to contribute to competitiveness in manufacturing, but the approach must start from the needs. It must not be an e-commerce cure in search of manufacturing diseases.
By Michel Baudin • Technology • 0 • Tags: Data mining, Lean manufacturing, Manufactuting
Nov 2 2011
Lean Reflections on Temple Grandin
Via Scoop.it – lean manufacturing
I just wish we would talk more about Temple Grandin’s work than her autism. Like Sakichi Toyoda with looms, she focused on one of the oldest economic activities, raising cattle, and made it better by observing details nobody else cared about. Even for a non-cowboy, her Humane Livestock Handling is fascinating. Professionally, autism may have hindered or helped her. In any case, it is something she was born with, not something she accomplished. Having >50% of all cattle handling facilities in the US based on her designs is an accomplishment.
Show original
Share this:
Like this:
By Michel Baudin • Press clippings • 0 • Tags: Line design