Feedback LearningThe more you teach it,the smarter it gets.

Every piece of operator feedback matters. Report false calls and defects to help the AI learn what is acceptable and what needs attention.

One clickFrom a wrong call to a training exampleReported at the review screen, during production. Nothing leaves the machine.

80%Fewer false callsAgainst a rule-based baseline, and it keeps improving with every report.

Continuous learningImprove the model with each round of feedback.Update after reviewing a false call, or collect feedback during production and update later.

You provide feedback. The AI learns from it.

STEP 01 · OPERATOR

Mark it OK or NG

Mark the component as OK or NG. Your feedback can apply to other components in the same group.

STEP 02 · OPERATOR

Choose what the AI learns from

Turn training on to include this feedback in model updates. Leave it off to record the feedback without using it for training.

STEP 03 · THE AI

Update the AI

Run AI Update to learn from the selected feedback and adjust inspection parameters automatically.

STEP 04 · MACHINE

Re-inspect

Inspect the board again and review the updated results.

Same part number, different supplier.

A different supplier can mean a different body shape or marking, even for the same part number. Mark an acceptable variation as OK so the AI can learn to recognize it across the component group.

Variation is not a defect

A different marking font or a change in body colour between batches does not necessarily mean a defect. Your feedback teaches the AI which variations are acceptable, while lifted leads, solder bridges and missing components remain inspection targets.

An update will not touch what you set by hand.

Your settings stay

An update works around anything you set yourself.

Manual settings take priority

Where your setting and the update disagree, yours is kept.

The line comes first

An update waits for the line, not the other way around.

Undo an update

Not what you wanted? Put it back the way it was.

How we stand out from the alternatives.

The same false call, handled three ways.

Tune thresholdsBY HAND

Generic AI AOIVENDOR RETRAINS AND SHIPS IT

DaoAIFEEDBACK AND AI UPDATE

What actually changes

The accept band widens for everything judged by that parameter

Nothing on your machine. The request goes to the vendor and the deployed model stays as it is

The model learnsIt gains an example of what that component looks like when correct

Effect on real defects

Defects inside the widened band are accepted too

Unknown until the next model arrives, and it was not trained on your defect

Still caughtA defect near the same score is still outside what is now normal

Where the decision lives

A number somebody changed, and the reason is not stored with it

With the vendor, in a dataset you do not hold

In your datasetA labelled example in the product’s dataset, with the image attached

Scope of the change

Everything that parameter governs, whether you meant it or not

Whatever their retraining changed, across every plant running that model

The group you chooseOne position, a class, a part number, or a package

Who can do it

Whoever has permission to change inspection parameters

An AI engineer, usually theirs

Any operatorCalls can be reported without permission to change the program

Long term

The threshold stays loose and the reason is not recorded

You wait on a release cycle, and your images may have to leave the plant to get there

Fixed for goodThe model has one more example and does not call that component again

Four questions we get every time.

How many reports before it stops calling that component?

It depends on the item and how different the component looks. The machine tells you when a product has collected enough to be worth an update.

Does reporting a false call change the program?

No. A report adds an example. The program changes when someone with that permission runs an update, and that can be undone.

Does the line stop while it retrains?

No. An update waits for the line rather than the other way around.

Will an update overwrite our engineer’s thresholds?

No. Anything you set by hand is what the machine keeps.

See it fix a false call.

Join an engineer for a live, 30-minute demo on your board. Report a false call, run AI Update, and inspect the board again to review the result.

NEXT IN PROGRAM & LEARNFull Control →

Want more control? Adjust inspection settings yourself, from individual thresholds to the tools used on each component.