Need Help Creating an MSA

@sebvlarsen What do YOU think you should do? Why or why not? Be more specific about what problem you’re having and you’re more likely to get a response.  People want to see that you’re putting in a good-faith effort to figure out the solution on your own.

MSA stands for Measurement System Analysis therefore it is related to the “measurement system” (combination of gauges, instruments, methods, people, ecc..) used in the process to collect data. In this respect, from what is shown in the conversation, it seems that the process data are those related to collection of delivery times which supposingly are derived from “clocks” (the measurement instrument). Purpose of the MSA is therefore to check whether the “clocks” are correctly recording the process data (delivery times) in terms of: resolution, accuracy, stability, linearity, repeatability and reproducibility. That said, at a first sight and from my personal experience, usually there is not too much need and value in conducting MSA’s about “clocks” especially if the granularity of the measurements (in the case of delivery times) it’s hours or even days. In conclusion I would suggest that you can even skip the MSA step in your project, but now you know why!!!

@Straydog, I know very well what is (and it is much more valuable of a “simple” calibration) and the importance of MSA and I do push all my trainees and coachees to use it, but on the other hand I also convey the message to not “overprocess” projects where there is not a real need to use a specific tool and from what I could realize about Sebvlarsen project I could not see the real need to carry out an MSA about the clock used to record delivery times especially because the granularity required is about hours or even days. But if you could see something I could not, maybe you could share your advice to Sebvlarsen about the specific MSA he should carry out which is what he’s looking for.

Hi,

you can check out this article:

https://www.isixsigma.com/tools-templates/measurement-systems-analysis-msa-gage-rr/msa-be-sure-that-your-data-is-valid/

To understand how to do an MSA, you need to look into the information flow. The lead time for each order is characterised by the start time and the end time. What is the variation (actual or potential) of these measurement points. How large is the potential deviation in comparison to the total lead time.

Even though this analysis may not be as technical as Gage R&R you will understand, for example, that the measurement variation is in hours and the process itself lasts a few days – then it’s okay. Or there could be a short actual lead time, then a few hours difference in the data may distort it significantly.

Do you see what I mean?

You shouldn’t skip MSA.  Per my previous comments, you need to use the appropriate tool/method rather than force-fit a tool such as GR&R.  Also beware that there may be hidden (uncaptured) data when you’re dealing with something like delivery time.  I recall a case where the data showed that delivery times were nearly always met and measurement of days to delivery was accurate, according to MSA.  But customers complained.  It turned out that customer service did not enter orders until they could confirm with production since the system made it a real pain to change production schedules and/or orders and keep them in synch.  So this, and negotiating with the customer, was all done off-line with no record!