Turnkey, Consigned, or Hybrid: Which EMS Model Fits Your Build?

Jul 17
EMS Basics

Turnkey, Consigned, or Hybrid: Which EMS Model Fits Your Build?

The right material model is not simply a purchasing choice. It determines who owns sourcing, shortages, substitutions, inventory, schedule risk, and the information needed to keep a PCB assembly moving.

TurnkeyEMS manages material sourcing
Consignedcustomer supplies the kit
Hybridresponsibility is intentionally shared

Turnkey

Micron sources and manages the material package.

Consigned

You provide the parts; Micron receives and builds the kit.

Hybrid

You supply selected items; Micron sources the balance.

EMS sourcing ownershipCustomer sourcing ownership

Two companies can request quotes for the same PCB assembly and need completely different material strategies. One may want its EMS partner to source every component. Another may already own inventory or control a proprietary device. A third may need something in between.

Turnkey, consigned, and hybrid models can all work. The best fit depends on material control, internal purchasing resources, component risk, cash and inventory preferences, schedule, and how clearly ownership is defined.

Quick Answer

The three models differ mainly in who owns the material work

Assembly may happen on the same production floor, but sourcing responsibility changes the RFQ, schedule, receiving process, shortage handling, and final cost structure.

Turnkey

One partner manages most or all material

Micron sources the bare boards, components, and specified material, then assembles, inspects, tests, and documents the build according to the agreed scope.

  • Reduces the customer’s day-to-day purchasing workload
  • Creates one coordinated path for material and assembly
  • Works best with a clear BOM, AVL, alternates, and approval rules
Consigned

The customer supplies the material kit

The customer purchases and provides the bare boards, components, or complete kit. Micron receives, verifies, stages, and uses those materials for the build.

  • Preserves customer control over suppliers and owned inventory
  • Can suit proprietary, allocated, or customer-controlled parts
  • Requires an accurate, complete, production-ready kit
Hybrid

Responsibility is divided by part or category

The customer supplies selected critical, proprietary, long-lead, or already-owned items while Micron sources the remaining material.

  • Balances customer control with EMS sourcing support
  • Can reduce delays around critical customer-owned components
  • Needs a precise ownership matrix to avoid gaps or duplication
Decision Framework

Start with three questions before choosing a model

The material strategy should support the project—not create a second project for engineering, purchasing, and production to untangle.

1

Who can source effectively?

Consider approved suppliers, purchasing bandwidth, pricing leverage, alternate approval, lead-time monitoring, and lifecycle knowledge.

2

Who needs material control?

Identify customer-owned inventory, proprietary devices, regulated sources, controlled AVL requirements, and traceability expectations.

3

Who owns the risk?

Clarify shortages, excess material, substitutions, schedule changes, handling damage, kit discrepancies, and end-of-program inventory.

Choose turnkey whenyou want the EMS partner to coordinate material and assembly through one controlled workflow.
Choose consigned whenyou already own, control, or must directly purchase most of the required material.
Choose hybrid whensome parts need customer control while the remaining BOM benefits from EMS sourcing support.
Turnkey Builds

Turnkey simplifies coordination—but depends on clear sourcing rules

A turnkey quote can combine material, PCB fabrication, assembly, inspection, programming, test, and related services into one managed scope. That can reduce handoffs, but it does not remove the need for customer decisions.

A

Advantages

One team coordinates material status with production readiness, reducing the disconnect between purchasing and the manufacturing schedule.

D

Decisions still required

The customer should define approved manufacturers, alternates, substitution authority, date-code or traceability requirements, and critical parts.

C

Cost considerations

Material cost, procurement effort, carrying risk, minimum buys, excess inventory, expedite charges, and market changes can all affect the quote.

F

Best fit

Teams that want fewer purchasing handoffs and can provide a stable BOM, realistic quantities, schedule context, and fast component approvals.

Turnkey does not mean “no customer involvement.”

Engineering approval may still be needed for alternates, lifecycle risk, sourcing exceptions, or changes that affect form, fit, function, quality, or compliance.

A stronger turnkey RFQ includes forecast context.

Quote quantities, likely repeat demand, target schedule, critical components, approved sources, test scope, and documentation needs help the EMS partner build a more useful material plan.

Consigned Builds

