12.2 Rate-of-Change and Multi-Inspection Trending

Key Takeaways

  • Rate of change of ΔT (or same-point temperature under comparable conditions) is often more predictive than a single snapshot severity band alone
  • Normalize or qualify trends for load and ambient whenever possible; raw temperature plots without condition context produce false trends
  • Multi-year route plots should use consistent ROI, geometry, and metadata so each point is comparable
  • Condition mismatch (different load, ε, path, solar, process state) is a leading cause of false upward or downward trends
  • Level II interprets trend slope, step changes, and scatter—not just the latest number—before escalating or clearing findings
Last updated: August 2026

A single survey answers a static question. Rate-of-change analysis answers a dynamic one: Is the asset stable, slowly degrading, or racing toward failure? Level II programs treat multi-inspection trending as a core analytical product—especially for assets that sit for years in mild Priority 4 bands while quietly worsening, or for unique equipment without peers.

Why ΔT Over Time Can Beat a Single Snapshot

InsightExample
Early faults growLug ΔT_peer: 3 °C → 6 °C → 11 °C over three annual surveys at similar load
Snapshot band lags riskStill “Priority 4” at 9 °C, but tripling in two years warrants earlier action
Post-event stepsBearing housing jumps +15 °C after a lubrication miss, then stays high
Process cycles hide in one visitSeasonal load changes look like “faults” without a multi-point view

Exam theme: The slope and acceleration of thermal abnormality matter. Standards-style priority bands remain mandatory for snapshot classification, but Level II adds trend intelligence when history exists.

Define quantities clearly:

  • ΔT_peer(t) = T_suspect(t) − T_similar(t) at survey t (NETA-style)
  • ΔT_base(t) = T_ROI(t) − T_ROI(baseline) under comparable conditions
  • ΔT_amb(t) = T_ROI(t) − T_ambient(t) (context; not a full substitute for peer/baseline when those exist)

Rate of change might be expressed as °C per month, per year, or per 1,000 operating hours—whatever matches the inspection interval and runtime data available.

Normalization: Making Points Comparable

Raw temperature is a function of fault resistance/friction, load/process, ambient/cooling, and measurement error. Plotting raw °C without context is how false trends are born.

FactorEffect on temperatureLevel II practice
Electrical load (I)Connection heating ~ I²RRecord amps/%; prefer surveys at similar % rated; note if not
Mechanical load / RPM / process rateBearing and drive heat rise with workSame production state when possible
Ambient / cooling airShifts absolute surface TRecord ambient; consider rise above ambient or peer ΔT
Wind / enclosure ventilationChanges convectionOutdoor and enclosure notes
Emissivity / RAT / window τApparent T biasLock methods; document changes
Geometry / focus / distanceSpot-size errorsStandardize stand-off and ROI

Practical normalization approaches

ApproachWhen usefulCaveat
Survey only at similar load bands (e.g., 50–70% rated)Best simple controlPlant may not cooperate every visit
Peer ΔT (same survey)Cancels much common-mode ambient/load on three-phase gearFails if all phases degrade together or loads differ
Temperature rise vs ambientUnique assetsStill load-sensitive
Engineering load correction (estimate full-load T from partial load)Advanced programsDocument assumptions; do not fake precision
Qualifying notes (“↑ load this visit”)Always availableNot a full numeric normalize but prevents false alarm

Rule: If you cannot normalize, you must qualify. A report that says “ΔT rose 8 °C but load rose from 30% to 90%” is honest; a chart that screams “failure” without load is not.

Multi-Year Route Plotting

Predictive routes (switchgear rooms, motor lists, steam trap walks, roof grids) generate time series per asset or per ROI.

Plot elementGood practice
X-axisDate or operating hours
Y-axisPrimary metric: ΔT_peer or ΔT_base (label which!)
Secondary seriesLoad %, ambient (on second axis or companion table)
EventsRepair, outage, process change markers
LimitsSnapshot priority thresholds as horizontal reference lines
Missing dataGaps shown; never interpolate a fake “smooth failure” without basis

Consistency beats camera megapixels. The same bolt head, same phase, same window, same ε method, year after year, is worth more than a new camera model with wandering ROIs.

Example multi-year table (teaching model)

SurveyLoad (% rated)Ambient (°C)T_PhaseB (°C)T_peer avg (°C)ΔT_peer (°C)Notes
2023-04602238353Baseline year
2024-04582342366Rising
2025-046121483711Crosses into P3 band
2025-106024493712Mid-cycle check; still climbing slowly

