New Ark Acoustic Detection logoNEW ARKACOUSTIC DETECTION

ACOUSTIC DETECTION · BUYER & TECHNICAL GUIDES / 607

01 / 3THREE DISTINCT QUESTIONS · ONE ACOUSTIC TOPIC

Acoustic UAV detection tender: One Lot or Separate Hardware and Software Lots?

An acoustic UAV detection tender does not have to choose between a single supplier and two isolated purchases in the abstract. The better question is where the buyer wants commercial accountability to sit: with one supplier responsible for a usable combination, or across clearly defined hardware and platform-software lots. Acoustic sensing remains a passive observation function, while the application that receives, stores, and presents its results may be a separate product. Packaging should make that boundary visible.

Explore PCBA deliveryDiscuss the tender scope
WRITTEN FOR607Public purchasing planner deciding how to package a general acoustic acquisition

KEY TAKEAWAY

The purchasing decision is about responsibility, not only lot count

A combined lot is attractive when the buyer needs one accountable party to supply and demonstrate a defined hardware-software combination. Separate lots can broaden competition and preserve choice, but only if the tender names the interface, test evidence, dependencies, support route, and owner for every shared deliverable. Neither structure removes the need to describe what the acoustic output means or what it does not prove.

NEW ARKChoose the lot boundary that leaves the fewest unanswered dependencies.A lotting decision should be justified against the specific requirement, market, and technical-management risk.

01

How an acoustic UAV detection tender benefits from a combined lot

Public purchasing planner deciding how to package a general acoustic acquisition

A combined hardware-and-software lot can give the purchasing team a single commercial route for a defined product combination.

The main benefit is not that one supplier magically removes integration work. It is that the tender can name one party to provide the acoustic hardware, the platform software, the agreed interface, documentation, and acceptance evidence as one package. If an event is not displayed, the buyer has a clearer first point of contractual inquiry. This can be valuable for a public body with limited technical staff or a requirement for a simple handover.

The trade-off is concentration. A combined lot may exclude smaller specialists that could supply only the sensor or only the application. It can also conceal dependencies behind a single product label: a particular processor, operating environment, licence, data format, or support subscription may be necessary even though the lot description says “complete system.” The buyer should therefore require a component and dependency schedule rather than treating the combined lot as self-explanatory.

What the single supplier must actually own

The tender should state whether the combined-lot supplier is responsible for supplying both products, integrating products from another party, or merely coordinating introductions. It should also identify who owns defects at the boundary, who supplies version information, and who maintains the customer-facing documentation. A bidder’s broad portfolio description is not a substitute for a deliverable list.

Acceptance should test the named outputs in the agreed environment. It should not silently turn a passive acoustic observation into proof of aircraft identity, operator identity, intent, or an authorised response function. Those are different questions from whether an acoustic event reaches the platform in the documented form.

02

When separate lots improve choice but create an interface gap

Public purchasing planner deciding how to package a general acoustic acquisition

Separate hardware and software lots can support competition, substitution, and future purchasing flexibility, but the interface becomes a procurement deliverable rather than an assumption.

A hardware lot may attract an acoustic module specialist, while a software lot may attract a platform provider with stronger skills in event handling, user access, storage, or reporting. The buyer can compare each capability on its own merits and avoid making one supplier’s unrelated product features mandatory. Separate lots may also reduce dependence on one source and make later replacement of one layer more practical.

The risk is a responsibility gap. The hardware supplier may say the output is available, while the software supplier says the message is not in its contracted scope. A connector, driver, licence, host computer, network permission, data retention rule, or version change can sit between the two awards. If the tender does not assign that boundary, the buyer may own the integration problem without having priced or staffed it.

Make the interface an awarded item

Name the interface format, event fields, status states, time meaning, authentication expectations, and documentation to be supplied. The wording can remain technology-neutral while still requiring a bidder to show how its product meets the boundary. Ask each lot bidder to identify prerequisites supplied by the other lot and assumptions about the customer environment.

