Site icon Tutorial

Improvement Techniques

Various improvement methods are used which are discussed.

Brainstorming

Brainstorming is a technique to systematically generate ideas usually to handle a challenging situation, from a group of people by nurturing free-thinking. There are several such opportunities in any organisation, e.g. Improving productivity, increasing sales, finding new business development areas, launching new products or defining new processes.

While there may be well defined techniques or processes to handle these situations, but brainstorming is a critical activity in all of these processes. Techniques such as Affinity, Nominal group technique, Cause and Effect Diagram, Failure mode effect analysis, 5 whys, Fault tree analysis, Decision matrix, and Risk analysis require brainstorming as an integral part of their execution. The list is endless!

Brainstorming required for generating inputs for the above techniques is complex as compared to the free flow ideation that one usually associates with the term brainstorming. An example of the kind of brainstorming required here can be observed in a 5-why analysis, where brainstorming occurs for every why in a hierarchical manner until a root cause is discovered.

Brainstorming session must be orchestrated by a facilitator. The number of participants in a session must be limited to a manageable number – typically between 5 and 15. There are few rules for a successful brainstorming, which should be enforced by the facilitator. These rules are listed below.

Process to conduct brainstorming is as

5 Whys

To use the 5 Whys tool, you select an identified cause of defects and ask “why” five times. You may ask a lot more than just five “why” questions, but asking “why” five times per cause is a good rule of thumb. If you start a root cause analysis and you’re only going down two or three levels, you’re probably still just getting at the symptoms of the problem and not the true root cause. The goal for moving through root cause analysis using the 5 Whys and other tools is always to get down to the actual, actionable, true root cause. If you eliminate the root cause of defects, the defects will disappear. They are asked in a sequence from top to bottom for root cause analysis, as

An example of a manufacturing process with a defect is considered for 5Whys, as

The root cause would then be that there is no measurement system in place.

Multi-vari studies

Multi-Vari Analysis is a tool that graphically displays patterns of variation. These studies are used to identify possible X’s and/or families of variation. These families of variation can frequently hide within a subgroup, between groups or over time.

It is a technique for viewing multiple sources of process variation. Different sources of variation are categorized into families of related causes and quantified to reveal the largest causes. Multi-vari analysis provides a breakdown for example, that machine B on shift 1 is causing the most variation. It won’t quantify the variation just show where it is. Multi-Vari is the perfect tool to determine where the variability is coming from in process (lot-to-lot, shift-to-shift, machine-to-machine, etc.), because it does not require to manipulate the independent variables (or process parameters) as with design of experiments. It enables analyzing the effects of multiple factors, multi-vari analysis is widely used in six sigma projects.

Also, the effect of categorical type inputs can be displayed on a response on a multi-vari chart. It is one of the tools used to reduce the trivial many inputs to the vital few. In other words it is used to identify possible Xs or families of variation, such as variation within a subgroup, between subgroups, or over time. Multi vari charts are useful for quickly identifying positional, temporal and cyclical variation in processes.

FMEA

The acronym FMEA stands for “Failure Modes and Effects Analysis”. It represents a technique aimed at averting future issues in project processes and eliminating risks that may hamper a solution.

It identifies and evaluates defects which could potentially result in reducing quality of a product. Defects within the methodology are defined as anything that reduces the speed or quality at which a product or service is delivered to customers. FMEA is used to discover and prioritize aspects of the process that demand improvement and also to statistically analyze the success of a preemptive solution. There various types of FMEA are

The steps to creating a FMEA are

Measurement system capability re-analysis

It is a method to re-identify the components of variation in the measurement. It is used to re-quantify the impact of measurement errors and to ensure the integrity of data used for analysis.

Just as a process has inherent variations, the process of measurement has variations too. Therefore, when making decisions that relies on data, it is important to ensure that the systems that collect that data are accurate and precise. Although it may not be possible to totally eliminate measurement errors, the objective of it is to ensure that measurement variance is relatively much smaller than the observed variance. It uses scientific tools to determine the amount of total variation is from the measurement system.

The areas of measurement error are analyzed and quantified

Post-improvement capability analysis

Post improvement re-measuring and re-analyzing the capability and performance of a process under review enables organizations to numerically represent and interpret its current state, and to report its sigma level. When done correctly, process capability analyses enable project team to precisely assess current performance in light of future goals, and ultimately, to determine the need and targets of process improvement. Process capabilities can be determined for normal and non-normal data, and for variable (continuous) and attribute (discrete) data alike. It is reported through the statistical measurements of Cp, Cpk, Pp, and Ppk which are

It also involves validating solutions through F-test, t-test and other similar tests.

Exit mobile version