BUYER KNOWLEDGE / NEW ARK
Products & Technical Specifications
Buyer questions about product families, microphone arrays, PCBA modules, specifications, and configuration boundaries.
21—34
Products & Technical Specifications
21Which models do you offer, and how do I choose between them?
The catalogue includes the LS8118F 64/expandable-channel array, the 8026F 128-channel array and the 3A-360 three-array acoustic plus EO system reference. These identify different catalogue configurations, not a simple ranking in which more channels automatically guarantee greater range or better site coverage.
Choose by the outputs you need, acoustic environment, installation boundaries and integration scope. Compare a standalone array requirement with a multi-array or acoustic-and-optical approach, then confirm the proposed hardware and acceptance tests. The three-array reference is not a guaranteed hemispherical or site-wide coverage claim.
22How many microphones are in one array?
The LS8118F is listed as a 64/expandable-channel array, while the 8026F is listed as a 128-channel array. These are catalogue channel descriptions. For a purchase, confirm the physical microphone count, populated channels and expansion arrangement of the exact unit rather than assuming every listed expansion is included.
Channel count alone does not establish detection range, localisation accuracy or simultaneous tracking capacity. Request the selected configuration's hardware description and assess its required outputs under your site's noise and geometry. Compare models using agreed acceptance measures, not just the larger number.
23What does one array cover, and how many do I need for 360 degrees?
A single array's usable coverage depends on its selected configuration, orientation, surroundings and acoustic conditions. The 3A-360 catalogue reference describes three arrays and 360-degree azimuth, but that is not guaranteed detection everywhere around a site and does not establish hemispherical coverage.
First distinguish directional field of view from validated detection coverage and localisation capability. A site survey should examine noise, obstructions and permitted mounting locations before deciding the number of arrays. Confirm the proposed coverage map through authorised validation rather than applying a fixed array count to every facility.
24How many drones can one array track at the same time?
A guaranteed simultaneous track count for one array is not established here. The About page's 16+ and 48+ concurrent-object references are initial discussion context, not confirmed per-array persistent-tracking capacities. Detecting several sound sources, classifying them and maintaining separate tracks are distinct tasks.
For the chosen model, define target types, simultaneous object count, source separation and required track continuity. Validate these together with detection and false alarms under representative noise conditions. Ask how the proposed output distinguishes individual observations from maintained tracks before using a headline count as a procurement requirement.
25What is the latency from sound to alarm?
No fixed sound-to-alarm latency is verified for every configuration. The measurement depends on where timing begins and ends: a usable acoustic observation, a processing decision and an alert received by another system are not the same endpoint. The selected processing and integration path must be specified.
Agree a timing definition and test it with labelled target observations under representative conditions. Record the relevant processing and notification intervals separately, along with detection performance. A fast isolated processing result should not be presented as the control room's end-to-end alert time.
26What power and network does each array need?
Power and network requirements must be confirmed for the selected array and processing configuration. No universal supply rating, PoE support or bandwidth figure is established here. A standalone hardware description may also exclude the needs of associated processing, networking or optical equipment.
Request a complete equipment and interface schedule covering power requirements, network connections and responsibility for site infrastructure. The survey should confirm available power, permitted communications and access at each proposed location. Qualified site personnel should assess compatibility; do not design circuits or cabling from an assumed catalogue default.
27What IP rating and temperature range do you support?
An IP rating and operating-temperature range need configuration-specific confirmation; IP66 or another rating should not be inferred from an outdoor application or a search term. Environmental suitability concerns the actual delivered enclosure and equipment, not just the general acoustic sensing principle.
Ask for the applicable model and version documentation, including the stated conditions and scope of any conformity evidence. Compare those limits with your site's exposure and operating environment. Enclosure protection does not by itself establish all-weather detection performance or approval for a hazardous area.
28How heavy is an array, and what mounting does it need?
Weight and mounting requirements must be checked against the exact array, enclosure and accessories being supplied. A verified universal weight or mounting design is not established here. The complete installed assembly may differ from the sensor alone, so procurement and structural review should use the same configuration.
Request the equipment dimensions, mass and proposed mounting requirements for review by qualified site personnel. A survey should confirm permitted locations, access and obstructions. The site-specific support and approval process should be agreed before installation, rather than adopting a generic mounting or foundation design.
29What interfaces does the system expose?
New Ark's PCBA and integration scope supports discussion of SDK/API and system interfaces, but the exact protocols and licensed functions need confirmation for the chosen configuration. MQTT, REST or a named platform connector should be treated as a requested requirement to check, not an established supported feature.
Use an agreed interface-control document to define fields, coordinate and time conventions, confidence and status information, authentication and versioning. Assign integration responsibilities and acceptance tests so both parties know what a valid event means and how compatibility will be demonstrated.
30Does processing run at the edge or on a server?
New Ark's About page describes an edge-processing direction, but that does not establish the complete processing architecture of every offered system. Acquisition, acoustic assessment, event handling and integration may have different placement requirements, which need confirmation for the selected configuration.
Request an architecture showing what runs at the array, at any local processing equipment and on any server involved. Confirm hardware requirements, network dependencies and data flows, including raw audio, features and events. Do not infer offline operation, an on-premise default or a cloud requirement from the word edge.
31How many drone signatures are in your library, and how often is it updated?
A verified signature-library count or update schedule is not established here. New Ark describes AI-assisted acoustic assessment, but that does not identify the models represented, the number of usable signatures or how often a particular product's assessment capability changes.
Ask which targets and operating conditions are covered by the proposed version and how those claims will be validated. Confirm update entitlement, delivery arrangements and any associated licensing in the project agreement. A large library count alone would not demonstrate reliable detection or model identification in your site's noise.
32Can you identify the drone model, or only detect it?
Detection, classification and exact model identification are distinct outputs. New Ark's AI-assisted acoustic assessment should not be read as a guarantee of recognising every drone model. A usable sound observation may support an assessment without establishing the aircraft's precise make, model or control-link type.
Ask what labels the proposed configuration reports, how confidence and uncertainty are shown, and which targets have been evaluated. Validate model-level claims separately from basic detection under representative conditions. Where identity matters, consider corroborating acoustic information with other authorised sensors rather than relying on sound alone.
33How do you handle wind noise and echoes?
Wind can reduce the quality of acoustic observations, while reflections and obstructions complicate the directional information available to an array. AI-assisted assessment does not establish that these effects are completely removed. Performance needs to be evaluated in the actual surroundings rather than assumed from an open-site demonstration.
Include wind conditions, reflective structures and alternative permitted locations in the site survey. During validation, compare detection, false alarms and directional or position outputs against labelled observations. Ask which mitigation measures belong to the proposed configuration and how their effectiveness will be checked.
34What is the MTBF, and what service life should we plan for?
No verified MTBF figure or service-life duration is established for the proposed equipment. A reliability statistic would need its method, operating conditions and product version identified; it should not be treated as a guaranteed lifespan or a substitute for warranty terms.
For lifecycle planning, request the selected hardware's reliability information and confirm maintenance, repair, spares and software-support arrangements in the agreement. Assess the site's environmental exposure and replacement responsibilities, and budget around documented support and component availability rather than an assumed universal lifetime.
NEW ARK / PROJECT CONSULTATION
Have a question about your site?
Share your application, target types, existing sensors and procurement requirements. We can use those details to scope the next project discussion.