Acceptance based on product risk
PCBA Testing & Inspection Services
PCBA testing services including visual inspection, AOI, X-ray, ICT and functional test planning based on design risk and acceptance criteria.
What this service solves
A controlled path from requirements to acceptance
No single test method proves every assembly is good. Test coverage should be selected according to component visibility, circuit access, failure consequence and the customer’s acceptance requirements.
Best fit for
- Boards with hidden-joint packages
- Products requiring electrical or functional screening
- Programs needing documented acceptance records
Scope
Typical project deliverables
The exact scope is frozen in the quotation and approved build documentation.
| Deliverable | Control point | Customer output |
|---|---|---|
| 01 · Inspection and test-coverage proposal | Confirmed before material commitment | Approved assumptions and responsibilities |
| 02 · AOI/X-ray allocation by package risk | Confirmed before material commitment | Approved assumptions and responsibilities |
| 03 · ICT or flying-probe feasibility review | Controlled during manufacturing | Repeatable production instruction |
| 04 · Functional-test fixture input | Controlled during manufacturing | Repeatable production instruction |
| 05 · Failure handling and retest rules | Verified before release | Inspection, test or shipment evidence by scope |
| 06 · Test records by agreed scope | Verified before release | Inspection, test or shipment evidence by scope |
Start with your actual project
PCBA inspection and test-plan review
Use the enquiry form to describe the decision you need help with. We select the relevant project context; you remain in control of the details.
- Assembly revision and fault/coverage priorities
- Procedure, fixture, firmware and numerical limits where available
- Quantity, status of supplied boards and records required
Inspection and functional testing are not interchangeable. Standalone testing of supplied assemblies requires a feasibility review and is not automatically accepted.
Request this reviewSpecify test coverage by the fault you need to detect
| Concern | Method to discuss | Input needed from the product team |
|---|---|---|
| Visible placement / polarity | Visual inspection and AOI | Released assembly drawing and component orientation |
| Hidden solder joints | X-ray where appropriate | Package map, inspection scope and acceptance criteria |
| Structural electrical faults | ICT or flying-probe feasibility | Net information, test access and isolation constraints |
| Firmware and configuration | Programming and version verification | Approved image, checksum/version and programming interface |
| Product behavior | Functional test | Sequence, loads, interfaces, measured limits and failure rules |
Bare-board electrical testing and populated-board functional testing serve different purposes. Neither should be described as complete coverage of every possible product fault.
Technical references
Use the applicable standard revision and the component manufacturer's documentation when defining your requirements.
Workflow
How a build moves forward
- 01
Qualification
Confirm product stage, quantities and commercial fit.
- 02
File review
Identify missing data and manufacturability conflicts.
- 03
Quotation
Separate material, fabrication, assembly, test and logistics assumptions.
- 04
Approval
Freeze revisions, alternates and acceptance criteria.
- 05
Build & validation
Manufacture against the approved package and record agreed results.
Before release
Issues to resolve with the build team
Record an owner and an agreed resolution for any issue that applies to your design.
- Claiming 100% coverage without a coverage analysis
- Testing without pass/fail limits
- No ownership for fixture maintenance
- Rework without retest rules
Buyer questions
Frequently asked questions
What is the difference between AOI and X-ray?
AOI inspects visible features such as placement and solder joints. X-ray is used for hidden joints and internal solder features that optical systems cannot see.
Who supplies the functional-test procedure?
The customer normally defines product behavior and acceptance limits. The manufacturer can help translate that into a repeatable fixture and production procedure.
Does every board need ICT?
No. ICT feasibility depends on test access, volume, fault coverage and fixture economics. Other combinations may be more appropriate.
Next step
Ready for a build review?
Share your project stage, quantity and target date. We will confirm the files, process and testing information needed for an accurate quotation.