Publish Time: 2026-10-30 Origin: Site
A changeover is the most dangerous minute on an SMT line. The board, the stencil, the program, and often the components all change at once, and the first board of the new run is the only free chance to catch a setup error before it multiplies across the whole job. First article inspection is the discipline of checking that one board thoroughly against everything it is supposed to be — the bill of materials, the placement program, the reference image, and the customer drawing — before volume production begins. Done well, it converts a high-risk transition into a controlled, documented start instead of a gamble.
Most defects are not random; they arrive in clusters tied to a setup event. The board that starts a new job carries every assumption made during changeover, and if one of those assumptions is wrong, the line will faithfully build the mistake at full speed until someone notices.
Once a job is running, every board inherits the setup. A misloaded component, a flipped polarity, or a wrong program version is reproduced on every unit until someone notices. The first article check is the one gate that sees the setup before the copies exist, and it is the cheapest point at which any of those errors can be caught.
High-mix lines change over many times per day, which means many first boards and many chances to get it wrong. The risk is not the occasional change; it is the cumulative probability across dozens of transitions per week, each one a fresh opportunity for a mismatch between intent and reality.
A random solder defect scatters across boards; a changeover error hits the whole lot the same way. That uniformity is actually helpful — it means the first article, if checked well, reveals the entire problem instead of a sample of it, which is why a single thorough check can protect an entire production run.
A setup error found at final test costs the rework or scrap of every board built since the changeover, plus the time to trace which boards are affected. The same error caught at first article costs one board and a few minutes. The economics alone justify the gate, before any quality argument is made.
It is not a replacement for inline inspection, and it is not a one-time purchase order check. It is a per-job verification of the built board against the intent, performed at the machine before the run is released. The distinction matters when you decide how to match inspection methods to each defect risk, because each method owns a different failure mode.
The hardest part of first article inspection is rarely technical; it is cultural. Under schedule pressure, the gate is the first thing people want to skip, because its benefit is invisible until something goes wrong. The lines that do it consistently are the ones that made it the default path rather than an extra step, and that tied non-compliance to a visible block rather than a quiet omission.
A useful exercise is to count changeovers per week and estimate the rework cost of one missed setup error, then multiply. The resulting figure is the budget for the gate, and it usually dwarfs the cost of an FAI machine or a disciplined checklist. Framed this way, first article inspection stops being a quality luxury and becomes plain risk management.
A useful first article check compares the physical board to several independent sources of truth and confirms they agree. Skipping any one of them leaves a class of error undetected, and the check is only as strong as its weakest comparison.
Every component on the board should match the BOM by part number, value, package, and quantity. The check catches a wrong reel loaded at a feeder, which is one of the most expensive errors a changeover can introduce and one that passes a casual visual without difficulty.
Polarized parts — diodes, electrolytic capacitors, IC pin 1 — must be oriented correctly. A reversed part passes a visual glance far too often and fails only at functional test or, worse, in the field. Polarity is a first-article must, not a nice-to-have, and it is exactly the kind of error a tired operator misses.
Where the value matters, the marked value on the part should match the BOM and the placement program. This is especially important for passive values that look identical in package but differ by an order of magnitude, where a single digit on the reel label is the only difference between right and wrong.
The board should match the approved reference image and the active placement program, confirming the job loaded is the job intended. A wrong program version produces a board that looks fine in isolation but is wrong for this product, and only a comparison against the intended program exposes the mismatch.
Because the first article follows printing, confirming the correct stencil and a good paste deposit on the first board closes the loop on the printing half of the setup. The plan for inspection locations usually places SPI right after the printer for exactly this reason, so the paste side of the setup is verified before it propagates.
Each comparison — BOM, program, reference, drawing — is a separate source of truth, and the power of the check is that they have to agree. If the BOM says one value and the placed part shows another, the conflict is exactly the defect, surfaced before a single good board is built. Relying on any single source, by contrast, lets a single wrong entry pass unchallenged.
A first article check that is performed but not recorded is half a check, because the next person has no evidence the board was verified. The record — what was compared, against what, and by whom — is what turns a momentary action into an auditable fact, and it is what protects the line when a question arises weeks later about whether this job was ever confirmed.
A dedicated first article inspection machine automates most of the verification above: it images the board, compares it to the reference and the BOM, and flags mismatches without relying on an operator's memory under time pressure, which is precisely when human checks fail.
The machine stores an approved reference and compares the first board component-by-component, catching missing, wrong, rotated, or shifted parts far more reliably than a manual glance during a rushed changeover, and it does so in a consistent way every time regardless of who is on shift.
A good FAI system links the placement program and the BOM to the inspection job, so the check itself confirms that the right program is running — not just that the board looks acceptable. This linkage turns the machine from a camera into a setup verifier.
The inspection only helps if it finishes before the run is released, so the station has to keep pace with realistic changeover intervals. A slow check gets skipped under schedule pressure, which defeats the purpose and gradually erodes the discipline entirely.
A machine such as the online first article inspection machine FAI1095 verifies the first board of a job against the BOM, the placement program, and the reference image before volume production begins, which is the exact gate this article describes and the kind of automation that survives a busy schedule.
The machine is most useful when it sits close to the placement output, so the first board can be checked before it travels far or gets mixed with the run. The planning of inspection locations should treat first article as a position with its own space and handling, not as an afterthought bolted onto the end of the line.
The machine should assist the operator, not replace their judgement, because the operator is the one who understands the product and can spot a discrepancy the program would accept. The best setups let the operator confirm rather than compute, and they treat a flagged mismatch as a conversation with the engineer, not an automatic stop that everyone learns to override.
The checklist is the artifact that makes the practice repeatable. A checklist that lives only in someone's head disappears the day that person is absent; a written, enforced one survives turnover, shift changes, and the inevitable "we always do it this way" forgetting.
Before touching the board, confirm the product, the revision, the program version, and the work order. Most changeover errors start with "wrong job selected," and the checklist should refuse to proceed until this is unambiguous, because everything downstream depends on it being correct.
The stencil ID, the paste type, and the printer program should be checked against the setup sheet for this product. These are the inputs the first board depends on and the easiest to confuse during a quick change, which is why they belong at the top of the list rather than at the bottom.
Walk every component against the BOM, with explicit attention to polarity and value. This step is where the costly reel and orientation errors surface, and it should never be abbreviated on a "simple" job, because simplicity is exactly where attention lapses.
Save the inspection result, the reference used, and the operator sign-off as a record tied to the work order. That record is what you show a customer and what you review if a field issue appears months later, and it is the difference between a claim and evidence.
The FAT and SAT checklist for inspection equipment is a useful sibling document: the first-article checklist belongs inside the production workflow, while acceptance criteria govern the equipment that performs it. The acceptance references most factories work to, such as those published by IPC, give the first article a shared definition of "correct" that survives a customer audit.
The risk with any checklist is that it becomes a signature rather than a check. Guard against this by sampling verified first articles and re-inspecting them independently, so the record reflects reality. A checklist nobody audits quietly degrades into the box everyone ticks, which is worse than having no checklist because it hides the gap.
First article inspection and inline inspection are complementary, not competing. The first article guards the setup; inline guards the run. Using one without the other leaves a gap that the other was never designed to fill.
Because setup errors hit every board identically, the first article sees the whole pattern in a single unit. It is the most efficient possible check for changeover risk, and no amount of inline sampling can recover the information that a skipped first article throws away.
Once the job is released, inline AOI and SPI catch the drift, the random defect, and the gradual wear that no first article can predict. The two layers cover different failure modes, and the combination is what makes a high-mix line trustworthy.
When inline inspection flags a new defect type mid-run, that information should flow back to tighten the next first article check for that product. The inline versus offline decision shapes how fast that feedback arrives, because inline data is available the moment the board is built.
The value decays if the first article is only checked on the very first board and never re-verified after a mid-run program tweak. Any change to the setup during the job warrants a fresh first-article confirmation, because the original check no longer describes the current state of the line.
A sensible split is that first article owns the setup-class defects — wrong part, wrong polarity, wrong program — while inline owns the process-class defects that emerge during the run, such as gradual paste degradation or random placement drift. Drawing that line explicitly prevents both layers from duplicating effort and, more importantly, prevents a defect class from falling between them.
Because the first board is the one moment where everything is checked together, it is also the best teaching moment for new operators. Walking a trainee through the first article of a familiar product shows, in one board, every class of error the line can make, and it builds the intuition that a later inline alarm will assume the operator already has.
Understanding the mistakes makes the practice feel less like bureaucracy and more like insurance. Each of these is a real, recurring failure mode on busy lines, and each one is cheap to prevent at first article and expensive to discover later.
Under changeover pressure, a similar-looking reel gets placed at the wrong slot. The first article BOM check is the control that catches it before the lot is built, and without that check the error is usually found only when the customer does incoming inspection.
A reversed polarized component often passes a rushed visual and fails only later. First article verification of orientation stops it at the source, where fixing it costs one board instead of a recall or a field return.
A board built on an older program version can be functionally wrong while looking assembled. Linking the FAI to the active program exposes the mismatch immediately, rather than letting a silent version error run for an entire shift.
The wrong stencil or paste type produces subtle but systematic solder defects. Confirming these at first article prevents a full lot of weak joints that may pass visual inspection and fail only under thermal or mechanical stress.
The most damaging errors often happen on the job judged too simple to check. The checklist must apply uniformly, because simplicity is exactly where attention lapses and where the skipped step is least expected by everyone on the line.
When the gate is skipped and a setup error runs, the true cost is not one board but every board built before discovery, plus the traceability scramble to find which ones are affected. That scramble is slower and less certain precisely because the first article record that would have bounded the problem does not exist, which is why the gate pays for itself on the failures you never see.
A single missed check is bad; a pattern of them is worse, because each skipped gate teaches the next operator that the step is optional. The discipline is therefore as much about consistency as about any individual board, and the way to protect it is to make the gate the obvious default rather than a hurdle someone must choose to climb.
The first article record is only the beginning of the learning. The changeover history, aggregated, tells you which products and which stations cause the most setup errors, and that information is what turns quality from a fire drill into a managed process.
Every first article result, with its work order and sign-off, should be stored so you can answer "what was different on the last job for this product?" The traceability here supports both quality and continuous improvement, and it is the foundation for every analysis that follows.
If a particular error type repeats across changeovers, that is a training gap, not a machine gap. The aggregated first-article records show the pattern plainly, and they tell you exactly which step of which product deserves a revised procedure.
Products that generate frequent first-article findings may benefit from standardized setups, dedicated feeders, or clearer setup sheets. The inspection data points directly at where to simplify, so the next changeover of that product is less error-prone by design.
The findings should reshape the broader inspection plan from solder paste to final test, strengthening first-article rigor on the products that need it most and relaxing it where the history shows it is never needed.
A factory that can prove every changeover was verified, and show the trend improving, is a factory customers trust with harder work. The changeover log becomes a sales asset in audits and a quiet advantage in negotiations, because it demonstrates control that competitors who "usually check" cannot document. The data that protects the line also protects the order book.
High-mix environments need the discipline most and resist it hardest, because the tempo feels too fast for a gate. The trick is to make the gate fast and automatic so it keeps up, and to make it the path of least resistance rather than an obstacle.
Automate the comparison and pre-link the BOM and program so the operator's role is to confirm, not to compute. A fast gate gets used; a slow one gets skipped, and a skipped gate is worse than none because it creates a false record of compliance.
A clear, product-specific setup sheet turns changeover from memory into procedure. The first article check then verifies the procedure was followed, rather than reinventing it each time, and it removes the ambiguity that causes most mismatches.
When operators understand that the first article protects them from building a bad lot, they defend the practice instead of rushing past it. Ownership is the difference between a checklist and a habit, and a habit is what survives a busy Friday afternoon.
Track the rate of setup-related defects found at first article and at final test. A falling trend proves the program works; a flat one means the gate is being bypassed somewhere, and the metric is how you find out before the customer does.
As product variety grows, the discipline should scale through automation and stored references, not through thicker binders. The goal is a faster, more reliable gate, not more forms, and every added page of paper is one more reason for an operator to skip the step.
A first article that was skipped should raise an alert that blocks the run record from closing, rather than being silently omitted. Making the gap visible is what prevents the slow drift from "we check first articles" to "we sometimes check first articles" to "we used to check first articles."
The discipline should be reflected in the broader inspection plan from solder paste to final test, where first article is an explicit position rather than an implied step. When the plan names it, the practice survives staffing changes and the inevitable pressure to move faster than is safe.
For a plant weighing the investment, the argument is not the price of an FAI machine but the avoided cost of one escaped setup error across a full lot, repeated across the changeovers in a year. Most high-mix lines reach payback in months once the gate is actually used, and the softer benefit — customer trust earned through documented control — is harder to quantify and longer lasting.
What exactly does first article inspection check on an SMT board? It verifies the first board of a new job against the bill of materials, the placement program, and the approved reference image, confirming correct components, polarity, values, orientation, and that the right program is running before volume production starts.
Is first article inspection a replacement for inline AOI? No. First article catches systematic setup errors that affect the whole lot, while inline AOI catches random and drifting defects during the run. They cover different failure modes and work best together as two layers rather than as alternatives.
How long should a first article inspection take? It should be fast enough to finish before the run is released — often a minute or two with an automated FAI machine. If it takes longer, the gate tends to be skipped under schedule pressure, which defeats its purpose.
Do I need a dedicated FAI machine, or can an operator do it? A careful operator can do it manually, but a dedicated machine is far more reliable under changeover tempo and removes reliance on memory. For high-mix lines with frequent changeovers, automation is usually the only way the gate survives.
Should the first article be re-checked after a mid-run change? Yes. Any change to the setup, program, stencil, or components during the job warrants a fresh first-article confirmation, because the original check no longer describes the current state of the line and the risk returns with the change.
What should be recorded from a first article inspection? Record the work order, product and revision, program version, stencil and paste used, the inspection result, the reference image applied, and the operator sign-off, all tied to a board or lot identifier for later traceability and customer review.