Yield Engineering
Long-cycle design programs where IP, foundry, and ecosystem partnerships execute against tapeout and market windows.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, timeline, and what ‘good’ looks like for each stakeholder.
Alignment Questions
Quick Check — Where we start together
- In one short paragraph, describe the specific yield gap, defect event, or KPI that prompted this conversation now.
- Which process node and product line are we focusing on for this evaluation?
- How long has this gap or unexpected yield drop been visible in your metrics?
- Roughly how many wafers per week or month would be involved in a side-by-side qualification?
- Who on your team should we credit as the primary point-of-contact for technical and logistical details during discovery?
Why is this keeping you up at night?
- If this defect trend or ramp delay continues for two more quarters, what are the top business consequences we should know about?
- Can you estimate the revenue, margin, or customer-impact tied to the current yield shortfall?
- Who internally is most pressured to resolve this, and what does success look like to them personally (short answer)?
- How would you describe the emotional tone: urgent firefight, measured concern, exploratory, or comfortable to wait?
- Have you experienced a near-miss or customer escalation tied to these defects in the last 12 months? If yes, tell us what happened.
What are you assuming that might be wrong?
- Which capabilities do you believe your current inspection and analytics stack cannot deliver?
- What evidence supports those assumptions (logs, missed defects, past experiments)? Please point to any recent examples.
- How long do you expect it will take your team to identify a new defect mode today and push a classifier to stable accuracy?
- If you had to rank the weakest link in your current defect-detection workflow, which is it?
- Is there anything your team believes an external partner could never do better than the incumbent tools or in-house work? Explain briefly.
If we could deliver a measurable win, what would it feel like?
- What is the minimum yield uplift (absolute) that would make this project 'worth it' for you?
- Beyond percent yield, which outcome matters most: fewer escapes to downstream test, lower scrap, faster ramp, or improved cycle time?
- How important is classifier accuracy on novel defect types vs. speed-to-classify when deciding success?
- Who on the customer side will need to say 'this is a success'—and what exact metric would make them say it?
- Tell us about a past win where an analytics or inspection change made a clear business difference. What indicators did you watch?
How will you validate — the bar for saying yes
- What are the non-negotiable acceptance criteria for a side-by-side qualification (examples: classification ≥ X, capture recall ≥ Y, false positive rate ≤ Z)?
- Statistically, what minimum sample size or wafer count will you require to be confident in the comparison?
- How long must a pilot run to satisfy your engineering and quality gates?
- Which metrics will you want in the dashboard during the pilot (select all that apply)?
- What reporting cadence and format do you prefer for pilot checkpoints (daily standup, weekly scorecard, executive review)?
Who needs to be in the room when we make the call?
- Which stakeholders must approve the pilot and final purchase (select all that apply)?
- What is the approval timeline you are operating under for a pilot decision and for capital procurement if the pilot succeeds?
- Who owns the budget for pilot-related expenses (equipment time, sample wafers, engineer hours)?
- When technical issues arise during a pilot, who will be the primary escalation contact on your side?
- How will success be socialized internally—what audience needs to be convinced beyond the immediate project sponsors?
What could stop this from moving forward?
- Which of these potential barriers do you consider most likely to derail a pilot?
- Have you run a similar pilot before that failed to scale? If so, what was the primary reason?
- What mitigation would convince you we can manage the top-3 risks you selected?
- How tolerant is your team of exploratory false positives during early tuning—are we allowed to generate noisy results to accelerate learning, or must accuracy be near-production from day one?
- If a cost overrun or schedule slip happens, what contractual guardrails would you expect to see (caps, milestones, rollback options)?
Small first step — what would make you comfortable to start?
- Do you have representative sample wafers, labeled defect examples, or historical inspection datasets ready to share for initial testing?
- Which data feeds are required and available for correlation during the pilot (select all that apply)?
- What access constraints or data treatment (anonymization, IP controls) must we honor to proceed?
- What does an acceptable pilot kickoff timeline look like for you?
- If we agreed on a minimal pilot plan now, what would be the single best next step you’d expect from us this week?
-
Current State Mapping
Document the current inspection fleet, yield trends, known defect modes, and available data feeds for correlation.
Current State
Quick Reality Check: What Brought Us Together Today?
- In one short sentence, what's the single most urgent yield problem you're hoping to solve with external help?
- Which wafer generation or process node is this issue affecting right now?
- How long have you been tracking this problem?
- Who on your team will own evaluating an inspection + analytics qualification (title or role)?
- What outcome would make this conversation feel like time well spent to you personally?
Are You Quietly Burning Margin?
- If your current yield trend continued unchanged for the next two quarters, how would it impact wafer cost or competitive pricing?
- Quantitatively, what is the approximate yield gap versus target (percent or ppm defect difference)?
- How often do yield shortfalls translate into lost business or missed shipment commitments?
- Tell me about a recent situation where yield underperformance created executive pressure—what happened and who was involved?
- Which metric matters most to your leadership right now?
What’s Invisible to Your Current Tools?
- What defect types or process excursions do you suspect are slipping past your inspection fleet today?
- Which inspection systems are in active use on the affected line(s)?
- How would you rate your current fleet on sensitivity to new or rare defect modes?
- Give a recent concrete example of a defect mode you only discovered late—what signs were missed earlier?
- How frequently do false positives from inspection tools create wasted engineering investigations?
When Did Your Last Surprise Happen—and Why Did It Hurt?
- Describe the most recent unexplained yield drop or excursion that cost you meaningful throughput—when was it and how big was the impact?
- How long did it take your team to form a root-cause hypothesis for that event?
- Which data streams did you consult during that investigation?
- Was a definitive root cause established? If yes, what was it; if no, what evidence was missing?
- How did that episode change how leadership views inspection and analytics spend?
If Fixing This Was Fast, What Would Change for Your Team?
- What's a realistic, measurable uplift you would be satisfied with from a successful qualification (e.g., percent yield, defect reduction, classification accuracy)?
- Which success criteria will you insist on during a side-by-side qualification?
- How soon would you need to see positive qualification signals before recommending capital purchase?
- What internal KPIs would this improvement positively affect (list concrete metrics and owners)?
- If we demonstrated the expected uplift, what downstream organizational changes would you expect (e.g., faster ramps, pricing leverage, headcount shifts)?
Who Really Decides and What Feels Good Enough?
- Who are the formal decision-makers and informal influencers for buying inspection and analytics (names, roles, and their primary success metric)?
- Which stakeholder is most risk-averse about new inspection tech, and what are they most worried about?
- For each stakeholder, what would 'good' look like at pilot completion (be specific by role)?
- Is there an executive or board-level timeline driving this decision (e.g., pricing deadlines, customer commitments)?
- Who needs to be in the room for a pilot sign-off conversation?
How Ready Is Your Data to Tell the Story?
- Which data feeds are available and routinely captured for the affected wafers?
- How accessible are those feeds for a partner to ingest (APIs, SFTP, direct DB, manual export)?
- What historical window of data can you provide for correlation work (days/weeks/lot counts)?
- Are there known gaps or quality issues in any of these feeds we should plan around (timestamps, missing fields, image compression)?
- Who owns the data access and who will be our day-to-day contact for integrations?
What Would Make You Pull the Trigger Quickly?
- What are the minimum commercial or risk guarantees you need to greenlight a pilot (po clauses, capital holdbacks, trial periods)?
- How long of a pilot do you consider sufficient to validate defect capture and classification?
- Which integrations are must-haves for the pilot to be meaningful (select all that apply)?
- What classification accuracy and defect capture targets would be considered a clear pass?
- What maximum recipe development time or production downtime would you tolerate for pilot activation?
Comfort and Control During a Pilot: What Do You Need?
- What rollback controls or safety gates must be in place before any pilot work touches production wafers?
- What sample wafer types and quantities can you commit for side-by-side runs?
- Who will dedicate time to recipe tuning, image review, and weekly qualification syncs?
- What acceptance test method do you prefer to verify classification (blind review, SEM confirmation, electrical correlate)?
- How frequently do you want progress updates during the pilot and in what form (dashboards, executive briefs, daily standups)?
Next Steps — A Low-Risk Path to Insight
- Based on this conversation, what would you consider a low-effort next step that helps us prove value quickly?
- Who else on your side should we include in a scoping session to avoid rework later?
- When would be the earliest practical date to start a light-touch proof step (data ingest or demo)?
- What would make you say yes to that first step—what guarantees, evidence, or reassurance do you need?
- Any final concerns or constraints we haven't touched on that would block moving forward?
-
-
Customer Discovery
Clarify target yield gains, constraints, success signals, and acceptance criteria for a side-by-side qualification.
Discovery Questions
Starting Together: Who's On This Mission?
- Who should we know on your team for this project—names, roles, and decision authority?
- Which functional owners will be directly involved (select all that apply)?
- What timeline are you under to show measurable yield improvement before leadership escalates?
- Which single KPI will make leadership relax the most if it moves in the right direction?
- In one sentence, why fixing this inspection/defect problem matters for your line today?
Are You Settling for 'Good Enough'?
- What have you been tolerating in your inspection data that, if fixed, would change how you feel about the line?
- How long has this tolerance been the norm for this node or line?
- Which defect families do you believe are currently escaping the most often?
- Tell us about a specific incident where missed defects caused rework, scrap, or missed revenue—what happened and what was the impact?
- When an unexplained yield drop occurs, how does the team typically react and what emotions surface?
What's Really Costing You?
- If nothing changes, how many wafer lots or estimated dollars could this defect trend cost over the next 12 months?
- Which process steps see the most downstream impact from these defects?
- What internal resources are currently consumed by manual defect triage and RCA (select all that apply)?
- Roughly, what is the expected revenue improvement per 1% yield gain on the affected line?
- How frequently do you pause production or divert lots for investigation because inspection can't explain the issue?
What Would Winning Look Like?
- Name the top three signals you would need to see to call a qualification a clear success.
- What minimum percentage improvement in defect detection or reduction in escapes would you consider a meaningful win?
- For automated classification, what accuracy and confidence thresholds are non-negotiable for you to rely on the results?
- Beyond analytics, which operational criteria must be met (select all that apply)?
- If the pilot hits those outcomes, what would be the expected timeline for procurement and full deployment?
Obstacles You're Underestimating
- Which hidden risk keeps you up at night when considering swapping or augmenting inspection tools?
- How much calendar time do you have available for recipe tuning before production consequences appear?
- What internal governance steps or committees could block or delay the pilot or tool purchase?
- Have you tried replacing or augmenting inspection before? If yes, what specifically caused that attempt to fail or stall?
- What evidence would make your engineers trust a new AI classifier on day one?
How We’d Prove This Side-by-Side
- What would make you stop the side-by-side early and confidently declare success or failure?
- Which acceptance metrics should be measured in the side-by-side (pick all that must be included)?
- Which sample types absolutely must be included for a representative qualification?
- What duration and wafer count would give you statistical confidence in the side-by-side results?
- Who on your side will own day-to-day execution of the side-by-side and who must approve using production wafers?
Practical Next Steps & Decision Signals
- If we delivered a pilot plan that guaranteed X: capture parity, Y: 95% classification on target defects, Z: integration to metrology within the pilot, what would be the single biggest remaining blocker to your sign-off?
- Which commercial or capital constraints will drive the final go/no-go (select all that apply)?
- What deliverables and documentation must we hand over at pilot close for you to accept results?
- Who should attend the final alignment meeting and by what date must that meeting occur to stay on your timeline?
- How should we communicate progress and raise blockers during the pilot? Choose preferred cadence and channels.
- How urgent is a decision on this pilot from your perspective?
-
Solution Experience
Walk through a qualification scenario using the customer’s wafers to validate defect capture, classification, and root-cause correlation workflows.
Experience Meetings
- Experience Readiness & Alignment
- Baseline Data Review & Hypothesis Mapping
- Live Qualification Run — Capture & Classification
- Classification Validation & Root-Cause Correlation Workshop
- Decision & Next Steps — Qualification Outcome
- Agree on a concrete remediation and revalidation plan for any gaps identified.
- Customer to provide labeled examples for priority defect classes and corresponding metrology/e-test slices.
- Seller to produce a test-plan mapping each hypothesis to measurable metrics and expected pass thresholds.
- Both parties to finalize the exact lot and wafer list for the side-by-side comparison.
- Pre-run Checklist & Roles
- Produce a first-pass dataset showing defect capture and classifier outputs tied to lot IDs.
- Demonstrate that the system detects the prioritized defect classes at or above the agreed sensitivity threshold or document gaps.
- Collect representative FP/FN examples and retraining seeds for the Validation Workshop.
- Seller to archive the run dataset, logs, and representative defect image sets and share with customer analytics team.
- Customer to flag any protected or sensitive images/data and confirm redaction requirements.
- Both parties to schedule the Classification Validation Workshop with delivered artifacts.
- Aggregate Metrics Presentation
- Verify whether classifier meets the agreed per-class accuracy targets (e.g., 95% for prioritized classes) or document shortfalls.
- Confirm that the correlation workflow produces actionable root-cause hypotheses within the required timeframe.
- Introductions & Objectives
- Seller to deliver a Validation Report with metrics, confusion matrices, sample images, and correlation case studies.
- Customer to provide feedback/approval on whether each correlation hypothesis is actionable.
- Both parties to schedule and scope any required re-run(s) and dataset augmentations for retraining.
- Executive Summary of Results
- Obtain a clear go/conditional-go/no-go decision and record the decision criteria.
- Agree pilot scope, timeline, owners, and measurable success gates for the next stage.
- Assign immediate next actions to move to Solution Scope and Deployment readiness if proceeding.
- Produce a Decision Memo summarizing results, ROI, recommended path, and required conditions for a conditional go.
- If go: initiate pilot contracting, schedule Pre-Deployment Readiness activities, and assign deployment owners.
- If remediation needed: schedule remediation runs, dataset labeling commitments, and revalidation timeline.
- Capture a single-sentence Current State that all parties can repeat.
- Agree and document the quantified business consequence of the current state.
- Define measurable Future State and explicit acceptance criteria (e.g., capture %, classification % per class, correlation latency).
- Confirm physical and data logistics (wafers, recipes, data feeds, owners) necessary to run the qualification.
- Customer to deliver a one-sentence Current State, yield maps, representative lot IDs, and baseline inspection data.
- Seller to prepare an Experience Plan mapping acceptance criteria to specific measurement points and reserve instruments.
- Customer and Seller to provision required data feeds and grant access to test environment and owners.
- Document and circulate rollback controls and risk mitigation steps for running production wafers.
- Baseline Fleet Performance
- Agree baseline metrics to compare during the experience (capture rate baseline, classification baseline, FP/FN tolerances).
- Prioritize 3–5 defect classes and hypotheses to validate during the live run.
- Confirm which correlation data channels will be used and owners responsible for providing them.
- Current State Statement
- Consequence & ROI Recalculation
- Per-class Failure Modes
- Run Execution & Live Monitoring
- Defect Taxonomy & Examples
- Early Capture Triage
- Root-Cause Correlation Demos
- Recommendation (Go/Conditional-Go/No-Go)
- Available Correlation Data
- Consequence Quantification
- Forced Validation Checkpoints
- Define Future State & Acceptance Criteria
- On-the-fly Classification & Quick Retrain
- Hypothesis Mapping
- Pilot Scope, Timeline & Owners
- Immediate FP/FN Check & Logging
- Signoffs & Next Actions
- Define Side-by-side Scenarios
- Logistics & Sample Requirements
- Gap Remediation Plan
- Access, Owners & Risk Controls
- Wrap-up Run Findings & Short Actions
- Acceptance Recommendation & Next Runs
-
Solution Scope
Define inspection coverage, classification targets, integrations, pilot duration, and measurable acceptance criteria.
Scope Configuration
- Install and commission wafer inspection hardware
- Configure inspection recipes and imaging parameters
- Run production-wafer inspections on specified lots
- Collect SEM imagery and label defect instances
- Deploy AI defect classifier for novel defect types
- Deploy trained classifiers to production inspection fleet
- Tune inspection recipes to reduce false positives
- Integrate inspection data with metrology and electrical test
- Ingest and normalize equipment sensor logs
- Automated defect clustering and wafer-map hotspotting
- Correlate defects with sensor logs and process steps
- Generate ranked root-cause hypotheses and drilldowns
- Activate real-time defect dashboard and alerts
Scope Questions
Install and commission wafer inspection hardware
- How many inspection tools do you plan to install during the pilot?
- Where will the tools be commissioned (e.g., production line, staging lab)?
- What cleanroom class, power, network, and vacuum utilities are available at the install site?
- Are there planned production downtimes or preferred install windows we must coordinate with?
- Who are the on-site owners for facilities, IT, and equipment safety during installation?
- Do you require on-site training and handover for operators and maintenance staff?
- Are there vendor or site-specific certification / qualification steps required before commissioning?
Configure inspection recipes and imaging parameters
- Do you have existing recipes or golden recipes we should import as a baseline?
- Which layers, features, or process steps are highest priority for inspection recipe coverage?
- What target defect size sensitivity and throughput trade-off is acceptable?
- How many recipe variants or product SKUs must be supported during the pilot?
- Do you require automated recipe generation/tuning or manual recipe validation?
- Who will own final recipe sign-off (customer role/title)?
Run production-wafer inspections on specified lots
- Which lot IDs or wafer types are in scope for the qualification inspections?
- What is the expected inspection throughput and daily wafer volume during the pilot?
- Will inspected lots be held from release pending qualification results?
- What handling and contamination controls are required (e.g., FOUP protocols, special carriers)?
- Who are the process owners and operators we will coordinate with for lot moves?
- Are there specific security or access controls required for on-machine data (e.g., air-gapped, VPN)?
Collect SEM imagery and label defect instances
- Is SEM imaging available on-site for high-resolution defect capture?
- How many SEM images per defect type / per wafer do you expect to collect for classifier training?
- Who will perform image labeling (customer engineers, vendor labeling team, hybrid)?
- What metadata must accompany each SEM image (e.g., lot ID, wafer position, process step)?
- What turnaround time is required for labeled SEM datasets to be available for training?
- Are there preferred labeling taxonomies or defect class names we must adhere to?
Deploy AI defect classifier for novel defect types
- How many novel defect types do you expect to qualify during the pilot?
- How many labeled examples are available per novel defect type today?
- What target classification accuracy and confidence threshold do you require for novel defect classes?
- Do you prefer on-premise model training or cloud-based training for IP/latency reasons?
- How frequently should models be retrained or updated during the pilot?
- Do you require human-in-the-loop review for new class proposals before deployment?
Deploy trained classifiers to production inspection fleet
- How many production inspection tools will receive the trained classifiers?
- Are the inspection tools homogeneous by model/firmware or heterogeneous?
- What deployment strategy do you prefer: single-tool pilot, phased rollout, or full fleet cutover?
- Do you require automated rollback and versioning of classifiers on tools?
- What monitoring metrics must be collected post-deployment (e.g., classification drift, latency, throughput)?
- Who will own day-to-day model maintenance and approvals for updates?
Tune inspection recipes to reduce false positives
- What is the current false positive (FP) rate baseline for the inspection process?
- What FP reduction target is required to consider recipe tuning successful?
- Do you permit temporary throughput reduction during tuning iterations?
- Will you provide labeled FP examples for tuning, or do you need vendor identification tooling?
- How many tuning iterations and validation runs do you expect to approve during the pilot?
- What acceptance gate will be used to promote tuned recipes to production?
Integrate inspection data with metrology and electrical test
- Which downstream systems must be integrated for the pilot?
- What data formats and protocols are available from those systems (e.g., CSV, SECS/GEM, REST API)?
- What matching keys exist to correlate inspection data with metrology and e-test (lot ID, wafer ID, die coordinates)?
- How frequently must data be synchronized for correlation workflows (real-time, hourly, daily)?
- Are there access or compliance constraints for sharing metrology or test data (IP, export controls)?
- Who owns the integration (customer IT, fab data team, vendor services)?
Ingest and normalize equipment sensor logs
- Which equipment vendors and tool models generate the sensor logs we must ingest?
- What log formats and connectivity are available (e.g., CSV, JSON, time-series DB, SECS/GEM)?
- Is clock/time synchronization between tools and inspection data assured (NTP, other)?
- What retention and sampling frequency is required for sensor logs during the pilot?
- Are there unit or naming normalization rules we must apply (e.g., temperature units, sensor IDs)?
- Do you require secure transfer or on-prem ingestion vs. cloud forwarding for sensor logs?
Automated defect clustering and wafer-map hotspotting
- Do you want spatial, temporal, or spatio-temporal clustering for hotspots?
- What hotspot sensitivity and minimum cluster size should trigger an alert?
- Do you prefer unsupervised clustering, rule-based hotspotting, or a hybrid approach?
- What wafer-map visualizations and drill-downs are required for engineers?
- What time window should clustering consider for recurring vs one-off hotspots?
-
Mutual Commit
Agree on the qualification plan, commercial terms, capital exposure, and go/no-go decision gates.
Agreement Modules
- Statement of Work (SOW)
- Commercial Terms & Pricing
- Purchase Order / Capital Authorization
- Pilot / Qualification Plan & Go‑No‑Go Gates
- Equipment Loan / Evaluation Hardware Agreement
- Service Level & Support Agreement (SLA)
- Data Access & Processing Agreement (DPA)
- Intellectual Property & Model Usage License
- Confidentiality & Proprietary Information Addendum (NDA)
- Integration & Site Access Authorization
- Risk, Liability & Warranty Agreement
- Rollback & Contingency Plan
- Change Order & Scope Management
- Final Acceptance & Commercial Close
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm recipes, sample wafers, data access, owners, and rollback controls are in place for the pilot.
Readiness Questions
Getting Oriented — What’s the single priority we should put on the table?
- In one sentence, what is the single most important yield or production outcome you need solved in the next 3–6 months?
- Which product line(s) or node(s) does this impact most?
- How urgent is this from a business perspective?
- Who will be the primary internal owner(s) for this engagement (role, not name)?
- Roughly, what’s at stake if nothing changes (choose best fit)?
Starting Small — Walk Me Through the Most Recent Incident
- Can you briefly describe the most recent yield excursion or chronic defect trend you’d like us to help with?
- When did you first notice it and how has the trajectory changed since then?
- Which signals first alerted you (select all that applied)?
- How confident are you today that your incumbent inspection tools are capturing the defect modes causing this issue?
- Share one example (anonymized) of a defect mode or wafer map that we should see during qualification.
Are You Comfortable Leaving Yield to Chance?
- If your current inspection/classification misses a new defect mode for another two quarters, what would the operational and financial consequences be?
- How often do you discover novel defect modes that require manual triage and new classifier training?
- How long does it typically take your team to stabilize a classifier or rule-set for a new defect mode today?
- Who in your org bears the pain when classification is slow or inaccurate?
- What would it mean to you emotionally and professionally if we cut that diagnosis time from weeks to hours?
Where Hidden Defects Live — Tell Me About Your Current Signals
- Which inspection tools and vendors are in your current fleet (list top 3 by usage)?
- What metrology and test data streams can we correlate during qualification?
- How accessible are those data streams for a short-term pilot (days to weeks)?
- Describe the wafer types and process layers you’ll want us to inspect during qualification (e.g., BEOL metal, via, CMP, STI).
- On average, what defect density and distribution are we likely to see on the sample wafers you’ll provide?
What’s Getting in the Way of Faster Root Cause?
- When you try to accelerate root-cause, what single operational constraint blocks you most often?
- How many labeled defect images (approx) do you have today for the defect types you care about?
- Have past vendor pilots failed because of recipe development time, or some other integration issue? Tell us a specific story.
- If recipe tuning is a bottleneck, which resources are available internally to accelerate it?
- How comfortable would you be letting us run an initial tuning session on non-production wafers to speed pipeline readiness?
What Would Production-Grade Confidence Actually Look Like?
- Beyond headline accuracy, what specific quantitative acceptance criteria matter to you (e.g., capture rate, false positive rate, classification recall)?
- Which of these metrics do you require as a pass/fail for qualification?
- Our platform aims for 95%+ classification on novel defects — how would you validate that claim internally?
- What sample size (wafers or defects) would you need to feel statistically comfortable with results?
- Who signs off on qualification results and what governance or committee is involved?
If We Could Snap Our Fingers — What’s the Minimal Viable Win?
- If this pilot delivered a single measurable improvement, what outcome would first convince leadership we’re onto something?
- What minimum % yield improvement would justify a capital expenditure on a new inspection system for this line?
- What’s an acceptable timeline from pilot start to production acceptance in your org?
- How important is preserving existing process recipes and tool behavior during qualification (i.e., low vs high risk to production)?
- If we hit the minimal win, what would you expect us to deliver next (scale, integration, handover)?
What Would Make Procurement and Capital Say Yes?
- Which procurement model is easiest for your organization for pilot-to-production transitions?
- What internal approval gates typically slow inspection tool purchases (select all that apply)?
- When does your next capital planning window open?
- What commercial risks do you need to mitigate in a pilot to say yes (e.g., ROI guarantees, limited capital exposure, rollback plan)?
- Would a short-term capital protection (e.g., refundable deposit, success-based payment) make you more comfortable? If so, how much?
How Will This Live Inside Your Fab Day-to-Day?
- Who will own day-to-day operations of the new inspection/analytics stack if we move beyond pilot?
- Which team will be responsible for providing sample wafers, recipes, and tooling access during the pilot?
- What are your expectations for training and knowledge transfer during the pilot?
- How tolerant is your fab of false positives during the pilot—how much extra engineering triage can you absorb?
- What rollback controls must be in place before any inspection changes touch production?
Designing a Side‑by‑Side That Actually Proves It
- How do you typically run side‑by‑side qualifications today and where do they fall short?
- Which acceptance gates would be non-negotiable for you (choose top 3)?
- Do you prefer blind comparison runs, or paired runs with operators aware of which tool is which?
- What statistical confidence level would you require to accept pilot results (e.g., 95% confidence)?
- Who needs to be present for final acceptance testing and signoff?
What Would Smooth the Transition to Production?
- Which integrations are must-haves before a production handover (MES, SECS/GEM, ELN, e-test DB, other)?
- How long do you expect recipe tuning and validation to take before steady-state production behavior is achieved?
- What operational KPIs should we monitor during the first 90 days after deployment?
- What success communication cadence do you want during the pilot and handover (e.g., daily standups, weekly reviews)?
- What ongoing governance will be in place to triage edge cases after handover?
What Would Make Saying Yes Easy — Low-Risk First Steps
- Would you be open to a limited-scope pilot focused on one critical layer or tool to de-risk the program?
- What minimum commitments (time, wafers, staff) can you realistically provide for a high-quality pilot?
- Which week(s) in the next quarter are best for an initial kick-off and sample collection?
- Who should be our primary day-to-day contact and who is the executive sponsor for decisioning?
- What one concern would prevent you from moving forward right now, and what would need to change to remove it?
-
Deployment Enablement
Schedule install and integration, execute recipe tuning, and coordinate metrology and e-test data pipelines.
-
Validation Checklist
Run side-by-side qualification runs, verify defect capture and 95%+ classification targets, and document acceptance results.
Validation Questions
Quick Snapshot: The Line We're Talking About
- Which single production line or process node should we focus on for this qualification conversation?
- Who will be our primary contact for day-to-day qualification coordination, and what role do they play?
- Briefly describe the trigger that brought this to the table right now (pick the closest and add details):
- Approximately how many wafers per week flow through this line today?
- How urgent is resolving this problem from a business perspective?
If We Do Nothing, What Breaks First?
- What’s the single most consequential thing that will fail if current defect trends continue for another quarter?
- Can you quantify the recent yield impact in absolute terms (wafer starts lost, yield percentage, or estimated revenue)?
- How long has the team been tolerating this condition before escalating it to leadership?
- When defects escalate, what downstream activities get delayed or reworked most often (e.g., tape-outs, product ramps, customer shipments)?
- If you had to assign a financial urgency level to fixing this problem right now, how would you categorize it?
What’s Invisible Today That Should Make Us Nervous?
- Which defect modes or excursions do you suspect are slipping past your current inspection fleet entirely?
- Give a concrete example of a time you found a root cause late—what was missed initially and how long until it was identified?
- Where do you see the biggest gaps today: defect capture (sensitivity), classification (accuracy), or root-cause correlation with metrology/e-test?
- How often do false positives from the current inspection tools lead to wasted engineering investigations?
- Who on your team currently owns triage of new defect modes and how do they escalate something unusual?
Who Holds the Keys — and Who Actually Pulls Them?
- If you mapped every decision required to approve a new inspection tool/qualification, where do real bottlenecks or veto points exist?
- Which stakeholders must sign off on a side-by-side qualification and production acceptance?
- For each stakeholder group you've selected, what is their single most important success metric for this project (e.g., dollars saved, ramp schedule, classification accuracy)?
- Who controls the capital and what is the typical approval horizon for equipment purchases at the required scale?
- Who would be the internal champion driving day-to-day work during the pilot, and how much of their time can be allocated?
If We Could Wave a Wand — What Would Change?
- Imagine yield improved by 1% in six months: what would that unlock for product, pricing, or customer commitments?
- What specific measurable targets would make you call the qualification a success (e.g., defect capture rate lift, classification accuracy, time-to-root-cause)?
- What trade-offs are acceptable during qualification—longer pilot time vs higher confidence, or faster pilot with tighter acceptance thresholds?
- Beyond metrics, how would you describe the ideal day-to-day experience after deployment (e.g., fewer emergency meetings, automated alerts you trust)?
- Which of these would make your leadership most comfortable signing off on production acceptance?
What’s Honestly Been Holding Change Back?
- When similar initiatives have stalled in the past, what was the real reason—not the official reason—that they stopped?
- Which of the following constraints are you most worried will derail a qualification?
- How many engineering hours are you realistically able to commit from your team for recipe tuning and investigation during a pilot?
- What would be a deal-breaker for you in commercial terms or deployment risk?
- If you could remove one internal obstacle right now, what would it be?
Data, Recipes, and Experiment Readiness — Can We Run the Test?
- If we tried to start a side-by-side qualification next week, what single logistical or technical roadblock would stop us immediately?
- Do you have representative sample wafers and known-defect wafers available for a side-by-side within the next 30 days?
- What data feeds do we need to integrate for meaningful correlation (select all that apply)?
- Who will own data access and security approvals on your side, and how long does that typically take?
- How much recipe tuning lead time do you expect will be required before we can run production-like wafers on our system?
Decision Gate: What Would Make This a Clear Yes?
- What are the non-negotiable acceptance criteria you would require to approve production acceptance after qualification?
- What pilot duration would you consider sufficient to validate those criteria?
- What level of capital exposure or financial commitment is acceptable to start a pilot (e.g., loaner tool, capital purchase, subscription)?
- Which go/no-go gates should be in place during the pilot (technical, schedule, financial)? Please list the minimal gates you require.
- Who on your side will make the final go/no-go sign-off and what evidence do they insist on seeing?
Emotional Check: How This Is Landing on Your Team
- On a scale from calm to crisis, where does this issue sit for your leadership team right now?
- How confident are you that your current vendors or internal tools will detect and classify a new, novel defect mode quickly?
- What would keep you up at night if we switched inspection platforms and something unexpected appeared?
- What emotions—relief, skepticism, excitement—do you expect from the extended team if the pilot shows early success?
- Who do you trust inside or outside the company to validate the technical claims (benchmarks, classification performance)?
Small Steps That Create Momentum — Practical Next Moves
- What is one low-risk experiment you would be willing to commit to in the next 30 days to build momentum?
- Who needs to be in the room for that first experiment to be meaningful (names, roles)?
- What is the earliest practical date you could make the wafers and access available for that experiment?
- What would you need from us to make that first experiment feel low-risk (e.g., loaner hardware, data-only pilot, strict rollback plan)?
- After this conversation, what is the single most important follow-up we should do to keep momentum?
-
-
Success
Review qualification outcomes, confirm production acceptance, and maintain a shared channel for issues and continuous improvements.
Success Reviews
- Qualification Outcomes Review
- Production Acceptance Decision
- Issue Escalation & Shared Channel Setup
- Knowledge Transfer & Operational Handover
- Continuous Improvement Roadmap & Quarterly Review
Issues & Enhancements
- Deliver and store operational artifacts (SOPs, runbooks, training materials) in an agreed repository.
- Schedule the follow-up verification run and date for re-review if gaps remain.
- Recap of Qualification Verdict
- Obtain formal sign-off to proceed to production or define conditional acceptance with concrete remediations.
- Ensure operational and commercial readiness (owners, budget, schedule) is in place for the approved path.
- Document and agree rollback triggers and escalation paths to mitigate production risk.
- Capture formal approval decision in writing with signatories and any conditional acceptance items listed.
- Issue or confirm purchase order / capital authorization steps if go approved.
- Publish deployment timeline and assign project leads for each milestone.
- Purpose and Scope
- Create and activate a shared communication channel with clear roles and access.
- Agree escalation tiers and measurable SLAs for incident handling.
- Establish recurring triage and RCA cadences to drive continuous improvement.
- Provision the agreed channel, invite participants, and publish channel rules and escalation matrix.
- Assign on-call rotations and document SLAs with contact details.
- Provide required dashboard and log access to all triage participants.
- Handover Objectives & Success Criteria
- Transfer run-level and classifier management skills to the customer's operational team and obtain sign-off on competency checkpoints.
- Introductions & Meeting Objectives
- Validate that the customer's team can execute an incident RCA using provided dashboards and playbooks.
- Deliver SOPs, runbooks, and classified training datasets to the customer's document repository.
- Schedule hands-on follow-up training sessions and competency sign-off runs.
- Provide temporary vendor shadowing schedule for first two production weeks post-handover.
- Review Current Performance & Business Impact
- Agree on a prioritized continuous improvement roadmap with owners and timelines.
- Establish measurable KPIs and reporting cadence to track ongoing value delivery.
- Secure necessary resource and budget commitments for the next quarter.
- Publish the agreed 90-day and 12-month roadmap with owners and deliverables.
- Enable KPIs on dashboards and schedule automated weekly/monthly reports to stakeholders.
- Allocate required labeling and engineering hours for top-priority roadmap items.
- Confirm whether qualification results meet each acceptance criterion and secure explicit customer validation.
- Identify and prioritize remaining gaps with assigned owners and realistic closure dates.
- Ensure consequence of any remaining gaps is clearly quantified to preserve decision urgency.
- Produce a final qualification report with per-defect-mode metrics, correlations, and recommended remediation actions.
- Assign owners for each identified gap (recipe tuning, classifier retrain, additional wafer samples) and set target close dates.
- Current State (One-sentence)
- Operational Readiness Checklist
- Identify Improvement Opportunities
- Roles, Ownership, and Escalation Overview
- Current Incident Types & Response Expectations
- Prioritization Framework & Roadmap
- Qualification Data Summary
- Financial & Risk Assessment
- Operator Procedures: Inspection & Recipe Tuning (Demo with Customer Wafers)
- Shared Channel Structure & Access
- Escalation Paths & Role Definitions
- Classifier Management & Correction Workflow
- Success Metrics & Reporting Cadence
- Metrology & E-test Correlation Findings
- Acceptance Criteria Verification
- Gap Analysis vs Acceptance Criteria
- Analytics, Dashboards, and RCA Workflow
- Go/No-Go Vote and Decision Gates
- Service Level Targets (Detection→Resolution)
- Resource & Budget Commitments
- Consequence Review
- Continuous Improvement Cadence
- Training Plan, Materials & Validation Checklist
- Deployment Schedule & Capital Authorization
- Close & Action Review