Jun 4 2014
Business Intelligence and Jidoka | Toyota’s Simon Dorrat | PEX
See on Scoop.it – lean manufacturing
Simon Dorrat is Manager of Toyota’s Business Intelligence function where he is responsible for defining and delivering all services relating to Business Intelligence and Data Warehousing including BI, ETL, Data Quality, Master Data and OLAP. […] Simon shares his thoughts on how Business Intelligence fits with the Toyota Way, suggests three ways for IT to provide better value to the business and even explains why doing a kitchen renovation helped some illuminate important aspects of software development.
For the IT-phobic, a Data Warehouse is a database that makes historical data from multiple sources accessible for analytics. It is commonly used to provide management with Business Intelligence (BI). The process of periodically feeding a data warehouse is called Extract, Transfer and Load (ETL).
Of course, analysis is only worth doing on data that is complete and accurate, hence the need for tools to ensure Data Quality. The different sources usually have different nomenclatures for products, processes, or facilities, and you need your Master Data to integrate them in a single, consistent model. Finally, “OLAP” stands for Online Analytical Processing.
The first sentence in the article describes Toyota as “creating the precursor to Lean Manufacturing” and nearly made me stop reading further. It would have been a mistake.
See on www.processexcellencenetwork.com
Jun 6 2014
Next frontiers for lean | McKinsey
See on Scoop.it – lean manufacturing
“…Quietly, though, in Nagoya, Japan, Taiichi Ohno and his engineering colleagues at Toyota were perfecting what they came to call the Toyota production system, which we now know as lean production. Initially, lean was best known in the West by its tools: for example, kaizen workshops, where frontline workers solve knotty problems; kanban, the scheduling system for just-in-time production; and the andon cord, which, when pulled by any worker, causes a production line to stop…”
This article implies that the “Kaizen workshop” is a tool of the Toyota Production System, when in fact it is an American invention from the 1990s and what it does is not what is meant by Kaizen in Japan
Then the article describes Kanban as “the scheduling system for just-in-time production.” It is really only a a tool of scheduling among many, including heijunka, just-in-sequence, consignment… The last example, Andon cords, had been observed at Ford in 1931.
Even if this choice of examples is unfortunate, Toyota people invented many tools while adopting and refining existing ones, and it is true that each tool, taken out of context, is of limited value. Toyota’s merit is to have deployed them in a uniquely effective way as part of a system of production.
This is, however, not what the article says. It jumps instead to management disciplines, like “putting customers first,” an idea that bazaar merchants worldwide have had for millenia.
“Enabling workers to contribute to their fullest potential” and “constantly searching for better ways of working” is in fact something that Toyota has done better than its competitors. And these are sound management objectives, but you could pursue them and still not be competitive.
The article implies that the technical content of the Toyota production system is a detail. All that matters is focusing on customers and treating people right. Is it? I don’t think so.
This attitude is the root cause of the failure of so many “Lean implementations.” Until the technical content of the Toyota Production System is understood and properly valued, the Lean movement cannot claim “Mission Accomplished” in manufacturing.
See on www.mckinsey.com
Share this:
Like this:
By Michel Baudin • Press clippings • 2 • Tags: Lean, Lean implementation, Toyota, TPS