An IEPE sensor needs an appropriate excitation and conditioning path, not merely an acquisition input with a plausible voltage range. For a UG35 integration inquiry, identify the exact sensor, conditioner and input before asking a qualified engineer to assess compatibility. Keep that review separate from aircraft integration approval. The term IEPE does not establish a UG35 interface, an included vibration sensor or permission to connect equipment.

Start with the sensor architecture

A quotation can list a vibration sensor and an acquisition device without explaining how they form a working measurement chain. The buyer sees voltage figures and assumes the remaining task is choosing a connector. That skips the question of how the sensor is supplied and how its signal is conditioned. Before comparing prices, ask the supplier to identify the architecture of the proposed devices.

This is a procurement review, not an electrical design or a wiring guide. It does not specify current levels, pin assignments, test connections or operating limits. Those details must come from the exact device documentation and the responsible engineering review. The purpose is to help a buyer request the right evidence without converting a general sensor term into an unsupported system claim.

What the NI source explains

NI's official guide, Measuring Vibration with Accelerometers, describes IEPE accelerometers with built-in amplification that requires constant-current excitation and appropriate signal conditioning. It distinguishes this arrangement from charge-mode sensing. The practical point is that a generic voltage-input description does not answer every interface question. This source explains instrumentation concepts; it provides no evidence about a UG35 interface or a particular proposed aircraft payload.

Ask the engineer to identify which parts of the general explanation apply to the proposed sensor and which do not. A family name is not enough to establish the limits of an exact device. The documentation should identify the model, revision and relevant conditions. If those are not yet selected, the quotation should describe a proposal awaiting review rather than an approved configuration.

Put excitation into the responsibility table

The buyer should know which device supplies the required excitation, who confirms its suitability and where the supporting evidence will be recorded. A proposal that simply says the sensor is compatible leaves those responsibilities unclear. Ask the supplier to separate sensor identity, conditioning equipment, acquisition input and engineering verification into distinct items.

Keep the supplier's confirmed scope separate from the buyer's existing equipment. If the buyer already owns an acquisition unit, identify it accurately and ask whether the supplier has actually reviewed that device. If the conditioner is not included, show it as an unresolved dependency. Neither party should discover after purchase that each expected the other to provide a necessary part of the chain.

A clear responsibility table also distinguishes documentation from a service commitment. Providing a datasheet is not the same as designing an interface, performing a test or approving installation. Ask which deliverables are included and which require a separately appointed integrator. Unknown service availability should be stated plainly rather than inferred from a product listing.

Request an interface evidence pack

The following checklist is an editorial aid for a purchasing conversation. It is deliberately about documents and ownership, not instructions for energizing or connecting hardware. The qualified reviewer should determine the actual engineering evidence needed for the intended use.

• Exact sensor identification and the manufacturer's current documentation.
• Declared sensor architecture and the relevant excitation requirements.
• Identity of the proposed conditioner and acquisition input.
• Documentation showing the conditions and limits the engineer must assess.
• A diagram labeled as proposed or approved, with the responsible author identified.
• A written list of unresolved compatibility and integration questions.
• The scope, owner and acceptance criteria of any separately commissioned test work.

The pack should allow a reviewer to trace a claim to the relevant component and document. A brochure that describes an entire product family may be useful background, but it should not silently replace the exact device information. Ask for clarification when the model shown in a demonstration differs from the one proposed in the quotation.

Distinguish a component claim from a chain claim

A sensor can have well-documented characteristics while the proposed complete chain still needs review. The acquisition equipment may have its own conditions, and the conditioner may introduce separate responsibilities. Ask the integrator to explain the proposed combination rather than collecting unrelated favorable statements from several catalogs.

For a buyer, the important question is which conclusion the evidence supports. A document may establish that a device has a named input type. It may not establish that the complete proposed chain is suitable for the measurement task or aircraft environment. Keep each claim attached to its scope so a narrow component fact does not become a broad system promise during negotiation.