Interpretation: rate of change ~ +4 °C/year in peer ΔT, then a slower rise. Snapshot classification in 2025 is Priority 3, but the trend justified mid-cycle inspection before the next annual only survey.

False Trends from Condition Mismatch

MismatchFalse storyCorrection
Load much higher this year“Fault doubled”Compare % load; use peer ΔT; reschedule at matched load
Load much lower“Repair miracle” without workUnder-loaded survey hides I²R faults
ε set 0.95 then 0.60 on metalHuge fake ΔTStandardize surface preparation / tape
Different IR window or open door vs closedPath biasSame path + τ
Solar-loaded outdoor busAfternoon “hotspot”Time-of-day control; shade; peer check
Cold start vs steadyTransient riseWait for thermal equilibrium
ROI moved from lug to cable jacketDifferent objectTemplate ROIs
Different camera range/calibration statusBiasCalibration program (Chapter 7)
Process fluid temperature changeWhole machine warmerNormalize to process T or peer unit

Level II skepticism: Any large year-to-year jump without a matching work order, failure mode story, or confirmed matched conditions is suspect measurement or condition change until proven otherwise.

Reading Trend Shapes

ShapeTypical meaningResponse thinking
Flat low ΔTStable healthy or stable minor anomalyMaintain interval
Linear slow riseProgressive degradation (loosening, wear, fouling)Tighten interval; plan repair before next band jump
Accelerating riseApproaching failureEscalate priority earlier than snapshot alone (Section 12.3)
Step change upEvent (torque loss, lube failure, blocked cooling)Investigate cause now; do not wait for “next year”
Step change down after workSuccessful repairRe-baseline
High scatterUncontrolled conditions or intermittent loadFix method before trusting slope

Linking Trending to Other Severity Systems

DomainSnapshot toolTrend add-on
ElectricalNETA-style peer ΔT bandsSame-connection ΔT_base and ΔT_peer history
Rotating machineryISO 18434-style zones vs referenceBearing ROI vs baseline under same load
Steam trapsFailed vs live patternsRepeat failures on same trap ID
BuildingsPattern + envelope ΔT validitySeasonal series only under valid weather

Do not force electrical Priority numbers onto unrelated domains, but do carry the shared idea: history changes urgency.

Worked Scenarios

Scenario A — Normalized rise. ΔT_peer goes 4 → 9 → 14 °C at 55–60% load each year. Real degradation; schedule repair (P3) and consider shorter interval.

Scenario B — False rise. Absolute lug T up 18 °C versus last year, but load was 25% then and 95% now; peer ΔT unchanged at 2 °C. Not a failure trend—load mismatch.

Scenario C — False improvement. Peer ΔT falls from 16 °C to 5 °C, yet load collapsed from 80% to 15%. Do not close the work order as “healed”; re-inspect at load.

Scenario D — Multi-year route. Motor DE bearing ROI rise vs ambient climbs 2 °C/year for four years with stable production. Even if still in an “advisory” ISO-style band, plan bearing service before an exponential end-stage.

Scenario E — Step event. Gearbox surface ROI jumps +20 °C between monthly routes after oil leak. Treat as event-driven investigation, not a gentle annual slope problem.

Common Traps

TrapBetter practice
Charting absolute T only across seasons outdoorsUse peers, rise, or matched conditions
Declaring trends from two points with mismatched loadNeed comparable conditions or heavy qualification
Ignoring accelerating curvatureLate-stage risk
Changing ROI freelyKills multi-year meaning
Assuming “Priority 4 forever” if still < 10 °CRising 2 → 9 °C may still need action planning

Summary for Recall

Rate-of-change of peer or baseline ΔT often reveals risk that a single snapshot understates. Normalize or qualify for load and ambient (and lock radiometric method). Build multi-year route plots with consistent ROIs, event markers, and clear metric definitions. Condition mismatch is the chief source of false trends—Level II challenges dramatic slopes that lack matched conditions or plausible failure physics before alarming the plant.

Test Your Knowledge

Why can multi-year rate-of-change analysis be more important than a single mild snapshot ΔT?

A
B
C
D
Test Your Knowledge

Absolute temperature of a lug is 15 °C higher than last year’s survey, but load increased from 20% to 90% of rated and peer-phase ΔT is unchanged. Best Level II conclusion?

A
B
C
D
Test Your Knowledge

What is a primary purpose of standardizing ROI placement on multi-year IR routes?

A
B
C
D
Test Your Knowledge

Which situation most clearly illustrates a false trend from condition mismatch?

A
B
C
D