13.2 Equipment Identification and Finding Reclassification
Key Takeaways
- Wrong asset tags, panel names, or phase labels make a correct thermogram operationally useless or dangerous—Level II must reconcile IR, visual, and one-line identity before release
- After correcting emissivity, RAT, τ, load, or reference choice, Level II reclassifies severity using the same NETA-style bands (P4 1–10 °C, P3 >10–20 °C, P2 >20–40 °C, P1 >40 °C ) or absolute/ISO/ASHRAE rules as applicable
- Priority may be upgraded when corrected radiometry or proper load increases ΔT into a higher-urgency band, or when absolute limits are newly recognized
- Priority may be downgraded when corrections remove reflection artifacts, fix peer mismatch, or show the anomaly was load/ambient pattern rather than a defect
- Reclassification requires an audit trail: original Level I call, corrected parameters/load/ID, new Priority, and reason—never a silent overwrite
After parameters and coverage pass the first gate, Level II still asks two hard questions: Is the finding on the right asset? and Is the severity still correct after the data are fixed? Misidentified equipment sends electricians to the wrong cubicle. Unreclassified severity leaves operations with a false urgency map. This section is the technical heart of QA/QC judgment.
Equipment Identification Failures
Level I work often happens under time pressure in look-alike MCCs and outdoor yards. Common ID errors:
| Error type | Example | Risk |
|---|---|---|
| Wrong panel / cubicle | Image labeled MCC-2-A but visual shows MCC-3-A nameplate | Repair on healthy gear; real fault left live |
| Wrong elevation / bucket | Starter bucket 3 vs 5 in same vertical section | Same |
| Phase mislabel | “A-phase lug” is actually B on the one-line | Wrong torque/repair scope |
| Asset tag typo | Pump P-101A vs P-101B | Mechanical crew on wrong machine |
| Recycled filename / template text | Prior survey text left in report body | Systematic misdirection |
| Mirror / reflection confusion | Hot reflection labeled as the component | False positive on wrong object |
Level II identity reconciliation workflow
- Compare IR + visual pair (Chapter 14 paired-image discipline supports this).
- Read nameplates, engraved tags, and permanent markers in the visual.
- Cross-check one-line, MCC schedule, or CMMS ID against the report string.
- Confirm phase and circuit using wire color standards only when they match site practice—never assume.
- If identity is uncertain, do not release a quantitative finding against a guessed tag; re-photograph with a clear visual of the label or walk-down with operations.
| Evidence | Strong ID | Weak ID |
|---|---|---|
| Visual shows legible nameplate matching report | Yes | — |
| Only IR, no visual, generic “Panel 1” | — | Yes |
| GPS/outdoor structure photo + unique tag | Yes | — |
| Thumbnail of identical gray doors only | — | Yes |
Exam point: A perfect ΔT with a wrong equipment ID is still a failed deliverable. Identity QC is not optional paperwork.
When Reclassification Is Required
Reclassify severity whenever a material input to the decision changes:
| Trigger | Why Priority may change |
|---|---|
| Corrected ε or RAT | Apparent T and ΔT change |
| Corrected window τ | Far-side temperatures change |
| Corrected distance / spot size invalidation | Measurement may be non-quantitative |
| Load restated or re-surveyed | Electrical ΔT validity and magnitude |
| Reference changed (wrong peer → correct peer) | ΔT definition changes |
| Absolute / OEM limit newly applied | Absolute axis may outrank mild relative ΔT |
| Identity corrected to different equipment class | Different limits and peers |
| Trend data (Chapter 12) available | Rate-of-change may escalate |
Do not reclassify for palette, logo, or font changes. Do reclassify when the physics or asset truth changes.
Priority Map (Recall for Reclassification Math)
Experience-Based criteria, Infraspection Standard §10.1 (P1 = most severe):
| Priority | ΔT vs similar component, similar load | Action gist |
|---|---|---|
| P4 | 1–10 °C | Monitor / next inspection |
| P3 | >10–20 °C | Schedule next outage |
| P2 | >20–40 °C | Repair soon / ~24 h or before next maintenance |
| P1 | >40 °C | Immediate; consider de-energize per procedures |
Electrical standard priorities generally need ~40% of rated load minimum. If Level I assigned P3 at 15% load, Level II may withdraw the standard Priority and require re-inspection rather than “confirming” P3.
Upgrading Priority (Level II Raises Urgency)
Upgrade when corrected analysis shows more risk than Level I reported.
| Situation | Typical upgrade path |
|---|---|
| τ corrected from 1.0 → real window value increases ΔT across a band boundary | P4 → P3 or P3 → P2, etc. |
| ε too high on low-ε metal hid a true hotspot (after proper method) | Mild → severe |
| Level I compared to ambient only; peer ΔT is much larger | Understated relative severity |
| Absolute OEM limit exceeded though relative ΔT looked mild | Elevate on absolute axis |
| Load was higher than Level I recorded, or full-load re-survey worsens ΔT | Band increase |
| Identity fix moves fault onto critical life-safety or process feed | Same ΔT, higher operational urgency language |
Worked upgrade: Level I: sister-phase ΔT = 9 °C (P4), ε = 0.95 on bright lug, no tape. Level II tape method: true ΔT = 24 °C at 55% load → P2. Report must show original P4, corrected parameters, new P2, and rationale.
Worked upgrade (absolute): Unique VFD heat sink 105 °C, OEM max continuous 95 °C; Level I called “monitor” because no peer. Level II elevates on absolute OEM limit, not peer ΔT.
Downgrading Priority (Level II Lowers Urgency)
Downgrade when corrections show less defect severity—or no defect.
| Situation | Typical downgrade path |
|---|---|
| Reflection from lights/sun on shiny metal mistaken for connection heat | P2/P1 → non-finding or monitor after proper ε/RAT |
| Wrong peer: compared loaded phase to unloaded spare | Large false ΔT collapses when peers match load |
| Level I used unequal currents as “fault” without checking ammeter | Pattern is load imbalance, not high-R joint |
| τ or ε correction reduces ΔT across a boundary | P2 → P3, etc. |
| Transient inrush / just-started motor captured as steady state | Wait and re-measure; may clear |
| Building solar loading mistaken for insulation void without condition notes | Re-time survey; may clear |
Worked downgrade: Level I reports 38 °C ΔT P1 on a bus cover reflection of a heater. Level II confirms low ε, measures RAT, images the actual joint with tape: joint ΔT = 4 °C → P4 or no action band, with explanation that the original was a reflection false positive.
Ethics note: Downgrades must be earned by data, not by desire to reduce work orders. Upgrades must not be avoided to “keep the client calm.”
Reclassification Decision Table (Exam Drill)
| Level I call | Material correction | Level II disposition |
|---|---|---|
| P3, ΔT 17 °C | ε/RAT fix → ΔT 28 °C, load OK | Upgrade to P2 |
| P2, ΔT 30 °C | Correct peer under same load → ΔT 8 °C | Downgrade to P4 |
| P3, ΔT 14 °C | Load only 18% rated | Invalidate standard Priority; re-inspect ≥40% |
| P4, unique transformer near OEM oil/winding limit | Absolute review | Elevate per absolute/OEM even if peer ΔT small |
| P1 on “MCC-4” | Visual proves MCC-5 | Re-ID, keep severity only after identity locked |
| “Normal” | Coverage shows asset never imaged | Not a thermal pass—open item |
Documentation of Reclassification (Minimum Content)
Every change of Priority or ID should leave a trace:
- Original Level I equipment ID and Priority / narrative
- What was wrong (parameter, load, peer, identity, absolute limit)
- Corrected values and method (tape, foil RAT, window data, meter load)
- New Priority or “non-finding / re-inspect”
- Who performed Level II review and when
- Whether field re-image was required vs post-process correction only
Silent PDF edits that hide the Level I error train the organization to repeat it and destroy the learning loop (12.3).
Interaction with Multiple Severity Systems
Level II may reclassify across frameworks:
| Domain | Reclass tool |
|---|---|
| Electrical connections | NETA-style ΔT bands + load rules |
| Unique electrical assets | Absolute / nameplate / IEEE-NEMA thinking |
| Rotating machinery | ISO 18434-1-style zones vs baseline |
| Building envelope | ASHRAE-style ΔT and condition validity |
A finding can be downgraded on relative electrical ΔT yet upgraded on absolute limit—or the reverse. Report the governing recommendation clearly.
Common Traps
| Trap | Better practice |
|---|---|
| Trusting the filename over the nameplate | Believe the engraved/printed ID in the visual |
| Reclassifying without showing math | Show old ΔT, new ΔT, band |
| Keeping P1 language after proving reflection | Downgrade with evidence |
| Refusing to upgrade because “Level I already issued draft” | Truth over draft ego |
| Applying NETA peer Priority to a unique transformer only | Add absolute criteria |
| Changing ID in the table but not in the work order system | Sync CMMS / client list |
Summary for Recall
Level II locks equipment identity using visual, tags, and one-lines before anyone acts on a thermogram. After parameters, load, peers, or limits are corrected, recalculate severity and upgrade or downgrade using the same transparent bands and absolute rules taught earlier. Invalid load or non-quantitative geometry may force re-inspect instead of a fake Priority. Always leave an audit trail of original call, correction, and final classification.
Level I reports Priority 3 (ΔT = 16 °C) on a bolted lug. Level II applies correct emissivity and RAT; recalculated ΔT at ≥40% load is 29 °C versus a true sister-phase peer. Using the mapping, what should Level II do?
A Level I report labels a severe hotspot “MCC-2 Bucket 4,” but the paired visual clearly shows the nameplate for MCC-3 Bucket 4. Parameters and ΔT math are otherwise solid. Best Level II action?
When is Level II most justified in downgrading a Level I Priority 1 electrical call?
Level I assigned Priority 3 to a 12 °C phase-to-phase ΔT measured at 12% of rated load. What is the most appropriate Level II severity disposition?