ITC Thermographer Level III study materials
ITC Thermographer Level III study resources

ITC Thermographer Level III: Thermography program management and standards

ITC Thermographer Level III · Work through your exam, one topic at a time.

All guide sections

Thermography program management and standards

Domain 2 - Thermography program management and standards

This domain tests whether you can run a defensible program rather than take isolated pictures: written procedures, standards, baseline conditions, severity criteria, data control, corrective action, and safety.

Core rules

  • Build a documented program with scope, responsibilities, route sheets, inspection procedures, severity criteria, reporting, data retention, and audit. ISO 18434-1 provides general thermography procedures for machines; ASTM E1934 guides electrical and mechanical inspections.
  • Qualify personnel to ISO 18436-7 categories; use NFPA 70B for electrical maintenance practices and NFPA 70E for arc-flash safety, including PPE and infrared windows.
  • Establish baselines under repeatable load and environment: similar time of day, load above a stated minimum, low wind, no solar loading, and stable ambient.
  • Severity should use ΔT against similar components and ambient, plus load and trend - not absolute temperature alone. Define repair priorities and re-scan after repair to verify.
  • Record equipment ID, load, ambient, wind, ε, reflected temperature, distance, camera, and analyst; keep raw radiometric files.

Worked example

A 480 V disconnect shows phase A 72 °C, B 61 °C, C 60 °C, ambient 25 °C, load 65%. The A-to-B ΔT is 11 K; similar disconnects show 2–3 K. The pattern indicates a probable loose connection, so schedule an electrician. After repair, re-scan at the same load: ΔT should return to the 2–3 K range. The absolute 72 °C is secondary to the phase imbalance and comparison.

Traps

No baseline; comparing scans at different loads; treating a certificate as a program; skipping post-repair verification; ignoring wind or solar effects; and using vague severity language that cannot be audited.