Consigned material gives the customer control—and responsibility

A consigned build can be practical when the customer already owns parts, has direct supplier agreements, controls proprietary components, or needs to maintain purchasing authority. The critical issue is kit readiness.

K

Kit completeness

A kit should match the current BOM and build quantity, including setup loss, attrition, alternates, reference designators, and any do-not-install items.

P

Packaging and identification

Parts should arrive in usable packaging with manufacturer part numbers, quantities, lot information, and labels that can be matched to the BOM.

M

Material condition

Moisture-sensitive, ESD-sensitive, damaged, loose, mixed, or poorly packaged components can create handling, verification, and schedule risk.

S

Shortage ownership

When a consigned kit is short or mismatched, the build may pause unless the RFQ defines who investigates, sources replacements, approves alternates, and absorbs delay.

A packing list is not the same as a verified kit.

The material still needs to be compared against the correct BOM revision, quantities, packaging condition, and production requirements before assembly can be scheduled confidently.

Include attrition and setup quantities.

Exact unit quantity may not be enough for feeders, setup, inspection, or normal process loss—especially for small components, cut tape, loose parts, or hand-inserted hardware.

Hybrid Builds

Hybrid can be the most practical model—if ownership is explicit

Hybrid builds are common because the real world is rarely all-or-nothing. A customer may supply a processor, display, enclosure, custom magnetics, or previously purchased inventory while Micron sources standard components and the balance of the BOM.

CCustomer-supplied examples

Proprietary components, allocated devices, customer-owned inventory, programmed modules, custom mechanical parts, or items tied to direct supplier agreements.

MMicron-sourced examples

Standard passives, common semiconductors, connectors, bare boards, approved alternates, hardware, and other items identified in the agreed sourcing matrix.

AApproval rules

Define which substitutions Micron may make, which require written approval, who approves technical changes, and how urgent material decisions are communicated.

RReconciliation rules

Clarify how shortages, overages, unused material, scrap, replacement parts, excess buys, and customer-owned inventory are reported and handled.

The hybrid rule: every BOM line needs one owner.

If both parties assume the other is buying a component, the build stops. If both purchase it, cost and excess inventory increase. A line-by-line ownership matrix prevents both problems.

Use status checkpoints before the build date.

Customer-supplied and Micron-sourced material should be reviewed together so shortages, approvals, PCB timing, stencil readiness, and test dependencies are visible before production launch.

Six Selection Factors

What should drive the decision?

The best model is the one that assigns each responsibility to the party best able to control it—and documents the handoff clearly.

1

Internal purchasing capacity

Does your team have the time, supplier access, systems, and component knowledge to source and monitor the complete BOM?

2

Material control

Do contractual, technical, regulatory, security, or proprietary requirements force direct control of certain parts or suppliers?

3

Inventory position

Do you already own usable material, or would a new purchase create duplication, stranded stock, or an avoidable cash commitment?

4

Schedule and lead time

Which party can secure critical components fastest, and how will shortages or late deliveries affect the planned build date?

5

Change frequency

Early prototypes with changing BOMs may benefit from flexibility, while repeat production needs stable ownership and approval rules.

6

Traceability and records

Define what supplier, lot, date-code, certificate, inspection, test, or material records the program needs—and who must retain them.

Ownership Matrix

Document the responsibilities before material starts moving

The labels “turnkey,” “consigned,” and “hybrid” are useful, but the working agreement should be more specific. A short responsibility matrix can eliminate costly assumptions.

Material sourcing

  • Who purchases each BOM line and the bare PCB?
  • Who approves manufacturers, suppliers, and alternates?
  • Who monitors lead times, lifecycle status, and shortages?
  • Who pays for minimum buys, excess, or non-cancelable material?

Receiving and kit control

  • Who supplies packing lists, labels, quantities, and lot information?
  • How are shortages, damage, mixed parts, and discrepancies reported?
  • What attrition or setup quantity is required?
  • How are moisture-sensitive and ESD-sensitive parts handled?

Engineering decisions

  • Who may approve substitutions and under what conditions?
  • Who resolves BOM, footprint, polarity, and documentation questions?
  • How quickly must approvals be returned to protect the schedule?
  • Which components are critical, proprietary, or no-substitute?

