14.2 Paired Image Documentation and Presentation
Key Takeaways
- Every quantitative finding should present a thermal image and a visual (visible-light) image as a pair so identity, defect context, and location are unambiguous
- Pairs should share essentially the same field of view and viewpoint; mismatched FOV invites wrong-asset interpretation
- Temperature scale, span, and palette should be consistent and honest across related images so readers can compare siblings and trends without optical tricks
- Annotations (spots, boxes, arrows, IDs, ΔT callouts) must point to the true measurement location and match the finding table
- Image processing may improve clarity but must not mislead—extreme palette or span choices that invent drama or hide faults are unethical
Numbers in a table convince engineers; images convince the people who open the panel. Level II presentation standards require paired documentation: a radiometric thermal image and a visible-light visual of the same target, prepared so a third party can locate the fault, trust the measurement markups, and avoid being misled by cosmetic processing. This section covers pairing rules, FOV guidance, scale/palette consistency, annotation discipline, and honesty in image processing.
Why Pair Thermal with Visual
Infrared alone is often a grayscale or false-color blob among look-alike metal boxes. The visual image supplies:
| Visual contribution | Benefit |
|---|---|
| Nameplates, tags, markers | Equipment identity (Chapter 13) |
| Phase colors, wire layout | Correct phase/component |
| Dirt, corrosion, loose hardware clues | Context for thermal pattern |
| Orientation (left/right, top/bottom) | Crew navigation |
| Safety context | Covers, barriers, adjacent live parts |
| Thermal contribution | Benefit |
|---|---|
| Temperature distribution | Where heat is |
| Spot/area measurements | Quantitative T and ΔT |
| Pattern type | Connection, load, reflection, air leak, moisture |
Rule of practice: If you cannot identify the asset from the visual alone, the pair is not ready for a quantitative finding release.
Same Field of View (FOV) Guidance
“Paired” means corresponding, not merely “both exist somewhere in the report.”
| Good pairing | Poor pairing |
|---|---|
| IR and visual from same stance, similar zoom framing the same cubicle face | IR of Bucket 4, visual of the entire MCC lineup from the aisle end |
| Same side of outdoor transformer | IR of bushings, visual of nameplate only on the far side |
| Roof wet area IR + visual of the same bay grid | Daytime roof visual from a prior year |
| Close-up IR of lug + close-up visual of that lug | Close-up IR + building exterior hero shot |
Practical FOV workflow
- Compose the IR for radiometry (focus, fill factor / spot size, angle).
- Capture visual from the same position immediately after (or use camera fusion if the FOV match is honest).
- If the visual must zoom for a nameplate, add a second visual: context wide shot + detail tag shot—and still keep a visual that matches the IR FOV for the fault location.
- In the report, place pairs side-by-side or stacked with a single caption linking to the finding ID.
Fusion overlays are acceptable when alignment is accurate. Misregistered fusion that paints heat on the wrong breaker is worse than separate clean pairs.
Scale, Span, and Palette Consistency
Readers compare images. If every IR uses a random auto-span, a healthy motor can look “on fire” next to a true fault that was manually compressed.
| Control | Level II guidance |
|---|---|
| Level / span | Prefer consistent span for sibling components and for trend sets of the same asset |
| Auto vs manual | Auto is fine for screening; for report presentation of related assets, lock comparable spans when it improves fairness |
| Palette | Pick one primary palette per report section (e.g., iron or rainbow) and stick to it unless a second palette is explained |
| Temperature scale bar | Always visible on quantitative IR images with units |
| Isotherms | Useful for thresholds; define the isotherm temperature in the caption |
| Scenario | Consistent presentation choice |
|---|---|
| Three-phase lug comparison | Same span and palette for A/B/C images |
| Quarterly trend of Pump P-12 bearing | Same palette; note if span changed and why |
| Building elevation survey | Similar span across facade sections when comparing anomalies |
| One extreme P1 hotspot | May widen span to avoid clipping, but state the span and still show peer images fairly |
Clipping honesty: If the hotspot exceeds the displayed max, the scale bar or caption must say so—or expand span. Silent clipping understates severity visually even when the spot meter is correct.
Annotations That Match the Data
Annotations are part of the measurement record, not decoration.
| Annotation type | Use |
|---|---|
| Spot meter | Primary quantitative point; place on intended surface, not on reflection or background |
| Box / ellipse max | Area max for larger surfaces; ensure box does not include unrelated hot objects |
| Delta tools | Show T1, T2, and ΔT when the software supports it |
| Arrows / circles | Guide the eye without covering the measurement pixel |
| Text labels | Equipment ID, phase, Priority, parameter summary as space allows |
| Cross-reference | “Finding F-017” matching the table |
Annotation integrity checks
- Spot location in IR matches the component described in the visual and table.
- Reported temperature equals the on-image readout (no manual typo).
- Reference spot for ΔT is on a true peer under similar load—not ambient air unless ambient-referenced method is declared.
- Annotations survive export (not only on the camera screen).
- Visual annotations (if any) do not imply a thermal measurement that was not taken.
Image Processing Honesty
Post-processing is allowed for clarity, not for advocacy.
| Acceptable | Misleading / unethical |
|---|---|
| Focus sharpening within reason | Adding false color heat where radiometry shows none |
| Adjusting span to show real structure without hiding the fault | Cranking span so a 40 °C ΔT looks cool gray |
| Choosing a palette for print readability | Palette designed only to maximize client alarm or to minimize work orders |
| Cropping empty margins | Cropping out the nameplate that disproves the ID |
| Noting digital zoom limits | Presenting heavy zoom as if IFOV/spot requirements were still met |
| Showing before/after repair with same palette/span when possible | “After” image with compressed span that hides residual heat |
Palette ethics exam point: There is no single “correct” palette, but inconsistent or extreme choices that change the story without changing the data are report defects. Level II prefers: (1) radiometric truth in numbers, (2) fair visual encoding of that truth, (3) captions that explain any special display choice.
Processing checklist before PDF freeze
- Scale bar present; units consistent with table.
- Palette consistent across comparison set.
- No auto-span surprises between sister phases unless noted.
- Pair FOV match verified.
- Annotations match finding IDs and ΔT math.
- Reflection or solar artifacts labeled when present so readers do not treat them as faults.
- File names or embedded metadata retain link to raw radiometric files for audit.
Report Layout Patterns
| Layout | When to use |
|---|---|
| Side-by-side IR | Visual per finding | Default for electrical/mechanical exceptions |
| Contact sheet of normals + callouts | Prove coverage; baseline gallery |
| Multi-image phase strip A/B/C | Three-phase pattern teaching in one glance |
| Trend strip (date1, date2, date3) | Chapter 12 trending deliverables |
| Wide visual key plan + detail pairs | Large buildings, roof grids, substations |
Captions should be self-contained: equipment ID, date/time, key parameters or “see table,” measured T / ΔT / Priority, and one-line recommendation pointer.
Worked Presentation Scenarios
Scenario A — FOV mismatch. IR shows a hot lug; visual is a doorway photo of the MCC room. Level II rejects the pair, requires a visual of the same cubicle face with legible ID.
Scenario B — Palette drama. Single P3 finding exported in ultra-contrasting rainbow with a 5 °C span while peers use 50 °C span. Client panics. Level II re-exports comparison set on common span, keeps Priority 3 math unchanged, and explains display correction.
Scenario C — Annotation error. Spot sits on a shiny bolt reflection; table claims joint temperature. Level II moves measurement to taped surface or correct material, reclassifies if needed, and re-annotates.
Scenario D — Honest clipping fix. Hotspot reads 120 °C; display max was 80 °C so the image is a white blob. Level II expands span, keeps spot value, and shows sister phase on the same new span for fairness.
Common Traps
| Trap | Better practice |
|---|---|
| IR-only appendix “to save pages” | Always pair for findings that drive work orders |
| Different FOV “close enough” | Match stance and framing |
| Auto-span everything in final PDF | Harmonize comparison sets |
| Covering the hotspot with a huge arrow | Annotate beside; keep pixels readable |
| Editing visual colors to “look hotter” | Never fake thermal information on the visual |
| Discarding raw radiometric files after JPEG export | Retain radiometric originals for QA |
Summary for Recall
Level II image documentation is paired, co-located, and fair. Thermal plus visual images share field of view so identity and defect location are obvious. Scales, spans, and palettes stay consistent enough for honest comparison; scale bars and units always appear on quantitative IR frames. Annotations must mark the real measurement and match the table. Processing may clarify but must not manufacture or hide severity—misleading palette or span games are ethics failures as much as technical ones. When in doubt, show the numbers clearly and make the pictures agree with those numbers.
What is the primary purpose of pairing a visible-light image with each quantitative thermal finding?
Which presentation practice is most likely to mislead a client even if spot temperatures in the table are numerically correct?
A Level II reviewer sees an IR annotation spot on a bright metal reflection while the finding table claims a bolted joint temperature. Best action?
Which FOV pairing best meets Level II paired-image guidance for a switchgear bucket finding?