Seeing a thermal target and supporting a temperature measurement are different acceptance goals. Before selecting a proposed UVH2 inspection configuration, specify the target of interest and ask for evidence that the imaging arrangement supports the intended result. An enlarged image is not enough. Review the target at its native acquisition scale, the proposed measurement footprint and the limitations of the complete configuration. This guide does not assign a sensor specification or temperature-accuracy claim to UVH2.

What must the inspection result actually say?

A buyer may want to notice an unusual pattern, identify the asset associated with it, compare observations or report a defensible temperature measurement. These requests can appear together in a tender while requiring different evidence. Start by naming the decision the report must support. A supplier cannot give an answerable configuration proposal if every attractive thermal image is treated as equivalent to a validated measurement.

For industrial inspection teams in the United States and the United Kingdom, this is a practical procurement question. Define the smallest relevant target or feature, describe the proposed viewing situation and explain what will happen after the observation. The technical provider should then identify what evidence is needed. Do not let a demonstration image choose the acceptance criterion after the hardware comparison has already begun.

The documented distinction behind the footprint question

FLIR's Understanding Distance:Size Ratio, published May 8, 2020 and accessed October 1, 2026, discusses target size, viewing distance and instantaneous field of view. It explains that digital zoom does not improve measurement accuracy. Its examples are technical background for asking a better question, not universal acceptance limits and not evidence of a UVH2 sensor's capabilities.

The rest of this article is United UAV purchasing analysis. Ask the proposed sensor or measurement provider to explain the footprint relevant to its specific equipment and the intended result. Do not convert a generic illustration into a flight altitude, operating distance or accuracy promise. The actual configuration, conditions and competent review must establish whether the requirement is supportable.

Write a target statement that a provider can evaluate

Identify the feature the buyer needs to distinguish, not just the whole asset that contains it. A broad description such as inspect the installation may conceal a much smaller decision-critical area. Provide a drawing or other authorized description where appropriate, and ask the provider to state which part of that feature must be represented for the proposed interpretation.

Then describe the expected observation conditions at the level needed for a configuration discussion. Separate confirmed project constraints from assumptions that remain open. The provider should explain what additional information is required before making a measurement claim. It is better to record an unresolved requirement than to force a premature answer from a product title or a single promotional image.

State the deliverable as well. A visual observation report, a prioritized review list and a quantitative measurement report are not interchangeable descriptions. Ask who will interpret the data and who will approve any resulting action. That responsibility should remain clear even when the aircraft, payload, software and reporting work come from different parties.

Ask for native-scale evidence, not only a large presentation

Request a view that preserves the relationship between the target and the acquired image, together with the provider's explanation of its measurement basis. A presentation enlargement can help a meeting audience see the feature, but it should not replace the evidence used to justify the result. Ask the supplier to identify which view is for communication and which record supports the technical claim.

Keep file identity and configuration context attached to that evidence. If the provider changes the proposed sensor, lens, processing or intended use, ask whether the previous demonstration remains relevant. Do not assume that an example from a different arrangement proves the new proposal. A useful response identifies what is comparable, what is different and which claim the evidence can still support.

Where the evidence is insufficient, define the next decision rather than negotiating a stronger adjective. The project might narrow its reporting claim, seek additional evaluation or consider a different configuration. Those are legitimate procurement outcomes. Calling the image high resolution does not resolve a missing link between the target footprint and the measurement requirement.

Separate detection evidence from measurement evidence

The table is a way to separate purchasing questions, not a universal thermal-inspection standard. The technical owner should adapt the acceptance review to the actual application. A contract can require several outcomes, but it should not use evidence for one as an automatic substitute for another. That distinction makes supplier comparisons more meaningful and keeps limitations visible.

A field lesson: show both views in the review

Ask for the target at native acquisition scale and at the scale used in the presentation report. Have the provider explain which conclusions each view supports. This is an editorial review habit, not a claim that a real customer encountered a particular failure. It gives the buyer a concrete way to discuss evidence without pretending that visual inspection alone can validate temperature measurement.

If the enlarged view is the only evidence available, record that limit. Ask for the relevant acquisition and configuration information before approving a stronger claim. Do not assume bad intent or reject a useful observation merely because it is not a quantitative measurement. Instead, align the language of the deliverable with the evidence actually supplied and identify what would be needed to go further.

Budget for the review, not just the image capture

A quote should distinguish acquisition, interpretation and reporting responsibilities. Ask whether the price includes a configuration-specific measurement explanation, review of exceptions and delivery of the agreed supporting records. A lower quote may simply cover a narrower task. That is not inherently a problem, provided the buyer understands the boundary and has assigned the remaining work.

Also agree how inconclusive targets will be reported. The buyer needs to know which observations require another review and which fall outside the accepted scope. A blank cell or absent annotation should not have an undocumented meaning. This is especially important when the report passes from the inspection contractor to an asset owner who did not attend the original technical discussion.

Do not let one gate stand in for the whole measurement case

A target-footprint discussion is not a complete measurement validation. Calibration evidence, configuration identity and relevant conditions still need competent review. The companion validated calibration-range guide explains how to keep one of those boundaries explicit in a quote. Its general purchasing questions do not establish that a particular measuring payload is included with either aircraft.

If an inspection project also uses a processed spatial representation, document what changed between source evidence and delivered output. The point-cloud removal review offers a separate example of traceable processing decisions. Apply that connection only where the actual workflow includes such data. The shared lesson is to preserve the reasoning between an observation and the claim presented to the buyer.

Frame a bounded UVH2 configuration inquiry

The approved UVH2 product page is the starting point for a model-specific discussion. It does not, by itself, answer the target-footprint question or establish an included sensor's temperature accuracy. Ask for confirmed configuration details, the proposed measurement arrangement and the evidence supporting its intended use. Keep any unresolved lens, sensor or processing detail explicitly open.

Compare options in the VTOL and fixed-wing drone collection against the same mission brief, without assuming that every platform offers the same payload or reporting services. A useful comparison states which requirements have evidence, which need integration work and which are not being claimed. That is more actionable than ranking aircraft by a thermal illustration whose acquisition context is unknown.

Request evidence against a named target

A useful acceptance discussion can compare two proposed report statements about the same target: an observation requiring follow-up and a quantitative measurement intended to support a decision. Ask the provider to identify the evidence needed for each statement and the point at which it would decline the stronger claim. This does not prescribe a measurement threshold. It makes the reporting boundary explicit and gives the buyer a way to distinguish a useful limited result from an unsupported conclusion.

Send the United UAV inquiry team the target description, intended observation or measurement, expected report and responsible reviewer. Ask the response to separate confirmed configuration facts from evaluation still required. Request an explanation of the relevant footprint and its limitations, together with an agreed way to report inconclusive cases.

The objective is not to make every image support the strongest possible conclusion. It is to choose a configuration and reporting scope that fit the buyer's actual decision. Keep detection, identification, measurement and action as distinct questions until the evidence connects them. That makes a thermal inspection proposal easier to assess without turning an enlarged target into an unsupported measurement promise.