Where the supplier proposes a demonstration, request a description of the actual equipment and configuration used. The reviewer should know whether it matches the quoted arrangement and which differences remain. This article does not define a bench test or authorize one. It recommends making the identity and purpose of any professionally planned demonstration explicit.

Separate measurement review from aircraft integration

Evidence from an instrument setup should not be treated automatically as approval for an aircraft installation. The responsible integrator must identify the additional reviews appropriate to the proposed configuration. The buyer should request a written boundary between measurement-chain evidence, installation design and any operational approval that may be required.

Do not assume that a sensor's published rating answers questions about mounting, complete-system behavior or the aircraft's supported interfaces. Ask which facts are confirmed and which require a project-specific assessment. This keeps the quotation honest even when the intended application is still being defined. A useful supplier response can identify missing information without pretending to have approved an incomplete design.

The same caution applies when comparing models. A sensor arrangement discussed with one aircraft should not be copied to another merely because both belong to the VTOL category. Keep the exact configuration under review visible in every document. Any change should go back to the responsible engineering owner rather than being treated as a naming update.

A purchasing lesson about missing dependencies

The editorial lesson is to ask about excitation and conditioning before the purchase list is finalized. A buyer can otherwise order individually plausible devices while leaving the connection between them undefined. That is a scope problem the procurement team can help expose early, even though it cannot resolve the underlying engineering question itself.

Consider a hypothetical request containing a sensor model and a generic request for voltage recording. A better revision would ask the integrator to identify the sensor architecture, the required supporting devices and the evidence needed to assess the proposed chain. The revised request does not dictate a design. It gives the engineer a specific responsibility and gives the buyer a way to recognize an incomplete response.

No customer result, saved cost or successful deployment is claimed here. The proposed approach is an editorial checklist derived from the distinction between sensor identity and supported integration. Any real design decision requires the exact documents, the actual intended use and qualified review.

Make changes visible during procurement

If a supplier substitutes a sensor or acquisition device, ask which earlier conclusions need to be revisited. Do not keep an approval attached to a component that is no longer being supplied. A change record should identify the replacement, the reason for it and the person responsible for reviewing its implications.

Likewise, label unresolved items when issuing a purchase request. A provisional device list can be useful for planning, but it should not appear to authorize an installation. Ask purchasing and engineering to agree the release condition for each open item. This is especially helpful when several vendors supply different parts of the proposed measurement chain.

How UG35 enters the conversation

The UG35 product page identifies the aircraft for a configuration inquiry. It does not establish an IEPE input, a vibration acquisition package or the availability of an integration service. Ask UNITED UAV which configuration information can be confirmed and which questions need a separately scoped engineering provider. Do not infer specifications that have not been supplied.

US and Singapore integrators can use the same evidence structure while keeping their actual project requirements explicit. This is not a statement about local certification, aviation permission or electrical compliance. Identify any such requirements separately and obtain appropriate professional advice rather than relying on a general buyer guide.

Questions before accepting the interface line item

Is a matching voltage range enough? It is not a complete explanation of the proposed sensor architecture, excitation and conditioning path. Ask for the engineer-owned assessment.

Does IEPE mean the aircraft supplies it? No. Confirm the exact supporting device and its scope; the term does not establish a UG35 feature.

Can a successful demonstration approve the installation? Only the responsible reviewers can determine what the demonstration supports and what additional approval is required. Keep those conclusions separate.

Send the exact documents, not a generic compatibility claim

Source note: NI's accelerometer guide was checked on 15 October 2026; no page publication date was established. This is an editorial procurement review, not a wiring procedure, integration approval or claim of included equipment.

Related buyer questions include the interpretation of monitoring evidence and the scope of later ground-learning support. They concern different responsibilities but share the need to identify what a supplier is actually offering.

Review the VTOL and fixed-wing collection, then use the UNITED UAV contact page to provide the exact sensor and conditioner references, intended measurement question and owner of the compatibility decision. Request a bounded UG35 configuration discussion with engineering dependencies listed explicitly. The useful outcome is a reviewed path to a decision, not a connection assumed from a voltage label.