Michel Baudin's Blog
Ideas from manufacturing operations
  • Home
  • Home
  • About the author
  • Ask a question
  • Consulting
  • Courses
  • Leanix™ games
  • Sponsors
  • Meetup group
Traffic light

Nov 21 2011

Communication challenges in multilingual organizations

This was a post in the discussion  in the AME discussion group on LinkedIn that Karen Wilhelm prompted with the following question:

Karen Wilhelm: What languages are spoken at your facility? How do you manage the communication challenge? No matter where a factory, or even an office, is situated, there are likely to be several languages spoken by employees. In your experience, how does that affect employee involvement, company culture, daily performance, and safety? What are your strategies for bridging language differences?

Written communication can be addressed more easily than oral communication, by using photographs, drawings, cartoons, pictograms, ideograms and color codes as much as possible. It works, but only as a short term solution: these symbols amount to a new language that the participants need to learn, so you don’t want to overdo it. In the long run, the work force should be proficient and literate in the local language, and you should do what it takes to get it to this point. If you don’t want to make language proficiency a prerequisite in hiring, then you must provide in-house language training.

A good example of a system understood across multiple languages is traffic signals in Europe that contain no words and are understandable to a Lithuanian truck driver on the road in Portugal. This system is easily learned as part of basic driver’s ed. The Chinese writing system is another example that, for over 2,000 years, has allowed written communication among people who speak dialects like Mandarin and Cantonese that are as different from each other as German and French. But it takes 10 years to learn.

Spoken communication in the work place is more problematic because it is more difficult to control. You can’t prevent two operators from using a common native tongue when talking to each other, but it has the effect of excluding third parties, which, immediately causes interpersonal problems and may impact quality, productivity, and even safety. In factories that are foreign transplants, expatriate managers often have discussions in their own language, which accidentally or deliberately keeps locals out of the loop.

While it is reasonable to expect shop floor operators to master English if the plant is in the US, or Spanish if it is in Mexico, you cannot expect them to also learn Swedish because it is owned by a company based in Stockholm. At the management level, multinational companies usually have an official language in which everyone is supposed to be professionally functional. And managers make a point of never using any other language in a mixed group. For example, two Swedes in the privacy of an office may converse in Swedish, but switch immediately to English if an Italian joins them.

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • Management • 6 • Tags: Management

OLYMPUS DIGITAL CAMERA

Nov 20 2011

Russian award for manufacturing excellence named after A. K. Gastev

In any country, if you can present Lean as the continuation of the work of local pioneers, it is easier to implement than as a wholly alien concept. Lean’s debt to Ford, Taylor, Gilbreth, the TWI program, and others is acknowledged in Japan, which makes the connection easy to make in the US. In Russia, it was more of a challenge.

At OrgProm in 2008, Mikel Wader first told me about Gastev, who was by then so obscure that his books had not been reprinted in 40 years and it took months for OrgProm’s Julia Klimova to locate copies for me. A quick look at Gastev’s works then convinced me that he was indeed someone Russians could look up to as a precursor to Lean. Alexey Kapitonovitch Gastev (1882-1939) was the father of industrial engineering in Russia, creator of the Central Institute of Labor in Moscow in 1920, author of How Work Must be Done (Как надо работать) and Worker Training (Трудовые установки).  Through an example,  Figure 1 illustrates his thinking. His career was cut short when the government shot him as a “counter-revolutionary” in 1939.

Figure 1. Gastev’s sketch of multiple phases of improvement on a tube piercing operation

In 2008, OrgProm was already making efforts to naturalize Lean for Russia, for example by using the graphic style of soviet-era posters in illustrations of 5S. In the same spirit, I thought that establishing a “Gastev Prize” for manufacturing excellence would also make sense and suggested it. OrgProm followed up, and I was pleased this morning to receive the following notice from Omsk University’s Konstantin Novikov:

