Академический Документы
Профессиональный Документы
Культура Документы
1. TQM and Problem Solving 2. The 7 Management Tools 3. The 7 Quality Control Tools
Presented To:
After Planning for and Establishing TQM system you have to solve many problems to untie the rope knot connected to the TQM Balloon so that the TQM Balloon will move upward and downward easily according to different customers perceiving different levels of Quality
4. Other Tools.
4.1. 4.2. 4.3. 4.4.
Types of Problems
A. B. C. D. E.
There are five types of problems: Compliance Unstructured Efficiency process design product design The first three are performance problems where an existing system is not performing satisfactorily, and the last two are design problems that require a new or improved design.
A. Compliance
Compliance problems occur when a structured system having standardized inputs, processes, and outputs is performing unacceptably from the user's viewpoint. These problems are identified by comparing with standards or by feedback from the internal or external customer. The major challenge is to determine the root cause of the nonconformity and then take corrective action. Diagnosis can be difficult, because products and processes are quite complex. Standards cannot address all of the potential problems due to the interaction of individuallyacceptable characteristics.
B. Unstructured
Unstructured problems resemble compliance problems except that they are not specified by standards. The absence of standards may be due to system immaturity or to the need for flexibility in system performance. For example, customer service workers adapt their behavior to individual customers. Identification of unstructured problems is usually brought about by negative customer feedback. The major challenges are to determine customer needs and to diagnose the causes of poor performance.
B. Unstructured
of customer variability, it is difficult to determine why a product or service was unacceptable. Organizations need to treat each customer as an individual and maintain a database on acceptable and unacceptable behavior.
Because
C. Efficiency
Efficiency problems occur when the system is performing unacceptably from the viewpoint of its owners or operators. In other words, the end user is satisfied; however, the process is more costly than desired, or working conditions are not acceptable. Problem solving is directed towards reducing cost and providing safe working conditions. Identification of such problems occurs from benchmarking and operator suggestions.
D. Process Design
Process-design problems involve the development of new processes and revision of existing processes. Many business and production processes have not been well designed or have become obsolete with advances in technology. Identification of problems is prompted by poor performance, the knowledge that we can do better (benchmarking), or the introduction of new products. It requires that user needs and relevant constraints be identified.
E. Product Design
Product-design problems involve the development of new products and the improvement of existing products. A major focus is to prevent process and end user problems by relying on customer needs. Although design work can be initiated as a result of poor product performance, problem solving usually occurs as a natural part of a competitive environment. A major challenge is translating, in a timely manner, user needs and constraints into product attributes and specifications, usually using quality function deployment (QFD).
the term 'tools and techniques' is used generically to describe practical methods and skills applied to particular tasks to facilitate change and improvement.
A technique has a wider application than a tool. There is also a need for more intellectual thought, skill, knowledge, understanding and training to use them effectively. A technique may even be viewed as a collection of tools .The use of a technique may cause the need for a tool to be identified. Examples of techniques are: -Statistical Process Control -Failure Mode and Effects Analysis -Benchmarking -Design of Experiments -Quality Function Deployment -Self-assessment
7- reinforce teamwork through problem solving, 8- make a contribution to the achievement of business results, 9- provide a framework which ensures that the right things are done first time and every time,
tools and techniques in current use must be employed effectively before attempts are made to introduce others, the temptation to single out one tool or technique for special attention should be avoided, the limitations of how and when tools and techniques can best be used should be understood, and tools and techniques must be used as an integral part of the business operations.
There are a variety of means for classifying the tools and techniques used in a process of improvement. Tools and techniques can be broadly categorized as relating to (1) role, (2) tasks and activities associated with the improvement process, and (3) the stageslsteps involved with a process of improvement These uses include:
collection of data summarizing data presentation of data discovering problems selecting problems understanding a problem assisting with the setting of priorities finding and removing the root causes of a problem
identifying
relationships structuring ideas performance measurement capability assessment * planning implementing actions monitoring and maintaining control
Table : shows a typical classification of tools and techniques, aligned to their main perceived role,
In the majority of organizations tools and techniques are commonly used to solve problems, undertake projects, demonstrate commitment and facilitate improvement. They are used in the majority of the processes of a business Everyone, including managers, should be encouraged to use tools and techniques as a matter of routine in their business activities. Within an organization, all employees should be able to:
find
a use for tools and techniques in their processes, find opportunities to make improvements and cost savings, outside of quality improvement teams, and improve the effectiveness of the tools and techniques currently used
Most
organizations use tools and techniques as an aid to improvement. They are commonly used to assist with improvement projects and to solve problems, and are increasingly being used as a routine approach to day-to-day data collection, problem solving and data handling.
1- Relations Diagram
Relations
diagrams are used to identify, understand and clarify complex cause and effect relationships to find the causes and solutions to a problem and to determine the key factors in the situation under study. They are also employed to identify the key issues to some desired result.
Relations Diagram
Relations diagrams are used when the causes are non-hierarchical and when there are multiple interrelated problems. They allow the problem to be analysed from a wide perspective, because a specific framework is not employed. Relations diagrams can be considered to be a freer and broader version of a cause and effect diagram
central problem or issue to be discussed is described clearly and accepted by those concerned. Issues, causes and related problems that are believed to be affecting the central problem(s) are identified. These are written, in summary form, on cards, one issue, cause or problem per card.
The cards are then placed around the central problem/issue in a cause and effect relationship. This is done by placing the card believed to have the strongest relationship closest to the central problem/issue; other cards are ranked accordingly. The cause and effect cards are enclosed within rectangles or ovals, and arrows are used to highlight which causes and effects are related. The relationship is indicated by arrows pointing from cause to effect. The key cause and effects are emphasized by double lines, shading etc. Appropriate revisions are made to the diagram. The resulting diagram is analysed for principle causes.
Figure : is an example from Rank Xerox, which links the issues and ideas from the affinity diagram in relation to managing the CCC.
Confusion with a cause and effect diagram in terms of to which type of problem it should be applied. Stifling logical patterns of thought. Questioning the credibility of the data that has been collected. The volume of data being handled and portrayed on the diagram, which may prevent focus on key items.
the key relationships by summing the number of incoming and outgoing arrows. Clearly indicating the major cause and effect relationships. Seeking the views of people from outside the team to assess the accuracy of the diagram.
2-Affinity Diagram
Affinity
diagrams are used to categorize verbal data about previously unexplored issues, problems and themes that are hazy, uncertain, complex and difficult to understand, thereby helping to create order out of chaos.
Affinity Diagram
They
are used in conjunction with or as an alternative to brainstorming, and are useful when new thoughts and ideas are needed. The diagram uses the natural affinity between opinions and partial data from a variety of situations to help understand and structure the problem.
Affinity Diagram
It
tends to be a creative rather than a logical process. The diagram helps to organize data, ideas, issues and concerns for decision making and to reach solutions about previously unresolved problems.
Those cards with related ideas are placed together and separated from the remaining cards. This development of related issues and natural clusters is often done by the team members moving the cards around the board in an atmosphere of silence .The idea of this is to allow the more creative right-hand part of the brain to be used. Team discussion can help to develop the individual statements, ideas etc. on the cards within the cluster.
Figure : shows an example of an affinity diagram from Rank Xerox UK in relation to the customer contact cycle. The customer contact cycle (CCC) is an analysis tool that provides a way of understanding how Rank Xerox supports its customers
Uncertainty about when to use them and their benefits in comparison to other tools such as brainstorming and relationshipdiagrams. The tendency to put more than one idea on a card. Lack of group participation. Failure to work as a team. Data presented in an unmanageable form. Traditional thinking based on previous experiences.
3- Systematic Diagram
Systematic or tree diagrams are used to examine, in a systematic manner, the most appropriate and effective means of planning to accomplish a task ('how to') or solve a problem ('why'); events are represented in the form of a root and branch relationship. Such diagrams display in increasing detail the means necessary to achieve a specific goal or clarify the component parts that lead to the root cause of a problem.
Systematic Diagram
They are used when the causes that influence the problem are known, but a plan and method for resolving the problem have not been developed. Systematic diagrams are usually used to evaluate several different methods and plans for solving a problem and thereby assisting with complex implementations. They are also useful to identify dependencies in a given situation and to search for the most suitable improvement methods.
The problem to be solved or task to be accomplished is written on a card. The card is placed on the left-hand side of the board, table, wall or other means being used to display the data. The primary methods and tasks to accomplish the objective or primary causes of the problem are identified. A typical question used in this identification is 'To achieve the objective, what are the key means?'. Each of these methods, tasks etc. is written on a card and placed directly to the right of the problem statement. In this way the first level of a root and branch relationship is created.
Working back from the right-hand side of the completed diagram through the levels, the relationship between objectives and means, or problem and causes, is checked to ensure that the means and causes are each related to the objectives and problem, respectively: 'Will such and such an objective be accomplished if a particular method or task is implemented?'
Figure : is an example from Rank Xerox, which maps out the full range of paths and tasks to be accomplished to manage customer retention
A
poorly defined primary goal or issue. Failure to identify all of the means to achieve the goals. Leaving gaps in the diagram as a result of inadequately answered questions. Allowing the diagram to become inflexible.
Having clear, simple objectives or issues. Applying logical thinking. Using the combined experience of the team. Working to the level of detail decided by the team at the outset. Using the output for action planning or root cause elimination; action planning
4- Matrix Diagram
Matrix
diagrams are used to clarify the relationship and key connecting points between results and causes or between objectives and methods and to indicate their relative importance. They are also useful for drawing conclusions between consequences and their causes.
Matrix Diagram
They are used when there are two sets of factors and methods, which may have no relationship with each other. The factors are arranged in rows and columns on a chart with the intersections identifying the problem and its concentration; the intersecting points are the base for future action and problem solving. There are number of types of matrix diagrams (e.g. L-type, T-type, Y-type), each having a specific range of applications
Decide the format of the matrix - L-type, T-type, Ctype, X-type, etc. - and the characteristics, tasks, problems, causes, methods, measures etc. to be compared, mapped and displayed. Decide how to arrange the problems and their causes. For example, in an L-shaped matrix for relating customer needs and design features, the customer needs are listed in the rows and the design features relating to each need are listed in the columns. Define and specify the symbols that are to be used to summarize a relationship.
relationships between, say, the needs and features or problems and causes etc. are identified and discussed and symbols used to indicate the strength of the relationship where a column and a row intersect. Review the completed diagram for accuracy
Figure :shows the structure of an L-type matrix used on a Rank Xerox customer retention project
Arranging the problems and their causes into rows and columns. Attempting to force a particular pattern from a set of data. Agreeing the degree of correlation/impact of the factors at each intercept. Failing to use the data to draw conclusions about priorities
is used to quantify and arrange the data presented in a matrix diagram in a clear manner. It is a numerical analysis method and employs techniques such as multivariate analysis.
to achieve particular objectives do not always go according to plan, and unexpected developments may have serious consequences. The process decision program chart (PDPC) avoids surprises and identifies possible countermeasures
7- Arrow Diagram
This method applies systematic thinking to the planning and executionof a complex set of tasks. It is used to establish the mostsuitable plan for a series of activities in a project, and to monitor its progress in an efficient manner to ensure adherence to the schedule. Arrow diagrams are necessary to describe the interrelationships and dependencies of tasks within a complex job or project.
Arrow Diagram
They
are deployed at the implementation planning stage of a project, which is always the critical stage. The sequence of the steps involved and their relation to each other are indicted by arrows and in this way a network of activities is developed
Identify all activities needed to complete the plan. Decide the feasible sequence of the activities: - which activities must precede certain activities (consecutive activities) - which activities must follow an activity (consecutive activities) - which activities can be done at the same time (concurrent or parallel activities) Arrange the diagram from left to right according to the above logic with each activity represented by an arrow.
Figure : is an example of an arrow diagram : siting and construction of a quality notice board
Lack of understanding of the project activities and implementation objectives. Deciding the feasible sequence of the project activities that have been identified. Establishing the dependencies of activities Calculation of float (i.e. the amount of time by which an activity can extend beyond its duration without affecting the overall time for the project). Incorrect use of dummy activities (these are used to preserve the unique numbering system and the network logic).