Key pointAn investigation assistant reduces repetitive data querying and manual synthesis, making recommendations transparent; tool holds, maintenance actions, recipe changes, and lot dispositions remain governed by fab operational protocols.
Hold
Pause Flow According to Production Rules
PM
Preventive Maintenance
Qual
Verification That Equipment or a Process Meets Requirements
CIM
Manufacturing Information and Automation Systems

Between Alarm and Action Lies Engineering Judgment

Whether an out-of-limit metric holds a lot, disables equipment, or notifies staff depends on fab configuration and business rules; not every SPC system automatically controls MES. Investigations must confirm event scope, reference conditions, actual processing history, and inspection validity. Customers may already have automation, and improvements should be evaluated against that real baseline.

Process IllustrationAccelerating Investigations Along Existing Workflows
  1. 01
    TriggerStart with an Engineering Question

    It may concern a defect anomaly, equipment introduction, or verification after maintenance.

  2. 02
    QueryInspect Ready Images and Analyses

    First confirm the objects, inspection definitions, and comparable references.

  3. 03
    InvestigatePerform Standard Checks and Address Evidence Gaps

    Professional methods guide the next check; propose supplementary analysis when needed.

  4. 04
    DeliverEngineers Review and Arrange On-Site Actions

    Deliver a report, candidate explanations, and a verification plan, retaining unresolved matters.

Target workflow illustration; this does not mean every alarm automatically results in root-cause localization.

Three Distinct Entry Points in Day-to-Day Operations

Operational Entry PointInvestigation TaskUseful Deliverable
Inline Defect ExcursionsAssess Anomaly Patterns and Screen Possible SourcesLocalization Level, Candidate Explanations, Evidence Gaps, and the Next Check
New Tool / Chamber BaselineEvaluate Matching, Stability, and Compatibility Against a ReferenceDeviation Metrics, Comparison Conditions, and a Verification Plan
Engineering ReviewCheck Executed Actions and How Results Support ExplanationsActual Process, Valid Evidence, Unresolved Issues, and Method Improvements

Engineering reviews can support material-review and related workflows. Reports should state evidence strength and applicable scope, retaining multiple possible causes, measurement blind spots, and unfinished verification.

Define Automation Permissions by Actions Rather Than a Slogan

Investigations should initially use read-only data access with explicit tools, objects, and budgets. Saving reports is a local write; training or deploying a model is another action class; equipment control and recipe changes have separate risks and approval paths.

WaferPilot should clearly state what is currently permitted, who can take over, and which recommendations remain unexecuted. Each deployment must separately agree permissions for reading, saving, training, deployment, and equipment control.

A transparent audit log must capture every executed SQL query, image transformation, and statistical calculation.

Serving as an Investigation Co-Pilot in Engineering Workflows

Within connected task scope, WaferPilot assists observation, checking, report organization, and recommendations. Automatic event triggers, cross-system data retrieval, and on-site loops require implementation and acceptance per environment. Time savings and faster return to service are measured through pilot results.

Deliverables for Engineers:An investigation report and action recommendations stating inspection goals, required data, execution conditions, and items awaiting engineer confirmation.

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.