Industrial computer vision
Computer vision for industrial inspection and event review
A product change reaches the inspection station, and the review queue grows. Some flagged items are acceptable, while inspectors still need to catch the defect that matters. NeoBram builds computer-vision workflows around a defined visible condition, representative images and a clear response, helping your quality team evaluate a useful check in the conditions its line actually produces.
Start small, review the result
A practical first step
- Start with
- One visible condition and the decision it should support.
- The scoped work can produce
- A feasibility scope can cover a camera-view assessment, a defect and sample plan, and a prototype with results for review.
- Your team brings
- Accepted, rejected and difficult images; line-speed and item-identification context; and the quality or safety response owner.
- Next decision
- Decide whether the supplied-image evidence justifies a line trial. Agree hardware, installation and production integration separately.
Deliverables, access and responsibilities are agreed for the engagement.
Choose the visual condition your team needs to catch
A missing label, unreadable date code, surface defect and restricted-zone event need different definitions and evidence. Quality or safety specialists identify acceptable variation, important exceptions and the consequence of a miss. First assess whether the condition is visible from the proposed camera position.
Make the rule specific enough for reviewers to apply consistently. A label can be present but damaged, misplaced or associated with the wrong product. Resolve or record expert disagreement before treating a sample as a definitive training example.
Include product changes, reflective surfaces, damaged packaging, movement and occlusion. These can cause missed defects or unnecessary flags. Candidate checks need their own scope; plant-event monitoring has a different response process from product quality release.
From a packaging image to an inspector’s decision
An illustrative label-presence check starts with visibility at the intended speed and orientation. The review queue must connect the image to the correct product and item, then make the inspector's response practical without creating a new bottleneck.
Conventional image processing may suit some checks; learned patterns may suit others. Dedicated inspection can require controlled lighting, optics or triggering. Assess image quality and timing before moving from a supplied-image test to a production installation.
Three outcomes in a label-review queue
Schematic packs, not inspection images. Synthetic label-presence review: product [variant] · item [reference] · captured [date/time]. Keep this context with each inspector decision.
Acceptable
Label visible in the expected location for this product.
Inspector records the reviewed disposition under the agreed quality procedure.
Suspected defect
Expected label is not visible on this item.
Inspector checks the pack and chooses its disposition.
Unjudgeable image
Glare obscures the label area.
Use the agreed manual check or recapture path; keep the outcome unresolved until reviewed.
These are review states, not a production-release claim. A physical reject mechanism requires its own engineering and approval.
Related work: high-mix electronics inspection
NeoBram's published high-mix electronics account describes selected defect checks in product context, an approved camera and edge-compute setup, and human review of uncertain results. Reviewed events and operator feedback supported controlled model changes; the manufacturer retained quality-release authority.
The linked anonymized, company-reported account explains its independent-validation limits. It does not establish coverage of every rare defect or zero customer escapes.
Build the check around real line conditions
Keep the same item and similar frames out of both development and test sets. Show sample gaps, especially for rare defects, with sample counts and uncertainty. Keep model flags, reviewer dispositions and physical outcomes separate.
Define the owner and fallback for obscured cameras or failed feeds. Assign camera upkeep, product-change review and controlled model updates before regular use; an inspection model does not replace machine safety systems.
Processing can be near the camera, on site or in an approved cloud environment according to the task. NeoVision supports defined plant-video monitoring scenarios. Specialized quality inspection needs its own scope and evaluation.
- Coverage: does the test represent important defects, products, lots, camera views, lighting, speeds and changeovers?
- False accepts: how many known defective test items passed, out of all known defective test items?
- False rejects: how many known conforming test items were incorrectly flagged or rejected, out of all known conforming test items?
- Unjudgeable images: how often is no reliable decision possible, and what human response follows?
- Response time: can the full path keep pace, including capture and human review or a separately scoped reject mechanism?
From supplied images to a line trial
Evidence from supplied images establishes only the tested image scope. Hardware, lighting, installation, line interfaces and production support need explicit ownership before an installed system is assessed.
Compare the complete check with current practice: missed defects, unnecessary rejection, unjudgeable images, response delays and operator effort. Include equipment, software, maintenance, camera cleaning and fallback inspection in the operating assessment.
Reduce avoidable inspection and quality-loss costs
Compare inspection-related loss and operating expense, including missed defects, unnecessary rejection, rework and review. Add cameras, lighting, installation, software, upkeep and repeat evaluation where needed. A flagged defect is not automatically a verified loss avoided. Preserve quality requirements and use supported net savings to decide whether to add a line or defect class.
More clarity
Questions and answers
Can we use existing CCTV?
Sometimes. Coverage, resolution, motion and lighting must suit the specific task; a feed suitable for monitoring may not support detailed inspection.
Can you promise an accuracy percentage?
A meaningful measure needs agreed conditions, representative evidence and an acceptance test. We do not promise one figure for every site.
Will people still review results?
Review can focus on defined exceptions and sampled images when your approved process allows it. Your quality or safety team defines the automation boundary and response. For inspection, tune on development examples and test false accepts (defective items passed) and false rejects (acceptable items rejected) against agreed limits. Monitor performance as products and conditions change. Event monitoring needs its own missed-event and false-alarm checks.
What should we bring to feasibility scoping?
A clear check definition, permitted representative images, timing requirements, acceptable examples and known failures. Include the person who owns the response and any physical constraints on installation.
How do we assess value beyond model accuracy?
Compare total inspection and correction effort, important misses and unnecessary rejection with current practice. Include imaging equipment, integration and maintenance. Faster inspection is not a gain if quality or usable output suffers.
Start with one business problem