PROJECT OF THE YEAR: CUP, AK Gastev.
Gasteva Cup – a public initiative, Interregional Public Movement “Lin-Forum. Professionals lean manufacturing. “It lies in the organization and conduct of national competition efficiency of production systems among the leading companies. Companies may be nominated for the award and the Cup as Gasteva program effectiveness and individual projects. Results evaluates expert group, consisting of the most respected and experienced expert consultants on operational efficiency and top managers of successful companies. The award ceremony will be held Gasteva Cup on November 15-18 at the VI Forum “Development of production systems” (up to 2011 – Russian Lin forum “Lean Russia”).

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • History, Management • 4 • Tags: industrial engineering, Lean, Management

Nov 19 2011

Is it true that you get what you measure?

Via Scoop.it – lean manufacturing

The article Lean Manufacturing: Measuring To Get Results by Gerald Najarian lists a number of useful metrics. It also opens with the saying, or cliche, that “you get what you measure.”

The implications are (1) that people will always do whatever it takes to maximize their metrics, and (2) that, if you put the right metrics in place, improvement will take care of itself.   While I agree that we need good metrics, we should not overestimate their impact. Peer pressure and personal ethics, among other factors, drive most people more than their performance metrics. And even when employees do their utmost to maximize their scores, they often do not have the necessary skills, and performance targets will have no effect unless backed up by some form of training, coaching and support.
Via ezinearticles.com

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • Metrics, Press clippings • 35 • Tags: Lean, Management, Performance

Nov 18 2011

What’s unique about the Kanban system? (Revisited)

10 years ago, I wrote an article by this title in Karen Wilhelm’s Lean Directions, and a detailed treatment of pull systems in Lean Logistics, pp. 199-270 (2005). While 6 to 10 years in an eternity in Information Technology, it is not in Manufacturing, and I have not seen evidence that technological advances since then have invalidated these discussions yet. Also in 2005, Arun Rao and I wrote a paper on RFID Applications in Manufacturing, which outlined ways this technology could be used, among other things, to implement the Kanban replenishment logic on the side of an assembly line. To the best of our knowledge, it still isn’t broadly used, and bar codes are still the state of the art on the shop floor.

For placing orders with suppliers, on the other hand, the recirculating  hardcopy Kanban has never really taken root in the US, and orders are usually placed electronically. When Kanbans are used with suppliers, they are usually single-use cards printed by the supplier to match electronic orders, that are attached to parts and scanned when the corresponding parts are consumed to trigger a reorder. This is the eKanban system, and more a horseless carriage than a car, in that it is an electronic rendition of a system whose logic was constrained by the use of cards.

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • Technology • 0 • Tags: IT, Kanban, Lean manufacturing

Nov 18 2011

At 25, Toyota plant still lean, flexible, world-famous | Op-Ed | Kentucky.com

Via Scoop.it – lean manufacturing

An important milestone in automotive manufacturing is taking place with Toyota’s celebrated Georgetown plant marking its 25th anniversary on Monday.
Via www.kentucky.com

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • Press clippings • 0 • Tags: Lean assembly, Lean manufacturing, Manufactuting, Toyota

Greek temple diagram

Nov 17 2011

Jidoka versus automation

Toyota’s jidoka isn’t just about stopping production when something goes wrong. It is an automation strategy that works because it is incremental and centered on human-machine interactions. It is essential to the strength of manufacturing in high-wage economies and should command more attention than it has so far among Lean implementers.

The most striking characteristic of automation in manufacturing is that, while making progress, it has consistently fallen short of expectations. In Player Piano, Kurt Vonnegut articulated the 1950s vision of automated factories: integrated machines produce everything while their former operators are unemployed and the managers spend their time playing silly team-building games at offsite meetings. 60 years on, the most consistently implemented part of Vonnegut’s vision is the silly team-building games…

Nippon Steel’s Yawata Steel Works in Kitakyushu, Japan, produce as much today with 3,000 employees as they did with 40,000 in 1964, and this transition was accomplished without generating massive unemployment. There are other such limited areas of automation success, like the welding and painting of car bodies. When manufacturing jobs are lost today, it is almost never to automation and almost always to cheaper human competition elsewhere. In the words of an experienced operator in a plant making household goods in the US, “When I joined 25 years ago, I expected these jobs to be automated soon, but we’re still doing them the same way.”

