First-Article or Setup Inspection¶
Startup gate — instantiates Inline vs. Offline Inspection Trade-Off
Inspects the first output after a setup or changeover to catch configuration errors before a large defective batch is produced.
First-Article or Setup Inspection puts a single, intense check at exactly one moment — the very start of a run, right after a setup, changeover, tooling swap, or new-job configuration. Its defining logic is timing, not volume: a setup error is systematic (a wrong offset, a misloaded program, a swapped material) and will replicate identically across every unit until someone notices, so catching it on the first piece prevents the entire downstream batch of clones. The mechanism inspects one item thoroughly, against the full spec, before authorizing the run to proceed. It is the cheapest possible insurance against the most expensive kind of defect — the kind you make thousands of before discovering you were making it wrong the whole time.
Example¶
A commercial print shop mounts new plates for a 40,000-sheet magazine run. Before the press is cleared to run production speed, the operator pulls the first good impression as a "first-off" sheet and checks it against the approved proof and a control strip: are the colors on target, is the registration tight, is the plate the right one, is nothing transposed or upside down? On this run the first-off reveals a cyan plate hung one station off, throwing registration — a fault that, uncaught, would have ruined all 40,000 sheets identically. The operator corrects the setup, pulls a fresh first-off, confirms it against the proof, and only then releases the run. One inspected sheet stands as the gate for the whole job. Nothing downstream is routinely inspected at this intensity; the coverage is concentrated at the start where the systematic error lives.
How it works¶
- Trigger on change, not on time. The check fires at every setup, changeover, tool change, material lot change, or program load — the moments a new systematic error can be introduced — not on a routine clock.
- Inspect the first piece against the full spec. Unlike a fast inline check on one feature, the first article is verified comprehensively, because any configuration dimension could be the one that is wrong.
- Gate the run. Production is not authorized to proceed until the first article passes; the placement is a startup gate, not a monitor.
- Spend coverage where clones originate. The coverage strategy is n≈1 at the start, justified because the error, if present, is in every unit — so one representative catch protects the batch.
Tuning parameters¶
- What counts as a trigger — how broadly "setup change" is defined (only tooling swaps vs. any material-lot or shift change). Broader triggering catches more configuration errors but adds a gate to more transitions.
- First-article depth — how many spec dimensions the first piece is checked against. Fuller checks catch subtler setup faults but delay run start.
- Sample size at start — literally one piece, or the first few, to guard against a first-piece fluke. More pieces reduce false confidence but consume startup time.
- Sign-off authority — who must approve the first article before the run proceeds. Independent sign-off cuts self-serving passes but adds a coordination step.
When it helps, and when it misleads¶
Its strength is extraordinary leverage: a single well-chosen inspection at the start prevents an entire batch of identical defects, which is why formal first-article inspection is a backbone of regulated manufacturing[n1]. It is the ideal placement when defects are dominated by setup and configuration error rather than random drift.
Its failure mode is that it protects against systematic startup error and nothing else. A process that drifts during the run — tool wear, gradual heating, a slowly loosening fixture — sails past a clean first article, because the first piece was genuinely good and the trouble arrived later. The classic misuse is treating a passed first article as blanket assurance for the whole run and skipping any in-run monitoring, so a mid-run shift escapes uncaught. The guarding discipline is to pair the startup gate with a during-run mechanism for drift, and never to let "the first one was fine" stand in for watching the process as it goes.
How it implements the components¶
inspection_placement_map— it fixes one precise placement: immediately after a setup or changeover, before the run is released.coverage_strategy_choice— its coverage strategy is the first-article check, concentrating a full-spec inspection on the run's first unit rather than spreading effort across all of them.
It does not disposition an already-built suspect population (containment_and_rework_trigger — that's containment_hold_and_sort), and it does not gate the finished units at the end of the line (defect_criticality_and_escape_cost_profile at an exit gate — that's end_of_line_batch_release_test, its nearest twin: both are gates, but the first-article gate sits at the run's start to catch setup error, whereas the end-of-line gate sits at the exit to catch anything that survived production).
Related¶
- Instantiates: Inline vs. Offline Inspection Trade-Off — it is the startup-gate placement in the inspection mix.
- Sibling mechanisms: end_of_line_batch_release_test · automated_inline_sensor_check (the during-run partner that catches drift a first article cannot) · containment_hold_and_sort
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism evaluates the first output after setup or changeover and produces a conformance or configuration-error finding before defects multiply.
Nearest alternative: Decision, Gate & Allocation — The finding can block a batch, but the inspection itself is defined by verification of the first output rather than production authorization.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Inspecting the first output after setup is a canonical manufacturing quality-control gate.
Related originating lineages:
- Organizational & Management Science — Operations and quality management materially standardized startup gates.
Review resolution: Both reviewers agree that engineering_design is primary. I retain organizational_management only as formative origin lineage(s), without treating every later application as an origin. single_lineage is appropriate because the evidence supports one principal professional lineage. Reach is specialized as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is false because the artifact is already established enough that encyclopedia-specific synthesis is not required. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] First Article Inspection is a formal, documented verification of the first production unit from a new or changed setup against every drawing requirement — codified in aerospace practice (e.g. the AS9102 reporting standard). Its logic is that a configuration error is identical across the run, so proving the first article correct protects the whole batch. ↩