End-of-build reconciliation

  • How are unused customer-owned parts returned or stored?
  • Who owns excess turnkey material purchased for the program?
  • How are scrap, attrition, replacements, and damaged material recorded?
  • What inventory or traceability report is required at shipment?
RFQ Checklist

What to include when asking Micron to quote the build

You do not need every material decision finalized before contacting Micron. Sharing the current package and ownership assumptions makes the quote more useful and identifies what still needs to be resolved.

Core build files

  • BOM with manufacturer part numbers, quantities, alternates, and revision
  • Gerbers or ODB++, pick-and-place data, and assembly drawings
  • Target quantities, schedule, prototype or production status
  • Test, programming, inspection, and documentation requirements

Material model

  • Turnkey, consigned, or hybrid preference
  • Parts already purchased or physically available
  • Customer-controlled, proprietary, or critical components
  • Items Micron should source and quote

Sourcing rules

  • Approved vendor list, approved manufacturers, and alternates
  • Substitution approval process and no-substitute items
  • Traceability, date-code, certificate, or source restrictions
  • Known shortages, long-lead parts, and lifecycle concerns

Commercial context

  • Quote quantities and expected annual or repeat demand
  • Material ownership, excess inventory, and cancellation expectations
  • Schedule drivers, customer commitments, or regulatory milestones
  • Packaging, labeling, shipping, and finished-goods requirements
External Reference

Clear material ownership supports a controlled manufacturing process

Material strategy is connected to the wider quality system: approved components, revision control, handling, traceability, workmanship, inspection, and acceptance criteria all need a shared language. The IPC standards library is a useful external reference for electronics manufacturing quality, reliability, and consistency expectations.

The practical point is not that a sourcing model should be chosen because of a standard. It is that sourcing decisions should preserve the material controls, records, and acceptance requirements the program actually needs.

Related Micron Capabilities

Sourcing decisions work best when they are aligned with DFM, assembly, inspection, test, documentation, and production planning.

The best model is the one with the fewest hidden assumptions.

Turnkey can simplify coordination. Consigned can preserve customer control. Hybrid can combine the strongest parts of both. None works well unless material ownership, approval authority, shortage response, and inventory expectations are clear.

Micron can review your BOM, available inventory, critical components, sourcing preferences, quantities, schedule, and test requirements to help define a practical material model for the build.

  • Share the BOM and identify material you already own or must control.
  • Flag critical, proprietary, long-lead, allocated, and no-substitute components.
  • Clarify quantities, schedule, approval rules, test scope, and record requirements.

Suggested slug: turnkey-consigned-hybrid-ems-model
Meta title: Turnkey, Consigned, or Hybrid EMS: Which Model Fits? | Micron Corp
Meta description: Compare turnkey, consigned, and hybrid EMS models, including sourcing ownership, schedule risk, inventory control, and what to include in your RFQ.
Suggested category: EMS Basics   Secondary category: Supply Chain

Prototype vs. Production: Why the Same PCB Can Be Two Different Projects

Jul 10
DFM & NPI

Prototype vs. Production: Why the Same PCB Can Be Two Different Projects

A prototype and a production build may start with the same board design, but they are not managed the same way. One is built to learn quickly. The other is built to repeat reliably.

Same PCBdifferent build objective
Prototypelearn, debug, revise
Productioncontrol, document, repeat
Same PCB, prototype and production paths A stylized circuit board splits into prototype and production paths, showing that prototype work focuses on learning while production focuses on repeatability. Prototype Learn quickly DFM feedback, bring-up, ECOs Production Repeat reliably locked process, records, test Rev control BOM risk Test plan Build records
The big idea

A prototype answers one question. Production answers another.

It is common for an OEM to ask: “We already built prototypes. Why does production feel like a new project?” The answer is that the board design may be the same, but the manufacturing objective has changed.

A prototype build is usually about learning. Can the board be assembled? Are the footprints right? Are there polarity, placement, sourcing, programming, or bring-up issues? What needs to change before the next revision?

A production build is about repeatability. Can the same assembly be built again and again with controlled materials, locked documentation, defined inspection, test coverage, traceability, packaging, and a process that does not rely on memory or improvisation?

Quick Answer

Prototype and production have different definitions of success

The same PCB can move through very different workflows depending on whether the goal is discovery or repeatability.

