AI AOI for EMS and Contract Manufacturers

What makes EMS inspection different

Many customers, many short jobs. A contract manufacturer may run several new part numbers a week, often on the same line. Each job needs an inspection program before the first board ships, and programming time multiplies with every changeover. When one engineer owns AOI programming, that person becomes the line's bottleneck.

CAD data is often missing or late. Customers send kits without usable CAD, centroid files arrive incomplete, or legacy boards have no data at all. An AOI that needs CAD and a component library to start can't inspect the job until someone rebuilds that data.

Each customer sets its own acceptance class. IPC-A-610 defines three classes: Class 1 for "General Electronic Products," Class 2 for "Dedicated Service Electronic Products," and Class 3 for "High Performance/Harsh Environment Electronic Products." The same line may build all three in one week, with different thresholds for each job.

Customer data is not yours to share. Board images show your customers' designs. NDAs and quality agreements often limit where that data can go, and customers in defense, medical and automotive markets ask more questions about it.

Customers ask for traceability. IPC-1782B, the IPC standard for manufacturing and supply chain traceability, sets "minimum requirements for manufacturing and supply chain traceability based on perceived risk." More customers expect board-level inspection records.

Margins depend on operator time. False calls cost review time on every board, and long programming cycles keep a line waiting.

How DaoAI fits EMS operations

• Golden-board programming. Every DaoAI AOI programs itself from one golden board in 30 seconds to 5 minutes, with no CAD, Gerber or component library (auto-programming). CAD is optional, never required.
• Program away from the line. You can program a product on another machine, export it, and import it on the production machine, so the SMT line keeps running (production integration).
• Panels and arrays. See panel inspection and panel and array AOI.
• Per-job control. Thresholds are adjustable per check, and permissions separate who can program, tune and train from who can only inspect (full control).
• Customer data stays in your plant. All AI runs on the machine; inspection data never leaves your factory (data security).
• Records customers can audit. Every inspection is stored with its images and verdict. Exports include CSV results, defect crops and the whole-board image per unit, with defect codes mapped to your MES vendor codes.
• Low false calls. With tuning, the false-call rate can reach about 1%.
• Support where you are. Sales and engineering support come from DaoAI's North American team in Vancouver, plus authorized partners. There are 1,000+ systems in the field.

For a step-by-step evaluation framework, see how to choose an AOI for high-mix PCB assembly and how to calculate AOI ROI and payback.

Recommended DaoAI configurations

Compare all models on the machines page.

How to run a fair trial on your own jobs

1. Pick two or three jobs that are hard to program today: dense boards, missing CAD, or frequent revisions.
2. Time each one from golden board to running inspection.
3. Count false calls per board over a full lot, and note how many your operators would have to review each shift.
4. Check that the exported records cover what your customers ask for in their quality agreements.
5. Ask who supports the machine in your time zone, and how fast.