What is holding up automation today is not technology  but the lack of consideration for people. There are entire books on automation without a paragraph on what their roles should be. Of course, a fully automatic, “lights-out” factory has nobody working inside, so why bother? There are at least two reasons. First, even an automatic plant needs people, to program its processes, tell it what work to do, maintain it, monitor its operations and respond to emergencies. Second, successful automation is incremental and cannot be developed without the help of the people working in the plants throughout the migration.

Enter autonomation, or jidoka, which is sometimes also called “automation with a human touch” but really should be called human-centered automation. Instead of systems of machines and controls, it is about human-machine interactions. In the classical House of Lean model, the two pillars holding up the roof at Just-In-Time and Autonomation, or Jidoka. Figure 1 is lifted from the introduction to Working with Machines, and shows what happens when the jidoka pillar is ignored.

Figure 1. Just-in-Time and Jidoka

More and more, the Lean literature in English uses the japanese word jidoka rather than autonomation, but with its scope reduced to the idea of stopping production whenever anything goes wrong, and the concept is tucked away under the umbrella of Quality Management.

Toyota’s jidoka is a tricky term, because it is an untranslatable pun. Originally,  the Japanese word for automation is jidoka (自動化) , literally meaning “transformation into something that moves by itself.” What Toyota did is add the  human radical 人 to the character 動  for “move,” turning it into the character 働 for “work,” which is still pronounced “do” but changes the meaning to “transformation into something that works by itself.” It”s automation with the human radical added, but it is still automation, with all the technical issues the term implies.

The discussion of automation in the first draft of Working with Machines started with the following historical background, which was edited out like the chapter on locomotives and typewriters, on the ground that it contained no actionable recommendations. In this blog, I can let you be the judge of its value.

From tea-serving wind-up dolls to autonomation

The word automation was first used by Ford manufacturing Vice President Delmar Harder in 1947 for devices transferring materials between operations. He set as targets a payback period of at most one year in labor savings, which meant in practice that each device should not cost more than 15% above an operator’s average yearly wages and eliminate at least one operator. While this kind of economic analysis is still used, from the perspective of Toyota’s system, Ford’s focus on materials handling was putting the integration cart before the unit operation horse. Toyota’s approach focuses on individual operations first, and only then addresses movements of parts between them. In 1952, John Diebold broadened the meaning of automation to what has become the common usage, and painted a picture of the near future that was consistent with Kurt Vonnegut’s.

At that time, automatic feedback control was perceived to be the key enabling technology for automation, to be applied to ever larger and more complex systems. It was not a new concept, having been applied since 1788 in the centrifugal governor regulating pressure in a steam engine (See Figure 2)

Figure 2. James Watt’s 1788 centrifugal governor

Applying electronics to feedback control in World War II had made it possible, for example, to move a tank’s gun turret to a target angle just by turning a knob. Postwar progress in the theory and application of feedback control both caused many contemporary thinkers, like Norbert Wiener,  to see in the concept a philosophical depth that is truly not there, and to underestimate what else would need to be done in order to achieve automation. Of course, if you cannot tell a machine to take a simple step and expect it to be executed accurately and precisely, then not much else matters. Once you can, however, you are still faced with the problem of sequencing these steps to get a manufacturing job done.

While automatic feedback control was historically central to the development of automatic systems, it is not at center stage in manufacturing automation today. With sufficiently stable processes, open-loop systems work fine, or feedback control is buried deep inside such off-the-shelf components as mass flow controllers, thermostats, or humidity controllers. Manufacturing engineers are occasionally aware of it in the form of variable-speed drives or adaptive control for machine tools, but other issues dominate.

Fixed-sequence and even logic programming also have a history that is as long as that of feedback control and are by no means easier to achieve. Figure 2 shows two examples of 18th century automata moved by gears, levers and cams through sequences that are elaborate but fixed.

Figure 2. 18th century automata from France and Japan

These concepts found their way into practical applications in manufacturing as soon as 1784, with Oliver Evans’s continuous flour mill that integrated five water-powered machines through bucket elevators, conveyors and chutes (See Figure 3). The same kind of thinking later led to James Bonsack’s cigarette making machine in 1881, and to the kind of automatic systems that have dominated high-volume processing and bottling or cartonning plants for 100 years, and to the transfer lines that have been used in automotive machining since World War II.

