Using Pareto charts in project quality control

2001-12-29 11:26:52【作者】 畅享网 【进入论坛】
本文关键字
广告

Using Pareto charts in project quality control

When you're analyzing problems on a project, or measuring the impact of procedural changes, you need a tool that will pinpoint the important areas quickly. Pareto charts are easy to generate once you have chosen the data to be analyzed. Even those who are unfamiliar with data analysis can easily understand them - so it can be useful to include them in reports and presentations.

What is a Pareto chart?


A well-designed Pareto chart should provide you with an instant analysis of a situation

A Pareto chart is a bar chart that's organized according to specific guidelines. The bars are arranged in descending order from left to right. You use it to quickly identify the sources of problems and to see how individual pieces of data fit into a whole process. When you implement a solution to a problem, you can use a series of Pareto charts as a comparative tool to assess the effect of the solution. A well-designed Pareto chart should provide you with an instant analysis of a situation.

The "80 percent/20 percent" rule

The Pareto chart is based around the "80 percent/20 percent" rule. This is a phenomenon that was first noted by an Italian economist named Vilfredo Pareto (1848 - 1923), who observed that 80 percent of a country's wealth is usually held by 20 percent of the population. This principle, known as the Pareto effect, was applied to other situations and a similar pattern was observed. The proportions may vary, but the principle of a small number of events or conditions (the "vital few") influencing a greater number of outcomes (the "useful many") holds true in many areas, including quality management. It's a useful principle for determining the cause of problems, and a good way of checking the relevance of the data that you include in your Pareto chart. If the chart doesn't produce a clear result, you might need to regenerate it using different data.

Choosing the right data

Before you draw the chart, you need to decide on the data to be analyzed. Let's say you're analyzing data in a production process where six machines must produce a weekly quota of 3,000 units. The acceptable failure rate is 30 units per week, but when you study your first report you discover an average failure rate of 120 units per week.

You begin by grouping the failures according to the following major faults:

  • faulty soldering
  • missing jumpers
  • bent pins
  • incorrect switch settings

And you construct your first Pareto chart based on these results.

Analysis by fault type chart

A quick look at the Analysis by fault type chart tells you that no one fault type is responsible for the large number of failures in the process. If you take steps to eliminate all of the soldering faults, for example, the process still produces eighty faulty units per week, more than twice the acceptable failure rate.

You decide to redesign the chart using different data. This time, you analyze the number of faulty units produced by a particular machine to see if that yields a more meaningful result.

Analysis by machine number chart

You can see from the Analysis by machine number chart that the vast majority of faulty units are produced by machine number 4. You can analyze this data further to determine whether the high number of faults is due to a problem with the machine, or perhaps an inexperienced crew. You can use the charts to illustrate your findings in reports or presentations on the matter.

Drawing the chart

As you can see, the Pareto chart is laid out with the vital few, or 20 percent, on the far left of the chart, and the numbers decrease as you read across the chart from left to right, with the lowest number to the far right of the chart. Sometimes you might find it useful to include a cumulative curve to reinforce a pattern. Cumulative curves are usually found on comparative Pareto charts. In the example shown above, when the problem is diagnosed and fixed, you can use a series of before-and-after charts to display the improvements in a graph.

如果您希望与本文章的作者或其所在机构,进一步交流,请联系:畅享网 姜小姐
jill.jiang@amt.com.cn | 021-51096826-112 | 在线联系
商蓉蓉专栏[原创]营销就是“先入为主”吗..

在激烈的竞争中要努力寻找蓝海,在进入新市场时要抢占先机,以占据有利的地位。否则错失良机,蓝海很快会变成红海。

人月神话专栏[原创]精益看板管理和敏捷软件..

我们要意识到在软件开发中的浪费没有所谓的原材料,软件开发最大的浪费就是人力资源的等待已经我们开发完成工件的返工。

郭远刚谈项目管理[原创]信息系统项目成本估算的..

1. 需求信息的复杂性。与其他有些传统项目不同,信息系统要满足的诗人的主观需要。由于人的复杂性,给信息系统带来了无数的难以确定的因素。而且,随着项目的……

中国式项目管理[原创]软件产品的生命周期

管理软件,无论规划多好,一般生存10年就不错了,随着客户个性化需求不断累积,原来的架构难以适应鲜活的业务需求。

段柯专栏[原创]诊断中小企业软件项目管..

对于企业管理,大公司有大公司的方式,小公司有小公司的方式,如果把别人的经验生搬硬套到自己身上,可能会适得其反。