Download IVISION Catalog
01Confirm the reject record
Use the authoritative disposition and reason source.
Learn from confirmed product rejections
A useful reject review begins with actual disposition records. Where images and identifiers are available, compare visible examples with the documented reasons and process conditions, without assuming that every visual anomaly was rejected or that a pattern proves its cause.
Confirm detector support, camera suitability and the proposed event workflow before deployment.
Plan a reject review
Example
Without IVISIONStandard CCTV feed
With IVISIONIllustrative event overlayThe Process
How It Works
Keep reject reasons tied to verified evidence Help quality teams connect documented dispositions with visible examples and process context.
01
02Link available evidence
Verify any image, product identifier and observation-time connection.
03Review the recurring condition
Inspect representative examples and inconsistent reason labels.
04Investigate the process
Quality engineers test causes and corrective actions using appropriate evidence.
Explore Your Options
Explore Related Capabilities
| Dimension |  Rejected-product analysis |  Defective-product detection |
|---|---|---|
| Observation |  Confirmed reject dispositions with available product images and context. | Visible finished-product features outside validated acceptable examples. |
| Event criteria | A reviewer groups verified records by documented reason or relevant process condition. | A supported defect observation meets the agreed review criteria. |
| Monitoring setup | Verify record linkage, reason definitions and review period. | Define product variants, visible defects and acceptance references. |
| What it cannot establish | Images alone do not establish that an item was rejected or identify the cause of a defect. | A visual pass does not establish internal condition, function or full specification compliance. |
| Practical outcome | Help quality teams connect documented dispositions with visible examples and process context. | Help final inspectors focus on items needing a closer acceptance check. |
Illustrative demonstration
Review The Event.
Understand The Context.
Example footage and simulated events explain the review workflow. They do not measure detector performance.
Sites overview
Example Activity
No matching events.
Related Scenarios
View More
Production MonitoringDefective-product detection
Provide candidate visible anomalies for final inspection.
Read More
Production MonitoringLabel and barcode verification
Distinguish label mismatches from read failures.
Read More
Production MonitoringProduct-quality inspection
Keep dispositions connected to controlled acceptance criteria.
Read MoreEXPLORE WHAT’S POSSIBLE
What Can You Do With Rejected-product analysis?
01 / 04 · REJECTED-PRODUCT ANALYSIS
Component manufacturing
Reason labels may hide different visible conditions.
Example event: Confirmed rejects show several surface appearances.
Operator response: Review examples against the actual disposition criteria.
Practical value: Improve the focus of quality investigation.
Discuss this capability
02 / 04 · REJECTED-PRODUCT ANALYSIS
Packaging
Read failures and wrong labels can be mixed in records.
Example event: Verified cases contain different documented reasons.
Operator response: Separate uncertain reads from confirmed mismatches.
Practical value: Clarify the issue being addressed.
Discuss this capability
03 / 04 · REJECTED-PRODUCT ANALYSIS
Assembly
A recurring visible mismatch needs context.
Example event: Linked images show a repeated assembly condition.
Operator response: Check revision, material and process records before assigning cause.
Practical value: Support evidence-based corrective review.
Discuss this capability
04 / 04 · REJECTED-PRODUCT ANALYSIS
Deployment review
Use inspection images that show the documented condition.
Visibility: Missing images and inconsistent labels limit conclusions.
Configuration: Verify disposition linkage and analysis tools; automatic root-cause reporting is not assumed.
Privacy: Protect product identifiers and confidential quality records.
Human review: Quality teams confirm classifications and causal explanations.
Discuss this capability
Frequently asked questions
Rejected-product analysis, Explained.
Review confirmed reject records and their available images to investigate recurring quality issues.
Is every flagged anomaly a rejected product?
No. Only a confirmed disposition establishes rejection.
Can it identify the cause of every reject?
No. Process investigation and additional evidence are required.
What if reject reasons are inconsistent?
Review and normalize them through the quality process before comparing trends.
Can it prove a corrective action worked?
Evaluate subsequent quality data and operating conditions, not image examples alone.
Find your fit
What are you trying
to achieve?
Help quality teams connect documented dispositions with visible examples and process context. For Quality engineers, Production improvement teams.
Workflow to discuss
Rejected-product analysis + Start from confirmed quality dispositions.
