Pattern screen

Repeat Occurrence Pattern Analyzer

Turn a small, structured event list into transparent counts of repeated units, phases, codes, recoveries, and exact signatures.

Comparable events

Enter 3–100 rows. Use the same naming rules and time basis for every event.

What the screen counts

Each event contributes once to its unit, phase, code, and recovery counts. An exact repeated signature requires the same phase, code, and recovery text after trimming. The leading-signature share is its count divided by all entered events.

What it cannot establish

Raw occurrence counts do not measure operating exposure. A startup signature may lead because the fleet performs more starts, and spelling differences may split one real category. Normalize with eligible operating hours, starts, cycles, environmental exposure, or another defensible denominator before comparing rates.

Next review

Return to original logs, configuration, serial history, and the event reports. Treat a cluster as a question for controlled investigation—not proof of mechanism or component guilt.