内容简介:Common uses of the Ishikawa diagram areproduct design and quality defect prevention to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to
Ishikawa diagram | |
---|---|
One of the Seven Basic Tools of Quality | |
First described by | Kaoru Ishikawa |
Purpose | To break down (in successive layers of detail) root causes that potentially contribute to a particular effect |
Ishikawa diagrams (also called fishbone diagrams , herringbone diagrams , cause-and-effect diagrams , or Fishikawa ) arecausal diagrams created byKaoru Ishikawa that show thecauses of a specific event.
Common uses of the Ishikawa diagram areproduct design and quality defect prevention to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to identify and classify these sources of variation.
Contents
Overview [ edit ]
Sample Ishikawa diagram shows the causes contributing to problem.
The defect is shown as the fish's head, facing to the right, with the causes extending to the left as fishbones; the ribs branch off the backbone for major causes, with sub-branches for root-causes, to as many levels as required.
Ishikawa diagrams were popularized in the 1960s byKaoru Ishikawa,who pioneered quality management processes in theKawasaki shipyards, and in the process became one of the founding fathers of modern management.
The basic concept was first used in the 1920s, and is considered one of theseven basic tools ofquality control.It is known as a fishbone diagram because of its shape, similar to the side view of a fish skeleton.
Mazda Motors famously used an Ishikawa diagram in the development of theMiata (MX5) sports car.
Advantages [ edit ]
- Highly visual brainstorming tool which can spark further examples of root causes
- Quickly identify if the root cause is found multiple times in the same or different causal tree
- Allows one to see all causes simultaneously
- Good visualization for presenting issues to stakeholders
Disadvantages [ edit ]
- Complex defects might yield a lot of causes which might become visually cluttering
- Interrelationships between causes are not easily identifiable
Root causes [ edit ]
Root-cause analysis is intended to reveal key relationships among various variables, and the possible causes provide additional insight into process behavior.
The causes emerge by analysis, often through brainstorming sessions, and are grouped into categories on the main branches off the fishbone. To help structure the approach, the categories are often selected from one of the common models shown below, but may emerge as something unique to the application in a specific case.
Each potential cause is traced back to find the root cause, often using the5 Whys technique.
Typical categories include:
The 5 Ms (used in manufacturing) [ edit ]
See also:5M model
Originating with lean manufacturing and the Toyota Production System , the 5 Ms is one of the most common frameworks for root-cause analysis:
- Man / mind power (physical or knowledge work, includes:kaizens, suggestions)
- Machine (equipment, technology)
- Material (includes raw material, consumables, and information)
- Method (process)
- Measurement / medium (inspection, environment)
These have been expanded by some to include an additional three, and are referred to as the 8 Ms:
- Mission / mother nature (purpose, environment)
- Management / money power (leadership)
- Maintenance
The 8 Ps (used in product marketing) [ edit ]
See also:Marketing mix
This common model for identifying crucial attributes for planning in product marketing is often also used in root-cause analysis as categories for the Ishikawa diagram:
- Product (or service)
- Price
- Place
- Promotion
- People (personnel)
- Process
- Physical evidence
- Performance
The 8 Ps are primarily used in product marketing.
The 4 Ss (used in service industries) [ edit ]
An alternative used for service industries, uses four categories of possible cause:
- Surroundings
- Suppliers
- Systems
- Skill
Fishbone Diagram in Lean [ edit ]
A recurring theme in a lean orSix Sigma transformation is removing the clutter to reveal waste or opportunities for improvement. A fishbone diagram aims to break down and organise the Causes of an issue to reveal what elements have the greatest impact. Grouping the “causes” means you can think about the different elements of the problem as separate from the overall process. One or two of these “causes” will have a greater effect than the others and will guide you to the root of the problem. This structure also allows you to tackle smaller chunks which have a large impact on the problem. Looking at elements of the problem and not the whole process will likely make finding your solution less daunting and problem solving more manageable.
After you have determined your root cause, prioritise or screen the causes to determine which are having the largest effect. Once identified focus on these. An easy Cause screening method involves looking at each one and asking two questions:
How likely is this cause to be the major source of the issue or variation?
- V - Very Likely
- S - Somewhat Likely
- N - Not Likely
How easy would it be to fix or control?
- V - Very Easy
- S - Somewhat Easy
- N - Not Easy
Put the answers of the two questions together. Work on the Causes that have a result of VV, VS, and SV.
See also [ edit ]
以上所述就是小编给大家介绍的《Ishikawa diagram》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
Processing语言权威指南
Casey Reas、Ben Fry / 张静 / 电子工业出版社 / 2013-10-1 / 139.00
本书介绍了可视化艺术中的计算机编程概念,对开源编程语言Processing作了非常详尽的阐述。学生、艺术家、设计师、建筑师、研究者,以及任何想编程实现绘画、动画和互动的人都可以使用它。书中的大部分章节是短小的单元,介绍Processing的语法和基本概念(变量、函数、面向对象编程),涵盖与软件相关的图像处理、绘制,并且给出了大量简短的原型程序,配以相应的过程图像与注释。书中还有一些访谈文章,与动画......一起来看看 《Processing语言权威指南》 这本书的介绍吧!