Prototype

Built to learn

A prototype build gives the product team something real to inspect, power up, debug, test, revise, and learn from.

  • Supports DFM feedback and engineering changes
  • May tolerate controlled handwork, jumpers, or debug notes
  • Often uses small quantities and flexible material decisions
  • Helps expose assembly, test, programming, and design issues early
Production

Built to repeat

A production build should be stable enough to schedule, source, assemble, inspect, test, document, package, and repeat with confidence.

  • Requires clear revision control and controlled documentation
  • Needs approved materials, alternates, and sourcing assumptions
  • Benefits from defined inspection and test acceptance criteria
  • Requires records, labels, packaging, and process discipline
Prototype-to-Production Handoff

The transition is where many avoidable delays appear

The move from prototype to production is not just a quantity increase. It is a handoff from engineering discovery to controlled manufacturing.

Prototype to production handoff A process map showing prototype learning, pilot stabilization, and production repeatability. Prototype learn, debug, revise Pilot stabilize the process Production repeat with records

Review what changed

Confirm the latest BOM, PCB revision, assembly drawing, firmware, test notes, and ECO history before treating a prototype as production-ready.

Stabilize the BOM

Move from prototype substitutions to approved manufacturer part numbers, alternates, lifecycle checks, and sourcing assumptions.

Lock the build path

Define stencil strategy, panelization, programming, inspection points, traveler instructions, labels, and special handling needs.

Plan the test strategy

Decide what needs AOI, X-ray, ICT, flying-probe, programming verification, functional test, calibration, and per-unit records.

Run a pilot when needed

A pilot build helps validate process assumptions before a larger lot magnifies small documentation, sourcing, or test problems.

Document for repeat builds

Production should leave a clean record: revision, materials, traveler, inspection results, test logs, labels, packaging, and release notes.

What Changes

Six areas that change when a board moves into production

Prototype flexibility is useful. Production flexibility without control is risk. These are the areas to tighten before the build becomes repeat work.

1

Revision control

A prototype can survive with notes and redlines. Production needs a known design revision across the BOM, PCB files, assembly drawings, firmware, test instructions, and customer approvals.

2

Material strategy

Prototype parts may be bought quickly to keep engineering moving. Production requires approved alternates, lifecycle awareness, AVL rules, lead-time planning, and clear sourcing ownership.

3

Process repeatability

A one-time workaround may be acceptable during debug. Repeat production needs controlled setup, work instructions, fixture assumptions, inspection points, and defined acceptance criteria.

4

Test coverage

A power-up test may be enough for early learning. Production may require functional test, programming verification, ICT or flying-probe, calibration, logs, serialization, and failure handling.

5

Documentation and records

Production builds often need travelers, inspection records, test results, lot traceability, labels, packaging instructions, certificates, or customer-specific documentation.

6

Cost and schedule assumptions

Prototype timing is often driven by speed and availability. Production timing depends on repeatable sourcing, setup, test, inspection, yield, documentation, and shipment requirements.

Prototype Mindset

A prototype build should create useful learning

The purpose of a prototype is not only to make a small number of boards. It is to uncover risk while changes are still manageable.

Prototype success looks like this:

The board can be assembled, powered, inspected, debugged, and evaluated with clear feedback for the next revision.

The most valuable output is feedback.

DFM comments, BOM questions, placement observations, test access gaps, firmware notes, and build findings should feed the next design or pilot run.

D

Design feedback

Prototype builds are a good time to flag footprint issues, polarity ambiguity, component access, thermal concerns, panelization questions, and other DFM items.

B

BOM learning

Small builds often reveal missing manufacturer part numbers, unavailable components, unclear substitutions, lifecycle risk, or parts that need approved alternates.

T

Test intent

Early builds help determine whether the final production strategy needs simple power-up, flying-probe, ICT, functional test, firmware programming, or a custom fixture.

E

ECO discipline

Even during prototype work, engineering changes should be captured. Informal fixes become risk when nobody knows which changes made the board work.

Production Mindset

A production build should reduce variation

Production does not mean nothing will ever change. It means changes are controlled, documented, and reviewed before they affect cost, schedule, quality, or field performance.

R

Repeatable instructions

