Buying & Integration Guides

They cover requirement writing, supplier and factory evaluation, payload testing, mounting and centre of gravity, power and interface checks, MAVLink control, video delivery and the steps from bench test to first flight. Each guide is written for a technical buyer who needs to compare configurations without losing sight of the airframe, the operator and the delivery schedule.

The articles also address commercial and programme risk: how to separate a manufacturer from a trading company, what documentation should accompany a sample, how to compare quotations with different assumptions, and when a custom configuration is justified. The aim is a decision that holds up after delivery, not only at the quotation stage.

Use the guides as a working checklist for a new payload programme, or send the current brief to the HITS engineering team through the project inquiry form for a focused review.

• 01 Requirement brief: Mission, platform and interface constraints.

• 02 Supplier evaluation: Factory evidence, tests and documentation.

• 03 Airframe integration: Mounting, power, control and video.

• 04 Procurement: Samples, quotations and production readiness.

Turn a mission requirement into a comparable RFQ

Procurement becomes difficult when each supplier quotes a different configuration against a different assumption. A clear RFQ fixes the common baseline: aircraft type, payload mass and dimensions, mounting interface, power, control protocol, video output, operating environment and the smallest target that must be seen. It should also state the quantity for prototypes and series production, the required delivery date and the documentation needed for an engineering review.

The technical baseline should distinguish mandatory requirements from preferences. A supplier may offer a stronger sensor but exceed the payload allowance, or meet the mass target with a lens that cannot deliver the required range. Separating ‘must have’ from ‘would improve’ helps the buyer compare trade-offs instead of ranking a single headline number. It also makes it easier to identify when a custom configuration is justified.

Ask for evidence that can be checked

A datasheet is a starting point, not a test report. Ask for mechanical drawings, interface documentation, power figures, stabilisation data, environmental test evidence and sample imagery at known distances. For thermal products, request the detector, lens and NETD specification together with the conditions used for any range claim. For AI functions, ask which tasks run onboard, what hardware supports them and how the operator can verify or override a detection.

Sample evaluation should follow a written checklist. Inspect the mechanical finish and connectors, confirm the firmware and configuration, test the control protocol and video path, and record the image at several zoom levels and in the intended light conditions. If the payload will be integrated into a new airframe, include the mounting, centre-of-gravity, cable routing and electromagnetic compatibility checks in the same plan.

Compare total programme cost, not unit price

The lowest quotation can become the most expensive option if it excludes the cable set, ground-station software, integration support, spare parts or a second sample iteration. Compare warranty terms, repair turnaround, minimum order quantity, packaging, shipping terms and the availability of replacement modules. A supplier that can explain its production and test process is usually easier to qualify than one that can only provide a catalogue and a price.

For OEM and distributor programmes, confirm who owns the mechanical and software customisation, how configuration changes are controlled, and what support is available after the first batch. A clear change process protects both sides when a connector, firmware feature or mounting detail changes during a long programme.

Use the guides as a decision record

The articles below cover requirement writing, supplier evaluation, integration and acceptance testing. Read them before the first supplier call, then use the checklists to record what was verified and what remains open. If the programme needs a focused review, send the payload brief to the HITS engineering team or browse the industrial UAV camera range to build a comparison shortlist.

What to verify before the payload is released to the airframe

A guide becomes useful when it ends in a decision that can be recorded. For every requirement, note the evidence, the conditions under which it was checked, who confirmed it and what risk remains. Payload mass should include the mount, cable set and any adapter plate, not only the camera head. Power should be measured at start-up, steady state and during zoom or laser operation, because a peak that exceeds the aircraft rail can force a redesign after the payload has already been selected.

Control and video deserve the same treatment. Exercise the protocol on the bench with the actual flight controller and ground station, confirm the baud rate and message set, and check the video at the output the operator will use. A camera that produces a clean image at the connector can still fail after the cable run, the encoder or the radio link. Record latency and recovery behaviour as well as the steady-state picture.

Environmental and mechanical checks should follow the mission profile rather than a generic checklist. Confirm the operating temperature range, ingress protection, vibration and shock limits, and the clearance needed when the gimbal reaches its extremes. If the payload will be used on more than one aircraft, repeat the centre-of-gravity and mounting check for each platform.

Keep the decision record alive after delivery

Acceptance testing does not end with the purchase order. Keep the approved configuration, serial numbers, firmware versions, test records and any deviations in one place. When a replacement unit or a second batch arrives, compare it with that baseline instead of relying on memory. A documented change process also makes it easier to introduce a new lens, connector or software feature without losing the evidence that supported the original approval.

Use the articles below as a sequence: define the requirement, verify the supplier, check the airframe, then test the sample against the same criteria. If a requirement cannot be verified, mark it as open rather than assuming it will be resolved in production. That habit is what turns a collection of datasheets into a procurement decision the programme can defend.