We’ve talked about accuracy, repeatability and reproducibility in your MSA’s but now we need to talk about data integrity.
Numbers shouldn’t lie, but when they do it is usually because somewhere along the line the integrity of the data didn’t hold up.
Before you begin your analysis there are two questions you should ask yourself:
- Does my data have known reference points?
- Does the data match control documents? If you’re looking at product returns, does the data match the information on your financial documents?
Accuracy and Precision
The next thing to think about is accuracy and precision. When you are evaluating the accuracy of your data, what you are looking for is how close the average is to the anticipated value. Your precision will tell you how much variation occurs in you data. Think about it in terms of playing pool. Your accuracy tells you how close you were to making the shot and your precision shows you how far apart the balls were from the pocket.
The third thing to look at is any bias your data might have. Formally the definition of bias is the deviation of what was measured from the actual value. What that means is how far off your measurement is from the actual number. The goal is to reduce bias as much as possible, I say reduce because you will never be able to eliminate it. You will need to decide what acceptable bias limits are. If you have a worker who is consistently late and you’re measuring organizational tardiness, you know your bias is going be about 10 minutes.
Next you can move on to stability. Stability is defined as your error rate. The less errors, the more stable the process. All stability does is tell you when accuracy or bias changes in your process. What you should be looking for it to do is serve as an alarm, letting you know that something has changed. This alerts you to areas in your process that are no longer stable.
Last but not least, you have linearity. What this tells you is if your bias is consistent. If something happens once, it’s an outlier. It’s not consistent which means you don’t want to hinge a change or a new process on something that may or may not happen again.
MSA is a big subject and we are far from done with it. Next week we will continue to talk about MSA Windows in Minitab and how to interpret them. In the meantime if you have any questions give us a call and let us help!
This week we will continue our discussion on process mapping, I promise it will not go on forever, but it does have a lot of intricacies. Many people think that process mapping is just putting some shapes on a diagram, but it means much more than that. There are 3 levels of process mapping that are commonly accepted among the 6Sigma crowd.
Level 1 –The Macro Process Map
This is typically how management views the processes of the organization; it’s a big picture, future strategy kind of view. It also creates the ability for management to see how to position the organization or resources in a way that complements the product/service being created. This is a high-level map which generally includes:
- Activities that relate to one major process step
- How the process fits into the big picture
- Little specific detail
- Visualizes only major process steps
- Can be used with only a general understanding of the purpose of the process and its steps.
Level 2-Process Map
This is the worker bee process map, where the people who have specific knowledge of the process come in. This is the map that is used to identify all the major steps a worker takes to complete a process. Within Level 2, there are 4 types of process maps:
- Linear Flow- A straight line from beginning to end.
- Swim Lane-shows you who is responsible for what task.
- SIPOC-a little more complicated. It takes five areas: your suppliers, your inputs, your process, your outputs and your customers.
- Value Stream-a specific map that helps to visualize and understand the metrics for the performance of major steps.
Level 3-Process Flow Diagram
Level 3 is not a must because this is a micro process map. It is where you zero in on a specific area and focus on the steps in the process that are causing whatever challenge you are having. When beginning this level you need to ask the following questions:
- Which steps contributed to the problem?
- Where would the problem most likely have occurred?
- Are there elements to the product/service that lend itself to the problem?
These questions help you find the focus that you decided in your problem statement. For this to work you will have to break each step in the process down, most easily using SIPOC. Remember a Level 3 map should include:
- All process flows
- Any set points
- Any standard or automated procedures
- Inputs and outputs (specify if the are controllable or non-controllable)
- Defects per unit
- Yield and rolled throughput yield
- Value and non value added activities
It’s a lot of information, but mapping a process is a fundamental step in your improvement project. It is absolutely critical that you get it right. For more help or more information, give us a call and we will be happy to get you started.