Skip to content
Avecas
Avecas

FAILURE ANALYSIS

Failure analysis

Isolate failure mechanisms through a staged investigation.

Discuss your requirements
Technician inspecting a printed circuit board through a microscope

Illustrative engineering photography.

THE ENGINEERING SCOPE

Built around
your requirements.

Explore the approach ↓
01

Technical starting point

Failure symptoms, sample history, conditions and test evidence.

02

Acceptance evidence

Sample traceability, reproducibility and alternative explanations.

03

Delivery package

Failure report, supporting measurements and proposed next investigations.

CLIENT GUIDE

Scope failure analysis with the right evidence.

Use these technical checkpoints to make the first project review productive.

Provide before the review

  • Failure symptoms
  • Sample history
  • Conditions and test evidence

Review during execution

  • Sample traceability
  • Reproducibility and alternative explanations

Agree for delivery

  • Failure report
  • Supporting measurements and proposed next investigations

HOW WE WORK

Clarity at each stage.

01

Reproduce the failure

The initial review establishes the baseline using failure symptoms, sample history, conditions and test evidence. Record gaps and dependencies before implementation.

02

Narrow electrical behaviour

Carry out the agreed work against the reviewed baseline. For failure analysis, keep the interfaces and configuration used by this stage visible to the receiving team.

03

Select analysis methods

Retain the intermediate artifacts and review sample traceability, reproducibility and alternative explanations. Investigate failures before using these results as an input to the next stage.

04

Correlate findings

Package failure report, supporting measurements and proposed next investigations. Review unresolved findings against the agreed acceptance criteria and assign ownership for follow-up.

PROJECT DECISIONS

Know what moves the work forward.

Use these gates to agree readiness, review evidence and responsibility at each stage.

  1. 01

    Baseline ready

    Are the starting inputs complete enough to proceed?

    Review method and evidence

    Failure symptoms, sample history, conditions and test evidence.

    Review evidence

    Record input revisions, missing material and who can resolve each dependency.

  2. 02

    Implementation reviewed

    Has the work addressed the agreed technical objective?

    Review method and evidence

    Isolate failure mechanisms through a staged investigation.

    Review evidence

    Keep the intermediate artifacts with review comments and the decisions that changed the design.

  3. 03

    Evidence checked

    Can the result be reproduced and interpreted?

    Review method and evidence

    Sample traceability, reproducibility and alternative explanations.

    Review evidence

    Capture the configuration, expected result, observed result and unresolved findings.

  4. 04

    Handoff accepted

    Can the receiving team use the delivery package?

    Review method and evidence

    Failure report, supporting measurements and proposed next investigations.

    Review evidence

    Review build or execution instructions, known limitations and ownership of follow-up actions.

INPUTS & OUTPUTS

What the work involves.

The final statement of work defines the scope and acceptance criteria.

Client inputs
Failure symptoms, sample history, conditions and test evidence.
Engineering sequence
Reproduce the failure; narrow electrical behaviour; select analysis methods; correlate findings.
Outputs to agree
Failure report, supporting measurements and proposed next investigations.

TECHNICAL DECISIONS

Planning failure analysis.

Read the technical guide

The engineering objective

Isolate failure mechanisms through a staged investigation.

The work starts from failure symptoms, sample history, conditions and test evidence. The team should identify the authoritative revision of each input and record any assumptions needed to proceed. This prevents a later result from being interpreted against a different specification or configuration.

What needs technical attention

Destructive analysis can consume the sample; the sequence and approval boundary must be agreed first.

The review centres on sample traceability, reproducibility and alternative explanations. Each finding should identify the input revision, observed behaviour and supporting evidence. Distinguish a confirmed defect from a configuration issue, an unsupported case or an open engineering question before deciding how to resolve it.

How the work is reviewed

The practical sequence is: reproduce the failure; narrow electrical behaviour; select analysis methods; correlate findings. Intermediate reviews allow the client to resolve decisions while changes are still manageable. If an input changes, identify the affected activities and repeat the checks that depend on it.

The expected package comprises failure report, supporting measurements and proposed next investigations. Acceptance criteria should specify what the receiving team needs to reproduce, inspect or integrate these artifacts. Include known limitations and outstanding actions in that package, rather than assuming that delivery of a file implies acceptance.

Link measurements to configuration and sample history

Test and manufacturing-support work relies on traceable device, board and measurement information. Keep sample identity, lot or revision, fixture version, instrument settings and environmental conditions with the results. Establish how limits are chosen and which reference measurements support them. A result without these conditions can be difficult to compare after a fixture, device or software change.

Correlation should precede optimisation. Compare repeated measurements, investigate setup sensitivity and distinguish contact or fixture failures from device behaviour. When looking at yield, segment data by the relevant conditions instead of treating an aggregate trend as a root-cause finding. Changes to test order, settling time or limits can affect the distribution and must be recorded.

Coordinate release requirements with the actual assembly, test or fabrication partner. Confirm the format and ownership of interface files, test programs and acceptance records. Design engineering support does not imply ownership of a manufacturing line, procurement responsibility or qualification authority. Destructive analysis, stress testing and sample consumption need a defined sequence and approval boundary within the project plan.

An illustrative review scenario

A device appears to fail only on one fixture. Repeat the measurement under controlled conditions, compare contacts and calibration, and use a known-good reference where available. Preserve the original failing data before changing the setup. The aim is to distinguish device failure from the measurement chain; this illustration does not establish a diagnosis for an actual sample.

Preserve the failure before changing the sample

Record the observed symptom, operating conditions, sample identity and available history before rework or destructive examination. Compare a failing unit with a known-good reference where possible, while keeping their configurations consistent. Establish whether the failure is repeatable and whether it follows the board, component, software image or external setup. Document each intervention because cleaning, heating, probing or replacing a part can change the evidence. Agree any destructive analysis separately and preserve the findings in a traceable report. A plausible explanation is a hypothesis until the observations support it; the final report should distinguish confirmed causes, contributing factors and unresolved possibilities.

BEFORE WE BEGIN

Project questions.

A clear conversation is the start of a strong engineering relationship.

What inputs are needed for failure analysis?

The starting review needs failure symptoms, sample history, conditions and test evidence. Share the current revision and known limitations so the scope reflects the actual design state.

What does the failure analysis handoff include?

The statement of work can define failure report, supporting measurements and proposed next investigations. The final package should include review results and any open actions.

Which technical risks need particular attention?

Destructive analysis can consume the sample; the sequence and approval boundary must be agreed first.

Can we start with a focused technical review?

The first work package can be a review of the available inputs and the engineering questions that must be resolved. Agree its boundaries, access requirements and expected findings before committing to a larger implementation. A review should leave an actionable list of decisions, dependencies and next steps.

How are changes and unresolved findings handled?

Tie each finding to the relevant revision and supporting evidence. A change should identify the affected interfaces, activities and checks. Confirm its effect on scope and delivery with the responsible owner. At handoff, distinguish closed findings, accepted limitations and open work so that a file transfer is not mistaken for technical acceptance.

PUT THE WORKFLOW IN CONTEXT

Explore the engineering decisions.

Practical reading to help prepare your project discussion. Studies are illustrative; they do not report client results.

Connecting DFT deliverables to manufacturing test ↗

YOUR NEXT CHAPTER STARTS HERE

What will you
build next?

Bring us your engineering challenge.
Let’s define the path from idea to implementation.

Start a conversation