Key pointThe final deliverable is not merely a collection of charts, but a peer-reviewable investigation report: what was investigated, what is the evidentiary basis, and how to verify next steps.
Candidate Mechanism
A Source or Mechanism That Still Requires Verification
Localization Tier
The Step, Tool, Chamber, or Component Level Currently Supported by Evidence
Contradictory Evidence
An Observation That Weakens an Explanation
Verification Objective
Specific questions to be resolved following physical checks

Define the Problem and Investigation Boundaries First

Assume post-etch inspection finds increased edge detections in a wafer lot. Initially, only a change in inspection results is established, not equipment failure. Engineers need to assess whether the anomaly is valid, its affected scope, and the interval to which its source can be narrowed.

Process IllustrationAn Illustrative Investigation of an Edge Anomaly
  1. 01
    DetectionElevated Defect Detections Along Wafer Outer Perimeters

    Confirm inspection recipes and edge care areas did not introduce non-comparability.

  2. 02
    ComparisonContrast Against Reference Lots and Pre-Etch Baselines

    Distinguish newly detected adders from pre-existing patterns and visibility shifts.

  3. 03
    DiagnosisExamine Candidate Equipment Along Actual Processing Histories

    Cross-check products, recipes, chambers, processing timestamps, and maintenance logs.

  4. 04
    ReportingDeliver Evidence-Backed Inspection and Tuning Plans

    Provide concrete recommendations when evidence is sufficient; deliver verification plans when gaps remain.

Pedagogical walkthrough scenario, not an actual client incident; schematic does not preset specific component root causes or yield gains.

Six Diagnostic Checks Transforming Observations into Recommendations

  • 1. Verify Inputs:Wafer IDs, spatial coordinates, inspection care area coverage, recipe versions, and missing channels.
  • 2. Confirm Anomaly:Compare against verified reference baselines, checking metrology sensitivity and effective inspected area.
  • 3. Pre/Post Step Comparison:Find new detections or morphology changes, retaining the possibility that upstream defects have become visible.
  • 4. Screen Tool Histories:Compare tool and chamber histories between excursion and normal lots, controlling for product, recipe, and time confounders.
  • 5. Physical Mechanism Check:Synthesize inline metrology, sensor traces, and SEM reviews to evaluate supporting and contradictory evidence.
  • 6. Formulate Recommendations:State target tools, verification goals, comparative conditions, expected outcomes, and unresolved gaps.

These are not rigid mechanical steps. Existing standard checks are reused; investigations may pause for supplementary data or conclude early. New analysis plans require verified tools and authorization.

Advanced: Why Statistical Differences and Micrographs Still Demand Verification

Statistical differences between chambers support further checks of equipment or related conditions. SEM/EDS can provide morphology and material information, and waveforms may indicate a phase change. Calibration, material, maintenance, and scheduling remain alternative explanations. Controlled checks or verification results are needed to further distinguish mechanisms. A p-value describes results under a specified statistical hypothesis, not the probability that a root cause is true.

A Complete Engineering Report Must Deliver Actionable Insights

Report SectionHow Engineers Use It
Executive SummaryReview verified phenomena, localization tiers, and unresolved gaps
Analytical WorkflowAudit evaluated entities, reference baselines, methods, parameters, and outputs
Candidate Causes & EvidenceExamine supporting, contradicting, and alternative hypotheses
Inspection / Tuning ActionsDetermine inspection priorities and when split experiments or models are required
Verification PlanDefine how new empirical data will evaluate effectiveness and update conclusions

Specific parameter tuning setpoints require validated response models and verified operating windows. Tool holds, component swaps, lot splits, and product releases must follow fab operational protocols, not illustrative examples.

WAFERPILOT / APPLICATION TO THIS TOPIC

Delivering Reports, Recommendations, and Traceable Workflows

WaferPilot's end-to-end mission is to organize visual and operational data, advancing authorized analyses to produce reports and verification plans for PE/PIE/EE review. The current interactive demo focuses on ImageLens inspection and attributed findings; live on-site diagnostics and closed-loop actions are evaluated separately.

Deliverables for Engineers:A conclusion summary, the full analytical process, candidate causes and evidence, inspection or adjustment recommendations, and a verification plan for evaluating new results.

View the Current Demo and Capability Scope →

Related Reading & References

Below are verifiable industry references; specific processes, permissions, and acceptance criteria are governed by fab site specifications.

Continue Reading: Staying Inside Customer Environment: Why Deploy Agents On-Prem in the Fab?Return to Product and User Guides