Managing the Sample Library
A sample library is the foundation under a vision system. It proves at acceptance that the system can do the job, it monitors day to day whether the system still does it, and it settles disputes about whether the system or the criteria misjudged a part. It is also the asset that disappears most easily. It ends up in a drawer without numbers, or spread across several boxes without a list, or in the head of one engineer. By the time it is needed, nobody can say which sample is which, or whether they still represent what they did.
Key takeaways
- Every sample must answer three questions: what it is, why it is in the library, and whether it is still valid.
- Physical samples change over time and need sealed storage and periodic review.
- The library version tracks the criteria version; revise one and revisit the other.
- Without a list and a named owner, the library will not survive staff turnover.
How much a vision system can be trusted depends heavily on the quality of the samples behind it. Acceptance needs them to state a detection and false call rate. Routine monitoring needs them to confirm the criteria still hold. A customer complaint about a part judged wrongly needs them to establish whether the system erred or the criteria were understood differently. The library is not supporting documentation, it is part of the system — and it is the part hardest to rebuild, because defect samples arise by chance and the lot that produced them may never recur.
What each sample record has to carry
A usable record answers three questions: what it is (defect type, severity, location), why it qualified for the library (who judged it, under which revision of the criteria, when it was admitted), and whether it is still valid (storage, most recent review, current status). Those three map onto three groups of fields. Leave any group out and the sample becomes unusable at the moment it is needed.
| Group | Fields | Why |
|---|---|---|
| Identity | Unique number, defect type, severity, location sketch | Without a number it cannot be cited; without a type it cannot be counted in a detection rate |
| Origin | Source lot or date, reason for admission | Establishes whether it represents real production |
| Judgement | Conclusion, judge, criteria revision applied, date | Establishes why it is in the library |
| Status | Storage, last review date, review conclusion, in use or withdrawn | Establishes whether it still represents what it did |
| Image | Original image and annotation at admission | The object changes; the image is the most reliable record of how it looked |
The samples change by themselves
This is the counterintuitive part: the things used to measure whether the system has changed are themselves changing. Steel rusts slowly in humid air; aluminium dulls; plastics deform slightly with temperature and humidity; painted surfaces accumulate fine scratches from handling; everything collects dust. The change is slow enough that nobody notices, but over a few years a part that was "acceptable with a light scratch" may have become "clearly unacceptable". The system, quite correctly, starts rejecting it — and the reference sample reading begins to drift. A maintainer who assumes the system is at fault will adjust parameters and damage a system that was working correctly.
- Photograph on admission. The image is the only basis for judging whether the object has changed. Take it under the same imaging conditions as the line, and keep it bound to the sample number. Years later, putting the image beside the object makes any change obvious.
- Seal, shade, and hold conditions steady. This need not be a precision environment. Avoiding direct sunlight, damp corners and large temperature swings, and using a lidded box in a fixed cupboard, is enough to slow the change considerably.
- Handle as little as possible. Oil and sweat are common contaminants on appearance samples. Tweezers or gloves are the cheapest discipline available.
- Compare against the image periodically and record the conclusion. Once or twice a year, review the key samples alongside their admission images and decide whether each is still usable. Withdraw anything that has changed, but keep it on file rather than discarding it — it may still be needed for historical traceability.
When the person who built it leaves
The most common way a sample library fails is not damage but loss of explanation. The engineer who assembled it knows which samples are critical, which once caused a disagreement, and which should have been withdrawn but never was. After they leave, it is a box of unidentified objects. There are only two defences: get the information onto paper instead of leaving it in memory, and give the library a named owner rather than an individual's possession. Numbers, a list, labels and review records look like bureaucracy; their function is converting personal memory into an organisational asset.
The owner need not be a dedicated role. Attaching it to a quality or process position, with responsibility for periodic review and for maintaining the records, is the common arrangement, and it takes very little time — reconciling the list against the physical samples once a quarter and organising one status review a year. What matters is that the responsibility has a name and a handover requirement, rather than being shared by everybody, which in practice means held by nobody.
Common questions about sample libraries
Should the full original images be kept?
Yes. They consume storage that grows over time, but nothing replaces them: they are the only objective record of how a sample looked, and the most direct basis for reviewing a judgement. Give sample images their own retention policy rather than including them in the routine cleanup of production images — production images can be archived by lot to reclaim space, while sample images should be kept long term.
How many samples are needed?
The acceptance set is a statistical question, driven by the target detection rate and the confidence level required, and it is usually not a small number. The routine monitoring set is different: a handful of carefully chosen, stable parts is enough. They answer different questions — whether the system can do the job, and whether it still does — and the two should not be confused.
Can samples be returned to production after use?
It is better not to. Returning a part to the line means it will be scrapped, reworked or mixed back in with conforming parts, and the sample is gone. A defect sample, particularly a rare one, is usually worth more than the material it is made of. Samples should be marked as non-returnable at the point they are admitted.
Are your samples still usable?
Tell us how they are stored and how often the criteria are revised. We will say what the records are missing and which samples may no longer represent what they did.
Related articles
-
Alarm Fatigue: Why the Floor Turns the System Off
Many visual SOP systems are not beaten by technical problems — they are muted by…
Read more → -
Visual SOP Camera Selection and Mounting
Camera selection for visual SOP is not the same as for product inspection. The s…
Read more → -
Vision Monitoring at the Semiconductor Die Bonder
Semiconductor packaging stations are characterised by high precision, fast cycle…
Read more → -
Wrong-Assembly Alarms Without the False Alarms
The most common reason a visual SOP project fails is not poor recognition — it i…
Read more →
Need specific advice for your production line?
Our engineers can share practical approaches to process error prevention and SOP compliance inspection for your scenario.
Request a free trial plan