| Trend charts are also known as Run charts, and are used to show trends in data over time. All processes vary, so single point measurements can be misleading. Displaying data over time increases understanding of the real performance of a process, particularly with regard to an established target or goal. Following is an example of a trend chart of order fill rate performance: | ||||||||||||||||||
|
| ||||||||||||||||||
| Major Elements: | ||||||||||||||||||
| A good trend chart has the following characteristics: | ||||||||||||||||||
| ||||||||||||||||||
| Two common errors in chart construction are shown below: | ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
| ||||||||||||||||||
Sunday, April 29, 2007
Trend Chart - Run Chart
Failure Mode and Effect Analysis - FMEA
| Failure Mode and Effects Analysis (FMEA) is a model used to prioritize potential defects based on their severity, expected frequency, and likelihood of detection. An FMEA can be performed on a design or a process, and is used to prompt actions to improve design or process robustness. The FMEA highlights weaknesses in the current design or process in terms of the customer, and is an excellent vehicle to prioritize and organize continuous improvement efforts on areas which offer the greatest return. |
| The process is very straightforward, and begins by identifying all of the probable failure modes. This analysis is based on experience, review, and brainstorming, and should use actual data if possible. New designs or processes may not have actual historical data to draw from, but "proxy" data may be available from similar designs or processes. |
| The next step is to assign a value on a 1-10 scale for the severity, probability of occurrence, and probability of detection for each of the potential failure modes. After assigning a value, the three numbers for each failure mode are multiplied together to yield a Risk Priority Number (RPN). |
| The RPN becomes a priority value to rank the failure modes, with the highest number demanding the most urgent improvement activity. Error-proofing, or poka-yoke actions are often an effective response to high RPN's. |
| Following is an example of a simplified FMEA for a seat belt installation process at an automobile assembly plant. |
| As you can see, three potential failure modes have been identified. Failure mode number two has an RPN of 144, and is therefore the highest priority for process improvement. |
| FMEA's are often completed as part of a new product launch process. RPN minimum targets may be established to ensure a given level of process capability before shipping product to customers. In that event, it is wise to establish guidelines for assessing the values for Severity, Occurrence, and Detection to make the RPN as objective as possible. |
Flow Chart
| The Process Flow chart provides a visual representation of the steps in a process. Flow charts are also referred to as Process Mapping or Flow Diagrams. Constructing a flow chart is often one of the first activities of a process improvement effort, because of the following benefits: | ||||||||
| ||||||||
| There are many symbols used to construct a flow chart; the more common symbols are shown below: | ||||||||
| | ||||||||
| If you have Microsoft Word or Excel, you can access a gallery or symbols in the Autoshapes function, together with a description of their use. The next step is to identify the process steps and link them together with direction arrows. | ||||||||
| Following is an example of a very simple flow chart for the process of getting out of bed in the morning: | ||||||||
| You can make a flowchart more useful by adding information beside the boxes. This flowchart gives a better description of the process when you know that the snooze bar gets hit three times, postponing the inevitable by five minutes each time. |
Pareto Chart
The theory behind the Pareto Chart originated in 1897 when an Italian economist named Vilfredo Pareto created a formula representing the uneven distribution of wealth - what later came to be known as the 80-20 rule. You have probably heard a version of it like: "20% of the people cause 80% of the problems", or a derivative. Dr. J. M. Juran started applying this principal to defect analysis - separating the "vital few" from the "trivial many", and called it the "Pareto Chart". In fact, many (most) defect distributions follow a similar pattern, with a relatively small number of issues accounting for an overwhelming share of the defects. The Pareto Chart shows the relative frequency of defects in rank-order, and thus provides a prioritization tool so that process improvement activities can be organized to "get the most bang for the buck", or "pick the low-hanging fruit". Following is an example of paint defects from an automotive assembly plant: |
| After reviewing the chart above, there is no question which defect to work on first. However, this pareto chart is constructed from one dimension only - defect frequency. If you learned that it costs $10 to fix a Dirt defect, while Sag defects cost $100 to correct, Sags would probably be the highest priority. Likewise, if one category represents a constraint on the whole process, its priority would be elevated. You may wish to consult the Project Priority Calculator for a template to prioritize along multiple dimensions. |
Six Sigma Answer to Material Shortages
One of Six Sigma¡¯s strengths is its facility for revealing causes and solutions that run contrary to our initial assumptions. When a persistent condition resists all attempts at improvement, or when an obvious fix to a newly discovered problem turns out to be lacking, a methodical approach like Six Sigma¡¯s can uncover even the most unlikely of causes and deliver results.
In the following case study the continuous improvement team was in for just such a surprise. Conventional wisdom was wrong, and the path the team started down hid unexpected complexities.
Definition
The XYZ Pump Garage program overall performance was poor. Future customer orders would not have been forthcoming without substantial improvements in quality and delivery.
- On-time delivery was 80% vs. >99% goal.
- Direct labor overtime was running 15% vs. a goal of zero.
- Field reported defects were found in 50% of system shipments vs. 0.5% goal.
- Project margin was approximately 22% vs. a 33% goal.
A process improvement team was formed with members from Customer Service, Manufacturing, Production Control, Engineering, Operations, and Purchasing.
Measurement
' Initial ' majority team consensus was that the program¡¯s poor on-time delivery was the result of material shortages due to understaffing in Purchasing. More buyers seemed to be the probable solution. The team suspected that the field defects were principally a result of poorly trained assembly staff.
The team began daily monitoring of data for number of daily kit shortages, overdue suppliers, and daily purchasing workload based on Material Requirements Planning (MRP) demands. Field personnel were interviewed for detailed descriptions of field defect rework.
Briefly summarized, the data showed:
- Typical labor overtime occurred near the end of the manufacturing process.
- 100% of all kits were issued with shortages.
- The key suppliers were >3 days late 50% of the time.
- The MRP system was posting material demands inside the material lead times!
- The requested delivery dates for material in the MRP system did not match well with project ship dates!
- A majority of customer-reported defects appeared to be the result of incomplete or incorrect manufacturing documentation.
- Overtime was being worked to make up lost time due to late material deliveries.
- Understaffing in Purchasing was not the problem! An army of buyers would not result in on-time material when the MRP ¡®buy¡¯ signal came too late or not at all. The team¡¯s true analysis problem was to understand why the MRP System was giving wrong signals. The team decided to focus on one specific sales order line item that exemplified the problem set for a typical system.
What they found:
- The sales order was coded incorrectly in a fashion that would generate several MRP problems.
- Item master attributes were not properly populated for many of the material items that had MRP problems.
- Customer engineering change orders (ECO) had been accepted without renegotiating product delivery dates with the customer to allow time for ECO implementation, including new material delivery.
- A check of other customer order line items showed similar problems.
- Customer ECO information was not being properly transmitted and propagated throughout the organization, resulting in out-of-date manufacturing instructions and field defects.
- Problems would not have occurred if program participants had properly followed the procedures and work instructions documented in the Quality Management System.
Improvement
The improvements we implemented can be summed up in one word: training. The company had grown significantly during the past year and while all employees had received training, it had sometimes been rushed or had not been completely absorbed by the new personnel. Mandatory training was scheduled immediately for all Customer Service, Engineering, and Operations personnel on the documented procedures for sales order entry, customer engineering change orders, creating item masters, and creating engineering masters. Retraining took 7 working days with approximately 30 personnel participating.
ERP data for all active purchase orders was audited for the most common errors the team had recently discovered. This process required 5 working days.
New delivery dates were negotiated with the customer¡¯s buyer based on the new solid data foundation. This was difficult, but fortunately the customer¡¯s buyer is a mature personality with a long-term partnership attitude.
Results:
- Within 4 weeks material shortages had improved considerably.
- On-time delivery reached 100%.
- Overtime labor became negligible.
- After 8 weeks there had been no field defects found in the 6 systems shipped in the prior 5 weeks.
- Margin has improved to 28%, but this needs further investigation.
- Teamwork between organizations improved as a result of greater appreciation for the needs and complexities of their respective jobs.
Control
On-time delivery, customer field defects, and margin remain the bottom-line metrics for process control on the XYZ program. However, most importantly, as a result of the XYZ team findings, a new continuous improvement team was formed: the Enterprise Resource Planning Data Integrity Team (EDIT). EDIT is tasked with developing a set of strategies and process control tools to insure there are no repeats of the XYZ difficulties on other programs.
Implications
This single Six Sigma project thus had far-reaching implications for the XYZ Pump Garage program. First, in fulfilling the immediate purpose of improving our performance, we achieved customer retention for the near future. On a broader level, we also seized an opportunity to enhance our overall long-term approach to improvement. The value of reaching beyond obvious solutions having been so dramatically reinforced, we created a new continuous improvement team charged with making the pursuit of quality a more proactive endeavor.
Choosing the Best Method for Listening to the Customer
Here is a table which summarizes these aspects of eight types of data collection. It is followed by a short discussion of each method.
Telephone Surveys
The results of a telephone survey of a randomly selected sample can usually be generalized to an entire population. For example, if a person wants to learn how satisfied customers are with a type of software, a survey of randomly selected individuals who have purchased that software will provide the information. A standard questionnaire must be developed, a sample selected, and interviewers must make the phone calls and record the data.
This type of data can produce valuable information but it is expensive. A 10-minute telephone interview with a random sample could cost in the neighborhood of $20,000 or more; the actual cost will, of course, depend on a number of factors such as how many people will be interviewed and how readily available an accurate sample of the target group is. Actual data collection usually takes a couple weeks although the preparation time needed to write the questionnaire can be several weeks.
The primary disadvantage of this method is that standardized, quantifiable telephone surveys are somewhat rigid. For example, all questions must be asked to all respondents in the same manner. Question wording should not vary. With some exceptions, all response categories must be the same and all inclusive. Also, no visual aids can be used.
Mail Surveys
A mail survey also can yield quantifiable data that can be generalized to an entire population and typically at a much lower cost than a telephone survey. However, the survey can take several months to complete and response rates are low. As a rule of thumb, the lower the response rate, the less reliable the data. For example, if a questionnaire is sent out to learn whether customers are satisfied with that same software, a small percentage ?maybe 5 to 20 percent ?will usually return the survey. Follow-up letters and questionnaires must be sent which adds to the cost and, more importantly, the time it takes to complete the study. After all of those efforts, it is not unusual to end up with a completion rate of 40 or 50 percent. Fifty percent is generally considered the lowest acceptable response rate.
Focus Groups: In-Person
The trade off in an in-person focus group ?a discussion of 5 to15 people, usually for two hours, guided by a moderator ?is that detailed information can be obtained but the information cannot be generalized to a population larger than the group itself. Using the same software example as above, a questionnaire may be able to determine how satisfied the customer is with the product and perhaps even areas of dissatisfaction. In a focus group, the moderator can probe about the reasons behind the dissatisfaction and perhaps discuss some possible solutions to the problems. The discussion can be quite in-depth. Visual aids can be provided. Much flexibility exists. To help mediate the fact that the results cannot be generalized to a larger population, focus groups and surveys are often conducted in partnership which provides both qualitative and quantitative data.
The cost of a focus group varies somewhat depending on location and availability of participants. However, a focus group typically costs about $5,000. Travel also can be expensive. Groups should be conducted in a variety of locations throughout the area in which the product or service is used. That often can require clients, moderators and viewers to travel to the different locations. Although a focus group takes only a couple of hours to complete, recruiting participants and preparation of guidelines usually takes at least a couple of weeks.
Another issue to consider is that many focus group facilities have a list of people they tap into to participate in focus groups. They can and often do use the same people over and over. Although research has yet to be done on the effects of using the same individuals frequently as focus group participants, one might conclude that these people could lack the spontaneity or freshness that is sought from focus group participants.
Focus Groups: Online
While in-person focus groups have been used by researchers since the 1940s, online focus groups are a recent development. Online groups consist of a dozen or so people who log onto an Internet chat site at the same time. A moderator leads the group. The moderator types in questions and participants respond and a dialogue among participants ensues.
The biggest disadvantage is that this type of research is suited only for younger age groups. Individuals age 40 and over generally are not as comfortable or accustomed to online chatting. Their input can be stifled by the technology. In contrast, younger participants are comfortable and this method can yield a lot of information.
The cost of this method can be as much as an in-person focus group. The primary savings is in the elimination of travel expenses. Viewers, clients and the moderator can all log on from different locations.
One-on-One Interviews
One-on-one interviews typically provide qualitative information that cannot be generalized to a larger population. As with focus groups, however, the interview allows for detailed information that cannot be obtained from a survey. One disadvantage is that the interaction or discussion that results from a group is eliminated. There is only a dialogue between the interviewer and interviewee.
One-on-one interviews can be particularly useful for people with limited availability such as doctors, CEOs and celebrities. Getting a group of these people together in a room at the same time for a two-hour focus group discussion can be difficult. One-on-one interviews can be planned more easily around a busy individual's schedule. Regardless, interviews with such people can still be difficult to obtain because of the demands on their time. And often high-profile individuals expect some type of financial incentive, like compensation for their time or a donation to a favorite charity in their name.
An advantage of one-on-one interviews is the cost usually is low. Of course, possible compensation for interviewees and the cost of the interviewer must be considered. If the same interviewer is used ?which is often a good approach ?travel expenses may become a factor as the interviewer travels to various locations to meet with the individuals.
Intercepts
Intercepts consist of approaching an individual in a public location. For example, if information is needed from mothers of infants, the interviewer may go to a shopping mall and approach people who fit that description and ask for their input. Often these individuals are provided an incentive, perhaps $10 or $20.
This information is qualitative in most respects. Intercepts also can yield limited quantitative information if enough interviews are conducted. However, the population to which the data is being generalized must be clearly noted. Using the above example, if data is gathered from 200 mothers with a standardized questionnaire who were randomly selected (such as every fourth woman with an infant), the data can be generalized only to women at the mall on that specific day and time frame who passed the location of the interviewer and who had brought an infant.
Another example of intercept data is to approach customers who are leaving a movie theater to ask them about their experience at the theater or their reaction to the movie, advertisements or whatever else was shown. Again, the researcher must be careful in generalizing the data. Interviewers also must be trained because they tend to want to approach only people who look friendly even though data is needed from all types of people.
User Testing
This methodology requires asking individuals to use a product, often while they are being observed. Or, instead of being observed, the individuals could be asked to keep a diary. User testing can be extremely valuable in understanding how to make a product easier to use. Web sites often undertake user testing to see if their site is easy to navigate. It can be determined at what point and why, for example, people who have initiated a purchase on a web site suddenly exit and the sale is lost. This data is primarily qualitative.
The time frame for user testing varies. If a group of people can be observed while navigating a web site, the data can be collected in one evening. However, research may need to done over the course of several weeks. The cost depends on specific situations but it generally is comparable to a focus group.
Customer Complaints
Obtaining input from customers who complain can provide insight into problem areas but it also is qualitative data that cannot be generalized. For example, if customers write letters or phone with complaints, there has been no systematic way of collecting the data. And it is often the case that people who complain are simply those who are habitual complainers, who have had a particularly bad experience, or who have the time to register a complaint. These individuals do not provide an accurate reading of the experiences of all customers. Customer complaints can provide a sense of where problems exist, but the data cannot be generalized.
The cost of collecting customer complaints usually is low. The only effort required is for someone to monitor and tabulate the complaints as they come in. It usually is necessary to collect complaints for several months to provide insights into any but the most obvious problems.
Friday, April 27, 2007
Six Sigma Case Study: Defect Reduction in the Service Sector
by Chris Bott
This case study discusses the effective use of Six Sigma tools to improve our plastic issuance processes. It will take you through a project American Express completed, “Eliminate Non-received Renewal Credit Cards.?This analysis demonstrates how we applied Six Sigma techniques to reduce the defect rate with ongoing dollar savings.
Define and Measure the Problem
(Data has been masked to protect confidentiality.)
- On average (in 1999), American Express received 1,000 returned renewal cards each month.
- 65% (650) were due to the fact that the card members changed their addresses and did not tell us.
- The U.S. Post Office calls these forwardable addresses. Please note: Amex does not currently notify a card member when we receive a returned plastic card.
Analyze the Data
We applied various Six Sigma tools to identify Vital Xs, or the root causes of the defect. The use of Chi Square indicated the following:
- By type of card/plastic: We isolated significant differences in the causes of returned plastics among product types. Optima, our revolving card product, had the highest incident of defects but was not significantly different in the percentage of defects from the other card types.
- Issuance reason: Renewals had far and away the highest defect rate in the three areas in which we issue plastic—replacement, renewal, and new accounts.
- Validated reason for returned: Because we suffered scope creep early in the project, it was important to confirm what our initial data was telling us. After testing the five reasons for returns, returns with “forwardable?addresses were overwhelmingly the largest percentage and quantity of returns.
Improve the Process
An experimental pilot was run on all renewal files issued. This “bumping?against the “National Change of Address?service was implemented on all renewal cards in mid August. Due to the strict file matching criteria, this solution will impact 33% of the remaining population (or 333 cards monthly).
As a result of a successful pilot, we were able to reduce the defect rate by 44.5%, from 13,500 to 6,036 defects per million, reflecting annual savings of $1,228. Figure 1 outlines the combined test results.
Fig. 1 Combined Test Results
| Non-Received Renewal Credit Cards | Baseline | Test Results |
| Defect rate | 1.35% | .6% |
| DPMO | 13552 | 6036 |
| COPQ |
| $3,360 |
| Total annual savings |
| $1,228 |
| Sigma level | 3.71 | 4.01 |
Control the Process
To ensure that we perform within the acceptable limits on an ongoing basis, it is important to monitor the new process. To achieve “control?status, we will be using the p chart, a tool that tracks proportions of returns over time.
In addition, our vendor has constructed reporting, which gives us the ability to monitor the defect rate on a monthly basis. The report will tell us if any credit cards that were “bumped?against the "National Change of Address" database were returned back to our warehouse.
Impact on Customer Satisfaction
Using the "National Change of Address" will enable over 1,200 card members to get their credit cards. Prior to this implementation, these card members would have never received their cards automatically. Revenue and customer satisfaction will undoubtedly increase.
Thursday, April 26, 2007
(Illustration) Map the entire process to know the where the improvement oppurtunities lie
Doc : Welcome to Step C of Define. This final step will allow us to develop the process that we are trying to improve. The overall layout is signified by the acronym COPIS. It start with the Customer and run through outputs, processes, inputs, and finally, the supplier.
Doc : The high-level process map displays the relationship between the customer and the process as well as the overall flow of the process.
Doc : Having said that, a high-level process map identifies key inputs
Doc : As well as identifies project requirements. Basically a process is defined as a collection of activities that takes one or more kinds of input and creates output that is valuable to the customer. The contents of a high-level process map will explain the process. Take a look.
Doc : The contents of a process map for a project includes:Customers and their key requirements
Doc : Outputs, which result from the process, and meet or exceed the customer’s needs and related requirements
Doc : Process Steps, which are selected in order to improve something
Doc : Inputs, which are parts and personnel provided by the suppliers
Doc : And suppliers, who as we just mentioned, provide the inputs. This information can be more easily illustrated in a diagram. Take a look and you be the judge.
Doc : Well, what do you think? See where each of the pieces fit? The project flows from right to left while the customer’s thinking flows from left to right. The most significant thing to remember is: The focus is on the Customer: COPIS Next, we will create a process map relevant to the Rockledge case.
Doc : Examining the generic process map just now has given you the experience for what you are about to do. Brainstorm about the Rockledge Case: think about who the supplier and the customer are, the problem and the goal statements, the systems needed to accomplish the goal, and the people and supplies need to operate the systems.
Doc : Congratulations! You have completed step C in Define, which means you have worked your way through the entire Define phase. In measure, we will add more details to the process map so that measurements can be taken to locate sources of improvement.
Doc : Well, we have accomplished all of the objectives in Step C of Define. We defined the purpose of a high-level process map and described its contents. Then, we developed the Rockledge high-level process map.
Master: In step B of Define, you learned about a team charter. Defining the business case,
Master: Developing a problem and goal statement,
Master: Assessing the project scope,
Master: And selecting the team and defining each members?roles are components of developing a team charter.
Master: In Step C of define you defined the purpose,
Master: Described the contents
Master: And, finally, developed a high-level process map.
Master: Did you do Ok in define? I hope so. Just in case you have any doubts I will give you a brief review before asking you some questions. The define phase has three steps:
Master: In Step A you identified project's C T Qs. If you recall, identifying the customer is the first step in understanding the projects C T Qs.
Master: Next, we analyzed data from the customer to figure out what the customer wanted.
Master: Finally, you learned about the process product drill-down tree, which is a way to integrate C T Qs and business strategy.
Master: If you want more of a review than that, you can access all of the steps from the Define Menu on your screen.
(Illustration) Develop the team Charter
Develop the team Charter
Doc : We will now move on to Step B of define. By taking the information we learned from step A, we will develop a team charter.
Doc : The goal for step B, the second step in Define is to create a team charter. A team charter is vital to the success of the overall project. What we will actually do is
Doc : Define the Business Case, which communicates the project direction and benefits to all the team members.
Doc : We also will develop a problem and preliminary goal statement, which is aligned with organizational priorities.
Doc : We will keep focused by assessing the project scope.
Doc : And, finally we will select a project team and define the roles of each member. We will use these components to develop a team charter for the Rockledge Case. But first we will define the elements of a team charter.
Doc : The first element of a team charter is to establish the business case: The business case drills down, and explains why the project should be done and why the project is important to do now.
Doc : It also explains the consequences of not doing the project, as well as prioritizes the activities Professor : And evaluates the project fit to business initiatives.
Doc : The next element of a team charter includes a problem statement that describes the opportunity for improvement.
Doc : And a goal statement that defines the improvement objective. The goal statement tends to be broad, and should include measurable target and completion dates.
Doc : Together, the problem statement and goal statement
Doc : Provide focus and purpose for the team.
Doc : A good team charter has a clear scope to a project that defines the process.
Doc : And places boundaries on that process. Starting points and ending points, as well as any constraints the team has to deal with, all are defined.
Doc : The final element of a team charter includes people, who should be carefully chosen,
Doc : Based on the needs of the project.
Doc : Their roles, responsibilities, and expectations, including time committed to the project, should be well defined.
Doc : Now that we have defined the elements of a team charter, let's see how this all applies to the Rockledge Case.
Doc : At Rockledge, the goal is to maximize availability and plant performance so that the customer has the ability to sell power anytime. This will maximize the GE bonus, which is directly tied to customer's financial performance. This will also prevent GE from incurring any Liquidated Damages, which are fees that GE would be required to pay if the customer was unable to generate power in accordance with the agreements contained in the GE Customer Contract. In short, GE and the customer have goals which are aligned for a mutual win-win situation. This information will be contained in the financial analysis used to dedicate resources to the project.
Doc : Rockledge Power Company's problem and goal statements are linked. The problem statement addresses the issue of reducing outage in year three of the contract while the goal statement requires ninety eight percent plant availability in year three of the contract. Each point addresses separate issues but strives for ninety eight percent plant availability in year three of the contract.
Doc : All we have left to complete the team charter is to determine who will work on this project. Let me introduce you to the team members and their roles: Naturally, the first team member is Jim Frank, the GE Facility Manager. He needs to make sure that contractual obligations are met.
Doc : The next member of the team is the field engineer
Doc : A third team member is the shift supervisor, who needs to balance scheduled outage with maximizing availability.
Doc : We need a mechanic on the team to provide the hands-on familiarity with the current process.
Doc : We also need a Black Belt or Master Black Belt identified to provide six sigma expertise to the project.
Doc : The final member of the team for the Rockledge case is the GE Operations Manager, who oversees multiple sites within the region.
Doc : We know now that we need to reduce scheduled outage time in year three of three contract. That means that we have ten months, when the next scheduled outage will occur, to complete the project. I am confidant that with our team and the business incentives, our project will be a success.
Doc : Congratulations, you have completed step B of Define.
Doc : Now we are ready to develop a high-level process map, Step C of Define.
Doc : We have completed the team charter with all the components. We know the value of completing the project as stated in the business case. We developed problem and goal statements. We know the time requirements of this project, and performed a financial analysis to justify the resources required. Finally, we selected a team and explained their roles.
Doc : We area about to begin the last step in Define Step C, where we will describe the purpose and contents of a high-level process map. Then, we will actually develop a high-level process map for the Rockledge case.So far we have derived and documented the customer's C T Qs, and developed a team charter. So, we are ready to develop the process that we are striving to improve. We begin by defining the purpose of the process map.
(Illustration) Let's identify our Six Sigma Project.
Master : I hope you're ready to learn about the Six Sigma D M A I C process because now its time to get down to business. You're going to start with Define and find out what this customer really wants.
Master : That's where the D M A I C process comes in. In the Define phase we can help John to wrap his arms around the problem, so to speak, by identifying some issues that are critical to meeting Alberti's expectations.
Master : Here are the three steps of the Define phase:.
Master : Step A is to identify your customer's CTQs. CTQ means Critical to Quality. In other words, what does your customer think is essential and how do you set up a project to meet their desires.
Master : Step B is to develop your team charter. This documents the scope of your project, the business case, and the role of team members.
Master : Step C, the final step of the define phase, is to build a map of the current process that will help you target a specific area for improvement.
Master : So your first job is to define what the customer wants and then start finding areas for improvement.
Master : I'll turn over the teaching of define to a good friend of mine, Angela Davis, PhD. She's an expert on this phase and you'll learn a lot from her.
Master : Good Luck and I'll see ya later.
Doc : Thank you Master. Hello there, I'm Doc. Friends say I'm a real people person, and I tell them I have to be it's my job. Getting to know people and what they want from a business is what I love to do. So, let's get to know the folks at Rockledge and show them how we use Six Sigma to meet and exceed their expectations!
Doc : We will begin by determining how to determine what the customer wants and use it as the foundation for developing the project goals.
Doc : The objectives for step A are to identify a projects C T Qs. In order to be able to figure out what is critical to quality for your customer,
Doc : we will need to identify the project's customers.
Doc : Once we know who the customer is, we will analyze customer data to determine customer's project CTQs.
Doc : Then we will take the CTQs and define and build a process product drill-down tree to figure out the process that needs attention. Now we are ready to begin.
Doc : The first question we need to answer is: Who is the Customer? The customer is the person who receives the output of the process. Once we learn who the customer is, we will be able to determine what they want.
Doc : There are two basic types of customers, the internal customer, and the external customer.
Doc : An external customer is the person or company outside of GE that requires the process output. On the other hand,
Doc : an internal customer is a person who depends on the output of your process to refine or create the final output for the external customer.
Doc : Therefore, we have
Doc : customer-driven C T Qs, which are defined by external customers, and
Doc : process-driven C T Qs, which are typically driven by internal customers.
Doc : Now that we know who the customer is, the next question we need to answer is, how do we finally determine the customers C T Qs? Since Critical to Quality C T Q characteristics are determined by the customer our job is to explicitly define the C T Qs.
Doc : So, the next step is to determine what the customer really wants. There are several sources of information or existing customer data that can be gathered to determine exactly what the customer wants : > Business goals, > Customer surveys, > Complaints, > Benchmarking data, > Executive-level discussions, and
Doc : Job-specific discussions all represent common factors that can be prioritized to find out what the customer wants. The customer data collected then will lead to the project C T Qs.
Doc : You're doing great so far. You have successfully determined two very important components for this case: The customer Mr. John, the General Manager and the C T Qs,
Doc : Which are to maintain ninety-eight percent availability as determined by the contract
Doc : and meet the contract delivery requirements. Now we are ready to create a process product drill-down tree to identify product and process C T Qs and complete Step A. Again, congratulations for a job well done.
Doc : So now that we know what the Rockledge customer wants, we are about to begin examining what we can do internally to meet those desires.
Doc : Six Sigma's focus on improving internal processes to meet customer requirements can be further explained using the formula Y equals f of x.
Doc : On the left of the formula is what we call the big Y. It is equal to the customer's CTQ; therefore, it is the desired outcome of Six Sigma. In the Rockledge case the big Y is Unit Availability.
Doc : The right side of the equation explains that this desired outcome is a function of internal processes or product characteristics that we can control. We call those processes X's, and it is our job to find an X for the Rockledge case that will contribute to achieving Unit Availability.
Doc : Depending upon how broad your Y is, you may have to subdivide it into more manageable components. We often refer to that as drilling down from the Big Y to little y’s. Drilling down to a little Y will be part of our task throughout the Define and Measure phases. We will get to the X's in Analyze.
Doc : Our next job is to define and build a process product drill-down tree.
Doc : A definition of a process product drill-down tree is a way to integrate C T Qs and business strategy. It helps to determine how customer C T Qs become project C T Qs. and ensure that what we are addressing has a genuine impact on the customer.
Doc : We are going to build a generic product process drill-down tree.
Doc : First, identify the high-level C T Q covered by your project Next, break this C T Q into the component lower-level C T Qs or processes. Then, identify the product groups or process steps, which form the next logical way to subdivide the project.
Doc : This process continues until it reaches the scope of interest The number of levels you drill down with depend on both the complexity of the higher level processes and the scope of our intentions to implement improvement through our six sigma project.
Doc : Now take a look at how the Rockledge case C T Qs are illustrated in a process product drill-down tree.We are only going to focus on one side, or branch, of the drill-down tree.
Doc : First, we have two C T Qs, which are maintaining high-level availability and meet contract delivery requirements. Doc : We will focus on the unit availability issue for now. We’ll deal with contract delivery requirements later. Now, we will drill down and see how a customer C T Q becomes a Project C T Q.
Doc : From the Big Y, we will drill down to a dependent variable better known as the little Y, which is, in this case, scheduled outages.
Doc : From the little Y,we can drill down to a second little Y, which is reduce outage duration. Here we can measure the duration of the outages. You will be able to accomplish that during the Measure Phase of the DMAIC process. We now have taken the customer's C T Q, maintain a high level of availability, and flowed it right into the project level C T Q; reduce outage duration. Whew! You did it!
Doc : By completing the process product drill-down tree, you have finished step A of Define. Now the project is taking shape. Spend a moment reviewing what you have learned.
Doc : For the Rockledge case we learned that
Doc : The customer is Mr. John
Doc : We also realized Mr. John primary C T Q, Frank and G E Contractual Services must to meet ninety eight percent plant availability in year three of the contract. Doc : The product process drill down tree allowed us to flow this C T Q?into the projects C T Q which is to reduce outage duration at Rockledge..
Doc : Congratulations!
Doc : You now are ready to develop a Team Charter, Step B of Define.
Doc : Believe it or not, you are finished with Step A of Define: You identified the projects C T Qs, which means:Doc : You identified the project customers, which ensured a valid source for the voice of the customer.
Doc : And analyzed the voice of the customer to determine the customer C T Qs.
Doc : You also discovered that using the process product drill-down tree allowed you to integrate the customer data with business strategies and flow the customer's C T Q into the project C T Q.