Feeding Vision Inspection Results into the Traceability Chain
A vision station that lights a tower lamp and drops NG photos into a dated folder has done only half the job. When a complaint arrives weeks later, quality still cannot answer which part, which station, which operator, which fixture and which process curve sat next to that judgment. Full-element traceability already runs across barcode ↔ machine ↔ operator ↔ fixture ↔ process curve; this article is about folding the vision judgment into that same chain — not about choosing a vision toolchain.
Detected but untraceable counts as not detected
Inspection that cannot be retrieved later does not protect the plant. Audits, customer complaints and containment all ask the same question: given this serial or nameplate, what was judged at which station, by whom, with which fixture, and under which process curve. If the vision result lives only on the camera PC, the answer is a file hunt, not a query.
Quality traceability as we deliver it already binds barcode, machine, operator, fixture and process curve in both directions. On stations that retain process curves, a single machine keeps on the order of ten thousand rows of process data per day — 14,400 rows per machine per day in full in delivered work. Vision data that does not join that record cannot take part in forward or backward search, no matter how clearly the station itself called NG.
- NG images sit in dated folders on the vision PC; searching by part ID is not possible
- The judgment only drives a lamp or an interlock; it is never written as a field on the unit record
- Process curves and vision results live in two files; a complaint cannot place them on the same timeline
The fields that must be written
The vision station can keep using the toolchain it already runs. What the traceability chain needs is a small, stable set of fields written at the moment of judgment, keyed to the same part ID the rest of the line already scans. Leave any one of these out and later retrieval breaks in a different place.
- Part ID (barcode / nameplate / serial): binds the vision record to the unit that moves down the line
- Station (and machine ID): locates which process step produced the judgment
- Judgment (OK / NG, and the inspection item): states what was decided
- Capture (NG snapshot path or archive ID): keeps visual evidence for complaints and audits
- Timestamp: places the judgment on the same timeline as the process curve
- Recipe / SOP version: records which process and work instruction were in force
Where vision stops and the MES / quality module starts
Vision should not grow into a second MES, and MES should not re-implement inspection algorithms. The split is by responsibility: the vision station triggers, images, judges and archives evidence; MES and the quality module own genealogy, process curves, SPC and recall.
The join is part ID + station + timestamp. Once those three match, operator, fixture and process-curve rows already stored by the quality module can sit next to the vision result. GMP and ISO traceability requirements are met by the chain as a whole, not by the camera PC acting alone. On general manufacturing stations — assembly, packing and appearance — this split keeps both systems maintainable.
- Vision station: trigger, image acquisition, OK/NG, NG capture and local archive
- MES / quality module: unit genealogy, operator and fixture binding, process-curve retention, SPC, containment and recall
- Shared contract: the six fields written once at judgment time, readable later by query
- What to avoid: a parallel spreadsheet of vision results, or asking MES to be the image archive of record
Data item, source, and what tracing uses it for
Put each field next to where it comes from and what a later query actually does with it. The table is the write-contract; if a column is empty at go-live, that use is not available when a complaint arrives.
| Data item | Source | What it is used for when tracing |
|---|---|---|
| Part ID (barcode / nameplate) | Station barcode or RFID scan | Joins the vision record to the unit; enables forward and backward search |
| Station / machine ID | Station configuration or PLC | Locates which process step produced the judgment; supports station-level containment |
| Judgment (OK / NG and item) | Vision runtime | Shows pass/fail and inspection item without reopening the image |
| NG capture (path or archive ID) | Camera snapshot at judgment time | Visual evidence for a complaint, audit or training review |
| Timestamp | Clock aligned with the process historian | Places the judgment on the same timeline as the process curve |
| Recipe / SOP version | MES recipe or SOP master | Shows which process and work instruction were in force after a changeover |
Operator and fixture do not have to be written by the vision runtime if MES already binds them to the same part ID and station. Omit the join key, and those bindings cannot be found later.
Assembly error-proofing: state capability by route
On assembly error-proofing, capability has to be stated by route; a blanket claim that AI-SOP is already mature is not one we make. HkVisionPro — multi-layer assembly, layer-by-layer feature-point inspection, automatic flow-through when the current layer is all OK, NG alarms with capture and evidence archiving — is deployed, and those NG captures are the kind of evidence the traceability chain can store.
The OrpaonVision motion-recognition standalone route is close to commercial use, but still requires scenario acceptance against workstation data, cycle time and acceptance criteria. It must not be described as already delivered at scale. When a station does pass acceptance, the same field set — part ID, station, judgment, capture, timestamp, SOP version — is what would enter the chain; the route itself is not a substitute for that write.
The OrpaonSOP Hikrobot VM plugin route is still in R&D and joint validation, and is not offered as a standard deliverable. Inspection performance is confirmed in scenario acceptance against the specific station, samples and acceptance criteria; this article makes no numeric claims.
Summary
A vision station that only detects has not finished the quality job. Until the judgment, capture and timestamp sit on the same record as barcode, machine, operator, fixture and process curve, later complaints and audits cannot use them. The field set is small; the failure mode is leaving it on the camera PC.
If the station already inspects but results never appear in a trace query, start by writing the six fields at judgment time and joining them to the existing genealogy. Toolchain selection is a separate discussion.
Discuss how vision results enter your traceability chain
Tell us the station type, how you identify the unit today, and whether MES already binds operator, fixture and process curves. An English-speaking contact can outline the field set and a pilot write-path.
Contact Us