ADC resolution is not a complete measurement-accuracy claim. When discussing a proposed measurement payload around UG35, ask what quantity must be measured, over what range and with what evidence for the complete measurement chain. A larger bit count alone does not answer those questions. This guide is technical background and editorial procurement advice, not evidence that UG35 includes a digitizer, supports a particular sensor or has achieved a tested measurement result.

The headline number is an incomplete comparison

Suppose two hypothetical proposals advertise different digitizer bit counts. A purchasing spreadsheet sorts them and puts the larger number first. The comparison looks objective, but important information is missing: what input is being measured, what configuration is proposed and what evidence supports the claimed result? Ranking a complete system from one isolated component characteristic can produce a confident decision without a well-defined measurement requirement.

The answer is not to ignore resolution. It is to give resolution the correct place in the discussion. Ask the engineering reviewer to explain how the digitizer characteristic relates to the intended decision and what other evidence is needed. Procurement can then compare bounded claims against the same requirement. Without that common basis, a supplier's concise headline may be interpreted much more broadly than the supporting documentation allows.

This distinction is useful for US and South African engineering buyers alike, but it does not establish local certification requirements or authorize an aircraft integration. The article concerns how to frame a commercial inquiry. Detailed electrical design, airworthiness considerations, installation and operational procedures belong with qualified professionals and current configuration-specific documentation, not a general blog explanation.

Code width and accuracy answer different questions

NI's official explanation of accuracy, code width and resolution relates code width to input range and bit resolution. It also discusses input noise, gain error, offset error and temperature drift as relevant to measurement quality. The bounded technical takeaway is that a bit count does not independently establish the accuracy of the complete measurement. This source describes general instrumentation concepts, not electronics installed on UG35.

For procurement purposes, separate the advertised characteristic from the statement you need to rely on. One describes a property of a proposed component or configuration. The other concerns whether the complete measurement is suitable for the buyer's decision. A supplier may have good evidence for both, but the purchasing team should request that evidence explicitly. It should not create the second claim by assuming that the first one proves it.

Start with the quantity and the decision

Write the quantity of interest in ordinary language and ask a competent reviewer to confirm the technical requirement. Avoid beginning with a preferred bit count. The team should be able to explain what the measurement will help someone decide and what happens when the evidence is inconclusive. That decision statement gives the supplier a reason to discuss the full configuration instead of simply returning a component specification sheet.

Describe the intended input range and relevant conditions only to the extent that they are known. Mark uncertain entries as questions. Do not invent a range to make the inquiry look complete, and do not assume the widest advertised range is automatically the best choice. The purpose of an early brief is to expose the information needed for a qualified response, not to simulate an engineering design that has not been performed.

Also identify the expected output. Does the organization want a raw record, a processed measurement, a screening statement or a professionally reviewed conclusion? These are possible scope categories, not claims about supplied UG35 services. A supplier cannot reliably price or explain the requested evidence if different stakeholders are using the word measurement to mean different deliverables. Resolve that ambiguity before ranking proposals.

Request evidence for the proposed chain

Ask the supplier to identify the components and processing stages covered by its claim, using an appropriate level of detail for the procurement. A claim supported for a digitizer alone should remain a component claim. A claim about the complete arrangement needs evidence that addresses the arrangement being proposed. The buyer does not need to demand proprietary design files to ask where the documented scope begins and ends.

Request the conditions attached to the evidence. A qualified response should say what configuration was assessed, what the record establishes and what remains outside its scope. If the supplier provides a general brochure, ask whether it supports the particular statement in the quotation. If additional evaluation is required, record that as a dependency. Do not convert an intention to evaluate into a completed result in the internal comparison table.

Keep the evidence tied to a version or configuration identifier wherever the proposal uses one. The record should remain intelligible if a component or setting is changed during clarification. This is an editorial document-control recommendation, not a claim about automatic traceability in any product. Its practical purpose is to keep a promising result from being carried over to a materially different proposal without a competent review.

Give uncertainty a place in the purchasing record

A useful proposal review has more than pass and fail. It can distinguish evidence received, clarification needed and evaluation not yet performed. Those statuses help the project team see what must happen before it can rely on a claim. They also prevent an unanswered accuracy question from being hidden by a fully populated spreadsheet cell containing a bit count.

Ask the engineering owner how the required evidence should be judged. The buyer should not invent an error budget, acceptance threshold or test method from a general educational source. Instead, procurement can ensure that an appropriate requirement exists, that each bidder knows it and that responsibility for review is assigned. This is a division of roles, not an excuse to leave the technical decision vague.

Consider a hypothetical bidder that offers a larger bit count but cannot yet document the complete arrangement. Another bidder gives a narrower, clearly scoped claim with an explicit evaluation plan. This example does not determine which proposal should win. It illustrates why the committee needs separate columns for advertised characteristics, evidence scope and unresolved work. Price and technical merit should not be judged on different hidden assumptions.

A short clarification agenda can be enough

Start the meeting by restating the quantity, intended decision and required output. Then ask the supplier to identify which part of the proposed chain each accuracy-related statement describes. Follow with the conditions and limitations of the supporting record. End by assigning an owner and next action to every unresolved question. This agenda keeps the discussion concrete without turning a purchasing meeting into an unplanned design session.

Record answers using the supplier's actual level of confidence. If a document provides an illustrative explanation, do not call it a test certificate. If the supplier says compatibility requires review, do not mark compatibility confirmed. If a service is separately quoted, do not include it in the aircraft price comparison by assumption. These distinctions matter because later project decisions often rely on the purchasing summary rather than the original conversation.

The field-oriented lesson is editorial analysis: define the decision before comparing the digitizer headline. It is not a report of UG35 field testing or a statement from a named engineer. The lesson helps the organization ask an answerable question and retain the limits of the answer. A larger number may be relevant, but its commercial value depends on the requirement and evidence around it.

Do not collapse other interpretation questions into bit depth

A digitizer question is only one part of evaluating measurement information. The UVH2 emissivity and reflection guide concerns a different issue: what a thermal image pattern can justify about a target surface. A technically impressive component characteristic should not be used to bypass the separate interpretation question. The buyer should know which uncertainty each piece of evidence addresses.

Similarly, the UG39 point-cloud classification guide asks what delivered categories mean and who reviews them. That is an information-contract question rather than an ADC specification. Linking the discussions is useful because a complete workflow can require several independent answers. It is not evidence that the products share sensors, electronics, processing tools or interchangeable configurations.

Frame a bounded UG35 configuration inquiry

The UG35 product page identifies the aircraft for the commercial discussion. List the proposed payload, interfaces, supporting services and evaluation needs as items requiring confirmation. Do not infer supported electronics, power arrangements, sensor performance or installation details from this article. The illustrative scene preserves the product reference but does not show a verified measurement system.

Review the VTOL and fixed-wing drone collection if the aircraft category is still under consideration. Keep configuration suitability and commercial terms subject to a current response. A product inquiry becomes more useful when it includes the measurement requirement and the missing evidence, rather than a demand for the largest available bit count with no defined application context.

Send the requirement, not just the headline target

Prepare a short note naming the quantity, known range, intended decision and required output. Add the conditions that are known, clearly mark those that are not, and list the evidence your technical reviewer needs. Contact UNITED UAV about the UG35 configuration question with that note. Ask which elements can be confirmed, which need further assessment and which services are separate. That response provides a sounder basis for procurement than treating resolution as a complete promise of measurement accuracy.