Operators, inspectors, test technicians, and shipping teams need the same controlled understanding of the job: what to build, how to inspect it, how to test it, and how to release it.

Q

Defined quality criteria

Workmanship class, inspection scope, special process notes, customer requirements, test limits, and documentation needs should be known before production begins.

S

Stable sourcing

Production should avoid surprise substitutions. Material decisions should be tied to approved alternates, AVL rules, traceability needs, and customer approval when needed.

L

Launch readiness

The cleanest transition often includes a pilot or first article step to validate setup, yield, test coverage, documentation, packaging, and repeat-build assumptions.

Common Handoff Risks

What can go wrong when a prototype is treated like production too soon

Most transition problems are not dramatic. They are small assumptions that were never converted into controlled instructions.

Unresolved prototype notes

A board may have worked only because of a jumper, rework note, part substitution, or firmware workaround. Production needs to know whether those items became approved design changes.

Assuming all parts are production-ready

The parts used for five prototypes may not be available, economical, traceable, or approved for 100, 500, or repeat production quantities.

Late test planning

If test access, firmware, fixtures, pass/fail limits, labels, or serialization are not planned early, production can stall after assembly instead of moving cleanly to release.

Mixed document revisions

A BOM revision, PCB revision, assembly drawing, or firmware image mismatch can create confusion even when each file looks correct by itself.

Customer Checklist

What to send when moving from prototype to production

A clean handoff package helps an EMS partner understand what was learned, what has changed, and what must now be controlled.

Design and revision package

  • Current BOM with manufacturer part numbers and approved alternates
  • Gerbers or ODB++ files, pick-and-place data, and assembly drawings
  • PCB revision, assembly revision, firmware revision, and ECO history
  • Known DFM notes from the prototype build and how they were resolved

Production planning details

  • Target quantities, annual forecast, and repeat-build expectations
  • Turnkey, consigned, or hybrid material preference
  • Critical components, AVL rules, lifecycle concerns, and customer approvals
  • Schedule drivers such as demos, regulatory testing, or customer shipments

Inspection and test requirements

  • AOI, X-ray, ICT, flying-probe, functional test, or power-up expectations
  • Firmware files, programming method, serialization, MAC/UID rules, and logs
  • Pass/fail criteria, calibration needs, fixtures, adapters, and test reports
  • Known prototype failures or bring-up findings that test should now cover

Release and shipping requirements

  • Labeling, packaging, ESD packaging, serialization, and customer labels
  • Inspection records, certificates, traceability, or lot documentation needs
  • Special processes such as conformal coating, cleaning, torque, or masking
  • Acceptance criteria and any customer-specific quality requirements
External Reference

Standards help turn build expectations into shared language

When a project moves toward production, expectations need to be clear enough for engineering, manufacturing, inspection, test, and the customer to interpret them the same way. IPC standards are a useful external reference for electronics manufacturing quality, reliability, and consistency expectations.

The practical takeaway for OEMs is simple: define workmanship class, inspection needs, test coverage, documentation, traceability, and acceptance criteria early rather than waiting until the first production lot is already underway.

Related Micron Capabilities

Moving from prototype to production connects design review, sourcing, assembly, inspection, test, documentation, and repeat-build support.

The best production builds start before the production lot begins.

If your prototype worked, that is a strong start. The next question is whether the design, BOM, documentation, test strategy, and process controls are ready to repeat.

Micron can help review the prototype history, current design package, material assumptions, inspection needs, test requirements, and documentation expectations so the transition into production is cleaner and less dependent on guesswork.

  • Share the current BOM, PCB data, assembly drawings, and revision history.
  • Identify prototype findings, known workarounds, unresolved DFM notes, and test gaps.
  • Clarify quantities, schedule, sourcing model, inspection needs, and production records.

Suggested slug: prototype-vs-production-same-pcb-different-projects
Meta title: Prototype vs. Production: Why the Same PCB Can Be Two Different Projects | Micron Corp
Meta description: A prototype PCB and production build can use the same design files but require different planning, sourcing, testing, documentation, and process control.
Suggested category: DFM & NPI   Secondary category: EMS Basics

AOI, X-ray, ICT, and Functional Test: What Each One Actually Catches

Jul 03
Quality & Test

AOI, X-ray, ICT, and Functional Test: What Each One Actually Catches