A joint clarification or limited integration exercise may be appropriate before award where procurement rules allow it. The purpose is to establish ordinary interoperability and acceptance evidence, not to prescribe an operational deployment layout or a tactical response workflow.

03

Name shared deliverables once, with a supplying party

Public purchasing planner deciding how to package a general acoustic acquisition

A clean lot structure prevents the same item from appearing in both lots or in neither lot.

Shared deliverables commonly include interface specifications, sample messages, configuration records, release notes, test scripts, training material, and fault-report information. The tender should create a responsibility matrix with one named supplying party for each item. A second supplier may need to review or use the item, but review is different from supply and acceptance responsibility.

For example, the hardware lot might supply the sensor data dictionary and device revision record, while the software lot supplies the platform mapping and user-facing status documentation. If a joint integration report is required, the tender should say whether one lot lead produces it, both suppliers sign it, or the buyer coordinates it. This avoids double pricing, contradictory documents, and disputes over which version is authoritative.

Separate detection outputs from application behaviour

The acoustic product should describe the output it supplies, such as an acoustic event or a classification state, together with its documented status and limitations. The platform should describe how it receives, stores, displays, exports, or alerts on that output. A screen label is not evidence that the underlying sensor has identified an aircraft or located its operator.

This distinction also helps evaluation. The buyer can assess sensing documentation and platform usability without awarding unsupported claims about range, accuracy, latency, or simultaneous targets. Qualitative evidence about environmental noise, reverberation, microphone variability, and generalisation is more useful than copying a research result into a universal performance promise.

04

Keep optional services visible between the lots

Public purchasing planner deciding how to package a general acoustic acquisition

Services are often where a seemingly complete package becomes incomplete after award.

Software configuration, data mapping, installation assistance, acceptance testing, training, support, updates, and documentation may be optional in a supplier’s catalogue. That does not mean they should be absent from the tender. List each service as included, optional, customer-supplied, or excluded, and state which lot may price it. Otherwise a buyer may compare a hardware quote with a software quote that assumes the buyer will perform the integration work.

Optionality should also explain consequences. If a platform connector requires a separate licence or recurring support arrangement, the bidder should identify that dependency beside the option. If a service is not selected at award, the buyer should know whether the product remains usable, whether a later order is possible, and which party would perform the work. No supplier should be expected to promise an undefined future scope.

Use alternates without hiding the base case

Ask for a base configuration and clearly labelled alternates. A base offer might include hardware, documented output, platform receipt, and ordinary acceptance evidence. An alternate might add data export, extended support, or application customisation. Keep prerequisites and recurring obligations beside each alternate so evaluators do not add incompatible options together or mistake an optional service for a guaranteed deliverable.

The same principle applies to customer-furnished items. A host computer, network access, identity service, storage location, or translated training material should be identified as a buyer dependency rather than silently assumed to be included.

05

Put compatibility responsibility into commercial scope

Public purchasing planner deciding how to package a general acoustic acquisition

Compatibility needs a named outcome and evidence, not an implied promise that two products will work together.

The tender can require bidders to state supported hardware revisions, operating environments, interface versions, data fields, update dependencies, and known exclusions. It can also require a compatibility statement for the proposed lot combination and a route for handling a change before delivery. These are ordinary purchasing controls; they do not prescribe sensor placement, array geometry, flight routes, or response tactics.

A useful scope distinguishes demonstration from acceptance. A supplier may show an example message or replay file to explain an interface, but the buyer should decide what evidence demonstrates the contracted configuration. Acceptance might check that the named hardware produces the documented event states and that the platform handles those states as specified. It should not be written as a promise of universal acoustic performance in every environment.

Write change and support routes before award

Ask who approves a firmware or application revision, who informs the other lot supplier, and who investigates a fault that appears only at the boundary. Request revision identifiers, release notes, and a support escalation path. If the buyer expects one supplier to coordinate the other, say so and price that coordination as a responsibility rather than relying on goodwill.

New Ark describes project-scoped PCBA delivery, interface and integration support, and OEM or ODM discussions. Those are possible discussion areas, not a universal promise that every third-party platform combination is already validated. A quotation should therefore record the selected hardware, software, interfaces, services, and acceptance criteria for the particular project.

