Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for manufacturing engineers

Production Test Yield Review Agent

Find the real cause of a yield drop and confirm the fix with later yield

Production Test Yield Review Agent: what goes in, what the agent does and what you get

What it does

Yield drops from 97% to 91% and the team blames the operator, the supplier or bad luck. This agent reads the production test data and groups failures by test step, lot, station, shift and component date code. It looks for the grouping where the failures concentrate, and tests each likely cause against the data: does the failure follow one station, or one reel of parts? It lists the best explanations with the numbers. It proposes a corrective action, such as recalibrating a fixture, quarantining a lot or changing a test limit review. After the change it checks yield for the next batches. The engineer approves the corrective action. Edge case: failures follow one station, but that station only tests one product, so the agent checks the product mix.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedYes, continueNoNo 1 STARTS WHEN Yield falls below target 2 USES A TOOL Load test results with lot, station and componentdata 3 DOES Group failures by test, station, shift, lot and datecode 4 DOES Rank groupings by concentration and size 5 CHECKS THE RESULT Does the top cause hold after checking product mixand sample size? If not: drop it, check the next grouping, and combinefactors. Back to step 3. 6 DOES Draft a corrective action with expected yield effect 7 YOU APPROVE Engineer approves the corrective action 8 USES A TOOL Apply the action and mark the affected units andlots 9 USES A TOOL Read the yield for the next batches 10 CHECKS THE RESULT Is yield back within 1 point of target? If not: reopen the analysis with the new data and testthe next cause. Back to step 3. 11 RESULT Yield report with cause and result
Read the steps as a list
  1. Yield falls below target
  2. Load test results with lot, station and component data
  3. Group failures by test, station, shift, lot and date code
  4. Rank groupings by concentration and size
  5. Does the top cause hold after checking product mix and sample size?If not: drop it, check the next grouping, and combine factors. Back to step 3.
  6. Draft a corrective action with expected yield effect
  7. Engineer approves the corrective actionThe agent waits here for your OK.
  8. Apply the action and mark the affected units and lots
  9. Read the yield for the next batches
  10. Is yield back within 1 point of target?If not: reopen the analysis with the new data and test the next cause. Back to step 3.
  11. Yield report with cause and result

How it decides

It ranks groupings by how strongly failures concentrate beyond what chance would give, and checks each cause for confounders before it recommends action.

  • Require at least 30 failures in a group before calling it a cause
  • Check product mix before blaming a station
  • Quarantine a lot when its failure rate is 3 times the others
  • Review again after 3 batches or 500 units

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Yield target
  • Minimum group size (default 30)
  • Fields used for grouping
  • Review window (default 3 batches)
  • Who approves quarantine

What keeps you in control

It always asks you first

  • Engineer approves corrective actions
  • Quality lead approves lot quarantine

Hard limits

  • Never release or scrap units without approval
  • Never loosen a test limit to raise yield

It stops when

  • Done: yield recovers and the cause is documented
  • Stop: no cause is found and the agent recommends a deeper investigation

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensYield fell from 97% to 91.4% over two weeks. Failures at the 3.3 V rail test were 70% of the total. Station 4 showed 3 times the failures, but it also ran the newer board variant, so the check failed. Controlling for variant, the failures followed one reel of regulators from date code 2411. The engineer quarantined the reel and yield recovered to 96.6% in the next three batches.

More agents for manufacturing engineers