A thermal scan records temperature patterns across an operating plant at a specific time and under specific capture conditions. Reliable thermal analysis does not extend that data beyond what it supports. It shows what was observed, where it was observed, and how the record changes over time, while root-cause and action decisions remain with the responsible engineering teams.

Four supported thermal patterns

Within Asset Intelligence, eyerod records hotspot, bypass diode activation, PID pattern, and string or module open circuit observations. Each finding is connected to a module, coordinate, date, and scan context. The same position can then be reviewed again in later scans.

The boundary of thermal data

A thermal map describes a temperature pattern and its location. Determining the underlying cause may require site conditions, electrical data, and direct examination. The project-management platform output is therefore treated as a traceable observation record rather than a diagnosis.

Why capture conditions matter

Irradiance, wind, sky conditions, and capture method affect whether thermal images can be compared. Keeping scan context with the data gives teams a stronger basis for reviewing observations from different dates. An image without its capture conditions is a weak foundation for longitudinal comparison.

A descriptive record supports better judgment

Keeping the boundary clear does not reduce the value of thermal analysis; it protects the reliability of the record. eyerod links the observation to module and location and makes change across scans visible. Engineering interpretation, maintenance planning, and field action remain with the teams responsible for the plant.

See how Asset Intelligence records and compares thermal observations over time.