And then there are these buzzwords. Stable, under control, capable... And strange definitions such as "SPC should only be started when the process is capable", or "SPC when the process is stable and under control"...
The author has his own opinion. If all of this were adhered to, then most companies would be in a bad way when it comes to this topic. Because literature refers to beautiful examples. They really make a difference in training rooms...
And then you come up against reality!
A process that is stable and under control does not have to be capable, because this depends only on the specification limits.
A process that is unstable and not under control can be capable due to extremely large specification limits.
A process that is unstable can be under control because the instability is known.
And you have to start somehow, don't you? After all, the consistent implementation of SPC is part of the continuous improvement process.
It's not because it's difficult that we don't dare!
It's difficult because we don't dare!
Start it!. The Q-DAS Software tries to help you as much as possible. The topic is not easy, our Software is. We can just give possibilities.
A little “philosophical” explanations have been also described in the document of “Saving a QCC for procella”. In the last chapter an idea about how to start (after the preconditions have been done). Save QCCs, see what could happen. You accept the alarms? What to have it harder, smoother?
You want to use the WW2-scrap of Run/Trend/Middle Third? Use it. Test it. Maybe it is your process, where this can still help you. Maybe not.
If you don’t try, you can not fail and not learn.