Inspection and test are not interchangeable. Each method sees a different part of the build: visible workmanship, hidden solder joints, circuit-level defects, and real-world product behavior.

4major inspection and test methods
Bettercoverage through the right combination
EarlierDFT planning reduces test surprises
PCB assembly inspection and test coverage illustration A stylized PCB surrounded by AOI, X-ray, ICT, and functional test checkpoints, showing that each method checks a different kind of issue. AOI visible defects X-ray hidden joints ICT circuit faults FCT behavior
The big idea

Inspection and test answer different questions.

When an OEM asks whether a board has been “tested,” the answer should usually be more specific. Was it optically inspected? X-rayed? Electrically checked at the component and net level? Powered up and exercised like the finished product?

AOI, X-ray, ICT, and functional test all reduce risk, but they do not catch the same issues. A strong electronics manufacturing strategy uses the right method for the right failure mode instead of assuming one inspection step can prove everything.

At Micron, this matters because high-mix, low-volume PCB assemblies often have different combinations of SMT parts, through-hole components, firmware, customer-specific acceptance criteria, and test requirements. The right coverage depends on the product, the design data, the volume, and the risk of a field failure.

Quick Answer

What each method is best at catching

Think of these as four different lenses. Each one sees something the others may miss.

A

AOI

Best for visible assembly conditions: missing parts, skewed components, polarity, solder bridges, insufficient solder, and placement issues.

X

X-ray

Best for hidden solder joints and features AOI cannot see, including BGA/QFN joints, voiding, shorts, and hidden alignment issues.

I

ICT

Best for circuit-level manufacturing faults: opens, shorts, incorrect values, orientation, basic powered checks, and net-level coverage.

F

Functional Test

Best for proving behavior: power-up, interfaces, sensors, firmware, calibration, loads, communication, and real-world operation.

Coverage Flow

A stronger test strategy layers coverage

The most practical approach is usually not “pick one.” It is to decide which risks matter, then build a coverage plan that catches issues as early and efficiently as possible.

Layered inspection and test strategy A process map showing AOI, X-ray, ICT, and functional test as layered checkpoints moving from assembly verification to product behavior verification. AOI Visible assembly conditions X-ray Hidden solder and voids ICT Component and net faults Functional Product behavior and firmware
Coverage Matrix

What each method catches — and what it does not

No single inspection or test method catches everything. The best test strategy depends on the board design, component types, risk level, available test access, and what the product needs to prove before shipment.

AOI

Automated Optical Inspection

Good at catching

Missing parts, wrong polarity, visible solder defects, skewed components, obvious placement issues.

May not catch

Hidden solder joints, internal opens, marginal electrical behavior, firmware or functional issues.

Most useful when

The board has visible SMT joints and the goal is fast, consistent workmanship inspection.

X-ray

X-ray Inspection

Good at catching

Hidden joint issues under BGAs, QFNs, LGAs, bottom-terminated parts, solder bridges, voiding, opens.

May not catch

Incorrect firmware, software behavior, many functional failures, or issues unrelated to hidden solder joints.

Most useful when

The assembly includes components where solder joints cannot be fully inspected visually.

ICT

In-Circuit Test

Good at catching

Opens, shorts, wrong values, missing components, many component-level and net-level electrical issues.

May not catch

Full product behavior, user-interface issues, wireless behavior, enclosure-level issues, final system performance.

Most useful when

The design has adequate test access and repeat production volume justifies a fixture or defined test setup.

Functional

Functional Test

Good at catching

Power-up failures, firmware issues, input/output problems, communication failures, product-level behavior.

May not catch

Some hidden solder defects, marginal component values, or process issues that do not affect the tested functions.

Most useful when

The assembly must prove that it behaves correctly in a realistic operating condition before shipment.

Method by Method

A closer look at the four checkpoints

Each method has a role. The best choice depends on what the design needs to prove.

A

AOI: automated optical inspection

AOI is a visual inspection tool. It uses cameras and programmed criteria to compare the assembled board against expected placement, orientation, and solder conditions.

  • Catches missing, shifted, skewed, or tombstoned components.
  • Helps flag visible solder bridges, insufficient solder, and polarity issues.
  • Works well as a fast process-control checkpoint after SMT assembly.
