Reading Whether a Fault Is Getting Worse or Holding Steady

Why this matters

A reading that is out of spec tells you there is a problem. It does not tell you whether that problem is racing toward failure or has been sitting stable for years. Those are different jobs, different quotes, and different risks. Call a stable condition urgent and you oversell a repair the customer did not need. Call a fast-degrading one steady and you leave, and it fails next week with your name on the last visit. Reading trajectory, the direction and speed a fault is moving, is a separate skill from reading the fault itself, and most techs never learn it because it does not fit in a single visit.

Three trajectories, three meanings

Any off-normal condition is on one of three paths, and the path matters more than the current value:

• Progressive. The measurement is moving steadily toward a limit. Left alone it will reach failure, and the only question is when. This is the one that must not be missed.
• Steady-state. The condition is off-normal but stable, holding the same wrong value visit after visit. It may be a design compromise, an old repair that settled, or wear that plateaued. It needs a decision, not an alarm.
• Cyclic or condition-driven. The measurement swings with a driver: load, weather, time of day, duty. It looks like it is worsening if you catch it on the way up and improving if you catch it on the way down. Reading a single point on a cycle as a trend is the most common trajectory mistake there is.

You cannot read a trajectory from one point

A trajectory is a rate of change, and a rate needs at least two measurements separated in time. One visit gives you a value, not a direction. This is why trajectory reading lives in your records, not your meter. To read the slope you need:

• Two or more timestamped readings of the same measurement, taken the same way at the same points.
• The conditions each was taken under, because a reading at full load and one at idle are not comparable and their difference is not degradation.

If you have no prior reading, you cannot claim a trend. You can note the current value, capture it cleanly as the baseline, and say honestly that the direction is unknown until a second look. Manufacturing a trend from a single point, or from a reading you took differently last time, is worse than admitting you do not have one.

Separate real worsening from a moving condition

Before you call something progressive, rule out that you are just watching it ride a driver up and down. Normalize the comparison:

• Match the load and conditions between readings, or measure the same fixed reference point, so you are comparing like to like.
• Watch the swing versus the baseline. A value that oscillates around a stable center is cyclic. A center that itself keeps moving in one direction across cycles is progressive. The trend is in the center, not the peaks.
• Look for physical evidence of accumulation. Progressive faults leave a record: growing heat discoloration, spreading corrosion or staining, increasing play, deposit build-up. Steady conditions do not keep adding damage. A worsening measurement backed by growing physical evidence is a real trend; a swinging measurement with no new damage is a cycle.

Read the slope against the margin left

Speed only matters relative to how much room is left. A measurement creeping slowly but already close to its limit is more urgent than one moving fast with a long way to go. Put the two together: how fast is it moving, and how much margin remains before it reaches the point where the system is harmed or trips. That ratio, not the raw rate, is the real read, and it is what turns "it is drifting" into "it has roughly this long."

The caveat that keeps this honest: degradation rarely stays linear near the end. Many failures accelerate as they approach the limit, because damage feeds on itself, so a slope measured in the middle of the range tends to underestimate how little time is left at the edge. Treat a projection as a floor on urgency, not a promise of time.

What each trajectory tells you to do

• Progressive: act on it now or set a defined recheck window sized to the slope, and tell the customer plainly which way it is headed.
• Steady-state: decide deliberately. Document the value, and choose repair now or accept-and-monitor as a business and risk call, not an emergency.
• Cyclic: stop treating it as a trend. Find the driver, capture the range across the cycle, and judge whether the extremes cross a limit, not whether one snapshot looked bad.

References

• Trade-standard practice for condition monitoring and trend analysis
• Manufacturer service limits and acceptable-range specifications
• See related: In-Spec but Trending Bad, Act Now vs Monitor (decision tree); The Pattern That Only Shows Across Multiple Visits