06

Request dependency statements for both lot arrangements

Public purchasing planner deciding how to package a general acoustic acquisition

Before selecting one lot or several, ask bidders to expose what their offer depends on and what it leaves to the buyer.

For a combined lot, request a statement listing every included component, external dependency, licence, customer prerequisite, interface, support item, and exclusion. For separate lots, request the same statement from each bidder plus a cross-lot dependency statement showing which party supplies, tests, documents, and supports the boundary. This gives evaluators a common basis for comparing a convenient bundle with a more open architecture.

The final choice should reflect the authority’s capacity to manage contracts and technical interfaces. If the requirement is modest and the market offers a genuinely integrated configuration, one lot may reduce management overhead. If competition, resilience, modular replacement, or specialist capability matters more, separate lots may be sensible. In either case, the tender should award a defined set of deliverables rather than a label such as “complete solution.”

A practical decision rule

Choose one lot when the buyer needs one accountable supplier, can describe the required combination clearly, and has a reason to accept concentration or reduced competition. Choose separate lots when the interfaces are mature enough to specify, the buyer can manage coordination, and the market benefits from independent bids. If neither condition is met, conduct proportionate market engagement before freezing the lot design.

Public procurement rules differ by jurisdiction. This article is general purchasing guidance, not legal advice. The purchasing team should record why its chosen structure is proportionate, how dependencies will be controlled, and how bidders will be evaluated on the same stated basis.

QUESTIONS FOR YOUR PROJECT

Buyer checklist for the lot boundary

  • Does each lot say exactly what physical hardware, software, licences, documentation, and services it supplies?
  • Who owns the interface specification, sample messages, version record, and acceptance evidence?
  • Which prerequisites are customer-furnished, and which are priced as supplier work?
  • If separate suppliers win, who coordinates integration and handles a boundary fault?
  • Are optional services, recurring support, updates, and data exports visible beside the base offer?
  • What compatibility statement covers revisions, interface versions, operating environment, and exclusions?
  • Does the acceptance approach test the agreed outputs without making unsupported acoustic performance promises?
  • Has the authority recorded why one lot, separate lots, or a permitted combination is appropriate?

REFERENCES

Sources for this article

Publisher names, dates and relevant contributions are listed below. Confirm offered product details with the supplier.

UK Cabinet Office, Guidance: Lots · 13 July 2026
Supports the discussion of lotting benefits, SME access, supply-chain resilience, and the possibility that technical risk or contract-management burden can justify not splitting a procurement.

Cybersecurity and Infrastructure Security Agency, Unmanned Aircraft System Detection Technology Guidance · 30 October 2025
Supports the distinction between selecting detection technology for situational awareness and making site-appropriate capability decisions; it does not establish a performance promise for acoustic products.

Acta Acustica, Passive acoustic detection and localization of drones using MEMS microphones · 2026
Supports qualitative cautions that environmental noise, reverberation, microphone variability, controlled-test conditions, and generalisation affect acoustic sensing interpretation.

New Ark, public acoustic detection and PCBA delivery information · Accessed 20 November 2026
Supports the limited company description of project-scoped PCBA delivery, interface and integration support, and OEM or ODM discussions subject to written project validation.

ARTICLE FAQ / 607

Questions on Acoustic UAV detection tender: One Lot or Separate Hardware and Software Lots?

Practical questions about this article and the proposed product scope.

NEW ARK / ARC-PERIMETERFAQ
RECORD
ACOUSTIC DETECTION LIBRARY

TALK TO NEW ARK

Turn the chosen boundary into a documented project scope

New Ark can discuss project-scoped PCBA delivery, acoustic interfaces, platform integration, and OEM or ODM requirements. Share the proposed lot structure and expected deliverables so the commercial and technical boundaries can be recorded for review; final compatibility and acceptance remain subject to the agreed project documents.

Explore PCBA deliveryDiscuss the tender scope

Hong Kong New Ark Intelligent Technology Limited · Acoustic detection, partner integration and local-assembly discussions.

Back to newsroom