Evidence before diagnosis

Turn intermittent events into a reviewable investigation record.

Capture the operating moment, compare repeated signatures, screen no-fault-found history, and draft a bounded reproduction sequence without pretending the pattern proves a cause.

Event capture

Intermittent Fault Event Report Builder

Structure the observable symptom, operating context, recovery, and missing evidence.

Pattern screen

Repeat Occurrence Pattern Analyzer

Count exact unit, phase, code, recovery, and combined signatures across 3–100 events.

History screen

NFF & Rogue Unit History Screener

Compare declared unit concentration, no-fault-found share, and recurrence after swaps.

Test preparation

Intermittent Fault Reproduction Plan Builder

Draft trigger stages, logging, repetitions, restoration, and stop criteria for qualified review.

One investigation workflow, four separate decisions.

Start with the intermittent fault investigation guide and use the data-field reference to keep event records comparable. Each tool also works independently when only one handoff is needed.

These tools organize declared observations and plans. They do not diagnose a fault, authorize stress or energized testing, establish an exposure-normalized failure rate, prove a component is defective, or release equipment to service.