This verification is essentially used to check the reliability of the sensitivity of the metal detector (there is actually an equally important rejection reliability at the same time, which will not be discussed here).
If you deal with metal detectors on a regular basis and follow this CCP very closely, you should be able to notice a phenomenon:
A certain validation on a certain day, and your test stick passes straight through without being rejected.
( Only cases that are not detected by MD, rather than detected but not rejected, are discussed here. )
When you feel confused and revalidate at this moment, this phenomenon no longer occurs! And it may not happen for a long time thereafter.
This is actually detecting reliability, so we need verification.
Therefore, different companies may take different programmes.
For example, the 30 times you have here (which I believe should be after a new product or MD has been adjusted), as well as the hourly verification that almost all companies have.
As of now there doesn't seem to be a more advanced technology to confirm the reliability of MD, so almost all users can only check it by repeated testing, including relevant industry standards with similar requirements.
We've been working in the extremely challenging field of MD service support, so we noticed this situation many years ago, and after further research and testing with our customers, we actually have the technology, which we currently call DPA ( Digital Performance Analysis technology ).
Here I'll upload another simple brochure with a simple example there.
Simply put, if the risk can be controlled by technical analysis in advance, it is almost impossible to encounter the risk of a missed test piece again.
This means in practice extremely reliable detection reliability and sensitivity.
The highest record we've tracked is 260,000 consecutive reliable detections without a missed detection.
We look forward to seeing more interesting professional issues and relish the challenge!