Figure 3. Oliver Evans’ continuous flour mill (1784)

Fixed-sequence automation works, but only in dedicated lines for products with takt times under 1 second, where the investment is justifiable and flexibility unnecessary. Rube Goldberg machines parody this type of automation.

Figure 3. Winner of the 2008 Penn State Rube Goldberg machine contest

Automation with flexibility is of course a different goal, and one that has been pursued almost as long, through programmable machines. The earliest example used in production is the Jacquard loom from 1801, shown in Figure 4. It is also considered a precursor to the computer, but it was not possible to make a wide variety of machines programmable until the actual computer was not only invented but made sufficiently small, cheap and easy to use, which didn’t occur until decades after Vonnegut and Diebold were writing.

Figure 4. Jacquard loom from museum in Manchester, UK

By the mid 1980’s, the needed technology existed, but the vision of automation remained unfulfilled. In fact, more technology was available than the human beings on the shop floor, in engineering, and in management knew what to do with. As discussed in the post on Opinels and Swiss knives, the computer as a game changer. In manufacturing, this was not widely recognized when it became true, and it still is not today.

Writing in 1952, John Diebold saw nothing wrong with the way manufacturing was done in the best US plants, nor did he have any reason to, as the entire world was looking at the US as a model for management in general and manufacturing in particular. In the 1980’s, however, when GM invested $40B in factory automation, it was automating processes that were no longer competitive and, by automating them, making them more difficult to improve.

Whether the automation pioneers’ vision will ever come true is in question. So far, every time one obstacle has been overcome, another one has taken its place. Once feedback control issues were resolved came the challenge of machine programming. Next is the need to have a manufacturing concept that is worth automating, as opposed to an obsolete approach to flow and unit processes. And finally, the human interface issues discussed must be addressed.

21st century manufacturers do not make automation their overall strategy. Instead, automation is a tool. In a particular cell, for example, one operator is used only 20% of the time, and a targeted automation retrofit to one of the machines in the cell may be the key to eliminating this 20% and pulling the operator out of the cell.

Share this:

  • Click to print (Opens in new window) Print
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on X (Opens in new window) X
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

By Michel Baudin • History, Technology • 4 • Tags: Autonomation, Lean manufacturing, Manufacturing engineering, Strategy, Toyota

«< 156 157 158 159 160 >»

Follow Blog via Email

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 579 other subscribers

Recent Posts

  • Using Regression to Improve Quality | Part III — Validating Models
  • Rebuilding Manufacturing in France | Radu Demetrescoux
  • Using Regression to Improve Quality | Part II – Fitting Models
  • Using Regression to Improve Quality | Part I – What for?
  • Rankings and Bump Charts

Categories

  • Announcements
  • Answers to reader questions
  • Asenta selection
  • Automation
  • Blog clippings
  • Blog reviews
  • Book reviews
  • Case studies
  • Data science
  • Deming
  • Events
  • History
  • Information Technology
  • Laws of nature
  • Management
  • Metrics
  • News
  • Organization structure
  • Personal communications
  • Policies
  • Polls
  • Press clippings
  • Quality
  • Technology
  • Tools
  • Training
  • Uncategorized
  • Van of Nerds
  • Web scrapings

Social links

  • Twitter
  • Facebook
  • Google+
  • LinkedIn

My tags

5S Automation Autonomation Cellular manufacturing Continuous improvement data science Deming ERP Ford Government Health care industrial engineering Industry 4.0 Information technology IT jidoka Kaizen Kanban Lean Lean assembly Lean Health Care Lean implementation Lean Logistics Lean management Lean manufacturing Logistics Management Manufacturing Manufacturing engineering Metrics Mistake-Proofing Poka-Yoke Quality Six Sigma SMED SPC Standard Work Strategy Supply Chain Management Takt time Toyota Toyota Production System TPS Training VSM

↑

© Michel Baudin's Blog 2025
Powered by WordPress • Themify WordPress Themes
%d