X

X-ray: seeing hidden solder joints

X-ray inspection is used when important joints are not visible from the outside. It is especially helpful for BGAs, QFNs, bottom-terminated parts, and dense assemblies.

  • Helps evaluate hidden bridges, opens, solder volume, and voiding.
  • Useful when AOI cannot see the actual solder interface.
  • Can support documentation needs when image retention is requested.
I

ICT: circuit-level manufacturing test

In-circuit test uses physical access to the board to check electrical conditions at the component and net level. It is strongest when test access is designed in early.

  • Catches opens, shorts, incorrect values, missing parts, and some orientation problems.
  • Can provide fast fault isolation compared with a broad functional failure.
  • Depends heavily on probe access, net coverage, fixture design, and DFT planning.
F

Functional test: proving the product works

Functional test checks whether the assembly behaves as intended. It may include power-up, firmware, communication, load, sensor, interface, calibration, and end-of-line checks.

  • Catches behavior-level problems that visual inspection cannot prove.
  • Validates firmware loading, I/O, communications, sensors, and expected outputs.
  • Works best when pass/fail criteria and test steps are defined before production.
Practical Sequence

A common way to think about order

The exact order depends on the board and the test plan, but many assemblies move through a layered sequence like this.

Inspect the build

Use AOI and visual review to confirm placement, polarity, and visible solder conditions after assembly.

Check what is hidden

Use X-ray where the solder joint or termination cannot be verified optically.

Verify the circuit

Use ICT or flying-probe style checks when net-level or component-level coverage is needed.

Prove behavior

Use functional test to confirm the assembly performs the job the product requires.

Customer Planning

What to share when planning inspection and test

The earlier an EMS partner understands your test intent, the easier it is to recommend practical coverage and avoid late surprises.

For AOI and X-ray

  • Assembly drawings and polarity/orientation notes.
  • Critical components, BGAs, QFNs, fine-pitch ICs, and bottom-terminated parts.
  • Customer-specific inspection criteria, image retention needs, and reporting expectations.

For ICT or flying-probe

  • Gerbers/ODB++, netlist, BOM, and test-point information.
  • Known critical nets, programming headers, boundary-scan requirements, and access constraints.
  • Expected test coverage, pass/fail criteria, and whether a fixture is justified by volume.

For functional test

  • Power requirements, safe startup sequence, and current limits.
  • Firmware files, programming instructions, communications interfaces, and expected outputs.
  • Calibration steps, fixtures, scripts, golden units, logs, and acceptance limits.

For documentation

  • Required records, lot-level traceability, serial numbers, labels, and traveler requirements.
  • Whether the build needs AOI/X-ray images, test reports, programming logs, or certificates.
  • Revision level for the BOM, PCB files, firmware, test procedure, and customer drawings.
External Reference

Standards help define what “good” means

Inspection and test only work when expectations are clear. IPC standards are a useful external reference for electronics manufacturing quality, reliability, and consistency expectations. For an OEM, the practical takeaway is to define workmanship class, inspection needs, test requirements, and acceptance criteria early.

Related Micron Capabilities

Inspection and test planning connects directly to assembly, NPI, programming, documentation, and repeat-build readiness.

The right question is not “Was it tested?” It is “What risks did the test strategy cover?”

AOI helps confirm visible assembly quality. X-ray helps verify hidden solder conditions. ICT helps isolate circuit-level manufacturing faults. Functional test helps prove the assembly behaves as intended.

For many products, the best answer is a practical combination. Micron can help review the design data, test intent, critical components, quantities, and documentation needs to recommend a coverage plan that fits the build.

  • Share BOM, Gerbers/ODB++, pick-and-place data, assembly drawings, and test intent.
  • Identify critical components, firmware needs, serialization, calibration, and reporting requirements.
  • Clarify whether the build is a prototype, pilot run, or repeat production program.

Suggested slug: aoi-xray-ict-functional-test-what-each-catches
Meta title: AOI, X-ray, ICT, and Functional Test: What Each One Actually Catches | Micron Corp
Meta description: Understand what AOI, X-ray inspection, in-circuit test, and functional test each catch in PCB assembly—and why a strong EMS test strategy often uses more than one method.

EMAIL OR CALL US
(781) 949-3500