Skip to main content

http://josephmcohen.com/post/71536977591/toyota-manufacturing-principles

Toyota Manufacturing Principles

Throughout its history, Toyota has made a habit of labeling its business concepts and guiding values. In learning more about the company, I’ve picked up a few useful concepts from their manufacturing vocabulary:
Jidoka: Automation with a Human Touch
The idea of jidoka is that humans should work with machines to produce the best possible outcome, leveraging the execution ability of a machine and the judgement of a human. I learned this term on a tour of Toyota’s Nagoya factory, where jidoka is a guiding principle. The concept originally comes from Sakichi Toyoda’s invention of the automatic loop in 1896, back when Toyota was in the textile business.
Jidoka will become increasingly relevant as computers continue to do more and more work that humans have historically done. The concept has been ported to English under the name “autonomation,” and the Atlantic recently ran a story on how human-computer hybrids are changing the telemarketing business.
Poka-yoke: Mistake-Proofing
Poka-yoke is about designing processes to minimize human error, such that there’s nowrong way to do something. Treehouse did a nice write up of the idea. It can broadly be applied to any kind of user assembly (furniture), tool (hold the break to start a car), or education (try it until it works). Thanks to Brad Sewell for sharing. 
Kaizen: Continuous Improvement
Kaizen translates to iterative improvement, the process of refining processes, testing assumptions, and implementing learnings. From Wikipedia:
Kaizen is a daily process, the purpose of which goes beyond simple productivity improvement. It is also a process that, when done correctly, humanizes the workplace, eliminates overly hard work, and teaches people how to perform experiments on their work using the scientific method and how to learn to spot waste in business processes.
The lean startup methodology, where new businesses are created by hypothesis-driven experimentation and iterative development, is heavily influenced by the concept ofKaizen.
TAGGED: toyota manufacturing
NOTES:
  1. ideasandform posted this



Comments

Popular posts from this blog

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     pub...

Validating CSV Files

What is CsvValidator ?   A Java framework which validates any CSV files something similar to XML validation using XSD. Why should I use this ?   You don't have to use this and in fact its easy to write something your own and also checkout its source code for reference. Why did I write this ?   Some of our projects integrate with third party application which exchanges information in CSV files so I thought of writing a generic validator which can be hooked in multiple projects or can be used by QA for integration testing. What is the license clause ?   GNU GPL v2 Are there any JUnit test cases for me checkout ?  Yes,  source How to integrate in my existing project ? Just add the Jar which can be downloaded from here  CsvValidator.jar  and you are good. Instantiate  CsvValidator c onstructor which takes these 3 arguements          // filename is the the file to be validated and here ...

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column ...